Skip to Content

SAP Cloud Platform Integration- Creating Reusable Templates


Being a Integration Developer, its very common as we lookout for shortcuts while creating artifacts:).If lot of custom integrations are involved in SAP CPI obviously, we will look out for easier way to configure the steps or reuse some of the configuration parameters from other integration projects.

Below blog will help you to explore those shortcuts in Eclipse Tooling using “Save As Template”

Lets go through the process in detail.

Case 1: Reuse of steps with as is configuration .

Lets take an example of content modifier with below configuration.

Step 1:

Right click and select ‘Save As Template

Step 2:

Template will be stored in Eclipse Work-space Folder in .fst format

Step 3:

Right click on any Content Modifier and load the previously saved template to have all the configured header,property and body ( visibility not restricted to integration project but restricted to Eclipse Workspace)

Above functionality works for Content Encryptor,Message Signer,Content Modifier,Converter,Sender Channel and Receiver Channel steps

Case 2: Creation of integration template with predefined configured steps.

Step 1:

Create a Integration flow which needs to be saved as template.In the below case I have created integration project with basic steps including Error Handling  ( refer my blog on Exception Sub process ) which I want to use as template for my rest of interfaces.

Step 2:

Now click on File and follow below steps

Step 3:

Give logical name to template and select Retain the externalized parameter(s) if you want to retain the external parameter of above IFlow to template.

Step 4:

Now navigate to Eclipse folder from where you have opened the eclipse and template file will be created there.

Step 5:

Lets see how we can use the above saved template while creating new integration projects.

Create a new integration project with valid integration project name and click on Next

click on User Defined Templates and you will be able to locate the template which we created in earlier step.Click on Finish


You will be able to see all the above predefined steps of template auto populated in new IFlow.


  1. Its easier and quicker to configure the new IFlow with predefined set of fully configured steps.
  2. Reduces manual effort of configuration ( more likely with SF/mail Adapter configuration).


  1. Save As Template option with Integration Project Steps is limited to Workspace and user scope.
  2. It works only with Eclipse Tooling.


Very useful option which eases out effort of Developer for quicker development with considerably less efforts.


Sriprasad Shivaram Bhat


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