Over the past six months we have been hard at work designing and developing a brand new supportability platform for SAP BusinessObjects BI Platform. This product is the SAP BI Platform Support Tool version 2.0 which is an evolution and follow up of the original BI Platform Support Tool version 1. Over 2014, we collected feedback from engineers, developers, and customers and implemented as much as possible into the new platform. I believe with the new version, we will significantly reduce the number of incidents needed, reduce the amount of work for the BI administrator, and considerably reduce the time it takes to resolve support incidents raised to SAP support.
In this article, I will share the release schedule and provide details on all of the confirmed features coming soon in the version 2.0 release.
BI Support Dashboard
The home view now in version 2.0 is a BI supportability dashboard that brings together all of the resources that a BI administrator needs to support their BI Platform environments. It is essentially a browser that displays useful SCN RSS feeds, hyperlinks to important maintenance, patching, and documentation, as well as a knowledge base search feature that searches KB Articles, SAP Notes, BOB Forum, and Google Search all simultaneously from a single query. Once you have logged on using your S-USER account, the S-USER SSO certificate is stored within the BI Platform Support Tool client providing you a quick way to access important support content.
Landscape Analysis Report
One of the primary features of the product is the Landscape Analysis Report. The Landscape Analysis Report is the name given to a collection of one or more analysis reports containing information about the BI Platform landscape. The user can select which types of analysis should be included in the Landscape Analysis Report depending on the type of information that is needed for a particular service or root cause analysis task.
The criteria for including data in the Landscape Analysis Report are:
- Data for an analysis type can be collected in less than 10 minutes
- Information is useful to be reviewed on a re-occurring basis
- Data can be collected without introducing a large performance hit on the target system
- Change Analysis and Alerting can be applied to the collected data
The generation of a Landscape Analysis Report occurs in two separate phases, Extraction phase, and Report Generation phase. This separation makes it such that historical report instances can be opened and saved data can be analyzed or compared separately from the actual data extraction. As a result, it is possible for offline analysis to occur by SAP support or other consulting organizations that cannot connect directly to the live customer system.
We have implemented the same charting engine as used by other SAP BusinessObjects Analytics products such as Lumira and Design Studio. The CVOM charting engine allows us to visualize more of the system metrics and properties making analysis quicker and more intuitive.
New Analysis Types
In version 2.0, we have both added new types of analysis and improved the functionality of the existing analysis that existed in version 1.x. Refer to the table below for a list of the analysis types and information about that analysis.
|Analysis Type||Description||Data Source|
|Server and Services||Information about BI server configuration, settings, and metrics. The configuration is also displayed in a side by side comparison report for quickly spotting differences in server settings or command line properties|
|Content||Displays information regarding the count of Info Objects in the system. This is useful for understanding which products are in use and how large the InfoStore repository is||InfoStore|
|Schedule||Pulls back scheduled instances and does analysis on why reports are failing, which instances are taking up most disk space, most common error messages for failed instances, and longest running instances. You can also now add a date filter to view only the instances you need to analyze||InfoStore|
|License Key||Analyzes the current keycodes in use and gives alerts if the keycode will expire soon or if there is missing functionality||InfoStore|
|Platform Search||Confirms that best practices are being followed concerning the Platform Search feature. This is a common reason for performance degradation if not optimally configured||InfoStore|
|Hardware Summary||Invokes the SAP Host Agent and returns information about the host and operating system for each node in the BI landscape||SAP Host Agent|
|Authentication||Displays information about the third party authentication setup and single sign on||InfoStore|
|Semantic||Shows which Universes and Connections are being used the most. Displays how many reports will be affected by changes to these semantic layer objects (UNX, UNV). Checks for orphaned Webi documents (those without a linked universe)||InfoStore|
|Web Application Server||Connects to the Java Application Server and shows information and metrics about the Java Virtual Machine as well as the application server settings and configuration||JMX|
|Patch History||Collects from each BI node the installation and patch history. This is useful to see which patches have been applied, what order they were applied, who installed the patch, was it an install, uninstall, repair, etc||SAP Host Agent|
New Custom Alerting Framework
One limitation of the previous version is that all the alerts and thresholds were static and configured at development time. In version 2.0, we have made a new extensible alert framework that allows the expansion and customization of the metrics and settings that are evaluated. Additionally, the threshold values and logic used to trigger the alerts can also be customized to better align with the needs of a particular organization or environment.
The alerts themselves are evaluated during the extraction phase so that the triggered alerts are stored within landscape xml itself. This way, if you are reporting on the landscape xml outside of the SAP BI Platform Support Tool or if you are sending the landscape xml to SAP for analysis, the alerts that were triggered at extraction time will always be able to be recalled and viewed in a historical manner.
There is some new alert terminology to be aware of in the 2.0 platform.
Simple Alerts – Allow user customization, changes to thresholds, delete or add new metrics. Simple alerts are limited to evaluation of one metric/setting and one logic operator
System Alerts – These are system defined alerts which allow for more advanced logic and analysis. System alerts include things such as keycodes expiring in the next 30, 60, or 90 days, nodes not at the same install patch level, or nodes not running the same support pack
Complex Alerts – Complex alerts are alerts which allow you to combine the results of two or more alerts and allow the use of AND and OR logic to determine the alert state. Complex Alerts are not available yet in version 2.0 and are scheduled to be implemented in the next version (version 2.1)
Alert Definitions – Alerts are configured via the preferences UI and are stored in the file alerts.xml under the BI Platform Support Tool /resources/Alerting directory
Alert Summary Tab
Any simple or system alerts triggered in the Landscape Analysis will appear on the Alert Summary Tab. This makes it possible to quickly review which alerts were triggered in a particular analysis so that actions may be taken where necessary. The Alert Summary tab also contains information such as the user who ran the Landscape Analysis, how long the processing took, and what version of the SAP BI Platform Support Tool was used to generate the analysis.
Improved E2E Trace Wizard
One of the most common activities required for root cause analysis of a BI landscape is to generate an End to End Trace. Using the included SAP Client Plug-in, each request sent from the BI client contains an SAP Passport which is intercepted by the application server and passed along to the backend processing servers and databases. This feature automates this process by automatically configuring the BO_trace.ini on each BI node, recording a video capture of the trace session, and collecting the log files from each host in the landscape for the user.
The E2E Trace Wizard relies on the existing Landscape Definition to understand which BI nodes and Application Server nodes are defined for the target landscape. For each BI node and Application Server node, the user has a choice of whether they want to use the SAP Host Agent or UNC Shared Directories to collect log files from the remote hosts. This allows flexibility for cases where the customer cannot run a SAP Host Agent or share network folders on a particular node type. After the logs are collected, the content is zipped up and stored in the E2E working directory of the BI Platform Support Tool user directory. The user may then forward this required tracing information and video capture to SAP for quick problem resolution or code correction. Once the trace session is complete, the E2E Trace Wizard will revert the BO_trace.ini back to default settings on each node in the landscape.
Change Analysis 2.0
A useful technique in troubleshooting the SAP BI Platform is to understand what changes have been made in the BI system as some changes may lead to performance problems and/or system crashes. The Change Analysis feature builds on the existing Landscape Analysis Report feature and allows the end user to select two or more Landscape Analysis Report Instances for comparison.
When compared, each data landscape XML is loaded into memory of the BI Platform Support Tool. Each property name, property value pair is compared using a comparator and when differences are found, the differences are displayed in the client in columnar format. Values determined to be different are highlighted in yellow for quick and easy identification. Although useful for identifying changes to the system, the Change Analysis tool can also be used to view a change in performance metrics over a period time (for example, Memory Usage on Saturday each week).
3rd Party Authentication Wizards
The procedure for setting up third party authentication and single sign on (SSO) tends to generate a lot of incidents and can be a fairly complex set of procedures. This process requires the administrator to read the manual and follow instructions very closely for success. Additionally, differences in environments can make understanding the setup guide a bit difficult since it is not tailored for their particular landscape. This is where the Authentication Wizard comes in. This wizard guides the BI administrator through every step of the process while customizing the setup depending on their own domain, LDAP, or SAP environment. Furthermore, it even authors emails for the BI administrator to send to their domain administrators with instructions on the steps that need to be taken on the domain controller, BW system, LDAP server, etc. This wizard is truly like having SAP Support helping you without ever needing to create an incident.
The new Landscape Tools section contains a number of Diagnostic Tools which are mostly used by SAP Support for specific troubleshooting tasks. This area is mainly for smaller applications that do not fit the criteria required for the Landscape Analysis Report. Applications in this area are usually tools that have existed in support in the form of JSP pages or smaller Java console applications. Refer to the table below for details on the included tools:
Publish Landscape to SAP (Reverse 911 Alerting)
Predictive Maintenance is a big initiative here at SAP Active Global Support and to help facilitate a more pro-active support service, we have built into version 2.0 the ability to safely and securely publish your Landscape Analysis Report directly to SAP. If you choose to participate, your landscape XML is consumed on an internal SAP HANA system where a variety of analytics can automatically check for problems such as:
- Landscapes not following best practice or not within PAM recommendations
- Systems where tracing was accidentally not disabled
- Systems that may be vulnerable to a new security vulnerability that was discovered
- Systems that may contain a setting that was recently discovered to introduce a problem
- Landscapes running a patch or SP that may contain a regression
The goal of this functionality is to identify problems before they occur and pro-actively reach out via email to those customers and administrators who may be affected by the problem or situation.