On the Core server, use PRIMARY.CLIENT.LOCATION Class instances to define the SAP priorities based on location criteria. The priority for a SAP is defined directly above the connection to that SAP instance in the SAPPRI attribute.
By default, the Core_RPS
and Core_RCS
instances are connected to the CLIENT.LOCATION._BASE_INSTANCE_ with priorities of 60 and 70, respectively.
Note: The priority values run low to high; the lower the number, the higher the priority. So, by assigning a lower number priority to Satellites, HPCA agents will attempt to connect to them as their preferred access points. They will use the Core (with a higher priority number) as the failover access point.
To connect the Core and Satellite SAP instances to a LOCATION Class Instance:
On the Core server, use the HP Client Automation Administrator CSDB Editor to set a priority for each SAP instance for each LOCATION Class Instance.
For example, the following image shows SAP Instances connected to the CLIENT.LOCATION._BASE_INSTANCE_
so that all HPCA agents will use the Satellites as the preferred access points.
CLIENT.SAP.PARISSAT3_RPS
Instance to the first available connection in the CLIENT.LOCATION._BASE_INSTANCE_
and give it a priority of 10.CLIENT.SAP.EUROSAT1_RPS
Instance to the second available “Connect To” connection and give it a priority of 20.CLIENT.SAP.EUROSAT1_RCS
Instance to the third available “Connect To” connection and give it a priority of 30.By giving the Satellite SAP instances higher priorities than the Core SAP instances, HPCA agents will first attempt to connect to the Satellites. If the Satellites are unavailable, they will attempt to connect to the Core.