SMD-IntroscopeAgentSettings doesn't show Serv.Node details after mgd.wizard

[Former Member]

Hi Gurus/Experts,

-

---

Our solman(WMP) is on EHP1-SP04(SP20). I'm configuring EP (WPP).

I have re-ran the managed system wizard and it shows all green status as :

-

---

Step Wilyhost Agent Details

-

---

Created destination WPP_JC90_server0

Created destination WPP_JC90_server1

Created destination SapStartSrv_ners35_WPP_90

Created action SAP GC|WPP_JC90_server0 - SAP GC|WPP_JC90_server0

Created action SAP GC|WPP_JC90_server1 - SAP GC|WPP_JC90_server1

Created action WPP|ners35_WPP_90 - SapStartSrv_ners35_WPP_90

Created 3 action(s).

1 Wilyhost Agent(s) from host ners35 is connected to the EM.

Wilyhost Agent setup finished successfully

-

---

But, when we check in the ners35-SMDAgentApplication log under agent administration, we get error as:

-

---

Feb 24, 2010 2:49:00 PM [Thread[Reconnect,5,main]] Warning com.sap.smd.wily.hostagent.action.ReconnectAction - doRun(): Failed to reconnect destination SapHostControl_Default

-

---

[EXCEPTION]

com.sap.smd.wily.hostagent.TransientException: Error: cannot connect to destination SapHostControl_Default

-

---

at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:95)

at com.sap.smd.wily.hostagent.action.ReconnectAction.doRun(ReconnectAction.java:35)

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)

Caused by: java.rmi.RemoteException: Service call exception; nested exception is:

java.net.ConnectException: A remote host refused an attempted connect operation.

at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:149)

at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:157)

at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:92)

... 4 more

-

---

Caused by: java.net.ConnectException: A remote host refused an attempted connect operation.

-

---

In Introscope Agent Settings -> system(WPP) -> click Retrieve Current Settings -> J2ee Noe Information Details :

JDK Location:

-

---

Enterprise Manager Host:

Enterprise Manager Port:

Introscope Agent Name:

Introscope Agent Profile:

Autoprobe Directives:

Wily Version:

Introscope Agent Version:

Introscope Agent Log Location:

-

---

No Information is displayed.

-

---

Also, one more question. In earlier version there was a option of choosing the JVM for IBM J9 JVM. It is not shown in EHP1 - any idea, where to set that option.

-

---

Waiting for your help.

-

---

Thanks/Rakesh

Edited by: Rakesh G Nagula on Feb 24, 2010 4:19 PM

[Former Member]

Hi Shyam,

Thanks for your reply.

I have checked the areas which you suggested. And, was in process of sending the files as you requested.

But, in meantime, SAP has replied in OSS Message as "need to rerun the manage system wizard under the transaction

solman_setup and please make sure finish all the steps"

So, we gave a try to re-ran the managed system wizard (all steps) and it seems all green status in the result(as shown earlier).

Surprisingly, now I got all the CI Data displayed in the Wily Introscope.

Issue got fixed.

It is required to note that as our Enterprise Portal CI is on AIX 5.3 Server, we need to add the wily parameters manually. Our EP DI Instance was on Linux and happen to add the wily parameters automatically by the wizard. Then, re-ran mgd.sys wizard (all steps through tcode solman_setup) and seems all working fine (as of now).

Its always a question why it worked this time. Because, we have tried re-run of the mngd. wizard earlier too..

Shyam, Thanks again & appreciate for your kind help

Thanks/Rakesh

[Former Member]

Hi Rakesh,

Strange, that for DI data is visible and no data for CI

Have you installed SMD in both the hosts ?

If yes, check Introscope workstation whether you can see CI data there.

If not

1. On the Enterprise MAnager host, increase the log level: Edit the file /usr/sap/ccms/wilyintroscope/config/IntroscopeEnterpriseManager.properties, and change

log4j.logger.Manager.QueryLog=INFO, querylog

to

log4j.logger.Manager.QueryLog=ALL, querylog

The change is active immediately, no restart required.

2. Refresh the Enterprise Manager status in Diagnostics Setup >Advanced Setup > Tab "Wily" via the button "Refresh".

3. COllect the complete log directory of the Enterprise Manager

(/usr/sap/ccms/wilyintroscope/logs)., post the logs in this thread.

4. For the same time frame, please attach the defaultTrace of the

Solution Manager.

Regards,

Shyam.

[Former Member]

Hi Shyam,

Thanks for reply.

I agree with your reason.

I tried checking the SAPNote 1413583, but it is showing now as "The requested SAP Note is

either in reworking or is released internally only" - probably some version update.

I happen to get rid of this issue by manually adding the Wily parameters as mentioned below, and could able to see the ners35-WPP(enterprise Portal -CI Instance) in the list and able to setup introscope for the same successfully. But, the Issue is with the data. We are not able to see the monitoring data for all the areas in the Wily introscope monitoring for the WPP-ners35 CI instance, under http://<host>:8081/webview. But, we could see for DI instance of WPP-nert90 in areas of Wily Introscope Monitoring. So, question still remains...

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

-Dcom.wily.introscope.agentProfile=/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.1.0.0-2009-09-04/wily/IntroscopeAgent.profile

-Dcom.wily.autoprobe.prependToJVMRuntimePath=/usr/lib/java/jre/bin/j9vm/jclSC14/classes.zip

-Xbootclasspath/p:/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.1.0.0-2009-09-04/wily/connectors/AutoProbeConnector.jar:/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.1.0.0-2009-09-04/wily/Agent.jar

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

-Dcom.wily.introscope.agentProfile=/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.1.0.0-2009-09-04/wily/IntroscopeAgent.profile

-Dcom.wily.autoprobe.prependToJVMRuntimePath=/usr/lib/java/jre/bin/j9vm/jclSC14/classes.zip

-Xbootclasspath/p:/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.1.0.0-2009-09-04/wily/connectors/AutoProbeConnector.jar:/usr/sap/SMD/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.1.0.0-2009-09-04/wily/Agent.jar

Any suggestion for the above to fix.

Thanks/RAKESH

[Former Member]

Hello Rakesh,

There could be 2 possiblities

1) probably your WIly host tiem is not in sync with agent host

2) Wilyintroscope host missing.

refer note 1413583 - Solution Manager: Introscope Host Adapter Central Note.

and also check JVM parameters, refer to this link below

https://websmp105.sap-ag.de/~sapdownload/011000358700001995842008E

Regards,

Shyam.