Skip to Content
Technical Articles
Author's profile photo Sookriti Mishra

SAP Cloud Platform Integration (CPI) || Part 11 || How to use a Local Integration Process

Dear Reader,

This blog post is a part of a series of blog posts related to SAP Cloud Platform Integration. The blogs so far are:

  • My adventure in learning CPI || Part 1 || All about SAP Cloud
  • My adventure in learning CPI || Part 2 || Deployment Models
  • My adventure in learning CPI || Part 3 || Cloud Security
  • SAP Cloud Platform Integration (CPI) || Part 4 || Know your tool
  • SAP Cloud Platform Integration (CPI) || Part 5 || Content Modifier
  • SAP Cloud Platform Integration (CPI) || Part 6 || Configuring Mail Adapter
  • SAP Cloud Platform Integration (CPI) || Part 7 || Maintaining logs by using “Groovy Scripts”, even if the IFlow is not on trace mode
  • SAP Cloud Platform Integration (CPI) || Part 8 || Working with Request Reply
  • SAP Cloud Platform Integration (CPI) || Part 9 || SAP Cloud Platform Cockpit || All about Account, Tenant, and User ID
  • SAP Cloud Platform Integration (CPI) || Part 10 || How to use “Send”?

Other blogs:

— o — — o — — o — — o —

LOCAL INTEGRATION PROCESS: A Local Integration Process is like a subprocess-call within an IFlow. The scenario which I have used to explained is an absolutely fictitious scenario. For small scenarios we may avoid and unnecessary Local Integration Process call. Before continuing to the routing step, this sub-process may be added to the integration model.

We shall need:

a) Local Integration Process, where the subprocess-steps shall be formulated.

b) Process Call, a step in the Integration Process (i.e. the main IFlow),  to call the Local Integration Process.

 

The below is the Integration Flow which has been created to demonstrate how to use Local Integration Process. The IFlow has been divided into 3 parts.

1. Process Call: As mentioned above, a Process Call is to be used to call the Local Integration Process.

2. Local Integration Process: This is where the subprocess steps are setup.

2.1 Request Reply: To know how request reply works, click here.

3. Mail: To know how request reply works, click here

 

OUTPUT:

Hope you had a good read.

If you wish to know more, or have any queries on this blog, then please feel free to drop a comment.

 

Thanks & Regards,

Sookriti Mishra

Assigned Tags

      4 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Jiaqi Jing
      Jiaqi Jing

      These articles are really good,they are very detailed and useful. Thank you for your dedication

       

      Author's profile photo Christopher Linke
      Christopher Linke

      Is there a way to "convert" a local process to an own iFlow (DirecProcess)? I guess there is no copy&paste functionality?

      Author's profile photo Michalis Mastorantonakis
      Michalis Mastorantonakis

      One quick workaround I used is to copy the whole artifact into a new one and then do the below modifications on the copy.

      1. Keep the flow steps “Sender->ProcessDirect (define address for Connection tab)-> Start message -> Local Process -> End message”
      2. Delete non-used resources.
      3. Save and Deploy

      You can now use your new iFlow with a connection like “RequestReply-> ProcessDirect (use above defined address) -> Receiver” in any other flow.

      Hope works for your case.

      Michalis

      Author's profile photo Gregory Igbanoi
      Gregory Igbanoi

      Welldone Sookriti Welldone

      Best Regards

      Gregory