Teamcenter Environment Manager Helphelp.aviacons.ru/.../pdf/teamcenter_environment_manager_help.pdfProprietary and restricted rights notice This software and related documentation

Teamcenter 10.1

Teamcenter EnvironmentManager Help

Publication NumberPLM00128 H

Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens ProductLifecycle Management Software Inc.

© 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.

Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenteris a trademark or registered trademark of Siemens Product Lifecycle ManagementSoftware Inc. or its subsidiaries in the United States and in other countries. Allother trademarks, registered trademarks, or service marks belong to their respectiveholders.

2 Teamcenter Environment Manager Help PLM00128 H

Contents

Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2

Introduction to Teamcenter Environment Manager . . . . . . . . . . . . . . . 1-1

Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

About database configuration in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Rebuilding a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Microsoft SQL Server connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

License management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

About license management in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Configuring FLEX license client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Teamcenter Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Welcome to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Identifying the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Teamcenter Foundation installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Teamcenter Foundation settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Configure the database for Teamcenter Foundation . . . . . . . . . . . . . . . . . . . . 4-4License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Selecting solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Selecting features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Teamcenter administrative user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Password security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Password security settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Configuring the operating system user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10TcServer character encoding settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Creating a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12TC_DATA proxy setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Installing database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Configuring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Java path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Assign volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Configuration maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Selecting a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Selecting configuration to remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Feature maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Confirm silent distribution file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Custom distribution options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19Message panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Confirming selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Installing features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Teamcenter data directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

PLM00128 H Teamcenter Environment Manager Help 3

Contents

Volume access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Teamcenter installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Recovering from a failed Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . 4-21Enter Java Runtime Environment location . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Migrating Teamcenter to another JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Uninstall Teamcenter Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Uninstall Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22Confirm removal of all Teamcenter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22Completely uninstall Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22Confirm removal of all Teamcenter software and data . . . . . . . . . . . . . . . . . . 4-22

Quick preconfigured installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

About quick preconfigured installation in TEM . . . . . . . . . . . . . . . . . . . . . . . 5-1Product selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Teamcenter four-tier rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Teamcenter corporate server and two-tier rich client . . . . . . . . . . . . . . . . . . . 5-4Teamcenter corporate server and .NET-based server manager . . . . . . . . . . . . 5-6Teamcenter corporate server and J2EE-based server manager . . . . . . . . . . . . 5-8

Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Business Modeler IDE templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Database Configuration Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Business Modeler IDE templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Business Modeler IDE client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Database Template Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Updating a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

File Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

About File Management System installation in TEM . . . . . . . . . . . . . . . . . . . 7-1FCC settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1FCC parents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Installing FMS server cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2FSC cache settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3FSC proxy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5FSC service – FCC defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Selecting the FSC deployment model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7FSC service additional sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Adding an external site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Create/Edit remote site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8FSC service connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8Rich client FCC parent settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9FSC service additional group sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Verifying the FSC service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10FSC client map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10FSC groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10FSC nonmaster settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11FSC servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11FSC service additional group sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11FSC service additional sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Create/Edit FSC client map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Create/Edit file store group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13


Contents

Create/Edit FSC group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Create/Edit FSC server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14File store group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14Scan for sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15Assign to FSC group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15Volume query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15FSC security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16Create/edit remote group site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Teamcenter client communication system . . . . . . . . . . . . . . . . . . . . . . . 8-1

About Teamcenter client communication system configuration in TEM . . . . . . 8-1Teamcenter client communication system (TCCS) switch . . . . . . . . . . . . . . . . 8-1TCCS environment settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1TCCS forward proxy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2TCCS reverse proxy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3TCCS client tag filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4TCCS configuration selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Removing a TCCS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Kerberos authentication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Secure socket layer (SSL) settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

About Web tier installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1J2EE Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1.NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Configuring Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Configuring Security Services for rich client . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Configuring Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

About Dispatcher installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Installing Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Installing Dispatcher components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Dispatcher settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Dispatcher translation service settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4Dispatcher translation service (additional settings) . . . . . . . . . . . . . . . . . . . . 11-5Selecting translators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6Translator settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Teamcenter reporting and analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

About Reporting and Analytics installation in TEM . . . . . . . . . . . . . . . . . . . . 12-1Reporting and Analytics install options and general settings . . . . . . . . . . . . . 12-1Reporting and Analytics license server settings . . . . . . . . . . . . . . . . . . . . . . . 12-2Reporting and Analytics WAR file settings . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Reporting and Analytics license settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3Reporting and Analytics metadata settings . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Reporting and Analytics database selection . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4Reporting and Analytics WAR and metadata settings . . . . . . . . . . . . . . . . . . 12-6Reporting and Analytics authentication settings . . . . . . . . . . . . . . . . . . . . . . 12-7


Contents

Reporting and Analytics WAR SMTP settings . . . . . . . . . . . . . . . . . . . . . . . . 12-7Reporting and Analytics metadata SSO settings . . . . . . . . . . . . . . . . . . . . . . 12-8Reporting and Analytics WAR SSO settings . . . . . . . . . . . . . . . . . . . . . . . . . 12-8Reporting and Analytics Security Services configuration . . . . . . . . . . . . . . . . 12-8Reporting and Analytics Web parts and services . . . . . . . . . . . . . . . . . . . . . . 12-9Reporting and Analytics snapshot migration . . . . . . . . . . . . . . . . . . . . . . . . . 12-9Upgrading a cloned environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

About Global Services installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Global Services database settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Global Services preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Configuring the Global Services Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Configuring an RDV database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1Configuring Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3Database engine selection for Repeatable Digital Validation . . . . . . . . . . . . . . 14-3

Rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

About rich client installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1Setting two-tier transport mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1Two-tier Teamcenter server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1Rich client settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Supplying middle-tier server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Rich client run-time home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3Rich client two-tier settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3Rich client settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3Rich client run time folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4

Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

About Lifecycle Visualization installation in TEM . . . . . . . . . . . . . . . . . . . . . 16-1Choosing a license level for Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . 16-1Installing the embedded viewer for rich client . . . . . . . . . . . . . . . . . . . . . . . . 16-2Installing the stand-alone application viewer for rich client . . . . . . . . . . . . . . 16-3Configuring Lifecycle Visualization for Teamcenter . . . . . . . . . . . . . . . . . . . . 16-3

Teamcenter integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Configuring ERP Connect Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1Teamcenter Integration for NX for rich client . . . . . . . . . . . . . . . . . . . . . . . . 17-1Teamcenter Extensions for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1Workflow to Schedule Integration settings . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2Configuring SCM ClearCase Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Installing Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Additional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Installing CAD-BOM alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1Product Master Management URL and Security Services . . . . . . . . . . . . . . . . 19-2


Contents

Product Master Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3Installing online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4Microsoft Office support for rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6Teamcenter Client for Microsoft Office installation . . . . . . . . . . . . . . . . . . . . 19-6Teamcenter Client for Microsoft Office configuration . . . . . . . . . . . . . . . . . . . 19-6Configuring Teamcenter Automotive Edition-GM Overlay . . . . . . . . . . . . . . . 19-7Embedded Software Solutions for Foundation . . . . . . . . . . . . . . . . . . . . . . . . 19-7Installing the full-text search engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8Hierarchical storage management (HSM) settings . . . . . . . . . . . . . . . . . . . . . 19-9Manufacturing Process Management options . . . . . . . . . . . . . . . . . . . . . . . . 19-9MATLAB Client Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9NX Graphics Builder installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9Configuring Content Management for rich client . . . . . . . . . . . . . . . . . . . . . . 19-9Configuring Remote Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10SCM ClearCase for rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-11

Updates Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

About Updates Manager actions in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Updates Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Removing backup files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Choosing a patch to apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Choosing an update to apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1Supplying information about the updates server . . . . . . . . . . . . . . . . . . . . . . 20-2Applying updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2Enable new capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2

Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Pre-upgrade diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1Warnings from diagnostic tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1Custom database template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1Type collision verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Upgrading workflow objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Identify the Teamcenter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Additional upgrade options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Database daemons port check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3Reporting and Analytics upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3Repeatable Digital Validation database user . . . . . . . . . . . . . . . . . . . . . . . . . 21-4Selecting a Teamcenter configuration to upgrade . . . . . . . . . . . . . . . . . . . . . . 21-4New application root directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4Old application root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4Test environment location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4Verifying templates and features for the test environment . . . . . . . . . . . . . . . 21-5Upgrade information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5Upgrade database features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Figures

Welcome to Teamcenter panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2


Contents

Maintenance panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Tables

IBM DB2 database server values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Oracle database server values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Microsoft SQL Server values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7


Chapter

1 Introduction to TeamcenterEnvironment Manager

PLM00128 H Teamcenter Environment Manager Help

Chapter

1 Introduction to TeamcenterEnvironment Manager

Teamcenter Environment Manager (TEM) is an installation wizard that installs,upgrades, and updates Teamcenter configurations. For each installation step, TEMdisplays a panel requesting information from the installer. Each panel providesonline help that describes the content of the panel. To view the online help for a

given panel, click the help button .

This guide contains all online help displayed in the TEM user interface, organizedfor reference from the Teamcenter online help collection. Online help topics forTEM panels are organized by features (such as About File Management Systeminstallation in TEM) and general configuration areas (such as About databaseconfiguration in TEM). Because of this organization, the sequence of TEM helptopics differs from the sequence of panels displayed in TEM.

This guide contains TEM help topics included in the standard Teamcenter release.It does not include help for TEM panels added by Teamcenter products that arelicensed and sold separately, such as Teamcenter product master management.

When you launch TEM from a Teamcenter software distribution image (disc ordownloadable image), the first panel displayed is theWelcome to Teamcenter panel.

PLM00128 H Teamcenter Environment Manager Help 1-1

Chapter 1 Introduction to Teamcenter Environment Manager

Welcome to Teamcenter panel

From this panel, you choose whether to create a new installation or upgrade anexisting installation. You can also create a silent installation package that can beused to install a Teamcenter configuration with preselected features and settingson other hosts.

For more information about options in the Welcome to Teamcenter panel, seeWelcome to Teamcenter.

When you launch TEM from an installed Teamcenter home directory, the first paneldisplayed is the Maintenance panel.

1-2 Teamcenter Environment Manager Help PLM00128 H

Introduction to Teamcenter Environment Manager

Maintenance panel

From this panel, you can perform maintenance on your Teamcenter configuration,such as adding or removing features, changing FMS settings, or even uninstalling aconfiguration, by choosing Configuration Manager. To apply downloaded patches ormaintenance packs (MPs) to a Teamcenter configuration, choose Updates Manager.

For more information about configuration maintenance options, see Configurationmaintenance. For more information about applying patches or MPs to aconfiguration, see Applying updates.

Note Some panels are not displayed in all platforms. Some features are notavailable on all platforms.


Chapter

2 Database configuration

About database configuration in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Rebuilding a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Microsoft SQL Server connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1


Chapter

2 Database configuration

About database configuration in TEMThe following TEM help topics describe panels that allow you to create and configuredatabases for Teamcenter. For more information about creating and configuringTeamcenter databases, see the appropriate server installation guide (for Windowsor UNIX/Linux) or the System Administration Guide.

Rebuilding a DatabaseThis panel displays a list of templates to be applied when TEM rebuilds thedatabase. The Installed Templates table shows templates that have been appliedto the current database.

The Candidate Templates table shows the latest templates available to apply whenrebuilding the database. Select the candidate templates you want to apply to thedatabase.

Note You cannot select templates that were not previously installed. In theCandidate Templates table, you can only select templates listed in theInstalled Templates table.

To locate additional candidate templates, click Browse. TEM searches for .zip filesthat contain Teamcenter templates. For example, the Teamcenter Foundationtemplate, foundation_template.xml, is in the file foundation_template.zip.

Microsoft SQL Server connectionIn this step, you specify whether your Microsoft SQL Server server is accessiblethrough a named instance or a port. Select the appropriate option and type the nameof the instance or the port your server uses.


Chapter

3 License management

About license management in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Configuring FLEX license client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1


Chapter

3 License management

About license management in TEMThe following TEM help topics describe panels in which you enter Teamcenterlicense settings.

For more information about configuring the Teamcenter licensing client, see theappropriate server installation guide (for Windows or UNIX/Linux).

For more information about installing the Teamcenter license server andmanaging Teamcenter licenses, see Installing UGS Licensing for UNIX,Installing UGS Licensing for Windows, and UGS Licensing User Guide inthe additional_documentation directory on the Teamcenter documentationdistribution image.

See also the Siemens PLM Software licensing frequently asked questions:

http://support.industrysoftware.automation.siemens.com/license/license_faq.pdf

Configuring FLEX license clientIn this step, you configure the Teamcenter FLEX license client to provide licenseauthorizations for Teamcenter and NX.

Prerequisite:

The Siemens PLM License Server (ugslmd) must be installed and configured.

For more information, see the Installing Siemens PLM Software Licensingfor UNIX, Installing Siemens PLM Software Licensing for Windows,and Siemens PLM Common Licensing User Guide documents in theadditional_documentation directory on the Teamcenter documentationdistribution image.

To add a license server to the list, click Add. TEM adds a row to the table of licenseservers. Double-click the Port or Host boxes to enter the host name and the port forthe host serving the Teamcenter license file.

To modify a value in the table, double-click the box and enter the new value.

To remove a server from the table, select the row and click Delete.Teamcenter Environment Manager sets the SPLM_LICENSE_SERVERenvironment variable on the local host to point to the license server. (Thisenvironment variable replaced the UGS_LICENSE_SERVER environmentvariable beginning in Teamcenter 10.1.)

Set the following additional values as appropriate for your system.


http://support.industrysoftware.automation.siemens.com/license/license_faq.pdf

Chapter 3 License management

Value Description

License Server ModeRedundant Server Specifies your network uses redundant license

servers.

Multiple Server Specifies your network uses multiple licenseservers.

Flex License File Location Specifies the location of your Teamcenterlicense file if it is not specified in theSPLM_LICENSE_SERVER environmentvariable.


Chapter

4 Teamcenter Foundation

Welcome to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Identifying the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Teamcenter Foundation installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Teamcenter Foundation settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Configure the database for Teamcenter Foundation . . . . . . . . . . . . . . . . . . . . 4-4

License agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Selecting solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Selecting features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Teamcenter administrative user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Password security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Password security settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Configuring the operating system user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

TcServer character encoding settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Creating a volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

TC_DATA proxy setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Installing database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Configuring data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Java path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Assign volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Configuration maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Selecting a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16


Selecting configuration to remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Feature maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Confirm silent distribution file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Custom distribution options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Message panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Confirming selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Installing features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Teamcenter data directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Volume access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Teamcenter installation location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Recovering from a failed Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . 4-21

Enter Java Runtime Environment location . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Migrating Teamcenter to another JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Uninstall Teamcenter Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Uninstall Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Confirm removal of all Teamcenter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Completely uninstall Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Confirm removal of all Teamcenter software and data . . . . . . . . . . . . . . . . . . 4-22

Teamcenter Environment Manager Help PLM00128 H

Chapter

4 Teamcenter Foundation

Welcome to TeamcenterIn this step, you begin a Teamcenter installation or upgrade. Click one of thefollowing buttons.

Button DescriptionInstall Creates a new installation of Teamcenter. This

option allows you to select and configure featuresbefore you begin installing.

Quick Preconfigured Install Installs one of several predefined commonTeamcenter configurations that require minimaluser input to install. You choose a configurationin the next panel.

Upgrade Upgrades an existing installation of Teamcenter.

Create custom distribution Specifies you want to create a silent distributionor a compact distribution for simplifieddeployment of Teamcenter configurations.

Create environment forupgrade testing

Specifies you want to create a copy of aproduction environment for performing upgradetesting.

If you want to add a new Teamcenter configuration to an existing Teamcenterinstallation, launch Teamcenter Environment Manager (TEM) from the location ofthe Teamcenter installation, not from the Teamcenter software distribution image.

Note • A Teamcenter configuration is a collection of features associated withone Teamcenter data directory. The collection of configurations thatshare the same Teamcenter application root directory is a Teamcenterinstallation.

When you install Teamcenter executables using TEM from the softwaredistribution image, you create the first configuration.

• A silent distribution is a configuration file you can use to installTeamcenter silently (without user interaction) on another host. Acompact distribution is an installable package with a selected subset ofTeamcenter client features. It is much smaller than a full Teamcentersoftware distribution image and is more easily distributed to multiplehosts in an organization.


Chapter 4 Teamcenter Foundation

• The Quick Preconfigured Install button is unavailable if you select theCreate custom distribution check box.

For the latest information about issues that may affect Teamcenter installationand upgrade, see the Release Bulletin.

Identifying the configurationIn this step, you uniquely identify this configuration of a Teamcenter installation.

Tip Record the name. To modify or uninstall this configuration, you must selectthe configuration ID from a list displayed by Teamcenter EnvironmentManager.

A Teamcenter configuration is a collection of features associated with oneTeamcenter data directory. A Teamcenter installation is a collection ofTeamcenter configurations that share the same Teamcenter applicationroot directory.

Teamcenter Foundation installationIn this step, you choose how you want to configure the database and data directoryfor the Teamcenter server. Select the option that best suits your needs.

Teamcenter Foundation settingsIn this step, you provide additional settings for Teamcenter Foundation.

These settings include the creation of transient volumes on the local host.

A transient volume is an operating system directory controlled by Teamcenter andused to store temporary data for transport of reports, PLM XML data, and othernonvolume data between the enterprise tier and client tier in a deployment of thefour-tier architecture. All four-tier clients accessing this installation of Teamcenteruse this transient volume.

Note Two-tier clients do not use this transient volume, using instead a temporarydirectory on the client host that is defined either by the start_server scriptor by the Transient_Volume_RootDir environment variable on the clienthost.

If you plan to install another Teamcenter data server for the database you arepopulating, but the host is on a different platform, you must:

1. Specify the location of the transient volume for each platform on this panel.

For example, if the local host is a Windows-based system, and you intend toinstall a Teamcenter data server for this database on a UNIX-based system,specify the transient volume location for the additional host as well as the localhost.


Teamcenter Foundation

2. If you do not specify an existing directory for the additional Teamcenter dataserver, manually create the location for the transient volume.

References:

• For more information on deploying Teamcenter on heterogeneous platforms,see the Installation on UNIX and Linux Servers Guide and the Installation onWindows Servers Guide.

Value DescriptionTransient VolumeDirectories

Windows clients Specifies the full path to a directory to act as thetransient volume when the host is Windows-based. Theoperating system user running the FSC and Teamcenterserver processes must have a minimum of read and writeprivileges for this directory. This field must contain avalue.

If this directory does not exist, Teamcenter EnvironmentManager creates it if the local host is Windows-based.

Tip • If you are deploying the two-tier architecture,accept the default value.

• If the local server is UNIX-based, and youdo not intend to install a Teamcenter dataserver for this database on a Windows-basedsystem, accept the default value.

• If the local server is UNIX-based, and youintend to install a Teamcenter data server forthis database on a Windows-based system,either enter the path to an existing directoryon the UNIX system or record the pathyou enter (you must create this directorymanually).

UNIX clients Specifies the full path to a directory to act as the transientvolume when the host is Linux-based. This field mustcontain a value.

If this directory does not exist, Teamcenter EnvironmentManager creates it if the local host is Linux-based.

Tip • If you are deploying the two-tier architecture,accept the default value.

• If the local server is Windows-based, and youdo not intend to install a Teamcenter dataserver for this database on a Linux-basedsystem, accept the default value.



Value Description

• If the local server is Windows-based, and youintend to install a Teamcenter data server forthis database on a Linux-based system, eitherenter the path to an existing directory on theLinux system or record the path you enter(you must create this directory manually).

Generate server cache Specifies that you want to generate a shared servercache. If you select this option, TEM runs thegenerate_metadata_cache utility at the end of theinstall, upgrade, or update action. This option reducesTeamcenter memory consumption by moving metadatato shared memory. Types, property descriptors, andconstants are placed in a shared cache that is shared byall Teamcenter server instances.

This option is selected by default in a Teamcenter serverinstallation.

For more information about managing shared servercache, see the System Administration Guide.

Generate client cache Specifies that you want to generate a cache of data thatrich clients can download once at initial logon and thenreuse on the client host. This option reduces serverdemand, reduces startup time, and improves overallperformance. When this option is selected, TEM runsthe generate_client_meta_cache utility at the end ofthe install, upgrade, or update action. If you clear thisoption, but a client cache already exists, the old clientcache is deleted.

This option is selected by default in a Teamcenter serverinstallation.

For more information about thegenerate_client_meta_cache utility, see the UtilitiesReference.

For additional advanced options, click the Advanced button.

Configure the database for Teamcenter FoundationIn this step, you provide the information that Teamcenter requires to connect tothe Teamcenter Foundation database. The contents of this panel depend on yourselection in the Foundation panel.

Prerequisites:

• You must install a database server. Teamcenter supports IBM DB2, Oracle,and MS SQL Server databases.



• If you use Oracle, you must create a database instance, either a specific instanceconfigured for Teamcenter or a multipurpose instance to be configured in thisstep.

If you use IBM DB2, you must create a database using the DB2 script or the DB2database creation command.

References:

For information about installing a database server and configuring databasesfor use with Teamcenter, see the Installation on UNIX and Linux Servers Guideand the Installation on Windows Servers Guide available in the Teamcenteronline help collection.

In the Data Directory box, enter a location for the Teamcenter data directory(TC_DATA). TEM creates shared data subdirectories and files in this location.

In the Database Server box, select your database vendor (IBM DB2, Oracle, orMicrosoft SQL Server).

Enter the following database configuration values, depending on the databasevendor you select.

IBM DB2 database server values

Value DescriptionHost Specifies the name of the host on which the IBM DB2

server runs.

This host must exist, and IBM DB2 must be installed.

Database Name Specifies the name of the DB2 database to be used byTeamcenter.

The database name was defined when the IBM DB2database was created.

Port Specifies the number of the port on which IBM DB2 serverlistens.

The port number was determined when IBM DB2 wasinstalled.

OS User Specifies a database user name:

• To connect to an existing database configured for usewith Teamcenter, enter the name defined for a databaseuser when the database was configured.

