Warning about Pro 2.1 and publishing to federated servers

2420
19
01-18-2018 08:50 AM
MVP Regular Contributor

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

19 Replies
MVP Frequent Contributor

This could be avoided if  is implemented.

Reply
0 Kudos
MVP Regular Contributor

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.

Occasional Contributor III

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

MVP Regular Contributor

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

Reply
0 Kudos
Occasional Contributor III

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

Reply
0 Kudos
MVP Regular Contributor

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

Reply
0 Kudos
Occasional Contributor III

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

Reply
0 Kudos
MVP Regular Contributor

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"

Reply
0 Kudos
Occasional Contributor III

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:

  1. 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 
  2. Click on the Server ID for the non-hosting server
  3. Click Update Server
  4. 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

Reply
0 Kudos