Preface
Introduction
- 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.3
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

Table Creation and Data Population

With the connection configuration complete, select how the Switch Database process will migrate the database. The first option will make a copy of the existing

Managed File Transfer

data to the new database. The second option will create a new database configured for use by

Managed File Transfer

with the default data, just as it was when it was first installed. The third option will not configure the new database or populate any data.

The third option is commonly used when configuring

Managed File Transfer

on a clustered, HA or DR system. These installations only need to point their connection to the Production database in use by the running system.

Rename Saved Search

Table of Contents

User Guide

User Guide

Table Creation and Data Population

Table Creation and Data Population