57
Venky Varadadesigan SAP Labs Introducing SAP NetWeaver Administrator (NWA) — The New Tool to Administer and Monitor SAP Systems

Introducing SAP NetWeaver Administrator (NWA) — …...System SAP NetWeaver Administrator SLD Solution Manager ABAP System Java System Non-SAP Component SAP NW ’04 >= SP12 or SAP

  • Upload
    others

  • View
    45

  • Download
    1

Embed Size (px)

Citation preview

Venky VaradadesiganSAP Labs

Introducing SAP NetWeaver Administrator (NWA) —The New Tool to Administer and Monitor SAP Systems

© SAP AG 2006, 2

Learning Objectives

As a result of this session, you will be able to:Explain the functionality of SAP NetWeaver AdministratorWork with the available plug-insMonitor the performance of your system landscape

Setting Up NWA Infrastructure

Summary

Motivation and Overview

NWA Details

© SAP AG 2006, 4

Positioning: IT Practices and IT Scenarios

SAP NetWeaver®

Com

posi

te A

pplic

atio

n Fr

amew

ork

PEOPLE INTEGRATION

Multi-Channel Access

Portal Collaboration

INFORMATION INTEGRATION

Bus. Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATIONIntegration Broker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAP

Lifecycle Mgm

t

IT practices “slice” SAP NetWeaver to directly address key issues ... and help enterprises find the right starting point

Use

r Pro

duct

ivity

Ena

blem

ent

Dat

a U

nific

atio

n

Bus

ines

s In

form

atio

n M

anag

emen

t

Bus

ines

s Ev

ent M

anag

emen

t

End-

to-E

nd P

roce

ss In

tegr

atio

n

Cus

tom

Dev

elop

men

t

Uni

fied

Life

cycl

e M

anag

emen

t

App

licat

ion

Gov

erna

nce

and

Secu

rity

Con

solid

atio

n

Ente

rpris

e Se

rvic

e A

rchi

tect

ure

Different capabilities are used jointly in each “slice”

© SAP AG 2006, 5

Positioning: SAP NetWeaver Technology Map

User Productivity Enablement

Running an Enterprise Portal

Enabling User Collboration

Business Task Management

Mobilizing Business Processes

Enterprise Knowledge Management

Data Unification Master-Data Harmonization Master-Data Consolidation Central Master-Data Management Enterprise Data Warehousing

Business Information Management

Enterprise Reporting, Query, and Analysis

Business Planning and Analytical Services Enterprise Data Warehousing

Business Event Management Business Event Resolution Business Task Management

End-to-End Process Integration

Enabling Application-to-Application Processes

Enabling Business-to-Business Processes

Business Process Management

Enabling Platform Interoperability

Business Task Management

Custom Development Developing, Configuring, and Adapting Applications Enabling Platform Interoperability

Unified Lifecycle Management Software Life-Cycle Management SAP NetWeaver Operations

Application Governance & Security Authentication and Single Sign-On Integrated User and Access Management

Consolidation Enabling Platform Interoperability SAP NetWeaver Operations Master-Data Consolidation Enterprise Knowledge

Management

Enterprise Service Architecture – Design & Deployment

Enabling Enterprise Services

IT Practices IT Scenarios

© SAP AG 2006, 6

Motivation: Why Do We Need SAP NetWeaver Administrator?

Multiple J2EE and ABAP systems to monitor

Need to log into different “Visual Admin” to manage various J2EE systems

No centralized tool available

No Web-based zero footprint tool available to administer the entire landscape

© SAP AG 2006, 7

SAP NetWeaver Administrator is the new central administration and monitoring tool for your SAP NetWeaver system landscape

SAP NetWeaver Administrator is a Java application

Availability: It is part of the shipment of SAP NetWeaver ’04 SP 12

Central Monitoring andAdministration System

SAP NetWeaver Administrator (NWA)

Java

ABAP

SAP NetWeaver Administrator

© SAP AG 2006, 8

SAP NetWeaver Administrator at a Glance

Target groupCustomer administrators and operators (daily use)

MonitoringLandscape availability viewDisplay of CCMS RZ20 monitorsPerformance reportsCentral log viewer

AdministrationStart and stop of Java applicationsCentral configuration

Platform focusFirst version is focused on JavaNext versions will cover the complete SAP NetWeaver

© SAP AG 2006, 9

SAP NetWeaver Administrator: Key Features

CentralAdministration, problem detection, and problem analysisin ONE tool

UsableTask-oriented navigationScreens follow newest SAP UI standards

ExtensibleSeamless navigation to other SAP NetWeaver administration functionality (UME, SLD, AC, etc.)

RemoteWeb Dynpro-basedRuns in a browser (no client-side installation necessary)

Note: There are a number of admin and monitoring tools for SAP NetWeaver. NWA is positioned to unify these functionalities under one roof.

© SAP AG 2006, 10

Role of Solution Manager in Lifecycle Management

Application Management SAP Solution Manager

Enables end-to-end application managementIs an application based on SAP NetWeaverIs delivered as a separate product

NetWeaver Lifecycle ManagementSAP NetWeaver Administrator and Software Logistics

Daily system administration Landscape monitoring and configurationPart of SAP NetWeaverInitial setupSoftware Maintenance Management

Planning Status

Note: NWA is not positioned to replace Solution Manager nor Solution Manager Diagnostics

© SAP AG 2006, 11

Solution Manager Diagnostics vs. SAP NetWeaver Administrator

Different Roles

Web Dynpro application for administration, monitoring, and

configuration

Safe: No changes allowed

Remotely accessibleExpert functionality

Focus

Proactive on a daily basis

Reactive in case of a problem

Usage

Administrator RoleCustomer

administrators and operators

Support RoleSAP Active Global

SupportCustomer CC

Role

SAP NetWeaver Administrator

Solution Manager Diagnostics

Setting Up NWA Infrastructure

Summary

Motivation and Overview

NWA Details

© SAP AG 2006, 13

Monitoring and Management

NWA: Monitoring and Management – Big Picture

Monitoring and Management Connectivity Layer(JMX, Agents, etc.)

Monitoring and Management Connectivity Layer(JMX, Agents, etc.)

Productive Landscape

Central Monitoringand Administration

System

SAP NetWeaverAdministrator

SLD Solution Manager

ABAP System

JavaSystem

Non-SAPComponent

SAP NW ’04 >= SP12 or SAP NW 2004s ABAP and Java

All systems are connected to the System Landscape Directory

All systems are monitored by CCMSPING for availability monitoring

All systems are connected to the

central monitoring system via SAPCCM4x or SAPCCMSR agents

for online and alert monitoring

© SAP AG 2006, 14

NWA: The Entry Page

The NWA can be used as an administration tool for the whole SAP NetWeaver system landscape, as well as for local system administration

For the central use, a setup has to be performed, including configuration of the System Landscape Directory, central monitoring, and connections from the remote systems to the central monitoring system and NWA

© SAP AG 2006, 15

NWA – What Is Inside Administration?

Administration

Monitoring

© SAP AG 2006, 16

Administration: System Selection

Defining Landscape Subsets

Define Subsets in the SLDPrerequisite: You have a user assigned to the LcrInstanceWriterLD role (contained in role Administrator)

Define Selections in the NWAIn the NWA, you can define system sets that are saved for your user under a name you specify. Click on “Define System Selection”All Technical Systems. Select systems holding the Strg. button and enter a name for your selection.

© SAP AG 2006, 17

Administration: Manage the Selected Systems

Choose System Management →Administration.

From the detailed navigation on the left, select Systems. A list of the instances you selected when defining your system selection will appear in a tree view.

Expand the tree of a selected system and choose the blue square next to the instance name to administer this instance.

When an instance is selected, the Start, Stop, and Restart options on the top are activated. Use them to start, stop, or restart the whole instance at once. A Details pane will also appear below the SAP Systems pane, where you can see the details of the selected instance, and manage the separate J2EE processes and services.

