Preface
Informatica Managed File Transfer Welcome Overview
- Managed File Transfer General Features
  - Workflow Automation
  - Ad-Hoc File Transfers and Collaboration
- Getting Started
  - Screen Tips
  - Login
Dashboard
Resources
Workflows
Task Reference
Services Overview
Users
Logs and Reports
Encryption
System
Appendix
Glossary Terms
- AES
- Asymmetric
- Asymmetric Cryptology
- Authentication
- Certificate
- Certificate Authority
- CIDR
- Cipher
- Cryptology
- CSV
- Decryption
- Diffie-Hellman/DSS
- Digital Signature
- DSA
- Element
- Encryption
- Fingerprint
- FTP
- FTPS
- Hash Function
- HTTP
- HTTPS
- ICAP
- Icon
- ISO format
- JCE Service Provider
- JDBC drivers
- JKS
- Key
- Key Alias/Key ID
- Key Pair
- Key Store
- MDN
- MMS
- Non-Repudiation
- Passphrase
- PKCS12
- Private Key
- Project
- Public Key
- Public Key Cryptology
- Public Keyring
- RSA
- Run Priority
- SAML
- Secret Key
- Secret Keyring
- Self-Signed Certificate
- SFTP
- Signing
- SMS
- SMTP
- SSH
- SSL
- SSO
- Symmetric
- Symmetric Cryptology
- URL
- Variable
- Verification
- XML

User Guide

10.2.2
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.1
- 10.2

Back Next

Clustering Prerequisites

The following are requirements for operating

Managed File Transfer

in a cluster.

All

Managed File Transfer

installations in the cluster must be on the same product version.

It is also recommended that the operating systems and Java versions match for each system for simplifying configurations.

The same folder locations must be specified for the Logs Directory, Documents Directory, WebDocs Directory as well as the Packages Directory when Secure Mail is enabled.

All systems must be configured to use the same external database (SQL Server, Oracle).

The system clock on each Participant system must be within five minutes from the system clock on the Coordinator system. This time is compared in UTC and ignores time zone differences between systems.

The cluster.xml file (located in [installdirectory]/config), needs to be configured to enable clustering.

: systemNameA unique name to identify this system in the cluster. The maximum system name length is 20 characters.
: clusterBindAddressThe IP address on which
Managed File Transfer
will use to communicate with other systems in the cluster. This IP address must be valid for the local system.
: clusterBindPortThe port number which
Managed File Transfer
will use to communicate with other
Managed File Transfer
systems in a cluster. For example, if the cluster bind port is 9006, the XML would look like <entry key="clusterBindPort">9006</entry>.
: clusterLogLevelThe log level of "info" will record all standard log messages from each system in the cluster. When the log level is set to "verbose" the log will also record all of the system-to-system messages used to manage the cluster.
: clusterEnabledThis must be set to "true" for
Managed File Transfer
to be cluster aware.
If using the
Managed File Transfer
Gateway for reverse proxy, the load balancing feature needs to be added to
Managed File Transfer
Gateway and the Load Balancer Rules configured in
Managed File Transfer
.
Additional cluster configuration information is available in the
Managed File Transfer
Installation Guide.

Rename Saved Search

Table of Contents

User Guide

User Guide

Clustering Prerequisites

Clustering Prerequisites