Configure Pivot and Transfer DAL for the same domain with the source and target systems in a different ADAM realm

In this scenario, the source system and target systems are in the same domain but in different Active Directory Application Mode (ADAM) realms. A deployment system is typically in its own ADAM realm with no ADAM visibility to the production system.

For this scenario, a Remote_SSO configuration needs to be performed. The scenario for Configure Pivot and Transfer DAL for the same domain with the source and target systems in the same ADAM realm will also work with this Remote_SSO configuration.

Ensure Remote Client Service (RCS) service delegation is enabled for the system. For more information around installation, please contact AVEVA Customer Support.

To configure the Data Access Layer (DAL) for Pivot and Transfer in this scenario

Note: In the example files, ls1pdcdep system to ls1pdc system will be used.

1. Configure the source DAL file.

   For a list of configurable parameters and an example file, refer to Source Data Access Layer (DAL) file.

2. Configure the target DAL file.

   For a list of configurable parameters and an example file, refer to Target Data Access Layer (DAL) file.

3. Place the DALConfig_Source_DBEdit_SSO_PDC.xml source DAL file in the %DNADataRoot%\Shared\config\DAL\ls1pdcdep\control_room folder on the deployment server.

4. Place the DALConfig_Target_DBEdit_SSO_PDC.xml target DAL file in the %DNADataRoot%\Shared\config\DAL\ls1pdc\remote folder on the servers running the RCS service.

5. After the DAL files in the %DNADataRoot%\Shared\config\DAL\ls1pdc\remote folder are updated, restart the RCS service.