Message Queue Dependencies

Message Queue dependencies on other Java ES components can impact the procedure for upgrading and reconfiguring Message Queue software. Changes in Message Queue interfaces or functions, for example, could require upgraded version of components upon which Message Queue depends. The need to upgrade such components depends upon the specific upgrade path.

Message Queue has dependencies on the following Java ES components:

• Shared components. Message Queue has dependencies on specific Java ES shared components, as listed in Table 1–8.

• Directory Server (optional). If you want to configure Message Queue to store administered objects and/or user data in an LDAP directory rather than locally, you can use Directory Server for that purpose.

• Web Container (optional). If you need HTTP messaging between client and broker, then Message Queue requires web container support from Java ES Web Server or from Java ES Application Server.

• Databases (optional). You can configure Java DB or a third-party database as a data store for the Message Queue persistence layer.