Deployment Wizard

The Deployment Wizard bundles together a set of files and packages that constitute an image of an application or applet that can be run. The Deployment Wizard enables you to easily distribute JavaBeans to other users.

To open the Deployment Wizard:

  1. Open the project you wish to deploy.
  2. Compile your project to create the class files.
  3. Choose Wizards|Deployment Wizard.

Note: The Deployment Wizard always uses the most recently built .class files, but does not check to see if the .class files are up to date. If you have made changes to your source, be sure to compile your project again before running the Deployment Wizard.

See also:
User's Guide: Deploying Java programs

The Deployment Wizard contains the following fields:

Select Files to Deploy

The Deployment Wizard is project-based. All files that are needed as part of a deployment must be referenced in the project either indirectly (such as classes in .java files) or directly in the project. All files that are needed in the deployment that are not .java or .class files must be explicitly referenced in the project. For example, you need to explicitly add to the project any other files you wish to deploy, such as resources (.gif, .jpeg, and audio files), property files, or archived documentation (.html, readme.txt, and so on).

By default, all files and packages in a project are selected to be deployed. The list box supports multiple selection.

Note: If the project to be deployed has a package or a folder in it, you can only select or deselect the entire package or folder for deployment.

The Deployment Wizard places all selected files for deployment (regardless of the file extension) in an archive file. The wizard does not filter out what files to include in the archive. The wizard doesn't check to make sure that the archive contains a complete set of files needed to deploy a specific application or applet.

The Deployment Wizard will not deploy the JDK. The JDK is part of the Java VM and, thus, never should need to be deployed. The Deployment Wizard does not include any class files from the JDK. The JDK is contained in the Java, Sun packages.

Dependency Options

The Deploy Dependencies checkbox controls whether any .class files on which the deployment files are dependent are included in the archive. You can further refine what dependency files are included in the archive by checking which dependency files to include.

The Deployment Wizard contains the following dependency checkboxes:

Include JBCL - When this option is checked, the Borland JBCL class files upon which the deployment files are dependent will be included in the archive. You should select Include JBCL when you do not know if the target system for deployment already has JBCL classes installed.

Include JGL - When this option is checked, the Java Generic Library (JGL) class files upon which the deployment files are dependent will be included in the archive. You should select Include JGL when you do not know if the target system for deployment already has JGL classes installed.

Include All Others - When this option is checked, all other classes (besides JBCL, JGL, and AS/400 Toolbox for Java) upon which the deployment files are dependent are included in the archive.

Delivery Options

The Deployment Wizard supports the zip and JAR archive formats. Within those two formats, you can also choose between having a compressed or an uncompressed archive generated.

No Archive Copies all the specified files to the Archive Output Path such that package paths are created and files are placed in the correct locations relative to the Archive Output Path and their package. For example if the Archive Output Path is d:\applets and the file dog.class is in the package of animal.fourlegged, the file would be placed in the path: d:\applets\animal\fourlegged\dog.class.
Zip Writes an uncompressed zip file using the file name specified in the Archive Output Path.
JAR Writes an uncompressed JAR file using the file name specified in the Archive Output Path. If you do not have a manifest file specified in the deployment list, a manifest will be created and installed in the JAR. Use uncompressed files for applications.
Compressed Writes a compressed JAR file using the file name specified in the Archive Output Path. If you do not have a manifest file specified in the deployment list, a manifest will be created and installed in the JAR. Use compressed files for applets.
Manifest File If the JAR archive format and <Auto Generated> are selected, the Deployment Wizard will generate a manifest file and include it in the resultant .jar file in a \meta-inf subdirectory (\META-INF\MANIFEST.MF). If other manifest files (.mf) are part of the project, they will appear in the drop-down choice. If selected, the Deployment Wizard will place a copy of the selected file in META-INF\MANIFEST.MF in the .jar file.

Archive Output Path

The fully qualified path and file name for the archive to be generated by the Deployment Wizard. You can use the Browse button to browse to a different directory location.

The extension of the file in the Archive Output Path and the Delivery Option archive type must be in sync. The extension for the archive must be either .jar or .zip.

Browse

This button enables you to locate and select the Archive Output Path using a Filer dialog, rather than typing in the text box.

Finish

When you click the Finish button, the wizard attempts to create the archive file based on the settings in the dialog. If successful, the archive will be created and the Deployment Wizard will exit. If not successful, an error message will be displayed and the Deployment Wizard will re-appear.