Troubleshooting

The main tool for troubleshooting import is logs. You can start with import.summary.log. It tells you what was the top-level import action (create, start or clean), against which ActiveMatrix Administrator and how many ActiveMatrix objects were processed.

The same information can be inferred from the post-build report if the import process was over. If the process is still going ON but you think it is not normal (taking too long), refer to import.antTarget.progress.log. Find out what was the last target that was started by import and which build and data file were in use. Start your investigation from there.

Sometimes, the import process has already completed with an error and you do not have a system to re-run it, then go through the exact execution steps found in import.admin.cmdline.log and try to piece together the exact chain of events that caused this failure. In import.admin.cmdline.log, you can find details of each action and you can find out what exactly caused this failure.

Sometimes, you want to get more information about the exact parameters passed to each ActiveMatrix Administrator task. To do this, update the property printAMXTaskAttributes in common.xml file to true or re-run the import process with -D option like this:

>ant -f build.xml clean -DprintAMXTaskAttributes=true

This command returns the following output for each ActiveMatrix Administrator task that gets executed. 
>ant -f build.xml runDataFileReport
Buildfile: <full_path_of>\build.xml
[propertyfile] Updating property file: <full_path_of>\import.summary.log

common.runDataFileReport:
     [echo] Running data file report to detect number of AMX objects found in data_files under [<full_path_of_export_folder>][total **/*_data.xml found :17]
[ImportDataFileReport] 02 Nov 2014 00:05:45  INFO - Total data files processing: 17
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - Object types found                 :In Data file
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - AMX environments : 2
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - AMX Nodes : 2
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - SOA Applications : 3
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - Hosts : 4
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - DAAs : 4
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - Log Appenders : 3
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - Global Substitution Variables :2
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - Global Resource Templates   : 8
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - Top Level Permissions :2
[ImportDataFileReport] 02 Nov 2014 00:05:46  INFO - ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

runDataFileReport:

BUILD SUCCESSFUL
Total time: 4 seconds

Sometimes, the actual cause of failure is not in any of these log files but can be found in the target ActiveMatrix Administrator's log (SystemNode.log). So, you might have to start the investigation from there.