topic Re: Warning about Pro 2.1 and publishing to federated servers in ArcGIS Pro Questions

Warning about Pro 2.1 and publishing to federated servers

JeffPace — Thu, 18 Jan 2018 16:50:42 GMT

I was overjoyed to see the option to finally overwrite web layers on federated servers when publishing to Portal. While i would prefer to publish directly to server, this will do. But alas, it does not work

When publishing a web layer to Portal, if you choose a server that is not your HOSTING server (a secondary federated server) it ignores your choice and publishes to your hosting server.

I am so tired of this not working. It is half-baked and seemingly untested. This is a new feature, so obviously it was just added, but you would think it would at test the basic functionality.

dlaw-esristaff‌

Re: Warning about Pro 2.1 and publishing to federated servers

ThomasColson — Tue, 22 Jun 2021 08:38:37 GMT

This could be avoided if https://community.esri.com/ideas/12258 is implemented.

Re: Warning about Pro 2.1 and publishing to federated servers

JeffPace — Thu, 18 Jan 2018 17:03:00 GMT

Of course, just fighting the battle on all fronts. I would prefer going directly to server, but if they're going to a force us into a workflow that we don't want they could at least make sure that that work flow works.

Re: Warning about Pro 2.1 and publishing to federated servers

MelanieSummers — Thu, 18 Jan 2018 18:09:16 GMT

Hi Jeff,

Pro does support publishing and overwriting map services to your non-hosting federated server. I'm not able to reproduce the issue you're seeing where "it ignores your choice and publishes to your hosting server."

Are you seeing that behavior when you initially share the web layer or when you overwrite?

Thanks,

Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

JeffPace — Thu, 18 Jan 2018 19:09:32 GMT

Here is what i am observing. It is on initial publishing. I can now overwrite fine, but its on the wrong server

(view in My Videos)

Re: Warning about Pro 2.1 and publishing to federated servers

MelanieSummers — Thu, 18 Jan 2018 20:09:26 GMT

Thanks for the video, Jeff.

1. I'm logging the issue you found with the hosting server always being displayed when you hover over the federated server drop down - thank you.

2. I'm still not able to reproduce the service being published to the wrong federated server, my current hunch is it has to do with the web adaptor names so I'm setting up a test portal that matches yours and will retest when that's done.

Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

JeffPace — Thu, 18 Jan 2018 20:25:24 GMT

I bypassed my proxy, load balancer, and web adapter and logged into portal at

https://bcc-ap-portal02:7443/arcgis/

I see the same behavior. publishing to hosting no matter which server is chosen, and mouse over always shows the hosting server name

Re: Warning about Pro 2.1 and publishing to federated servers

MelanieSummers — Thu, 18 Jan 2018 22:15:00 GMT

Hey Jeff,

Could you email me how you federated each server? I'd like to see the admin URL and the service URL for the hosting and non-hosting server.

My email is msummers at esri.com

Thanks,

Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

JeffPace — Tue, 23 Jan 2018 14:42:55 GMT

Thank you Melanie for all the hard work. This is a confirmed bug when the hosting and federated servers are on the same domain and therefore end up with the same "name"

Re: Warning about Pro 2.1 and publishing to federated servers

MelanieSummers — Wed, 24 Jan 2018 17:17:07 GMT

The bug stems from Pro depending on the federated server name instead of a unique ID. When the web adapators are on the same machine, the names of the federated servers are likely to be the same so the first server in the list is always used.

As a workaround, you can change the names of your federated servers using the following steps:

Go to https://<your portal>/portal/sharing/rest/portals/self/servers
1. Note: you may need to manually generate a token and append it to the URL if your portal is 10.5.1 or earlier, you can do this at https://<your portal>/portal/sharing/rest/generateToken
Click on the Server ID for the non-hosting server
Click Update Server
Modify the Name of the federated server, this can be as small of a change as updating the casing or you can completely change the string

5. Re-paste the admin URL and click Update

Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

