...

Taking a backup includes to consistently store the following data in a JS7 environment:

• Configuration data such as Data
  • This includes installation options and configuration items that are updated after installation, for example certificates and settings for HTTPS connections.
• Logging Data
  • Log files are created and updated continuously. They are mainly used for problem analysis. 
• Inventory Data
  • JS7 - Inventory of workflows, jobs and related objects to manage dependencies.
• Transaction Data
  • JS7 - History of past order and task executions, of deployments and submissions.
  • JS7 - Daily Plan for future order
  executions
  • starts.

JOC Cockpit

Configuration Data

The following JOC Cockpit configuration data are stored to files in the JETTY_BASE/resources/joc directory, for example:

...

Except for problem analysis log files are not too relevant, However, compliance reasons might suggest to backup log files.

Inventory Data

...

and Transaction Data

All objects managed with JOC Cockpit are stored in the JS7 - Database.

This includes any data that can be are managed by the JOC Cockpit GUI such as Inventory, History, Daily Plan and Settings:

• Inventory Data
  • JS7 - Inventory of workflows, jobs and related objects to manage dependencies.
  • JS7 - Settings that determine the working of JOC Cockpit.
  • JS7 - Controllers and Agents that are managed by JOC Cockpit.
  • JS7 - Identity Services that are managed by JOC Cockpit.
  • JS7 - Profiles that hold user preferences.
• Transaction Data
  • JS7 - History of past order and task executions, of deployments and submissions.
  • JS7 - Daily Plan for future order starts.

Users should take backups of the JS7 database on a regular basis. 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.

Controller

Configuration Data

All The Controller's configuration data are available from files in the Controller's  JS7JS7_CONTROLLER_DATA/config directory, for example

...

• 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.

Agent

Configuration Data

All The Agent's configuration data are available from files in the Agent's  JS7JS7_AGENT_DATA/config directory, for example

...