← Blog

Figaf DevOps 2.15: CPI on Cloud Foundry

Figaf DevOps 2.15 adds a visual iflow diff, Cloud Foundry support for CPI and API Management, a transport API, custom header search and Tradacom.

October 20, 2020 · 2 min read

I always love shipping new important features, that make life easier for integration developers. All the things that I did not have once I was starting out.

This is one of the times.

We have added quite a lot of new improvements to make it easier to manage SAP CPI.

Visual iflow diff tool, so you can see if there are any changes between the two iflows. It is much easier to view visually. We already have other options to see the BPMN model in a text view. It could be a little difficult to see what was changed between the two iflow versions.

Figaf visual diff of two SAP CPI iflow versions, with changed steps highlighted and the XML of the changed step shown side by side

Support Cloud Foundry for SAP CPI and API management, so we support the platform that customers are moving to. We have also upgraded the Gradle plugins to support those platforms. To use this you will need a user and then client ID/Secret to send a message to the Cloud Foundry application. Once you create a CPI or API Management agent you have the option to select the Neo or CF platform. Read more on Figaf on Cloud Foundry.

This is also useful when you want to migrate to CPI on Cloud Foundry. Here we also have an option to save a system with our virtual landscapes.

API to work on tickets and transports. This will allow you to orchestrate your transports from external tools like Azure DevOps or CTS+. This way you can ensure your integration transports are delivered at the same time. Read More.

In SAP CPI monitor custom headers so you can search for other values, and only see the iflows you have access to. This is if you use the option if you want to search in more than Application ID. You will need to add some custom Groovy script to save the values. You will still only be able to see the iflows that you have in a given tile/group. So users cannot search to see iflows they should not have access to. You can also see the Custom Headers in the main instance viewer.

Figaf CPI monitor searching messages by custom header name and value, with the matching custom header shown in the message properties

Tradacom support in comparisons. We already support EDIFACT and X12, so this is a logical addition to enable.

Figaf test comparison of expected and actual Tradacom messages, with changed segments highlighted in orange

When doing SAP CPI testing automatically start fetching result after the sending of messages has ended. It has been an area that has been bugging me when I was doing demonstrations. Now it works much smoother. And it will also increase the usability of the application.

Try Figaf DevOps Suite

You can always try out the tool yourself. Just start a free trial.

This post covers these products

Capabilities covered

  • Change and transportMoving a change between systems is manual, undocumented, and often done by someone outside the integration team.
  • Monitoring and alertingYou find out an integration failed when the business calls you.
  • Regression testingYou cannot tell what a change broke until someone downstream complains.

More from the blog

All posts →

See this working in your landscape

No credit card required.

Integration cost calculator →

Start your free trial

No credit card required

Try Figaf DevOps Suite free for 30 days. It takes less than an hour to get started, and we send everything you need by email.

Join our newsletter

Get the latest about Figaf, SAP and anything relevant to SAP integration, every week in Figaf Weekly.