TIBCO MDM Customization Guide - TIBCO Product Documentation

Configuring Queues| 175Vendor specific properties:— com.tibco.cim.bus.cluster.MQSeriesCluster.clusterLiaison.clusteredQMgrs=LocalhostQMgr— com.tibco.cim.queue.cluster.MQSeriesCluster2.clusterLiaison.clusteredQMgr.LocalhostQMgr.connFactory.mqQMgr=VeloselMPJMSQMgr— com.tibco.cim.queue.cluster.MQSeriesCluster2.clusterLiaison.clusteredQMgr.LocalhostQMgr.connFactory.mqHost=VeloselMPJMSServerIPAddress— com.tibco.cim.queue.cluster.MQSeriesCluster2.clusterLiaison.clusteredQMgr.LocalhostQMgr.connFactory.mqPort=— com.tibco.cim.queue.cluster.MQSeriesCluster2.clusterLiaison.clusteredQMgr.LocalhostQMgr.connFactory.mqChannel=SCC_ECMThe mapping of the logical queue to the physical queue on the Brand Ownerinstance needs to be changed to use Q_ECM_INTGR_STD_INBOUND_INTGR_MSG(instead of Q_ECM_INTGR_STD_OUTBOUND_INTGR_MSG) hosted on the JMSserver connected to the TIBCO MDM M/P instance (the queue will be hostedby MQSeriesCluster2).Set the following properties in the Configurator:Properties needed by the messaging framework:— com.tibco.cim.queue.queue.StandardOutboundIntgrMsg=\inherit:com.tibco.cim.queue.queue.DefOutboundIntgrQueue— com.tibco.cim..queue.queue.StandardOutboundIntgrMsg.cluster=MQSeriesCluster2— com.tibco.cim.queue.queue.StandardOutboundIntgrMsg.msgIO=\inherit:com.tibco.cim.queue.msgIO.process.OutboundIntgrMsgIOProcess— com.tibco.cim.queue.queue.StandardOutboundIntgrMsg.addToJNDI=trueCluster specific properties - JNDI:— com.tibco.cim.queue.queue.StandardOutboundIntgrMsg.cluster.JNDICluster2.jndiQueueName=Velosel_Queue_StandardInboundIntgrMsgCluster specific properties - MQSeries:— com.tibco.cim.queue.queue.StandardOutboundIntgrMsg.cluster.MQSeriesCluster2.mqBaseQueue=Q_ECM_INTGR_STD_INBOUND_INTGR_MSGTIBCO MDM Customization Guide