cancel
Showing results for 
Search instead for 
Did you mean: 

Solman 72 Introscope Managed System Saprouter

Former Member
0 Kudos

hi,

I'm trying to configure the connection between the managed system introscope and the solution manager EMIntroscope 7.2. To do this I would like to use the two saprotuer on the Managed side and on the Solman side. I followed the procedure described on various sites / notes that says to insert the following line in the SMD configuration file:


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

unfortunately, once the line has changed and after restart it seems that SMD does not recognize it, giving me this error:

[IntroscopeAgent.Isengard] Could not add EM DEFAULT because of invalid Connection Properties: Exception creating socket factory for 'client.socketfactory.DEFAULT.default' property: com.sap.sup.wily.saprouter.SapRouterSocketFactory: com.sap.sup.wily.saprouter.SapRouterSocketFactory.
[WARN] [IntroscopeAgent.Isengard] No valid Enterprise Manager locations were found in the property introscope.agent.enterprisemanager.connectionorder in IntroscopeAgent.profile. Using default settings.

Can u help me?

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

New update, it seems that java class for saprouter connection is missed

11/08/18 11:59:17 AM CET [DEBUG] [IntroscopeAgent.Agent] Failed to create socket factory. java.lang.ClassNotFoundException: com.sap.sup.wily.saprouter.SapRouterSocketFactory at com.sap.smd.agent.loader.FileClassLoader.findClass(FileClassLoader.java:789) at com.sap.smd.agent.loader.FileClassLoader.loadClass(FileClassLoader.java:684) at com.sap.smd.agent.loader.FileClassLoader.loadClass(FileClassLoader.java:668)

Former Member
0 Kudos

hi i'm sorry for delay,

nping works, and the connection from Configuration from SOLMAN -> Managed works, the problem is from managed to Solman.

it seems that the managed try to reach the Enterprise Manager of Solman at localhost:5001 but in IntroscopeSapAgent.profile i configured the saprouter.

This is log

Manager localhost:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (188). 11/07/18 06:01:12 PM CET [WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at localhost:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (188). 11/07/18 06:01:12 PM CET [DEBUG] [IntroscopeAgent.Agent] java.net.ConnectException: Connection refused: connect (local port 58320 to address 0:0:0:0:0:0:0:0, remote port 5001 to address 0:0:0:0:0:0:0:1 (localhost))

Thanks

0 Kudos
Hi

Please configure the SAP Router by the following command on the Managed System Host:

  • smdsetup.bat addsaprouter route:"/H/Saprouter/H/SolmanHost" or "/H/Saprouter/S/Gateway/H/SolmanHost if you are using a gateway"

Verify the SAP Router connection by the following command :

On the Managed System Host

  • niping -c -H /H/Saprouter/H/SolmanHost -S "port"

On the SAP Router Host

  • niping -c -H localhost -S "port"

Verify the Saprouter.log on the SAPRouter Host for more details

Configure the Diagnostic Agent on the Managed System Host:

  • smdsetup.bat managingconf hostname:"SolmanHost" port:"5000x" user:"SMD_AGT_ADMINXX" pwd:"xxxxxxxxxxxxx"
  • smdsetup.bat managingconf hostname:"sapms://SolmanHost" Port:"81xx" user:"SMD_AGT_ADMINXX" pwd:"xxxxxxxxxxxxx

Verify the /usr/sap/DAA/SMDAXX/SMDAgent/log/SMDSystem.log to see if the connection is correctly working

See Also

More information about the Configuration of the SAPRouter

More information about Niping command:

More information about Diagnostic Agent for Solution Manager 7.2

More information about Diagnostic Agent for Solution Manager 7.1

  • 1907909 - How to connect Diagnostics Agent to Solution Manager system directly by using smdsetup script [VIDEO]
  • 1348549 - P4 over SAPRouter connection fails in SMD agent scenario