Using the Import Export Console
Deployment managers can use the Import Export console to perform data migration for the following processes:
|To export BMC Service Request Management objects and data||Exporting from the Import Export Console|
|To import BMC Service Request Management objects and data||Importing data from the Import Export Console|
For the following data import options:
|Import data options|
|Viewing the history of imports and exports|
The following video describes the import export process for SRDs.
The video is referring to an older version and you might observe some changes in the procedure.
To migrate data with the Import Export Console
Before you begin, ensure that you have the Request Catalog Manager and Remedy AR System Administrator permissions.
The Import Export Console handles only certain kinds of BMC Service Request Management objects and data, as explained in the Objects and data that are migrated section in Migrating BMC Service Request Management objects and data.
If the data migration fails, ensure that the kettle.properties file does not contain any user credentials that do not have the required permission to perform the job. You can comment out the AR_USER and AR_PASS fields in the kettle.properties file before running the job and then uncomment the fields after the job is complete. The kettle.properties file is available on the AR System server installation location. The default location on Windows is: C:\Program Files\BMC Software\ARSystem\diserver\.kettle.
- Prepare your destination server.
This step migrates objects and data that are used by BMC Service Request Management, but are not handled by the Import Export Console.
Export selected service request definitions (SRDs), process definition templates (PDTs), and supporting data from the source server.
To perform this step, use the Import Export Console, as explained in Exporting SRDs, PDTS, and supporting data. The export process creates an .zip file and attachments folder (containing images).
- Import SRDs, PDTs, and supporting data to the destination server.
Use the .zip file created in Step 2 to perform the steps in the Import Export Console. For more information, see Importing data from the Import Export Console.