Setting Up JMS Driver Classes

Use the following procedure to set up JMS driver classes for inbound and outbound messaging transports that are dependent on external JMS databases or messaging providers.

To set up JMS driver classes:

Stop the Unwired Orchestrator server.

Locate all jar or zip files associated with the driver and DLLs if the implementation includes native code. Choose from the following driver types:

Driver Files

Driver Jar File DLL

Driver	Jar File	DLL
OpenJMS	`exolabcore-0.3.7.jar` `openjms-0.7.6.1.jar`	None
IBM WebSphere MQ JMS	`com.ibm.mq.jar` `com.ibm.mqjms.jar` For File System JNDI: `fscontext.jar` `providerutil.jar` Note If you use a JNDI other than a file system, review the JNDI product documentation to determine the files to unzip.	`mqjbdf02.dll` `mqjbnd05.dll` `MQXAi02.dll`
TIBCO JMS	`tibjmsadmin.jar` `tibjms.jar` `WORKSPACE\or50Dt\Eclipse\sybase_workspace_1.0\services\eclipse\plugins\com.sybase.stf.jmsadmin.tibco_1.0.0\tibcojmsadmin.jar`	None

OpenJMS

exolabcore-0.3.7.jar

openjms-0.7.6.1.jar

None

IBM WebSphere MQ JMS

com.ibm.mq.jar

com.ibm.mqjms.jar

For File System JNDI:

fscontext.jar

providerutil.jar

Note

If you use a JNDI other than a file system, review the JNDI product documentation to determine the files to unzip.

mqjbdf02.dll

mqjbnd05.dll

MQXAi02.dll

TIBCO JMS

tibjmsadmin.jar

tibjms.jar

WORKSPACE\or50Dt\Eclipse\sybase_workspace_1.0\services\eclipse\plugins\com.sybase.stf.jmsadmin.tibco_1.0.0\tibcojmsadmin.jar

None

Extract jar and zip files containing Java classes to the following directory:
<installation directory>\EAServer\java\classes
If the driver uses DLL files, copy the files to the following directory:
<installation directory>\ Shared\jdk1.4.2_06\jre\bin
Restart the Unwired Orchestrator server.

Driver Administration