1862925 - Session handling and tuning

Symptom

In certain scenarios it is observed that Sessions are not being released when users close the browsers.

Environment

SAP Business Intelligence 4.0 / 4.1
Central Management Console
BI Launchpad

Reproducing the Issue

Here is just one example workflow, but there are various methods of where a session get created within Business Intelligence 4.0 (BI4.0)
Logon to the Central Management Console (CMC) or BI Launchpad
Close browser
Observe your session count on same or other machine in the CMC the behavior of your sessions.

Cause

Due to the single BOE.war deployment now in BI4.0, the Session behavior has somewhat altered when comparing to the older versions (Example of older version BusinessObjects Enterprise XI3.1).
One shared browser session behavior is currently being looked at by SAP development to see if this can be altered or improved. The following Problem Report has been created for this: ADAPT01685736

Resolution

Here are various scenarios and workflows related to session count.

Logon as a user in BI Launchpad or CMC in a browser and use log off button. This will clear one session count.
Logon as a user in BI Launchpad or CMC in a browser and close browser. The default 20 minutes timeout setting will catch and clean session.
Logon as a user in BI Launchpad and/or CMC in same browser but 2 different tabs and log out of one of them on same machine. This will clear one session and one will remain. (go from 2 down to 1 sessions).
Logon as a user in BI Launchpad and/or CMC in two browser windows and log out of one of them and close browser on same machine. This will clear one session and one will remain. (go from 2 down to 1 sessions).
Logon as a user in BI Launchpad and/or CMC in two different kind of browsers (IE, Firefox, Chrome etc) and log out of one of them and close browser on same machine. This will clear one session and one will remain. (go from 2 down to 1 sessions).
Logon as a user in BI Launchpad and/or CMC in two different kind of browsers (IE, Firefox, Chrome etc) and close one of them on the same machine. This will clear one session after default 20 minutes timeout. (go from 2 down to 1 sessions after 20 minutes).
Logon as a user in BI Launchpad and/or CMC in two browser windows on 2 different machines and log out of one of them and close browser on one of the machines. This will clear one session and one will remain. (go from 2 down to 1 sessions). Also note that this is the same for no matter what kind of browser is used (IE, Firefox and Chrome).
Logon as a user in BI Launchpad and/or CMC in two browser windows on two different machines and simply close one of the browsers on one of the machines. This will clear one session after default 20 minutes timeout. (go from 2 down to 1 sessions after 20 minutes). Also note that this is the same for no matter what kind of browser is used (IE, Firefox and Chrome).
Logon as a user in BI Launchpad and/or CMC in two browser windows and simply close one of the browsers on same machine. Two sessions will remain even after default 20 minutes timeout. Timeout and session cleanup will only occur after "ALL"browser windows are closed on same machine.
Logon as a user in BI Launchpad and/or CMC in two tabs in same browser window and simply close one of the tabs on same machine. Two sessions will remain even after default 20 minutes timeout. Timeout and session cleanup will only occur after "ALL"browser windows are closed on same machine.

NOTE: Do keep in mind that the above scenarios are given as example when a user or users log on one or two times, but the same applies to no matter the amount of user logons.

The last two given scenarios above are currently being looked at by the aforementioned ADAPT (see the "Cause" section) and see if it can be improved. The difference for these two scenarios in BI4.0 vs XI3.1 is that in BI4.0 the Web application deployment is done under one single BOE.war deployment that houses the CMC and BI Launchpad. In XI3.1 and previous versions the Infoview and CMC was split in different deployments and session handling was addressed separately.

What can you do to tweak your session handling in BI4.0.

Currently there is only one setting that can be altered to affect session handling in BI4.0.
The one setting available is the setting that alters the default 20 minutes timeout.

look up your deployed Web.xml file on your Web application server.
Open this xml and scroll to the bottom of this file and you will see:

<session-config>
<session-timeout>20</session-timeout>
</session-config>

3. You can alter this to any amount of minutes.

Keywords

ADAPT01685737, TE: 5050114680, BOE, CMC, login, session, close, hung, stuck

1861180 - Customer instructions and best practice for collecting a BI Platform 4.x end to end trace

