ServerView Operations Manager- Installation under...

Installation Guide - English

FUJITSU Software ServerView Suite

ServerView Operations Manager V7.20Installing ServerView Operations Manager Software under Linux (OperationsManager, Update Manager, Event Manager)

Edition February 2018

Comments… Suggestions… Corrections…The User Documentation Department would like to know your opinion of this manual. Yourfeedback helps us optimize our documentation to suit your individual needs.

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

Certified documentation according to DIN EN ISO 9001:2008To ensure a consistently high quality standard and user-friendliness, this documentation wascreated to meet the regulations of a quality management system which complies with therequirements of the standard DIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-Dokumentation mbH

www.cognitas.de

Copyright and trademarksCopyright 1998 - 2016 FUJITSU LIMITED

All rights reserved.

Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

Apache Tomcat, Tomcat, Apache, the Apache feather, and the Apache Tomcat project logo aretrademarks of the Apache Software Foundation.

mailto:[email protected]

http://www.cognitas.de/

Contents

1 Introduction 6

1.1 Target groups and objectives 7

1.2 Technical requirements 7

1.2.1 Last-minute changes/corrections 71.2.2 Management console 71.2.3 Central management station (CMS) 8

1.3 ServerView database 8

1.4 Operating-System-Dependent packages 9

1.5 Changes since the previous version 9

1.6 ServerView Suite link collection 10

1.7 Documentation for the ServerView Suite 11

1.8 Notational conventions 12

1.9 Product names - conventions 13

2 PRIMERGY server management 17

2.1 Architecture 17

2.2 Installation on the central management station 20

2.3 Installation on the managed servers 21

3 Installing ServerView Operations Manager 22

3.1 ServerView Operations Manager components 22

3.2 Tomcat web server 23

3.2.1 Calling and ports used 253.2.2 Role-based user administration 263.2.3 Managing certificates 26

3.3 Web browser 26

3.4 Changes on the system 27

3.5 Requirements 27

3.5.1 Management station 273.5.2 Management console 46

3.6 Rights 47

3.7 Installation check list 48

3.8 Installing the Operations Manager software 51

Installation under Linux 3

Inhalt

3.8.1 Language settings 523.8.2 Administrative user "svuser" in ApacheDS directory service 523.8.3 Cipher suite settings 523.8.4 Installation 543.8.5 Parameters for directory service 623.8.6 Update installation 683.8.7 Installed Operations Manager packages 69

3.9 Available services for operating Operations Manager 70

3.10 Using SNMPv3 with ServerView Operations Manager 72

3.11 Uninstalling the Operations Manager software 73

3.12 Changing configuration parameters 74

3.13 Collecting diagnosis data 76

3.14 Troubleshooting 76

3.14.1 Removing faulty/stuck packages 763.14.2 Purging the system 773.14.3 PostgreSQL server does not start 783.14.4 ServerView Operations Manager cannot connect to the database server 793.14.5 System with active PAM configuration 793.14.6 Tomcat does not work correctly 79

4 ServerView database 81

4.1 Configuration files 81

4.2 Connection to the ServerView database is interrupted 82

4.3 Sample configuration for pgAdmin3 82

4.4 Administering the ServerView database 83

4.5 Backing up the ServerView database 84

4.6 Restoring the ServerView database 84

4.7 Exporting/Importing the ServerView database 85

4.8 ServerView database on a remote database server 85

4.8.1 Installation 864.8.2 Update installation 874.8.3 Uninstallation 874.8.4 ServerView database backups 874.8.5 Switching the database server 88

4.9 Error diagnostic 88

4.9.1 unixODBC Manager 884.9.2 Error during installation/uninstallation 884.9.3 Uninstalling the ServerView database 89


Inhalt

4.9.4 System is slowing down 894.9.5 Checking the status of PostgreSQL 894.9.6 Starting and stopping PostgreSQL 904.9.7 Restarting Operations Manager 90

4.10 Changing the load distribution 91

5 Fujitsu Technology Solutions Software License Agreement for End User 93


1 IntroductionServerView Operations Manager (Operations Manager for short) is a free servermanagement module of the Fujitsu ServerView Suite. It is used for central administrationof industry-standard servers which run the operating systems Windows and Linux (SUSEand Red Hat) or which serve as hosts for virtual machines (VMs) that use the hypervisorsVMware ESXi or Hyper-V.

The standardized management of all servers occurs via one or more central managementstations, which you can access from any workstation in the network that has a popularweb browser and the Java Runtime Environment.

Operations Manager controls the individual systems, including critical hardwarecomponents such as processors, RAM, hard disks, fans and power supply. It monitors andcontrols the power consumption, analyzes the performance and utilization data andupdates the server configuration.

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

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

l Role-Based Access Control (RBAC)

l Single Sign-On (SSO) based on a Centralized Authentication Service (CAS)

With RBAC you can tailor your security concept to the organizational structure of yourcompany by assigning a task-oriented authorization profile to each role.

SSO means that you only need to authenticate yourself once. Once you have done thissuccessfully, you are given access to all ServerView components without having to sign onto any of them again.

Server management with Operations Manager offers important benefits to operators of acomprehensive 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 easilyadjusted 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


1.1 Target groups and objectives

components and their resources

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

1.1 Target groups and objectivesThis manual is intended for system administrators, network administrators and servicetechnicians that have a basic knowledge of hardware and software. The manualdocuments the requirements for the use of Operations Manager that are specific to theoperating system and describes the installation of the products ServerView OperationsManager, ServerView Update Manager, and ServerView Event Manager.

1.2 Technical requirements

1.2.1 Last-minute changes/corrections

Any last-minute changes/corrections of the technical requirements can be found in theReadme 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 ServerView Software Products in the Welcome dialog. In theweb browser window select ServerView- Operations Manager - Info.

1.2.2 Management console

l Standard PC, LAN with http access

l Microsoft Windows with Internet Explorer 10 / 11 or Mozilla Firefox 16 / 17 or higher.

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

l Java Runtime Environment (JRE) V1.8.x


1.3 ServerView database

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)

Software

l SUSE (SLES 11): SP3 and SP4

l Red Hat Enterprise Linux 6.6/6.7

l Red Hat Enterprise Linux 7.1/7.2

Database (local and remote)

l PostgreSQL 9.2 (contained in the ServerView package)

Java Runtime Environment

l Java Runtime Environment (JRE) V1.8.x

1.3 ServerView databaseOperations Manager uses an SQL database. This database is a prerequisite for theOperations Manager software. PostgreSQL is used as the database management system.

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

The installation software contains the PostgreSQL database management system. ThisPostgreSQL is automatically installed when you install the Operations Manager software.This does not affect the operation of an already installed PostgreSQL databasemanagement system. For PostgreSQL administration you can use pgAdmin3 (only forLinux), which you can download from http://www.pgadmin.org. Please use a version 1.8.x.

For further information on the ServerView database under Linux, see "ServerViewdatabase" on page 81.


http://www.pgadmin.org/

1.4 Operating-System-Dependent packages

1.4 Operating-System-Dependent packagesDepending on the installed operating system, you must install additional packages for thevarious ServerView components (Operations Manager and ServerView RAID Manager).

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

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

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

SLES 11

With SUSE SLES 11, the easiest way to subsequently install the required rpm packages isvia the YaST control center by selecting Software – Install or delete software. YaST alsoresolves 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 byAdd/Remove Software functionality available in Gnome Tool bar (Red Hat 5 in entryApplication, Red Hat 6 in entry System - Administration). These tools detect themselveswhen a package has dependencies on other packages which are not yet installed. Themissing packages are then listed and you can confirm whether you want to have theseinstalled 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.

1.5 Changes since the previous versionThis edition of the manual applies to ServerView Operations Manager as of V7.20 andreplaces the online manual ServerView Operations Manager V7.11 - Installing ServerViewOperations Manager Software under Linux", edition December 2015.

The manual features the following changes and enhancements:

l The technical requirements has been updated, see "Technical requirements" on page 7.

l The ServerView Deployment Manager is no longer supported.

l As of version 7.10, ServerView Operations Manger supports SNMPv3. Therefore thesection "Using SNMPv3 with ServerView Operations Manager" on page 72 has been


1.6 ServerView Suite link collection

updated. For further information, see the "Usage of SNMPv3 with ServerView Suiteproducts" overview.

l Support of automatic installation of prerequisites for supported Linux distributions,see "Installation" on page 54.

l Cipher suites and SSL protocols used by ServerView Application Server can beconfigured during the ServerView Operations Manager installation, see "Cipher suitesettings" on page 52.

l With unified Role Based Access Control (uRBAC), you can configure an additionalActive Directory server (see "Installation" on page 54 and "Parameters for directoryservice" on page 62).

1.6 ServerView Suite link collectionVia the ServerView Suite link collection, Fujitsu provides you with numerous downloadsand further information on the ServerView Suite and PRIMERGY servers.

For ServerView Suite, links are offered on the following topics:

l Forum

l Service Desk

l Manuals

l Product information

l Security information

l Software downloads

l Training

The downloads include the following:

o Current software statuses for the ServerView Suite as well as additional Readmefiles.

o Information files and update sets for system software components (BIOS,firmware, drivers, ServerView Agents and ServerView Update Agents) forupdating the PRIMERGY servers via ServerView Update Manager or for locallyupdating 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 web server.

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

l Service Desk

l Manuals


1.7 Documentation for the ServerView Suite

l Product information

l Spare parts catalogue

Access to the ServerView Suite 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 the menu bar.

2. Via the start page of the online documentation for the ServerView Suite on the Fujitsumanual server.

You access the start page of the online documentation via the followinglink:

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.

3. Via the ServerView Suite DVD 2.

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

l On the menu bar select Links.

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

1.7 Documentation for the ServerView SuiteThe documentation can be downloaded free of charge from the Internet. You will find theonline documentation at http://manuals.ts.fujitsu.com under the link x86 Servers.

For an overview of the documentation to be found under ServerView Suite as well as thefiling structure, see the ServerView Suite sitemap (ServerView Suite – ServerView SuiteSitemap).


http://manuals.ts.fujitsu.com/

http://manuals.ts.fujitsu.com/

1.8 Notational conventions

1.8 Notational conventionsThe following notational conventions are used in this manual:

Notationalconventions

Indicates

Indicates various types of risks, 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, forexample file names and paths.

monospacesemibold

Indicates statements that are to be entered usingthe keyboard.

blue continuoustext

Indicates a link to a related topic.

purple continuoustext

Indicates a link to a location you have alreadyvisited.

<abc> Indicates variables which must be replaced withreal values.

[abc] Indicates options that can be specified (syntax).

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

Screenshots

The screenshots are to some degree system-dependent and consequently will notnecessarily match the output on your system in all the details. The menus and theircommands can also contain system-dependent differences.


1.9 Product names - conventions

1.9 Product names - conventionsIn the document, product names used in the text are abbreviated as follows:

Windows Server 2016

Windows Server 2012 and 2012 R2



Windows Server 2008 and 2008 R2



Linux

Virtualization software



Component names


2.1 Architecture

2 PRIMERGY server management

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


2.1 Architecture

Management console

A browser-based console allows you to manage the servers and displaythe 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 withdistribution

The Java Runtime Environment must also be installed.

Central management station (CMS)

On the central management station the ServerView Operations Manageris installed. The optional components of the ServerView Suite, such asVirtual IO-Manager, are also installed on the central managementstation and integrated in Operations Manager.

The central management station (and thus the ServerView OperationsManager with its components) may also run on a Windows or Linuxvirtual machine (VM).

The global user management of the ServerView Suite and of the iRMCeach centrally stores users for all Central Management Stations (CMS) /iRMC in the directory of an LDAP directory service. This enables you tomanage the users on a central server. The users can therefore be used byall the CMS and iRMC that are connected to this server in the network.

