Setup Guide- Central PI Monitoring in Technical Monitoring Work Center of SAP Solution Manager

Setup Guide Central Monitoring of SAP NetWeaver Process Integration 7.3 with SAP Solution Manager 7.1 Active Global Support February 2011

Agenda Overview Landscape Setup  Recommended Setup  SLD/LMDB Synchronization

Prerequisites  Managed System Configuration  System Monitoring Setup

PI Monitoring Setup  Scope Definition  PI Domain Overview  PI Component Availability/Selftest

 PI Channel Availability  PI Message Monitoring  Activation

© 2011 SAP AG. All rights reserved.

2

Overview Central PI Monitoring in SAP Solution Manager

Overview of Setup Procedure for Central PI Monitoring

PI Monitoring works in context of a PI Domain  A PI domain includes several technical systems that might be distributed in the landscape.  Each monitoring KPI is collected in context of a landscape component (e.g. Technical System or Technical Component).  SAP Solution Manager must know all this landscape information and establish connectivity to all involved systems and components.  The following Setup and Configuration Steps are necessary: – – – –

Landscape Setup (once/per PI SLD) Managed System Configuration (per Technical System) System Monitoring Setup (per Technical System) PI Monitoring Setup (per PI Domain)

© 2011 SAP AG. All rights reserved.

4

Landscape Setup Central PI Monitoring in SAP Solution Manager

Recommended Landscape Setup

Synchronize the content PI SLD into LMDB of SAP Solution Manager  Although you can synchronize several SLDs into one LMDB, we recommend a central SLD to collect all PI SLDs before synchronizing it into LMDB of SAP Solution Manager  If the unidirectional content synch is established, the SLD bridging is not (longer) required.

Central SLD

Integration Server

(Release ≥ 7.10)

with PI SLD Unidirectional Content Synch PI Domain Adapter Engines and Business Systems

SLD Bridging

LMDB inside SAP Solution Manager PI Domain

Adapter Engines and Business Systems

© 2011 SAP AG. All rights reserved.

6

Unidirectional Content Synch

To forward the entire SLD Content of PI SLD into central SLD of SAP Solution Manager (especially the content about PI Domain and all its PI Components), an unidirectional content synch needs to be setup. Central SLD of landscape (must be on Release 7.10 or higher to be able to receive Content Synch)  Logon to SLD and go to Administration  Synchronization  Use button “Add…” to add the PI SLD  Just follow the guided procedure to choose the source SLD and the Namespace for synchronization  Do not set the flag “Bi-Directional” on the first step!  You can trigger a “Full Sync.” or check the status of the incremental synch.

© 2011 SAP AG. All rights reserved.

7

SLD Bridging not required

Usually Technical System information are transferred to central SLD via SLD Bridging mechanism. This is NOT required any more for PI SLDs, since we have established the content synch. On PI SLD    

© 2011 SAP AG. All rights reserved.

Logon to SLD Administration Data Supplier Delete the central SLD of SAP Solution Manager from section “Update Other SLDs”

8

LMDB Content Synch

LMDB Content Synch between central SLD and LMDB is setup in transaction SOLMAN_SETUP  In Step 6.5 “Set Up LMDB” of System Preparation Workcenter you can check and/or add Subscriptions for Remote Content Changes

 Using button “Details” you can check e.g. the last polling time or the number of pending changes

© 2011 SAP AG. All rights reserved.

9

Prerequisites Managed System Configuration

Overview of Managed System Configuration Managed System Configuration for all managed systems inside SAP Solution Manager is a prerequisite for all monitoring used cases, also for PI Monitoring. All configuration steps needs to be processed for the involved technical systems*. Open Managed System Configuration Workcenter (transaction SOLMAN_SETUP) and choose a Technical System or a Technical Scenario and click Configure System/Configure Scenario. The following steps are especially important:      

Step “Select Product” Step “Connect Managed System” (ABAP only) Step “Assign Diagnostic Agent” Step “Enter System Parameters” Step “Create Users” Step “Configure Automatically”

* For double stack systems, e.g. Integration Server, the LMDB will automatically create Technical Scenarios of type “Double Stack”. Use those scenarios for configuration of double stacks © 2011 SAP AG. All rights reserved.

11

Configuration Step “Select Product”

Assign one of the following products*:    

