configuration solution manager port of rotterdam (en)

7/31/2019 Configuration Solution Manager Port of Rotterdam (en)

http://slidepdf.com/reader/full/configuration-solution-manager-port-of-rotterdam-en 1/39



Solution Manager 3.2 Configuration

Contents

Introduction ...................................... 3

1. Adding a satellite system to Solution Manager ...........................4

1.1 Installation CCMS agent on satellite system (linux) ....................................................................................6

2. Creating a monitoring solution ....73.1 Transaction RZ20 ........................................................................................................................................19

4. Earlywatch Alert service ............21

5. SLR Reporting ........................... 236. Solution Manager configuration

Port of Rotterdam ..........................266.1 General user defined alerts .........................................................................................................................266.2 SAP Application server alerts .....................................................................................................................27

7 Emailing of Alerts .......................30

Appendix 1: Configuration automatical email on alerts ...........32

1. Creating user and fill in email adres .............................................................................................................322. Client assignment.......................................................................................................................................... 323. Configuration of SAPconnect........................................................................................................................344. Monitoring properties and methods ..............................................................................................................365. Checking the proces ......................................................................................................................................38 Appendix 2: Important notes .............................................................................................................................39

Page - 2 -




Introduction

The configuration of solution manager and the involved system monitoring consist of a number of steps:

•

Adding a satellite system in solution manager.

• Creating rfc connection’s to the satellite systems.

• Creating a solution.

• Connecting a system to a solution.

• Creating and configuring alerts.

In this document the above steps will be described. Both for the creation of new systems and for changing existing ones.

Page - 3 -




1. Adding a satellite system to Solution Manager

In the satellite system:

• Create the role Z_RFCACL with PFCG with authorization object S_RFCACL, all authorizations,or transport this role from the development environment.

• Create user SOLMAN with profiles SAP_ALL and role Z_RFCACL.

• Login once to change the initial password.

In the Solution Manager system:

• Login as user: SOLMAN

• Generate the RFC destinations via transaction SMSY – Systems - <Product> - <SID> ,Display/Change, Generate RFC Destinations.. See below screenshot.(generate username/password)

Figure 1. Generate RFC Destinations.

Page - 4 -




• Add the newly created system to the right Logical Component:

o Via Transaction SMSY, ‘System Groups and Logical Components.

o Choose the logical component to where the system belongs to (ex. ECC).

o Add the new system to the desired role (development/quality/production/etc.) system

(see screenshot) en save this.

Figure 2. Logical component change

• Add the new system to SDCCN:

o Via Transaction SMSY – Goto – Solution manager Operations – Administration SDCCN

o Add system (plus-sign), select the new system

o Select the new added system and activate SDCCN with the activate button

Page - 5 -




1.1 Installation CCMS agent on satellite system (linux)

The CCMS agent is used to forward alerts, this way they can be centrally send via email. The solutionmanager system will be configured as the central system

Registration of the agents:

• Logon as user: <SID>adm

• Create a directory /usr/sap/<SID>/<Instance dir>/log/sapccm4x

• Copy the file ‘csmconf’ into this directory. The file is available via NFS onli001:/sapcd/Patches/CCMS

• Register the agent with the following command: /sapmnt/<SID>exe/sapccm4x –R pf=<instance profile>

On a questions asked the default can be chosen.

Configure the agents to start automatically with every boot of the system:

• Logon as user root

• Copy the startup file ‘sapccm4x’ into the directory /etc/init.d. The file is available via NFS onli001:/sapcd/scripts/ccms/init.d

• Copy the configuration file ‘sapccm4x’ into directory /etc/sysconfig. The file is available via NFSon li001:/sapcd/scripts/ccms/sysconfig

• Adjust the configuration file with the accurate information of the system tob e monitored.

Adjust the startup of the daemon ‘sapccm4x’ via yast so that it will start in runlevels 3 and 5.

Page - 6 -




2. Creating a monitoring solution

A solution has to be made first to be able to monitor systems. Solutions are used to divide systems intological groups. This way a landscape can be logically divided in all BW systems together and all R3

systems together, of for example all production systems together. This will give a better overview of allsystems, as not all systems are on one page then.

Figure 3. Overview active solutions

Behind every solution is a status overview of the latest EWA reports and the system alerts. Below isdescribed how to make a new solution.

Page - 7 -




• Start transaction solution_manager and click on new in the main screen of the solution manager (maybe after starting transaction solution_manager you have to click on back once to get intothe main screen)

Figure 4. Create new solution

