Provisioning a Amazon Web Services instance for SAP BusinessObject BI4.x

This document is part of the series Getting Started with SAP BusinessObjects BI4.x on AWS

You can provision an Amazon Web Services (AWS) instance by selecting a system meeting your sizing requirements as defined in an earlier steps. If you have not yet defined a sizing for your SAP BusinessObjects BI4.x deployment on AWS, please start reading the sizing guidelines available on : BI@AWS 01 : Sizing you SAP BusinessObjects BI4.x system for AWS Deployments

Provisioning a Amazon Web Services instance for SAP BusinessObject BI4.x
- Prerequisites:
- Provisioning an AWS Instance

Prerequisites:

An Amazon Web Services account
Note: When you create an account, you are automatically signed up for all AWS services. However, you will only be charged for the services you use.
Go through the SAP BusinessObjects What's New Collection to gain insight in what your best version is.
Understanding the support of deploying an SAP BusinessObjects BI4.x system on AWS as documented in http://service.sap.com/sap/support/notes/1656250
A sizing estimate as defined in BI@AWS 01 : Sizing you SAP BusinessObjects BI4.x system for AWS Deployments
Recommended : Setup your Virtual Private Cloud (VPC) connector. The VPC is recommended by Amazon, setting up a VPC is described in the document from SAP HANA ONE (AWS VPC setup) however the steps are equal for any SAP deployment.

Provisioning an AWS Instance

Create your VPC (AWS VPC setup) or reuse one you already have in place
Ensure you selected the correct region to where you want to deploy your image
Within the homescreen of AWS, select EC2 for the creation of a new instance
Select "Launch Instance" to startup a new instance
Select the operating system of your choice which is supported by the SAP BusinessObjects BI version of your choice. To validate supported Operated Systems, please check the Product Availability Report via : https://apps.support.sap.com/sap/support/pam

For the example, a Windows 2012 R2 Base system will be deployed
Select the required instance size. the instance size is key for running a well performing BI4.x deployment and is recommended to be memory optimized. For understanding the translation of Instance Types, please ensure you have executed a correct sizing and translation of ECU into SAPS as described in Sizing you SAP BusinessObjects BI4.1 system for AWS Deployments

For this example I'll deploy the BI4.x system against the memory optimized r3.2xlarge model.
Select "Next: Configure Instance Details" as the next step (not "Review and Launch") as we have a few more configurations to take care of during initialization

Within the Configure Instance Details ensure you select the following items correclty
- Network : Select the VPC as created for step 1
- Subnet : if you have instances within AWS, ensure you select the same subnet if you want to connect into these AWS instances as well
- Auto-Assign Public IP : Recommendation is to disable the auto-assign mode as it is recommended to work with a Elastic IP (default auto assigned IP's can changed after restarting your Instance).. We will later assign a Elastic IP to the system
- Shutdown Behavior : Leave this to Stop, unless you want to have the instance terminated at shutdown (all data will be lost)
- Optional : Enable Termination Protection
- Optional : Enable Monitoring (note: additional costs are involved)
- Optional : Enable EBS-optimized instance (note: additional costs are involved)
- Optional : Select you instance to be Dedicated (note: additional costs are involved)
- Optional : Enable the request for Spot Instances
Select "Next: Add Storage" as the next step (not "Review and Launch") as we have a few more configurations to take care of during initialization

By default a new image is create with a 30Gb Disk. To ensure enough diskspace is available for the deployment of SAP BusinessObjects, we need to add additional capacity.

In the example setup, we'll create / enhance the following disks:
- Increase capacity in the default disk to 80Gb
- Add new disk with a capacity of 128Gb (for installing SAP BusinessObjects and future updates)
- Add new disk with a capacity of 64 Gb (for storing the Windows Page File)
Note : adding disk capacity influences the costs of your AWS Instance
Select "Next: Tag Instance" as the next step (not "Review and Launch") as we have a few more configurations to take care of during initialization

In this example setup, We'll not going to add Tags. for details on how to use tags, please read : Tagging Your Amazon EC2 Resources - Amazon Elastic Compute Cloud
Select "Next: Configure Security Group" as the next step (not "Review and Launch") to enter the final detail for your initial Instance Creation

Security Groups will configure the firewall settings for your Instance. for details on Security Groups, please read : Amazon EC2 Security Groups for Linux Instances - Amazon Elastic Compute Cloud. To enable access into the BI Launchpad and Central Management Console of the BI Platform, we have to enable access to the port for the Web Application Server. For enabling communication by the BI Platform into other server hosted within AWS we potentially need to configure the ports for BIP communications.

In this example setup, we create a new security group "BI42" and enable the port 8080 (as we will use the default Tomcat) as well as a port range (6400-6599) for future inter-AWS communication.

Enabling port 8080 or 3389 (RDP) for "Anywhere" is not recommended, but for the sake of the example deployment currently used. Typically you want to have your organizations External or Internal IP ranges being enable for these ports, which can be set via "Custom IP"

The BIP Port Range is being assigned to the IP Range as used by the VPC as being defined in step 1
We are now ready with the initial setup of the Instance and van hit the "Review and Launch" button. This will provide us the overview of settings applied during the previous steps. Review your settings and when OK, "Launch" your image to become created.
During the launch, you will be requested to select an existing key pair of create a new one. The Key Pair is required to connect into your system. for details around the AWS Key Pair, please read : Amazon EC2 Key Pairs - Amazon Elastic Compute Cloud

In this example setup, we'll create a new Key Pair "BI42@AWS" and download the file to the local machine for later use.
After creating / reusing a Key Pair, You'll be able to launch you instance.
You are informed about the Launch Status and by selecting View Instance, you will be directed to the EC2 Instances listing to validate the progress
Check if the instance is initializing
Once Initialized, a public IP has to be assigned to enable the remote access.
As we selected not to assign a public IP, the instance cannot yet be reached from outside AWS.

for deploying the instance against a Public IP and connecting with remote desktop (windows OS), please continue with step 3 in the process available via : BI@AWS 03 : Connecting to an AWS instance for SAP BusinessObjects BI4.x

Back to the Main Page for Deploying BI4.x against Amazon Web Services

Connecting to an AWS instance for SAP BusinessObjects BI4.x

This document is part of the series Getting Started with SAP BusinessObjects BI4.x on AWS

You can connect to an Amazon Web Services (AWS) instance by selecting a system meeting your sizing requirements as defined in an earlier steps. If you have not yet provisioned an AWS Instance for your SAP BusinessObjects BI4.x deployment , please start reading the provisioning guidelines available on : BI@AWS 02 : Provisioning a AWS instance for SAP BusinessObjects BI4.x

Connecting to an AWS instance for SAP BusinessObjects BI4.x

Prerequisites:

An Amazon Web Services account
Note: When you create an account, you are automatically signed up for all AWS services. However, you will only be charged for the services you use.
Go through the SAP BusinessObjects What's New Collection to gain insight in what your best version is.
Understanding the support of deploying an SAP BusinessObjects BI4.x system on AWS as documented in http://service.sap.com/sap/support/notes/1656250
An up and running AWS Instance meeting the requirements as described in Provisioning a AWS instance for SAP BusinessObjects BI4x
The Instance ID as received in the previous step
Recommended : Setup your Virtual Private Cloud (VPC) connector. The VPC is recommended by Amazon, setting up a VPC is described in the document from SAP HANA ONE (AWS VPC setup) however the steps are equal for any SAP deployment.

Assign Elastic IP:

Have your AWS Image up and running in your preferred region
Note the fact that no Public IP has been assigned in the sample setup. If you have a public IP assigned, please validate if this has been defined as a Elastic IP. In case you have no Elastic IP assigned, your Public IP may change after restarting your Image, driving potential issues while connecting into your SAP BusinessObjects environment. Additionally it is not recommended to have the SAP BusinessObjects BI Platform (BIP) being deployed against a dynamic IP, as BIP has bindings with the IP.
To assign a static public IP, we have to create a Elastic IP.
for information about the Elastic IP, please check : Elastic IP Addresses - Amazon Elastic Compute Cloud

Creating an Elastic IP can be done via the menu bar on the left under -> Network & Security -> Elastic IPs
Navigate to "Elastic IPs" and select "Allocate New Address" to start the creation of an Elastic IP
You will get a confirmation IF you want to allocate a new IP. Select "Yes, Allocate" to generate a new Elastic IP
Note: Creating Elastic IP's without using them will result in an additional charge
Your Elastic IP is generated and can be assigned to your Instance

The IP created will be listed under your Elastic IP's
Now having the Elastic IP created, we can assign this to our Instance, enabling a fixed IP for usage outside AWS. To assign the IP to you Instance, select Action -> Associate Address
Select the Instance ID from your system and confirm via "Associate"
If we move back to the EC2 screens, we will see that the Elastic IP has been assigned to the Instance

Connecting to AWS Instance running Windows

Now that we have assigned a public IP to the AWS Instance, we can connect to the AWS instance using Microsoft Remote Desktop

Before connecting to the Windows Instance, we need to set an Administrator password to enable a logon. To decode the Administrators password from the key file generated during instance a few steps are required. If you have already set your Windows Password, please continue with step 5

- Select the instance you want to retrieve the Windows Password
- Navigate to Actions -> Get Windows Password
Choose the key pair file as stored while creating the instance
Once the Key Pair is loaded, the value will be visible, select "Decrypt Password" to get the Windows Password
The Windows Password is shown, note down to password or copy this for later use
Start your Remote Desktop via your preferred path :
- Start -> Run -> mstcs.exe
- Start -> All Programs -> Accessories -> Remote Desktop Connection
- Start -> Run -> Remote Desktop

Enter the IP Number as recorded for the Public IP of you Instance
On the Credentials Screen, enter you credentials to connect to the AWS Windows Instance. Please note to connect with .\Administrator to force the use of the local authentication model within the AWS Instance
Depending on your security settings, a security popup may appear

Accept the warning (and if preferred select the tickbox "Don't ask me again for connections to this computer")
You can now work on your AWS Instance and start the installation of SAP BusinessObjects BI4.x. Please continue with : Deployment and Configuration of BI4x on AWS

Connecting to AWS Instance running Linux

To be added

Back to the Main Page for Deploying BI4.x against Amazon Web Services

SAP BusinessObjects BI4.x is being certified and supported for deployments on Amazon Web Services (AWS). Via this document we provide you with all the steps to deploy SAP BusinessObjects BI4.x on a Amazon Web Services hosted system.

Amazon Web Services (AWS)

AWS is currently available in various geographic locations:

US
- East (North Virginia)
- West (Oregon)
- West (N. California)
EU
- Ireland
- Frankfurt - Germany)
Asia Pacific
- Singapore
- Tokyo
- Sydney
South America
- São Paulo

for the latest list of locations, please check Global Infrastructure

It is strongly recommended to select a AWS location nearby your (organizations) datacenter / datasource to reduce a potential performance impact due to network latency.

Before deploying SAP BusinessObjects BI 4.4, please read the SAP Note around SAP Application on AWS: http://service.sap.com/sap/support/notes/1656099

		STEP 1: Sizing Sizing requirements Sizing for AWS Sizing Recourses
		STEP 2 : Provisioning Log into your Amazon Web Services (AWS) Account Select Instance Type Create EC2 Instance Launch and Configure Instance
		STEP 3 : Connect and Roll-Out Assign an Elastic IP Address Connect to Instance
		STEP 4: Deployment and configuration of SAP BusinessObjects BI4.x Download SAP BusinessObjects BI4.1 Installer Run Installer Configure SAP BusinessObjects BI4.1 Connect SAP BusinessObjects BI4.1 Client Tools

		STEP 5: Connect to SAP HANA One (AWS) Create SAP HANA One Instance Create SAP BusinessObjects BI4.1 Connection to SAP HANA One (to be added)

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

SAP Cloud for Analytics

What's New in SAP Cloud for Analytics - January 2016

SAP Lumira

SAP BusinessObjects BI4.2 What's New Slides

SAP BusinessObjects BI4.1 What's New Slides

Client Specific Content

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 BusinessObjects Design Studio

SAP Crystal Solutions 2013

What's New in SAP Crystal Solutions 2013

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

Overview

Top Online Resources

Tutorials

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 BI Platform Support Tool 2.0 - Deep Dive with the Expert	Jan 19	TJ
	Data Federation Admin Tool – Tuning Execution of Multi-Source Universes	Feb 16	SP
h
Recordings of Past Webinars		Date	Presenter
	Gain insight into your BI Platform with a new Auditing Universe and Reports (recording)	Dec 08	MS
	SAP Analytics - Integration of SAP BI Platform with SAP Design Studio (recording)	Nov 24	HJ
	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

More Webinars: SAP Lumira | SAP Predictive | EPM | SAP Design Studio | Web IDE

This is a brief, step by step demonstration of BI Recycle bin: new functionality introduced from BI 4.2.

First step is to enable the application. To do that you will need to navigate to Applications from CMC.

Important: Right click Recycle bin Application and select properties. By default, Recycle bin functionality is off. i.e You will need to check the following Enable recycle bin and configure automatic remove files according to you need.

Now, once a user deletes a document it should show up in recycle bin.

Once done you should get a response like. Once restored the file will move to its original location similar to what happens in Windows systems.

Important links/ references:

All documents relating to BI 4.2: SAP BusinessObjects Business Intelligence platform 4.2 – SAP Help Portal Page

Recycle bin documentation available in BI 4.2 Admin guide.

NOTICE: All forward looking statements made by SAP are subject to change

Thanks to SAP's Maheshwar Singh, we had an active question and answer on yesterday's ASUG webcast

Question & Answer

Q: How often are the Developer teams using SAP Idea Place to look at Customer Requests and Votes..?

A: Maheshwar does that quite frequently

Q: Support for MS-OFFICE 2016 will be available soon..?

A: Evaluate that - PAM document will be updated when certified.

Q: Design Studio Audit data is not like the data captured for Webi and Crystal, will that be enhanced?

A: Yes, that is true, idea is to improve all auditing going forward including Design Studio

Q: Writing alerts using the expression language in CMC Monitoring is extremely cumbersome just to check if a system is online/offline ; and the interface is complex; any change this will be simplified?

A: Need to rethink; find it complex; rather do administrative type monitoring that easy to use - evaluating a proposal; perhaps include in the influence council

Q: Will Audit data be enhanced to capture meaningful data for duration_ms (to capture more of the components duration) and for Design Studio and other addins?

A: For Design Studio, yes begin capturing - next version of Analysis Office will be audited. Lumira, no, but next version of Lumira should support auditing.

Q: Will you be providing any standard content (universes, canned reports etc) for BusinessObjects auditing? Similar to BW Statistics

A: See this: Unlock the Auditing database with a new Universe and Web Intelligence Documents for BI4.1

Q: Can you share a link where we can participate in influence council for this aspect? (admin cockpit, etc.)

A: CEI is now closed; please consider joining - POST data or see https://influence.sap.com/BusinessObjectsBIPlatform2016

Q: We currently have BI41 with Design Studio 1.6, after the upgrade to BI4.2 do we need to reinstall DS1.6 for 4.2?

A: Looking at introducing new license key for 4.2 if you go with that route may need to reinstall otherwise no impact - depends on proposal

Q: Has a release date for 4.2 been announced yet?

A: Looking at tentative timeline of end of Q1 or early Q2 - need to meet KPI's for rampup

Q: Admin cockpit has longest running reports or jobs? If either...can you drill down to details to where it is taking the most time?

A: Not at this time. Trying to see if case log files - seeing if feasible.

Q: Is Administrators Cockpit configurable? - Where are RunTime stats coming from - auditdb ? cmsdb?

A: Not in 4.2; doing some ideation with customers to find out what would like to configuration

Q: Although the recycle bin is in the CMC does it catch documents that are deleted by Launchpad users?