© SAP AG 2006, 18

Administration: Manage Applications

With the NWA you can start and stop applications of the selectedJava systems as well as display their status, their modules, resources, and references

An advanced search option is also available, which helps you to apply more sophisticated filtering criteria when searching for deployed applications

© SAP AG 2006, 19

Administration: User Management

User Management Engine (UME) is a plug-in within the SAP NetWeaver Administrator

For use of the NWA, the user can be assigned four different roles:SAPJAVA_NWADMIN_CENTRALSAPJAVA_NWADMIN_CENTRAL_READONLYSAPJAVA_NWADMIN_LOCALSAPJAVA_NWADMIN_LOCAL_READONLY

TIP: It is possible to slice and dice these four standard roles to create custom roles. (For example: New role only with Local Logs and Trace monitoring capability)

© SAP AG 2006, 20

NWA — What Is Inside Monitoring?

Administration

Monitoring

© SAP AG 2006, 21

Monitoring: Availability Check

ABAP

Java

Monitoring Infrastructure

NetWeaverAdministrator

ABAP System

JavaSystem

CCMSPINGMessage

Server

MessageServer

All systems that are monitored in the Central Monitoring System (CEN) can be observed by an availability check. This check is realized by the agent CCMSPING, which calls the message servers of the monitored systems and sends availability data to the CEN every minute.

In the NWA, a dashboard with the overall availability data is displayed

Central Monitoring System

© SAP AG 2006, 22

Monitoring: Availability Details

Status of the monitored systems with the number of instances

Information of the system instances, including status, instance type, and availability in percent

For the ABAP systems, an additional logon check is done via RFC

The details show the number of users logged on, the average dialog response time, and the standard response time

Availability Check is not activated for

this system

© SAP AG 2006, 23

Monitoring: Central Reports (RZ20 Web View)

Select the monitors to be displayed

Monitoring tree with the values and alerts for the monitors

Current monitor

Information about the current monitor

With the “Mark” option, you can select and combine monitors from different Setsand Views in one screen. This is a temporary combination. For permanent view customizing, use the CCMS alert monitor functionality.

© SAP AG 2006, 24

Monitoring: Central Reports – Details

Wed Aug 03 14:15:01 CEST 2005

You can display all alerts of a monitor element that are not yet closed. To delete an alert after having fixed the problem, click “Complete Alerts.”

Like in CCMS, you can display Current Data, Alerts, Customizing Data, Methods, and the Thresholds for the monitor elements

© SAP AG 2006, 25

Monitoring: Central Reports – Analyze Option

Wed Aug 03 14:15:01 CEST 2005

… call the remote ABAP system via ITS and deal with the ABAP system analysis as usual

To start ABAP analysis methods …

© SAP AG 2006, 26

Monitoring: Java Performance Reports

Performance reports for Java systems are created with the use of the (JMX) status monitoring data and the Java Application Response Time Measurement (JARM) data

The reports help to do capacity planning, to check the resource consumption over time, and to scrutinize the applications’ activity

© SAP AG 2006, 27

Monitoring: Create New Java System Reports

You can define Java System Reports and charts out of all available counters, such as performance counters from the monitoring tree, JARM requests, and application components

© SAP AG 2006, 28

Monitoring: Logs and Traces

Viewing the Log Files can be done in a generic view in the Monitoring Work Center, e.g., the Alert View gives a good overview of problems that have occurred

Filtering functionality helps you to easily find the log entries in question

© SAP AG 2006, 29

Monitoring: Related Area Navigation

With the related tasks navigation,you can open other areas with pre-set filters, e.g., open the log viewer with filter for the selected application

Setting Up NWA Infrastructure

Summary

NWA Details

Motivation and Overview

© SAP AG 2006, 31

Setting Up NWA Infrastructure

The following steps have to be performed:

1. Configure and Activate the System Landscape Directory (SLD)1a. Activate the Object Server1b. Load the CIM model1c. Start the Data Supplier Bridge1d. Set up connections to SLD

