Setup of the SAP NetWeaver Administrator

Dr. Astrid Tschense-Oesterle, SAP AG

Introduction to SAP NetWeaver Administrator Setup of the NWA infrastructure Demo

SAP NetWeaver Administrator

SAP NetWeaver Administrator is the new central administration and monitoring tool for the 6.40 Java systems of your SAP NetWeaver system landscape.

Central Monitoring & Administration System ABAP

Java
SAP NetWeaver Administrator

SAP NetWeaver Administrator is a Java application that is part of the shipment of SAP NetWeaver 04 SP 12.

SAP AG 2004, Title of Presentation / Speaker Name / 3

As of SAP NetWeaver 6.40 SP12, the SAP NetWeaver Administrator is part of the installation of the Java system (standalone installation as well as add-in installation). In release 04s the installation contains different usage types. If usage type EP is chosen, the SAP NetWeaver Administrator can be run inside the Enterprise Portal. Without EP, the NWA can be used as standalone application like in NW04.

SAP NetWeaver Administrator at a Glance

Target group
n Customer administrators and operators (daily use)

Platform focus
n First version is focused on Java n Next versions will cover the complete SAP NetWeaver

Monitoring
n Landscape availability view n Display of CCMS RZ20 monitors n Performance reports n Central log viewer

Administration
n Start and stop of Java applications n Central configuration

SAP AG 2004, Title of Presentation / Speaker Name / 4

SAP NetWeaver Administrator: Key Features

Central
n Administration, Problem detection and problem analysis in ONE tool

Usable
n Task oriented navigation n Screens follow newest SAP UI standards

Extensible
n Seamless navigation to other SAP NetWeaver administration functionality (UME, SLD, AC...)

Remote
n WebDynpro based n Runs in a browser (no client-side installation necessary)
SAP AG 2004, Title of Presentation / Speaker Name / 5

SAP NetWeaver Monitoring & Management

Central Monitoring & Administration System SAP NetWeaver Administrator

SLD
Monitoring & Management Productive Landscape

Solution Manager

Monitoring & Management Connectivity Layer Monitoring & Management Connectivity Layer (JMX, Agents) (JMX, Agents)

ABAP System

Java System

Non-SAP Component

SAP AG 2004, Title of Presentation / Speaker Name / 6

The system landscape consists of the systems which shall be monitored and one central administrative system of the highest release possible. To use the NWA, the release has to be at least NW04 6.40 SP12 or NetWeaver 2004s. SAP recommends to use a double stack (ABAP+ Java system) for the central system (CEN) where the System Landscape Directory is running, too. The SLD is a java application that can be started in every NetWeaver Java system. With agents and different kinds of connections the remote systems are connected to the central system, the SLD and the SAP NetWeaver Administrator.

Introduction to SAP NetWeaver Administrator Setup of the NWA infrastructure Demo

NWA Configuration
The following steps have to be performed: n Configure and Activate the System Landscape Directory (SLD)
Activate the Object Server Load the CIM model Start the Data Supplier Bridge

n Adjust the Central Monitoring System (CEN)

For every instance of a J2EE Engine: Register a CCMS Agent SAPCCMSR For every ABAP instance: Register a CCMS Agent SAPCCM4X Register CCMSPING and assign the monitored systems

n Setup of the NWA connections

SAP AG 2004, Title of Presentation / Speaker Name / 8

Landscape-Wide Monitoring with NWA: Setting up an SLD

SAP AG 2004, Title of Presentation / Speaker Name / 9

This graphic gives an overview of the main connections needed fo r landscape-wide monitoring. All systems must be known to the monitoring infrastructure of the central system (CEN): n Monitored ABAP systems have to be registered in transaction RZ21 of the CEN. Additionally, they should be monitored with a SAPCCM4x agent. n For Java systems the SAPCCMSR agents have to be registered. Availability monitoring is done with CCMSPING agents. At least o ne has to be registered at the CEN system.

Setup of the Object Server

SAP AG 2004, Title of Presentation / Speaker Name / 10

To prepare the SLD for registering all systems of the system landcape, first the object server has to be started: n Call the SLD with http://<host>:<port>/sld Administration Server Settings. n As Object Server, enter the name of the host the SLD is running on, and click Set. n If your Java system consists of more than one instance, choose Profile and change the parameter of the Object Manager BufferInstances to false. n Select Start Server.

If you start the SLD and you receive an error message that you dont have the right permissions, start the NWA of the CEN system and open Administration User and Access. Go to Group and select the group sap.com.Lcr.Administrator. Add the administrator user (j2ee_admin) to this group. Open the SLD again.
10

Import of the CIM Model

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

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

SAP AG 2004, Title of Presentation / Speaker Name / 11

Import the Common Information Model: n Under Content, choose Import. n Enter the path to the CIM Model in your file system. n Default: : saploc/<SID>/SYS/GLOBAL/SLD/Model/CR_Content.zip n Choose Import File. Caution: This data import may take more than one hour!

11

Activate the Data Supplier Bridge

NW2004s

NW04 SP12

Enter the information for the gateway over which the monitored systems report data to the SLD. (NW04: Start the Data Supplier Bridge)

SAP AG 2004, Title of Presentation / Speaker Name / 12

Next step is to set the gateway parameters for the Data Supplier Bridge (in 04s the Bridge is already running, in NW04 systems the Data Supplier Bridge has to be started manually after entering the parameters). n NW2004s: Under Parameters ? Section Datasupplier, enter Gateway host and service for the RFC gateway which will be used to transfer the information of the monitored systems to the SLD. n NW04 SP12: Under Data Supplier Bridge, enter Gateway host and service for the RFC gateway. Start the Data Supplier Bridge.

12

Setup of Connections to the SLD

To display data from the system landscape the SLD has to be connected to the central monitoring system and the remote systems: n The JCo RFC connection SAPSLDAPI goes from CEN (gateway) to the J2EE Engine and calls the application lcrabapapi which registers new monitored systems at the SLD. n The SLD access data should be stored in transaction SLDAPICUST. n The data transfer from all ABAP systems to the SLD goes over the Data Supplier Bridge. The connection information has to be entered in transaction RZ70. n For the monitored Java systems the connection to the Data Supplier Bridge has to be entered in the local Visual Administrator.

SAP AG 2004, Title of Presentation / Speaker Name / 13

This is an overview of the necessary connections to the SLD from CEN, from the monitored ABAP- and Java systems. The details of the connection setup are displayed on the next slides.

13

Create the SLD customizing connection from CEN

Central Monitoring and Admin System
ABAP
Monitoring Infrastructure
SLDAPICUST

J2EE Engine

NetWeaver Administrator
RFC Connection SLD_<host>_<SID>

SLD-System
lcrabapapi

J2EE Engine
http

SLD

Data Supplier Bridge

SAP AG 2004, Title of Presentation / Speaker Name / 14

With the RFC connection SAPSLDAPI monitored systems are registered in SLD. This connection goes over the gateway to a j2ee application named lcrabapapi, talking with SLD over http. A password is needed for the connection from lcrabapapi to SLD which has to be entered in transaction SLDAPICUST in the CEN system.

14

SAPSLDAPI Gateway

Java

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

Connections between SLD system and CEN

Transfer information of new systems from CEN to gateway

and from gateway to the J2EE Engine, where appl. lcrabapapi is called.

SAP AG 2004, Title of Presentation / Speaker Name / 15

In transaction SM59 in the CEN system, create the RFC destination SAPSLDAPI. n Enter Connection Type T and a description like Connection to SLD. Click on Save. n As Activation Type choose Registered Server Program. n Enter the Program ID SLD_<host>_<SID>, where SID is the CEN system. n Enter Gateway host and port. n Save the destination. In the Visual Admistrator of the SLD system, go to Server Services JCo RFC Provider and create a destination with the Program ID you ha ve specified before: SLD_<host>_<SID>. n Add the gateway host and service name. n For the number of processes which can work in parallel, enter 3. n Enter the application server name of the CEN system and the system number. n As a user is needed to log on to the CEN system, specify logon data for a user with administration rights at the CEN system.
15 n Click on Set. Now you can test the connection in SM59.

