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

Managed File Transfer User Guide

Managed File Transfer User Guide

Connection Tab

Connection Tab

The Connection tab contains the following fields:
Port
The port number to use for connecting to the HTTPS server. If this field is left blank, then the default port number of 443 will be used.
User
The user name (login name) to use for connecting to the HTTPS server. This is only needed if the HTTPS server requires that the HTTPS client be authenticated using either the BASIC, DIGEST, or NTLM authentication schemes.
Password
The password to use for connecting to the HTTPS server. This is only needed if the HTTPS server requires that the HTTPS client be authenticated using either the BASIC, DIGEST, or NTLM authentication schemes. After entering the password, you can optionally click the
Encrypt
button, which will encrypt the password when it is stored in
Managed File Transfer
's database.
If you do not wish to store the password for the HTTPS server resource, the password can be supplied when executing a Project.
Is Password Encrypted
Indicates if the password is encrypted. Select
Yes
if you clicked the
Encrypt
button for the Password.
Connection Timeout
The maximum amount of time, in seconds, to wait when trying to establish a connection to the HTTPS server. A timeout value of 0 (zero) is interpreted as an infinite wait time. If the field is left blank, then the default value of 60 seconds will be used.
Read Timeout
The maximum amount of time, in seconds, to wait for a (read) response from the HTTPS server. A timeout value of 0 (zero) is interpreted as an infinite wait time. If the field is left blank, then the default infinite value of 0 (zero) will be used.
SSL Context Protocol
Specify the protocol to use when creating the SSLContext. The value you need to specify here depends on the security providers you have installed in the JRE (Java Runtime Environment). In most cases, the default value (SSL) should just work fine. However, on some IBM JRE implementations the default value would not work if the server you are connecting to does not support SSLv3.

0 COMMENTS

We’d like to hear from you!