Versions Compared

Key

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

...

Expand
titleINVENTORY_INSTANCES
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
SCHEDULER_IDNOT NULLVARCHAR corresponds to the SCHEDULER_ID that is specified during installation of the JobScheduler instance
HOSTNAMENOT NULLVARCHAR host on which the JobScheduler instance has been installed
PORTNOT NULLNUMERIC 

TCP port that the JobScheduler instance is listening to

Status
colourRed
titleto be discussed

TCP, UDP Port in separate columns? yes

. Should not TCP port be specified then the UDP port is provided.

LIVE_DIRECTORYNOT NULLVARCHAR path of the live directory
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification
Expand
titleINVENTORY_FILES
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
INSTANCE_IDNOT NULLNUMERICForeign Key

references INVENTORY_INSTANCES.ID

FILE_TYPENOT NULLVARCHAR 

file types in use:

  • job
  • job_chain
  • order

file types not used:

  • process_class
  • config
  • lock
  • schedule
  • ...
FILE_NAMENOT NULLVARCHAR 

path from live directory

e.g. test/my_job.job.xml

FILE_BASENAMENOT NULLVARCHAR 

file base name

e.g. my_job.job.xml

FILE_DIRECTORYNOT NULLVARCHAR 

path calculated from the live directory

e.g. test

FILE_CREATEDNULLDATETIME UTC timestamp of the creation date of the file
FILE_MODIFIEDNULLDATETIME UTC timestamp of the modification date of the file
FILE_LOCAL_CREATEDNULLDATETIME local timestamp of the creation date of the file
FILE_LOCAL_MODIFIEDNULLDATETIME local timestamp of the modification date of the file
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification

...

Expand
titleINVENTORY_JOB_CHAINS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
INSTANCE_IDNOT NULLNUMERICForeign Key

references INVENTORY_INSTANCES.ID

used for simplified clean-up
FILE_IDNOT NULLNUMERICForeign Keyreferences INVENTORY_FILES.ID
START_CAUSENOT NULLVARCHAR 

the following start causes are available:

  • file_trigger
  • order...
  • Status
    colourRed
    titleTODO
    complete the list of start causes
NAMENOT NULLVARCHAR 

job chain name

e.g. test/my_jobchain for a given job chain path test/my_jobchain.job_chain.xml

BASENAMENOT NULLVARCHAR 

job chain base name

e.g. my_jobchain for a given job chain path test/my_jobchain.job_chain.xml
TITLENULLVARCHAR job chain title
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification
Expand
titleINVENTORY_JOB_CHAIN_NODES
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
INSTANCE_IDNOT NULLNUMERICForeign Key

references INVENTORY_INSTANCES.ID

used for simplified clean-up
JOB_CHAIN_IDNOT NULLNUMERICForeign Keyreferences INVENTORY_JOB_CHAINS.ID
NAMENOT NULLVARCHAR 

job node name:

  • file_order_source
  • job_chain_node

Status
colourRed
titleto be discussed

  • possibly add end nodes such as END_NODE ...?file_order_sink
ORDERINGNOT NULLNUMERIC ordering of node in job chain

STATE

NULLVARCHAR job node state as specified in the configuration
NEXT_STATENULLVARCHAR next state for an order in case of successful execution
ERROR_STATENULLVARCHAR error state for an order in case of unsuccessful execution
JOBNULLVARCHAR 

job reference name as specified in the job node configuration

e.g. ../my_job

JOB_NAMENOT NULLVARCHARForeign Key

corresponds to INVENTORY_JOBS.NAME. Paths are resolved to absolute values starting from the live directory

e.g. test/my_job

CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification
Expand
titleINVENTORY_JOB_CHAIN_ORDERS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
INSTANCE_IDNOT NULLNUMERICForeign Key

referencesINVENTORY_INSTANCES.ID

used for simplified clean-up
FILE_IDNOT NULLNUMERICForeign Keyreferences INVENTORY_FILES.ID
JOB_CHAIN_NAMENOT NULLVARCHARForeign Key

corresponds to INVENTORY_JOB_CHAINS.NAME

e.g. test/my_jobchain

ORDER_IDNOT NULLVARCHAR 

order identification (unique per job chain)

e.g. my_order for a given job chain order path test/my_jobchain,my_order.order.xml

TITLENULLVARCHAR order title

IS_RUNTIME_DEFINED

 

NOT NULLNUMERIC 

specifies if a start time has been configured:

  • 1: yes
  • 0: no
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification

...

  • The following tables are used to collect facts from the JobScheduler history.
  • No standalone jobs are given. Fact tables contain job chain starts exclusively.
  • These tables can be used These tables can be used to create individual reports.

...

...

colourRed
titleto be discussed
  • Use of a separate table REPORT_TRIGGER_CONFIGURATIONS for job chains including the PARENT_xxx columns?

 

Expand
titleREPORT_TRIGGERS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 

SCHEDULER_ID

NOT NULL

VARCHAR

 

corresponds to SCHEDULER_ORDER_HISTORY.SCHEDULER_ID

HISTORY_IDNOT NULLNUMERIC 

corresponds to SCHEDULER_ORDER_HISTORY.HISTORY_ID

NAMENOT NULLVARCHAR 

corresponds to SCHEDULER_ORDER_HISTORY.ORDER_ID

TITLENULLVARCHAR 

order title

corresponds to INVENTORY_JOB_CHAIN_ORDERS.TITLE

PARENT_NAMENOT NULLVARCHAR 

corresponds to SCHEDULER_ORDER_HISTORY.JOB_CHAIN

PARENT_BASENAMENULLVARCHAR job chain base name
PARENT_TITLENULLVARCHAR 

corresponds to INVENTORY_JOB_CHAINS.TITLE

START_TIMENOT NULLDATETIME 

corresponds to SCHEDULER_ORDER_HISTORY.START_TIME

END_TIMENULLDATETIME 

corresponds to SCHEDULER_ORDER_HISTORY.END_TIME

SYNC_COMPLETEDNOT NULLNUMERIC 

for use by the JobScheduler Reporting Interface jobs only:
specifies if a synchronization has been configured and has been completed successfully:

  • 1: yes
  • 0: no
RESULTS_COMPLETEDNOT NULLNUMERIC 

specifies if for use by the JobScheduler Reporting Interface jobs only:
specifies if all job nodes have been completed successfully:

  • 1: yes
  • 0: no
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification
Expand
titleREPORT_EXECUTIONS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
SCHEDULER_ID NOT NULLNUMERICForeign Key corresponds to SCHEDULER_ORDER_HISTORY.SCHEDULER_ID
HISTORY_IDNOT NULLNUMERICForeign Key corresponds to SCHEDULER_ORDER_HISTORY.HISTORY_ID
TRIGGER_IDNOT NULLNUMERICForeign Keyreferences REPORT_TRIGGERS.ID
STEPNOT NULLNUMERIC 

corresponds to SCHEDULER_ORDER_STEP_HISTORY.STEP

NAMENOT NULLVARCHAR 

corresponds to SCHEDULER_HISTORY.JOB_NAME

e.g. test/my_job

BASENAMENOT NULLVARCHAR 

job base name

e.g. my_job, for a given job path test/my_job.job.xml

TITLENULLVARCHAR corresponds to INVENTORY_JOBS.TITLE
START_TIMENOT NULLDATETIME 

corresponds to SCHEDULER_ORDER_STEP_HISTORY.START_TIME

END_TIMENULLDATETIME 

corresponds to SCHEDULER_ORDER_STEP_HISTORY.END_TIME

STATENOT NULLVARCHAR 

corresponds to SCHEDULER_ORDER_STEP_HISTORY.STATE

CAUSENOT NULLVARCHAR start cause for execution, can be mapped to an individual start cause by use of table REPORT_MAP_CAUSES
ERRORNOT NULLNUMERIC 

specifies if an error occurred:

  • 0: no error
  • 1: error
ERROR_CODENULLVARCHAR JobScheduler error code
ERROR_TEXTNULLVARCHAR error message
IS_RUNTIME_DEFINEDNOT NULLNUMERIC 

specifies if a start time has been configured:

  • 1: yes
  • 0: no
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification

...

Mapping Tables

  • The following tables are used for customization the mapping of reportsreport data. Users can add individual records that are used for the mapping of results in individual reports:
    • Mapping of start causes for jobs

 

Expand
titleREPORT_MAP_CAUSES
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
CAUSENOT NULLVARCHAR start cause as used by JobScheduler
MAPPED_CAUSENOT NULLVARCHAR individual mapping of start cause
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification

 

Custom Tables (Samples)

  • The following tables are used for customization of reports. Users can add individual records that are used for the mapping of results in individual reports:
    • Mapping of applications applications to jobsMapping of mandators to jobs
    • Mapping of start causes for mandators to jobs

 

Expand
titleREPORT_CUSTOM_APPS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
NAMENOT NULLVARCHAR application name
TITLENULLVARCHAR application title
Expand
titleREPORT_CUSTOM_JOBS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
NAMENOT NULLVARCHAR job name
TITLENULLVARCHAR job title
Expand
titleREPORT_CUSTOM_MANDATORS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
NAMENOT NULLVARCHAR mandator name
TITLENULLVARCHAR mandator title
Expand
titleREPORT_MAPCUSTOM_JOB_APPS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
JOB_IDNAMENOT NULLVARCHARForeign Key  corresponds to INVENTORYreferences REPORT_JOBS.IDNAME
APPLICATIONAPP_IDNAMENOT NULLNUMERICVARCHARForeign Key referencescorresponds REPORT_CUSTOM_APPLICATIONSAPPS.IDNAME
Expand
titleREPORT_MAPCUSTOM_JOB_MANDATORS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
JOB_CHAINNOT NULLVARCHARForeign Keyreferences REPORT_JOBS.ID
MANDATOR_IDNOT NULLNUMERICForeign Keyreferences REPORT_MANDATOR.ID


Aggregation Tables

Expand
titleREPORT_MAPTRIGGER_CAUSESRESULTS
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
CAUSENOT NULLVARCHAR start cause as used by JobScheduler
MAPPED_CAUSENOT NULLVARCHAR individual mapping of start cause

Aggregation Tables

SCHEDULER_IDNOT NULLVARCHAR corresponds to SCHEDULER_ORDER_HISTORY.SCHEDULER_ID
HISTORY_
Expand
titleREPORT_TRIGGER_RESULTS
 
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key corresponds to SCHEDULER_ORDER_HISTORY.HISTORY_ID
TRIGGER_IDNOT NULLNUMERICForeign Key

references REPORT_TRIGGERS.ID

START_CAUSENOT NULLVARCHAR 

references SCHEDULER_HISTORY.CAUSE of the first step

for the value order check the start cause given in INVENTORY_JOB_CHAINS.START_CAUSE

STEPSNOT NULLNUMERIC 

specifies the number of steps that have been effected:

  • SCHEDULER_ORDER_STEP_HISTORY.STEP of the last step or
  • 1 for standalone jobs

job steps that have been executed

ERRORNOT NULLNUMERIC 

specifies if an error occurred

  • 0: no error
  • 1: error
ERROR_CODENULLVARCHAR JobScheduler error code
ERROR_TEXTNULLVARCHAR error message
CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification
Expand
titleREPORT_EXECUTION_DATES
FieldNullableData typeConstraintDescription
IDNOT NULLNUMERICPrimary Key 
SCHEDULER_IDNOT NULLVARCHAR corresponds to SCHEDULER_ORDER_HISTORY.SCHEDULER_ID
HISTORY_IDNOT NULLNUMERIC corresponds to SCHEDULER_ORDER_HISTORY.HISTORY_ID
REFERENCE_IDNOT NULLNUMERICForeign Key

references REPORT_TRIGGERS.ID or REPORT_EXECUTIONS.ID

REFERENCE_TYPENOT NULLNUMERIC 

type of reference:

  • 0: references REPORT_TRIGGERS
  • 1: references REPORT_EXECUTIONS
START_DAYNOT NULLNUMERIC 

calendar day

e.g. 1

START_WEEKNOT NULLNUMERIC 

calendar week

e.g. 52

START_MONTHNOT NULLNUMERIC 

calendar month

e.g. 12

START_QUARTERNOT NULLNUMERIC 

quarter

e.g. 1

START_YEARNOT NULLNUMERIC 

year

e.g. 2015

END_DAYNOT NULLNUMERIC 

calendar day

e.g. 1

END_WEEKNOT NULLNUMERIC 

calendar week

e.g. 52

END_MONTHNOT NULLNUMERIC 

calendar month

e.g. 12

END_QUARTERNOT NULLNUMERIC 

quarter

e.g. 1

END_YEARNOT NULLNUMERIC 

calendar year

e.g. 2015

CREATEDNOT NULLDATETIME timestamp of record creation
MODIFIEDNOT NULLDATETIME timestamp of record modification