SAP Library - Find your answers

Use

In the configuration of availability monitoring with CCMSPING, you can deactivate the monitoring during certain specified times, such as during the weekend or for maintenance work. You can also repeat these monitoring pauses daily or weekly.

Prerequisites

This procedure is part of the Configuring Availability Monitoring process. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure.

Procedure

The system is displaying the Configure Availability and Performance Overview screen. If you want to create or change a monitoring pause for monitored systems, follow the procedure below:

...

...

1. Select the desired systems by choosing the folder symbol for the corresponding systems.

Note that a system is only correctly selected when the entire line is highlighted:

2. If you have only selected one system, or want to create different monitoring pauses for the selected systems, choose the Pauses button and then Create Monitoring Pause.

If you want to create an identical monitoring pause for the selected systems, choose the Pauses button and then Create Uniform Monitoring Pause.

3. The Maintain Time not Monitored screen appears. The screen has the following structure:

4. You can define monitoring rules for single monitoring pauses, and pauses that are repeated daily or weekly. The monitoring pauses that are repeated daily take effect immediately, the monitoring pauses that are repeated weekly are valid from the time specified, each time for the selected period of time and on the selected weekday.

5. Save the monitoring rule that you have created. Once you have successfully saved your rule, the system displays a success message and your rule appears in the list at the bottom of the screen. If you have selected multiple systems, and do not want to create a uniform monitoring pause, repeat these steps for all selected systems.

To change a monitoring rule, delete the rule from the list, and recreate the rule.

6. To leave the screen, choose Cancel ()

Result

The selected systems are not monitored for their availability during the specified times; that is, no corresponding alerts are generated during these time periods.

Availability Monitoring with CCMSPING start page

Monitoring objects and attributes are assigned various properties and methods. There are default settings in the standard SAP System (which is delivered with the properties variant SAP_DEFAULT) for most nodes for properties and methods, meaning that you can already work with these settings.

Auto-reactions are an example. There are very few assignments of these in the standard SAP System. You can make your own assignments of these (see also: Selected Methods of the Alert Monitor).

If the standard settings do not meet your requirements, you can change the properties and method assignments at any time. You can make the changes both in the Alert Monitor and in the Customizing transaction RZ21. You can either make changes for the individual node itself or for the MTE class or attribute group, to which the node belongs (we recommend the latter).

Features

The following cases occur most often in practice:

Use

You can create monitoring rules in the configuration of the availability monitoring with CCMSPING. You define the type of monitoring for the relevant system in these rules. You have the following options:

· Monitoring the application servers:

¡ Ping Monitoring

With this type of monitoring, the availability agent queries the message server of the corresponding system as to whether the application server is reported as active. It does not perform a check at the monitored server itself to see whether, for example, it is possible to log on. This monitoring is possible for both Java and ABAP application servers, since CCMSPING can communicate with both the ABAP and Java message servers, depending on the communication settings of the system.

Important performance attributes from the dialog service of the server are also reported in availability monitoring for ABAP application servers (see Availability and Performance Overview Monitor). The prerequisite for this is the existence of logon groups in the corresponding system.

¡ Check Logon

With this monitoring type, the monitoring architecture performs an RFC call in the relevant server. Although no actual logon is performed, you can, however, determine whether it is possible to log on ‑ since the RFC call requires a free dialog work process, in the same way as a user logging on does. This method also checks whether the database of the monitored system is functioning and is connected to the system. This monitoring is only possible for ABAP application servers.

This type of RFC call is not subject to the quotas that you can set with the various profile parameters with the prefix rdisp/rfc to prevent overloading due to RFC calls (see System Configuration for Parallel RFCs).

· Monitoring the logon groups

You can check whether it is possible to log on to the currently selected ABAP application server of a logon group (see Logon Load Balancing). This function uses the same technique to do this as Check Logon.

Prerequisites

This procedure is part of the Configuring Availability Monitoring process. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure.

Procedure

The system is displaying the Configure Availability and Performance Overview screen. To create or change a monitoring rule for one or more systems, follow the procedure below:

...

1. Select the desired systems by choosing the folder symbol for the corresponding systems.

Note that a system is only correctly selected when the entire line is highlighted:

2. Proceed as follows, depending on whether the desired systems are already monitored:

¡ To create an availability rule for a system that has not been monitored until now, choose Monitoring ® Activate System Monitoring in the Unmonitored Systemssubscreen. This activates the monitoring for this system; confirm the relevant query.

To assign an identical monitoring rule to multiple systems that were not previously monitored, select these systems, and choose Monitoring ® Define Uniform Monitoring.

¡ To change the availability rule for a monitored system, choose Monitoring ® Change Connection/Options in the Monitored Systemssubscreen.

To assign an identical monitoring rule to multiple monitored systems, select these systems, and choose Monitoring ® Use Uniform System Options.

3. The Connection Data and Monitoring Options screenappears. The screen has the following structure:

Make the following entries in this screen:

4. Save your entries.

Result

You have created or changed a monitoring rule for the selected systems, on the basis of which the corresponding systems will be monitored. To further refine monitoring, for example, to change the monitoring of individual application servers or logon groups, follow the instructions in Changing Monitoring Settings for Servers and Groups.

Availability Monitoring with CCMSPING start page

Sometimes, internal user or customer might request you to change the Title of the SAP Transaction code to a more meaningful one.

The steps are as follows:

Goto tcode SE63 . On the top left Menu of the screen - Click Translation ---> Short texts - --> Transactions

For example, assuming you want to change the title of the t-code su10 from user maintenance: Mass changes Initial Screen to Mass User changes . On the first screen, fill in the following information:

Transaction code - SU10

Source Language - English

Target Language - English

To change the Title, click the Edit button. On the second line (the one in dark yellow), type in the Title (For e.g. Mass User changes) you want for the transaction code. Click the Save button

Now, call up the transaction code /nSU10 again and you should be able to view the new Title.

Sometimes, internal user or customer might request you to change the Title of the SAP Transaction code to a more meaningful one and SAP allows this to be done painlessly.

The steps to change the Title of any SAP transaction code are as follows:

First, goto tcode SE63

On the top left Menu of the screen - Click Translation - Short texts - Transactions

For example, assuming you want to change the title of the tcode FB01 from Post Document to Post Document for G/L. On the first screen, fill in the following information:

Transaction code - FB01

Source Language - English
Target Languate - English

To change the Title, click the Edit button

On the second line, type in the Title (For e.g. Post Document for G/L) you want for the transaction code

Click the Save button

Now, called up the transaction code /nFB01 again and you should be able to view the new Title.

Please note that it works for most of the Transaction code except for those new Enjoy transaction code in 4.6x.

To change the SAP Pre-defined objects, the ABAP developers need an Object Key, to request an Object Key please go through the following link:-

http:\service.sap.com\sscr

Keyword: BASIS
Title : CCMS Monitoring : Creating and Changing Monitors

Sometimes, internal user or customer might request you to change the Title of the SAP Transaction code to a more meaningful one.

The steps are as follows:

Goto tcode SE63 . On the top left Menu of the screen - Click Translation ---> Short texts - --> Transactions

For example, assuming you want to change the title of the t-code su10 from user maintenance: Mass changes Initial Screen to Mass User changes . On the first screen, fill in the following information:

Transaction code - SU10

Source Language - English

Target Language - English

To change the Title, click the Edit button. On the second line (the one in dark yellow), type in the Title (For e.g. Mass User changes) you want for the transaction code. Click the Save button

Now, call up the transaction code /nSU10 again and you should be able to view the new Title.

Please note that it works for most of the Transaction codes. The t-code is available from from version 4.6x.

Steps to change the default SAP IMAGE on the right hand column of the screen :-

Transaction code - SMW0
X - Binary data for WebRFC application
Hit Enter
Click Execute
Click Settings -> Maintain MIME types
Click the Create button
Fill in :- TYPE : image/gif EXTENSION : .GIF
Click Save
Click Back to the Binary data for WebRFC
Click Create
Fill in :- Obj. name : ZXXXX.GIF Description :
Company Logo
Click Import and specify the filename where your
GIF file is
located.File type is BIN. Finish press the
Transfer button.
If successful, your logo will be shown in the
Binary data for
WebRFC.
Transaction code SM30 - Table/View - SSM_CUST
Click Maintain
Click New Entries
Name Value to be set
START_IMAGE ZXXXX.GIF
RESIZE_IMAGE NO
Logoff and Login again

If the CCMS Alert Monitor or Transaction ST06 (see Monitoring the Status of the R/3 System) displays a high paging rate for the operating system, decrease the size of the roll and paging buffers (only Windows NT and UNIX). In the profile management of the CCMS, set the profile parameters rdisp/ROLL_SHM and rdisp/PG_SHM to 0. You must change the profiles used by the R/3 application servers on the relevant host system.

If free memory is available even during heavy system usage, or if there is only low paging activity, you can increase the size of the roll and paging buffers. This decreases the accesses to the hard disk caused by rolling and paging.

Keyword: BASIS
Title : Changing SAP MaxDB Database Properties

Prerequisites

You are on the Maintain Applicant Activities screen.

Procedure

1. Select the desired activity, and choose Edit
® Planned <-> Completed.

The system displays a screen entitled Change mode planned -> completed or Change mode completed -> planned.

2. Enter data in the Performance field.
3. Choose Planned -> Completed or Completed -> planned.

The Maintain Applicant Activities screen appears.

4. Save the activity.

Result

Prerequisites

You are on the Maintain Applicant Activities screen.

Procedure

1. Either create a new applicant activity from scratch, create a new activity by copying an existing one, or change an existing activity. Proceed as follows:

In order to:	Perform the following action:	The following screen appears:
Create a new planned activity	Choose Edit ® Create planned activity	Create Planned Activity, or Create Completed Activity
Create a new completed activity	Choose Edit ® Create completed activity	Create Planned Activity, or Create Completed Activity
Create an activity by copying from an existing activity	Select the planned or completed activity you want to copy, and choose Copy activity.	Create Planned Activity, or Create Completed Activity
Change an activity	Select the planned or completed activity you want to change, and choose Change activity.	Change Planned Activity, or Change Completed Activity



Activities created by copying are automatically assigned the same status (planned/completed) as the activity copied.

The data transferred to the fields of a copied activity are default values, and can be overwritten, if required.

2. In the Activity type field, enter the key for the activity type, and, in the Performance date field, the desired performance deadline. Make any other necessary entries.
3. To send an e-mail to the person responsible for the activity, or the appropriate administrator, select Send mail.
4. To create a note for the activity, choose Maintain notes.
5. Choose Transfer.

This takes you back to the Maintain Applicant Activities screen.

6. Save the activity.

Result

Use