Create a cluster configuration file specifying the cluster’s high-availability-related configuration properties.
Enhanced Broker Cluster Properties shows the required property values. However, do not include the imq.brokerid property in the cluster configuration file; this must be specified separately for each individual broker in the cluster.
Specify any additional, vendor-specific JDBC configuration properties that might be needed.
For each broker in the cluster:
Start the broker at least once, using the imqbrokerd command.
The first time a broker instance is run, an instance configuration file (config.properties) is automatically created.
Shut down the broker.
Use the imqcmd shutdown bkr command.
Edit the instance configuration file to specify the location of the cluster configuration file.
In the broker’s instance configuration file, set the imq.cluster.url property to point to the location of the cluster configuration file you created in step 1.
Specify the broker identifier.
Set the imq.brokerid property in the instance configuration file to the broker’s unique broker identifier. This value must be different for each broker.
Place a copy of, or a symbolic link to, your JDBC driver’s .jar file in the Message Queue external resource files directory , depending on how Message Queue was installed (see Appendix A, Distribution-Specific Locations of Message Queue Data):
IPS packages: IMQ_HOME/lib/ext
Solaris SVR4 packages: /usr/share/lib/imq/ext
Linux RPM packages: /opt/sun/mq/share/lib/ext
Create the database schema needed for Message Queue persistence.
Use the imqdbmgr create tbl command; see Database Manager Utility.
Restart each broker with the imqbrokerd command.
The brokers will automatically register themselves into the cluster on startup.