Skip to Content

Pros and cons of using a single SAP Cloud Integration tenant

I'm looking to understand what are the best practices and pros/cons for using only one tenant for Cloud Integration for prod and non-prod environments. Technically, it seems possible, but why is it advised or not?


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Oct 05, 2018 at 07:58 PM


    I can think of some cons of using only one tenant for PROD and NON-PROD environments:

    - Some prepackaged content (configure-only) would use non-configurable endpoints in the iflows. This would prevent the deployment of copies of this iflow at the same time (e.g. for TEST and PROD). However when these cases are identified we usually recommend opening a support incident to make the endpoint configurable as it is a easy fix.

    - When something goes wrong with a TEST implementation/deployment that would affect the whole tenant (OOM, deadlocks, etc), PROD would also be affected.

    Best Regards,

    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.