Control Center Guide

PUBLIC
SAP HANA Platform SPS 10 DSP

Document Version: 1.1 2015-08-21
SAP DB Control Center 4 Guide
Content
About SAP DB Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installation and Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1
Before Installing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2
Upgrading SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3
Downloading the SAP DCC Delivery Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
2.4
Adding the SAP DB Control Center System to SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5
Installing the SAP DCC Delivery Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6
Uninstalling SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.7
Tutorial: Migrating SAP DB Control Center to a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . .13

1. Install an SAP HANA System in Single-Container Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2. Install and Configure SAP DCC on Single-Container System. . . . . . . . . . . . . . . . . . . . . . . . . . 17
3. Convert and Configure System for Multitenancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuration: SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
3.1
Setting up SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.2
Setting up the System Configuration Login Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3
Setting up Administrator Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4
Setting up the Collector Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5
Setting up User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.6
Updating Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
3.7
Configuring SAP HANA XS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.8
Configuring with SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.9
Optional Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Configuring Connection Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Enabling a Proxy Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring Storage of Historical Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Configuration: Monitored Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
4.1
Setting up the Technical User Account on Monitored Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Accessing SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.1
Browser Compatibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1
Adding Launchpad Tiles and Tile Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
6.2
Moving and Removing Launchpad Tiles and Tile Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
PUBLIC
2015 SAP SE or an SAP affiliate company. All rights reserved.

Content
System Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.1
Add and Remove Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Adding a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Creating an Import File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Importing Systems in Bulk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Removing a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.2
Add, Remove, and Modify System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Creating System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Removing System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Modifying System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Alert Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Enterprise Health Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
9.1
Connecting to a Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10
Starting and Stopping a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Content
PUBLIC
About SAP DB Control Center
SAP DB Control Center (SAP DCC) lets you perform aggregate monitoring of SAP database products,
including SAP HANA, and manage the cockpits (management consoles) that manage the database products.
Use control center to check the overall health of systems located within a data center or across your
enterprise. You can drill down into status indicators for more detailed information, monitor the databases
running on monitored systems, and access cockpits on those systems.
Status displays focus on four high-level areas:
Availability - is the system running and accessible on the network? Is it able to serve the business needs of
its users, including humans and applications? Performance and capacity issues can affect availability.
Performance - is the system meeting the response time expectations of database users, including humans
and applications?
Capacity - is the system meeting its service level agreements?
Alerts - are there errors to resolve or event messages that need review? Alert events, given priorities of
high, medium, or low, are triggered when the system exceeds state and range thresholds set by system
and database administrators.
PUBLIC

About SAP DB Control Center
Installation and Upgrade
Load SAP DB Control Center, a component of SAP HANA, into your system.
You can install SAP DCC on any SAP HANA system running SPS09 or later. However, in an SAP HANA
multitenant database containers environment, you must install SAP DCC within a tenant database. Operation
within a system database is not supported. (You can use SAP DCC to monitor a system database.)
One SAP DCC system can monitor multiple SAP HANA systems.
1. Before Installing [page 5]

Understand the installation process, decide how to install SAP DB Control Center, and read the
relevant SAP HANA documentation.
2. Upgrading SAP DCC [page 7]
Follow these steps to upgrade SAP DB Control Center to SPS 10.
3. Downloading the SAP DCC Delivery Unit [page 8]
Get the SAP DB Control Center delivery unit from the SAP Software Download Center.
4. Adding the SAP DB Control Center System to SAP HANA Studio [page 9]
Make SAP HANA studio aware of the SAP HANA system on which you plan to run SAP DB Control
Center. This enables you to install and configure the SAP DCC delivery unit.
5. Installing the SAP DCC Delivery Unit [page 10]
Load the delivery unit for SAP DB Control Center. This task applies to both new installations and
upgrades.
6. Uninstalling SAP DCC [page 12]
Remove the SAP DB Control Center delivery unit (DU) from an SAP HANA system.
7. Tutorial: Migrating SAP DB Control Center to a Tenant Database [page 13]
SAP DB Control Center (SAP DCC) is an application that runs on SAP HANA. In this tutorial, you'll
migrate an SAP DCC installation so that it goes from running on a single-container SAP HANA system
to running in the tenant database of the same system converted to support multitenancy.
2.1
Before Installing
Understand the installation process, decide how to install SAP DB Control Center, and read the relevant SAP
HANA documentation.
For information on upgrading from a previous release, see Upgrading SAP DCC [page 7].
Before you can use SAP DCC, you must:
Table 1:
Install SAP HANA,
SAP HANA studio

SAP HANA Master Guide, installation

planning and overview
PDF
HTML
PUBLIC
SAP HANA Server Installation and Update PDF

Guide
HTML
SAP HANA Studio Installation and Update PDF
Guide
HTML
SAP HANA Developer Guide, general in
formation on delivery units (DUs)
PDF
Download the HANA

DBCC delivery unit
Covered in this document
Downloading the SAP DCC Delivery Unit [page 8]
Install the HANA

DBCC DU into SAP
HANA
There are three ways to install the DU:
HTML
Complete Adding the SAP DB Control Center System

to SAP HANA Studio [page 9] and Installing the
SAP DCC Delivery Unit [page 10].
Use SAP HANA studio. This method

is covered in this document.
Use the SAP HANA command-line

PDF
lifecycle management tool, hdbalm.
HTML
This method is covered in the SAP
HANA Administration Guide.
In the SAP HANA Administration Guide, see Installing

and Updating Add-On Products and Software Compo
nents.
Use the SAP HANA Application Life PDF

cycle Management graphical user in
HTML
terface. This method is covered in
the SAP HANA Developer Guide.
In the SAP HANA Developer Guide, see Import a Deliv
ery Unit.
Configure SAP DCC
Covered in this document
Start with Adding the SAP DB Control Center System

to SAP HANA Studio [page 9] and complete all
the tasks up to Accessing SAP DCC [page 50].
Note
If you chose to install the HANA DBCC DU using
one of the SAP HANA lifecycle management tools,
skip Installing the SAP DCC Delivery Unit [page
10].
Parent topic: Installation and Upgrade [page 5]

Next task: Upgrading SAP DCC [page 7]
PUBLIC

2.2
Upgrading SAP DCC
Follow these steps to upgrade SAP DB Control Center to SPS 10.
Prerequisites
Review Before Installing [page 5].
Procedure
1. (Optional) Upgrade the SAP HANA system where SAP DCC is installed to SPS 10.
2. Before you upgrade SAP DCC, back up the host SAP HANA system.
For instructions, see SAP HANA Database Backup and Recovery in the SAP HANA Administration Guide.
3. Download but do not install the SAP DCC SPS 10 PL01 delivery unit from the SAP Software Download
Center.
For instructions, see Downloading the SAP DCC Delivery Unit [page 8].
4. Log in to the SAP HANA application lifecycle management tool (HALM) using an SAP HANA account with
the role sap.hana.xs.lm.roles::Administrator.
Access HALM at http://<hana.host.name>:<port>/sap/hana/xs/lm/,
where the value of <port> is 80 followed by the 2-digit SAP HANA instance number:
80<instance_number>
For example, use port 8001 for an HTTP connection to instance 01.
5. Select
PRODUCTS
Delivery Units
HANA_DBCC .
6. In the Assigned Packages section, scroll to and select the sap.hana.dbcc.services.dest package.
7. Click Unassign and confirm the unassignment of the package from the delivery unit.
8. Import the SAP DCC SPS 10 DU.
For instructions, see Installing the SAP DCC Delivery Unit [page 10].
Caution
Do not import the delivery unit unless you have performed the previous steps in this procedure.
9. If you enabled a proxy server for SAP DCC, enable it again.
For instructions, see Enabling a Proxy Server [page 41]. Re-enabling is necessary because the location
of the default.xshttpdest file has changed to the sap.hana.dbcc.services.dtdest package.
10. Read these sections and complete the steps that are appropriate for your environment.

PUBLIC
Table 2: Configuration Checklist

Optional: Configuring Single Sign-On [page 36]
Optional: Configuring Connection Security [page 40]
Optional: Enabling a Proxy Server [page 41]
Optional: Configuring Storage of Historical Data [page 42]
11. (Optional) Convert the SAP HANA system to support multitenant database containers. Note that SAP
DCC can operate only in a tenant database container. Operation in a system database container is not
supported.
For conversion instructions, see Tutorial: Migrating SAP DB Control Center to a Tenant Database [page
13].
Task overview: Installation and Upgrade [page 5]

Previous: Before Installing [page 5]
Next task: Downloading the SAP DCC Delivery Unit [page 8]
Related Information
SAP HANA Administration Guide
2.3
Downloading the SAP DCC Delivery Unit
Get the SAP DB Control Center delivery unit from the SAP Software Download Center.
Procedure
1. Point your Web browser to the Software Download Center at https://support.sap.com/swdc
2. Select
Support Packages and Patches
3. Click H and select

4. Select
A-Z .
SAP HANA Platform Edition
Entry by Component
DB Control Center
SAP HANA PLATFORM EDIT. 1.0

SAP DB Control Center 4
(near top of screen).
# OS Independent
SAP
HANA database .
5. Click to check the box for the DBCC package (for example, HANADBCC00). Select the option with the
most recent SP and patch level.
PUBLIC

6. Click Add to Download Basket, then (in the new window that appears) click Download Basket.
7. To start the zip file download, click the file description in the download window (for example, SP99
PatchA for SAP DB Control Center 4).
8. Save the zip file (HANADBCC00_0-70000079.zip, for example) to a convenient location and extract it.
9. Copy the HANADBCC.tgz file you extracted from the zip to a location accessible from your chosen
installation tool: SAP HANA studio or SAP HANA application lifecycle management.
Next Steps
If you plan to use SAP HANA studio to install SAP DCC, continue following the steps in this document.
If you plan to install with SAP HANA application lifecycle management, see Before Installing [page 5].
Note
After installing with SAP HANA application lifecycle management, return here to configure SAP DCC.

