3.1 Hardware Resources

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 and client have been installed is referred to as the "system drive," and the disk where Systemwalker Operation Manager has been installed (Note) is referred to as the "installation directory."

Note): Systemwalker Operation Manager installation directory ( Default : C:\Systemwalker)

[Windows]

Additional functions	Areas used	Server	Client
No additional functions selected (default installation)	System drive	380 MB or more	400 MB or more
	Installation directory	1080 MB or more	120 MB or more
	Total	1460 MB or more	520 MB or more
All additional functions selected	System drive	380 MB or more	400 MB or more
	Installation directory	1100 MB or more	120 MB or more
	Total	1490 MB or more	520 MB or more

[Solaris]

Additional functions	Areas used	Server	Client
All additional functions selected	/(root) (Note)	1 MB or more	---
	/opt	1100 MB or more	---
	/etc	25 MB or more	---
	/var	150 MB or more	---
	System drive	---	400 MB or more
	Installation directory	---	120 MB or more
	Total	1276 MB or more	520 MB or more

Note): If there is not /opt or /etc or /var directory, it takes each capacity additionally in /(root) directory.

[Linux ]

Additional functions	Areas used	Server	Client
All additional functions selected	/opt	1300 MB or more	---
	/etc	30 MB or more	---
	/var	180 MB or more	---
	System drive	---	400 MB or more
	Installation directory	---	120 MB or more
	Total	1510 MB or more	520 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]

Server	Client
450 MB or more	60 MB or more

[Solaris]

Server	Client
720 MB or more	60 MB or more

[Linux]

Server	Client
600 MB or more	60 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

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

Note): Operation log files for calendar and power control

Files required for operations	Required disk space (bytes)
Information file	2 KB

Note): The service startup function cannot be used with UNIX systems.

Files required for operations	Required disk space (bytes)
Basic capacity	13 MB
Schedule information file	(512 x <number of projects>) x 2 + (10000 x <total number of job nets> + 2200 x <total number of jobs>) x 2 (Note 1)
Log file (Note 2)	<value set in Jobscheduler startup parameter (1 to 99 MB)> x 3
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

Note 1): 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

Note 2): Log files for job net execution histories

Remarks 1:

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

Remarks 2:: 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.

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>) q: Number of queues n: Maximum number of jobs that can exist concurrently in the system (the total number of jobs that are "waiting", "on hold", "active", and "output on hold") j: Size of job file o: Size of standard output file e: Size of standard error output file
Trace file [Windows version] (Note)	500 KB x 202
Trace file [UNIX version] (Note)	5 MB x 2 x 12

Note): The trace file is used for cyclic control of trace information within the calculated disk capacity.

Remarks:

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

Files required for operations	Required disk space (bytes)
Definition file	<number of event lines defined> x 2 KB (Note)

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.

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>

Remarks:

Each file is stored in the following location.

[Windows version] Installation directory

[UNIX version] /opt

Files required for operations	Required disk space (bytes)
Trace file [Windows version]	Server: 190.0 MB or more (Up to 380.0 MB) Client: 1.0 MB or more (Up to 2.0 MB)
Trace file [UNIX version]	Server: 5.0 MB or more (Up to 10.0 MB)

Remarks:

Each file is stored in the following location.

[Windows version] System drive

[UNIX version] /var

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)>

Note 1): This is the total number of login operations, definition change operations and job/queue operations per day. This includes operations resulting from commands, APIs, or Web API 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.)

Note 2): 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.)

Note 3): 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.

Management server

Files required for operations	Required disk space (bytes)
Basic capacity	(10000 x <number of distribution job nets> + 2200 x <number of jobs>) x 2 (Note 4)
Master schedule management status file (Note 1)	(100 + <number of schedule servers> x 200) x <number of schedule records (Note 5)> + 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) + (115 x <number of job nets not applied that day>)
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> + 2200 x <number of jobs>) x 2 (Note 4)
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) + (115 x <number of job nets unapplied to the subject day>)
Trace file (Note 3)	(30 MB x <number of subsystems>) + 30 MB

Remarks:: 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.

Note 1): 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.

Note 2): 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.

Note 3): The trace file is used to cyclically control trace information within the determined disk capacity.

Note 4): 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

Note 5): 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.

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	Software	Installation location and Software
Windows	APC (Fujitsu OEM)	PowerChute(R) Business Edition Version 10.0	Installation location: Server UPSSLEEP.EXE(Note) (attach to PowerChute(R) Business Edition)

Remark:: Clients do not need to be set up if power control is only performed according to schedules for each server.

Note)

Set up the path to the directory where UPSSLEEP.EXE is installed in the PATH system environment variable.

If you use "PowerChute(R) Business Edition Version 10.0", execute jmsetauthinfo command and register authentication information of PowerChute(R).

This authentication information is used when accessing PowerChute(R). For more information of jmsetauthinfo command, refer to the "Systemwalker Operation Manager Reference Guide".

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)

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.