Table of Contents

Search

  1. Preface
  2. Informatica Managed File Transfer Welcome Overview
  3. Dashboard
  4. Resources
  5. Workflows
  6. Task Reference
  7. Services Overview
  8. Users
  9. Logs and Reports
  10. Encryption
  11. System
  12. Appendix
  13. Glossary Terms

Clustering

Clustering

Clustering allows two or more
Managed File Transfer
installations (systems) to work together to provide file transfer services for the enterprise. This provides greater scalability by allowing workloads to be distributed across multiple
Managed File Transfer
systems. The active-active cluster configuration provides high availability in that if one of the
Managed File Transfer
systems fail, then the remaining
Managed File Transfer
systems in the cluster will continue to process workloads and file transfer requests.
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 tables.
  • The System Name (specified in cluster.xml) will appear on the
    Managed File Transfer
    login page, on the top-right corner of the dashboard and any cluster-related pages. 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 page displays all trading partner sessions (IP address, user name, login date, audit activity) for any system in the cluster. Within this page, sessions can also be terminated (killed) on any system in the cluster.
    Informatica 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 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.
  • Batch jobs will be executed by any available systems in the cluster. If a particular system becomes too busy, other systems in the cluster will pick up any jobs from the job queue for execution.
  • The Active Jobs page will display all jobs which are executing across all systems in the cluster. Within this page, jobs can be held/released/cancelled on any system in the cluster.
  • File monitor jobs (for scanning folders) will be distributed evenly across all systems in the cluster to optimize performance.

0 COMMENTS

We’d like to hear from you!