After you've created downloaded the exportExport.zip file containing the EDI Transactions, you can import the objects them by using the Import Package option under Solution Promotion feature at the target environment. A successful import completes the migration process, and you'll be able to access all the objects in your new environment.
...
Property name | Description |
migration.job.cpu.request | Number of minimum CPU cores allocated to a migration pod in the deployment. |
migration.job.cpu.limit | Number of maximum CPU cores a migration pod can use. |
migration.job.memory.request | Minimum memory allocated to a migration pod. |
migration.job.memory.limit | Maximum memory a migration pod can use. |
migration.job.jvmParameters | Value for JVM parameters required for migration. |
migration.job.pendingStatus.checkInterval | The frequency (time interval in seconds) at which the system checks for the status of the migration job. |
exportzip.path | Path of the export.zip file created while generating the export package. Default value: migration/export/export-$TIMESTAMP$.zip |
migration.job.pendingStatus.waitingPeriod | The time period (in seconds) for which the system checks for the migration job to get up and running. |
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
Go to this location to view the details of migration helm package.
Add migration repo using the following command:
Code Block helm repo add adeptia-connect-migration https://adeptia.github.io/adeptia-connect-migration/charts/
Click DEFAULT VALUES 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.
...