/
Exporting Objects

Exporting Objects

Owned by Akash Kumar Jaiswal (Unlicensed)
Last updated: Nov 10, 2021 by Ashhad AlamVersion comment

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. To export activities:

You can also automate the migration process through a CD pipeline by using a tool such as Jenkins.

  1. Copy the export.xml file from shared repository ${SHARED_PATH}$/migration/template and paste at ${SHARED_PATH}$/migration/custom location. 

  2. Open export.xml in a text editor, and do the followings.

    1. Provide the location where you want to create the export zip along with the file name in the <TargetZipLoc> tag, for example, $SHARED_PATH$/migration/export/export-$TIMESTAMP$.zip. 



    2. Specify the activity you want to export. Type A to export all activities or a specific activity and PR to export based on the projects in the <ExportType> tag.




    3. Type the group name to which activity belongs in the <Groups> tag. In connect migration, we can export objects of 1 group at a time, so no option to define multiple groups.








    4. Define the list of projects that you want to export. You can export the activities of more than one Project.



    5. Define the activity type that you want to export under <Activities> tag.

      If you want to export specific activity then add the name or activityid under the specified Activity type. The format of ActivityId is: <id>ActivityID</id>. The format of name is: <name>Name</name>.



    6. Define the list of folders or files that you want to export with criteria. You can use these attributes for including or excluding multiple files/sub-folders.

      All of the following attributes support wildcards. You can also use multiple wildcards separated by commas (,). If no values are specified for Folder attribute, it considers the whole folder by default.



    7. Save the file.

  3. Provide values for the following properties and environment variables in values.yaml file as shown in the table below.



  4. Navigate to the migration directory, and run the below command to export the objects.

    helm upgrade -i migration adeptia/migration -f adeptia/values.yaml -n <NAMESPACE>

    After you perform these steps, the export zip file will be created at the defined target location.