Hello, Legolas.
Start with the documentation on the GlassFish documentation site. In particular, look at the Developer's Guide in the Developing Java Clients section:
https://glassfish.dev.java.net/nonav/javaee5/docs/AS91DG.pdf
You start by deploying the app containing the app client to the server. From there you have two approaches you can follow.
In one you run a script (package-appclient) on the server that packages up the app client with the required bits from the GlassFish distribution into a JAR file. You transport that JAR file to each end-user system that needs to run your client, then you expand the JAR and set up a script or a desktop icon to run a script that launches the app client.
The second approach is probably better for your situation, especially for a large number of end-user systems. You can use the built-in support for launching app clients using Java Web Start. In this approach you do not need to run the package-appclient script on the server and you do not need to manually transport anything to the end-user systems. Instead, you can send your end-users a URL in an e-mail message, or place a link on a web page in your application. When users click on the link, GlassFish and Java Web Start combine to deliver the required bits to that user's system and launch the app client automatically.
You do not need to do anything differently when you develop or deploy your application. This feature is there automatically for every app that contains an app client.
You can also read more in my blog
http://blogs.sun.com/quinn and in an upcoming article to be published on the java.sun.com website.
Please use those resources and if you have more questions please post them here.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=213925