CCMS Agent Installation NW 7.1 Onwards

CCMS setup for Experts
Installing/Registering the CCMS Agents

for Experts
By
Anupam Giri
SAP Basis Consultant
Version: 0.1
Page 1 of 23
CCMS configuration for Experts-CAB
DOCUMENT CONTROL
Document Information
Deliverable Name
Installing/Registering the CCMS Agents for Experts
Owner
Anupam Giri
Author(s)
Anupam Giri
Stream
Technical stream
Status
Draft
Location
share-point ( to be updated )
Document Revision History

Version
No.
Status
Date
Author(s)
Change Log
0.1
Initial
Draft
29/04/2013
Anupam
Initial Draft
Reviewers
Name
Position
Date
Remarks
Approvers
Name
Version: 0.1
Page 2 of 23
Position
Date
Remarks
Table of Contents
Contents
Infrastructure of the SAP NetWeaver Management Agents.................4
Purpose............................................................................................................4
Integration.......................................................................................................5
Constraints.......................................................................................................5
Host Agent:............................................................................................................. 6
Monitoring Hosts with SAPHostControl and saphostexec........................................6
Use.........................................................................................................................................................................6
Prerequisites..........................................................................................................................................................7
Instance Agent:....................................................................................................... 7
Administration/Monitoring of SAP Components with sapstartsrv............................7
Use.........................................................................................................................................................................7
STEP 1 - Registering SAP NetWeaver Components and Hosts in CEN........................................8

Use.........................................................................................................................................................................8
Prerequisites..........................................................................................................................................................8
Procedure (in CEN System)................................................................................................................................10
Technical Background.........................................................................................................................................12
Result...................................................................................................................................................................13
STEP 2 - Creating and Changing Monitors........................................................................13

Use.......................................................................................................................................................................13
Prerequisites........................................................................................................................................................14
Procedure.............................................................................................................................................................14
Example...............................................................................................................................................................16
1.
Defining Monitors with the DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Rules 16

Monitor Definition..............................................................................................................................................17
Monitor Display..................................................................................................................................................18
2.
Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS............18

Example 1: Monitor Definition...........................................................................................................................19
Example 1: Monitor Display...............................................................................................................................19
Example 2: Monitor Definition...........................................................................................................................20
3.
Defining Monitors with the Rule GET_MTE_BY_CLASS_AS_VIRTUAL................21

Monitor Definition..............................................................................................................................................22
Monitor Display..................................................................................................................................................23
Version: 0.1
Page 3 of 23
Introduction:
Installing/Registering the CCMS Agents for Experts
CCMS agents are no longer required for purely SAP NetWeaver 7.1 landscapes; their
functions are performed by NetWeaver Management Agents.
Infrastructure of the SAP NetWeaver Management Agents
Purpose
The SAP NetWeaver management agents are used to administer and monitor SAP
NetWeaver components. They are automatically installed and started during the
installation of any SAP NetWeaver components as of release SAP NetWeaver 7.0
EhP2. There are two types of agents, depending on the associated component:
Component
Host
AS ABAP
Type
Host agent; one host agent runs for each monitored hosts
(including hosts on which one or more instance agent is running)
Instance agent; an instance agent runs for each monitored
instance
AS Java
Dual-Stack
TREX
Version: 0.1
Page 4 of 23
The agents provide Web services that can be used by applications, including:
SAP Management Console (SAP MC) is a browser-based, platform-independent user interface with
which you can start, stop and monitor the status of systems and their instances.
In the monitoring infrastructure, once the relevant component is registered with the central monitoring
system (CEN), data is transferred to CEN
The host agent also controls these two executables:
Operating System Collector SAPOSCOL
sapacosprep; an executable of the Adaptive Computing Infrastructure
Integration
As of this release, the SAP NetWeaver management agents replace the CCMS agents.
Constraints
You now only require the classic CCMS agents in the following two cases:
You want to monitor any systems with a central monitoring system (CEN) with a release older than SAP
NetWeaver 7.0 EhP 1. More information: SAP Note 1368389.
Note :If you are operating a CEN with this old status, note also that you no longer require a CCMS agent
SAPCCMSR j2ee for a monitored dual-stack system as of SAP NetWeaver 7.0 EhP2. This is because
Version: 0.1
Page 5 of 23
the ABAP and Java stacks share the same monitoring segment as of SAP NetWeaver 7.0 EhP2.
Therefore, for dual-stack systems of this type as of SAP NetWeaver 7.0 EhP2, install only the CCMS
agent SAPCCM4X. However, this is mandatory, not optional.
You want to monitor a system with a release up to SAP NetWeaver 7.0 EhP1. In this case, irrespective
of the release of the CEN, you require the classic CCMS agents for this monitored system.
Host Agent:
Monitoring Hosts with SAPHostControl and saphostexec
Use
The two programs below run on every host with SAP NetWeaver components as of release 7.0
EhP2 and on every host that is monitored by a central system with this release:
SAPHostControl
SAPHostControl is the executable sapstartsrv running in host mode. It is therefore not responsible for an
SAP instance (see Administration/Monitoring of SAP Components with sapstartsrv), but for any host that
is to be centrally monitored.
Whether sapstartsrv runs in host or in instance mode is determined by the profile that is transferred
when the executable is started. In instance mode, it runs with the instance profile of the corresponding
instance, in host mode with its own profile, which can contain the two following profile parameters:
SAPSystem = 99
SAPSystemName = SAP
It always runs together with the executable saphostexec (see below); both are always started during the
startup of the host.
NOTE
On Microsoft Windows hosts, the automatic start is ensured by the

