HPE Shadowbase Streams for Application Integration

HPE Shadowbase Streams is a powerful and flexible facility that enables diverse applications to interoperate with each other at the event-driven level (called application integration). This capability is provided even for legacy applications that were never intended nor designed to work together. Shadowbase Streams focuses on distributing information in real-time throughout the enterprise, enabling the provision of a Real-Time Enterprise (RTE), a concept in business systems design focused on ensuring organizational responsiveness. It rapidly delivers information where and when it is needed without customer application modification. The application’s responsibility is simply to make functional use of the data delivered by Shadowbase Streams.

With application integration, events generated by a source application are sent in real-time to a target application for processing, and is known as an Event-Driven Architecture (EDA), a software architecture pattern promoting the production, detection, consumption of, and reaction to events. Target application processing may or may not result in a reply back to the source application. Target system applications may use the events generated by the source application for expanded functionality. Therefore, integration using Shadowbase Streams typically involves sending a source application’s events from one environment to a target application in another.

HPE Shadowbase Streams Event-Level Integration

Figure 1 — HPE Shadowbase Streams Event-Level Integration

Event-level integration enables Event-Driven Architectures, which deliver services based on changes made to the source system’s database. Event-level integration avoids the necessity of developing special agents or adapters for each application that is to be integrated. Rather, it monitors source application events in real-time and sends them immediately to the target application so that action can be taken on the event by the target. This method is employed by HPE Shadowbase Streams for Application Integration. It makes use of the fact that in most applications, events are evidenced by changes made to the application’s database. As shown in the figure below, Shadowbase Streams monitors these database changes. If a change represents an event of interest, Shadowbase Streams reformats the event data as required by the target application and it is sent to the target application for processing.

Figure 2 illustrates an application on the source system that makes changes to a database, which are recorded in a transaction log. Triggering database updates in the TX log are predetermined to Shadowbase Streams by the configuration parameters. The updates are detected by HPE Shadowbase Streams, which selects the appropriate events and delivers them to the target application through a variety of supported application interfaces (thereby avoiding the need for any changes to the target application):

  • A work queue from which the target application can fetch events
  • A work file from which the target application can read events
  • Messaging middleware, such as IBM MQSeries, which accepts events and passes them to the target application (via its own mechanisms, for which the target application is written)
  • A specific API that can be called to supply events (e.g., a procedure call)
  • TCP/IP sessions established with the target application over which events can be passed
  • Published events to which the target application can subscribe
(Target) application interfaces supported by HPE Shadowbase Streams: Work queue, database file, middleware, api's, tcp/ip session, pub/sub, etc.

Figure 2 — Application Interfaces Supported by HPE Shadowbase Streams

Using HPE Shadowbase Streams to integrate applications provides many benefits to the enterprise, enabling the business value inherent in isolated applications to easily be unlocked and leveraged to deliver new business services, as an RTE.

  • Shadowbase Streams is efficient. It is event-driven and acts only upon selected data-change events as they happen.
  • Applications can react to events in real-time as they occur. There is no need to periodically poll for pertinent events, a process that introduces significant latency and overhead into event-processing.
  • Because events are processed in real-time, there is no stale data. The reaction to events is timely and the data is always up to date.
  • No application code changes are required to monitor and deliver selected events to a target application. There is no need to build costly and complex agents and adapters.
  • Shadowbase Streams is heterogeneous. It interoperates between a variety of applications, databases, and platforms from different vendors.
  • A source system generating events can act as a hub, sending events to multiple other systems. Each system can receive its own set of events formatted according to the requirements of its own target applications, on a schedule that matches the target application’s needs.
  • Shadowbase Streams can publish events as they occur. Different target applications can subscribe to the subset of events that they would like to receive.
  • Shadowbase Streams is flexible. It can be configured in a variety of architectures to provide a wealth of application integration options, and processing can be customized to meet specific application requirements.

Related Solutions:
Related White Papers:
Related Case Studies:
Related Solution Briefs: