{"id":4702,"date":"2015-05-03T11:11:31","date_gmt":"2015-05-03T03:11:31","guid":{"rendered":"http:\/\/rmohan.com\/?p=4702"},"modified":"2015-05-04T10:22:42","modified_gmt":"2015-05-04T02:22:42","slug":"4702","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=4702","title":{"rendered":"How to Install MQ on Redhat Linux"},"content":{"rendered":"

How to Install MQ on Redhat Linux<\/h3>\n
1.1 User creationLogin as\u00a0<\/span>root\u00a0<\/span>to install mq<\/p>\n

Create following user with group name of \u201cmqm\u201d which will be used to run MQ
\ngroupadd mqm # add group mqm (purpose of gropuadd is to create\u00a0<\/span>
\na new group account)
\nuseradd -g mqm mqm # add user mqm to group mqm
\n(gpn)(usrn)\u00a0<\/span>
\n# gpn \u2013 groupname\u00a0<\/span>
\n# usrn — username\u00a0<\/span>
\n(useradd or usermod command is used to add a user to a\u00a0<\/span>
\ngroup.useradd command creates a new user or update\u00a0<\/span>
\ndefault new user information.usermod command modifies a\u00a0<\/span>
\nuser account i.e. it is useful to add user to existing\u00a0<\/span>
\ngroup.User account related info is stored in \/etc\/passwd,\u00a0<\/span>
\n\/etc\/shadow and \/etc\/group.)<\/p>\n

1.2 Create mount points to install MQ<\/p>\n

create mqm folder under \/opt and \/var where the Websphere MQ gets installed.
\ncreate \/opt\/mqm\u00a0<\/span><\/p>\n

root@li-dev01\/> cd \/opt\/\u00a0<\/span>
\nroot@li-dev01\/opt> mkdir mqm # make it RW to mqm group and 600MB in space capacity
\ncreate \/var\/mqm as above # make it RW to mqm group and 300MB in space capacity
\nroot@li-dev01\/var> mkdir mqm<\/p>\n

1.3 Kernel configuration parameters<\/p>\n

make following kernel changes (\/etc\/sysctl.conf ): # mq prerequisites
\nvi \/etc\/sysctl.conf
\n#add these propeties if they are not available
\nkernel.msgmni = 1024
\nkernel.shmmni = 4096
\nkernel.shmall = 2097152<\/p>\n

edit \/etc\/sysctl.conf\u00a0<\/span>
\n#add
\nkernel.sem 250 32000 32 1024<\/p>\n

If you wish to load these sysctl values immediately, enter the command sysctl -p.
\nNote: If you do not issue the sysctl -p command, the new values are loaded when the system is rebooted.<\/p>\n

1.4 Max open files<\/p>\n

If the system is heavily loaded, you might need to increase the maximum possible number of open files. If your distribution supports the proc filesystem you can query the current limit by issuing the following command: cat \/proc\/sys\/fs\/file-max<\/p>\n

If you are using a pluggable security module such as PAM (Pluggable Authentication Module), ensure that this does not unduly restrict the number of open files for the \u2019mqm\u2019 user. For a standard WebSphere MQ queue manager, set the \u2019nofile\u2019 value to 10240 or more for the \u2019mqm\u2019 user. We suggest you add this command to a startup script in \/etc\/rc.d\/\u2026<\/p>\n

1.5 Max process<\/p>\n

A running WebSphere MQ queue manager consists of a number of thread programs, and each connected application will increase the number of threads running in the queue manager processes. You should ensure that the maximum number of processes which the mqm user is allowed to run is not unduly restricted by one of the pluggable security modules such as PAM. Set nproc for the mqm user to 4090 or more.<\/p>\n

1.6 Root access privilege
\nthis is needed when doing the MQ installation.<\/p>\n

1.7 64bit consideration
\nImplications of a 64-bit queue manager Note: A 64-bit queue manager is available on the POWER, x86-64 and zSeries (s390x) platforms. When using the 64-bit queue manager, the use of the LIBPATH and LD_LIBRARY_PATH environment variable is not advised.<\/p>\n

The recommended way of using WebSphere MQ commands and your applications is as follows:
\n\u2022 Unset LIBPATH and LD_LIBRARY_PATH and build your applications with a built in path to the appropriate WebSphere MQ libraries, this is detailed in the appropriate WebSphere MQ book for your type of WebSphere MQ application.
\n\u2022 If you need to set LIBPATH or LD_LIBRARY_PATH, consider not including \/usr\/lib in the path you specify in the variable. If you need to include \/usr\/lib in your LIBPATH or LD_LIBRARY_PATH then in order to avoid errors running 64-bit WebSphere MQ applications or WebSphere MQ commands, consider removing the symbolic links from \/usr\/lib to the 32-bit WebSphere MQ libraries using the dltmqlnk command. The symbolic links can be restored with the crtmqlnk command. You also need to build your applications with a built in path to the appropriate WebSphere MQ libraries.
\nNote that both the dltmqlnk command and the crtmqlnk command are scripts, and take no parameters.
\n\u2022 If you cannot use either of the first two options, run your applications in a different environment to the one which issues any WebSphere MQ commands.
\nNote: WebSphere MQ libraries are in the following locations: \/opt\/mqm\/lib (32-bit libraries) and \/opt\/mqm\/lib64 (64-bit libraries).<\/p>\n

2. Installation of Websphere MQ on Linux:<\/p>\n

2.1 Install rpm<\/p>\n

2.1.1 Log in as root.<\/p>\n

extract Websphere MQ files to the current directory(\/home\/test\/Desktop\/MQ)
\ntar -xzvf Websphere MQ for x86 6.0.tar.gz\u00a0<\/span><\/p>\n

And make sure all RPMs are in your current directory(\/home\/test\/Desktop\/MQ)<\/p>\n

2.1.2 Run the mqlicense.sh script.<\/p>\n

If you want to view a text-only version of the license, which can be read by a screen-reader, type:\u00a0<\/span>
\nroot@li-dev01\/MQ>.\/mqlicense.sh -text_only
\nThe license is displayed.If want to accept the license without it being displayed, you can run the mqlicense.sh script with the -accept option.\u00a0<\/span><\/p>\n

# run this command from the current directory where Websphere MQ files are extracted.\u00a0<\/span>
\nroot@li-dev01\/MQ>.\/mqlicense.sh -accept\u00a0<\/span>
\nYou must accept the license agreement before you can proceed with the installation.<\/p>\n

2.1.3 Install components
\nUse the rpm -ivh command to install each component that you require.
\nThe\u00a0<\/span>minimum\u00a0<\/span>components you must install are:
\n\u2022 MQSeriesRuntime
\n\u2022 MQSeriesJRE
\n\u2022 MQSeriesServer
\n\u2022 MQSeriesJava
\nThis example shows a minimum installation:<\/p>\n

rpm -ivh MQSeriesRuntime-6.0.0-0.i386.rpm MQSeriesSDK-6.0.0-0.i386.rpm MQSeriesServer-6.0.0-0.i386.rpm MQSeriesJava-6.0.0-0.i386.rpm
\n(At a strech u can install all the rpms or u can install one by one\u00a0<\/span>
\n(1.) rpm -ivh MQSeriesRuntime-6.0.0-0.i386.rpm
\n(2.) rpm -ivh MQSeriesSDK-6.0.0-0.i386.rpm
\n(3.) rpm -ivh MQSeriesServer-6.0.0-0.i386.rpm
\n(4.) rpm -ivh MQSeriesJava-6.0.0-0.i386.rpm)<\/p>\n

for 64bit:
\nrpm -ivh MQSeriesRuntime-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesJava-7.0.0-0.x86_64.rpm MQSeriesJRE-7.0.0-0.x86_64.rpm MQSeriesServer-7.0.0-0.x86_64.rpm<\/p>\n

You can reinstall the \/bin\/sh shell using RPM, or specify the RPM option \u2013nodeps to disable dependency checking during installation of WebSphere MQ.<\/p>\n

Install rest of the components:
\nrpm -ivh MQSeriesSDK-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesSamples-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesClient-7.0.0-0.x86_64.rpm
\nrpm -ivh gsk7bas-7.0-4.14.i386.rpm
\nrpm -ivh gsk7bas64-7.0-4.14.x86_64.rpm
\nrpm -ivh MQSeriesKeyMan-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesMan-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesTXClient-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesEclipseSDK33-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesConfig-7.0.0-0.x86_64.rpm<\/p>\n

when you are installing\u00a0<\/span>MQSeriesIES33-7.0.0-0.x86_64.rpm, if you get any error saying that\u00a0<\/span>libstdc++.so\u00a0<\/span>is needed then go to the link\u00a0<\/span><\/p>\n

http:\/\/rpmfind.net\/linux\/rpm2html\/search.php?query=libstdc%2B%2B.so.5&submit=Search+…
\nAnd search for\u00a0<\/span>libstdc++5.0-3.3.3-62745cl.i386.html\u00a0<\/span>GNU c++ library and download and Install that rpm.
\n(or)<\/p>\n

use rpm -ivh -nodeps MQSeriesIES33-7.0.0-0.x86_64.rpm<\/p>\n

2.1.4 client install:<\/p>\n

Install minimum components:
\n\u2022 MQSeriesRuntime
\n\u2022 MQSeriesJRE
\n\u2022 MQSeriesServer
\n\u2022 MQSeriesJava<\/p>\n

for 64bit:
\nrpm -ivh MQSeriesRuntime-7.0.0-0.x86_64.rpm
\nrpm -ivh MQSeriesJava-7.0.0-0.x86_64.rpm MQSeriesJRE-7.0.0-0.x86_64.rpm MQSeriesServer-7.0.0-0.x86_64.rpm<\/p>\n

Then:
\nrpm -ivh MQSeriesClient-7.0.0-0.x86_64.rpm<\/p>\n

================
\n2.2 Install verification
\n================<\/p>\n

2.2.1 Create a sample Queue<\/p>\n

login as MQM user
\nsu – mqm<\/p>\n

mqm@li-dev01>crtmqm -q QM_test.queue.manager #-q indicates default queue manager
\nThere are 90 days left in the trial period for this copy of WebSphere MQ.
\nWebSphere MQ queue manager created.
\nCreating or replacing default objects for QM_test.queue.manager.
\nDefault objects statistics : 58 created. 0 replaced. 0 failed.
\nCompleting setup.
\nSetup completed.<\/p>\n

# if queue manager is not created and gives\u00a0<\/span>AMQ8081\u00a0<\/span>error with863\u00a0<\/span>code
\ndownload\u00a0<\/span>fixpack\u00a0<\/span>from\u00a0<\/span>
\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?rs=171&uid=swg24015717<\/p>\n

tar -xvf 6.0.2-WS-MQ-LinuxIA32-FP0005.tar
\nMake sure that Fix pack is extracted in the directory(\/home\/test\/Desktop\/Patch)<\/p>\n

rpm -ivh all the below rpms<\/p>\n

\u2022 MQSeriesRuntime
\n\u2022 MQSeriesJRE
\n\u2022 MQSeriesServer
\n\u2022 MQSeriesJava<\/p>\n

# if queue manager is not created and gives\u00a0<\/span>AMQ8108\u00a0<\/span>error with893\u00a0<\/span>code then install\u00a0<\/span>IBMJava2-142-ia32-SDK-1.4.2-6.0.i386.rpm\u00a0<\/span>from the fix pack,<\/p>\n

when you are installing this rpm if you get any error saying that libXp.so, then go to the link and download that and install this rpm
\nftp:\/\/ftp.pbone.net\/mirror\/ftp.centos.org\/5.4\/os\/x86_64\/CentOS\/libXp-1.0.0-8.1.el5.i386.rpm\u00a0<\/span><\/p>\n

mqm@li-dev01>strmqm
\nThere are 90 days left in the trial period for this copy of WebSphere MQ.
\nWebSphere MQ queue manager \u2018QM_test.queue.manager\u2019 starting.
\n5 log records accessed on queue manager \u2018QM_test.queue.manager\u2019 during the log replay phase.
\nLog replay for queue manager \u2018QM_test.queue.manager\u2019 complete.
\nTransaction manager state recovered for queue manager \u2018QM_test.queue.manager\u2019.
\nWebSphere MQ queue manager \u2018QM_test.queue.manager\u2019 started.<\/p>\n

mqm@li-dev01>runmqsc
\n5724-H72 (C) Copyright IBM Corp. 1994, 2008. ALL RIGHTS RESERVED.
\nStarting MQSC for queue manager QM_test.queue.manager.<\/p>\n

define qlocal (test_QL.queue)
\n1 : define qlocal (test_QL.queue)
\nAMQ8006: WebSphere MQ queue created.
\nend
\n2 : end
\nOne MQSC command read.
\nNo commands have a syntax error.
\nAll valid MQSC commands were processed.
\nmqm@li-dev01><\/p>\n

2.2.2 Test the sample queue
\nmqm@li-dev01>cd \/opt\/mqm\/samp\/bin
\nmqm@li-dev01>.\/amqsput test_QL.QUEUE
\nSample AMQSPUT0 start
\ntarget queue is test_QL.QUEUE
\nSample AMQSPUT0 end<\/p>\n

# if \/opt\/mqm\/samp\/bin is not found install rpm MQSeriesSamples.<\/p>\n

Sample AMQSPUT0 end
\nmqm@li-dev01>.\/amqsget test_QL.QUEUE
\nSample AMQSGET0 start
\nmessage
\nno more messages
\nSample AMQSGET0 end<\/p>\n

3. Uninstalling Websphere MQ in Linux:<\/p>\n

Remove install RPMs<\/p>\n

login as root<\/p>\n

root@websphere mwinstall]# rpm -ivh IBMJava2-SDK-1.4.2-0.0.i386.rpm to install, so I queried to find out what the software name of the rpm was as you cannot use the rpm filename that you used to install the rpm.<\/p>\n

