FUJITSU ServerView Operations Manager, Update Manager, Event Manager server management software Installation guide
تبلیغات
تبلیغات
Installation Guide - English
FUJITSU Software ServerView Suite
ServerView Operations Manager
V7.10
Installing ServerView Operations Manager Software under Windows
(Operations Manager, Update Manager, Event Manager)
Edition
August 2017
Comments… Suggestions… Corrections…
The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs.
Feel free to send us your comments by e-mail to [email protected]
.
Certified documentation according to DIN EN ISO
9001:2008
To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard
DIN EN ISO 9001:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH www.cognitas.de
Copyright and trademarks
Copyright 1998 - 2015 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.
Contents
1.1 Target groups and objectives
1.2.1 Last-minute changes/corrections
1.2.3 Central management station (CMS)
1.3 Changes since the previous version
1.4 ServerView Suite link collection
1.5 Documentation for the ServerView Suite
1.7 Product names - conventions
2.2 Installation on the central management station
2.3 Installation on the managed servers
2.4 Integration options of Operations Manager
3 Installing ServerView Operations Manager
3.1 ServerView Operations Manager components
3.2.2 Role-based user administration
3.4 Administrative user "svuser"
3.5 ServerView Status gadget for Windows Vista and Windows 7
3.6 Preparations and important steps before you start the installation
3.6.1 Install the SNMP service
3.6.2 Installing Java Runtime Environment
3.7 Installation options for SQL Server
3.7.1 Locally on the management station
3.7.2 Remotely on a different system
Installation under Windows 3
Contents
4
3.7.3 Installing SQL Server on a domain controller
3.8 Setting SQL Server memory option
3.9.1 Hardware and software requirements
3.9.3 Setting up a service account
3.9.4 Installing SQL Server 2014 Express edition
3.9.5 Installing SQL Server 2014 Express Management Studio
3.9.6 Installing SQL Server 2014 Enterprise/Standard edition
3.9.7 Adding a user account with SQL Server administrator rights
3.10.1 Hardware and software requirements
3.10.1.1 Hardware requirements
3.10.1.2 Software requirements
3.10.3 Setting up a service account
3.10.3.1 Operations Manager service accounts
3.10.3.2 SQL Server service accounts
3.10.4 Installing SQL Server 2012 Express edition
3.10.5 Installing SQL Server 2012 Express Management Studio
3.10.6 Installing SQL Server 2012 Enterprise/Standard edition
3.10.7 Adding a user account with SQL Server administrator rights
3.11.3 Setting up a service account
3.11.3.1 Operations Manager service accounts
3.11.3.2 SQL Server service accounts
3.11.4 Installing SQL Server 2008 (R2) Express edition
3.11.5 Installing SQL Server 2008 R2 Express Management Studio
3.11.6 Installing SQL Server 2008 (R2) Enterprise/Standard/Workgroup edition 80
Installation under Windows
Contents
3.11.7 Adding a user account with SQL Server administrator rights
3.12.2 Preparing for installation
3.12.3 Installing SQL Server 2005 Express edition
3.12.4 Installing SQL Server 2005 Enterprise/Standard/Workgroup edition 89
3.13 Configuring a remote SQL Server 92
3.13.1 Troubleshooting for Remote SQL Server
3.13.1.1 Messages after clicking Next in the Remote DB dialog
3.14 Operations Manager installation without SQL Server "sysadmin" access
3.14.1 Overview of Windows accounts and access rights
3.14.2.1 Tasks to be performed by the Windows Administrator on the
3.14.2.2 Select the SQL Server
3.14.2.3 Tasks to be performed by the SQL Server Administrator
3.14.3 Further configuration steps for a remote SQL Server
3.14.4 Further procedure on the management station
3.15 Upgrade installations of SQL Server
3.15.1 Upgrading to later SQL Server versions
3.15.1.1 Upgrading the SQL Server instance
3.15.1.2 Moving the ServerView database
3.15.2 Upgrading SQL Server 2012/2014 Express to SQL Server
3.15.3 Upgrading SQL Server 2008 Express to SQL Server 2008
3.15.4 Upgrading SQL Server 2005 Express to SQL Server 2005
Installation under Windows 5
Contents
6
3.16 Installing Operations Manager on Windows Terminal
Server/Remote Desktop Services
3.19 Menu-driven installation of Operations Manager software
3.20 Modify installation of Operations Manager software
3.21 Upgrade installation of Operations Manager
3.22 Uninstalling the Operations Manager software
3.24 Collecting diagnostics data
4.1 Configuration file ServerViewDB.ini
4.2 Connection to the ServerView database is interrupted
4.3 Managing the ServerView database
4.4 Backing up the ServerView database
4.4.1 Backup jobs for the ServerView database
4.4.2 Requirements for executing jobs
4.4.3 Editing and tracking the progress of the backup jobs
4.4.4 Checking the existence of backup files
4.4.5 Checking the contents of the backup files
4.5 Restoring the ServerView database
4.5.1 Restoration via SQL Server Management Studio
4.5.2 Checking the database backup
4.6 SQL Server Express - database limit
4.6.1 Monitoring measures in Operations Manager
4.6.2 Measures for solving the problem
4.7 Moving the ServerView database from local to remote SQL Server 193
4.7.1 Requirements on the remote server 194
4.8 Changing the load distribution
4.9.2 Important information in the event of an error
4.9.3 Growth of the ServerViewDB_log.LDF file
Installation under Windows
Contents
4.9.4 Exporting the ServerView database
5.1 Installing Operations Manager software via the command line
5.2 Database management via sqlcmd
5.2.1 Checking the product version and language of SQL Server
5.2.2 Restoring the ServerView database
5.3 Backing up/Restoring the ServerView database via command line tool
5.3.1 Backing up the ServerView database
5.3.2 Restoring the ServerView database
6 Fujitsu Technology Solutions Software License Agreement for
Installation under Windows 7
8 Installation under Windows
1 Introduction
ServerView Operations Manager (Operations Manager for short) is a free server management module of the Fujitsu ServerView Suite. It is used for central administration of industry-standard servers which run the operating systems
Windows and Linux (SUSE and Red Hat) or which serve as hosts for virtual machines (VMs) that use hypervisors such as VMware ESXi, Citrix XenServer or
Hyper-V.
The standardized management of all servers occurs via one or more central management stations, which you can access from any workstation in the network that has a popular Web browser and the Java Runtime Environment.
Operations Manager controls the individual systems, including critical hardware components such as processors, RAM, hard disks, fans and power supply. It monitors and controls the power consumption, analyzes the performance and utilization data and updates the server configuration.
The security concept of Operations Manager includes role-based user management based on three underlying concepts: l
Global user management via an LDAP directory service (Lightweight
Directory Access Protocol) l
Role-Based Access Control (RBAC) 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 your company by assigning a task-oriented authorization profile to each role.
SSO means that you only need to authenticate yourself once. Once you have done this successfully, you are given access to all ServerView components without having to sign on to any of them again.
Installation under Windows 9
1 Introduction
Server management with Operations Manager offers important benefits to operators of a comprehensive server network: l l l
Higher productivity thanks to high failsafety of the servers
Reduced costs through automated monitoring of the IT infrastructure
Flexible expansion possibilities for the servers, as Operations Manager can be easily adjusted to changed conditions l l l l l
Shorter downtimes thanks to simplified error analysis
Guarantees energy-efficient and, where possible, uninterruptible server operation
Quicker response times in the event of errors
Reduction in total cost of ownership (TCO) through efficient use of network components and their resources
Very easy operation thanks to ergonomic software: clearly laid out, intelligent user guidance and supportive help system
1.1
Target groups and objectives
This manual is intended for system administrators, network administrators and service technicians that have a basic knowledge of hardware and software. The manual documents the requirements for the use of Operations Manager that are specific to the operating system and describes the installation of the products
ServerView Operations Manager, ServerView Update Manager and ServerView
Event Manager.
10 Installation under Windows
1.2 Technical requirements
1.2
Technical requirements
1.2.1
Last-minute changes/corrections
Any last-minute changes/corrections of the technical requirements can be found in the Readme file on the ServerView Suite DVD 2. You have the following options: l l
On the DVD switch to the directory SVSSoftware – Software – ServerView
– Windows – ServerView_S2.
Start the DVD and select ServerView Software Products in the Welcome dialog. In the Web browser window select ServerView- Operations
Manager - Info.
1.2.2
Management console
l l l l
Standard PC, LAN with http access
Microsoft Windows with Internet Explorer V9/V10 or Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_45 or higher, Firefox as of V25 is required.
SUSE/Red Hat Linux with default Web browser released with distribution
Java Runtime Environment (JRE) V1.7.0_40 or higher, Java Runtime
Environment (JRE) V1.8.x
1.2.3
Central management station (CMS)
Hardware
l
PRIMERGY server l
Only for PRIMEQUEST: PRIMEQUEST server l l l l l
Processors with at least two cores
Main memory: at least 4 GB RAM
100 MBit-LAN
At least 100 GB free disk space
Graphics 1280 x 1024 (recommended: minimum 1024 x 768)
Installation under Windows 11
1 Introduction
Software
l
Microsoft Windows® Server 2012 all editions
(but no Server Core installation) l
Microsoft Windows® Server 2012 R2 all editions
(but no Server Core installation) l l
Microsoft Windows® Server 2008 all editions
(but no Server Core installation)
Microsoft Windows® Server 2008 R2 all editions
(but no Server Core installation)
Database
l
Local under Windows:
Included with the ServerView package: Microsoft SQL Server 2008 R2
Express SP2 and Microsoft SQL Server 2005 Express SP4
Additionally supported: o o o
Microsoft SQL Server 2005 Standard, Workgroup, Enterprise
Microsoft SQL Server 2008 Standard, Workgroup, Enterprise, Express
Microsoft SQL Server 2008 R2 Standard, Workgroup, Enterprise, Express l o o
Microsoft SQL Server 2012 Standard, Enterprise, Express
Microsoft SQL Server 2014 Standard, Enterprise, Express
Remote under Windows o o o o o
Microsoft SQL Server 2005 Standard, Workgroup, Enterprise
Microsoft SQL Server 2008 Standard, Workgroup, Enterprise
Microsoft SQL Server 2008 R2 Standard, Workgroup, Enterprise
Microsoft SQL Server 2012 Standard, Enterprise
Microsoft SQL Server 2014 Standard, Enterprise
Java Runtime Environment
l
Java Runtime Environment (JRE) V1.7.0_40 or higher
12 Installation under Windows
1.3 Changes since the previous version
1.3
Changes since the previous version
This edition of the manual applies to ServerView Operations Manager as of
V7.10 and replaces the online manual "ServerView Operations Manager V7.00 -
Installation under Windows", edition October 2014.
The manual features the following changes and enhancements: l l
Support for SQL Server 2014, see
"SQL Server 2014" on page 51 .
The internal directory service is now ApacheDS instead of OpenDJ.
The sections
and
Operations Manager software" on page 140
have been updated.
l l
Modified SSL/TLS configuration of JBOSS and ApacheDS. By default, the TLS v1.1, TLS v1.2, and SSLv2Hello protocols are supported. See section
"Menudriven installation of Operations Manager software" on page 140 .
As of Installation Manager V11.14.09 there are two ServerView Suite DVDs: o
DVD 1: Installation (Installation Manager) o
DVD 2: Management and Serviceability (e.g. ServerView Operations
Manager Software)
Therefore the section
"ServerView Suite link collection" on page 13 " has
been updated.
1.4
ServerView Suite link collection
Via the ServerView Suite link collection, Fujitsu provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers.
For ServerView Suite, links are offered on the following topics: l l l l l
Forum
Service Desk
Manuals
Product information
Security information
Installation under Windows 13
1 Introduction l l
Software downloads
Training
The downloads include the following: o o o
Current software statuses for the ServerView Suite as well as additional Readme files.
Information files and update sets for system software components
(BIOS, firmware, drivers, ServerView Agents and ServerView Update
Agents) for updating the PRIMERGY servers via ServerView Update
Manager or for locally updating individual servers via ServerView
Update Manager Express.
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 l
Service Desk
Manuals l l
Product information
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 on the menu bar.
This opens the start page of the ServerView Suite link collection.
2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu manual server.
You access the start page of the online documentation via the following link: http://manuals.ts.fujitsu.com
l
In the selection list on the left, select x86 Servers.
14 Installation under Windows
1.5 Documentation for the ServerView Suite l l
On the right, click PRIMERGY ServerView Links under Selected
documents.
This opens the start page of the ServerView Suite link collection.
3. Via the ServerView Suite DVD 2.
In the start window of the ServerView Suite DVD 2, select the option
ServerView Software Products.
l
On the menu bar select Links.
This opens the start page of the ServerView Suite link collection.
1.5
Documentation for the ServerView Suite
The documentation can be downloaded free of charge from the Internet. You will find the online 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 the filing structure, see the ServerView Suite sitemap (ServerView Suite
– Site Overview).
Installation under Windows 15
1 Introduction
1.6
Typographic conventions
The following typographic conventions are used:
Convention Explanation
Indicates various types of risk, namely health risks, risk of data loss and risk of damage to devices.
Indicates additional relevant information and tips.
bold
monospace
monospace semibold
Indicates references to names of interface elements.
Indicates system output and system elements, e.g., file names and paths.
Indicates statements that are to be entered using the keyboard.
Indicates a link to a related topic.
blue continuous text pink continuous text
<abc>
[abc]
[key]
Indicates a link to a location you have already visited.
Indicates variables which must be replaced with real values.
Indicates options that can be specified (syntax).
Indicates a key on your keyboard. If you need to enter text in uppercase, the Shift key is specified, for example, [SHIFT] + [A] for
A. If you need to press two keys at the same time, this is indicated by a plus sign between the two key symbols.
Screenshots
Some of the screenshots are system-dependent, so some of the details shown may differ from your system. There may also be system-specific differences in menu options and commands.
16 Installation under Windows
1.7 Product names - conventions
1.7
Product names - conventions
In the document, product names used in the text are abbreviated as follows:
Windows Server 2012 and 2012 R2
Installation under Windows 17
1 Introduction
Windows Server 2008 and 2008 R2
18 Installation under Windows
Linux
Virtualization software
1.7 Product names - conventions
Installation under Windows 19
1 Introduction
Component names
20 Installation under Windows
2.1 Architecture
2 PRIMERGY server management
2.1
Architecture
The architecture of ServerView Operations Manager is based on a management console, a central management station (CMS) and the managed servers.
Installation under Windows 21
2 PRIMERGY server management
Management console
A browser-based console allows you to manage the servers and display the determined data. The following can be used as a browser: l
Microsoft Windows with Internet Explorer or Mozilla
Firefox l
SUSE/Red Hat Linux with default Web browser released with distribution
The Java Runtime Environment must also be installed.
Central management station (CMS)
On the central management station the ServerView
Operations Manager is installed. The optional components of the ServerView Suite, such as Virtual IO-Manager, are also installed on the central management station and integrated in Operations Manager.
The central management station (and thus the ServerView
Operations Manager with its components) may also run on a
Windows or Linux virtual machine (VM).
The global user management of the ServerView Suite and of the iRMC each centrally stores users for all Central
Management Stations (CMS) / iRMC in the directory of an
LDAP directory service. This enables you to manage the users on a central server. The users can therefore be used by all the
CMS and iRMC that are connected to this server in the network.
The ServerView Suite currently supports the following directory services: l l
ApacheDS (running on JBoss 7).
Microsoft Active Directory
22 Installation under Windows
2.1 Architecture
During the installation of ServerView Operations Manager you have the option to choose ServerView’s internal directory service (ApacheDS). For further information about the use of directory services with ServerView, refer to the manual ’’User
Management in ServerView’’ (see
).
The data which ServerView creates and uses is stored in an
SQL database within an SQL Server. The following SQL Server are part of the ServerView Operations Manager installation: l l
SQL Server 2008 R2/2005 Express under Windows Server
PostgreSQL under Linux
However, other Microsoft SQL Server databases can be used under Windows.
The Java Runtime Environment is required on the central management station.
How to install the ServerView Operations Manager is explained in the following manuals: l l
Installing ServerView Operations Manager Software under Windows
Installing ServerView Operations Manager Software under Linux
Installation under Windows 23
2 PRIMERGY server management
Managed servers
On the managed servers, ServerView Agents, ServerView CIM
Providers, or ServerView Agentless Service should be installed, which supply the information to the central management station. ServerView RAID Manager and
ServerView Update Agent should be also installed on the managed servers.
The installation of ServerView Agents on virtual machines
(VMs) is not released.
l l
The ServerView Agents are available for Windows, Linux, and Citrix XenServer.
ServerView CIM Providers are available for Windows,
Linux, and VMware ESXi.
ServerView Operations Manager currently only supports
ServerView CIM providers for VMware ESXi.
How to install them is explained in the following manuals: l l l l
ServerView Agents for Windows
ServerView Agents for Linux
Installing ServerView ESXi CIM Provider
ServerView CIM Providers for Windows, Linux, and
VMware ESXi
24 Installation under Windows
2.2 Installation on the central management station
2.2
Installation on the central management station
You have to install Operations Manager (incl. ServerView Update Manager) on a management station and thus of monitoring the PRIMERGY servers via PC or notebook with a standard Web browser. Furthermore you can install the Event
Manager on the central management station or on its own on another server.
To display CIM indications from VMware vSphere Hypervisor server (ESXi-Server) in Event Manager, you have to install Operations Manager on the same server.
You can install the Operations Manager on the following operating systems: l
Windows, SUSE Linux and Red Hat Linux
The Operations Manager software is supplied on the ServerView Suite DVD 2.
l l
An Installation Wizard is provided for installation under Windows. This covers the installation of Operations Manager, Update Manager, and Event
Manager. In addition, the Wizard permits separate installation of the
Operations Manager software on different servers.
Installation can also occur in the Windows command line mode.
A description of the installations on the management station can be found in
"Installing ServerView Operations Manager" on page 29
and in
Operations Manager software via the command line" on page 209 .
Installation under Linux is script-based and involves the installation of
Operations Manager, Update Manager, and Event Manager.
For a description of the installations, see the ServerView Operations
Manager Installation Guide for Linux.
2.3
Installation on the managed servers
The following components must be installed on the managed servers, which supplies information to the central management station: l
ServerView Agents, ServerView CIM Providers, or ServerView Agentless
Service
The ServerView Agents are available for Windows, Linux, and Citrix
XENServer. CIM providers are available for Windows, Linux, and VMware
Installation under Windows 25
2 PRIMERGY server management l l
ESXi. The installation is described in the "ServerView Agents for Windows",
"ServerView Agents for Linux", "ServerView CIM Providers for Windows,
Linux, and VMware ESXi" installation and user guides.
ServerView Agentless Service is available for Windows and Linux. The installation is described in the "ServerView Agentless Management" overview.
The ServerView System Monitor is installed automatically (via the
ServerView Agents installation) and allows you to monitor and check some server information locally on the server. A detailed description can be found in the "ServerView System Monitor" user guide.
ServerView update agent
To keep the managed servers up-to-date by Update Management functions the ServerView update agent must be installed on the managed servers.
How to do this is described in the "ServerView Update Management" user guide.
ServerView RAID Manager
The ServerView RAID is used to monitor and manage the RAID controllers integrated in PRIMERGY servers. A detailed description can be found in the
"RAID Management" user guide.
Additional installations
l
ServerView Online Diagnostics l
During installation of the ServerView Agents for Windows, Online Diagnostics is also installed. You can use Online Diagnostics to perform a series of hardware tests on a managed PRIMERGY server from the remote workstation.
When installing the ServerView Agents (for Windows) in Expert mode, you can choose whether to install additional components, including Asset CLI,
Configuration Tools, Prime Collect and ServerView System Monitor.
2.4
Integration options of Operations Manager
The use of standardized protocols and interfaces means that Operations
Manager can easily be integrated into other management systems. The
Operations Manager integration modules ensure the output of detailed
26 Installation under Windows
2.4 Integration options of Operations Manager information on the status of the PRIMERGY servers on the console of the connected management system. PRIMERGY servers can thus be managed with a central enterprise management console (Single Point of Administration).
Additional management functions such as network management, application management and software distribution can also be used without any problem for PRIMERGY servers.
Integration modules are available for the following management systems: l l l
IBM Tivoli TME 10™ Framework TE/C
IBM Tivoli NetView
HP OpenView Network Node Manager l l l
HP Operations Manager
Microsoft MOM and SCOM 2007
Microsoft SMS and SCCM 2007 l l
Nagios and BMC Patrol
VMWare vCenter 5.1
l
PRIMEPOWER ServerView Suite
Some integration modules (e.g. Microsoft SMS, MOM) are provided on the
ServerView Suite DVD 2 and can be automatically installed on the management station when the Operations Manager software is installed. This is provided that the relevant management software is already installed on the system. The description of this is provided in
"Menu-driven installation of Operations Manager software" on page 140
.
The other integration modules (e.g. HP Operations Manager, IBM Tivoli TME
NetView) are available on the special ServerView Integration CD.
For more information on the integration modules, see the corresponding integration manuals and the data sheet "ServerView Integration".
Installation under Windows 27
28 Installation under Windows
3 Installing ServerView Operations
Manager
This chapter describes how to install Operations Manager (including ServerView
Update Manager) and Event Manager on the management station under
Windows operating systems.
l l
If Update Manager (up to version 4.71) is already installed on the management station, it must be uninstalled before installation of the Operations Manager software, otherwise the installation will abort.
If ServerView Agents are installed on the management station, you must install the current ServerView Agents before installing
Operations Manager.
The relevant software is supplied on the ServerView Suite DVD 2.
The products can be installed together on a central management station, or separately on different computers.
An upgrade installation is only supported from an existing Operations
Manager version 6.00.06.
All Operations Manager versions < 6.00.06 must first be upgraded to version 6.00.06.
Installation under Windows is user-friendly and menu-driven and is based on the
Microsoft Windows Installer Technology (see
Operations Manager software" on page 140 ).
Installation can also occur in the Windows command line mode. An editable script for installation without a dialog - silent installation - is provided for this purpose (see
"Installing Operations Manager software via the command line" on page 209
).
Installation under Windows 29
3 Installing ServerView Operations Manager
3.1
ServerView Operations Manager components
ServerView Operations Manager installation
When you install ServerView Operations Manager, the following ServerView components are also automatically installed:
ServerView Configuration Manager
With ServerView Configuration Manager, you can make system-dependent configurations on a managed server. (Only supported for servers on which the ServerView Agents are installed.)
ServerView Archive Manager
With Archive Manager you can record system and operating data of
PRIMERGY servers and store it centrally. This data can then be checked and evaluated.
ServerView Inventory Manager
With Inventory Manager you can retrieve data of a managed server or multiple servers and display it on the screen. You can also export the data from Operations Manager and store it in various formats (e.g. CSV, ODBC).
ServerView Performance Manager
With Performance Manager you can monitor the performance of specific server components. Performance Manager works on the basis of rules. The centrally created rules can be executed on any number of servers.
ServerView Threshold Manager
With Threshold Manager you can monitor one or more managed PRIMERGY servers and any virtual machines running on them centrally from the management station on the basis of threshold values.
ServerView Remote Management Frontend
ServerView Remote Management Frontend provides a Web-based work environment for the remote management of PRIMERGY servers.
30 Installation under Windows
3.1 ServerView Operations Manager components
ServerView Update Manager installation
When you install Update Manager, the following ServerView Operations
Manager components are also installed:
Update Manager
With Update Manager you can install and update software across an entire domain via a central management station.
Repository Manager
With Repository Manager you can manage the update repository.
Download Manager
With Download Manager you can conveniently obtain the latest statuses of firmware, BIOS, drivers and ServerView Agents for your servers.
Configuration
With Configuration you can set global parameters for Update Manager.
ServerView Event Manager installation
When you install Event Manager, the following ServerView Operations Manager components are also installed:
Alarm Monitor
Alarm Monitor displays all incoming alarms for the selected servers and server groups in the Operations Manager main window.
Alarm Configuration
The Alarm Configuration component lets you define settings for alarm handling. You can define alarm rules, filter rules and general settings.
Installation under Windows 31
3 Installing ServerView Operations Manager
3.2
JBoss Web server
As of ServerView Operations Manager version 5.0, the Microsoft Web server (MS Internet Information Server) and the ServerView Web server
(based on Apache for Windows) are no longer supported.
As of ServerView Operations Manager version 5.0, the Web server used is JBoss.
The necessary files for JBoss are automatically installed when the Operations
Manager software is installed. JBoss is configured as a standalone service
ServerView JBoss Application Server 7, which you can start and stop via the
Windows start menu:
Select Administrative Tools – Services
You can also start and stop the service via the following command:
%WINDIR%\system32\net.exe start "ServerView JBoss Application Server
7"
%WINDIR%\system32\net.exe stop "ServerView JBoss Application Server 7"
Automatic deletion of JBoss access logs
Log files localhost_access_log.<YYYY-MM-DD>.log are written in the directory
<installation_path>/jboss/standalone/log. A separate log is created for each day. In previous versions they were never deleted.
32 Installation under Windows
3.2 JBoss Web server
As of version 5.10, JBoss now includes automatic deletion. In the directory
<installation_path>/jboss/standalone/svconf the sv-com-config.xml configuration file describes the parameters:
<ns0:fileNamePrefix>localhost_access_log.</ns0:fileNamePrefix>
List of file name prefixes, qualifying the files that are to be checked for deletion. The default is a list with the single entry "localhost_access_log.".
<ns0:testInterval>12:00</ns0:testInterval>
Test interval, measured in minutes. The test interval can range between 1 minute and 24 hours. The behavior of the automated file deletion depends on the specified value:
Number [1...1439]
File checking begins when JBoss starts up, and is repeated at the specified time interval.
Time [hh:mm]
The test interval is 24 hours and the file checking occurs every day at the specified time. (The values for hh range from 00 till 23.) The default is 12:00, i.e. files are checked every day at noon.
<ns0:maxAge>10080</ns0:maxAge><!-- one week -->
Maximum age of a log file, measured in minutes. Any file matching an entry in the fileNamePrefix list which is older than this value is deleted. The default is 10080, i.e. seven days. If no value is specified in the configuration file, the value 4320, i.e. three days, is used.
Installation under Windows 33
3 Installing ServerView Operations Manager
3.2.1
Calling and ports used
The entry address of the Operations Manager begins with the prefix https.
Port
3169
3170
3171
3172
Used for
http (When trying to access this port, Operations
Manager versions older than V4.92 are automatically redirected to port 3170.) https (The port must be unlocked in the firewall.)
By default, TLS v1.1, TLS v1.2, and SSLv2Hello are supported.
Update Management (The port must be unlocked in the firewall to allow Update Management.)
Remote Connector Service (Server Configuration
Manager, Power Monitor, etc.) (The port must be unlocked in the firewall.)
ServerView RAID Manager
JBoss (only used for internal socket connections)
3173
1325, 9999
Some additional ports are used for dynamical assignment of system components.
1473
1474
9212
9363 non-SSL port of ServerView’s directory service
(ApacheDS)
LDAPS, if ApacheDS is configured as directory service.
PostgreSQL database server (only for Linux) used by the Operations Manager to contact XEN daemons used by the KVM service 16509, 16514
For detailed security information see the White Paper “Secure PRIMERGY Server
Management“.
34 Installation under Windows
3.2 JBoss Web server
To gather information, Operations Manager accesses the following ports of all network nodes of a subnet which is specified on ServerBrowser and managed servers.
Port
80
135
161
443
623
3172
5988
5989
9363
16509
16514
Used for
Citrix
Hyper-V
SNMP
VMware
BMC (iRMC)
ServerView Remote Connector
VMware
VMware
XEN
KVM
KVM
3.2.2
Role-based user administration
JBoss also enables role-based user administration. For further information on managing certificates, see "User Management in ServerView" user guide.
3.2.3
Managing certificates
To communicate with the JBoss Web server, Web browsers always use an HTTPS connection (i.e. a secure SSL connection). Therefore, the JBoss Web server needs a certificate (X.509 certificate) to authenticate itself at the Web browser. The
X.509 certificate contains all the information required to identify the JBoss Web server plus the public key of the JBoss Web server.
For further information on managing certificates, see "User Management in
ServerView" user guide.
Installation under Windows 35
3 Installing ServerView Operations Manager
3.3
Web browser
A Web browser is required to display the data. This means that the data can be transmitted via a LAN to any other computer that has a Web browser and displayed there. The browser must be able to interpret HTML V3.2 and Javascript
V1.1.
If you should experience problems when accessing the Web server, make the following settings in the browser: l
Disable the access option for the use of a proxy entirely in the browser, or l
Enter the IP address at an appropriate position to specify that no proxy is to be used for the host on which the Web server is running.
3.4
Administrative user "svuser"
The password for the special administrative user svuser cannot be changed by the ApacheDS user interface. You can only change it locally in the Operations
Manager Installation Wizard: l
During a new installation, enter the password in the Administrative User
Password window,
"Menu-driven installation of Operations Manager software" on page 140
.
l
For an existing installation execute a modify installation (see
"Modify installation of Operations Manager software" on page 161
) and change the password in the ApacheDS Administrative User window,
"Menu-driven installation of Operations Manager software" on page 140
.
36 Installation under Windows
3.5 ServerView Status gadget for Windows Vista and Windows 7
3.5
ServerView Status gadget for Windows Vista and
Windows 7
If Windows Vista or Windows 7 is installed on a standard PC, a ServerView status gadget is offered. This gadget allows you to display the number of servers in the different status situations. Via a link you can start the ServerView Operations
Manager.
Installation
You can install the gadget in one of the following ways: l
Double-click the StatusGadget.gadget file.
l
This file is located on the ServerView Suite DVD 2 in the following directory:
SVSSoftware/Software/ServerView/Windows/ServerView_
S2/StatusGadget
Via the ServerView Suite DVD 2.
Execute the file StatusGadget.gadget.
This file is located under ServerView Suite – Operations Manager.
If the status gadget is already installed, you will be asked whether you want to replace the current version.
Configuration
After installation the following dialog is displayed:
Installation under Windows 37
3 Installing ServerView Operations Manager
Figure 1: ServerView status gadget - start dialog
For connecting to a ServerView Operations Manager installation (on a central management station) you need to enter the corresponding URL. By clicking the tool icon (see figure above) you start the SV Status Gadget dialog to enter the
URL.
Figure 2: SV Status Gadget dialog
38 Installation under Windows
3.5 ServerView Status gadget for Windows Vista and Windows 7
After this, the name of the central management station is displayed as a link in the status gadget, see figure below. Via this link you can start the ServerView
Operations Manager which is located on this central management station.
Figure 3: ServerView status gadget
The icons identifies the status of the servers. The meaning of the icons is explained in the "ServerView Operations Manager" user guide.
Opening the status gadget
If you have closed the gadget, you can reopen it as follows:
1. Right-click anywhere on the desktop.
2. Select Gadget.
3. On the displayed gadget overview, select the ServerView status gadget.
4. Select Add from the context menu.
After reopening the gadget, you will need to configure it again, see
.
Opening multiple status gadgets
You can open more than one status gadget. This allows you to display the number of servers in the different status situations from different central management stations.
Installation under Windows 39
3 Installing ServerView Operations Manager
Uninstalling the status gadget
To uninstall the gadget proceed as follows:
1. Right-click anywhere on the desktop.
2. Select Gadget.
3. On the displayed gadget overview, select the ServerView status gadget.
4. Select Uninstall from the context menu.
40 Installation under Windows
3.6 Preparations and important steps before you start the installation
3.6
Preparations and important steps before you start the installation
Make sure that the following tasks have been completed before you start installing the Operations Manager software: l l
Install a Windows operating system (Windows Server 2008 or Windows
Server 2012) on the management station.
Service Pack Application: Apply Service Pack to all servers and computers in which ServerView components are installed if necessary. It is recommended to apply Service Pack 2 for Windows Server 2008 and Service Pack 1 or later for Windows Server 2008 R2.
l l l l
Make sure to apply the Service Pack. If the Service Pack is not applied, the operation is not guaranteed. If the Service Pack has been already applied, it does not need to reapply.
Before applying the Service Pack, make sure that the SNMP service is installed.
Set up the SNMP service on the management station. Therefore you must specify which communities and servers (IP addresses) the management station is to receive traps from, see
"Install the SNMP service" on page 42
.
Install Java Runtime Environment on the management station, see
"Installing Java Runtime Environment" on page 43
.
Set up a non-administrative user account for the JBoss application server which is installed with the ServerView Operations Manager. During the installation you have to specify the account in the JBoss Service Logon
Information window.
ServerView Operations Manager requires an SQL Server in which to install its
SQL database, see
"Installation options for SQL Server" on page 43 .
Operations Manager checks whether a suitable SQL Server instance is installed. If no suitable SQL Server instance is found, you can install SQL
Server 2008 R2 or SQL Server 2005 Express automatically with Operations
Manager.
Installation under Windows 41
3 Installing ServerView Operations Manager
3.6.1
Install the SNMP service
Windows Server 2008/2012
1. Install the SNMP service on the server:
1. Start the Server Manager.
2. On Windows Server 2012 start the Add Roles and Features Wizard.
On Windows Server 2008 click in the left window Features and then select Add Features.
3. Select the option SNMP Services.
4. Click Next and then Install.
2. Configure the SNMP service on the server as follows:
The default community name is public. This default entry is used by most SNMP services. For security reasons, we recommend that you change this entry. In principle you can define an individual community for each server or server group. Remember to make corresponding changes on the manager. If you want to use the entire range of ServerView functions, you must assign read-write rights to the community. You can restrict access to certain functions by assigning (read-only) access rights to them.
1. Select Administrative Tools – Services – SNMP Service.
2. Select Properties from the context menu.
3. Click Traps.
4. Enter the community name under Community Name, e. g. public.
5. Click add to list.
6. Click Add.
7. Enter the IP address of the management station for the chosen community and then click the Add button. Traps are only sent to the management stations entered here.
8. Click Security and set the Rights for the specified community to e.g.
READ WRITE. Confirm your new settings with OK.
42 Installation under Windows
3.7 Installation options for SQL Server
9. Specify the computer from which SNMP packets will be accepted by selecting the relevant option.
10. Click OK to finish the configuration.
3.6.2
Installing Java Runtime Environment
You can install JRE via the ServerView Suite DVD 2. Proceed as follows:
1. Place the ServerView Suite DVD 2 in the DVD-ROM drive. If the DVD does not start automatically, click the start.html file in the DVD’s root directory.
2. Mark the option Select ServerView Software Products.
3. Click Start.
4. Select the desired language in the displayed window.
5. Select Java.
6. Now click the appropriate *.exe to install.
You can also download the latest version of JRE via the Oracle Software
Downloads website.
If the message
Java has discovered application components that could indicate a security concern appears, after starting a Operations
Manager component, answer with No. To avoid this, set the following in the Java
Control panel:
1. Select Control Panel – Java.
2. In the Java Control Panel dialog box change to the Advance tab.
3. Under Mixed code (sandboxed vs. trusted) security verification activate the Enable - hide warning and run with protections option.
3.7
Installation options for SQL Server
Operations Manager requires an SQL Server in which to install its SQL database
ServerViewDB.
During the installation of Operations Manager, an SQL Server can, under certain conditions, be installed automatically. But in some cases, which are described in the following sections, you must install SQL Server yourself before installing
Operations Manager.
Installation under Windows 43
3 Installing ServerView Operations Manager
Optionally, an SQL Server that is already on the system and is suitable for
Operations Manager, can be used and selected during the installation.
In any case, a number of important installation requirements and constraints must be observed.
Microsoft SQL Server Express edition is suited for monitoring less than
200 servers.
To monitor 200 or more servers, we recommend you to install a full edition of Microsoft SQL Server.
Parallel (side-by-side) installation of SQL Server
SQL Server can be installed up to 16 times in parallel, always under a different instance name, in any edition on the same system.
Suitable instances for ServerView Operations Manager must comply with the following restrictions: l
For SQL Server full editions, any instance name is valid.
l
For SQL Server free (Express) editions, the instance name must be
“SQLSERVERVIEW”.
An SQL Server instance can contain several databases.
Operations Manager will install its database “ServerViewDB” in the SQL Server instance selected by you during the Operations Manager installation.
The name of the ServerView Operations Manager database is always
ServerViewDB.The database name is fixed and cannot be selected during the ServerView Operations Manager setup. As the database name is always unique, it is not possible to install Operations Manager on multiple local management stations and to use the same remotely installed SQL Server instance for each.
CAUTION!
The name of the ServerView Operations Manager database must never be changed.
Otherwise, Operations Manager applications cannot access the database anymore and installation errors may occur in subsequent upgrade or new installations.
44 Installation under Windows
3.7 Installation options for SQL Server
Instances of different SQL Server versions may be installed side-by-side on the same system.
For general information regarding side-by-side installation of all versions, please also refer to the corresponding chapter in SQL Server Books Online from
Microsoft: "Work with multiple instances and versions of SQL Server".
For SQL Server 2008 and 2008 R2, some additional hints apply, which are documented in the article "Considerations for side-by-side instances of SQL Server
2008 and SQL Server 2008 R2". Both articles mention internal version numbers used by SQL Server which are useful for understanding side-by-side concepts.
The following internal version numbers are used by SQL Server versions that are supported by ServerView Operations Manager: l
SQL Server 2005: 9.00
l l l l
SQL Server 2008: 10.00
SQL Server 2008 R2 : 10.50
SQL Server 2012: 11.00
SQL Server 2014: 12.00
Installations of different language versions of SQL Server instances on the same system are not supported:
Example
SQL Server 2005 (English) and SQL Server 2005 (German) as sideby-side installations on the same system are not supported.
If a non-English SQL Server instance is already installed on the system, Operations Manager cannot automatically install the standard English SQL Server in parallel. In this case a dialog box opens, prompting you to manually install an SQL Server in the appropriate language version.
Displaying the existing instances
You can display existing instances of SQL Server as follows:
1. Open the input prompt.
2. Enter the following command: sqlcmd -L | findstr -i <computer_name>
Installation under Windows 45
3 Installing ServerView Operations Manager
All installed SQL Server instances on the system <computer_name> are displayed. Bear in mind that it can take several minutes for this command to execute.
You can install Operations Manager if there are fewer than 16 instances on the system.
The version and language of the instances can be queried via commands, see
"Important information in the event of an error" on page 201
.
General information on SQL Server instance names
A single instance does not require an instance name and is designated the default instance. This default instance appears in the selection lists under the name (local) or, for a remote server, under that server’s computer name. The other 15 instances require unique instance names. They are referred to as named instances. SQL Server Express is often installed with an instance name that appears in selection lists under the name <server_name>\<instance_
name>.
Language version and operating system language of SQL Server
SQL Server is available in various language versions. You must install an SQL
Server version whose language is compatible with that of the operating system.
l
The English version of SQL Server can be installed on all supported operating systems. We suggest installing English SQL Server on western European
Windows operating systems.
l
Alternatively you can install SQL Server in the same language as your operating system.
Verify that the disk where the SQL Server will be installed is uncompressed.
Authentication mode
l
Operations Manager uses only Windows authentication mode to connect to
SQL Server.
l
If not otherwise needed, it is recommend to install SQL Server with Windows
Authentication mode only. This is the default setting in the SQL Server setup and is also recommended by Microsoft.
46 Installation under Windows
3.7 Installation options for SQL Server l
If you choose mixed mode (Windows Authentication and SQL Server authentication), please read the hints from Microsoft regarding authentication mode in SQL Server.
3.7.1
Locally on the management station
SQL Server can be installed locally on the management station or automatically by Operations Manager.
Suitable SQL Server instances for Operations Manager are: l
SQL Server Express editions with instance name SQLSERVERVIEW.
SQL Server 2008 R2 Express can be installed as part of the
ServerView Operations Manager installation on Windows Server
2012.
SQL Server 2005 Express can be installed as part of the ServerView
Operations Manager installation on Windows Server 2008.
l
SQL Server full editions (Enterprise/Standard or Workgroup where available) with any instance name or as an unnamed instance.
The Workgroup Edition was discontinued by Microsoft for SQL
Server 2012 and higher.
Side by Side installations of different SQL Server versions on the system are supported as defined by Microsoft.
For general information regarding side-by-side installation of all versions, please also refer to the corresponding chapter in SQL
Server Books Online from Microsoft: "Work with multiple instances and versions of SQL Server".
Recognition of SQL Server instances during Operations Manager installation
An SQL server is provided on the ServerView Suite DVD 2. You can automatically install this SQL Server instance as well during installation of the Operations
Manager software if no or no suitable SQL Server instance is installed on the system.
The automatically installed SQL Server is given the SQL Server instance name
SQLSERVERVIEW.
Installation under Windows 47
3 Installing ServerView Operations Manager
If a suitable SQL Server instance for Operations Manager is already available, the automatic installation of SQL Server is not offered. You can choose one of the existing SQL Server instances from a selection list and install the ServerView database there.
For more information on installing SQL Server 2014 or SQL Server 2014 Express, see
"SQL Server 2014" on page 51 .
For more information on installing SQL Server 2012 or SQL Server 2012 Express, see
"SQL Server 2012" on page 61 .
For more information on installing SQL Server 2008(R2) or SQL Server 2008 (R2)
Express, see
"SQL Server 2008 (R2)" on page 73
.
For more information on installing SQL Server 2005 or SQL Server 2005 Express, see
"SQL Server 2005" on page 84 .
3.7.2
Remotely on a different system
You can also use a remotely installed SQL Server instance to install the
ServerView database into it.
l l
Operations Manager must not be simultaneously installed locally on the remote server.
It is not possible to install Operations Manager on multiple local management stations and use the same remotely installed SQL
Server instance for each.
Requirements
The local management station and the remote system must belong to the same domain or to two domains with a two way trust relationship. You need at least one domain user account in the Domain Users group.
A suitable SQL Server instance is SQL Server 2014, SQL Server 2012, SQL Server
2008 R2, or SQL Server 2008/2005 in Standard, Workgroup (where available) or
Enterprise Edition. It must be installed and configured on the remote server before Operations Manager is installed.
For more information on configuring SQL Server for use as a remote SQL Server, see
"Configuring a remote SQL Server" on page 92 .
48 Installation under Windows
3.7 Installation options for SQL Server l l
Side by Side installations of different SQL Server versions on the system are supported as defined by Microsoft.
For general information regarding side-by-side installation of all versions, please also refer to the corresponding chapter in SQL
Server Books Online from Microsoft: "Work with multiple instances and versions of SQL Server".
SQL Server Express is not supported.
Microsoft SQL Server 2012/2014 Command Line Utilities
The use of a remote SQL Server requires the SQL Server command line tools
sqlcmd and bcp on the management station.
If these commands are not available, the Microsoft SQL Server 2012
Command Line Utilities software is automatically installed.
As a prerequisite the Microsoft SQL Server 2012/2014, Native Client is installed beforehand.
3.7.3
Installing SQL Server on a domain controller
For security reasons, whenever possible, do not install SQL Server on a domain controller.
SQL Server installation is not supported on a Read Only Domain
Controller.
Please note the order of installation:
1. First promote the server to a domain controller.
2. Then install SQL Server and ServerView Operations Manager.
Proceed as follows:
1. Assign a static IP address to this computer.
2. Log on as a local administrator.
3. Select Start – Run.
4. Under Open, type dcpromo and then click OK. Run the Active Directory
Installation Wizard.
5. Log on to the server as a domain administrator.
Installation under Windows 49
3 Installing ServerView Operations Manager
6. Install SQL Server, for example Workgroup/Standard/Enterprise Edition.
SQL Server service accounts should run as Windows domain user accounts.
Run separate SQL Server services under separate Windows accounts. On a domain controller the SQL Server services cannot run as Local Service or
Network Service. You can also install SQL Server service accounts to run as
Local System. This option is not recommended.
7. Install ServerView Operations Manager.
You can still change the service-account assignment after the installation using the SQL Server Configuration Manager, for example for the Express Edition.
Do not change the role of the server after you have installed SQL
Server.
For example, if you install SQL Server on a member server, do not use the Active Directory Installation Wizard (dcpromo.exe) tool to promote the server to a domain controller.
Or, if you install SQL Server on a domain controller, do not use the
Active Directory Installation Wizard to demote the server to a member server. Changing the role of a server after you install SQL Server can cause loss of functionality and is not supported.
3.8
Setting SQL Server memory option
On Windows, ServerView Operations Manager uses Microsoft SQL Server as the database server. Microsoft SQL Server has a server property max server memory which defines the upper limit of memory used by the buffer pool of the Microsoft
SQL Server Database Engine.
By default, this value is set to 2147483647 MB and Microsoft SQL Server will change its memory requirements dynamically based on available system resources.
But you can also set SQL Server memory options manually and restrict the amount of memory that SQL Server can access to a lower limit. This may be desirable when system administrators want to configure an instance of SQL
Server in conjunction with the memory requirements of other applications that run on the same computer.
50 Installation under Windows
3.9 SQL Server 2014
For this purpose, therefore, ServerView Operations Manager offers a Windows batch file as a utility tool. The batch file sets the max server memory option in the Microsoft SQL Server instance that Operations Manager uses according to customer input.
l
Open a command prompt window.
l
Find out <DllPath> and switch to the directory: type %windir%\ServerViewDB.ini | findstr -i DllPath= l cd /d <DllPath>\Tools
Execute the tool:
SVConfigSQLMaxMemSize.bat
The max server memory value may be set within a range of 32 to 2147483647
MB. These limits are offered and checked by the tool. The default value if nothing is specified is 64 MB.
Please be aware that the server property max server memory should only be changed with care and with regard to system and application load. From test observations, a setting of 64 MB seems to be enough when there are about ten normally-running servers registered in the server list.
Please observe the required permissions in MS SQL Server, especially when the
ServerView Operations Manager was installed without SQL Server “sysadmin” access:
Changing the max_server_memory option requires permissions held by the sysadmin (or serveradmin) fixed server roles. It is therefore required to execute the utility tool from an account which is a member of the "sysadmin" server role in MS SQL Server.
3.9
SQL Server 2014
You can install the ServerView database into an SQL Server 2014 instance on a
Windows Server 2008 or later operating system version.
SQL Server 2014 must be installed before installing Operations
Manager.
Installation under Windows 51
3 Installing ServerView Operations Manager
3.9.1
Hardware and software requirements
3.9.1.1
Hardware requirements
For a detailed overview of the hardware requirements for installing SQL Server
2014, please refer to http://msdn.microsoft.com
, and quick-search the website for "Hardware and Software Requirements for installing SQL Server 2014"
3.9.1.2
Software requirements
l
Operating systems supported for SQL Server 2014:
Windows Server 2012 R2
Windows Server 2012 l
Windows Server 2008 R2 SP1
Windows Server 2008 SP2
Microsoft .NET Framework 3.5 SP 1 and .NET Framework 4.0
For details on how to acquire these packages for the relevant operating system, please refer to http://msdn.microsoft.com
, and quick-search the website for "Hardware and Software
Requirements for installing SQL Server 2014".
l
Windows PowerShell 2.0 is required for installing Database Engine components and SQL Server Management Studio, which is a database administration software.
o o
For details on how to install and enable SQL Management Studio, please refer to the website mentioned above.
On Windows Server 2008 R2 SP1 PowerShell 2.0 comes with the operating system. You find it in All Programs – Accessories – Windows
PowerShell.
For Windows Server 2008 SP2 search in Microsoft Download Center for
Windows PowerShell 2.0 and download it. Two different packages exist. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package. Install the required package.
52 Installation under Windows
3.9 SQL Server 2014 o o
In case of Windows Server 2012:
Windows Power Shell 3.0 is part of the Windows Server 2012 installation.
In case of Windows Server 2012 (R2):
Windows Power Shell 4.0 is part of the Windows Server 2012 installation.
3.9.2
Editions
You can use the following editions, among others, depending on your performance requirements and budget: l
Express Edition
SQL Server 2014 Express is the successor to SQL Server 2012 Express. SQL
Server 2014 Express is free and available from the Microsoft Download
Center. The database size limit for SQL Server 2014 Express is 10 GB.
The full versions are: l
Standard Edition l
Enterprise Edition
SQL Server is available in 32-bit and 64-bit editions.
Please note limitations and recommendations for using SQL Server
Express editions with ServerView Operations Manager (see
"Installation options for SQL Server" on page 43
).
3.9.3
Setting up a service account
If you want to execute an "Operations Manager installation without SQL Server
"sysadmin" access", see
"Overview of Windows accounts and access rights" on page 101
and
"Setting up a service account" on page 53 .
For more information of setting up a service account see the section
"Setting up a service account" on page 74
under
"SQL Server 2008 (R2)" on page 73
.
3.9.4
Installing SQL Server 2014 Express edition
SQL Server 2014 Express is a free edition of SQL Server. You can download these editions from the Microsoft Download Center. More information on installing SQL
Installation under Windows 53
3 Installing ServerView Operations Manager
Server 2014 Express is available from the Microsoft Download Center.
It is recommended that you always use the latest service pack.
Downloading the files from the Microsoft Download Center
1. Go to the Microsoft Download Center: http://www.microsoft.com/downloads
2. In the field Search Download Center enter Microsoft SQL Server 2014
Express and press Enter or click the Search button. You can sort the downloads by release date.
3. In the displayed list, click the link Microsoft SQL Server 2014 Express.
4. Under Change language, select the appropriate language version.
5. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package.
6. The required packages are listed under Instructions:
Download the packages and install them.
7. Optional: Installation of Microsoft SQL Server 2014 Management Studio
Express. In Microsoft Download Center search for Microsoft SQL Server
2014 Management Studio and download it.
Eventually check all installation requirements as specified by Microsoft.
Installation
1. Log onto the system as administrator.
2. Execute the relevant *.exe file, e.g.: l
SQLEXPR_x64_ENU.exe
l
SQLEXPR_x86_ENU.exe
The installation is interactive. Only the entries required for Operations Manager are described below. Operations Manager only recognizes an SQL Server 2014
Express instance under the instance name SQLSERVERVIEW.
1. If you have a 64-bit operating system, select the entry Options in the left window pane, followed by the processor type x64.
2. Select Installation.
3. Select the entry New SQL Server stand-alone installation or add
features to an existing installation.
54 Installation under Windows
3.9 SQL Server 2014
4. In the Feature Selection window, leave the option Database Engine
Service selected, and deselect the options SQL Server replication and
SQL Client Connectivity SDK.
5. In the Instance Configuration window, enter the instance name
SQLSERVERVIEW under Named instance and Instance ID.
6. Specify the Windows user account under which you want SQL Server to run.
Select a suitable account as described in
"Setting up a service account" on page 74 .
7. In the Server Configuration window, select the startup type Automatic for the SQL Server Browser service.
8. In the Database Engine Configuration window, click the Add Current
User button.
This action adds SQL Server administrator rights to the current Windows user account.
You can start the Operations Manager installation under this account later.
If you want to execute an "Operations Manager installation without SQL
Server "sysadmin" access, at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL
Server.
9. In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts:
In to execute an "Operations Manager installation without SQL
Server "sysadmin" access, skip this step, follow the instructions as described in
1. The user account in the Operations Manager installation dialog Update
Management Logon Information.
2. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set).
3. The Local system account. Otherwise you will receive the following error message in the SQL Server error logs:
Installation under Windows 55
3 Installing ServerView Operations Manager
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason:
Failed to open the explicitly specified database
'ServerViewDB'.
Do not add the account of dialog JBoss Service Logon Information. This account will be granted permission during Operations Manager installation automatically.
You find the details for the required users for a local SQL Server 2014 in section
"Setting up a service account" on page 74
and for a remote SQL
Server 2014 in section
"Configuring a remote SQL Server" on page 92
.
10. By default, the TCP/IP network protocol is not activated for SQL Server
Express editions. This protocol is, however, necessary for the Operations
Manager database accesses. When you have installed SQL Server Express, therefore, you still need to activate this protocol before you start the
Operations Manager installation.
Proceed as follows to activate the TCP/IP network protocol:
1. Start the SQL Server Configuration Manager.
2. Under SQL Server Network Configuration, select the SQL Server instance name of your previously installed SQL Server instance.
3. Set the TCP/IP protocol to enabled.
You will need to restart the SQL Server service for this change to become effective.
3.9.5
Installing SQL Server 2014 Express Management Studio
On Windows Server 2012 proceed as follows:
1. Call Server Manager and add feature .NET Framework 3.5 SP1. This will require the Windows Server 2012 installation media (folder \sources\sxs).
2. Start the SQLManagementStudio installation executable.
3. Click Installation on the left side of the wizard.
4. Select New installation or add features to an existing installation and click the OK button
5. Click New installation or add shared features in the Installation Type dialog.
6. Accept the License Term.
56 Installation under Windows
3.9 SQL Server 2014
7. Let Management Tools – Basic selected on the Feature Selection page.The remaining installation dialogs are self-explanatory.
3.9.6
Installing SQL Server 2014 Enterprise/Standard edition
The packages Microsoft .NET Framework and Windows Power Shell will be installed automatically, if the management station is currently connected to the internet. Otherwise, you have to install the Microsoft .NET Framework and optionally - the Windows PowerShell before installing the SQL Server.
On Windows Server 2012, PowerShell 3.0 is already installed.
To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows:
1. Select Start – Server Manager.
2. In the left window pane, select Features.
3. Select Add Features.
4. Select the option Windows PowerShell.
5. Click Next and then Install.
Installation
1. Log onto the system as administrator.
2. Insert the installation medium (DVD).
3. Click the setup.exe file in the root directory.
The installation is interactive. Only the entries required for Operations Manager are described below. For the instance name you can use the default instance name or any other.
If the Microsoft .NET Framework is not yet installed: l l
In the Welcome to Setup window, accept the license agreement.
In the Setup Complete window, click Exit to start the update.
After the automatic installation of the required packages, the SQL Server
Installation Center starts.
1. If you have a 64-bit operating system, select Options in the left window pane, followed by the processor type x64.
Installation under Windows 57
3 Installing ServerView Operations Manager
2. Select the entry Installation.
3. Select the entry New SQL Server stand-alone installation or add
features to an existing installation.
4. In the Feature Selection window, select the option Database Engine
Service and Management Tools - Basic or Management Tools -
Complete.
5. In the Server Configuration window, click the option Use the same
account for all SQL Server services. If you are installing the SQL Server
2014 Edition on the same system as Operations Manager, enter a local
Windows user account without administrator authorization and a password.
In the case of a remote database, enter a domain user account without administrator authorization and a password, see
"Setting up a service account" on page 74 .
6. In the Server Configuration window, select the startup type Automatic for the services SQL Server Agent and SQL Server Browser.
7. In the Database Engine Configuration window, click the Add Current
User button. This action adds SQL Server administrator right to the current
Windows user account. Start later the Operations Manager installation under this account or add another account for the Operations Manager installation in the next step.
Start later the Operations Manager installation under this account.
In the case you want to execute an "Operations Manager installation without SQL Server "sysadmin" access" at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server.
8. In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts:
If you want to execute an "Operations Manager installation without
SQL Server "sysadmin" access, skip this step, follow the instructions as described in
"Overview of Windows accounts and access rights" on page 101 , and then return to
"Installing service packs" on page
here in this section.
58 Installation under Windows
3.9 SQL Server 2014
1. The user account in the Operations Manager installation dialog Update
Management Logon Information.
2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon
Information window for an upgrade installation.
3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set).
4. If you are using a local SQL Server, the Local system account.
Otherwise you will receive the following error message in the SQL
Server error logs:
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason:
Failed to open the explicitly specified database
'ServerViewDB'.
Do not add the account of dialog JBoss Service Logon Information. This account will be granted permission during Operations Manager installation automatically.
You find the details for the required users for a local SQL Server 2014 in section
"Setting up a service account" on page 74
and for a remote SQL
Server 2014 in section
"Configuring a remote SQL Server" on page 92
.
Installing service packs
Microsoft SQL Server 2014 may be used to upgrade any edition of SQL Server
2014.
If your SQL Server system has Internet access, you can update via the Microsoft
Update web page ( http://www.update.microsoft.com
): l
Click the Custom button to list the available updates.
Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance
( http://www.microsoft.com/downloads ):
1. In the field Search Download Center, enter SQL Server 2014 and press
Enter or click the Search button. You can sort the downloads by release date.
2. In the displayed list, click the current Service Pack (SQL Server 2014
Service Pack 1) link.
Installation under Windows 59
3 Installing ServerView Operations Manager
3. Under Change language select the appropriate language version.
4. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package.
5. Click DOWNLOAD to download the file.
6. In the window that opens, click Save and then select the storage location for the file.
Before you perform the update installation, you must stop all applications and services which are connected to the server instance. SQL Server Management
Studio and the Add or Remove Programs window must be closed.
1. Start the installation.
The installation is interactive and you can accept the default values.
2. On Windows Server 2008 mark in the Additional Information window the option Launch the User Provisioning Tool. The updated components are shown in the Feature Selection window.
3. After the installation, the system is restarted.
For setting up high availability you can configure an automatic restart for the
ServerView services and SQL Server services. For more information see
"ServerView services" on page 167
.
3.9.7
Adding a user account with SQL Server administrator rights
User accounts can also be checked and added later via SQL Server Management
Studio.
Adding accounts must be done before the Operations Manager installation.
In SQL Server Management Studio you will find the authorized SQL Server administrators under Security – Server Roles – sysadmin and selection of
Properties from the context menu.
You can add a user account with SQL Server administrator rights as follows:
1. Check if the account to be added is already present in the list of valid SQL
Server logins.
To view the valid logins, select Security – Logins.
60 Installation under Windows
3.10 SQL Server 2012
2. If the account is not present:
1. Select New Login from the context menu.
2. On the General page, enter the name of the Windows user under
Login name or Name. You can keep the other settings.
3. Switch to the Server Roles tab.
4. Select sysadmin or System Administrators as the server role and click
OK.
3. If the user account is already present:
1. Select Security – Logins – <login>.
2. Select Properties from the context menu.
3. Switch to the Server Roles tab and select the sysadmin checkbox.
4. Then click OK.
3.10
SQL Server 2012
As of Operations Manager version 6.30, you can install the ServerView database into an SQL Server 2012 instance on a Windows Server 2008 or later operating system version.
SQL Server 2012 must be installed before installing Operations
Manager.
3.10.1
Hardware and software requirements
3.10.1.1
Hardware requirements
For a detailed overview of the hardware requirements for installing SQL Server
2012, please refer to http://msdn.microsoft.com
, and quick-search the website for "Hardware and Software Requirements for installing SQL Server 2012"
3.10.1.2
Software requirements
l
Operating systems supported for SQL Server 2012:
Windows Server 2012
Windows Server 2008 R2 SP1
Installation under Windows 61
3 Installing ServerView Operations Manager l
Windows Server 2008 SP2
Microsoft .NET Framework 3.5 SP 1 and .NET Framework 4.0
l l
For details on how to acquire these packages for the relevant operating system, please refer to http://msdn.microsoft.com
, and quick-search the website for "Hardware and Software
Requirements for installing SQL Server 2012".
Windows Installer as of version 4.5
Windows PowerShell as of version 2.0 is required for installing Database
Engine components and SQL Server Management Studio, which is a database administration software.
For details on how to install and enable SQL Management Studio, please refer to the website mentioned above.
Proceed as follows: l
In case of Windows Server 2008 SP2:
Search in the Microsoft Download Center for Windows Power Shell 2.0 and download it.
l l
In case of Windows Server 2008 R2:
Windows Power Shell 2.0 is part of the Windows Server 2008 R2 installation. (Select All Programs - Accessoires - Windows
PowerShell.)
In case of Windows Server 2012:
Windows Power Shell 3.0 is part of the Windows Server 2012 installation.
3.10.2
Editions
You can use the following editions, among others, depending on your performance requirements and budget: l
Express Edition
SQL Server 2012 Express is the successor to SQL Server 2008 Express. SQL
Server 2012 Express is free and available from the Microsoft Download
Center. The database size limit for SQL Server 2012 Express is 10 GB.
62 Installation under Windows
3.10 SQL Server 2012
The full versions are: l l
Standard Edition
Enterprise Edition
3.10.3
Setting up a service account
If you want to execute an "Operations Manager installation without SQL Server
"sysadmin" access", see
"Overview of Windows accounts and access rights" on page 101
and
"SQL Server service accounts" on page 63
.
3.10.3.1
Operations Manager service accounts
When you install SQL Server 2012, you will see instructions in the Database
Engine Configuration window on how to add Windows user accounts which will later be used as Operations Manager service accounts
By doing this, you will add SQL Server administrator rights to these accounts. You can also specify the Windows user accounts after SQL Server installation, but before Operations Manager installation. Follow the instructions in
"Adding a user account with SQL Server administrator rights" on page 83
.
Using a local SQL Server 2012 you must add the following Windows user accounts to SQL Server 2012: l
Account under which you will be logged on the system during the
Operations Manager installation.This account must have Windows administrative rights.
l l
Account in the Operations Manager installation window Update
Management Logon Information. This account must have
Windows administrative rights. Usually you will add the
Administrator account.
The Local System Account (NT AUTHORITY\SYSTEM). Locally,
ServerView Services will be installed to use this account.
3.10.3.2
SQL Server service accounts
When you install SQL Server 2012, you must specify a service account in the
Server Configuration window. It is advisable to set up one or more service accounts before the installation.
Installation under Windows 63
3 Installing ServerView Operations Manager
You require service accounts for the following services: l l
SQL Server Database Service
SQL Server Agent (not for SQL Server Express) l l
SQL Server Browser
Bear in mind the following if you are installing SQL Server and Operations
Manager on the same system:
Do not use the Network Service account.
l
The Operations Manager installation will be cancelled if SQL Server runs under the Network Service account.
To increase the security of the SQL Server installation, the services should run under a local Windows user account. Do not assign it to the administrator group. Local Windows user accounts have the lowest privileges.
l l
Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option activated and that they have strong passwords. Otherwise, follow the Microsoft documentation
"How to: Change the Password of the Accounts Used by SQL Server" if the
SQL Server is running under an account for which the password is to be changed.
There are, however, a few exceptions for using a local Windows user account: o o
If remote procedure calls, replication, backing up to network drives, and heterogeneous SQL joins that involve remote data sources are to be used on the server, a local Windows account is not sufficient.
In fail cluster installations, local system and local service accounts are not allowed.
If you do not want to set up a local Windows user account, you can use a system account. Proceed as follows: o o
Select Local System for the services SQL Server and SQL Server
Agent.
Select Local Service for the service SQL Server Browser.
64 Installation under Windows
3.10 SQL Server 2012
The local system account (Local System) is an integrated account with very high privileges. You should therefore use the system accounts with appropriate caution.
l
If you install SQL Server and Operations Manager on different systems, the
SQL Server services must run under a domain user account without administrator rights. Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option activated and that they have strong passwords. Otherwise, follow the Microsoft documentation "How to: Change the Password of the Accounts Used by SQL
Server" if the SQL Server is running under an account for which the password is to be changed.
After the SQL Server 2012 installation you can still assign service accounts later with the SQL Server Configuration Manager.
For more information on service accounts, see the SQL Server 2012 Books
Online.
3.10.4
Installing SQL Server 2012 Express edition
SQL Server 2012 Express is a free edition of SQL Server. You can download these editions from the Microsoft Download Center. More information on installing SQL
Server 2012 Express is available from the Microsoft Download Center.
It is recommended that you always use the latest service pack.
Downloading the files from the Microsoft Download Center
1. Go to the Microsoft Download Center: http://www.microsoft.com/downloads
2. In the field Search Download Center enter Microsoft SQL Server 2012
Express and press Enter or click the Search button. You can sort the downloads by release date.
3. In the displayed list, click the link Microsoft SQL Server 2012 Express
Edition.
4. Under Change language, select the appropriate language version.
5. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package.
Installation under Windows 65
3 Installing ServerView Operations Manager
6. The required packages are listed under Instructions:
Download the packages and install them.
7. Optional: Installation of Microsoft SQL Server 2012 Management Studio
Express:
The SQL Management Studio is also available via the SQL Server
2012 Express download page, which contains multiple packages.
You will be prompted to select the SQLManagementStudio package from the Details list. Download and install the package you need (x86 or x64).
Windows Power Shell is a prerequisite for the Management Studio.
On Windows Server 2012, PowerShell (PowerShell 3.0) is already installed.
Installation
1. Log onto the system as administrator.
2. Execute the relevant *.exe file, e.g.: l l
SQLEXPR_x64_ENU.exe
SQLEXPR_x86_ENU.exe
The installation is interactive. Only the entries required for Operations Manager are described below. Operations Manager only recognizes an SQL Server 2012
Express instance under the instance name SQLSERVERVIEW.
1. If you have a 64-bit operating system, select the entry Options in the left window pane, followed by the processor type x64.
2. Select Installation.
3. Select the entry New SQL Server stand-alone installation or add
features to an existing installation.
4. In the Feature Selection window, leave the option Database Engine
Service selected, and deselect the options SQL Server replication and
SQL Client Connectivity SDK.
5. In the Instance Configuration window, enter the instance name
SQLSERVERVIEW under Named instance and Instance ID.
6. Specify the Windows user account under which you want SQL Server to run.
Select a suitable account as described in
"Setting up a service account" on page 74 .
66 Installation under Windows
3.10 SQL Server 2012
7. In the Server Configuration window, select the startup type Automatic for the SQL Server Browser service.
8. In the Database Engine Configuration window, click the Add Current
User button.
This action adds SQL Server administrator rights to the current Windows user account.
You can start the Operations Manager installation under this account later.
If you want to execute an "Operations Manager installation without SQL
Server "sysadmin" access, at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL
Server.
9. In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts:
In to execute an "Operations Manager installation without SQL
Server "sysadmin" access, skip this step, follow the instructions as described in
1. The user account in the Operations Manager installation dialog Update
Management Logon Information.
2. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set).
3. The Local system account. Otherwise you will receive the following error message in the SQL Server error logs:
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason:
Failed to open the explicitly specified database
'ServerViewDB'.
Do not add the account of dialog JBoss Service Logon Information. This account will be granted permission during Operations Manager installation automatically.
You find the details for the required users for a local SQL Server 2012 in section
"Setting up a service account" on page 74
and for a remote SQL
Server 2012 in section
"Configuring a remote SQL Server" on page 92
.
Installation under Windows 67
3 Installing ServerView Operations Manager
10. By default, the TCP/IP network protocol is not activated for SQL Server
Express editions. This protocol is, however, necessary for the Operations
Manager database accesses. When you have installed SQL Server Express, therefore, you still need to activate this protocol before you start the
Operations Manager installation.
Proceed as follows to activate the TCP/IP network protocol:
1. Start the SQL Server Configuration Manager.
2. Under SQL Server Network Configuration, select the SQL Server instance name of your previously installed SQL Server instance.
3. Set the TCP/IP protocol to enabled.
You will need to restart the SQL Server service for this change to become effective.
3.10.5
Installing SQL Server 2012 Express Management Studio
On Windows Server 2012 proceed as follows:
1. Call Server Manager and add feature .NET Framework 3.5 SP1. This will require the Windows Server 2012 installation media (folder \sources\sxs).
2. Start the SQLManagementStudio installation executable.
3. Click Installation on the left side of the wizard.
4. Select New installation or add features to an existing installation and click the OK button
5. Click New installation or add shared features in the Installation Type dialog.
6. Accept the License Term.
7. Let Management Tools – Basic selected on the Feature Selection page.The remaining installation dialogs are self-explanatory.
68 Installation under Windows
3.10 SQL Server 2012
3.10.6
Installing SQL Server 2012 Enterprise/Standard edition
If the management station is currently connected to the internet, the packages Microsoft .NET Framework and Windows Power Shell will be installed automatically. Otherwise, you have to install the Microsoft
.NET Framework and - optionally - the Windows PowerShell before installing the SQL Server.
On Windows Server 2012, PowerShell 3.0 is already installed.
To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows:
1. Select Start – Server Manager.
2. In the left window pane, select Features.
3. Select Add Features.
4. Select the option Windows PowerShell.
5. Click Next and then Install.
Installation
1. Log onto the system as administrator.
2. Insert the installation medium (DVD).
3. Click the setup.exe file in the root directory.
The installation is interactive. Only the entries required for Operations Manager are described below. For the instance name you can use the default instance name or any other.
If the Microsoft .NET Framework is not yet installed: l
In the Welcome to Setup window, accept the license agreement.
l
In the Setup Complete window, click Exit to start the update.
After the automatic installation of the required packages, the SQL Server
Installation Center starts.
1. If you have a 64-bit operating system, select Options in the left window pane, followed by the processor type x64.
2. Select the entry Installation.
Installation under Windows 69
3 Installing ServerView Operations Manager
3. Select the entry New SQL Server stand-alone installation or add
features to an existing installation.
4. In the Feature Selection window, select the option Database Engine
Service and Management Tools - Basic or Management Tools -
Complete.
5. In the Server Configuration window, click the option Use the same
account for all SQL Server services. If you are installing the SQL Server
2012 Edition on the same system as Operations Manager, enter a local
Windows user account without administrator authorization and a password.
In the case of a remote database, enter a domain user account without administrator authorization and a password, see
"Setting up a service account" on page 74 .
6. In the Server Configuration window, select the startup type Automatic for the services SQL Server Agent and SQL Server Browser.
7. In the Database Engine Configuration window, click the Add Current
User button. This action adds SQL Server administrator right to the current
Windows user account. Start later the Operations Manager installation under this account or add another account for the Operations Manager installation in the next step.
Start later the Operations Manager installation under this account.
In the case you want to execute an "Operations Manager installation without SQL Server "sysadmin" access" at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL Server.
8. In the Database Engine Configuration window, click the Add button if installation is done with SQL Server "sysadmin" access. Add SQL Server administrator right to the following Windows user accounts:
If you want to execute an "Operations Manager installation without
SQL Server "sysadmin" access, skip this step, follow the instructions as described in
"Overview of Windows accounts and access rights" on page 101 , and then return to
"Installing service packs" on page
here in this section
1. The user account in the Operations Manager installation dialog Update
Management Logon Information.
70 Installation under Windows
3.10 SQL Server 2012
2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon
Information window for an upgrade installation.
3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set).
4. If you are using a local SQL Server, the Local system account.
Otherwise you will receive the following error message in the SQL
Server error logs:
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason:
Failed to open the explicitly specified database
'ServerViewDB'.
Do not add the account of dialog JBoss Service Logon Information. This account will be granted permission during Operations Manager installation automatically.
You find the details for the required users for a local SQL Server 2012 in section
"Setting up a service account" on page 74
and for a remote SQL
Server 2012 in section
"Configuring a remote SQL Server" on page 92
.
Installing service packs
Microsoft SQL Server 2012 may be used to upgrade any edition of SQL Server
2012.
If your SQL Server system has Internet access, you can update via the Microsoft
Update web page ( http://www.update.microsoft.com
): l
Click the Custom button to list the available updates.
Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance
( http://www.microsoft.com/downloads ):
1. In the field Search Download Center, enter SQL Server 2012 and press
Enter or click the Search button. You can sort the downloads by release date.
2. In the displayed list, click the current Service Pack (SQL Server 2012
Service Pack 1) link.
3. Under Change language select the appropriate language version.
Installation under Windows 71
3 Installing ServerView Operations Manager
4. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package.
5. Click DOWNLOAD to download the file.
6. In the window that opens, click Save and then select the storage location for the file.
Before you perform the update installation, you must stop all applications and services which are connected to the server instance. SQL Server Management
Studio and the Add or Remove Programs window must be closed.
1. Start the installation.
The installation is interactive and you can accept the default values.
2. On Windows Server 2008 mark in the Additional Information window the option Launch the User Provisioning Tool. The updated components are shown in the Feature Selection window.
3. After the installation, the system is restarted.
For setting up high availability you can configure an automatic restart for the
ServerView services and SQL Server services. For more information see
"ServerView services" on page 167
.
3.10.7
Adding a user account with SQL Server administrator rights
User accounts can also be checked and added later via SQL Server Management
Studio.
Adding accounts must be done before the Operations Manager installation.
In SQL Server Management Studio you will find the authorized SQL Server administrators under Security – Server Roles – sysadmin and selection of
Properties from the context menu.
You can add a user account with SQL Server administrator rights as follows:
1. Check if the account to be added is already present in the list of valid SQL
Server logins.
To view the valid logins, select Security – Logins.
72 Installation under Windows
3.11 SQL Server 2008 (R2)
2. If the account is not present:
1. Select New Login from the context menu.
2. On the General page, enter the name of the Windows user under
Login name or Name. You can keep the other settings.
3. Switch to the Server Roles tab.
4. Select sysadmin or System Administrators as the server role and click
OK.
3. If the user account is already present:
1. Select Security – Logins – <login>.
2. Select Properties from the context menu.
3. Switch to the Server Roles tab and select the sysadmin checkbox.
4. Then click OK.
3.11
SQL Server 2008 (R2)
As of Operations Manager version 5.10, you can install the ServerView database into an SQL Server 2008 R2 instance. The description for SQL Server 2008 also applies for SQL Server 2008 R2 in this manual.
As of Operations Manager version 4.90, you can install the ServerView database into an SQL Server 2008 instance.
If you are using Windows Server 2012, SQL Server 2008 R2 Express can be installed automatically with the ServerView installation. All other editions of SQL Server 2008 must be installed before Operations
Manager.
3.11.1
Software requirements
l l
Operating system for SQL Server 2008 R2:
Windows Server 2012
Windows Server 2008 and R2
Operating system for SQL Server 2008:
Windows Server 2012
Installation under Windows 73
3 Installing ServerView Operations Manager l l l
Windows Server 2008 and R2
Microsoft .NET Framework 3.5 SP 1 or .NET Framework 4.0
Windows Installer 4.5 or later version
Optional: Windows PowerShell 1.0 if you want to install SQL Server 2008
(R2) – Management Tools, a program for database administration.
3.11.2
Editions
You can use the following editions, among others, depending on your performance requirements and budget: l
Express Edition
Successor to SQL Server 2005 Express, SQL Server 2008 Express is free and available from the Microsoft Download Center. The database size limit is 10
GB for SQL Server 2008 R2 Express, 4 GB for SQL Server 2008 Express, and 4
GB for SQL Server 2005 Express. The newer edition can store more data than the older one.
The full versions are: l
Workgroup Edition l l
Standard Edition
Enterprise Edition
3.11.3
Setting up a service account
3.11.3.1
Operations Manager service accounts
If you want to execute an "Operations Manager installation without SQL Server
"sysadmin" access", see
"Overview of Windows accounts and access rights" on page 101
and
"SQL Server service accounts" on page 75
.
When you install SQL Server 2008, you will see instructions in the Database
Engine Configuration window on how to add Windows user accounts which will later be used as Operations Manager service accounts
By doing this, you will add SQL Server administrator rights to these accounts. You can also specify the Windows user accounts after SQL Server installation, but before Operations Manager installation. Follow the instructions in
"Adding a user account with SQL Server administrator rights" on page 83
.
74 Installation under Windows
3.11 SQL Server 2008 (R2)
Using a local SQL Server 2008 you must add two Windows user accounts to SQL Server 2008: l
Account under which you will be logged on the system during the
Operations Manager installation.This account must have Windows administrative rights.
l
Account in the Operations Manager installation window Update
Management Logon Information. This account must have
Windows administrative rights. Usually you will add the
Administrator account.
3.11.3.2
SQL Server service accounts
When you install SQL Server 2008, you must specify a service account in the
Server Configuration window. It is advisable to set up one or more service accounts before the installation.
You require service accounts for the following services: l l l
SQL Server Database Service
SQL Server Agent (not for SQL Server Express)
SQL Server Browser
Bear in mind the following if you are installing SQL Server and Operations
Manager on the same system: l
Do not use the Network Service account.
l
The Operations Manager installation will be cancelled if SQL Server runs under the Network Service account.
To increase the security of the SQL Server installation, the services should run under a local Windows user account. Do not assign it to the administrator group. Local Windows user accounts have the lowest privileges.
Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option activated and that they have strong passwords. Otherwise, follow the Microsoft documentation
"How to: Change the Password of the Accounts Used by SQL Server" if the
SQL Server is running under an account for which the password is to be changed.
Installation under Windows 75
3 Installing ServerView Operations Manager l l
There are, however, a few exceptions for using a local Windows user account: o
If remote procedure calls, replication, backing up to network drives, and heterogeneous SQL joins that involve remote data sources are to be used on the server, a local Windows account is not sufficient.
o
In fail cluster installations, local system and local service accounts are not allowed.
If you do not want to set up a local Windows user account, you can use a system account. Proceed as follows: o o
Select Local System for the services SQL Server and SQL Server
Agent.
Select Local Service for the service SQL Server Browser.
The local system account (Local System) is an integrated account with very high privileges. You should therefore use the system accounts with appropriate caution.
l
If you install SQL Server and Operations Manager on different systems, the
SQL Server services must run under a domain user account without administrator rights. Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option activated and that they have strong passwords. Otherwise, follow the Microsoft documentation "How to: Change the Password of the Accounts Used by SQL
Server" if the SQL Server is running under an account for which the password is to be changed.
After the SQL Server 2008 installation you can still assign service accounts later with the SQL Server Configuration Manager.
For more information on service accounts, see the SQL Server 2008 Books
Online.
3.11.4
Installing SQL Server 2008 (R2) Express edition
SQL Server 2008 R2 Express and SQL Server 2008 Express are free versions of SQL
Server. You can download these editions from the Microsoft Download Center.
More information on installing SQL Server 2008 Express is available from the
Microsoft Download Center.
76 Installation under Windows
3.11 SQL Server 2008 (R2)
It is recommended that you always use the latest service pack.
Downloading the files from the Microsoft Download Center
1. Go to the Microsoft Download Center: http://www.microsoft.com/downloads
2. In the field Search Download Center enter Microsoft SQL Server 2008
R2 Express or enter Microsoft SQL Server 2008 Express and press Enter or click the Search button. You can sort the downloads by release date.
3. In the displayed list, click the link Microsoft SQL Server 2008 R2 SP2 -
Express Edition or Microsoft SQL Server 2008 SP3 Express Edition.
4. Under Change language, select the appropriate language version.
5. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package.
6. The required packages are listed under Instructions:
Download the packages and install them.
7. Optional: In Microsoft Download Center search for Microsoft SQL Server
2008 Management Studio Express and install it if you want to install a program for database administration.
Windows Power Shell 1.0 is a prerequisite for the Management Studio.
On Windows Server 2012, PowerShell 1.0 is already installed.
To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows:
1. Select Start – Server Manager.
2. In the left window pane, select Features.
3. Select Add Features.
4. Select the option Windows PowerShell.
5. Click Next and then Install.
Installation
1. Log onto the system as administrator.
2. Execute the relevant *.exe file, e.g.: l
SQLEXPR_x64_ENU.exe
Installation under Windows 77
3 Installing ServerView Operations Manager l
SQLEXPR_x86_ENU.exe
The installation is interactive. Only the entries required for Operations Manager are described below. Operations Manager only recognizes an SQL Server 2008
Express instance under the instance name SQLSERVERVIEW.
1. If you have a 64-bit operating system, select the entry Options in the left window pane, followed by the processor type x64.
2. Select Installation.
3. Select the entry New SQL Server stand-alone installation or add
features to an existing installation.
4. In the Feature Selection window, select the option Database Engine
Service and Management Tools - Basic.
5. In the Instance Configuration window, enter the instance name
SQLSERVERVIEW under Named instance.
6. In the Server Configuration window, click the option Use the same
account for all SQL Server services.
7. Specify the Windows user account under which you want SQL Server to run.
Select a suitable account as described in
"Setting up a service account" on page 74 .
8. In the Server Configuration window, select the startup type Automatic for the SQL Server Browser service.
9. In the Database Engine Configuration window, click the Add Current
User button.
This action adds SQL Server administrator rights to the current Windows user account.
You can start the Operations Manager installation under this account later.
If you want to execute an "Operations Manager installation without SQL
Server "sysadmin" access, at least one account must hold the sysadmin server role in the SQL Server. Use this account for administration of the SQL
Server.
10. In the Database Engine Configuration window, click the Add button. Add
SQL Server administrator right to the following Windows user accounts:
If you want to execute an "Operations Manager installation without SQL
Server "sysadmin" access, skip this step, follow the instructions as described
78 Installation under Windows
3.11 SQL Server 2008 (R2) in
"Overview of Windows accounts and access rights" on page 101
, and then return to step 11 here in this section.
1. The user account in the Operations Manager installation dialog Update
Management Logon Information.
2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon
Information window for an upgrade installation.
3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set).
Do not add the account of dialog JBoss Service Logon Information. This account will be granted permission during Operations Manager installation automatically.
You find the details for the required users for a local SQL Server 2008 in section
"Setting up a service account" on page 74
and for a remote SQL
Server 2008 in section
"Configuring a remote SQL Server" on page 92
.
11. By default, the TCP/IP network protocol is not activated for SQL Server
Express editions. This protocol is, however, necessary for the Operations
Manager database accesses. When you have installed SQL Server Express, therefore, you still need to activate this protocol before you start the
Operations Manager installation.
Proceed as follows to activate the TCP/IP network protocol:
1. Start the SQL Server Configuration Manager.
2. Under SQL Server Network Configuration, select the SQL Server instance name of your previously installed SQL Server instance.
3. Set the TCP/IP protocol to enabled.
You will need to restart the SQL Server service for this change to become effective.
3.11.5
Installing SQL Server 2008 R2 Express Management Studio
On Windows Server 2012 proceed as follows:
1. Call Server Manager and add feature .NET Framework 3.5. This will require the Windows Server 2012 installation media (folder \sources\sxs).
Installation under Windows 79
3 Installing ServerView Operations Manager
2. Start the SQLManagementStudio installation executable.
3. Click Installation on the left side of the wizard.
4. Select New installation or add features to an existing installation and click the OK button
5. Click New installation or add shared features in the Installation Type dialog.
6. Accept the License Term.
7. Let Management Tools – Basic selected on the Feature Selection page.The remaining installation dialogs are self-explanatory.
3.11.6
Installing SQL Server 2008 (R2)
Enterprise/Standard/Workgroup edition
In the manual the description for SQL Server 2008 also applies for SQL Server
2008 R2.
The packages Microsoft .NET Framework are automatically installed when you install the SQL Server 2008 Enterprise/Standard/Workgroup Edition.
On Windows Server 2012, PowerShell 1.0 is already installed.
To install Windows PowerShell as of version 2.0 on Windows Server 2008, proceed as follows:
1. Select Start – Server Manager.
2. In the left window pane, select Features.
3. Select Add Features.
4. Select the option Windows PowerShell.
5. Click Next and then Install.
Installation
1. Log onto the system as administrator.
2. Insert the installation medium (DVD).
3. Click the setup.exe file in the root directory.
80 Installation under Windows
3.11 SQL Server 2008 (R2)
The installation is interactive. Only the entries required for Operations Manager are described below. For the instance name you can use the default instance name or any other.
If the Microsoft .NET Framework is not yet installed: l
In the Welcome to Setup window, accept the license agreement.
l
In the Setup Complete window, click Exit to start the update.
After the automatic installation of the required packages, the SQL Server
Installation Center starts.
1. If you have a 64-bit operating system, select Options in the left window pane, followed by the processor type x64.
2. Select the entry Installation.
3. Select the entry New SQL Server stand-alone installation or add
features to an existing installation.
4. In the Feature Selection window, select the option Database Engine
Service and Management Tools - Basic or Management Tools -
Complete.
5. In the Server Configuration window, click the option Use the same
account for all SQL Server services. If you are installing the SQL Server
2008 Edition on the same system as Operations Manager, enter a local
Windows user account without administrator authorization and a password.
In the case of a remote database, enter a domain user account without administrator authorization and a password, see
"Setting up a service account" on page 74 .
6. In the Server Configuration window, select the startup type Automatic for the services SQL Server Agent and SQL Server Browser.
7. In the Database Engine Configuration window, click the Add Current
User button. This action adds SQL Server administrator right to the current
Windows user account. Start later the Operations Manager installation under this account or add another account for the Operations Manager installation in the next step.
Start later the Operations Manager installation under this account.
In the case you want to execute an "Operations Manager installation without SQL Server "sysadmin" access" at least one account must hold the
Installation under Windows 81
3 Installing ServerView Operations Manager sysadmin server role in the SQL Server. Use this account for administration of the SQL Server.
8. In the Database Engine Configuration window, click the Add button. Add
SQL Server administrator right to the following Windows user accounts:
If you want to execute an "Operations Manager installation without
SQL Server "sysadmin" access, skip this step, follow the instructions as described in
"Overview of Windows accounts and access rights" on page 101 , and then return to
"Installing service packs" on page
here in this section.
1. The user account in the Operations Manager installation dialog Update
Management Logon Information.
2. If you are using a remote SQL Server, the account in the Remote DB window for a new installation or the ServerView Service Logon
Information window for an upgrade installation.
3. The account of the SQL Server and the SQL Server Agent (if in the previous dialog Server Configuration the Local System account has not been set).
Do not add the account of dialog JBoss Service Logon Information. This account will be granted permission during Operations Manager installation automatically.
You find the details for the required users for a local SQL Server 2008 in section
"Setting up a service account" on page 74
and for a remote SQL
Server 2008 in section
"Configuring a remote SQL Server" on page 92
.
Installing service packs
Microsoft SQL Server 2008 Service Pack 3 (SP3) respectively Microsoft SQL Server
2008 R2 Service Pack 1 may be used to upgrade any edition of SQL Server 2008.
If your SQL Server system has Internet access, you can update via the Microsoft
Update web page ( http://www.update.microsoft.com
): l
Click the Custom button to list the available updates.
82 Installation under Windows
3.11 SQL Server 2008 (R2)
Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance
( http://www.microsoft.com/downloads ):
1. In the field Search Download Center, enter SQL Server 2008 and press
Enter or click the Search button. You can sort the downloads by release date.
2. In the displayed list, click the Microsoft SQL Server 2008 Service Pack 3 respectively Microsoft SQL Server 2008 R2 Service Pack 2 link.
3. Under Change language select the appropriate language version.
4. For a 32-bit system, download the x86 package, or for a 64-bit system, download the x64 package.
5. Click DOWNLOAD to download the file.
6. In the window that opens, click Save and then select the storage location for the file.
Before you perform the update installation, you must stop all applications and services which are connected to the server instance. SQL Server Management
Studio and the Add or Remove Programs window must be closed.
1. Start the installation.
The installation is interactive and you can accept the default values.
2. On Windows Server 2008 mark in the Additional Information window the option Launch the User Provisioning Tool. The updated components are shown in the Feature Selection window.
3. After the installation, the system is restarted.
For setting up high availability you can configure an automatic restart for the
ServerView services and SQL Server services. For more information see
"ServerView services" on page 167
.
3.11.7
Adding a user account with SQL Server administrator rights
User accounts can also be checked and added later via SQL Server Management
Studio.
Adding accounts must be done before the Operations Manager installation.
Installation under Windows 83
3 Installing ServerView Operations Manager
In SQL Server Management Studio you will find the authorized SQL Server administrators under Security – Server Roles – sysadmin and selection of
Properties from the context menu.
You can add a user account with SQL Server administrator rights as follows:
1. Check if the account to be added is already present in the list of valid SQL
Server logins.
To view the valid logins, select Security – Logins.
2. If the account is not present:
1. Select New Login from the context menu.
2. On the General page, enter the name of the Windows user under
Login name or Name. You can keep the other settings.
3. Switch to the Server Roles tab.
4. Select sysadmin or System Administrators as the server role and click
OK.
3. If the user account is already present:
1. Select Security – Logins – <login>.
2. Select Properties from the context menu.
3. Switch to the Server Roles tab and select the sysadmin checkbox.
4. Then click OK.
3.12
SQL Server 2005
Use of Operations Manager requires an SQL database in an SQL server. If there is already a full version of SQL Server 2005 on your system, you can specify this when installing the Operations Manager software. For the SQL Server 2005
Express Edition, an instance exclusively for Operations Manager is required, which must be called SQLSERVERVIEW. It is recommended that you always use the latest service pack.
When you install the Operations Manager software on Windows Server 2008, you will be offered SQL Server 2005 Express for the automatic SQL Server installation if no suitable SQL Server is pre-installed.
To manage the database you can use SQL Server Management Studio (Express), or sqlcmd, see
"Managing the ServerView database" on page 174
.
84 Installation under Windows
3.12 SQL Server 2005
3.12.1
Editions
You can use the following editions of SQL Server 2005, depending on your performance requirements and budget: l
Express Edition
SQL Server 2005 Express is available from the Microsoft Download Center.
Requires at least 512 MB RAM and uses a maximum of 1 CPU and 1 GB
RAM.
The full versions are: l l l
Workgroup Edition
For small organizations. Uses up to 2 CPUs and 3 GB RAM.
Standard Edition
For small and medium-sized organizations.
Uses up to 4 CPUs. The maximum RAM used is equivalent to the maximum size supported by the operating system. Failover cluster support (up to 2 nodes).
Enterprise Edition
Supports more than 4 CPUs. The maximum RAM used is equivalent to the maximum size supported by the operating system. Failover cluster support.
3.12.2
Preparing for installation
During the installation of SQL Server 2005, the necessary hardware and software requirements are checked. For information on this, the current service packs and the SQL Server 2005 Express package for downloading, see the Microsoft
Download Center website at http://www.microsoft.com/downloads .
There you will find Readme files and SQL Server 2005 Books Online with more detailed information on installing SQL Server 2005.
Installation under Windows 85
3 Installing ServerView Operations Manager
Installations of different language versions of SQL Server instances on the same system are not supported.
Example
SQL Server 2005 (English) and SQL Server 2005 (German) are not supported as parallel installed instances on the same system.
3.12.3
Installing SQL Server 2005 Express edition
The ServerView Suite DVD 2 provides the edition SQL Server 2005 Express
(English and Japanese). You can install this version automatically while installing the Operations Manager software. If a different language version of SQL Server from English or Japanese is detected on the machine during installation, you are asked to download this package from the Microsoft Download Center with a language that matches that of the existing SQL Server and install it interactively,
"Installing SQL Server 2005 Express from the Microsoft Download Center" on page 86 .
SQL Server 2005 Express is automatically installed with the Operations
Manager software if you use Windows Server 2008 and neither SQL
Server 2014/2012/2008/2005 Workgroup/Standard/Enterprise Edition with any instance name or as unnamed instance nor SQL Server
2014/2012/2008/2005 Express with the ServerView instance name
SQLSERVERVIEW is installed on your management station.
Installing SQL Server 2005 Express from the Microsoft Download Center
The following section describes how to install SQL Server 2005 Express, which is available via the Microsoft Download Center. Make sure you always use the latest Service Pack. This section describes the currently latest Service Pack 4.
Download the following files from the Microsoft Download Center
( http://www.microsoft.com/downloads ) onto your system, enter the following in the search field and, in the Quick details section, select the relevant language: l
.NET Framework 2.0 redistributable package (not on Windows Server 2008) l
SQL Server 2005 Express Edition SP4
86 Installation under Windows
3.12 SQL Server 2005 l
Optional: SQL Server Management Studio Express SP4 l
Optional: SQL Server 2005 Books Online
Install the software in the order given:
1. Install the .NET Framework 2.0 redistributable package software.
2. Install SQL Server 2005 Express Edition SP4:
Start the installation via the SQLEXPR.EXE file. The installation of SQL Server
2005 Express is interactive. In most of the dialog boxes you can accept the default settings, with the following exceptions: l
In the Registration Information window, deactivate the option Hide
advanced configuration options.
l l
In the Instance Name window, change the instance name from
SQLEXPRESS to SQLSERVERVIEW.
In the Service Account window o
Do not use the Network Service account.
o
Click the option Use the domain user account and enter the user name, password and domain name.
The domain user account does not require administrator authorization. You can use this account for all SQL services.
If you enter a local Windows user account here, use the account with the least privileges and the highest security level.
Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option activated and that they have strong passwords. Otherwise, follow the
Microsoft documentation "How to: Change the Password of the
Accounts Used by SQL Server" if the SQL Server is running under an account for which the password is to be changed.
There are, however, a few exceptions for using a local Windows user account: n
If remote procedure calls, replication, backing up to network drives, and heterogeneous joins that involve remote data sources are to be used on the server, the local Windows account is not sufficient.
Installation under Windows 87
3 Installing ServerView Operations Manager l l n
In fail cluster installations, local system and local service accounts are not allowed.
The SQL Server 2005 Readme files and the SQL Server 2005 Books
Online contain further details under the heading “Service account“.
Alternatively, you can select the option Customize for each
service account and choose a separate service account for each service, e.g. an integrated system account: n
Assign the Local System account for the SQL Server Service services, and the Local Service account for the SQL Server
Browser service.
You can still change the service-account assignment after the installation using the SQL Server Configuration Manager. For detailed information on this, see the SQL Server 2005 online documentation, heading “Service account“.
Mark in the Configuration Options window the option Add user to
the SQL Server Administrator role.
Activate TCP/IP network protocol:
By default, the TCP/IP network protocol is not activated for SQL Server
Express editions. This protocol is, however, necessary for the Operations
Manager database accesses. When you have installed SQL Server
Express, therefore, you still need to activate this protocol before you start the Operations Manager installation. Proceed as follows:
1. Start the SQL Server Configuration Manager.
2. Under SQL Server Network Configuration, select the SQL Server instance name of your previously installed SQL Server instance.
3. Set the TCP/IP protocol to enabled.
You will need to restart the SQL Server service for this change to become effective.
3. Optional: Install SQL Server Management Studio Express SP4
1. Execute the file SQLServer2005_SSMSEE.msi.
The installation is interactive. In most of the dialog boxes you can accept the default settings. This installs the graphical program SQL
Server Management Studio Express.
88 Installation under Windows
3.12 SQL Server 2005
4. Optional: Install SQL Server 2005 Books Online
This installs the SQL Server 2005 online documentation.
5. If your SQL Server system has Internet access, you can update via the
Microsoft Update website ( http://www.update.microsoft.com
). If not, check for further update packages in the Microsoft Download Center.
3.12.4
Installing SQL Server 2005 Enterprise/Standard/Workgroup edition
This section describes how to install the initial version of SQL Server 2005
Enterprise/Standard/Workgroup Edition, which must be installed from the
Microsoft SQL Server 2005 DVD.
The installation of SQL Server 2005 is interactive. In most of the dialog boxes you can accept the default settings, with the following exceptions: l l
In the Components to Install window, select the option SQL Server
Database Services and click Advanced. The Components to Install window does not appear in the Workgroup Edition.
In the Feature Selection window, expand SQL Server Database Services.
l l l
Under Data Files, select the entry Will be installed on local hard drive from the context menu.
Under Shared (Management) Tools, select the entry Will be installed
on local hard drive from the context menu.
In the Feature Selection window, expand Client Components.
l l l
Under Management Tools, select the entry Will be installed on local
hard drive from the context menu. This installs the graphical program SQL
Server Management Studio.
Under Documentation, Samples, and Sample Databases you can, if you wish, select Will be installed on local hard drive from the context menu.
This installs the SQL Server 2005 online documentation.
Note the following in the Service Account window: o
Do not use the NetworkService account.
o
Click the option Use a domain user account and enter the user name, password and domain name. The domain user account does not require administrator authorization. You can use the domain user
Installation under Windows 89
3 Installing ServerView Operations Manager account for all SQL services.
If you enter a local Windows user account here, use the account with the least privileges and the highest security level.
Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option activated and that they have strong passwords. Otherwise, follow the Microsoft documentation “How to: Change the Password of the Accounts Used by
SQL Server” if the SQL Server is running under an account for which the password is to be changed.
There are, however, a few exceptions for using a local Windows user account: n
If remote procedure calls, replication, backing up to network drives, heterogeneous joins that involve remote data sources, SQL
Server Agent mail features and SQL Mail are to be used on the SQL
Server for other applications, the local Windows account is not sufficient.
n
In fail cluster installations, local system and local service accounts are not allowed.
The SQL Server 2005 Readme files and the SQL Server 2005 Books
Online contain further details under the heading “Service account“.
Alternatively, you can select the option Customize for each service
account and choose a separate service account for each service, e.g. an integrated system account: n
Assign the Local System account for the SQL Server Service and
SQL Server Agent services, and the Local Service account for the
SQL Server Browser service.
You can still change the service-account assignment after the installation using the SQL Server Configuration Manager. For detailed information on this, see the SQL Server 2005 online documentation, heading “Service account“.
n
Also select the options SQL Server Agent and SQL Browser.
90 Installation under Windows
3.12 SQL Server 2005
The installation procedure for the Enterprise/Standard/Workgroup Editions is similar.
Installing service packs
After installation of the initial version of SQL Server 2005 the
Enterprise/Standard/Workgroup Editions must be updated with the latest service pack.
This section describes the currently latest Service Pack 4.
If your SQL Server system has Internet access, you can update via the Microsoft
Update web page ( http://www.update.microsoft.com
). Click the Custom button to list the available updates.
Otherwise, find a system with Internet access and download the service pack from the Microsoft Download Center SQL Server instance
( http://www.microsoft.com/downloads ):
1. In the field Search Download Center, enter SQL Server 2005 and press
Enter or click the Search button. You can sort the downloads by release date.
2. Select the current service pack from the results list.
3. In the Change Language list, select the language of the installed SQL
Server.
4. Click Download to download the file.
5. In the window that opens, click Save and then select the storage location for the file.
On Windows Server 2008 mark in the Additional Information window the option Launch the User Provisioning Tool.
Before you perform the update installation, you must stop all applications and services which are connected to the server instance.
SQL Server Management Studio and the Add or Remove Programs window must be closed.
l
Start the installation.
The installation is interactive and you can accept the default values. The updated components are shown in the Feature Selection window.
After the installation, the system is restarted.
Installation under Windows 91
3 Installing ServerView Operations Manager
For setting up high availability you can configure an automatic restart for the
ServerView services and SQL Server services. For further information, see
"ServerView services" on page 167
.
3.13
Configuring a remote SQL Server
To configure a remote SQL Server, proceed as follows:
1. Login as the local administrator.
2. The following services for the SQL Server instance must be started on the remote system:
SQL Server
SQL ServerAgent
SQL Server Browser
The services SQL Server and SQL Server Agent should run under a domain user account. For security reasons this account should not be a member of
Windows group Administrators.
Microsoft recommends that user accounts that are used to log on as a service have the Password never expires option activated and that they have strong passwords. Otherwise, follow the Microsoft documentation
"How to: Change the Password of the Accounts Used by SQL Server" if the
SQL Server is running under an account for which the password is to be changed.
This domain user account must belong to the same domain where the remote system is connected to.
If both systems are connected to the same domain, the services can also run under the service account Local System. This account has high privileges and is not recommendable for security reasons. The SQL Server Browser service runs under service account Local Service by default.
Use a database administration tool to change the startup account for SQL
Server. This ensures to automatically assign all the required permissions and
Windows user rights to the new startup account for you.
92 Installation under Windows
3.13 Configuring a remote SQL Server
Use SQL Server Configuration Manager:
1. Click on SQL Server <version> Services.
2. Stop the services for changing the account.
3. Change via the context menu entry Properties the service account.
4. Start the services.
The SQL Server is restarted automatically.
3. Accesses to the remote SQL Server are authenticated via the Windows domain user accounts of the Operations Manager services.
If you want to do an "Operations Manager installation without SQL Server
"sysadmin" access" skip the current step. Please refer to
Windows accounts and access rights" on page 101
and then return to the next step 4.
Therefore, for the domain user account l l under which you will be logged on to the system during the Operations
Manager installation, in the Operations Manager installation window Remote DB (for a new installation) or ServerView Service Logon Information for an upgrade installation l in the Operations Manager installation window Update Management
Logon Information, you must bear in mind the following: l l
The domain user accounts must belong to the same domain as the server on which Operations Manager is installed.
The domain user accounts must be created in SQL Server as Login using the SQL Server administration tools.
l
These logins must also be assigned a certain server role. This role include the authorization necessary for installing and running the application.
To set up a user account, proceed as follows:
1. Log in as the administrator on the remote system.
2. Start the program SQL Server Management Studio for database administration.
Installation under Windows 93
3 Installing ServerView Operations Manager
3. Select the SQL Server instance or connect to it.
4. Select Security – Logins.
5. Select New Login from the context menu. The Login - New window opens.
6. Enter the name for the domain user account under Login name or
Name. You can keep the other settings.
7. Switch to the Server Roles tab.
8. Select sysadmin or System Administrators as the server role.
9. Click OK.
4. Remote access (via TCP/IP) to the corresponding SQL Server instance must be activated as follows.
1. Open the SQL Server Configuration Manager by selecting Start – All
Programs – Microsoft SQL Server <version> – Configuration Tools –
SQL Server Configuration Manager.
2. Select SQL Server <version> Network Configuration.
3. Click Protocols for <instance>. A list of protocols and their status is displayed.
4. Check the setting Protocol for <instance>.
5. The status for the TCP/IP protocol must be Enabled.
6. If not, activate TCP/IP for the instance.
5. For remote access to the SQL Server instance, a static port is required. Either use an unnamed SQL Server instance or configure a static port for a named instance.
To check the port configuration of a named instance, proceed as follows:
1. Open the Registration Editor.
2. Search for the following entries: l
For an SQL Server 2014 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL12.<Instance
Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
94 Installation under Windows
3.13 Configuring a remote SQL Server l l l l
For an SQL Server 2012 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL11.<Instance
Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
For an SQL Server 2008 R2 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL10_50.<Instance
Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
For an SQL Server 2008 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL10.<Instance
Name>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
For an SQL Server 2005 instance:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.<n>\MSSQLServer\SuperSocketNetLib\Tcp\IPAll
In SQL Server 2005, MSSQL.<n> identifies the number of instance on the server with. <n> = .1..16 (e.g. MSSQL.1).
As of SQL Server 2008, the internal version number (10, 10_50,
11) suffixed with the instance name is used:
MYSQL<internal version number>.<Instance Name>.
3. Check the values for TCPDynamicPorts and TCPPort. If the value for
TCPDynamicPorts is not set, SQL Server always uses a static port. You will see the port number under TCPPort.
If a static port was configured previously, the SQL Server instance must be restarted for the changes to the port configuration to take effect.
The static port for a named instance can be assigned via SQL Server
Configuration Manager. The procedure is described in SQL Server Books
Online "Configure a Server to Listen on a Specific TCP Port (SQL Server
Configuration Manager)".
6. Make sure that the port is not blocked by any firewall settings.
Installation under Windows 95
3 Installing ServerView Operations Manager
If necessary, allow via firewall administration program the following port for the SQL Server instance: l
Add for program SQL Server and protocol TCP either the default port number 1433 or the port number given under TCPPort in the
Registration Editor.
l
Add for program SQL Server and protocol UDP port number 1434.
7. When installing SQL Server in another, but trusted domain, the SQL Server must be accessible via netbios name. You can do this by expanding the DNS
Suffix Search List.
1. Log on to the SQL Server machine.
2. Look at the current DNS Suffix Search List.
Open a command prompt window and type ipconfig /all.
3. In the Windows IP Configuration entry you will find the DNS Suffix search list. The suffix of the domain to which the central management station is connected must be listed.
4. If not, you can change it e.g. by configuring Append these DNS
suffixes:
1. Select Control Panel – Network and Sharing Center.
2. Click Properties and click Internet Protocol Version.
3. Click Properties and click Advanced for the DNS server address.
4. In the DNS tab, select the option Append these DNS suffixes (in
order) and click Add.
5. Insert the TCP/IP Domain Suffix of the domain to which the central management station is connected to.
Further procedure on the management station
If you followed all instructions in "Operations Manager installation without SQL Server "sysadmin" access" skip the following steps 1 to 3 and go on with step 4.
1. Log on as local administrator.
2. Add the domain user account under which you want to perform the
Operations Manager installation and all further domain user accounts which you specify for services during the installation, as for example in the
96 Installation under Windows
3.13 Configuring a remote SQL Server
Remote DB window, ServerView Service Logon window and in the
Update Management Logon Information window to the Administrators group.
3. Log on under this domain user account.
4. Start ServerView Operations Manager installation and select in the Select
SQL Server window the Use existing remote SQL Server option,
"Menudriven installation of Operations Manager software" on page 140 .
5. On a new installation enter in the Remote DB window the corresponding values,
"Remote DB window" on page 142 . The local service ServerView
Services will run under this account and will have access to the remote SQL
Server via the SQL Server Login you created above.
6. In the other Logon Information windows enter the same domain user account or a further domain user account for which you have created a SQL
Server Login.
7. In the other windows fill in as described in section
"Menu-driven installation of Operations Manager software" on page 140
.
If you want to change the service account of SQL Server and SQL Server Agent after the ServerView Operations Manager installation you must additionally give on remote system write admission to the SQL Server backup folder
DbBackupPath from %windir%\ServerViewDB.ini file and to the files below.
Upgrade installation
When you installed ServerView Operations Manager, you specified a user name and password for the ServerView services in the Remote DB window.
In an upgrade installation you must enter the password in the ServerView
Service Logon information dialog again because it is not saved.
3.13.1
Troubleshooting for Remote SQL Server
This section describes examples of error messages which appear if the remote
SQL Server was not configured correctly. Under Troubleshooting you will find a short description of the cause of the error. For the configuration details please search for the underlined terms in
"Configuring a remote SQL Server" on page 92
if no other section is specified.
Installation under Windows 97
3 Installing ServerView Operations Manager
3.13.1.1
Messages after clicking Next in the Remote DB dialog
Message
"Error: Unable to connect to SQL Server. Connection attempt rejected […] SQL Server does not exist or access denied."
Troubleshooting
1. Enter the correct SQL Server name in the Remote DB dialog.
You can display existing SQL Server instances and see the correct SQL Server names by entering at the command prompt: sqlcmd -L
2. Make sure that the port is not blocked by any firewall settings.
You can test the connection by entering at the command prompt: sqlcmd -S <SQL Server instance> -E
The message "Unable to complete login process due to delay in opening server connection" indicates blocking by a firewall.
Message
"Error: Unable to connect to SQL Server. Connection attempt rejected […] Login failed for user '…'. Reason: Not associated with a trusted SQL Server connection"
Troubleshooting
Please check for a two-way trust relationship via Administrative Tools – Active
Directory Domain and Trusts.
Message
"Error: Given user name does not exist in SQL Server. Check user name and SQL Server logins.
Troubleshooting
Create the domain user account in the SQL Server as Login.
Message
"The specified remote database could not be validated. Please check the server name and user account parameters. Error: New
98 Installation under Windows
3.13 Configuring a remote SQL Server installation, but ServerViewDB already exists in SQL Server database."
Troubleshooting
See
"Remotely on a different system" on page 48
.
3.13.1.2
Messages after the “Ready to Install the Application” dialog during execution of SQL Script ExecDefRecBcp.sql
Message
1.
"String or binary data would be truncated."
2.
"Conversion failed when converting the … value '…' to data type …"
Troubleshooting
1. Start the SQL Server services SQL Server and SQL Server Agent under a domain user account that should not be a member of the Windows group
Administrators.
2. Make sure that the domain user account under which you are performing the Operations Manager installation still exists.
3. Check if the central management station and remote SQL Server computer are in different domains, see Control Panel – System entry Domain.
If they are in different domains, please check for a two-way trust relationship via Administrative Tools – Active Directory – Domain and
Trusts.
4. The SQL Server must be accessible via netbios name.
3.13.1.3
Messages after the “Click Install to begin installation” dialog during execution of SQL Script ServerConfig.sql or SVSQLDbCreation.sql
Message
"… permission denied in database …"
"… permission denied on object …"
Troubleshooting
Assign the SQL Server administrator right sysadmin or System Administrators to the domain user accounts under which you want to perform the Operations
Manager installation and which you are specifying for services.
Installation under Windows 99
3 Installing ServerView Operations Manager
3.13.1.4
Messages after the “Click Install to begin installation” dialog during execution of GrantLoginJBoss.sql
Message
[…] Windows NT user or group ‚…' not found. Check the name again."
Troubleshooting
You must insert a domain user in the JBoss Service Logon Information window, see
"Menu-driven installation of Operations Manager software" on page
3.14
Operations Manager installation without SQL
Server "sysadmin" access
The default installation of Operations Manager requires system administrator permission in the SQL Server (the sysadmin server role) for the installing account and the accounts used for ServerView Services and ServerView Download
Services. The SQL Server “sysadmin” permission is considered critical by customers in security-sensitive environments, especially when using remote SQL
Servers and SQL Server Clusters.
An alternative since ServerView Operations Manager V6.20 is to configure the
SQL Server without SQL Server administration rights for the accounts - so-called
“enhanced security”. When you then start the Operations Manager installation the enhanced security settings in SQL Server are detected.
You will need to configure the SQL Server before you execute a new or upgrade installation of Operations Manager.
IMPORTANT:
The configuration for enhanced security settings (without “sysadmin”) requires good knowledge and experience of SQL Server administration.
It is therefore only recommended for customers with enhanced security requirements especially using a remote SQL Server.
The default installation method with “sysadmin” user access uses default settings and is easier to handle for users without SQL Server administration knowledge. It therefore remains the normal installation method.
100 Installation under Windows
3.14 Operations Manager installation without SQL Server "sysadmin" access
This section explains the configuration of accounts for SQL Server with enhanced security. For the default installation with “sysadmin” access, refer to the corresponding chapters in this installation manual.
3.14.1
Overview of Windows accounts and access rights
The ServerView Operations Manager setup may require up to four Windows accounts for installation and operation for SQL Server.
Important for all Windows accounts used:
l l
For a remote SQL Server, you may only use domain accounts from a trusted domain or from the same domain as the Central
Management Server.
For a local SQL Server, predefined Windows accounts or userdefined accounts may be used.
The following Windows accounts are used:
1. The installation account.
Windows account used to start the Operations Manager installation. This account needs permission in SQL Server to create the ServerViewDB database.
2. ServerView Services account.
Windows account used to start ServerView Services.
o o
For a local SQL Server:
Always the Local System account.
For a remote SQL Server:
During setup, specified in the window Remote DB (for a new installation) or ServerView Service Logon Information (for an upgrade installation).
The account cannot be changed in upgrade or modify installations.
3. ServerView JBoss Application Server account.
Windows account used to start the JBoss Application Server service. During setup, specified in the window JBoss Service Logon Information.
4. ServerView Download Service account.
Installation under Windows 101
3 Installing ServerView Operations Manager
The account used to start the ServerView Download Service. During setup, specified in the window Update Management Logon. As this account needs access to the Internet, it is recommended to use a separate account for this purpose.
Required membership in the Windows Administrator group on the CMS:
2
3
4
No. Account
1 Installation Account
ServerView Services
ServerView JBoss Application
ServerView Download Service
Local and Remote SQL Server
Yes
Yes
No
Yes
Yes: must be a member of the Windows Administrator group
No: need not be a member of the Windows Administrator group
Predefined Windows accounts used with a local SQL Server:
2
3
No. Account
1 Installation Account
4
ServerView Services
ServerView JBoss Application
ServerView Download Service
Local and Remote SQL Server
Administrator
LocalSystem
LocalService
.\Administrator
SQL Server service accounts
For security reasons, the services SQL Server and SQL Server Agent service should run under an account which is not a member of the Windows group
Administrators. For a local SQL Server, local Windows accounts may be used. For a remote SQL Server, these accounts must either be domain accounts or (but only when both the CMS and the SQL Server are in the same domain) the Local
System account. For security reasons, however Local System is not recommended or further details, please
"SQL Server service accounts" on page
102 Installation under Windows
3.14 Operations Manager installation without SQL Server "sysadmin" access
SQL Server Logins
ServerView Operations Manager uses Windows authentication to authenticate in
SQL Server. Any account used for Operations Manager setup and operation must correspond to a valid login for Windows in SQL Server. The SQL Server
Administrator must add the installation account (1) and any further account to be used ((2) – (4) specified above) as SQL Server Login for Windows
authentication before the Operations Manager setup is started.
SQL Server Permissions
The installing account (1) must also be given at least the permission to create a database in SQL Server.
Server and database roles for the installation account
The accounts used need the following server and database roles in SQL Server to successfully perform the ServerView Operations Manager database setup and operation:
2
3
4
Login Server Role Database Role
1
dbcreator
optional:
diskadmin
Recommended in database msdb for full versions of SQL
Server: l l
db_backupoperator (or db_owner)
SQLAgentReaderRole
l
SQLAgentUserRole
Optional in database master for all SQL Server editions:
db_backupoperator (or db_owner)
-
-
-
-
-
-
The dbcreator server role is required to create the ServerView database and database schema. The setup will check the role assignment and display an error message if this role is not granted. If this is the case, it will exit with rollback.
The two SQLAgent roles are highly recommended for full versions of SQL Server.
They are not needed at all for SQL Server Express Editions. The ServerView setup
Installation under Windows 103
3 Installing ServerView Operations Manager will try to install backup and maintenance jobs for its database ServerViewDB via
SQL Server Agent procedures. If this cannot be done, the setup will display an informational message but will not exit or rollback.
Please note that backup jobs for the database ServerViewDB are especially important if you want to choose option the SQL Server
Backup Mode “advanced / full” in the Operations Manager setup later on. This is because the database transaction log may grow to enormous sizes if regular backups are not performed.
When you choose the SQL Server Backup Mode “advanced / full” for the
ServerView database, it is highly recommended to either assign the
SQLServerAgent roles or install a backup scheme of your own.
The diskadmin server role is optional. If granted the ServerView setup will try to create backup devices by storing the database backup files in the ServerView installation path otherwise the backups are performed within the SQL Server default backup path. The setup will not exit or roll back if the role assignment is missing.
The db_backupoperator database role for the system database msdb is highly recommended for the full versions of SQL Server. The db_backupoperator database role for the master database is optional for all SQL Server editions.
ServerView setup will try to perform a backup of these system databases depending on the SQL Server edition at the end of the setup.
The setup will display an informational message if the role is not granted , but it will not exit or rollback. The db_owner role comprises the permission to back up, but is the role with the highest privilege. It has permission to perform any task on the database.
3.14.2
Configuration steps
Note down in the following table the accounts you want to use in the Operations
Manager setup:
No. Account Window (title)
1 Installation Account -
Account
104 Installation under Windows
3.14 Operations Manager installation without SQL Server "sysadmin" access
No. Account
2 ServerView Services
Window (title)
l l
For remote SQL Server:
Remote DB or ServerView Service
Logon Information
For local SQL Server: no window
JBoss Service Logon Information
3 ServerView JBoss
Application
4 ServerView
Download Service
Update Management Logon
Information
Account
3.14.2.1
Tasks to be performed by the Windows Administrator on the CMS
1. Log on as a user with administrator rights on the central management station.
2. Add the accounts to the Windows Administrator group: l l
For a local SQL Server:
Add the accounts (1) and (4) to the Windows Administrator group.
For a remote SQL Server:
Add the domain accounts used for the accounts (1), (2) and (4) to the
Windows Administrator group.
3.14.2.2
Select the SQL Server
l
Decide whether to use a remote or local SQL Server.
o o
IMPORTANT:
A remote SQL Server is recommended.
Valid editions for a remote SQL Server:
SQL Server Standard, Enterprise and Workgroup (where available).
Valid editions for a local SQL Server:
SQL Server Express, SQL Server Standard, Enterprise, Workgroup (where available), see
"Installation options for SQL Server" on page 43 .
Installation under Windows 105
3 Installing ServerView Operations Manager l l
No SQL Server 2005 editions are supported. This is because, by default,
SQL Server 2005 creates the BUILTIN\Administrators login group. Any member of the local Windows administrator group is automatically a member of this group and thereby also acquires the “sysadmin” fixed server role in SQL Server. This is the case for the Operations Manager accounts (1), (2), and (4). It is not recommended to remove this group from the SQL Server.
If you do not have an SQL Server already installed, install it as described in one of the previous “SQL Server 20xx” sections. Install a full version of SQL
Server with the Management Tools feature. For an SQL Server Express edition install the SQL Server Management Studio.
In the case of a remote SQL Server, now follow: o o
Section
"Remotely on a different system" on page 48
Section
"Configuring a remote SQL Server" on page 92
, steps 1 and 2.
Instead of step 3, follow the next sections below.
3.14.2.3
Tasks to be performed by the SQL Server Administrator
Add the accounts (1) to (4) with SQL Server Management Studio as follows:
1. Start the SQL Server Management Studio by selecting Run as
Administrator from the context menu.
2. Connect to the server instance as SQL Server Administrator under an account which holds the “sysadmin” server role in SQL Server.
IMPORTANT:
The sysadmin server role is always required for the SQL Server
Administrator account to administer the SQL Server.
DO NOT revoke the sysadmin right from all logins in SQL Server.
At least one account must hold the sysadmin server role in the SQL
Server.
Check if the account to be added is already present in the list of valid SQL Server logins and add if necessary:
106 Installation under Windows
3.14 Operations Manager installation without SQL Server "sysadmin" access
1. To view the valid logins, select Security – Logins.
2. If the account is not present, create a new login:
1. Select New Login from the context menu.
2. On the General page, select Windows Authentication.
Enter the name of the Windows user under Login name or Name. You can keep the other settings.
3. Then click OK.
Do the steps 1. to 3. for the accounts (1) to (4).
IMPORTANT:
If the account is already present, revoke the sysadmin right for accounts (1) to (4):
1. Start SQL Server Management Studio as described above.
2. Select Security – Logins.
3. Select the entry for the accounts (1) to (4).
4. Select Properties from the context menu.
5. Switch to the Server Roles page.
6. Uncheck the sysadmin option.
Add the installation account to the server role “dbcreator”:
1. Start SQL Server Management Studio as described above.
2. Select Security – Logins.
3. Select the entry for the installation account (1).
4. Select Properties from the context menu.
5. Switch to the Server Roles page.
6. Select the dbcreator checkbox and optionally diskadmin.
7. Click OK.
Add the installation account to the database roles in the msdb database for full versions of SQL Server:
1. Start SQL Server Management Studio as described above.
2. Select Security – Logins.
3. Select the entry for the installation account (1).
Installation under Windows 107
3 Installing ServerView Operations Manager
4. Select Properties from the context menu.
5. Switch to the User Mapping page.
6. Select the Map checkbox for the msdb database.
7. Select the row for the msdb database.
8. Select the following checkboxes for Database role membership: for msdb: o
db_backupoperator (or db_owner) (not for Express editions) o o
SQLAgentUserRole (not for Express editions)
SQLAgentReaderRole (not for Express editions)
Optionally add the installation account to the database roles in the master database:
1. Start SQL Server Management Studio as described above.
2. Select Security – Logins.
3. Select the entry for the installation account (1).
4. Select Properties from the context menu.
5. Switch to the User Mapping page.
6. Select the Map checkbox for the master database.
7. Select the row for the master database.
8. Select the following checkboxes for Database role membership: for
master.
o
db_backupoperator (or db_owner)
Additional task
For a local SQL Server, ServerView Operations Manager always uses the Local
System account for ServerView Services operation.
Check whether this account has a valid SQL Server Login for Windows authentication in SQL Server:
1. Log in to SQL Server Management Studio under an account holding the
“sysadmin” role in SQL Server.
2. Select Security – Logins.
3. Can you see the following?
108 Installation under Windows
3.14 Operations Manager installation without SQL Server "sysadmin" access
NT AUTHORITY\SYSTEM on a English operating system
NT AUTORITÄT\SYSTEM on a German operating system
AUTORITE NT\SYSTEM on a French operating system
If the login is not present, add it with New Login from the context menu.
3.14.3
Further configuration steps for a remote SQL Server
IMPORTANT:
Now return to chapter 3.12 Configuring a remote SQL Server, and continue with step 4 “Remote access (via TCP/IP) to the corresponding
SQL Server instance must be activated” and complete the rest of the remote SQL Server configuration.
3.14.4
Further procedure on the management station
1. Log on to the central management station as the installation account (1).
2. Proceed with the installation as described in section
"Menu-driven installation of Operations Manager software" on page 140
and add the accounts in the corresponding installation windows as specified in the previous section 3.13.2 Configuration steps.
3. After the installation you will see the following entries in the file
%windir%\ServerViewDB.ini:
[Accounts]
InstallationAccount=Domain\User
SqlServerViewServicesAccount=Domain\User
SqlServerViewDownloadServiceAccount=Domain\User
SqlServerWithEnhancedSecurity=yes
The entry SqlServerWithEnhancedSecurity must be set to yes.
Installation under Windows 109
3 Installing ServerView Operations Manager
3.15
Upgrade installations of SQL Server
3.15.1
Upgrading to later SQL Server versions
An installed ServerView database from an existing instance of SQL Server can be upgraded to a later version of SQL Server.
l
Operations Manager as of version 4.90 supports an upgrade from SQL
Server 2005/SQL Server 2005 Express to SQL Server 2008 edition.
l l
Operations Manager as of version 5.10 supports an upgrade from SQL
Server 2005/SQL Server 2005 Express to SQL Server 2008/2008 R2 edition.
The description for SQL Server 2008 is also valid for SQL Server 2008 R2 in this manual.
Operations Manager as of version 6.30 supports an upgrade to SQL Server
2012 version from the following SQL Server versions: l o o o
SQL Server 2005/SQL Server 2005 Express
SQL Server 2008/SQL Server 2008 Express
SQL Server 2008 R2 /SQL Server 2008 R2 Express
Operations Manager as of version 7.10 supports an upgrade to SQL Server
2014 version from the following SQL Server versions: o o o o
SQL Server 2005/SQL Server 2005 Express
SQL Server 2008/SQL Server 2008 Express
SQL Server 2008 R2 /SQL Server 2008 R2 Express
SQL Server 2012/SQL Server 2012 Express
You have two upgrade options:
1. Upgrade the complete SQL Server instance to a later version of SQL Server, see
"Upgrading the SQL Server instance" on page 111
.
2. Move only the ServerView database from the existing SQL Server instance into an SQL Server instance of a later version, see
"Moving the ServerView database" on page 117 .
Once you have upgraded the SQL Server instance or moved the ServerView database, further migration steps are necessary in order to update or set up
110 Installation under Windows
3.15 Upgrade installations of SQL Server internal backup and administration jobs for Operations Manager. For this purpose, the installation provides a batch file, which you must execute after upgrading the instance or moving the database.
Please observe the permissions in Microsoft SQL Server needed for upgrades. Several upgrade steps require membership of the
"sysadmin" server role of MS SQL Server. It is therefore recommended to perform the process as a member of the "sysadmin" server role.
If the SQL server is not installed on the central management station but remotely on another server (see
"Remotely on a different system" on page 48
), you must check or ensure the following:
Installation of SQL Server client tools
To access the remote SQL Server 2005/2008/2012, you will need the relevant
SQL Server client tools (Microsoft SQL Server Native Client) on the local management station. Check whether these tools are installed: l l l
For SQL Server 2005: Microsoft SQL Server Native Client
For SQL Server 2008: Microsoft SQL Server 2008 Native Client
For SQL Server 2008 R2: Microsoft SQL Server 2008 R2 Native Client l l
For SQL Server 2012: Microsoft SQL Server 2012 Native Client
For SQL Server 2014: Microsoft SQL Server 2012 Native Client
If the tool is not installed, you must install it on the local management station after completing the SQL Server upgrade and before executing the provided batch files. SQL Server client tools are available from the Microsoft Download
Center.
3.15.1.1
Upgrading the SQL Server instance
This upgrade method is also called an “in-place“ upgrade and is offered as an installation option by the SQL Server setup. The upgrade is performed when you execute the SQL Server setup and select the appropriate option offered there.
During the SQL Server upgrade, all databases installed in this instance - i.e. also the ServerView database - are automatically upgraded.
Operations Manager remains installed on the system. Only while the upgrade is being performed must accesses to Operations Manager be temporarily stopped.
Installation under Windows 111
3 Installing ServerView Operations Manager
An in-place upgrade requires the following: l
An installed instance of SQL Server in a particular edition can only be upgraded to a corresponding compatible edition of SQL Server. An SQL
Server 2005 Express instance can, for example, be upgraded to an SQL
Server 2008 Express instance, but not directly to an SQL Server 2008
Standard or Enterprise Edition.
l l
You cannot perform an in-place upgrade from an installed 32-bit edition of
SQL Server to a 64-bit edition of SQL Server.
Language dependencies must also be taken into account:
During an in-place upgrade it is not possible to upgrade a localized version of SQL Server (for example, the German version) to a different-language version of SQL Server. For an in-place upgrade, therefore, you must install the new SQL Server instance in the same language version as the old instance. Only an English version of SQL Server can be upgraded to a localized version in a different language.
The installation requirements are also checked by the SQL Server setup process itself, with messages or warnings being output if necessary.
If the existing SQL Server instance was installed by Operations Manager, the installation language is English or Japanese.
You can also check the product version, installation language and edition of the installed SQL Server instance beforehand as follows:
1. Find out the contents of the Server_Instance parameter in the configuration file ServerViewDB.ini. The configuration file is located in the
<windir> directory.
2. Open the input prompt.
3. Enter the following commands: osql -S <server_instance> -E xp_msver
GO select @@version
GO
You will find the necessary information on the version and language in the command output under 2 ProductVersion and 3 Language. @@version
112 Installation under Windows
3.15 Upgrade installations of SQL Server gives you the edition.
You quit osql with the quit command.
Preparing for installation
l
While the SQL Server instance is being upgraded, the setup checks the necessary hardware and software requirements. You can find out these requirements in advance from the web pages of the Microsoft Download
Center for the SQL Server version required or from the SQL Server online documentation available on the Internet.
l l
To install an SQL Server Express Edition, you may have to download the required software from the Microsoft Download Center and install it yourself in advance. All other editions of SQL Server come with the necessary software components and install them when you start the setup.
You should also find out from the relevant SQL Server online documentation which version and edition upgrades from SQL Server to later SQL Server editions Microsoft supports in the setup.
l
Find out the type (default instance or named instance) and name of the installed SQL Server instance. You have to specify the instance name and type while executing the SQL Server installation, so that the SQL Server setup upgrades the correct SQL Server instance. You will find this information in the configuration file ServerViewDB.ini (in the <windir> directory) in the
Server_Instance and Instance parameters: o o
If there is no Instance parameter, the instance is a default one. Under
Server_Instance, only the server name (usually (local)) is given.
For a named instance, the instance name is given under Instance. The
Server_Instance parameter contains the information <server_name>\
<instance_name>.
Necessary actions before the upgrade
l
Back up the databases of the relevant instance.
l l
Close all applications which have access to the relevant SQL Server instance.
Stop all dependent services, in particular ServerView Services and
ServerView Download Service.
Installation under Windows 113
3 Installing ServerView Operations Manager l
Install the required software for the installation of the new SQL Server version and edition.
Performing the upgrade
You upgrade the instance by executing the SQL Server setup. The installation can be performed interactively for all editions of SQL Server. It is recommended that you always use the latest service pack. If possible you should also perform a
Microsoft update after the setup, so that you receive any current security updates for the upgraded SQL Server version from Microsoft.
Upgrading from older SQL Server editions
Bear in mind the following during the upgrade to a newer SQL Server version: l
During the procedure, the SQL Server setup program detects all installed SQL
Server instances on the server and displays them for selection and configuration in various interactive steps.
l
First of all, in the Select Instance window you must select the instance name from the displayed list. If there are several instances installed, the setup preselects a standard instance of SQL Server, if there is one. An SQL
Server Express instance used by ServerView is normally installed as a named instance (instance name SQLSERVERVIEW). You can find out the name and type of the instance used by ServerView from the configuration file
ServerViewDB.ini (in the <windir> directory) as described above.
l l
In the later Instance Configuration window, you must then check the instance name again and specify whether you want to install a standard instance or a named instance.
For the remaining configuration options, apart from the instance name, you can accept the default options.
Upgrading from an older SQL Server Express version
The Microsoft documentation contains a detailed upgrade support matrix for any version and edition of SQL Server. Please check the supported path for your version of SQL Server Express in advance.
For example, additional tools allow you to perform the following upgrades: l
An installed SQL Server 2005 Express, you can upgrade to SQL Server 2008
Express or its extended versions with additional tools (SQL Server 2008
114 Installation under Windows
3.15 Upgrade installations of SQL Server
Express with Tools).
If you want to install the extended editions, however, you must execute the installation program again after the upgrade in order to add the additional components.
l l
An installed SQL Server 2005 Express, you can upgrade to SQL Server 2012
Express or SQL Server 2014 Express or its extended versions with additional tools (SQL Server 2012/2014 Express with Tools).
An installed SQL Server 2008 Express, you can upgrade to SQL Server 2012
Express or SQL Server 2014 Express or its extended versions with additional tools (SQL Server 2012/2014 Express with Tools).
You can get the editions of SQL Server 2008/2012/2014 Express you require from the Microsoft Download Center. After starting the setup, select the option
Upgrade from SQL Server 2005 / Upgrade from SQL Server 2008 / Upgrade
from SQL Server 2008 R2 / Upgrade from SQL Server 2012. During the installation you must then specify in a later follow-up dialog the SQL Server instance to be upgraded.
Upgrading from all other SQL Server editions
All SQL Server editions can usually be upgraded to a corresponding edition of a higher SQL Server version, provided the upgrade path is supported by Microsoft version and edition restrictions. Please check the supported upgrade path for your version and edition in the Microsoft documentation in advance. Full editions of SQL Server are not available free of charge from the Download Center but must be licensed and installed from your SQL Server installation medium.
Necessary actions after the upgrade
After the in-place upgrade of the instance, you must perform the following steps for all versions of SQL Server:
1. Check whether the SQL Server (<instance_name>) service was started.
2. For editions other than SQL Server Express:
Check whether the SQL Server Agent (<instance_name>) service was started.
Installation under Windows 115
3 Installing ServerView Operations Manager
If you are using a remote SQL Server for Operations Manager, you must perform the additional steps on the management station. To do this, log on to the management station under the user account specified in the %windir%\ServerViewDB.ini file under the entries Domain and Username.
3. For SQL Server Express:
Check whether the Windows service Task Scheduler has started.
4. Internal backup jobs of Operations Manager must now be set up again before you can restart Operations Manager.
The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView
Operations Manager installation: l
SQL Server Client tools must be installed and accessible via the
PATH environment variable in their default location on the
CMS: l
<Program Files>\Microsoft SQL
Server\<version>\Tools\Binn\ (with <version> in
90\100\110).
The calling account must be a member of the sysadmin server role in SQL Server.
l
The Windows command prompt used to call the tool must be opened with full administrator rights.
Proceed as follows:
1. Open the input prompt.
2. Switch to the directory:
<installation_path>\ServerView Services \scripts\ServerView\Tools
3. Execute the following batch file, which you will find in this directory after upgrading to an SQL Server 2008, SQL Server 2012 edition, or SQL
Server 2014 edition: l
SVCreateJobs_Upgrade2008
l l
SVCreateJobs_Upgrade2012
SVCreateJobs_Upgrade2014
116 Installation under Windows
3.15 Upgrade installations of SQL Server
4. During the execution, answer
Renamed SQL Server Instance
[Y/N] ?
with N.
5. All necessary upgrade steps for Operations Manager will be executed from this batch file. The individual steps will also be logged in the log file
<DbApplicationFolder>\SVCreateJobs_Upgrade2008.log or
<DbApplicationFolder>\SVCreateJobs_Upgrade2012.log(for SQL Server
2012/2014). You can find out the contents of the DbApplicationFolder parameter from the configuration file ServerViewDB.ini (in the <windir> directory).
6. After successful execution, start the services ServerView Services and
ServerView Download Service.
7. Then check whether the backup jobs for the ServerView database have been set up and can be executed.
For SQL Server Express editions the jobs were set up via the Windows Task
Scheduler and therefore can only be monitored via this tool: l
To do this, open Control Panel – Scheduled Tasks and you will see a list of jobs and their schedules.
For all other editions of SQL Server, the service SQL Server Agent is used to set up the jobs. In this case, check the jobs and schedules via SQL Server
Management Studio.
l
Start SQL Server Management Studio.
l l
Click the SQL Server instance and select the entry SQL Server Agent.
Under Jobs you will see the jobs that have been set up. You can view the current schedule for each job with View History.
3.15.1.2
Moving the ServerView database
If you do not want to or cannot perform an in-place upgrade of the entire SQL
Server instance, you can instead move the ServerView database from an installed SQL Server instance into a new SQL Server instance, thus migrating it.
This procedure is also referred to in the Microsoft online documentation for SQL
Server as a "side-by-side" upgrade. You must choose this variant if an in-place upgrade for your SQL Server edition is not supported by Microsoft. This is the case, for example, if you want to upgrade from a 32-bit SQL Server edition to a
64-bit SQL Server edition.
Installation under Windows 117
3 Installing ServerView Operations Manager
In the Microsoft online documentation for the SQL Server version required, you can find out which version and edition upgrades from SQL Server/SQL
ServerExpress to later SQL Server editions are supported by Microsoft.
With this upgrade method, a new SQL Server instance is installed side-by-side with the existing one. The ServerView database is first detached from the installed instance and then attached to the new instance. Operations Manager also remains installed on your system with this method.
You must install the new SQL Server instance on the same system as the old one, so that the client configuration for Operations Manager is retained. So that, the old and new instances of SQL Server cannot be installed side-by-side under the same instance name.
You must either l
Uninstall the SQL Server instance after the database is detached and before the new instance is installed, or l
Install the new SQL Server instance under a different instance name.
Note the following:
Switching the instance type is not supported for the upgrade of the
ServerView database. For the upgrade you can install a named instance under a different name, but not switch from a named instance to a default instance (or vice versa).
Preparing for installation
l
During the installation of the newer instance, the necessary hardware and software requirements are checked. For information on this, see, for example, the product pages for the new SQL Server version in the Microsoft
Download Center.
l l
To install an SQL Server Express Edition, you may have to download the required software from the Microsoft Download Center and install it yourself in advance. All other editions of SQL Server come with the necessary software components.
Find out the type (default instance or named instance) and name of the installed SQL Server instance. You will find this information in the
118 Installation under Windows
3.15 Upgrade installations of SQL Server l configuration file ServerViewDB.ini (in the <windir> directory) in the
Server_Instance and Instance parameters: o o
If there is no Instance parameter, the instance is a default one. Under
Server_Instance, only the server name (usually (local)) is given.
For a named instance, the instance name is given under Instance. The
Server_Instance parameter contains the information <server_name>\
<instance_name>.
Find out the current path names of the ServerView database files. The path names are needed for attaching the database to the newer SQL Server instance.
You can find out the path names as follows using the SQL Server
Management Studio:
1. Start the tool and connect to the installed SQL Server instance.
2. Select the database ServerViewDB.
3. Select Properties from the context menu. After selecting files, you will find the path name.
You can find out the path names using osql (or sqlcmd) as follows:
1. Open the input prompt and enter the following commands: osql -S <Server_Instance> -E
EXEC sp_helpfile
GO
The filename column contains the path details.You quit osql with the quit command.
Necessary actions before the upgrade
l l
In the existing SQL Server instance, back up the ServerViewDB database so that you have an up-to-date backup.
Close all applications which have access to the relevant SQL Server instance.
l l
Stop all dependent services, in particular ServerView Services and
ServerView Download Service.
Install the required software for the installation of the new SQL Server version.
Installation under Windows 119
3 Installing ServerView Operations Manager
Performing the upgrade
l
Detach the ServerView database from the existing SQL Server instance.
You can either do this with SQL Server Management Studio, or directly by calling an SQL Server procedure from an input prompt with osql.
If you want to use a management tool, you can find out from the online help for the tool you are using how to detach the database.
If you are using an input prompt, proceed as follows:
1. Open the input prompt and enter the following commands: osql -S <server_instance> -E
EXEC sp_detach_db @dbname='ServerViewDB' l l l l l
GO
You quit osql with the quit command.
Detach does not delete the database files from SQL Server; instead they remain in the relevant storage location. You can either leave the files there or copy them to a different directory. In any case you must specify the current path name in the new instance when you attach the database later.
If the name of the SQL Server instance is not to be changed, you must now uninstall the existing SQL Server instance.
Install the new SQL Server instance: o o
For an SQL Server Express Edition, start the installation from the files downloaded from the Download Center.
For all other editions of SQL Server you can start the installation directly from your installation medium (DVD or iso image).
If the instance name is not to be changed and a previous SQL Server instance was uninstalled, then perform the installation with the same type
(default instance or named instance) and name (for a named instance), e.g. SQLSERVERVIEW for SQL Server Express edition.
Note the following when installing SQL Server Express:
Deactivate the option Hide advanced configuration options in the
Registration Information window, otherwise you will not be able to assign an instance name other than the default name SQLEXPRESS during the installation.
120 Installation under Windows
3.15 Upgrade installations of SQL Server l l l l l
Then attach the database as follows:
1. Open SQL Server Management Studio and connect to the new instance.
2. Select New Query and enter the following command in the Query window, where <data_path> is the path name of the ServerView database files on your system.
CREATE DATABASE ServerViewDB
ON PRIMARY (FILENAME='<data_path>\ServerViewDB.mdf')
LOG ON (FILENAME='<data_path>\ServerViewDB_log.LDF')
FOR ATTACH
Following the attachment, execute the following command to check the consistency and to update:
DBCC UPDATEUSAGE('ServerViewDB')
If you are using the SQL server as a remote SQL server for Operations
Manager, set up the user account as described in section
"Configuring a remote SQL Server" on page 92
. On the management station you will find the user account in the %windir%\ServerViewDB.ini file under Domain and Username.
Set up the user account under which the ServerView Services and
ServerView Download Service are registered in SQL Server as of 2008 as an authorized SQL administrator, see
"Adding a user account with SQL Server administrator rights" on page 83 .
If you are using SQL Server as of 2012 as a local SQL Server, also add the
LOCAL SYSTEM account as an authorized administrator.
Necessary actions after the upgrade
After the side-by-side upgrade of the instance, you must perform the following steps for all versions of SQL Server:
If you are using the SQL server as a remote SQL server for Operations
Manager, you must perform the additional actions on the management station, logging on as the user who is entered on there in the %windir%\ServerViewDB.ini file under Domain and Username.
1. For an Express Edition, check whether the service Windows Task Scheduler is started before you continue with the upgrade.
2. For all other editions of SQL Server: Check whether the service SQL Server
Installation under Windows 121
3 Installing ServerView Operations Manager
Agent <instance_name> is started.
3. Internal backup jobs of Operations Manager must now be set up again before you can restart Operations Manager.
The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView
Operations Manager installation: l
SQL Server Client tools must be installed and accessible via the
PATH environment variable in their default location on the
CMS:
<Program Files>\Microsoft SQL
Server\<version>\Tools\Binn\ with <version> in 90\100\110.
l l
The calling account must be a member of the sysadmin server role in SQL Server.
The Windows command prompt used to call the tool must be opened with full administrator rights.
Proceed as follows:
1. Open the input prompt.
2. Switch to the directory <installation_path>\ServerView Services
\scripts\ServerView\Tools.
3. Execute the following file, which is located in this directory: o o o
For SQL Server 2012 / SQL Server 2014:
SVCreateJobs_Upgrade2012
For SQL Server 2008:
SVCreateJobs_Upgrade2008
4. Answer the question Renamed SQL Server Instance [Y/N] ?
o
With N if the new SQL Server instance was installed under the same name.
o
With Y if the new instance was installed under a different name.
Then enter the new name at the following prompt:
Please enter new SQL Server Instance Name
4. The necessary upgrade steps for setting up the Operations Manager jobs are executed while this application is running and are logged in the log file
122 Installation under Windows
3.15 Upgrade installations of SQL Server
<DbApplicationFolder>\SVCreateJobs_Upgrade2012.log
or<DbApplicationFolder>\SVCreateJobs_Upgrade2008.log. You can find out the contents of the DbApplicationFolder parameter from the configuration file ServerViewDB.ini (in the <windir> directory).
5. After successful completion, start the services ServerView Services and
ServerView Download Service.
6. Then check in all cases whether the backup jobs for the ServerView database have been set up correctly and can be executed on your system: o
For SQL Server Express editions the jobs were set up via the Windows
Task Scheduler. You can check the jobs and the schedule via the relevant Windows user interface:
1. Open Control Panel – Scheduled Tasks. You will see a list of jobs and their schedules.
o
For all other editions of SQL Server you can use the SQL Server Agent service to set up the jobs. You can check the jobs and the schedule via
SQL Server Management Studio:
1. Start SQL Server Management Studio.
2. Click the SQL Server instance and select the entry SQL Server
Agent.
3. Under Jobs you will see the jobs that have been set up. You can view the current schedule for each job with View History.
3.15.2
Upgrading SQL Server 2012/2014 Express to SQL Server
2012/2014
You can perform the following upgrade installations: l
SQL Server 2012 Express instance to an SQL Server 2012 full version.
l
SQL Server 2014 Express instance to an SQL Server 2014 full version.
Because the upgrade installation is the same for both SQL Server 2012 and SQL Server 2014, it is described for both in this section. Below, the full edition is always referred to as SQL Server 2012/2014 and the express edition as SQL Server 2012/2014 Express.
An upgrade could be necessary if the maximum size of the ServerView database
(10 GB) is reached or if you want to use additional features or components of
Installation under Windows 123
3 Installing ServerView Operations Manager
SQL Server 2012/2014 full versions in your environment, which are not included in SQL Server 2012/2014 Express.
Preparing for installation
Before you perform an upgrade installation, you must make the following preparations: l
During the upgrade installation of SQL Server 2012/2014, the necessary hardware and software requirements are checked. For information on this, see the Microsoft website.
l l
Find out which edition updates of SQL Server 2012/2014 (Express) are supported by Microsoft by checking the online documentation for SQL Server
2012/2014 (Express).
If you require a particular feature or component in your environment, find out the functional scope of the edition to which you want to upgrade.
Note the following for the upgrade: l l l
Localized versions of SQL Server 2012/2014 Express can only be upgraded to localized versions of the same language or to the English version of SQL
Server 2012/2014.
It is recommended that you always install the latest service pack. After the upgrade you should always check whether any current updates are missing and install them if so.
An existing installation of SQL Server Management Studio (Basic) may have to be uninstalled and reinstalled for the new edition, as different editions of
SQL Server Management Studio cannot be installed side-by-side.
Necessary actions before the upgrade
1. Back up the databases of the installed instances.
2. Close all applications which have access to the relevant SQL Server
2012/2014 Express instance.
3. Stop all dependent services, in particular ServerView Services and
ServerView Download Service.
124 Installation under Windows
3.15 Upgrade installations of SQL Server
Performing the upgrade
The upgrade is performed by executing the SQL Server 2012/2014 Setup from the installation DVD.
1. Start the Setup for the target edition you require.
2. In the left window pane, select Maintenance and then select the option
Edition Upgrade.
3. The Installation Wizard for upgrading the edition opens.
4. When a number of preconditions have been verified, you must select in the
Select Instance window the instance you want to upgrade to the target edition. The instance name for a named SQL Server 2012/2014 used by
Operations Manager is SQLSERVERVIEW.
5. The program then checks whether an edition upgrade is possible, asks you to reconfirm in the Ready to upgrade edition window, and then performs the upgrade.
The successful upgrade is displayed in the following Complete window.
Necessary actions after the upgrade
1. Install any outstanding service packs, service-pack updates or hotfix updates for the new edition status.
2. Check whether the SQL Server (<instance_name>) service is started.
3. Check whether the SQL Agent (<instance_name>) service is started.
Before you can restart the ServerView services and Operations Manager, you must recreate internal backup and maintenance jobs for the ServerView database.
Installation under Windows 125
3 Installing ServerView Operations Manager
The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation: l
SQL Server Client tools must be installed and accessible via the
PATH environment variable in their default location on the CMS: l l
<Program Files>\Microsoft SQL Server\<version>\Tools\Binn\
(with <version> in 90\100\110).
The calling account must be a member of the sysadmin server role in SQL Server.
The Windows command prompt used to call the tool must be opened with full administrator rights.
Proceed as follows:
1. Open the input prompt.
2. Switch to the directory <installation_path>\ServerView
Services\scripts\ServerView\Tools.
3. Execute the file SVCreateJobs_Upgrade2012, which is located in this directory. During the execution, answer the question Renamed SQL Server
Instance [Y/N] ? with N.
All necessary upgrade steps are performed by this batch file and are logged in the log file <DbApplicationFolder>\SVCreateJobs_Upgrade2012.log.
You can find out the path for <DbApplicationFolder> from the configuration file ServerViewDB.ini (in the <windir> directory).
4. When the file has successfully executed, start the services ServerView
Services and ServerView Download Service.
5. Then always check whether the backup jobs for the ServerView database are set up on your system and can be executed. The jobs are set up using the SQL Server Agent service.
You can view the jobs via SQL Server Management Studio:
1. Start SQL Server Management Studio.
2. Click the SQL Server instance and select SQL Server Agent.
3. The jobs that have been set up are listed under Jobs. You can view the current schedule for each job with View History.
126 Installation under Windows
3.15 Upgrade installations of SQL Server
3.15.3
Upgrading SQL Server 2008 Express to SQL Server 2008
The description for SQL Server 2008 is also valid for SQL Server 2008 R2.
You can perform an upgrade installation of an SQL Server 2008 Express instance to an SQL Server 2008 full version. An upgrade could be necessary if the maximum size of the ServerView database (for SQL Server 2008 R2 Express: 10
GB, for SQL Server 2008 Express: 4 GB) is reached or if you want to use additional features or components of SQL Server 2008 full versions in your environment, which are not included in SQL Server 2008 Express.
Preparing for installation
Before you perform an upgrade installation, you must make the following preparations: l l
During the upgrade installation of SQL Server 2008, the necessary hardware and software requirements are checked. For information on this, see the
Microsoft website.
Find out which edition updates of SQL Server 2008 (Express) are supported by Microsoft by checking the online documentation for SQL Server 2008
(Express).
l
If you require a particular feature or component in your environment, find out the functional scope of the edition to which you want to upgrade.
Note the following for the upgrade: l l l
Localized versions of SQL Server 2008 Express can only be upgraded to localized versions of the same language or to the English version of SQL
Server 2008.
It is recommended that you always install the latest service pack. After the upgrade you should always check whether any current updates are missing and install them if so.
An existing installation of SQL Server Management Studio (Basic) may have to be uninstalled and reinstalled for the new edition, as different editions of
SQL Server Management Studio cannot be installed side-by-side.
Installation under Windows 127
3 Installing ServerView Operations Manager
Necessary actions before the upgrade
1. Back up the databases of the installed instances.
2. Close all applications which have access to the relevant SQL Server 2008
Express instance.
3. Stop all dependent services, in particular ServerView Services and
ServerView Download Service.
Performing the upgrade
The upgrade is performed by executing the SQL Server 2008 Setup from the installation DVD.
1. Start the Setup for the target edition you require.
2. In the left window pane, select Maintenance and then select the option
Edition Upgrade.
3. The Installation Wizard for upgrading the edition opens.
4. When a number of preconditions have been verified, you must select in the
Select Instance window the instance you want to upgrade to the target edition. The instance name for a named SQL Server Express 2008 instance used by Operations Manager is SQLSERVERVIEW.
5. The program then checks whether an edition upgrade is possible, asks you to reconfirm in the Ready to upgrade edition window, and then performs the upgrade.
The successful upgrade is displayed in the following Complete window.
Necessary actions after the upgrade
1. Install any outstanding service packs, service-pack updates or hotfix updates for the new edition status.
2. Check whether the SQL Server (<instance_name>) service is started.
3. Check whether the SQL Agent (<instance_name>) service is started.
Before you can restart the ServerView services and Operations Manager, you must recreate internal backup and maintenance jobs for the ServerView database.
128 Installation under Windows
3.15 Upgrade installations of SQL Server
The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation: l
SQL Server Client tools must be installed and accessible via the
PATH environment variable in their default location on the CMS: l l
<Program Files>\Microsoft SQL Server\<version>\Tools\Binn\
(with <version> in 90\100\110).
The calling account must be a member of the sysadmin server role in SQL Server.
The Windows command prompt used to call the tool must be opened with full administrator rights.
Proceed as follows:
1. Open the input prompt.
2. Switch to the directory <installation_path>\ServerView
Services\scripts\ServerView\Tools.
3. Execute the file SVCreateJobs_Upgrade2008, which is located in this directory. During the execution, answer the question Renamed SQL Server
Instance [Y/N] ? with N.
All necessary upgrade steps are performed by this batch file and are logged in the log file <DbApplicationFolder>\SVCreateJobs_Upgrade2008.log.
You can find out the path for <DbApplicationFolder> from the configuration file ServerViewDB.ini (in the <windir> directory).
4. When the file has successfully executed, start the services ServerView
Services and ServerView Download Service.
5. Then always check whether the backup jobs for the ServerView database are set up on your system and can be executed. The jobs are set up using the SQL Server Agent service.
You can view the jobs via SQL Server Management Studio:
1. Start SQL Server Management Studio.
2. Click the SQL Server instance and select SQL Server Agent.
3. The jobs that have been set up are listed under Jobs. You can view the current schedule for each job with View History.
Installation under Windows 129
3 Installing ServerView Operations Manager
3.15.4
Upgrading SQL Server 2005 Express to SQL Server 2005
You can upgrade the installation of an SQL Server 2005 Express instance to an
SQL Server 2005 full version.
An upgrade could be necessary, for example, if the maximum database size of the ServerView database (for SQL Server 2005 Express: 4 GB) is reached or if you want to use additional features or components of SQL Server 2005 in your environment, which are not included in SQL Server 2005 Express.
Preparing for installation
Before you perform an upgrade installation, you must make the following preparations: l l
During the upgrade installation of SQL Server 2005, the necessary hardware and software requirements are checked. For information on this, see the
Microsoft website.
l l
Find out which edition updates of SQL Server 2005 (Express) are supported by Microsoft by checking the online documentation for SQL Server 2005
(Express).
If you require a particular feature or component in your environment, find out the functional scope of the edition to which you want to upgrade.
Note the following for the upgrade:
Localized versions of SQL Server 2005 Express can only be upgraded to localized versions of the same language.
l
During the upgrade, the version status of the edition to be upgraded and the version status of the edition to be newly installed are checked.
If you have installed SQL Server 2005 Express with a current service pack, the status of this installation is already more up-to-date than the version status of the basic installation of the SQL Server 2005 edition to which you are upgrading.
To avoid this leading to warnings and abortion of the upgrade during the setup, you must start the installation of the new SQL Server 2005 edition with an additional calling parameter from the input prompt, see
"Performing the upgrade" on page 131
.
130 Installation under Windows
3.15 Upgrade installations of SQL Server l l
It is recommended that you always use the latest service pack. After the upgrade, you must therefore re-install all current service packs, service-pack updates or any hotfix updates for the upgraded edition.
If you have already installed SQL Server Management Studio Express on your system, and now also want to install the full version of SQL Server
Management Studio with the higher edition of SQL Server 2005, you must uninstall SQL Server Management Studio Express before the installation.
Side-by-side installation of SQL Server Management Studio Express and SQL
Server Management Studio is not possible.
Necessary actions before the upgrade
1. Back up the databases of the installed instances.
2. Close all applications which have access to the relevant SQL Server 2005
Express instance.
3. Stop all dependent services, in particular ServerView Services and
ServerView Download Service.
Performing the upgrade
You can perform the upgrade of the SQL Server 2005 Express instance directly as an "in-place" upgrade of the whole instance with all databases.
The upgrade is performed by executing the SQL Server 2005 setup from the installation DVD. The process is similar to a new installation but with the following changes:
1. Open the input prompt and navigate to the folder on your installation medium which contains the setup.exe file for the edition to be installed.
2. Start the installation from the input prompt with the parameter
SKUUPGRADE=1.
Example
<drive>:\<folder>\setup.exe SKUUPGRADE=1
3. In the Components to Install window, select at least the component SQL
Server Database Services. You can select additional components for installation which are not included in SQL Server 2005 Express.
Installation under Windows 131
3 Installing ServerView Operations Manager
4. In the Instance Name window, select the SQL Server 2005 Express instance to be upgraded for the upgrade. You can enter the name directly, or select it from a list which you get by clicking Installed Instances.
5. The installed components will be displayed in the Existing components window.
If the checkbox in front of the component name is selectable, the upgrade is possible. Select the checkbox and proceed with the upgrade.
If the checkbox is not selectable, you can click Details to display an additional error message explaining why the upgrade is not possible.
Necessary actions after the upgrade
1. Install any outstanding service packs, service-pack updates or hotfix updates for the new edition status.
2. Check whether the MSSQL$SQLSERVERVIEW service is started.
3. Check whether the SQLAgent$SQLSERVERVIEW service is started.
Internal backup and maintenance jobs of Operations Manager must now be recreated before you can restart Operations Manager.
The following prerequisites must be met to ensure correct functioning of the upgrade tool provided by the ServerView Operations Manager installation: l
SQL Server Client tools must be installed and accessible via the
PATH environment variable in their default location on the CMS:
<Program Files>\Microsoft SQL Server\<version>\Tools\Binn\
(with <version> in 90\100\110).
l l
The calling account must be a member of the sysadmin server role in SQL Server.
The Windows command prompt used to call the tool must be opened with full administrator rights.
Proceed as follows:
1. Open the input prompt.
2. Switch to the directory <Installation_path>\ServerView
Services\scripts\ServerView\Tools.
132 Installation under Windows
3.16 Installing Operations Manager on Windows Terminal Server/Remote
3. Execute the file SVCreateJobs_Upgrade2005, which is located in this directory.
All necessary upgrade steps for Operations Manager are performed by this batch file and are logged in the log file
<DbApplicationFolder>\SVCreateJobs_Upgrade2005.log.
You can find out the path for <DbApplicationFolder> from the configuration file ServerViewDB.ini (in the <windir> directory).
4. When the file has successfully executed, start the services ServerView
Download Service and ServerView Services.
5. Then check whether the backup jobs for the ServerView database have been set up and can be executed.
You can view the jobs via SQL Server Management Studio:
1. Start SQL Server Management Studio.
2. Click the SQL Server instance and select SQL Server Agent.
3. The jobs that have been set up are listed under Jobs.
3.16
Installing Operations Manager on Windows
Terminal Server/Remote Desktop Services
If the Terminal Services/Remote Desktop Services server role is installed, a special installation mode is required for installing Operations Manager.
Remote Desktop Services is known as Terminal Services in Windows
Server 2008 and earlier.
Installation on Windows Terminal Server/Remote Desktop Services
1. Click Server-Manager – Roles. If you see terminal services/Remote Desktop
Services, the Terminal Server/Remote Desktop Services role is installed.
2. Find out the path for the Operations Manager installation program:
1. Insert the ServerView Suite DVD 2.
2. Search for the file serverview.exe.
3. Note the path to file serverview.exe.
Installation under Windows 133
3 Installing ServerView Operations Manager
3. Install Operations Manager via the command prompt window:
1. Open a command prompt window and type:
Change user /install
2. Type the path name to the serverview.exe file in the same command prompt window and install Operations Manager.
3. After the installation, type in the command prompt window:
Change user /execute
General procedure with Operations Manager and Terminal Server/Remote
Desktop Services
It is recommended that you install Terminal Server/Remote Desktop Services before installing Operations Manager. Then install Operations Manager as described above.
If Terminal Server/Remote Desktop Services has been installed after Operations
Manager, please check whether Operations Manager is working well. If error messages appear, uninstall Operations Manager and execute the steps described above.
Installation of Operations Manager on Terminal Server/Remote Desktop Services with remote SQL Server is not supported
The installation mode described above does not apply when a remote SQL
Server is used.
134 Installation under Windows
3.17 Installation check list
3.17
Installation check list
Web browser
No. Check point
Configuration
1 Supported version
Supported Web browser for Windows is the following: l
Internet Explorer V9/V10 l
Mozilla Firefox V16/V17 or higher. For use with JRE 1.7.0_
45 or higher, Firefox as of V25 is required.
Supported Web browser for Linux is the following: l
Default Web browser released with distribution.
2 Trusted sites
If you use Internet Explorer, add the URL of SVOM into Trusted sites.
1. Open Internet Explorer.
2. Select Tools – Internet Options.
3. Click the Security tab and select Local intranet or
Trusted sites.
4. Click Sites and enter the URL of the server on which SVOM is installed.
3 Proxy It cannot access to SVOM via proxy. Disable to use proxy on
Web browser configuration.
4 32-bit/64bit
On 64 bit operating systems the 64 bit JRE can be used. But this can only be done together with the 64 bit Internet Explorer.
Otherwise a 32 bit JRE is necessary.
Table 1: Check list Web browser
Installation under Windows 135
3 Installing ServerView Operations Manager
Java Runtime Environment (JRE)
No. Check point
1
2
Supported version
32-bit/64bit
Configuration
V1.7.0_40 or higher. A client is also supporting V1.8.x.
JRE must be installed on both server side (system where
SVOM is installed) and client side.
You can use the same architecture of JRE as the system OS.
i.e. 32-bit version of JRE on 32-bit Windows, and 64-bit version of JRE on 64-bit Windows.
3 Java Plug-in
(only for
Windows)
Enable the next-generation Java Plug-in must be checked. This item is checked in default.
1. Open Java Control Panel.
2. Select Advanced tab.
3. Open Settings – Java Plug-in.
4. Make sure that Enable the next-generation Java
Plug-in is checked.
4 Security Configure security settings as follows:
1. Open Java Control Panel.
2. Select Advanced tab.
3. Open Settings – Security – Mixed code (sandboxed
vs. trusted security verification.
4. Check Enable - hide warning and run with
protections.
Set up the link for the plug-in to access from Linux by Firefox.
5 Symbolic link (only for Linux)
Table 2: Check list JRE
136 Installation under Windows
3.17 Installation check list
OS settings
No.
Check point
1
Configuration
host name resolve
Hostname of the CMS must be available to resolve from both
CMS itself (system where SVOM is installed) and client side.
Make sure that the name resolve is available by the following commands.
l l
Windows:
> tracert <hostname>.<DNS suffix>
Linux:
# traceroute <hostname>.<DNS suffix>
2
3
Network ports
SVOM uses some network ports. Which ports SVOM requires is described in
"Calling and ports used" on page 34
.
host name Hostname and DNS suffix of CMS must not contain underscore ('_').
4
5
6
SQL instance
(only for
Windows)
Active
Directory
Network drive
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, see
"Installation options for SQL Server" on page 43
.
Important: Please consider the notes in section
"Setting up a service account" on page 74 " for a local SQL Server and in
section
"Configuring a remote SQL Server" on page 92
for a remote SQL Server.
If you want to use Active Directory for directory service of
SVOM, Active Directory must be installed and configured for
SVOM before SVOM installation. When you install SVOM, the connection to Active Directory must be available.
Details of configuration of Active Directory are described in the "User Management in ServerView" user guide.
It is not possible to install SVOM to network drives.
Installation under Windows 137
3 Installing ServerView Operations Manager
No.
Check point
7 Terminal
Server
(only for
Windows)
8
9
/etc/hosts
(only for
Linux)
SELinux
(only for
Linux)
Configuration
If the Terminal Services/Remote Desktop Services server role is installed, a special installation mode is required for installing Operations Manager.
Details of how to install SVOM is described in
Operations Manager on Windows Terminal Server/Remote
.
localhost must be resolved to 127.0.0.1. It should be configured in /etc/hosts.
Disable SELinux on distributions on which it is not supported by SVOM.
Table 3: Check list OS settings
Update Installation
No.
Check point
1 Base version
Configuration
Update installation is only possible from version 6.00.06 or newer.
Table 4: Check list update installation
3.18
Installation process
As of Operations Manager version 6.10, the installation process has been changed. It now consists of three steps: l
Installation of SQL Server l l
For details see
"Installation options for SQL Server" on page 43
.
Installation of JBoss 7
Installation of ServerView Operations Manager
138 Installation under Windows
3.18 Installation process
Installation of JBoss 7
The start program serverview.exe calls the wizard Fujitsu ServerView JBoss
Application Server Setup to install JBoss 7. If you start an upgrade installation, the old JBoss version will be removed. An upgrade installation is only possible as of Operations Manager Version 6.00.06, ServerView Deployment Manager
Version 6.20.xx or ServerView Installation Manager Version 10.12.07.
The wizard contains the JBoss-relevant queries from the former installation procedure: l l
Destination Folder window. This window is only displayed during a new installation. JBoss 7 and ServerView Operations Manager software are installed in the same directory.
JBoss Service Logon Information window l l l l
Select Directory Server window
Directory Service Settings window
Administrative User Password window
Computer Details window
JBoss 7 is configured as the standalone service ServerView JBoss Application
Server 7, which is automatically started after the installation.
The entry Fujitsu ServerView JBoss Application Server is created under
Control Panel - Programs and Features to modify or uninstall JBoss 7.
The folder structure in the installation directory has been changed for JBoss 7.
For example, log files are located in the directory <installation_
path>/jboss/standalone/log and the configuration file is located in the directory
<installation_path>/jboss/standalone/svconf.
Installation of ServerView Operations Manager
After installation of JBoss 7, the installation wizard Fujitsu ServerView
Operations Manager Setup is started. The wizard contains the relevant windows for installing the ServerView Operations Manager software.
Installation under Windows 139
3 Installing ServerView Operations Manager
3.19
Menu-driven installation of Operations Manager software
The Operations Manager software (Operations Manager and Event Manager) can be installed under Windows under menu control.
On the ServerView Suite DVD 2, under SVSSoftware – Software – ServerView –
Windows – ServerView S2, you will find the serverview.exe file, which you use to start installation. If the Microsoft Installer is not yet installed on the computer, it will be installed now.
Installation and application language of Operations Manager on a Japanese operating system is Japanese by default. For all other operating system languages it is English. On installation via command line the language can be determined by the user, see
"Installing Operations Manager software via the command line" on page 209
.
If you copy the installation files and folders to your local disk and install from there, do not delete these setup files. Sometimes when executing a Modify installation you are prompted for the original media. In this case reuse the setup files or DVD.
Starting the installation procedure
1. Log on as a user with Windows administrator rights or, if using a remote SQL
Server instance, as a domain user with Windows administrator rights.
2. Place the ServerView Suite DVD 2 in the DVD-ROM drive. If the DVD does not start automatically, click the start.html file in the DVD’s root directory.
3. Select ServerView Software Products.
4. Select the desired language in the displayed window.
5. Select ServerView – Operations Manager.
6. Under ServerView Operations Manager Application (incl. ServerView
Event Manager and ServerView Operations Manager) start the
serverview.exe program.
7. Unpack the software to a directory of your choice.
8. Open Windows Explorer and switch to this directory.
140 Installation under Windows
3.19 Menu-driven installation of Operations Manager software
9. Start the program serverview.exe by double-clicking it.
The installation can also be done unattended (“silent“). For more information on silent installation, see
"Installing Operations Manager software via the command line" on page 209 .
SQL Server settings in case of a new installation
1. Once the program has started, the following window is displayed in case of a new installation:
Figure 4: Select SQL Server window
The program then checks whether an SQL Server Express with the instance name SQLSERVERVIEW or a full edition with any instance name in a version supported by SVOM are already installed on your system.
l
If no suitable SQL Server instance is found, you can select the option
Install free edition of SQL Server to install automatically SQL Server
2005 Express or SQL Server 2008 R2 (depending on your version of the
Windows Server Operating System). Then click Next.
l
The ServerView database will be installed locally on the management station into the SQL Server 2008 R2 Express or SQL Server 2005 Express instance with instance name SQLSERVERVIEW. Following this, the
Operations Manager Installation Wizard is automatically started.
Installation under Windows 141
3 Installing ServerView Operations Manager l l
If a suitable SQL Server instance is found on the local management station, you can use this local SQL Server instance. Select the option Use
existing local SQL Server and then click Next. You will be moved to the Operations Manager start page.
You can also use a remotely installed SQL Server instance. For further information, see
"Remotely on a different system" on page 48
.
Select the option Use existing remote SQL Server ... and then click
Next.
The Remote DB window opens:
142
Figure 5: Remote DB window
SQL Server Name
Name of the SQL Server instance. (With an unnamed default instance of SQL Server this is the name of the system.) The SQL
Server Name can be seen when opening the SQL Server
Management Studio: You will find SQL Server Name (e.g .
MYCOMPUTER\SQLSERVER1) under Server name in the first dialog box.
User Name
For this user name you must have set up a domain user account on the SQL Server, see
"Configuring a remote SQL Server" on page 92 .
Installation under Windows
3.19 Menu-driven installation of Operations Manager software
Domain Name
Name of the domain.
Password
Password for accessing the user name.
Now click Next.
2. Click OK.
Installing JBoss 7 via Fujitsu ServerView JBoss Application Server Setup wizard
1. The wizard also checks the installed product versions of Deployment
Manager and Installation Manager. If these versions are incompatible a message is displayed and the installation is aborted.
In the case of an upgrade installation from version 6.00.06 or higher, the following dialog box opens:
Click OK to start the removal. A progress window is displayed. Click Cancel to exit the wizard.
Installation under Windows 143
3 Installing ServerView Operations Manager
2. In the case of a new installation or after the removal the Fujitsu
ServerView JBoss Application Server Setup wizard opens.
3. With Next you initially go through general windows of the wizard which contain, for example, the license conditions and information on installation.
4. In the Destination Folder window, define the installation directory for
JBoss 7. This window is only displayed in the case of a new installation.
ServerView Operations Manager and JBoss 7 are always installed in the same installation directory. So if you are doing an upgrade installation, the installation directory already exists.
By default the software is installed in the following directory:
(32-bit OS): C:\Program Files\Fujitsu\ServerView Suite\
(64-bit OS): C:\Program Files(x86)\Fujitsu\ServerView Suite\
5. Click Next.
144 Installation under Windows
3.19 Menu-driven installation of Operations Manager software
6. Enter the user account for the JBoss service.
Figure 6: JBoss Service Logon Information window
Use LocalService?
This option is only available if you use a local SQL database. Select Yes if you want to use the built-in account LocalService for the ServerView
JBoss service. Otherwise click No.
Please be aware that the LocalService account has full access to the ServerView Operations Manager files. If another service is also running under this account, it can access the ServerView Operations
Manager files as well. It is recommended that you use a separate user account for the service.
User Name
For this user name you should have set up a standard user account with no special rights. Enter this user name.
If you use a remote SQL Server instance, the field is preset to the domain name, which you have specified in the Remote DB window
Installation under Windows 145
3 Installing ServerView Operations Manager under Domain Name. You can use a domain user account with no special rights.
Password
Password for accessing to the user name.
7. Select the directory server.
146
Figure 7: Select Directory Server window
ApacheDS installed with ServerView
Enable this option if you want to use the directory server ApacheDS.
If you enable this option, the directory server ApacheDS is automatically installed when you install ServerView Operations
Manager.
The Administrative User Password window opens, where you can specify the password for the administrative user svuser.
The password for svuser must not be an empty string.
Installation under Windows
3.19 Menu-driven installation of Operations Manager software
Other directory server
Enable this option if you want to use an already existing Active
Directory server.
Choose where the authorization is to be done.
Authorization on other directory server
The authorization is done on the other directory server.
So user authentication and user authorization are managed within the same "external" directory service (e.g. Active Directory).
For more information see the "User Management in ServerView" user guide.
Authorization on local ApacheDS
The authorization is done on the local ApacheDS.
The "internal" directory service of the ServerView Operations
Manager (ApacheDS) is used for managing the role assignments, whereas the "external" directory service (e.g. Active Directory) is only accessed for managing user authentication (unified RBAC management).
For more information about unified RBAC, see the "User
Management in ServerView" user guide.
If you enable this option, the directory server ApacheDS is automatically installed when you install ServerView Operations
Manager.
You must then make some more settings for the directory service, see below.
The Directory Service Settings window opens, where you specify the following parameters:
Host(FQN)
Fully-qualified name of the server on which the directory service is running.The fully-qualified name is an unambiguous name which specifies the system in the network. It is important that this name can always be properly resolved! This can be done via a DNS or NIS server, or through appropriate entries in the hosts file of the central management station. If you are not sure whether you
Installation under Windows 147
3 Installing ServerView Operations Manager ensure for a proper name resolution, you can issue the system's IP address here.
Backup Host(FQN)
Fully-qualified name for a backup directory server, which is configurable in the JBoss setup. The fully-qualified name is an unambiguous name which specifies the system in the network. It is important that this name can always be properly resolved! This can be done via a DNS or NIS server, or through appropriate entries in the hosts file of the central management station. If you are not sure whether you can ensure a proper name resolution, you can issue the system's IP address here.
Port
Port number used for access to the directory service. By default, port 389 is used for LDAP and port 636 is used for LDAPS (i.e. LDAP with SSL).
SSL
Yes is enabled by default to protect the data transfer with SSL encryption.
By default, 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, as the user passwords transferred via this connection are not separately encrypted. Bear in mind, however, that Microsoft Active Directory does not offer SSL encryption as standard; a certificate must be installed on the Windows server system for this purpose.
For further information, see section "Managing SSL Certificates on the CMS and managed nodes" and "Integrating ServerView user management into Microsoft Active Directory" in the "User
Management in ServerView" user guide.
Domain Name
Only if the option Authorization on local ApacheDS is selected
(unified RBAC management is configured).
Domain name of the Active Directory server.
148 Installation under Windows
3.19 Menu-driven installation of Operations Manager software
For further information, see section "Integrating ServerView user management into Microsoft Active Directory" in the "User
Management in ServerView" user guide.
You must enter this domain name in the login window of the
Central Authentication Service where you are asked to specify the authentication domain of your user account (see
"ServerView Operations Manager" user guide).
SVS Base DN
Base directory for the ServerView authorization data, e.g.:
OU=application,DC=fujitsu,DC=com
You can specify any directory in the Active Directory here. The
Operations Manager setup procedure generates an LDIF file for importing the authorization data, which you must then import after the Operations Manager installation. For further information, see section "Integrating ServerView user management into
Microsoft Active Directory" in the "User Management in ServerView" user guide.
User Search Base
Starting point for the user search in the directory server e.g.:
CN=Users,DC=fujitsu,DC=com
User Search Filter
Filter for user search.
User (read only account)
User ID for read access to the data. The user ID should only have basic read rights. This password is stored in a text file so only a user with simple read access should be chosen. The user ID should be specified in the notation USERNAME@DOMAIN, as displayed in the Active Directory in the user’s account settings under User logon
name.
Password / Confirm
Password for read access. The password which is written into the
sv-sec-config.xml file is stored encrypted.
Installation under Windows 149
3 Installing ServerView Operations Manager
In case of an upgrade or modify installation:
If the previous directory service also was Active Directory, the
Password / Confirm fields can be left empty. In this case, the previous password remains in effect.
Password Expiry Warning
No is enabled by default. In this case, expiry of user passwords will not be indicated when a user authenticates to CAS.
Select Yes and then click Next if you want configure that a user signing on to CAS is informed on an imminent password expiry.In
this case, the Password Expiration Settings dialog box opens,which allows you to configure the required parameters.
Selecting Yes and configuring the first three options in the
Password Expiration Settings dialog box enables the LDAP
Password Policy Enforcement (LPPE), which is disabled by default. LPPE handles a variety of login exceptions which would otherwise prevent user authentication. For more information see the manual "User Management in
ServerView".
Domain DN
Distinguished Name of the Active Directory domain, e.g.:
DC=fujitsu,DC=com
Valid Days
Number of days a password is valid (e.g. 90).
This value is used as default if no maxPwdAge attribute is found in Active Directory. A maxPwdAge value configured in Active Directory always overrides the value specified in the Valid Days field.
Warning Days
Number of days a user is warned before the password expires
(e.g. 60).
150 Installation under Windows
3.19 Menu-driven installation of Operations Manager software
There is no corresponding attribute in Active Directory.
Therefore, the Warning Days field is the only option for configuring the password expiry warning time.
Password URL (optional)
URL to which the user will be redirected in order to change the password.
Via the Test button you can test the settings by calling up the
ldapsearch command. You can see the result in the displayed DOS window.
8. The Computer Details window displays information about the computer.
Figure 8: Computer Details window
Computer
Name of the central management station.
DNS Suffix
DNS suffix used for JBoss configuration.
Installation under Windows 151
3 Installing ServerView Operations Manager
IP Address
IP address of the management station.
If any of these details change, you must perform a Modify installation to update the information, see
Operations Manager software" on page 161 .
9. Click Next. In the Ready to Install the Application window click Next to start the installation.
10. Click Finish to complete the installation. After installation of JBoss 7 the service ServerView JBoss Application Server 7 is started automatically.
Installation of the ServerView Operations Manager
1. After the JBoss 7 installation, the Fujitsu ServerView Operations Manager
Setup wizard opens.
2. With Next you initially go through general windows of the wizard which contain, for example, the license conditions and information on installation.
3. In case of an upgrade installation, an additional window is displayed providing you with important hints on the upgrade installation.
Important notes:
l
There is server and configuration data from a previous
ServerView installation. Please save the old data before performing this upgrade installation so that you can restore the data in case of a failure. Information about the old version can be found in C:\Windows\OldSVVersion.ini. Please read the release notes for further information.
l
Please clean the cache of the java plug-in on all systems on which you used a web browser for installing the old
ServerView version.
Additionally, the window allows you to specify whether to change the default settings for the internal trap that indicates changes of connectivity settings. As of Operations Manager V6.30, these default settings are preset to "enabled" (with one poll interval and no startup check). Prior to this,
"disabled" was the default.
152 Installation under Windows
3.19 Menu-driven installation of Operations Manager software
To change the value to "enabled" for all servers in the server list which have the old default value, select Yes. Otherwise select No.
The configured value is stored in the ServerView database and can be changed via the Base Configuration Wizard.
4. In the next window, select the SQL Server instance (
Server instances during Operations Manager installation" on page 47
) into which the ServerView database is to be installed.
Figure 9: SQL Server connection window
Installation under Windows 153
3 Installing ServerView Operations Manager
5. Select the setting(s) for the SQL Server database backup, see also
"Backing up the ServerView database" on page 175 .
154
Figure 10: SQL Server Backup window
typical
Leave the backup mode typical selected if the management station is not always running.
typical is equivalent to the SQL Server recovery model "simple".
advanced
Select advanced if you perform a lot of important monitoring functions with Operations Manager and the management station is nearly always running. advanced is equivalent to the SQL Server recovery model
"full".
Browse button
During a new installation, you can additionally specify under SQL
Server Backup Path a path under which the backup files of SQL Server are created. You can use the backup files if you have to restore the
Installation under Windows
3.19 Menu-driven installation of Operations Manager software
ServerView database, as described in
"Restoring the ServerView database" on page 185
.
In case your are using a locally installed SQL Server instance you see:
In case you are using a remotely installed SQL Server instance you see:
Installation under Windows 155
3 Installing ServerView Operations Manager
6. Define the installation type.
Figure 11: Select Installation Type window
Custom enables you to select individual Operations Manager products for installation as the Operations Manager Installation Wizard run progresses.
156 Installation under Windows
3.19 Menu-driven installation of Operations Manager software
7. The Select Features window below is displayed if you selected the installation type Custom. Select the management products you wish to install. With Complete you select them all. For an overview of which
ServerView components are installed, see
"ServerView Operations Manager components" on page 30
.
Figure 12: Select Features window
Installation under Windows 157
3 Installing ServerView Operations Manager
8. Enter a password for the user name for the ServerView Download Service.
Figure 13: Update Management Logon Information window
Refer to the "ServerView Update Management" user guide ("Prerequisites” section) to get more information about the logon.
158 Installation under Windows
3.19 Menu-driven installation of Operations Manager software
9. The Computer Details window displays information about the computer.
Figure 14: Computer Details window
SNMP Community
Management station’s community. This is important for receiving traps.
If any of these details change, you must perform a Modify installation to update the information, see
Operations Manager software" on page 161 .
Installation under Windows 159
3 Installing ServerView Operations Manager
10. Select the required integration into another Enterprise Management
System.
160
Figure 15: Select Enterprise Management Integrations window
This window is only displayed if Enterprise Management software was found on the management station.
The corresponding management system must already be installed on the management station so that the integration can be selected.
Further information on integrations is provided in the corresponding
ServerView Integration guides.
Installation under Windows
3.20 Modify installation of Operations Manager software
11. Start the installation.
Figure 16: Ready to Install the Application window
You start installation with Install >. < Back enables you to correct the details for installation if required. With Cancel you terminate the Operations
Manager Installation Wizard without any change being made.
In the last window of the Operations Manager Installation Wizard you are shown concluding information. Click Finish to complete the installation.
Edit/addition/deletion of ServerView-related files may give influences on operations. Make sure not to do any other operations than the ones explained in this documentation.
3.20
Modify installation of Operations Manager software
You choose a Modify installation if you want to install or uninstall a feature of
Operations Manager or if the computer name, the membership of a domain/workgroup, the IP address of the system, the directory service or the
Installation under Windows 161
3 Installing ServerView Operations Manager service account has been changed after the installation of ServerView Operations
Manager.
If you change the computer name, you must remove the managed server from the server list and add it again. Otherwise, the old computer name will be retained in the server list.
If you only want to change the passwords of the accounts for the services
ServerView JBoss Application Server, ServerView Services and ServerView
Download Service you should NOT execute a modify installation. Change the passwords for these services in Administrative Tools – Services. Wait at least 5 minutes after the restart of the JBoss service.
Please note that the installation account and the user names you add into the installation dialogs need access rights in the SQL Server instance. Either reuse the preset user names. Or refer to the "Setting up a service account" section corresponding to your SQL Server (in chapter
"Installing ServerView Operations
Manager" on page 29 ) if you use a local SQL Server or see
SQL Server" on page 92 , step 3 if you use a remote SQL Server or see
Manager installation without SQL Server "sysadmin" access" on page 100
if you have configured the SQL Server for enhanced security.
You see the used accounts in file %windir%\ServerViewDB.ini (see also section
"Further procedure on the management station" on page 109 ).
Proceed as follows:
1. Log on as a user with administrator rights or, if using a remote SQL Server instance, as a domain user with administrator rights.
2. Close every open window of Operations Manager, Event Manager and
Update Manager.
3. Select Control Panel – Programs and Features.
4. Select Fujitsu ServerView Operations Manager or Fujitsu ServerView
JBoss Application Server.
5. Click Change.
6. Enable the Modify option and click Next.
Modifying ServerView Operations Manager
1. The Select Feature window opens.
Select the features you would like to install or uninstall.
162 Installation under Windows
3.21 Upgrade installation of Operations Manager
2. In the Update Management Logon Information window, you can change the service account of the ServerView Download Service. This window is only displayed if in the Select Features window the feature ServerView
Update Manager was not set to Entire feature will be unavailable.
3. If you have removed the system from the domain, please clear the field
DNS Suffix in the Computer Details window.
4. Click Install.
5. Click Finish.
After a successful run of setup, you have to do the following action:
If you have ServerView Agents running on the system, you will need to restart the SNMP service, so that the agents work with the new IP address.
Modifying JBoss 7
1. In the JBoss Service Account window, you can choose whether you want to change the account of the ServerView JBoss service.
2. In the Select Directory Server window, you can select your directory server.
3. In the ApacheDS Administrative User window, you can select whether you want to change the password of the administrative user svuser in your
ApacheDS directory service.
The password for svuser must not be an empty string.
4. In the Computer Details window, you can change the computer details.
3.21
Upgrade installation of Operations Manager
If an older version of Operations Manager is already installed, you can perform an upgrade installation of Operations Manager. To execute an upgrade installation, proceed as described in section
Operations Manager software" on page 140 .
Installation under Windows 163
3 Installing ServerView Operations Manager l l
An upgrade installation to the current is only supported as of
Operations Manager version 6.00.06. The old JBoss version is then uninstalled automatically and the new one is installed. Certificates and user settings are taken over. Afterwards all ServerView Suite applications which use JBoss must also be upgraded.
Operations Manager requires Java Runtime Environment (JRE)
V1.7.0_40 or higher. Please ensure that these requirements are met before upgrading. To avoid a reboot, stop ServerView Services and the JBoss service first.
If an newer version of Operations Manager is already installed, you cannot perform an downgrade installation. To downgrade, you must uninstall the existing Operations Manager first.
Please note that the installation account and the user names you add into the installation dialogs need access rights in the SQL Server instance. Either reuse the preset user names or refer to the corresponding sections.
l l l
If you use a local SQL Server, refer to the "Setting up a service account" section corresponding to your SQL Server (in chapter
"Installing ServerView Operations Manager" on page 29 ).
If you use a remote SQL Server 2005, see
SQL Server" on page 92 , step 3.
If you have configured the SQL Server for enhanced security, see
"Operations Manager installation without SQL Server "sysadmin" access" on page 100 .
You see the used accounts in file %windir%\ServerViewDB.ini (see also section
"Further procedure on the management station" on page
Some windows are omitted during an upgrade installation, for example: l
The Select SQL Server, Remote DB and SQL Server Connection windows do not open.
The SQL Server must be the same as in the new installation.
You cannot switch between the local and remote SQL Servers.
164 Installation under Windows
3.22 Uninstalling the Operations Manager software l
The Destination Folder window does not open.
You cannot change the destination folder.
3.22
Uninstalling the Operations Manager software
If you want to uninstall a web component and then install an older version of the same component, you must first flush all caches.
l l l l l
Before you uninstall Operations Manager, you should make a note of the name of the SQL Server instance and the SQL Server edition from the configuration file ServerViewDB.ini (in the <windir> directory). The name of the instance is shown under Server_
Instance, and the edition under DbServerEdition.
Before you uninstall Operations Manager, it is recommended that you remove all report configurations of the Performance Manager according to the description in the "Performance Manager" user guide. If you do not remove them, there will be a discrepancy between Operations Manager and agents after Operations
Manager is installed again. Please check before removal whether there are any other Operations Manager installations which use these reports too.
If Virtual-IO Manager, Deployment Manager or Installation
Manager are still installed on the system, you will be asked to uninstall them first.
Do not stop the uninstallation while it is running. Please wait until the process is completed.
It is recommended to log in at the central management station with the account you used during installation. If not, it may occur that database ServerViewDB cannot be deleted. In this case you can delete it with SQL Server Management Studio by your own.
You see the Installation Account in file
%windir%\ServerViewDB.ini (see also section
"Further procedure on the management station" on page 109 ).
Installation under Windows 165
3 Installing ServerView Operations Manager
You uninstall the Operations Manager software via the Windows start menu:
1. Select Control Panel – Programs and Features.
2. To display the product versions on Windows Server 2008, select Choose
Details from the View menu.
3. Select the Version option and click OK.
First you must uninstall ServerView Operations Manager and then JBoss 7.
Uninstalling ServerView Operations Manager
1. Select Fujitsu ServerView Operations Manager.
2. Click Remove to remove the complete package.
Uninstalling JBoss 7
1. Select Fujitsu ServerView JBoss Application Server.
2. Click Remove to remove the complete package.
Uninstalling the SQL Server instance
If you are using the SQL Server instance SQLSERVERVIEW, you can then uninstall this instance.
If in the configuration file ServerViewDB.ini (in the <windir> directory) the entry for the edition (DBServerEdition) was Express Edition, proceed as follows:
1. Select the entry Microsoft SQL Server <version>.
2. Click Remove.
3. Select the instance SQLSERVERVIEW: Database Engine.
4. Uninstall the software.
If SQLSERVERVIEW is the only SQL Server instance, you can also uninstall the
Workstation Components/Shared Components. If you have installed SQL
Server Management Studio Express, you can uninstall this software.
With an SQL Server instance of an Enterprise/Standard/Workgroup Edition, you must first make sure that the SQL Server instance is not being used by another application. If it is not, you can uninstall it in the same way as for the
SQLSERVERVIEW instance.
166 Installation under Windows
3.23 ServerView services
Depending on your version of SQL Server, you can then uninstall Microsoft SQL
Server Native Client/SQL Server 2008 Native Client/SQL Server 2008 R2 Native
Client/SQL Server 2012 Native Client.
If you uninstalled the SQL Server accidentally you can install the same SQL Server edition with the same instance name (see in configuration file
ServerViewDB.ini the entry DBServerEdition and Server_Instance) and restore the ServerView database from backups as described in
ServerView database" on page 185
(restore additionally master database in case of a remote SQL Server and msdb database in case of a SQL Server full edition).
3.23
ServerView services
The following services are available for operating Operations Manager: l l
ServerView Download Service
ServerView JBoss Application Server 7
l l l
ServerView Services
MSSQL$SQLSERVERVIEW or SQL Server (SQLSERVERVIEW) or SQL
Server (MSSQLSERVER)
ServerView Apache Directory Server
Stopping/starting/restarting services
You can stop, start and restart the services:
1. Select Administrative Tools – Services.
2. Select the appropriate service and then select Stop, Start or Restart from the context menu.
Watchdog for ServerView Services
On Windows, the main service program AlarmService.exe watches the started subservices and, if one of them disappears, it is restarted.
Auto-restart of services
As of Operations Manager version 5.30, for the SQL Server Express instance with the name SQLSERVERVIEW, an automatic restart of the SQL Server service SQL
Server (SQLSERVERVIEW) or MSSQL$SQLSERVERVIEW is automatically configured for the event of failure.
Installation under Windows 167
3 Installing ServerView Operations Manager
You can check these settings:
1. Select Administrative Tools – Services.
2. Select the SQL Server service and select Properties from the context menu.
3. Select the Recovery tab. You will find the restart properties in the fields
First/Second/Subsequent failure.
For the Workgroup/Standard/Enterprise edition, you can manually configure the
SQL Server and SQL Server Agent services to restart automatically.
On failover cluster instances, auto-restart should not be enabled for these services.
You can choose one of three options for setting up auto-restart of the SQL Server and SQL Server Agent services.
1. Via the Windows Services Microsoft Management Console:
1. Select Administrative Tools – Services.
2. Select the services SQL Server (MSSQLSERVER) and SQL Server
Agent (MSSQLSERVER) and then select Properties from the context menu.
3. Select the Recovery tab. You will find the restart properties in the fields
First/Second/Subsequent failure. Set these fields to Restart the
Service and in the Reset fail count after: ... days field set e.g. to 1.
2. You can use the service controller command sc for a detailed setting of the delay time:
1. In the configuration file ServerViewDB.ini (in the <windir> directory) you will find the name of the SQL Server service under the entry
DbService and the name of the SQL Server Agent service under the entry DbAgent.
2. Open a command prompt window.
3. Check the current recovery settings via the following command: sc qfailure <Service>
<Service>
Value of the DbService and DbAgent parameters.
4. To get help, type: sc failure
168 Installation under Windows
3.24 Collecting diagnostics data
5. To configure the recovery action to automatic restart, type: sc failure <Service> reset= <failureResetPeriod> actions= restart/<delay_time>/restart/<delay_ time>/restart/<delay_time>
You must include a space after the equal sign (=).
3. You can activate a two-way control of the SQL Server and SQL Server Agent services. If both services are started and one of them fails, this service will be restarted by the other one. Configuration in SQL Server Management
Studio:
1. In Object Explorer, connect to Database Engine and Server name, and then expand that instance.
2. Right-click SQL Server Agent, and then select Properties from the context menu.
3. On the General page, check Auto restart SQL Server if it stops
unexpectedly and Auto restart SQL Server Agent if it stops
unexpectedly and then click OK.
3.24
Collecting diagnostics data
After Operations Manager is installed on the central management station, the
CmsCollect.bat script is available in the directory Programs - Fujitsu -
ServerView Suite. This script allows you to collect various diagnostics data (e.g.
information about JBoss, ServerView Services, log files). For diagnostic purposes you can send this file to your Fujitsu Customer Service Desk.
To collect the data, proceed as follows:
1. Switch to the directory Programs - Fujitsu - ServerView Suite.
2. To start the collection double-click the file CmsCollect.bat.
The result of the collection is stored in the zip file cmscollect.zip in the directory
...\ServerView Suite\svom\data.
Installation under Windows 169
170 Installation under Windows
4.1 Configuration file ServerViewDB.ini
4 ServerView database
Operations Manager requires an SQL database in an SQL Server.
You can use SQL Server versions 2005 / 2008 / 2008 R2 and 2012. Both Express edition and full editions are supported, depending on your system and installation requirements (see
"Installation options for SQL Server" on page 43
). It is recommended that you always use the current service pack. SQL Server 2008
R2 Express and SQL Server 2005 Express is supplied with the Operations Manager software.
4.1
Configuration file ServerViewDB.ini
The configuration file ServerViewDB.ini contains, among other things, information about the SQL Server instance, installation paths and the path names of the log files. The configuration file is located in the directory
%windir%. You must not modify the ServerViewDB.ini file. Sometimes you may need information from this file to execute some actions.
1. Press the Windows Logo key + [R] .
2. Enter the text %windir% in the Open field.
3. Click OK. A Windows Explorer window opens.
4. Scroll to the ServerViewDB.ini file and open it.
Installation under Windows 171
4 ServerView database
Figure 17: Example of an *.ini file
Important entries in the ServerViewDB.ini configuration file
You will find the following important entries in the ServerViewDB.ini configuration file: l l
Instance name of the database server: entry Server_Instance
This entry must be specified for <SQL Server_Instance>
Path for the database backup files: entry DbBackupPath l l l l l
Backup mode for the database: entry DbBackupMode
SQL Server version: entry DbServerVersion
SQL Server edition: entry DbServerEdition
Accounts: entries InstallationAccount, SqlServerViewServicesAccount,
SqlServerViewDownloadServiceAccount
Whether Operations Manager was installed on an SQL Server configured with enhanced security: entry SqlServerWithEnhancedSecurity
172 Installation under Windows
4.2 Connection to the ServerView database is interrupted
4.2
Connection to the ServerView database is interrupted
If the connection to the ServerView database is interrupted, e.g. in the case of
LAN problems, the following occurs: l l l
The ServerView Services service and, if present, the ServerView
Download Service service are stopped.
A message (see figure below) is written to the Windows event log.
If Operations Manager is running, the following screen is displayed:
Figure 18: Error message
Once the connection to the ServerView database has been restored, the services
ServerView Services and ServerView Download Service must be restarted manually:
1. Select Administrative Tools – Services.
2. Select the relevant service.
3. Select Start from the context menu.
Installation under Windows 173
4 ServerView database
4.3
Managing the ServerView database
The following programs are available for managing the ServerView database on
SQL 2014 /2012/2008/2005. The description for SQL Server 2008 also applies for
SQL Server 2008 R2 in this manual.
l
SQL Server Management Studio (Basic) for SQL Server 2014/ SQL Server
2012 / SQL Server Management Studio (Basic) for SQL Server 2008/SQL
Server Management Studio (Express) for SQL Server 2005
Graphical program. With the Enterprise/Standard/Workgroup Edition, this is a component of SQL Server and can be found on the Microsoft SQL Server installation DVD.
l
For SQL Server 2014 Express / SQL Server 2012 Express/SQL Server 2008
Express and SQL Server 2005 Express, there are edition variants that already contain a basic version of SQL Server Management Studio (SQL Server
2014/2012/2008 Express with Tools, SQL Server 2014/2012/2008/2005
Express with Advanced Services). The basic versions of the Management
Studio can also be downloaded from the Internet separately as installation packages and installed additionally or later. With a later installation, make sure you use the current service pack.
sqlcmd
The command line program sqlcmd is available after installation of SQL
Server full edition.
For management of the ServerView database, the SQL Server instance must be registered in the programs. In the configuration file ServerViewDB.ini (in the
<windir> directory) you will find the entry for the SQL Server instance under
Server_Instance=<SQL Server instance>.
174 Installation under Windows
4.4 Backing up the ServerView database
SQL Server Management Studio (Basic/Express)
To enter the SQL Server instance, proceed as follows:
1. Start Microsoft SQLServer <version> – SQL Server Management Studio
(Express).
2. In the Connect to Server dialog, select the server type Database Engine.
For the server name, select the instance name of the SQL Server.
3. Click Connect.
sqlcmd
To connect the SQL Server instance, proceed as follows:
1. Start the input prompt.
2. Enter the following command: sqlcmd -S <SQL Server instance> -E
4.4
Backing up the ServerView database
The ServerView database ServerViewDB is automatically backed up at regular intervals by backup jobs entered during the installation.
Please note:
Adjust the backup jobs for automatic backup of the ServerView database to the times when your system is running. The backup jobs will only be performed if the system is running. In the backup mode
advanced the backup jobs JobServerViewHourly and
JobServerViewLongInterval not only take care of the backup but also ensure that the ServerView database does not grow too big. In the backup mode advanced this backup jobs must be performed automatically from time to time.
The backups are performed online. The database services
MSSQL$SQLSERVERVIEW or MSSQLSERVER (for SQL Server 2014
/2012/2008/2005: SQL Server (SQLSERVERVIEW) or SQL Server
(MSSQLSERVER)) continue to run and the ServerView database remains accessible during the backup.
Installation under Windows 175
4 ServerView database
4.4.1
Backup jobs for the ServerView database
During the installation of Operations Manager you could select the SQL server backup mode typical or advanced. In the ServerViewDB.ini configuration file
(in the <windir> directory) you will find the selected backup mode under the entry DbBackupMode.
If you selected the backup mode typical during installation, you will have the backup job JobServerViewDaily. This job backs up the ServerView database every day, overwriting the previous day’s backup.
If you select the backup mode advanced, the following backup jobs will be available: l l l
JobServerViewDaily
Backs up the database every day, appending each backup to the previous day’s.
JobServerViewHourly
Backs up the transaction log every hour.
JobServerViewLongInterval
Backs up the database once a week, overwriting all previous backups.
Overview of the differences between backup modes:
SQL Server recovery model
Maximum data loss
Frequency of backups
Overhead for monitoring the backup jobs (see
"Editing and tracking the progress of the backup jobs" on page 178 )
Disk space usage
Backup mode
typical
Backup mode
advanced
simple
The data entered during one day full
The data entered during one hour
Once a day Hourly
Low Higher
Lower Higher
176 Installation under Windows
4.4 Backing up the ServerView database
Define a suitable execution time for the backup jobs when the system is normally running.
If you selected advanced backup mode, you should check from time to time whether the backup jobs JobServerViewHourly and
JobServerViewLongInterval are being executed, to prevent the log file
ServerViewDB_log.LDF from getting too big. If the file is growing rapidly, reduce its size, see
"Growth of the ServerViewDB_log.LDF file" on page 202
and follow the steps in the following paragraphs (
"Requirements for executing jobs" on page 177
to
"Checking the contents of the backup files" on page 184
).
The log file ServerViewDB_log.LDF is also generated in typical backup mode. It is automatically reduced in this mode, but not backed up.
As well as backing up the ServerView database onto hard disk, you should also save it to external media at regular intervals. Under Windows, use the backup program Administrative Tools - Windows Server Backup on Windows Server
2012 and Start – All Programs – Accessories – System Tools – Backup on
Windows Server 2008.
4.4.2
Requirements for executing jobs
For jobs to be executed, the following services must be running and the start type must be set to Automatic in Administrative Tools – Services: l
For SQL Server Express Task Scheduler.
l
For SQL Server Enterprise/Standard/Workgroup Edition the SQL Server agent
SQL Server Agent (MSSQLSERVER) for unnamed instances.
l
For SQL Server Enterprise/Standard/Workgroup Edition the SQL Server agent
SQL Server Agent (<INSTANCE NAME>) for named instances.
For the full versions of SQL Server you can list and manage the SQL Server Agent
Services via Program Files – Microsoft SQL Server <SQL Server version> –
Configuration Tools – SQL Server Configuration Manager:
Installation under Windows 177
4 ServerView database
In the ServerViewDB.ini configuration file (in the <windir> directory) you will find the name of the SQL Server agent under the entry DbAgent.
For the Express editions of SQL Server there is no SQL Server agent.
Job management is described in
"Editing and tracking the progress of the backup jobs" on page 178
.
4.4.3
Editing and tracking the progress of the backup jobs
Editing and tracking via a database management tool for full versions of
SQL Server (not SQL Server Express)
To view the schedule for the backup jobs, proceed as follows:
1. Start the SQL Server Management Studio.
2. Click the SQL Server instance and then select the entry SQL Server Agent.
3. Then click Jobs.
4. Select the appropriate backup job and then select Properties from the context menu.
In SQL Server Management Studio you can display the progress details for each job:
1. Under SQL Server Agent – Jobs, select all jobs or a specific one.
2. Select View History from the context menu.
178 Installation under Windows
4.4 Backing up the ServerView database
3. Select Properties from the context menu.
4. In the properties window select the Schedules link to adjust the schedule of a job if necessary.
5. Then click Edit. Adjust the schedule in the displayed window, by selecting an execution time for the job when the system is normally running.
Editing and tracking via Windows Explorer or task scheduler for SQL
Server Express editions
With SQL Server Express, the backup and maintenance jobs cannot be managed via SQL Server agent. This component does not exist for SQL Server Express. The jobs are set up via the Windows Task Scheduler and therefore can only be monitored via this component.
Windows Server 2012 and Windows Server 2008
1. In Administrative Tools select the entry Task Scheduler.
2. In the middle window, scroll down to the entry Task Status.
3. Double-click one of the JobServerView jobs. All ServerView jobs are shown in the middle window.
4. Click the History tab to view the progress of the job.
5. In the top part of the window, select a JobServerView job.
6. Select Properties from the context menu, followed by the Trigger tab.
Installation under Windows 179
4 ServerView database
7. Click Edit… and adjust the schedule, by selecting an execution time for the job when the system is normally running.
Tracking via Event Viewer on all editions of SQL Server
To view the scheduled execution of the database backup jobs, Windows Event
Viewer can be applied as follows:
1. Select Administrative Tools – Event Viewer.
2. Select Windows Log.
3. Select Application.
The following table shows the entries in the Windows Application Event Log written during the regular execution of the backup jobs dependent on the used
SQL Server.
For SQL Server Express:
Column Source Column
Event
ID
Description
MSSQL$SQLSERVERVIEW 18264
18265
Database backed up. Database:
ServerViewDB, pages dumped: …,
MEDIANAME='ServerViewDB':
{'ServerViewDBData'}). This is an informational message only. No user action is required.
MSSQL$SQLSERVERVIEW 17060 Windows Task Scheduler Job
'JobServerView…' invoked.
For SQL Server Enterprise/Standard/Workgroup Edition (in case of remote SQL
Server track on the remote SQL Server machine):
Column Source Column
Event
ID
Description
SQLSERVERAGENT or
SQLAgent$Instancename
208 SQL Server Scheduled Job 'JobServerView…'
… - Status: Succeeded - ….
180 Installation under Windows
4.4 Backing up the ServerView database
Column Source
MSSQLSERVER or
MSSQL$Instancename
Column
Event
ID
Description
18264
18265
Database backed up. Database:
ServerViewDB, …, pages dumped: …,
MEDIANAME='ServerViewDB':
{'ServerViewDBData'}). This is an informational message only. No user action is required.
You can create a filter for selective tracking.
4.4.4
Checking the existence of backup files
The ServerView database is backed up at regular intervals. This creates two files with the suffix .bak: l
ServerViewDBData.bak
Backup file of the ServerView database.
l
ServerViewDBLog.bak
Backup file of the transaction logs of the ServerView database. This is only created in advanced backup mode.
In the ServerViewDB.ini configuration file (in the <windir> directory) you will find the path of the files at the time of installation under the entry
DbBackupPath, and the setting for the backup mode under DbBackupMode.
Installation under Windows 181
4 ServerView database
The following applies only for installation with a remotely installed SQL
Server instance:
During installation of the Operations Manager software, you can specify the path for the backup files on the remote SQL Server in the SQL
Server Backup Path window. If you do not specify a path or if you executed an Operations Manager installation without SQL Server
"sysadmin" access and the installation account does not have the server role "diskadmin", the backup files will be created in the SQL Server default path. In this case the configuration file ServerViewDB.ini (in the <windir> directory) contains the entry default for DbBackupPath.
l
Default path for SQL Server 2005:
\Program Files\Microsoft SQL
Server\MSSQL.<n>\MSSQL\Backup\
l l l
<n>: Instance number
Default path for SQL Server 2005 (unnamed instance):
\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\
Default path for SQL Server 2008 (named instance):
\Program Files\Microsoft SQL
Server\MSSQL10.<Instancename>\MSSQL\Backup
Default path for SQL Server 2008 (unnamed instance): l l l
\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\Backup\
Default path for SQL Server 2008 R2 (named instance):
\Program Files\Microsoft SQL Server\MSSQL10_
50.<Instancename>.MSSQLSERVER\MSSQL\Backup\
Default path for SQL Server 2008 R2 (unnamed instance):
\Program Files\Microsoft SQL Server\MSSQL10_
50.MSSQLSERVER\MSSQL\Backup\
Path if the instance was upgraded from SQL Server or MSDE 2000:
\Program Files\Microsoft SQL
Server\MSSQL$SQLSERVERVIEW\BACKUP\
182 Installation under Windows
4.4 Backing up the ServerView database l l
Default path for SQL Server 2012 (named instance):
\Program Files\Microsoft SQL
Server\MSSQL11.<Instancename>\MSSQL\Backup\
Default path for SQL Server 2012 (unnamed instance):
\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\Backup\
l l
Default path for SQL Server 2014 (named instance):
\Program Files\Microsoft SQL
Server\MSSQL12.<Instancename>\MSSQL\Backup\
Default path for SQL Server 2014 (unnamed instance):
\Program Files\Microsoft SQL
Server\MSSQL12.MSSQLSERVER\MSSQL\Backup\
The path name is also displayed in SQL Server Management Studio.
SQL Server Management Studio
1. Start SQL Server Management Studio.
2. In the Connect to Server dialog, select the server type Database Engine and the server name <SQL Server_Instance>.
3. Click Connect.
4. Then in the Object Explorer select the entry Server Objects.
5. Click Backup Devices.
6. Select ServerViewDBData and then select Properties from the context menu.
7. The path name for the ServerView database backup file is displayed below the Destination field.
8. If you are using advanced backup mode, you can find out the path name for the transaction logs via Backup Devices – ServerViewDBLog –
Properties. The path name for the backup file of the transaction logs is displayed below the Destination field.
Installation under Windows 183
4 ServerView database
If you are using a remote SQL Server instance and nothing was specified for SQL
Server Backup Path during the installation, you can set up the following:
1. Click Backup Devices.
2. Select New Backup Device ... from the context menu.
3. Under Device name enter ServerViewDBData.
4. Click OK.
If you are using advanced backup mode, repeat these steps for the backup file
ServerViewDBLog.
4.4.5
Checking the contents of the backup files
You can check what the backup jobs have written to the backup files. You can also view the number of data records etc. in the backup files.
If you are using a remote SQL Server instance, you can do the check if the backup media ServerViewDBData and ServerViewDBLog are displayed in the
Management Studio. Otherwise you can set them up as described above and then proceed with the contents check.
You have the following options for the check:
1. Start SQL Server Management Studio (Express):
2. Click the SQL Server instance.
3. Click Server Objects.
4. Click Backup Devices.
5. Select a backup device.
6. Select Properties from the context menu.
7. Select the Media Contents tab.
184 Installation under Windows
4.5 Restoring the ServerView database
By advanced backup mode please check from time to time that the device ServerViewDBLog only contains one week’s worth of records.
When a week has passed, ServerViewDBLog must be overwritten from the beginning.
If this is not done, the backup job JobServerViewLongInterval did not run. In this case, start the backup job JobServerViewLongInterval.
This causes the *.bak files to be reduced.
If the log file ServerViewDB_log.LDF has grown very big, reduce its size as described in
"Growth of the ServerViewDB_log.LDF file" on page
For permanent, automatic execution of backups and reduction of file size, follow the steps described in
"Requirements for executing jobs" on page 177
and the subsequent sections.
4.5
Restoring the ServerView database
In the event of an error, you can restore the ServerView database from the backups. If you detect any errors during the process, you can restart the restoration from the beginning.
For the restoration, you must first read in the database backup and then, if available, one or more transaction log backups.
Backups of transaction logs are available if, in the ServerViewDB.ini file (in the
<windir> directory), the entry DbBackupMode is set to advanced.
For information on the directory for the database backup, see
"Checking the existence of backup files" on page 181 .
4.5.1
Restoration via SQL Server Management Studio
You should only restore the ServerView database from backup files to the same
Operations Manager version. The SQL Server version must either be the same or higher on the server where the backup is restored.
If you restore to the wrong version, Operations Manager will not work, either immediately or after the next upgrade installation. Please note: Restoring the database requires membership in the "sysadmin" server role of SQL Server.
Installation under Windows 185
4 ServerView database
Find out the version of the installed Operations Manager:
1. Select Control Panel – Programs and Features.
2. Select Fujitsu ServerView Operations Manager.
Find out the Operations Manager version in the backup files:
3. Restore the backup files into a test database, see
"Checking the database backup " on page 191 . Please make sure there is enough disk space, as the
files RECOVERYTEST.mdf and RECOVERYTEST.LDF will be created.
4. Start SQL Server Management Studio.
5. Connect to the SQL Server instance.
6. Select Databases – RECOVERYTEST.
7. Select Tables – dbo._Property.
8. Select Open Table or Select Top 1000 rows from the context menu.
9. See row ParentVersion. Is the value in column Value the same as the installed Operations Manager version determined before?
If this is true, the first prerequisite for restoring is achieved.
Find out the installed SQL Server version:
10. Select the New Query button and type: select @@version
GO
Find out the SQL Server version in the backup files:
11. Select Databases – RECOVERYTEST.
12. Select Properties from the context menu.
13. Select Options.
In field Compatibility level you see the SQL Server used during backup.
14. If the value of @@version is the same or higher than the value in the field
Compatibility level the second prerequisite is achieved and restoration can be executed.
186 Installation under Windows
4.5 Restoring the ServerView database
To restore the ServerView database and, if available, the transaction logs, proceed as follows:
1. Restrict the access to the ServerView database.
1. Start SQL Server Management Studio.
2. Connect with the SQL Server instance and select Databases –
ServerViewDB.
3. Select Properties from the context menu.
4. Select the Options page and, under Restrict Access, select the entry
RESTRICTED_USER. Click OK followed by YES.
2. The services ServerView Services, ServerView JBoss Application Server 7 and ServerView Download Service must be stopped:
1. Select Administrative Tools – Services.
2. Select the appropriate service and then select Stop from the context.
3. Restore from the database backup:
1. Click Databases and then select Restore Databases … from the context menu.
Installation under Windows 187
4 ServerView database
2. The Restore Databases window opens:
188
1. On the General page, enter the name ServerViewDB or msdb in the To database field or select the name from the list.
2. Select the option From device.
3. Click the ... button.
4. Add the database backup ServerViewDBData.bak from the appropriate storage location and then click OK.
3. Select the database backup to be restored:
In Select the backup sets to restore, click the box in the Restore column.
4. Switch to the Options page.
5. Select the options Overwrite the existing database.
6. If no transaction log backup ServerViewDBLog.bak is available, click
OK. Otherwise, select the option Overwrite the existing database
and Leave database nonoperational and do not roll back
Installation under Windows
4.5 Restoring the ServerView database
uncommitted transactions. Additional transaction logs can be
restored.
7. Click OK and then OK again.
Restoration of the database begins. In the Object Explorer you will see the message ServerViewDB (Restoring…).
4. Restore the transaction logs, if available:
1. Click Databases and then select Restore Databases … from the context menu.
2. The Restore Database window opens.
3. On the General page, in the To Database field select the name
ServerViewDB from the list.
4. Select the option From Device.
5. Click the ... button.
6. Add the transaction log file ServerViewDBLog.bak from the appropriate storage location and then click OK.
7. Select the database backup to be restored:
In Select the backup sets to restore, click the box in the Restore column.
8. Switch to the Options page.
9. Select the option Overwrite the existing database.
If you want to restore further transaction logs, select the option Leave
the database non-operational and do not roll back uncommitted
transactions. Additional transaction logs can be restored.
If you want to restore the last transaction log, select the option Leave
the database ready to use ... Additional transaction logs cannot
be restored.
10. Click OK and then OK again.
Once the last transaction log has been restored, the database status must be normal again. The add-on (Restoring…) is no longer displayed in the
Object Explorer.
Installation under Windows 189
4 ServerView database
If the backup has been restored from a different system you have to adapt the JBoss Service Logon:
1. Find out the value of the Server_Instance parameter in the configuration file ServerViewDB.ini. The configuration file is located in the <windir> directory.
2. Find out the value of <server_name\user_name> and use it in the next step:
1. Open Administrative Tools - Services and scroll to the service
ServerView JBoss Application Server 7. Column Log On As contains the required value.
3. Open SQL Server Management Studio and connect to <Server_
Instance>:
1. Select Security - Logins.
Look for <server_name>\<user_name> and note the spelling and upper and lower case.
2. Select Databases - ServerViewDB- Security - Users.
If you can find <server_name>\<user_name> click the New Query button, type the following command (type the [] brackets literally and pay attention to the correct spelling) and press the Execute button:
USE ServerViewDB
ALTER USER [<server_name\user_name>] WITH LOGIN =
[<server_name\user_name>];
GO
If you cannot find <server_name>\<user_name> click the New
Query button, type the following command (type the [] brackets literally and pay attention to the correct spelling) and press the
Execute button:
USE ServerViewDB
CREATE USER [<server_name>\<user_name>];
GO sp_addrolemember 'db_owner', [<server_name>\<user_ name>];
GO
190 Installation under Windows
4.6 SQL Server Express - database limit
The services ServerView Services, ServerView JBoss Application Server 7, and
ServerView Download Service must be restarted:
1. Select Administrative Tools – Services.
2. Select the appropriate service and then select Restart from the context menu.
Please wait about five minutes until all JBoss processes are completely restarted.
It is now possible to access the ServerView database via Operations Manager again.
4.5.2
Checking the database backup
From time to time you can check the backups with SQL Server Management
Studio. Follow the instructions in the sections on restoration under Windows
(
"Restoration via SQL Server Management Studio" on page 185
) but with the following changes: l l
Call the Restore Database... dialog.
On the General tab, enter any name in the To Database field, e.g.
RECOVERYTEST.
Make all other entries as described in the relevant sections of the previous sections. Afterwards, the database should have been restored under the name
RECOVERYTEST. You can check this as follows:
1. Click the SQL Server instance and select Databases.
2. Select Refresh from the context menu.
The database RECOVERYTEST must be displayed in the list.
You can then delete the database RECOVERYTEST as follows:
1. Select the database and then select Drop from the context menu.
4.6
SQL Server Express - database limit
When you install the Operations Manager software, you can also install SQL
Server Express editions as the database server. These database servers are free of charge but have some restrictions, including the maximum available database size. This is:
Installation under Windows 191
4 ServerView database l l l
For SQL Server 2005 Express: 4 GB
For SQL Server 2008 Express: 4 GB
For SQL Server 2008 R2 Express: 10 GB l l
For SQL Server 2012 Express: 10 GB
For SQL Server 2014 Express: 10 GB
If you are monitoring more than the recommended number of servers with
ServerView Operations Manager, and, for example, a lot of Threshold or
Inventory Management data is produced, you may find that the ServerView database limit is reached.
If this happens, you cannot continue working with ServerView Operations
Manager until you have taken certain measures, see
Operations Manager" on page 192
and
"Measures for solving the problem" on page 192
.
4.6.1
Monitoring measures in Operations Manager
As of Operations Manager version 5.0, a monitoring job
(JobServerViewCheckDBSize) is set up for the database for Operations
Manager SQL Server Express editions.
This job checks the database size at regular intervals and causes appropriate error messages to be written to the error files of SQL Server. In addition, a message is displayed in the Operations Manager interface if the database size is approaching a critical limit. By default the job is activated once an hour.
The job is set up via the Windows Task Scheduler. This means that the job and its runtime schedule can be controlled via the user interface of the Windows Task
Scheduler.
4.6.2
Measures for solving the problem
To solve the problem you can do the following: l l
Upgrade SQL Server to an edition with no size limit, e.g. SQL Server Standard or SQL Server Enterprise edition.
Delete servers from the ServerView server list to gain more storage space.
192 Installation under Windows
4.7 Moving the ServerView database from local to remote SQL Server
It is recommended that you upgrade SQL Server to a full version. This will permanently solve the problem and enable Operations Manager to monitor any number of servers. Bear in mind, however, that SQL Server full versions require a license. This means that the software is chargeable and the corresponding license has to be purchased from
Microsoft.
By default, SQL Server is not configured to reduce the database size automatically when data is deleted. Additionally, you will have to shrink the database following the deletion. This can be done via SQL
Server Management Studio. Please refer to the SQL Server documentation from Microsoft, chapter "How to: shrink a database
(SQL Server Management Studio)" in this case.
Please observe the required permissions in MS SQL Server. Shrinking a database requires membership of the "sysadmin" server role or at least the "db_owner" database role for the database "ServerViewDB". It is recommended to log in to SQL Server Management Studio with
"sysadmin" access.
An SQL Server 2008/2005 Express can alternatively be updated to an SQL Server
2008 R2/2012 Express edition. Although SQL Server Express also has a size limit for the database, this limit is 10 GB instead of 4 GB and SQL Server Express editions are available free of charge.
4.7
Moving the ServerView database from local to remote SQL Server
ServerView Operations Manager supports a remote SQL Server instance to install the ServerView database. The ServerView Operations Manager setup does not support the movement of an already local installed ServerView database to a remote SQL Server, but it may be configured by the customer as described below.
For the move you must upgrade the existing ServerView Operations Manager installation to the current version status. At least version 4.92 is required.
Installation under Windows 193
4 ServerView database
This description refers to the installation of ServerView Operations
Manager only. Other installed components (such as ServerView Update
Manager, ServerView Deployment Manager) must in any case be reinstalled after the move.
The local management station and the remote server must both belong to the same domain. You also require at least one domain user account in the Domain
Users group.
4.7.1
Requirements on the remote server
The SQL Server version must either be the same on both systems used or must be higher on the remote server than on the local server.
On the remote server, proceed as described in
.
4.7.2
Configuration steps
To move the ServerView database from the local management station to the remotely installed SQL Server, proceed as follows:
1. Upgrade the local ServerView Operations Manager installation:
Log onto the management station as the local administrator. Upgrade the local ServerView Operations Manager installation to the current version. It is absolutely essential to use the same version intended for the remote installation. Otherwise the database schema will not fit.
2. Stop all applications and services with access to the ServerView database, especially the following services: l
ServerView Services
l
ServerView Download Service
l
ServerView JBoss Application Server 7
3. Save the following folders of the current local installation; a copy of this data is needed because uninstallation/reinstallation will have to be performed later on: l l
ServerView Suite\svom\data\ServerView\SnmpExport\Logs
ServerView Suite\svom\data\ServerView\SnmpExport\ExportedData
194 Installation under Windows
4.7 Moving the ServerView database from local to remote SQL Server l l l l l l
ServerView Suite\svom\data\ServerView\SnmpExport\Tasks
ServerView
Suite\svom\data\ServerView\SnmpInventory\InventoryTasks
ServerView Suite\svom\data\ServerView\InventoryArchives
ServerView Suite\svom\data\ServerView\Download\svtmpdir
ServerView Suite\svom\data\ServerView\Download\Tasks
ServerView Suite\svom\data\ServerView\OnlineUpdate\Logs
l l l l l
ServerView Suite\svom\data\ServerView\OnlineUpdate\Tasks
ServerView
Suite\svom\data\ServerView\SnmpArchive\ArchiveTasks
ServerView Suite\svom\data\ServerView\SnmpArchive\Logs
ServerView Suite\svom\data\ServerView\Archive
ServerView Suite /svom/data/ServerView/CSVFiles
l
ServerView
Suite/ServerView/ServerViewServices/scripts/ServerView/common/ mibs
4. Detach and copy the ServerView database from the local SQL Server instance:
The current SQL database must now be copied from the local server.
Proceed as follows:
1. Determine the current path for the ServerView database files. The path is displayed in SQL Server Management Studio within the context menu of database – ServerViewDB – Properties – Files.
2. Detach the database using the corresponding SQL Server administration tools with the following functions:
Tasks – Detach (SQL Server Management Studio)
3. The database files ServerViewDB.mdf and ServerViewDB_log.LDF are now removed from the instance and ready to be copied.
4. Copy the database files to another folder. You will need these files later to replace the ServerView database on the remote SQL Server instance.
Installation under Windows 195
4 ServerView database
5. Uninstall the local ServerView Operations Manager installation:
The locally installed ServerView Operations Manager must now be uninstalled on the management station. In order to work correctly without error messages, the ServerView database must be temporarily re-attached to the instance from its original path. Attach the database with the corresponding SQL Server administration tools from the context menu of
databases. The current path to the database file (ServerViewDB.mdf) must be specified in the dialog Attach (SQL Server Management Studio).
Perform the uninstallation, see
"Uninstalling the Operations Manager software" on page 165
.
6. New installation with remote SQL Server
Now start a new installation of ServerView Operations Manager on the management station and choose the option Use existing remote SQL
Server. Proceed as described in
"Further procedure on the management station" on page 96
.
7. Replace the ServerView database on the remote SQL Server:
Following installation, the ServerView database on the remote server must now be replaced with the database previously copied from the local installation. Proceed as follows:
1. Stop all applications on the management station and services with access to the ServerView database, especially services ServerView
Services ,ServerView Download Service and ServerView JBoss
Application Server 7.
2. Open SQL Server Management Studio on the remote SQL Server and connect to the remote instance.
3. Get the current path for the ServerView database.
4. Detach the existing database on the remote SQL Server as described above for the local database.
5. Replace the database files with the corresponding files copied from the local server.
6. Re-attach the database.
8. If the database was upgraded from an earlier SQL Server version during migration, it is recommended that you run the following command on the
196 Installation under Windows
4.7 Moving the ServerView database from local to remote SQL Server upgraded database (via Management Studio):
DBCC UPDATEUSAGE ('ServerViewDB')
9. In case your remote installation was performed with "sysadmin" access, you have to adapt the JBoss Service Logon Information window. If a different domain user account was used than for the ’remote’ installation, the JBoss user account in the migrated database must be entered again:
1. Find out the value of <JBoss Accountname> and use it in the next steps:
Open Administrative Tools - Services and scroll to the service
ServerView JBoss Application Server 7. Column Log On As contains the required value.
2. Find out the value of the Server_Instance parameter in the configuration file ServerViewDB.ini.
3. Open SQL Server Management Studio:
Connect with <Server_Instance>.
Select Security - Logins.
Look for <JBoss Accountname> and note spelling and upper and lower case.
4. Log in at the central management station and switch to the directory
<Installation_path>\ServerView Services\scripts\ServerView\Tools.
5. Execute the following batch file located in this directory and apply the
<JBoss Accountname>:
GrantLoginJBoss.bat
10. If your remote installation was performed without "sysadmin" access, you must check and possibly add any domain accounts used for ServerView services in the migrated database:
1. Find out the accounts needed and use them in the next step: Open
Administrative Tools - Services and note the accounts used for
ServerView Services, ServerView Download Service and ServerView
JBoss Application Server 7.
2. Open SQL Server Management Studio and connect to the SQL Server instance. Check that these accounts are present under Security -
Logins and note the spelling in correct upper and lower case.
Installation under Windows 197
4 ServerView database
3. Log in on the central management station and switch to the following directory:
<Installation_path>\ServerView Services\scripts\ServerView\Tools
4. Execute the following batch file located in this directory and apply the account names noted in the step above:
GrantLoginSecure.bat.
NOTE: You will have to call the batch file separately for each account.
11. Back up the database on the remote SQL Server instance.
12. Copy the folders saved from the previous installation (as specified in step 3) to the corresponding folders on the local management station.
13. Finally, restart the services ServerView Services, ServerView JBoss
Application Server 7 and ServerView Download Service on the local management station.
Please wait about five minutes until all JBoss processes are completely restarted.
4.8
Changing the load distribution
ServerView allows you to influence the system load it incurs or the number of concurrent jobs.
The following services start jobs whose concurrent number may be defined in an
ini file.
ArchiveService
ExportService
<scripts>/ServerView/SnmpArchive/SVArchiveServer.ini
<scripts>/ServerView/SnmpExport/ExportServer.ini
InventoryService <scripts>/ServerView/SnmpInventory/ SVInventoryServer.ini
<scripts>: directory <Installation_path>/ServerView Services/scripts
Each of these configuration files holds a variable ConcurrentJobsAllowed in the section GLOBALS. 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 the server list. If ConcurrentJobsAllowed is set to 30 in
198 Installation under Windows
4.8 Changing the load distribution
SVArchiveServer.ini, there will always be at most 30 servers being archived at the same time. Once archiving is finished for one server of the 30 started jobs, then archiving for another server is started. This is repeated until all
100 servers are archived.
The current default values for ConcurrentJobsAllowed are:
SVArchiveServer.ini
DownloadServer.ini
30
30
ExportServer.ini
100
SVInventoryServer.ini 10
If you upgrade the Operations Manager software, the value for
ConcurrentJobsAllowed parameter will be reset to the default value.
1. Before changing the number of ConcurrentJobsAllowed:
Before changing the number of ConcurrentJobsAllowed, please ensure that no jobs of the respective service are running. For
ArchiveService, DownloadService and ExportService this can easily be verified via the respective GUI in the tab settings. If there are blue arrows displayed for the status of a task then a job is running for the server.
For InventoryService please check in the process list whether a process called SVSnmpInventory is running. In Linux you can view the process list via the command ps.
2. Effect of reducing the number of concurrent jobs:
Reducing the number of concurrent jobs has two effects: On the one hand it reduces the system load; on the other it increases the time required by a job to process a group of servers.
Installation under Windows 199
4 ServerView database
4.9
Error diagnostic
In the event of an error in the ServerView database, you can send various files and information to your Fujitsu Customer Service Desk for error diagnostics.
4.9.1
Log file
If an error occurs during installation of the ServerView database, send the following log files: l l
%TEMP%\serverview.log
%TEMP%\SVSqlServer.log
l l l
%TEMP%\serverview_list_instances.txt
<DatabaseLog>\svsqldb.log
<DatabaseLog>\svsqldbERROR.log
l
%windir%\ServerViewDB.ini
If an installation error occurs with Wise SQL Scripts or during file import with bcp, zip the <DiagnosePath> directory. If an error occurs while ServerView is connecting to the ServerView database, send the current log files *.log located in the <SVCommon> directory.
Replace the relevant environment variable (%TEMP% and %windir%) with its value. On all Windows operating systems the value of the variable is displayed via the input prompt with the set command.
You get the wildcards in the square brackets by entering the following commands via the input prompt: type %windir%\ServerViewDB.ini | findstr /B DatabaseLog type %windir%\ServerViewDB.ini | findstr /B DiagnosePath type %windir%\ServerViewDB.ini | findstr /B SVCommon
200 Installation under Windows
4.9 Error diagnostic
To make the folders of the log files visible it may be necessary to configure
Windows Explorer:
1. In the menu bar select Tools – Folder Options – View Tools.
2. In Advanced Settings configure:
1. Activate the Show hidden files and folders option.
2. Deactivate the Hide extensions for known files types option.
3. Deactivate the Hide protected operating system files
(Recommended) option.
4.9.2
Important information in the event of an error
In the event of an error, the following information is important: l
Operations Manager version
Click the entry Fujitsu ServerView Operations Manager under Software and then click the support information.
l l l
Operating system version
Open Windows Explorer and select About Windows from the help menu.
Operating system language
List instance name, edition, version, service pack, language of all installed and running SQL Server instances.
Enter the following command at the command prompt:
%TEMP%\serverview_osql.bat
Or enter the following command at the input prompt: sqlcmd -S <SQL Server instance> -E select @@version
GO
Installation under Windows 201
4 ServerView database l
Details similar to the following are displayed:
Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright © 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack
3)
Installed language
Enter the following command at the input prompt: sqlcmd -S <SQL Server instance> -E xp_msver language
GO
4.9.3
Growth of the ServerViewDB_log.LDF file
If in advanced backup mode the backup jobs, as described in
ServerView database" on page 175 , do not run regularly or have not run for a
while, the transaction log file ServerViewDB_log.LDF may become very large.
In this case it may have to be reduced in size, which you must do manually.
In typical backup mode, the absence of the backup jobs means that
ServerViewDB_log.LDF no longer grows.
Please observe the required permissions in the SQL Server for this task.
Shrinking a database requires membership in the "sysadmin" server role or at least in the db_owner database role for the database
ServerViewDB. It is recommended to perform the following process as a member of the "sysadmin" server role.
Proceed as follows:
1. Check the size of the ServerViewDB_log.LDF file.
The file is located in the Data folder of SQL Server. The location of this folder depends on the version of SQL Server used. You may verify the location of the data folder either with SQL Server Management Studio or with SQL
Server Configuration Manager.
202 Installation under Windows
4.9 Error diagnostic
If you use SQL Server Configuration Manager:
1. Open the tool:
Select ( Microsoft SQL Server <version> – Configuration Tools –)
SQL Server Configuration Manager.
2. Select the instance:
Click SQL Server <version> Services, for instance SQL Server 2005
Services. In the details pane, then right-click the instance name queried for, for example: SQL Server (SQLSERVERVIEW)
3. Get Properties:
From the drop down list for the service, select Properties. Then select the Advanced tab.
The default path to the data folder is: l
For instances of SQL Server 2005:
\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data
l
Example
\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
For instances of SQL Server 2008:
\Program Files\Microsoft SQL
Server\MSSQL10.Instancename\MSSQL\Data
l
Example
\Program Files\Microsoft SQL
Server\MSSQL10.SQLSERVERVIEW\MSSQL\Data
The Name for the unnamed Default Instance is MSSQLSERVER.
For instances of SQL Server 2008 R2:
\Program Files\Microsoft SQL Server\MSSQL10_
50.Instancename\MSSQL\Data
Example
\Program Files\Microsoft SQL Server\MSSQL10_
50.SQLSERVERVIEW\MSSQL\Data
The Name for the unnamed Default Instance is MSSQLSERVER.
Installation under Windows 203
4 ServerView database l
For instances of SQL Server 2012:
\Program Files\Microsoft SQL
Server\MSSQL11.Instancename\MSSQL\Data
l
Example
\Program Files\Microsoft SQL
Server\MSSQL11.SQLSERVERVIEW\MSSQL\Data
The Name for the unnamed Default Instance is MSSQLSERVER.
For instances of SQL Server 2014:
\Program Files\Microsoft SQL
Server\MSSQL12.Instancename\MSSQL\Data
Example
\Program Files\Microsoft SQL
Server\MSSQL12.SQLSERVERVIEW\MSSQL\Data
The Name for the unnamed Default Instance is MSSQLSERVER.
If the ServerViewDB_log.LDF file is bigger than the ServerViewDB.mdf file, you should shrink it.
2. Shrink the file ServerViewDB_log.LDF:
1. Stop the services ServerView Services and ServerView Download
Service.
2. If applicable, close the database management program.
3. Call the dbcc_shrink.sql script.
As of Operations Manager version 4.71, the dbcc_shrink.sql script is provided for shrinking. The script is located in the <DllPath>\Tools directory.
This directory also contains the document Shrink_ServerViewDB_
log.LDF.doc with a detailed and, where appropriate, updated description of this problem.
To execute the script, enter the following commands at the input prompt: type %windir%\ServerViewDB.ini | findstr Server_ instance
204 Installation under Windows
4.9 Error diagnostic type %windir%\ServerViewDB.ini | findstr -i DllPath= cd /d <DllPath>\Tools sqlcmd -S <Server_instance> -E -i dbcc_shrink.sql -n
4. Check the size of the file again (see 1) to make sure that the
ServerViewDB_log.LDF file is smaller than the ServerViewDB.mdf file.
5. Start the SQL Server agent SQLSERVERAGENT (not for SQL Server
Express editions).
6. Set the start type to Automatic (not for SQL Server Express editions).
7. Start the services ServerView Services and ServerView Download
Service.
8. Now start the backup job JobServerViewLongInterval.
The backup job JobServerViewLongInterval now backs up the database and the transaction log and reduces the backup files
ServerViewDBData.bak and ServerViewDBLog.bak.
For SQL Server Express editions, the backup jobs are run via the Windows
Task Scheduler, for all other SQL Server editions via the corresponding SQL
Server agent.
3. Recommendation
In advanced backup mode, check that the ServerView backup jobs are being executed correctly. For more information see
ServerView database" on page 175 .
By regularly running the backup job JobServerViewHourly, you prevent the
ServerViewDB_log.LDF file from becoming too big. This job deletes parts of the file that are no longer needed on an hourly basis.
4. Additional troubleshooting
Error messages for backup jobs are written in log files called ERRORLOG.*.
These files are located in the LOG directory: l
Default for SQL Server 2005: %ProgramFiles%\Microsoft SQL
Server\MSSQL.n\MSSQL\LOG\
l
Default for SQL Server 2008 and higher: %ProgramFiles%\Microsoft
SQL Server\MSSQL<version>.<Instancename>\MSSQL\LOG\
Installation under Windows 205
4 ServerView database
You may verify the location of the LOG directory either via SQL Server
Management Studio or SQL Server Configuration Manager.
With SQL Server Configuration Manager:
1. Open the tool:
Select All Programs – Microsoft SQL Server <version> –
Configuration Tools – SQL Server Configuration Manager.
2. Select the instance
Click on SQL Server <version> Services, for instance SQL Server 2005
Services. In the details pane, then right-click the instance name queried for, for example: SQL Server (SQLSERVERVIEW)
3. From the drop down list for the service, select Properties. Then select the Advanced tab.
You will find the path to the log files under Dump Directory.
If the following message appears in the log files, you must take appropriate measures:
"The backup data in 'ServerViewDBLog' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable."
For new backups to be created, the existing backup devices must be reformatted. The reformatting can be necessary for the following reasons:
1. A backup was interrupted.
2. A disk error occurred.
3. There is not enough disk space available.
4. Backup path could not be found.
5. A write error occurred during creation of the backup.
Reformatting the backup:
1. Find out the cause and remedy it.
Check all possible cases (see above). For 1. and 2.: Check the application and system log in the event display for further information.
2. Find out the backup path <DBBackupPath> for the ServerView backup files by entering the following commands at the input prompt: type %windir%\ServerViewDB.ini | findstr DBBackupPath
206 Installation under Windows
4.9 Error diagnostic type %windir%\ServerViewDB.ini | findstr Server_
Instance sqlcmd -S <Server_Instance> -E
3. Format the backup file:
BACKUP DATABASE ServerViewDB TO DISK =
'<DBBackupPath>ServerViewDBData.bak' WITH FORMAT,
MEDIANAME='ServerViewDB'
GO
BACKUP LOG ServerViewDB TO DISK
='<DBBackupPath>ServerViewDBLog.bak' WITH FORMAT,
MEDIANAME='ServerViewDB'
GO quit
4. Then check that the ServerView backup jobs are being correctly executed, see
"Backing up the ServerView database" on page 175 .
4.9.4
Exporting the ServerView database
For error diagnostics, it might also be necessary to send a copy of the ServerView database and the transaction logs to the Service Center.
In this rare event, you are advised to switch the database offline by stopping the services MSSQL$SQLSERVERVIEW or MSSQLSERVER (for SQL Server
2014/2012/2008/2005: SQL Server (SQLSERVERVIEW) or SQL Server
(MSSQLSERVER)). As long as these services are stopped, no one can access the database.
Therefore, the procedure described in this section is not suitable for repeated, everyday use. However, for error analysis, importing the ServerView database file and the transaction log file (files with suffix .mdf and .ldf) is easier to manage than restoring from the database backups (file with suffix .bak).
This requires the following steps:
1. Find out the important information relating to the error, see
"Important information in the event of an error" on page 201 .
2. Find out the directory of the ServerView database and the transaction logs.
With SQL Server Management Studio:
Installation under Windows 207
4 ServerView database
1. Start the SQL Server Management Studio.
2. Select the SQL Server instance.
3. Select Databases – ServerViewDB and then select Properties from the context menu.
4. Click the Data files tab.
The Location column contains the path name of the file
ServerViewDB.mdf. The Path column contains the path name.
With sqlcmd:
1. Start sqlcmd and enter the following command: use ServerViewDB exec sp_helpfile
GO
The filename column shows the path names.
3. Stop the service SQL Server <DbService>. The service name can be found in the configuration file ServerViewDB.ini (in the <windir> directory) under DbService.
4. Send the files ServerViewDB.mdf and ServerViewDB_log.LDF to the
Service Center together with the transaction logs.
5. Start the service SQL Server <DbService>.
208 Installation under Windows
5.1 Installing Operations Manager software via the command line
5 Command Line Interface
5.1
Installing Operations Manager software via the command line
You can also install Operations Manager, Update Manager and the Event
Manager via the Windows command line. To do this, insert the ServerView Suite
DVD 2, start the installation of Operations Manager and specify that you only want to unpack the Operations Manager installation package. You can specify a directory in which the files are to be placed.
Keep these setup files or the DVD. Sometimes when executing a
Modify installation, you are prompted for the original media. In this case reuse these setup files or the DVD.
Silent installation
Silent installation on a remote SQL Server is not supported.
You can install JBoss 7 and Operations Manager software in a silent installation, i.e. without an installation dialog. This is done using the configuration file
silent_install.ini, which contains default values for individual options, including: l
Installation path l l l
Port number
Host name
IP address l
Use of built-in account for ServerView JBoss service (entry LocalService)
You can edit this file and adjust it to your requirements.
Installation under Windows 209
5 Command Line Interface
During the installation, the program checks whether SQL Server Express with the instance name SQLSERVERVIEW or SQL Server Standard/Enterprise/Workgroup
Edition (if available) in a version supported by Operations Manager with any instance name are already installed on your system.
If no suitable instance is found, Server 2008 R2 Express or SQL Server 2005
Express with instance name SQLSERVERVIEW is installed.
If you want to get SQL Server 2008 R2 Express installed on Windows Server 2008, use option /SS2008.You have then to provide the appropriate .NET Framework version by your own.
To perform a silent installation, switch to the command line and start the installation with the following call: start /wait serverview.exe /s
After the installation you can check in the Windows event display in the
Application Event Log whether the installation was successful. You can view the installation log in the %TEMP%\MSIsvinst.log file. The message
"Installation success or error status: 0" indicates successful installation.
Language
You can specify your preferred installation and application language via the command line option /l ja or /l en.
This allows a different language than that of the standard installation. The following two variants are helpful.
l
Start the installation on an English operating system: start /wait serverview.exe /l ja l
The installation and application language of Operations Manager appear in
Japanese.
Start the installation on an Japanese operating system: start /wait serverview.exe /l en
The installation and application language of Operations Manager appear in
English.
210 Installation under Windows
5.2 Database management via sqlcmd
5.2
Database management via sqlcmd
SQL Server 2005 and higher can be managed not only with SQL Server
Management Studio but also via sqlcmd. When SQL Server 2005 or higher is installed, sqlcmd is installed as well. You can use sqlcmd to execute the following functions, among others: l
Check the product version and language l
Restore the ServerView database
5.2.1
Checking the product version and language of SQL Server
You can check the product version and language of SQL Server as follows:
1. Switch to the input prompt.
2. Start sqlcmd with the following command: sqlcmd -S <SQL Server instance> -E xp_msver
GO
The information you need is the entries for 2 ProductVersion and 3 Language.
You terminate sqlcmd with the quit command.
5.2.2
Restoring the ServerView database
Before you restore the ServerView database, you must first restrict the access to the database. You can then restore the database and the transaction logs.
1. Switch to the input prompt.
2. Start sqlcmd with the following command: sqlcmd -S <SQL Server instance> -E
Restricting access to the database
You restrict access to the database with the following command: exec sp_dboption 'ServerViewDB', 'dbo use', 'true'
GO
Installation under Windows 211
5 Command Line Interface
Restoring a database backup
You restore a chosen database backup with the following command - with the option NORECOVERY:
RESTORE DATABASE [ServerViewDB] FROM DISK =
'<Path>\ServerViewDBData.bak' WITH FILE = <Position>,
NORECOVERY,
MOVE 'ServerViewDB' TO '<Drive>:\Program Files\Microsoft SQL
Server\MSSQL$SQLSERVERVIEW\Data\ServerViewDB.mdf'
GO
Restoring transaction logs
The following command - with the option NORECOVERY - restores all transaction logs apart from the current one. The command must be entered separately for each transaction log.
RESTORE LOG [ServerViewDB] FROM DISK
='<Path>\ServerViewDBLog.bak' WITH FILE = <Position>,
NORECOVERY,
MOVE 'ServerViewDB_log' TO '<Drive>:\Program Files\Microsoft
SQL Server\MSSQL$SQLSERVERVIEW\Data\ServerViewDB_log.LDF'
GO
Restoring the most recent (last) transaction log
The following command restores the most recent (last) transaction log:
RESTORE LOG [ServerViewDB] FROM DISK =
'<Path>\ServerViewDBLog.bak' WITH FILE = <Position>,
RECOVERY,
MOVE 'ServerViewDB_log' TO '<Drive>:\Program Files\Microsoft
SQL Server\MSSQL$SQLSERVERVIEW\Data\ServerViewDB_log.LDF'
GO
212 Installation under Windows
5.3 Backing up/Restoring the ServerView database via command line tool
5.3
Backing up/Restoring the ServerView database via command line tool
5.3.1
Backing up the ServerView database
With the command line tool SVBackupServerViewDB.bat you can backup the
ServerViewDB database.See section
"Restoration via SQL Server Management
for requirements of matching versions.
When the tool is executed without parameters you can step interactively through the tool.
1. Open a command prompt window.
2. Find out <Dllpath> and switch to the directory: type %windir%\ServerViewDB.ini | findstr -i DllPath= cd /d <DllPath>\Tools
3. Execute the tool SVBackupServerViewDB.bat:
SVBackupServerViewDB.bat [<cmd> [<path>]]
<cmd>
Specify 1 or 2.
1: Create backups in the user-defined <path>.
2: Create backups in the default backup folder <DBBackupPath>. Find out <DBBackupPath> by entering in the command prompt window: type %windir%\ServerViewDB.ini | findstr -i
DBBackupPath=
<path>
Specify the folder where the backups will be stored.
This parameter is available only when 1 is specified for <cmd>.
Example
SVBackupServerViewDB.bat 1 C:\SV_BKUPC
Backups will be created in file C:\SV_BKUP\ServerViewDBData.bak.
Installation under Windows 213
5 Command Line Interface
4. For error checking, a log file named SVBackupServerViewDB.log is generated within the folder the tool was called from. When called with command line parameters, any output goes to the log file.
5. If a remote SQL Server is used and nothing was specified for dialog field SQL
Server Backup Path during the installation (the configuration file
ServerViewDB.ini contains at DbBackupPath the entry default): In this case set up a backup device as described in
"Checking the existence of backup files" on page 181 .
5.3.2
Restoring the ServerView database
With the command line tool SVRestoreServerViewDB.bat you can restore the
ServerView database from a backup taken with the same ServerView version.
1. Stop the ServerView services ServerView Services and ServerView
Download Service.
2. Open a command prompt window.
3. Find out <Dllpath> and switch to the directory: type %windir%\ServerViewDB.ini | findstr -i DllPath= cd /d <DllPath>\Tools
4. Execute the batch file SVRestoreServerViewDB.bat:
SVRestoreServerViewDB.bat
The tool will ask interactively for the path where the backup file
ServerViewDBData.bak is located.
214 Installation under Windows
5.3 Backing up/Restoring the ServerView database via command line tool
Example
5. For error checking, a log file named SVRestoreServerViewDB.log is generated within the folder the tool was called from. When called with command line parameters, any output goes to the log file.
6. Complete with following post processing steps: Create a new full backup to the Operations Manager backup device.
SVBackupServerViewDB.bat 2
7. Restart ServerView Services and ServerView Download Service.
In
"Restoring the ServerView database" on page 185
you will find a detailed description of the commands used in the tool SVRestoreServerViewDB.bat and additionally a description how to restore from a transaction log.
Installation under Windows 215
216 Installation under Windows
6 Fujitsu Technology Solutions Software
License Agreement for End User
1. Subject of this Agreement
1.1 For the purposes of this agreement “Software” shall mean the software with the object code, the version and the specification indicated in the software product data sheet of Fujitsu Technology Solutions.
The Software consists of machine-readable instructions and/or printed documentation and related licensed materials.
1.2 Please read this agreement carefully before you use the Software. If you do not agree with the license terms in this agreement, you are not permitted to use the Software and must immediately return all copies of the Software and all accompanying items to the Licensor/Sublicensor (either Fujitsu Technology
Solutions or the reseller who supplied you with 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. By using 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 future an additional software license key and/or license certificates as countermeasures against software piracy.
1.5 Software components from third-party software suppliers which are part of the scope of the delivery are subject to separate license agreements that are included with the Software or that are transmitted by Fujitsu Technology
Solutions upon request.
2. End User License
2.1 Fujitsu Technology Solutions grants you a non-exclusive and nontransferable license to 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 on more than the maximum number of licensed workstations or on hardware that exceeds the specified type.
You are permitted to make a backup copy of the Software for archiving purposes, provided you properly mark the copy or partial copy of the Software with the copyright notice and any other ownership information.
Installation under Windows 217
6 Fujitsu Technology Solutions Software License Agreement for End User
2.2 You are not permitted to copy, modify or distribute the Software.
Furthermore, you are not 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 or transfer the Software except as expressly permitted by this agreement or due to mandatory legal regulations.
2.3 If you acquired the Software as a program upgrade, your license for the use of the old software version ends automatically with the installation of the upgrade version of the Software. If parts of the old software version are not replaced by the upgrade version, the license for the old version continues to be effective until the remnants of the old software version 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
Technology Solutions, the license for a software version or release does not give you any rights to new releases (updates), new versions (upgrades) or technical support services for the Software. Supplemental software support contracts and maintenance services, including or excluding new releases and new versions and additional technical support services, can be purchased separately either from
Fujitsu Technology Solutions directly or from authorized software resellers.
3. Downloading
For Software supplied by Fujitsu Technology Solutions over a network or a similar distribution path, the following additional conditions shall apply:
All products supplied for downloading by Fujitsu Technology Solutions are selected, made available and — if supplied by third parties — provided without modification. However, you are fully responsible for ensuring the most current version and usability of downloadable material for your own purposes and on your own system. You download Software at your own risk. Fujitsu Technology
Solutions will not accept any liability, particularly not for transmission 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 those countries in which Fujitsu Technology Solutions has one or more offices.
Fujitsu Technology Solutions accepts no responsibility that Software and/or documentation can or may be downloaded from a Fujitsu Technology Solutions website also in locations other than the countries mentioned above. If you access a website of Fujitsu Technology Solutions from abroad, you are fully responsible for complying with any local regulations. Fujitsu Technology
218 Installation under Windows
Solutions expressly prohibits the downloading of Software and/or documentation from a Fujitsu Technology Solutions website in countries where such downloading is considered illegal.
4. Copyright
All rights and licenses, unless they are expressly granted to you in this license terms, as well as all property and usage rights related to the Software (including parts of the Software) 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
Fujitsu Technology Solutions or its third-party licensors, nor are you permitted to use any other brands which are deceptively similar to the brands, logos or trademarks of Fujitsu Technology Solutions. Each and any use of brands, logos or trademarks with respect to the Software or Fujitsu Technology Solutions requires the express consent of Fujitsu Technology Solutions.
5. Licensor’s warranty and liability disclaimer, if Software is sold and delivered by Reseller
If you acquire the Software directly from an authorized reseller (called
“Reseller”), the right to install and use the Software may be subject to additional software license conditions agreed upon between you as the licensee and the respective reseller.
In all cases of an authorized software resale, the software is sublicensed and made available to the licensee directly by the Reseller. In such cases, Fujitsu
Technology Solutions is not a contractual party of the software license agreement between you, as licensee 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 on the basis of the agreements with the Reseller. Under no circumstances, however, will the respective scope of the license for the licensee exceed the scope of the license agreements as specified in sections 1, 2, 3 and 4 of this agreement.
Subject to mandatory legal regulations, particularly those governing liability and/or warranties, which cannot be excluded in connection with end user license agreement regulations and with reference to the licensee’s claims against the
Reseller, Fujitsu Technology Solutions disclaims all warranties for the Software in this agreement.
For the same reason, Fujitsu Technology Solutions disclaims any and all liability/claims for any violations of third parties’ rights as well as any implied
Installation under Windows 219
6 Fujitsu Technology Solutions Software License Agreement for End User warranties for the software’s marketability and its suitability for a particular purpose. This disclaimer of liability does not apply in cases of willful or malicious behavior by Fujitsu Technology Solutions.
In this End User License Agreement, Fujitsu Technology Solutions grants no warranties of any kind, either express or implied.
6. Disclaimer of liability with respect to shareware, freeware and/or open source software components
6.1 The Software may contain freeware or shareware which Fujitsu Technology
Solutions received from a third party. Fujitsu Technology Solutions paid no license fees for the use of this freeware or shareware. Accordingly, the licensee is not charged any license fees for the use of the freeware or shareware. You recognize and accept that Fujitsu Technology Solutions therefore grants no warranties with respect to such freeware or shareware components and does not assume any liability in connection with the ownership, the distribution and/or the use of the respective freeware or shareware.
6.2 The Software may also contain open source software components that were developed according to the “open source model” and which are distributed exclusively on the basis of the GPL (General Public License: http://www.gnu.org/copyleft/gpl.html) terms and conditions or other standard open source standard license terms and conditions applicable 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 is governed exclusively by the above-mentioned GPL terms or by the conditions which are otherwise included with the open source software components. Fujitsu
Technology Solutions receives neither license fees nor any other compensation for the delivered open source software components. As far as Fujitsu Technology
Solutions or a third party receives any compensation in connection with open source software components, it is received exclusively for additional delivery items and/or services.
Because of the special nature of the development and distribution of open source software components, Fujitsu Technology Solutions assumes no express or implied liability for such components and excludes any kind of warranty for such open source software components, particularly in connection with missing specifications, lack of functionality, programming errors or any other malfunctions.
220 Installation under Windows
7. General limitations of liability
7.1 Neither Fujitsu Technology Solutions nor its suppliers are liable for any consequential or indirect damages, including damages arising as a result of or in connection with an operational interruption, lost profits or sales, lost data, or costs of capital. Fujitsu Technology Solutions and its suppliers will not be liable for additional ancillary or consequential costs or for any other losses, costs or expenses of any kind which arise as a result of the holding, sale, use or impossibility of use of the Software, independent of whether such claims are asserted due to warranty rights, contracts, tort or any other legal theory.
7.2 The liability of Fujitsu Technology Solutions for direct damage caused as a result of a contract violation and/or other action or lapse on the part of Fujitsu
Technology Solutions which have not been excluded or cannot be completely excluded due to mandatory law are limited to no more than €250,000.00. Any and all other liabilities for direct damage are excluded. Damage caused by
Fujitsu Technology Solutions as a result of slight negligence are excluded to the extent permitted by applicable legal regulations.
7.3 Limitations and exclusions of liability resulting from this agreement do not apply to damage where Fujitsu Technology Solutions carries compulsory liability according to applicable laws and where such liability cannot be limited to a maximum amount (for example, liability for bodily damage; product liability or fraudulently incorrect information).
Installation under Windows 221
6 Fujitsu Technology Solutions Software License Agreement for End User
8. Export controls
Due to its components as well as the nature or purpose of these components, the export of the Software and/or its accompanying documents may be subject to official or regulatory approval. In cases where the Software is intended for export, you are obliged to get all approvals 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 be used 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 such companies or persons who are listed in the applicable U.S. export regulations (particularly the 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 German export 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 other contractual commitments if this would be a violation of the applicable export regulations of the Federal Republic of Germany, the European
Union, the United States of America or of any other countries.
If you export or re-export the Software or a copy of it, this may be a violation of applicable export laws and a severe violation of the terms of this agreement.
9. Miscellaneous
9.1 If any term or condition in this agreement or any other contract that is subject to the terms and conditions of this agreement turns out to be invalid or unenforceable (partly or in full), the validity of all other terms and conditions remains unaffected, unless complying with the remaining terms and conditions would represent an unreasonable hardship for either contract party, even with the application of applicable legal regulations to close the legal gap.
9.2 If you/ the licensee do not pay the license fees due and/or if the licensee does not comply with essential terms and conditions of this license agreement,
Fujitsu Technology Solutions reserves the right to cancel the license. In case of such cancellation, you must immediately return any and all copies of the software in your possession and confirm the complete return [of the software copies] or the destruction of these copies in writing.
222 Installation under Windows
9.3 Neither you nor Fujitsu Technology Solutions is responsible or liable for the respective party’s non-compliance with its obligations if the reason for such noncompliance is outside the party’s control due to force majeure.
9.4 Any and all modifications and/or amendments to these license terms and conditions are only valid if they are made in writing.
10. Applicable law
10.1 These license terms and conditions are governed by the laws of the Federal
Republic of Germany.
10.2 In the event that provisions of clause 10.1 are unenforceable, these license terms and conditions 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 are governed by the laws of the state or sovereign territory in which the business contract is being concluded; 2) in Albania,
Armenia, Belarus, Bosnia-Herzegovina, Bulgaria, Croatia, the Czech Republic,
Georgia, Hungary, Kazakhstan, Kirgizia, the former Yugoslavian Republic of
Macedonia (FYROM), Moldavia, Poland, Romania, Russia, Slovakia, Slovenia, the Ukraine and the Federal Republic of Yugoslavia, the terms and conditions of this license are governed by the laws of the Federal Republic of Germany; 3) in the United Kingdom [Great Britain], all disputes with respect to these license terms and conditions are 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 of Ontario; 5) in the United States of
America and in Puerto Rico as well as in the People’s Republic of China the terms and conditions of this license are governed by the laws of the U.S. State of New
York.
Installation under Windows 223
224 Installation under Windows
دانلود
پیوند عمومی به روز شد
پیوند عمومی به چت شما به روز شده است. You may view and manage your chat links after registration here.
پیوند عمومی سند
تبلیغات
