Client - Server Deployment

Question

Good day everyone!
I've got this scenario hoping some kind souls will spend some time explaining in details the steps for achieving it.
1) I've got a J2EE server running in Machine A. (Server)
2) Machine B, C, D does NOT have j2ee installed, they only runs on jdk. (Clients)
3) I've created 3 different application clients for use with the 3 machines
4) I've successfully ran the 3 different application clients on the (Server) locally using runclient.bat
5) Now I need to provide, a direct and simple deployment for all the clients that does not have j2ee installed.
Question:
1) How do I create a .bat or .sh file for the clients to execute the application?
2) What are ALL the necessary .jar files to be included, eg. SimpleAppClient.jar returned after server deployment, j2ee.jar and what else??????
3) What are the necessary config files to be transferred?
Thanks.

Answer 1

A relevant answer stolen from the [email protected] mailing list:
Date: Mon, 25 Oct 1999 15:57:50 -0700
From: Kenneth Saks <[email protected]>
Subject: Re: connecting to a remote EJB
Ron, "have I got a deal for you!!! ..." It's a new component type called an
Application Client that was created specifically to address j2ee CLIENT
portability. You can get details on it in the J2EE and EJB specs. (
http://java.sun.com/j2ee/docs.html )
Basically, it's similar to a normal client except that your "public static
void main(String args[])" method is invoked from a container. The application
client container is similar to the containers for ejb components and web
components, but has fewer responsibilities. It performs authorization and
sets up the client's environment. So, all the environment types you know and
love ( environment entries, ejb-links, resource references ) are accessed from
an application client in EXACTLY the same way as in ejbs or web components.
This means the container must support the no-arg InitialContext constructor.
Furthermore, you use the java:comp/env namespace to look up the Home interface.
E.g.
import hello*;
import javax.naming.*;
import javax.rmi.*;
public static void main(String args[]) {
Context ic = new InitialContext();
// create EJB using factory from container
// java.lang.Object objref = ic.lookup("helloApp/Hello"); // old way
java.lang.Object objref = ic.lookup("java:comp/env/MyEjbReference");
HelloHome home = (HelloHome)PortableRemoteObject.narrow(
objref, HelloHome.class);
// do something ...
So, according to the official J2EE spec, there is no such thing as a
stand-alone client. All clients are Application Clients that do Home lookups
via the ejb-link mechanism, which insulates the code from vendor-specific
differences.
Now the bad news... as far as I know, only the J2EE reference
implementation supports application clients right now. So until then, you
need to have code in your client that handles any vendor-specific
InitialContext setup. You also need to roll your own mechanism to avoid
hard-coding the JNDI names. Most j2ee products will probably still support
"stand-alone" clients in some way. However, the J2EE will not address
stand-alone client issues since it recommends Application Clients.
Hope that helps a bit. The Application Client was a relatively late
addition to J2EE. Lots of people don't know about it yet. Hope this helps.
--Ken