Exporting a Package From a Source PLM System
This section explains the steps required to export a package. Detailed information for exporting packages can be found in
Exporting Packages and
Exporting Packages Using the Recipe Language.
Setting Export Preferences
The Windchill or Pro/INTRALINK design partner or supplier that wants to export a package begins by setting export preferences for the data to be exported in the wpc_preferences.txt file.
After preferences have been set in the wpc_preferences.txt file, create the package you want to send.
Typically, you must have access to all of the CAD objects that you want to export, along with their dependents. If you do not have access to all of the CAD objects and their dependents, it is possible to export an incomplete package The incomplete package contains the global ID for the CAD objects for which you do not have permission. To export this type of package, you must set the
wpc.export.secured.version preference. For more information, see
Setting Export Preferences.
Creating the Package
Creo Packages supports the creation of complete, incremental, and synchronization packages.
Creating a Complete Package
Complete packages contain all of the components of the data and metadata criteria using the Creo PackagesWPCExport command.
• A complete package can be a basic export that uses the WPCExport command and applicable arguments, but doesn’t utilize a recipe file upon the export and creation of the complete package.
• A complete package can be an advanced export that uses the WPCExport command and applicable arguments that utilizes a recipe file upon the export and creation of the complete package.
• A complete package can be an object ownership transfer package to transfer the object ownership from the original owner to a new owner.
Creating an Incremental Package
An incremental export is accomplished by utilizing a recipe file. A recipe file defines the baselines being used to subtract a set of already exported objects.
Incremental packages are created by WPCExport command with the contents of a baseline from a previous WPCExport package.
You can find the baseline-related to a previously exported package by locating an object that was included in the last package. For example, to find the top-level object that is at a later iteration than what is currently in the target PLM system.
Creating a Synchronization Package
A synchronization package can be used to:
• Synchronize information about previously exported data in a target PLM system with the source PLM system. A synchronization package uses the WPCExport_synch command to include only the metadata of objects whose properties are changed after exporting them to a target PLM system.
• After a complete package for object ownership transfer has occurred, a master synchronization package is sent to the original owner of the object. The new owner and the original owner also send the master synchronization package to any other partners that they share the data for the object with.
Viewing the Package Log or Conflict Reports
The Creo Packages system generates log reports for a successful export or conflict reports in case the export fails. The overridable conflict file is generated in the location set by the preferences in the wpc_preferences.txt file.
After a successful export of a package, the model files and the associated metadata are contained in a newly created package on the source PLM system machine used for the Creo Packages export.
The Export Post report, created by Creo Packages upon the successful export of the package, should be viewed on the source PLM system before sending it to the target PLM system recipient.
Sending the Package
The exported package can be sent to another design partner or supplier for the sharing of information. Depending on the collaboration procedures established with the partner or supplier, the package can be transferred in several ways, including email, file transfer protocol (FTP), CD-ROM, and tape.
