Table of Contents
Advertisement
This value is similar to
and limits the number of jobs sitting in a queue waiting to be started. Therefore, the maximum
jobs that can be present on an Orchestrate Server is
New jobs are not be accepted by the server if, when added, they would exceed this total.
job.finishing.timeout: Set a (global default) limit on the timeout for job completion.
This value represents the number of seconds that the Orchestrate Server allows a job to execute
it's
job_cancelled_event()
from potentially hanging during cancellation.
5.1.2 The Orchestrate Server Authentication Tab
The Authentication tab opens a page with several collapsible sections where you can configure
various methods for authenticating both users and resources to the PlateSpin Orchestrate Server.
"Resources" on page 65
"Users" on page 65
Resources
The resources in a PlateSpin Orchestrate grid are actually PlateSpin Orchestrate Agents that
authenticate or "register" with the PlateSpin Orchestrate Server.
Auto Register Agents: Select this check box if you want the PlateSpin Orchestrate Server to
automatically register agents when they first connect to the Orchestrate Server.
Users
Only authenticated users can log into the PlateSpin Orchestrate Server. As an administrator, you can
configure this authentication to use an internal user database or to externally authenticate users
through an LDAP server.
Auto Register Users
Select this check box if you want the PlateSpin Orchestrate Server to automatically register users
when they first connect to the Orchestrate Server.
Enable LDAP
Select this check box if you want the Orchestrate Server to authenticate users externally using an
LDAP server. Additional LDAP-related configuration fields are displayed when you select check
box.
Administrators
The Administrators list specifies the group names whose membership includes PlateSpin
Orchestrate administrators as returned by the specified authentication provider. You can add groups
to this list by clicking the
be added, removed, and reordered. A group must be in the format
<provider>:<group|groupnocase>:<groupname>
"LDAP". For example, adding
(see above) but it is used in the
max.active.jobs
(if defined) before forcibly aborting the job. This prevents jobs
button to open an array editor dialog box, which allows groups to
LDAP:groupnocase:XyZ
+
max.active.jobs
max.queued.jobs
, where the
<provider>
allows users reported by the LDAP server
constraint
accept
.
is either "ZOS" or
The Explorer Tree
65
Advertisement
Table of Contents