ThomasColson — Wed, 24 Jan 2018 18:58:52 GMT

How does that work when the SSL certificate is tied to the FQDN of the server name? As Portal doesn't seem to work well when using wildcard certs, or certs without the machine name in the SAN.....

Re: Warning about Pro 2.1 and publishing to federated servers

JeffPace — Wed, 24 Jan 2018 19:20:58 GMT

We have a single SSL cert on our main domain, www.mymanatee.org. All our servers are behind a reverse proxy and web adaptor, so they are

www.mymanatee.org/arcgis01/

www.mymanatee.org/arcgis02/

etc.

This was causing all the servers to show up in portal with the "name" www.mymanatee.org. I renamed them in portal (no change to the server itself, just the name of the federated server which i believe is an alias).

Hope that clarifies

Re: Warning about Pro 2.1 and publishing to federated servers

StevenHaslemore — Thu, 01 Feb 2018 22:54:47 GMT

Hi Jeff Pace,

good find and thanks for documenting the issue up here, this just helped me resolve map service publishing issues.

However we're having issues publishing Web Tools, have you tried this within your environment?

Prior to updating the "name" I was getting the following issues for map services and web tools respectively, `The ArcGIS GIS server role is not licensed on the ArcGIS Server` and `Your federated server version does not support web tools`. We have three federated servers, 'server' (server for maps and Is Hosted True), 'geoprocess' (server for gp), 'image', the image server was first in the list and publishing to image services was fine.

After updating the "name" map services work but the web tool error remains.

Within the Web Tool Content pane at first no Federated Server is selected in the dropdown, then when switching it to either of our 'server' servers (site.com/server or site.com/geoprocess) and analyzing again it will crash Pro.

Any thoughts appreciated!

Cheers,

Steven

cc Melanie Summers‌

Re: Warning about Pro 2.1 and publishing to federated servers

MelanieSummers — Fri, 02 Feb 2018 01:08:04 GMT

Hi Steven,

What version is your federated server? Are you still getting the error that your server role is licensed on the ArcGIS Server or that the federated server version doesn't support web tools?

For the geoprocess server, is access to the admin API available through the admin URL?

Thanks,
Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

StevenHaslemore — Fri, 02 Feb 2018 01:54:51 GMT

Hi Melanie,

Yes, still getting the `Your federated server version does not support web tools` error.

We're running 10.5.1 and have got access to the admin API.

Thanks,

Steven

Re: Warning about Pro 2.1 and publishing to federated servers

MelanieSummers — Mon, 05 Feb 2018 18:53:40 GMT

Web tools require a 10.6 federated server.

Publish web tools

Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

StevenHaslemore — Tue, 06 Feb 2018 21:01:56 GMT

Ahha, well that was easily answered, I clearly need to do some more reading up on the changing landscape!

Thanks Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

SimonJackson — Fri, 16 Mar 2018 01:02:54 GMT

Having a similar issue on a 10.6 single machine base deployment using the Esri Azure template.

'Your federated server version does not support web tools"

Trying to publish a GP Tool from Pro from my local machine to this instance. Any ideas?

You mention access to the Admin API? I believe that this is not exposed externally using the default security settings for Azure. Does this need to be tweaked?

Re: Warning about Pro 2.1 and publishing to federated servers

MelanieSummers — Fri, 16 Mar 2018 16:15:06 GMT

Hi Simon,

Server based services (map image layers, web tools, etc.) as well as web layers that are cached (scene and tile layers) require access to the admin API, so yes, you would need to change your security settings from the default option for the Esri Azure template.

We're working on improving this experience with future releases.

Thanks,

Melanie

Re: Warning about Pro 2.1 and publishing to federated servers

SimonJackson — Mon, 30 Apr 2018 06:56:31 GMT

Hi Melanie

Just to confirm, you mean poke through access to the GIS Server Admin URL?

e.g. https://amachinename.domain.com.au:6443/server or access to the portaladmin component?