Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

After you've created the export.zip file, you can import the objects using import.xml file. A successful import completes the migration process, and you'll be able to access all the objects in your new environment. 

Info
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. For more information, refer to Structure of Retain XML.

To import objects:

  1. Copy the import.xml file PVC shared location <shared>/migration/template, and paste it to another folder.
    For example, shared/migration/custom/import.xml.

  2. Open import.xml in a text editor and do the followings.
    1. Type the location of the export zip file that you want to import in the <SourceZipLoc>.

      Image Removed

    2. Type the location of retain.xml file in the <RetainXMlLocation>

    3. Enter the User Id of the user to whom you want to provide the ownership of the objects that you are deploying from the source environment in the <OverrideUser>.
    4. Save the file.
  3. Provide values for the following properties and environment variables in values.yaml file as shown in the table below.

    Variable/Property

    Value

    BACKEND_DB_URL<URL of the backend database server>BACKEND_DB_USERNAME<Username of your backend database server>BACKEND_DB_PASSWORD<Password for your backend database server>

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

    name> server> For example, SQL-<Environment variable in the

    Environment Variable

    Value

    Description
    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>/import.xmlPath of the import.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_CLASS<Backend com.microsoft.sqlserver.jdbc.SQLServerDriveroracle.jdbc.OracleDriverBackend database driver class name.
    BACKEND_DB_TYPE<Type SQL-serverOracleType of the backend database server.SHARED_PATH


  4. Provide the values for the following environment variables too in 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_PATH<Path of the import.xml in PVC> For example, shared/migration/custom/import.xml.

    for migration. These values will override the values for the corresponding tags in import.xml file.

    Environment Variable
    ValueDescription
    OPERATIONimport

    The type of operation for which deployment will be performed.

    Tip
    If you do not provide a value for this environment variable, you need to set the value for the operation attribute in the import.xml file.


    SOURCE_ZIP_PATH/shared/<migrationtest1/SA_PF.zip>

    Path of the exported ZIP in the PVC.

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


    OVERRIDE_USER<'IndigoUser:127000000001107055536473900001'>

    User Id, Entity Id, or Type Id of the user with which all objects will be deployed.

    Tip
    Enter the value in single quotes. If you do not provide a value for this environment variable, you need to set the value for the OverrideUser tag in the import.xml file.


    OVERRIDE_MODIFIEDBY_USER<'IndigoUser:127000000001107055536473900001'>

    User Id, Entity Id, or Type Id of the user which will be reflected in the modified by field of every activity after the deployment.

    Tip
    • Enter the value in single quotes.
    • If you do not provide a value for this environment variable, you need to set the value for the OverrideModifiedByUser tag in the import.xml file.


    RETAIN_XML_PATH


    /shared/<migrationtest1/retain.xml>

    Path of the retain XML file in the PVC.

    Tip

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


    LOG_IDENTIFIER

    <LogID_1>

    Log identifier to capture logs from MS environment.

    Tip
    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.


    ROLLBACK_ZIP_PATH

    /shared/<Rollback_SA_PF.zip>

    Path in the PVC where you want to keep the rollback zip.

    Tip
    • If you do not wish to provide a value for this environment variable in the values.yaml file, you can set the value for the RollbackZipLoc tag in the import.xml file.

    • If you neither specify this value in the values.yaml file nor provide it in the import xml file:
      • The system creates the rollback zip file at the location where your exported zip is created in the PVC.
      • The format of rollback zip file name will be Rollback_<name of the exported zip file>.



  5. Navigate to the migration directory, and run the below command to import the objects.

    Code Block
    languagecss
    themeMidnight
    helm upgradeinstall -i migration adeptia-connect-migration/migration -f adeptia/values.yaml -n <NAMESPACE> <Path of the values.yaml>


    Info
    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. 


Rolling back the import operation

If you decide upon rolling back the import operation, you need to follow the instructions given below.

  1. Change the values for the following two parameters in the

    Provide the values for the following environment variables in values.yaml file for migration. These values will override the values for the corresponding tags in import.xml file.


  2. Enter rollback as the value for the operation attribute.
  3. Type the location of the rollback ZIP file in the <SourceZipLoc> tag. 

    InfoThe rollback ZIP is created at the location where your Exported ZIP is created in the PVC. 
    The format of rollback ZIP file name is Recovery_<EXPORT_ZIP_NAME>.zip

    Environment VariableValueDescription
    OPERATIONrollback

    The type of operation for which deployment will be performed.

    SOURCE_ZIP_PATH/shared/<Rollback_SA_PF.zip>

    Path of the rollback zip in the PVC.

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



  4. Navigate to the migration directory, and run the below command to perform the rollback operation.

    Code Block
    languagecss
    themeMidnight
    helm upgradeinstall -i migration adeptia-connect-migration/migration -f adeptia/values.yaml -n <NAMESPACE> <Path of the values.yaml>


    Info
    RetainXmlLocation, OverRideuser, and OverrideModifiedByuser parameters are not applicable in case of rollback. 



Panel
borderStylesolid
titleYou may be interested in...
What is new
Application architecture
Key terms
Install
Usage scenarios