Previous task: Upgrading SAP DCC [page 7]
Next task: Adding the SAP DB Control Center System to SAP HANA Studio [page 9]
2.4
Adding the SAP DB Control Center System to SAP

HANA Studio
Make SAP HANA studio aware of the SAP HANA system on which you plan to run SAP DB Control Center. This
enables you to install and configure the SAP DCC delivery unit.
Prerequisites
Install the SAP HANA platform. For details, see:
SAP HANA Server Installation and Update Guide: PDF HTML
Install SAP HANA studio. For details, see:
SAP HANA Studio Installation and Update Guide: PDF HTML

PUBLIC
Procedure
1. In SAP HANA studio, go to the Administration Console.
2. Right-click in the Systems view and select Add System.
3. Enter the host name and instance number for the system you are adding. You may also enter a description
if you wish.
4. If you are adding a system running SAP HANA multitenant database containers:
a. Select Multiple containers.
b. Select the type of database container you are adding:
Tenant database container (enter the tenant's name if you choose this option).
System database container.
5. Click Next.
6. Enter credentials for the SYSTEM account and click Next.
7. Click Finish.

Previous task: Downloading the SAP DCC Delivery Unit [page 8]
Next task: Installing the SAP DCC Delivery Unit [page 10]
2.5
Installing the SAP DCC Delivery Unit
Load the delivery unit for SAP DB Control Center. This task applies to both new installations and upgrades.
Prerequisites
Download the SAP DCC delivery unit. [page 8]
In SAP HANA studio, add the system on which SAP DCC will run. [page 9]
If you are upgrading SAP DCC, have the user ID and password available for the collector account
(DCC_COLLECTOR, for example). If you have to reactivate any jobs during the job activation check, the
system prompts you for these credentials.
Context
In an SAP HANA multitenant database containers environment, install the SAP DCC DU on a system with a
tenant database container. Operation with a system database container is not supported.
10
PUBLIC

Procedure
1. In SAP HANA studio, log in as SYSTEM or a user with the same roles.
2. Select
File
Import
SAP HANA Content
Delivery Unit
and click Next.
3. Select the system to which you are importing the delivery unit and click Next.
4. Click the Client radio button.
5. Click Browse and navigate to the HANADBCC.tgz file you saved earlier.
6. Under Actions, select Overwrite inactive version and Activate objects. (They might be selected already.)
7. Click Finish.
In the Job Log view, notice that the import status changes to Running and then to Completed succesfully.
8. If you are upgrading SAP DCC, check and if necessary reactivate your collection and maintenance jobs:
a. Point your browser to:
https://<hana.host.name>:<port>/sap/hana/xs/admin
43<instance_number>
For example, use port 4301 for an HTTPS connection to instance 01.
b. In the left pane, click the arrows to expand
ScheduleCollections.xsjob.
sap
hana
dbcc
collections
and select
c. Click the Configuration tab.

d. Look at the Active checkbox. If it does not contain a check mark, click to check it.
e. If you clicked the checkbox, select Save Job (bottom right).
f. In the left pane, click dbcc and click the arrow to expand jobs.
g. Select JobWorkerTask.xsjob.
h. On the Configuration tab, look at the Active checkbox. If it does not contain a check mark, click to
check it.
i.
If you clicked the checkbox, select Save Job (bottom right).
j.
In the left pane, click dbcc and click the arrow to expand maintenance.
k. Select Maintenance.xsjob.
l.
On the Configuration tab, look at the Active checkbox. If it does not contain a check mark, click to
check it.
m. If you clicked the checkbox, select Save Job (bottom right).
Next Steps
If you are installing SAP DCC for the first time, complete the configuration tasks, starting with Setting up
SAP DCC [page 26].
If you are upgrading SAP DCC, complete the tasks listed in Upgrading SAP DCC [page 7].
Previous task: Adding the SAP DB Control Center System to SAP HANA Studio [page 9]

PUBLIC
11
Next task: Uninstalling SAP DCC [page 12]
2.6
Uninstalling SAP DCC
Remove the SAP DB Control Center delivery unit (DU) from an SAP HANA system.
Context
For details on SAP HANA Lifecycle Management, see the SAP HANA Administration Guide.
Procedure
1. Point your browser to:
43<instance_number>
2. Log in as SYSTEM (or any user with the lifecycle management Administrator role,
sap.hana.xs.lm.roles::Administrator).
3. Click the Delivery Units tile.
4. In the Delivery Units list in the left pane, select HANA_DBCC (sap.com).
5. Click the Delete button (top of left pane).
6. In the confirmation dialog, click the checkbox to select including objects and packages, then click Yes to
confirm and start the deletion process.
7. (Optional) Uninstalling the delivery unit does not remove every trace of SAP DCC. To clean up the SAP
DCC schema and users, execute these SQL commands. If you configured nondefault user names, enter
them in place of the names shown here.
drop
drop
drop
drop
drop
user SAPDBCC;
user DCC_ADM;
user DCC_USR;
user DCC_COLLECTOR;
schema SAP_HANA_DBCC cascade ;
Note
Perform this step only if you need to start over with a clean environment.
12
PUBLIC


Previous task: Installing the SAP DCC Delivery Unit [page 10]
Next task: Tutorial: Migrating SAP DB Control Center to a Tenant Database [page 13]
2.7
Tutorial: Migrating SAP DB Control Center to a Tenant

Database
SAP DB Control Center (SAP DCC) is an application that runs on SAP HANA. In this tutorial, you'll migrate an
SAP DCC installation so that it goes from running on a single-container SAP HANA system to running in the
tenant database of the same system converted to support multitenancy.
Context
This tutorial takes you through the following steps:
1. Installing an SAP HANA system in single-container mode [page 13].
2. Installing and configuring SAP DCC on the single-container system [page 17].
3. Converting and configuring the SAP HANA system to support multitenancy [page 20].

Previous task: Uninstalling SAP DCC [page 12]
1. Install an SAP HANA System in Single-Container Mode

In this step, you'll install an SAP HANA system, MD0, in single-container mode using the SAP HANA database
lifecycle manager. This is the system on which you'll then install SAP DCC.
Prerequisites
You're logged on as root user.
You're familiar with installation tools and procedures as documented in the SAP HANA Server Installation
and Update Guide.

PUBLIC
13
Procedure
1. Change to the following directory on the installation medium:
<installation medium>/DATA_UNITS/HDB_LCM_LINUX_X86_64
2. Start the SAP HANA database lifecycle manager interactively in the command line:
./hdblcm
Note
You can also use the graphical user interface tool ./hdblcgui.
3. Select the index for Install New System, then select Enter .
4. Select the components you would like to install as a comma-separated list, then select Enter .
5. Specify the SAP HANA system properties when prompted.
In particular, select the single_container value for the Database Mode property. For more information
about the other system properties, see the SAP HANA Sever Installation and Update Guide.
6. Once you've provided the installer with all requested responses, enter y to continue:
14
PUBLIC

7. Check for errors in the installation log:

cat /var/tmp/hdb_<SID>_install_<timestamp>/hdbinst.log |grep ERROR
8. Open the SAP HANA studio and add the system:

PUBLIC
15
The system MD0 appears in the Systems view:
Results
The system MD0 is now up and running and you can install SAP DCC.
Related Information
SAP HANA Server Installation and Update Guide (PDF)
SAP HANA Server Installation and Update Guide (HTML)
16
PUBLIC

2. Install and Configure SAP DCC on Single-Container

System
In this step, you'll install SAP DCC by importing the corresponding delivery unit (DU) into the newly installed
system. Then, you'll configure SAP DCC and add systems to be monitored.
Prerequisites
You're familiar with deploying and configuring SAP DCC as described in the SAP DB Control Center 4
Guide and SAP Note 2188247.
You're a registered user of SAP Service Marketplace and you have the Download Software authorization.
Your database user has the following privileges required to import the SAP DCC DU using the SAP HANA
studio:
System privilege REPO.IMPORT
Package privileges REPO.READ and REPO.ACTIVATE_IMPORTED_OBJECTS on the root
package .REPO_PACKAGE_ROOT
Procedure
1. Download SAP DB Control Center 4 from the SAP Software Download Center (http://support.sap.com/
swdc ).
a. In the Software Download Center, click Search for Software:
b. Enter SAP DB Control Center, and choose Search.

PUBLIC
17
c. Add the target release SP10 Patch1 for SAP DB CONTROL CENTER 4 to the download basket, select
the download basket, and then click the patch description to download.
2. Unpack the file into a temporary directory and note the location of the HANADBCC.tgz file.
3. Import the SAP DCC DU (HANADBCC.tgz) using the SAP HANA studio and check for successful activation.
Note
Instead of the SAP HANA studio, you could also use SAP HANA Application Lifecycle Management to
import the DU. For more information, see Import a Delivery Unit in the SAP HANA Application Lifecycle
Management Guide.
a. In the SAP HANA studio, choose
Next.
File
Import
SAP HANA Content
Delivery Unit
and then
b. Select the target system you wish to import the SAP DCC DU to (in this example, MD0) and choose
Next.
c. Select the Client option and browse for the HANADBCC.tgz file that you unpacked above.
18
PUBLIC

d. Check the object import simulation to make sure there are no errors and choose Finish to complete
the import.
e. Review the information in the Job Log view to make sure the DU import completes successfully.
4. Configure SAP DCC.
You need to configure the XS server, create administrator accounts update passwords, and create user
accounts.
a. In the SAP HANA studio, open the SQL console connected to the system MD0.
b. Execute the SQL statements for configuring SAP DCC.
The SQL statements for configuring SAP DCC are available in the Configuring with SQL section of the
SAP DB Control Center 4 Guide.
5. Configure SAP HANA Extended Application Services (SAP HANA XS) for SAP DCC using the SAP HANA
XS Administration Tool.
You need to set up a trust store and configure data collections, message queue maintenance, and the job
worker task. For more information, see Configuring SAP HANA XS in the SAP DB Control Center 4 Guide.
6. Log on to SAP DCC as the DCC administrator.
The URL is: http://<host>.corp:80<instance>/sap/hana/dbcc.
7. Register the systems to be monitored in the system directory.

PUBLIC
19
For more information about adding systems, see System Directory in the SAP DB Control Center 4 Guide.
8. Check the status of registered system in the Enterprise Health Monitor.
For more information, see Enterprise Health Monitor in the SAP DB Control Center 4 Guide.
Related Information
SAP DB Control Center 4 Guide (PDF)
SAP DB Control Center 4 Guide (HTML)
SAP HANA Application Lifecycle Management (PDF)
SAP Note 2188366
Request User for SAP Service Marketplace
3. Convert and Configure System for Multitenancy

In this step, you'll convert the MD0 system on which SAP DCC is running into a multiple-container system.
Afterward, SAP DCC will be running on the first tenant database in the multitenant system.
Prerequisites
You have operating system access to the SAP HANA system.
Procedure
1. Log on to the server as the operating system user, in this case md0adm.
2. Run the conversion script:
python /usr/sap/MD0/HDB00/exe/python_support/convertMDC.py
When prompted, enter and confirm a password for the SYSTEM user of the system DB.
The system now supports multitenancy and has two databases: the system database (SYSTEMDB) and one
tenant database (MD0) that corresponds to the original system.
Note
When you convert a system, the name of the first tenant database is the same as the SID of the system.
20
PUBLIC

3. In the SAP HANA studio, add the system database with the SYSTEM user.
Note
You will have to change the password of the SYSTEM user since this is the first time this user is logging
on.
4. Connected to the system database, open the SQL console and start the tenant database:
ALTER SYSTEM START DATABASE MD0;
Now, if you refresh the Systems view, you'll see both the system database and the tenant database MD0
as up and running.

PUBLIC
21
Note
Because you added MD0 when it was a single-container system, it still looks like a single-container
system. If you were to remove it and re-add it as a tenant database, then it would be identified as a
tenant database (MD0@MD0):
5. Check the M_DATABASES view to confirm the creation of the system database and tenant database:
SELECT TOP 1000 * FROM "SYS"."M_DATABASES";
6. Deploy all auto-content delivery units on the system database:

a. In the console, change to the following directory:
cd /usr/sap/MD0/SYS/global/hdb/install/bin
b. Start the repository update tool:
./hdbupdrep
Note
When prompted to enter the password of the SYSTEM user, enter the password of the SYSTEM
user of the system database.
22
PUBLIC

7. Configure HTTP access to the tenant database by entering the URLs by which the tenant database is
publicly accessible in the xsengine.ini file.
You can do this in the Administration editor on the Configuration tab, or by executing the following
statements in the SQL console (connected to the system database):
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'database', 'MD0) SET
('public_urls', 'http_url') = 'http://<tenant_FDQN>:8000 ' WITH RECONFIGURE;
ALTER SYSTEM ALTER CONFIGURATION ('xsengine.ini', 'database', 'MD0) SET
('public_urls', 'https_url') = 'https://<tenant_FDQN>:4300 ' WITH RECONFIGURE;
8. Check the status of the xsengine service on the tenant database by opening the Administration editor of
the tenant database and choosing the Landscape tab.
If the xsengine service is in the list of services, the XS server on the tenant database is running as a
separate service. After a conversion, this should be the case. However, if you want it to run as an
embedded service in the index server, follow these steps:
a. Open the Administration editor of the system database and choose the Configuration tab.
b. In the xsengine.ini change the value of the [httpserver] embedded parameter to true.
c. Remove the existing xsengine server by executing the following statement in the SQL console
(connected to the system database):
ALTER DATABASE MD0 REMOVE 'xsengine' AT '<host>:<port>';
Tip
You can see the port of the xsengine service on the Landscape tab.
d. Restart the system.

PUBLIC
23
9. Configure the virtual host names by which the tenant database is publicly accessible in your Domain Name
Sever (DNS).
10. Open a Web browser and check that the XS servers of both the system database and the tenant database
are accessible.
The system database is accessible under the localhost: https://<localhost>:80<instance>, or if
SSL is configured: https://<localhost>:4300.
The tenant database MD0 is accessible under the full qualified domain name (FQDN) that you specified
in step 7: http://<tenant_FDQN>:80<instance> or if SSL is configured https://<tenant_FDQN>:
43<instance>.
In both cases you should see the following screen:
11. Check that SAP DCC has been successfully migrated to the tenant database and is accessible by logging
on to SAP DCC on the tenant database:
24
PUBLIC

http://<tenant_FQDN>:80<instance>/sap/hana/dbcc
12. Change the connection information of the system monitored by SAP DCC.
If you previously configured SAP DCC to monitor the SAP HANA system on which it is installed, the
connectivity information will now be incorrect as SAP DCC has moved to the tenant database. The only
workaround is to remove the old system reference and to re-register it to SAP DCC with the new
connection information.
a. Log on to SAP DCC as a user with the DBCCAdmin role.
b. Open the system directory.
c. Select the system representing the single-container SAP HANA system on which SAP DCC was
originally installed.
d. On the System Information screen, select Remove System and confirm.
e. Add the SAP HANA system representing the tenant database.
13. Optional: Register the system database in SAP DCC.
Remember
The host of the system database is not the FQDN but the localhost name.

PUBLIC
25
Configuration: SAP DCC
Set up SAP DB Control Center to monitor and manage SAP database products, including SAP HANA.
3.1
Setting up SAP DCC
Configure the SAP HANA XS engine for SAP DB Control Center. Perform these steps for single-container SAP
HANA systems and for tenant systems in SAP HANA multitenant database containers.
Context
SQL option: If you are configuring a typical single-container SAP HANA system, you can execute SQL
statements instead of performing the steps below. For details, see Configuring with SQL [page 33].
If you are configuring a system running SAP HANA multitenant database containers, complete the steps below
before using SQL for any SAP DCC configuration.
Procedure
1. In SAP HANA studio, go to the Systems view in the Administration Console.
2. Right-click a system running SAP DCC, then select
Configuration and Monitoring
Open
Administration .
For SAP HANA multitenant database containers, the SAP DCC system must be a tenant container, not a
system container.
3. Click the Configuration tab.
4. Right-click xsengine.ini and select Add Section.
5. Enter the name scheduler and click Next.
6. Click the Assign Values to menu to display its options.
7. Select Database and click Next.
8. Enter:
Key: enabled
Value: true
9. Click Finish.
10. Right-click xsengine.ini and select Add Section again.
26
PUBLIC

11. Enter the name httpserver and click Next.
Note
The httpserver section might be present already, but SAP recommends that you follow the steps below
to ensure that it is configured correctly for SAP DCC.
12. Click the Assign Values to menu to display its options.
13. Select Database and click Next.
14. Enter:
Key: sessiontimeout
Value: a value in seconds (for example, 3600 sets a session timeout of one hour)
Note
If a session timeout value has already been set, consult your security administrator before changing it.
In many organizations, session timeout values are dictated by security policy.
15. Click Finish.
3.2
Setting up the System Configuration Login Account
Grant the SYSTEM account (or an equivalent login account) special privileges that allow it to complete initial
configuration of SAP DB Control Center.
Context
The SYSTEM account's DBCCConfig role gives it access to the /sap/hana/xs/admin configuration tool. SAP
does not recommend granting this access to other SAP DCC users, including administration users such as
DCC_ADM. Further, SAP suggests that when you finish setting up SAP DCC, you remove the DBCCConfig role
from the SYSTEM account if you do not expect to be performing ongoing configuration.
SQL option: Instead of performing the steps below, you can execute SQL statements. For details, see
Configuring with SQL [page 33].
Procedure
1. In SAP HANA studio, open the SYSTEM account (or another account with the DBCCConfig role) under
Security
Users .
2. Select the Granted Roles tab and click +.

3. Select sap.hana.dbcc.roles::DBCCConfig and click Ok.

PUBLIC
27
4. Press F8 to deploy the role change to SAP HANA.
3.3
Setting up Administrator Accounts
Create a new user account and grant it administrative privileges or grant the privileges to an existing user.
Context
Users with administrative roles can add, import, and delete systems. Set up at least one administrator account
by:
Granting the DBCCAdmin and Monitoring roles to an existing user, or
Creating a new account for the purpose (we use DCC_ADM as an example) and granting it the
DBCCAdmin and Monitoring roles.
Procedure
1. In the SAP HANA studio Systems view, expand the SAP HANA system on which SAP DB Control Center is
installed, then expand
Security
Users .
2. To create a new administrative user:

a. Right-click the
Security
Users
folder and select New User.
b. Enter the new user's name (for example, DCC_ADM). Enter a temporary password such as AAA111aaa.
You will change the password later in the configuration process.
3. To grant roles to an existing user, double-click the user name under Users.
5. Select these roles and click Ok after each selection:
sap.hana.admin.roles::Monitoring
sap.hana.dbcc.roles::DBCCAdmin
6. Press F8 to deploy the role changes to SAP HANA.
Next Steps
(Optional) Create additional administration accounts with the same roles as DCC_ADM.
28
PUBLIC

3.4
Setting up the Collector Account
Create the technical user account SAP DB Control Center will use to run data collection, maintenance, and
worker thread jobs, then grant it monitoring and administration privileges.
Context
You can give this technical user account any name you like; here we call it DCC_COLLECTOR. The account
runs collection jobs to gather the availability, performance, capacity, and alerts data that SAP DCC displays for
each system it monitors. It also runs the jobs for multiple worker threads and cleaning up the message queue.
Note
An expired password can disable the collector account's collection and housekeeping jobs. If you have
password expiration policies in force, SAP recommends that you configure exemptions for the collector
account and for any other accounts you use for monitoring, so that their passwords do not expire. For
information on managing password lifetime, see the SAP HANA Security Guide. See also Configuring with
SQL [page 33], which includes a statement that disables password expiration
Procedure
1. In SAP HANA studio, right-click the
Security
Users
2. Enter a name tor the new user (for example, DCC_COLLECTOR). Enter a temporary password such as
AAA111aaa.
4. Select the sap.hana.dbcc.roles::DBCCCollector role and click Ok.

PUBLIC
29
3.5
Setting up User Accounts
(Optional) Create accounts for general users , and grant them monitoring and user privileges.
Context
Procedure
1. In SAP HANA studio, right-click the
Security
Users
2. Enter a name for the new user (for example, DCC_USR). Enter a temporary password such as AAA111aaa.
4. Select these roles and click Ok after each selection:
sap.hana.admin.roles::Monitoring
sap.hana.dbcc.roles::DBCCUser
Next Steps
(Optional) Create additional user accounts with the same roles as DCC_USR.
3.6
Updating Passwords
Change the temporary initial passwords for the user accounts you just created.
Context
Perform these steps for the new accounts you created, including these (under whatever names you assigned
to them):
30
PUBLIC

DCC_ADM (administrator account)

DCC_COLLECTOR (account for collections and other background tasks)
DCC_USR (general user accounts)
If you created extra administrator or user accounts, update their passwords too.
Note
If your SAP HANA system is configured such that passwords do not need to be changed upon first login,
you can skip this task.
Procedure
1. In SAP HANA studio, right-click the SAP DCC host SAP HANA system and select Add system with different
user.
2. Enter the user ID and temporary password of the account you are updating. For example,
DCC_COLLECTOR/AAA111aaa.
3. Click Finish.
4. When the system prompts you, enter and confirm a new password.
Note
Make a note of each new passwordyou will need them for the tasks that follow.
Next Steps
Repeat the steps for all the accounts you want to update.
3.7
Configuring SAP HANA XS
In SAP HANA Extended Application Services (SAP HANA XS), set up a trust store and configure data
collections, message queue maintenance, and the job worker task.
Prerequisites
Have updated passwords available for these accounts:
The SYSTEM account or an account with the same roles

PUBLIC
31
The DCC_COLLECTOR account or an account with the same roles
Context
For more on SAP HANA XS and SQLCC, see the SAP HANA Administration Guide.
Procedure
43<instance_number>
2. Log in using SYSTEM or an equivalent account.
3. To set up a trust store:
a. In the left pane, click the arrows to expand
b. Click the Configuration menu icon
sap
hana
dbcc
and select services.
(upper left).
c. In the left pane, click Trust Manager.

d. At the bottom of the screen, click Add to create the trust store. Name it SAP_HANA_DBCC.
e. Click OK.
SAP_HANA_DBCC appears in the Trust Store area.
For more on managing trust stores, click the Help Content icon
at the top of the screen.
4. To enable collection of data:

a. In the left pane, click XS Artifact Administration.
b. Click the arrows to navigate to
sap
hana
dbcc
collections .
c. Click ScheduleCollections.xsjob.
d. Click Configuration (upper right).
e. Set the user to the collector account (for example, DCC_COLLECTOR) and enter the collector
account's password.
f. Select the Active check box.
g. Click Save Job.
Look for a message at the bottom of the screen: Job saved successfully.
5. To enable multiple worker threads:
sap
hana
dbcc
jobs .
c. Click JobWorkerTask.xsjob.
account's password.
32
PUBLIC


g. Click Save Job.
Note
Do not add schedules for this jobSAP DB Control Center adds them automatically.
6. To enable maintenance, which cleans up the message queue:
sap
hana
dbcc
maintenance .
c. Click Maintenance.xsjob.
account's password.
g. Click Save Job.
3.8
Configuring with SQL
You can perform a number of the configuration tasks for SAP DB Control Center using SQL.
For ease of cutting and pasting, the sample SQL statements below are provided together, but do not cut and
paste blindly. Read these sections for explanations and caveats that may prevent you from breaking
something or aggravating your administrators:
Setting up SAP DCC [page 26]
Setting up the System Configuration Login Account [page 27]
Setting up Administrator Accounts [page 28]
Setting up the Collector Account [page 29]
Setting up User Accounts [page 30]
The sample SQL statements use a password placeholder that is not a valid password. To avoid password
errors, replace each occurence of my_Password with a valid password.
You can execute SQL statements in SAP HANA HDBSQL, in the SAP HANA studio SQL console, or in the SQL
console provided in the cockpit for your monitored product. To execute SQL in SAP HANA studio:
1. In the System view, identify the system where you want to execute the SQL. All the SQL samples provided
are intended for execution on the SAP HANA system where SAP DCC is installed; also execute the
statements for setting up the technical user account on each system you plan to monitor.
2. Right-click the system you identified and select Open SQL Console.
3. Insert the SQL in the SQL Console.
4. Modify the SQL as needed. For example, replace my_Password with a valid password.
5. Press F8 to execute the SQL statements.

PUBLIC
33
SQL for SAP DCC on Single-Container SAP HANA Systems

Use these SQL statements to configure SAP DCC on a single-container SAP HANA system (a single-container
configuration is typical). For a system running SAP HANA multitenant database containers, see the next
section.
Sample Code
-- Setting up SAP DCC
-- Configure and start the scheduler:
alter system alter configuration ('xsengine.ini','SYSTEM')
set('scheduler','enabled')='true' with reconfigure;
-- Configure the session timeout for SAP HANA XS:
alter system alter configuration ('xsengine.ini','SYSTEM')
set('httpserver','sessiontimeout')='3600' with reconfigure;
-- Setting up the SYSTEM account
call "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCConfig',
'SYSTEM');
-- Setting up an Administrative Account
-- Create an admin user (DCC_ADM in this example) and assign a
-- password (optional - you can also assign the roles to an
-- existing account in the next step):
create user DCC_ADM password "my_Password";
-- Grant the DBCCAdmin and Monitoring roles to a user account
-- (DCC_ADM in this example):
call "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCAdmin',
'DCC_ADM');
call "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.admin.roles::Monitoring',
'DCC_ADM');
-- Setting up the Collector Account
-- Create the collector user (DCC_COLLECTOR in this example) and
-- assign a password:
create user DCC_COLLECTOR password "my_Password";
-- Grant the DBCCCollector role to the new account:
call
"_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCCollector',
'DCC_COLLECTOR');
-- Disable password expiration for the new account (optional):
alter user DCC_COLLECTOR disable password lifetime;
-- Setting up User Accounts
-- Create a user (DCC_USR in this example) and assign a password:
create user DCC_USR password "my_Password";
-- Grant the DBCCUser and Monitoring roles to the new account:
call "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCUser',
'DCC_USR');
'DCC_USR');
34
PUBLIC

