In the past few months I had the chance to implement a solution based on the combination of SAP BusinessObjects Explorer and mobile devices. The challenge was: “I want to explore the same information that I see on my dashboards with SAP BusinessObjects Explorer on my iPad. In this particular case, some of the customer`s dashboards were really complex and we had to deal with many issues.

Today I would like to share with you how we solved one of these issues: How to implement row-level security into a space of Explorer? The solution to this challenge cannot be based in any case of security implemented at universe level, in SAP BO Explorer the information of the spaces is retrieved when we index the space, this means that any kind of security applied at universe level will have a direct impact when we index the space. Manual Para Carburador Bocar 2 Gargantas Del.

What we needed was a space with all the information but able to be filtered on demand based in some personalization rules. With SAP BO Explorer 3.2 we are able to generate and apply this kind of security by creating two spaces: one reference space with all the possible information to explore and one personalized, where we will be able to filter the information displayed on demand based on the rules of personalization and making use of the reference space. Definition of the scenario To be able to follow the implementation of the solution, assume that we start from: • SAP BusinessObjects XI 3.1 installed and fully operational • SAP BusinessObjects Explorer 3.2 installed and fully operational To make it easy to follow I will make use of the eFashion universe and we will need to create users in BO according with the list of values of Name of Manager dimension ( Store ->Store Details->Name of manager).Note that the name of the users should be exactly the same as the values of the dimension. We will create a new space based on the eFashion universe information. The personalization rule is that the Store managers will have access to the space but they will only be able to see the information related to their Store(s).

Creating the e-Fashion Reference space First open SAP BO Explorer and login with administrator credentials.

Platform BOE 4.1 on Windows There is a limit of 90 characters for the SI_Name of an object to be translated using Translation Manager. When an object is first published to BOE, the name of the object in the input filestore is set to a combination of the internal ids of object in the CMS database.

How To Install Efashion Universe Sandbox. I am planning to install Patch 11 but would be glad to fix the. Today when I run. Blog Torrent Alison Moyet. Today Downloads: 7. Bedside Clinics in Surgery, 2nd Edition. How To Install Efashion Universe Sandbox Game.

When the object is exported from translation manager back to the CMS, the name of the object in the filestore becomes the si_name of the object and the guid. If the si_name exceeds the 90 character limit, the filename in the CMS will not match the name of the file in the input FRS. When a user tries to run the report, the report can not be accessed and the object appears to be corrupt. If this happens, • go to the filepath shown under the object properties and get the file You may need another resource to get the file if you do not have access to the server • Open the object in the design tool • Republish the object to the CMS. • Before using Translation Manager, shorten the name to be less than 90 characters.

• DO NOT DELETE the un-accessible object until it has been republished. This document helps the user to migrate CMS DB from SQLAnywhere to HANA Database where BOE is installed in Linux/Unix environment. To make it simple I have divided the migration into two phases where Phase 1(Configuration Phase) deals with the configuring the required settings for migration and Phase 2(Migration Phase) deals with the actual migration.

Phase 1: Configuration Phase In this phase we install the HANA client, configure the DSN, which is explained in detail below. Step 1: Install HDB Client in the machine where BOE is installed. Step 2: Using the below command copy libodbcHDB.so file from HDB Client directory to linux_x* directory. Cp //sap_bobj/enterprise_xi40/linux_x64/ cp //sap_bobj/enterprise_xi40/linux_x86/ Step 3: Add the details of HANA server in odbc.ini which is present in /sap_bobj/enterprise_xi40/ Below is the screenshot, which has details of HANA driver echo $ODBCINI Note: Output should be: /sap_bobj/enterprise_xi40/linux_x64/ Phase 2: Migration Phase In this phase, we perform the actual migration using cmsdbsetup.sh script. Step 1: Run cmsdbsetup.sh script present in /sap_bobj/./ cmsdbsetup.sh Step 2: Specify the name of the node and press enter.

In this example 'lnxsuse11x64' is the name of the node. Step 3: You need to stop the node before migration so select option 3 to stop the node.

Step 4: Select option 4 'copy' for Database Copy(by default it will be 'update'). Step 5: It will show a warning message that this operation will deleted BIP tables in destination DB. Select option 3 'Yes'(by default it will be 'No') Step 6: It will prompt whether you need current DB(SQLAnywhere) as destination database.

You need to select option 2 'No'(by default it will be 'Yes') Note: If you choose yes it will delete all BIP tables from current DB. In this our destination DB is HANA so select option 2.

Step 7: Select option 8 “SAP HANA” as destination database. Step 8: Enter the ODBC DSN for connecting HANA DB(This values should be same as values entered in odbc.ini file). In this example “Hana_Migration” is DSN name for HANA DB.

Step 9: Enter User Name for connecting HANA DB. Step 10: Enter Password for connecting HANA DB. Step 11: Enter CMS Cluster Key. Step 12: Now you need to specify Source CMS database.

In this case you need to select option 2 “SQLAnywhere”. Step 13: Enter the ODBC DSN for connecting SQLAnywhere DB(This values should be same as values entered in odbc.ini file). In this example “BI4_CMS_DSN_” is DSN name for SQLAnywhere DB. Step 14: Enter User Name for connecting SQLAnywhere DB.

Step 15: Enter Password for connecting SQLAnywhere DB. Step 16: Enter CMS Cluster Key. Step 17: Data successfully migrated to HANA DB. Step 18: You can see CMS tables in HANA DB using HANA Studio.

As we know that BEx query condition is not working in dashboard report, then how condition can put on keyfigure to get Top-N or Bottom-N values, for this webi report can be created for Top-N and Bottom-N No of values with rank formula and same can access in dashboard using web service. Below is the step by step process. 1) Create BEx query report as per requirement.

2) Create webi report on Bex query for Top 15 Customer by using Rank function. A) Create webi report on Bex query(in my example it consist of Customer id, name and there turnover of the month) b) Right click on turnover column and Add Ranking. C) Now desire output of Top Ten Customer will get as below, saved the webi report on BI platform.

3) Create web service on webi report. A) Select report table properly and right click then ‘Publish as Web Service’ then Next b) Click on next and check for Filter prompt which we use for Filter in dashboard. C) Define Publish content(Name and description) for web service d) Create or select existing web service to publish new content to as web service. E) Now web service has been created successfully, you can see it in ‘Web Service Publisher’ Panel at the left side. The content of web service would access through WSDL URL Link refer below screen shot.

4) Open dashboard report and Add connection (Query web service) to web service.(Click on Data and then Add Connection in menu bar or Click on manage connection in tool bar and then select Web service query(Query as web service). In the WSDL URL box, Paste WSDL URL and click on import button.

5) As per below screen shot, two block Input Values and Output Values are shown we need to provide values in ‘Input values block’ and take output values from ‘output value block’, refer below screen shots and bind input block with excel cell in which required value is given like login id, password, required prompt value, resetState (resetState and refresh are used for refresh data on selection prompt values) and Also bind output block with Excel cell to taking web service values like Header, footer and Table values. 6) Please check ‘Refresh Before Component are Loaded’ check box and check when value changes option button and bind Trigger cell with Excel, so whenever the value is changed new data is refresh from Web service. 7) Drag and Drop Dashboard components and bind it with Excel cell as per requirement and execute. Thanks, Kashif Ali Khan. What is PHASE-WISE? Phase-wise installation of BI 4.2 installer You can now perform the installation of BI platform 4.2 in two phases - Caching and Installation after caching.

During caching the system downtime is eliminated, which reduces the overall system downtime.This will save your time and more importantly if you have issues in INSTALL-DATA folder or any files or any issue which may arise during the update because of Cache will be minimized and your main server update will be unaffected. Pre-requisites before proceeding: • Ensure you take the necessary backup of CMS database and Filestore for safe side using KBA-1275068 - Backup and restore BusinessObjects Enterprise XI 3.x / BI 4.x system from one environment to another. • Follow BEST practice KBA- 1952120 - SAP BusinessObjects (XI 3.1 and BI 4.0) Installation pre-requisites & best practices / KBA-1757132 - BI4 Support Pack Upgrade and Patch Install Best Practice Guide • Download the correct setup for SAP BusinessObjects Business Intelligence (BI) platform UPDATE from Support and Patches section in SMP ( Service Market Place) • Applicable for BI 4.2 Installers and should not be tried with BI 4.0/4.1 products. • VERY IMPORTANT: If updating the Server from BI 4.1 ensure to check the licensee policy and requirement using link: Step by Step Update using Phase-wise installation method in BI 4.2 • Navigate to command prompt ( Elevated Mode: Run as Administrator ) & Enter the location where the software is downloaded. • Enter the setup.exe -cache.

• Here I have Created 'phaseresponse' folder for it: setup.exe -cache c: phaseresponse response.ini In the Installation wizard window, review the instructions displayed. 'In the License Agreement window, review and accept the license agreement. In the New License Key Requirement window, review the contents of the New License Key Requirement, and select the check box I have read the documentation and understand the process to request the new license key, and agree to add the new license key after update installation, and choose Next Note When you update your system from Business Intelligence Platform 4.2 SP1 or earlier versions to Business Intelligence Platform 4.2 SP2 or higher versions, the existing licenses behave as invalid licenses. You need to request a new license key for Business Intelligence Platform 4.2 update from SAP Service Market Place, visit For more information on how to request a new license key, visit ' After you update your system to Business Intelligence Platform 4.2 update, you must logon to Central Management Console; delete the old license key and add the new license key. Alternatively, you can run the script to delete the license keys.

For more information on how to delete the license key through the script, see SAP Note 227613 Until you add the new license key in Central Management Console, certain servers are in disabled state. Once you add the new license key, navigate to Servers window, enable those servers which are in disabled state.

For more information, see Business Intelligence Platform Administrator Guide • In the Existing CMS Deployment Information window, enter the CMS Logon Administrator Information password. • Start Installation window apperars, To start caching, choose Next. • Caching completed successfully screen appears.!!!

Please note this Windows will be minimized in Task Bar So Please check it or it will appear that installer is hung' During the caching process the system downtime is eliminated and servers can be up and running during this process and no changes to done. Step by Step Starting the update: • Once the response file is generated and caching is done then you can follow the Best practices KBA mentioned in the Pre-requisites. THIS WILL REQUIRE THE DOWNTIME AND UPDATE STRATEGY WE FOLLOW' • Navigate to the directory where response.ini file is located. • Edit and Enter the Remote CMS Administrator Password and save the response.ini file. • Navigate to command prompt.Enter the location where the software is downloaded.

• Enter the setup.exe -resume_after_cache. • Here I have Created 'phaseresponse' folder for it: setup.exe -resume_after_cache c: phaseresponse response.ini • In the Resume installation window, choose OK In the Post Installation Steps window, follow the instructions and choose Next The installation of SAP BusinessObjects Business Intelligence Platform 4.2 update is completed successfully. Note ● You can experience the system downtime only during the installation after caching, hence the overall system downtime is reduced.

● After you start the installation, the installer repairs any errors that occurred during the caching and proceeds with the installation. Introduction Are you new to SAP BusinessObjects Business Intelligence (BI)? Or are you looking for a fast and easy way to find the answer to you BI questions?

Then this guide is for you. New to SAP BI What is BI? These tutorials have been developed to help you get started using Business Intelligence products. New content is added as it becomes available, so check this site for updates. Where to download BI products?

You can download SAP BI product’s Support Packages and Patches here. Where are BI-related documents? The Analytics Knowledge Center lets you search for files related to a specific product, or a specific release, or a combination of product and release. Multiple languages versions are available.

What is Service Market Place (SMP)? – One Support Launchpad? The Service Market Place (SMP) hosts the Support Portal, Help Portal and other useful content.

The One Support Launchpad is also available. What is the Support Portal?

– One Support Launchpad Here you can • search for SAP Notes, Knowledge Base Articles; • request a license key; • create incidents and check your inbox; • read SAP Spotlight News, etc. The One Support Launchpad is also available. How to get a license key for a BI product? You can request a license key or get a temporary license key here: For problems when requesting or creating a license key, you can create an incident using component XX-SER-LIKEY-BOJ. Self-service What is the BI Platform Support tool?

The BI Platform Support Tool is a Java-based utility used by support engineers, consultants, and BI administrators. It simplifies the process of reporting on the landscape configuration, performing root cause analysis, and delivering performance optimization and go-live services. Please always remember to provide this information to SAP Support when you create an incident. Where to find Product Available Matrix (PAM)?

Product Availability Matrix: The following KBA contains links to all the PAM documents for BI Products. Where is the SAP BI Forum?

The BI Forum contains useful blogs, answers to questions from other customers, and useful localized documents. When you have a question about BI products, this is the best place to start. How to troubleshoot on my own?

Would you rather try to solve an issue on your own, rather than creating an incident? With ‘Troubleshooting by Scenario,’ you can. This allows you to follow exactly the same steps and methodology that a SAP support engineer or developer would follow to isolate the issue.

How to size your system to improve performance? Sizing means determining the hardware requirements of an SAP solution, such as network bandwidth, physical memory, CPU power, and I/O capacity. SAP’s Sizing Guide provides recommendations and best practices to help with deploying and scaling the various services in SAP BusinessObjects BI 4. Also included are information and details about the sizing tests and the methodology used to create the various sizing tools and documents in support of BI 4. What would you do when you meet a third-party product error? Apache Tomcat, a free open-source third-party web application server, is not an SAP product.

SAP recommends you contact a qualified third-party vendor or consultant for problems such as performance tuning, OutOfMemory issues, or not being able to start or stop Apache Tomcat. The other third-party products used by BI are also supported as the similar way. Where to check SAP BI Product’s Support Package and Patch schedule? Here you will find the information on the Maintenance Strategy and Schedule for BusinessObjects Enterprise XI 3.1 and BusinessObjects BI Platform 4.x. While please be aware that the information contained in this schedule is subject to change. SAP BusinessObjects does not guarantee the availability of a delivery on the specified date.

The delivery frequency of a product version may change during its lifecycle. How to handle the security vulnerabilities? When a third-party tool such as WebInspect or AppScan has been pointed at a deployment of an SAP Business Objects product, (XI R2, XI 3.1, BI 4.x etc) and the resulting report shows a number of security vulnerabilities (such as Cross Site Scripting), you could refer to the following SAP KBA to see the responsibilities of SAP engineers and the customer. Where to submit a product enhancement request? To request a new feature or product enhancement, SAP has defined a new process and a new tool that is now available to customers called Idea Place. Idea Place allows customers to log Enhancement Requests themselves and work more directly with our technology and Development group. Creating an incident How to use chat with BI Support in real time?

SAP is now offering chat support for specific product components. For these, you can always use chat to contact SAP Support in real time. What is the SAP Customer Interaction Center’s hotline number? What’s the difference between Support and Consulting? When you have a consulting request, you can use SCN BI forum or consulting service. What’s the criteria for Very High priority incident?

An incident should be categorized with the priority 'very high' if the problem has very serious consequences for normal business processes or IT processes related to core business processes. Urgent work cannot be performed. This is generally caused by the following circumstances.

- A productive system is completely down. - The imminent system go-live or upgrade of a production system can't be completed. - The customer's core business processes are seriously affected. - And for each circumstance a workaround is not available.

How many questions can I ask in one incident? There should only be one question per incident. This ensures that you get speedy assistance for each problem you may be having. Different questions can be addressed separately by different engineers specialized in different areas.

Why do SAP Support engineers ask how to reproduce an issue? SAP Support engineers need to reproduce the errors in order to be able to find a solution. This is the only way to find out what is happening in the code. If the issue cannot be reproduced, you may find out some information on the SAP SCN Forum. How to do a remote screen-share session with SAP Support? SAP Support uses Citrix GoToAssist to perform remote sessions with customers.

How to perform a remote support? There are many remote support types according to different situation, such as HTTP connection, WTS connection, BW specific connection. Your system needs to be configured according to the notes below to benefit from remote support. In the event of a problem, you can create an incident using component XX-SER-NET.

Our engineers from the Network team will help you. Administrator Cockpit – • If the administrator want to get a fast insight about the BO systems.

• With the new SAP Business Objects BI platform 4.2, administrators can now view some basic information about the BI environment in real-time using the BI Administrator’s cockpit application that’s available in CMC. Currently you can view information about Servers, Scheduled Jobs, Content Usage, and Applications. • Note - This application is not supported in Internet Explorer. Servers Tile – • Servers tile displays the total Servers that are available and the number of server that are running, failed, or stopped. • On clicking the servers tile user will be navigated to detailed server page with all the servers state and the last modified date. Scheduled Jobs Tile – • Scheduled Jobs tile displays all the jobs that are running, success, or failed, and you can filter the tile for a specific time (i.e. Today, Last 7 Days, Last 30 days, Quarter, or Year).

• On clicking the scheduled jobs tile user will be navigated to detailed jobs page which shows status of all the jobs. Content Usage Tile – • Content Usage Tile displays the total content that is active or Inactive in your BI Platform, i.e.

It shows the no. Of reports or dashboards that are active or inactive. Users can filter the tile for a specific time (i.e.

Today, Last 7 Days, Last 30 days, Quarter, or Year). Application Tile – • Application Tile displays the no of artefacts by each application type, and similar to other tiles you can filter the tile for a different time ranges. Webinars covering all things important for BI projects. Register for upcoming sessions or watch recordings of past events.

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. This document helps the user to migrate CMS DB from SQLAnywhere to HANA Database where BOE is installed in Linux/Unix environment. To make it simple I have divided the migration into two phases where Phase 1(Configuration Phase) deals with the configuring the required settings for migration and Phase 2(Migration Phase) deals with the actual migration.

Phase 1: Configuration Phase In this phase we install the HANA client, configure the DSN, which is explained in detail below. Step 1: Install HDB Client in the machine where BOE is installed. Step 2: Using the below command copy libodbcHDB.so file from HDB Client directory to linux_x* directory. Cp //sap_bobj/enterprise_xi40/linux_x64/ cp //sap_bobj/enterprise_xi40/linux_x86/ Step 3: Add the details of HANA server in odbc.ini which is present in /sap_bobj/enterprise_xi40/ Below is the screenshot, which has details of HANA driver Note: ServerNode Value should be ServerNode=:315 echo $ODBCINI Note: Output should be: /sap_bobj/enterprise_xi40/linux_x64/ Phase 2: Migration Phase In this phase, we perform the actual migration using cmsdbsetup.sh script. Step 1: Run cmsdbsetup.sh script present in /sap_bobj/./ cmsdbsetup.sh Step 2: Specify the name of the node and press enter. In this example 'lnxsuse11x64' is the name of the node.

Step 3: You need to stop the node before migration so select option 3 to stop the node. Step 4: Select option 4 'copy' for Database Copy(by default it will be 'update'). Step 5: It will show a warning message that this operation will deleted BIP tables in destination DB.

Select option 3 'Yes'(by default it will be 'No') Step 6: It will prompt whether you need current DB(SQLAnywhere) as destination database. You need to select option 2 'No'(by default it will be 'Yes') Note: If you choose yes it will delete all BIP tables from current DB. In this our destination DB is HANA so select option 2. Step 7: Select option 8 “SAP HANA” as destination database. Step 8: Enter the ODBC DSN for connecting HANA DB(This values should be same as values entered in odbc.ini file).

In this example “Hana_Migration” is DSN name for HANA DB. Step 9: Enter User Name for connecting HANA DB. Step 10: Enter Password for connecting HANA DB. Step 11: Enter CMS Cluster Key. Step 12: Now you need to specify Source CMS database.

In this case you need to select option 2 “SQLAnywhere”. Step 13: Enter the ODBC DSN for connecting SQLAnywhere DB(This values should be same as values entered in odbc.ini file).

In this example “BI4_CMS_DSN_” is DSN name for SQLAnywhere DB. Step 14: Enter User Name for connecting SQLAnywhere DB. Step 15: Enter Password for connecting SQLAnywhere DB. Step 16: Enter CMS Cluster Key. Step 17: Data successfully migrated to HANA DB. Step 18: You can see CMS tables in HANA DB using HANA Studio.

Hi Everyone, There have been situations where we may need to remove SAP Business Intelligence (BI) 4.0/4.1/4.2 from the Server machine and you may be not able to remove it from PROGRAMS AND FEATURES or clean the registries etc. Below are the possible reasons when you wanted to remove BI: • Installation went wrong or terminated and you wanted to do a fresh install again.

• Unable to remove the product from Programs and features of Windows Control Panel. • Due to binary corruptions of BI Server like Install Data Problems, Corrupted etc. • You have installed many service packs updates / patches and you wanted to clean it and install only targeted pack. • For Example: BI 4.0 SP6 (Full Build) >updated>BI 4.0 Sp12 >updated>BI 4.1 Sp6 >updated>BI 4.1 Sp6 Patch3 >updated>BI 4.1 SP7 and you wanted to remove BI and install only BI 4.1 Sp7 (Full Build) on the server to save disk space.

Etc We use KBA: 1691555 - How to manually remove SAP Business Intelligence (BI) 4.0/4.1/4.2 Manually from Windows Server to remove it and performing the KBA very precisely and accurately is one of the important point. So I have create a Script (Batch +vbs) which we will do the job automatically and it will be Cleanup Utility for BI. Products will be removed: • This script will remove all the product associated with SAP BI with Add-on or Component installed on the server where script is running. • SAP BusinessObjects Business Intelligence Platform 4.0 • SAP BusinessObjects Business Intelligence Platform 4.1 • SAP BusinessObjects Business Intelligence Platform 4.2 • Crystal Reports 2011 • Crystal Reports 2013 • Crystal Reports 2016 • SAP BusinessObjects Explorer, Data Services, Live Office or any Add-on which is associated with SAP BusinessObjects • SAP BusinessObjects Business Intelligence Platform Clients Tools • If you are using CUSTOM Database present on another server it will not affect it and do any operation on it.

Same is applicable for the FILE-STORE on Network Location. • If you are using Distributed or Clustered combination it will not affect other system. It will remove the content on the local server where the script is executed. Pre-requisites: • Take the backup of the necessary files/customizations present in SAP BusinessObjects SAP BUsinessObjects Enterprise XI 4.0. • Default Filestore: SAP BusinessObjects SAP BUsinessObjects Enterprise XI 4.0 Filestore (OPTIONAL and Asked in theScript) • Default Database (If using SQL Anywhere): SAP BusinessObjects sqlanywhere database • Default Tomcat: SAP BusinessObjects Tomcat • Stop all the services if you are cleaning a running SAP BI 4.x • Check if any process is running in the task manager and kill if present related to Business Objects. • Ensure you have Administrator rights as this will clean registries and files under Windows Installer folder. Finally Remove BI: • Download the Script: • Extract the two files #RemoveBI.bat and #CleanupBI.vbs into any folder.

• Open Command Prompt in Elevated Mode (Administrator) • Run RemoveBI.bat and it will ask you to continue. • It will ask you to take the backup of Default File Store If you have already taken the backup hit N or if you wanted to take backup hit Y. Here I have used option YES = Y. • Then it will ask you for the DRIVE where you wanted to take the backup. Example: E:, F:, etc. Here I have use C: Drive to take the backup. • After completion of Backup it will automatically start to DELETE the services for Default Tomcat, SQL Anwhere Service, Subversion ( If present if not then exception of error is acceptable since the service will not there) • It will Automatically detect the INSTALLATION FOLDER of SAP BI and start deleting it.

• Now it will take the backup of the FULL Registry and place it in the USERS Profile. After that it will start to delete the Registry Keys for 'SAP BusinessObjects'. • Once Completed it will start to Remove the Files associated with BI in Windows Installer • Next and Final Step to remove all the Registries from the computer associated with BI in Current users and Local Machine. IT MAY TAKE A WHILE • Don't worry about the 'ERROR: The system was unable to find the specified.' Message it is to cross check in loop if the registry is deleted or not.

• Once the script is completed Simply reboot the server and you have a fresh machine of windows server where bi was not installed. ============================================================================================================ ============================================================================================================ Disclaimer: This script is the property of SAP and should not be used in any form commercially. Free for non commercial use only redistribute is forbidden. This script to help the customer and in case of any issues SAP or I will not be responsible any damage or unusual behaviour of script. Cheers, Mahak Rathore. Summary While installing BusinessObjects BI Platform 4.x you do not have an option to choose SAP HANA as CMS database even from 4.0 SP4 it already supported SAP HANA as CMS database. But it is possible to change or migrate CMS from one database to another one after installation, the Administrator Guide has a section that describes what you need to do to select SAP HANA as the CMS database.

This Step by Step Guide demonstrates how to change/migrate CMS from default database (MS SQL Server or SAP Sybase SQL Anywhere) to SAP HANA. Note that below procedure is only for Windows and applies to BusinessObjects BI Platforms 4.1 SP1. Preparation In addition to BusinessObjects BI Platform 4.x, SAP HANA database you also need SAP HANA client and SAP HANA Studio. There is guide Step by Step Installation SAP BusinessObjects BI Platform 4.x available if you need. You can download client and Studio from the. Please ensure you use same version of client, studio and database. Step 1: Create HANA users and add systems Assuming that you have administrative rights on your HANA database, create two new users BOE141 and BOE141_Audit which will own the CMS and Auditing tables.

Also add two systems using these two users on SAP HANA Studio. • Enter the host name, instance number of your HANA database also description then click on Next to continue • Enter the user name and password for the CMS database you just created then click on Next to continue • Click on Finish. Now you successfully add a new system 4. Add second system with user for Auditing database, on SAP HANA Studio will look like this Step 2: Create a System ODBC Data Source Name for HANA You don't have to create ODBC Data Source now since you can create later when you choose ODBC Data Source • Launch ODBC Data Source Administrator. Ensure you launch the 64Bit version ODBCad32.exe from location%Windir% System32 if you installed 64Bit version SAP HANA Client.

Otherwise you can just launch 32Bit version one form Control Panel ->Administrative Tools • Select System DSN tab then click on Add to create ODBC Data Source. Select HDBODBC driver from the driver list then click on Finish to continue • Enter Data Source Name, Description and Server: Port for CMS then click on OK You can click on Connect then enter user name and password to test connection • Create ODBC Data Source for Auditing database following the same steps. ODBC Data Source Administrator window will look like this Step 3: Stop SIA from CCM In order to change CMS database you have to stop Server Intelligence Agent(SIA) from Central Configuration Manager(CCM) first. SAP BI Platform 4.2 brought along lot of additional features with its release. Additional drivers for Apache Spark, Recycle Bin, BI Commenting solution and the new Admin cockpit are few to mention. If you have missed the awesome presentation from SAP, read If you are doing a fresh install, you would be presented a screen where you get to choose the features you would need. But upgrade does not work the same way.

Some of the features comes built in which will be installed as applications or activated as web applications when the upgrade redeploys the new applications. By default SAP Upgrade installers will update only the existing features that you have enabled to ensure stability in the system. So what you would need to do if you need to activate the new features?

Read on to find out. Active new features For features that does not come bundled and require additional step, you would need to enable them manually. This involves the server going down during the phase, so treat it as maintenance downtime.

• Navigate to the “Program and features” applet from the Control panel. You can also use the shortcut to directly launch it from the run with the command “appwiz.cpl”.

Siemens Lotus 12p Hearing Aid Manual. • You will find individual entries for the SAP BI Platform base along with patch updates installed. Update install will be append with “update” This is similar for the BI Platform Add-ons like Design Studio and Lumira • Right click on the base entry and select “Uninstall/Change”. Do not worry as it would not uninstall the platform. • It would take some time depending on the system and you would see the Installer Setup running with three options.

Select modify and proceed to Next • Select your preferred language. It would usually show the languages that you had selected when you installed the base version. Continue with the next screen. • The next screen is where our focus should be. It lists the set of features that are already present in the system. You also get an option to select the features that you need.

The unchecked box represent the features that are not installed and the checked box represent the features that are already installed. Select the features you would need to install (i.e. Apache Spark).

Click on next to proceed for the installation. The setup detects existing installation and like any upgrade it would take some time for the feature to get installed.

Once the installation is completed. You can now start using the feature that you had enabled. In one of my previous documents i have written several words about the version.

Of course this document is not complete, since it is not contains all the possibilities of the timeout settings. In this document I am giving guideline for SAP BusinessObjects Live Office users to check/troubleshoot timeout errors of the application.

Before you do any changes in the timeout settings, we have to answer minimum the following questions: • What is the BI Platform version? Is the Live Office application version the same as the BI Platform version? SAP BusinessObjects Business Intelligence Platform version must be the same as SAP Live Office version. Different versions use different backend processing methods. SAP BI Platform 4.x has 2 different workflows when working with Live Office documents: • version 4.0 and 4.1 up to SP5 P5 uses the dswsbobj web application • from version 4.1 SP5 P5 and version 4.2 uses the RESTful web service • What is the proper error message when we facing timeout issue?

The root cause of various different error message can be timeout. Some examples: • 'The operation has timed out.' • 'An error occurred when the report is refreshed. Detail: the operation has timed out' • 'Unknown error (0x8013500)' • 'GetDocumentInformation exception (Error: WRE 99999) The operation has timed out.' • 'Failed to upgrade this document (LO 01400) - Invalid pointer' • What business workflow is being executed by the user when the error message displayed?

'Refresh All' objects workflow requires more time and effort for each the client application (preparing and displaying prompts) and also for the server application (to execute all the reports) than r efresh a single Live Office object; of course requires a different troubleshooting steps. Also important to understand the technical process of the Live Office application, since different settings are related to different tiers and requires different places to perform these settings. Understanding the technical process Let's review the technical process.

I would go for the following example: when refreshing a single object, which is a part of an existing WEB Intelligence report. The interactive version can be found in the following document: As you see, each tier is affected in the refresh process, and there are different setting for timeout for each tiers.

• The client tier the Live Office application itself, which is connects to the web server via the:/dswsbobj/services/session url. • The Web tier, the web server (tomcat) forwards the request to the Web Application Server and creating an enterprise session after the CMS successfully validated the given credentials for the connection. • Now the process can continue on 2 different ways, pending on the BI Platform version. If you are using BI Platform 4.1 SP5 P5 or newer, the Web Application Container Server will process the requests of Live Office application via RESTful service, and calls the WEB Intelligence processing server to refresh the report.

As we have 3 different tiers in the technical process, we can modify the timeout properties for each 3 different one. Before we go for the details, please note the golden rule: Keep it simple! To modify a timeout without modification of other parameters not always not solves the issue. Example: increasing a Live Office application timeout more than a enterprise session timeout is not a valid case in production environments, since the session will expire earlier than the Live office application would reach the timeout value, but this technique is candidates for troubleshooting without generating traces about the full workflow. Timeout settings in Live Office application The Live Office application installed on client PCs and used as an Addin in the Microsoft Office applications (Excel, Word, Powerpoint, Outlook), in windows environment, and the timeout value stored in the windows registry, so can be modify via the registry editor.

To do this change, you need local administrator rights on the windows machine. This timeout is valid for a single operation step started from the Live Office application, and it is defines the maximum waiting time of the Live Office client application between to server calls. The default value for this timeout is 600 seconds, so 10 minutes.

Steps to change the DefaultTimeOut value: 1. Open the registry ( Start ->RUN ->Type regedit). Locate the following path: - for a specific user: HKEY_CURRENT_USER Software SAP BusinessObjects Suite XI 4.0 Live Office ENTERPRISE - for all users on the same machine: HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node SAP BusinessObjects Suite XI4.0 Live Office ENTERPRISE 3. Create (if not already exist) a new DWORD key named DefaultTimeOut 4. Set the default timeout (Decimal) value to 3600. The value is in seconds, which is 60 minutes so basically it is the same as enterprise session logon token timeout of the WACS server. After restarting the MS Office application ( Excel, Word, Powerpoint, Outlook) the new timeout value will be used from the client side.

If there are have more than one Live Office client application installed on your environment, you must do this change on all the effected machines. Timeout settings for WEB services If the client side timeout setting was not solved the problem, and there is continuously the timeout error message displayed in Live Office client application, as a next step at the web tier, the Web Server, Web Application Server and Web Application Container Server (WACS) timeout can be increased. • The web server (by default tomcat) is responsible for the connection handling especially communication response times between Live Office client and Web Application Servers. • Under the Web Server several web applications are deployed.

One of these is the dswsbobj, which is responsible for the sessions, as also for the session timeouts. • The Web Application Container Server serves the RESTfull service, which handles and process the data, communicates with the other BI servers such as WEB Intelligence processing server (when a WEB Intelligence document or Universe is the data source) or Crystal Processing Server (when the data source is a crystal report). Connection timeout for tomcat servers When refreshing a large document in Live Office, or the data source has large number of prompts or prompt values, the technical workflow can be timed out at the point, when the Live Office application tries to send the request to the web server, and waits for the response. This waiting time can be customized by a parameter called connectionTimeout in tomcat server configuration file.

To change this timeout value, follow these steps: 1. Go to conf server.xml 2. Change ' connectionTimeout' to 600000. This value is in milliseconds, which means 10 minutes. The value in must be milliseconds, and the Connector will wait, after accepting a connection, for the request URI line to be presented. Use a value of -1 to indicate no (i.e.

Infinite) timeout. The default value is 60000 (i.e. 60 seconds) but note that the standard server.xml that ships with Tomcat sets this to 20000 (i.e. Unless disableUploadTimeout is set to false, this timeout will also be used when reading the request body (if any). Restart Tomcat in Central Configuration Manager In this example screenshot i have set the timeout ot For more information, you may reffer to the following link: Session timeout in Live Office process flows In BI Platform, the web application dswsbobj is first web application which handling calls of the Live Office application requests,so the session timeout parameters can be defined in the dsws.properties. The file at tomcat webapps dswsbobje WEB-INF classes on windows machines. To change the Live Office session timeout follow these steps: 1.

Open file dsws.properties on the path: SAP BusinessObjects Tomcat webapps dswsbobje WEB-INF classes 2. By default there is no session.timeout parameter in this file. You can insert one line to the end of the file like: session.timeout=3600 3. Save the file and restart the web server. The session.timeout value is in seconds, so 3600 seconds is 60 minutes, which is the default value enterprise session logon token timeout. From BI Platform version 4.1 SP5 P5 this value will be passed to the RESTful service as a session timeout.

For WACS timeout settings please look the following document:. Section Logon token timeout. Summary There are various options to extend the live office application timeouts on client also on server side in SAP BusinessObjects Business Intelligence Platform. To start, i suggest to take the easiest options, first change the Live Office client application timeout which helps you to narrow down to the root cause of the issue. Please note: changing the BI server configurations, manipulating session timeouts can cause unexpected behaviors in other applications such as dashboards or WEB Intelligence Rich Client which are using the same mechanism.

Dear all, Recently we released 30-day free trial library of SAP BusinessObjects Business Intelligence (BI) Platform 4.1 SP6 and SAP BusinessObjects Business Intelligence Platform 4.2 SP2, which can be accessed from the SAP Cloud Appliance Library(CAL)( ). The trial library has been preconfigured and can be deployed instantly to the Amazon Web Service(AWS: ) cloud. You can evaluate these SAP Business Intelligence libraries and not worry about setting up and configuring them. You can also utilize Amazon VPC, which enables your BI solution to access your own corporate data center. To subscribe these library solutions, you need an SAP CAL account and an AWS account.

Accessing the SAP Cloud Appliance Library is always free of charge and the library already contains a 30-day temp license. But there is a fee for the infrastructure costs of AWS.

If you fit into one of the following categories, this Free Trial BI version is exactly for you: a. You are not familiar of SAP Business Intelligence and you want to try it and see how it works b. You are already running a previous BI version and you plan to upgrade to BI4.1 or BI4.2 c. You want to see if some issues have been fixed in recent BI release Now why are you still waiting? If you are not familiar with SAP Cloud Appliance, you can refer to: • SAP Cloud Appliance Library - SCN Homepage: • SAP Cloud Appliance Library - FAQ.