In order for Lucity maps to interact with Lucity, GIS administrators must create maps containing Lucity features in ArcMap and publish them to ArcGIS Server. The following are some considerations for publishing those map services.
Requirements
Each feature class in a map that links to Lucity must have the following fields visible when the service is published.
Lucity Common ID - the field that links to the common id inside of Lucity. The name of this field varies.
Shape - The Esri field that controls geometry.
Optimization
Include the Lucity Auto ID field. This field links to the auto id inside of Lucity [Web?]. The name of this field varies. While this field is not required by the webmap some functions will perform better with the Auto ID present.
Always use scale dependant rendering wherever possible. This speeds up the map display, reduces load on the server, and makes for a better working map for the end-user.
Use MSD-based map services. These are services optimized for faster rendering and have other advantages as well.
Take advantage of ArcGIS's Analyze Map tool. This tool verifies the integrity of the map and provides suggestions on optimizing the map for publishing to the web. See ESRI documentation on the tools. They are available in ArcMap by selecting Customize > Toolbars > Map Service Publishing.
Cache certain services to save download and server time. It is recommend to cache map services for base layer data that does not change; however, caching is a time and server intensive process and should not be taken lightly. Be well read and prepared before starting a caching process (don’t overdo it). Map caching is documented in the ArcGIS Server help that is installed with the ArcGIS Server product.
Secured Map Services
Secured Map services are supported.
When Secured services are loaded in the map the data will not show until a correct username and password have been entered.
Not Supported
Multi-layer caches
Notes
The background color for dynamic services is always transparent.
Map Services must be deployed as pooled services. ESRI's Silverlight components do not support non-pooled services.
Resetting the REST cache
Caching with ESRI’s REST API improves performance and reduces server load. Any time services are added, removed, updated, or updated to a new version, the REST cache may need to be reset. See the ESRI help article for instructions.