SYSTEM monitoring , RFCs

Hi All
  I want to setup system monitoring from solution manager 7.0 for other satellite systems (4.6) .
Satellite systems have already been added in the System landscape (Tcode -SYSY) and also I have already enabled EWA , SL reporting and they are getting generated properly in solution manager .
Do we need to create RFCs for CCMS read destination and CCMS Login destination to enable system monitoring for those satellite systems . If yes, then are they will be created for client 000 ??
Waiting for suggestions.
Links and documents will also be appreciated...
Still waiting for your suggestion , Experts
Edited by: Rocky on Jun 9, 2008 1:53 PM

As recommended by some colleagues I am also investigating Customer Center of Excelence as a reference to define roles and responsibilities, particularly in the concept of Application Lifecycle Management.  
Any other input is welcome.
Regards
Esteban

Similar Messages

  • RFC destinations for system monitoring could not be assigned

    Hi,
    I am having 2 system landscape DEV (DEV/QA), PRD. I want to monitor both system from Solution manager and created both system, db, server & logical component in SMSY.
    Problems:
    1. System not allowing to assign RFC for (PRD) system monitoring where as it is working for DEV system.
    2. When running System monitoring setup only PRD is showing there, both server/system should be shown ?
    3. When i am tring to assign system in RZ21 manully then also system giving error in case of PRD server. where as DEV system is created in RZ21 -->> Technical Infra. --->>> Display topology (Error when calling the underlying C function (function 'SALS_MS_GET_LOCAL_MS_INFO')
    Message no. RA336)
    Please help me to solve this issue.
    Thanks & Regards,
    Tejinder

    Hello Arwel,
    if the solution manager should monitor itself via EWA, you have to set "mySAP.com Support Workplace system" to "NONE". To get there, start transaction SDCC in you solution manager system -> Maintenance -> remote enviroment -> default target system.
    Hope that will help you.
    regards,
    Marco

  • Monitoring RFCs on Remote Systems

    Hi,
    I am attempting to convert our CCMS monitoring to a central instance on solman. One of the things we monitor in the PRD system is availability of two RFC destinations.
    I am unable to figure out how these can be monitored from solution manager as a central system. When I set these up in solman under availability monitoring, it appears that solman is expecting these RFC destinations to be local to solman, rather than on the PRD system.
    How can I get solman to monitor the RFC on PRD? It does not appear that the RFC availability monitoring method allows you to specify which system the RFC resides on.
    Thanks much,
    Chris.

    Hi,
    ok I will try to explain how get to see the MTE's of ur PRD system.
    1.   TA: RZ20
    2.   change in maintenance mode (Extras -> Activate Maintenance Mode)
    3.   now u r able to create a new monitor set. So please do this by clicking on the create button.
    3.2 place a describing name and select who should be able to see this set. Click OK and now u will see ur new own monitor set
    4.   Click one time on that set and click one more time on the create button. Now u will get an list with all monitored Systems, that are connected to the solution Manager. Search in the PRD System the MTE u like to see and save ur new monitor with an discribing name.
    5. Hopefully if I'm forgottin' nothin u will see after save and activate ur objects from the managed System in the CEN System.
    So if anything is missing feel fre and contact me ...
    br Lars

  • RFC configuration for system monitoring / Early Watch reports

    Hello Basis Gurus:
    Please help me out.....
    The early watch reports in the solution manager of my system are failing consistently to execute.This is happening for all the 3 systems DEV,QAS,PRD.when i click on individual earlywatch reports it takes me to a screen which says  "data for this report is overdue.....go to your satellite system SDCCN to see why the data was not sent...."
    It says ...check the following things.....
    "The RFC connection for the SAP Solution Manager system is not working.
    The 'Task Processor' background job, which collects the session data, has been changed.
    Problems arose while data was being collected (see the detail log for the task that collects the session data).
    A periodic 'SDCC Maintenance Package' task has not been scheduled to check whether your SAP Solution Manager system requests session data."
    I can see the task processor job , and the periodic Maintenance package scheduled everyday and completed sucessfully.So is it the RFC which is causing the problem.
    Im SM59 of the solman, i can see system generated RFCs for the PRD,DEV,QAS and SND  (...3 for each of these systems...).
    say for PRD, these are the 3 RFCs.
    1.)SM_PRDCLNT<client#>_READ.
    2.)SM_PRDCLNT<client#>_TMW.
    3.)SM_PRDCLNT<client#>_TRUSTED.
    I am not sure which RFCs among the 3 for any given system does the solman use to communicate to the satellite systems.
    *The user id section in the Logon Data of any of these RFCs is blank.and the password says "is initial"...*is this correct.Does the user id have to be a communication type of user...
    PLeaase advise as to what could be going wrong..
    Regards.

    Hi,
    The system uses ABAP Connection (Connection Type 3) to connect to different Systems to execute Functional Calls.
    Now in your case, there are 3 different connections meaning your Basis Team has used 3 connections for different connection activities. This is totally a business dependent scenario.
    Now each time you create a RFC Connection, the system will need the following information to remotely call another system, they are:
    Host Details of Target System
    Logon Details to remotely login
    For RFC Connections the User Type has to be Communications User. But there are companies which use Dialog User Types as well to remotely login for some cases. When the User ID is created for an RFC User and a Password is assigned to it, this Password is considered as the Initial Password by the system. This Password is taken as the Initial Password in the RFC Connection as well.
    There can be cases where the system is Trusted and there is no need of a password, but an Username is mandatory in all cases. Remember if you set the system as Trusted, the password option gets deactivated and the connection wont work, if the system does not have the Trusted status.
    But in any case you must assign the Username alongwith the Client and Language Details in the RFC Connection for it to work.
    Hope this helps.
    /Manoj

  • System monitoring - alert email notification

    Hello Sapers,
    I already set up system monitoring in our Solution Manager but i would like to receive mail if any alert occur.  Unfortunatelly I did not find any way how to do it through Solution Manager. I guess there must be something like edit -> Automatic email transmission where I set up sending Earlywatch and SL reports to my mailbox, but how to set up alert email notification?
    I also tried another way - setting up CEN (in our sollution manager) in RZ20, there i created monitor where i have desired alerts from all remote systems configured in SMSY (i have not used sapccm4x or any other ccms agent), also tried autoreaction method on local and it is working fine (SCOT is set up) but when i tried create and assign central autoreaction method (sapnote 429265) during assigning i receive error "no ccms agent avalable for system" and it is not working. Do I really need configure SAPCCM4X on all remote systems when i want to use central autoreaction? I dont feel very confortable with this solution. I think there must be some other smarter way (maybe in solution manager).
    We also tried to connect our RZ20 monitor set to nagios (used in our company to monitor non sap servers and email notification), but we are not able to compile the ccms nagios plugin uder 64bit. AIX 5.3.
    I also heard little bit about ALM (Alert management) but dont know anything about forwarding alerts from RZ20 to ALM and transmitting email from there. But I think this sollution would be the most difficult from all mentioned above.
    Thank you very much for any help

    Josef,
      Somewhat chasing the point here - when you have the Solman and you look in your CCMS and you can see the other systems - it is all RFC data and not actually on the Solution Manager (the only local MTE's are those tha belong to the Solution Manager).  For the Solution Manager to Centrally Auto-React to threasholds (act as the CEN System), the information needs to be passed to the Central System through the agents.
      If you want to do email threasholds on your remote systems, you can configure it on each of the systems individually without agents as this is a CCMS Function that any SAP System can do - but this is not Central Auto-Reaction.  This is just actions taken on individual systems based on local MTE's.
      To Centrally Auto-React - you have to add the agents so the information is passed to the CEN to react on.
      I hope that this has clarified the situation a bit more.  If this answers your question, please set this thread to answered.

  • System Monitoring - Solman 7 EHP1

    Hi
    Solution Manager 7.0 EHP1 / Windows 2008 / Oracle
    Satellite System R/3 Enterprise extn set 110 / Solaris on Sparc / Oracle
    I am having trouble configuring System monitoring on solution Manager. Here is what I have done
    Added the satellite system to SLD, Configured data collector (RZ70) in the satellite system, Pushed data from SLD to SMSYS (automatic transfer).
    Installed CCMS agent + CCMSPING agent in satellite system. Checked connectivity in solman with RZ21. Connectivity is fine.
    Created Monitor sets and monitors in CCMS for monitoring satellite system. Client data is visible in CCMS.
    Created a solution in DSWP. Created logical component in SMSY. Assigned the logical component to the solution. Now I can see the data in DSWP.
    Here are my questions
    ==================
    1. In DSWP, everytime I have to view data, I have to click on "Setup System Monitoring" to view the alerts in the satellite system
    I see a red alert reading for instance availability. Similarly,
    In the system monitoring workcenter, I see the status of both the solution manager and the satellite system greyed out with a cross. When I move my mouse over it, it reads, no CCMSPING data available.
    Any idea as to why this happens?
    2. For what I see after I click on "Setup System Monitoring" I have parameters which I can configure. I see default values for these parameters. Is there like a recommendation or a template which can be used to setup these monitoring parameter values?
    3. I have configured the ccmsping in the solution manager (for the solution manager) however the ccmsping service refuses to run. It throws a error reading "The system could not find the file specified". The ccmsping exe file is present in the location stated. Are there other files that this is looking for?
    4.  While registering the agent in the satellite system, I first registered with the CSMREG id. It failed with the message,
    INFO: [SMG:040:CSMREG] connected to SMG, host sapsm.NA.XXX.NET, System Nr. 00, traceflag [ ]
    INFO: SMG release is 701 , (kernel release 701 )
            RFC Error Info:
             message:
             status:  EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
             intstat:
          Go Ahead anyway?  n/[y] :
    INFO: handling destination SAPCCM4X.SAPR3PR1.00
    ERROR: can't register at SMG. RfcRc = 2, AUTHORITY_NOT_AVAILABLE
    RFC Error Info for SALF_CSM_AGENT_REGISTER
    message:
    status:  EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
    intstat:
    I then did this with a dialog user. That worked. Agent was registered in solution manager. Any idea on why this error would show up with the CSMREG? I am concerned about issues which can come up when the password for the dialog user changes.
    I am not sure how to upload screenshots of what i see, probably if i do that, it will be easy to relate to the issue which I am mentioning here. Is there a way I can do that?
    Let me know if you need any more information from my side to understand this.
    Ideas will be appreciated.
    thanks
    Ravi

    Hello Ravi,
    Additionally you will want to look at SAP Note 1175058 - Problems with CCMSPING in SAP Solution Manager, especially
    c) Ensure that the message server host name in the monitoring options of CCMSPING and the message server of the corresponding main instance of the relevant system is the same in the SAP Solution Manager landscape
    (SMSY). Important: The monitoring options of CCMSPING must not be configured using an IP address.
    Regards,
    Paul

  • System Monitoring in Solution Manager

    Friends
    1.System monitoring for one of the satellite systems has been configured in solution manager (through DSWP - Setup system monitoring) using RFC connections(Read and Trusted RFCs generated in SMSY).
    2.Installed CCMS Agent on the satellite system and registered to solution manager system.
    RZ21 -> Remote Agent Status shows online.
    Should something else to be done (settings, background jobs, configuration )in Solman or satellite system to make  communication to satellite via CCMS agent primary for system monitoring?
    How do i get to see the satellite system's monitoring context in Solution manager?
    Please help me out
    Thanks
    Gnana

    Friends
    1.System monitoring for one of the satellite systems has been configured in solution manager (through DSWP - Setup system monitoring) using RFC connections(Read and Trusted RFCs generated in SMSY).
    2.Installed CCMS Agent on the satellite system and registered to solution manager system.
    RZ21 -> Remote Agent Status shows online.
    Should something else to be done (settings, background jobs, configuration )in Solman or satellite system to make  communication to satellite via CCMS agent primary for system monitoring?
    How do i get to see the satellite system's monitoring context in Solution manager?
    Please help me out
    Thanks
    Gnana

  • Solution Manager System Monitoring of a CE 7.10

    Hi
    I am trying to setup a Solution Manager Monitoring Solution for a CE 7.10 Enviroment.
    I have already setup CEN in SOLMAN.
    I have registered CE Systems with a sapccmsr j2ee agent.
    I have setup the JCO RFC Connection in CE.
    I have created the TCP/IP Connection to the JCO Connection in Solman.
    I have set the TCP/IP Connection in RZ21 as the J2EE Customizing Destination.
    The solution involves only 1 Logical Component with 3 CE Systems.
    When I go to the solution manager setup and try to configure the MTE Nodes for my solution I cannot get the MTE context while clicking in Activate Monitoring for other Software Components
    I choose Java Application Server, choose my server, choose CEn but when i have to choose the context of the MTE i get an empty list.
    IF i go Activate Monitoring for Other Servers and choose the server I get the contexts of the remote server, but I can only choose one.
    So how can I see the context of the CE servers in the Software component part?
    Ty.

    Hi,
    Have you defined and added corresponding logical systems for the respective satellite systems?
    Here is the sequence of steps you've to do:
    in SMSY:
    1) Define server, DB, Systems
    2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
    3) define logical systems and assign the satellite system to it
    in Solution_Manager:
    1) define new solution
    2) add the logical system into the solution
    If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
    Have you already done these steps?
    After performing these steps:
    Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
    Your system will then appear.
    Does this help any way?

  • Solution manager system monitoring configuration

    Hi
    I am configuring system monitoring in solution manager (Oracle / Solman 7.0 EHP1 / Windows 2008 / VM)
    I have added a satellite system to solution manager thru CCMS and CCMSPING agents. These are visible in RZ21 / Technical infrastructure / Overview. This has also been added in SMSY, SMSY when refreshed pulls out data from the satellite system. However I am having trouble with the transaction SOLUTION_MANAGER. This is where I setup system monitoring.
    Here I find the solution maanger system however am not able to find the satellite system which I had added.
    Thoughts?
    thanks
    Ravi

    Hi,
    Have you defined and added corresponding logical systems for the respective satellite systems?
    Here is the sequence of steps you've to do:
    in SMSY:
    1) Define server, DB, Systems
    2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
    3) define logical systems and assign the satellite system to it
    in Solution_Manager:
    1) define new solution
    2) add the logical system into the solution
    If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
    Have you already done these steps?
    After performing these steps:
    Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
    Your system will then appear.
    Does this help any way?

  • System Monitoring in Solution Manager 4.0

    Hi all,
    I want to set up system monitoring for landscape BW, ECC and SCM systems using Solution Manager 4.0 and am new to Sol Man.
    So could anyone please help me with the steps.
    Thanks in advance,
    Sandeep.

    Sandeep,
    Trust me, there is no one resource that you can refer to and complete this system monitoring project. I recently configured this a couple of days ago. I can tell you that I haven't completed it yet. I have only completed the configuring the 'System Monitoring' part of it. I am yet to define monitors so that, I can monitor what I want of the satellite systems. So far, it took me about 4 days. Let me point out the basic steps you need to follow. Beyond that, please refer to the links I paste below:
    Steps to configure 'System Monitoring' in Solution Manager:
    1. Follow the 'Solution Manager Preparation' found under SPRO --> Solution Manager --> Read Me.
    2. Make sure you have the latest ST-ICO and ST-SER installed in your Solution Manager (Note: 892412).
    3. Make sure the Solution Manager has the latest support packages applied.
    4. Prepare the 'Satellite Systems' as per note 455356:
         a. Create the role 'SAP_BC_CSMREG' (if it doesn't exist) with the following authorization objects
              --> S_CCM_RECV (with the objects and values mentioned in the above note)
              --> S_RFC (with the objects and values mentioned in the above note)
              --> S_RZL_ADM (with the objects and values mentioned in the above note)
              --> S_CUS_CMP (with the objects and values mentioned in the above note)
         b. Create a 'communication' user CSMREG (if it doesn't exist) and assign the profile S_CSMREG
    5. Create the user CSMREG in Solution Manager using RZ21 transaction
              -->RZ21 --> Technical Infrastructure --> Configure Central System --> Create CSMREG user (Provide the required password and confirm).
    6. An agent needs to be registered in all the satellite systems that collects the monitor statistics and pass on to the Solution Manager. Before registering the agent in the satellite system, a 'CSMCONF' file has to be generated in the Solution Manager and store it in a central location which, will be used by the CCMS agent while registration. This CSMCONF file holds the communication details for the agent to talk to the Solution Manager. To create CSMCONF file, proceed as follows:
              --> RZ21 --> Technical Infrastructure --> Configure Central System --> Create Start CSMCONF for Agents
              --> Store the file in a central location that can be accessed by the satellite system/s.
    7. In the satellite system, copy the file 'CSMCONF' to the working directory of SAPCCM4X (F:\usr\sap\PD1\SYS\DVEBMGS01\log\sapccm4x - for example. If the 'sapccm4x' folder does not exist, create one).
    8. Copy the downloaded 'SAPCCM4X.exe' file to the kernel directory on the satellite system.
    9. Execute "sapccm4x -R pf=<path of the instance profile>". This should ask for the 'CSMREG' password and the admin user password on the solution manager system. Please input the same and confirm other questions. Upon confirmation, the CCMS agent should be registered in the satellite system.
    10.Make sure you establish the trusted RFC connection on the Solution Manager to the satellite system you would want to monitor. This you can do from 'SMSY' transaction.
    11.After successfully creating the RFC connections, and assigning the system to a logical component, please go to transaction, 'SOLUTION_MANAGER'. You can see the monitored system in the System Overview.
    Below are the reference links:
    Weblogs Related to Solution Manager
    Hope this helps. Award with relevant points if my response is helpful.
    Thank you.

  • System Monitoring with Solution Manager Ehp1

    Hi,
    I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
    Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
    Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
    when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
    <SID>_RZ20_COLLECT
    <SID>_RZ20_ANALYZE
    I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
    <SID>_RZ20_COLLECT_123539Error when opening an RFC connection
    Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
    Error during remote call of SALC function: Error when opening an RFC connection
    Error during remote call of RFC1 function: Error when opening an RFC connection
    I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
    Please, Could you help me?
    Thanks and regards,
    Tomas.

    Tomas,
    I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system).  I downloaded the lates ccmsagent file from the market place based my target system configurations.
    Herewith attaching the logs while I'm trying to check the profile parameter.
    tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    ================================================================================
    ==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    ================================================================================
    ***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
    ***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
    ***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
    ***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
    ***WARNING: Unexpected parameter: dbs/io_buf_size =100000
    ***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
    ***WARNING: Unexpected parameter: rsau/selector1/class =35
    ***WARNING: Unexpected parameter: rsau/selector1/severity =2
    ***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
    ***ERROR: Size of shared memory pool 40 too small
    ================================================================
    SOLUTIONS: (1) Locate shared memory segments outside of pool 40
                   with parameters like: ipc/shm_psize_<key> =0
    SOLUTION: Increase size of shared memory pool 40
              with parameter: ipc/shm_psize_40 =1472000000
    Shared memory disposition overview
    ================================================================
    Shared memory pools
    Key:   10  Pool
                Size configured.....:   642000000 ( 612.3 MB)
                Size min. estimated.:   637597428 ( 608.1 MB)
                Advised Size........:   640000000 ( 610.4 MB)
    Key:   40  Pool for database buffers
                Size configured.....:  1048000000 ( 999.4 MB)
                Size min. estimated.:  1468229308 (1400.2 MB)
                Advised Size........:  1472000000 (1403.8 MB)
    Shared memories inside of pool 10
    Key:        1  Size:        2500 (   0.0 MB) System administration
    Key:        4  Size:      523648 (   0.5 MB) statistic area
    Key:        7  Size:       14838 (   0.0 MB) Update task administration
    Key:        8  Size:    67108964 (  64.0 MB) Paging buffer
    Key:        9  Size:   134217828 ( 128.0 MB) Roll buffer
    Key:       11  Size:      500000 (   0.5 MB) Factory calender buffer
    Key:       12  Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
    Key:       13  Size:   200500000 ( 191.2 MB) Alert Area
    Key:       16  Size:       22400 (   0.0 MB) Semaphore activity monitoring
    Key:       17  Size:     2672386 (   2.5 MB) Roll administration
    Key:       30  Size:       37888 (   0.0 MB) Taskhandler runtime admin.
    Key:       31  Size:     4806000 (   4.6 MB) Dispatcher request queue
    Key:       33  Size:    39936000 (  38.1 MB) Table buffer, part.buffering
    Key:       34  Size:    20480000 (  19.5 MB) Enqueue table
    Key:       51  Size:     3200000 (   3.1 MB) Extended memory admin.
    Key:       52  Size:       40000 (   0.0 MB) Message Server buffer
    Key:       54  Size:    20488192 (  19.5 MB) Export/Import buffer
    Key:       55  Size:        8192 (   0.0 MB) Spool local printer+joblist
    Key:       57  Size:     1048576 (   1.0 MB) Profilparameter in shared mem
    Key:       58  Size:        4096 (   0.0 MB) Enqueue ID for reset
    Key:       62  Size:    85983232 (  82.0 MB) Memory pipes
    Shared memories inside of pool 40
    Key:        2  Size:    31168040 (  29.7 MB) Disp. administration tables
    Key:        3  Size:   114048000 ( 108.8 MB) Disp. communication areas
    Key:        6  Size:  1064960000 (1015.6 MB) ABAP program buffer
    Key:       14  Size:    28600000 (  27.3 MB) Presentation buffer
    Key:       19  Size:    90000000 (  85.8 MB) Table-buffer
    Key:       42  Size:    13920992 (  13.3 MB) DB TTAB buffer
    Key:       43  Size:    43422392 (  41.4 MB) DB FTAB buffer
    Key:       44  Size:     8606392 (   8.2 MB) DB IREC buffer
    Key:       45  Size:     6558392 (   6.3 MB) DB short nametab buffer
    Key:       46  Size:       20480 (   0.0 MB) DB sync table
    Key:       47  Size:    13313024 (  12.7 MB) DB CUA buffer
    Key:       48  Size:      300000 (   0.3 MB) Number range buffer
    Key:       49  Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
    Shared memories outside of pools
    Key:       18  Size:     1792100 (   1.7 MB) Paging adminitration
    Key:       41  Size:    25010000 (  23.9 MB) DB statistics buffer
    Key:       63  Size:      409600 (   0.4 MB) ICMAN shared memory
    Key:       64  Size:     4202496 (   4.0 MB) Online Text Repository Buf.
    Key:       65  Size:     4202496 (   4.0 MB) Export/Import Shared Memory
    Key:     1002  Size:      400000 (   0.4 MB) Performance monitoring V01.0
    Key: 58900130  Size:        4096 (   0.0 MB) SCSA area
    Nr of operating system shared memory segments: 9
    Shared memory resource requirements estimated
    ================================================================
    Nr of shared memory descriptors required for
    Extended Memory Management (unnamed mapped file).: 64
    Total Nr of shared segments required.....:         73
    System-imposed number of shared memories.:       1000
    Shared memory segment size required min..: 1472000000 (1403.8 MB)
    System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
    Swap space requirements estimated
    ================================================
    Shared memory....................: 2050.4 MB
    ..in pool 10  608.1 MB,   99% used
    ..in pool 40  999.4 MB,  140% used !!
    ..not in pool:   34.4 MB
    Processes........................:  716.8 MB
    Extended Memory .................: 8192.0 MB
    Total, minimum requirement.......: 10959.2 MB
    Process local heaps, worst case..: 1907.3 MB
    Total, worst case requirement....: 12866.5 MB
    Errors detected..................:    1
    Warnings detected................:    9
    After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
    Pls have a look at these two and let me know what could I do to proceed further.
    tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
    INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
    INFO: Central Monitoring System is [SMP]. (found in config file)
          additional CENTRAL system y/[n] ?   :
    INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
    INFO:
          CCMS version  20040229, 64 bit, multithreaded, Non-Unicode
          compiled at   Jun 28 2010
          systemid      324 (IBM RS/6000 with AIX)
          relno         6400
          patch text    patch collection 2010/1, OSS note 1304480
          patchno       335
    INFO Runtime:
          running on    saptqa01 AIX 3 5 00069A8FD600
          running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
    INFO profile parameters:
          alert/MONI_SEGM_SIZE = 200000000
          alert/TRACE          = 1
          SAPSYSTEM            = 30
          SAPSYSTEMNAME        = TQA
          SAPLOCALHOST         = saptqa01
          DIR_CCMS             = /usr/sap/ccms
          DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
          DIR_PERF             = /usr/sap/tmp
    INFO:
          pid           4165682
    INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
    INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct  3 2008,  kernel 6400_20020600_254,  platform 324 (IBM RS/6000 with AIX)]
            segment status     ENABLED
            segment started at Tue Sep 14 09:35:56 2010
            segment version    20040229
    ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
           Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
           Please change configuration with profile parameters
               ipc/shm_psize_01 = -<different pool nr>
           xor
               ipc/shm_psize_13 = -<different pool nr>
    EXITING with code 1

  • System Monitoring Setup in Solution Manager

    Hello Experts,
    We are going to implement and configure Solution Manager - System monitoring setup for pre testing purpose
    Currenly we have installed below SAP Systems
    1.Solution Manager Server
    2.ECC server (Without Ides) - Abap
    3.CRM Server (Without Ides) -Abap + Java
    We need to setup below tasks in Solution Manager
    1.Early watch alert
    2.System Monitoring
    3.Central System Administration
    4.Business Process Monitoring
    5.Service Level reporting
    1.Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
    Could you please someone give input reg this.
    Thanks
    Thirumal
    Edited by: Thiru Thirumal on Aug 6, 2008 4:56 AM
    Edited by: Thiru Thirumal on Aug 6, 2008 4:57 AM

    Hi,
    Q. Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
    A. Yes.
    Check with links for
    1.Early watch 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 u2013 Connections between: and an RFC u2013 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
    2.System Monitoring
    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.
    3.Central System Administration
    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, u201EBPMu201C 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 u201EOther CCMSu201C 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.
    4.Business Process Monitoring
    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
    5.Service Level reporting
    http://service.sap.com/solutionmanager for all solman tasks as given below.
    http://www.asap.net.cn/homepage_en/Solution%20Manager%20EN.pdf
    http://help.sap.com/saphelp_sm32/helpdata/en/1b/f02c41ab78f66fe10000000a1550b0/content.htm
    http://help.sap.com/saphelp_sm32/helpdata/en/9f/1f46570f8a4a268b3154e0e0f07280/content.htm
    Regards,
    Srini Nookala

  • System monitoring configuration in solution manager EHP1

    Hi all
    I am in a bit of fix
    We have upgraded our solution manager devlopment to EHP1
    Now I have added one system through SMSY in solution manager to configure system monitoring
    I have generated all the RFC's,I have created the logical component and solution and assigned the system to the solution
    When I check my solution it is looking fine
    Now when I go within solution and click on the tab system monitoring
    It shows me on the left hand side -> Set up system monitoring
    when I click on Set up system monitoring on the left part of SAP screen,strangely it doesnt take me to the activation of screen monitoring,it just shows me the best practices documents on the right side but nothing more than that
    I have checked many guides,blogs and SAP tutors anfd have followed them but strangely I am not been able to go to the screen for activating system monitoring
    Are there any activities that need to be done after upgrading to EHP1?
    Are there any services to be activated for system monitoring?
    Please advice
    Rohit

    I'm not 100% sure that it is necessary, but it won't hurt.
    Perhaps the essential adjustment you need for system monitoring is being done in there.
    It won't hurt

  • Solution Manager System Monitoring for non SAP system

    Dear Support,
    I have configured the CCMS Agent (SAPCCMSR) for non-SAP system (Windows 2008R2).
    The system information (e.g. CPU, Memory, Disks etc) has already showed in RZ20 of Central Monitoring system (e.g. Solution Manager).
    How can I do to configure to display these information in the Alert Inbox tab on System Monitoring Workcenter?
    Best regards,
    Fan Hung

    Hi,
    Have you defined and added corresponding logical systems for the respective satellite systems?
    Here is the sequence of steps you've to do:
    in SMSY:
    1) Define server, DB, Systems
    2) Generate READ, TMW, TRUSTED RFCs to the satellite systems
    3) define logical systems and assign the satellite system to it
    in Solution_Manager:
    1) define new solution
    2) add the logical system into the solution
    If these steps are successful, you should be able to see the satellite system in SYSTEM MONITORING in Solution_Manager.
    Have you already done these steps?
    After performing these steps:
    Solution_Manager>choose relevant solution>operations setup>Solution Monitoring>System monitoring>Activate monitoring> choose the system and activate monitoring.
    Your system will then appear.
    Does this help any way?

  • Database component is not displayed in system monitoring

    hi all
    I configured system monitoring but I can`t see Database conponent (ex.SID_database) .
    I can see another components that are servers and systems (ex.host_SID_SNO)
    I checked database in SMSY and rfc commuication is trustconnection between SOLMAN and ERP
    Another Servers (ex. BW, XI, EP) are displayed Database component.
    how can I solve this problem
    thanks

    hi, Andreas
    thanks for your reply
    I tried but same.
    any help plz

Maybe you are looking for