System Monitoring for SAP BPC · SAP Solution Manager 7.1 SP8 MAI System Monitoring for SAP...

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2013 SAP AG 1

SAP Solution Manager 7.1 SP8 MAI

System Monitoring for SAP Business

Objects Planning and Consolidation

Applies to:

SAP Business Objects Planning and Consolidation, version for Microsoft platform, as of 7.5, and version for SAP Netweaver, as of 7.5. As Managing System an SAP Solution Manager 7.1 SP08 or higher is required unless mentioned otherwise.

Summary

SAP Business Objects Planning and Consolidation (BPC) is integrated into SAP Technical Monitoring / System Monitoring application SAP Monitoring & Alerting Infrastructure (MAI). This document provides information of how to setup and configure MAI of an SAP Solution Manager managing system with and for BPC managed systems.

Authors: Robin Haettich, Boyang Sha

Company: SAP America Inc., SAP China

Created on: 09 December 2013

Authors Bio

Robin Haettich has been working for SAP America Inc. since 2008. His current focus area is SAP Application Lifecycle Management as well as Solution Operations Management concepts and SAP Solution Manager integration. As Solution Architect, Robin leads customer engagements and projects to implement business process operations standards, procedures, and solutions to make SAP applications and systems ’run better’.

Boyang Sha is working for SAP China, Active Global Support. His current focus area is the support of SAP Business Planning and Consolidation solutions. As product integrator, Boyang works on SAP Solution Manager Diagnostics content and Monitoring & Alerting content for SAP and Business Objects products and applications.

SAP Solution Manager 7.1 SP8 MAI System Monitoring for SAP Business Objects Planning and Consolidation


© 2013 SAP AG 2

Table of Contents

Monitoring & Alerting Infrastructure Integration .................................................................................................. 3

System Monitoring Setup in Solution Manager 7.1 (SP08 and higher) .............................................................. 3

Prerequisites ................................................................................................................................................... 3 System Requirement ................................................................................................................................................... 3

Basic Configuration of Solution Manager ..................................................................................................................... 3

Managed System Setup ............................................................................................................................................... 4

Technical Monitoring Configuration .............................................................................................................................. 4

MAI Content Update .................................................................................................................................................... 5

MAI Content Customization ............................................................................................................................ 7 Customize Template .................................................................................................................................................... 7

Customize Metric ......................................................................................................................................................... 8

Customize Alert .......................................................................................................................................................... 11

Customize Notification ............................................................................................................................................... 13

System Monitoring Setup Procedure ............................................................................................................ 16 Assign Template to Managed System ....................................................................................................................... 16

BPC Specific Templates Assignment ......................................................................................................................... 17

Base Template Content for BPC 7.5 for Netweaver ................................................................................................... 20

Base Template Content for BPC 7.5 for Microsoft ..................................................................................................... 22

Base Template Content for BPC 10.0 for Netweaver ................................................................................................. 25

Base Template Content for BPC 10.0 for Microsoft ................................................................................................... 25

Features of System Monitoring ..................................................................................................................... 28 Overview of System Monitoring for BPC .................................................................................................................... 28

Copyright ........................................................................................................................................................... 32



© 2013 SAP AG 3

Monitoring & Alerting Infrastructure Integration

This document explains the SAP standard BPC Monitoring templates and how to use them to monitor your BPC system, i.e. SBOP PC 7.5. Please refer to the SAP Note 1952575 for further references.

System Monitoring Setup in Solution Manager 7.1 (SP08 and higher)

Technical Monitoring / System Monitoring in SAP Solution Manager requires the setup and configuration in

SAP Solution Manager Configuration / Technical Monitoring. In the following, we describe the steps to setup

and configure the Technical Monitoring / System Monitoring MAI content for SAP BPC.

Prerequisites

System Requirement

Requirements for Managing System:

SAP Solution Manager 7.10 SP08 or higher.

ST-PI SP version higher or equal to the one on managed system.

ST-A/PI SP version higher or equal to the one on managed system.

CA Wily Introscope Enterprise Manager 8.2.4.0 or higher.

Managed System Configuration done for managed system.

Requirements for Managed Systems:

For all components mentioned below, i.e. SBOP PC, ST-PI, ST-A/PI, the latest version is recommended.

SBOP PC 7.5 for Microsoft: Support Package 2 or higher.

SBOP PC 7.5 for Netweaver: Support Package 3 or higher. (Note: Highly recommended Support Package 11 or higher) Add-on ST-A/PI 01M* or higher on SAP CPM BPC ABAP Stack. ST-PI 2008_1XX_ SP0007 required on SAP CPM BPC ABAP Stack.

SBOP PC 10.0 for Microsoft: Support Package 6 or higher.

SBOP PC 10.0 for Netweaver: Support Package 6 or higher. ST-A/PI 01P or higher. ST-PI 2008_1_710_SP0007 or higher.

CA Wily Introscope .Net Agent 8.2.4.0. (for BPC 7.5 for Microsoft and Netweaver)

CA Wily Introscope .Net Agent 9.1.0.0. (for BPC 10 for Microsoft)

Basic Configuration of Solution Manager

Before using any SAP Solution Manager tools including System Monitoring, the System Preparation and Basic Configuration on SAP Solution Managed must be completed. Please refer to SAP SCN webpage http://wiki.scn.sap.com/wiki/display/SMSETUP/Home for guidance and documentation.

http://service.sap.com/sap/support/notes/1952575

http://wiki.scn.sap.com/wiki/display/SMSETUP/Home



© 2013 SAP AG 4

Managed System Setup

Before using any SAP Solution Manager tools including System Monitoring, the Managed System Setup

procedure for your BPC system(s) must be completed successfully according to the guidance in SAP Note

1461749.

Technical Monitoring Configuration

For more detailed generic information about Technical Monitoring / System Monitoring refer to the SCN webpage http://wiki.scn.sap.com/wiki/display/TechOps/System+Monitoring+-+How-to+Guides. There is documentation which describes the setup and configuration process of the first three steps of technical monitoring as well as the creation and customizing of template content.

http://wiki.scn.sap.com/wiki/display/TechOps/System+Monitoring+-+How-to+Guides



© 2013 SAP AG 5

MAI Content Update

New support packages (SPs) and patches of official MAI content (base templates) will be released regularly. The latest SP usually includes new base templates for newly supported products, new or updated metrics and alerts for existing base template, as well as bug fixes. It is important to keep MAI content in your SAP Solution Manager system up-to-date.

To update MAI content in your SAP Solution Manager system, navigate the path below. Log onto SAP Solution Manager -> execute transaction code ‘SM_WORKCENTER’ -> SAP Solution Manager: Configuration -> Technical Monitoring -> Step 2.7 Update Content.

For SAP Solution Manager before SP11, click button ‘Generate Request’ to check whether there is a new content release available, then select the latest released SP entry in the Available Content list, then click button ‘Import Content’. The latest MAI content uploaded by SAP is retrieved by the system and downloaded into the corresponding tables.



© 2013 SAP AG 6

For SAP Solution Manager SP11 or higher, navigate to step 2.7 Update Content, click button ‘refresh’ to check for new MAI content. If there is new content available, click ‘Update Content’, and the MAI content on your SAP Solution Manager system will be updated automatically.



© 2013 SAP AG 7

MAI Content Customization

For better flexibility, SAP provides a tool to customize the MAI template.

For easy customization, SAP has modularized MAI content into several parts with different scope. There are some common parts in all MAI content, i.e. Data Collector, Data Provider, Metric, Alert. Data Collector and Data Provider artifacts are used by metrics to provide data. They are regarded as part of an SAP Solution Manager SP, and can’t be customized via customization tools. Metric and Alert definitions are delivered in and with templates. Their corresponding customization method will be introduced in the following section.

Customize Template

An MAI template is a collection of metric and alerts specific for a product component version. In the settings of a template, you can define some global parameters, display the structure of alerts and metrics, and check the assignment status of the template.

To create or customize a BPC MAI template, navigate the path below: Log onto SAP Solution Manager -> Execute transaction code ‘SM_WORKCENTER’ -> SAP Solution Manager: Configuration -> Technical Monitoring -> Step 4 Template Maintenance. Select a BPC base template, switch to ‘Edit Mode’, and select ‘Expert Mode’. To create a new BPC custom template, please follow the steps below:

1. Click ‘Create Custom Template’.

2. Input the template name started with ‘Z’ to differ from SAP standard template.

3. Set the template global Notification parameter. For detail, please refer to ‘Customize Notification’.



© 2013 SAP AG 8

4. Click the ‘Save’ button and select the package for transport.

