ServerView Operations Manager V7.02

(1)

Installation Guide - English

FUJITSU Software ServerView Suite

ServerView Operations Manager

V7.02

Installing ServerView Operations Manager Software under Linux (Operations Manager, Update Manager, Event Manager)

(2)

Comments… Suggestions… Corrections…

The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs.

Feel free to send us your comments by e-mail to [email protected].

Certified documentation according to DIN EN ISO

9001:2008

To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality

management system which complies with the requirements of the standard DIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de

Copyright and trademarks

(3)

1 Introduction

ServerView Operations Manager (Operations Manager for short) is a free server management module of the Fujitsu ServerView Suite. It is used for central administration of industry-standard servers which run the operating systems Windows and Linux (SUSE and Red Hat) or which serve as hosts for virtual machines (VMs) that use hypervisors such as VMware ESX/ESXi, Citrix XenServer or Hyper-V.

The standardized management of all servers occurs via one or more central management stations, which you can access from any workstation in the network that has a popular Web browser and the Java Runtime Environment. Operations Manager controls the individual systems, including critical hardware components such as processors, RAM, hard disks, fans and power supply. It monitors and controls the power consumption, analyzes the performance and utilization data and updates the server configuration.

The security concept of Operations Manager includes role-based user management based on three underlying concepts:

l Global user management via an LDAP directory service (Lightweight Directory Access Protocol)

l Role-Based Access Control (RBAC)

(8)

1 Introduction

Server management with Operations Manager offers important benefits to operators of a comprehensive server network:

l Higher productivity thanks to high failsafety of the servers

l Reduced costs through automated monitoring of the IT infrastructure l Flexible expansion possibilities for the servers, as Operations Manager can

be easily adjusted to changed conditions

l Shorter downtimes thanks to simplified error analysis

l Guarantees energy-efficient and, where possible, uninterruptible server operation

l Quicker response times in the event of errors

l Reduction in total cost of ownership (TCO) through efficient use of network components and their resources

l Very easy operation thanks to ergonomic software: clearly laid out, intelligent user guidance and supportive help system

1.1 Target groups and objectives

(9)

1.2 Technical requirements

1.2.1 Last-minute changes/corrections

Any last-minute changes/corrections of the technical requirements can be found in the Readme file on the ServerView Suite DVD 2. You have the following options:

ServerView Operations Manager

l On the DVD switch to the directory SVSSoftware – Software – ServerView – Linux – ServerView_S2.

l Start the DVD and select in the Welcome dialog ServerView Software Products – Start; Info under ServerView – Operations Manager.

1.2.2 Management console

l Standard PC, LAN with http access

l Microsoft Windows with Internet Explorer V9/V10 or Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_45 or higher, Firefox as of V25 is required. l SUSE/Red Hat Linux with default Web browser released with distribution l Java Runtime Environment (JRE) V1.7.0_40 or higher

1.2.3 Central management station (CMS)

Hardware

l PRIMERGY server

l Only for PRIMEQUEST: PRIMEQUEST server l Processors with at least two cores

l Main memory: at least 4 GB RAM l 100 MBit-LAN

l At least 100 GB free disk space

l Graphics 1280 x 1024 (recommended: minimum 1024 x 768)

(10)

1 Introduction

Software

l SUSE (SLES 11): SP2 and SP3 l Red Hat Enterprise Linux 5.9/5.10 l Red Hat Enterprise Linux 6.4/6.5 l Red Hat Enterprise Linux 7.0

Database (local and remote)

l PostgreSQL 8.4.17 (contained in the ServerView package)

Java Runtime Environment

l Java Runtime Environment (JRE) V1.7.0_40 or higher

1.3 ServerView database

Operations Manager uses an SQL database. This database is a prerequisite for the Operations Manager software. PostgreSQL is used as the database management system.

As of Operations Manager version 4.80 you can install the ServerView database separately on a remote database server. For further information, see"ServerView database on a remote database server" on page 82.

The installation software contains the PostgreSQL database management system. This PostgreSQL is automatically installed when you install the

Operations Manager software. This does not affect the operation of an already installed PostgreSQL database management system. For PostgreSQL

(11)

1.4 Operating-System-Dependent packages

Depending on the installed operating system, you must install additional packages for the various ServerView components (Operations Manager and ServerView RAID Manager).

Very detailed lists on operating-system-dependent packages are provided in"Requirements" on page 31.

When you update the relevant operating systems, the version specifications of the packages may change.

The extra packages required for ServerView agents are described in "ServerView Agents for Linux" installation guide.

SLES 11

With SUSE SLES 11, the easiest way to subsequently install the required rpm packages is via the YaST control center by selecting Software – Install or delete software. YaST also resolves the dependencies and selects the installation source.

Red Hat (RHEL5, RHEL6, and RHEL7)

Subsequent installation of the required rpm packages should be done by YUM or by Add/Remove Software functionality available in Gnome Tool bar (Red Hat 5 in entry Application, Red Hat 6 in entry System - Administration). These tools detect themselves when a package has dependencies on other packages which are not yet installed. The missing packages are then listed and you can confirm whether you want to have these installed as well.

Installation is possible from the DVD or the mounted DVD image (e.g. mount RHEL5-Server-20070208.0-i386-DVD.iso -t iso9660 -o loop /mnt) with the rpm command.

(12)

1 Introduction

1.5 Changes since the previous version

This edition of the manual applies to ServerView Operations Manager V7.02 or later and replaces the online manual "ServerView Operations Manager V7.00 -Installing ServerView Operations Manager Software under Linux", edition October 2014.

The manual features the following changes and enhancements: l As of ServerView Operations Manager V7.02, Java 8 is required on

management console and central management station.

1.6 ServerView Suite link collection

Via the link collection, Fujitsu Technology Solutions provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers.

(13)

The downloads include the following:

o Current software statuses for the ServerView Suite as well as

additional Readme files.

o Information files and update sets for system software components

(BIOS, firmware, drivers, ServerView agents and ServerView update agents) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express.

o The current versions of all documentation on the ServerView Suite.

You can retrieve the downloads free of charge from the Fujitsu Technology Solutions Web server.

For PRIMERGY servers, links are offered on the following topics: l Service Desk

l Manuals

l Product information l Spare parts catalogue

Access to the link collection

You can reach the link collection of the ServerView Suite in various ways: 1. Via ServerView Operations Manager.

