NoPublic, bureaucrat, administrator
1,068
edits
Changes
no edit summary
A log with all the steps is written in this window as the generation process goes on. This might take some time, depending on the size of the source IMSMA database. The range is from very few minutes up to two hours for very big databases. Once the generation is finished, the newly generated staging area database can be explored with a database query tool such as ''pgAdmin3'' or ''Navicat'', and reporting tools can be connected to it.
==Changing the log level of the Staging Area Generator==__NOEDITSECTION__
In order to change the log level of the SAG, for example to write a more detailed output to the log file (etl.log in C:\IMSMAETLTool), the following steps are required:
# Open a command line window and go to C:\IMSMAETLTool\bin
# Extract the configuration file by typing the following in the command line: <pre> C:\IMSMAETLTool\jdk1.6.0_45\bin\jar xf etl-1.0-jar-with-dependencies.jar mylog4j.properties </pre>
# Open the resulting file mylog4j.properties (in C:\IMSMAETLTool\bin) in an editor (e.g. Notepad++)
# Change the line <pre> log4j.category.com.fgm=INFO </pre> to <pre> log4j.category.com.fgm=DEBUG </pre>
# Bundle the log file in the jar again by typing the following in the command line: <pre> C:\IMSMAETLTool\jdk1.6.0_45\bin\jar uf etl-1.0-jar-with-dependencies.jar mylog4j.properties </pre>
More output is now written to the '''etl.log''' file.
{{Note|This is only required in case of doubt/error, when more details are needed in order to investigate what goes wrong.}}
==Scheduling the Staging Area creation==__NOEDITSECTION__
The above described generation of a staging area needs human interaction. However, once all the options are fixed, there might be the requirement to re-generate the staging area regularly, in order to have an up-to-date reporting database. It is possible to automatize the staging area generation by following these steps: