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

Compare with Current View Page History

« Previous Version 14 Next »

Scope

  • The system architecture explains
    • system boundaries
    • components
    • platforms
    • setup scenarios

System 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_System_Architecture.pdf" on this page

Basic System Architecture

Components

Secure Connections

Explanations

  • Components
    • JOC Cockpit: manage workflow configuration, monitor and control job execution
    • Controller: orchestrate Agents, manage job execution
    • Agents: execute jobs and return job execution history and log output
  • Operation
    • JOC Cockpit can be operated in the following modes:
      • as a standalone instance,
      • as a cluster with one active instance and any number of passive instances.
    • The Controller can be operated
      • as a standalone instance,
      • as a cluster with one active instance and one passive instance.
    • Agents can be operated
      • as a single instance,
      • as a passive cluster with one active instance and one passive instance,
      • as an active cluster with any number of active instances.
  • Network Connections
    • JOC Cockpit connects to Controller instances and connects to a database
    • Controllers connect to Agents
    • Network connections are firewall friendly, a single connection is initiated between each component
  • Platforms
    • JOC Cockpit: Windows, Linux
    • Controller: Windows, Linux
    • Agent: any platform that provides a Java Virtual Machine
  • Setup Scenarios
    • Standalone Server
    • Controller High Availability
    • Controller and JOC Cockpit High Availability
    • Multi-Client Capability












  • No labels