l Select Help – Links on the start page or on the menu bar. This opens the start page of the ServerView Suite link collection.

2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu Technology Solutions manual server.

You access the start page of the online documentation via the following link:

http://manuals.ts.fujitsu.com

l In the selection list on the left, select x86 Servers.

l On the right, click PRIMERGY ServerView Links under Selected documents.

This opens the start page of the ServerView Suite link collection.

(14)

1 Introduction

3. Via the ServerView Suite DVD 2.

l In the start window of the ServerView Suite DVD 2, select the option Select ServerView Software Products.

l Click Start. This takes you to the page with the software products of the ServerView Suite.

l On the menu bar select Links.

This opens the start page of the ServerView Suite link collection.

1.7 Documentation for the ServerView Suite

The documentation can be downloaded free of charge from the Internet. You will find the online documentation athttp://manuals.ts.fujitsu.comunder the link x86 Servers.

(15)

1.8 Typographic conventions

The following typographic conventions are used: Convention Explanation

Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices.

Indicates additional relevant information and tips. bold Indicates references to names of interface elements.

monospace _{Indicates system output and system elements, e.g., file names}

and paths. monospace

semibold Indicates statements that are to be entered using the keyboard. blue

continuous text

Indicates a link to a related topic.

pink continuous text

Indicates a link to a location you have already visited.

<abc> Indicates variables which must be replaced with real values. [abc] Indicates options that can be specified (syntax).

[key] Indicates a key on your keyboard. If you need to enter text in uppercase, the Shift key is specified, for example, [SHIFT] + [A] for A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols.

Screenshots

Some of the screenshots are system-dependent, so some of the details shown may differ from your system. There may also be system-specific differences in menu options and commands.

(16)

1 Introduction

1.9 Product names - conventions

In the document, product names used in the text are abbreviated as follows:

(17)

Windows Server 2008 and 2008 R2

(18)

1 Introduction

Linux

(19)

2 PRIMERGY server management

2.1 Architecture

The architecture of ServerView Operations Manager is based on a management console, a central management station (CMS) and the managed servers.

(20)

2 PRIMERGY server management

Management console

A browser-based console allows you to manage the servers and display the determined data. The following can be used as a browser:

l Microsoft Windows with Internet Explorer or Mozilla Firefox

l SUSE/Red Hat Linux with default Web browser released with distribution

(21)

Central management station (CMS)

On the central management station the ServerView

Operations Manager is installed. The optional components of the ServerView Suite, such as Virtual IO-Manager, are also installed on the central management station and integrated in Operations Manager.

The central management station (and thus the ServerView Operations Manager with its components) may also run on a Windows or Linux virtual machine (VM).

The global user management of the ServerView Suite and of the iRMC each centrally stores users for all Central

Management Stations (CMS) / iRMC in the directory of an LDAP directory service. This enables you to manage the users on a central server. The users can therefore be used by all the CMS and iRMC that are connected to this server in the

network.

The ServerView Suite currently supports the following directory services:

l OpenDS/OpenDJ (running in embedded mode on JBoss 5.1 resp. JBoss 7).

l Microsoft Active Directory

During the installation of ServerView Operations Manager you have the option to choose ServerView’s internal directory service (OpenDJ). For further information about the use of directory services with ServerView, refer to the manual ’’User Management in ServerView’’ (see"Documentation for the ServerView Suite" on page 14).

The data which ServerView creates and uses is stored in an SQL database within an SQL Server. The following SQL Server are part of the ServerView Operations Manager installation:

l SQL Server 2008 R2/2005 Express under Windows Server l PostgreSQL under Linux

However, other Microsoft SQL Server databases can be used under Windows.

(22)

The Java Runtime Environment is required on the central management station.

How to install the ServerView Operations Manager is explained in the following manuals:

l Installing ServerView Operations Manager Software under Windows

l Installing ServerView Operations Manager Software under Linux

Managed servers

On the managed servers, ServerView agents, CIM providers, or ServerView Agentless Service should be installed, which supply the information to the central management station. ServerView RAID Manager and ServerView Update Agent should be also installed on the managed servers. The installation of ServerView agents on virtual machines (VMs) is not released.

l The ServerView agents are available for Windows, Linux, VMware ESX and Citrix XenServer.

l ServerView CIM Providers are available for Windows, Linux and VMware ESXi.

ServerView Operations Manager currently only supports ServerView CIM providers for VMware ESXi.

How to install them is explained in the following manuals: l ServerView Agents for Windows

l ServerView Agents for Linux

l Installing ServerView ESXi CIM Provider

(23)

2.2 Installation on the central management station

You have to install Operations Manager (incl. ServerView Update Manager) on a management station and thus of monitoring the PRIMERGY servers via PC or notebook with a standard Web browser. Furthermore you can install the Event Manager on the central management station or on its own on another server. To display CIM indications from VMware vSphere Hypervisor server (ESXi-Server) in Event Manager, you have to install Operations Manager on the same server. You can install the Operations Manager on the following operating systems:

l Windows, SUSE Linux and Red Hat Linux.

The Operations Manager software is supplied on the ServerView Suite DVD 2: l Installation under Linux is script-based and involves the installation of

Operations Manager, Update Manager, and Event Manager.

The installation is described in"Installing ServerView Operations Manager" on page 25.

l A Installation Wizard is provided for installation under Windows. This covers the installation of Operations Manager, Update Manager, and Event Manager. In addition, the Wizard permits separate installation of the Operations Manager software on different servers.

Installation can also occur in the Windows command line mode.

The installation is described in "Installing ServerView Operations Manager Software under Windows" user guide.

(24)

2.3 Installation on the managed servers

The following components must be installed on the managed servers. These are operating-system-specific programs which supply information to the

management station, which supplies information to the central management station:

l ServerView agents, CIM providers, or ServerView Agentless Service The ServerView agents are available for Windows, Linux, VMware ESX and Citrix XENServer. CIM providers are available for VMware ESXi. The

installation is described in the "ServerView Agents for Windows", "ServerView Agents for Linux", "ServerView CIM Providers for Windows"and "Installation ServerView ESXi CIM Provider" user guides.

ServerView Agentless Service is available for Windows and Linux. The ServerView System Monitor is installed automatically (via the

ServerView agents installation) and allows you to monitor and check some server information locally on the server. A detailed description can be found in the "ServerView System Monitor" user guide.

l ServerView update agent

To keep the managed servers up-to-date by Update Management functions the ServerView update agent must be installed on the managed servers. How to do this is described in the "ServerView Update Management" user guide.