The ServerView Suite currently supports the following directory services:

l ApacheDSl Microsoft Active Directory


2.1 Architecture

During the installation of ServerView Operations Manager you have theoption to choose ServerView’s internal directory service (ApacheDS). Forfurther 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 11).

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

l SQL Server 2014 Express under Windows Serverl PostgreSQL under Linux

However, other Microsoft SQL Server databases can be used underWindows.

The Java Runtime Environment is required on the central managementstation.

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

l Installing ServerView Operations Manager Software under Windowsl Installing ServerView Operations Manager Software under Linux

Managed servers

On the managed servers, ServerView Agents, ServerView CIM Providers, orServerView Agentless Service should be installed, which supply theinformation to the central management station. ServerView RAIDManager and ServerView Update Agent should be also installed on themanaged servers.

The installation of ServerView Agents on virtual machines (VMs) is notreleased.

l The ServerView Agents are available for Windows, Linux, and CitrixXenServer.

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

ServerView Operations Manager currently only supports ServerViewCIM 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

l ServerView CIM Providers for Windows, Linux, and VMware ESXi


2.2 Installation on the central management station

2.2 Installation on the central management stationYou have to install Operations Manager (incl. ServerView Update Manager and ServerViewEvent Manager) on a management station and thus of monitoring the PRIMERGY serversvia PC or notebook with a standard web browser.

You can install the Operations Manager on the following operating systems:

l Windows

l SUSE Linux

l Red Hat Linux.

The Operations Manager software is supplied on the ServerView Suite DVD 2.

The installation under Linux is script-based and involves the installation of OperationsManager, Update Manager, and Event Manager. The installation is described in chapter"Installing ServerView Operations Manager" on page 22


2.3 Installation on the managed servers

2.3 Installation on the managed serversThe following components must be installed on the managed servers. These are operating-system-specific programs which supply information to the management station, whichsupplies information to the central management station:

l ServerView Agents, CIM Providers, or ServerView Agentless Service

The ServerView Agents are available for Windows, Linux, and Citrix XENServer. CIMProviders are available for Windows, Linux, and VMware ESXi. The installation isdescribed in the "ServerView Agents for Windows", "ServerView Agents for Linux","ServerView CIM Providers for Windows, Linux, and VMware ESXi" installation and userguides.

ServerView Agentless Service is available for Windows and Linux. The installation isdescribed in the "ServerView Agentless Management" overview.

The ServerView System Monitor is installed automatically (via the ServerView Agentsinstallation) and allows you to monitor and check some server information locally onthe server. A detailed description can be found in the "ServerView System Monitor" userguide.

l ServerView Update Agent

To keep the managed servers up-to-date by Update Management functions theServerView Update Agent must be installed on the managed servers. How to do this isdescribed in the "ServerView Update Management" user guide.

Additional installation on the management station

ServerView RAID ManagerServerView RAID Manager offers standardized administration and management ofhard disks for PRIMERGY servers.

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

The installation is described in the "RAID Management" user guide.


3.1 ServerView Operations Manager components

3 Installing ServerView Operations ManagerThis chapter describes how to install the Operations Manager software on themanagement station under Linux. Installation of the Operations Manager softwareinvolves installing Operations Manager, Event Manager, and Update Manager.

The corresponding software is supplied on the ServerView Suite DVD 2.

3.1 ServerView Operations Manager components

ServerView Operations Manager installationWhen you install ServerView Operations Manager, the following ServerView componentsare also automatically installed:

ServerView Configuration ManagerWith ServerView Configuration Manager, you can make system-dependentconfigurations on a managed server. (Only supported for servers on which theServerView Agents are installed.)

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

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

ServerView Performance ManagerWith Performance Manager you can monitor the performance of specific servercomponents. Performance Manager works on the basis of rules. The centrally createdrules can be executed on any number of servers.

ServerView Threshold ManagerWith Threshold Manager you can monitor one or more managed PRIMERGY servers andany virtual machines running on them centrally from the management station on thebasis of threshold values.

ServerView Remote Management FrontendServerView Remote Management Frontend provides a web-based work environment forthe remote management of PRIMERGY servers.


3.2 Tomcat web server

ServerView Update Manager installationWhen you install Update Manager, the following ServerView Operations Managercomponents are also installed:

Update ManagerWith Update Manager you can install and update software across an entire domainvia a central management station.

Repository ManagerWith Repository Manager you can manage the update repository.

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

ConfigurationWith Configuration you can set global parameters for Update Manager.

ServerView Event Manager installationWhen you install Event Manager, the following ServerView Operations Managercomponents are also installed:

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

Alarm ConfigurationThe Alarm Configuration component lets you define settings for alarm handling. Youcan define alarm rules, filter rules and general settings.

3.2 Tomcat web serverThe web server used is Tomcat. The necessary files for Tomcat are automatically installedwhen ServerView Operations Manager is installed. Tomcat is configured as a standaloneservice ServerView ApplicationService.

You can start and stop the service. Use the following command:

/etc/init.d/sv_tomee start|stop


You can enable or disable restarting Tomcat once a month. Disable is set by default. If youwant to enable restarting Tomcat monthly, you should call ChangeComputerDetails.shcommand.

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

If you want to enable restarting Tomcat 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 Tomcat once a month?

Automatic deletion of Tomcat access logs

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

Tomcat includes automatic deletion. In the directory <installation_path>/tomee/svconf thesv-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. Thedefault is a list with the single entry "localhost_access_log.".

<ns0:testInterval>12:00</ns0:testInterval>Test interval, measured in minutes. The test interval can range between 1 minute and24 hours. The behavior of the automated file deletion depends on the specified value:

Number [1...1439]File checking begins when Tomcat starts up, and is repeated at the specified timeinterval.

Time [hh:mm]The test interval is 24 hours and the file checking occurs every day at the specifiedtime. (The values for hh range from 00 till 23.) The default is 12:00, i.e. files arechecked every day at noon.

<ns0:maxAge>10080</ns0:maxAge>Maximum age of a log file, measured in minutes. Any file matching an entry in thefileNamePrefix 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. threedays, 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 thanV4.92 are automatically redirected to port3170.)

3170 https (The port must be unlocked in thefirewall.) TLS v1.1, TLS v1.2, andSSLv2Hello are supported.

3171 Update Management (The port must beunlocked in the firewall to allow UpdateManagement.)

3172 Remote Connector Service (ServerConfiguration Manager, Power Monitor,etc.) (The port must be unlocked in thefirewall.)

3173 ServerView RAID Manager

1473 non-SSL port of ServerView’s directoryservice (ApacheDS)

1474 LDAPS, if ApacheDS is configured asdirectory service.

9212 PostgreSQL database server (only forLinux)

9363 used by the Operations Manager to contactXEN daemons

16509, 16514 used by the KVM service

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

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

Port Used for

80 Citrix

135 Hyper-V


3.3 Web browser

Port Used for

161 SNMP

443 VMware

623 BMC (iRMC)

3172 ServerView Remote Connector

5988 VMware

5989 VMware

9363 XEN (up to SLES 11)

16509 KVM, XEN (as of SLES 12)

16514 KVM, XEN (as of SLES 12)

3.2.2 Role-based user administration

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

3.2.3 Managing certificates

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

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

3.3 Web browserA web browser is required to display the data. This means that the data can betransmitted 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 followingsettings 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 be usedfor the host on which the web server is running.


3.4 Changes on the system

3.4 Changes on the systemServerView Operations Manager creates a user svuser and a group svgroup. Almost allprocesses are started under this ID.

By default, Operations Manager installs its own directory service, ApacheDS. Youcannot change the password via ApacheDS.

You can only change it locally by using the script ChangeComputerDetails.sh, see"Changing configuration parameters" on page 74.

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 ofthe ODBC Manager.

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

disableAuthorization yes

ignoreAuthFailure yes

3.5 RequirementsOn 64-bit systems, the distribution includes many packages for both architectures,32-bit and 64-bit. 32-bit packages are distinguished differently on the differentplatforms. On SLES systems the package name has the file extension 32bit. OnRHEL systems the architecture part of the package takes the value i386, i586 ori686.

3.5.1 Management station

l Tomcat web server

The Tomcat web server is installed when you install the ServerView OperationsManager software. The corresponding service is automatically started when you startOperations Manager.

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


3.5 Requirements

l Network configuration

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

Example111.22.33.44 myserver.mydomain

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

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

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

o the central management station itselfo any monitoring stationo the managed nodeo 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 Java Runtime Environment package from the ServerView Suite DVD2:

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 – 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, theJava plug-in must be activated and depending on the platform 64-bit jre mustbe installed.


3.5 Requirements

l SELinux must be deactivated on distributions on which it is not supported byServerView 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 requiresuperuser 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 Yaston SLES platforms and Add/Remove Software in menu bar as well as YUM on RHELplatforms. These platform managers implicitly resolve all dependencies. How toconfigure YUM, see "Configuring YUM" on page 44.

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 thearchitecture of the package. Please pay attention to this.

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

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


3.5 Requirements

RHEL 5.11 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 openldap-clients.i686

l openssl

l unixODBC

l unixODBC-libs

l zlib

l Prerequisites for special functionality:

DeskView Interface: curl

RHEL/KVM monitoring: libvirt


3.5 Requirements

RHEL 5.11 64-bit:

l compat-libstdc++-33.i386

l curl.i386

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 openldap-clients.x86_64

l openssl.i686

l perl-Net-SSLeay

l perl-Socket-SSL

l unixODBC.i386

l unixODBC-libs.i386

l zlib.i386


DeskView Interface: curl.i386

RHEL/KVM monitoring: libvirt.x86_64


3.5 Requirements

RHEL 6.4 32-bit:


l cyrus-sasl-lib

l glibc

l gzip

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 perl-Net-SSLeay

l perl-Socket-SSL

l unixODBC

l zlib



RHEL/KVM monitoring: libvirt-client


3.5 Requirements

RHEL 6.4 64-bit:


l cyrus-sasl-lib.i686

l glibc.i686

l gzip.x86_64


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 perl-Net-SSLeay

l perl-Socket-SSL

l unixODBC.i686

l zlib.i686


DeskView Interface: curl.x86_64

RHEL/KVM monitoring: libvirt-client.x86_64


3.5 Requirements

RHEL 6.5 32-bit:


l cyrus-sasl-lib

l glibc

l gzip

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-util

l openldap


l openssl

l perl-Net-SSLeay

l perl-Socket-SSL

l policycoreutils-python

l unixODBC

l zlib





3.5 Requirements

RHEL 6.5 64-bit:



l glibc.i686

l gzip.x86_64


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-util.i686

l openldap.i686


l openssl.i686

l perl-Net-SSLeay

l perl-Socket-SSL


l unixODBC.i686

l zlib.i686





3.5 Requirements

RHEL 6.6 32-bit:


l cyrus-sasl-lib

l glibc

l gzip

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-util

l openldap


l openssl

l perl-Net-SSLeay

l perl-Socket-SSL


l unixODBC

l zlib





3.5 Requirements

RHEL 6.6 64-bit:



l glibc.i686

l gzip.x86_64


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-util.i686

l openldap.i686


l openssl.i686

l perl-Net-SSLeay

l perl-Socket-SSL


l unixODBC.i686

l zlib.i686





3.5 Requirements

RHEL 6.7 32-bit:

l glibc

l gzip

l keyutils-libs

l krb5-libs

l libcom_err

l libcurl

l libgcc

l libselinux

l libstdc++

l libtool-ltdl

l libxml2

l ncurses-libs

l net-snmp


l openldap-clients

l openssl-libs

l pcre

l perl-Net-SSLeay

