Splitter will split record by record

 General Splitter
 Iterator splitter
 EDI splitter
1. Parallel Multicast he message is sent to multiple receivers in parallel (concurrently), and each
receiver can process the message independently and in parallel.

when the receivers do not depend on each other,i f an error occurs in any branch, it can affect that
specific receiver, but the other branches continue to execute.

Sequential : The message is routed through each receiver sequentially, meaning one branch finishes
before the next one starts.

when there is a dependency or order of processing between the receivers, or when the execution
needs to happen in a specific order.

 If an error occurs in one branch, it can prevent the other branches from being processed, as the
processing is sequential.

use parallel multicast for independent operations that can run simultaneously, and sequential
multicast when order or dependencies between the receivers are important.

2. Paralle Multicast :Inorder to create Multiple branches you need to drag end message .. how
may branches you need th
3. at many end messages you need to have.

Parallel Multicast with multiple Recievers

Parallel Multicast with single receiver

You can make use of Hashmaps to share data between branches

-------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------

In a multicast pattern, the main branch of the integration flow is split into multiple child branches that
are processed either in parallel (parallel multicast) or in a defined order (sequential multicast).

There are the following constraints:

 Headers and properties set in the main branch before the multicast step are available in the
child branches.
 Headers and properties set in a child branch aren't available in other child branches.
 When the multicast branches are again merged in a Join and Gather step, properties that are set
in the child branches are available in the main branch. However, headers that are set in the child
branches aren't available in the main branch.

Assume that in a sequential multicast scenario there's the requirement that a value set in 1 branch is
available in a subsequent branch.

In this case, you have the option to use the local persistence (variable or data store) to share this data
across the different branches.
Manage Security

 Security Materials
 Manage Keystores
 PGP keys

Mail Adatpor :
Clike on Send
Download certificate

Zip file – in that we have root certificate ,Intermediate certificate , Peer Certificate

Adding certificates in CPI: add three certificates

Next step:
Setting up Gmail Account

1. Navigate to the settings of your Gmail account and locate the Security tab. Within this section, activate
the Two-Step verification feature. Once you have enabled it, an opportunity to configure application
passwords will be presented to you. Proceed by selecting "App Passwords" as illustrated below.

2. In the App Password, select Other(Custom name).

3. Provide any name and click on Generate.

4. You will get a code in yellow box, copy that code and click on Done.
‍

Configure Mail Adapter in SAP CPI Monitor

1. Open the Connectivity Test in Monitor section of SAP Cloud Integration.

2. Navigate to SMTP and provide the initial details as shown below. You will get the successful test result, Now
download the certificate from Server Certificate Chain.

3. Open the Keystore in Manage Security and Add certificate there, By clicking on Add > Certificate.
4. Provide the Alias and Browse the certificate which we recently downloaded. Click on Add.

5. When you have downloaded the Certificate from the Connectivity test, you would have got the zip folder with
three certificates. Add other two certificates in the same way you have added the above one. you can
change the alias name for each certificate.
6. Navigate to Security Material and Create the User Credentials.‍
7. Provide the details as shown below. Provide the Gmail username in User and in the Password, provide the
14 letter code which we get from the "App Password". CLick on Deploy.
Using Mail Adapter in Integration Flow

1. Open your Integration flow in the edit mode.

2. Delete the Start and replace it with Timer.
3. Our motive is to send some data through mail. We will use the Content Modifier and type our message in the
Message Body.

4. Connect the Mail Adapter with End and the Receiver. In the Connection tab, provide the following details.
5. In the Processing tab, provide the following details. Provide the To, From and Subject here.

6. Save and Deploy the Integration flow.

7. You can see the your message has been sent successfully to the receiver as shown below.
Exception Sub Process:

If any error occurs in developed i-flow this Exception Sub-Process will generate an email and will send it to the required
stakeholders which we will configure in MAIL adapter. So, that Support/Monitoring team will get an alert mail then they will look into
the issue and will rectify that error.