service SAPHostControl, which runs under user SAPadm. On UNIX hosts, the
automatic start is ensured by the executable sapstartsrv being started by
the start scrip sapinit.
SAPHostControl contains the functionality of the previous CCMS agent
SAPCCMSR, that is, the agent that monitors hosts
SAPHostExec
saphostexecis an executable that runs under root (UNIX) or the Local System Account (Microsoft
Windows). It controls all of the functions for which a special user of this type are required, such as the
Version: 0.1
Page 6 of 23
operating system collector saposcol and sapacosprep. It is connected to sapstartsrv in host mode (see
above) using a local socket, which ensures quick and secure communication and is also started during
the startup of the host.
Note :
On Microsoft Windows hosts, the automatic start is ensured by a

service called SAPHostExec, on UNIX hosts, the automatic start is ensured
by the executable saphostexec being started by the start script sapinit.
sapacosprep is an executable of the Adaptive Computing
Infrastructure that, for example, performs the addition of file systems and
general operating system-side preparations for being able to monitor SAP
instances.
Prerequisites
The listed executables and services are automatically installed and started during the installation
of SAP NetWeaver instances. In this case, you no longer need to perform any steps yourself.
In the case of hosts with no SAP components that you want to monitor with a central system as of
SAP NetWeaver 7.0 EhP1, you need to download and install the specified executables and
services yourself.
Instance Agent:
Administration/Monitoring of SAP Components with
sapstartsrv
Use
sapstartsrv is available for administering and monitoring any hosts and SAP instances. It has a
variety of SOAP interfaces, with which the service can be used by remote clients, and is known as
an instance agent. Clients for this service include:
The platform-independent, browser-based SAP Management Console for administration and monitoring
of SAP systems
Under Microsoft Windows, the SAP Systems Manager snap-in for the SAP Microsoft Management
Console
Version: 0.1
Page 7 of 23
sapstartsrv is automatically installed during the installation of the relevant instance. A setting is
also made during the installation that ensures that sapstartsrv is automatically started when the
host is started up (see below). Manual installation is not required. A sapstartsrv process is
automatically running on the relevant host for every SAP instance (ABAP, Java, double-stack, or
TREX).
Platform
Start of sapstartsrv
Microsoft Windows
During the installation of the instance, a service called SAP<SysID>_<instance