2. Adjust the Central Monitoring System (CEN)2a. For every instance of a J2EE Engine: Register a CCMS Agent SAPCCMSR2b. For every ABAP instance: Register a CCMS Agent SAPCCM4X2c. Register CCMSPING and assign the monitored systems

3. Setup of the NWA connections3a. CIM Client generation setting3b. JCo RFC connection setting3c. JMX monitored system account details

© SAP AG 2006, 32

1. Setting Up an SLD for NWA – Big Picture

© SAP AG 2006, 33

1a. Activate the Object Server

© SAP AG 2006, 34

1b. Import the CIM Model

To import the CIM model, choose Content -> Import and open the file …/<SID>/SYS/GLOBAL/SLD/Model/CR_Content.zip

Caution: The import may run for more than one hour!

© SAP AG 2006, 35

1c. Activate the Data Supplier Bridge

Enter the information for the gateway over which the monitored systems report data to the SLD

(NW04: Start the Data Supplier Bridge)

NW2004s

NW04 SP12

© SAP AG 2006, 36

1d. Create the SLD Customizing Connection from CEN

Central Monitoring and Admin System

ABAP

Java

MonitoringInfrastructure

NetWeaverAdministrator

SLD SystemJ2EE Engine

SLDData

SupplierBridge

J2EEEngine

Gatew

ay

SA

PS

LDA

PI

SLDAPICUST

RFC ConnectionSLD_<host>_<SID>

http

Over this connection, monitored systems and their association to the CEN get registered at the SLD

lcrabapapi

© SAP AG 2006, 37

1d. SLD Bridge Connection Data in All Monitored Systems

ABAP Transaction: RZ70

The data transfer from all ABAP and Java systems to the SLD goes over the Data Supplier Bridge

(Server node → Services → SLD Data Supplier → HTTP Settings)

JAVA Local Visual Admin Tool

© SAP AG 2006, 38

Setting Up NWA Infrastructure

The following steps have to be performed:

1. Configure and Activate the System Landscape Directory (SLD)1a. Activate the Object Server1b. Load the CIM model1c. Start the Data Supplier Bridge1d. Set up connections to SLD

2. Adjust the Central Monitoring System (CEN)2a. For every instance of a J2EE Engine: Register a CCMS Agent SAPCCMSR2b. For every ABAP instance: Register a CCMS Agent SAPCCM4X2c. Register CCMSPING and assign the monitored systems

3. Setup of the NWA connections3a. CIM Client generation setting3b. JCo RFC connection setting3c. JMX monitored system account details

© SAP AG 2006, 39

2a. and 2b. Register SAPCCMSR and SAPCCM4X Agents

© SAP AG 2006, 40

2c. Setting Up CCMSPING

© SAP AG 2006, 41

2c. Add System to Availability Check

The central monitoring system gets automatically checked for registered CCMSPING agents. You can select one of the running CCMSPING destinations and enable the availability monitoring.

© SAP AG 2006, 42

Setting Up NWA Infrastructure

The following steps have to be performed:

1. Configure and Activate the System Landscape Directory (SLD)1a. Activate the Object Server1b. Load the CIM model1c. Start the Data Supplier Bridge1d. Set up connections to SLD

2. Adjust the Central Monitoring System (CEN)2a. For every instance of a J2EE Engine: Register a CCMS Agent SAPCCMSR2b. For every ABAP instance: Register a CCMS Agent SAPCCM4X2c. Register CCMSPING and assign the monitored systems

3. Setup of the NWA connections3a. CIM Client generation setting3b. JCo RFC connection setting3c. JMX monitored system account details

© SAP AG 2006, 43

3. Setup of the Connections for NWA

For central monitoring and administration with the NWA, you have to go through some steps in the Visual Administrator of the Central Monitoring System

You need a direct connection to SLD with the corresponding permissions (login) (“CIM Client generation settings”) A connection from the Java part of the central system to the ABAP part has to be established. This is a JCo RFC connection with the naming convention SAP.CCMS.CEN.<SID>. Without this connection, the monitors of CEN are not displayed in the NWA.You may store the login data to all monitored Java systems in the Java part of the central system. If you don’t do this, you have to enter user/password each time you want to display data from the connected systems.

