Cloud Integration- Activating and Managing Enterprise Messaging Capabilities ( AS2, JMS and XI Adapters ) in Neo
In this blog, I would describe the steps required to activate Enterprise Messaging on a tenant and explain the following scenarios:
- Activate Enterprise Messaging on a tenant
- Increase Message Queues quota on CPEA licensed Tenants
Step 1. Navigate to Cloud Integration Service
Prerequisite: To perform the next steps, you need to have AuthGroup.Administrator role assigned for provision application.
1.1 Navigate to Cloud Integration service as shown below
1.2. Click on Configure Cloud Integration
1.3 Navigate to Configure Tenant -> Enterprise Messaging and click on Activate.
During the activation, the tenant would be allocated with all the assigned quota on the subaccount.
The below screen appears after the activation of Enterprise Messaging.
NOTE: Message broker activation requires the tenant restart and would cause the downtime of the tenant for few minutes.
Step 2. Create and Deploy Integration Flows with JMS capabilities:
The Integration Developer can now logon to the tenant and check the status of the Enterprise Messaging by navigating to Monitor -> Message Queues -> JMS Resources Details
Now you should be able to create and deploy integration flows with AS2 and JMS adapters and use the XI adapter with JMS Queue as temporary storage.
Message Queue Quota Management
Scenario : Increase Message Queues quota on CPEA licensed Tenants
CPEA tenants get activated with default quota of 30 Message Queues without the need of purchasing SAP Enterprise Messaging.
CPEA tenants can increase the Message Queues on their tenant by simply editing the Edit Message Broker in the Configure Tenant screen. They need not purchase any additional SKUs and they would be charged based on their usage at runtime.
NOTE: If you have a usecase of requiring more than 100 queues, you need to create an incident following the KBA 2589823
This concludes my blog about Activating Enterprise Messaging, and managing Message Queues Quotas on a Cloud Integration tenant. Hope you enjoy the new feature on cloud integration.
See you again with another blog on another new feature. Until then, Take care.
Thanks Appala Naidu Uppada for the detailed blog so below are few questions -
let me answer your questions:
Many thanks for an excellent blogs.
What are the main differences between activating the service within CPI or using Enterprise Messaging as a standalone service outside of CPI?
As far as I have read in the previous reply, when enabled in CPI, the interactions with the queues/topics are limited to the CPI adapters whereas Enterprise Messaging provides capabilities to push and retrieve messages to/from queues/topics using several communications protocols as JMS, AMQP or REST. Any additional considerations to bear in mind when choosing the correct option in order to handling asynchronous queuing in CPI?
In Neo, you can consume Enterprise Messaging service only through CPI adapters.
Whereas in Cloud Foundry, you can consume it as a standalone service.
More details can be found here : https://help.sap.com/viewer/bf82e6b26456494cbdd197057c09979f/Cloud/en-US/df532e8735eb4322b00bfc7e42f84e8d.html
Many thanks Appla,
Happy new year 🙂
Hi Appala Naidu Uppada
You write in the beginning “SAP Cloud Platform Integration comes up with a new feature to enable Enterprise Messaging capabilities like AS2, JMS, XI (with JMS storage) adapters on all licensed versions of cloud integration tenants.This feature will be available for customers after 5-Jan-2019.”
But when I read the material on:
I get a bit confused in regards to how it enables AS2 and XI? From my point of view Enterprise Messaging enables an MQTT environment. How is AS2 and XI enabled? I can’t seem to find any other info than this blog on that subject.
I really hope you can clear that for me?
Enterprise Messaging is available as a standalone service on Cloud Foundry environment. AS2, JMS and XI enablement is not applicable here.
Whereas, On Neo Environment, it is consumed internally with SAP Cloud Integration within the adapters like AS2,XI and JMS. These adapters use the Enterprise Messaging service capabilities to store and process the messages asynchronously.
Hope this clarifies.
Hi Appala Naidu Uppada
Thanks a lot for your reply. I believe I understand you. I believe the sentence should state:
"SAP Cloud Platform Integration comes up with a new feature to enable Enterprise Messaging capabilities with AS2, JMS, XI", since I understood Enterprise Messaging provided you with AS2.
So just to clarify in detail: I have a scenario where we have CPI PI Editions available, but not Enterprise edition - therefore no AS2 adapter. I hoped that by utilizing Enterprise Messaging I could get access to AS2 capabilities. But I understand from your clarification, that Enterprise Messaging only provides an MQTT/ADQP platform and on Neo Environment you can access that with the adapters available in your CPI tenant (ie. AS2 if you have Enterprise Edition only), correct?
Thanks a million,
If you have a PI Edition of Cloud Integration and Enterprise Messaging of atleast 10 SKUs ( i.e, 10 GB), you will get AS2,JMS adapter capabilities on Cloud Integration design time as well the JMS Queuing capabilities on the run time after you activate the Enterprise Messaging through self-service screen of cloud integration as mentioned in blog.
Long story short,
AS2 becomes active on a standard PI edition tenant as soon as you activate Enterprise Messaging on the Cloud Integration self-service screen as mentioned in the blog.
Hello again Appala,
With this new capability we have now two mechanisms to enable asynchronous queuing over JMS in SAP CPI:
For new SAP CPI customers with Enterprise Edition license, what is the SAP recommended option? What is the way forward? What are the Pros and Cons of each option?
Many thanks for your time.
I am not sure if i got your question.
JMS Message broker activation on Enterprise Edition license would allow the customer to consume upto 30 CPI queues by default. A customer needs to buy additional SAP Enterprise Messaging units only if he has a requirement of additional CPI queues.
We have managed to activate the JMS message broker for 1 "TEST" subaccount, in which we are allowed to have 31 queues. Can we split the queues among several subaccounts (5 queues per subaccounts) as per Scenario 2? But it states that minimum queues is 31. Does this mean we need to purchase additional units if we needed 5 queues for say “PROD”?
These 31( 30 queues for your usage + 1 queue for monitoring application on the tenant) queues are allocated for your enterprise tenant and you cannot redistribute the embedded quota of the tenant to other tenants.