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, 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.

To import objects:

Copy the import.xml file PVC shared location <shared>/migration/template, and paste it to another folder.
For example, shared/migration/custom/import.xml.

Provide values for the following environment variables in values.yaml file for migration as shown in the table below.

Environment Variable	Value		Description
SHARED_PATH	/shared		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	shared/migration/<custom>/import.xml		Path of the import.xml in PVC.

Environment Variable	Value for Azure SQL Database	Value for Oracle Database	Description
BACKEND_DB_URL	jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>	jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>	URL of the backend database server.
BACKEND_DB_USERNAME	<User defined>	<User defined>	Username of your backend database server.
BACKEND_DB_PASSWORD	<User defined>	<User defined>	Password for your backend database server.
BACKEND_DB_DRIVER_CLASS	com.microsoft.sqlserver.jdbc.SQLServerDriver	oracle.jdbc.OracleDriver	Backend database driver class name.
BACKEND_DB_TYPE	SQL-server	Oracle	Type of the backend database server.

Provide the values for the following environment variables too in values.yaml file for migration. These values will override the values for the corresponding tags in import.xml file.

Environment Variable	Value	Description
OPERATION	import	The type of operation for which deployment will be performed. If you do not provide a value for this environment variable, you need to set the value for the operation attribute in the import.xml file.
SOURCE_ZIP_PATH	/shared/<migrationtest1/SA_PF.zip>	Path of the exported ZIP in the PVC. If you do not provide a value for this environment variable, you need to set the value for the SourceZipLoc tag in the import.xml file.
OVERRIDE_USER	<'IndigoUser:127000000001107055536473900001'>	User Id, Entity Id, or Type Id of the user with which all objects will be deployed. Enter the value in single quotes. If you do not provide a value for this environment variable, you need to set the value for the OverrideUser tag in the import.xml file.
OVERRIDE_MODIFIEDBY_USER	<'IndigoUser:127000000001107055536473900001'>	User Id, Entity Id, or Type Id of the user which will be reflected in the modified by field of every activity after the deployment. Enter the value in single quotes. If you do not provide a value for this environment variable, you need to set the value for the OverrideModifiedByUser tag in the import.xml file.
RETAIN_XML_PATH	/shared/<migrationtest1/retain.xml>	Path of the retain XML file in the PVC. If you do not provide a value for this environment variable, you need to set the value for the RetainXmlLocation tag in the import.xml file.
LOG_IDENTIFIER	<LogID_1>	Log identifier to capture logs from MS environment. If you do not provide a value for this environment variable, the name of exported zip file will be used as the value for the log identifier.
ROLLBACK_ZIP_PATH	/shared/<Rollback_SA_PF.zip>	Path in the PVC where you want to keep the rollback zip. If you do not wish to provide a value for this environment variable in the values.yaml file, you can set the value for the RollbackZipLoc tag in the import.xml file. If you neither specify this value in the values.yaml file nor provide it in the import xml file: The system creates the rollback zip file at the location where your exported zip is created in the PVC. The format of rollback zip file name will be Rollback_<name of the exported zip file>.

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

Before running this command, ensure that you have taken the backup for the migration files. This backup will help you restore the changes you may have made in those files before migration. Why do we need a backup if we are already using the copies of migration files?
```
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.

Rolling back the import operation

If you decide upon rolling back the import operation, you need to follow the instructions given below.

Provide the values for the following environment variables in values.yaml file for migration. These values will override the values for the corresponding tags in import.xml file.

Environment Variable	Value	Description
OPERATION	rollback	The type of operation for which deployment will be performed.
SOURCE_ZIP_PATH	/shared/<Rollback_SA_PF.zip>	Path of the rollback zip in the PVC. If you do not provide a value for this environment variable, you need to set the value for the SourceZipLoc tag in the import.xml file.

Navigate to the migration directory, and run the below command to perform the rollback operation.

Before running this command, ensure that you have taken the backup for the migration files. This backup will help you restore the changes you may have made in those files before migration. Why do we need a backup if we are already using the copies of migration files?
```
helm install migration adeptia-connect-migration/migration -f <Path of the values.yaml>
```
RetainXmlLocation, OverRideuser, and OverrideModifiedByuser parameters are not applicable in case of rollback.