Before users can access Insights in ArcGIS Enterprise, you must set up a base ArcGIS Enterprise deployment.
You also need to install Insights in ArcGIS Enterprise. For instructions, see Install ArcGIS Insights in ArcGIS Enterprise.
Required base ArcGIS Enterprise deployment
A base ArcGIS Enterprise deployment is required to support Insights in ArcGIS Enterprise, licensed with ArcGIS Server Standard, ArcGIS Server Advanced, ArcGIS Server Workgroup Standard, or ArcGIS Server Workgroup Advanced. For a tutorial on how to create a base deployment, see Tutorial: Set up a base ArcGIS Enterprise deployment.
Note:
If ArcGIS Web Adaptor for ArcGIS Server is not configured to enable administrative access, ArcGIS Server must be configured to use a CA-signed certificate to support creating database connections.
Some organizations may require a CA-signed SSL certificate for ArcGIS Data Store. For more information, see Replace ArcGIS Data Store SSL certificate.
After you build your deployment, you will also need to configure required portal settings (see below).
Required portal configuration settings
After you set up the base ArcGIS Enterprise deployment, ensure that users in your organization have the appropriate role, privileges, and user type to access and use Insights.
A user requires the following:
- The default Publisher or Administrator role, or an equivalent custom role to add data, create visualizations, and use spatial analytics.
- Insights Analyst, Creator, or GIS Professional user type.
- An Insights license assigned to the user. The Insights Analyst user type has an Insights license included.
For more information, see Licensing.
Next, configure other settings to enable important services and features such as geocoding and routing (see below).
Important settings for ArcGIS Insights features
These configuration settings are not required, but they allow portal members to connect to data warehouses, geocode data, use maps (and extents) suitable for their region, and more.
- Register relational data store types
- Edit relational data store types
- Configure utility services
- Configure scheduling
- Configure boundary layers
- Configure Living Atlas content
- Batch geocoding
Register relational data store types
To support database connections that allow users to add datasets from a business database, your portal's hosting server site must have the required relational data store types registered for use. Follow these steps to ensure Insights can work with your database.
- Upload the required vendor files to ArcGIS Server. This step is not required for PostgreSQL because the PostgreSQL JDBC driver is included in ArcGIS Server. If you are registering a PostgreSQL relational data store type, skip to step 2.
- Get the required vendor files for the database type you want to register (see Required vendor files to get the list).
- Package vendor files into a compressed folder (.zip) for a single database type.
Note:
When compressing the JDBC drivers for upload, .jar files should be located in the root of the archive. There should not be any folders in the .zip file.
- Using an administrator account, sign in to the ArcGIS Server Administrator Directory (http://server:port/arcgis/admin).
- Browse to Uploads.
- Click Choose File.
- Browse to the compressed folder containing the vendor files for the database to be registered.
- Select the compressed folder and click Open.
- Optionally add a description to the file to upload.
- Click Upload.
- Note the item ID of the uploaded file.
- Browse back to Home.
- Register the data store type on ArcGIS Server.
- Browse to Data in the ArcGIS Server Administrator Directory.
- Browse to relationalDatastoreTypes.
- Browse to Register.
- Select the compressed folder using the item ID from the Uploaded item ID drop-down list. This step is not required for PostgreSQL because a compressed folder was not created for step 1.
- Select the corresponding type from the Relational Datastore Type drop-down list.
- Click Register Item.
- Restart ArcGIS Server.
- After registering all required data store types following steps 1 and 2, you have to restart ArcGIS Server on each machine in your site. To do this, you need to restart the Windows service or use the stopserver and startserver scripts on Linux.
- Validate user database privileges.
- Make sure that Insights users have the required database privileges to create database connections and query data.
Tip:
Insights displays spatial data in the spatial reference system of your portal organization's default basemap. This is for display and query purposes only; the underlying data is not altered. If the two spatial reference systems' underlying geographic coordinate systems are incompatible, alignment and accuracy problems may be observed. To ensure fast performance and accurate display of spatial data, it is recommended that organizations use the same spatial reference system for their default basemap and their spatial data. You can change the default basemap of the portal or reproject your spatial data to match your organization's basemap.
Edit relational data store types
Edit a registered relational data store type to update its properties. Before proceeding with any edit, make a backup copy of the JSON properties. To edit the relational data store type, use the following steps:
- Edit the registered relational data store type on ArcGIS Server.
- Using an administrator account, sign in to the ArcGIS Server Administrator Directory (http://server:port/arcgis/admin).
- Browse to Data in the ArcGIS Server Administrator Directory.
- Browse to relationalDatastoreTypes.
- Click the registered relational data store type that needs to be edited.
- Scroll down to the bottom of the page and click edit.
- Modify the properties and click update.
- Restart ArcGIS Server for the changes to take effect.
After editing registered relational data store types, restart ArcGIS Server on each machine in your site. To do this, you need to restart the Windows service or use the stopserver and startserver scripts on Linux.
For more information, see Edit Relational Data Store Type.
Configure utility services
Configure utility services required to power specific functionality in your portal, such as performing analysis that depends on utility services. The table below lists each utility service and the Insights feature it supports.
| Option | Description |
|---|---|
Allows users to add location to their datasets by specifying an address. For user instructions, see Enable location for your data. | |
Enables the use of dissolved boundaries for Create Buffer/Drive Times. | |
Enables Find Nearest. | |
Allows users to add demographic information to a location or area using Enrich Data. | |
Allows users to specify a means of transportation, such as walking time or trucking distance, for Create Buffer/Drive Times. |
Note:
- You can configure your portal to use utility services from ArcGIS Online. See Configure ArcGIS Online utility services for details.
- If you are running Insights in a disconnected environment, you must configure the service from a federated or hosting server.
Configure scheduling
Scheduling must be enabled in your ArcGIS Enterprise organization before you can schedule updates in Insights. You can configure ArcGIS Enterprise to support scheduling and change other configurations using the gw-cinfig.properties file in the following location on Portal for ArcGIS: arcgis/portal/framework/webapps/arcgis#sharing/WEB-INF/classes/resources.
Note:
Scheduled updates are available beginning in ArcGIS Enterprise 10.8.1.
| Setting | Description | Default value |
|---|---|---|
| config.is-tasks-scheduling-enabled | Enable or disable scheduling for the organization. | true |
| config.max-scheduled-active-tasks-per-user | The maximum number of schedules that can be created by an individual user. All schedule types (Insights pages, ArcGIS Notebooks, and so on) count toward the total. | 20 |
| config.max-scheduled-task-runs-history-count | The number of previous runs saved in the schedule history. | 30 |
| config.failed-scheduled-task-runs-to-disable | The maximum number of failures in a row for a single schedule. If the maximum number of failures is met, the scheduled updates will be paused. | 5 |
Configure boundary layers
Configure boundary layers to allow organization members to use feature layers containing boundary information for supported countries in their maps and analyses.
When you configure boundary layers, users can add these layers from the Boundaries tab of the Add to page window. Boundary layers are another way for users to add location to their data. For user instructions, see the following:
Configure Living Atlas content
Configure subscriber and premium content from ArcGIS Living Atlas of the World to make this ArcGIS Online collection available in your portal. Living Atlas content that does not require you to sign in to an ArcGIS Online account is available by default.
Batch geocoding
The geocoder in your organization must support batch geocoding to be used to enable location on multiple addresses. For more information on geocoders available for configuration, see Configure utility services.