Install Aras Innovator

The following steps described the on-premises installation of Aras Innovator. In case of a cloud availability of Aras Innovator, you can skip this section.

1. Obtain an installation package of Aras Innovator.

2. Download the Aveva.DeliverablesManagement.Server.Installer.zip package.

3. Unblock the zip file and unzip the package.

   Note: Avoid inserting spaces in the path of the unzipped package.

4. Edit the InstallInnovator.bat and update the listed components to install the clean Aras Innovator. All commands mentioned below must be performed in a Command Prompt started with administrative rights.

Install .net libraries

With following the commands, the required .NET libraries are installed. The command assumes the zip archive was unzipped into F:\ArasInnovatorR30. Update the path as needed if different.

start /w

F:\DMServer\Installables\dotnet-runtime-6.0.6-win-x64.exe /install /quiet /norestart start /w F:\DMServer\Installables\aspnetcore-runtime-6.0.6-win-x64.exe /install /quiet /norestart start /w F:\DMServer\Installables\dotnet-hosting-6.0.6-win.exe /install /quiet /norestart

Once the prerequisites are installed and the server has been configured according to the prerequisites section in this installation guide the installation of Aras Innovator can be performed as follows:

Note: The following command must be a one line. It was split into multiple lines for better readability.

start /w msiexec /i "<FolderOfInstallationFile>\InnovatorSetup.msi" /qn

/l*v "F:\DMServer\Installables\InnovatorSetup.log" MSIFASTINSTALL=1

INSTALLDIR="C:\Program Files (x86)\Aras\Innovator" WEBALIAS="InnovatorServer"

LICENSEKEY="<License lic_type=""Unlimited"" lic_key=""XXXXXX"" act_key=""YYYYYY""/>" VAULTNAME=Default VAULTSERVER_APP_URL=http://localhost/InnovatorServer/Server/InnovatorServer.aspx VAULTFOLDER="C:\Aras\Vault"

INSTALL_CONVERSION_SERVER=1

CONVERSION_SERVER_NAME=ConversionServer CONVERSION_SERVER_APP_URL=http://localhost/InnovatorServer/Server/InnovatorServer.aspx INSTALL_AGENT_SERVICE=1

AS_FOLDER="AgentService" INNOVATOR_TO_SERVICE_ADDRESS=http://localhost:8764

ARAS_AGENTSERVICE_TO_INNOVATORSERVER_URL=http://localhost/InnovatorServer/Server/InnovatorServer.aspx OAUTH_CERTIFICATES_PASSWORD=innovator

SMTPSERVER="queue" CHANGEGUID=1 INSTALL_DATABASE=1

DB_CREATE_NEW_OR_USE_EXISTING=0 IS_SQLSERVER_SERVER="(local)" IS_SQLSERVER_AUTHENTICATION=1 IS_SQLSERVER_USERNAME="sa"

IS_SQLSERVER_PASSWORD="sa-password" IS_SQLSERVER_DATABASE="InnovatorSolutions" SQL_SERVER_LOGIN_NAME="innovator" SQL_SERVER_LOGIN_PASSWORD="innovator" SQL_SERVER_LOGIN_REGULAR_NAME="innovator_regular" SQL_SERVER_LOGIN_REGULAR_PASSWORD="innovator"

INSTALLDBTYPE="InnovatorSolutions"

Notes:

The orange highlighted values are customer specific and must be changed accordingly.

The fuchsia highlighted values can be used as is and must not be changed.

Note the double quotes when specifying the license key string.

When specifying passwords for the innovator and innovator_regular SQL accounts, comply with your environment's SQL password policy.

Install AVEVA Deliverables Management customization packages to update Aras Innovator

This section describes the steps to install the AVEVA Deliverables Management add-ins to update Aras Innovator.

5. From the downloaded package, unzip the ALMDeploymentTool.zip.

6. Run the ALMDeploymentTool.exe located in the ALMDeploymentTool folder.

7. Unzip the ALM_DM_Package.zip.

8. Use "+ Add package reference" and select the ALM_DM_Package folder.

9. Select the ALM Deployment Package and select the Install link. The installation wizard starts, and some configuration settings are asked. Keep in mind that all paths must be absolute for the corresponding components and spaces in the path should be avoided. All of the following settings were asked during the Aras Innovator installation.

