Channel

BP Server requires the following information to publish a message to the specified destination:

JMS Topic Name or Queue Name

Server Properties

Factory class

Provider URL

Principal

Credential

The provider URL includes variable information, like host-name, port number. In general, any change in the server properties should not force you to make any change in the message publisher workstep definition. This means, the above properties required for a message destination cannot be stored in the publisher workstep. Instead, it uses alias for all these properties with a unique channel name as described below:

<ChannelDescriptor>
    Channel type="JMS" name="{channel-name}">
    Description/>
    <Destination type="QUEUE">{dest-name}</Destination>
    <Server local="false">
    <FactoryClass/>
    <Provider/>
    <Principal/>
    <Credential/>
    </Server>
    </Channel>
</ChannelDescriptor>

As shown above, a channel is an alias that identifies a JMS destination and its server properties, where the JMS destination is accessible. The <Server> tag is optional for the local server, where BP Server is running. When no server properties are defined for a channel, BP Server automatically looks up the destination within the local server.

An example :

<ChannelDescriptor>
    <Channel type="JMS" name=" ProductChannel ">
    <Destination type="QUEUE"> jms/ProductQueue Destination>
    <Server local="true"/>
    </Channel>
</ChannelDescriptor>

In this section:

BP Server channel