Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Lluis
Active Contributor
4,240

I forgot that second part of saprouter configuration for JAVA diagnostics agents, but thanks to jeffrey.sterner2 I remember to finish it, :smile:

Remember that this problem is related and the second part of an scenario named on that post http://scn.sap.com/docs/DOC-45491 , That is on a VAR scenario where the managed systems are connected to Solution Manager outside of Solution Manager local networks trough firewalls, and 2 or more saprotuers... That's is a real nightmare for saprouter remote connection for diagnostic agents.

Error message after diagnostic installation:

"Wilyhost Agent] Wilyhost Agent configuration finished without errors, but on Enterprise Manager (sapsolman:6001) no Wilyhost Agent was detected from host  aptest. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration  as been changed recently please restart the SMD Agent on OS level and execute the Wilyhost Adapter setup step again"

If you look at jvm_smdagent.out  file, you will find:

"...10/17/11 09:02:56 PM CEST [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at sapsolman:6001 ,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (1)..."

* The problem is than wilyhost agent try to conect to "sapsolman:6001"! host instead to use saprouter conection.

Steps to solve that problem:

1. Download the file IntroscopeSapAgent.profile from the Diagnostics agent administration for the diagnostics agent on the managed system

(Agent Administration -> Applications Configuration -> com.sap.smd.agent.application.wilyhost -> Application Resources -> IntroscopeSapAgent.profile )

Make sure to select the correct scope for your agent.

2. Edit the downloaded file IntroscopeSapAgent.profile:

a. comment out standard entries:

#introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=localhost

#introscope.agent.enterprisemanager.transport.tcp.socketfactory.DEFAULT=com.wily.isengard.postofficehub.link.net.DefaultSocketFactory

#introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=6001

b. de-comment the saprouter entries and adapt the saprouter

introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT=/H/199.100.1.5/S/3299/H/solman.domain.com/S/3299/H/solmanserver

introscope.agent.enterprisemanager.transport.tcp.socketfactory.DEFAULT=com.sap.sup.wily.saprouter.SapRouterSocketFactory

introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT=6001

3. Upload the modified file to the same scope.

4. Reboot the diagnostics agent to activate the changes.

5. Check in the Introscope Investigator if the agent is connected.

Thinks that you have to take in consideration:

  1. If you perform a managed system setup on this agent after changing the wilyhost settings you should skip the step for configuring the wilyhost in managed  system setup.  Otherwise the changes you did in agent admin are getting overwritten again.
  2. DEFAULT and SAPROUTER is the key for the other properties like introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT So for your setting SAPROUTER no corresponding properties like introscope.agent.enterprisemanager.transport.tcp.host.SAPROUTER were existing
  3. After a good setup you are able that no problems are registered on logs, but on E2E worload monitor you can't see any data, that is because the extraction for the system need to be re-started to return some records. Verify in some days (after the InfoCube 0SMD_PE2H has been compressed ).

More Information:

About Diagnostic Agents:

http://scn.sap.com/community/it-management/alm/solution-manager/blog/2013/10/15/diagnostics-agents-v...

Regards,

Luis

2 Comments
Labels in this area