Key Components and Message Flow BAM Server

Event Engine BAM Web Apps Alerts OEP Message Queues Enterprise

1

2

3

This slide shows the architectural components of Oracle BAM.

1. Data source infrastructures provide real-time and historical information, most commonly in the form of messages. This enables Oracle BAM to update dashboards

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

co o y t e o o essages s e ab es O ac e to update das boa ds

and generate alerts very quickly. Oracle BAM can accept tens of thousands of updates per second into a memory-based persistent cache that is the center of the Oracle BAM architecture. Any application can send events using web services or over any JMS- based messaging protocols. Legacy applications can integrate with Oracle BPEL PM using custom-created adapters and can in turn integrate with Oracle BAM via the Oracle BPEL PM native sensor architecture. In addition to integrating real-time information coming out of these message queues, you can integrate historical data or information coming out of these message queues, you can integrate historical data or information coming out of any operational database or any data warehouse.

2. Oracle BAM:

- Enterprise Integration Framework: The Enterprise Integration Framework is a

collection of enterprise integration components for Oracle BAM. It connects Oracle BAM to enterprise information sources such as a database server, flat files, and XML sources.

It is also capable of reading messages from all of the major message queue providers, and then running that data through real-time data integration plans. Real-time integration plans cleanse the data, aggregate it, filter it, correlate it, and perform other necessary actions before sending the data to the Active Data Cache. - Active Data Cache (ADC): The Active Data Cache is designed to provide access

to current business information for event-based reporting and alerting. ADC offers real-time, intelligent, analytical data cache capabilities. Using Active Viewset technology, the ADC can monitor and detect changes in specific views that users have on the data. When Active Viewset detects changes, it sends changes to the dashboards (to update the real-time visualizations in the dashboards, to the Event Engine (to perform all of the actions that are defined in the alert), or to both. The g ( p ), ADC stores all data in memory. The database is used to persist data to disk. When the Enterprise Integration Framework sends data, the ADC simultaneously writes data to database tables. When required, this data can be pulled from the database to memory.

- Report Cache: The Report Cache offloads the viewset snapshots so that the ADC

does not have to maintain them in memory. The Oracle BAM Report Cache opens viewsets and active viewsets in the Oracle BAM ADC for the Oracle BAM Report viewsets and active viewsets in the Oracle BAM ADC for the Oracle BAM Report Server (in the Oracle BAM Web Applications set of components). It then caches the snapshot (in chunks) and the active data before sending it to the Oracle BAM Report Server. The Report Cache thus provides random access to the dashboard data. It also caches the change lists that are sent to the dashboards to allow recovery from lost Internet connectivity without reloading the dashboard.

- Event Engine: The Event Engine monitors for changes in data, time, or date. It

d t t h i l d t diti b d d fi d diti R l

detects changes in complex data conditions based on predefined conditions. Rules can include a series of conditions and actions attached to an event. The Event Engine continuously monitors the information in the ADC for certain conditions and executes the actions defined in the associated rules. The Message Center tracks the presence of users so that the dashboards and alerts are sent appropriately. Messages and dashboards can be delivered via email, instant messaging, and so on.

- Report Server: The Report Server is an application that runs on the web server. It

transforms the data it retrieves from the views, and according to their definitions, it generates dashboards. It maintains an open connection to the dashboards in order to stream changes to them based on changes it gets from the Report Cache. It pushes real-time data to dashboards that end users are currently viewing. 3. Dashboards and events: The analysis performed by Oracle BAM sends real-time

alerts dashboards and updates to Application Development Framework (ADF) pages alerts, dashboards, and updates to Application Development Framework (ADF) pages. In this architecture, everything is push-based, with the exception of reading data directly from tables in online transaction processing (OLTP) databases and data warehouses, for which you define external data objects. After a message is put in a data queue, Enterprise

Integration Framework processes constantly pull the data, transform it, and push it to the Active Data Cache. When there is a change in data, the ADC detects it and pushes the relevant information through the Report Cache or Report Server to the dashboards and

th h th E t E i l t

through the Event Engine as alerts.

Enterprise Integration Framework