Oracle GlassFish Server Message Queue Administration Guide Release 4.5.2 Part Number E24943-01 |
|
|
View PDF |
Message Queue data is stored in different locations based on the distribution used to install Message Queue. The tables that follow show the location of various types of Message Queue data for the following types of installations:
Installations of Previous Message Queue Versions from Solaris SVR4 Packages
Installations of Previous Message Queue Versions from Linux RPMs
In the tables, instanceName denotes the name of the broker instance with which the data is associated.
Table A-1 shows the location of Message Queue data when Message Queue is installed from an IPS image, such as when the Message Queue installer is used. Locations denote the IMQ_HOME
and IMQ_VARHOME
directory variables defined in Directory Variable Conventions.
Table A-1 Message Queue Data Locations for Installations from an IPS Image
Data Category | Location |
---|---|
Command line executable files |
|
Broker instance configuration properties |
|
Broker configuration file templates |
|
Persistent data store (messages, destinations, durable subscriptions, transactions, acknowledgements) |
|
Broker instance log file directory (default location) |
|
Administered objects (object store) |
Local directory of your choice or an LDAP server |
Security: user repository |
|
Security: access control file (default location) |
|
Security: password file directory (default location) |
|
Security: example password file |
|
Security: broker's key store file location |
|
JavaDoc API documentation |
|
Example applications and configurations |
|
Java archive ( |
|
External resource ( |
|
JMS Bridge DTD file |
|
Note:
Message Queue is no longer distributed as Solaris SVR4 packages. The following information is provided as a point of reference when upgrading from previous versions of Message Queue that were distributed as Solaris SVR4 packages.
Table A-2 shows the location of Message Queue data when Message Queue was installed from Solaris SVR4 packages.
Table A-2 Message Queue Data Locations for Installations from Solaris SVR4 Packages
Data Category | Location |
---|---|
Command line executable files |
|
Broker instance configuration properties |
|
Broker configuration file templates |
|
Persistent data store (messages, destinations, durable subscriptions, transactions, acknowledgements) |
|
Broker instance log file directory (default location) |
|
Administered objects (object store) |
Local directory of your choice or an LDAP server |
Security: user repository |
|
Security: access control file (default location) |
|
Security: password file directory (default location) |
|
Security: example password file |
|
Security: broker's key store file location |
|
JavaDoc API documentation |
|
Example applications and configurations |
|
Java archive ( |
|
External resource ( |
|
JMS Bridge DTD file |
|
Note:
Message Queue is no longer distributed as Linux RPMs. The following information is provided as a point of reference when upgrading from previous versions of Message Queue that were distributed as Linux RPMs.
Table A-3 shows the location of Message Queue data when Message Queue was installed from Linux RPMs.
Table A-3 Message Queue Data Locations for Installations from Linux RPMs
Data Category | Location |
---|---|
Command line executable files |
|
Broker instance configuration properties |
|
Broker configuration file templates |
|
Persistent data store (messages, destinations, durable subscriptions, transactions, acknowledgements) |
|
Broker instance log file directory (default location) |
|
Administered objects (object store) |
Local directory of your choice or an LDAP server |
Security: user repository |
|
Security: access control file (default location) |
|
Security: password file directory (default location) |
|
Security: example password file |
|
Security: broker's key store file location |
|
JavaDoc API documentation |
|
Example applications and configurations |
|
Java archive ( |
|
External resource ( |
|
Shared library ( |
|
JMS Bridge DTD file |
/opt/sun/mq/share/lib/dtd |