New features coming soon in the SAP BI Platform Support Tool 2.0
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.
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.
Release Dates and Beta
The SAP BI Platform Support Tool 2.0 will be released for free as an official product on the SAP Store. Since it is an official product, we are subject to SAP Product Standards and as a result, the release has taken a bit longer than originally expected. Prior to release to customer, we will be having a beta release. We are in the final stages of the release process now and plan to release the beta in August 2015. Release to customer will follow in September / October time frame after the beta program wraps up.
Good work Toby. I will send an email to you to be part of Beta program.
Thank you Toby and team for this tool.
Will you be releasing a 2.0 command line version?
I'm running version 1.1.8 as a scheduled object via the CMC to monitor BO system changes. The actual analysis is still a manual process, I’m working to automate that and provide notification on change. I’m very anxious to see how 2.0 will help with an automated solution. Is that how Simple Alerts would be used, to monitor and alert on a particular metric from a job server (as an example)?
Looking forward to the 2.0 beta.
We had to push back the command-line version for the next release version 2.1. We do plan to improve the command line version by allowing the publishing/scheduling to happen directly from the BIPST client. This version is targeted for Q1 2016 but may happen sooner. In the meantime, we will keep version 1.1.9 command line version available for download.
Another improvement I can mention is that the data XML is formatted much better this time around and allows for easier consumption by the BOBJ Analytics tools.
Yes, simple alerts can be used to set a threshold value on a single server metric or configuration setting (property).
I am interested in participating the beta version as well.
One of the best thing that ever happened to SAP BI product, Awesome futures. Can't wait any longer to use this product. I used to wonder every time how to capture all the recurring instances and tried different macros from BOBJ forum, which doesn't get updated when their is a new version of BI released and it was most of the times don't work.
The other thing setting up 3rd party SSO is another awesome feature, which will save time for many.
I would also like to participate in 2.0 Beta.
Count me too Toby. I will send out a separate mail as well.
thanks for this greart article
How will this tool will be combined with the CMC ?
Brilliant Stuff. This is what separates an enterprise level product from a hobbyist product.
Have sent mail for the Beta Invite. Please count me in.
Eventually if you centralize all the system management aspects in one tool you can lift these product 3 or 4 steps ahead:
1. 1.Version control management
(Folder, Universe ,connection and report ,easy comparison and rollback)
2. 2.Hot and cold backup operations and maintenance (schedule, system recovery )
3. 3.Query online monitoring
4. 4.Customization ease of use implementation
The change analysis seems like a great feature
Good news ! Thanks Toby and others for this great tool we're using a lot !
I have been using the version 1 - and am excited to use the version 2. I am interested in the beta version. how can I participate?
I am also interested in participating in the beta program.
Sounds Amazing. Looking forward for the release. Thanks Toby!!
is this already released ?
I am looking forward to it.
Currently, we are in beta release. We plan to release to customer on Nov 6th. If your interesting in participating in the beta program shoot me an email with your S-USER and I can see about getting you added. firstname.lastname@example.org
Are there thoughts of implemening a way of showing Meta Data information ?
What specifically are you looking to see? You can access the raw data via the XML stored in the user's data folder (by default C:\Users\USERID\AppData\Roaming\BISupportTool\data)
The XML in version 2.0 is formatted much better for consumers such as Crystal Reports, Universe, etc so in a sense, you could build your own reports on top of the data we are collecting.
Apologies for my late response. I'm wondering how to get metadata information like which WebI report uses which Datasource, which dimensions/objects are used in that WebI report, stuff like that.
Yes, the Semantic Analysis provides the Universe to Report metadata
The Universe Analyzer feature does an integrity check for each Universe. It checks each object and validates the objects against the database and provides a report showing the results.
For granular object level metadata and impact analysis, the existing tool Metadata Manager provides this level of detail
THanks a lot for your swift response. My reports are based on bex queries.. I'm able to get THE bw metadata into a bex query. is iT possible that kind of data, with the metadata of BusinessObjects?
Yes, technically you could through the use of many InfoStore queries pull together a similar report to show which BEx queries are used by which Webi reports and vice versa. This is not possible yet in the BIPST but I have created a user story and we will consider to add this for a future version.
I'll have a go with that and stay tuned on your postings 🙂 Thanks !
For an enterprise that has a mature monitoring landscape, is there a way to send alerts to a central console via SNMP, email or other methods? That seems handier than having one more place to look for issues.
In the next version (version 2.1), you will be able to schedule the Landscape Analysis to an email (SMTP) destination, so in a way this will be possible. The report would come as an attachment and the alerts triggered would make up the contents of the email body. Would this meet your requirements?
As Perl programmers are wont to say, there's more than one way to do it. SNMP traps are the preferred method for alerts, though parsing email is possible. Thanks for responding, and nice to meet you in Austin!
Is your goal to integrate the BIPST alerts with another central monitoring tool like Introscope or Tivoli?
How would you be utilizing the SNMP traps? This is certainly something we could consider for the next version so the more info on this requirement the better. Feel free to email me your ideas email@example.com
We use EMC Smarts as our central console; previously we used BMC Patrol Enterprise Manager (PEM). Other customers deploy other solutions, presumably including SAP Solution Manager.
We would use SNMP traps to designate details such as alert severity, team assignment, and historical trending. As mentioned, in the absence of SNMP capability we would configure email parsing. The traps are preferred due to the delivery mechanism and content rigor.
Once I'm back in the office I'll circulate this thread for feedback.
I'm also interested in the participating in the Beta testing program. Send you mail with the details.
It would be nice to have this available. Thank you for all of your hardwork on previous versions.
Is it possible to have a Japanese version for the brand new BI Platform Support Tool? Or like our BI Product, there are many language packs to show multi-language user interface.
I thought Japanese customer will like it so much as it is such an amazing tool, so I am wondering if you could also consider this idea.
Depending on our resources available in the future, it is something we can definitely consider. Could you send me an email and let me know approx how many Japenese only customers this might help?
I have two questions please:
Do you have an estimate date to release the version BI Platform Support Tool 2.0?
Are you considering to integrate the Active Directory authentication method for logging on the tool?
Thanks in advance
The BIPST 2.0 will be released to customer early November.
We did include secWinAD authentication in this release. Would you like to test it out? Send me your S-USER id and I'll get you the beta to test out and make sure it works ok for you before release. My email is: firstname.lastname@example.org
I am interested with the BIPST 2.0 version. Can you please advise, how would I participate or have access to the beta?
Thanks for your interest in the beta. If you could send me your S-USER account # to my email, I will get you signed up.
Hello Toby, Thank you. Where can I find your email id? I have searched in your profile page and could not find it.
Toby, I have sent an email with my S-USER id. Please sign me up.
Great work in this latest version. So far I am only having one problem. The Patch History portion is throwing an error. I may be able to figure it out but if someone has already run into this error then please share your experience and/or resolution.
3 Suggestions I would like to see:
1. In the section for Semantic Layer, please include an identifier so that this could be exported and joined to this identifier in the Audit DB for further analysis. Not looking for full lineage, I can use Info Steward for that; but for my customers the ability to evaluate basic usage stats without advances auditor knowledge would be a nice to have. This information would allow for a simpler query and provide much of the info already.
2. Provide an export to Lumira Dataset(s) option for us to pull this into Lumira and build some visualizations giving a picture of the system to admins. I would also potentially take the data and use it Auditor & PA to forecast when resizing hardware and reconfiguring APS services for example may be needed. Access to the raw data would make all kinds of neat BI content on this info possible.
3. In addition to the ability to publish to SAP, allow the option for Partners & Customers to publish to their own Solution Manager system or HANA Environment. As a Partner we provide Maintenance to some of our customers and something like this might help us reduce the number of incidents have to forward to SAP. At the least it would help us better prepare our incidents for forwarding.
All "nice to haves" in my mind. I'll let the community speak to whether or not they would like to see any of these as well.
Thanks for the feedback! Regarding the Patch History error, did you copy the operations.d folder from the BIPST folder to your SAP Host Agent folder? Refer to step 5 of the Getting Started Guide (BI running on Windows)
If you continue to have issues with this, please post the issue to our new forum click here so that the solution can be shared with other users.
I have created JIRA items for all 3 of your enh requests. Some feedback: