Messages are received by subscribers . Regardless of messaging style, the link between applications and the JMS provider is the connection object. Applications get their connection objects from the Connection Factories. In order to maximize portability of an application between JMS providers, provider specific messaging aspects are encapsulated in administered objects. Administration tools are used to create and configure administered object class instances, and to configure them to the deployment requirements.
Administrators use the tools to set provider specific parameters.
This programming model allows JMS programs to be written that are completely provider independent. Applications should reference objects in the JMS subcontext directly, since the iPlanet Application Server deployment manager does not support JMS resource references. The iPlanet Application Server includes the software to integrate JMS providers, but it must be enabled. This section describes how to integrate a JMS provider with the iPlanet Application Server, and to enable the JMS connection pooling and user identity mapping features. See the vendor's installation instructions.