How to IMPLE SMD/Wily?

Hi
Need some information
1.what are the OSS Notes which say SMD is required for troubleshooting for SAP components like, PI 7.1, Netweaverr 7.1, Netweaver 7.0 or any specific component like AS Java 7.0 troubleshooting.
2.How to findout which version installed in my system of Wily introscope and SMD agent ?
3. What is the latest version of Wily introscope and SMD agent available. Does any of the installed SAP components(PI 7.1, BI 7.0, BIA 7.0, MDM 7.1(forthcoming)) require a upgraded version of Wily/SMD agent?
4.what special requirements for the new version of the SMD/Wily?
Regards,
Neni

Hi
Have you refered
https://websmp210.sap-ag.de/~sapidb/011000358700000048292009F/
This got almost everthing
Also refer to : https://websmp110.sap-ag.de/support and Solution Manager Coloum for more informaton.
Cheers
Deepanshu

Similar Messages

Error when configure SMD - Wily (WAITING_FOR_DESTINATION)

When I'm configuring the agent with smd wizard I have the following error.
Mar 16, 2011 12:58:12 PM [Thread[SAP GC|EPP_J02_server1,5,main]] Error      com.sap.smd.wily.hostagent.action.GcScannerAction - scanInitial(): scan for file D:\usr\sap\EPP\J02\j2ee\..\work\std_server1.outterminated: D:\usr\sap\EPP\J02\j2ee\..\work\std_server1.out (The device is not ready) Mar 16, 2011 12:58:12 PM [Thread[SAP GC|EPP_J02_server1,5,main]] Info       com.sap.smd.wily.hostagent.action.AbstractAction - setStatus(): new status for action SAP GC|EPP_J02_server1: WAITING_FOR_DESTINATION
Mar 16, 2011 12:58:12 PM [Thread[SAP GC|EPP_J02_server1,5,main]] Error      com.sap.smd.wily.hostagent.action.GcScannerAction - doRun(): Action temporarily stopped: SAP GC|EPP_J02_server1
[EXCEPTION]
com.sap.smd.wily.hostagent.TransientException: java.io.FileNotFoundException: D:\usr\sap\EPP\J02\j2ee\..\work\std_server1.out (The device is not ready)
at com.sap.smd.wily.hostagent.action.AbstractAction.handleError(AbstractAction.java:322)
at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:389)
at com.sap.smd.wily.hostagent.action.GcScannerAction.doRun(GcScannerAction.java:136)
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:725)
at java.lang.Thread.run(Thread.java:664)
Caused by: java.io.FileNotFoundException: D:\usr\sap\EPP\J02\j2ee\..\work\std_server1.out (The device is not ready)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
at com.sap.smd.wily.hostagent.action.GcScannerAction.scanInitial(GcScannerAction.java:370)
... 4 more
   the problem is that my instance is not installed in D:\usr\sap\EPP\J02..,but it is on c:\usr\sap\EPP\J02.
For that reason me GC is not running. Because I have status WAITING_FOR_DESTINATION.
Best Regards
Donaldo

Hi Donaldo,
Is the problem solved?
I have a simular problem only the Agent is pointing to the directory ../J00/.. instead of ../JC00/.., and I also get the message "SMD - Wily ( WAITING_FOR_DESTINATION)
I checked all log-files and configuration files but iI can not find the problem.
Regards,
Meindert

How to impl result match percentage and statistics on # of visit of docs

Can someone please suggest on how to impl result match percentage and statistics on # of visit of docs.
Can this be achieved without using ultra search?
For example, by entering 'merge', I would like to see
result such as
"Party Merge High Level Design", 100%, # of hits:125.

Can someone please suggest on how to impl result match percentage and statistics on # of visit of docs.
Can this be achieved without using ultra search?
For example, by entering 'merge', I would like to see
result such as
"Party Merge High Level Design", 100%, # of hits:125.

Diagnostics - How to patch SMD Agent

Dear SAP Colleague,
I will have to install the SMD Agent on all managed system of my SAP landscape.
Do you know how this agent is patched ?
I know that both Wily IS Agent (Introscope Java Agent) and Host-level Introscope Agent) are updated from SAP Solution Manager and deployed to all managed systems.
But how do we patch the SMD Agent (Java instance) ?
Thanks
Best regards
P.C.

