Upgrading 3DPassport

This section describes how to upgrade to the latest 3DPassport level.

When upgrading an encrypted 3DPassport, before a GA or HF installation, you must set the following variable: X3DPASS_EKEY_PATH.

Note: If you are installing a HF following the installation of GA release and if you are using embedded TomEE server or an external TomEE that is already running after installation of GA, make sure that the 3DPassport application has been deployed and is running. You need to open the main URL of the 3DPassport application to perform this check.

If the production environment has multiple instances of 3DPassport, upgrade one instance at a time.

  1. If you are upgrading from an R2016x release or higher, with encrypted installation, to R2022x (GA or HF), copy the cipher file:

    <3DPassportInstallPath>\win_b64\3dpass.cypher (Windows)

    <3DPassportInstallPath>/linux_a64/3dpass.cypher (Linux)

  2. Uninstall the previous 3DPassport level.
  3. Export the following variable before upgrading to R2022x

    X3DPASS_EKEY_PATH= <full_cipher key path>

    where full_cipher key path is the full path of the cipher file.

  4. Reinstall the latest 3DPassport level.

    During the installation, when you are prompted to select the database, specify the parameters of the previous database.

    Note: If the 3DPassport database to be upgraded is imported from another database instance (for example using the Oracle expdp/impdp tools), then after installation you need to run the command updateDatabaseProperties_3dpassport (.sh or .bat) documented in Updating 3DPassport Database Properties. The script will correct the JDBC URL in the database.