Administration d'entreprise > Exportation et importation dans Windchill > Understanding Windchill Export and Import > Windchill Import Properties
  
Windchill Import Properties
 
Properties that control Windchill import operations can appear in the wt.properties file or in mapping files. If you do not set properties through a graphical user interface or in mapping files, you add or edit properties with the xconfmanager utility. For more information, see Using the xconfmanager Utility.
• wt.ixb.import.parser.validate (name in wt.properties file) or import.parser.validate (name in mapping files)—Specifies whether the imported document is validated by the XML parser. The default value is false.
• wt.ixb.import.overrideConflicts (name in wt.properties file) or import.overrideConflicts (name in mapping files)—Overrides the overridable folder and other conflicts during import. The default value is false.
• import.default.lifecycleInfo.lifecycleTemplateName—Specifies the default name to be assigned to a life cycle template whose name is missing from the XML file.
• import.default.lifecycleInfo.lifecycleState—Specifies the default state to be assigned to a life cycle whose state is missing from the XML file.
• wt.iba.definition.hierachicaldefinition.enabled—When set to true, allows hierarchical reusable attribute definitions to be imported. When set to false, hierarchical reusable attribute definitions can be created, but they cannot be imported unless you use a properly written mapping file that maps hierarchical reusable attribute definitions to non-hierarchical reusable attributes. The default value is false. You should not create hierarchical reusable attribute definitions unless this property is set to true in the wt.properties file.
• wt.ixb.import.allowCrossReleaseImport—Enables users to import a cross-release export JAR file into a Windchill system. The default value is false. This property is applicable only for the import operations performed through the Windchill Import/Export Management utility. Cross-release imports are not supported; this property simply allows the import operation to proceed. The import may not be successful, and even for successful import operations, the integrity of the imported data cannot be guaranteed. It is highly recommended that you avoid cross-release import operations.
• wt.ixb.import.maxThreads—The number of threads for import. The job list will be distributed over the number of threads you define.
Using multiple threads has the most significant impact on received delivery import performance. The threads share the same database connection, which can impact performance if the threshold is reached. The number of objects can also impact performance; the greater the number or objects, the greater the performance improvement when using multiple threads. In general, one thread will be sufficient for incremental package deliveries. An initial package delivery may benefit from multiple threads, particularly if the import time window is small. When importing CAD objects, this property must be set to 1. By default, this property is set to 1.
* 
The value of the wt.ixb.import.maxThreads property is used in conjunction with the wt.ixb.import.noOfParallelImportPaths property, which determines the number of transactions used for import.
• Single Transaction Scenario: If the wt.ixb.import.noOfParallelImportPaths property is set to 1, the value of the wt.ixb.import.maxThreads property is the total number of threads used for import.
• Multiple Transaction Scenario: If the value of the wt.ixb.import.noOfParallelImportPaths is set to more than 1, the value of the wt.ixb.import.maxThreads property is the number of threads used per import transaction.
• wt.ixb.import.batchSize—Indicates the maximum number of objects to be imported in one batch. The default value is 10k.
* 
The import multithreading property only applies to import of a received delivery for importable packages.
To add multithreaded environments for received delivery import of an importable package, do the following:
1. Add the following properties in site.xconf:
◦ <Property name="wt.ixb.logThread" overridable="true" targetFile="codebase/wt.properties" value="true"/>
◦ <Property name="wt.ixb.import.objPerThreadGuidance" overridable="true" targetFile="codebase/wt.properties" value="1"/>
◦ <Property name="wt.ixb.import.maxThreads" overridable="true" targetFile="codebase/wt.properties" value="2"/>
2. In a Windchill shell, run the following command: xconfmanager -p