Cloud Integration Automation services (CIAS) now available for all RISE with SAP customers

Introduction:

I had an opportunity to configure SAP Launchpad service by using Cloud Integration Automation service.

I would highly recommend the use of Cloud Integration Automation service in your RISE with SAP project. It saves time and cost and avoids the need to troubleshoot issues during the setup process.

Below is my configured SAP Launchpad service screen to access SAP S/4HANA in the private cloud environment with principal propagation. After SAP Launchpad service is configured, you can access to SAP S/4HANA apps and others from SAP Mobile Start.

SAP Launchpad service:

As you know, SAP Launchpad service on Business Technology Platform (BTP) is now a central access point of the RISE with SAP S/4HANA Cloud and others. SAP Launchpad service is bundled with RISE with SAP. With SAP Launchpad service, SAP Mobile Start is also available to access SAP S/4HANA and other applications from mobile devices.

Cloud Integration Automation service:

The below links are a great source of information on how to get started and get to know more about the Cloud Integration Automation service.

Cloud Integration Automation service – What is it?

Start a scenario integration workflow with Cloud Integration Automation service on Cloud Foundry (BTP)

New video: Easy to Use Cloud Integration Automation service

In my opinion, “Cloud Integration Automation service” is the next gen configuration guide with workflow-based configuration guide with configurations automated partially.

Once you have selected a plan, workflow creates configuration tasks in your inbox. The tasks are persona based and different users will be notified to complete their set of tasks.

Configuration Challenges:

In the past, we loved going through a configuration guide with screenshots. It was easy to understand and follow through the configuration steps. However, we still have several challenges with this approach.

1. It takes time to find a good configuration guide
2. System environment is not exactly same with my system environment.
   With cloud environment, there are many configuration points in several landscape like SAP S/4HANA, Cloud Connector, Identity Authentication service (IAS) and Business Technology Platform (BTP)
3. If you do not have any experience before, you are not sure if the input parameter values are correct. If we make a mistake, it takes long time to find the root cause. From my experience, simple typos in the configuration are the ones which are hard to spot.
4. If we do not have enough authorization to configure, we need to ask other colleague who has the right authorization.
5. I usually make a configuration log to record my activities in a work document with screenshots. This can be used to repeat the same changes in other environments. Documenting these activities take lot of time too.

How does Cloud Integration Automation service addresses above challenges?

1. Over 120 integration scenarios are available

SAP Launchpad service Integration with SAP S/4HANA  is just one of supported integration scenarios.You can view all the Supported Scenarios.

2. Landscape components are selected in the first place.

It is integrated with Maintenance Planner and your systems are listed for selection.

System Data Upload to the SAP Support Portal via Landscape Information services

3. All parameters are managed in the workflow. Parameters are generated based on the system selection and the input provided in the previous steps. Just confirm the values or copy and paste the value. There is no room to make any typos.

Example: Based on the system selection, BTP-IAS trust configuration step parameters are generated.

4. If there is different admin in each system, you can assign corresponding roles to them.
   
5. Configuration Monitoring is available.

You can check executed task and parameters. You do not need to log your activities in separate document.

My experience: SAP Launchpad service for SAP S/4HANA Private Cloud.

To automate the setup of the SAP Launchpad service with SAP S/4HANA Private Cloud, you can follow the blog post and SAP Help documentation.

Simplify Your Integration Experience of SAP Launchpad service with SAP S/4HANA

CIAS Guide: SAP Launchpad service Integration with SAP S/4HANA

The overall configuration took me about 4 hours as it was the first time, I was using Cloud Integration Automation service. Probably I would do it in 2-3 hours the next time.

Below are the high-level configuration blocks for this scenario:

Here are some of the things I loved about using Cloud Integration Automation service:

• Cloud Integration Automation service is free of charge
• SAP Launchpad service is bundled with RISE with SAP. No extra cost
• SAP Mobile Start is also free of charge
• Time saved with the configurations which were partially automated. About 30-40% of tasks are automated
• Almost no need for troubleshooting as input parameters are generated by the service
• Content federation from SAP S/4HANA is easy and simple
• The manual certificate configuration was quite technical and complex, but it was half automated in Cloud Integration Automation service.

The most powerful one is avoiding the need to troubleshoot issues. I remember that when I configured the principal propagation first time in Cloud Connector, I did some mistakes and took more than a week to fix.

If you are implementing a RISE with SAP project, I recommend configuring SAP Launchpad service with Cloud Integration Automation service. It will help you accelerate your project and save time as well as cost.

Reference Links:

Cloud Integration Automation service

Cloud Integration Automation service – What is it?

Start a scenario integration workflow with Cloud Integration Automation service on Cloud Foundry (BTP)

New video: Easy to Use Cloud Integration Automation service

SAP Launchpad service

Simplify Your Integration Experience of SAP Launchpad service with SAP S/4HANA

CIAS Guide: SAP Launchpad service Integration with SAP S/4HANA

SAP Mobile Start

Introduction – How to set up SAP Mobile Start in a productive landscape

My reflections since RTC (Release to Customer) of SAP Mobile Start