You have two options:

Options 1: (Exiting BI 4.0 w/ SP4+ Install, migrate Derby Database)

If you have existing data in your Derby trending database, you will need to migrate the Derby database to the auditing database, and then configure the BI platform to record monitoring information in the auditing database. These are the high-level steps you'll need to follow. For details, see the related topics.

• Migrate the Derby database.
• Verify that the auditing database is working, and auditing is running properly.
• Create the monitoring tables in the ADS (optional).
• Configure the SBO files and add alias names.
• Switch to the auditing database.
• Restart the Adaptive Processing Server that hosts the Monitoring Service.
• On the Monitoring Dashboard, ensure that everything works as expected. Verify that these monitoring tables have been created in the database:
  • MOT_MES_DETAILS
  • MOT_MES_METRICS
  • MOT_TREND_DATA
  • MOT_TREND_DETAILS
• Restore Derby Database

Option 2: (New BI 4.0 w/ SP4 Install, No Data in Derby Database)

If you do not have data in your trending database, that is, you have a fresh installation, you do not need to migrate the database; you only need to configure the BI platform to record monitoring information in the auditing database. These are the high-level steps you'll need to follow.

• Verify that the auditing database is working, and auditing is running properly.
• Create the monitoring tables in the ADS (optional).
• Configure the SBO files and add alias names.
• Switch to the auditing database.
• Restart the Adaptive Processing Server that hosts the Monitoring Service.
• On the Monitoring Dashboard, ensure that everything works as expected. Verify that these monitoring tables have been created in the database:
  • MOT_MES_DETAILS
  • MOT_MES_METRICS
  • MOT_TREND_DATA
  • MOT_TREND_DETAILS

Step 1: Migrate existing Derby Database

Logon into CMC > Application > Monitoring Application Properties > Export

For best results Export Data to CSV. If you a cluster BI Platform environment then export data from most heavy used server environment and you should only import the data from one Derby instance. Importing data from multiple Derby instances will result in data inconsistency and is therefore not recommended.

Date will be export in CSV format to the default location of the Derby Trending Database folder, located in \SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB.  This is also the same location of all the database scripts to create the tables manually (optional).

BEFORE EXPORT:

AFTER EXPORT:

The following four CSV files are generated in the default Trending Database location; each CSV file is a representation of each table to be created in the monitoring DB:

• DerbyMot_Mes_Details.csv
• DerbyMot_Trend_Data.csv
• DerbyMot_Trend_Details.csv
• DerbyMot_Mes_Metrics.csv

Step 2: Verify Auditing Database Working Properly

Launch MS SQL Server Management Studio to validate Auditing database have been created properly

Step 3: - Create Monitoring Tables manually (Optional)

Use the SQL Scripts provided by BI Platform install to create the monitoring tables manually, location

\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB\

Step 4: - Configure SBO Files

Internally, the Monitoring application uses Connection Server libraries, and the SBO configuration is required for the Connection Server to establish connectivity to the database driver. You need to specify the database driver and its location in the SBO file to establish this connectivity, file location is <Install_Dir>\dataAccess\connectionServer\odbc\<dbType>.sbo

• If the database used for auditing is SAP HANA, the file where the driver needs to be configured is: newdb.sbo
• If the database used for auditing is MS SQL Server, the file where the driver needs to be configured is: sqlsrv.sbo
• For more details on other database type refer to The Platform Administration Guide, location http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp4_bip_admin_en.pdf
• Below is an example of changes MUST be made to ALL MS SQL 2008 / 2012 / 2014 database

BEFORE:

AFTER:

Step 5: - Switch Monitoring to Auditing Database

Logon into CMC > Application > Monitoring Application Properties > Select Use Audit Database

•   Select Use Audit Database
• Save & Close

Step 6: - Restart the APS Server used by Monitoring or SIA

• Restart the APS Server being used by Monitoring
  • If you are NOT sure, restart the ALL servers using SIA

Step 7: - Validate the creation of NEW Monitoring Tables

• Validate the creation of Monitoring tables within Auditing Database, if you did NOT create the tables manually using the sql scripts
  • You have 4 – NEW tables created within Auditing Database schema
  • See below

Step 8: - Restore exported content to target Audit database

• Restore matching CSV file to matching tables crated in Audit database
• For more details please refer to your Database Administrator

While the CMC does allow some of the BI Launchpad preferences to be customized, the only attributes that can be set are in the preferences, General Panel.  This does not apply to preferences for the viewer or locale.

SAP has provided some code that can be added to your BOE deployment to resolve this.

SAP NOTE 1659566 - How to Apply Preferences to All Users Accounts in BI 4.0 (works for 4.x)

Download the zip file and extract the 2 files to tomcat\webapps\AdminTools

The utility clones a specified users preferences to all members of a specific group.  It is better to use a create a temporary user and set the preferences than to clone an existing user unless you have validated all of the setting for the specific user.

Check preferences for a user.

• Logon to Admin Tools
• run the following query
  select si_id, si_name, si_data from ci_systemobjects where si_kind = 'user' and si_name in ('userid', 'userid2')

The SI_DATA property bag only exists for users where the preferences have been changed in the BI Launchpad (or preferences were migrated from 3.1 InfoView).

To show users using default preferences run the following query in AdminTools

select si_id, si_name, si_data from ci_systemobjects where si_kind = user and si_data = Null

The user viewer preference for Webi is stored in the si_data property bag in the field si_data.document_WIViewTechno, valid values are I, H, P, and J

(I = 3.1 Interactive, H = 3.1 Web or 4.1 HTML, J = Java, P = PDF).  You can query to find the users for each viewer using the following query.

select si_id, si_name, si_data from ci_systemobjects where si_kind = user and si_data_documentWIViewTechno = 'P'

The si_data.documentWIViewTechno can not used in the where clause but not in the select.  Trying to select the field while result in no field being returned, to see the values, the full property bag si_data must be returned.

Comparison of Features by Version for the SAP BusinessObjects BI Platform

The components in the SAP® BusinessObjects™ Business Intelligence (BI) platform have evolved and continue to evolve rapidly. This document is a reference to help you understand when key features were introduced in the BI platform. This information should help you plan how to evolve your infrastructure, plan your upgrades, and deploy the right component to the right audience. This document covers the SAP BusinessObjects BI Suite and the Edge edition of SAP BusinessObjects BI software.

Although this document is not an exhaustive reference of every feature in the BI platform, we attempted to identify features that are important to most implementations. There may be features not described in this document that are important to your specific deployment.

This document does not replace the product availability matrix, which details the specific supported platforms for each release and support pack. These are available at service.sap.com/sap/support/pam. Please note: you need an authorised user ID to access this information.

The document presents you the list of features starting with SAP BusinessObjects XI3.1 up to BI4.1 SP05

View this Document

For the previous version containing XIR2 up to BI4.0 GA (version 4), please download the report here

Version History

Planned Updates

Additions planned for version 7 of the document are:

- Include/Update BI4.1 SP07 Features

- Include/Update Design Studio 1.6 Features

- Include/Update Analysis Office 2.x Features

- Include/Update Lumira 1.28+

Welcome to the October edition of the BI Platform SIG Newsletter.  The ASUG BI Platform SIG “brings together SAP customers to share best practices and real-world experiences implementing, supporting, and troubleshooting the SAP BusinessObjects solution portfolio”.   The BI Platform SIG is part of the ASUG Business Intelligence Community.  Join today.

Inside this issue:

• Upcoming Webcasts – We’re Listening
• Past Webcasts
• Call for Speakers for ASUG Annual Conference
• SAP Analytics & BusinessObjects Conference
• News you Can Use

Upcoming Webcasts – We’re Listening

Join us for these upcoming BI platform webcasts:

• Oct. 27: Sizing SAP BusinessObjects Enterprise - How a Sizing Exercise at Cardinal Health Made Drastic Performance Improvements(Customer Story)
• Dec. 2: BI4.2: Improved Collaboration Capabilities and Mobile Push Notifications
• Dec. 3: BI4.2: Improved Upgrade Process
• Dec. 7: BI4.2: Improved Migration Process
• Dec. 8: Deploying BI in the Cloud
• Dec. 9: BI4.2: Improvements in Managing the BI Platform

We heard you on our 2014 survey  - BI platform was a top priority.  On the survey you said you wanted more webcasts in this area.  The ASUG standard is 4 webcasts per year per SIG.

This year the BI Platform SIG has already held 5 webcasts this year with 6 more on the way:

For a complete list of upcoming ASUG BI webcasts click here.

Past Webcasts

Last month SAP provided an update on BI4.2 – to listen to the webcast, review the materials and question and answer click here.

SAP Analytics BusinessObjects Conference

If you missed the ASUG SAP Analytics BusinessObjects Conference, materials and presentations can be located here.  Save the date for next year’s conference October 18-20, 2016 in New Orleans

News You Can Use

SAP is offering BI Chat Support – for more information click here.

Free SAP BI Tutorials by SAP – click here

We hope you have enjoyed this newsletter. Comments and suggestions are always welcome. Be sure to join the BI Community here and the BI Platform SIG here.

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x as the runtime databases(CMS & Audit)

This document will explain, how to create database from Sybase Control Center.

The screenshot are attached for creating one of the db's (among cms/audit), same can be followed for other db.

The first part of could be found at the following location.

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part1

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part3

Thanks & Regards,
Vijay

I will continue with the installation of SAP Business objects on Sybase ASE.

Earlier we saw how to install Sybase ase and create the run time databases for SAP Business objects cms and audit.

In this we will see the actual installation.

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part1

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part2

Thanks & Regards,

Vijay

This document outlines the high-level steps for installing SQL Anywhere 12.0.1 for use with an SAP BusinessObjects Business Intelligence Platform 4.1 installation.

These steps were used while we were building out a performance testing environment for an upcoming Performance Testing Pattern Book for BI 4.1.  Once the Pattern Book is public, we will update this document with the link.

Ensure you are installing a supported CMS/Audit Repository Data Source

The first step is to ensure you are installing a Supported Platform for your BI 4.1 environment.

1. First check the Platform Availability Matrix (PAM), aka Supported Platforms Guide, for the BI 4.1 version you are installing.  Supported Platform Guides can be found at this link:http://help.sap.com/bobip
   
   
2. Navigate to Section 12 in the PAM to ensure your database version and Operating System are listed.  In our case, we are using Windows Server 2012 and Sybase SQL Anywhere 12.0.1.
   
   
   
   
3. For our Pattern, we used BI 4.1 Support Package 6.  We can see from the screenshot below that this is supported on Windows Server with using Sybase SQL Anywhere ODBC Driver 12.0.1.

We can now continue on with the Installation of Sybase SQL Anywhere 12.

Installing Sybase SQL Anywhere 12

This doc assumes you already have the install media available for the database you choose.  Below are the steps that we used during our installation:

1. Run Setup from the Install Media directory
   
   
2. Choose Install SQL Anywhere 12
   
3. Follow the Install Wizard prompts and choose your preferred options to kick off the installation
   
   
4. Once the installation is complete, you will have to carry out the steps in section 4.2 of the Installation Guide:
   
   BI 4.1 SP6 Install Guide
   
   
   1. Create a Database/schema and account for the CMS
   2. Create a Database/schema and account for the Auditing
   3. Ensure the database server is configured for Unicode character encoding (UTF-8)
   4. Ensure accounts have create, modify, and delete tables and to create stored procs
   5. Ensure client drivers are available for BI Platform servers
      
      
5. Be sure to check if there are “extra requirements” for the database you are using for the CMS/Auditing databases.  For SQL Anywhere, there are added requirements listed under section 4.2.4 of the install guide.
   1. Install SQL Anywhere client 12.0.1 on the CMS Machines - SAP SQL Anywhere Database Client Download
   2. Create an ODBC DSN connecting to the Primary Node SQL Anywhere CMS database
      
      
6. Create a User for the CMS and Auditing Databases (We used BICMSdba / BIAuditdba)
   
   
7. Create a Database for the CMS and Audit Database (We used BICMSDB / BIAuditDB)
   1. Ensure you use a page size of 8KB
      
      
8. Run these databases as a service on a particular port.  Doc:  http://dcx.sap.com/index.html#1201/en/dbadmin/running-sectb-3454334.html

That's essentially it!

Many a time I have worked on MTM and gone through many blogs, however I have never found the information about updating Database information for Crystal Reports.

We deal in the Airline industry wherein we provide the sets of standard reports to all of our clients. These sets of standard reports contain Crystal Reports. We use MTM to create tenants on BI4.1 servers. After creating a tenant we copy the standard reports and manually update the database information for Crystal Reports. This was a time consuming and difficult process for us until we found a way of automating this process by using MTM.

Please refer an informative blog Overview of SAP BI 4.x Multitenancy Management Tool by Christina Obry.

I was really not sure whether it works or not until I tried it in our environments and it worked for us as expected.

This document will describe all the required steps to use MTM in BI4.1 environments. Here, we will create a new tenant and will update the Crystal Report's Database information. We will also apply the security to the tenant using a template. I have used BI4.1SP04 and Oracle 11G DB to test this on Windows 2012 server.

Before running MTM command we will create the required templates as below:

1. Create the folder template as required:

  2.  Create the user group templates:

  3.  Assign Access Rights as required on the template folders:

    4.  Copy the required Crystal Reports 2013 to one of template folders:

Now, we will configure the template configuration file:

This file can be found at the location: <BI installed path>\java\apps\multitenancyManager\jars\tenant_template_def.properties.

NOTE: Do not modify this file, take the backup and rename this file to the tenant name something like "TestMTM_def.properties". You can rename this file to anything you want. File name should always contain the string "_def.properties". I have renamed this file as "TestMTM_def.properties".

Here are the contents of this file:

1. Speciy the tenant name: tenantName= Test[PROD] (This can be anything you like.)
2. Specify the template token: $tenant_template$ (This is nothing but a template name what we have created in CMC, root folder of the template.)
3. Specify the logon information of the BO server where you want to create this new tenant.
4. reviewBeforeProceed=true (This option will review all paramters specified in this properties file, always keep this true.)
5. tenantConcurrentUserLimit=100 (This option is to distribute the license deployed on the same BO server. You can chnage the value as required.)
6. statusLog=E:\BOADMIN (This will be loggin directory where the MTM logs will be stored. We will discuss this later in detail.)
7. abortANDRollback=true (Always keep this true, if anything goes wrong with MTM then it will revert all the changes it has done while creating a tenant.)
8. templateContentFolder=$tenant_template$ (This should be a root folder of the template folder structure.)
9. Now, we will specify the database information for all of the Crystal Reports.

NOTE: "crystalreport.templatedb" will be the database information of the crystal reports what we have in the template folders. "crystalreport.tenantdb" will be the database information of the new tenant which will be created by MTM. I have removed the DB information what I have used in our environments for this activity. If you have mutiple CR reports using multiple DB information then you would need to mention all of them in the following manner. We had only two DB information specified for all of the CR reports. We have to ensure that the BO server can communicate with all of the DB servers we are going to use in the following DB information.

E.g.

crystalreport.templatedb1=templateserver;templatedbname;odbc;administrator;password

crystalreport.tenantdb1=tenantserver;tenantdbname;odbc;administrator;mypassword

I have used following two database information in this file.

Let's discuss about how to specify this DB information for CR reports.

1. crystalreport.templatedb1 and crystalreport.tenantdb1 => You would need change the number (1) to specify multiple DB information. E.g. crystalreport.templatedb2, crystalreport.tenantdb2 and so on.

1. templateserver and tenantserver => This would be data source name of the CR reports. To find this, go to the database configuration of CR reports from CMC as shown below.

                             iii.  templatedbname and tenantdbname => would be a database name if you have specified any on the CR reports as shown                                                         below highlighted in red.

                              iv. odbc => This would be a database server type, I have used oracle DB so I have mentioned oracle in the screenshot above.

                                                  Valid database server types are odbc, oracle, db2, sybase, informix, crdb_xml.

                              v. administrator;password and administrator;mypassword => This would be database usernames/passwords for the template and

                                   tenant's CR reports.

                              vi. Save the properties file.

Time To Run MTM command:

Command: java -jar multitenancymanager.jar -configfile TestMTM_def.properties -tenantName=Test[PROD]

The output of the above command will be shown as below if everything goes well with MTM.

After the successful execution of the above command, it will create the following objects.

1. CMC->Multitenancy.
   

    2. Created Folder Structure.

     3. Copied all CR reports to the new folder "Test[PROD] Ad Hoc Reports".

     4. Replicated access rights on the tenant's folders from template folders.

              
    5. Updated DB information on the CR reports:

        NOTE: You would find that all new CR reports are using Custom Database logon information.

Points To Note:

1. MTM will not move any report from the template folder structurte to the new tenant folder structure. It will copy all the CR reports in the new tenant's folder.
2. BO server where we will use MTM should be able to communicate with all the DB servers i.e. all DB servers what we have specified in the properties file.
3. Table prefix can also be updated using MTM, however I have not mentioned that in this document.
4. To increase the memory for MTM, use the parameter below in the command.

               Parameter: -XX:MaxPermSize=512m

               Command: java -XX:MaxPermSize=128m -jar multitenancymanager.jar -configfile TestMTM_def.properties

Troubleshooting:

1. Enable tracing by creating a BO_trcae.ini file as below. Please note that few parameters are changed for this file which can be found in the admin guide.

     2. Logs will be generated the location "BOInstallDIR\SAP BusinessObjects Enterprise XI 4.0\logging" as multitenancymanager_XXXXXXX_trace.glf. This            file can be opened using a notepad or notepad++.

     3. You can also check the CSV file generated by MTM while creating a new tenant. This file would be created at the location what we have mentioned in           the properties file, here it was "E:\BOADMIN". This CSV file will contain the information about all the objects which would be created during the           creation of the new tenant.

     4. Please check the KBAs: 1955167 and 2072040.

MTM Workflow:

1. It will first review the properties file.
2. Will check all the templates created in CMC.
3. Will look for the objects placed in the templates.
4. Will fetch all the objects from the templates.
5. Will copy/update the objects in the new tenant's folders.
6. Will refresh the DB information for the reports.

More with MTM:

1. We can also update the Crystal Reports for Enterprise, WEBI reports, universes(UNX and UNV), relational connections.
2. There are some limitations for updating UNX and UNV using MTM.

To Know More About MTM: Please refer this guide.

I hope this document would be helpful.   I am really not good with the formatting still I have given my best today

You have two options:

Options 1: (Exiting BI 4.0 w/ SP4+ Install, migrate Derby Database)

If you have existing data in your Derby trending database, you will need to migrate the Derby database to the auditing database, and then configure the BI platform to record monitoring information in the auditing database. These are the high-level steps you'll need to follow. For details, see the related topics.

• Migrate the Derby database.
• Verify that the auditing database is working, and auditing is running properly.
• Create the monitoring tables in the ADS (optional).
• Configure the SBO files and add alias names.
• Switch to the auditing database.
• Restart the Adaptive Processing Server that hosts the Monitoring Service.
• On the Monitoring Dashboard, ensure that everything works as expected. Verify that these monitoring tables have been created in the database:
  • MOT_MES_DETAILS
  • MOT_MES_METRICS
  • MOT_TREND_DATA
  • MOT_TREND_DETAILS
• Restore Derby Database

Option 2: (New BI 4.0 w/ SP4 Install, No Data in Derby Database)

If you do not have data in your trending database, that is, you have a fresh installation, you do not need to migrate the database; you only need to configure the BI platform to record monitoring information in the auditing database. These are the high-level steps you'll need to follow.

• Verify that the auditing database is working, and auditing is running properly.
• Create the monitoring tables in the ADS (optional).
• Configure the SBO files and add alias names.
• Switch to the auditing database.
• Restart the Adaptive Processing Server that hosts the Monitoring Service.
• On the Monitoring Dashboard, ensure that everything works as expected. Verify that these monitoring tables have been created in the database:
  • MOT_MES_DETAILS
  • MOT_MES_METRICS
  • MOT_TREND_DATA
  • MOT_TREND_DETAILS

Step 1: Migrate existing Derby Database

Logon into CMC > Application > Monitoring Application Properties > Export

For best results Export Data to CSV. If you a cluster BI Platform environment then export data from most heavy used server environment and you should only import the data from one Derby instance. Importing data from multiple Derby instances will result in data inconsistency and is therefore not recommended.

Date will be export in CSV format to the default location of the Derby Trending Database folder, located in \SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB.  This is also the same location of all the database scripts to create the tables manually (optional).

BEFORE EXPORT:

AFTER EXPORT:

The following four CSV files are generated in the default Trending Database location; each CSV file is a representation of each table to be created in the monitoring DB:

• DerbyMot_Mes_Details.csv
• DerbyMot_Trend_Data.csv
• DerbyMot_Trend_Details.csv
• DerbyMot_Mes_Metrics.csv

Step 2: Verify Auditing Database Working Properly

Launch MS SQL Server Management Studio to validate Auditing database have been created properly

Step 3: - Create Monitoring Tables manually (Optional)

Use the SQL Scripts provided by BI Platform install to create the monitoring tables manually, location

\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Data\TrendingDB\

Step 4: - Configure SBO Files

Internally, the Monitoring application uses Connection Server libraries, and the SBO configuration is required for the Connection Server to establish connectivity to the database driver. You need to specify the database driver and its location in the SBO file to establish this connectivity, file location is <Install_Dir>\dataAccess\connectionServer\odbc\<dbType>.sbo

• If the database used for auditing is SAP HANA, the file where the driver needs to be configured is: newdb.sbo
• If the database used for auditing is MS SQL Server, the file where the driver needs to be configured is: sqlsrv.sbo
• For more details on other database type refer to The Platform Administration Guide, location http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp4_bip_admin_en.pdf
• Below is an example of changes MUST be made to ALL MS SQL 2008 / 2012 / 2014 database

BEFORE:

AFTER:

Step 5: - Switch Monitoring to Auditing Database

Logon into CMC > Application > Monitoring Application Properties > Select Use Audit Database

•   Select Use Audit Database
• Save & Close

Step 6: - Restart the APS Server used by Monitoring or SIA

• Restart the APS Server being used by Monitoring
  • If you are NOT sure, restart the ALL servers using SIA

Step 7: - Validate the creation of NEW Monitoring Tables

