Integration Suite - Simplified Onboarding and Provisioning

[appalanaidu_uppada]

Introduction

SAP Integration Suite is an open, versatile, modular and enterprise-grade iPaaS supporting a comprehensive set of enterprise wide integration scenarios.

In this blog, we would like to inform you about two key aspects of Integration Suite that you can consume starting from May 2020 release onward.

1. 
   
   
   
   1. Simplified Onboarding
   
   
   2. Harmonized Provisioning
   
   
   
   

Let’s get started.

November 2023 blog update:

• Updated the provisioning experience for creating Edge Integration Cell nodes, which enables you to manage APIs and run integration scenarios within your private landscape.Scroll down to the bottom of the blog to check the steps.

March 2021 blog update:

• Updated the provisioning experience for different types of Global Accounts (Feature A or Feature B).


• Updated with consolidated SAP BTP cockpit changes.


• Updated the provisioning flow with additional steps like Accessing Runtime and Usage Analytics.

Simplified Onboarding

Integration Suite includes powerful capabilities like Cloud Integration, API Management, Open Connectors, and Integration Advisor to enable A2A, B2B, B2G and API-based integrations.

Refer the note https://launchpad.support.sap.com/#/notes/2903776 for getting more details on features offered via different SKU of Integration Suite.

All CPEA/PAYG/PAYG-TDD customers can take advantage of the free tier offering. Refer my integration suite free tier blog to get started with a Integration Suite free tier tenant.

Harmonized Provisioning

NOTE 1 :  If your subaccount has subscriptions to Process Integration, API Management, and/or Open Connector services, please subscribe to the Integration Suite service in a new subaccount

NOTE 2:  If you are coming from Neo CPI background , kindly note that unlike Neo times, Integration Suite tenants should be provisioned by the customers.

Trial users can refer Set Up Integration Suite Trial

Let us take a closer look at the different steps involved in provisioning of an Integration Suite tenant.

The diagram below summarizes the steps involved:

Integration Suite Tenant Provisioning - Overview

In this blog, I would cover steps 1,2 and 3.

Step 4 would be covered in this blog: Integration Suite – Accessing Cloud Integration Runtime

Step 5 would be covered in this blog: Integration Suite – Usage Analytics

Prerequisite: Identify the Global Account Type

One of the key prerequisite to consider is to Determine your Global Account type as the provisioning process will slightly differ based on whether the Global Account is of Feature Set A or Feature Set B

Navigate to SAP BTP Cockpit > Global Account > User (top right corner) > About to determine the Global Account type as shown below:

Global Account Type - Feature Set A or Feature Set B

 

Step 1: Create Subaccount and Assign Entitlements

a) Create New Subaccount :

Only Global Account Administrator can create a new Subaccount by clicking on New Subaccount as shown below:

Refer Create a Subaccount for additional information on Creating Subaccount.

NOTE 3:  Integration Suite is not available on Neo based environment. Hence, make sure that the Subaccount that you are trying to create should not be of Neo environment type.

NOTE 4:  Used for Production checkbox is meant only to provide transparency whether the subaccount will be used for production or not. The value of this parameter has no impact on Integration Suite tenant or the metering of the usage.This checkbox is for your reference only.

1.a. Create New Subaccount

b) Enable Cloud Foundry ( not a mandatory step to provision a tenant ) :

This step is required to create service instances for accessing the Integration Suite runtime which shall be covered in Step #4 in another blog.

1.b. Enable Cloud Foundry

c) Assign Entitlements

This step behavior will vary based on the Global Account Type ( Feature Set A/ Feature Set B) and Global Account Contract Type ( Subscription / Consumption ). Based on the feedback received from different users, i tried to summarize different kind of entitlements available in Integration Suite and their behavior on different kind of Global Accounts.

1.c.i) Entitlements > Service Assignment:

Integration Suite will have below three type of entitlements:

•    SaaS Application Plans


•    Message plan


•    Service Plans

SaaS Application Plans:

The quota for these plans ( e.g: standard_edition (or) enterprise_agreement ) are required to Subscribe to  Integration Suite SaaS application and provision a tenant.

