Information Flow in Asynchronous Publishing

The following flow explains the steps in the previous section.

In asynchronous or 2-Step publish, broadly the following sequence of information flow takes place:

1. The record ID (or any other identifier field data) is published to Kafka.

2. The published ID is then asynchronously consumed by Siebel using Subscription.

3. Siebel generates the complete payload per the eventpayloadconfig.txt file.

4. Siebel sends the complete payload to Kafka.

Therefore, configurations for asynchronous or 2-Step publish involves configurations for the following:

1. Synchronous Publish of record id (or any other necessary and equivalent field) to a topic.

   Sample payload:

   • Use case (extract from eventpayloadconfig.txt):

     	Event: testevent1
     	Business Service: Event Pub1
     	Business Service Method: SendEvent
     	Business Object: Contact
     	Primary Business Component: Contact
     	Context Field: Id
     

   • Old Payload:

     	{
     	  "BusinessObjName": "Contact",
     	  "Id": "88-328W54",
     	  "ToSubscriber": "True",
     	  "BusinessCompName": "Contact"
     	}
     

   • New Optional Payload:

     	{
     	  "Id": "88-328W54",
     	  "ToSubscriber": "True"
     	}
     

2. Subscribing to the topic from the last step and calling necessary business services (derived from CSSEAIEventHandler class) for subsequent publish of full payload to a desires Kafka topic.