Installing IIB 9.0 silently

  • To begin the installation silently, all we have to do is run the following script called installAllSilent.sh which is locate in the sample-scripts folder of the integrationbus_developer installation set (please use root for local learning, it is much easier, but you can use any account that has the correct elevated privileges).
  • Note: Before we run the script, we need to edit the response.properties file to ensure that the License is set to TRUE
###############################################################################

#

# IBM Integration Bus sample response file

#

# This file contains sample values for installing IBM Integration Bus.

#

###############################################################################

# Has the license been accepted?

#——————————-

LICENSE_ACCEPTED=TRUE

# Run the installer in silent mode

#———————————

INSTALLER_UI=silent

# Installation location

#———————-

USER_INSTALL_DIR=/opt/ibm/mqsi/9.0.0.2

# License location

#———————-

External_License_Path=

  • Locate the sample-scripts directory
[root@localhost integrationbus_developer]# cd sample-scripts/

[root@localhost sample-scripts]# ls -ltra

total 16

-rw-r–r–. 1 226 12201 616 Jul 11 2014 response.properties

-rwxr-xr-x. 1 226 12201 3515 Jul 11 2014 installAllSilent.sh

-rw-r–r–. 1 226 12201 504 Jul 11 2014 ibx-response.properties

  • When we run ./installAllSilent.sh, we see the following
[root@localhost sample-scripts]# ./installAllSilent.sh

You must accept the product licenses when running this script using the -ACCEPT_ALL_LICENSES option

A script to install IBM Integration Bus and pre-req components

options:

-ACCEPT_ALL_LICENSES

-WMQ_INSTALL_IMAGE <Directory of WMQ install image>

-IB_INSTALL_IMAGE <Directory of IBM Integration Bus install image>

-IX_INSTALL_IMAGE <Directory of IBM Integration Explorer install image>

-ITK_INSTALL_IMAGE <Directory of IBM Integration Toolkit install image>

 

Unfortunately, this means the entire set will be installed i.e. IB, IB Explorer, WMQ, IB Toolkit and we can presume default directories.

 

./installAllSilent.sh -ACCEPT_ALL_LICENSES -WMQ_INSTALL_IMAGE /var/apps/installs/integrationbus_developer/WebSphere_MQ -IB_INSTALL_IMAGE /var/apps/installs/integrationbus_developer -IX_INSTALL_IMAGE /var/apps/installs/integrationbus_developer/IBExplorer -ITK_INSTALL_IMAGE /var/apps/installs/Integration_Toolkit

The installer will start with installing WMQ silently, then IBM Integration Bus, then IBM Integration Explorer, then it will install IBM Integration Toolkit

Result:

Installing WMQ

Licensed Materials – Property of IBM

5724-H72

(C) Copyright IBM Corporation 1994, 2013 All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure

restricted by GSA ADP Schedule Contract with IBM Corp.

License has already been accepted: Proceed with install.

Preparing… ################################# [100%]

package MQSeriesRuntime-7.5.0-3.x86_64 is already installed

package MQSeriesJRE-7.5.0-3.x86_64 is already installed

package MQSeriesJava-7.5.0-3.x86_64 is already installed

package MQSeriesFTBase-7.5.0-3.x86_64 is already installed

package MQSeriesServer-7.5.0-3.x86_64 is already installed

package MQSeriesFTAgent-7.5.0-3.x86_64 is already installed

package MQSeriesFTService-7.5.0-3.x86_64 is already installed

package MQSeriesAMS-7.5.0-3.x86_64 is already installed

package MQSeriesFTLogger-7.5.0-3.x86_64 is already installed

package MQSeriesXRService-7.5.0-3.x86_64 is already installed

package MQSeriesFTTools-7.5.0-3.x86_64 is already installed

package MQSeriesExplorer-7.5.0-3.x86_64 is already installed

package MQSeriesGSKit-7.5.0-3.x86_64 is already installed

package MQSeriesClient-7.5.0-3.x86_64 is already installed

package MQSeriesMan-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_cs-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_de-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_es-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_fr-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_hu-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_it-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_ja-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_ko-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_pl-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_pt-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_ru-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_Zh_CN-7.5.0-3.x86_64 is already installed

package MQSeriesMsg_Zh_TW-7.5.0-3.x86_64 is already installed

package MQSeriesSamples-7.5.0-3.x86_64 is already installed

package MQSeriesSDK-7.5.0-3.x86_64 is already installed

package MQSeriesXRClients-7.5.0-3.x86_64 is already installed

Refreshing settings for Primary Installation ‘Installation1’ (/opt/mqm).

118 of 118 tasks have been completed successfuly.

‘Installation1’ (/opt/mqm) set as the Primary Installation.

/var/apps/installs/integrationbus_developer/WebSphere_MQ

Installing IBM Integration Bus

/var/apps/installs/integrationbus_developer/WebSphere_MQ

Installing IBM Integration Explorer

