Skip to Content
Technical Articles
Author's profile photo Alexander Bundschuh

Best practices Cloud Integration Content in SAP Process Orchestration – Deploy integration flows

This is a blog within a series of best practices blogs for cloud integration content in SAP Process Orchestration. For an overview of all blogs published within this series so far, refer to the overview blog.

The following blog covers the deployment of cloud integration content on SAP Process Orchestration. We assume that you have already copied an integration package to the workspace in your SAP Cloud Platform Integration tenant, and that you have done the required configuration such as selecting the right product profile, maintaining the communication settings, maintaining the proxy, etc.

Prerequisites for directly accessing the tenant

The preferred option to access the tenant is to create an http destination using the destination service of the SAP NetWeaver Administrator. Open the SAP NetWeaver Administrator via url http(s)://host:port/nwa, and switch to the Configuration –> Security tabs. Select the link Destinations.

Create a new http destination. Enter the url of the tenant.

Select basic authentication, and enter the user credentials. Note, the user entered here requires the role AuthGroup.IntegrationDeveloper on the SAP Cloud Platform Integration tenant.

Deployment of cloud integration content

Open the Cloud Integration Content Management cockpit on your SAP Process Orchestration system via url http(s)://host:port/IGWGBDeploy/Admin. On the Integration Content tab, select button Deploy.

In the upcoming dialog, you have three options, either directly accessing the tenant workspace via an http destination or manually entered, or via file upload. Here, we choose the Cloud Tenant via Destination option, and select the beforehand created http destination from the drop down menu. Then, click on Next.

On the next screen, all your packages within the workspace are displayed. Select the Integration Flow and click on Deploy. Here, we have chosen the electronic transport registration for Hungary package. By the way, you can select multiple integration flows and deploy all at once.

The deployment is done in the background. On the bottom of your browser, you can see a notification that the deployment has been triggered.

After a while, the status of the integration flow should have turned green. If not, check the deployment log in the SAP NetWeaver Administrator (below tabs Troubleshooting –> Logs and Traces, select link Log Viewer, here choose Developer Traces view).


In case of http based communication components on the sender side, you can display the generated endpoint. Mouse over the deployed integration flow, and select View Endpoints from the context menu.

Optionally, scroll down to the integration content details, here you also find a link pointing to the endpoint.

This will context-sensitive open the End Points tab showing the endpoint of the selected integration flow.

Operating cloud integration content

You have the options to start, stop or restart integration flows. Select the integration flow, and then select either option. Note, if you restart an integration flow with run once scheduling, it won’t schedule again since it would then violate the run once settings. Here, you need to undeploy and deploy again.

Configure cloud integration content

As of release 7.5 SP10, you can configure integration flows from within the deployment cockpit of SAP Process Orchestration in case that externalized parameters have been defined for the particular integration flow. This way, you can configure your integration flow parameters without the need of accessing the package on your Cloud Platform Integration tenant. In the integration content details of an integration flow, you find a new button called Configure.

In the upcoming pop-up, all externalized parameters are displayed. You can maintain the parameters, and re-deploy.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Sudhansu Behera
      Sudhansu Behera

      Hi Alexander,

      Thanks for the nice blog.

      I am trying to connect our CPI instance with SAP PI and following the steps you have mentioned.

      I am stuck at the point of HTTP Destination creation in the SAP PI NWA


      I tried a ping to the Tenant Management node (tmn) but I don't get a response from it.


      Could you please tell me if you are able to ping the tmn successfully ?

      In the PI - Cloud Integration Content Management Cockpit, i receive the following error-


      Author's profile photo Alexander Bundschuh
      Alexander Bundschuh
      Blog Post Author

      Hi Sudhansu,

      this might be a network issue, maybe you need to setup a proxy in the java app server

      best is that you reach out to your basis admin


      Author's profile photo Sudhansu Behera
      Sudhansu Behera

      Hi Alex,

      Thanks for your response. I spoke to our basis admins and we tried ping as well as telnet from our PI system, but unfortunately the connectivity is unsuccessful from PI to CPI.

      We also tried to do a Connectivity Test from another CPI instance to our CPI instance with the "Test Connectivity" feature of CPI. In this case the connectivity was successful.

      It seems just the hostname - is not accessible external (internet).

      Author's profile photo Sudhansu Behera
      Sudhansu Behera

      Hi Alex,

      Thanks for your earlier response. The issue is resolved when i used the destination name - IntegrationContentCatalog. The Integration Contents in Cloud Integration Content Management Cockpit is visible (although i get still get a 404 message when performing a ping).

      Excerpt: The destination type must be HTTP. The recommended name for the destination is IntegrationContentCatalog