Installing multiple 3DPassport instances in load balancer environment

When installing multiple 3DPassport instances in load balancer environment, 3DPassport instances can be installed in several hosts by this method. In all these multiple 3DPassport installations: the installation directory path, database details and all other installation inputs must be the same.

Note:
  • TomEE port can be different for multiple instances.
  • You need to perform this task each time you need to install a Hot Fix to keep your second instance.

  1. Install 3DPassport R2022x GA level in default password encryption mode in 3DPassport_host1.
    An encryption key is generated in:

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

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

  2. Copy the cipher key from 3DPassport installation in 3DPassport_host1 to 3DPassport_host2.
  3. In 3DPassport_host2, export the cypher key and install 3DPassport GA in the same console:

    set X3DPASS_EKEY_PATH=<full_cipher key path> (Windows)

    export X3DPASS_EKEY_PATH=<full_cipher key path> (Linux)

  4. Install the 3DPassport R2022x Hot Fix in server 3DPassport_host1.
  5. Following the example of GA, export the cipher key in 3DPassport_host2 and install 3DPassport HF.

    3DPassport first instance will be available in 3DPassport_host1 and the second instance will be available in 3DPassport_host2

    If the admin disabled the encryption during first 3DPassport instance installation, then you do not need to export X3DPASS_EKEY_PATH variable in the second instance installation.