Customize Metric

Metric is the minimum unit of a monitoring data entry. A metric can provide different data based on your definition of it.

To create or customize a metric of SAP BPC, navigate the path below: Log onto SAP Solution Manager -> Execute ‘SM_WORKCENTER’ -> SAP Solution Manager: Configuration -> Technical Monitoring -> Step 4 Template Maintenance. Select a BPC custom template, switch to ‘Edit Mode’, and select ‘Expert Mode’. To create a new metric, please follow steps below:

1. To create a new metric, click the button ‘Create -> Metric’.

2. In the pop out page, define the display name of the metric, the category of the metric (Availability,

Performance, Configuration, Exception), class of metric (Metric, Metric Group), metric data type of

representation form (Inter, Floating point, String), unit of data (Byte, Byte per second, CPUs, Days,

Entries, Errors, Gigabytes, Hours), and the text description of function of the metric.

Note: You must define the ‘Name’, ‘Category’, ‘Class’ and ‘Data’ Type at least. When maintaining

‘Class’ filed, select ‘Metric’. For ‘Average BPC Action Response Time' metric of ABAP instance only,

select ‘Metric group’.



© 2013 SAP AG 9

3. Click button ‘Next’ and enter the parameters according to the Template definition table.

In tab ‘Data Collection’, define the data collection interval and choose the correct ‘Data Collector’ and

‘Data Provider’. If the data is collected by a function module on monitored system and transferred by

RFC call, select ‘RFC (pull)’ as the Data Collector. If the data is transferred by SMD agent, select

‘Diagnostic Agent (push)’ accordingly. If the data is collected by CA Introscope agent and extract

from CA Introscope Enterprise Manager, select ‘Introscope EM (push)’. After choosing the ‘Data

Collector’ & ‘Data Provider’, input parameter for the Data Collector in the table below.

Note: For detail info of the parameter for BPC case, please refer to the corresponding template

content in chapter 5.

For the Collection Interval, select 5 Min for Availability, Performance, Exceptions, and select 1 day

for Configuration. For metric ‘Average BPC Action Response Time' of ABAP instance only, use

‘metric group variant’ to maintain parameters as shown below: Input ‘TOTAL’ for the parameter

‘Action’, ‘Application ID’, ‘Appset’. For ‘Last N Minutes’, the values can be 15, 30, 60, 120, 180, 360,

720, 1440. The unit is minute, so 1440 means one day.



© 2013 SAP AG 10

4. In tab ‘Data Usage’, setup the mapping rule for the data storage and aggregation.

5. In tab ‘Threshold’, setup the threshold for the alert trigger.

6. Click ‘Next’, enter the metric name for storage in the next page and click ‘Next’ again.



© 2013 SAP AG 11

7. The metric will be assigned to the alert you created. Leave it as it is and click ‘finish’. Save the

change afterwards locally or assign to corresponding package.

8. The existed metric can also be modified, please refer to step 2 and 3 and save the change you do

afterwards.

Customize Alert

Alert is the implementation of the alerting mechanism. Within an alert, you can configure alerts for metrics and define different forms of alerting.

To create or customize an alert of SAP BPC, navigate the path below: Log onto SAP Solution Manager -> execute transaction code ‘SM_WORKCENTER’ -> SAP Solution Manager: Configuration -> Technical Monitoring -> Step 4 Template Maintenance. Select a BPC custom template, switch to ‘Edit Mode’, and select ‘Expert Mode’. To create a new alert, please follow steps below.

1. Click button ‘Create -> Alert’.

2. Enter the value for the parameters as explained in the screenshot below. ‘Name’ is the display name

of the alert. ‘Category’ should be the same as the one of the metric assigned to it. ‘Severity’



© 2013 SAP AG 12

represents different criticalities. ‘Description’ offers the textual description of the alert.

3. Modify the notification of a specific alert or use the global setting of template. For details, please refer to ‘Customize Notification’.

4. Click ‘Next’ and reenter the alert name.



© 2013 SAP AG 13

5. Click ‘Next’, assign the existing metric and click button ‘Finish’.

6. Modify the assignment between metric and alert if required.

7. Click button ‘Save’.

8. The existed alert can also be modified, please refer to step 2 and 3 in and save the change you do

afterwards.

Customize Notification

Notification is the object in which the alert action rule is defined. To modify notifications, please follow the steps below.

