SAP Replication Server Monitoring

With Solution Manager 7.1

This document helps you to setup monitoring of SAP Replication Server with Solution Manager 7.1.
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

TABLE OF CONTENTS
PREREQUISITES .............................................................................................................................................. 3
SETUP SRS SERVER FOR MONITORING ..................................................................................................... 3
Steps to be performed on SRS Server .......................................................................................................... 3
SETUP SOLUTION MANAGER FOR SRS MONITORING .............................................................................. 3
Create SRS System in Solution Manager ...................................................................................................... 3
Create Technology type for SRS ....................................................................................................................... 3
Create System in LMDB .................................................................................................................................... 4
Managed System Configuration for SRS system ......................................................................................... 7
Custom script deployment for SRS Monitoring ......................................................................................... 10
Changes to commands.xml file ....................................................................................................................... 10
Maintain SRS Users ........................................................................................................................................ 11
Changes to SapAgentConfig.xml .................................................................................................................... 12
Create custom data providers ...................................................................................................................... 13
Generic SRS Collector..................................................................................................................................... 14
SRS Module Specific Data Collector – Sample Throughput Collector ............................................................ 15
Create custom system monitoring templates ............................................................................................ 16
Create Custom SRS Template ........................................................................................................................ 16
Create Custom Metric ...................................................................................................................................... 17
Server Availability Metric (Wily) ....................................................................................................................... 17
Performance Metric (Wily) ............................................................................................................................... 19
Setup System Monitoring for SRS ............................................................................................................... 20

2
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

PREREQUISITES
 Sybase SRS 15.5 or higher is installed
 Solution Manager 7.1 SP10 or higher
 SAP Diagnostic Agents 720 or higher is installed on all SRS Servers

SETUP SRS SERVER FOR MONITORING

Steps to be performed on SRS Server
 Unzip package file sap_srsmon-*-bin.zip attached to SAP note 2343655
 Copy the extracted sap_srsmon-*.jar to $SYBASE/srsmonitoring folder(create new directory if not
available) on the central SRS Server
 Rename sap_srsmon-*.jar to SRSMonitoring.jar

SETUP SOLUTION MANAGER FOR SRS MONITORING

Create SRS System in Solution Manager

Create Technology type for SRS

The first step is to create a custom technology type. A technology type describes the architecture of an
unspecific cluster system. Depending on the technology type parameter on system and instance level are
available. Call transaction SM30 and display the view V_LMDB_FIXVALMAP

In this view you have to add two entries. SAP_UNSPECIFICCLUSTERSYSTEM is for the system level of the
3rd party system and SAP_UNSPECIFICAPPLICATIONSYSTEM for the instance level.

Value Text
Owner CIM Class Name CIM Property Name CIM Property Value

SAP Replication SAP Replication

Customer SAP_UNSPECIFICAPPLICATIONSYSTEM TECHNOLOGYTYPE
Server Server
SAP Replication SAP Replication
Customer SAP_UNSPECIFICCLUSTERSYSTEM TECHNOLOGYTYPE
Server Server

Save you entries.

3
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Create System in LMDB

Call transaction LMDB, switch to the tab “Technical Systems” and select “Unspecific Cluster System” from
the drop-down field. Click “Create Technical System

A wizard opens that helps you to create the technical system. Make sure the system type is correct and click
“Next”

Enter the name for your system and select the technology type as SAP Replication Server

4
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Check you entries and specify the Extended System ID.

Save your entries

A new wizard appears that takes you through the further definition of the system. At first you have to enter
the installation path for the SRS system.

5
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Click “Next” to go to “Software” and make sure Standard Custom Instance is maintained as Product Instance

Click “Technical Instance” to move to the Instance maintenance.

Enter the instance information with the SRS hosts. If you installed the Diagnostics and the SAP Hostagent
the host should be reported to the SLD and to the LMDB automatically

Enter the installation path of the instance and click “Next”. This is necessary to successfully perform the
managed system setup later.

Save the system

6
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Managed System Configuration for SRS system

To connect the installed agents to your system and to make it fully usable you have to run the managed
system configuration for the system.
Call transaction SOLMAN_SETUP and switch to the scenario “Managed Systems Configuration”. Select your
system from the list and click “Configure System”.

The first step is to assign software and mark it as diagnostics relevant. We already did this. For Unspecific
Cluster Systems neither a Product System nor a Logical Component is mandatory. Click “Next”

Click “Execute All”

7
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

In the next step you have to assign a diagnostics agent. Select the system and click the “Assign” button.
Sometimes the agent is assigned automatically

After the agent is successfully assigned, you can go to the next step. In the 4th step you have to select the
Wily Introscope Enterprise Manager.

There is nothing to do in the next step

8
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

In the 6th step it is important to make sure “Introscope Host Adapter” setup activity run successfully. Select
“Execute All”

In the last step you check the configuration to make sure everything is fully operational. Click “Execute All” to
run the check.

Complete the setup.

9
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Custom script deployment for SRS Monitoring

Changes to commands.xml file

Go to Agent Administration using the below URL or from Step 3 of Managed System Configuration
http://<solmanhost>:<solmanport>/webdynpro/dispatcher/sap.com/tc~smd~server~agent~admin/SMDAgent
AdminApplication?sap-language=EN

Select Application Configuration Tab to change agent configuration

Expand the com.sap.smd.agent.application.remoteos and select commands.xml file. Select the central host
of your SRS system as agent in scope and click “Download Default” button

10
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Add the following lines to the default commands.xml file

<!-- SRS Monitoring -->

<CmdGroup name="SRS" cv_ppms_id="*">
<Cmd key="srs.availabilitykpis" name="SRSAvailabilityKPIs" desc="Display Availability and KPIs for the SRS
system (metric format)">
<OsCmd ostype="WINDOWS" exec=".\java -jar %SYBASE%\srsmonitoring\SRSMonitoring.jar -user
%SRS_USER% -password %SRS_PASSWORD% -port %SRS_PORT% -host %SRS_HOST% -
logFilePath c:\temp\SRSMonitoring.log" path="%SYBASE%\jre64\bin" param="false" runtime="360"/>
<OsCmd ostype="UNIX" exec="./java -jar %SYBASE%/srsmonitoring/SRSMonitoring.jar -user
%SRS_USER% -password %SRS_PASSWORD% -port %SRS_PORT% -host %SRS_HOST%"
path="%SYBASE%/jre32/bin" param="false" runtime="360"/>
</Cmd>
</CmdGroup>

Upload the updated commands.xml for the SRS Agent in scope.

Maintain SRS Users

Select the com.sap.smd.agent.application.remoteos and for the SRS Agent in scope maintain the below 4
variables and Save.

%SRS_HOST% - SRS Hostname or IP

%SRS_USER% - SRS User
%SRS_PASSWORD% - SRS User Password
%SRS_PORT% - Port for SRS Projects
%SYBASE% - Sybase Home directory

11
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Changes to SapAgentConfig.xml
Expand the com.sap.smd.agent.application.wilyhost and select SapAgentConfig.xml file. Select the central
host of your SRS system as agent in scope and click “Download Default” button

Edit the SapAgentConfig.xml file as below.

<?xml version="1.0" encoding="UTF-8" ?>

<sapagent>
<destination class="com.sap.smd.wily.hostagent.destination.SocketDestination"
name="Port%PORT%"><property name="port" value="%PORT%"/></destination>
<pool>
<action prefix="SAP SYBASE|%SID%" name="srs_availabilitykpis_%SID%"
class="com.sap.smd.wily.hostagent.action.RemoteOsCommandAction" metriclimit="5000"
period="300000">
<property name="commandkey" value="srs.availabilitykpis" />
<property name="longsid" value="%SID%" />
</action>
</pool>
</sapagent>

%SID% - SID of your SRS system in LMDB

%PORT% - Any free port for Wily Agent communication

Upload the updated SapAgentConfig.xml for the SRS Agent in scope.

12
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Once the upload is done, SRS KPIs should be visible in Wily Enterprise Manager.

Create custom data providers

Go to the below URL for creating new data collectors for SRS
http://<solmanhost>:<solmanport>/sap/bc/webdynpro/sap/wd_mai_dpc_main?sap-language=EN
Select Introscope EM (Push) as Collector Type

Create new Data Collector by clicking “Create” button

13
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Generic SRS Collector

Enter the Collector ID, Collector Name and Description.

Note: Make sure Collector ID starts with ZZ.

Go to Parameters tab and maintain the following parameters

Parameter D Parameter Description Type Ext. Mand Sequenc Ranges Usage Predefined Value
Name Context atory e
COLL_HOST Collection Collection MP 0 HIDDEN .*
Host Host
IS_AGENT_NAME Introscope Introscope MP 0 HIDDEN SAP HostAgent.*
Agent Agent
IS_PATH Introscope Introscope MP YES 0 HIDDEN SAP
Path Path SYBASE\|$T_SYSTEM_SID$\|SRS_KPIs.*\|$PATH_NAME$
IS_PROCESS_NAME Introscope Introscope MP 0 HIDDEN SAP HostAgent Process
Process Process
PATH_NAME Path Path Name MP YES 0 CONFIG
Name

Save the Data Collector and assign to a package and transport request in case you want to transport the
changes.

14
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

SRS Module Specific Data Collector – Sample Throughput Collector

Enter the Collector ID, Collector Name and Description.

Note: Make sure Collector ID starts with ZZ.

Go to Parameters tab and maintain the following parameters

Parameter D Parameter Description Type Ext. Mand Sequence Ranges Usage Predefined Value
Name Context atory
COLL_HOST Collection Collection MP 0 HIDDEN .*
Host Host
IS_AGENT_N Introscope Introscope MP 0 HIDDEN SAP HostAgent.*
AME Agent Agent
IS_PATH Introscope Introscope MP YES 0 HIDDEN SAP
Path Path SYBASE\|$T_SYSTEM_SID$\|SRS_KPIs.*\|Throughput\|(
$METRIC_CAT$)\|Instance\|($MODULES$)\|.*\|.*\|($M
ETRIC_NAME$):Current Value
IS_PROCESS_ Introscope Introscope MP 0 HIDDEN SAP HostAgent Process
NAME Process Process
METRIC_NA Metric Metric MP YES 3 CONFIG VALUEHELP
ME Name Name
METRIC_CAT Metric Metric MP YES 2 CONFIG VALUEHELP
Category Category
MODULES Modules Modules MP YES 1 CONFIG .*

Predefined values for METRIC_CAT

bps Bytes per Second
cps Commands per Second
tps Transaction per Second

Predefined values for METRIC_NAME

Obs Objects
Rate x/sec Rate (per Sec)

15
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Save the Data Collector and assign to a package and transport request in case you want to transport the
changes

Create custom system monitoring templates

Create Custom SRS Template
Enter transaction SOLMAN_SETUP. Select Technical Monitoring and then System Monitoring to enter
System Monitoring configuration screen. Click on Step 4 – Template Maintenance

Go to Edit Mode and Expert Node. Expand Technical System and select Generic Product Version. Click on
Create Custom Template

16
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Enter name for the template and Save.

Note: Assign it to Package and Transport Request if you wish to transport the templates later.
In the same way create Custom Template for Technical Instance

Create Custom Metric

Server Availability Metric (Wily)

In the SAP Replication Server System template,
Select Create -> Metric to create new custom metric.

Fill the necessary fields in Overview screen

17
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Go to Data Collection tab and enter the below details

Go to Data Usage tab and enter Reporting settings

Go to Thresholds and enter the below threshold settings

18
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Select Next and assign the alert created.

Note: Refer below link to create custom alert.

https://wiki.scn.sap.com/wiki/display/TechOps/SysMon_Create+custom+metrics+and+alerts

Performance Metric (Wily)

Fill the necessary fields in Overview screen

Go to Data Collection tab and enter the below details

19
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

In the same way, create separate custom metric for each performance KPIs by changing METRIC_NAME
and METRIC_CAT

Based on the metric, set the Data Usage and Thresholds settings for each metric
Save the complete template

Setup System Monitoring for SRS

Go to Step 5 – Define Scope and select the SRS System and click Next

20
SYBASE SRS SERVER MONITORING WITH SOLUTION MANAGER 7.1

Assign the System and Instance template and activate the template.

System Monitoring is now active and SAP Replication Server is monitored from Solution Manager.

21
www.sap.com

© 2016 SAP SE or an SAP affiliate company. 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 SE or an SAP
affiliate company.
SAP and other SAP products and services mentioned herein as well as their
rSRSective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices. Some software products
marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or
omissions with rSRSect to the materials. The only warranties for SAP SE or
SAP affiliate company products and services are those that are set forth in
the express warranty statements accompanying such products and services,
if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any course of business outlined in this document or any related presentation,
or to develop or release any functionality mentioned therein. This document,
or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform
directions and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice.
The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned
not to place undue reliance on these forward-looking statements, which
speak only as of their dates, and they should not be relied upon in making
purchasing decisions.