The process for updating LightWave Server from an earlier release to a later release is similar to the initial installation process. These instructions apply to 'full product' update releases. If you received a hotfix patch release, refer to the specific instructions included with the release.
Before proceeding with the update process refer to the Release Notes for important information about the current release of the software.
The software is delivered in a single PAK archive containing the following files:
SUTILITY - The LightWave Server Utility process
SUTILITY has been deprecated and will no longer be updated. LWSCOM has replaced SUTILITY as the LightWave Server management CLI.
The process is performed from a TACL prompt. These are the steps:
Product updates are available only to customers with a Support Agreement. Your product license file contains the expiration date of your Support Agreement. Each time you renew your Support Agreement, we issue you an updated license containing the new expiration date. View the contents of your product license file to ensure that your support expiration date is later than the release date of the product update you wish to install. See Product Licensing for information about the location of your product license. Contact Product Support if you have any question about your eligibility for installing updates. Regardless of your Support Agreement status, you will be able to download and install the update. However, the product will not run if your license support expiration date is earlier than the release date of the product version you are installing.
The software is distributed as a single PAK archive file. The software may be downloaded from our Software Download Center. Transfer the PAK file to your NonStop system using binary transfer mode.
Ensure that there are no active users of applications which depend on LightWave Server. From the existing LightWave Server installation subvolume, use the FILEINFO command to ensure that no files are open. Stop any processes that have files opened. From the LightWave Server installation subvolume:
> run server --shutdown <server-process-name> ! > status *, prog SERVER, stop
Verify that you have a current backup of the existing installation, including the LightWave Server filesystem (FS0* files). In the unlikely event of an unsuccessful update, you will need to restore the installation from this backup. You can use BACKUP, or use the PAK utility to perform the backup if you like. If you created the filesystem in a subvolume other than the installation subvolume, be sure to backup both subvolumes.
> PAK <pakfile>, (*), audited, listall
where <pakfile> is the name of the backup PAK archive file to be created, which should be in a separate subvolume.
We recommend that you install the update in the same subvolume as the existing installation in order to eliminate confusion over the location of the "current" version. However, it is possible (i.e. supported), to install the update into a new subvolume and even to run different versions in parallel, but bear in mind that LightWave Server filesystems (FS0* files) cannot be shared between installations.
Verify that you have the necessary permissions to overwrite the exiting files. Unpak the release package PAK archive file, overlaying the originally installed files.
> UNPAK <pakfile> ($*.*.*), vol <installation-subvolume>, myid, listall
where <pakfile> is the name of the release package PAK archive file you transferred earlier.
The LightWave Server filesystem contains information necessary to support the LightWave Server operation including API, dictionary, and service definitions you have created. The filesystem must be upgraded to incorporate any structural or content modifications included in the new release. The filesystem is upgraded using the LWSCOM program, which is run as follows:
> run LWSCOM control filesystem <filesystem-subvolume>, upgrade
where <filesystem-subvolume> is the name of the subvolume that contains the LightWave Server filesystem.
If the filesystem has an existing Console installation, then the console package file included with the new release must be installed. Install the console package as follows:
where <filesystem-subvolume> is the name of a subvolume containing an existing LightWave Server filesystem. The <console-package-file> parameter specifies the console package file included with the release in the form SCPnnnnn.
Restart the LightWave Server components as per your locally-developed procedures.