Generic Inbound Gateway implementation

To process the incoming message, Interact requires information in the form of configuration to map the incoming message fields with appropriate Interact properties. The UI configuration must define all mandatory properties that Interact requires in order to call Interact APIs: startSession, postEvent, and endSession. You can perform the configuration by navigating to “Interactive Channel” -> “Gateways” -> “Generic Inbound Gateway”.

The following is a sample inbound message through Kafka channel. Kafka activity receiver mandates the “gateway” and “message” properties to identify the channel for processing. “message” contains the information sent to the inbound gateway for processing.

{
  "gateway": "GenericIn",
  "message": 
{
    "ICName": "SB_InteractiveChannel",
    "audienceID": [
      {
        "n": "CustomerID",
        "v": "1",
        "t": "numeric"
      }
    ],
    "events": [
      {
        "event": "EP_contact",
        "parameters": [
          {
            "n": "UACIOfferTrackingCode",
            "v": "5.2.ffffffffe4699811.4fad551",
            "t": "string"
          }
        ]
      }
    ],
    "parameters": [
      {
        "n": "country",
        "v": "INDIA",
        "t": "string"
      },
      {
        "n": "UACILogSeparationFileName",
        "v": "log123",
        "t": "string"
      }
    ],
    "CH_debug": "true",
    "CH_sessionID": "session1"
  }
}