Creating an update site

After exporting both your HATS application feature and the HATS runtime features, you must create an update site that can be used by the feature install and update process to deploy your application. To create an update site, 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 > Update Site Project. This launches the New Update Site wizard. The wizard can also be launched from the Rational® SDP menu bar by selecting File > New > Other > Plug-in Development > Update Site Project > Next.
  2. On the Update Site Project panel:
    1. Give your project a name, for example myHATSUpdateSite.
    2. Clear the Use default location check box and click Browse to locate and select the directory to where you exported your HATS application feature and the HATS runtime features, for example c:\myHATS.
    3. Click Finish.
  3. In the site.xml editor view on the Site Map tab, click New Category.
  4. In the Category Properties section:
    1. Enter a Name, for example, HATS.
    2. Enter a Label, for example, HATS.
    3. Optionally enter a Description.
    4. Click the Save icon on the Rational® SDP toolbar.
  5. In the site.xml editor view on the Site Map tab, click Add Feature.
  6. In the Feature Selection panel, scroll down and select your HATS application feature, for example hostaccess (nnnn), where nnnn represents the version number of the feature, and click OK. For more information about version numbers, see Updating plug-in and feature version numbers.
    Note:
    If you begin typing the name of a feature in the Select a feature field, the data you enter acts as a wildcard, and the list of features in the list box narrows until the desired feature is showing.
  7. Click Add Feature to add each of the HATS runtime features:
    • com.ibm.etools.terminal.beans (nnnn)
    • com.ibm.hats.core (nnnn)
    • com.ibm.hsrendering (nnnn)
    • com.ibm.iseries.wfcommon (nnnn)
    • org.eclipse.emf.ecore.sdo (nnnn)
  8. Click Build All to complete building the update site site.xml file.
    Note:
    If an error message is displayed stating that Compilation errors occurred during the build. Logs can be found in 'logs.zip' at the root of the site project., then check the logs.zip file. If it contains only warnings, you can safely ignore them and continue.

You have now created an update site, in this example c:\myHATS, including the site.xml file that indicates what features, and versions of those features, are available from the site for download by a client. You can now move this update site directory to a Web server that can be accessed by clients. For instructions on how to define an update site on the client system and install your HATS rich client applications in a runtime environment, see Installing your application in a runtime environment.

Note:
After installing a HATS service update, you should re-export and redeploy the HATS runtime features to pick up any changes. You must modify the update site's site.xml file to reflect any version number changes. The versions are listed on the first panel of the Export HATS Runtime Features wizard. For more information see Updating plug-in and feature version numbers.