User Guide

10.5.0
- 10.5.3
- 10.4.0
- 10.2.3
- 10.2.2 HotFix 1
- 10.2.2
- 10.2.1
- 10.2

Back Next

Executing Projects

Several methods are available for executing Projects within

Managed File Transfer

. Users can execute Projects on-demand from within

Managed File Transfer

’s browser-based administrator. Projects can also be executed by the integrated Scheduler and File Monitor processes.

External applications can additionally launch Projects from other systems (Windows and Unix) by using

Managed File Transfer

’s commands and APIs, or by making HTTP(S) requests to the

Managed File Transfer

server.

Managed File Transfer

provides enterprise features for executing Projects including a job queue, multi-threading (to allow the concurrent execution of multiple Projects), priority settings, real-time monitoring and detailed logging.

Every execution of a Project is considered a

Job

. Listed below are the primary steps performed as jobs flow through

Managed File Transfer

After an authorized request is received to execute a Project, a Job will be created and assigned a unique job number.

A batch job initially starts in the

Managed File Transfer

job queue.

When

Managed File Transfer

is ready to run the job, it will advance the job from the job queue into the active subsystem to execute.

The job’s Project will then be compiled and executed by

Managed File Transfer

When the job finishes, a job log will be generated.

The completion status (along with any error messages) will be returned to the user or requesting application.

Rename Saved Search

Table of Contents

User Guide

User Guide

Executing Projects

Executing Projects