My client wanted to display a live chart on customer facing SharePoint site which should display the current performance metrics. The requirement was to display only chart from a webi report and not the entire report contents. Here is the simple solution I did to get this done, does not require IOMS installation or configuration and involvement of SharePoint person. The solution is not just related to SharePoint site but can be used with any web pages. Utilized the IFrame feature of HTML to display part of the webpage.

I don't know whether this solution was already discussed but as I could not find I am posting it.

The solution comprises of following three major steps

1. BI Workspace.
2. HTML Code.
3. Deploy on SharePoint or any other webpage.

Assumption: SSO is configured.

1. Creating BI Workspace

   To get more details about BI Workspace please Click Here. We would be using BI Workspace as a container to hold only the chart area from any report.

• Logon to BI Launchpad and open BI Workspace application.

• Set the layout to "Freeform" and from Public modules drag the report on canvas which contains the desired chart. As shown below.

• Right Click on chart within report and click on "Select this report part".
• Adjust the height and width of the chart container.
• Click on Edit button.

• From "Report Content" section select "Latest Instance" and click Ok.
• Save BI Workspace in public folder.
• Create a recurring schedule (Daily/Hourly as per your requirements) of the report which we used. (Note that we are using this approach to improve the performance of chart display)
• Right click on BI workspace which you have just created, go to Document link and make a note of opendoc URL.

2. HTML Code

• Following is the HTML code (Also available in the attachment) which I used, copy it in a notepad window and just replace the opendocument URL of BI workspace captured above. Later I will show how to adjust the pixels.

<div style="overflow: hidden; max-width: 838px; boarder-top: 0px; border-right: 0px; border-bottom: 0px; margin: -14px auto; border-left: 0px; max-height:970px"><ifrmae class="myiframe" src=http://myserver/BOE/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&amp;iDocID=Abusdf9mjkllasdfk88909070" scrolling="no" style="border-top: 0px; height: 970px; border-right: 0px; width: 874px; border-bottom: 0px; margin-left: 19px; border-left: 0px; margin-top: -55px"></iframe>

• Save the notepad document as .html on your local desktop.
• Double click to open the html page in Internet Explorer.
• The next step is to adjust the pixels so that only the complete chart is displayed and exclude the unnecessary portion.
• Right click on the webpage and click on "Inspect Element"
• Adjust width, margin, height etc using arrow keys of the keyboard for <div> and <iframe> sections as shown below.

• Once done note down the pixel changes and update your .html file.

3. Deploy on SharePoint or any other webpage

• Open the SharePoint site, make sure you have full control on the page where you want to show the chart.
• Edit webpage

• Add new web part or modify existing, click on HTML and Edit HTML

• Copy the HTML code from .html file created on your desktop and paste here.
• The same HTML code can be used in any other webpages.

I hope you find it useful.

We are currently working on moving our BO system from one data center to another data center. We initially planned for installing BO on NAS storage. We started the installation and almost at the last step it gave us an error. But the error message seemed to be more generic one.

So We worked with SAP Support and came to know that "BusinessObjects installation on a SAN/NAS drive is not supported."  For more information please read SAP Note# 1686440 - Support for BusinessObjects installation on Network location

We successfully installed SAP BusinessObjects BI Platform 4.1 SP6 on Windows Server 2012. But when I try to open Promotion Management it was giving me below error

Resolution

We stopped the existing InputFileRepository services from CMC and disabled it.

We created a new <Hostname>.InputFileRepository , enabled and started it.

After that it was working fine. Upon confirmation we deleted the old InputFIleRepository Services.

Hi............................,

I would like to share my own experience on Upgrade management tool...

Before going to discuss about Upgrade management Tool, you need to know about Business Intelligence Content.

What is BI Content...??

BI content is nothing but Collection of Users,groups,folders,reports,universes,security,other objects, which is available with Central Management

Server..

that is called BI Content or CMS Content.

Suppose you are working with BOXI 3.1,whatever the BO version you are using the CMS Stores the above data(Users, Groups, Universes,

Documents, Folders etc.)

Now consider you are working with BOXi 3.1,If you want upgrade your version from BOXI 3.1 to BO 4.X

Here you need to upgrade your CMS content to higher version, to do that we use Upgrade Management Tool.

**User has a choice to select method of Upgrade as per his requirement.**

If I talk about the above two methods..

Complete Upgrade: This is Best and Fastest Method to Upgrade, Because it take all the CMS content at a time from source and it will deploy it to destination.

                                If you use it you can save time also.

Incremental Upgrade: it allows user to select required content to upgrade.

Once you start with upgradation by selecting complete upgrade technique, you will see three options...

Defends upon selection you need to provide some credentials on next to this selection. Credentials are User name, Password.

Live to Live: to do this you need to authenticate with Source  CMS to Destination CMS.

Live to BIAR: To do this you need to Authenticate with source CMS and you have to provide a path to save BIAR file along with a name.

Defending upon your requirements and complexity of content you can create more than one BIAR file, but condition is all BIAR files should be in Same

Directory.

while creating BIAR file you can encrypt that by giving password to it, But it is Good to avoid encryption, if you do it will take more time while processing.

finally it perhaps an performance issue.

generally we use BIAR files while transporting content from one environment to another environment (Development to Test to Production etc.)

Note:: If you want to Transport CMS content from one environment another with in the same version like BO 4.X to BO 4.x

          It is NOT possible with Upgrade management tool,  to do that You need to go with PROMOTION MANGAMENT.

Note:: Before Start Upgrade, you need to stop all services except 1.CMS 2.File Repository Server

BIAR format will bebiarengine.jar

will update soon.....

Thanks & Regards

Brahma Reddy

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 <HDB_Client_Install_Directory>/libodbcHDB.so<BOE_Install_Dir>/sap_bobj/enterprise_xi40/linux_x64/

                              cp <HDB_Client_Install_Directory>/libodbcHDB.so<BOE_Install_Dir>/sap_bobj/enterprise_xi40/linux_x86/

                             Step 3: Add the details of HANA server in odbc.ini which is present in <BOE_Install_Dir>/sap_bobj/enterprise_xi40/

                                  Below is the screenshot, which has details of HANA driver

                                  Note: ServerNode Value should be ServerNode=<HOSTNAME OF HANASERVER>:3<INSTANCENUMBER>15

                                                                                               echo $ODBCINI

                                          Note: Output should be: <BOE_Install_Dir>/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 <BOE_Install_Dir>/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_1452244015” 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.

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 here if you need.

You can download client and Studio from the HANA Developer Center.  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.

1. Enter the host name, instance number of your HANA database also description then click on Next to continue
2. Enter the user name and password for the CMS database you just created then click on Next to continue
3. 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

1. 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
2. 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
3. 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

4. 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.

1. Launch CCM from Start > All Programs > SAP BusinessObjects Intelligence > SAP BusinessObjects BI platform 4 > Central Configuration Manager
2. Select Server Intelligence Agent (SIA) then click on Stop icon (black square) on toolbar, or right click on SIA then select Stop from the popup menu to stop the service

Step 4: Change CMS database

1. Once the SIA service is stopped, select SIA then click on Specify CMS Data Source icon on the toolbar ( the gold cylinder)
2. CMS Database Setup window pop up, you can choose desire setup method then click on OK to continue

• Update Data Source Settings

Choose this option if you would like to point to a different data source. This option will simply change your data source without copying over existing data.

Note: The destination data source must contain deployment information for this cluster. Do not use this option for clustering with a different CMS cluster. Refer to the Administrator ‘s Guide for details on CMS clustering workflows.

If you choose Update Data Source Settings a Select Database Driver window will pop up to allow you choose a connection method. Here choose SAP HANA database (ODBC) of cause then click on OK to continue

Select Machine Data Source then select CMS141 created in Step 2 then click on OK to continue. If you have not yet created data source for you HANA database you can now click on New to create new one here.

Enter the user name and password then click on OK to continue

Enter the cluster key then click on OK to continue. CMS tables will be created on HANA database BOE141(ODBC CMS141)

• Copy  data from another Data Source

Choose this option if you would like to copy data form a different data source. You may change your data source or keep the one that you are currently using. This option will destroy any information already present in the destination data source. The deployment topology of the destination cluster must match the topology of the source cluster. Refer to the Administrator’s Guide for details on copying CMS data Sources.

The Specify Data Source window pop up to allow you specify source and target data source. First click on Specify to select source database.

Select current using database from list, default is SQL Server or SQL Anywhere. Click on OK to continue.

