Enterprise Portal monitoring with Solution Manager

Dear guru's,
I have just installed a SAP Solution Manager 4.0
I would like to monitor a Enterprise Portal SP15.
Does someone have a walkthrough for this because very little information can be found on the sap help pages.
I'm interested in user/memory/iview statistics etc.
Hopefully someone of you has experience in this.
I would appreciate it alot.
Thank you
Kind Regards,
Bud

Hi Bud,
I've found useful docs here:
https://websmp109.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700001908512005E
and.
http://service.sap.com/nw04operation
-->Supportability --Solution Manager Diagnostics - Setup Guide SP Stack 16
bet regards
Wolfgang

Similar Messages

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

SABRIX/JBOSS monitoring with Solution Manager and Wily Introscope

Reading SCN discussions it is not quite clear to me if an extra (Wily) license is needed for monitoring SABRIX/JBOSS with Solution Manager and Wily Introscope. Does someone have experience in this area what exact to do?

Hi GSAP,
Please check this pdf file:
Wily Introscope a CA Product- Utility that Comes with Solution Manager Specifically for Java Monitoring
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50973df5-e1d1-2c10-cf89-c177fbfd7e65?QuickLink=index&…
Thanks
Vikram

Error while Regestring Enterprise portal system in solution manager

Dear Experts ,
recently we installed enterprise portal and now we required to register ep system in solution manager but i tried more and also checke in sdn & other sites but system is showing errors (system does not exist) i think i done mistakes in this process so ..
please give me steps for registering enterprise portel system in solution manager
Regards

Hello Swathi,
First get the EP system registered in the SLD connected to the Solution Manager system.
Then via Landscape Fetch job fetch the system data in SMSY. The system should automatically get created.
What are the errors that you are facing ?
Regards
Amit

SUP Monitoring with Solution Manager 7.1

We are currently on Solution Manager 7.1 SP6.
We currently have Sybase Unwired Platform system setup under managed system and
technical monitoring in Solution Manager. We have followed steps in note 1762741 but we are
receiving only high level alerts - sytem availability. No other alerts
are coming from any other SUP logs. Even though errors are in DB ,
server logs in SUP - we don't see any alerts.
All the Metrics are enabled. No errors in template.
Here's the example from SUP log files
E. 2013-03-06 14:09:12. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:12. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:14. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:28. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:28. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:28. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
I. 2013-03-06 14:09:42. <Main> Shutdown request from mlstop
I. 2013-03-06 14:09:42. <Main> MobiLink server shutting down
I. 2013-03-06 14:09:42. <Main> MobiLink server undergoing soft shutdown
I. 2013-03-06 14:09:42. <Main> No more new connections accepted.
Completing existing synchronizations
E. 2013-03-06 14:09:42. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:42. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:42. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:09:56. <Main> [-10002] Consolidated database server or
ODBC error: ODBC: [Sybase][ODBC Driver][SQL Anywhere]Database server
not found (ODBC State = 08001, Native error code = -100)
E. 2013-03-06 14:11:41. <Main> [-10124] The
Any help would be appreciated
Thanks

Hi Jyoti,
Are all your extractor working like they should?
Have you considered setting up log file monitoring by creating custom metrics and alerts?
Maybe this could help you bypass the issue.
Regards,
David

Basic Strategy / Best Practices for System Monitoring with Solution Manager

I am very new to SAP and the Basis group at my company. I will be working on a project to identify the best practices of System and Service level monitoring using Solution Manager. I have read a good amount about SAP Solution Manager and the concept of monitoring but need to begin mapping out a monitoring strategy.
We currently utilize the RZ20 transaction and basic CCMS monitors such as watching for update errors, availability, short dumps, etc.. What else should be monitored in order to proactively find possible issues. Are there any best practices you all have found when implimenting Monitoring for new solutions added to the SAP landscape.... what are common things we would want to monitor over say ERP, CRM, SRM, etc?
Thanks in advance for any comments or suggestions!

Hi Mike,
Did you try the following link ?
If not, it may be useful to some extent:
http://service.sap.com/bestpractices
---> Cross-Industry Packages ---> Best Practices for Solution Management
You have quite a few documents there - those on BPM may also cover Solution Monitoring aspects.
Best regards,
Srini
Edited by: Srinivasan Radhakrishnan on Jul 7, 2008 7:02 PM

Open Service Connection to Enterprise Portal system from Solution Manager

Hi All,
We are getting below error, when we tried to Enable/Open Service Connection ( DSWP -> Solution Landscape ->Service Connection) to Enterprise Portal system.
Here we selected the row Connection -> R/3 support and Connection tab -> open/change connection and clicked on SUBMIT. The we got below short dump.
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_WD_CONTEXT
Short text
    An exception occurred that was not caught.
What happened?
    The exception 'CX_WD_CONTEXT' was raised, but it was not caught anywhere along the call hierarchy.
    Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program
     'CL_WDR_CONTEXT_NODE===========CP' has to be
    terminated.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis:
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_WD_CONTEXT', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    The node does not contain any elements. COMPONENTCONTROLLER.1.SYSTEMS.1.CLIENTS
How to correct the error:
    If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following keywords:
    "UNCAUGHT_EXCEPTION" "CX_WD_CONTEXT"
    "CL_WDR_CONTEXT_NODE===========CP" or "CL_WDR_CONTEXT_NODE===========CM00R"
    "_RAISE_ELEMENT_NOT_FOUND"
SMSY configuration ( logical component assignmnet) is alredy done. Is it required to do any other settings. SMD ( Solution Manager Diagnostics ) settings are not done. Is this required?
We are able to enable/open Service Connection open to ABAP system . Only for Java system we are getting error.
Please help me on this.
Thanks..
Preethish

Hi,
note 1081895 should solve this. Otherwise please create a ticket.
Regards
Andreas

Standalone SQL Server monitoring with Solution Manager

Hi,
We have a Solman 3.1 instance monitoring all of our SAP and non-SAP Infrastructure. We have several SQL Server systems we would like to monitor.
Currently we have installed saposcol and sapccms agents on the servers and are getting the OS alerts and additionally have also configured Process and Log file monitoring. We would now like to get SQL Server specific alerts like Log full alerts and other db specific alert situations. Since this is a standalone db, how can we configure this db to report these type of alerts?
thanks,
binoy.

Binoy,
If I remember correctly I had this setup @ Sharp for oracle. You can use the same step to monitor the SQL DB liek transaction logs, backup etc's. If you can run the report RSDBMON0 this will build the <DB monitoring Tree> on the solman. So you can setup the autoreaction for the respective monitoring segment which you wanted.
Let me know if any questions.
Ashwin

Solution Monitoring configuration with solution manager 4.0

Hi Friends,
I have to the Solution Monitoring configuration with solution manager 4.0.
Please provide steps or screen shot if any body having that.

Hi,
Check <a href="https://websmp108.sap-ag.de/sapidb/011000358700005479192006E.sim">this.</a> and <a href="https://websmp108.sap-ag.de/sapidb/011000358700006936062005E.sim">this</a>.
This will solve your problem.
Feel free to revert back.
--Ragu
Message was edited by:
Raguraman C

EP Monitoring in Solution Manager

Dear Experts,
I would like to create a monitoring system using our solution manager. Therefore i would like to know the ways of doing it. I also would like to know what can be monitored in Solution manager for EP(enterprise portal). If possible i would like to monitor from Server to Application level, meaning to say i would like to know all the components that can be monitored using SolMan such as CPU utilization , disk space availability and from application point of view, i would like to view /receive alert that can show number user locked in EP an so on.
Our EP is running on version 7.0 and on SP15.
Regards
Ramesh

Hello Ramesh,
Please use the following links.
Monitoring with the SAP Solution Manager
http://help.sap.com/saphelp_nw04/helpdata/en/1a/40f83ee0e66856e10000000a114084/frameset.htm
SAP How-to Guides
https://www.sdn.sap.com/irj/sdn/howtoguides#section4
SAP NetWeaver 7.0
http://help.sap.com/nw70/
Also check service.sap.com/instguidesnw04s --> operations and look for Supp. Setup Guide - Solution Manager Diagnostics NW04 SPS 15
Hope the above links helps you.
Cheers,
Satish.
Edited by: Satish Arram on Oct 8, 2008 5:49 PM

Can PI 7.1 and Central Monitoring on Solution Manager 7.0 coexist

Hi,
I would like to know if there are any restrictions if any for using PI 7.1 instead of PI 7.0 with Solution Manager 7.0, NWA 7.0 and CCMS 7.0. I would like to know the problems if any we may face for central monitoring PI 7.1 from Solution manager 7.0.
Thanks in advance.

Hi,
In SAP xi it depends on sp (service pack ) only.
Refer this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9070bf2e-9196-2a10-c183-eca16b22256f
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f08287c4-a4ee-2a10-b0a2-c863755fdb94
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60ec1de2-76c6-2a10-7198-fa4e9dd07e11
Hope it help this
Regards,
Surya

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.

UI5 Monitoring in Solution Manager / General

Hi All
We have recently been involved in a roll out of UI5 screens throughout our organisation and although we are still in the 'settling down' phase I want to know if there is any monitoring we can look to implement?
I know this might be very specific to the areas we are using in UI5 but I would hope there would be some form of Web Dispatcher monitoring or Solution Manager Java monitoring we could use.
Any help or pointers would be great.
Many Thanks
Phil

Hi;
yes, you can use probes that will do some basic workflows on the system and return feedback to your enterprise monitoring system, have a look at this document:
http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_monitoring_guide_en.pdf
Regards;
Lionel

Connection With Solution Manager!!!!

HI all,
01) Could anyone send me docs on How to connect Solution Manager With the ECC 6.0??
02) How to do Issue tracking with solution manager and use as a repository??
Thanks In advance
Regards,
Ami_Eka

Hi,
check following
How to generate EWAu2019s From Satellite Systems:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0f35bf3-14a3-2910-abb8-89a7a294cedb
SAP Solution Manager service desk:
please refer to the SAP Help Portal (help.sap.com -> SAP Solutions -> SAP Solution Manager -> SAP Solution Manager [current release] [Choose language] -> Service Desk).
https://websmp108.sap-ag.de/~sapdownload/011000358700000509252008E
Maintenance Optimizer:
https://websmp108.sap-ag.de/~sapdownload/011000358700000235502007E
regards,
kaushal
Edited by: kaushal malavia on May 27, 2008 6:12 PM

System Monitoring though Solution Manager

Hi ,
Can someone tell me SAP Notes for doing system monitoring through Solution Manager if i don`t want to use CCMS .

Hi
I think you are looking for Central monitoring using Solman .. If yes please go through the following links
http://service.sap.com/moniotring
https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/30237989-0901-0010-70a4-944691eb5e52 [original link is broken]
You are still going to use CCMS but if an alert occurs in satelite system , it will forward this alrt to Solman and solman will send out the alert .This happens if you configure central auto reaction , You can also monitor other system by adding the systems to Solman using SMSY_SETUP/SMSY and define solution using DSWP/SOLUTION_MANAGER . These are well documented with screens in
http://service.sap.com/rkt --> Solution manager --> Solman Manager < rel > --> Technology Consultants and System Administrator
I dont think there is any note which talks about the entire configuration
Thanks
Prince Jose

Enterprise Portal monitoring with Solution Manager

Similar Messages

Maybe you are looking for