Self-service enablement of Cloud Integration service on consumption-based commercial model for SAP BTP
NOTE: This blog is obsolete as Cloud Integration standalone will be replaced with Integration Suite
SAP is now offering to its customer’s self-service enablement of Cloud Integration service on SAP Cloud Platform in consumption-based commercial model. A customer who purchases Cloud Platform Enterprise Agreement (CPEA) and Cloud Credits from SAP Cloud Platform can activate or deactivate the required Cloud services based on the operational requirements.
More information on CPEA and Cloud Credits can be found in the below mentioned blogs:
Services qualified for Cloud Credits on SAP Cloud Platform
FAQ on consumption-based commercial model for SAP Cloud Platform
In this blog, I would like to discuss the steps involved for the Administrator of an account to activate and provision a cloud integration service.
Refer my other blog if you want to learn about the self-service provisioning of CPI tenants on Cloud Foundry environment.
Setting up Cloud Integration Tenant
The Account Administrator must execute the following steps to enable the SAP Cloud Integration service:
Navigate to the global account in the account cockpit page and create a new subaccount as shown below.
Enabling Process Integration Service
From the newly created subaccount, choose Services from the left pane and search for Process Integration ( formerly called as Cloud Integration) service.
Now you must choose the Process Integration tile and Enable the service.
NOTE: After the service gets enabled, there will be a new subscription created for provision application.
Configuring the Process Integration Service
Once the service is enabled, choose Configure Process Integration to configure and provision a tenant.
Tenant configuration requires you to choose the environment.Based on your operational requirement you can select Non-Production for test purposes and Production for real-time usage.
You would see the below screen after the tenant provisioning is successful.
Accessing the Tenant
NOTE: Once the role assignment is done, you need to open a fresh instance of browser and open the account page to access tenant.
Once the tenant is in active state, you need to assign the roles on the tenant.
Assigning the roles to the new Tenant
Navigate to Subscriptions page of the subaccount to assign the roles on the tmn application as shown below
Edit Tenant Environment
With May 2019 release, SAP released a new feature to allow the editing of tenant environment to address some of the Trade-in ( Subscription -> CPEA) customers concerns related to billing of additional CPI connections for their non-production tenants.
Many customers whoever traded-in have some of their tenants marked as production by default, but these tenants are used for non-production purposes in their landscape.
Using this feature, SAP enables the customers to mark their tenant environment as per their operational needs.
NOTE: Before you proceed , To understand the impact kindly read the note 2784487
You can perform the editing of the tenant environment as shown below:
Activating Enterprise Messaging
All the tenants that will be provisioned after October 2018 will have the enterprise capabilities ( like AS2, JMS , EDI Flowsteps ) available on the design time.
You can configure and deploy integration flows with AS2 or JMS adapters.
For running the scenarios with JMS/AS2 you need to activate the Enterprise Messaging.
This can be activated as shown below:
Once the activation is successful, you would see a JMS message broker activated as shown below:
This would allow you to create integration flows with JMS message queues upto 30 that has a maximum JMS storage of 9000 MB and 150 JMS transactions. More details about size limits can be found in the blog Cloud Integration – JMS Resource and Size Limits
Increase of Message Queue Quota:
Sometimes, you would end up consuming all the assigned JMS queue quota resources (queues/storage/transactions/consumers/providers ) on the tenant and the new integration flows with JMS,AS2 or XI adapters would fail during deployment with an error like “Queue creation failed”.
In such scenarios,you can increase the message queue quota as shown below:
NOTE: If you have a usecase of requiring more than 100 queues, you need to create an incident following the KBA 2589823
Deactivating Enterprise Messaging:
Enterprise Messaging can be deactivated as shown:
You can delete the tenant by simply clicking on Disable button as shown below:
You can verify the total tenants available under this Global account by navigating to License Entitlements tab
We learnt about self-service enablement of Cloud integration service on consumption-based commercial model for SAP Cloud Platform. I will meet you again with another new story on the self-service enablement of cloud integration journey.
References: Provisioning Self-Services with a Consumption-Based Account
Very Useful Info .. thank You ...
Thank you for a well-documented blog. cheers.