Environment
NetIQ Directory Resource Administrator 9.x
NetIQ Directory Resource Administrator REST Services 9.x
NetIQ Directory Resource Administrator REST Services 9.x
Situation
How does the DRA Win32 client discover a DRA server?
How does the DRA Delegation and Configuration console locate a DRA Server?
How does the DRA Account and Resource Management console locate a DRA Server?
How does the DRA Web Console locate and DRA Server and DRA REST Server?
How does the DRA Delegation and Configuration console locate a DRA Server?
How does the DRA Account and Resource Management console locate a DRA Server?
How does the DRA Web Console locate and DRA Server and DRA REST Server?
Cause
Every DRA Server and DRA REST will create a Service Connection Point (SCP) object. This SCP will be created in every domain managed by that specific DRA server. This object type stores basic information about the services offered by the DRA server.
The system container of AD will container two DRA specific sub containers. The DRA and REST Services will create these containers after a managed domain has been added. These services also check the status of the containers, and SCPs on service start up. The DRA Administration Server SCP object will be stored within the DRAServer sub container of the System container. The DRA REST Server SCP object will be stored within the RESTServer sub container of the System Container.
Each time a client attempts to connect to DRA, the client application (32bit installed or web) will perform a few checks before attempting to connect to a DRA Server
The system container of AD will container two DRA specific sub containers. The DRA and REST Services will create these containers after a managed domain has been added. These services also check the status of the containers, and SCPs on service start up. The DRA Administration Server SCP object will be stored within the DRAServer sub container of the System container. The DRA REST Server SCP object will be stored within the RESTServer sub container of the System Container.
Each time a client attempts to connect to DRA, the client application (32bit installed or web) will perform a few checks before attempting to connect to a DRA Server
- The client will determine what option is set for DRA Server location
- Use Automatic Discovery
- Use this Specific DRA Server
- If automatic discovery is chosen, the client starts the process of Server location
The client will determine the best DRA or REST Server using a specific set of steps
- The client will determine the AD membership for the Windows OS hosting the client
- The client will determine the AD Domain and AD Site membership
- When the client is Web Based, it will use the IIS Server AD Site membership
- The client query AD for the domain membership of the client OS
- The client will look in the system container for a DRA Servers container or REST Servers Container (if using the REST Web Console)
- The client will look for all SCPs listed in the DRA Servers or REST Servers Container
- The client compare the AD site details listed in the Keywords attribute for the SCP to the AD Site Details for the client OS
- The client will then determine the best available DRA Server whose AD site is the same as the client AD Site
Additional Information
Within the DRA REST Web Console, the ability exists to pre-populate a default value for both REST Server and HOST Server. These values are set on a per IIS Server basis. The end DRA user still has the ability to change the values each time they launch the DRA REST Web Console.
The 32bit Consoles (ARM & D&C) can have their client specific settings exported to an ARM file. This is a plain text configuration file that can be used by the 32bit console. This file can be distributed to the end users as needed.
The 32bit Consoles (ARM & D&C) can have their client specific settings exported to an ARM file. This is a plain text configuration file that can be used by the 32bit console. This file can be distributed to the end users as needed.