Configuring the IBM WebSphere MQ Series Client v5.3 to work with ...

groupertomatoInternet και Εφαρμογές Web

30 Ιουλ 2012 (πριν από 5 χρόνια και 1 μήνα)

437 εμφανίσεις

Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 1 of 1
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved
Supported Version: Oracle BAM 10.1.3 and IBM WebSphere MQ Client v5.3.
This document refers to configuration of IBM MQ Server connection to Oracle BAM
Message Source.
Objectives:
 Understand Oracle BAM Message Sources and configuration parameters for IBM
Websphere MQ client.
 Configuring the Oracle Enterprise Message Source.
 Verify connection settings for IBM MQ Message Source.

Prerequisites:

Installed version of BAM, and completely installed version of MQ server and client
software. Install instructions for IBM MQ server and client software could change
depending on IBM Websphere versions and release notes.
User should be familiar with EnterpriseLink DesignStudio.
This document assumes the default location of IBM Websphere MQ installation path at:
C:\Program Files\IBM\WebSphere MQ.
Design details for BAM ADC Data Objects and Dashboard Reports are not included in
this document.
MQ Client Dependency and Downloads
End users are responsible for purchase and download of the server from
http://www-
306.ibm.com/software/integration/wmq/
. This is the location for version 6.0 of the server.
The instructions however refer to version 5.3.
The URL for software installation for MQ Publish\Subscribe install is
http://www-
1.ibm.com/support/docview.wss?rs=203&uid=swg24000643&loc=en_US&cs=utf-
8&lang=en
.
End users using WebSphere MQ 6.0 will not need to install MQ Publish\Subscribe.
End users using WebSphere MQ 5.3 will not need to install MQ Publish\Subscribe if they
have applied any fix pack since fix pack 8 (URL for download of the latest recommended
updates for version 5.3 is
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
)

Configuring the IBM WebSphere MQ Series Client v5.3 to
work with the Oracle BAM Enterprise Message Source

The following suggestions can be used to enable an Oracle BAM Enterprise Message
Source to exchange messages with the IBM WebSphere MQ Series Server where the MQ
Series Server is installed on a different machine than the Oracle BAM Enterprise Link.
MQ Series v5.3 has been used to develop these instructions. These instructions may
change depending on IBM Websphere release notes and available software versions.
Modifications may be needed to these examples based on the customer environment and
the version of the software products that they have installed. It should be noted that there
could be some subtle or undocumented differences between v5.3 and v6. The below
Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 2 of 2
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved
mentioned procedures have not been tested on v6, however, some suggestion for
commands on v6.0 have been mentioned whenever possible.

Setting up the server side

Step 1) Install the Server (if necessary)
If the end user has not already installed the MQ Series Server, install the server from the
WebSphere MQSeries installation CD.
Step 2) Install MQ Series Publish/Subscribe (if necessary)
If the server does not already have Publish/Subscribe capability (this is included in MQ
Series v6 and in Fix Pack 8 for MQ Series v5.3), download is available at SupportPac
MA0C for NT (ma0c_ntmq53.exe) from:
http://www-
1.ibm.com/support/docview.wss?rs=203&uid=swg24000643&loc=en_US&cs=utf-
8&lang=en

and run it to install Publish/Subscribe (NOTE: This SupportPac is no longer supported).

Step 3) Create a Queue Manager.
From the MQ bin directory (C:\Program Files\IBM\WebSphere MQ\bin), run the
command:
crtmqm QM_host/your_queue_mgr

where host is the name of the server machine (any hyphens are replaced with
underscores, for example myname-lap becomes QM_myname_lap) and your_queue_mgr
is the name you want to assign to the queue manager.

Step 4) Start the Queue Manager.
From the MQ bin directory, run:
amqmdain start QM_host/your_queue_mgr

to start the Queue Manager.
(NOTE: On v6 this command may be: amqmdain qmgr start QM_host/your_queue_mgr)

Step 5) Enable the Publish/Subscribe broker.
For v5.3, create a broker for the Queue Manager by running the following command from
the MQ bin directory:
strmqbrk -m QM_host/your_queue_mgr

and verify it is running with the command:
dspmqbrk -m QM_ host/your_queue_mgr

For v6.0, configure and start the Publish/Subscribe broker by running the following
command from the bin directory:
Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 3 of 3
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved
runmqsc QM_host/your_queue_mgr

and then issuing the following MQSC commands:
ALTER SERVICE('SYSTEM.BROKER') CONTROL(QMGR)
START SERVICE('SYSTEM.BROKER')
END

Step 6) Create the Publish/Subscribe Broker System Queues.
From the bin directory, run the command:
runmqsc QM_host/your_queue_mgr < "C:\Program Files\IBM\WebSphere
MQ\Java\bin\MQJMS_PSQ.mqsc"

Step 7) Start a TCP/IP listener for the Queue Manager.
From the bin directory, run the command:
runmqlsr -t tcp -m QM_host/your_queue_mgr -p 1414

If the server already has a listener on port 1414 (the default), you can specify another port
number. The above command executed at a command prompt will not return until you
Ctrl-C out of it. You can also start a listener by launching the:
Programs\IBM WebSphere MQ\WebSphere MQ Services
Application from the Start menu, right-clicking on the queue manager and selecting New
and then Listener.


and then specifying the port number for the listener:

Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 4 of 4
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved


Hit the OK button and then right click on the new listener and specify All Tasks and then
Start.


