Setup: Lucity-to-Geodatabase Integration

The Lucity-to-geodatabase integration allows edits made in Lucity Inventory modules to be pushed to the geodatabase.

Note: An agency that uses GIS must complete this configuration if it wants to allow Lucity to update the geodatabase.

There are two ways to set up this integration: 1) using a feature service, or 2) using a map service. The suggested method uses a feature service as this is based on ESRI's newer more robust technology.

Complete one of the following configuration processes to establish a default link between Lucity and the geodatabase.

A feature service is usually the primary link between Lucity and the geodatabase. Feature services are map services published through ArcServer that have feature access capabilities enabled. An administrator adds a feature service to the Lucity connection string using the Lucity Administration Tool, which is located under GIS > Connection Strings.

Create the feature service while keeping in mind:
- The map service must contain all of the feature classes to be updated in the geodatabase.
- The feature classes must display all of the fields that are configured to link to Lucity.
- The map service does not need any additional non-Lucity feature classes.
- The map service can either be a new map service or an existing one.
- This map does not need to be included in any Webmaps.
- The map does not require any special symbology.
- The user account used to access the map service must have edit permissions for the feature classes that Lucity will update in the geodatabase.
- The map service must be pointed to the version of the geodatabase that Lucity should update.
Publish the feature service to ArcServer.

Collect map service information.
For Arc 10.x
1. Log into Arc Server Manager and click on Services > Manage Services.
2. Locate the service you wish to use and click on it to view its properties.
3. Click the Capabilities button.
4. Copy down the REST URL, which should have a path similar to:
  - Map Service: http://<server name>/ArcGIS/rest/services/<service name>/MapServer
  - Feature Service: http://<server name>/ArcGIS/rest/services/<service name>/FeatureServer
  - Geocoding Service: http://<server name>/ArcGIS/rest/services/<service name>/GeocodeServer
  - Geometry Service: http://<server name>/ArcGIS/rest/services/<service name>/GeometryServer
  - Routing Service: http://<server name>/ArcGIS/rest/services/<service name>/RoutingServer
5. If collecting information for the map service that contains your operational data, click on the REST URL. A page containing the properties of the map service appears.
6. Scroll down and copy down the Spatial Reference Number. (Do this only for the layer that contains Lucity data.)
  Note: If text appears in the Spatial Reference field, rather than numerals, use the closest matching Spatial Reference Number from the following lists: Projected Coordinate Systems Geographic Coordinate Systems
Launch the Lucity Administration Tool and select GIS > GIS Services.
- On the Map Services tab click the Add Map Service button.
- Enter a Name and the REST URL of the map service.
  Note: This URL should end in /MapServer.
- Check the Has Feature Service? box. This tells the map that the layer has an attached Feature Service.
- Fill out other fields as necessary.
- Click the Save button.
  Note: If you are modifying an existing map service to have editing capabilities you just need to mark Has Feature Service? box for the existing record in the Map Service setup.
- Close the GIS Services tool
Point Lucity to the feature service.
1. Open Lucity Administration Tool > GIS > Connection Strings.
2. Find the connection string that links to the same data that the feature service does.
3. Use the Editable Map Service dropdown, select the map service that you added to the map services grid.
Configure Lucity to recognize that it is using a feature service.
1. Open Lucity Web > Admin Portal > Settings > System Settings > GIS Edit Integration section.
2. Make sure the Use Feature Service instead of Lucity SOE setting is set to TRUE.
  Users need Lucity App Admin > Run permission to access this section of the Lucity Administration tool.

A map service with the SOE (service object extension) can also create a link between Lucity and the geodatabase. A map service contains feature class and database connection information that is published through ArcServer. When the Lucity SOE is enabled on a map service, its connection information passes information from Lucity to the geodatabase.

Although using a map service is an older method, it is still a viable option. However, an agency should not implement this integration method if it plans to use feature services and GIS tasks to push edits from the Lucity Webmap (or other GIS editing platforms) to the Lucity Database. More information on GIS Editing outside of ArcMap

Requirements

ArcGIS 10.1 +
ArcServer Manager

Installation

Log into ArcServer Manager.
Click on Site at the top of the screen.
Select Extensions on the left of the screen
Select Add Extension. The file selection screen appears:
Click Browse and navigate to the Lucity SOE file downloaded from the Lucity Support site.
Click Add.

The SOE is now installed. Confirm that the Lucity extensions are enabled on the desired map services.

Note: If you see the Lucity MetaData extension under the services Capabilities ignore it. It is not relevant and will be removed in a future version.

Create a map service. Keep in mind:
- This map service must contain at least one feature class from the geodatabase that contains the features that Lucity will update. It is acceptable for the map service to contain all of the feature classes that could be updated; however, this is not required.
- The map service does not need any additional non-Lucity feature classes.
- You can either use a new map service or an existing one.
- The map does not need to be included in any Webmaps.
- The map service does not require any special symbology.
- The user account used to add the data to the map service must have edit permissions for the feature classes that Lucity will update in the geodatabase.
- The map service must point to the version of the geodatabase that Lucity should update.
Enable the SOE for the map service.
1. Log into Arc Server Manager and click on Services > Manage Services.
2. Find the map service to use for the SOE update.
3. Click on the map service to see its properties.
4. Click Capabilities.
5. Check the Lucity Data Update SOE check box.
6. Click Save and Restart.

