This content has been marked as final. Show 8 replies
The correct way to configure a bridge to work with foreign JMS providers is to put the foreign JMS provider client jar file in the WebLogic server's CLASSPATH.
Here is what the public doc says.
Interoperating with Foreign Providers
When configuring a messaging bridge involves interoperability with a third-party messaging provider, you must configure the following:
Before starting WebLogic Server:
Supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
Include the PATH of any native code required by the provider's client-side libraries in the WebLogic Server system PATH. (This variable may vary depending on your operating system.)
In the JMSBridgeDestination instance for the third-party messaging product being bridged, provide vendor-specific information in the following attributes:
Initial Context Factory
Connection Factory JNDI Name
Destination JNDI Name
For more details about bridge configuration, please refer to
Hope this helps.
This is the problem! I don't know how can I supply the provider's CLASSPATH in the WebLogic Server CLASSPATH. It's through the console?
Connection URL: tcp://localhost:61616
Initial Context Factory: weblogic.jndi.WLInitialContextFactory
Connection Factory JNDI Name: QueueConnectionFactory
Destination JNDI Name: msgAct
There are two ways to do that:
1. put the jar file or the path of the ActiveMQ client classes in the CLASSPATH environment variable on the window where you start the WebLogic server instance.
2. add the jar file or the path of theActiveMQ client classes in the java command line that you use to start the WebLogic server (-classpath XXXXX).
Here is a step by step guide to setting up a messaging bridge with a foreign JMS provider. This has been written using Tibco, but if you replace the Tibco components with ActiveMQ ones, the process is the same.
Edited by: EramusBlack on May 10, 2012 10:06 AM
I put the path of the ActiveMQ in the WebLogic's classpath but nothing happened! When I started the server, it appeared in the Log view:
WLS Start Mode=Development
But the messages doesn't arrive in the ActiveMQ queue!
Edited by: fe.mag on 11/05/2012 11:32
You should add the C:\apache-activemq-5.4.3\activemq-all-5.4.3.jar to commEnv.cmd