© SAP AG 2006, 44

3a. This Error Message for the SLD Server …

… comes up if the CIM Client Generation Settings are not entered in the Visual Administrator of the NWA system

The CIM Client is needed by the NWA to access the SLD

© SAP AG 2006, 45

3a. CIM Client for Data Transfer from SLD to NWA

sap.com/tc~lm~webadmin~mainframe~wd/webdynpro/public/lib/app.jarsap.com/tc~lm~webadmin~sld~wd/webdynpro/public/lib/app.jar

In the Visual Administrator of the NWA, go to service SLD Data Supplier, and open the CIM Client Generation Settings tab. Select the named jars and enter the connection parameters for the SLD.

© SAP AG 2006, 46

3b. This Error Message for the Central Monitoring …

An error message comes up if the rfc destination SAP.CCMS.CEN.<SID> has not been set up

© SAP AG 2006, 47

3b. Create JCo RFC Destination in the NWA System

In the JCo RFC Provider Service of the NWA system, create the rfc destination SAP.CCMS.CEN.<SID> pointing to the CEN gateway host

© SAP AG 2006, 48

3c. This Error Message for the JMX Connection …

This error message comes up if the login to the monitored system is not stored in the NWA system

© SAP AG 2006, 49

3c. Enter Connecting Data for Administered Systems

The name is: sap.com/tc~je~jmx~wsconnector~sp/<SID>/<host>The URL is: http://<host>:<port>/WSConnector/Config1?style=document

In the Central Monitoring System, the http connections and authentication parameters for all administered Java systems can be stored

© SAP AG 2006, 50

Ready!

Now the NetWeaver Administrator is set up for system landscape-wide monitoring and administration

You can start it with: http://<host>:<port?/nwa

Log in with a user with central administration permissions to have the whole functionality

Setting Up NWA Infrastructure

Summary

NWA Details

Motivation and Overview

© SAP AG 2006, 52

Resources

Service MarketplaceSAP Service Marketplace: http://service.sap.com/

- QuickLink/NWA-> Media Library -> Films & Tutors

- eLearning: Setting up NWA-> Media Library -> Presentations

- QuickLink/javamonitoring- QuickLink/monitoring

SDNSAP Developers Network: http://sdn.sap.com/

- eLearning – LCM256 NWA

Help portalSAP Help portal: http://help.sap.com/

- Documentation -> SAP NetWeaver -> SAP NetWeaver 2004s -> Tecnology Consultants Guide -> SAP NetWeaver Operations

© SAP AG 2006, 53

For more information: Access the SAP Developer Network – www.sdn.sap.com

The central hub for the SAP technology community

Everyone can connect, contribute and collaborate- consultants, administrators and developersFocus around SAP NetWeaver and SAP xApps

High quality of technical resourcesArticles, how-to guides, Weblogs, collaborative areas, discussion forums and downloads, toolkits and code-samples

A collaboration platform, not a one-way street

SAP experts from customers, partners and SAP

SDN is powered by SAP NetWeaver®Built on the SAP Enterprise PortalFeaturing collaboration capabilities of SAP Knowledge Management

© SAP AG 2006, 54

7 Key Points to Take Home

SAP NetWeaver Administrator is the new tool for administration and management of your SAP NetWeaver system landscape

NWA is positioned to unify all administration and monitoring functionalities under a single roof

Start/stop of Java processes and applications is possible from this central place

Availability Dashboards help you to get a quick overview of the system status

New reporting functionality makes resource planning and activity reporting easier

ABAP and Java monitors are integrated in NWA with jumps into the ABAP analysis methods

More ABAP functionality will be added in future development

© SAP AG 2006, 55

Q&A

Questions?

© SAP AG 2006, 56

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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.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. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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.

Copyright 2006 SAP AG. All Rights Reserved

© SAP AG 2006, 57

Demo