Skip to Content
Technical Articles

Cloud Integration and Enterprise Messaging FAQs

Introduction

SAP Cloud Platform Integration (#SAPCPI) has enabled all the customers, irrespective of the license types, to consume JMS and AS2 adapters on their tenants.

All the CPEA (Cloud Platform Enterprise Agreement) / Enterprise Edition customers would get these capabilities (JMS and AS2 adapters) by default on their tenants. Customers with other license types (subscription) need to buy SAP Enterprise Messaging (8005999) as an a-la-cart option to activate these adapters. Required steps are mentioned in this blog.

I am writing this additional blog to address some of the frequently asked questions (FAQs) on this feature.

   FAQ 1:  The Pricing estimator of SAP Enterprise Messaging ( 8005999) is in GB, whereas the blog mentions it in SKU units. What is the relation?

  Answer: 1 unit of SKU means 1 GB.

 

 FAQ 2: SAP offers SAP Cloud Platform Enterprise Messaging on CF Environment as a messaging and event-enabling service . Does SAP Cloud Platform Integration offer the same capabilities on Neo?

Answer:

Enterprise Messaging is available in below platforms

Neo:  It cannot be used as standalone service. It is integrated with cloud platform integration for the below mentioned use cases only.

  • To enable asynchronous message processing through the below adapters
  • JMS
  • AS2 Sender
  • XI (JMS as temporary storage)

Cloud Foundry: As of Today, it is available only as a standalone service with a messaging and eventing capabilities.

But, CPI is working towards bringing the Cloud Integration service on Cloud Foundry. Once CPI becomes available on CF, it can be used for asynchronous message processing through AS2, JMS and XI adapters.

 

  FAQ 3: What is the relation between Enterprise Messaging SKU units and Cloud Integration Message Queue Units?

For Asynchronous message processing, cloud integration makes use of SAP Enterprise Messaging.

Every Message Queue created on the tenant would consume 5 SKU units of SAP Enterprise Messaging.

 

  FAQ 4: On my non-enterprise licensed CPI tenant, how can I calculate the required SKU units of Enterprise Messaging to activate and run scenarios with AS2/JMS/XI adapter scenarios.

Before I answer the question, let me explain how CPI provides asynchronous message processing using Enterprise Messaging SKU Units.

Activation: Activation of Enterprise Messaging on any CPI tenant requires 5 SKU units of Enterprise Messaging for monitoring purposes.

AS2 Sender: A unique CPI Message Queue is created whenever you deploy an integration flow with AS2 Sender adapter. AS2 Receiver adapters does not create CPI Message Queues on deployment.

JMS Adapter (Sender or Receiver): A unique CPI Message Queue is created whenever you deploy an integration flow with a unique JMS Queue name within a JMS adapter. If you are deploying another integration with the same Queue name with JMS Sender/ receiver, it would not create a new queue. But, it just uses the existing queue for reading/writing.

 XI Adapter (Sender or Receiver with JMS as temporary storage): A unique CPI Message Queue is created whenever you deploy an integration flow with XI Sender/Receiver adapter.

 

In summary,

  1. During the activation of Enterprise Messaging, each tenant consumes 5 SKU units for monitoring (They are not re-usable for message processing) .
  2. Every additional CPI Message Queue used with the above adapter scenarios would require 5 SKU units of Enterprise Messaging.

Examples:

a) SAP CP Integration, PI edition (for example) tenant, I want to activate AS2 and JMS adapters on my tenant, what is the minimum SKU units of Enterprise Messaging I need to purchase to activate these adapters?

   Answer: You need to purchase a minimum of 10 SKU units (i.e., 10 GB) to activate and run AS2 and JMS capabilities.

On Every tenant, 5 SKU units would be consumed during the activation of Enterprise Messaging and with the remaining 5 SKU units you can run only one integration flow either with

  • AS2 Sender or
  • JMS or
  • XI Sender with JMS as temporary storage or
  • XI Receiver with JMS as temporary storage.

   b)SAP CP Integration, PI edition (for example) tenant, I already activated Enterprise Messaging with 10 SKU units and running a scenario with one AS2 Sender adapter (just example).

      Now I realized that I need to run another new scenario that uses a JMS queue (for example), how many additional SKU units (GBs), I need to purchase? 5 or 10?

Answer:  You just need 5 additional SKU units (GBs) of Enterprise Messaging.

   c) SAP CP Integration, PI edition CPI tenant to run 2 different AS2 Senders

Answer: You would need

5 (Activation) + 2(adapters with JMS queues) *5 = 15 SKU units (GBs).

   d) SAP CP, app services pckg, prem edition CPI tenant to run 2 different AS2 Senders and 2 different JMS queues.

Answer: You would need

5 (Activation) + 4(adapters with JMS queues) *5 = 25 SKU units (GBs).

These are just few examples. But the same pattern will be application for all the tenants with all other non-enterprise edition licenses.

 

FAQ 5: I am a customer with 2 cloud integration tenants (1 SAP CP, app services pckg, prof ed edition (for example) and 1 SAP CP Integration, enterprise edition), Can I distribute the default Enterprise Messaging SKU units (i.e, 150 ) assigned from enterprise tenant to standard pi tenant?

Answer: No. This is not possible. The JMS resources provisioned with enterprise edition are bound to the enterprise edition tenant.

 

FAQ 6: I am a customer with 2 standard PI edition cloud integration tenants (one used for Test and second one for Production purpose), Do I need to buy Enterprise Messaging SKUs for both the tenants to run scenarios with AS2 or JMS adapters?

Answer: Yes. You need to buy Enterprise Messaging SKU units irrespective of the tenant type. You can distribute the Enterprise Message SKU units across multiple CPI tenants under the same Global Account as per your need.

E.g: If you want to run scenarios with 2 different AS2 Senders and 2 different JMS queues on each tenant, you would need

5(Activation) + 4 (adapters with JMS queues) *5 = 25 SKU units (GBs) * 2 (number of tenants) = 50 SKU units.

This is just an example. But the same pattern will be application for all the tenants with all other non-enterprise edition licenses.

 

FAQ 7: Can I move the subscribed Enterprise Messaging SKU units (purchased as an additional order) across the tenants?

Answer: Yes. Within the same Global Account, you can move the JMS resources across tenants.

You need to ensure to free up the JMS resources (Message Queues, Transactions and Storage) from the tenant where it is currently in use to allow the movement to another tenant.

 

FAQ 8: I am a customer with SAP CP Integration, enterprise edition (8005996) tenant, I have already consumed the default Quota of 30 CPI Message Queues ( 150 GB ) on my tenant. Do I need to buy additional Enterprise Messaging (8005999) SKU units to run more scenarios with additional CPI Message Queues on my tenant? 

Answer: Yes. After you consume the default quota entitled with Enterprise Edition, you need to buy and assign Enterprise Messaging SKU units (5 units per every additional CPI Message queue) to the tenant.

 

FAQ 9: I am a customer with SAP CP Integration, enterprise edition tenant, But i do not see Enterprise Messaging service under my services 

Answer: Since Enterprise Messaging comes as an embedded package as part of Enterprise Edition of CPI, you would not see the service explicitly.

You can activate Enterprise Messaging on the tenant simply by navigating to Process Integration->Configure Process Integration->Enterprise Messaging.

 

FAQ 10: I am a CPEA licensed customer and I expect SAP to charge me based on my usage. But, when I activate the Enterprise Messaging on my tenant, I get a confirmation message saying, it would activate with 30 Message Queues. Does it mean, I will get charged for 30 Message Queues (150 SKU units) every month? 

Answer: Do not worry. You will not be charged for 150 SKU units despite of activating with 150 SKU units.

You will be charged based on your JMS throughput (incoming and outgoing).

E.g:

After activation, you deployed an integration flow with JMS queue.

Consider a case, within that month the throughput of the JMS messages is 4 GB.

Then, you will be charged for 4 GB against Enterprise Messaging (8005999) material ID.

Note: We got feedback about the confusions this confirmation message is creating. We will improve the message in the upcoming release.

 

FAQ 11: I am a CPEA licensed customer and I have one tenant for Test and another one for Production. Will the JMS usage on Test tenant be charged? 

Answer: Yes. As per the contract Cloud Integration promises customers not to charge for additional connections on a Non-Production (Test) tenant.

But the JMS throughput on Cloud Integration will be charged irrespective of the tenant type.

 

FAQ 12: Can I access the JMS queues used in Cloud Platform Integration from other applications to exchange messages or events?

Answer: No, this is not yet possible.

 

Hope, this blog helps your understanding on using Enterprise Messaging on CPI and clarifies all the questions that you may have.  🙂

Be the first to leave a comment
You must be Logged on to comment or reply to a post.