Example: Install WebSphere Message Broker in the zones

---

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.

---

1. Mount the WebSphere Message Broker software in the zones.

   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

2. Install the DB2 software in zone z1.

   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

3. Install the WebSphere Message Broker software in zone z1.

   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

4. Relocate the ZFS pool to zone z2.

   Perform this step in the global zone.

   Vigor5# zpool export -f HAZpool3
   Vigor5# zpool import -R /zones/z2/root HAZpool3

5. Install the DB2 software in zone z2.

   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

6. Install the WebSphere Message Broker software in zone z2.

   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

7. Relocate the ZFS pool back to zone z1.

   Perform this step in the global zone.

   Vigor5# zpool export -f HAZpool3
   Vigor5# zpool import -R /zones/z1/root HAZpool3