l perl-IO-Socket-SSL.noarch


l unixODBC

l xz-libs

l zlib





3.5 Requirements

RHEL 6.7 64-bit:

l glibc.i686

l gzip.x86_64


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 openssl-libs.i686

l pcre.i686

l perl-Net-SSLeay



l unixODBC.i686

l xz-libs.i686

l zlib.i686





3.5 Requirements

RHEL 7.0/RHEL7.1 64-bit:

l glibc.i686

l gzip.x86_64


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 openssl-libs.i686

l pcre.i686

l perl-Net-SSLeay



l unixODBC.i686

l xz-libs.i686

l zlib.i686




Visual popups for Alarm Manager: xorg-x11-apps


3.5 Requirements

SLES11 SP2 32-bit:

l cyrus-sasl

l glibc

l gzip

l keyutils-libs

l krb5

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 openldap2-client

l perl-Net-SSLeay

l perl-Socket-SSL

l termcap

l unixODBC

l zlib





3.5 Requirements

SLES11 SP2 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 libgcc46-32bit

l libidn-32bit

l libldap-2_4-2-32bit

l libltdl7-32bit

l libopenssl0_9_8-32bit

l libstdc++33-32bit

l libstdc++46-32bit

l libxml2-32bit

l net-snmp

l openldap2-client

l perl-Net-SSLeay

l perl-Socket-SSL

l termcap-32bit

l unixODBC

l unixODBC-32bit

l zlib-32bit





3.5 Requirements

SLES11 SP3 32-bit:

l cyrus-sasl

l glibc

l gzip

l keyutils-libs

l krb5

l libcom_err2

l libcurl4

l libgcc_s1

l libidn

l libldap-2_4-2

l libltdl7

l libopenssl0_9_8

l libstdc++33

l libstdc++6

l libxml2

l net-snmp

l openldap2-client

l perl-Net-SSLeay

l perl-Socket-SSL

l termcap

l unixODBC

l zlib





3.5 Requirements

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 openldap2-client

l perl-Net-SSLeay

l perl-Socket-SSL

l termcap-32bit

l unixODBC

l unixODBC-32bit

l zlib-32bit




l Configuring YUM

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

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

ln -s '/media/RHEL xxx xxx xx' /tmp/instmedia


3.5 Requirements

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

The automatic typing extension of the shell might insert \ before theblanks 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 eachof the repositories in the YUM configuration file, if you want to use it. The mainrepository 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 thefollowing contents.

Example for RHEL5[instserver]

name=RHEL 5.x iso image / directory Server

baseurl=file:///path/to/local/repo

enabled=1

gpgcheck=0

[instvt]

name=RHEL 5.x iso image directory VT

baseurl=file:/tmp/instmedia/VT

enabled=1

gpgcheck=0

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

Example for RHEL6[instserver]

name=RHEL 6.2 iso image Server

baseurl='file:///path/to/local/repo'

enabled=1

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 Requirements

3.5.2 Management console

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 toinstall 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

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.8.0_51>/lib/i386/libnpjp2.solibnpjp2.so

The following passage is on setting up browser plugins for 64-bit systems:


3.6 Rights

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_oji.so exists,remove it.

rpm -ql jre | grep libnpjp2.so

o Set up the link, e.g.

ln -s /usr/java/<jre1.8.0_51>/lib/amd64/libnpjp2.solibnpjp2.so

Web browser (Windows)

l Internet Explorer 10 / 11

l Mozilla Firefox 16 / 17 or higher.

ServerView Operations Manager does not always work properly with MozillaFirefox later than 37 because of Java crashes.

3.6 RightsFor installation and configuration, you must have administrator rights, i.e. you must belogged onto the server as the superuser root.


3.7 Installation check list

3.7 Installation check listWeb browser

No. Checkpoint

Configuration

1 Supportedversion

Supported web browser for Windows is the following:

l Internet Explorer 10 / 11

l Mozilla Firefox 16 / 17 or higher.

Supported web browser for Linux is the following:

l Default web browser released with distribution.

2 Trustedsites

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 browserconfiguration.

4 32-bit/64-bit

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

Table 1: Check list Web browser

Java Runtime Environment (JRE)

No. Check point Configuration

1 Supportedversion

V1.8.x

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

2 32-bit/64-bit You can use the same architecture of JRE as the system OS, i.e. 32-bitversion of JRE on 32-bit Linux, and 64-bit version of JRE on 64-bitLinux.




3 Java Plug-in(only forWindows)

Enable the next-generation Java Plug-in must be checked. This itemis 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 ischecked.

4 Security Configure security settings as follows:

1. Open Java Control Panel.

2. Select Advanced tab.

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

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

5 Symbolic link(only forLinux)

Set up the link for the plug-in to access from Linux by Firefox. Pleasesee "Requirements" on page 27.

Table 2: Check list JRE

OS settings

No. Checkpoint

Configuration

1 host nameresolve

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 followingcommands.

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

l Linux:# traceroute <hostname>.<DNS suffix>

2 Networkports

SVOM uses some network ports. Which ports SVOM requires is describedin "Calling and ports used" on page 25.

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



No. Checkpoint

Configuration

4 SQLinstance(only forWindows)

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 aremote SQL Server.

5 ActiveDirectory

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

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

6 Networkdrive

It is not possible to install SVOM to network drives.

7 TerminalServer(only forWindows)

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

8 /etc/hosts(only forLinux)

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

9 SELinux(only forLinux)

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

Table 3: Check list OS settings

Update Installation


1 Base version Update installation is only possible from version 7.11.04 or newer.

Table 4: Check list update installation


3.8 Installing the Operations Manager software

3.8 Installing the Operations Manager softwareThe Operations Manager software (Operations Manager, Event Manager, and the UpdateManager) 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 furtherinformation, see "ServerView database on a remote database server" on page 85.

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 orupgrade.log) is stored in the directory /var/log/fujitsu/ServerViewSuite/ServerView.

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

l If an newer version of Operations Manager is already installed, you cannotperform a downgrade installation. To downgrade, you must uninstall theexisting 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 Manageron the same server, and if the Operations Manager is installed before the LinuxAgents, the server is not automatically registered to ServerView OperationsManager.

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

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

l Edit/addition/deletion of ServerView-related files may give influences onoperations. Make sure not to do any other operations than the ones explainedin this documentation.

l For Red Hat 6.6, 6.7 and 7.0, compat-libstdc++-33 library is installedautomatically during ServerView Operations Manager installation. Butcompat-libstdc++-33 library will not be uninstalled, when ServerViewOperations Manager is uninstalled.



3.8.1 Language settings

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

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 amessage is displayed for querying the language.

3.8.2 Administrative user "svuser" in ApacheDS directory service

This section is only relevant if the ApacheDS directory service is used, which is thedefault for ServerView Operations Manager on Linux.

The administrative user svuser is created in the ApacheDS database during installation ofServerView Operations Manager.

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

Please note that this user svuser in the directory service ApacheDS is different from theoperating system account svuser created during a new installation of ServerViewOperations Manager.

The password for svuser must not be an empty string.

3.8.3 Cipher suite settings

Cipher suites and SSL protocols used by ServerView Application Server can be configuredduring ServerView Operations Manager installation (see "Installation" on page 54). Thereare three defined configuration sets available:

• Modern (strongest cipher suite set)

• Intermediate

• Old (weakest cipher suite set)

These three cipher suite sets are equivalent to the Modern/Intermediate/Old sets definedin the Mozilla document https://wiki.mozilla.org/Security/Server_Side_TLS. Modern settingsare the most secure. Only the latest SSL protocol version TLSv1.2 is allowed. So it will passvulnerability scannings without errors. The Intermediate configuration set allows TLSv1.2,


https://wiki.mozilla.org/Security/Server_Side_TLS


TLSv1.1 and TLSv1.0. If a client which can be connected to ServerView Operations Managerallows only the SSL protocol version SSLv3, the Old configuration set should be selected.Otherwise a connection cannot be established. This set is the weakest cipher suite set andallows TLSv1.2, TLSv1.1, TLSv1.0, and SSLv3. By default the Intermediate set is configured.

The configuration of the cipher suites and SSL protocols is stored in the <SVOMinstallation directory>/tomee/conf/server.xml configuration file.

After ServerView Operations Manager is installed, you can modify the configuration ofcipher suites and protocols by editing the server.xml configuration file. In the <Connector>section for the port 3170, you can define allowed cipher suites under the ciphers attributeand also specific protocols to use (e.g. SSLv2Hello, TLSv1, TLSv1.1, TLSv1.2) under thesslEnabledProtocols attribute.

You have to restart the /etc/init.d/sv_tomee service after modifying the server.xmlfile.

In the server.xml configuration file, allowed cipher suites are specified in IANAnomenclature, whereas the tables of ciphers for specific cipher suites on the Mozilla pageprovided use OpenSSL cipher designators. However, you will find a cipher namesequivalence table in the Mozilla document, showing the corresponding OpenSSL and IANAcipher names (see link above).

Athttps://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SupportedCipherSuites you will find two tables under Cipher Suites (The SunJSSEProvider), which show you which cipher suites support which Java version. With Java8 are no restrictions in this regard.


https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SupportedCipherSuites

https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SupportedCipherSuites


3.8.4 Installation

Installation is performed with the install.sh script.

Proceed as follows:



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 beinstalled by default.

For <option> you can specify:

-OMOnly Operations Manager (see the note below) is installed.

-UMOperations Manager and Update Manager (as of version 4.91) are installed.

-EMOnly Event Manager is installed.

-l | --lang [en | ja]You choose the language for the installation (English or Japanese).

--baseInstalls the ServerViewBase package. Use this option if you want to install theServerView database on a remote database server, see "ServerView database on aremote database server" on page 85.

--remotedbserver | --RDBSInstalls the packages ServerViewPostgresql and ServerViewDB. Use this option if youwant to install the ServerView database on a remote database server, see "ServerViewdatabase on a remote database server" on page 85.

-q | --quietStarts a silent installation.

-f | --forceForces an installation.



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

-i | --installdir <directory>Specify the directory containing the RPM packages.

Example-i <CD_root>/SVSSoftware/RPMS

-v | --verbose| --debugWrites 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 therelevant community here.

--ipaddr <IP_address>By default the first IP address found is used as local IP address for the centralmanagement station. If several IP addresses are available for the central managementstation you may specify another valid one.

--ipchangecheck [yes|no]By default the ServerListService service checks whether the IP address of the centralmanagement 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 IPaddress.

--chgtrap [yes|no]Change settings for connectivity changed notification during an upgradeinstallation.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 thedomain name. Depending on the network configuration, you can also specify just theserver name without the domain name.

-d|--ds-dialogUser authentication and user authorization are managed within the same "external"directory service (e.g. Active Directory).

-r|--rds-dialogThe "internal" directory service of the ServerView Operations Manager (ApacheDS) isused for managing the role assignments, whereas the "external" directory service(Active Directory) is only accessed for managing user authentication (unified RBACmanagement).

In this case, the directory server ApacheDS is automatically installed when youinstall ServerView Operations Manager.



You can specify further parameters for directory server, see "Changing configurationparameters" on page 74.

If you cannot start the script, invoke it with /bin/bash install.sh.

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

l If you did not specify the language as argument, the following dialog will bedisplayed:

Which language?

Please enter en (for English) or ja (for Japanese):

Enter the relevant language.

l If the detected operating system version is supported, a special dialog allows you toperform manual or automatic installation of requirements. This dialog is displayedafter you specify the language:

Starting prerequisites check...

Detected OS: <OS_version>

Dependencies directory: deps-rules/<os_dir>

Checking installed packages...

Processing main.deps

…

Do you want to run shell to perform manual install of therequired packages? (y/N)

