Messages are sent by publishing to a Topic. Regardless of messaging style, the link between applications and the JMS provider is the connection object. Applications get their connection objects from Connection Factories. In order maximize portability of applications between JMS providers, provider specific aspects of messaging are encapsulated in administered objects. Administration tools are used to create and configure instances of the administered object classes, and to configure them to the requirements of the deployment.
Administrators use the tools to set provider specific parameters.
This programming model allows JMS programs to be written that are completely independent of the provider. Applications should reference objects in the JMS subcontext directly, since the iAS deployment manager does not support iAS JMS beta JMS resource references. Enabling JMS and Integrating Providers IAS6.0 includes the software required to integrate JMS providers, but it must be enabled. This section describes how to integrate a JMS provider with iAS, and to enable the JMS connection pooling and user identity mapping features. Enable the object pooling infrastructure in the iAS runtime Adapt the JMS administration programs to the iAS installation location The JMS provider software should have been installed previously.