多站点help 英文版多站点7章

第7章4thGenerationDesigndataKey concepts of TC XML-based data exchange . . . . . . . . . . . . . . . . . . 7-14th Generation Design data exchange . . . . . . . . . . . . . . . . . . . . . . 7-3 Traversal-free synchronization . . . . . . . . . . . . . . . . . . . . . . . . 7-13Multi-SiteCollaborationGuidePLM00028 J4thGenerationDesigndata第7章4thGenerationDesigndataKey concepts of TC XML-based data exchangeThe following are key concepts for understanding how you use Multi-Site TC XML-based data exchange and how it is different from classic Multi-Site functionality. Closure ruleA closure rule controls the scope of the data translation for both import and export by: o Specifying how to traverse the data structure. o Defining the relationships that are of interest.o Defining what action to take when relationships of interest are encountered.Closure rules provide an efficient and codeless approach to extension of the data model. By default, Multi-Site uses the MultiSiteDefaultCR closure rule. For 4GD object replication or ownership transfers, the closure rules determine the contents of the island of data used in the transfer process.For more information about 4GD object islands of data, see 4thGeneration Designdataexchange.Multi-Site closure rules and their controlling transfer option sets are used to provide direction to the data_share and data_sync utilities about how to traverse the Teamcenter database and how to process the information traversed. Teamcenter provides a set of default closure rules as part of the installation and upgrade process.For more information about closure rules and transfer options, see the PLM XML/TCXMLExportImportAdministrationGuide. Dependent objectA dependent object that must be included in the set of objects implied by the principal object and the closure rules to correctly form the island of data. Not all principal objects have dependent objects. Principal objectA principal object is the initial object that can be used to start the traversal to determine an island of data. Island of dataAn island of data is a fundamental unit of transfer for moving data objects between sites using TC XML formatted data. It consists of a principal object and the additional objects on which it depends (identified by closure rules) for its correct functional definition and usage within Teamcenter.For 4th Generation Design data, an island of data for reference transfer (replication) is different from an island of data for ownership transfer. ScoperWhen the exporter or importer receives a request to transfer data, it determines the transfer mode from the option set object. It then creates the traversal object based on the transfer mode scope (import, export) and the schema format (PLM XML or TC XML). The basic behavior of a traversal object is to provide two methods, process and traverse. The process method processes the present object in hand and calls the traverse method. The traverse method navigates to the next object and then calls the process method. This operation iterates until no more objects are available to process.The scoper evaluates the transfer mode closure rules and the options provided by the exporter and returns only the objects that are identified for the process method in a closure rule clause. This list is sent to the exporter or importer for serialization or deserializaton. SynchronizationWhen a master object is replicated at other sites, you must update the replicas whenever the master object is modified. The process of updating replicas is referred to as synchronization. The synchronizer is responsible for ensuring that a previously replicated data is synchronized.In a Multi-Site environment, you perform manual synchronization using the data_sync utility. It is a re-export or re-import of the object of the object with the same transfer formula.CautionWhen manually synchronizing a replica, both the owning site and replica site must be online to receive replica deletion notification.NoteTC XML-based data exchange does not support automatic pull synchronization.TC XML-based data exchange provides a traversal-free synchronization that provides better performance.For more information about traversal-free synchronization, see Traversal-freesynchronization. Transfer modeA transfer mode () is a logical grouping of closure rule clauses. An administrator selects a transfer mode when creating closure rule clauses. Transfer modes allow users to export and import data by knowing only the transfer mode name that they must use, for example, ToSiteA or FromSiteB. Transfer option setA transfer option set (TOS) () is a stored set of transfer options used for remote data export. A transfer option set displays all of the unique options in the closure rule conditional clauses for the selected transfer mode. By default, Multi-Site uses the MultiSiteOptSet transfer option set.4th Generation Design data exchange4th Generation Design (4GD) is the process of developing a collaborative design that contains all the necessary design information used to manufacture the subject product, for example a car, ship, or aircraft. A collaborative design is the collector for product configurations and includes all product design data as design elements and design features. You develop your collaborative design using the 4G Designer application. The 4G Designer application supports massive product designs with millions of business objects and also supports enhanced collaborative business processes. 4GD data exchange uses the Multi-Site Collaboration communication framework with Data Exchange TC XML as the payload to provide the scalability to handle the massive data required for 4GD data exchange.Although TC XML import and export (TIE) functionality that Multi-Site uses for exchanging 4GD data can also be used to exchange other types of objects from Multi-Site, Siemens PLM Software certifies only 4GD objects as the root objects for this functionality. Not all Multi-Site import and export features and options are supported when you use the TIE functionality from Multi-Site. You access the Multi-Site TIE feature for 4GD objects using the data_share and data_sync utilities with the -low_level argument.All sites that participate in your Multi-Site environment can replicate data at remote sites, synchronize remote data, and transfer ownership between sites for the following 4GD business objects: Collaborative design (Cpd0CollaborativeDesign class) Design control element (Cpd0DesignControlElement class) Worksets (Cpd0Workset class) Promissory, reuse, and shape design elements (Cpd0DesignElement class) Partition (Ptn0Partition class) Subset definition (Mdl0SubsetDefinition class) Partition template model (Ptn0PartitionTemplateModel class)For more information about 4GD concepts, see the 4thGenerationDesignGuide.Multi-Site supports the following 4GD data exchange: Export and import of the latest persistent object model (POM) minor revision data. Synchronization of 4GD objects. Transfer of ownership of 4GD objects. Replication of unconfigured 4GD objects.Note If you export a design element, design control element, subset definition, or a workset with transfer of ownership, the associated collaborative design object must already exist at the importing site.TC XML import and export uses islands of data to perform replication. Islands of dataAn island of data contains the following objects when you export the indicated principal object.Principal objectObjects exported with principal objectCollaborativeDesignCollaborativeDesignPtn0PartitionRealization (if it is realized from PartitionTemplate) and its attachmentsPartitionTemplateModelPartitionTemplateModel and its attachmentsMdl0PositionedModelElementMdl0ElementThreadMdl0EffectivityExprBlockMdl0VariantExprBlockMdl0AttributeGroupMdl0DefaultGeometry and its associated datasets BoundingMultiBoxReuse design elementReuse design elementSubordinate design elementCpd0DesignItemInstanceRlz0ItemRealizationMapMember-owned Ptn0MembershipSee item 1 of the note following this table.Promissory design elementPromissory design elementMember-owned Ptn0MembershipPrincipal objectObjects exported with principal objectShape design elementShape design elementMember-owned Ptn0MembershipCpd0DesignControlElementCpd0DesignControlElementCpd0DesignFeatureCpd0DesignFeatureMdl0ConditionalElementMdl0ElementThreadMdl0EffectivityExprBlockMdl0VariantExprBlockMdl0AttributeGroupPtn0PartitionPtn0PartitionApprSearchCriteriaPtn0ChildParentLinkPartition-owned Ptn0MembershipRlz0ModelRealizationMap (if it is realized from PartitionTemplate)See item 2 of the note following this table.Mdl0SubsetDefinitionMdl0SubsetDefinitionConfigurationContextApprSearchCriteriaMdl0AttributeGroupCpd0WorksetCpd0WorksetPSBOMViewCpd0WorksetRevisionPSBOMViewRevisionCpd0WorksetModelCpd0DesignSubsetElementCpd0DesignSubsetInstanceMdl0DefaultGeometryPrincipal objectObjects exported with principal objectRlz0ModelRealizationMapApprSearchCriteriaGroupSee item 1 of the note following this table.Note Due to a stub display issue in 4G Designer, the following objects are transferred as full objects in Teamcenter 10.1. This issue may be addressed in a future version.1. Source objects (ItemRevision of a DesignElement and DesignElement of a Subset) are exported as full objects in a different island.2. A member of partition owned membership is exported as full object. Partition schemesPartition schemes and collaborative design content can be exported in two steps.1. Add the following external closure rule to replicate collaborative design (CD) content and its associated partition schemes (PS). This step is required only once for collaborative design, for example, once for instantiation of a vehicle program.CLASS.Mdl0ApplicationModel:CLASS.Ptn0PartitionScheme: REFBY.mdl0model_object:PROCESS+TRAVERSE:,2. After Teamcenter replicates the collaborative design content and its partition schemes, remove the external closure rule to replicate collaborative design content including partition membership in case of a partition owned membership. This step may be required many times (potentially as overnight tasks performed on a daily basis). Collaborative design and its contentsFor CollaborativeDesign objects and their contents, add the following closure rule clauses to the SiteConsolidationDefaultCR closure rule for low-level TIE or the TIEExportDefaultCR closure rule for high-level TIE:CLASS.Mdl0ApplicationModel:CLASS.Ptn0PartitionScheme: REFBY.mdl0model_object:PROCESS+TRAVERSE:, CLASS.Cpd0CollaborativeDesign:CLASS.Mdl0ModelElement: REFBY.mdl0model_object:PROCESS+TRAVERSE:, CLASS.Cpd0CollaborativeDesign:CLASS.Mdl0SubsetDefinition:REFBY.mdl0model_object:PROCESS+TRAVERSE:, Partition structureFor a partition structure, add the following closure rule clauses to the SiteConsolidationDefaultCR closure rule for low-level TIE or the TIEExportDefaultCR closure rule for high-level TIE:CLASS.Ptn0Partition:CLASS.Ptn0ChildParentLink:ATTRIBUTE.ptn0partition_id:PROCESS+TRAVERSE:(PRIMARY.ptn0partition_id=SECONDARY.ptn0partition_id) &(PRIMARY.ptn0partition_scheme_type=SECONDARY.ptn0partition_scheme_type) & (PRIMARY.mdl0model_object = SECONDARY.mdl0model_object):I,(PRIMARY.ptn0partition_scheme_type=SECONDARY.ptn0partition_scheme_type)& (PRIMARY.mdl0model_object = SECONDARY.mdl0model_object)&(PRIMARY.ptn0source_object != SECONDARY.ptn0partition_definition), Design control elementsTC XML import and export ensures the DesignControlElement objects, and the elements and features it controls, are always transferred together. The elements that a design control element can control are reuse design elements and shape design elements.o If a design control element is the root object, the elements and features it controls are transferred. If the element is reuse design element, all its subordinate design elements are also transferred.o If a reuse design element is the root object and it is controlled by a design control element, data transfer is proceeds as follows:The reuse design element and its subordinate reuse design elements are transferred.The design control element is transferred.All other secondary objects (such a DesignFeature) controlled by the same design control element are transferred.o If a shape design element is the root object and it is controlled by a design control element, data transfer is proceeds as follows: The shape design element and the design control element are transferred. All other secondary objects controlled by the same design control element are transferred. Partition template modelFor PartitionTemplateModel objects, the following example shows the export results:Source partition template Ptn0PartitionRealization Target collaborative designRlzModelRealizationMap functionalScheme functionalSchemeRlzModelRealizationMap RlzModelRealizationMap Ptn2 Ptn2Rules for export of realized partitions:o The general rules defined for partition transfers are applied to a realized partition transfer.o A Ptn0PartitionRealization object is transferred with the target collaborative design.o A Rlz0ModelRealizationMap object is transferred with a realized partition.o A realized partitionScheme object is transferred using external closure rule.Selected root objectObjects transferredSource partitionSource partitionTarget collaborative designTarget collaborative design and Ptn0PartitionRealization objectNote Use external closure rule to export the PartitionScheme object.Ptn2Island of partitionPtn2Island of partition andRlz0ModelRealizationMap objectNote Use external closure rules to export the entire partition structure.TC XML import and export also uses islands of data to perform ownership transfers. However, the behavior is different. Islands of dataFor the selected root object in the following table, the ownership of the objects in the islands is transferred together.Root objectObjects in islandsCollaborativeDesignCollaborativeDesignPartitionTemplateModelPartitionTemplateModelReuse design elementReuse design elementPromissory design elementPromissory design elementRoot objectObjects in islandsShape design elementShape design element shapeDesignCpd0DesignControlElementCpd0DesignControlElementReuse design elementShape design element shapeDesignCpd0DesignFeatureCpd0DesignFeatureCpd0DesignFeatureCpd0DesignControlElementReuse design elementShape design element shapeDesignPtn0PartitionPtn0PartitionMdl0SubsetDefinitionMdl0SubsetDefinitionCpd0WorksetCpd0WorksetItem (child item of workset)The following example shows the export results:Collaborative design1Top Item realization DE2 (subordinate)ch1-1DE3 (subordinate) ch1-2DE4(subordinate)DE5 (subordinate)ch2-1DE6 (subordinate) ch2-2DE7 (subordinate)2DE9 (promissory)3DE2 (subordinate)4Subset21. Collaborative design ownership is not transferred if the selected root object is not the collaborative design itself.2. Ownership of the source object (ShapeDesign or ShapeDesignRevision) is transferred together with shape design element.3. A subset cannot be transferred without the workset for both reference and ownership transferred cases.4. Ownership of a design element is not transferred together with a workset or subset.PLM00028 JMulti-SiteCollaborationGuide 7-104thGenerationDesigndataDE5 (subordinate)ItemRevision . Teamcenter 10.1 follows the current BOM ownership transfer behavior.6DE . Ownership of the Ptn object, Ptn object owned memberships, and childParent links are transferred together. (subordinate)DE8 (shape)DCE source object(shapeDesignRevision) . Ownership of design control element, design feature, design element, and datum are all transferred together.DFDE (shape)DE (resuse)The following 4GD concepts apply to Multi-Site Collaboration data exchange: POM revision dataOnly the latest minor revision can be exported/imported. Partitionsde_incl_rlz_bomBy default, BOM structure is exported separately from 4GD structure due to the potential size of the data. If you want to export BOM structure and 4GD structure together in single operation, set this option to true.DesignElement source objects are exported as full objects. For ShapeDE objects, ShapeDesignRevision is the source object. For ReuseDE and SubordinateDE objects, ItemRevision is the source object.opt_de_rlz_itemYou can add a design element under a replicated partition. The master partition does not have the knowledge of all design elements under the replicated partition. This behavior is acceptable as long as either a well-defined best practice approach is exercised so your users can assume the master partition is always up-to-date within a given time interval, or a central authority, implemented later in the future, can be consulted to determine what data is up to date. For a parent-child link owned by child partitions, users must make sure the partition hierarchy is constructed at one site, and then replicated to all other sites.The following TC XML options apply to 4GD object replication.Multi-Site option nameDescriptionExport behaviorTC XML option nameNoteBOM structureincludes the full island of data ofan associated item/BVR with a design element.-workset_incl_rlz_deBy default, theWorkset/Subset structure is exported separatelyfrom DesignElement objects. If youwant to export theWorkset/Subset structure and DesignElement objects together in a single operation, set this option to tru