2 Replies Latest reply on Apr 4, 2004 7:27 PM by bevynq

    comminucate to another application server.

    bevynq Newbie

      Hi Everybody,

      A situation has come up at work where we will need to be able to communicate between two application servers.

      my current gusess is it would be along the lines of create a client session bean for one server and a server session bean on the other.

      create a jndi entry in the client machine so it can see the other server.

      i have two ejbs doing this inside jboss im not sure how to move the server bean to a different application server though.

      is that the way to go??

      I have seen some documentation that relates to rmi-iiop but that doesn't seem to be appropriate for a client application server.

      a pointer in the right direction would be greatly appreciated.



        • 1. Re: comminucate to another application server.
          Erik Sliman Apprentice

          I have found that JNDI works great, so you don't need the complexity of rmi-iiop. Currently, I tested it successfully with JBoss --> JBoss and WebSphere --> JBoss, although I had to include the JBoss client jar for WebSphere.

          Basically, if your JNDI look internally was "MyApplication/MyBean", then your JNDI for remote lookup might be "jnp://remotehost:1099/MyApplication/MyBean". You can obtain any remote EJB interface this way so long as you can plug the host name or IP address for the remote server in the lookup string. I have the Web module grab this from a properties file. For EJB to EJB, you might grab the remote host or IP from a user updateable database entry.

          Let me know if you need more details.

          • 2. Re: comminucate to another application server.
            bevynq Newbie

            worked a treat.