By default, Patch Bay is configured to use Local JMS and SQL JMS. These providers and the connection factories they use are specified through Nucleus components of class atg.dms.patchbay.JMSProviderConfiguration. For example, to configure SQL JMS, Oracle ATG Web Commerce includes a component of this class named /atg/dynamo/messaging/
. The properties file for this component includes these lines:


You generally should not need to modify any of these settings for Local JMS or SQL JMS. However, you can configure Patch Bay to work with additional JMS providers. See Using Patch Bay with Other JMS Providers for more information.

You can designate a JMS provider as the default provider in Patch Bay by setting the defaultJMSProvider property of the /atg/dynamo/messaging/MessagingManager component to point to the component that configures the provider. By default, this property points to the DynamoSQLJMSProvider component, which configures SQL JMS. Designating a provider as the default simplifies configuration of the destinations for that provider, and makes it easier to switch between providers. See Connecting to Destinations for more information.

You can also declare JMS providers at the top of the Patch Bay configuration file, using tags that correspond to the properties of JMSProviderConfiguration. Note, however, that a JMS provider declared this way cannot be designated as the default provider.

These tags are equivalent to the DynamoSQLJMSProvider properties shown above:

<!-- SQL JMS provider -->

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices