BOE 31 EWA Report (Ejemplo Reporte EWA)

SERVICE REPORT
SAP EarlyWatch Alert
SAP System ID B32
SAP Product SAP BusinessObjects Enterprise XI 3.1
Status
DB System
Customer SAP AG R11

69190 Walldorf
Germany
Analysis from 07.06.2010 Session No. 2000000006639

Until 13.06.2010 Installation No.
Processed by SAP Customer No.
System Status BOB
Note: The recommendations in this report are based on general experience only. You should test these
recommendations before implementing them in your production system.
1 System Status BOB

Performance Overview
Workload Distribution
Hardware Capacity
Hardware Capacity Forecast
SAP System Operating
Note: If you require any assistance in resolving concerns about your system performance, or if you require a
technical analysis of other aspects of your system as highlighted in this report, you can create a customer
message on component SV-BO. For information about how to set the appropriate priority level, see SAP
Note 67739.
Note: If you have questions concerning the accuracy of the checks in this report or the correct configuration of
the Solution Manager EarlyWatch Alert service, you can create a customer message on component.
For full details of our service offering, refer to http://service.sap.com/servicecatalog on SAP Service Marketplace.
SAP offers a comprehensive range of technical and strategic textbooks which can increase your organization's
knowledge of SAP's products and best practices. For more information, refer to www.sap-press.com, where you
can download the latest catalog. We recommend that you order material relevant to your particular software
solution.
SAP also offers "Empowering Workshops for System and Solution Optimization".
Workshops relevant to this particular system include:
- TASP01 EarlyWatch Empowering Workshop
For a complete overview of the SAP Empowering Workshops and information about ordering these, refer to
http://service.sap.com/empoweringworkshops or visit SAP Service Marketplace.
SAP EarlyWatch Check, Test value contract OSS corp. 01.07.2010 2

Table of Contents
2 Table of Contents
1 SYSTEM STATUS BOB.................................................................................................................................. 2
2 TABLE OF CONTENTS.................................................................................................................................. 3
3 HARDWARE CONFIGURATION..................................................................................................................... 4
4 HARDWARE CAPACITY ................................................................................................................................ 4
4.1 OVERVIEW SYSTEM BOB............................................................................................................. 4
4.2 SERVER XI31CMS1 ................................................................................................................... 5
4.3 SERVER XI31CMS2 ................................................................................................................... 5
5 BUSINESS OBJECTS - TECHNOLOGY CHECKS ......................................................................................... 6
5.1 BUSINESS OBJECTS VERSIONS..................................................................................................... 6
5.2 PERFORMANCE & AVAILABILITY OVERVIEW ..................................................................................... 7
5.2.1 Report Overview .............................................................................................................................. 7
5.2.2 BOE Server Availability .................................................................................................................... 7
5.2.3 CMS Server Metrics ......................................................................................................................... 8
5.2.4 Failed Schedules Overview .............................................................................................................. 8
5.2.5 User Workload Overview .................................................................................................................. 8
5.2.6 Average Runtimes & Requests ......................................................................................................... 9
5.2.7 Top WebIntelligence Documents..................................................................................................... 10
5.2.8 Top Calls to Data Source ................................................................................................................ 10
5.2.9 Top SAP BW Calls ......................................................................................................................... 10
5.2.10 Timed-out Requests ..................................................................................................................... 11
5.3 KEY PERFORMANCE INDICATORS ................................................................................................ 11
5.4 BUSINESS OBJECTS SERVER SETTINGS ...................................................................................... 13
5.4.1 Job Server DIAGP001.AdaptiveJobServer ...................................................................................... 14
5.4.2 Central Management Server Settings DIAGP001.CentralManagementServer .................................. 14
5.4.3 Crystal Report Cache Server DIAGP001.CrystalReportsCacheServer ............................................. 14
5.4.4 Job Server DIAGP001.CrystalReportsJobServer ............................................................................. 15
5.4.5 Crystal Report Processing Server DIAGP001.CrystalReportsProcessingServer ............................... 15
5.4.6 Job Server DIAGP001.DesktopIntelligenceJobServer...................................................................... 16
5.4.7 Job Server DIAGP001.DestinationJobServer .................................................................................. 16
5.4.8 Job Server DIAGP001.LCMJobServer ............................................................................................ 16
5.4.9 Job Server DIAGP001.ListOfValuesJobServer ................................................................................ 17
5.4.10 Job Server DIAGP001.ProgramJobServer .................................................................................... 17
5.4.11 Job Server DIAGP001.PublicationJobServer ................................................................................. 17
5.4.12 Report Application Server DIAGP001.ReportApplicationServer ...................................................... 17
5.4.13 Web Intelligence Processing Server DIAGP001.WebIntelligenceProcessingSe.25 ......................... 17
5.5 FURTHER RECOMMENDATIONS ................................................................................................... 18
5.5.1 Virtual Memory Size ....................................................................................................................... 18
5.6 GENERAL SETTINGS AND DESIGN ................................................................................................ 19
5.6.1 Browser Settings............................................................................................................................ 19
5.6.2 Scheduling of Reports .................................................................................................................... 19
5.6.3 Universes - General Recommendations .......................................................................................... 20
EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 3