Transaction SLDAPICUST
A password is needed for the connection from the Java application lcrabapapi to the Sld which has to be entered in transaction SLDAPICUST in the CEN system.

store SLD password

SAP AG 2004, Title of Presentation / Speaker Name / 16

Enter the logon data to the SLD in transaction SLDAPICUST: Enter the Alias name (or host name), check the Prim. checkbox, e nter SLD port and user as well as the password for the user. Now you may call transaction SLDCHECK to see whether the connection to the SLD works properly.

16

Store SLD Bridge connection Data in every ABAP system

Transaction RZ70

The data transfer from all ABAP systems to the SLD goes over the Data Supplier Bridge. The connection information has to be entered in transaction RZ70 of all monitored ABAP Systems (default data transfer every 720 minutes).

SAP AG 2004, Title of Presentation / Speaker Name / 17

The data transfer from all ABAP systems to the SLD goes over the Data Supplier Bridge. The connection information has to be entered in transaction RZ70 (default data transfer every 720 minutes) of all monitored ABAP Systems. n For SLD Bridge: As Gateway Information, enter Host and Service of the gateway. n Click on Activate .

17

HTTP Connection from (all) Java systems to SLD

All monitored Java systems have to specify an HTTP connection to the SLD. In the local Visual Adminstrator, go to the server node, choose Services SLD Data Supplier HTTP Settings tab. Enter the Host and the HTTP port of the SLD system to which your system will report the data. Enter the Administrator user and password of the SLD system and choose the Save option.
SAP AG 2004, Title of Presentation / Speaker Name / 18

All monitored Java systems have to specify an HTTP connection to the SLD. An initial configuration of the data supplier for J2EE-based systems is performed by the SAP installation tool SAPinst when you install the SAP J2EE Engine. However, if you want to change the default settings, or if you used a different method to install the SAP J2EE Engine, you can use the Visual Administrator to configure the data supplier manually. n From the server node, choose Services SLD Data Supplier HTTP Settings tab. n Enter the Host and the HTTP port of the SLD system to which your system will report the data. n Enter the Administrator user and password of the SLD system and choose the Save option.

18

Summary
We have started the SLD and created all necessary connections from the monitored ABAP and Java systems to the SLD.

Next step: Adjust the Central Monitoring

SAP AG 2004, Title of Presentation / Speaker Name / 19

19

Setup Scenarios
2 Possible Cases: n Setup of the Monitoring Landscape from Scratch Steps are described on the following slides. n Integration of the NetWeaver Administrator and System Landscape Directory into an already existing monitoring landscape System registration in the System Landscape Directory has to be triggered with a startup-method (CCMS_SCR_SLD_Consistency_Check)

SAP AG 2004, Title of Presentation / Speaker Name / 20

If you enter a remote ABAP or Java system in the monitoring architecture, an association is automatically created in the SLD (if both monitored system and CEN are entered in the SLD), that the remote system is monitored by CEN. You require this association with the name Centrally Monitored Application System, so that monitoring data from the remote system can be displayed in the NW Admin. If you have already set up central monitoring and are only configuring the SLD afterwards, this association is created by a start-up method. Methods of this type are automatically started after the system has been booted up.

20

Reset Segment to Warmup Status

Central Instance segment

SAP AG 2004, Title of Presentation / Speaker Name / 21

In a double-stack installation, the Java applications are started after the ABAP system parts, therefore it is not guaranteed that the SLD is already running at this time. We therefore recommend that you create the required associations by manually starting the method (CCMS_SCR_SLD_Consistency_Check). To do this, reset the central instance of CEN to WARMUP status, in order to start all start-up methods again. To do this, follow the procedure below: 1. Call transaction RZ21 in CEN and choose Technical Infrastructure Display Topology. 2. Choose the Local Segments (<System ID>) tab page, and switch to change mode by choosing the Display Change button. 3. Select the segment for the central instance (naming convention SAP_CCMS_<host name>_<System ID>_<instance number>), and choose the Reset Segment to WARMUP Status button. Confirm in the messages that appear that you want to start the start-up methods again. It will take 5 minutes until the association in the SLD is created.