Additional installation on the management station

ServerView RAID Manager

ServerView RAID Manager offers standardized administration and management of hard disks for PRIMERGY servers.

Unless the ServerView RAID Manager is installed, no information about RAID drives and their statuses will be available.

(25)

3 Installing ServerView Operations

Manager

This chapter describes how to install the Operations Manager software on the management station under Linux. Installation of the Operations Manager software involves installing Operations Manager and Event Manager. The corresponding software is supplied on the ServerView Suite DVD 2.

3.1 ServerView Operations Manager components

ServerView Operations Manager installation

When you install ServerView Operations Manager, the following ServerView components are also automatically installed:

ServerView Configuration Manager

With ServerView Configuration Manager, you can make system-dependent configurations on a managed server. (Only supported for servers on which the ServerView agents are installed.)

ServerView Archive Manager

With Archive Manager you can record system and operating data of PRIMERGY servers and store it centrally. This data can then be checked and evaluated.

ServerView Inventory Manager

With Inventory Manager you can retrieve data of a managed server or multiple servers and display it on the screen. You can also export the data from Operations Manager and store it in various formats (e.g. CSV, ODBC). ServerView Performance Manager

With Performance Manager you can monitor the performance of specific server components. Performance Manager works on the basis of rules. The centrally created rules can be executed on any number of servers.

ServerView Threshold Manager

With Threshold Manager you can monitor one or more managed PRIMERGY servers and any virtual machines running on them centrally from the

(26)

3 Installing ServerView Operations Manager

management station on the basis of threshold values. ServerView Remote Management Frontend

ServerView Remote Management Frontend provides a Web-based work environment for the remote management of PRIMERGY servers.

ServerView Update Manager installation

When you install Update Manager, the following ServerView Operations Manager components are also installed:

Update Manager

With Update Manager you can install and update software across an entire domain via a central management station.

Repository Manager

With Repository Manager you can manage the update repository. Download Manager

With Download Manager you can conveniently obtain the latest statuses of firmware, BIOS, drivers and ServerView agents for your servers.

Configuration

With Configuration you can set global parameters for Update Manager.

ServerView Event Manager installation

When you install Event Manager, the following ServerView Operations Manager components are also installed:

Alarm Monitor

Alarm Monitor displays all incoming alarms for the selected servers and server groups in the Operations Manager main window.

Alarm Configuration

(27)

3.2 JBoss Web server

The Web server used is JBoss. The necessary files for JBoss are automatically installed when ServerView Operations Manager is installed. JBoss is configured as a standalone service ServerView JBoss Application Server 7.1.1.

You can start and stop the service. Use the following command: /etc/init.d/sv_jboss start|stop

You can enable or disable restarting JBoss once a month. Disable is set by default. If you want to enable restarting JBoss monthly, you should call ChangeComputerDetails.sh command.

The ChangeComputerDetails.sh command is located in the directory /opt/fujitsu/ServerView/svom/ServerView/Tools.

If you want to enable restarting JBoss monthly, proceed as follows. 1. Switch to the directory where ChangeComputerDetails.sh is located:

cd

/opt/fujitsu/ServerViewSuite/svom/ServerView/Tools 2. Run ChangeComputerDetails.sh:

sh ChangeComputerDetails.sh

3. Type yes when you are asked Do you want to restart Jboss once a month?

Automatic deletion of JBoss access logs

Log files localhost_access_log.<YYYY-MM-DD>.log are written in the directory <installation_path>/jboss/standalone/log. A separate log is created for each day. In previous versions they were never deleted.

As of version 5.10, JBoss now includes automatic deletion. In the directory <installation_path>/jboss/standalone/svconf the sv-com-config.xml configuration file describes the parameters:

<ns0:fileNamePrefix>localhost_access_log.</ns0:fileNamePrefix> List of file name prefixes, qualifying the files that are to be checked for deletion. The default is a list with the single entry "localhost_access_log.".

(28)

<ns0:testInterval>12:00</ns0:testInterval>

Test interval, measured in minutes. The test interval can range between 1 minute and 24 hours. The behavior of the automated file deletion depends on the specified value:

Number [1...1439]

File checking begins when JBoss starts up, and is repeated at the specified time interval.

Time [hh:mm]

The test interval is 24 hours and the file checking occurs every day at the specified time. (The values for hh range from 00 till 23.) The default is 12:00, i.e. files are checked every day at noon. <ns0:maxAge>10080</ns0:maxAge>

Maximum age of a log file, measured in minutes. Any file matching an entry in the fileNamePrefix list which is older than this value is deleted. The default is 10080, i.e. seven days. If no value is specified in the configuration file, the value 4320, i.e. three days, is used.

3.2.1 Calling and ports used

The entry address of the Operations Manager begins with the prefix https.

Port Used for

3169 http (When trying to access this port, Operations Manager versions older than V4.92 are

automatically redirected to port 3170.)

3170 https (The port must be unlocked in the firewall.)

