SRM LandscapeMonitor

8/17/2019 SRM LandscapeMonitor

http://slidepdf.com/reader/full/srm-landscapemonitor 1/41

© 2007 SAP AG

SAP SRM 4.0/5.0 SystemLandscape Monitoring

Best Practice for Solution Management

Version Date: April 2007

Contents

Applicability, Goals, and Requirements................................................................................................1

Best Practice Procedure......................................................................................................................3

Procedure.....................................................................................................................................3

CCMS Agent Installation ...............................................................................................................5

System Groups .............................................................................................................................7

Property Variant ............................................................................................................................8

Monitoring the SRM Server...........................................................................................................9

Monitoring the Standalone ITS 6.20............................................................................................. 11

Monitoring the Integrated ITS 6.40 or 7.0.....................................................................................15

Monitoring Internet Pricing Configurator 4.0.................................................................................16

Monitoring the Internet Pricing Configurator 5.0 (Integrated in VMC)............................................18Monitoring SAP Catalog Content Management 2.0 ......................................................................19

Monitoring TREX 7.0...................................................................................................................23

Monitoring Live Auction Cockpit 2.0 or 5.0...................................................................................29

Monitoring Business Connector 4.6 or 4.7 ...................................................................................33

Set Up CCMS.............................................................................................................................40

Further Information ...........................................................................................................................41

Applicability, Goals, and RequirementsTo ensure that this Best Practice is the one you need, consider the following goals and requirements.

Goal of Using this Service

SAP Supply Relationship Management (SRM) is a product that focuses on procurement. The SRMSolution Landscape consists of several components that need to be monitored both from a technicalas well as from a business process perspective. The aim of this Best Practice is to briefly show, how toset up a System Monitoring for a SRM System Landscape with its different technical components.

This is not an in-depth description of the whole SAP monitoring architecture. However, examples willbe given where appropriate. Where necessary, references to related documents will be referenced.



Best Practice: SAP SRM 4.0 / 5.0 System Landscape Monitoring

© 2007 SAP AG

2

Al ternat ive Practices

This Best Practice focuses on technical issues. Refer to the Best Practice Manage Procurement inSAP EBP to obtain information on how to set up a monitoring from a Business Process point of view.The Best Practice Central System Monitoring for mySAP.com provides information about systemmonitoring and the use of the Solution Manager

Staff and Skills Requirements

To implement this Best Practice, you require a system administration team with technical knowledgeabout the system components used in a SRM solution landscape.

System Requirements

We recommend that you use a separate R/3-based system for the Solution Manager. This systemshould also be used as the main system for the CCMS, that is, all components send their data to thisR/3-based monitoring system.

Duration and Timing

Duration

Creating and implementing a SRM Solution Monitoring concept could take appoximately one week.

Timing

The best time to apply this Best Practice is after installation of the SRM solution landscape.

How to Use this Best Practice

Follow the order of sections of this Best Practice when implementing the SRM Solution Monitoring.

Case Study or Sample Scenario

In the following, it is assumed that monitoring should be set up for the components to implement atechnical monitoring for a SRM System Landscape:




© 2007 SAP AG

3

Component Relevant for SRM 4.0 Relevant for SRM 5.0

SRM Server 5.0/5.5

Internet Transaction Server (ITS) 6.20

Integrated ITS 6.40/7.0

Internet Pricing Configurator (IPC) 4.0

Internet Pricing Configurator (IPC) 5.0(integrated in VMC)

Business Connector (BC) 4.6 or 4.7

SAP Catalog Content Management (CCM) 2.0

Text Retrieval and Extraction (TREX) 7.0

Live Auction Cockpit (LAC) 2.0/5.0

Furthermore, an R/3-based monitoring system with the Solution Manager installed is assumed to beavailable.

Best Practice Procedure

Procedure

To monitor the SRM landscape we assume in the following that you have an extra SAP R/3-basedsystem available with the Solution Manager installed.

All individual components send their monitoring data to the CCMS of the monitoring R/3 system,therefore monitoring data of each component can be displayed in transaction RZ20.. After that, it is

possible to map this data to the Solution Manager, where monitoring can be configured using agraphical representation with simple step-forward-navigation.

The following diagram shows an example of the most commonly used business process with SRM.This is the indirect procurement; that is, procurement of indirect materials. The diagram is a screenshot from the Solution Manager.




© 2007 SAP AG

4

The solution landscape shown in the diagram below, displays a more technical perspective. Again, thediagram is a screen shot from the Solution Manager. You can see the software components involvedin the SRM solution landscape. The dark boxes show the names of the involved servers anddatabases. For each component you can assign certain alerts. In the example the Internet TransactionServer (ITS) sends an alert to the monitoring R/3 system, which is displayed as a little box with anexclamation mark in it. You can click this box, which opens another pop-up providing more detailsabout the alert.




© 2007 SAP AG

5

CCMS Agent Installation

Funct ion of the CCMS Agent

Non-R/3-based components can be monitored using the CCMS agent technology. This technologyenables you to monitor components remotely from any R/3-based system (In this Best Practice this isthe monitoring R/3 system). The agent sapccmsr uses RFC to communicate with the central

monitoring system. As an RFC client, the agent automatically sends the collected data to the centralmonitoring system. The agent monitors components on which there is no active SAP instance, such asstand-alone databases, OS components and also monitors the other components' log files. Datacollected by saposcol can be viewed by using the agent technology.

Configuring saposcol

Install saposcol as described in SAP-note 19227. After successful installation saposcol is able to

provide data about the operating system:

File systems

CPU

Paging

Commit charge (NT)

OS Collector

LAN

Data is written to shared memory and read out by the agent. The agent transfers this data to theCCMS of the monitoring R/3 system.

© 2007 SAP AG

6

Installation and Registration of the Agent

Download the SAPCCMSR. EXE for the operating system of your choice into the agent’s working

directory (see SAP note 209834). Check the following table for the working directory.

Operating System Working DirectoryUNIX / usr / sap/ t mp/ sapccmsr

Windows 2000, Windows2003

<dr i ve>: \ usr \ sap\ sapl oc\ pr f cl og\ sapccmsr

sapl oc must be released (shared); you must create the

working directory yourself during the installation

It is important that directory \ sapl oc is shared. Otherwise the agent will not run.

Create a configuration file called csmconf . This file is required for a dialog-free installation. Save the

file in the working directory of the CCMS agent. Using a configuration file allows the installation to rununsupervised and the file is always the same when installing the CCMS agent on several servers. The