21

NWA Configuration
The following steps have to be performed: n Configure and Activate the System Landscape Directory (SLD)
Activate the Object Server Load the CIM model Start the Data Supplier Bridge

n Adjust the Central Monitoring System (CEN)

For every instance of a J2EE Engine: Register a CCMS Agent SAPCCMSR For every ABAP instance: Register a CCMS Agent SAPCCM4X Register CCMSPING and assign the monitored systems

n Setup of the NWA connections

SAP AG 2004, Title of Presentation / Speaker Name / 22

22

Register SAPCCMSR and SAPCCM4x Agents

SAP AG 2004, Title of Presentation / Speaker Name / 23

CCMS agents are independent processes with an interface using RFC to a central monitoring system and an interface to the shared memory. These agents have the following properties: A connection to CEN using RFC, to ensure greater downtime security and general availability Use of the push technology to optimize performance when reading and writing monitoring attributes and alerts Inclusion of the operating system collector SAPOSCOL to monitor processes at operating system level. Connection to systems with no SAP Web Application Server Monitoring of any log files There are various CCMS agents, including: Agent SAPCCMSR: Monitoring of components on which no SAP ABAP instance is active, such as the J2EE Engine or SAP IPC Agent SAPCCM4X: Monitoring of SAP ABAP systems as of SAP Basis 4.X

23

Setting up SAPCCM4X for ABAP Systems

The agent SAPCCM4X needs to be installed on the ABAP systems that shall be monitored. The agent executable is part of the installation (saploc/<sid>/Sys/exe/run/sapccm4x.exe). For the registration of the SAPCCM4X you need the user CSMREG and the file csmconf. Start the executable sapccm4x.exe in directory saploc/<SID>/SYS/exe/run in a command prompt with the command: sapccm4x.exe r pf=<drive>:/usr/sap/<SID>/SYS/profile/<inst_profile> Enter the necessary parameters the dialog requests, the admin password and CSMREG password. The agent gets registered as service sapccm4x.<inst_no>

SAP AG 2004, Title of Presentation / Speaker Name / 24

Use the SAPCCM4X agent to monitor any ABAP instance of an SAP System.

n Creation of CSMREG You create the user CSMREG in the central system. Choose transaction RZ21 -> Technical Infrastructure -> Configure Central System -> Create user CSMREG. Specify a password for CSMREG. n Creation of CSMCONF You get the csmconf file in the same transaction: Choose transaction RZ21 -> Technical Infrastructure -> Configure Central System -> Create start file csmconf for agents. Save the csmconf file in usr/sap/<SID>/<Inst.ID >/log/sapccm4x.

n Run the command sapccm4x.exe r pf=<path of instance profile>

24

Setting up SAPCCMSR for Java Systems

The agent SAPCCMSR needs to be installed on the Java systems that shall be monitored. The agent executable is part of the installation (no download necessary). For the registration of the SAPCCMSR agent you need the user CSMREG and the file csmconf. Start the executable sapccmsr.exe in directory usr/sap/<SID>/SYS/exe/run in a command prompt with the command: sapccmsr.exe r j2ee pf=<drive>:/usr/sap/<SID>/SYS/profile/<inst_profile> Enter the necessary parameters the dialog requests, the admin password and CSMREG password. The agent gets registered as service sapccmsr.<inst_no>

SAP AG 2004, Title of Presentation / Speaker Name / 25

Use the SAPCCMSR agent to centrally monitor a Java system. With this agent monitoring data from the Java system is transferred to the CEN system. n Creation of CSMREG You create the user CSMREG in the central system. Choose transaction RZ21 -> Technical Infrastructure -> Configure Central System -> Create user CSMREG. Specify a password for CSMREG. n Creation of CSMCONF You get the csmconf file in the same transaction: Choose transaction RZ21 -> Technical Infrastructure -> Configure Central System -> Create start file csmconf for agents. Save the csmconf file in usr/sap/ccms/<SID><Inst.ID >/sapccmsr.

n Run the command