Symptom

Active Global Support has requested for you to collect an end to end trace for a problematic workflow
This note outlines the steps you should follow to collect a useful end to end trace from your SAP BI Platform 4.x landscape if you do not have Solution Manager diagnostics.
End to end tracing allows SAP Support to identify root cause by analyzing a unified log view from all nodes in the BI Platform landscape
This note is applicable to workflows reproduced from browser based clients (e.g. BI Launchpad)

Environment

SAP BusinessObjects Business Intelligence Platform 4.0
SAP BusinessObjects Business Intelligence Platform 4.1

Resolution

PREPARE THE BI LANDSCAPE

Prepare your BI landscape to make sure that when traces are generated, we are keeping enough trace files to capture the whole workflow.
On each node in your BI Platform 4.x landscape, make the following change:
1. Browse to the following directory:

WINDOWS

<INSTALL_PATH>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\conf

UNIX

<INSTALL_PATH>/sap_bobj/enterprise_xi40/conf

2. Make a backup copy of bo_trace.ini
3. Edit bo_trace.ini and change the value for the parameter keep_num to 20 (for Webi workflows, use a keep_num value of 50). Also update the value for parameter append to false.

keep_num = 20;
append = false;

4. Save the changes and repeat steps 1-3 for each BI node in the landscape.

GENERATE THE TRACE

1. Download the correct SAP Client Plug-in version according to your version of Internet Explorer

VERSION	PLUG-IN DOWNLOAD	SAP NOTE
Internet Explorer 8, 9, 10	SAPClientPlugin_1.26_x86.zip	SAP NOTE 1435190
Internet Explorer 11	SAPClientPlugin.rar	SAP NOTE 1608231

IMPORTANT: Always use the x86 version of the SAP Client Plug-in when tracing with Internet Explorer (regardless of the OS bit version)

2. Unzip the SAP Client Plug-in to the client where you will be executing the problematic workflow
3. Close any open web browsers before launching the SAP Client Plug-in
4. Browse to the location where you unzipped the SAP Client Plug-in, then right click on plugin-starter-gui.exe and choose 'run as administrator'.
5. Set the 'Application' option to Microsoft Internet Explorer and click Launch

6. Under the "Business Transaction Name" property choose a descriptive name that describes the workflow that you are capturing and set the 'Next Step TraceLevel' to High

7. Before you start your end to end trace, you should first queue up the browser to the beginning of the problematic workflow that you wish to trace.
8. When you are ready to begin your workflow, click the "Start Transaction" button then execute only the workflow you are trying to trace. Observe that the number of sent bytes/received bytes will increase if the trace is working.

It is best practice to only trace the transactions where the problem is occurring. Try to avoid additional browsing and clicking as this will generate extraneous logs and make analysis more difficult

9. As soon as you have completed your workflow press the "Stop Transaction" button. You can ignore the message "Settings are not valid" as it relates to the SMD Agent settings for Solution Manager.
10. Click OK to close the SAP Client Plug-in window.

COLLECT THE TRACES

There are three types of traces you must collect for SAP Support.

SAP Client Plug-in traces
BI Platform server traces
BI Platform web application traces

Before you start, first create a new temporary folder on your client. This folder will be used to store all of the trace files generated on our BI landscape. In this example, the temporary folder will be C:\e2e_traces

Collect SAP Client Plug-in logs

1. In the same directory where you executed the SAP Client Plug-in, browse to the /log directory.
2. Inside of the log directory will be a folder that is named after the value that you specified as "Business Transaction Name". Copy this folder to the central temporary folder that you created at the beginning of this article (for example: C:\e2e_traces)

Collect BI server logs

For each node where you are running a Server Intelligence Agent do the following:
1. Browse to the BI Platform 4.x logging directory in the location

WINDOWS

<INSTALL_PATH>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging

UNIX

<INSTALL_PATH>/sap_bobj/logging

2. Change the view to details

3.  Filter for files using the pattern *.glf
     WINDOWS

     UNIX

4. Sort by date so that the newest logs are shown at the top of the list

5. Copy all glf files generated in the last 4 days and paste these logs in the temporary folder created on your client machine in step 1 (C:\e2e_traces)

