Upgrading on Separate Portal and Database Servers (Valid for Legacy Systems)
Note: The Portal and Database components should be installed on the same server. Although the installer includes an option to install these components on two separate servers, this option exists for legacy customers, is no longer a standard supported configuration and requires the engagement of Professional Services.
The upgrade utility is designed to support installations where the Portal and Database servers are separate physical systems. To upgrade a system with this configuration the recommended approach is as follows:
1. Ensure that your current license is in compliance by running the following script before attempting to upgrade:
Linux: /opt/aptare/utils/verifylicense.sh
IMPORTANT: If you are upgrading in a split-architecture environment—that is, the Portal and database on different servers—it is particularly important that you verify that your license is in compliance, as an out-of-compliance license can result in an upgraded database, without the ability to upgrade the Portal.
2. Verify the currently running version, as identified in the version.txt file, located in:
/opt/aptare/portal/WEB-INF
3. Shut down the application on the Portal server (via /opt/aptare/bin/aptare stop).
Upon completion of the last step, the Portal restarts automatically.