Versions Compared

Key

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

...

Reports are created from predefined Report Templates. The templates individually implement which data will be processed when creating a report. Report Templates can be parameterized with the number of hits and the sorting (highest/lowest).

Reports are created from a Java class that can be configured to use Java options. It is recommended to use the -Xmx<number>m option to limit memory usage. The default value is Xmx64M. 

The memory usage depends on

  • The report template
  • The frequency, where frequencies with small interval like weekly consumes less memory than frequencies with large intervals like yearly.
  • The value for "hits".
  • The value for "Step overlap", where small values consumes more memory. The step overlap is configured for the templates "Top n periods with highest/lowest number of workflow/job executions"
  • The duration of job/workflow runs for the templates "Top n periods with highest/lowest number of workflow/job executions"
  • The number of different workflows/jobs, that are considered in the counting, e.g. for the number of failed workflows.
  • Then number of different agents for reports based on the template "Top n Agents with highest/lowest number of parallel job execution"
  • The setting is made in the setting JOC section with the item "report_java_options".

Example: The report for the template "Top n periods with highest/lowest number of workflow/job executions" will consume more memory when using the frequency "Yearly" instead of "Monthly" or with a step overlay of 1m instead of 60m.

Find below the list of Report Templates that ship with JS7.

...

  • A workflow execution is considered being failed if the order leaves the workflow with an unsuccessful outcome, for example if an order is cancelled or if a JS7 - Finish Instruction is used indicating unsuccessful outcome.
  • A workflow execution is not considered being failed just because some job failed, for example if a JS7 - Retry Instruction is used a later retry of a job can be successful. Instead, the resulting history status of an order is considered.

The

Report Template: Top n jobs with highest/lowest number of failed executions

...