Create a JMS client.
Next, configure a JMS resource on the Enterprise Server.
For information on configuring JMS resources, see Creating JMS Resources: Destinations and Connection Factories.
Define the @Resource or @Resources annotations or the resource-ref elements in the application-client.xml file. Define the corresponding resource-ref elements in the sun-application-client.xml file.
For more information on the sun-application-client.xml file, see The sun-application-client.xml file in Sun GlassFish Enterprise Server v3 Application Deployment Guide. For a general explanation of how to map JNDI names using reference elements, see Mapping References.
Ensure that the client JAR file includes the following files:
A Java class to access the resource.
application-client.xml - (optional) Java EE application client deployment descriptor.
sun-application-client.xml - (optional) Enterprise Server specific client deployment descriptor. For information on the sun-application-client.xml file, see The sun-application-client.xml file in Sun GlassFish Enterprise Server v3 Application Deployment Guide.
The MANIFEST.MF file. This file contains a reference to the main class, which states the complete package prefix and class name of the Java client.
Prepare the client machine. This step is not needed for Java Web Start.
If you are using the appclient script, package the Enterprise Server system files required to launch application clients on remote systems using the package-appclient script, then retrieve the application client itself using the asadmin get-client-stubs command.
For more information, see Using the package-appclient Script and the Sun GlassFish Enterprise Server v3 Reference Manual.
Run the application client.