Skip to Content
Technical Articles
Author's profile photo Kamlesh Zanje

SAP Cloud Integration – Deployment status in the Integration Flow Editor

Introduction

With the 5.24.x/6.16.x release, SAP Cloud Integration provides a feature to show the deployment status in the integration flow web editor. In this blog, I will give a detailed overview on this feature.

This feature is described in the SAP Help Portal ( see deployment status in the iflow web editor).

Deployment status feature in the integration flow editor has been enabled to address the following use cases for an integration developer

  1. To know the real time runtime status on the trigger of explicit deploy action without navigating to Monitoring page.
  2. To know the deployment status, runtime and other details such as deployed version, deployed by, deploy on for an existing deployed iflow in the deployment status tab.
  3. Easy navigation from the designer to the manage integration content of the operations view to troubleshoot the error cases.
  4. Show short error message for the deployed integration flow whose runtime status is “Error”. This will help Integration developer to fix the issue without need to navigate to the operations view.

Note – The first three increments are available in this release, however the fourth one would be available in the forthcoming release. You will be notified once it is available.

Let us have a quick walk through and understand the behavior of the feature.

Open the integration flow which is not yet deployed. You will notice Deployment Status as “Not Deployed” in the page header of the integration flow editor.Image1: Integration flow deployment status is “Not Deployed”

You will notice a Deployment Status tab when an integration flow canvas is clicked.Image2: Deploy status tab in the integration flow

 

Trigger the deploy action explicitly. You will notice a real time status in the page header. Deployment status is Deployed along with the timestamp and Runtime status will be “Starting”.

In addition to this, deployment status tab will be prefilled with the real time data.Image3: Deploy action triggered.

After few seconds, the runtime status of the deployed integration flow would be “Started”.Image4: Runtime status “Started”.

Now let us understand how the runtime status will look when the deployed integration flow goes into Error status due to some reason.

Deployed integration flow goes into “Starting” semantic status and other details are populated as well.Image1:  Deploy action triggered.

After few seconds, the runtime status of the deployed integration flow would go into “Error”. Integration developer can click navigation link to navigate to the manage integration content of the operations view to trouble shoot the root cause.Image2: Runtime status is “Error”.

Manage integration content of the operations view is opened in a new tab. Integration developer can analyze the root cause and can solve the erroneous situation.Image3: Manage integration content of the operations view

Benefits

  1. Deployment and runtime status is known prominently in the designer. No need to navigate to Monitoring view to know whether the deployed artifact is started or in Error.
  2. Easy navigation to the manage integration content from the designer.
  3. Deployed version, deployed by and Deployed at details can be figured out from the designer.
  4. Short error message in the designer helps to resolve the issue by staying in the designer.

Points to note

  1. Deploy status is available regardless whether integration content is configure-only or editable.
  2. This feature is available in the following artifacts
    1. Integration flow
    2. REST API
    3. SOAP API
    4. ODATA API (Template based)
  3. We will bring this capability in other artifacts such as Value mapping, Script collection, Message mapping etc.

Next steps

In the forthcoming increment we will produce increment which will show short error message when the deployed artifact runtime status is “Error”, so integration developer can probably fix the issue by staying in the designer and without navigating to the operations view.

 

I hope, you can benefit from the feature presented in this blog post.

In case of questions or feedback, please feel free to comment on this blog.

 

