Refer to the examples and default settings in this topic when defining JMS drivers.
| Driver definition |
Description |
Connection properties |
| EAServer 5.x |
The default JMS driver for EAServer 5.x servers. |
Default settings:
- Provider URL – iiop://localhost:9000
- Initial Context Factory – com.sybase.jms.InitialContextFactory
Note: EAserver 5.x uses localhost as the default hostname.
|
| EAServer 6.x |
The default JMS driver for EAServer 6.x servers.
|
Default settings:
- Provider URL – iiop://hostname:2000
- Initial Context Factory – com.sybase.jms.InitialContextFactory
Note: hostname is the actual name of the host machine on which EAServer 6.x resides.
|
| Generic JMS |
A Generic JMS driver. |
There are no defaults. |
| OpenJMS v0.7.6 |
An open source implementation of Sun Microsystem's JMS specification. |
Default settings:
- Provider URL – rmi://localhost:1099
- Initial Context Factory – org.exolab.jms.jndi.InitialContextFactory
|
| TIBCO JMS (versions 3.1.1, 4.0, and 4.1) |
Three versions of TIBCO JMS. |
Default settings are the same for all three versions:
- Provider URL – tcp://localhost:7222
- Initial Context Factory – com.tibco.tibjms.naming.TibjmsInitialContextFactory
|
| WebSphere MQ (versions 5.3 and 6.0) |
Two versions of IBM's WebSphere MQ JMS. |
Default settings are the same for both versions:
- Provider URL – file:/c:/fsjndi
- Initial Context Factory – com.sun.jndi.fscontext.RefFSContextFactory
The Provider URL identifies the path to the WebSphere MQ .bindings file that is generated when you install and configure WebSphere MQ. Depending on where you install WebSphere MQ, the type of host, wether or not WorkSpace or the Service Container are on the same host, determines what your Provider URL should be. Here are some examples of various scenarios. In each example, the .bindings file is located in the genmessage subfolder:
- For Message Transport Connection Profiles ( the connection made to the .bindings file in Enterprise Explorer):
- WorkSpace on Windows, MQ .bindings on Unix – file:////filer1/home/user1/SOLARIS/jms/genmessage
- WorkSpace on Windows, MQ .bindings on remote Windows host – file:////win2khost/myJNDI/jms/genmessage
- WorkSpace on Windows, MQ .bindings local – file:/c:/myJNDI
- For Message Service Endpoint Properties (the configuration specified in the actual service):
- Service Container on Windows, MQ .bindings local – file:/c:/myJNDI
- Service Container on Windows, MQ .bindings on UNIX – file:////filer1/home/user1/SOLARIS/jms/genmessage
- Service Container on Windows, MQ .bindings on remote Windows host – file:////win2khost/myJNDI/jms/genmessage
- Service Container on UNIX, MQ .bindings on UNIX – file:///usr/u/user1/SOLARIS/jms/genmessage
You must place the following MQ files into the <SCS install>/EAServer/lib/ext directory. - For WebShere MQ version 5.3:
- com.ibm.mq.jar
- com.ibm.mqbind.jar
- com.ibm.mqjms.jar
- fscontext.jar
- providerutil.jar
- For WebShere MQ version 6.0:
- com.ibm.mqjms.jar
- com.ibm.mq.jar
- dhbcore.jar
- j2ee.jar
- connector.jar
- fscontext.jar
- providerutil.jar
and the following MQ files into the <SCS install>/JDK1.5.0_11/jre/bin directory (for both WebSphere 5.3 and 6.0).
- If the server is on Windows:
- mqjbdf02.dll
- mqjbnd05.dll
-
MQXAi02.dll
- If the server is on Solaris:
- libmqjbdf02.so
- libmqjbnd05.so
- libMQXAi02.so
Restart the server.
|