0506 SAP BusinessObjects Business Intelligence 40 Installation Deployment Tips

7/28/2019 0506 SAP BusinessObjects Business Intelligence 40 Installation Deployment Tips

1/21

SAP BusinessObjects BI 4.0Installation Deployment TipsDhirendra Gehlot

Shivaji Patnaik

[


2/21

[ Disclaimer

This presentation is based on presentes personal and shared

experiences. The tips and recommendations shared here

represent presenters learning and collaboration while workingon SAP BusinessObjects BI4.0 projects . The tips or

recommendations presented here are not SAPs official

recommendations or best ractices.

Real Experience. Real Advantage. 2


3/21

[ Learning Points

Understand key pre-install considerations for BI4.0

Learn how to get BI4.0 installed right the very first time

Know configuration and security tips



4/21

[ SAP BusinessObjects BI4.0 Installation Tips

1. BI4.0 Platform

1. BI4.0 Platform Tiers

2. BI4.0 Platform Components2. BI4.0 Server Deployment

1. Installation Tips

2. Patchin Ti s

Real Experience. Real Advantage.

3. Firewall Setting Tips

4. Server Configuration Tips

5. Authentication and Security Tips


5/21

[ SAP BusinessObjects BI 4.0 Platform

Client Tier

Web Tier

Management Tier


Storage Tier

Processing Tier

Data Tier


6/21

[ SAP BusinessObjects BI4.0 Components

Client Tier (Desktop Products)

BI 4.0 Client

WebIntelligence Rich Client

Information Design Tool

Design Tool

Report Conversion Tool, QaaWS, Widgets,


Crystal Reports 2011

SAP Dashboard

Live Office

Analysis edition for MS Office


7/21

[ SAP BusinessObjects BI4.0 Components

Web Tier

Web Server / Web Application Server

Tomcat web application server is bundled with binaries

Server Platform (Management/Storage/Processing Tiers)

BI 4.0 Server


,

CMS and other server

wDeployTool

Upgrade Manager Tool, Life Cycle Manager, Subversion

Mobile, Analysis edition for Web,

Data Tier

Reporting Data Sources

SAP HANA, SAP BW, MSSQLServer, ..


8/21

[ BI4.0 Server Installation Tips

Check the Product Availability Matrix (PAM) for the supported platform

Check installation pre-requisites

Hardware recommendations

BI Node WAS Node

8 Cores 4 Cores

16 GB RAM 8 GB RAM


Min Disk space for Server install

14 GB English only / 16 GB All Languages

Min Disk space for Client install

4 GB English only / 8 GB All Languages

Plus Disk space for Binaries, SPs, FPs, FRSs etc

100 GB Free Disk Space 20 GB Free Disk Space

20 GB Free Disk Space for TEMP Dir 10 GB Free Disk Space for TEMP Dir


9/21


Install CMS/Audit Database on a server other than BI4.0 server

Install Web Application Server on a server other than BI4.0 server

Host Operating system must be 64-bit

Web Application Server must be 64-bit

Web Application server must use 64-bit JVM.


Determine multi languages requirements prior to install

Install all needed languages during the initial BI4.0 install.

Adding a language later would require reinstall


10/21


When extracting the installer ensure

The path does not contain square brackets, or other special characters

The path is not too deep

The install directory can NOT

Have Unicode characters in its name

Be the same folder in which the installation program has been extracted. Do not

install to the current workin director when runnin the installation ro ram from


the current working directoryUse Custom Install even if you want Full Install or Web Tier Install

Install required Database Access features on Web Tier

Install SAPBW, and SAP Database Access features if SAP Authentication needed

Install theJava Web Applications feature It installes the WAS configuration files required for wdeploy


11/21


Install SubVersion only on Only ONE server

SubVersion can not be clustered

Configure LCM ClearCase Service to run on the SubVersion servers

LCM ClearCase Service is bundled with Adaptive Processing Server

LCM ClearCase Service talks with SubVersion


,

User External Database as CMS database

Uncheck the Integrated Database feature when external database is used as CMS

database

Write down following values used during installCluster key

Administrator users password

LCM User ID/Password


12/21

[ BI4.0 Server Installation Tips Windows Platform

Enable Windows 8-dot-3 filename support

Minimum screen solution of1024 768

Install Microsoft ODBC MDAC 2.8

Install Microsoft .Net Framework 3.5 or higher

Disable the Anti-Virus software and Firewall during install

Install user must be a member ofLocal Administrators group


nsta so tware t roug an emove rograms nter ace

Install software on drive other than OS drive or C:\ drive

Keep the install directory path short.

Default install dir is C:\Program Files (x86)\SAP BusinessObjects

Short install path without spaces, such as E:\SAPBOBJ, is recommended

SQLServer 2008 Express is default database for CMS and Audit Databases

On Windows Server 2008, ifUAC (User Account Control) is enabled, then right-click

setup.exe and select Run as administrator.


13/21

[ BI4.0 Server Installation Tips Unix Platform

Install user must not be root

Install user must not belong to the root group

Install user must have a HOME directory

Install user must NOT belong to the 'Users' group

BOBJ user should not belong to BOBJ group, for example

Ensure that en_US.utf8 language pack is install on the server


_ _ .

Verify that setup.sh and other files are executable

DB2 9.7 is default database for CMS and Audit Databases

Default DB2 gets install under /home//sqllib dir

Default install path for DB2 is not changeable

Use an existing external database for CMS (DB2 or any supported database)


14/21

[ BI4.0 Server Patching Tips

Consider following before rolling out a patch

Does it fix issues needed for deployment?

Does it offer new features needed for deployment?

Does it get affected for Forward Fit rule? (Details on the bottom of Maintenance

schedule page)

Test patch in a sandbox environment

A l atch/su ort atch for the com onents installed on the com uter.


Support Packages must be first installed on the Central Management Server If deployment has multiple CMSs, the credentials for the first CMS that you upgrade must

be used when upgrading the other clusters.


15/21

[ BI4.0 Server Firewall Setting for Intranet

Configure Firewall for a reserved port range to used for BI4.0

Port range (6400 to 6700 for example)

Web Application Server port ( Tomcat by default use port 8080 for example)

Port range helps firewall monitoring easy

BI4.0 ports are easily identified

Port range eases BI environment expansion


Avoid Firewall port request every time a BI4.0 service is added

Bind each BI service to a specific port from the reserved port range

Ensure ports are assigned for the Job Server Child processes as well


16/21

[ BI4.0 Server Configuration Tips

Properties files store configurable parameters

Authentication, Cluster, SSO, etc

Use Custom Properties files to override default parameters

Name Custom Properties file same as corresponding default properties file name

Define only those parameters that you want to change


,

Create custom BIlaunchpad.properties file with following parameter

authentication.visible=true

Backup custom properties file folder.

Restore it after patching your environment

Patch would overwrite the properties files


17/21


Ensure custom BIlaunchpad.properties has following parameters correctly defined

authentication.visible

authentication.default

cms.default

Ensure custom CrystalReports.properties has following parameter correctly defined


.

Ensure custom dsws.properties has following parameter correctly defined

domain

Ensure that Web Services application Access URL is a valid URL

CMC > Applications > Web Services > Properties >Access URL

http://:/dswsbobje


18/21


Configure Anti-Virus software to exclude The Web Application Server (Tomcat) dir

Would significantly reduce Tomcat startup time

Would significantly reduce Web Application Deployment time

Would significantly reduce install/patching time

Run dedicated AdaptiveProcessing Server (APS) containing only one Service


Set one APS for A-OLAP ( MDAS), for example

Set APS heap size to 4GB. This is tuned by selecting dedicated APS and editing the

Command Line Parameters -Xmx value to be 4GB.

Default setting isXmx1g

Change it toXmx4g.


19/21

[ BI4.0 Server Authentication & Security Tips

OLAP connections, by default, are not visible / accessible to non Administrators.

Grant Access rights at Top Level

Grant Access rights at Common Connection folder under OLAP connections

Custom Access Levels(CALs)

Dont copy default CALs

Create your own CALs


Create Enterprise user groups for each AD or LDAP user group

Set AD or LDAP user group as a member to corresponding Enterprise user group

Setting AD or LDAP user groups, ensure to have a single parent user group.

To minimize the maintenance work to add user groups in BI 4.0 CMS

Ensure that the Max header size for Tomcat is set to a number divisible by 8

The non SSO page url

http://:/BOE/BI/logonNoSso.jsp


20/21

[ Further Information

Product Documentation

Product Availability Matrix (PAM)

Installation Guide, Administration Guide

Mater Guide

Deployment Planning Guide

Release Notes



21/21

[

] Thank you for participating.SESSION CODE:

Please remember to complete and return your

evaluation form following this session.

For ongoing education on this area of focus, visit the

Year-Round Community page at www.asug.com/yrc


0506

Documents

0506 SAP BusinessObjects Business Intelligence 40 Installation Deployment Tips