Installing the application/web server - AcceleratorKMS - Version 3.12 - Installation & Upgrade - Hexagon

AcceleratorKMS Installation and Configuration

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

Install and configure the application/web server to use AcceleratorKMS.

Before you begin

  • Ensure the application/web server meets the minimum hardware and software requirements.

  • Know the parameters for the database connection string.

  • Ensure you have the zip archive that contains the AcceleratorKMS software.

When PDFs are generated, times are based on the same time zone set for the application server. It is recommended that application servers are set to UTC time zone and that the selected time zone is added to the OutputControlMessageTemplate configuration key.

For example, "Printed on {0}. All times are UTC. If using a printed version, it must match the controlled version in AcceleratorKMS."

About this task

This server stores all AcceleratorKMS application files and services.

Procedure

  1. Add Web Server IIS role using the following specifications:

    • In addition to the default features, select all features in Common HTTP Features, Application Development, and Security.

    • After installation completes, remove all files from c:\inetpub\wwwroot

  2. In the IIS Manager, configure your website basic settings to use the following:

    • Application Pool with .Net CLR Version 4.0

    • Integrated Managed Pipeline Mode

  3. On the administrative command prompt, configure PowerShell.

    Powershell
    Set-ExecutionPolicy RemoteSigned

Install and deploy AcceleratorKMS software

  1. If the zip is blocked by Windows because it was downloaded from an internet location, then right-click the zip, select Properties > Unblock > OK.

  2. Extract all contents of the zip to a temporary folder.

  3. Verify SOLR is installed. If it is not, then install using SOLR installation (see SOLR™ installation).

  4. Using an Administrator Command Prompt, navigate to the temporary folder and execute the deploy.bat file.

    • For multiple instances of AcceleratorKMS when installed on the same server - The deployment process prompts for an Application folder name. For single instance installation - Press Enter to accept the default (none).

    • During first-time installations or when the deployment process is unable to locate an existing connection string in the target location, you are required to enter database connection details.

  5. Delete the temporary folder.

  6. Edit security on the PDF converter folder to add modify permissions for IIS_IUSRS and NETWORK SERVICE.

    The PDF converter folder is typically configured as c:\inetpub\wwwroot\pdfconverter.

  7. Edit security on the export output folder to add modify permissions for IIS_IUSRS and NETWORK SERVICE.

    The export output folder is defined in the OutputDirectory configuration key and typically configured as c:\inetpub\wwwroot\export\output. If this folder does not exist, you must create it.

Verify database connection string

  1. If you are installing a single instance of the AcceleratorKMS application, verify database connection string exists in c:\inetpub\wwwroot\web.config.

  2. If you are installing multiple instances of the AcceleratorKMS application on the same server, verify the database connection string web.config exists for each instance of the application on the same server: c:\inetpub\wwwroot\apps\<app-folder-name>\web.config

  3. Verify Procedure Accelerator Worker Service (PAWS) defines the connection string in: C:\Program Files\AcceleratorKMS\Procedure Accelerator\PAWS\PA.WorkerService.exe.config

    Servers with multiple instances of AcceleratorKMS are organized with apps folder: \PAWS\apps\<app-folder-name>\PA.Worker.Service.exe.config.

    <configuration>
    <connectionStrings>
    <add name="PAConnectionString" connectionString="Data
    Source=[sql server address];Initial Catalog=[database name];User
    ID=[sqlUsername];Password=[password];MultipleActiveResultSets=False"
    providerName="System.Data.SqlClient" />
    </connectionStrings>
    </configuration>

  4. For High Availability deployments, repeat this task for every application/web server being installed.

Results

The application/web server is ready for use.