The /atg/dynamo/messaging/MessageImporter component, whose receiveObjectMessage() method is invoked by JMS Web Services, is a Patch Bay message source. When a Web Service invokes the method, the message passed to that method is sent either to the destination patchbay:/sqldms/MessageImporter/IndividualEvents or to patchbay:/sqldms/MessageImporter/CollectiveEvents, depending on the message type.

The standard Patch Bay configuration file, /atg/dynamo/messaging/dynamoMessagingSystem.xml, includes the necessary declarations for the message source and destinations:

<message-source>
 <nucleus-name>
 /atg/dynamo/messaging/MessageImporter
 </nucleus-name>

 <output-port>
 <port-name>
 IndividualEvents
 </port-name>
 <output-destination>
 <destination-name>
 patchbay:/sqldms/MessageImporter/IndividualEvents
 </destination-name>
 <destination-type>
 Topic
 </destination-type>
 </output-destination>
 </output-port>
 <output-port>
 <port-name>
 GlobalEvents
 </port-name>
 <output-destination>
 <destination-name>
 patchbay:/sqldms/MessageImporter/CollectiveEvents
 </destination-name>
 <destination-type>
 Queue
 </destination-type>
 </output-destination>
 </output-port>
</message-source>

The Scenario Manager is a message sink configured to receive messages from these destinations. This configuration occurs in two places:

You can configure other message sinks to receive messages from the patchbay:/sqldms/MessageImporter/IndividualEvents destination by declaring them in the dynamoMessagingSystem.xml file. Note, however, that you cannot configure other sinks to receive messages from patchbay:/sqldms/MessageImporter/CollectiveEvents. This destination is a queue, used by global Scenario Managers only; adding sinks to this destination may interfere with the global Scenario Managers receiving messages. If you want another message sink to receive these messages, configure an additional destination for MessageImporter to send global scenario events to, and configure your sink to listen to that destination instead.