Installation on Windows

This section describes the steps for a fresh installation of IVIG Software Stack version 11.0.0 on Microsoft Windows.

Stand-alone deployment

Perform the following steps to install IVIG-Software Stack on Microsoft Windows Server 2022, as a stand-alone setup.

IBM Java 8 SDK
  1. Download IBM Java 8 SDK.

    You can download the IBM Java 8 SDK from this page.

  2. After downloading the package, unzip it to your local Windows computer. Next, you must add this PATH to the system PATH environment variable.

    For example, if you had unzipped the IBM Java 8 SDK to C:\Users\me\java then you must add the system PATH environment variable. Open the System Properties dialog, and go to Advanced tab. Click the Environment Variables button. In the System Variables section, edit the PATH entry as shown here: set PATH=C:\Users\me\java\sdk\jre\bin;%PATH%

IBM MQ

Download IBM MQ from IBM Passport Advantage

MQ 9.4 LTS is under part number G0B7VML.

Next, install IBM MQ.

  • Unzip the IBM MQ package.
  • Right click on MQServer/Setup.exe and select Run as Administrator
  • Choose Typical option. When done, make sure to choose to let it run Prepare IBM MQ Wizard to create the Account and Group for the Service.

For detailed instructions, see the IBM MQ documentation

Configure IBM MQ
  1. Create new Windows user isimsystem.
    Note: For the next set of steps, be sure to use a user in the mqm or Administrators group. And if the user is not in mqm group, then run the command prompt as Administrator. Also, the isimsystem user must NOT be in the mqm group
  2. Download the IVIG - Software Stack files from IBM Passport Advantage site.
  3. Extract the IVIG- Software Stack package into its own directory (for example <extracted_directory>).
  4. Using command-prompt, navigate to this folder: <extracted_directory>\wlp\usr\servers\defaultServer\config\config\mq and then choose either SSL or plain (non-SSL) option.
  5. Run this command: crtmqm -ii isvgqm.ini ISVGQueueMgr
  6. Run this command: strmqm ISVGQueueMgr
  7. Run this command: runmqsc ISVGQueueMgr < ISVGQMgr.mqsc

    This sets up the shared queues. It can be done on the IM system, or you can install MQ on another machine and run it there.

  8. Run this command: crtmqm -ii isvgqm.ini ISVGQMgrShared
  9. Run this command: strmqm ISVGQMgrShared
  10. Run this command: runmqsc ISVGQMgrShared < ISVGQMgr-shared.mqsc
Using SSL for MQ

Perform the steps in this section only if you are using SSL option for IBM MQ.

  1. Run this command: runmqakm -keydb -create -populate -db C:\ProgramData\IBM\MQ\qmgrs\ISVGQueueMgr\ssl\key.kdb -pw the_password -stash
  2. Run this command: runmqakm -cert -create -db C:\ProgramData\IBM\MQ\qmgrs\ISVGQueueMgr\ssl\key.kdb -stashed -label ibmwebspheremqisvgqueuemgr -dn "CN=ISVGIM" -san_dnsname your_hostname -san_ipaddr your_ip
  3. Alternatively, if you have a PKCS12 file, run this command: runmqakm -cert -import -db C:\ProgramData\IBM\MQ\qmgrs\ISVGQueueMgr\ssl\key.kdb -stashed -label pkcs12label -new_label ibmwebspheremqisvgqueuemgr -target cert.p12 -target_pw pkcs_password -type kdb -target_type pkcs12
  4. If you created your cert now, extract the CA with: runmqakm -cert -extract -label ibmwebspheremqisvgqueuemgr -db C:\ProgramData\IBM\MQ\qmgrs\ISVGQueueMgr\ssl\key.kdb -stashed -file localCA.crt -format ascii

    NOTE: The label for the shared QM MUST be ibmwebspheremqisvgqmgrshared, and use a different file name

  5. Use mqcertck Queue_Manager_Name
    Note: This is an important step that verifies that the updates have been made correctly. For accurate results, this must be run as the used specified in the LogOn tab of the MQ service, since that is the userid that will be attempting to access the keystores.
  6. Run this command: endmqm ISVGQueueMgr
  7. Run this command: strmqm ISVGQueueMgr
  8. You must restart to enable SSL.
  9. Similarly, perform the above steps (1 to 7) for ISVGQMgrShared QM
