Exporting service targets and agreements
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*
You can export service targets and agreements from the current AR System server to a new server. You don't need a password to export service targets.
When exporting a service target from the source AR System server to the destination server, a matching entry for the configure data source is important, especially the Field As Unique Identifier. The Field As Unique Identifier has to be the same on both source and destination server with the same application form. With the same Field As Unique Identifier, the service target can be imported without error and the correct filters are created.
Important
If you export Service Level Management agreements from a source server, the export file contains agreements and service targets related to those agreements. If you then export service targets separately and include some service targets that were exported along with the agreements, those service targets will appear in both export files. If you attempt to import the contents of both export files into the destination server, you might encounter index violation errors as the second import attempts to import service targets that already exist on the destination server. Therefore, make sure that you only export service targets that are not associated with an agreement.
Important
The Import/Export utility is not supported on Helix. Helix customers must use D2P for exporting and importing data.
In the File Path/Name field, enter the required path and the name for the file to which you want to export service targets, for example, c:/temp/filename.arx. The file is saved on the server where BMC SLM is installed.
Important
Ensure that the name and location of the .arx file specified in the File Path/Name, and the Log File Path/Name are different. If you use the same name, in some cases, the .arx file may not be created.