This section describes how to export the Web Start application.
The following prerequisites must be met before an application can be exported for Web Start:
- The application must be structured as one or more features.
- A product configuration must be created which defines the features that make up the application along with application launch details.
Creating and editing a product configuration follows the same steps as used when exporting a client runtime image. See ../com.ibm.rcp.tools.doc.appdev/pb_creatingawedclientplatform.dita for further information.
When one or more features have been created for the application and a product configuration has been created, the application can be exported using the following steps:
- Select File -> Export.
- From the Client Services folder, select Client Services Web Start, and click Next.
- Select the product configuration for the application.
- Specify the destination directory for the export, and optionally change the application jar name.
- Optionally, provide a version specification for the target runtime. Blank (default) indicates any version.
- Indicate whether to export the common launch component. This component is required to run the application through Web Start, but a single instance of this can be deployed to the Web server and shared by multiple applications.
- Optionally, you can have the export wizard sign the common launch component. The common launch component must be signed, but you can opt to sign it after it is exported using a utility such as the Java jarsigner.
- You can select Finish to export the application using the default JNLP options, or select Next to bring up the JNLP options page, followed by the Properties page.
The exported Web Start application will be configured to use a J2SE environment matching the workspace JDK Compiler compliance level.
The default JNLP URL settings used by the export wizard will reference the application as exported to the destination directory. If you use these defaults, you can run your application directly from that directory by browsing to the main jnlp file in the directory. On Windows®, you can also double-click on the jnlp file to run the application. You must have Web Start properly installed on your development machine for this to work. See Installing Web Start support on the client
See Structure of a Client Services Web Start application
for further information on the resources that are exported to the target directory. See Deploying the application on the server
for information on how to deploy these resources on a web server.
The following table lists the JNLP options that can be specified during export. A default value of <blank> also implies that the option is not written to the JNLP file.
Table 1. JNLP options
|JNLP option||Description||Default value|
|Application codebase||URL of location containing the application jar||Export destination|
|Common launch component URL||URL of the common launch component location||Location of the common launch component in the export destination directory|
|Title||Application title||Product configuration name|
|Offline allowed||If true, Web Start is allowed to run a cached version of the application if the client is not connected to the network||true|
|Homepage||URL to a homepage containing application information||<blank>|
|Icon||URL to an application icon||<blank>|
The Web Start Export wizard Properties
page allows you to specify name and value pair properties to pass to the application. These properties are passed as Java System properties, and can be accessed by the application through the System.getProperty and System.getProperties Java APIs.
Parent topic: Deploying applications through Web Start: XPD622