The migration step is the easy part
“Export the iFlow” sounds like two minutes. The iFlow is the easy part. What travels with it is harder.
Figaf with CPIHelper
CPIHelper and Figaf: a great combination
You already use CPIHelper to work faster in SAP Cloud Integration. Figaf takes care of the rest: testing, transport, documentation and monitoring.
Focus on building integrations
We have built a tool that simplifies the way you handle SAP Cloud Integration (SAP Integration Suite). We want you to focus on creating integrations, while we handle everything around them:
- Automatic test cases, created from the messages your iFlows already process
- Transport of your integrations from development to production, with documentation and configuration
- Virtual tenants, where you reuse your development system for test but still get a documented transport. See more about our transport process
- Versions and differences between your iFlows and other artifacts
- Monitoring and alerting, with rules that notify you about specific conditions
- Replication of all your iFlows and artifacts to a Git repository, which makes your Groovy code much easier to maintain and develop
- PI to CPI migration with the Figaf Migration Tool
It is one tool that covers all the requirements you have for the full DevOps process, as part of the Figaf DevOps Suite. See our prices.
Figaf inside CPIHelper
With the Figaf plugin for CPIHelper you can jump from SAP Cloud Integration straight to the right place in Figaf:
- Select a specific recording as a test case
- See the versions of an object and its recent changes
- Start a synchronization with Figaf
- Open a Groovy script from an iFlow or a script collection in the Figaf editor
Watch on YouTube Figaf and CPIHelper plugin to automate your SAP Cloud Integration
Already using Figaf?
Once you have configured your first connection, configure CPIHelper to work even faster with Figaf. See how to set it up.
From the blog: Figaf with CPIHelper
Figaf and SAP Solution Manager Change Management System
How Figaf fits under your existing release process - without changing it
I didn’t think you could convert a compiled Java mapping
How a decompiled SAP PI Java mapping became a Groovy script in twenty minutes, and how to prove the result matches the original byte for byte.