A: Yes, any content that is part of the public folder is caught by recycle bin - plan to include recycle bin for launchpad users

Q: Will there be any enhancements for Design Studio on BI platform, especially in the area of bookmark administration & folders?

A: BI platform is choice for Design Studio going forward. Commentary in future coming. Bookmark admin - some discussions happening; not closed

Q: Will the new BI platform customer connection program influence BI4.3? Will there be a 4.3? https://influence.sap.com/BusinessObjectsBIPlatform2016

A: Good question - Customer Connection - not 4.3 really, could influence SP for 4.2. First SP's may include customer connect request or SP after. There will likely be a 4.3 but still don't have 4.2 out the door. Under discussion

Q: Does Lumira for BI platform work with BI4.2 or is it dependent on a certain platform?

A: The current version 1.29 w/ SP3 now supports BI 4.2

Q: When will all the "hidden" FLASH Browser Dependencies in CMC and Launchpad be REMOVED from those interfaces..?

A: 4.2 remove flash dependencies from Promotion Manager; now HTML5. Flash today continues to exist in CMC for monitoring. BI Workspace has 1 component for Flash. Crystal Reports has flash in the prompts page. Need to remove.

The SAP User Group in France shared this with ASUG yesterday:

A new focus topic (Customer Connection) BI Platform will begin the January 8.

https://influence.sap.com/BusinessObjectsBIPlatform2016

This presentation lists specific platforms and configurations for the SAP Crystal Reports 2016.

View this Presentation

This presentation lists specific platforms and configurations for the SAP Crystal Reports Server 2016, OEM Edition.

View this Presentation

Making BOE SOAP WebServices work on JBoss application server requires a few steps.

Step 1:

Once BOE is installed, locate the "wdeploy\rsa_module" directory.

Copy all files from the following WDeploy RSA module directory:

Path : “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy\rsa_module”

(Below images are just a reference install on Windows.)

Step 2:

On installed JBoss application server,

Create a “com\rsa\main” directory under this “modules” directory.

Path : “<JBOSS_INSTALL_DIR>\modules\"

Place all files copied in step#1 above.

Path: “<JBOSS_INSTALL_DIR>\modules\com\rsa\main”

Step 3:

Move the jboss-deployment-structure.xml file from:

Path: “<JBOSS_INSTALL_DIR>\modules\com\rsa\main”

And place the file in the following dswsbobje source file directory:

Path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\dswsbobje\WEB-INF”

Step 4:

Remove the listed RSA JAR files from the dswsbobje war:

1. certjFIPS.jar,

2. cryptojFIPS.jar

3. ssljFIPS.jar

Path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\ dswsbobje \WEB-INF\lib”

Step 5:

Predeploy the modified dswsbobje web application using the Wdeploy tool.

Path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy

Command: “wdeploy jboss6 predeploy -DAPP= dswsbobje”

Step 6:

A dswsbobje.war file will be generated in following directory.

path: “<BOE_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy/workdir/jboss6/application”

Step 7:

Deploy on JBoss.

Place “dswsbobje.war” file copied in step#6 above.

Path: “<JBOSS_INSTALL_DIR>\standalone\deployments”

Step 8:

Restart the JBoss application server.

Step 9:

Verify deployment

Check list of BOE services available: http://<server>:<port>/dswsbobje/services

Note:

Follow the same steps for AdminTools application.

This API will retrieve Metadata from a crystal report. The response will include following information:

Database connection, tables, aliases, joins, fields used in the document and all its associated properties. It should list fields from CrossTabs as well (see Response format)
Parameters of the report
Formula fields of the report
Parameter fields of the report
Special fields of the report
Filters and all expressions, calculations involved in the report
It will contain similar information for sub reports as well

The URI is: http://<baseURI>/infostore/<reportID>/rpt/structure
Make a GET request to retrieve the report summary information.
Request:
Method: GET
URI: http://<baseURI>/infostore/<reportID>/rpt/structure
Request header attributes: X-SAP-LogonToken
Request body: none

Note: Pre-Requisite for retrieving metadata is toLogon to RestService with below URL and set the header with X-SAP-LogonToken

http://BOEServerIP:6405/biprws/logon/long

