Introduction

This section gives a brief detail on TAFC servers and their initialization checks.

In a multi-application server architecture, Temenos Transact is deployed as an application cluster with one database server and multiple TAFC application servers. Before a server goes online, it can make a number of initialization checks. These confirm that the server’s internal configuration is sufficient to successfully run TAFC.

A server can also pole for other TAFC server instances and confirm that their configuration is compatible with its own.

A context name set in the TAFC_CONTEXT environment variable identifies each cluster. Servers attempt to communicate with other servers from the same cluster.

Generally, each server is run on a separate machine. However, there is no reason why more than one instance (for the same or different contexts) should not be run on a given machine. In this user guide, the term remote refers to another server instance even if it happens to be co-located.