root@websphere mq]# rpm -qa | grep IBM
\nIBMJava2-SDK-1.4.2-0.0<\/p>\n

rpm -e IBMJava2-SDK-1.4.2-0.0<\/p>\n

This worked however for the other rpm;s I had to remove the fix-packs first<\/p>\n

Remove fix pack rpm’s<\/p>\n

Use this command to see which Websphere MQSeries base rpms and fixpacks are installed
\nroot@websphere mq]# rpm -qa | grep MQSeries<\/p>\n

I used rpm -ivh IBMJava2-142-ia32-SDK-1.4.2-6.0.i386.rpm to apply fix pack
\nSo I used rpm -e IBMJava2-142-ia32-SDK-1.4.2-6.0<\/p>\n

install: rpm -ivh MQSeriesRuntime-U809950-6.0.2-2.i386.rpm
\nremove: rpm -e MQSeriesRuntime-U809950-6.0.2-2<\/p>\n

install: rpm -ivh MQSeriesServer-U809950-6.0.2-2.i386.rpm
\nremove: rpm -e MQSeriesServer-U809950-6.0.2-2<\/p>\n

install: rpm -ivh MQSeriesJava-U809950-6.0.2-2.i386.rpm
\nremove: rpm -e MQSeriesJava-U809950-6.0.2-2<\/p>\n

Remove base rpm’s<\/p>\n

I had to do in this order<\/p>\n

rpm -e MQSeriesJava-6.0.0-0<\/p>\n

rpm -e MQSeriesServer-6.0.0-0<\/p>\n

rpm -e MQSeriesRuntime-6.0.0-0<\/p>\n

Query to make sure they have all been removed<\/p>\n

rpm -qa | grep MQSeries<\/p>\n

Remove MQ directories<\/p>\n

\/opt\/mqm # cd \/opt , rm -rf mqm
\n\/var\/mqm # cd \/var , rm -rf mqm<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

How to Install MQ on Redhat Linux 1.1 User creationLogin as root to install mq<\/p>\n

Create following user with group name of \u201cmqm\u201d which will be used to run MQ groupadd mqm # add group mqm (purpose of gropuadd is to create a new group account) useradd -g mqm mqm # add user mqm to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[57],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/4702"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4702"}],"version-history":[{"count":2,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/4702\/revisions"}],"predecessor-version":[{"id":4704,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/4702\/revisions\/4704"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}