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>/opt/AdeptiaSuite/AdeptiaSuite-<your-version><
<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.
<ExportType>PA</ExportType>
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 |
| Info |
|---|
While exporting objects on the basis of users, only A and PR type are supported. |
<Groups>
<Group name="administrators" export="yes" activityId="001" processFlowId="001" projectId="001" users="user1*,user2"/>
<Group name="DemoGroup" export="no" activityId="002" processFlowId="002" users=""/>
</Groups>
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. |
| Info |
|---|
You can define more than one group 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:
...
<Solution export="yes" tableId="001">
<DatabaseType><![CDATA[sql]]></DatabaseType>
<Server><![CDATA[192.168.1.17]]></Server>
<Port><![CDATA[1433]]></Port>
<DatabaseName><![CDATA[SqlDatabase]]></DatabaseName>
<UserName><![CDATA[sa]]></UserName>
<Password><![CDATA[p@ssw0rd]]></Password>
</Solution>
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:
...
<Activities activityId="003">
<activity name="DatabaseTarget" />
<activity name="FileTarget" />
<activity name="MailSource" />
</Activities>
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 |
| Info |
|---|
You can define as many activities type as you want. |
<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:
...
<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
...
| Info |
|---|
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 |
| Info |
|---|
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:
...