Hardware Configuration
3 Hardware Configuration
SERVER OVERVIEW
Server Hardware Manufacturer Model Operating System No. of CPUs Memory in MB
XI31CMS1 Windows Server 2003 (x86_32) 1 2048
XI31CMS2 Windows Server 2003 (x86_32) 1 2048
4 Hardware Capacity
We have checked your system for potential CPU or memory bottlenecks and
found that the hardware is sufficient for the current workload.
4.1 Overview System BOB

General
This analysis focuses on the workload during the peak working hours (9-17) and is based on the hourly averages
collected by SAPOSCOL. For information about the definition of peak working hours, see SAP Note 1251291.
CPU
If the average CPU load exceeds 75%, temporary CPU bottlenecks are likely to occur. An average CPU load of
more than 90% is a strong indicator of a CPU bottleneck.
Memory
If your hardware cannot handle the maximum memory consumption, this causes a memory bottleneck in your
SAP system that can impair performance. The paging rating depends on the ratio of paging activity to physical
memory.
Server Max. Date Rating RAM Max. Date Rating Analysis Analysis
CPU [MB] Paging [% Start End
load [%] of RAM]
XI31CMS1 11 24.06.2010 2048 1 24.06.2010 21.06.2010 27.06.2010
XI31CMS2 11 24.06.2010 2048 12 22.06.2010 21.06.2010 27.06.2010

Hardware Capacity
4.2 Server XI31CMS1
This graph shows the average CPU load and the average paging rates in relation to the physical RAM of the
XI31CMS1 server.
CPU
This server's CPU resources are sufficient to handle the current workload.
Memory
The memory resources are sufficient for the current workload.
4.3 Server XI31CMS2
This graph shows the average CPU load and the average paging rates in relation to the physical RAM of the
XI31CMS2 server.
CPU
This server's CPU resources are sufficient to handle the current workload.
Memory
The memory resources are sufficient for the current workload.

Business Objects - Technology Checks
5 Business Objects - Technology Checks
Your SAP BusinessObjects Server settings were compared with

the recommended parameters. Some settings may affect the
performance of your BusinessObjects system.
This section provides an overview of your SAP BusinessObjects solution from a technological perspective.
Rating Check Description

Central Management Server Settings
Web Intelligence Processing Server Settings
Crystal Report Processing Server Settings
Crystal Report Cache Server Settings
Report Application Server Settings
Job Server Settings
5.1 Business Objects Versions

The types, numbers, and versions of your BusinessObjects servers are listed in the table below:
Number of Servers Type of Server Version

1 Central Management Server BO XI 3.1
8 Job Server BO XI 3.1
1 Report Application Server BO XI 3.1
2 Adaptive Processing Server, MultiDimensionalAnalysisServicesServer BO XI 3.1
1 Connection Server BO XI 3.1
1 Crystal Reports Cache Server BO XI 3.1
1 Crystal Reports Processing Server BO XI 3.1
1 Dashboard Analytics Server BO XI 3.1
1 Dashboard Server BO XI 3.1
1 Desktop Intelligence Cache Server BO XI 3.1
1 Desktop Intelligence Processing Server BO XI 3.1
1 Event Server BO XI 3.1
2 File Repository Server BO XI 3.1
1 PM Metrics Server BO XI 3.1
1 PM Repository Server BO XI 3.1
1 PM Rules Server BO XI 3.1
1 Predictive Analysis Server BO XI 3.1
1 Process Analysis Server BO XI 3.1
1 Sets Profile Server BO XI 3.1
1 Sets Query Server BO XI 3.1
1 Web Intelligence Processing Server BO XI 3.1
1 polestarExploration Server BO XI 3.2

Number of Servers Type of Server Version

1 polestarIndexing Server BO XI 3.2
1 polestarSearch Server BO XI 3.2
1 polestarMaster Server BO XI 3.2
5.2 Performance & Availability Overview

Below you can find a selection of performance and usage metrics for your Business Objects environment. If not
mentioned otherwise, the values are weekly averages.
5.2.1 Report Overview

Below you can find an overview on the amount of defined documents, reports and related objects like universes.
KPI Name KPI Value Description

BOE_EXPLORER_INFOSPACES 14 Number of InfoSpaces
BOE_PROGRAMS_INST 0 Number of executed program instances
BOE_PROGRAMS_TOT 5 Number of programs
BOE_PUBLICATIONS 0 Number of publications
BOE_UNIVERSES 28 Number of defined universes
BOE_XCELSIUS_MODELS 0 Number of defined Xcelsius models
BOE_XCELSIUS_SWFS 0 Number of generated Xcelsius Shockwave files
5.2.2 BOE Server Availability

In the graphic below you can see the availability of BOE servers (servers running - servers stopped) for last week.
Date/Time Interval Servers running Servers stopped

20100607: 00-04 70 2
20100607: 04-08 70 2
20100607: 08-12 70 2
20100607: 12-16 70 2
20100607: 16-20 70 2
20100607: 20-24 70 2

Date/Time Interval Servers running Servers stopped

20100608: 00-04 70 2
20100608: 00-04 70 2
20100608: 16-20 70 2
20100608: 20-24 70 2
20100609: 00-04 70 2
20100609: 04-08 70 2
20100609: 08-12 70 2
20100609: 12-16 70 2
20100609: 16-20 70 2
20100609: 20-24 70 2
20100610: 00-04 70 2
20100610: 04-08 70 2
20100610: 08-12 70 2
20100610: 12-16 70 2
20100610: 16-20 70 2
20100610: 20-24 70 2
20100611: 00-04 70 2
20100611: 04-08 70 2
20100611: 08-12 70 2
5.2.3 CMS Server Metrics

Below you can find selected metrics for the CMS server.
KPIS
KPI Name KPI Value Description
BOE_CMS_OBJECTS 3224 Number of objects in CMS
5.2.4 Failed Schedules Overview

Scheduling in BOE can be used for different purpose, e.g. to prepare document instances for better performance.
To ensure optimal performance and availability of your BOE solution, check for failed schedules on a regular basis.
Below you can find a daily overview for last week.
Date Schedules completed Schedules failed

07.06.2010 1574 81
08.06.2010 1574 106
09.06.2010 1574 132
10.06.2010 1575 156
11.06.2010 1588 164
5.2.5 User Workload Overview

Below you can find information on the current number of defined concurrent and named (with guaranteed access)
users and the maximum number of users logged on for last week.
DEFINED USERS
Type Amount
User Groups 11
Concurrent Users 5
Named Users 5

Date Max. Concurrent Users logged on Max. Named Users logged on

07.06.2010 17
08.06.2010 7 2
09.06.2010 4 26
10.06.2010 3 26
11.06.2010 3 26
5.2.6 Average Runtimes & Requests

