Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note

This article describes how to upgrade PRIME. To read about how to upgrade Smart ID Identity Manager, see Upgrade Smart ID.

...

Expand
titleReplace .war files

To replace the .war files:

  1. Stop the Tomcat service.
  2. Delete the following subfolders:
    ▪ prime_designer
    ▪ prime_explorer
    ▪ prime_tenant
    ▪ ussp
  3. Copy all the provided .war files into the webapps subfolder of the Tomcat installation directory:
    ▪ prime_designer.war
    ▪ prime_explorer.war
    ▪ prime_tenant.war
    ▪ ussp.war
    ▪ plus any other provided .war file

  4. Open the Tomcat properties via the Tomcat Icon in that System Tray or in the Windows Services.

  5. In the General tab, verify the information and set Startup type to Automatic. Click Start.

    The Tomcat server is started and unzips the .war files into the new folders:
    ▪ prime_designer
    ▪ prime_explorer
    ▪ prime_tenant
    ▪ ussp

    This process usually takes a few minutes.

...

Note that the server on which these scripts are run requires access to the database server. If the script is run on the application server, this should not be a problem because the connection is also needed at runtime.

  • After successful execution, the following message is displayed on the console:
    Liquibase Update Successful
  • Restart Tomcat to establish the database connection. 
  • Expand
    titleUpdate database

    Identity Manager uses a tool called Liquibase to update the database. This allows database changes to be made independently of the underlying database type, therefore making it easy to maintain the database schema for different databases with maximum flexibility.

    To update the database:

    1. Stop the Tomcat service:
      In the General tab, click Stop.

    2. Open the following file:
      update_db.bat, in the delivery directory db_update

    3. Adjust the URL, USER, and PASSWORD parameters to reflect the database. See Database properties file.
    4. Save the file.
    5. Run the batch file.

    Note

    ...