1 2 3 24 Previous Next

BI Platform

358 Posts

I got real problems with performance in BI Launch Pad. For instance, my reports were opening very long time, navigation in BI Launch Pad was awful.

1. Let's modify the Tomcat setting, because by default they have low value.
o JavaHeapSize (-Xmx) from 2G to 4G
o MaxThreads from default (200) to 900
1.1 JavaHeapSize we should modify:
cd <bo inst folder>/sap_bobj/tomcat/bin
modify setenv.sh

# set the JAVA_OPTS for tomcat

JAVA_OPTS="-d64 -Dbobj.enterprise.home=${BOBJEDIR}enterprise_xi40 -Djava.awt.headless=true -Djava.net.preferIPv4Stack=false -Xmx4g -XX:MaxPermSize=384m -XX:+HeapDumpOnOutOfMemoryError -Xloggc:<bo_inst_folder>/sap_bobj/tomcat/logs/tomcat.gc.log -XX:+PrintGCDetails -XX:+UseParallelOldGC"

1.2 MaxThreads we would modify:
cd <bo_inst_folder>/sap_bobj/tomcat/conf modify

Define a non-SSL HTTP/1.1 Connector on port 8080

<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" maxThreads="900" URIEncoding="UTF-8"/>
  <!-- A "Connector" using the shared thread pool-->
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               redirectPort="8443" />




2. Cleaning of old installed patches and service packs from BO. What does it mean?
Just go to <bo inst folder> and run ./modifyOrRemoveProducts.sh (for Linux):
It is clear that i have many various installation on my server. But it is important to delete old installation!


3. Cleaning of logging directory, in <bo inst folder>/sap_bobj/logging
o Deleting Trace-Files
o Deleting Logs old than 30 days
4. Tuning APS, for start you can use CMC Wizard.
5. APS properties for tracing set to unspecified (-> means bo_trace.ini are used)


Level - Description
Unspecified - Force the use of BO_trace.ini to be used
None - Only critical events such as failures will be logged
Low - Ignores warning and status messages
Medium - Only Status messages with least important will be ignored
High - Includes all the logging messages


6. Disabling of unused services in the CMC, for instance, Crystal, Analyses services.


7. Reorganisation of database statistics of BO-Repository and BO-Auditing.


This one is high important point. As you know, every database has to manage its statistics according to number of rows. And if you do not collect stat, than you performance as well as refresh rate are decreasing.

Join Ty Miller, VP of Product Management SAP Analytics, on Thursday November 19th at 07:00 AM PST / 16:00 CET to learn about the revolutionary release of SAP Cloud for Analytics .


On this call Ty will discuss details of the release, the future of Cloud Analytics at SAP, as well as how you can get exclusive access to the software.


Registration for the webinar required and available via : SAP Customer Experience Group




Hello everyone,


I would like to take sometime to explain the behavior of the scenario when we schedule a report which contains the prompts and mark the delivery as "BI Inbox" as destination.


I am pretty sure most of you are quite aware of this functionally as this is being with the product for a while, however i am trying to establish the reason from the product and the design perspective.


The reason I am reaching out through SCN is that there are some discrepancies in understanding the significance of the "BI Inbox" aka Managed destination.


The end users see a difference when they try to compare the property bags of the instance delivered to "BI Inbox" to that of the same instance copied to other folder of users choice.


There is a difference which need to be understood, however few customers are complaining this is a bug.


Steps Involved while Scheduling a Report which is marked for "BI Inbox" as destination :


1) Select/choose the report wish to schedule.


2) Right Click select Schedule or select schedule option from the menu.


3) The user is redirected to the schedule page and there we choose the destinations, formats, other desired schedule options


4) Once the user is completed with the customizations click on schedule.


5) The History page opens up and display the status of the schedule ( Pending/Running/success and failed)


Internally the Servers which are responsible in this activity are. (Considering We are scheduling a Webi document) The processing server will vary for a CR document.



Webi Processing Server

Job server

Job server Child

Destination job server ( as we have choose the destination as "BI Inbox")


On top of this, the "BI Inbox" which is a Managed Destination doesn't have a option to schedule the report. however we can {view/refresh/Save As} the report through the users inbox.


This is where there is a noticeable design from the Platform While Viewing the Report instance, the Platform takes the help of the respective Plugin.


Hence in this case the View is done through Webi Plugin and because of which the user is able to view all the prompts which is integral part of the .wid file.


The user can even refresh and use Save As option to save the instance in that case the Webi Plug-in supplies all the desired property values.


This is not true in case of scheduling the report ,as the destination job server doesn't necessarily need to know about the report Kind as this is already processed by the respective Processing server,


The Delivery is based on the schedule options provided by the user and the delivery rules.


These delivery rules are different for all the 4 destinations (Managed - "BI Inbox", Unmanaged - "File System", SMTP- "Email", FTP- "File Transfer") .


This scenario is already validated with the affected domain teams and the Platform team and we also performed the tests on 3.x 4.0 and 4.1 and found the behavior is consistent.


Hence I would conclude that this is not a bug , as each destination is designed for a specific purpose.


Best Regards,


Whats this about?


This is an adjunct to Steve Fredell document in 1631734 - Configuring Active Directory Manual Authentication and SSO for BI4 in regard to manual authentication of SSO for BI4 which is tomcat centric.


However at a recent client there a similar use case required however was for deployment of the BO on NW7.31 >rather< than tomcat as the web application server.


There is also a worthwhile troubleshooting guide for tomcat here 1476374 - ***Best Practices*** including Basic and Advanced AD Troubleshooting Steps for Manual Logon, NTLM, Kerberos and Vintela Single Sign On





I have been asked to configure AD authentication, following Steve Fredell's "Configure Active Directory Manual Authentication and SSO for BI4" I could successfully get AD authentication working  fine with tomcat , but got stuck with NW as the web application server.

After spending close to 1 day of my customers time attempting this I failed to get it to work and posted this forum message AD authentication for BI4.0 on NW7.3x portal


-----------------  Forum Post ----------------------------



However when I use the same BOE/CMC with imported early into portal I get the error:



Account Information Not Recognized: Active Directory Authentication failed to log you on. Please contact your system administrator to make sure you are a member of a valid mapped group and try again. If you are not a member of the default domain, enter your user name as UserName@DNS_DomainName, and then try again. (FWM 00006)




So tomcat obviously understands the kerberos authentication, I have made sure the same server principle name and AD administrator credentials are the same, is in use by tomcat and portal both use SAPService<SID>


Any tips as to what I need to do to get Windows AD authentication working to BOE/CMC from a NW7.3 portal? Do I need to re-import the BOE deployment?



Swapnil Yavalkar  responded saying he had been successful but without capturing any details, which was good news as at least it proved it was possible.



Unfortunately in the available notes there is almost zero about how to get NW7 working as the web application server, I placed a service call to SAP in regard to the problem. Days later I got the response that there is a unpublished internal note 1852377 that describes the solution to my problem, I had got 95% of the way there but had not performed the subnode configuration in NW config tool.

Whilst I cannot republish this note I will post my solution ( albeit sanitized of customer details) which fairly much covers the same trajectory as 1852377


Step 0. Ensure principle names for Kerberos


Find and ensure you have set principle names for the service running your NW (portal) web application server.


You may need to setspn -A  to configure your principle names, however scope is beyond this blog for a start try here . However here is a sanitized list of principle names for the service owner ( which is more than needed)




Step 1. Create your kerberos configuration file


You will need a krb5.ini file as per notes above  into C:\windows, I copied mine from an existing tomcat configuration I had working.







Step 2. Add kerberos module to Netweaver Administrator


You will need to enable krb5 module to  NWA  http://theportalserver.com:50200/nwa




Configuration -> Authentication and Single Sign-On -> "Login Modules" tab



Create a module with the display name Krb5LoginModule with the class name of com.sun.security.auth.module.Krb5LoginModule





Then in tab "Components" tab create  a custom configuration called  com.businessobjects.security.jgss.initiate


Choose the lower authentication stack tab and then add the login module "krb5LoginModule" with the flag "REQUIRED"


Dont forget to save



Step 3 Using SAP Java configuration tool we add Java options.


I found it is best to do this during downtime of the NW portal.



Call configtool.bat from usr\sap\<SID>\J<id>\j2ee\configtool




I normally choose expert mode.


Choose the instance then choose "VM Parameters" tab


Select sap from the vendor list and global from the platform list.


Choose the "system" tab and new.
Add Name java.security.krb5.conf and the value of C:\windows\krb5.ini


Create another parameter called javax.security.auth.useSubjectCredsOnly with the value "false"


Choose File -> Apply changes.



Step 4. Adding sub-nodes for com.businessobjects.security.jgss.initiate policy.

Continuing with config tool

Choose Tools -> Configuration editor







Choose Edit mode.



Navigate to Configurations -> Security -> Configurations -> com.businessobjects.security.jgss.initiate -> security -> authentication.




Right click and choose "Create sub-node"


Choose "Value-Entry" name create_security_session with the value "false"


Then apply changes again.


Step 5. Restart NW Portal






Testing after 10 minutes system will restart and you should be able to authenticate with NW7.3 Web.loginok.png



For me it just worked first time , so I don't have any troubleshooting validation except check your syntax each time.




a) Get it working with your tomcat server first as per the guide attached to note 1631734 use the troubleshooting guide 1476374

b) Then follow this blog or note 1852377

Hi All,


We did a great PoC on the last month and I would like to share with you the results and what we did.


The POC history

Customer have on their environment SAP HANA installed with one BW productive system (BW on HANA) since 2013. Since the initial implementation, they were able to see many improvements on performance of many BW queries, DSOs and cubes. But, one of their most important reports, accessible per more than 1,000 users was not with a good performance with a performance of around 6 minutes to refresh the data

This generate a large negative noise against all the company like:

“SAP HANA doesn’t work”

“After the migration of BW to SAP HANA, the performance of my report didn’t change significantly”

"SAP HANA is not what I expected”

With that in mind, we did a meeting with the customer and schedule a small assessment. During our assessment we find some issues related to modeling best practices that were affecting the performance:

  • The union of 4 cubes resulting in a data set of almost 1 million rows;
  • Combination of ABAP Code on this SAP BW Query to convert some currencies and also to restrict data based on one Table (They are not using the Standard Analysis Authorizations);
  • Combination of two hierarchies structures on the same query/report;
  • Usage of Web Intelligence to one demand that could be fit with Design Studio;
  • Execution of many queries in Web Intelligence;
  • Many calculations done on report level

Technically speaking, this is what we find on their BW system when we start our assessment:


The POC Challenge:

With that in mind and after show these issues to customer, they challenge us: “OK SAP. We want this report running in 5 seconds or less.”

What and how we did:

Before thinking about how technically we could improve the performance of this report, we started talking and engaging the customer IT area to break some paradigms like: “Why you don’t do this directly on HANA?” or “Did you try to use a different tool?”. The business area also got involved during all process, to test if the report is ok in terms of usability and also if the values are ok.

These teams was a critical success factor, as they helped a lot validating some features of security, transformations, filters etc and also validating the data when we developed the HANA Views and also the dashboard.

We decided then to develop this same logic structure directly on SAP HANA, accessing the Calculation Views of each cube automatically created by SAP BW and modeling there all transformations.

As a front-end tool, we decided that the best would be Design Studio, as don’t generate any MicroCube and it’s also optimized to read HANA Views and the usage of Parent-Child Hierarchies.

It was the customer requirements for this dashboard:

Key Functionalities:

  • Good Performance (5 seconds)
  • Hierarchies (parent-child)
  • Custom Row-Based Security (based on one table)
  • Currency and Unit of Measure Conversion
  • Multi-Language
  • Drill down to more granularity (never possible with WebIntelligence)

After some weeks of hard work, we showed for this customer all of these functionalities based on HANA Views and the result was impressive:

Reduction of time from 6 minutes to less than 5 seconds (4,8 seconds on the best execution).

An improvement of 72X!!

To have a better understanding of how much this improve the customer operation and how this number is representative, let’s imagine that you could improve the time spend of a trip from São Paulo to New York that takes around 10 hours in 72 times. You would arrive in New York in only 8,5 minutes.


10 hours.JPG


8 minutes.JPG

After this job, the customer was satisfied and convinced that SAP HANA is really fast and really saw that with SAP HANA they can have an improvement on their process by increasing the BI adoption against all the company

The customer also saw that the problem was not on HANA, but in the way they did their BW query and also on the Front-End tool that they are using.

With this blog I want to give you a few highlights and, more important, inform you how this release will boost your 'analytical' organization.


It is time to set your sights on the upcoming major release of SAP BusinessObjects Business Intelligence 4.2 (BI 4.2), which is planned to be General Available Q1 of 2016.


Let's elaborate and approach from a business and technology perspective.

We are all aware things are changing around us including markets & segments, business requirements, solutions & IT-landscapes (Premise-Hybrid-Cloud).

When there is serious believe and business demand, a solid landscape for Analytics is a MUST.


Getting your landscape ready and provide a good foundation will help your analytical insights and grow your business.

Analytics needs to get simpler AND we need to be able to consume more data (aka data tsunami).



Because large amounts of data can become instant information without loss of time.

It's that simple.


Improving your landscape with this major release will give you extra benefits and toolset to enable your digital footprint throughout your organization.



In the following summary of BI 4.2, it will show you the highlights.