It is important that you collect at least 4 days worth of traces since the time stamp shown will not always be updated to the current date

6. Repeat steps 1 to 5 for each node in your BI landscape that is running a Server Intelligence Agent and copy these logs to the central temporary log folder

For Promotion Management / Lifecycle Management promotion job tracing, you should collect these traces from all SIA nodes on the SOURCE, DESTINATION, and LCM CMS landscapes

Collect BI Platform web application logs

For each node where you are running a Java Application Server (e.g. Apache Tomcat, Oracle Weblogic, IBM Websphere, etc), complete the following steps to collect the Web Application Server logs. The BI Platform 4.x web application logs may be generated in different locations depending on the application server you are using and the user account in which the application server is running under.
BI Platform 4.x web application logs are captured in folders with the name beginning with SBOP. For example, the BI Launchpad logs are stored in the folder,C:\SBOPWebApp_BILaunchpad_10.169.1.110_8080
1. On each application server node, check the following locations for the BI Platform 4.x web application logs

WINDOWS

<INSTALL_DRIVE>:\SBOP*
<INSTALL_PATH>:\SAP BusinessObjects\Tomcat 6\*.glf
<INSTALL_PATH>:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging\SBOP*
C:\windows\system32\configure\<systemprofile>\SBOP*
C:\users\<appserver_user>\SBOP*

UNIX

$HOME/SBOP*
<INSTALL_PATH>/sap_bobj/tomcat/bin/SBOP*

2. Copy the folders with the name beginning with SBOP* to your central temporary log folder. For example: C:\e2e_traces

SUBMIT TRACES TO SAP SUPPORT

1. After you have collected all of the required information, zip up the central temporary log folder. For example: C:\e2e_traces
2. SAP Support will provide you with a SAP Box container. Upload the zip file to the SAP Box container provided.

Send SAP Support the entire set of traces, not the filtered view. It may be necessary for SAP Support to analyze traces generated without the SAP Passport transaction id in order to determine root cause

RESTORE BO_TRACE SETTINGS

On each node in your BI Platform 4.x landscape, make the following change:
1. Browse to the following directory:

WINDOWS

<INSTALL_PATH>\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\conf

UNIX

<INSTALL_PATH>/sap_bobj/conf

2. Restore the backup copy of BO_trace.ini

1475602 - Support procedures for identifying and resolving security vulnerabilities in SAP Business Objects products

Symptom

A third-party tool such as WebInspect or AppScan has been pointed at a deployment of an SAP Business Objects product, (XI R2, XI 3.1, BI 4.x etc) and the resulting report shows a number of security vulnerabilities (such as Cross Site Scripting). How are these issues addressed by SAP Support? What are the responsibilities of the customer? What are the responsibilities of SAP engineers?

Environment

Any SAP BusinessObjects XI / BI deployment.

Reproducing the Issue

Employ a third-party tool such as WebInspect or AppScan to point to an XI deployment and run the application. The resulting report will list categorized security vulnerabilities (Critical, High, Medium, Low, Informational), and details on each one. Product Support will only address vulnerabilities of Critical categories. Please provide evidence that your vulnerability is critical.

Cause

The individual items identified in the report may have resolutions that require configuration or changes made to products in use that are not SAP products (such as the application server in use), or they may point to specific BI 4.0 or XI 3.1 pages as being vulnerable to specific types of attacks.

Resolution

