Event Processing Demands Real-Time Response for Communications-Enabled Business Applications (cont'd)

Complementary Architectures
Event processing in today's rapid development and event response environment utilizes the efficiencies of two complementary architectures, Service-Oriented Architecture (SOA) and Event-Driven Architecture (EDA). SOA is a software architecture that defines the use of loosely-coupled services to support your company's business processes requirements. EDA is a software architecture that defines how systems can be designed to detect and respond to events. EDA is ideal for handling one or more, less predictive, asynchronous events happening in parallel that trigger a single action, whereas SOA is ideal for linear, predictable sequences.

advertisement

SOA and EDA are complementary in that events drive service invocation, making it an event-driven SOA, and on the flip side, services act as event generators.

Event Processor Components
The Avaya Event Processor includes the following components:

  • Event Processor Server
  • EPL (Event Processing Language)
  • EPL Studio
  • Event Processor Console
  • Event Processor Input/Output Adapters
  • Event Processor SDK, including the Applications Programming Interface (API) and the EPL+ command line tool.

    We'll delve deeper into the components of the Event Processor article and cover how developers can use each component in a future.

    The components of the Avaya Event Processor allow you to create applications that provide such functionality as event-driven customer management, portfolio management and monitoring suspicious activities.

    In the financial services industry, an event-driven customer management system can be developed to issue alerts to sales and marketing personnel, and automate communications with customers. An optimal application could work like this: A customer/marketing application includes a Web site, Customer Relationship Management (CRM) system interactions, daily transactions and a customer portfolio. These components interact with the Avaya CEBP application, which analyzes customer trends over all touch points. It then sends alerts to staff, such as when a customer browsed for a new product 30 days prior and is due to be targeted for marketing. The event is sent to the closest branch, where an employee views the event and determines whether or not to launch a call with the customer. If so, the Avaya CPM system launches the conference call and updates the CRM system after completion.

    As another example, in a portfolio management application stock movements for specific stocks on the New York Stock Exchange are monitored and relevant new events are analyzed simultaneously. Alerts are fired when the monitored stock price fall below a specified amount. Other possible scenarios include events being raised on regression analysis of the stock price, company news, or combinations of these. The system alerts investment representatives by initiating calls to their desk and cell phones, e-mail or other chosen communications device. The representatives could make the decision to create instant conference call with company fund managers to discuss the stock price.

    Finally, a common application of the Event Processor is monitoring suspicious activities. Using application data feeds, the Avaya CEBP application uses the Event Processor to constantly analyze contact and address changes in customer and account data. The Event Processor in the monitoring application also monitors transaction data by analyzing order execution constantly.

    This application also monitors Contact Center statistics and agent data using the Event Processor to analyze constantly the rules set up by the Contact Center supervisor. In all of these suspicious activities scenarios, when the Event Processor encounters suspicious patterns, CPM issues an advisory, and the employee receives an alert, confirms receipt and follows up.

    Conclusion
    Event processing must keep up with the increasingly rapid pace of business, the volume of data and complex business efficiency requirements. The Avaya approach to event processing through its CEBP application and Event Processor provide you with the tools you need to rapidly create event-driven applications that address your customers' demands. Keep track of new articles on the Avaya portal, so you can learn more about the Event Processor components and how to use them to develop event-driven, Web-based applications that make use of the efficiencies of SOA and EDA.


  • Previous Page: Event Processing at Avaya  
    Shari L. Gould has more than 16 years of journalism and technical writing experience. Shari has written for numerous leading publications throughout her career, most recently Software Development Times and its various publications, and had an article hand picked by Sun Microsystems for inclusion in its Solaris Developer Connection. She also has more than 10 years experience working with high-tech companies documenting everything from network designs and installations, through software design and APIs, to user interfaces. Shari currently is pursuing her Master's degree in Criminal Justice, specializing in Information Security.
    Page 1: Event Processing at AvayaPage 2: Complementary Architectures