bi4.0 installation configuration tips

North America ServicesInfo DaysJuly 20-22, 2011Salt Lake City

© 2011 SAP AG. All rights reserved. 2

Services Transformation KPI‘s 2011

Be Essential – Make an Impact

EMPLOYEE MOTIVATION GROWTH MARGINCUSTOMER SUCCESS

• Partner certifications

• “Zero” Escalations inpartner-led projects*

• Value delivered

• High-value Services

• Zero Escalations

• Mobility

• Virtualization/CloudManagement

• Analytics/ In-Memory(HANA)

• Skill Transformationto new Delivery modeland Portfolio

• University GradProgram

INNOVATION PEOPLEVALUE ECO-SYSTEMENGINEERING

• Engineered Services,incl. RDS

• Custom Development

• Remote Delivery

8


SAP BusinessObjects BI4.0 Installation Configuration Tips

1.BI4.0 Server Deployment1.BI4.0 Components2.Installation Tips3.Patching Tips4.Firewall Configuration5.Server Configuration Tips6.Authentication and Security Tips2.BI4.0 Client Products Deployment1.BI4.0 Client Tools2.SAP Dashboard3.Crystal Reports 20114.Crystal Reports for Enterprise5.Live Office6.Analysis edition for MSOffice


SAP BusinessObjects BI4.0 Components

Server ProductsBI 4.0 Server

CCM, SIA, …wDeploy, Upgrade Manager ToolLife Cycle Manager, SubversionMobile, Analysis edition for Web, …Tomcat (Web Application Server)

Explorer Standard / Accelerated

Desktop ProductsBI 4.0 Client

Webi Rich Client, IDT, Design Tool, RCT, QaaWS, Widgets, …Crystal Reports for EnterpriseCrystal Reports 2011SAP DashboardPresentation DesignLive OfficeAnalysis edition for MS Office


BI4.0 Server Installation Tips

Check the Product Availability Matrix (PAM) for the supported platformCheck the pre-requisites for installHardware recommendations

When extracting the installer ensureThe path does not contain square brackets, or other special charactersThe path is not too deep

The install directory can NOTHave Unicode characters in its nameBe the same folder in which the installation program has been extracted. Do not install to the currentworking directory when running the installation program from the current working directory

BI Node WAS Node

8 Cores 4 Cores

16 GB RAM 8 GB RAM

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



Side-by-side installBI 4.0 and BOE Servers can be installed side-by-side on the same h/w provided h/w meets BI4.0pre-reqsRecommendation is to install BI4.0 on separate h/w

Determine multi languages requirements prior to installInstall all needed languages during the initial BI4.0 install.Adding a language later would require reinstall

Use Custom Install even if you want Full Install or Web Tier Install

Install required Database Access features on Web TierInstall SAPBW, and SAP Database Access features if SAP Authentication needed

Uncheck the Integrated Database feature when external database is used asCMS database

Use Fully Qualified Domain Name (FQDN) to avoid network communication relatedissues



Write down following values used during installCluster keyAdministrator user’s passwordLCM User ID/Password

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

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

Web Application Server must be 64-bit

Web Application server must use 64-bit JVM.run command java -d64 -version to verify JVM version.


BI4.0 Server Installation TipsWindows Platform

Enable Windows 8-dot-3 filename supportInstall Microsoft ODBC MDAC 2.8Install Microsoft .Net Framework 3.5 or higherDisable the Anti-Virus software and Firewall during installInstall user must be a member of Local Administrator’s groupInstall software through Add and Remove Programs interfaceInstall software on drive other than C:\ drive or OS driveKeep the install directory path short. Default install dir is C:\Program Files (x86)\SAPBusinessObjects.

Short install path without spaces, such as E:\SAPBOBJ, is recommendedSQLServer 2008 Express is default database for CMS and Audit Databases


BI4.0 Server Installation TipsUnix Platform

Install user must not be rootInstall user must not belong to the root groupInstall user must not belong to the 'Users' group

BOBJ user should not belong to BOBJ group, for example

Change dir to the install dir and launch the installer from there using full path tosetup.sh.

This will avoid you to have to enter the install pathThis is valid for patches installers as well

DB2 9.7 is default database for CMS and Audit DatabasesDefault DB2 gets install under /home/<user>/sqllib dirDefault install path for DB2 is not changeableUse an existing database for CMS (DB2 or any supported database)

Rather than installing DB2 with BI4.0 Install


BI4.0 Server - Patching

Consider following before rolling out a patchDoes it fix issues needed for deployment?Does it offer new features needed for deployment?Were Patch successfully tested in a sandbox environment ?

Apply patch/support patch for the components installed on the computer.Support Packages must be first installed on the Central Management Server(CMS)If deployment has multiple CMSs, the credentials for the first CMS that youupgrade must be used when upgrading the other clusters.Clear out the value in the following registry key, if patch pre-requisite fail to detectthe server reboot:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\PendingFileRenameOperations