content of the csmconf should look as shown below. Make sure all parameters are set to match your configuration and system information. (For detailed explanation refer to the CCMS Agent Description

document. See also http://service.sap.com/monitoring.)

Example: Content of the csmconf file

CEN_CONFI G

CEN_SYSI D=<SI D of moni tor i ng R/ 3 syst em>

.

CEN_ADMI N_USER

CEN_ADMI N_CLI ENT=<cl i ent >

CEN_ADMI N_USERI D=<val i d user >

CEN_ADMI N_LANG=<l anguage> CEN_ADMI N_LOADBALANCI NG=n

CEN_ADMI N_ASHOST=<host name of appl i cat i on ser ver >

CEN_ADMI N_SYSNR=

CEN_ADMI N_TRACE=0

CEN_ADMI N_MSHOST=<host name of message ser ver >

CEN_ADMI N_PASSWORD=<Passwor d of t he user >

.

CEN_GATEWAY

CEN_GATEWAY_HOST=<host name of gat eway ser ver >

CEN_GATEWAY_SYSNR=

CEN_GATEWAY_ TRACE=0.

CEN_CSMREG_USER

CEN_CSMREG_CLI ENT=<cl i ent >

CEN_CSMREG_USERI D=<val i d user >

CEN_CSMREG_LANG=<l anguage>

CEN_CSMREG_LOADBALANCI NG=n

CEN_CSMREG_ASHOST=<host name of appl i cat i on s er ver >

CEN_CSMREG_SYSNR=

CEN_CSMREG_TRACE=0

CEN_CSMREG_MSHOST=<host name of message ser ver >

CEN_CSMREG_PASSWORD=<Passwor d of t he user >

.

http://service.sap.com/monitoring

© 2007 SAP AG

7

Both ADMI N_USERI D and CSMREG_USERI D must be valid R/3 users in the Central Monitoring System

with RFC privilege.

It is possible to install the agent without using a configuration file. All the information will be promptedfor, and should be answered interactively. After the completion of the installation, a configuration filewill be created in the agent’s working directory.

Register the agent using the following command. During registration, the agent automaticallycreates an RFC connection to the central monitoring system.

sapccmsr –R –f <f i l e name> to Register

sapccmsr –U to Un-Register

<f i l e name> is the name of the configuration file for the dialog-free installation. The default file

name is csmconf .

Registration of the agent creates a log file (sapccmsr <pi d>. l og) in the working directory. Check

the file for any errors and warnings.

On Windows NT and Windows 2000, the agent will be configured as a NT service that will startautomatically. The NT Service is called ‘SAPCCMSR. 99’.

On UNIX platform, the agent does not start automatically. You must start it manually and alsoensure that the CCMS agent is started after a system restart. The command to start the agent is

sapccmsr –DCCMS

Troubleshooting

Checking the successful operation of the agent can be done by inspecting the log:

Check the log-file sapccmsr <pi d>. l og

Check whether your user id has the administrative rights to start a service on Windowsenvironment.

System Groups

Before creating new SRM monitors, we recommend that you first maintain the system groups intransaction RZ21.

A system group consists of a series of systems that you want to display together in the CCMSmonitoring architecture. You can specify a system group when you are defining a monitor—themonitor then contains all systems that belong to the system group.

Definitions of system groups are stored in the CCMS System Component Repository (SCR). The SCRis a component that maps to one or more SAP systems.

To call the individual functions in the table, choose CCMS Configuration Alert Monitor , or go to

transaction RZ21. Then choose Technical Infrastructure Configure Central System MaintainSystem Groups, and expand the tree to display the groups that have already been defined.

We recommend creating the following system groups:

System Group System

ExchangeInfrastructure_Systems SAP Exchange Infrastructure

SAP SRM Server

SAP CCM

J2EE_Systems LACWPS SAP WAS Java

SRMServer_Systems SAP SRM Server

TREX_Systems TREX

CCM_Systems SAP CCM




© 2007 SAP AG

8

Property Variant

You should also create a property variant (for example, SRM40_Default) to save your customizing andconfiguration during the setup of the CEN.

A monitoring properties variant contains the following data:

Settings for properties

Method assignments for monitoring tree elements (MTE)

MTE classes and attribute groups.

Every change made to these settings is assigned to a properties variant.

For further information about property variants consult the NetWeaver online help: help.sap.com/nw04

SAP NetWeaver Release ’04 SAP NetWeaver Solution Lifecycle Management Solution

Monitoring Monitoring in the CCMS The Alert Monitor

http://help.sap.com/

http://help.sap.com/

© 2007 SAP AG

9

Monitoring the SRM Server

Relevant for

SRM 4.0 and SRM 5.0

Setup of Monitoring

In the following, we assume that the SRM system reports alerts to a so-called monitoring R/3 systemthat has a Solution Manager installed.

1. Create a user CSMREG in the SRM system. (see SAP-note 455356 for details)

2. Create 2 RFC connections using transaction SM59 from the monitoring R/3 system to the SRM-system:

o <SID of the SRM system>_RZ20_COLLECT using CSMREG as login user

o <SID of the SRM system>_RZ20_ANALYZE using any dialog user of your choice as

login user

3. Create a new entry for the SRM system in RZ21 of the monitoring system (RZ21 Technical

Infrastructure Configure Central System Create Entry for Remote System). Enter the RFCdestinations created in the step above.

As per standard the monitoring of the SRM system via CCMS is available in the SRM system itself.Therefore, just the mapping of CCMS data from the SRM system to the monitoring R/3 system needsto be done:

1. Log on to the monitoring R/3 system, and call transaction RZ20. Choose Extras Activatemaintenance function

2. Click the button Create

3. Expand the tree that belongs to the SRM system and select the monitor elements that are of interest. As an example, we suggest to select:

Database

EBP Procurement Internal

Oracle (if an Oracle database is used for the SRM system, else the database type used)

SAP Change & Transport System

Spool

System Configuration

Instance




© 2007 SAP AG

10

4. Next, click the Save button

5. In the next dialog box enter the name of the monitor. Here, we assumed that a monitor set SRM4.0 was already created.


7. In the central monitoring R/3 system map the data of the SRM system from the CCMS to theSolution Manager. See the Best Practice Central System Monitoring for mySAP.com for details onhow to perform the mapping to the Solution Manager.

© 2007 SAP AG

Monitoring the Standalone ITS 6.20

Relevant for

SRM 4.0 only

Prerequisites

Use this procedure to enable monitoring of the standalone Internet Transaction Server 6.20 (ITS)activity by the Computing Center Management System (CCMS) in the R/3 System. Previously, theonly way to monitor an ITS inside the R/3 system was to get the ITS to report performance-relevantdata via an RFC call into the CCMS environment of an SAP R/3 system. Now, you can monitor the ITSenvironment by using the CCMS agent technology to collect ITS performance and configurationvalues. The values are sent on a regular basis via the agent to the R/3 system. The data is thenavailable to the CCMS monitors inside the R/3 system using transaction RZ20. Transaction RZ20enables you to track alerts, view the current status of the ITS environment and read configuration dataof each virtual ITS instance on demand.

Furthermore, you can collect data for each reported value and automate actions that should betriggered after an alert has occurred. In addition to the option of monitoring the ITS values, you cancollect the operating-system-specific data (such as overall CPU consumption, memory consumption,or paging activity) via the agent technology. You can then use ITS Administration to get additionaldetails and, if necessary, correct any errors.

To install the ITS performance monitor and use the CCMS agent:

Install the CCMS agent (the sapccmsr program for monitoring of hosts without SAP application

servers) and prepare the ITS for CCMS monitoring.

Set up the monitors in the R/3 CCMS monitoring environment.

Apply the required basis support package in the R/3 monitoring system.

For the latest information about setting up ITS monitoring, refer to SAP Note 418285. Setting upoperating system monitoring (for example, for ITS servers and web servers) is described in SAP Note450741.

Check the version of the ITS you are using. To do this, open a Windows Explorer, change to the ITSprogram directory (usually <dr i ve>: \ PROGRAM\ FI LES\ SAP\ I TS\ 6. 20\ Pr ogr ams\ ) and right-

click the file Agat e. EXE. Select Properties, go to the tab Version and choose the Build No.

Remember the value and search for this value in note 491781. In this note the corresponding patchlevels are listed. You meet the prerequisites, in case you have:

ITS 6.20 (patch level 5 or higher).

R/3 System, release 4.6C or higher

Installing the CCMS Agent and Preparing the ITS

Download the agent documentation from the Service Marketplace. The documentation can be foundunder the alias SYSTEMMANAGMENT. Choose System Monitoring and Alert Management MediaLibrary -> Documentation. The document is called ‘CCMS-Agents: Features, Installation and Usage’.

1. Download the latest version of the agent.

For the ITS monitoring an CCMS agent version 6.20 is required. The ITS 6.20 ITSmon plugin isnot compatible with a CCMS agent 6.40.

The CCMS agent version 6.20 is available under http://service.sap.com/patches SAP Support

Packages and Patches

Entry by Application Group

SAP Application Components

SAP SRM (with SAP EBP)

http://service.sap.com/patches

http://service.sap.com/patches

© 2007 SAP AG

12

SAP SRM 4.0

Entry by Component

ITS

SAP ITS 6.0

<operating system>

Download the file SAPCCMSR*. EXE.

2. Install the CCMS agent. You need a valid user in the monitoring R/3 system with RFC-privileges.See section CCMS agent Installation

3. Call the ITS Admin instance and set the parameter PerfMonitoring on all virtual ITS instances that

you want to monitor to 1. This can be done by calling the ITS Admin instance choosing the

virtual instance Configuration Registry CCMS Perfmonitoring. You have to restart theITS to apply these changes!

4. The ITS monitoring library (I TSMON. DLL) is placed into the ITS program directory during the ITS

installation. Adapt the sapccmsr . i ni file in the CCMS agent directory by adding the line:

Pl ugI n \ I TSMON. dl l 

The string must be entered in DOS format (for example,Pl ugI n C: \ PROGRA~1\ SAP\ I TS\ 6. 20\ pr ogr ams\ i t smon. dl lC: \ PROGRA~1\ SAP\ I TS\ 6. 20\ pr ogr ams).

5. Save the file and restart the CCMS agent service.

6. Check the sapccmsr . l og file if the plugin has been loaded, you should see something like:

I NFO: Pl ugI n manager i ni t i al i zed success f ul l y.

The sapccmsr . l og file is located in the CCMS agent directory just like the sapccmsr . i ni file.

Sett ing up the Monitors in the R/3 CCMS Monitoring Envi ronment

1. Start transaction RZ20.

2. Choose Extras Activate maintenance function.

3. Choose Monitor (set) Create.

4. Select New monitor set.

5. Choose Enter .

6. In the Monitor set field, enter Early Watch Alert. The name of the monitor set is mandatory.

7. Select Public (visible for all users).8. Choose Enter .

9. Select the new monitor set and choose Monitor (set) Create.

10. Select <<< New monitor >>> and then choose Edit Create nodes.

11. In the dialog box, select Rule node and choose Continue

12. In the Rule field, enter CCMS_GET_MTE_BY_CLASS, and then choose Continue.

13. In the R3System field, enter <CURRENT>.

14. In the field MTEClass, enter the ITSRootContext.

15. In the Display options for MTE nodes from a rule, select Display following parts of the MTE name

and choose Context.

16. Choose Continue.




© 2007 SAP AG

13

17. Repeat from step 10 but in the MTEClass field, enter ITSselfH.

18. Save the monitor and enter as the name EWA ITS. This name is mandatory. New ITS servers

reporting to this R/3 system will be automatically visible in this monitor.

19. When using a monitoring system with a release below 6.20 with support package 17, perform thebelow mentioned steps:

Start transaction RZ21. Activate the performance database by selecting Technical Infrastructure

Performance database Define Background Job. Then schedule the background job. After theinitial run of the job, you can go to transaction RZ20 and select the MTE that you want toinvestigate.

For releases from 6.20 with support package 17 and higher, refer to SAPNet note 577467 for details on activating the collection of history data for the above created ITS monitor.

20. If the monitoring system is on basis release 4.6C, 4.6D or 6.10 apply the basis support packagespecified in SAP Note 452797.

After the installation, the CCMS of the monitoring system contains a new tree EWA ITS below Early

Watch Alert.

21. Next, map the ITS monitoring from the tree Early Watch Alert to the tree SRM 4.0. To do so, log onto the monitoring R/3 system, and call transaction RZ20. Choose Extras Activate maintenancefunction.

22. Set the cursor on the tree element SRM 4.0 and click the button Create.23. Expand the tree that belongs to the SRM system and select the monitor elements of the ITS.




© 2007 SAP AG

14


25. Enter the name of the new monitor: SAP ITS




© 2007 SAP AG

Monitoring the Integrated ITS 6.40 or 7.0

Relevant for

SRM 4.0 and SRM 5.0

Setup of Monitoring

As of kernel release 6.40 patch level 82, the monitoring of the integrated ITS via CCMS is availableand switched on by default. Therefore, only the mapping of CCMS data from the SRM system (wherethe ITS is integrated) to the monitoring R/3 system needs to be done:

Log on to the monitoring R/3 system, and call transaction RZ20. Choose Extras Activatemaintenance function

1. Set the cursor on the tree element SRM 4.0 and click the button Create.


3. In the dialog box choose Rule node and then choose Continue.

4. In the Rule field, enter CCMS_DEFINE_R3_SYSTEMS, and then choose Continue.

5. In the R3System field, enter the name of the SRM system.

7. Mark the previously created rule node and choose Create to create another rule node of typeCCMS_GET_MTE_BY_CLASS.

8. In the R3System field, the name of the SRM system is already pre-filled. In the field MTEClass,enter the R3ITS. Choose Continue.

As the integrated ITS receives HTTP requests from the Internet Communication Manager (ICM), wealso suggest monitoring that component as well. To do this create another rule node of typeCCMS_GET_MTE_BY_CLASS. Assign MTEClass ICM to this node.

As a result you should get a monitoring structure like this:


10. Enter the name of the new monitor: Integrated ITS




© 2007 SAP AG

16


Monitoring Internet Pricing Configurator 4.0

Relevant for

SRM 4.0 only

Setup of Monitoring

The procedure described in this paper only applies if the following prerequisites are fulfilled:

- Version of the CCMS agent 620 Patch collection 1/2004 and higher

- IPC version 3.0 SP6 and higher or IPC version 4.0

The monitoring of the IPC is set up by the following steps (see also SAP-note 502461):

1. Check whether the configuration file i pcmon. i ni is located in the current directory of the

SAPCCMSR agent (for example, c: \ usr \ sap\ sapl oc\ PRFCLOG\ sapccmsr ). If this file ismissing it can be downloaded from SAP note 502461.

2. Verify the contents of the i pcmon. i ni .

In the configuration file set parameter i nst al l path to the installation directory of the IPC.

Furthermore, statuses of the IPC can be excluded from a red valuation. Parameter I PC_GREEN_I F_VALUE contains a list of return codes for which a 'green' alert should be returned

instead of the default value. For example, if no knowledge base is used, the heartbeat returnsstatus code 541. This leads to a red alert if it is not maintained in the exception list. In this case,set value 541 in the value list for parameter I PC_GREEN_I F_VALUE.

Example: I PC_GREEN_I F_VALUE="541"

You can attach further values separated by commas to the list.3. Restart the CCMS agent to activate the IPC Monitoring.

Shortly after that, the agent sends the data to the CCMS of the monitoring system. Next, map the IPCdata to the SRM tree:

4. Set the cursor on the monitor set SRM 4.0 and click Create.

5. Expand the tree that belongs to the SRM system and select the monitoring elements of the IPC




© 2007 SAP AG

17


7. Enter the name of the new monitor: SAP IPC and click the Save button



© 2007 SAP AG

Monitoring the Internet Pricing Configurator 5.0

(Integrated in VMC)

Relevant for

SRM 5.0 only

Prerequisites

The profile parameter vmcj / enabl e_ccms_moni t or i ng must not be set to false. This parameter

has been introduced with VMC Patch Collection 21 to deactivate the VMC monitoring in the CCMS if VMC is not used.

Setup of Monitoring

If not switched off explicitly the monitoring of the Virtual Machine Container via CCMS is available per

default. Therefore, only the mapping of CCMS data from the SRM system (where the VMC isactivated) to the monitoring R/3 system needs to be done:

1. Log on to the monitoring R/3 system, and call transaction RZ20. Choose Extras Activatemaintenance function



4. In the dialog box, choose Rule node and choose Continue.


6. In the R3System field, enter the name of the SRM system.


8. In the R3System field, the name of the SRM system is already pre-filled. In the field MTEClass,enter the vmcSum. Choose Continue.


After creating all nodes, click the Save button and enter Virtual Machine Container as name of

the monitor.

© 2007 SAP AG

19

Monitoring SAP Catalog Content Management 2.0

Relevant for

SRM 4.0 and SRM 5.0

PrerequisitesSAP Catalog Content Management (CCM) is an Add-on installed in the ABAP stack of a Web Application Server. This can be the SRM Server itself or a separate WebAS.

In the following we assume, that the CCM Add-on is installed on a different system than the SRMserver. To include the CCM monitoring into the monitoring infrastructure of CEN perform the followingpreparation steps. These actions are not required if CCM is installed in the SRM system.

Create a user CSMREG in the CCM system. (see SAP-note 455356 for details)

Create 2 RFC connections using transaction SM59 from the monitoring R/3 system to the CCM-system:

<SID of the CCM system>_RZ20_COLLECT using CSMREG as login user

<SID of the CCM system>_RZ20_ANALYZE using any dialog user of your choice aslogin user

Create a new entry for the CCM system in RZ21 of the monitoring system (RZ21 Technical

Infrastructure Configure Central System Create Entry for Remote System). Enter the RFCdestinations created in the step above.

CCMS Configuration

Catalog upload and publishing is done via the SAP Exchange Infrastructure (XI) and severalbackground jobs. Therefore the Integration Engine of the underlying SAP Web Application Server

(ABAP) and these background jobs should be monitored in addition to the standard Web ASmonitoring.

To monitor SAP CCM background jobs in CEN, you need to enter the job names in table ALBTCMONin the SAP CCM system. The following are the most important jobs for CCM:

CATALOG_PUBLI CATI ON_REQUEST

AUTH_UPDATE

MAPPI NG_J OB

© 2007 SAP AG

20

Additionally, the background job monitor must be defined in the CEN system. To do this, perform thefollowing steps:



3. Choose Virtual node and enter Background Processing as node name

4. Mark the created node and choose Create



7. In the R3System field, enter the CCM system or the name of the created system group (for example, CCM_SYSTEMS).

8. Create another rule node of type CCMS_GET_MTE_BY_CLASS.

9. In the R3System field, enter the CCM system or the name of the created system group (for example, CCM_SYSTEMS).

10. In the field MTEClass, enter the R3BPSystemWideContext.

11. Choose Continue.

Beside the background jobs, we also recommend including monitoring objects for the CCMdatabase as well as for the Integration Engine into the monitoring infrastructure. Create thefollowing two virtual nodes:

- Database Monitoring

- Integration Engine for CCM

Afterwards refer to the table below and create the corresponding rule nodes following the sameprocedure as described above.

Node Type Parameter Value

Background Processing Virtual

CCMS_DEFI NE_R3_SYSTEMS Rule R3System <CCM_SYSTEMS>

R3System <CCM_SYSTEMS>CCMS_GET_MTE_ BY_CLASS Rule

MTEClass R3BPSyst emWi deCont ext

Database Monitoring Virtual

CCMS_DEFI NE_R3_SYSTEMS Rule R3System <CCM_SYSTEMS>

CCMS_GET_MTE_ BY_CLASS Rule R3System <CCM_SYSTEMS>

© 2007 SAP AG

21

MTEClass Dat abase Moni t or i ng

R3System <CCM_SYSTEMS>CCMS_GET_MTE_ BY_CLASS Rule

MTEClass CCMS_DB_mcmt c

Integration Engine for CCM Virtual

CCMS_DEFI NE_R3_SYSTEMS Rule R3System <ExchangeI nf r ast r uct ure _Syst ems>

QRFC Queues Virtual

Exactly-Once Processing Queues Virtual

R3System <ExchangeI nf r ast r uct ure _Syst ems>

CCMS_GET_ MTE_BY_CLASS Rule

MTEClass XI _I nt _Serv_I nbound_XBTI



MTEClass XI _I nt _Ser v_Outbound

_XBTO



MTEClass XI _Appl _Syst _Send_XBTS



MTEClass XI _Appl _Syst _Recei ve _XBTR



MTEClass XI _I nt_ Serv_ Acknowl edgmnet _XBTB



MTEClass XI _I nt_Serv_Lar ge_XBTL

Exactly-Once Processing Queues Virtual



MTEClass XI _I nt _Serv_I nbound_XBQI

R3System <ExchangeI nf r ast r uct ure

_Syst ems>


MTEClass XI _I nt _Ser v_Outbound _XBQO



MTEClass XI _Appl _Syst _Send_XBQS



MTEClass XI _Appl _Syst _Recei ve _XBQR

R3System <ExchangeI nf r ast r uct ure

_Syst ems>


MTEClass XI _I nt_ Serv _Acknowl edgmnet _XBQB




© 2007 SAP AG

22


After creating all nodes, click the Save button and enter SAP Catalog Content Management as

name of the monitor.

© 2007 SAP AG

23

Monitoring TREX 7.0

Relevant for

SRM 5.0

Prerequisites

In a TREX 7.0 installation all files and directories that you require for correct operation of CCMS andGRMG are available on your host after the installation: The CCMS agent SAPCCMSR, and the library

DSRLI B (name extensions depend on the platform). These files are located in the directory

<TREX_DI R>/ exe.

Setup of Monitoring

The following monitoring functions are available:

Parameter Reporting

Monitoring Availability (Heartbeat/GRMG)

Monitoring Log Files

Monitoring Processes

To configure the CCMS monitoring functions for TREX, you have to configure the parameter reportingfirst. Configuring the parameter reporting is a prerequisite for configuring the monitoring of availability(heartbeat/GRMG), log files and processes. After configuring the parameter reporting, you configurethe monitoring of availability (heartbeat/GRMG), log files and processes by means of a Pythons script.

Parameter Repor ting:

To configure the parameter reporting perform the following steps:

1. Run a script to set the correct environment variables:

a.) Log on to the TREX host with the <sapsid>adm user.

