Installing and Configuring MQ 5.2

Resolving The Problem

Install, Configure MQ Series 5.2

The Implementation of the Adapter Startcommunicationgroup has been done in 3 steps.
Steps 1 and 2 are for Installing and Configuring the MQ 5.2
Step 3 is to configure the Startcommunication group .

Step 1. Installing the MQ 5.2 server.
Get the MQ 5.2 software - This software might not be available on the net.
If installing the software on Unix you need
Root password
mqm user created
/var/mqm file system (not a link) with minimum 40 MB disk space.

I tried to install MQ 5.2 on HP-UX but I was unable to install the software due to disk space constraints /var/mqm

I have installed the MQ 5.2 on support3-dt, which is a Win 2000 box.
Before installing please make sure you can ping the Server machine (support3-dt).

After installing MQ-5.2 Server
- Create a Queue Manager using the MQ 5.2 UI.
- Create Queues
- Start the listener cd c:\program files\IBM\MQ series\bin runmqlsr -t TCP -m <QUEUE_MANAGER>
From e.g. runmqlsr -t TCP -m queue_manager45

The Server is now ready

Step 2: Installing and Configuring the Client

- Please not run the client on the machine where you have the Yantra installation running.
- Get the ma88_sol.tar.Z file
- Ftp the file to the Server machine.
- Create mqm user
- Login as root
- gunzip the file and untar the file (tar -xvf)
- pkgadd -d.
- The package is added under /opt/mqm/java
- Give read/write and execute permissions to /opt/mqm/java
- Log out as root
- Login as mqm
- cd /opt/mqm/java
- Create a directory `jndi? under /opt/mqm/java
- Copy JmsAdmin.sh and iiop_setup to java/bin
- Open the JMSAdmin.config file
Change the following entries
Uncomment INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
If using weblogic
Uncomment
INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory<br >If using websphere

Uncomment and add the correct file path if using Weblogic
PROVIDER_URL=file:/opt/mqm/jndi( note - this is the directory created under /opt/mqm)

Uncomment and add the correct address if using websphere
PROVIDER_URL=iiop://localhost/

- Close the file
- Now open the iiop_setup file (note you can name the file with any name)
- Define the following
def qcf(Connection_factory_name[weblogic admin]) qmgr(queue_manager) transport(CLIENT) host(ip address of the MQ 5.2 server) channel(channel_name)

For e.g. def qcf(SRG_CF) qmgr(queue_manager45) transport(CLIENT) host(10.xx.xx.xxx) channel(S
YSTEM.DEF.SVRCONN)
- before running the JMSAdmin.sh make sure you have the correct classpath. Please note you need to define the correct jar file in the ClASSPATH and the jar files for Weblogic and Websphere are different.

- Next define the queues
def q(alias_queue_name) qu(queue_name) qmgr(queue_manger_name)
For e.g.
def q(Publish_Queue1) qu(Publish_Queue1) qmgr(queue_manager45)

- Run the JMSAdmin.sh
- If the file does not run for some reason
(a) check the JMSAdmin.config
(b) Check the CLASSPATH defined in the JMSAdmi.sh
(c) Check the file:/opt/mqm/jndi entry or a similar entry for Websphere.

You are done with your Step 3.

Step 3 - Configuring Yantra

1. Make a new Connection Factory in the WebLogic Server Console
2. In the Yantra Configuration
a. Create a communication group
b. Create a System under Communication group
c. Add APIs to the system.
3. When defining the communication group
a. Add the correct connection_factory_name [QFC look up]
b. Add the correct jndi file name (file:/opt/mqm/jndi) [url]
c. Add the correct initial context factory (reference - JMSAdmin.config)
4. cd $YFS_HOME/bin
5. Run the Sender.sh under $YFS_HOME/bin
This will test if the Connection between the MQ 5.2 Client and the Server are correct. You can check the MQ 5.2 queue if the message has been successfully delivered.
6. Next run the startcommunicationgroup <comm_group>