SAP NETWEAVER 7.1: Process Integration SAP EHP1 FOR SAP NW PI 7.1: Process Integration SAP NETWEAVER 7.3: Process Integration SAP EhP1 FOR SAP NETWEAVER 7.3: Process Integration

* Applicable Technical Systems running followingf PI Components: -

Adapter Engine

-

Integration Engine

-

Integration Directory

-

Enterprise Services Repository

© 2011 SAP AG. All rights reserved.

12

Configuration Step “Connect Managed System” 1/2 For Managed Systems of type ABAP, the RFC destinations are created in Step “Connect Managed System”:  Create following RFC connections into all required clients: – RFC Read Access – Trusted System RFC – other RFC Connection types may also be required by other used cases

© 2011 SAP AG. All rights reserved.

13

Configuration Step “Connect Managed System” 2/2 Creation of RFC Connection to Managed System

© 2011 SAP AG. All rights reserved.

14

Configuration Step “Assign Diagnostic Agent”

For each instance of PI system a Diagnostic Agent needs to be assigned.  Usually the proposed values can be accepted by pressing “Assign”.  If no agent is proposed, choose tab “SLD Agent Candidates” and pick the agent on the respective instances host. – It is required to connect all agents to the central SLD. From there you can choose agents and assign it to the local SAP Solution Manager to use it for one of the managed systems.

© 2011 SAP AG. All rights reserved.

15

Configuration Step “Enter System Parameters” Enter the following data for the managed system

Enter the http port of Java Central Instace here Connection Parameter for ABAP System (in case of Double Stack)

Connection Parameter for Java System

For Decentral Adapter Engines (Technical Systems of type Java), it is very comon in PI to use the ABAP Stack of Integration Server for Central User Administration. You can enter the required data by setting this flag. © 2011 SAP AG. All rights reserved.

16

Configuration Step “Create Users”

The following Users (Dialog/System user) need to be created in the managed system. The adequate roles and authorizations need to be assigned. All this can be done in the configuration step “Create Users”.

In case of Technical System Type ABAP

In case of Technical System Type Java

© 2011 SAP AG. All rights reserved.

17

Configuration Step “Configure Automatically” Single Sign On Setup:  This activity enables central manage functions in PI monitors.  Certificates are exchanged with Managed System and SAP Solution Manager  Assertion Ticket Login Module is assigned to several Java Applications.

WEB Service Logical Port Creation:  Logical Ports for communication to the Java Stack of Managed System are created in SAP Solution Manager System (Prerequisite: User with ID SM_COLL_xxx must exist in Managed System)

Both steps have extensive logging. Please execute all steps and make sure, the status for execution is green/successful. © 2011 SAP AG. All rights reserved.

18

Prerequisites System Monitoring Setup

System Monitoring Setup Setup of System Monitoring for all systems in the PI Domain is a requirement for PI Monitoring Setup.  Choose relevant systems  Choose Monitoring Templates  Assign and Activate

© 2011 SAP AG. All rights reserved.

20

PI Monitoring Setup Central PI Monitoring in SAP Solution Manager

Overview of PI Monitoring Setup

The PI domain with all its PI components must be know to SAP Solution Manager to be able to take advantage out of central PI Monitoring.  PI domain is modeled as Technical Scenario based on LMDB data of PI domains.  Various PI domains can be created.

For each PI domain you can customize the monitoring objects (metrics).      

PI Domain Overview Load Meta data Component Availability and Self test Channel Availability Message Monitor Activate

© 2011 SAP AG. All rights reserved.

22

Setup Step “Define Scope”

Choose the PI Domain to be used for PI Monitoring setup    

Pick relevant PI domain from list or create new PI domain (based on LMDB data) You can also maintain existing PI domains (based on LMDB data) PI Domains listed here are taken from LMDB (onlythose, with PI releases >7.11 SP06) Start setup procedure for PI Monitoring

© 2011 SAP AG. All rights reserved.

23

Setup Step “Create/Maintain PI Domain” Define or maintain a Technical Scenario  Existing Technical Scenario of type PI_DOMAIN is prerequisite for all monitoring used cases  Technical scenario is based on LMDB Data for PI domain (synchronized from PI SLD)  You can exclude Technical Systems from Technical Scenario List of Technical Systems included in PI (in case those systems should not be monitored) Pick a PI Domain from LMDB (with PI Release as of 7.11 SP06)

