By default, Patch Bay is configured to use SQL JMS as its default JMS provider. This ensures that the ATG products and demos work without any further configuration.
You can use SQL JMS as your JMS provider for your own applications. However, if you are running the ATG platform on IBM WebSphere Application Server or BEA WebLogic Server, you may prefer to use your application server’s JMS provider. Or you may want to develop your applications using SQL JMS, and switch over to the application server’s provider on your production systems.
To facilitate this switch, the ATG platform provides components of class atg.dms.patchbay.JMSProviderConfiguration that are preconfigured for the WebSphere and WebLogic JMS providers. By default these components are disabled, but you can enable the component for your application server by running the ATG platform with the WebLogic.JMSProvider or WebSphere.JMSProvider application module, as described below.
Note that when you switch over to your application server’s JMS provider, you should also reconfigure ATG to use your application server’s data sources and transaction manager. For information about how to do this, see the ATG Installation and Configuration Guide.
IBM WebSphere Application Server
When you start up an application that includes the WebSphere.JMSProvider module, the JMSProviderConfiguration component /atg/dynamo/messaging/WebSphereJMSProvider is enabled and is set to the default provider for Patch Bay. This means that Patch Bay will now map each destination name declared using the patchbay:/ prefix to the corresponding name used by WebSphere’s Embedded MQ JMS provider, as described in Specifying Destinations for the Default Provider.
By default, the WebSphereJMSProvider component is configured to use the following WebSphere connection factories:
topicConnectionFactoryName=WAS.XA.TCF
queueConnectionFactoryName=WAS.XA.QCF
You can change these values if you are using different connection factories. You should not need to modify any other properties of this component.
The ATG installation includes a jacl script named createATGTopicsAndQueues.jacl for creating the destinations used by the ATG platform. The script is located in <ATG2007.3dir>/DAF/wsbin. See the notes in the script file for information about how to run it.
The script creates only the standard Patch Bay destinations. If your application defines additional topics and queues to be used by Patch Bay, you must create them manually in Embedded MQ.
Running the WebSphere.JMSProvider module enables several additional components used by Patch Bay, including the WebSphereJMSInitialContextFactory component, which resolves the JNDI names of connection factories and destinations, and the WebSphereNameTranslator component, which performs the mapping of destination names in Patch Bay to their WebSphere names.
For more information about WebSphere Embedded MQ, see the WebSphere documentation.
BEA WebLogic Server
When you start up an application that includes the WebLogic.JMSProvider module, the JMSProviderConfiguration component /atg/dynamo/messaging/WeblogicJMSProvider is enabled and is set to the default provider for Patch Bay. This means that Patch Bay will now map each destination name declared using the patchbay:/ prefix to the corresponding name used by WebLogic’s JMS provider, as described in Specifying Destinations for the Default Provider. You can modify the properties of the WeblogicJMSProvider component to change aspects of the configuration, such as the connection factory classes.
In addition to configuring the provider component, Patch Bay attempts to use WebLogic’s API for dynamically creating destinations to create the topics and queues used by the ATG platform. To use this API, Patch Bay assumes that WebLogic is running in the WebLogic Server Examples domain. If this is not the case, you can modify the following properties of the WeblogicJMSProvider component to reflect the actual WebLogic configuration:
JMSHelperClass- The name of the WebLogic class that provides methods for creating topics and queues (default:weblogic.jms.extensions.JMSHelper)JMSHelperCreateQueueMethod- The name of the method in the helper class used for creating queues (default:createPermanentQueueAsync)JMSHelperCreateTopicMethod- The name of the method in the helper class used for creating topics (default:createPermanentTopicAsync)JMSServerName- The WebLogic-specific name of the JMS server (default:examplesJMSServer)
If the destination creation fails, you can use the WebLogic Administration Console to create the topics and queues.
Running the WebLogic.JMSProvider module enables several additional components used by Patch Bay, including the WebLogicJMSInitialContextFactory component, which resolves the JNDI names of connection factories and destinations, and the WebLogicNameTranslator component, which performs the mapping of destination names in Patch Bay to their WebLogic names.
For more information about WebLogic’s JMS provider, see the WebLogic documentation.
