Sun Java System Message Queue 4.3 Administration Guide

Solaris OS

Table A–1 shows the location of Message Queue data on the Solaris operating system. If you are using Message Queue on Solaris with the standalone version of Sun Java System Application Server, the directory structure is like that described under Windows.

Table A–1 Message Queue Data Locations on Solaris Platform

Data Category 

Location 

Command line executable files

/usr/bin

Broker instance configuration properties

/var/imq/instances/instanceName/props/config.properties

Broker configuration file templates

/usr/share/lib/imq/props/broker/

Persistent data store (messages, destinations, durable subscriptions, transactions, acknowledgements)

/var/imq/instances/instanceName/fs370or a JDBC-accessible data store

Broker instance log file directory (default location)

/var/imq/instances/instanceName/log/

Administered objects (object store)

Local directory of your choice or an LDAP server

Security: user repository

/var/imq/instances/instanceName/etc/passwdor an LDAP server

Security: access control file (default location)

/var/imq/instances/instanceName/etc/accesscontrol.properties

Security: password file directory (default location)

/var/imq/instances/instanceName/etc/

Security: example password file

/etc/imq/passfile.sample

Security: broker’s key store file location 

/etc/imq/

JavaDoc API documentation

/usr/share/javadoc/imq/index.html

Example applications and configurations

/usr/demo/imq/

Java archive (.jar), Web archive (.war), and Resource Adapter archive (.rar) files

/usr/share/lib/imq

External resource (.jar) files such as JDBC drivers, JAAS login modules, and so forth

/usr/share/lib/imq/ext