TIBCO MDM Customization Guide - TIBCO Product Documentation

174 Chapter 7 Customizing Data Synchronization|Configuring QueuesFor communication between two different enterprises, a couple of gateways areneeded to transport messages across two firewalls, and to transfer messages fromthe Q_ECM_INTGR_STD_OUTBOUND_INTGR_MSG queue of the sender instance to theQ_ECM_INTGR_STD_INBOUND_INTGR_MSG queue of the receiver instance.The same physical queue (Q_ECM_INTGR_STD_INBOUND_INTGR_MSG) hosted onone of the JMS servers (the one connected to TIBCO MDM M/P) can be used, andyou can map it to the following:— logical queue (StandardOutboundIntgrMsg) used for sending outboundintegration messages from the Brand Owner instance, and— logical queue (StandardInboundIntgrMsg) used for receiving inboundintegration messages in the TIBCO MDM M/P instance.This is possible because the messaging framework allows:1. Mapping between logical queue name and physical queue names.2. Connectivity to multiple JMS servers from the same instance.The following configuration changes need to be made:• Since Brand Owner will need to connect to two different queue managers, itwill need two different clusters.• If the Brand Owner instance is using MQSeriesCluster, add the followingproperties using Configurator. This is just a copy of the MQSeriesClustersection with a different queue manager (VeloselMPJMSQMgr) and a differentIP address (VeloselMPJMSServerIPAddress):Properties needed by the messaging framework:— com.tibco.cim.queue.cluster.MQSeriesCluster2=\inherit:com.tibco.cim.queue.cluster.DefCluster— com.tibco.cim.queue.cluster.MQSeriesCluster2.clusterLiaison.class=com.tibco.mdm.integration.messaging.queue.ibm.MQSeriesClusterLiaison— com.tibco.cim.queue.cluster.MQSeriesCluster2.replaceAllConnOnFailure=trueTIBCO MDM Customization Guide