Job Management Partner 1/Automatic Job Management System 3 Operator's Guide
This section describes the preparations that are necessary before using the system to perform the example operations.
- user1 is the JP1 user name for logging into JP1/AJS3 Console Manager at the Tokyo headquarters.
The JP1 user name user1 has been registered in host1, the authentication server host in the Tokyo headquarters.
- In each branch, the JP1 user name user1 can be used to access from JP1/AJS3 Console Manager.
To the hosts host2, host3, and host4 in the branches, the JP1 user name user1 has been mapped as an OS user.
- In each branch, a JP1 permission level allowed for JP1 user user1 has been set for all units located under jobnets Daily_Order_Processing, Weekly_Order_Processing, and Monthly_Order_Processing, to be monitored.
For applications to be monitored, a JP1 permission level called JP1_AJS_Operator has been set to JP1 user user1.
- In each branch, root jobnets Daily_Order_Processing, Weekly_Order_Processing, and Monthly_Order_Processing, each located under a job group called AJSROOT1, have been registered for execution.
For details on how to establish an environment which allows logging into JP1/AJS3 Console Manager at the Tokyo headquarters and how to establish an environment which allows to make access through JP1/AJS3 Console Manager from the monitored host, see 6.6 User management when monitoring work tasks centrally in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide. For details on how to set JP1 permission levels, see 6.4 Setting access permissions in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
Covered next is how to define applications executed in each branch as applications to be monitored into the host at the Tokyo headquarters.
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.