• To create and configure a database for use withTeamcenter, enter the name of the database user youwant to create.

Note The Teamcenter database user must exist in theoperating system.



IBM DB2 database server values

Value DescriptionPassword Specifies a database password:

• To connect to an existing database configured for usewith Teamcenter, enter the password defined for thedatabase user when the database was configured.

• To configure a new database for use with Teamcenter,enter a password for the database user you are creating.

If you chose to create a new database instead of using an existing database,provide the following values:

System User Specifies a user name of the IBM DB2 system administratoraccount. The default value is db2admin.

Password Specifies a password for the IBM DB2 system administratoraccount.

Caution Make sure the password does not contain spacecharacters or any of the following characters:

! @ $ % ’ " : ; . < > ( ) { }

Database Path Specifies the location of the database on the IBM DB2server.

Oracle database server values

Value DescriptionHost Specifies the name of the host on which the Oracle server

runs.

This host must exist, and the Oracle server must beinstalled.

Service Specifies the name of the service for the Oracle instance.

The service name was determined when the Oracleserver was installed.

Port Specifies the number of the port on which the Oracleserver listens.

The port number was determined when the Oracle serverwas installed.




Value DescriptionUser Specifies a database user name:

• To connect to an existing database configured foruse with Teamcenter, enter the name defined for adatabase user when the database was configured.


Password Specifies a database password:


• To configure a new database for use with Teamcenter,enter a password for the database user you arecreating.


System User Specifies a user name of the Oracle system administratoraccount. The default value is system.

Password Specifies a password for the Oracle system administratoraccount.

Caution Make sure the password does not containspace characters or any of the followingcharacters:

! @ $ % ’ " : ; . < > ( ) { }

Database Path Specifies the location of the tablespacesfor the Teamcenter database onthe Oracle server. This is typicallyORACLE_HOME\oradata\Oracle_SID (on Windowssystems) or ORACLE_HOME/oradata/Oracle_SID (onUNIX/Linux systems).

Microsoft SQL Server values

Value DescriptionInstance If you connect to Microsoft SQL Server using a named

instance, select this option and enter the instance name youdefined when you installed MS SQL Server.

Port If you connect to Microsoft SQL Server using a specific port,select this option and enter the port number you specifiedwhen you installed MS SQL Server.




Value DescriptionLogin Name Specifies a database user name:


• To create and configure a new database for use withTeamcenter, enter the name of the database user youwant to create.

Login Password Specifies the password for the database user:



Database Name Specifies the name of the MS SQL Server database.

The database name was determined when database wascreated.


System User Specifies the user name of the SQL Server systemadministrator account. The default value is sa.

Password Specifies the password for the SQL Server systemadministrator account.


! @ $ % ’ " : ; . < > ( ) { }

Database Path Specifies the directory in which to create the Teamcenterdatabase on the SQL Server server.

License agreementIn this step, you read and accept the Siemens PLM Software license agreement.

Read the license agreement, then choose the option to accept the license agreementto continue with Teamcenter installation.

Selecting solutionsIn this step, you optionally choose solutions to install in your Teamcenterconfiguration.



Solutions are preselected groups of features that provide starting points forrecommended Teamcenter configurations. You can add features or deselect featuresin the Features panel in Teamcenter Environment Manager (TEM). For informationabout a solution, point to the solution name in the list. TEM displays a description.

Selecting featuresIn this step, you select features to include in your Teamcenter configuration ordeselect features to remove them from your configuration. Features are groupedby related functionality.

For information about a feature, point to the feature name in the list. TEM displaysa description of the feature.

Note • Some features are disabled because they require other features. Toenable a feature, select its prerequisite features. For information aboutfeature prerequisites, see the feature description.

• Some features cannot be installed in the same configuration, so selectingone disables the other.

If this is a new installation, enter the directory in which you want to installTeamcenter in the Installation Directory box. Specify a directory that does not exist.Teamcenter Environment Manager (TEM) creates the directory you specify.

If this is a new Teamcenter configuration, or if you are adding or removing featuresfrom an existing configuration, you cannot change the installation directory. TEMcreates the new configuration using the same installation root directory.

Teamcenter administrative userIn this step, you enter logon information for the Teamcenter administrative useraccount.

During an initial Teamcenter installation, these boxes are read-only.

Box DescriptionUser Specifies the user name of the Teamcenter administrative

user account. This value is set to infodba by default.Password Specifies the password for the Teamcenter administrative

user account. This value is set to infodba by default.


! @ $ % ’ " : ; . < > ( ) { }

Caution Siemens PLM Software strongly recommends you change the passwordfor the Teamcenter administrative user (infodba) account afterinstallation. You can change the password through the rich client.



Password securityIn this step, you specify where to store encrypted passwords for Teamcenter users.

Value Description

Password Security Specifies the path to the directory that containsthe password files. Teamcenter EnvironmentManager(TEM) locks access to the passworddirectory to all users except the operatingsystem user performing the installation.

For more information about password security settings, see the SystemAdministration Guide.

Password security settingsIn this step, you specify where to store encrypted passwords for Teamcenter users.

Value Description

Password Security Specifies the path to the directory that containsthe password files. Teamcenter EnvironmentManager (TEM) locks access to the passworddirectory to all users except the operatingsystem user performing the installation.

List of Known Users Specifies a list of known Teamcenter users whocan access security settings.

For more information about password security settings, see the SystemAdministration Guide.

Configuring the operating system userIn this step, you configure the operating system logon account for Teamcenterservices. This account represents a responsibility rather than a person. AllTeamcenter services run on the server as this user account. It is also the logonaccount Teamcenter administrators use to install, upgrade, and patch Teamcenter.

Prerequisite:

You must define the logon account (user name and password) in the operatingsystem with administrator privileges. This account can have any name andpassword. For Windows systems, this account must have administratorprivileges and be granted the Log on as service right.

Note If you did not log on to this account to install Teamcenter, you can cancelthis installation and restart it as this user account.

Value DescriptionUser Specifies the operating system user name defined to run

Teamcenter services.



Value DescriptionPassword Specifies the password defined for the Teamcenter services

user name.

TcServer character encoding settingsIn this step, you specify settings for character encoding in your Teamcenter richclient installation.

Value Description

Canonical Name Specifies by canonical name of the character encoding setthe rich client uses to access the database.

Caution To prevent data corruption, this characterencoding set must match the encoding set usedby the Teamcenter database.

Choose an appropriate value for your locale. Some valuesfor Teamcenter are as follows:

• Chinese (Simplified): GBK

• Chinese (Traditional): Big5

• Czech: Cp1250

• English: ISO8859_1

• French: Cp1252

• German: Cp1252

• Hebrew: ISO8859_8

• Italian: Cp1252

• Japanese: SJIS

• Korean: Cp949

• Polish: Cp1250

• Portuguese (Brazilian): Cp1252

• Russian: Cp1251

• Spanish: Cp1252

The values specified in this field and the Description fieldare a pair: when you select a value for this field, Teamcenter



Value DescriptionEnvironment Manager automatically selects and displaysthe correct value in the Description field.

Description Specifies by description the character encoding set the richclient uses to access the database.

The values specified in this field and the Canonical Namefield are a pair: when you select a value for this field,Teamcenter Environment Manager automatically selectsand displays the correct value in the Canonical Name field.

Creating a volumeIn this step, you create a volume, a directory that stores files managed byTeamcenter. A Teamcenter volume is controlled by one, and only one, database.

When you create or populate a database during a Teamcenter installation, you mustcreate a volume for it. This requires an FMS server cache (FSC) that creates andserves default volumes. The volume can be created while installing a Teamcentercorporate server or a volume server.

You can optionally use Teamcenter Environment Manager to create additionalvolumes for a database:

• When you install the Teamcenter application directory but point to a Teamcenterdata directory in another installation

• When you install Teamcenter and create a new data directory for an existingdatabase

Additional volumes created using Teamcenter Environment Manager are notpopulated.

Teamcenter administrators can also use the rich client Organization application tocreate additional volumes for a database.

Reference:

• For information about creating volumes using the rich client user interface,see the Organization Guide.

Value DescriptionName Specifies the name of the volume directory.

Directory Specifies the path to the volume directory.

Serving FSCFSC DeploymentModel

Specifies the FMS server and volume model deploymentmodel you want to use. Select a model from the list.

FSC ID Specifies the ID of the FMS server cache (FSC) for thevolume. This value is needed only if you specify SimpleModel in the FSC Deployment Model box.



Value Description

FSC Host Name Specifies the host name of the host on which the FSCresides.

FSC Port Specifies the port the FSC uses.

If you define an FSC in the current Teamcenter configuration, the default values inthe Serving FSC fields are populated with the values from that FSC. If you createa volume as part of a corporate server installation, TEM installs the FSC beforeTeamcenter Foundation to enable Teamcenter to create volumes.

TEM validates the FSC settings by attempting to connect to the specified hostand port, and adds the specified FSC specified to the FMS_BOOTSTRAP_URLSpreference in the new database after population.

TC_DATA proxy settingThis panel displays the TC_DATA proxy path. Teamcenter stores files for selectedservices in this location. This value is display-only.

Installing database daemonsIn this step, you install optional database support services. Although the databasedaemons are optional, installing them is required to activate the TeamcenterSubscription Monitor application and the notification of late tasks in the workflowapplications and to tessellateUGMASTER andUGALTREP datasets to JT datasetsfor use with Repeatable Digital Validation (RDV) and the DesignContext application.

References:

• For general information about configuring database daemons, see the SystemAdministration Guide.

• For information about configuring tessellation for Repeatable Digital Validationand the DesignContext application, see Getting Started with RDV and theDesignContext Guide.

• For information about the Subscription Monitor application, see SubscriptionMonitor Guide.

• For information about late task notification, see the Workflow Designer Guide.

Value DescriptionInstall ActionManager Service

Specifies that you want to install the service that monitorsthe database for the creation of action objects anddispatches events that have a specific execution time andevents the Subscription Manager daemon fails to process.

Installing the Action Manager service is required to enablethe Teamcenter Subscription Monitor application.

If you install the Action Manager service, you must alsoinstall the Subscription Manager service.



Value Description

Install SubscriptionManager Service

Specifies that you want to install the service that monitorsthe database event queue for the creation of subscriptionevent objects.

Installing the Subscription Manager service is required toenable the Teamcenter Subscription Monitor application.

If you install the Subscription Manager service, you mustalso install the Action Manager service.

Install Task MonitorService

Specifies that you want to install the service that checksuser inboxes for tasks that have passed due dates, notifiesthe delegated recipients, and marks the task as late.

Installing the Task Monitor service is required to enablenotification of late tasks.

Install TesselationService

Specifies that you want to install the service that tessellatesUGMASTER and UGALTREP datasets to the JT(DirectModel) dataset and attaches the JT dataset backto the item revision and UGMASTER and UGALTREPdataset.

Installing the Tessellation service is required to create thetessellated representations in Repeatable Digital Validation(RDV) that enable users of the DesignContext applicationto quickly visualize components in context. The tessellatedrepresentations are created during the workflow releaseprocess, ensuring that JT files of the DirectModel datasetsare updated as the NX files are released.

Configuring dataIn this step, you choose whether to install Teamcenter shared data subdirectoriesand files on this host or point to these files installed on another host.

This directory containing the shared data subdirectories and files is referred to asthe Teamcenter data directory. The TC_DATA environment variable points to thislocation. A data directory is associated with one (and only one) database instance.

The data directory is exported with full write access and mounted via NFS/CIFSby other Teamcenter nodes. If the data directory is a mapped drive, UNC paths areused for the TC_ROOT and TC_DATA environment variables.

Value Description

Create a new datadirectory

Specifies that you want to install the Teamcenter shareddata subdirectories and files on this host.

Connect to anexisting datadirectory

Specifies that you want to point to Teamcenter shared datasubdirectories and files installed on another host.



Value DescriptionData DirectoryLocation

Specifies either:

• The full path to the location on the local host whereyou want to install the Teamcenter shared datasubdirectories and files.

• The full path to the location where Teamcenter shareddata subdirectories and files are installed on anotherhost.

Share Name (Teamcenter Rapid Start only)

Specifies a name for the Teamcenter Rapid Start networkshare. The default value is TcX.

During Teamcenter Rapid Start installation, TEM createsthe network share to the configuration directory (accessibleas \\server-name\TcX) where client workstations can accessconfiguration information. Because this shared directory isaccessed using the UNC path, the server must be connectedto the network during the installation.

Java pathIn this step, you provide the path to the Java Runtime Environment (JRE) installedon your host.

This is required to create services for the Business Modeler IDE.

Assign volumeIn this step, you assign a volume to an FSC (FMS server cache) server, externalload balancer, or file store group.

Value Description

Assign to FSCServer or ExternalLoad Balancer

Select to assign the volume to an FSC server (a machinewhere FMS processes run) or an external load balancer(a machine designated to take some of the load of FMSprocesses).

Assign to File StoreGroup

Select to assign the volume to a file store group, whichspecifies volumes to be load balanced across several FSCs.

MaintenanceIn this step, you choose the maintenance action you want to perform:

• Configuration ManagerSelect this option to add or remove features or modify settings for an existingTeamcenter configuration.



• Updates Manager

Select this option to install Teamcenter product updates and patches.

• Migrate Teamcenter to another JRE

Select this option to change the Java Runtime Environment (JRE) used byTeamcenter and TEM.

• Uninstall Teamcenter

Select this option to completely uninstall Teamcenter from your system. Thisincludes all configurations, databases, volumes, and TEM itself.

Note A Teamcenter configuration is a collection of features associated with oneTeamcenter data directory. A Teamcenter installation is a collection ofTeamcenter configurations that share the same Teamcenter applicationroot directory.

Configuration maintenanceIn this step, you choose the configuration action you want to perform:

• Add new configuration

Select this option to create a new Teamcenter configuration.

• Perform maintenance on an existing configuration

Select this option to add or remove features or update settings for an existingTeamcenter configuration.

• Upgrade a configuration from another installation

Select this option to upgrade an existing configuration to Teamcenter 10.1.

• Apply an MP from another installation

Select this option to apply a maintenance pack from an existing Teamcenterconfiguration to Teamcenter 10.1.

• Remove configuration (uninstall)

Select this option to remove an existing Teamcenter configuration.

Note A Teamcenter configuration is a collection of features associated with oneTeamcenter data directory. A Teamcenter installation is a collection ofTeamcenter configurations that share the same Teamcenter applicationroot directory.

Selecting a configurationIn this step, you choose the configuration you want to modify. Select the configurationfrom the list shown.



Selecting configuration to removeIn this step, you choose the Teamcenter configuration to remove.

Note When you remove a configuration, the database and directory for theselected configuration are removed.

Removal of the selected configuration does not begin until you confirm yourselections later in the process. Teamcenter Environment Manager prompts you toconfirm your selections before any changes are made.

Feature maintenanceIn this step, you can select a variety of maintenance actions to perform on yourTeamcenter configuration. This may include the following groups of options,depending on the features in your configuration:

• TeamcenterThe Add/Remove Features option allows you to add or remove features in yourconfiguration.

• FMS Server CacheThis group contains options to import FMS server cache (FSC) groups andupdate FMS master settings.

• Business Modeler TemplatesThese options allow you to add or update templates you use within the BusinessModeler IDE client.

• Teamcenter FoundationThese options allow you to update database templates and settings for yourTeamcenter configuration.

o Update Database (Full Model)Updates the database with Business Modeler IDE templates that containsall the custom data model, including schema items such as business objectsand classes.

o Update Database (Perform Live Updates)Updates the database with operational data templates that contains onlyoperational (nonschema) data such as LOVs and rules.

o Modify SettingsAllows you to modify certain Teamcenter Foundation settings.

For more information about operational data, see the Business Modeler IDEGuide.

• NX IntegrationThese options allow you to update settings for the Teamcenter NX Integration.



• Online HelpThese options allow you to add online help components to the Teamcenter onlinehelp installed on your local host.

• Client Communication SystemThis group contains options to update Teamcenter client communication system(TCCS) settings.

o Use Configurations and EnvironmentsAllows you to enable TCCS in your Teamcenter installation.

o Modify ConfigurationsAllows you to modify TCCS configurations.

o Modify 4-tier server settingsAllows you to modify settings for the four-tier server.

o Modify FCC Parent settingsAllows you to modify FCC parent settings.

o Remove ConfigurationsAllows you to remove TCCS configurations.

• 2-tier Teamcenter server configurationsThis group contains options to modify two-tier server settings.

• Teamcenter Rich client 2-tierThis group contains options to modify settings for the two-tier rich client.

• Dispatcher ServerThis group contains options to modify Dispatcher Server settings.

• Dispatcher ClientThis group contains options to modify Dispatcher Client settings.

Note • A Teamcenter configuration is a collection of features associated with oneTeamcenter data directory.

• A Teamcenter installation is a collection of Teamcenter configurationsthat share the same Teamcenter application root directory.

Confirm silent distribution file nameA silent distribution file with the specified name exists on your system. ChooseLoad to load the existing file or choose Overwrite to replace your existing silentdistribution file.



Custom distribution optionsIn this step, you create a custom distribution of Teamcenter software to simplifyinstallation on other hosts. Teamcenter supports the following custom distributions:

• Silent distribution

A silent distribution is an XML-based configuration file you can use to installTeamcenter silently (without user interaction) on another host.

The silent installation configuration file records the selections and values youenter during Teamcenter installation and enables TEM to perform these stepsnoninteractively when executed on another host.

• Compact distribution

A compact distribution is an installable package with a selected subset ofTeamcenter client features. It is much smaller than a full Teamcenter softwaredistribution image and is more easily distributed to multiple hosts in anorganization.

A compact distribution is an alternative to installing Teamcenter from a fullTeamcenter software distribution image. A compact deployable package cancontain a selected subset of Teamcenter features rather than the entire set offeatures in the release. This reduces network loads and simplifies large-scaleTeamcenter deployments by providing an installation package that is smallerand more easily distributed to an organization. For example, a two-tier richclient installation can be packaged in a deployable media as small as 580 MB,where a full Teamcenter distribution can require up to 5 GB. A four-tier richclient compact distribution can be as small as 283 MB, and a Client for Officecompact distribution can be only 93 MB.

Value Description

Create silentconfiguration file

Specifies the path to an existing, writable directory andthe name of the silent configuration file, for example,C:\silent.xml.

Note The silent configuration file must have a .xmlextension.

Create compactdeployable media

Specifies the path to an existing, writable directory and thename of the compact distribution file, for example, C:\tc.zip.

Note The compact deployable media file must have a .zipextension.

Note If your silent installation contains third-party features, set the TEM_PATHenvironment variable on client hosts before running your silent installation.Set this variable to a list of paths that contains the feature XML files andother supporting files. This ensures TEM finds the feature XML files duringinstallation.

For information about creating, launching, and modifying a silentinstallation file, see the Installation on UNIX and Linux Servers Guide andthe Installation on Windows Servers Guide.



Message panelThis panel displays important information about your installation. Read theinformation displayed and click Next to continue.

Confirming selectionsIn this step, you review and confirm the choices you made and start the installationor uninstallation of Teamcenter:

• To change a selection:

1. Click Back until Teamcenter Environment Manager displays the stepcontaining the information you want to change.

Teamcenter Environment Manager saves the information you entered forthe various steps.

2. Make changes where needed, and then click Next until you return to theConfirmation panel.

• To start the installation or uninstallation, click Start.

Installing featuresIn this step, you monitor the process of installing Teamcenter.

When installation completes successfully, Teamcenter Environment Managerdisplays Install Successful.

Teamcenter Environment Manager installs a version of itself (tem.bat or tem.sh) inthe install directory of the Teamcenter root directory. This version of TeamcenterEnvironment Manager enables the Teamcenter administrator to perform sitemaintenance tasks for Teamcenter.

Value Description

Overall Progress Displays the progress of the entire Teamcenter installationprocess.

Message Displays the progress of the current step in the installationprocess.

Show Details Displays the installation details of the current step in theinstallation process.

Teamcenter data directoryIn this step, you specify a location for the Teamcenter data directory (TC_DATA).TEM creates shared data subdirectories and files in this location.

In the Data Directory box, enter the path to the TC_DATA directory.



Volume accessIn this step, you view available volumes for use with Teamcenter. You must havewrite permission on the default volume before you continue with Teamcenterinstallation. If necessary, see your Teamcenter system administrator to obtain writepermission to this volume.

To refresh the lists of available local and remote volumes, click Scan.

Teamcenter installation locationIn this step, you specify locations for the Teamcenter installation root directory(TC_ROOT) and the Teamcenter data directory (TC_DATA).

Recovering from a failed Teamcenter installationTEM detected that a previous Teamcenter installation was unsuccessful. In theCurrent Application Root Directory, type the path to the previously attemptedinstallation. TEM attempts to recover and complete the installation.

Enter Java Runtime Environment locationEnter the path to the Java Runtime Environment (JRE) you want Teamcenter to use.

The JRE is used by Teamcenter applications and Teamcenter Environment Manager(TEM).

Migrating Teamcenter to another JREBefore you update the Java Runtime Environment (JRE) Teamcenter uses, youmust make sure no Teamcenter features that depend on Java are running. Afteryou verify the features listed are not running, select All features from the above listhave been shut down, and then continue.

Uninstall Teamcenter FoundationIn this step, you specify actions to perform during uninstallation of TeamcenterFoundation.

Select Advanced Uninstall Options to see available uninstallation options.

Select Remove to remove the Teamcenter database, volume, and TC_DATA directory.

Warning Removal of the database, volume, and TC_DATA directory is irreversible.Do not select this option unless you are absolutely certain you want toremove these.



Uninstall TeamcenterIn this step, you confirm whether to uninstall Teamcenter from your system.

Confirm removal of all Teamcenter dataIn this step, you confirm whether to remove the Teamcenter database, volume, andTC_DATA directory. If you want to remove all of these, select I want to permanentlyremove these items.

Warning Removal of the database, volume, and TC_DATA directory is irreversible.Do not select this option unless you are absolutely certain you want toremove these.

Completely uninstall TeamcenterIn this step, you confirm whether to completely uninstall Teamcenter from yoursystem. This includes all Teamcenter configurations, databases, volumes, andTeamcenter Environment Manager (TEM).

