Sizing and Deploying SAP BI 4 and SAP Lumira
Properly deploying your SAP BusinessObjects BI4 or SAP Lumira landscape involves more than punching some numbers into a calculator and installing the right number of servers. Approaching this from a BI systems perspective means understanding how your BI system works and making intelligent decisions to ensure good system performance and stability.
This site contains resources to help you properly size and deploy SAP BusinessObjects BI4 and SAP Lumira in both production and non-production scenarios. It is important to remember that these resources are not replacements for other existing documentation such as the Installation and Administration Guides where they provide additional information based on generally accepted best practices, internal lab tests, and customer feedback.
These resources are not a replacement for a proper sizing exercise performed by an expert BI consulting architect that can glean the nuances of your particular landscape from discussions with your stakeholders and combine that information with the resources here and his or her own personal learnings.
|Primary Sizing and Deployment Resources for SAP Lumira|
Sizing HANA applications is a very new type of activity. Following the sizing guide is very important for a successful deployment.
- SAP Lumira Sizing Guide Updated June 2015!
|Primary Sizing and Deployment Resources for SAP BI 4|
Every deployment requires a sizing exercise. It is critical to fully read and understand the SAP BI 4 Sizing Companion Guide before using SAP BI 4 Sizing Estimator tool. Without properly understanding this material, the outputs of the tool will be invalid.
- SAP BI 4 Sizing Guide
- Updated June 2013 with all new content and sizing methodology!
- Revised February 2014 with many performance-related updates
- SAP BI 4 Resource Usage Estimator (aka Sizing Estimator)
- Updated June 2013
- BI 4 Sizing Webinar (October 2013)
- SAP Note 1742488 - SBOP Explorer 4.0 SP3 Sizing and Performance Information
- Improve BI 4.0 P&R by using Java's Parallel Garbage Collector
- Tuning Web Intelligence: Query Stripping and Server Settings
Reduce back-end load and Improve the User Experience by 'splitting' Web content delivery: Team-up Apache and Tomcat, having them each do what they do best. Apache serves up the static content and does compression natively while Tomcat runs the Web apps. Multiple articles:
- Improving the User Experience with Apache (aka the 'Apache Split') Significant performance improvements possible while reducing load on your Web tier. Update for BI 4.1 and Apache 2.4
- Quick Guide to implementing the Apache Split for BI 4.1 and Apache 2.4
- Platforms Support Guide For SAP BusinessObjects Products
- Additional information to supplement the Platform Availability Matrix (PAM)
- BI 4.1 PAM
- Best Practices for SAP BusinessObjects BI 4 Adaptive Processing Servers
- Splitting the Adaptive Processing Server (video)
- How to split the APS into multiple service instances that are dedicated to specific tasks
- Large-Scale SAP BusinessObjects BI 4 Platform Deployment COIL Whitepaper
- Description of the "MONSTA" project that simulates a large number of BI users on a multi-node deployment
- Evaluating Selected Java Best Practices for SAP BusinessObjects BI 4 on vSphere
- BI4 Pattern Books - Deploying SAP BusinessObject BI platform in the real world