Sharing SAP CPI resources

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

  1. From an iFlow Resource, you select create a resource
  2. Enter a name for the resource. Shared_ will be added as a prefix to make it easier to see what is shared
  3. IRT will then add the new resource to your Iflow
    1. Make manual changes to start using it
  4. On other iFlows you can add the shared resource
  5. If a user changes a resource in an iflow the shared resource will have a new version
  6. Use can then apply the shared version to iFlows where it is used
  7. 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.

Links to your SAP Cloud Landscape

As a developer one of the things that I often struggle with is to understand what system I need to login to to develop. With PI your learn to remember that PIT is the test system. But with CPI you just have some seemingly random numbers and it can be difficult to remember. I have received my fair share of emails with links in that I often go search for. I need to create a long series of bookmarks. And all new developers need to do that. Now we have made it easier for you to access the different pages.

I also normally added new tab names for each system so I can remember which system I’m currently have open in my tab.

With the new release of Figaf IRT 2.8 we are adding a function to allow you to configure your full landscape so you from the Figaf home page can go to all the relevant systems. Since we support transport and monitoring in your landscape you will anyway need to configure all your systems in Figaf IRT. You can also register all instances to a landscape so you will get links to all the entries in your environment.

The new homepace of Figaf IRT now look like this.

New Figaf IRT homepage with links to all your SAP Integration tenants or systems.

From each landscape you can then go to the relavant tennant and links. You can have multiply landscapes of each.

  • For API management it is both the developer portal and the API portal.
  • For PI it is /dir, Netweaver Administrator, PI monitor and B2B Add-on homepage
  • For CPI it is design, monitoring and IRT monitoring page.

If you have ideas to more then let me know.

We may add links to SAP sites like status pages or Cloud Platfrom links.

This feature will be rolled out to Figaf IRT Cloud and Figaf IRT around 14 May. You can get free access on either link. We also have some other cool features making your development process a lot easier.