• Validate the creation of Monitoring tables within Auditing Database, if you did NOT create the tables manually using the sql scripts
  • You have 4 – NEW tables created within Auditing Database schema
  • See below

Step 8: - Restore exported content to target Audit database

• Restore matching CSV file to matching tables crated in Audit database
• For more details please refer to your Database Administrator

Webinars covering all things important for BI projects. Register for upcoming sessions or watch recordings of past events.

Technical Webinar Series: SAP BusinessObjects BI Platform 4.x

Once again will we provide a series of free webinars that are focused on upgrading to the SAP BI Platform 4.1. This webinar series is a supplement to other information assets found on SCN.

Webinar title, date, registration and presenter information is given below - all webinars will start at 7am PDT, unless otherwise specified. Webinar dates and times may be subject to change.

• Registration links: will be enabled a few days before the scheduled webinar date.
• Recordings: will be posted no later than a week after the event.

If you 'follow' this page, you will receive notifications of any updates, including new webinar content, dates and registration links - also recordings of all completed webinars will be made available from this page. Stay Tuned !

Upcoming Webinars - Registrations		Date	Presenter
	SAP Analytics - Integration of SAP BI Platform with SAP Design Studio	Nov 24	HJ
	Gain insight into your BI Platform with new Auditing Universe and Reports	Dec 08	MS
	SAP BI Platform Support Tool 2.0 - Improved administration and Supportability	Jan 19	TJ
	Data Federation Admin Tool – Tuning Execution of Multi-Source Universes	Feb 16	SP
h
Recordings of Past Webinars		Date	Presenter
	What's new in SAP BI 4.2 (recording | pdf)	Oct 27	ME
	UNX Adoption - Planning & Execution (by APOS Systems) (recording | pdf)	Sep 29	FW,HJ
	Creating Relational Connections for SAP BI 4.1 for Reporting on SAP BW (recording)	Aug 04	JR
	User Authentication and Single Sign-On with BI 4.1 (recording)	Jul 21	GDL
	Sizing your BI Platform, using the SAP Sizing Tool (recording)	Jul 07	HJ
	What's new in BI 4.1 SP6 (recording | presentation)	Jun 23	ME
	Best Practices for WebI (recording)	Jun 23	JB
	A guided Tour: How to best make use of Online Resources (recording)	May 18	HB
	BI 4.1 Monitoring - (Recording)	Nov 13	TJ
	Troubleshooting - (Recording)	Nov 06	GS
	Promotion Management & Version Management - (Recording)	Oct 23	MS
	WebI Calculation Engine Changes - (Recording)	Oct 16	PG
	DeskI to WebI Conversion & Desktop Compatibility Pack - (Recording)	Oct 09	ME
	Upgrading from XI Release 2/3.1 to 4.1 and updating From BI 4.0 to 4.1 - (Recording)	Sep 25	ME
	User Authentication & Single Sign-On - (Recording)	Sep 11	TZ
	BusinessObjects BI Strategy & Roadmap - (Recording)	Sep 09	JL
	Installation & Patching - (Recording)	Sep 04	HJ
	Deployment Best Practices - (Recording)	Aug 29	HJ
	Sizing & Virtualization - (Recording)	Aug 14	CL
	Update Best Practices - (Recording)	Jul 30	SR
	Value Prop & Tools - (Recording)	Jul 17	HB

Comparison of Features by Version for the SAP BusinessObjects BI Platform

The components in the SAP® BusinessObjects™ Business Intelligence (BI) platform have evolved and continue to evolve rapidly. This document is a reference to help you understand when key features were introduced in the BI platform. This information should help you plan how to evolve your infrastructure, plan your upgrades, and deploy the right component to the right audience. This document covers the SAP BusinessObjects BI Suite and the Edge edition of SAP BusinessObjects BI software.

Although this document is not an exhaustive reference of every feature in the BI platform, we attempted to identify features that are important to most implementations. There may be features not described in this document that are important to your specific deployment.

This document does not replace the product availability matrix, which details the specific supported platforms for each release and support pack. These are available at service.sap.com/sap/support/pam. Please note: you need an authorised user ID to access this information.

The document presents you the list of features starting with SAP BusinessObjects XI3.1 up to BI4.1 SP05

View this Document

For the previous version containing XIR2 up to BI4.0 GA (version 4), please download the report here

Version History

Planned Updates

Additions planned for version 7 of the document are:

- Include/Update BI4.1 SP07 Features

- Include/Update Design Studio 1.6 Features

- Include/Update Analysis Office 2.x Features

- Include/Update Lumira 1.28+

Hi,

This blog describes how to create a query snapshot in SAP BW, which creates a SAP HANA index on that query snapshot.

How to do this?

• Run Transaction RSDDB in the SAP BW system and enter your SAP BW query name and click on Release Query as InfoProvider.

• This launches the index maintenance screen where you select the table and click on Activate and Fill Index. After activating and filling the index is completed, Index Status will appear as green.

• Log on to SAP HANA Studio to import the query as a snapshot that we created in the earlier step.

• Import the SAP NetWeaver BW model by clicking File > Import. On the Import screen, click the SAP HANA Content folder, and choose the Import SAP NetWeaver BW Models option.

• Select the connection and provide a Username and Password to login to the SAP NetWeaver BW system to import an SAP NetWeaver BW model> Click Next.

• Select the Target folder where you want to import SAP NetWeaver BW models by entering the Target Package on the screen.

• Import BW Query "DEMO_QUERY_03" snapshot and click "Next". Note that imported models will be created as an SAP HANA model (analytic or calculation view) under the Target package sap.bw.

• Once you have imported SAP BW Query as Hana View, you can check newly created SAP Hana View under Content > sap.bw

• Make sure to apply "Analytic" privileges to assign BW analytics roles.

After the import of the query as a snapshot as SAP HANA views, these views can be exposed to SAP BusinessObjects Explorer or SAP Lumira for business users to search and explore on the SAP NetWeaver data.

Caveats

• Since you are creating snapshot of your SAP BW Queries in SAP HANA database, this means you are using additional Hana memory to save these datasets.
• Furthermore creation of indexing on SAP BW Queries to be scheduled on daily basis to have recent data.

This page provides an overview of the available What's New Materials for the SAP BusinessObjects BI4.x Suite

SAP Lumira

• What's New in SAP Lumira 1.16 (summary)
• What's New in SAP Lumira 1.17 (summary)
• What's New in SAP Lumira 1.18 (summary)
• What's New in SAP Lumira 1.19 (summary)
• SAP Lumira 1.19: What's new in SAP Lumira
• What's New in SAP Lumira 1.20 (summary)
• SAP Lumira 1.20: What’s new in SAP Lumira
• What's New in SAP Lumira 1.21 (summary)
• SAP Lumira 1.21: What's new in SAP Lumira
• What's New in SAP Lumira 1.22 (summary)
• SAP Lumira 1.22: What's new in SAP Lumira
• What's New in SAP Lumira 1.23 (summary)
• SAP Lumira 1.23: What's new in SAP Lumira
• What's New in SAP Lumira 1.25 (summary)
• SAP Lumira 1.25: What's new in SAP Lumira
• What's New in SAP Lumira 1.27 (summary)
• What's New in SAP Lumira 1.28 (Summary)
• What's New in SAP Lumira 1.29 (Summary)

SAP BusinessObjects BI4.2 What's New Slides

• SAP BusinessObjects BI4.2 What's New L0

• SAP BusinessObjects BI4.2 What's New L1
• SAP BusinessObjects BI4.2 What's New L2

SAP BusinessObjects BI4.1 What's New Slides

• SAP BusinessObjects BI 4.1 What's New L1 | SCN
• SAP BusinessObjects BI 4.1 What's New L2 | SCN
• SAP BusinessObjects BI4.1 SP3 What's New | SCN
• SAP BusinessObjects BI4.1 SP4 What's New | SCN
• SAP BusinessObjects BI4.1 SP05 What's New | SCN
• SAP BusinessObjects BI4.1 SP06 What's New | SCN

Client Specific Content

• BI4.1 What is New in BusinessObjects Analysis, Edition for OLAP - Part 1
• BI4.1 What is New in BusinessObjects Analysis OLAP Part 2
• Web Intelligence 4.1, what's new?
• BI 4.1 Ramp-Up Knowledge Transfer Live Expert Session Schedule
• SAP BusinessObjects BI4.1 Explorer New Features - More Details
• What is new with SAP Integration BI4.1 and SAP ERP?
• What is new with SAP Integration BusinessObjects BI4.1 and BW? Part 2
• What is New with SAP Integration with BusinessObjects BI4.1 and BW - Part 3
• What is new with Web Intelligence BI 4.1 – Part 1, Developer Support ASUG Webcast
• What is new with Web Intelligence BI 4.1 – Part 2, Core Capabilities
• What is New with Web Intelligence BI4.1 - Part 3 - Data Source Enhancements
• What is New with Web Intelligence BI4.1 - Part 4 with Question & Answer

SAP BusinessObjects BI4.1 What's New Recorded Presentations