Find below the peak usage times for Voyager, Web Intelligence or Crystal Reports as well as the average
response time experienced by end users. In particular for WebIntelligence you can also find the documents with
highest average runtimes in the subsequent chapter.
WEEKLY OVERVIEW
Component Average runtime (ms) Average executions/day
WEBI 1309 8
CRYSTAL 241902 1
VOYAGER 55752 7
WEB INTELLIGENCE REQUESTS

Date Average Runtime (ms) Executions
07.06.2010 516 1
08.06.2010 336 10
09.06.2010 313 14
10.06.2010 4804 7
CRYSTAL REQUESTS
12.06.2010 241902 1
VOYAGER REQUESTS
10.06.2010 55752 7

5.2.7 Top WebIntelligence Documents

The view below provides the top list of Web Intelligence documents (document instances scheduled or document
instances loaded from the cache). The ID of a document is available in InfoView portal with a right click on a
document (properties). To find the name of a document from its ID, you need to use the Query Builder.
The list is sorted by the total accumulated runtime of a document.
TOP WEBI DOCUMENTS
Document Number Average Runtime (ms) Executions
18513 2748 18
34722 1598 4
42615 1479 3
111582 1766 2
1086 2359 1
111586 1422 1
149375 1297 1
86473 1109 1
5.2.8 Top Calls to Data Source

Below you can find the top calls to the data sources used in your documents. This list can help to identify whether
performance problem are related to the processing within BOE or within the data source itself. This layer is
involved always independant of the type of data source (including SAB BW). If SAP BW is used as data source,
the runtimes include the Top BW calls in the subsequent chapter.
Call Average runtime (ms) Executions

CS_OPENJOB_DESCRIBE 2568 115
CS_GENERICJOB_EXECALLOCANDFETCH 791 114
CS_OPENJOB_EXECUTE 791 114
CS_OPENJOB_INITIALIZE 136 242
CS_GENERICJOB_ALLOCANDFETCH 267 114
CS_CENTAUR_API_ROWRESULTSET_FIRST 334 87
CS_CENTAURDRIVER_CONNECT 131 212
CS_CENTAURDRIVER_CREATECONNECTION 130 212
CS_CENTAURDRIVER_DISCONNECT 11 88
CS_CENTAURDRIVER_DESCRIBECOL 0 96
5.2.9 Top SAP BW Calls

,,The table below shows the top list of operations executed against SAP BW backend. It monitors in the timeframe
all SAP BW driver operations. This layer handles the connection to the SAP BW backend; it is called by the
generic Data Source layer (see above).
Call Average Runtime (ms) Executions

MDA_SAPUTILS_GETHIERARCHYBYUNAME 452 96
MDA_SAPFLATDATALOADER_GET_SAP_FLATTENED_ROWSET 7386 3
MDA_SAPFLATDATALOADER_GETFLATDATA 5385 3
MDA_SAPFLATDATALOADER_FUNCGETDATA_FROM_BI 5385 3
MDA_SAPCOMMAND_EXECUTE 2307 3
MDA_SAPCOMMAND_EXECUTE_QUERY 2302 3
MDA_SAPFLATDATALOADER_GETCOLUMNINFO 1729 3
MDA_SAPUTILS_GETDIMENSIONBYUNAME 45 90
MDA_SAPDIMENSION_LOAD_HIERARCHIES 39 90
MDA_SAPFLATDATASET_ISSERVERFLATTENINGAVAILABLE 8 87

5.2.10 Timed-out Requests

Below you can find the number of timed out executions per day. For a high number of timed out requests, please
review the timeout parameters on the different types of BOE servers.
Date Number
07.06.2010 4
08.06.2010 2
09.06.2010 2
10.06.2010 9
11.06.2010 2
13.06.2010 1
5.3 Key Performance Indicators

The key metrics provided below refer to the usage of your Business Objects environment over the past week.
KPI Name KPI Description Host Date

