Map Service Settings
Before you publish the map service for DHFC, review the following requirements.
Parameters
On the Parameters pane, increase the Maximum number of records returned by the server to 1000000.
The DHFC application is not set to paginate data, which is a method to display a limited number of search results. Increasing this number to 1000000 ensures you receive all data upon import.
Disable Schema Locking
While administering a GIS, there are situations when you might encounter a schema lock that prevents you from updating the underlying geodatabase while a service is running. In this case, you need to stop the active services before you can update the geodatabase. This is the default behavior, and you do not have to change it. However, since the DHFC service is running continually, you might find it beneficial to disable schema locking, specifically for the DHFC map service, so that you may perform geodatabase updates even while DHFC services are running. To do so:
- On the Parameters pane, under the Maximum number of records
returned by the server, click the Advanced button.
- On the schemaLockingEnabled field, change the value to
false, then click OK.
Capabilities
The DHFC map service requires three Capabilities: Mapping, Feature Access, and ArcFMMapServer.
-
Mapping: Use the defaults for this capability.
-
Feature Access: You can use almost all the defaults for this capability. The one setting to change is to check the box next to Allow update of true curves. In this manner, curves maintain their arc geometry instead of being replaced by a densified line.
-
ArcFMMapServer: Use the defaults for this capability.
Analyze: Messages, Warnings, and Errors
To analyze the map service, click Analyze. Or, when you click Publish, the application automatically runs the Analyze task. Either way, you are presented with a list of messages, warnings, and errors contained in the service.
Messages and warnings do not prevent a publish, but they usually indicate an area or configuration you can improve for better performance. Conversely, errors do prevent a publish and must be addressed. The list of errors and warnings vary by company, but here are some common examples:
Warnings
|
Warning |
Description |
|---|---|
|
Any warning discussing a custom server object extension (SOE). |
These can safely be ignored and published as is. DHFC requires the SOE. |
Errors
|
Error |
Description |
|---|---|
|
Any error discussing annotation being included in the service. |
DHFC does support annotation, but a map service with annotation cannot also have feature access enabled. To fix, publish two services: one with features and feature access enabled, and one with annotation and feature access disabled. |