Response:
The response contains report summary as shown below:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns17:reportstructure xmlns:ns2="http://www.sap.com/rws/cr/connection" xmlns:ns3="http://www.sap.com/rws/cr/dbfield" xmlns:ns4="http://www.sap.com/rws/cr/table" xmlns:ns5="http://www.sap.com/rws/cr/datasource"xmlns:ns6="http://www.sap.com/rws/cr/fieldlink" xmlns:ns7="http://www.sap.com/rws/cr/join" xmlns:ns8="http://www.sap.com/rws/cr/datasources" xmlns:ns9="http://www.sap.com/rws/cr/usedfield" xmlns:ns10="http://www.sap.com/rws/cr/parameter"xmlns:ns11="http://www.sap.com/rws/cr/parametergroup" xmlns:ns12="http://www.sap.com/rws/cr/parameters" xmlns:ns13="http://www.sap.com/rws/cr/formula" xmlns:ns14="http://www.sap.com/rws/cr/groupcondition"xmlns:ns15="http://www.sap.com/rws/cr/summaryfield" xmlns:ns16="http://www.sap.com/rws/cr/runningtotalfield" xmlns:ns17="http://www.sap.com/rws/cr/reportstructure">
<datasources>
<datasource>
<datasourcename>10.160.192.101 - Oracle12c_JDBC_Connection_5</datasourcename>
<connection>
<cuid>AUy28zmbGthPtalH6n3Gshg</cuid>
<kind>SQL</kind>
<networklayer>JDBC</networklayer>
<database>Oracle 12</database>
</connection>
<tables>
<table>
<name>CUSTOMER</name>
<tablekind>SQL_Table</tablekind>
<dbfields>
<dbfield>
<name>CUST_ID</name>
<kind>SQL_Field</kind>
<datatype>decimal</datatype>
<technicalname>CUST_ID</technicalname>
<qualifiedname>CUSTOMER.CUST_ID</qualifiedname>
</dbfield>
<dbfield>
<name>FIRST_NAME</name>
<kind>SQL_Field</kind>
<datatype>string</datatype>
<technicalname>FIRST_NAME</technicalname>
<qualifiedname>CUSTOMER.FIRST_NAME</qualifiedname>
</dbfield>
<dbfield>
<name>LAST_NAME</name>
<kind>SQL_Field</kind>
<datatype>string</datatype>
<technicalname>LAST_NAME</technicalname>
<qualifiedname>CUSTOMER.LAST_NAME</qualifiedname>
</dbfield>
<dbfield>
<name>AGE</name>
<kind>SQL_Field</kind>
<datatype>decimal</datatype>
<technicalname>AGE</technicalname>
<qualifiedname>CUSTOMER.AGE</qualifiedname>
</dbfield>
<dbfield>
<name>PHONE_NUMBER</name>
<kind>SQL_Field</kind>
<datatype>string</datatype>
<technicalname>PHONE_NUMBER</technicalname>
<qualifiedname>CUSTOMER.PHONE_NUMBER</qualifiedname>
</dbfield>
<dbfield>
<name>ADDRESS</name>
<kind>SQL_Field</kind>
<datatype>string</datatype>
<technicalname>ADDRESS</technicalname>
<qualifiedname>CUSTOMER.ADDRESS</qualifiedname>
</dbfield>
<dbfield>
<name>CITY_ID</name>
<kind>SQL_Field</kind>
<datatype>decimal</datatype>
<technicalname>CITY_ID</technicalname>
<qualifiedname>CUSTOMER.CITY_ID</qualifiedname>
</dbfield>
<dbfield>
<name>SALES_ID</name>
<kind>SQL_Field</kind>
<datatype>decimal</datatype>
<technicalname>SALES_ID</technicalname>
<qualifiedname>CUSTOMER.SALES_ID</qualifiedname>
</dbfield>
<dbfield>
<name>SPONSOR_ID</name>
<kind>SQL_Field</kind>
<datatype>decimal</datatype>
<technicalname>SPONSOR_ID</technicalname>
<qualifiedname>CUSTOMER.SPONSOR_ID</qualifiedname>
</dbfield>
</dbfields>
</table>
<table>
<name>CITY</name>
<tablekind>SQL_Table</tablekind>
<dbfields>
<dbfield>
<name>CITY_ID</name>
<kind>SQL_Field</kind>
<datatype>decimal</datatype>
<technicalname>CITY_ID</technicalname>
<qualifiedname>CITY.CITY_ID</qualifiedname>
</dbfield>
<dbfield>
<name>CITY</name>
<kind>SQL_Field</kind>
<datatype>string</datatype>
<technicalname>CITY</technicalname>
<qualifiedname>CITY.CITY</qualifiedname>
</dbfield>
<dbfield>
<name>REGION_ID</name>
<kind>SQL_Field</kind>
<datatype>decimal</datatype>
<technicalname>REGION_ID</technicalname>
<qualifiedname>CITY.REGION_ID</qualifiedname>
</dbfield>
</dbfields>
</table>
</tables>
</datasource>
<joins>
<join>
<sourcetable>CUSTOMER</sourcetable>
<kind>FullOuter</kind>
<targettable>CITY</targettable>
<fieldlinks>
<fieldlink>
<fromfield>
<name>CITY_ID</name>
<kind>DatabaseField</kind>
<datatype>decimal</datatype>
</fromfield>
<fieldlinkOperator>NotEqual</fieldlinkOperator>
<tofield>
<name>CITY_ID</name>
<kind>DatabaseField</kind>
<datatype>decimal</datatype>
</tofield>
</fieldlink>
</fieldlinks>
</join>
</joins>
</datasources>
<usedfields>
<usedfield fieldtype="DatabaseField" uniqueid="{CITY.CITY}" name="CITY"/>
<usedfield fieldtype="DatabaseField" uniqueid="{CUSTOMER.FIRST_NAME}" name="FIRST_NAME"/>
<usedfield fieldtype="DatabaseField" uniqueid="{CUSTOMER.LAST_NAME}" name="LAST_NAME"/>
</usedfields>
</ns17:reportstructure>

Match specific parts of your dataset with precise locations around the world via a geographical database embedded in Web Intelligence.
Via the graphic engine integrated into Web Intelligence, you can look for specific locations that you can link to the values of selected dimension objects
Visualize your data on a map.

Sizing you SAP BusinessObjects BI4.x system for AWS Deployments

This document is part of the series Getting Started with SAP BusinessObjects BI4.x on AWS

SAP BusinessObjects BI4.x is being certified and supported for deployments on various Cloud Solutions, via this document we provide you the required sizing recommendations before you start deploying SAP BusinessObjects BI4.1 on Amazon Web Services.

