Configuration services
The FTM SWIFT configuration services are:
- A message flow that a configuration administrator can use to specify
and administer configuration data (for example, to define CTs, or
to specify the COs and attributes that comprise an OU).
Only a configuration administrator can carry out these actions. If dual authorization is used, a different configuration administrator must approve any changes before they can be deployed (see Dual authorization). The approval and deployment steps are recorded in the user audit log.
The configuration administration message flow is assigned to SYSOU.
- Two nodes, each of which can be embedded in any message flow,
and each of which adds configuration data required by other nodes
in the same message flow. These other nodes can then use this data
as a basis for decisions, for example, whether audit data is to be
recorded, or which queue or database table is to be used. Both of these nodes add the configuration data either to the MQRFH2 header of the message being processed, or to the environment of the message flow that processed the message:
- Configuration-data provider node (CPN)
- The decision as to where the configuration data is to be stored is made by the developer of the message flow. Use this node when the configuration data consists of predefined objects or the list of potential objects is small.
- Selective configuration-data provider node (SCPN)
- Where
the configuration data is stored depends on the structure of the message.
Use this node when:
- A small subset of a large amount of configuration data is required
- The required configuration data depends upon the content of the message
- The required configuration data is located in another OU, for example, in a system OU