WebSphere: Passing in apps server port# independent of launchClient.bat utility?

Hi,

My friend has built additional API layers on top of
getInitialContext() and getHomeInterface() that does
not permit the EJB client to specify the JNDI port
number of my apps server.  They were depending on IBM
WebSphere's launchclient.bat utility to specify the
port #.  In the launchClient.bat utility, there is an
IBM-specific switch parameter that gets passed into
the proprietary LaunchClient.bat utility.  This design
made the port # separated from the client, which still
seems like a good idea.

However, now they need to launch the EJB client
independent of WebSphere's launchclient.bat utility
while keeping their API layers.  What parameters do
they need to specify on the standard Java command line
to pass in the appropriate JNDI port # of the apps
server which they want to communicate with?  Or, how
else can they communicate with WebSphere from their
new standard EJB client to pass in this port info
using their custom API layer?  (They are not using the
default port #.)

Thanks,
Steve

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/