Configure the AVEVA Recipe Management Server Components

You can specify to run AVEVA Recipe Management in Standalone Mode or integrated with AVEVA Application Server. The AVEVA Recipe Management Server is configured to start as a Network service named AVEVA Recipe Management Execution Service. The startup type for this service is “Automatic.” The AVEVA Recipe Management Execution Service that is used when running in standalone execution mode is not configured for automatic recovery. For more information, refer to "Configuring the AVEVA Recipe Management Execution Service for Automatic Recovery".

NOTE: There should be one node in the network where System Management Server needs to be configured before configuring the Server Components.

To configure the server components

1. Open the Configurator utility.

2. Click Server Components in the left pane. The configuration options appear in the right pane.

   

3. In the SQL Administrator Login (Create/Upgrade Database) area, do the following:

   1. Specify the SQL node name or SQL Instance Name which is installed on the local or remote node or Windows node name in the Server Name box.

   2. Specify the account that will be used to log on to the SQL Server and create the AVEVA Recipe Management model database.

   NOTE:
   
   - It is recommended to use Windows Authentication for accessing the database as a best practice. However, no matter which approach you choose, make sure the user has 'sysadmin' privileges in SQL Server. The 'sysadmin' privilege defined in SQL Server is necessary so that they can create the database. Also, the current logged on user will be added to the AVEVA Recipe Management security configuration and is given Administrator privileges (if they do not already exist in the database). This will work on new and existing databases. This can be useful if you restore a database from one domain to another domain; it allows you to access with the current user.
   
   - AVEVA Recipe Management supports SQL Server Transport Encryption, and AVEVA recommends turning it ON. For more information, refer to the documentation of the SQL Server version you are using.

4. In the Application Pool Identity (Read/Write access to Database) area, specify the user account that the web application will use to access the recipe model database. This account should not have a password that expires. The Application Pool identity account should have the least privileges possible, but needs enough privileges to access Active Directory to look up users and groups (if Active Directory is being used). If you are using Active Directory, then this user will most likely need to be a domain user. It is also a best practice to not add this user in the AVEVA Recipe Management user configuration.

5. In the ArchestrA Identity Manager Client Registration area, do the following:

   1. Enter the ArchestrA Identity Manager host name in the AIM Host box. For the ArchestrA Identity Manager in the Application Configurator, if a value other than the default (443) for the HTTPS Port is used, you must enter the ArchestrA Identity Manager host name as <AIMHostName>:<PortNumber>. If the SSL Certificate used by ArchestrA Identity Manager Host is issued to Fully Qualified Domain Name (FQDN), then the ArchestrA Identity Manager host name will have to be provided as the same FQDN. For example, myserver.mydomain.com.

   2. Enter the Registrar user name in the Registrar User box. Make sure that the Registrar User that you enter has Administrator privileges, otherwise client registration will not succeed.

   3. Enter the password in the Password box.

   NOTE: AIM Host needs to point to the ArchestrA Identity Manager, which was installed locally/remote to the AVEVA Recipe Management server.

6. Select the SQL Server Reporting Services (SSRS) Configuration check box and do the following:

   1. Specify the SQL node name in the SQL Server Instance box.

   2. Specify the account that will be used to log on to the SQL Server and create the AVEVA Recipe Management model database.

   Select this option when you want to deploy the Reports automatically. You also need to pre-configure the Reporting services on the SQL Server Instance node.

   NOTE: If you reconfigure AVEVA Recipe Management server without selecting SQL Server Reporting Services (SSRS) Configuration option, it will undeploy the existing deployed Reports.

7. In the Execution mode area, specify which application should be used for IO mapping and execution.

   • Click Standalone for AVEVA Recipe Managementto use the OPC UA Client service. You will then need to configure the OPC UA Client service. For more information, refer to "Configuring Server Components in Standalone Mode".

   • Click Integrated with AVEVA Application Server for AVEVA Recipe Management to use AVEVA Application Server. For more information, see the AVEVA Recipe Management User Guide or Help.

8. In the SSL Certificate area, select the certificate from the Name list. You must use the same certificate as specified under the Certificates area while configuring the Certificates option.

9. In the Event Service area, select the check box to configure and create an instance of the Event service to the server node. For the Standalone configuration, if you select the Event Service area, the details are not enabled. For the Integrated environment, the Event Service area along with the details are available for you to configure the Event Service. Do the following:

   1. Specify the GR Node Name under which the event service is hosted in the GR Node Name box.

   2. Specify the galaxy name under which the event service is hosted in the Galaxy Name box.

   NOTE: Make sure that a Galaxy platform is deployed on the AVEVA Recipe Management node before configuring the Event Service in AVEVA Recipe Management Server. For example, if you install ArchestrA Galaxy Repository + AVEVA Recipe Management IDE Extensions on node 1 and AVEVA Recipe Management Server on node 2, then the WinPlatform has to be deployed on Node 2 from Node 1 before configuring Event Service in AVEVA Recipe Management Server.

   If the Galaxy is not deployed, the following warning message is logged in the logger:
   Failed to connect to Configuration Service on node: <GR Node Name>
   Invalid URI: The format of the URI could not be determined.Connection to the GR Node could not be established due to some of the following reasons:
   1. Event Service configuration requires Wonderware System Platform 2014 R2 or greater.
   2. Event Service can be configured if either Server feature is installed on this node / Components for AVEVA System Platform are installed on the GR node and the platform is deployed on this node.
   3. If Integrated with AVEVA Application Server option is selected, then check the GR Node Name for galaxy to be in deployed state.

10. Click Configure. A green check icon appears in the left pane when Server Components are successfully configured.