After you've downloaded the Export.zip file containing the EDI Transactions, you can import 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.
| Tip |
|---|
You may want to configure the solution promotion properties described in the Solution Promotion Configuration section on the Microservice Settings - Webrunner page before you begin the import operation |
...
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.
...
. |
...
...
migration.job.pendingStatus.waitingPeriod
...
The time period (in seconds) for which the system checks for the migration job to get up and running.
Prerequisite
Make sure that you have the required permissions to view and use the Solution Promotion feature. To have this permission, the role that you have been assigned must have the required permissions on the Solution Import entity. To know more, refer to the documents Creating a Role and Permission model.
Ensure that you have followed the migration prerequisites mentioned on this page.
...
Click Account > Tools > Solution Promotion
On the left panel, select Import Packages.
Click CREATE Import Package
On the Create Import Package screen,
Provide a name for the import package.
Provide a description for the import package.
In the Select Project field, select the project where you want to keep the import package.
In the Override User field, select the user to whom you want to provide ownership of the activities.
In the Override Modified By User field, select the user who will be reflected in the Modified By field of every activity after the deployment.
Select the Retain Activities checkbox if you want to retain the services at the target environment, and then click Browse to select the required Retain XML file.
Select the Solution Database checkbox if you want to import data to the solution database to be specified in the next screen.
If you have selected Solution Database checkbox, continue following the steps from step 6, else perform step 5.
If you have not selected any of the checkboxes (Retain Activities or Solution Database), or selected only the Retain Activities checkbox, perform step 5, else perform the steps from step 6.
Click Save & Exit.
Click Continue.
In the Database Info section, provide the following details of the solution database to which you want to import data.
Type - Enter the type of database. For example MySQL, SQL, etc.
Server - Enter the hostname of the database server.
Port - Enter the port number of the database server.
Name - Enter the name of the database.
Username - Enter the username to access the database.
Password - Enter the password to access the database.Click Save & Exit. This creates the import package that gets listed in the Import Packages mange page.
Click More under ACTION against the package, and then click Import Package.
On the Import Package screen, click Browse to select the Export ZIP file.
Click Import.
This imports the objects to the target environment and also creates a corresponding Rollback ZIP that can be used to rollback the import operation. You can visit the Dashboard to view the details of the import operation.You can also perform the following actions on the package from its More menu under ACTION:
Perform the rollback operation.
Edit, delete, or view the import package.
...
| Anchor | ||||
|---|---|---|---|---|
|
...
If you decide upon rolling back the import operation, you need to follow the instructions given below.
Download the Rollback ZIP file corresponding to the import package from the Dashboard by navigating as follows:
Dashboard > Solution Promotion > More > Rollback ZIP
Go to the Import Packages manage page by navigating as follows:
Account > Tools > Solution Promotion > Import PackagesClick More under ACTION against the import package, and then click Rollback.
On the Rollback screen, click Browse to select the Rollback ZIP you have downloaded in step 1.
Click Rollback.
This rolls back the import operation. You can go to Dashboard > Solution Promotion to see the details of the rollback operation.
...
Related pages
...
.
...
Deploying in AC 4.x
To deploy the EDI accelerators, follow the steps given below:
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.
...
Variable/Property
...
Value
...
BACKEND_DB_URL
...
<URL of the backend database server>
jdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>
jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>
...
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 folder that contains the accelerator>.
5. Navigate to the migration directory, and run the below command to install the accelerator.
| Code Block |
|---|
helm upgrade -i migration adeptia/migration -f adeptia/values.yaml -n <NAMESPACE> |
...