Page History

...

JS7 and JS1 both require similar Reporting Databasesa Reporting Database for similar purposes. However, this is not the same database: initial installation of JS7 has to start from a new database or schema, see JS7 - Database.
- Users who want to access the job history and logs of JS1 are recommended to continue use of JS1 JOC Cockpit and its database with the JS1 Master being deactivated.
The JS7 - Database stores inventory information and deployment information for job-information about inventory, deployment and execution history of jobs, workflows and related configuration. This
- Inventory and deployment: The database is not required at run-time but at design-time and at deploy-time only.
Therefore
- In this respect high availability requirements for
this
- the database
are
- can be considered to be more relaxed
by a number of users
- .
- Execution history: If the database is not available then the execution history and logs cannot be made available in near-real time with JOC Cockpit. This does not affect execution of jobs and workflows. The execution history is not lost but will be streamed from the Controller to JOC Cockpit at a later point in time when the database becomes available.
- API Service: The database is required for use of the JS7 - REST Web Service API. Users who run jobs with access to the API might prefer to use a highly available database.

Controller / Agent

...