Professional Documents
Culture Documents
4 Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.1 Adding Launchpad Tiles and Tile Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2 Moving and Removing Launchpad Tiles and Tile Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5 System Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1 Add and Remove Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
5.1.1 Adding a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.2 Creating an Import File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.3 Importing Systems in Bulk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
5.1.4 Removing a System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2 Add, Remove, and Modify System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.2.1 Creating System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.2 Removing System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.3 Modifying System Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6 Alert Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7 Health Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.1 Connecting to a Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
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.
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.
1.1 Limitations
SAP DB Control Center does not support SAP HANA multitenant database containers.
Understand the installation process, decide how to install SAP DB Control Center, and read the relevant SAP
HANA documentation.
Download the HANA Covered in this document Downloading the HANA DBCC Delivery Unit
DBCC delivery unit [page 6]
Note
If you chose to install the HANA DBCC DU
using one of the SAP HANA lifecycle man
agement tools, skip Installing the HANA
DBCC Delivery Unit [page 7].
Get the SAP DB Control Center delivery unit from the SAP Software Download Center.
Procedure
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.
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 delivery unit.
Prerequisites
Procedure
Prerequisites
1. In SAP HANA studio, select File Import SAP HANA Content Delivery Unit and click Next.
2. Select the system to which you are importing the delivery unit and click Next.
3. Click the Client radio button.
4. Click Browse and navigate to the HANADBCC.tgz file you saved earlier.
5. Under Actions, select Overwrite inactive version and Activate objects. (They might be selected already.)
6. Click Finish.
In the Job Log view, notice that the import status changes to Running and then to Completed succesfully.
Procedure
1. In SAP HANA studio, select the system running SAP DCC, then select Configuration and Monitoring
Open Administration .
2. Click the Configuration tab.
3. Right-click xsengine.ini and select Add Section.
4. Enter the name scheduler and click Next.
5. Enter assign values to System and click Next.
6. Enter key enabled and value true.
7. Click Finish.
8. Right-click xsengine.ini and select Add Section again.
9. Enter the name httpserver and click Next.
10. Enter assign values to System and click Next.
11. Enter key sessiontimeout and a large value (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.
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 roles give 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.
Procedure
1. In SAP HANA studio, open the SYSTEM account (or another account with the same roles) under
Security Users .
2. Select the Granted Roles tab and click +.
3. Select each of these roles and click Ok:
sap.hana.dbcc.roles::DBCCAdmin
sap.hana.uis.db::SITE_DESIGNER
sap.hana.xs.admin.roles::HTTPDestAdministrator
sap.hana.xs.admin.roles::JobAdministrator
sap.hana.xs.admin.roles::RuntimeConfAdministrator
sap.hana.xs.admin.roles::SQLCCAdministrator
sap.hana.xs.admin.roles::TrustStoreAdministrator
4. Press F8 to deploy the role changes to SAP HANA.
Create a DCC_ADM user account and grant it administrative privileges, grant the privileges to an existing user,
or create one or more administrator accounts, according to your needs.
Context
Users with administrative roles can add, import, and delete systems. Set up at least one administrator
account.
1. In SAP HANA studio, right-click the Security Users folder and select New User.
2. 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 the configuration process.
3. Select the Granted Roles tab and click +.
4. Select each of these roles and click Ok:
sap.hana.admin.roles::Monitoring
sap.hana.dbcc.roles::DBCCAdmin
5. Press F8 to deploy the role changes to SAP HANA.
Next Steps
(Optional) Create additional administration accounts with the same roles as DCC_ADM.
Create a DCC_COLLECTOR user account and grant it monitoring and administration privileges.
Context
The DCC_COLLECTOR account runs collection jobs to gather the availability, performance, capacity, and
alerts data that SAP DB Control Center displays for each system it monitors.
Procedure
1. In SAP HANA studio, right-click the Security Users folder and select New User.
2. For the new user's name, enter DCC_COLLECTOR. Enter a temporary password such as AAA111aaa.
You will change the password later in the the configuration process.
3. Select the Granted Roles tab and click +.
4. Select each of these roles and click Ok:
sap.hana.admin.roles::Monitoring
sap.hana.dbcc.roles::DBCCAdmin
5. Press F8 to deploy the role changes to SAP HANA.
(Optional) Create an account for general users, DCC_USR, and grant it monitoring and user privileges. Create
more user accounts if you need them.
Procedure
1. In SAP HANA studio, right-click the Security Users folder and select New User.
2. For the new user's name, enter DCC_USR. Enter a temporary password such as AAA111aaa.
You will change the password later in the the configuration process.
3. Select the Granted Roles tab and click +.
4. Select each of these roles and click Ok:
sap.hana.admin.roles::Monitoring
sap.hana.dbcc.roles::DBCCUser
5. Press F8 to deploy the role changes to SAP HANA.
Next Steps
(Optional) Create additional user accounts with the same roles as DCC_USR.
Assign UIS catalogs and groups to the SAP DB Control Center DBCC_USER role to enable interaction with SAP
HANA Cockpit.
Prerequisites
To access the role editor, you must log in using the SYSTEM account or an account with the same roles and
privileges. (If you are not logged in, SAP HANA prompts you to do so.)
Procedure
where the value of <port> depends on the connection protocol and the 2-digit SAP HANA instance
number:
For example, use port 8000 for an HTTP connection to instance 00. Use port 4301 for an HTTPS
connection to instance 01.
2. Select sap.hana.dbcc.roles::DBCCUser.
3. Select the Catalogs tab and click +.
4. Select SAP DB CC from the list.
5. Click Ok.
6. Select the Groups tab and click +.
7. Select SAP DB Control Center from the list.
8. Click Ok.
Context
Perform these steps for the new accounts you created, including:
If you created extra administrator or user accounts, update their passwords too.
Procedure
1. In SAP HANA studio, right-click the SAP DCC host 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. 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.
Repeat the steps for all the accounts you want to update.
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.
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.
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, right-click the Security Users folder and select New User.
2. For the new user's name, enter SAPDBCC. Enter a temporary password such as AAA111aaa.
3. Select the Granted Roles tab and click +.
4. Select the sap.hana.admin.roles::Monitoring role and click Ok.
5. Press F8 to deploy the role changes to SAP HANA.
6. To update the temporary password:
a. Right-click the SAP HANA system and select Add system with different user.
where the value of <port> depends on the connection protocol and the 2-digit SAP HANA instance
number:
For example, use port 8000 for an HTTP connection to instance 00. Use port 4301 for an HTTPS
connection to instance 01.
8. Log in using SYSTEM or an equivalent account.
9. In the left pane, click XS Artifact Administration.
10. Click the arrows to expand sap hana admin dbcc .
11. Click dbccuser.xssqlcc.
12. Set the user to SAPDBCC and enter the new SAPDBCC password (step 6.c [page 14]).
13. Click Save.
Look for a message at the bottom of the screen: SQLCC values successfully saved.
Next Steps
In SAP HANA Extended Application Services (SAP HANA XS), set up a trust store and configure data
collections and message queue maintenance.
Prerequisites
The SYSTEM account or an account with the same roles and privileges
DCC_COLLECTOR
Context
For more on SAP HANA XS and SQLCC, see the SAP HANA Administration Guide.
where the value of <port> depends on the connection protocol and the 2-digit SAP HANA instance
number:
For example, use port 8000 for an HTTP connection to instance 00. Use port 4301 for an HTTPS
connection to instance 01.
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 sap hana dbcc and select services.
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 DCC_COLLECTOR and enter the DCC_COLLECTOR password.
f. Select the Active check box.
g. Click Save Job.
Look for a message at the bottom of the screen: Job successfully saved.
5. To enable maintenance, which cleans up the message queue:
a. In the left pane, click XS Artifact Administration.
b. Click the arrows to navigate to sap hana dbcc maintenance .
c. Click Maintenance.xsjob.
d. Set the user to DCC_COLLECTOR and enter the DCC_COLLECTOR password.
e. Select the Active check box.
f. Click Save Job.
Look for a message at the bottom of the screen: Job successfully saved.
Prerequisites
Procedure
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 . Follow its link to the latest SAPUI5 documentation and look
up the sap.m library.
Options menu Log out or display information about this login session. The drop-down dis
plays the name of the logged-in user.
Show/hide tile groups icon Open the tile groups panel, where you can add tiles to the launchpad, re
move them, or rearrange them. You can also create and remove tile
groups. (Every tile belongs to a tile group.)
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.
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 24].
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 (upper left) to return to the launchpad and see the new tiles and tile groups you
added.
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.
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 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 9].
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 13].
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.
SAP DCC needs HTTP access to run an initial system scan. All subsequent interactions are authenticated and
occur over HTTPS.
Procedure
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 13].
Context
The import file must contain one line per system. On each line, include this information in this order, separated
by commas:
For example:
#Systems in Bedrock
myserver.mycompany.com,8000,hana1,basic
Be sure to press Enter after the last line of your import file.
Procedure
1. Create an import file in the comma-separated value (CSV) format described above.
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 include all the login credentials in the import file.
Next Steps
Use the import file to add systems to SAP DCC. [page 22]
Add two or more systems to SAP DB Control Center so you can monitor and manage them.
Prerequisites
Note
When you omit login information from the import file, ensure that all the systems you selected for
import use the same login ID and password. (Perform a separate import for each group of systems that
share login credentials.)
Results
Procedure
If the list of systems is long, use these tools provided in the dialog to search, filter, or sort the list.
and click the magnifying glass . The list is reduced to show only systems
that match your search string.
The search box accepts certain regular expressions. For details, see http://
www.w3schools.com/jsref/jsref_obj_regexp.asp .
Click the X in the search box to cancel the search and restore the full list of
systems.
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 . Select System Group, then select
the groups you want to display and click Ok.
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 sys
tems). At the top of the screen, click the filter . Select Type, then select the
system types you want to display and click Ok.
Change sorting rules You can modify the sorting rules to:
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.
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.
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 20] or import several systems together [page 22].
Note
System groups are different from tile groups. For information on tile groups, see Adding Launchpad Tiles
and Tile Groups [page 18].
Procedure
Context
Deleting a system group does not delete the systems that belong to the group.
Procedure
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 . The list is reduced to show only groups that match your search string.
Click the blue X 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.
Change the name, owner, or description of a system group, or add or remove systems.
Procedure
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 . The list is reduced to show only groups that match your search string.
Click the blue X 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 at the end of its row.
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
Context
Tip
The Monitor Enterprise Health tile tells you how many systems are running.
Procedure
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
1. In the Enterprise Health Monitor, click a system name to drill down into that system's cockpit.
If the list of systems is long, use these tools provided in the dialog to search, filter, or sort the list.
Search Enter a full or partial system name in the search box at the top of the screen
and click the magnifying glass . The list is reduced to show only systems
that match your search string.
The search box accepts certain regular expressions. For details, see http://
www.w3schools.com/jsref/jsref_obj_regexp.asp .
Click the X in the search box to cancel the search and restore the full list of
systems.
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 . Select System Group, then select
the groups you want to display and click Ok.
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 sys
tems). At the top of the screen, click the filter . Select Type, then select the
system types you want to display and click Ok.
Change sorting rules You can modify the sorting rules to:
At the top of the screen, click the Sort icon , choose sorting rules, and click
Ok.
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
The Start & Stop Systems tile tells you if any systems are stopped.
Procedure
Search Enter a full or partial system name in the search box at the top of the screen
and click the magnifying glass . The list is reduced to show only systems
that match your search string.
The search box accepts certain regular expressions. For details, see http://
www.w3schools.com/jsref/jsref_obj_regexp.asp .
Click the X in the search box to cancel the search and restore the full list of
systems.
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 . Select System Group, then select
the groups you want to display and click Ok.
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 sys
tems). At the top of the screen, click the filter . Select Type, then select the
system types you want to display and click Ok.
At the top of the screen, click the Sort icon , choose sorting rules, and click
Ok.
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.
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).