-- Setting up the Technical User Account (do this on every system you plan to
monitor)
-- Create the technical user, SAPDBCC, with a temporary password:
create user SAPDBCC password "my_Password";
-- Grant the Monitoring role to the new account:
'SAPDBCC');
alter user SAPDBCC disable password lifetime;
After executing the SQL, return to the documented configuration tasks, starting with Updating Passwords
[page 30].
SQL for SAP DCC with SAP HANA Multitenant Database Containers
Before you execute these statements, you must follow the steps in Setting up SAP DCC [page 26]. Then return
here and use these SQL statements to continue configuring SAP DCC on a system running SAP HANA
multitenant database containers.
Sample Code
-- Setting up the SYSTEM account
call "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCConfig',
'SYSTEM');
-- Setting up an Administrative Account

-- Create an admin user (DCC_ADM in this example) and assign a
-- password (optional - you can also assign the roles to an
-- existing account in the next step):
create user DCC_ADM password "my_Password";
-- Grant the DBCCAdmin and Monitoring roles to a user account
-- (DCC_ADM in this example):
call "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCAdmin',
'DCC_ADM');
'DCC_ADM');
-- Setting up the Collector Account
-- Create the collector user (DCC_COLLECTOR in this example) and
-- assign a password:
create user DCC_COLLECTOR password "my_Password";
-- Grant the DBCCCollector role to the new account:
call
"_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCCollector',
'DCC_COLLECTOR');
alter user DCC_COLLECTOR disable password lifetime;

