After startup of Systemwalker Operation Manager server has completed, any of Systemwalker Operation Manager functions can be used from a Systemwalker Operation Manager client. Start up the Systemwalker Operation Manager client in the following procedure.
Procedure
Displaying the Systemwalker Operation Manager [Login] window
Select Start/App >> Systemwalker Operation Manager >> Systemwalker Operation Manager.
Figure 1.1 Systemwalker Operation Manager [Login] window
Connecting to the Systemwalker Operation Manager servers.
Specify the destination host name, user ID and password on the Systemwalker Operation Manager [Login] window and click the Login button.
When the Systemwalker Operation Manager window appears, the startup of Systemwalker Operation Manager client has completed.
Note
If the Extended User Management function is being used, specify an Operation Manager user. If the Systemwalker authentication repository is being used, specify a Systemwalker user ID or a system administrator (a built-in Administrator account for the Windows version or a superuser for the UNIX version).
Figure 1.2 Systemwalker Operation Manager window
Note
Note the following when connecting to a Systemwalker Operation Manager server.
Number of clients to be connected:
You can simultaneously connect up to 62 (Note) Systemwalker Operation Manager clients per Systemwalker Operation Manager server. The maximum number of connected clients can be restricted in the Use function 2 sheet of the Define Jobscheduler Startup Parameters window. The limited clients include servers which are targeted for monitoring by the multi-server monitoring client and Jobscheduler info print clients.
Note) The maximum number varies depending on the OS.
Failure during connection to a Systemwalker Operation Manager server:
Connection to a Systemwalker Operation Manager server will end in failure in the following cases.
When the host name that has been specified does not exist
Specify the correct host name on which the Systemwalker Operation Manager server has been installed.
When the specified host name cannot be correctly interpreted (i.e., when it cannot be converted to an IP address)
Check the environments to resolve name. Or, directly specify the IP address.
When the user ID that has been specified does not exist
Specify a user ID that can log in to the connection destination host.
The user ID is more than 20 bytes
Enter a correct user ID.
When the password is incorrect
Specify the correct password.
When the Systemwalker Operation Manager infrastructure services are not operating on any destination host
In the Windows system, start up the Systemwalker Operation Manager infrastructure service (Systemwalker MpJmSrv) from the Windows' Services dialog box.
In the UNIX system, start up the Systemwalker Operation Manager infrastructure daemon (mpjmsrv).
When the user that has been specified does not have the rights for local logon [Windows version]
Set Log on Locally for user rights from the Windows' Local Security Policy window.
When no user ID or password is specified [UNIX]
A user ID and password cannot be omitted if the connection destination host is running on UNIX. Specify the user ID and password.
Understanding default settings for the Systemwalker Operation Manager [Login] window [Windows version]:
A host name, user ID or password can be omitted in the Systemwalker Operation Manager [Login] window. When omitted, the following values will be used:
When host names are omitted:
The host name that is logged on
When user IDs and passwords are omitted:
The user ID and password of the logged on user
User ID search sequence [Windows]
User IDs that have been specified are searched in the following sequence:
Local computers
Domain
Domains in trust relationships