Important: After the MQ certificates are created, ensure that the C:\ProgramData\IBM\mq\qmgrs\<queueMgrName>\ssl\key.kdb and key.sth files are readable by the mqm group. To verify this, perform these steps: Using the File Explorer, go to key.kdb and key.sth file. Right-click the file, and go to Properties → Security tab. If the mqm group is not listed, you must add it with default permissions 'Read' and 'Read & execute'. Save your changes and close all the dialog boxes.
Deploy IVIG - Software Stack
  1. Go to the IVIG- Software Stack package that you had extracted into its own directory (for example <extracted_directory>).
  2. Run this command: cd <extracted_directory>\wlp\bin
  3. Run this command: im_installer.bat configure --configfile \path\to\configfile

    The im_installer.bat script, when run in the configure mode, prompts for various inputs (such as LDAP, DB2, IBM connection parameters) and stores them in the configuration file created in the specified folder on the local computer. If the same file already exists in the specified folder, then it will be updated.

    In this command, replace \path\to\configfile with the complete folder path including the file name. For example: im_installer.bat configure --configfile \home\imssliberty\ivig11_config.properties

  4. Run this command: im_installer.bat install --configfile \path\to\configfile

    Here, the im_installer.bat script, when run in the install mode, uses the parameters from the configuration file created in the previous step. In this command, replace \path\to\configfile with the same folder path and the file name that was created in the previous step. For example: im_installer.bat install --configfile \home\imssliberty\ivig11_config.properties

  5. If you want the IVIG 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.
  6. Run this command: <wlp>\bin\server start
  7. Log in to IVIG Server:
    • If using SSL: https://<hostname>:9443/itim/console
    • If using non-SSL: http://<hostname>:9080/itim/console
  8. The screen prompts you to change the default password. Set a password of your choice, and then proceed with logging in to the IVIG application.

Multi-node deployment

If you want to deploy IVIG v11.0.0 Software Stack in a multi-node Microsoft Windows environment, create the first node (for example, Node-1) by performing the steps described in the Stand-alone 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 v11.0.0 Software Stack files.
  4. Extract the downloaded IVIG Software Stack package into its own folder in Node-2.
  5. On Node-2, configure the local MQ queue manager, by performing steps 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: im_installer.bat addnode --configfile \path\to\configfile
  7. The script prompts you to provide the hostname for Node-2 and other required details for the MQ local. Provide the required values.
  8. The script then adds the required files to \path\to\configfile.zip
  9. 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.
  10. On Node-2, go to the wlp\bin directory and run the following command: im_installer.bat install --configfile \path\to\configfile
  11. On Node-2, navigate to <IVIG Home>\wlp\usr\servers\defaultServer folder.
  12. Open the bootstrap.properties file.
    In the following two parameter values, change any "\" characters to "/".
    • liberty.keystore.location
    • liberty.truststore.location

    For example: If the bootstrap.properties file has:

    liberty.keystore.location=C:\Users\imsslib\IVIG\wlp\usr\servers\defaultServer\resources\security\isvgimKeystore.jksliberty.truststore.location=C:\Users\imsslib\IVIG\wlp\usr\servers\defaultServer\resources\security\isvgimTruststore.jks

    Update it to:

    liberty.keystore.location=C:/Users/imsslib/IVIG/wlp/usr/servers/defaultServer/resources/security/isvgimKeystore.jksliberty.truststore.location=C:/Users/imsslib/IVIG/wlp/usr/servers/defaultServer/resources/security/isvgimTruststore.jks

  13. From the wlp\bin directory, run the following command: <wlp>\bin\server start
  14. Log in:
    • If using SSL: https://<hostname>:9443/itim/console
    • If using non-SSL: http://<hostname>:9080/itim/console