ArcGIS Server federation after server migration

1318
8
Jump to solution
09-06-2019 08:58 AM
BarbaraS
New Contributor III

I moved our ArcGIS Server and Portal installations to new servers. I feel like I am very close to get everything up and running properly but have problems with federating the server with Portal correctly. 

I had troubles unfederating the old machine (error saying, that the server can't be unfederated and while I wanted to add the new server, it was stating, that it is already federated). So i then went to this page: 

https://portalurl:7443/arcgis/sharing/rest/portals/self/servers, registered the new server, and unregistered the old server. Restarted the Portal and all looked good in the Portal settings too. The old servername was gone and the new one appeared:

Same in the Portal Admin Dir:

Would it be safe to change the Portal properties under this link: https://serverurl:6443/arcgis/admin/security/config/update 

Where do I find the PortalSecretKey and the webgisServerTrustKey in that case?

Any help is highly appreciated!

0 Kudos
1 Solution

Accepted Solutions
BarbaraS
New Contributor III

Update: I talked to Esri support consultants and two of them worked on my screen for some hours and fixed it in the end. They set up a Webcontext URL and tried a lot of other stuff. In the end, they changed the federated server from hosting to standalone in the Portal Admin Directory, unfederated that server and federated the server again with the DNS name on Portal settings. All fixed now!

View solution in original post

8 Replies
BarbaraS
New Contributor III

Update: I talked to Esri support consultants and two of them worked on my screen for some hours and fixed it in the end. They set up a Webcontext URL and tried a lot of other stuff. In the end, they changed the federated server from hosting to standalone in the Portal Admin Directory, unfederated that server and federated the server again with the DNS name on Portal settings. All fixed now!

View solution in original post

JonathanQuinn
Esri Frequent Contributor

Was the URL staying the same in this migration? We have a few blogs that describe migration workflows:

Migrate to a new machine in ArcGIS Enterprise 

Migrate to a new machine in ArcGIS Enterprise using the WebGIS DR tool 

They expect that the public URLs will stay the same.

Mehretab
Occasional Contributor

Hi Jonathan,

The documentation is quite clear but the focus was not on enterprise deployment that is accessed via a proxy server.

We are in a distributed environment. Our Server is installed in one machine while Portal, Datastore and the Web Adaptors are installed in another machine. In addition we also used a proxy server to access our machines (public URLs).

Here are how our deployment's URLs looks like:

 Portal URL: 

             https://proxyserver.domain.com/portal

Server URL:

             https://proxyserver.domain.com/server/ 

 ArcGIS Server Manager :

               https://serverMachine.domain.com:6443/arcgis/manager

 ArcGIS Portal Administrator:

              https://portalMachine.domain.com:7443/arcgis/portaladmin

 

I installed all the components of our ArcGIS enterprise in another machines in order to migrate our old enterprise deployment. If I am correct the only thing I need to do is redirect the server and portal contexts in our proxy server to point to the new machines during the importing/recovering process:

webgisdr --import --file /home/ags/arcgis/portal/propfiles/toimport.properties

I am assuming there is no need to alter the etc/hosts file to resolve to the old machine, before installing the Web Adaptors in the new deployment,  because they are not used as public url's?

Mehretab

0 Kudos
JonathanQuinn
Esri Frequent Contributor

Yes, if you flip your proxy server to point to the new environment, there's no need for etc\hosts entries. The point of the etc\hosts entries is so you can configure the environment without affecting your primary/production environment. If you can accept some downtime, that's not necessary.

Mehretab
Occasional Contributor

Thanks Jonathan,

I already tried to to export our ArcGIS Enterprise using  the webgisdr tool and it is throwing an error message which I found it not that helpful to understand what is happening in the process. Here is the detailed error posted as a question in GeoNet.

0 Kudos
JoshHevenor1
New Contributor III

I'm looking at a different federation problem (my problem), and am considering this unfederate/refederate approach.  Can you give more detail on "changed the federated server from hosting to standalone in the Portal Admin Directory"?  I see options to change my server role from "hosting" to "Federated" or "Federated with Restricted...", under Federation > Servers > serverid > Update action, but I may be looking in the wrong place.

EDIT: I think I see what you're talking about on the server admin (not portal), under security > config > changeServerRole. Can you confirm this was your order

1. Update server role to standalone using server admin: security > config > changeServerRole

2. Unfederate using Portal admin

3. Refederate with desired new URL

0 Kudos
BarbaraS
New Contributor III

Hi Josh,

My apologies for my late reply, I don't have notifications on.

This seems like it was our approach yes! I hope you were able to solve your problem, I had a look at your thread but have never had this issue myself.

0 Kudos
LorenzMeyer1
New Contributor III

Hi

We currently face a similiar problem. After unfederating a server, federating to internal url (webadaptor url), exporting backup with wegbgisdr tool, unfederate again and refederate with original "public" url it seems that the sharing items (for groups or no groups) does no longer work properly. 

Just trying to set again the sharing permissions on a item does not work. 

Anyone a hint on how to fix this issue?

0 Kudos