NOTE 5:  SaaS application plan assignment is not relevant for Feature Set A Global Accounts.Do not get surprised incase if you do not see an entry for Integration Suite SaaS application plan under entitlements. In Feature Set A Global Accounts,by default, all subaccounts will display the Integration Suite tile if you have entitled to Integration Suite service. But, your quota will be restricted with a check at the subscription step.

Messages Plan:

All Subscription based Global Accounts would show messages as an entry under Entitlements -> Service Assignments. But assigning this quota to different subaccounts would not have any impact provisioning or metering. This entry is shown to give transparency to Global Account Administrator on the overall eligibility of messages quota.

This plan is not relevant for CPEA Global Accounts since you would be metered and charged based on your monthly consumption.

Service Plans:

The quota for these plans are required to create Service instances/keys for accessing the runtime.I shall be covering additional details while explaining step #4.

Navigate to this page to view the service assignments available on your Global Account as shown in below screenshots:

Feature Set A - CPEA Global Account (sample screenshot)

Feature Set A- CPEA- Entitlements - Service Assignment

Feature Set B - CPEA Global Account (sample screenshot)

Feature Set B - CPEA - Entitlements - Service Assignments

NOTE 6:  enterprise_agreement is the plan name used in CPEA Global Accounts. The suffix word Subscription used here after the plan name is to provide the user additional information that this plan is associated with a SaaS application. 

1.c.ii) Entitlements > Subaccount Assignment:

Assign the required entitlements quota ( SaaS Application plans and Service plans on the subaccount ) as shown below:

As mentioned earlier, there is no need to assign SaaS Application plan quota for Feature Set A Global Account.

The screenshot shown below is from Feature Set B ( CPEA Global Account ). Here I would be assigning all the plans (  Application Plan and Service plans) required for CPI. If you have a scenario to access APIM runtime, you can also assign APIM service plans as well.

Navigate to Entitlements > Entity Assignment > Configure Entitlements > Assign Service Plans as shown below:

Feature Set B- Entitlements - Entity Assignments - Configure Entitlements - Assign Service Plans

Select services and corresponding plans as shown below:

Select - Assign Service Plans - Save

Refer  Managing Entitlements and Quotas Using the Cockpit for additional details.

With this step, we have successfully completed step #1.

 

Step 2: Subscribe to Integration Suite SaaS Application:

As you would have already noticed, SAP BTP Cockpit  consolidated both applications and services into one service marketplace.

For additional information refer the blog: Introducing the new consolidated marketplace on SAP Business Technology Platform (SAP BTP) cockpit!

2.a Subscribe to Integration Suite:

Navigate to Service Marketplace > Select Integration Suite Application as shown below:

Service Marketplace - Select Integration Suite

 

Select Create > Keep the defaults in the next screen and click on Create as shown below:

Create Subscription

 

2.b Assign Roles to Access Application:

Configure Trust Configuration to Assign Roles by navigating to Subaccount > Security > Users 

Assign Role Collection Integration_Provisioner as shown below:

 

 

2.c Navigate to Integration Suite Launchpad

Navigate to Integration Suite Launchpad ( based on the screen you are in ) as shown below:

Go To Application - Screen 1

 

Go To Application - Screen 2

With this, we completed Step #2.

 

Step 3: Provision a Tenant via Add Capabilities of Launchpad

1. After the assignment of the role collection  "Integration_Provisioner" , clicking on Go To Application link would take you to Integration Suite Launchpad page . Click on Add Capabilities as shown below

Integration Suite Launchpad- Add Capabilities

 

2.You would be navigated to a page to select the capabilities that you want to activate on this Integration Suite tenant.

NOTE 7:  The environment ( Production or Non-Production) value chosen for Cloud Integration would not have any impact on metering and billing. 

 

3. Click Activate.

  Once the tenant provisioning has been completed successfully, you will be directed to the following screen:

Provisioning page with a back navigation to Launchpad

 

Congratulations! You have successfully provisioned Integration Suite tenant. Click on the Integration Suite link on the above page to navigate to the launchpad.

Integration Suite Tenant with Activated Capabilities

Assign Capabilities specific roles:

In order to access different capabilities, you need to have the corresponding roles assigned to your user. For CPI, you need to assign PI_Administrator / PI_IntegrationDeveloper / PI_BusinessExpert etc. based on the persona accessing the capability.

