System Requirements
|
System Requirements |
|
|
Supported Operating Systems Tivoli Workload Scheduler KM for PATROL can be run on the following operating systems:
TWS KM may run on other variants of Unix, on which Tivoli Workload Scheduler runs, but has not been tested. On Windows platforms the Tivoli Workload Scheduler installation is identified by checking the Windows registry. Depending on the version of Tivoli Workload Scheduler, the registry entries can be found under one of the following registry paths: “HKEY_LOCAL_MACHINE\SOFTWARE\Unison Software, Inc.\Unison Maestro\” “HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Tivoli Workload Scheduler” “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\Tivoli Workload Scheduler”. Therefore the PATROL Agent user should have read access to the registry path.
Supported Versions Tivoli Workload Scheduler KM for PATROL supports the following versions for PATROL and Tivoli Workload Scheduler:
Security Requirements Tivoli Workload Scheduler KM for PATROL does not require any specific security rights. The only base requirement is that the PATROL account should be able to run the conman and cpuinfo (UNIX only) commands to be able to view CPU, Schedule, Job, Prompt and TWS application status details. If for some reason the Security file in TWS has been configured to restrict access, then the PATROL account may need to be added to the file, to have display access to most components. Specific menus do require the operators to enter the login and password of a valid user to perform TWS Operations. Disk and Memory Usage When monitoring a standard installation of TWS using TWS KM, the PATROL Agent will consume approximately 800KB of additional system memory. A Tivoli Workload Scheduler for PATROL master machine configured with additional CPU’s, or with filters for prompts, schedules, or jobs that create more instances, this will consume additional memory resources as per other KMs used by the PATROL Agent. When monitoring a standard installation of TWS using TWS KM, the PATROL Agent will generate approximately 200K of history data per day. An installation configured with additional CPU’s or modified filter rules will generate more history data as per other KMs used by the PATROL Agent.
|
