{"id":6459,"date":"2017-02-02T16:00:22","date_gmt":"2017-02-02T08:00:22","guid":{"rendered":"http:\/\/rmohan.com\/?p=6459"},"modified":"2017-02-02T16:00:22","modified_gmt":"2017-02-02T08:00:22","slug":"mq-8-on-centos-6-8","status":"publish","type":"post","link":"https:\/\/mohan.sg\/?p=6459","title":{"rendered":"MQ 8 on CENTOS 6.8"},"content":{"rendered":"

MQ 8 on CENTOS 6.8<\/strong><\/p>\n

WebSphere MQ installation and validation<\/p>\n

WebSphere MQ installation and validation
\nready
\n1 Check the installation hardware and software requirements
\n2 Installation Notes
\nSingle server installs MQ and authentication
\n1 Create a user and user group Optional step
\n2 Extract the downloaded MQ installation package
\n3 Check if the rpm package is installed
\n4 Review the license agreement and accept the required
\n5 Install the MQ Server components
\n6 Verify that the installation was successful
\nDual-server installation of MQ and authentication
\n1 Preparation
\n2 Configure the B machine
\n3 Configure the A machine
\n4 Authentication
\nMQ client installation and validation
\n1 Preparation
\n2 Configure the MQ server B machine
\n3 Configure the MQ client C machine
\n4 Test the connectivity between the client and the server
\nUnload MQ
\nOther records<\/p>\n

1. Preparation
\n1.1 Check the installation hardware and software requirements<\/p>\n

Check MQ installation conditions, SUSE Linux 64-bit installation requirements are as follows: here to the latest 9.0, 8.0 example
\n– MQ 9.0 operating system requires SUSE Linux Enterprise Server 12 SP1 x86-64, 8.0 SUSE Linux 11 SP2
\n– The HyperVisor virtualization platform supports VMware ESXi 5.5 and above, and Hyper-V supports 2012, KVM
\n– Supported software: WAS, gcc4.8 or above, DB2 10.5.0.6, IBM JRE (most components only support built-JRE)
\n– Disk space requires 1GB (server component installation), memory recommended 3GB<\/p>\n

Specific see the official website to provide the requirements of the various platforms, including version MQ 9.0, MQ 8.0
\n1.2 Installation Precautions<\/p>\n

About the installation name<\/p>\n

Determine the unique installation name, incremented by Installation1,2 by default, and Installation0 reserved for the 7.0.1 MQ installation name
\nThe installation name can not be changed after successful installation
\nNames require upper and lower case letters and numbers, no spaces, case insensitive, up to 16 bytes
\nInstallation description information, you can set a 64-byte description, allowing Chinese and English
\nLinux use crtmqinst command to set the installation name, setmqinst command to set the description information<\/p>\n

Multiple copies are installed<\/p>\n

MQ supports single mount multiple copies (multiple versions or different installations of the same version), differentiated by different installation locations
\nA single machine supports up to 128 copies of the installation
\nMulti-copy installation can set up a master copy, the system will create environment variables and symbolic links, part of the management script command function requires these settings;
\nMulti-copy installations that support MQ 7.0 fp6 later, for installations that require multiple copies 7.0.1 Must be the first installation and automatically a master installation copy
\nPrior to MQ 7, only one product instance could be installed on a single machine<\/p>\n

Single copy installation
\n– Beginning with version 7.1, the first copy of the MQ installation on Windows defaults to the master copy. Linux needs to be configured manually (the setmqinst command)
\n– It is recommended that you set up a master installation copy so that MQ commands and libraries can be easily applied and create symbolic links under \/ usr \/ lib, \/ usr \/ bin \/, \/ usr \/ include
\n– For non-primary installation copies, manually set the environment variables and the library path configuration, such as LD_INSTALLATION_PATH<\/p>\n

Installation location
\n– Linux default installation location \/ opt \/ mqm, working data directory \/ var \/ mqm
\n– Linux path length up to 256 bytes, no spaces allowed
\n– The installation path can not have subdirectories and partial paths of the installed MQ path
\n– Typical installation paths: \/opt\/IBM\/MQ and \/opt\/IBM\/MQnew or \/opt\/IBM\/MQ\/installations\/1 and \/opt\/IBM\/MQ\/installations\/2<\/p>\n

MQ Installation Components (Linux)
\n– Runtime (MQSeriesRuntime), the runtime environment, must be installed (both client and server)
\n– Server (MQSeriesServer), running the queue manager and providing message queue services, the server-side needs
\n– Client (MQSeriesClient), a small subset of the functionality of MQ, a connection to the Server component, no queue manager
\n– SDK (MQSeriesSDK), development needs, used to compile the application
\n– Sample program, sample program
\n– Java messaging (MQSeriesJava), support Java Message Service Function (JMS)
\n– Man pages, help documentation, provide control commands, MQI commands, MQSC command help
\n– Java JRE, must, Java runtime, support the MQ part of Java written functions
\n– Message Catalogs, supported languages
\n– Global Security Kit, which supports encryption and security authentication, must be installed JRE
\n– Telemetry Service (MQSeriesXRService), remote sensing communication MQTT protocol, support for sensors and other devices to connect communication
\n– MQ Explorer, Management Monitor MQ
\n– Managed File Transfer, file transfer
\n– Advanced Message Security, the more advanced security, you must install the JRE and Security Kit
\n– AMQP Service, providing AMQP channel, support MQ Light APIs
\n2. Stand-alone server to install MQ and authentication<\/p>\n

This article uses SUSE Linux Enterprise 11 x64 SP4 system, installed in the virtual machine environment, MQ selected version 8.0.
\nBefore you install MQ, you need to set up the operating system.
\n2.1 Creating Users and User Groups (Optional)<\/p>\n

On Linux, MQ needs to create the install user mqm and the user group mqm (be careful to ensure that the UID and GID are consistent when installing MQ with multiple systems or multiple instances)
\nThe user ID has permissions to the MQ installation directory and files. The default MQ installation is automatically created when no mqm user is found.
\nYou need to specify a specific UID and GID as the installation user for MQ, and you can manually create users and groups before installation.
\nPrivilege Requirement: The normal user must belong to the mqm group to run the related administrative commands, such as crtmqm (create queue manager) and strmqm (start queue manager) commands<\/p>\n

# groupadd -g 3000 mqm
\n# useradd -g mqm -u 3000 mqm<\/p>\n

2.2 Extract the downloaded MQ installation package<\/p>\n

# su – root
\n# cd \/home\/mq
\n# tar -xvf WSMQ_8.0_IFR_TRIAL_LNX_ON_X86_64_.tar.gz<\/p>\n

2.4 Viewing the License Agreement and Accepting (Required)<\/p>\n

# cd \/home\/mq\/server
\n# .\/mqlicense.sh -text_only<\/p>\n

2.5 Install the MQ Server components<\/p>\n

Installed in the default location \/opt\/mqm, if you need to change to join – prefix \/opt\/mymq<\/p>\n

rpm -ivh MQSeriesRuntime-*.rpm MQSeriesServer-*.rpm<\/p>\n

WARNING: System settings for this system do not meet recommendations for this product
\nSee the log file at “\/tmp\/mqconfig.11472.log” for more information<\/p>\n

more \/tmp\/mqconfig.11472.log<\/p>\n

sysctl -a | more<\/p>\n

Modify sysctl.conf file, mqconfig.11472.log not pass parameters modified
\nSp4 linux suse main file-max, nofile failed to detect<\/p>\n

Add a line, note the space\u00a0 Sets the maximum number of kernel open files
\nvim \/etc\/sysctl.conf<\/p>\n

fs.file-max = 524288<\/p>\n

View the maximum number of files that can be opened by the user process<\/p>\n

View the maximum number of files that can be opened by the user process
\n# su – mqm
\n# Ulimit -n shows 1024, and MQ requires 10240
\nIncrease the maximum number of mqm users to open files
\n# su – root
\n# vim \/etc\/security\/limits.conf
\nAdd to:
\nmqm hard nofile 10240
\nmqm hard nofile 10240
\nroot hard nofile 10240
\nroot hard nofile 10240<\/p>\n

# su – root
\n# ulimit -n
\nView the display 10240 is to take effect<\/p>\n

rpm -ivh MQSeriesRuntime-*.rpm MQSeriesServer-*.rpm
\nprompt:
\npackage MQSeriesRuntime-8.0.0-2.x86_64 is already installed
\npackage MQSeriesServer-8.0.0-2.x86_64 is already installed<\/p>\n

# rpm -q MQSeriesServer
\n# rpm -e MQSeriesServer-8.0.0-2
\n# rpm -q MQSeriesRuntime
\n# rpm -e MQSeriesRuntime-8.0.0-2<\/p>\n

# cd \/home\/mq\/server
\n# .\/mqlicense
\n# rpm -ivh MQSeriesRuntime-*.rpm MQSeriesServer-*.rpm<\/p>\n

2.6 Verify that the installation was successful<\/p>\n

Verify that you need to install the built-in sample package component, MQSeriesSamples-8.0.0-2.x86_64.rpm
\nExamples of Authentication Complete the functions of creating and configuring a queue manager, sending messages to a queue, and getting messages from a queue<\/p>\n

# rpm -ivh MQSeriesSamples-8.0.0-2.x86_64.rpm<\/p>\n

# su – mqm
\nSet the environment variable
\n~ cd \/opt\/mqm\/bin
\n~ .\/setmqenv -s<\/p>\n

An error occurred:
\nAMQ8595: The setmqenv command was not preceded by the source command
\nFor an official explanation, see [Web site] (http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.5.0\/com.ibm.mq.ref.doc\/amq8.htm)
\nNeed to order the implementation of the source, not. \/ Or bash setmqenv way;
\nSource or setmqenv -s: is in the current shell environment variables
\nBash setmqenv or. \/ Setmqenv: will open a new sub-shell settings,
\nset up after the return to the parent shell, set the variable can not change the parent shell<\/p>\n

source setmqenv -s
\nCheck whether the set is successful, the implementation of the query mq version information command<\/p>\n

~ dspmqver<\/p>\n

Create the queue manager QMA
\n~crtmqm QMA
\nStarts queue management
\n~strmqm QMA<\/p>\n

To start the MQ script interpreter:
\n~runmqsc QMA<\/p>\n

Define the local queue in the script interpreter:
\nDEFINE QLOCAL (QUEUE1)<\/p>\n

Stop MQSC:
\nEnd<\/p>\n

Go to the sample component directory:
\n~cd \/opt\/mqm\/samp\/bin
\n~.\/amqsput QUEUE1 QMA
\nEnter the sent test message:
\ntest messages from john
\ntest2 messages
\nType enter twice to end with a blank line<\/p>\n

Retrieves the message from the queue
\n.\/amqsget QUEUE1 QMA<\/p>\n

3. Double-server installation of MQ and authentication<\/p>\n

This approach requires two servers, and are installed MQ server, one for sending, one is responsible for receiving messages, which is commonly used MQ scene.<\/p>\n

3.1 Preparation<\/p>\n

Two virtual machine A machine (192.168.98.129), B machine (192.168.98.130), two must be able to communicate with each other network, you can use the ping test
\nA machine and B machine in accordance with the single-server installation (2.1-2.5 steps, not 2.6 verification) Server, Runtime, Sample installed three components.
\nA machine as a sending server (sender), B machine as a receiving server (receiver)<\/p>\n

3.2 Configuration B machine<\/p>\n

Log in as root and switch to the mqm user
\n# su – mqm
\n~ cd \/opt\/mqm\/bin
\n~ source setmqenv -s
\n~ crtmqm QMB
\n~ strmqm QMB
\n~ runmqsc QMB<\/p>\n

Input: DEFINE QLOCAL (RECEIVER.Q) Defines the local queue RECEIVER.Q
\nContinue typing: DEFINE LISTENER (LISTENER1) TRPTYPE (TCP) CONTROL (QMGR) PORT (1414) Defines a listener to receive messages
\nEnter: START LISTENER (LISTENER1)\u00a0 Starts the listener
\nInput: DEFINE CHANNEL (QMA.QMB) CHLTYPE (RCVR) TRPTYPE (TCP) Defines the receiver channel
\nType: end and press Enter to end the input<\/p>\n

3.3 Configuration A machine<\/p>\n

The same root user login, switch to mqm users
\n# su – mqm
\n~ cd \/opt\/mqm\/bin
\n~ source setmqenv -s
\n~ crtmqm QMA
\n~ strmqm QMA
\n~ runmqsc QMA<\/p>\n

Input: D?DEFINE QLOCAL (QMB) USAGE (XMITQ) Defines the local queue QMB as a transmission queue<\/p>\n

Access local definition of remote queue LOCAL.DEF.OF.REMOTE.QUEUE
\nThis definition indicates that the transmit queue QMB of the A machine sends a message to the remote queue (QMB, RECEIVER.Q on the B)<\/p>\n

Input: DEFINE QREMOTE (LOCAL.DEF.OF.REMOTE.QUEUE) RNAME (RECEIVER.Q) RQMNAME (‘QMB’) XMITQ (QMB)<\/p>\n

To define the transmit channel:
\nDEFINE CHANNEL (QMA.QMB) CHLTYPE (SDR) CONNAME (‘192.168.98.130(1414)’) XMITQ (QMB) TRPTYPE (TCP)
\nstart up:
\nSTART CHANNEL (QMA.QMB)<\/p>\n

End:
\nend<\/p>\n

3.4 Verification<\/p>\n

Enter A machine, using the sample program to verify<\/p>\n

# su – mqm
\n~ cd \/opt\/mqm\/samp\/bin
\n~ .\/amqsput LOCAL.DEF.OF.REMOTE.QUEUE QMA
\nAt this point you can easily enter the information in the B machine view
\nFor example: Test messages from A<\/p>\n

Into the B machine
\n# su – mqm
\n~ cd \/opt\/mqm\/samp\/bin
\n~ .\/amqsget RECEIVER.Q QMB<\/p>\n

Found not receive the message, check the reasons and found that network communications may be the problem, mainly port is open, so turn off the B machine firewall
\nLog in as the root user
\n#systemctl stop iptables ; systemctl disable iptables
\n# su – mqm
\n~ cd \/opt\/mqm\/samp\/bin
\n~ .\/amqsget RECEIVER.Q QMB<\/p>\n

4.MQ client installation and validation
\n4.1 Preparation<\/p>\n

Two virtual machines, including B machine (192.168.98.130) as MQ server, C machine (192.168.98.131) as the MQ client
\nThe MQ client (machine C) is connected to the MQ server (machine B), sends the message to the server, and retrieves the message from the server<\/p>\n

** Focus: **
\nIn the client and server machines need to create a non-mqm group of the same id users, the user’s id must be consistent
\nFor example, the user name is mquser1 and the id is 3001<\/p>\n

# useradd mquser1 -u 3001<\/p>\n

4.2 Configuring the MQ Server (B Machine)<\/p>\n

Install the MQ Server components on the B machine, as described in section 2 of this document
\n# useradd mquser1 -u 3001
\n# su – mqm
\n~ cd \/opt\/mqm\/bin
\nSets the mq environment variable
\n~ source setmqenv -s<\/p>\n

Create the queue manager QUEUE.MANAGER.1 and start it
\n~ crtmqm QUEUE.MANAGER.1
\n~ strmqm QUEUE.MANAGER.1
\n~ dspmq\u00a0\u00a0 View all queue manager running status<\/p>\n

Start the script executor and make settings
\n~ runmqsc QUEUE.MANAGER.1
\nInput:
\nDEFINE QLOCAL(QUEUE1) Creates the local queue QUEUE1
\nAuthorize the mquser1 user (id 3001) to use the queue QUEUE1
\nSET AUTHREC PROFILE(QUEUE1) OBJTYPE(QUEUE) PRINCIPAL(‘mquser1’) AUTHADD(PUT,GET)
\nThe authorized user mquser1 can connect to the queue manager
\nSET AUTHREC OBJTYPE(QMGR) PRINCIPAL(‘mquser1’) AUTHADD(CONNECT)<\/p>\n

Defines the server connection channel
\nDEFINE CHANNEL(CHANNEL1) CHLTYPE(SVRCONN) TRPTYPE(TCP)<\/p>\n

Authorized MQ clients can connect to the above-defined channel, and authorize them by ip address and user name
\nSET CHLAUTH(CHANNEL1) TYPE(ADDRESSMAP) ADDRESS(‘192.168.98.131’) MCAUSER(‘mquser1′)<\/p>\n

Defines a listener to accept connections
\nDEFINE LISTENER(LISTENER1) TRPTYPE(TCP) CONTROL(QMGR) PORT(1315)
\nstart up:
\nSTART LISTENER(LISTENER1)
\nEnd:
\nEnd<\/p>\n

4.3 Configuring the MQ Client (C)<\/p>\n

After you unpack the installation package, install the client components
\n# cd \/home\/mq\/server
\n# .\/mqlicense.sh -accept
\n# rpm -ivh MQSeriesRuntime-8.0.0-2.x86_64.rpm MQSeriesClient-8.0.0-2.x86_64.rpm\u00a0 MQSeriesSamples-8.0.0-2.x86_64.rpm<\/p>\n

Test the network connectivity to the MQ Server B machine
\n# Ping 192.168.98.130<\/p>\n

Create a user connecting to the mq server:
\n# useradd mquser1 -u 3001<\/p>\n

Switch to mquser1
\n# su – mquser1<\/p>\n

Set the environment variable to indicate the connection information to the MQ server
\n~ export MQSERVER=CHANNEL1\/TCP\/’192.168.98.130 (1315)’<\/p>\n

Telnet test in Telnet C machines, and success
\n# telnet 192.168.98.130 1315
\n# su – mquser1
\n~ cd \/opt\/mqm\/samp\/bin
\nSend the message to the server
\n~ .\/amqsputc QUEUE1 QUEUE.MANAGER.1
\nEnter the message, the last two enter the end of the key
\nGet the message from the server
\n~ .\/amqsgetc QUEUE1 QUEUE.MANAGER.1<\/p>\n

5. Uninstall MQ<\/p>\n

# rpm -qa | grep MQ Queries the currently installed MQ components
\n# rpm -e MQSeriesServer Uninstall the server component
\n# rpm -e MQSeriesSamples Unload the sample program
\n# rpm -e MQSeriesRuntime Unloads the run-time component, which is typically the last uninstallation<\/p>\n

6. Other records<\/p>\n

Login server implementation:
\n# cd \/opt\/mqm\/samp\/bin
\n#.\/amqsgetc QUEUE1 QUEUE.MANAGER.1<\/p>\n

An error occurred: .\/amqsgetc: error while loading shared libraries: libmqic_r.so: can not open shared object file: No such file or directory<\/p>\n

The error is part of the library is not found, install rpm -ivh rpm -ivm MQSeriesClient-8.0.0-2.x86_64.rpm, and then set the environment variable<\/p>\n

MQ commonly used commands:
\nYou must first set the environment variable to run directly
\n# su – mqm
\n~ cd \/opt\/mqm\/bin
\n~ source setmqenv -s
\n~ dspmq View queue manager status
\n~ runmqsc QUEUE.MANAGER.1
\nEnter the script command to execute the command
\nDIS Displays all commands that can be entered
\nDIS CHL(*) View the channel definition
\nDIS CHL(CHANNEL1) View the specific channel definition
\nDIS LISTENER(*) View the listener definition
\nDIS LSSTATUS(LISTENER1) View the status of the specified listener
\nDIS Q(*) View the queue definition
\nDIS Q(QUEUE1) View the queue definition<\/p>\n","protected":false},"excerpt":{"rendered":"

MQ 8 on CENTOS 6.8<\/p>\n

WebSphere MQ installation and validation<\/p>\n

WebSphere MQ installation and validation ready 1 Check the installation hardware and software requirements 2 Installation Notes Single server installs MQ and authentication 1 Create a user and user group Optional step 2 Extract the downloaded MQ installation package 3 Check if the rpm package […]<\/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\/6459"}],"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=6459"}],"version-history":[{"count":1,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/6459\/revisions"}],"predecessor-version":[{"id":6460,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/6459\/revisions\/6460"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6459"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6459"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6459"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}