Configure the data curator component

Use the AVEVA Production Management data curation configuration tool to configure the following:

• AVEVA Platform Common Services (PCS) token information for the data curator

• Data curator service and AVEVA Events to CONNECT general and data ingress settings

• Port setting

  Note: If you made updates to the project, you need to restart the service manager first, the data curator service, and then the AVEVA Events to CONNECT service.

Prerequisites

• Start the AVEVA Production Management service manager. This enables the data curator service to identify which project database it should connect to.

• Ensure that AVEVA Events to CONNECT is installed and running.

• Configure AVEVA Events to CONNECT for data curation. This task configures the agent's data egress endpoint.

To configure the data curator component

1. Run the Production Management Data Curation Configuration tool as an administrator.

   You can access it from either of these locations:

   • Start menu, under the AVEVA folder, or

   • <ProductionManagement InstallPath>\DataCurator\ConfigurationTool\DataCurator.Configuration.exe

2. On the window that appears, specify the following details and select Save.

   • Token server URL - This is the URL of the server where the curation services are installed. For example: https://amp-srvr01.domain.com (https://<ComputerName>.<DomainName>)

     For detailed steps on how to get the token server URL, refer to Get the token server URL for the curation services.

   • Username and Password - The credentials from a domain user account in the Administrators group on the computer where the PCS token server is installed and running. The username must include the domain name. For example: <DomainName>\<Username>

   • Data curator port - The port number assigned to the curation services.

   • Certificate - This is your organization's SSL trusted certificate. During the installation, if you provide a least-privilege account, grant read permissions to the root CA's private key of this certificate. If the root CA is not available locally, grant read permissions to the certificate itself.

     If your AVEVA Production Management installation uses HTTP binding, ensure that you have followed the steps described in Configure the data curator for Production Management with HTTP binding and use Ampla Server Certificate for this field.

     

     IMPORTANT: Be sure to copy and securely save the client secret for data ingress and token settings. You'll need it for future configuration updates in the AVEVA Events to CONNECT agent Configurator plugin.

     After saving the configuration settings, the tool updates the data curator appsettings.json file with the certificate thumbprint, data curator port, configuration, and project database details. The tool also automatically configures the AVEVA Events to CONNECT General and Data Ingress settings and runs the data curator service.

3. Restart the AVEVA Events to CONNECT service from the Services window to trigger the event data publishing (upsert) operation.

   Note: The upsert operation is based on the default poll interval of 5 minutes.