Skip to main content

How to install IBM WebSphere MQ on Ubuntu (Linux)

Following are the steps to install IBM WebSphere MQ version 8 on Ubuntu 14.04.

1) Create a user account with name "mqm" in Ubuntu. This should basically create a user called "mqm" and usergroup called "mqm"

2) Login to "mqm" user account and proceed with next steps

3) Increase the open file limit for the user "mqm" to "10240" or higher value. For this open "/etc/security/limits.conf" file and set the values as bellow.

 mqm       hard  nofile     10240
mqm       soft   nofile     10240

4) Increase the number of processes allowed for the user "mqm" to "4096" or higher value. For this open "/etc/security/limits.conf" file and set the values as bellow. You will need to edit this file as a sudo user.

mqm       hard  nproc      4096
mqm       soft   nproc      4096


5) Install "RPM" on Ubuntu if you already don't have it.

sudo apt-get install rpm  

6) Download the IBM MQ (you will get a file like WSMQ_8.0.0.4_TRIAL_LNX_ON_X86_64_.tar.gz)

7) Unzip above downloaded file. Following command will unzip the file and create a folder called "MQServer" in same location.
tar -xzvf WSMQ_8.0.0.4_TRIAL_LNX_ON_X86_64_.tar.gz

8) Go to "MQServer" folder and run following command to accept the licence

sudo ./mqlicense.sh -text_only

9) Then run following command to create unique set of packages in system (Please note that you can replace "mqmtest" part with any alphanumeric suffix if needed)

sudo ./crtmqpkg mqmtest

You will get following output once successfully run the above step in commandline.

mqm@mqm-esb:~/Downloads/MQServer$ sudo ./crtmqpkg mqmtest
Repackaging WebSphere MQ for "x86_64" using suffix "mqmtest"
###############################################################
Repackaging complete  - rpms are at "/var/tmp/mq_rpms/mqmtest/x86_64"

10) Now go to "/var/tmp/mq_rpms/mqmtest/x86_64" folder and run following command to install all components to default location "/opt/mqm/"

sudo  rpm -ivh --force-debian --ignorearch MQSeries*.rpm

11) Once above step runs successfully you have installed the WebSphere MQ and you can start to using it. You can use MQ Explorer to administrate local and remote Queue Managers  and therir resources. Go to "/opt/mqm/bin" directory and run following command to open MQExplorer.

 ./MQExplorer 


Comments

  1. UnknownJune 2, 2017 at 4:09 AM

    I am unable to edit limits.conf file with mqm user

    ReplyDelete

Post a Comment

Popular posts from this blog

Creating a Simple Axis Service(.aar file) and Deploy it in WSO2 Application Server

In this post I am explaining how to Create a Simple Axis Service(.aar file) and Deploy it in WSO2 Application Server using a simple sample. And also at the end I am describing how to do the same thing with creation of a Jar Service. Lets assume "sample-home" as our parent directory and inside that we can create following folder structure. With this folder structure we can include our external libraries (jar files) inside lib folder and  the "services.xml" file inside "META-INF" folder. Following is the sample services.xml definition which I used with this sample creation. < service name = "HelloService" > < Description > This is a sample service to explain simple aar service </ Description > < messageReceivers > < messageReceiver mep = "http://www.w3.org/2006/01/wsdl/in-out" class = "org.apache.axis2.rpc.receivers.RPCMessageReceiver" /> </ messageReceivers > < parame
1 comment
Read more

How to use Dynamic Registry Keys with WSO2 ESB Mediators

From this post I will going to briefly introduce about one of the new features provided by WSO2 ESB . Earlier WSO2 ESB supported static registry keys where users can select a key for the mediator as a static value. But from ESB 4.0.0 users can use dynamic registry keys where users can define XPath expression to evaluate the registry key in run time. For an example let's consider XSLT mediator. With earlier static registry key based method user have to define only single XSLT file for transformation. With the use of dynamic registry key, user will be able to use XPath expressions to dynamically generate the registry key, based on the message context. So with that user can have multiple XSLT files and based on the evaluated key mediator will be able to select the required XSLT file in run time. Following is a sample usage of static and dynamic registry keys and user can use both of them according to situation.   Static Registry Key – define the exact path to find the xslt fil
6 comments
Read more