1

Domain (Mouse over displais the role(s) of Technicals System in PI domain)

3

You can exclude systems from Technical Scenario

Enter a description

2

4

Pick the PI SLD related to this PI domain from LMDB

Overview of all input Press Button Setup to create the Technical scenariop scenario

© 2011 SAP AG. All rights reserved.

24

Setup Step “PI Domain Overview”

This screen provides an overview of all technical systems involved in the PI domain and its setup status.  Choose a technical system and jump into Managed System Configuration of System Monitoring Setup (if necessary) System Monitoring Setup

© 2011 SAP AG. All rights reserved.

25

Setup Step “Load Meta-Data” This automatic step performs a number of automatic functions  Initial Setup Step and after major changes in the PI domain

The following functions are executed:  Check of PI component roles in PI domain  BI master data texts are loaded for the following BI characteristics: – – – –

PI component name and role PI status group PI status and relation to PI status group (attributes) PI status details

 Loading of Channel Attributes – In the Channel Monitor additional attributes of channels (like channel type), these attributes are loaded into the SAP Solution Manager here. – A collector is scheduled to update the data daily.

© 2011 SAP AG. All rights reserved.

26

Setup Step “PI Component Availability” You can display and save standard SAP Settings or customize the settings (mark the component and choose the button Change SAP settings)

You can change the setting:  Data collection Period (min).  Active PI Component for alerting (tab Alert Details)  The Incident Tickets tab defines default support components for further issue escalation.  The Notifications tab defines notification mechanisms that will be triggered upon alert generation.

Save Changes  Note: Availability monitoring is not available for the PI components ABAP Business System and Business Process Engine. © 2011 SAP AG. All rights reserved.

27

Setup Step “PI Component Selftest” Component Self-Test settings are very similar to Component Availability Settings.  Use SAP Settings or adjust the standard settings  Save the settings after changing  The settings are activated in the last step (Complete Set Up).

 Note: Self-test status monitoring for the component is not available for the PI components ABAP Business System and System Landscape Directory. © 2011 SAP AG. All rights reserved.

28

Setup Step “Channel Availability” Channel status information is available for all adapter engines in the PI domain (central and de-central adapter engines).  The overall status calculated from the channel and activation states of a channel.  You can specify the following settings for each adapter engine individually in the tab Data Collection below: – CHANNELONLYERR If set, channels in status SUCCESSFUL will not be collected – SHORTLOGCOLLECT If set, the short log data of the channel is collected – SHORTLOGONLYERR If set, short log data for channels in status SUCCESSFUL is not collected (this setting is relevant if CHANNELONLYERR is not set) – SHORTLOGSIZE The number of characters to be collected for short log, per channel and server node – SHORTLOGTRIM - If set, stack traces will not be put in the short log, to keep it readable © 2011 SAP AG. All rights reserved.

29

Setup Step “Message Flow Monitor” Activate the collection of message processing status information The following PI Components are involved in Message Processing     

Central Integration Engine Central Adapter Engine Adapter Engine ABAP Proxy Java Proxy To activate message status collection for any component, activate the indicator in the Collect column.

General setting for all PI components  Specify the Data Collection Period and the Time Ranges to be Collected (as message processing statistics are pre-aggregated for different time ranges already in the PI Component)

You cannot save this customizing. Choose the button Activate Monitoring if the current settings are to be used for the data collection. © 2011 SAP AG. All rights reserved.

30

Configuration Step “Activation”

Complete Set Up  This step will activate all the monitoring and alerting settings made in the previous setup steps, except Message Flow Monitor, which is activated independently.

 Extensive logging is available for this step. You can check in the log the status for all activation activities  You can also jump into Alert Directory Browser and check the settings and configurations, that are saved in the Alert Directory for this specific PI Domain and its PI components

© 2011 SAP AG. All rights reserved.

31

Finished!

The setup for PI Monitoring is finished and the Technical Monitoring Workcenter is ready to display the PI Monitors…

© 2011 SAP AG. All rights reserved.

32

Thank You!

Contact information: Active Global Support SAP AG

© 2011 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.

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 Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase 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. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. 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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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.

© 2011 SAP AG. All rights reserved.

34