Skip to content

Commit 429e39e

Browse files
committed
Moving diagram up
1 parent b04f184 commit 429e39e

File tree

1 file changed

+5
-9
lines changed
  • exercises/11-aem-cloud-integration-adapter

1 file changed

+5
-9
lines changed

Diff for: exercises/11-aem-cloud-integration-adapter/README.md

+5-9
Original file line numberDiff line numberDiff line change
@@ -6,23 +6,19 @@ In previous exercises, we've communicated with SAP Integration Suite, advanced e
66
- REST protocol, from the Node.js application in exercise 08.
77
- AMQP protocol, from the CAP project in exercise 10.
88

9-
Now, in this exercise, we will consume the events from AEM using the Cloud Integration service. We will leverage the [AEM adapter](https://hub.sap.com/integrationadapter/AdvancedEventMesh) available and use it in an integration flow to consume the purchased tickets events from a queue in AEM (the AEM adapter uses the Solace Messaging protocol). We will then enrich the message and publish it to a topic. As explained in the previous exercise, there is a separate service that simulates the ticket purchased events from the ticket website. We will extend the consumption of those events in this exercise.
9+
Now, in this exercise, we will consume the events from AEM using the Cloud Integration service. We will leverage the [AEM adapter](https://hub.sap.com/integrationadapter/AdvancedEventMesh) available and use it in an integration flow to consume the purchased tickets events from a queue in AEM (the AEM adapter uses the Solace Messaging protocol). We will then enrich the message and publish it to a topic. As explained in the previous exercise, there is a separate service that simulates the ticket purchased events from the ticket website. We will extend the consumption of those events in this exercise. By the end of this exercise, we will achieve a communication scenario like the one below.
1010

11-
![Final data flow](assets/diagrams/final-diagram.png)
11+
<p align = "center">
12+
<img alt="Consuming and publishing messages from a Cloud Integration iFlow" src="assets/codejam-exercises-Exercise11 - CloudIntegration.png" width="90%"/><br/>
13+
<i>Consuming and publishing messages from a Cloud Integration iFlow</i>
14+
</p>
1215

1316
> The goal of this exercise is not to create an integration flow from scratch but to get familiar with the AEM integration adapter and understand the connectivity mechanism between AEM and Cloud Integration.
1417
1518
Before we get started, make a note of the connection details for the Solace Messaging adapter available in the `EU-North-Broker` service, as we will be using these details in the integration flow configuration.
1619

1720
![Solace Messaging protocol](assets/solace-messaging-protocol-connection.png)
1821

19-
By the end of this exercise, we will achieve a communication scenario like the one below.
20-
21-
<p align = "center">
22-
<img alt="Consuming and publishing messages from a Cloud Integration iFlow" src="assets/codejam-exercises-Exercise11 - CloudIntegration.png" width="90%"/><br/>
23-
<i>Consuming and publishing messages from a Cloud Integration iFlow</i>
24-
</p>
25-
2622
## Queue for Cloud Integration
2723

2824
👉 Access the `EU-North-Broker` and clone the queue created in the previous exercise and name it: `codejam/edi/[your-sap-community-username]/Tickets/Purchased_CloudIntegration`. Make sure to also clone the subscriptions.

0 commit comments

Comments
 (0)