CCMS and SAP Solution Manager

System and Business Process Monitoring in the SAP Solution Manager

The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.

You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system.

CCMS and system monitoring in the SAP Solution Manager

The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.

The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.

The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.

CCMS and business process/interface monitoring

You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, „BPM“ of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.

The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:

● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and „Other CCMS“ and interface data, in the local CCMS of the satellite systems.

● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.

The SAP Solution Manager system copies the data from the local CCMS.

The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.

The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.

Session Change Modes

Definition

In the change mode:

· of the business process monitoring maintenance session, you specify the business processes and business process steps which you have created.

· of the business process monitoring Setup session, you specify the business processes and their alerts which you want to monitor.

· of the business process monitoring Monitoring session, you monitor the business processes and process the alert messages.

Structure

The screen is divided into three areas:

Left-hand column

Displays all the checks which you must perform to set-up the business process monitoring of your solution.

Business Process Maintenance session

· Business Processes - Overview

· Interface Overview

· Contact Data

Business Process SETUP session

· Solution Support Organization

· Business Processes

¡ BPMon:

...

§ Notifications

§ Steps (according to process steps set up)

Monitoring Types (according to the number of monitoring types selected)

Monitoring Transactions

Monitoring Activities

Notifications

§ Generate Monitoring Customizing

¡ Interface Monitoring

§ Analyses and Monitoring tools

§ Monitoring activities

§ Notifications

...

· Data Collector Frequencies

· Local RFC Destination for Data Collection

· Monitoring Check Lists

· Cover Page

Business Processes MONITORING session

· Basic Settings

· Activation

· Business process

¡

Any subitems of checks only appear when you have performed and saved the check. The subitems are partially preconfigured if the system has the necessary information.

¡

Top right screen area:

Explains the use, background and procedure of the check.

To hide the documentation, move the frame.

Bottom right screen area:

The tables to be maintained by the check.

You can call the online documentation in the logon language, for the checks, with HELP (see SAP note: 789703).

Send E-Mail Automatically

Procedure

You want the system to send SAP EarlyWatch or Service Level Reporting reports automatically by E-Mail.

To send HTML reports automatically by E-Mail, you have performed the required activities in the IMG (transaction SPRO).

1. Start the transaction SOLUTION_MANAGER.

2. If you are in the solution overview, choose a solution.

3. Choose Edit Send E-Mail Automatically .

4. To add an E-Mail address to which to send your reports automatically, choose Create E-Mail.

   A dialog box appears.

5. Enter the required data.

   The system sends the selected report to the assigned E-Mail address(es), automatically. You can specify several E-Mail addresses. The system specifies the rating und the report type in the E-Mail subject line. The subject line is formatted as follows: Unkritisch (Grün) # EW_ALERT # XXX # EarlyWatch Alert Report with Graphics

   Note

   The E-Mail address is only valid for the selected solution. If you want to set-up automatic sending of E-Mails for other solutions, proceed analogously for them.

   You can also send EarlyWatch Alert reports per system with self-defined subject line or send options, e.g. Only with Red status EarlyWatch Alerts in a BAdIs implementation (cf. IMG transaction SPRO).

Save, Retrieve and Archive EarlyWatch Alert

You can save no longer needed EarlyWatch Alerts, i.e. remove them from the EWA list, to keep the EarlyWatch Alert services list short and comprehensible. If you have an archiving system connected, you can archive saved EarlyWatch Alerts, to reduce database load.

Prerequisites

Note

Your archiving system is not part of the SAP environment. You must set-up an external archiving system (note 546685).

End of the note.

To archive, you have made the following settings in the IMG: SAP Netweaver Application Server Basis Services Archive Link .

Procedure

Save Early Watch Alert

You can:

• To save no longer needed SAP Early Watch Alerts automatically after a specified time, specify a retention time for the SAP Early Watch Alerts of a system:

  1. Choose transaction SOLUTION_MANAGER Settings Solution Monitoring EarlyWatch Alert .

  2. Enter the required data in the Retention Time column.

  3. Save your changes.

     The system automatically removes the EarlyWatch Alert sessions which are older than this retention time, and any attachments, from the EWA list.

• To save no longer required SAP Early Watch Alerts manually:

  1. Start the transaction SOLUTION_MANAGER.

  2. Choose Solution Monitoring EarlyWatch Alert in the Operations screen

     You go to the overview of all SAP EarlyWatch Alert services.

  3. Choose Save Services.

  4. Select the service that you want to save.

  5. Choose Save Services.

     You go back to the SAP EarlyWatch Alert overview screen, in which a new pushbutton, Display Archive Queue, is displayed. You go to the overview of saved services with Display Archive Queue.

Retrieve EarlyWatch Alert

1. Choose Display Archive Queue.

2. Choose Retrieve Service to retrieve the SAP EarlyWatch Alert.

   You go back to the overview screen. The retrieved SAP EarlyWatch Alert service appears in the overview: Archive Sessions

Archive EarlyWatch Alert

You must put sessions in the repository before you can archive them.

You can:

• To archive sessions manually:

  1. Choose Archive Services in the repository.

  2. Specify a date and confirm your entries.

     The system archives the sessions which are older than the specified date, with their attachments.

• To archive sessions automatically, schedule automatic archiving:

  1. Schedule the job RDARCH_ARCHIVE_DATA_SOLMAN with transaction SM37.

     You can schedule the job for regular execution, e.g. daily, to archive all sessions which are more than ten days old.

  2. The job archives sessions in the repository which are older than an age specified by you, with their attachments.

You can accesss any session in the archive. Saved sessions can be displayed, but not changed. When you archive sessions, the system saves them in an external repository and deletes them physically from the database. This reduces the size of the database.

Result

You can display, but not change, saved sessions and their documents, with Display Archive Queue.

Note

The job RDARCH_CLEAN_DATABASE, which runs daily, deletes archived sessions and documents physically from the Solution Manager system database. You can then no longer open the archived sessions. You can only display them.

Create Report and Display Session Details

Procedure

The SAP EarlyWatch report gives you detailed information about system status, performance, configuration, system processing, database administration and trend analyses.

You have:

• processed the session.

• installed the Internet Graphics Server (IGS), to create an HTML report with graphics.

• set-up automatic sending of E-Mails, if required.

Create SAP EarlyWatch report

1. Start the transaction SOLUTION_MANAGER.

2. Choose Solution Monitoring EarlyWatch Alert in the Operations screen

   You go to the overview of all SAP EarlyWatch Alert services. You can generate an SAP EarlyWatch Alert report in various ways:

   • HTML document

     1. Choose the link to a service.

     2. Choose a report type.

        Note

        You can send the HTML report as an E-mail to yourself and any number of other recipients (Add Recipient pushbutton) . You can only enter one recipient per row.

        End of the note.

   • MS Word document

     1. Choose Create Word Report.

     2. Choose a report type.

        When you have generated the report, it appears as an attachment. You can send the document as an E-mail from MS Word.

Display session details

1. Start the transaction SOLUTION_MANAGER.

2. Choose Solution Monitoring EarlyWatch Alert in the Operations screen

   You go to the overview of all SAP EarlyWatch Alert services.

3. Choose Display Session.

4. Confirm the information dialog box

   You go to display mode: EarlyWatch Alert.

   • You can see all data without evaluation, in a hierarchy, with the EWA Viewer.

   • You can create reports with HTML Document or MS Word Document.

   • To save an HTML document locally, choose Goto HTML Document Save .

ProcedureManually Executing Downloads

Procedure

You want to check the download data functionality when you create an SAP EarlyWatch Alert. You want current data, regardless of the weekly reports.

1. Start the transaction SOLUTION_MANAGER.

2. Choose Solution Monitoring EarlyWatch Alert in the Operations screen.

   You go to the overview of all SAP EarlyWatch Alert services.

3. Choose Create Service.

4. Choose the SAP EarlyWatch Alert Create Service for a system.

5. Select the planned date.

