BPC RCA & Monitoring

BPC RCA & Monitoring

Best Practice for SAP BPC

Version Date: January 2010

Contents

1 Root Cause Analysis .......................................................................................................................... 2

1.1 Solution Manager with BPC Microsoft Version (with Diagnostic Agent) ................................ 2

1.1.1 Change Reporting (Viewer and Compare) ...................................................................... 2

1.1.2 File System Browser ........................................................................................................ 5

1.1.3 OS Command Console .................................................................................................... 7

2 Monitoring Tools ...............................................................................................................................10

2.1 DBACockpit ..........................................................................................................................10

2.2 CA Wily Introscope ............................................................................................................... 11

2.2.1 CA Wily Introscope.NET Agent ...................................................................................... 11

2.2.2 CA Wily Introscope Workstation..................................................................................... 11

2.3 BPC Management Console (MS version) ............................................................................26

2.3.1 Accessing BPC Management Console ..........................................................................26

2.3.2 Navigating the Home Screen .........................................................................................27

2.3.3 Navigating the Database Server Screens ......................................................................37

2.3.4 Navigating the BPC Logging Screens ...........................................................................44

2.4 CCMS Monitoring with SAPCCMSR Agent .........................................................................49

3 Further Information ...........................................................................................................................53

3.1 Memory Metrics Information – Appendix..............................................................................53

Best Practice: BPC MS RCA & Monitoring

© 2010 SAP AG

2

1 Root Cause Analysis

1.1 Solution Manager with BPC Microsoft Version

(with Diagnostic Agent)

1.1.1 Change Reporting (Viewer and Compare)

With Solution Manager’s Change Reporting, we can view the content of BPC_MS components configuration file to check the current configuration values for example to identify wrong values. It also allows comparing configuration values between 2 technical systems or between 2 dates on one technical system (Compare) to identify what had been changed or the difference.

To perform BPC_MS configuration changes monitoring, you can use the Change Reporting tool in SAP Solution Manager Work Centers. Go to Root Cause Analysis System Analysis Select the correct System ID Click on Change Reporting button.


© 2010 SAP AG

3

Inside Change Reporting there are 2 tabs, Viewer tab and Compare tab.

Change Reporting: Viewer

Under the Viewer tab, you can view the important configuration files of each BPC_MS component (BPC .NET Server, Microsoft IIS and Microsoft .NET Framework) by expanding down the selected node.

Select the date on the Timestamp and click on Apply button. On each selected configuration node, you will see the detail or contents of the configuration on the right hand side. Select the configuration file in the Store List will expands the content of the configuration file on Store Content.


© 2010 SAP AG

4

Change Reporting: Compare

With Compare, you can make a configuration file comparison between 2 different BPC Technical Systems in the Solution Manager, or you can do comparison of configuration file on a BPC Technical System between 2 dates.

With this Compare function, you should be able to identify the difference between working and not-working environment cases.

The Compare screen contains 3 areas:

1. Reference System/date

2. Custom System/date

3. Result Summary

Select the base configuration of a Technical System and/or Date in the Reference area and the counterpart for comparison in the Custom area then select the configuration node. Choose comparison type, Fast or Deep, and choose the Compare button.

The result of the comparison will be shown in the Result Summary area.


© 2010 SAP AG

5

1.1.2 File System Browser With Solution Manager’s File System Browser we can browse BPC_MS components files, put the files into our basket for later analysis, and download the files to our local drive.

To perform the File System Browser in Solution Manager’s Work Centers, go to Root Cause Analysis Hot Analysis Select the application server host of interest File System Browser

Tips: You must have Internet Explorer as your default browser to open the File System Browser (?)

On the opened Internet Explorer, you will find 3 pre-defined folders:

BPC folder, pointed to %Drive%:\BPC folder in the application server.


© 2010 SAP AG

6

sap folder, pointed to %Drive%:\USR folder in the application server.

WINDOWS folder, pointed to %Drive%:\WINDOWS folder in the application server.

You can add file(s) into your basket by marking a checkbox on the file(s) and either choosing Add All to Basket or Add Selection to Basket button on the top side.

You can show the content of your Basket by choosing the Show Basket button on the top side.

To download the files, or to open or show your Basket, select the file(s) and click on Get All/GetFile

button on the top side then on the pop up window, choose Click Here To Save The File. You delete

them from the Basket by clicking on Remove File or Remove All button.


© 2010 SAP AG

7

Tips: The content of the Basket will be removed automatically when your session ends if you do not

save the basket via Basket Manager.

You can use Basket Manager to organize your file(s) into more than one Basket and load them back to workspace when you need them.

