SLD Data Supplier to to SAP's Support Backbone, for AS Java, through a Web Prox

[benoit-schmid]

Good Afternoon,

I would like to configure SLD Data Supplier to Directly Send Data to SAP's Support Backbone as documented in SAP Note 2855951, for ADS Servers (AS Java).

Our AS Java Servers can not connect directly to the Internet.
It has to use a Web Proxy to create a outgoing HTTP connection to supply.landscape.services.sap.

Note 2855951 does note explain how to proceed to configure a web proxy.
It describes the configuration through a proxy only for an AS ABAP.

Could you you tell me how I could configure a web proxy for this SLD configuration ?

For an AS ABAP, it is also possible to use a SAP Router instead of a web proxy.
Is it also possible to configure the SLD of my AS Java to use a SAP router instead of Web Proxy?

Have a nice day.

[john_p_grimes]

Hi!

I see you've added the "SAP Cloud ALM" tag to this post. However, none of what you've written about seems familiar to me and the SAP Cloud ALM Product. Is there a more appropriate product tag that you could add to the post, so it gets attention from the right people? Using the correct tags is the best way to get the attention of people with the relevant expertise.

Thanks and regards,
John

[benoit-schmid]

Good Morning,

If you migrate to SAP Cloud ALM, you need to configure your On Premise server to SLD Data Supplier to Directly Send Data to SAP's Support Backbone because you can not send it to Solman LMDB anymore.

Anyone who migrate from Solman to SAP Cloud ALM has to perform SLD Data Supplier changes.

As my question concerns the migration to SAP Cloud ALM, I have used the Tag SAP Cloud ALM.

Have a nice day.

[benoit-schmid · Accepted solution]

Good Morning,

Thanks for you late answer Vera_Jiang.

As there is no possible way to handle this basic functionality with SAP AS Java tools, I have set a reverse proxy to solve the issue: AS Java -> Reverse Proxy (FQDN=sld.mydomain) -> supply.landscape.services.sap

For the one who may want to solve this issue.
This is a basic apache reverse proxy configuration that could be use for domain xxx.

<VirtualHost *:80>
ServerName sld.xxx

SSLProxyEngine On
SSLProxyCheckPeerName off
AllowEncodedSlashes On

ProxyPass / https://supply.landscape.services.sap/ nocanon
</VirtualHost>

On the Java AS, you need to configure:
NWA -> Configuration -> Infrastucture -> Destinations -> SLD_DataSupplier -> Edit
---
URL : http://sld.xxx/sld/ds
System ID: EMPTY
Client : EMPTY
Language : EMPTY
IgnoreSSL: Selected
User Name: SUser for SLD Update
Password : PAssword of the SUser
---

In case your network between your servers is not secure, you can make it work with https used between the AS Java and the Reverse Proxy. But you need to import SSL certificate of the sld.xxx in the AS Java Trust Store.

Have a nice day.

[benoit-schmid]

Good afternoon,

While waiting for a better solution, I wanted to mention that our AS Java has sent their SLD Data to the SAP Support Backbone by using a reverse web proxy on our site.

I created a reverse proxy xxx.mydomain that proxies requests to https://supply.landscape.services.sap.
In the AS Java, I have configured the following SLD_DataSupplier connection.
---
URL : http://xxx.mydomain/sld/ds or https://xxx.mydomain/sld/ds
System ID: Empty
Client : Empty
Language : Empty
User Name: Technical communication S-User
Password: Pasword of the Technical communication S-User
---

In the AS Java, ping test of SLD_DataSupplier connection worked.
Collecting and Sending the SLD also returned a success.

In the maintenance planner, I see that the System has been updated.

Therefore it seems to work. It is complicated compared to using a proxy server in SLD_DataSupplier.
But I have not found an easier way.

If you would know a better way to configure this SLD_DataSupplier, please do not hesitate to share.

Have a nice day.

[benoit-schmid]

Good Morning,

Thanks Vera for your answer.

I know that I can perform manual update of my systems to SAP Support Backbone.
But this is useless human resources consumption.

Switching to a new technology which is SAP Cloud ALM, should not bring us to prehistoric technology.
By prehistoric technology, I mean that Solman automates the LMDB pushes to SAP Support backbone.
Therefore SAP should provide the same automatic mechanism if case of Solman to ALM migration.

Have a nice day.

[Vera_Jiang88]

Dear Customer, 

It seems no existing official information contains how to support the JAVA data push by router or proxy. I will check this question with DEV support and give you the definite answer. 

BTW, there is a workaround to upload the JAVA system info to Maintenance Planner and SAP Portal manually. 

2287046 - How to Generate the System Info XML and upload to Maintenance Planner
2293050 - SUM: Generating a System Information XML File for use with SAP Maintenance Planner

Best regards,
Vera Jiang

[Vera_Jiang88]

Dear Customer, Unfortunately, setting a proxy only for the SLD_DataSupplier destination is not supported, as it is not part of the implementation by design. Best regards, Vera Jiang