Issue Pointing AR Web Server to Specific AR App server

There is a second setting (a number) in that file that indicates preferred behavior for use of the named server.

I cannot recall which is which off the top of my head, but one value means "use this AR server (only)" and the other means "use any AR server that shares the same configuration as this one"

Regardless, check to see if the values are the same on all your web interfaces.

Thanks, but this is how it looks:

<?xml version="1.0" encoding="utf-16"?><Connection EDMServiceType="2" EDMServiceName="exampleserver01.domain" />

Should we use a different value than 2 here?  Per this article that is what we should be using I think?

support.oneidentity.com/.../modify-active-roles-web-interface-connection-settings

That appears to be the correct setting.

I can't think of any other setting that would override that.

Does the service connection point for the desired server exist in your Active Directory Configuration container?

That is the correct setting.

You may have some bad cached data which could be interfering with expected functionality.

Please follow Solution 1 from this resource:

Solution Title: How to clear the Active Roles Server schema cache
Solution Number: 4322345
Solution URL: https://support.oneidentity.com/kb/4322345

No it does not...

??? - is that intentional?

Shouldn't matter since you are specifying the server explicitly but it is a bit of a loose end in your configuration.

Tried solution 1....  rebooted app server and web server after clrearing the cache, still no bueno, tried differnt machines, browsers too, doesn't matter, it always connects back to same server, I'm stumped

Hi,
might be silly but do you use the right file?
Maybe the server was installed twice and used another location for the installation.

BEN

To confirm that the Web interface is reading the XML file, I would suggest that you edit the file to insert an invalid server name. Recycle your AR IIS application pool, then your Web browser should show an error/failure to connect. If you don't get that failure, then that would suggest that the Web interface is getting its configuration elsewhere.

Also, the syntax of that Settings.xml file is as follows:

<!--EDMServiceType identifies type of using EDM service;
0 - use local service,
1 - use any available service,
2 - use EDMServiceName service
3 - use any service from EDMServiceName replication group -->
<Connect EDMServiceType="0" EDMServiceName=""/>

Also, is this how you're confirming which AR server the Web application is connecting to?

Cheers!
Shawn

yes, so we use that xml file and point each web server to a specific AR app server.  So for instance webserverp01 points to appserverp01, webserverp02 points to appserverp02 and so forth:

for example, web server p01 xml:

<Connect EDMServiceType="2" EDMServiceName="appserverp01"/>