Configuring the scheduler database

ArcGIS Data Reviewer for Server 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 or Oracle.

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

• You are installing ArcGIS Data Reviewer for Server in an ArcGIS for 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 to read and write scheduler information to an enterprise database. Configuration prerequisites include the following:

• Install and configure ArcGIS Data Reviewer for Server.
• Create the scheduler tables in a database. ArcGIS Data Reviewer for Server installs table creation SQL scripts in <ArcGIS Server install folder>\ArcGISDataReviewerServer\Server<version>\sql.

Steps:

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

   Your manager URL is http://<server name>:6080/arcgis/manager.

2. Click Services on the top panel of the page.
3. Click the reviewer map service that hosts Data Reviewer Server functionality.
4. Click Capabilities in the left 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 ArcGIS Data Reviewer for Server participates in an ArcGIS for 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.
   • SQLServer—The scheduler tables are stored in SQL Server.
8. If you checked Enterprise in step 6, type a connection string to your data store in the Scheduler Database Connection String text box.

   Make sure 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 SQLServer is Server=myServerName;Database=scheduler_database_name;User ID=myUsername;Password=myPassword;Trusted_Connection=False;.

   An example connection string for a named instance of SQLServer (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.