• What's New in SAP BusinessObjects BI4.2 (L1) video
• SAP BI4.1 SP4 & 5 technology update | myBrainshark
• What's new in Web Intelligence 4.1 SP5 (1:40)interactive / video
• What's new in Web Intelligence 4.1 SP4 (1:10)interactive / video
• What's new in Web Intelligence 4.1 SP3 (1:37)interactive / video
• What's new in Web Intelligence 4.1 SP2 (3:02)interactive / video
• What's new in Web Intelligence 4.1 (5:27)interactive / video

SAP BusinessObjects BI4.0 What's New Slides

Client Specific Content

• BI 4.0 New Features and Changes - Business Intelligence (BusinessObjects) - SCN Wiki

SAP BusinessObjects BI4.0 What's New Recorded Presentations

• Concept - What's New in SAP BusinessObjects Web Intelligence 4.0 - YouTube
• What's New in SAP BusinessObjects Web Intelligence 4.0 Feature Pack 3: Web Intelligence 4.0 FP3 - YouTube
• Concept: What's New in SAP BusinessObjects Web Intelligence 4.0 SP5: Web Intelligence 4.0 SP5 - YouTube
• What's new in Web Intelligence 4.0 SP5 (2:04)interactive / video
• What's new in Web Intelligence 4.0 Feature Pack 3 (4:20)interactive/ video
• What's new in Web Intelligence 4.0 (6:25)interactive /video

SAP Crystal Solutions 2013

• What's New in SAP Crystal Solutions 2013

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x as the runtime databases(CMS & Audit)

This document will explain, how to create database from Sybase Control Center.

The screenshot are attached for creating one of the db's (among cms/audit), same can be followed for other db.

The first part of could be found at the following location.

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part1

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part3

Thanks & Regards,
Vijay

I will continue with the installation of SAP Business objects on Sybase ASE.

Earlier we saw how to install Sybase ase and create the run time databases for SAP Business objects cms and audit.

In this we will see the actual installation.

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part1

SAP Business objects 4.1, SP-04 installation, Using Sybase ASE 16x - Part2

Thanks & Regards,

Vijay

Hi All,

I just want to share my experience which may help to many BI folks to resolve their issues when create or running webi Reports. Due to unsupport java we may can see below error.

"Unspecified error invoking method or accessing property "onChangeDocID"

Replication steps: Logged on and selected the Webi  Icon, select Web Intelligence Document, select Universe, Looked at universe list to make sure I didn’t see any restricted universes.  Selected universe and created a new Webi report.  When I ran the report, may get above error, however, as you can see report data did return but when select close of X out of the error, report will disappears.

Cause: Unsupported java Version

Resolution:

Update java version later to Java 1.0.7_51

Reference Note: Same issue mentioned in the below SAP note: 1933283 - Error: "Unspecified error invoking method or accessing property "onChangeDocID" " when refreshing a new WebI report after choosing query elements.

Issue will be no longer occurred after Java version 7 update 45 .

But in you case you are in Java Update 51. Hence i would request you to clear the Java cache and try the same flow.

To clear java cache:

Navigate to control panel --> Java --> On general tab --> Temporary file settings --> Delete files --> ok.

Restart browsers and retest.

Hope this helps.

Thanks

Venky

Hi All,

I would like to share my experience how to overcome CMC login issues due to port issues.

When may require to add static request port for CMS for specific reasons. For ex: when setup multi domain config for promotion management. When we enter wrong/conflict port at the request port or named space port, we can not login CMC at all and we will get below error.

We can not login to CMC to revert back the ports we entered. So below is the alternative way to revert back your port changed for the specific servers in the CMC. Here I am showing for CMS as it will be the show stopper for the CMC.

For ex: if I gave the request port as 6401 as below.

Actual request ports should be 6408 or 6409 or from 6411 based on the network settings.

Also when maintaining request port make sure select the "name server port" with "user default settings" rather than with 6400.

So to revert back navigate to the application server C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\ and modify “_boe_hostname.bootstrap” file proper ties by comparing existing working version if any.

Wrong port maintenance tag looks like as below: (this may vary based on the server or port or any other reason. Best way to compare this file whole code with working environment).

• <property flags="0" name="SI_ARGS" type="String">-startedBySIA -requestport 6408 -port 6400</property>

then change it to original version to login back to CMC and then give the desired valid port. (Recommended)

• <property name="SI_ARGS" type="String" flags="0"/>

or if you want to set correct ports here itself update as below.

<property name="SI_ARGS" type="String" flags="0">-startedBySIA -requestport 6408</property>

Hope this helps.

I gave very high level, please feel free to ask if any clarifications in this.

Thanks

Venky