Date: Thu, 28 Mar 2024 19:42:18 +0000 (UTC) Message-ID: <1182435456.11877.1711654938442@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11876_267559716.1711654938441" ------=_Part_11876_267559716.1711654938441 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The JOC Cockpit allows to configure both shared and dedicated services o= ver any number of JobScheduler Masters.The JobScheduler Masters can th= en be operated, managed and monitored from a single user interface with per= missions and roles assigned for each Master.
The JOC Cockpit can also be configured to work with JobScheduler Masters= that use different databases and database management systems.
The JOC Cockpit's multi-client capability is a direct feature of the Job= Scheduler Architecture and allows operation for multiple clients - i.e. sch= eduling customers - to be separated through the use of separate JobSchedule= r Masters for individual clients. See the JOC Cockpit - Architecture article for more backgrou= nd information.
This clear separation of resources brings a number of advantages for bot= h service providers and users:
The use of individual JobScheduler Masters for individual clients also a= llows authorization - the allocation of permissions determining what a user= is allowed to do - to be granted according to duties or roles. This approa= ch may be contrasted with other systems that allocate permissions according= to resources such as files or folders. See the JOC Cockpit - Authentication a= nd Authorization article for more information.
JobScheduler makes use of two logically separate database instances:
All JobScheduler Master instances that should be managed with the same J= OC Cockpit instance have to use the same Reporting Database. Howev= er, the Master instances can use the same or different JobScheduler Dat= abases.
This section describes how to configure the JOC Cockpit to operate with = different JobScheduler Masters that are using different databases. Note tha= t this is only possible when these JobSchedulers are configured to use diff= erent JobScheduler and Reporting databases.
The database configuration information for each JobScheduler Master is s=
tored in a hibernate XML configuration file. By default this file is named =
hibernate.cfg.xml
and is to be found in the $SCHEDU=
LER_DATA/config/
directory of each JobScheduler Master.
The configuration information that the JOC Cockpit uses to access the Jo= bScheduler Master databases is stored in one or more hibernate XML configur= ation files. The default locations for these files are:
/home/[JOCC user]/sos-berlin.com/joc/resources/joc
on L=
inux systems and
C:\ProgramData\sos-berlin.com\joc\resources\joc
on Windows=
.When the JOC Cockpit is used with one or more JobScheduler Masters that =
are using a common database then the hibernate information file is named Hibernate configuration files for databases used by specific JobSchedule=
r Masters can be configured where each file is named according to the forma=
t: where These files can be stored in the same folder as the These files have to be listed in the with each list entry following the pattern: where If the hibernate database configuration files are not stored in the same=
folder as the where joc.properties
file that by default is stored in=
the same folder as the jobscheduler.hibernate.cfg.xml
file.=
p>
<jobschedulerID>.hibernate.cfg.xml
<jobschedulerID>
is the ID of the relevant=
JobScheduler Master.joc.=
properties
file or in another folder.joc.properties
file in=
the section:
hibernate_configuration_file_
<jobschedulerID>
=
=3D
.hibernate.cfg.xml<jobschedulerID>
<jobschedulerID>
is the ID of the relevant=
JobScheduler Master.joc.properties
file, the files are to be listed=
as follows:
hibernate_configuration_file_
<jobschedulerID>
=
=3D <path>
.hibernate.=
cfg.xml<jobschedulerID>
<path>
is either relative to the For more=
information see