This blog is part of a series which is related to configuring and using SAP Cloud Platform Serverless services along with Open Connectors.
|React to events and connect 3rd Party systems using Serverless services & Open Connectors|
In the previous blog post, we had a look at how to configure SAP Cloud Platform Open Connectors and in particular test the Twitter APIs to post a tweet. In this part of the blog, I will show you how to configure SAP Cloud Platform Enterprise Messaging service.
Enterprise Messaging service is also available in the trial landscape of the Cloud Foundry environment. Navigate to your global SAP Cloud Platform account and under “Entitlements” menu, allocate units of Enterprise Messaging and Functions to your trial subaccount.
Within the space in the Cloud Foundry account, you should now be able to see both the services listed in the Service Merketplace.
Click on the “Enterprise Messaging” tile and from the Instances menu, create a new instance
In the create instance popup window, accept the default “dev” plan
In the Parameters section, you would need to provide an “emname” along with few options. These are mentioned in the SAP Help documentation.
In the last screen, provide the instance name same as the emname (for convenience)
This will create an Enterprise Messaging instance as shown below. Launch the administration screen by click on the “Show Dashboard” icon in the right hand corner.
In the Enterprise Messaging Administration screen, you have many options to create and manage queues. From the Queues menu, click on the create button to create you’re a queue.
Once your queue is created, its now ready to be used. You can have applications which push & receive messages from this queue.
Since we are going to integrate Enterprise Messaging service with Functions, we would need to create a Service Key. Navigate back to the newly created instance of Enterprise Messaging and select it to find the “Service Keys” menu.
When you create a new service key, it will provide you with set up of parameters in JSON format. Notice there are three “oa2” sections for each supported protocols.
This concludes the configuration of the Enterprise Messaging service. In the next blog post, I will go through the configuration steps for Functions and test this E2E scenario.