A Dashboard in Avantra is a page in the UI you can customize to your liking. It features the positioning of so called Dashlets in either a fixed or a floating grid layout.
Dashboards may be private to a User or shared between all Users of a given Customer. There is also an option to open a Dashboard outside of the UI by a direct URL.
An Oracle, DB2, MaxDB Database, a Microsoft SQL Server (also referred to as MSSQL server), an SAP ASE (formerly SAP Sybase ASE), an SAP SQL Anywhere Database, or SAP HANA Database. This can either be a stand-alone Database or a database instance of an SAP System‚ or a liveCache, etc.
A Database is hosted by exactly one Physical Server or Virtual Cluster Server, but multiple Databases can be hosted on the same server.
If you want to manage or monitor a Database you need manage or monitor the Physical Server or the Virtual Cluster Server the Database is hosted on.
From a license perspective, it depends if a Database is the primary Database of an SAP System or not. If yes, the license is included in the SAP System’s license. If not, a separate Database license is required.
The Avantra Agent needs the credentials of an SQL (!) Database User in order to connect to a stand-alone Database or the Database instance of an SAP System.
- Database instance of an SAP System
As a general rule, use the following Database users in order to monitor the Database instance of an SAP System:
ABAP-only SAP System
Use the SAP ABAP schema user (e.g. SAPSR3)
Java-only SAP System
Use the SAP Java schema user (e.g. SAPSR3DB)
Double-stack SAP System
Use both users
For an SAP System with MaxDB Database you also need a DBM Operator (e.g. the CONTROL user).
- Stand-alone Databases
As a general rule, use an administrative Database user for the Database monitoring.
The more detailed description is as follows (applies to Database instances of a SAP System as well if you do not use the schema users):
Please make sure the SQL user you use has the permission to access the Catalog Views in Oracle; at least the role SELECT_CATALOG_ROLE must be granted to the user, unless it is an Oracle administrator user. To do so, connect to your Oracle Database using SQLPlus and enter the following command:
SQL> GRANT CONNECT, SELECT_CATALOG_ROLE TO <sql-user>
Additionally, when using BR*Tools, the SQL user must be granted
SELECTprivileges to the
SDBAHtable in the corresponding SAP schema, unless you already use the SAP schema owner or an administrator user.
The same holds true for the table
BC_COMPVERSfound in the SAP schema of Java SAP Instances.
Please make sure your user is part of the
SYSMONauthority group or has system administration or system control authority. Please refer to your DB2 documentation on how to grant those authorities to your user.
- Microsoft SQL Server
Please make sure the user you use has assigned the login permission
VIEW SERVER STATE. See the Microsoft SQL Server documentation on how to assign the permission to your login user.
Avantra supports both, SQL Server authentication and Windows authentication. In case you choose a Windows authentication user, please define the user in domain format in the Avantra UI:
Please define a user in the DBA User Class. For a MaxDB Database you also need a DBM Operator (e.g. the
CONTROLuser usually is not able to run SQL commands!
- SAP HANA
Please make sure the user has assigned the role Monitoring. In case you run a Java SAP Instance on top of HANA the Database user also needs the following permissions:
GRANT SELECT ON TABLE [DBSCHEMA.]BC_COMPVERS TO [user]
- SAP ASE (formerly SAP Sybase ASE)
Please make sure the user has assigned the roles mon_role and oper_role.
For the SYB_Backup check, permission setting depends if granular permissions are enabled for the database or not.
With granular permissions enabled, the dump configuration privilege must be granted to the user.
With granular permissions disabled, according to official Sybase ASE documentation the role oper_role should be sufficient for the check SYB_Backup (all other checks only require mon_role permissions). Unfortunately tests have shown that the stored procedure called for SYB_Backup fails with permission error unless the user is a member of sa_role.
- SAP SQL Anywhere
Please make sure the user has assigned the system privileges to run the procedure
sa_disk_free_space. To do this, run the following grant statements:
GRANT EXECUTE ON sa_disk_free_space to [user] GRANT MANAGE ANY DBSPACE to [user] GRANT SELECT ON maint_plan to [user] GRANT SELECT ON maint_plan_report to [user]
Make sure to replace
[user]by the real user name.
In addition to RealTime Monitoring, Avantra also checks certain system conditions of an SAP System or a Database only once per day. Among these, there are e.g. Checks for a backup (which you usually perform once a day only) and others. We call these kind of Checks the Daily Checks. They are also referred to as Full Checks.
You may want to skip the execution of Daily Checks on the weekend using Monitoring Parameter RunDailyCheckOnWE.
You can also restrict the Daily Checks details to those parts that are relevant for you using the SAP System or Database Monitoring Parameter RelevantDailyCheckDetails.
A Dynamic Group is a way to implicitly define a group of Systems for use with Monitoring Parameter Sets, Custom Checks, and Maintenance Windows.
A Dynamic Group is defined by one or more System properties. Whenever a newly defined System has the defined properties, it is automatically included in the grouping. If the property of a System changes or the System is removed it is automatically removed from the grouping.
The most simple Dynamic Group is the one consisting of all Systems of a certain System Type.
So a Dynamic Group can be e.g.
all servers of a certain operating system type
all SAP Instances with a certain Release
all SAP Systems of a certain Customer with a Database of a certain type
all (stand-alone) Databases of a certain type
all productive systems having a SAP Instance running on a certain operating system
and many others more.
Dynamic Groups are implemented using Selectors.