There are two Dynamo Message System configuration files that you may have to edit as part of setting up a custom event:
The
dynamoMessagingSystem.xmlfile, located in your configuration path at/atg/dynamo/messaging/dynamoMessagingSystem.xml. Each product in the ATG suite adds its own message definitions to this file. The default contents of the Scenarios module version of this file are shown below.The
dynamoMessagingSystemDSSGlobal.xmlfile, which is specifically used to define message source and message sinks for global scenario events. The default file is located in your configuration path at/atg/dynamo/messaging/dynamoMessagingSystemDSSGlobal.xml. Note that the name of the file is specified by theglobalConfigurationFileproperty of theScenarioManagercomponent.
For information on how the system combines the contents of these files, refer to the Dynamo Message System chapter in the ATG Platform Programming Guide.
By default, the Scenarios module adds the following to the dynamoMessagingSystem.xml file:
message-registrydefinitions for all JMS messages that come with the Scenarios module, including global JMS messages.message-sourcedefinitions for the following ports:IndividualTimersSlotItemRequestport
message-sinkdefinitions for the following ports:IndividualEvents
ProcessUpdates The default dynamoMessagingSystemDSSGlobal.xml file contains the following:
message-sourcedefinitions for the following ports:CollectiveTimersBatchTimersProcessUpdatesSegmentStartTimers
message-sinkdefinitions for the following ports:GlobalEventsIndividualTimersCollectiveTimersBatchTimersSegmentStartTimers
You can extend either configuration by creating a file with the same name in your localconfig directory or within your custom application module.
If you are adding a global event, do the following:
Add a
message-sourcedefinition for this event. If you want this event to be listened to by the Scenario Manager, you must add the definition to thedynamoMessagingSystemDSSGlobal.xmlfile (see Configuring the Message Source). If you want the event to be listened to by other message sinks (for example, custom applications that you have set up to use the contents of Scenarios module messages), add the definition to thedynamoMessagingSystem.xmlfile.Add a
message-registrydefinition for this event to thedynamoMessagingSystem.xmlfile (see Configuring the Scenario Manager to Receive Your Message).
For an individual event, add both the message-source and message-registry definitions to the dynamoMessagingSystem.xml file.
