Queue Configuration
You can define queues using the Tools menu.
For more information and step by step instructions, refer to Creating an Inbound Queue and Creating an Outbound Queue.
Communication Context for Incoming Messages
TIBCO MDM requires that each incoming message from external applications be assigned a set of differentiating attributes.
These attributes allow the application to apply different processing methods to different types of messages. These attributes are associated with an incoming message by associating a communication context. A receiver is defined, and the receiver is then assigned to a queue. All messages received on that queue are assigned the same attributes. These attributes are added to a message when it is transferred from external queue to internal queue.
Communication Context for Outgoing Messages
A Communication context can be used to assign attributes to a message being sent from an application.
When the application sends a message, it is received by the receiver manager configured for the queue. This receiver manager uses an associated communication context to assign properties to the message.
However, when the application sends a message, some properties may already be assigned (for example, packagingScheme and commType) in the workflow. Once assigned, such properties are not overridden by the communication context during the message exchange between internal and external integration queues. If specified in the communication context, such properties are ignored.
New commType
If you do not want to use the default commType JMS, you can define a new communication context. Start with defining a commType in the workflow, for example, MyCommType. This parameter is an input to the SendProtocolMessage workflow activity.
<Parameter direction="in" name="BizProtocol" type="string" eval="constant">MyCommType</Parameter>
Ensure that the name of the new commType does not start with the names of any of the existing commTypes.