Sizing you SAP BusinessObjects BI4.x system for AWS Deployments
- Supported Cloud Offerings for SAP BusinessObjects BI4.x
- Sizing your AWS deployment for BI4.x

Supported Cloud Offerings for SAP BusinessObjects BI4.x

Current SAP BusinessObjects BI4.1 is being certified and supported on the following Cloud Solutions:

SAP HANA Enterprise Cloud (HEC)
Amazon Web Services (AWS)
Microsoft Azure

This document will focus on deploying SAP BusinessObjects BI4.x on an AWS Instance and refer to relevant pre-read documentation to ensure your AWS instance is well prepared for deploying SAP Software.

Sizing your AWS deployment for BI4.x

For a deployment of SAP BusinessObjects BI4.x there is no difference in sizing an on-premise solution, it is strongly recommended to execute a full sizing of your planned deployment by leveraging the content provided in Sizing and Deploying SAP BI 4 and SAP Lumira

As the sizing definition for your SAP BusinessObjects BI4.x system will be provided in a number of SAPS, you do have to validate the instance configuration of the EC2 systems with the number of SAPS provisioned by the AWS instance. An nice overview over translating the ECU's of AWS into SAPS can be found here : BI in the cloud: sizing SAPS and ECUs on AWS servers

Additional interesting food for your brains before starting you SAP BusinessObjects BI4.x deployment on AWS

Back to the Main Page for Deploying BI4.x against Amazon Web Services

Provisioning a Amazon Web Services instance for SAP BusinessObject BI4.x

This document is part of the series Getting Started with SAP BusinessObjects BI4.x on AWS

Provisioning a Amazon Web Services instance for SAP BusinessObject BI4.x
- Prerequisites:
- Provisioning an AWS Instance

Prerequisites:

An Amazon Web Services account
Note: When you create an account, you are automatically signed up for all AWS services. However, you will only be charged for the services you use.
Go through the SAP BusinessObjects What's New Collection to gain insight in what your best version is.
Understanding the support of deploying an SAP BusinessObjects BI4.x system on AWS as documented in http://service.sap.com/sap/support/notes/1656250
A sizing estimate as defined in BI@AWS 01 : Sizing you SAP BusinessObjects BI4.x system for AWS Deployments
Recommended : Setup your Virtual Private Cloud (VPC) connector. The VPC is recommended by Amazon, setting up a VPC is described in the document from SAP HANA ONE (AWS VPC setup) however the steps are equal for any SAP deployment.

Provisioning an AWS Instance

Create your VPC (AWS VPC setup) or reuse one you already have in place
Ensure you selected the correct region to where you want to deploy your image
Within the homescreen of AWS, select EC2 for the creation of a new instance
Select "Launch Instance" to startup a new instance
Select the operating system of your choice which is supported by the SAP BusinessObjects BI version of your choice. To validate supported Operated Systems, please check the Product Availability Report via : https://apps.support.sap.com/sap/support/pam

For the example, a Windows 2012 R2 Base system will be deployed
Select the required instance size. the instance size is key for running a well performing BI4.x deployment and is recommended to be memory optimized. For understanding the translation of Instance Types, please ensure you have executed a correct sizing and translation of ECU into SAPS as described in Sizing you SAP BusinessObjects BI4.1 system for AWS Deployments

For this example I'll deploy the BI4.x system against the memory optimized r3.2xlarge model.
Select "Next: Configure Instance Details" as the next step (not "Review and Launch") as we have a few more configurations to take care of during initialization

