Skip to Content

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.

With release 7.5 SP10 of SAP Process Orchestration, the deployment procedure for deploying cloud integration content on SAP Process Orchestration has been improved. Now, you get direct status information of the progress of the asynchronous deployment steps. This improves transparency especially in case of deployment issues. If you like to know how to deploy cloud integration content on SAP Process Orchestration in general, please first read the Best practices Cloud Integration Content in SAP Process Orchestration – Deploy integration flows blog.

By the way, if you compare the screenshots of the previous blogs with the current one, you will notice that the layout of the deployment cockpit has been changed. With the latest shipment, the latest SAP UI5 themes have been applied. I hope you like the new look and feel.

We have logged on to our SAP Cloud Platform Integration tenant, and have selected a couple of integration flows. Now click on the deploy button. By the way, the new deployment behavior works for any deployment option regardless whether you deploy from file system or directly by accessing the tenant.

A pop-up appears showing the deployment progress. You can either close (hide) the dialog, or wait until the deployment has been finished, either successfully or with an error. If the deployment takes too long, a clock counts down, and eventually the pop-up automatically closes.

Even if the pop-up is hidden, the deployment progress is shown in the deployed cloud integration content table.

The status of the deployment can be checked later. Click on the bubble at the bottom of your browser. The information provided here can be filtered by the status, i.e., either successful or with errors. All entries can be cleared from this screen.

 

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Philippe Addor

    Hi Alexander,

    I have a question related to the deployment of CPI content on PO as described here. It is apparently mandatory to configure a virus scanner before being able to deploy iFlows – or deactivate the virus scanner function completely, which we have done for now. However, it’s not clear what exactly is the purpose of the virus scanner – is it to scan the deployed files or the message exchange in general (like what is also possible for standard PO messages)?
    Thank you,
    Philippe
    (0) 

Leave a Reply