Oracle ATG Web Commerce includes a number of JMS-related tools, which are known collectively as the Dynamo Messaging System (DMS). The main parts of DMS are:
Two JMS providers, Local JMS and SQL JMS. Local JMS is built for high-speed low-latency synchronous messaging within a single process. SQL JMS is more robust, and uses an SQL database to handle communication between components within the same Oracle ATG Web Commerce application, or components running in different processes.
Patch Bay is an API and configuration system layered on top of JMS. Patch Bay is designed to ease the development of messaging applications in Oracle ATG Web Commerce. The Patch Bay API allows Nucleus components to send and receive messages. The configuration system uses an XML file to specify how these components should be connected. This file allows developers to change or add connections between components without changing code. Patch Bay also maintains a Message Registry that the Oracle ATG Web Commerce user interfaces use to present lists of possible notifications to users. Oracle ATG Web Commerce registers the messages that it sends with the Message Registry. Applications can also register their own messages, which then appear in the Oracle ATG Web Commerce user interfaces.
The different DMS pieces can be used independently. For example, you can use Local JMS, SQL JMS, or both, with or without Patch Bay. You can use a third-party JMS provider, or use the JMS implementation provided with your application server, also with or without Patch Bay. For more information about other JMS providers you can use, see the documentation for your application server.
