Instance

A group of FTM SWIFT servers that share the same runtime database, the services they provide, and the OUs on behalf of which they operate, form an FTM SWIFT instance. A system can contain any number of FTM SWIFT instances. For example, you might want to use one instance for test purposes, and several other instances for production purposes.

Each instance must contain the following components:
  • At least one FTM SWIFT broker server
  • Exactly one FTM SWIFT system OU (SYSOU)
  • At least one business OU
  • A set of initial services used for FTM SWIFT system administration

If additional services are installed, additional system OUs might be required. For example, the services used to transfer messages or files via the SIPN require their own system OU, which has the name DNFSYSOU.

Each instance contains exactly one broker server that is designated as the primary server. All resources that must be deployed exactly once per instance or once per OU are deployed on the primary server.

A single application can use the services of more than one instance, and more than one application can use the services of a single instance. The method of dispatching messages employed by FTM SWIFT ensures that each message is passed to the correct instance.

Each instance can contain any number of servers of all types, and any number of OUs. An FTM SWIFT instance containing more than one broker server can span any number of z/OS® operating systems. Running several servers in a single instance on more than one system:
  • Increases throughput, because each additional system provides additional processing power
  • Improves availability, because if one broker server fails, the others assume its workload until it can be restarted
Servers can be made to share their workloads by using an IBM® MQ cluster.
Each instance is configured and operated independently of the others, runs independently of the others, and shares no data with the others. Therefore:
  • Each FTM SWIFT instance must use a separate set of integration nodes.
  • Each FTM SWIFT instance must use a separate DB2® schema.