In the first part of this series I discussed, how to configure a database connection to a MaxDB database instance from a SAP system (Solman 7.1 in our case) running on a non MaxDB database instance for the purpose of configuring DBACOCKPIT with MaxDB as the remote database instance to be managed.
Part-I talked about how to setup this connection manually once we have installed and configured MaxDB client libraries as well as MaxDB database library.
In this part, I will describe how to setup complete Technical Monitoring integration of MaxDB database in to Solman MAI , how to register the instance with SLD and configure Dbacockpit database connection through automated Managed system setup in Solman 7.1.
A valid MaxDB client and database library is required in this case as well and should be installed in same way as described in the first part of this series.
We will also be able to monitor the availability, backup status, log backup status and other KPIs for a MaxDB database through Solman
If your MaxDB is running standalone or as a database for content server , livecache or a SAP system , we first have to install a SAP diagnostic agent and a SAP hostagent on the server running the MaxDB database and register it with the SLD of solman or a central SLD.
SAP Host Agent is installed automatically during the installation of new SAP instances with SAP kernel 7.20 or higher.
How to install and configure diagnostics agent and connect it to SLD of the solution manager system and the per-requisites are described clearly here.
Once the diagnostics agent has been successfully installed and configured, for sap hostagent to successfully discover the maxdb instance and collect data related to MaxDB instance monitoring and administration, we have to configure a XUSER for the user running the diagnostic agent(smdadm) and the host agent( runs with root and sapadm user on unix)
To know more about xuser concept, check XUSER – SAP Documentation
Create xuser with keys c, c_J2EE and <SID>. ( SID of Maxdb instance).
xuser -u control,”passwd” -d <SID> -n hostname -U <key>
You need to logon with the corresponding OS user and then run the command to create a key for the logged on OS user.( xuser utility is located in /sapdb/programs/bin ). Do this for the root and smdadm user.
Once this is done, the database instance should be visible in LMDB after sometime.
Now , we are ready to do the managed system setup for the Maxdb database instance in solman Technical monitoring setup.
Check the document (page 73) on how to perform managed system setup https://websmp202.sap-ag.de/~sapidb/011000358700000482292011E
In the 2nd step provide values as below and save.DBA cockpit connection should be successfully created. Otherwise check the maxdb client and database library configuration.
After completing the managed system setup. We have to apply a technical monitoring database template of Maxdb type. ( create a new template copying from the standard). We can change threshold values in the template metrics.( like for backups, database check).
Once the template has been created and assigned to the managed object of type maxdb database. we are now ready to monitor the remote MaxDB database in Solution Manger 7.1.
Below metrics are available to be monitored and alerts can be generated in case of errors ( Email notifications, SNMP traps)
Now that we have seen and learnt how to setup Solution Manager monitoring and DBACOCKPIT for a MaxDB database , in the next part of this series, I will discuss on how to setup MaxDB database backups , create backup templates, backup mediums and a DBA planning calendar centrally in Solman which can be easily maintained and monitored as for any other database like oracle