Many customers only use two SAP Cloud Integration/CPI tenants for their landscape. They do this to save money on the subscription but can easily end up with Wild West.
They have normally copy and rename iFlows to add a prefix like QA to the name of the IFlow that is being tested.
One person called this Wild West because you can just make small modifications in the IFlows and have no governance process in place. Then you can forget to externalize parameters and just modify channels directly. Then at some point, you move one of the versions to production via file transport. Next time you move, you forget which changes you made.
The process works but is flawed and not something a customer running SAP should be doing because of the missing governance and high risk of failure.
So customers have to choose between governance or saving a tenant.
With Figaf, you can have both.
- Governance
- Save one or more tenants
We have our Virtual tenants (earlier called Virtual agents) where we can handle transport just like if it was between systems. You will have:
- Configuration
- Approval processes
- Deployment points
- Renaming objects for the integration
You can block people from making changes in the renamed object using Access policies; that way, you know your governance is followed.
The business case is pretty clear.
Save one tenant is 4.000 EUR/month (depending on the version)
Figaf starts at 1000 EUR/month + 200 EUR for hosting.
The Figaf not just saves money on the tenant but also provides a lot of other capabilities that you will need to manage an integration:
- Regression testing
- Documentation
- Monitoring
- Git repository with all your development artifacts
You can see a video of our transport process here. Here you see an IFlow moved to the virtual QA system.
You can tryout our transport. We have a guide showing you how you create your first transport. It can create transport in just 10 minutes to a QA system.
What about just one tenant for the full landscape?
It is possible to run both Development, QA, and Production on the same tenant with Figaf. It is not a recommended approach, but some of our customers are using Cloud Integration that way.