Value
BOE_WEBIREPORTS_TOT 0 Number of defined Web Intelligence XI31CMS2 01.07.2010
reports
reports
BOE_WEBIREPORTS_INST 0 Number of scheduled Web Intelligence XI31CMS2 01.07.2010
report instances
report instances
BOE_CRYSTALREPORTS_TOT 0 Number of defined Crystal reports XI31CMS2 01.07.2010
BOE_CRYSTALREPORTS_INST 0 Number of scheduled Crystal report XI31CMS2 01.07.2010
instances
instances
BOE_DESKIREPORTS_TOT 0 Number of defined Desktop Intelligence XI31CMS2 01.07.2010
reports
reports


Value
BOE_DESKIREPORTS_INST 0 Number of scheduled Desktop XI31CMS2 01.07.2010
Intelligence report instances
BOE_XCELSIUS_MODELS 0 Number of defined Xcelsius models XI31CMS2 01.07.2010
BOE_XCELSIUS_SWFS 0 Number of generated Xcelsius XI31CMS2 01.07.2010
Shockwave files
Shockwave files
BOE_PROGRAMS_TOT 0 Number of programs XI31CMS2 01.07.2010
BOE_PROGRAMS_INST 0 Number of executed program instances XI31CMS2 01.07.2010
BOE_EXPLORER_INFOSPACES 0 Number of InfoSpaces XI31CMS2 01.07.2010
BOE_PUBLICATIONS 0 Number of publications XI31CMS2 01.07.2010
BOE_UNIVERSES 0 Number of defined universes XI31CMS2 01.07.2010
BOE_CONNECTIONS 0 Number of connections XI31CMS2 01.07.2010
BOE_USERGROUPS 0 Number of user groups XI31CMS2 01.07.2010
BOE_USERS_CONCURRENT 0 Number of defined concurrent users XI31CMS2 01.07.2010
BOE_USERS_NAMED 0 Number of defined named users XI31CMS2 01.07.2010
BOE_SCHEDULES_PENDING 0 Number of schedules pending XI31CMS2 01.07.2010
BOE_SCHEDULES_COMPLETED 0 Number of completed schedules XI31CMS2 01.07.2010
BOE_SCHEDULES_FAILED 0 Number of failed schedules XI31CMS2 01.07.2010
BOE_CMS_OBJECTS 0 Number of objects in CMS XI31CMS2 01.07.2010
reports
reports
report instances
report instances
instances
instances
reports
reports


Value
Shockwave files
Shockwave files
5.4 Business Objects Server Settings

The following SAP BusinessObjects servers are analyzed in your solution:
Analysi Server Name CM WebiProcSe CRProcSe JobSer CRCacheSe RepAppSe

s? S rver rver ver rver rver
DIAGP001.ProgramJobServer
DIAGP001.AdaptiveJobServer
DIAGP001.ReportApplicationSer
ver
DIAGP001.PublicationJobServer
DIAGP001.ListOfValuesJobServ
er
DIAGP001.CrystalReportsCache
Server

Analysi Server Name CM WebiProcSe CRProcSe JobSer CRCacheSe RepAppSe

s? S rver rver ver rver rver
DIAGP001.CrystalReportsProces
singServer
DIAGP001.LCMJobServer
DIAGP001.WebIntelligenceProce
ssingSe.25
DIAGP001.CentralManagementS
erver
DIAGP001.DesktopIntelligenceJo
bServer
DIAGP001.DestinationJobServer
DIAGP001.CrystalReportsJobSer
ver
5.4.1 Job Server DIAGP001.AdaptiveJobServer

Parameter Description Current Value Recommended Rating
Value
ISPROP_IPROC_MAXJOBS Maximum 5 5
Concurrent
Jobs
ISPROP_OPROC_TMPDIR Temporary C%3A%5CProgram+ >= 250MB
Directory Files+%28x86%29 %5CBusiness+Obj
ects%5CBusiness Objects+Enterpr
ise+12.0%5CData
%5CprocSched%5C DIAGP001
You can change the settings by choosing 'Central Management Console -> Servers'. Double-click 'Crystal Reports
Job Server' and choose 'Properties'.
5.4.2 Central Management Server Settings