Confirm removal of all Teamcenter software and dataIn this step, you confirm whether to completely uninstall your Teamcenterinstallation. This includes all Teamcenter configurations, databases, volumes,TC_DATA directory, and Teamcenter Environment Manager (TEM).

If you want to remove all of these, select I want to permanently remove these items.

Warning Removal of the Teamcenter installation is irreversible. Do not selectthis option unless you are absolutely certain you want to remove allTeamcenter software and data from your system.


Chapter

5 Quick preconfigured installation

About quick preconfigured installation in TEM . . . . . . . . . . . . . . . . . . . . . . . 5-1

Product selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Teamcenter four-tier rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Teamcenter corporate server and two-tier rich client . . . . . . . . . . . . . . . . . . . 5-4

Teamcenter corporate server and .NET-based server manager . . . . . . . . . . . . 5-6

Teamcenter corporate server and J2EE-based server manager . . . . . . . . . . . . 5-8


Chapter

5 Quick preconfigured installation

About quick preconfigured installation in TEMThe following TEM help topics describe panels for creating a quick preconfiguredinstallation of Teamcenter.

TEM provides a set of predefined common Teamcenter configurations that requireminimal user input to install. To create one of these installations, click QuickPreconfigured Install in the Welcome to Teamcenter panel:

This allows you to choose one of four common Teamcenter configurations:


Chapter 5 Quick preconfigured installation

Quick preconfigured installations provide in as few as four TEM panels Teamcenterconfigurations that otherwise require as many as 18 panels. These simplifiedTeamcenter installations are designed to require minimal documentation outsidethe installation wizard. Help for each panel in the quick preconfigured installation

process is provided from the help button .

For advanced details about Teamcenter installation, see the Teamcenter serverinstallation guides (for Windows and UNIX/Linux) and the client installation guides(for Windows and Linux).

Product selectionIn this step, you choose which quick preconfigured Teamcenter configuration youwant to install.

Option Description

Teamcenter Rich Client4–Tier

Installs a Teamcenter four-tier rich client toconnect to an existing Teamcenter Web tier.

Teamcenter Corporate Serverand J2EE Based ServerManager

Installs a Teamcenter corporate server and aJ2EE-based server manager to which Teamcenterclients can connect.


Quick preconfigured installation

Option Description

Teamcenter Corporate Serverand .Net Based ServerManager

Installs a Teamcenter corporate server and aMicrosoft .NET-based server manager to whichTeamcenter clients can connect.

This option is available only on Microsoft Windowshosts and requires Microsoft Internet InformationServer (IIS) and Microsoft .NET. TEM verifies therequired versions of IIS and Microsoft .NET areinstalled.

Teamcenter Corporate Serverand Rich Client 2–Tier

Installs a Teamcenter corporate server with atwo-tier rich client.

Note After you complete a quick preconfigured installation, you can modifyyour Teamcenter configuration by launching TEM from the Windows startmenu or from the install directory under the Teamcenter home directory.The launches TEM in maintenance mode, allowing you to add Teamcenterfeatures and change configuration values if needed.

Teamcenter four-tier rich clientIn this step, you provide information to install a four-tier rich client that connects toan existing Teamcenter middle tier and corporate server.

Value Description

4 Tier Server URI Specifies the URI to the rich client middle tier.Type a URI of the following form:

http://host:port/tcFCC Parent Specifies the URI to the FMS server cache (FSC)

used by the local FMS client cache (FCC) in yourfour-tier rich client configuration. Type a URI ofthe following form:

http://host:port

For more information about configuringFile Management System, see the SystemAdministration Guide.

Installation Directory Specifies the directory in which you want to installTeamcenter. Enter a directory that does not exist.TEM creates the directory you specify.

Note Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, usehost names in URIs wherever possible so the domain name system (DNS)can determine which IP address should be used.

If you must use IP addresses and your network uses IPv6 addresses, enclosethe literal IPv6 address in square brackets, for example:

http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc



Teamcenter corporate server and two-tier rich clientIn this step, you provide information to create the Teamcenter corporate serverand install a two-tier rich client.

This option also installs the Teamcenter Business Modeler IDE client to use toadminister the Teamcenter corporate server.

Before you proceed, make sure you have the following values for your databaseserver:

• Database type (IBM DB2, Oracle, or Microsoft SQL Server)• Database name and port• Database system user name and password

If you do not know these values, contact your database administrator.

For information about installing a database server and configuring databases for usewith Teamcenter, see the Installation on UNIX and Linux Servers Guide and theInstallation on Windows Servers Guide in the Teamcenter online help collection.

Value Description

OS User Password Specifies the password for the operating systemuser account under which you logged on before youlaunched TEM. Teamcenter services run underthis account.

If you want to install Teamcenter under a differentaccount, cancel this installation and restart TEMusing the account you want to use.

Database Type Specifies the database vendor for your database.Select IBM DB2, Oracle, or Microsoft SQL Server.

Database Name/Service Specifies the name of the database to be used byTeamcenter.

For IBM DB2 and Microsoft SQL Server databases,this box is labeled Database Name. For Oracledatabases, it is labeled Service.

Type the name of the database or Oracle service tobe used by Teamcenter. This name was definedwhen the database server was created.

Port Specifies the port number used by the databaseserver. The port number was determined when thedatabase server was installed.

Database System User Specifies the user name of the database systemadministrator account.

The default value is one of the following:

• IBM DB2 databases: db2admin• Oracle databases: system• Microsoft SQL Server databases: sa



Value Description

Database System Password Specifies the password for the database systemadministrator account.

Caution Make sure the password does notcontain space characters or any of thefollowing characters:

! @ $ % ’ " : ; . < > ( ) { }

Database Path Specifies the directory in which to create theTeamcenter database on the database server.

Type an appropriate location. If necessary,consult your database administrator. ForOracle servers, the database path is typicallyORACLE_HOME\oradata\Oracle_SID(on Windows systems) orORACLE_HOME/oradata/Oracle_SID (onUNIX/Linux systems).

Character Encoding Type Specifies by canonical name of the characterencoding set Teamcenter clients use to access thedatabase.

Caution To prevent data corruption, thischaracter encoding set must match theencoding set used by the Teamcenterdatabase.

For more information about character encodingsets, see the Localization Guide.

Volume Directory Specifies the path to the Teamcenter volume.

A Teamcenter volume is a directory that storesfiles managed by Teamcenter. It is controlled byone, and only one, database.

In this quick preconfigured installation, TEMcreates the Teamcenter database and volume, andalso an FMS server cache (FSC) that creates andserves default volumes. The volume can be createdwhile installing a Teamcenter corporate server ora volume server.

After installation, you can optionally createadditional volumes for a database using TEM orthe rich client Organization application.

Note If the specified volume directory does nothave sufficient space, TEM prompts you tospecify a different location.




Teamcenter corporate server and .NET-based server managerIn this step, you provide information to create the Teamcenter corporate serverand configure the .NET based server manager to which Teamcenter four-tier richclients can connect.

This option also installs the Teamcenter two-tier rich client and the BusinessModeler IDE client to use to administer the Teamcenter corporate server.



If you do not know these values, contact your database administrator.


Value Description













Value Description



! @ $ % ’ " : ; . < > ( ) { }














Teamcenter corporate server and J2EE-based server managerIn this step, you provide information to create the Teamcenter corporate serverand configure the J2EE based server manager to which Teamcenter four-tier richclients can connect.

This option also installs the Teamcenter two-tier rich client and the BusinessModeler IDE client to use to administer the Teamcenter corporate server.



If you do not know these values, contact your database administrator before youproceed.


Value Description













Value Description



! @ $ % ’ " : ; . < > ( ) { }













Chapter

6 Business Modeler IDE

Business Modeler IDE templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Database Configuration Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Business Modeler IDE templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Business Modeler IDE client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Database Template Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Updating a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2


Chapter

6 Business Modeler IDE

Business Modeler IDE templatesIn this step, you select templates to apply to your Business Modeler IDEenvironment. Business Modeler templates contain the data model for Teamcentersolutions. The Teamcenter Foundation template contains the data model used forcore Teamcenter functions. Other templates extend this template.

Select the Teamcenter Foundation template and any other templates you wantto apply.

To install additional template, such as custom templates you built, click Browse tolocate those templates and add them to the table of available templates.

Database Configuration ChangeThis panel contains important information about steps you must perform to completethe Business Modeler IDE installation. Select the check box to indicate you haveread this information, then click Next to continue.

Business Modeler IDE templatesIn this step, you add templates to apply to your Business Modeler IDE environment.The templates contain the data model for Teamcenter solutions.

This panel shows two lists. The Installed Templates list displays the list of templatesalready installed and available for use within the Business Modeler IDE client. TheCandidate Templates list displays the list of new templates you select to update orinstall. Click the Browse button to locate templates to update or install.

Value DescriptionInstalled Templates The templates installed to the server.

CandidateTemplates

Templates that can be installed to the server, obtained byclicking the Browse button and locating the templates.Select the templates you want to install to the BusinessModeler IDE.

Browse Click this button to locate templates to install to theBusiness Modeler IDE. Default Teamcenter templates arelocated on the installation source in the tc directory.


Chapter 6 Business Modeler IDE

Business Modeler IDE clientIn this step, you select templates to install in the Business Modeler IDE.

Templates contain the data model for Teamcenter solutions. The TeamcenterFoundation template is installed by default. The Foundation template contains thedata model used for core Teamcenterfunctions. All custom templates must extendthe Foundation template.

Click Add to select the templates to install. Click Remove to remove templatesfrom the list.

If you have custom templates or templates from a third-party to install, click Browseand browse to the directory where the templates are located.

To view the contents of a template, click View.

Note Select the same templates that were installed on the server so that theBusiness Modeler IDE contains the same data model definitions as theserver.

Database Template SummaryThis panel is for information only. It displays a list of templates to be applied whenTEM populates the database during installation. Click Next to accept and continue.

Database configurationIn this step, you verify the list of templates to be applied to the database according tothe features in your configuration.

If a template is shown without an associated feature, click Browse to locate themissing feature XML file.

Updating a databaseThis panel allows you to apply updated database templates when performingmaintenance on your Teamcenter configuration.

The database update mode depends on the option you select under TeamcenterFoundation in the Feature Maintenance panel:

• Update Database (Full Model)

Updates the database with Business Modeler IDE templates that contains all thecustom data model, including schema items such as business objects and classes.

• Update Database (Perform Live Updates)

Updates the database with live update templates that contain only nonschemadata such as LOVs and rules.

The template list shows currently installed templates.


Business Modeler IDE

To add a template to the list, click Browse to navigate to the directorywhere the packaged template files are located, and then select the updatedtemplate-name_template.zip file.

Click Refresh to query the database for installed templates.

For more information about live updates, see the Business Modeler IDE Guide.


Chapter

7 File Management System

About File Management System installation in TEM . . . . . . . . . . . . . . . . . . . 7-1

FCC settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

FCC parents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Installing FMS server cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

FSC cache settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

FSC proxy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

FSC service – FCC defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Selecting the FSC deployment model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

FSC service additional sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Adding an external site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Create/Edit remote site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

FSC service connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Rich client FCC parent settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

FSC service additional group sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Verifying the FSC service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

FSC client map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

FSC groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

FSC nonmaster settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

FSC servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

FSC service additional group sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

FSC service additional sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Create/Edit FSC client map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12


Create/Edit file store group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Create/Edit FSC group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Create/Edit FSC server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

File store group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Scan for sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Assign to FSC group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Volume query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

FSC security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Create/edit remote group site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Teamcenter Environment Manager Help PLM00128 H

Chapter

7 File Management System

About File Management System installation in TEMThe following TEM help topics describe panels that allow you to create and manageFile Management System (FMS) volumes and services. For more informationabout using FMS, see the appropriate server installation guide (for Windows orUNIX/Linux) and the System Administration Guide.

FCC settingsIn this step, you configure the installation directory for the FMS client cache (FCC)process for the locally installed rich client.

The FCC process uploads files to a file server, requests files from the file server,and caches client files.

Value Description

Use current FCC Select this option if you want to keep your existing FCClocation.

Use new FCC Select this option if you want to use the proposed new FCClocation.

Teamcenter Environment Manager sets the FMS_HOME environment variable onthis host to point to the selected location.

If you want to use the proposed FMS_HOME location but add information fromthe current FMS_HOME location on the client host, select Merge values fromexisting FMS_HOME. This results in an FCC configured to support the previousFMS_HOME environment as well as the one being installed.


Chapter 7 File Management System

Note The option to merge values from an existing FMS_HOME location isenabled only if your current configuration includes Teamcenter Foundationand the existing FMS_HOME location meets the following conditions:

• Detectable

The previous FMS_HOME location must be the current value of theFMS_HOME environment variable.

• Accessible

The installer must be able to open and read the previously installedfcc.xml file to extract the required information.

• Legible

The installer must be able to parse this information using thefccconfig.dtd file being installed. At a minimum, it must be well-formedXML, containing no XML features absent from the installing DTD.

• Upgradable

The existing installation must be of an equal or earlier version than thatyou are installing. Retrograde merges may be detected if the versionattribute of the fccconfig element of the fcc.xml file is in the currentFMS_HOME directory.

For advanced FCC configuration options, including enabling Teamcenter clientcommunication system (TCCS), click Advanced.

FCC parentsIn this step, you specify the FMS server caches (FSCs) used by the FMS client cache(FCC). The FCC can have multiple parent FSCs. FSCs are used in the priorityyou specify.

The FSC assignment mode box specifies how you want to assign FSCs.

To add an FSC to the list, click Add. TEM adds a row to the table of FSC values.Double-click the Protocol, Host, Port, or Priority boxes to enter values.


To remove an FSC from the table, select the row and click Delete.

Installing FMS server cacheIn this step, you install and configure an FMS server cache (FSC) process that actsas either a volume server for file management or a server-level performance cacheserver for shared data access between multiple users:

• When you install Teamcenter on a host that physically contains or directlymounts a Teamcenter volume, you install an FSC to act as a volume server,uploading files to a Teamcenter volume and downloading files from the volume.


File Management System

• When you install Teamcenter on a host where a volume is not located or directlymounted, you install an FSC to act as a performance cache server, managing twosegment file caches, one for downloading files and one for uploading files.

• You also either install an FMS master configuration file on this host or identify ahost in the FMS network that has an installation of this file (the master host).

The FMS master configuration file describes the FMS network and providesdefault configuration values for FMS server caches and client caches. When youinstall multiple volumes on different hosts for the same database, the multipleFSCs are linked through a common FMS master host.

References:

• For an overview of installing FMS and Teamcenter volumes, see the Installationon UNIX and Linux Servers Guide and the Installation on Windows ServersGuide in the Teamcenter help library.

• For detailed descriptions of the FMS deployment options and configurationchoices, see the System Administration Guide in the Teamcenter online helpcollection.

Value Description

FSC ID Specifies the identifier that FMS uses to identify this FSCserver within the FMS network; it must be unique withinthe network.

Port The port address dedicated to the FSC process. The defaultvalue is 4544.

Enableconfigurationmaster

Specifies that you want to install the FMS masterconfiguration file (fmsmaster.xml) on the local host.

Tip If you are installing only one FSC server inthe network, you must select this option. EachTeamcenter network must have at least one masterconfiguration file and one FSC designated to readthis file.

FSC Parent URL Specifies the URL to the parent FSC if the current FSCis not a master.

For advanced FSC configuration options, click Advanced.

FSC cache settingsIn this step, you specify settings for the FSC cache.

Value Description

Read Cache



Value DescriptionDirectory Specifies the path to the file system location on the local

host for the read cache required when the FSC serveracts as a cache server. The directory must not exist; it iscreated by Teamcenter Environment Manager.

The default $HOME setting creates the read cache inthe Documents and Settings directory for Windowssystems and in the /tmp directory for UNIX systems.

Tip For FMS to operate correctly, the location youspecify must be on the local host.

Max. Size (MB) Specifies the size in megabytes for the read cacherequired when the FSC server acts as a cache server.

Tip If you are installing a volume on this host,FMS does not use the read cache; SiemensPLM Software recommends accepting thedefault cache size (10 megabytes). Do notspecify 0; specifying 0 creates a file cachewith a default size larger than 10 megabytes.

If you are not installing a volume on thishost, FMS acts as a cache server. In thiscase, Siemens PLM Software recommendsincreasing the value to 1000 megabytes.

Write CacheDirectory Specifies the path to the file system location on the local

host for the write cache required when the FSC serveracts as a cache server. The directory must not exist; it iscreated by Teamcenter Environment Manager.

The default $HOME setting creates the write cache inthe Documents and Settings directory for Windowssystems and in the /tmp directory for UNIX systems.

Tip For FMS to operate correctly, the location youspecify must be on the local host.

Max. Size (MB) Specifies the size in megabytes for the write cacherequired when the FSC server acts as a cache server.

Tip If you are installing a volume on this host,FMS does not use the write cache; SiemensPLM Software recommends accepting thedefault cache size (10 megabytes). Do notspecify 0; specifying 0 creates a file cachewith a default size larger than 10 megabytes.

If you are not installing a volume on thishost, FMS acts as a cache server. In thiscase, Siemens PLM Software recommends



Value Descriptionincreasing the value to 512 megabytes ormore.

FSC proxy settingsIn this step, you specify proxy settings for the FMS server cache (FSC).

Value DescriptionEnable HTTP Proxy Specifies that this FSC server contacts other FSC servers

through a proxy server in HTTP mode.

Tip Select this option only when installing other FSCprocesses that can be contacted only through afirewall.

Host Specifies the name of the host running the HTTP proxyserver.

Port Specifies the number of the port the HTTP proxy serverlistens on.

Enable HTTPS Proxy Specifies that this FSC server communicates with otherFSC servers through a proxy server in HTTPS mode.

Tip Select this option only when installing other FSCprocesses that can be contacted only through afirewall.

Host Specifies the name of the host running the HTTPS proxyserver.

Port Specifies the number of the port the HTTPS proxy serverlistens on.

FSC service – FCC defaultsIn this step, you enter default settings FMS clients use to connect to the FSC service.

Value Description

Windows CacheDirectory

Specifies the default file system location for the FMS clientcache (FCC) on all Windows-based rich client hosts. Thisdefault setting can be overridden by the FCC configurationfile.

Tip Select a location that can be created locally onall Windows-based rich client hosts. The valueyou enter must include a reference to $HOMEor $USER.



Value Description

UNIX CacheDirectory

Specifies the default file system location for the FMS clientcache (FCC) on all UNIX-based rich client hosts. Thisdefault setting can be overridden by the FCC configurationfile.

Tip Select a location that can be created locally onall UNIX-based rich client hosts.

Max. Read CacheSize (MB)

Specifies the default maximum size in megabytes of wholefiles downloaded from the volume to rich client hosts. Userscannot download a file whose size exceeds the value you setfor this field. This default setting can be overridden by theFMS client cache configuration file.

Tip Select a size large enough to accommodate thelargest whole file that users download from thevolume.

Max. Write CacheSize (MB)

Specifies the default maximum size in megabytes of wholefiles uploaded to a volume from rich client hosts. Userscannot upload a file whose size exceeds the value you setfor this field. This default setting can be overridden by theFMS client cache configuration file.

Tip Select a size large enough to accommodate thelargest whole file that users upload to the volume.

Max. Partial CacheSize (MB)

Specifies the default maximum size in megabytes ofthe segment file cache used by Teamcenter lifecyclevisualization and Engineering Process ManagementVisualization on rich client hosts.

This default setting can be overridden by the FMS clientcache configuration file.

Tip • If no or few rich client users in the networkdeploy Lifecycle Visualization, Siemens PLMSoftware recommends setting this cache sizeto 10 megabytes. Do not specify 0; specifying 0creates a file cache with a default size largerthan 10 megabytes.

• If rich client users in the network deployLifecycle Visualization, Siemens PLM Softwarerecommends setting this cache size in the rangeof 2000 megabytes to 4000 megabytes.

The cache size is initially small, expandingto the maximum size only if a user launchesLifecycle Visualization to view a file of that size.The initial size of the cache is proportional tothe value specify.



Parent FSCs are listed in the Client Accessible External Sites table. To add aparent FSC to the list, click Add. To edit or remove an existing site in the table,click Edit or Remove.For more information about configuring File Management System, see the SystemAdministration Guide.

Selecting the FSC deployment modelIn this step, you choose the FMS server and volume model deployment model youwant to use. Select a model from the list. Teamcenter Environment Managerdisplays a description of the selected model.

FSC service additional sitesIn this step, you can enter information about additional sites to which the FMSserver cache (FSC) service can connect.

To add a site to the list, click Add.To edit or remove an existing site, click Edit or Remove.When you run TEM in maintenance mode, you can click Scan to locate existingFSCs in your Teamcenter configuration.

Note If you have multiple FSCs, it may be useful to group them. You can add FSCgroups when you run TEM in maintenance mode.

Adding an external siteIn this step, you enter settings for an additional external site.

Value Description

Site ID Specifies the site ID for the external site.

Assignment Mode Specifies an FSC assignment mode. Theoptions are clientmap and parentfsc. Selectparentfsc only if recommended by your systemadministrator. The default value is clientmap.

You can also specify an FSC assignment mode in FSC assignment mode. Theoptions are clientmap and parentfsc. Select parentfsc only if recommended by yoursystem administrator. The default value is clientmap.To add a site to the list of external FSCs accessible from this host, click Add. Toenter or change any value in the table of sites, double-click the box containing thatvalue, and then type the new value.

Value Description

Protocol Specifies the protocol used by the FSC. Thedefault value is http.



Value DescriptionHost Specifies the host name of the FSC.

Port Specifies the port used by the FSC. The defaultvalue is 4544.

Path Specifies the path to the FSC.

Priority Specifies the assignment priority for the FSC.The default value is 0.

Transport Specifies the transport mode used by the FSC.The default value is lan.

To remove a site from the list, click Remove.

For more information about configuring File Management System, see the SystemAdministration Guide.

Create/Edit remote siteIn this step, enter the connection information for the remote site.

Value Description

Site ID Provide an ID for the remote site.

FSC ID Enter the ID of the FSC you want to assign to the remotesite.

