Choose an Operational Map

In Solution Center > Feeder Services > Mapping > Maps, select the Operational Map to use for the Network Feature Service.

Refer to the Group Subnetworks topic for more information.

When configuring the Network Feature Service:

Make sure your operational map URLs have a unique base hostname. If the two maps have the same base hostname, one of those two maps can report an invalid user error if one of them has invalid credentials, since the Edge storage service groups operational maps together by hostname.
Depending on the other applications you have installed, you might already have an Operational Map to use for Feeder Services.
- If you already have an Operational Map (for example, an existing map used by Editor XI) that you need to update for Feeder Services, refer to the Update Existing Operational Map for Feeder Services topic for more information.
If you don’t have an Operational Map, the next question to ask is if you already have a published map service within ArcGIS Server. If you already have the published map service URL, refer to the Create Operational Map from Feature Service topic for more information.
If you don’t have a published map service URL yet, you need to publish the map service first in order to get the URL. Refer to the Publish Feature Services topic for more information.

IMPORTANT: Feeder Services requires that the Feature Service (therefore, the operational map) not be published as publicly available. If the Feature Service is set to Everyone (public), then attempts by ArcFM to use the Utility Network result in a failed authorization call from ArcGIS Enterprise. Feeder Services is built for the Utility Network, so the Feature Service must be set to Organization.