Third-party scan reports cannot be raised wholesale as a support case. These third-party tools scan in an non-discriminatory way, bringing up results for high, low and negligible security threats for a particular environment.
Each issue that a customer would like to have considered must be raised as a separate issue/support ticket as a full scan report contains too many disparate, unqualified and negligible results.
For a support ticket to be usefully processed, the customer would first have to show that a specific result has critical security implications in their particular deployment and provide a reproducible workflow for the issue to be considered.
Given a successful reproduction, the issue can then be raised to development for possible inclusion in a later version of the product.
The following is how SAP Support addresses these issues. The first three items are customer responsibilities:
1. The customer scans the product with the latest Service Pack/Fix Pack that is available.
2. The customer manually tests each URL reported that they believe to be a significant vulnerability. Different security scan products may categorize the same issue at different levels. Generally speaking, SAP Support will only evaluate issues that your business considers critical - these will usually be categorized in the scan report as Critical.
3. For each unique URL that reveals a reproducible vulnerability, customer opens a separate ticket identifying the URL and documenting how to reproduce the issue manually (proof of concept). Typically, this is just the URL and an example script injection. This is necessary to track each XSS/CSS/CRLF/CSRF vulnerability, as each unique URL is going to require a different fix. It is possible a scan tool may report the same URL multiple times, with the only difference being perhaps different variables within the page used when injecting a script. If the same URL shows up several times in the scan, only one ticket needs to be opened for this unique URL. Within the ticket, document the individual variables identified.

4. The engineer assigned has several responsibilities in their investigation:

Verify the vulnerability against the latest release (Fix pack level or internal build).
If the issue is something that can be resolved with an application server or other product configuration change, this is when this would be identified and proposed.
The engineer identifies if any open fix requests that have already identified the same issue, and the status of the fix request.
If the issue is reproducible and has not already been identified, document it and submit a fix request to the Product Group for a resolution (patch).
When the patch is released, test and verify it fixes the issue, then notify the customer of the patch release.

Keywords

security vulnerability vulnerabilities cross site scripting xss webinspect appscan policy

1757132 - BI4 Support Pack Upgrade and Patch Install Best Practice Guide

Symptom

A guide to best practices for upgrading to BI4.x

Environment

SAP BusinessObjects Business Intelligence Platform 4.0 and above (Windows platform)

Resolution

When upgrading your installation to a Support package (eg: SP04) from a lower version, always use the update installer, but never use SP04 full build* for this scenario. A Support package full build is applicable to you in case you are starting a new installation.
*using a full build SP04 to upgrade from a lower version like SP02/FP03 can cause undesirable results and make the installation unsupported*

Best practices when performing an upgrade or patch install on your BI4 Platform:

Make sure to go over the latest support & feature pack release notes available at SAP Help Portal
Make sure to Turn OFF ALL servers Except essential servers: CMS, FRS (input/output),Tomcat (or other App server)

If needed, use a task manager, kill all processes* other than those essential servers listed above.
1. Using Windows Task Manager: Show all processes from all users, right click on the process you wish to terminate, select End Process Tree
2. Optionally you may wish to use another task manager such as process explorer to kill the processes
If you use the DB2 bundled CMS DB, do NOT kill that process*
Kill all JAVA.EXE processes that may still be running and taking up CPU / RAM (using task manager: right click, end process tree on each java process; or use process explorer)NOTE: This will ensure that there won’t be any issues with missing libraries which is primarily caused by the java processes locking up files not allowing them to be updated or deleted.

Once you have completed the above steps, look through the task manager to be sure all processes are still down and did not auto-recover, or restart.
Also make sure that the Anti-virus, Data Execution Prevention (DEP) and User Account Control (UAC) is turned off.

This section is specific to clustered or distributed environments :
Use this methodology up to BI 4.0 version Support pack 4 (SP04)[Sequentially]

Always run the update installer one server at a time [sequentially].
DO NOT run simultaneous update installs; run each update, on each tier independently - starting with the intelligence tier (CMS)

Update ALL intelligence tiers first (all machines with a CMS being actively used), then move on to the processing tier, then the web tier.

The installer updates metadata in the CMS database. Updating concurrently is known to cause failures in the installer and will severely impact the success rate of the install.
NOTE:This is because the installer did not support parallel patching of distributed environments until SP05.

For more details on this methodology, refer to the SAP kbase 1807514 on how to patch a BI4.0 cluster.
For patch specific prerequisites and documentation, refer to the update documentation at SAP Help Portal.

Use this methodology for BI 4.0 versions Support pack 5 (SP05) and above (including BI4.1 and above) [ using Parallel Patching ]
As of BI 4.0 support package 5 (SP05), patching of servers or nodes in a distributed environment can be performed in parallel. This methodology can also be referred to as parallel patching.

