Best Practices for SAPBO BI 4.0 Adaptive Processing ... - archive SAP

Best Practices for SAPBO BI 4.0 Adaptive Processing Servers

Applies to: SAP BusinessObjects BI 4.0,

Summary: This whitepaper summarizes best practices, tuning, configuration and troubleshooting to help make your SAP BusinessObjects Adaptive Processing Server perform best. There are plenty of additional whitepapers / notes which delve into significant detail – this whitepaper is meant to be a handy summary for an administrator familiar with SAP BusinessObjects Enterprise BI4.0 platform. Document Owner:

Jan De Vilder Senior Certified BI / MoBI Consultant SAP Belgium – Luxembourg SAP Levallois - France [email protected]

Company: SAP Last update:

November 26 2012

SAP COMMUNITY NETWORK © 2012 SAP AG

SCN – http://scn.sap.com/docs/DOC-31711 1


Version November 26th, 2012

Contents 1

Document update history ...................................................................................................................... 4

2

Background ........................................................................................................................................... 4

3

Architecture overview ............................................................................................................................ 5

4

Adaptive Processing Server Services ................................................................................................... 6

5

Best practices for SAP Business Objects BI4.0 server configuration ................................................... 9 5.1

Introduction............................................................................................................................................ 9

5.2

Adding multiple APS servers................................................................................................................. 9

5.2.1

How to create a new APS server in the CMC ................................................................................................ 9

5.2.2

Cloning APS servers ................................................................................................................................... 11

5.3

Starting point after installing BI4.0 ...................................................................................................... 12

5.3.1

CLONE the original Adaptive Processing Server (APS) .............................................................................. 12

5.3.2

Add a dedicated APS for DSL BRIDGE Service .......................................................................................... 12

5.3.3

Add a dedicated APS for SEARCH Index .................................................................................................... 12

5.3.4

Add a dedicated APS for ANALYSIS (Multi Dimensional Analysis Service - Analysis for OLAP) ................ 13

5.3.5

Add dedicated APS for ALL OTHER NECESSARY Services ...................................................................... 13

6

Other APS servers to consider............................................................................................................ 14 6.1

Separate APS for DSLBridge Service ................................................................................................. 14

6.1.1

DSL component in Crystal Reports for Enterprise and Dashboards ............................................................ 14

6.1.2

Isolating DSLBRIDGE: ................................................................................................................................ 15

6.1.3

Memory options for DSLBRIDGE: ............................................................................................................... 15

6.2

Separate APS for Search Service ....................................................................................................... 16

6.3

Separate APS for Analysis .................................................................................................................. 17

6.4

Separate APS for Life Cycle Manager (LCM) ..................................................................................... 17

6.5

Configure the APS to handle concurrent publications. ....................................................................... 18

6.6

Separate APS for Heavy Visualisations (Charting) ............................................................................. 18

6.7

Other APS to consider ........................................................................................................................ 19

6.8

Separate APS for unnecessary Services ............................................................................................ 19

6.9

Keep the original APS ......................................................................................................................... 19

6.10 General APS recommendations ......................................................................................................... 19 6.11 Command Line Parameters ................................................................................................................ 20 6.12 Overview of available JVM –X parameters ......................................................................................... 21 7

Configuring, monitoring and tracing APS ............................................................................................ 22 7.1

Analyzing APS memory consumption by Heap Dump generation ..................................................... 22

7.1.1

Heap Dump generation:............................................................................................................................... 22

7.1.2

Using MAT to Analyze SAP ME Heap Dumps: ............................................................................................ 22

7.2

Stop unnecessary servers ................................................................................................................... 22

7.3

Multi-instances deployment................................................................................................................. 23

7.4

Configuring BICS Result Chunk Sizes (BICS) .................................................................................... 23

7.5

Adapting the parameters for LOV chunk size ..................................................................................... 24

7.5.1

For Interactive Analysis Desktop (i.e. WebI Rich Client): ............................................................................ 24

7.5.2

For WebIntelligenceProcessingServer:........................................................................................................ 25

7.5.3

For DSL-BICS layer: .................................................................................................................................... 25

7.6

How to monitor DSLBRIDGE memory usage ..................................................................................... 27