Protocol Select the transport method to use to connect to the remotesite, either http or https (HTTP secure).

Host Enter the name of the remote site host machine.

Port Enter the port address dedicated to the FSC process. Thedefault is 4544.

Priority Enter a number to designate the priority this remote sitehas for processing. The default is 0, meaning that it hasthe highest priority. Next would be priority 1, followed bypriority 2, and so on.

FSC service connectionsIn this step, you specify ports on which the FMS server cache (FSC) service listens.

The FSC service can listen on multiple ports.

To add a port to the list, click Add. TEM adds a row to the table of port values.Double-click the Port or Protocol boxes to enter values.


To remove a port from the table, select the row and click Delete.



Rich client FCC parent settingsIn this step, you specify settings for accessing the parent hosts of the FMS file servercache (FSC).

You can specify a FSC assignment mode in FSC assignment mode. The options areclientmap and parentfsc. Choose parentfsc only if recommended by your systemadministrator. The default value is clientmap.

Parent hosts are listed in the FCC Parents field. To add a parent host to the list,perform the following steps:

1. Click Add.

2. Double-click the Host box, then type the host name of the FSC.

3. Double-click the Port box, then type the port used by the FSC. The default valueis 4444.

4. In the Protocol box, type the appropriate protocol used by the FSC.

5. In the Transport box, type the appropriate transport mode used by the FSC.The default value is lan.

If you want to add access to additional hosts, repeat steps 1 through 5 to add accessinformation for each FSC parent host.

After you add an FSC host, you can remove hosts from the list or edit settings usingthe Remove and Edit buttons. You can also change the priority the rich client usesin accessing FSC parent hosts by selecting a host in the table and clicking the Upor Down buttons.

For more information about configuring File Management System, see the SystemAdministration Guide.

FSC service additional group sitesIn this step, you can enter information about additional FMS server cache (FSC)group sites to which the FSC service can connect.

If you have multiple FSCs, it may be useful to group them. Create FSC groups fromthis panel when you run TEM in maintenance mode.

To add an FSC group to the list, click Add. TEM adds a row to the table of remotesites. Double-click the FSC Group, Site ID, FSC ID, FSC Server, or Priority boxes toenter values.


To remove a site from the table, select the row and click Delete.

When you run TEM in maintenance mode, you can click Scan to locate existingFSCs in your Teamcenter configuration.



Verifying the FSC serviceIn this step, the installer checks if an FSC (FMS server cache) is installed andwhether it is configured as a master. If both are true, click NEXT to continue thismaintenance activity.

FSC client mapIn this step, click the Add button to add a new DNS (domain name system) mappingto the FMS master. When you click the Add button, enter values in the Create/EditFSC Client Map dialog box:

Value Description

FSC Group Select an FSC group to assign the DNS. An FSC groupis a group of server caches defined in the FMS masterconfiguration file.

IP Subnet/Mask Enter the Internet Protocol (IP) subnet and mask addressfor the DNS.

DNS Zone Enter the DNS zone if you want to use a zone instead ofsubnet and mask.

DNS Hostname Enter the DNS host name if you want to use host nameinstead of subnet and mask.

DNS Default Select if you want to use the system’s default DNS address.Use this whenever subnet/mask, DNS zone, or DNS hostname client maps fail to map an FCC. This default attributereplaces the legacy mask=0.0.0.0 technique previouslyused for subnet/mask maps.

DNS Not Defined Select if the DNS is not defined for the system. This can beused to define an FSC map whenever a requesting FCC’s IPaddress cannot be converted to a DNS name.

FSC ID Select the FSC to map to.

Priority Enter the priority you want to assign this DNS on theserver, for example, 0,1, 2, 3, and so on.

FSC Transport Select lan (local area network) or wan (wide area network)as the kind of network to transport the FSC data.

FSC Connection Select the type of connection to make with the FSC.

FSC groupsIn this step, click the Add button to add FSC groups. An FSC (FMS Server Cache)group is a group of server caches defined in the File Management System (FMS)master configuration file.



FSC nonmaster settingsIn this step, you enter the host, port, protocol, and priority values for the FSCmaster service.

FSC serversIn this step, enter the FSC servers that are accessible from this FMS master.

Value Description

FSC ID Enter the ID you want to assign to the FSC.

FSC Group Select the FSC group that this new FSC will belong to. AnFSC can only belong to one group.

Host Enter the name of the host machine where the FSC willreside.

Server Type Select the type of FSC server you are creating:

• Master FSC Server

The main FSC server.

• Non-Master FSC Server

A secondary FSC server.

• External Load Balancer

A server that helps route FMS messages.

External LoadBalancer

Select the external load balancer to use with this FSCserver. External load balancers are external networkhardware devices not supplied by Siemens PLM Software,but are capable of forwarding FMS messages throughnetwork channels to other FSCs.

Protocol The transport method, either http or https (HTTP secure).Port The port address dedicated to the FSC process.

Add Click to add a port for the server to use. By default, thehttp protocol is assigned port 4544, and the https protocol isassigned port 4545. To change the port, click in the port cell.

Delete Click to remove a protocol and port.

FSC service additional group sitesIn this step, you can enter information about additional FMS server cache (FSC)group sites to which the FSC service can connect.

If you have multiple FSCs, it may be useful to group them. Create FSC groups fromthis panel when you run TEM in maintenance mode.



To add an FSC group to the list, click Add. TEM adds a row to the table of remotesites. Double-click the FSC Group, Site ID, FSC ID, FSC Server, or Priority boxes toenter values.




FSC service additional sitesIn this step, you can enter information about additional sites to which the FMSserver cache (FSC) service can connect.

To add a site to the list, click Add. TEM adds a row to the table of remote sites.Double-click the Site ID, FSC ID, or FSC Server boxes to enter values.




Note • You cannot specify multiple remote FSCs using TEM. You can do thisonly by manually updating the master configuration (fmsmaster.xml)file.

If you enter multiple FSCs in TEM, only the last-created site ID isrecorded in the master configuration file. TEM does not display anymessage that states this.

For more information about specifying multiple remote FSCs in thefmsmaster.xml file, see the System Administration Guide.

• If you have multiple FSCs, it may be useful to group them. You can addFSC groups when you run TEM in maintenance mode.

Create/Edit FSC client mapIn this step, use DNS (domain name system) names to map an FMS client cache(FCC) to the parent FMS server cache (FSC).

Value Description

IP Subnet/Mask Enter the Internet Protocol (IP) subnet and mask addressfor the DNS.

CIDR Enter the Classless Inter-Domain Routing (CIDR) valuethat specifies the desired subnetted IP address in the form.

DNS Zone Enter the DNS zone if you want to use a zone instead ofsubnet and mask.



Value Description

DNS Hostname Enter the DNS host name if you want to use host nameinstead of subnet and mask.

DNS Default Select if you want to use the system’s default DNS address.Use this whenever subnet/mask, DNS zone, or DNS hostname client maps fail to map an FCC. This default attributereplaces the legacy mask=0.0.0.0 technique previouslyused for subnet/mask maps.

DNS Not Defined Select if the DNS is not defined for the system. This can beused to define an FSC map whenever a requesting FCC’s IPaddress cannot be converted to a DNS name.

FSC ID Select the FSC to map to.

Priority Enter the priority you want to assign this DNS on theserver, for example, 0,1, 2, 3, and so on.

FSC Transport Select lan (local area network) or wan (wide area network)as the kind of network to transport the FSC data.

FSC Connection Select the type of connection to make with the FSC.

Create/Edit file store groupIn this step, you define a file store group, which specifies volumes to be load balancedacross several FSCs. You can load balance FMS data by distributing the networkaccess load.

Select the FSC (FMS server cache) group to which the file store group belongs.Then select the FSC servers and external load balancers in the table that shouldhave access to the file store group. Also select the priority with which each serveraccesses the volume.

Value DescriptionName Enter the name you want to assign to the file store group.

FSC Group Select an FSC group to assign to the file store group. (AnFSC Group is a group of server caches defined in the FMSmaster configuration file.)

FSC Servers andExternal LoadBalancers

Select the FSC servers and external load balancers thatshould have access to the file store group, and select thepriority to define its load balancing priority (for example,0, 1, 2, 3, and so on).

Create/Edit FSC groupIn this step, you provide a name for the FSC group. An FSC (FMS server cache)group is a group of server caches defined in the File Management System (FMS)master configuration file.



Create/Edit FSC serverIn this step, enter the information for the FSC server or external load balancer.

FMS caching enables placing the data close to the user, while maintaining a centralfile volume and database store. FMS requires the installation of FMS server cache(FSC) and FMS client cache (FCC) components. The FSC component provides aserver process and file caches for Teamcenter server hosts. (The FCC componentprovides a client process and file caches for rich clients on user workstations.)

Value Description

FSC ID Enter the ID you want to assign to the FSC.

FSC Group Select the FSC group that this new FSC will belong to. AnFSC can only belong to one group.

Host Enter the name of the host machine where the FSC willreside.

Server Type Select the type of FSC server you are creating:

• Master FSC Server

The main FSC server.

• Non-Master FSC Server

A secondary FSC server.

• External Load Balancer

A server that helps route FMS messages.

External LoadBalancer

Select the external load balancer to use with this FSCserver. External load balancers are external networkhardware devices not supplied by Siemens PLM Software,but are capable of forwarding FMS messages throughnetwork channels to other FSCs.

Protocol The transport method, either http or https (http secure).Port The port address dedicated to the FSC process.

Add Click to add a port for the server to use. By default the httpprotocol is assigned port 4544, and the https protocol isassigned port 4545. To change the port, click in the port cell.

Delete Click to remove a protocol and port.

File store groupIn this step, you assign volumes to file store groups. A file store group specifiesvolumes to be load balanced across several FSCs. Grouping volumes into file storegroups is not required, but it is useful when creating a failover FMS master.



Value DescriptionAdd Click the Add button and enter the name of the file store

group. Then click the arrow in the FSC Group box to selectthe FSC group to which the file store belongs. Select theFSC servers and external load balancers in the table thatcan access to the file store group. Also select the prioritywith which each server accesses the volume.

Edit Make changes to the file store group.

Delete Remove a file store group.

Scan for sitesSelect the sites that this FSC should have access to.

Value DescriptionImport Whether the site is imported.

Site ID The ID for the FSC site.

FSC ID The ID for the FSC (FMS Server cache).

FSC Server The server where the FMS process runs.

Priority The priority that this site has for processing, for example,0,1, 2, 3, and so on.

Assign to FSC groupIn this step, you select the FSC group to assign to the servers. An FSC group is agroup of server caches defined in the FMS master configuration file. All FSCs mustbelong to one, and only one, FSC group.

Volume queryIn this step, you search for available volumes in the FMS master file. Volumes canbe assigned to an FSC server, to an external load balancer, or to a file store group.



Value DescriptionAssign Click this button to assign a volume to an FSC server, to an

external load balancer, or to a file store group. Choose theseoptions on the Assign Volume dialog box:

• Assign to FSC Server or External Load Balancer

Select to assign the volume to an FSC server (a machinewhere FMS processes run) or an external load balancer(a machine designated to take some of the load of FMSprocesses).

• Assign to File Store Group

Select to assign the volume to a file store group, whichspecifies volumes to be load balanced across severalFSCs.

Scan Click this button to query the database for a current list ofvolumes. Any new volumes will be added to the list, andany information on existing volumes will be updated.

FSC securityIn this step, you specify whether to enable HTTPS access and also specify theHTTPS access port.

Create/edit remote group siteIn this step, enter the connection information for the remote site.

Value Description

FSC Group Select an FSC group from the list.

Site ID Provide an ID for the remote site.

FSC ID Enter the ID of the FSC you want to assign to the remotesite.

Protocol Select the transport method to use to connect to the remotesite, either http or https (HTTP secure).

Host Enter the name of the remote site host machine.

Port Enter the port address dedicated to the FSC process. Thedefault is 4544.

Priority Enter a number to designate the priority this remote sitehas for processing. The default is 0, meaning that it hasthe highest priority. Next would be priority 1, followed bypriority 2, and so on.


Chapter

8 Teamcenter client communicationsystem

About Teamcenter client communication system configuration in TEM . . . . . . 8-1

Teamcenter client communication system (TCCS) switch . . . . . . . . . . . . . . . . 8-1

TCCS environment settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

TCCS forward proxy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

TCCS reverse proxy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

TCCS client tag filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

TCCS configuration selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Removing a TCCS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Kerberos authentication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Secure socket layer (SSL) settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6


Chapter

8 Teamcenter client communicationsystem

About Teamcenter client communication system configuration in TEMThe following TEM help topics describe panels for installing and configuringTeamcenter client communication system (TCCS).

For more information about installing and configuring TCCS, see the appropriateserver installation guide (for Windows or UNIX/Linux).

For more information about managing TCCS environments, see the SystemAdministration Guide.

Teamcenter client communication system (TCCS) switchIn this step, you choose whether to enable TCCS in your Teamcenter installation.TCCS provides client support for proxy environments and centralized configurationcapabilities.

Select the Use Configurations and Environments check box to use TCCSconfigurations.


TCCS environment settingsIn this step, you specify environment settings for Teamcenter client communicationsystem (TCCS).

Click Add to add an environment to the table of TCCS environments. This addsa row to the table. Double-click a box in the new row to type a value. For eachenvironment, type a name, URI, and Security Services logon values.

To remove a configuration from the table, select the appropriate row and clickRemove.


Chapter 8 Teamcenter client communication system





TCCS forward proxy settingsIn this step, you define forward proxy settings for Teamcenter client communicationsystem (TCCS).

Value Description

Do not use forward proxy Specifies that you do not want to use a forwardproxy.

Use web browser settings Specifies that you want to obtain proxy settingsfrom your Web browser.

Detect settings from network Specifies that you want to obtain proxy settingsfrom your local network.

Retrieve settings from URL Specifies that you want to obtain settings froma specified URL.

Proxy URL Specifies the URL to the Web server fromwhich you want to obtain proxy settings. Thisvalue must be a valid URL for a forward proxyautoconfiguration file.

Configure settings manually Specifies that you want to enter proxy settingsmanually.

All protocols host Specifies a name of a valid proxy to use for allprotocols. In the accompanying Port box, typethe port used by the proxy host.

HTTP Host Specifies the host of a forward proxy server forthe HTTP protocol. In the accompanying Portbox, type the port used by the proxy host.

HTTPS Host Specifies the host of a forward proxy server forthe HTTPS protocol. In the accompanying Portbox, type the port used by the proxy host.

Exceptions Specifies a semicolon-delimited list of hostnames and IP addresses to exempt. This boxis optional.



Teamcenter client communication system

Note Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, usehost names in proxy URLs wherever possible so the domain name system(DNS) can determine which IP address should be used.



TCCS reverse proxy settingsIn this step, you specify reverse proxy settings for Teamcenter client communicationsystem (TCCS) on this client host. Teamcenter uses these settings to detect a logonWeb page from a reverse proxy server through which Teamcenter services areaccessed.

Reverse proxy configuration is optional.

The criteria table lists the reverse proxy criteria currently defined. Each row of thetable is a criteria XML element defined in the specified format. By default, the tableis blank and no criteria are defined. A criterion string is of the following form:

Header_Name1,Header_Value1,Header_Name2,Header_Value2,…:Form_Action

Each criterion must contain at least one header name/header value pair or at least asingle form action.

To add a criterion to the table, perform the following steps:

1. Click Add.

2. In the Criteria Details table, add or remove HTTP header names and values forthe selected criterion using the Add and Remove buttons.

3. In the Form Action box, specify a form action.

4. Click Apply.

The criterion is added to the criteria table.

Teamcenter Environment Manager (TEM) validates reverse proxy criteria. If youdo not want TEM to perform this validation, select the Skip reverse proxy criteriacheck check box.



Note • If you must connect to a Teamcenter environment through a reverseproxy server (such as WebSEAL or SiteMinder), you may need toconfigure reverse proxy settings for TCCS.

o If you use SiteMinder, you must configure TCCS to detect form-basedchallenges originating from the reverse proxy by adding the followingcriterion to the Private Reverse Proxy Settings table.

Header name Header valuecheckHeaders false

This setting also applies to other reverse proxy servers that do notsend specific header information in the 200 form-based challenge.

o If you use WebSEAL and you deploy the TCCS configuration, addthe following criterion to the Private Reverse Proxy Settings table.

Header name Header value Form actionserver webseal /pkmslogin.form

This is required because the settings in the deployedreverseproxy_cfg.xml override the default WebSEALconfiguration.

If you do not deploy the TCCS configuration, TCCS uses thedefault WebSEAL configuration, so this manual configuration isnot required.

• Criteria definitions are written to the reverseproxy_cfg.xml file.

TCCS client tag filterIn this step, you optionally specify a pattern on which to filter Teamcenter clientcommunication system (TCCS) environments available to the rich client.

In the Client Tag Filter box, type a pattern to apply when filtering TCCSenvironments. Wildcard characters (*) are allowed.

The Client Tag Filter pattern is compared to the Tag parameters on defined TCCSenvironments. Environments that do not fit the pattern are not available to therich client. For example, If the rich client Client Tag Filter value is 9.*, all TCCSenvironments with Tag values beginning with 9. are available to the rich client.Environments withTag values beginning with 10 are not available.




TCCS configuration selectionIn this step, you choose whether to modify the shared or private Teamcenter clientcommunication system (TCCS) configuration.

If both the shared and the private TCCS configurations exist, the privateconfiguration takes precedence. If both shared and private TCCS configurationsexist, modifying the shared configuration may have no effect on clients becausethe private configuration takes precedence. Shared configurations may be editedonly by administrators.


Removing a TCCS configurationIn this step, you can remove Teamcenter client communication system (TCCS)configurations.

A TCCS configuration contains information on how TCCS connects to the server. ATCCS configuration can be either shared or private. Whether a TCCS configurationis shared or private is determined at installation time. Shared configurations can becreated only by administrators.

Select the Shared or Private check boxes to remove shared or private TCCSconfigurations.

Note A shared TCCS configuration is located in the%ALLUSERSPROFILE%/Siemens/cfg directory (Windows systems) orthe /etc/Siemens/cfg (UNIX/Linux systems). A private TCCS configurationis located in the %USERHOME% directory.

Kerberos authentication settingsIn this step, you specify settings for Kerberos authentication in Teamcenter.

Kerberos is a network authentication protocol that uses a system of tickets to allownodes communicating over nonsecure networks to securely verify identities of eachside. Using a client-server model, it provides mutual authentication: the user andthe server verify each other’s identities.

Value Description

Support Kerberos authentication Specifies you want to use Kerberosauthentication for Teamcenter logon.

Use default settings Specifies you want to use the default Kerberosconfiguration file on the host.

Use this Krb5 file Specifies you want to use a custom Kerberosconfiguration file. If you Select this option,enter the path to the custom Kerberosconfiguration file.



Value Description

Always prompt for user ID Specifies you want to always prompt for aKerberos user name.

If you want to enable zero sign-on functionalityon Windows hosts, clear this checkbox. Zerosign-on allows Windows users to launch aTeamcenter client without being prompted tolog on to Teamcenter.

Note Zero sign-on functionality requiresyou configure Security Services inapplet-free mode in the SecurityServices panel.

For more information about SecurityServices installation, see the SecurityServices Installation/Customizationguide.

Secure socket layer (SSL) settingsIn this step, you specify settings for secure socket layer (SSL) authentication inTeamcenter.

Value Description

Use Internet Explorer CertificateStore (Recommended)

Specifies you want to use certificates stored inMicrosoft Internet Explorer.

This option is available only on Windowshosts.

Disable SSL Specifies you want to disable SSLauthentication.

Configure Certificate StoreManually

Specifies you want to manually configure thecertificate store for Teamcenter.

Configure trust store Contains options for manually configuring thecertificate store for Teamcenter.

Use trust store Specifies you want to use a trust store. If youselect this option, enter the path to file thatcontains the trust store you want to use.

Accept untrustedcertificates

Specifies you want to accept untrustedcertificates.

Configure key store Contains options for configuring the keystorefor Teamcenter.

Use key store Specifies you want to use a keystore.

If you choose this option, enter the path tothe keystore. Also, specify the file type. Thedefault file type is JKS.



For more information about configuring SSL for Teamcenter, see the SecurityServices Installation/Customization guide.


Chapter

9 Web tier

About Web tier installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

J2EE Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Setting default Web server preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Installing the J2EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2Server manager TreeCache configuration . . . . . . . . . . . . . . . . . . . . . . . . 9-4

.NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Internet Information Services (IIS) settings . . . . . . . . . . . . . . . . . . . . . . . 9-6.NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8.NET Web tier client integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10Installing the .NET server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11.NET server manager performance tuning . . . . . . . . . . . . . . . . . . . . . . . . 9-12ASP .NET state service configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13


Chapter

9 Web tier

About Web tier installation in TEMThe following TEM help topics describe panels that install the server managers forthe J2EE Web tier and the .NET Web tier, and enable the Web tier to communicatewith the Teamcenter server.

If you use the J2EE Web tier, you can build Teamcenter J2EE Web applicationsusing the Web Application Manager.

For more information about using installing the Teamcenter Web tier, see theappropriate server installation guide (for Windows or UNIX/Linux).

J2EE Web tier

Setting default Web server preferences

In this step, you optionally define a Web tier application server that enables richclient users to generate and view bookmark files that interact with Teamcenterlifecycle visualization and enables thin client users to receive Teamcenternotifications.

Requirements:

A Teamcenter Web tier application must be generated and deployed.

References:

For information about configuring the Web tier application, see the Installationon Windows Servers Guide and the Installation on UNIX and Linux ServersGuide in the Teamcenter help library.

Value Description

Set the preferences Specifies whether to set the specified preferences in theTeamcenter configuration.

Host Specifies the name of the server where the Web tierapplication is deployed.

Port Specifies the number of the port for the Web tier application.

Application Name Specifies the name of the Web tier application.

The default name of the Web tier application is tc.


Chapter 9 Web tier

Note • If you use SSL, make sure you include the fully qualified host name inthe URL to the Web application.

• Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses,use host names in URIs wherever possible so the domain name system(DNS) can determine which IP address should be used.

If you must use IP addresses and your network uses IPv6 addresses,enclose the literal IPv6 address in square brackets, for example:


