Configuration Solution Manager Port of Rotterdam (en)

Published on January 2017 | Categories: Documents | Downloads: 99 | Comments: 0 | Views: 572
of 39
Download PDF   Embed   Report

Comments

Content

Solution Manager Configuration
Port of Rotterdam

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....7
3.1 Transaction RZ20........................................................................................................................................19

4. Earlywatch Alert service............21 5. SLR Reporting...........................23 6. Solution Manager configuration Port of Rotterdam..........................26
6.1 General user defined alerts.........................................................................................................................26 6.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.............................................................................................................32 2. Client assignment..........................................................................................................................................32 3. Configuration of SAPconnect........................................................................................................................34 4. Monitoring properties and methods..............................................................................................................36 5. Checking the proces......................................................................................................................................38 Appendix 2: Important notes.............................................................................................................................39

Page - 2 -

Solution Manager 3.2 Configuration

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 -

Solution Manager 3.2 Configuration

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 -

Solution Manager 3.2 Configuration



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

Via Transaction SMSY, ‘System Groups and Logical Components. Choose the logical component to where the system belongs to (ex. ECC). 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 o

Via Transaction SMSY – Goto – Solution manager Operations – Administration SDCCN Add system (plus-sign), select the new system Select the new added system and activate SDCCN with the activate button

o

Page - 5 -

Solution Manager 3.2 Configuration

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 solution manager 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 on li001:/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 on li001:/sapcd/scripts/ccms/init.d Copy the configuration file ‘sapccm4x’ into directory /etc/sysconfig. The file is available via NFS on 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 -

Solution Manager 3.2 Configuration

2. Creating a monitoring solution
A solution has to be made first to be able to monitor systems. Solutions are used to divide systems into logical 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 all systems, 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 is described how to make a new solution.

Page - 7 -

Solution Manager 3.2 Configuration



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 into the 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 -

Solution Manager 3.2 Configuration

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 sorts of settings can be adjusted with the solution settings.

Page - 9 -

Solution Manager 3.2 Configuration



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 will appear 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 the column and click on the button “system”. Use “save” to save all your changes.

Page - 10 -

Solution Manager 3.2 Configuration

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 the systems.

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 these systems can be configured.

Page - 11 -

Solution Manager 3.2 Configuration

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, here also click on “Setup system monitoring”.

Page - 12 -

Solution Manager 3.2 Configuration

Figure 9. Activating the alert monitoring. In the left column are the systems which have been added to the solution with above that a few configuration options. This list needs to be worked out from top to bottom step by step. Underneath will be a short explanation of every step. Activate Monitoring Here you select the systems for which alert monitoring should be activated. If there is a system missing in this overview which should be in this solution then you should first add it as described in previous chapters. Check CCMS Connectivity This is an overview of all systems in this solution with the rfc connection belonging toe each system and the 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 via transaction SM59. Copy customizing You can copy already created alerts from one system to the other with this option. The copy part works separated for; database, instance, R3 system and server.

Page - 13 -

Solution Manager 3.2 Configuration

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 only need to be activated by selecting the column active. Check all pre-defined alerts to put them active 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, sap app. server). Underneath will follow an example of how to make user defined alerts.



Page - 14 -

Solution Manager 3.2 Configuration

Figure 11. Choose CCMS context. Click in the left column on database <SID>. In the middle column a tab page called CCMS Content will 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), every part has his own content tab page. This tab page needs to be selected first before user defined alerts can be created.

Page - 15 -

Solution Manager 3.2 Configuration

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 Technical Expert 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 corresponding system. 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 -

Solution Manager 3.2 Configuration

To adjust alert thresholds you have to doubleclick on the value behind the alert in one of the columns: “green to yellow”, “yellow to red”, “red to yellow” or “yellow to green”. Now a new screen will appear where you can adjust the thresholds. To get an alert for example if the cpu is being used for 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 -

Solution Manager 3.2 Configuration



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”, “yellow

to 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 -

Solution Manager 3.2 Configuration

