Assemble the necessary client files.
Assemble the EJB components to be accessed by the client.
Package the client and EJB components together in an application.
Deploy the application as described in Tools for Deployment.
If you are using the appclient script to run the application client, retrieve the client JAR file.
You can use the --retrieve option to get the client JAR file.
You can also use the asadmin get-client-stubs command to retrieve the stubs and ties whether or not you requested their generation during deployment. For details, see the Sun GlassFish Enterprise Server 2.1 Reference Manual.
If you are using the appclient script to run the application client, copy the client JAR file to the client machine.
You can execute the client on the Enterprise Server machine to test it in one of the following ways:
If Java Web Start is enabled for the application client, use the Launch link on the Application Client Modules page to launch the application client using Java Web Start.
You can also use the appclient script in the as-install/bin directory to run an application client. If you are using the default server instance, the only required option is -client, which points to the client JAR file. For example:
appclient -client converterClient.jar
The -xml parameter, which specifies the location of the sun-acc.xml file, is also required if you are not using the default instance.
For more detailed information about Java Web Start, see Chapter 11, Developing Java Clients, in Sun GlassFish Enterprise Server 2.1 Developer’s Guide.
For more detailed information about the appclient script, see the Sun GlassFish Enterprise Server 2.1 Reference Manual.
For information on deploying and running an application client that connects to an EJB module on a Enterprise Server instance that is behind a firewall, see Connecting to a Remote EJB Module Through a Firewall in Sun GlassFish Enterprise Server 2.1 Developer’s Guide.