Please enable JavaScript to view this site.

Altova FlowForce Server 2021 Advanced Edition

» No topics above this level «

Monitoring Job Execution

Scroll Home Prev Top Next More

When a job meets the trigger criteria or when it is triggered on demand through a Web service call, an instance of that job starts running. The outcome of the job instance, its transition from one status to another, and other execution details are logged by FlowForce Server.

 

You can monitor the job execution progress in real-time or at a later date, from the Log View page. The recent and running jobs are also displayed in the Home page, as further illustrated below.

 

Note:By default, you can view the log of any jobs where you have "read" access. To view the global log of all jobs and events in FlowForce Server, your user account must have the View unfiltered log privilege.

 

Recent and running jobs

You can view the status of all currently running jobs in the Home page of the FlowForce Web administration interface, in the "Recent and Running Jobs" section.

fs_monitoring_jobs

The "Status" column reflects the job status as it was when the page was last refreshed. To get the latest status of all jobs, click the Reload Grid gui_refresh button. For reference to all the job instance statuses, see Job Statuses.

 

The grid displays also any recently finished jobs, including jobs that failed for whatever reason. Such jobs are displayed only for a short time (approximately 1-2 minutes) after their execution finished. You can always check the full history of each job instance from the Log page, see Viewing the Job Log.

 

When it starts, each job instance is assigned a unique ID that is displayed in the Instance ID column. The instance ID helps you subsequently track the execution status of each job instance, from the Log page. You can also click the instance ID inside the grid as the job is running—this redirects you to the Log page where you can view only the details pertaining to the selected job instance. If you would like to use to the job's instance ID in a job (for example, to create unique file names), this is possible with the help of the instance-id expression function.

 

If necessary, it is possible to stop running job instances by clicking the Stop job button. Note, however, that this may cause data corruption and should be done only exceptionally, see also Stopping Jobs.

 

If multiple FlowForce Server instances run as a cluster, the "Running jobs" table includes additional details about the cluster members running each job instance, see Monitoring Execution of Distributed Jobs.

 

Active timers

The "Active Timers" section of the page displays all active timer triggers.

 

Active Triggers and Services

To view all active job triggers as well as any jobs exposed as Web services, click Show all active triggers and services.

fs_active_triggers_services

The grid on the "Active Triggers and Services" page has the following columns:

 

Type - Indicates the type of the trigger (watch, timer, service). The label "watch" refers to either a file system trigger or an HTTP trigger, see the "Info" column for additional details.

Job - Specifies the path of the job where the trigger or the service is defined. Click the link to open the job's configuration page.

Next run - Applicable only for watch triggers. This column indicates when the trigger will run next.

Info - Provides additional information, such as the URL of the Web service, in case of jobs exposed as Web services. For watch or timer triggers, this column summarizes the current configuration of the trigger.

Service URL - Specifies the URL where the Web service exposed by the respective job is accessible. This is applicable only to jobs expose Web services.

 

Note:The "Active Triggers and Services" page is not refreshed automatically. Click the Reload Grid gui_refresh button to refresh the page.

© 2020 Altova GmbH