test

Sun Java Enterprise System 5 Update 1 Upgrade Guide for Microsoft Windows

Overview of Message Queue Upgrades

This section describes the following general aspects of Message Queue that impact upgrading to Java ES 5 Update 1 :

About Java ES 5 Update 1 Message Queue

Release 5U1 Message Queue is a maintenance release that fixes bugs in Release 5 Message Queue. Release 5 Message Queue was a feature release that represented a minor upgrade with respect to Release 4.

Message Queue software has historically included two editions, a Platform Edition and an Enterprise Edition, each corresponding to a different feature set and licensed capacity. Enterprise Edition was for deploying and running messaging applications in an enterprise production environment. Platform Edition was mainly for developing, and debugging messaging applications and components. With Release 5 Message Queue, the Platform Edition was deprecated and Message Queue includes all Enterprise Edition features. An upgrade from an earlier Java ES version to Java ES 5 converts any installed Platform Edition to full Message Queue enterprise-level features.

Message Queue Upgrade Roadmap

The following table shows the supported Message Queue upgrade paths to Release 5U1.

Table 8–1 Upgrade Paths to Java ES Update 1Message Queue 3.7 UR2

Java ES Release 

Message Queue Release 

General Approach 

Reconfiguration Required  

Release 5 

Sun Java System Message Queue 3.7 UR1 

Maintenance Upgrade. Apply patches. 

None 

Message Queue Data

Message Queue, like other Java ES components, makes use of various kinds of data that for any specific upgrade might need to be migrated to an upgraded version. Table 8–2 shows the type of data that could be impacted by an upgrade of Message Queue software.

In the table, Instance-Name identifies the name of the Message Queue broker instance with which the data is associated and MessageQueue-base is the installation directory for Message Queue.

For Java ES 5 Update 1, C:\Program Files\Sun\JavaES5\mq is the default installation location for Message Queue . For Java ES 4, C:\Sun\MessageQueue is the default installation location.

Table 8–2 Message Queue Data Usage

Data Category  

Location  

Usage  

Broker instance configuration properties 

MessageQueue-base\var\instances\Instance-Name\config.properties

Broker and related services configurations 

Persistent store for dynamic application data 

Release 4: 

MessageQueue-base\var\instances\Instance-Name\fs350

Release 5: 

MessageQueue-base\var\instances\Instance-Name\fs370

or accessible through the Java Database Connectivity (JDBCTM) API

Stores messages, destinations, durable subscriptions, transactions, and other dynamic data 

Administered objects (object store) 

Local directory of your choice or an LDAP Directory Server 

Objects used to configure client/broker connections 

Security: user repository 

MessageQueue-base\var\instances\Instance-Name\etc\passwd

Stores user data used for authentication and authorization 

Security: access control file (default location) 

MessageQueue-base\var\instances\Instance-Name\etc\accesscontrol.properties

Sets the rules that authorize user access to destinations and related capabilities 

Security: passfile directory (default location) 

MessageQueue-base\var\instances\Instance-Name\etc\

Stores encrypted password information. 

Security: broker’s keystore file location 

MessageQueue-base\etc

Stores encrypted certificate information for secure messaging. 

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: