JS7 JobScheduler

Space shortcuts

Page tree

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

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

  • The cluster architecture describes:
    • cluster operation
    • node distribution
    • site distribution

Cluster Architecture

Error rendering macro 'viewpdf'

com.atlassian.confluence.macro.MacroExecutionException: com.atlassian.confluence.macro.MacroExecutionException: The viewfile macro is unable to locate the attachment "JS7_JobScheduler_Cluster_Architecture.pdf" on this page

High Level Architecture

JS7 includes the following products:

  • The JOC Cockpit, which is used to manage the JS7 - Inventory of scheduling objects, to monitor and control workflow execution and to access the JS7 - History.
  • The Controller, which is used to orchestrate Agents, to deploy workflows and to pass orders for workflow execution to Agents.
  • Agents, which are dedicated to a Controller and are used to execute workflows and jobs. Agents can act autonomously for workflows that execute all included jobs with the same Agent.


JS7 products can be clustered:

  • JOC Cockpit and Controller can each implement a passive cluster with an active node and a standby node.
  • Agents can be operated standalone or as instances of a JS7 - Agent Cluster which implements active-passive or active-active scheduling.

Controller Cluster Operation

A Controller Cluster offers restart capabilities for fail-over and switch-over:

Controller Cluster of Two Nodes

Limited high availability is provided from a cluster using two nodes:

Controller Cluster of Three Nodes

A number of disaster scenarios are covered when using a cluster of three nodes:

Controller Cluster of Four Nodes

High availability for most disaster scenarios when loosing more than one node is covered by a cluster using four nodes:

Director Agent Cluster Operation

The Director Agent Cluster works similarly to a Controller Cluster:

Site Redundancy

Operating nodes for JS7 products from separate sites is a means to increase redundancy.

Redundancy of Two Active/DR Sites

Use of an Active Site and a DR Site allows the distribution of nodes for switch-over between sites:

Redundancy of Three Active Sites

Use of three Active Sites offers improved redundancy for fail-over and switch-over:



  • No labels