SAP BusinessObjects BI 4.2 theme - 3 main topics (as mentioned by SAP, SAP BO BI 4.2 What's New)

BI42 Theme1.PNG



- Empower everyone with analytics

- Access in the cloud; pay as you go

- Partner with one vendor for all your analytics need



- Integration of your current source systems

- Reuse and expand platforms



- Reveal hidden opportunities and risks

- Anticipate and plan future outcomes

- Manage your business based on what matters



Top 5 main features/enablers




Your organziation will be able to:

- Interact with each other on analysis and figures accompanied by comments

- Get your (common) information at any location via HANA Online

- Restore files by using the Recycle Bin

- Directly get the latest data with speed of thought from your HANA landscape

- Process combination of data sources faster




Using commentary to discuss amongst peers, shared elements to reuse objects and formulas without development changes and add GEO data to pinpoint hotspots.

Enabling these new features and enhancements will make it possbile to strive for Self Service Analytics.


My advice, scan and review your current landscape and roadmap for Analytics.

If you really want to be ready and benefit form 'All kinds of Things', this is it!




'Back to the the Future', let's preview the technical enhancements and specifications of BI 4.2.


Top 5 Features - Platform, IDT & WebIntelligence


SAP HANA Business Layer option using IDT

IDT - wizards_blog.png



SAP HANA Views for buildsing a Universe (Data Foundation & Business Layer)

IDT - wizards_HANAlayerX2_blog.png

IDT - wizards_HANAlayerX1_blog.png



Recycle Bin option for restoring files

Recycle bin - why default disabled.PNG



BI 4.2 WebI features (some of them)


Supporting GEO-data

WebI - Geography_onHANAunx.PNG


Freeze panes within a report-objects

Freeze panes.PNG



Many thanks to Christian, Silvia and SAP WebI/Semantic Layer engineering team for their efforts and support.

Great stuff!


Thank you for your reading-time and I really look forward to see this release into play.

Are you ready to join the game?



Patrick Sandriman



As this article describes beta material please remember that this presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.

In BI 3.x while creating the user in BI through CMC we have option of "user cannot change password"



1. When "user cannot change password"  option is checked.

   Here the user name is user1. So a new principal with name "user1" is getting added to this user after migrating to 4.0 SP05 on wards.



   Here for the user "user1" and users he owns cannot change the password as this right is denied for the user and for his descendants.




2. when the "user cannot change password" option is unchecked.


   Here user name is user2. New principal with user2 is getting added to the user after migrating to 4.0 SP05 on wards.



   Here for the user "user2"  and the users he owns can change their password as right is enable for the user and for his descendants.





In both the cases  the principal which is getting added is specific to the user. It will not effect any other users in BI.


Reason for this  new principal is getting added is "user cannot change password" option is getting converted in to rights.


These rights are put under one principal with same as user name. This principal we can see by selecting user security by right click the user.

Hi All,


I am no expert in Business Objects but encountered an issue on Monday that made me learn a lot. In this short blog post i will cover the error, analysis and resolution for the error we got on Monday Morning and got resolved by Tuesday evening only.


Our BO version 4.1 SP4 Update 4



The error began with an email from our customer that the BO isn't working. We have been facing issues with tomcat lately so we are used to getting these kind of calls. We took it as any other day and started looking at the logs for tomcat crash.

By the way if anyone of you face issues like below in your BO environment, the fix is documented in SAP note  1906557 - Tomcat crash due to EXCEPTION_ACCESS_VIOLATION in the zip.dll with Java_java_util_zip_ZipEntry_initFields

A file named hs_err_pidxxxxx contains


RE version: Java(TM) SE Runtime Environment (6.0_65-b11) (build 6.1.058)

# Java VM: SAP Java Server VM (6.1.058 24.45-b11 Nov  3 2013 00:29:18 - 61_REL - optU - windows amd64 - 6 - bas2:205339 (mixed mode) compressed oops)

# Problematic frame:

# C  [zip.dll+0x4c9b]  Java_java_util_zip_ZipEntry_initFields+0x1f8b (sp=0x00000000390bf170) (pc=0x000007fefb524c9b)


Coming back to the Monday Error, there were no traces or this kind of file so we thought of restarting BO once as i have been getting alerts for high memory consumption. Post restart the customer could enter BO CMC and BI Launchpad but when refreshed one of the Webi Reports to fetch data from backend BW, we got an error as "Failed to Connect to the OLAP Source (Error: INF)" and the day began with a High priority ticket in my queue. Too much for a Monday morning



Our analysis included a number of notes, SCN links, Wiki links and a very high ticket with SAP by Monday evening. The most important blog post was by Ted Ueda which helped me narrow down the issue.

End-to-End Trace and Identifying Root Cause for BI 4.x Web Intelligence


In the CMC -- Under Authentication, we maintain a user to backend SAP BW. as soon as we refreshed the report thrice it was getting locked. The users could not login to BI Launchpad if this user was locked using SAP authentication.


Then the blog post mentioned above came to our rescue. With the step by step instructions to look for error in GLF files, I could see the error Name or Password is incorrect. We changed the password, put the password in BO but it did not help


Now we were quite dependent on SAP's engineer as we had tried almost everything. Like trying create a new OLAP connection, check new Webi Report, etc, etc but to no avail. It looked more like a treasure hunt with clues and clues but no actual treasure


Another interesting thing was the error when creating a new Webi report. As soon as we clicked on the the OLAP connection we were presented with the Error


java.util.concurrent.ExecutionException: com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: [[error.openSapBwBrowsingSessionFailed] 0] <<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ConnectionString>


I will call myself too tired to do a note search with error.openSapBwBrowsingSessionFailed as i found numerous SCN posts with similar failed connection to OLAP and no resolution. We have already wasted 1.5 days to resolve this and we were nowhere.

The SAP engineer who had a session with me helped find SAP note 2062091 - In the "Select a BEx query" window, when creating a Web Intelligence report based on BEx, the message "Error: openSapBwBrowsingSessionFailed" appears.


This particular note talks about

  1. Log into BI Launchpad with the user that was added to the Administrator’s group.
  2. Create a new Web Intelligence report in the Applet, selecting BEx as the data source, and selecting the OLAP connection on the left window.
  3. After a few moments, the error "Error: openSapBwBrowsingSessionFailed" appears.
  • Once this occurs, the SAP BW account for the Entitlement System becomes or may become locked in BW system, due to too many incorrect attempts.
  • If the password for the SAP account that is entered in the Entitlement System tab within the CMC / Authentication SAP  section is updated to not contain a special character, the problem does not appear for some environments.

The same was happening with us and the reason was too simple to be true. But as soon as we setup a password without Special characters it was all back to normal. So if you are also getting an issue like this. Try above SAP note and see if it helps.


Such a simple issue gave me and my team a sleepless night but as they say --- all is well that ends well


Hope you enjoyed reading the post and special thanks to Ted for helping others with such a nice blog and the SAP Engineer who helped us resolve this issue.



Aditya Khorana

Mike Griffiths

Chat Support for BI

Posted by Mike Griffiths Oct 9, 2015

Hi BI Community,


We are extremely pleased to announce the introduction of Chat Support for BI.  Chat Support is one of our Real Time support offerings that is available to our BI customers.  Customers who use Chat Support are instantly connected with an experienced SAP BI Support Engineer.  The SAP BI Support Engineer will provide immediate assistance in order to help resolve your BI support issue during the Chat session.


This initiative has started as a pilot for BI Product Support and has been rolled out to three Topic areas:


BI Administration (Component BI-BIP-ADM)


All security issues and issues pertaining to Rights and Permissions

Issues dealing with Encyclopedia

Problems with the various servers in the Business Intelligence Platform

BW Publisher

Security Viewer

All Enterprise printing and export issues with Crystal Reports on the Server

Crystal Report Refresh issues in Enterprise

Issues with Query as a Web Service (QaaWS) consumption in a Crystal report

OpenDocument issues with Crystal reports.


BI Publications (Component BI-BIP-PUB)


General scheduling, publishing, and exporting issues with publications

Issues with publications where the source document is a Crystal Report and the report itself fails to schedule.


BI Dashboards (Components BI-RA-XL*)


All Xcelsius/Dashboard install, design and refresh issues

Issues publishing Xcelsius/Dashboard models to Infoview, .swf, .ppt, etc.

Issues related to Query as a Web Service (QaaWS), Live Office, and BW consumption in an Xcelsius/Dashboard model.

Issues with Xcelsius/Dashboard and BI Widgets



Using the Incident Wizard, you will see a new "Chat Support" button when you select one of these components (BI-BIP-ADM, BI-BIP-PUB, BI-RA-XL)


Chat Button.png


Selecting the button will connect you to an SAP BI Support Engineer via a Chat session. To keep track of your chat, the SAP BI Support Engineer will create an incident on your behalf.


This Chat Button will only appear:

·         For the BI Components areas mentioned above

·         If a SAP BI Support Engineer is ready to take your Chat.


We have SAP BI Support Engineers online globally during the working week to assist you via Chat.  For further details on how this works, reference SAP Knowledge Base 2213344 - How to start a chat with SAP Support [video] which provides a video demonstration.


I encourage you to give this a try in order to get a faster resolution to your BI Product support topics.

Any feedback you have is very welcome. The best way to provide it is via the Chat, when prompted at the end of the session. Your feedback will help us to improve the Chat Support experience for the roll-out of this service across all of the BI components.


Thanks and regards,


Mike Griffiths

Global Director, SAP BI Product Support

I did not find any specific documentation for configuring Windows AD and SSO for only IS/DS components. Just thought of puttig all those steps together. I followed the below SAP Notes.


1631734 - Configuring Active Directory Manual Authentication and SSO for BI4


OS: Windows Server 2012

DB: MS SQL Server

Apps: IS/DS (Installed with IPS - Information Platform Service, no additional license required)


In our case we enabled SSO for InfoSteward and DS Designer. For DS console and CMC we are using Windows AD athentication only. But this article gives you steps to enable SSO for all components.



Section 1 - Planning your Service Account Configuration

Before configuring IS/DS for AD logins we must request AD service accounts. This service accounts should have 3 roles.

1.      Query AD

2.      Run the SIA/CMS and allow manual AD logins

3.      Allows SSO


Section 2 - Creating and preparing the service account

Instead for creating new AD account in Domain Controller, we decided to use already existing <sid>adm user as BI Service account.


Get it done these steps with the help of AD team:


It has been setup with “Password never expire" and "unlock"



Delegation for the Service Account


navigate to the properties of the service account and choose

Trust this user for delegation to any service (Kerberos only) under the Delegation tab.



Setspn Commands - Should be run on Domain controller server by AD team


setspn -a BICMS/<sid>adm.domain.com <sid>adm

setspn -a HTTP/host.domain.com <sid>adm

setspn -a HTTP/host <sid>adm


Once they run this commands you can view them from your IS/DS server by running below commands


setspn -l <sid>adm


Section 3 - Configure the AD Plugin Page in the CMC and map in AD groups

Login to CMC => Authentication => Windows AD


Check "Enable Windows Active Directory (AD)"


AD Administrator Name: Domain\<sid>adm

Default AD Domain: Domain.com


Mapped AD Member Groups: We need to add the required AD groups here who needs access.


Authentication Options:

Use Kerberos authentication

Service principal name: BICMS/<sid>adm.domain.com


Check "Enable Single Sign On for selected authentication mode.


New Alias options: Assign each new AD alias to an existing user account with the same name

Alias update options: Create new alias when alias update occurs

New User options: New users are created as concurrent users


On-demand AD update:

Update AD Groups and Alias now





Verifying users


Go to


CMC>Users and Groups>Group Hierarchy

and select the AD group you mapped to view the users for that group. This will generate a live query to AD (using the CMC query account) and display the current users in that group. It will also display any nested users in that group (users that belong to nested AD groups).



Do not proceed if users and/or groups are not mapping in properly!



Section 4 — Steps to start the SIA/CMS under the service account

In order for the service account to run the SIA there are specific operating system settings that need to be set.


      1. Add the service account to the local administrator‘s group on any server where the service account will be running a SIA/CMS.

          Open Computer Management > Local Users and Groups > Groups > Administrator > Properties > Add


      2. You should also grant the local policy Act as Part of the operating system as seen in the screenshot below.

          Open Local security Policy > Local Policies > User Rights Assignments > Act as part of operating system > Properties > Add User or Group


      3. After the above changes have been made the service account can now run the Server Intelligence Agent (SIA). Navigate to the Central Configuration Manager (CCM), stop the SIA and on the properties tab enter the account in domain\username format. And restart SIA.



1.   4. Verify the service account and AD logins are working


You should be able to login via DataServices Designer at this point. The next steps will test an AD login with the Central Configuration Manager‘s Manage Servers tool.

Add your user to Administrator group temporarily and login to server with your id and test it.

Add your user to Administrator group in CMC temporarily


      Open the DataServices Designer >

      System - host[:port]: host:6400

      User name: Blank

      Password: Blank

      Authentication: Windows AD

      Log on


      Then it should show the DS repositories.



Section 5 –Configuring Manual AD authentication to Java Application Servers


Two files need to be created when using java. These files need to be created from scratch and should be placed in the C:\windows\ directory on any windows application server.

Create the bscLogin.conf file

Note: Make sure the file is not a text file



com.businessobjects.security.jgss.initiate {


com.sun.security.auth.module.Krb5LoginModule required debug=true;




     Create the krb5.ini file




default_realm = DOMAIN.COM

dns_lookup_kdc = true

dns_lookup_realm = true

default_tgs_enctypes = rc4-hmac

default_tkt_enctypes = rc4-hmac

udp_preference_limit = 1




default_domain = DOMAIN.COM


Regfer OSS Note 1690665 - Unable to logon to BI Launchpad or CMC using Manual AD Authentication in BI 4.0 while creating krb5.ini file.


    Verify java can successfully receive a kerberos ticket


      1. From DOS command line navigate to the sapjvm\bin directory. By default this is:


E:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin


2. Run

kinit username hit enter and type your password


kinit <sid>adm



If the KDC and other configurations in the krb5.ini are correct you should receive a ticket.


Section 6 – Configuring CMC for manual AD login


Create CmcApp.properties file with below lines






Point your application server to the bscLogin.conf and krb5.ini files.


Add the following lines to the tomcat java options. Tomcat must be restarted to test.





Restart the Tomcat


Verify the bscLogin.conf has been loaded by your application server


To verify the bscLogin.conf has been loaded by your application server attempt to logon to CMC (with AD selected in the drop down).



Check the sdtout.log in ..\


tomcat\logs folder and you should see "Commit succeed"


At this point you will be able to login InfoSteward, DataService Console & CMC with Windows AD logins.


Section 7 – Configuring Active Directory Single Sign On



Increase Tomcat’s maxHttpHeaderSize



Take the backup of existing server.xml and add the maxHttpHeaderSize="65536" in Connector Port 8080 tag



Create and configure a global.properties file




Create a file named global.properties with the following text inside:












For the values in bold above replace them with the values for your service account from Section 2 above.


Create and configure a ICCExplore.properties file


Copy the ICCExplore.properties file from ..\tomcat\webapps\BOE\WEB-INF\config\default to ..\tomcat\webapps\BOE\WEB-INF\config\custom folder and modify it





Add additonal parameters to CmcApp.properties file - Optional

If you want to configure SSO for CMC as well? you can create CmcApp.properties file with below text inside. But it is not a good idea to enable SSO for CMC. Because if SSO doesn't work in order to troubleshoot you need to login to CMC first and also you might see security issues if some hacker get access to your domain.





sso.supported.types=vintela, trustedIIS, trustedHeader, trustedParameter, trustedCookie,

trustedSession, trustedUserPrincipal, trustedVintela, trustedX509, sapSSO, siteminder




Refer OSS Note: 2190831 - How to enable CMC SSO in BI 4.1 SP6


Configuring the application server’s Java Options for AD Single Sign On


1. Add the following lines to the tomcat java options. Tomcat must be restarted to test.





The wedgetail.sso.password is the password for your service account from Section 2 above.

The DJCSI.kerberos.debug options will enable a start up trace of the vintela filter.


Configuring the Data Services for SSO

Take the backup of existing web.xml file and modify the parameters which you have put in global.properities file.








Uncomment the auth filters and update domain & service account details. Disable the content related to keytab. We need to enable it later


<!-- start filter setting -->
















<!-- End filter setting -->



Verify the vintela filter has loaded successfully

Stop Tomcat

Delete or backup the logs in below folders



Remove the folder ..\tomcat\work\Catalina\localhost\DataServices

Restart Tomcat


Open the sdterr.log file in tomcat\logs and look for lines


INFO: Server startup in ###### ms


jcsi.kerberos: ** credentials obtained .. **.



Testing AD Single Sign On

Note: Do not test SSO on Tomcat server, so you should check on different server. When we hit the URL on browser it should automatically make you login without user/password since we logged into the server where we are testing with domain user.


Testing AD Single Sign On for InfoSteward



Testing AD Single Sign On for DS Designer


Login to IS/DS server with your id and start DS Designer

Open DS Designer

System - host[:port]: host:6400

      User name: Blank

      Password: Blank

      Authentication: Windows AD

      Log on

Select the repository and click OK


You should login to that repository.


Note: You should have access to that repository on DB level.


Testing AD Single Sign On for DS Management Console




You should be able to login to DS console with your domain without prompting for user/password


Section 8 – Encrypting your service account password with a keytab

An alternative to hard-coding the service account‘s password in the java options we can encrypt the password in a keytab file.


We need to run the below command on AD server.


ktpass -out bosso.keytab -princ <BI Service Account> -pass

<password> -kvno 255 -ptype KRB5_NT_PRINCIPAL -crypto RC4-HMAC-NT


Once you receive the file you need to perform the below steps


Copy the bosso.keytab to the C:\Windows\ directory of the IS/DS application server


Add the following line to ..\tomcat\webapps\BOE\WEB-INF\config\custom\global.properties


idm.keytab=C:/WINDOWS/bosso.keytab (note the FORWARD slashes)


Remove the wedgetail.passwords option from the application server‘s Tomcat java options.


Add the following lines to ..\tomcat\webapps\DataServices\WEB-INF\web.xml




Restart Tomcat and ensure you still see jcsi.kerberos: ** credentials obtained.. **. in the application server logs per the directions in the section above titled Verify the vintela filter has loaded successfully.


Test again SSO for IS, DS.


See KBA 1359035 to test the keytab separately if SSO stops working after these changes.


Disable debug mode in Tomcat java properites


Section 9 – Additional information and settings


Ensure your .properties files are not overwritten after a patch or redeploy

1. Copy the BIlaunchpad.properties, global.properties and ICCExplorer.properties files from:



2. Paste the .properties files in the folder below:

SAPBusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom


3. Copy the web.xml file from



SAPBusinessObjects\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\DataServices\WEB-INF

Take the backup of existing file before copying it.

End of the Article


You can post your questions or comments here, so that I can clarify.

Hi All,

As most of you are aware that the Sample Auditing unx/unv along with the sample reports are available in SCN  @http://scn.sap.com/docs/DOC-53904

However there is a problem observed for one of the dimension part of Auditing universe.

This is for the users who are using the audit reports which are based out of Auditing.unx. where the Event status - successful/failed field is part of the audit report will show most of the status as failed despite they are successfully audited.

This is noticeable only when the users are trying to retrieve the Event status - successful/failed dimension from the Auditing.unx during that time almost all of them are showing it as failed.

The reason for this behavior is the query condition mentioned for the Event status - successful/failed is wrong and need an update.

Here are the steps to modify one of the dimension in the Auditing.unx.

1) Open the Universe using Information Design Tool (IDT) for BOE 4.x.

2) Traverse to the Events table and select the dimension Event status - successful/failed and double click on that, You can notice the query on the Query panel  as "ADS_STATUS_STR.Status_ID WHEN 0 THEN 'Successful' ELSE 'failed' END" which is not the correct condition.

