Databases Reference
In-Depth Information
Chapter 9. Troubleshooting
your
BAM Applications
In a typical business flow in BAM, business data moves from various upstream
data sources to Oracle BAM, which internally processes and pushes the data to
IE browsers for report rendering. As different technologies and BAM Server com-
ponents are involved, it could be time-consuming and challenging to identify and
solve the problem if anything goes wrong in this flow.
As different issues can happen in different product areas and contexts, it is im-
practical to address all these issues in one chapter. Thus, rather than focusing
on the individual issues and the resolutions, the objective of this chapter is to in-
troduce the methodologies for troubleshooting common BAM issues, and provide
useful guidelines that can help you to analyze and figure out your own solutions.
To illustrate the BAM troubleshooting methodologies and techniques, we will take
a look at case studies.
In this chapter, the following topics will be covered:
•
Methodologies for troubleshooting Oracle BAM
•
Troubleshooting Active Data processing
•
Troubleshooting BAM HA issues
Understanding
BAM
logging
and
troubleshooting methodologies
In many cases, enabling BAM logging is the prerequisite for troubleshooting BAM
issues. It is critical to set up the correct loggers to appropriate levels (for example,
SEVERE, WARNING, INFO, CONFIG, FINE, FINER
, and
FINEST)
, so that
you can collect the information to identify the actual problem, and determine the
root cause.
