In this chapter the import/export function of the ITP/MDK Repository is discussed. There are four ways in which data can be exported/imported from the ITP/MDK Repository:
Save to... and Load from... can be used to save documents to the file system as documents and to load documents from the file system. This functionality can be used when it is necessary to communicate with other applications than the ITP/MDK Repository. Its main use is to load a new ITP/MDK Repository with an existing collection of ITP Model Documents.
Import/Export allows you to export objects from the ITP/MDK Repository as ITP/MDK Repository objects. This allows you to copy objects to other ITP/MDK Repositories. Its practical use is in third-party development, helpdesk exports and archiving. Exported objects are stored in a file that can be read by the import process. An exported project, folder or document is after an import present in the importing ITP/MDK Repository as it was in the exporting ITP/MDK Repository.
Repdump/repload are tools that can be used to migrate the database of a ITP/MDK Repository. Repdump.exe creates a file that contains all data - documents, models but also settings and users etcetera.- present in the database. The ITP/MDK Repository created with repload.exe will be an exact duplicate of the dumped ITP/MDK Repository. Do not use repdump/repload to implement document life-cycles, use export/import instead.
Deploy exports all models and support files form a project ready to be used in an ITP setup aimed at running models.
Note
Only the models and support files the user is authorized for will be deployed.