Database Reference
In-Depth Information
high usability, together with the fact that there are no complex SOA patterns associated
with this product alone, simplifies our task by presenting this functionality in this para-
graph, as we do not have room here for providing drag-and-drop cookbook screenshot
demonstrations.
If you return to the figure that presents the WLS SOA console in OFM's introductory
chapter for a moment, you will see that simplicity starts with the combined installation of
SOA Suite, where the BAM server will be installed in one go, with the whole bundle (of
course, you can exclude it from the installation).
It runs on its own WebLogic server (in our case,
bam_server1
by default), and it is
controlled from the same administration console/OFM control in the same way as other
servers are controlled. The Oracle BAM server is a collection of the components Oracle
BAM Active Data Cache (Oracle BAM ADC), Oracle BAM Report Cache, Oracle BAM
Enterprise Message Sources (EMS), and Oracle BAM Event Engine. All BAM object
definitions and reports will be stored in the OFM DB repository, created during the install-
ation. As long as object data is involved, we have two sides of BAM connectivity; natur-
ally, it has APIs for data producers (SOAP and RMI) and data consumers, who will use
the BAM DB schema, like with ODI. In fact, Oracle Data Integrator can be both; a data
provider for reporting and data consumer of BI data.
When you start
bam_server
and log in to the BAM web application,
ht-
tp://<your_BAM_host>:<your_BAM_port>/OracleBAM/default.htm
,
you will see four main buttons that lead to the console responsible for all aspects of the
BAM dashboard's life cycle. The architect's console is the most interesting to us, as its
name denotes. The architect's console is responsible for creating BAM data objects on
which all our reports will be based. Every type of BAM and OFM integration will start
from this console. Let's quickly walk through the possible BAM integration use cases.
Search WWH ::
Custom Search