For more details on this methodology, refer to SAP kbase 2013616 on How to patch BI 4.x servers in a distributed BI Platform deployment simultaneously ( in parallel ).
For patch specific prerequisites and documentation, refer to the update documentation at SAP Help Portal.

An Interactive tool is available on the SCN to help you determine how best to patch your SAP BI 4.x server or cluster environments.

Keywords

BI 4.0 4.1 sp04 sp05 SP patch package installer intallation BI4.0 BI4.1 distributed cluster node sequential parallel

SAP BO - Setup and Configuration References

Purpose

Explain briefly the purpose of this page (Why it is useful to the community/reader). E.g. The purpose of this page is to clarify the understanding of the system logic and requirements in relation to.....

Overview

This should be an executive summary of the content and argument being made in the document. Basically a summary (not repeat) of the information you are explaining.

<Section Title>

This is the main body of your WIKI Page where you talk through the system logic or behavior you are explaining. Use pictures to emphasize the points you are trying to make or to illustrate the transactions/selection screens/reports etc.

<Another Section Title>

Same as the first section, this is also part of the main body of the WIKI. You can add as many sections as you require to make the information you are explaining as clear and simple to follow as possible.

Related Content

Related SAP Notes/KBAs

General Administration:1689163 – Repository Scanner tool (reposcan) in BI 4.x
1267338 – Repository Scanner tool (reposcan) in XI 3.1
1480761 – How to clean up Audit database in XI 3.1
1581890 – How to clean up Audit database in BI 4.x
1586824 – How to customize and add company logos in BI LaunchPad
1899321 – Migrating the CMS system database
1757132 – Support Package / Patch installation best practices in BI 4.x
1909881 – How to upgrade from one version of BI 4.x to another
1608960 – How to deploy / redeploy WAR files in BI 4.x using wdeploy command line tool
1475602 – Procedures for identifying and resolving security vulnerabilities in SAP BI
1645009 – How to set identical preferences for all users or specific groups in BI 4.x
1461109 – How do instance limits work in Business Objects Enterprise XI 3.x?
1573029 – How to verify SMTP connectivity via command line
1679970 – How to reset the Administrator password in BI 4.x
1320151 – How to reset the Administrator password in XI 3.1
1688743 – Oracle client configurations for Crystal Reports

Tracing:2103024 – Tracing in BI 4.x
1861180 – Creating an End-to-End trace in BI 4.x
1335757 – Tracing in XI 3.1
1734958 – How to keep more than five log files per server, BI 4.x

Server Management / Health:1339944 – How to delete an unused Node that is listed in the Central Management Console
1612745 – Crystal Reports RAS won’t start in BI 4.x, Unix / Linux
1542578 – How to Recreate Server Intelligence Agent (SIA)
1694041 – BI 4.x Consulting:- How to size the Adaptive Processing Server (APS) [Video]
1950573 – Is it Necessary to Split the Adaptive Job Server in BI4.x?
1868751 – Sporadic and Random scheduling failures, due to split Adaptive Job Servers
1463190 – Central Management Server (CMS) high memory utilization or crashes / restarts in XI 3.1
2168668 – CMS hangs or crashes during Groups Update process

Platform Search:1863726 – How does BI 4.x Platform Search application indexing work?
1640934 – How to safely use Platform Search Service in BI 4.x without overloading the server
1726392 – The number of Indexed Documents is always 0
2046675 – How to retrieve information regarding BI Platform Search application in BI 4.0-4.1
1844013 – How to configure the Platform Search Index location in a clustered environment
1932005 – PlatformSearchData folder size is too large
1787321 – Indexing of search services leads to database deadlock warnings in Event Logs

User Sessions:1862925 – Session handling and tuning
1837122 – How to increase session timeout values in BI 4.x
1668750 – Sessions not being released in BI 4.x
1996692 – Automate the Cleanup of Stale BI 4.x user sessions

Monitoring:1772632 – Explanation of Server Monitoring Metrics for BI 4.x
1741961 – How to move Monitoring from Derby Database to the Audit Database in BI 4.x
1833881 – Monitoring Service causes Adaptive Processing Server to run at 100% CPU

