...
| Excerpt |
|---|
The JOC Cockpit allows service providers to configure both shared and dedicated services over any number of JobScheduler Masters. |
...
The use of individual JobScheduler Masters for individual clients also allows authorization - the allocation of permissions determining what a user is allowed to do - to be granted according to duties or roles. This approach may be contrasted with other systems that allocate permissions according to resources such as files or folders. See the JOC Cockpit - Authentication and Authorization article for more information.
JobScheduler makes use of two logically separate database instances:
- JobScheduler Database
- Reporting Database
All JobScheduler Master instances that should be managed with the same JOC Cockpit instance have to use the same Reporting Database. However, the Master instances can use the same or different JobScheduler Databases.
For more information see
...
The database configuration information for each JobScheduler Master is stored in a hibernate XML configuration file. By default this file is named hibernate.cfg.xml and is to be found in the $SCHEDULER_DATA/config/ directory of each JobScheduler Master.
The configuration information that the JOC Cockpit uses to access the JobScheduler Master databases is stored in one or more hibernate XML configuration files. The default locations for these files are:
/home/[JOCC user]/sos-berlin.com/joc/resources/jocon Linux systems andC:\ProgramData\sos-berlin.com\joc\resources\jocon Windows.
...