Packaging an Eclipse client environment for distribution

The Eclipse SDK, on which the Rational® SDP is based, provides the ability to generate a complete Eclipse client which includes your HATS application plug-ins and all other required plug-ins. This client can be distributed to individual client systems and run as a stand-alone application.
Note: Prior to following these instructions, it is assumed that a HATS rich client plug-in project has been created and run in the local test environment.

To create the client package, perform the following steps:

  1. In the HATS Projects view, right-click your HATS rich client project and from the pop-up menu select New HATS > Product Configuration. This launches the New Product Configuration wizard. The wizard can also be launched from the Rational SDP menu bar by selecting File > New > Other > Plug-in Development > Product Configuration > Next.
  2. Select the com.ibm.hats.rcp.runtime.extension plug-in project folder as the parent folder.
  3. Enter hostaccess.product in the File name field.
  4. Select the Use a launch configuration radio button and select hostaccess.
    Note: In this example, hostaccess is the default name used for the Run, or Debug, configuration you used when you tested your application in the local test environment.
  5. Click Finish.
  6. Click the Overview tab and click the Eclipse Product export wizard link.
  7. Under Destination, in the Directory field, enter the name of the directory to export the Eclipse product to. For example c:\hostaccess. Alternatively, you can select to export to an archive (.zip) file which is useful when you want to make the client package available as a one file download.
  8. Under Export Options, clear Generate metadata repository.
  9. Click Finish.

A complete Eclipse client environment is created. To test your application, use Windows Explorer to navigate to the c:\hostaccess directory. From the eclipse folder double-click eclipse.exe. This directory can be zipped up and downloaded to individual client machines. All that is required on the client system is a compatible Java™ Runtime Environment (JRE).

Parent topic: Deploying HATS rich client applications