number> is created under the user SAPService<SysID>. This service is automatically
started when the corresponding host is started. The service starts the executable
sapstartsrv.
UNIX
During the installation of the instance, the start script sapinit is installed. This script, in
turn, starts sapstartsrv.
A profile file is specified when sapstartsrv is started. If sapstartsrv administers and monitors an
instance, the profile is the instance profile of the corresponding instance. sapstartsrv can also run
in host mode, that is, the service is not used to administer and monitor an instance, but rather to
monitor a host
Note :
sapstartsrv also contains the functions of the previous CCMS agents SAPCCM4X and
SAPCCMSR j2ee, that is, the agents that monitor ABAP and Java instances
STEP 1 - Registering SAP NetWeaver Components and Hosts in CEN
Use
To centrally monitor remote SAP NetWeaver components or any hosts, you need to register the
corresponding component in CEN. You can do this in two ways:
If you are using the SAP NetWeaver Administrator (NWA), it is recommend that you configure the
monitored components using the Configuration Wizard.
If you are using the Alert Monitor, register the desired component in the configuration transaction for the
Alert Monitor (transaction RZ21). This procedure is described here.
Version: 0.1
Page 8 of 23
Prerequisites
There is a CSMREG user in CEN. To create this user, go to Tcode RZ21 -> Technical infrastructure
-> Configure central system - > Create CSMREG user. You need to create this user both in satellite
as well as CEN system (if not present) see screenshots below.
The message server details of CEN system has to be updated in the services file (in OS
level) of Satellite system and vice-versa
There is also a CSMREG user on the ABAP or dual-stack system to be monitored. Create the same
using RZ21 mentioned in 1st step above.
If you want to register a host without an SAP NetWeaver component in CEN, install the SAP
NetWeaver management agents on that host
The Java or TREX systems to be monitored have a release status of at least SAP NetWeaver 7.0
EhP2.
Version: 0.1
Page 9 of 23
Version: 0.1
Page 10 of 23
Procedure (in CEN System)

1. To monitor an additional system or host, call transaction RZ21.
2. Choose Technical Infrastructure Configure Central System Create Remote Monitoring
Entry.
3. Choose which component type you want to register in CEN. See figure below
4. In the group box CSMREG User of the Central System, enter the password for the
CSMREG user in CEN.
5. Depending on the type of component to be monitored, enter the following
system and connection data for the component to be monitored:
Type
Input Data
More Information
ABAP
System ID
The connection to the monitored system is tested
Dual-Stack
Message server
with user CSRMREG when you save (or if you
Logon Group; the SPACE
choose the
group, which always exists, is
Connections to Remote Component) group box.
set as the default
The monitored component is only added and the
Password of CSMREG on the
RFC destinations (see below) are only created if
monitored system
the test is performed successfully.
Java
System ID
Message server
HTTP Port of the Message
(Test) button in the RFC
Server
TREX
Host
System ID
You require the user at operating system level to
Server
execute a configuration script on the TREX host
Instance number
Host name
Register only hosts without SAP NetWeaver

components here. Ensure that the SAP
NetWeaver management agents are installed on
the host
6. In the Operating System User on the Host of the Monitored System group box, enter
the password of an administration user at operating system level. For an SAP
NetWeaver component, this is the user <SysID>adm., for a host, it is sapadm.You
require this authentication since the Web service call for registering a
component in CEN is protected.
7. Save your entries.
Version: 0.1
Page 11 of 23
Technical
Background
To monitor an
ABAP or dualstack system
centrally, the
system creates
two RFC
destinations in
that system:
<SysID>_RZ20_COLLECT reads monitoring data for the monitored system;

the connection uses the CSMREG user.
<SysID>_RZ20_ANALYZE is the destination with which you as an
administrator can execute an analysis method in the monitored system. The
destination is created without a user, meaning that you need to authenticate
yourself in the monitored system.
A Customizing destination between the CEN and the relevant Java Engine is required, so that you can
change the properties of the monitoring data of the Java Engine (such as threshold values) from the
Alert Monitor. This is automatically created under the name SAP.CCMS.J2EE.<SysID> when adding
a Java system, where <SysID> is the system ID of the Java system to be monitored.
Version: 0.1
Page 12 of 23
Result
You can now monitor the corresponding with the Alert Monitor or with the NWA. If you are using
rule-based monitors for monitoring, the new system is automatically added to your monitors.
Otherwise, add the new system to your monitors or create a new monitor
STEP 2 - Creating and Changing Monitors
Use
You can quickly and easily create your own monitors that meet your own specific requirements. If,
for example, you want to monitor the relationship between your CPUs, operating system paging,
and the dialog response time of your SAP systems, you can create an alert monitor that contains
only these monitoring tree elements (MTEs). You can decide whether this monitor covers one or
more systems.
To be able to create a monitor, first create a tree structure. You have the following options for the
individual nodes:
Static MTE Selection

You can explicitly select MTEs for your monitor. Only the selected MTEs are added to the monitor, and
the selection of the MTEs is not updated.
Rule-Based MTE Selection

You can also use rule-based MTE selection (dynamic selection) to create your monitor. In this case,
the alert monitor includes all MTEs that fulfill a certain rule in your monitor. If the MTEs that meet this
rule change, the system automatically updates your monitor. In this way, your monitor is automatically
updated if a new system is added to the alert monitor. You can combine both static and rule-based MTE
selection in the same monitor.
Virtual MTEs
You can define virtual MTEs to structure your monitor. Virtual nodes are used as titles or labels in the
alert monitor. They have no function other than to group monitoring tree elements visually. For example,
you can create virtual MTEs as titles for different groups of real MTEs in your monitor.
Version: 0.1
Page 13 of 23
Prerequisites
To be able to create or change a monitor, you must first activate the maintenance functions.
Procedure
1. Choose CCMS Control/Monitoring Alert Monitor, or call transaction RZ20.
2. Choose Extras Activate Maintenance Functions.
3. Choose one of the functions from the table:

Function
Menu Path
Create monitor
Choose the monitor set in which you want to create the monitor; ensure that it is
); choose Monitor (set) Create (
a monitor set that you can modify (

Change monitor
).
Expand the monitor set and choose the monitor that you want to change.
Choose Monitor (set) Change (
).
You can also change a monitor that has already been started by choosing
Monitor Change (
).
4. The alert monitor displays the complete monitoring tree. The system displays
the name of the monitor in the top line of the tree. You can now either add MTEs
to your monitor or display the properties of existing MTEs. To do this, choose one
of the functions from the table:
Function
Procedure
Insert static MTE selection
Select the desired MTEs from the list of Selectable MTEs
. Only the selected
MTEs will be visible in the completed monitor. The system displays the list at
every point in the monitoring tree where you can insert statically created MTEs.
Version: 0.1
Page 14 of 23
Insert rule-based MTE
Choose the node under which you want to insert a rule-based node; choose
selection
Edit Create Node (
) and, on the Create Node screen, choose the Rule
Node radio button

Insert a virtual MTE
Choose the node under which you want to insert a virtual node; choose Edit
Create Node (
) and, on the Create Node screen, choose the Virtual Node
radio button. Enter a name for the node.

Change node
Select the relevant node; choose Edit Change Node (
). You can change
different properties, depending on the type of the node.

Display node
Select the relevant node; choose Edit Display Node (
). The system
displays different properties, depending on the type of the node.

Delete node
Select the relevant node; choose Edit Delete Node (
). The node is deleted,
along with its subnodes.
The following rules apply to the sequence of nodes in the monitoring tree:
The root node (top node) of a monitor is always a virtual node. Its
name is the name of the monitor.
You can create as many layers of virtual MTEs as you wish. A virtual
node can only be placed under a rule node or another virtual node in
the tree hierarchy.
Version: 0.1
Page 15 of 23
A rule node can only be placed under a virtual node or another rule
node in the tree hierarchy.
A static node can only be placed under a virtual node.
5. Save your monitor by choosing Monitor Definition Save or Generate Monitor (

). If you are creating a new monitor, the system prompts you to enter a name for
your monitor.
Result :
Once you double click on Virtual node AL08 Users Logged on It will show the
below screen
Example
The following sections contain examples of monitor definitions :
1. Defining Monitors with the DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Rules
2. Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS

3. Defining Monitors with the Rule GET_MTE_BY_CLASS_AS_VIRTUAL
1. Defining Monitors with the

DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Rules
You can use these two rules to quickly and simply create monitors:
From which systems is monitoring data to be displayed?
What MTE classes do the monitoring data to be displayed have?
Version: 0.1
Page 16 of 23
You can determine the MTE class of the desired data by calling a monitor that contains the desired
nodes, switching to the Technical View: Info on MTE, or by selecting the desired node and choosing
Properties.
Monitor Definition
The figure below shows a simple rule-based monitor definition using the above rule
Note the following for the CCMS_DEFINE_R3_SYSTEMS rule:
You usually use the rule as the root node of the monitor.
You define the systems to be displayed in the parameter R3System. You can enter the following values
when doing so:
Entry
Meaning
<CURRENT>
Local system
<ALL>
All systems that are known to the monitoring architecture as monitored systems
<any name>
System group; you can define a system group yourself that contains the desired
systems
In the display options for the rule, you should activate the indicator Display virtual summary nodes in the
monitor if, and only if, you want to display multiple systems. If you are only monitoring one system,
another level with the system name does not provide any new information, but rather makes the monitor
less clear.
Version: 0.1
Page 17 of 23
Note the following for the rule CCMS_GET_MTE_BY_CLASS:
If (as in this example) there is a CCMS_DEFINE_R3_SYSTEMS rule above this rule, the rule inherits
the system, otherwise, you usually define the systems yourself.
It is usually not necessary to select Display long MTE name in the display options. You should instead
select only the parts of the MTE name that are necessary to understand the monitor display. In this
example, this is the context (which specifies the instance for most nodes).
Monitor Display
If you choose Generate Monitor (
) for the above monitor definition, the following monitor is
generated:
2. Defining Monitors with the Rule

GET_MTE_BY_CLASS_AND_OPTIONS
Use this rule primarily in the following cases:
You want to display multiple MTE classes that have a common naming convention in the monitor,
especially if you do not yet have the names of all of the MTE classes to be displayed when you are
creating the monitor definition (see example 1).
Version: 0.1
Page 18 of 23
You want to restrict the search for MTE classes at runtime when creating the monitor to certain segment
types to improve performance or clarity (see example 2).
Example 1: Monitor Definition

The MTE classes to be displayed for the availability of the GRMG scenarios have the naming
convention GRMG_ScenAvail_<scenario name>. If you wanted to display the availability of all
scenarios, you would need to enter all MTE classes without this rule. However, the names of
these MTE classes are not currently available to you.
Example 1: Monitor Display

Version: 0.1
Page 19 of 23
) for this monitor definition, the following monitor is generated:
Example 2: Monitor Definition

