XTMT (Axon Upload XT Migration Tech)

XTMT (Axon Upload XT Migration Tech) is a low-code or no-code solution to automate migration and integration scenarios to easily upload and sync files to Axon Evidence.

XTMT has been used by customers to script migrations of on-premise server data, as well as upload large, complex cases that require scalability and logging beyond the use cases of Upload XT itself. Upload time will vary depending on the number and size of files, and your organization's internet bandwidth. The number of files affects the performance more than total size. In one example, a single case containing 130,000 files across 4,000 folders totaling 2.7 TB was uploaded with XTMT running over a five-day period. However, a single 1 TB file might upload more quickly.

This document contains a link to XTMT, with an overview of what XTMT is and how it can be used. Additional information can be found in the articles Using XTMT and XTMT Tutorial.

Register for XTMT updates if you have not yet: https://forms.office.com/r/N5NufbJ9zC

XTMT overview

XTMT is a tool for evidence uploads for migrations and integrations that encapsulates all the API calls to the Axon Evidence platform, while providing robust retry support and logging to enable reliable migration of files. XTMT can upload files to Axon Evidence as individual evidence, or add the evidence to Cases which support folder hierarchies. Metadata such as ID and categories can also be set at time of upload.

The tool is a Command Line Interface (CLI) application for Windows that leverages the Upload XT service running on the device to perform upload operations. Each migration operation is assigned a name (for logging) and a folder path to upload, as well as optional settings that can be specified in an .XTO (JSON format) file, or directly from the command line with parameters.

As a CLI it enables flexible and powerful ingestion to Axon Evidence for scripting; using batch files, PowerShell, Python, etc. for migrations. In the sample case set included in the download, each case has a folder with the CFS number of the incident.

This could be programmatically crawled while parsing the naming convention to create a batch file that can run unattended for days to create new cases in Axon Evidence, set metadata, and upload the folder structure, as shown in this example:

Copy
xtmt.exe --operation "2022-migration-001" --path "x:\2022\CFS-2022-02-21-23"
  --case "2022-02-21-23" --evidenceID "CFS-2022-02-21-23" 
  --categories "Legacy" --createIfNewCase --autoRun
 
rem Use paramater short codes:
xtmt.exe -o "2022-migration-002" -p "x:\2022\CFS-2022-03-07-01" -c "2022-03-07-01"
  -e "CFS-2022-03-07-01" -t "Legacy" -n -a
xtmt.exe -o "2022-migration-003" -p "x:\2022\CFS-2022-09-27-02" -c "2022-09-27-02"
  -e "CFS-2022-09-27-02" -t "Legacy" -n -a

Each case would contain the path specified and any subfolders in Axon Evidence:

Downloading XTMT

XTMT is now included in the latest version download for Upload XT, which can be found on the Upload XT product page. You will have to sign in to MyAxon to see the download. The download includes the XTMT.exe CLI tool, documentation, sample operation files, and a .ZIP file of mock cases with test files to use to start using XTMT. These will also help you compare your experience with the expected outcomes in Axon Evidence.

Note

By default, the XTMT files are in the C:\Program Files (x86)\Axon Enterprise\Axon Evidence Upload XT v2\XTMT folder.

We recommend moving the files to a separate folder, for example, C:\XTMT, to ensure that log files generated are not deleted if Upload XT is uninstalled from the device.

Next steps

  1. Using XTMT - background and details about how to plan, run, and manage XTMT upload operations
  2. XTMT XTO Tutorials - step-by-step walkthrough using the included test evidence for a sample on-prem folder structure upload to Axon Evidence and best practices
  3. XTMT Command Line Tutorial - planning tips and example of PowerShell automation based on Excel-compatible (.tsv) input file of file paths, case information, and metadata to migrate