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

Upgrade Project

The Upgrade Project process converts an existing Project from version 1.0 to the new Project version 2.0. Project version 2.0 provides additional functions for manipulating values, flexible expressions and enhanced job controls. Projects created in this version of

Managed File Transfer

and later are automatically set at version 2.0.

The Project upgrade process is comprised of a few different steps. First, the Project is validated and then the user can select whether to make a backup of the Project before upgrading. It is highly recommended to make a backup of a Project to restore it later if the upgraded version produces undesirable results. Secondly, the upgrade process is performed and the user can choose to save the upgraded Project or cancel the upgrade.

During the upgrade, the following components will be modified in the Project:

Any Module with a "Depends On" setting will be updated with one or more Call Module Tasks. For example, if the Project's Main module depends on modules A and B, then the "Depends On" will be removed from the Main module and two Call Module tasks would be inserted to the beginning of the Main module (one to call module A and another to call module B).

Any expression used for conditioning, such as the "Execute Only If" statement, will be updated to use the new Expression syntax. For example, the previous syntax ${var1} ge ${var2} will be converted to the new expression of ${var1 ge var2}.

RowSets using the column name, instead of the column index, will be converted in the upgrade process to place quotes around the column name (for example, ${data[columnName]} becomes ${data["columnName"]}).

Variables, module names and resource names will no longer be case sensitive.

When the upgrade is complete, an Upgrade Log is displayed. The Upgrade Log displays any issues encountered while upgrading the Project and provides options to Download the upgrade log in text format, Save and Finish the Project upgrade process, or Cancel the upgrade.

Follow the steps below to upgrade a Project:

From the main menu, select

Workflows

and then click the Projects link.

Click the

Action icon and then click

Edit

icon.

In the Project page, click the

Upgrade Project link in the page toolbar.

On the Upgrade page, complete the required fields and then click the

Upgrade

button.

The Upgrade Project process starts and when complete, an Upgrade Log is displayed.

It is strongly recommended that you test the upgraded Project to ensure it behaves as expected.

Rename Saved Search

Table of Contents

User Guide

User Guide

Upgrade Project

Upgrade Project