b.) Navigate to the TREX installation directory

c.) Execute script TREXSettings.bat (Windows) or

TREXSettings.sh (Unix)

2. Register the CCMS agent with the central monitoring system (CEN)

sapccmsr pf=<full_path_to_instance_profile> -j2ee –R

Only Windows:

During the registration dialog you will be asked for the startup of the service. Choose manualfor the startup type. This query only appears on Windows.

Disable the Startup Type of the service of the CCMS agent in the Windows Administrative Tool

Start Settings Control Panel Administrative tools Service Choose the service of the

CCMS agent with the name SAPCCMSR. and single-click the secondary

(right) mouse button Properties General Startup Type: Disable.

3. Change the TREX start profile START_TRX_<host >.

You can find the TREX start profile for your TREX installation under \ usr \ sap\ <SAPSI D>\ SYS\ prof i l e ( on UNIX / usr / sap/ <SAPSI D>/ prof i l e) .

© 2007 SAP AG

24

a.) On UNIX:

Change the following sections of the TREX start profile:

Before the change:

SETENV_<nr > = LD_LI BRARY_PATH=$( DIR_LIBRARY) : %( LD_LI BRARY_PATH)

SETENV_<nr > = SHLI B_PATH=$( DIR_LIBRARY) : %( SHLI B_PATH)

SETENV_<nr > = LI BPATH=$( DIR_LIBRARY) : %( LI BPATH)

After the change:

SETENV_<nr > = LD_LI BRARY_PATH=$( DIR_EXECUTABLE) : %( LD_LI BRARY_PATH)

SETENV_<nr > = SHLI B_PATH=$( DIR_ EXECUTABLE) : %( SHLI B_PATH)

SETENV_<nr >= LI BPATH=$( DIR_ EXECUTABLE) : %( LI BPATH)

Insert the following entry in the TREX start profile:

#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

# St ar t CCMS Agent

#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

TREX/ NameSer ver / Por t =3$( SAPSYSTEM) 01

_CCMS = $(DI R_EXECUTABLE) / sapccmsr $(FT_EXE)

Star t _Pr ogram_<number> = l ocal $( _CCMS) pf =$(_PF) - j 2ee –DCCMS - nodaemon

Choose the next free number for the value <number >in St ar t _Pr ogram_<number>.

Note: You have only to specify the parameter TREX/ NameServer / Por t =3$( SAPSYSTEM) 01 for

the TREX versions 7. 0. 08 and TREX 7. 0. 24 versions. The file TREX_DI R>/ exe/ doc/ TREXVersi on. ht ml indicates the current TREX version.

b.) On Windows:

