Databases Reference
In-Depth Information
Understanding
the
key
terminologies
and
the
BAM
architecture
Understanding the key terminologies and the BAM architecture is a prerequisite
for troubleshooting the BAM applications. The key terminologies for BAM include
Active Data, Active Data Cache, Report Cache, Report Server, ChangeList,
Data Objects, Report, and so on. For more information about these concepts,
Identifying the problem
Different issues may require different techniques to troubleshoot. For example,
for a report design issue (for example, calculated fields do not show correct val-
ues), you should focus on the building blocks for the report design, instead of
enabling loggings for the BAM server, which does not provide any help at all.
A BAM issue typically falls into the following categories:
•
Report design and report loading (static rendering)
•
Report rendering with Active Data (Active Data processing)
•
Issues with the key BAM Server components (Active Data Cache, securities,
Report Cache, and Event Engine)
•
BAM Web applications (Active Viewer, Active Studio, Architect, Administrat-
or, and Report Server)
•
Issues with BAM Integration Framework (EMS, Web services APIs, SOA
Suite integration, and ODI integration)
To fully identify a problem, you need to first understand the problem description
and the category to which the issue belongs. Then, you can gather relevant in-
formation, such as the time frame of when the issue happened, the BAM Server
release information and patch level, BAM deployment topologies (single node or
HA), and so on.
