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 2 Next »

  1. Type 3 and Press ENTER.

  2. Select the action and press ENTER.

    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.




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

  4. Provide the directory where the target system 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 differ.

    1. In case you have selected All, all objects are deployed at the target environment.

    2. In case you have selected Only Databaseoption, then the list of all the tables of the Adeptia Server appears.

    3. In case you have selected Only Configuration Files, then 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. If they are different then deselect the log objects such as (AU_Log and AU_TransactionData) as it slows down the migration process.

  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. If it is successful, a message stating, "Selected database/configuration tables restored successfully" appears. In case of failure, it displays an error message and rollbacks the entire operation.

  • No labels