3) Please replace the Query with "ADS_STATUS_STR.Status_ID WHEN 1 THEN 'failed' ELSE 'successful' END".

4) Save and Publish the Universe back to repository

5) Refresh the Report.

Note: This is required only to support the Event_Type_ID (1008) Save, the reason being Save has 3 successful status (0,2,3) and 1 failed status where as all other events has only one successful status (0)  and one failed status(1).

Best Regards,



Here I go again, yapping about performance. It's one of those topics that never really goes away. Inevitably, as a BI consultant, you will have to perform performance tuning either on your reports, or your back end. Fortunately, I've already covered a few back end tips and tricks on a previous blog post (Backend Performance Tips) . In this post, I will be covering a few performance tuning tricks that I've used in previous projects, to improve the performance of WEBI reports, connected to BW via BICS connection and BEx queries. There are a plethora of guides on SCN on how to improve WEBI performance, which uncovers some not so obvious places where performance can be improved.


This is by no means a comprehensive list of everything you can do to speed up those WEBI reports, but they are a few tips that have been very effective in my projects. These tips are valid up to BW 7.3 on HANA, and BOBJ 4.0 and above.


With BW 7.4 on HANA and HANA Studio, some of these tips might still be relevant, and some might not, as we have more back end modelling options, the HANA Views provide tremendous analytical capabilities, which in certain scenarios might just make these tips irrelevant.


