Upgrading to a new eperi sEcure Platform WAR file

Update eperi sEcure Platform manually by deploying the WAR file on the web application server. These instructions are only relevant if you have previously deployed eperi sEcure Platform manually using the WAR file.

1. Shut down all services, including the Tomcat Server:

   ./opt/tomcat/bin/shutdown.sh

   Important: In a cluster setup, shut down every eperi sEcure Platform instance! This is very important to keep the eperi sEcure Platform and Token database consistent!
2. Change to the webapps directory of your Tomcat installation and move the ROOT directory to another place (e.g. to /opt/tomcat/ROOT.backup.20190626):

   sudo mv ROOT /opt/tomcat/ROOT.backup.20190626/

3. Backup the eperi sEcure Platform database according to the procedures defined in your company.
4. Delete the old eperi sEcure Platform WAR file from the Tomcat webapps directory.

   sudo rm /opt/tomcat/webapps/ROOT.war

5. Upload the new version of the eperi-gateway.war file to the target system.
6. Copy the new version of the eperi-gateway.war file to the Tomcat webapps directory (renamed to ROOT.war), for example:

   sudo cp /home/admin/eperi-gateway.war /opt/tomcat/webapps/ROOT.war

7. If you use or intend to use "RAM password" as Master Key method, modify the Tomcat startup script, so that the RAM password is prompted on startup. For example:

   EPERIMASTERKEY=$(systemd-ask-password "Please enter eperi Master Key: ")
   export EPERIMASTERKEY
   ;start tomcat now

8. Start the Tomcat Server, for example:

   ./opt/tomcat/bin/startup.sh

   The new version of eperi sEcure Platform is deployed and started on the Tomcat Server.
9. Stop the Tomcat Server, for example:

   ./opt/tomcat/bin/shutdown.sh

10. Copy the following files from the backup directory:
    1. The file connector.properties:

       sudo cp /opt/tomcat/ROOT.backup.20190626/ROOT/connector.properties \
       /opt/tomcat/webapps/ROOT/

    2. The license file product.lic:

       sudo cp /opt/tomcat/ROOT.backup.20190626/ROOT/etc/product.lic \
       /opt/tomcat/webapps/ROOT/etc/

    3. The file database.conf:

       sudo cp /opt/tomcat/ROOT.backup.20190626/etc/database.conf /opt/tomcat/webapps/ROOT/etc/

11. If applicable, copy the new version of the Adapter file (e.g. ca.salesforce-19.9.1.0.jar) for your respective SaaS application (e.g. Salesforce) to the Tomcat WEB-INF/lib directory. For example:

    sudo cp /home/admin/ca.salesforce-19.9.1.0.jar /opt/tomcat/webapps/ROOT/WEB-INF/lib

12. Copy additional JAR files needed for the appropriate Adapter into the .../WEB-INF/lib directory. In case of the Salesforce Adapter, these are, for example, the following files:
    • rhino-1.7R4.jar
    • super-csv-2.4.0.jar
13. Start the Tomcat Server, for example:

    ./opt/tomcat/bin/startup.sh

14. Log in to the eperi sEcure Admin Console.
15. Go to Settings > License and check that the license is all right.