SAG configuration

The SAG configuration service (SAG_CFG) processes each request in one of the following ways:
Direct configuration
This approach is used for configuration commands that involve objects to which FTM SWIFT does not control access, such as SWIFTNet users, SWIFTNet user roles, and SWIFTNet user certificates. Such commands are passed directly from the CLI to the SAG Add-On. The SAG Add-On translates each command into an SAG primitive, and passes the primitive to the SAG. None of the corresponding configuration data is stored in the FTM SWIFT configuration database.
Direct configuration is used for the following actions:
  • Creating SWIFTNet users
  • Handling certificates of SWIFTNet users
  • Handling roles of SWIFTNet users
  • Acquiring certificates to SAG
  • Defining SWIFTNet users in SAG
  • Setting SNL protocol modes on SAG
Configuration via configuration objects
This approach is used for configuration commands that involve the following objects, to which FTM SWIFT controls access:
  • Message partners (including certificate and service lists)
  • Endpoints
  • Global parameters for the MQ Host Adapter (MQHA)
  • MQ connections
Such commands are entered using the CLI, and each one results in a new or modified configuration object (CO) being assigned to the OU DNFSYSOU.

As with all FTM SWIFT COs, the creation or changing of these COs must be deployed before they become active. The deploy command sends a request to the DNI_RCP service, which sends the configuration data for the CO to the SAG Add-On. If the configuration data exists and is different from the new data, the SAG Add-On checks whether the data is already in use by an external application. If the data is not in use, the SAG Add-On deploys the configuration data to the SAG; otherwise, it does not deploy the data and flags the deployment as having failed. If several COs are deployed as part of a single transaction, and if one or more of the deployments fails, the other deployments are carried out; however, the entire deployment transaction is flagged as having failed.

The information that indicates whether an SAG configuration entity changed or is in use by an external application is stored in an XML message in the reference information queue. This queue contains one such message for each FTM SWIFT instance that uses the SAG. These messages are created by the SAG Add-On when the data for the instance is initially deployed, and is updated during each subsequent deployment.