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.
- Simplified Onboarding
- Harmonized Provisioning
Let’s get started.
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.
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.
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:
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:
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: 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.
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.
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 4: 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.
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.
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)
NOTE 5: 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:
Select services and corresponding plans as shown below:
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:
Select Create > Keep the defaults in the next screen and click on Create as shown below:
2.b Assign Roles to Access Application:
Configure Trust Configuration to Assign Roles by navigating to Subaccount > Trust Configuration
Assign Role Collection Integration_Provisioner
You need to click on Show Assignments followed by Assign Role collection
2.c Navigate to Integration Suite Launchpad
Navigate to Integration Suite Launchpad ( based on the screen you are in ) as shown below:
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
2.You would be navigated to a page to select the capabilities that you want to activate on this Integration Suite tenant.
NOTE 6: 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:
Congratulations! You have successfully provisioned Integration Suite tenant. Click on the Integration Suite link on the above page to navigate to the launchpad.
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.
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 and API Management.