PUBLIC
35
-- Setting up User Accounts

-- Create a user (DCC_USR in this example) and assign a password:
create user DCC_USR password "my_Password";
-- Grant the DBCCUser and Monitoring roles to the new account:
call "_SYS_REPO"."GRANT_ACTIVATED_ROLE"('sap.hana.dbcc.roles::DBCCUser',
'DCC_USR');
'DCC_USR');
-- Setting up the Technical User Account (do this on every system you plan to
monitor)
-- Create the technical user, SAPDBCC, with a temporary password:
create user SAPDBCC password "my_Password";
-- Grant the Monitoring role to the new account:
'SAPDBCC');
alter user SAPDBCC disable password lifetime;
After executing the SQL, return to the documented configuration tasks, starting with Updating Passwords
[page 30].
3.9
Optional Configuration
Tasks described in this section are not required for SAP DB Control Center to run, but may enhance security
or performance.
3.9.1
Configuring Single Sign-On
In a single sign-on (SSO) environment, you log in once, either on an SAP HANA server or on a client such as a
monitored server or its cockpit, and that authentication gives you access to the server and clients as if you had
logged in to each one separately.
SAP HANA supports several SSO mechanisms, including Security Assertion Markup Language (SAML),
Kerberos, X.509 client certificates (for HTTP access via SAP HANA XS only), and SAP logon/assertion tickets.
For SAP DB Control Center, we explain how to set up SSO using SAML.
Granting the DBCCUser Role to All New Users [page 37]
(Optional, recommended) Configure SAP HANA to grant an SAP DB Control Center role to new user
accounts. The DBCCUser role (or another SAP DCC role with greater permissions) is required for
accounts that will use SAP DCC.
Enabling Single Sign-On for SAP DCC [page 39]
Set up SAP DB Control Center to use single sign-on authentication.
36
PUBLIC

