13.1 List of case studies
The following table lists the scenarios and challenges assumed in the case studies.
No |
Case study |
Reference |
---|---|---|
1 |
Acquiring information about job execution activity by specific users. |
|
2 |
Preventing execution of jobs that are invalid due to an incorrectly specified execution agent or other reason. |
|
3 |
Saving the results of a daily job to a different file each day. |
|
4 |
Reinstating a temporary schedule change that was cleared by a release registration. |
|
5 |
Using an alias for the execution host name of an event job in a manager/agent configuration. |
|
6 |
Limiting JP1/AJS3 - Manager resources to those used for job operation |
|
7 |
Isolating the business operations of each scheduler service on a single manager host. |
|
8 |
Editing units defined by JP1/AJS3 - View and comparing definitions before and after editing |
|
9 |
Executing jobs in an auto-scaling cloud environment |
|
10 |
Executing a single job on multiple agent hosts |
|
11 |
Restricting operations that can be performed from the Web GUI (Job Portal) or user applications |
|
12 |
Graphically viewing the JP1/AJS3 operating status |
|
13 |
Checking the JP1/AJS3 operational status by using the Web GUI |
- Organization of this section
-
-
13.1.1 Acquiring information about job execution activity by specific users
-
13.1.3 Saving the results of a daily job to a different file each day
-
13.1.4 Reinstating a temporary schedule change that was cleared by a release registration
-
13.1.5 Using an alias for the execution host name of an event job in a manager/agent configuration
-
13.1.6 Limiting JP1/AJS3 - Manager resources to those used for job operation
-
13.1.7 Isolating the business operations of each scheduler service on a single manager host
-
13.1.8 Editing units defined by JP1/AJS3 - View and comparing definitions before and after editing
-
13.1.13 Checking the JP1/AJS3 operational status by using the Web GUI
-