JNDI lookup problem with two appservers in WSAD 4.0.3

Hi,
we have the following problem while moving our application from to WSAD 4.0.3:
We've set two appservers in WSAD and face the problem that EJB clients that are
deployed on one apperver are not able to lookup any EJBs that are deplyoed on the
other appserver in WSAD.
It's seems taht we are not able to see the reomote JNDI tree, or is there only one?
Is this a known limitation of WSAD or are we making something complete wrong?
Any help is really appreciated.
Thanks in advance,
Michel

Hi,
Could you copy-paste the lookup code and the exception being thrown. You have said that the application is being migrated to WAS 4.0.3....so i would like to know if previously also the application was running in two appserver instances??
cheers
Ramesh

Hi,

Hi, sorry pressed the button to early ;-) Yeah, this application is already running on WAS 4.0.3 with
two different appservers. But we developed until now with VAJ 4.0 and try now to migrate that stuff to WSAD.
Code phrase for the lookup:
1) lookup code phrase in the factory:
Object homeObject=initContext.lookup(jndiName);
with the variable jndi name defined as
"RemoteBDAPISession"

2) and then we get the following exception:
javax.naming.NameNotFoundException: RemoteBDAPISession

The same code works when we try the lookup from the appserver where the EJB is deployed, i.e. when the EJB
client is installed on the same appserver.
Thanks in advance.
Michel