To have the Lucity Web map interact with Lucity, GIS administrators must create maps containing Lucity features in ArcMap and publish them to ArcServer. 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 is the field that links to the auto id inside of Lucity. 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.
MSD based map services are highly recommended. These are services optimized for faster rendering and have other advantages as well.
ArcGIS has an Analyze Map tool that 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.
Some services can be cached 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 ArcServer product.
Not Supported
Lucity does not currently do not support "secured" map services or services that use token-based authentication.
Multi-layer caches are not supported.
Notes
The background color for dynamic services will always be 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 provides performance improvements and reduces server load. Anytime services are added, removed, updated, or updated to a new version the REST cache may need to be reset. The linked ESRI help article describes how to do this.