Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

The following screenshot displays the structure of import xml.

Image RemovedImage Added
The following paragraphs contain the description of the tags available in the import XML file:

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

<SourceZipLoc>$SHARED_PATH$/migration/export/EXPORTED_ZIP_FILENAME.zip</SourceZipLoc>
Enter the path along with the file name, of the exported zip. This is the zip that you have created during export step. 

<RetainXmlLocation>$SHARED_PATH$/migration/custom/RETAIN_FILENAME.xml</RetainXmlLocation>
Enter the path along with file name of the retain xml. Retain XML file is used to specify the activities that you want to retain while importing the objects.<OverrideGroup >IndigoGroup:127000000001107055548721600002</OverrideGroup>
Enter the Id or name of the group, which will be the owner group of the deployed objects in the target environment.

<OverrideUser>IndigoUser:127000000001107055536473900001</OverrideUser>
Enter the id or name of the user, which will be the owner of the deployed objects in the target User Id of an IT user to whom you want to provide the ownership of the objects that you are deploying from the source environment.

<OverrideModifiedByUser>IndigoUser:127000000001107055536473900001</OverrideModifiedByUser>
Enter the Id or name of the user which will be reflected in the modified by field of every activity after deployment.

<OverrideProjectGroup></OverrideProjectGroup>
Enter the Group Id which will be reflected in the project group field of the project after deployment.

<OverridePermission></OverridePermission>
Enter the permission/s which will be reflected in the permission field of every activity after deployment.

<Solution >
<DatabaseType><![CDATA[]]></DatabaseType>
<Server><![CDATA[]]></Server>
<Port><![CDATA[]]></Port>
<DatabaseName><![CDATA[]]></DatabaseName>
<UserName><![CDATA[]]></UserName>
<Password><![CDATA[]]></Password>
</Solution>

Enter values for all the parameters. You need to define these parameters to export table(s) from the respective database.
Here:

DatabaseType

Type of database from where you want to import the tables.

Server

IP address of the host server.

Port

Port number.

DatabaseName

Name of the database whose tables you want to import.

UserName

User name to access the database.

Password

Password to access the database.


Info

OverrideUser , and OverrideModifiedByUser, and OverrideGroup fields also support Entity entity name together with the Entity entity Id. For example, the field value highlighted in Red red in the following tag will be treated as an Entity entity name.

<OverrideUser comment="User Id with which all objects will be deployed">ituser@adeptia.com</OverrideUser>



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