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 and target systems. 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 received deliveries that contain version mismatch data. The report is displayed in Attachments tab of the received delivery. For more information, see Version Mismatch Report.
To import and overwrite data marked as Locked for Replication, you must use the command line utility. Specify the parameter -o or --overwrite in the import command, as shown below:
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 both the parameters -o and -p are specified, the -o parameter is ignored.
After the received delivery is successfully imported, the replication lock transitions to a product design lock named Locked by Product Design Package. If an object continues to display the replication lock, it indicates that the import was unsuccessful due to issues such as a version mismatch, inaccessible object, or a non-overridable conflict. To identify and resolve these issues, refer to the version mismatch report and import log available in the Attachments tab of the received delivery. After addressing the identified problems, retry the import process.
The import log file displays 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 attempt to re-import the same uploaded delivery, the import log from the earlier attempt is retained. A new import log is generated for the latest import.
 |
• Only base packages can be successfully imported using the replication lock. Incremental packages are not supported through this process.
• The following points apply to change management objects:
◦ When importing a replication package, if a change notice is overwritten, all associated local change tasks are removed and recreated based on the source package.
◦ Effectivity is collected only if the effectivity context is marked as Locked for Replication or has already been 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.
• After a base package is successfully imported, any changes on the source system can be directly replicated on the target system using an incremental package.
|