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 HotFix 1
- 10.5.3
- 10.5.0
- 10.4.0
- 10.2.3
- 10.2.2
- 10.2.1
- 10.2

Back Next

Schedule Tab

The Schedule tab contains the following settings:

Trigger Type: The type of schedule this job should use. The trigger types are explained below:
One time - The job will run once at the indicated start date and time.
Startup - The job will run once whenever the
Managed File Transfer
application is started.
Minutely - The job will run every X minutes.
Hourly - The job will run every X hours.
Daily - The job will run every X days.
Weekly - The job will run every X weeks, in which additional settings can be specified.
Monthly-The job will run once a month, in which the day of month can be specified.
Start date: The date that the Scheduled Job should first run.
Start Time: For trigger types of One Time, Minutely, Hourly and Daily. The time that the Scheduled Job should first run.
Run Every: For trigger types of Minutely, Hourly, Daily and Weekly. The number of units to wait between each execution of the Scheduled Job. The valid range is 1 to 999. The unit type (weeks, days, hours or minutes) depends on the trigger type selected.
End Date: For trigger types of Minutely, Hourly, Daily, Weekly and Monthly. Optional: The date/time that the Scheduled Job should stop running. Leave this option unchecked to schedule a job that does not have an end date.
Days to Run: For trigger type of Weekly. The days of the week (Sun, Mon, Tue, etc.) this Scheduled Job should run.
Run At: F or trigger types of Weekly and Monthly. The time of day this Scheduled Job should run.
Day of Month: For trigger type of Monthly. The day of the month (1st, 2nd, 3rd, etc.) which this Scheduled Job should run.
Day of Week: For trigger type of Monthly. The week of the month (first, second, etc.) and day of the week (Sun, Mon, etc.) this Scheduled Job should run.
Holiday Calendar: For trigger types of Daily, Weekly, Monthly. The drop-down list provides a list of available holiday calendars that were created on the Manage Calendars page.
Holiday Rule: For trigger types of Daily, Weekly, Monthly. The action taken by the scheduled job when the next runtime falls on a holiday.
Skip - The scheduled job cycle is skipped and runs as scheduled after the holiday.
Previous Business Day - The scheduled job cycle will run a day before the holiday.
Next Business Day - The scheduled job cycle will run a day after the holiday.
Advanced Options: After the Scheduled Job runs, indicate if it should repeat itself for a period of time. This advanced option is like having a schedule within a schedule. This could be used for repeatedly calling Projects that only need to run during certain periods of the day. If the scheduled job uses a holiday calendar and executes the day before a holiday, the repeat options can cause the job to continue executing into the holiday.
The valid repeat options are:

Do not repeat
Repeat Always
The next execution time of a repeating job will be based on when the current execution finishes (not when it started). For instance, if a job execution finishes at 9:02am, and if the Run Every parameter is set to 5 minutes, then the next execution time for the job will be 9:07am

Repeat only when the project fails
Repeat only when the project succeeds
Repeat only if the specified condition evaluates to true
When specifying the condition that would evaluate to true, the value can be composed of another variable. If using a variable, type the name of the variable and not the variable syntax (for example, variableName instead of ${variableName}).
If a Repeat option is selected, you can indicate how long the Scheduled Job should repeat and how long the delay should be between repeats.

Example #1: You could set up a scheduled job that runs every day by specifying the Daily trigger type. Lets say the Start Time is set for 9:00 am and the advanced option is set to Repeat Always for 2 hours with a 5 minute delay between executions. With this example, the Scheduled Job will first run at 9:00am. If the job takes 2 minutes to run, then it will repeat again at 9:07am, then again at 9:14am, and so on, until 11am (when the 2 hours expires). This entire sequence would be repeated each day of the week.

Example #2: You could set up a scheduled job that runs every Monday using the
Weekly
trigger type. Lets say the
Start Time
is set for 1 pm and the advanced option is set to
Repeat only when the project fails
for 3 hours with a 10 minute delay between executions. With this example, on Monday, the Scheduled Job will first run at 1 pm. If the Project takes 1 minute to run and if it fails, then the Scheduled Job will repeat again at 1:11 pm. If it fails again, then it will repeat again at 1:22pm, and so on until 4 pm (when the 3 hours expire). This entire sequence would be repeated the next Monday.

Rename Saved Search

Table of Contents

User Guide

User Guide

Schedule Tab

Schedule Tab