3.9.1.1
Granting the DBCCUser Role to All New Users
(Optional, recommended) Configure SAP HANA to grant an SAP DB Control Center role to new user accounts.
The DBCCUser role (or another SAP DCC role with greater permissions) is required for accounts that will use
SAP DCC.
Prerequisites
Set up a SAML identity provider (IDP).
Configure single sign-on for each system you plan to monitor with SAP DCC. On SAP HANA systems,
configure SAP HANA XS to use the SAML IDP.
SAP recommends that you enable dynamic user creation when you configure SAP HANA XS with the
SAML IDP. Dynamic user creation automatically sets up a SAP HANA user account for any user who
authenticates. If you do not enable dynamic user creation, you must provide some other method of linking
user accounts to authenticated users. For example, you can add user accounts manually (granting each
one an SAP DCC role such as DBCCUserRole) or link all incoming connections to a single existing user with
an appropriate SAP DCC role.
For details on configuring single sign-on in SAP HANA:
In the SAP HANA Security Guide, see:
SAP HANA Authentication and Single Sign-On
SAP HANA Authentication and Single Sign-On > Single Sign-On Using SAML 2.0
SAP HANA Authentication and Single Sign-On > Single Sign-On Using Kerberos
In the SAP HANA Administration Guide, see:
Security Administration > Managing SAP HANA Users > User Authentication and Single Sign-On
Security Administration > Managing SAP HANA Users > User Authentication and Single Sign-On >
Configuring SAP HANA for User Authentication and Single Sign-On
Configuring SAP HANA for User Authentication and Single Sign-On > Add an SAML Identity Provider
Configuring SAP HANA for User Authentication and Single Sign-On > Configure Kerberos for SAP HANA
Database Hosts
Context
You can configure SAP HANA to automatically grant the DBCCUser role to each user account it creates upon
first authentication of a new user if:
You are configuring a SAP HANA server that will be used primarily for SAP DB Control Center
You enabled dynamic user creation when you configured SAP HANA XS with the SAML Identity Provider
(IDP)
Following the steps below, create a new database role in SAP HANA studio, called, for example,
DBCC_USER_SSO, and grant DBCCUser role to the new database role. Then set DBCC_USER_SSO as the

PUBLIC
37
default role for saml in indexserver.ini. This allows DBCC_USER_SSO to be automatically granted to
dynamically created users.
Procedure
1. In SAP HANA studio, use the SYSTEM account (or an account that has the DBCCConfig role) to log in to a
SAP HANA server you plan to use primarily for SAP DCC.
2. In the System view, click the arrows next to object names to expand the server and the Security folder.
3. Right-click Roles and select New Role.
4. Give the new role a name (for example, DBCC_USER_SSO).
5. On the Granted Roles tab, click + and select:
sap.hana.dbcc.roles::DBCCUserRole
6. Click Ok.
7. Set the new database role you just created (here called DBCC_USER_SSO) to be the default role for
dynamically generated users:
a. In the System view on the left, double-click the SAP HANA system you logged in to in step 1 [page 38].
b. Click the Configuration tab.
c. Expand indexserver.ini and look for saml.
d. If saml is not present, add it:
Right-click indexserver.ini and select Add Section.
For the section name, enter saml.
On the Scope Selection page, leave Assign Values to set to System and click Next.
On the Key Value Pairs page, enter:
Key: defaultrole
Value: DBCC_USER_SSO (or whatever name you gave the role created in step 4 [page 38])
Click Finish.
e. If saml appears under indexserver.ini, right-click saml and select Add Parameter.
f. On the Scope Selection page, leave Assign Values to set to System and click Next.
g. On the Key Value Pairs page, enter:
Key: defaultrole
Value: DBCC_USER_SSO (or whatever name you gave the role created in step 4 [page 38])
h. Click Finish.
Task overview: Configuring Single Sign-On [page 36]
Related Information
Enabling Single Sign-On for SAP DCC [page 39]
38
PUBLIC

3.9.1.2
Enabling Single Sign-On for SAP DCC
Set up SAP DB Control Center to use single sign-on authentication.
Prerequisites
Set up a SAML identity provider (IDP).
Configure single sign-on for each system you plan to monitor with SAP DCC. On SAP HANA systems,
configure SAP HANA XS to use the SAML IDP.
SAP recommends that you enable dynamic user creation when you configure SAP HANA XS with the
SAML IDP. Dynamic user creation automatically sets up a SAP HANA user account for any user who
authenticates. If you do not enable dynamic user creation, you must provide some other method of linking
user accounts to authenticated users. For example, you can add user accounts manually (granting each
one an SAP DCC role such as DBCCUserRole) or link all incoming connections to a single existing user with
an appropriate SAP DCC role.
Grant the DBCCUser role to all dynamically created user accounts (optional but recommended) [page 37]
For details on configuring single sign-on in SAP HANA:
In the SAP HANA Security Guide, see:
SAP HANA Authentication and Single Sign-On
SAP HANA Authentication and Single Sign-On > Single Sign-On Using SAML 2.0
SAP HANA Authentication and Single Sign-On > Single Sign-On Using Kerberos
In the SAP HANA Administration Guide, see:
Security Administration > Managing SAP HANA Users > User Authentication and Single Sign-On
Configuring SAP HANA for User Authentication and Single Sign-On
Configuring SAP HANA for User Authentication and Single Sign-On > Add an SAML Identity Provider
Configuring SAP HANA for User Authentication and Single Sign-On > Configure Kerberos for SAP HANA
Database Hosts
Context
Enable single sign-on both for SAP DCC itself and for the UI (SAP Fiori), as described in these steps.
Procedure

PUBLIC
39
43<instance_number>
2. Log in using the SYSTEM account (or an account that has the DBCCConfig role).
3. In the left pane, click the arrows to expand
sap
hana
and select dbcc.
4. On the Security & Authentication tab, click Edit (bottom right).

5. Under Authentication Methods, select a single sign-on option. In this example, we use SAML.
6. Click Save.
7. In the left pane, select uis.
8. On the Security & Authentication tab, click Edit (bottom right).
9. Under Authentication Methods, select the same single sign-on option you selected in step 5 [page 40].
10. Click Save.
Task overview: Configuring Single Sign-On [page 36]
Related Information
Granting the DBCCUser Role to All New Users [page 37]
3.9.2
Configuring Connection Security
Set security for browser connections to SAP DB Control Center.
Context
By default, you can use either nonsecured HTTP or secured HTTPS when you connect to SAP DCC with a Web
browser. You make the choice by choosing a port:
Table 3:
Instance 00
Instance 01
HTTP
8000
8001
HTTPS
4300
4301
SAP recommends using HTTPS for browser connections. However, it requires an SSL certificate, which you
may have to purchase.
40
PUBLIC

If you force the use of HTTPS, be sure to inform users of which port to use to connect to SAP DCC. When SAP
DCC is configured to force use of SSL, access attempts via an HTTP ports result in 403 "Forbidden" errors.
(Most procedures provided here use HTTPS ports only.)
Note
If Force SSL is configured on a SAP HANA system or cockpit being monitored by SAP DCC (including the
SAP HANA system where SAP DCC is installed), you must also configure Force SSL on SAP DCC. However,
it is ok to configure Force SSL on SAP DCC even if it is not configured on SAP HANA or the cockpit.
Follow the steps below if you want to:
Force the use of SSLthat is, to always use a secure HTTPS connection.
Stop forcing the use of SSL.
Procedure
http[s]://<hana.host.name>:<port>/sap/hana/xs/admin
where the value of <port> is depends on the connection protocol and the 2-digit SAP HANA instance
number:
For HTTP: 80<instance_number>
For HTTPS: 43<instance_number>
For example, use port 8000 for an HTTP connection to instance 00. Use port 4301 for an HTTPS
connection to instance 01.
sap
hana
and select dbcc.
4. Select the Security & Authentication tab.

5. Click Edit (bottom right).
6. Click to select (or unselect) the Force SSL checkbox.
7. Click Save.
3.9.3
Enabling a Proxy Server
Configure SAP DB Control Center to use a proxy server to connect to the systems it manages.
Prerequisites
You need access to the SYSTEM account or an account with the same roles.
Determine the proxy host, port, user, and proxy type. Consult your IT department if you need help.

PUBLIC
41
Context
Use SAP HANA Extended Application Services (SAP HANA XS) to set a default proxy. Configuring a default
proxy activates the proxy options you can use when you add systems:
For adding systems one at a time, the Use HTTP proxy for this host checkbox on the Add System page
For adding systems in batch, the useproxy option in the import file
Note
You can configure only one proxy at a time, the default proxy. Each system you add to SAP DCC copies the
default proxy information rather than pointing to it, so if you change the default proxy, only systems added
after the change use the new proxy. Systems added before the change continue to use the old default
proxy. To change proxy servers for a system already added to SAP DCC, you must remove the system,
change the default proxy, and add the system to SAP DCC again.
Procedure
43<instance_number>
default.xshttp.
sap
hana
dbcc
services
dest
and select the file
4. Click Edit.
5. On the Proxy Details tab, set the proxy type, proxy host, proxy port, and (if required in your environment)
the proxy user and password.
6. Click Save.
3.9.4
Configuring Storage of Historical Data
(Optional) Set SAP DB Control Center to save the status data it receives from monitored systems. You can use
the saved data to graph trends in availability, performance, capacity, and alerts.
Prerequisites
Log in using DCC_ADM or another account with the DBCCAdmin role.
42
PUBLIC