After you add a file(s) into a Basket, it will be saved in <current> basket which is temporary basket. You can permanently save the Basket and give it a name in Basket Manager.

To save and name the Basket, go to Basket Manager select <current> Basket click on Edit button.

Edit the Name field (remove <current> text) and type in your Basket name and write some texts in Description field.

You can load back the Basket’s content by clicking the Load button in Basket Manager and you will see the loaded file(s) in the Basket in File System Browser.

Tips: When you save again after the loading, the file(s) will be stored in a new Basket.

To delete a saved Basket, click on Delete button in the Basket Manager.

1.1.3 OS Command Console With Solution Manager’s OS Command Console, we can run the pre-defined Operating System commands to help us to troubleshooting at OS level.


© 2010 SAP AG

8

To open the OS Command Console in Solution Manager’s Work Centers, go to Root Cause Analysis Hot Analysis Select the application server host of interest Os Command Console.

Tips: You must have Internet Explorer as your default browser to open the OS Command Console.


© 2010 SAP AG

9

OS Command Console window contains 3 main panes:

1. Prompt pane

2. Result pane

3. History pane

In the Prompt pane, you select the monitored system, the hostname, Group of commands, and the

command that you want to run. Note that you can only run the pre-defined commands in the Prompt

Pane. You can put parameter(s) for the command (optional) and you can specify whether to run the

command once (Option = Simple) or you want to run the command multiple time (Option = Recurrent)

by specifying the Interval for each run.

Here are some pre-defined OS Commands that would be helpful:

No. Group Command Description

1 Network Netstat Shows active connections on the server

2 Network IPConfig Shows the IP configuration on the server

3 Network Ping Test connection from the server to the other computer

4 System Tasklist Shows the current running processes on the server (similar

to Task Manager)

5 System CpuStat Shows the CPU usage on the server

6 System MemStat Shows the current memory usage on the server

In Result pane, you will see the result of the command that you run.

In History pane, the command(s) that you run will be logged for your future reference. You can delete

the whole commands history by clicking on Clear History button or click on Delete Command button

for deleting single command history.


© 2010 SAP AG

10

2 Monitoring Tools

2.1 DBACockpit

With SAP_BASIS support package 12, SAP delivers a new database monitor transaction

DBACOCKPIT, which combines the functionality of the older transactions ST04, DB02, DB12 and

DB13 and of ABAP program MSSPROCS. The main advantages of the new transaction are improved

functionality, a more consistent user interface and the option to remotely monitor multiple SAP and

non-SAP databases from one central system (for example, a Solution Manager system).

DBACOCKPIT works for all database platforms supported by SAP including Microsoft SQL Server in

BPC_MS (see SAP Note: 1027512 for more information on DBACOCKPIT with MSSQL).

Tips: You need at least one Windows based Application server on your Solution Manager to do MS

SQL Server monitoring with DBACockpit


© 2010 SAP AG

11

2.2 CA Wily Introscope

2.2.1 CA Wily Introscope.NET Agent

With CA Wily Introscope.NET Agent, we can monitor the BPC .NET Application Server. The

Introscope .NET Agent instruments the BPC .NET components by measuring the average response

time of the methods in .NET classes and stores it in the CA Wily Introscope Enterprise Manager.

CA Wily Introscope instruments 3 areas in BPC_MS which are:

1. Send Data processes

2. Retrieve Data processes

3. Data Manager processes

2.2.2 CA Wily Introscope Workstation

With CA Wily Introscope WorkStation or Introscope Webview, we can monitor the average response

time of each BPC_MS .NET components that get involved during each process.

You can access the Introscope WorkStation or Introscope Webview from Solution Manager Work

Centers Host Analysis Select the BPC system Introscope WorkStation or Introscope Webview

(on left pane under Offline Analysis)

Enterprice Manager

BPC App

Server

.NET Agent

BPC App

Server

.Net Agent

BPC App

Server

.NET Agent

Introscope

Workstation

/Webview


© 2010 SAP AG

12

This document will use Introscope Workstation as a guideline, but you will find the similar functionality

and look & feel on Introscope Webview which is a web based GUI.

On the pop up logon screen, type in the Wily Introscope username and password:

Inside the Introscope Workstation Console view, you will find BPC_MS and BPC_NW on the

navigation dashboard.


© 2010 SAP AG

13

There are 2 links in BPC_MS navigation: Triage link to BPC_MS Triage dashboard and Overview link

to BPC_MS Overview dashboard.

Click the Overview link. You will be brought to BPC_MS Overview dashboard as shown below. The

