|
Home > Archive > WebSphere Portal Server > January 2004 > Re: Can I deploy a normal servlet/EJB to the Portal Server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Can I deploy a normal servlet/EJB to the Portal Server
|
|
| machron1 2004-01-19, 3:02 pm |
| The behavior for this is very odd indeed. We found we had to start the stand alone WAS and use the admin screen. You'll notice you will have 2 servers (server1 and wps, forget the exact name it gives it). Anyway, we just deployed the EJB using the WAS
admin screen ensuring it was made available to BOTH server1 and wps. After this, the EJB is accessible to wps/portlets even if you do not start WPS seperately. The EJB is available by just using its JNDI name, no port information or anything. IBM it se
ems is doing some magical mystical things behind the scenes.
| |
| Scott A. Roehrig 2004-01-19, 3:02 pm |
| The EJB is bound into the NameSpace for the Node more than likely. This
would make it available to both. Anyways, you can use the Admin app for WPS
to register the EJB with the Portal server instance alone. This should make
it availble via WPS app and other apps running on the WPS instance.
Scott
"machron1" <ryankennedy@freightliner.com> wrote in message
news:1764749101.1074190579462.JavaMail.wasadmin@swg3ws006...quote:
> The behavior for this is very odd indeed. We found we had to start the
stand alone WAS and use the admin screen. You'll notice you will have 2
servers (server1 and wps, forget the exact name it gives it). Anyway, we
just deployed the EJB using the WAS admin screen ensuring it was made
available to BOTH server1 and wps. After this, the EJB is accessible to
wps/portlets even if you do not start WPS seperately. The EJB is available
by just using its JNDI name, no port information or anything. IBM it seems
is doing some magical mystical things behind the scenes.
|
|
|
|
|