1772632 - Explanation of Server Monitoring Metrics for SAP BusinessObjects Business Intelligence 4.0. A complete guide to setup CA APM Introscope 9 f. The procedure to setup CA APM Introscope 9 (formerly known as Wily Introscope) for SAP BI Platform 4.1 has got a bit easier however, the documentation is still spread out across several locations.
In this article, I will give you a complete step by step example on how to get started monitoring your BI landscape using CA APM Introscope 9. In this example, I have one host which will run the Introscope Enterprise Manager and another host where I am running SAP BI Platform 4.1 SP2 + default Apache Tomcat deployment. Here is the workflow we will follow: Step 1: Download the installation media from the Software Download CentreStep 2: Install the Introscope Enterprise ManagerStep 3: Install the Diagnostic Agent on each BI node and application server nodeStep 4: Configure each BI node and application server nodeStep 5: Validate the installation/configuration is working Step 1: Download the installation media from the Software Download Centre. Developing and deploying a custom Java probe in. In this SCN document I'll demonstrate how to develop your own custom Java probe and successfully register it with your SAP Business Intelligence Platform 4.0.
Included in this tutorial is a basic sample which you can use as a starting point for your own custom probe development. The sample in this tutorial takes as input parameters a host name and port number of a web server. Upon execution the probe will attempt to make a socket connection to the host on the specific port and if successful the probe will return a success (in the language of BI4 watches, this is represented as a value of 1). If the socket connection fails, the probe will return a failure (a value of 0). Considerations before you get started For large productive landscapes it's recommended that you upgrade your BI Platform to SP4 Patch 12, SP6 Patch 1, or SP7. Health Probe, Diagnostic Probe, or Hybrid Probe A health probe generates metrics of data types such as integer, Boolean, or string. Source code walk-through try. Remote Supportability and Monitoring Tools: Fiv.
The BI Platform 4.x monitoring application has undergone significant improvements since the 4.0 release.
In this SCN blog series, I'll outline some important fixes, tips, tricks, and documentation regarding the BI Monitoring application that every BI administrator should be made aware of. The goal of this series is for you to get the most out of the native BI monitoring application so that you may keep your BI landscape as stable and efficient as possible. False Alerts When using probes and alerts to programmatically re-create user workflows and confirm the availability of various aspects of your BI landscape, you may find that you are getting alerts in your email or BI inbox that have already been triggered in the past.
This can be particularly annoying since you depend on these alerts to inform you of any system outages. BI Platform Support Tool. E2E Trace Wizard The E2E Trace Wizard simplifies the process of executing and collecting E2E traces in SAP BI Platform 4.x.
In landscapes where there are multiple SIA nodes and application server nodes, the collection of logs from each server can be a very time consuming and tedious task. Additionally, before each trace session the global BO_trace.ini on each SIA node must be updated manually otherwise the GLF logs will be overwritten and the E2E trace will be incomplete. When the trace session is complete, then you must revert each global BO_trace.ini back to the original settings again to prevent too many logs from being generated. The E2E Trace Wizard addresses these issues by automating the setting of BO_trace.ini on each node and automatically collecting / zipping the necessary logs from each node in the landscape.
SAP Passport Decoder The SAP Passport technology is used to generate E2E traces for all SAP products. Remote Supportability and Monitoring Tools: Sol. I look into the differences between these two solutions to explain which one would be best for the various SAP BusinessObjects Enterprise XI 3.1 landscapes.
Every SAP BusinessObjects installation should have a system monitoring and analysis solution. I will endeavor to cover the differences and which solution fits the landscape better. Let’s first start off with a direct comparison this chart covers when it is most appropriate to install each solution based upon the specific situation. Not all environments are created equal thus there are two solutions to choose from that provide a broad offering of solutions. Remote support component strictly supports SAP BusinessObjects Enterprise 3.1 SP2 and higher.
Many ecosystems may have a Solution Manager installation somewhere, however the Business Intelligence teams are unable to connect the SAP BusinessObjects Enterprise system to this Solution Manager due to resource constraints. Solution Manager 7.0 EHP 1: Note 1010428 End-to-End Diagnostics.