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 »



The JS7 includes three resources:

  • JOC Cockpit
  • Controller
  • Agent

The resource outage refers to the situation in which due to any condition the JS7 resources are not available. The effects of outage of JOC Cockpit and Controller is different as compared to an outage of Agent. The outage of the JOC Cockpit and Controller will not stop the execution of Workflows but the outage of the Agent will stop the execution of the workflows. 


JOC Cockpit Outage

JOC Cockpit is used to manage the inventory of objects and to handle, monitor the execution of workflows by the Controller or the agent. The outage to the JOC Cockpit does not affect the workflow execution by the controller or the agent. The outage to the JOC Cockpit effect:

  1. Monitoring of the workflows i.e user cannot open the logs of the workflows, cannot login to the JOC Cockpit and check the status.
  2. Managing the inventory i.e. user cannot edit the inventory like workflows, jobs and other objects.

The outage to the JOC Cockpit does not mean that the workflow execution will stop or the workflow running on the scheduled time will not run. As the workflows are executed by the Agent so the workflow will run as expected the only effect will be that this execution cannot be monitored from the UI. The workflow execution results will be updated Controller once the JOC Cockpit becomes available.


The SOS has performed the successful test with the scenario when the JOC Cockpit was not available for 24 hours and the Agent executed all the scheduled orders and when the JOC Cockpit was started again the results were updated.

Controller Outage

The Controller holds the job related configurations and orchestrates the number of Agents. The agent receives the workflow configuration from the Controller and returns the execution results to the Controller. Then the Controller passes those execution results to the JOC Cockpit which then updates them to the database. The communication between the Agents and the Controller is done by journals. All the information is stored in the respective journals. 

The outage to the controller will also not affect the execution of workflow as the workflow execution is done by Agent. The Agent will store all the information regarding the workflow execution in the journal and will later forward them to the Controller once it is available.  


The SOS has performed the successful test with the scenario when the Controller was not available for 24 hours and the Agent executed all the scheduled orders and when the Controller was started again the results were updated by Journals and were passed to the JOC Cockpit.

Agent Outage

The agent is the component in JS7 that executes the workflow and stores all the information in the form of journals and pass the results to the Controller. The outage of the agent affects the execution of the workflows. The workflow will not be executed if the agent is not available. But will execute all the outstanding orders when the agent is available.

The agent outage can be handled either by resolving the issue with the current agent or by moving the /state directory to the running agent. The journals for the agent are stored in the /state directory. So if we want the workflow execution of one agent to be forwarded to another agent then we need to copy the journals of the agent outraged to another agent.


So, if agent1 is  facing the outage and the agent2 is running (on the same server or another server) then follow the below steps to forward the execution of orders from agent1 to agent2:

  1.  Shutdown the services of agent2
  2. Copy the files from the state folder of agent1 to the state folder of agent2. 
  3. Start the services of agent2
  4. If the agent URL is the same for agent2 then the orders will be automatically started. But if the agent URL is changed then it has to be updated in the JOC Cockpit.
  5. To change the agent URL, login to the JOC Cockpit.
  6. From the profile select Manage Controllers/Agents.
  7. Make sure you edit the existing agent which is not in service as if we add a new agent then all the workflows need to be updated with the new Agent. So, edit the agent which is not available due to the outage.
  8. Change the agent1 URL to the agent2 URL and click Submit button:

The SOS has performed the successful test with the scenario when the Agent was not available for 24 hours and we copied the files from the state folder of agent1 to agent2. Changed the URL in the JOC Cockpit for the Agent. Then the agent2 executed all the outstanding orders from the previous day and also the new orders.


  • No labels