Register Data Stores with Server Site

WilliamShoop · ‎04-01-2019

Hello all,

I am trying to register the data stores, all stored on one machine for test environment, with a Server site that has two ArcGIS Servers in it. We configured a Load Balancer to divert traffic to the Server site and Portal. To register the Data Stores we are trying to run the registerdatastore utility tool but are having issues. Below is the error:

Error encountered: Machine 'https://machine name/arcgis/datastoreadmin' returned an error. 'Could not connect to server on machine 'testafmserver.domain.com'. ArcGIS Data Store or ArcGIS Server on that machine may not be running or the machine is not reachable at this time.'

Syntax:

registerdatastore https://testafmserver.domain.com/arcgis serveradminname password --stores relational,tileCache,spatiotemporal

It doesn't seem to recognize the Load Balancer URL for the server site. I know the URL works as I can get to the REST services directory via the URL I put in the script. Can you register a data store to a server site? Or is it required to register them to a single machine?

Thanks,

Bill

JonathanQuinn · ‎04-02-2019

We're working on making it more clear how to register the ArcGIS Data Store to a multi-machine Server site. The ArcGIS Data Store has logic to determine the machines in the site and the traffic between the Servers and the Data Stores isn't HTTP traffic, so you don't need to put a LB in front of it. You'll just register the Data Store to a single machine within your Server site, (https://s1.domain.com:6443, or https://s2.domain.com:6443, etc), and the Data Store will sort out getting the list of machines in the site.

WilliamShoop · ‎04-03-2019

Thanks a lot Jonathan!

In our first install/configuration of the data stores we did have it registered to a single machine, https://s1.domain.com. The script was able to run without any errors but we found that we were not able to create any hosted content from the Portal so we unregistered the datastores. I can not say for sure if we included ':6443' in the configuration would that cause an issue? I know this may be hard to answer without looking at our environment setup but any input would be appreciated.

Thanks,

Bill