CCMS - ERROR

[Former Member]

Hi all,

I am configuring CCMS, I am getting an error with following log

=======================================================================================================

java.lang.ClassNotFoundException: com.sap.sup.admin.selfcheck.checks.prerequisite.JavaToAbapCheck

-

---

Loader Info -

---

ClassLoader name: [sap.com/tc_smdselfcheck~repository]

Parent loader name: [Frame ClassLoader]

References:

common:service:http;service:servlet_jsp

service:ejb

common:service:iiop;service:naming;service:p4;service:ts

service:jmsconnector

library:jsse

library:servlet

common:library:IAIKSecurity;library:activation;library:mail;library:tc_secssl

library:ejb20

library:j2eeca

library:jms

library:opensql

common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:signature_lib;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore

interface:resourcecontext_api

interface:webservices

interface:cross

interface:ejbserialization

sap.com/tc_{webadministrator}solmandiag

service:tc_smdserver~service

sap.com/tc_smdagent_applicationfilesystem

sap.com/tc_smdagent_applicationpar

sap.com/tc_smdagent_applicationruntime

sap.com/tc_smdagent_applicationdatacollector

sap.com/tc_smdagent_applicationdatabase

sap.com/tc_smdagent_applicationremoteos

sap.com/tc_smdagent_applicationremotesetup

sap.com/tc_smdagent_applicationtelnet

sap.com/tc_smdagent_applicationldap

sap.com/tc_smdagent_applicationconnectors

sap.com/tc_smdagent_applicationwsclients

library:com.sap.aii.proxy.framework

sap.com/tc_smdagent_applicationglobal~conf

sap.com/tc_smdagent_applicationlogviewer

sap.com/tc_smdagent_applicationwily

sap.com/tc_smdagent_applicationtracing

sap.com/tc_smdagent_applicationwilyhost

interface:tc_secdestinations~interface

interface:keystore_api

interface:security

library:com.sap.mw.jco

library:com.sap.util.monitor.jarm

library:com.sap.exception

library:sapxmltoolkit

library:tc.httpclient

library:tc_SLUTIL

library:jnet

library:core_lib

service:webdynpro

service:webservices

service:rfcengine

service:timeout

service:licensing

Resources:

G:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\tc_smdselfcheck_{repository\servlet_jsp\tc}smd_selfcheckrepository\root\WEB-INF\lib\selfcheck.jar

G:\usr\sap\SOL\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\tc_smdselfcheck_{repository\servlet_jsp\tc}smd_selfcheckrepository\work

Loading model: {parent,references,local}

-

---

at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:219)

at com.sap.sup.admin.selfcheck.fwk.state.builder.SelfCheckContextBuilder.startElement(SelfCheckContextBuilder.java:486)

at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.startElementEnd(SAXDocHandler.java:146)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1772)

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.scanContent(XMLParser.java:2442)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843)

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:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

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:345)

at com.sap.sup.admin.selfcheck.fwk.state.builder.SelfCheckContextBuilder.buildSelfCheckContext(SelfCheckContextBuilder.java:155)

at com.sap.sup.admin.selfcheck.fwk.SelfCheckImpl.<init>(SelfCheckImpl.java:37)

at com.sap.sup.admin.selfcheck.fwk.SelfCheckFactoryImpl.newSelfCheck(SelfCheckFactoryImpl.java:19)

at com.sap.sup.admin.selfcheck.wd.SelfCheckComp.getSelfCheckInstance(SelfCheckComp.java:567)

at com.sap.sup.admin.selfcheck.wd.SelfCheckComp.runSelfCheck(SelfCheckComp.java:579)

at com.sap.sup.admin.selfcheck.wd.SelfCheckComp.reCheckManagedSystem(SelfCheckComp.java:331)

at com.sap.sup.admin.selfcheck.wd.wdp.InternalSelfCheckComp.reCheckManagedSystem(InternalSelfCheckComp.java:241)

at com.sap.sup.admin.selfcheck.wd.SelfCheckCompView.onActionReCheck(SelfCheckCompView.java:447)

at com.sap.sup.admin.selfcheck.wd.wdp.InternalSelfCheckCompView.wdInvokeEventHandler(InternalSelfCheckCompView.java:385)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)

at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

========================================================================================================

Can any body give suggestgions for this log

[Former Member]

Hi jagan,

Yes we are configuring CCMS,

We have followed the SAP Note 1274287 and as per the note all the Software Components are up-to-date.

As you suggested we have already installed the agents in development system and the initial and basic configurations are completed in solman_setup. My understanding is the next step is managed system configuration. Correct me if I am wrong.

We have created the 2 RFCs (SID_RZ20_COLLECT & SID_RZ20_ANALYZE) in Solution manager and able to connect to the development system. After installation of agents in development system, I have configured the ABAP & JAVA instances as per the CCMS documentation and agents are succefully registered

But in the Diagnostic System setup wizard for managed systems, the agent status is N/A (not available) for development system. But the Server Name(xxxxxxxxx) for the development system is showing. In the remark it is mentioned that The SMD Agent 'xxxxxxxxxx' hasn't been found.

Could you please let me know why the agent status is showing not available.

Regards,

J Nair

[Former Member]

Hi Nair,

If you are configuring SMD and Preparing the system for all the functionalities? then yes, the next step is manages systems configurations which sets up satellite system for further configurations.

What i can infer is that you are following two different guides, 1 for Solman_setup and other for CCMS.

Please note that, If you are configuring the CCMS, You have to have SMSY entries with SMXXXXXXx_READ , Trusted/Login RFC connections in case of solution manager as CEN system and is the best practice. SID_RZ20_COLLECT & SID_RZ20_ANALYZE is used for the CEN monitoring, which can be done in any system.

Did you run RFC generation step as a Part of Managed system setup?. Please run it and assign the READ, Trusted RFCs for system Monitoring. The actual CCMS/System monitoring configuration has to take place in Tx DSWP/Solution_manager. Since you are done with Agent Installation and the configuration is restricted to CCMS/System Monitoring alone, do follow the CCMS setup guide alone.

Please follow this blog : /people/federico.babelis2/blog/2006/04/25/system-monitoring-configuration-guide-for-dummies

The SMD agent concept is different and is especially for Diagnostics configuration- Root Cause Analysis- you have to install the SMD agent and Register it in Solman and you have to follow diagnostics setup for this.

Kindly revert for any queries.

Thanks,

Jagan

[Former Member]

Hi jagan,

I have installed the agents in Development System.

While configuring the managed system configuration in Solution Manager, in the Check Prerequisites I am getting the above error.

Regards,

J Nair

[Former Member]

So for SMD-Is solution manager's Diagnostics Prerequisite Green???. Did it meet the Pre-req as of note 1274287???. Is initial and Basic configuration complete in Solman(on EHP1)?. I believe its a problem with solution mnager's application itself. Check the components pls.

As per the first post, you are configuring CCMS right?. Why do you need the Diagnostics setup step for this?. Just install the SAPCCmxx AGENTS and proceed with creating RFCs.

Is RFC connections established?.

Thanks,

Jagan

[Former Member]

Hi,

At Exactly which step you are getting this error pls.

Is it during Agent Installation or during system moniroting setup?.

From the log it can be due to Connectivity error. Put some more light on it, to help you out.

Thanks,

jagan