7.7 8


Getting Traces for investigation .......................................................................................................... 28 SAP Business Objects BI4.0 platform settings ................................................................................... 29

8.1

CMS settings ....................................................................................................................................... 29

8.2

Web application server (Tomcat) ........................................................................................................ 29

8.3

Avoid background activities................................................................................................................. 29

9

Deployment Examples ........................................................................................................................ 30 9.1

Deployment example 1 ....................................................................................................................... 31

9.2

Deployment example 2 ....................................................................................................................... 32

10

Additional Information ......................................................................................................................... 33

10.1 Abbreviations ...................................................................................................................................... 33 10.2 SAP Notes ........................................................................................................................................... 33 10.3 Pattern Books ...................................................................................................................................... 33 10.4 BI4 Sizing Companion guide ............................................................................................................... 34 10.5 BI4 Sizing Estimator ............................................................................................................................ 34 11

Copyright ............................................................................................................................................. 35




1


Document update history

Version 0.2 0.3 0.4 0.5 1.0 1.1 1.2

Modification By(*) Jan De Vilder Jan De Vilder Jan De Vilder Jan De Vilder Jan De Vilder Jan De Vilder Jan De Vilder

Date th June 12 , 2012 th June 13 , 2012 th June 20 , 2012 th June 26 , 2012 th, August 7 2012 th September 6 , 2012 th October 11 , 2012

1.3

Jan De Vilder

October 26 , 2012

th

Comment DRAFT first version proposed for review. DRAFT second version proposed for review. DRAFT third version proposed for review. DRAFT fourth version proposed for review. Pre-Final version Final Version to be published Additional information on Crystal Reports for Enterprise Dashboards and LCM Updated Sizing info

(*) Many people, consultants, product specialists, architects, support engineers… have contributed to this document while adding, modifying or reviewing content. Without their help, the document would not be in its current shape. Thanks a lot!

2

Background

The default installation of SAP BusinessObjects Business Intelligence Platform installs one Adaptive Processing Server (APS) per host system. The Adaptive Processing Server is a generic server that hosts services responsible for processing requests from a variety of sources. This default configuration is not always optimal, as all services run on a single java APS instance, with a maximum java heap size allocation of 1 GB RAM. The best practices described in this document help the BI Administrator to optimally configure the APS in SAP BO BI4.0. This document is based on the server architecture in BI4.0 SP2 patch 2.12 minimum. APS services are updated on regular basis for every new Service Pack, Support Pack, or Fix Pack. The services listed in this document can get outdated, hopefully not causing confusion. This document is particularly focused on isolation of services in a dedicated APS.




3


Architecture overview

Tiers: SAP BusinessObjects Business Intelligence platform can be thought of as a series of conceptual tiers:     

Client tier Management tier Storage tier Processing tier (where X is determined by the above formula) “BICSLOVChunkSIZE”=”Y” (where Y is determined by the above formula)



UNIX


You will need to edit the .registry file for BI 4.0 which is located in the following path (the OS in this example is RedHat): INSTALL_BASE_DIR/sap_bobj/





Below a picture is shown, describing the architecture. IAD

InfoView

WebIntelligence IAD

WebIntelligence Processing Server

Cube

Cube

DSL C++

DSL C++

Adaptive Processing Server

DSL Java

DSL Java (DSLBridge service)

BICS + JCo

BICS + JCo

NetWeaver BW

NetWeaver BW

*IAD = Interactive Analysis Desktop (= new name for Webi Rich Client)





It is wise to set those three parameters to small values (50000) in the following situations. That will help DSL and WebI to limit the number of chunk iteration. - For some reason, user needs to load entirely large LOV. - No limit on memory resource (DSLBRIDGE is configured with large heap size).




7.6


How to monitor DSLBRIDGE memory usage

A simple way to check if the DSLBRIDGE suffers from memory starvation is to visualize its GC log file. It is enabled by default in “C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\logging\”. The filename is post fixed by _gc.log. (For example: aps_dewdftf1134as.PJS_1_gc.log). For convenience, you can use gcviewer to view this log file: http://www.javaperformancetuning.com/tools/gcviewer/index.shtml To install GCViewer simply download the latest version from tagtraum.com: http://www.tagtraum.com/gcviewerdownload.html To detect heap memory contention, you can observe the frequency of the full GCs.

Full GCs

Another way is to observe, in the GCViewer statistics view, the throughput. It is the Time percentage the application was NOT busy with GC. A low throughput means your JVM spends hard time in recycling data. If memory contention is detected, you can enlarge the heap size (-Xmx) of your APS containing the DSLBRIDGE Service - see section above, “DSLBridge Service (PJS)”.




7.7


Getting Traces for investigation

Traces are a best help for SAP Support to investigate efficiently on application issue. The procedure is below: 1. 2. 3. 4.

Log into CMC. Select Servers / Servers List. Open the properties window of APS. In TraceLog section, set the log level to High:

5. Reproduce the issue. 6. Collect the log files in the folder \ SAP BusinessObjects Enterprise XI 4.0\logging\. 7. On Unix machine, you can look for additional RFC trace files and core file: o Go to /sap_bobj/enterprise_xi40//. o List the last created files: ls -lrt  You will see core file whenever a process has crashed.  Possible log files are created (*.trc, *.log).




8


SAP Business Objects BI4.0 platform settings

8.1

CMS settings

Increasing instances of CMS helps improve responsiveness of BIP actions (login, logout, folder navigation). This is particular true for “small” queries scenario (documents very fast to refresh). CMS database must be well tuned. With high number of concurrent users, CMS database could be intensively loaded both in read (select) and in update statements (insert, update, delete). The usual best practices are: 8.2

Updates database statistics. Maximize cache effect to minimize IO (buffer hit ratio = 99%). Speedy disk access (SCSI, raid system …). Web application server (Tomcat)

The following parameters are to be verified for the Web application Server (Tomcat): -

8.3

Maximum of possible threads (maxthread parameter in Tomcat). For Tomcat, it can be set to 900. JVM heapsize. For 128 users, a heapsize of 4GB is enough. Recommended options: -Xmx4g. Avoid background activities

In case your machine has little resources in CPU or memory, you may want to avoid disturbance by background activities which are turned on by default. You can stop Platform Search indexing service (see section on Search): o Open CMC o Go to Applications o Select Platform Search Application o Edit Properties o Stop Indexing o Modify the Crawling frequency: choose “Scheduled crawling” instead of “Continuous crawling”. You can also stop BI platform monitoring. o Open CMC o Go to Applications o Uncheck “Enable Monitoring Application”.




9


Deployment Examples

Before deploying multiple APS’s, it is important to analyze first how the BI platform will be used: which tools, what connectivity, Multi Source universes, publications, Auditing, LCM etc. It is obvious that the more RAM your platform has available, the more flexibility there is in creating dedicated APS’s and corresponding Xmx parameters. BI4.0 Hosts should not have less than 32 GByte of RAM for each Node in the Cluster, but again, this is very much dependent on each individual customer situation. A decent sizing exercise executed by qualified people should tell you in more detail the required RAM and CPU. All of the available RAM should not be consumed by the various APS only. Leave sufficient RAM available for other BI4 processes!

As many users have different needs and requirements with their deployments of BusinessObjects BI 4.0, some products may not be used and some services may not be needed. The first step:



 identify the products that you will be using.  The table in section 4 “Adaptive Processing Server Services” can help. The second step: by looking at the following tables determine:  which APS servers you will need to create  and the max heap size (value for –Xmx) for each APS The third step: create the necessary APS’s. The fourth step: perform system sizing and tuning.

Note that you do not always have to run all APS’s on the same machine, but you may choose to run several APS’s on one machine, while other on other machines.




9.1


Deployment example 1

This is an example of a deployment with the full set of possible APS’s. Choose from the table the APS’s you might need. The other services can be grouped in for example “AdaptiveProcessingServerOTHER”, as in Deployment example 2. See BI4 Sizing Estimator, to perform sizing estimates. APS

Xmx

Included Services

AdaptiveProcessingServerDSLBridge

Xmx8g

"DSL Bridge Service;

This APS is imperative in all Webi deployments

Web Intelligence Monitoring Service; Security Token Service; Trace log Service"