Assign Roles for accessing the capabilities

 

Increasing the JMS Message Broker resources:

You can also increase the JMS resources associated with your CPI tenant from the default 30 Queues upto 100 queues as following the below two steps

 Select Edit in Cloud Integration:

Edit Cloud Integration Configuration

 

Increase the JMS Queues

Increase JMS Queues

NOTE 8:  Increasing the JMS Queues would automatically increase the associated JMS resources like Max. Storage & Max. JMS Transactions

 

NOTE 9:  If you require more than 100 JMS queues, follow the SAP Note 2904202

 

Provisioning an Edge Integration Cell Node

Pre-requisites:

• One of the pre-requisites for creating an Edge Integration Cell Node to manage APIs and run integration scenarios within your private landscape is to have Integration Suite with standard, premium,CPEA/PAYG license.


• This is available on selected regions, refer the note 3326553 for details


• There are few limitations you should be aware of . Refer the note 3391207 for details.

Step 1: Verify the Edge Integration Cell entitlements.

Global Account admin can already see Edge Integration Cell Entitlements assigned for all existing/upcoming contracts with Integration Suite standard+ licenses.

The quota assigned will vary based on the contract and the quantity of Integration Suite tenants

purchased.

1. Verify Edge Integration Cell entitlements on GA

Step 2: Assign the Edge Integration Cell Quota on the Subaccount

Global Account Admin can decide to distribute the available Edge Integration Cell Quota to different Subaccounts.

In the below example, I would be assigning 2 Quantities of Edge Integration Cell to the subaccount. Customers can decide to use all the available Quota within one or more selected subaccounts.There is no tight coupling of Edge Integration Cell quota with Integration Suite tenant.

2. Assign Edge Integration Cell Entitlement on Subaccount

3. Update assigned Quota ( optional )

Step 3: Activate Edge Integration Cell Runtime

You need to be assigned with the role Integration_Provisioner to perform this action.

Edge Integration Cell can be activated by navigating to Settings -> Runtimes as shown below.

4. Activate Edge LM Subscription

Step 4: Assign Edge LM roles to Add an Edge Node

Step 5. Add Edge Node

Navigate to the Edge LM URL and add a node. For detailed step refer the guide

Refer the blog next-gen-hybrid-integration-with-sap-integration-suite-edge-integration-cell-introduction-setup for detailed next steps

Summary

In summary, with SAP Integration Suite, users will experience a simplified onboarding model and a harmonized provisioning process which will further improve the handling and using of the different capabilities of Integration Suite: Cloud Integration, Open Connectors, Integration Advisor, API Management.

Related Blogs:

Integration Suite – Accessing Cloud Integration Runtime

Integration Suite – Usage Analytics

Help Documentation:

https://help.sap.com/viewer/product/SAP_CLOUD_PLATFORM_INTEGRATION_SUITE

 

 

 

 

 

[fatihpense]

Hello Appala,

Thanks for sharing this. I think it is very important for the CPI Suite to have a clear and documented capability, licensing, pricing options.

Regards,
Fatih

[saurabhkumbhare]

Thanks Appala.

Good to see your blog.

Miss working with you since those Arla days 🙂

Regards

Saurabh

[former_member675302]

Hi,

thanks for the blog. Does this change anything for existing subscriptions and is there a difference between Neo and Cloud Foundry tenants?

Also some other questions:

• Do you have pricing infos?


• How many queues are included?


• How many worker nodes are included per CPI tenant? Or does one tenant mean one worker node?

Best regards

 

[piyush_gakhar]

Dear Markus,,

 

Pricing information is available at sap.com estimator or you can reach out to your Account Manager. Integration Suite provides inbuilt JMS queue capabilities and it is included in license.

 

Regards,

Piyush

[Murali_Shanmu]

Great to see a simplified onboarding. I noticed you haven't covered the entitlement assignments

[Harish_Kintali]

Is this applicable for NEO as well ? Especially when customers are migrating let us say from one data center to other...they might need both subscriptions to be active until the duration of the migration.

[former_member594998]

Hello, this makes sense as it simplifies entire onboarding and dont have to switch between different subaccounts for navigating in and out.. i also see these services are available as individual “services” and part of suite.. is there anything we should think before we enable it within integration suite capability or individual one?

