[ SAP BusinessObjects BI 4.0 Installation Deployment Tips Dhirendra Gehlot Shivaji Patnaik
[ Disclaimer This presentation is based on presentes personal and shared experiences. The tips and recommendations shared here represent presenters learning and collaboration while working on SAP BusinessObjects BI4.0 projects. The tips or recommendations presented here are not SAP s official recommendations or best practices. 2
[ 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 3
[ SAP BusinessObjects BI4.0 Installation Tips 1. BI4.0 Platform 1. BI4.0 Platform Tiers 2. BI4.0 Platform Components 2. BI4.0 Server Deployment 1. Installation Tips 2. Patching Tips 3. Firewall Setting Tips 4. Server Configuration Tips 5. Authentication and Security Tips
[ SAP BusinessObjects BI 4.0 Platform Client Tier Web Tier Management Tier Storage Tier Processing Tier Data Tier
[ 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 for Enterprise Crystal Reports 2011 SAP Dashboard Live Office Analysis edition for MS Office
[ 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 CCM, SIA CMS and other server wdeploy Tool Upgrade Manager Tool, Life Cycle Manager, Subversion Mobile, Analysis edition for Web, Data Tier Reporting Data Sources SAP HANA, SAP BW, MSSQLServer,..
[ 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 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 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
[ BI4.0 Server Installation Tips 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. Use Fully Qualified Domain Name (FQDN) to avoid network related issues Determine multi languages requirements prior to install Install all needed languages during the initial BI4.0 install. Adding a language later would require reinstall
[ BI4.0 Server Installation Tips 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 working directory when running the installation program from the current working directory Use 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 the Java Web Applications feature It installes the WAS configuration files required for wdeploy
[ BI4.0 Server Installation Tips 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 See KBA or SAP Notes: 1628235, 1628590 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 install Cluster key Administrator user s password LCM User ID/Password
[ BI4.0 Server Installation Tips Windows Platform Enable Windows 8-dot-3 filename support Minimum screen solution of 1024 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 of Local Administrator s group Install software through Add and Remove Programs interface 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, if UAC (User Account Control) is enabled, then right-click setup.exe and select Run as administrator.
[ 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 Set LC_ALL and LANG environment variables to en_us.utf8 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/<user>/sqllib dir Default install path for DB2 is not changeable Use an existing external database for CMS (DB2 or any supported database)
[ 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 Apply patch/support patch for the components installed on the computer. 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.
[ 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 New services or server can use free ports from the port range 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
[ 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 For example, to make Authentication visible for BI Launch Pad logon page 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
[ BI4.0 Server Configuration Tips Ensure custom BIlaunchpad.properties has following parameters correctly defined authentication.visible authentication.default cms.default Ensure custom CrystalReports.properties has following parameter correctly defined cms.default 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://<web application server>:<port>/dswsbobje
[ BI4.0 Server Configuration Tips 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 Separate Services across APS instances 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 is Xmx1g Change it to Xmx4g.
[ 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) Don t copy default CALs Create your own CALs Use Enterprise User Groups to implement security model 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://<webhostname>:<port>/boe/bi/logonnosso.jsp
[ Further Information Product Documentation Product Availability Matrix (PAM) Installation Guide, Administration Guide Mater Guide Deployment Planning Guide Release Notes
[ ] Thank you for participating. 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 [ SESSION SESSION CODE: 0506 21