Within the Configure Instance Details ensure you select the following items correclty
- Network : Select the VPC as created for step 1
- Subnet : if you have instances within AWS, ensure you select the same subnet if you want to connect into these AWS instances as well
- Auto-Assign Public IP : Recommendation is to disable the auto-assign mode as it is recommended to work with a Elastic IP (default auto assigned IP's can changed after restarting your Instance).. We will later assign a Elastic IP to the system
- Shutdown Behavior : Leave this to Stop, unless you want to have the instance terminated at shutdown (all data will be lost)
- Optional : Enable Termination Protection
- Optional : Enable Monitoring (note: additional costs are involved)
- Optional : Enable EBS-optimized instance (note: additional costs are involved)
- Optional : Select you instance to be Dedicated (note: additional costs are involved)
- Optional : Enable the request for Spot Instances
Select "Next: Add Storage" as the next step (not "Review and Launch") as we have a few more configurations to take care of during initialization

By default a new image is create with a 30Gb Disk. To ensure enough diskspace is available for the deployment of SAP BusinessObjects, we need to add additional capacity.

In the example setup, we'll create / enhance the following disks:
- Increase capacity in the default disk to 80Gb
- Add new disk with a capacity of 128Gb (for installing SAP BusinessObjects and future updates)
- Add new disk with a capacity of 64 Gb (for storing the Windows Page File)
Note : adding disk capacity influences the costs of your AWS Instance
Select "Next: Tag Instance" as the next step (not "Review and Launch") as we have a few more configurations to take care of during initialization

In this example setup, We'll not going to add Tags. for details on how to use tags, please read : Tagging Your Amazon EC2 Resources - Amazon Elastic Compute Cloud
Select "Next: Configure Security Group" as the next step (not "Review and Launch") to enter the final detail for your initial Instance Creation

Security Groups will configure the firewall settings for your Instance. for details on Security Groups, please read : Amazon EC2 Security Groups for Linux Instances - Amazon Elastic Compute Cloud. To enable access into the BI Launchpad and Central Management Console of the BI Platform, we have to enable access to the port for the Web Application Server. For enabling communication by the BI Platform into other server hosted within AWS we potentially need to configure the ports for BIP communications.

In this example setup, we create a new security group "BI42" and enable the port 8080 (as we will use the default Tomcat) as well as a port range (6400-6599) for future inter-AWS communication.

Enabling port 8080 or 3389 (RDP) for "Anywhere" is not recommended, but for the sake of the example deployment currently used. Typically you want to have your organizations External or Internal IP ranges being enable for these ports, which can be set via "Custom IP"

The BIP Port Range is being assigned to the IP Range as used by the VPC as being defined in step 1
We are now ready with the initial setup of the Instance and van hit the "Review and Launch" button. This will provide us the overview of settings applied during the previous steps. Review your settings and when OK, "Launch" your image to become created.
During the launch, you will be requested to select an existing key pair of create a new one. The Key Pair is required to connect into your system. for details around the AWS Key Pair, please read : Amazon EC2 Key Pairs - Amazon Elastic Compute Cloud

In this example setup, we'll create a new Key Pair "BI42@AWS" and download the file to the local machine for later use.
After creating / reusing a Key Pair, You'll be able to launch you instance.
You are informed about the Launch Status and by selecting View Instance, you will be directed to the EC2 Instances listing to validate the progress
Check if the instance is initializing
Once Initialized, a public IP has to be assigned to enable the remote access.
As we selected not to assign a public IP, the instance cannot yet be reached from outside AWS.

for deploying the instance against a Public IP and connecting with remote desktop (windows OS), please continue with step 3 in the process available via : BI@AWS 03 : Connecting to an AWS instance for SAP BusinessObjects BI4.x

Back to the Main Page for Deploying BI4.x against Amazon Web Services

Connecting to an AWS instance for SAP BusinessObjects BI4.x

This document is part of the series Getting Started with SAP BusinessObjects BI4.x on AWS

Connecting to an AWS instance for SAP BusinessObjects BI4.x

Prerequisites:

An Amazon Web Services account
Note: When you create an account, you are automatically signed up for all AWS services. However, you will only be charged for the services you use.
Go through the SAP BusinessObjects What's New Collection to gain insight in what your best version is.
Understanding the support of deploying an SAP BusinessObjects BI4.x system on AWS as documented in http://service.sap.com/sap/support/notes/1656250
An up and running AWS Instance meeting the requirements as described in Provisioning a AWS instance for SAP BusinessObjects BI4x
The Instance ID as received in the previous step
Recommended : Setup your Virtual Private Cloud (VPC) connector. The VPC is recommended by Amazon, setting up a VPC is described in the document from SAP HANA ONE (AWS VPC setup) however the steps are equal for any SAP deployment.

Assign Elastic IP:

Have your AWS Image up and running in your preferred region
Note the fact that no Public IP has been assigned in the sample setup. If you have a public IP assigned, please validate if this has been defined as a Elastic IP. In case you have no Elastic IP assigned, your Public IP may change after restarting your Image, driving potential issues while connecting into your SAP BusinessObjects environment. Additionally it is not recommended to have the SAP BusinessObjects BI Platform (BIP) being deployed against a dynamic IP, as BIP has bindings with the IP.
To assign a static public IP, we have to create a Elastic IP.
for information about the Elastic IP, please check : Elastic IP Addresses - Amazon Elastic Compute Cloud

Creating an Elastic IP can be done via the menu bar on the left under -> Network & Security -> Elastic IPs
Navigate to "Elastic IPs" and select "Allocate New Address" to start the creation of an Elastic IP
You will get a confirmation IF you want to allocate a new IP. Select "Yes, Allocate" to generate a new Elastic IP
Note: Creating Elastic IP's without using them will result in an additional charge
Your Elastic IP is generated and can be assigned to your Instance

The IP created will be listed under your Elastic IP's
Now having the Elastic IP created, we can assign this to our Instance, enabling a fixed IP for usage outside AWS. To assign the IP to you Instance, select Action -> Associate Address
Select the Instance ID from your system and confirm via "Associate"
If we move back to the EC2 screens, we will see that the Elastic IP has been assigned to the Instance

Connecting to AWS Instance running Windows

Now that we have assigned a public IP to the AWS Instance, we can connect to the AWS instance using Microsoft Remote Desktop

Before connecting to the Windows Instance, we need to set an Administrator password to enable a logon. To decode the Administrators password from the key file generated during instance a few steps are required. If you have already set your Windows Password, please continue with step 5

- Select the instance you want to retrieve the Windows Password
- Navigate to Actions -> Get Windows Password
Choose the key pair file as stored while creating the instance
Once the Key Pair is loaded, the value will be visible, select "Decrypt Password" to get the Windows Password
The Windows Password is shown, note down to password or copy this for later use
Start your Remote Desktop via your preferred path :
- Start -> Run -> mstcs.exe
- Start -> All Programs -> Accessories -> Remote Desktop Connection
- Start -> Run -> Remote Desktop

Enter the IP Number as recorded for the Public IP of you Instance
On the Credentials Screen, enter you credentials to connect to the AWS Windows Instance. Please note to connect with .\Administrator to force the use of the local authentication model within the AWS Instance
Depending on your security settings, a security popup may appear

Accept the warning (and if preferred select the tickbox "Don't ask me again for connections to this computer")
You can now work on your AWS Instance and start the installation of SAP BusinessObjects BI4.x. Please continue with : Deployment and Configuration of BI4x on AWS

Connecting to AWS Instance running Linux

To be added

Back to the Main Page for Deploying BI4.x against Amazon Web Services

Amazon Web Services (AWS)

AWS is currently available in various geographic locations:

US
- East (North Virginia)
- West (Oregon)
- West (N. California)
EU
- Ireland
- Frankfurt - Germany)
Asia Pacific
- Singapore
- Tokyo
- Sydney
South America
- São Paulo