sapccmsr r -j2ee pf=<path of instance profile>

25

Enter ABAP systems for monitoring in CEN

make the monitored system known in CEN, TA RZ21

create 2 RFC connections to the monitored system: <sid>_rz20_collect <sid>_rz20_analyze

SAP AG 2004, Title of Presentation / Speaker Name / 26

To monitor remote ABAP systems with CEN, you have to enter the remote systems in CEN to make them known. Two RFC destinations are necessary per remote system: n one for data collection with name <SID>_RZ20_Collect n one for analysis with name <SID>_RZ20_Analyze In transaction RZ21 of CEN choose Technical Infrastructure Create Entry for Remote Systems Goto RFC connections. Create a new connection with type r/3 connection. 1. Enter the name <SID>_RZ20_Collect and a description. 2. Choose connection type 3, click on save. 3. Specify the hostname, system number and gateway information. 4. Save and test the connection. 5. Create the connection <SID>_RZ20_Analyze with the same information. 6. Additionally, specify the logon type (current user, or enter a specific user). 7. Save and test the connection. 8. Go back to Create new Entry and enter the target system ID and the RFC destinations.
26

Setting up CCMSPING

SAP AG 2004, Title of Presentation / Speaker Name / 27

With the help of the availability agent CCMSPING you can check whether remote systems and their instances are available or not. In addition, basic performance attributes of the ABAP instances are reported, e.g. everage dialog response time, number of logged on users. A step by step description how to set up CCMSPING is provided in the SAP tutor Availability Monitoring with CCMSPING.

27

CCMSPING

SAP AG 2004, Title of Presentation / Speaker Name / 28

If you want to install CCMSPING you can download the executable from the SAP Service Marketplace, quick link swdc In the navigation bar, choose Download Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER 04 ABAP Server SAP KERNEL 6.40 32/64-BIT <operating system> Database Independent. You can install CCMSPING on any host in your IT environment, and it is not necessary to install the agent on a host with an SAP system. If you want to monitor a very large number of systems (>100=, we recommend that you do not install the agent on a host on which an SAP system is running. In distributed environments, you can also use multiple CCMSPING agents for your availability monitoring). Take SAP Note 212876 into account. Under Microsoft Windows, ensure that a share is released on the host with the name saploc, and that the directory \\host\saploc\prfclog exists. Install CCMSPING with the following call: ccmsping [-push] [n<instance number>] -R

28

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 2004, Title of Presentation / Speaker Name / 29

On the Availability Dashboard every selected system is displayed with its instances and an overview how many of them are available. For the ABAP systems, additional basic information like average response time, standardized response time (response time of a predefined transaction with average response time) and number of logged on users is offered.

29

Summary
n Now we have registered the agents for ABAP and Java systems n We have introduced the monitored systems to CEN (automatically in case of Java, with TA RZ21 -> Create System Entry in case of ABAP) n We have registered CCMSPING for the availability monitoring and assigned all systems.

Next Step: Setup of the NWA connections

SAP AG 2004, Title of Presentation / Speaker Name / 30

30

NWA Configuration
The following steps have to be performed: In CEN: n Configure and Activate the System Landscape Directory (SLD)
Activate the Object Server Load the CIM model Start the Data Supplier Bridge

Adjust the Central Monitoring System (CEN)

For every instance of a J2EE Engine: Register a CCMS Agent SAPCCMSR For every ABAP instance: Register a CCMS Agent SAPCCM4X Register CCMSPING and assign the monitored systems

Once for the system landscape: n Setup of the NWA connections

SAP AG 2004, Title of Presentation / Speaker Name / 31

31

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. n You need a direct connection to SLD with the corresponding permissions (login). (CIM Client generation settings) n 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. n You may store the login data to all monitored Java systems in the Java part of the central system. If you dont do this you have to enter user/password each time you want to display data from the connected systems.

SAP AG 2004, Title of Presentation / Speaker Name / 32

32

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 2004, Title of Presentation / Speaker Name / 33

An Error message for the SLD server comes up if either the SLD server is not running, or the permissions to get data from the SLD are missing. Check if the SLD is set up properly, then enter the CIM Client settings in the Visual Administrator of the NWA system, as displayed on the next slide.

