多站點(diǎn)help-英文版13章

Teamcenter10.1PLM00028JProprietaryandrestrictedrightsThissoftwareandrelatedationareproprietarytoProductLifecycleManagementSoftwareInc.?2013ProductLifecycleManagementSoftwareandthelogoaresofAG.TeamcenterisatrademarkorofProductLifecycleManagementSoftwareInc.oritssubsidiariesintheUnitedStatesandinothercountries.Allothertrademarks,s,orservicemarksbelongtotheirrespectiveholders.Multi-Proprietaryandrestrictedrightsnotice; 第1部分:GettingstartedwithMulti-Site 1BasicMulti-SiteCollaborationrequirements..................Beforeyoubegin.................................Multi-Sitebasicconcepts...........................Sharingproductdataacrossanenterprise...................Multi-SiteCollaborationsolution.......................Sites,facilities,andtheMulti-SiteCollaboration 2-Datareplication................................. 2-Usingmultipleattributesforobjectkeys(unique 2-Publishingandunpublishing 2-Objectownershipand 2-Globalorganizationobjects........................2-SystemsEngineeringVisio 2-Multi-Sitetransaction 2-Upgradingfromaprevious 3-Siteconsistencycheckandtheupgrade 3-PrepareaMulti-SiteCollaborationsitefor 3-Preventsiteconsistencyfailuresduring 3-UpgradingaMulti-SiteCollaboration 3-CompleteaMulti-SiteCollaborationsite 3-Generateupgradedsitedatasetmap 3-Version 3-2ConfiguringandadministeringMulti-SitePlanningand 4-Audience............................ 4-Advanced 4-Planningandsetup 4-Planning 5Siteinformationform.........................4-Setup 32 1Synchronization........................... 1Exportrecords............................ 1Multi-SiteCollaborationGuidedata_syncutility....... .5- 5-Enablingautomatic System 6-Systemadministration..................... 6-Best 6-Compatibilitywithearlier 6-Remotecheckinandcheckout 6-ItemID 6-Distributingsystemadministration 6-Controlledreplicationofstructurecontext 6-4thGenerationDesign 7-KeyconceptsofTCXML-baseddata 7-4thGenerationDesigndata 7-Traversal-free 7-Custom 8-Remoteprocedurecall 8-Configuringmultiplesitesonasingle 8-UsingMulti-SiteCollaborationthrougha 8-CustomizinganODS 8-Customizingdatasetexport 8-Troubleshooting 9-Troubleshootingguidelines..................... 9-Findingerrorcodesand 9-Error 9-Recoveringdataduetofailedtransferof 9-Workingwithlog 9-Postinstallation 9-Commoninstallation-related 9-Commonimport/export 9-ItemID 9-Windowsplatform Multi-SiteremoteprocedurecallmodedoesnotsupportSecurity Remoteinbox 第3部分:UsingMulti-SiteBestpracticesusingMulti-Site 10-BestpracticesusingMulti-Site 10-Publishingandunpublishing................. 11-Publishingand 11-Publishandsearchwithmultifield 11-Publishan 11-Unpublishan 11-Multi-SiteCollaborationpublish 11-Objectprotectionand 12-Objectprotectionand 12-Site Accesscontrolonreplica 12-Site Site Remoteimportandexport 13-Remoteimportandexport 13-Importandexport 14-Importandexport 14-Remote 15-Remote 15-Whentouseremotecheckin/checkoutovertransferofsite 15- RemoteCICOof Workingwithremote 15-RemoteCICOanddata_share 15-Errorrecovery 15-Importingremote Importingremote Remoteimportandtransferof 2Importremote 5Modifyingremote 1Modifyingremote 1Usingremotecheckinand 1Automaticremotecheckinandcheckoutforbaseline 9Sharingdatawithunconnected 1Sharingdatawithunconnected 1Updatinganobjector 1Updatearemote 1Updatearemote 1Updatearemote 1Updatearemote 1Usingremote 1Usingremote 1Subscribetoaremote 1Workingwiththedataassociatedwithtasksinyourremote 1Datareplication....... 23-Datareplication................................Usingsynchronization.............................Usingsynchronization.............................Datasynchronization..............................Automaticsynchronization...........................Configuringglobalcachingamong 1PrepopulateatargetFSCforglobal 1Supportforrequirementcontent........................Supportforrequirementcontent........................Glossary....................................A-1索引-圖Multiplesites...............................Unconnectedsites.............................Peer-to-peer................................Hierarchical................................Combination.................................FMSmaster–site 4-FMSmaster–site 4-subtypefromparentItem 9subclassfromparentItem 9site...............................9-site...............................9-site...............................9-site...............................9-site...............................9-site...............................9-site...............................9-site...............................9-site...............................9-Proxy 9-Target 18GettingstartedwithMulti-SiteCollaboration...............1-2-3-1BasicMulti-SiteCollaborationrequirements.............1-1Beforeyou 1BasicMulti-SiteCollaborationYoucanuseMulti-SiteCollaborationtoeasilyshareproductinformationacrossyourentireenterprise.Multi-SiteCollaborationallowstheexchangeofTeamcenterdataobjectsbetweendatabases.EachdatabaseshouldbeeasilyaccessibleusingTCP/IP,eitherovertheInternetoryourcompanyintranet.YoumustcoordinateconfigurationofMulti-SiteCollaborationwiththesystemadministratorsoftheotherTeamcenterdatabasesthatareparticipatinginyourMulti-SiteCollaborationenvironment.InformationaboutallparticipatingTeamcenterdatabasesitesmustbestoredineachdatabaseandineachsite’spreferencefile.Inaddition,youmustidentifythenetworknodesyouwanttorunMulti-SiteCollaborationserverprocessesforthesedatabasesandconfigurethosesystemstoruntheprocesses.您可以使用多站點(diǎn)協(xié)作來(lái)輕松地在您的整個(gè)企業(yè)共享產(chǎn)品信息。多站點(diǎn)協(xié)作使得TeamcenterTCPIP，或者通過(guò)互聯(lián)網(wǎng)或公司網(wǎng)絡(luò)。你必須協(xié)調(diào)與其他Teamcenter數(shù)據(jù)庫(kù)，參與你的多站點(diǎn)協(xié)作環(huán)境的系統(tǒng)管理員配置多站點(diǎn)協(xié)作。信息對(duì)所有參與Teamcenter數(shù)據(jù)庫(kù)信息必須在數(shù)據(jù)庫(kù)中的每個(gè)文件和每個(gè)的偏好。此外，您必須確定要運(yùn)行多個(gè)“坐”的網(wǎng)絡(luò)節(jié)點(diǎn)這些數(shù)據(jù)庫(kù)的協(xié)作服務(wù)器進(jìn)程，并配置這些系統(tǒng)來(lái)運(yùn)行進(jìn)程。Beforeyou YoudonotneedanyspecialpermissionstouseMulti-SiteCollaboration.YoumusthavesystemadministrationanddatabaseadministrationprivilegestoconfigureMulti-Site Assystemadministrator,youenableMulti-Site bysettingitupandconfiguringit.Thesetupand configurationrequiredisdeterminedbywhatdatayouintendtoshareandhowyouintendtosynchronizethedata.OnceMulti-SiteCollaborationissetupandconfigured,nofurtheractionisrequiredforyoutouseit. ThetasksrequiredtoconfigureMulti-SiteCollaboration dependonthehowthesitesthatparticipateareconnected, howdataiscoupledbetweensites,andotherThesearedeterminedduringplanningandsetupofyourMulti-SiteCollaborationnetwork.ForinformationaboutplanningandconfiguringMulti-SiteCollaboration,seeConfiguringandadministeringMulti-Site Multi-SiteCollaborationisaccessiblefromwithinthethinMulti-Siteclientorrichclientinterface.Multi-SiteCollaborationGuide1-2Multi-SitebasicconceptsSharingproductdataacrossan Multi-SiteCollaboration Sites,facilities,andtheMulti-SiteCollaboration Data Usingmultipleattributesforobjectkeys(unique Publishingandunpublishing Objectownershipand Globalorganization SystemsEngineeringVisio Multi-Sitetransaction

Multi-2Multi-SitebasicSharingproductdataacrossanToclearlyunderstandtheissuesinvolvedwithsharingproductinformationacrossanentireenterprise,considerhowtheXYZWidgetCorporationsharesdatawithoutthebenefitofMulti-SiteCollaboration.ThefollowingfigureshowsthattheXYZWidgetCorporationhasengineeringsitesinDetroitandLondon,amanufacturingsiteinDetroit,andrsinTokyoandS?oPaulo.Eachofthesesitescurrentlystorestheirproductinformationinseparatedatabases.(SaoPaulo MultipleDuringproductdevelopment,theengineeringsitesinDetroitandLondonoccasionallysharesmallamountsofdatawithoneanotherandwiththeirrsinS?oPauloandTokyo.Thisisplishedbymanuallyexportingproductinformationasobjects,transferringtheseobjectsusingFileTransferProtocol(FTP)orremovablemedia(DAT)tothedesiredsite,andmanuallyimportingthemintothedatabases.Afterproductdevelopmentcompletes,engineeringdataismanuallyexportedandtransferredtotheDetroitmanufacturingsiteandimportedintothatAlthoughthissolutioncanworkacceptablyonalimitedbasis,itrequirestoomuchlaborandtoomanyadhocarrangementstobeviableforroutinelysharinglargeamountsofproductinformationacrossthisenterprise.Multi-SiteCollaborationTheMulti-SiteCollaborationsolutionprovidessemiautomatedreal-timedatasharingacrosstheentireenterprise.Itautomatesmanyoftheoperationsthathadtobeperformedmanuallyinourfirstexample.UnconnectedPractical XYZWidgetsdecidestolinkboththeDetroitsitestheLondonandTokyositesusingahigh-speedwideareanetwork(WAN).TheyalsodecidethattherinS?oPaulowouldnotbesharingenoughproductinformationwiththeothersitestojustifyaWANconnection.UnconnectedsitesTheS?oPaulositeisnotconnectedtotheotherthroughalocalorwideareanetwork(LANorWAN).DatasharingwithS?oPaulomustbeplishedusingmanualexport,transfer,andimportasdescribedinourfirstexample.However,becausetheXYZWidgetCorporationhasimplementedaMulti-SiteCollaborationnetwork,sometrackingofobjectsintheS?oPaulodatabasemustbeperformedforthebenefitoftheothersites.ODSsite TheMulti-SiteCollaborationsolutionusesaspecialsitecalledanObjectDirectoryServices(ODS)site.TheODSsitemaintainsarecordofeachobjectintheentireMulti-SiteCollaborationnetwork.TheODSdoesnotstoretheobjects,itmaintainsarecordthatissimilartoalibrarycard;itlsyouwhichsiteiscurrentlystoringitandsomebasicinformationaboutitinformationsoyoucandecideifitistheobjectyouarelookingfor).Sites,facilities,andtheMulti-SiteCollaborationThreeverycommontermshaveveryspecificmeaningsinMulti-SiteCollaboration:sites,facilities,andnetwork.Thesearedefinedinthefollowingtable. Asingledatabaseandallusersthataccessthedatabase.Additionally,includesanynon-Teamcenterresourcessuchashardware,networkingcapabilities,andthird-partysoftwareapplications(tools)requiredtoimplementTeamcenteratthatsite. Aphysicallocation(forexample,manufacturingplant,designcenter,andsoforth)inyourenterprise.Donottoconfusesitesandfacilities.Sitesaredatabases;facilitiesarebuildings.Onefacilitycanhavemultiple Afederationofindependentsitesthatsharedatawithinthesameenterprise.Thougheachsiteisindependent,itisabletooperateonandsharedatawithintheMulti-SiteCollaborationnetwork.Multi-SiteCollaborationintentionallyimposesasfewrestrictionsandlimitationsonautonomoussiteactivityaspossible.DataDatareplication,throughimportandexportfunctions,isthefoundationofMulti-SiteCollaboration.Incontrast,mostotherdistributedsolutionssimplyexportacopyofanobjectintoaremoteapplicationsmemoryandeitherdiscarditwhentheapplicationexits,orsaveitbyreimportingthenewversionbackintotheoriginaldatabase.Thelatterapproachhastheadvantageofusinglessdiskspacebecauseeachobjecthasonlyonediskcopyintheentirenetwork.However,itresultsinpoorperformancebecausetheobjectmustbetransmittedoverthenetworkeverytimearemoteuserwantstoaccessit.ThedatareplicationapproachusedbyMulti-SiteCollaborationdoesusemorediskspacebecauseobjectsarereplicatedatvarioussites.However,afteranobjectiscopiedtoanothersite,accessisasfastasanyotherobjectinthelocalAreplication-baseddistributedsolutionmustaddressthefollowing DataintegrityAsanobjectisreplicatedtovarioussites,howdoyoudeterminewhichobjectisthelatestversionofanobject?Thisisespeciallytrueifusersareallowedtomodifyreplicated SecurityWithoutpropersecuritycontrols,replicatedproductinformationcouldfallintothehandsofpeoplenotauthorizedtohaveit.Auditingand

Areplication-basedsystemmustprovidesomemethodoftrackingallreplicasofanobjectnotonlyforauditpurposes,butalsoforensuringthatallreplicasareupdatedwhentheoriginalismodified. Multi-SiteCollaborationaddressestheseconsiderationsbyimposingthefollowingrulesonobjectreplication:Onlythemasterobjectcanbereplicated.Youcannotreplicatereplicas.Whenanobjectisinitiallycreatedandsavedinadatabase,thatinstanceisconsideredthemasterobjectuntilsuchtimeasitisexportedwithtransferofownership.AnexceptiontothisruleistheMulti-SiteCollaborationhubconfiguration.OnlythemasterobjectcanbeAllreplicasofthemasterobjectareread-only.ThisWhenyouexportanobject,youmustspecifywhichsitesareauthorizedtoimportit.Thisensuresthatnounauthorizedreplicasaremadeandstorestrackinginformationwiththemasterobject.Whentransferringownershiptoanothersite,onlyonesitecanbespecified.ThisensuresthatthereisonlyonemasterobjectintheAfteritisreplicated,amasterobjectcannotbedeleteduntilallreplicasaredeleted.Thisensuresnetwork-widereferentialAreplication-basedsolutionmustensurethatreplicasarekeptup-to-datewhenthemasterobjectismodified.Multi-SiteCollaborationaddressesthisbymaintainingexportrecordsandprovidingsynchronizationfacilities. ExportrecordsWhenanobjectisexported,exportrecordsareforeachtargetsitespecified.EachexportrecordcontainsthesiteIDofeachtargetsiteandthedateofthelastexporttothatsite.Exportrecordsarealwaysassociated(andstored)withthemasterobject.Foritems,aspecialItemExportrecordisalsocreatedtorecordtheimport/exportoptionsusedsothatthesesameoptionscanbeusedtosynchronizetheitem.data_syncutilityWhenyoumodifyamasterobject,usethisutilityupdateanyreplicas.Youmusthavesystemadministratorprivilegestousethisutility.Theprocessofkeereplicateddataup-to-dateiscalledsynchronization.Optionally,synchronizationmaybelimitedtovisualizationdatathatisdirectlyorindirectlyrelatedtodatasets.Forinformationaboutthisutility,seetheUtilitiessync_on_demandutilityYoumayupdatereplicatedobjectsastheyusingthisutility.Youcanselectacomponent,assembly,orobjectforasynchronizationreportthatallowsyoutodetermineifsynchronizationisrequiredandtoselectthespecificcomponentstosynchronize.Forinformationaboutthisutility,seetheUtilities

userwhoreplicatesanobjectmayspecifythatthereplicabesynchronizedautomaticallywhenthemasterobjectismodified.ThereplicaisthensynchronizedautomaticallyusingtheMulti-SiteCollaborationautomaticsynchronizationUsingmultipleattributesforobjectkeys(uniqueMulti-Sitesupportsmultifieldkeydefinitionsforobjectsthatittransfers.Multifieldkeysareidentifiersassignedtoeachobjecttoensuretheiruniquenessinthedatabase.Teamcenteradministratorscanaddmultiplepropertiestodefineakey.Themultifieldkeyiscomposedofaname(thenameofthebusinessobjecttype)andacombinationoftheobject’sproperties.Thisensuresauniqueidentifieracrossalltheobjectsinthe.YouconfiguremultifieldkeysforobjectsusingtheBusinessModelerIDE.Formoreinformationaboutmultifiedkeysandtheiruse,seetheBusinessPublishingandunpublishingParticipatingsitesinadistributednetworkmusthaveareliablewayofcontrollingwhichdatatheywanttosharewiththerestofthenetwork.WithMulti-SiteCollaboration,youcanpublishandunpublishobjectseithersinglyorinabatch. Publishinganobjectmakesthatobjecttoothersites.Whenyoupublishanobject,apublicationrecordiscreatedintheODSthatcanbereadandsearchedbyothersites.Untilyoupublishanobject,itcanonlybeseenbythelocalowningsite;othersitesarenotawarethatitexists.UnpublishingUnpublishinganobjectreversestheprocedure.Theobjectaccessibleonlybythelocalowning ObjectownershipandInanormal(forexample,nondistributed)environment,theownershipandprotectionofobjectsisstraightforwardandgenerallytransparenttousers.However,inadistributedenvironment,thelevelofcomplexityisgreatlyincreasedinordertoextendobjectprotectionacrossanentirenetwork.InadditiontothefamiliarconceptsofowninguserandowningMulti-SiteCollaborationusestheconceptofsiteownership.Theowningsiteisthesitewherethemasterobjectresides.ItistheonlysitewheretheobjectcanbemodifiedorwhereyoucanobtainareplicatedcopyofthemasterTheowningsiteisapropertyofanyobject,andtheowningsitecanbefoundusingthePropertiesdialogbox.Whenanobjectisreplicatedbyaremotesite,theowningsitepropertygoesalongwithit.However,otheraspectsofaccesscontrolmayvaryforeachreplicaaccordingtotheenvironmentofthereplicating(thatis,remote)site.Thefollowingdescribesaccesscontrolonreplicas:Allreplicasareread-onlyobjects,regardlessofwhetherthesiteusesrules-basedorobject-basedprotection.Whenanobjectisreplicated,theowninguserandowninggroupforthereplicaaredeterminedasfollows:IftheowninguserandowninggroupofaMasterobjectarebothdefinedattheimportingsite,theimportedcopy(replica)isownedbythisuserandgroupfollowingtheimport.Theownershipisfullyp.IfeithertheowninguserorowninggroupofaMasterobjectisnotdefinedattheimportingsite,theimportedcopy(replica)isownedbytheuserperformingtheimport;theowninggroupisthatuser’scurrentgroupatthetimeoftheimport.IftheTC_retain_group_on_importthispreferenceisdefinedandsettoTRUE,andtheowninggroupisdefinedattheimportingsite,theoriginalowninggroupisp.sitetoanother.Ifthegroupsetinthispreferenceisnotdefinedattheimportingsite,thispreferencehasnoeffectandthegroupissettothedefaultgroupoftheuserngtheimport.Whenanobjectisexportedfromasiteusingtraditionalobject-basedprotection(thatis,notusingrules-basedprotection)andimportedintoasiteusingrules-basedobjectprotection,accesscontrolsattheimportingsiteapply(subjecttothelimitationthatremoteobjectsarealwaysread-only).Thisistrueregardlessofwhethersiteownershipistransferredornot.Siteautonomypermitted:Multi-SiteCollaborationimposesasfewrestrictionsandlimitationsonautonomoussiteactivityaspossible.Thisincludesobjectprotectionandownership.Sitesarenotrequiredtodefineusersfromothersitesintheirdatabase,andeachsiteisfreetochoosetheobjectprotectionscheme(object-basedorrules-based)usedattheirsite.Furthermore,ifrules-basedobjectprotectionisused,eachsiteisfreetodefinetherulesineffectattheirsite.Siteunitymended:Poftwaremendsthatallsitesuserules-basedobjectprotectionanddefinesimilarrulessothcesstosharedobjectsisuniformacrosstheentireMulti-SiteCollaborationnetwork.Definingaconsistentsetofusersforallsitesismendedwheneverpossible.GlobalorganizationYoucandefineorganizationalobjects(Group,Role,User,,andGroupMemberclassobjects)andthenreplicatethemthroughoutyourMulti-Siteenvironmenttoprovideaglobalorganization.AglobalorganizationallowscentralizedadministrationfororganizationdatausingMulti-SiteCollaborationtechnology.Youselectacentralsiteinyourenvironmenttostorethemastercopiesoforganizationdataandtheothersitescontainread-onlyreplicas.Youcanmakechangesatthemastersiteandsynchronizethereplicasattheothersites.GlobalorganizationobjectscanbeimportedandexportedmuchthesameasotherTeamcenterobjects,withtheexceptionthattheycannothavetheirownershiptransferredtoanothersitefromthemastersite.InanexistingMulti-Siteenvironment,sitesmaycontainidenticalorganizationstructures(clonedorganizationobjects).Thesemustbemigratedtothereplicatedmodeltoestablishatrueglobalorganization.Forinformationaboutmigratingclonedorganizationobjectstoreplicatedobjects,seeMigratingorganizationobjects.attribute.Thisattributedefinestheworkingsitefortheobjectwhichisthesitewheretheuserphysicallyworks.Usersthatworkattheowningsitefortheglobalorganizationobjectsmayhaveanullvalueforthisattribute.Thehomesiteattributeisusedtodeterminetheworkingsiteofauserorgroupinaglobalworkflow.Basedonthisattributeanassignedtaskisdeliveredtoaremoteuserathisorherworkingsite.TheUserclassobjectalsohasaremote_sites_deny_loginattribute.Userscannotpermittedtologontotheirhomesite.Amasterobjectcannotbedeletedifanexportrecordexistsfortheobjectindicatingtheobjecthasbeenexported(replicatedatanothersite).Replicaorganizationobjectscannotbemodified,thereforeifanexportrecordexistsforanorganizationobjectitcannotbemodified.Forobjectsthathavebeenmigrated,noexportrecordexists,howeverallobjectsthatcanbereplicatedhaveanowning_siteattribute.Thisattributepreventsmodificationofreplicasformigratedobjects.Tochangereplicatedorganizationobjects,youmustmodifythemasterobjectandsynchronizethereplicastopickupthechanges.Youcansynchronizeorganizationobjectsusingthedata_syncutilityorbyre-exportingtheobjecttotheremotesitesfromtheOrganizationapplication.Synchronizationisbasedonthelastmodifieddateoftheselectedobjects.YoucsoreplicateorganizationobjectsfromtheOrganizationapplicationbyselectingtheobjectandchoosingTools→Export→RemoteExport.Formoreinformation,seetheThefollowingpreferencesarerelatedtoreplicatingorganizationobjectsareabletoexistalonewithoutrelatedobjects.Therefore,notraversaltorelatedobjectsisperformed.RoleobjectsowntheirGroupMemberobjects.Whenroleownershipistransferred,allofitsGroupMemberobjectsaretransferred.ItisnotpossibletoaddaUserobjecttoareplicaRoleobjearesultofthisDesignThedatabaseadministrator(DBA)groupandDBArolecannotbeexportedthroughMulti-SiteCollaborationormigratedDesignUserscanbeassignedtoprojectteamsinconjunctionwithexistingTeamcenterorganizationalroles.Inaglobalorganizationenvironment,youcannotexportormigratetheprojectteamassignments.UserobjectsarealwaysexportedwiththeirdefaultGroupMemberobject.ThereisanoptiontosendallofitsGroupMembersobjects.ThegroupandrolefortheGroupMemberobjectmustalreadyexistatthetargetsite,otherwisetheexportfails.SystemsEngineeringVisioYoucantransfercontainingSystemsEngineeringVisiodiagramsusingMulti-SiteCollaboration.TheimageanddatasetobjectsassociatedwiththediagramareexportedalongwithanyrelationshipobjectsdefinedforVisiodiagramsintheTC_relation_required_on_exportpreference.Youcanexportdiagramsforreference(replicas)orwithownershiptransfer.However,forownershiptransfers,onlythelatestrevisionistransferred.ThefollowingdiagramobjectsandrelationsareImagedatasetwithattachesrelationshipVisio(Fnd0Visio)datasetwithattachesrelationship(TC_Attaches)POM_objectclassobjectswithshaperelationship(Fnd0ShapeRelation)Thefollowingcaveatsapplytoexporteddiagrams:Diagramtemplatesarenottransferredduringdiagramexports.Youmustexporttheassociateddiagramtemplateseparay.Adiagramwithstubobjectsoronethatisnottherootstructureoftheexportcannotbeopenedattheimportingsite.ForinformationaboutVisioexportingSystemsEngineeringdata,seeMulti-SitetransactionTeamcenterlogsMulti-Siteimportandexporttransactionsthatincludeexportandimportobjectcounts,thetimetakenforeachoperation,andacorrelationIDforeachrequestintheadministrator’ssyslogfile.YoucanconfigurethepriorityofMulti-SiogmessagestothestandardTeamcenterlevels(FATAL,ERROR,WARN,INFO,DEBUG,andTRACE).ForinformationaboutthecorrelationID,seeUsingtheMulti-SiteForinformationaboutsettingtheloglevel,seeConfiguringtheMulti-Site3Siteconsistencycheckandtheupgradeprocess................PrepareaMulti-SiteCollaborationsiteforupgrade.............Preventsiteconsistencyfailuresduringupgrade...............UpgradingaMulti-SiteCollaborationsite...................CompleteaMulti-SiteCollaborationsiteupgrade...............Generateupgradedsitedatasetmapfiles.................Versioninteroperability.............................SiteconsistencycheckandtheupgradeBeginningwithTeamcenter9.1,TeamcenterEnvironmentManager(TEM)runstheensure_site_consistencyutilityduringupgradeofaMulti-SiteCollaborationsite.Thisavoidsfailureordelaysduringupgradeduetopotentialdataintegrityissues.Becausetheupgradeprocessrequiresthesitetobeunavailableduringtheprocess,resolvinganyissuestheensure_site_consistencyutilityencounterspriortostartingtheupgrademinimizesthesitedowntime.PrepareaMulti-SiteCollaborationsiteforCheckforandrecovertransactionfailuresresultinginunrecoveredtransferlockstwoorthreedayspriortotheupgradingthesite.Allservicescancontinuetorunduringthisprocess.Runtheensure_site_consistencyutilitywiththereportfunctionattheupgradeensure_site_consistency-u=infodba-p=infodba--f=report-search-Checktheoutputfileforpossibletransfer**CommandlineoptionusedtogeneratetheReport-f=report-search-report=myReport.txtObjectsFound:0ObjectId/NameClassNameof Owning – Class Owning Atthissite,run-f=recovery- Atthissite,run-f=recovery-Ifyoufindpossiblefailures,useanSQLcommandtoquerythecreationdateoftheSSTrecoverydatasets(TC_sst_record),forexample:selectpcreation_date,rsecondary_objectufromPIMANRELATION,PPOM_APPLICATION_OBJECTpaowherersecondary_objectu=pao.puidandrrelation_typeu=(selectpuidfromPIMANTYPEwhereptype_name=’TC_sst_record’)orderbypcreation_date;TheoutputofthisqueryshowsthecreationdataforeachSSTdatasetandthedatasetuniqueidentifier(UID),forexample:2013–02–202013–02–282013–02–28Thetimeperiodfordetermininganactiveorabortedtransactionisbasedontheassumptionthatonlypartsormoderate-sizeassembliesareselectedforexportwithtransferofownership.Exportingaverylargeassemblywithownershiptransfer,suchasanentirevehicle,isnotanexpectedormendedpractice.IftheSSTdatasetcreationdateiswithinthelast24hours,youmayignorethetransactionasitmaybeactiveandshouldcompletepriortothestartofthescheduledupgrade.hasaborted.Toavoidthedelaycausedbyopentransferlocksduringtheupgradeoperation,runtheensure_site_consistencyutilitywiththerecoveryfunction:ensure_site_consistency-u=infodba-p=infodba--f=recovery-search-Optionally,youcanrunthiscommandaftertheupgradeoperationcompletes.However,thismaycausedelaysduringtheupgradeandrequiresanadministratortomonitortheprocessforrequiredactions.Poftwarehighly mendsthatyoudonotdefertherecoveryoftransferlocks.DuringthePrevent instructedtoremovealltransferlocks.Thereisapossibilityofobjectschangingduringthetimethatthetransferlocksaremissing.Runningtherecoveryfunctionatthistimeminimizesthetimeperiodtheobjectsareexposedtotheriskoftheobjectsbeinglockedbyaprocessotherthantheupgradeprocess.PreventsiteconsistencyfailuresduringTwenty-fourhoursbeforeperformingthesesteps,informyourusersthatMulti-SitetransfersareprohibitedpendingthecompletionoftheupgradeprocessandshutdowntheIntegratedDistributedServicesManager(IDSM)andObjectDirectoryencounteredduringtheupgradeorthatyoumayhavet