Importing Data to TIBCO ActiveMatrix Administrator
Unzip the exported archive file and run the ant command from the root of the unzipped folder:
> ant create
There are three ant targets create, start and clean as a part of import.
You can run ant create from the root of the unzipped exported data folder. As described in the Export archive directory structure, there is a top level build.xml file. Ant by default looks for the build.xml file if you run it without specifying any build file (with -f option).
| Target Name | Description |
|---|---|
| create |
This target is solely responsible for doing ‘Import’. Once the target is run successfully, you get your data that was exported back in the provided target ActiveMatrix Administrator enterprise. If you run it from the root of exported data folder, it starts recreating all the ActiveMatrix objects that are found in the exported data folder. It discovers the build files and starts running create target from that file and so on. Every time this target runs, it discovers the build files and runs them in a specific order. Before you run this target, you can delete top level folders or files in it and those objects are excluded from the import process. Each of the build files (either build.xml or *_build.xml) you find in this exported data folder has the same structure. In addition, each build.xml file in a different location (under the top folders or sub folders) can discover the appropriate build file needed for that level. This enables users to run import from a different level giving control to user where they want to create everything in the exported data folder subset of them. |
| start |
Once an ActiveMatrix object has been created, you can run this target and it starts all the objects that can be started. For example, Node. It is first installed and then started or Application is first deployed and then started. The ‘create’ target does the actual import. The start target is just a helper target. You need not use it to start all ActiveMatrix objects; you can optionally login to ActiveMatrix Administrator and start each object manually or through the ActiveMatrix Administrator CLI scripts. If you do not want to start certain objects (like all the nodes in one Environment) you can delete or move those files out of this export data folder. Similar to ’create’, you can run start target from any build.xml or *_build.xml from any sub folders giving you control on what AMX objects you want to start. |
| clean |
Deletes Applications, Nodes, and then deletes the Environment. You must be very careful when you use this target because of its destructive nature. As a security measure, you are prompted before the deletion. Reply with a “y” to confirm. If you do not want to be prompted, run the script with the target “noprompt”: > ant noprompt clean (useful for automation) If you use the ‘dryRun’ target, it runs the script as if it is processing all the clean targets but does not actually send a delete command to the ActiveMatrix Administrator. > ant dryRun clean After the dryRun finishes its processing, you can review the output in a file called ‘import.admin.cmdline.log’. After you are satisfied with the data that was selected for deletion, you can re-run the clean target but this time without the ‘dryRun’ target. Similar to ‘create’ and ‘start’, you can run clean target also from any build.xml or *_build.xml file from any of the sub folder giving you control on exactly what ActiveMatrix objects you want to delete or clean. |