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. |