AdaptiveProcessingServerPUBLISHING

Xmx4g

Publishing Post Processing Service; Publishing Service; Trace log Service"

AdaptiveProcessingServerWEBI

Xmx4g

"Rebean Service; Web Intelligence Monitoring Service; Document Recovery Service; Custom Data Access Service; Excel Data Access Service; Trace log Service"

AdaptiveProcessingServerCHARTS

Xmx2g

"Visualization Service; Trace log Service

AdaptiveProcessingServerANALYSIS

Xmx8g

"Multi Dimensional Analysis Service; BEx Web Application Service; Trace log Service"

AdaptiveProcessingServerDF

Xmx3g

“Data Federation Service; Trace log Service"

AdaptiveProcessingServerMONITORING

Xmx1g

“Monitoring Service; Trace log Service"

AdaptiveProcessingServerCAPS

Xmx512m

“Client Auditing Proxy Service; Trace log Service"

AdaptiveProcessingServerCONNECTIVITY

Xmx1g

"Adaptive Connectivity Service; Trace log Service"

AdaptiveProcessingServerOTHER

Xmx1g

Security Token Service; Translation Service; Insight to Action Service; Trace log Service"

AdaptiveProcessingServerSEARCH

Xmx3g

"Platform Search Service Trace log Service"

AdaptiveProcessingServerLCM

Xmx2g

"Lifecycle Management Service; Lifecycle Management ClearCase Service; Visual Difference Service; Trace log Service"




9.2


Deployment example 2

This is an example of a deployment for Web Intelligence documents with BICS connectivity and Analysis Edition for OLAP. Use of UNX Universe is very limited. Focus is on Publications not on Auditing. See BI4 Sizing Estimator, to perform sizing estimates.

APS

Xmx

Included Services

AdaptiveProcessingServerDSLBridge

Xmx8g

"DSL Bridge Service;

This APS is imperative in all Webi deployments

Web Intelligence Monitoring Service; Security Token Service; Trace log Service"

AdaptiveProcessingServerPUBLISHING

Xmx4g

Publishing Post Processing Service; Publishing Service; Trace log Service"

AdaptiveProcessingServerWEBI

Xmx4g

"Visualization Service; Rebean Service; Web Intelligence Monitoring Service; Document Recovery Service; Trace log Service"

AdaptiveProcessingServerANALYSIS

Xmx8g

"Multi Dimensional Analysis Service; BEx Web Application Service; Trace log Service"

AdaptiveProcessingServerOTHER

Xmx4g

"Adaptive Connectivity Service; Custom Data Access Service; Excel Data Access Service; Client Auditing Proxy Service; Monitoring Service; Security Token Service; Translation Service; Insight to Action Service; Data Federation Service; Trace log Service"

AdaptiveProcessingServerSEARCH

Xmx3g

"Platform Search Service Trace log Service"

AdaptiveProcessingServerLCM

Xmx2g

"Lifecycle Management Service; Lifecycle Management ClearCase Service; Visual Difference Service; Trace log Service"





10 Additional Information 10.1 Abbreviations Sometimes abbreviations are used in this document:           

RAM: Random Access Memory. Available memory on a server or Host. BI: Business Intelligence BOE: Business Objects Enterprise; usually BOE is referring to the BI-platform, server or host SAP BO BI: SAP Business objects Business Intelligence; new name for BOE BIP:Business Intelligence Platform GB: Giga Byte or 1024 Mega Byte GByte: Giga Byte CMC: Central Management Console LCM: Life Cycle Management CR: Crystal Reports C4E: Crystal Reports for Enterprise

10.2 SAP Notes         

SAP Note 1640036 – Added memory usage when splitting Adaptive Procesing Server (APS) services SAP Note 1717717 – How to troubleshoot high CPU consumption issues on BI 4.0 SAP Note 1621001 – Adaptive Processing Server not getting started BI4.0 SAP Note 1630185 – Adaptive Procesing Server crashes repeatedly while indexing a system to enable search functionality in BI Launchpad SAP Note 1694041 - BI 4.0 Consulting:- How to size the Adaptive Processing Server SAP Note 1642935 - LCM Override settings are not working in BI4.0 SAP Note 1735431 - Error: “The datasource cannot be generated for the specified datasource name"xxx".(WIS 00000).” when creating Webi report based on a .unx universe from BILaunchpad SAP Note 1752843 - Error while using scan option within in Promotion Management in SAP BI 4.0 SP04 SAP Note 1697105 - How do I set Java settings such as Xmx for the Crystal Reports Processing Server