Hello folks,
Was wondering too if any way to update / patch SMD Host Agentu2019s executable.
I could not find any SAP document on that.
Checking our own AIX kernel that came with the install e.g. u201Cjstart u2013Vu201D, I saw that the patch # was 37, in the context of kernel 7.11_REL UNICODE, compile time Jun 6 2009. It to be noticed that in the exe directory there are just some of the u201Cfullu201D kernel folders present (it makes sense, because it is just a Java env.).. In my case there are 79 u201Cfoldersu201D in the exe dir. Please note that one of it, u201Cservicehttpu201D is a directory.
Thus, my thoughts on a potential way to patch the SMD Host Agent SAP Kernel is to apply that pool of kernel components that matches the SMD Agentu2019s executables.
Thus, first download the kernel 7.11 latest patches e.g. from (Entry by Application Group -> Additional Components -> SAP Kernel -> SAP Kernel 64 BIT UNICODE -> SAP Kernel 7.11 64 BIT UNICODE , then uncar these and rm a script that will copy only the folders that are present in the installed exe SMD Host Agent exe dir as well. Also, is should be checked to that all the files in the SMD Agent should be part of the updated kernel. If not, then I will not recommend to do it, since SAP may have something special for the SMD SAP Kernel.
Have not tried yet to perform this procedure, but is very tempting, since for 7.11 AIX the default install is at patch level 37 while today the corresponding 7.11 patch level is 92.
Please, note that this is just a personal look at this issue and absolute not a SAP recommendation. Maybe the fist question should be u201Cwhatu2019s the need for the SAP SMD Agent u201CSAP Kernel Upgradeu201D? The more correct and recommended way will be to open a customer message with SAP, e.g. asking to u201Cblessu201D the SMD Agent Kernel upgrade procedure described above.
Kind regards,
C.P.

How to remove SMD entries from SLD?

We migrated our systems to new hardware. The SLD still have SMD entries for the old servers, and they show up in the Agent Administration screen on the SLD tab.
I have removed the SAP systems from the SLD, but the SMD instances are still there.
How can I remove unwanted SMD installations from SLD? I cannot even see them...
Thanks in advance for your help.
Edited by: Russell Day on Feb 8, 2011 7:34 PM

This is what you can do:
go to your sld
http://<host>:<port>/sld
Go to "Administration"
Go to "Automatically Updated Data"
Choose a date (if you want to see all data I suggest you choose tomorrow).
A list of items will appear.
Select the things you want to remove from your SLD, you can always identify them by looking at the "last update" collumn, and choose remove.
Confirm the popup.....done!
Hope this helps!
Cheers,
David

SOLMAN SMD Wily Introscope: no dashboards are available

Hi!
I would like to use the SAP SMD functions and Wily Introscope 8.0
I am on SAP SOLMAN 7.0 EhP1.
The problem I have: when I start Wily Introscope no dashboards are available.
Can some one help me to solve this problem?
Thank you very much!
regards
Axel

You might have already checked the SAP Note 797147 and installation guide for Wily I 8.0 at
http://service.sap.com/instguides -> Installation & Upgrade Guides -> SAP Components -> SAP Solution Manager -> Release 7.0 -> Wily Introscope 8.0 - Installation Guide
From the installation guide could you confirm section ..."Check That Introscope Is Running Properly"
Also confirm you have set Java VM Parameters...
I think you need to check the Installation guide thoroughly.
Let us know if you have any error log or something....
All the best.

How critical is the wily agent name?

The wily Introscope 7.2 installation guide suggests using agentName = SID_instaceName_serverx.
The e2e diagnostics managed system wizard asks for agentName = SID_hostname_serverx.
Does anything break if you followed the wrong instructions? If so what?
I am running e2e diagnostics SPS 15.
and Wily Introscope 7.2
and smd Agent 7.0 pl 14
wily bytecode agent 7.2
Ken Chamberlain
University of Toronto

Hi Andy,
I would assume that it would be a given that a faster data connection would result in faster downloads, but it should not make a difference to the very popular phrase on the discussion groups of "failed download"
I've tried downloading on the office connection which is a 1MB 1:1 ratio link on a fibre backbone as well as on a normal 384k DSL line. The only difference being that it fails the downloads faster on the office line. All my tracks will start downloading, restart a while later and eventually it fails them. Before the Comes with Music became Nokia Music I could download on the same pc without issues.
My 2c (in South Africa we don't use these coins anymore) worth

How to install SMD Agent on a MSCS?

Hello helpers,
we have installed a PI 7.1 (double stack) on a MSCS environment. The next step is to connect the PI 7.1 SAP system to our SolMan and to install the diagnostics agent. Unfortunately I wasn't able to find any documentation explaining an installation of the SMD Agent in a MSCS environment.
Does anybody know what has to be done? Do I have to install 3 agents, one on every MSCS node and one in the SCS/ASCS cluster resource group, or is only one agent needed in the SCS/ASCS cluster resource group?
Looking forward for any answers,
Sascha Piotrowsky

Hi Sascha,
To distribute a solution to the diagnostics the install path must be verified in TC SMDIAG_WIZARD. To verify the install paths an installed SMD-AGENT is neccessary.
Yes
Another point is that we like to monitor the J2EE Servers and Dispatchers from the 2 instances on "nodeA" and "nodeB". So in my opinion at least 2 SMD-Agent should be installed, one on every node. Do you agree?
No, you need one SMD Agent, this agent can then monitor multiple instances on one virtual host. The connection is only between virtual host and agent, not between instance and agent.
But what shall I do with the ASCS00/SCS01 instance. Does an SMD-Agent installation bring any effort on "clusterSID" or is it a must?
It's not a must, only relevant if you want to receive host metrics from this host. As this is only virtual, I would not install one here.
Best regards
Michael

SOLMAN SMD Wily Introscope

Hi!
Has some one experience working with Wily Introscope 8.0?
I use currently the version 7.2 and would like to upgrade this version to Wily Introscope 8.0.
When I do so I cannot install and run Wily Introscope 8.0.
Any helpful information will be very appreciated!
regards
Axel Schulze

Hi Axel
I am planning to un-install my current wily 7.2 and plannign to install 8.0, can you let me know if you have already completed upgrading and also can you send me details on the upgrade.
Thanks
Reddy

How to impl. Enter key (when fill some input text field and then submit)

I have some input field for login user in application and then when user submit on enter I want to login process start.
Which is my solution for this?
Now, user can login process start with click on Log in button.
Thx.

See complete explanation:
http://blogs.oracle.com/Didier/ButtonToSubmitForm
and download sample 2:
http://blogs.oracle.com/Didier/Samples

SMD Agent Metrics/BOE native code metrics Missing in wily Enterprise Manager

SMD Agent and BOE native code metrics are not updated to wily EM. Previously the metrics were written to Wily EM. This is standalone setup of Wily Ent Manager without Solution Manager.
Environment:
Standalone Wily introscope Eterprise Manager - Introscope Enterprise Manager 9 SP15
DIAGNOSTICS AGENT 7.3 SP03 (incl. HostAgent)
BI 4.0 SP6 Patch 6, Windows 2008, Clustered/Distributed.
Logs:
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Initialization done.
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Service provider initialized.
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       [AgentContext.startApplications] Agent Applications started.
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Info       Smd connector has been disabled
Apr 25, 2014 3:54:35 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from INITIAL to CONNECTING
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]] Info       [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to DISABLED
Apr 25, 2014 3:54:38 PM [Thread[Connector,5,main]                     ] Fatal      com.sap.smd.wily.hostagent.WilyHostService - init(...): Failed to start Agent!
[EXCEPTION]
java.rmi.RemoteException: WilyHostAgent start failed; nested exception is:
com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:122)
at com.sap.smd.wily.hostagent.WilyHostService.init(WilyHostService.java:68)
at com.sap.smd.core.plugin.service.ServiceEntityHandle.entityLoad(ServiceEntityHandle.java:114)
at com.sap.smd.core.runtime.broker.application.api.entity.AbstractEntityHandle.load(AbstractEntityHandle.java:234)
at com.sap.smd.core.runtime.broker.application.core.entity.PseudoEntityHandle.load(PseudoEntityHandle.java:154)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:308)
at com.sap.smd.om.impl.broker.ObjectReference.loadDependencies(ObjectReference.java:305)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.loadInternal(ObjectProxyImpl.java:272)
at com.sap.smd.om.impl.broker.ObjectProxyImpl.load(ObjectProxyImpl.java:146)
at com.sap.smd.core.runtime.broker.ApplicationManager.loadState(ApplicationManager.java:468)
at com.sap.smd.core.runtime.broker.ApplicationManager.reachInitializationStates(ApplicationManager.java:366)
at com.sap.smd.core.runtime.Runtime.run(Runtime.java:57)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.runStarterPlugin(SMDAgeletsRuntimeContext.java:111)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.startApplications(SMDAgeletsRuntimeContext.java:154)
at com.sap.smd.agent.AgentContext.startApplications(AgentContext.java:733)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStart(SMDAgeletsRuntimeContext.java:495)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.offlineStartAppsIfNeeded(SMDAgeletsRuntimeContext.java:354)
at com.sap.smd.agent.SMDAgeletsRuntimeContext.statusChanged(SMDAgeletsRuntimeContext.java:311)
at com.sap.smd.agent.connection.SMDConnector.triggerStatusChanged(SMDConnector.java:1016)
at com.sap.smd.agent.connection.SMDConnector.setConnectionStatus(SMDConnector.java:933)
at com.sap.smd.agent.connection.SMDConnectionTask.startOffline(SMDConnectionTask.java:862)
at com.sap.smd.agent.connection.SMDConnectionTask.internalAttemptConnection(SMDConnectionTask.java:549)
at com.sap.smd.agent.connection.SMDConnectionTask$1.run(SMDConnectionTask.java:107)
at com.sap.smd.agent.connection.P4JNDIContextHelper.executeInSecurityContext(P4JNDIContextHelper.java:148)
at com.sap.smd.agent.connection.SMDConnectionTask.attemptConnection(SMDConnectionTask.java:102)
at com.sap.smd.agent.connection.SMDConnectionTask.run(SMDConnectionTask.java:1282)
at java.lang.Thread.run(Thread.java:743)
Caused by: com.sap.smd.wily.hostagent.PermanentException: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:62)
at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:510)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:99)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
... 26 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)(:main:, row=18, col=81) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
... 29 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: > expected to close empty element(:main:, row:18, col:81)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1782)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2454)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1855)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2857)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:235)
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)
... 31 more

