3.1.1 Flow of SSO installation and setup tasks

This subsection describes the flow of SSO installation and setup tasks.

Install SSO.

You can perform product installation steps 1 to 3 in any order.

In a distributed configuration, install NNMi and each SSO program on different hosts. Note that every SSO program must be set up.

For how to install SSO, see 3.2.1 Installing.
Install NNMi.

For how to install NNMi, see the Job Management Partner 1/Consolidated Manager 2/Network Node Manager i Installation Guide.
Install JP1/Base.

JP1/Base is required only when the user authentication function of JP1/Base is to be used. You can install JP1/Base at any point before step 6.

For details about how to install JP1/Base, see the Job Management Partner 1/Base User's Guide.
Set the information about connection to NNMi.

Execute the ssonnmsetup -add command.

For details about the ssonnmsetup command specification, including options, see ssonnmsetup in 5. Commands.

Set the incident definitions of SSO in NNMi.

The following table lists the incident definition file names and definition conditions.

Table 3‒1: Names and registration conditions for incident definition files
#	Incident definition file name	Registration condition
1	`$SSO_INCIDENT/ssoincident.def`	This file must be registered.
2	`$SSO_INCIDENT/apmtrap.def`	Set this file if an APM that does not use TCP communication for event notification is set for process and service monitoring.

The incident definition file ssoincident.def is set by using the nnmconfigimport.ovpl command.

If NNMi is stopped, start it before executing the nnmconfigimport.ovpl command. After moving the current directory to bin in the NNMi installation directory, execute the following command:

nnmconfigimport.ovpl -u user-name -p password -f $SSO_INCIDENT/ssoincident.def

The following describes the values that can be specified for the command arguments.

user-name: Specify the user name of the NNMi administrator.

password: Specify the password for the NNMi administrator account.

You do not need to re-register the incident definition file when you perform an upgrade installation of SSO.

In a distributed configuration, the incident definition file ssoincident.def must be copied and registered to the management manager. Since the incident definition file needs to be registered only once, you do not need to perform registration for each host on which SSO is installed. Registration of apmtrap.def is unnecessary.

Note that the incident definition file must be copied and registered to NNMi on all other hosts specified as transmission destinations in the event destination definition file (ssodest.conf), as in a distributed configuration.

Set the URL action definitions of SSO in NNMi.

The following table lists the URL action definition file names and recommended registration requirements.

Table 3‒2: Names of URL action definition files and recommended registration requirements
#	URL action definition file name	Registration requirement
1	`$SSO_URLACTION/ssourlaction.def`	Set this file if NNMi is other than a multitenant environment.
2	`$SSO_URLACTION/ssourlaction-mt.def`	Set this file if NNMi is a multitenant environment.

The same menu items are registered for either of the above files, but the local settings differ. Select either one of these file names. If both are registered, only the definitions of the file that was registered last are valid.

The roles of the menu items registered in that definition file can be changed according to the operation. For details about the roles, see 2.6.2(2) Action menu access rights and 2.6.4(3) Action menu access rights.

TheURL action definition file is set by using the nnmconfigimport.ovpl command.

If NNMi is stopped, start it before executing the nnmconfigimport.ovpl command. After moving the current directory to bin in the NNMi installation directory, execute the following command:

nnmconfigimport.ovpl -u user-name -p password -f $SSO_URLACTION/ssourlaction.def

The following describes the values that can be specified for the command arguments.

user-name: Specify the user name of the NNMi administrator.

password: Specify the password for the NNMi administrator account.

Do not re-register the URL action definition file when you perform an upgrade installation of SSO. If you do so, resource status change events that were generated before the upgrade installation can no longer be used to display incident graphs.

However, you must re-register the URL action definition file if you set the NNM action address definition file when you upgrade SSO from a version earlier than 10-10.

In a distributed configuration, the URL action definition file must be copied and registered to the management manager. Since the URL action definition file needs to be registered only once, you do not need to perform registration for each host on which SSO is installed.

Note that the URL action definition file must be copied and registered to NNMi on all other hosts specified as transmission destinations in the event destination definition file (ssodest.conf), as in a distributed configuration.

Register the users for user authentication on the SSO console.

Set the user authentication method on the SSO console. Two user authentication methods are available. Set the desired method in the ssoconsoled action definition file. For details about the settings of the ssoconsoled action definition file, see 6.3.23 ssoconsoled action definition file (ssoconsoled.def).

If the user authentication method is the SSO authentication method:

Execute the ssoauth -add command.

For details about the SSO console, see 2.1.1 SSO console.

For details about the ssoauth command, see ssoauth in 5. Commands.

If the user authentication method is the JP1 authentication method:

For details about how to register the JP1/Base authentication user, see the Job Management Partner 1/Base User's Guide.
Set the community name.
Set the resource collection conditions.
Set the process monitoring conditions.

To Page Top