For those of you who haven't yet taken the plunge into BW 7.4 on HANA, and HANA Studio, and are using BEx through BICS to connect to WEBI, hopefully these will be of use to you. So let's get to it.

Logical Partitioning

Although this is really a change to the back end data modelling, it is one that can improve significantly the performance of your reports. So much so, that in more recent versions of BW, SAP introduced a tool to automate the process of creating logically partitioned infoproviders, the Semantic Partitioned Objects. I have covered this in my previous blog (Backend Performance Tips) as well as referenced a great article by Rakesh Dilip Kalyankar on SPOs:


Focusing on the Front End, the reason logical partitioning improves performance is quite simple, as illustrated by the example below:

A user has a report that outputs current YTD key figures, and previous YTD key figures. All the data resides in a cube which has 10 years worth of data (say 2005 - 2015), sitting under a multiprovider. For simplicity, let's say that there's 50 million records, 5 million per year.

When the user runs the report for 2015, we expect to see 2014 and 2015 YTD figures. The SQL statement has to sift through 50 million records to identify only the 2014 and 2015 records and will take x amount of time.

Now let's imagine that in the back end, we have 10 cubes, identical in structure, logically partitioned by year (2005 cube, 2006.... 2015, 2016 etc.). Each cube will contain 5 million records, all of them sitting under a single multiprovider. When the user runs that same report, the multiprovider is intelligent enough to direct the read to the 2014 and 2015 cubes. Rather than sifting through 50 million records, we're now only going through 10 million records (5 million in each cube).

This will result in faster running reports due to less volume of data to read. This is an effective and recommended approach to improving query performance.

Aggregation Flag on HANA

BEx queries can be complex beasts. With aggregations, exception aggregations, counting documents, customers, items, restricted and calculated key figures, cell calculations, etc., they can become very onerous on the OLAP Analytic Manager. The OLAP manager has an orchestration role, in which it translates the BW query into an OLAP calculation graph. See below:


Source: openSap

With a non HANA DB, these are the steps taken to calculate exception aggregations:


Source: openSap

And here are the steps for a BW on HANA system:


Source: openSap

The performance gains from enabling this setting are huge.

For those of you running BW on HANA, there's a nifty little setting hidden in the multiprovider properties. It allows us to push the aggregation and exception aggregation functions down to the HANA DB.

1. Go to the multiprovider to be modified, and make sure you're in change mode. Once in the design screen, go to Extras > InfoProvider Properties > Change:


In the next screen, under SAP HANA/BWA Ops, make sure to select 6 Exception Aggregation. This will enable the push down of the functionality to the HANA DB


