In my DB Performance Tuning: What is on Your Top 5 List?, I wrote about some of the tools for determining what your database tuning priorities are. Some have mentioned to me that, with SAP Netweaver Java applications, they feel left out in the cold due to the fact that many of these advanced tools don’t exist in the Java toolbox, or that they’re simply used to the ABAP transactions and don’t like the “feel” of the Java ones.
Well, never fear, there is a way to access these ABAP tools to use them on your Java systems as well, even if they are standalone Java instances (not dual-stacks). To do this, the easiest way is to ensure that your SLD is set up properly, which I won’t cover in this blog. You can do it manually as well, but the SLD import is the most reliable method. I will not cover SLD setup, but I will cover SLD import, as well as adding systems manually.
I am going to show my example from my Solution Manager system, as that’s the system that makes most sense here for a few reasons. First, Solution Manager is, in SAP’s model, the one system to manage them all, to butcher a phrase. (I’m sure all the geeks get the reference 🙂 Second, in my environment, Solution Manager is the master SLD, so it naturally makes sense to use it for a purpose that depends on the SLD.
So, as always, my example is referencing systems running on DB2 LUW 9.1. I am sure that similar methods exist for other databases, but I don’t have SAP systems running on other databases to show you screenshots of. Sorry, I wish I could help there.
The first step in this process is to go to the DBA Cockpit (transaction code: DBACOCKPIT).
Next, you’ll want to click on the SLD System Import button to add systems to the DBA Cockpit.
If you wish to manually add systems, you can click on DB Connections
then click Add to do it manually (adding entries to the DBCON table)
After you have imported or manually added your systems, you should be able to click on the currently selected system to get a drop-down of additional systems, both ABAP and Java, to manage.
In this case, I am selecting a Java-only Enterprise Portal system. Once I do this, I will be able to use the standard SAP DBA Cockpit in ABAP to manage the database for my Java application.
So now you should be able to log on to a single tool to be able to view all of your database metrics, and achieve the goal of having one tool to manage them all, and in the data center bind them. 🙂