Digitally signed notes - http 1.1 and compression

[JaySchwendemann]

Dear all,

we have (long by now) configured our SAP AS ABAP systems to consume digitally signed SAP notes via HTTP. We (as of now) refrained from using download service. That being said we carried (to best of our knowledge) everything out as SAP tells to

• RCWB_SNOTE_DWNLD_PROC_CONFIG is set to HTTP with Destinations "SAP-SUPPORT_PORTAL" and "SAP-SUPPORT_NOTE_DOWNLOAD"
• RCWB_SNOTE_DWNLD _PROC_ CONFIG returns all green checkmarks

That being said, we experienced a lag when downloading notes via SNOTE. We narrowed that down to the (good ol') "SAPOSS" destination being called in what I believe is an SAP internal check (through "CL_SCWN_NOTE_SAR_FILE_N=>IS_SYSTEM_INTERNAL").

Sure enough "SAPOSS" is not functional anymore and we get a timeout, hence the bad performance, when trying to download notes.

While that might be interesting for some of you, I think the solution to that might be straight forward: Delete the obsolete "SAPOSS" (and maybe ask SAP what the hell they were trying to do in the first place by means of opening an incident)

Now, however, this whole issue got me thinking: Am I wasting time / performance on other areas as well? Specifically I was thinking about this two options within the HTTP Destinations "SAP-SUPPORT_PORTAL" and "SAP-SUPPORT_NOTE_DOWNLOAD"

• HTTP Version = 1.1
• Compression = active
• Cookies = yes

I know that the automatic creation of said HTTP destination create them with "HTTP 1.0" "Compression = inactive" and "Cookies = no" but maybe SAP is being a little conservative

Are there any best practices on how to set the destinations / are the bespoke parameters supported? I could not find anything in the SAP notes for this

Many thanks and kind regards

Jens

[Former Member]

You will get no benefits from compressing already compressed content.