Configure Database Component

• SqlServer: The name of the SQL server where the Aras Innovator database is hosted.

• DatabaseName: The name of the database the customization should be deployed.

• InnovatorLogin: The SQL server login, which doesn’t have sa privileges, but has access to #DatabaseName# database. (Can be omitted if it’s an innovator)

• InnovatorPassword: The password of #InnovatorLogin#.

• InnovatorUrl: The URL to Aras Innovator application.

• PasswordOfRootInnovatorUser: The password of root user in Aras Innovator.

Configure Innovator Component

• ServerName: The name of the server where IIS is running. If #ServerName# is not localhost, then it must be in lower case.

• ApplicationPoolName: The name of the application pool running innovator (for example Aras Innovator AppPool ASP.NET Core).

• DeploymentPackageDir: The path to the folder within the deployment package.

• InstallationPath: The path to the folder where Aras Innovator is installed on the #ServerName# server (e. g. C:\Program Files (x86)\Aras\Innovator\Innovator).

• VirtualDirectoryPath: The web alias by which the component is accessible. Must begin with the '/' symbol.

Configure Vault Component

• ServerName: The name of the server where IIS is running. If #ServerName# is not localhost, then it must be in lower case.

• ApplicationPoolName: The name of the application pool running innovator (for example Aras Vault AppPool ASP.NET Core).

• InstallationPath: The path to the folder where Aras Innovator is installed on the #ServerName# server (e. g. C:\Program Files (x86)\Aras\Innovator\VaultServer).

• VirtualDirectoryPath: The web alias by which the component is accessible. Must begin with the '/' symbol.

Configure Conversion Component

• ServerName: The name of the server where IIS is running. If #ServerName# is not localhost, then it must be in lower case.

• ApplicationPoolName: The name of the application pool running innovator (for example Aras Conversion AppPool ASP.NET Core)

• DeploymentPackageDir: The path to the folder within the deployment package.

• InstallationPath: The path to the folder where Aras Innovator is installed on the #ServerName# server (e. g. C:\Program Files (x86)\Aras\Innovator\ConversionServer).

• VirtualDirectoryPath: The web alias by which the component is accessible. Must begin with the '/' symbol.

Configure Agent Component

• ServerName: The name of the server where IIS is running. If #ServerName# is not localhost, then it must be in lower case.

• DeploymentPackageDir: The path of the AgentService folder in Deployment Package.

• InstallationPath: The path to the folder where Aras Agent Service is installed on the #ServerName# server (e. g. C:\Program Files (x86)\Aras\Innovator\AgentService).

• ServiceName: The Windows service name on the #ServerName# server.

Configure OAuth Component

• ServerName: The name of the server where IIS is running.

  Note: If #ServerName# is not localhost, then it must be lowercase.

• ApplicationPoolName: The name of the application pool running innovator (for example Aras OAuth AppPool ASP.NET Core)

• DeploymentPackageDir: The path of the AgentService folder in Deployment Package.

• InstallationPath: The path to the folder where Aras Agent Service is installed on the #ServerName# server (e. g. C:\Program Files (x86)\Aras\Innovator\OAuthServer).

• VirtualDirectoryPath: The web alias by which the component is accessible. Must begin with the '/' symbol.

• InnovatorURL: The URL to Aras Innovator application (e. g. http://localhost/InnovatorServer).

Configure Scheduler Component

• ServerName: The name of the server where IIS is running.

  Note: If #ServerName# is not localhost, then it must be lowercase.

• DeploymentPackageDir: The path of the Scheduler folder in Deployment Package (can be relative to Deployment-Package-Content folder. for example .\CodeTree\Scheduler).

• InstallationPath: The path to the folder where Aras Agent Service is installed on the #ServerName# server (e. g. C:\Program Files (x86)\Aras\Innovator\Scheduler).

• ServiceName: The Windows service name on the #ServerName# server (for example InnovatorService).

• DisplayServerName: The display name of #ServiceName#. Can be same as Scheduler ServiceName (for example InnovatorService).

• StartMode: Set value to "auto".

• DoStartOnSetup: Set value to "true".

Configure ALM Component

• ServerName: The name of the server where IIS is running.

  Note: If #ServerName# is not localhost, then it must be lowercase.

• ApplicationPoolName: The name of the application pool running innovator (for example Aras ALM AppPool).

• ManagedRuntimeVersion: Set value to "v4.0".

• DeploymentPackageDir: The path of the ALM folder in Deployment Package.

• InstallationPath: The path to the folder where the ALM component is installed on the #ServerName# server (e. g. C:\Program Files (x86)\Aras\Innovator\ALM).

• VirtualDirectoryPath: The web alias by which the component is accessible. Must begin with the '/' symbol.

• TransformationFolderName: The Transformation folder name of the ALM component (for example ALM)

Select the Package to deploy

• ALM Deployment Package: To deploy the ALM changes to the Aras Innovator installation, the checkbox ALM Deployment Package must be selected.

• Sample Data: To deploy the Sample Data, the checkbox Sample Data must be selected. The Sample Data package must be available in the Deployment Package folder for this selection.

Finalize the installation

The last step in the wizard is to deploy all the necessary packages into the right folder and make the required changes in the correct places.

• To start the final deployment, press Deploy in the installation wizard.

Administrative installation of AVEVA Deliverables Management customization packages into Aras Innovator

10. Unpack Deployment-Package-Content.zip to the Deployment-Package-Content folder.

11. Ensure that path does not contain spaces. A samples folder below is used as an example.

12. Edit the InstanceTemplate.deploy.xml and update the listed components to match the target installation environment. The terms are defined above above in the Guided installation section.

Configure Database Component

Configure Innovator Component

Configure Vault Component

Configure Conversion Component

Configure Agent Component

Configure OAuth Component

Configure Scheduler Component

Configure ALM Component

Configure Setup

The Setup section specifies which component needs configuration as part of the deployment; typically, these are components come with the default Aras Innovator installation.

Configure Package

PathToDeploymentPackage: This must be configured to use an absolute path to the Deployment-Package-Content folder.

Configure Feature Licenses

FeatureLicenses: Used to automatically activate feature licenses as part of the deployment process.

Configure Sample Data

Sample Data Package can be imported as a part of Deployment. Uncommenting/Adding the below tag in apply section to import the Sample Data Package. The Sample Data package must be available in the Deployment Package folder for this procedure.

Enable HTTPS

To enable HTTPS an additional entry for all the configured components named Protocol must be added to the configuration. An example is shown below.

Apply Package

This updates the URLs to use https for the Innovator Instance, assuming that SSL certificates are already installed and a provided host is available for both https and http.

Edit DeployLocal.bat

This configures the .bat file to reflect the target installation environment.

Finalize the installation

13. Open the Command Prompt in Administrator mode.
    

14. Run the DeploLocal.bat and follow the instructions.

Configure SHA-256 for ALM instance

Prerequisite: ALM Innovator Instance requires administrator rights to edit ALM Innovator’s instance specific files.

15. Navigate to the ALM Innovator installation directory (e.g. C:/Program Files (x86)/Aras/Innovator).

16. Open InnovatorServer.config file and add the attribute below into the DB-Connection tag.
    

17. Open Microsoft SQL Server Management Studio (SSMS) and login to the SQL Server using sa user.

18. Open ALM Configuring SHA-256.sql file or copy the SQL command and execute to the ALM deployed database (default: InnovatorSolutions).

    Notes:

    For any non-system user in the database, their password will be set to their login name.

    Non-system users will be required to set their passwords upon their first login.

Enabling Read Committed Snapshot

Prerequisite: The ALM Innovator Instance and Administrators rights are required to configure database instance.

By default, the isolation level in SQL Server is set to Read Committed. This prevents uncommitted data (dirty) reads by specifying that statements cannot read data values that have been modified but not yet committed by other transactions. In ALM, some transactions such as processing big TDPs can easily take more than 10-15 minutes. Leaving this default setting means that no user will be able to search for deliverables while a TDP is being processed.

Because of this, the recommendation is to set the isolation level to Read Committed Snapshot to allow statements to read data as they were prior to any uncommitted changes.

19. Log in to SQL Server Management Studio using the ‘sa’ account.

20. Under Databases, right-click the database and select Properties.

21. Under options, set “Is Read Committed Snapshot On” to True.

22. Select Yes to close all other connections and commit the change.