FTM SWIFT nodes
- The core function and its purpose. This helps you decide whether the service is applicable to a programming task.
- The prerequisites that must be met before you can use the service or node.
- The name of the service or node as part of the name of the interface queue that is supposed to
receive request messages.
Application should not directly access the service input queues, but should instead use interface queues. This ensures that an FTM SWIFT service processes and isolates workload for different organizational units independently.
For example, if an application wants to use the Remote Audit service in the FTM SWIFT instance INST1 with a transaction for bank BANKA, it must send the request to the alias queue INST1.BANKA.DNI_R_AUDIT. The message is routed to the appropriate queue.
You must know the names of the available instances, organizational units, and services to properly specify services in application programs. The names of the services provided with FTM SWIFT are shown in this book. For information about other services that are available, contact your system administrator.
- The properties of the node. You set the node properties in the message broker toolkit when you configure the node for use in a message flow.
- The structure of the message being processed by node.
- All elements containing input to the service or node. The allowed data type, cardinality, and description are listed for each element.
- A description of the major processing steps performed.
- All elements containing output from the service or node. The allowed data type, cardinality, and description are listed for each element.
- A description of the possible error conditions and the actions FTM SWIFT takes.