Collect the REST URL for the feature service.
1. Log into Arc Server Manager, and, in the toolbar, select Services > Manage Services.
2. Find a map service to use.
3. Click on the map service to view its properties.
4. Click the Capabilities button.
5. Copy down the REST URL, which should have a path similar to: http://<server name>/ArcGIS/rest/services/<service name>/MapServer.
Point Lucity to the map service.
1. Open Lucity Administration Tool > GIS > Connection Strings.
2. Find the connection string that links to the same data that the map service does.
3. Under Edit Map Service URL, add the REST URL for the map service to the connection string.
4. If the map service is protected, complete the Map Service User and Map Service Password fields by providing a username and password for an ArcGIS account that has permission to edit the data used to create the map service.
Configure Lucity to recognize that it is using a map service.
1. Open Lucity Web > Admin Portal > Settings > System Settings > GIS Edit Integration settings.
2. Make sure the Use Feature Service instead of Lucity SOE setting is set to FALSE.
  Users must have the Lucity App Admin > Run permission to access this section of the Lucity Administration tool.

Settings that affect this integration are found in Lucity Web, under Admin Portal > Settings > System Settings > GIS Edit Integration section.

While the integration instructions outlined above create a default link between Lucity and the geodatabase, an agency can also set up alternate links between Lucity and the geodatabase. Doing so allows an agency to divide its feature classes into different feature services.

Using alternate feature services is not necessary; however, feature services are also used to establish edit capabilities in the Webmap and other web-editing platforms. Feature services used for Webmap editing are typically small and contain feature classes from only one set of GIS data (e.g., Storm features). Therefore, multiple editing feature services are required for different types of data.

In such a situation, an agency can reuse its editing feature services as alternate feature services within the geodatabase configuration.

Create the feature service using ArcMap. Keep in mind:
- The map service must contain the feature classes that you want it to update in the geodatabase.
- The feature classes must display all of the fields that are configured to link to Lucity.
- The map service does not need any additional non-Lucity feature classes.
- You can either use a new map service, or an existing one.
- The map service does not require any special symbology.
- The user account used to add the data to the map service must have edit permissions for the feature classes that Lucity will update in the geodatabase.
- The map service must point to the version of the geodatabase that Lucity should update.
Publish the feature service to ArcServer.

Collect map service information.
For Arc 10.x
1. Log into Arc Server Manager and click on Services > Manage Services.
2. Locate the service you wish to use and click on it to view its properties.
3. Click the Capabilities button.
4. Copy down the REST URL, which should have a path similar to:
  - Map Service: http://<server name>/ArcGIS/rest/services/<service name>/MapServer
  - Feature Service: http://<server name>/ArcGIS/rest/services/<service name>/FeatureServer
  - Geocoding Service: http://<server name>/ArcGIS/rest/services/<service name>/GeocodeServer
  - Geometry Service: http://<server name>/ArcGIS/rest/services/<service name>/GeometryServer
  - Routing Service: http://<server name>/ArcGIS/rest/services/<service name>/RoutingServer
5. If collecting information for the map service that contains your operational data, click on the REST URL. A page containing the properties of the map service appears.
6. Scroll down and copy down the Spatial Reference Number. (Do this only for the layer that contains Lucity data.)
  Note: If text appears in the Spatial Reference field, rather than numerals, use the closest matching Spatial Reference Number from the following lists: Projected Coordinate Systems Geographic Coordinate Systems
Launch the Lucity Administration Tool and select GIS > GIS Services.
- On the Map Services tab click the Add Map Service button.
- Enter a Name and the REST URL of the map service.
  Note: This URL should end in /MapServer.
- Check the Has Feature Service? box. This tells the map that the layer has an attached Feature Service.
- Fill out other fields as necessary.
- Click the Save button.
  Note: If you are modifying an existing map service to have editing capabilities you just need to mark Has Feature Service? box for the existing record in the Map Service setup.
- Close the GIS Services tool
Configure the feature class(es) to use an alternative feature service.
- Single Feature Class/Single Alternative Feature Service:
  - In ArcCatalog, open the Geodatabase Configuration tool.
  - Select the feature class for which you would like to set the Alternative Feature Service.
  - Select the Edit Map Service tab for that feature class.
  - Check the Use alternate service for this feature class box.
  - Use the drop-drop down to select the feature service you configured in Step 2 above.
- Multiple Feature Classes/Multiple Alternative Feature Services:
  - In ArcCatalog, open the Geodatabase Configuration tool.
  - Right-click on a configured connection (on the left side of the Geodatabase Configuration tool) and select Update Feature Class Services.