Mq Linux Installation

8/8/2019 Mq Linux Installation

1/4

Installation

=====================1 Preparations on MQ server

=====================

1.1 User creation

Create following user with group name of mqm which will be used to run MQ

1.2 Create mount points to install MQ

create mqm under /opt and /varcreate /opt/mqm, make it RW to mqm group and 600MB in space capacitycreate /var/mqm, make it RW to mqm group and 300MB in space capacity

1.3 Kernel configuration parameters

make following kernel changes (/etc/sysctl.conf ):kernel.msgmni = 1024kernel.shmmni = 4096kernel.shmall = 2097152kernel.sem = 500 256000 250 1024fs.file-max = 32768net.ipv4.tcp_keepalive_time = 300

If you wish to load these sysctl values immediately, enter the command sysctl -p.note: If you do not issue the sysctl -p command, the new values are loaded when the system is rebooted.

1.4 Max open files

If the system is heavily loaded, you might need to increase the maximum possible number of open files. Ifyour distribution supports the proc filesystem you can query the current limit by issuing the followingcommand: cat /proc/sys/fs/file-max

If you are using a pluggable security module such as PAM (Pluggable Authentication Module), ensurethat this does not unduly restrict the number of open files for the mqm user. For a standard WebSphereMQ queue manager, set the nofile value to 10240 or more for the mqm user. We suggest you add thiscommand to a startup script in /etc/rc.d/

1.5 Max process

A running WebSphere MQ queue manager consists of a number of thread programs, and eachconnected 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 undulyrestricted by one of the pluggable security modules such as PAM. Set nproc for the mqm user to 4090 ormore.

1.6 Root access privilegethis is needed when doing the MQ installation.

1.7 64bit considerationImplications of a 64-bit queue manager Note: A 64-bit queue manager is available on the POWER, x86-


2/4

64 and zSeries (s390x) platforms. When using the 64-bit queue manager, the use of the LIBPATH andLD_LIBRARY_PATH environment variable is not advised.

The recommended way of using WebSphere MQ commands and your applications is as follows: Unset LIBPATH and LD_LIBRARY_PATH and build your applications with a built in path to theappropriate WebSphere MQ libraries, this is detailed in the appropriate WebSphere MQ book for your

type of WebSphere MQ application. If you need to set LIBPATH or LD_LIBRARY_PATH, consider not including /usr/lib in the path youspecify in the variable. If you need to include /usr/lib in your LIBPATH or LD_LIBRARY_PATH then inorder to avoid errors running 64-bit WebSphere MQ applications or WebSphere MQ commands, considerremoving the symbolic links from /usr/lib to the 32-bit WebSphere MQ libraries using the dltmqlnkcommand. The symbolic links can be restored with the crtmqlnk command. You also need to build yourapplications with a built in path to the appropriate WebSphere MQ libraries.Note that both the dltmqlnk command and the crtmqlnk command are scripts, and take no parameters. If you cannot use either of the first two options, run your applications in a different environment to theone which issues any WebSphere MQ commands.Note: WebSphere MQ libraries are in the following locations: /opt/mqm/lib (32-bit libraries) and/opt/mqm/lib64 (64-bit libraries).

==========2 Installation

==========

2.1 Install rpm

2.1.1 Log in as root.And make sure all RPMs are in your current directory.

2.1.2 Run the mqlicense.sh script.If you want to view a text-only version of the license, which can be read by a screen-reader, type:./mqlicense.sh -text_onlyThe license is displayed.

If want to accept the license without it being displayed, you can run the mqlicense.sh script with the -accept option. ./mqlicense.sh -acceptYou must accept the license agreement before you can proceed with the installation.

2.1.3 Install componentsUse the rpm -ivh command to install each component that you require.The minimum components you must install are: MQSeriesRuntime MQSeriesJRE MQSeriesServer MQSeriesJavaThis example shows a minimum installation:rpm -ivh MQSeriesRuntime-7.0.0-0.i386.rpm MQSeriesSDK-7.0.0-0.i386.rpm MQSeriesServer-7.0.0-

0.i386.rpm MQSeriesJava-7.0.0-0.i386.rpm

for 64bit:rpm -ivh MQSeriesRuntime-7.0.0-0.x86_64.rpmrpm -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

You can reinstall the /bin/sh shell using RPM, or specify the RPM option nodeps to disable dependencychecking during installation of WebSphere MQ.


3/4

Install rest of the components:rpm -ivh MQSeriesSDK-7.0.0-0.x86_64.rpmrpm -ivh MQSeriesSamples-7.0.0-0.x86_64.rpmrpm -ivh MQSeriesClient-7.0.0-0.x86_64.rpmrpm -ivh gsk7bas-7.0-4.14.i386.rpm

rpm -ivh gsk7bas64-7.0-4.14.x86_64.rpmrpm -ivh MQSeriesKeyMan-7.0.0-0.x86_64.rpmrpm -ivh MQSeriesMan-7.0.0-0.x86_64.rpmrpm -ivh MQSeriesTXClient-7.0.0-0.x86_64.rpmrpm -ivh MQSeriesEclipseSDK33-7.0.0-0.x86_64.rpmrpm -ivh MQSeriesConfig-7.0.0-0.x86_64.rpm

2.1.4 client install:

Install minimum components: MQSeriesRuntime MQSeriesJRE MQSeriesServer MQSeriesJava

for 64bit:rpm -ivh MQSeriesRuntime-7.0.0-0.x86_64.rpmrpm -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

Then:rpm -ivh MQSeriesClient-7.0.0-0.x86_64.rpm

================2.2 Install verification

================

2.2.1 Create a sample Queuemqm@li-dev01>crtmqm -q QM_test.queue.managerThere are 90 days left in the trial period for this copy of WebSphere MQ.WebSphere MQ queue manager created.Creating or replacing default objects for QM_test.queue.manager.Default objects statistics : 58 created. 0 replaced. 0 failed.Completing setup.Setup completed.

mqm@li-dev01>strmqmThere are 90 days left in the trial period for this copy of WebSphere MQ.WebSphere MQ queue manager QM_test.queue.manager starting.

5 log records accessed on queue manager QM_test.queue.manager during the log replay phase.Log replay for queue manager QM_test.queue.manager complete.Transaction manager state recovered for queue manager QM_test.queue.manager.WebSphere MQ queue manager QM_test.queue.manager started.

mqm@li-dev01>runmqsc5724-H72 (C) Copyright IBM Corp. 1994, 2008. ALL RIGHTS RESERVED.Starting MQSC for queue manager QM_test.queue.manager.


4/4

define qlocal (test_QL.queue)1 : define qlocal (test_QL.queue)

AMQ8006: WebSphere MQ queue created.end2 : endOne MQSC command read.

No commands have a syntax error.All valid MQSC commands were processed.mqm@li-dev01>

2.2.2 Test the sample queuemqm@li-dev01>cd /opt/mqm/samp/binmqm@li-dev01>./amqsput test_QL.QUEUESample AMQSPUT0 starttarget queue is test_QL.QUEUESample AMQSPUT0 end

Sample AMQSPUT0 endmqm@li-dev01>./amqsget test_QL.QUEUESample AMQSGET0 startmessageno more messagesSample AMQSGET0 end

Mq Linux Installation

Documents

Transcript of Mq Linux Installation