Deploying EDI solutions

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.

You may want to configure the following 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.memory.limit	Maximum memory a migration pod can use.
migration.job.memory.request	Minimum memory allocated to a migration pod.
migration.job.cpu.limit	Number of maximum CPU cores a migration pod can use.
migration.job.cpu.request	Number of minimum CPU cores allocated to a migration pod in the deployment.
exportzip.path	Path of the export.zip file created while generating the export package. Default value: migration/export/export-$TIMESTAMP$.zip
migration.job.pendingStatus.checkInterval	The frequency (time interval in seconds) at which the system checks for the status of the migration job.
migration.job.pendingStatus.waitingPeriod	The time period (in seconds) for which the system checks for the migration job to get up and running.
migration.job.jvmParameters	Value for JVM parameters required for migration.

Prerequisites

Before you perform the Solution Promotion steps for import, you need to make sure that you have met the prerequisites discussed in this section.

You need to make sure that you have:
1. The access to the source Kubernetes environment where the application is installed.
2. Installed the followings:
  1. Helm
  2. kubectl client
3. The Export ZIP file ready.
4. The Retain XML file ready if you want to retain any activity.

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.

Important
If you ever make any changes to the resources in the migration values.yaml file, you need to change the JVM parameters accordingly through the environment variable JAVA_OPTS – It can be up to 70% of the allocated resources.

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.

ENTITIES	Permissions
	VIEW TAB\LINK	LIST & READ	CREATE	EDIT	EXECUTE
Solution Import	View the tabs/links on the Import Package manage page	View	Create the Import Package	Edit the Import Package	Import Package Rollback Package

Ensure that you have followed the migration prerequisites mentioned on this page.

You can import the objects by following the steps given below.

Click Account > Tools > Solution Promotion
On the left panel, select Import Packages.
Click CREATE Import Package
On the Create Import Package screen,
1. Provide a name for the import package.
2. Provide a description for the import package.
3. In the Select Project field, select the project where you want to keep the import package.
4. In the Override User field, select the user to whom you want to provide ownership of the activities.
5. 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.
6. 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.
7. Select the Solution Database checkbox if you want to import data to the solution database to be specified in the next screen.
8. If you have selected Solution Database checkbox, continue following the steps from step 6, else perform step 5.
9. 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.

Rolling back the import operation

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 Packages
Click 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.