Configure the curation services database settings

Use the Staging tab to verify and configure the MES curation services database connection settings, including the database server, database name, and MES CONNECT data services unique identifier.

Configure the curation services database settings

1. Review the configured MES database connection settings:

   MES Server Name

   The SQL Server the MES middleware is connecting to. The MES curator service uses the server name configured for the MES middleware and the setting cannot be modified in this tab.

   MES Database Name

   The name of the MES production database used by the MES middleware. The MES curator service uses the database configured for the MES middleware and the setting cannot be modified in this tab.

   For more information on the MES database connection settings, see Configure the MES production database connection string.

2. Enter a CONNECT Unique Site Name.

   This string prepends all ID's from the MES site and uniquely identifies the ID's in CONNECT data services.

   The unique site name is created as an asset in CONNECT data services.

3. Review the user account used to access the MES production database:

   The SQL permissions are determined based on the connection parameters configured for the MES middleware. The MES Curator service uses the same connection type specified for the MES middleware. The MES database user account cannot be modified from this tab.

   Note: AVEVA recommends using Windows integrated security rather than SQL Server authentication to access SQL Server because it is more secure.

   • If Use Windows integrated security is selected, the SQL permissions to access and query the database are assigned to the current Windows user account.

   • If Use Windows integrated security is unselected, the SQL permissions are manually assigned by entering an SQL Server login user name and password.

   For detailed information on configuring the MES database user account, see Configure the MES production database connection string.

4. Select Validate to verify the following:

   • The MES server name exists and SQL Server exists and is reachable.

   • The MES database exists as a SQL Server database in the specified instance.

   • The version of the MES database specified is a supported version and the SQL Server version is at least 2017.

   • Whether there is an existing MES staging schema in the database, and if it does, its version.

   If validation is successful, the Configurator displays version information about the database, and available configuration actions.

   

5. Depending on the result of the database validation, take one of the following configuration actions:

   • If the validation was successful and a staging schema does not exist, proceed to step 6.

   • If the validation was successful and an MES staging schema exists, do one of the following:

     • Select Keep to update only the unique site name and preferred curator host in the MES database.

     • Select Overwrite to overwrite the existing staging configurations in the MES database.

       Note: AVEVA recommends backing up the MES database before overwriting it.

     • Select Migrate configuration and data to copy the existing MES staging schema configuration and data to a new version of the schema.

       The migrate option is only enabled if the existing staging schema version is at least 7.0.1 and there is a difference in the MES production database version.

     When the new staging schema version is exactly the same as the existing schema version (in the example shown, 8.00.6.02), then the scripts are consumed from the existing schema when creating the staging objects (for example, C:\Program Files (x86)\Wonderware\MES\Cloud Integration\Database Resources\8.00.6.02). This means that any script modified in the existing version's database resources folder will be consumed during schema creation.

6. (Optional) Select Dump Scripts to Disk to download the embedded resources associated with the database configuration (including database scripts) to the database resources folder. For example, C:\Program Files (x86)\Wonderware\MES\Cloud Integration\Database Resources\[Install Version Number].

   The scripts are downloaded to the installation version specific folder (8.00.6.02) on the machine to prevent accidental overwrites on pre-existing scripts in the downloaded from earlier versions.

7. Use the downloaded scripts to customize the MES database.

   Important: During the staging schema configuration, if dumped scripts are found on disk, the installer uses those scripts—bypassing the in-memory scripts provided by the Staging Curation Services component. To ensure the in-memory scripts are used instead, remove the corresponding scripts from the database resources folder before you configure the component.

8. Complete the AVEVA Identity Manager tab. For detailed instructions, see Configure the curation services AVEVA Identity Manager settings.

9. If the AIM tab is complete, select Configure to configure the component.

   Notes: Progress information and any errors, if they occur, appear in the Configurator's Configuration Messages window. If the configuration completes successfully, a success message appears in the Configuration Messages window. If errors are encountered, check the Operations Control Management Console (OCMC) Log Viewer for details. To view additional details, enable the Log Script Execution log flag in the Log Viewer.