Overview dashboard contains 3 quick links to:

1. BPC_MS Retrieve Data Triage dashboard.

2. BPC_MS Send Data Triage dashboard.

3. BPC_MS Data Manager Triage dashboard.


© 2010 SAP AG

14

Click the Triage link. You will be brought to BPC_MS Triage dashboard as shown. The Triage

dashboard contains the Average response time graph of Web Services of each BPC_MS processes

like Retrieve Data process, Send Data process and Data Manager process. These graphs would give

you a quick view on the Web Services average response time of each process so you can find the

higher response time activities in your BPC_MS system quickly.

There are quick links to CPU and Memory usage for each OS process, where you can jump into the

CPU utilization dashboard and Memory utilization dashboard for further analysis.


© 2010 SAP AG

15

2.2.2.1 Using Introscope Workstation: How to Read the Graph

On every graph, if you hover your mouse on a point in the graph, you will get value information of the

measure.


© 2010 SAP AG

16

2.2.2.2 Using Introscope Workstation: How to Analyze Retrieve Data process

You can start the Retrieve Data process analysis on the Introscope Workstation by going to BPC

Retrieve Data dashboard from BPC Overview dashboard click on BPC Retrieve Data link.

Retrieve Data dashboard shows the metrics of each component, which is involved in data retrieving

process. It measures the average response time start from when a retrieve request come into the

system from Microsoft IIS web services, BPC DLL library components, BPC SQE methods and

Microsoft ADO .NET components. Therefore, this looks more like a request calls flow in BPC_MS

Retrieve Data process.


© 2010 SAP AG

17

Note that this is a simplified diagram to get the picture of Retrieve Data process quickly.

When a request comes in, you will see a metric in the BPC WebService graph, followed by a metric in

BPC DLL Library. Based on the requested data, the BPC_MS Shared Query Engine (SQE) could

retrieve the data either from Microsoft Analysis Service with MDX statements or Microsoft SQL

Database with SQL statements.

For data that contains Non-based members, SQE will generate MDX query by calling getOLAP

method then queries Microsoft Analysis Service. Then, you will see a metric in BPC SQE Engine

getOLAP graph and metric in BPC SQE Engine to MS Analysis Service.

For data that contains only Based members, SQE will generates SQL query by calling getSQL method

then queries Microsoft SQL Server. Then, you will see a metric in BPC SQE Engine getSQL graph

and metric in BPC SQE Engine to MS SQL Server. Note: The metrics in BPC SQE Engine to MS SQL

Server could also include other SQL statements metric which not related to data retrieval from FACT

tables but were triggered by SQE components to MS SQL Server.

To extend your analysis on the total CPU utilization of each OS process in BPC Retrieve Data process,

you can go to BPC_MS Triage dashboard click BPC Retrieve Data CPU Usage link on the right-

hand side.

MS Excel BPC

Plug-In

MS Analysis

Services

MS SQL

Server

HT

TP

/s -

SO

AP

IIS

BPC WS Components DLL

SQE Data Access Components

.net server

AD

O .N

ET

TC

P/IP


© 2010 SAP AG

18

There are 2 main OS processes which work on the server side to run the BPC Retrieve data: W3WP

process and OSoftDataService process (COM+). The higher value on the CPU metrics is 100%

For memory analysis on each OS process in BPC Retrieve Data process, you can go to BPC_MS

Triage dashboard click BPC Retrieve Data Memory Usage link on the right side.


© 2010 SAP AG

19

There are 5 memory metrics for each OS process which are Private Bytes, Working Set, Working Set

Peak, Virtual Bytes and Virtual Bytes Peak. See Memory Metrics Information Appendix for more

information.

2.2.2.3 Using Introscope Workstation: How to Analyze Send Data process

You can start the Send Data process analysis on Introscope Workstation by go to BPC Send Data

dashboard from BPC Overview dashboard click on BPC Send Data link.


© 2010 SAP AG

20

Send Data dashboard shows the metrics of each component which is involved in the data sending

process. It measures the average response time start from when a retrieve request come into the

system from Microsoft IIS web services, BPC DLL library components, BPC SG check and submit

launch methods and SG’ s Stored Procedures to store the data into FACT tables. Therefore, this

looks more like a request calls flow in BPC_MS Send Data process.

When a request comes in, you will see a metric in the BPC WebService graph, followed by a metric in

the BPC DLL Library. The incoming data will be stored into SG queue tables. SG will do a regular

check on its queue tables; you will see a regular spike on the metric in BPC SendGovernor Sending

Check graph. When data is ready to be submitted into the FACT tables, SG will trigger launch sending