You might be asked ID and password to log in database

Enter cluster key then click on OK to continue

Next then click on Browse to select target data source. From the list select SAP HANA database then click on OK to continue.

You might be asked ID and password to log in database.

After specifying source and target database then click on OK to start copy CMS tables from source to target. All data in target will be overwritten.

• Recreate the current Data Source

Choose this option if you would like to re-initialize the current data source. This option will destroy any data already present in the data source.

Step 5: Verify CMS changed and configure Audit database

1. Select Server Intelligence Agent (SIA) then click on Properties icon on toolbar from Central Configuration Manager (CCM), or you can also right click on SIA then select Properties to verify changed

    2. Select Configuration you can find out the CMS now has been changed to CMS141 ( SAP HANA database BOE141). You can also change cluster name and cluster key here. Click on Cancel go back to CCM

Select SIA then click on Start icon ( black triangle) or right click on SIA then select Start to start SIA service again.

After SIA service is running you can login to Central Management Console (CMC), click on Auditing under column Manage

Configure ADS Database settings accordingly, enter SAP HANA ODBC DNS name in field Connection Name, select SAP HANA Database from Type then enter user name and password. Click Save to save configuration.

Warning: You must restart all CMSs before ADS configuration changes will take effect.

Restart server then login CMC again then you will see the Auditing is taking effect

Launch SAP HANA Studio to view CMS and Auditing tables

(End…….Enjoy!)

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

Technical Webinar Series: SAP BusinessObjects BI Platform 4.x

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

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

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

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

Upcoming Webinars - Registrations		Date	Presenter
	Data Federation Admin Tool – Tuning Execution of Multi-Source Universes	TBD	SP
	#askBI: Innovation in Core BI Solutions (hint: BI 4.2)	Mar 24
h
Recordings of Past Webinars		Date	Presenter
2016
	Best Practices for the Administration of the Design Studio Add-On (recording coming soon)	Apr 24	PB& PS
	SAP BI Platform Support Tool 2.0 - Deep Dive with the Expert (recording| pdf)	Jan 19	TJ
2015
	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
2014
	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

Hi all,

Here I would like to list some BI important Master KBAs.

These Master KBAs include many trouble shooting methods, best practices and known issues.

• BI servers startup:

2294812 - *** Master KBA *** - Troubleshooting server startup issues in SAP BusinessObjects Business Intelligence Platform

• Crystal reports:

2238875 - *** Master KBA *** Crystal Reports with Oracle datasources

• Platform Search:

2241459 - *** MASTER KBA *** Platform Search Application

• Upgrade Management Tool (UMT):

1904814 - Master KBA: Best practices for a successful migration to BI4 using the upgrade management tool

• Authentication:

1476374 - ***Best Practices*** including Basic and Advanced AD Troubleshooting Steps for Manual Logon, NTLM, Kerberos and Vintela Single Sign On

• BW BICS connection:

2315476 - *** Master KBA *** - Troubleshooting problems when reporting against BW BICS connection

• Mobile:

2306555 - *** MASTER KBA *** BusinessObjects Mobile - Installation / Configuration / Connection / Display / SDK

2306677 - *** Master KBA *** - Troubleshooting BusinessObjects Mobile issues

• Lumira:

2308200 - *** MASTER KBA *** Refreshing datasources in SAP BusinessObjects BI Platform when using SAP Lumira

2303956 - *** MASTER KBA *** Configuring SSO with SAP Lumira

2255102 - *** MASTER KBA *** Installation and Configuration of SAP Lumira Server for BI Platform

2219393 - *** Master KBA *** SAP Lumira - Common Issues

I will keep this blog updated if more Master KBAs are created. Hope they help.

Best regards,

Vincent

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.

If you want to play with SAP BusinessObjects BI4.1 or BI4.2, you can also enroll yourselves for a TRAIL version of our software via our Cloud Appliance Library. steps how to enroll your free 30 day trail version of SAP BusinessObjects BI4.1 or SAP BusinessObjects BI4.2 can be found here : Deploy your BI4.2 Trial@AWS

Before deploying SAP BusinessObjects BI 4.x, 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.x Installer Run Installer Configure SAP BusinessObjects BI4.x Connect SAP BusinessObjects BI4.x Client Tools
		STEP 5: Connect to SAP HANA One (AWS) Create SAP HANA One Instance Create SAP BusinessObjects BI4.x Connection to SAP HANA One (to be added)

