Verifying IB9

To verify that the IB9 administration command work, we will create a broker, run it and then delete it

Setting up the environment.

To make the IB command available, we will use a pre-defined script that we will add the path to the IB command scripts into the .bash_profile file, so that when we log in as mqm the path will automatically be set.

  • Edit the bash profile
[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

PATH=$PATH:/opt/ibm/mqsi/9.0.0.2/bin

 

export PATH

 

Once you have changed the .bash_local file, source it to ensure the path is set

source ./bash_profile

 

Using the echo command verify the path is set, or just re-login as mqm to execute the bash_profile

  • Confirm PATH

 

[mqm@localhost ~]$ echo $PATH

/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/var/mqm/.local/bin:/var/mqm/bin:/opt/mqm/bin:/opt/ibm/mqsi/9.0.0.2/bin

 

To set up an IB environment we can run the mqsiprofile command

 

  • Setting an IB environment profile

 

[mqm@localhost ~]$ source /opt/ibm/mqsi/9.0.0.2/bin/mqsiprofile

 

MQSI 9.0.0.2

/opt/ibm/mqsi/9.0.0.2

 

  • Create a Broker Node
mqsicreatebroker Brk01Verify -q QMVerify02

WebSphere MQ queue manager created.

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

The queue manager is associated with installation ‘Installation1’.

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

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

Completing setup.

Setup completed.

WebSphere MQ queue manager ‘QMVerify02’ starting.

The queue manager is associated with installation ‘Installation1’.

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

Log replay for queue manager ‘QMVerify02’ complete.

Transaction manager state recovered for queue manager ‘QMVerify02’.

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

BIP8081 An exception was caught while processing the response message for the command, ‘Unable to format an ImbException message for output, ImbException message number is BIP8000’.

 

In the example above, since this is a new installation we have an error. The error code us BIP8081:

 

Message BIP8081 is issued when creating a broker

Scenario: Message BIP8081E is displayed when you are creating a broker, the inserted message does not format correctly, and the broker is not created.

Explanation: This problem occurs because you are not a member of the correct group.

Solution: Read the explanation of message BIP8081, and ask your WebSphere® Message Broker administrator to give your user ID access to the mqbrkrs group.

 

We now need to go switch back to root and add the appropriate group and add mqm to that group

[root@localhost ~]# groupadd mqbrkrs

groupadd: group ‘mqbrkrs’ already exists

 

Note: Above, I show you the command, but we already have it as the installation created the group for us.

  • Add the mqm user to mqbrkrs group
[root@localhost ~]# usermod -G mqbrkrs mqm

[root@localhost ~]# groups mqm

 

  • Switch back to mqm user

Verify state of Broker Node

 

[mqm@localhost ~]$ mqsilist

BIP1285I: Broker ‘Brk01Verify’ on queue manager ‘QMVerify02’ is stopped.

BIP8071I: Successful command completion.

 

  • Start Broker Node

 

mqsistart Brk01Verify

BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.

 

  • Verify Broker State
[mqm@localhost ~]$ mqsilist

BIP1284I: Broker ‘Brk01Verify’ on queue manager ‘QMVerify02’ is running.

BIP8071I: Successful command completion.

 

  • Stop Broker
[mqm@localhost ~]$ mqsistop Brk01Verify

BIP8071I: Successful command completion.

 

 

  • Remove Broker

If you remove a broker by just using the command mqsideletebroker it will only remove the broker, not the queue manager associated. To remove the broker, the QM and trace files use the following command

[mqm@localhost ~]$ mqsideletebroker Brk01Verify -q -w

Waiting for queue manager ‘QMVerify02’ to end.

WebSphere MQ queue manager ‘QMVerify02’ ended.

WebSphere MQ queue manager ‘QMVerify02’ deleted.

BIP8071I: Successful command completion.

 

  • Re-verify Broker Status
[mqm@localhost ~]$ mqsilist

\BIP1281I: No brokers have been defined on this machine.

BIP8071I: Successful command completion.

 

  • Verify that the QM was also deleted
[mqm@localhost ~]$ dspmq

[mqm@localhost ~]$

 

If there is no result then we have verified that the QM has been removed as well

Congratulations, you have now completed the module.

Summary

In this chapter, we have learned how to install IIB9.0 on a Linux CentOS 7 server. The product we used as the free demo known as IBM Integration Bus for Developers.

We covered how to solve installation issues with Integration Bus, Integration Toolkit and Integration Explorer and we also learned how to verify the components to ensure they were all working as intended.

This module is a sample chapter which is included in the IIB 9.0 course which will be released 2015.

To learn more about the courses available from The Middleware Shop, please go to http://www.themiddlewareshop.com/products to see a full list of the current courses available.

Facebooktwittergoogle_plusredditpinterestlinkedinmail

Leave a Reply