You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Introduction

JobScheduler has a full JADE managed file transfer program "on board". This allows JobScheduler to be used to automate file transfer operations using the full features of JADE such as error detection, compliant logging and notifications.

JADE can be accessed from the JobScheduler using one of the JADE JITL jobs, via the JADE API. The JITL jobs are pre-configured job templates that can be used to rapidly develop job scheduling operations and are provided as standard with every JobScheduler installation package.

The configuration and use of a simple JITL job was described in JobScheduler - Tutorial 4 - Editing and Running a JITL Job: the current tutorial will build on the information provided in the Editing and Running a JITL Job tutorial and show how to configure, run and test simple file transfer operations. Users should then be able to build on this information to complete their own real-life transfer operations.

Background

The screenshots used in this tutorial were made using JobScheduler 1.9.x. All operations described have also been tested with 1.8.x. VERIFY

This tutorial assumes that a JobScheduler has been installed and is running. See for information about the requirements for the installation of JobScheduler and instructions about the installation procedure itself.

This tutorial describes how to configure the JobScheduler JITL job to carry out a relatively simple file transfer operation. The operation described has already been used in the JADE file transfer tutorial, which described how to transfer files from the online SOS demo server to the local file system. The demo server server allows read-only FTP and SFTP access and has been installed to allow users get their JADE and JADE JITL job users get their systems up, running and tested as quickly as possible.

Note that to get the file transfer operation described in this tutorial up and running, your firewall(s) will need to allow file transfer via ports 21 (for FTP) and 22 (for SFTP).

A separate installation of JADE is not required for this tutorial.

 

Configuration of the JADE JITL job

Initial steps

The first three steps have already been described in detail in the JobScheduler - Tutorial 2 - Editing a Simple Job with JOE tutorial and are therefore only summarized here:

  1. Start JobScheduler
  2. Open the JobScheduler Object Editor (JOE)
  3. Open the JobScheduler Live Folder:
    1. A sub-folder of the live folder is used In this tutorial for all the objects related to the tutorial, "tutorials-5-jade-jitl-job".
      A link to a download file containing the contents of this file will be provided at the end of this article.
  4. In the left hand pane of JOE mark the Jobs icon - opening the JobScheduler icon if necessary.
  5. Start the Wizard function by clicking on the Button of the same name as shown in the screenshot below.



  6. Select Order controlled job in the small window that opens and then Next, which will open the Import Jobs window as shown in the next screenshot.
    1. Enter a Jobname such as jitl_job_1.
    2. In the Jobs pane, scroll down until the two JADE-Jobs are visible and select the job with the jadeJob.xml file name.
      This will cause the Title field to be filled with "API Job for JobScheduler ...."
    3. Click on the Next button



  7. The Job Parameter form for the JITL job will now open.
    • The use of this form to set and modify parameter values was described in detail in Tutorial 4 - Editing and Running a JITL Job.
      This form is shown in the screenshot below, where it can be seen that parameters have already been selected and set.
    • Note that the parameter names specified in the Wizard are not identical with those set in the JADE file transfer tutorial. This JITL job Wizard still uses deprecated names without source_ or target_ prefixes. This means that the Wizard cannot be used to directly configure a file transfer from a remote source to a remote target. However this type of file transfer can be configured using a profile in a settings file, both of which can be specified using the profile and settings parameters, which are available in the Wizard. The use of a profile and settings file has already been described in the JADE file transfer tutorial and this method of configuration for this JITL job will be described below.
    • The parameter values specified here and shown in the screenshot below are identical with those described for the JADE file transfer tutorial with the exception of the local_dir parameter, which in the JADE tutorial had the value ${USERPROFILE}\jade_demo\a.
      In the JITL job the User depends on the JobScheduler configuration and therefore the value for the local_dir parameter is specified absolutely.



    • Note that this Job Parameter Wizard form can be directly opened from the Job Parameter form in JOE as can be seen in the following screenshot:



  8. Create new job chain for the job:



  9. Add the job to the job chain along with two end nodes as shown:



  10. Create and configure an order for the job chain:



  11. Don't forget to save the configuration using the button as shown:



  12. Start the Order in JOC, the JobScheduler Operations Center using the Order menu button as shown



  13. Open the log file after the order has run using the Show Log link as shown in the next screenshot:



    The screenshot below shows a extract from the log file for this order and the detailed log information that is available for JADE file transfer operations:



    As can be seen from the log file, seven files have been copied to the ...\jade_demo\a folder. These were all the files in the remote folder as a filter was not used to select particular files.

