Skip to Content

Introduction

In my previous blog, I shared about the new “Resources” view added in SAP Cloud Platform Integration’s Web Application, where I talked about the actions like download and delete of resources of the integration flow.

As the next increment to the “Resources” view, we have now added the possibility to add resources to the integration flow. This would allow the integration developers to include resources directly from the file system or copy resources from other integration flows across packages within the same tenant.

Once a resource is available within your integration flow, you can consume it in a flow-step or an adapter from their respective configuration (or property sheet).

 

“Add” Resources 

In the “Resources” view, you can click on the “Add” button to select the type of resource you want to include into the Integration Flow. Currently adding of these types of resources are supported;

  • Archive
  • EDMX
  • Script
  • WSDL
  • XSD
  • XSLT Mapping

 

Image 1: “Add” button and types 

 

This would open up a dialog which gives you an option to choose the source from where you want to pick up the resource, it can be either “File System” or “Integration Flow”.

 

Image 2: Add dialog with “Source” as File System or Integration Flow

 

“Add” Resources from File System

If you choose the “File System” as the source, then you can click on the “Browse” to select the respective type of resource you want to add into your integration flow.

 

Image 3: Select resources from File System

 

You can also add multiple resources of the same type from the file system by selecting them all and adding them together.

 

Image 4: Multiple resource selection 

 

“Add” resources from file system is now extended to accept zip files to allow adding of dependent  or related resources of different types for a particular resource.

For example, if you have a WSDL which requires an XSD as a dependent resource and has to be in the same path as the WSDL. In this case, you can create a zip file which contains the WSDL & its dependent resources and add it using the Add -> Schemas -> WSDL option.

 

 

Image 5: Adding multiple related resources as an archive

 

On add, the zip is unzipped and the content of the archive placed in the current selected path within the integration flow.

You can also add the dependent resources with a folder structure by adding this within the zip file, and on upload, the same folder structure (or path) is retained within the integration flow.

 

“Add” Resources from other Integration Flows

If you choose the “Integration Flow” as the source, you need to first select the package and then find the integration flow from where you want to copy the resources.

 

Image 6: Select resources from Integration Flows

 

The package and integration flow selection drop down also supports filtering which can be used to search for a particular package or integration flow. Just start typing the package or integration flow name and the list will be filtered accordingly. This filter comes in handy in case you have too many packages or integration flows in your tenant.

 

Image 7: Filtering packages and integration flows

 

You can also add multiple resources of the same type from an integration flow by selecting them all and adding them together.

 

Image 8: Multiple resource selection 

 

“Add” resources from integration flow is now extended to allow adding of dependent or related resources of different types for a particular resource.

For example, if you have a WSDL which requires an XSD as a dependent resource and has to be in the same path as the WSDL. In this case, you can click on “Include Additional Resources” and select required XSD available in the same path and add in into your target integration flow.

 

Image 9: Adding multiple related resources

 

Overwrite Resources

While adding resources either from file system or from an integration flow, if the your integration flow already contains resource of the same type and same name, then there is a confirmation dialog shown which lists all the conflicts and gives you an option to either overwrite them or cancel the add operation.

 

Image 10: Overwrite existing resource with the same name 

 

Conclusion

Every resource that is added in the integration flow via the “Resources” view is a copy of resource and not a reference of a resource, which means that any changes made to the resource within your integration flow doesn’t impact the resource with the same name in other integration flows.

You can also add message mapping into your integration flow via the “Resources” View using the Import from ESR feature.

Hope this blog was useful and helps you consume the “Add” of resources in the Web.

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

    1. Finny Babu Post author

      Hi Morten

      Thanks for your feedback.

      Renaming resources is already part of our road map for “Resources” view. Sorry that we could not give it to you for this Christmas but for sure it will make it before next Christmas :-).

      (1) 
  1. Former Member

    This is really great , is there some way to also find in resources view where are these resources used ? e.g. old scripts generated but script steps deleted later ; so to cleanup these old scripts ?

    Is it possible to reuse resources across flows rather than copying them in duplicate scenarios ?

    (0) 
    1. Finny Babu Post author

      Thanks Sachit for your feedback.

      Showing the usage of resources within an integration flow is part of the road map and would come in the future.

      Using resources across iflows is also something we have it in our minds but not yet started detailing it out.

      (0) 

Leave a Reply