DIAGP001.CentralManagementServer
Parameter Description Current Recommended Rating
Value Value
RestartOnDBConnectionLoss Disable Auto Reconnect to 0 0
System and Auditing
Databases
RequestedNumDBConnections How many system database 14 14
connections exist between the
CMS and the system database
Monitor.SystemDB.NumObjectsInCache The maximum number of <50000
objects that the CMS stores in
its memory cache
Caution:
The CMS database should not be accessed directly. System information should only be retrieved using the calls
provided in the BusinessObjects Enterprise Software Development Kit (SDK) or using the Query Builder.
5.4.3 Crystal Report Cache Server DIAGP001.CrystalReportsCacheServer

Value
RefreshAlwaysHitsDb Viewer Refresh Always Active Active
Yields Current Data
ShareData Share Report Data Active Active
Between Clients
MaxIdleTimeMinutes Idle Connection Timeout 20 50
(minutes)


Value
RefreshIntervalSeconds Oldest On-Demand Data 0 < 60
Given to Clients
(seconds)
CacheSizeKB Maximum Cache Size 256000 256000
(KB)
TempDir Cache Files Directory %DefaultDataDir >= 250MB
%/CrystalReport
sCachingServer/ temp
Cache Server' and choose 'Properties'.
5.4.4 Job Server DIAGP001.CrystalReportsJobServer

Value
Concurrent
Jobs
ise+12.0%5CData
5.4.5 Crystal Report Processing Server

DIAGP001.CrystalReportsProcessingServer
Value
ProcThreadIdleTimeMinutes Idle Job Timeout (minutes). 60 60
Setting the value to high will
keep to many reports in
memory and use up memory
LimitedDBRecNum Database Records Read 20000 <= 20000
When Previewing or
Refreshing (0 for unlimited)
MaxLifetimeJobsPerChild Maximum Lifetime Jobs Per 1000 1000
Child (seconds)
RefreshAlwaysHitsDb Viewer Refresh Always Yields Active Active
Current Data
ShareData Share Report Data Between Active Active
Clients
MaxIdleTimeMinutes Idle Connection Timeout 20 20
(minutes)
MaxThreads Maximum Concurrent Jobs (0 0 0
for automatic)
RefreshIntervalSeconds Oldest On-Demand Data 0 0
Given to Clients (seconds)
MaxNumPrestartedChildren Maximum Number of 1 1
Prestarted Children
TempDir Temporary Directory. Rule of %DefaultDataDir >= 250MB
thumb is that a report %/CrystalReport
expands to about 15 times it's sProcessingServ
original size in the temporary er/temp
direct


Value
NoAutomaticDBDisconnect Allow Report Jobs to Stay Inactive Inactive
Connected to the Database
until the Report Job is Closed
You can change the settings by choosing Central Management Console -> Servers. Double-click 'Crystal Reports
Processing Server' and choose 'Properties'.
5.4.6 Job Server DIAGP001.DesktopIntelligenceJobServer

Value
Concurrent
Jobs
ise+12.0%5CData
5.4.7 Job Server DIAGP001.DestinationJobServer

Value
Concurrent
Jobs
ise+12.0%5CData
5.4.8 Job Server DIAGP001.LCMJobServer

Value
Concurrent
Jobs
ise+12.0%5CData

5.4.9 Job Server DIAGP001.ListOfValuesJobServer

Value
Concurrent
Jobs
ise+12.0%5CData
5.4.10 Job Server DIAGP001.ProgramJobServer

Value
Concurrent
Jobs
ise+12.0%5CData
5.4.11 Job Server DIAGP001.PublicationJobServer

Value
Concurrent
Jobs
ise+12.0%5CData
5.4.12 Report Application Server DIAGP001.ReportApplicationServer

Parameter Description Current Value Recommended Value Rating
srvr_userinactivitytimeout Idle Connection timeout 30 50
srvr_maxreportjobs Maximum Concurrent Report Jobs 75 < 100
You can change the settings by choosing 'Central Management Console -> Servers'. Double-click 'Report
Application Server' and choose 'Properties'.
5.4.13 Web Intelligence Processing Server

