So does this mean when I deploy an app onto Weblogic for instance, the web pages are served by the app server as well?
----- Original Message -----
To: glenn
Sent: Thursday, June 05, 2003 6:23 PM
Subject: RE: [EJB-INT] Separation of war and jar file to respective servers

We’ve deployed the following configuration:

  1. WAR on TomCat (JRun).
  2. EJB JAR on WebLogic.

 

Client (JSP & JSP helper classes) can obtain EJB (from WebLogic only!) in such manner:

 

Properties h = new Properties();

h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");

h.put(Context.PROVIDER_URL,  "t3://HOST:PORT" );

Context ctx =  new InitialContext(h);

obj = ctx.lookup( beanInfo.jndiName );

home = (EJBHome)PortableRemoteObject.narrow( obj , Class.forName(beanInfo.homeClassName));

 

 

Where:

  1. HOST:PORT – host name and port number where WebLogic serves EJB.
  2. beanInfo.jndiName – JNDI name of EJB (from weblogic-ejb-jar.xml). So, you should lookup from root, not from “java:comp/env” in this case.
  3. “t3://” is special protocol from BEA WebLogic only.

 

So, for WebSphere you need another approach but maybe this information helps you.

If you solve with this issue with WebSphere, please, send me details as well.

We need to do the same with WAS 5.0 in the near future.

 

Best regards,

Ihar Makushynski

 

-----Original Message-----
From: glenn [mailto:[EMAIL PROTECTED]]
Sent
:
Friday, May 30, 2003 4:58 AM
To: [EMAIL PROTECTED]
Subject: [EJB-INT] Separation of war and jar file to respective servers

 

Just wondering what the strategy is for separating war file on the webserver and ejb class on the App server.

 

I hear that the web pages can reside on the application server (particularly on Websphere) but should be deployed onto their respective servers, that is war onto web server and ejb-jar onto app server.

 

Is this the case for Weblogic ?

Do you have to stipulate that you want this arrangement or is it automatic?

What is your opinion and experiences please?

 

Regards

Glenn

 

Reply via email to