Setting up the client side

Step 1) If the end user’s MQ Series Server installation disk is available, install the client
from the customer’s server installation CD onto the same machine running the Oracle
BAM Enterprise Link Data Flow Server. Start the MQ Series installation, and during the
service installation, select Custom Install. Make sure that the Client and Java Messaging
options are selected and the Server and Development Toolkit features are not selected
(shown below).
Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 5 of 5
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved


If the server installation CD is not available, a free client download is available from:

http://www14.software.ibm.com/webapp/download/preconfig.jsp?id=2003-10-
23+09%3A27%3A44.107254R&cat=&fam=&s=p&S_TACT=104CBW71&S_CMP
=

Step 2) Set up to run JMSADMIN
Create the directory C:\JNDI-Directory.
Modify the file C:\Program Files\IBM\WebSphere MQ\Java\ JMSAdmin.config to
comment out the lines:
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
#PROVIDER_URL=ldap://polaris/o=ibm,c=us

and comment in (or add) the lines:
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/C:/JNDI-Directory

Step 3) Create the Topic Connection Factory.
From the C:\Program Files\IBM\WebSphere MQ\Java directory, run the command:

JMSAdmin

and enter the following commands:
DEFINE TCF(ivtTCF) QMANAGER(QM_host/your_queue_mgr) +
TRANSPORT(CLIENT) +
HOST(servermachineaddress) +
PORT(1414)

where ivtTCF is the name of the Topic Connection Factory object.
Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 6 of 6
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved
Replace servermachineaddress with the actual TCP/IP host name (do NOT replace
hyphens in the name with underscores) or TCP/IP address of the server where the listener
is running.
If you specified a port other than 1414, specify the correct port in the PORT option.

Step 4) Create the Topic.
While still in JMSAdmin, enter the following commands:

DEFINE T(ivtT) TOPIC(MQJMS/PSIVT/Information)
END

where ivtT is the name of the Topic object and MQJMS/PSIVT/Information is the topic
name.
Step 5) Create an Enterprise Message Source
The Topic Connection Factory and Topic names used above correspond to the BAM
sample data Enterprise Message Source WebSphereAllEMSTypes. If you do not have
the sample data installed, you can import the accompanying file
WebSphereAllEMSTypes.ems with the command:
iCommand cmd=import file=WebSphereAllEMSTypes.ems

You can also manually create the EMS from Oracle BAM Architect, selecting Enterprise
Message Sources in the object type drop down and specifying Create and selecting IBM
WebSphere MQ as the type of Enterprise Message Source:



Fill out the fields as follows:
Name: WebSphereAllEMSTypes
Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 7 of 7
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved
Initial Context Factory: com.sun.jndi.fscontext.RefFSContextFactory
JNDI Service Provider URL: file:/C:/JNDI-Directory
TopicConnectionFactory Name: ivtTCF
Topic Name: ivtT
JMS Message Type: MapMessage
Durable Subscriber Name (Optional): IterationFilteredSubscription
Message Selector (Optional):
Client ID (Optional): IterationFilteredClientID

and add the following fields:


and Click on “Save”
Step 6) Test the Enterprise Message Source.
Make sure that Oracle BAM Plan Monitor service is running and import the
accompanying plan files using iCommand:
iCommand cmd=import file=WebSphereAllEMSTypesPublish.plan
iCommand cmd=import file=WebSphereAllEMSTypesSubscribe.plan

Copy the file messages.csv provided in the samples to C:\temp directory.

Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 8 of 8
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved
Open an instance of Oracle BAM Enterprise Link Design Studio and log in as BAM user.
Open the Plans bin by clicking on the Plans icon in the bottom toolbar:



Drag the plan “WebSphereAllEMSTypes Publish Test Plan” and drop it onto the
workspace next to the Plans bin. Hit the Update button. If everything is set up correctly,
the plan should finish quickly with no error (the Update button will change to Stop while
the plan is running and back to Update when it is complete, and the information bar will
show “Updated” followed by how long it took the plan to run).


With the original instance of Design Studio still open, start another instance of Design
Studio and log in as the BAM user. Go to the Plans bin and drag the plan
“WebSphereAllEMSTypes Subscribe Test Plan” into the workspace. Click the update
button. While this plan is running, go back to the original instance of Design Studio and
hit the update button on the publish test plan again. Go back to the Design Studio where
the subscribe test plan is running. When the plan completes, you should see all of the
messages that were posted by the publish test plan.



Summary

At the end of this exercise, students will have completed the following sections.
Objectives:
 Understand Oracle BAM Message Sources and configuration parameters for IBM
WebSphere MQ client.
Tech Note: Oracle BAM Configuration for IBM WebSphere MQ messages
TechNote_BAM_ConfigurationForWebSphereMQClient.doc
Page 9 of 9
Aug 01, 06 (version 10.1.3)
Document version (1)
Oracle confidential, All rights reserved
 Configuring the Oracle Enterprise Message Source.
 Verify connection settings for IBM MQ Message Source.
 Testing and verifying that, MQ messages are received in the BAM EnterpriseLink
Plans.

NOTE: Details for Plan Design, Defining BAM ADC Data Objects and Dashboard
Reports is outside the scope of this document.

Questions & Clarifications:
If you have any comments or need additional information, please communicate through
the Oracle BAM forum at:
http://forums.oracle.com/forums/forum.jspa?forumID=252