Page History
...
- Configuration Data
- This includes installation options and configuration items that are updated after installation, for example certificates and settings for HTTPS connections.
- Log Data
- Log files are created and updated continuously and are mainly used for problem analysis. As past log files are not used at run-time many users consider them not be an immediate target of backups.
- Inventory Data
- JS7 - Inventory of workflows, jobs and related objects managed with JOC Cockpit.
- Transaction Data
- JOC Cockpit
- JS7 - History of past order and task executions, of deployments and order submissions.
- JS7 - Daily Plan for future order starts.
- Controller and Agent
- JS7 - Order State Transitions that are persisted to allow restart capabilities.
- JOC Cockpit
- Log Data
- Log files are created and updated continuously and are mainly used for problem analysis. As past log files are not used at run-time many users consider them not be an immediate target of backups.
JOC Cockpit
Configuration Data
...
Configuration data are created during installation and optionally are modified by users later on. This suggests that backups of configuration data are required only in case of changes by users.
Log Data
JOC Cockpit log files are stored in the JETTY_BASE/logs directory.
Except for problem analysis log files are not too relevant, However, compliance reasons could suggest to backup log files.
...
Inventory Data, Transaction Data
All objects managed with JOC Cockpit are stored in the JS7 - Database.
...
- The database backup tool is required to create consistent backups, for example in case of concurrent transactions if new items are added to the JS7 History while a backup is performed.
- The database backup tool should not interfere with JS7 database transactions and should not affect JS7 operations.
- If no decent backup tool is in place then users can shutdown JOC Cockpit to take a backup by exporting the JS7 database.
Log Data
JOC Cockpit log files are stored in the JETTY_BASE/logs directory.
Except for problem analysis log files are not too relevant, However, compliance reasons could suggest to backup log files.
Controller
Configuration Data
...
Configuration data are created during installation and optionally are modified by users later on. This suggests that backups of configuration data are required only in case of changes by users.
Log Data
Log files of the Controller (not: of workflows or jobs) are available from the Controller's JS7_CONTROLLER_DATA/logs directory.
Except for problem analysis the log files are not too relevant, However, compliance reasons could suggest to backup log files.
Transaction Data
Transaction data of Controller instances are available from the Controller's JS7_CONTROLLER_DATA/state directory that holds a journal of JS7 - Deployment operations and JS7 - Order State Transitions. This applies to Standalone Controller instances and to Controller Cluster instances.
...
- The JS7 - Controller Cluster guarantees redundancy and consistency of transaction data that are synchronized between Active and Standby Controller instances on different machines.
- Should the Active Controller instance's journal be lost, for example due to disk failure, then the Standby Controller instance will pick up operation form a synchronized copy of the journal. If the failed Controller instance is started later on then it will be assigned the standby role and will synchronize its journal from the Active Controller Instance.
Log Data
Log files of the Controller (not: of workflows or jobs) are available from the Controller's JS7_CONTROLLER_DATA/logs directory.
Except for problem analysis the log files are not too relevant, However, compliance reasons could suggest to backup log files.
Agent
Configuration Data
The Agent's configuration data are available from files in the JS7_AGENT_DATA/config directory hierarchy, for example
...
Configuration data are created during installation and optionally are modified by users later on. This suggests that backups of configuration data are required only in case of changes by users.
Log Data
Log files of the Agent (not: of workflows or jobs) are available from the Agent's JS7_AGENT_DATA/logs directory.
Except for problem analysis the log files are not too relevant, However, compliance reasons could suggest to backup log files.
Transaction Data
Transaction data of Agents are available from the Agent's JS7_AGENT_DATA/state directory that holds a journal of JS7 - Deployment operations and JS7 - Order State Transitions.
...
- The JS7 - Agent Cluster guarantees redundancy and consistency of transaction data that are synchronized between Active and Standby Director Agent instances on different machines. Should the Active Director Agent's journal be lost, for example due to disk failure, then the Standby Director Agent will pick up operation form a synchronized copy of the journal. If the failed Director Agent instance is started later on then it will be assigned the standby role and will synchronize its journal from the Active Director Agent.
- Subagents do not make use of a journal as they are used for job execution only. Workflows and order state transitions are managed by the Director Agent only.
Log Data
Log files of the Agent (not: of workflows or jobs) are available from the Agent's JS7_AGENT_DATA/logs directory.
Except for problem analysis the log files are not too relevant, However, compliance reasons could suggest to backup log files.
Overview
Content Tools