Update the organization URL in ArcGIS Enterprise 11.5 multimachine deployment

ChadTheismann

Hello,

We are working to upgrade Enterprise version from 11.2 to 11.5 and change the URL in a parallel environment with a multi-machine deployment.

After we upgraded to 11.5 version and everything appeared to be functioning properly, we went through the steps to update org URL in this document- https://enterprise.arcgis.com/en/portal/11.5/administer/windows/update-the-organization-url.htm

On the surface, the update appeared successful but as we dived into the applications, we're finding many URLs pointing to our old URL environment. Note- the old url is still currently "live", the servers for our new 11.5 environment with updated url are using a host file.

The "Web Application patch" is installed. However, we are still encountering issues, including an error when accessing ArcGIS Experience Builder.

In Experience Builder, the error states this service is hosted on an ArcGIS Enterprise that the Experience Builder is not registered with. Please provide a Client ID to register first.

We updated the "Web Application patch" and rebooted the ArcGIS Enterprise portal service, as well as cleared the browser cache, but the issue persists.

Any insights, documentation, or additional places to look to address this issue? Data paths in Experience Builder still point to our old url. I appreciate any and all assistance!

Thank you for your time!

HarryPlendl

Have you done anything to change the URLs using the Arc GIS Assistant?

ArcGIS Assistant

This what we used for a 11.1 deployment to change the URL from the machine name to the organization. This required updating the URL manually (search and replace). We also had Esri professional services on site when this was happening. It's a lesson learning in planning. Pick a sustainable site name, have GIS that is easy to republish the services and apps to reconfigure. WHY? Because it seems the life cycle is about 2-3 years for anything software dependent.

I would republish the services using the new portal name as the active portal. It's just about as easy as all the band-aid work arounds. It just makes for a giant mess in IIS.

JoshuaBixby

Not sure if the following is related, but our organization just logged the following defect a couple weeks ago:
BUG-000181467 for Portal for ArcGIS

ChadTheismann

Thank you for the tips!

Yes, we're ending up using ArcGIS Assistant to rebuild more apps than originally expected.

I'm not familiar with that defect and would be interested in learning more. The link didn't work and web searches didn't find any information, could you relink that bug report?

JoshuaBixby

Unfortunately, I can't re-link to the public defect listing because Esri appears to have yanked it from being publicly available. I have never had that happen before, where a defect is logged and made public and then Esri removes it from public view. Here is the defect and description:

BUG-000181467: When running the updateFederatedServerUrl operation after changing the server Web Adaptor name, all feature services become inaccessible and are not updated.

JakeSkinner

Hi @ChadTheismann,

Here are locations to check to make sure the URLs updated successfully:

1. Portal Admin > System > Properties > check the WebContextURL

2. Portal Admin > System > Web Adaptors. If the web adaptor is not updated, and /edit to the URL and you can update the URL.

3. Portal Sharing REST (i.e. https://portal.domina.com/portal/sharing/rest). Log in and navigate to Home > Portal > scroll to the bottom and click Servers under Child Resources. Verify the URLs are updated here:

4. On the ArcGIS Server machine(s), open the security-config.json file located at \arcgisserver\config-store\security. Check the URLs are updated here:

5. Using Notepad++, search the \arcgisporta\content\items directory for any occurrences of the old alias. If any are found, make a copy of the items directory and then perform a Find/Replace using Notepad++.