Newsletter sign-up
View all newsletters

Enterprise Java Newsletter
Stay up to date on the latest tutorials and Java community news posted on JavaWorld

Sponsored Links

Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs

JavaWorld.com > Java Development Tools >

Tools of the trade, Part 3

Install your Java programs with InstallAnywhere

By Jeff Friesen, JavaWorld.com, 01/03/03

  • Print
  • Feedback

Page 4 of 6

Figure 3. The Add Files window displays all of the Lines application's classfiles

Click the Next button on the Add Files window and the Choose Main window appears. Use that window to identify the classfile that specifies the byte code equivalent of a main(String []args) method. (Do not identify a classfile if you are creating an installer for a non-Java application.) For Lines, click the Automatically Find Main Classes button. In response, InstallAnywhere displays Lines in the Main Class (Full Package Name) text field. Although the Choose Main window also lets us choose appropriate icons for a LaunchAnywhere-created program that runs the Java application, I chose to keep the default icon.

Click the Next button on the Choose Main window and the Set Classpath window appears. Use that window to select an appropriate classpath for a Java application's various class and jar files. Either manually select those items or click the Automatically Set Classpath button to have InstallAnywhere perform that task automatically. For our Lines application, I chose to click Automatically Set Classpath.

Click the Next button on the Set Classpath window and the Build Installer window appears. Use that window to select all platforms (with or without a virtual machine) for which you want to build an installer. As Figure 4 illustrates, I chose Windows without a virtual machine because Java is present on my platform.

Figure 4. Use the Build Installer window to select all platforms for which you want to build an installer. A separate installer builds for each platform.

After choosing the appropriate platform(s), click the Build button to build the installer(s). A Building dialog box tracks the progress of various building activities. Once those activities finish, Building disappears and a Try Installer window appears.

On my platform, the Try Installer window reveals C:\projects\Lines\Lines_Build_Output\Web_Installers as the location of an HTML file from which I can run my Windows/no virtual machine GLA.EXE installer. Furthermore, that window reveals C:\projects\Lines\Lines.iap_xml as the location and name of the project file, and a Try It button to try out the installer.

Click the Try It button to run the installer. My Windows-based GLA.EXE installer displays various windows that reveal installation information and prompt for user input. For example, the Choose Shortcut Folder window prompts me for instructions on where to create product icons. (I chose to keep the In A New Program Group setting.) Figure 5 illustrates the Choose Shortcut Folder window.

Figure 5. The Choose Shortcut Folder window is one of several installer windows that appear during installation. Click on thumbnail to view full-size image.

Once installation completes, my Windows Start menu presents a Graphical Lines Application program group with a single Lines entry. Furthermore, my c:\Program Files\GLA install folder reveals the following file and folders:

  • UninstallerData
  • lax.jar
  • Lines.exe
  • Lines.lax
  • Context.class
  • Lines.class
  • Lines.class
  • Stub.class


The UninstallerData folder provides a program and files for removing the Lines application from the Windows platform. Select Lines from the Start menu's Graphical Lines Application program group to launch Lines.exe. That program works in partnership with Lines.lax to run the Lines application, whose four classfiles appear in the same folder.

  • Print
  • Feedback

Resources