process and the average response time of this process is shown in BPC SendGovernor Launch

Sending graph.

BPC SG calls the correct SQL Server stored procedures to perform a data update into the FACT

tables based on the submitted parameter or type of data. The stored procedures are:

1. SP1#_<APP> stored procedure; if SG has to perform Difference Calculation and Signs Data

Conversion.

2. SP2#_<APP> stored procedure; if SG has to perform Difference Calculation only on the data.


© 2010 SAP AG

21

3. SP3#_<APP> stored procedure; if no additional operation is needed on the data and SG simply

submit the data into FACT table.

You can find the average response time of each stored procedure below the BPC Send Data

dashboard

To extend your analysis on total CPU utilization of each OS process in BPC Send Data process, you

can go to BPC_MS Triage dashboard click BPC Send Data CPU Usage link on the right-hand side.

The highest value on the CPU metrics is 100%

For memory analysis on each OS process in BPC Send Data process, you can go to BPC_MS Triage

dashboard click BPC Send Data Memory Usage link on the right-hand side.


© 2010 SAP AG

22

There are 5 memory metrics for each OS process, which are Private Bytes, Working Set, Working Set

Peak, Virtual Bytes, and Virtual Bytes Peak. See Memory Metrics Information Appendix for more

information.

2.2.2.4 Using Introscope Workstation: How to Analyze Data Manager Process

You can start the Data Manager process analysis on the Introscope Workstation by going to Data

Manager dashboard from BPC Overview dashboard click BPC Data Manager link.


© 2010 SAP AG

23

The Data Manager dashboard shows the metrics of each component, which is involved in BPC Data

Manager package run process. It measures the average response time start from when a retrieve

request come into the system from Microsoft IIS web services, BPC DLL library components, and

Microsoft SSIS packages execution runtime.

When a request comes in, you will see a metric in the BPC WebService graph followed by metric in

BPC DLL Library. Microsoft SSIS RunTime Execute graph will show you the average response time of

a SSIS package run and SSIS Tasks graph will show the average response time of each task inside

the package that run.

With the metric in SSIS Tasks graph, you can see the average response time of each task inside a

package. For example, inside BPC Data Manager Export package, it contains 2 tasks, Dump Data and

Convert Data, and each task will be executed dependently. When there is a long running package in

BPC Data Manager, we can use this metric to find which individual task took the longest time.


© 2010 SAP AG

24

In SSIS Tasks graph you will see the average response time for Dump Data task (Dark Yellow line in below example) and the Convert Data task (Green line in below example).

To extend your analysis on total CPU utilization of each OS process in BPC Data Manager process,

you can go to BPC_MS Triage dashboard click on BPC Data Manager CPU Usage link on the right-

hand side.

SSIS Package name: Export.dtsx

Number of Tasks: 2

Tasks Detail:

1. Dump Data (DumpLoad task)

2. Convert Data (Convert task)

BPC Data Manager Package: Export

SSIS Package name: Clear.dtsx

Number of Tasks: 3

Task Detail:

1. Export_Zero (DumpLoad task)

2. Load Cube (DumpLoad task)

3. Clear Comments (Comment task)


© 2010 SAP AG

25

There are 2 main OS processes which work on the server side to run the BPC Retrieve data: W3WP

process and OSoftDMServer process (COM+). The higher value on the CPU metrics is 100%

For memory analysis on each OS process in the BPC Data Manager process, you can go to BPC_MS

Triage dashboard click on BPC Data Manager Memory Usage link on the right-hand side.


© 2010 SAP AG

26

There are 5 memory metrics for each OS process which are Private Bytes, Working Set, Working Set

Peak, Virtual Bytes and Virtual Bytes Peak. See Memory Metrics Information Appendix for more

information.

2.3 BPC Management Console (MS version)

BPC Management Console is a web based monitoring tool which comes with BPC Server installation.

It provides performance metrics on the Windows Operating System (OS), Microsoft SQL Server and

Microsoft Analysis Server. In additional to providing performance metrics, the BPC Management

Console also can activate and deactivate BPC logging as well as manage logging schedules.

2.3.1 Accessing BPC Management Console

To access the Management Console, Open your internet browser and type

http://<servername>/managementconsole, where <servername> is the name of your application

server. If you are in the NLB environment, this means you monitor only the specified BPC application

server or the <servername> application server.


© 2010 SAP AG

27

2.3.2 Navigating the Home Screen

Once connected to the Management Console, you are immediately taken to the Home screen, which

acts as an overview of all functionality.

Task Manager


© 2010 SAP AG

28

In the upper left hand corner is the Task Manager monitor. This is the same functionality as the

Windows Task Manager Process tab. The processes listed are sorted by which process is consuming

the most memory at the given time.

If you click on the Process ID (PID), that process will populate the box immediately to the right of the

Task Manager box. If the PID is a BPC DLLHOST, it will populate the corresponding BPC COM+

object.

Any process can be ended using this screen.

Hits by Users

The Hits by User pie chart will show a breakdown of by each user and what pages they have

accessed on the web server.

Hits by Users

The Status Breakdown returns IIS status codes per user. This can be helpful in identifying trends such

as user authentication issues.

System Performance (Appserver)

In the lower left hand corner is the System Performance (Appserver) screen. This screen shows

several counters from Windows Performance Monitor also known as Perfmon. By default, it will

monitor:

- CPU Utilization: Indicates the current processor load, as a percentage. This number is an average

across all of the available processors or cores available on the machine.

- Memory: Page Writes / sec: The rate at which pages are written to disk to free up space in physical

memory. Pages are written to disk only if they are changed while in physical memory, so they are

likely to hold data, not code. This counter shows write operations, without regard to the number of

pages written in each operation. This counter displays the difference between the values observed in

the last two samples, divided by the duration of the sample interval.

- Available Bytes: The amount of physical memory, in bytes, immediately available for allocation to a

process or for system use. It is equal to the sum of memory assigned to the standby (cached), free

and zero page lists. For a full explanation of the memory manager, refer to MSDN and/or the System

Performance and Troubleshooting Guide chapter in the Windows Server 2003 Resource Kit.

Add PerfMon Counter


© 2010 SAP AG

29

Additional counters can be added using the Add PerfMon Counter button in the top right-hand corner

of the System Performance (Appserver) screen.

Set Thresholds

A visual alert can be set using the Set Thresholds functionality. When a counter meets criteria that you

set, the System Performance (Appserver) screen will be outlined in red.

Example: If the CPU Utilization reaches a value of 30%, the threshold will show the visual indicator.


© 2010 SAP AG

30

Compare

The counters that are in use can be compared among two BPC servers. By choosing the Compare

button, the Management Console will bring up a split screen view of the two BPC servers of your

choice, monitoring the same counters on each server.

Server Disk IO


© 2010 SAP AG

31

The Server Disk IO screen displays the following counters from the Physical Disk object from Perfmon:

- Avg Disk Bytes per Read: The average number of bytes transferred from the disk during read

operations.

- Avg Disk Write Queue Length: The average number of both read and write requests that were

queued for the selected disk during the sample interval.

- Current Disk Queue Length: The number of requests outstanding on the disk at the time the

performance data is collected. It also includes requests in service at the time of the collection. This is

an instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have

multiple requests that are active at one time, but other concurrent requests are awaiting service. This

counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk

drive, it is likely that this will be consistently high. Requests experience delays proportional to the

length of this queue minus the number of spindles on the disks. For good performance, this difference

should average less than two.

Analysis Services Connections and Locks

The Analysis Services Connections and Locks screen contains several counters from several MSAS

objects in Perfmon.

- Current Locks: Current number of locked objects.

- Current Lock Waits: Current number of clients waiting for a lock.

- Current Connections: Current number of client connections established.

- Cache Evictions per Second: Rate of evictions from the cache. This is per partition per cube per

database, typically due to background cleaner.

2.3.2.1.1 Navigating the Web Server Screens

The Web Server sub menu contains the following sub screens:

- Summary

- Who is Online

- Services


© 2010 SAP AG

32

Summary

The Summary screen contains the information on what users are online, what IIS status codes have

been returned on the Web Server, and what web pages are being used.

Summary: Who’s Online

The Who’ s Online screen will show all users who have been online for the given period of

time, by default, the screen will show all users online for the last twenty minutes.

Summary: Services

The Service Status screen show a summary of all IIS service status codes, their description

and the total number of times the status code has been generated.

Summary: All Active Pages


© 2010 SAP AG

33

The All Active Pages screens show which BPC web pages have been used in the given

period of time. One screen shows in pie chart format, the other has the same information in

list format.


© 2010 SAP AG

34

Who’s Online

The Who’ s Online screen contains information on all users that are online, details about what pages

those users are hitting, and summary IIS status codes for each user.

Who’s Online: Who’s Online

The Who’ s Online screen contains information about all users online for a given time period

and lists the number of page hits each user had.

Who’s Online: Page Hits by User

The Page Hits by User screen shows information provided in the Who’ s Online screen in

pie chart format.

