I have been using Glassfish for almost a year. I have done some basic
things with the JMS. I've been asked (really told) to integrate
Glassfish with the company's MQ backbone. I know nothing about MQ Series
or Websphere. Our Websphere/MQ site is supported by a beauracratic IM
organization. As such, I am having a lot of difficulties understanding
the steps listed in the MQ series integration guide. Hopefully I can get
some answers to my questions about the guide.
The group has created 2 test queues for me to work with. Before
attempting this integration, I have used the Java for MQ client to
validate access and working of the test queues. I have also installed
and used the IH03 client to use as a debugging tool.
Configuration info
Websphere, MQ, and Glassfish all running on separate servers
MQ series 6.x
Glassfish sever
Lintel
Red Hat Linux
V1 build 48
Initial Setup
A series of MQ jars are added to the Glassfish server's classpath. All
but one of these jars are available in the Java for MQ client download.
One is com.ibm.mqetclient.jar. This is not a client jar, it is a
websphere jar. I'm getting flack from the Websphere group for needing a
server jar. Could you summarize why the jar is needed?
You ask for a modification of LD_LIBRARY_PATH. You do not specify the
DLL equivalents required. I need to request these from the MQ group.
Could you enumerate them please?
Configuring the Resource Adapter
I'm assuming I need to replace
java.naming.provider.url\\=file\\:\\/\\/opt\\/tmp with the URL/port to
the Q Manager?
UserName=mqm:Password=###: You're not saying that I need the su for the
MQ server are you? If you are, could you provide me some explanation
that I could use with the IM group? If not, what are you referring to?
How do I specify the remote JNDI resource needed to look up the remote
Q's? Or does specifying a path to the Q manager sufficient?
Thanks
Ron Rockwell
Xerox