Defining a New Pipeline for Incoming Integration Messages (Sample 1)

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

Procedure

  1. In the Queue Definition fields, specify the following details to send messages from the ActiveMatrix BusinessWorks project to TIBCO MDM.
    Inbound Queue - Queue Definition for ActiveMatrix BusinessWorks Integration
    Field Name Description
    Logical queue name Specify the logical queue name as CimBK1IntegrationInboundIntgrMsg
    Physical queue name Specify the logical queue name as Q_CIM_CUSTOMIZATION_BK1_INBOUND_INTGR_MSG
    Add to external JNDI file Do not select this check box.
  2. Click Next to continue.
    Note: The queue entries are added to the cluster level under Queue Setup > Queue Definition > CimBK1IntegrationInboundIntgrMsg.
  3. In the Communication Context step, you can assign distinguishing message properties. Enter the following details in the Communication Context fields:
    Inbound 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. Specify BK_INTEGRATION_IN_1 in the New Value column.
    Override Property For other communication context properties, the default values are displayed. To override any property, select the Override Property check box and provide a new value for the property.
  4. Click Next to continue.
    Note:
    • The communication context properties are added to the cluster level under Messaging Settings.
    • The entries of payload packaging scheme definition are added to the cluster level under Backend Integration Initialization.
  5. In the Receiver Manager step, specify the following details to receive messages on the queue:
    Inbound Queue - Receiver Manager for ActiveMatrix BusinessWorks Integration
    Field Name Description
    Receiver Manager Name Automatically generated. Leave as is.
    Receiver Manager Class Select the MqMessageReceiverManager receiver manager class.
    Pool Size The default is eight. Leave as is.
    Message Acknowledgement Mode The default is autoAck (automatic acknowledgement). Leave as is.
    IO Process Template Select the StandardInboundIntgrMsgStringMsgIOProcess

    IO process template.

  6. Click Next to continue.
    Note:
    • The receiver manager properties are added to the cluster level under Backend Integration Initialization.
    • Since the receiver manager pool size can be altered for each instance in the cluster, this property is added at the instance level under Integration Setup - External.
  7. In Unmarshaler step, define an unmarshaling pipeline for the receiver manager so that TIBCO MDM can read the messages received on this queue. The message processors are defaulted from the StandardInboundIntgrMsgStringMsgIOProcess IO process template. No more message processors need to be selected or reordered.
  8. Click Next to continue.
    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.CimBK1IntegrationInboundIntgrMsg.msgIO.msgContentUnmarshaler.msgFromMsgUnmarshalers
    • Message Content Extractor: com.tibco.cim.queue.queue.CimBK1IntegrationInboundIntgrMsg.msgIO.msgContentUnmarshaler.msgContentFromMsgUnmarshaler
    • Message Content Unmarshalers List: com.tibco.cim.queue.queue.CimBK1IntegrationInboundIntgrMsg.msgIO.msgContentUnmarshaler.msgContentFromMsgContentUnmarshalers
  9. In the Sender Manager step, specify the following details to send message to TIBCO MDM:
    Inbound Queue - Sender Manager for ActiveMatrix BusinessWorks Integration
    Field Name Description
    Sender Manager Name Automatically generated using the logical queue name. Leave as is.
    Sender Manager Class Select the MqMessageSenderManager sender manager class.
    Pool Size The default is eight. Leave as is.
    Message Persistence By default, the check box is selected. Specifies whether the message senders are to send persistence messages. Leave as is.
    Do you want to define marshaling pipeline? Select the check box to override the existing marshaling pipeline before sending the message to TIBCO MDM for further processing.
  10. Click Next to continue.
    • The sender manager properties are added to the cluster level under Backend Integration Initialization.
    • Because the sender manager pool size can be altered for each instance in the cluster, this property is added to the instance level under Integration Setup - External.
    • To define routing of messages based on the packaging scheme, to select CimBK1IntegrationInboundIntgrMsgInboundQueueSenderManager the sender manager, and to send messages to TIBCO MDM, the following property is added to the server level under Backend Integration Initialization. 
      BK_INTEGRATION_IN_1 Integration Inbound Sender Property Key: com.tibco.cim.init.IntraCommunicatorMessagingManager.commType.JMS. payloadPackagingScheme.BK_INTEGRATION_IN_1.inboundMsgSenderManager.startupInitObjPropKey
  11. In the Marshaler step, some of the message processors are already selected and ordered in a particular sequence based on the CommStandardInboundIntgrMsgMsgIOProcess marshaling pipeline. Do not select or reorder any other message processors. You need to change only the XSLTransformMessageContentProcessor's XSL file property.
    1. Click the Edit link for XSLTransformMessageContentProcessor. The Edit Properties screen is displayed.
    2. Change the XSL file property value to standard/maps/mpfromebxml21envelopetomlxml_Sample1.xsl
    3. Click Done.
  12. Click Next to continue.
    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.CimBK1IntegrationInboundIntgrMsg_Sender.msgIO.msgContentMarshaler.msgContentToMsgContentMarshalers
    • Message Creator: com.tibco.cim.queue.queue.CimBK1IntegrationInboundIntgrMsg_Sender.msgIO.msgContentMarshaler.msgContentToMsgMarshaler
    • Message Marshalers List: com.tibco.cim.queue.queue.CimBK1IntegrationInboundIntgrMsg_Sender.msgIO.msgContentMarshaler.msgToMsgMarshalers
  13. In the XPath Definition File step, enter location of the externalized XPath definitions file. The default xpath.props file is located at $MQ_HOME/config/xpath.props. Change the value to $MQ_HOME/config/Sample_xpath.props.
  14. Click Finish.

    The CimBK1IntegrationInboundIntgrMsg queue property is added to the Configurator at the cluster level under Queue Setup > Queue Definition.

    Because the marshaling pipeline is also defined for the sender manger, another category is created at the cluster level under Queue Setup > Queue Definition
The name of this category is set, based on the logical name of the newly created queue CimBK1IntegrationInboundIntgrMsg_Sender.

  15. Click Save in the Configurator.

Result

To associate the XPath property file with the payload packaging scheme, the following property is added at the cluster level under Backend Integration Initialization:

BK_INTEGRATION_IN_1 XPath Terms Configuration File: com.tibco.cim.neutralizexpath.propFile.BK_INTEGRATION_IN_1