多站点help 英文版多站点4章 1

Configuringandadministering Multi-SiteCollaborationPlanning and setup . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1System administration . . . . . . . . . . . . . . . . . . . . . . . . 6-14th Generation Design data . . . . . . . . . . . . . . . . . . . . . 7-1Custom configurations . . . . . . . . . . . . . . . . . . . . . . . 8-1Troubleshooting reference . . . . . . . . . . . . . . . . . . 9-1第4章PlanningandsetupAudience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Advanced concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Integrated Distributed Services Manager (IDSM) . . . . . . . . . . . . . . 4-1ODS and IDSM daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Using remote procedure call (RPC) . . . . . . . . . . . . . . . . . . . . . 4-2ISO/OSI network model . . . . . . . . . . . . . . . . . . . . . . . 4-3Sharing write access to shared data . . . . . . . . . . . . . . . . . . . . 4-3 Transferring site ownership . . . . . . . . . . . . . . . . . . . . . . . 4-3Remote checkin and checkout . . . . . . . . . . . . . . . . . . . . 4-4Multi-Site Collaboration records . . . . . . . . . . . . . . . . . . . 4-4Planning and setup process . . . . . . . . . . . . . . . . . . . . . . . 4-5Planning considerations . . . . . . . . . . . . . . . . . . . . . . . 4-5Determining how to share data . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Site coupling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Planning your network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Structured context object caching . . . . . . . . . . . . . . . . . . . . . 4-8Connecting external sites using a hub site . . . . . . . . . . . . . . . 4-10Synchronizing replicas . . . . . . . . . . . . . . . . . . . . . . . 4-11Working sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Working site guidelines . . . . . . . . . . . . . . . . . . . . . . . . 4-12Determining IDSM server node requirements . . . . . . . . . . . . . . 4-12Object directory services (ODS) sites . . . . . . . . . . . . . . . . . . 4-13Object Directory Services . . . . . . . . . . . . . . . . . . . . . . . 4-13 Number of Object Directory Services sites required . . . . . . . . 4-14ODS network bandwidth and server node requirements . . . . . . . . 4-15Adjusting the network for your work patterns . . . . . . . . . . . . . . 4-16Configuring a central library . . . . . . . . . . . . . . . . . . . . 4-17Additional requirements for existing sites . . . . . . . . . . . . . 4-17Site naming conventions . . . . . . . . . . . . . . . . . . . . . . . . 4-18Multi-Site Collaboration license considerations . . . . . . . . . . 4-18Distributed User license . . . . . . . . . . . . . . . . . . . . . . . 4-19Working site security considerations . . . . . . . . . . . . . . . . 4-20ODS site security considerations . . . . . . . . . . . . . . . . . . . 4-23Replica file management considerations . . . . . . . . . . . . . . . 4-23Transfer of site ownership security considerations . . . . . . . . 4-24 Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Access rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Remote checkout/checkin security considerations . . . . . . . . . . 4-25Using preferences to control remote checkout access . . . . . . 4-25Using access rules to control remote check out access . . . . 4-26Remote checkout privilege access . . . . . . . . . . . . . . . . . 4-26Supporting multiple languages . . . . . . . . . . . . . . . . . . . . 4-26Multi-SiteCollaborationGuideSite information form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27Setup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32Determining the setup process . . . . . . . . . . . . . . . . . . . . . . . 4-32Configure Multi-Site Collaboration sites . . . . . . . . . . . . . . . . 4-33Configure FMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33Configure global data caching . . . . . . . . . . . . . . . . . . . . . . . 4-35Set up a hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35Create remote site definitions . . . . . . . . . . . . . . . . . . . . . . 4-37Synchronizing POM transmit schema files . . . . . . . . . . . . . . . . . 4-37Configure a multiprocess ODS . . . . . . . . . . . . . . . . . . . . . . . 4-37Setting up partial item export . . . . . . . . . . . . . . . . . . . . . . 4-38Pull versus push strategy . . . . . . . . . . . . . . . . . . . . . . . . . 4-39Using revision selectors . . . . . . . . . . . . . . . . . . . . . . . . . 4-40Synchronizing specific revisions . . . . . . . . . . . . . . . . . . . . . 4-40Synchronizing a single site versus multiple sites . . . . . . . . . 4-41Synchronizing a single class and multiple classes . . . . . . . . . 4-41Synchronizing by class or file name . . . . . . . . . . . . . . . 4-42Synchronizing assemblies or individual items . . . . . . . . . . 4-42Synchronizing modified objects only . . . . . . . . . . . . . . . 4-42Setting up data compression . . . . . . . . . . . . . . . . . . . . . . 4-43On-demand synchronization . . . . . . . . . . . . . . . . . . . . . . . . . 4-44ODS security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44Configure remote inboxes . . . . . . . . . . . . . . . . . . . . . . . . . 4-45Multi-SiteCollaborationGuidePLM00028 JPlanningandsetup第4章PlanningandsetupAudienceThis information is intended for system administrators and other persons concerned with planning and setting up a Multi-Site Collaboration network. Other users need not be concerned with this information. Siemens PLM Software strongly recommends that anyone setting up a Multi-Site Collaboration network thoroughly review all planning considerations before performing any setup procedures.With Multi-Site Collaboration you can set up a network of sites that can share data among one another on an as-needed basis. One of the primary concerns when using Multi-Site Collaboration is ensuring that the system is configured and maintained properly. This information is intended to provide some practical guidelines that you, as a system administrator, can use to plan your Multi-Site Collaboration network.AdvancedconceptsIntegrated Distributed Services Manager (IDSM)Multi-Site Collaboration solution discusses the concept of the Object Directory Services (ODS) and the role it plays in a Multi-Site Collaboration environment. Another fundamental component of Multi-Site Collaboration is the Integrated Distributed Services Manager (IDSM). While the ODS can be considered an object locator, the IDSM can be thought of as an object transporter. It provides the mechanism used to export an object from the owning site, transmit it over the network, and import it into the destination site. The IDSM functions the same when configured for remote procedure call (RPC) or HTTP/HTTPS communications except that there are no separate IDSM daemons as this functionality is part of the tcserver process. The calling sites logging functionality is the same for when using HTTP/HTTPS. However, logging that is done within the remote sites IDSM process for RPC communications is handled by the remote sites tcserver process when using HTTP communications. The content is the same but the log information is sent to the tcserver log file.ODS and IDSM daemonsThe ODS requires a server process or daemon. When using RPC communications, the IDSM also requires a daemon. The network nodes that run these daemons are referred to as the ODS or IDSM server node, respectively.The ODS daemon is started by the run_tc_ods script and runs until the process is killed or the ODS server node is shut down. There is only one ODS daemon per ODS and it auto-logs on to the ODS database using the administrator user (infodba by default) account.The IDSM daemon is dynamically started using the run_tc_idsm script and runs until it has accomplished its task of transporting a set of objects from one site to another. It then transitions to a dormant state for about two minutes, then terminates if it is not reused for another request.You can have more than one IDSM daemon running on the same IDSM server node at a time. One IDSM daemon is required for each Multi-Site Collaboration request to deliver an object. This is an important factor to consider when configuring an IDSM server node.Each IDSM daemon logs in automatically to the working site database that it serves using the administrator user account. For sites using rules-based object protection, Siemens PLM Software recommends that this user account be changed to a special account (for example, IDSM) so that the IDSM daemon runs under the context of a user that can be controlled. This technique makes it possible to define rules based on the IDSM user account for maximum security.Using remote procedure call (RPC)When you configure Multi-Site Collaboration to use remote procedure call (RPC) technology for host-to-host communication, it is an important part of the setup process to ensure that the RPC software on your systems is operational outside of Multi-Site Collaboration.The rpcinfo utility can be used at the operating system level to determine if the RPC software is operational. The following examples show how to use this utility: rpcinfo -p node_nameThis returns a list of RPC programs running at the specified node. For example:ProgramVersionProtocolPortService1000004TCP111Portmapper1000003TCP111Portmapper5368755251TCP1035Not applicableIf no results or an error is returned, the RPC software was not installed correctly.If the Multi-Site Collaboration daemons are running, you should see some entries with the program numbers ending in 85 and 86. Those that end in 85 are used by the ODS daemon and those that end in 86 are used by the IDSM daemon. For example:ProgramVersionProtocolPortService5368755861TCP1035NotapplicableProgramVersionProtocolPortService5368755851UDP1761Not applicable5368755851TCP2021Notapplicable rpcinfo -T tcp node_nameprogram_numberversion_numberNote On some platforms, the syntax of this command requires a lowercase t as in rpcinfo -t.Use this to test whether a daemon is ready, for example:program 536875586 version 1 ready and waitingIf the daemon is not ready, the following message is returned:rpcinfo: RPC: Unable to receive; An event requires attention program 536875586 version 1 is not availableISO/OSI network modelMulti-Site Collaboration integrates into the 7-layer ISO/OSI network model as follows: The Multi-Site Collaboration software resides in layer-7 (application layer). The RPC software resides in layer-5 (session layer). Multi-Site Collaboration also uses TCP and UDP protocols for layer-4 (transport layer).Any networking enhancements below the transport layer (layer-4) are transparent to Multi-Site Collaboration. For example, you can use data compression and encryption enhancements with Multi-Site Collaboration without any changes to the software or the way it is installed.Sharing write access to shared dataData sharing does not involve modifying the shared data. Sites replicate a part for use as an assembly component with no intention of modifying the part itself. However, there are cases when a remote site must modify data owned by another site. In these situations, Multi-Site Collaboration provides two methods for sharing write access to shared data: transferringownershipandremotecheckinandcheckout.Transferring site ownershipThe remote site imports the object with transfer of site ownership. For items, this requires transferring site ownership of all revisions and most attachments and files. For item revisions with sequences, all sequences are transferred along with the sequence manager. Previous sequences are deleted from the transferring database. When the remote site gains ownership ofan item, the item can be modified. When all modifications are made, site ownership is transferred to the original owning site or to any site that must modify the data.Ownership access by remote users is controlled by the owning site using preferences and access management rules.If an item owned by Site1 is replicated to Site2, and the items site ownership is transferred to Site3, the site ownership of the replica at Site2 is not updated to show the new owning site. Using the data_sync utility at Site3 does not update the replica at Site2, since the last modification date of the master copy at Site3 has not changed. It is not necessary to sync the owning site property because the replica at Site2 has not changed. To sync the replica at Site2, run the data_share utility at Site3 or perform a remote import at Site2.Remote checkin and checkoutThe remote site checks out the object by first replicating the item, then checking out the specific portion of the item requiring modification, for example an attached dataset. When the replica is checked out, a remote checkout is performed at the items owning site ensuring no other user in the Multi-Site Collaboration network can modify it.When all modifications are made to the replica, it is checked in to the owning site. All changes are sent to the owning site and the remote check out status is removed. Any new objects created are owned by the items owning site.This method avoids transferring site ownership of an entire item when write access is required only for portions of the item. For performance reasons, Siemens PLM Software recommends using this method whenever possible.NoteFor information regarding the types of data modifications available using remote checkin and checkout functionality, see Modifyingremoteobjects.Multi-Site Collaboration recordsMulti-Site Collaboration uses replication to share data. This increases the need for keeping track of which sites have a copy of an object and when the copy was made. This information is stored in an Import Export Record (IXR). The IXR is a database object that is created during export and is attached to the master copy. When the master copy is modified, the information in the IXR is used to determine which copies must be synchronized.The information in the IXR is also used to generate the Exported To property of a Teamcenter object. If you must see the information stored in an IXR, which includes the export reason, you can create a custom query on the ImanExportRecord class.A similar concept applies when publishing an object to an ODS. When an object is published, a Publication Audit Record (PAR) is created and attached to the master copy. The information in the PAR is used to determine if an object needs to be republished, for example, when the objects description is modified. If you must view the information stored in a PAR, you create a custom query on the PAR class.Both the IXR and PAR objects reference the object they are attached to. This reference prevents the master copy from being deleted, ensuring network-wide referential integrity. To delete a master copy, the IXRs and PARs must be deleted first. PARs are deleted by unpublishing the object while IXRs are deleted using the -verify argument of the data_sync utility. For additional information, see the UtilitiesReference.Planning and setup processThe following table provides the preferred sequence of tasks for setting up a Multi-Site Collaboration network.TaskDescriptionReview planningReview the Planningconsiderations. This helps you considerationsdecide if Multi-Site Collaboration is the best data sharing solution for your enterprise and helps you plan your Multi-Site Collaboration network.Fill out site information Fill out one site information form for each site you forms intend to include in your entire (enterprise-wide)Multi-Site Collaboration network. For more information, see Siteinformationform.Configure Multi-Site Configure your working sites and at least one ODS Collaboration sites site according to the instructions found in the installation manual for your platform.For information about setting up sites, see Setup procedures.Synchronize siteSynchronize all site definitions by adding all site definitionsdefinitions in the entire Multi-Site Collaborationnetwork to all Multi-Site Collaboration databases.Synchronize POM transmit Distribute a copy of each sites POM transmit schema files schema file to each site in the Multi-SiteCollaboration network.Planning considerationsDetermining how to share dataThe optimum Multi-Site Collaboration configuration varies greatly from enterprise to enterprise. When implementing an enterprise-wide Teamcenter solution for your enterprise, it is easiest to use a single database for all users. However, when your enterprise comprises multiple facilities in different geographic regions, you must consider some sort of distributed Teamcenter solution.It is possible to share data with various sites through the rich client import and export functions. This solution is effective if you only share small amounts of data on a periodic basis. However, if you want to share large amounts of data on a regular basis you should consider using Multi-Site Collaboration.Multi-Site Collaboration provides the publishing and system administration features needed to reliably share large amounts of data on a regular basis. Users can routinely search for and view data stored at other sites.Site couplingTeamcenter sites can be grouped into the following broad categories:Site categoryDescriptionLoosely coupledLoosely coupled sites typically have little in commo