KEMBAR78
Technical Monitoring Alert Configuration | PDF | Login | System Software
Scribd
Upload
154 views36 pages

Technical Monitoring Alert Configuration

This document provides instructions for configuring technical monitoring alerts in SAP systems using RRBASIS. It outlines the prerequisites, installing the diagnostic agent, configuring the managed system in Solman, and setting up monitoring templates with thresholds. The prerequisites include approvals, login credentials, Solman access, and media files. The diagnostic agent is installed individually on each CI and app server. Key steps include using sapinst to install, starting the agent, and checking statuses. Managed system configuration in Solman includes selecting the system, making fields green, creating RFCs, and assigning the diagnostic agent. Finally, templates are created locally for each technical system and instance, metrics and thresholds are defined, scopes are selected, and templates are

Uploaded by

mohd4red
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
154 views36 pages

Technical Monitoring Alert Configuration

This document provides instructions for configuring technical monitoring alerts in SAP systems using RRBASIS. It outlines the prerequisites, installing the diagnostic agent, configuring the managed system in Solman, and setting up monitoring templates with thresholds. The prerequisites include approvals, login credentials, Solman access, and media files. The diagnostic agent is installed individually on each CI and app server. Key steps include using sapinst to install, starting the agent, and checking statuses. Managed system configuration in Solman includes selecting the system, making fields green, creating RFCs, and assigning the diagnostic agent. Finally, templates are created locally for each technical system and instance, metrics and thresholds are defined, scopes are selected, and templates are

Uploaded by

mohd4red
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 36

RRBASIS

Technical Monitoring Alert Configuration


Topics Covered

1. Prerequisite
2. Diagnostic agent Installation
3. Managed system Configuration
4. Technical monitoring Setup

Note 1: - All the screen shots and values mentioned in this doc are with reference to SAP
P42 system.

Note 2:- Do not try to uninstall diagnostic agent, if you come across the situation where
you need to uninstall it, please consult with seniors.

Note 3: - If you come across any other screen which is not mentioned in this document
and you are not sure of, please do not go ahead. Please consult with seniors. Especially
during DAA installation.

Note 4:- Please make all the prerequisite ready beforehand instead of struggling on the
go.

Note 5:- This document does not contain how to add recipients for alerts, please do not
add any recipients until you fine tune the template. For testing purpose, please check
alerts in solman alert in box.

Note 6:- Starting and Stopping Diagnostic agent must be done through daaadm
user. Command to start/stop daa is stopsap r3 / startsap r3. Double check the user
you are logged in with before you run this command, otherwise you may end up stopping
CI / app server.
Prerequisite:-

1. Approval to reset the root password on Managed system


2. Login password on managed system with root, sidadm user
3. Access to solman
4. Diagnostics agent media files, SAPCAR, SWPM.
5. Solman will create below users in Managed system – Get approval for this
beforehand.

Diagnostic agent Installation

1. Install Diagnostic Agent on CI and all app servers individually

Diagnostic Agent on app server P42APP2A

(/sapmnt is common for CI and all app servers when installing DA in app servers it will get installed in
the /usr/sap specific path)

Before starting make sure SOLMAN entries are present in the servers /etc/hosts files of managed
system
Same sapinst will be used for installation on all CI and App servers
If below screen appears after this give same password as usr id daaadm
Select No
Yes
Check status of DA processes

/usr/sap/hostctrl/exe# ./saphostexec -status


Before smdsetup for port no

Below files need to copied to the CI and app servers at their respective locations

In CI
Copy files from CI to app servers
Below command is to be executed by daaadm account on all CI and app servers

cd /usr/sap/DAA/SMDA98/script and run the bellow script

./smdsetup.sh managingconf hostname:"sapms://solman.ril.com" port:"8101" user:"SMD_ADMIN"


pwd:"s09admin”
For log details when setting up port no for DA
2. Managed system Configuration

T-code : -Solman_setup

Select your system


For production system select Full configuration and for non prod select Min config preferably.

Try to make all the lights Green …. Details in next steps

Click EDIT and Create automatically

Select the activity and click execute all


If solman allows you to create this RFC automatically , click execute. If its not turning green, create
all these rfcs manually and go ahead.

Note :- back rfc will be in managed system remaining rfc’s will be in solman. Take reference from P35
/ p42

Assign configured Diagnostic agent, this will remain red as we are not configuring Database alerts
and have not installed DAA on DB hosts.
Put the system details

You may have to activate ping services from SICF in your abap stystem. Over all status will be Yellow
as DB is not configured here.

Simply execute and Next


Select user one by one and click execute.

Next and Execute All


Next and execute all

Here below you can check the summary of your Managed system configuration.

Make sure you click Finish button and come out.

3. Technical monitoring Setup

Setting Template with Required Threshold.

T-code :- solman_setup

Navigation as per screen shot


For CI : - Create template in Technical System

For App server: - Create template in Technical instance

Go to required template click on Edit and create new custom new template (Right click on standard
template and click new template)

While saving a template, it will ask for Global or local object. Save it as local object. This will be non-
transportable object.

Select Required Metric and maintain the threshold values after checking in the system for live
scenario.

You can take a reference from p42 / p16 / p35 template. But the values will be different for every
system as per the live scenario.
Define Scope : - Select your Technical system and Click next.

Click Assign template and assign respective template.


Click on Apply and activate button and select “” Selected managed object only”.

You might also like