Context
Two options control the storage of historical data:
apca.historical.enabled Turns data storage on (1) or off (0). Default is off.
apca.historical.purge.max_age Specifies the age in minutes at which stored historical data can be
deleted by an automatic purge process. Valid values are 5 52560000 (about 100 years); default is
43200 (30 days).
Stored historical data is relatively lightweight. By default, SAP DCC collects status data from each monitored
system every minute. At that collection rate, SAP DCC gathers about 100KB of historical data per monitored
system per day. At the default purge interval of 30 days, each monitored system requires approximately 3MB
of storage. Some purge scenarios:
Table 4:
Monitored Systems
Purge max_age in Days Max_age Value in Minutes
30 (the default)
Storage Required (RAM or disk, ap

proximate)
43200
3MB
90
129600
9MB
365
525600
36.5MB
15
30
43200
45MB
15
90
129600
135MB
15
365
525600
547.5MB
50
30
43200
150MB
50
90
129600
450MB
50
365
525600
1.825GB
Note
Historical data can grow quickly and use up significant system resources. However, if you work with data
covering a longer period of time, you are more likely to notice meaningful trends. Weigh these factors as you
choose the max_age value for purging historical data.
Execute SQL statements to set the historical data options. You can use SAP HANA HDBSQL, the SAP HANA
studio SQL console, or the SQL console provided in the cockpit for your managed server.
Procedure
1. Enable SAP DCC to store monitoring data:
Sample Code
upsert "SAP_HANA_DBCC"."sap.hana.dbcc.data::Site.PreferenceValues" ("name",
"v_int")
values('apca.historical.enabled', 1) with primary key

PUBLIC
43
2. Set SAP DCC to purge old data. Set the max_age value in minutes. In this example, we specify that data
older than 21,600 minutes (15 days) will be deleted:
Sample Code
"v_int")
values('apca.historical.purge.max_age', 21600) with primary key
3. (Optional) Disable storage of monitoring data:
Sample Code
"v_int")
values('apca.historical.enabled', 0) with primary key
Next Steps
Visualize stored data using a tool of your choice (for example, SAP Lumira, SAP Crystal Reports, or Microsoft
Excel). For details on the schema, see Schema for Stored Historical Data [page 44].
Schema for Stored Historical Data [page 44]
You can access historical monitoring data stored in the SAP_HANA_DBCC schema.
3.9.4.1
Schema for Stored Historical Data
You can access historical monitoring data stored in the SAP_HANA_DBCC schema.
Table 5: Columns in the sap.hana.dbcc.data::APCA.Historical Table
Column Name
Column Description
resourceID
A key pointing to the

RES_ID column of the RE
SOURCES table
timestamp
Date and time when the

data was collected
result
The result of the attempt to

collect monitoring data
Ok
The condition of the moni

tored system
Unknown
Stopped
state
44
PUBLIC
Values
Value Description
Failed

Column Name
Column Description
availability
performance
capacity
alertHigh
alertMedium

Count of high-level alerts
Count of medium-level
alerts
Values
Value Description
Pending
Running
Warning
Error
-1
State not collected
-2
State reporting not supported for this system
High priority: attention needed immediately
Medium priority: attention needed
Low priority
No problems
-1
Availabilty not collected
-2
Availabilty reporting not supported for this sys

tem
Low priority
No problems
-1
Performance not collected
-2
Performance reporting not supported for this

system
Low priority
No problems
-1
Capacity not collected
-2
Capacity reporting not supported for this sys

tem
<Any positive
number>
The number of alerts at this level
No alerts at this level
-1
Alert count not collected
-2
Alert count reporting not suppored at this level
<Any positive
number>
-1
PUBLIC
45
Column Name
alertLow
alertInfo
Column Description
Count of low-level alerts
Count of info-level alerts
Values
Value Description
-2
<Any positive
number>
-1
-2
<Any positive
number>
-1
-2
Parent topic: Configuring Storage of Historical Data [page 42]
46
PUBLIC

Configuration: Monitored Systems
Perform the tasks in this section on each system you plan to monitor with SAP DB Control Center.
You can monitor:
Typical single-container SAP HANA systems (SPS09 or later)
SAP HANA multitenant database container systemsboth system database containers and tenant
database containers
Other SAP database systems, provided their documentation describes configuration for SAP DCC
(including instructions on setting up a technical user)
4.1
Setting up the Technical User Account on Monitored

Systems
On every SAP HANA system you will monitor with SAP DB Control Center, create an SAPDBCC user account,
grant it monitoring privileges, and add the SAPDBCC account to the SQL connection configuration (SQLCC) in
SAP HANA XS.
Prerequisites
Add the sap.hana.xs.admin.roles::SQLCCAdministrator role to an account on the system you plan to monitor
with SAP DB Control Center. Use that account to set up the technical user. (On a system running SAP DCC,
SQLCCAdministrator is among the roles granted to the SYSTEM user by the DBCCConfig role.)
Context
When you add (register) systems, SAP DCC uses the technical user account, SAPDBCC, to scan hosts for
systems that can be added and monitored.
If SAP DCC finds a system and you choose to add it, you are prompted to supply credentials for a monitoring
login that SAP DCC will use to collect high-level health data from the system's cockpit, including up/down
status and alert counts. (This monitoring collection occurs every minute.) Though you can use any SAP HANA
account that has the role sap.hana.admin.roles::Monitoring, SAP recommends that you use SAPDBCC as the
monitoring login. SAPDBCC has the required role (you set it up during installation and configuration), so you
do not have to set up another account.

PUBLIC
47
Note
An expired password can disable monitoring functions. If you have password expiration policies in force,
SAP recommends that you configure exemptions for the SAPDBCC technical user account and for any
other accounts you use for monitoring, so that their passwords do not expire. For information on managing
password lifetime, see the SAP HANA Security Guide.
Procedure
1. In SAP HANA studio, log in to the system you plan to monitor using the SYSTEM account or another
account with the DBCCConfig role.
2. Right-click the
Security
Users
3. For the new user's name, enter SAPDBCC. Enter a temporary password such as AAA111aaa.
5. Select the sap.hana.admin.roles::Monitoring role and click Ok.
7. To update the temporary password:
a. Right-click the SAP HANA system and select Add system with different user.
b. Enter SAPDBCC and the temporary password you set in step 3 [page 48].
c. When the system prompts you, enter and confirm a new password for SAPDBCC.
43<instance_number>
10. Click the XS Administration Tools icon (top left), then in the left pane, click XS Artifact Administration.
11. Click the arrows to expand
sap
hana
admin
dbcc .
12. Click dbccuser.xssqlcc.

13. Click Edit (bottom right).
14. Set the user to SAPDBCC and enter the new SAPDBCC password (from step 7.c [page 48]).
15. Click Save.
Look for a message at the bottom of the screen: SQLCC configuration details successfully
saved.
48
PUBLIC

Next Steps
Repeat these steps for other SAP HANA systems to be monitored.
Related Information
SAP HANA Security Guide

PUBLIC
49
Accessing SAP DCC
Connect to SAP DB Control Center and log in.
Prerequisites
Install the HANA_DBCC delivery unit and configure it. [page 5]
Obtain a web browser compatible with SAPUI5 [page 50].
Procedure
1. Point your web browser to:
http://<HANA_server>:<port>/sap/hana/dbcc
2. Log in.
If you plan to add or import systems to SAP DCC, log in using the DCC_ADM account or an account with
the same roles and privileges.
Browser Compatibility [page 50]
Use a compatible Web browser to access SAP DB Control Center.
5.1
Browser Compatibility
Use a compatible Web browser to access SAP DB Control Center.

SAP DCC uses the SAPUI5 control library sap.m and requires a browser that supports that library (for
example, Internet Explorer 9).
For more information, see SAP Note 1716423
up the sap.m library.
. Follow its link to the latest SAPUI5 documentation and look
Parent topic: Accessing SAP DCC [page 50]
50
PUBLIC

Accessing SAP DCC
Launchpad
The customizable launchpad appears when you log in to SAP DB Control Center. It provides access to
monitoring and management tools and serves as a high-level status monitor.
Table 6:
Options menu
Log out or display information about this login session. The menu displays the name of
the logged-in user.
Search tool
Find a tile on the launchpad.
Tile group
Every tile on the launchpad belongs to a tile group.
Show/hide tile groups icon
Open or close the tile groups panel, where you can browse the tile catalog, add tiles to
the launchpad, remove them, or rearrange them. You can also create and remove tile
groups.
Default tiles
The default tiles appear in every copy of SAP DCC. They let you monitor and manage
systems known to SAP DCCclick a tile to start its app.
Launch System Directory tile - add systems to SAP DCC or remove them; add, re
move, or modify system groups. The tile displays the number of systems SAP DCC
is monitoring.
Launch Alert Monitor tile - review alerts generated by systems you are monitoring.
The tile displays the total number of alerts and the number of high priority (HP) and
medium priority (MP) alerts.
Start & Stop Systems tile - start or shut down systems you are monitoring. The tile
displays the number of systems stopped for any reason.
Monitor Enterprise Health tile - review the availability, capacity, performance, and
alerts status of systems you are monitoring. The tile displays the number of systems
running.
Adding Launchpad Tiles and Tile Groups [page 52]

Put a new tile or tile group on the launchpad.
Moving and Removing Launchpad Tiles and Tile Groups [page 53]

Launchpad
PUBLIC
51
Move a tile from one tile group to another, rearrange tiles within a tile group, or take a tile or tile group
off the launchpad.
6.1
Adding Launchpad Tiles and Tile Groups
Put a new tile or tile group on the launchpad.
Context
Tiles are clickable and give you easy access to functions and information. For example:
Add the SAP HANA Developer Guide tile so you can open the guide in your browser.
Add the SAP HANA XS Administration Tool tile so you can launch the tool in your browser.
The launchpad displays tiles in labeled groups. When you add a tile, you assign it to a tile group.
Note
Tile groups are different from system groups. For information on system groups, see Add, Remove, and
Modify System Groups [page 59].
Procedure
1. On the launchpad, click the Show/Hide Groups menu icon
(upper left).
2. Click Tile Catalog (lower left).

