Avatar billede fredand Forsker
05. februar 2006 - 10:54 Der er 6 kommentarer og
1 løsning

How to set up JMS between 2 different servers?

Hello!

I'm trying to set up a WebLogic and a WebSphere for JMS communication.

So far I'm just trying on the WebLogic to an other WebLogic on 2 different machines.

In a JSP-page I'm trying to set up the different properties in a Properties object, like this:

java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://localhost:7001/
java.naming.security.principal=weblogic
java.naming.security.credentials=weblogic

Then i load the context like:
jndiContext = new InitialContext(properties);

This works fine from a stand-alone app, if I change the java.naming.provider.url to an other machine it works fine.

But in a JSP-page it doesn't seems to a work. I do not got any error but I only connect to the locale machine even if I try with an other url value at the java.naming.provider.url.

So if any one know how to point the context to an other url please let me know.

Best regards
Fredrik
Avatar billede arne_v Ekspert
05. februar 2006 - 15:40 #1
are you sure that you get it loaded correctly ?

BTW, it is very unusual to use another JNDI tree than the app server
you are running on - why do you want that ?
Avatar billede fredand Forsker
05. februar 2006 - 20:09 #2
Hello!

The scenario is that the customer has got 2 platforms for different apps. One on WebLogic and one on WebSphere.

The Scenario is:
Some event occurs in the WebLogic app. The WebSphere app need to be notified about this. The idea then is to push a message to a JMS-queue on the WebLogic app. The WebSphere app continueosly pulls theese messages.

For this I guess that we need to set up the JMS queue on the WebLogic, add messages to this queue. In some way set up the context at the WebSphere to point to the JMS queue at WebLogic to be able to pull theese messages.

To start with we just uses 2 WebLogic apps on 2 different machines. To manualy simulate this we have set all the code in a JSP-page. But for the "pulling" side it doesn't seems to take affect when we ty to change this property:
java.naming.provider.url=t3://REMOTE_IP:7001/

Perhaps it is not allowed to change this context property?? Perhaps it belongs to the server application (WebLogic)??

We are able to set it from a standalone app.

Feel free to comment the solution idea!!

Best regards
Fredrik
Avatar billede arne_v Ekspert
05. februar 2006 - 20:21 #3
Now I am not a message queue expert but:

JMS is just an interface - there must be an implementation behind

maybe IBM MQ

I think it would make sense to use a shared message queue (obvious shared to
communicate), but declare it twice - once in WAS JNDI and once in WL JNDI and
then each app server could look it up in its own JNDI without problems


but not my area of expertise
Avatar billede arne_v Ekspert
12. marts 2006 - 05:24 #4
did you solve the problem ?
Avatar billede fredand Forsker
13. marts 2006 - 07:51 #5
Hello!
Yes we have solved it recently, I will get back with a description some time very soon I hope!

Best regards
Fredrik
Avatar billede fredand Forsker
30. december 2006 - 13:30 #6
The customer changed his mind so lets close this one!
Please give svar so I can reward you!
Avatar billede arne_v Ekspert
30. december 2006 - 16:10 #7
ok
Avatar billede Ny bruger Nybegynder

Din løsning...

Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.

Loading billede Opret Preview
Kategori
Kurser inden for grundlæggende programmering

Log ind eller opret profil

Hov!

For at kunne deltage på Computerworld Eksperten skal du være logget ind.

Det er heldigvis nemt at oprette en bruger: Det tager to minutter og du kan vælge at bruge enten e-mail, Facebook eller Google som login.

Du kan også logge ind via nedenstående tjenester