Sun N1 Advanced Architecture for SAP Solutions 5.2.1 User's Guide

Chapter 2 N1 AA Manager

This chapter describes the configuration and use of N1 AA base components. These base components are functions and features with an overall relationship across all of the N1 AA modules.

User Management

Login accounts for the N1 AA Manager are created and managed at the OS-level. For more information, see Sun N1 Advanced Architecture for SAP Solutions 5.2.1 Installation Guide.

Customizing

General Customizing

Purpose: General customizing for N1 AA
Menu: Administration ⇒ Customizing
Tasks for an initial basic setup: Mandatory

Figure 2–1 General Customizing

General customizing table with nine entries

General customizing for N1 AA is done here. The following parameters are supported:

Table 2–1 General Customizing Parameters


Parameter	Description	N1 AA Module	Value
`none.general.auth.analyzer`	Determines if the Analyzer menu is available in the GUI or not	Mandatory for: Analyzer	Insert this parameter with any value to make the menu available
`none.general.auth.builder`	Determines if the Builder menu is available in the GUI or not	Mandatory for: Builder	Insert this parameter with any value to make the menu available
`none.general.auth.deployment`	Determines if the Deployer menu is available in the GUI or not	Mandatory for: Deployer	Insert this parameter with any value to make the menu available
`none.general.n1aa.communication`	Defines the communication from the N1 AA Server to the N1 AA Clients. The Analyzer uses simple OS commands on the N1 AA Clients to import the Performance Collector data: Localhost: N1 AA Server Remote host: All N1 AA Clients OS User: noaccess OS Commands: `tail`, `cat`, and `logadm` Configure this parameter with the prefix to use in front of the fixed coded part. See examples. Note – You can add an additional parameter `servergroup.general.n1aa.communication`. For example, if there is a server group `DEV` configured, than you can overwrite the value customized by parameter `none.general.n1aa.communication` specifically in the server group `DEV` by adding the parameter `dev.general.n1aa.communication`. This overwrites the parameter `none.general.n1aa.communication` within this dedicated server group. You could configure the communication type server group dependently. This parameter must be in line with the configured communication method OS level. This is normally done during the installation process of N1 AA. For more information see the Sun N1 Advanced Architecture for SAP Solutions 5.2.1 Installation Guide.	Mandatory for: Analyzer	Examples: Value = /opt/SUNWn1aa/aasap/bin/aasap Command, that is used within N1 AA: /.../aasap `remotehost` `command` Value = rsh Command that is used within N1 AA: rsh `remotehost` `command` Value = ssh Command that is used within N1 AA: ssh `remotehost` `command` Value = ssh `-p` 5122 Command that is used within N1 AA: ssh `-p` 5122 `remotehost` `command`
`none.general.n1aa.logfile`	Defines the location of the N1 AA logfile. Note – Make sure that the OS user `noaccess` has the rights to create the file in the target directory or create an empty log file manually. If you create the log file manually, make sure that the OS user `noaccess` has the rights to write to the file.	Mandatory for all modules	Example: `/var/opt/SUNWn1aa/n1aa.log`
`none.general.n1aa.loglevel`	Defines the log level to be used.	Mandatory for all modules	Available levels are: DEBUG, INFO, SUCCESS, WARNING, ERROR, FATAL, PANIC
`none.general.sps.installpath`	Installation path to the SPS Java API Note – N1 AA has to be restarted for changes on `none.general.sps.installpath` to take effect.	Mandatory for: Builder Deployer	Example: `/opt/SUNWn1sps/N1_Service_Provisioning_System_5.2.1/cli`
`none.general.sps.user`	Specifies the user that N1 AA uses to log in to SPS.	Mandatory for: Builder Deployer	Example: spsusr
`none.general.sps.password`	Specifies the password, that N1 AA uses to log in to SPS.	Mandatory for: Builder Deployer	Example: spspw

Server Groups

Purpose: Definition of Server Groups
Menu: Administration ⇒ Customizing
Tasks for an initial basic setup: Mandatory