If SQLServer is used as CMS and/or Audit database, please backup following filebefore patching the environment located in INSTALLDIR\SAPBusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64

sqlrule.dfa and sqlrule.llr filesAfter patching, you need to restore these two file for CMS to start


BI4.0 Server – Firewall Setting for Intranet

Configure Firewall for a reserved port range to used for BI4.0Port range (6400 to 6700 for example)Web Application Server port ( Tomcat by default use port 8080 for example)

Port range helps firewall monitoring easyBI4.0 ports are easily identified

Port range eases BI environment expansionNew services or server can use “free” ports from the port rangeAvoid Firewall port request every time a BI4.0 service is added

Bind each BI service to a specific port from the reserved port rangeEnsure ports are assigned for the Job Server Child processes as well

Job Server is bind to a port, say port 6410Job Server is configured to have 5 Child ProcessesBind each Child Process of this Job Server to a PortUse port numbers range next to Job Server portSpecify 6411-6415 ports for these 5 Child Processesadd switch -requestJSChildPorts 6501- 6504 to the Job Server command


BI4.0 Server Configuration Tips

BI launch pad login, by default, uses Enterprise AuthenticationUsers cant select or change default Authentication typeYou may want to change default parameters, such as

Change the default Authentication typeEnable Authentication Option if multiple Authentication options are needed

These configurable parameters are stored in properties filesDefault Properties files contain all supported parameters with default valuesCustom Properties file override parameters defined in the default properties filesUse Custom Properties files to override default parametersName Custom Properties file same as corresponding default properties file nameDefine only those parameters that you want to change

For example, to make Authentication visible for BI Launch Pad logon pageCreate custom BIlaunchpad.properties file with following parameter

authentication.visible=true

Backup custom properties file folder.Restore it after patching your environmentPatch would overwrite the properties files



Ensure custom BIlaunchpad.properties has following parameters correctlydefined

authentication.visibleauthentication.defaultcms.default

Ensure custom CrystalReports.properties has following parameter correctlydefined

cms.default

Ensure custom dsws.properties has following parameter correctly defineddomain

Ensure that Web Services application Access URL is a valid URLCMC > Applications > Web Services > Properties >Access URLhttp://<web application server>:<port>/dswsbobje



Configure Anti-Virus software to exclude The Web Application Server (Tomcat) dirWould significantly reduce Tomcat startup timeWould significantly reduce Web Application Deployment time

Update the JAVA JDK to recent versionCould improve performance of wDeploy, Upgrade Manager Tool etc.

Run dedicated AdaptiveProcessing Server (APS) containing only one ServiceSet Separate Services across APS instancesSet one APS for A-OLAP ( MDAS), for exampleSet APS heap size to 4GB. This is tuned by selecting dedicated APS and editing the “Command LineParameters” -Xmx value to be 4GB.

Default setting is –Xmx1gChange it to –Xmx4g.



Change the heap size and maximum perm size settings of JVM to-Xms128m -Xmx1024m -XX:MaxPermSize=512m

For TomcatJAVA_OPTS="-Xms128m -Xmx1024m -XX:MaxPermSize=512m“

For SAP NetWeaver AS Java 7.2, ensure that the maximum heap size is at least2048 megabytes.

JAVA_OPTS="-Xms128m -Xmx2048m -XX:MaxPermSize=512m”

Turn off unused servers in the CMC

Turn off monitoring in the CMC, if not needed


BI4.0 Server – Authentication & Security Tips

OLAP connections, by default, are not visible / accessible to non Administrators.Grant Access rights at Top LevelGrant Access rights at Common Connection folder under OLAP connections

Custom Access Levels(CALs)Don’t copy default CALsDefault CALs are multi-language objectsRequire Translation Manager Tool to rename the labelLCM may fail to promote to other environmentsCreate your own CALs

Use Enterprise User Groups to implement security modelCreate Enterprise user groups for each AD or LDAP user groupSet 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 urlhttp://<hostname>:8080/BOE/BI/logonNoSso.jsp


SAP BusinessObjects BI4.0 Installation Configuration Tips

1.BI4.0 Server Deployment1.BI4.0 Components2.Installation Tips3.Patching Tips4.Firewall Configuration5.Server Configuration Tips6.Authentication and Security Tips2.BI4.0 Client Products Deployment1.BI4.0 Client Tools2.SAP Dashboard3.Crystal Reports 20114.Crystal Reports for Enterprise5.Live Office6.Analysis edition for MS Office


BI4.0 Desktop – Client Tools

Check the Product Availability Matrix (PAM)for the supported platformCheck the pre-requisites for install

Administrative privileges for the account being used to run the installation program.

Hardware Recommendation2 Cores4 GB RAM50 GB DISK Space

