sap #bobj #bi 4.1 upgrade webcast series 12: monitoring

© 2014 SAP AG or an SAP affiliate company. All rights reserved. 1 Internal

SAP BusinessObjects BI 4.1 Upgrade

Webinar Series

BI 4.1 Monitoring

Presenter: Toby Johnston

SAP Active Global Support

Brought to you by the Customer Experience Group


We bring to you all that you need to

successfully upgrade to the SAP

BusinessObjects BI Platform 4.1.

You can find a BI 4.1 Upgrade

Overview page on SCN at:

http://scn.sap.com/docs/DOC-56525

Webinars also complement these

published resources:


SAP BusinessObjects BI Platform 4.1 Upgrade

Enablement







Key Components of the BI Platform Monitoring Application


Key Components: Server Metrics

Server Metrics


Key Components: Server Metrics

Server Metrics

What servers should I monitor? Refer to product tutorials for guidance:







Key Components: Derived Metrics

Derived Metrics


Key Components: Metrics

Host Metrics


Key Components: SAP Host Agent

Allows SAP processes to be stopped / started remotely

Enables monitoring of operating systems via SAP OsCol

Included with the Solution Manager Diagnostic Agent

SAP BI Platform Support Tool will also leverage the SAP Host Agent

Must be installed on each node in the landscape

Download version 7.20 on the Service Marketplace

http://wiki.scn.sap.com/wiki/display/BOBJ/How+to+install+the+SAP+Host+Agent+for+BI+Platform+Host+Monitoring

How to install the SAP Host Agent for BI Platform Host Monitoring





Topology Metrics


Key Components: Health State Metric

Health State metric is determined by that server’s watch status

Different states

Green = Server OK

Amber = Caution

Red = Danger

Disabled = Watch not enabled

Failed = Error in formula or monitoring service disabled

In CMC, Server’s Page has “Health” column to show Server’s Health

Server Health is shown for

Default Servers

New Server instances

Nodes and Service Categories

Click to see

watch details


Key Components: Server Health Watch

State Value

Green 2

Amber 1

Red 0

State Value

Green 1

Red 0

Two stage watch returns:

BIPW08R2.APS$'Server Running

State'==0 || BIPW08R2.APS$'Server

Running State'==5

Three stage watch returns:

Danger Rule is false

3 state watch returns 2

which evaluates to GREEN


Key Components: Server Running State Metric

State Value

Stopped 0

Starting 1

Initializing 2

Running 3

Stopping 4

Failed 5

Running With Errors 6

Running With Warnings 7


Key Components: Configuring Server Watch Example

State Value

Stopped 0

Starting 1

Initializing 2

Running 3

Stopping 4

Failed 5

Running With Errors 6

Running With Warnings 7

Two stage watch

Three stage watch

Caution Rule

BIPW08R2.APS$'Server Running State'==1 ||




BIPW08R2.APS$'Server Running State'==7

Danger Rule BIPW08R2.APS$'Server Running State'==0 ||

BIPW08R2.APS$'Server Running State'==5

Danger Rule BIPW08R2.APS$'Server Running State‘!=3

Server Running State


Health State Watch Hierarchy

Enterprise Nodes Watch

SIA Node 1 Health State SIA Node 2 Health State

CMS 1 Health State

APS 1 Health State

AJS 1 Health State

CMS 2 Health State

APS 2 Health State

AJS 2 Health State

Service Categories Watch

Consolidated Health Watch

Analysis Services Health

Dashboard Service Health

Core Services Health

Explorer Services Health

Webi Services Health

Connectivity Services Health

Crystal Reports Service Health

Data Federation Service Health

Promotion Management Health

OK

Failed





CMS 1 Health State

APS 1 Health State

AJS 1 Health State

CMS 2 Health State

APS 2 Health State

AJS 2 Health State












OK

Failed


Key Components: Enhanced Topology GUI


Key Components: Watches


Key Components: Alerts


Key Components: Probes



• Health Probe

Generates metrics of data types such as integer, Boolean, or string. An example of a

health probe is the default CMS Logon/Logoff probe which checks that a user may

successfully logon/logoff the Central Management Server

• Diagnostic Probe

Generates reports containing current system information. An example of a diagnostic

probes is the default Stop/Start server probe. This probe checks all the servers, records

the state of each server, restarts the servers and collects information about servers again

• Hybrid Probe

Functions as both a health probe and a diagnostic probe


Key Components: Copying a probe and why?

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

How to create a copy of a default probe

Apache Tomcat #1

Apache Tomcat #2

BI Launchpad Probe 1

BI Launchpad Probe 2

http://server1:8080/BOE/BI

http://server2:8080/BOE/BI


Key Components: BI Launchpad SSL Probe

http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=388793398

Guide for configuring BI Launchpad Probe for SSL



31 © 2014 SAP AG or an SAP affiliate company. All rights reserved.

http://scn.sap.com/docs/DOC-39449 Developing and deploying a custom Java probe in BI Platform 4.0


Key Components: Custom Probe

String hostname = (String) inputParams.get("hostname");

String portnum = (String) inputParams.get("portnum");


Key Components: Custom Probe


Key Components: Monitoring Stack

Alerts

Watches

Metrics Probes

Best Practices and Getting Started


Monitoring Strategy

Give it the necessary resources

(KISS) Keep it simple

and significant

Focus on mission critical

components

Known vulnerabilities


Be Patient

Changes in watch states take 60

seconds to update by default so be

patient when making changes to metric

definitions


Trending Database


Trending Database

http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp4_bip_admin_en.pdf

Configuring the Auditing Connection for Trend Database

Monitoring uses the Connection Server libraries to connect to the Auditing Database

The Monitoring application refers to the auditing connection name, and uses JDBC if

<hostName>.<Portnum>.<dbName> is used, or ODBC otherwise

You must configure the corresponding SBO file on each node in case of failover

Refer to the newest Administrator guide for up to date configuration details

http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp4_bip_admin_en.pdf


Trending Database

CSV


Getting started checklist

Make sure you have applied SP4 + Patch1 or higher (contains fixes for Host metrics)

Enable Monitoring Application (CMC --> Monitoring)

Reconfigure APS (remove Monitoring Service from existing APS servers)

Add new Monitoring Service on each SIA node with 2gb RAM

Fix broken server and health watches

Deploy custom probes (optional)

Enable JMX RMI protocol (optional)

Install Host Agent on both nodes and configure Host Monitoring

Configure Trend Database to use Auditing Datasource

Disable Alert Reminders under CMC Application settings by changing 2 to 0

Enable Email Alerts and configure Adaptive Job Server for SMTP

Schedule Recurring Probes and create watches


Troubleshooting

Enable TraceLog Service for “active” monitoring service


SAP BusinessObjects BI 4.1 Upgrade

Webinar Series

BI 4.1 Monitoring

Q & A

Brought to you by the Customer Experience Group


© 2014 SAP AG or an SAP affiliate company. 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 or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG (or an SAP affiliate

company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP AG or its

affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP AG or SAP affiliate company 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.

In particular, SAP AG or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or

release any functionality mentioned therein. This document, or any related presentation, and SAP AG’s or its affiliated companies’ strategy and possible future

developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP AG or its affiliated companies at any time for

any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-

looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place

undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx



sap #bobj #bi 4.1 upgrade webcast series 12: monitoring

Technology