Insert the following entry in the TREX start profile:

#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

# St ar t CCMS Agent

#- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

_CCMS = $(DI R_EXECUTABLE) \ sapccmsr $(FT_EXE)

Star t _Pr ogr am_<number > = l ocal $( _CCMS) pf =$(_PF) - j 2ee - DCCMS

Choose the next free number for the value <number >in St ar t _Pr ogram_<number>.

4. Only on UNIX: Change TREX instance profile <SAPSI D>_TRX_<host >.

You can find the TREX instance profile for your TREX installation under

/ usr / sap/ <SAPSI D>/ pr of i l e) .

Insert the following entry at the end of the file the TREX instance profile:

TREX/ NameServer / Por t =3$( SAPSYSTEM) 01

© 2007 SAP AG

25

Note: You have only to specify the parameter TREX/ NameSer ver / Por t =3$( SAPSYSTEM) 01 for

the TREX versions 7. 0. 08 and TREX 7. 0. 24 versions. The file TREX_DI R>/ exe/ doc/ TREXVersi on. html indicates the current TREX version.

5. Restart the TREX instance for the new settings in the TREX start profile and instance profile to

take effect.

On Windows, you use the SAP Management console to start and stop TREX instances.

On UNIX, you use the shell scripts startsap and stopsap to start and stop TREX instances.

After performing the steps above TREX monitoring data should be sent to the CCMS of the monitoringsystem. Call transaction RZ20 in the monitoring system and navigate to monitor set S AP CCMSMonitors for Optional Components. Double-click the entry TREX and verify that monitoring data areavailable.

Avai lab il it y Moni to ring of TREX:

You can use the Generic Request and Message Generator (GRMG) to monitor the availability(heartbeat/GRMG) of TREX components. The SAP system (CCMS) uses an HTTP request to send anXML file defined for GRMG to one of the TREX GRMG servers that runs on the TREX host. The TREXGRMG server analyzes the XML file and starts the relevant scenario text to check the availability of theindividual TREX server on the selected TREX host.

To configure this monitoring function, perform the following steps:

1. Execute a python script

a.) Log on the TREX host as administrator (or root user on UNIX)

b.) Execute script TREXSettings.bat (Windows) or TREXSettings.sh (UNIX) in the

TREX installation directory

c.) Go to directory <TREX_DI R>/ exe/ CCMS and execute the following command:

