Skip to Content
author's profile photo Former Member
Former Member

Enabling http Proxy in SMD Agent

Hi

I have installed the Diagnostic Agent 7.3 on a managed SAP system and have connected it to our Solution Manager 7.1 system. However, the SAP system is not directly accessable by the Solution Manager due to our company network restrictions. I am connecting it via our saprouter which works fine except the SMD Agent is also trying to access the Solman system using URL http://<solman host>:52200/sap/bc/srt/scs/sap/e2e_dcc_push?sap-client=<client>

I notice in smdsetup.sh there are some settings output for http proxy.

_________________________________________________________________________

SAP Solution Manager - Diagnostics Agent - Copyright (c) 2012 SAP AG

_________________________________________________________________________

------- VM Properties ----------

OS : Linux

OS Version : 2.6.32.49-0.3-default

OS Architecture : amd64

OS data model : 64

Java Vendor : SAP AG

Java Home : /usr/sap/<SID>/SMDA97/exe/sapjvm_6/jre

Java Version : 1.6.0_41

Java Classpath : .:lib/patch_7.10.8.0.20130129152302/launcher/smdagentlauncher.jar:lib/patch_7.10.8.0.20130129152302/sapxmltoolkit.jar:lib/patch_7.10.8.0.20130129152302/smdagent.jar:lib/patch_7.10.8.0.20130129152302/tc_sec_secstorefs.jar:lib/patch_7.10.8.0.20130129152302/iaik_jce_export.jar:lib/patch_7.10.8.0.20130129152302/smdserver.jar:lib/patch_7.10.8.0.20130129152302/logging.jar:lib/patch_7.10.8.0.20130129152302/exception.jar:lib/patch_7.10.8.0.20130129152302/sldclient.jar:lib/patch_7.10.8.0.20130129152302/sldserv.jar:lib/patch_7.10.8.0.20130129152302/jARM.jar:lib/patch_7.10.8.0.20130129152302/httpclient.jar:lib/patch_7.10.8.0.20130129152302/sapj2eeclient.jar:

Java Runtime version : 6.1.047

Java Specfic. version : 1.6

File Encoding : UTF-8

Console Encoding : null

HTTP Proxy : null

HTTP Proxy port : null

HTTP non Proxy hosts : null

Does anyone know how to set the HTTP Proxy and port. I thought it was via the smdagent.properties via parmameter

smdagent.javaParameters=-DP4ClassLoad=P4Connection -Dhttp.proxyHost=<proxy> -Dhttp.proxyPort=<proxyport> -Xmx256m -Xms256m -XX:MaxPermSize=128m

but this did not seem to work. Any ideas welcome.

regards,

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 19, 2013 at 07:04 AM

    You can use saprouter to connect to sap solution manager. Check smdsetup addsaprouter option.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Richard,

      I also tried adding http.proxy* parameters to the SMD agent profile before being referred to the wsnotify.proxy* properties, but without success (see my reply dated Sep 2, 2013 2:56 PM). But maybe your problem is a bit different from mine. Please report what SAP suggested as solution.

      Best regards,

      Michael

  • author's profile photo Former Member
    Former Member
    Posted on Jan 09, 2014 at 11:28 AM

    Hi Richard (and all the others trying to use a http proxy for SMD2SolMan communication),

    I am facing a similar problem: some SMD agents (only those in the DMZ, but not the ones in the intranet!) have to connect ot our SolMan via saprouter. Thus they also should use a http (reverse)proxy (SAP Webdispatcher) for http communication to SolMan. As far as I understand, this SAP Webdispatcher can be maintained centrally at "SOLMAN_SETUP--> Configure Connectivity--> Configure Web Dispatcher". However when maintaining a SAP Webdispatcher in SOLMAN_SETUP, this would be used by ALL SMD agents! And this would not be working in our landscape. I opened an according OSS incident (new wording!) for this matter.

    Best regards,

    Jan

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.