Federating anArcGIS Server site with your portal integrates the security and sharing models of your portal with one or more ArcGIS Server sites. Deploying ArcGIS Data Reviewer-enabled map services with portal security affects the following deployment workflows and the availability of capabilities based on a user’s role.
Deploying Data Reviewer batch validation services
When deploying the service definition (*.sd) for the batch validation geoprocessing service the following should be noted:
Enable sharing using the Everyone (public) setting when publishing the ExecuteBatchJob GP service to ensure that scheduled batch validation completes as expected.
Deploying Data Reviewer Dashboard services
When deploying the service definition (*.sd) for the Reviewer map service the following should be noted:
From the Capabilities – Data Reviewer Server page, configure the Batch Validation Service URL property to use the portal URL (including the task name ExecuteBatchJob) for the batch validation service.
Configuring the Map Service using the DRS Configuration Utility
When configuring ArcGIS Data Reviewer for Server capabilities on your map service the following should be noted:
From DRS Configuration Utility, use the ArcGIS Server primary site administrator user name and password when connecting to the ArcGIS Server Administrator Directory.
Understanding access privileges
Access to capabilities provided by the ArcGIS Data Reviewer for Server extension is controlled by the portal roles defined for users accessing the service. When secured using portal security, a user’s role will impact the capabilities available for their use. For more information, see Levels, roles, and privileges.
The following tables outline the capabilities available for each of the default roles when secured using portal authentication.
Batch validation
| Operations | Default role | |||
|---|---|---|---|---|
Viewer | User | Publisher | Administrator | |
 | | | | |
| | | | |
| | | ||
| | | ||
| | | | |
| | | | |
| | | ||
| | | ||
| | | ||
| | | ||
| | | ||
For more information, see Automated data review.
Dashboard
| Operations | Default role | |||
|---|---|---|---|---|
Viewer | User | Publisher | Administrator | |
All operations under Dashboard are accessible to default roles. | ||||
For more information, see Data quality reporting.
Reviewer results
| Operations | Default role | |||
|---|---|---|---|---|
Viewer | User | Publisher | Administrator | |
| | | | |
| | | ||
| | | ||
| | | | |
| | | | |
| | | ||
For more information, see Results management.
Utilities
| Operations | Default role | |||
|---|---|---|---|---|
Viewer | User | Publisher | Administrator | |
| | | | |
| | | | |
| | | | |
| | | ||
Custom roles
Organizations may want to refine the default roles into a more fine-grained set of privileges by creating custom roles. When secured using portal security, the privileges assigned to a custom role will impact the capabilities available for those users assigned to the role. For more information, see Custom roles.
The following tables outline the capabilities available for custom roles when secured using portal authentication.
Batch validation
| Operations | Edit and Edit with full control privilege | |
|---|---|---|
Disabled | Enabled | |
| | |
| | |
| ||
| ||
| | |
| | |
| ||
| ||
| ||
| ||
| ||
For more information, see Automated data review.
Dashboard
| Operations | Edit and Edit with full control privilege | |
|---|---|---|
Disabled | Enabled | |
No additional privileges are required for any operations under Dashboard. | ||
For more information, see Data quality reporting.
Reviewer results
| Operations | Edit and Edit with full control privilege | |
|---|---|---|
Disabled | Enabled | |
| | |
| ||
| ||
| | |
| | |
| ||
For more information, see Results management.
Utilites
| Operations | Edit and Edit with full control privilege | |
|---|---|---|
Disabled | Enabled | |
| | |
| | |
| | |
| ||