When extracting the installer ensureThe path does not contain square brackets, or other special charactersThe path is not too deep

Determine which languages are required and install them all during the initial BI4.0install. To add or remove language support later requires that you remove and re-install SAP BusinessObjects Enterprise.

Client Tools are 32-bit applications, but supported on 64-bit operating systemsInstall 32-bit database driver s on Client Tools machinesSet screen resolution to at least 1,024 × 768 pixels for installer


BI4.0 Desktop – SAP Dashboard

Check the Product Availability Matrix for the supported platformCheck the pre-requisites for install

Dashboard Design requires keycodeInstall Adobe Flash 10.1 or higherInstall Adobe Acrobat 9.3To use BICS connectivity, ensure that system meets following pre requisites

Install SAP Frontend 720 with BI Add Ons.Dashboard Design requires Java and ABAP to connect to NetWeaver BW.

Administrative privileges for the account being used to run the installation program.

Disable the McAfee IPS and FirewallSide-by-side install:

SAP Dashboard upgrade the Xcelsius 2008SAP Dashboard and Xcelsius 2008 side-by-side install can be performed by

First Install SAP DashboardThen Install Xcelsius 2008

SWF fileadd the file to the trusted locations in Adobe Flash Player Settings ManagerCrossDomain policy file in the Web Application Server root


BI4.0 Desktop – Crystal Reports 2011

Check the Product Availability Matrix for the supported platformCrystal Reports 2011 is a 32-bit application, but supported on 64-bit operatingsystemsEnsure 32-bit version of data drivers are installedInstall user must be a member of Local Administrator’s group

The installation process creates registry entries and may update some system files that requireAdministrator rights.

Crystal Reports 2011 requires keycodeUse all upper case for license key code

On Windows XP OS, Remove following MSFT KBs that conflict with the CR 2011installation package.

KB2467175KB2467174KB2467173

Verify that the value of the "path" setting at the following registry key:HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI4.0\SharedTools\keydecoder.dll is similar to "C:\Program Files (x86)\SAP BusinessObjects\SAPBusinessObjects Enterprise XI 4.0\win64_x64\keydecoder.dll".


BI4.0 Desktop – Crystal Reports for Enterprise

Check the Product Availability Matrix for the supported platformCrystal Reports for Enterprise is a 32-bit application, but supported on 64-bitoperating systemsEnsure 32-bit version of data drivers are installedInstall user must be a member of Local Administrator’s group

The installation process creates registry entries and may update some system files that requireAdministrator rights.

Crystal Reports for Enterprise requires keycodeUse Crystal Reports 2011 keycodeUse all upper case for license key code

Crystal Reports for Enterprise connectivity to BI4.0 systemVerify http://<host>:8080/dswsbobje/ is accessibleEnsure \webapps\dswsbobje\WEB-INF\classes\dswsbobje.properties file has domain parameter setto the proper CMS server name and CMS port.

domain=yourcmsname:yourcmsportEnsure that the following services ports have been opened through the firewall: Input FRS, CMS, andConnection Server.Configure connection to use SSL, if SSL is used


BI4.0 Desktop – Live Office


Microsoft .NET Framework 3.5 or higher is installed.Microsoft Office 2003/2007/2010 is installedWith Microsoft Office 2003, must Install update for Office 2003 (KB907417),Administrative privileges for the account being used to run the installation program.


BI4.0 Client – Analysis edition for MS Office


MS OfficeMicrosoft Office 2010 (Excel and PowerPoint), orMicrosoft Office 2007 (Excel and PowerPoint) , orMicrosoft Office 2003 (Excel)

Microsoft .NET Framework 2.0 Redistributable PackagePrimary Interop Assemblies for Microsoft Office


Further Information

Product DocumentationProduct Availability Matrix (PAM)Installation Guide, Administration GuideMater Guide, Deployment Planning GuideRelease Notes

BOPedia Forumhttps://cw.sdn.sap.com/cw/docs/DOC-124167https://cw.sdn.sap.com/cw/docs/DOC-139541https://community.wdf.sap.corp/sbs/groups/bi-launchhttps://cw.sdn.sap.com/cw/docs/DOC-139781https://cw.sdn.sap.com/cw/docs/DOC-139619https://cw.sdn.sap.com/cw/thread/18455https://cw.sdn.sap.com/cw/thread/18431

https://cw.sdn.sap.com/cw/docs/DOC-124167


https://community.wdf.sap.corp/sbs/groups/bi-launch



https://cw.sdn.sap.com/cw/thread/18455

https://cw.sdn.sap.com/cw/thread/18431

Thank You!

Contact information:

Dhirendra GehlotBI Competency [email protected]

mailto:[email protected]


© SAP

Copyright 2007 SAP AGAll rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or

other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services

sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu

Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten

Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder

ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

bi4.0 installation configuration tips

Documents