OSS note 2063449 - Push down of BW OLAP functionalities to SAP HANA provides the list of operations that can be pushed down to the HANA DB, and is constantly being updated. Below is the list of functionalities as of the publication of this post:


Analytic Manager operationRelease*
AggregationBW 7.0 + BWA 7.00
Cell-based calculations (FEMS)BW 7.0 + BWA 7.00
Hierarchy-processing (part 1)BW 7.0 + BWA 7.00
MultiProvider-UNIONBW 7.3 + BWA 7.20
Exception aggregation COUNTBW 7.3 + BWA 7.20
Exception aggregation for keyfigures w/o currency/unit conversionBW 7.3 + BWA 7.20
Exception aggregation for keyfigures w/ currency conversionBW 7.3 + BWA 7.20
Exception aggregation for keyfigures w/ unit conversion without reference InfoObjectBW 7.3 + BWA 7.20
Time-dependent currency conversionBW 7.3 (SP10) on HANA
Avoid intermediate result set materialization (Layer ”Q” virtualization)BW 7.4 (SP05) on HANA
“Current member” calculationBW 7.4 (SP05)
CompositeProvider (e.g. JOIN between fact data)BW 7.4 (SP05) on HANA
Stock coverage keyfiguresBW 7.4 (SP06)
Unit conversion with Reference InfoObjects  (see SAP Note 2001947 to switch off)BW 7.4 (SP08) on HANA
Parts of Handling of inventory keyfigures  (see SAP Note 2001947 to switch on)BW 7.4 (SP08) on HANA
Leverage HANA hierarchy processingplanned with BW 7.5(SP00) on HANA
List-based calculations (like conditions)under discussion
Time-Series calculationsunder discussion
Temporal Hierarchy JOINplanned
Internal Business Volume eliminationunder discussion
Formula exception aggregation for non-dimensional keyfiguresplanned
Formula exception aggregationplanned

Use Selection of Structure Elements

For queries that use many restricted and calculated key figures, BW provides a nice little checkbox, Use Selection of Structure Elements which will allow the SQL statement to only select and calculate the Key Figures or structure elements that are actually being used, which will result in less time for the select to run.

To access this, go to RSRT, enter the query name and then hit the properties button.


BEx - Free Characteristics

This is a really simple tip. Make sure all of your characteristics are in the Free Characteristics section of BEx. As we're simply passing along the data to BOBJ, we don't need the overhead of BEx calculating intermediary results by placing characteristics in the rows section. The final presentation will be done in WEBI, and that's where you will create the layout the end users are looking for.

BEx - Suppress Results

Very frequently, before the BOBJ days, we'd want to have fancy looking BEx reports, which included totals either by the end of the rows or columns. That was a legitimate requirement. However, similar to the Free Characteristics above, if we do not suppress the results, we have an overhead in the OLAP engine to calculate them. Even though we're putting all the characteristics in the Free Characteristics section, it's good practice to highlight them all, and suppress the results.

A quick example to show how performance is affected by having results, is to create a simple BEx report, put a couple of characteristics in the rows, and enable results for all of them. Run that report in RSRT with the debugging option, and note down the execution times. Then highlight all the characteristics in the rows and suppress the results, and re-run the report in RSRT, and compare the execution times. You should note a difference in the execution times.


BEx - Calculated and Restricted Key Figures

WEBI gives us the option to do a lot of calculations using variables and built in functions, somewhat similar to how you'd do formula calculations in Excel. It is very tempting to completely ignore BEx's OLAP capabilities, as we did, and do all the calculations to WEBI and the BOBJ server.

However, as described above, the OLAP Analytical Manager is very powerful, and with HANA in the mix, I would argue it's a pre requisite to push down if not all, the most complex calculations to BEx, via Calculated and Restricted Key Figures (CKF and RKF).

Although it might be simpler or easier to use variables in WEBI, performance will be significantly hindered using the BOBJ server. It is not made to handle huge volumes of data, and also does not have the same capabilities of the OLAP Analytical Manager.

Once we pushed all the calculations back to BEx, and used WEBI purely as presentation, with minimal logic in the variables, most of our complex reports began to run in under a minute, whereas they sometimes would simply timeout.

Key lesson - send it all back to BEx!

BEx - Variables

As a general rule, we the BW developers, instruct users to always filter the data they're running, so they don't try to run a report with wide open criteria, and fetch the entire table.

A way we enforce it, is by making some filters mandatory, say Fiscal Year, Fiscal Period, therefore limiting the amount of data users can run a report by, and improving performance that way.

When we have a scenario with WEBI using BEx via BICS connection, we are faced with the option of using BEx variables, or WEBI filters. We should always strive for the former (BEx variables).

If we simply set filters in WEBI, all the records from the cube will be selected, passed along to the BOBJ server, and then parsed for whatever values are in the filters. This makes for unnecessary data being transferred.

Conversely, if we have all the filters as variables in BEx, the records that will be passed to BOBJ are those which have been selected in the BEx selection screen. The illustration below might help to view this:


Using filters in WEBI, will result in the entire data in the cube being selected, and parsed within WEBI.



By using filters in BEx, only the filtered data will be passed to BOBJ, resulting in a smaller data set and better performance.

Navigational Attributes

One of the great functionalities of WEBI is that you can easily use Master Data Navigational and Display attributes. It's really a matter of dragging them in to the results area and then into the report itself once the report is executed. There are some functionality trade offs between the two, such as applying drill down and formula calculations to navigational attributes but not display attributes. That will not be covered here.

If we know that the user will have a requirement for reporting on attributes, and they will be a part of the standard layout, we've found that flagging them as navigational attributes will result in better performance.

The reason for that is, if we keep the attribute as Display, and add it to the report layout, the report has to go back and go through each parent characteristic of that attribute (Ex, color would be the display attribute and Material the parent characteristic) and then determine the output of the report.

If we flag the attribute as Navigational, the report treats it as it's own dimension, and therefore doesn't have the overhead of going to the parent characteristic to calculate the report output.

Query Stripping

This functionality within WEBI enables reports to 'pay for what they consume'. Many times, we design WEBI reports with many available fields, but only a selected few are part of the standard report layout, see below:


In the example above, all the available objects in the left are being retrieved from BW, although we're really only using a few in the default report.

Query stripping will optimize fetching of data to only the objects actively being used in the main report. With query stripping enabled, this particular report would only fetch the 5 fields actively used (Fiscal Year/Period, Material, Base Unit, Currency/Unit and Net Val. in stat curr).

By reducing the amount of objects being fetched from BW, we will improve report performance.

To activate this functionality, we must first do so at the WEBI query level, by going to Query Properties in the Query Panel, and selecting Enable query Stripping


And within the active document, under properties tab > Document


And then select Enable query stripping


Once these are enabled and you refresh the WEBI report, you will noticed that all the non active objects will be bold to indicate they have been 'stripped'


If you then add one of those objects into the report, you will get the message #REFRESH indicating that you need to refresh the report, so that it can go back to BW, and fetch the data for that object


The main challenged of using query stripping is educating the users of this functionality, why the report behaves the way it does, and why we're using it. Usually the performance trade-off of using the functionality turns users around the nuisance of having to refresh the report every time they drag a new object into it.


If end users aren't bugging you that WEBI reports are running slow, well then good for you, you've done a great job in creating awesome performing reports! For everyone else, hopefully this guide can help with the some simple yet highly effective and fast ways to get those slow running reports to run faster.

Like mentioned earlier, there are many blogs out there with more advanced ways in which you can create even better running reports.

