Just because it's analytical and not transactional doesn't mean it's not a core part of service delivery.
As a leading Business Intelligence and analytic platform SAP BusinesObjects (BOBJ or BO) needs to deliver business performance metrics to business users to help them make informed decisions that directly impacts revenue. So if BO is slow or unavailable, then "ITOBjects" (pun intended) failed at delivering that service to the business. It is core and it is mission-critical, therefore it must perform.
See our updated content BusinessObjects Monitoring is Tricky but These Resources Should Help
One of our customers recently deployed SAP BW on HANA with SAP BusinessObjects 4.1 as the reporting front-end. Both HANA and BO are new to them, so they were unsure how to best tackle the performance management of the environment. We proceeded based on our SAP Performance Management Best Practices and a summary of our approach for BO is described in this publication, including the 3 major areas of performance assurance: Sizing/Design, Testing/Optimization, and Monitoring/Management. We were able to quickly identify key components, test scenarios, monitor and report key optimization recommendations.
A common SAP technology stack for Business Intelligence that we've come across in the field has been SAP Business Warehouse (BW) backend as the enterprise data warehouse platform, with a BusinessObjects (SAP BOBJ) Business Intelligence (BI) reporting application. Performance testing, monitoring and tuning in such environment requires the setup of tools that will monitor the BOBJ as well as the BW system. This has to be part of any performance and availability management project involving the environment described above. We previously covered the technical monitoring setup using SAP Solution Manager in SAP NW on HANA Monitoring Setup (Preparation, Managed System Configuration and Technical Monitoring). The next series of 3-parts blog we will detail the setup for SAP BOBJ Monitoring in Solman 7.1
This last part we will hook up the 2 components of a SAP BOBJ BI 4.0 environment to the SAP Solution Manager, using Managed System configuration and Technical Monitoring by assigning the products and logical components.
Continuing on after installing the SAP Diagnostics Agent on the BI 4.0 system, we will use the AC (Auto-Configure) tool to step through the setup of SAP BOBJ and its various components to enable their integration and instrumentation for monitoring SAP Business Intelligence including:
- Wily Introscope
- SAPOSCOL (SAP Operating System Collector)
- Tomcat web server