Figure 2–2 Server Groups

Server Groups, groups of physical hosts, allow you to split your landscape into administrative units. This splitting is reflected in the GUI. You always work inside a Server Group. Your actions are limited to the hosts belonging to the server group.

Define Server Groups

Name – Short name of the Server Group
Description – Description of the Server Group

Note –

Be careful when deleting a server group. You lose all physical hosts including their settings and referenced data. For example, N1 AA Analyzer cube data. For more information, see Chapter 3, N1 AA Analyzer. In order to keep these physical hosts, assign the hosts to another server group before deletion.

Physical Hosts

Purpose: Define hosts of the N1 AA landscape and assign them to Server Groups.
Menu: Administration ⇒ Customizing
Tasks for an initial basic setup: Mandatory

Figure 2–3 Physical Hosts

Maintain all physical hosts that are part of your N1 AA landscape.

Physical host: Hostname (IP name) of the server
Server Group: Assign the host to an existing group
Date import (yes or no)
- yes (default): The performance data of this host is regularly imported into the database by the import job. For more information, see Data Imports. This is the normal case.
- no: This host's data is not imported. The import job ignores this host. Use this behavior in special situations. For example, if you know that the host is unavailable for a long period.
OS provisioning (yes or no)
- yes (default): This host is available in the N1 AA Builder as a target host for OS provisioning.
- no: This host is locked for OS provisioning.
SW provisioning (yes or no)
- yes (default): This host is available in the N1 AA Builder as a target host for SW provisioning.
- no: This host is locked for SW provisioning.

Caution –

Deleting a physical host erases these settings and all data related to this entry. For example, N1 AA Analyzer cube data. For more information, see Chapter 3, N1 AA Analyzer.

Attention: For N1 AA Builder - OS Provisioning only

Using OS Provisioning in N1 AA, the selected target hostname will automatically be extended by the suffix –target. This means that the resulting installation target is hostname–target . This is in line with the default settings within the N1 SPS OSP Plug–in. Do not modify these default settings within SPS. Otherwise, OS Provisioning does not work with the N1AA Builder.

For more information on how to manage hosts in the N1 SPS environment, see Sun N1 Service Provisioning System 5.2 System Administration Guide and Sun N1 Service Provisioning System User’s Guide for OS Provisioning Plug-In 3.1.

Scheduler

This is a general description of the job scheduler. The Chapter 3, N1 AA Analyzer, Chapter 4, N1 AA Builder, and Chapter 5, N1 AA Deployer describe the necessary jobs needed for the operative business.

Purpose: Define jobs scheduled by N1 AA and view their logs
Menu: Administration ⇒ Scheduling
Tasks for an initial basic setup: None

Based on jobs and the scheduler, N1 AA can handle asynchronous and periodically scheduled task executions in background threads. Jobs will be automatically scheduled in the background (for example if you start or stop a resource in the N1 AA Deployer), but you can create jobs manually too.

Name: Name of the job.
Class: Fully-qualified class name of an N1 AA scheduling job, which is a descendant of class com.sun.web.admin.n1aa.common.SchedulingJob.
Parameters: Parameters of the job. Spaces to separate parameters and quotation marks if a space is contained in a parameter. Syntax is analogous to console line arguments.
Persistence
- Persistent: Job definition and its log is saved permanently in the database. All data is available after a restart of N1 AA.
- Transient: Job definition and its log is lost after a restart of N1 AA.
Start: Date and time this job is should be executed for the first time.
Interval: Restart period in seconds. A value of 86400 will define a daily interval. An empty field means that the job is immediately re-executed after it is finished.
Repeats: Number of restarts that will appear on this job. A value of 1 specifies this job to be executed once, 2 for twice and so on. Empty field means an infinite repetition.

Each job collects messages into its own log that can be viewed. You find scheduling events, for example, Job started or Job finished, job info messages or errors along with a timestamp and a log level.

The default values are set to show only the most recent log lines at log level INFO. You can change these settings, For example, to see the complete log or ERROR messages only.