In this case, you are using the options of the rule CCMS_GET_MTE_BY_CLASS_AND_OPTIONS.
Among other things, you can use the options OnlyAgent and NoAgent to define whether the MTE
class must be in an agent segment or must not be in an agent segment. The Java nodes, for
example, always belong to the monitoring segment of a SAPCCMSR CCMS agent (for more
options, see Rule MTEs: Rule Descriptions and Use).
Version: 0.1
Page 20 of 23
) for this monitor definition, the following monitor is generated:
3. Defining Monitors with the Rule

GET_MTE_BY_CLASS_AS_VIRTUAL
Always use the rule CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL together with the rule
CCMS_GET_MTE_BY_CLASS_UNDER_CLASS. You can use these two rules to display sections of
hierarchy trees without having to do without the hierarchical display.
For example, if you want to monitor the following operating system resources, which are to be
displayed structured by the monitored hosts:
CPU utilization (MTE class CPU_Utilization)
Paging-in rate (MTE class Page_In)
Paging-out rate (MTE class Page_Out)
These MTE classes are part of the operating system subtree (MTE class OperatingSystem). If you
create a monitor with the rule CCMS_GET_MTE_BY_CLASS with the MTE classes listed above, you
obtain all of the desired values, but in a flat hierarchy:
However, if you specify the superordinate MTE class OperatingSystem in the rule
CCMS_GET_MT_BY_CLASS, you obtain the desired hierarchy, but all other values in this subtree as
well as the desired values.
Use the rules CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL and

CCMS_GET_MTE_BY_CLASS_UNDER_CLASS instead.
Version: 0.1
Page 21 of 23
Monitor Definition
Keep in mind the following points when you use these rules:
Specify the MTE class of a subtree of which you only want to display a section in the rule
CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL. Typical examples of subtrees of this type are:
Instance (MTE class R3ApplicationServer)

Operating system data (MTE class OperatingSystem)
J2EE Engine (MTE class SAP_J2EE_Engine)
Corresponding subtrees are then displayed in the monitor as virtual nodes.
You specify the MTE class of the node that you want to display under the subtree defined above in the
ChildMTEClass parameter in the rule CCMS_GET_MTE_BY_CLASS_UNDER_CLASS. The rule adopts
the parameters MTEClass and R3System from the higher-level rule
CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL.
To display multiple MTE classes, simply create multiple
CCMS_GET_MTE_BY_CLASS_UNDER_CLASS rules under the
CCMS_GET_MTE_BY_CLASS_AS_VIRTUAL rule.
The Short Name is usually sufficient in the Display Options in

CCMS_GET_MTE_BY_CLASS_UNDER_CLASS, since the context is already displayed by the
superordinate rule.
Version: 0.1
Page 22 of 23
Monitor Display
) for the above monitor definition, the following monitor is
generated:
Version: 0.1
Page 23 of 23

CCMS Agent Installation NW 7.1 Onwards

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

CCMS Agent Installation NW 7.1 Onwards

Caricato da

Copyright:

Formati disponibili

CCMS setup for Experts

Installing/Registering the CCMS Agents

CCMS configuration for Experts-CAB

CCMS setup for Experts

Installing/Registering the CCMS Agents for Experts

Document Revision History

CCMS configuration for Experts-CAB

CCMS setup for Experts

STEP 1 - Registering SAP NetWeaver Components and Hosts in CEN........................................8

STEP 2 - Creating and Changing Monitors........................................................................13

Defining Monitors with the DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Rules 16

Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS............18

Defining Monitors with the Rule GET_MTE_BY_CLASS_AS_VIRTUAL................21

CCMS configuration for Experts-CAB

CCMS setup for Experts

Infrastructure of the SAP NetWeaver Management Agents

CCMS configuration for Experts-CAB

CCMS setup for Experts

system (CEN), data is transferred to CEN

The host agent also controls these two executables:

Operating System Collector SAPOSCOL

sapacosprep; an executable of the Adaptive Computing Infrastructure

CCMS configuration for Experts-CAB

CCMS setup for Experts

On Microsoft Windows hosts, the automatic start is ensured by the

CCMS configuration for Experts-CAB

CCMS setup for Experts

On Microsoft Windows hosts, the automatic start is ensured by a

CCMS configuration for Experts-CAB

CCMS setup for Experts

During the installation of the instance, a service called SAP<SysID>_<instance

STEP 1 - Registering SAP NetWeaver Components and Hosts in CEN

CCMS configuration for Experts-CAB

CCMS setup for Experts

CCMS configuration for Experts-CAB

CCMS setup for Experts

CCMS configuration for Experts-CAB

CCMS setup for Experts

Procedure (in CEN System)

The connection to the monitored system is tested

with user CSRMREG when you save (or if you

Logon Group; the SPACE

group, which always exists, is

Connections to Remote Component) group box.

set as the default

The monitored component is only added and the

Password of CSMREG on the

RFC destinations (see below) are only created if

the test is performed successfully.

HTTP Port of the Message

(Test) button in the RFC

You require the user at operating system level to

execute a configuration script on the TREX host

Register only hosts without SAP NetWeaver

CCMS configuration for Experts-CAB

CCMS setup for Experts

<SysID>_RZ20_COLLECT reads monitoring data for the monitored system;

CCMS configuration for Experts-CAB

CCMS setup for Experts

STEP 2 - Creating and Changing Monitors

Static MTE Selection

Rule-Based MTE Selection

CCMS configuration for Experts-CAB

CCMS setup for Experts