Configuring the user-specific endpoints file
The best way to configure a server endpoint that locates your own Esri server is through the Analyst's Notebook user interface. However, the information is added to the user-specific ServerEndpoints.config file, which you can edit by hand.
The user-specific file is in XML format. You can use a simple text editor such as Notepad, but a dedicated XML editor is better. Badly formed XML stops the product from working.
Note: If you want to change the default tokenLifespan attribute value
of an endpoint configured through the user interface, you can do this only by editing the
ServerEndpoints.config file manually.
To add details of your own server endpoints to the user-specific
ServerEndpoints.config file:
You can add as many server endpoints as you need.
Tip: To remove unnecessary servers from the user interface list, you can remove
the Esri demonstration server endpoints from the
preinstalled server endpoints file. This is the portion of the file that you remove:
<endpoint name="EsriDemoBaseMapProvider"
binding="basicHttpBinding"
bindingConfiguration="arcGisHttpBinding"
address="http://services.arcgisonline.com/ArcGIS/services/"
contract="i2.Mapping.Esri.ArcGISModule.Proxy.ServiceCatalogPort"/>
<endpoint name="EsriDynamicMaps"
binding="basicHttpBinding"
bindingConfiguration="arcGisHttpBinding"
address="http://serverapps.esri.com/ArcGIS/services"
contract="i2.Mapping.Esri.ArcGISModule.Proxy.ServiceCatalogPort"/>
<endpoint name="EsriDemoRouting"
binding="basicHttpBinding"
bindingConfiguration="arcGisHttpBinding"
address="http://tasks.arcgisonline.com/ArcGIS/services/"
contract="i2.Mapping.Esri.ArcGISModule.Proxy.ServiceCatalogPort"/>
<endpoint name="DriveTimes"
binding="basicHttpBinding"
bindingConfiguration="arcGisHttpBinding"
address="http://sampleserver3.arcgisonline.com/ArcGIS/services"
contract="i2.Mapping.Esri.ArcGISModule.Proxy.ServiceCatalogPort"/>