Who’s Online: Selected User Detail

The Selected User Detail screen shows detailed information on which user is selected in the

Who’ s Online screen. Details include the total count of each page hit, first and last request


© 2010 SAP AG

35

times, the status code received when requesting the page, the target page itself, and any

parameters passed when requesting the page.

Who’s Online: User Request by Status over time

The User Request by Status over time screen will show the status codes returned for the

selected user in the Who’ s online screen by Current, 1 Day, and 1 Week views.


© 2010 SAP AG

36

Services

The Services screen contains detailed and summary information on all IIS status codes that have

been registered over a given period of time.

Services: Service Status

The Service Status screen shows all IIS status codes that have been recorded over a given

period of time, their description, and the number of times they have occurred.

Services: Service Status Breakdown

The Service Status Breakdown screen shows the same information on the Service Status

screen, but in pie chart format.

Services: Selected Status Detail

The Selected Status Detail screen shows detailed information about the status code that was

selected in the Service Status screen. From here, you can see which user the selected status

coded happened to as well as the first request, latest request, target page, and any

parameters that were passed during the request.

Services: Selected Status Over Time


© 2010 SAP AG

37

The Selected Status Over Time screen will show the status code selected by the user in the

Service Status screen by Current, 1 Day, and 1 Week views.

2.3.3 Navigating the Database Server Screens

The Database Server sub menu contains the following sub screens:

- Summary

- Microsoft SQL Server

- Microsoft Analysis Server

Summary

The Summary screen contains the information on SQL Server Who functionality, SQL Server Statistics,

System Performance (Database Server), and Analysis Services Connections & Locks.


© 2010 SAP AG

38

Summary: Who

The Who screen displays the following information on current activity for database:

System process id (SPID)

Status of process

Login name of user

Host name of machine

SPID of blocking process

Name of database process is using

Command being executed

Summary: SQL Server Statistics

In the upper right hand corner is the SQL Server Statistics screen which displays the

following counters from the SQLServer: General Statistics object from Perfmon:

User Connections: Number of users connected to the system.

OLE DB Calls: Event class occurs when SQL Server calls an OLE DB provider for

distributed queries and remote stored procedures.

Active Temp Tables: Number of temporary tables/table variables in use.

Processes Blocked: Number of currently blocked processes.

Summary: System Performance (Database Server)


© 2010 SAP AG

39

In the lower left-hand corner is the System Performance (Database Server) screen. This

screen is the same as Windows Perfmon monitor. By default it will monitor:

CPU Utilization: Indicates the current processor load, as a percentage. This number is

an average across all of the available processors or cores available on the machine.

Memory: Page Writes / sec: The rate at which pages are written to disk to free up

space in physical memory. Pages are written to disk only if they are changed while in

physical memory, so they are likely to hold data, not code. This counter shows write

operations, without regard to the number of pages written in each operation. This

counter displays the difference between the values observed in the last two samples,

divided by the duration of the sample interval.

Available Bytes: The amount of physical memory, in bytes, immediately available for

allocation to a process or for system use. It is equal to the sum of memory assigned

to the standby (cached), free and zero page lists. For a full explanation of the memory

manager, refer to MSDN and/or the System Performance and Troubleshooting Guide

chapter in the Windows Server 2003 Resource Kit.

Summary: Analysis Services Connections & Locks

The Analysis Services Connections and Locks screen contains several counters from several

MSAS objects in Perfmon.

Current Locks: Current number of locked objects.

Current Lock Waits: Current number of clients waiting for a lock.

Current Connections: Current number of client connections established.

Cache Evictions per Second: Rate of evictions from the cache. This is per partition

per cube per database, typically due to background cleaner.

Microsoft SQL Server

The SQL Server screen contains information on SQL Server’ s Who and Who2 functionality, SQL

Server Agent Statistics, Database Disk I/O, SQL Server Statistics, and Operations by Database.


© 2010 SAP AG

40

Microsoft SQL Server: Who

The Who and Who2 procedures provide information about current SQL Server connections,

the applications used to connect to the SQL Server, and the type of work each connection is

performing.

System process id (SPID): System process id that requested the lock.

Status of process: Runnable, sleeping, or background. If the status is runnable that

means the process is actually performing work, sleeping means the process is

connected to the server, but is idle at the moment.

Login name of user: The login that has initiated the lock request.

Host name of machine: The name of the computer where the lock request was

initiated.

SPID of blocking process: The connection that is blocking the lock request from the

current connection.


© 2010 SAP AG

41

Name of database process is using: Database name where the lock has been

requested.

Command being executed: General command type that requested the lock.