3. Scroll down to browse the catalog or use the All drop-down to choose a tile type (HANA Administration
and Development, for example).
4. To choose a tile, click the + below it. Select a tile group to add the new tile to or select New Group and
enter a group name.
5. Click the Home icon
added.
(upper left) to return to the launchpad and see the new tiles and tile groups you
Task overview: Launchpad [page 51]
Related Information
Moving and Removing Launchpad Tiles and Tile Groups [page 53]
52
PUBLIC

Launchpad
6.2
Moving and Removing Launchpad Tiles and Tile Groups
Move a tile from one tile group to another, rearrange tiles within a tile group, or take a tile or tile group off the
launchpad.
Procedure
1. On the launchpad, click the Show/Hide Groups menu icon
(upper left).
2. To move a tile, drag it to the desired spot.

You can move a tile within its current group or drag it into another tile group.
3. To remove a tile from a tile group, drag it toward the lower right corner of the screen. When the tile starts
to move, the corner turns red and a trash can appears. Drop the tile on the trash can.
4. To remove a tile group, drag it from the list on the left toward the lower right corner of the screen. When
the group starts to move, the corner turns red and a trash can appears. Drop the tile group on the trash
can.
You cannot remove the My Home group or the SAP DB Control Center group.
5. To change the name of a tile group, double-click the group name on the left. Edit the name and press
Return.
Task overview: Launchpad [page 51]
Related Information
Adding Launchpad Tiles and Tile Groups [page 52]

Launchpad
PUBLIC
53
System Directory
Add and manage systems and system groups.

Add and Remove Systems [page 54]
Add systems to SAP DB Control Center or remove them.You can add systems one at a time or import
many systems in a batch.
Add, Remove, and Modify System Groups [page 59]
System groups let you label sets of systems and use the labels (group names) to control which
systems are displayed on certain screens.
7.1
Add and Remove Systems
Add systems to SAP DB Control Center or remove them.You can add systems one at a time or import many
systems in a batch.
Parent topic: System Directory [page 54]
Related Information
Add, Remove, and Modify System Groups [page 59]
7.1.1
Adding a System
Add a system so you can monitor and manage it with SAP DB Control Center.
Prerequisites
Obtain the password for an SAP DCC administrator account such as DCC_ADM. For details on
administrator accounts, see Setting up Administrator Accounts [page 28].
Identify and if necessary create a user account for SAP DCC to use when it monitors this system. You can
use any SAP HANA account that has the role sap.hana.admin.roles::Monitoring. SAP recommends using
the technical user account, SAPDBCC, which is set up during installation and configuration and has the
required role. For more on the technical user account, see Setting up the Technical User Account on
Monitored Systems [page 47].
54
PUBLIC

System Directory
Context
When you add a system, you make it available to all users of SAP DCCit is not necessary for each user to add
the same systems.
Procedure
1. Log in using an SAP DCC administrator account such as DCC_ADM.
You need administration permissions to add systems.
2. On the launchpad, click Launch System Directory.
3. On the System Directory screen, click Add System (lower right corner).
4. Enter the name of the host where the system you want to manage resides.
You might need to enter a fully qualified host name. For example, if a simple name like myhost does not
work, try myhost.mycompany.com.
5. Enter the HTTPS port for the system you want to manage.
For example, 4300.
6. (Optional) Click Use HTTP proxy for this host.
The proxy option is available if you have set a default proxy server for systems monitored by SAP DCC.
7. Click Next.
SAP DCC lists the systems available on the host.
8. Select at least one system from the list and click Add.
You can select multiple systems and register them at the same time.
9. Enter a login ID and password for SAP DCC to use for monitoring the system or systems you are adding.
For example, enter SAPDBCC and its password.
10. Click Apply.
In the system directory, you can see the list of registered systems, which includes those you just added.
Related Information
Enabling a Proxy Server [page 41]

System Directory
PUBLIC
55
7.1.2
Creating an Import File
Create an ASCII import file with the information SAP DB Control Center needs to import multiple systems at
one time.
Prerequisites
Identify one or more user accounts for SAP DCC to use for collecting monitoring data. For details, see
Setting up the Technical User Account on Monitored Systems [page 47].
If you include the useproxy option for any system, make sure that a proxy has been set up. For
instructions on setting up proxies, see Enabling a Proxy Server [page 41].
Context
The import file must contain one line per system. On each line, include this information in this order, separated
by commas:
The name of the system's host.
The system's HTTP or HTTPS port.
A proxy indicator, one of {useproxy | noproxy | <empty string>}. An empty string has the same effect as
the noproxy option: this system does not use a proxy.
The system ID.
The authentication type: basic.
(Optional) The monitoring login control center will use to authenticate with the system. For example,
SAPDBCC.
(Optional) The monitoring login's password.
The syntax is:
<hostname.fully.qualified.domain.name>,<port_number>,[useproxy |
noproxy],<systemID>,basic,[<loginID>],[<password>]
For example:
#Systems in Bedrock
myserver.mycompany.com,8000,useproxy,HD1,basic
servergold.mycompany.com,8002,noproxy,HD2,basic,SAPDBCC,r0cksr0ck
serverblue.mycompany.com,4283,,ES1,basic,fred,p3bbles
When SAP DCC reads an import file, it ignores:
Lines that begin with # (comments)
Lines that do not end with a return
56
PUBLIC

System Directory
Procedure
1. Create an import file in the format described above. Save it as a comma-separated value (.csv) or text
(.txt) file.
Note
When you omit login IDs or passwords from an import file, SAP DCC prompts you during the import
processbut it prompts you for only one login/password pair, which it tries to use for each system
selected for import. This makes it easy to import multiple systems together when they use the same
login ID and password. If you are importing multiple systems with unique login ID/password
combinations, it is simplest to import the systems in separate operations, or to include all the login
credentials in the import file.
2. Save the import file on the machine where you access SAP DCC.
Next Steps
Use the import file to add systems to SAP DCC. [page 57]
7.1.3
Importing Systems in Bulk
Add two or more systems to SAP DB Control Center so you can monitor and manage them.
Prerequisites
Create an import file. [page 56]
Obtain access to an account with SAP DCC administrator privileges, such as DCC_ADM. For details on
administrator accounts, see Setting up Administrator Accounts [page 28].
Procedure
1. Log in using an SAP DCC administrator account such as DCC_ADM.
You need administration permissions to add systems.
3. On the System Directory screen, click Import Systems (lower right corner).
4. Click Browse, find the import file you created, and select it.
5. Click Load File (lower right corner).
Watch the discovery process. SAP DCC searches for the systems listed in the import file and displays:

System Directory
PUBLIC
57
A blue 'Discovered' bar for each system that is ready to import

A green 'Already Registered' bar for each system that was added previously
A red 'Error' bar with an error message for each system that cannot be found or that is not ready to
import
6. Check the box next to each system you want to add that has a blue 'Discovered' bar and click Import.
Note
If you omitted login information from the import file, ensure that all the systems you select for import
use the same login ID and password. (Perform a separate import for each group of systems that share
login credentials.) For details, see Creating an Import File [page 56].
Results
The systems you imported appear in the system directory.
7.1.4
Removing a System
Remove a system from SAP DB Control Center.
Procedure
The system directory lists all the systems known to SAP DCC.
2. Click a row to select a system.
If the list of systems is long, use these tools provided in the dialog to search, filter, or sort the list.
Table 7:
Search
Enter a full or partial system name in the search box at the top of the screen and click the
magnifying glass
string.
. The list is reduced to show only systems that match your search
The search box accepts certain regular expressions. For details, see http://
www.w3schools.com/jsref/jsref_obj_regexp.asp
Click the X
58
in the search box to cancel the search and restore the full list of systems.
PUBLIC

System Directory
Filter by system group
If you have assigned systems to groups, you can filter the system list by group. At the top
of the screen, click the filter
to display and click Ok.
. Select System Group, then select the groups you want
To cancel the filter, click the filter
again, unselect the group you filtered on, and click
Ok.
Filter by system type
You can filter the list by system type (for example, display only SAP HANA systems). At
the top of the screen, click the filter
want to display and click Ok.
Change sorting rules
. Select Type, then select the system types you
You can modify the sorting rules to:
List systems in ascending (the default) or descending order
Sort by system name (the default), connection, system type, or version
At the top of the screen, click the Sort icon
, choose sorting rules, and click Ok.
3. Click Remove System in the lower right corner of the screen, then click Yes to confirm the removal.
The selected system disappears from the list.
Note
You cannot remove the SAP HANA host system.
7.2
Add, Remove, and Modify System Groups
System groups let you label sets of systems and use the labels (group names) to control which systems are
displayed on certain screens.
For example, you might create a system group for each department or city with monitored systems (Finance,
Sales, and Development, or Boston, Amsterdam, and Seoul).
On SAP DB Control Center screens that allow you to filter systems by group (such as the system directory),
you can choose a system group to narrow the list of systems displayed.
Parent topic: System Directory [page 54]
Related Information
Add and Remove Systems [page 54]

System Directory
PUBLIC
59
7.2.1
Creating System Groups
Add a system group to SAP DB Control Center and add systems to the group.
Prerequisites
Add systems to SAP DCC. You can add one at a time [page 54] or import several systems together [page 57].
Note
System groups are different from tile groups. For information on tile groups, see Adding Launchpad Tiles
and Tile Groups [page 52].
Procedure
2. Click System Groups (on the left, above the systems list).
3. Click Create Group (lower right).
4. Enter a name for the group, add a description if you wish, and click Save Changes.
5. Select systems to include in the new group and click Add.
6. Click Save Changes again.
The new group appears in the Groups list.
7.2.2
Removing System Groups
Delete a system group from SAP DB Control Center.
Context
Deleting a system group does not delete the systems that belong to the group.
Procedure
60
PUBLIC

