Databases Reference
In-Depth Information
Troubleshooting
the
BAM
applications
In this section, you will learn how to troubleshoot the BAM Active Data processing
issues and the issues around HA.
Troubleshooting the Active Data processing
issues
BAM uses the pushed-based mechanism to process Active Data. As illustrated in
the following diagram that you saw in Chapter 1 , the Active Data Cache produces
Active Data based on the ViewSet , and data changes in associated Data Ob-
jects. After that, the Active Data is sent to the Report Cache and then the Report
Server for processing:
Theoretically, Active Data processing could fail in any step of the flow (Active Data
Cache, Report Cache, Report Server, network, or JavaScript issues at the client
side). Therefore, in this section of troubleshooting, you will learn the guidelines to
test all these components for Active Data issues.
Troubleshooting Report Server issues
At the BAM Server side, Active Data is originally produced in the Active Data
Cache, and then pushed forward to the Report Cache and the Report Server.
The Report Server is the component that maintains the persistent HTTP con-
nections between the client and BAM Server, and pushes Active Data payloads
(ChangeLists) asynchronously to the client.
Search WWH ::




Custom Search