Run Deploy Application Server

An AVEVA Enterprise Resource Management application server environment is identified by a unique Environment name. The environment includes IIS sites for the AVEVA Enterprise Resource Management Server, API, API-REST, and Supplier Portal, along with Windows services for the Import Service and Multi Consumer Service. Database schema management is not handled by the application server environment.

After the deployment of a new environment is complete, the generated IIS sites appear in the IIS Manager. The corresponding Windows services are visible in the Services snap-in, which can be launched using %windir%\system32\services.msc.

1. To start AVEVA Enterprise Resource Management deployment manager, in the AVEVA Enterprise Resource Management installation package, from the DeploymentManager folder, below the InstallTools, run Aveva.Erm.DeploymentManager.exe.

   The AVEVA ERM Deployment Manager 1.3.0.0 dialog appears.

2. Select Deploy Application Server.

   

   The Environment Action window appears.

   

   Configuration: The configuration file for either a new environment, or an already existing environment. Default path and filename is C:\AVEVA\ServerUpgrade.config.

   Environment: The environment name.

3. Select Next.

   The Server Components window appears.

   

4. In the Include Components section, select the required checkbox to configure other setups.

   The default setting in AVEVA Enterprise Resource Management Deployment Manager is to setup a common AVEVA Enterprise Resource Management application server environment.

   Note: If you are installing the application based on an imported dump, then clear the Database option if the dump version matches the installer version. For example, if you receive a dump with version 19.0 and install the application using the 19.0.0 installer, clear the Database option.

5. Select Next.

   The Setup Server Environment window appears.

   

6. Enter the relevant details in the fields as required.

   Field	Description
   Run As Username	Specifies the domain service account or local administrator user. The account runs the Windows Services for the Import Service and Multi Consumer Service, and is also used for authentication for certain IIS sites.
   Run As Password	Specifies the password associated with the configured Run As Username field account.
   Installation Directory (Root Path)	Specifies the installation directory on the application server. The default value for new environments is C:\AVEVA. The field is read-only when upgrading an existing environment.
   Port Index	Specifies the port index used to access the environment. For new application servers, the initial port index is 00, which configures ports such as 9100, 9200, 9300, and so on, depending on the selections in the Server Component screen in the previous step. The field is read-only when you upgrade an existing environment.

7. Select Next.

   A terminal pop-up window appears, processing the command.

   

8. When the process is completed, in the terminal, enter exit.

   The Deploy Server Environment window appears.

   

9. Enter the relevant details in the fields as required.

   Field	Description
   Server (TNS Name)	Specifies the Oracle database connection. Either an EZCONNECT string in the format <host>:<port>/<service-name> (for example, Oracle01:1521/ERMTEST) or a TNS alias name is defined in the tnsnames.ora file of the Oracle Client.
   ERM Schema Name	The name of the AVEVA Enterprise Resource Management application database schema as entered in the Create Database Schema procedure.
   ERM Schema Password	The password specified for the AVEVA Enterprise Resource Management application database schema in the Create Database Schema procedure.
   Role Password	The password defined for the database role when you run the Create Database Schema procedure.
   Custom Schema Password	The password defined for the custom schema in the Create Database Schema procedure.
   Connection Name (shown in client)	The name displayed in the lower-left corner of the AVEVA Enterprise Resource Management Client. By default, this value is TNS:Custom Schema Name, however it can be changed as needed.
   Log Path	The path where log files from all AVEVA Enterprise Resource Management services and servers are stored. The default path is C:\ProgramData\AvevaErm. The account specified in Run As Username field requires read and write access to this directory. The C:\ProgramData is a hidden folder; that enables you to view hidden files in Windows if needed (In Tools, in Folder Options, in View, in Show hidden files, folders, and drives).
   Log Level	Determines the information written to the log files. The default level is Full. You can log level for a warning if the server is heavily loaded. Log files are required when raising support cases with AVEVA HelpDesk.
   SMTP Host	The SMTP server used by AVEVA Enterprise Resource Management application server components to send emails. Depending on server configuration, SMTP credentials are required. The SMTP server allows mail relaying from the AVEVA Enterprise Resource Management application server hostnames or IP addresses.
   SMTP Port	The port number used on the SMTP server, usually set to 25.
   SMTP Username	The username used for sending emails if company policy requires authentication on the SMTP server.
   SMTP Password	The password associated with the configured SMTP user account.
   Enable SSL	The security level used for communication encryption.
   Encrypt Configuration Files	Indicates the sensitive information in configuration files is encrypted using the IIS protected configuration provider. For more information, refer to the Microsoft Learn aspnet.
   Data Root Path	The root directory used by the Folders functionality in AVEVA Enterprise Resource Management. The path is used by plugins and staging areas and is visible in the AVEVA Enterprise Resource Management Client s00041 Folders screen after client installation.

10. Select Finish.

    The application is deployed to the required directories, existing software is replaced, and the database is updated to support new or changed AVEVA Enterprise Resource Management functionality.