Setting up JBoss 4.2.2 so MDBs can subscribe to Topic on rem

[gortman]

Hope this is the right forum for asking my question. If not, I'd appreciate it if you could point me in the right direction.

We have a an EJB3 MDB deployed to our JBoss server that needs to subscribe to a Topic on a remote WebLogic server. I'm having difficulty finding much documentation (an example would be best) of how exactly to establish the connectivity to the topic. Based on my web search it seems like I need to update jms-ds.xml, possibly jboss-service.xml, and perhaps include wlclient.jar in the JBoss classpath.

I've tried a variety of ways to make the connection so far with no success. On the JBoss wiki I found the article "HowDoIConfigureAnEJB3MDBToTalkToARemoteQueue" but that only addresses JBoss-to-JBoss. The other web search hits were mostly people asking the same question I am but with no resolution attached.

Any help you could give would be appreciated. Thanks!

[knifegun]

I have the same problem and cannot find an answer. There has to be a way.

[vickyk]

There are some scenarios which are explained for connectivity to the WebsphereMQ and similar can be tried/looked with weblogic stuff.
The simplest one is to push the messages from the weblogic messaging to Jboss Messaging queue , the Jboss Messaging Queue will have the MDB listening to the messages which come from weblogic messaging system

The similar scenario is explained over here
http://wiki.jboss.org/wiki/UsingWebSphereMQSeriesWithJBossASPartI

Some more info can be obtained from here
http://wiki.jboss.org/wiki/UsingWebSphereMQSeriesWithJBossASPart2
http://wiki.jboss.org/wiki/UsingWebSphereMQSeriesWithJBossASPart3
http://wiki.jboss.org/wiki/UsingWebSphereMQSeriesWithJBossASPart4

[gortman]

We now have the WebLogic topic messages being sent to a secured queue (one of the default queues, queue/A) on our JBoss server. However, we haven't been able to configure our EJB3 MDBs to listen to the local queue. It should be an easy thing but has turned out to be anything but. We are getting a "not bound" exception when JBoss tries to deploy the MDB to listen to queue/A.

Any tips on what the solution might be? Here are the activation configs we are using in our MDB:

@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/A"),
@ActivationConfigProperty(propertyName="userName",
propertyValue="uname"),
@ActivationConfigProperty(propertyName="password",
propertyValue="psswd"),
@ActivationConfigProperty(propertyName="providerUrl",
propertyValue="jnp://localhost:1299"),
@ActivationConfigProperty(propertyName="JmsProviderAdapterJNDI",
propertyValue="DefaultJMSProvider")

[genman]

You don't need to set the provider URL if you're connecting locally. I'm pretty sure that providerUrl and JmsProviderAdapterJNDI aren't needed.