Daylight Savings Time:1448881 – Multiple instances spawned after DST time change
1986781 – Recurring instances' runtimes are adjusted +1 hour following DST (Spring)
1568718 – How to delete all failed instances in XI3.1 programmatically
1568239 – After DST, “Object could not be scheduled within the specified time interval”
2176887 – How will Leap Seconds affect my SAP BI environment?

Additional SAP Resources:1554331 – Interactive SAP BusinessObjects 4.x eLearning Tutorials
2026090 – How to install and configure Citrix GoToAssist from the SAP Service Marketplace
1922012 – Where to download BI Platform Support Tool, generate Landscape Report
1681036 – Using the survey script in to assist support, Unix / Linux
1983169 – Patch History Analysis Tool
1570271 – How to find Sizing information for SAP Business Objects Products
1515837 – How To submit Enhancement Requests for all BI products
2171560 – How to receive notifications when SAP Notes are updated (e.g. to track a fix)
2051288 – How to update the BI product version for a System in Service Marketplace
0083020 – What is Consulting? What is Support?
1054121 – The SAP Ecosystem in a Nutshell
1560818 – What information is required when creating a support message?
0067739 – Priorities of Support incidents

Distributed installation of SAP Business Intelligence and configuration of its web tier in Windows

Purpose:

The purpose of this page is to give a high level review of how custom installation is done in SAP Business Intelligence 4.0 in multiple machines with the web tier hosted on one host and the processing tier hosted on a different host and configuration of its web tier with the processing tier

Overview:

There are several types of deployment that can be possible with SAP Business Intelligence 4.0.

Standalone deployment
Distributed deployment
Split deployment
Cluster deployment

Based on these deployments the installation of the product is done accordingly.
In this page we are going to cover the Distributed deployment where the web tier is installed on a different host and the Business Objects processing tier is installed on a different host.
In the first section we cover the step by step installation of the web tier along with the screenshots for a Windows environment.
In the second section we cover the step by step installation of the processing tier components along with the screenshots.

In the third section we cover how the web tier is configured with the processing tier.
Business Objects communicates via certain ports which require that all servers have to reside in the same sub-net.
Before installing Business Objects, it is required to install Windows .NET Framework 3.5 Service Pack 1 or higher,
A complete installation requires between 4-6 hours, depending on network and system speed for every Business Objects Application Server.
The configuration requires between 3-4 hours, depending on the skill level of the installer

The above diagram explains what the webapp server or web tier components are and what the Business Object server components are:

A:Web Tier Installation

The Web Tier consists of a Web Server and a Web Application Server hosting on the same server.
Here the web server as well as the webapplication server is Tomcat 6.
We will use Tomcat 6.0 that comes with the BI 4.0 software for Web Application Server and the BO Java components.

Run the setup.exe.

Here you can select any other language other than English as per the requirement of the organization.
If the below “Prerequisite checking” shows any missing components in the “Status” column, please install/fix it and run the Setup.exe again.
Here in the screenshot we observe the following components.

1.Cannot be installed on the same machine

2.Cannot coexist with SAP Crystal Reports Server.

3.Administrative Privilege

4.Microsoft .NET Framework 3.5 or higher

5.Check suppressed reboot state.

6.Requirement to install Integrated database.

7.Windows version.

8.Platform memory Architecture Requirement.

For example, if .NET Framework 3.5.1 or higher was not found then you would see the “Missing” status.
If everything was correct on the server the all the Prerequisite checking components will show “Succeeded” statuses (see below).

Click Next button

Select “I accept…” and click Next button

Select Web Tier and click on Next

Select the Destination Folder you would want to install Tomcat

After selecting the features click on Next

First Check if the port 8080 is not occupied by any other application, then you can put port 8080 and click on Next

This is not a mandatory step.
If you do not have Wily Introscope select the second option "Do not integrate connectivity to Introscope Enterprise Manager" and click on Next.

Once you select the Next option you will be redirected to the next screen

Once the installation has completed you will be redirected to the next screen

Click on finish to complete the installation.
Now we need to verify the Tomcat Installation.
Open a browser and enter: http://servername:8080
If the Tomcat homepage (similar to the below) comes up then the installation was successful.