10.3 Pattern Books Since setup instructions vary for different operating systems, application server vendors, and database vendors, this wiki contains end-to-end instructions for setting up various deployment scenarios in your company's environment. Each deployment scenario is called a pattern. Go to: http://wiki.sdn.sap.com/wiki/display/BOBJ/SAP+Business+Intelligence+Platform+Pattern+Books





10.4 BI4 Sizing Companion guide A new version of the BI4 Sizing Companion Guide is available here: https://scn.sap.com/docs/DOC-33126 This document provides recommendations and best practices to help with deploying and scaling the various services in SAP BusinessObjects BI 4. Also, included, are information and details about the sizing tests and methodology used to create the various sizing tools and documents in support of BI 4. We recommend consulting this guide if you are:   

Working on a sizing strategy, especially in conjunction with the BI 4 Sizing Estimator. Be sure to use the most recent version of the Sizing Estimator. Planning to deploy BusinessObjects BI 4 software Optimizing or tuning an existing BusinessObjects BI 4 deployment

For all deployments, it is necessary to consult a Sizing Expert in order to validate sizing exercises after initial planning using the Sizing Estimator and this Sizing Guide. There may have been updates made to this document. The most recent version is always available at this location. This link is at the top of the document, so if readers are ever unsure about having the newest version, they can follow the link in the document. The publish date of the document is on the first page.

10.5 BI4 Sizing Estimator The Sizing Estimator has also been updated and is available here: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/1055c550-ce45-2f10-22ad-a6050fff97f1

This version of the Sizing Estimator has significantly refined data from the P&R testing team. It was used to predict existing known good deployments and it has shown itself to be quite accurate. This tool must be used in conjunction with the new BI4 Sizing Companion Guide so its estimates can be employed correctly. The Sizing Estimator shows guidance for deployment on a single large dedicated machine. If the target landscape is not such a device, it is very important to follow the guidance of the BI4 Sizing Companion Guide to learn how to scale-out a deployment successfully.





11 Copyright © Copyright 2012 SAP AG. All 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 changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.



Best Practices for SAPBO BI 4.0 Adaptive Processing ... - archive SAP

Best Practices for SAPBO BI 4.0 Adaptive Processing ... - archive SAP

Suggest Documents

Best Practices for SAPBO BI 4.0 Adaptive Processing ... - archive SAP

Routines in SAP BI 7.0 Transformation - archive SAP

Best Practices for Migrating SAP Environments

Configuration Best Practices for SAP HANA TDI

Configuration Best Practices for SAP HANA TDI

Best Practices for SAP BI using DB2 9 for z/OS - IBM Redbooks

SAP HANA Best Practices Guide - Amazon AWS

Oracle BI Publisher 10g Best Practices [PDF]

SAP Solutions on VMware Best Practices Guide

PDF SAP BI - Emagister

Best Practices for Running SAP NetWeaver on SUSE Linux ... - Novell

SAP Business Intelligence (BI)

5 Best Practices for SAP® Master Data Governance - Bitpipe

formación sap: bw-bi formación sap

Best PDF SAP BusinessObjects BI 4.0 The Complete ... - Google Sites

Best Practices for Archival Processing for Geospatial ... - GeoMAPP

Best Practices for Archival Processing for Geospatial ... - GeoMAPP

Quick Guide to EhP 5 for SAP ECC 6.0 based on SAP Best Practices ...

Best Practices Guide for Hop Processing - Gorst Valley Hops

Best Practices Guide for Hop Processing - Gorst Valley Hops

A Guide to Best Practices for the Food-Processing Industry

Tools and best practices for data processing in ... - Semantic Scholar

EMC Documentum Archive Services for SAP

SAP BW vs. SAP BusinessObjects Web Intelligence ... - archive SAP