3.1 Transaction RZ20
Before Solution Manager was developed transaction Rz20 (CCMS Monitoring sets) was used to monitor systems centrally and to check without having to go through all transactions manually. RZ20 has different tree structures for different SAP parts. The alerts are configured under these tree structures and also the way that these alerts are picked up and the thresholds defined is put here. Below the surface RZ20 is used by Solution Manager. All alerts which are adjusted in RZ20 are also adjusted in Solution Manager.

Figure 15. Transaction Rz20

Page - 19 -

Solution Manager 3.2 Configuration

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

Figure 16. Overview All monitoring contexts

Page - 20 -

Solution Manager 3.2 Configuration

4. Earlywatch Alert service
The SAP EarlyWatch Alert service (EWA) is a diagnostic service for SAP systems that are added to the solution 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-in levels. SAP Earlywatch alert reports are scheduled for each system from solution manager en run generally every 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 a rfc authorization problem on solution manager or the target system. Most probably a changed user or password.

Page - 21 -

Solution Manager 3.2 Configuration

= There is EWA data available. By clicking the row involved or via the menu “SAP Solution Manager” -> “start service processing” a background job will be started which will process al the data available. 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. this is the generated word document



After the generation of the report a new icon will be shown: created 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 every week 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.

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

Page - 22 -

Solution Manager 3.2 Configuration

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 SLR reports.

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 -

Solution Manager 3.2 Configuration

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 Report Here you fill in company details under customer data. Fill in the day and period that the SLR reporting should run. Select systems for SR Report systems Here 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: system availability, trend analysis, etc. System availability Here you fill in how much percent a system has tob e available minimal (example: 95%). In the week table or the time table you fill in when the availability needs to be measured. This can be between 9:00 and 17:00 of from Monday to Friday. It is also possible to fill in specific hours of the day, between 9:00 and 12:00 and between 13:00 and 18:00 for example.

Page - 24 -

Solution Manager 3.2 Configuration

System performance Thresholds Here you fill in what the minimal response time and the average database time should be in dialog. The standard 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 the Service level reporting. For the rest opening and generating the SLR reports works exact the same as for EWA reports.

Page - 25 -

Solution Manager 3.2 Configuration

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 Aborted jobs Filesystems Tablespaces Concurrent users Description Aborted (background) jobs Space on the filesystem Space in the tablespaces Number of logged in users
Green to yellow Yellow to red Red to yellow Yellow to Green

Aborted job gives red 95% of 98% of 97% of <250 MB <100 MB >101 MB 90% of 95% of 94% of <100 MB <50 MB >51 MB No alert, this is for information

94% of >251 MB 89% of >101 MB

Page - 26 -

Solution Manager 3.2 Configuration

6.2 SAP Application server alerts
SAP Application Server alerts EsPeak Long runners Old Update Records PrivWpNumber Update Status WpDiaRestart WpNonDiaRestart Description Maximum number of used memory in % Long running programs in dialog Are there old update records? Are there processes in PRIV mode? Is the update proces active? Did dialog workprocesses restart? Did non dialog workprocesses restart?
Green to yellow Yellow to red Red to yellow Yellow to Green

100% 300 sec.

100% 600 sec.

100% 600 sec.

100% 300 sec.

Red if there is an old update record. Red if there is a process in PRIV mode. Red if the update process is not active. Red if one or more processes restarted. Red if one or more processes restarted.

Page - 27 -

Solution Manager 3.2 Configuration

6.3 Server alerts
Server alerts CPU Lan Description CPU load Is the LAN slow, or are there any collisions?
Green to yellow Yellow to red Red to yellow Yellow to Green

90%
Packets In >4000 /s Packets Out >1400 /s Collisions >30

98%
Packets In >5000 /s Packets Out >2000 /s Collisions >50

92%
Packets In <3000 /s Packets Out <1600 /s Collisions <40

85%
Packets In <2000 /s Packets Out <1000 /s Collisions <20

OS Collector Paging Swap Space

Is the OS collector running? Is there paging? Is there enough swap space?

Red when the OS collector is not running In >80 In > 90 In <89 In <79 Out >150 Out > 200 Out <199 Out <149 <20 MB <10 MB >15 MB >30 MB

Page - 28 -

Solution Manager 3.2 Configuration

6.4 Database alerts
Server alerts Last succ. Database check Objects missing in the database Optimizer R/3 consistency check Description Last succesfull database check Are there missing objects in the database? Status latest Optimizer check Status of the last consistency check
Green to yellow

>10 days

Yellow to red >30 days

Red to yellow <30 days

Yellow to Green <10 days

If there are objects missing then yellow or red.

Yellow or red if there are warnings in the optimizer check. If the consistency check is not good then yellow or Red.

Page - 29 -

Solution Manager 3.2 Configuration

7 Emailing of Alerts
From solution manager it is possible to email alerts from the satellite systems. In appendix 1 it is explained 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 -

Solution Manager 3.2 Configuration

In the left column underneath system ID are all the systems listed which are configurated with solution manager. In the middle column are all the alerts as they are shown in RZ20. In the right column are all the 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, then you have to select the alert for which you want to email in the middle column, and in the right column you select the method “emailen bij alert”. Click on the button assign central auto-reaction. After this is saved the system with alert and the auto-reaction will appear in the column below. Now an email will be send if the chosen alert comes up in the system. In appendix 1 it is described how to configure an email address. For the Port of Rotterdam this is set to: [email protected].

Page - 31 -

Solution Manager 3.2 Configuration

Appendix 1: Configuration automatical email on alerts
The configuration to send alerts via email consist of 4 steps: Creating user and fill in email adres 2. Client assignment 3. Configuration sapconnect 4. Monitoring properties and methods
1. 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 status notifications 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 this email address via transaction su01 -> username -> edit -> in the column communication -> email.



2. Client assignment
• Goto transaction SICF For 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 host as well as the login credentials are being stored. There already is a SMTP server (envelop icon) in transaction SICF. Use this for the first client where you want to receive mail and make a new SMTP server for each other client. Double click on the envelop icon server. • The next settings need tob e made on the SMTP

Host data For 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 a parameter, then you can fill in a “0”.

Page - 32 -

Solution Manager 3.2 Configuration



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



Handler list Fill in CL_SMTP_EXT_SAPCONNECT on position 1.

Page - 33 -

Solution Manager 3.2 Configuration



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 be send or received.


Default domain (settings  default domain) The domain of the sap system is defined here. For instance ‘portofrotterdam.com’. This is used for the following purposes: The SMTP plugin logs on to the mail server with the domain as ID. The message ID of the outgoing mail is compiled with this domain. If a SAP user who doesn’t have an internet email address filled in in his user master record, then the sender address 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)

o
o

There is always a SMTP node in each client. This is automatically created by the system and cannot be removed. This is configured in the following way: Double click in the node name Select: ‘Node in use’ o Specify for ‘mail host’ and ‘mail port’ the mail server to where outgoing mail will be send.

Page - 34 -

Solution Manager 3.2 Configuration

Click next to Internet on ‘set’ 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 HTM Business Object / Link HTM RAW Text TXT
o o

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 job can be scheduled as following:

Page - 35 -

Solution Manager 3.2 Configuration

‘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’
o

o

o

If there are problems with the creation of this job, then you can also create it via transaction SM36: 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’. 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 for call has to be ‘SALO_EMAIL_IN_CASE_OF_ALERT’. Select ‘Execute method on any server’.

Page - 36 -

Solution Manager 3.2 Configuration

Click on tab page ‘Control’.

Select under ‘execute method’ the option: ‘Periodically in background process (as job)’ and select under ‘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. At RECIPIENT-TYPEID you have to fill in a ‘U’ for an internet email address. You can also specify a timezone here.

Page - 37 -

Solution Manager 3.2 Configuration

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 the background job has run. When there is another alert before the mail is send then this number will increase. The mail will come in our mailbox after the job has run to pick up the mail from the queue and send it over the internet.

Page - 38 -

Solution Manager 3.2 Configuration

Appendix 2: Important notes
176492 455140 207223 817791 814853 558506
697175

Automatic e-mail in case of alert Configuration E-mail, fax, paging/SMS via SMTP Activating the SAP Earlywatch alert Solution manager installation manual: changes Implementation guide for solution manager 3.2 RZ20 and CCMS agents: Overview agent version
RZ20: Missing monitors for Netweaver 04 supportability

Page - 39 -

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close