In order for Lucity Maps to interact with Lucity data, GIS administrators must create maps containing Lucity features in ArcMap and publish them to ArcGIS Server.
Consider these factors when publishing map services:
Requirements
Each feature class in a map that links to Lucity must have the following fields visible when the service is published:
ObjectID - The field that stores the Esri layer's object ID. This field should be the first field in the list of fields.
Lucity Common ID - The field that links to the related Lucity module's user-defined ID for the asset.
Shape - The Esri field that controls geometry. This field should also be the last field in the list of fields.
Optimization
Include the Lucity Auto ID field. This field links to the related Lucity module's system-defined ID for the asset. While this field is not required by the Web Map, some functions will perform better with the Auto ID present.
Use scale-dependent rendering wherever possible. Scale-dependent rendering speeds up the map display and reduces server load, which makes for a better end-user experience.
Use MSD-based map services. MSD (map service definition) services are optimized for faster rendering and provide other advantages, as well.
Take advantage of ArcGIS's Analyze Map tool. The Analyze Map tool verifies the integrity of the map and suggests methods for optimizing it for web use. See the ESRI documentation on the tools, available in ArcMap under Customize > Toolbars > Map Service Publishing, for more information.
Cache certain services to save download and server time. Lucity recommends caching map services for base-layer data that does not change; however, caching is a time- and server-intensive process. It's important to fully understand the implications of the caching process before establishing one. Map-caching is documented in the ArcGIS Server help documentation installed with the ArcGIS Server product.
Secured Map Services
The Webmap supports secured map services.
An authorized login and password can be included in the setup for the configuration or users can be required to enter a username and password when they launch the webmap.
When secured services are loaded in the Web Map, the data will not appear until a authorized username and password have been entered.
Lucity currently only supports securing services using ArcGIS Token Authentication. We do NOT support Web Tier Authentication.
Multiple-Layer Caches
The Webmap does not support multi-layer caches.
Notes
The background color for dynamic services is always transparent.
Resetting the REST Cache
Caching with ESRI’s REST API improves performance and reduces server load. Any time services are added, removed, updated, or upgraded to a new version, the REST cache may need to be reset. See the ESRI help article for instructions.