Microsoft SQL Server: Who2

Who2 is a newer version of Who. It returns some additional information.

System process id (SPID): System process id that requested the lock.

Status of process: Background, sleeping, or runnable.

Login name of user: The login name that has requested the lock.

Host name of machine: The computer where the lock request has been initiated.

SPID of blocking process: The spid of the connection that is blocking the current

connection.

Name of database process is using: The database name where the lock request has

been generated.

Command being executed: General command type that requested the lock.

Total CPU time process took: The number of milliseconds the request has used.

Total amount of disk reads: Disk input /output that the command has used.

Last time client called procedure: Date and time of the last batch executed by the

connection.

Application that initiated the connection: The name of the application that issued the

connection.

Microsoft SQL Server: SQL Server Agent Statistics

Displays jobs that are currently running on SQL Server.

Microsoft SQL Server: Database Disk I/O

In the lower left-hand corner is the Database Disk IO screen which displays the following

counters from the Physical Disk object from Perfmon:

Avg Disk Bytes per Read: The average number of bytes transferred from the disk

during read operations.


© 2010 SAP AG

42

Avg Disk Write Queue Length: The average number of both read and write requests

that were queued for the selected disk during the sample interval.

Current Disk Queue Length: The number of requests outstanding on the disk at the

time the performance data is collected. It also includes requests in service at the time

of the collection. This is an instantaneous snapshot, not an average over the time

interval. Multi-spindle disk devices can have multiple requests that are active at one

time, but other concurrent requests are awaiting service. This counter might reflect a

transitory high or low queue length, but if there is a sustained load on the disk drive, it

is likely that this will be consistently high. Requests experience delays proportional to

the length of this queue minus the number of spindles on the disks. For good

performance, this difference should average less than two.

Microsoft SQL Server: SQL Server Statistics

In the lower middle is the SQL Server Statistics screen which displays the following counters

from the SQLServer: General Statistics object from Perfmon:

User Connections: Number of users connected to the system.

OLE DB Calls: Event class occurs when SQL Server calls an OLE DB provider for

distributed queries and remote stored procedures.

Active Temp Tables: Number of temporary tables/table variables in use.

Processes Blocked: Number of currently blocked processes.

Microsoft SQL Server: Operations by Database

The Operations by Database screen provides the total percentage of operation by database

in pie chart format.

Microsoft Analysis Services

The Analysis Services sub screen contains the following two screens:

Microsoft Analysis Services: Connections & Locks

Microsoft Analysis Services: Disk IO


© 2010 SAP AG

43

Microsoft Analysis Services: Connections & Locks

The Analysis Services Connections and Locks screen contains several counters from several

MSAS objects in Perfmon.

Current Locks: Current number of locked objects

Current Lock Waits: Current number of clients waiting for a lock

Current Connections: Current number of client connections established

Cache Evictions per Second: Rate of evictions from the cache. This is per partition

per cube per database, typically due to background cleaner.

Microsoft Analysis Services: Disk I/O

The Analysis Services Disk IO screen displays the following counters from the Physical

Disk object from Perfmon:


© 2010 SAP AG

44

Avg Disk Bytes per Read: The average number of bytes transferred from the disk

during read operations.

Avg Disk Write Queue Length: The average number of both read and write requests

that were queued for the selected disk during the sample interval.

Current Disk Queue Length: The number of requests outstanding on the disk at the

time the performance data is collected. It also includes requests in service at the time

of the collection. This is an instantaneous snapshot, not an average over the time

interval. Multi-spindle disk devices can have multiple requests that are active at one

time, but other concurrent requests are awaiting service. This counter might reflect a

transitory high or low queue length, but if there is a sustained load on the disk drive, it

is likely that this will be consistently high. Requests experience delays proportional to

the length of this queue minus the number of spindles on the disks. For good

performance, this difference should average less than two.

2.3.4 Navigating the BPC Logging Screens

By choosing the BPC>Logging sub menu, you can do the following:

Viewing, Managing Current Logs & Historical Logs

Manage Debug Logs

Perform a Server Diagnostic

Manage System Logs


© 2010 SAP AG

45

After choosing Logging, you will be prompted to log into your appset. You must be a Web Admin (in

BPC Security) to log into this section.

Viewing, Managing Current Logs and History Logs

Helpful logs can be viewed by choosing View Current Logs. This screen can be filtered by the ID,

System, and Job fields. Please note that you are not able to filter on the Date column.


© 2010 SAP AG

46

To narrow down the number of logs you are viewing, move logs to a historical table. This can be done

using the Manage System Logs functionality. Using this functionality, you can move all logs to history,

