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

Compare with Current View Page History

Version 1 Next »

Introduction

The JITL FileOrderVariablesJob template can be used to read variables from incoming files that are subject to JS7 - File Watching.

  • The job template is used to switch-over between active and passives cluster instances of JOC Cockpit, Controller and Agents.
  • The job template cannot be used for standalone instances of JOC Cockpit and Controller.

FEATURE AVAILABILITY STARTING FROM RELEASE 2.4.0

Usage

When defining the job either:

  • invoke the Wizard that is available from the job properties tab in the Configuration view and select the JITL FileOrderVariablesJob and relevant arguments from the Wizard

or

  • specify the JITL job class and com.sos.jitl.jobs.fileordervariablesjob.FileOrderVariablesJob Java class name and add arguments specifying the variables that are expected to be carried by incoming files.

Example

Download (upload .json): pdMaintenanceWindow.workflow.json

You can use the job wizard like this:


Explanation:

  • Add an empty job from the instruction panel.
  • Specify a name and a label for the job.
  • Select an Agent.

In a next step invoke the job wizard that you find in the upper right corner of the job property editor. The wizard brings up the following popup window:


Explanation:

  • From the list of available job templates select the MaintenanceWindowJob.

Then hit the "Next" button to make the job wizard display available arguments:


Explanation:

  • Required arguments include the state argument to specify 
    • inactive:  indicates a switch-over by which the component is set to the inactive state.
    • active:  indicates a switch-back by which the component is set to the active state.
  • The controller_host and joc_host arguments specify the host name of the Controller and JOC Cockpit for switch-over or switch-back.
    • One of the arguments can be used and both arguments can be used.
    • The controller_id argument has to be used if the JOC Cockpit is connected to more than one Controller. The Controller ID is the unique identifier of a Standalone Controller or Controller Cluster.
  • The agent_ids and subagent_ids arguments specify Agents that should be disabled during switch-over and enabled during switch-back.
  • The controller_host, joc_hostagent_ids and subagent_ids arguments can be used at the same time to perform switch-over and switch-back operations for all components from a single job.
  • Select the check box provided with each argument if you want this argument to be added to the arguments of the MaintenanceWindowJob template.

When hitting the Submit button the wizard adds the required arguments to the job which should look like this:

Documentation

The Job Documentation including the full list of arguments can be found under: https://www.sos-berlin.com/doc/JS7-JITL/MaintenanceWindowJob.xml

The MantenanceWindowlJob class accepts the following arguments:


NameRequiredDefault ValuePurposeExample
stateyes

Desired state of the JS7 component: 

  • inactive:  indicates a switch-over operation by which the component is set to the inactive state.
  • active:  indicates a switch-back operation by which the component is set to the active state.
inactive

controller_id

no

Specifies the identifier of a Standalone Controller or Controller Cluster

  • if the controller_host argument is used and
  • if the JOC Cockpit is connected to more than one Controller.
controller_prod

controller_host

no

Specifies the host name of the Controller should a switch-over or switch-back operation for a Controller be performed.

controller-2-0-primary

joc_host

no

Specifies the host name of the JOC Cockpit instance should a switch-over or switch-back operation for JOC Cockpit be performed.

joc-2-0-primary
agent_idsno
Specifies the unique identifiers of Agents that should be disabled during switch-over and enabled during switch-back operations.
subagent_idsno
Specifies the unique identifiers of Subagents that should be disabled during switch-over and enabled during switch-back operations.

Further Resources



  • No labels