Installing the J2EE server manager

In this step, you install the server manager that manages a pool of Teamcenterserver processes running in the enterprise tier. The server manager starts andtimes out the server processes.

Note This option applies only when you are deploying the four-tier architecture.

For small deployments, install the server manager on the host running theWeb tier application in a Java 2 Enterprise Edition (J2EE) application server.

For larger deployments, you can install the server manager on multiplehosts. In this case, the pool of server processes is distributed as subpoolsacross the hosts, with a server manager for each subpool.

References:

• For an overview of the four-tier architecture components and instructions forinstalling and deploying the Web tier application, see the Installation on UNIXand Linux Servers Guide and the Installation on Windows Servers Guide.

• For information about configuring and administering the server manager, seethe Preferences and Environment Variables Reference.

These documents are available in the Teamcenter help library.

Note Record each value you set for the server manager: for some values, you mustprovide the identical value when configuring the Web tier application; forother values, you must coordinate the values in the Web tier application.

Value DescriptionPool ID Specifies a unique ID for this pool of server processes.


Web tier

Value DescriptionJMX HTTP Adaptor Port Specifies the number of the port running the Java

Management Extension (JMX) HTTP adaptor.

The JMX HTTP adaptor enables viewing the statusof the server pool and dynamically altering the poolconfiguration values.

Tip Record this port number. Administratorsrequire the port number to access the adaptorat a URL (composed of the server manager hostname and this port number).

Server Host Specifies the logical host name of the server managerhost. This value allows you to control which IP addressis used when connecting to Teamcenter servers.

If your server manager host has only one IP address,leave this field blank. If the server host has multipleIP addresses and you want the server manager to usea specific address when connecting to Teamcenterservers, type the address or the logical host name ofthe server manager host.

The value you enter is written to the SERVER_HOSTparameter in the serverPool.properties file.

Max Servers in Sub-Pool Specifies the maximum number of Teamcenter serverprocesses allowed to run in this pool (for a single-hostconfiguration) or in this subpool (for a multihostconfiguration).

Min Warm Servers Specifies the minimum number of Teamcenter serverprocesses in this pool that are started but not loggedonto.

Tip If necessary to maintain the minimum numberof warm servers, while not exceeding themaximum number of server processes, theserver manager times out servers in use.

Server Target Specifies the target number of server processes to beavailable in this pool or subpool during specified times.

Specify these values as time and integer pairsseparated by commas. For example:

0700 3, 1700 2

This value sets the target number of server processesas 3 between 7 a.m. and 5 p.m. and as 2 between 5p.m. and 7 a.m.

• If the number of server processes is below thespecified target, warm servers are added to reachthis number. In this case, the number of warmservers exceeds the minimum.


Chapter 9 Web tier

Value Description

• If the number of server processes exceeds thespecified target, only the minimum number ofwarm servers is maintained and servers areterminated as they time out.

logons per Minute Specifies the number of logons the server managerallows per minute for this pool or subpool.

Tip Setting this value to 0 allows an unlimitednumber of logons.

Startup Mode Specifies how you want to start the J2EE servermanager

Service/Daemon Specifies you want to run the server manager as aservice (a system service on Windows or a daemon onUNIX/Linux).

Command Line Specifies you want to run the server manager manuallyfrom a command line.

Note • The server manager log file contains status messages recorded duringserver manager startup. See the information in this file if you encounterWeb tier connection problems.

• On UNIX/Linux systems, if you install the server manager using anaccount without root privileges, a user with root privileges must run theroot postinstallation tasks script to register the server manager daemon.

After you complete server manager installation in TEM, locate and runthe following script:

TC_ROOT/install/root_post_tasks_id.ksh

Server manager TreeCache configuration

In this step, you set the initial configuration values for the pool of Teamcenterserver processes.

Note This step applies only when you are deploying the four-tier architecture.

Reference:

For more information about configuring and administering the server manager,see the System Administration Guide.


Web tier

Value Description

TreeCache Cluster Name Specifies the name of a cluster of components accessinga shared global server pool. This name must be uniquefor this database and corporate server.

Tip You must supply this same name for theTreeCache Cluster Name parameter whenconfiguring the Web tier application.

Multicast Mode Specifies that the communication protocol modebetween TreeCache peers is multicast.

Tip If you choose Multicast Mode, you must enterMcast for the TreeCache Mode parameterwhen configuring the Web tier application.

TreeCache ClusterPort

Specifies the port used for multicast communicationbetween the application server and the server manager.

Tip This port number must match the port numberspecified for the TreeCache Cluster Portparameter in the Web tier application.

TCP Mode Specifies that the communication protocol modebetween TreeCache peers is TCP.

Tip If you choose TCP Mode, you must type TCPfor the TreeCache Mode parameter whenconfiguring the Web tier application.

Local Service Port Specifies the TCP port at which this TreeCache clustermember provides the TreeCache service.

If you install the Web tier application on the same hostas the server manager, the local service port for the Webtier application must be different from the local serviceport for the server manager.

ConnectionTimeout

Specifies the maximum time in milliseconds that aTreeCache cluster member waits for peer responses toTCP pings.

Tip The larger the value you specify, the moreslowly the first server manager starts.

Typically, you supply this same value forthe Connection Timeout parameter whenconfiguring the Web tier application.


Chapter 9 Web tier

Value Description

TreeCache Peers Specifies a list of addresses (host name and port numberpairs) to ping for peer members of the TreeCache clusterin TCP communication mode. It is a comma-separatedlist of the form host1[port1],host2[port2],.. Donot use the form host1:port1, ... because the coloncharacter (:) is not permitted.

For each host/port pair, this cluster member pings theport you specify.

Once established, peers exchange data regardingavailable server pools. This cluster member pings eachhost/port pair in the list. To be found, a peer must havea matching service port. (See Local Service Port in thistable.)

• As a minimum, specify the service port for all Java2 Enterprise Edition (J2EE) application serverhosts and server manager hosts you want thisTeamcenter server to communicate with.

• For each host, you can include more than onehost/port pair in the list.

It is not necessary to include all members of thecluster in this list. For example, you may includeonly a subset of the server managers and none ofthe application servers. In this case, the clusterconnects only when one or more of the designatedmanagers is running. This technique reducespinging and thereby improves performance.

For small configurations, all members should beincluded in the peers list. For larger configurations,it is recommended that the number of pinged portsbe limited to no more than six. All members shouldping at least the same subset of primary servermanagers so that TreeCaches connect and data isshared.

.NET Web tier

Internet Information Services (IIS) settings

In this step, you provide Internet Information Services (IIS) settings for TeamcenterWeb tier deployment.

Value Description

IIS Web Configuration


Web tier

Value DescriptionUse Existing WebSite

Specifies that you want to use an existing Web site.You must select the existing Web site from the list.Teamcenter creates the virtual directory for theTeamcenter application in the specified Web site in IIS.The Teamcenter application is thus hosted in the specifiedWeb site.

This option is selected by default.

Create New Web Site (Optional) Specifies that you want to create a new Website for the Teamcenter Web tier deployment. You mustspecify values for Web Site Name, Web Site Port, andWeb Site Root Path.

Web Site Name (Optional) Specifies the name of the new Web site in IIS.This value is required only if you select the Create NewWeb Site option.

Web Site Port (Optional) Specifies the port number of the new Web Sitein IIS. This port must be available and unassigned. Thisvalue is required only if you select the Create New WebSite option.

Web Site Root Path (Optional) Specifies the root of Web content subdirectoriesfor the new Web site. This value is required only if youselect the Create New Web Site option.

IIS Web Application Pool ConfigurationUse ExistingApplication Pool

Specifies whether to use an existing application pool fromthe list provided. An application pool is a set of one ormore applications assigned to an IIS worker process. TheTeamcenter .NET Web tier is an ASP.NET 2.0 application,so the application pool can only host other ASP.NET 2.0applications (not other versions of ASP.NET, such as 1.1).Keep this in mind if you intend to have this applicationpool host other applications. A general recommendationis to use a dedicated (stand-alone) application pool forTeamcenter Web tier deployment.

This option is selected by default.

Create NewApplication Pool

(Optional) Specifies whether to create a new applicationpool. You must provide a value for Application PoolName.

Application PoolName

(Optional) Specifies the name for the IIS application pool.This value is required only if you select the Create NewApplication Pool option.

IIS Virtual Directory ConfigurationVirtual DirectoryName

Specifies the IIS virtual directory name for TeamcenterWeb tier deployment. The default value is tc. Web URLsfor Teamcenter four-tier deployments are based on thisvalue. For example, if you specify the default value as tc,the URLs are of the form: http://host:port/tc/...


Chapter 9 Web tier

Note Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, usehost names in URLs wherever possible so the domain name system (DNS)can determine which IP address should be used.



.NET Web tierIn this step, you set the initial configuration values for installing the .NET Web tierin a four-tier Teamcenter deployment.


Value DescriptionWeb Tier Language Specifies the same locale that is specified for Teamcenter

server. This locale is used for localization of messagescoming from Web tier. The default Web tier language isEnglish. Choose one of the following languages:

Language Value

Chinese (Simplified) zh_CNChinese (Traditional) zh_TWCzech cs_CZEnglish en_USFrench fr_FRGerman de_DEHebrew en_USItalian it_ITJapanese ja_JPKorean ko_KRPolish pl_PLPortuguese (Brazilian) pt_BRRussian ru_RUSpanish es_ES

Session Time Out Specifies the Web tier session time out in minutes. Thedefault value is 20. If a user is inactive for more than thetime-out value, the user’s web tier session expires.

In the thin client, if a session expires, the user mustauthenticate again to continue working.

In the rich client, client credentials are cached. After asession time-out, the rich client automatically logs onsilently and allows the user to continue working.


Web tier

Value DescriptionResponseCompressionThreshold

Specifies the threshold in number of bytes beyond whichthe Web server should compress responses sent back tothe client. Typically, compressing smaller responses doesnot yield significant compression, so all responses equalto or less than the value specified are sent to the clientuncompressed.

Note Setting this value to 0 causes the server tocompress every response sent to the client. Thedefault value is 500 bytes.

Client Cache Time Out Specifies the time, in minutes, to retain the client cache.Cached files are deleted after the specified interval.

TcSS Enabled (Optional) Specifies whether to enable Security Services.If Security Services is enabled, you must provide validvalues for TcSS Application ID and TcSS Service URL.The default value is false.

TcSS Application ID (Optional) Specifies the application ID of your Teamcenterinstallation as configured in the Security Servicesinstallation.

TcSS Login ServiceURL

(Optional) Specifies the URL to the Security ServicesLogin Service Web application.

Critical System EventsNotification

(Optional) Specifies whether to notify the administratorof critical system events. If selected, you must providevalues for Administrator Email and SMTP Host. Ifselected, certain error level log messages are e-mailedto the specified e-mail address. These error messagesusually signify a serious operational or functionalproblem in the deployment and typically require manualintervention to be correct. These messages are also loggedon the Windows event log. If you do not specify e-mailnotification, you can view messages in the Windows eventlog.

Administrator Email (Optional) Specifies the administrator’s e-mail address forcritical system events notification.

SMTP Host (Optional) Specifies the SMTP (Simple Mail TransferProtocol) Host to send e-mail for critical system eventsnotification.


Chapter 9 Web tier

Value Description

Cluster Deployment (Optional) Select this option if you have a clustered WebTier deployment using the ASP.NET state service as theout-of-process state server. If selected, you must specifyvalues for ASP.NET State Service Host and ASP.NETState Service Port. Select this option only if you use aWeb Farm (Clustered Web Tier) deployment and you wantto use the ASP.NET State Service as your out-of-processstate server. If you plan to use any other out-of-processstate server, such as SQL*Server, do not select this option.The Teamcenter installer supports only the ASP.NETState Service as the out-of-process state server; otherstate servers may be configured manually after the initialTeamcenter installation is complete.

State Server Host (Optional) Specifies the ASP.NET state service host namefor session state management.

State Server Port (Optional) Specifies the ASP.NET state service portnumber for session state management.

Legacy URL Support (Optional) Select this option if you want to provide basicURL redirection to support legacy URLs from Teamcenterengineering process management 2005 or earlier toTeamcenter 10.1.

This option automatically redirects legacy URLs toTeamcenter 10.1 URLs with no informational messages.

Teamcenter 10.1 changes part of the client URL from/cgi-bin/iman to /file-name/webclient. Replace file-namewith the name of the Web tier application.

Server ManagerPeers

Specifies each server manager host and port for yourTeamcenter installation. At least one server managermust be configured for a working deployment, so youmust specify at least one host and value. Host specifiesthe machine name where the server manager is running,and Port specifies the port on which the server managerlistens. This port must match the port you specify duringthe corresponding server manager installation.




.NET Web tier client integration

In this step, you set the optional configuration values for .NET Web tier clientintegration.


Web tier

Value Description

Session Time Out (Optional) Specifies the time, in minutes, to allow aninactive client session to remain open.

Use HybridAuthentication

(Optional) Specified whether to use hybrid authenticationfor Microsoft Applications. If this is set to false, users mustenter a name and password in Microsoft applications evenif they have logged on through Teamcenter applications.Set this value to true to avoid the extra authenticationchallenges from Microsoft applications. The default valueis true.

Use AIWS Specifies whether to use the Application Interface WebService (AIWS) for integration with Remote Workflow.

User Name (Optional) Specifies the user name for logging on toTeamcenter on behalf of the remote Teamcenter application.The default value is set to infodba.

User Password (Optional) Specifies the user password for logging on toTeamcenter on behalf of the remote Teamcenter application.This value is encrypted.

Installing the .NET server manager

In this step, you install the .NET server manager. The server manager managesa pool of Teamcenter server processes running in the enterprise tier. The servermanager starts and times out the server processes.

Note This option applies only when you are deploying the four-tier Teamcenterarchitecture.

For small deployments, install the .NET server manager on the samemachine that hosts the IIS (Internet Information Services) Teamcenter WebTier application.

For larger deployments, you can install the .NET server manager on multiplehosts. In this case, the pool of server processes is distributed as subpoolsacross the hosts, with a server manager for each subpool.

Record each value you set for the server manager. For some values, you must providethe identical value when configuring the Web tier application; for other values, youmust coordinate the values in the Web tier application.

Value DescriptionPool ID Specifies a unique ID for this pool of server processes.

Pool Port Specifies the port number of the pool of server processes.

Specify Server Host (Optional) Select this option if you want to specify the .NETserver manager host. If you do not select this option, TEMuses the default host.


Chapter 9 Web tier

Value Description

Server Host Name (Optional) Specifies the logical host name of the servermanager host. Enter a value in this field only if the servermanager host has multiple IP addresses. Otherwise, leaveit blank.

This value allows you to control which IP address is usedwhen connecting to Teamcenter servers. The value enteredin this field is written to the PoolConfiguration.xml file.

Critical SystemEvents Notification

(Optional) Select this option if the administrator shouldbe notified of critical system events. If you select thisoption, you must enter values for Administrator Email andSMTP Host. If selected, certain error level log messagesare e-mailed to the specified e-mail address. These errormessages usually signify a serious operational/functionalproblem in the deployment, which typically needs manualintervention to be corrected. These messages are also loggedon the Windows event log and log files independent of thisselection, so if you choose to not receive e-mail notification,you can check the log messages there.

Administrator Email (Optional) Specifies the administrator’s e-mail address forcritical system events notification.

SMTP Host (Optional) Specifies the SMTP (Simple Mail TransferProtocol) Host to send e-mail for critical system eventsnotification.

.NET server manager performance tuning

In this step, you set the initial configuration values for the pool of Teamcenterserver processes.

Note This step applies only when you are deploying the four-tier Teamcenterarchitecture.

Value Description

Max Servers Specifies the maximum number of Teamcenter serverprocesses allowed to run in this pool (for a single-hostconfiguration) or in this subpool (for a multihostconfiguration). The total number of servers should notexceed this number.

Min Warm Servers Specifies the minimum number of Teamcenter serverprocesses in this pool that are started but not logged onto.

Note The Server Manager always tries to maintain thismany number of minimum ready (warm) servers.The Server Manager may time out servers in use, inorder to ensure that there are at least the requirednumber of minimum warm servers at all times.


Web tier

Value Description

Target Servers Specifies the target number of server processes to beavailable in this pool or subpool during specified times.

Specify these values as time and integer pairs separated bycommas. For example:

0700 3, 1700 2

This value sets the target number of server processes as 3between 7 a.m. and 5 p.m. and as 2 between 5 p.m. and7 a.m.

• If the number of server processes is below the specifiedtarget, warm servers are added to reach this number.In this case, the number of warm servers exceeds theminimum.

• If the number of server processes exceeds the specifiedtarget, only the minimum number of warm servers ismaintained and servers are terminated as they timeout.

Logons per Minute (Optional) Specifies the number of logons the servermanager allows per minute for this pool or subpool. Settingthis value to 0 allows an unlimited number of logons perminute.

Query Time Out (Optional) Specifies the maximum time in seconds allowedfor the business logic server to serve a user request. Settingthis value to 0 allows an unlimited request time.

Soft Time OutStateless

(Optional) Specifies the time-out for stateless mode serversin a busy pool in seconds. The default value is 1200.

Soft Time Out Read (Optional) Specifies the time-out for read mode servers in abusy pool in seconds. The default value is 28800.

Soft Time Out Edit (Optional) Specifies the time-out for edit mode servers in abusy pool in seconds. The default value is 28800.

Hard Time OutStateless

(Optional) Specifies the load-insensitive time-out forstateless mode servers in seconds. The default value is28800.

Hard Time Out Read (Optional) Specifies the load-insensitive time-out for readmode servers in seconds. The default value is 28800.

Hard Time Out Edit (Optional) Specifies the load-insensitive time-out for editmode servers in seconds. The default value is 28800.

ASP .NET state service configuration

In this step, you set initial configuration values for the ASP .NET state service forthe Teamcenter .NET Web tier. You can use the ASP .NET state service to configurethe .NET Web tier in clustered mode for network load balancing.



Chapter 9 Web tier

Value Description

ASP .NET StateService Host

Specifies the host on which the ASP .NET state service runs.

ASP .NET StateService Port

Specifies the port used by the ASP .NET state service.


Chapter

10 Security Services

Configuring Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Configuring Security Services for rich client . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Configuring Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2


Chapter

10 Security Services

Configuring Security ServicesIn this step, you configure Security Services for Teamcenter. These services eliminateprompts for logon credentials when users launch multiple Teamcenter productswithin a single user session. Authentication is performed by an external identityservice provider, such as lightweight directory access protocol (LDAP), instead ofthe Teamcenter product.

Note This option applies only when you are deploying the two-tier architecture.

When you deploy the four-tier architecture, you configure Security Servicesin the Web tier application. For information, see the Installation on UNIXand Linux Servers Guide or the Installation on Windows Servers Guide.

Prerequisite:

Installation and configuration of Security Services.

For information, see the Security Services Installation/Customization guide inthe Teamcenter help library.

Value Description

Enable SecurityServices

Select this check box to enable Security Services for thisTeamcenter configuration.

Login URL Specifies the complete URL of the Security Services LoginService Web application.

Service URL Specifies the complete URL of the Security Services IdentityService Web application.

Application ID Specifies the application ID for this instance of Teamcenterin the Security Services application registry.





Chapter 10 Security Services

Configuring Security Services for rich clientIn this step, you provide information required to enable Security Services in therich client.

Note This option applies only to the two-tier rich client architecture.

When you deploy the four-tier architecture, you configure Security Servicesin the Web tier application.

For information, see the Installation on UNIX and Linux Servers Guide orthe Installation on Windows Servers Guide.

Prerequisite:

Installation and configuration of Security Services.

For information, see the Security Services Installation/Customization guide inthe Teamcenter help library.

Value DescriptionLogin URL Specifies the complete URL of the Security Services Login

Service Web application.

Application ID Specifies the application ID for this instance of the richclient in the Security Services application registry.

An application is represented within Security Services asa unique text string known as an application ID. You mustdefine an application ID for each Teamcenter application inyour Security Services domain. You use these applicationIDs when completing the Application Registry table.




Configuring Security ServicesIn this step, you configure Security Services for use with Teamcenter.

Value DescriptionLogin URL Specifies the complete URL of the Security

Services Login Service Web application.

If you use Security Services in applet-free mode,type the URL using the following format:

http://host:port/login-service-name/tccs


Security Services

Value DescriptionApplication ID Specifies the application ID for this instance of

Teamcenter in the Security Services applicationregistry.

For more information about Security Services installation, see the Security ServicesInstallation/Customization guide.





Chapter

11 Dispatcher

About Dispatcher installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Installing Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Installing Dispatcher components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Dispatcher settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Dispatcher translation service settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Dispatcher translation service (additional settings) . . . . . . . . . . . . . . . . . . . . 11-5

Selecting translators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Translator settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6


Chapter

11 Dispatcher

About Dispatcher installation in TEMThe following TEM help topics describe panels that allow you to install andconfigure the optional Dispatcher feature for Teamcenter. For more informationabout installing Dispatcher, see Getting Started with Dispatcher (TranslationManagement).

For information about translators for the Dispatcher server, see the DispatcherServer Translators Reference Guide.

Installing DispatcherIn this step, you install the optional Dispatcher feature, an integration of theDispatcher Server and Teamcenter. Dispatcher enables Teamcenter users totranslate CAD data files that are managed by Teamcenter to JT or CGM file formatfor viewing in either Engineering Process Management Visualization or Teamcenterlifecycle visualization.

Prerequisites:

• Install and configure the Dispatcher Server.

• Install, configure, and verify translators.

Postinstallation task:

Manually create an Access Manager rule that permits the Dispatcher proxy userto update attributes of a TranslationRequest object. If you fail to create thisrule, the Dispatcher service reports errors.

Condition = Has ClassValue = DispatcherRequestACL Name = DispatcherRequestACE Type of Accessor = UserACE ID of Accessor = DC-proxy-user-idACE Privilege = WriteACE Privilege Value = GrantACE Privilege = DeleteACE Privilege Value = Grant

References:

• For information about Dispatcher Server, see Getting Started with Dispatcher(Translation Management).

• For information about starting and stopping Dispatcher, see the DispatcherServer Installation Guide.


Chapter 11 Dispatcher