DIAGP001.WebIntelligenceProcessingSe.25
The following table shows the Web Intelligence parameters and the recommended values.

Parameter Description Current Recommended Rating

Value Value
WebiParamCacheCleanupInterval Document Cache 120 120
Cleanup Interval
(seconds)
WebiParamMaxCacheDuration Cache Timeout 1 4370
(seconds)
WebiParamUniverseMaxCacheSize Universe Cache 20 50
Maximum Size
(Universes)
WebiParamDocExpressMaxCacheSizeKB Maximum Document 1000000 1000000
Cache Size (KB)
WebiParamRecycleLevel Maximum Documents 50 200
Before Recycling
WebiParamMaxConnections Maximum 50 100
Connections
WebiParamConnectionTimeoutMinutes Idle Connection 20 20
Timeout (minutes)
WebiParamEnableListOfValueCache Enable List of Values 1 1
Cache
WebiParamDocExpressMaxReductionSpace Maximum Document 70 70
Cache Reduction
Space
WebiParamWIDMaxCacheSize Maximum Documents 0 0
in Cache
WebiParamDocExpressRealTimeCachingEnable Enable Document 1 1
Cache
WebiParamMaxIdleTimeSec Timeout Before 1200 7200
Recycling (seconds)
You can change the CMS settings by choosing Central Management Console -> Servers -> Properties.
5.5 Further Recommendations

5.5.1 Virtual Memory Size
To optimize performance, Microsoft recommends that you do not set the initial size to less than the minimum
recommended under 'Total paging file size for all drives'.
The recommended size is equivalent to 1.5 times the amount of RAM on your system. It is best to leave the
paging file at its recommended size, although you could increase this if you routinely use programs that require a
lot of memory.
Note:
Virtual memory settings are commonly referred to as Swap File settings.

For more information about EarlyWatch Alert, you can review sample EarlyWatch Alert reports on SAP Service
Marketplace at /EWA -> Library -> Media Library. General information about the EarlyWatch Alert is available at
SAP Note 1257308.
5.6 General Settings and Design

5.6.1 Browser Settings
High front-end times or high front-end CPU times indicate that the script execution time in the Internet browser is
slow.
Runtime-intensive script coding or intensive virus scanning together with the rendering of the screen means that
the CPU consumes a lot of resources on the front-end PC. This may cause performance problems on weak front-
end PCs.
Recommendations:
Different browsers and versions usually result in different front-end performance. Microsoft Internet
Explorer is used in many customer networks as an exclusive browser. Consider that IE 7.0 is faster than IE
6.0.
SAP also supports other browsers such as Firefox. These browsers can often provide much better
performance compared to Internet Explorer.
The following settings must be set correctly for Internet Explorer. Activate HTTP 1.1 use of the Web client.
HTTP 1.0 does not support compression. This is important so that the Web client can accept compressed
data.
Internet Options -> Advanced -> HTTP 1.1 = X

Internet Options -> Advanced -> HTTP 1.1 through proxy connections = X
The following settings can also improve performance:
General -> Browsing History -> Settings: "Check for newer versions of stored pages" should be set to
"Automatically" or "Every time I start Internet Explorer".
Advanced - Security -> Do not set "Empty Temporary Internet Files Folder when browser is closed".
Regardless of the browser that is used, avoid running scripts on your Web site that result in a long runtime
and high front-end CPU load.
Deactivate the virus scanner for secured script. For more information, see SAP Note 1061240 "Slow Web
browser due to JavaScript virus scan". If you need to use scripts, try to reduce the file size of javascripts.
To do so, use optimization tools to compress the size of javascrips (e.g. JSMIN) or CSS files.
Internet Explorer (as well as other browsers) allows only two parallel http connections by default. You
should therefore adjust the Windows registry settings on client PCs.
Increase the number of parallel http connections for your browser. For example, for Internet Explorer
increase the number of parallel http connections in the Windows registry to 10 (DWORD entry
"MaxConnectionsPerServer = 10" under
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ ).
For more information, see SAP Note 968283.
5.6.2 Scheduling of Reports