o The following dialog is only displayed if you want to perform a manualinstallation of prerequsites (y (yes)):

Executing shell: /bin/bash

When you exit (using ^D or exit command), theinstallation will continue.

You can find the list of required packages in/tmp/dependencies_list_554

o The following dialog is only displayed if you want to perform an automaticinstallation of prerequsites (N (no), default value ):

If needed, please provide here any special options foryum (leave blank if not needed):

*** WARNING ***



Next, the control is going to be handed over to thesystem specific tool which will install the requiredpackages.

Please make sure all the required resources for thepackage management system are available, i.e., networkconnection is functional, CD/DVD is mounted, etc.

Hit ^C to stop the installation or return to continue.

Processing main.deps

Executing: yum -y install compat-libstdc++-33.i686 cyrus-sasl-lib.i686 glibc.i686 gzip.x86_64 keyutils-libs.i686krb5-libs.i686 libcom_err.i686 libcurl.i686 libgcc.i686libidn.i686 libselinux.i686 libssh2.i686 libstdc++.i686libtool-ltdl.i686 libxml2.i686 ncurses-libs.i686 net-snmp.x86_64 nspr.i686 nss.i686 nss-softokn-freebl.i686nss-util.i686 openldap.i686 openldap-clients.x86_64openssl.i686 perl-Net-SSLeay perl-IO-Socket-SSLpolicycoreutils-python unixODBC.i686 zlib.i686 -- Is thisokay? (Y/n)

The default value is Y (yes).

l Parameters that are determined automatically can be confirmed with the [Enter] key.

l 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 onlyxxx)

ok? (yes|no):

IP address:<IP address>

ok? (yes|no):

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

l After specifying IP address the following dialog is displayed which enables you toselect the cipher suites and SSL protocols used by the ServerView Application Server.

Select cipher suites and SSL protocols used by ServerViewApplication Server. Modern settings are the most secure, butit can happen that older Java versions will not work. Legacysettings should work with the oldest browsers and Javaversions.

Choose security mode:



> Modern (m)

> Intermediate(i)

> Old (o)

Security mode: (m|i|o)?:

Modern is the most secure mode, but it can happen that older Java versions will notwork. Old should work with the oldest web browsers and Java versions. By default theIntermediate set is configured.

l The next dialog enables you to add a provided address to /etc/hosts file.

You must specify an IP address from the following list:

<IP address1>

<IP address2>

<IP address3>

IP address?:<IP address1>

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

According to documentation (chapter 3, page 32) file"/etc/hosts" should contain ip address and hostname binding.

Content of /etc/hosts file:

127.0.0.1 localhost localhost.localdomain localhost4localhost4.localdomain4

::1 localhost localhost.localdomain localhost6localhost6.localdomain6

Is proper entry present in the file? (yes|no)?:no

Do you want to add entry to "/etc/hosts" file (yes|no)?:yes

Entry added.

l The next dialog enables you to choose the type of Directory Service.

ServerView needs a directory server to authenticate user.

Please note: You can use an already existing externaldirectory server from your environment (Active directory) orlocal directory server installed with ServerView (ApacheDS).

Choose type of Directory Service.

>> Local directory server installed with ServerView (ads)

External existing directory server:

> with authorization on remote directory server. RequiresLDIF import there. (ad)



> with authorization on local directory server. No LDIFimport necessary (adr)

Directory Service (ads|ad|adr)?:<directory service>

o The following dialog is only displayed if you use the directory service ApacheDS(Directory Service (ads/ad/adr) ?: ads)/(default) for user authentication and userauthorization.

You must specify password for apacheds 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 forthe ApacheDS directory service. Make sure you remember it, as you might need itlater on for administration of ApacheDS.


o The following dialog is only displayed if you use unified RBAC (Directory Service(ads/ad/adr) ?: adr) - Active Directory Service for user authentication andApacheDS directory service for user authorization.

uRBAC Part 1: configuring the local ApacheDS

You must specify password for apacheds account ‘svuser’.


Password:


Please remember the password. You need it foradministration of apacheds.

uRBAC Part 2:collecting details of the existing DirectoryService.

Specify parameters for directory service used for userauthentication.

Host?:<hostname>|<IP adress>

Host specified: <hostname>, ok? (yes|no):yes

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

SSL specified: yes, ok? (yes|no):yes

Port (often: 636)?:<port>



Port specified: <port>, ok? (yes|no):yes

Domain?: DOMAIN

Domain specified:DOMAIN, ok? (yes|no):yes

Base DN?:DC=DOMAIN,DC=local

Base DN specified: DC=DOMAIN,DC=local,ok?(yes|no):yes

User Search Base (example:CN=Users,DC=my_domain,DC=local)?:CN=Users,DC=DOMAIN,DC=local

User Search Base specified: CN=Users,DC=DOMAIN,DC=local,ok? (yes|no):yes

Group Search Base (press RETURN for default)?:<GROUP_SEARCHBASE>

Group Search Base specified:<GROUP_SEARCHBASE>, ok?(yes|no):

User Search Filter (example:sAMAccountName=%u)?:sAMAccountName=%u

User Search Filter specified: sAMAccountName=%u, ok?(yes|no):yes

User?:<ds_username>

User specified: svadmin, ok? (yes|no):yes


Password:


Starting check on access to "primary" directory service.

Access to the "primary" directory service successful.

Check on access to "primary" directory service finished.

Do you want to configure SECONDARY directory service(yes|no)?:

o The following dialog is only displayed if you want to configure a second ActiveDirectory Service for user authorization (Do you want to configureSECONDARY directory service (yes|no)?:yes).

Specify parameters for SECONDARY directory service.

Host?:<hostname>|<IP adress>

Host specified: <hostname>, ok? (yes|no):

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



Port (often: 636)?: <port>

Port specified:<port>, ok? (yes|no):

Domain?:<DOMAIN>

Domain specified: <DOMAIN>, ok? (yes|no):

Base DN?: <BASE_DN>

Base DN specified: <BASE_DN>, ok? (yes|no):

User Search Base (example: CN=Users,DC=my_domain,DC=local)?: <USER_SEARCHBASE>

User Search Base specified: <USER_SEARCHBASE>,DC=<DOMAIN>,DC=local, ok? (yes|no):

Group Search Base (press RETURN for default)?:<GROUP_SEARCHBASE>

Group Search Base specified:<GROUP_SEARCHBASE>, ok?(yes|no):

User Search Filter (example:sAMAccountName=%u)?:<user_searchfilter>

User Search Filter specified:<user_searchfilter>, ok?(yes|no):

User?:<ds_username>

User specified: <ds_username>, ok? (yes|no):


Password:


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

Do you want to configure a warning for the case of ausers password expiry? (yes|no)

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


If Directory Service check fails, you can choose to correct parameters above. If thecorrect parameters can not be provided or verified, the installation will be proceed butthe ChangeComputerDetails.sh script must be executed later on.



You can change parameters at any time by executing the ChangeComputerDetails.shscript. How to change the parameters with the ChangeComputerDetails.sh script after theinstallation is described in section "Changing configuration parameters" on page 74.

3.8.5 Parameters for directory service

ServerView Operations Manager makes use of a directory service, which stores informationfor user authorization and user authentication.

By default, Operations Manager installs its own directory service, ApacheDS. Alternativelyyou may use your own directory service. Currently only Microsoft Active Directory Service issupported.

In this case, the ServerView User and Security concept provides the following options:

l User authentication and user authorization are managed within the same "external"directory service (Active Directory). For further information see the "User Managementin ServerView" user guide.

l In "unified RBAC management", the “internal” directory service of the ServerViewOperations Manager (ApacheDS) is used for managing the role assignments whereasthe "external" directory service (Active Directory) is only accessed for managing userauthentication. For further information about unified RBAC, see the "User Managementin ServerView" user guide.

During installation of Operations Manager, you can determine which of the abovestrategies will be used in your ServerView user management and specify furtherparameters for the Active Directory service.

Installation via the install.sh script

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

Invoking a dialog

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

install.sh -d|--ds-dialog

User authentication and user authorization are managed within the same "external"directory service (e.g. Active Directory).

install.sh -r|--rds-dialog

The "internal" directory service of the ServerView Operations Manager (ApacheDS) isused for managing the role assignments, whereas the "external" directory service(Active Directory) is only accessed for managing user authentication (unified RBACmanagement).



In this case, the directory server ApacheDS is automatically installed when youinstall ServerView Operations Manager.

In both cases, a dialog starts to enter parameters for the directory service. The dialog willbe as follows.

ServerView needs a directory server to authenticate user.

Please note: You can use an already existing external directoryserver from your environment (Active directory) or localdirectory server installed with ServerView (ApacheDS).

Choose type of Directory Service.

>> Local directory server installed with ServerView (ads)

External existing directory server:

> with authorization on remote directory server. Requires LDIFimport there. (ad)

> with authorization on local directory server. No LDIF importnecessary (adr)

Directory Service (ads|ad|adr)?:

Specify parameters for directory service used for userauthentication:

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)?:

Group Search Base (press RETURN for default)?:

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

User?:

Password?:

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

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



Configuring the first three of the following parameters enables the LPPE, whichis disabled by default. The fourth parameter is optional. LPPE handles avariety of login exceptions which would otherwise prevent user authentication.For further 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 beredirected in order to change the password? (yes|no)?:

Answering with "yes",displays the following prompt:

URL to which the user will be redirected in order to changethe 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 (-- ds for userauthentication and user authorization managed within the same directory service (ActiveDirectory) or --rds for unified RBAC):

install.sh --[r]ds-host <hostname>--[r]ds-port <port> --[r]ds-backup <yes|no>

--[r]ds-backup-host <backup host name>

--[r]ds-ssl <yes|no> --[r]ds-basedn <dn>

--[r]ds-user <username> --[r]ds-password <password>

--[r]ds-user-searchbase <searchbase>

--[r]ds-group-searchbase <searchbase>

--[r]ds-user-searchfilter <user search filter>

--[r]ds-domain <Domain Distinguished Name>

--[r]ds-val-days <days>

--[r]ds-warn-days <days>



--[r]ds-pw-url <URL>

Parameter

--[r]ds-host <hostname>Fully-qualified name of the server on which the directory service is running.The fullyqualified name is an unambiguous name which specifies the system in the network. Itis important that this name can be always properly resolved! This can occur by use ofan DNS or NIS server, or by appropriate entries in the hosts file of the centralmanagement station. If you are not sure whether you can provide for a proper nameresolution, you can issue the system's IP address here.

--[r]ds-port <port>Port number used for access to the directory service. By default, port 389 is used forLDAP and port 636 is used for LDAPS (i.e. LDAP with SSL).

--[r]ds-backup <yes|no>You can specify if a backup server for LDAP is used (yes) or not (no). If you answerwith yes, the following parameter can be set:

--[r]ds-backup-host <backup host name>Fully-qualified server name on which a backup for the directory service is running.

--[r]ds-ssl <yes | no>yes is enabled by default to protect the data transfer with SSL encryption.

The TLS v1.1, TLS v1.2, and SSLv2Hello protocols are supported.

It is recommended that you always protect the connection to the directory service, asthe user passwords transferred via this connection are not separately encrypted. Bearin mind, however, that Microsoft Active Directory does not offer SSL encryption asstandard; a certificate must be installed on the Linux server system for this purpose.

For further information, see section "Managing SSL Certificates on the CMS andmanaged nodes" and "Integrating ServerView user management into Microsoft ActiveDirectory" in the "User Management in ServerView" user guide.

--[r]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 ActiveDirectory here. The Operations Manager setup procedure generates an LDIF file forimporting the authorization data, which in the case of Active Directory you must thenimport manually after the Operations Manager installation. For unified RBAC, usersand roles are imported automatically. For further information, see "User Managementin ServerView" user guide (section "Integrating ServerView user management intoMicrosoft Active Directory").