These documents are available in the Teamcenter help library.

Value Description

Translation ServiceProxy User Name

Specifies the name of the Teamcenter user that logs in forDispatcher services (the ETS proxy user).

Tip Siemens PLM Software recommends that theDispatcher proxy user not be the same as theTeamcenter user as the proxy user requires aunique access rule.

Translation ServiceProxy Password

Specifies the password for the Dispatcher proxy user.

TSTK SchedulerHost

Specifies the name of the host on which the DispatcherServer scheduler is deployed.

This host name is added to the translation server URL:

rmi://host-name:port-number

TSTK SchedulerPort

Specifies the number of the port used by the DispatcherServer scheduler.

This port number is added to the translation server URL:

rmi://host-name:port-number

NX UG ManagerSupport

Specifies whether this installation of Dispatcher supportsTeamcenter Integration for NX or NX Integration.

Service RegistryHostname

Specifies the name of the host where the Dispatcher serviceregistry runs.

When deploying the two-tier architecture, this can be thelocal host.

Service RegistryPort

Specifies the number of the port used by the Dispatcherservice registry.

Translation ServiceTCServer Hostname

Specifies the name of the host on which the Dispatcherservice tcserver runs.

Extractor Port Specifies the number of the port used by the Dispatcherextractor service.

This port is used to control this Dispatcher service.

Scheduler Port Specifies the number of the port used by the Dispatcherscheduler service.


Loader Port Specifies the number of the port used by the Dispatcherloader service.



Dispatcher

Value Description

Specify DatasetOwner

Specifies the owner of the datasets submitted fortranslation. The default value is CAD.

Installing Dispatcher componentsIn this step, you specify settings for Dispatcher installation.

Value DescriptionDispatcher Rootdirectory

Specifies the root directory of the Dispatcher installation.

Siemens PLM Software recommends specifying theDispatcher root directory as close to the Teamcenter rootdirectory as possible.

SCHEDULERInstall Scheduler Select this check box to install the Dispatcher scheduler.

Scheduler Port Specifies the port for the translation scheduler.

MODULEInstall Module Select this check box to install the Dispatcher module.

Staging Directory Specifies the default staging directory for translations.

Note If you are installing the module and the scheduleron the same machine, the Module Port box isdisabled.

Module Port Specifies the port for the translation module.

ADMIN CLIENTInstall Admin Client Select this option to install the Dispatcher administrative

client.

Dispatcher settingsIn this step, you specify installation settings for Dispatcher.



Value DescriptionEnter Logging Level Enter the level of messages you want Dispatcher to

record. Select one of the following levels:

• OFF• FATAL• ERROR• WARN• INFO• DEBUG• TRACE• DBCHG• ALL

The default level is INFO.Dispatcher ServicesLog Directory

Specifies a directory for the Dispatcher service log.

Install Documentation Specifies whether to install documentation (JavaDoc)for the Translation Service. If you select this check box,specify a location in which to install the documentationin the Documentation Install Directory box.

Starting DispatcherServices

Select this check box to automatically start Dispatcherservices.

Start DispatcherServices asWindows Service

Specifies you want to run Dispatcher services asWindows services. These services can be managedthrough the Services dialog box in the Windows ControlPanel.

Start DispatcherServices at console

Specifies you want to launch Dispatcher services in aconsole window.

Dispatcher translation service settingsIn this step, you specify settings for the translation service.

Value Description

Dispatcher ServerConnection Type

Specifies the mode the Translation Service uses forcommunication between Teamcenter and the Dispatchercomponents.

• ClickWebServer if you send translation requests over afirewall.

• Click RMI for communicating using the RMI mode.

Note The RMI mode of communication is faster thanthe WebServer mode.

Dispatcher ServerHostname

Specifies the name of the server where the translationserver will be hosted.


Dispatcher

Value Description

Dispatcher ServerPort

Specifies the port to be used for the translation service. Thedefault value is 2001.

Make sure that the port you type is not used by any otherprocess.

Staging Directory Specifies the location to be used as the staging directoryfor the translation service.

Dispatcher ClientProxy User Name

Specifies the name of the proxy user who will usetranslation services.

Dispatcher ClientProxy Password

Specifies the password for the proxy user. Enter thepassword again in the Translation Service Proxy ConfirmPassword box.

Polling interval inseconds

Specifies the time, in seconds, that the translation servicewaits before querying for translation requests.

Do you want to storeJT files in SourceVolume?

Specifies whether to store visualization files in theassociated visualization dataset. Choose Yes or No.

Dispatcher translation service (additional settings)In this step, you specify additional settings for the translation service.

Value DescriptionEnter Logging Level Enter the level of messages you want Dispatcher to

record. Select one of the following levels:

• OFF• FATAL• ERROR• WARN• INFO• DEBUG• TRACE• DBCHG• ALL

The default level is INFO.Advanced Settings

Do you want toupdate existingvisualization data?

Specifies whether the Translation Service should updateexisting visualization data for subsequent translations ofthe same version. Choose Yes or No.

Deletion ofsuccessfultranslation inminutes

Specifies the number of minutes the translation servicewaits before querying and deleting successful translationrequest objects.

If the this value is 0, no translation request cleanup isdone.



Value DescriptionThreshold timein minutesfor successfultranslation deletion

Specifies the number of minutes to allow after the lastmodification of a successful translation request beforethe request can be deleted.

Deletion ofunsuccessfultranslation inminutes

Specifies the number of minutes the translationservice waits before querying and deleting unsuccessfultranslation request objects.

If the this value is 0, no translation request cleanup isdone.

Threshold timein minutes forunsuccessfultranslation deletion

Specifies the number of minutes to allow after the lastmodification of an unsuccessful translation requestbefore the request can be deleted.

Selecting translatorsIn this step, you select translators to install for the Dispatcher server.

For information about translators, see the Dispatcher Server Translators ReferenceGuide.

Translator settingsIn this step, you specify settings for translators used by the Dispatcher server. Thesettings required vary by the applications associated with each translator. For moreinformation about translators, see the Dispatcher Server Installation Guide.


Chapter

12 Teamcenter reporting andanalytics

About Reporting and Analytics installation in TEM . . . . . . . . . . . . . . . . . . . . 12-1

Reporting and Analytics install options and general settings . . . . . . . . . . . . . 12-1

Reporting and Analytics license server settings . . . . . . . . . . . . . . . . . . . . . . . 12-2

Reporting and Analytics WAR file settings . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Reporting and Analytics license settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Reporting and Analytics metadata settings . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Reporting and Analytics database selection . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Reporting and Analytics WAR and metadata settings . . . . . . . . . . . . . . . . . . 12-6

Reporting and Analytics authentication settings . . . . . . . . . . . . . . . . . . . . . . 12-7

Reporting and Analytics WAR SMTP settings . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Reporting and Analytics metadata SSO settings . . . . . . . . . . . . . . . . . . . . . . 12-8

Reporting and Analytics WAR SSO settings . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Reporting and Analytics Security Services configuration . . . . . . . . . . . . . . . . 12-8

Reporting and Analytics Web parts and services . . . . . . . . . . . . . . . . . . . . . . 12-9

Reporting and Analytics snapshot migration . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

Upgrading a cloned environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10


Chapter

12 Teamcenter reporting andanalytics

About Reporting and Analytics installation in TEMYou install the Teamcenter integration to Teamcenter reporting and analytics usingTEM. Reporting and Analytics requires additional steps to complete configuration.

For more information, see the appropriate server installation guide (for Windows orUNIX/Linux) and also the Teamcenter reporting and analytics Deployment Guide inthe Reporting and Analytics software distribution image.

Reporting and Analytics install options and general settingsIn this step, you configure installation options for the Reporting and Analyticsintegration.

Reporting and Analytics is a stand-alone reporting application. Reporting andAnalytics adds a Reporting and Analytics Reports folder to Report Builder, whichcontains reports created with Reporting and Analytics. You can view, edit, setpermissions and delete Reporting and Analytics reports from Report Builder.Viewing reports launches Reporting and Analytics. Reporting and Analytics alsoadds menu commands to My Teamcenter and Teamcenter thin client to generateReporting and Analytics reports.

Value Description

Create licenseserver

Specifies whether you want to install a Reporting andAnalytics license server.

Create WAR file Specifies whether to generate a WAR file for the Reportingand Analytics Web application.

Create metadata Specifies whether to populate the Reporting and Analyticsmetadata database. Select this only during the firstinstallation of Reporting and Analytics. If you areupgrading from a previous version of Reporting andAnalytics or adding additional hosts, do not select thisoption.

Secure Connection Specifies whether to use a secure connection (HTTPS) whenconnecting to the Reporting and Analytics license server.


Chapter 12 Teamcenter reporting and analytics

Note Reporting and Analytics requires additional steps to complete configuration.For more information, see the Teamcenter reporting and analyticsDeployment Guide in the Reporting and Analytics software distributionimage.

Reporting and Analytics license server settingsIn this step, you specify settings for the Reporting and Analytics license server.

Value DescriptionLicense File Specifies the location of the Reporting and Analytics license

file (license.dat).LicenseAuthenticationTimeout

Specifies the interval in seconds to wait for a response fromthe Reporting and Analytics license server.

Keystore SettingsOverrideKeystore DefaultInput

Specifies whether to allow the license server to use itsdefault keystore and password.

Keystore Path Specifies the path to the keystore for Reporting andAnalytics licenses.

Specifies the path to the keystore file that contains thepublic and private key used for encryption and decryptionin HTTPS communication.

KeystorePassword

Specifies the password to be used for encryption anddecryption in HTTPS communication.

Note • For information about starting the Reporting and Analytics licenseserver, see the Teamcenter’s reporting and analytics Deployment Guidein the Reporting and Analytics software distribution image.

• Reporting and Analytics requires additional steps to completeconfiguration.

For more information, see the Teamcenter reporting and analyticsDeployment Guide in the Reporting and Analytics software distributionimage.

Reporting and Analytics WAR file settingsIn this step, you specify the Web application context, host, and port for the Reportingand Analytics integration Web application.

Value DescriptionWeb ApplicationContext

Specifies the application name for the Reporting andAnalytics Web application. The default value is eQube.This name is included in the URL for the Web application:


Teamcenter reporting and analytics

Value DescriptionWeb ApplicationServer Name

Specifies the name of the server where the Reporting andAnalytics Web application is deployed.

Web ApplicationServer Port

Specifies the port number used by the Reporting andAnalytics Web application.

The complete URL to the Reporting and Analytics Web application is of the followingform:

http://host-name:port/context-name/rest-of-path

For example, a Web application named TcRA running on a host named MyHostusing port 7001 uses the following URL:

http://MyHost:7001/TcRA/BuildNPlay

Note Reporting and Analytics requires additional steps to complete configuration.


Reporting and Analytics license settingsIn this step, you configure the local host to provide license authorizations for theReporting and Analytics integration.

Reporting and Analytics is a stand-alone reporting application. Reporting andAnalytics adds a TcRA Reports folder to Report Builder, which contains reportscreated with Reporting and Analytics. You can view, edit, set permissions and deleteReporting and Analytics reports from Report Builder. Viewing reports launchesReporting and Analytics. Reporting and Analytics also adds menu commands to MyTeamcenter and Teamcenter thin client to generate Reporting and Analytics reports.

Value Description

License Server Host Specifies the host on which the Reporting and Analyticslicense server runs.

License Server Port Specifies the port used by the Reporting and Analyticslicense server.

Note • For information about starting the Reporting and Analytics licenseserver, see the Teamcenter’s reporting and analytics Deployment Guidein the Reporting and Analytics software distribution image.





Reporting and Analytics metadata settingsIn this step, you specify metadata settings for the Reporting and Analyticsintegration.

This panel is displayed only if you select Create metadata in the Reporting andAnalytics install options and general settings panel.

Value DescriptionTeamcenter 4–tier URL Specifies the URL to the Teamcenter four-tier rich client

