installations (systems) to work together to provide file transfer services for the enterprise. This provides greater scalability by allowing workloads to be distributed horizontally across multiple
Managed File Transfer
systems.
If one
Managed File Transfer
system fails, the remaining systems in the cluster will automatically continue to process workloads and file transfer requests.
This active-active clustered environment also provides the best high availability option for handling potential system failures. If one
Managed File Transfer
system fails, the remaining systems in the cluster will automatically continue to service the trading partners.
The following features are available in
Managed File Transfer
when running in a cluster:
Two or more
Managed File Transfer
systems within a cluster can connect to the same external database at the same time. This allows these systems to share security settings, trading partner user accounts, configurations, audit logs and other product tables. The database can be configured or switched from any system in the cluster, in which the new database settings will be replicated to all systems in the cluster.
The System Name (specified in [InstallationDirectory]/config/cluster.xml) for each participant in the cluster will appear on the
Managed File Transfer
login screen, on the top-right corner of the dashboard and any cluster-related screens. This name will also be recorded in audit log records to indicate which system was servicing a trading partner's session during each event. The system name is accessible in Triggers using the event.systemName variable.
The Active Sessions screen displays all trading partner sessions (IP address, user name, login date, audit activity) for any system in the cluster. Within this screen, sessions can also be terminated (killed) on any system in the cluster.
Managed File Transfer
Gateway configurations can be viewed, updated, started and stopped from any
Managed File Transfer
system within the cluster.
Auto blacklist features for "Denial of Service" and "Brute Force" attacks are cluster-aware. This allows each
Managed File Transfer
system (in the cluster) to share security activity with each other to determine when to block attacking IP addresses from the cluster.
The Max Sessions setting for a Web User account will limit the total number of that user's sessions for all systems within the cluster. For instance, if the Max Sessions for a Web user is set to 2 and if they are logged into 2 different systems in the cluster, then they will not be able to open any additional sessions in the cluster at that time.
When setting up a cluster, you will need to install
Managed File Transfer
onto two or more servers. It is recommended that the Operating Systems and JRE versions on these servers to be the same for simplifying configuration.
The following diagram illustrates two instances of
Managed File Transfer
in a cluster, in which both instances are using a shared database and file system.