Some details need to be given:

• Solution Name: Give a description of the solution.

• Customer Number: The SAP customer number of the Port of Rotterdam (323139).

• Original Language: Choose here the desired language (English/German).

Click on continue to create the new solution.

Page - 8 -




The solution is created and now the screen below will appear:

Figure 5. Main screen solution landscape

Systems which we made in the previous chapter can be connected here to solutions. Also different sortsof settings can be adjusted with the solution settings.

Page - 9 -




• Click on solution landscape

Figure 6. Adding systems to a solution

Select a logical component of a system that is available in the landscape (ex. ECC). Now there willappear an entry ECC under Logical components, with under every column (production system,development system, etc.) the SID’s of the systems which were added in previous chapter.

All green columns will be added into the system monitoring. To make a column green just select thecolumn and click on the button “system”. Use “save” to save all your changes.

Page - 10 -




Click on back to go back to the solution landscape screen (Figure 5). Now select solution monitoring ->system monitoring from the tab pages and then monitoring graphic to get the graphical overview of thesystems.

Figure 7 Graphical Overview of the solution Test – Development & Sandbox systems.

Add all systems which need you need on the same way. When all systems are added, alerts for thesesystems can be configured.

Page - 11 -




3. Configuration of alerts

Transaction solution_manager

Go to the main screen of solution manager where there is the overview of the created solutions. Select

the solution for which alerts should be created.

Figure 8. Graphical Overview of the systems in a solution.

Click on “Setup system monitoring” in the right column of the screen. A new screen will appear, herealso click on “Setup system monitoring”.

Page - 12 -




Figure 9. Activating the alert monitoring.

In the left column are the systems which have been added to the solution with above that a fewconfiguration options. This list needs to be worked out from top to bottom step by step. Underneath willbe a short explanation of every step.

Activate MonitoringHere you select the systems for which alert monitoring should be activated. If there is a system missingin this overview which should be in this solution then you should first add it as described in previouschapters.

Check CCMS ConnectivityThis is an overview of all systems in this solution with the rfc connection belonging toe each system andthe status of these connections. If the status of a rfc connection is red then there is a problem with for

example the user, password or the ip address. The rfc connection can be tested and re-adjusted viatransaction SM59.

Copy customizingYou can copy already created alerts from one system to the other with this option. The copy part worksseparated for; database, instance, R3 system and server.

Page - 13 -




SAP System SID (installation number)Here alerts can be added and activated. Click on the system you want to configure and a list will appear with all parts for which alerts can be configured.

Figure 10. Overview alerts

2 different types of alerts can be configured:

• Pre-defined alerts: SAP has defined some standard alerts in solution manager, these will onlyneed to be activated by selecting the column active. Check all pre-defined alerts to put themactive or not.

• User defined alerts: This are alerts that can be copied from the monitors in transaction RZ20 of

the system involved. User defined alerts can be created for every part (database, server, sapapp. server). Underneath will follow an example of how to make user defined alerts.

Page - 14 -




Figure 11. Choose CCMS context.

Click in the left column on database <SID>. In the middle column a tab page called CCMS Contentwill appear. Here you have to choose your database type, in this case for example Oracle.

Because user defined alerts can be created for every part (database, server, sap app. server), everypart has his own content tab page. This tab page needs to be selected first before user definedalerts can be created.

Page - 15 -




In the left column under database <SID> click on the row: “user defined alerts”.

Figure 12. Overview user defined alerts.

A list will appear with all alerts in regard to Oracle if you click the icon in the right of the column“alert name”. This is the same list which you will get via transaction RZ20 – SAP CCMS TechnicalExpert Monitors – All Monitoring Contexts – Oracle.

Now select a subject from the list, for example: “space management” and click on ok. Now the alert“space management” is configured and will appear in the graphical overview by the correspondingsystem.

The creation of user defined alerts works the same for all other parts like the SAP application server,server and database, just like described above.

Page - 16 -




To adjust alert thresholds you have to doubleclick on the value behind the alert in one of thecolumns: “green to yellow”, “yellow to red”, “red to yellow” or “yellow to green”. Now a new screenwill appear where you can adjust the thresholds. To get an alert for example if the cpu is being usedfor more then 80 percent, you need to do the following:

• Start transaction solution_manager -> Setup system monitoring in the left column -> Setup

system monitoring.

• Select a system for which the alerts need to be adjusted and select a server <servername>,then click on “setup monitoring for server <server>”.

Figure 13. Overview alerts with thresholds.

Page - 17 -




