Configure the scheduler database

Note:

ArcGIS Enterprise 10.9.x, part of the ArcGIS 2021 releases, are the last ArcGIS Enterprise releases that support services published from ArcMap. You are encouraged to migrate automated review workflows to ArcGIS Data Reviewer capabilities available in ArcGIS Pro attribute rules.

The Data Reviewer ArcMap runtime-based server object extension (SOE) allows you to configure batch validation to execute repeatedly according to a schedule. By default, schedules are stored in an SQLite database. You can store the scheduler tables in SQL Server, PostgreSQL, or Oracle.

Consider storing your scheduler tables in an enterprise database if you have any of the following requirements:

• You are installing the Data Reviewer server extension in an ArcGIS Server cluster.
• Your scheduler database needs enterprise database backup and restore or high availability functionality.

This document describes how to configure a Reviewer map service's Data Reviewer server extension to read and write scheduler information to an enterprise database. Configuration prerequisites include the following:

• Install and configure the Data Reviewer server extension.
• Create the scheduler tables in a database. The Data Reviewer server extension installs table creation SQL scripts in <ArcGIS server installation location>\ArcGISDataReviewerServer\Server<version>\sql\creation_scripts.

1. Sign in to ArcGIS Server Manager by opening your manager URL in a web browser.

   Your manager URL is https://<server name>:6443/arcgis/manager.

2. Click Services on the top panel of the page.
3. Click the reviewer map service that hosts the Data Reviewer Desktop server extension functionality.
4. Click Capabilities in the side panel.
5. Click Data Reviewer Server.
6. Check one of the following Scheduler Database Type options:
   • Local—Indicates that the batch validation scheduler will use a local data store for its tables. This is the default. Do not choose this option if the Data Reviewer Desktop server extension participates in an ArcGIS Server cluster.
   • Enterprise—Indicates that the batch validation scheduler will use an enterprise database to store its tables.
7. If you checked Enterprise in step 6, choose one of the following options by clicking the Scheduler Database Platform drop-down arrow:
   • Oracle—The scheduler tables are stored in Oracle.

     Note:

     To use the scheduler database in Oracle, you must install the full version of the 64-bit Oracle database client software on each machine in the ArcGIS Server site.

   • SQLServer—The scheduler tables are stored in SQL Server.
   • PostgreSQL—The scheduler tables are stored in PostgreSQL.
8. If you checked the Enterprise check box in step 6, type a connection string to your data store in the Scheduler Database Connection String text box.

   Ensure that the user account listed in the connection string has SELECT, INSERT, UPDATE, and DELETE permission on the scheduler tables.

   An example connection string for Oracle is Data Source=<tnsnames.ora alias name>;User ID=myUsername;Password=myPassword;.

   An example connection string for PostgreSQL is User ID=myUsername;Password=myPassword;Host=myServerName;Port=5432;Database=scheduler_database_name;

   An example connection string for SQL Server is Server=myServerName;Database=scheduler_database_name;User ID=myUsername;Password=myPassword;Trusted_Connection=False;.

   An example connection string for a named instance of SQL Server (or SQL Express) is Server=myServerName\instance_name;Database=scheduler_database_name;User ID=myUsername;Password=myPassword;Trusted_Connection=False;.

9. Click Save and Restart.

   Note:

   If the service fails to start, review the ArcGIS Server logs. If the logs contains this error: "Data Reviewer scheduler database version does not match the installed release," you'll need to migrate to the currently installed version.