1. The information (especially the email address or equivalent) of recipients are maintained in SAP

Solution Manager. Log on to SAP Solution Manager -> execute transaction code ‘SM_WORKCENTER’ -> Technical Administration -> Notification Management, and click the button ‘Add Recipient’ to maintain the information.



© 2013 SAP AG 14

2. The notification function can be tested, i.e. by generating an alert mail to the recipients maintained.

To generate the alert mail, go to Technical Monitoring -> Alert Inbox. Select an alert in the list and click ‘Create Notification’, then select the recipient and confirm the request. Thereafter, Solution Manager will send out an email to the inbox of the recipient. Log on to the inbox to check whether the email has been received.

3. To maintain the settings in the Notification tab, use either template or alert level setting. The difference is that the settings on template level is the global default setting for all alerts in this template. Moreover, every alert can use its own specific Notification setting. To activate the notification, switch the setting for ‘Auto-Notification’ to active, and add the recipient to the list.



© 2013 SAP AG 15

4. To customize the action plan for On-duty and Absence situation, click the button ‘My Notification Setting’ and maintain the action plan and contact persons for different situations.



© 2013 SAP AG 16

System Monitoring Setup Procedure

To setup the System Monitoring for SAP BPC, assign the template to the corresponding SAP BPC product component version. For SAP BPC ABAP component, an extra report should be activated. The following section describes the steps of template assignment as well as the detailed content of SAP BPC base template.

Assign Template to Managed System

The following section outlines how to assign the template to technical system or technical instance.

1. In SOLMAN_SETUP -> Technical Monitoring -> System Monitoring go to Step 5 “Select Scope”. Then select your system in the system list.

2. Click ‘Next’. In the next step, click the ‘Assign Templates’ of the desired managed object in the object list. For the ABAP component of SAP BPC for Netweaver, assign the template to the technical system. For the other components, assign the template to the technical instance.

3. Select and assign the correct template for the selected SAP BPC object. Make sure that the base template or custom template is assigned to the corresponding SAP BPC system or instance.



© 2013 SAP AG 17

4. Repeat step 3 for all managed objects in the list. After assigning the correct template, select ‘Apply and Activate’ -> 'All managed objects’ button to activate the template. Click ‘Next’ and activate the reporting for the ABAP system if necessary.

BPC Specific Templates Assignment

For SAP BPC, SAP offers 6 standard templates at instance level, and 2 templates at system level. Please refer to the table below for the mapping of SAP BPC product components to SAP BPC template.



© 2013 SAP AG 18

BPC version Technical instance/system Template assigned

BPC 7.5 MS BPC SSAS SAP BPC analysis service (technical instance)

BPC SSIS SAP BPC Integration service (technical instance)

BPC SSRS SAP BPC Reporting service (technical instance)

BPC Application server SAP BPC 7.5 for Microsoft (technical instance)

BPC 7.5 NW ABAP system SAP BPC ABAP 7.5 (technical system)

Application server instance SAP BPC 7.5 for Netweaver (technical instance)

BPC 10.0 NW ABAP system SAP BPC ABAP 10.0 (technical system)

BPC 10.0 MS BPC SSAS SAP BPC analysis service (technical instance)

BPC SSIS SAP BPC Integration service (technical instance)

BPC Application server SAP BPC 10.0 for Microsoft (technical instance)

1. SAP BPC 7.5 for Microsoft: use this base template or the custom template based on this template

and assign to the application server instance of your BPC 7.5 for MS unspecific cluster system as follows.



© 2013 SAP AG 19

2. SAP BPC 10.0 for Microsoft: use this base template or the custom template based on this template and assign to the application server instance of your BPC 10.0 for MS unspecific cluster system as follows.

3. SAP BPC 7.5 for Netweaver: use this base template or the custom template based on this template and assign to the Dot.Net web server instance of your BPC 7.5 for NW unspecific cluster system as follows.

4. SAP BPC ABAP 7.5: use this base template or the custom template based on this template and assign to the application technical system of your BPC 7.5 for Netweaver ABAP system as follows.

5. SAP BPC ABAP 10.0: use this base template or the custom template based on this template and assign to the application technical system of your BPC 10.0 for Netweaver ABAP system as follows.



© 2013 SAP AG 20

6. SAP BPC Analysis service: If you are on BPC 7.5 or 10.0 Microsoft version, use this template and assign to the SSAS instance of your unspecific cluster system.