--[r]ds-user <username>User ID for read access to the data. The user ID should only have basic read rights. Thispassword is stored in a text file so only a user with simple read access should bechosen. The user ID should be specified in the notation USERNAME@DOMAIN, asdisplayed in the Active Directory in the user’s account settings under User logon name.

--[r]ds-password <password>Password for read access to the directory server.

--[r]ds-user-searchbase <searchbase>Starting point for the user search in the directory server e.g.CN=Users,DC=fujitsu,DC=com.

--[r]ds-group-searchbase <searchbase>Starting point for the group search in the directory server e.g.CN=Users,DC=fujitsu,DC=com.

--[r]ds-user-searchfilter <user search filter>Filter for user search, e.g. sAMAccountName=%u.

--[r]ds-domain <Domain Distinguished Name>Base directory for LPPE settings e.g. dc=example,dc=com

--[r]ds-val-days <days>Number of days a password is valid (e.g. 90).

--[r]ds-warn-days <days>Number of days a user is warned before the password expires (e.g. 30).

--[r]ds-pw-url <URL>Optional. URL to which the user will be redirected in order to change the password,e.g. https://www.myurl.com

Parameters in the configuration file

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

The parameter names for the configuration of the second directory service correspond tothe parameter names for the configuration of the active directory service. In addition a 2is attached to the parameter names of the second directory service, e.g. COM_DS_HOST2.

COM_DS_SERVERDirectory service type: Active Directory Service or ApacheDS (Value: apacheds or ad)

COM_DS_HOSTFully-qualified name of the server on which the directory service is running.The fullyqualified 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 ofan DNS or NIS server, or by appropriate entries in the hosts file of the centralmanagement station. If you are not sure whether you can provide for a proper nameresolution, you can issue the system's IP address here.

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

COM_DS_SSLyes is enabled by default to protect the data transfer with SSL encryption.

The TLS v1.1, TLS v1.2, and SSLv2Hello protocols are supported.

It is recommended that you always protect the connection to the directory service, asthe user passwords transferred via this connection are not separately encrypted. Bearin mind, however, that Microsoft Active Directory does not offer SSL encryption asstandard; a certificate must be installed on the Linux server system for this purpose.

For further information, see section "Managing SSL Certificates on the CMS andmanaged nodes" and "Integrating ServerView user management into Microsoft ActiveDirectory" in the "User Management in ServerView" user guide.

COM_DS_BASE_DNBase directory for the ServerView authorization data, e.g.OU=application,DC=fujitsu,DC=com. You can specify any directory in the ActiveDirectory here. The Operations Manager setup procedure generates an LDIF file forimporting the authorization data, which in the case of Active Directory you must thenimport manually after the Operations Manager installation. For unified RBAC, usersand roles are imported automatically. For further information, see "User Managementin ServerView" user guide (section "Integrating ServerView user management intoMicrosoft Active Directory").

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

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

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

COM_DS_SEARCHFILTERFilter for user search, e.g. sAMAccountName=%u.



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

COM_DS_VAL_DAYSNumber of days a password is valid, e.g. 90.

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

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

3.8.6 Update installation

l Update installation is only supported as of Operations Manager version7.11.04.

l Do not stop Postgresql when you execute the update installation. The updateinstallation is not correctly done.

In the case of an upgrade installation, user-specific changes to the PostgreSQLconfiguration 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 isdescribed in "Update installation" on page 87.

Script-based upgrade

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



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 softwarewill be updated by default.

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

In a non-silent upgrade of a ServerView Operations Manager installation using theApacheDS directory service, you will be asked whether you want to change the password



for the administrative user svuser in ApacheDS. If you agree, you will be asked for the oldpassword 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 tospecify 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 ApacheDS user svuser. You will also need tospecify the password used in the prior version, default was admin.


3.8.7 Installed Operations Manager packages

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

ServerViewBaseConfiguration files for Operations Manager and the Operations Manager specific webserver instance.

ServerViewPostgresqlPackage for PostgreSQL database server. Operations Manager version 4.71 and latercome with the separate PostgreSQL database server.

The ServerViewPostgresql package sets up a user called postgpls forPostgreSQL. The database processes run under this user, who is also the ownerof the files from ServerViewPostgresql. This user needs super user access. ThePostgreSQL database server set up via ServerViewPostgresql uses TCP/IP port9212.

ServerViewDBPackage for the ServerView database.

ServerViewTomeePackages for the Tomcat web server.

ServerViewCommonLibraries and files used by Operations Manager and Event Manager.

ServerView_S2Package for installation of Operations Manager (without Update Manager and EventManager).

ServerViewUpdateManagerPackage for installation of Update Managers.

ServerViewEventManagerPackage for installation of Event Manager.


3.9 Available services for operating Operations Manager

ServerViewOperationsManagerVirtual package containing the dependencies to the other packages.

ServerViewConnectorServicePackage for remote connection to Operations Manager.

The packages ServerViewBase, ServerViewPostgresql, ServerViewDB,ServerViewTomee, and ServerViewCommon are always installed. (If only aremote DB is installed, only the packages ServerViewBase, ServerViewPostgresqland ServerViewDB are installed.) By default, the complete Operations Managersoftware including the database management system is installed. The databasemanagement system is installed in the directory/opt/fujitsu/ServerViewSuite/Postgresql by default.

3.9 Available services for operating Operations ManagerThe following services are available for operating Operations Manager:

l /etc/init.d/sv_watchdogd

l /etc/init.d/sv_tomee

l /etc/init.d/sv_downloadd

l /etc/init.d/sv_updated

l /etc/init.d/sv_inventoryd

l /etc/init.d/sv_fwdserver

l /etc/init.d/sv_exportd

l /etc/init.d/sv_archivd

l /etc/init.d/sv_serverlistservice

l /etc/init.d/sv_bmcservice

l /etc/init.d/sv_vme

l /etc/init.d/sv_DBServer

l /etc/init.d/sv_postgresql

l /etc/init.d/srvmagt_scs

Stopping/starting/restarting all services

You can stop, start and restart all services with the following command:

/usr/bin/sv_services stop | start | restart [service]

serviceThe following services are only stopped if additional options are specified:

-withPostgresService /etc/init.d/sv_postgresql


3.9 Available services for operating Operations Manager

-withTomeeService /etc/init.d/sv_tomee

-withSCSService /etc/init.d/srvmagt_scs

Stopping services individually

You stop the ServerView services - in the order listed above - with the following command:

<service> stop

You can check whether all services have been stopped with the following command:

ps ax | grep SV

Services which are still running can be terminated with the kill command (kill -9). Childservices must also be terminated with this command.

Starting services individually<service> start

The services must be started in reverse order (see above list).

Watchdog for services

Each ServerView service, e.g. ServerListService, creates a so called pid file on startup anddeletes it on closure. The watchdog checks the existence of the pid file and, if it exists,checks whether the process is running. If not, it restarts the service.

All services to be monitored are configured in the file/etc/fujitsu/ServerViewSuite/ServerView/sv_watchdogdrc. It is possible to list services thatmay not exist when the watchdog starts up. Service are monitored as soon as they comeinto existence. The exact location of the pid file is listed for each service in thisconfiguration file.

The watchdog itself is a normal service with init script /etc/init/sv_watchdogd. It is the lastof all ServerView services to start.

The watchdog is integrated in the overall service handling script, /usr/bin/sv_services. Sothe watchdog is implicitly started / stopped together with all other services.

If the product Virtual-IO Manager is installed, then the script /usr/bin/sv_servicesalso handles the services of VIOM.


3.10 Using SNMPv3 with ServerView Operations Manager

3.10 Using SNMPv3 with ServerView Operations ManagerAs of ServerView Operations Manager V7.10 SNMPv3 is supported. SNMPv3 introduces anew framework with a new format of SNMP messages, security issues, access control, andremote configuration of SNMP parameters. To use SNMPv3, you must make certainpreparations on the managed node and the central management station.

For communication between ServerView Operations Manager on the central managementstation and the ServerView Agents on the managed nodes via version 3 of SNMP acommon user must be configured on the communication end points.

If you have prepared the managed node and the central management station you canenable SNMPv3 in ServerView Operations Manager. You have two options for enablingSNMPv3 in ServerView Operations Manager:

l Via the V3 Setting configuration window

l Via the snmp.conf configuration file

For further information on preparing the central management station and the managednode or technical requirements, see "Using SNMPv3 with ServerView Suite products"overview.


3.11 Uninstalling the Operations Manager software

3.11 Uninstalling the Operations Manager softwareIf you want to uninstall a web component and then install an older version of thiscomponent, you must delete all caches beforehand.

How to uninstall when using a remote ServerView database is described in "Uninstallation"on page 87.

l The database backup files are located in the directory/var/fujitsu/ServerViewSuite/ServerViewDB. For reasons of space, you shoulddelete any files that are no longer required.

l Before you uninstall Operations Manager, it is recommended that you removeall report configurations of the Performance Manager according to thedescription in the "Performance Manager" user guide. If you do not removethem, there will be discrepancies between Operations Manager and agentsafter Operations Manager is installed again. Please check before removalwhether there are any other Operations Manager installations which use thesereports too.

l If Virtual-IO Manager or Installation Manager are still installed on the system,you will be asked to uninstall them first.

l Do not stop the uninstallation while it is running. Please wait until the processis completed.

l For Red Hat 7.0, compat-libstdc++-33 library is installed automatically duringServerView Operations Manager installation. But compat-libstdc++-33 librarywill not be uninstalled, when ServerView Operations Manager is uninstalled.

You uninstall the software with the UninstallServerView.sh script, located in the directory/opt/fujitsu/ServerViewSuite/ServerView/scripts and /usr/bin.

By default, the complete Operations Manager software including the databasemanagement system is uninstalled.

SyntaxUninstallServerView.sh <option>

For <option> you can specify:

-OMOperations Manager is uninstalled. An installed Update Manager is also uninstalled.

-UMOnly Update Manager is uninstalled.


3.12 Changing configuration parameters

-EMOnly Event Manager is uninstalled.

-v | --verbose | --debugWrites additional information to the log file.

-f | --forceForces an uninstallation.

If this option is set, the uninstallation will continue even if one of the individualpackages fails to uninstall.

-q | --quietNo console outputs are generated.

If the file /etc/cron.d/pg_CrontabEntry exists even after finishing the uninstallation, removethis file.

3.12 Changing configuration parametersIf either the fully qualified hostname or the IP address of the central management stationchanges, you can reconfigure ServerView Operations Manager by calling theChangeComputerDetails.sh command.

If you want to change the directory service used by ServerView Operations Manager, youcan do this by calling ChangeComputerDetails.sh.

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

If you change the hostname, you must remove the managed server from the serverlist and add it again. Otherwise, the old hostname will be retained in the serverlist.

If you want to change parameters other than the fully qualified hostname, IP address orparameters for the active directory service, proceed as follows.

The ServerView Operations Manager configuration parameters are stored in the file/etc/fujitsu/ServerViewSuite/ServerView/global.conf. In the rare event that you might needto change them, you should do so with caution.

You can either change them during the installation or after it (to change the SNMPcommunity, change the COM_SNMP_COMMUNITY parameter.). You should only changethe parameters COM_SNMP_COMMUNITY and COM_IPCHANGECHECK in this way:

l Changing during the installation

Proceed as follows:


3.12 Changing configuration parameters

1. Install the ServerViewBase package:

sh install.sh --base

2. Edit the file /etc/fujitsu/ServerViewSuite/ServerView/global.conf, e.g. with vi.

3. Install all the other packages:

sh install.sh

