Skip to Content

SAP SCP Reduce bandwidth usage when accessing documents from content server

Hi Experts,

Our S4HANA along with Content Server is hosted in a private cloud. SAP DMS will be used to store documents in the content server. The private cloud data centre is located closer to our geo location. We are planning to build mobile as well as web application on the SAP SCP. We came to know that there are no data centres of SCP in our country.

All of our documents stored in the content server are large in size. Hence we believe that if we try to access these documents on the cloud platform application then there will be a rise in our internet bandwidth consumption. We would like to know if we can access the documents directly from the content server rather than taking the SAP SCP -> Cloud Connector -> SAP ERP route.

I found the following link on sap help which describes keeping an additional Content Server in the DMZ zone so that the file can be accessed from the extranet.

Content Server Network Security

Please advise if the above mentioned link is the best method or if there are any other better ways to do it.

Regards,

Sam

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 10, 2018 at 03:24 PM

    Hi Sam,

    Let me start by saying that while being a SAP employee the following answer is based on my thoughts as a consultant and I have no direct relation to any of the product teams (i.e.: I don't belong to the Content Server team).

    With that in mind, I'll begin by saying the obvious: The private cloud and the public cloud run on different landscapes. Meaning: there is no direct communication between them. Thus, you'd really need to have the Cloud Connector to allow communication between the two worlds.

    What I believe would be a possible approach to avoid the extra bandwidth on the private cloud is to have a Cloud installation of SAP Cache Server (Content Server Cache) directly on SCP. In order to achieve this you would require a Linux VM subscription to perform the Cloud Installation of SAP software. Then setup a Cache Server on this Linux box - just as you would in a normal WAN setup (check also SAP Note 216419). Then, connect it to your Content Server via Cloud Connector URLs. Once this is done, the first time a document needs to be fetched from the Cache Server URLs it will request it from the Content Server (local repository) and later on any request to the same document will be retrieved directly from the Cache Server (cloud repository). I have never seen such use case in a productive mode, but it should work. But, just to be safe, I would test it thoroughly via a PoC.

    Another possibility - and let me say it is way more complex - would be to have your users fetch documents from the a cloud service. We do have the Cloud Document Service on SCP. Then you would need to find a way to maintain the cloud repository in sync with the local Content Server's repository. I must say that this would not be very transparent to the end-user in terms of usability, but would surely transfer the onus of bandwidth consumption to your SCP account. To achieve this kind of complex integration it would be required development skills on the DMS side to perform initial document upload to the CMIS repository and delta uploads to keep it in sync. I'm not aware of any single solution that would do this task automatically.

    Hope this info helps.

    Best regards,
    Ivan

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Ivan Mirisola ,

      First of all I would like to thank you for providing an answer to my question.

      I understood the options that you have provided as a solution to problem. Could you please help me just one more time in validating whether the following scenario could also be a possible solution.

      • An additional content server is placed in the demilitarized zone (DMZ) of the private cloud
      • The DMZ content server is connected to the intranet content server on the private cloud via ODBC
      • A request is made from an app hosted on the SCP cloud for a document present in the intranet content server
      • This request now reaches S4HANA DMS via cloud connector
      • With the DMZ content server, the documents requested can now temporarily be placed in the database instance of the DMZ content server, by copying them into a DMZ repository by running some programs based on request
      • Then the URL required for accessing them can be given to the requesting client from SCP, as a response to request
      • When the URL is executed the file is directly accessed from the private cloud since the DMZ content server is accessible over the internet
      • Once the file is accessed the file can be removed from the DMZ content server

      Thanks & Regards,

      -Sam