CCMS In sap PI

  • View

  • Download

Embed Size (px)

Text of CCMS In sap PI

  • 8/13/2019 CCMS In sap PI


    SAP Buffers


    Each SAP instance (application server) has its own buffers. These buffers are also known as client caches be

    they are implemented on the client, that is, the application server. SAP buffers occupy memory areas that are the work process, and in individual shared memory sements that can be accessed by all work processes. Thmemory areas are e!ecuted for the application server.

    Some of the shared memory sements in an SAP System are rouped into one shared memosement known as a pool. This is done to meet the operatin system limits on the number of smemory allocations per process. "n most operatin systems, you can allocate as many sharedmemory sements as re#uired. The limits depend on the kernel confiuration. The A"$ operatsystem, for e!ample, allows %& shared memory sements per process.

    SAP buffers store fre#uently'used data, and make this data available to the local application server instance. Thelps to reduce the number of database accesses, the load on the database server (it does not need to be accrepeatedly to obtain the same information), and network traffic. As a result, system performance is considerabimproved.

    The data that is buffered includes AAP prorams and screens, AAP ictionary data, and company'specificTypically these remain unchaned durin system operation.

    *ou can chane, ortune, the si+es of buffers to optimi+e performance for a particular hardware confiuration. are several ways to tune buffers. As there are many constraints to consider when chane the buffer si+e, sevedifficulties may arise.

    *ou can use table bufferin to fine'tune applications, that is, some or all of the contents of infre#uently chanecan be held in local buffers.

    SAP Buffers

    Program Buffer This buffer occupies a whole shared memory sement.

    Generic Buffer

    Screen BufferThese buffers are held in a shared memory pool. All work processes caaccess this pool.

    Roll Area ocal work process buffers. -nly one work process can access these ba time.
  • 8/13/2019 CCMS In sap PI


    Monitoring in the CCMS


    The CCMS provides a range of monitors for monitoring the SAP environments and its components. T

    monitors are indispensable for understanding and evaluating the behavior of the SAP processing

    environment. In the case of poor performance values, the monitors provide you with the informationreuired to fine tune your SAP system and therefore to ensure that your SAP installation is runningefficiently.

    Implementation Considerations

    !or central monitoring, that is, for the monitoring of a system landscape from one system, you must p

    various configuration steps yourself. These are outlined in Configuring the Monitoring Architectur


    The CCMS analysis monitors provide functions for

    heckin the system status and the operatin modes

    etectin and correctin potential problems as #uickly as possible An early dianosis of potential problems, such as resource problems in a host or database system, whi

    could affect the SAP system

    The analysis and fine tunin of the SAP system and its environment (host and database system) to opt

    the throuhput of the SAP system

    The previous monitorin and alert system in the /S was replaced by the monitorin archite

    The new monitorin architecture provides all of the functions that previously e!isted as well as nemore reliable alerts and more comple!, more powerful functions.


    "ou can either use the following monitors independently or e#ecute them as analysis methodsin thmonitor$

    0lobal 1ork Process -verview

    1orkload /onitor

    0lobal 1orkload /onitor

    -peratin System /onitor

    -peratin System ollector

    SAP uffer

    atabase /onitor

    Global Wor Process !"er"ie#


    *ou can #uickly investiate the potential cause of a system performance problem by checkin the work proces*ou can use the lobal work process overview to2
  • 8/13/2019 CCMS In sap PI


    /onitor the work process load on all active instances across the s$stem

    "dentify locks in the database (lock waits).

    3sin the Global Work Process Overview screen, you can see at a lance2

    The status of each application server

    The reason why it is not runnin

    1hether it has been restarted

    The P3 and re#uest run time

    The user who has loed on and the client that they loed on to

    The report that is runnin

    See also%

    Selectin 1ork Processes

    isplayin etailed 1ork Process "nformation

    Selecting Wor Processes


    all /S ontrol4monitorin 1ork process overview. Alternatively, call Transaction S/55.

    hoose the Select process pushbutton.

    Select the work processes and statuses that you want to display more information on. *ou can also dinformation on specific prorams and users.


    hoose the work process type.


    *ou can select the work process statuses you are interested in.

    Runtime selection

    3se this option to select lon'runnin work processes.

    Application selection

    3se this option to select re#uests for specific 647 transactions.

  • 8/13/2019 CCMS In sap PI


    3se this option to select specific AAP48 prorams.

    User selection

    *ou can investiate the potential specific causes of a problem. "f you suspect that a particular user is work processes, enter the name of the proram or user, then choose Continueto filter the information

    'ispla$ing 'etailed Wor Process Information


    hoose CCMS Control/monitoringWork process overview.Alternatively, call Transaction S/55

    Position the cursor on the instance and choose Choose. *ou can terminate the proram that is curren

    runnin and debu it.

    9or backround processes, additional information is available for the backround :ob that is curunnin. *ou can only display this information, if you are loed onto the instance where the :runnin, or if you choose Settings and deselect Display only abbreviate in!ormation" avoi #any case, the :ob must still be runnin.

    Worload Monitor


    The workload monitor (transaction ST&7;) is intended for use by Early1atch and 0oinive teams. The work

    monitor was reworked as part of the En:oySAP initiative, so that the 1orkload -verviewis now simpler andintuitive.

    *ou use the workload monitor to analy+e statistical data from the SAP kernel. 1hen analy+in the performanc

    system, you should normally start by analy+in the workload overview.9or e!ample, you can display the toall instances and the compare the performances of individual instances over specific periods of time. *ou can

    determine the source of possible performance p