System Directory
3. Select a system group to remove.

If the list of groups is long, use the Search box to find the group you want. Enter a full or partial name and
click the magnifying glass
Click the blue X
. The list is reduced to show only groups that match your search string.
in the search box to cancel the search and restore the full list of groups.
4. Click Delete Group in the lower right corner of the screen, then click Yes to confirm the removal.
The selected system group disappears from the list.
7.2.3
Modifying System Groups
Change the name, owner, or description of a system group, or add or remove systems.
Procedure
3. Select a system group to modify.
If the list of groups is long, use the Search box to find the group you want. Enter a full or partial name and
click the magnifying glass
Click the blue X
. The list is reduced to show only groups that match your search string.
in the search box to cancel the search and restore the full list of groups.
4. Change the system group's name or description and click Save Changes.
5. To add registered systems to the group, click Add System.
6. In the dialog, select systems to add and click Add.
7. To remove a system from the group, click the red X

System Directory
at the end of its row.
PUBLIC
61
Alert Monitor
Open the alert monitor and investigate alert messages.
Context
Tip
The Launch Alert Monitor tile tells you how many total high priority (HP) and medium priority (MP) alerts
have been reported, and how many of each.
Procedure
1. On the launchpad, click Launch Alert Monitor.
On the Alert Monitor screen, you see a list of systems on the left that shows how many alerts each one
has.
2. Click a system to display more information.
If the list of systems is long, use these tools provided in the dialog to search, filter, or sort the list.
Table 8:
Search
magnifying glass
string.
Click the X
Ok.
62
PUBLIC

Alert Monitor
List systems in ascending or descending (the default) order
Sort by weighted count of active alerts (the default), system name, system host ID,
or system type
If the monitored system supports drilling down into alerts, you can click the listed alerts to display further
details.

Alert Monitor
PUBLIC
63
Enterprise Health Monitor
Check the status of systems known to SAP DB Control Center.
Context
Tip
The Monitor Enterprise Health tile tells you how many systems are running.
Procedure
1. On the launchpad, click Monitor Enterprise Health.
The health monitor displays a list of systems with health indicators for availability, capacity, performance,
and alerts.
2. Hover your mouse over a health indicator icon (an arrow, for example) to see an explanation of what it
means.
3. Click in the System, Availability, Capacity, Performance, or Alerts column for a system to display
information provided by the system's cockpit. The links available vary; some systems do not provide links
for every column.
You may be prompted to log in to the system.
4. If the list of systems is long, use these tools provided in the dialog to search, filter, or sort the list.
Table 9:
Search
magnifying glass
string.
Click the X
64
PUBLIC

Ok.
Filter by priority
You can filter the list by priority, displaying only systems with high priority issues, or me
dium priority issues, or low priority issues. The filter displays systems with availability is
sues first, then those with performance issues, then capacity issues. At the top of the
screen, click the filter
click Ok.
. Select Priority, then select the priority you want to display and
Sort by system name (the default), connection, system type, or alerts
Connecting to a Cockpit [page 65]

Log in to a cockpit (management console) to get more information about the availability, capacity,
performance, and alert status of the system managed by the cockpit.
9.1
Connecting to a Cockpit
Log in to a cockpit (management console) to get more information about the availability, capacity,
performance, and alert status of the system managed by the cockpit.
Prerequisites
Add a system [page 54] to SAP DB Control Center.
Obtain a login ID and password for a database on the system managed by the cockpit. These credentials
will allow you to log in to the cockpit.
Procedure
1. In the Enterprise Health Monitor, click a system name to drill down into that system's cockpit.

PUBLIC
65
If the list of systems in the Enterprise Health Monitor is long, use these tools to search, filter, or sort the
list.
Table 10:
Search
magnifying glass
string.
Click the X
Ok.
Filter by priority
You can filter the list by priority, displaying only systems with high priority issues, or me
dium priority issues, or low priority issues. The filter displays systems with availability is
sues first, then those with performance issues, then capacity issues. At the top of the
screen, click the filter
click Ok.
. Select Priority, then select the priority you want to display and
Sort by system name (the default), connection, system type, or alerts
2. Use your database credentials to log in to the cockpit.

3. To display the cockpit documentation, click an appropriate tile on the cockpit's launchpad. (For example,
SAP HANA Administration Guide.)
If there are no tiles on the cockpit's launchpad, use the Tile Catalog to add any tiles you want to use to the
My Home group.
Task overview: Enterprise Health Monitor [page 64]
66
PUBLIC

10 Starting and Stopping a System
Start or stop a system managed by SAP DB Control Center.
Context
SAP DCC starts and stops systems using the SAP host agent, which is included in a typical installation. If the
agent is missing, you cannot start or stop the system from SAP DCC.
Tip
If collections are running and status data is available, the Start & Stop Systems tile tells you if any systems
are stopped. (To check for status data, click Monitor Enterprise Health on the launchpad. If you see question
marks in place of meaningful status displays, the Start & Stop Systems tile cannot provide a stopped
systems count.)
Procedure
1. On the launchpad, click Start & Stop Systems.
On the Start & Stop Systems screen, you see a list of systems that shows the state of each one (running,
shutting down, stopped, or unknown).
2. If the list is long, focus on systems of interest by clicking Running Systems or Stopped Systems at the top
of the screen, or use the search and filter tools.
Table 11:
Search
magnifying glass
string.
Click the X
Ok.

Starting and Stopping a System
PUBLIC
67
Sort by system name (the default), connection, system type, authentication, or

state
3. Authenticate with a system before you try to start or stop it. Click the system's checkbox and click
Authenticate (lower right corner of the screen).
4. (Optional) Click a system name to drill down into that cockpit for more information.
5. To start a stopped system, click its checkbox and click Start (lower right corner of the screen).
After a minute or so, the state of the system changes to RUNNING.
6. To stop a running system, click its checkbox and click Stop (lower right corner of the screen). Click Yes to
confirm.
The state of the system changes to SHUTTING DOWN and after half a minute or so to STOPPED.
68
PUBLIC

Starting and Stopping a System
Important Disclaimer for Features in SAP

HANA Platform and Options
SAP HANA server software and tools can be used for several SAP HANA platform and options scenarios,
based on the available SAP HANA licenses and the SAP HANA landscape. Which features and tools are
available depends on the type and version of the backend systems the SAP HANA administration and
development tools are connected to. For more information, see also SAP Note 2164095 . There are several
types of licenses available for SAP HANA. Depending on the license type of your SAP HANA installation, some
of the features and tools that are described in the SAP HANA platform documentation may only be available
via the SAP HANA options, which may be released independently of an SAP HANA Platform Support Package
Stack (SPS). Although various features included in SAP HANA options are cited in the SAP HANA platform
documentation, customers who only purchased the license for the base edition of the SAP HANA platform do
not have the right to use features included in SAP HANA options, because these features are not included in
the license of the base edition of the SAP HANA platform. For customers to whom these license restrictions
apply, the use of features included in SAP HANA options in a production system requires purchasing the
corresponding software license(s) from SAP. The documentation for the SAP HANA optional components is
available in SAP Help Portal at http://help.sap.com/hana_options. For more information, see also SAP Note
2091815 - SAP HANA Options . If you have additional questions about what your particular license provides,
or wish to discuss licensing features available in SAP HANA options, please contact your SAP account team
representative.

Important Disclaimer for Features in SAP HANA Platform and Options
PUBLIC
69
Important Disclaimers and Legal Information
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Accessibility
The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be
a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however,
does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of
SAP.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as
"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun
does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does
not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any
damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for
transparency (see: http://help.sap.com/disclaimer).
70
PUBLIC


PUBLIC
71
www.sap.com/contactsap

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company. The information contained herein may
be changed without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP or SAP affiliate company products and services
are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

Control Center Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Control Center Guide

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP HANA Platform SPS 10 DSP

SAP DB Control Center 4 Guide

About SAP DB Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installation and Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Upgrading SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Downloading the SAP DCC Delivery Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Adding the SAP DB Control Center System to SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing the SAP DCC Delivery Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Uninstalling SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Tutorial: Migrating SAP DB Control Center to a Tenant Database. . . . . . . . . . . . . . . . . . . . . . . . . . .13

Configuration: SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Setting up SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Setting up the System Configuration Login Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Setting up Administrator Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Setting up the Collector Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Setting up User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Updating Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Configuring SAP HANA XS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configuring with SQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuration: Monitored Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Setting up the Technical User Account on Monitored Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Accessing SAP DCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Adding Launchpad Tiles and Tile Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Moving and Removing Launchpad Tiles and Tile Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

SAP DB Control Center 4 Guide

Add and Remove Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Add, Remove, and Modify System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Enterprise Health Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Starting and Stopping a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

SAP DB Control Center 4 Guide

About SAP DB Control Center

SAP DB Control Center 4 Guide

Installation and Upgrade

1. Before Installing [page 5]

SAP DB Control Center 4 Guide

SAP HANA Master Guide, installation

SAP HANA Server Installation and Update PDF

Download the HANA

Covered in this document

Downloading the SAP DCC Delivery Unit [page 8]

Install the HANA

There are three ways to install the DU:

Complete Adding the SAP DB Control Center System

Use SAP HANA studio. This method

Use the SAP HANA command-line

In the SAP HANA Administration Guide, see Installing

Use the SAP HANA Application Life PDF

Configure SAP DCC

Covered in this document

Start with Adding the SAP DB Control Center System

Parent topic: Installation and Upgrade [page 5]

SAP DB Control Center 4 Guide

Upgrading SAP DCC

Follow these steps to upgrade SAP DB Control Center to SPS 10.

SAP DB Control Center 4 Guide

Table 2: Configuration Checklist

Task overview: Installation and Upgrade [page 5]

Downloading the SAP DCC Delivery Unit

Support Packages and Patches

3. Click H and select

SAP HANA Platform Edition

SAP HANA PLATFORM EDIT. 1.0

(near top of screen).