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

Version 1 Current »

You begin the migration of objects (services and activities) with the very first step of exporting them to a ZIP file at a location specified by you. You can export the objects by using the Export XML file. Click here to know more about generating the Export xml file using the GUI.

To export activities:

  1. Copy the export.xml file you generated using the GUI, and paste it to another folder in the PVC. For example, shared/migration/custom/export.xml.

  2. Go to migration 4.0.0 · adeptiainc/adeptia-connect-migration (artifacthub.io) to view the details of migration helm package.

  3. Add migration repo using following command:

    helm repo add adeptia-connect-migration https://adeptia.github.io/adeptia-connect-migration/charts/

  4. Click DEFAULT VALUES to download the values.yaml file.

  5. Provide values for the following environment variables in values.yaml file for migration as shown in the table below.

    Environment variableValueDescription
    SHARED_PATH/sharedEnvironment 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_PATHshared/migration/custom/export.xmlPath of the export.xml in PVC.

    Environment Variable
    		Value for Azure SQL DatabaseValue for Oracle DatabaseDescription
    BACKEND_DB_URLjdbc:sqlserver://<DB Hostname>:<Port Number>;database=<Backend Database Name>jdbc:oracle:thin:@<hostName>:<portNumber>:<S ID/ServiceName>URL of the backend database server.
    BACKEND_DB_USERNAME<User defined><User defined>Username of your backend database server.
    BACKEND_DB_PASSWORD<User defined><User defined>Password for your backend database server.
    BACKEND_DB_DRIVER_CLASScom.microsoft.sqlserver.jdbc.SQLServerDriveroracle.jdbc.OracleDriverBackend database driver class name.
    BACKEND_DB_TYPESQL-serverOracleType of the backend database server.


  6. Provide the values for the following environment variables too in values.yaml file for migration. 

    Environment VariableValueDescription
    OPERATIONexport

    The type of operation for which deployment will be performed.

    LOG_IDENTIFIER<LogID_2>

    Log identifier to capture logs from MS environment.

    If you do not provide a value for this environment variable, the name of exported zip file will be used as the value for the log identifier.
    EXPORT_ZIP_PATH/shared/<migrationtest1/SA_PF.zip>

    Path in the PVC where you want to create the exported zip.

    If you do not provide a value for this environment variable, you need to set the value for the TargetZipLoc tag in the export.xml file.

  7. Navigate to the migration directory, and run the following command to execute the Adeptia Connect Migration utility job. 

    helm install migration adeptia-connect-migration/migration -f <Path of the values.yaml>

    After you perform these steps, the Exported ZIP file will be created at the target location defined by you while creating the Export XML file.

    The Migration job does not get deleted automatically after the migration is complete. You need to manually delete it before you start a new migration process. 
  • No labels