of 27/27
© 2013 SAP AG or an SAP affiliate company. All rights reserved. 1 SAP BusinessObjects BI 4.1 Upgrade Webinar Series BI 4.1 Deployment Best Practices Presenter: Harjeet Judge SAP Customer Experience Group Brought to you by the Customer Experience Group

SAP #BOBJ #BI 4.1 Upgrade Webcast Series 4: BI 4.1 Deployment Best Practices

  • View
    912

  • Download
    6

Embed Size (px)

DESCRIPTION

http://spr.ly/BI41_Migration_Webinars - Obtain key information about SAP BusinessObjects BI 4.1 deployment best practices - including upgrade planning, architecture and sizing, and deployment overviews. Also get some configuration tips on optimizing BI server tiers. • Learn about administrative best practices for rolling out a productive landscape • Understand how the architecture works together, what can be decoupled, and what cannot • Take a holistic view of systems administration from inception to delivery For more on upgrading to SAP BusinessObjects BI 4.1, visit http://www.sapbusinessobjectsbi.com

Text of SAP #BOBJ #BI 4.1 Upgrade Webcast Series 4: BI 4.1 Deployment Best Practices

  • 1. 2013 SAP AG or an SAP affiliate company. All rights reserved.1SAP BusinessObjects BI 4.1 Upgrade Webinar SeriesBI 4.1 Deployment Best PracticesPresenter: Harjeet JudgeSAP Customer Experience GroupBrought to you by the Customer Experience Group

