Import/Restore

Steps for offline migration (Import/Restore)

Select the Import/Retain radio button on the Offline Actions screen and click Next. This displays the Import Actions screen (see Figure 51).

Figure 51: Import Actions screen
This screen displays the Import migration actions, which are outlined in the table below.
Table 6: Import Actions

Action	Description
All	Migrates Database object, Data Files and configuration file. Database Objects includes Activities, Process Flows, Users and Groups etc. Data Files includes Data Dictionary XSDs, Custom Methods and WSDL etc. Configuration Files includes Server-Configure.Properties, and Launcher.properties etc. If you select All and click Next, two options are displayed. Those options are given below: Skip Configuration File: Select this option if you want to migrate only Database Objects and Data Files and not the Configuration Files. Include Configuration Files: Select this option if you want to migrate all Database Objects, Data Files and Configuration Files.
Only Database	Migrates only Database objects. Data Files and Configuration file are not migrated using this option.
Only Configuration File	Migrates only Configuration Files. Database Objects and Data Files are not migrated using this option.

In case you have selected WebSphere Build, you can only use Only Database option.

Select the required option and click Next. This displays the Select Source Data Location screen (see Figure 52).

Figure 52: Select Source Location

Click Browse to select the zip file created in the Export process and click Next. The Select Target Location screen is displayed (see Figure 53).

Figure 53: Select Target System Install Directory

Click Browse to select the directory, where the target system of the Adeptia Server is installed and click Next, for example, C:\Program Files\AdeptiaSuite \AdeptiaSuite-6.1\ AdeptiaServer.

In case you have selected WebSphere Build, you need to select the AdeptiaSharedLibrary folder in the above step.

Screen which is displayed next depends on the option that you have selected in Select Action screen.
1. In case you have select All, all objects are deployed at the target environment.
2. In case you have selected Only Database option, then the next screen displays the list of all the tables of the Adeptia Server (see Figure 54).

Figure 54: Select Objects Screen

Select the checkbox(s) against the objects that you want to restore.
You can select one or more objects.

All objects that are prefixed with ABPM are quartz tables. These tables and the dt_properties objects are listed in case of the SQL Server database. It is recommended not to restore these objects as the migration process is likely to fail in such a case, as all tables in the source and target databases should be the same. If they are different then deselect the log objects such as (AU_Log and AU_TransactionData) as it slows down the migration process.

You need to be careful while migrating objects, as if an error occurs, it cannot be undone. Additionally, if the migration process fails, you have to rollback the entire operation.

1. In case you select Only Configuration Files option then the next screen displays the list of all the configuration files for all objects of the Adeptia Server. (See Figure 55)

Figure 55: Select Configuration Files

Select the checkbox(s) against the files that you want to restore.
You can select one or more files.

Click Next. This displays the View Restore Logs screen (see Figure 56).

Figure 56: View Restore Logs
This screen displays all logs and confirms whether the import operation is successful or not. If it is successful, a message stating, "Selected database tables restored successfully" is displayed in the View Restore Logs screen and as a popup window. In case of failure, it displays an error message in the View Restore Logs screen and as a popup window.
Once the migration process is complete, you can start the target environment.

Before starting the target environment, it is advised to manually compare server-configuration properties and server-configuration-bak properties files to check the selected configuration parameters.

6
Migrating objects in version control
Versioning refers to the process of assigning unique version numbers to unique states of the activities and objects. These numbers are generally assigned in increasing order and correspond to new developments in a group or project. While migrating objects in version control we can omit the version control fields if required.
This can be done through a configuration file migration.propeties which further has the following configurable properties:

migration.export.omitVersionControlFields
migration.import.omitVersionControlFields

By default the value of these properties is set as false. This means by default, the version control fields will not be omitted while exporting or deploying objects in version control.

Steps to Omit the Version Control Fields while Exporting and Deploying Objects in Version Control:

Go to <Adeptia Suite Installation folder>\AdeptiaServer\ServerKernel\MigrationUtility folder.
Open the migration.properties file.
Set the value of migration.export.omitVersionControlFields property as true while exporting objects in version control.

To learn how to export objects, please refer to the Export section.

Set the value of migration.import.omitVersionControlFields property as true while deploying objects in version control.

To learn how to deploy objects, please refer to the Deploy section.

Save this file.
It is recommended that whenever you migrate version control objects to target environment, then it shall not have version control enabled in it.
7
Backup and Restore
It is always recommended to take the backup of Adeptia Suite on a certain interval so that you can restore the objects incase drive on which Adeptia Suite is running gets damaged.
This section explains the steps to take the backup of objects. (Activities, Process flows, User, Groups and configuration file etc.).