How can I communicate to EJB in another server?

Published: 08 Apr 2004

Step 2 of 2:

You forgot to provide an Email Address.

This email address doesn’t appear to be valid.

This email address is already registered. Please login.

You have exceeded the maximum character limit.

Please provide a Corporate E-mail Address.
- I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.
Please check the box if you want to proceed.
- I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.
Please check the box if you want to proceed.

I want to communicate to an EJB in another server. Since this EJB to EJB call is between servers, it is showing an error at the time of look up. My server is JBoss. I am stuck with this problem -- any advice?
One difference between accessing EJBs from local clients vs. remote clients is in the construction of the InitialContext for the bean. Remote clients typically obtain an InitialContext via an InitialContext factory, with server-specific credentials and URL, as in the following example:

   Properties props = new Properties();
   props.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,
             "weblogic.jndi.WLInitialContextFactory");
   props.put(javax.naming.Context.PROVIDER_URL, "t3://myhost:7001");
   props.put(javax.naming.Context.SECURITY_PRINCIPAL, "jdoe");
   props.put(javax.naming.Context.SECURITY_CREDENTIALS, "foobar");
   javax.naming.Context context =
      new javax.naming.InitialContext(props);
   Object homeObject = context.lookup("java:comp/env/myejb");
  
   MyEJBHome home = null;

   if (usingIIOP == true)
   {
      home = (MyEJBHome)PortableRemoteObject.narrow(homeObject,
                                                    MyEJBHome.class);
   }
   else
   {
      home = (MyEJBHome)homeObject;
   }

   MyEJB myEJB = MyEJBHome.create();

Internal clients of an EJB, such as servlets, can simply create an InitialContext using the default constructor, as shown here:

   javax.naming.Context context =
      new javax.naming.InitialContext();
   Object homeObject = context.lookup("java:comp/env/myejb");
   MyEJBHome home = (MyEJBHome)homeObject;
   MyEJB myEJB = MyEJBHome.create();

Dig Deeper on Topics Archive

Intercepting JNDI Filters This article presents a simple filtering framework to "intercept" JNDI operations and objects in a non-intrusive way (without code changes or the overhead of AOP systems).

Testing Entity Beans This section covers techniques and strategies for testing your Entity Beans. Entity Beans come with their own special considerations and issues, because in addition to the bean classes and the test cases, you must also concern yourself with generating a database.

Testing Inside the Container This article discusses how to use OpenEJB's container driven testing features to simplify and supercharge your EJB testing.

How can I access an EJB in WebSphere on one machine from a Java program on another?

How do I change a stateless session bean into a stateful session bean?

Adding functionality with email messages using struts app

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

Meet all of our Application Architecture experts

View all Application Architecture questions and answers

Please create a username to comment.

How software prototyping beats requirements gathering

5 vital QA skills for software testers

Is RPA the future of test automation?

Prepare for an AWS outage with these preventative steps

AWS seeks niche in the cloud UC market

National Australia Bank cashes in on AWS training and certification

The future of the Kubernetes ecosystem isn't all about cloud

Evaluate general and niche cloud service use cases

Compare niche cloud services to the hyperscale offerings

Don't ever put a non-Java LTS release into production

Public API strategy considerations for enterprise adoption

Ideas on how to hold a successful code hackathon

Dig Deeper on Topics Archive

Have a question for an expert?

Start the conversation

0 comments

Register

Login

Forgot your password?

Your password has been sent to:

Please create a username to comment.