This document proposes a framework for adding an Apache web server to your deployment of SAP BI Platform 4.0.  By using Apache in conjunction with the WDeploy web application deployment tool, significant performance improvements become possible.  These modifications reduce the server footprint of the web applications, and speed delivery of web content to client browsers.

View Document

In this quick document i am focusing a smaller piece of a bigger topic: How to troubleshoot intermittent issues in BI Platform where sharing some experiences from first steps of troubleshooting intermittently appearing issues on such BI platform 4.x where having more than one processing servers or nodes configured.

To isolate the report perform the following steps:

1. Launch the CMC and go to Servers
2. Click Manage -> New -> Create Server Group
3. Type a name for the group as "Isolation Group"
   
4. Go to the ServiceCategories -> Web Intelligence Services
5. Select the webintelligence server you would like to isolate
6. Open Properties -> Turn on Disable Cache Sharing option in the Web Intelligence Common Service block to prevent webi processing server to interact with other servers. Restart the WebintelligenceProcessingServer is required
   
   
   
   
   
7. Select the WebIntelligenceProcessingServer you would like to isolate
8. Right click-> Select Add to Server Group and select "Isolation Group"
   
   
   
   
9. In CMC go to Folders and locate and select the report file needs to be isolated in the environment
10. In Properties click Default Settings-> Web Intelligence Process Settings
    
    
    
    
11. In section Default servers to use for viewing and modification: select option Only use servers in the selected group and select "Isolation Group" from the list of group

NOTE: If the servers in the Server group are either not enabled or not running, the report will be not processed  You can also include Adaptive Processing Servers, Central Management Server into the "Isolation Group" if required

Hi all,

suddenly I FeedBack.

My Customer's BO WebI Report is not working.

Error Message Like  'Olap Connection Failed'.. and so on.

I Found Googling And any Guide, Notes..

Main Task.

1. Certificate Regeneration and Reregistration.

2. Seperate, DSL Bridge.

3. Seperate, STS(Security Token Service) in DSL Bridge .

and Countless Restart and OS Reboot.

Finally, I found exactly answer.

it's very Simple Problem.

cause BETWEEN BO Server AND BW Server TimeStamp is Different.

Where Document IN NetWeaber.

Using Logon Tickets - User Authentication and Single Sign-On - SAP Library

I hope this help someone else.

Have a good Day.

Hyun-Bae

SAP BusinessObjects BI4.2 Trial system rollout agains Amazon Web Services

SAP BusinessObjects BI4.x is being certified and supported for deployments on Amazon Web Services (AWS). To enable everyone experiencing the capabilities of SAP BusinessObjects BI4.2, we have enabled a 30 days trial deployment against an Amazon Web Service account, via the SAP Cloud Appliance Library (CAL).

Via this document we provide you with a step-by-step to rollout a pre-setup SAP BusinessObjects BI4.2 trial system against Amazon Web Services. If you want to deploy SAP BusinessObjects BI4.x all by yourself, check out: BI@AWS : Getting Started with SAP BusinessObjects BI4.x on AWS

SAP Software Deployed

the Trial System provided via this solution is:

• SAP BusinessObjects BI Platform 4.2, including Web Intelligence, Crystal Reports, Dashboard services
• SAP BusinessObjects Explorer 4.2
  

Prerequisites

To enable the rollout of an SAP BusinessObjects BI4.2 30 days trial system, the following prerequisites are to be completed.

• An activated AWS Account
• An activated SAP CAL Account
  

If you have not yet an activated AWS Account, you can set on up via : Amazon Web Services (AWS) - Cloud Computing Services. Choose for "Create an AWS Account" and follow the steps provided.

If you have not yet an activated CAL Account, you can request one via : SAP Cloud Appliance Library. For details on setting up an CAL Account please refer to : Applying for a User of SAP Cloud Appliance Library.

Mapping your CAL Account with AWS

If not yet done, we need to configure your CAL Account with the Cloud Provider ID for AWS before we can rollout any CAL provided solution. For configuring your CAL Account with the AWS Cloud Identity, please check out CAL FAQ - Specific questions for Amazon Web Services

