Skip to Content
Technical Articles
Author's profile photo Irina Kirilova

SAP Continuous Integration and Delivery for SAP Integration Suite Artifacts

With its latest release, SAP Continuous Integration and Delivery provides a predefined pipeline for SAP Integration Suite Artifacts. In this blog post I would like to show you the steps how to use this new functionality and configure a CI/CD pipeline for the development of integration content in SAP Cloud Integration.

Prerequisites

Procedure

  • First, you have to transfer your integration artifacts from SAP Cloud Integration to a repository of your source code management system. To do this, perform the following steps:
    • In SAP Cloud Integration, open your integration package and choose  Artifacts.

    • Choose Actions→ Download.

    • Save the *.zip file to your choice of destination.

    • Extract the file and upload its contents into your repository.

      Note: Repeat the procedure in case you make changes in your integration flow in SAP Cloud Integration.

  • In SAP Continuous Integration and Delivery, configure a new job as described in Create a Job. As Pipeline, choose SAP Integration Suite Artifacts.

  • In this demo, I will use Job Editor from the Configuration Mode dropdown list.
  • In the Stages tab, specify the general parameters. Then switch on and configure the stages you want to execute.
  • Don’t forget to save your job.

Of course, if you prefer, you can use the Source Repository Option for configuring your job.
In that case you can follow our documentation instead.

After you have created the job, you can either run it manually, or you can create Webhook to automate your builds.

The picture below shows the result of a job run. In this view, you can monitor its outcome.

 

Documentation & Further Readings

If you have found this article useful and want to learn more and use the SAP Continuous Integration and Delivery to manage your SAP Integration Suite Artifacts, take a look at the following resources:

Not what you have expected?

If you think that we’ve missed important use cases, please help us improve our offering by leaving a note to this blog or submit your idea in SAP Business Technology Platform Continuous Influence Program.

Assigned tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Srini Reddy
      Srini Reddy

      Hello Irina Kirilova

      I have a few questions after going through the documentation.

      1. Does this use any integration artifacts from the source code repository or pulling the artifact from the Integration Suite instance?
      2. Do I need to create multiple pipelines to deploy multiple iflows or Can I deploy multiple iflows from the same pipeline?
      3. How to handle iflow configuration parameters in the pipeline?
      4. Any plans to support Azure Repos for the webhooks?

      Thanks,

      Srini

      Author's profile photo Irina Kirilova
      Irina Kirilova
      Blog Post Author

      Hi Srini,

      1. The service takes the artifatcs from a Git Repository. In the procedure above, I have described one possibility how to do that.
      2. You can deploy one flow per pipeline. In case you have multiple flows in one package, you have to create multiple pipeline for them.
      3. Currently not supported in the service. In case you need more flexibility in your pipeline, you could consider using Project "Piper" which covers this feature already - https://www.project-piper.io/steps/integrationArtifactUpdateConfiguration/
      4. We get frequent customer requests for this, so we are considering the feature for 2022.

      Best regards,

      Irina

      Author's profile photo Ramoji Sabnekar
      Ramoji Sabnekar

      Hi,

      I have one question related to SAP CPI DS.

      Question :  CPI-DS option is getting covered in SAP BTP Integration suite?

      Please clarify.

       

      Thanks, Ramoji

      Author's profile photo Mayur Belur Mohan
      Mayur Belur Mohan

      No CPI-DS is not part of SAP BTP Integration suite.