python ccms_config.py --grmg

2. Upload the XML customizing file in transaction GRMG

a.) Start transaction GRMG in the monitoring system

b.) Choose Upload/Download Upload a scenario to upload the XML customizing file

GRMG_conf i g. xml . This file was created during the execution of the python script and can

be found in the following directory:

On Windows:<di sk_dr i ve>: \ usr \ sap\ pr f cl og\ grmg

On UNIX: / usr / sap/ prf cl og/ grmg

c.) After uploading the file choose Upload/Download Poll agents for new scenarios.

d.) In the list GRMG Availability Monitoring Scenarios select the corresponding TREX scenarioand choose Start/Stop Start scenarios.

© 2007 SAP AG

26

Note: This upload of the TREX scenario will only work if the SAPCCMSR agent is running and hasbeen registered previously.

Log File Monitoring of TREX:

Most of the TREX server services write status respectively error and warning messages in log-files.You can monitor the content of these log-files in the CCMS of the central monitoring system.



a.) Log on the TREX host as administrator (or root user on Unix)

b.) Execute script TREXSettings.bat (Windows) or TREXSettings.sh (UNIX) in theTREX installation directory

c.) Go to directory <TREX_DIR>/exe/CCMS and execute the following command:

python ccms_config.py --logmon

Process Monitoring of TREX:

To monitor whether all server processes are running (simply whether the server tasks are existing) it ispossible to use the process monitoring functionality of the SAPOSCOL. You only need to define whichprocesses should be monitored (the name of the processes). Afterwards in the CCMS of the

monitoring system more information concerning the processes is available.



a.) Log on the TREX host as administrator (or root user on UNIX)

b.) Execute script TREXSettings.bat (Windows) or TREXSettings.sh (Unix) in the TREX

installation directory

c.) Go to directory <TREX_DIR>/exe/CCMS and execute the following command:

python ccms_config.py --procmon

© 2007 SAP AG

27

CCMS Configuration

After activating the TREX monitoring features the TREX monitoring nodes located in the centralmonitoring system in transaction RZ20 SAP CCMS Monitors for Optional Components TREXshould be mapped to the SRM monitoring tree. To do this, perform the following steps:

1. Log on to the monitoring R/3 system, and call transaction RZ20. Choose Extras Activate

maintenance function

2. Set the cursor on the tree element SRM 4.0 and click the button Create.


4. In the dialog box, choose Virtual node and choose Continue.

5. Enter TREX Configuration as name of the node.




9. In the R3System field, enter the name of the TREX system or the name of the system groupTREX_Systems.


11. In the R3System field, the name of the TREX system is already pre-filled. In the field MTEClass,enter the TREX Applications. Choose Continue.

To include the TREX Availability monitoring, the TREX log file monitoring as well as the TREXprocess monitoring into the monitoring tree create the following three virtual nodes:

- TREX Process Monitoring

- TREX Log Files- TREX Server Heartbeat

Afterwards refer to the table below and create the corresponding rule nodes following the sameprocedure as described above.

Node Type Parameter Value

TREX Configuration Virtual

CCMS_DEFI NE_R3_SYSTEMS Rule R3System <TREX_SYSTEMS>

R3System <TREX_SYSTEMS>CCMS_GET_MTE_ BY_CLASS Rule

MTEClass TREX Appl i cat i onsTREX Process Monitoring Virtual



MTEClass TREX_PROC

TREX Log Files Virtual



MTEClass CcmsFi l eMoni t or i ng

TREX Server Heartbeat Virtual

© 2007 SAP AG

28


MTEClass GRMG_<scenname>


After creating all nodes, click the Save button and enter TREX 7.0 as name of the monitor.

© 2007 SAP AG

Monitoring Live Auction Cockpit 2.0 or 5.0

The Live Auction Cockpit runs on SAP Web Application Server (Java) 6.40 (LAC 2.0) respectively SAPWeb Application Server (Java) 7.0 (LAC 5.0) so the main focus of monitoring this component is the

monitoring of the SAP J2EE Engine.Besides the SAP J2EE Engine, the availability of the SAP LACWPS component can be monitoredusing the GRMG technology of the CCMS.

Relevant for

SRM 4.0 and SRM 5.0

Monitoring the J2EE Engine

Regis tering the SAPCCMSR Agent

The monitoring data for the J2EE Engine is transferred to the central monitoring system (CEN) usingthe CCMS agent SAPCCMSR. The agent is part of the installation package of the Engine. You onlyneed to register the agent once for each Java system with CEN and to start the agent.

Basically there are two deployment options of the Live Auction Cockpit in the SRM environment.

1. The LAC is running on the SRM server itself. (Double-stack installation of the SRM server)

2. The LAC is running on a SAP J2EE Engine separated from the SRM server. (Standalone Javasystem for LAC)

In the case of a double-stack system, you need to register the agent with two systems: primarily withthe local ABAP system and secondarily with CEN. You only need to register and start the agent onceper system.

Step-by-Step description:

1. Log on to the host of a J2EE Engine of the system as <SID>adm.

2. Copy the start file CSMCONF in the following directory:

Windows: [drive]:\ usr \ sap\ ccms\ <SysI D>_\ sapccmsr

UNIX: / usr / sap/ ccms/ <SysI D>_/ sapccmsr

You can also save the start file to any directory that you can access from your local host. In this case,however, you need to specify, during the registration of the agent, where you saved the file. To do this,choose the Change …button in the Monitoring service of the Visual Administrator (see below), andspecify the path of the start file. The file is then automatically copied to the above directory.

3. Start the Visual Administrator by calling the start script go (UNIX) or go.bat (Microsoft Windows),

and log on with your user as the J2EE Engine administrator.

4. In the navigation bar, choose Cluster <SysID> Dispatcher Services Monitoring, andchoose the CCMS Agent Configuration tab page.

5. The access data for both users required in CEN (Administration user and CSMREG user) isdetermined from the start file and displayed in the corresponding fields.

6. Enter the passwords of the CEN Administration User and the CEN CSMREG User in the Passwordcolumn.

7. In case of a double-stack installation additionally specify the access data of these users for the local ABAP system by making all of the entries for the Local Administration User and Local CSMREG User

rows.

© 2007 SAP AG

30

8. If necessary, you can use the Information button to answer the following questions:

• Is the instance profile of the instance to be monitored valid? • Is the CSMCONF start file to be used valid?

• What is the version of the CCMS agent SAPCCMSR?

9. Choose the Register button. The system displays the registration log; errors are highlighted in red.

10. Under UNIX, the agent is automatically started by the start sap script when you start the J2EE

Engine. Under Microsoft Windows, you need to start the associated service (which was created duringthe installation of the J2EE Engine) yourself.

To do this, on the Microsoft Windows host on which the agent is running, choose Start Settings

Control Panel Administrative Tools Services, and choose the service SAPCCMSR.<InstanceNo.> by double-clicking it. Set the Start Type to Automatic, and choose Start.

