Importing Objects

After you've created the export.zip file, you can import the objects using import.xml file. A successful import completes the migration process, and you'll be able to access all the objects in your new environment. 

If you want to retain the activities while importing the objects then you need to configure the parameters in the retain.xml that you want to retain. The objects can be retained at service and field level. You will find retain.xml in the $SHARED_PATH$/migration/template folder. For more information, refer to Structure of Retain XML.

To import objects:

1. Copy the import.xml file from shared repository $SHARED_PATH$/migration/template and paste at $SHARED_PATH$/migration/custom location.

   $SHARED_PATH$ is an environment variable that contains the configured shared path.
2. Open import.xml in a text editor and do the followings.

   1. Type the location of the export zip file that you want to import in the <SourceZipLoc>.

      

   2. Type the location of “retain.xml” file in the <RetainXMlLocation>. 

   3. Enter the User Id of the user to whom you want to provide the ownership of the objects that you are deploying from the Source environment in the <OverrideUser>.
   4. Save the file.

3. Provide values for the following properties and environment variables in values.yaml file as shown in the table below.

   Variable/Property	Value
   BACKEND_DB_URL	<URL of the backend database server>
   BACKEND_DB_USERNAME	<Username of your backend database server>
   BACKEND_DB_PASSWORD	<Password for your backend database server>
   BACKEND_DB_DRIVER_CLASS	<Backend database driver class name>
   BACKEND_DB_TYPE	<Type of the backend database server. (for example, SQL-server)>
   SHARED_PATH	<environment variable that contains the configured shared path. (for example, /shared)>
   MIGRATION_XML_FILE_PATH	<Path of the import.xml. (for example, ${SHARED_PATH}$/migration/custom/import.xml)>
   image.pullSecret.registry	<URL of the repository>
   volumes.claimName	<Name of the PV claim>
   Infra.secret	<Name of the Secret>

   
   

4. Navigate to the migration directory, and run the below command to import the objects.

   helm upgrade -i migration adeptia/migration -f adeptia/values.yaml -n <NAMESPACE>

   The Migration job does not get deleted automatically after the migration is complete. You need to manually delete it before you start a new migration process.