For a partial installation, add the relevant option -OM (Operations Manager), -UM (Update Manager), or -EM (Event Manager).

l Changing after the installation

Proceed as follows:

1. Stop all ServerView services:

/usr/bin/sv_services stop

2. Edit the /etc/fujitsu/ServerViewSuite/ServerView/global.conf file, e.g. with vi.

3. Execute the reconfiguration:

/usr/bin/configure-ServerView.sh

4. Start all ServerView services:

/usr/bin/sv_services start

If you have changed the SNMP community you must execute the following script:

/opt/fujitsu/ServerViewSuite/ServerView/scripts/configure/20-SVDBClient.sh

If you have changed the COM_IPAddress or COM_IPCHANGECHECK parameters, youmust also execute the following:

PACKAGE=ServerViewCommon;/usr/bin/configure-ServerView.sh

Both instructions must be entered in the same line.


3.13 Collecting diagnosis data

3.13 Collecting diagnosis dataAfter installing Operations Manager on the central management station, the scriptcmscollect.sh is available in the directory/opt/fujitsu/ServerViewSuite/svom/ServerView/Tools. The script allows you to collectvarious diagnosis data (e.g. information about the web server used by ServerViewOperations Manager, ServerView Services, log files). For diagnostics purposes you can sendthis file to your Fujitsu Customer Service Desk.

To collect the data, proceed as follows:

1. Switch to the directory /opt/fujitsu/ServerViewSuite/svom/ServerView/Tools.

2. To start the collection execute the following command:

sh cmscollect.sh

The result of the collection is stored in the file cmscollect.tar.gz in the directory/var/log/fujitsu/ServerViewSuite.

3.14 Troubleshooting

3.14.1 Removing faulty/stuck packages

Very rarely it may occur that an Operations Manager package cannot be uninstalled.Because of the dependencies of the various packages, they must be uninstalled in thefollowing order:

1. ServerViewOperationsManager

2. ServerViewUpdateManager

3. ServerView_S2

4. ServerViewEventManager

5. ServerViewCommon

6. ServerViewTomee

7. ServerViewDB

8. ServerViewPostgresql

9. ServerViewBase

10. ServerViewConnectorService (But this package could still be required by a ServerViewAgent that might be installed.)



You can use the following command to check whether any other packages are dependenton the one you wish to uninstall:

rpm -q --whatrequires <package>

If there are dependent packages, uninstall these first with the following command:

rpm -e <package>

Or, if you get error messages, uninstall the packages with the following command:

rpm -e --noscripts <package>

3.14.2 Purging the system

Very rarely an installation / uninstallation process might not run to completion. To purgethe system, first uninstall all dependent packages and then the packages themselves (see"Removing faulty/stuck packages" on page 76).

You must then delete the following directories:

l /etc/fujitsu/ServerViewSuite/Postgresql

l /etc/fujitsu/ServerViewSuite/ServerView

l /opt/fujitsu/ServerViewSuite/Postgresql

l /opt/fujitsu/ServerViewSuite/ServerView

l /opt/fujitsu/ServerViewSuite/ServerViewDB

l /opt/fujitsu/ServerViewSuite/UpdateManager

l /opt/fujitsu/ServerViewSuite/tomee

l /opt/fujitsu/ServerViewSuite/apacheds

l /opt/fujitsu/ServerViewSuite/svcommon

l /opt/fujitsu/ServerViewSuite/svom

l /opt/fujitsu/ServerViewSuite/web

This might also delete archives and regular archive and export tasks.

l /usr/bin/UninstallServerView.sh

l /usr/bin/setServerViewEnviron*

l /usr/bin/configure-ServerView.sh



The following directories contain log files of the installation and uninstallation. You cankeep these files:

l /var/log/fujitsu/ServerViewSuite/ServerView

l /var/log/fujitsu/ServerViewSuite/ServerViewDB

l /opt/fujitsu/ServerViewSuite/tomee

l /var/log/fujitsu/ServerViewSuite/vme

l /var/fujitsu/ServerViewSuite/ServerViewDB (Please decide whether you need thebackup files in this directory)

3.14.3 PostgreSQL server does not start

l Check whether the initlog files and the server log file serverlog in the directory/opt/fujitsu/ServerViewSuite/Postgresql/pgsql contain error messages.

l Check that directory /tmp has read, write and execution rights for all.

l Ensure that no old PostgreSQL server is running, by executing the following command:

ps ax | grep -i postgres

If an old PostgreSQL process is running, try to end it. If nothing helps, kill it.

Then remove /tmp/.s.PGSQL.9212.* files.

l If no old PostgreSQL process is running, check that there are no /tmp/.s.PGSQL.9212.*files. If there are, remove them.

Installation fails

l If the installation script aborts with the message "which: no java ...", enter your Javapath in the path variable.

Example

If java is in the directory /usr/java/jre1.8.0-51/bin, execute exportPATH=$PATH:/usr/java/jre1.8.0-51/bin followed by the installation script.

l If the installation of ServerViewDB fails, check whether PostgreSQL is running. If not,perform the steps as described in "PostgreSQL server does not start" on page 78.



3.14.4 ServerView Operations Manager cannot connect to the databaseserver

If ServerView Operations Manager cannot connect to the database server, you will findrelevant messages in the following files:

/opt/fujitsu/ServerViewSuite/web/cgi-bin/ServerView/common/SVDBServer.log

and/or

/opt/fujitsu/ServerViewSuite/web/cgi-bin/ServerView/common/SVDBTrace*.log

As well as in the log files of Postgresql located in:

/opt/fujitsu/ServerViewSuite/Postgresql/pgsql/data/pg_log

Check whether the /etc/hosts file includes the entry for localhost with the IP address127.0.0.1.

3.14.5 System with active PAM configuration

l Installation fails or database backups are not performed.

l System update

Following an update of the operating system on which PAM is activated, ServerViewOperations Manager might no longer work.

Check your PAM configuration, in particular to make sure that the users postgpls and rootcan be called with superuser access.

3.14.6 Tomcat does not work correctly

Very occasionally you may find that the web server used by ServerView OperationsManager starts up and the process is running but it is somehow not working properly. Forexample, the graphical user interface might not start up properly.

One possible reason is that it could not find all the TCP ports that it needs.

Normally there will be an indication in the log files <installation_path>/tomee/logs/localhost_access_log.<YYYY-MM-DD>.log, e.g.

l a Java exception and possibly a URL including a port, e.g. Bad URLpath:rh/jndi/rmi://samnaun_rh:1401/jmxconnector.

l binding failed, TCP connection already in use.



Sometimes it helps to restart Tomcat, with /etc/init.d/sv_tomee restart. But inrare situations you may need to reboot the system.

If you wish to analyze the situation further, you may enter the following:

/opt/fujitsu/ServerViewSuite/tomee/bin/portcheck -v -f

/opt/fujitsu/ServerViewSuite/tomee/bin/jbports >/tmp/ports_v2>&1

for port in $(cat /tmp/ports_v | grep read | cut -d" " -f3); donetstat -antp | grep $port;

done

This would normally list all the processes that use ports required by SVOM. If a port is onlybound but not actually opened for listening, it will not be displayed by netstat, but it stillcannot be opened.

Further information on problems with the web server used by ServerView OperationsManager can be found in the log files of Tomcat located in:

<installation_path>/tomee/logs


4.1 Configuration files

4 ServerView databaseThe ServerView database has been replaced by an SQL database. Under Linux thedatabase management system PostgreSQL is used. Operations Manager does not use thePostgreSQL server from the distribution, but comes with its own. This is installed via therpm package ServerViewPostgresql.

After installation, a description of PostgreSQL can be found in the following directories:

l /opt/fujitsu/ServerViewSuite/Postgresql/pgsql/share/doc

l /opt/fujitsu/ServerViewSuite/Postgresql/pgsql/share/man

For more information on PostgreSQL, visit http://www.postgresql.org.

4.1 Configuration filesDirectory /opt/fujitsu/ServerViewSuite/Postgresql/pgsql/data

The directory /opt/fujitsu/ServerViewSuite/Postgresql/pgsql/data contains the followingconfiguration files for PostgreSQL:

l postgresql.conf

This file contains default values for individual options, including the maximumnumber of users, who is allowed to access the ServerView database, the port numberused (default port: 9212) and installation paths.

l pg_hba.conf

This file defines access authorization to databases. It specifies which system is allowedto log on, the access authorizations for each system, and which system can accesswhich database.

In an upgrade installation, the most recent status of each of these files is saved in thedirectory /var/fujitsu/ServerViewSuite/ServerViewDB. The complete history of these files isstored in the directory /etc/fujitsu/ServerViewSuite/Postgresql.

Directory /etc/fujitsu/ServerViewSuite/ServerView

The directory /etc/fujitsu/ServerViewSuite/ServerView contains the configuration fileglobal.conf, in which global settings are defined. This file is created during installation ofthe ServerViewBase package.


http://www.postgresql.org/

4.2 Connection to the ServerView database is interrupted

4.2 Connection to the ServerView database is interruptedIf the connection to the ServerView database is interrupted, e.g. in the case of LANproblems, the following occurs:

l The ServerView Services service and, if present, the ServerView Download Serviceservice are stopped.

l A message (see figure below) is written to the file /var/log/messages.

l If Operations Manager is running, the following screen is displayed:

Figure 1: Error message

Once the connection to the ServerView database has been restored, the servicesServerView Services and ServerView Download Service must be restarted.

Start the services with following command:

/usr/bin/sv_services start -withPostgres

4.3 Sample configuration for pgAdmin3For the database administration, pgAdmin3 can be used under Linux. To be able to accessthe data of the ServerView database from a Linux system, you must make various settingsin the configuration files.

postgresql.conf

In the configuration file, the entry under listen_addresses specifies whether only the localserver or also remote servers can access the PostgreSQL database server. This entry ispreset to localhost. For the use of Operations Manager, also from a remote system, this issufficient.

For access from a remote system to the data of the ServerView database with pgAdmin3,listen_addresses=’*’ must be specified.


4.4 Administering the ServerView database

pg_hba.conf

Under the line IP1, you enter the system from which the ServerView database can beaccessed:

# IP1: allow all users on the client <Client IP address>

host all postgpls <IP address/network> <Access method>

<IP address/network>Specify the IP address and the netmask in CIDR notation.

For example, 172.20.143.89/32 means one system, while 172.20.143.0/24 means thatall systems in the network (172.20.143) can access the database.

<Access method>Specify the authentication: trust

4.4 Administering the ServerView databaseFor administering the ServerView database under Linux, the following tools are available:

l Tool psql

The CLI is part of the supplied database management system PostgreSQL.

The ServerView database is set up under the database user svuser. Call up the tool asfollows:

/opt/fujitsu/ServerViewSuite/Postgresql/pgsql/bin/psql -p 9212 -U svuser -d ServerViewDB

l pgAdmin3

Graphical tool for administration of PostgreSQL. This tool is available viahttp://www.pgadmin.org/download.

For a description of pgAdmin3, visit http://www.pgadmin.org/docs/.

For PostgreSQL administration you can use pgAdmin3 (only for Linux), whichyou can download from http://www.pgadmin.org. Please use a version 1.8.x.

If you want to use this version to manage the ServerView database, you mustmake appropriate access settings in the database management systemPostgreSQL after installation, see "Sample configuration for pgAdmin3" onpage 82.

In the connection dialog, enter postgpls or svuser. The corresponding entries must beadjusted in the configuration examples.

l phpPgAdmin


http://www.pgadmin.org/download

http://www.pgadmin.org/docs/

http://www.pgadmin.org/

4.5 Backing up the ServerView database

Web-based graphical tool for administration of PostgreSQL.

This tool is available via http://phppgadmin.sourceforge.net.