for the latest list of locations, please check Global Infrastructure

It is strongly recommended to select a AWS location nearby your (organizations) datacenter / datasource to reduce a potential performance impact due to network latency.

Before deploying SAP BusinessObjects BI 4.4, please read the SAP Note around SAP Application on AWS: http://service.sap.com/sap/support/notes/1656099

		STEP 1: Sizing Sizing requirements Sizing for AWS Sizing Recourses
		STEP 2 : Provisioning Log into your Amazon Web Services (AWS) Account Select Instance Type Create EC2 Instance Launch and Configure Instance
		STEP 3 : Connect and Roll-Out Assign an Elastic IP Address Connect to Instance
		STEP 4: Deployment and configuration of SAP BusinessObjects BI4.x Download SAP BusinessObjects BI4.1 Installer Run Installer Configure SAP BusinessObjects BI4.1 Connect SAP BusinessObjects BI4.1 Client Tools

		STEP 5: Connect to SAP HANA One (AWS) Create SAP HANA One Instance Create SAP BusinessObjects BI4.1 Connection to SAP HANA One (to be added)

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

SAP Cloud for Analytics

What's New in SAP Cloud for Analytics - January 2016

SAP Lumira

SAP BusinessObjects BI4.2 What's New Slides

SAP BusinessObjects BI4.1 What's New Slides

Client Specific Content

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 BusinessObjects Design Studio

SAP Crystal Solutions 2013

What's New in SAP Crystal Solutions 2013

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

Overview

Top Online Resources

Tutorials

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.

Upcoming Webinars - Registrations		Date	Presenter
	SAP BI Platform Support Tool 2.0 - Deep Dive with the Expert	Jan 19	TJ
	Data Federation Admin Tool – Tuning Execution of Multi-Source Universes	Feb 16	SP
h
Recordings of Past Webinars		Date	Presenter
	Gain insight into your BI Platform with a new Auditing Universe and Reports (recording)	Dec 08	MS
	SAP Analytics - Integration of SAP BI Platform with SAP Design Studio (recording)	Nov 24	HJ
	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

More Webinars: SAP Lumira | SAP Predictive | EPM | SAP Design Studio | Web IDE

Supported Platforms (PAM) for SAP BusinessObjects Business Intelligence 4.2 - This presentation describes compatibility with external platforms and technologies.

View this Presentation

'This presentation was shown as part of the BI Webinar Series (recording on http://scn.sap.com/docs/DOC-56308). Product owner Toby Johnston demos and discusses the SAP BI Platform Support Tool 2.0 application: Many new features of the BI Support Tool have been introduced in this version, which greatly improves on the BI administration and support paradigm. Learn how the 2.0 version aligns with SAP's "Next Generation Support" strategy and see what is in store for future versions.

View this Document

Provisioning a Amazon Web Services instance for SAP BusinessObject BI4.x

Prerequisites:

Provisioning an AWS Instance

Connecting to an AWS instance for SAP BusinessObjects BI4.x

Prerequisites:

Assign Elastic IP:

Connecting to AWS Instance running Windows

Connecting to AWS Instance running Linux

SAP Cloud for Analytics

SAP Lumira

SAP BusinessObjects BI4.2 What's New Slides

SAP BusinessObjects BI4.1 What's New Slides

SAP BusinessObjects BI4.1 What's New Recorded Presentations

SAP BusinessObjects BI4.0 What's New Slides

SAP BusinessObjects BI4.0 What's New Recorded Presentations

SAP BusinessObjects Design Studio

SAP Crystal Solutions 2013

Technical Webinar Series: SAP BusinessObjects BI Platform 4.x

Recordings of Past Webinars

Question & Answer

Related:

Sizing you SAP BusinessObjects BI4.x system for AWS Deployments

Supported Cloud Offerings for SAP BusinessObjects BI4.x

Sizing your AWS deployment for BI4.x

Provisioning a Amazon Web Services instance for SAP BusinessObject BI4.x

Prerequisites:

Provisioning an AWS Instance

Connecting to an AWS instance for SAP BusinessObjects BI4.x

Prerequisites:

Assign Elastic IP:

Connecting to AWS Instance running Windows

Connecting to AWS Instance running Linux

SAP Cloud for Analytics

SAP Lumira

SAP BusinessObjects BI4.2 What's New Slides

SAP BusinessObjects BI4.1 What's New Slides

SAP BusinessObjects BI4.1 What's New Recorded Presentations

SAP BusinessObjects BI4.0 What's New Slides

SAP BusinessObjects BI4.0 What's New Recorded Presentations

SAP BusinessObjects Design Studio

SAP Crystal Solutions 2013

Technical Webinar Series: SAP BusinessObjects BI Platform 4.x

Recordings of Past Webinars