ATG Commerce includes the Patch Bay configuration required for data logging. Logging components use the messageSource property to specify a component to use as the source for logging messages, as shown in this example:
messageSource=/atg/dynamo/service/LogRotationMessageSource
The LogRotationMessageSource component is responsible for sending out logging-related JMS messages. The message source definition for this component in dynamoMessagingSystem.xml is:
<message-source> <nucleus-name> /atg/dynamo/service/LogRotationMessageSource </nucleus-name> <output-port> <port-name> DEFAULT </port-name> <output-destination> <provider-name> local </provider-name> <destination-name> localdms:/local/Reporting/LogRotation </destination-name> <destination-type> Queue </destination-type> </output-destination> </output-port> </message-source>
The message sink for the localdms:/local/Reporting/LogRotation queue has the following configuration:
<message-sink> <nucleus-name> /atg/reporting/datawarehouse/loaders/LogRotationSink </nucleus-name> <input-port> <port-name> DEFAULT </port-name> <input-destination> <provider-name> local </provider-name> <destination-name> localdms:/local/Reporting/LogRotation </destination-name> <destination-type> Queue </destination-type> </input-destination> </input-port> </message-sink>
The table that follows lists the logRotationMessageType for each logging component:
Logging Component | Message Type |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
