• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
  • Piet Souris
  • Himai Minh

WSAD 5.1 : J2EE application client on remote machine

Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Could any one please provide hint on how to deploy a "J2EE application client" ?

Here's what I have:
1. I used WSAD wizards to created an EJB project, with some session beans ("remote").

2. I Used WSAD wizards to create a "J2EE application client" project.
Added a "main" method that tries to obtain some service from the above-mentioned Session Bean.

3. I successfully ran the client on my local machine (so both the EJB project & the client project are running on the same WSAD ).
I used the WSAD menu option "Run as -> WAS 5 application client"

4. My question: how do you deploy that "client project" on a remote machine (so that you have machine 1 for the EJB server, and machine 2 for the client) ?
In particular:
- *where* do you tell the client what's the server URL?
- when clinet invokes "new InitialContext().lookup(MY_HOME_INTRFACE)", what context is it, and how does it find the Home that's registered (by JNDI) on another machine ?
Just the other day, I was thinking ... about this tiny ad:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earth
    Bookmark Topic Watch Topic
  • New Topic