You start a load process by using a project in BIRT Analytics Loader. Before running a project, you must create the data source connections and define the loading transactions and the data transformation scripts. To make the loaded data available to the BIRT Analytics users, you must synchronize the loaded database with the active database and grant access privileges to database users.
After defining the table mappings and all transactions in a load process, you can run the project to load the data. You can run a single or multiple transaction processes. You can run a process with or without data transformation.
The load process loads the data in the FastDB database, the same database that users analyze. To avoid inaccurate analysis, consider loading data when users are not logged in to the system.
To prevent user access to databases while a load process runs, stop the web server running the BIRT Analytics application. Alternatively, schedule the loading process to run at a time when users are offline. For more information on how to schedule a load process, check Administering BIRT Loader.
Stopping the Tomcat service
BIRT Analytics installs on Tomcat Apache. To prevent end users from logging in to BIRT Analytics, stop the web server on which BIRT Analytics runs, using either a command‑line editor or Windows Services.
Stopping using Services
You use Services to stop, start, or restart a service.
Running a project
To run a loading project, you must choose Run, as shown in Figure 2‑8.
Figure 2‑8 Running MyFirstProject
In the message that confirms whether you want to run the project, choose Yes. A list of database table names and the number of records loaded into each table appears in Running project, as shown in Figure 2‑9.
Figure 2‑9 Running project log
The Running project log provides information about the tables into which the data is loaded, and the number of the records that are loaded. In the log viewer, standard message text is in black print, INFO messages in green and Error messages in red. The stack trace shows the line of script where the error was generated.
To limit the number of message lines in the log, set a number of records for which a log entry is created, in Options—Notify. For loading processes requiring a long time, choose Run in background, to minimize the Running project window. You can work on a different project until the running project finishes.
Using reports
To browse through the generated log files, select Reports from the control menu. The list of reports appear in Executions, as shown in Figure 2‑10. Date displays a date and time when a project is executed. State displays the generation status. After selecting a date, the log content appears in Detail.
