Installing the Database Anonymizer

How to install the eperi sEcure Anonymized Test Data on your target system.

About this task

Note: The following procedure describes the installation under Ubuntu.

Procedure

  1. If the old eperi sEcure Anonymized Test Data (release 20.6 or lower) is already installed on your system, you must delete it beforehand. Use the following commands:
    sudo systemctl stop eperi-gateway
    sudo dpkg -P eperi-adapter-testdata
  2. Option 1: To install the eperi sEcure Anonymized Test Data manually, proceed as follows:
    1. Navigate to the directory you copied the eperi sEcure Anonymized Test Data JAR file to.
    2. Copy the eperi sEcure Anonymized Test Data JAR file into the Tomcat WEB-INF/lib directory:
      sudo cp testdata.indb-<version>.jar /opt/eperi/gateway/tomcat/webapps/ROOT/WEB-INF/lib
      Important: The destination directory may be different if you have installed eperi sEcure Platform manually with the eperi-gateway.war file, for example /opt/tomcat/webapps/ROOT/WEB-INF/lib.
    3. Copy all additional JAR files provided alongside the eperi sEcure Anonymized Test Data JAR file into the .../WEB-INF/lib directory.
    4. Change to the directory to which you copied the eperi sEcure Anonymized Test Data JAR file.
    5. Check, if the user and the group of the eperi sEcure Anonymized Test Data JAR file as well as the additional JAR files is eperi.
    6. If this is not the case, change it as follows:
      sudo chown eperi:eperi testdata.indb-<version>.jar
  3. Option 2: To install the eperi sEcure Anonymized Test Data with the installation package, execute the following command:
    sudo dpkg -i eperi-adapter-testdata-db-<version>.x86_64.deb
    Note: If you are upgrading from a version without installation package, you must remove all old JAR files of the existing installation before upgrading with the installation package!
  4. Restart the eperi sEcure Platform services:
    sudo service eperi-gateway restart
    Important: In a cluster setup, the changes must be made on every eperi sEcure Platform instance and each eperi sEcure Platform instance must be restarted.