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

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

  • 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

  • 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

  • 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

  • SMD Configuration on MDM 7.1 with Solution Manager 7.01 SP19

    Hi,
    Kindly let me know if someone has faced issue with configuring SMD on SMD 7.1 with Solution Manager 7.01 SP19. Presently I have configured that and System is being shown in Wily Introscope Webview but Saposcol is greyed out in that.
    Also system is not showing any data in Introscope Dashboard. Any guess for this?
    Earlier while I was configuring SMD, error related to null installation directory (...Invalid root directory: /usr/sap/SID/null ) were occuring. After that when I created a softlink for saposcol service from /usr/sap/hostctrl/exe/saposcol to /usr/sap/SMD/SMDA97/exe.
    Still no data and still in SMD Agent logs saposcol service warning is there.
    Thanks & Regards,
    Manish Singh

    Hi Jansi,
    Thanks for the reply..
    Here is our scenario. SAPOSCOL was not there in /usr/sap/SMD/SMDA97/exe first place. So I made the softlink from /usr/sap/hostctrl/exe/saposcol to /usr/sap/SMD/SMDA97/exe and than re-ran setup again but still of no use.
    Our Soltuion Manager saposcol version and MDM saposcol version is same. Below is the SMD Agent log of MDM server:
    Apr 20, 2011 2:36:19 PM [Thread[Thread-22,5,main]] Error      com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed
    [EXCEPTION]
    com.sap.smd.wily.hostagent.PermanentException: Error: cannot connect to destination SapHostControl_Default. Probably saphostctrl is not installed. This error can be ignored if saposcol is available.
    at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:98)
    at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(AgentConfigVO.java:85)
    at com.sap.smd.wily.hostagent.config.AgentConfigXmlHandler.endElement(AgentConfigXmlHandler.java:174)
    at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:156)
    at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1953)
    at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846)
    at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442)
    at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843)
    at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845)
    at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
    at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
    at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
    at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
    at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:430)
    at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:93)
    at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
    at com.sap.smd.wily.hostagent.WilyHostServicep4_Skel.dispatch(WilyHostServicep4_Skel.java:168)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
    at java.lang.Thread.run(Thread.java:664)
    Caused by: javax.xml.rpc.soap.SOAPFaultException: Method 'SOAP-ENV:Envelope' not implemented: method name or namespace not recognized
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
    at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:142)
    at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:157)
    at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:94)
    ... 25 more
    Apr 20, 2011 2:36:19 PM [Thread[Thread-22,5,main]] Warning    com.sap.smd.wily.hostagent.SapAgent - startActions(): Action SAPOsColWs
    [EXCEPTION]
    com.sap.smd.wily.hostagent.TransientException: Destination not available:SapHostControl_Default
    at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlAction.init(SapHostControlAction.java:74)
    at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:396)
    at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:94)
    at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
    at com.sap.smd.wily.hostagent.WilyHostServicep4_Skel.dispatch(WilyHostServicep4_Skel.java:168)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
    at java.lang.Thread.run(Thread.java:664)
    Apr 20, 2011 2:36:20 PM [Thread[Thread-22,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): saposcol exited with 255***********************************************************************
    This is Saposcol Version COLL 21.01 711 - AIX v12.01 5L-64 bit 090324
    Usage:  saposcol -l: Start OS Collector
            saposcol -k: Stop  OS Collector
            saposcol -d: OS Collector Dialog Mode
            saposcol -s: OS Collector Status
    The OS Collector (PID 1552388) is already running .....
    Apr 20, 2011 2:36:23 PM [Thread[SAPOsCol,5,main]] Error      com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action throws exception, will be terminated: SAPOsCol
    [EXCEPTION]
    java.lang.NullPointerException:
    at com.sap.smd.wily.hostagent.action.SapOsColAction.reportProperty(SapOsColAction.java:293)
    at com.sap.smd.wily.hostagent.action.SapOsColAction.dumpSection(SapOsColAction.java:239)
    at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:164)
    at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:417)
    at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
    at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
    at java.lang.Thread.run(Thread.java:664)
    Our MDM is 7.1 version and Solution Manager is 7.01 (EHP1) with SP19 so we should configure our MDM system as 7.1 version which we did but still data is not coming in Wily properly. Its not showing SID name under the hostname in Wily Introscope and neither is MDM Servers (Master Data Import Server, Master Data Server & Master Data Syndication Server under SID).
    Now the interesting thing is that if we configure our MDM server as 5.5 version with Solution Manager and do the configuration than its showing in Wily but in that case MDM Cockpit doesn't work.
    We want both to work Wily as welll as MDM Cockpit since our MDM and Solman version matches for both configuration.
    Any ides or help steps to do that?
    Thanks,
    Manish Singh

  • 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

  • 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

  • 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

  • Solution Manager Certification , Wily Introspective and Topaz FAQs

    Hi All,
    I am preparin for certification exam on Solution Manager Certification , Wily Introspective and Topaz. Could you please send me FAQs and certification questions on those topics.
    Please fored to my email.
    I appreciate your help and award points.
    Thank you
    Maruti CR
    [email protected]

    Can u please share with me
    [email protected]

  • Solution Manager and external Central Monitoring system

    We have a Solution Manager system SOL and a Central Monitoring system
    CEN.  The monitored system SDS is configured to report CCMS data to CEN
    and I wanted SOL to be able to access this data.  After configuring SDS
    to CEN, CEN that the following entry in RZ21:
    SDS#SDS_RZ20_COLLECT#SDS_RZ20_ANALYZE
    After performing the wizard in SOL, SOL now has the following entries
    in RZ21:
    SDS2#SM_SDS2CLNT200_READ#SM_SDS2CLNT200_TRUSTED
    This would indicate to me that SOL is reading the CCMS information
    directly from the monitored system, rather than via CEN.
    In the 'Setup System Monitoring' of Solution Manager the Central
    Monitoring System and CEN destination are SOL and NONE respectively.
    Is this configuration correct, and if not how do I correctly configure
    it?
    Is the monitored system now only reporting data to SOL, or is it
    reporting to both CEN and SOL?
    Regards,

    Issue closed

  • SSO from Solution Manager to Wily Enterprise Manager issue

    Hi,
    We are facing problem in SSO from Solution Manager to Wily Enterprise Manager. We have done the configuration as per the Wily Enterprise Guide- "Introscope Version 8 Installation Guide For SAP" Page 38.
    Our Solution Manager system is running on AIX platform and Wily Enterprise Manager is on Windows 2008.
    This is what we are trying
    SOLMAN Production Client --> SOLMAN_WORKCENTER --> INTROSCOPE WORKSTATION --> this opens a new browser page and from there we click on Start Introscope -->
    Result --> SSO doesn't work, still we get login window.
    Introscope Enterprise Manager logs says -->
    9/12/11 10:47:17 PM BST [WARN] [Manager] Single sign on failed: No SAP single sign on ticket was found in the request header.
    Note: Another Solution Manager system in our landscape (on windows 2008 platform) is connected to same Wily Enterprise Manager (windows 2008) and from this solution manager SSO to Wily Enterprise Manager is working.
    Please help me with your expertise to solve this problem.
    Best Regards
    Davinder

    Hello Singh,
    Could you check if you have maintained these parameters in instacne profile ?
    From SCN post -> http://scn.sap.com/thread/969538
    Hi Hector,
    To configure SSO as per initial setup guide, please check your profile parameters in your Solution Manager as below:
    You have set up SSO, see also:
    SAP Note 817529: Checking the SSO Configuration
    Installation Guide and Security Guide for SAP Solution Manager
    Create the following profile parameters in the instance profile:
    login/create_sso2_ticket = 2
    login/accept_sso2_ticket = 1
    icm/host_name_full = fully qualified server name
    This parameter must be attributed to the fully qualified server name (for example wdfd002568.wdf.sap). The name must contain at least two periods. See also SAP Note 434918.
    Hope this helps,
    Regards,
    -Rohan
    BR,
    kamil

  • 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.

  • Expert Opionon on Landscape with Solution Manager 4

    Hi Experts:
    I would like your expert opinion of the following.  (Points will be rewarded for all posts)
    I have been tasked with setting up a DEMO environment involing Solution Manager 4 (SM4) , ECC 6.0 (ECC) and Business Intelligence 7 (BI7).
    We would like this to be set up in such a way so that we could maximize Solution Manager and show its full functionality and capbility to our clients. 
    I was thinking of setting up the landscape in the following order.
    3 Servers, OS: Windows, DB: MS SQL 2005
    1. Setup SAP Transport Host (This will reside in SM4)  This will be done as suggested in the SAP install guides.
    2. Install SM4 through a Central Install (ABAP only System)
    3. Post Install Activities (From SM4 Installation Guide)
    4. Share the following in ECC (
    SAPTRANSHOST\SAPMNT\trans.) and share it with SM4. (So, essentially ECC shares the same transport directory)
    (I am not sure about the above step...please confirm here)
    5. Install ECC through a Central Install (ABAP only System)
    6. Post Install Activities (From ECC Installation Guide)
    7. Share the following in BI7 (
    SAPTRANSHOST\SAPMNT\trans.) and share it with SM4. (So, essentially BI7 shares the same transport directory as ECC and SM4)
    (I am not sure about the above step...please confirm here)
    8. Install BI7 through a Central Install (ABAP only System)
    6. Post Install Activities (From BI7 Installation Guide)
    I do realize that we also need EP7 for BI7, but that is being planned for release 2, the client is only interested BW lite at the moment.
    Please feel free to critque the above and offer all alternatives.
    Thanks!
    I owe my SAP Basis Career to this site as I have learned so much here.  Again, Points will be rewarded.

    Hello Imran,
    I will answer in your text...
    I have been tasked with setting up a DEMO environment involing Solution Manager 4 (SM4) , ECC 6.0 (ECC) and Business Intelligence 7 (BI7).
    -->Exactly with escenario? Implementation scenario, monitoring, Change request management, service desk???
    We would like this to be set up in such a way so that we could maximize Solution Manager and show its full functionality and capbility to our clients.
    -->OK! all scenarios
    I was thinking of setting up the landscape in the following order.
    3 Servers, OS: Windows, DB: MS SQL 2005
    1. Setup SAP Transport Host (This will reside in SM4) This will be done as suggested in the SAP install guides.
    2. Install SM4 through a Central Install (ABAP only System)
    --->NOT possible, solman 4.0 has only one installation possibility, ABAP+J2EE
    3. Post Install Activities (From SM4 Installation Guide)
    4. Share the following in ECC (
    SAPTRANSHOSTSAPMNT     rans.) and share it with SM4. (So, essentially ECC shares the same transport directory)
    (I am not sure about the above step...please confirm here)
    ---> You don´t need to share the trans folder for any solman scenario
    5. Install ECC through a Central Install (ABAP only System)
    6. Post Install Activities (From ECC Installation Guide)
    -->ok
    7. Share the following in BI7 (
    SAPTRANSHOSTSAPMNT     rans.) and share it with SM4. (So, essentially BI7 shares the same transport directory as ECC and SM4)
    (I am not sure about the above step...please confirm here)
    ->Please don´t do it!!!
    8. Install BI7 through a Central Install (ABAP only System)
    6. Post Install Activities (From BI7 Installation Guide)
    ->Ok
    I do realize that we also need EP7 for BI7, but that is being planned for release 2, the client is only interested BW lite at the moment.
    -> With this two satellites, ECC and BI7 you work in Implementation scenario defining a Implementation project
    ->Also monitoring scenario and service desk will be cover
    -->For change request scenario still you need to have at least two client in each satellite to be able to test the scenario
    The transports managed by the solman must be done as always between roles
    DEV->QUA->PRD of the same product release
    Hope this helps,
    Dolores

Maybe you are looking for