Logging for Import
| Log file name | Description |
|---|---|
| admincmdline.log |
This file is a standard log4j style log file that ActiveMatrix Administrator ANT task produces. This file does not reset on each new run; it appends to the existing file. For its log4j settings, refer to file found at <TIBCO_HOME> administrator\<version>\samples\admin_cmdline_logging.properties. |
| import.admin.cmdline.log |
This file is a capture of console – that mans any import targets you run via ant is captured here. This file can be useful when user want to see what exactly has happened during import phase. The ‘create’ target of import tends to run (scroll) quite fast and does not give user enough time to observe what is happening – so going over this file at a latter stage gives user chance to study exactly what happened. This file also keeps appending data to it. Each run is delimited with lines like this:
============================================================================ [timestamp] Start of CLI action from [<full_location_of>\build.xml] ============================================================================ |
| import.antTarget.progress.log |
This file logs each ant target, it’s start and end time stamp, from what build file and data file that target was ran and was working on what AMX object (its name) This file also keeps appending data to it. Each run is delimited with lines like this:
============================================================================ [timestamp] Start of CLI action from [<full_location_of>\build.xml] ============================================================================ Below is sample output that you will find in this log. Looking at the sample, we can see that was running “clean” target. It first started cleaning the environment that lead to clean of application followed by node clean. You can also find out from what build file each action started and what was data file for that. Also it happens to be case where task ended up in failure so you see that too. If it had finished successfully you will see word “Finished” instead of “Failed” in below output. |
Sample output:
[timestamp] [Started.Environment.clean] [MyEnvironment] from build file : [\env_build.xml] data file : [\env_data.xml] [timestamp] [Started.Application.clean] [MyApp] from build file : [2\3_MyApp.app_build.xml] data file : [\3_MyApp.app_data.xml] [timestamp] [Failed.Application.clean] [MyApp] from build file : [2\3_MyApp.app_build.xml] data file : [\3_MyApp.app_data.xml] [timestamp] [Started.Application.clean] [MyApp2] from build file : [\2_MyApp2.app_build.xml] data file : [\2_MyApp2.app_data.xml] [timestamp] [Failed.Application.clean] [MyApp2] from build file : [\2_MyApp2.app_build.xml] data file : [\2_MyApp2.app_data.xml] [timestamp] [Started.Application.clean] [MyApp3] from build file : [\Apps\1_MyApp3.app_build.xml] data file : [\1_MyApp3.app_data.xml] [timestamp] [Failed.Application.clean] [MyApp3] from build file : [\Apps\1_MyApp3.app_build.xml] data file : [\1_MyApp3.app_data.xml] [timestamp] [Started.Node.clean] [Node7] from build file : [\Nodes\node7.node_build.xml] data file : [\node7.node_data.xml] [timestamp] [Failed.Node.clean] [Node7] from build file : [\Nodes\node7.node_build.xml] data file : [\node7.node_data.xml] [timestamp] [Failed.Environment.clean] [MyEnvironment] from build file : [\env_build.xml] data file : [\env_data.xml] |
|
| import.summary.log |
Just like Export.report.txt this file is report but for import process. Once import is finished you will find pertinent information regarding import in this file – like What was top level target (that is, create, start, and so on). What was final outcome of build (success or failure) What was target ActiveMatrix Administrator’s information What time import started and ended How long it took to finished (duration) What were the import options (that is, import.upgrade.apps=false) For each ActiveMatrix object that was processed during import you will also find What were their names (comma separated) How many of them we processed |