A report that contains saved data is quicker to open than a report that connects to the database to refresh the data.
If the business requirements allow, it is preferable to schedule reports. This will improve the viewing performance
and create less strain in the back-end database because there are fewer refreshes.
Recommendation: Identify the reports for which it is acceptable not to have the very latest data but that
are viewed on a regular basis and schedule them. There are options to schedule reports for users with
different settings. Consult the Business Objects Enterprise manuals for more information.

5.6.3 Universes - General Recommendations

5.6.3.1 Use of Index Awareness
Index awareness is the ability to take advantage of the indexes on key columns to speed up data retrieval. If you
want to set up index awareness in the Universe Designer, you must tell the Designer which database columns of
your data source are primary and foreign keys.
These object keys now allow the Universe Designer to generate more efficient SQL by filtering on primary key
values and eliminating unnecessary joins. This can have a significant effect on query performance, especially
when prompted with a list of values (LOV).
Recommendation: If you experience poor performance, in particular with lists of values (LOVs), set up
index awareness.
Implementation: Go into the object properties of a dimension object and define a key for index awareness
on the "Keys" tab page.
Select the "enabled" checkbox. Also configure the staff key in the fact table as the foreign key?
A table can have foreign keys in more than one place. The designer can include as many key values as
necessary.

BOE 31 EWA Report (Ejemplo Reporte EWA)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BOE 31 EWA Report (Ejemplo Reporte EWA)

Uploaded by

Copyright:

Available Formats

SERVICE REPORT

SAP EarlyWatch Alert

SAP System ID B32

SAP Product SAP BusinessObjects Enterprise XI 3.1

Customer SAP AG R11

Analysis from 07.06.2010 Session No. 2000000006639

1 System Status BOB

SAP EarlyWatch Check, Test value contract OSS corp. 01.07.2010 2

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 3

4.1 Overview System BOB

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 4

4.2 Server XI31CMS1

4.3 Server XI31CMS2

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 5

5 Business Objects - Technology Checks

Your SAP BusinessObjects Server settings were compared with

Rating Check Description

5.1 Business Objects Versions

Number of Servers Type of Server Version

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 6

Number of Servers Type of Server Version

5.2 Performance & Availability Overview

5.2.1 Report Overview

KPI Name KPI Value Description

5.2.2 BOE Server Availability

Date/Time Interval Servers running Servers stopped

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 7

Date/Time Interval Servers running Servers stopped

5.2.3 CMS Server Metrics

5.2.4 Failed Schedules Overview

Date Schedules completed Schedules failed

5.2.5 User Workload Overview

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 8

Date Max. Concurrent Users logged on Max. Named Users logged on

5.2.6 Average Runtimes & Requests

WEB INTELLIGENCE REQUESTS

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 9

5.2.7 Top WebIntelligence Documents

5.2.8 Top Calls to Data Source

Call Average runtime (ms) Executions

5.2.9 Top SAP BW Calls

Call Average Runtime (ms) Executions

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 10

5.2.10 Timed-out Requests

5.3 Key Performance Indicators

KPI Name KPI Description Host Date

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 11

KPI Name KPI Description Host Date

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 12

KPI Name KPI Description Host Date

5.4 Business Objects Server Settings

Analysi Server Name CM WebiProcSe CRProcSe JobSer CRCacheSe RepAppSe

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 13

Analysi Server Name CM WebiProcSe CRProcSe JobSer CRCacheSe RepAppSe

5.4.1 Job Server DIAGP001.AdaptiveJobServer

5.4.2 Central Management Server Settings

5.4.3 Crystal Report Cache Server DIAGP001.CrystalReportsCacheServer

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 14

Parameter Description Current Value Recommended Rating

5.4.4 Job Server DIAGP001.CrystalReportsJobServer

5.4.5 Crystal Report Processing Server

EarlyWatch Alert, SAP AG R11, 07.06.2010 - 13.06.2010 15

Parameter Description Current Value Recommended Rating

5.4.6 Job Server DIAGP001.DesktopIntelligenceJobServer