7. SAP BPC Integration service: If you are on BPC 7.5 or 10.0 Microsoft version, use this template and assign to the SSIS instance of your unspecific cluster system.

8. SAP BPC Reporting service: If you are on BPC 7.5 Microsoft version, use this template and assign to the SSRS instance of your unspecific cluster system.

Base Template Content for BPC 7.5 for Netweaver

For BPC 7.5 Netweaver ABAP server component, template name: SAP BPC ABAP 7.5 (Technical System).

Alert name Alert explanation Metric name Data collector type /collector name

Values for Parameters of data collector

Average BPC Action Response Time

Average Response Time executing BPC actions recorded in Transaction UJSTAT


RFC pull/Avg BPC Action Response Time

Metric Group Variant(Action=Total;Application ID=total;Appset=total;Last N minutes =Today

Number of changes in configuration files

The total number of changes in tables: UJA_Domain, UJA_SVR_DEFAULT , UJU_AUDSTING and UJA3_CLT_OPT

Changes in UJA_Domain

RFC_PULL /Config Store Change

GROUP_COMP_ID=*;GROUP_NAME=BPC;GROUP_SOURCE=ABAP;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=UJA_DOMAIN;STORE_TYPE=TABLE

Changes in UJA_SVR_DEFAULT

GROUP_COMP_ID=*;GROUP_NAME=BPC;GROUP_SOURCE=ABAP;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=UJA_SVR_DEFAULT;STORE_TYPE=TABLE

Changes in UJU_AUDSTING

GROUP_COMP_ID=*;GROUP_NAME=BPC;GROUP_SOURCE=ABAP;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=UJU_AUDSTING;STORE_TYPE=TABLE

Changes in UJA3_CLT_OPT

GROUP_COMP_ID=*;GROUP_NAME=BPC;GROUP_SOURCE=ABAP;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=UJA3_CLT_OPT;STORE_TYPE=TABLE



© 2013 SAP AG 21

For BPC 7.5 Netweaver Dot.Net server component, template name: SAP BPC 7.5 for Netweaver (Technical Instance).



SAP BPC Job service availability

Availability of Job service

SAP BPC Job service availability

Introscope EM(Push) /Generic host service state“IS_HOT_SERVICE_STATE

SERVICE_NAME= SAP BusinessObject Planning and Consolidation Job Service


The total number of changes in configuration files: outlooksoft.config, Osoftinstall.xml ,EAPSERVER,web.config and configuration.config

Changes in outlooksoft.config


GROUP_COMP_ID=*;GROUP_NAME=BPC_CONFIG;GROUP_SOURCE=FS;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=OutlookSoft.config;STORE_TYPE=XML

Changes in Osoftinstall.xml

GROUP_COMP_ID=*;GROUP_NAME=BPC_INSTALL;GROUP_SOURCE=FS;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=OSoftInstall.xml;STORE_TYPE=XML

Changes in EAPSERVER

GROUP_COMP_ID=*;GROUP_NAME=REGISTRY_CONFIG;GROUP_SOURCE=REG;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=EAPSERVER;STORE_TYPE=PROPERTY

Changes in web.config

GROUP_COMP_ID=*;GROUP_NAME=WEB_CONFIG;GROUP_SOURCE=FS;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=Web.config;STORE_TYPE=XML

Changes in Server configuratin.config

GROUP_COMP_ID=*;GROUP_NAME=WEB_CONFIG;GROUP_SOURCE=FS;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=ServerConfiguration.config;STORE_TYPE=XML

Errors in in BPC log file detected

Errors in BPCTRACE.*.log on .NET server


Diagnostic Agent(PUSH)/ BPC_ERRORS_FROM_LOG

Filename=\Q$INSTANCE_PATH$/Logging/Log/BPCLOG.*.log\E; Filename:\Q$INSTANCE_PATH$/Logging/Trace/BPCTRACE.*.log\E

Average data sending response time

Average Response Time of the web service that is called


Introscope EM(Push) / BPC Service Response Time

METRIC_PATH=Frontends\|Apps\|OSoft\|URLs\|/osoft/app/analysiscollectionservice/analysi



© 2013 SAP AG 22

when user send data to the server (analysiscollectionservice.asmx)

scollectionservice\.asmx:Average Response Time $ms$

Average data retrieval response time

Average Response Time of the web service that is called on the BPC Application Server when users retrieve data from server to BPC Client (queryengine.asmx)


METRIC_PATH=Frontends\|Apps\|OSoft\|URLs\|/osoft/app/osoftdataservice/queryengine\.asmx:Average Response Time $ms$

Average data manager response time

DataMgrService.GetDMServerInfo method within Data Manager in web process (in millisecond) This method will run the main job of executing a Data Manager package.


METRIC_PATH=Frontends\|Apps\|OSoft\|URLs\|/osoft/app/datamgrservice/datamgrservice\.asmx:Average Response Time $ms$

Average BPF response time

Average Response Time of the web service that is called on the BPC Application Server when users execute BPF (executionservice.asmx)


METRIC_PATH=Frontends\|Apps\|OSoft\|URLs\|/osoft/app/bpfservice/executionservice\.asmx:Average Response Time $ms$

Base Template Content for BPC 7.5 for Microsoft

For BPC 7.5 MS APP server component, template name: SAP BPC 7.5 for Microsoft (Technical Instance).



Number of changes in Configuration files

The total number of changes in configuration file: outlooksoft.config, Osoftinstall.xml and web.config

Changes in outloosoft.config







© 2013 SAP AG 23



Changes in web.config

GROUP_COMP_ID=*;GROUP_NAME=WEB_CONFIG;GROUP_SOURCE=FS;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME=Web.config;STORE_TYPE=XML


errors in BPCLOG.*.log Errors in BPC log file detected

Diagnostic Agent/ BPC_ERRORS_FROM_LOG

TRANSFORMERCLASS= com.sap.tc.logviewer.unification.impl.nw.NWLogReaderFactory; FILENAME= \Q$INSTANCE_PATH$Logging/Log/BPCLOG.*.log\E

Errors in BPC trance file detected

errors in BPCTRACE.*.log

Errors in BPC trance file detected

TRANSFORMERCLASS= com.sap.tc.logviewer.unification.impl.nw.NWLogReaderFactory; FILENAME= \Q$INSTANCE_PATH$Logging/Trace/BPCTRACE.*.log\E

Average BPC data sending response time

Average Response Time of the web service that is called when user send data to the server (analysiscollectionservice.asmx)

Average BPC data sending response time


METRIC_PATH=Frontends\|Apps\|OSoft\|URLs\|/osoft/app/analysiscollectionservice/analysiscollectionservice\.asmx:Average Response Time $ms$

Average BPC data retrieving response time


Average BPC data Retrieving response time


Average BPC data manager response time


Average BPC data manager response time




© 2013 SAP AG 24

Average BPC BPF response time


Average BPC BPF response time


SendGovernor availability

Availability of Send Governor service


Introscope EM(Push) /Generic host service state“IS_HOT_SERVICE_STATE

SERVICE_NAME=OSoftSendGovernor

For BPC 7.5 MS SSAS server component, template name: SAP BPC analysis service (Technical Instance).



MS SQL server analysis availability

Availability of SSAS MS SQL server analysis availability

Introscope EM(Push) /Generic host service service state “IS_HOT_SERVICE_STATE

SERVICE_NAME = MSOLAP\$SAPBPC

For BPC 7.5 MS SSIS server component, template name: SAP BPC integration service (Technical Instance).



MS SQL server integration availability

Availability of SSIS MS SQL server integration availability

Introscope EM(Push) /Generic host service state “IS_HOT_SERVICE_STATE

SERVICE_NAME = MsDtsServer100

For BPC 7.5 MS SSRS server component, template name: SAP BPC reporting service (Technical Instance).



MS SQL server reporting availability

Availability of SSRS MS SQL server reporting availability


SERVICE_NAME = ReportServer\$SAPBPC



© 2013 SAP AG 25

Base Template Content for BPC 10.0 for Netweaver

For BPC 10.0 NW ABAP server component, template name: SAP BPC ABAP 10.0 (Technical System).




Average Response Time executing BPC actions recorded in Transaction UJSTAT


RFC pull/Avg BPC Action Response Time

Metric Group Variant(Action=Total;Application ID=total;Appset=total;Last N minutes =Today


The total number of changes in tables: UJ0_PARAMG, UJ0_PARAMG_APP

Changes in UJ0_PARAMG


GROUP_COMP_ID=*;GROUP_NAME=BPC;GROUP_SOURCE=ABAP;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME= UJ0_PARAMG;STORE_TYPE=TABLE

Changes in UJ0_PARAMG_APP

GROUP_COMP_ID=*;GROUP_NAME=BPC;GROUP_SOURCE=ABAP;STORE_CATEGORY=CONFIG;STORE_FULLPATH=*;STORE_NAME= UJ0_PARAMG_APP ;STORE_TYPE=TABLE

Base Template Content for BPC 10.0 for Microsoft

For BPC 10.0 MS APP server component, template name: SAP BPC 10.0 for Microsoft (Technical Instance).




The total number of changes in configuration files: outlooksoft.config, Osoftinstall.xml ,EAPSERVER

Changes in outloosoft.config









© 2013 SAP AG 26

Errors in BPC log file detected

errors in BPCLOG.*.log Errors in BPC log file detected

Diagnostic Agent(PUSH)/ BPC_ERRORS_FROM_LOG

TRANSFORMERCLASS= com.sap.tc.logviewer.unification.impl.nw.NWLogReaderFactory; FILENAME= \Q$INSTANCE_PATH$Logging/Log/BPCLOG.*.log\E

Errors in BPC trace file detected

errors in BPCTRACE.*.log

Errors in BPC trace file detected

TRANSFORMERCLASS= com.sap.tc.logviewer.unification.impl.nw.NWLogReaderFactory; FILENAME= \Q$INSTANCE_PATH$Logging/Trace/BPCTRACE.*.log\E


Average Response Time of the web service that is called when user send data to the server (analysiscollectionservice.asmx)



METRIC_PATH=Frontends\|Apps\|OSoft\|URLs\|/osoft/app/analysiscollectionservice/analysiscollectionservice\.asmx:Average Response Time $ms$














Availability of send Governor service



SERVICE_NAME=OSoftSendGovernor



© 2013 SAP AG 27

For BPC 10.0 MS SSAS server component, template name: SAP BPC analysis service (Technical Instance).




Availability of SSAS service


Introscope EM(Push) /Generic host service service state “IS_HOT_SERVICE_STATE

SERVICE_NAME =SQL Server Analysis Services (SAPBPC)

For BPC 10.0 MS SSIS server component, template name: SAP BPC integration service (Technical Instance).




Availability of SSIS service



SERVICE_NAME = SQL Server Integration Services 10.0



© 2013 SAP AG 28

Features of System Monitoring

Overview of System Monitoring for BPC

To utilize System Monitoring of SAP BPC, the user must be familiar with the concept of SAP Solution Manager based System Monitoring.

System Monitoring is a centralized monitoring tool. Differed from Root Cause Analysis, System Monitoring puts its emphasis on the monitoring and alerting functionality. The main purpose of System Monitoring is to let the operations team, i.e. the Operations Control Center, be aware of the present status of the system and be warned when system components deteriorate.

System Monitoring monitors four aspects or categories of a system component: Availability, Performance, Configuration and Exception. Availability monitors whether the server or specific services on a server is available and accessible. Performance monitors the workload performance of specific processes or tasks on a server. Configuration monitors the number of changes in specific configuration files, registry etc. Exception monitors the number of error log entries written into specific log files or tables.

In the overview page, there is a central monitoring panel, which provides the overview of all the monitored system with status of Availability, Performance, Configuration, Exception, Alerting Number and Configuration Status listed.



© 2013 SAP AG 29

Navigation into a specific system provides a hierarchy view of the architecture of the system on the left side, and its metric status as well as detailed values for every metrics on the right side.

Switch the view category at top of the left panel to display the detailed information of specific aspects of components.



© 2013 SAP AG 30

Click the button located next to a metric to navigate to historical data for this metric. Modify the time scale to see the data for different time ranges.

Click the button in overview page or graphic view panel to navigate to the alert data view page. Display detailed alert information here.

SAP BPC specific alerts and metrics are displayed in the next example screenshots. The first shows the specific MAI content for App server of BPC for Microsoft. The second shows the MAI content for ABAP application server of BPC for Netweaver.



© 2013 SAP AG 32

Copyright

© Copyright 2013 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.

System Monitoring for SAP BPC · SAP Solution Manager 7.1 SP8 MAI System Monitoring for SAP...

Documents

Transcript of System Monitoring for SAP BPC · SAP Solution Manager 7.1 SP8 MAI System Monitoring for SAP...