Testing Objectives

  1. To create a Sales order, publish the event and monitor the events in SAP.
  2. To be able to receive the events in Integration Suite.
  3. To be able to publish the events to a dummy queue in AEM.
  4. Monitor the Dummy queue message count increase.
  5. Create a subscriber iFlow to consumer messages from the dummy queue (optional).

Table of Contents

  1. Testing Objectives
  2. Table of Contents
  3. Create an SO
  4. Receive Event in Integration Suite iFlow
  5. Publish event to dummy queue in AEM
  6. (Optional) Create a subscriber iFlow for the dummy Queue
  7. Where to go from here?

Create an SO

I will not go over the details of the SO Creation steps, but just to show its flow to AEM.

Receive Event in Integration Suite iFlow

We will enable the “Trace” first to be able to check payload for confirmation.

Head over to the iFlow 1 (AEM to IS-Subscribe):

Now if we look into traces for this, you will see the SO is received.

Note that in AEM you can see that there is one consumer for mentioned ICO. However, if our iFlow doesn’t listen to the relevant endpoint configured in the queue, the consumer count will be zero.

As messages are not persisted in the queue as long the consumer has successfully received message you can not see it. In next example however, we will be able to see the count in “Message queued” column.

Below is the flow though which the event ends up in Integration Suite:

Publish event to dummy queue in AEM

First, we will disable the first iFlow as both expose same endpoint. then we will deploy the modified second iFlow and enable “Trace” to check dynamic topic details.

Next, lets create a new SO.

This event is published to Event Mesh through HTTP Destination (SM59) in ERP system which points to the broker.

From Event Mesh it is published to “https://{is-host:port}/http/socreate” and ends up in Integration Suite.

In the iFlow we derivee the dynamic topic parameters and publish it to the topic in the AEM.

As we test the iFlow, you will see the count increasing on the queue in AEM as seen below:

The reason for this is that IS is publishing the event to the dynamic topic endpoint which is added as subscription to this queue.

(Optional) Create a subscriber iFlow for the dummy Queue

You can build a new iFlow which listens this queue (i.e. CITestSalesOrder) and is able to consume the events for Sales Order in our case.

This optional activity will help you to understand what you need to create and change to be able to receive and publish events.

Where to go from here?

If you have AEM Trial or licensed software available, dig into:

  1. RDP Configuration
  2. Message VPN
  3. Achitecting optimal mesh for your needs.
  4. Settings for various types of connectors.

There are numerous settings in AEM which can open up new doors to new capabilities, easing out on already existing solution. You can dig into that once you are comfortable with basic terminologies mentioned in this blog series.

Note: As I have written and explained most of the concept in the way I understand them and worked for me, feel free to builld your own framework of understanding of different topics.

Thank you and I will see you in next blog on another topic.