Originally posted by: paul.brett
Each JMS provider should adhere to the JMS standard, and yet there's always a tinge of proprietary behaviour involved that requires the 'vanilla' examples get a little colouring before they will work.
I spent a while setting up OpenMQ using the slightly older (Java 6 compatible) version 4.5.2. The following Quick Start Guide was very handy: http://docs.oracle.com/cd/E19798-01/821-1794/aeoay/index.html
The examples themselves are pretty straight forward, using adapter command line:
-ICTXFURL file:///C:/ObjectStore -ICTXF com.sun.jndi.fscontext.RefFSContextFactory -CFN MyQueueConnectionFactory -QN MyQueue -T
...and then it's only the JAR file loading that needs to be considered. I did this with edits to the dtx.ini file, adding to JAR reference to the [External Jar Files] section:
[External Jar Files]
jar1=C:\PROGRA~2\OpenMQ\mq\lib\imq.jar
jar2=C:\PROGRA~2\OpenMQ\mq\lib\jms.jar
Any questions - ask away!
Thank-you.
Paul
Follow me on Twitter
#IBMSterlingTransformationExtender#DataExchange#IBM-Websphere-Transformation-Extender