Changes on RCT to accept responses over webhook
RCT can be enhanced to accept incoming responses as it already handles further processing like saving those responses in Deliver OP tables or handing over responses to Journey for messages sent from Journey.
Deliver has changed RCT to a Spring Boot standalone application which can be
triggered from command line or in dockerized manner. REST controllers are exposed in
RCT which can handle responses pushed by Deliver OD. For example, inet responses can
be pushed to the endpoint /inetresp. This endpoint is exposed at a
common path. Example:
https://CAMPAIGN_HOST:CAMPAIGN_PORT/deliver/responses. Use this
as a proxy URL instead of directly exposing the host which runs RCT (which is either
Campaign web or listener node).
Securing communication between OD and OP
Customers must provide inbound access to above mentioned URL so Deliver can push responses to that URL. Inbound requests into customer's OP network must be secured so RCT will process responses originating only from Deliver datacenters. To secure the communication, Whitelist Deliver IP address which pushes responses into customer's network.
Performance and Scaling considerations for RCT
Based on typical response numbers (example 1 million contact, 1 million responses) determine if a single RCT instance can handle load of all incoming response events and and recommend scaling based on contact and response data getting processed by Deliver for each customer.