Approving and deploying SAG configuration data
For example, to approve and deploy the SAG configuration for SAG1 in instance INST1:
When you issue the approve command, you approve the changes to the configuration data for SAG1 and all changes to the DNFSYSOU.
Similarly, when you issue the deploy command, you activate all approved changes to the configuration data for SAG1 and all changes to the OU. The deploy command also sends a request to the remote configuration-data provider service (DNI_RCP) to send the configuration data to the SAG Add-On. The DNI_RCP encrypts the configuration data. The SAG Add-On receives the configuration data and, if necessary, decrypts it, then configures the SAG accordingly.
The deployment of the SAG configuration data to the SAG is not immediate. It can take several minutes after you issue the deploy command.
The response from the deploy command returns for each SAG configuration entity only the information about whether the deploy succeeded or failed. Because only the FTM SWIFT event log contains information about the possible causes for a failed deployment, you must register to receive events from the SAG.
See approve and deploy for a description of these commands' syntax and parameters.
After you approved and deploye the SAG configuration, enable all configured entities in SAG as described in Enabling configured entities.