Windchill export enables you to place all the data stored in high-level objects in the local database into JAR files on the local file system. Optionally, you can include only objects that were created or modified within a date and time range. Later, use import to extract these JAR files to locations that you specify in the local database. The data that is exported (stored) and then imported (extracted) does not include information required for change control.

Export enables you to compress the data found in a variety of objects into a JAR file, including the following:

You can view all of the types of objects that you can export in the Export window. Documents that are referenced by other objects are included in the export data. You can filter objects by their time of last modification to control which objects are included in the JAR file.

You can give the JAR files any name you want. The files have the . jar extension unless you specify a different file extension. You can open the JAR file with any software that opens and expands ZIP files.

Windchill import enables you to expand the compressed files created by the export process and place the objects in the local database. After you have imported the objects, they can be modified just like any other files.

If you use the default settings, import does not overwrite objects that already exist in the same namespace in the local database and have the same status as the object that you are trying to import. For most business objects, such as parts, documents, and CAD documents, import determines whether an object is unique based on the following identifiers:

If an object to be imported has the UFID as an existing database object but a different business identity, the import fails. If you do not want the import to fail in this situation, select the Resolve Overridable Conflicts checkbox in the Import window or use a policy or rule file to change either the UFID or the business identity of the import object.

If there is a conflict in the value of other attributes, the system response varies depending on the attribute and the import options that you selected. For details about overriding conflicts, see Import and Export Policies, Mapping Rules, and Conflict Messages.

The export and import processes can refer to mapping rule files that transform or block attribute data on the interface to the JAR file. In addition, the import process can refer to context mapping files which control into which context imported objects are placed.

The way objects in the database can be created or modified is governed by use of policy files or selected actions available in the user interface during import or export. These import policy files or actions are applied after any mapping rules files are applied.

A preview feature shows the expected results of importing from a specific file. This feature shows which files will be imported, what conflicts might arise, and whether the import process will be completed or will fail. However, it may not report every detail of the results of the import operation.

If the Detailed Log checkbox is not selected, the log shows how many objects will be imported and how many XML files will be processed. If the Detailed Log checkbox is selected, the log also shows which files will be imported, what conflicts might arise during import, and whether the import process will be completed or will fail. Note that because this is a lightweight check, it is possible for the import process to fail even if the preview did not indicate any issues.

For information about mapping rules and policies, see Import and Export Policies, Mapping Rules, and Conflict Messages.

Windchill export and import do not support the export and import of JAR files across releases. In other words, a JAR file that was created by performing an export in an earlier version of Windchill cannot be imported into a new version of Windchill unless a specific property is enabled. If a cross-release import is necessary, you can enable this property.

To enable cross-release import, specify the following property in the wt.properties file and then restart the method server:

Alternatively, to dynamically reload this property, specify it in a mapping rule file with the following format:

For more detailed information about conflicts and policies and mapping rules, see Import and Export Policies, Mapping Rules, and Conflict Messages.