/var/apps/installs/integrationbus_developer/WebSphere_MQ

Installing IBM Integration Toolkit

Installed com.ibm.cic.agent_1.6.2000.20130301_2248 to the /opt/IBM/InstallationManager/eclipse directory.

Installed com.ibm.integration.toolkit.dev.v90_9.0.0.20140515-1210 to the /opt/IBM/IntegrationToolkit90 directory.

You will see that when WMQ installed it is given an instance: ‘Installation1’ (/opt/mqm) set as the Primary Installation. This is important to note as you can in fact have more than one installation of WMQ now on the same machine.

Verifying Installation

We have now completed the installation. Since this is an installation which presumes you are using IIB 9.0 on a Linux desktop for learning, I am going to log into a remote session using X2Go client and test the GUI’s.

I am using a MATE XSession, and we can now see that we have the following:

IBM Installation Manager has been installed, this is the IBM interface to manage GUI installs. IBM Integration Toolkit can also be seen in the menu.

Launching the IBM Installation Manager (IM), we see the following:

If we click on modify, we can see what has been installed and managed by IM.

Running IB Explorer

After installing IBM Integration Explorer you must complete the following step:

To initialize the new installation of IBM Integration Explorer, run the following command from a command line in which the mqsiprofile command has not run:

Note: You must be in a terminal within an XSession or have a display set i.e. to a local XServer like Xming.

  • Initialise IB Explorer
/usr/bin/strmqcfg-i

 

To run this command, you must be the administrator or root user.

Once the command is run, you can now run the following command to start IB Explorer

  • Start IB Explorer

 

/usr/bin/strmqcfg

 

Once you have verified that IB Explorer is working, we just need to verify that WMQ is installed and working.

Verifying WMQ

The majority of these commands are run as the mqm (or equivalent) user. By default these commands are in /opt/mqm/bin

It is recommended that you add this path to the mqm users PATH. Now since we are using root still at this time, we will find that there is not path set. You can set the path for the root profile or you can start using the mqm user. I would recommend using the mqm user now that we have WMQ installed.

  • Switch to the mqm user
su – mqm

 

  • Add the /opt/mqm/bin directory to the mqm users’s environment PATH
[mqm@localhost ~]$ vi .bash_profile

# .bash_profile

 

# Get the aliases and functions

if [ -f ~/.bashrc ]; then

. ~/.bashrc

fi

 

# User specific environment and startup programs

 

PATH=$PATH:$HOME/.local/bin:$HOME/bin

PATH=$PATH:/opt/mqm/bin

 

export PATH

 

  • Run dspmqver command to confirm the WMQ installed version
[mqm@localhost ~]$ dspmqver

Name: WebSphere MQ

Version: 7.5.0.3

Level: p750-003-140123

BuildType: IKAP – (Production)

Platform: WebSphere MQ for Linux (x86-64 platform)

Mode: 64-bit

O/S: Linux 3.10.0-123.13.2.el7.x86_64

InstName: Installation1

InstDesc:

Primary: Yes

InstPath: /opt/mqm

DataPath: /var/mqm

MaxCmdLevel: 750

LicenseType: Production

 

We will then create a Queue Manager and then delete it, just to test that the WMQ software is working correctly

  • Create a Queue Called QMVerify1
[mqm@localhost ~]$ crtmqm QMVerify1

WebSphere MQ queue manager created.

Directory ‘/var/mqm/qmgrs/QMVerify1’ created.

The queue manager is associated with installation ‘Installation1’.

Creating or replacing default objects for queue manager ‘QMVerify1’.

Default objects statistics : 74 created. 0 replaced. 0 failed.

Completing setup.

Setup completed.

 

  • Display the current Queue Managers (QM) to see if QMVerify1 exists?
[mqm@localhost ~]$ dspmq

QMNAME(QMVerify1) STATUS(Ended immediately)

 

  • Let’s now start the QM to verify that it will run?
[mqm@localhost ~]$ strmqm QMVerify1

WebSphere MQ queue manager ‘QMVerify1’ starting.

The queue manager is associated with installation ‘Installation1’.

5 log records accessed on queue manager ‘QMVerify1’ during the log replay phase.

Log replay for queue manager ‘QMVerify1’ complete.

Transaction manager state recovered for queue manager ‘QMVerify1’.

WebSphere MQ queue manager ‘QMVerify1’ started using V7.5.0.3.

Now that we have verified that WMQ is working we can stop and remove the QM.

  • Stop the running QM
[mqm@localhost ~]$ endmqm QMVerify1

Quiesce request accepted. The queue manager will stop when all outstanding work

is complete.

 

  • Verify the status
[mqm@localhost ~]$ dspmq

QMNAME(QMVerify1) STATUS(Ended normally)

 

  • Remove the QM
[mqm@localhost ~]$ dltmqm QMVerify1

WebSphere MQ queue manager ‘QMVerify1’ deleted.

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Leave a Reply