Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for WebSphere Message Broker Guide Oracle Solaris Cluster |
1. Installing and Configuring HA for WebSphere Message Broker
A. Deployment Example: Installing WebSphere Message Broker in Zones
Installing and Configuring WebSphere Message Broker
Example: Prepare the Cluster for WebSphere Message Broker
Example: Configure zones z1 and z2 for WebSphere Message Broker
Example: Verify WebSphere Message Broker
Example: Configure Cluster Resources for WebSphere Message Broker
Example: Enable the WebSphere Message Broker Software to Run in the Cluster
Example: Verify the HA for WebSphere Message Broker Resource Group
Caution - The steps within this procedure are not precise steps to install WebSphere Message Broker or DB2. Refer to the relevant IBM documentation for complete information. |
Perform this step in the global zone only.
In this example, the WebSphere Message Broker software and DB2 software has been copied to node Vigor5 in directories /export/software/ibm/wmbv6 and /export/software/ibm/db2v8.
Vigor5# zlogin z1 mkdir -p /var/tmp/software Vigor5# zlogin z2 mkdir -p /var/tmp/software Vigor5# mount -F lofs /export/software /zones/z1/root/var/tmp/software Vigor5# mount -F lofs /export/software /zones/z2/root/var/tmp/software
Perform this step from the global zone for zone z1.
Vigor5# zlogin z1 # cat > /var/tmp/db2_response <<-EOF PROD = ENTERPRISE_SERVER_EDITION INSTALL_TYPE = TYPICAL LIC_AGREEMENT = ACCEPT EOF # cd /var/tmp/software/ibm/db2v8 # ./db2setup -r /var/tmp/db2_response
Comment out chk_kernel_conf in /opt/IBM/db2/V8.1/instance/db2iutil as indicated by ->.
# Check that kernel parameters are updated -> # chk_kernel_conf # Set the value of vars INSTHOME and INSTPGRP # and check their validity
# vi /opt/IBM/db2/V8.1/instance/db2iutil # exit
Perform this step from the global zone for zone z1 which can be performed at the same time you are installing the DB2 software.
Vigor5# zlogin z1 # cat > /var/tmp/install.opt <<-EOF -W setupTypes.selectedSetupTypeId=typical -P installLocation=/opt/IBM/mqsi/6.0 -P brokerFeature.active=true -P transformationServicesFeature.active=true -p unsFeature.active=true -P configManagerFeature.active=true EOF # cd /var/tmp/software/ibm/wmbv6/messagebroker_runtime1 # ./setupsolarisx86 -options /var/tmp/install.opt -silent # exit
Perform this step in the global zone.
Vigor5# zpool export -f HAZpool3 Vigor5# zpool import -R /zones/z2/root HAZpool3
Perform this step from the global zone for zone z2.
Vigor5# zlogin z2 # cat > /var/tmp/db2_response <<-EOF PROD = ENTERPRISE_SERVER_EDITION INSTALL_TYPE = TYPICAL LIC_AGREEMENT = ACCEPT EOF # cd /var/tmp/software/ibm/db2v8 # ./db2setup -r /var/tmp/db2_response
Comment out chk_kernel_conf in /opt/IBM/db2/V8.1/instance/db2iutil as indicated by ->.
# Check that kernel parameters are updated -> # chk_kernel_conf # Set the value of vars INSTHOME and INSTPGRP # and check their validity
# vi /opt/IBM/db2/V8.1/instance/db2iutil # exit
Perform this step from the global zone for zone z2 which can be performed at the same time you are installing the DB2 software.
Vigor5# zlogin z2 # cat > /var/tmp/install.opt <<-EOF -W setupTypes.selectedSetupTypeId=typical -P installLocation=/opt/IBM/mqsi/6.0 -P brokerFeature.active=true -P transformationServicesFeature.active=true -p unsFeature.active=true -P configManagerFeature.active=true EOF # cd /var/tmp/software/ibm/wmbv6/messagebroker_runtime1 # ./setupsolarisx86 -options /var/tmp/install.opt -silent # exit
Perform this step in the global zone.
Vigor5# zpool export -f HAZpool3 Vigor5# zpool import -R /zones/z1/root HAZpool3