Introduction
The JOC cockpit allows service providers to configure both shared and dedicated services over any number of JobScheduler Masters.The JobScheduler Masters can then be operated, managed and monitored from a single interface and permissions and roles assigned for each Master.
Architecture-Based Multi-Client Capability
The JOC Cockpit's multi-client capability is a direct feature of the JobScheduler Architecture and allows operation for multiple clients - i.e. scheduling customers - to be separated through the use of separate JobScheduler Masters for individual clients. See the JOC Cockpit - Architecture article for more background information.
This clear separation of resources brings a number of advantages for both service providers and users:
- Increased processing requirements of one user will not affect the processing capacity available for another, meaning that service requirements can be clearly stated and met.
- Maintenance windows, can be implemented individually according to customer requirements.
- Software updates can be implemented independently according to client wishes.
The use of individual JobScheduler Masters for individual clients also allows authorization - the allocation of user rights and 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 rights and permissions according to resources such as files or folders.
The use of role-based rights and permissions brings a number of significant advantages:
- It simplifies their administration in complex environments. Whilst the administration of the permissions of several hundred folders in a multi-client system is manageable, the administration of several thousand requires brings an extremely high administrative requirement and error susceptibility.
- Role-based rights and permissions allow the rights and permissions for individual clients to be managed separately.
- The clear separation of rights and permissions also simplifies meeting compliance requirements.
For more information see