Please post your comments to make sure I'm being kept true to all that's being mentioned here. Let me know what you've done in your projects and hopefully will can make this an interesting discussion on real world solutions to this never ending topic.

Happy reporting!


SAP TechEd Las Vegas (October 19-23) offers 5 days of learning (counting Monday, October 19th for the ASUG pre-cons) over a wide variety of topics to help you make the most out of your SAP investment.


This is a quote from a past SAP TechEd attendee:


"There's always a great deal to learn at the conference. But the key reason [Community: to attend SAP TechEd] each year is to focus on areas within BI, and to learn and understand the latest choices and direction that SAP is moving towards. We also often have the opportunity to meet with SAP executives to help guide future product direction" SOURCE




Source of comment by Raphael Branger


A subset of SAP TechEd BI agnostic sessions for SAP TechEd Las Vegas  is listed here - meaning those that do not rely on a BW/SAP ERP backend.


Platform developers, architects, and business users can take advantage of road map sessions to learn about the strategy, planning, execution, and collaboration available with solutions including:


Session ID



Road Map Q&A: SAP BusinessObjects Mobile


Road Map Q&A: SAP BusinessObjects Web Intelligence


Road Map Q&A: SAP Lumira


Road Map Q&A: SAP Predictive Analytics


Road Map Q&A: SAP BusinessObjects Business Intelligence Suite


Road Map Q&A: The Cloud and SAP Lumira Software


With SAP TechEd, as SAP's premiere technical education conference, and experience hands-on workshops developed for SAP's platform agnostic customers.


Session ID



Explore SAP BusinessObjects Design Studio


Leverage a Business Intelligence Platform to Deploy SAP Lumira


Learn Best Practices, Tips, and Tricks for Upgrading from XI3 to BI4


Automated Predictive Analytics Integration and Scripting


Build Analytical and Planning Apps with SAP BusinessObjects Design Studio


Create Connectors with SAP Lumira Software Data Access Extensions


The above picture is from last year's hands-on session by SAP TechEd photographer.


There are several lecture sessions for BI platform agnostic customers as well:


SAP Lecture Sessions – mostly Platform Agnostic:

Session ID




Enterprise Analytics Track Overview



Deploy Predictive Models in No Time with Rapid-Deployment Solution Content



Overview of the What, Why, and How of Analytics from SAP in the Cloud



Everything You Need to Know About SAP Lumira in Two Parts



Business Users Control and Drive Their Data



Leverage SAP BusinessObjects Mobile SDK for Your Analytical Needs



Tame Big Data with SAP Lumira Software



World Premiere of the Latest Release of SAP BusinessObjects Design Studio



Become a Data-Driven Business: Exploratory and Prescriptive Analytics



Analytics Partner Platform Play for Customers and Partners



Analyze Clinical and Genomic Data with Real-Time Medical Insight



It Isn't Only Brain Surgery: SAP HANA and SAP BusinessObjects BI Solutions



Apply a Fresh Face to Your BI Apps with SAP BusinessObjects Design Studio



Location Analytics and SAP BusinessObjects Design Studio



Take a Deep Dive into Deploying BI in the Cloud



Guide to SAP BusinessObjects Business Intelligence Platform Improvements



Know How and Where to Fine-Tune Your Business Intelligence Platform



Extract Real Business Value from Big Data with a Rapid-Deployment Solution



Interactive Charting Using Shiny in Predictive Analytics and SAP HANA



Extend Your Systems with Analytic Applications in SAP HANA Cloud Platform



SDK Experiences: SAP Lumira VizPacker and SAP BusinessObjects Design Studio



Using SAP BusinessObjects Design Studio for Self Service BI



Faster SAP Lumira Extension Development with D3 Data Manipulation



SAP BusinessObjects Web Intelligence Software Innovations



Dr Pepper's BI Accelerated with SAP HANA: From Design to Production



So hopefully you see you can obtain a comprehensive education on SAP solutions for analytics, business intelligence (BI), and mobile BI, as well as SAP HANA. If you’re gearing up to upgrade to the latest release of the SAP BusinessObjects BI platform, or sizing and administering the servers, there’s plenty of content at SAP TechEd 2015 to help you select the right tool for the job.   You can take advantage of this unique opportunity to expand your skill base – to excel at your job.


Platform agnostic solutions covered in include SAP Lumira SAP Predictive AnalyticsSAP BusinessObjects Web IntelligenceBI Platform, SAP BusinessObjects Mobile and SAP Design Studio


You can view all BusinessObjects sessions here. Also view the 6 ASUG BI Influence Council sessions at TechEd below:

Session ID



ASUG Influence Council: SAP BusinessObjects Analysis


ASUG Influence Council: SAP Predictive Analytics


ASUG Influence Council: SAP BusinessObjects Design Studio


BIP Influence Council Live Meeting


ASUG Influence Council Open Meeting: SAP Lumira


ASUG Influence Council Update and Road Map: SAP Business Objects Mobile BI


ASUG Influence Councils allow you to "impact the future of SAP products".  See you next month in Las Vegas.


Consider joining ASUG next month at SAP TechEd Las Vegas, including someSAP BusinessObjects Design Studio hands-on sessions as well.

Related Items

September 15 ASUG Webcast - What is Coming in SAP BusinessObjects BI4.2

Upcoming ASUG Webcasts

#askSAP September 17 webcast  - open to everyone

ASUG SAP Analytics BusinessObjects Conference Presentations

Doing a Full install from BI 4.0.6+ to BI 4.1.6 and Retaining FULL content & Settings

Major Benefits:

  • Save an average of 5-8Gig per SP/FP applied to your original install
  • Installing NEW features of BI 4.1.6 with any corruption to your BI4 install
  • Consistent built of all DLL and library files, no mixed versions of DLL’s
  • Opportunity to cleaning up OS build and optimize base server Pre BI 4.1.6
  • Upgrade from Windows 200x to 2012 with FULL content retention
  • Move your install from Drive C: long name to any Drive with shorter path
    • D:\SAP BusinessObjects\
  • NO need for Promotion Manager to move any objects
  • NO need to re-configure any BI4 Server, all settings fully retained
  • No Size &/or Objects limit for FRS restore (restored up to 50Gig)


High-Level Steps:

  • The CMS database MUST be the correct version prior to connecting to BI 4.1.6
  • Do complete back-up of existing BI 4.0.6+ Server, including
    • CMS and Audit database
    • BOBJ Administrator password should be complicated
    • Reset / Validate Cluster Key password
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
    • Any other special customization done
    • Originally running on Windows 2003 Ent 64bit
  • Upgrade the current BI 4.0.6+ environment to BI 4.1.6
  • Upgrade any additional options being used such as:
    • BI 4.1.6 Explorer
    • Analysis 1.4 w/ SP13 BIP Add-In
    • Design Studio v1.5 Add-In
    • Lumira v1.0.27 BIP Add-In
  • All other options should be installed after BI 4.1.6 Cluster has been reinitialized



Our Restore Example:

Server Name:          PS01

CMS Name:             PS01

Administrator:         <Confirm password is complex>

Cluster Key:            Confirmed password

CMS_DB:                XI4_CMS (MS SQL Server 2012)

Audit_DB:               XI4_AUDIT (MS SQL Server 2012)

ORG BI4 ver:           BI 4.0 w/ SP2

  • Upgraded to BI 4.0 w/SP4
  • Upgraded to BI 4.0 w/SP6
  • Upgraded to BI 4.1
  • Upgraded to BI 4.1 Patch 02
  • Upgraded to BI 4.1 w/SP4
  • Upgraded to BI 4.1 w/SP6