Hello Gopal,
Please refer to section Wily Introscope setup for BOE 4.0 of this wiki:
Managed System Setup of BOE 4.0 system in Solman 7.1 - SAP Solution Manager Setup - SCN Wiki
You may also found interesting
Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki
https://service.sap.com/sap/support/notes/1722874
https://service.sap.com/sap/support/notes/1357901
Best Regards.
Luis Roel

Error setting up new Managed System in SMD

Hi,
we get the following error after trying to setup a new (Java)-System:
DataCollect Initial Data Collect ERROR for host xyz
Step DataCollect Details
Initial Data Collect ERROR for host xyz
!! Exception : An error occurred while uploading the Configuration Data from host [xyz] !(cause=java.lang.Exception [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz])
Exceptions
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: An error occurred while uploading the Configuration Data from host [xyz] !
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:72)
at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)
at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:348)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:736)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1000)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz]
at com.sap.smd.agent.plugins.datacollector.util.DataCollectorClientUtil.collectInitialConfigurationData(DataCollectorClientUtil.java:315)
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:67)
... 8 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: [DataCollector] Error during collectInitialConfigurationData() on host [xyz]; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:684)
at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
... 1 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
... 5 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
... 7 more
in file SMDAgentApplication.0.log of the server, that hosts the system and the SMD agent, I get:
Nov 27, 2008 2:22:57 PM [Thread[Thread-25,5,main]] Error      DataCollectorService@40c5f303: collectInitialConfigurationData()
[EXCEPTION]
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
     com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
     at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
     ... 7 more
Nov 27, 2008 2:23:03 PM [Thread[Thread-35,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
the mentioned cca_systemlandscape.xml that should be located in usr\sap\SMD\J98\SMDAgent\applications.config\com.sap.smd.agent.application.datacollector is 0 byte.
where should this file be generated/has its source?
kr, achim

Helpfull notes:
987835 - How to define Solutions in SMSY for Diagnostics
986350 - SM Diagnostics: "Monitored setup" fails during data collect

SMD Setup for MDM

Hello Gurus,
While configuring SMD setup for MDM system, i am getting following error, for MDIS and MDSS
[Wilyhost Agent] Failed to configure EP Agent for sapkrftmox01.krft.net (MDM Host)
My MDM system is not an EP system, strainge how am i getting this error related to EP.
Also in the Local SMD Agent Application log on MDM Host getting the error
[Thread[Thread-14,5,main]] Warning    com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action SAPOsCol not running because status is PERMANENT_ERROR
[Thread[Thread-23,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
[Thread[ExecutionRunner_4,5,ExecMgrThreadGroup]] Warning    com.sap.smd.wily.hostagent.destination.ProcessReader - readOutput: Error output: prtdiag can only be run in the global zone
Need the help...please....
Regards
Manoj

Hi,
Can you check your SAP OS Collector is running (SSAPOSCOL)?
What is your Solman version?
Thanks,
Pradeep

SMD, Introscope and EWA for CE

Hi Gurus,
Please let me know how to check if SMD, Wily Introscope and EWA are set up for Composition Environment 7.2. If they are not set up please let me know how to do it. These terms are pretty new to me.
Thanks & Regards,
Manu

Hello Manu,
You should be able to review the configuration of Early Watch Alerts, your SMD agent and other Solution Manager components using the sections of the help site
http://help.sap.com/saphelp_sm71_sp01/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm
and the Wiki here also has a lot of configuration information.
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=64259204
Hope this helps.

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

How to IMPLE SMD/Wily?

Similar Messages

Maybe you are looking for