• Double click on the row CPU Utilization. A new screen will appear;

Figure 14. Aanpassen van waardes

• Select the tab page PerformanceAttribute and click on the change button.

• You can fill in below threshold values when an alerts should go from: “green to yellow”, “yellowto red”, “red to yellow” or from “yellow to green”.

• Save this settings and click on the back button to go back to solution manager.

Page - 18 -




The monitoring set which contains all information is found at: SAP CCMS Technical Expert Monitors – AllMonitoring Contexts.

Figure 16. Overview All monitoring contexts

Page - 20 -




4. Earlywatch Alert service

The SAP EarlyWatch Alert service (EWA) is a diagnostic service for SAP systems that are added to thesolution manager. SAP Earlywatch alert reports consist of recommendations for technical SAP settings,

overviews of performance and database growth en recommendation for support packages and plug-inlevels.

SAP Earlywatch alert reports are scheduled for each system from solution manager en run generallyevery week.

To display reports:

• Start Transaction solution_manager and click on: Solution monitoring Earlywatch Alert.

Figure 17. Overview scheduled Earlywatch sessions.

= This session still has tob e executed. The execute date is in the column right next to it.

= There is a problem with the collection of or the sending of the data. In most cases there will be arfc authorization problem on solution manager or the target system. Most probably a changed user or password.

Page - 21 -




= There is EWA data available. By clicking the row involved or via the menu “SAP SolutionManager” -> “start service processing” a background job will be started which will process al the dataavailable.

When the “service processing job” is finished a status will be shown of the involved system.

= There are recommendations / alerts in the EWA report

= There are no recommendations / alerts in the EWA report, everything is fine

There are 2 possibilities to view the EWA report:

• If you click on the icon the report will be shown in solution manager. This is handy for administrators, but the EWA report now doesn’t have graphs and cannot be printed.

• If you click on the icon a word document will be automatically generated. This document

does have graphs in it and can be printed.

After the generation of the report a new icon will be shown: this is the generated word documentcreated as an attachment in solution manager.

To re-schedule or plan an extra EWA session you need to use button:

The re-scheduling of an EWA session is in normal circumstances not needed because standard everyweek there is a session scheduled.

If the list with EWA reports becomes to long than you have to use the button:

With this old EWA reports will be archived.

Page - 22 -

How to configure Earlywatch (EWA) reports is described in the solutionmanager 3.2 configuration guide.




5. SLR Reporting

The Solution Manager can also create Service Level Reports (SLR). SLR reports can be used to monitor system downtime, response times, database growth, etc. Parts of the EWA report can be added to the

SLR. SLR reports are mainly used to check up on Service Level agreements made with the customer.

The Earlywatch Alert reporting has to be configured in Solution Manager to be able to create SLRreports.

Figure 18. Service level reporting.

To Configure service level reporting: start transaction solution_manager -> solution monitoring -> service

level reporting -> setup service level reporting.

Page - 23 -




Figure 19. Setup Service Level reporting.

The screen above shows the setup of the service level reporting. Some details need to be filled in.

General Settings for SL ReportHere you fill in company details under customer data. Fill in the day and period that the SLR reportingshould run.

Select systems for SR Report systemsHere you select the systems which need to be added in the SLR reporting.

Report content for system <systemname>Here you select the parts of the EWA that needs to be added in the SLR reporting. Think about: systemavailability, trend analysis, etc.

System availabilityHere you fill in how much percent a system has tob e available minimal (example: 95%). In the weektable or the time table you fill in when the availability needs to be measured. This can be between 9:00and 17:00 of from Monday to Friday. It is also possible to fill in specific hours of the day, between 9:00and 12:00 and between 13:00 and 18:00 for example.

Page - 24 -




System performance ThresholdsHere you fill in what the minimal response time and the average database time should be in dialog. Thestandard is 1200ms for the response time and 600ms for the database time.

After you save the above made settings there will be a session scheduled in the main screen of theService level reporting.

For the rest opening and generating the SLR reports works exact the same as for EWA reports.

Page - 25 -




6. Solution Manager configuration Port of Rotterdam

At the following pages is described how the solution manager is configured for the Port of Rotterdam.

6.1 General user defined alerts

General user defined alerts

Description Green toyellow

Yellow tored

Red toyellow

Yellow toGreen

Aborted jobs Aborted (background) jobs Aborted job gives red

Filesystems Space on the filesystem 95% of <250 MB

98% of <100 MB

97% of >101 MB

94% of >251 MB

Tablespaces Space in the tablespaces 90% of <100 MB

95% of <50 MB

94% of >51 MB

89% of >101 MB

Concurrent users Number of logged in users No alert, this is for information

Page - 26 -




6.2 SAP Application server alerts

SAP ApplicationServer alerts

Description Green toyellow

Yellow tored

Red toyellow

Yellow toGreen

EsPeak Maximum number of usedmemory in % 100% 100% 100% 100%

Long runners Long running programs indialog

300 sec. 600 sec. 600 sec. 300 sec.

Old Update Records Are there old update records? Red if there is an old update record.

PrivWpNumber Are there processes in PRIVmode?

Red if there is a process in PRIV mode.

Update Status Is the update proces active? Red if the update process is not active.

WpDiaRestart Did dialog workprocessesrestart?

Red if one or more processes restarted.

WpNonDiaRestart Did non dialog workprocessesrestart?

Red if one or more processes restarted.

Page - 27 -




6.3 Server alerts

Server alerts Description Green toyellow

Yellow tored

Red toyellow

Yellow toGreen

CPU CPU load 90% 98% 92% 85%

Lan Is the LAN slow, or are there

any collisions?

Packets In

>4000 /s

Packets Out>1400 /s

Collisions>30

Packets In

>5000 /s

PacketsOut >2000/s

Collisions>50

Packets In

<3000 /s

PacketsOut <1600/s

Collisions<40

Packets In

<2000 /s

PacketsOut <1000/s

Collisions<20

OS Collector Is the OS collector running? Red when the OS collector is not running

Paging Is there paging? In >80Out >150

In > 90Out > 200

In <89Out <199

In <79Out <149

Swap Space Is there enough swap space? <20 MB <10 MB >15 MB >30 MB

Page - 28 -




6.4 Database alerts

Server alerts Description Green toyellow

Yellow tored

Red toyellow

Yellow toGreen

Last succ. Databasecheck

Last succesfull database check >10 days >30 days <30 days <10 days

Objects missing in thedatabase

Are there missing objects in thedatabase?

If there are objects missing then yellow or red.

Optimizer Status latest Optimizer check Yellow or red if there are warnings in theoptimizer check.

R/3 consistencycheck

Status of the last consistencycheck

If the consistency check is not good then yellowor Red.

Page - 29 -




7 Emailing of Alerts

From solution manager it is possible to email alerts from the satellite systems. In appendix 1 it isexplained how to configure this. Following now is an explanation of how you can select alerts for which

an email should be send if the alerts comes up.

• Start Transaction RZ21

• Select technical infrastructure assign central autoreactions

The CCMS agent needs to be installed in the satellite system to be able to email alerts from the

satellite systems. (see chapter 1.1)

Page - 30 -




In the left column underneath system ID are all the systems listed which are configurated with solutionmanager. In the middle column are all the alerts as they are shown in RZ20. In the right column are allthe auto reactions. For the Port of Rotterdam there already is an auto reaction email created for an alert.

To create an auto reaction email on an alert you first have to select the system in the left column, thenyou have to select the alert for which you want to email in the middle column, and in the right columnyou select the method “emailen bij alert”. Click on the button assign central auto-reaction. After this issaved the system with alert and the auto-reaction will appear in the column below. Now an email will besend if the chosen alert comes up in the system. In appendix 1 it is described how to configure an emailaddress. For the Port of Rotterdam this is set to: [email protected].

Page - 31 -

mailto:[email protected]







Appendix 1: Configuration automatical email on alertsThe configuration to send alerts via email consist of 4 steps:

1. Creating user and fill in email adres

2. Client assignment3. Configuration sapconnect

4. Monitoring properties and methods

Following is an explanation of how this should be configured step by step.

1. Creating user and fill in email adres

• An user have to be created in every client of a SAP system where incoming mail (or statusnotifications of send mail) should be received. This can also be an existing user.

•

Every user who send mail in a SAP system should have an Internet email address. Fill in thisemail address via transaction su01 -> username -> edit -> in the column communication ->email.

2. Client assignment

• Goto transaction SICFFor every client of a SAP system where incoming mail (or status notifications of send mail)should be received, a SMTP server has to be made where the connection to a virtual mail hostas well as the login credentials are being stored.

There already is a SMTP server (envelop icon) in transaction SICF. Use this for the first clientwhere you want to receive mail and make a new SMTP server for each other client. Double

click on the envelop icon The next settings need tob e made on the SMTPserver.

• Host dataFor the “profile parameter number”, fill in the rising number from the is/SMTP/virt_host_<*>parameter of the profile. If you only have 1 client and because of that not created such aparameter, then you can fill in a “0”.

Page - 32 -




• Service dataFill in the client where the received mail via this virtual mail host is being send to, as well asthe login credentials (user, password en language) of the service user created for the mail.

• Handler listFill in CL_SMTP_EXT_SAPCONNECT on position 1.

Page - 33 -




• Activate the SMTP server after you have changed or created it.

(Service/virt.Host activate, or context menu).

3. Configuration of SAPconnect

• Goto transaction SCOT

The SAPconnect settings must be configurated separately for each client from which email should besend or received.

• Default domain (settings default domain)

The domain of the sap system is defined here. For instance ‘portofrotterdam.com’. This isused for the following purposes: The SMTP plugin logs on to the mail server with the domainas ID. The message ID of the outgoing mail is compiled with this domain. If a SAP user whodoesn’t have an internet email address filled in in his user master record, then the senderaddress will be generated from the sap username and this domain, for example:[email protected]

• Node (view node)There are different types of nodes in SAPconnect:

o SMTP node (for the SMTP function of the SAP application server)

o HTTP node (for paging/SMS providers who make use of web services, as of 6.20)

o RFC node (for old RFC-compatible e-mail/fax/paging gateways)

There is always a SMTP node in each client. This is automatically created by the system and cannotbe removed. This is configured in the following way:

o Double click in the node name

o Select: ‘Node in use’

o Specify for ‘mail host’ and ‘mail port’ the mail server to where outgoing mail will

be send.

Page - 34 -






o Click next to Internet on ‘set’

o Specify address areas of sender addresses which can be reached via this node

(normally an “*” if all email is being send via SMTP)o For “output formats for SAP Documents” the following is advised:

SAPscript / smart Forms PDF ABAP List HTMBusiness Object / Link HTMRAW Text TXT

Emails which are send from a SAP application will be placed in a queue. A periodic background job,

the SAPconnect send job takes the mails from this queue and sends them via the internet. This jobcan be scheduled as following:

Page - 35 -




o ‘view’ ‘jobs’. Check if a job is already scheduled. (you can see this if there is a

calendar icon)

o Kies ‘job’ ‘create’ and give a name for the new job.

o Place the cursor on the ‘SAP&CONNECTALL’ variant and choose ‘schedule job’.

o Choose ‘Schedule periodically’.

o Specify a time interval (for example 10 minutes) and choose ‘create’

If there are problems with the creation of this job, then you can also create it via transaction SM36:o Give a job name.

o Click on step, it needs to be an ABAP program, fill in the program name: ’

RSCONN01’ And choose the variant’ SAP&CONNECTALL’.o Schedule the job and fill in what the interval should be.

4. Monitoring properties and methods

Goto transcation ‘RZ21’, select ‘Method definitions’ under ‘methods’ and click on ‘display overview’.

Search in the screen that appears for the entry ‘CCMS_OnAlert_Email’

Open the properties of this method and click on change.Make sure that on the tab page ‘Execution’ at ‘type of call’ ‘funcion module’ is selected, the setting forcall has to be ‘SALO_EMAIL_IN_CASE_OF_ALERT’. Select ‘Execute method on any server’.

Page - 36 -




Click on tab page ‘Control’.

Select under ‘execute method’ the option: ‘Periodically in background process (as job)’ and selectunder ‘startup method’: ‘Execute method immediately after monitoring segment start’ and select:

‘on all application servers’.

Click on the tab parameters

Here you need to fill in which user will be used as sender and to whom the mails should be send. AtRECIPIENT-TYPEID you have to fill in a ‘U’ for an internet email address. You can also specify a time-zone here.

Page - 37 -




Click on Release and check if auto-reaction method is selected.

5. Checking the proces

You will see a 1 at ‘waiting’ in transaction SCOT ‘system status’ (view -> system status) after thebackground job has run. When there is another alert before the mail is send then this number willincrease. The mail will come in our mailbox after the job has run to pick up the mail from the queueand send it over the internet.

Page - 38 -




Appendix 2: Important notes

176492 Automatic e-mail in case of alert

455140 Configuration E-mail, fax, paging/SMS via SMTP

207223 Activating the SAP Earlywatch alert

817791 Solution manager installation manual: changes

814853 Implementation guide for solution manager 3.2

558506 RZ20 and CCMS agents: Overview agent version

697175 RZ20: Missing monitors for Netweaver 04 supportabili ty