Once you have setup the Access Keys from CAL to AWS you can test the connection to ensure a successful deployment, for this navigate within the CAL Webpage to : Accounts -> Double Click your account -> Test Connection.

Activate SAP BusinessObjects BI4.2 Trial Solution

We are almost ready to initiate the 30 Days Trial system for SAP BusinessObjects BI4.2, before rolling out we need to activate the solution within your account.

1. Open https://cal.sap.com
   
   
   
   
2. Logon with your user account as defined in earlier steps
   
   
   
   
3. Within the CAL portal, navigate to -> Solutions
   
   
   
   
4. Scroll Down to the Solution "SAP BusinessObjects Business Intelligence platform 4.2 SP2
   You can use the Filter option to view only the Free Solutions
   
   
   
5. By clicking the Solution, it will open up the solutions detail page
   
   
   
6. Read the Terms and Conditions and accept them if required
   
   
   
7. If you have interest, activate the solution within your account
   
   
   
8. Read and download the "Getting Started Guide" as this contains the details on how to connect and logon to your 30 days trial system
   

Create SAP BusinessObjects BI4.2 Trial Instance

If there is little experience with deploying a system within AWS and/or you have no other instances and or security settings applied within AWS the default deployment would be sufficient to get you going. By default settings, this instance will be suspended after 8 hours of running, to save costs from the AWS side. If you do not want the system to suspend, please move to the next chapter for an advanced deployment.

if you have multiple instance already in place, it is advised to use the Advance deployment option, please continue at the next chapter

1. To startup your 30 days trial deployment, choose "Create Instance"
2. Within the "Create Instance" Screen select the account you want to use for the deployment (if you have multiple)
   - Enter the name for the instance
   - Select the region you want to deploy against (note: choice of region may influence the costs of hosting the AWS instance)
   - Provide a password for accessing the instance via a remote session
   
3. Finish the process by "Create"
4. The Instance with SAP BusinessObjects BI4.2 Trial deployment will now be created within your AWS account. To enable access into the system (OS Level) you need a private key. Download the key and keep it safe for potential future use.
   
5. You will be informed that the instance is being created.. please do not connect to the instance until the deployment is 100% completed.. This will take approx 20 minutes
   
6. You can check the progress under instances
   
7. Once the instance creation against AWS has been completed, you will find the instance recorded as "Active" under your instances
   
8. You can now connect the your system by a direct logon to the Central Management Console and BI Launchpad via the public URL of your instance.
   for connecting directly to the Central Management Console (CMC) or BI Launchpad you have to lookup the public IP of you system. If you click on your Instance, in this example "SAPCAL_BI42_TRAIL", you can see the details of your system. The public IP is recorded on the right side of the screen.
   
   For the example, connecting to the CMS would be http://<IP>:8080/BOE/CMC or http://<IP>:8080/BOE/BI for the BI Launchpad
   
9. After browsing to the SAP BusinessObjects BI42 system (CMC or BI Launchpad), you can logon the the system using the Administrator account. The password for the account is recorded in the "Getting started guide". You can now start using your SAP BusinessObjects BI4.2 system, by creating connections to your database(s) or upload an Excel file to the system as source for your BI Content.
   
   
10. For accessing the underlying operating system (SUSE Linux 11) you need to run an SSH Client. Detailed steps for connecting to the Operating System are described in "Connecting to Operating System" further down in this document.
    
    

Create SAP BusinessObjects BI4.2 Trial Instance with advanced settings

If you are experienced in deploying a system within AWS and/or you have  other instances, VPC and/or security settings applied within AWS the advance mode is recommended to ensure specific settings can be addressed.

1. To startup your 30 days trial deployment, choose "Create Instance"
2. In the initial screen for creating an instance, select "Advanced Mode" at the bottom right of the screen
   
3. If Applicable, select the account you would like to use for the deployment
   
4. In Step 2, enter the required details
   - The name for the instance
   - (Optional) A description for the instance
   - Choose the region you want to use for deploying the system (us-east-1 or us-west-2)
   - Select the network you want to use. If you have no VPC defined, SAPCAL will be created by default.
   - Select the subnet range you want to use
   - Select (tickbox) if you want to assign a Public Static IP Address (additional costs involved)
   
5. If preferred you can change the Image settings and sizes in step 3.
   - Changing to provisioned IOPS will provide a faster system but increases costs
   - Changing from R3_LARGE to R3_XLARGE will provide a faster system but increases costs
   - Adding Access Points (Opening the firewall), can reduce the security of your system, but may be required to access your data
   
