Structure of Export XML

Following screenshot displays the structure of export XML:

Figure 1: Structure of Export XML

Following is the description of tags used in export XML file:

<Configuration operation="export">
This is the root tag of the XML. It also specifies the type of operation. For example: Export or Import. You need not to change anything within this tag.

<SourceInstallDir><AdeptiaInstallFolder>/AdeptiaServer</SourceInstallDir>
Enter the installation path of the Adeptia Suite of source environment from where you want to export the objects. You may also specify this value as parameter through the command prompt at run-time.

<TargetZipLoc>/opt/export/export.zip</TargetZipLoc>
Enter the path along with the file name, where you want to store the exported zip file. You may also specify this value as parameter through the command prompt at run-time.

Enter the type of objects to be exported. Please refer the following table.
Here:

P	Process flows
A	Activities
PA	Both Process flows and activities
PR	Project

While exporting objects on the basis of users, only A and PR type are supported.

Enter the name of the group whose objects you want to export.
Here:

name	Name of the group
export	Whether you want to export the objects of this group or not. It values can be yes or no.
activityId	Id of the activity list in the export.xml file. While exporting, only those activity list will be used, whose Id will match with this Id.
processFlowId	Id of the Process flow list in the export.xml file. While exporting, only those process flow list will be picked, whose Id will match with this Id.
projectId	Id of the project in the export.xml file. While exporting, only those projects will be picked, whose Id will match with this Id.
users	Name of user/s within a specified group. While exporting, all-objects/project objects of the specified user/s will be picked. You can specify multiple users separated by comma. Wildcards are also supported. If no value is specified for users attribute, it considers all the users of that group by default.

You can define more than one group at a time.

If you are exporting process flows, you cannot export the process flow of multiple groups at a time.
You can export process flows of only one group at a time. You can export activities of multiple groups at a time.

<Projects>
<Project activityId="001" export="yes">Default</Project>
<Project activityId="003" export="no"/>
</Projects>
Define the list of projects that you want to export. You can create more than one Projects list.
Here:

Project activity id	Id of the project activities list and this should match with id of activity list.
Export	Whether you want to export the objects of this project or not. It values can be yes or no.
Name of the project	Name of project that you want to export. For example, the 'Default' project.

Define the list of parameters that you need to define to make connection with solution database from where you want to export a table. You can export more than one table from the same database.
Here:

export	Yes or no. Define yes if you want to export a table from a database.
tableId	Id of the table that you want to export. For example, 001
Database Type	Type of database that you want to export. For example, ![CDATA[sql]]
Server	IP address of the server where solution table exist. For example, ![CDATA[192.168.1.17]]
Port	Port number. For example, ![CDATA[1433]]
DatabaseName	Name of the database whose tables you want to export
UserName	User name to access the database
Password	Password to access the database

Define the list of activities that you want to export for a particular group or project. You can create more than one Activities list.
Here:

activityId	Id of this activity list. This should match with the activityId defined in the <GroupName> or in <project>.
activity name	Type of the activity that you want to export. For example if you define Database Target, all the database target activities that belong to the specified group or project, are exported

You can define as many activities type as you want.
For reference list of all activities type is defined in the export.xml file.

<ProcessFlows processFlowId="100">
<ProcessFlowName>EvalXform_ProcessFlow</ProcessFlowName>
<ProcessFlowName>EvalScript_ProcessFlow</ProcessFlowName>
</ProcessFlows>

Define the list of process flow that you want to export. You can create more than one process flow list.
Here:

processFlowId	Id of this process flow list. This should match with the processFlowId, defined in the <GroupName> tag.
ProcessFlowName	Name of the process flow that you want to export. You can define wild cards in the process flow names.

<SolutionTables tableId="001">
<Table>
<name><![CDATA[employee]]></name>
<whereClause><![CDATA[empid =(select max(empId) from employee)]]></whereClause>
</Table>
<Table>
<name><![CDATA[Order]]></name>
<whereClause><![CDATA[orderid =1]]></whereClause>
</Table>
</SolutionTables>
Enter the value of parameters for the table that you want to export

Name and structure of the table that you want to export should be same at the source and target end.

Here:

tableID	Id of the table that you want to export
Name	Name of the table that you want to export
whereClause	Defines the where clause to specify the data to be fetched from the table

You can define as many tables as you want.

The below example explains how you can export the customClasses folders with include/exclude criteria.
<Folders>
<Folder includeSubFolders="" excludeSubFolders="" includeFiles="" excludeFiles="DataInterface*">customClasses</Folder>
</Folders>

The above example will export all the files and folders except the ones starting with DataInterface name.
Specify a criteria to include or exclude files and folders while exporting objects. The following table explains all the attributes of Folder tag.
Here:

Folder Attributes	You may use these attributes for including or excluding multiple files/sub-folders. All of the following attributes support wildcards. You may also use multiple wildcards separated by commas (,). If no values are specified for Folder attribute, it considers the whole folder by default.
includeSubFolders	The specified folders will be exported including all sub-files
excludeSubFolders	The specified subfolders will not be exported
includeFiles	The specified files will be exported
excludeFiles	The specified files will not be exported

The below example explains how you can export the server-configure.properties file.
<Files>
File>etc/server-configure.properties</File>
</Files>