Skip to Content

How to promote projects in SAP Cloud Platform Integration

Hi all,

We are integrating data from SAP ECC to IBP through SAP Cloud Platform for Data Service. In ECC we have three environments (Dev, Qua, Prod) but in SAP CPI we have only one.

We have modelled all our projects from SAP Quality Environment, now we need to promote to production environment and we have the below questions:

  • 1.Do I need to install a new Agent or can I use the same installed agent?
  • 2.In my Datasources I have IBP Development and ECC Quality, I understand I need now to add IBP Production and ECC Production
  • 3.Once I have my Prod datasources do I need to create again all the projects in the sandbox and then promote those? Or can I promote my projects from ECC Quality – IBP Dev so that it will connect ECC Prod with IBP Prod?

Thanks in advance for your support.

Best Regards,

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Oct 22, 2019 at 05:19 PM

    Hi Carlos,

    Please see answer to your questions:

    1) As s best Practice, its advised to have separate agents for sandbox and Production Instances for CPI-DS, reason being if we use same agent, in case there is server downtime where agent is installed or server is overloaded due to some testing activities happening, that may impact production jobs as those will run on same server. having said said there is no restriction/limitation from config point, you can use the same agent, just be watchful of the jobs running in CPI-DS test and Production instances.

    2) you can create the production connection to ECC after promoting the jobs to production, when you promote the jobs to production first time, data stores will be imported in production and you can create a production connection and default it in data stores so jobs will use production config when they run.

    3) you would only need to create Project - names in production and when you promote the jobs from sandbox to production you would get a popup asking in which project you want to move the job. we create same name projects in sandbox and production and promote respectively.

    Do let me know if you have any further questions.

    Thanks,

    Nikunj

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 23, 2019 at 07:31 PM

    I fully agree with Nikunj on all topics!


    Just in addition my recommendation is to work with separate so-called sub-organization, see here: Working in Multiple Environments.

    Principle is that you get with the additional sub-organization (which you request via OSS message, no extra license as far as I am aware of) a second URL. This extra URL has only one "Sandbox", that serves as Development and should be connected to the ECC-Dev system.

    From here you can promote (= transport) your data flows to the "Sandbox" of your main URL, which then will serve as Quality system, connected to the ECC-Quality system. So you do not need to create separate data flows.

    And from here you will be able to promote to "Production", which should be connected to the ECC-production-system.


    You will need one extra Agent for the extra sub-organization. Plus one agent for the main URL: And here you can theoretically use the same agent, but usually due to security aspects company use an additional agent, as mentioned by Nikunj.
    In case you have the server running on Linux, you can install more than one agent on one server. When running on Windows, you would need separate servers. And you can use the same server that you may use in case you are already using SDI agent for order based planning or the cloud connector for other cloud products.
    Again, for security reasons it is best practice to have a separate server for productive agent, no matter what operating system.

    -----

    Regarding IBP as target system: I assume you have two-tier IBP, dev and production only?

    Than you can connect the IBP-DEV to both the additional and the main CPI-DS-URL as data store, and the productive on the main URL. That means, you can load from ECC-DEV plus from ECC-Q to IBP-Dev, by switching the target store. As long as you are using the same planning area, you dont need to replicate any data flow. Just make sure that you dont load at the same time into the same version the same products/locations, else you get inconsistencies in regards to data.

    IBP-Production should only be connected to ECC-Production via the main CPI-DS-URL and only after promoted to "PRODUCTION"

    -----

    Totally confused? Just read the online docu

    If you search for CPI-DS in here , you will find some useful links to get started, even if they are partially pretty old they are still helpful.

    -----

    And if you ask yourself why work with sub-organizations: There are several reasons.

    One is that you have a better tier-strategy and everything will be more organized, especially if you have many data flows, better overview. You get a clear promote/transport path, each CPI-DS has one source system in ECC (or BW or APO or whatever).

    Plus, when you need to write back data from IBP to ECC with web services, it is MUCH easier to work with 3 separate CPI-DS areas.

    And a couple of other reasons...

    Yours
    Irmi

    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.