site_consolidation_guide.pdf - Teamcenter 10.1 Site Consolidation Guide Publication Number PLM00142 F Proprietary and restricted rights notice This

site_consolidation_guide.pdf - Teamcenter 10.1 Site...

This preview shows page 1 out of 300 pages.

You've reached the end of your free preview.

Want to read all 300 pages?

Unformatted text preview: Teamcenter 10.1 Site Consolidation Guide Publication Number PLM00142 F Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management Software Inc. © 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved. Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter is a trademark or registered trademark of Siemens Product Lifecycle Management Software Inc. or its subsidiaries in the United States and in other countries. All other trademarks, registered trademarks, or service marks belong to their respective holders. 2 Teamcenter Site Consolidation Guide PLM00142 F Contents Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2 Getting started with site consolidation . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Overview of the site consolidation process . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 High-level technical considerations for site consolidation . . . . . . . . . . . . . . . . 1-5 Basic concepts for using site consolidation . . . . . . . . . . . . . . . . . . . . . . 2-1 Process definition assumptions . . . . . . . . . . . . . Site consolidation phases . . . . . . . . . . . . . . . . . . Planning cleanup and volume relocation activities Global Services orchestration . . . . . . . . . . . . . . . Site consolidation tools and utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-2 2-5 2-5 2-8 Preparing for site consolidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Deploying Teamcenter components . . . . Making site definitions compatible . . . . Planning increments . . . . . . . . . . . . . . Detecting and repairing data anomalies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 3-2 3-21 3-25 Execution phase activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Execution phase increments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replicating data and changing ownership in a typical execution phase increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Consolidating using multiple execution phase increments . . . . . . . . . . Replication phase activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time critical period activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 . . . . . . . . . . . . . . . . . . . . 4-1 4-2 4-2 4-5 Cleanup phase activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Determining when to perform cleanup activities . . . . . Resolving issues after moving consolidation information Cleaning up the target site . . . . . . . . . . . . . . . . . . . . Cleaning up the ODS . . . . . . . . . . . . . . . . . . . . . . . . Cleaning up third sites . . . . . . . . . . . . . . . . . . . . . . . Cleaning up the source site . . . . . . . . . . . . . . . . . . . . Determining final cleanup steps . . . . . . . . . . . . . . . . . .. . .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 5-1 5-2 5-3 5-3 5-4 5-5 Site consolidation utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 Shared FMS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Prerequisites for a shared FMS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Configuring the shared FMS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 Standard FMS configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 PLM00142 F Teamcenter Site Consolidation Guide 3 Contents Shared FMS slave and master sites . . . . . . Create master and slave configurations . . . Install the shared network configuration file Create shared volumes . . . . . . . . . . . . . . . Auditing affected sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4 B-5 B-6 B-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 Using audit components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1 Considering infrastructure issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 Planning for recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Performance tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 Using database statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5 File system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5 Using log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 Log file names and locations . . . . . . . . . . . . . Utility debug options and default file locations TIE_DEBUG environment variable . . . . . . . . Sample run of tcxml_import low-level . . . . . . . Orchestration data transfer log files . . . . . . . . Orchestration change ownership log files . . . . Global Services tables cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1 E-1 E-2 E-4 E-6 E-7 E-8 Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1 Can site consolidation utilities be used with 4th Generation Design data? . . . . F-1 How are unmodifiable 4th Generation Design properties handled during import? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1 What can be done if the replication process aborts because special characters are encountered during mapping? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3 Will site consolidation work across multiple releases? . . . . . . . . . . . . . . . . . . F-3 What out-of-the-box data model coverage is available in Teamcenter 9.0? . . . . F-3 What out-of-the-box data model coverage is available in Teamcenter 8.3? . . . . F-4 What out-of-the-box data model coverage is available in Teamcenter 2007.2? . . F-5 What does the term site definition data include, which must be addressed during the preparation phase? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-7 How are scalability and performance impacted by island size? . . . . . . . . . . . . F-8 Why do we need the fix_release_status, clean_up_shared_objects, and sitcons_fix_ixr utilities? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-8 What are closure rules? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9 What happens when a network loss or outage happens during site consolidation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9 What can be done if replication aborts because sitcons_replicate_mgr mapping fails when special characters, such as illegal XML 1.0 characters, are encountered? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-9 How can I override the default delimiter in TC XML for string variable length arrays (VLAs)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10 When you transfer ownership of data having subscription, does the subscription get transferred along with it? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10 How do you determine whether unreferenced objects are orphaned? . . . . . . . F-10 How do you transfer objects not referenced by an item but by a folder? . . . . . F-10 How do I configure the Global Services URL for site consolidation . . . . . . . . . F-10 4 Teamcenter Site Consolidation Guide PLM00142 F Contents When a Teamcenter Web user accesses data (after consolidation) in a remote location with a volume nearby, does the data need to be transferred through the Web server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10 Can the file client cache (FCC) recognize cached data if the FMS ticket is from a different server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-11 What happens to replicated files when a site is consolidated after a period of data exchange? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-11 Can we use volumes located near remote (former source) sites to increase operational speed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-11 When does the database fail? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-11 What is the process of deleting files from the source site if files on the target site are up to date? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-11 What impact do the database tuning guidelines have on the production database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-12 What can be done when using the sitcons_replicate_mgr and there is failure to connect? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-12 What happens when an object’s User/Group profile is not found in the target database during import? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-13 How do I identify the failure point when the accountability table trigger creation fails without error information? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-13 Why do I get an FSC proxy error when I access a volume in a shared FMS environment? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-13 How do site consolidation closure rules handle incremental change elements? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-13 How do I resolve an import failed error that indicates the last_mod_user was not found in the database for a workspace object? . . . . . . . . . . . . . . . . . . . . . . F-14 Why is my custom form object exported in a different island by itself? . . . . . . F-14 Why does Global Services fail on import and display an XML/XSL file for import/export is invalid error? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-15 Why does sitcons_replicate_mgr utility not submit some requests? . . . . . . . . F-15 Global Services fails in the data mapping step. How do I fix this? . . . . . . . . . F-16 How do I transfer Audit Manager logs to the target site? . . . . . . . . . . . . . . . F-16 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1 Figures Directory structure required by the bmide_commontemplategenerator utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCSE2 shared FMS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3.drop.sql script listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3.create.sql script listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unmodified siteConsolidationInternalClosureRules.xml file . . . . . . . . Modified siteConsolidationInternalClosureRules.xml file . . . . . . . . . . PLM00142 F . . . . . A-2 B-4 B-8 E-8 E-9 F-14 F-15 Teamcenter Site Consolidation Guide 5 Contents Tables SiteConsolidationDefault transfer option set . . . . . . . . . . . . . . . . . . . SiteConsolidationDefaultCR closure rule . . . . . . . . . . . . . . . . . . . . . . SiteConsolidationLW transfer option set . . . . . . . . . . . . . . . . . . . . . . SiteConsolidationLWCR closure rule . . . . . . . . . . . . . . . . . . . . . . . . . Intersite data precondition matrix . . . . . . . . . . . . . . . . . . . . . . . . . . MRO classes supported for site consolidation . . . . . . . . . . . . . . . . . . . Additional out-of-the-box data model coverage in Teamcenter 8.3 . . . . Out-of-the-box data model coverage for CAD solutions integrations in Teamcenter 8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Out-of-the-box data model coverage for site consolidation . . . . . . . . . . Codeless extensibility through closure rule if needed . . . . . . . . . . . . . Closure rule extensibility required . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Teamcenter Site Consolidation Guide . . . . . . . 3-22 3-23 3-23 3-23 3-26 F-3 F-4 . . . . F-5 F-5 F-7 F-7 PLM00142 F Chapter 1 Getting started with site consolidation Overview of the site consolidation process . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Before you begin . . . . . . . . . . . . . . . . . Setting goals . . . . . . . . . . . . . . . . . Developing a high-level plan . . . . . Reviewing your goals and plan . . . . Source and target site requirements PLM00142 F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-3 1-3 1-3 1-4 High-level technical considerations for site consolidation Compatibility requirements . . . . . . . . . . . . . . . . . . Physical infrastructure issues . . . . . . . . . . . . . . . . Performance monitoring . . . . . . . . . . . . . . . . . . . . Client performance considerations . . . . . . . . . . Enterprise server tier issues . . . . . . . . . . . . . . . Database server considerations . . . . . . . . . . . . Site definition data . . . . . . . . . . . . . . . . . . . . . . . . Administrative data . . . . . . . . . . . . . . . . . . . . Schema information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 1-5 1-7 1-8 1-8 1-9 1-9 1-10 1-10 1-11 Teamcenter Site Consolidation Guide Chapter 1 Getting started with site consolidation Overview of the site consolidation process The site consolidation process, which reduces the number of Teamcenter sites in operation in an enterprise Multi-Site environment, requires extensive planning and uses a variety of Siemens PLM Software tools. Warning Some of the tools and processes described in this document can cause data corruption or data loss if they are not used or performed properly. Because of the potential for damage to your enterprise data, you must contact the Global Technical Access Center (GTAC) to obtain a key for the use of site consolidation specific tools and to ensure that you have the proper experience to perform the required tasks. You must fully understand the intent of each process step and the use of each tool before attempting to consolidate sites. A typical large enterprise may reduce a dozen sites to one or two sites. The site consolidation process is organized in three distinctive phases: • Preparation During the preparation phase, you collect data, do in-depth analysis, and perform specific readiness steps to ensure site definition, product, and volume data is ready for consolidation. • Execution During the execution phase, you move product data from the source to the target site. It consists of multiple increments based on the source site size and the business drivers for the consolidation activity. • Cleanup During the cleanup phase, you do final cleanup, retirement, and, optionally, decommissioning of the source site, including activities such as volume data relocation, ownership conflict resolution, and Object Directory Service (ODS) configuration/cleanup. PLM00142 F Teamcenter Site Consolidation Guide 1-1 Getting started with site consolidation Chapter 1 Caution Site consolidation procedures are complex and require precision planning and execution. • This document, the site consolidation tools, and all relevant supporting material do not guarantee success prior to, during, or post consolidation. • A well-planned methodology developed by an experienced system integrator is essential. The site consolidation tools and detailed documentation are protected by license to ensure that a proper qualification is done through the Siemens PLM Software Global Sales and Services organization in cooperation with the Siemens PLM Software Research and Development organization. Before you begin Site consolidation requires a multidisciplinary team versed in the business, legal, infrastructure, data management, and end-user issues impacted by the effort. • Many business drivers can create a need for consolidation activity, such as infrastructure cost reduction, Information Technology (IT) centralization, and business acquisition. • End-user performance considerations, such as network latency, proximity to volume data, and global data sharing patterns, can create the need for consolidation. • OEM, supplier, joint-venture situations require careful planning and analysis from business and legal perspectives. • Business initiatives that drive global data replication scenarios must be considered for successful timing and coordinated data movement. • Active production data growth during the preparation phase, which could take several weeks or months, must be anticipated by strategic planning. The active growth for source sites and target sites, which impacts server and storage capacity planning, must be determined far enough in advance of consolidation to account for procurement lead time. • 1-2 All involved sites (source, target, and third sites) must be operating at the same appropriately licensed Teamcenter version level, which includes the site consolidation tools. The involved third sites are those that have shared Teamcenter data with the source site. You can determine these using the Multi-Site Assistant (MSA) sharing profile analysis. The site consolidation tools must be run at these sites during the cleanup phase. Teamcenter Site Consolidation Guide PLM00142 F Getting started with site consolidation Note The Multi-Site assistant (MSA) toolkit is available for download from the Global Technical Access Center (GTAC). This toolkit can help you a...
View Full Document

  • Fall '19
  • Data Management, Product lifecycle management, Teamcenter, site consolidation

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern

Stuck? We have tutors online 24/7 who can help you get unstuck.
A+ icon
Ask Expert Tutors You can ask You can ask You can ask (will expire )
Answers in as fast as 15 minutes