11. To check whether the agent was successfully registered with CEN, call transaction RZ21 in CEN,select the Agents for Remote Systems radio button, and choose Display Overview. The agent that youhave just registered is displayed in the list in the line SAPCCMSR.<host name>.<inst. no.>.

12. Additionally in case of a double-stack installation: To check whether the agent was successfullyregistered with the local ABAP system, call transaction RZ21 in the local ABAP system, select the Agents for Local System radio button, and choose Display Overview. The agent that you have justregistered is displayed in the list, in the line SAPCCMSR.<hostname>.<inst. no.>.

13. To check whether the J2EE Engine was included in the system group J2EE_Systems, calltransaction RZ21, and choose Techn. Infrastructure Configure Central System Maintain SystemGroups. The system ID of the J2EE Engine should be displayed in the tree System Groups for the Alert Monitor J2EE_Systems.

CCMS Configuration

If the registration of the CCMS agent was successful monitoring data for the J2EE Engine will beavailable in the CCMS of the central monitoring system. To display this data, call transaction RZ20,and choose Monito,r set SAP J2EE Monitor Templates Monitor Engines. If data is beingtransferred, there will be a sub-tree <SID> in the monitor.

Next, map the J2EE monitoring data to the SRM tree:



3. Choose Virtual node and enter J 2EE Engi ne on <host name>as node name



6. In the Rule field, enter CCMS_DEFINE_R3_SYSTEMS, then choose Continue.

7. In the R3System field, enter the name of the J2EE system or the name of the system groupJ2EE_Systems.


9. In the R3System field, the name of the J2EE system or the name of system group J2EE_Systemsis already pre-filled. In the field MTEClass, enter the J2EE_PROC. Choose Continue.

© 2007 SAP AG

31

After creating all nodes, click the Save button and enter Live Auction Cockpit Monitor as

name of the monitor.

Avai lability Monitoring of LACWPSFor the availability monitoring of the Live Auction Cockpit, the Generic Request and MonitoringGenerator (GRMG) is used. Basically a request is sent out of the CCMS of the monitoring system to aGRMG application, this application sends a response back to the CCMS and the response isdisplayed in a monitor in RZ20.

GRMG Customizing

Step-by-Step description:

1. Obtain the XML format customizing files for the GRMG monitoring scenarios of Live AuctionCockpit.

The GRMG customizing file is named l a_gr mg. xml for Live Auction Cockpit and it can be foundon the LAC host in directory <INSTDIR>:\usr\sap\<system name>\SYS\global\srmla\monitoring.

2. To adjust the customizing files, you need to edit the l a_gr mg. xml file using an XML editor or any

plain text editor. Change the URL specified in the <scenstarturl> element of the customizing

file to the correct hostname and port for your installation.

Example: <scenstarturl>http://<yourhostname>:<port>/srm/heartBeat </scenstarturl>

3. Upload the customizing file into the central monitoring system.

a. Log on to the monitoring system as a user with administrator rights.Make sure that you log on to the central application server. This is the server which offers theEnqueue service.

© 2007 SAP AG

32

b. Start transaction GRMG.

c. Click Upload a GRMG Scenario and select the GRMG customizing file. There will be noconfirmation message

4. After you have uploaded all of the customizing files, start the availability monitoring by clickingbutton Start all scenarios in transaction GRMG.

CCMS Configuration

After the GRMG customizing file has been uploaded and the GRMG scenario is started, availabilitymonitoring data is available in the CCMS of the central monitoring system. To display this data, calltransaction RZ20, and choose Monitor, set SAP CCMS Technical Expert Monitors Monitor AllMonitoring Contexts.

Find and expand the monitoring sub-tree which is named SRM Live Auction Scenario (or the valuespecified for the element <scendesc>in the XML customizing file). You should now see a further

sub-tree with the name Web Server of SRM Live Auction Scenario.

This tree should be mapped to the SRM tree:

1. Set the cursor on the monitor Live Auction Cockpit in monitor set SRM 4.0 and click Change.

2. Select Live Auction Cockpit Monitor and then choose Edit Create nodes.

3. Choose Virtual node and enter GRMG Monitors as node name




7. In the R3System field, enter the name of the J2EE system hosting the Live Auction application or the name of the system group J2EE_Systems.


9. In the R3System field, the name of the J2EE system or the name of system group J2EE_Systems

is already pre-filled. In the field MTEClass, enter the GRMG_<scenname>, whereas <scenname>should be replaced by the scenario name used in the GRMG customizing file. Choose Continue.

© 2007 SAP AG

Monitoring Business Connector 4.6 or 4.7

Relevant for

SRM 4.0 and SRM 5.0

Introduction

Now you can monitor the SAP Business Connector (=SAP BC) environment by using the CCMS agenttechnology to collect SAP BC performance and configuration values.

The values are sent on a regular basis via the agent to the R/3 system. The data is then available tothe CCMS monitors inside the R/3 system using transaction RZ20. CCMS enables you to track alerts,view the current status of the SAP BC environment and read configuration data of each SAP BCinstance on demand.

Furthermore, you can collect data for each reported value and automate actions that should betriggered after an alert has occurred. In addition to the option of monitoring the SAP BC values, you

can collect the operating-system-specific data (such as overall CPU consumption, memoryconsumption, or paging activity) via the agent technology. You can then use SAP BC Administration toget additional details and, if necessary, correct any errors.

To transmit the data, two "monitor drivers" can be used for reporting this data into CCMS.

A driver using the new " Agent" technology, which can be used since 4.6B. The Agent collects alldata locally and is called by the central system only once in a while, to update all values in onesingle call. In this paper we shall only introduce the Agent in the installation section.

The RFCMonitorDriver , a driver using direct RFCs, which can be used from CCMS release 4.5Bon. The RFCMonitorDriver works with older systems, which do not yet support the Agent. It hasthe disadvantage that for every reported value a call to the central system has to be executed.

In this paper we will show you an exemplary installation of the Agent installation in a SAP BC 4.6.xenvironment. The CCMS system is an R/3 basis release 4.6C.

Installation

To use the SAPMonitoring Package, the Business Connector has to run , minimum, under Java 1.3.

Under Windows, this is the default JVM, which will automatically be used unless you havechanged the JAVA_ROOT variable in server . bat .

You need to access the SAP web page http://service.sap.com/sbc-download and get the newestversion of the monitoring tool and its OS subcomponent.

To install the SAPMonitoring Package, you need the following files from the software update sectionthat can be downloaded from the URL mentioned above:

SAPMoni t or i ng. zi p (the general functionality for all platforms)

SAPMoni t or i ng_Li bs_<os>. zi p (the native libraries for the different operating systems)

(Currently BC Monitoring is available for the following platforms: NT, Linux, HP_UX32, HP_UX64,Solaris32, Solaris64, AIX32, AIX64. For Windows2000 use "NT".)

