Importing the select AC v3.x activities

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 exported objects in your new environment.

If you want to retain the activities while importing the objects, 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>/migration/template folder. For more information, refer to Structure of Retain XML.

Pre-requisite

Ensure that you have followed the required steps to avoid the creation of rollback zip file while importing the objects at the target.

Important

If you ever make any changes to the resources in the migration values.yaml file, you need to change the JVM parameters accordingly through the environment variable JAVA_OPTS – It can be up to 70% of the allocated resources.

Steps to import the objects

Copy the exported zip file to a Kubernetes shared location in the PVC.
Copy the import.xml file from PVC shared location <shared>/migration/template, and paste it to another folder.
For example, shared/migration/custom/import.xml.
Open import.xml in a text editor and do the followings.
1. In the <SourceZipLoc>, type the location (shared path of exported zip file in PVC) of the exported zip file that you want to import.
2. Type the location of retain.xml file in the <RetainXMlLocation>.
3. In the <OverrideUser>, enter the User Id of an IT user to whom you want to provide the ownership of the objects that you are deploying from the source environment.
  Important!
  
  In case of AC v4.1.3, apart from an IT user, you can also enter the User Id of any Admin user while importing the User type of objects from one environment to the other.
4. Add <CreateRecovery>false</CreateRecovery> tag to disable the creation of rollback zip.
  
  Alternatively, you can set the environment variable RECOVERY_ENABLED to false in the values.yaml file.
5. Save the file.
Go to migration helm artifactHUB repository.
Select the appropriate version of the helm chart to view the details of migration helm package.

Add migration repo using following command:

helm repo add adeptia-connect-migration https://adeptia.github.io/adeptia-connect-migration/charts/

Click DEFAULT VALUES.
On the Default values screen, click to download the values.yaml file.

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 in the values.yaml file that contains the configured shared path> The default value for this variable is /shared. This is the folder created at the root level in the PVC when you deploy Adeptia Connect.
MIGRATION_XML_FILE_PATH	<Path of the import.xml in PVC> For example, shared/migration/custom/import.xml.
RECOVERY_ENABLED	true (default).

Navigate to the migration directory, and run the below command to import the objects.
```
helm install migration adeptia-connect-migration/migration -f <Path of the values.yaml>
```
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.