4.5 Backing up the ServerView databaseBy default, the ServerView database is backed up once a day and once a week. Thesesettings for regular backup are contained in the crontab table /etc/cron.d/pg_CrontabEntryand you can adjust them with the crontab command.

Independent of your settings, only one backup per weekday is created.

The pg_dump command is used for backup. The generated backup file is then compressedwith the program gzip.

You should additionally save the ServerView database to external media so that you havea backup available, for example in the event of a disk error. This should also be done atregular intervals. Use the archiving programs such as tar, cpio or backup for this. TheServerView database backups are kept in the directory/var/fujitsu/ServerViewSuite/ServerViewDB/backup.

4.6 Restoring the ServerView databaseIn the event of an error, you can restore the ServerView database from the backups. Theerrored database must not be deleted before the restoration.

The backup files are located in the directory:

/var/fujitsu/ServerViewSuite/ServerViewDB/backup

To restore a ServerView database from a backup, proceed as follows:

1. Stop the ServerView services:


2. Deactivate the regular backup:

mv /etc/cron.d/pg_CrontabEntry /tmp

3. Import the ServerView database:

gzip -cd /var/fujitsu/ServerViewSuite/ServerViewDB/backup/ServerViewDB_<type>.gz |/opt/fujitsu/ServerViewSuite/Postgresql/pgsql/bin/psql -p 9212 -d ServerViewDB -U svuser

For <type>, enter the backup type (weekly or daily):

Week_<week number><week number> is the number of the week in which the weekly backup took place.


http://phppgadmin.sourceforge.net/

4.7 Exporting/Importing the ServerView database

Monday, ..., SundayWeekday of the daily backup.

4. Activate the regular backup:

mv /tmp/pg_CrontabEntry /etc/cron.d

5. Start the ServerView services:


4.7 Exporting/Importing the ServerView databaseYou can export the ServerView database, for example to send it to the Service Center fordiagnostics. Use the pg_dump command. The backup file contains the user data, scriptsand SQL statements of the database.

To export the database, use the pg_dump command as follows:

/opt/fujitsu/ServerViewSuite/Postgresql/pgsql/bin/pg_dump -p9212 -U svuser ServerViewDB --clean | gzip ><directory>/ServerViewDB_<name>.gz

<directory>Directory of the database backup.

<name>Optional specification of your own identifier for the backup.

To import the ServerView database during operation, proceed as follows:

1. Stop the ServerView services:


2. Import the ServerView database:

gzip -cd /var/fujitsu/ServerViewSuite/ServerViewDB/backup/ServerViewDB_<type>.gz |/opt/fujitsu/ServerViewSuite/Postgresql/pgsql/bin/psql -p9212 -d ServerViewDB -U svuser

3. Start the ServerView services:


4.8 ServerView database on a remote database serverAs of ServerView Operations Manager version 4.80 you can install the ServerView databaseon a remote database server. The following sections describe the steps necessary for


4.8 ServerView database on a remote database server

installation, update installation and uninstallation on the remote database server and onthe central management station.

4.8.1 Installation

Installation on the remote database server

Proceed as follows on the remote database server:

1. Install the packages ServerViewBase, ServerViewPostgresql, and ServerViewDB withthe following command:

./install.sh --remotedbserver

or

./install.sh --RDBS

The packages are installed.The ServerView database itself is not generated duringinstallation of the ServerViewDB package, but only when the installation is performed onthe central management station.

Installation on the central management station

Proceed as follows on the central management station:

1. Install the ServerViewBase package with the following command:

./install.sh --base

2. When you install the ServerViewBase package, the configuration file global.conf isalso installed in the directory /etc/fujitsu/ServerViewSuite/ServerView.

Open this file and enter the IP address of the remote database server at the followingentry:

export COM_DB_SERVER="127.0.0.1"

e.g.:

export COM_DB_SERVER="111.22.33.77"

3. Install further required packages with the following command:

./install.sh

Unless you specify an option, all packages will be installed, see "Installed OperationsManager packages" on page 69. If you only want to install individual packages, youmust specify the relevant option, see "Installation" on page 54.

During installation of the ServerViewDB package, the ServerView database isgenerated on the remote database server.


4.8 ServerView database on a remote database server

4.8.2 Update installation

Before you begin an update installation you must stop all ServerView services on thecentral management station. Do this by entering the following command:


Proceed as follows:

1. For an update installation of the ServerView database on the remote database server,enter the following command:

./install.sh --remotedbserver

or

./install.sh --RDBS

2. Start the service with following command (on the central management station):


For an update installation on the central management station, enter the followingcommand:

./install.sh

The entire Operations Manager software is updated. For an update installation ofindividual components, you must specify the relevant option, see "Installation" onpage 54.

4.8.3 Uninstallation

For uninstallation you must first uninstall the Operations Manager software on the centralmanagement station and then the ServerView database on the remote database server.

Uninstallation is described in "Uninstalling the Operations Manager software" on page 73.

4.8.4 ServerView database backups

By default the ServerView database on the remote database server is backed up daily. TheServerView database is also backed up once a day on the central management station.

The backups of the ServerView database are kept in the directory/var/fujitsu/ServerViewSuite/ServerViewDB/backup.


4.9 Error diagnostic

4.8.5 Switching the database server

Switching from local database server to remote database server

Install the remote database server as described in the previous sections. On the centralmanagement station, execute the following command:

/opt/fujitsu/ServerViewSuite/ServerView/scripts/change-DB.sh --remote <IP address of the remote server>

Switching from remote database server to local database server

On the central management station, execute the following command:

/opt/fujitsu/ServerViewSuite/ServerView/scripts/change-DB.sh --local

When you have switched the database server, you can uninstall the Operations Managersoftware on the former remote database server.


4.9.1 unixODBC Manager

The Operations Manager software and the database management system PostgreSQL canonly be installed if the unixODBC Manager is installed (see also "Requirements" on page27).

4.9.2 Error during installation/uninstallation

Installation

The installation process is logged in log files. To receive debugging information, specifythe option -v for install.sh.

If an error occurs during installation, the error will be displayed and all actions so far willbe undone. The log files of the database management system PostgreSQL are storedunder:

l /opt/fujitsu/ServerViewSuite/Postgresql /pgsql/initlog

l /opt/fujitsu/ServerViewSuite/Postgresql /pgsql/data/serverlog

l /var/log/fujitsu/ServerViewSuite/ServerView/install.log

l /var/log/fujitsu/ServerViewSuite/ServerView/upgrade.log



l /var/log/fujitsu/ServerViewSuite/ServerViewDB/ServerView_Debug/ServerViewError.log

l /opt/fujitsu/ServerViewSuite/ServerView/tomee/logs/svom/catalina.log

