IBM MQ and IIB HA Architectures Using GCP | IBM
IBM Blog

IBM MQ and IIB HA Architectures Using GCP

Target audience: Mid to Highly skilled Linux, MQ/IIB and GCP admins.

IBM MQ and IIB have 2 distinct HA Architectures. MQ and IIB can be configured to have an Active Standby(2 live server) or an Active Passive(1 live server) HA configuration. Both MQ/IIB HA designs are publish documents. This article focuses on using just the IBM software and GCP components.

Since GCP only supports NFS v4 with a separate file server instance this article focuses on the active pass MQ/IIB HA configuration.

Again, these are high-level design and the details will need to be worked out with a specific client. Internet domains, SSL/TLS and certs are not cover, these items will also need to be incorporated to the client’s specifications.

Create the MQ/IIB environment on GCP – Active Passive:

Other references for this design are listed below. Again, this article focuses on using just the IBM software and the tools available in GCP.

  • Create a VPC for MQ/IIB that has a default network. Update Firewall rules as needed. These GCP components will be created and configure to a client’s specifications. The firewall rule should include MQ/IIB ports and should limit who can get to the MQ/IIB from the internet.
  • Create an instance of one of the GCP public images that meets the client’s virtual machine specification. Make sure that delete boot drive is unchecked.
  • Create cloud storage shares for MQ and IIB.
  • Mount the shares using FUSE.
  • Put the remount commands in /etc/fstab
  • Upload the MQ/IIB software to the instance.
  • Install MQ and IIB.
  • Now create a QMgr configuration on the VM instance. Follow the IBM info center for these steps.
  • Now create an IIB configuration on the VM instance. Follow the IBM info center for these steps. Now write a script.
    1. The script will execute at bootup. Call it ESB_startup.
    2. It will start the QMgr and Brkr.
    3. Put ESB_startup script in /etc/init.d
    4. chmod 755 /etc/init.d/ESB_startup
    5. chkconfig –add ESB_startup
    6. chkconfig ESB_startup on
    7. Check it: chkconfig –list ESB_startup
  • Now stop the instance.
  • Now reboot the Instance to see your script work. If both QMgr and Brkr startup, then continue. Otherwise go back and debug your script.
  • Now delete the current instance.
  • Now create and image from the boot disk of the instance.
  • Now create a template and use the image you just created.
  • Now create an instance group from the template. The auto scaling group will be a scaling group of 1. Setup a health check for port 1414. Default MQ port.
  • Now create a load balancer and use the instance group.
  • Test your configuration by shutting down the Qmgr. You should see the Auto Scaling destroy the current instance and spin up a new instance of the Qmgr and Brkr.

References:

https://www.ibm.com/developerworks/community/blogs/messaging/entry/mq_openstack_part1_packer?lang=en

https://www.ibm.com/developerworks/community/blogs/messaging/entry/mq_openstack_part2_heat?lang=en

Subscribe to the IBM Weekly Digest

* indicates required

Technical Architect

Leave a Reply

Perficient IBM Blog

Trends, best practices, and technical perspectives from IBM experts and thought leaders. Gain valuable insights to enable digital transformation through analytics, cloud, commerce, digital experience, and middleware solutions.

Archives