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

Similar Messages

Health Monitoring and Restart Configuration with Node Manager

We have a WL 9.2.2 instance setup using Node Manager to control it. It contains a JMS server with a persistant store that is in an oracle database. If the Oracle database becomes unavailable, the Weblogic server throws a number of errors eventually leaving the Managed Server in a "FAILED" state. I configuring/activated the following "Configuration - Health Monitoring" options for the managed server to have it automatically recover from this situation:
Health Check Interval: 180
Auto Kill If Failed: Checked
Auto Restart: Checked
Max Restarts Within Interval: 2
Restart Delay Seconds: 0
However it is not automatically restarting, even though the server shows in a "FAILED" state.
1st question: Do I need to restart the server with the settings above to have it react to the FAILED state? I would think that 3 minutes after I configured the above it would begin a restart on the FAILED server, but that does not happen
I also note on the "Configuration - OverLoad" page, there is a setting for "Failure Action:" that can be set to "Ignore, take no action" or "Force Immediate Shutdown of this server" I did configure/activate this for "Force immediate Shutdown..." but again the currently FAILED server does not restart.
2nd question: Does this "Configuration - Overload- Failure Action" setting override or effect in any way the configuration of restart on the "Configuration - Health Monitoring" page?
3rd question: Same as 1st question but for these Overload settings: Do they require a full restart of the managed server to somehow take effect?


Have you set the field : CrashRecoveryEnabled=true in file : ..\bea\weblogic92\common\nodemanager\nodemanager.properties ?

EX60 configuration with Call Manager 9.1

Dear All,
I am running CUCM 9.1
I have an EX60 Device which i need to register with call manager 9.1
Please provide the steps to perform this task and bring it into a working condition
Will be thankful for your response.
Regards,
Malik.

Hi Malik,
Here we go
http://www.cisco.com/en/US/docs/telepresence/endpoint/codec-c-series/tc6/administration_guide/administering_endpoints_running_tc6_on_ucm90.pdf
Cheers!
Rob
"go easy...step lightly...stay free "
- The Clash

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

Changing port configuration with Event Manager

Hello,
I'm trying to change the configuration of a port when the port goes down with EEM.
So when an flex connect access-point is disconnected the port becomes an access-port.
I don't want to use the MAC address.
Does anyone has experience with this.
Below is the applet I'm using.
Thanks in advanced,
Michel
event manager applet CONFIG-ACCESS-PORT
event neighbor-discovery interface regexp "(FastEthernet[0-9]\/[0-9]+)" cdp delete
action 100 regexp "(AIR-LAP)" "$_nd_cdp_platform" value
action 110 if $_regexp_result eq "1"
action 200 cli command "enable"
action 210 cli command "config t"
action 220 cli command "interface $_nd_local_intf_name"
action 240 cli command "switchport mode access"
action 250 cli command "switchport access vlan 20"
action 260 cli command "no switchport trunk encapsulation dot1q"
action 270 cli command "no switchport trunk native vlan 88"
action 280 cli command "no switchport trunk allowed vlan 88,100"
action 290 cli command "spanning-tree portfast"
action 400 syslog msg "EXECUTED EEM APPLET FOR ACCESS-PORT interface $_nd_local_intf_name"
action 500 cli command "end"
action 510 cli command "copy run start"

Hi Evan,
For sure! There is a really good example on the configuration guide, and assciated caveats.
http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED_chapter_0100011.html
Benefits for using LAG is increased bandwidth, and redundancy - especially if you have the two (or more in the case of a 5508 WLC) ports connected to different physical switches, eg a 3750 stack.
Best,
Evan

APN configuration with Profile Manager password payload

hi all,
I have succesfully enrolled an iPhone using Active Directory credentials. The standard profile configures mail too, using credential given during login to /mydevices web page. My problem is that I can't configure APN (3G) settings in the same way...I can put username (%short_name%) in the APN username field, it works, but I can't find a solution for a password request (or any other way) for let users put their password for APN access during enrollment process...
Is there any way to do it?
Thanks
Ale

Same issue under 10.7.4.
I pulled a console log from the F5 BIG-IP app and found this error when the iPad tries to install the VPN profile:
com.apple.managedconfiguration.profiled profiled[1018] <Error>: VPN: couldn't create vpn interface
Doesn't realy explain WHY it can't create the interface though.

Regarding Monitoring Service for Solution manager

We need to configure "Monitoring" services in SAP solution manager 7.0.
Could somebody suggest us what are the main tasks we need to consider for doing Monitoring settings.
How many Minimum servers required to configure Monitoring services in solution manager system.
Also if any good document reference for this?
Thanks

Hi Jai,
welcome to sdn.
COMPONENTS & TOOLS OF SAP NETWEAVER
SAP Solution Manager
The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
SAP Solution Manager features and functions include:
SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
It provides a range of scenarios to support this. Extending from project management to Solution Monitoring to Service Desk to E-learning Management, it provides an efficient way to carry out a plethora of business tasks.
SAP Solution Manager is the successor to ASAP ValueSAP. SAP Solution Manager helps in implementing and managing complex system landscapes. Globally systems are getting distributed across geographies and business processes cover more than one system. In such complex scenarios, integrating technical and business requirements is important for the success of IT. SAP Solution Manager provides SAP customers with an efficient means of handling both the technical and business process side of solution implementation .
As part of SAP Solution Management Solutions, the customers receive best practices relating to:
- Global Strategy and Service Level Management
- Business Process Management
- Management of MySAP Technology
- Software Change Management
- Support Desk Management
SAP delivers this using support programs during implementation of the system solution. Some of the benefits of using SAP's Solution Manager are that it helps:
- Manages the technical risk associated with the implementation of the solution ensuring technical robustness
- Helps leverage users core competencies in implementing solutions
- Ensures solution works as intended with best practices built in.
see these links...
http://www.ne-sap-solution-manager.com/
http://www.saptechies.com/category/sap-solution-manager/
thanks
karthik
reward me if usefull

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

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

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

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

Regading PI monitoring setup in solution manager

Hi Folks,
I am new to solution manager and I need to setup PI monitoring setup in solution manager...
I read some blogs and docs but not getting clear idea. all the remaning setup has been done in solution manager and only need to configure the technical monitoring thing in solution manager...
Please help me on this step by step guide...
Thanks,
Sreenivas

Hi Hareesh,
Thanks for your reply.
In Solution manager if I opend the technical monitoring I am getting below screen..
Can you please tell me what are the steps I need to do... For first i want to test this with one file communication channel later I will do remaining channels.
I am new to this setup.. help me on this..
Thanks,
Sreenivas

BPM Monitor job in solution manager

Hi
I am trying to monitor job's with solution manager.
In the BPM (Trans' solution_manager) I config a business process and add a job to the monitor.
But there is no support massage create when the job fails.
I don't know what i did wrong.
Help
Best regards
Lior Grinberg

Hello,
The automatic creation of a notification has to be configured separately from alerting. See documentation: http://help.sap.com/saphelp_smehp1/helpdata/en/a6/a1b52fda154614ba38a17be5243b73/frameset.htm
Please also visit the Business Process Monitoring site in Service Marketplace: http://service.sap.com/bpm
I recommend to configure the Job Monitoring from within a Job Documentation. The process is described in :
a) End user documentation
http://help.sap.com/saphelp_smehp1/helpdata/en/8e/3ad6f807e147669036d2a6aed597aa/frameset.htm
b) Tutorial on Service Marketplace
http://service.sap.com/~sapidb/011000358700001911422008E.sim
Best regards,
Martin

Monitoring EWA in solution manager for EP

Hi
How to monitor and configure the EP 7.0 on solution manager 7.0 for SP 16
Can any body give the doc and steps to do.
Regards

Hi,
Follow Guides
Setting Up your Central Monitoring [original link is broken]
Notes
987835 - How to define Solutions in SMSY for Diagnostics
976054 - Availability of EWA for Non ABAP components
Prerequisites
The SAP EarlyWatch Alert is available for:
SAP systems based on ABAP stack of SAP Netweaver or SAP WebAS
SAP R/3 (minimum release 3.1H)
The Java stack of SAP Netweaver components with a J2EE Engine 6.40 or above (requires ST-SER 700 2007 1 or above on the Solution Manager)
The main prerequisites for using SAP EarlyWatch Alert are:
A remote connection between your SAP component and your SAP Solution Manager
On a ABAP stack system implement SAP Note 69455, run report RTCCTOOL and follow instructions.
For a Java stack system or a CRM system: setup of Solution Manager Diagnostics. For Java SAP Note 976054 describes the prerequisites.
The EarlyWatch Alert content is shipped on the Solution Manager with software component ST-SER u2018SAP Solution Manager Service Toolsu2019 and on the satelite systems (ABAP) with software components ST-PI u2018SAP Solution Tools Plug-Inu2019 and ST/A-PI u2018Application Servicetoolsu2019.
Chk Pdf
https://websmp201.sap-ag.de/~sapidb/011000358700002009362008E.pdf
/people/federico.babelis2/blog/2006/04/25/system-monitoring-configuration-guide-for-dummies
Hope it solves ur problem
Regards
Prakhar

Solution Monitoring configuration with solution manager 4.0

Similar Messages

Maybe you are looking for