Setting Up SAP Cell and Gene Therapy Orchestration Event Mesh

Customers who subscribe to SAP Cell and Gene Therapy Orchestration must also create a subscription to the SAP Event Mesh default plan in order to integrate with other applications.

To configure the default plan, you need to add service plan under the entitlement section.

1. In the same subaccount, go to entitlement section.

2. Configure Entitlements Add Service Plans.

3. In the Subaccount Entitlements dialog box, choose the Event Mesh service.

4. In the Service Details: Event Mesh window, choose both the service plans.

5. Choose Add 2 Service Plans to add this entitlement for the Event Mesh service in your subaccount.

6. Choose Save.

   Note

   If the entitlement isn't available then go to global account level and add the entitlement on global account level. If no entitlement is available at global account level, then reach to the SAP Business Technology Platform support.

In this step, you will create the instance for SAP Event Mesh service. The service plan added in the previous step will be visible and used to create the instance. Follow these steps:

1. On subaccount level, navigate to Instance and Subscription menu. Go to Instance tab, choose Create.

   

2. In the dialog box, search the service plan using "Event Mesh" as a search term. The SAP Event Mesh service plan added by the entitlements step would be visible in the list.

3. Choose the service plan "Event Mesh".

4. Select the default - Instance plan. There are two types of plans available in the dropdown menu named standard and default. Choose the default plan.

   

5. Choose runtime as Cloud Foundry.

6. Choose Space.

   Note

   The space was created in previous lesson.

7. Enter Instance Name (for example, cgto-dev-em).

   Note

   You can use your own instance name, follow the naming guidelines provided under the information icon.

8. Choose Next.

9. The following service descriptor should be provided during an instance creation of the SAP Event Mesh.

   Code Snippet

   Copy codeSwitch to dark mode

   123456789101112131415161718192021222324252627282930313233
   
   {
   "version": "1.1.0",
   "emname": "<em-instance-name>",
   "namespace": "<namespace>",
   "options": {
     "management": true,
     "messagingrest": true,
     "messaging": true
   },
   
     "rules": {
       "topicRules": {
       "publishFilter": [
       "${namespace}/*",
       "*"
       ],
       "subscribeFilter": [
       "${namespace}/*",
       "*"
     ]
     },
     "queueRules": {
       "publishFilter": [
         "${namespace}/*"
       ],
       "subscribeFilter": [
       "${namespace}/*"
       ]
      }
     }
   }
   

10. Update emname and namespace during instance creation.

    

    Note

    To update emname and namespace during instance creation refer to more information Syntax for Service Descriptor.

11. Choose Next and Create.

In this step, you can create the subscription for SAP Event Mesh to access the application. Complete the following steps:

1. On subaccount level, navigate to Instance and Subscription menu. Go to Subscription tab, choose Create.

2. In the dialog box, search the service plan using "Event Mesh" as search term. The SAP Event Mesh service plan added through the entitlements step will be visible in the list.

3. Choose the service plan "Event Mesh".

4. Select the correct subscription plan. There are two types of plans available in dropdown menu named Subscription and Instance. Choose the Subscription plan.

   

5. Choose Create.

Let's take an example of creation of Treatment Order.

1. A request (in form of event) from patient information system is sent to the SAP Event Mesh Service topic name "default/sap.cgt/-/inbound/events/receiver".

   Note

   You need to ask for the API details to publish the data into this queue. For more information on how to publish the event using Rest API, refer the documentation link, Use REST APIs to Send and Receive Messages.

2. In the SAP Event Mesh, topic send this event to an inbound queue named "default/sap.cgt/-/inbound/events/receiver" (pre-delivered by SAP already).

3. SAP Cell and Gene Therapy Orchestration applications establish a messaging protocol with the Queue using AMQP/HTTP and consume these messages from the queue.

4. In SAP Cell and Gene Therapy Orchestration, information provided in the request payload is verified and the application creates the treatment order number.

5. The SAP Cell and Gene Therapy Orchestration application tries to look up the customer namespace's queue created with pre-defined Topic - "<default/sap.cgt/-/inbound/responses" - if it is found, the response message is pushed to the customer namespace queue 'default/sap.cgt/int001/response'.

6. The Patient information system needs to keep listening to this response queue and consume the response messages from this queue. The technical implementation can be done either by configuring the webhook option or using any other middleware to directly consume the queues using REST API.

The SAP Cell and Gene Therapy Orchestration application has many outbound events available like Approve Details Update in treatment order, Processing Node planned date update, and Update Logistic Details for bio specimen shipment scenario and many more.

Let's take an example of an approval details update of Treatment Order. When the treatment order is approved for processing in the SAP Cell and Gene Therapy Orchestration application, it is important for a Patient information System to keep the status updated for the treatment order. The Patient Information System needs to consume this outbound event by connecting to SAP Event Mesh.

Here are the high-level steps:

1. Order is approved in SAP Cell and Gene Therapy Orchestration, an outbound event is triggered.

2. SAP Cell and Gene Therapy Orchestration will look up the pre-defined topic 'default/sap.cgt/-/outbound/events' configured in customer namespace event mesh instance and if found, event is pushed into the queue named "default/sap.cgt/int001/cgto/outbound".

3. The Patient information system need to keep listening to this outbound queue and consume the outbound messages from this queue. The technical implementation can be done either by configuring the webhook option or use any other middleware to directly consume the queues using REST API approach.