Let’s consider that you have the below i-Flow named Exception_SubProcess. In that we should create an Exception Sub process.
So, that if any exception/error occurs in that flow it will send an alert mail to Support team.
Below is the Exception Sub Process. To create this in i-Flow go to Pallets ->> Process ->> Exception Sub Process. It will look like
below.

Then, Delete End Pallet and add Error End Pallet in place of that. Because End pallet will end the message whereas Error End
Pallet sends continuous alert mail to support team.
After this go to Pallets ->> Transformation ->> Content Modifier and add it to the Exception Sub Process.

In this Content Modifier we need to declare variables in the message header or exchange property and body which we will get in
alert mail.

I'm declaring in Exchange Property as shown below

Then we need to write the below message in Message Body as shown below

Hello Team,

Message has been failed with below error:

Error detail: ${exception.message}

Correlation ID: ${header.SAP_MplCorrelationId}

Message ID: ${property.SAP_MessageProcessingLogID}

Iflow Name: ${camelId}

Date: ${date:now:dd-MM-yyyy HH:mm} / SAP CPI - Tenant Number: ${property.SystemName}

Thanks & Regards,

SAP CPI Team

After this again go to Pallets ->> Call ->> External Call ->> Send and add it to the flow. This Send request is used to configure a
service call to the receiver system.

Again go to Pallets ->> Participant ->> Receiver add this Receiver to the flow and connect this with Send request by using MAIL
adapter

Configure the Mail adapter as below

With this we have competed creating Exception Sub Process. After deploying this i-Flow if any error occurred it will send an alert
mail like below.

Note: I wontedly kept some error in this i-Flow to show the alert mail as below.

Key Components of the Exception Subprocess:

  Error handling: The Exception Subprocess records pertinent information about an error when one occurs.
This information may consist of error codes, descriptions, timestamps, and the integrated components that
were harmed.
 Retry Mechanism: Occasionally, exceptions may occur as a result of momentary problems. The
unsuccessful integration phase is automatically processed again after a predetermined amount of time
thanks to the retry mechanism provided by the exception subprocess.
 Alerts and notifications: It's important to keep stakeholders updated. IT teams can quickly respond to
problems thanks to the Exception Subprocess's ability to start alerts or notifications.

Utilizing the Exception Subprocess: A Step-by-Step Guide

This Exception Sub-Process will create an email and send it to the necessary stakeholders that we will configure in
the MAIL adapter if any mistake occurs in the developed i-flow. Therefore, the Support/Monitoring staff will receive an
alert email, and they will investigate the problem and correct the error.
Let's say you have the i-Flow below with the name Exception Subprocess. In this case, we ought to develop an
exception subprocess. So that the Support team will receive a notification email if any exceptions or errors occur in
that flow.

The Exception Sub Process is seen below. Go to Pallets ->> Process ->> Exception Sub Process in i-Flow to build
this. It'll appear as seen below.

Then remove End Pallet and replace it with Error End Pallet. Because Error End Pallet sends a continual alert mail to
the support staff, End Pallet will end the message. Add the Send attribute in the message flow to connect the receiver
with mail adapter as shown below.
Configure the Mail adapter and in the Processing tab of it you can specify you Message.

‍
With this, the creation of the Exception Sub Process is complete. If there was a mistake after this i-Flow was
deployed, an alert email similar to the one below would be sent.

Router : will send entire payload to the branch that satisfy the condition Remaining branches it will
ignore

Router Basics:

Say you have three branches and if branch one condition is satisfied then the entire payload is routed
to Branch1

If you don’t want entire payload to be routed then we need to use splitter before router
Data Store Write operation:

Externalization

DEV-QA- Prod

Dev- Unit testing

QA-Iflow test,SIT,UAT,E2E Actual testing

Users will provide sign off and its working as expected and its go live and ready to move to Production
Double flower bracket two times
Click on the https ://services.odata.org/

If you want to move the ilfow to different environment then we can download
Once you download you will get zip file

How to upload it in different environment :

Click on configure:

So you have see drop down under Reciever so for each you can change the parameters
You can click on save and then deploy

Difference between draft and version:

Click on save as version