Importing Data Marked for Replication
Before starting the import activity, it is a good practice to check for any version mismatch between the data in the source system and target system. Use the parameter -p or --mismatchReport in the import command to generate the report.
windchill com.ptc.windchill.rd.cli.WindchillPackage import -u <username> -c "<context>" -l "<directory>" -p
windchill com.ptc.windchill.rd.cli.WindchillPackage import -u demo -c "/wt.inf.container.OrgContainer=Demo Organization/wt.pdmlink.PDMLinkProduct=Drive System" -l "D:\importedFiles\packageDeliveries\20131202" -p
The version mismatch report is generated only for those received deliveries that have version mismatch data. The report is displayed in the Attachments tab of the received delivery. For more information on the report, see Version Mismatch Report.
To import and overwrite data that is marked with the replication lock, you must use the command line utility only. Specify the parameter -o or --overwrite in the import command, as given in the following example:
windchill com.ptc.windchill.rd.cli.WindchillPackage import -u demo -c "/wt.inf.container.OrgContainer=Demo Organization/wt.pdmlink.PDMLinkProduct=Drive System" -l "D:\importedFiles\packageDeliveries\20131202" -o
If you specify both the parameters -o and -p, -o is ignored.
After successfully importing the received delivery, the replication lock changes to the product design lock, named “Locked by Product Design Package”. If an object still shows the replication lock, the object is not imported due to issues such as version mismatch, object not being accessible, or non-overridable conflict. Access the version mismatch report and import log generated in the Attachments tab of the received delivery to identify and resolve such issues, and then retry the import.
The import log file shows the value YES for LOCAL_OBJECTS_OVERWRITE_MODE if the replication lock was applied. However, when importing an incremental package, the log file for the received delivery shows the value NO.
If a received delivery is imported partially, that is, with the status “Unsuccessful: Partial Import”, and you try to import the same uploaded received delivery again, the import log for the earlier import is retained as is. A new import log is generated for the latest import.
 |
• Only base packages can be successfully imported when using the replication lock. Incremental packages are not supported for import through the replication lock process.
• The following points apply for change management objects:
◦ When importing a replication package, for a change notice getting overwritten, all the associated local change tasks are removed and then recreated based on the source package.
◦ Effectivity is collected only if the effectivity context is marked for replication or is already replicated. However, Date effectivity is collected even if the effectivity context is not assigned.
◦ The entire change network is collected when applying the replication lock.
• If a base package is successfully imported, any change on the source system can be directly replicated on the target system through an incremental package.
|