3171 Update Management (The port must be unlocked

in the firewall to allow Update Management.) 3172 Remote Connector Service (Server Configuration

(29)

Port Used for 1325, 9999

Some additional ports are used for dynamical assignment of system components.

JBoss (only used for internal socket connections)

1473 non-SSL port of ServerView’s directory service (OpenDJ)

1474 LDAPS, if OpenDJ is configured as directory service.

4444 OpenDJ control port

9212 PostgreSQL database server (only for Linux) 9363 used by the Operations Manager to contact XEN

daemons

16509, 16514 used by the KVM service

For detailed security information see the White Paper “Secure PRIMERGY Server Management“.

To gather information, Operations Manager accesses the following ports of all network nodes of a subnet which is specified on ServerBrowser and managed servers.

80 Citrix

135 Hyper-V

161 SNMP

443 VMware

623 BMC (iRMC)

3172 ServerView Remote Connector

5988 VMware

5989 VMware

(30)

9363 XEN

16509 KVM

16514 KVM

3.2.2 Role-based user administration

JBoss also enables role-based user administration. For further information on managing certificates, see "User Management in ServerView" user guide.

3.2.3 Managing certificates

To communicate with the JBoss Web server, Web browsers always use an HTTPS connection (i.e. a secure SSL connection). Therefore, the JBoss Web server needs a certificate (X.509 certificate) to authenticate itself at the Web browser. The X.509 certificate contains all the information required to identify the JBoss Web server plus the public key of the JBoss Web server.

For further information on managing certificates, see "User Management in ServerView" user guide.

3.3 Web browser

A Web browser is required to display the data. This means that the data can be transmitted via a LAN to any other computer that has a Web browser and displayed there. The browser must be able to interpret HTML V3.2 and Javascript V1.1.

If you should experience problems when accessing the Web server, make the following settings in the browser:

l Disable the access option for the use of a proxy entirely in the browser, or l Enter the IP address at an appropriate position to specify that no proxy is to

(31)

3.4 Changes on the system

ServerView Operations Manager creates a user svuser and a group svgroup. Almost all processes are started under this ID.

By default, Operations Manager installs its own directory service, OpenDJ. You cannot change the password via OpenDJ.

You can only change it locally by using the script

ChangeComputerDetails.sh, see"Changing configuration parameters" on page 69.

For the PostgreSQL server the user postgpls is created. For regular database server activities a cron job is created.

For ODBC access to the database server, additions are made to the configuration files of the ODBC Manager.

For snmptrap the configuration file /etc/snmp/snmptrapd.conf is modified to contain the following entries:

disableAuthorization yes ignoreAuthFailure yes

3.5 Requirements

On 64-bit systems, the distribution includes many packages for both architectures, 32-bit and 64-bit. 32-bit packages are distinguished differently on the different platforms. On SLES systems the package name has the file extension 32bit. On RHEL systems the architecture part of the package takes the value i386, i586 or i686.

3.5.1 Management station

l JBoss Web server

The JBoss Web server is installed when you install the ServerView Operations Manager software. The corresponding service is automatically started when you start Operations Manager.

(32)

Before version V5.00, httpd service was required. V5.00 or higher does not require httpd service.

l Network configuration

The commands hostname and hostname -f must deliver valid names. The network configuration can be set up in various ways. This condition is satisfied for many configurations if the server is entered in /etc/hosts with its domain name.

Example

111.22.33.44 myserver.mydomain

The local host must be entered in /etc/hosts with the IP address 127.0.0.1 to give ServerView access to the database server.

With ServerView Operations Manager as of V5.30 the fully qualified hostname of the central management station is decisive for its correct working. Normally the fully qualified hostname is the host’s name plus domain name. But depending on the netconfiguration it may be a simple hostname without any domainname.

Your network configuration must allow access to the central management station by using the fully qualified hostname from:

o the central management station itself o any monitoring station

o the managed node

o HW management boards like MMB, iRMC

l Java Runtime Environment

You can check whether the package is installed with the following command:

rpm -q jre

Install the package for the Java Runtime Environment from the ServerView Suite DVD 2:

(33)

SVSSoftware – Software – Other_Tools – Java – Linux 4. Extract the package for Linux with the following command:

sh jre-<version>-linux-i586-rpm.bin 5. Accept the license agreement.

6. Install the extracted rpm file.

If you are also using the management station as a management console, the Java plug-in must be activated and depending on the platform 64-bit jre must be installed.

l SELinux must be deactivated on distributions on which it is not supported by ServerView Operations Manager.

SELinux is supported on RHEL6 and RHEL7.

On these distributions you may set SELinux to enforcing with default policies.

On the remaining supported distributions, SELinux must be set to disabled.

l Root / superuser access

ServerView Operations Manager creates a user postgpls. Postgpls and root require superuser access. The user postgpls is secure, as it can only be called via superuser.

l Directory access rights

The /tmp directory must have read, write and execution rights for all. l Use the package managers of the platforms to install missing packages.

These are Yast on SLES platforms and Add/Remove Software in menu bar as well as YUM on RHEL platforms. These platform managers implicitly resolve all dependencies. How to configure YUM, see"Configuring YUM" on page 42.

You may check whether a package is installed with the following command:

rpm -q <package name>

On RHEL 64-bit systems you must use the following command in order to view the architecture of the package. Please pay attention to this.

rpm -q --queryformat “%{NAME} %{ARCH}”

(34)

For RHEL 64-bit platforms we always also state the architecture of the package separated by a dot from the package name. You can directly use this syntax name.arch in the package manager.

Prerequisites packages per platform RHEL 5.9 32-bit: l compat-libstdc++-33 l curl l e2fsprogs-libs l glibc l gzip l keyutils-libs l krb5-libs l libgcc l libidn l libselinux l libsepol l libtermcap l libxml2 l net-snmp l openssl l unixODBC l unixODBC-libs l zlib

l Prerequisites for special functionality: DeskView Interface: curl

(35)

l e2fsprogs-libs.i386 l glibc.i686 l gzip.x86_64 l keyutils-libs.i386 l krb5-libs.i386 l libgcc.i386 l libidn.i386 l libselinux.i386 l libsepol.i386 l libtermcap.i386 l libxml2.i386 l net-snmp.x86_64 l openssl.i686 l unixODBC.i386 l unixODBC-libs.i386 l zlib.i386

l Prerequisites for special functionality: DeskView Interface: curl.i386

RHEL/KVM monitoring: libvirt.x86_64 RHEL 5.10 32-bit:

See package list of"RHEL 5.9 32-bit:" on page 34. RHEL 5.10 64-bit:

(36)

3 Installing ServerView Operations Manager l keyutils-libs l krb5-libs l libcom_err l libcurl l libgcc l libidn l libselinux l libssh2 l libstdc++ l libtool-ltdl l libxml2 l ncurses-libs l net-snmp l nspr l nss l nss-softokn-freebl l nss-util l openldap l openssl l unixODBC l zlib

RHEL/KVM monitoring: libvirt-client RHEL 6.4 64-bit:

(37)

l keyutils-libs.i686 l krb5-libs.i686 l libcom_err.i686 l libcurl.i686 l libgcc.i686 l libidn.i686 l libselinux.i686 l libssh2.i686 l libstdc++.i686 l libtool-ltdl.i686 l libxml2.i686 l ncurses-libs.i686 l net-snmp.x86_64 l nspr.i686 l nss.i686 l nss-softokn-freebl.i686 l nss-util.i686 l openldap.i686 l openssl.i686 l unixODBC.i686 l zlib.i686

l Prerequisites for special functionality: DeskView Interface: curl.x86_64

RHEL/KVM monitoring: libvirt-client.x86_64 RHEL 6.5 32-bit:

See package list of"RHEL 6.4 32-bit:" on page 35. RHEL 6.5 64-bit:

See package list of"RHEL 6.4 64-bit:" on page 36.

(38)

3 Installing ServerView Operations Manager RHEL 7.0 64-bit: l glibc.i686 l gzip.x86_64 l keyutils-libs.i686 l krb5-libs.i686 l libcom_err.i686 l libcurl.i686 l libgcc.i686 l libselinux.i686 l libstdc++.i686 l libtool-ltdl.i686 l libxml2.i686 l ncurses-libs.i686 l net-snmp.x86_64 l nss-softokn-freebl.i686 l openssl-libs.i686 l pcre.i686 l unixODBC.i686 l xz-libs.i686 l zlib.i686

l Prerequisites for special functionality DeskView Interface: curl

RHEL/KVM monitoring: libvirt-client SLES11 SP2 32-bit:

l cyrus-sasl l glibc

(39)

l libcom_err2 l libcurl4 l libgcc46 l libidn l libldap-2_4-2 l libltdl7 l libopenssl0_9_8 l libstdc++33 l libstdc++46 l libxml2 l net-snmp l termcap l unixODBC l zlib

(40)

3 Installing ServerView Operations Manager l libopenssl0_9_8-32bit l libstdc++33-32bit l libstdc++46-32bit l libxml2-32bit l net-snmp l termcap-32bit l unixODBC l unixODBC-32bit l zlib-32bit

(41)

l termcap l unixODBC l zlib

RHEL/KVM monitoring: libvirt SLES11 SP3 64-bit: l cyrus-sasl-32bit l glibc-32bit l gzip l keyutils-libs-32bit l krb5-32bit l libcom_err2-32bit l libcurl4-32bit l libgcc_s1-32bit l libidn-32bit l libldap-2_4-2-32bit l libltdl7-32bit l libopenssl0_9_8-32bit l libstdc++33-32bit l libstdc++6-32bit l libxml2-32bit l net-snmp l termcap-32bit l unixODBC l unixODBC-32bit l zlib-32bit

l Prerequisites for special functionality

(42)

DeskView Interface: curl RHEL/KVM monitoring: libvirt l Configuring YUM

You need to provide a configuration file in /etc/yum.repos.d to make the DVD or the iso-file of the RHEL distribution known to YUM.

1. Often the RHEL distribution DVD or an iso-file of the DVD is mounted to the directory /media/RHEL xxx xxx xx, containing several blanks. YUM cannot handle such paths. Therefore do the following:

ln -s ‘/media/RHEL xxx xxx xx’ /tmp/instmedia

Example

ln -s '/media/RHEL_6.2 x86_64 Disc 1' /tmp/instmedia

The automatic typing extension of the shell might insert \ before the blanks into the path name of the RHEL iso. Be sure to remove them.

2. The RHEL DVD / iso file contains several YUM repositories. You need to specify each of the repositories in the YUM configuration file, if you want to use it. The main repository is located under the directory Server. Normally you only need this.

In the directory /etc/yum.repos.d create a file named rheldistro.conf with the following contents.

Example for RHEL5

[instserver]

name=RHEL 5.x iso image / directory Server baseurl=file:/tmp/instmedia/Server

enabled=1 gpgcheck=0 [instvt]

(43)

The directory VT on the DVD / iso-file contains the virtlib packages that you may need.

Example for RHEL6:

name=RHEL 6.2 iso image Server baseurl='file:/tmp/instmedia/Server' enabled=1[instserver]

gpgcheck=0

3. Test your YUM configuration:

yum list unixODBC

should list

l unixODBC on all SLES / 32-Bit and RHEL / 32-Bit l unixODBC.i686 and unixODBC.x86_64 on RHEL / 64-Bit l unixODBC and unixODBC-32bit on SLES / 64-Bit

3.5.2 Management console

l Web browser (Linux): default Web browser released with distribution Please make sure that the Java plug-in is activated.

If the Java plug-in is not yet installed on the management console, proceed as follows to install it:

1. Open a terminal window.

2. Install the Java Runtime system from the ServerView Suite DVD 2, see Java Runtime.

3. Set up the link for the plug-in.

On 32-bit systems ascertain the browser’s plug-in directory:

o On RHEL 5, this is usually the following directory:

/usr/lib/<browser_name>/plugins or /opt/lib/<browser_name>/plugins or /usr/lib/mozilla/plugins or

/usr/lib/browser-plugins

(44)

On RHEL 6 the plugin directory is /usr/lib/mozilla/plugins. On SLES 11 the plugin directory is /usr/lib/browser-plugins.

o To find out the directory you can also enter the following

command:

rpm -ql <browser_name> | grep plugins

o Switch to the plug-in directory:

cd <plugin_directory>

o Find out the path name of the plug-in. If a link to libjavaplugin_

oji.so exists, remove it.

rpm -ql jre | grep libnpjp2.so

o Set up the link, e.g.

ln -s /usr/java/<jre1.7.0_

51>/lib/i386/libnpjp2.so libnpjp2.so The following passage is on setting up browser plugins for 64-bit systems: For SLES 11 64-bit, RHEL 5 64-bit and RHEL 6 64-bit proceed in the following way.

Ascertain the browser's plugin directory:

o On SLES 11 64-bit this is usually /usr/lib64/browser-plugins. o On RHEL 5 and RHEL 6 the plugin directory is

/usr/lib64/mozilla/plugins.

o If the plugin directory does not exist, then create it.

o Ensure that you installed Java Runtime Environment 64-bit.

Execute the following:

rpm -qa --queryformat '%{Name}-%{VERSION}.% {ARCH}\n' | grep jre

The architecture extension must be x86_64.

o Switch to the plug-in directory:

cd <plugin_directory>

o Find out the path name of the plug-in. If a link to libjavaplugin_

(45)

ln -s /usr/java/<jre1.7.0_

13>/lib/amd64/libnpjp2.so libnpjp2.so l Web browser for Windows:

o Internet Explorer V9/V10

o Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_45 or higher,

Firefox as of V25 is required. l Web browser for Linux:

o Default Web browser released with distribution

3.6 Rights

For installation and configuration, you must have administrator rights, i.e. you must be logged onto the server as the superuser root.

3.7 Installation check list

Web browser No. Check point Configuration 1 Supported version

Supported Web browser for Windows is the following: l Internet Explorer V9/V10

l Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_ 45 or higher, Firefox as of V25 is required.

Supported Web browser for Linux is the following: l Default Web browser released with distribution.

(46)

3 Installing ServerView Operations Manager No. Check point Configuration 2 Trusted sites

If you use Internet Explorer, add the URL of SVOM into Trusted sites.

1. Open Internet Explorer.

2. Select Tools – Internet Options.

3. Click the Security tab and select Local intranet or Trusted sites.

4. Click Sites and enter the URL of the server on which SVOM is installed.

3 Proxy It cannot access to SVOM via proxy. Disable to use proxy on Web browser configuration.

4 32-bit/64-bit

You can use the same architecture of Firefox as the system OS. i.e. 32-bit version of Firefox on 32-bit Linux, and 64-bit version of Firefox on 64-bit Linux.

Table 1: Check list Web browser

Java Runtime Environment (JRE)

No. Check point Configuration 1 Supported

version

V1.7.0_40 or higher

JRE must be installed on both server side (system where SVOM is installed) and client side.

(47)

No. Check point Configuration 3 Java Plug-in

(only for Windows)

Enable the next-generation Java Plug-in must be checked. This item is checked in default.

1. Open Java Control Panel. 2. Select Advanced tab.

3. Open Settings – Java Plug-in.

4. Make sure that Enable the next-generation Java Plug-in is checked.

4 Security Configure security settings as follows: 1. Open Java Control Panel. 2. Select Advanced tab.

3. Open Settings – Security – Mixed code (sandboxed vs. trusted security verification.

4. Check Enable - hide warning and run with protections.

5 Symbolic link (only for Linux)

Set up the link for the plug-in to access from Linux by Firefox. Please see"Requirements" on page 31.

Table 2: Check list JRE

OS settings No. Check point Configuration 1 host name resolve

Hostname of the CMS must be available to resolve from both CMS itself (system where SVOM is installed) and client side. Make sure that the name resolve is available by the following commands.

l Windows:

> tracert <hostname>.<DNS suffix> l Linux:

# traceroute <hostname>.<DNS suffix>

(48)

3 Installing ServerView Operations Manager No. Check point Configuration 2 Network ports

SVOM uses some network ports. Which ports SVOM requires is described in"Calling and ports used" on page 28.

3 host name Hostname and DNS suffix of CMS must not contain underscore ('_').

4 SQL

instance (only for Windows)

If you want to use not a bundled SQL Server but your own SQL Server, you must setup a suitable SQL Server instance before installing SVOM.

Important: Please consider the notes for a local SQL Server and for a remote SQL Server.

5 Active Directory

If you want to use Active Directory for directory service of SVOM, Active Directory must be installed and configured for SVOM before SVOM installation. When you install SVOM, the connection to Active Directory must be available.

Details of configuration of Active Directory are described in the "User Management in ServerView" user guide.

6 Network

drive

It is not possible to install SVOM to network drives.

7 Terminal Server (only for Windows)

If the Terminal Services/Remote Desktop Services server role is installed, a special installation mode is required for installing Operations Manager.

8 /etc/hosts (only for Linux)

localhost must be resolved to 127.0.0.1. It should be configured in /etc/hosts.

9 SELinux (only for Linux)

Disable SELinux on distributions on which it is not supported by SVOM.

(49)

Update Installation No. Check point Configuration 1 Base version

Update installation is only possible from version 6.00.06 or newer.

Table 4: Check list update installation

(50)

3.8 Installing the Operations Manager software

The Operations Manager software (Operations Manager, Event Manager, and the Update Manager) and the database management system PostgreSQL can be installed under Linux (SUSE and Red Hat).

You can install the ServerView database on a remote database server. For further information, see"ServerView database on a remote database server" on page 82.

During installation the following messages can be ignored:

l warning: commands will be executed using /bin/sh l warning: waiting to reestablish exclusive database

lock

Installation is script-based. The log file of the installation process (install.log or upgrade.log) is stored in the directory

(51)

l If you have several different versions of ServerView Operations Manager, make sure to install the latest ServerView Operations Manager version.

l If an newer version of Operations Manager is already installed, you cannot perform a downgrade installation. To downgrade, you must uninstall the existing Operations Manager first.

l To install ServerView Operations Manager, use runlevel 3 or runlevel 5. Runlevel 1 (single mode) is not supported.

l When you install ServerView Linux Agents and ServerView Operations Manager on the same server, and if the Operations Manager is installed before the Agent, the server is not automatically registered to ServerView Operations Manager.

Restart the system, or execute the following commands. /usr/bin/sv_services stop

/usr/bin/sv_services start

l You cannot install both 64-bit ServerView agents for Linux and ServerView Operations Manager on the same server. During installation of Operations Manager, the system checks whether the ServerView agents for Linux are installed on the server. If so, the installation is aborted.

l To operate ServerView Operations Manager properly, a definition of the localhost line in /etc/hosts is required. Do not delete the definition of the localhost line.

l Edit/addition/deletion of ServerView-related files may give

influences on operations. Make sure not to do any other operations than the ones explained in this documentation.

(52)

l For Red Hat 7.0, it is mandatory to install the necessary ServerView Operations Manager prerequisites to avoid package

inconsistencies. Therefore the necessary prerequisites will be checked before package installation starts. If there are missing prerequisites a warning message is given, e.g. Before

installation please install package: libgcc.i686. The installation is aborted.

l For Red Hat 7.0, compat-libstdc++-33 library is installed

automatically during ServerView Operations Manager installation. But compat-libstdc++-33 library will not be uninstalled, when ServerView Operations Manager is uninstalled.

3.8.1 Language settings

You can set the language for the Operations Manager. Therefore you have the following possibilities:

l Calling up the script-based installation with the option -l | --lang. l If you call up the script without the language option and without the -q

option, then a message is displayed for querying the language.

3.8.2 Administrative user "svuser" in OpenDJ directory service

This section is only relevant if the OpenDJ directory service is used, which is the default for ServerView Operations Manager on Linux. The administrative user svuser is created in the OpenDJ database during installation of ServerView Operations Manager.

In previous versions it was always installed with the default password admin, but as of ServerView Operations Manager version 5.50 you may specify the password for user svuser during a dialog-based installation. You may change the password at any time by executing the command ChangeComputerDetails.sh.

(53)

3.8.3 Installation

Installation is performed with the install.sh script.

For RHEL7 it is mandatory to install the necessary ServerView Operations Manager prerequisites to avoid package inconsistencies. Therefore the necessary prerequisites will be checked before package installation starts. If there are missing prerequisites a warning message is given, e.g. Before installation please install package:

libgcc.i686. The installation is aborted.

Proceed as follows:

1. Place the ServerView Suite DVD 2 in the drive. 2. Open a terminal and switch to the mounted directory. 3. Switch to the directory:

SVSSoftware – Software – ServerView – Linux – ServerView_S2 4. Start the installation with the following command:

./install.sh <option>

(54)

If you do not specify an option, the complete Operations Manager software will be installed by default.

For <option> you can specify: -OM

Only Operations Manager is installed. -UM

Operations Manager and the Update Manager (as of version 4.91) are installed.

-EM

Only Event Manager is installed. -l | --lang [en | ja]

You choose the language for the installation (English, or Japanese). --base

Installs the ServerViewBase package. Use this option if you want to install the ServerView database on a remote database server, see"ServerView database on a remote database server" on page 82.

--remotedbserver | --RDBS

Installs the packages ServerViewPostgresql and ServerViewDB. Use this option if you want to install the ServerView database on a remote database server, see"ServerView database on a remote database server" on page 82. -q | --quiet

Starts a silent installation. -f | --force

Forces an installation.

If this option is set, the installation will continue even if one of the individual packages fails to install. Normally the installation would abort. This option should be used with caution.

-i | --installdir <directory>

(55)

-v | --verbose| --debug

Writes additional information to the log file during the installation. --snmp-community <community>

By default the SNMP community is set to public. If it is different, you can specify the relevant community here.

--ipaddr <IP_address>

By default the first IP address found is used as local IP address for the central management station. If several IP addresses are available for the central management station you may specify another valid one.

--ipchangecheck [yes|no]

By default the ServerListService service checks whether the IP address of the central management station has changed. You can deactivate this function by specifying no. You must specify this value if you specified an IP address different from the default IP address.

--chgtrap [yes|no]

Change settings for connectivity changed notification during an upgrade installation.To change it for all servers to enabled, specify yes.

--fqhostname <hostname>

Fully qualified name of the server. Normally the name is extended to include the domain name. Depending on the network configuration, you can also specify just the server name without the domain name.

If you cannot start the script, invoke it with /bin/bash install.sh. You can specify further parameters for directory server, see"Changing configuration parameters" on page 69.

You close the license display by entering q and then confirming with yes.

If you did not specify the language as argument, the following dialog will be displayed:

Which language?

Please enter en (for English) or ja (for Japanese): Enter the relevant language.

(56)

With a non-silent installation the following dialog is displayed unless the options --fqhostname or –ipaddr were specified:

Fully-qualified hostname: xxx.yyy.zzz (or sometimes only xxx)

ok? (yes|no):

IP address:<IP address> ok? (yes|no):

The fully qualified name of the server and the IP address are determined automatically.

The following dialog is only displayed if you use the directory service OpenDJ (default).

You must specify password for opendj account ‘svuser’. Echo is off during password input.

Password:

Please repeat password:

Provide the password that you want to give to the administrative user svuser for the OpenDJ directory service. Make sure you remember it, as you might need it later on for administration of OpenDJ.

The password for svuser must not be an empty string.

How to change the parameters after the installation is described in"Changing configuration parameters" on page 69.

3.8.4 Parameters for directory service

ServerView Operations Manager makes use of a directory service, which stores information for authorization.

By default, Operations Manager installs its own directory service, OpenDJ. Alternatively you may use your own directory service. Alternatively the use of Microsoft Active Directory Service is supported.

(57)

Installation via the install.sh script

Two options are available: Either invoke a dialog or specify all parameters in command line.

Invoking a dialog

The dialog is not displayed by default. It is invoked by specifying an option in the command line.

install.sh -d|--ds-dialog

This starts the dialog for you to enter parameters for the directory service. The dialog will be as follows:

Specify parameters for directory service: Currently only Active Directory is supported). Host?:

Port?:

Use a LDAP backup server (yes|no)?:

If you answer with yes, the following parameter is displayed: LDAP backup server?:

SSL (yes|no; recommended: yes)?: Base DN?:

User Search Base (e.g. CN=Users)?:

User Search Filter (e.g. sAMAccountName=%u)?: User?:

Password?:

Do you want to configure a warning for the case of a user's password expiry? (yes|no):

Answering with "yes" invokes the following dialog which allows you to enter the parameters for the LDAP Password Policy Enforcement (LPPE):

(58)

Configuring the first three of the following parameters enables the LPPE, which is disabled by default. The fourth parameter is optional. LPPE handles a variety of login exceptions which would otherwise prevent user authentication. For more information see the manual "User Management in ServerView".

Domain Distinguished Name (Example: dc=example,dc=com)

Number of days a password is valid (e.g.: 90)?: Number of days a user is warned before the password expiry (e.g.: 30)?:

Do you want to specify an URL to which the user will be redirected in order to change the password? (yes|no)?:

Answering with "yes",displays the following prompt:

URL to which the user will be redirected in orderto change the password?:

For each of the above parameters you must confirm your input as follows (example):

Host?: xxxxx

Host specified: xxxxx , ok? (yes|no): no Host?: xxxxxy

Host specified: xxxxxy, ok? (yes|no): yes Then the next parameter will be displayed.

Command line interface

You can specify the following parameters via the command line interface: install.sh --ds-host <hostname>

(59)

--ds-user-searchfilter <user search filter> --ds-domain <Domain Distinguished Name> --ds-val-days <days>

--ds-warn-days <days> --ds-pw-url <URL> --ds-host <hostname>

Fully-qualified name of the server on which the directory service is

running.The fully qualified name is an unambiguous name which specifies the system in the network. It is important that this name can be always properly resolved! This can occur by use of an DNS or NIS server, or by appropriate entries in the hosts file of the central management station. If you are not sure whether you can provide for a proper name resolution, you can issue the system's IP address here.

--ds-port <port>

Port number used for access to the directory service. By default, port 389 is used for LDAP and port 636 is used for LDAPS (i.e. LDAP with SSL).

--ds-backup <yes|no>

You can specify if a backup server for LDAP is used (yes) or not (no). If you answer with yes, the following parameter can be set:

--ds-backup-host <backup host name>

Fully-qualified server name on which a backup for the directory service is running.

--ds-ssl <yes | no>

yes is enabled by default to protect the data transfer with SSL encryption. It is recommended that you always protect the connection to the directory service, as the user passwords transferred via this connection are not separately encrypted. Bear in mind, however, that Microsoft Active Directory does not offer SSL encryption as standard; a certificate must be installed on the Windows server system for this purpose. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory").

(60)

--ds-basedn <dn>

Base directory for the ServerView authorization data, e.g.

OU=application,DC=fujitsu,DC=com. You can specify any directory in the Active Directory here. The Operations Manager setup procedure generates an LDIF file for importing the authorization data, which you must then import after the Operations Manager installation. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory"). --ds-user <username>

User ID for read access to the data. The user ID should only have basic read rights. This password is stored in a text file so only a user with simple read access should be chosen. The user ID should be specified in the notation USERNAME@DOMAIN, as displayed in the Active Directory in the user’s account settings under User logon name.

--ds-password <password> Password for read access. --ds-user-searchbase <searchbase>

Starting point for the user search in the directory server e.g. CN=Users,DC=fujitsu,DC=com.

--ds-user-searchfilter <user search filter>

Filter for user search, e.g. sAMAccountName=%u. --ds-domain <Domain Distinguished Name>

Base directory for LPPE settings e.g. dc=example,dc=com --ds-val-days <days>

Number of days a password is valid --ds-warn-days <days>

Number of days a user is warned before the password expires. --ds-pw-url <URL>

(61)

Parameters in the configuration file

The file /etc/fujitsu/ServerViewSuite/ServerView/global.conf contains parameters for the configuration of the active directory service. Please do not change these parameters for the directory service manually. You may specify them during installation/upgrade as parameters or dialog to the script install.sh. You may change them any time by calling the script ChangeComputerDetails.sh.

COM_DS_SERVER

Directory service type: Active Directory Service or OpenDJ (Value: opendj or ad)

COM_DS_HOST

Fully-qualified name of the server on which the directory service is

running.The fully qualified name is an unambiguous name which specifies the system in the network. It is important that this name can be always properly resolved! This can occur by use of an DNS or NIS server, or by appropriate entries in the hosts file of the central management station. If you are not sure whether you can provide for a proper name resolution, you can issue the system's IP address here.

COM_DS_PORT

Port number used for access to the directory service. By default, port 389 is used for LDAP and port 636 is used for LDAPS (i.e. LDAP with SSL).

COM_DS_SSL

yes is enabled by default to protect the data transfer with SSL encryption. It is recommended that you always protect the connection to the directory service, as the user passwords transferred via this connection are not separately encrypted. Bear in mind, however, that Microsoft Active Directory does not offer SSL encryption as standard; a certificate must be installed on the Windows server system for this purpose. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory").

COM_DS_BASE_DN

Base directory for the ServerView authorization data, e.g.

(62)

Active Directory here. The Operations Manager setup procedure generates an LDIF file for importing the authorization data, which you must then import after the Operations Manager installation. For further details, see "User Management in ServerView" user guide (section "Integrating ServerView user management into Microsoft Active Directory"). COM_DS_USER

User ID for read access to the data. The user ID should only have basic read rights. This password is stored in a text file so only a user with simple read access should be chosen. The user ID should be specified in the notation USERNAME@DOMAIN, as displayed in the Active Directory in the user’s account settings under User logon name.

COM_DS_USER_SEARCHBASE

Starting point for the user search in the directory server e.g. CN=Users,DC=fujitsu,DC=com.

COM_DS_SEARCHFILTER

Filter for user search, e.g. sAMAccountName=%u. COM_DS_DOMAIN

Base directory for LPPE settings, e.g. dc=example,dc=com COM_DS_VAL_DAYS

Number of days a password is valid, e.g. 90. COM_DS_WARN_DAYS

Number of days a user is warned before the password expires, e.g. 30. COM_DS_PW_URL

Optional. URL to which the user will be redirected in order to change the password, e.g. https://www.myurl.com.

3.8.5 Update installation

l Update installation to version 6.10 is only supported as of Operations Manager version 6.00.

(63)

In the case of an upgrade installation, user-specific changes to the PostgreSQL configuration files postgresql.conf and pg_hba.conf, pg_ident.conf are not taken over, therefore you must make these changes again.

The log file of the upgrade process (upgrade.log) is stored in the directory /var/log/fujitsu/ServerViewSuite/ServerView.

How to perform an update installation when using a remote ServerView database is described in"Update installation" on page 84.

Script-based upgrade

The upgrade installation is performed with the install.sh script. Proceed as follows:

1. Place the ServerView Suite DVD 2 in the drive. 2. Open a terminal and switch to the mounted directory.

3. Switch to the directory SVSSoftware – Software – ServerView – Linux – ServerView S2.

4. Start the installation with the following command: ./install.sh <option>

If you do not specify an option, the complete Operations Manager software will be updated by default.

For <option> you can specify, see"Installation" on page 53.

In a non-silent upgrade of a ServerView Operations Manager installation using the OpenDJ directory service, you will be asked whether you want to change the password for the administrative user svuser in OpenDJ. If you agree, you will be asked for the old password for svuser. If you specify this correctly you will be asked for the new password.

When upgrading from a version previous to SVOM 6.10 you are always requested to specify the password for svuser.

During a non-silent upgrade from ServerView Operations Manager versions prior to V6.10, you will have to provide a password for the OpenDJ user svuser. You will also need to specify the password used in the prior version, default was admin.

The password for svuser must not be an empty string.

(64)

3.8.6 Installed Operations Manager packages

The installable packages are located on the ServerView Suite DVD 2 in the directory SVSSoftware/RPMS. The installation installs the following rpm packages:

ServerViewBase

Configuration files for Operations Manager and the Operations Managerspecific Web server instance.

ServerViewPostgresql

Package for PostgreSQL database server. Operations Manager version 4.71 and later come with the separate PostgreSQL database server.

The ServerViewPostgresql package sets up a user called postgpls for PostgreSQL. The database processes run under this user, who is also the owner of the files from ServerViewPostgresql. This user needs super user access. The PostgreSQL database server set up via ServerViewPostgresql uses TCP/IP port 9212.

ServerViewDB

Package for the ServerView database. ServerViewJBoss

Packages for the JBoss Web server. ServerViewJBossCommon

Package with utilities for the directory services OpenDJ and Active Directory. ServerViewCommon

Libraries and files used by Operations Manager and Event Manager. ServerView_S2

Package for installation of Operations Manager (without Update Manager and Event Manager).

ServerViewUpdateManager

ServerView Operations Manager V7.02