Use of a profile and settings file

The JADE JITL Job can also be configured to use one or more file transfer configurations specified in the form of a settings.ini file and profile(s) as used in JADE up to Release 1.10 of JADE and JobScheduler.

This is described in the next tutorial.

Error handling, notifications and monitoring

Error handling, notifications and monitoring for the JADE JITL job can be handled on two levels:

  • using standard JobScheduler error handling, notifications and monitoring,
  • using the JADE error handling and notifications

JobScheduler error handling, notifications and monitoring

Error handling

The JobScheduler comes with a number of methods for error handling. These include:

  • stop a job: running orders have to wait for the job to become available
  • suspend an order: the order waits to be resumed later on
  • setback an order: make an order repeatedly try to continue processing after a predefined time interval
  • make an order leave a job chain
  • make an order continue processing with a specific job node for error handling

See the Error handling article for a list of links to articles describing these features in detail.

Notifications

JobScheduler comes with its own mail client which it can use to send notifying e-mails in the event of, for example, jobs ending in error.

See the Notifications article for a list of links to articles describing the notification features in detail.

Monitoring

JobScheduler can be monitored by System Monitors. Such products include e.g. HP OpenView®, Microsoft SCOM®, Nagios®, op5®, Opsview®, Zabbix® etc.

As System Monitors are restricted to check the availability and performance of a monitored service the JobScheduler provides additional functionality for System Monitors to report on individual job failure and recovery. The JobScheduler Monitoring Interface can be used with any System Monitor that provides a command line tool for passive checks.

See the Monitoring article for a list of links to articles describing the monitoring features in detail.

JADE error handling and notifications

Error handling

JADE has a limited number of parameters that can be used to provide error handling:

  • transactional and atomic file transfer
  • check_size
  • force_file
  • raise_error_if_result_set_is

Definitions for these parameters are provided in the JITL Job Wizard Job Parameter form.

Notifications

The JADE JITL job can send e-mails when file transfer events have taken place::

  • on success (mail_on_success)
  • on error (mail_on_error)
  • on empty files (mail_on_empty_files)

Note that the exact definitions of these parameters are not available in the lower pane of the JITL Job Wizard Job Parameter form. In addition, with the change over to XML-based configuration in release 1.11, the legacy (i.e. settings.ini file based configuration) JADE parameter reference has been withdrawn. However a Parameter Mapping is available showing the settings.ini file parameter names and their corresponding XML-based ones. The XML names can then be used to access the new JADE Parameter Reference.

E-mails are configured in the JADE JITL job with a number of parameters whose (legacy) names begin with ftp_file_notification - e.g.  ftp_file_notification_to, ftp_file_notification_bcc, etc .

Exact definitions of these parameters can be found in the XML-based parameter reference under their new names - in this case to, bcc, etc.

Scheduling the Job

To Be Done TODO

Further documentation

JADE JITL job

As can be seen from the screen shot of the Job Parameter form above, documentation for individual JITL job parameters is shown in the lower pane of the Wizard Job Parameter form.

In addition, the full job documentation is provided alongside the job definition. This is an XML file (jadeJob.xml) and can be found in the JITL jobs folder in the JobScheduler installation Program Data jobs directory. On a Windows 7/8 installation with default settings this would be:

  • C:\ProgramData\sos-berlin.com\jobscheduler\scheduler_ID\jobs where scheduler_ID is the ID given to the JobScheduler. 

The full documentation for the JADE JITL job can also be found in the SOS Product Knowledge Base.

JADE parameters

To Be Done TODO

 

  • No labels