[appalanaidu_uppada]

Hello Harish,

This is available only on CF as of today.

Thanks,

Appala

[appalanaidu_uppada]

Hello Subash,

In a given subaccount, you can either activate the services via the individual tiles (or) all via Integration suite tile.

 

Thanks,

Appala

[appalanaidu_uppada]

Hello Murali,

SaaS application entitlement management is not available yet for productive usage. As of now, it is available only on Trial landscape. Integration Suite tile would automatically appear on all subaccounts on productive landscapes without the need to assign entitlement. Nevertheless, i added a note on it.

Thanks,

Appala

[michael866056]

Hello,

At the step 2. Click Activate to provision the selected capabilities.

I receive the error "UPDATE_FAILED"



If i try to "subscribe" again it give this error



there is something that i can do to solve that issue?

 

Regards.

[michael866056]

Hello,

I was able to fix it deleting the trial account and following the guide again.

 

Thanks.

 

 

[rahul_a]

Hi,

Deleting and recreating the account has not solved the problem for me. I keep getting the same error.

Can someone suggest a solution?

Thanks,

Rahul

[rasjoshi]

Hi appalanaidu.uppada ,

I assigned roles and now trying to click on “Go to Application“. I am getting below error –>

Google Chrome -->

Your connection is not private

Attackers might be trying to steal your information from suite1.integrationsuite.cfapps.eu10-001.hana.ondemand.com (for example, passwords, messages, or credit cards). Learn more

NET::ERR_CERT_COMMON_NAME_INVALID

Internet Explorer --> 

The hostname in the website’s security certificate differs from the website you are trying to visit.

Error Code: DLG_FLAGS_SEC_CERT_CN_INVALID

Because this site uses HTTP Strict Transport Security, you can’t continue to this site at this time.

Please help to understand it and resolve.

BR,

Rashmi

[appalanaidu_uppada]

Hello Rashmi,

Kindly unsubscribe & wait for 30 minutes and subscribe the tile again.

Thanks,

Appala

 

[former_member473375]

Hi Appala,

is there any updated page, because the process is different now. UI has changed.

Best regards

Peter

[appalanaidu_uppada]

Hello Peter,

 

Thanks for the feedback. I shall update the blog with latest screenshots of consildated service market place.

 

Thanks,

Appala

[JaySchwendemann]

Bold move to call this "simplified" 🙂 . Nevertheless, thanks for the guiding hand. Very much needed and appreciated. I second Peter in that it would be nice to have updated screenshots

[alex_radu]

Thanks @appalanaidu.uppada for this article, it saved me some frustration with the ability to activate the CI / Integration Suite. The proper role was created during the BTP trial, but my user was not added to / part of that Integration_Provisioner role.

[appalanaidu_uppada]

Dear Alex,

Thank you for your feedback. If your Global Account is of Feature set B, it should be assigned automatically like trial. Incase such assignment is not happening, request you to create a BCP an incident on LOD-HCI component.

 

Thanks,

Appala

[NareshDasika18]

Would it be possible to setup any number of Integration Suite tenants from SAP BTP by creating a new sub account? If so, Is there any cost associated with it?

[Wes_Ancog]

This is really good stuff! Thank you!

[Juliuspereira]

Hi Appala,

I had a few questions.

We currently have subscriptions to Process Integration, API Management, and/or Open Connector services in 2 cloud foundry tenants (test and prod). We have now purchased Integration Suite subscription. My questions.

1. Can we get the integration suite service available in the service marketplace in our existing tenants?
   
   
   
   1. Once/ if this is possible and done, do we need to do anything to move our existing artifacts, mappings etc. from the existing ala carte subscriptions to the integration suite service
   
   
   
   


2. I see in your note above that we need to get new tenant and subscribe to Integration Suite in the new tenant.
   
   
   
   1. If yes, how do we migrate all our artifacts, value mappings etc from the existing tenants to the new tenants
   
   
   
   

I appreciate any insights that you can provide around this.

Thank you

Julius

 

 

[Sanatan]

How can we extract information of field data flow from Recruiting to Onboarding for Crossboarding cases?