Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

This section details how to import or restore the objects. Before you start, ensure that you have already run the Migration utility and selected Migration option to migrate the objects.

  1. Type 3 for Import/Restore and Press ENTER.

  2. Select the appropriate action and press ENTER.

    Action

    Description

    All

    Migrates Database object, Data files, and Configuration file.

    Database objects include Activities, Process Flows, Users, and Groups, etc.
    Data files include Data Dictionary XSDs, Custom Methods, and WSDL, etc.
    Configuration files includes server-configure.properties, launcher.properties, etc.

    If you select All and press ENTER, following two options are displayed.
    Skip Configuration File: Select this option to migrate only Database objects and Data files.
    Include Configuration Files: Select this option to migrate all Database objects, Data files and Configuration files.

    Only Database

    Migrates only Database objects. Data files and Configuration files are not migrated using this option.

    Only Configuration File

    Migrates only Configuration files. Database objects and Data files are not migrated using this option.




  3. Type the source directory with the zip file name and press ENTER. 

  4. Provide the directory where the target environment of the Adeptia Server is installed and press ENTER.

  5. Depending on the option (All, Only Database, and Only Configuration Files) selected in step 2, the next option differs.

    1. For All, all objects are deployed in the target environment.

    2. For Only Database option, the list of all the tables of the Adeptia Server appears.

    3. For Only Configuration Files, the list of all the configuration files for all objects of the Adeptia Server appears.

      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.

  6. Provide the data file number. You can also provide more than one number separated by comma (,), range (1-10) or a combination of both (1,2, 5-9, 13).

  7. Press ENTER to start importing/restoring. A message "Selected database/configuration tables restored successfully" appears confirming tables/files are restored successfully. In case of failure, it displays an error message and rollbacks the entire operation.

  8. Press ENTER to exit from the utility.
  • No labels