(http://host:port/context-root).Teamcenter User Specifies the user name for the Teamcenter user who

administers Reporting and Analytics.

Teamcenter Password Specifies the password for the Teamcenter user whoadministers Reporting and Analytics.

Teamcenter GroupName

Specifies the group name for the Teamcenter user whoadministers Reporting and Analytics.

Teamcenter Role Name Specifies the role name for the Teamcenter user whoadministers Reporting and Analytics.

Connection ID Specifies a connection ID of one or more alphanumericcharacters to use when connecting to the Reporting andAnalytics server.

Connection Name Specifies a name for the Reporting and Analytics, forexample, TcConnection.

Remote Plugins URL Specifies the URL to the remote plug-ins directory.

Note • Reporting and Analytics requires additional steps to completeconfiguration.


• Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses,use host names in URLs wherever possible so the domain name system(DNS) can determine which IP address should be used.



Reporting and Analytics database selectionIn this step, you configure database settings for the Reporting and Analyticsintegration.

Reporting and Analytics is a stand-alone reporting application. Reporting andAnalytics adds a Reporting and Analytics Reports folder to Report Builder, whichcontains reports created with Reporting and Analytics. You can view, edit, set



permissions, and delete Reporting and Analytics reports from Report Builder.Viewing reports launches Reporting and Analytics. Reporting and Analytics alsoadds menu commands to My Teamcenter and the Teamcenter thin client to generateReporting and Analytics reports.

Prerequisites:

• A database server must be installed. Teamcenter supports Oracle, MS SQLServer, and IBM DB2 databases.

• A database instance must exist, either a specific instance configured forTeamcenter or a multipurpose instance to be configured in this step.

• A database user for Reporting and Analytics must be configured on the databaseserver.

References:

For information about installing a database server and configuring databasesfor use with Teamcenter, see the Installation on UNIX and Linux Servers Guideand the Installation on Windows Servers Guide available in the Teamcenterhelp library.

In the Database Engine box, select the database engine you use (Oracle or MicrosoftSQL Server 2005).

Enter the following database configuration values, depending on the databaseengine you select:


Value Description

Database Server Specifies the name of the host on which Oracle Server runs.

This host must exist, and Oracle Server must be installed.


The service name was determined when the Oracle serverwas installed.

Port Specifies the number of the port on which Oracle Serverlistens.

The port number was determined when Oracle Server wasinstalled.

Database User Specifies the Reporting and Analytics database user name.The database user must exist and be configured for usewith Teamcenter.

Database Password Specifies the password for Reporting and Analytics databaseuser.




Value Description

Database Server Specifies the name of the host on which MS SQL Serverruns.

This host must exist, and MS SQL Server must beinstalled.

Choose one of the following methods to connect to the database:Named Instance If you connect to Microsoft SQL Server using a named

instance, select this option and enter the instance nameyou defined when you installed MS SQL Server.

Port If you connect to Microsoft SQL Server using a specificport, select this option and enter the port number youspecified when you installed MS SQL Server.

Login Name Specifies the Reporting and Analytics database username. The database user must exist and be configured foruse with Teamcenter.

Login Password Specifies the password for the Reporting and Analyticsdatabase user.

Database Name Specifies the name of the MS SQL Server database.

The database name was assigned when database wascreated.



Reporting and Analytics WAR and metadata settingsIn this step, you specify WAR file and metadata settings for the Reporting andAnalytics integration.

Value Description

Metadata Owner Specifies the user name for the owner of Reporting andAnalytics metadata. By default, this is the databaseuser name you specified in the Reporting and AnalyticsDatabase Selection panel.

Web ApplicationServer

Specifies the vendor of the Web application server on whichyou deploy Reporting and Analytics.


For more information, see the Teamcenter Reporting and AnalyticsDeployment Guide in the Reporting and Analytics software distributionimage.



Reporting and Analytics authentication settingsIn this step, you specify the authentication method and related settings for theReporting and Analytics integration.

Value DescriptionAuthentication Type

eQube Authentication Specifies eQube authentication.

SSO Authentication Specifies Teamcenter Security Services authentication.

Windows (NTLM)Authentication

Specifies Windows NT LAN Manager (NTLM)authentication.

Network PropertiesDomain Controller Specifies the name of the NTLM domain controller.

Note • Selecting SSO Authentication requires that you install Teamcenter withSecurity Services enabled and configure the LDAP server before youinstall Reporting and Analytics.

For information about installing Security Services, see the SecurityServices Installation/Customization guide.



Reporting and Analytics WAR SMTP settingsIn this step, you specify SMTP settings to enable users to receive e-mail generatedby Reporting and Analytics.

Value DescriptionAuthenticate Specifies whether to require authentication on the SMTP

server.

SMTP Host Specifies the host name of the SMTP server host.

User Name Specifies the user name of the Reporting and Analyticse-mail account.

Password Specifies the password for the Reporting and Analyticse-mail account.





Reporting and Analytics metadata SSO settingsIn this step, you specify metadata settings for Security Services with the Reportingand Analytics integration.

Value DescriptionTeamcenterApplicationIdentifier

Specifies the identifier of the Teamcenter Web tierapplication. Security Services uses this identifier for logonauthorizations in Reporting and Analytics.



Reporting and Analytics WAR SSO settingsIn this step, you specify WAR file settings for Reporting and Analytics with SecurityServices.

Value DescriptionTcRA ApplicationIdentifier

Specifies the application identifier for the Reporting andAnalytics Web application.

Identity Service URL Specifies URL to the Security Services Identity Service.

Login Service URL Specifies the URL to the Security Services Login Service.






Reporting and Analytics Security Services configurationIn this step, you specify configuration settings for Reporting and Analytics withSecurity Services.



Value DescriptionTeamcenterApplicationIdentifier

Specifies the application identifier for the Teamcenter Webapplication.

TcRA ApplicationIdentifier

Specifies the application identifier for the Reporting andAnalytics Web application.

Identity Service URL Specifies URL to the Security Services Identity Service.

Login Service URL Specifies the URL to the Security Services Login Service.






Reporting and Analytics Web parts and servicesIn this step, you optionally enable Web services and integration with SharePoint andTeamcenter community collaboration with Reporting and Analytics.

Value Description

Enable SOA Enable the Teamcenter service-orientedarchitecture (SOA) connector with Reportingand Analytics.

Enable Sharepoint/Tc CommunityIntegration

Select this check box to enable Reportingand Analytics integration with MicrosoftSharePoint services and Teamcentercommunity collaboration.



Reporting and Analytics snapshot migrationNo online help is available for this step.



In this step, you specify how you want to migrate Reporting and Analytics snapshotsduring upgrade.

Value DescriptionDo not run snapshot migrationthrough installer

Specifies you do not want to migrate Reportingand Analytics snapshots during upgrade.

Run snapshot migration throughinstaller

Specifies you want to migrate Reporting andAnalytics snapshots during upgrade.

Snapshot Migration Scheme Options to specify how to migrate snapshots.

SequentialSpecifies sequential migration. If you selectthis option, select Normal or Batch Execution,and type a batch size in the Batch Size box.

Parallel Specifies parallel migration. Type a threadcount in the Thread Count box.

Note For more information about these options, see the Teamcenter reportingand analytics Deployment Guide in the Reporting and Analytics softwaredistribution image.

Upgrading a cloned environmentIn this step, you provide information required to upgrade a cloned Teamcenterreporting and analytics environment.


Chapter

13 Global Services

About Global Services installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Global Services database settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Global Services preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Configuring the Global Services Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1


Chapter

13 Global Services

About Global Services installation in TEMThe following TEM help topics describe panels that allow you to install and configureGlobal Services on the Teamcenter server. After you install Global Services onthe Teamcenter server, build Global Services Web tier applications using the WebApplication Manager.

For more information about installing and configuring Global Services and GlobalServices Web tier applications, see the appropriate server installation guide (forWindows or UNIX/Linux) and also the Global Services Configuration Guide.

Global Services database settingsIn this step, you specify database settings for Global Services.

Value Description

Oracle Tablespace Specifies a tablespace name for the Global Services database.The default value is TC-database-user_globalservices,where TC-database-user is the database user you specifiedfor the Teamcenter database in the Database EngineSelection panel.

Database Directory Specifies a directory for the Global Services database.

Global Services preferencesIn this step, you specify Global Services preferences.

Value Description

Global Services URI Specifies URI Global Services uses for SOA envelopes, usingthe form http://host:port/application-name.

Configuring the Global Services AdapterIn this step, you configure the optional Global Services Adapter.

The optional Global Services Adapter connects to Teamcenter Global Services, aWeb-based application enabling clients to access information stored in virtually anytype of data source that manages site data.


Chapter 13 Global Services

Prerequisites:

Install and configure Global Services. For information, see the appropriateTeamcenter server installation guide (for Windows or UNIX/Linux).

Note Record the URL for accessing the Global Services Web service.

Value Description

Global Services Adapter ServiceGlobal ServicesAdapter ServiceURL

Specifies the URL to the Global Services Web service.


Chapter

14 Repeatable Digital Validation

Configuring an RDV database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Configuring Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Database engine selection for Repeatable Digital Validation . . . . . . . . . . . . . . 14-3


Chapter

14 Repeatable Digital Validation

Configuring an RDV databaseIn this step, you configure a separate database for use with Repeatable DigitalValidation.

Note QPL and a separate RDV database are not required if you use cachelesssearch.

A separate RDV database also allows you to tune the RDV database withoutinterfering with the Teamcenter database.

Prerequisites:

• An Oracle database server must be installed.


References:

For information about installing a database server and configuring databases foruse with Teamcenter, see the Installation on UNIX and Linux Servers Guide andthe Installation on Windows Servers Guide in the Teamcenter help library.

Value Description

Database ServerDatabase Engine Specifies the type of database server you are connecting

to, in this case, Oracle Server.

Host Specifies the name of the host on which Oracle Serverruns.



The port number was determined when Oracle Serverwas installed.

Instance (SID) Specifies the name of the service for the Oracle instance.



Chapter 14 Repeatable Digital Validation

Value DescriptionDatabase User Specifies a database user name. For the RDV database, if

you use QPL, the user name must be qpl.

• To connect to a database configured for use withTeamcenter, enter the name defined for a databaseuser when the database was configured.

• To configure a database for use with Teamcenter, enterthe name of the database user you want to create.

You must also complete the fields in the DatabaseCreation section.

Database Password Specifies a database password:

• To connect to a database configured for use withTeamcenter, enter the password defined for thedatabase user when the database was configured.

• To configure a database for use with Teamcenter, entera password for the database user you are creating.

To configure a database, you must also complete thefields in the Database Creation section.

Caution Make sure the password does not containspace characters or any of the followingcharacters:

! @ $ % ’ " : ; . < > ( ) { }

Database CreationCreate Tablespacesand User

Specifies that you want to configure a database.

The Database User and Database Password fields in theDatabase Server section must identify the user name andpassword for the database you are configuring.

Database SystemUser

Specifies the user name for the Oracle system useraccount.

Database SystemPassword

Specifies the password for the Oracle system user account.

TablespaceDirectory on Server

Specifies the full path to the tablespace directory on theOracle server host where the database tablespace filescan be created.

Enter this path in the format valid for the operatingsystem on which Oracle Server runs, rather than of thecorporate server you are installing. For example, if thecorporate server is a UNIX system, but the Oracle Serverhost is a Windows system, enter the path in Windowsformat.


Repeatable Digital Validation

Value Description

Tablespace Sizes(MB)

IDATA SizeTEMP Size

Specifies the size for each tablespace in megabytes.

The size of the tablespace depends on the amount ofdata harvested from the Teamcenter database. TheRDV database is heavily used for data warehousing (itexperiences large uploads and simple queries but fewupdates).

Configuring Repeatable Digital ValidationIn this step, you install and configure files used in conjunction with the rich clientDesignContext application.

For QPL-based DesignContext, installing Repeatable Digital Validation (RDV)services is required. For Appearance-based DesignContext, installing RDV servicesis not required.

Note RDV does not require QPL or appearances.

For more information about QPL and RDV, see Getting Started with RDV.For more information about appearances, see the Appearance ConfigurationGuide.

Value Description

SettingsQPL Port Specifies the number of the port the QPL server listens to

for requests. The default value is 14730.Search EngineJT search engine Specifies a search engine that is not specific to NX.

Tip Use this value when files used with RDV aretessellated files originally created using anysoftware (including NX).

UG search engine Specifies an NX-based search engine.

Tip Use this value when all files used with RDV arecreated in NX.

NX ApplicationLocation

Specifies the path to the location of an installed NXapplication.

Database engine selection for Repeatable Digital ValidationIn this step, you provide information required to create the database for RepeatableDigital Validation (RDV).

Note QPL and a separate RDV database are not required if you use cachelesssearch.



Prerequisites:

• A database server must be installed, either Oracle Server or MS SQL Server.


References:

For information about installing a database server and configuring databasesfor use with Teamcenter, see the Installation on UNIX and Linux Servers Guideand the Installation on Windows Servers Guide available in the Teamcenterhelp library.

In the Database Engine box, select the database engine you use (Oracle or MicrosoftSQL Server 2005).

Enter the following database configuration values, depending on the databaseengine you select:


Value Description

Database Server Specifies the name of the host on which Oracle Server runs.





The port number was determined when Oracle Server wasinstalled.

Database User Specifies a database user name. For the RDV database, ifyou use QPL, the user name must be qpl.




Repeatable Digital Validation

Value DescriptionDatabase Password Specifies a database password:




! @ $ % ’ " : ; . < > ( ) { }


Value Description

Database Server Specifies the name of the host on which MS SQL Serverruns.

This host must exist, and MS SQL Server must beinstalled.

Choose one of the following methods to connect to the database:Named Instance If you connect to Microsoft SQL Server using a named

instance, select this option and enter the instance nameyou defined when you installed MS SQL Server.

Port If you connect to Microsoft SQL Server using a specificport, select this option and enter the port number youspecified when you installed MS SQL Server.

Database User Specifies a database user name:

• To connect to an existing database configured foruse with Teamcenter, enter the name defined for adatabase user when the database was configured.

• To create and configure a new database for use withTeamcenter, enter the name of the database user youwant to create.

Database Password Specifies the password for the database user:


• To configure a new database for use with Teamcenter,enter a password for the database user you arecreating.



Value DescriptionDatabase Name Specifies the name of the MS SQL Server database.

The database name was determined when database wascreated.


Chapter

15 Rich client

About rich client installation in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Setting two-tier transport mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Two-tier Teamcenter server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Rich client settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Supplying middle-tier server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Rich client run-time home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

Rich client two-tier settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

Rich client settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

Rich client run time folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4


Chapter

15 Rich client

About rich client installation in TEMThe Teamcenter rich client is a gateway to your company’s product information. Therich client framework allows you to integrate and run Product Data Managementapplications along with various other applications, all from a common platform.These applications can be Microsoft Office applications, custom applications, JavaPlug-ins, or CAD/CAM/CAE applications such as NX.

The following TEM help topics describe panels that allow you to install Teamcenterrich clients and add-on features. For more information about using FMS, see theappropriate client installation guide (for Windows or UNIX/Linux) and the SystemAdministration Guide.

Setting two-tier transport modeIf you want to allow multiple concurrent user sessions of your two-tier rich client, setthe transport mode for the two-tier rich client. In the Activation Mode box, selectPER_CLIENT. (The default value, NORMAL, does not allow multiple concurrentuser sessions.)

• The number of user sessions allowed in PER_CLIENT mode is limited by thecapabilities of your operating system.

• For information about enabling multiple rich client support, see Enablingmultiple client sessions in the appropriate client installation guide (for Windowsor Linux).

Two-tier Teamcenter server settingsIn this step, you specify values required for the rich client to access your Teamcenterserver.

Value Description

Connection Port Specifies the port number on which the TAO implementationrepository service is to run on the client workstation.

Make sure this value reflects the port used by yourTeamcenter corporate server.


Chapter 15 Rich client

Value Description

2–tier Servers Specifies the servers that provide database access for yourrich client.

To add a database, perform the following steps:

1. Click Add.

2. Enter the path to the data directory (TC_DATA) whereyou want Teamcenter Environment Manager to createshared data subdirectories and files. This can be thenetwork path to the TC_DATA directory on yourcorporate server.

3. Enter a unique name for the connection.

4. Click OK.

5. If you want to add access to additional databases,repeat steps 1 through 4 to add access information foreach database.

After you add a database, you can remove databases fromthe list or edit settings using the Remove and Edit buttons.You can also change the priority the rich client uses indatabase access by selecting a database in the table andclicking the Up or Down buttons.

Rich client settingsIn this step, you specify a directory for the rich client to use to store temporary files.Enter a path or accept the default path shown.

Supplying middle-tier server settingsIn this step, you supply connection settings for the four-tier rich client.

The 4-tier Servers table lists Web servers to which the four-tier rich client connects.

To add a server to the table, click Add. Double-click the box in the URI or ConnectionName columns to type values for the additional server.

Use the Up and Down buttons to assign server priority.

To remove a server from the table, select the appropriate row and click Remove.

The Compress (gzip) the responses from the Web application servers check boxis selected by default. This option provides faster connection performance fromthe server.


Rich client

Rich client run-time homeIn this step, you enter a location in which you want to place rich client files duringrun time for the shared rich client installation. In the Runtime Home Locationbox, enter a local path.

For more information about installing a shared rich client, see the appropriate clientinstallation guide (for Windows or UNIX/Linux).

Rich client two-tier settingsIn this step, you enter settings for the two-tier rich client.

In the Rich client Web Server box, enter the URL to the presentation tier Webapplication. Teamcenter uses this value to construct URLs within the two-tier richclient. Optionally, you can leave this field blank, making URLs within the richclient nonfunctional.

Note • Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses,use host names in URIs wherever possible so the domain name system(DNS) can determine which IP address should be used.



• If you use SSL, make sure you include the fully qualified host name inthe URL to the Web application.

Rich client settingsIn this step, you configure access to the Teamcenter online help collection.

Note If you want to install the Teamcenter online help collection on your localhost, return to the Features panel and select the Online Help feature.

Prerequisite:

The Teamcenter online help collection must be installed to a shared locationor a Web server in your network or you must select the Online Help featurein the Features panel.For more information, see the appropriate server installation guide (for Windowsor UNIX/Linux).

Value DescriptionEnable onlinehelp

Specifies that you want to access the Teamcenter online helpcollection from your rich client configuration. Select this checkbox to enable online help access.

Note If you select the Online Help feature in the Featurespanel, this option is enabled by default.


Chapter 15 Rich client

Value DescriptionHelp FilesDirectory

Specifies that you want to access online help installed in anetwork file system location. Enter the path to location of theTeamcenter online help collection, for example, e:\tc\help.

Note • On Windows systems, make sure this path containsa drive letter, such as a local drive or a mappeddrive. Teamcenter online help does not work withUNC paths.

• If you select the Online Help feature in the Featurespanel, the default path is TC_ROOT\help (Windowssystems) or TC_ROOT/help (UNIX/Linux systems).

Web server URL Specifies that you want to access online help deployedon a Web server. Type the URL to the location thatcontains the Teamcenter online help collection, for example,http://host:port/tc/help.

For advanced configuration options, click Advanced.




Rich client run time folderIn this step, you enter a location in which you want to place rich client temporaryfiles during run time. In the Runtime Temp Folder box, enter a local path.


Chapter

16 Lifecycle Visualization

About Lifecycle Visualization installation in TEM . . . . . . . . . . . . . . . . . . . . . 16-1

Choosing a license level for Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . 16-1

Installing the embedded viewer for rich client . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Installing the stand-alone application viewer for rich client . . . . . . . . . . . . . . 16-3

Configuring Lifecycle Visualization for Teamcenter . . . . . . . . . . . . . . . . . . . . 16-3


Chapter

16 Lifecycle Visualization

About Lifecycle Visualization installation in TEMThe following TEM help topics describe panels that allow you to configure LifecycleVisualization.

Teamcenter provides an embedded viewer, the stand-alone Teamcenter lifecyclevisualization product, and the Lifecycle Visualization perspective. The embeddedviewer allows you to visualize 3D models in the Lifecycle Viewer application and alsowithin other Teamcenter client applications such as the rich client and StructureManager. If you want to use the enhanced Lifecycle Visualization capabilities ofTeamcenter lifecycle visualization or the embedded viewer, you must purchase andinstall the necessary additional licenses.

For more information about using Lifecycle Visualization, see Getting Started withProduct Visualization.

Choosing a license level for Lifecycle VisualizationIn this step, you choose the license level for the Lifecycle Viewer.

Prerequisites:

• The Teamcenter license server must be installed and configured with thenecessary Lifecycle Visualization license. Base level Lifecycle Visualizationfunctionality is provided with Teamcenter 10.1. Other license levels must bepurchased separately.

References:

For information about Lifecycle Visualization functionality, see the GettingStarted with Product Visualization guide and the Teamcenter 10.1 lifecyclevisualization help library.

License level DescriptionBase Enables you to access documents, such as 2D images and

3D models, including navigating the 3D product structure.You can also perform basic measurements and view 3Dcross sections of your model.

Standard Provides advanced navigation capabilities, markup tools,including 3D annotations and layering, and precisemeasurement tools.


Chapter 16 Lifecycle Visualization

License level Description

Professional Adds motion playback capabilities to review the dynamicsof a mechanism, advanced 3D cross sections, and outlinecapture. You can optionally use the add-on Concept module.

Mockup In addition to all the functionality listed for the otherproducts, adds 3D clearance analysis and movie capture.You can optionally use the add-on modules listed forProfessional, as well as ClearanceDB and Path Planning.

Note The selected License level includes certain optional licenses:

• Base includes an optional ECAD license.

• Standard includes an optional ECAD license.

• Professional includes optional ECAD, Concept Desktop, andCollaboration licenses.

• Mockup includes optional ECAD, Analysis, Path Planning, ConceptDesktop, and Collaboration licenses.

For information about optional licenses and how to modify them afterinstallation, see the topic about Lifecycle Visualization licensing in theApplication Administration Guide.

Installing the embedded viewer for rich clientIn this step, you provide information required to install the Lifecycle Visualizationembedded viewer for rich client.

Prerequisites:

• A Lifecycle Visualization software distribution image must be available in alocation accessible to this host, or Lifecycle Visualization must be installed ona host accessible to this host.

If Lifecycle Visualization (embedded viewer or stand-alone application viewer) isalready installed:

1. In the Teamcenter Visualization Location box, enter the location in whichLifecycle Visualization software is installed.

2. Select Connect to existing Teamcenter Visualization application at the abovelocation.

If no Lifecycle Visualization software is installed:

1. In the Teamcenter Visualization Location box, enter the location in which youwant to install Lifecycle Visualization software.

2. Select Install Teamcenter Visualization (Embedded) to the above location fromthe following image.


Lifecycle Visualization

3. In the Teamcenter Visualization Install Image box, enter the location of theLifecycle Visualization software distribution image.

Installing the stand-alone application viewer for rich clientIn this step, you provide information required to support the Lifecycle Visualizationstand-alone application viewer for rich client.

Prerequisites:

• Teamcenter 10.1 lifecycle visualization must be installed on the current host.

References:

For information about Lifecycle Visualization licensing and functionality, seethe Getting Started with Product Visualization guide and the Teamcenter 10.1lifecycle visualization help library.

In the Existing Install Location box, enter the location in which LifecycleVisualization software is installed. This feature enables the rich client to launch theinstalled stand-alone application viewer.

Configuring Lifecycle Visualization for TeamcenterIn this step, you enter Lifecycle Visualization settings for Teamcenter.

Value DescriptionProtocol Specifies the protocol to use for Lifecycle Visualization

requests.

Host Specifies the host on which to install Lifecycle Visualization.

Port Specifies the port you want Lifecycle Visualization to use.

Domain Specifies the domain under which Lifecycle Visualizationruns.


Chapter

17 Teamcenter integrations

Configuring ERP Connect Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Teamcenter Integration for NX for rich client . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Teamcenter Extensions for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Workflow to Schedule Integration settings . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Configuring SCM ClearCase Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2


Chapter

17 Teamcenter integrations

Configuring ERP Connect ToolkitIn this step, you install the generic ERP Connect Toolkit interface.

Configuring ERP Connect Toolkit is required only if your site needs to integrateTeamcenter with other Enterprise Resource Planning (ERP)-supported applications,such as BAAN.

Postinstallation:

Complete the software configuration following the instructions in the Preferencesand Environment Variables Reference.

Value Description

Generic Interface Specifies installation of the ERP Connect Toolkit interface.

Teamcenter Integration for NX for rich clientIn this step, you specify the location of your NX installation in the NX InstallLocation field.

Teamcenter Extensions for Microsoft OfficeThis panel verifies whether the current host meets the system requirements forTeamcenter Extensions for Microsoft Office. This includes the required versions ofthe Microsoft .NET framework and other libraries and also a supported versionof Microsoft Office.

On 64-bit operating systems, you cannot install Teamcenter Extensions forMicrosoft Office using TEM. If your host is running a 64-bit operating system,click the Back buttons to return to the Features panel, deselect the TeamcenterExtensions for Microsoft Office feature, and then run the TeamcenterApplications for Microsoft Office installation program (tc_ext4mso.exe) in theadditional_applications\tc_ext4mso directory in the Teamcenter 10.1 softwaredistribution image.

For more information about installing Teamcenter Extensions for Microsoft Office,see the Installation on Windows Clients Guide.


Chapter 17 Teamcenter integrations

Workflow to Schedule Integration settingsIn this step, you specify settings for the Workflow to Schedule Integration.

The Workflow to Schedule Integration allows workflow to send updates to relatedtasks in a schedule. This feature requires a four-tier rich client installation andDispatcher installed and configured.

Value Description

Proxy User Name Specifies the proxy user name for the Teamcenter server.

Proxy User Group Specifies the proxy user group for the Teamcenter server.

Proxy User Password Specifies the password for the proxy user.

4-Tier Web ServerURL

Specifies the URL to the Teamcenter four-tier rich clientdistribution instance.




Configuring SCM ClearCase IntegrationIn this step, you configure the SCM ClearCase Integration by specifying the locationof a ClearCase server on the local host.

Note An existing installation of a ClearCase server is required.


Chapter

18 Multi-Site Collaboration

Installing Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1


Chapter

18 Multi-Site Collaboration

Installing Multi-Site CollaborationIn this step, you install the components that replicate data between multipleTeamcenter sites, enabling the exchange of data objects with other Teamcenterdatabases over a wide area network (WAN).

You must install at least one of the services that Multi-Site Collaboration uses tomanage the replication process for this database:

• The object directory service (ODS) provides location and access information forTeamcenter objects distributed to various sites in a distributed Teamcenterenvironment.

• One or more Teamcenter Distributed Services Manager (IDSM) processesmanage the replication of objects from one Multi-Site Collaboration site toanother.

Value Description

Distributed ServicesManager (IDSM)

Specifies that you want to install the distributed servicesmanager service on this host.

You can choose to install both the IDSM service and theODS service. You must install one of the two services. Ifyou choose both, this system becomes both an IDSM and anODS server for the same database.

Object DirectoryServices (ODS)

Specifies that you want to install the object directoryservices on this host.

You can choose to install both the IDSM service and theODS service. You must install one of the two services. Ifyou choose both, this system becomes both an IDSM and anODS server for the same database.


Chapter

19 Additional features

Installing CAD-BOM alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Product Master Management URL and Security Services . . . . . . . . . . . . . . . . 19-2

Product Master Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3

Installing online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4

Microsoft Office support for rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6

Teamcenter Client for Microsoft Office installation . . . . . . . . . . . . . . . . . . . . 19-6

Teamcenter Client for Microsoft Office configuration . . . . . . . . . . . . . . . . . . . 19-6

Configuring Teamcenter Automotive Edition-GM Overlay . . . . . . . . . . . . . . . 19-7

Embedded Software Solutions for Foundation . . . . . . . . . . . . . . . . . . . . . . . . 19-7

Installing the full-text search engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8

Hierarchical storage management (HSM) settings . . . . . . . . . . . . . . . . . . . . . 19-9

Manufacturing Process Management options . . . . . . . . . . . . . . . . . . . . . . . . 19-9

MATLAB Client Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9

NX Graphics Builder installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9

Configuring Content Management for rich client . . . . . . . . . . . . . . . . . . . . . . 19-9

Configuring Remote Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10

SCM ClearCase for rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-11


Chapter

19 Additional features

Installing CAD-BOM alignmentIn this step, you configure a set of parameters to be used as database preferences toallow the Teamcenter installation to interact and share visual data with Teamcenterproduct master management. Configuring this feature allows designs managed bythis installation of Teamcenter to be related to parts in products that are managedby Product Master Management.

Value Description

PDM SystemNamespace

Specifies a unique cluster of Teamcenter installations.This value must correspond to a valid value defined inthe Product Master Management database. Contactyour Product Master Management administrator for anappropriate valid value. This value is used to populate aUsageWC_MathSystemNamespace database preference.

Note The PDM system namespace is also referred to as amath system namespace.

PDM System Name Specifies a unique name for your Teamcenter installationwithin the scope of the PDM system namespace. This nameis used to identify the originating system of related designcomponents aligned or published to the Product MasterManagement database. This value should be unique withinthe scope of the PDM system namespace. The recommendedvalue is the site ID of your installation. This value is usedto populate a UsageWC_MathSystemName databasepreference.

Note • The PDM system name is automaticallyregistered with Product Master Managementat run time.

• The PDM system name is also referred to asa math system name.


Chapter 19 Additional features

Value Description

Item ID Namespace Specifies the scope of uniqueness for item ID values ofdesigns that are aligned with or published to ProductMaster Management. This value must correspond to avalid value defined in the Product Master Managementdatabase. Contact the Product Master Managementadministrator for an appropriate valid value. This value isused to populate a UsageWC_MathNumberNamespacedatabase preference.

Note The PDM system namespace is also referred to as amath number namespace.

Product Master Management URL and Security ServicesIn this step, you configure access to the Product Master Management application.

Value DescriptionTeamcenter PMM URL Specifies the locale and endpoint URL of the

Product Master Management Web services.Click Add to add a URL to the list.

Locale Specifies the locale for the Product MasterManagement Web services URL. Select a localefrom the list.

PMM URL Specifies the URL of the Product MasterManagement Web tier end point. Type a URLof the following format:

http://host:port/tc/tcbompost/tcbompostwebservice

This value is used to populate aUsageWC_Endpoint database preference.

Enable SSO Specifies whether to enable Security Servicesfor single sign-on with Product MasterManagement.

Application ID Specifies the application ID of your ProductMaster Management installation as configuredin the Security Services installation.

Perpetual Release Mode Specifies that you want Product MasterManagement to use perpetual release mode.

Perpetual release mode uses date-basedpart effectivity to configure the product.Product Master Management does not supportperpetual releasing without part effectivity.

Present Time Mode Specifies that you want Product MasterManagement to use present time release mode.


Additional features

Note • Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses,use host names in URLs wherever possible so the domain name system(DNS) can determine which IP address should be used.



• The release mode cannot be changed after installation completes. Tochange the release mode, you must reinstall the Usage Server.

Product Master ManagementIn this step, you configure Teamcenter alignment with Product Master Management.

Value Description

Teamcenter BOM Web ServiceEnd-Point

Specifies the endpoint URL of the ProductMaster Management Web services, forexample:

http://host:port/tc/tcbompost/tcbompostwebservice

This value is used to populate aUsageWC_Endpoint database preference.

PDM System Namespace Specifies a unique cluster of Teamcenterinstallations. This value must correspond toa valid value defined in the Product MasterManagement database. Contact your ProductMaster Management administrator for anappropriate valid value. This value is used topopulate aUsageWC_MathSystemNamespacedatabase preference.

Note The PDM system namespace isalso referred to as a math systemnamespace.

PDM System Name Specifies a unique name for your Teamcenterinstallation within the scope of the PDMsystem namespace. This name is used toidentify the originating system of relateddesign components aligned or published to theTeamcenter BOM database. This value shouldbe unique within the scope of the PDM systemnamespace. The recommended value is thesite ID of your installation. This value is usedto populate a UsageWC_MathSystemNamedatabase preference.

Note • The PDM system name isautomatically registered with



Value DescriptionProduct Master Management atrun time.

• The PDM system name is alsoreferred to as a math system name.

Item ID Namespace Specifies the scope of uniqueness for item IDvalues of designs that are aligned with orpublished to Product Master Management.This value must correspond to a valid valuedefined in the Product Master Managementdatabase. Contact the Product MasterManagement administrator for an appropriatevalid value. This value is used to populate aUsageWC_MathNumberNamespace databasepreference.

Note The PDM system namespace isalso referred to as a math numbernamespace.

Also, select a release mode for Product Master Management, either PerpetualRelease Mode or Present Time Mode.




Installing online helpIn this step, you choose Teamcenter online help components to include in yourconfiguration. This panel is displayed if you selected the Online help feature inthe Features panel.

Component DescriptionTeamcenter online help library Installs the Teamcenter online help library. This

component is required.

This component requires approximately 561 MBof disk space.


Additional features

Component DescriptionTeamcenter developerreferences

Adds the Teamcenter developer references to theonline help collection. The following referencesare added to the Developer References forCustomization group in the online help library:

C++ API Reference

Integration Toolkit (ITK) Function Reference

Services Reference

This component requires approximately 629 MBof additional disk space.

Note These references are installed only tothe Teamcenter HTML Help Collection.They are not available in PDF format,and therefore are not installed to thePDF collection.

Teamcenter Data Model Report Adds the Teamcenter Data Model Report to theDeveloper References for Customization group inthe online help library.

The Teamcenter Data Model Report containsdocumentation on standard Teamcenter datamodel objects, such as business objects, classes,attributes, properties, lists of values (LOVs), andothers.

This component requires approximately 3.44 GBof additional disk space.

Note Due to its size, this component requiressignificantly more time to install.

Teamcenter PDF help collection Installs the Teamcenter online help collection inPDF format on your local host.

After installation, you can open the online helpcollection from the following location:

• Windows systems:

TC_ROOT\PDF\index.html

• UNIX or Linux systems:

TC_ROOT/PDF/index.html

This component requires approximately 344 MBof additional disk space.



You can add any of these components when creating a new Teamcenter configurationor updating an existing configuration.

During installation, TEM prompts you for the location of the online help archive filesneeded for installation. When prompted, browse to the location of the Teamcenterdocumentation distribution image. The files you may be prompted for are thefollowing:

tchelp.jartcrefs.jarDataModelReport.zipPDF.zip

Microsoft Office support for rich clientIn this step, you type the URI to the Teamcenter Client for Microsoft Officeapplication.




Teamcenter Client for Microsoft Office installationThis panel verifies whether the current host meets the system requirements forTeamcenter Client for Microsoft Office. This includes the required versions of theMicrosoft .NET framework and other libraries and also a supported version ofMicrosoft Office.

On 64-bit operating systems, you cannot install Teamcenter Client for MicrosoftOffice using TEM. If your host is running a 64-bit operating system, click the Backbuttons to return to the Features panel, deselect the Office Client for MicrosoftOffice feature, and then run the Teamcenter Client for Microsoft Office installationprogram (setup.exe) in the additional_applications\OfficeClient directory inthe Teamcenter 10.1 software distribution image.

For more information about installing Teamcenter Client for Microsoft Office, see theInstallation on Windows Clients Guide.

Teamcenter Client for Microsoft Office configurationIn this step, you enter Teamcenter server settings for Teamcenter Client forMicrosoft Office.

Value Description

Install Teamcenter Single Sign-onsupport for Office Client

Select this check box if you want to useSecurity Services with Client for Office.


Additional features

Value Description

SSO Application IDSpecifies the application ID of your Teamcenterinstallation as configured in the SecurityServices installation.

Protocol Specifies the protocol used to access theSecurity Services application (http or https).

SSO Server Host Specifies the server host for the SecurityServices application.

SSO Server Port Specifies the port used by the Security Servicesapplication.

SSO Application Name Specifies the application name of the SecurityServices application.

Configuring Teamcenter Automotive Edition-GM OverlayIn this step, you configure Teamcenter Automotive Edition-GM Overlay.

Value Description

GMO Prefix ID Specifies three uppercase alphabetical characters to prefixGMO item IDs.

The prefix ID you enter must be 3 characters and containonly uppercase letters.

A GMO item ID has 8 characters, the first 3 are thealphabetical characters you specify as the prefix; thefollowing 5 characters are numeric. For example, if youspecify an item ID prefix of ABC, items are created withitem IDs starting from ABC00001 to ABC99999.

Note For postinstallation tasks for Teamcenter Automotive Edition-GM Overlay,refer to the Installation on Windows Clients Guide and the Installation onLinux Clients Guide.

Embedded Software Solutions for FoundationIn this step, you select settings for Embedded Software Solutions:

Install default software typesSelect this option if you want to install the default Teamcenter item types thatrepresent recognized embedded software parts and types.

Install default processor typesSelect this option if you want to install the default Teamcenter item types thatrepresent recognized processors.

For more information about configuring and using Embedded Software Solutions,see the Embedded Software Solutions Guide.



Installing the full-text search engineIn this step, you install the full-text search engine and configure searching for thelocal database. The full-text search engine enables users to retrieve objects from theTeamcenter database based on search criteria. It allows users to specify searcheson metadata values, as well as full-text retrieval searches on both metadata andcommon forms of text data.

For information about building keyword indexes, see the description of thebuild_fts_index utility in the Utilities Reference guide.

Prerequisite:

If you intend to connect to a full-text search engine on another host, the full-textsearch engine must be installed and running on that host.

Value Description

DISH ServiceConfiguration

ACI Port Specifies the number of the port on which AutonomyContent Infrastructure (ACI) sends action commandsto the Autonomy Distributed Services Handler (DiSH)service. This setting should be the same as the PORTsetting in the search engine server configuration file.

Service Port Specifies the number of the port on which the DISHservice runs.

IDOL ServiceConfiguration

ACI Port Specifies the number of the port on which AutonomyContent Infrastructure (ACI) sends action commands tothe Autonomy Intelligent Data Operating Layer (IDOL)server. This setting should be the same as the PORTsetting in the search engine server configuration file.

Service Port Specifies the number of the port on which the full-textsearch engine service runs.

Index Port Specifies the number of the port on which to indexdocuments for full-text search engine server. This settingshould be the same as the INDEXPORT setting in thesearch engine server configuration file.

File System FetchService Configuration

ACI Port Specifies the number of the port on which AutonomyContent Infrastructure (ACI) sends action commands tothe file system fetch service. This setting should be thesame as the PORT setting in the search engine serverconfiguration file.

Service Port Specifies the number of the port on which the file systemfetch service runs.


Additional features

Hierarchical storage management (HSM) settingsIn this step you specify settings for third-party hierarchical storage management(HSM) software.

Value Description

HSM Primary Hosts Specify hosts on which third-party HSM software isinstalled. To add a host to the table, click Add. To remove ahost from the table, select the host and click Delete.

Read ThruSupported by 3rdParty HSM Software

Specifies whether third-party HSM provides read-throughcapability.

HSM Secondary TierCapacity (GB)

Specifies the capacity, in gigabytes, of the HSM storagevolume.

Manufacturing Process Management optionsIn this step, you select Manufacturing Process Management types to include inyour installation.

MATLAB Client IntegrationIn this step, you configure the Teamcenter integration with MATLAB Simulink.

Value DescriptionMATLAB Installation Directory Enter the path to the installation directory for

the MATLAB integration.

Staging Directory Enter the path to the staging directory whereMATLAB files are stored.

Teamcenter SOA URL Type the Teamcenter services URL for thelogon dialog.

For more information about the Teamcenter integration with MATLAB, see theBehavior Modeling Tool Integration Guide.

NX Graphics Builder installationIn this step, you enter the location of the NX installation.

Configuring Content Management for rich clientIn this step, you identify Content Management Web servers you want to accessfrom this rich client host. Click Add or Remove to add or remove server URLsfrom the table.






Configuring Remote WorkflowIn this step, you configure Teamcenter to enable linking between Teamcenter andother products such as Teamcenter portfolio, program and project management.

Note This option applies only when you are deploying the four-tier architecture.

Prerequisites:

• Remote Workflow components, including the Application Registry, must beseparately installed and configured.

• The Web tier application must be installed and configured as described in theInstallation on UNIX and Linux Servers Guide and the Installation on WindowsServers Guide.

Value Description

Application RegistryServer

Host Specifies the name of the host on which TeamcenterApplication Registry runs.

Port Specifies the port number used by Application Registry.

Web ContainerProtocol Specifies the protocol used to access the Java servlet

container (http or https).Host Specifies the host where the Java servlet container that

runs Teamcenter Application Registry resides.

Port Specifies the port number used by the Java servletcontainer that runs Teamcenter Application Registry.

Application Name Specifies the name of the Web application that containsApplication Registry.


Additional features

Value Description

Local ApplicationGUID

Specifies a global unique identifier (GUID) for theTeamcenter database being registered with ApplicationRegistry.

Tip Enter only one GUID for each Teamcenterdatabase being registered (that is, one per site).For example, if you configure remote workflow formultiple products at a single site, use one GUID.Entering a new GUID overwrites a previouslyentered GUID.

Servlet Name Specifies the name of the Teamcenter chooser servletinstance being registered.

Tip This information applies only to linking withPortfolio, Program and Project Management.If you are configuring linking with a differentproduct, accept the default value (the field cannotbe left blank).

Servlet Description Specifies a brief description of the Teamcenter chooserservlet instance being registered.

Tip This information applies only to linking withPortfolio, Program and Project Management.If you are configuring linking with a differentproduct, accept the default value (the field cannotbe left blank).

SCM ClearCase for rich clientThis panel verifies the required version of the ClearCase client is installed on thisrich client host.


Chapter

20 Updates Manager

About Updates Manager actions in TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Updates Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Removing backup files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Choosing a patch to apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Choosing an update to apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Supplying information about the updates server . . . . . . . . . . . . . . . . . . . . . . 20-2

Applying updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2

Enable new capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2


Chapter

20 Updates Manager

About Updates Manager actions in TEMThe following TEM help topics describe panels displayed by Updates Manager, aTEM feature that applies downloaded patches to Teamcenter.

For more information about applying patches using Updates Manager, see theappropriate server installation guide (for Windows or UNIX/Linux).

Updates ManagerIn this step, you choose whether to download updates, apply updates, or roll backupdates.

The Updates Manager is TEM feature that applies downloaded patches toTeamcenter.

Removing backup filesIn this step, you may choose to remove backups of files replaced by patches youapplied previously.

Choosing a patch to applyIn this step, you choose a patch to apply to your Teamcenter installation.

Prerequisites:

• Download patch files from GTAC.

In the Download Directory box, enter the path to the directory in which youdownloaded Teamcenter patches. In the File box, enter the name of the update filethat contains the patch you want to apply.

Choosing an update to applyIn this step, you choose an update to apply to your Teamcenter installation.

Prerequisites:

• Download update files from GTAC.


Chapter 20 Updates Manager

In the Download Directory box, enter the path to the directory that contains theupdate file you downloaded. In the Update List box, select one or more updatesto apply.

To view the readme file for the update, click View README.

Supplying information about the updates serverIn this step, you provide FTP access information for the server on which you postdownloaded Teamcenter updates.

Value DescriptionHost Specifies the host name of the updates server.

Port Specifies the port used by the updates server.

User Specifies the user name to use when accessing the updatesserver.

Password Specifies the password to use when accessing the updatesserver.

Directory on FTPwhere updates arelocated

Specifies the FTP path on the updates server fortransferring updates.

Path can be browsed Specifies whether the FTP directory on the updates servercan be browsed.

Applying updatesIn this step, you specify the locations of the update kit and the backup directory.

In the Update kit location box, enter the directory that contains the downloadedTeamcenter update files you want to apply to your Teamcenter installation.

In the Backup directory box, enter the directory you want to contain backups offiles replaced during the update process.

For more information about applying Teamcenter updates, see the appropriateTeamcenter server installation guide (for Windows or UNIX/Linux).

Enable new capabilitiesIn this step, you confirm whether to enable new capabilities added by the currentTeamcenter maintenance pack.

To enable the new capabilities listed, click Next. Otherwise, click Back to choosea different maintenance option, or click Cancel to cancel installation of themaintenance pack.

For information about the new capabilities listed, see the What’s New section ofthe maintenance pack README file.


Chapter

21 Upgrade

Pre-upgrade diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Warnings from diagnostic tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Custom database template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Type collision verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Upgrading workflow objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Identify the Teamcenter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Additional upgrade options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Database daemons port check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3

Reporting and Analytics upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3

Repeatable Digital Validation database user . . . . . . . . . . . . . . . . . . . . . . . . . 21-4

Selecting a Teamcenter configuration to upgrade . . . . . . . . . . . . . . . . . . . . . . 21-4

New application root directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4

Old application root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4

Test environment location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4

Verifying templates and features for the test environment . . . . . . . . . . . . . . . 21-5

Upgrade information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5

Upgrade database features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5


Chapter

21 Upgrade

Pre-upgrade diagnosticsThis panel performs a series of diagnostics on your existing Teamcenter installationto assess readiness for upgrade to Teamcenter 10.1.

In the Enter a working directory where logs can be created box, enter a locationwhere TEM can create log files for pre-upgrade diagnostics.

Click Run to begin pre-upgrade diagnostics.

Note No Teamcenter data is modified in this step. No upgrade processes areinitiated.

When the diagnostics are complete, this panel displays the results of the pre-upgradediagnostics. To view a detailed log of these results, click Review.

If any pre-upgrade diagnostics fail, you must resolve those issues before you canproceed with upgrade.

For more information about troubleshooting upgrade issues, see the Upgrade Guide.Also, see the latest Teamcenter Upgrade Issues Catalog on GTAC:

http://support.industrysoftware.automation.siemens.com

Warnings from diagnostic testsThis panel is displayed because one or more warnings occurred during pre-upgradediagnostics. Review the warnings and any recommended actions, and acknowledgeeach warning by selecting each check box before you continue.

Custom database templateIn this step, you enter a template file name. Any items found in the database whichare not part of the default templates will be written out into this custom template file.

Value DescriptionTemplate Type a name for a new custom template that will be used to

store the extra items.


Chapter 21 Upgrade

Type collision verificationIn this step, you specify your current version of Teamcenter for the type collisionverification analysis performed during pre-upgrade diagnostics.

Type collisions occur when two or more types (business objects) have the same name.This duplication causes a conflict (collision), requiring that one of the identicalnames be changed. If your database has defined custom type names that are thesame as any type that will be added by Teamcenter during this upgrade, yourdatabase cannot be upgraded.

In the Current Release box, select your current Teamcenter version, and then clickthe OK button to return to the Pre-Upgrade Diagnostics panel.Warning It is very important that you select the exact version and patch level

of your database. Do not guess or select a release that is close to therelease. Doing so can cause an incorrect analysis.

TEM performs the type analysis during pre-upgrade diagnostics. If TEM detectsa type collision, the upgrade is blocked from proceeding. The results of the typecollision analysis are placed in the log directory.

Note If you do not see your Teamcenter version listed in the Current Release box,contact your Siemens PLM Software customer support representative.

Upgrading workflow objectsIn this step, you specify how to handle workflow objects during Teamcenter upgrade:

• Upgrade all workflow jobsSelect this option if you want to convert all file-based workflow templates todatabase workflow template objects, convert any transient objects associatedwith the workflow templates to persistent objects, and update the referencingworkflow processes.

• Upgrade in-process jobs onlySelect this option if you want to convert only those workflow objects that are inprocess.

For more information about configuring and using workflows, see the SystemAdministration Guide.

Identify the Teamcenter configurationIn this step, you type a unique ID and optional description for the Teamcenterconfiguration.

Additional upgrade optionsIn this step, you specify how you want to proceed when errors are encounteredduring Teamcenter upgrade.


Upgrade

• Stop database upgrade at first errorThis option stops Teamcenter upgrade when the first error occurs.

Note Siemens PLM Software strongly recommends this option whenupgrading production systems.

• Stop database upgrade after accumulating all errorsThis option allows the database upgrade to continue when an error isencountered, and report all errors at the end of the upgrade process.

Caution Siemens PLM Software strongly recommends using this optiononly when upgrading a test environment. Errors during databaseupgrade could render the database unusable.

Using the upgrade errors report displayed in TEM, you can address multipleissues preventing a successful upgrade before you attempt an upgrade again.

You can also submit the upgrade errors log file to Siemens PLM Softwarecustomer support for further analysis.

For more information about using Teamcenter upgrade error logs, see the UpgradeGuide.

If you want to generate a client cache, select the Generate client cache check box.The client cache is a cache of data that rich clients can download once at initiallogon and then reuse on the client host. This option reduces server demand, reducesstartup time, and improves overall performance. When you select this option, TEMruns the generate_client_meta_cache utility at the end of the install, upgrade,or update action. If you clear this option, but a client cache already exists, the oldclient cache is deleted.

For more information about the generate_client_meta_cache utility, see theUtilities Reference.

Database daemons port checkThis panel verifies the port specified for database daemons is available.

Reporting and Analytics upgradeIn this step, you choose how you want to upgrade your Reporting and Analyticsinstallation.

• Upgrade metadata

Upgrade metadata from previous installation.

• Upgrade WAR

Upgrade the Reporting and Analytics WAR file from the previous installation.

• Upgrade WAR and metadata

Upgrade the WAR file and metadata from the previous installation.


Chapter 21 Upgrade

• Upgrade metadata and create new WAR

Upgrade the metadata and create a new Reporting and Analytics WAR file.

Repeatable Digital Validation database userIn this step, you provide information needed to access the Repeatable DigitalValidation (RDV) database.

Value DescriptionUser Specifies the user name of the RDV database

user.

Password Specifies the password for the RDV databaseuser.

Selecting a Teamcenter configuration to upgradeIn this step, you select a Teamcenter configuration to upgrade from the list ofconfigurations provided.

New application root directoryIn this step, you specify the root directory for your upgraded Teamcenter installation.In the New Application Root Directory, enter the root directory for the upgradedTeamcenter installation.

This panel contains a table of all features found in the existing installation, withthe current status of each. Click Browse to add any custom templates missingfrom the table.

Old application rootIn this step, you specify the location of your previous Teamcenter installation.

Test environment locationIn this step, you specify a location in which to create the copy of your productionenvironment.

Note TEM does not prompt you to select features when creating a copy of anenvironment for testing. The features installed in the test environment arebased on the feature data models that are installed in the database. You canadd additional features after the copy process is complete.


Upgrade

Verifying templates and features for the test environmentIn this step, you locate features associated with templates applied to the database ina copy of a production environment you create for upgrade testing.

TEM displays this panel if you select Create environment for upgrade testing in theWelcome to Teamcenter panel.

The table shows features being applied to the database for the copy of the productionenvironment. If a feature is not shown for a given template, click Browse to locatethe associated feature XML file.

Caution This panel does not verify template versions. Make sure the templateand feature versions are correct before you continue.

Upgrade informationIn this step, you enter information to upgrade your existing installation. When youclick the Next button, TEM attempts to connect to the database and get all volumeinformation from it. TEM also verifies you have write permission on each localvolume folder. This can take up to several minutes.

Value Description

Old TC_DATALocation

Enter the path of the TC_DATA location on the server tobe upgraded.

New TC_DATALocation

Enter the new path you want to use for the upgradedTC_DATA location on the server.

Database User Enter the user name of a user with DBA rights on the sever,for example, infodba.

Database Password Enter the password for the user.


! @ $ % ’ " : ; . < > ( ) { }

Upgrade database featuresIn this step, you provide paths to templates that need to be upgraded.

This panel provides a list of templates provided by Siemens PLM Software and ourpartners. Any template showing Upgrade in the status column has been detected inthis database and must be upgraded. If a template was detected and the path to thetemplate is missing, use the Browse button to find the missing template package.After all matched template packages are found, the Next button is enabled.

Warning Failure to find all missing template packages results in migration issueswith your custom data model to the Business Modeler IDE, possiblecorruption of data, and issues with using TEM.


Chapter 21 Upgrade

Value DescriptionBrowse Click this button to locate paths to the packaged template

ZIP files.


Index

CConfiguration Manager . . . . . . . . . . . . . 1-2Creating a Teamcenter configuration . . . 1-1

DDatabase configuration . . . . . . . . . . . . . 2-1Dispatcher . . . . . . . . . . . . . . . . . . . . . 11-1

FFile Management System . . . . . . . . . . . 7-1FMS . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

GGlobal Services . . . . . . . . . . . . . . . . . . 13-1

IInstallationQuick preconfigured installation . . . . . 5-1

Installing Teamcenter . . . . . . . . . . . . . . 1-1

LLicense management . . . . . . . . . . . . . . . 3-1Lifecycle Visualization . . . . . . . . . . . . . 16-1

MMaintenance packs, applying . . . . . . . . . 1-2MP, applying . . . . . . . . . . . . . . . . . . . . 1-2

PPanelsMaintenance . . . . . . . . . . . . . . . . . . . 1-2Welcome to Teamcenter . . . . . . . . . . . 1-1

Password, valid characters . . . . . . . 4-6–4-9,5-5, 5-7, 5-9, 14-2, 14-5, 21-5

Patches, applying . . . . . . . . . . . . . . . . . 1-2Patching . . . . . . . . . . . . . . . . . . . . . . . 20-1

RReporting and Analytics . . . . . . . . . . . 12-1Rich client . . . . . . . . . . . . . . . . . . . . . 15-1

SSilent installation . . . . . . . . . . . . . . . . . 1-1

TTCCS) . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Teamcenter administratorpassword . . . . . . . . . . . . . . . . . . 4-6–4-9,5-5, 5-7, 5-9, 14-2, 14-5, 21-5Teamcenter client communicationsystem . . . . . . . . . . . . . . . . . . . . . . . . 8-1Teamcenter Environment ManagerAccessing online help . . . . . . . . . . . . . 1-1Launching . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter lifecycle visualization . . . . . 16-1Teamcenter reporting and analytics . . . 12-1TEMAccessing online help . . . . . . . . . . . . . 1-1Launching . . . . . . . . . . . . . . . . . . . . . 1-1

UUninstalling Teamcenter . . . . . . . . . . . . 1-2Updates Manager . . . . . . . . . . . . . 1-2, 20-1Updates, installing . . . . . . . . . . . . . . . . 1-2Upgrading a Teamcenter configuration . . 1-1

WWeb tier . . . . . . . . . . . . . . . . . . . . . . . . 9-1

PLM00128 H Teamcenter Environment Manager Help Index-1