Upgrading a Basic model - AcceleratorKMS - Version 3.12 - Installation & Upgrade - Hexagon

AcceleratorKMS Installation and Configuration
Language
English
Product
AcceleratorKMS
Search by Category
Installation & Upgrade
AcceleratorKMS Version
3.12

Before you begin

  • Installed hardware and software meet the current requirements.

  • A current backup of application database has been created for recovery purposes, if necessary.

  • The upgrade software is unzipped to a temporary folder on the application/web server and ready for deployment. If the zip is blocked, then right-click the zip, select Properties > Unblock > OK.

  • The machine name or IP address for every application/web server is known.

  • Before running the deployment batch file, remove the cassette folder found under the App_Data folder. By default, the App_Data folder is located here: C:\inetpub\wwwroot\. If you have installed the application files in another location, refer to that location instead.

About this task

When a new version of AcceleratorKMS is released, you must upgrade your application/web servers with the new software to take advantage of the latest changes.

Procedure

  1. On the application/web server, run the deploy.bat file from the temporary folder.

  2. If a 'CUSTOMERNAME-Customizations-Release1.0.sql ' script is provided in the upgrade package, launch it against the database using SQL Server® Management Studio.

  3. If a 'CUSTOMERNAME-SOLR-Customizations-Release1.0.txt ' script is provided in the upgrade package, perform the following tasks:

    • Before attempting this step, back up the existing schema files in a safe location in case you need to revert if the change(s) do not deploy successfully.

      • <solr deployment directory> by default c:\solr

      • backup Akms_Content Schema <solr deployment directory>\server\solr\Akms_Content\conf\managed-schema

      • backup Akms_Statements Schema <solr deployment directory>\server\solr\Akms_Statements\conf\managed-schema

    • AcceleratorKMS has an Akms_Statements and an Akms_Content index. The above mentioned file, CUSTOMERNAME-SOLR-Customizations-Release1.0.txt , will include changes to either or both of these index configuration sets. This is a manual step. The file will indicate which schema needs to be altered and what line(s) need to be added to the file and where. After the file has been altered and saved, the SOLR service needs to be restarted.

    • Each affected index needs to be cleared by running the following command in a browser with access to the solr index. You may execute both statements as the deployment will rebuild both indexes.

      • If altering the Akms_Content index, execute this in a browser: http://localhost:8983/solr/Akms_Content/update?stream.body=<delete><query>*:*</query></delete>&commit=true

      • If altering the Akms_Statements index, execute this in a browser: http://localhost:8983/solr/Akms_Statements/update?stream.body=<delete><query>*:*</query></delete>&commit=true

    The value of maxRequestLength in the web.config file will be reset to 100000. If this figure is smaller than your original value (assuming you previously altered it), reset this value prior to testing your environment after the upgrade. An IIS restart is also required to complete this change.

  4. Verify the server is running using the following Heartbeat test:

    • https://<Server-URL>/Home/SystemStatus

    Where <Server-URL> is the fully qualified domain name (FQDN).

  5. Use the FQDN to eliminate any software connection issues when using SSL.

Results

AcceleratorKMS is upgraded and ready for use.