About connecting to ArcGIS Server in ArcGIS for Desktop
ArcCatalog and the Catalog window in ArcGIS for Desktop allow three options for connecting to an ArcGIS Server site: a Use GIS services connection to use services, a Publish GIS services connection to publish services, and an Administer GIS server connection to manage the site.
Connection types
Administrative connections (Administer GIS server)
When you connect to an ArcGIS Server site using an Administer GIS server connection, you can edit server properties such as the configuration store location, cluster configurations, and the list of machines participating in the site. You can also publish, add, delete, start, and stop services.
When you connect, you'll be asked for a user name and password that has been granted administrative privileges to ArcGIS Server. This can either be the primary site administrator account that you defined when you first created the ArcGIS Server site (in other words, when you first logged in to ArcGIS Server Manager), or it can be another account that has been added to your security store and granted administrative permissions.
For complete instructions on how to make an administrative connection, see Making an administrative connection to ArcGIS Server in ArcGIS for Desktop.
Publisher connections (Publish GIS services)
When you connect to an ArcGIS Server site using a Publish GIS services connection, you can publish GIS resources, such as map documents, globe documents, databases, and service definitions, to your server. You can also configure and publish draft services that reside locally on disk or in the Drafts folder of your connection to the server. Additionally, you can add, delete, start, and stop services. You cannot edit any properties of the site.
When you connect, you'll need to enter a user name and password from your security store that has been granted at least publishing privileges by the server administrator.
For complete instructions on how to make a publisher connection, see Making a publisher connection to ArcGIS Server in ArcGIS for Desktop.
User connections (Use GIS services)
When you connect with a Use GIS services connection, you can view and use the services published to the site. However, you cannot edit server properties, publish services, edit service properties, or add, delete, start, stop, or pause services.
When you connect, you'll need to enter a user name and password from your security store.
For complete instructions on how to make a user connection, see Making a user connection to ArcGIS Server in ArcGIS for Desktop.
Specifying the server URL
When you attempt to connect, you'll be asked to type the URL to your ArcGIS Server site. Depending on your site configuration, the URL will vary. For example:
Site configuration | URL syntax |
|---|---|
In a site that includes the ArcGIS Web Adaptor… | …include the name of the web server hosting the ArcGIS Web Adaptor and the name of the Web Adaptor in the URL. If the ArcGIS Web Adaptor is installed on a default website, such as port 80, you do not need to include the port number in the URL. For example: http://<web server name>/<web adaptor name> Conversely, if the ArcGIS Web Adaptor is not installed on a default website, for example, port 55, you'll need to include the port number in the URL. For example: http://<web server name>:55/<web adaptor name> |
In a site that does not include the ArcGIS Web Adaptor… | …include the name of the GIS server that ArcGIS Server is installed on, port 6080, and arcgis in the URL. For example: http://<server name>:6080/arcgis |
Caution:If your server administrator has configured the Web Adaptor to block administrative access to the server, you will not be able to connect to the server in ArcGIS for Desktop through the Web Adaptor URL using an administrative or publisher connection. Alternatively, you can connect directly to the GIS server by using the URL format http://<GIS server>:6080/arcgis.
For more information about the ArcGIS Web Adaptor, see About the ArcGIS Web Adaptor. To learn more about the various ArcGIS Server site configurations, see Deployment scenarios.