You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 23
Next »
If an existing Smart ID Identity Manager System is being updated, re-installation of the Tomcat server (or another application server) is not usually necessary.
Only the .war files, which contain the actual program files of the program package, are replaced or installed over the existing files.
Step-by-step instruction
Backup current installation
To create a backup:
Go to the webapps folder in the Tomcat installation directory, for example:
C:/Program Files/nexus-PRIME-tomcat7/webapps/
- Back up files and folders:
- Back up all subfolders, in case something interrupts the installation.
- Make individual backups of the following configuration files:
▪ database.properties
▪ system.properties
▪ log4j.xml
from each of the following subfolders:
▪ prime_designer\WEB-INF\classes\
▪ prime_explorer\WEB-INF\classes\
▪ prime_tenant\WEB-INF\classes\ - For PRIME Self-Service, backup the following locations:
▪ ussp\WEB-INF\config.xml
▪ ussp\WEB-INF\classes\log4j.xml
▪ ussp\branding - Make individual backup of any custom beans in the following folder:
▪ prime_explorer\WEB-INF\classes\spring
Replace .war files
To replace the .war files:
- Stop the Tomcat service.
- Delete the following subfolders:
▪ prime_designer
▪ prime_explorer
▪ prime_tenant
▪ ussp 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
Open the Tomcat properties via the Tomcat Icon in that System Tray or in the Windows Services.
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.
Restore configuration files from backup
Restore the configuration files from the backup:
- Copy the following configuration files from the backup:
▪ database.properties
▪ system.properties
▪ log4j.xml
to the following subfolders:
▪ prime_designer\Web-inf\classes\
▪ prime_explorer\Web-inf\classes\
▪ prime_tenant\Web-inf\classes\ - Copy the following configuration files for PRIME Self-Service from the backup:
▪ ussp\WEB-INF\config.xml
▪ ussp\WEB-INF\classes\log4j.xml
▪ ussp\branding - Copy any custom beans from the backup to the following folder:
▪ prime_explorer\WEB-INF\classes\spring
Update 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:
Stop the Tomcat service:
In the General tab, click Stop.
Open the following file:
update_db.bat, in the delivery directory db_update
- Adjust the
URL, USER, and PASSWORD parameters to reflect the database. See Database properties file. - Save the file.
Run the batch file. 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.
Additional steps for a specific version
For upgrade from PRIME 3.11 to 3.12 click here.
