This section explains the hardware resources required to install and operate Systemwalker Operation Manager.
Hardware resources required for installing Systemwalker Operation Manager
This section explains the hardware resources required for installing Systemwalker Operation Manager.
Disk capacity
The disk capacity required for installing Systemwalker Operation Manager is shown in the tables below.
The disk where the Windows system has been installed is referred to as the "system directory," and the disk where Systemwalker Operation Manager has been installed is referred to as the "installation directory."
[Windows x86]
Additional functions | Areas used | Server | Client |
---|---|---|---|
No additional functions selected (default installation) | System directory | 30 MB or more | 15 MB or more |
Installation directory | 660 MB or more | 395 MB or more | |
Total | 690 MB or more | 410 MB or more | |
All additional functions selected | System directory | 30 MB or more | 15 MB or more |
Installation directory | 680 MB or more | 400 MB or more | |
Total | 710 MB or more | 415 MB or more |
[Windows x64]
Additional functions | Areas used | Server | Client |
---|---|---|---|
No additional functions selected (default installation) | System directory | 45 MB or more | 35 MB or more |
Installation directory | 700 MB or more | 375 MB or more | |
Total | 745 MB or more | 410 MB or more | |
All additional functions selected | System directory | 45 MB or more | 35 MB or more |
Installation directory | 720 MB or more | 380 MB or more | |
Total | 765 MB or more | 415 MB or more |
[Solaris 32bit version]
Additional functions | Areas used | Server | Client |
---|---|---|---|
All additional functions selected | /(root) (Note) | 1 MB or more | --- |
/opt | 480 MB or more | --- | |
/etc | 25 MB or more | --- | |
/var | 150 MB or more | --- | |
System directory | --- | 35 MB or more | |
Installation directory | --- | 380 MB or more | |
Total | 656 MB or more | 415 MB or more |
If there is not /opt or /etc or /var directory, it takes each capacity additionally in /(root) directory.
[Solaris 64bit version]
Additional functions | Areas used | Server | Client |
---|---|---|---|
All additional functions selected | /(root) (Note) | 1 MB or more | --- |
/opt | 480 MB or more | --- | |
/etc | 25 MB or more | --- | |
/var | 150 MB or more | --- | |
System directory | --- | 35 MB or more | |
Installation directory | --- | 380 MB or more | |
Total | 656 MB or more | 415 MB or more |
If there is not /opt or /etc or /var directory, it takes each capacity additionally in /(root) directory.
[Linux x86]
Additional functions | Areas used | Server | Client |
---|---|---|---|
All additional functions selected | /opt | 580 MB or more | --- |
/etc | 30 MB or more | --- | |
/var | 110 MB or more | --- | |
System directory | --- | 35 MB or more | |
Installation directory | --- | 380 MB or more | |
Total | 720 MB or more | 415 MB or more |
[Linux x64]
Additional functions | Areas used | Server | Client |
---|---|---|---|
All additional functions selected | /opt | 580 MB or more | --- |
/etc | 30 MB or more | --- | |
/var | 180 MB or more | --- | |
System directory | --- | 35 MB or more | |
Installation directory | --- | 380 MB or more | |
Total | 790 MB or more | 415 MB or more |
Hardware resources required for operating Systemwalker Operation Manager
In addition to the hardware resources required for installing Systemwalker Operation Manager, it is also necessary to estimate the following memory and disk requirements for operating Systemwalker Operation Manager.
Memory requirements
Disk space requirements for different operation configurations
Memory requirements
The following table lists the amount of memory that is required to run Systemwalker Operation Manager.
[Windows x86]
Server | Client |
---|---|
320 MB or more | 60 MB or more |
[Windows x64]
Server | Client |
---|---|
420 MB or more | 60 MB or more |
[Solaris 32bit version]
Server | Client |
---|---|
400 MB or more | 60 MB or more |
[Solaris 64bit version]
Server | Client |
---|---|
480 MB or more | 60 MB or more |
[Linux x86]
Server | Client |
---|---|
230 MB or more | 60 MB or more |
[Linux x64]
Server | Client |
---|---|
390 MB or more | 60 MB or more |
[HP-UX]
Server | Client |
---|---|
90 MB or more | 50 MB or more |
[AIX version]
Server | Client |
---|---|
20 MB or more | 50 MB or more |
Disk space requirements for different operation configurations
The disk space shown below is required to operate Systemwalker Operation Manager, depending on the scale of operation. Estimate the disk space required and allocate more than enough space when installing Systemwalker Operation Manager, by referring to the tables below.
Note that Systemwalker Operation Manager files are stored in the following location. (With the exception of the files for the Jobscheduler, Job Execution Control, Task Link and Systemwalker trace information)
[Windows version] Installation directory
[UNIX Version] /var
<Calendar>
Files required for operations | Required disk space (bytes) |
---|---|
Calendar file | <number of calendars> x 14 KB + 94 KB |
Power control file | 5 KB |
Log file (Note) | 6 MB |
Operation log files for calendar and power control
<Starting services and applications>
Files required for operations | Required disk space (bytes) |
---|---|
Information file | 2 KB |
The service startup function cannot be used with UNIX systems.
<Jobscheduler>
Files required for operations | Required disk space (bytes) |
---|---|
Basic capacity | 13 MB |
Schedule information file | (512 x <number of projects>) x 2 + |
Log file (Note 2) | <value set in Jobscheduler startup parameter |
Job net history file | 10000 x <number of job nets> x <1 to 24 generations> |
Standard output and error output files for each job | Total space required for all registered jobs that send output to the standard output and the error output |
Message event history file | 99 MB x 3 |
To operate groups, add the following value to the value shown in the table above:
(1000 x <total number of groups> + 27400 x <total number of job nets belonging to groups>) x 2
Log files for job net execution histories
If job nets are nested, child job nets are registered as jobs in their parent job nets. This means that jobs need to be counted, as well as job nets.
Each file is stored in the following location.
[Windows version] Installation directory
[Solaris version/Linux version] /var
[HP-UX version/AIX version] /opt
Both jobs and job nets need to be counted because linked job nets are registered as jobs in parent job nets. If the referenced master linked job net is also nested, then the linked job net will also be nested and all job nets and jobs registered under the nested linked job net will need to be counted.
<Job Execution Control>
Files required for operations | Required disk space (bytes) |
---|---|
Basic capacity [Windows version] | 14 MB |
Basic capacity [UNIX version] | 15 MB |
Spool | 256 bytes x <q> + <n> x (4 KB + <j> + <o> + <e>) |
Trace file | 500 KB x 202 |
Trace file | 5 MB x 2 x 12 |
The trace file is used for cyclic control of trace information within the calculated disk capacity.
To collect log files and operation record files, there needs to be enough space to store them.
For information on how to make these estimates, refer to the Systemwalker Operation Manager Installation Guide.
Each file is stored in the following location.
[Windows version] Installation directory
[Solaris version/Linux version] /var
[HP-UX version/AIX version] /opt
<Event Monitoring [Windows version]>
Files required for operations | Required disk space (bytes) |
---|---|
Definition file | <number of event lines defined> x 2 KB (Note) |
If complex definitions and long parameters are specified, the required capacity may exceed this limit.
In this case, double the estimate for the space required.
<Task Link>
Files required for operations | Required disk space (bytes) |
---|---|
Trace file [Windows version] | 6.2 MB |
Host information definition file | 350 x <number of registration hosts> |
Password management file | 200 x <number of registration users> |
Each file is stored in the following location.
[Windows version] Installation directory
[UNIX version] /opt
<Systemwalker trace information>
Files required for operations | Required disk space (bytes) |
---|---|
Trace file | Server: 190.0 MB or more (Up to 380.0 MB) |
Trace file [UNIX version] | Server: 5.0 MB or more (Up to 10.0 MB) |
Each file is stored in the following location.
[Windows version] System drive
[UNIX version] /var
<Audit log output>
Files required for the operations | Required disk space (bytes) |
---|---|
Audit log files | <number of operations per day (Note 1)> x <average output size per record (Note 2)> x <number of storage days (Note 3)> |
This is the total number of login operations, definition change operations and job/queue operations per day. This includes operations resulting from commands or APIs, as well as operations performed from clients. A large number of operations will be performed on maintenance days and at initial installation time, so use the highest likely value for the estimate. (Assume around 1,000 operations per day, depending on the system being installed.)
This is the average length of one line of messages output to audit logs. (This value depends on the user names and host names that are being used, but assume around 500 bytes.)
This is the number of days that audit logs will be held. The default value is 31 days. Because audit log files are stored for only the specified number of days, it is recommended that audit log files be backed up periodically if necessary. Refer to the Systemwalker Operation Manager Reference Guide for more information about the mpsetlogsend_omgr command.
<Master Schedule Management>
Management server
Files required for operations | Required disk space (bytes) |
---|---|
Basic capacity | (10000 x <number of distribution job nets> |
Master schedule management status file (Note 1) | (100 + <number of schedule servers> x 200) x <number of schedule records (Note 5)> |
Carried over control information file (Note 2) | (420 x <number of carried over job nets> x 2) |
Trace file (Note 3) | (30 MB x <number of subsystems>) + 30 MB |
Schedule server [UNIX version]
Files required for operations | Required disk space (bytes) |
---|---|
Basic capacity | (10000 x <number of distribution job nets> |
Master schedule management status file (Note 1) | 40 x <number of schedule records (Note 5)> |
Carried over control information file (Note 2) | (420 x <number of carried over job nets> x 2) |
Trace file (Note 3) | (30 MB x <number of subsystems>) + 30 MB |
When the management server and schedule server are run on the same machine, the required disk space will be the same as if only the management server was used.
The master schedule management status file is used to store the distribution status of the schedule information. The following files are master schedule management status files:
- "stemmanager.db" and "start_end.log" in the master schedule management database directory.
The carried over control information file stores the carried-over job net information and so on.
These files are as follows:
- "carry_st.lst", "carry.lst" and "process date(yyyymmdd).dat" files, located in the database directory for master schedule management.
The trace file is used to cyclically control trace information within the determined disk capacity.
The following value must be added for group operations:
(1000 x <total number of groups> + 27400 x <total number of job nets belonging to groups>) x 2
The number of schedule records is the number of days calculated with the following formula:
<number of days for schedule status management> + <number of days in future schedules>
where <number of days in future schedules> means "the number of days in advance that schedules are registered".
Hardware requirements for server power control
A power control device and supporting software are required in order to control the power to servers. This function is only available when the operating system is Windows x86.
The power control device and software are not required for operations that only involve shutting down and rebooting.
Note
For Solaris servers, power control is not available for a Non-global Zone. If Systemwalker Operation Manager is installed on a Global Zone, power control is available for the Global Zone.
The power control function is not supported if multiple operating systems are running with a VM function or on a blade server.
Hardware and software requirements for server power control
Server OS | Provider | Power control device/UPS | Software |
---|---|---|---|
Windows x86 | APC | SmartUPS, and one of the following network adapters for SmartUPS | PowerChute(R) plus V5.2 (Note) |
Web/SNMP Management Card (AP9606) or Network Management Card EX (AP9617) is required to start the server from the client, or to use the Batch Power Control function. The PowerChute(R) Plus V5.2 software can be integrated at this time, however the PowerChute(R) Business Edition cannot be used.
If the server is not started by a client, the Web/SNMP Management Card (AP9606) and the Network Management Card EX (AP9617) are not required.
The software to be installed may vary depending on the software used and the client/server type, as shown in the following table.
Software used | Server/client type | Software to be installed |
---|---|---|
PowerChute(R) plus V5.2 | Server | UPSSLEEP.EXE (Note) |
PowerChute(R) Business Edition Version 9.0.1 | Server | UPSSLEEP.EXE (Note) |
Clients do not need to be set up if power control is only performed according to schedules for each server.
Set up the path to the directory where UPSSLEEP.EXE is installed in the PATH system environment variable.
Some of the functions of the power control software for "Systemwalker Enabled" authorized products may not be available depending on the software. Also, some functions may need special care when used. For more information, refer to the Systemwalker website and the manuals for the software.
Hardware requirements for Event Monitoring [Windows version]
The following hardware is required in order to send short mail notifications:
An NTT DoCoMo mobile phone
A phone that supports Short Mail is required. Refer to the NTT DoCoMo home page for information about Short Mail-compatible phones.
The following hardware device is required for voice notification.
WAVE audio card (Note)
It may not be possible to install an audio card on some models.
Hardware required for Task Link
The following hardware devices are required to use various Task Link functions.
Client power-on
A device that supports Wakeup on LAN
A LAN card that supports Wakeup on LAN
Turning the power on via Wakeup on LAN must be enabled at the BIOS level.
Client power-off
A device that supports either APM (Advanced Power Management) or ACPI (Advanced Configuration & Power Interface)
Turning the power off from Windows must be enabled.