33

CIM Client for data transfer from SLD to NWA

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

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

SAP AG 2004, Title of Presentation / Speaker Name / 34

Here an (SLD) administrator can give rights to SAP J2EE applications on the SAP J2EE Engine. These applications can then, by means of an internal interface of the SLD service, generate a CIM client for accessing the SLD (code-based security). To execute a particular CIM operation, a Java client calls the corresponding Java methods of the API. The API packs the operation and its parameters in an XML message. The API then sends the request to the SLD server by using HTTP. The SLD server executes the operation and sends the result, or the error message, in an XML message as an HTTP response to the API on the client side. The API forwards the results as the return value of the method call to the application.

[The first application is the NWA mainframe, the second is the SLD landscape selection popup.]

34

This error message for the central monitoring

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

SAP AG 2004, Title of Presentation / Speaker Name / 35

If you have created the connections to the SLD you may display monitoring data, but get the error message No central monitoring system configured.

Then the JcoRFC connection SAP.CCMS.CEN.<sid> is missing which is needed to get the monitoring data from CEN.

35

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 2004, Title of Presentation / Speaker Name / 36

The connection has to be created in the Jco RFC Provider Service in the Visual Administrator of the NWA system. Enter the program ID SAP.CCMS.CEN.<sid>, gateway host and service and the number of processes which should be processed in parallel (e.g. 3).

For the repository (which is created by the Jco server in the ABAP system), an administrator user and login is needed. Click on Set and see whether the connection can be started (running icon in the destination list).

36

This Error message for the JMX connection

comes up if the login to the monitored system is not stored in the NWA system.

SAP AG 2004, Title of Presentation / Speaker Name / 37

Even if you can select systems in the system selection list in NWA, you are not automatically allowed to view the information from this system. If you want to display data, a JMX connection is called which needs a user and password authentication. You can either enter the login information every time you want to display the system, or you enter the login information persistently in the Visual Administrator of the NWA system, as e xplained on the next slide.

37

Enter Connecting Data for administered Systems

In the central monitoring system the http connections and authentication parameters for all administered Java systems can be stored.

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

SAP AG 2004, Title of Presentation / Speaker Name / 38

In the Visual Administrator of the NWA system you can enter the http connections and authentication parameters for all administered Java systems. n Go to Server Services Destinations and open the HTTP tree. n Click on New an enter the destination name: sap.com/tc~je~jmx~wsconnector~sp/<SID>/<host> n Specify the URL: http://<host>:<port>/WSConnector/Config1?style=document n Set Authentication to Basic and enter user and password of an administrator user of the remote system. n Save your entries.

Caution: In case of a distributed installation, modify the entries as follows: n name: "sap.com/tc~je~jmx~wsconnector~sp/<SID>/<db host>" n name: "sap.com/tc~je~jmx~wsconnector~sp/<SID>/<db host>\<db instance name>" - in case of named MSSQL instances n URL: http://<j2eehost>:<port>/WSConnector/Config1?style=document
38

Optional Steps
n Start Availability Monitoring with GRMG n Create Users for the SAP NetWeaver Administrator n Create Administration Landscapes to make up smaller groups out of your System Landscape

SAP AG 2004, Title of Presentation / Speaker Name / 39

39

Configure the Availability Monitoring with GRMG

1. GRMG customizing file is maintained in Visual Administrator. 2. Download the GRMG customizing file into the file system. 3. The GRMG customizing file is uploaded into CEN by CCMS agent after max. 1 hour. 4. The GRMG infrastructure starts automatically.

SAP Web AS Java SAP Web AS Java

SAP System for SAP System for Central Monitoring Central Monitoring

GRMG Application
DB

GRMG Infrastructure

GRMG

SAPCCMSR Agent

CEN

CCMS

SAP AG 2004, Title of Presentation / Speaker Name / 40

Configuring Availability Monitoring with the GRMG

