вторник, 16 июля 2013 г.

SAP BO 4 Adaptive Processing Server sizing


By default, the installation routine deploys an 'out-of-the-box' configuration, where the APS hosts ~20 services simultaneously.
All services run on a single java APS instance, with a maximum java heap size allocation of 1Gb RAM.


  • Adaptive Connectivity Service
  • BEx Web Applications Service
  • Client Auditing Proxy Service
  • Custom Data Access Service
  • Data Federation Service
  • Document Recovery Service
  • DSL Bridge Service
  • Excel Data Access Service
  • Lifecycle Management ClearCase Service
  • Lifecycle Management Service
  • Monitoring Service
  • Multi Dimensional Analysis Service (MDAS)
  • Platform Search Service
  • Publishing Post Processing Service
  • Publishing Service
  • Rebean Service
  • Security Token Service
  • Translation Service
  • Visual Difference Service
  • Visualization Service
  • Web Intelligence Monitoring Service


For best performance and scalability, SAP recommends that you host important services in multiple dedicated APS containers, and then adjust the sizing parameters to answer the different memory/processor requirements. This is considered a Consulting activity.

At a minimum, it is advisable to create an Adaptive Processing Server relating to each of the main six processing categories:


  • Core Services,
  • Analysis Services,
  • Connectivity Services,
  • Data Federation Services,
  • Lifecycle Management Services,
  • Web Intelligence Services.


However, the SAP BusinessObjects Enterprise Administrator’s Guide and Sizing Companion Guide also recommend to separate the following APS services:


  • MDAS service (for Analysis OLAP),
  • DSL Bridge service (for .UNX),
  • Visualization service (for CVOM charting),
  • Monitoring service (CMC application), 
  • Auditing service.


As a starting point for large enterprise deployments, these guidelines should be taken further. Below is a more complete example of how each APS container could be configured.

By default, the -Xmx Java Heap Size (in each Server's start-up command line properties) is set to 1g (1GB of RAM).
These Java Heap values are flexible, and should be increased/decreased on an ad-hoc basis, depending on requirements (guideline indications are given below).
In the case of DSl_Bridge and MDAS the recommended heap size is 4 GB minimum; with 6-8 GB or better preferred. These settings depend on the size and number of concurrent queries at a time.
Data Access DSL  (-Xmx4g -> 8g)


  • DSL Bridge Service
  • WebI Monitoring Service
  • Security Token Service
  • TraceLog Service

MDAS OLAP Analysis  (-Xmx4g -> 8g)


  • Multi Dimensional Analysis Service
  • TraceLog Service

BEx WAD  (-Xmx2g -> 8g)


  • BEx Web Applications Service

Data Access Other (-Xmx2g -> 4g)


  • Adaptive Connectivity Service
  • Custom Data Access Service
  • Excel Data Access Service
  • Rebean Service
  • TraceLog Service

Life Cycle Manager  (-Xmx2g -> 8g)


  • Lifecycle Management ClearCase Service
  • Lifecycle Management Service
  • Visual Difference Service
  • TraceLog Service

Auditing  (-Xmx1g -> 4g)


  • Client Auditing Proxy Service
  • TraceLog Service

Publishing  (-Xmx1g -> 4g)


  • Publishing Post Processing Service
  • Publishing Service
  • TraceLog Service

Multi Source Federation (-Xmx2g -> 8g)


  • Data Federation Service
  • TraceLog Service

Monitoring (-Xmx2g -> 8g)


  • Monitoring Service
  • Document Recovery
  • TraceLog Service

Platform Search  (-Xmx2g -> 8g)


  • Platform Search Service
  • TraceLog Service

Translation (-Xmx2g -> 4g)


  • Translation Service

CVOM Charting (-Xmx2g -> 8g)

Visualization Service
This approach will result in improved response times and larger throughput, but at the expense of higher overall memory utilization on the platform due to the increased number of Java Virtual Machines (1 per APS).

Benefits will include:

Performance, Stability and Scalability
Isolated workflows for easier troubleshooting (i.e. focused TraceLog and Monitoring)
Ability to turn-off specific features without requiring downtime