6. Confirm your entries.

   Note

   The system creates a new SAP EarlyWatch Alert service. The newly-created SAP EarlyWatch Alert appears with the symbol Wait for ’Download Data’.

   End of the note.

7. Choose the SAP EarlyWatch Alert for a system.

   You go to a screen which explains the subsequent procedure.

8. Call the Service Data Control Center (transaction: SDCCN) in the system, with Call Service Data Control Center.

   You go to the Service Data Control Center of the selected satellite system.

9. Choose Create in the Service Data Control Center.

10. Choose the task Refresh Sessions.

    A dialog box appears.

11. Choose Now to refresh the task immediately.

12. Choose Run Task Once to schedule the task once.

13. Choose the target RFC destination to the Service Data Control Center, from the possible entries help.

14. Confirm.

    You get a task number.

15. Confirm.

    Your task number appears in a row in the To Do tab.

16. Select the row of your task.

17. Choose Edit EarlyWatch Alert .

18. Confirm.

19. You can check the progress of the job in the Task Log tab.

20. Go back to the SAP Solution Manager System.

21. Refresh your data in the SAP Solution Manager.

    Successful download is indicated by a symbol in the overview in the SAP Solution Manager. The alert data is now available in the SAP Solution Manager.

22. To edit your session data in the SAP Solution Manager, choose the link to the SAP EarlyWatch Alert.

23. Proceed as described in the subsequent procedure.

    You can start the background job yourself with Start Service Processing.

You can see the status of the data of your systems in the SAP Solution Manager. Performance data is for the last complete week. All other data is from no earlier than when the download was made. You can generate the SAP EarlyWatch Alert report as an MS Word or HTML document, or display the SAP EarlyWatch Alert session in display mode.

Setting-Up EarlyWatch Alerts

Set-up the EarlyWatch Alert for your systems and solutions. You can also set-up EarlyWatch Alerts per system or solution.

Prerequisites

You have put systems in a solution.

Procedure

1. Choose the transaction SOLUTION_MANAGER.

2. Choose the Solution Monitoring EarlyWatch Alert tab in the Operations Setup area.

   Note

   To call a cross-solution display of the Setup EarlyWatch Alert, choose Settings in the solution overview, then Solution Monitoring EarlyWatch Alert .

   End of the note.

3. Choose the Set-Up EarlyWatch Alert link.

   You go to the EarlyWatch Alert Administration.

4. You can set-up EarlyWatch Alert monitoring data collection per system or solution, here.

5. Select fields according to your requirements.

   EarlyWatch Alert Set-Up Settings

   Column	Meaning	Note
   Active	The system collects monitoring data.	If you do not set this flag, the system collects no data.
   Send to SAP	The system sends your monitoring data to SAP.	Only set this flag when you have set the collection to active.
   In EWAfS	The monitoring service for EarlyWatch Alert per system is put in the monitoring service EarlyWatch Alert per solution.	You can decide which EarlyWatch Alerts per system appear in your EarlyWatch Alert per solution.
   Day of the week	You can specify the data collection day.	The data collection day for EarlyWatch Alert per system and Early Watch Alert per solution, can vary.
   Retention time	You can specify the retention time in days.	After the retentio time, the EarlyWatch Alerts are saved.

6. Save your settings.

SAP EarlyWatch Alert

This process helps you to identify potential problems early, avoid bottlenecks, and monitor the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The data collection infrastructure comprises the ABAP Service Data Control Center and the JAVA function module Data Provider. The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.

To be able to use it, you have:

• maintained the non-ABAP systems correctly in the system landscape maintenance (transaction SMSY)

• RFC – Connections between: and an RFC – Connections established.

  • your satellite systems and the SAP Solution Manager system

  • SAP Solution Manager and the SAP Service Marketplace

  • Solution Manager system and Solution Manager Diagnostics

    Cf: Solution Manager IMG (transaction SPRO).

• checked the availability of the tools required for the SAP Service sessions (add-on ST-A/PI), with the report RTCCTOOL.

• activated Alert Monitoring and set-up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCCN) of your satellite systems, for all SAP satellite systems and the central SAP Solution Manager of your solution

• set-up your systems in a solution landscape in the SAP Solution Manager

• configured Solution Manager Diagnostics

Process

Early Watch Alert for ABAP Systems

1. Configure the SAP EarlyWatch Alert in SAP Solution Manager scheduling. You have:

   • scheduled the service sessions of your solution in the SAP Solution Manager Solution Directory.

     Note

     The default value is Mondays. You should retain this value.

     End of the note.

   • activated or deactivated the download of the SAP EarlyWatch Alert data from the Service Data Control Center, for the systems in your solution.

2. You have activated SAP EarlyWatch Alert monitoring for the systems in your solution.

3. Data collectors in the satellite systems aggregate analysis-relevant system and performance date weekly.

4. The system forwards this data to the SAP Solution Manager by automatic download via the Service Data Control Center (SDCCN).

5. The job SM:EXEC SERVICES triggers the processing of the data in a session.

6. The procedure continues according to the following rules which SAP put in the system:

• Red: Very critical/error.

  1. Analyze the report. The SAP Solution Manager system automatically sends the data to SAP.

  2. The SAP Support checks the problems and contacts you, if required, to discuss possible activities.

  3. If you regard the alert as critical, discuss possible reactions with SAP.

  4. Take the appropriate measure

• Yellow: Critical/warning. Analyze the report.

• Gray: System status cannot be determined. Check why the system status could not be determined.

• Green: No error.

The system sends a session to SAP, initially and monthly, using the SAP Service Marketplace, independently of the analysis of the weekly SAP EarlyWatch Alert reports.

EarlyWatch Alert for ABAP Systems

Solution Manager Diagnostics is installed in the Solution Manager JAVA stack. It collects data from all monitored non-ABAP systems, centrally. The ABAP stack is used to generate the EarlyWatch reports.

1. In the Solution Manager Diagnostics, data collectors collect data centrally for Garbage Collection Analysis (EWA GCA Task), and data based on Wily Introscope (EWA ISData task) . This data is typically collected hourly. Garbage Collection Analysis should be activated per host for the EarlyWatch Alert report.

2. The central Service Data Control Center calls a function module which then calls the Data Provider in Solution Manager Diagnostics. This occurs weekly.

3. The Data Provider collects and processes the database data and passes it to the calling function module.

4. The data processing then continues as for EarlyWatch Alert for ABAP systems, step 4.

ploading Repeatedly Delivered D&B Files

Purpose

In addition to the D&B files delivered only once (see Uploading Initially Delivered D&B Files) you also get the following files:

D&B file	Technical Name
D&B Marketing Universe Matched Client File	0DB_IMPORTFILE_MU.csv
D-U-N-S Text File	0DBDUNS_NUM_TEXT_MU.csv
D&B Universe of Abstract Data	0DBDUNS_NUM_ABSTRACT_MU.csv

These files are also delivered each time you request new data from D&B, for example on a six-monthly or quarterly basis depending on your contract with D&B.

Each time D&B provides new data both the master data for the InfoObjects D-U-N-S number and vendor number (0VENDOR) require updating. If a SAP CRM system is involved, the business partner number requires updating, too. The data also has to be loaded into the InfoCube D&B Marketing Cube.

The process of uploading D&B data is simplified significantly by using process chains. The process chains delivered by SAP enable the automatic upload of D&B master and transactional data.

Prerequisites

You have successfully performed the previous steps of the upload process.

Process

The upload process for these files can be described as a ten-step procedure. The following chart gives an overview of the individual steps.

For a description of the individual steps, see:

· Uploading the D-U-N-S Text File

· Uploading D&B's Universe of Abstract Data

· Enhancing the D-U-N-S Number with Status Information

· Applying Attribute Changes to InfoObject D-U-N-S Number

· Updating InfoObject Customer Number

· Applying Attribute Changes to InfoObject Customer Number

· Updating InfoObject Business Partner

· Applying Attribute Changes to InfoObject Business Partner

· Enhancing Business Partner in SAP CRM with D-U-N-S Number

· Uploading Transactional Data into the Marketing Cube