Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

The following screenshot displays the structure of import xml.


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.

<OverrideUser>IndigoUser:127000000001107055536473900001</OverrideUser>
Enter the 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.

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

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

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

  • No labels