delete all historical logs, schedule their movement, and set parameters to delete the historical logs.

By default, current logs are kept in the tblLogs table and the historical logs are located in tblLogHist in

the Appserver database.


© 2010 SAP AG

47

Managing Debug Logs

The Manage Debug logs section lets you enable logging for BPC for Excel, the BPC Administration

and Live Reporting.

Select the logs you wish to enable and click the Update/Close button. When you enable logs, they are

written to the database, they are no longer saved as files so they will not be located in their usual

directories. You should be able to view them in the management console. When you disable them, the

logging stops and the information does not get deleted.

Server Diagnostic

The Server Diagnostic functionality is the same as is provided in the Server Manager utility located on

the application server. The diagnostic can give important details on:

Server Computer / User Profile: Displays information on who is logged to the

Management Console and Server Information.


© 2010 SAP AG

48

Microsoft and Third-Party Software: Displays status information on version of

prerequisite software and status of NTFS drives

Computer Services Status: Displays status information on required services that need

to be running

COM+ Component Service: Displays status information on all SAP BPC COM+

objects

Appserver DB in SQL Server: Displays connection status information to the Appserver

database on the SQL server

IIS Configuration: Displays configuration status information on the OSOFT virtual

directory in IIS


© 2010 SAP AG

49

2.4 CCMS Monitoring with SAPCCMSR Agent

SAP Solution Manager 7.0 EhP1 can be used as central monitoring system for SAP Business Objects

Business Planning and Consolidation, both Microsoft and NetWeaver version. It provides Basic

availability monitoring (GRMG scenario), error monitoring (log files and Windows Event log monitoring),

operating system monitoring (process monitoring) and alert monitoring.

Please refer to SAP Note: 1379213 - CCMS-based Monitoring for SAP BusinessObjects BPC

Microsoft for further information about CCMS monitoring setup and configuration on BPC_MS. The

SAP Note is also workable for BPC_MS 7.0 version.


© 2010 SAP AG

50

With transaction code RZ20, you can access the CCMS Monitor Sets in the Central Monitoring System

(CEN) and expands the monitoring tree element (MTE) to the configured BPC system.

Double-click the Availability Monitoring node; you get the system availability monitoring with GRMG

scenario that shows if any service is down that could, for example, disturb the system as whole.

SOLMAN

Central Monitoring

System (CEN)

Application Server(s)

IIS + BPC components

SAPCCMSR

Microsoft SQL Server

SAPCCMSR

Microsoft Reporting Server

SAPCCMSR

Microsoft Analysis Server

SAPCCMSR


© 2010 SAP AG

51

Double-click the Error Monitoring node; you will get the error information from the system log files.

Double-click the Operating System Monitoring node; you will get the server’ s information such as

CPU utilization, Memory, Processes and Event Log information.


© 2010 SAP AG

52


© 2010 SAP AG

53

3 Further Information

3.1 Memory Metrics Information – Appendix

1. Private Bytes: represents the amount of private virtual memory a process has allocated. This

memory cannot be shared with other processes. If the Private Bytes metric rises steadily, the

process is exhibiting a memory leak bug.

2. Working Set: represents the virtual address space of the process that is currently resident in

physical memory. When you see the Working Set metric goes down steadily, there are 2

possibilities: 1) The process released un-used memory pages from the physical memory or 2) the

system is run out of free physical memory.

3. Working Set Peak: represents the peak amount of Working Set that has been used by a process.

4. Virtual Bytes: the current size, in bytes, of the virtual address space for this process. The virtual

address space limit of a user mode process is 2 GB, unless 3 GB address space is enabled by

using the /3GB switch in boot.ini. Performance degrades as this limit is approached, and typically

results in a process or system crash.

5. Virtual Bytes Peak: represents the peak amount of Virtual Bytes that has been used by a process.


© 2010 SAP AG

54

© Copyright 2010 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

®, NT

®, EXCEL

®, Word

®, PowerPoint

® and SQL Server

® are registered trademarks of

Microsoft Corporation. IBM

®, DB2

®, OS/2

®, DB2/6000

®, Parallel Sysplex

®, MVS/ESA

®, RS/6000

®, AIX

®, S/390

®, AS/400

®, OS/390

®, and

OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix

® Dynamic Server

TM

are registered trademarks of Informix Software Incorporated. UNIX

®, X/Open

®, OSF/1

®, and Motif

® are registered trademarks of the Open Group.

HTML, DHTML, XML, XHTML 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, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials are

provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third party Web pages.

Documents

BPC RCA & Monitoring