Management Tier & Processing Tier Installation

Install BusinessObjects BI Components

Please follow the instructions in this section to install the BO components for the management tier & processing tier on the dedicated BO server.
This server will serve as the CMS name for subsequent installation for future expansion of the servers in the cluster.

Note: During the time of this installation , the default database (SQLServer2008) shipped with the BI 4.0 was used. After the new BI 4.0 database is created than BO Admin can configure the CMS to point to any other database as per the need of their organization.

In this setup only the BO Components Server were installed. The Web/App Server was installed on the separate machine . Please see “Install Web/App Server” section for details

Click on the OK button.

If all the options are succeeded click on the Next button.

Click on Next.

Select the option "I accept the License Agreement"

You can enter the SAP Business Objects Keycode that you have received from the Licensing team and click on Next

Please select the language packs that you need to install during this installation.Here the language pack installed were English, Italian and Korean

Select the "Custom/Expand" option and click on Next

You can select the Destination Folder where you want to install Business Objects.

Select Platform Services under Servers option.and click on the Next option

Select the option "Start a new SAP BusinessObjects BI platform deployment"

The node name will be your host name by default and the port name would be 6410,click on Next

Select the CMS port as 6400 and click on Next

Specify the Business Objects Administrator word and the CMS cluster key and click on Next.
Once you click on Next ,it will start the installation.
Once the installation is completed ,you can go to Start >Programs>Business Objects>Central Configuration manager and Server Intelligence Agent .
Right click on Server Intelligence Agent and you will see the Cluster as shown in the next screenshot.

BusinessObjects BI System Configuration

In a split deployment environment, the web/app server and BO components server are installed and deployed separately. It will be needed to be manually configured for the web/app server to talk to the BO components server.
Configure connectivity between Web/App Server and BO Components serverogon to WEB Server and go to directory
F:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\BOE\WEB-INF\config\default
Copy BIlaunchpad.properties, CmcApp.properties , CrystalReports.properties, OpenDocument.properties files to F:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\BOE\WEB-INF\config\custom
Go to F:\Program Files (x86)\SAP BusinessObjects\Tomcat6\webapps\BOE\WEB-INF\config\custom

Launchpad Config:

Open BIlaunchpad.properties file in WordPad (notepad will not show in proper format)

Serach for below items and change accordingly

	Orginal	Changed
1	# application name app.name=BI launch pad app.name.greeting=BusinessObjects app.name.short=BI launch pad	app.name=BI DEV Launch Pad app.name.greeting=BusinessObjects app.name.short=FTI BI 4.0 Development
2	cms.default=servername:6400	cms.default=@BODevCluster

CMC Config:

Open CmcApp.properties

Search for “cms.default”

Old value cms.default=Servername:6400

New Value cms.default=@BODevCluster

Crystal reports Config:

Open CrystalReports.properties

Search for “cms.default”

Old value cms.default=Servername:6400

New Value cms.default=@BODevCluster

Open Document Config:

Open OpenDocument.properties

Search for “cms.default”

Old value cms.default=Servername:6400

New Value cms.default=@BODevCluster

Restart Tomcat:

Open Services in Server Manager and right click “Apache Tomcat 6.0.24” and Restart.

Please note: Here Servername is your hostname and the @BODevCluster is the value that I have used in the screenshots

Basis and others

1862925 - Session handling and tuning

1861180 - Customer instructions and best practice for collecting a BI Platform 4.x end to end trace

Collect SAP Client Plug-in logs

Collect BI server logs

Collect BI Platform web application logs

1475602 - Support procedures for identifying and resolving security vulnerabilities in SAP Business Objects products

1757132 - BI4 Support Pack Upgrade and Patch Install Best Practice Guide

Best practices when performing an upgrade or patch install on your BI4 Platform:

SAP BO - Setup and Configuration References

Purpose

Overview

<Section Title>

<Another Section Title>

Related Content

Related Documents

Related SAP Notes/KBAs

Distributed installation of SAP Business Intelligence and configuration of its web tier in Windows

Purpose:

Overview:

A:Web Tier Installation

Management Tier & Processing Tier Installation

BusinessObjects BI System Configuration