Connection between SMD Agent and SMD server via SAProuter

[Former Member]

In our scenario, we have to setup the connection between SMD agent and SMD server(solution manager server) via saprouter. But during the installation of SMD agent, we can only specify the hostname of the managing system, we have no place to add saprouter string(/H/..../H/). I I am not sure if we could connect the agent and server via saprouter, if so how to do it?

Hope someone can give us your precious advices on this issue.

Karl

[former_member213255]

almost 7year ago, but 🙂

smd.agent.connection.saprouter this property can solve the issue.

https://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+7.2+Connectivity+Troubleshooting

[Former Member]

In our scenario, we have to setup the connection between SMD agent and SMD server(solution manager server) via saprouter. But during the installation of SMD agent, we can only specify the hostname of the managing system, we have no place to add saprouter string(/H/..../H/). I I am not sure if we could connect the agent and server via saprouter, if so how to do it? 
> 
> Hope someone can give us your precious advices on this issue. 
> 
> Karl

Hello Karl

There are different types of connections that you can use for the SMD agent to connect to the SMD server. Eg :

- direct connection to the P4 port (5xx04) of the Java EE dispatcher node of the SMD server

- Direct SSL connection to the Java EE Dispatcher node

- P4 Connection via the Java EE Message server of the SMD server

However in these connections the usage of a SAPRouter is not technically possible. SAPRouter is not meant to be used in such types of connections and hence you would not be able to make a connection via the saprouter.

For more details on SMD Agent configuration and troubleshooting use the Agent installation guide on

https://websmp101.sap-ag.de/diagnostics

Regards

Amit

[Former Member]

I have a similar question; why I don't have the option to configure a proxy, user proxy and/or saprouter. In many data centers hosted systems are separated in different physical LANs and the proxy is gerenrally not allowed on such kind of systems. For every HTTP RFC in an ABAP system it is possible to insert a separate proxy config and for every host clients like sapccm4x, 4r or ping it is possible to add a saproute. Why the f**k the SMD environment don't support this?

[Former Member]

I have a similar question; why I don't have the option to configure a proxy, user proxy and/or saprouter. In many data centers hosted systems are separated in different physical LANs and the proxy is gerenrally not allowed on such kind of systems. For every HTTP RFC in an ABAP system it is possible to insert a separate proxy config and for every host clients like sapccm4x, 4r or ping it is possible to add a saproute. Why the f**k the SMD environment don't support this?

Hello Rene,

Please understand that a SAP Router is not meant for use in such connections.

Also we would expect a certain amount of decorum while posting replies or comments. Please avoid using phrases which have to be abbreviated by " *** " .

Hope you understand that this is a technical forum and not a place to vent out disappointments.

Regards

Amit

[Former Member]

Perfect; and thanks for your response. I found this help page for developers to implement P4 support over SAP router: http://help.sap.com/saphelp_nw73/helpdata/en/48/2992d7ad8758d7e10000000a421937/content.htm

But in the SM Diagnostics Setup options I can set up only a direct HTTP adresses and have no options to set up connections over a sap router to P4 ports directly. I can at the moment only solve my problems with NAT or firewall rules.

And also the diagnostic agent setup has no options to config a proxy or sap router. I found yesterday a blog on sdn side with screenshots of the setup with all available connection opetions to SLD... sry I can not post this link today.

This is an official statment of SAP from the current version of SMD guide; it is also possible but why not from the beginning???:

In some network conficurations, the Diagnostics agent has to connect to the Managing system though a SAP router.

This feature will be fully supported in Solution Manager 7 Ehp2 (7.02).

In order to enable this feature in Ehp1, please contact the Diagnostics Agent support team to get information on how to

setup the agent and on which patch level you can perform the installation.

This thread were a long time not answared; proxy and routing connections are mostly stepmotherly handled by SAP; this is also a problem by set up of automatic RFC generations in SMSY; why there are in the setup assitents no options to set up the router string.

I have absolutly no comprehension for this in year 2011. All this technics are good known and long time tested.

In this case the f**k has provoked an answare to this thread and this is what I expected; but sorry for my style You are right I could also writh why the heck

FAQ:

SMD root side on SDN: http://service.sap.com/diagnostics

SM FAQ: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/4e49dbea-0c01-0010-91bd-f0b61388c9ae

SM Setup Home: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home

SM Diagnostic Troubleshooting Guide: https://websmp201.sap-ag.de/~sapdownload/002007974700000409092009E/DiagAgent_TroubleShooting.pdf

SMD Candidate Setup: http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents

[mkloeffer]

Hi Rene,

sorry but I have to correct my colleagues. The connection between the Diagnostics Agent and the Solution Manager system can indeed be configured using a SAProuter connection.

This is available since the Diagnostics Agent 7.20 and is decribed in the appropriate Agent Installation Guide, you can find attached to the following SAP Note:

https://service.sap.com/sap/support/notes/1368413

on page 17.

Additionally in SolMan 7.1 you can also set up the RFC connection within the standard UI using a defined SAProuter connection in the UI in solMan_Setup

I think this should solve your problem, but let me know if I got something wrong...

Best Regards,

Michael

[Former Member]

Here the missing link to the Wiki: SMD Agent installation: http://wiki.sdn.sap.com/wiki/display/SMSETUP/InstallationofSMD+Agent

Diagnostic Setup Guide: https://service.sap.com/sap/support/notes/1368413 >> 720_Diag_Agent_Setup_Guide.pdf

@Michael Kloeffer

thx for your feedback: we redisigned in the meantime the network topology to have direct access to all satalite systems without saprouter or proxy (only with firewall). But good to know that the agents are meanwhile able to connect via SAP Router

[Former Member]

A last question, somewhere in the SLD the registered Agents are stored; where I can find these... I don't remember that. I would like to remove obsolet Agents and check other problems e.g. "The host name of the managed system (as declared in SLD) cannot be resolved"