Defining a New Pipeline for Outgoing Integration Messages

To define a new pipeline for the outgoing integration messages, you need to create the outbound queues in Configurator. For information on the outbound queue creation, refer to Creating an Outbound Queue.

The subsequent sections provide integration messages details that you need to enter during queue creation.

Procedure

  1. In the Queue Definition fields, enter the following details to send messages from TIBCO MDM to the ActiveMatrix BusinessWorks project, create an outbound queue:
    Outbound Queue - Queue Definition for ActiveMatrix BusinessWorks Integration
    Field Name Description
    Logical queue name Specify the logical queue name as CimBK2IntegrationOutboundIntgrMsg.
    Physical queue name Specify the physical queue name as Q_CIM_CUSTOMIZATION_BK2_OUTBOUND_INTGR_MSG.
    Add to external JNDI file Do not select this check box.
  2. Click Next to continue.
    The queue entries are added to the cluster level under Queue Setup > Queue Definition > CimBK2IntegrationOutboundIntgrMsg.
  3. In the Additional Properties fields, enter the following details to inherit or override standard properties.
    Outbound Queue - Additional Properties for ActiveMatrix BusinessWorks Integration
    Field Name Description
    Communication Context Name Select the check box if it is a communication context name.
    Payload Packaging Scheme Name Specify a name for the payload packaging scheme. For example: BK_INTEGRATION_OUT_2

    Note: If you have selected the Communication Context Name check box, the Payload Packaging Scheme Name field is enabled.

    Inherit Outbound Sender Manager Properties Select this check box to use the sender manager by inheriting properties from the standard outbound sender manager. The inherited properties can be edited.
    IO Process Template Select the StandardOutboundIntgrMsgStringMsgIOProcess IO process template option from the drop-down list. For information on the various IO process templates, refer to Outbound Queue - Additional Properties.
    Use Internal Transport Clear this check box.
  4. Click Next to continue.
    Note:
    • Since the sender manager has been defined by inheriting outbound sender manager properties, the Sender Properties are added at cluster level under Backend Integration Initialization.
    • The sender manager destination name property is added at cluster level under Integration Setup - External.
    • Since the sender manager pool size can be altered for each instance in the cluster, the sender pool size property is added at instance level under Integration Setup - External.
    • The Sender manager is added to the user defined sender initialization list, which is present at cluster level Backend Integration Initialization > com.tibco.cim.initialize.sender.user.
    • To define routing of messages based on the packaging scheme (to select CimBK2IntegrationOutboundIntgrMsgOutboundQueueSenderManager to send messages), the BK_INTEGRATION_OUT_2 Integration Outbound Sender Property Key property is added at cluster level under Backend Integration Initialization.

    A pipeline of marshalers and unmarshalers can be defined for internal queues to enhance the message after it is delivered by the workflow.

  5. In the Unmarshalers step, some of the message processors in this screen are already selected and ordered in a particular sequence. These message processors are defaulted from StandardOutboundIntgrMsgStringMsgIOProcess. No more message processors need to be selected or reordered.
  6. Click Next.
  7. In the Marshalers step, some of the message processors on this screen are already selected and ordered in a particular sequence. These message processors are defaulted from StandardOutboundIntgrMsgStringMsgIOProcess.
    1. For Message Content Processors, in addition to already selected message processors, you need to select two more message processors. Select the following corresponding check boxes:
    • CommCommandInfoToMessageContentCarrierMessageContentToMessageContentMarshaler
    • CustomStdIntgrOutboundMessageContentToMessageContentMarshaler.

      Reorder the sequence so that following sequence is obtained for the selected message processors:

    • CommCommandInfoToMessageContentCarrierMessageContentToMessageContentMarshaler CustomStdIntgrOutboundMessageContentToMessageContentMarshaler MapToMessageContentCarrierMessageContentProcessor
    • TransformFileMessageContentProcessor
    • CreateStringMessageContentProcessor
  8. Click Next.
    The following properties are overridden to define an unmarshaling pipeline using the unmarshalers selected during queue creation:
    • Message Unmarshalers List: com.tibco.cim.queue.queue.CimBK2IntegrationOutboundIntgrMsg.msgIO.msgContentUnmarshaler.msgFromMsgUnmarshalers
    • Message Content Extractor: com.tibco.cim.queue.queue.CimBK2IntegrationOutboundIntgrMsg.msgIO.msgContentUnmarshaler.msgContentFromMsgUnmarshaler
    • Message Content Unmarshalers List: com.tibco.cim.queue.queue.CimBK2IntegrationOutboundIntgrMsg.msgIO.msgContentUnmarshaler.msgContentFromMsgContentUnmarshalers

      The following properties are overridden to define a marshaling pipeline using the marshalers selected during queue creation:

    • Message Content Marshalers List: com.tibco.cim.queue.queue.CimBK2IntegrationOutboundIntgrMsg.msgIO.msgContentMarshaler.msgContentToMsgContentMarshalers
    • Message Creator: com.tibco.cim.queue.queue.CimBK2IntegrationOutboundIntgrMsg.msgIO.msgContentMarshaler.msgContentToMsgMarshaler
    • Message Marshalers List: com.tibco.cim.queue.queue.CimBK2IntegrationOutboundIntgrMsg.msgIO.msgContentMarshaler.msgToMsgMarshalers
  9. In the Communication Context step, the communication context name (by default, JMS) and properties are displayed.

Outbound Queue - Communication Context for ActiveMatrix BusinessWorks Integration
Property Name Description
Communication Context Name By default the communication context name is generated based on the logical queue name that you have specified in the Queue Definition step.
Payload packaging scheme Select the check box. Enter BK_INTEGRATION_IN_2 in the New Value column.
Override Property To override any property, select the Override Property check box and provide a new value for the property.

  1. Click Finish. The CimBK2IntegrationOutboundIntgrMsg queue properties are added to the Configurator.
  2. Click Save to save the changed configuration.