New Windows 2012 RC2 64bit Install


FACT: You will save disk space when doing NEW full install

  • Using real world experience from supporting 50+ BI 4.x installs. With every patch upgrade BI4 Platform install directory increases in size.
  • The current clean-up processes after a patch is very poor, older files are NOT removed.
  • Clean move from Windows 2003/2008 to Windows 2012 with full retention
  • In install example, customer started with NEW Bi 4.0 w/SP2 install
    • Upgraded to BI 4.0 w/SP4 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.0 w/SP6 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 Patch 02 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 w/SP4 (Added ~ 7Gigs of overhead)
    • Upgraded to BI 4.1 w/SP6 (Added ~ 7Gigs of overhead)
    • Approx. added 40+ Gigs of overhead to your install


FACT: Move from Windows 200x to 2012 with full retention


This is an excellent opportunity to move your BI 4.1.6 install from Windows 200x to Window 2012 as long as the server name stay the same.

FACT: Repointing a newer BI 4.1.6 to an older Repository BI 4.xx is NOT valid

Starting with BI 4.x the CMS database now has full version signature.  You can’t take an older BI 4.0.6 CMS database and connect it to a BI 4.1.6 install, this will corrupt you install.



Step 1: Back-up Current BI 4.0.6 Environment

Complete Back-Up Process includes:

  • BOBJ Servers Image back-up by IT
  • CMS and Audit database
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
  • Any other special customization done


Step 2: In-Place Upgrade to BI 4.1 W/SP6

In-Place Upgrade involves:

  • NOTE: Confirm Administrator password is complex; otherwise you will have issues with SIA when doing FULL Install.  See NOTE – 2188271
  • We need to upgrade the current BI 4.x install to BI 4.1.6 in order to have the CMS database updated. 
    • Upgrade all the CMS Server in parallel
    • Next upgrade ALL the Applications servers within the cluster





Update - SAP Explorer to BI 4.1 w/ SP6 (Optional if installed)


Update – Analysis Add-On for BIP ver 1.4 w/ SP13 (Optional if installed)


Update – Design Studio 1.5 for BIP Add-On (Optional if installed)

Update – LUMIRA BI Platform add-on ver 1.27 (Optional if installed)

Step 3: Back-up In-Place Upgraded BI 4.1.6 Environment

Complete Back-Up Process includes:

  • BOBJ Servers Image back-up by IT
  • CMS and Audit database
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
  • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
  • Any other special customization done
  • Take NOTE of:
    • System DNS named and configuration
    • 64-bit Database drivers
    • Any other 3rd party software configuration
  • We will need the BI 4.1.6 signature upgraded CMS database & FRS as a SET to attached to NEW install.


Step 4: Doing NEW FULL-Build Install of BI 4.1 w/SP6

  • Get IT to do NEW installed Windows 2012 RC2 Server with same name as previous BOBJ server, in our example its “PS01”.  If running a BI4 Cluster, you will need IT do NEW installs of Windows 2012 with same name as previous server (SERVER_xx).



  • Install 64-ODBC Drivers required and configure properly. In our example it 64-bit MS SQL 2012 Native Client / Admin tool.
  • Configure the System ODBC-64bit with same names as original BOBJ server.  In our example XI4_CMS / XI4_AUDIT
  • Integrate other options, such as:
    • Joint NT Domain controller using proper NT Service Account
    • Integrate SAN / NAS as required
    • Install SUN JRE / JRK as required, set-up proper parameters
    • Install HTTP / JAVA Application as required
    • Install latest Windows Security updates, including .NET 4.5
    • Other miscellaneous application &/or configuration
  • Have IT take fully IMAGE / SNAPSHOT of system prior starting BI 4.1.6 NEW Install. Taking a full back-up of the NT Server PRE_BOBJ will come in handy in the future.


Install BI 4.1.6 w/SP6 NEW install












Install BI 4.1.6 w/SP6 Explorer Add-On (Optional):

Install Analysis 1.4 w/SP13 – Add-On for BIP (Optional):


Install Design Studio 1.5 w/SP00 – Add-On for BIP (Optional):


Install Lumira Server v 1.0.27 for BIP (Optional):


Validate NEW BI 4.1.6 CLUSTER Install with SAME Add-On’s




For a BI 4.1.6 Cluster, continue install of other servers

  • Install other CMS Servers within Cluster
  • Next install all other Application servers within Cluster
  • NEW base BI 4.1.6 Cluster is fully ready and on-line


Step 5: Doing Server Restore of ORIGINAL System:

Complete Restore Process includes:

  • STOP Tomcat & SIA
  • Restore CMS Database and Audit Database
    • In our sample it’s XI4_CMS & XI4_AUDIT
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\Polestar
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB
    • D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore
    • Any other special customization done


Server Restore Process Step-by-Step:















For more details on FULL restore, please refer to SCN post

How to Restore BI4 from FRS & CMS Backup


  • Continue installing any NEW add-on options as required to fully working cluster

Timehop is a popular mobile app that bills itself as "a time capsule of you." It allows you to review your historical social media activity from "this exact day in history" and re-share. The app is so popular, Facebook decided to copy the idea into its own "On This Day" feature. Today, September 2, was the last day of ASUG's SAP Analytics and BusinessObjects User Conference, or #SABOUC as we call it on social media. And on this day four years ago in 2011 (see what I just did there?), I wrote a blog entitled "Waiting on SAP BusinessObjects BI4" expressing both excitement and frustration at waiting for the general availability of SAP BusinessObjects Business Intelligence 4.0. SAP BI 4.0 would go GA just a few short days later on Friday, September 16, 2011.


SAP BusinessObjects Business Intelligence 4.2, the eagerly awaited update to the BI4 platform, quietly went into beta this week (see related SCN article, "SAP BusinessObjects BI4.2 Announced by Steve Lucas"). But there was barely a word of it breathed during SABOUC conference sessions. And not one word during conference keynotes. With mainstream support for SAP BusinessObjects Enterprise XI 3.1 and SAP BusinessObjects BI 4.0 ending on December 31, 2015 (see related SCN article, "New Maintenance Dates for SAP BusinessObjects BI4.1"), all roads lead to the currently available BI 4.1 and its Support Pack 6. SAP will provide BI 4.1 Support Pack 7 near the end of 2015. But customers wishing to meet the deadline (and that's all of you, right?) will most likely use the current release.


Quite simply, SAP BusinessObjects Business Intelligence 4.2 will not go GA in 2015 and is therefore not an appropriate upgrade path for organizations still using XI 3.1 or BI 4.0. Sadly, SAP reinforced that logic this week by not dangling any tempting carrots of BI 4.2 goodness in front of eager conference goers. As frustrating as the BI4 installer's “WaitForCMSForTheFirstTime” message can be, no doubt folks at SAP are experiencing a little frustration watching the "WaitForCustomersToUpgradeToBI41" message on their screens.


It's possible that SAP may have more to show and tell at the upcoming TechEd conference next month. Or possibly even the upcoming SAP Insider Reporting & Analytics conference. But it's also entirely possible that we'll be waiting until 2016. Instead of our usual New Year's Eve routine of watching Ryan Seacrest and the ball dropping in Times Square, SAP analytics customers may have to switch channels and watch Steve Lucas, President of SAP Platform Solutions, and a giant XI 3.1 logo dropping in Walldorf.


I will be watching.


Are you eagerly awaiting the arrival of SAP BusinessObjects Business Intelligence 4.2? Share your thoughts below.


Filter Blog

By author:
By date:
By tag: