cancel
Showing results for 
Search instead for 
Did you mean: 

wily agent not able to connect to wily enterprise manager

HJ1
Participant
0 Kudos

Hi i am trying to do monitoring configuration for Netweaver portal 7.0 system thru wily agent .

agent is configured as per the document but unabe to connect.

Please suggest and provide documents if u have any

Edited by: harish jaiswal on Apr 9, 2008 2:08 PM

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello, I have a question. We are running Solution Manager 7.0 EPH1 (enhancement Pak 1) on Aix.

How do you specify the Enterprise Manager URL and the port number? In the previous version when you went to http://solman:50000/smd.>Diagnostic Setup>Managed Sustems.---->Introscope Agent, you were able to Specify Enterprise Manager settings by selecting EDIT Settings button. In EPH1 there is no EDIT setting buttion. Does anyone have an idea how to enter the value?

Thank you in advance...!

0 Kudos

Hello, did you ever find out how to specify the setting using EHP1. I am having the same issue. I entered the Wily informaiton during the setup, but it doesn't show in the work center.

Basically, Solman doesn't see my Wily EM (though it DOES see my agent).

Thank you.

markus_doehr2
Active Contributor
0 Kudos

Please provide the agent logs.

Markus

HJ1
Participant
0 Kudos

INFO] [IntroscopeAgent] Stall event service: resolution of 10 seconds

4/07/08 11:03:58 AM CEST [INFO] [IntroscopeAgent] Started Stall Service

4/07/08 11:03:58 AM CEST [INFO] [IntroscopeAgent] The Introscope AutoProbe log file has been automatically renamed from /usr/sap/ccms/wily/logs/AutoProbe.20080407-110352.log to /usr/sap/ccms/wily/logs/AutoProbe.P30_EP_Server0.log.

4/07/08 11:03:58 AM CEST [INFO] [IntroscopeAgent] The Introscope Agent log file has been automatically renamed from /usr/sap/ccms/wily/logs/IntroscopeAgent.20080407-110356.log to /usr/sap/ccms/wily/logs/IntroscopeAgent.P30_EP_Server0.log.

4/07/08 11:04:07 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (2).

4/07/08 11:04:17 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (3).

4/07/08 11:04:27 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (4).

4/07/08 11:04:30 AM CEST [INFO] [IntroscopeAgent] SQL Agent: configured maximum SQL statement length to 990.

4/07/08 11:04:30 AM CEST [INFO] [IntroscopeAgent] SQL Agent: configured blame participation to true

4/07/08 11:04:37 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (5).

4/07/08 11:04:47 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (6).

4/07/08 11:04:57 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (7).

4/07/08 11:05:07 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (8).

4/07/08 11:05:17 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (9).

4/07/08 11:05:27 AM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at madap8010:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (10).

4/07/08 11:05:27 AM CEST [INFO] [IntroscopeAgent.ConnectionThread] The Agent will continue to attempt to connect to Introscope Enterprise Manager. Further failures will not be logged.

4/07/08 11:06:46 AM CEST [INFO] [IntroscopeAgent.SAPTracerStartupHook] Tracer is not activated because prerequisite class is not present: com.sap.sup.wily.agent.tracer.SapAllocStatTracer

4/07/08 11:06:46 AM CEST [INFO] [IntroscopeAgent.SAPTracerStartupHook] Tracer is not activated because prerequisite class is not present: com.sap.sup.wily.agent.tracer.SapMemoryTracer

4/07/08 11:06:46 AM CEST [INFO] [IntroscopeAgent.SAPTracerStartupHook] start tracer com.sap.sup.wily.agent.tracer.SapPerfLibTracer

4/07/08 11:06:46 AM CEST [INFO] [IntroscopeAgent.SAPTracerStartupHook] startTrace: registered real tracer for com.sap.sup.wily.agent.tracer.SapPerfLibTracer

4/07/08 11:20:46 AM CEST [INFO] [IntroscopeAgent.SAPJMX] start of JMX hook

4/07/08 11:20:46 AM CEST [INFO] [IntroscopeAgent.SAPJMX] Agent directory must contain WebAppSupport.jar and sap/SapJmx.jar: /usr/sap/ccms/wily

4/07/08 11:20:47 AM CEST [INFO] [IntroscopeAgent.SAPJMX] JMX hook finished successfully

4/07/08 11:20:47 AM CEST [INFO] [IntroscopeAgent] Activating JMX Data Collection

4/07/08 11:20:52 AM CEST [INFO] [IntroscopeAgent.JMXService] Using IJMXCustomizer class: com.sap.sup.wily.agent.jmx.SapJMXCustomizer

4/07/08 11:20:55 AM CEST [INFO]

Former Member
0 Kudos

Harish,

How are you doing this? Did you use SMD wizard setup to do this or are you doing this manually in configtool?

Labinot

markus_doehr2
Active Contributor
0 Kudos

Can you resolve the name "madap8010" from the client, where the agent is installed on?

Markus

HJ1
Participant
0 Kudos

I have istalled the wily agent on monitored system then set some parameter in config tool.

fillowing the document

Introscope7.1_Installation_Guide.pdf

is there any othere method to this ?

please suuggets if u have any other solution to enable poetal monitoring.

HJ1
Participant
0 Kudos

masdap8010 is the monitoring server where wily enterprise manager is installed.

markus_doehr2
Active Contributor
0 Kudos

Yes - and you can

ping masdap8010

from the machine you're running the agent? For me it looks like the system can't resolve the name of the server and thus being unable to connect....

Markus

Former Member
0 Kudos

You can setup Wily agents via Solution Manager Diagonstics if you have this setup.

Make sure that Java Parameters fields are correct in configtool. This is case sensitive.

Example:

-Xbootclasspath/p:/usr/sap/ccms/wily/connectors/connector.jar;/usr/sap/ccms/wily/Agent.jar

-Dcom.wily.introscope.agentProfile=/usr/sap/ccms/wily/sap_IntroscopeAgent.profile

-Dcom.wily.introscope.agent.agentName=GPX_EP_Server0

Restart JAVA instance.

Hope this helps!

Labinot

HJ1
Participant
0 Kudos

Hi Yes i have set the paramete in configtool and restarted the intence

-Xbootclasspath/p:/usr/sap/ccms/wily/connectors/connector.jar:/usr/sap/ccms/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/usr/sap/ccms/wily/sap_IntroscopeAgent.profile

-Dcom.wily.introscope.agent.agentName=P30_EP_Server0

HJ1
Participant
0 Kudos

hey i have one more question we know that in windows environment we enter the server name in drivers---Hosts file.

IS the same thing u are asking and how to do that?