Update 2022-05-18: SAP CPI do have a way to handle sharing of scripts in the script collections and Message Mapping objects. In the our May release Figaf Tool will also be able to handle governance and transport of the Script Collection and Mapping Mappings. So you will be able to see which script collections is used in which iflow.
A common use case when using SAP CPI is that you want to share scripts with multiply CPI iflows. Currently, now you have to manage this your self by copy or upload scripts in all the places it is used. It makes it pretty difficult to have a good shared repository of resources.
With shared resources, you will get a repository of all the different scripts that you have and can easily check the status of them. If the resource version, you can update all iFlows where that resource is used. If you make a modification of an object it should be possible to test to validate that nothing has happened with your processing.
You can watch a presentation of the flow here.
The flow is as the following
- From an iFlow Resource, you select create a resource
- Enter a name for the resource. Shared_ will be added as a prefix to make it easier to see what is shared
- IRT will then add the new resource to your Iflow
- Make manual changes to start using it
- On other iFlows you can add the shared resource
- If a user changes a resource in an iflow the shared resource will have a new version
- Use can then apply the shared version to iFlows where it is used
- Test that the modification does not affect processing
There is some challenge with the current setup. You cannot share message mappings primarily because they rely on the source and target schema and possible groovy scripts, that they also need to be shared. We can probably find some way to get around it. If it becomes a requirement, we can find a solution that allows you to share message mappings also.
A standard solution from SAP
It is a common request and it may be possible that SAP will implement something similar to a standard part of the development. One thing that is required for this to work is the ability to test that the change does not affect other iFlows. It should be possible to adopt our solution, so it will enable version and support testing of the shared resources.
Want to try it out
The feature will be released in the next version of Figaf IRT probably in the week of 17 June. But you can already now signup and try all the other great functions we have to make your SAP CPI life easier.