Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 9

changes.mady.by.user Mahendra Patidar

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Püschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

colour
Statustoc

Solution

...

 

Table of Contents

 

Introduction  

Download

  • Download the attached archive: 
  • Unzip the archive to the live folder of your JobScheduler installation
  • Create inbound, success and error directories
  • Adjust the configuration to your environment

Components

  • A job chain that monitors the directory for incoming files
  • A job that prints the name of the incoming file to stdout

Introduction  

This feature can be useful to dynamically process large number of incoming files, e.g. upload transactions into a database, convert meta files to PDF files, convert image file formats etc.. JobScheduler's File Order Source feature simplifies business processes that should be triggered on arrival of a file.

A job chain A job chains can be triggered by two type of Orders 1. time based Orders and 2. File Orders. A types of orders:

  • Time based orders
  • File based orders. By use of a File Order Source a job chain can be configured to start immediately on arrival of a file

...

  • in a directory.

A File Order Source require configured by minimum to parameters 1. Directory and 2. Regex, where Directory is the requires two parameters

  • Directory that specifies the file system location where JobScheduler should watch for

...

  • incoming files
  • Regex that is the Regular Expression that names of incoming files have to match to trigger the job chain. A most simple example of File Order Source is 
    <file_order_source directory="c:\sandbox\outgoing" regex="^test.txt$"/>

...

  • .

How to configure a job chain for a File Order Source

To learn how to create a job chain, refer following the article JobScheduler - Tutorial 2 - Editing a Simple Job with JOE. 

Image Added

 

Example: job chain  FileWatching - file order source 

...

  1. Open your job chain in JOE (JobScheduler Object Editor), expand job chain configuration by clicking on Job Chains --> FileWatching and click on Steps/Nodes.
  2. From right window pan select File Order Source tab.
  3. Click on New File Order Source, this will open a dialog to create a new File Order Source configuration.
  4. Click in the text filed in front of Directory parameter, configure directory which should  be watched for arrival of file e.g.
  1. c:\sandbox\outgoing.

...

  2. Click in the text field in-front of Regex parameter, configure file name or Regular Expression e.g. ^test.txt$.
  3. Click Apply File Order Source button to apply your  configuration.
  4. Click Save to save job chain.

Example: job chain - FileWatching 

Code Block
languagexml
titleFileWatchinng.job_chain.xml
<?xml version="1.0" encoding="ISO-8859-1"?>

<job_chain  title="File watching - file order source and regex" name="FileWatching">
    <file_order_source  directory="c:\sandbox\outgoing" regex="^test.txt$"/>
    <job_chain_node  state="100" job="show_file_name" next_state="success" error_state="error"/>
    <file_order_sink  state="success" remove="yes"/>
    <file_order_sink  state="error" remove="yes"/>
</job_chain>

 

Example: job - show_file_name

By default JobScheduler creates few internal environment variables during the Order processing. All the JobScheduler environment variables are prefixed by SCHEDULER_PARAMS_ prefix. JobScheduler stores the trigger file's path in environment variable SCHEDULER_PARAM_SCHEDULER_FILE_PATH In the following job example JobScheduler's inbuilt environment variable SCHEDULER_PARAM_SCHEDULER_FILE_PATH will be used to print file name on the stdout. 

Explanation

Following example is a Windows operation system FileWatching job chain example. Job chain FileWatching is configured to start as soon as the file test.txt arrives in the directory c:\sandbox\outgoing. The File Order will processed as a normal JobScheduler Order through job chain, one step to the next, until the Order reaches end node of job chain. In this example there are two distinct job chain end nodes, each one for success and error state of File Order processing. 

Example: job - show_file_name

Code Block
languagexml
titleshow_file_name.job.
Code Block
languagexml
<?xml version="1.0" encoding="ISO-8859-1"?>

<job  order="yes" stop_on_error="no" title="show file name" name="show_file_name">
    <script  language="shell">
        <![CDATA[
			@echo %SCHEDULER_JOB_NAME% : job starting			
            @echo .
@echo .
			@echo %SCHEDULER_JOB_NAME% :Start processing for file [ %SCHEDULER_PARAM_SCHEDULER_FILE_PATH% ].....
            @echo .
			@echo File Name :  %SCHEDULER_PARAM_SCHEDULER_FILE_PATH%			
			
@echo .
@echo %SCHEDULER_JOB_NAME% :End processing for file [ %SCHEDULER_PARAM_SCHEDULER_FILE_PATH% ] .....
@echo .
@echo .
        ]]>
    </script>
    <run_time />
</job>

How to configure File Order Source - job chain 

To learn how to create a job chain, refer following KB article TBD

Image Removed

 

...

Explanation
By default JobScheduler creates few internal environment variables during the Order processing. All the JobScheduler environment variables are prefixed by SCHEDULER_PARAMS_ prefix. JobScheduler store the trigger file's path in the environment variable SCHEDULER_PARAM_SCHEDULER_FILE_PATH. In the following job example JobScheduler's inbuilt environment variable SCHEDULER_PARAM_SCHEDULER_FILE_PATH will be used to output trigger file name on the console (stdout). 
How to configure File Order Sink - job chain
...
File Order Sink
Every File Order is associated with a file on file system, this file was used as trigger to start the job chain. JobScheduler offers two options to handle files associated with a File Order, Once a File Order reaches to the end success/error node of job chain, file . File associated with it File Order Source either can be remove or move to a locationdifferent directory on file system. 
Remove File
A file_order_sink node can be configured to remove file after processing e.g.( <file_order_sink state="success" remove="yes"/> ). If File Order Source's parameter remove=yes is set, file associated with the File Order will be deleted from file system location configured in  the directory parameterthe directory parameter.

Image Added
  1. Open your job chain in JOE (JobScheduler Object Editor), expand job chain configuration by clicking on Job Chains --> FileWatching and click on Steps/Nodes.
  2. From the right window panel select the Nodes tab.
  3. Click on state success, this will enable the dialog to configure the FIle Sink for success state.
  4. Select radio option File Sink.
  5. Select the check box Remove File to delete incoming files after successful processing. 
  6. Click the Apply Chain Node button to apply your configuration.
  7. Click Save to save the job chain.
  8. Repeat steps 3 to 7 for the error state too.
Move File
A file_order_sink node can be configured to move  file incoming files after processing to  another a different directory e.g.  (
<file_order_sink  state="success" remove="no" move_to="c:\sandbox\success"/>). File associated with the File Order will be moved from file system location configured in the directory parameter to the location configured in the move_to parameter. 
How to configure File Order Sink - job chain
Remove File
x
Move File
 
 
 Image Added 
  1. Open your job chain in JOE (JobScheduler Object Editor), expand job chain 's and configuration by clicking on Job Chains --> FileWatching and click on Steps/Nodes.
  2. From right wondow pan select the right window panel select the Nodes tab.
  3. Click on state state success, this will enable the dialog to configure FIle File Order Sink for success state.
  4. Select the radio option File Sink.
  5. Click in the text field in-front of Move to parameter, configure directory location where file should be move after successful processing  e.g. c:\sandbox\success.
  6. Click Apply Chain Node button to apply your  configurationconfiguration.
  7. Click Save to save job chain.
  8. Repeat steps 3 to 7 for the error state too.
Watching multiple directories
Watching multiple files
  1. .
Operation
To trigger the FileWatching job chain, create a file test.txt in the directory c:\sandbox\success. As soon as the file is created, JobScheduler will start the FileWatching job chain. You can check the job chain log with the Order History tab in the JobScheduler Operation Center (JOC).
See also
 
 x