In this post, we will build and deploy your first iFlow with the help of range capabilities. This will guide you through the process of creating your initial integration flow and setting it up for deployment.
Outline of this blog series:
- SAP CPI Introduction
- SAP BTP tools and features overview (BTP, Global Account, Sub-Account, Entitlements, Connectivity, Security)
- SAP CPI Web IDE overview
- Registering a trial account and enrolling to SAP CPI service
- Deep dive into Cloud Integration features with real world scenario example
- Use cases of palette functions
- Adapter configurations
- Using Cloud connector for connecting to backend SAP systems
- Overview on API Management & Open Connectors
- Integration using Open Connectors with real world example
In short, below is the content we will elaborate in this tutorial:
- Build your first IFlow
- Tour on the Artifact Editor
Build your first IFlow
To start making IFlow, first make bundle and make a relic as depicted in past post.
After tapping on the IFlow made, you will actually want to see some range previously made for you by SAP. There will be one source, one recipient and one fundamental combination process segment.
Prior to moving into the IFlow creation, we will have visit on the things accessible in the ancient rarity manager.
2. Tour on the Artifact Editor
At the upper left corner of the manager, we will actually want to see the way of the IFlow made. Under Plan tab – > P_SelfLearning_IFlows – > IF_HelloWorld. Also, the IFlow name displayed in strong letters underneath.
The most compelling thing to take care of is the Arrangement status of the IFlow, which is close to the IFlow name. Prior to testing the IFlow you need to save and convey the IFlow (as we do in the PO, save and actuate). The sending length regularly takes 5-10secs and some of the time it could take >1min in light of the IFlow size. After the status showing conveyed just, we need to test it, generally new changes will not be considered while testing.
At the upper right corner, normally you would have just initial 4 connections/buttons (Alter, Arrange, Send, Erase). The other 5 connections/buttons will be accessible solely after you introduce a chrome expansion. I will direct you on the utilization instance of having it, trust me it is the most valuable element while attempting to troubleshoot the IFlow. We will zero in on those in later posts.
The initial four connections:
Alter – For empowering the alter mode
Design – This choice you regularly utilize solely after finishing the IFlow advancement. This cycle is called Designing the Externalized Boundaries. For e.g.: In DEV climate, the sftp server will be unique and in QA the server will be unique. Thus, we need to go inside the IFlow and alter the SFTP server subtleties. To stay away from altering the IFlow, in the event that we externalize (this idea will cover in later posts) those fields, with Design choice, we can see every one of the externalized boundaries in a single window and change it.
Send – For enacting the IFlow
Erase – For erasing the IFlow (Note: When IFlow/Bundle is erased, it can’t be recuperated).
On the off chance that you click on Alter, you would get additional two buttons:
Save – For saving the progressions
Save as variant – For saving the progressions as a different rendition, so designer can return to past form.
Next going to the palette toolbar.
This toolbar is the range toolbar. It has all the essential SAP gave standard instruments to fostering an IFlow.
For e.g.: Message planning, XML to JSON converter, PGP encryptor, Switch, etc.
Each button in the range has numerous devices inside it. We wouldn’t go individually making sense of the utilization instance of the range instrument as it would require part greater investment. We will utilize all the range apparatuses in our IFlow advancement with the goal that you would comprehend it much better. Next is the Dish ZOOM apparatuses accessible in the right side.
The circle with four bolts indicates the Dish device. It will be utilized for showing the whole IFlow inside the screen. If the IFlow is huge and you need to look the entire IFlow in that screen, then you can tap on the little circle in the center to fit the IFlow inside the screen.
- also – signifies the Zoom IN and Zoom OUT.
Next is the properties area, which will be in the lower part of the screen.
This part is where you would give the qualities/config of the range utilized. Click on the extend symbol at right or drag the properties segment or the most effective way is, double tap on the unfilled region in supervisor which would consequently open the properties area like beneath.
At this point, we don’t need to go through every tab. We will concentrate on the utilization situation when we for all intents and purposes work on the connection point advancement.
————-
Presently we will eliminate the default starter range instruments gave and will add physically from Range toolbar.
To begin with, we will add Combination Cycle. This is where we will add all rationales/planning capabilities.
In the Toolbar, Cycle symbol and select Coordination Cycle.
Comparable way in the members choice, select source, collector and spot it in the supervisor.
We will add a beginning message and end message occasion in the Mix Cycle which is compulsorily to be added. It will be accessible close to the Interaction symbol.
Click on Occasion symbol and select Beginning and End Message.
Presently click on Source process and select the bolt and drag it to the Beginning Message to interface. After delivering, you would be provoked in the screen to choose connectors recorded. For the present, click on HTTPS.
Source connector is associated with the Mix Cycle. In this IFlow we will not be utilizing recipient connector.
Presently double tap on the HTTPS word underneath the bolt imprint to open the properties area.
In the Association tab, you can see the location property. In the Location field, fill in any worth connected with IFlow which will be attached in the endpoint. With this URL just, we will test in the Mailman apparatus.
The endpoint gave -/hi/world. This will be annexed toward the finish of the URL.
We will have another in the middle of between the beginning and end message to pass consistent payload.
Click on Change – > Content Modifier choice in the range toolbar.
Presently interface the begin to content modifier and content modifier to end message. Your IFlow ought to look like underneath.
Presently we will add steady payload in the substance modifier.
Prior to continuing with that, we will become familiar with the utilization instance of content modifier.
A substance modifier will assist you with adjusting the approaching message or payload, by changing substance are engaged with Message Handling (i.e., Message Header, Message Trade Property, or Message Body).
Say, the collector framework is requiring a header property to be sent with the solicitation payload, yet the source framework isn’t sending such. Then, at that point, all things considered, we can make reference to the header name in the substance modifier, which will be shipped off the collector.
Comparative way properties and payloads can be added (properties are for inside IFlow use, it won’t be shipped off recipient framework).
In this model, we will add a payload and one header.
Double tap on the substance modifier to open the properties segment. We will set content sort to application/xml and add a steady XML payload under the Body segment.
Header:
Body:
In body, we will show the approaching payload and furthermore we will another steady payload toward the end. To pass the approaching payload to yield, we need to utilize camel structure, ${in.body}.
SAVE and DEPLOY.
Presently we really want to get the HTTPS endpoint for testing it in mailman.
Under the observing segment – > Snap on the Oversee Reconciliation Content.
After tapping the IFlow name, in the right sheet, you will be given HTTP endpoint URL.
Duplicate this URL and take a stab at testing it in Mailman with any example XML payload. For approval, get the accreditations from the BTP. This I have made sense of in the underlying posts on producing the help restricting key. From that point, we can get the client ID and client mysterious.
XML payload got added and with that consistent line which we passed in the substance modifier.
To really take a look at the checking of that sent message, go to observing screen – > Screen Message Handling.
One more significant data to be noted is the LOGS segment, where the log level is set as Data. This is known as the Message Handling Logs (MPL). MPL is a significant wellspring of data for observing and investigating, various arrangements are based on top of this usefulness to work with extra data and message content logging. This log level empowers logging of essential data about message handling steps, and more nitty gritty data about last handling ventures for bombed messages.
INFO
DEBUG
TRACE
We can change the log level in Oversee Reconciliation content screen. As a matter of course, Data will be chosen. For investigating the IFlow, we use Follow log level. Troubleshoot isn’t utilized generally.
In the event that you set it to Follow, you will get a data brief saying,
“Log level ‘Follow’ terminates at Dec 18, 2022, 09:17:59. After expiry the log level changes back to ‘Information’.” And that implies Follow lapses in 10mins and changes itself to Data log level, however the follow information is taken out after 1hour.
Presently, we should set off the message from mailman once more and see the follow logs.
Click on the Follow, which opens the message stream window. For each step it shows the comparing payload, headers and properties.
There is a superior method for following the logs, which I will make sense of in the later post.
I trust you figured out the complete process to build and deploy your first iFlow and the methods for monitoring and testing it.
YOU MAY LIKE THIS
Introduction to SAP ABAP for HANA
Bridging the Gap: Integrating ABAP with Other Cloud Services
WhatsApp us