Date: Fri, 29 Mar 2024 06:20:57 +0000 (UTC)
Message-ID: <699349925.12463.1711693257537@change.sos-berlin.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_12462_1136478578.1711693257537"
------=_Part_12462_1136478578.1711693257537
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Introduction=
The Controller's journal holds information about scheduling objects such=
as workflows, jobs and orders:
- scheduling objects are deployed from JOC Cockpit to a Controller.
- orders are submitted to indicate the start time of workflows.
The Controller's journal is available from a number of files in the foll=
owing location:
- Unix:
/var/sos-berlin.com/js7/controller/state
- Windows:
C:\ProgramData\sos-berlin.com\js7\controller\state
- Users can choose different locations when setting up a Controller.
When a Controller's journal is deleted or damaged then this indicates se=
vere loss:
- Consider that loss of a Controller's journal means that:
- any scheduling objects such as workflows have to be re-deployed,
- any orders of the Daily Plan have to be re-submitted,
- any currently running orders are lost and no information about orders a=
nd the execution status of jobs is available.
- See also the JS7 - FAQ - What happens to workflow=
s in case of outage of a Controller article.
- The use of a Controller cluster will leverage such a situation as the s=
tandby Controller instance operates a synchronized copy of the journal. The=
standby Controller instance will pick up operations immediately durin=
g fail-over after 3-5s. The failed Controller instance can then be started =
later on and will automatically synchronize with the then active Controller=
instance.
Initial =
Operation
Issues occurring during initial operation are described in the JS7 - How to troubleshoot Controller Cluster Initial Operation=
article.
Ongoing =
Operation
The scenarios in this section apply after a Controller has been successf=
ully registered with JOC Cockpit during JS7 - Initial Operation.
L=
oss of Controller Journal
- Problem: If initial operation has been suc=
cessfully completed for a Controller and due to some weird reason the Contr=
oller instance's journal is deleted later on then the Controller has to be =
registered once again from the JOC Cockpit.
- Solution: This problem can be resolved by =
restarting the Controller. The Controller will start a new journal. In the =
JOC Cockpit "Manage Controllers/Agents" page use the "Edit" action menu of =
the Controller and submit the same settings as before. This operation will =
connect the JOC Cockpit to the Controller. Registration of existing Agents =
is automatically repeated. Then redeploy any scheduling objects to the Cont=
roller from the JOC Cockpit Configuration view.
- Implication: This operation does not recover information about p=
ast job executions which have not yet been added to the JOC Cockpit history=
.
Damage to Controller Journal
There is no difference between in troubleshooting damage to a Controller=
Journal the loss of a Controller journal as described in the previous sect=
ion, except for the fact that users should remove the journal files from th=
e JS7_CONTROLLER_DATA/state
directory before starting the Cont=
roller instance.
------=_Part_12462_1136478578.1711693257537--