SAPMoni tor i ng_Li bs_ <os>. zi p also contains the sapccsmr executable. It needs to be installed

on the host machine of the SAP BC.

In the following <sapbc>refers to the installation directory of the Business Connector, for example

C: \ sapbc40\ Server .

The SAPBCMonitoringGuide is contained in the SAPMoni t or i ng. zi p file.

http://service.sap.com/sbc-download

© 2007 SAP AG

34

Check the version of PDH. dl l in C: \ WI NNT\ syst em32 (Right-mouseclick Properties Version).

If the version is older than 4.0 or if there is no PDH. dl l in system32, copy the one from

<sapbc>\ packages\ SAPMoni t or i ng\ code\ l i bs\ nt i nt el into C: \ WI NNT\ syst em32.

General Steps

1. Copy the files SAPMoni t or i ng. zi p and the corresponding version of SAPMoni t or i ng_Li bs_<os>. zi p into the directory <sapbc>\ r epl i cat e\ i nbound and start

the Server.

2. In the Business Connector Administrator screen go to Packages Management InstallInbound Release and install the SAPMoni t or i ng. zi p Package. The activation option needs to

be turned on.

3. Next install the SAPMoni t or i ng_Li bs_<os>. zi p Package. This installs the necessary native

libraries for the respective platform. After this you have to restart the Server to update theCLASSPATH.

Windows 2000

Check, whether the CCMS Agent sapccmsr is already installed on the machine. You can do this by

going to Start Settings Control Panel Administrative Tools Services and check whether a

service named SAPCCMSR. 99 exists and is started.

If it is not installed follow the procedure as described in section CCMS Agent Installation of this BestPractice.

If the agent is installed and you want to use the installed Agent (and the CCMS, it is reporting to), thenproceed with paragraph Setting up SAPCCMSR for the data transfer and chose Central MonitoringSystem=None in step two of that section.

Only if you want the SAP BC to use its own Agent, you have to uninstall the existing agent now withsapccmsr -U.

Be aware that different versions of sapccmsr . exe on the same machine can lead to a "Dr.Watson

access violation".




© 2007 SAP AG

35

Initial Setup

To check the installation was successful please go to:

Packages Management

There you should find an entry SAPMonitoring. The package should be enabled and loaded. The

checkmark should be green in both cases. You should then go to: Adapters SAP Monitoring Remote Monitoring

in the administrator screen. You also start the monitoring of the SAP BC by using this path. Thescreenshot below shows an installation that is correctly implemented.

If Uou are Not Already Using SAPCCMSR

(If the SAPCCMSR is running then continue with Setting up the SAPCCMSR for the data transfer .)

If you do not have a SAPCCMSR running, you need to configure it using the SAP BC. You do this byusing following path:

Adapters SAP SAP Servers Add SAP Server

You then need to enter the information for your CCMS-server.




© 2007 SAP AG

36

Setting up the SAPCCMSR for the Data Transfer

In the original Admin window go to Settings Resources Edit Resource Settings and increase thenumber of threads of the Scheduler Thread Pool by at least eight (if you are also using the Scheduler for other things).

Go to Adapters SAP Monitoring Remote Monitoring Setup General Settings for RemoteMonitoring Edit General Settings for Remote Monitoring.




© 2007 SAP AG

37

In the field Choose SAP Server to use as Central Monitoring System , you can select:

None, if the agent SAPCCMSR is already installed on the machine and is sending information to aparticular CCMS, or if you want to use a third party monitor instead of CCMS.For example if there is more than one SAP-BC instance on the same machine, you could use the Agent to monitor all of them, by selecting the Central System only in the first of these instancesand None in all the others.

A system with release greater than 4.6A. You should have already the SAPCCMSR.

1. In the field Choose Monitor Driver select the AgentMonitorDriver if the SAPCCMSR agent is to beused for reporting to the Central Monitoring System (recommended), or select theRFCMonitorDriver if direct RFC is to be used.

2. Then select the properties of the SAP-BC you want to monitor. (The BC Supplies you with someuseful default suggestions here.) See section 4 in the SAP BC Monitoring Guide for a detailedexplanation of the different properties.

You can leave the new driver entry blank.

3. Next go back to the Monitoring screen and click Initialize or update Monitoring Tree.

© 2007 SAP AG

38

This should generate the nodes of the tree in the CCMS Monitor. You can view the tree by goingto transaction RZ20 (in the Central Monitoring System).

If you had chosen the AgentMonitorDriver in step two and the installation of sapccmsr failed,

you should get an error message when the "Initialize or update Monitoring Tree" completes. In

any case you should also see a list of log files from the sapccmsr installation, which show you

detailed success or error messages.

To start monitoring, click the red button Monitoring Started?.

You also need to start the Business Connector again if you modify it (by for exampledelete/create server, change settings and so on).

CCMS Configuration

The next steps you need to do are in the CCMS of monitoring R/3 system.

1. Call the CCMS transaction RZ20. Choose Extras Activate maintenance function.


3. Click <<<New Monitor>>> and then click Create.

4. Select Rule node in the next dialog box.

5. In the next dialog box, select for rule: CCMS_GET_MTE_BY_CLASS

© 2007 SAP AG

39

6. Next, choose for R3System: <CURRENT> and for MTEClass: BusconContext.

7. Click the Save button and enter a name with which you can identify the SAP BC as the name of the monitor.

After configuring the CCMS in the R/3-monitoring system it is possible to map this data to the Solution

Manager and establish an alert-monitoring by setting appropriate thresholds and triggers. The BestPractice Central System Monitoring for mySAP.com shows how to perform the mapping.




© 2007 SAP AG

40

Set Up CCMS

Now, after finishing the above steps, the CCMS of the monitoring R/3 system is configured to display

the monitoring data of interest in the SRM components. You can use the CCMS tree (transactionRZ20) to check for potential problems.

However, you should use the Solution Manager for monitoring the SRM solution landscape. TheSolution Manager is able to show alerts of the system components as well as alerts of the Businessprocess steps. to make use of to Solution Manager, you need to configure it appropriately. It is beyondthe scope of the current Best Practice document to outline these steps in details. Refer to the BestPractice document Central System Monitoring for mySAP.com for more details.



Best Practice: SAP SRM 4.0 / 5.0 System Landscape Monitoring 41

Further Information

Background Information and References

Details of the CCMS agent technology and system monitoring in general are found in the SAPNet. Seethe CCMS Agent Description document. See also http://service.sap.com/monitoring.

Feedback and Questions

Send any feedback by formulating an SAP customer message to component SV-GST-SMC. You cando this at http://service.sap.com/message.

© Copyright 2007 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, 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 hereinas 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 notintended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please notethat 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 intentor 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.



http://service.sap.com/message




SRM LandscapeMonitor

Documents

Transcript of SRM LandscapeMonitor