There's a lot of interest in integrating SAS Real Time Decision Manager with SAS Event Stream Processing. So, let's shed some light on this subject. First, let's give a quick and dirty explanation of each product and what it does. (Please remember that I said "quick and dirty" so don't get offended if I over-simplify things)
If you understood that, skip past the numbered list. If you're a little unsure about event streams, web services, value-added transformation, and targeted real time marketing campaigns, let's dig in a little more.
OK, so we have SAS ESP that transforms event streams and RTDM that executes real time marketing when triggered by web services. How can we marry these two things? Well, I imagine there are lots of ways. People are creative. One great way, for sure, however, is to have ESP transform incoming customer-focused event streams into output web-services that trigger RTDM real time marketing. Let's look at an example: Imagine that a company (say Netflix) is going to raise its subscription price and they expect some of their customers to cancel their subscription because of it. They figure that cancellations will follow a certain pattern:
The company could modify their system to send a web service to RTDM when the customer hits "Cancel" (step 5) but that is too late. The customer has already cancelled. Assuming that we can capture all of the events described (Big Brother, I know), SAS ESP could look for the first three events (Open email -> Open Web Site -> Click "Account") with its Pattern Window and trigger RTDM preemptively. Maybe RTDM could send them a coupon or a list of really great movies that are coming next month. Regardless, as the example shows, ESP extends the capabilities of RTDM so it doesn't just react to a single event but to a pattern of events across an event stream.
So what's interface between ESP and RTDM? As I mentioned earlier, RTDM campaigns are triggered by web services. So the interface is literally a simple REST or SOAP call. ESP comes with a REST Adapter (a simple command line executable) that subscribes to ESP models and publishes the output event streams to target REST URLs. ESP also has a robust REST API that allows for simple URL-based output event subscription. See the doc for more information.