Table of Contents

Search

  1. Preface
  2. Introduction
  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

Configure the Gateway Parameters

Configure the Gateway Parameters

The Gateway Configuration page contains the operating parameters and service mappings for
Managed File Transfer
Gateway.
Configure the Gateway parameters and service mappings for
Managed File Transfer
Gateway.
The following table describes the Gateway Configuration parameters:
Gateway Configuration parameter
Description
Enabled
Indicates whether Informatica Managed File Transfer Gateway is enabled.
By default, Informatica Managed File Transfer Gateway is disabled.
Automatically Start
Indicates whether Informatica Managed File Transfer Gateway connection is started automatically when Informatica Managed File Transfer starts.
Controller Address
The IP address of the server running the Informatica Managed File Transfer Gateway server component. The IP address must match the controller address defined in the
gateway.xml
file on the Informatica Managed File Transfer Gateway server.
Controller Port
The port on which Informatica Managed File Transfer Gateway listens for incoming control connections. The default port is 9100 and must match the port defined in the
gateway.xml
file on the Informatica Managed File Transfer Gateway Server.
Minimum Number of Threads
The minimum number of threads reserved for connections to Informatica Managed File Transfer Gateway.
Default is 10.
Maximum Number of Threads
The maximum number of threads that can be used for connections to Informatica Managed File Transfer Gateway. This determines the maximum number of simultaneous requests that can be handled.
Default is 500.
Changing the thread values can alter the performance. Modify the thread values to obtain the optimal performance for your configuration requirements.
Thread Keep Alive Time
The amount of time that an idle thread waits before it is released.
Default is 60 seconds.
Increasing the value might cause a higher CPU and memory usage on the server. However, the connections start faster because they do not need to create new threads frequently.
Service Mappings
Each service such as lFTP, FTPS, HTTPS, and SFTP is mapped from Informatica Managed File Transfer Gateway to the corresponding service in Informatica Managed File Transfer. When a control connection is established, the mappings are sent to the Informatica Managed File Transfer Gateway server.
Informatica Managed File Transfer Gateway listens for incoming connections on the
From Address
and
From Port
for each service mapping.
When a connection occurs, Informatica Managed File Transfer Gateway forwards the traffic to Informatica Managed File Transfer based on the
To Address
and
To Port
service mappings.
If more service mappings are needed, for example, more than one listener for a particular service, click the
Add Service Mapping
link to add a new service mapping entry row. If a service mapping is no longer needed, click the icon to delete the corresponding service mapping.
Add service mapping
The Add service mapping contains the following parameters:
Label
An identifier for the service mapping.
From Address
The IP address that Managed File Transfer Gateway uses to listen on for incoming traffic. Optionally leave the From Address field blank to use the Controller Address as the bind address for client connections on that particular mapping.
From Port
The port that Managed File Transfer Gateway uses to listen on for incoming connections. The standard ports are 21 for FTP, 990 for FTPS, 22 for SFTP, and 443 for HTTPS/AS2.
To Address
The IP address of the local Managed File Transfer system.
To Port
The port that the service listener uses for a specific service on the Managed File Transfer system.
Load Balancer Rule
The Managed File Transfer Gateway uses the Load Balancer Rule to configure the load balancing for each service mapping. This rule is defined in Managed File Transfer Gateway and should be round-robin for FTP, FTPS, and SFTP protocols. For HTTPS, the Load Balancer Rule should be IP-based round-robin that routes traffic from specific IP addresses for a period of time to a single system.
By default, use the
default
rule for FTP, FTPS and SFTP.
Use the
https
rule for HTTPs and AS2.
Changes made to the Service Mappings take effect the next time the connection to the Managed File Transfer Gateway is reset.
To reset the connection, click the
Disconnect
button and then the
Connect
button on the
Gateway Manager
page. For more information, see Gateway Manager.
The following image shows the
Gateway Configuration
page:
The image shows the Gateway Configuration page.

Back to Top

0 COMMENTS

We’d like to hear from you!