Once you have created the zip file containing the exported objects, you can use it to restore the objects in the AC v4.0 environment. To restore the objects, perform the following steps.
- Copy the exported zip file to a Kubernetes shared location in the PVC.
Open the restore.xml located at <shared>/migration/template/restore.xml.
Info shared is the folder created at the root level in the PVC when you deploy Adeptia Connect. - Provide the path of the exported zip file in the <SourceZipLoc> tag of the restore.xml as illustrated below.
- Go to migration 4.0.0 · adeptiainc/adeptia-connect-migration (artifacthub.io) to view the details of migration helm package.
Add migration repo using following command:
Code Block language css theme Midnight helm repo add adeptia-connect-migration https://adeptia.github.io/adeptia-connect-migration/charts/Click DEFAULT VALUES to download the values.yaml file.
- Open the values.yaml file.
- Enter the path of the restore.xml file in the environment variable MIGRATION_XML_FILE_PATH.
Run the following command to restore the objects.
Code Block language css theme Midnight helm upgradeinstall -i migration adeptia-connect-migration/migration -f adeptia/values.yaml -n <NAMESPACE> <Path of the values.yaml>
Info A variable from the AC v3.x environment is available as an environment variable in AC v4.x environment. Once the migration has completed successfully, you need to manually update the values for the environment variables in the values.yaml file for the respective microservice. For example, the values of the variables from the AC v3.x ldapConfiguration.xml file need to be manually updated in the values.yaml file for the portal microservice. Restart all the running pods.
Redeploy all the accelerators (the bundled accelerators, and the drivers).
...
Some of the properties have become environment variables.
Info You can find the list of these environment variables in a .csv file that is generated by the system after performing the restore operation. You can refer to this file to make the changes in the values of these environment variables (converted properties) in values.yaml file. The file is created with the name Config_Report_<name of the exported ZIP>. This file is created in the same folder where the exported ZIP file is located in the PVC. following is an excerpt from the file. 
- Some properties are moved to database with the same name or different names.
- A few properties are deleted.
- The remaining ones are hard-coded in Some of the properties have been handled internally by the application.