Technical Articles
Start a scenario integration workflow with Cloud Integration Automation Service on Cloud Foundry (BTP)
Until recently, the integration of Cloud to Cloud scenarios or hybrid scenarios was based on integration guides, help pages, blog posts or other written documentation.
Now, Cloud Integration Automation Service (CIAS) provides partially automated, role based workflows, including system landscape information and integrated parameter management.
The first step to make use of this service is to subscribe via the service marketplace on your Business Technology Platform sub account. You can find more details on how to subscribe to the Cloud Integration Automation Service in this blog.
Once you know which scenario you want to integrate, you can start to create the workflow.
1. Select the Scenario
In the overview of the CIAS Launchpad you will see the list of available scenarios. If you choose one scenario, you get more details (e.g. configuration of the Custom Code Migration App):
2. Select the Systems for the Scenario
If you continue with “Select Systems”, you will get a list of systems that are necessary for the configuration of this scenario:
In the case of the configuration of the Custom Code Migration App you need to specify an SAP Business Suite System and a Cloud Connector System.
The list are all systems that are assigned to the user who started the workflow. The systems need to be assigned to the user in the BTP account.
After you have assigned the systems to the workflow, you can press “Generate Workflow”. If one or more systems are missing, you can still generate the workflow but you will get this warning:
3. Generate the workflow
Next step is to select the BTP account where the workflow will be generated:
Before the generation of the workflow starts, you get a summary of the details: which scenario, which systems and to which account the workflow goes:
Now you can generate the workflow and after a few seconds, you will get the success message and a link to the CIAS launchpad to open the workflow:
4. Do the first tasks of the workflow
The first few tasks of every workflow are the same:
- Disclaimer
- Confirm System Components
- Assign Users to required Roles
Disclaimer
Standard Disclaimer for the usage of the service. Read the text and press “I Agree”.
Confirm System Components
Here you may need add or change some System specific information, e.g. access URLs.
Once all mandatory fields are filled, you can continue and press “Confirm Systems”.
Assign Users to required Roles
Here you need to enter the users that are supposed to do the tasks in the respective system. E.g. the administrator of the Business Suite system might be the right person to do the tasks inside the Business Suite system. Press “Confirm Role Assignment”.
Now let’s take a look at the monitoring view:
In the monitoring view you can see all workflows that have been generated in this account. If you have the right privileges you can modify the workflow or terminate it.
You can also check the progress of the workflow. In the above example you see that the first 3 tasks were completed. The 4th task “Confirm execution scope for the scenario” is next. It will show up in the inbox of the person to which this task was assigned.
In my next blog I will show you some additional features of the Cloud Integration Automation Service.
Best Regards Stefan Jakobi Product Management CLM
Hi Stefan,
Great blog,
We are trying to setup the scanning app for the first time ... and we are encountering the following issue after a long waiting time:
I suspect this might have something to do with the 'business systems'.
You mention
The list are all systems that are assigned to the user who started the workflow. The systems need to be assigned to the user in the BTP account.
Where is that exactly ? I cannot find any documentation on this ... nor is it listed in the prerequisites.
Thanks,
Steven
Hello Steven,
thank you for the feedback!
As for the error, please try to refresh the screen or use an incognito window.
The systems assigned to the user who started the generation of the workflow should then show up. If this is not the case please open a ticket as mentioned in the pop-up.
Also let me know so I can trigger the solution asap.
Best Regards
Thanks Stefan Jakobi for your fast response.
I will retry but - I am sorry to come back to it again - I am still not sure how 'the systems assigned to the user' is supposed to work ? Is this a configuration step somewhere? Or are these authorizations related to the S user ?
BTW .. We also tried to start this journey via the maintenance planner - there the reverse issue is actually happening - I see all the ERP backends we have in our landscape but I cannot get our BTP subaccount to be found ... sigh.
Thanks,
Steven
Hello Steven,
thanks for your response.
It depends to which customer number the systems are assigned and which Super-User belongs to this customer number.
The customer number is attached to the Super-User (S-user) who then creates additional S-users.
Here are 2 blogs (+ additional links) that describe how this works:
https://blogs.sap.com/2021/06/10/how-to-generate-a-new-s-user-id/
https://blogs.sap.com/2018/12/24/fundamentals-of-s-user-id-for-new-successfactors-customers/
Please let me know if this helps and solves the problem.
Best Regards
Stefan Jakobi Product Manager @ CLM
Thanks Stefan Jakobi for your insights.
We ended up doing the installation manually as we could not get the advisor to work properly. Apparently we have 2 customer accounts - one holding on premise and the other our cloud - as such it probably causes the issues. SAP has an outstanding action apparently to 'combine' these accounts.
Kr,
Steven
Hi Steven,
thanks for getting back.
Yes, the reason why this didn't work is probably the different accounts and S-Users.
However, I should have mentioned that you could also have used the workflow without entering the systems during the creation of the workflow. The systems can later be added manually in one of the first tasks of the workflow itself called "Confirm System Components".
I hope the usage of the Customer Code Migration App works as expected.
Best Regards
Hi Stefan,
Ah that's unfortunate ! Due to the dramatic error popup I didn't realize one could actually continue selecting the other boxes and/or use the upper 'Generate Workflow' button.
We have used the customer code migration app a couple of times now but do have a couple of concerns/questions. See https://blogs.sap.com/2019/09/23/abap-custom-code-analysis-using-sap-cloud-platform/comment-page-1/#comment-624985
Thanks,
Steven
Hi Steven,
the expert for the functionality of the Custom Code Migration App is Olga and as I can see, she did already answer your question.