Installation on RHEL

This section describes the steps for a fresh installation of IVIG Software Stack version 11.0.0 on Red Hat Enterprise Linux.

Overview

Perform the following steps to install IM-Software Stack Beta-5 release on Red Hat Enterprise Linux v9.4.

Stand-alone deployment

IBM Java 8 SDK
  1. Download IBM Java 8 SDK.
  2. Install Java 8. Run: sudo rpm -Uvh ibm-java-x86_64-sdk-8.0-8.30.x86_64.rpm
  3. Add /opt/ibm/java-x86_64-80 to your PATH
IBM MQ

Download IBM MQ from IBM Passport Advantage .

IBM MQ 9.4 LTS is available with part number G0B7VML.

Next, install IBM MQ.

  1. Ensure that you have root or sudo access on the system.
  2. Run: tar zxf 9.4.0.0-IBM-MQ-LinuxX64.tar.gz
  3. Run: sudo groupadd -g 500 mqm
  4. Run: sudo useradd -u 501 -g mqm -s /bin/bash -d /home/mqm -m mqm
  5. NOTE: You may ignore the warning about uid range.
  6. Run: sudo passwd mqm
  7. Run: sudo useradd -s /bin/bash -d /home/isimsystem -m isimsystem
  8. Run: sudo passwd isimsystem
  9. Next, edit the file /etc/security/limits.conf to add the following to the end of the file, above the # End of File line.
  10. root hard nofile 10240
  11. root soft nofile 10240
  12. mqm hard nofile 10240
  13. mqm soft nofile 10240
  14. Edit the file /etc/sysctl.conf to add or change the following entries.
  15. fs.file-max = 524288
  16. kernel.threads-max = 32768
  17. Run: sudo sysctl -p
  18. This command ensures that changes are enforced without having to reboot the computer.
  19. Create the mqm data directory.
  20. sudo mkdir /var/mqm
  21. sudo chown mqm /var/mqm
  22. sudo chgrp mqm /var/mqm
  23. Run: sudo ./mqlicense.sh
  24. Run: sudo rpm -Uvh MQ*.rpm

For detailed instructions, see the IBM MQ documentation.

Configure IBM MQ
  • Ensure to use a user in the mqm group. You can also add your account to the group.
  • sudo usermod -g mqm <yourid>
  • newgrp (to reload groups without having to log in again)
  • Run: . /opt/mqm/bin/setmqenv -s
  • NOTE: Do not forget the <period><space> at the front to source this info into your environment.
  • Run: cd into wlp/usr/servers/defaultServer/config/config/mq/ and then either ssl OR plain
  • Here, choose ssl directory if you want to use SSL, and choose plain for non-SSL.
  • Check the listener line at the end of the .mqsc files. The local is configured for port 1414 and shared for 1415, but they can be adjusted as needed.
  • Run: crtmqm -ii isvgqm.ini ISVGQueueMgr
  • Run: strmqm ISVGQueueMgr
  • Run: runmqsc ISVGQueueMgr < ISVGQMgr.mqsc
  • Next, you need to set up the shared queues. It can be done on the IM system, or you can install MQ on another machine and run it there.
    • Run: crtmqm -ii isvgqm.ini ISVGQMgrShared
    • Run: strmqm ISVGQMgrShared
    • Run: runmqsc ISVGQMgrShared < ISVGQMgr-shared.mqsc

SSL: If you plan to use SSL, you will need to create a certificate for each queue manager. You can either use openssl to create a PKCS12 file to be imported into the MQ keystore, or you can create one with GSKit.

  1. Refer the MQ Documentation.
  2. Run as the mqm user or you will need to update permissions on the file.
  3. Run: runmqakm -keydb -create -populate -db /var/mqm/qmgrs/ISVGQueueMgr/ssl/key.kdb -pw the_password -stash
  4. If you have a PKCS12:
  5. Run: runmqakm -cert -import -db /var/mqm/qmgrs/ISVGQueueMgr/ssl/key.kdb -stashed -label pkcs12label -new_label ibmwebspheremqisvgqueuemgr -target cert.p12 -target_pw pkcs_password -type kdb -target_type pkcs12
  6. If you do not have PKCS12:
  7. Run: runmqakm -cert -create -db /var/mqm/qmgrs/ISVGQueueMgr/ssl/key.kdb -stashed -label ibmwebspheremqisvgqueuemgr -dn "CN=ISVGIM" -san_dnsname your_hostname -san_ipaddr your_ip
  8. If you have created a new certificate, extract the CA with:
  9. Run: runmqakm -cert -extract -label ibmwebspheremqisvgqueuemgr -db /var/mqm/qmgrs/ISVGQueueMgr/ssl/key.kdb -stashed -file localCA.crt -format ascii
  10. NOTE: The label for the shared QM MUST be ibmwebspheremqisvgqmgrshared, and use a different file name.
  11. Use mqcertck Queue_Manager_Name
  12. This step is important to ensure that all the updates are correct.
  13. Run: endmqm ISVGQueueMgr
  14. Run: strmqm ISVGQueueMgr
  15. You must restart to enable SSL.
  16. Next, perform the steps 3 to 9 for the ISVGQMgrShared QM.
IVIG Software Stack
From IBM Passport Advantage site, download the IVIG Software Stack files. Extract the files on your local computer. Next, perform the following steps.
  1. Run: cd wlp/bin
  2. Run: ./im_installer.sh configure --configfile /path/to/file
  3. Run: ./im_installer.sh install --configfile /path/to/file
  4. If you want the IM server to use SSL, add your certificate and private key to the keystore listed as liberty.keystore.location in bootstrap.properties file. If not using SSL, then you can use port 9080 instead of 9443.
  5. Run: <wlp>/bin/server start
  6. Log in to IM application:
  7. If using SSL: https://<hostname>:9443/itim/console
    • If using non-SSL: http://<hostname>:9080/itim/console
    • The screen prompts you to change the default password. Set a password of your choice, and then proceed with logging in to the IM application.

Multi-node deployment

If you want to deploy IM-Software Stack in a multi-node environment, create the first node (for example, Node-1) by performing the steps described in the Standalone Deployment section.

Next, we will configure a new node (for example, Node-2). Perform the following steps:

  1. On Node-2, install IBM Java.
  2. On Node-2, install IBM MQ.
  3. From IBM Passport Advantage site, download the IVIG Software Stack files.
  4. Extract the downloaded IVIG Software Stack package into its own directory in Node-2.
  5. On Node-2, configure the local MQ queue manager, by performing steps 1 to 7 from Configure IBM MQ section. Also, if you plan to use SSL, perform the SSL-related steps from the same section.
  6. On the existing Node-1, go to the wlp/bin directory and run the following command:
  7. im_installer.sh addnode --configfile /path/to/configfile
  8. The script prompts you to provide the hostname for Node-2 and other required details for the MQ local. Provide the required values.
  9. The script then adds the required files to /path/to/configfile.zip
  10. Transfer the two files (configfile and configfile.zip) from the existing Node-1 to the new node, Node-2. Ensure that both the files are placed in the same directory on Node-2.
  11. On Node-2, go to the wlp/bin directory and run the following command:
  12. im_installer.sh install --configfile /path/to/configfile
  13. From the wlp/bin directory, run the following command:
  14. <wlp>/bin/server start
  15. Log in:
    • If using SSL: https://<hostname>:9443/itim/console
    • If using non-SSL: http://<hostname>:9080/itim/console