nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changing the service workspace of all the map services

tempRodrigo_DaSilva

Hello,

I'm trying to change the workspace of all map services without republishing.

(We are migrating to the new SQL Enterprise GDB from the OLD SQL Enterprise GDB.
We need all map services to access new SQL Enterprise GDB data without republishing.

Suggestions for this are welcome 😃

Finde mehr Beiträge mit dem Tag

Accepted answers

MMBR

Hello @tempRodrigo_DaSilva

If you already have services published then wait for Pro 3.2 release, it will add the capability to change the data source of published services in the "Update Data Source for Map" tool.

If you cannot wait for Pro 3.2 release or if you cannot move to Pro 3.2 when it comes out, then I am sorry to say that you will need to republish the services.

However, you can use these steps to avoid having to republish services in the future and to avoid having to use the Pro 3.2 "Update Data Source for Map" tool as well.

1. create a DNS alias that points to the database server

example:

DNS alias "gisdb1.acme.com" resolves to the server hostname "sqldb1.acme.com"

2. SQL Server Instance runs on default port 1433

3. SQL Server Database Server has Static IP Address

4. In the Geodatabase Connection Files use the DNS alias - Example: gisdb1.acme.com

5. Resource all map documents with the new Geodatabase Connection Files

6. Republish all the Services

Now, the next time the SQL Server Instance and Databases need to move to a new Server Hostname you can simply change the DNS Alias to point to the new server hostname, this will not break the geodatabase connection files, therefore it will not break any ArcGIS Server Services that were published.

Example: SQL Server Instance & Dabases move from "sqldb1.acme.com" to "sqldb2.acme.com, and the DNS Alias changes to resolve to the new server.

"gisdb1.acme.com" resolves to "sqldb2.esri.com"

I hope this helps.

Aled Wyn Jones

The docs say that this is possible via ArcGIS Server manager:

https://enterprise.arcgis.com/en/server/latest/manage-data/windows/registering-your-data-with-arcgis-server-using-manager.htm#:~:text=update%20the%20hostname%20of%20that%20database.%20You%20can%20do%20so%20at%20any%20time%20using%20ArcGIS%20Server%20Manager.

(A few paragraphs down from here, it says "This updates the registration for all services except stream services and ArcGIS Workflow Manager (Classic) services")

Although I've never found this to work 😞

I have found that this can be achieved via changing the configuration on the backend with the ArcGIS Server service stopped - it's not a supported workflow and can break things!

All comments

MMBR

Hello @tempRodrigo_DaSilva

If you already have services published then wait for Pro 3.2 release, it will add the capability to change the data source of published services in the "Update Data Source for Map" tool.

If you cannot wait for Pro 3.2 release or if you cannot move to Pro 3.2 when it comes out, then I am sorry to say that you will need to republish the services.

However, you can use these steps to avoid having to republish services in the future and to avoid having to use the Pro 3.2 "Update Data Source for Map" tool as well.

1. create a DNS alias that points to the database server

example:

DNS alias "gisdb1.acme.com" resolves to the server hostname "sqldb1.acme.com"

2. SQL Server Instance runs on default port 1433

3. SQL Server Database Server has Static IP Address

4. In the Geodatabase Connection Files use the DNS alias - Example: gisdb1.acme.com

5. Resource all map documents with the new Geodatabase Connection Files

6. Republish all the Services

I hope this helps.

Aled Wyn Jones

The docs say that this is possible via ArcGIS Server manager:

(A few paragraphs down from here, it says "This updates the registration for all services except stream services and ArcGIS Workflow Manager (Classic) services")

Although I've never found this to work 😞

I have found that this can be achieved via changing the configuration on the backend with the ArcGIS Server service stopped - it's not a supported workflow and can break things!

tempRodrigo_DaSilva

Hi, thank you very much for your comments. @MarceloMarques and @A_Wyn_Jones

I will test in my test environment the actions mentioned.

But I'm glad to hear that a feature of this size is being envisioned by ESRI in the near future.

AryamanBhattacharya_BeansAI

Hey @MarceloMarques ,

We are encountering a similar situation however the map services reference file based data sources (File Geodatabases). What approach should we follow ? We have the latest version of ArcGIS Pro installed but I have not come across the 'Update data source for map' tool.

Look forward to your suggestions.

Regards,

Aryaman

MMBR

@AryamanBhattacharya_BeansAI you will need to republish the services if you change the location of your file geodatabases that are used by existing services, otherwise you can create a network shared folder in the network storage device, then ask IT to create a DNS alias that points to the network share, then use the DNS alias to publish the services, hence if you need to move the file geodatabases, you just need to update the DNS alias to point to a new location. The ArcGIS enhancement to fully support the update of data sources for published services is still coming in a future release. I hope this helps.

AryamanBhattacharya_BeansAI

Thank you for the suggestion, @MarceloMarques . That surely helps!

AbraamPankhurst

"If you already have services published then wait for Pro 3.2 release, it will add the capability to change the data source of published services in the "Update Data Source for Map" tool."

Would you happen to have a link to the documentation for this feature?

The Update Data Source for Map interface in ArcGIS Pro only includes the capability to change the data sources of layers in an ArcGIS Pro map, not in an already published map service directly.

The layer types & workspaces supported for use with this method are included in the documentation: https://pro.arcgis.com/en/pro-app/latest/help/projects/update-data-sources.htm

After using this workflow, republishing the Map Service from this modified ArcGIS Pro map is still a requirement.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.