1. Application analysts, working with their Epic coun- production
terparts, create and schedule reports in the
operational database envi-
ronment
2. Application analysts, working with their Epic counter- reporting
parts, create and schedule reports in the production
operational database environment. The build is then
replicated to the operational data-
base environment.
3. When a report is scheduled to run it is created by the reporting
environment.
4. When a report is scheduled to run it is created by the comcli.pl
reporting environment. The build references an EPR
which calls downtimerpt.pl, which is a symbolic link
to .
5. is referenced by comcli.pl to know where comcli.conf
and how to transfer the report.
6. downtimerpt.pl then routes through a load balancer
and transfers the report to one of the BCA server's
Incoming folders, usually using FTP.
7. From BCA server's Incoming folder, a service associ- Interconnect
ated with a BCA instance of , running
on each BCA server, picks up the report.
8. A service associated with a BCA instance of Intercon- global
nect, running on each BCA server, picks up the report.
The BCA Interconnect service encrypts the report and
then updates a BCA in the production opera-
tional database environment.
9. A service associated with a BCA instance of Intercon- production
nect, running on each BCA server, picks up the report.
The BCA Interconnect service encrypts the report and
1/2