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

Template XML Schema Defined

The email template schema ensures the following:

The "root" element must be emailTemplate.

The "from" element is optional, but if it is specified, it must be the first element. If not specified, the email engine uses the From Name and Address from the

Managed File Transfer

Global Settings.

Must have at least one "to" element. Multiple "to" elements are permitted and will send the email to more than one recipient.

The "to" element may be followed by one or more "cc" or "bcc" elements. The "cc" element must be defined before the "bcc" element.

There must be one "subject" element.

If required, a "contentType" may be specified. The default is "text/plain."

There must be one "message" element that contains the body text for the email.

Optionally, there could be one or more "attachment" elements.

The schema also defines two data types for EmailAddress and Attachment. The EmailAddress data type is used by the "from," "to," "cc" and "bcc" elements. Each of these elements must contain the address attribute. These elements may also define a name attribute which is the person’s name.

The Attachment data type, must define the file attribute and an optional name attribute. If a "name" attribute is not specified, it defaults to the name of the file defined using the file attribute. The file attribute may contain an absolute path or a relative path. Relative paths are resolved relative to the installation directory of the product.

Rename Saved Search

Table of Contents

User Guide

User Guide

Template XML Schema Defined

Template XML Schema Defined