on 02-07-2014 5:52 PM
Hi,
I am using PI 7.31 single stack system.
I have a interface. IBM websphere MQ is sending data to and receiving from PI.
I have got an inbound and a outbound queue details.
Can you please let me know what settings we need to do in PI for inbound and outbound queue testing.
Rgds
Hi,
are you setting up the connection for the first time?
make sure you that you have installed drivers and there is no firewall between pi and MQ server.
give the connection details in the channel check if it is working. if you have any doubt on this please let us know.
Regards,
Muni.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
yes
i am doing the connection setup for JMS first time in SAP PI 7.31 single stack.
which driver is needed for Webspher MQ. Connection check I have done ,its working fine.I did a ping from Websphere MQ to PI server and was able to get reply.
what details i need to test communication between PI and Webspher MQ. Websphere MQ has given the queue name to PI.
Hi -
Drivers depends on the MQ version.
This node should address your queries -1086303 - XI JMS Adapter and IBM Websphere MQ: FAQ
and the blog -
U can check this reference also
Hi,
Thanks for the replies. I stil have some queries :
Do we need library com.sap.aii.adapter.lib.sda or other for Websphere MQ 6.0.2.10 and PI 7.31 ?
Where do we need to install it ?
Is library and driver different thing? If yes, which driver will be needed for it ? Where do we install it ?
After library and driver, what's the next step. I have the INBOUND queue name with me.
Rgds
Hi,
coming to your connection details check page 13 in the below document.
just select the transport protocol as websphere MQ jms provider.
you are going to need jms ip address,port number,queue manager,channel name, queue name etc.
just show the cc details to mq team they can provide all.
once done with cc settings you can monitor the channel if it is working or not.
later ask the mq team to send the message and test the same.
Regards,
Muni
Do we need library com.sap.aii.adapter.lib.sda
Yes.
Is library and driver different thing? If yes, which driver will be needed for it ? Where do we install it ?
Driver is nothing but the jar files which will enable the connection to your JMS provider.
You need to bundle those jar in the above library and deploy on PI server using "SUM" Software update manager.
After deploying the Drivers - Configure your channels and try processing messages.
Hello,
First of all, u cannot deploy JMS jar files (using com.sap.aii.adapter.lib.sda) on ur own, but certainly u can help ur BASIS team in doing it. Check this article:
Secondly, ur MQ team cannot get away by just proving u queue name, u need lot of details from them:
Field | Value |
QueueConnectionFactory Java Class | See above under SonicMQ JMS Provider. The default value for WebSphereMQ 5.3 is com.ibm.mq.jms.MQQueueConnectionFactory. |
Queue Java Class | See above under SonicMQ JMS Provider. The default value for WebSphereMQ 5.3 is com.ibm.mq.jms.MQQueue. |
IP Address or Server Name | |
Server Port | |
Queue Manager Name | Enter the display name of the queue manager. |
Channel Name | Access channel for all queues |
JMS Queue | |
Character Set ID (CCSID) of Destination | Specifies the character set for the above-specified name. This entry does not affect the character set of the transferred messages. |
Transport/Network Protocol |
The JMS adapter communicates with the MQ Series server using TCP/IP sockets.
Communication takes place using dynamic libraries (Microsoft: files with the extension .DLL; Unix: files with the extension .SO or .SL). In a 64-bit operating system, the libraries must also be 64 bit. If this is not the case, see SAP Note 790963. |
JMS-Compliant | Specify whether the receiver uses the JMS API or the WebSphereMQ API |
More Info about SUM - http://scn.sap.com/docs/DOC-48969
Hello,
>>So , I should ask basis to get com.sap.aii.adapter.lib.sda in my PI 7.31 server.
Yes, above SDA file is already there on ur PI box, ur BASIS team has to modify it according to JMS adapter jar files. Refer the SDA Maker tool to do so.
BTW, i would suggest you to cross check from ur MQ team abt the jar files
Check below note for jar files for MQ 6.0 version - i think jar files will be same for MQ 6.0.2.10
747601 - J2EE JMSAdapter: MQSeries libraries
Thanks
Amit Srivastava
Hi,
you have to bundle received jars into com.sap.aii.adapter.lib. deploy this lib file using sum tool.
Regards,
Muni.
Hello,
>>Can you please let me know how basis will install the JAR files ? Is the JAR files installation neccessary ?
Yes, it's very much necessary.
Check this note (it talks abt AXIS but applicable for JMS also) - 1028961
Thanks
Amit Srivastava
I have Websphere 6.0.2.10. I got many JAR files from "<<IBM_MQ_HOME>>/java/lib folder of Websphere MQ.
Which JAR file I have to deploy.
"<<IBM_MQ_HOME>>/java/lib - under this i have 2 folders OSGI and soap,apart from it i have few JAR files there.
Under folders OSGI and soap - we have many JAR files.
WHICH JAR FILES I should deploy using SUM. Please let me know.
The jar file names can be found in the note
Hello,
I think u are not checking replies properly
Quote from my previous reply
Check below note for jar files for MQ 6.0 version - i think jar files will be same for MQ 6.0.2.10
747601 - J2EE JMSAdapter: MQSeries libraries
Thanks
Amit Srivastava
Hi - Did you check the help documentation??
http://help.sap.com/saphelp_nwpi71/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
are you looking for anything specific??
Just to add the only difference 7.3 support topics -
Have a look at the below blogs -
Also the note - 856346 - J2EE JMS Adapter: Frequently Asked Questions (FAQ)
Message was edited by: Hareesh Gampa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.