2. 2013 SAP AG or an SAP affiliate company. All rights reserved.2We bring to you all that you need to successfully upgrade to the SAP BusinessObjects BI Platform 4.1.You can find a BI 4.1 Upgrade Overview page on SCN at: http://scn.sap.com/docs/DOC- 56525Webinars also complement these published resources: http://scn.sap.com/docs/DOC- 56308SAP BusinessObjects BI Platform 4.1 Upgrade Enablement 3. 2013 SAP AG or an SAP affiliate company. All rights reserved.3Web Tier DeploymentIntelligence Tier DeploymentProcessing Tier DeploymentSystem Configuration Wizard DemoHigh Availability and Load Balancing ScenariosQ&AAgenda 4. 2013 SAP AG or an SAP affiliate company. All rights reserved.4BI 4 is all 64-bitBOE 3.1 was designed to squeeze the whole suite within a 32-bit architectureBI 4 is designed to take advantage of modern hardware and RAM (64-bit addressing)BI 4 can stretch out and is no longer artificially limited for resourcesBI 4 is architecturally different than 3.1BOE 3.1 was a collection of applications with their own connectivity stacksBI 4 components share a new common Semantic Layer for data connectivityBI 4 is designed as a first-class and highly integrated SAP client for BIBI 4 is bigger because it includes new services and applicationsBI 4 is designed for modern infrastructure dont expect to run on the same hardwareSAP BI 4.x is not a technical upgrade from BOE 3.1 or XI R2Conduct sizing exercise using the Sizing Estimator 5. 2013 SAP AG or an SAP affiliate company. All rights reserved.5What are the conceptual tiers in a BIPlatform ? 6. 2013 SAP AG or an SAP affiliate company. All rights reserved.6Web Tier DeploymentIntelligence Tier DeploymentProcessing Tier DeploymentSystem Configuration Wizard DemoHigh Availability and Load Balancing ScenariosQ&AAgenda 7. 2013 SAP AG or an SAP affiliate company. All rights reserved.7Background Need for Web Tier TuningXIR2XI3.1BI4.0 8. 2013 SAP AG or an SAP affiliate company. All rights reserved. 8Optimizing BI Server TiersWeb Server / Web TierBI 4.1Tomcat 7 + SAP JVM 6BI 4.1Apache 2.4 +Tomcat 7 +JVM 7~25% or better improvement in delivery of static content Improving the User Experience in SAP BI Platform 4.0 with Apache http://scn.sap.com/docs/DOC-6191 9. 2013 SAP AG or an SAP affiliate company. All rights reserved.9Optimizing BI Server Tiers Web Application Server (Java)The embedded Tomcat web application server now utilizes SAP JVM 1.6.0_37 as of the first release of BI4.1Tomcat 7 and SAP JVM 1.6.0_37 standardAs of Java 7, a new garbage collector called the Garbage First Collector (or GC1) is enabled and is optimal for use with multi-CPU servers. You can find details on GC1 as it pertains to BI4.x here.Java 7 + GC1GC1 simplifies garbage collection and can improve performance for java application servers running on multi-core systemsKey MessageRoadmap for SAPJVM includes plans to update to Java 7. BI4.2?Key Message+ Be generous with Tomcats memory pool! (configuration) 10. 2013 SAP AG or an SAP affiliate company. All rights reserved.10Web Tier DeploymentIntelligence Tier DeploymentProcessing Tier DeploymentSystem Configuration Wizard DemoHigh Availability and Load Balancing ScenariosQ&AAgenda 11. 2013 SAP AG or an SAP affiliate company. All rights reserved.11Understanding the Management / Intelligence tier. 12. 2013 SAP AG or an SAP affiliate company. All rights reserved. 12Optimizing BI Server TiersManagement/ Intelligence TierCentral Management Server System Database / RepositoryMetadataSecurityServer InfoKey Message: The CMS must have sufficient connections to the system database, else pendingrequests are queued, causing degradation in user-response times. Increase up to 50 if poss. 13. 2013 SAP AG or an SAP affiliate company. All rights reserved. 13Optimizing BI Server TiersManagement/ Intelligence TierCMS Objects in CacheMax objects in cache increased from 10K to 100K default in BI 4.0Increasing this value corresponds to higher memory consumptionfrom CMSIncrementing with System Database sizes larger than 100K objectsmay improve CMS performance-maxobjectsincache 250000 14. 2013 SAP AG or an SAP affiliate company. All rights reserved.14Web Tier DeploymentIntelligence Tier DeploymentProcessing Tier DeploymentSystem Configuration Wizard DemoHigh Availability and Load Balancing ScenariosQ&AAgenda 15. 2013 SAP AG or an SAP affiliate company. All rights reserved.15It can host a number of services simultaneouslyOut of box configuration has all services in a single APS instanceDefault install is to get system up and running and configurable for your scenariosConfigured for small systems Dev, Test, Trial, limited deploymentsCustomers are not expected to go to production without re-configurationFor production, host important services in their own APSIncreased throughput, improved scalability, and better response timesSlightly higher memory consumption due to more service containers (one per APS)Each service has its own memory and processor requirements:New in SAP BI 4.x: Adaptive Processing Service (APS)The BI Sizing Guide and BI Platform Installation Guide contain detailed technical information on specific services that is critical to configure and size correctly 16. 2013 SAP AG or an SAP affiliate company. All rights reserved.16Troubleshooting and getting support is going to be painful22 services in one APS makes debugging that APS almost impossibleTypically need to create additional APSes before proceeding with SupportSystem resources harder to manage what does a 16 GB process look like?You may experience non-optimal system behaviorLack of service isolation can magnify otherwise imperceptive operationsExample: Normal Java garbage collection processes:Reclamation of freed memory for 22 services is computationally largeJVM may need to focus on collection instead of executing processesMagnified wait times for the APS can affect entire system performanceWhats wrong with one APS if I have enough RAM?Proper deployment is not about just adding up the numbers, it is about making better decisions based on the numbers you have 17. 2013 SAP AG or an SAP affiliate company. All rights reserved.17Using the System Configuration Wizard (Demo)New in 4.1: Wizard performs essential post-install configurationQuick way to configure whole system consistentlyResponse + log files are generated each run .SCW can be invoked in script modeResponse file can be edited, and rerun using SCW.bat 18. 2013 SAP AG or an SAP affiliate company. All rights reserved.18Tailoring specific Services & ApplicationsDeploy only one server for Lifecycle Management ServiceMost heavy lifting is not handled by this service anywayLifecycle Management Job service deployed in multiple serversCan scale out for handling more loadPut Security Token Service (STS) alongside DSL_Bridge for BW SSO.Auditing and Monitoring applications can be enable/disabled.Build-up scope of Search Index gradually 19. 2013 SAP AG or an SAP affiliate company. All rights reserved.19Poorly provisioned databases will have an invisible effectCMS DB latencies have a cascading effect one BI admins cant see!Ensure that each reporting database has I/O path are large enoughI/O bottlenecks disk and network have severe effectsWorst thing you can do to an I/O intensive application is to starve it for dataBeing on an underperforming file server can starve the BI systemPatch your SAP BW systems incremental performance gains can be bigMany poorly performing WEBI instances can be traced back to a lack of BW patchesEnsure virtualization hosts can handle aggregate requirementsPutting 5 processing server VMs on one host means the host must have at least 5x the IO capability and 5x the RAM!Role of external systems to deployment 20. 2013 SAP AG or an SAP affiliate company. All rights reserved.20Keeping up to date on BI system patching is importantUpdates almost always have stability and performance improvementsDo not need to apply every patch, but at least every minor version and evaluate every support packMulti-node patchingNot always fun ensure you are orchestrating the patches to minimize downtimeParallel Patching available as of BI 4.0 SP05First, update in parallel all CMS host servers.Second, update in parallel all non-CMS host servers.Role of maintenance strategy in deployments 21. 2013 SAP AG or an SAP affiliate company. All rights reserved.21Web Tier DeploymentIntelligence Tier DeploymentProcessing Tier DeploymentSystem Configuration Wizard DemoHigh Availability and Load Balancing ScenariosQ&AAgenda 22. 2013 SAP AG or an SAP affiliate company. All rights reserved.22Scale Up or Scale Out?Scaling up has its limits, but machines are too large for single processes anymorePutting 5 WEBI servers on a machine might make sense but watch out for bottlenecks (i.e. I/O)!Requires planning and analysis of your scenarios:If you schedule Crystal Reports mostly at night, the CR Job/Processing Services may be run on the same machine as the Web Intelligence ServerIf CR users are actively analyzing data, putting CR and WEBI on the same server is a bad idea since they are both resource intensiveScale out more of an option than beforeVirtualization enables splitting a lot easier as there isnt incremental hardware cost.Design principles for scale out are no different than other enterprise softwareHomogeneous vs. Heterogeneous Nodes? 23. 2013 SAP AG or an SAP affiliate company. All rights reserved.23Single Server DeploymentsWeb Application ServerBusinessObjects Enterprise serversFRS Root FolderDatabase server hosting CMS system databaseSuited for a small organizationAssuming you have proper backup, a disaster may lead to long periods of unavailability.Trusted disaster recovery and back up strategies are critical to regaining availability.Vertical DeploymentWeb Client 24. 2013 SAP AG or an SAP affiliate company. All rights reserved.24Scale OutBI ClusterSAN StorageDatabase ClusterDefault Servers running on all machines 25. 2013 SAP AG or an SAP affiliate company. All rights reserved.25Scale Out Web Server to server static contentWeb ServerServes static content or redirector onlyWeb ClientBI Server(s)Web Application ServerServes dynamic content only 26. 2013 SAP AG or an SAP affiliate company. All rights reserved.26Scale Out Web Server to server static contentWeb ClientWeb Server FarmStatic content or redirector onlyClustered Application Servers (Session Replication)Business Intelligence ServersHardware redirector (Load Balancer) 27. 2013 SAP AG or an SAP affiliate company. All rights reserved.27SAP BusinessObjects BI 4.1 Upgrade Webinar SeriesBI 4.1 Deployment Best PracticesQ & ABrought to you by the Customer Experience Group