Assigned tags

      12 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Malte Schluenz
      Malte Schluenz

      Hi Kamlesh,

      great and helpful feature!

      I would kindly like to ask you to consider putting the deployment and design-time version also to the header, so that it is easily comparable if the latest version is deployed.
      What do you think?

      Best regards,
      Malte

      Author's profile photo Kamlesh Zanje
      Kamlesh Zanje
      Blog Post Author

      Hello Malte,

      Thanks for the feedback.  I think it would be useful to show design time version as well.

      But in some of the cases, the design time version would be "Draft", mainly when INT.developer is modifying the design time iflow and saving without version.  Will it be useful and value add to show "Draft" as a DT version? Let me know your thoughts.

      Thanks & Regards,

      Kamlesh.

      Author's profile photo Malte Schluenz
      Malte Schluenz

      Hei Kamlesh,

      I agree that having stated draft will not be that helpful.
      However, I think that displaying every time the same details at nearly the same position is easier to understand (also that your iflow is in draft). So I would also display draft status.

      Best regards,
      Malte

      Author's profile photo Kamlesh Zanje
      Kamlesh Zanje
      Blog Post Author

      Hello Malte,

      Thanks for reply and sharing your view. I'll take this requirement further. Probably we can show the design time version in the Deployment Status tab for a comparison with the deployed version.

      Regards,

      Kamlesh.

      Author's profile photo Allen Chew
      Allen Chew

      Another great feature that save a lot of time. It is always nice to know the iFlow deployment status upfront without further clicks.

      Author's profile photo Kamlesh Zanje
      Kamlesh Zanje
      Blog Post Author

      Thanks Allen for feedback and sharing your view on this feature.

      Author's profile photo Robert Jancich
      Robert Jancich

      Great feature. Do you also consider to make the status actual LINK to directly jump to monitoring of that iflow? That would be another great and simple feature to save lots of time!

      Author's profile photo Kamlesh Zanje
      Kamlesh Zanje
      Blog Post Author

      Hello Robert,

      Thanks for sharing feedback. You would have noticed that the click on the link "Navigate to Manage Integration Content" of the iflow editor open the Monitoring view in a new tab, but it doesn't filter the iflow.

      We have plan to enhance this behavior, but it needs some grooming and alignment. Nevertheless once this enhancement is available, it will notified via documentation and blogs.

      Regards,

      Kamlesh.

      Author's profile photo Robert Jancich
      Robert Jancich

      Hello Kamlesh

      thank you for your answer. Indeed i didn't notice first that option, because I noticed it just yesterday while I was doing a "training exercise" on openSAP. however, if you are already working on that feature, please consider directly putting link to that content text (saying e.g. Deployment Status: Deployed on Aug 11, 2021, 23:54:02, Runtime Status: Started) because than you normally can access it by one direct click while working on flow - anytime. Potentially often the bottom bar with option Deployment status is whole hidden and you need to click to see it. Than also you need to access that tab before clicking the link itself - this all seems funny but doing 1 click only instead of 3 clicks, will bring the speed, yes at least 3 times 🙂

      Author's profile photo Kamlesh Zanje
      Kamlesh Zanje
      Blog Post Author

      Hello Robert,

      The idea was to show the most prominent deployment details such as deployment status , deployment datetime and runtime status on the page header of the iflow web tooling and for other additional details such as deployed version, deployed by and navigation link in the property tab of the iflow editor which can be leveraged on demand basis as and when required.

      For an example when the deployed iflow is in the error state and if it is not solvable via a short error message ( next enhancement, stay tune !)  then I would like to navigate to the monitoring view via easy navigation link from the designer to troubleshoot further.

      Nevertheless, if you think navigation link in the page header would be useful for an end user regardless the runtime status then let me assess and groom this requirement. Thanks for your feedback and observation sharing.

      Thanks & Regards,

      Kamlesh.

      Author's profile photo Robert Jancich
      Robert Jancich

      Thank you. I really appreciate our voice is heard. any improvement from getting several "clicks" directly to get by one click to most wished content is helpful. i also don't want to have "overcrowded" options sometimes, but if that is smartly designed, or configurable, why not. one such great things was automatic next step proposal when building flow. i know it's based on AI but is really so smart and speed up your choices! 🙂 thanks!

      Author's profile photo Kamlesh Zanje
      Kamlesh Zanje
      Blog Post Author

      Thanks for explanation and yes I'll log your ask in a backlog to consider in the future increments.