You can use the Generic Request and Message Generator (GRMG) to monitor the availability both of technical components and of entire business processes. You define the required configuration settings in a GRMG Customizing file, which is transferred to CEN by a CCMS agent. Note: For using GRMG it is necessary that the Internet Communication Manager (ICM) is configured and active on every ABAP instance of your system landscape. 1. In the navigation bar, choose Cluster Server Services Monitoring, and choose the GRMG Customizing tab page. 2. Expand the left part of the screen. The system displays all applications for which there are prepared GRMG Customizing files. Select sap.com/com.sap.engine.heartbeat. 3. Transfer the Customizing file to the CCMS agent by choosing the Upload button.
Checking the Configuration (Optional)

To check whether the GRMG monitoring was successfully activated, call transaction GRMG in CEN, and choose Upload/Download Query CCMS Agent for Scenarios. Note: Without manual polling, you need to wait up to an hour for the GRMG scenarios that you have uploaded in the Visual Administrator are transferred to CEN and started. 1. Call transaction GRMG. The system displays the scenario that you have just activated with its URL (scenstarturl) and description (scendesc). 2. Call transaction RZ20, and start the Heartbeat monitor in the SAP J2EE Monitor Templates monitor set. 3. Expand the J2EE Engine subtree. The system displays the monitored J2EE Engines that are monitored with the GRMG. You can see the J2EE Engine for which you have just configured availability monitoring under the name that you entered above under scendesc.
40

Configuration of User Management for NWA usage

You can create users with central and local display and administration permissions.

SAP AG 2004, Title of Presentation / Speaker Name / 41

If you want to create new users in a standalone Java system, you may use the User Management plugin in the NetWeaver Administrator. For use of the NWA, 4 different roles are available:

SAP_JAVA_NWADMIN_CENTRAL SAP_JAVA_NWADMIN_READONLY SAP_JAVA_NWADMIN_LOCAL SAP_JAVA_NWADMIN_LOCAL_READONLY

In a double-stack system the user management is done in the ABAP system part, transaction SU01.

41

Create Administration Landscapes

Under System Landscapes, click on New Landscape and specify a name. Then select the systems you want to be part of that Administration Landscape (use type and filter opportunities).

SAP AG 2004, Title of Presentation / Speaker Name / 42

You may define administrative System Landscapes in the SLD which are displayed as such for each user of the NetWeaver Administrator: n In the SLD, select System Landscape New Landscape. n Specify a name. n Select the systems you want to group in this new subordinary landscape (logical landscape group). n Click on Finish. Now the new landscape appears under landscape type Administration in the System Selection of the NetWeaver Administrator.

42

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.

For usage details see n the online documentation n SMP service.sap.com/nwa n the SAP Tutor Setup of the SAP NetWeaver Administrator

SAP AG 2004, Title of Presentation / Speaker Name / 43

43

Hands-on Solve the following Tasks:

n n n

Login to NWA Find System Configuration Information Deal with Applications

n n n

Display and Start/Stop the Application Display and modify the Application Log Write a Trace for an Application

Create a Java System Report

SAP AG 2004, Title of Presentation / Speaker Name / 44

44

Further Information

Public Web:
www.sap.com NetWeaver Developers Guide: www.sdn.sap.com/sdn/developersguide.sdn SAP Developer Network: www.sdn.sap.com NetWeaver Platform IT Scenario Operations www.service.sap.com Quick link /nwa

Related SAP Education Training Opportunities

http://www.sap.com/education/ ADM200

SAP AG 2004, Title of Presentation / Speaker Name / 45

45

Questions?

Q&A
SAP AG 2004, Title of Presentation / Speaker Name / 46

46

Copyright 2005 SAP AG. All Rights Reserved

n 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.

n Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors . n Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. n 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 o f IBM Corporation.
n Oracle is a registered trademark of Oracle Corporation. n UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. n Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. n HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World Wide Web Consortium, Massachusetts Institute of Technology. n Java is a registered trademark of Sun Microsystems, Inc. n JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. n MaxDB is a trademark of MySQL AB, Sweden. n 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.

n 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.

n 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.
n 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.
n 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.
n 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 AG 2004, Title of Presentation / Speaker Name / 47

47