Upgrading the Web Services Option Pack

Upgrading the Web Services Option Pack from v3.0 onwards

If you are upgrading from WSOP v3.0, you need to run dbmt upgrade first. See Upgrade.

  1. Back up the WSOP configuration and the database.

  2. Stop all instances of the Web Services Option Pack and ensure that nothing is using the database.

  3. Uninstall the currently installed version of the DBMT and install the new version (see WSOP Database Management Tool).

  4. Run migrate-schema. See Migrate schema for more information.

    The migrate-schema tool must be run before installing the latest WSOP release or migrating anything new into the database.

  5. Uninstall any currently installed versions of the Web Services Option Pack (see Uninstalling the Web Services Option Pack).

  6. Install the required version of the Web Services Option Pack (see Install the Web Services Option Pack).

  7. Start the new corecrypto service (see Start the Web Services Option Pack).

Upgrading the Web Services Option Pack from releases before v3.0

If you are upgrading from WSOP v1.0, Java is no longer required and can be removed from the system if needed.

  1. Back up the WSOP configuration.

  2. Stop all instances of the Web Services Option Pack.

  3. Uninstall the currently installed version of the DBMT and install the new version (see WSOP Database Management Tool).

  4. Run migrate. See Migration for more information.

    • The migrate tool must be run before installing the latest WSOP release.

  5. Uninstall any currently installed versions of the Web Services Option Pack (see Uninstalling the Web Services Option Pack).

  6. Install the required version of the Web Services Option Pack (see Install the Web Services Option Pack).

  7. Start the new corecrypto service (see Start the Web Services Option Pack).

As described previously, in the current WSOP release the keys and tokens are stored in a database.

Older WSOP versions (WSOP2.1 and earlier) store the keys in file in /opt/nfast/kmdata/local folder.

Before using the current WSOP release, you must migrate your kmdata folder using the Database Management Tool. See WSOP Database Management Tool for more information.

Older WSOP versions (WSOP2.1 and earlier) supported OCS-protected keys, however the current release of WSOP does not. Your OCS-protected keys will not be migrated.

The current WSOP release will install a new configuration file, which includes new configuration options. You may need to transfer some configuration options from your existing configuration. Special attention should be paid to your security configuration, including certificates and, if using an API Gateway, any other client identity information to be passed to the gateway. Configure the Web Services Option Pack describes the configuration in more detail.

For previous versions of WSOP, the configuration file was installed to /opt/nfast/wsop/corecrpto/conf/. Please note any path changes when transferring previous values to the new WSOP 3.3.1 configuration.

Once migration is completed, WSOP is ready to use.