Hi, my name is Denys van Kempen, SAP HANA Academy.
You are watching a video tutorial that is part of a series about the SAP Business Technology
Platform, SAP Integration Suite certification, covering Cloud Integration
This video was recorded in March 2022.
For the latest tutorials on the topic, please check the playlist.
In this video we cover creating integration flows, iFlows in short.
Before we can create an iFlow, we first need to create a package.
Each package has a header with a name, technical name, short description, and optional version
number and vendor, if applicable.
On the overview tab, you can provide additional information.
before we can add artifacts or documents, we first need to save the package
with tags, we can properly identify the package,
select the product
country/region
line of business,
industry
On the Documents tab, you can add files, (PDFs) or a link to a webpage
Different type of artifacts
you can add custom integration adapters, to connect to systems not natively supported
by SAP
connectivity to the most common environments is included, all we need to do is select them
from a list
but for more exotic cases, we can develop custom adapters,
there is a A-D-K for this, Adapter Development Kit,
and the framework used is Apache Camel, open source, but this all beyond scope of the exam.
you upload a file and then deploy
same for message and value mappings,
OData, REST, and SOAP APIs,
and script collections
As we have seen, some packages can contain a large number of integration flows,
and instead of copy/paste the same script file,
create a single script collection, which you can version
and references in the flow.
You are not expected to be familiar with all these artifacts,
for the exam, you only need to focus on the integration flow
create or upload,
you can export packages and flows as file, as backup, as template, and then use this
as a starting point
add name and identifier
and optionally a sender and receiver, the source or target system
select the flow
the most basic format
we have a sender
a receiver
only the name is configurable
a start message
and end message
again, nothing to configure
both are connected
there is an alert: start event should have an incoming message flow
when you select the canvas, you can configure the integration flow, the runtime
and this includes a tab with problems, listing all the alerts
to fix this, select the Sender object
from the context menu, select the arrow (or select the arrow from the header menu)
and drag to the start message
we are now prompted to select the adapter type
so these are all the adapters provided with Cloud Integration
you can find these all documented in the Cloud Integration guide
the process direct adapter, for example, allows you to connect flows which are part of the
same package
requires an address, package name, iflow name
The tabs and fields will be different for each adapter.
To remove the connection, select it and click the bin in the context menu or in the header
same to add objects,
a mapping, for example
different types: ID, message, operation, and XSLT
drag it on the canvas
and configure
in case of a message mapping, we would first need to add this to the package
and then here make the reference
and this is all extensively documented
the same applies to the transformations
content modifiers, converters, decoders/encoders, extractors, scripts, and filters
each with its own properties
as documented
recommended reading is the integration flow design guidelines
which includes some sample material
and then there are also
a couple of tutorials
on the SAP Developer Center
that will help you
to get familiar with
configuring iFlows.
That’s it for Cloud Integration
creating iFlows
make sure you are very familiar with the menu here, as you will get quite a few questions
about it.
That’s it for
You can find the links to the resources mentioned in the description of this video below.
This video tutorial was recorded by Denys van Kempen, SAP HANA Academy.
Any good?
Give us a like, and for updates, don’t forget to subscribe.
Thanks for watching.