Technical Articles
Features of Cloud Integration Automation Service – Generating a workflow
This is part one of a series that covers features of the Cloud Integration Automation Service.
Some features of CIAS are very helpful but not well known, so I would like to bring those to your attention. It should also help to improve the usage of CIAS as some fields need a bit of explanation.
In this first part of the series I want to focus on the Generation of a workflow for a scenario integration. After subscribing to CIAS (see blog), this is obviously the first step when working with CIAS.
First step: Select a scenario
In the CIAS launchpad, which opens after you clicked on your CIAS subscription in your BTP account (hint: Add this link to your favorites), you can start with Plan for Integration:
You can always come back to this screen by clicking the Overview Button on the left. The Menu on the left opens after you pressed the 3 little lines on the left. Without that you would only see the symbols.
After clicking Plan for Integration, you get the list of available scenarios. As there are so many scenarios, they are grouped under e.g. “Intelligent Enterprise Solutions” or “SAP S/4HANA Cloud Integration”.
To see all scenarios you can click on “Expand All” and select “Cloud” or “Hybrid”.
Important hint also, pressing “click here” will bring you to SAP Note 2608492 which mentions all he pre-requisites in order to use in Cloud Integration Automation Service.
Once you selected a scenario, you will see more details to this specific scenario.
More details on the scenario, Description:
Which systems will be connected, Entities:
And you get an overview which tasks will be used during the execution of the workflow, Scenario Tasks:
Now you can continue to generate the workflow and the nest task is to select the right systems for the configuration. Press “Select Systems”
Second step: Enter the systems
On the next screen you will see in the upper part which systems are needed to configure the scenario. In the case of scenario “Configuring ABAP Env to use the Custom Code Migration App”, there are three systems needed:
- SAP Business Suite System
- Cloud Connector
- SAP Business Technology Platform
The first system is highlighted in light blue: SAP Business Suite System. Therefor you see in the lower part all systems that are assigned to the user who generates this workflow.
In my case here, the list of available systems is very long, as these are all SAP internal systems assigned to my user. In a customer environment you will far less systems as there should be less systems available. In any case you can also search for a system in the search field.
If you do not see the needed systems, there is a problem with the setup of the user/system environment. I will create a seperate blog to demonstrate how this setup has to be and where it can be changed.
So from here I select the SAP Business Suite System, then Cloud Connector, then the SAP Business Technology Platform.
You will then see a pop-up that says:
System Details Not Filled – Cloud systems for the following system(s) have not been filled. Do you wish to proceed?
If you press “Proceed”, the workflow can be generated without any system information.
You will then have to enter the systems in the second task of the workflow itself which is called: “Confirm System Components”.
So, the final screen in the preparation and to confirm the generation of the workflow looks like this:
Once the workflow has been generated, you can continue in your CIAS workflow inbox:
In the next blog I will give some details on the features of the workflow inbox and how you can work on the tasks of the workflow.
This could also be interesting for you:
Are you a developer or integration designer who already know his way around SAP BTP? Then find out how to build integrations from and to cloud applications SAP’s free learning content on SAP Integration Suite. Check out even more role-based learning resources and opportunities to get certified in one place on SAP Learning site.
Best Regards Stefan Jakobi Product Management @ CLM