6. Enter the solutions password in step 4
   
7. Define a suspend and resume schedule if preferred in step 5
   
8. Validate all settings applied in the review screen, edit settings you want to change.
9. If all OK, continue with "Create" to start the creation of your SAP BusinessObjects BI4.2 Trial system on AWS.
   
10. The Instance with SAP BusinessObjects BI4.2 Trial deployment will now be created within your AWS account. To enable access into the system (OS Level) you need a private key. Download the key and keep it safe for potential future use.
    
11. You will be informed that the instance is being created.. please do not connect to the instance until the deployment is 100% completed.. This will take approx 20 minutes
    
12. You can check the progress under instances
    
13. Once the instance creation against AWS has been completed, you will find the instance recorded as "Active" under your instances
    
14. You can now connect the your system by a direct logon to the Central Management Console and BI Launchpad via the public URL of your instance.
    for connecting directly to the Central Management Console (CMC) or BI Launchpad you have to lookup the public IP of you system. If you click on your Instance, in this example "SAPCAL_BI42_TRAIL", you can see the details of your system. The public IP is recorded on the right side of the screen.
    
    For the example, connecting to the CMS would be http://<IP>:8080/BOE/CMC or http://<IP>:8080/BOE/BI for the BI Launchpad
    
15. After browsing to the SAP BusinessObjects BI42 system (CMC or BI Launchpad), you can logon the the system using the Administrator account. The password for the account is recorded in the "Getting started guide". You can now start using your SAP BusinessObjects BI4.2 system, by creating connections to your database(s) or upload an Excel file to the system as source for your BI Content.
    
    
16. For accessing the underlying operating system (SUSE Linux 11) you need to run an SSH Client. Detailed steps for connecting to the Operating System are described in "Connecting to Operating System" further down in this document.

Suspending and Resuming your Instance

To save costs, you can suspend your BI4.2 Instance and resume it when required (i.e. suspend in the night and/or weekends). Suspending an AWS system reduces the costs as only consumed disk space will be charged. Once suspended you can easily resume the system once needed.

To suspend your instance please take the following steps:

1. Connect to the CAL portal
2. Navigate to you instance(s)
3. open the instance you want to suspend
4. Choose Suspend on the top right
   
   
5. Your system will be stopped on the AWS infrastructure.
   note: this will not remove any changes made within the system
   
   

To resume your instance please take the following steps:

1. Connect to the CAL portal
2. Navigate to you instance(s)
3. Open the instance you want to resume
4. Choose Activate on the top
   
5. By default the system will be suspended after 8 hours. You can chance or disable the suspend timeframe if preferred.
   
   
6. Your system will be started on the AWS infrastructure and can be accessed in approx 5 minutes afteer starting.
   Note: suspending and resuming an instance may lead to a change of the public IP, please check your public IP before connecting.

Terminating your Trial Instance

If you completed your trial and do not want to continue with the system (by acquiring a license) you can terminate the instance with the following steps.

1. Connect to the CAL portal
2. Navigate to you instance(s)
3. open the instance you want to suspend
4. Choose Suspend on the top right
5. Once suspended you can terminate your system by choosing "Terminate" at the top of the page
   
   
6. By terminating the instance, you will loose all changes applied and/or content created. Confirm you really want to terminate the system.
   
   
7. Your system will be terminated and removed from AWS. This will stop the charges from AWS against your account.
   
   
   

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

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

SAP BusinessObjects BI4.2 What's New Slides

• SAP BusinessObjects BI4.2 What's New L0

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

SAP BusinessObjects BI4.1 What's New Slides

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

Client Specific Content

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

SAP BusinessObjects BI4.1 What's New Recorded Presentations

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

SAP BusinessObjects BI4.0 What's New Slides

Client Specific Content

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

SAP BusinessObjects BI4.0 What's New Recorded Presentations

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

SAP BusinessObjects Design Studio

• SAP BusinessObjects Design Studio 1.6 What's New L0
• SAP BusinessObjects Design Studio 1.6 What's New L1
• SAP BusinessObjects Design Studio 1.6 What's New L2

SAP Crystal Solutions 2013

• What's New in SAP Crystal Solutions 2013