This section outlines the operating environment definition of Systemwalker Operation Manager.
System Definitions
Definitions about the system required to start using Systemwalker Operation Manager-
Defining hosts in the "hosts" file
Hosts should be defined in the "hosts" file when the Systemwalker Operation Manager client is used, when the Systemwalker Operation Manager Web Console is used, when network jobs are operated between servers and when the Systemwalker Operation Manager server is used in an IPv4/IPv6 dual stack environment.
Changing Port Numbers
The port numbers will need to be changed if they are being used by another product.
Tuning system parameters [UNIX]
For the UNIX version, the system parameters need to be tuned in order to ensure that Systemwalker Operation Manager runs stably.
Security Definitions
These definitions are required to operate Systemwalker Operation Manager securely. The definition items are as follows:
Extended User Management function [UNIX]
Systemwalker authentication repository
Access control
Restricting execution users
Audit log output
Common definitions for all Systemwalker products
These definitions are common to all Systemwalker products.
Definition for using a Systemwalker authentication repository
This definition is required to use a Systemwalker authentication repository.
Definition for using Systemwalker single sign-on
This definition is required to use Systemwalker single sign-on.
Common Systemwalker Operation Manager Definitions
Before defining environments specific to the Systemwalker Operation Manager functions, you need to define the environments that are common to the Systemwalker Operation Manager functions. The following items are defined:
Monitored Hosts in Systemwalker Operation Manager
Users
Users (When using Extended User Management function) [UNIX]
Users (When using a Systemwalker authentication repository)
User restrictions
Audit Log Output
Encrypted communications (HTTPS communications) for the Web Console
This is required if using the Web Console.
Definition of Multi-Subsystem Operations
Systemwalker Operation Manager Enterprise Edition supports a single server to operate multi-subsystems (Jobscheduler functions and Job Execution Control functions). This definition is required if you operate multi-subsystems. The following lists the required definition items.
Creating a subsystem environment
Assigning subsystem port numbers
You can also define the multi-subsystem operating environment after you have completed the operating environment setup explained in this chapter.
Definition of Power Control
In order to enable the power to the server to be turned on in response to a user logging in to a client, register the command for the power control function as a startup program on the client.
Definition of Jobscheduler
You need to define the following environments for the Jobscheduler.
Defining Startup Parameters
Defining a Message Table [Windows]
Defining a Monitoring Permitted Host
Definition of Job Execution Control
You need to define the following environments for the Job Execution Control functions.
Defining the System Operating Information
Defining a Trust Host
Defining the Job Owner Information [Windows]
Defining the user control list for job execution [UNIX]
Definition of Event Monitoring [Windows]
You need to define the following environments for Event Monitoring.
Defining the Event Monitoring environments (monitored log files)
Defining the action execution environments (mail, Short Mail, and COM port)
Definition of Task Link
You need to define the following operating environments for Task Link.
Defining a Password Management Book
Definition for Task Link with Clients
Defining the Host Information
Definitions when linking with Systemwalker Centric Manager
When monitoring the Jobscheduler by using Systemwalker Centric Manager's system monitoring functions, you must install Systemwalker Operation Manager's client functions in Systemwalker Centric Manager. Then, you must define the event logs to be output by the Jobscheduler in Systemwalker Centric Manager.
Definitions when linking with ServerView Operations Manager to perform Single Sign-On
In order to link with ServerView Operations Manager to perform Single Sign-On, first build a Single Sign-On environment in ServerView Resource Orchestrator and then configure the settings in Systemwalker Operation Manager.
Definitions when constructing the existing environment on another server
After extracting the environment definition data and registration information from the currently operating server, you need to distribute them to another server.
Definition for maintenance
For maintenance of Systemwalker Operation Manager, you must complete the followings.
Defining the Process Monitoring function
Controlling the generation of maintenance information