If you can resolve the error using the log files/opt/fujitsu/ServerViewSuite/Postgresql/pgsql/data/pg_log/*.log, you can then restart theinstallation.

If you have problems starting the web server used by ServerView Operations Manager oraccessing it after installation, you may be able to diagnose them with the help of the file<installation_path>/tomee/logs/localhost_access_log.<YYYY-MM-DD>.log.

If you cannot resolve the error, send the above-listed log files to the Service Center fordiagnostics.

You can delete old files from the directory/opt/fujitsu/ServerViewSuite/Postgresql/pgsql/data/pg_log if you do not need them forproblem diagnostics.

Uninstallation

The uninstallation process is logged in the file/var/log/fujitsu/ServerViewSuite/ServerView/uninstall.log.

4.9.3 Uninstalling the ServerView database

If the ServerView database is blocked by another program, it is not possible to uninstallthe ServerView database and the database management program. To solve the problem,stop all external programs that have access to PostgreSQL, e.g. programs for PostgreSQLadministration.

4.9.4 System is slowing down

If you notice that your system is slowing down, you can rebuild the indexes of theServerView database. This is done using the REINDEX command, which is described in thePostgreSQL documentation which can be found in the following directories:

l /opt/fujitsu/ServerViewSuite/Postgresql/pgsql/share/doc

l /opt/fujitsu/ServerViewSuite/Postgresql/pgsql/share/man

4.9.5 Checking the status of PostgreSQL

In some cases it may be necessary to check the status of the database managementsystem. Use the following command:

/etc/init.d/sv_postgresql status



4.9.6 Starting and stopping PostgreSQL

In some cases it may be necessary to stop or start the database management systemmanually or to restart a database management system that is already running.

Starting PostgreSQL/etc/init.d/sv_postgresql start

Stopping PostgreSQL/etc/init.d/sv_postgresql stop

Startup problems under SLES 11 can be resolved as follows:

1. Start YaST via the start menu.

2. Select System and then click System Services (Runlevel). The System Services(Runlevel): Services window opens.

3. Select Expert Mode.

4. Select the sv_postgresql service from the list.

5. Under Service will be installed in following run levels: activate levels 3 and 5.

6. Click Set/Reset and then select Enable the service.

7. Save your settings and then click Finish.

In the case of systems with Red Hat, please use the product ServiceConfiguration availableunder Menu – System Settings – Server Settings – Services.

Restarting a running PostgreSQL/etc/init.d/sv_postgresql restart

4.9.7 Restarting Operations Manager

You can restart Operations Manager completely on the Linux system. Proceed as follows:

/usr/bin/sv_services restart -withPostgres -withTomee -withSCS

The following services are started via the additional options:

l Service /etc/init.d/sv_postgresql:

-withPostgres

l Service /etc/init.d/sv_tomee:

-withTomee

l Service /etc/init.d/srvmagt_scs:

-withSCS


4.10 Changing the load distribution

4.10 Changing the load distributionServerView allows you to influence the system load it incurs or the number of concurrentjobs.

The following services start jobs whose concurrent number may be defined in an ini file.

ArchiveService <scripts>/ServerView/SnmpArchive/SVArchiveServer.ini

ExportService <scripts>/ServerView/SnmpExport/ExportServer.ini

InventoryService <scripts>/ServerView/SnmpInventory/ SVInventoryServer.ini

<scripts>: directory /opt/fujitsu/ServerViewSuite/web/cgi-bin

Each of these configuration files holds a variable ConcurrentJobsAllowed in the sectionGLOBALS. The number given there states how many concurrent jobs are started.

Example

Archiving is activated for all servers and 100 manageable servers are present in theserver list. If ConcurrentJobsAllowed is set to 30 in SVArchiveServer.ini, there willalways be at most 30 servers being archived at the same time. Once archiving isfinished for one server of the 30 started jobs, then archiving for another server isstarted. This is repeated until all 100 servers are archived.

The current default values for ConcurrentJobsAllowed are:

SVArchiveServer.ini 30

DownloadServer.ini 30

ExportServer.ini 100

SVInventoryServer.ini 10

If you upgrade the Operations Manager software, the value forConcurrentJobsAllowed parameter will be reset to the default value.


4.10 Changing the load distribution

1. Before changing the number of ConcurrentJobsAllowed:

Before changing the number of ConcurrentJobsAllowed, please ensure that nojobs of the respective service are running. For ArchiveService,DownloadService and ExportService this can easily be verified via therespective GUI in the tab settings. If there are blue arrows displayed for thestatus of a task then a job is running for the server.

For InventoryService please check in the process list whether a process calledSVSnmpInventory is running. In Linux you can view the process list via thecommand ps.

2. Effect of reducing the number of concurrent jobs:

Reducing the number of concurrent jobs has two effects: On the one hand itreduces the system load; on the other it increases the time required by a jobto process a group of servers.


5 Fujitsu Technology Solutions Software LicenseAgreement for End User1. Subject of this Agreement1.1 For the purposes of this agreement “Software” shall mean the software with the objectcode, the version and the specification indicated in the software product data sheet ofFujitsu Technology Solutions.

The Software consists of machine-readable instructions and/or printed documentation andrelated licensed materials.

1.2 Please read this agreement carefully before you use the Software. If you do not agreewith the license terms in this agreement, you are not permitted to use the Software andmust immediately return all copies of the Software and all accompanying items to theLicensor/Sublicensor (either Fujitsu Technology Solutions or the reseller who supplied youwith the Software) with proof of purchase for a full refund.

1.3 Any use of the Software requires the proper payment of the applicable license fees. Byusing the Software you agree to be bound by the terms of this agreement.

1.4 Fujitsu Technology Solutions reserves the right to implement at any time in the futurean additional software license key and/or license certificates as countermeasures againstsoftware piracy.

1.5 Software components from third-party software suppliers which are part of the scopeof the delivery are subject to separate license agreements that are included with theSoftware or that are transmitted by Fujitsu Technology Solutions upon request.

2. End User License2.1 Fujitsu Technology Solutions grants you a non-exclusive and non-transferable licenseto use the Software on the number of workstations for which you have purchased licenses.Unless you purchase additional licenses, you are not permitted to operate the Software onmore than the maximum number of licensed workstations or on hardware that exceedsthe specified type.

You are permitted to make a backup copy of the Software for archiving purposes, providedyou properly mark the copy or partial copy of the Software with the copyright notice andany other ownership information.

2.2 You are not permitted to copy, modify or distribute the Software. Furthermore, you arenot permitted to re-compile, re-engineer, convert, revise, compile or modify the Software.You may not sub-license, without selling the related hardware, assign, rent, lease ortransfer the Software except as expressly permitted by this agreement or due tomandatory legal regulations.


2.3 If you acquired the Software as a program upgrade, your license for the use of the oldsoftware version ends automatically with the installation of the upgrade version of theSoftware. If parts of the old software version are not replaced by the upgrade version, thelicense for the old version continues to be effective until the remnants of the old softwareversion are also replaced or deactivated or shut down in any other way.

2.4 Unless specified otherwise in the respective software data sheet of Fujitsu TechnologySolutions, the license for a software version or release does not give you any rights to newreleases (updates), new versions (upgrades) or technical support services for the Software.Supplemental software support contracts and maintenance services, including orexcluding new releases and new versions and additional technical support services, can bepurchased separately either from Fujitsu Technology Solutions directly or from authorizedsoftware resellers.

3. DownloadingFor Software supplied by Fujitsu Technology Solutions over a network or a similardistribution path, the following additional conditions shall apply:

All products supplied for downloading by Fujitsu Technology Solutions are selected, madeavailable and — if supplied by third parties — provided without modification. However, youare fully responsible for ensuring the most current version and usability of downloadablematerial for your own purposes and on your own system. You download Software at yourown risk. Fujitsu Technology Solutions will not accept any liability, particularly not fortransmission errors or problems that arise during the downloading process (line failures,connection interruptions, server failures, data corruption, etc.).

The website of Fujitsu Technology Solutions is operated and administered only for thosecountries in which Fujitsu Technology Solutions has one or more offices. FujitsuTechnology Solutions accepts no responsibility that Software and/or documentation can ormay be downloaded from a Fujitsu Technology Solutions website also in locations otherthan the countries mentioned above. If you access a website of Fujitsu TechnologySolutions from abroad, you are fully responsible for complying with any local regulations.Fujitsu Technology Solutions expressly prohibits the downloading of Software and/ordocumentation from a Fujitsu Technology Solutions website in countries where suchdownloading is considered illegal.

4. CopyrightAll rights and licenses, unless they are expressly granted to you in this license terms, aswell as all property and usage rights related to the Software (including parts of theSoftware) remain fully with Fujitsu Technology Solutions and/or its third-party licensors.

The license terms do not authorize you to use the brands, logos or trademarks of FujitsuTechnology Solutions or its third-party licensors, nor are you permitted to use any otherbrands which are deceptively similar to the brands, logos or trademarks of FujitsuTechnology Solutions. Each and any use of brands, logos or trademarks with respect to theSoftware or Fujitsu Technology Solutions requires the express consent of FujitsuTechnology Solutions.


5. Licensor’s warranty and liability disclaimer, if Software is sold and delivered byResellerIf you acquire the Software directly from an authorized reseller (called “Reseller”), the rightto install and use the Software may be subject to additional software license conditionsagreed upon between you as the licensee and the respective reseller.

In all cases of an authorized software resale, the software is sublicensed and madeavailable to the licensee directly by the Reseller. In such cases, Fujitsu TechnologySolutions is not a contractual party of the software license agreement between you, aslicensee and the Reseller, as far as the procurement of the software licenses are concerned.Legal claims in connection with the software licensing can therefore be asserted only onthe basis of the agreements with the Reseller. Under no circumstances, however, will therespective scope of the license for the licensee exceed the scope of the license agreementsas specified in sections 1, 2, 3 and 4 of this agreement.

Subject to mandatory legal regulations, particularly those governing liability and/orwarranties, which cannot be excluded in connection with end user license agreementregulations and with reference to the licensee’s claims against the Reseller, FujitsuTechnology Solutions disclaims all warranties for the Software in this agreement.

For the same reason, Fujitsu Technology Solutions disclaims any and all liability/claims forany violations of third parties’ rights as well as any implied warranties for the software’smarketability and its suitability for a particular purpose. This disclaimer of liability doesnot apply in cases of willful or malicious behavior by Fujitsu Technology Solutions.

In this End User License Agreement, Fujitsu Technology Solutions grants no warranties ofany kind, either express or implied.

6. Disclaimer of liability with respect to shareware, freeware and/or open sourcesoftware components6.1 The Software may contain freeware or shareware which Fujitsu Technology Solutionsreceived from a third party. Fujitsu Technology Solutions paid no license fees for the use ofthis freeware or shareware. Accordingly, the licensee is not charged any license fees for theuse of the freeware or shareware. You recognize and accept that Fujitsu TechnologySolutions therefore grants no warranties with respect to such freeware or sharewarecomponents and does not assume any liability in connection with the ownership, thedistribution and/or the use of the respective freeware or shareware.

6.2 The Software may also contain open source software components that were developedaccording to the “open source model” and which are distributed exclusively on the basis ofthe GPL (General Public License: http://www.gnu.org/copyleft/gpl.html) terms andconditions or other standard open source standard license terms and conditionsapplicable to the respective open source components at the time of their dissemination.You recognize and accept that the licensing of such open source software components isgoverned exclusively by the above-mentioned GPL terms or by the conditions which areotherwise included with the open source software components. Fujitsu TechnologySolutions receives neither license fees nor any other compensation for the delivered open


http://www.gnu.org/copyleft/gpl.html

source software components. As far as Fujitsu Technology Solutions or a third partyreceives any compensation in connection with open source software components, it isreceived exclusively for additional delivery items and/or services.

Because of the special nature of the development and distribution of open source softwarecomponents, Fujitsu Technology Solutions assumes no express or implied liability for suchcomponents and excludes any kind of warranty for such open source softwarecomponents, particularly in connection with missing specifications, lack of functionality,programming errors or any other malfunctions.

7. General limitations of liability7.1 Neither Fujitsu Technology Solutions nor its suppliers are liable for any consequentialor indirect damages, including damages arising as a result of or in connection with anoperational interruption, lost profits or sales, lost data, or costs of capital. FujitsuTechnology Solutions and its suppliers will not be liable for additional ancillary orconsequential costs or for any other losses, costs or expenses of any kind which arise as aresult of the holding, sale, use or impossibility of use of the Software, independent ofwhether such claims are asserted due to warranty rights, contracts, tort or any other legaltheory.

7.2 The liability of Fujitsu Technology Solutions for direct damage caused as a result of acontract violation and/or other action or lapse on the part of Fujitsu Technology Solutionswhich have not been excluded or cannot be completely excluded due to mandatory laware limited to no more than €250,000.00. Any and all other liabilities for direct damageare excluded. Damage caused by Fujitsu Technology Solutions as a result of slightnegligence are excluded to the extent permitted by applicable legal regulations.

7.3 Limitations and exclusions of liability resulting from this agreement do not apply todamage where Fujitsu Technology Solutions carries compulsory liability according toapplicable laws and where such liability cannot be limited to a maximum amount (forexample, liability for bodily damage; product liability or fraudulently incorrectinformation).


8. Export controlsDue to its components as well as the nature or purpose of these components, the export ofthe Software and/or its accompanying documents may be subject to official or regulatoryapproval. In cases where the Software is intended for export, you are obliged to get allapprovals and authorizations required to comply with all relevant export regulations.

The Software may not be exported if there is reason to assume that the Software will beused in connection with nuclear, chemical or biological weapons or for missile technology.Furthermore, you may not deliver the Software — or have it delivered indirectly — to suchcompanies or persons who are listed in the applicable U.S. export regulations (particularlythe Table of Denial Orders/U.S. Denied Persons Lists (DPL) or in the E.U. export regulations(particularly the EU Terrorist List) or in the applicable warnings issued by the Germanexport authorities or any other competent authorities in any country.

Under no circumstances is Fujitsu Technology Solutions obligated to deliver software,patches, updates or upgrades, to provide software for download or to fulfill any othercontractual commitments if this would be a violation of the applicable export regulationsof the Federal Republic of Germany, the European Union, the United States of America orof any other countries.

If you export or re-export the Software or a copy of it, this may be a violation ofapplicable export laws and a severe violation of the terms of this agreement.

9. Miscellaneous9.1 If any term or condition in this agreement or any other contract that is subject to theterms and conditions of this agreement turns out to be invalid or unenforceable (partly orin full), the validity of all other terms and conditions remains unaffected, unlesscomplying with the remaining terms and conditions would represent an unreasonablehardship for either contract party, even with the application of applicable legalregulations to close the legal gap.

9.2 If you/ the licensee do not pay the license fees due and/or if the licensee does notcomply with essential terms and conditions of this license agreement, Fujitsu TechnologySolutions reserves the right to cancel the license. In case of such cancellation, you mustimmediately return any and all copies of the software in your possession and confirm thecomplete return [of the software copies] or the destruction of these copies in writing.

9.3 Neither you nor Fujitsu Technology Solutions is responsible or liable for the respectiveparty’s non-compliance with its obligations if the reason for such non-compliance isoutside the party’s control due to force majeure.

9.4 Any and all modifications and/or amendments to these license terms and conditionsare only valid if they are made in writing.

10. Applicable law10.1 These license terms and conditions are governed by the laws of the Federal Republicof Germany.


10.2 In the event that provisions of clause 10.1 are unenforceable, these license terms andconditions shall be governed by the laws of the country in which you acquire the Software,with the following exceptions: 1) In Australia, the terms and conditions of this license aregoverned by the laws of the state or sovereign territory in which the business contract isbeing concluded; 2) in Albania, Armenia, Belarus, Bosnia-Herzegovina, Bulgaria, Croatia,the Czech Republic, Georgia, Hungary, Kazakhstan, Kirgizia, the former YugoslavianRepublic of Macedonia (FYROM), Moldavia, Poland, Romania, Russia, Slovakia, Slovenia,the Ukraine and the Federal Republic of Yugoslavia, the terms and conditions of thislicense are governed by the laws of the Federal Republic of Germany; 3) in the UnitedKingdom [Great Britain], all disputes with respect to these license terms and conditionsare governed by English law, and English courts have exclusive jurisdiction; 4) in Canada,the terms and conditions of this license are governed by the laws of the Province ofOntario; 5) in the United States of America and in Puerto Rico as well as in the People’sRepublic of China the terms and conditions of this license are governed by the laws of theU.S. State of New York.


ServerView Operations Manager- Installation under...

Documents

Transcript of ServerView Operations Manager- Installation under...