...
- Copy the exported zip file to a Kubernetes shared location.
- Open the restore.xml located at shared/migration/template/restore.xml.
- Provide the path of the zip file in the <SourceZipLoc> tag of the restore.xml as illustrated below.
- 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.
helm upgrade -i migration adeptia/migration -f adeptia/values.yaml -n <NAMESPACE>
Redeploy all the accelerators (the bundled accelerators, and the drivers).
As the server-configure.configure properties file doesn't exist in the microservices environment, the system generates a .csv file with the name Config_Report_name that helps you identify which all properties of server-configure.configure file properties file from AC v3.5 have been:
- Retained, renamed, and placed in the database.
- Embedded in the source code.
- Converted to environment variables, and placed in the values.yaml file. - mentioned in Config_Report_name
As the server-configure.properties file doesn't exist in the microservices environment, the system generates a .csv file with the name Config_Report_name that helps you identify the properties of server-configure.properties file from AC v3.5 have been:
- Converted to environment variables, and placed in the values.yaml file. - mentioned in Config_Report_name
The other properties related to the followings are handled as follows:
- Retained, renamed, placed in the database.
- Embedded in the source code.
| Info |
|---|
| The Config_Report_name file is created in parallel to the exported zip in shared location. |
...