Customization definition
- The name of an FTM SWIFT instance
- Which servers are to provide services for that instance
- Which OUs are to use services for that instance
- Which services are to be available to each combination of server and OU
- A value for each placeholder
- Which BAR files are assigned to each execution group
- A customization definition report, which describes the servers, OUs, and services of the instance, and how they are distributed within the instance
- Deployment data, which comprises the resource files needed to create the resources required by the instance
- Deployment instructions, which describe how to execute the resource files, and thereby deploy, on the runtime systems, the resources required by the instance
- A BAP Definition Document (BTDD), which the BAP uses to deploy BAR files to brokers
The resource files reflect the data recorded during customization definition about which OUs are to use the services, and in which servers the services run. For example, resource files that are used to create the queues required by an OU use the OU name that was specified during customization definition to create queues with names that contain, as a qualifier, the name of the OU.
This automatic substitution of values, and the taking into account of which OUs use services and in which servers the services run, makes it easier for you to adapt the services to your environment.
How service bundles are distributed among servers depends on your availability, scalability, and performance requirements of the services they contain. For example, to ensure a higher level of availability, deploy service bundles that contain critical services to more than one server.
Figure 1 shows an example of a typical setup containing services provided by FTM SWIFT.
