Comentários (2)

1 CHRIS64 comentou às Link permanente

Hi Roy,
Would you happen to know how Commerce determines whether a message should be handled by a serial inbound MQ connector or a parallel inbound MQ connector?

 
I can see them both defined and enabled in the wc-server.xml along with the Listener for "WebSphere MQ (TransportAdapter)" component which uses the TransportAdapter to load up the connectors at startup.
I can also see the MessageMappers defined for given message types.
 
There just doesn't seem to be any connection between the messageMapper and which connector it is linked to.
 
Cheers
Chris

2 Roy.Leung comentou às Link permanente

@CHRIS64
For the answer of the question, the connector that handles the message is determined by the queue that you setup in MQ, and by the configuration you follow in the Additional Software Guide or the link below:
Configuring WebSphere Application Server for use with WebSphere MQ
http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/index.jsp?topic=/com.ibm.commerce.integration.doc/tasks/tcvconfigure_was_for_mq.htm
Creating WebSphere MQ messaging provider queue destinations
http://publib.boulder.ibm.com/infocenter/wchelp/v7r0m0/index.jsp?topic=/com.ibm.commerce.integration.doc/tasks/tcvjmsqueuedestination.htm

 
There, you should have configured JMSParallelInboundQueue to connect to a queue in MQ, in which all messages are processed by the parallel connector. Similar case happens to JMSSerialInboundQueue.
I do not believe this has to do with message mapper.
Hope this helps.
 
Roy