Team Center 9.1 Installation - Server - Windows PDF

Teamcenter 9.
Installation on Windows Servers Guide
Publication Number
PLM00013 H
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2012 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter
is a trademark or registered trademark of Siemens Product Lifecycle Management
Software Inc. or its subsidiaries in the United States and in other countries. All
other trademarks, registered trademarks, or service marks belong to their respective
holders.
2 Installation on Windows Servers Guide PLM00013 H

Contents
Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2
Part I: Getting started with Teamcenter server installation
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installation and deployment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Part II: Database server installation
IBM DB2 installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

IBM DB2 installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Install IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Create a DB2 sample database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Verify connectivity with the sample database . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Create a DB2 database for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Upgrade Oracle server and databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Configure an Oracle database for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Microsoft SQL Server installation and configuration . . . . . . . . . . . . . . 5-1

Microsoft SQL Server installation and configuration . . . . . . . . . . . . . . . . . . . 5-1
Install MS SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Create an SQL Server database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Part III: Teamcenter server installation
Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
PLM00013 H Installation on Windows Servers Guide 3

Contents
Install the licensing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Select destination directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Install a volume server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Install NX and Teamcenter Integration for NX or NX Integration . . . . . . . . . . 6-4
Best installation practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Install a Teamcenter corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Start database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Configure heterogeneous operating system environment . . . . . . . . . . . . . . . . 8-4
Part IV: Web tier installation
.NET Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

.NET Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Install the .NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Start the Web client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Configuring online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
J2EE Web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Installing thin client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Installing rich client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Part V: Adding features
Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Install the .NET server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Install the J2EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Install the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Install the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Installing a custom solution or third-party template . . . . . . . . . . . . . . 13-1

Installing a custom solution or third-party template . . . . . . . . . . . . . . . . . . . 13-1
Install a template using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Update the database using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Contents
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Install the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Updating the Manufacturing Resource Library from an earlier version . . . . . . 14-7
Planning data migration from Genius4000 to Resource Manager . . . . . . . . . 14-10
Install EDA server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Install EDA server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Installing Teamcenter reporting and analytics . . . . . . . . . . . . . . . . . . 16-1

Installing Teamcenter reporting and analytics . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Create the Reporting and Analytics database . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Configure the Reporting and Analytics license file . . . . . . . . . . . . . . . . . . . . . 16-2
Install Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Install Remote Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Deploy Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Complete Reporting and Analytics installation . . . . . . . . . . . . . . . . . . . . . . . 16-5
Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Installing Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Installing Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Install online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Configure online help access for Teamcenter clients . . . . . . . . . . . . . . . . . . . 18-10
Part VI: Additional configuration and maintenance
Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . 19-1

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Create a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Modify a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Add an existing Teamcenter database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Add or configure a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Configure multiple databases for a four-tier rich client . . . . . . . . . . . . . . . . . . 19-5
Deploying localized versions of Teamcenter . . . . . . . . . . . . . . . . . . . . . 20-1

Deploying localized versions of Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Configuring client display language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Environment settings for non-English locales . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Deploying localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Silent installation using SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Silent installation using Teamcenter Environment Manager . . . . . . . . . . . . . 21-9
Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Contents
Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Patching Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Install patches on the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Patch the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1
Uninstall Teamcenter configurations and installations . . . . . . . . . . . . . . . . . . 23-1
Uninstall TCCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Uninstalling DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
Uninstall SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
Part VII: Appendixes
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . A-5
Troubleshooting the .NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Troubleshooting document rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . A-17
Recovering from a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18
Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Teamcenter documentation distribution image . . . . . . . . . . . . . . . . . . . . . . . B-2
Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Contents
Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Two-tier deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Four-tier deployment (enterprise and Web tiers on same host) . . . . . . . . 1-15
Four-tier deployment (enterprise and Web tiers on separate hosts with HTTP
server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Four-tier deployment (multiple enterprise tier hosts and Web tier
hosts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Four-tier deployment (load balancing) . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Basic File Management System deployment . . . . . . . . . . . . . . . . . . . . 2-12
Browsing for the template files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Selecting the new feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Viewing the templates to be installed . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Starting a full model update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Selecting the template for update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Teamcenter HTML online help collection . . . . . . . . . . . . . . . . . . . . . . . 18-1
Teamcenter PDF online help collection . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Multiple databases (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . 19-6
Sample silent installation configuration file . . . . . . . . . . . . . . . . . . . . 21-12
Tables
Platform support for Teamcenter servers and clients . . . . . . . . . . . . . . 1-2

Required hard disk space for Teamcenter configurations . . . . . . . . . . . . 1-4
Rich client optional parameter values . . . . . . . . . . . . . . . . . . . . . . . . 10-25
Lifecycle Visualization (embedded viewer) parameter and table
values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Lifecycle Visualization (stand-alone application viewer) parameter and table
values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Teamcenter Integration for NX parameter and table values . . . . . . . . 10-27
Content Management System for Rich Client 4-Tier values . . . . . . . . . 10-27
Environment settings on Windows systems . . . . . . . . . . . . . . . . . . . . . 20-5
Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Web tier required parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Web tier optional parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
Global Services context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . D-8

Part
I Getting started with Teamcenter

server installation
This guide describes how to install Teamcenter 9.1 on Microsoft Windows servers.
This includes installation of Teamcenter servers using Teamcenter Environment
Manager and the Teamcenter Web tier using the Web Application Manager.
This guide assumes you have a thorough working knowledge of your operating
system and general knowledge of Teamcenter use.
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
PLM00013 H Installation on Windows Servers Guide

Chapter
1 Getting started
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
System hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Web tier support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Software integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Teamcenter servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Additional servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Network Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Teamcenter network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Selecting and configuring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Basic tasks in Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Installing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Installing a Teamcenter server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Installing the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Installing Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

Chapter
1 Getting started
Getting started
Verify you have installed supported versions of all prerequisite software and plan
your Teamcenter network before you begin installing servers.
Prerequisites
Install prerequisite software and verify that your hardware is supported for
Teamcenter 9.1.
For information about versions of operating systems, third-party software,
Teamcenter software, and system hardware certified for your platform, see the
Siemens PLM Software Certification Database:
http://support.industrysoftware.automation.siemens.com/certification/teamcenter.shtml
Note
Some software requirements differ for non-English locales. When viewing the
certification database, make sure you note any exceptions for your locale.
Platforms
Determine from the following table which Teamcenter 9.1 servers and clients are
supported on your operating system. Bullet characters (•) denote supported servers
and clients.
Platform support for Teamcenter servers and clients
PLM00013 H Installation on Windows Servers Guide 1-1

Chapter 1 Getting started
Business
Modeler
Corporate Web Rich Thin IDE
Operating System server tier client client client TCCS1
Microsoft Windows • • • •
(desktop platforms)2
Microsoft Windows • • •
(server platforms)3
Sun Solaris • •
Hewlett-Packard HP-UX4 • •
IBM AIX • • • • • •
SUSE Linux • • • • • •
Red Hat Linux5 • • • • • •
Apple Macintosh Mac OS • •
Notes about platform support

General notes
• For information about versions of operating systems certified for Teamcenter
9.1, see the Siemens PLM Software Certification Database.
• For information about installing Teamcenter on Windows clients, see the

Installation on Windows Clients Guide.
• For information about installing Teamcenter on UNIX or Linux servers, see

the Installation on UNIX and Linux Servers Guide.
• If your Teamcenter database server is IBM DB2, all Teamcenter servers and
two-tier rich clients in your network must run operating systems supported
for Teamcenter with IBM DB2. IBM DB2 databases are supported only
with Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE
Linux platforms.
Microsoft Windows
• Make sure the C:\Temp directory exists, and grant full access permissions
to this directory for all users.
• On Windows Server and Windows 7, disable Windows User Account Control

(UAC) before you install Teamcenter. This option is available in the Control
Panel→User Accounts dialog box.
1. Teamcenter client communication system (TCCS) is installed with the rich client. This column refers to the stand-alone TCCS
application.
2. Microsoft Windows desktop platforms include Windows XP and Windows 7.For information about installing Teamcenter on Windows
clients, see the Installation on Windows Clients Guide.
3. Microsoft Windows server platforms include Windows Server 2008.
4. Itanium platforms only. PA-RISC hardware is not supported.
5. Only 64-bit Red Hat Linux is supported.
1-2 Installation on Windows Servers Guide PLM00013 H

Getting started
Windows UAC can interfere with Teamcenter installation programs.

Siemens PLM Software recommends turning off UAC for administrative
users only.
For more information, see Microsoft Windows documentation.
• Disable the Windows TCP scaling feature. Open a command prompt and
enter the following command:
netsh interface tcp set global autotuninglevel=disabled
Siemens PLM Software recommends setting this parameter before installing

Teamcenter because most client network infrastructures use one or more
switches or routers. By default, Windows enables TCP window scaling, but
some routers do not support this feature. This can cause installation failures
that are difficult to diagnose and correct.
For more information, see Microsoft Windows documentation.
• Teamcenter applications are 32-bit and run on both 32- and 64-bit versions
of Windows.
• If you use a nonnative language operating system version of Windows, you

must install and enable the Multilingual User Interface (MUI) pack to
ensure the language font is displayed properly.
1. Download and install the MUI pack for Windows from Microsoft.
2. Open the Regional and Language Options dialog box in the Windows
Control Panel.
3. In the Languages tab, set the required language for the menus and
dialogs.
4. In the Advanced tab and the Regional Options tab, set the required
language.
System hardware
Make sure your Teamcenter host has the required amount of disk space available.
Required hard disk space for Teamcenter configurations shows the required disk
space for the following common Teamcenter configurations:
• Corporate server
The corporate server contains the features included in the Corporate Server
solution in Teamcenter Environment Manager (TEM). Additional features may
require additional disk space.
For more information, see Install a Teamcenter corporate server.
• Two-tier rich client

The two-tier rich client contains the features included in the Rich Client 2-tier
solution in Teamcenter Environment Manager (TEM). Additional features may
require additional disk space.
For more information, see the appropriate Teamcenter client installation guide
(for Windows or UNIX/Linux).

• Web tier
The Web tier includes the Web Application Manager, a distribution server, and a
distribution server instance that contains the Over-the-Web installer and Rich
Client 4-tier solutions. Additional solutions may require additional disk space.
For more information, see J2EE Web tier installation.
Required hard disk space for Teamcenter configurations

Corporate Two-tier
Platform server rich client Web tier
Hewlett-Packard HP-UX6 3.0 GB Not supported 3 GB
IBM AIX 2.0 GB 450 MB 3 GB
SUSE Linux 2.0 GB 300 MB 3 GB
Red Hat Linux 2.0 GB 300 MB 3 GB
Sun Solaris 2.5 GB Not supported 3 GB
Microsoft Windows 1.5 GB 450 MB 4.5 GB
Database
Teamcenter requires a relational database management system (RDBMS) for storing
Teamcenter data. Before you install a Teamcenter, you must install an IBM DB2,
Oracle, or Microsoft SQL Server database server and make sure your Teamcenter
corporate server host has access to the server.
For information about supported database server versions, see the certification
database:
Choose a database management system that suits the platforms of your Teamcenter
servers and clients. When planning your network, consider the following limitations:
• Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannot
connect to Microsoft SQL Server database servers.
• If your Teamcenter database server is IBM DB2, all Teamcenter servers and
for Teamcenter with IBM DB2. IBM DB2 databases are supported only with
Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE Linux
platforms.
For information about installing a database server for Teamcenter, see IBM DB2
installation and configuration, Oracle installation and configuration, or Microsoft
SQL Server installation and configuration.
6. Itanium platforms only. PA-RISC hardware is not supported.

Getting started
Web browser
The Teamcenter thin client and Over-the-Web Installer7 require a Web browser.
Teamcenter 9.1 supports the following Web browsers:
• Windows systems: Microsoft Internet Explorer and Mozilla Firefox

• UNIX and Linux systems: Mozilla Firefox
• Macintosh systems: Apple Safari
For information about versions supported, see the Siemens PLM Software
Certification Database.
Note
No 64-bit Java plug-in is available for 64-bit Mozilla Firefox on Linux
platforms. If you use the thin client on Linux platforms, you must install 32-bit
Mozilla Firefox and the Java plug-in before you install the four-tier rich client.
Web tier support

Install the required software for the Teamcenter Web tier you use:
• J2EE Web tier
Java Runtime Environment (JRE)

Install a supported JRE on the host where you build Teamcenter Web
applications.
J2EE application server

Install a supported application server on the host where you deploy
Teamcenter Web applications.
• .NET Web tier
Microsoft Internet Information Server (IIS)

Install IIS on your Teamcenter corporate server host.
Microsoft .NET framework

Install the .NET framework on all Teamcenter hosts.
For supported versions of these products, see the certification database:

Note
Some Web application servers require special configuration for use with
Teamcenter.
For more information, see the Web Application Deployment Guide.
7. The Over-the-Web Installer installs the four-tier Teamcenter rich client and Teamcenter Microsoft Office interfaces.

Software integrations
If you use Teamcenter 9.1 integrations to other Siemens PLM Software products or
third-party software, install those products before you install Teamcenter 9.1.
Some Siemens PLM Software products require separate licenses from your Siemens
PLM Software representative. Siemens PLM Software products are licensed using
the Siemens PLM Software Common Licensing Server.
For more information about the Common Licensing Server, see Install the licensing
server.
Enabling Teamcenter installation

After you install prerequisite software, locate the Teamcenter software and
documentation distribution images and make sure they are accessible to your client
host. For descriptions of Teamcenter distribution images, see Distribution media.
Note
Teamcenter software distribution images can contain multiple ZIP files. For
example, the software distribution image for Windows consists of two files
named Tcn_win_1_of_2.zip and Tcn_win_2_of_2.zip. If you download
software distribution images for Teamcenter, you must download all files
in the set to obtain the complete image. After you download files, extract
all ZIP files to a common directory to assemble the image before you begin
installation.
Configuring Teamcenter installation

Before you install Teamcenter, create an operating system logon account for
Teamcenter. This account must belong to the Administrators group and must be
granted the Log on as a service right. Teamcenter services run on the server as
this user account.
Log on using this account when you install the Teamcenter corporate server and
when you perform maintenance such as upgrading or installing updates using
Teamcenter Environment Manager.
Starting Teamcenter installation

To begin installing Teamcenter installation, launch the appropriate Teamcenter
installation tool:
• Teamcenter Environment Manager
To install the Teamcenter corporate server, launch Teamcenter Environment
Manager using the tem.bat command from the Teamcenter software distribution
image.
• Web Application Manager

Getting started
To begin installing the Teamcenter J2EE Web tier, launch the Web Application
Manager using the insweb command from the install directory in the
WEB_ROOT directory.8
Interfaces: Teamcenter installation tools

Teamcenter installation tools (Teamcenter Environment Manager and the Web
Application Manager) enable you to build and manage your Teamcenter installation.
Teamcenter Environment Manager

Teamcenter Environment Manager is a tool that installs Teamcenter servers and
two-tier and four-tier rich clients.
Teamcenter Environment Manager

Teamcenter Environment Manager also performs maintenance operations, such as
upgrading servers, applying maintenance packs, and installing patches.
You launch Teamcenter Environment Manager using the tem.bat command.
8. You create this directory when you install the Web Application Manager as described in J2EE Web tier installation.

Web Application Manager

The Web Application Manager is a tool that installs thin client and rich client
solutions and builds Teamcenter J2EE Web applications.

You launch the Web Application Manager by entering the insweb command. The
Web Application Manager allows you to create multiple Web applications that
contain different sets of Teamcenter solutions. This enables you to create Web
applications for different groups of users in your network. Your Web applications
can access the same Teamcenter corporate server, but provide different subsets of
Teamcenter functionality. The Web Application Manager creates separate staging
locations and separate deployable files9 for each Web application. Some Teamcenter
solutions require other solutions and some solutions may not be combined with other
solutions in the same Web application. For more information about using the Web
Application Manager, see J2EE Web tier installation.
Note
The .NET Web tier is installed using Teamcenter Environment Manager,
not the Web Application Manager.
9. A deployable file is a Web archive (WAR) or enterprise archive (EAR) file, depending on the solutions it contains.

Getting started
Basic concepts about Teamcenter installation

Determine the Teamcenter servers and network architectures suit your needs and
which features you want to install.
Database server
A Teamcenter network requires access to a database server.
Before you install Teamcenter, you or your database administrator must install and
configure a database server to store Teamcenter data. The Teamcenter corporate
server must have access to a database server or a database client. Teamcenter
supports IBM DB2, Oracle, and Microsoft SQL Server databases.
For information about installing a database server for Teamcenter, see IBM DB2
For Oracle configuration settings and tuning methods to optimize Teamcenter
performance, see the Teamcenter Deployment Guide, available in the documentation
section of Siemens PLM Software’s support site. The Teamcenter Deployment
Guide also provides an in-depth review of Oracle database performance issues and
diagnosis, and configuration and tuning guidelines.
For Microsoft SQL Server configuration settings and tuning methods to optimize
Teamcenter performance, see the Teamcenter Deployment Guide, available in the
documentation section of Siemens PLM Software’s support site. The Teamcenter
Deployment Guide also provides an in-depth review of Microsoft SQL database
performance issues and diagnosis, and configuration and tuning guidelines.
Note
Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannot
connect to Microsoft SQL Server database servers.
Teamcenter servers
You can install different types of Teamcenter servers according to the features you
use and your load distribution needs.
Corporate server
A Teamcenter corporate server installation includes the following components:
• Teamcenter shared binary executables and files
• Teamcenter shared data subdirectories and files
• Database connection
• Teamcenter volume
• Additional optional Teamcenter features such as File Management System (FMS)
Additional servers
A Teamcenter network requires one corporate server configuration. Additional
servers are optional, but can help balance network loads and facilitate heterogeneous
networks (networks with hosts running different operating systems).

Teamcenter clients
Teamcenter provides clients suited to various uses and network configurations.
These clients include the rich client, the thin client, and specialized clients such as
Teamcenter Client for Microsoft Office and Network Folders.
Rich client
The rich client is a platform-independent client implementation (Java application)
for users who interact with Teamcenter frequently. It is extendable and able to run
both Teamcenter and customer-written applications. Customers can also extend the
standard user interface.
The rich client application is deployed on each user workstation using Teamcenter
Environment Manager or the Over-the-Web Installer, depending on which
Teamcenter network architecture you use. The rich client is supported in both
architectural models described in Two-tier architecture and Four-tier architecture.
Thin client
The thin client provides access to Teamcenter through a standard commercial Web
browser, such as Microsoft Internet Explorer or Mozilla Firefox. The user interface
provides a streamlined browser-based view of product information stored in a
Teamcenter database.
The thin client is supported only in the four-tier architectural model described in
Four-tier architecture.
Network Folders
Teamcenter Network Folders is an extension (plug-in) to Microsoft Windows Explorer.
Network Folders provides access to Teamcenter through Windows Explorer. Users
unfamiliar with the rich client and thin client interfaces can perform document
management of Teamcenter objects from Windows Explorer without launching
Teamcenter.
Network Folders is supported only on Microsoft Windows platforms and only in the
four-tier architecture model described in Four-tier architecture.
If you install the Teamcenter proxy server for WebDAV, you can also map a network
drive to Teamcenter, enabling access to Teamcenter objects through common
Windows actions like Open and Save As.
For more information, see the Installation on Windows Clients Guide.
Teamcenter network architectures

Teamcenter provides two architecture models for deployment: two-tier and four-tier.
Two-tier architecture
The two-tier architectural model comprises the following tiers:
• Client tier
The client tier comprises the Teamcenter rich clients.

Getting started
In a deployment of the two-tier architecture, the Teamcenter server runs on

the client workstation.
Note
The two-tier rich client is installed only through TEM. Over-the-Web
installation is supported only for the four-tier rich client.
Some Teamcenter client features, such as Teamcenter Integration for
NX, Lifecycle Visualization, and Teamcenter Client for Microsoft Office,
require the Web tier, a component of the four-tier architecture. To enable
these features for a two-tier rich client, you can connect the two-tier rich
client to a deployment of the Web tier. For information about functionality
you can add to a rich client and which add-ons require the Web tier, see
Rich client installation.
• Resource tier
The resource tier comprises a database server, database, volumes, and file
servers.
Rich Client Rich Client Rich Client

Client
Tier (Local TC (Local TC (Local TC
Server) Server) Server)
Resource Volume Database

Tier
Two-tier architecture
In the two-tier model, you deploy the Teamcenter rich client, which includes the
local server, and the optional applications that integrate with the rich client on the
client workstation. Typically, the database server, volumes, and file servers are
installed on one or more separate hosts.
Teamcenter File Management System (FMS) manages the rich client access to
volumes:
• The FMS server cache (FSC) process run on the server hosting the volume.
• The FMS client cache (FCC) process runs on the rich client host.
For more information about FMS and two-tier rich client architecture, see File
Management System installation.

2-Tier Rich Client

FCC FSC Volume
Teamcenter
Server
Teamcenter Files
(application root)
Database
Database
Server
Two-tier deployment
Four-tier architecture
The four-tier architecture model comprises the following tiers:
• Client tier
The client tier comprises the Teamcenter rich client, thin client, and other clients
such as Teamcenter Client for Microsoft Office.
Note
The rich client can be deployed with additional functionality, such as
Lifecycle Visualization, Teamcenter Client for Microsoft Office, and
Teamcenter Integration for NX or NX Integration 4.0.1. (Teamcenter
Integration for NX/NX Integration 3 is not supported.)
For information about the functionality you can add, see Rich client
installation.
• J2EE Web tier

The J2EE Web tier is a Java application that runs in a Java 2 Enterprise Edition
(J2EE) application server, such as Oracle WebLogic, and is responsible for
communication between the client tier and enterprise tier. For information about
supported application servers, see the Siemens PLM Software Certification
Database:
• Enterprise tier

Getting started
The enterprise tier comprises a configurable pool of Teamcenter C++ server

processes and a server manager. The enterprise tier retrieves data from and
stores data in the database.
A server manager manages a pool of Teamcenter server processes. You must
install a server manager whenever you deploy the Web tier.
Note
Teamcenter provides server managers based on the J2EE and the
Microsoft .NET platforms. Install the appropriate server manager for
the Web tier you use.
• Resource tier
The resource tier comprises a database server, database, volumes, and file
servers.
Client
Rich Client Thin Client WebDAV
Tier Client
Web Application Server

Tier Teamcenter EAR
Teamcenter Server
Enterprise Servers Manager
Tier
Resource
Tier Volume Database
Four-tier architecture
You can design deployments that host the Web tier, resource tier, and enterprise
tiers on the same computer or on separate computers:
• Smaller sites can run the pool of servers and the server manager on the same
host as the Web tier.

• Larger sites can distribute the pool of server processes across multiple hosts
and optionally include an HTTP server to serve static files or multiple HTTP
servers to support load balancing.
For a multihost configuration, the server pool consists of multiple subpools, one
or more for each host. Each subpool is managed by one server manager process.
The Web tier balances the load across the server pools.
The Teamcenter J2EE based server manager and Web tier application both employ
the JBoss cache, a tree-structured cache, to provide replication and transaction
context. You must configure the JBoss cache (called TreeCache in Teamcenter) in
both the J2EE based server manager and the Web tier application.10
To ensure communication between the Web tier and the server manager, you must
coordinate the values you specify for each component. For some values, you must
provide the identical value when configuring the Web tier application.
If you are setting up multiple Web tier environments with separate domains, you
must configure:
• A minimum of one server manager for each Web tier deployment.
• A separate TreeCache cluster for each environment.

To configure a separate TreeCache cluster, Siemens PLM Software recommends
configuring a different port (multicast) or set of ports (TCP) for each cluster.
The JMX HTTP adapter allows you to view the status of the server pool and
dynamically alter the pool configuration values (the values are not persistent).
Access this functionality from the following URL:
http://host-name:jmx-port
Replace host-name with the name of the host running the server manager. Replace
jmx-port with the number of the port running the JMX HTTP adapter. This port
number is defined when you install the J2EE based server manager.
The first time you log on to the adapter, use manager for both the user name
and the password. You can change the user name and password to unique values
using the adapter.
Teamcenter File Management System (FMS) manages the rich client access to
volumes:
• The FMS client cache (FCC) process runs on the rich client host.
• The FMS server cache (FSC) process runs on each server hosting a volume and
each server hosting a pool of Teamcenter servers (TcServer).
Note
If you install File Management System, the FMS server cache (FSC) and the
server manager must run on the same host server, with the same user ID.
10. This is not required if you use the .NET Web tier and the .NET based server manager.

Getting started
Thin Client 4-Tier Rich Client

FCC
Third-Party
Application Server
tc.ear
Starts server processes

for multiple users.
TC Server n
Server Manager
TC Server n+1
FSC
TC Server n+2
Database FSC
Volume
Database Server
Four-tier deployment (enterprise and Web tiers on same host)

HTTP Server
Third-Party
Application Server
Starts server processes

for multiple users.
TC Server n Server Manager
TC Server n+1
TC Server n+2
Database
Database Server
Four-tier deployment (enterprise and Web tiers on separate hosts with HTTP server)

Getting started
HTTP Server
Third-Party Third-Party
Application Server Application Server
tc.ear tc.ear
Server Manager Server Manager Server Manager
TC Server n TC Server n TC Server n
Database Server
Database
Four-tier deployment (multiple enterprise tier hosts and Web tier hosts)

Load Balancing
HTTP Server HTTP Server
Third-Party Third-Party
Application Server Application Server
tc.ear tc.ear
Server Manager Server Manager Server Manager
TC Server n TC Server n TC Server n
Database Server
Database
Four-tier deployment (load balancing)

Getting started
Selecting and configuring features

The Features panel in Teamcenter Environment Manager provides many features
you can include in your Teamcenter server.
For a complete list of available features, see Teamcenter features.
Some Teamcenter features require additional configuration after Teamcenter
installation is complete.
For information about additional configuration steps, see Teamcenter postinstallation
tasks.
Basic tasks in Teamcenter installation

Installing a Teamcenter network generally consists of installing a database server, a
Teamcenter server, an optional Web tier, and Teamcenter clients.
Installing a database server

Install a database server (IBM DB2, Oracle, or Microsoft SQL Server) according to
the vendor’s documentation and the Teamcenter guidelines provided in IBM DB2
Installing a Teamcenter server
Install one or more Teamcenter servers as described in Teamcenter server

installation.
Installing the Web tier
Install the .NET Web tier as described in .NET Web tier installation or install the
J2EE Web tier as described in J2EE Web tier installation.
Installing Teamcenter clients
Install Teamcenter clients as described in the appropriate client installation guide

(for Windows or UNIX/Linux).

Chapter
2 Site planning
Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installation and deployment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Planning the Teamcenter network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installing Teamcenter components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Thin client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
File Management System installation . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Installing File Management System . . . . . . . . . . . . . . . . . . . . . . 2-11
Creating volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Lifecycle Visualization installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Global Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Remote workflow installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Security Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Teamcenter online help installation . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Oracle server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
MS SQL server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Network environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Homogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Heterogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Required operating system and user accounts . . . . . . . . . . . . . . . . . . . . . 2-20

Chapter
2 Site planning
Site planning
Plan your Teamcenter network and identify software issues that may affect your
installation.
Installation and deployment overview

Determine the network architecture you want to use and the components you want
to install.
Planning the Teamcenter network

A Teamcenter network can include server and client hosts from more than one
vendor with each host running one of several supported operating systems.
The roles described in the following table are not restricted to one host on the
Teamcenter network. A host often performs more than one of these roles. A role can
be performed by more than one host in the network.
Network node Role

Database server Database service node that contains an installation
of RDBMS software and services queries from several
Teamcenter servers.
For large-scale installations, the database server is
typically a dedicated high-performance server system
that is optimized specifically for running database server
software.

Chapter 2 Site planning
Network node Role

Corporate server Teamcenter service node at the center of a Teamcenter
network. The corporate server contains installations of the
following Teamcenter components:
• The Teamcenter shared binary executables.
This installation directory is referred to as the
Teamcenter application root directory. The TC_ROOT
environment variable points to this location.
A Teamcenter application root directory can be
NFS/CIFS-mounted to more than one application client.
• The Teamcenter shared data subdirectories and files.

This installation directory is referred to as the
Teamcenter data directory. The TC_DATA
environment variable defines this location. Each data
directory is associated with a single database instance,
but multiple data directories can point to a single
database instance.
The data directory is exported with full write access
and mounted via NFS/CIFS by other Teamcenter nodes.
• A minimum of one Teamcenter volume and File

Management System (FMS).
To install volumes on multiple hosts for the same
database, install a server that points to the database
and install FMS on any system that services a volume.
• The server manager process required when the

Teamcenter network includes the Web tier.1
The server manager starts and stops Teamcenter
servers, informing a server assigner of its actions so
that the assigner can assign available servers to user
sessions.
Multiple application clients can map to or mount the

corporate server.
Web-tier application Teamcenter service node that contains an installation of the
server Teamcenter Web tier application deployed in a third-party
application server.
Teamcenter clients Hosts containing an installation of the Teamcenter
rich client executables and connected to a Teamcenter
corporate server or application server. Hosts accessing the
Teamcenter thin client over the Web.
1. Teamcenter provides server managers based on the J2EE and the Microsoft .NET platforms. Install the appropriate server manager
for the Web tier you use.

Site planning
The following table describes additional network nodes you can include in your
network.
Network node Role

Multi-Site Network node that runs a daemon process to publish data
Collaboration ODS objects within a Multi-Site Collaboration environment.
server Configuration of Multi-Site Collaboration is optional.
Publication of a data object makes the object visible to
other databases. At least one Teamcenter database on the
network must be designated as an ODS database: this
database stores publication records for the data objects.
One ODS server node must be designated for each ODS
database, and each server node can only act for one
database.
Multi-Site Network node running daemon processes that perform
Collaboration ODS proxy services for ODS servers within a Multi-Site
proxy server Collaboration environment. Configuration of Multi-Site
Collaboration is optional.
Typically, the proxy server node is connected between
a firewall and the ODS server nodes. ODS requests
originating from external sites go through the firewall
directly into the proxy server node, which relays the ODS
requests to the ODS servers. In this way, the proxy server
protects the ODS servers from direct access from external
sites. It also simplifies firewall management because the
firewall manages only one TCP/IP port for all external ODS
requests.
Note
A node can act both as an ODS proxy server and
IDSM proxy server at the same time.
Multi-Site Network node running a daemon process that transfers
Collaboration IDSM data objects among databases (sites) in a Multi-Site
server Collaboration environment. You must designate one IDSM
server node for each Teamcenter database from which
objects are published. Each server node can act only for
one database.
Multi-Site Network node running daemon processes that perform
Collaboration IDSM proxy services for IDSM servers.
proxy server
Typically, the IDSM proxy server node is connected between
a firewall and the IDSM server nodes. IDSM requests
originating from external sites go through the firewall
directly into the proxy server node, which relays the IDSM
requests to the IDSM servers. In this way, the proxy server
protects the IDSM servers from direct access from external
sites. It also simplifies firewall management because the
firewall manages only one TCP/IP port for all external
IDSM requests.

Network node Role

Quick part locator Component of Repeatable Digital Validation (RDV).
(QPL) server The QPL server provides a qpl daemon used with
DesignContext. This daemon coexists with all other
Teamcenter daemons. For QPL-based DesignContext,
QPL server setup is required. For Appearance-based
DesignContext, QPL server setup is not required.
Installing Teamcenter components

Your installation process depends on the network architecture and Teamcenter
features you use.
Note
The Teamcenter .NET Web tier supports both two-tier and four-tier
deployments but does not require a J2EE application server. For more
information about installing the .NET Web tier, see .NET Web tier installation.
Two-tier architecture installation

The primary components of a two-tier installation require three general installation
tasks:
1. Install the database and database server using IBM DB2, Oracle, or MS SQL
Server tools.
For the installation procedures, see Database server installation.
2. Install Teamcenter executables and files, create and/or populate the database,
and configure a volume using Teamcenter Environment Manager.
For the installation procedures, see Teamcenter server installation.
3. Install the rich client on a client workstation using Teamcenter Environment

Manager.
For the installation procedures, see either the Installation on Windows Clients
Guide or Installation on UNIX and Linux Clients Guide.

Site planning
4 2-Tier Rich Client
3 Exe - portal.bat
Installed
by TEM
Implementation Repository
Exe - start_imr.bat
Teamcenter Files
Teamcenter
Server Installed at TC_ROOT
Exe - start_TcServer1.bat
Corporate server installation
using Teamcenter Environment
Manager.
Database
Server
1
Database
Two-tier architecture installation
Four-tier architecture installation
A four-tier installation involves installation tasks for each tier:

1. Install the resource tier using the third-party database server software, either
Oracle or MS SQL Server.
Install the resource tier using the third-party database server software (IBM
DB2, Oracle, or MS SQL Server).
For the installation procedures, see Database server installation.
2. Install the enterprise tier using Teamcenter Environment Manager, being sure
to choose the server manager component.
Teamcenter Environment Manager installs the pool of Teamcenter servers and
the server manager, creates and or populates the database, and configures a
volume.2
For the installation procedures, see Teamcenter server installation.
2. Teamcenter provides server managers based on the J2EE and the Microsoft .NET platforms. Install the appropriate server manager
for the Web tier you use.

3. Generate the J2EE Web tier as an enterprise archive (EAR) file using the Web
Application Manager and deploy the EAR file in a J2EE application server.3
Note
The thin client is installed as part of the Web tier for access by clients.
For the installation procedures, see J2EE Web tier installation.
4. Install a third-party application server and deploy the Teamcenter EAR file.3
5. If you are deploying the rich client, deploy the Over-the-Web Installer and
configure a rich client for installation.3
For an overview, see Rich client installation.
For the installation procedures, see Installing rich client Web applications.
6. Install the rich client on a client workstation using the Over-the-Web Installer.
For the installation procedures, see either the Installation on Windows Clients
Guide or Installation on UNIX and Linux Clients Guide.
Note
The automatic logon feature is not supported in four-tier Teamcenter
deployments.
For more information about the automatic logon feature, see the Preferences
and Environment Variables Reference.
3. This is not necessary if you use the .NET Web tier and the .NET based server manager.

Site planning
6 Thin Client 4-Tier Rich Client

Installed on
Exe - http://host:port/tc/webclient Installed as Exe - portal.bat starts
Client Host
5 part of the otwportal.bat
Over the Web
Uses - http://host:port/tc/webclient Web tier. Uses - http://host:port/tc/webclient
4 EAR File Generated Using Web Application Manager (insweb)

Deployed in Third-Party Application Server Software
Third-Party Port number used by clients
3 Application Server
tc.ear
TC Server n+2
Exe - tcserver
TC Server n+1
Teamcenter Servers and
Exe - tcserver Server Manager installed using
Teamcenter Environment Manager (TEM)
TC Server n Server Manager

2 Exe - mgrstart
Exe - tcserver Starts server processes Uses - tc_root
for multiple users. tc_data
1 Database
Database Server
Four-tier architecture installation

Rich client installation
The Teamcenter rich client is a Java application that runs on client hosts. The
two-tier rich client is installed on each client host using a stand-alone instance of
Teamcenter Environment Manager. The four-tier rich client is installed using a
distributed instance of the Over-the-Web Installer.
To install the two-tier rich client, you launch Teamcenter Environment Manager on
your client host, select the client components you want to install, and then proceed
with installation.
To install the four-tier rich client, you use a Web browser open the URL of a
Web application server that serves the Over-the-Web Installer. The four-tier rich
client installs silently, with no prompts. Teamcenter administrators configure
all installation options and provide all the information necessary to complete
installation using Web Application Manager.
To enable over-the-Web installation for the four-tier rich client, you install the
following components on a server host.
• A rich client distribution server.
The distribution server software manages the connection between a rich client
distribution instance and the Over-the-Web Installer. The Over-the-Web
Installer contacts the distribution server for the rich client files to download to
the user’s workstation.
Only one rich client distribution server is required to manage multiple rich
client distribution instances.
• A rich client distribution instance or instances.

A rich client distribution instance contains the Over-the-Web Installer and the
rich client software to be installed on user workstations.
To enable different users to install different configurations of rich client software,
you must create a distribution instance for each unique configuration.
• A third-party Web server.

You deploy rich client distribution instances in a third-party Web application
server.
After you install and deploy a rich client distribution server and distribution
instances, you can change the distribution server contents, add components to
a distribution instance, and patch components in a distribution instance using
Web Application Manager. The next time users start a rich client installed from
that distribution instance, the rich client startup process checks for updates and
downloads them to the client hosts.

Site planning
Open Web page
Created by Web application manager

using 'Distribution Server' instance otw.html
installing.html
otw_installer.jar
Uses - instance = "web application name" Check that client
server_name = "hostname:rmi port" installed is current
and install or update.
Example - instance = "Teamcenter 2 Tier OTW
server_name = "hostname:12001"
Distribution Server
Exe - start_server.bat
Uses - webapps.dat
RMI
Created by Web application manager
Exe - start_rmi.bat
using 'Distribution Server'
Rich client installation

When configuring a rich client distribution instance (for a four-tier rich client) or a
local rich client instance (for a two-tier rich client), you can add the functionality to
the rich client, such as the following features:
• Teamcenter Integration for NX or NX Integration
When you choose this option, the rich client is enabled to use NX with
Teamcenter. Users must separately install NX executable files on the client
hosts. All client hosts installing from a particular distribution instance must
have NX installed in the same location.
Note
Configuring Teamcenter Integration for NX requires additional manual
steps to be performed by the user as prompted by the Over-the-Web
Installer.
• Teamcenter lifecycle visualization (embedded viewer)

When you choose this option, Teamcenter lifecycle visualization executable files
are included in the distribution instance.

Note
Installing the rich client does not require that the user have system
administration privileges on the client workstation. However, if
Teamcenter lifecycle visualization is included with the rich client instance,
system administration privileges are required.
• Teamcenter lifecycle visualization (stand-alone application viewer)

When you choose this option, the rich client is enabled to launch Teamcenter
lifecycle visualization. Users must independently install Teamcenter lifecycle
visualization executable files on the client hosts. All client hosts installing a
distribution instance must have Teamcenter lifecycle visualization installed
in the same location.
Note
The Teamcenter lifecycle visualization integration requires the
presentation tier application, a component of the four-tier architecture. To
enable Teamcenter lifecycle visualization for a two-tier rich client, you can
connect the two-tier rich client either to a deployment of the Web tier or to
a deployment of the presentation tier application.
• Teamcenter Automotive Edition–GM Overlay

When you choose this option, the Teamcenter Automotive Edition–GM Overlay
executable files are included in the distribution instance.
• Remote workflow
When you choose this option, the rich client is enabled to support the linking of
objects between Teamcenter and other applications such as Teamcenter portfolio,
program and project management. Separate installation of remote workflow
components and Teamcenter Application Registry are required.
• Teamcenter EDA
When you choose this option, the rich client is configured for use with Teamcenter
EDA. The Teamcenter EDA stand-alone client must also be installed.
• SCM ClearCase
When you choose this option, the executable files are included in the distribution
instance for the integration between Teamcenter and the IBM Rational
ClearCase software configuration management (SCM) tool.
For a complete list of available Teamcenter features for the rich client, see Solutions
and features reference.
For information about creating, deploying, and updating the rich client distribution
server and rich client distribution instances, see Installing rich client Web
applications. Instructions for installing the rich client over the Web on a client host
are in the Installation on UNIX and Linux Clients Guide and the Installation on
Windows Clients Guide.

Site planning
Thin client installation
The Teamcenter thin client is a Web browser-based application. You install the thin
client as part of the Web tier application. To install the Web tier, you use the Web
Application Manager to create and install an enterprise archive (EAR) file that you
then deploy in a third-party application server on the Web tier host.
Users access the thin client from the Web tier host using a third-party Web browser
such as Microsoft Internet Explorer, Mozilla Firefox, and Safari. No aspect of the
thin client is installed on a user workstation other than the required third-party
Web browser.
File Management System installation
File Management System (FMS) downloads and uploads file data for the rich client,
embedded viewer, and the thin client configured with Lifecycle Visualization.
Multi-Site Collaboration also uses FMS servers to transfer data.
Note
If you install File Management System, the FMS server cache (FSC) and the
server manager must run on the same host server, with the same user ID.
If the FSC does not manage any volumes, that is, if it is purely a cache server,
it can run as any user that is convenient.
Installing File Management System
FMS provides the following functions:

• Volume server for file management
• Shared server-level performance cache for shared data access between multiple
users
• Client-based private user cache for rich clients
• Transient data store mechanism for transporting reports, PLM XML, and other
nonvolume data between the Web and client tiers in the four-tier architecture
FMS caching enables placing the data close to the user, while maintaining a central
file volume and database store.
FMS requires the installation of FMS server cache (FSC) and FMS client cache
(FCC) components:
• The FSC component provides a server process and file caches for Teamcenter
server hosts.
• The FCC component provides a client process and file caches for rich clients
on user workstations.

Rich Client
FCC Vol 1
LAN SYSTEMS
Rich Client
FCC Vol 2
TC Server
FSC Server
Visualization
Client
Vol 3
FCC
Basic File Management System deployment
Installing the FMS server cache

You can configure the FMS server cache (FSC) server to perform any combination of
the following functions:
• Volume server or performance cache server
When running on a host where a volume is located or directly mounted on the
computer hosting the FSC, the FSC acts as a volume server.
When running on a host where a volume is not located or directly mounted, the
FSC acts as a performance cache server.
As a volume or cache server, the FSC checks all file access requests for a ticket
that Teamcenter generates to authorize file access. As a cache server, it manages
two segment caches, one for downloading files and one for uploading files.
• Configuration server
As a configuration server, the FSC provides FMS configuration information to
the FMS client caches and other FSCs.
• Transient server (in a deployment of the four-tier architecture only)

As a transient server, the FSC delivers PLM XML and other transient files
to clients.
Any deployment of Teamcenter requires a minimum of one FSC server. You can
deploy multiple FSC servers, each performing a multiple roles or each performing
a designated purpose as either a volume, a cache, or a configuration server. When
you install multiple volumes on different hosts for the same database, the multiple
FSC servers are linked through a common master FSC. (You can manually configure
more than one master FSC.)
You must install an FSC server on:
• Each host running a Teamcenter server manager.
• Each host that will contain a Teamcenter volume.
FSC servers and caches are configured using XML-based files, in a hierarchical
structure:

Site planning
• FMS master configuration file (fmsmaster_fsc_id.xml)

The master configuration file describes the File Management System network
and defines FSC groups. It is the highest file in the hierarchy and can define
default values for FSCs and FCCs, such as the maximum sizes of the caches.
Each installation of Teamcenter requires one FMS master configuration file.
At least one FSC server reads this file and is called the master FSC. Other
FSC servers in the network download FMS configuration information from the
master FSC server.
If you install only one FSC server in a Teamcenter network, it is the master.
• FSC configuration file (fscfsc_id.xml)

The FSC configuration file configures an individual FSC in a network. It specifies
the address of the master FSC (for downloading FMS network information) and
defines such values as the maximum sizes of the server segment file caches
and the upload timeout value.
This file can either inherit values from the master file or override them. It can
also define default values for FCCs.
• The FCC configuration file defines values for the FCC on client hosts, such as the
maximum sizes of the caches.
It can either inherit values from the FSC configuration file or override them.
The Teamcenter installation program, Teamcenter Environment Manager, installs

and initially configures the FSC servers, segment file caches, master configuration
file, and FSC configuration file or files. For small deployments of Teamcenter, this
may be the only installation and configuration required. For large deployments, you
can take advantage of FMS flexibility by manually configuring the FMS network.
For detailed information, see the System Administration Guide.
Installing the FMS client cache

The FMS client cache (FCC) process runs on a client host and performs the following
functions:
• Uploads files to an FSC server
• Requests files from an FSC server
• Caches files on the client host
The FCC process manages three file caches:

• A write cache containing whole files uploaded to a Teamcenter volume
• A read cache containing whole files downloaded from a Teamcenter volume
• A segment cache for Teamcenter lifecycle visualization
Installation of the FCC depends on whether the client workstation hosts the rich
client or thin client:
• The rich client requires an FCC, and the Over-the-Web Installer automatically
installs an FCC with each rich client.

The rich client uploads files to the Teamcenter volume and downloads files from
the Teamcenter volume using the FCC. If Teamcenter lifecycle visualization 6.0
or later is installed on the workstation and used with the rich client, it optionally
uses the FCC.
When you create the rich client instance to be installed on user workstations,
you configure the location of the cache on the workstation and the maximum size
of files downloaded from the volume or uploaded to the volume. Installing the
rich client instance on a workstation simultaneously installs the FCC process
and caches. No additional configuration steps are required.
For information on configuring the FCC while creating the rich client instance,
see Installing rich client Web applications. Configuring the FCC this way
may be the only configuration you require, but you can take advantage of
additional configuration options by manually configuring the FCC. For manual
configuration information, see the System Administration Guide.
• The thin client does not use the FCC. Workstations that access the thin client
do not require its installation.
However, if you install the FCC, Teamcenter lifecycle visualization 6.0 and NX
4.0.1 use it to upload files to and download files from the Teamcenter volume.
Installing the FCC enables users to take advantage of FMS features:
o Improved file transfer performance
FMS is a high-performance file transfer solution that gives client applications
direct access to files over a high-performance network connection.
o File streaming
Teamcenter lifecycle visualization uses proprietary file streaming technology
to download appropriate portions of the JT files over the network as they are
needed. FMS supports segment file transfer to keep network loads down and
support this high-performance file streaming technology.
o Built-in caching infrastructure

The FCC is dedicated to a specific user on the client. The FSC server can be
shared by groups of users.
o Deployment flexibility
FMS components support a multitude of deployment configurations. This
enables administrators to geographically locate volumes and shared FSC
servers close to client workstations, providing the ability to tune the system
for optimal file transfer performance.
For information on installing an FCC for use with the thin client and Teamcenter
lifecycle visualization, see the the appropriate Teamcenter client installation
guide (for Windows, UNIX/Linux, or Macintosh).
Creating volumes
Using Teamcenter Environment Manager installation program, you create two
types of Teamcenter volumes:
• Standard volumes

Site planning
Standard volumes are Microsoft Windows folders Teamcenter uses to store files
managed by Teamcenter. Users cannot directly access the files in these volumes;
they must do so via a Teamcenter session. One standard Teamcenter volume is
required per database. You can optionally create multiple volumes for a database.
You create a standard volume when installing Teamcenter and populating a
Teamcenter database. Volumes require the installation of File Management
System (FMS). FMS provides the volume services after the volume is created.
• Transient volumes
A transient volume is a Microsoft Windows folder that Teamcenter uses to store
temporary data for transport of reports, PLM XML, and other data between
the Web tier and client tier in a deployment of the four-tier architecture. One
transient volume is required per Teamcenter server host.
You can create a transient volume directory on a server host when installing
Teamcenter and populating a Teamcenter database (the installation program
adds the definition to the fmsmaster_fsc_id.xml configuration file). For
examples of manually configuring transient volumes that cannot be accomplished
using the installation program, see the Preferences and Environment Variables
Reference.
Note
Teamcenter uses transient volumes only in a deployment of the four-tier
architecture. For a deployment of the two-tier architecture, Teamcenter
stores this data into a temporary directory on the rich client host, rather
than in a defined transient volume. The temporary directory is defined
either by the start_server script or by the Transient_Volume_RootDir
on the client host.
Teamcenter administrators can also create volumes using the rich client
Organization application.
For information about creating volumes after installation of Teamcenter, see the
Organization Guide.
Lifecycle Visualization installation

For enterprise-wide product visualization capability, you can install Teamcenter
lifecycle visualization and add a Lifecycle Visualization viewer to your Teamcenter
configuration.
Siemens PLM Software provides two Lifecycle Visualization viewers for use with
Teamcenter:
• Lifecycle Visualization embedded viewer (rich client only)
The Lifecycle Visualization embedded viewer is embedded in the rich client user
interface. The embedded viewer provides full 2D visualization capabilities and
3D viewing and is available to all Teamcenter users.
The embedded viewer is installed on user workstations over the Web as part of
a rich client distribution instance. The license level is configured as part of
the rich client distribution image. All users installing a rich client distribution
image that includes Lifecycle Visualization must have administration privileges
on the workstation.

• Lifecycle Visualization stand-alone application viewer (rich client and thin client)
The Lifecycle Visualization stand-alone application viewer is launched from
either the Teamcenter rich client user interface or the thin client user interface.
Users can also run it as a stand-alone application. The suite includes the
embedded viewer and Teamcenter lifecycle visualization mockup.
The stand-alone application viewer is individually installed on each client
workstation using the Teamcenter lifecycle visualization distribution images.
The rich client distribution instance can be configured with the information
required to enable the rich client to integrate with Lifecycle Visualization
applications already installed on client workstations.
Lifecycle Visualization uses Teamcenter client communication system (TCCS).

If your Teamcenter configuration includes a rich client and a Lifecycle Visualization
viewer, Lifecycle Visualization uses Teamcenter volumes and FMS, including the
FMS server cache (FSC) and FMS client cache (FCC). (FCC is a component of TCCS.)
When installed as a stand-alone application, Lifecycle Visualization can use
Teamcenter volumes and FMS if you install TCCS on the client host.
When configured with the thin client, Lifecycle Visualization uses Teamcenter
volumes and the FSC if you install TCCS.
For information about installing TCCS, see the appropriate Teamcenter client
installation guide (for Windows, UNIX/Linux, or Macintosh).
For information about installing Lifecycle Visualization, see the Teamcenter lifecycle
visualization Installation Guide in the Lifecycle Visualization online help library.
For information about installing Lifecycle Visualization viewers provided with
Teamcenter, see Teamcenter features and Rich client solutions and Teamcenter
Environment Manager Help.
For information about patching Lifecycle Visualization viewers provided with
Teamcenter, see Patch Lifecycle Visualization.
Note
• The Teamcenter rich client supports the 32-bit embedded viewer only. On
64-bit systems, if you want to use the embedded Lifecycle Visualization
components in the rich client, you must install the 32-bit version of the
viewer.
You can install both 32-bit and 64-bit viewers on a given machine at the
same time, allowing you to run the 64-bit version of the application in
stand-alone mode and the 32-bit version in embedded mode. For this
installation scenario, you must install the 32-bit viewer last to ensure all
paths and environment variables are correct for the embedded viewer
to work in the rich client.
• You can configure both Lifecycle Visualization viewers for use with a rich
client. If you configure both products, you must install the embedded
viewer in a separate directory from the stand-alone application viewer.
The embedded viewer and the stand-alone application viewer require
separate license files.

Site planning
Global Services installation

Global Services provides the additional components that enable a Teamcenter site to
exchange BOM data with a Teamcenter Enterprise site:
• The Teamcenter connector extracts BOM data from Teamcenter.
• The Teamcenter Enterprise Connector extracts BOM data from Teamcenter

Enterprise.
To enable users to exchange data between Teamcenter and Teamcenter Enterprise,

you must install and configure Global Services, the Teamcenter and Teamcenter
Enterprise connectors.
Global Services is available in the Web_tier\tcgs directory on the Teamcenter
software distribution image. For installation information, see Install Global Services.
Remote workflow installation

Remote workflow enables users to create links between Teamcenter objects and
objects in Teamcenter portfolio, program and project management. Users can launch
the linked Teamcenter product from within the Teamcenter rich client.
Security Services installation

Security Services eliminates the need for multiple authentication challenges as users
move from one Teamcenter application to another. Authentication is performed by
an external identity service provider, such as lightweight directory access protocol
(LDAP).
Security Services is an optional feature and is installed separately from Teamcenter.
Installation and initial configuration involve the following steps:
1. Install Security Services, noting the following information for configuring
Teamcenter:
• Application ID for this instance of Teamcenter in the Security Services
application registry
• Complete URL of the Security Services Login Service Web application
• Complete URL of the Security Services Identity Service Web application
For more information, see the Security Services Installation/Customization

manual provided in PDF format on the Teamcenter documentation distribution
image.
2. If you are deploying the two-tier architecture:

a. Install Security Services on the Teamcenter corporate server, specifying the
Teamcenter application ID and the URLs of the Security Services Login
Service Web and Identity Service Web applications as determined in step 1.
For information, see Teamcenter server installation.
b. Create a two-tier Teamcenter rich client distribution instance, configuring

Security Services for the client by specifying the same Teamcenter
application ID, Security Services Login Service URL, and Identity Service

Web URL as specified when configuring Security Services on the corporate

server.
For information, see Install rich client distribution instances.
3. If you are deploying the four-tier architecture:

a. Configure the Web tier application to enable Security Services, specifying
the Teamcenter application ID and the URLs of the Security Services Login
Service and Identity Service Web applications as determined in step 1.
When you configure the Web tier application to enable Security Services, the
Teamcenter thin client is automatically configured to use Security Services.
For information, see J2EE Web tier installation.
b. If you are deploying the Teamcenter rich client, create a four-tier rich
client distribution instance, configuring Security Services for the client by
specifying the same Teamcenter application ID, Security Services logon
Service URL, and Identity Service Web URL as specified when configuring
Security Services for the Web tier.
For information, see Install rich client distribution instances.
Teamcenter online help installation

You can install Teamcenter online help on a Web server or in a directory on a network
file system to provide online help to Teamcenter rich client and thin client hosts.
For more information, see Installing Teamcenter online help.
Other considerations
Certain issues regarding distribution of database and license servers can affect
planning of your Teamcenter network.
Oracle server considerations

Determine whether to create a new Oracle database and/or upgrade existing Oracle
databases. You must install Oracle Server if a certified version is not installed on the
system. For certified versions of Oracle, see the Siemens PLM Software Certification
Database:
You can install Oracle from either of the following sources:
• Oracle CD-ROM supplied by Siemens PLM Software
• Oracle CD-ROM supplied by Oracle Corporation
You must create a database instance if one does not exist or if an additional database
instance is required (for example, to support testing, training, or RDV). If you are
installing RDV services, Siemens PLM Software recommends strongly that you
create a new database instance on an Oracle server with database partitions on a
separate disk drive. RDV requires extensive data warehousing with large uploads

Site planning
and simple queries. Such a configuration also makes the fine-tuning of the database
easier.
For information about installing Oracle Server, creating Oracle database instances,
and upgrading Oracle databases, see Oracle installation and configuration.
Note
QPL and a separate RDV database are not required if you use cacheless
search.
MS SQL server considerations

For certified versions of MS SQL Server, see the Siemens PLM Software Certification
Database:
When deploying MS SQL Server in a Teamcenter network:
• The Teamcenter corporate server must be installed on a Windows platform.
• Two-tier and four-tier rich clients can be installed on Windows platforms. Only
four-tier rich clients can be installed on UNIX platforms.
If you plan to implement a Teamcenter network incrementally at multiple sites,

consider configuring each site in a Multi-Site Collaboration environment with
separate hosts for the MS SQL database server (including Multi-Site Collaboration),
the rich client, the thin client, and volume servers, starting with the first phase. This
allows you to configure and manage the network consistently, as you scale it in each
phase. You can add CPUs, memory, and disks to the appropriate servers or deploy
additional servers as required, without moving or reconfiguring server processes on
different hosts or changing operational procedures.
For large or critical system implementations, consider implementing high-availability
systems with mirrored, dual-ported disk arrays. For a Teamcenter volume, consider
file servers with storage attached network (SAN) or network attached storage
(NAS) disk arrays.
To minimize system maintenance interruptions, consider separate file backup server
hosts to process metadata and volume data backups in realtime. While the primary
disk sets remain online, you can take secondary MS SQL Server and volume disk
sets offline simultaneously and back them up together (assuring MS SQL Server and
Teamcenter volume synchronization). When the backup is complete, you can return
the secondary disk sets online and resynchronize them with the primary disk sets.
The file backup servers also serve as fail-over machines.
For information about installing SQL Server and creating SQL Server database
instances, see Microsoft SQL Server installation and configuration.
Network environment considerations

You can implement Teamcenter in a homogeneous network environment or a
heterogeneous network environment.

Homogeneous network environment

In a homogeneous environment, the database server, Teamcenter corporate server,
and Teamcenter clients are all Microsoft Windows nodes provided by supported
vendors (for example, Dell, Hewlett-Packard, IBM, and so forth).
When deploying the two-tier architecture, you can install Teamcenter application
executable files on a single application server host, export the Teamcenter
application root directory structure from the Teamcenter application server, and
mount it using CIFS on client workstations to run Teamcenter locally. Typically, the
Teamcenter application server is also the Teamcenter data server. Similarly, you can
export the data directory structure and mount it using CIFS to other Teamcenter
clients to provide access to the database-specific information.
Heterogeneous network environment

In a heterogeneous environment, the database server, Teamcenter application server,
Teamcenter data server, and Teamcenter clients are provided by multiple vendors
and can be a mixture of UNIX and Microsoft Windows nodes.
Installation considerations for a heterogeneous environment are the same as for
a homogeneous environment, except that you must install Teamcenter for each
type of workstation on the network, resulting in a Teamcenter application directory
structure for each different type of workstation. You can configure one Teamcenter
application server to serve many Teamcenter directory structures for different
platforms.
Teamcenter volume data must be accessible by all Teamcenter clients in a
heterogeneous network. For clients that do not use File Management System, you
can usually share volume data using NFS and CIFS. When all clients use File
Management System, do not share the volume. Instead, configure File Management
System for volume access for all clients. For more information, see File Management
System installation.
Note
• The Teamcenter root directory is platform-specific. The files within it
can be shared only between systems of the same platform type. For
heterogeneous Teamcenter environments that include Windows clients or
Windows volume servers, configure File Management System to allow all
clients to communicate with all volume servers.
The Teamcenter root directory is specific to Windows or UNIX systems
(endian-specific). Maintain separate Teamcenter data directories on
Windows and UNIX systems.
• Teamcenter servers and two-tier rich clients on UNIX or Linux hosts

cannot connect to Microsoft SQL Server database servers. Keep this in
mind when planning database access in a heterogeneous network.
Required operating system and user accounts

Teamcenter uses the following user accounts for installation and maintenance:
• Operating system logon account

Site planning
You must create a logon account for the operating system before installation.
This account can have any name. This account does not represent a person: it
is a responsibility logon. log on with this account name to install or upgrade
Teamcenter or install patches.
This account must belong to the Administrators group and must be granted the
Log on as a service right.
• Teamcenter administrative user account

Teamcenter requires an administrative user account named infodba.
Teamcenter Environment Manager automatically creates this account when you
install Teamcenter on a server host. This account is used by the Teamcenter
administrator to access the Teamcenter system administration functions to
perform setup and maintenance tasks, such as creating Teamcenter users and
logons.
When you are populating a database during installation, you must use a
password of infodba for this account. After installation, change the infodba
password immediately.
Caution
o Never use the infodba user to create working data or initiate
workflow processes. This user ID has special behavior in the system:
using it to create data or initiate workflow processes can cause
unpredictable and undesirable behaviors.
If you require a user with high-level privileges to create data, create
a new user ID and add that user to the DBA group and other groups
as appropriate.
The infodba user is to be used only for the specific tasks and activities
described in the technical documentation for administrators.
o Make sure the password does not contain any of the following
characters:
@$%’": ;.<>(){}
In addition, Teamcenter requires a database user to be the owner of

Teamcenter-created tables and to perform tasks required by Teamcenter. You create
this database user either using the templates provided for Oracle databases or using
Teamcenter Environment Manager to install Teamcenter and populate a database.
Teamcenter Environment Manager refers to this user as DB user.
Note
Each user and group is identified by an alphanumeric name and an ID
number. The ID number is retained with the file information when a file
is exported across a network. If the ID numbers do not match for a user or
group, file access privileges may be unintentionally granted to the wrong user,
or not granted at all, on an NFS/CIFS client.

Part
II Database server installation
Teamcenter requires a supported relational database management system (RDBMS)

for storing Teamcenter data. Before you begin installing Teamcenter, you must
install and configure one of the following supported database systems:
• IBM DB2
• Oracle
• Microsoft SQL Server
Before proceeding with database server installation, make sure you are correctly
licensed through your database vendor for the database edition you install.
For information about database versions supported for use with Teamcenter, see the
Siemens PLM Software Certification Database:
Because Teamcenter can consume significant database resources, Siemens PLM
Software recommends that no other applications are served by the database server.
If other database applications must be served from the same host as Teamcenter,
there should be a dedicated database instance for Teamcenter. This allows the
designated instance to be tuned specifically for Teamcenter.

Chapter
3 IBM DB2 installation and

configuration
Install IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Install the DB2 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Register the DB2 server license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Install the DB2 redistributable client . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Set DB2 profile variables for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Create a DB2 sample database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Create a sample database using default sample tables . . . . . . . . . . . . . . . 3-5
Create a sample database using your own parameters and tables . . . . . . . 3-5
Verify connectivity with the sample database . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Create a DB2 database for Teamcenter . . . . . . . . . .. . . . . . . . . . . . . . . . . . . 3-6

Create a DB2 database for Teamcenter . . . . . . .. . . . . . . . . . . . . . . . . . . 3-6
Create a DB2 Teamcenter database . . . . . .. . . . . . . . . . . . . . . . . . . 3-6
Create a DB2 Teamcenter database user . . .. . . . . . . . . . . . . . . . . . . 3-7
Set DB2 database configuration parameters . . . . . . . . . . . . . . . . . . . 3-7
Archive DB2 database log files . . . . . . . . . .. . . . . . . . . . . . . . . . . . . 3-8

Chapter
3 IBM DB2 installation and

configuration
IBM DB2 installation and configuration

Install IBM DB2, verify installation and connectivity with a sample database, and
then configure a database for Teamcenter.
Before you begin installing DB2, make sure your host meets or exceeds the system
software and hardware requirements for DB2 servers and IBM data server clients
for your platform:
http://www-01.ibm.com/software/data/db2/9/sysreqs.html
For information about the IBM DB2 versions that Siemens PLM Software certifies
for use with Teamcenter, see the Siemens PLM Software Certification Database:
Note
If your Teamcenter database server is IBM DB2, all Teamcenter servers and
for Teamcenter with IBM DB2. IBM DB2 databases are supported only with
Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE Linux
platforms.
After you prepare your DB2 server host, install a Teamcenter-supported version
of IBM DB2.
Note
For more information about installing and using DB2 software, including the
DB2 Control Center, see the IBM DB2 Information Center:
http://publib.boulder.ibm.com/infocenter/db2luw/v9//index.jsp
Install IBM DB2

Install the DB2 server and configure it for Teamcenter.
Install the DB2 server

1. Prepare the software installation media:

Chapter 3 IBM DB2 installation and configuration
• If you use an IBM DB2 software CD or DVD, insert the disc.
• If you use downloaded images, download the appropriate DB2 image for your
platform from an IBM partner site such as the following:
http://www-01.ibm.com/software/data/db2/linux-unix-windows
Extract the image to a local directory.
2. In the IBM DB2 installation media, double-click the setup.exe program icon to
launch the IBM DB2 installation program.
3. In the DB2 Setup Launchpad dialog box, click Install a Product.
4. Under DB2 Enterprise Server Edition Version version, click Install New.
This launches the DB2 Setup - DB2 Enterprise Server Edition installation
wizard.
5. Proceed to the Software License Agreement dialog box. After you accept the
license terms, click Next.
6. In the Select the installation type dialog box, select the type of installation you
want to perform. The Typical option is sufficient for the Teamcenter server’s
needs.
7. In the Select the installation, response file creation, or both dialog box, select
the appropriate option. If you do not want to save your installation settings in
a response file, select the first option in the list (Install DB2 Enterprise Server
Edition on this computer).
8. In the Select the installation folder dialog box, enter an installation directory
or accept the default directory shown.
9. In the Set the DB2 copy name dialog box, accept the default value for DB2
copy name and make sure Set this as the default DB2 copy on my computer is
selected.
10. In the Set up a DB2 instance dialog box, click Create the default DB2 instance.
11. In the Set up partitioning options for the default DB2 instance dialog box,
click Single partition instance.
12. In the Configure DB2 instances dialog box, accept the existing values shown.
13. In the Set user information for the default DB2 instance dialog box, type and
confirm the password for the database user account.
Accept the default database user name shown. If multiple domains are available,
select the appropriate domain in the Domain list. Otherwise, accept the default
setting.
Make sure Use the same user name and password for the remaining DB2
instances is selected.

Note
IBM DB2 creates the following users and groups automatically during
installation:
Groups: db2admns, db2users
Users: db2admin
DB2 uses the operating system’s native user authentication.
14. In the Prepare the DB2 tools catalog dialog box, clear the Prepare the DB2
tools catalog check box.
15. In the Set up notifications dialog box, clear the Set up your DB2 server to send
notifications check box.
16. In the Enable operating system security for DB2 objects dialog box, accept the
default values shown.
If multiple domains are available, select the appropriate domain for the DB2
users group. Otherwise, accept the default setting.
17. In the Start copying files dialog box, click Install to begin installing the DB2
server.
18. When the DB2 installation program displays the Setup is complete dialog box,
click Next.
19. In the Install additional products dialog box, click Finish.
20. Install the IBM DB2 redistributable run-time client on all Teamcenter two-tier
rich client hosts.
For more information, see Install the DB2 redistributable client.
Register the DB2 server license

1. Choose Start→All Programs→IBM DB2→instance-name→General
Administration Tools→License Center.
This launches the DB2 License Center.
2. In the License Center, select your system name from the System name list. In
the Installed products list, select DB2 Enterprise Server Edition.
3. Choose License→Add.
4. In the Add License dialog box, browse to the location of your DB2 license file.
The default license file is DB2-image\db2\license\db2ese.lic. Replace
DB2-image with the path to your IBM DB2 installation media.
5. Select the license file and click Apply to add the license key.
The License Center displays a message confirming registration of your DB2
license.

6. Click Close.
7. Close the License Center.
Note
Alternatively, you can register your DB2 license by opening a DB2 command
prompt (Start→All Programs→IBM DB2→instance-name→Command Line
Tools→Command Window) and entering the following command:
db2licm —a license-file
Replace license-file with the path to your DB2 license file.

The default license file is DB2-image\db2\license\db2ese.lic.
Install the DB2 redistributable client

The Teamcenter server depends on the IBM DB2 open database connectivity (ODBC)
and call-level interface (CLI) drivers.
To install these drivers, browse to the additional_applications\db2_files
directory in the Teamcenter 9.1 software distribution image and double-click the
setup_DSDRIVER.exe program icon. Proceed through the installation wizard,
accepting the default settings.
The installation wizard installs the ODBC, CLI, and .NET drivers.
Note
• The DB2 ODBC and CLI drivers are required on Teamcenter servers and
two-tier rich client hosts.
• Installation of these drivers requires Windows administrative privileges.

If you want to install a Teamcenter two tier rich client without
administrative privileges, you must install and register the DB2
redistributable client before you install Teamcenter.
Set DB2 profile variables for Teamcenter

1. Open a command prompt, change to the DB2–home\sqllib\bin directory, and
type the following command:
db2set DB2_SNAPSHOT_NOAUTH=on
Note
This command is necessary to enable TEM to install Teamcenter with a
DB2 database.
2. Restart the DB2 server.

For more information, see the System Administration Guide.

Create a DB2 sample database

To verify the installation of the DB2 server, create a sample database you can use
to verify database connectivity.
Note
The sample database is for testing and verification only. It cannot be used by
Teamcenter.
Using the DB2 First Steps application, create the sample database by one of the
following methods:
• Using default sample tables
• Using your own parameters and tables
Create a sample database using default sample tables

1. Launch the DB2 First Steps application:
Start→Programs→IBM DB2→DB2-copy-nameSet-up Tools→First Steps
Note
The DB2 First Steps application requires a Web browser. Make sure a
Teamcenter-supported version of Mozilla Firefox or Microsoft Internet
Explorer is installed on the DB2 server host.
2. In the DB2 First Steps application, in the options on the left side, click Database
Creation.
3. In the Database Creation dialog box, click Create SAMPLE Database.

This launches the Create SAMPLE Database wizard.
4. In the Create SAMPLE Database dialog box, click SQL objects and data only.
(This is the default option.)
Click OK.
The wizard creates the sample database.
5. When database creation is complete, click OK to close the wizard.
Create a sample database using your own parameters and tables

1. In the DB2 First Steps application, in the options on the left side, click Database
Creation.
2. In the Database Creation dialog box, click Create your own Database.
This launches the Create Your Own Database wizard.
3. In the Specify a name for your new database dialog box, click option.
4. In the Specify where to store your data dialog box, enter one or more storage
paths for the database, or accept the default location shown.

5. In the Select your maintenance strategy dialog box, choose whether you want to
specify a time period for database maintenance. This is optional and does not
directly affect Teamcenter operation.
6. In the Provide a valid SMTP server dialog box, click Next. No options in this
dialog box are required for Teamcenter.
7. In the Review the actions that will take place when you click Finish dialog
box, click Finish.
The wizard creates the database.
Verify connectivity with the sample database

1. In the DB2 First Steps application, click Database Administration, and then
click Basic administration tasks.
2. In the Basic administration tasks dialog window, click Start DB2 Control Center.
This launches the DB2 Control Center.
3. When the Control Center prompts you to choose a view, click Advanced.
4. In the Control Center tree (under Object View), expand All Databases.
5. In the All Databases branch, expand SAMPLE.

If DB2 displays database objects, access to the database is verified.
6. Close the DB2 Control Center.
7. Close the DB2 First Steps application.
After you verify DB2 database connectivity, you can remove the sample database
to free disk space. However, if you use the sample applications, keep the sample
database.
Create a DB2 database for Teamcenter
Create a DB2 database for Teamcenter

Before you install the Teamcenter server, create a DB2 database for Teamcenter
using the CREATE DB command.
Create a DB2 Teamcenter database

1. Open a DB2 command prompt:
db2cmd
2. Launch the DB2 command line tool:

db2

3. Start the DB2 server:

start database manager
4. Exit the command line tool:

quit
5. Enter the following command to create a database:

CREATE DB db-name AUTOMATIC STORAGE YES ON ’path’ USING CODESET
UTF-8 TERRITORY US PAGESIZE 32 K
Replace db-name with the name or alias of the database to be created. Replace
path with the path or drive on which to create the database. This is also the
storage path or drive associated with the database.
For example:
CREATE DB tcdb2 AUTOMATIC STORAGE YES ON ’D:’ USING CODESET

UTF-8 TERRITORY US PAGESIZE 32 K
Note
To specify a path rather than a drive for database storage (for example,
D:\temp instead of D:), set the DB2_CREATE_DB_ON_PATH DB2
registry variable to YES. Otherwise, the database creation fails.
This setting affects the DB2 server, not the Teamcenter database.
Create a DB2 Teamcenter database user
DB2 uses the underlying operating system security to manage user IDs and
passwords. The Teamcenter database user and password must be established at
the operating system level. For information about creating a DB2 user, see the
DB2 documentation from IBM.
Set DB2 database configuration parameters
Optionally, set DB2 database configuration parameters for Teamcenter. Siemens

PLM Software recommends setting the following parameters for each database in
the instance on which you run your Teamcenter application. For other parameters,
accept the default settings.
Parameter Description Value

STMTHEAP Statement heap 100000
APPLHEAPSZ Default application heap 16000
LOGBUFSZ Log buffer size 512
LOGPRIMARY Number of primary log files 20
LOGSECOND Number of secondary log files 5
LOGFILSIZ Log file size 4096
UTIL_HEAP_SZ Maximum memory for utilities 150000

Database configuration parameters can be set using the DB2 Control Center or the
update database configuration command in the DB2 command line processor.
For example:
UPDATE DB CFG FOR db-name USING STMTHEAP 100000
After you change database configuration parameters, enter a DB2 TERMINATE

command to ensure the changes take effect.
For more information on modifying configuration parameters, see the IBM DB2
technical documentation.
Archive DB2 database log files
Optionally, you may archive DB2 database log files by setting the LOGRETAIN
and USEREXIT database parameters.
The LOGRETAIN database parameter is not enabled by default, and its behavior
is affected by the value of the USEREXIT parameter.
Set USEREXIT to one of the following values:
ON Enables the user exit program to archive log files when

they are full, and also to retrieve log files when roll
forward operations are used to restore a database.
OFF Disables archiving via the user exit program.
Set LOGRETAIN to one of the following values:
NO Specifies log files are not retained. The database manager

deletes log files in the log path directory and creates new
log files.
If USEREXIT is set to OFF, you can perform only
backup (restore) recovery, not roll forward recovery. This
may affect your data recovery process for your production
environment database.
The default value is NO.
RECOVERY Specifies all log files are kept on the system for the
database administrator to archive or delete.
Make sure your database administrator reviews the settings for the LOGRETAIN
and USEREXIT parameters.
For more information about these parameters, see the IBM documentation.
After you complete configuring your database, you can install a Teamcenter server
using Teamcenter Environment Manager (TEM). During installation, TEM creates
database objects and populates Teamcenter data.

Chapter
4 Oracle installation and

configuration
Upgrade Oracle server and databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Export Oracle databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Terminate Oracle sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Stop the listener process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Shut down an Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Shut down Oracle using Windows Control Panel . . . . . . . . . . . . . . 4-2
Shut down Oracle using SQL*Plus . . . . . . . . . . . . . . . . . . . . . . . 4-3
Back up an Oracle installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Upgrading the Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Upgrade using the Oracle installer . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Upgrade by uninstalling/reinstalling Oracle . . . . . . . . . . . . . . . . . . . 4-4
Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Configure Oracle Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Configure Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Configure an Oracle database for Teamcenter . . . . . . . . . . .... . . . . . . . . . . 4-7

Choose how to create the database . . . . . . . . . . . . . . . .... . . . . . . . . . . 4-7
Create a general purpose database . . . . . . . . . . . . . . . .... . . . . . . . . . . 4-7
Create a database instance using Teamcenter templates ... . . . . . . . . . . 4-8

Chapter
4 Oracle installation and

configuration
Oracle installation and configuration

Your Oracle database server must be a version certified for Teamcenter 9.1. For
information about the Oracle versions that Siemens PLM Software certifies for use
with Teamcenter 9.1, Oracle disk space requirements, and operating system and
service patch requirements, see the Siemens PLM Software Certification Database:
Perform the following tasks to prepare an Oracle database server and configure an
Oracle database for Teamcenter:
1. Choose a name for the Teamcenter user account. Teamcenter uses this account
as the owner of all Teamcenter-created tables. This account is used by the
database administrator to perform tasks required by Teamcenter.
Tip
If you use the Siemens PLM Software-supplied templates to create the
Teamcenter database, the name and password of the account is infodba.
2. If you do not have a certified version of Oracle, install or upgrade Oracle:

• If you do not have an Oracle server installed, install a certified version of
Oracle.
For more information, see Install Oracle server.
• If you have an Oracle server installed, but it is not a version certified for
Teamcenter 9.1, upgrade your Oracle server. For more information, see
Upgrade Oracle server and databases.
3. Configure Oracle software for Teamcenter.

For more information, see Configuring Oracle software.
4. Create a database for Teamcenter. For more information, see Configure an

Oracle database for Teamcenter.

Chapter 4 Oracle installation and configuration
Upgrade Oracle server and databases

Back up your Oracle database, install a certified Oracle version, and upgrade your
databases.
Export Oracle databases

1. Log on to the Oracle server as an administrator user.
2. Export the contents of your Teamcenter Oracle database to the dump file:
ORACLE_HOME\bin\exp db-user/password full=y
file=file-name.dmp log=export.log
Replace db-user with the Teamcenter database user account name; replace
password with the database user account password; replace file-name with the
full path and name of the dump file to contain the exported data; replace export
with the name of the log file to contain export output.
3. Store the dump file in a safe place.

Caution
Siemens PLM Software strongly recommends backing up the dump file on
tape or another disk. If the dump file becomes corrupted or lost, all data from
the existing database is lost.
Terminate Oracle sessions

If you are upgrading an Oracle installation on your Windows database server,
terminate all Oracle sessions and Oracle processes prior to installation.
Stop the listener process

1. Log on to the operating system as a user with administrator privileges.
2. Open the Services dialog box in the Windows Control Panel.
3. Select the Oracle TNS listener services (Oraclerelease-IDTNSListener) and

click Stop.
Shut down an Oracle database

You can shut down an Oracle database using either the Windows Control Panel
or the Oracle SQL*Plus utility.
Shut down Oracle using Windows Control Panel

2. Open the Services dialog box in the Windows Control Panel.

Windows displays the Services window.
3. Select the OracleServiceSID service.

Replace SID with the system identifier of the database instance.

4. Click Stop.
Shut down Oracle using SQL*Plus

2. Start the Oracle SQL*Plus utility:

sqlplus sys/password@Oracle—SID as sysdba
Replace password with the password for the sys user account.
Oracle starts the Oracle SQL*Plus utility.
Note
The sys user must be in the Oracle sysdba group for the Oracle system
identifier (SID) used by Teamcenter. To connect as internal (without a
password), the account must be part of the ORA_DBA local group in
Windows.
3. Shut down the database instance by typing the following command:

shutdown
4. Exit SQL*Plus:
exit
Back up an Oracle installation

If you are upgrading to the certified Oracle version, back up the existing Oracle
installation.
Back up the following files and directories:
• The Oracle home directory on each installed workstation.
• The directories containing database files for each configured database.
• The Oracle Net listener.ora and tnsnames.ora configuration files.

Note
These are the only Teamcenter directories affected by Oracle installation.
If you created other directories containing data used by Oracle, such as an
administration script directory, Siemens PLM Software recommends that
you also back up these directories.
Upgrading the Oracle server

You can upgrade your Oracle server and databases two ways:
• Using the Oracle installer to upgrade the server and databases
• Uninstalling all Oracle server software, installing a certified version of Oracle,

and importing existing databases from a dump file

Upgrade using the Oracle installer

1. Launch the Oracle installer to install a certified version of Oracle server.
2. When the Oracle installer prompts you to upgrade existing databases, enter the
required information about the databases you want to upgrade.
Upgrade by uninstalling/reinstalling Oracle

1. Remove existing Oracle databases.
2. Uninstall all existing Oracle server software.
3. Install a certified version of Oracle server.

4. After Oracle installation is complete, import your Oracle dump file into the
new Oracle database.
Install Oracle server

You can install Oracle from the Oracle software distribution images supplied by
Siemens PLM Software or Oracle Corporation.
If you install Oracle from a hard disk, copy the entire contents of the Oracle DVD
to the hard disk.
You can install Oracle application files on shared directories. However, Oracle
Corporation does not support Oracle database files on shared directories. To ensure
data integrity, create database files on local disk drives.
1. Log on to the server host as a member of the Administrators group. If you are
installing on a primary domain controller (PDC) or a backup domain controller
(BDC), log on as a member of the Domain Administrator group.
Note
The operating system user account under which you install the Oracle
database server must have system administrator privileges.
Siemens PLM Software recommends you create a system user account
named oracle to use during Oracle installation. When you use the oracle
account to install Oracle, this account is automatically added to the
Windows ORA_DBA local group, giving it SYSDBA privileges.
2. Record the name of the Oracle database server host. Teamcenter Environment
Manager requires this name during corporate server installation.
3. Insert the Oracle RDBMS installation DVD.

The system displays the Autorun dialog box.
4. In the Configure Security Updates dialog box:

a. If you want to receive e-mails from Oracle Corporation regarding security

issues, enter your e-mail address in the Email box.
b. If you want to be informed about security issues using your My Oracle

Support account, select I wish to receive security updates via My Oracle
Support and enter your password.
5. In the Select Installation Options dialog box, select Install database software
only, and then click Next.
6. In the Grid Installation Options dialog box, select Single instance installation,
and then click Next.
7. In the Select Product Languages dialog box, select the languages to run, and
then click Next.
8. In the Select Database Edition dialog box, select the database edition to install,
Note
Teamcenter supports Enterprise Edition and Standard Edition.
9. In the Specify Installation Location dialog box, specify:

• Oracle Base
Specifies the path in which to install all Oracle software and configuration
files.
• Software Location
Specifies the path in which to install Oracle software files. This is the Oracle
home directory.
Note
Do not install Oracle 11g or later into an existing Oracle home directory
that contains Oracle 10g or earlier software.
10. In the Summary dialog box, review the information to ensure you have sufficient
disk space, and then click Finish.
11. When the Finish dialog box displays the The installation of Oracle Database
was successful message, click Close to complete the installation.
Configuring Oracle software

Configure Oracle server processes and Oracle Net.
Configure Oracle Net

Teamcenter uses Oracle Net protocols to communicate with an Oracle database.
These protocols require that a listener process (OracleTNSListener) run on the

Oracle server to listen for remote connect requests and that all clients can translate
the service alias identifying the server and database.
For more information, see the System Administration Guide.
Configure Oracle server

1. Start Oracle Net Manager chose Start®All Programs®Oracle -
OraDb11g_home1®Configuration and Migration Tools®Net Manager.
2. Create the listener.ora file:

a. Expand the Local icon.
b. Select the Listeners folder and choose Edit®Create.
c. Accept the default listener name (LISTENER) and click OK.
d. Click the Add Address button.
e. Specify the port number.

Note
For the first listener, Siemens PLM Software recommends accepting
the default port number (1521).
Tip
Record the number of the port used by the Oracle database server
listener for entry during corporate server installation. Teamcenter
Environment Manager requires this port number.
f. In the Local tree, click Profile.
g. In the Naming list (to the right of the Oracle Net Configuration tree), choose
General.
h. Click the Advanced tab.
i. In the TNS Time Out Value box, type 10.

Note
This step sets the Oracle server-side SQLNET.EXPIRE_TIME
parameter. This value determines how often the Oracle server
checks for aborted client connections. Teamcenter requires that this
parameter be set to a nonzero value, and the recommended value
is 10 (10 minutes).
j. Save the listener information, choose File®Save Network Configuration.

Oracle Net Manager saves the listener information and creates the
network\admin\listener.ora and network\admin\sqlnet.ora files in
the Oracle home directory.
3. Exit Oracle Net Manager, choose File®Exit.

4. In a command prompt, create and start the listener service:

cd ORACLE_HOME\bin
lsnrctl start LISTENER
Replace ORACLE_HOME with the path to the directory where you installed the
Oracle server, for example, d:\app\infodba\product\11.2.0\dbhome_1.
This command creates and starts the service if it does not exist. If the service
exists, the command starts it.
Configure an Oracle database for Teamcenter

Create and configure databases for Teamcenter.
Choose how to create the database

Siemens PLM Software provides two methods for creating a Teamcenter database
configured with required user accounts and tablespaces:
• Create a database instance using Siemens PLM Software-provided templates
with Oracle DBCA. The templates populate the database with the required
Oracle user accounts and tablespaces.
Tip
o The templates create a single database user (infodba) per Oracle
system identifier (SID).
o For best performance and reliability, database parameters set by

Teamcenter templates should be customized to suit your installation.
This can be performed by your Oracle administrator after Teamcenter
installation is complete.
• Create a multipurpose Oracle database instance manually using Oracle

Database Configuration Assistant (DBCA). Then use Teamcenter Environment
Manager to configure the database and populate it with the Oracle user accounts
and required table spaces.
Tip
An advantage to creating a multipurpose database instance is that you
can create multiple Teamcenter databases using a single Oracle SID,
simplifying administration.
Create a general purpose database

Note
Teamcenter Environment Manager (TEM) verifies your Oracle version during
installation. If your Oracle server does not meet the minimum required
version, TEM does not allow installation to proceed. For information about
supported database servers for Teamcenter 9.1, see the Siemens PLM
Software Certification Database:

1. Create a general purpose database using Oracle DBCA. Select the General
Purpose or Transaction Processing template when creating the database.
For information, see the Oracle documentation.
Tip
Record the following information that you must provide when installing
the Teamcenter corporate server:
• Password of the database system user
• Absolute path to the tablespace directory on the database server host.

This is the path on the Oracle server where data files are stored.
2. Install a Teamcenter corporate server using Teamcenter Environment Manager

as described in Teamcenter server installation. To configure a database during
the installation:
a. Choose to install the Teamcenter Foundation component.
b. Choose to create a data directory.

When you create a data directory, you also provide information about the
database to use with this installation. When you specify a new database,
Teamcenter Environment Manager populates the database and creates a
volume.
Create a database instance using Teamcenter templates

Note
Make sure you have access to the Teamcenter software distribution image.
1. Log on to the Oracle server host as a user who is a member of the ORA_DBA
group. This may be the user who installed Oracle on the server host or one
assigned to ORA_DBA by a member of the ORA_DBA group.
2. Copy the Siemens PLM Software-supplied Oracle database template files:

a. Access the Teamcenter software distribution image.
b. Copy all files in the tc\dbscripts\oracle directory on the Teamcenter

software distribution image to the templates directory of the Oracle
installation. For example:
copy e:\tc\db_scripts\oracle\* ORACLE_HOME\assistants\dbca\templates
3. Start Oracle Database Configuration Assistant (DBCA):

Start→Programs→Oracle – Home0→Configuration And Migration Tools→
Database Configuration Assistant
4. In the Welcome dialog box, click Next.
5. In the Operations dialog box, select Create a database and click Next.

6. In the Database Templates dialog box, select the appropriate template (for
Oracle 11g) and click Next.
7. In the Database Identification dialog box, either accept the default database
name in the Global Database Name box or type a different name and click Next.
Note
The SID box is automatically filled in with the name you enter in the
Global Database Name box.
Tip
Record the SID of the Oracle instance for entry during corporate server
installation. Teamcenter Environment Manager requires this name.
8. In the Management Options dialog box, click Next.
9. In the Database Credentials dialog box, select Use the Same Password for All
Accounts, enter and confirm the password for the SYS, SYSTEM, DBSMNP,
and SYSMAN accounts, and click Next.
10. In the Storage Options dialog box, select File System and click Next.
11. In the Database File Locations dialog box, select Use Database File Locations
from Template and click Next.
12. In the Recovery Configuration dialog box, select Specify Flash Recovery Area
and click Next.
13. In the Database Content dialog box, click Next.
14. In the Initialization Parameters dialog box, click Next.
15. In the Database Storage dialog box, click Next.
16. In the Create Options dialog box, select Create Database and click Finish.
17. In the Confirmation dialog box, click OK to start creating the database.
When the database is created, DBCA displays a window containing information
about the created database.
18. Click Exit.
After the database is created, check for possible errors in the installation log files.
The Oracle DBCA displays the directory location of the installation log files in the
window that contains information about the created database after the database is
created.

Note
• Review the customScripts.log file carefully. This log file is the output
from running the custom Teamcenter steps.
• The database creation process creates Teamcenter objects (for example, the
database user account, default tablespaces, and create log tables/indexes)
by executing the Siemens PLM Software-supplied script in the Oracle
home directory:
\assistants\dbca\templates\tc_create_user_ilog.sql
If this script did not execute successfully, execute it again using the Oracle
SQL*Plus utility. Log on to SQL*Plus as sysdba.

Chapter
5 Microsoft SQL Server installation

and configuration
Install MS SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Create an SQL Server database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Chapter
5 Microsoft SQL Server installation

and configuration
Microsoft SQL Server installation and configuration

Install Microsoft SQL Server and configure a database for Teamcenter.
Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannot connect
to Microsoft SQL Server database servers.
For information about the SQL Server versions that Siemens PLM Software certifies
for use with Teamcenter, see the Siemens PLM Software certification database:
Install MS SQL Server

1. Log on to an account with system administrator privileges.
2. Launch the Microsoft SQL Server installation wizard and proceed through the
dialog boxes regarding licensing, prerequisites, registration information, and
so on.
3. In the Components to Install dialog box, select the following components:

SQL Server Database Services
Workstation components, Books Online and development tools
4. In the Instance Name dialog box, choose an instance type. Teamcenter supports
both Default Instance and Named Instance.1
1. If you choose Named Instance, make sure you start the SQL Browser service before connecting to the database. If this service is not
enabled, you can change these settings using the SQL Server Configuration Manager after installation is complete.

Chapter 5 Microsoft SQL Server installation and configuration
Note
A default instance in a Microsoft SQL Server installation uses the
name MSSQLSERVER. Teamcenter’s persistent object manager (POM)
utilities cannot connect to an instance with this name. If you use a default
instance, make sure you connect to the instance using a port connection
rather than the name.
If you use a named instance, make sure the instance has a unique name
other than MSSQLSERVER.
5. In the Service Account dialog box, enter the following settings:

• Make sure the Customize for each service account check box is cleared.
• Choose Use the built-in System account and select Local system in the
associated list.
• Under Start services at the end of setup, select SQL Server.
6. In the Authentication Mode dialog box, choose Mixed Mode and define a
password for the SQL Server sa logon account.
7. In the Collation Settings dialog box, enter the following settings:

• Choose Collation designator and sort order.
• Select Latin1_General from the list.
• Select Binary.
8. Proceed to the Ready to Install dialog box and click Install.
Create an SQL Server database

Teamcenter Environment Manager (TEM) can create and populate a SQL Server
database when you install a Teamcenter corporate server.2 If you want TEM to
create your Teamcenter database automatically, skip this topic. Otherwise, create
your Teamcenter database using the SQL Server Management Studio.
1. Make sure you have access to the Teamcenter software distribution image.
2. Launch the Microsoft SQL Server Management Studio:

Start→Programs→Microsoft SQL Server 2005→SQL Server Management Studio
3. In the SQL Connect to Server dialog box, log on using the system administrator
(sa) logon name and password.
4. Choose File→Open→File or press Control+O.
2. In the Database Engine Selection panel, TEM prompts you for database information for the SQL Server database. To create a
new database, enter new values. To connect to an existing database, enter values for the existing database. For information about
installing a corporate server, see Teamcenter server installation.

Microsoft SQL Server installation and configuration
5. Browse to the tc\db_scripts\mssql\2005 directory in the Teamcenter 9.1 software

distribution image.
6. Select the create_database.sql file and click Open.

If SQL Server Management Studio prompts you to log on, enter the system
administrator (sa) logon name and password.
7. If you want to customize how the Teamcenter database is created, edit the
database template (create_database.sql).
For example, if you want to change the database name, replace all instances of
the default database name (TcEng) in the template with the name you want
to use. The following table describes other editable database parameters in
the template.
Parameter Default value Description

Logon infodba Database logon name for the Teamcenter
name database.
Logon infodba Password for the database logon name.
password
Note
Do not globally replace instances of
infodba in the template because the
default logon name and password both
use this value. Make sure you identify
the instances that specify the database
password.
8. Click Execute to begin creating the database.
9. When creation of the MS SQL database instance is complete, verify the newly
created database. In the Object Explorer pane, under the MS SQL Server host
name, expand the Databases tree. Verify the new database name is included in
the list of databases.

Part
III Teamcenter server installation
Prepare the Teamcenter server host, install the corporate server, then perform any
required postinstallation tasks.

Chapter
6 Teamcenter preinstallation tasks
Install the licensing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Select destination directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Install a volume server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Install NX and Teamcenter Integration for NX or NX Integration . . . . . . . . . . 6-4
Best installation practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Chapter
6 Teamcenter preinstallation tasks
Teamcenter preinstallation tasks

Perform the appropriate procedures to prepare your Teamcenter server host.
Install the licensing server

Before you install Teamcenter, you must install the Siemens PLM Software Common
Licensing Server to distribute licenses to Teamcenter hosts.
Teamcenter employs named user licensing, which ties each user in the system to an
available license and ensures the total number of active licenses of each type in the
system is always less than or equal to the number of licenses purchased.
For descriptions of the available license types, see your license agreement
documentation.
Install the ugslmd license daemon:
1. Obtain a Teamcenter 9.1 license file from Siemens PLM Software. Save the
license file in a directory accessible to the license server host. This procedure
assumes the license file is named tc.lic, but you may give the license file any
name you choose.
2. Open the license file in a plain text editor and locate the following line in the file:
SERVER YourHostname ANY 28000
3. Replace YourHostname with the host name of the designated license server
host. Update your Siemens PLM Software customer service representative with
your license server host information.
Note
• Siemens PLM Software recommends you do not change the license
server port from its default value (280001) unless it is necessary to
resolve a port conflict.
• Keep note of the host name and port for the license server. Teamcenter
Environment Manager (TEM) prompts you for these values during
Teamcenter server installation.
1. Port 28000 is registered for the Common Licensing Server with the Internet Assigned Numbers Authority (IANA). For more
information, see http://www.iana.org/assignments/port-numbers.

Chapter 6 Teamcenter preinstallation tasks
4. Save the changes to the license file.
5. Set the UGS_LICENSE_SERVER environment variable to the following value:

port@host
Replace port with the port number and host with the host name of the license
server, for example, 28000@tchost. The port and host values must match those
you specified in the SERVER line of the Teamcenter license file.
6. Set the TCP_NODELAY environment variable to 1. This helps optimize logon

time when launching Teamcenter.
7. Extract the Siemens PLM Software Common License Server software:

a. Browse to the additional_applications\ugslicensing directory in the
Teamcenter software distribution image.
b. Extract the contents of the ugslicensing.zip archive to a temporary

directory on your hard drive.
8. Launch the Siemens PLM Software Common License Server installation

program:
a. Browse to the directory in which you extracted the ugslicensing.zip archive.
b. Launch the setup.exe program to install the Common Licensing Server.
c. During license server installation, enter the following values:

• Destination location for the license server
• Location of the Teamcenter license file (tc.lic)
When the installation is complete, the license server installation program

starts the license daemon (ugslmd).
Caution
The Siemens PLM Software Common License Server must be running
and two or more seats must be available on that license server during
Teamcenter server installation. Otherwise, database creation fails because
the make_user utility cannot create the required users in the database.
For more information, see the Installing Siemens PLM Software Licensing for
UNIX, Installing Siemens PLM Software Licensing for Windows, and Siemens PLM
Common Licensing User Guide documents in the additional_documentation
directory on the Teamcenter 9.1 documentation distribution image.
Select destination directories

Select destination directories for Teamcenter using the following guidelines:
• Ensure that all directories and files are owned and writable by the operating
system user installing Teamcenter over an existing installation.

• If your Teamcenter installation directory is on a mapped drive or a UNC path

(not on the local host) you must be logged on as an authenticated domain
user to ensure the remote host recognizes you. Alternatively, you can set the
permissions on the remote host to allow an anonymous user to access it. This is
necessary to ensure Teamcenter services such as the FMS server cache (FSC)
and Multi-Site Collaboration services can start.
Note
Siemens PLM Software requires that you store or create Teamcenter files on
NTFS partitions, not FAT partitions, to take advantage of the file security
features of NTFS.
Install a volume server

By default, you can create volumes only on local disks, but if you want to write files
to volumes residing on remote disks (shared across the network), you can create
a stand-alone volume server.
1. Log on to the operating system with the user account you want to own the
volume.
2. Start Teamcenter Environment Manager (TEM):

a. Browse to the root directory of the Teamcenter software distribution image.
b. Right-click the tem.bat program icon and choose Run as administrator.

Teamcenter Environment Manager starts and displays the Choose Install
Language dialog box.
c. Select a language for the installation program and click OK.

The language you select is used only for the installation program.
Teamcenter Environment Manager displays the Welcome to Teamcenter
panel.
3. Click Install.
4. Proceed to the Configuration panel.
5. Enter a unique ID and description for the new Teamcenter configuration.
6. Proceed to the Solutions panel. Select the Volume Server solution.

Note
For descriptions of solutions, point to the solution in the list or click Help
or see Solutions and features reference.
7. Proceed to the Features panel. This panel shows the FMS Server Cache feature
preselected by the Volume Server solution.
8. In the Installation Directory box, enter the absolute path to the directory where
you want to install the volume server.

Chapter 6 Teamcenter preinstallation tasks
9. Proceed to the Operating System User panel. Type the password for the
operating system account to which you logged on to install the volume server.
10. Proceed to the FSC Service panel. Enter required values for the FMS server
cache (FSC) service. For information about required values, click Help.
11. Proceed through the remaining panels, entering required values for the volume
server. For information about these panels, click Help.
12. Proceed to the Confirmation panel. Verify the information you entered. If you
want to change any values, click Back to return to the panels you want to change.
Otherwise, click Next to begin installing the volume server.
13. When installation is complete, close TEM.
Install NX and Teamcenter Integration for NX or NX Integration

Installing NX is not a prerequisite for installing or using Teamcenter. However,
if this is a new installation of both Teamcenter and NX, Siemens PLM Software
strongly recommends installing NX prior to installing Teamcenter.
When installing NX for use with Teamcenter, you must install the Teamcenter
Integration for NX or NX Integration executables. Although installed independently,
Teamcenter Integration for NX and NX Integration cannot be used until Teamcenter
is configured.
To use Teamcenter Integration for NX or NX Integration with Teamcenter, you
must install NX locally on every workstation. This is a requirement for Teamcenter
Integration for NX or NX Integration to function in a rich client local server
environment on Windows platforms.
Teamcenter Integration for NX and NX Integration provide the same NX user
interface and are both installed with NX.
For more information, see the NX Remote Manager Guide and also the installation
guides distributed with NX. Installing Teamcenter varies depending on whether you
have a license for NX Integration or Teamcenter Integration for NX.
Best installation practices

A Teamcenter network requires one corporate server configuration. Additional
servers are optional, but can help balance network loads and facilitate heterogeneous
networks (networks with hosts running different operating systems).
If you install the optional servers, Siemens PLM Software recommends installing
in the following order:
1. Perform a full installation of Teamcenter on a corporate server host.
The corporate server is a network node used as an application file server (from
the Teamcenter application root directory) and database-specific configuration
file server (from the Teamcenter data directory). Run Teamcenter Environment
Manager and install the Teamcenter executables and the directory containing
the database-specific configuration files. Teamcenter can also run locally on
this network node.

2. Optionally install additional Teamcenter servers to provide the following

capabilities:
• Run Teamcenter executables and point to the existing data directory on
the corporate server host or a another Teamcenter server. This server can
contain a Teamcenter application root directory structure on a network node
that may be configured to run Teamcenter in the future.
• Run Teamcenter Environment Manager and point to an existing database.

This server can contain a Teamcenter network node to be used as a
database-specific configuration file (Teamcenter data directory) server when
the Teamcenter application root directory is mapped from a Teamcenter
application server. Teamcenter can also be run locally on this system. You
are creating an additional Teamcenter database for use with an existing
Teamcenter application root directory.
Note
Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannot
connect to Microsoft SQL Server database servers. Keep this in mind when
planning database access in a heterogeneous network.

Chapter
7 Teamcenter server installation
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Install a Teamcenter corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Chapter
7 Teamcenter server installation
Teamcenter server installation

Teamcenter Environment Manager (TEM) installs the Teamcenter shared
executables and files and the Teamcenter data directory. TEM provides a wizard
interface that allows you to define a Teamcenter configuration, select features, and
enter the information needed to install the features you select.
Before you start

• Locate the Teamcenter software distribution image for your platform. If
you install Teamcenter online help, locate the Teamcenter documentation
distribution image.1
• On the local host, create the Teamcenter operating system user account.
Note
All Teamcenter services run as this user account. Ensure this account
belongs to the Administrators group and is granted the Log on as a
service right.
• Obtain the host name of the licensing server and the port number used for
licensing processes.
• Ensure that a database server is installed for Teamcenter and obtain the
following information from the database administrator:
o The type of database server used for this installation of Teamcenter.
o The following information about the database server:

Name of the host on which the database server runs.
Number of the port on which the database server listens.
For Oracle database servers, the service name of the Oracle instance.
Typically, the service name is the same as the SID.
For MS SQL database servers:
1. The Teamcenter documentation distribution image contains the tchelp.jar file needed by the online help feature.

Chapter 7 Teamcenter server installation
◊ Name of the database
◊ Name of a system data source (DSN) to be created by Teamcenter

Environment Manager
Whether you can create a database user or must use an existing

database user:
◊ If you can create a database user, obtain the following information
about the generic Oracle instance:
• Name of the database system user.
• Password for the database system user.
• Absolute path to the tablespace directory on the database server.
◊ If you must use an existing database user:

• Database user name
• Database user password
• Determine a parent directory to contain a Teamcenter volume or volumes.

This parent directory must exist before installation. Only the parent directory
should exist; the volume directory is created during installation.
Note
Siemens PLM Software recommends not defining the volume location
under the Teamcenter application root directory. Doing so leads to
complications when upgrading to a new version of Teamcenter.
• Select the features to install. Point to any feature to view a description.2
• Obtain the information required to install File Management System.
Note
• If you install File Management System, the FMS server cache (FSC) and
the server manager must run on the same host server, with the same
user ID.
• Teamcenter provides server managers based on the J2EE and the

Microsoft .NET platforms. Install the appropriate server manager for
the Web tier you use.
2. For further descriptions of server features, see Teamcenter features.

Data Description
Read cache directory and size? For FMS to operate correctly, the location you specify must
be on the local host.
If you are installing a volume on the host, FMS does not
use the read cache; Siemens PLM Software recommends
accepting the default cache size (10 megabytes). Do not
specify 0; specifying 0 creates a file cache with a default size
larger than 10 megabytes.
If you are not installing a volume on this host, FMS acts
as a cache server. In this case, Siemens PLM Software
recommends increasing the value to 1000 megabytes.
However, choose a size that represents the maximum size
of the data that must be processed. If you choose 1000
megabytes, and a user requests a 3 gigabyte assembly, the
request fails.
Write cache and size? This cache is required when the FSC acts as a cache server.
For FMS to operate correctly, the location you specify must
be on the local host.
If you are installing a volume on this host, FMS does not
use the write cache; Siemens PLM Software recommends
accepting the default cache size (10 megabytes). Do not
specify 0; specifying 0 creates a file cache with a default size
larger than 10 megabytes.
If you are not installing a volume on this host, FMS acts
as a cache server. In this case, Siemens PLM Software
recommends increasing the value to 512 megabytes or more.
However, choose a size that represents the maximum size of
the data that must be processed.
Communication mode between Either HTTP or HTTPS.
FMS components?
Configure proxy servers? Either HTTP proxy server or HTTPS proxy server.
If you choose to configure proxy servers, you must provide:
• The name of the host running the proxy server.
• The number of the port the proxy server listens on.

Is this host an FMS master? If you are installing only one FSC server in the network, it
must be the master host. Each Teamcenter network must
have at least one master configuration file and one FSC
designated to read this file.

Data Description
Add the URL of the local host This preference is used only by the Teamcenter thin client.
to the list of servers defined in
the Fms_BootStrap_Urls site When searching for an assigned FMS server cache to manage
preference? file downloads, thin clients contact FSC servers defined in
the Fms_BootStrap_Urls preference in the order they are
listed. The server responds with the FSC server assigned to
the thin client, and all subsequent communication is with
that assigned server cache.
If there is only the thin client and one FSC server in the
network, you must select this option. Each Teamcenter
network must have at least one server listed in the
Fms_BootStrap_Urls preference for thin client use. For
failover purposes, you can include multiple servers.
Default settings for the FCC? • Location of the cache directory for all Windows systems
and for all UNIX systems.
• Default maximum size in megabytes of whole files

downloaded from the volume to rich client hosts. Users
cannot download a file whose size exceeds the value you
set for this value. This default setting can be overridden
by the FMS client cache configuration file.
Choose a size large enough to accommodate the largest
whole file that users download from the volume. If the
user requests a 3-gigabyte assembly when the cache size
is set to 1000 megabytes, the request fails.
• Default maximum size in megabytes of whole files

uploaded to a volume from rich client hosts. Users cannot
upload a file whose size exceeds the value you set for this
value. This default setting can be overridden by the FMS
client cache configuration file.
Choose a size large enough to accommodate the largest
whole file that users upload to the volume.
• Default maximum size in megabytes of the segment file

cache used by the embedded viewer and the stand-alone
application viewer on rich client hosts.
This default setting can be overridden by the FMS client
cache configuration file.
o If no or few rich client users in the network deploy

Lifecycle Visualization, Siemens PLM Software
recommends setting this cache size to 10 megabytes.
Do not specify 0; specifying 0 creates a file cache with
a default size larger than 10 megabytes.
o If rich client users in the network deploy Lifecycle

Visualization, Siemens PLM Software recommends

Data Description
setting this cache size in the range of 2000 megabytes
to 4000 megabytes.
The cache size is initially small, expanding to the
maximum size only if a user launches Lifecycle
Visualization to view a file of that size. The initial
size of the cache is proportional to the value specify.
Install a Teamcenter corporate server

1. Log on to the operating system with the Teamcenter user account you created for
installing and maintaining the Teamcenter installation.

a. Browse to the root directory of the Teamcenter software distribution image.
b. Right-click the tem.bat program icon and choose Run as administrator.

TEM starts and displays the Installer Language dialog box.
c. In the Installer Language dialog box, select a language and click OK.
Your language selection applies only to the TEM session, not the Teamcenter
installation.
3. Proceed to the Welcome to Teamcenter panel. This panel contains the following
options:
• Install
Installs a new Teamcenter configuration using a fully configurable
installation process.
• Quick Preconfigured Install

Installs preconfigured corporate server and client configurations using a
simplified installation process.
For information about installing Teamcenter servers using quick
preconfigured install configurations, see Teamcenter Environment Manager
Help.
• Upgrade
Upgrades an existing Teamcenter configuration.
For information about upgrading, see the Upgrade Guide.
Click Install to begin installing a corporate server.

Note
For information about any TEM panel, click the help button .

Note
Alternatively, you can install a preconfigured corporate server by clicking
Quick Preconfigured Install and then selecting one of the corporate server
configurations.
For information about installing Teamcenter servers using quick
preconfigured install configurations, see Teamcenter Environment
Manager Help.
4. In the Configuration panel, type a unique ID and description for the new
Teamcenter configuration.
The configuration ID identifies your Teamcenter configuration when you
maintain, upgrade, uninstall, or add features to the configuration. Installation
log files are also named based on the ID you enter.
5. In the Solutions panel, select the Corporate Server solution.

For descriptions of solutions, point to the solution name or see Solutions and
features reference.
6. Proceed to the Features panel. This panel shows the corporate server features
preselected by the Corporate Server solution:
Teamcenter Foundation
FMS Server Cache
NX Integration
7. Select any additional features you want to include in your configuration.

For descriptions of features, point to the feature name or see Solutions and
features reference.
If you select additional features, TEM displays additional panels during
installation that are not described in this procedure.
For help with any panel in TEM, click the help button .
You can also add features to the corporate server later using TEM in
maintenance mode.
Note
• If you are deploying the J2EE Web tier or the .NET Web tier, select
the appropriate server manager feature, J2EE Based Server Manager
or .NET Based Server Manager (under Server Enhancements).
• If you want to install a custom solution, see Installing a custom

solution or third-party template.
• If you install Teamcenter Automotive Edition and GM Overlay with

the rich client, make sure you complete the required postinstallation
steps.
For more information, see the appropriate client installation guide (for
Windows or UNIX/Linux).

8. In the Installation Directory box, enter the path to a new directory where you
want to install Teamcenter.
Note
• The Teamcenter installation directory must not already exist on your
system. TEM creates the directory during installation.
• The Installation Directory value is the Teamcenter application root

directory stored in by the TC_ROOT environment variable.
Do not set TC_ROOT in the system environment. TEM sets this
variable as required in configuration files. Setting this variable
in the operating system can cause conflicts if you install multiple
Teamcenter configurations.
• If your Teamcenter installation directory is on a mapped drive or

a UNC path (not on the local host) you must be logged on as an
authenticated domain user to ensure the remote host recognizes you.
Alternatively, you can set the permissions on the remote host to
allow an anonymous user to access it. This is necessary to ensure
Teamcenter services such as the FMS server cache (FSC) and
Multi-Site Collaboration services can start.
9. In the File System Cache (FSC) panel, type a unique identifier and port for the
FMS server cache in the FSC ID and Port boxes.
A Teamcenter network must have at least one master FSC. If you want to
designate the current FSC as an FSC master, select the Enable configuration
master check box. Otherwise, type the URL to the parent FSC in the FSC
Parent URL box.
For advanced FSC configuration options, click Advanced.
10. In the Operating System User panel, type the password for the operating system
account under which you install Teamcenter.
11. In the Foundation panel, select how you want to create or designate the
Teamcenter database and Teamcenter data directory (TC_DATA).
Database Database TC_DATA

exists? populated? exists? Select this option
No N/A No Create and populate database, create
new data directory
No Teamcenter database or data
directory exists and you want TEM to
create both. This option is selected by
default.

Database Database TC_DATA

exists? populated? exists? Select this option
Yes No No Populate database, create new data
directory
A database exists but is not populated
with Teamcenter data. You want TEM
to populate the database and create a
new data directory.
Yes Yes No Create new data directory using
existing populated database
A database exists and is populated.
You want TEM to use this database
and create a new data directory.
Yes Yes Yes Use populated database and existing
data directory
A database exists and is populated, and
a data directory exists. You want TEM
to use both of these.
12. Enter the required values for your Teamcenter database according to your
selection in the Foundation panel.
• Create and populate database, create new data directory:
a. Proceed to the Foundation Database panel.
b. Select the appropriate database server vendor (IBM DB2, Oracle, or MS

SQL Server).
c. Enter the required values for the database server, the database user, and
the database administrator account.
• Populate database, create new data directory:


SQL Server).
c. Enter the required values for the database server and the database user.
• Create new data directory using existing populated database:


SQL Server).
c. Enter the required values for the database server and the database user.
• Use populated database and existing data directory:

No database information is required. Proceed to the Data Directory panel.

Note
For more information about database configuration values, click the help
button .
For Oracle and Microsoft SQL Server databases, the directory you specify
in the Database Path box must exist and you must have write permission
to the directory.
13. In the Data Directory box, enter a location for the Teamcenter data directory.
The Teamcenter data directory is called the TC_DATA directory. This value is
stored in the TC_DATA environment variable on your system. TEM creates
shared data subdirectories and files in this location. Each data directory is
associated with a single database user within a database instance.
Do not set TC_DATA in the system environment. TEM sets this variable as
required in various scripts. Setting this variable in the operating system can
cause conflicts if you install more than one configuration.
14. Proceed to the Volume Specification panel.

In the Name box, type a name for the Teamcenter volume you want TEM to
create.
In the Directory box, type the absolute path to the directory in which to create
the volume, or accept the default location.
Note
Siemens PLM Software recommends not defining the volume location
under the Teamcenter application root directory. Doing so leads to
complications when upgrading to a later version of Teamcenter.
15. Proceed to the Foundation panel.
Value Description
Transient Volume Directories Specifies transient volume locations for
Windows hosts, UNIX/Linux hosts, or both.
A transient volume is an operating system
directory controlled by Teamcenter and
used to store temporary data for transport
of reports, PLM XML data, and other
nonvolume data between the enterprise
tier and client tier in a deployed four-tier
architecture. All four-tier clients that
access the corporate server you are
installing use this transient volume.
For more information about transient
volumes, see the System Administration
Guide.
Windows clients Specifies the location for a transient
volume for Windows hosts.

Value Description
UNIX clients Specifies the location for a transient
volume for UNIX or Linux hosts.
Generate server cache Specifies you want to generate a shared
server cache. If you select this option, TEM
runs the generate_metadata_cache
utility at the end of the install, upgrade,
or update action. This option reduces
Teamcenter memory consumption by
moving metadata to shared memory.
Types, property descriptors, and constants
are placed in a shared cache that is shared
by all Teamcenter server instances.
This option is selected by default in a
For more information about managing
shared server cache, see the System
Administration Guide.
Generate client cache Specifies you want to generate a cache
of data that rich clients can download
once at initial logon and then reuse on
the client host. This option reduces
server demand, reduces startup time,
and improves overall performance. When
this option is selected, TEM runs 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 old client cache
is deleted.
This option is selected by default in a
For more information about the
generate_client_meta_cache utility, see
the Utilities Reference.
For advanced Teamcenter Foundation options, click Advanced.
16. Proceed to the Flex License Client panel. Enter settings for the Siemens PLM
Software Common Licensing Server. The Common Licensing Server must be
installed before you begin Teamcenter installation.
For more information, see Install the licensing server.
17. Proceed to the Teamcenter Administrative User panel. During a corporate server
installation, the values in this panel are read-only.
18. Proceed through the remaining panels, entering the required information for the
features you selected.

For information about these panels, click the help button .
19. Proceed to the Confirmation panel. Verify the information you entered.
If you want to change any values, click Back to return to the panels you want
to change. Otherwise, click Start to begin installing the Teamcenter corporate
server.
Note
• If you chose the Online Help feature, TEM prompts for the location of
the online help files during installation. Enter the path to the location
of tchelp.jar file on the Teamcenter documentation distribution
image.
• If an error occurs during installation, follow the instructions in the

error message displayed by TEM or see Troubleshooting for possible
solutions.
20. When installation is complete, close TEM.

Chapter
8 Teamcenter postinstallation tasks
Start database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Prepare the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . 8-2
Install a proxy server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Configure heterogeneous operating system environment . . . . . . . . . . . . . . . . 8-4

Chapter
8 Teamcenter postinstallation tasks
Teamcenter postinstallation tasks

Perform the appropriate procedures to complete installation of Teamcenter features.
Start database daemons

If you select Teamcenter database daemon features during Teamcenter installation,
Teamcenter Environment Manager (TEM) configures the database daemons to start
automatically as Windows services. After installation, you can find these services in
the Services dialog box in the Windows Control Panel:
Teamcenter Task Monitor Service
Teamcenter Subscription Manager Service
Teamcenter Action Manager Service
Teamcenter Tesselation Manager Service
Each service behaves as follows:

1. After the services are started, a program runs in TC_ROOT\bin named
tc_server.exe.
Windows displays tc_server.exe in the task manager. If you do not see this
process, either your registry entry for that service is corrupted (specifically the
path to the image) or the file is not on the system.
2. The tc_server.exe program identifies the service that launched it by

examining the service name. It expects the service name to contain either
actionmgrd, subscripmgrd, task_monitor, or tess_server. The default
service names for Teamcenter are tc_actionmgrd, tc_subscripmgrd,
tc_taskmonitor, and tc_tess_server. These services are defined in
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
3. The tc_service.exe program assembles a .bat file name by prefixing the

service name with run_ and appending the extension of .bat. For example, the
tc_actionmgrd service has the file name run_tc_actionmgrd.bat.
4. The tc_service.exe program calls the .bat file (created by the setup program
during configuration and placed in the \bin directory of the Teamcenter
application root directory).
5. The task manager displays the process, for example, actionmgrd.exe.

Chapter 8 Teamcenter postinstallation tasks
If the process is not displayed in the task manager, either the service name is
not one of the three supported names, the .bat file for the process does not exist,
or the process executable is missing.
6. The Services dialog box is updated to Started.

Note
For more information about database daemon features, see Teamcenter
features.
Configure Multi-Site Collaboration

Multi-Site Collaboration allows the exchange of Teamcenter data objects between
databases. Each database should be easily accessible via TCP/IP, either over the
Internet or the company intranet. Configuration of Multi-Site Collaboration is
optional.
Coordinate configuration of Multi-Site Collaboration with the system administrators
of the other Teamcenter databases to be part of the Multi-Site Collaboration
environment. Information about all participating Teamcenter database sites must
be stored in each database and in the site preference files. In addition, you must
identify the network nodes to run Multi-Site Collaboration server processes for these
databases and configure those systems to run the processes.
Prepare the Multi-Site Collaboration environment

Perform the following steps to configure Multi-Site Collaboration for a wide area
network:
1. Identify all Teamcenter databases to be part of the Multi-Site Collaboration
environment.
2. Identify the Teamcenter database to act as the ODS database.

This database stores records about the data objects published by other databases
in the Multi-Site Collaboration environment (that is, made public to the other
databases).
This can be one of the databases identified in step 1 or it can be a dedicated
database. The database must be populated with Teamcenter data.
3. For each database identified in step 2, identify a network node local to that
database to act as the ODS server.
The ods service runs on this system to listen for publication queries from other
databases.
4. For each database identified at step 1, identify a network node local to that
database to act as the IDSM for that database.
When other databases request an object published from this database, the idsm
service is run on this network node to export the object.
5. For each database identified in step 1, obtain the site name and site ID.

Teamcenter postinstallation tasks
The site ID of the database is generated during installation and cannot be

changed. The site name is customizable but by default is based on the site ID.
To obtain the site name and site ID, use the administration application named
Organization in Teamcenter rich client (in the rich client application manager,
click Admin and then click the Organization symbol). Within Organization,
choose the top-level Sites node from the Organization tree. The site details for
the local database are listed first. For more information, see Organization Guide.
6. Using the information obtained in steps 2 through 5, populate each database site
table with information about the other sites using the Organization application
in the Teamcenter rich client.
The node for each site is the name of the network node to run the necessary
Multi-Site Collaboration services (idsm and/or ods). If the site is an ODS
database, check the ODS site flag. To publish objects from the ODS database,
define the site of the ODS database in the site table and configure the ODS
server as an IDSM server.
7. For each database identified in step 1 and step 2, edit the site preference for
the database and modify the following preferences to reflect the Multi-Site
Collaboration environment:
ODS_permitted_sites (ODS database only)
ODS_site (Non-ODS databases)
ODS_searchable_sites
ODS_searchable_sites_excluded
IDSM_permitted_sites
IDSM_permitted_users_from_site_site-name
IDSM_permitted_transfer_sites
IDSM_permitted_transfer_users_from_site_site-name
IDSM_permitted_checkout_sites
IDSM_permitted_checkout_users_from_site_site-name
Fms_BootStrap_Urls
TC_publishable_classes
TC_transfer_area
For more information about these preferences, see the Teamcenter Preferences
and Environment Variables Reference.
8. For each database identified in step 1 and step 2, copy all POM transmit schema
files for that database into the POM transmit schema directories for each of the
other databases.
This step is required to allow the import of data objects from other databases.
Devise a strategy for regularly synchronizing POM transmit schema directories.
9. For each network node identified at step 3 and step 4, run the Teamcenter
setup program on that node to configure and start the Multi-Site Collaboration
daemons.
Install a proxy server

Configure a proxy server to be used with Multi-Site Collaboration. For more
information, see Multi-Site Collaboration Guide.

Chapter 8 Teamcenter postinstallation tasks
Configure heterogeneous operating system environment

If you are adding Windows Teamcenter clients to a UNIX Teamcenter environment,
you must perform the following tasks:
1. Install Teamcenter and configure the database (Teamcenter application root and
data directories) on a Windows system that can serve a common mount point
for all Windows clients.
This allows the Windows and non-Windows Teamcenter clients to interoperate,
particularly in volume management.
2. Synchronize site preference files, dataset definition files, and schema files in the
separate Teamcenter data directories.
3. Configure File Management System (FMS) on UNIX and Windows volume

servers.
Conversely, if you create a Teamcenter database by running the Teamcenter setup

program from a Windows workstation, you must install Teamcenter on UNIX clients
you want to connect to the database.

Part
IV Web tier installation
Install the Teamcenter Web tier, which manages communication between the
Teamcenter clients and the enterprise tier.

Chapter
9 .NET Web tier installation
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Install required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Configure Microsoft IIS on Windows Server 2008 . . . . . . . . . . . . . . . . . . . 9-1
Install the .NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Start the Web client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Configuring online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Chapter
9 .NET Web tier installation
.NET Web tier installation

The Teamcenter .NET Web tier is an alternative to the Teamcenter J2EE Web tier
for Microsoft Windows systems. The .NET Web tier supports four-tier Teamcenter
deployments and does not require a J2EE application server.
Before you start

Before you begin installing the .NET Web tier, make sure you log on using an account
with administrative privileges and that you have access to the Teamcenter software
distribution image. Also, make sure your host has the required software and is
correctly configured for the Teamcenter .NET Web tier.
Install required software

The Teamcenter .NET Web tier requires a supported Microsoft Windows server
operating system and also the following Microsoft components:
• Microsoft Internet Information Services (IIS)
• Microsoft .NET Framework
During installation of the .NET Web tier, Teamcenter Environment Manager (TEM)
verifies that you have the required software and operating system versions.
For information about required versions of these products, see the Siemens PLM
Software Certification Database:
Configure Microsoft IIS on Windows Server 2008

If you use Microsoft Internet Information Services 7 (IIS7) or later on a Windows
Server 2008 host, make sure the host is configured correctly for the Teamcenter
.NET Web tier by performing the following steps:
1. Start the Windows Server 2008 server manager (Start→Administrative
Tools→Server Manager).
2. In the Server Manager, expand the Server Manager (host) node.
3. Expand the Roles tree and select Web Server (IIS).
4. In the Roles pane, under Web Server (IIS), locate the Role Services table.

Chapter 9 .NET Web tier installation
5. In the Role Services table, verify that all of the following required role services
are installed on your host:
Web Server
Common HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection
Application Development
ASP.NET
.NET Extensibility
ASP
CGI
ISAPI Extensions
Server Side Includes
Health and Diagnostics

HTTP Logging
Logging Tools
Request Monitor
Tracing
Security
Basic Authentication
Windows Authentication
Digest Authentication
Client Certificate Mapping Authentication
IIS Client Certificate Mapping Authentication
URL Authorization
Request Filtering
IP and Domain Restrictions
Performance
Static Content Compression
Dynamic Content Compression
Management Tools
IIS Management Console
IIS 6 Management Compatibility
IIS 6 Metabase Compatibility
IIS 6 WMI Compatibilty
IIS 6 Scripting Tools
IIS 6 Management Console
If any of these services are not installed, click Add Role Services to
launch the Add Role Services wizard and install the required role
services.

Caution
Make sure the WebDav Publishing role is not installed.
Install the .NET Web tier

1. Launch Teamcenter Environment Manager. In the Windows start menu, click
Programs→Teamcenter 9.1, and then right-click Environment Manager and
select Run as administrator.
Note
This procedure assumes you are adding the .NET Web tier to an existing
Teamcenter configuration. To create a new configuration with the .NET
Web tier, perform the steps in Create a configuration and in the Features
panel, select Web Tier for .NET.
2. In the Maintenance panel, select Configuration Manager.
3. In the Configuration Maintenance panel, select Perform maintenance on an

existing configuration.
4. In the Old Configuration panel, select the configuration to which you want to
add the .NET Web tier.
5. In the Feature Maintenance panel, select Add/Remove Features.
6. In the Features panel, under Server Enhancements→Teamcenter Web Tier,

select Web Tier for .NET.
7. Proceed to the .NET Web Tier panel.

Note
For descriptions of TEM panels, click the help buttons in each panel.
8. Type values for the following required parameters:
Parameter Description
Web Tier Language Specifies the same locale that is specified for
Teamcenter server. This locale is used for
localization of messages coming from Web tier. The
default Web tier language is English.

Session Time Out Specifies the web tier session time out in minutes.
The default value is 20. If a user is inactive for
more than the timeout value, the user’s Web tier
session expires.
In the thin client, if a session expires, the user
must authenticate again to continue working.
In the rich client, client credentials are
cached. After a session time-out, the rich client
automatically logs on silently and allows the user
to continue working.
Response Compression Specifies the threshold in number of bytes beyond
Threshold which the Web server should compress responses
sent back to the client.
Typically, compressing smaller responses does
not yield significant compression, so all responses
equal to or less than the value specified are sent to
the client uncompressed. Setting this value to 0
causes the server to compress every response sent
to the client. The default value is 500 bytes.
Server Manager Peers Specifies server manager peer hosts for the .NET
Web tier. Enter one or more hosts using the Add
button and entering host and port numbers for
each.
At least one server manager must be configured
for a working deployment. The port number each
server manager peer must match the port you
specify during the corresponding server manager
installation.1
The remaining parameters in the .NET Web Tier panel are optional. Enter
values for these parameters as needed.
9. Click Next.
TEM displays the .NET Web Tier Client Integration panel.
10. Enter the necessary values to configure the .NET Web tier client integrations.
11. Click Next.

TEM displays the Internet Information Services (IIS) Settings panel.
12. Type values for the following required parameters:
1. For information about installing the .NET server manager, see Install the .NET server manager.

Use Existing Web Site Specifies whether to use an existing Web site.
If you select this option, select the Web site you
want to use from the list. The IIS virtual directory
for .NET Web tier deployment is created in the
selected Web site and the application is hosted on
that Web Site.
Alternatively, you can select Create New Web Site,
and then type a name, port, and root path for the
new Web site.
Use Existing Application Specifies whether to use an existing application
Pool pool from the list provided. An application pool is
a set of one or more applications assigned to an
IIS worker process. The Teamcenter .NET Web
tier is an ASP.NET application, so the application
pool that hosts it can only host applications
based on the same version of ASP.NET. Keep this
in mind if you have this application pool host
other applications. If possible, use a dedicated
(stand-alone) application pool for Teamcenter Web
Tier deployment.
The default value is Use Existing Application
Pool.
Note
Alternatively, you can create a new
application pool.
For more information, see the Teamcenter
Environment Manager online help.
Virtual Directory Name Specifies the IIS virtual directory name for
Teamcenter .NET Web tier deployment. The
default value is tc. Web URLs for Teamcenter
four-tier deployments are based on this value. For
example, if you specify the default value as tc, the
URLs are of the form: http://host:port/tc.
13. In the Confirmation panel, click Start to begin installing the .NET Web tier.
14. When installation completes, exit TEM.
Start the Web client

After you install the .NET server manager and the .NET Web tier, complete the
.NET Web tier installation:
• Start the .NET server manager as described in Start the server manager.

• Install Teamcenter clients as described in the Installation on Windows Clients

Guide.
Configuring online help

Additional steps are required to install Teamcenter online help for the .NET Web tier.
For more information, see Install online help on the .NET Web tier.

Chapter
10 J2EE Web tier installation
J2EE Web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Installing thin client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Build the Teamcenter Web Tier Web application . . . . . . . . . . . . . . . . . . . 10-3
Build additional Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Install Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Supporting files locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Generate Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Build a proxy WAR file for WebLogic . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Migrate legacy thin client URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Sharing an application server instance for multiple four-tier
environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Installing rich client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19

Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Rich client distribution instance requirements . . . . . . . . . . . . . . . . . 10-22
Install a rich client distribution instance . . . . . . . . . . . . . . . . . . . . . 10-28
Configuring TCCS, Security Services, and proxy settings . . . . . . . . . 10-31
Configure TCCS for the rich client distribution instance . . . . . . . 10-31
Configure Security Services for the rich client distribution
instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Configure reverse proxy settings for the rich client distribution
instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Deploy the distribution server instance . . . . . . . . . . . . . . . . . . . . . . 10-35
Publish information for users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38
Start and stop the rich client distribution server . . . . . . . . . . . . . . . 10-38
Start the rich client distribution server . . . . . . . . . . . . . . . . . . . 10-38
Stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . 10-39
Managing the rich client distribution server and instances . . . . . . . . . . . 10-39
Change the distribution server contents . . . . . . . . . . . . . . . . . . . . . 10-40
Add components to the distribution server instance . . . . . . . . . . . . . 10-40
Run the distribution server as a service . . . . . . . . . . . . . . . . . . . . . . 10-42

Chapter
10 J2EE Web tier installation
J2EE Web tier installation

J2EE Web tier installation begins with installing the Teamcenter Web Application
Manager, a tool that builds thin client and rich client Web applications. With this
tool, you can build thin client applications that distribute the Teamcenter thin client
to run in Web browsers on client hosts. The Web Application Manager also enables
you to install a rich client distribution server and build rich client distribution
instances that install the four-tier rich client over a network onto client hosts.
Building Web applications with the Web Application Manager consists of the
following general steps:
1. Launch the Web Application Manager.
2. Copy the necessary ICD files from the Teamcenter software distribution image.
This populates the list of solutions available to install.
3. Create a new Web application.

This includes specifying a name and staging location for the Web application,
locations of the install images, and the type of solutions it contains.
4. Choose solutions to include in your application.
5. Set context parameters.

Context parameters allow you to configure access to Teamcenter services and
behavior of Web tier solutions. Most Web tier solutions provide usable default
values you can modify as needed after installation, but some parameters must
be set during installation to enable the selected solutions.
6. Generate a deployable file.

Depending on the solutions you select, the Web Application Manager generates
either a Web archive (WAR) or enterprise archive (EAR) file.
7. Deploy the Web application on a supported J2EE application server.
Note
Deployment of Web applications is described in the Web Application
Deployment Guide.

Chapter 10 J2EE Web tier installation
J2EE Web tier prerequisites

Before you install the J2EE Web tier, make sure you complete the following tasks:
• Install the Teamcenter server and server manager using Teamcenter
Environment Manager as described in Teamcenter server installation.
• Install a supported third-party J2EE application server and the Java Runtime
Environment (JRE) on the Web tier host.1
• If you want to install Teamcenter online help for the Web tier, obtain the
Teamcenter 9.1 documentation distribution image.
Note
Alternatively, you can install the Teamcenter online help library using
Teamcenter Environment Manager (TEM) rather than installing it as
part of the Web tier.
Teamcenter developer references, the Teamcenter Data Model Report, and
the Teamcenter PDF help collection are not available to install on the
J2EE Web tier. These online help components can only be installed to a
local host or network file system path using TEM.
For more information, see Installing Teamcenter online help.
• If you use Security Services with the rich client or thin client, install Security
Services as described in Security Services installation.
Install the Web Application Manager

1. Create a home directory for the Teamcenter Web tier, for example, c:\tcweb.
This directory is referenced as WEB_ROOT.
2. In the Teamcenter software distribution image, browse to the Web_tier directory

and double-click the INSTALL_TCWEB.EXE program icon.
WinZip displays a self-extractor dialog box.
3. In the Unzip To Folder box, type the path to WEB_ROOT, and then click Unzip.
After WinZip extracts the installation files, click Close to close the WinZip
self-extractor dialog box.
4. To launch the Web Application Manager, browse to the WEB_ROOT directory

and double-click the insweb.bat program icon.
1. For information about supported application servers and Java versions, see the Siemens PLM Software Certification Database
(http://support.industrysoftware.automation.siemens.com/certification/teamcenter.shtml).

Installing thin client Web applications

The first thin client Web application you build is the Teamcenter Web Tier
application, which provides essential thin client functionality. To this application
you can add additional thin client solutions, including custom solutions, according
to your needs.
For information about installing this application, see Build the Teamcenter Web
Tier Web application.
After you build the Teamcenter Web Tier application, you can build additional
Web applications to support Teamcenter features you use, as described in Build
additional Web applications.
Build the Teamcenter Web Tier Web application

1. Launch the Web Application Manager (insweb.bat).
2. Copy Web tier solution ICDs:

a. Click Copy ICDs. In the Copy ICD Files dialog box, click Browse.
b. Browse to the Web_tier directory in the root directory of the Teamcenter

software distribution image and select the icd directory, and then click Open.
c. In the Copy ICD Files dialog box, click OK to load ICD files.
3. To begin creating a Web application, click Add.

Web Application Manager displays the Add Web Application dialog box.
4. Create the Teamcenter Web Tier Web application:

a. In the Name box, type the name of this application, for example, Teamcenter
Web Tier.
b. In the Staging Location box, enter the path to the location where you
want the application files to reside. Typically, this is a directory under the
WEB_ROOT directory. Web Application Manager creates the directory you
specify if it does not exist.
c. Optionally, in the Description box, type a brief description of the application.
d. Add the path to the Web_tier directory on the Teamcenter software

distribution image to the Disk Locations for Install Images box:
image-location\Web_tier
Use the Add or Modify buttons to add a location or modify an existing one.
Note
Do not change the default solution type (Thin Client) shown in the
Solution Type box.
5. Select the solutions to include in the Teamcenter Web Tier Web application:
a. Click Solutions.

b. In the Select Solutions dialog box, select the following required solutions:
Teamcenter – Server Adapter
Teamcenter – Web Tier Infrastructure
Teamcenter – Web Tier Core Applications

Note
Some solutions require other solutions, and some solutions are
incompatible with others. When you select a solution, the Web
Application Manager automatically selects prerequisite solutions and
disables incompatible solutions.
c. Optionally, select one or more of the following additional solutions:
Solution Description
Teamcenter – GM Overlay Provides the Teamcenter Automotive
Edition–GM Overlay for the Teamcenter
thin client.
Teamcenter – Online Help Provides Teamcenter online help for the
thin client.
Note
If you select this solution, you must
add the path to the Teamcenter
documentation distribution image to
the list of Disk Locations for Install
Images as in step 4.2
Teamcenter Services Installs the Teamcenter service-oriented
WSDL/SOAP Support architecture (SOA), which provides the
ability to develop task-specific clients,
utilities, and system integrations for the
Teamcenter server. The Teamcenter SOA
also ships with WS-I compliant WSDL files
for all operations, supporting open industry
standards.
For more information, see the Services
Guide.
6. If you require the deployable file for the Web application to be a distributable file,
click Advanced Web Application Options and select the Distributable option.
Note
A distributable file is required only if you deploy the Web tier application
in a cluster configuration.
2. The Teamcenter documentation distribution image contains the tchelp.jar file that contains the online help files.

7. Click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
8. Enter values for required context parameters.

For most context parameters, you may accept the default values shown. For the
Teamcenter Enterprise Tier Web application, you must supply values for the
following context parameters:
TreeCache Cluster Name3
TreeCache Mode
TreeCache Cluster Port (when using multicast communication protocol)
Local Service Port (when using TCP communication protocol)
TreeCache Peers (when using TCP communication protocol)
Enterprise Application Registration ID
LogVolumeName
LogVolumeLocation
To set a context parameter, double-click the Value box for the given parameter
and enter the new value. To view a description of any context parameter, click
the parameter name in the Modify Required Context Parameters dialog box.
For more information about context parameters, see Web tier context parameters.
9. Click OK to begin building the Web application.

The Web Application Manager displays the status of the installation in the
Progress dialog box. When the installation is complete, click OK to close the
Progress dialog box.
10. Click Exit to exit the Web Application Manager.
11. Locate the deployable file (tc.ear) generated during installation. This file is in
the deployment directory under the specified staging location.
Deploy the Web application as described in the Web Application Deployment
Guide.4
Build additional Web applications

Depending on the Teamcenter features you use, build one or more of the Web tier
applications described in the following table.
Feature Application Description

Global Global Services Provides the application directory
Services application directory functionality required by Global Services.
application For information about installing this
application, see Install Global Services.
3. For more information about configuring JBoss Cache TreeCache and setting TreeCache parameters, see www.jboss.org/jbosscache.
The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jgroup.org.
4. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose
the appropriate procedure for the application server you use.

Feature Application Description

Global Services Provides essential Global Services
Enterprise application functionality. You can add Global Services
connectors and other components to
this application. For information about
installing this application, see Install
Global Services.
Thin client Proxy WAR file for Provides support for WebLogic Express
deployed on WebLogic application as a front-end HTTP listener for the thin
WebLogic client.
Express
For information about installing this
application, see Build a proxy WAR file
for WebLogic.
Legacy thin Legacy URL support Upgrades legacy thin client URLs to
client support application Teamcenter 9.1. If you are upgrading
a previous Teamcenter installation that
includes the thin client, generate the
legacy URL management application.
For information about installing this
application, see Migrate legacy thin client
URLs.
Install Global Services
You build Global Services Web applications using the Web Application Manager.
Supporting files locations
Several Global Services connectors require that you provide the location to files that
are provided by the connector’s back-end system or from some other source. The
location must be accessible to the Web Application Manager as you must enter the
path to the file in the Disk Locations for Install Images box. If you plan to include
the connector in your Web application, make sure the files identified for the connector
are available, and note the path to the file for use in Generate Web applications.
Note
As an alternative to having the directories containing dependent connector
files accessible to the Web Application Manager, you can copy the dependent
files to an accessible location. However, if you do not keep the files in the
paths indicated in the ICD file, you must edit the ICD file for the connector
to eliminate or correct the path. For example, the Teamcenter Enterprise
connector ICD has the following dependent file entry:
[COPYFILE]
{
[FROM]
enterprise/mti.jar
[TO]
lib/enterprise
}

If you copy the mti.jar file to a Web Application Manager accessible location,
it must be in the enterprise directory under the location set in the Disk
Location to Add box. Alternatively, you can edit the ICD file to remove
enterprise/ from the [FROM] section.
• Teamcenter Enterprise connector

This solution requires the MTI_ROOT\evista\java\classes directory location.
This directory contains the mti.jar file and mtiems.jar files required for
connecting to Teamcenter Enterprise. The mtiems.jar file contains the import
and export functionality that the connector supports for Teamcenter Enterprise.
If you are connecting to an earlier version of Teamcenter Enterprise,
import and export is not supported and the required mtiems.jar
file is not available in this directory. However, after you install the
Teamcenter 9.1 Global Services – Application Directory solution, the
WEB_ROOT\application-directory-staging-directory\webapp_root\lib\enterprise
directory for that solution contains a version of this file containing
only a manifest file.
The easiest approach is to copy the required JAR files (mti.jar and mtiems.jar
to WEB_ROOT\application-directory-staging-directory\ webapp_root\
lib\ enterprise directory and add this location to the disk locations for install
images in the Web Application Manager.
• Teamcenter Engineering v9 connector

If you are installing the Teamcenter Engineering V9 connector, the Teamcenter
Engineering Portal client directory must be available to the host where the
connector is being installed. This directory contains resources that the connector
requires at runtime. The files used from this directory are:
o icctstubs.jar
o orbix.jar
o portal.jar
o soap.jar
o client_specific.properties
o portal.properties
o portal_locale.properties
o portal_user.properties
o site_specific.properties
• Teamcenter Engineering 2005/2007 connector

If you are installing the Teamcenter Engineering 2005/2007 connector, it
requires access to external dependent JAR files. These files are located in
thePortal directory for the Teamcenter Engineering server instance and must
be available to the Web Application Manager during the install process. This
directory is a first-level subdirectory under the Teamcenter Engineering server
base directory. The files used from this directory are:
o portal.jar
o portal_patch.jar
o fscproxy.jar
o icctstubs.jar
o tcgatewaystubs.jar

o xmldto.jar
o xercesImpl.jar
o client_specic.properties
o portal.properties
o portal_locale.properties
o portal_user.properties
o site_specic.properties
The Teamcenter Engineering 2005/2007 connector can access multiple

Engineering 2005 or 2007 instances; however, as with all Global Services
connectors, it requires that all instances be the same version.
Note
The Teamcenter Engineering 2005/2007 connector and Teamcenter
Engineering V9 connector can coexist with each other or any other Global
Services connector.
• Teamcenter 2007 rich client connector

If you are installing the Teamcenter 2007 rich client connector, the connector
requires access to dependent external JAR files. These files are located in the
portal\plugins directory for the Teamcenter server installation and must be
available to the Web Application Manager during the install process. The files
used from this directory are:
o com.teamcenter.rac.aifrcp_2007.1.0.jar
o com.teamcenter.rac.kernel_2007.1.0.jar
o com.teamcenter.rac.util_2007.1.0.jar
o icctstubs.jar
o tcgatewaystubs.jar
o TcSoaClient_2007.1.0.jar
o TcSoaCommon_2007.1.0.jar
o com.teamcenter.rac.external_2007.1.0\TcGatewayWebService.jar
o xmldto.jar
o configuration_2007.1.0\portal.properties
o configuration_2007.1.0\portal_locale.properties
o configuration_2007.1.0\portal_user.properties
o configuration_2007.1.0\site_specific.properties
o org.eclipse.jface_3.2.0.I20060605-1400.jar
o org.eclipse.ui.workbench_3.2.0.I20060605-1400.jar
o org.eclipse.core.commands_3.2.0.I20060605-1400.jar
The following files must also be available to the Web Application Manager in
the indicated directory path:
o WEB-INF\lib\JETIGateway-ejb-client.jar
o pool_manager\JETIUtil.jar
o teamcenter\dhtml\apps\fms\fscproxy.jar

Generate Web applications

Note
Some solutions require other solutions, and some solutions are incompatible
with others. When you select a solution, the Web Application Manager
automatically selects prerequisite solutions and disables incompatible
solutions. For example, Teamcenter – Server Adapter and Teamcenter 9.1
Global Services Framework – Enterprise Application are incompatible
solutions.
2. Copy Web tier solution ICDs:

a. Click Copy ICDs.
b. In the Copy ICD Files dialog box, click Browse.
c. Browse to the Web_tier directory in the Teamcenter software distribution

image, select the icd directory, and click Open.
d. In the Copy ICD Files dialog box, click OK to load ICD files.
3. Click Add to begin creating Global Services applications.

The Web Application Manager displays the Add Web Application dialog box.
4. Create the required undeployable solutions:

Note
If you are installing the Teamcenter 8 Rich Client Connector, you must
repeat this procedure selecting the Teamcenter 9.1 Global Services
Framework – Teamcenter Rich Client OSGi Plug-In solutions in step g.
If you are installing the Teamcenter 2007.1 Rich Client Connector, you
must repeat this procedure selecting the Teamcenter 9.1 Global Services
Framework – Teamcenter 2007.1 Rich Client OSGi Plug-In solutions in
step g.
a. In the Name box, type a name for the application, for example, Application
Directory.
b. Accept the default value for Staging Location or enter a different directory.
c. In the Disk Locations for Install Images box, add the path to the Web_tier
directory on the Teamcenter software distribution image.
d. Click Advanced Web Application Options.
e. In the Advanced Web Application Options dialog box, clear the

Automatically Build Deployable File check box.
f. Click Solutions.

g. In the Select Solutions dialog box, clear all preselected solutions and select
the Teamcenter 9.1 Global Services Framework – Application Directory
solution.
Note
Do not change the default solution type (Thin Client) in the Solution Type
box.
5. Click OK to begin installing the solution.

The Web Application Manager displays the installation status in the Progress
dialog box. When the installation is complete, click OK to close the Progress
dialog box.
6. Click Add to begin creating the Global Services enterprise application.

7. Create the Global Services enterprise application:

a. In the Name box, type a name for the application, for example, Global
Services Enterprise Application.
c. Click Advanced Web Application Options. Type a name for the deployable
file in the Deployable File Name box (alphanumeric characters only).
If you require the deployable file to be a distributable file, select the
Distributable option.5
d. (Optional) Enter the application’s description in the Description box.

Note
Do not change the default solution type (Thin Client) shown in the
Solution Type box.
8. Select the solutions to include in the Global Services Web application:

a. Click Solutions.
b. In the Select Solutions dialog box, clear all preselected solutions and select
the Teamcenter 9.1 Global Services Framework - Enterprise Application
solution.
c. Optionally, select sets of additional solutions according to how you use

Global Services:
If you use these products Select these solutions

Teamcenter 2007 or later Teamcenter 9.1 Global Services Framework
- Teamcenter SOA Connector
5. A distributable file is required only if you deploy the Web tier application in a cluster configuration.


Teamcenter 8 or later (full Teamcenter 9.1 Global Services Framework
rich client functionality) - Teamcenter 8 Rich Client Connector
Note
You must also create a separate
Web application containing the
Teamcenter 9.1 Global Services
Framework – Teamcenter 8 Rich
Client OSGi Plug-in solutions as
described in step 4 of this procedure.
Teamcenter 2007.1 MP5 Teamcenter 9.1 Global Services Framework
through MP8 (full rich client - Teamcenter 2007.1 Rich Client Connector
functionality)
Note
You must also create a separate
Web application containing the
Teamcenter 8 Global Services
Framework – Teamcenter 2007.1
Rich Client OSGi Plug-In solution as
described in step 4 of this procedure.
Teamcenter 2007 through Teamcenter 9.1 Global Services Framework
2007.1 MP4 (full rich client - Teamcenter 2007 Rich Client Connector
functionality)
Teamcenter Engineering Teamcenter 9.1 Global Services
(2005 through 2007) Framework - Teamcenter Engineering
2005/2007 Connector
Teamcenter Engineering Teamcenter 9.1 Global Services Framework
(prior to 2005) - Teamcenter Engineering V9 Connector
Teamcenter Enterprise Teamcenter 9.1 Global Services Framework
- Teamcenter Enterprise Connector
Web services Teamcenter 9.1 Global Services Framework
- WebServices Connector
Apache-based Web services Teamcenter 9.1 Global Services Framework
- Axis2 Services
JMS messaging Teamcenter 9.1 Global Services Framework
- JMS Messaging
EPSync Manager Teamcenter 9.1 Global Services Framework
- EPSync Reactor
Global Services user Teamcenter - Web Tier Infrastructure
interface (for a configuration
that does not contain Teamcenter 9.1 Global Services Framework
standalone user interface - User Interface
solution)


Server-to-server Teamcenter 9.1 Global Services Framework
communications for global - Security Proxy
workflow
Global Services orchestration Teamcenter 9.1 Global Services Framework
- Ode BPEL Enterprise Application
Note
This solution must be created
and deployed separately from the
Teamcenter 9.1 Global Services
Framework - Enterprise Application
solution.
Multiple instances of Global Teamcenter 9.1 Global Services Framework
Services you want to connect - Teamcenter Global Services Connector
Teamcenter Sourcing Teamcenter 9.1 Global Services Framework
- Teamcenter Sourcing
Teamcenter and Teamcenter Teamcenter 9.1 Global Services Framework
Enterprise (to share data) - Data Exchange
Note
• Some solutions require other solutions, and some solutions are
incompatible with others. When you select a solution, the Web
Application Manager automatically selects prerequisite solutions
and disables incompatible solutions.
• If you are installing the Teamcenter Enterprise Connector

for Teamcenter Enterprise 2005 SR1 or an earlier release of
Teamcenter Enterprise, ensure that you copy the mtiems.jar file
to the same location as the mti.jar file. For more information,
see Supporting files locations.
9. If you selected a connector that requires supporting files (see Supporting files
locations), click Modify Disk Locations and add the path to any supporting files.
10. Click OK.

11. Enter values for required context parameters.

For most context parameters, accept the default values shown. At a minimum,
Global Services requires values for the following context parameters:
For more information about Global Services context parameters, see Global
Services context parameters.

Note
For a description of these parameters, see Global Services context
parameters.
ApplicationInstance TcGSJDBCJNDI
SSOAppID TcGSMessageServerJNDI
LogFileLocation TcGSNotifierReactorJNDI
TcGSBOSJNDI TcGSDORJNDI
For more information about Global Services context parameters, see Global
Services context parameters.

The Web Application Manager displays the installation status in the Progress
dialog box. When the installation is complete, click OK to close the Progress
dialog box.
14. Locate the deployable files (by the names you specified in step 7) generated
during installation. This file is in the deployment directory under the specified
staging location.
Guide.6
Build a proxy WAR file for WebLogic

If you use WebLogic Express as a front-end HTTP listener, you must generate
a proxy WAR file:
2. Click Add to begin creating the Web application.

3. Create the proxy WAR file Web application:

a. In the Name box, type the name of this application, for example, WebLogic
Proxy.
c. Optionally, type a description of the application in Description box.

d. Click Advanced Web Application Options. Type a name for the deployable
file in the Deployable File Name box (alphanumeric characters only).
e. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image.
f. Click Solutions. In the Select Solutions dialog box, clear all preselected
solutions and select only the Teamcenter – Web Tier Proxy solution.7
Note
box.
4. Click OK.
5. Enter values for the following required context parameters:
WebLogicHost Host name of the WebLogic server running
the Web tier. The proxy forwards the request
to this server.
WebLogicPort Port number of the WebLogic server instance
running the Web tier. The proxy forwards the
request to this server.
6. Click OK to begin building the Web application. The Web Application Manager
displays the status of the installation in the Progress dialog box. When the
installation is complete, click OK to close the Progress dialog box.
8. Locate the deployable file by the name you entered in step 3. This file is in the
deployment directory under the specified staging location.
Guide.8
7. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Web
application.

Migrate legacy thin client URLs

If you migrate Web tier applications to Teamcenter 9.1 from Teamcenter engineering
process management 2005 or earlier, you must update the link your site uses to
access the thin client and the links users saved to objects managed in Teamcenter.
Teamcenter 9.1 changes part of the thin client URL from /cgi-bin/iman to
/file-name/webclient. The file-name reference is replaced with the name of the Web
tier EAR file. For example, if the Web tier EAR file is named tc.ear, the value is /tc.
To manage this change, install the legacy URL support application (cgi-bin.war)
and deploy it on the server where the Teamcenter Enterprise Tier Web application
runs.
Note
• Install the Teamcenter – Legacy URL (cgi-bin) Support thin client
solution in a separate Web application. This solution is not compatible
with other Teamcenter thin client solutions.
• Deploy the application so that it intercepts legacy requests and redirects

them to the new URL location.
For example, if the original requests are going to port 9090, deploy the
cgi-bin.war application on port 9090. If the original requests are going to
server1, deploy the cgi-bin.war application on server1.
When the cgi-bin.war file is deployed, users who access a legacy /cgi-bin/iman
URL are redirected to the /tc/webclient URL with the following message:
You have requested a resource which has moved to a new location.
Requested URL: http://host:port/cgi-bin/iman/w8PJDvpRxBRxDD
New URL: http://host:port/tc/webclient/w8PJDvpRxBRxDD
You will be redirected to the new URL automatically in nn seconds or you may
click the above link manually. If possible, update your links to reflect
the new location.
This notification message will be displayed each time an old URL is requested
prior to month-day-year. After this time, requested resources that have
moved will be automatically redirected to the new URL without notification.
When you create cgi-bin.war using Web Application Manager, you control aspects
of the application:
• Whether the application displays the Siemens PLM Software URL message
before redirecting users to the new URL. When you choose not to display the
Siemens PLM Software URL message, the application redirects users to the new
URL but displays no informative message.
• The period of time (in seconds) the application displays the Siemens PLM
Software URL message before redirecting users to the new URL.
• The date the Siemens PLM Software URL message expires. After this date,
the application redirects the users to the new URL but does not display the
informative message.
• The protocol or the port, server, and domain portion of the requested, legacy
URL. The application changes the Siemens PLM Software-provided portion of
the URL and passes through the site-provided portion of the legacy URL.

2. Click Add.
3. Create the legacy URL support application Web application:

a. In the Name box, type the name of this application, for example, Legacy
URL Support.
b. Optionally, in the Description box, type a description of the application.
c. Accept the default value for Staging Location or enter a different directory.
d. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image.
e. Click Solutions. In the Select Solutions dialog box, deselect all preselected
solutions and select only the Teamcenter – Legacy URL (cgi-bin) Support
solution.9
Note
box.
4. Click OK.
5. Enter values for the following required context parameters:
TcEngLocale Specifies a locale for messages displayed to
the user. This locale must match the locale
specified for the Teamcenter Enterprise Tier
Web application.
9. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Web
application.

expiryDateOfResource Specifies the date the URL message expires.
MovedNotification This parameter must contain a value.
Enter a value in month-day-year format
(mm-dd-yyyy), for example, 12-10-2007, or
enter one of the following keywords:
NEVER
Specifies that the URL message never
expires.
NOW
Specifies that no message or notification
regarding the resource move is displayed
to the user. The user is immediately
redirected to the new URL.

The Web Application Manager displays the status of the installation in the
Progress dialog box. When the installation is complete, click OK to close the
8. Locate the deployable file (cgi-bin.war) generated during installation. This file
is in the deployment directory under the specified staging location.
Guide.10
Note
After installation, you can optionally modify the following context parameters
for legacy URL support:
requestRedirectedTo
replacementFor CGIBIN_IMAN
redirectionWaitTime
For information about these context parameters, see Web tier context
parameters.

Sharing an application server instance for multiple four-tier

environments
Teamcenter supports deploying more than one instance of the same Teamcenter
Web tier application (EAR file) into one application server instance. Multiple EAR
files can be configured to run as discrete applications, each with a unique entry
point. This allows you to connect each application to a different enterprise tier
without the need to manage multiple application server instances. The following
example shows a possible scenario with three Web applications (EAR files) deployed
in a single application server instance.
Client Resource
tier Web tier Enterprise tier tier
Clients Single application server Server managers Databases
instance
Client ¬® ¬® ¬®
http://host:port/tc01 svrmgr11 DB1
A
Client ¬® http://host:port/tc02 ¬® svrmgr2 ¬® DB2
B ¬® http://host:port/tc03 ¬® svrmgr3 ¬® DB3
To deploy multiple Web applications in a single Web application server instance,

perform the following tasks:
1. Install multiple server managers with unique TreeCache settings.
For information about installing a server manager, see Installing the server
manager.
2. Create Web applications as described in Build the Teamcenter Web Tier Web
application. Assign each application a unique name.
3. Set the following Web tier context parameters to unique values for each Web
application.
Context parameter Description

DEPLOYABLE-FILE-NAME Name of the deployable file you are creating
for the Web tier application.
Enterprise Application Identifier for the Web application. This ID
Registration ID is used to register the application’s EJB and
J2C connector. If you want to deploy multiple
Teamcenter Web tier applications in a single
application server instance, each application
must be assigned a unique ID.
Enterprise Application Specifies the ID by which the Teamcenter
Lookup ID presentation tier accesses the application
identified by the Enterprise Application
Registration ID parameter. If you deploy your
EAR file with other EAR files in the same
application server instance, these two IDs
should be set to the same value for a given
application.

4. Deploy Web application EAR files in the Web application server instance.
For more information, see the Web Application Deployment Guide.
Note
Multiple EAR file deployment is not supported on JBoss. If you use JBoss as
your Web application server, you must deploy each EAR file in a separate
application server instance.
Installing rich client Web applications

Preparing the Teamcenter Web tier to distribute the four-tier rich client to client
hosts over a network requires the following tasks:
1. Install a rich client distribution server.
The rich client distribution server manages the connection between rich client
distribution server instances and the Over-the-Web Installer. The Over-the-Web
Installer contacts the distribution server for the rich client files to download
to the client host.
For more information, see Install the rich client distribution server.
2. Install a rich client distribution instance or instances.

For more information, see Install rich client distribution instances.
3. Deploy the Web components in a Web server.

The Web components include the Over-the-Web Installer and the HTML pages
that launch the Over-the-Web Installer.
For more information, see Deploying the distribution instance.
4. Start the distribution server.

For more information, see Start the rich client distribution server.
Note
The two-tier rich client is installed only through Teamcenter Environment
Manager (TEM). Over-the-Web installation is supported only for the four-tier
rich client.
Install the rich client distribution server

1. Start the Web Application Manager:
a. Browse to the Web_tier directory.
This is the directory in which you installed the Web Application Manager on
your hard drive.
b. Double-click the insweb.bat file.

The Web Application Manager displays the Teamcenter Web Application
Manager dialog box.

2. Click Copy ICDs.

The Web Application Manager displays the Copy ICD Files dialog box.
3. Enter the path to the icd directory in the rich client over-the-Web software
distribution image and click OK.
Note
Ensure that the icd folder is in the Source box of the Copy ICD Files
dialog box.
The Web Application Manager displays a Progress dialog box and copies and
loads the ICD files.
4. To ensure that ICD files are copied, check the Progress dialog box. When ICD
files are copied, a list of ICD files follows the Copying ICD files... notice. If
no files are listed, Web Application Manager did not find files to copy in the
directory you supplied.
If the copy was not successful, repeat steps 2 and 3, ensuring that you include
the icd directory in the path. Not including the icd directory is the most
common reason ICD files are not copied.
5. Click OK in the Progress dialog box.

Manager dialog box.
6. In the Teamcenter Web Application Manager dialog box, click Add.

7. In the Name box, type the name of this application, for example, Teamcenter
OTW Distribution Server.
8. In the Staging Location box, type the path to the location where you want the
distribution server software and administration files to reside.
Typically, you would install the distribution server software in a directory under
the Web_tier directory, the directory in which you installed the Web Application
Manager on your hard drive.
Note
• This directory must be empty. The Web Application Manager creates
the directory if it does not exist.
• Note the staging location path of this distribution server for later use.
9. Optionally, in the Description box, type a brief description of this distribution

server.
10. Click the Add button adjacent to the Disk Locations for Install Images box.
The Web Application Manager displays the Add Disk Location dialog box.

11. In the Disk Location To Add box, type the path to the icd directory in the thin
client over-the-Web software distribution image and click OK.
The Web Application Manager displays the Add Web Application dialog box with
the path you entered displayed in the Disk Locations for Install Images box.
12. Choose Distribution Server from the Solution Type list.

The Web Application Manager displays Distribution Server in the Selected
Solutions box.
Note
If Distribution Server is not in the Solution Type list, the required
ICD files were not copied correctly. To copy the ICD files, repeat steps
2 through 4.
13. Click OK.

14. Type values for the following context parameters:
Parameter Value
RMI Port Specifies the port number used by the rich client
distribution server, a remote method invocation (RMI)
registry server.
The default value, 12099, is in a range that is typically
available.
Note
Record the RMI port number for future use. It is
required when creating the distribution server
instance.
Remote Object Specifies the port on which the distribution server
Port listens for over-the-Web installers. The default value,
0, allows the distribution server to pick an available
port at run time. If you want to use a specific port,
enter a nonzero port number. This is helpful if, for
example, a firewall exists between distribution server
and over-the-Web installation clients.
File Transfer Port Specifies the port the distribution server uses to transfer
files to client hosts. The default value, 0, allows the
distribution server to pick an available port at runtime.
If you want to use a specific port, enter a nonzero
port number. This is helpful if, for example, a firewall
exists between the distribution server and over-the-Web
installation clients.
15. Click OK.

The Web Application Manager begins installing the distribution server and
displays a Progress dialog box.
16. When the Progress dialog box indicates that installation is complete, click OK.
Manager dialog box with the distribution server software you installed listed as
an application in the Web Applications box.
17. Either click Exit to exit the Web Application Manager or click Add to begin
installing the rich client distribution server instance.
Install rich client distribution instances

The Teamcenter rich client instance you install works only in a deployment of the
four-tier architecture.
For each unique rich client configuration, you must create a distribution server
instance.
Rich client distribution instance requirements

Before you build a rich client distribution instance, ensure that the following
software is installed and configured:
• Teamcenter corporate server
For information, see Teamcenter server installation.
• Rich client distribution server

For more information, see Install the rich client distribution server.
If you use Security Services with the rich client, make sure Security Services is
installed and configured.
For information, see Security Services installation and the Security Services
Installation/Customization guide.
Make sure the Web Application Manager has access to the following software images:
• Complete rich client over-the-Web software distribution image
Note
The rich client over-the-Web software distribution image includes files for
all supported Windows, UNIX, and Linux platforms. The Web Application
Manager requires access to all of these to build the Over-the-Web Installer.
• Teamcenter lifecycle visualization software distribution image
Obtain values for the required rich client parameters. You must provide these values
when building the rich client distribution instance.
Note
Required parameters must have values specified. If a required parameter
has no significance for your deployment (for example, a UNIX location in an
environment of all Windows systems), accept the default value.

RMI Port Port number used by the rich client distribution server.
This value was determined when the distribution server
was installed. The default is 12099.
WindowsLocation Location on the client host where you want the
Over-the-Web Installer to download rich client files on
Microsoft Windows systems by default.
The drive must exist on the client hosts prior to rich
client installation, and users must have write permission
to it. For example, if the installation location is
F:\Teamcenter\rich_client, every Windows client host
must have an F drive, and users must have permissions
to create Teamcenter\rich_client.
UnixLocation Location on the client host where you want the
Over-the-Web Installer to download rich client files on
UNIX systems by default.
The mount must exist on the client hosts prior to rich
client installation, and users must have write permission
to it.
WebBrowserUnixLocation Location of a Web browser on UNIX systems. This
location must be available for UNIX client hosts.
RichClientHelpWebServer URL specifying the name of the host and the port where
the Web tier or presentation tier application files are
deployed in an application server. This parameter works
together with the RichClientHelpLocation parameter to
determine how rich client users access help:
• To enable accessing help over the Web, set the
parameter value to http://host-name:port. Do
not supply the remainder of the path to the
help files (that information is supplied in the
RichClientHelpLocation parameter).
• To enable accessing help using direct file access, set

this parameter to file://.
RichClientHelpLocation Path to the Teamcenter Help Library files. This parameter
works together with the RichClientHelpWebServer
parameter to determine how rich client users access help:
• To enable accessing help using direct file access, set
the value of this parameter to the full path to the help
files. You must supply paths for Windows, UNIX, and
Linux systems.
• To enable accessing help over the Web, enter the full

path to the installed help library index.html file.

HTTPUseGZip Indicates whether the rich client prefers responses
from the J2EE server in a compressed (gzipped)
form. Compressing responses reduces the bandwidth
requirement significantly, and should be considered,
especially in lower bandwidth network environment.
When set to true, the server may send responses without
compression depending on the server configuration.
When set to false, the server never compresses responses
for this rich client.
ParentFSCAddressTable List of addresses (host name and port) of the FMS file
server caches (FSC) to act as the parents of the installed
FMS file client cache.
For information on the FMS file client cache and FMS file
server cache, see Installing File Management System.
HTTPServerTable List of Web tier application servers; the first server in the
list is the default server for logon. Requires the following
information for each server:
URI
URL of the Web tier SOAP endpoint. The value
depends on where the Web tier application is
deployed. Typically it has the form:
http://host-name:port/tc/webclient
Name
Display name of the URL for the rich client graphical
user interface.
SSOAppID
Provides the Teamcenter application ID and sets the
TC_SSO_APP_ID environment variable for Security
Services.
The value you provide in this context parameter is
used only when Security Services is enabled and
either multiple Teamcenter sites are served by a
single identity provider or the Security Services
service is configured to use an ID other than TC.
When the multiple sites have different sets of users
authorized to use the application for each installation,
or different identifications in each installation, this
value identifies which installation is authenticated.
Depending on the solutions you include in your rich client distribution instance, you
may need to provide values for the additional parameters shown in the following
tables.

Rich client optional parameter values

TeamcenterSSOService Complete URL of the Security Services Identity
Service Web application. This information is required
only when you configure the rich client to log on using
the optional Security Services.
This URL is determined when Security Services is
installed and configured. You must provide the same
URL used to configure Security Services on the Web
tier.
TeamcenterSSOlogonURL Complete URL of the Security Services logon Service
Web application. This information is required only
when you configure the rich client to log on using the
optional Security Services.
This URL is determined when Security Services is
tier.
TeamcenterSSOAppID Application ID assigned to this instance of Teamcenter
in the Security Services application registry. This
information is required only when you configure
the rich client to log on using the optional Security
Services and when multiple Teamcenter sites are
either served by a single identity provider or the
Security Services service is configured to use an ID
other than TC.
This ID is determined when Security Services is
tier.
When the multiple sites have different sets of users
authorized to use the Teamcenter application for
each installation, or different identifications in each
installation, this value identifies which installation is
authenticated.
FMSProxyHTTPHost Name of HTTP proxy server host for File Management
System (FMS) communication. If you do not specify a
host, the rich client does not communicate with FMS
using an HTTP proxy server.
To configure an HTTP proxy server, you must also
specify a value for the FMSProxyHTTPPort
parameter.

Rich client optional parameter values

FMSProxyHTTPPort Number of port for HTTP proxy server for File
Management System (FMS) communication. If you
do not specify a port number, the rich client does not
communicate with FMS using an HTTP proxy server.
To configure an HTTP proxy server, you must also
specify a value for the FMSProxyHTTPHost
parameter.
FMSProxyHTTPSHost Name of HTTPS proxy server host for File
Management System (FMS) communication. If
you do not specify a host, the rich client does not
communicate with FMS using an HTTPS proxy
server.
To configure an HTTPS proxy server, you must also
specify a value for the FMSProxyHTTPSPort
parameter.
FMSProxyHTTPSPort Number of port for HTTPS proxy server for File
Management System (FMS) communication. If you
do not specify a port number, the rich client does
not communicate with FMS using an HTTPS proxy
server.
To configure an HTTPS proxy server, you must also
specify a value for the FMSProxyHTTPSHost
parameter.
Lifecycle Visualization (embedded viewer) parameter and table values

EmbVisLicenseLevel License level for the embedded viewer: Mockup,
Professional, Standard, or Base.
The Base license is available for all users of the rich
client. The other license levels are purchased separately.
EmbVisUnixLocation Location on a UNIX system of the installed embedded
viewer Web application to be configured with this rich
client.
EmbVisWindowsLocation Location on a Windows system of the installed embedded
viewer Web application to be configured with this rich
client.

Lifecycle Visualization (stand-alone application viewer) parameter and table values

TcVisWindowsLocation Full path to the stand-alone application viewer installation
location on Windows client hosts.
Users install the stand-alone application viewer on
client hosts using the Teamcenter lifecycle visualization
installation program. This location must be the same for
all Windows clients.
TcVisUnixLocation Full path to the stand-alone application viewer installation
location on UNIX client hosts.
Users install the stand-alone application viewer on
client hosts using the Teamcenter lifecycle visualization
installation program. This location must be the same for
all UNIX clients.
Teamcenter Integration for NX parameter and table values

NXWindowsLocation Full path to the NX installation location on Windows client
hosts.
Users install the NX application on client hosts using the NX
installation program. This location must be the same for all
Windows clients installing this instance.
NXUnixLocation Full path to the NX installation location on UNIX client hosts.
Users install the NX application on client hosts using the NX
installation program. This location must be the same for all
UNIX clients installing this instance.
NXVersion Version of NX installed on client hosts.
Users install the Teamcenter Integration for NX application on
client hosts using the NX installation program. This version
must be the same for all clients installing this instance. The
default value, V22.0, specifies NX 4; V21.0 specifies NX 3.
Content Management System for Rich Client 4-Tier values

CMSWebAppServerTable The list of the locations of the Content Management Web
servers. The entries correspond to the associated Teamcenter
URI sequences. Leave the field blank if the Teamcenter URI
does not have a corresponding Content Management Web
Server URL.

Install a rich client distribution instance

Install the rich client instance on the same host and in the same directory as the
distribution server.
1. Start the Web Application Manager:
your hard drive.

Manager dialog box.
2. Enter the path to the icd directory in the rich client over-the-Web distribution
image and click OK.
The Web Application Manager displays a Progress dialog box and copies the
ICD files.
3. When copying is complete, click OK.

Manager dialog box.
4. In the Teamcenter Web Application Manager dialog box, click Add.

5. In the Name box, type a name for this instance.

Choose a name that uniquely identifies this Web application instance.
6. In the Staging Location box, enter the path to the directory where you want to
install the rich client image files for downloading to clients.
Typically, you would install the rich client distribution instance files in a
directory under the Web_tier directory, the directory in which you installed the
Web Application Manager on your hard drive.
Note
• This directory must be empty. The Web Application Manager creates
the directory if it does not exist.
• Note the staging location path of this distribution server instance

for later use.
7. Optionally, in the Description box, type a brief description of this instance.
8. Click the adjacent Add button adjacent to the Disk Locations for Install Images
box.
The Web Application Manager displays the Add Disk Location dialog box.
9. In the Disk Location to Add box, enter the paths to the following installation
images:

• Enter the path to the icd directory in the rich client over-the-Web installation
image.
• Enter the paths to the Teamcenter lifecycle visualization installation images

for each operating system.
Note
For each instance, the Over-the-Web Installer requires access to the
installation images files for all operating systems.
10. Click OK.

Web Application Manager displays the Add Web Application dialog box with the
paths you entered displayed in the Disk Locations for Install Images box.
11. In the Solution Type list, choose Distribution Server Instance.

The Selected Solutions list automatically includes the following required
solutions:
Over-the-Web Installer
Microsoft Visual C++ 2005/2008 Redistributables
Teamcenter client communication system
Rich Client 4-Tier
12. If you want to include additional solutions in the distribution instance, click
Solutions and select the applications you want installed with the rich client.
For information about available rich client solutions, see Rich client solutions.
13. When you are satisfied with your selections in the Add Web Application dialog
box, click OK.
14. Enter a value for each parameter and click OK.

Note
• For descriptions of the rich client required parameters, see Rich client
distribution instance requirements. The other required parameters
vary, depending on the applications you are installing with the rich
client instance. For descriptions, see Rich client distribution instance
requirements.
• The required parameters must have values specified. If a required

parameter has no significance for your deployment (for example, a
UNIX location in an environment of all Windows systems), retain
the default value.
The Web Application Manager displays the Modify Required Table dialog boxes
for the HTTPServerTable and the ParentFSCAddressTable.
15. For each table, type the values for each parameter. To add another row to the
table, click Add Row.

Table Description
HTTPServerTable Type a list of Web tier application servers; the first
server in the list is the default server for logon.
Requires the following information for each server:
URI
URL of the Web-tier SOAP endpoint. The value
depends on where the Web tier application is
deployed. Typically it has the form:
http://host-name:port/tc/webclient
Name
Display name of the URL for the rich client
user interface.
Note
• If you use Teamcenter client
communication system (TCCS),
you do not need to supply values for the
HTTPServerTable table because you
specify these when you define TCCS
environments.
For more information, see Configure
TCCS for the rich client distribution
instance.
• If you use Security Services in

applet-free mode, append /tccs to the
end of the TcSS Login URL value, for
example:
http://host:port/app-name/tccs
This setting uses TCCS for
communication between Security
Services and the logon service, but not
for SOA requests to a Teamcenter server
or Web tier.
ParentFSCAddressTable Type a list of addresses (host name and port) of the
FMS file server caches (FSC) to act as the parents
of the installed FMS file client cache.
For information on the FMS file client cache
and FMS file server cache, see Installing File
Management System.
Note
If you use Teamcenter client communication system (TCCS), you do not
need to supply values

16. When you complete each table, click OK.

When you complete setting values for the last table, the Web Application
Manager displays a Progress dialog box and performs the following tasks:
• Extracts the rich client image files into the webapp_root directory under
the staging location directory (named in step 6).
• Creates the manifest file (ds_manifest.mf) in the staging location directory

(named in step 6).
The manifest file records and maintains information about the rich client
image files, including a list of the files and a version for each file. The
Over-the-Web Installer consults the manifest file to determine which files
to download.
17. When the Progress dialog box indicates that installation is complete, click OK.
Manager dialog box.
To make the rich client distribution instance available to client hosts, deploy the
distribution instance on a supported Web application server.
For more information, see Deploying the distribution instance.
Configuring TCCS, Security Services, and proxy settings
If you use Teamcenter client communication system (TCCS) or Security Services,

or if you connect to Teamcenter through a reverse proxy, you must modify settings
in your rich client distribution instance using the Modify Web Application dialog
box in the Web Application Manager.
Configure TCCS for the rich client distribution instance
1. In the Web Application Manager, select your four-tier rich client application in
the Web Applications list, and then click Modify.
2. In the Modify Web Application dialog box, click Modify Context Parameters.
3. In the Modify Context Parameters dialog box, enter values for TCCS context
parameters, and then click OK to continue.
Context Parameter Description

Client Communication System Specifies whether to enable TCCS to
Switch handle communication between the client
application and the Web tier.
If you want to enable TCCS, set this
parameter to on; otherwise, set it to off.


Client Tag Filter Specifies a pattern to apply when filtering
TCCS environments. Wildcard characters (*)
are allowed.
The Client Tag Filter pattern is compared
to the Tag parameters on defined TCCS
environments. Environments that do not
fit the pattern are not available to the
rich client. For example, if the rich client
Client Tag Filter value is 9.*, all TCCS
environments with Tag values beginning
with 9. are available to the rich client.
Environments with Tag values beginning
with 10 are not available.
TcCSShareConfiguration Specifies whether the TCCS configuration is
a private or shared environment.
If this is a private environment, set this
parameter to false. If it is a shared
environment, set this parameter to true.
TcCSProxyConnectionType Specifies whether to use specify the proxy
connection type.
If you do not use a proxy, set this parameter
to Do not use proxy. Otherwise, accept the
default value.
TcCSKerberosSupport Specifies whether to use Kerberos
authentication for Teamcenter logon.
If you use Kerberos, set this parameter to
true; otherwise, set it to false.
Note
Teamcenter supports Kerberos
authentication only on Windows client
hosts.
TcCSKrb5File Specifies the path to the Kerberos
configuration file (krb5.ini). If you leave
this parameter empty, the client uses the
default Kerberos configuration file.
On Windows systems, the default krb5.ini
file is in the C:\Windows directory.


TcCSAlwaysPromptForUserID Specifies whether to always prompt for a
Kerberos user name.
If you want to enable zero sign-on
functionality on Windows hosts, set this
parameter to false. This setting uses the
native operating system user ID for Kerberos
authentication on the client host.
Zero sign-on allows Windows users to launch
a Teamcenter client without being prompted
to log on to Teamcenter.
4. In the Modify Web Application dialog box, click Modify Tables.
5. In the Modify Tables dialog box, select the TcCSEnvironmentTable table, and
then click Modify.
6. In the Modify Table dialog box, click Add Row. Enter values for the TCCS
environment and then click OK to continue.
Value Description
Name Specifies the name of a the TCCS environment.
This name is displayed in the TCCS logon
dialog after configuration is complete.
URI Specifies the URI to the TCCS environment.
This is the endpoint URI for the Web tier
deployment, for example, http://host:port/tc.
Tag Specifies a string identifier for the TCCS
environment.
When installing a rich client, you can
optionally provide a Client Tag Filter value to
filter the list of environments displayed in the
rich client to those environments that match
the filter.
For example, if the Client Tag Filter value
is 9*, all TCCS environments with Tag
values beginning with 9 are available to the
client host. Environments with Tag values
beginning with 10 are not available.
Note
You set the Client Tag Filter value in
step 3.
TcSS Application ID Specifies the ID of the Security Services
application you use with TCCS.

Value Description
TcSS Login URL Specifies the URL to the Security Services
application you use with TCCS.
If you use Security Services in applet-free
mode, include /tccs at the end of the URL,
for example:
http://host:port/app-name/tccs
7. In the Modify Web Application dialog windows, click OK to apply your changes.
8. Exit the Web Application Manager and redeploy the rich client distribution
instance.
Configure Security Services for the rich client distribution instance

2. In the Web Applications box, select the Web application that contains the rich
client distribution instance and click Modify.
The Web Application Manager displays the Modify Web Application dialog box.
3. Click Modify Context Parameters.

Web Application Manager displays the Modify Context Parameters dialog box.
4. Type values for the Security Services context parameters, and then click OK.
For descriptions of Security Services context parameters, see Web tier context
parameters.
5. Exit the Web Application Manager and redeploy the rich client distribution
instance.
For more information about installing and configuring Security Services, see the
Security Services Installation/Customization.
Configure reverse proxy settings for the rich client distribution instance
If you must connect to a Teamcenter environment through a reverse proxy server
(such as WebSEAL or SiteMinder), you may need to configure TCCS reverse proxy
settings for SiteMinder or WebSEAL by performing the following steps:
1. In the Web Application Manager, select your four-tier rich client application in
the Web Applications list, and then click Modify.
2. In the Modify Web Application dialog box, click Modify Tables.
3. In the Modify Tables dialog box, select the

TcCSReverseProxyConfigurationTable table, and then click Modify.
4. In the Modify Table dialog box, click Add Row.

5. In the Add Row to Table dialog box, in the Criteria String box, type the
appropriate value.
• SiteMinder:
checkHeaders,false
Note
This setting configures TCCS to detect form-based challenges
originating from the reverse proxy. This setting also applies to other
reverse proxy servers that do not send specific header information
in the 200 form-based challenge.
• WebSEAL:
server,webseal,:/pkmslogin.form
Click OK and close dialog boxes until you return to the Modify Web Application
dialog box.
6. Generate a deployable file and deploy the rich client distribution instance.
Deploying the distribution instance

Deploy the rich client distribution instance on a supported Web application server.
Before you start

Install a supported third-party Web server.
A rich client distribution instance requires a Web server, such as Apache HTTP
Server. You can also use an application server, such as IBM WebSphere, but it is
not required. For information about supported Web servers and application servers,
see the Siemens PLM Software Certification Database:
Deploy the distribution server instance

Web Application Manager installs the following files in the webapp_root\otwweb
folder under the distribution server instance staging location.
• otw_installer.jar file
Contains the Over-the-Web Installer.
• images directory
Contains all images used by the Web pages.
• installed.html file
Contains the English version of the HTML page displayed with installation
completes successfully.
• installfailed.html file
Contains the English version of the HTML page displayed when installation fails.

• installing.html file
Contains the English version of the HTML page for launching the Over-the-Web
Installer.
• launcherror.html file
Contains the English version of the HTML page displayed to the user when the
Over-the-Web Installer cannot install the rich client due to one of the following
problems:
o The connection to the Web is not available or the user has not provided
permissions to install.
o The required Java Plug-in is not available and cannot be installed

automatically.
o Java and or JavaScript are disabled in the Web browser.
• otw.html file
Contains the logic for detecting the Web browser and Java Plug-in required for
installing the rich client over the Web.
• localized directory
Contains subdirectories for each supported locale other than English (French,
German, Italian, Japanese, Korean, Russian, S_Chinese, Spanish, and
T_Chinese). The subdirectories contain localized versions of the installing.html
and error.html files. To use a localized version of the installation, deploy the
localized installing.html and error.html files rather than the English versions.
Note
Before deploying a localized installing.html file, you must edit it as
follows:
1. Using a text editor, find the following two lines and in each replace
change_me_instance with the name of the instance:
<param name="instance" value="change_me_instance>
instance="change_me_instance"
2. Find the following two lines and in each replace change_me_server

with the name of the server host:
<param name="server_name" value="change_me_server>
server_name="change_me_server"
When editing the preceding information, do not delete the quotation

marks.
For each distribution server instance you create, deploy these files in a Web server.
If you are creating multiple rich client distribution instances, consider creating a
unique directory in the Web server documentation root for each instance and copy
all the files in the webapp_root\otwweb folder there. For detailed deployment
information, see the documentation for the Web server. The following examples use
the name of the instance for the Web component directory name:

Web server Deployment

Apache HTTP 1. In the conf configuration file, find the HTTP document
Server root directory:
DocumentRoot “document-root-path”
2. Create the instance-name directory under the HTTP

document root directory.
3. Copy the rich client Web file to the instance-name

directory.
4. Publish the following URL:

http://host-name/instance-name/otw.html
Apache Tomcat 1. In the server.xml configuration file, find the HTTP
document base directory. For example:



document base directory.
3. Copy the rich client Web components to the instance-name

directory.

http://host-name:8080/instance-name/otw.html
Sun Java System 1. In the config configuration file, find the HTTP document
root directory. For example:
<VARS docroot="document-root-path">

document base directory.
3. Copy the rich client Web components to the instance-name

directory.


Web server Deployment

IBM WebSphere 1. Find the document root directory (HTTP server core
settings in the administration server console).

document root directory.
3. Copy the Web components to the instance-name directory.

Microsoft IIS • Create a new virtual directory under the default Web site
directory:
Virtual directory alias: instance-name
Web site content directory: path to the distribution

server instance installation directory webapp_root
Virtual directory access permissions: read, run scripts
instance-name default document property: otw.html
• Publish the following URL:

Publish information for users

To enable users to install the rich client over the Web, publish the following
information:
• URL where the Web components are located.
• The location in which the rich client will be installed on user workstations. Users
must have write permissions for this location.
• For rich client instances that include support for Teamcenter lifecycle
visualization or NX, the locations in which users must install Teamcenter
lifecycle visualization and NX.
Start and stop the rich client distribution server

You can start and stop the rich client distribution server as described in the following
sections.
Start the rich client distribution server

1. Go to the staging location directory you created for the distribution server.
This is the directory containing the distribution server application and
administration utilities.

2. Ensure that the Java runtime environment (JRE) bin folder is in the Windows
path. This is the path to your JRE installation, for example:
JRE-HOME\bin
3. Browse to the webapp_root subdirectory and double-click the start_rmi.bat

program file.
The start_rmi.bat program file starts the Java remote method invocation (RMI)
registry.
4. In the webapp_root subdirectory, double-click the start_server.bat program

file.
The start_server.bat program file starts the distribution server.
When this distribution server is successfully started, it displays the following
message:
Distribution Server Started
When the distribution server is running, rich client can be installed over the Web.
Stop the rich client distribution server

Stop a rich client distribution server from a local computer by closing the distribution
server command window. The distribution server stops, and cleanup progress is
reported.
To stop a rich client distribution server from a remote computer, or if you changed
the port number the RMI registry is running on, you must have file access to the
stop_server.bat program file and the dist_server.jar file in the webapp_root
subdirectory of the distribution server staging location. To stop the distribution
server, enter the following command:
stop_server host-name:port-number
Replace host-name with the name of the computer where the distribution server is
running. Replace port-number with the port number.
The stop_server program prints the results of the remote shutdown. If the
results include Java exceptions, errors occurred. Usually exceptions occur when no
distribution server is running on the specified host.
To stop the RMI registry, use the operating system facilities.
The operating system facilities stop the RMI registry server.
Managing the rich client distribution server and instances

After a rich client distribution server and server instances are installed and
configured, you can change the distribution server contents, add components to a
distribution server instance, and patch components in a distribution server instance.
Note
To allow automatic updating of a rich client when users start a Teamcenter
session, do not change the name of the distribution instance.

Change the distribution server contents

1. Stop the rich client distribution server.
For information, see Stop the rich client distribution server.
2. Replace the existing dist_server.jar file with the new JAR file.
The dist_server.jar is in the in the webapp_root subdirectory of the staging
location for the distribution server.
3. Restart the rich client distribution server.

For information, see Start the rich client distribution server.
Add components to the distribution server instance

1. Launch the Web Application Manager:
your hard drive.

Manager dialog box.
2. Click Copy ICDs.

The Web Application Manager displays the Copy ICD Files dialog box.
3. Enter the path to the icd directory in the Rich Client Over-the-Web distribution
image and click OK.
The Web Application Manager displays a Progress dialog box and copies the
ICD files.
4. When copying is complete, click OK.

Manager dialog box.
5. In the Web Applications list, select the distribution server instance you want to
add components to and click Modify.
6. Click Modify Disk Locations.

The Web Application Manager displays the Modify Disk Locations dialog box.
7. Ensure the paths to the installation images of components you want to add are
listed in the Disk Locations for Install Images box.
For example, if you intend to add the embedded viewer to the rich client, enter
the paths to the Teamcenter lifecycle visualization installation images for each
operating system.

Note
For each instance, the Over-the-Web Installer requires access to the
installation images files for all operating systems.
8. Click Add Solutions.

The Web Application Manager displays the Add Solutions dialog box.
9. Select the components you want to add and click OK.

If the solution you are adding has required parameters, the Web Application
Manager displays the dialog boxes as necessary.
10. Provide the information for the required parameters and click OK.
Note
• For descriptions of the rich client required parameters, see Rich client
distribution instance requirements. The other required parameters
vary, depending on the applications you are installing with the rich
client instance. For descriptions, see Rich client distribution instance
requirements.
• The required parameters must have values specified. If a required

parameter has no significance for your deployment (for example, a
UNIX location in an environment of all Windows systems), retain
the default value.
The Web Application Manager begins installation of the solutions and displays a
11. When installation is complete, click OK to close the Progress dialog box.
12. If the solution you added has optional parameters you want to modify, click
Modify Context Parameters.
The Web Application Manager displays the Modify Context Parameters dialog
box.
Note
If you change a context parameter, the Over-the-Web Installer cannot
automatically update the rich client installation on user workstations.
Users must uninstall the rich client and reinstall it from this instance.
For example, if you add the Teamcenter lifecycle visualization embedded
viewer solution, and modify the PVisLicenseLevel context parameter,
users must uninstall and reinstall the rich client.
13. Type the values for the optional parameters and click OK.
Note
For descriptions of the optional parameters, see Rich client optional
parameter values.

14. Exit the Web Application Manager.
15. If you changed a context parameter value, notify users that they must uninstall
the rich client and reinstall from the same instance.
Run the distribution server as a service

1. Create the service:
a. Open a command prompt and change to distribution server location, for
example, WEB_ROOT\staging\app-name\webapp_root.
Replace WEB_ROOT with your home directory for Teamcenter Web
applications. Replace app-name with the staging directory for your Web
application that contains the distribution server.
b. Type the following commands:

sc create OTWRMI binpath= WEB_ROOT\staging\app-name\webapp_root\srvany.exe
start= auto
sc create OTWDistServer binpath= WEB_ROOT\staging\app-name\webapp_root\srvany.exe
start= auto depend= OTWRMI
Make sure you include a space before WEB_ROOT when you type these
commands.
c. Open the Windows Registry Editor (regedit).
d. Locate the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OTWRMI
e. Create a key under OTWRMI named Parameters.
f. Create a string value under Parameters named Application.
g. Set the Application key to the following value:

rmiregistry -J-cp -JWEB_ROOT\staging\app-name\webapp_root\dist_server.jar 12099
Note
12099 is the default value of the RMI Port context parameter for the
distribution server. This value should match the value you specified
during distribution server installation.
h. Locate the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OTWDistServer
i. Create a key under OTWDistServer named Parameters.
j. Create a string value under Parameters named Application.
k. Set the Application string value to the following value:

java -cp WEB_ROOT\staging\app-name\webapp_root\dist_server.jar
com.teamcenter.install.otw.ds.DistributionServer

Note
Make sure you include a space following -cp as shown in the key value.
l. Create a string value under Parameters named AppDirectory.
m. Set the AppDirectory string value to the following value:

WEB_ROOT\staging\app-name\webapp_root
n. Close the Registry Editor.
2. Start the distribution server services:

a. Open the Services dialog box in the Windows Control Panel.
b. In the Services list, right-click the OTWRMI service and choose Start.
c. In the Services list, right-click the OTWDistServer service and choose Start.
Note
The distribution server services start automatically when you restart
Windows.
If you want to remove the distribution server services, perform the following steps:
1. In the Services dialog box in the Windows Control Panel, stop the OTWRMI
and OTWDistServer services.
2. Open a command prompt and enter the following commands:

sc delete OTWDistServer
sc delete OTWRMI

Part
V Adding features
You add features to Teamcenter configurations using Teamcenter Environment

Manager and the Web Application Manager. Some features require additional steps
to install or configure. See the appropriate topics for the features you want to install.
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Chapter
11 Installing the server manager
Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Install the .NET server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Install the J2EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

Start the .NET-based server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Start the J2EE-based server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

Chapter
11 Installing the server manager
Installing the server manager

If you install the .NET-based Web tier or the J2EE-based Web tier, install the
appropriate server manager for the Web tier you use (.NET-based or J2EE-based).
Gather required information

The following table describes information required to configure the server manager.
Data Description
TreeCache cluster name1 Name for a cluster of components accessing a shared global
server pool. This name must be unique for this database and
corporate server.
You must supply this same name for the TreeCache cluster
name when configuring the Web tier application.
JMX HTTP Adaptor port Number of the port running a Java Management Extension
(JMX) HTTP adaptor.
Server host name Logical host name of the server manager host. If the server
manager host has multiple IP addresses, the server host
name allows you to control which IP address is used when
connecting to Teamcenter servers.
If your server manager host has only one IP address, you do
not need to provide a value for this box. If the server host has
multiple IP addresses and you want the server manager to
use a specific address when connecting to Teamcenter servers,
you must provide the address or the logical host name of the
server manager host.
The value you enter is written to the SERVER_HOST
parameter in the serverPool.properties file.
Communication protocol The communication protocol mode between TreeCache peers,
either TCP or multicast mode.
The Web tier application must use this same mode.
The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jgroups.org/.

Chapter 11 Installing the server manager
Data Description
Multicast configuration If you are using multicast mode, ensure that the network on
which the server manager and Web tier run are configured to
allow multicast communication.
TCP configuration If you are using TCP, the following information is required:
• The TCP port at which this TreeCache cluster member
attempts to provide the TreeCache service. If the port is
in use, the application fails to start and issues an error
about having no port to bind to. Select an available port
and retry.
This port can vary from the port specified for the Web
tier application.
If you use multiple TreeCaches on the same host (for
example, a server manager and a Web tier application),
the TreeCaches must use different local service ports.
Depending on the network configuration, specifying the
same local service port for each component may cause
problems when they are on different machines.
• Maximum time in milliseconds that a TreeCache cluster

member waits for peer responses to TCP pings.
The larger the value you specify, the more slowly the
first server manager starts.
Typically, you supply this same value for the

Connection Timeout parameter when configuring the
Web tier application.
• A list of addresses (host name and port number pairs) to
ping for peer members of the TreeCache cluster in TCP
communication mode.
This cluster member pings each host/port pair in the
list. To be found, a peer must have a matching service
port (see the Local Service Port context parameter).
Once a peer is found, the peers exchange data regarding
available server pools.
Note
You can include more than one address on a given
host. It is not necessary to include all members of
the cluster in this list. However, it is important
that when each cluster member after the first is
started, it should ping a member that is already
in the cluster.
For example, it is valid to include only a subset of
the server managers and none of the application
servers. In this case, the cluster connects only
when one or more of the designated managers is

Data Description
running. This method reduces pinging and thereby
improves performance.
For small configurations, all members (server
managers and web tiers) should be included in
the peers list. For larger configurations, it is
recommended that the number of pinged ports be
limited to no more than six. All members should
ping at least the same subset of primary server
managers so that tree caches connect and data is
shared.
Maximum servers in pool Maximum number of Teamcenter server processes allowed
to run in this pool (for a single-host configuration) or in this
subpool (for a multihost configuration).
Minimum warm servers Minimum number of Teamcenter server processes in this pool
that are started but not logged onto.
If necessary to maintain the minimum number of warm
servers, while not exceeding the maximum number of server
processes, the server manager times out servers in use.
Target number of server Target number of server processes to be available in this pool
processes or subpool during specified times.
You specify these values as time and integer pairs separated
by commas. For example:
0700 3, 1700 2
This value sets the target number of server processes as 3
between 7 a.m. and 5 p.m. and as 2 between 5 p.m. and 7 a.m.
• If the number of server processes is below the specified
target, warm servers are added to reach this number.
In this case, the number of warm servers exceeds the
minimum.
• If the number of server processes exceeds the specified

target, only the minimum number of warm servers is
maintained and servers are terminated as they time out.
Number of logons Number of logons the server manager allows per minute for
this pool or subpool. The default value, 0, allows unlimited
logons per minute.
Note
For server pool sizing recommendations, see the Teamcenter Deployment
Guide available on GTAC.

Install the .NET server manager

1. Launch Teamcenter Environment Manager (TEM). Create a new Teamcenter
configuration or choose an existing configuration to which you want to add the
.NET-based server manager.
2. In the Features panel, under Server Enhancements, select .NET based Server
Manager.
3. Proceed through other panels as for a typical corporate server installation or

update, entering configuration values as needed2 until you reach the .NET
Server Manager panel.
Note
For information about fields in TEM panels, click the Help buttons in
each panel.
4. In the Pool ID and Pool Port boxes, type a name and port for the server pool.
If the server manager host has multiple IP addresses, select the Server Host
check box and type the logical host name of the .NET server manager host in the
Server Host Name box.
If you want the system administrator to be notified of errors and warnings on
the server manager, select the Critical System Events Notification check box
and type the necessary e-mail configuration values.
5. Click Next. TEM displays the Server Manager Performance Tuning panel.
6. Enter values for the following required parameters:
Max Servers Specifies the maximum number of Teamcenter
server processes allowed to run in the server
pool. Single-host configurations can contain a
single server pool. If you create a multi-host
configuration, you can create a server pool and
subpools. The total number of servers is not
allowed to exceed the Max Servers value.
Min Warm Servers Specifies the minimum number of Teamcenter
server processes in the server pool that are started
but not logged onto. The server manager may time
out servers as needed, but maintains the minimum
ready (warm) servers at all times.

Server Target Specifies the target number of server processes to
be available in the server pool or subpool during
specified times. Specify these values as time and
integer pairs separated by commas. For example, a
value of 0700 3, 1700 2 sets the target number of
server processes as 3 servers from 7 a.m. until 5
p.m. and 2 servers from 5 p.m. until 7 a.m.
If the number of server processes is below the
specified target, warm servers are added to reach
this number. In this case, the number of warm
servers exceeds the minimum. If the number
of server processes exceeds the specified target,
only the minimum number of warm servers is
maintained and servers are terminated as they
time out.
The remaining parameters in the Server Manager Performance Tuning panel

are optional. Type values for these parameters as needed.
7. Proceed through remaining panels until you reach the Confirmation panel. Click
Start to begin installing the Teamcenter server with the .NET server manager.
Install the J2EE server manager

1. Launch Teamcenter Environment Manager (TEM). Create a new Teamcenter
configuration or choose an existing configuration to which you want to add the
J2EE-based server manager.
2. Proceed to the Features panel. Under Server Enhancements, select J2EE based
Server Manager.
3. Proceed through other panels as for a typical corporate server installation or

update, entering configuration values as needed2 until you reach the Server
Manager for J2EE panel.
Note
For information about fields in TEM panels, click the Help buttons in
each panel.
4. In the Pool ID and JMX HTTP Adaptor Port boxes, type a name and port for the
server pool.
Enter the remaining values in the panel as described in Gather required
information.
2. For information about installing a Teamcenter corporate server, see Install a Teamcenter corporate server.

5. Click Next.
TEM displays the Server Manager for J2EE Performance Tuning panel.
6. Enter values for the following required parameters:
Field/Option Description
Max Servers in Specifies the maximum number of Teamcenter server
Sub-Pool processes allowed to run in this pool (for a single-host
configuration) or in this subpool (for a multihost
configuration).
Min Warm Servers Specifies the minimum number of Teamcenter server
processes in this pool that are started but not logged onto.
Tip
If necessary to maintain the minimum number of
warm servers, while not exceeding the maximum
number of server processes, the server manager
times out servers in use.
Server Target Specifies the target number of server processes to be
available in this pool or subpool during specified times.
Specify these values as time and integer pairs separated
by commas. For example:
0700 3, 1700 2
This value sets the target number of server processes as
3 between 7 a.m. and 5 p.m. and as 2 between 5 p.m.
and 7 a.m.
• If the number of server processes is below the
specified target, warm servers are added to reach
this number. In this case, the number of warm
servers exceeds the minimum.
• If the number of server processes exceeds the

specified target, only the minimum number of warm
servers is maintained and servers are terminated as
they time out.
logons per Minute Specifies the number of logons the server manager allows
per minute for this pool or subpool.
Tip
Setting this value to 0 allows an unlimited number
of logons.
Check CPU Load Specifies whether you want the server manager to control
server processes based on the CPU load of the local host.
Tip
This option applies only to Sun Solaris systems.

Field/Option Description
CPU Load Limit Specifies a limit for the CPU load of the local host.
When the CPU load of this host exceeds the specified
limit, the assigner skips assigning from the subpool.
CPU Interval Specifies the interval in seconds between checks of the
CPU load of the local host.
The remaining parameters in the Server Manager Performance Tuning panel

are optional. Type values for these parameters as needed.
7. Proceed through remaining panels until you reach the Confirmation panel. Click
Start to begin installing the Teamcenter server with the J2EE-based server
manager.

Note
If you experience connection delays during server manager startup, see
Troubleshooting four-tier architecture deployment for possible solutions.
Start the server manager

If you install the J2EE based Server Manager or .NET based Server Manager
features, you must start the appropriate server manager to enable four-tier rich
clients to connect to the corporate server.
For information about the J2EE version, see Start the J2EE-based server manager.
For information about the .NET version, see Start the .NET-based server manager.
Start the .NET-based server manager

The .NET-based server manager is installed as a Windows service and is
started automatically when the installation is complete. It is configured to start
automatically when Windows starts.
If you do not want the server manager to start automatically, change its startup type
to Manual.3 Then you can start the .NET-based server manager manually.
1. Open a command prompt with Teamcenter environment settings by clicking the
Start button and choosing the following menu commands:
Programs→Teamcenter 9.1→service-name_configuration-ID Command
Prompt
Replace service-name and configuration-ID with the Teamcenter service name
and configuration ID you entered during installation.
2. Change to the TC_ROOT\net_servermanager directory.
3. You can change a service’s startup type in the Services dialog window in the Windows Control Panel.

3. Enter the following command to start the server manager:

netmgrstart.bat pool-id
Replace pool-id with the server pool ID you entered when you installed the
.NET-based server manager.
For information about configuring the server manager see the System Administration
Guide..
Start the J2EE-based server manager

1. Open a command prompt with Teamcenter environment settings by clicking the
Start button and choosing the following menu commands:
Programs→Teamcenter 9.1→service-name_configuration-ID Command
Prompt
Replace service-name and configuration-ID with the Teamcenter service name
and configuration ID you entered during installation.
2. Change to the TC_ROOT\pool_manager directory.
3. Type the following command to start the server manager:

mgrstartconfiguration-ID.bat
Replace configuration-ID with the ID for your Teamcenter configuration. For

example:
mgrstartMYDB.bat
The server manager displays several messages during startup. The server
manager started successfully if you see a message similar to the following that
contains an IP address and a port number:
-------------------------------------------------------
GMS: address is 153.172.61.24:17800
-------------------------------------------------------
4. Launch the server manager user interface from

http://manager_host:jmx_http_adaptor_port.
Replace manager_host with the machine on which the manager is running, and
jmx_http_adaptor_port with the number of the port running a Java Management
Extension (JMX) HTTP adaptor. (You define this in Teamcenter Environment
Manager when you set the JMX HTTP Adaptor Port.)
5. To log on, use the default user ID (manager) and password (manager). You
can change these values using the Change_Authentication operation on the
Pool Manager page.
The server manager displays the Agent View page. Bookmark this page for
future reference.
Note
Running the J2EE-based server manager as a service, as opposed to manually
executing the server manager, is not supported.

For information about configuring the server manager, see the System Administration
Guide. Also, for information about using the server manager interface, see the
System Administration Guide.

Chapter
12 Install the Business Modeler IDE

Chapter
12 Install the Business Modeler IDE
Install the Business Modeler IDE

To install the Business Modeler IDE, you can install it as a stand-alone application,
or if you already have Eclipse installed, install it into your Eclipse environment.
After you install the Business Modeler IDE, allocate additional memory so that
Business Modeler IDE has enough memory to run.
Note
The Business Modeler IDE cannot be installed on Solaris or HP Itanium.

Chapter
13 Installing a custom solution or

third-party template
Install a template using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Update the database using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Chapter
13 Installing a custom solution or

third-party template
Installing a custom solution or third-party template

Use TEM to install custom templates you package using the Business Modeler IDE.
Install a template using TEM

After you package extensions, install the resulting template to a production
environment using Teamcenter Environment Manager (TEM). You can also use this
procedure to install a third-party template.
Warning
You should back up your data on a regular basis so that you can restore it in
the event of a template installation failure.
For more information, see the Business Modeler IDE Guide.
1. Copy the template files from the packaging directory on your Business Modeler
IDE client to a directory that is accessible by the server.
By default, packaged template files are located in the Business Modeler IDE
workspace directory in the folder under the project.
On UNIX, users must have permissions to the workspace directory.
2. Start Teamcenter Environment Manager (TEM).
3. In the Maintenance panel, choose Configuration Manager and click Next.
4. In the Configuration Maintenance panel, choose Perform maintenance on an

existing configuration and click Next.
5. In the Configuration pane, select the configuration from which the corporate
server was installed. Click Next.
6. In the Feature Maintenance panel, under the Teamcenter section, select

Add/Remove Features. Click Next.

Chapter 13 Installing a custom solution or third-party template
Note
If you already installed a template to the database and want to update
the template, under the Teamcenter Foundation section, select Update
the database. This option should not be used to install a new template
but only to update an already installed template.
Use the Add/Update templates for working within the Business Modeler
IDE client option under Business Modeler Templates only if you want to
add a dependent template to your Business Modeler IDE.
7. In the Features panel, click the Browse button on the lower right side of the
panel.
Browsing for the template files
8. Browse to the directory where you have copied the template files. In the
Files of type box, ensure that Feature Files is selected so that you see only
the installable template (feature) file. Select your template’s feature file
(feature_template-name.xml) and click the Select button.
The template appears as a new feature under Extensions in the Features panel.
You can change the location of the feature in the Features panel and add a new
group to place the feature under.
9. Select the new template in the Features panel. Click Next.

Selecting the new feature
10. In the Teamcenter Administrative User panel, enter your user name and
password to log on to the server. Click Next.
11. The Database Template Summary panel displays the list of templates that are
installed as part of your template install. Click Next.
Viewing the templates to be installed
12. In the Confirmation panel, click Start. The new template is installed.

Note
If the installation fails because of invalid data model, perform the
following steps:
a. Fix the incorrect data model and repackage the template.
b. Locate the template-name_template.zip in your project’s packaging

directory and unzip it to a temporary location. Copy the following files
to the server in the TC_ROOT/install/template-name folder:
template-name_template.xml
template-name_dependency.xml
template-name_tcbaseline.xml (if the file exists)
c. Launch Teamcenter Environment Manager in the maintenance mode

and continue with recovery.
13. To verify the installation of the new template, confirm that the TC_DATA
directory on the Teamcenter server contains the new template files.
Also log on to the server and confirm that you can create instances of your new
data model.
Note
To have libraries read on the user system, the TC_LIBRARY environment
variable must be set to the platform-specific shared library path. This
environment variable is set to the LD_LIBRARY_PATH (Solaris, Linux,
or HP-UX Itanium), LIB_PATH (AIX), or SHLIB_PATH (HP-UX)
environment variable, depending on the platform detected when the
Teamcenter session is initiated.
Update the database using TEM

If you already installed a template as a new feature and want to update it because
you have added more data model definitions to it, perform the following steps:
1. Copy the packaged template files from the packaging directory on your
Business Modeler IDE client to a directory that is accessible by the server.
By default, packaged template files are located in the Business Modeler IDE
workspace directory in the folder under the project. .
2. Start Teamcenter Environment Manager (TEM).
3. In the Maintenance panel, choose Configuration Manager and click Next.

existing configuration and click Next.
5. The Configuration panel displays the installed configuration. Click Next.
6. In the Feature Maintenance panel, under the Teamcenter Foundation section,

select Update Database (Full Model – System Downtime Required). Click Next.

Starting a full model update

Note
Use the Add/Update Templates for working with the Business Modeler
IDE Client option under Business Modeler only if you want to add or
update a dependent template to your Business Modeler IDE.
7. Click Next
8. In the Teamcenter Administrative User panel, enter your user name and
password to log on to the server. Click Next.
The Update Database panel displays currently installed templates.
9. Click the Browse button to navigate to the directory where the packaged
template files are located. Select the updated feature_template-name.xml file.
Note
If you are fixing a COTS template (for example, the Foundation
template) using a new template file provided in a patch, you
must copy the template’s feature_template-name.xml and the
template-name_install.zip files to the same temporary directory
containing the new template-name_template.zip file.
The template displays a refreshed status icon.

Selecting the template for update
10. Click Next.
11. In the Confirmation panel, click Next.

The new template is installed.
12. To verify the installation of the revised template, log on to the server and confirm
that you can create instances of your new data model.

Chapter
14 Manufacturing
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Install the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Install the resource library in another language . . . . . . . . . . . . . . . . . . . . 14-4
Configure NX Library using the installation wizard . . . . . . . . . . . . . . . . . 14-5
Configure the NX Library when using a shared MACH directory . . . . . . . . 14-6
Install fixture graphic macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Updating the Manufacturing Resource Library from an earlier version . . . . . . 14-7

Deleted classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
Planning data migration from Genius4000 to Resource Manager . . . . . . . . . 14-10

Chapter
14 Manufacturing
Manufacturing
To populate the database with sample Teamcenter manufacturing process
management data, make sure that the Teamcenter corporate server is installed on
the installation host and the Teamcenter database is configured or upgraded.
Install the Manufacturing Resource Library

The Manufacturing Resource Library is a collection of data that you can import
into the database. It includes a classification hierarchy for resources such as
tools, machines, and fixtures. You use this data in the Classification and Resource
Manager applications. In addition, you can access these resources from NX CAM. To
do this, you must configure NX Library.
For more information, see Configure NX Library using the installation wizard.
To populate the Manufacturing Resource Library on the Teamcenter server:
1. In the advanced_installations\resource_management directory in the
Teamcenter software distribution image, click Setup.exe.
Note
Before you begin installation, make sure you have the latest available
version of the Manufacturing Resource Library. If a later version is
available, download and extract the latest version and browse to the
advanced_installations directory in the location of the extracted files.
For information about later versions, see GTAC or your Siemens PLM
Software representative.
Teamcenter displays the Teamcenter Configuration Setup dialog box.
2. Click Next.
Teamcenter displays a notification that you must check for the most recent
version of the resource library.
3. Click Next.
Teamcenter displays the Setup Type Selection dialog box.
4. Select Manufacturing Resources — Database Population.
5. Click Next.

Chapter 14 Manufacturing
Teamcenter displays the Choose TC_ROOT Directory dialog box.
6. Choose the path to your Teamcenter installation and click Next. The path must
point to an existing installation.
Teamcenter displays the Choose TC_DATA Directory dialog box.
7. Choose the path to the directory containing the database-specific data files and
click Next. The path must point to an existing TC_DATA directory.
Teamcenter displays the Manufacturing Resource Library — Content Owner:
Name dialog box.
8. Enter the user name, password, and group of a valid Teamcenter login account.
The plmxml_import utility uses this login information to import the data into
the Teamcenter database.
9. Click Next.
Teamcenter displays the Manufacturing Resource Library — Content Selection
dialog box.
10. Specify which types of data you want to load. You can choose from the following:
• Tools (Assemblies and Components)
• Machines
• Fixtures
• Weld guns
• Robots
• Templates (NX Manufacturing Setups)
• Vendor catalog (sample)
11. Click Next.

Teamcenter displays the Load CLASS HIERARCHY for Module(s) dialog box.
12. Select the types of class hierarchies to be imported into the database.
If those hierarchies already exist in the database, you do not have to select
them again.
For more information, see Updating the Manufacturing Resource Library from
an earlier version.
13. Click Next.

Teamcenter displays the Load SAMPLE DATA for Module(s) dialog box.
14. Select the sample data to be imported into the database and click Next.
Teamcenter displays the Support GRAPHIC BUILDER dialog box.

Manufacturing
15. Select the modules for which you want to be able to create graphics using NX part
families. Creating graphics with part family templates is supported for tools only.
Teamcenter loads part family templates using the group that you specified in
Step 8. When users create graphics in the Classification application, they must
belong to the same group specified here.
16. Click Next.

Teamcenter displays the Set ITEM TYPE dialog box.
17. Select the item type with which each of the objects in the specified modules are
imported into the database. The item types you enter here must already exist in
the database. For a list of existing item types, press F1 in the dialog box.
If you enter an item type, you must be aware of the name of the revision of
this item. The name of the revision consists of the item name appended by the
word Revision, for example, MyItem Revision. These two terms may or
may not have a space between them. You must ascertain whether the revision
has a space. If so, type “item_name ”. Notice the empty space after the item
name, for example “MyItem ”. If the item revision contains no spaces, such as
ItemRevision, this is not necessary, and you can simply type Item.
You must specify the internal item type. This name can be different from the
displayed item type name. The following table shows the default item types
used by the installation.
Symbols
Internal Item display Typical (item, item
item type name usage revision)
Mfg0MENCTool MENCTool Tools,
components, ,
assemblies
Mfg0MENCMachine MENCMachine Machines
,
Mfg0MEResource MEResource Fixtures, devices
,
Mfg0MEEquipment MEEquipment Robots, weld guns
,
18. Click Next.

Teamcenter displays the Set ITEM TYPE dialog box again with new item types.
19. Enter the item types for weld guns and robots and click Next.
Teamcenter displays the Overwrite Existing Data dialog box.
20. If you have already loaded a classification hierarchy and you want to update
your existing classification data, select the Overwrite existing data check box. If
you leave this check box cleared, Teamcenter inserts only missing data into the
classification hierarchy, leaving existing data untouched.
21. Click Next.

Teamcenter displays the Confirmation dialog box.

22. Confirm that all your selections are correct and then click Start.
Teamcenter installs the specified classification hierarchies and data into your
database.
Install the resource library in another language

Before you can install the Manufacturing Resource Library in another language, you
must do the following:
• Enable localization for Classification.
For more information, see the Localization Guide.
• Run the Manufacturing Resource Library installation to install the English

language library. English is always installed as the master language.
Note
Currently, the Manufacturing Resource Library is available only in English
and German.

2. Click Next.
3. Click Next.
4. Select Manufacturing Resources – Localization.
5. Click Next.
6. Select the path to your Teamcenter installation and click Next. The path must
7. Select the path to the directory containing the database-specific data files and
Teamcenter displays the Manufacturing Resource Library – Content Owner:
Name dialog box.
The plmxml_import utility uses this logon information to import the data
into the Teamcenter database.
9. Click Next.

Manufacturing
Teamcenter displays the Manufacturing Resource Library – LANGUAGE

Selection dialog box.
10. Select the language you want to import.
11. Click Next.

Teamcenter installs the specified classification hierarchies and data into your
database.
Configure NX Library using the installation wizard

When you install the manufacturing tooling data, you must configure NX Library
so that the new data appears in the library selection dialog boxes when searching
for classified tools in NX CAM.
You must perform this configuration on the client on which NX is installed. If your
environment includes a shared MACH directory, see Configure the NX Library when
using a shared MACH directory.
Note
Before you begin installation, make sure you have the latest available
version of the Manufacturing Resource Library. If a later version is
available, download and extract the latest version and browse to the
advanced_installations directory in the location of the extracted files.
For information about later versions, see GTAC or your Siemens PLM
Software representative.
2. Click Configure NX Library.

Teamcenter displays the NX Base Directory dialog box.
3. Enter the path to the directory where NX is installed (UGII_BASE_DIR) and

click Next.
Teamcenter displays the LANGUAGE Selection dialog box.
4. Select the language in which you want the NX Library selection dialog boxes to
appear and click Next.
5. Confirm your selections and click Start.

Teamcenter performs the following actions:
• Copies the definition files to the target directory.

• Copies event handler files to the target directory.
• Copies the images for the NX CAM tool dialogs to the target directory.
6. Select the cam_part_planner_mrl.dat configuration file when working in

NX CAM.
When you retrieve a tool from the Teamcenter database in NX CAM, the library
selection dialogs now show the classification structure from the customer
assembly hierarchy, including images corresponding to the new tooling data. You
can search for and retrieve your customer-specific tool assembly data.
Configure the NX Library when using a shared MACH directory

If your enterprise installs NX using a shared MACH directory, there are several
steps that you must perform manually. These steps mirror the steps automatically
performed by the Configure NX Library using the installation wizard procedure
performed when you use a local MACH directory.
This procedure pertains to the following files:
MACH\resource\configuration\cam_part_planner_mrl.dat
MACH\resource\library\tool\inclass\dbc_mrl_tooling_library_tlas.tcl
MACH\resource\library\tool\inclass\dbc_mrl_tooling_library_tlas_en.def
MACH\resource\ug_library\dbc_mrl_general.tcl
1. Create a copy of your cam_part_planner_library.dat file and rename it to

cam_part_planner_mrl.dat.
2. Change the following line in the cam_part_planner_mrl.dat file:

Old:
LIBRARY_TOOL,${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_inclass_tlas.def,
${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_inclass_tlas.tcl
New:
LIBRARY_TOOL,${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_mrl_tooling_library_tlas_en.def,
${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_mrl_tooling_library_tlas.tcl
If you use a customized configuration file at your company, make the change in
the customized file and continue to use this file to initialize NX CAM.
3. Copy the following files to your MACH\resource\library\tool\inclass\

directory.
dbc_mrl_tooling_library_tlas.tcl
dbc_mrl_tooling_library_tlas_en.def
4. Copy dbc_mrl_general.tcl to MACH\resource\ug_library.
5. When you initialize NX CAM, use the modified cam_part_planner_mrl.dat

file, or the customized configuration file that you modified in step 2.

Manufacturing
Install fixture graphic macros

You can create graphics for fixtures by using TCL scripts. The following procedure
copies the required scripts to the database and modifies the NXGraphicsBuilder
preference.
You must install the graphic macros on the server where the graphics builder is
installed. This is the server that runs the tcserver process.
1. Obtain the Manufacturing Resource Library installation image.
2. Click Setup.exe.
3. Select Configure Fixture TCL Graphic Macros.
4. Click Next.
5. Choose the path to your Teamcenter installation and click Next. The path must
6. Choose the path to the directory containing the database-specific data files and
Teamcenter displays the Manufacturing Resource Library — Content Owner:
Name dialog box.
The plmxml_import utility uses this login information to import the data into
the Teamcenter database.
8. Click Next.
Teamcenter displays the Choose MRL Graphic Macros Directory dialog box
containing the default path to store graphic macros.
9. Verify that this path is the correct path or modify it by clicking Browse.
10. Click Start.

Teamcenter copies the graphic macros to the database and modifies the
NXGraphicsBuilder preference.
Updating the Manufacturing Resource Library from an earlier version

If you are upgrading from an earlier Teamcenter version, Teamcenter checks during
the Manufacturing Resource Library installation whether you have installed the
library or parts of it in an earlier installation. If this is so, you can choose to update
older data or install missing modules. Teamcenter automatically checks if a first
install (database population) or an update is required for an existing structure. The

update procedure is identical to the first install unless Teamcenter finds modules
that need updating.
To update the Manufacturing Resource Library from an earlier version:
2. Click Next.
3. Click Next.
4. Select Manufacturing Resources – Database Population.
5. Click Next.
6. Select the path to your Teamcenter installation and click Next. The path must
7. Select the path to the directory containing the database-specific data files and
Teamcenter displays the Manufacturing Resource Library – Content Owner:
Name dialog box.
The plmxml_import utility uses this logon information to import the data
into the Teamcenter database.
9. Click Next.
Teamcenter displays the Manufacturing Resource Library – Content Selection
dialog box.
10. Specify which types of data you want to load. You can choose from the following:
• Tools (Assemblies and Components)
• Machines
• Fixtures
• Weld guns
• Robots
• Templates (NX Manufacturing Setups)

Manufacturing
• Vendor catalog (sample)
11. Click Next.

Teamcenter displays the Current Kit Version Selection dialog box.
For each module, Teamcenter checks if the classification hierarchy was already
imported in a previous version. If it is not possible to evaluate the related
Manufacturing Resource Library version information for an existing module,
Teamcenter asks you to select the specific release that was used to import the
hierarchy of this module. This is, for example, the case for the weld guns module,
as there is no version history stored for this module.
12. Select the correct current installation version for each module that is displayed
and click Next.
When Teamcenter has gathered the missing version information, it displays the
Load CLASS HIERARCHY for Module(s) dialog box.
13. Select the modules for which the hierarchies should be imported or updated.
If those hierarchies already exist in the database, you can choose to update them.
Teamcenter displays the versions from which and to which it will update.
If Teamcenter cannot evaluate the version information for an existing module, it
asks you to enter that information manually.
14. Click Next.

Teamcenter displays the Import Guided Component Search (GCS) Data dialog
box.
15. Click Yes to load the GCS data or No to ignore this step.
For more information about using the guided component search, see the Resource
Manager Guide.
Teamcenter displays the Confirm Selections dialog box.
Warning
The update requires an extended period of time. The length of time
required depends on the performance of your hardware.
Upgrading the tool classification hierarchy can take up to 20 hours.
Teamcenter does the following during the update:

• Adds new classes to the hierarchy
• Adds new attributes to classes in the hierarchy
• Updates class images and hierarchy icons
For more information about the classes and attributes removed during the
update, see Deleted classes.

Deleted classes
• Classes that were deleted in the library since the last installation are not deleted
in your database so that any changes you have made in these are preserved.
• Attributes from the earlier version that are deleted in the later version are
removed from the view but not from the class.
The following lists the classes deleted from the Teamcenter 9.1 Manufacturing
Resource Library. If you do not use these, you can delete them manually.
Classes removed at Teamcenter 9.1
TA_MILL_20_30
TC_TURN_10_10_160
TC_TURN_10_20_140
TC_TURN_10_30_120
TC_TURN_10_40_140
TC_TURN_10_50_140
TC_TURN_10_60_140
TC_TURN_10_70_160
TC_MILL_10_80_900
TC_HOLDER_10_90_120
TC_HOLDER_10_90_130
TC_ADAPT_20
TC_ADAPT_20_00_100
TC_ADAPT_20_00_110
TC_ADAPT_20_00_120
TC_ADAPT_20_00_130
TC_ADAPT_20_00_140
TC_ADAPT_20_00_150
TC_ADAPT_20_00_160
TC_ADAPT_20_00_900
Planning data migration from Genius4000 to Resource Manager

The data in a Genius4000 installation is composed of database instances and
associated files, such as graphics files, part files, and text documents residing on
a file system.
Note
To migrate Genius4000 data from Teamcenter 9 onwards, you must do so by
installing Teamcenter 8.x (or earlier) and migrating the data using the Genius
data migration utility found in that installation.
Converting Genius4000 data to Resource Manager-compliant data involves the

following steps:
Step 1: Export data from the Genius4000 database.
This step performs two functions:
• Export the contents of the Genius4000 database to SML ASCII files

using the standard Genius SML Export function. The SML ASCII

Manufacturing
files are stored in an interim export directory where they are used as
input for the conversion process.
• Copy all associated files residing in the Genius4000 file system to the
Resource Manager import directories. Where necessary, these files
are converted to formats required for the import step.
Step 2: Convert the exported data to Resource Manager data.

This step converts the various data formats from Genius4000 and
converts them into formats required by Resource Manager. You have
some choice as to the final file types the system creates.
File conversion converts TOL files of records that do not have an
associated NX part file to NX part files. Since such files generally contain
2D graphics that cannot be converted to JT format, they are copied to
an intermediate directory (GeniusTolGraphics) and converted to CGM
format in a later conversion step. It also modifies the color tables of
HPGL files so that the embedded viewer displays them with the same
colors previously used by Genius4000 and UNC8500i.
Step 3: Import the Resource Manager data into the Teamcenter 8.x (or earlier)
Resource Manager database.
After you convert all the data, this step imports the results into an
existing Resource Manager database. This procedure is similar to that
required to install the small or full manufacturing content kit.
Step 4: Upgrade the Teamcenter 8.x (or earlier) database to your current
Teamcenter version.
For more information about using the migration utility, see the Installation on
Windows Servers Guide in the Teamcenter 8.x (or earlier) installation.

Chapter
15 Install EDA server support

Chapter
15 Install EDA server support
Install EDA server support

EDA server support adds the EDA data model to the existing Teamcenter data
model. Before installing EDA server support, you must have already installed the
Teamcenter server.
Note
You can also install EDA server support at the same time that you install
the Teamcenter server. However, the directions that follow only describe
installation of EDA server support and assume you have already installed
the Teamcenter server.

choose Run as administrator.
2. Proceed to the Features dialog box.

Note
If you are adding EDA server support to an already existing Teamcenter
server, select the Configuration Manager option to perform maintenance
on an existing installation and click Next until the Features dialog box
appears.
If this is a first-time installation, in the Solutions dialog box of the of
Teamcenter Environment Manager, select Corporate Server and click
Next.
3. In the Features dialog box, perform these steps:

a. Select the following options under the Extensions list:
• Under Mechatronics Process Management, select EDA Server Support.
Installs the EDA server components. This option installs EDA dataset
types and transfer modes.
• Under Enterprise Knowledge Foundation, select Dispatcher Server

(optional).
Installs the Dispatcher Dispatcher Server (Dispatcher Server) so that
you can translate CAD design files into viewable files. Users can view
and mark up the designs using a viewer such as InterComm.

Chapter 15 Install EDA server support
• Under Enterprise Knowledge Foundation, select Dispatcher Client

(optional).
Installs the Windows or UNIX service to enable translation of CAD
designs to a viewable file format.
If this is a first-time installation of the Teamcenter server, you should also

select the following option:
• J2EE Based Server Manager

Installs the pool manager. You must run the pool manager when users
connect to the server using the thin client (Web tier).
b. In the Installation Directory box, enter the location where you want to
install Teamcenter (the TC_ROOT). The EDA server files are installed to
an install\edaserver subdirectory.
c. Click Next.
4. Enter information as needed in subsequent panels.
5. In the Confirmation box, click Start. TEM installs EDA server components.
6. Obtain the license file that includes EDA licensing and install it on the licensing
server.
7. Verify the addition of the EDA data types to the server:

a. Run the Teamcenter rich client.
b. In the My Teamcenter application, choose File→New→Item.

The New Item dialog box is displayed.
c. Verify that the EDA, EDAComp, and EDASchem item types are added to the
list of types you can create. Choose one of the EDA item types and create
an instance.
d. Verify that the item instance is created.
8. Before you can save BOM data to EDA, an administrator must first populate the
database with components or change the EDA_CheckComponentExistence
preference from 1 (true) to 0 (false).

Chapter
16 Installing Teamcenter reporting

and analytics
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Create the Reporting and Analytics database . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Configure the Reporting and Analytics license file . . . . . . . . . . . . . . . . . . . . . 16-2
Install Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Install Remote Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Deploy Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Complete Reporting and Analytics installation . . . . . . . . . . . . . . . . . . . . . . . 16-5

Chapter
16 Installing Teamcenter reporting

and analytics
Installing Teamcenter reporting and analytics

Install and configure Teamcenter reporting and analytics in a new or existing
Teamcenter configuration.
Before you begin

Download the Teamcenter reporting and analytics software distribution image for
Windows from the Siemens PLM Software FTP site.
Reporting and Analytics requires additional preinstallation steps.
For information about steps to perform before you install Reporting and Analytics,
see the current version of the Teamcenter Reporting and Analytics Deployment
Guide in the Documentation directory in the Reporting and Analytics software
distribution image.
Create the Reporting and Analytics database

Reporting and Analytics requires an Oracle or Microsoft SQL Server database for
Reporting and Analytics metadata. Your database administrator must create this
database before you launch Teamcenter Environment Manager (TEM) to install
Reporting and Analytics.
TEM creates the required table structure for Reporting and Analytics, but the
database user and tablespaces must exist before you install Reporting and Analytics.
Metadata tables are divided into three categories based on the number of rows they
will hold and the growth potential. These tables can be stored in the same tablespace
or in separate tablespaces for better performance and manageability. Siemens PLM
Software recommends creating the following tablespaces:
Tablespace Description
Small Typical number of rows 1000. Minimum size 50MB Growth
is very slow.
Medium Typical number of rows 10000. Minimum size 150MB
Growth is Slow.
Large Typically 1000000 rows or more. Minimum size 500MB
Growth very rapid with usage.

Chapter 16 Installing Teamcenter reporting and analytics
Tablespace Description
Indexes Typically 1000000 rows or more. Minimum 400MB.
For more information about creating the metadata database for Reporting and
Analytics, see Planning for Installation in the Teamcenter Reporting and Analytics
Deployment Guide for the current version of Reporting and Analytics.
Configure the Reporting and Analytics license file

Reporting and Analytics requires an eQube license file (license.dat) on the host
where the Reporting and Analytics license server runs. TEM requires the location of
the license file to install the Reporting and Analytics license server during Reporting
and Analytics installation.
Note
The Reporting and Analytics license server uses the host’s MAC address to
identify the host. You must supply this information when you request a
Reporting and Analytics license file from eQ Technologic.
Note
For information about starting the Reporting and Analytics license server, see
the Teamcenter Reporting and Analytics Deployment Guide in the Reporting
and Analytics software distribution image.
Install Reporting and Analytics

1. Launch TEM.
2. Create a new Teamcenter configuration or select an existing configuration to

which you want to add Reporting and Analytics.
In the Features panel, select the following features:
Teamcenter for Reporting and Analytics

Installs the Teamcenter Reporting and Analytics integration.
Reporting and Analytics is a standalone reporting application that introduces
a new folder in Report Builder called TcRA Reports, which contains reports
created with Reporting and Analytics.
Dashboard
Installs the Reporting and Analytics Dashboard application for the rich
client. Dashboard provides an embedded viewer for Reporting and Analytics
reports in the rich client.
For more information about the Reporting and Analytics Dashboard, see the
Report Builder Guide.

3. Proceed to the TcRA Install Options and General Settings panel. Select one
or more of the following options to include in your Reporting and Analytics
installation:
Create license server Specifies you want to install a Reporting and

Analytics license server. If you select this
option, TEM later prompts for the location of
the eQube license file (license.dat). If you do
not select this option, TEM later prompts for
the location of the Reporting and Analytics
license server.
Create WAR file Specifies you want to generate a Reporting
and Analytics WAR file.
Create metadata Specifies you want to populate the metadata
database for Reporting and Analytics. Select
this only during the first installation of
Reporting and Analytics. If you are upgrading
from a previous version of Reporting and
Analytics or adding additional hosts, do not
select this option.
Secure Connection Specifies you want to connect to the Reporting
and Analytics license server through a secure
(HTTPS) connection.
The remaining sequence of TEM panels varies according to the options you select.
4. Enter the required information in TEM for the selected Reporting and Analytics
options.
Note
For more information about any TEM panel, click the help button .
Selected option TEM panel Tasks

Create license TcRA License Server Settings Enter the location of the Reporting and
server Analytics license file (license.dat), the
license authentication time-out in seconds,
and license keystore settings for the
Reporting and Analytics license server.
Create WAR file TcRA WAR Settings Type the Web application context, server
name, and port for the Reporting and
Analytics Web application.
Create WAR file TcRA WAR SMTP Properties Specify SMTP settings to enable users
to receive e-mail messages generated by
Reporting and Analytics.
Create WAR file TcRA Web Parts and Services Specify whether to enable Web services and
integration with SharePoint and Teamcenter
community collaboration with Reporting
and Analytics.

Selected option TEM panel Tasks

Create WAR file TcRA Authentication Settings Select the Reporting and Analytics
authentication method (eQube, SSO, or
Windows NTLM) and specify related
settings.
Note
Selecting SSO Authentication
requires that you install Teamcenter
with Security Services enabled and
configure the LDAP server before you
install Reporting and Analytics.
For information about installing
Security Services, see the Security
Services Installation/Customization
guide.
Create WAR file TcRA License Settings Type the host and port of the Reporting and
Analytics license server.
Create WAR file TcRA WAR and Metadata Type an owner for Reporting and Analytics
Settings metadata and select your Web application
Create metadata server vendor.
or
Create metadata TcRA Metadata Settings Specify metadata settings for the Reporting
and Analytics integration.
Note
The values you type under Oracle
Tablespace Names must match the
names of the Oracle tablespaces you
created in Create the Reporting and
Analytics database.
Any option TcRA Database Selection Specify the database engine you use for
Reporting and Analytics (Oracle, Microsoft
SQL Server, or IBM DB2) and type the
required values for the Reporting and
Analytics database you created in Create the
Reporting and Analytics database.
5. Proceed through the remaining TEM panels and begin installing Reporting
and Analytics.
During installation, TEM prompts you for the location of the TCRA2008.zip file.
When installation is complete, close TEM.

Install Remote Reporting and Analytics

Install Remote Reporting and Analytics as described in Deploying Remote
Teamcenter Reporting and Analytics Plugin in the Teamcenter Reporting and
Analytics Deployment Guide.
The Teamcenter Reporting and Analytics Deployment Guide is in the
Documentation directory in the Teamcenter reporting and analytics software
distribution image.
Deploy Reporting and Analytics

Deploy the Reporting and Analytics WAR file as described in the Teamcenter
Reporting and Analytics Deployment Guide in the Reporting and Analytics software
distribution image.
Note
Before you deploy the Reporting and Analytics WAR file, make sure that
Remote Reporting and Analytics is installed and running.
For more information, see Deploying Remote Teamcenter Reporting and
Analytics Plugin in the Teamcenter Reporting and Analytics Deployment
Guide.
The Teamcenter Reporting and Analytics Deployment Guide is in the
Documentation directory in the Teamcenter reporting and analytics
software distribution image.
Complete Reporting and Analytics installation

1. Set the TC_RA_server_parameters preference using the rich client. Set the
following values:
Value Description
Host Specifies the host on which you deploy the
Reporting and Analytics WAR file.
Port Specifies the port used by the Reporting and
Analytics Web application.
Context Specifies the name of the Reporting and
Analytics WAR file
ServletName Specifies the name of the Reporting
and Analytics servlet, for example,
BuildNPlay/eQTCnectIntegrationController.
This preference must be set to enable Reporting and Analytics to communicate

with Teamcenter.
For information about setting preferences, see Getting Started with Teamcenter.

2. Test connections to Reporting and Analytics applications. Log on to Reporting

and Analytics at the following URLs and click Test Connections:
Teamcenter reporting and analytics Mapper:
http://host:port/Reporting and Analytics-context/Mapper
Teamcenter reporting and analytics BuildNPlay:

http://host:port/Reporting and Analytics-context/BuildNPlay
Reporting and Analytics Portal:

http://host:port/Reporting and Analytics-context/Portal
If connections are not successful, you cannot create reports in Reporting and
Analytics until connection problems are resolved.
For more information about Reporting and Analytics Mapper and BuildNPlay,
see the Mapper User’s Guide and the BuildNPlay User’s Guide in the Reporting
and Analytics software distribution image.
3. Log on to the Reporting and Analytics administrative console using user name
ADMIN and password ADMIN.
Click Manage Instance→Properties, and then set the following values as
appropriate:
• SMTP Host
• Authentication required for SMTP (Set to True or False)
• SMTP User ID
• SMTP User Password
4. If Reporting and Analytics is installed with Security Services enabled, set the
following values for the Teamcenter connection (Connection 1):
• Set the user ID and password values to the LDAP user ID and password.
• Under Advanced Properties, set SSO Enabled to yes, and set the SSO
Application ID to the Teamcenter application ID.
Note
For information about using the Reporting and Analytics integration, see the
Report Builder Guide.

Chapter
17 Installing Render Management

Chapter
17 Installing Render Management
Installing Render Management

During installation using Teamcenter Environment Manager (TEM), along with the
selections made to support general installation, your administrator must select to
install the following features to support document rendering. The administrator can
accept default values unless otherwise directed.
Note
This topic describes an installation using a single server machine. Installation
in a distributed configuration using multiple server machines is supported.

Chapter
18 Installing Teamcenter online help
Install online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4

Install online help using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Install online help manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Install online help on the J2EE Web tier . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Install online help on the .NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Configure online help access for Teamcenter clients . . . . . . . . . . . . . . . . . . . 18-10

Configure online help for the thin client . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Configure online help for the rich client . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
Configure online help for the rich client distribution instance . . . . . . . . . 18-12

Chapter
18 Installing Teamcenter online help
Installing Teamcenter online help

Teamcenter provides an online help collection that contains guides for all Teamcenter
applications and clients. This collection can be viewed in a Web browser.
The collection is available in HTML and PDF formats.
Teamcenter HTML online help collection

Chapter 18 Installing Teamcenter online help
Teamcenter PDF online help collection

Teamcenter online help requires a supported Web browser and the appropriate Java
plug-in for your platform. The PDF online help collection requires a PDF reader
or Web browser plug-in.
For information about supported Web browsers and Java versions, see the Siemens
PLM Software Certification Database:
For information about using Teamcenter online help, see Getting Started with
Teamcenter.
You can access the Teamcenter online help collection directly from the documentation
distribution image, by installing the collection to a local host or Web server, from a
Teamcenter client, or from GTAC.

Access to Teamcenter online help collection HTML PDF

Directly from documentation distribution image1 •
Installed on a local host or network file location • •
Installed on a Web server2 • •
Installed in a rich client configuration3 •
Installed in a thin client Web application3 •
Directly from GTAC4 • •
Notes:
1. See the PDF directory on the documentation distribution image. No installation

is required.
2. For the PDF collection, full-collection search is not available over HTTP
protocol.
3. Access online help through the Help menu in the client.

For more information see Getting Started with Teamcenter.
4. The HTML and PDF online help collections for the current version of
Teamcenter are available at the following URL:
http://support.industrysoftware.automation.siemens.com/docs/teamcenter
If you install online help in a rich client configuration using TEM, online help access
from the rich client is configured automatically.
If you install online help in a thin client Web application, online help access from the
thin client is configured automatically.
If you install online help on a separate host or in a separate Teamcenter
configuration, you can configure clients to access those separate online help
installations.
After online help for the rich client or thin client is installed and configured, you can
view online help from the Help menu in the client.
For more information, see Getting Started with Teamcenter.
Note
• Teamcenter Client for Microsoft Office and the Business Modeler IDE
client contain their own online help, but do not include the complete
online help collection.
For more information, see the Client for Microsoft Office Guide or the
Business Modeler IDE Guide.
• The PDF online help collection is not accessible though the Help menu in
Teamcenter rich client or thin client.

Install online help

Install online help using the method appropriate to your needs:
• Install online help in a local rich client configuration using TEM.
• Install online help manually on a local host or network file location from the
documentation distribution image.
• Install online help on the .NET Web tier.
• Install online help on the J2EE Web tier.
If you want to configure clients to access online help installed on a separate host,
see Configure online help access for Teamcenter clients.
Install online help using TEM

1. Launch Teamcenter Environment Manager (TEM).
2. Create a new Teamcenter configuration or select the existing configuration to

which you want to add online help.
3. Proceed to the Features panel.
4. Under Server Enhancements, select the Online Help feature.
5. Proceed to the Online Help panel. Select the online help components you want
to install.
Component Description
Teamcenter online help library Installs the Teamcenter online help library.
This component is required.
This component requires approximately 561
MB of disk space.
Teamcenter developer Adds the Teamcenter developer references
references to the online help collection. The following
references are added to the Developer
References for Customization group in the
online help library:
• C++ API Reference
• Integration Toolkit (ITK) Function
Reference
• Services Reference

MB of additional disk space.

Component Description
Teamcenter Data Model Adds the Teamcenter Data Model Report to the
Report Developer References for Customization group
in the online help library.
The Teamcenter Data Model Report contains
documentation on standard Teamcenter
data model objects, such as business objects,
classes, attributes, properties, lists of values
(LOVs), and others.
This component requires approximately 3.44
GB of additional disk space and requires
significantly more time to install.
Teamcenter PDF help Installs the Teamcenter online help collection
collection in PDF format on your local host.
After installation, you can open the online
help collection from the following location:
TC_ROOT\PDF\index.html
MB of additional disk space.
6. Proceed to the Confirmation panel, and then click Start to install online help.
During installation, TEM prompts for the location of the online help files.
Enter the path to the location that contains these files on the Teamcenter
documentation distribution image.
TEM places files in

File Description this directory
tchelp.jar Online help library TC_ROOT\help
tcrefs.jar Developer references TC_ROOT\help
DataModelReport.zip Data Model Report TC_ROOT\help
PDF.zip PDF help collection TC_ROOT\PDF
Note
• You can later add or remove online help components using TEM in
maintenance mode:
1. Proceed to the Feature Maintenance panel.
2. Under Online Help, select Add Help Files.
3. In the Online Help panel, select online help components to add or clear
components you want to remove.
• After you install online help using TEM, you can view online help from
the Help menu in the rich client.

For more information, see Getting Started with Teamcenter.
Install online help manually

1. Locate the online help files on the Teamcenter 9.1 documentation distribution
image.
2. Extract online help files to a directory on your local host or a network file location.
File Description
tchelp.jar Contains the Teamcenter online help library. This
file is required and must be extracted before any
other online help files.
This file requires approximately 561 MB of disk
space.
tcrefs.jar Contains the Teamcenter developer references.
This file is optional.
Extracting this file added the following references
to the Developer References for Customization
group in the online help library:
• Integration Toolkit (ITK) Function Reference
This component requires approximately 629 MB

of additional disk space.
DataModelReport.zip Contains the Teamcenter Data Model Report. This
file is optional.
Extracting this file adds the Teamcenter Data
Model Report to the Developer References for
Customization group in the online help library.
documentation on standard Teamcenter data
model objects, such as business objects, classes,
attributes, properties, lists of values (LOVs), and
others.
This component requires approximately 3.44 GB
PDF.zip Contains theTeamcenter online help library in
PDF format. This file is optional.
3. If you want other hosts to access online help, set permissions for the HTML
online help directory (help) or the PDF online help directory (PDF) as needed
to allow access to other hosts.

After installation, you can open the online help collection from the following
locations:
• HTML online help:

help-directory\help\index.html
• PDF online help:

help-directory\PDF\index.htm
You can use this same method to install the online help on a Web (HTTP) server.
Rich client or thin client hosts can be configured to access the HTML online help
collection over a Web server.
For more information, see Configure online help access for Teamcenter clients.
Note
The PDF online help collection cannot be accessed through the rich client
or thin client.
Install online help on the J2EE Web tier

You can install online help on the J2EE Web tier as part of a thin client Web
application. This provides online help for the thin client that can also be accessed by
rich clients as described in Configure online help access for Teamcenter clients.
2. Click Add to create a new Web application.
3. In the Add Web Application dialog box, type a name and enter a staging location
for the online help Web application.
In the Solution Type box, select Thin Client.
4. In the Disk Locations for Install Images box, enter the path to the tchelp.jar
file on the Teamcenter 9.1 documentation distribution image.
5. Click Solutions.
6. In the Select Solutions dialog box, select the Teamcenter - Online Help solution,
and then click OK.
7. In the Add Web Application dialog box, click OK.
8. In the Modify Required Context Parameters dialog box, click OK.

The Web Application Manager builds the online help Web application.
9. Locate the deployable file generated during installation. This file is in the
deployment directory under the specified staging location.


Guide.1
After you install online help using TEM, you can view online help from the Help
menu in the thin client.
For more information see Getting Started with Teamcenter.
Note
• Additional online help components, such as the Teamcenter developer
references and Teamcenter Data Model Report, cannot be installed on
the J2EE Web tier. The Web Application Manager installs only the core
Teamcenter online help library.
• If you have additional thin client Web applications that do not contain
online help, you can configure those applications to access online help
installed in another thin client Web application.
For more information, see Configure online help for the thin client.
Install online help on the .NET Web tier

To configure Teamcenter online help for the .NET Web tier thin client and four-tier
rich client, you must create a virtual directory that contains the online help files.
1. Locate the online help files on the Teamcenter 9.1 documentation distribution
image.
2. Extract online help files to a directory on your Microsoft Internet Information

Server (IIS) host.
File Description
tchelp.jar Contains the Teamcenter online help library.
This file is required and must be extracted before
any other online help files.
This file requires approximately 561 MB of disk
space.

File Description
tcrefs.jar Contains the Teamcenter developer references.
Extracting this file added the following references
to the Developer References for Customization
group in the online help library:
• Integration Toolkit (ITK) Function Reference

DataModelReport.zip Contains the Teamcenter Data Model Report.
Extracting this file adds the Teamcenter Data
Model Report to the Developer References for
Customization group in the online help library.
documentation on standard Teamcenter data
model objects, such as business objects, classes,
attributes, properties, lists of values (LOVs), and
others.
This component requires approximately 3.44 GB
3. In the Internet Information Services (IIS) Manager, under your Teamcenter Web
site, create a virtual directory named help. Set the physical path for this virtual
directory to the location in which you extracted Teamcenter online help files.
4. Configure MIME types to enable online searching of the online help collection:
a. In IIS Manager, in the list of sites, select the Teamcenter application name
(for example, tc) and open the properties pane or dialog box for this site. (The
method for viewing properties varies depending on your version of IIS.)
b. In the properties pane or dialog box, click MIME Types.
c. In the MIME Types dialog box, add the following file extensions to the table
of MIME types:
Extension MIME type

.prm application/octet-stream
.jqf application/octet-stream
.cfs application/octet-stream
.json application/octet-stream

d. After you complete adding MIME types, restart IIS using the appropriate
method for your version of IIS.
5. Launch Teamcenter and modify the following Teamcenter preferences to add

the full path to the online help files:
Preference Description
WEB_core_help_server Set to the full path to the launch page for the
online help collection, including the application
name, for example, /tc/help/index.html.
WEB_help_server Set to the URL of the thin client help, for
example, /tc/help/index.html
#filename:thin_client_dhtml:getting_started
For more information about these preferences, see the Preferences and
Environment Variables Reference.
For information about setting preferences, see the Preferences and Environment
Variables Reference.
Configure online help access for Teamcenter clients

Configure access to installed online help for rich client and thin client hosts.
Note
If you install online help in a rich client configuration using TEM as described
in Install online help using TEM, no further configuration is needed to access
to online help.
Configure online help for the thin client

If your thin client Web application contains the Teamcenter - Online Help solution,
no further configuration is needed to enable online help.
To enable a thin client to access online help installed in a separate Web applications,
launch the thin client and modify the following Teamcenter preferences to add the
full path to the online help files.
Preference Description
WEB_core_help_server Set to the full path to the launch page for the
online help collection, including the application
name, for example, /tc/help/index.html.
WEB_help_server Set to the URL of the thin client help, for
example, /tc/help/index.html
#filename:thin_client_dhtml:getting_started
For more information about these preferences, see the Preferences and Environment
For information about setting preferences, see the Preferences and Environment

Note
This procedure assumes you have an existing deployed thin client Web
application that contains the Teamcenter - Online Help solution.
For information about creating a thin client Web application that contains
Teamcenter online help, see Install online help on the J2EE Web tier.
Configure online help for the rich client

Configure access to online help installed on a separate host in a new or existing
rich client configuration.
1. If you access online help from a network file location, use Windows Explorer to
map a drive letter from the client host to the location of the installed online
help, for example, e:.
Note
A mapped drive is necessary because on Windows systems, the rich client
cannot access online help from a UNC path.
2. Launch TEM.
3. Create a new Teamcenter configuration or perform maintenance on an existing

configuration.
• New configuration:
a. Proceed to the Features panel.
b. Select the two-tier or four-tier rich client, but do not select the Online
Help feature.
Note
For more information about installing a two-tier or four-tier rich
client, see the Installation on Windows Clients Guide.
• Existing configuration:
a. Proceed to the Feature Maintenance panel.
b. Under Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier,

select Modify settings.
4. Proceed to the Rich Client Settings panel. Select the Enable online help check
box.
5. In the Rich Client Settings panel, select the Enable online help check box, and
then specify how you want the rich client to access online help.
• Direct access from a network file location:
a. Select Help Files Directory.
b. Enter the path to the installed online help, for example, e:.

• Access from a Web server:

a. Select Web Server URL.
b. Type the URL to the location of the Teamcenter online help collection,
for example, http://host:port/tc/help.
6. Proceed to the Confirmation panel, and then click Start to update the Teamcenter
configuration.
Configure online help for the rich client distribution instance

1. If you access online help from a network file location, on each rich client host,
use Windows Explorer to map a drive letter from the client host to the location of
the installed online help, for example, e:.
Note
A mapped drive is necessary because on Windows systems, the rich client
cannot access online help from a UNC path.
This step is not needed if you access online help from a Web server.
3. Create or modify a rich client distribution instance.

In the Modify Required Context Parameters dialog box, specify how you want
the rich client to access online help by setting context parameters as follows.
• Direct access from a network file location.
Context parameter Value

RichClientHelpWebServer Specify file://.
RichClientHelpLocation Specify the path to the location that contains
the online help collection for both Windows
and UNIX systems.
The Web Application Manager appends
index.html to this path.
• Access from a Web server.
Context parameter Value

RichClientHelpWebServer Specify http://host-name:port, replacing
host-name and port with the host name
and port for the deployed thin client Web
application that contains the online help (the
Teamcenter - Online Help solution).
RichClientHelpLocation Specify the subpath to the deployed Web
application, for example, tc/help.
The Web Application Manager appends
index.htm to this path.

For more information about these parameters, see Rich client distribution
instance requirements.
Note
For more information about creating a rich client distribution instance,
see Install rich client distribution instances.
For more information about modifying an existing rich client distribution
instance, see Add components to the distribution server instance.
4. After you set context parameters, click OK.

The Web Application Manager updates the rich client distribution instance.

Part
VI Additional configuration and

maintenance
Create additional Teamcenter configurations, apply patches, or uninstall Teamcenter

as described in the appropriate topics.

Chapter
19 Managing installations and

configurations
Create a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Modify a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Add an existing Teamcenter database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Add or configure a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Configure multiple databases for a four-tier rich client . . . . . . . . . . . . . . . . . . 19-5

Multiple database overview (four-tier rich client) . . . . . . . . . . . . . . . . . . . 19-5
Multiple database example (four-tier rich client) . . . . . . . . . . . . . . . . . . . 19-6
Step 1: Install the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Step 2: Deploy the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Step 3: Configure the rich client instance . . . . . . . . . . . . . . . . . . . . . 19-9

Chapter
19 Managing installations and

configurations
Managing installations and configurations

A Teamcenter configuration is a collection of features associated with one Teamcenter
data directory. The collection of configurations that share the same Teamcenter
application root directory is a Teamcenter installation.
When you installed Teamcenter executables using Teamcenter Environment
Manager from the software distribution image, you created the first configuration.
You can create a new Teamcenter configuration or modify features in your existing
Teamcenter configuration using Teamcenter Environment Manager.
Create a configuration
1. Launch Teamcenter Environment Manager. In the Windows start menu, choose
Note
You can also run the tem.bat file in the install directory in the application
root directory for the Teamcenter installation. Right-click the tem.bat
program icon and choose Run as administrator.
2. In the Maintenance panel, choose Configuration Manager.
3. In the Configuration Maintenance panel, choose Create new configuration.
4. In the Configuration panel, type a description and unique ID for the new
configuration.
5. In the Solutions panel, optionally select one or more solutions.

For a description of a solution, point to the solution name in TEM or see
Teamcenter solutions.
Note
Solutions are preselected groups of features that provide starting points
for recommended Teamcenter configurations. You can add features or
deselect features in the Features panel in Teamcenter Environment
Manager (TEM).

Chapter 19 Managing installations and configurations
6. In the Features panel, select features to include in the configuration.

For a description of a feature, point to the feature name in TEM or see
Teamcenter features.
7. Proceed through the remaining panels in TEM, entering the required

information for the features you selected.
For information about each panel, click the help button .
8. When TEM displays the Confirmation panel, click Start to begin installation.
Modify a configuration
Add Teamcenter features to an existing configuration, or remove them from a
configuration:
Note
program icon and select Run as administrator.
2. In the Maintenance panel, choose Configuration Manager.

existing configuration.
4. In the Old Configuration panel, select the configuration you want to modify.
5. In the Feature Maintenance panel, select Add/Remove Features.

Note
Options in the Feature Maintenance vary depending on the features in
your configuration.
For information about other options, see Teamcenter Environment
Manager Help.
6. In the Features panel, select features to add to the configuration, or deselect

features you want to remove.
7. Proceed through the remaining panels in TEM, entering the required

information for the features you selected.
For information about each panel, click the help button .
8. When TEM displays the Confirmation panel, click Start to begin installation.

Add an existing Teamcenter database

You can add a Teamcenter database to an installation by creating a configuration
that references an existing Teamcenter data directory and its configured database. A
data directory is associated with one (and only one) database instance.
Note
program icon and choose Run as administrator.
2. In the Configuration Maintenance panel, select Add new configuration.
3. In the Configuration panel, enter a description of and unique ID for the

configuration you are creating.
4. Proceed to the Features panel. Select the Teamcenter Foundation feature only
and specify an installation directory for the new configuration the Installation
Directory box. The installation directory must not already exist on your system.
(TEM creates the directory.)
5. In the Foundation panel, select Use populated database and existing data
directory and enter the full path to the existing data directory in the Data
Directory Location box.
6. In the Data Directory box, enter a location for the Teamcenter data directory.
The directory must exist.
shared data subdirectories and files in this location.
7. In the Teamcenter Administrative User panel, enter the password for the
Teamcenter administrator.
Caution
Make sure the password does not contain any of the following characters:
@$%’": ;.<>(){}
8. In the Confirmation panel, review your selections and click Start to add the
database.

Add or configure a database

You can simultaneously configure a Teamcenter database and add it to an installation
by creating a new configuration. Because you are configuring a database, you must
also install and configure File Management System and create a data directory.
Prerequisites:
• A database server must be installed (IBM DB2, Oracle, or MS SQL Server).
• A database instance must exist, either a specific instance configured for

Teamcenter or a multipurpose instance to be configured in this procedure.
For information about installing a database server and database instances, see
Database server installation.
Note
program icon and select Run as administrator.
2. In the Configuration Maintenance panel, select Add new configuration.
3. In the Configuration panel, enter a description of and unique ID for the

configuration you are creating.
4. Proceed to the Features panel. Select the Teamcenter Foundation feature only
and specify an installation directory for the new configuration the Installation
Directory box. The installation directory must not already exist on your system.
(TEM creates the directory.)
5. In the Foundation panel, select Create new data directory using existing
populated database.
6. In the Foundation Database panel, enter access information for the existing
database.
In the Data Directory box, enter a location for the Teamcenter data directory.
The directory must exist.
shared data subdirectories and files in this location.
7. In the Teamcenter Administrative User panel, enter the password for the
Teamcenter administrator.

Caution
Make sure the password does not contain any of the following characters:
@$%’": ;.<>(){}
8. In the Confirmation panel, review your selections and click Start to add the
database.
Configure multiple databases for a four-tier rich client

Configure the rich client to access multiple databases.
Multiple database overview (four-tier rich client)

To configure a four-tier rich client with access to multiple databases, install a
Teamcenter corporate server, including a server manager, for each database and
deploy a Web tier EAR file for each server manager. For example, to configure rich
client access to two databases, configure:
• In the enterprise tier, install two corporate servers with server managers and
connect each server to a different database.
• In the Web tier, deploy two Web tier files, each connecting to one of the server
managers.

Four-Tier
Rich Client
FSC Parent=
TcHost1:4444
http://appserver:7001/tc/webclient http://appserver:7002/tc/webclient
tc.ear tc.ear
TreeCache= TreeCache=
ClusterTcData1 ClusterTcData2
<fmsworld>
<multisiteimport siteid="400783129"> FMS
<defaultfscimport fscid="FSC_TcHost2 FSC_TcHost2
fscaddress="TcHost2:4444" priority="0"/>
</multisiteimport>
Server Manager
Server Manager
TreeCache=
TreeCache= ClusterTcData2
ClusterTcData1
TC Server n TC Server n
TcHost1 TcHost2
TcData1 TcData2
Multiple databases (four-tier rich client)
Multiple database example (four-tier rich client)

This example describes a sample scenario for configuring multiple databases.
Step 1: Install the corporate server
To enable a rich client to access two databases, install and configure two corporate
servers:

Note
For the complete procedure, see Teamcenter server installation.
1. Using Teamcenter Environment Manager, install Teamcenter in a corporate

server configuration on host 1 (TcHost1):
• Configure the corporate server to connect to database 1 (TcData1).
• Select the server manager component and configure it with the TreeCache
cluster name of ClusterTcData1.
2. Using Teamcenter Environment Manager, install Teamcenter in a corporate

server configuration on host 2 (TcHost2):
• Configure the corporate server to connect to database 2 (TcData2).
• Select the server manager component and configure it with the TreeCache
cluster name of ClusterTcData2.
3. On TcHost1, edit the FMS master file to make FMS aware of the FSC on
TcHost2:
a. Go to the fms directory in the Teamcenter application root directory.
b. Open the fmsmaster_FSC_service-id.xml file and find the following lines:

<fmsworld>
<multisiteimport siteid="othersite">
<fscimport fscid="otherfsc" fscaddress="host:4444">
<volumeimport volumeid="othervol" />
</fscimport>
</multisiteimport>
c. Edit the lines, adding the bold text and deleting the indicated text:
Original:
<fmsworld>
<defaultfscimport fscid="otherfsc" fscaddress="host:4444" priority=”0”/>
<volumeimport volumeid="othervol" />
</fscimport>
</multisiteimport>
Revised:
<fmsworld>
<defaultfscimport fscid="otherfsc" fscaddress="host:4444" priority=”0”/>
</multisiteimport>
d. In the revised section:

• Replace the value for the siteid parameter with the FMS enterprise
ID of the FSC on TcHost2. This value is in the FMS master file on
TcHost2 in the fmsenterprise id parameter.
• Replace the value for the fscid parameter with the FSC ID on TcHost2.
This value is in the FMS master file on TcHost2 in the fsc id parameter.

• Replace the value for the fscaddress parameter with the host name and
port number of host 2. This value is in the FMS master file on TcHost2
in the fsc address parameter.
For example:
<fmsworld>
<multisiteimport siteid="400783129">
<defaultfscimport fscid="FSC_TcHost2" fscaddress="TcHost2:4444" priority=”0”/>
</multisiteimport>
e. On TcHost1, stop and restart the FSC service.
Step 2: Deploy the Web tier

Deploy and configure the Web tier EAR files to connect to the server managers:
Note
For the complete procedure, see J2EE Web tier installation.
1. Generate the Web tier EAR file, configuring it to connect to the server manager
of TcHost1 by specifying the same values for the TreeCache cluster name and
TreeCache mode.1
For example:
TcHost1 server manager Web tier application

TreeCache cluster name: TreeCache cluster name:
TreeCache mode: TCP TreeCache mode: TCP
2. Generate the Web tier EAR file, configuring it to connect to the server manager
of TcHost 2 by specifying identical values for the TreeCache cluster name and
TreeCache mode.
For example:
TcHost 2 server manager Web tier application

TreeCache cluster name: TreeCache cluster name:
TreeCache mode: TCP TreeCache mode: TCP
Note
Make sure you choose distinct sets of ports for each EAR file.
3. Deploy each Web tier EAR file in a third-party application server in a separate
domain.
The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jgroups.org.

Users who install this rich client instance, can choose from two databases, TcData1
and TcData2, when logging on to Teamcenter.
Step 3: Configure the rich client instance
Configure the rich client distribution instance to include the two databases:
Note
For the complete procedure, see Installing rich client Web applications.
1. For the ParentFSCAddressTable parameter, specify the host name and port
number of TcHost1. For example:
TcHost1:4444
TcHost1 has the site information about the FSC on TcHost2.
2. For the HTTPServerTable parameter, specify two URLs, one for each deployed
Web tier application. For example:
URI Name
http://appserver:7001/tc/webclient TcData1
http://appserver:7002/tc/webclient TcData2

Chapter
20 Deploying localized versions

of Teamcenter
Configuring client display language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2

Choose a display language for the thin client . . . . . . . . . . . . . . . . . . . . . . 20-2
Choose a display language for the rich client . . . . . . . . . . . . . . . . . . . . . . 20-3
Environment settings for non-English locales . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Deploying localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

Deploying thin client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Update thin client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Create a thin client localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
Convert the thin client user interface for Hebrew . . . . . . . . . . . . . . . . 20-8
Deploying rich client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9
Display Siemens PLM Software-provided rich client localizations . . . . 20-9
Update rich client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-9

Chapter
20 Deploying localized versions

of Teamcenter
Deploying localized versions of Teamcenter

Siemens PLM Software provides localized versions of Teamcenter in the following
languages:
Language Locale code

Chinese (Simplified) zh_CN
Chinese (Traditional) zh_TW
Czech cz_CZ
English en_US
French fr_FR
German de_DE
Hebrew en_US1
Italian it_IT
Japanese ja_JP
Korean ko_KR
Polish pl_PL
Portuguese (Brazilian) pt_BR
Russian ru_RU
Spanish es_ES
Use the appropriate locale codes to deploy Teamcenter localizations or launch

Teamcenter clients in a desired locale.
If you provide your own localizations for locales not provided by Siemens PLM
Software, use the appropriate Java standard locale codes similar to the locale codes
in the preceding table.2
For more information about localizing Teamcenter, see the Localization Guide.
1. The locale code for Hebrew is en_US because Siemens PLM Software does not yet provide a Hebrew translation. The en_US code
allows data entry in Hebrew, but interface text is in English.
2. Standard locale codes are composed of a two lowercase character language code from the ISO 639-1 standard, followed by an
underscore, followed by a two uppercase character country code from the ISO 3166-1-alpha-2 standard.

Chapter 20 Deploying localized versions of Teamcenter
Configuring client display language

By default, Teamcenter clients display in the language specified by your operating
system locale settings. If you want to override the default language, perform the
appropriate procedure to choose the display language for the thin client or the rich
client.
Choose a display language for the thin client

At each logon, you can choose between multiple languages, depending on your
company’s policy and installation. There are two ways you can specify the language:
• Specify the language in the URL. For example:
o To specify French, type http://sdlc:7001/tc/webclient?lang=fr in the URL.
o To specify Russian, type http://sdlc:7001/tc/webclient?lang=ru in the URL.
Note
When specifying a language in the URL, use standard W3C locale
identifiers.
For more information, see the following URL:
http://www.w3.org/TR/ltli/
• Specify the language in your browser preferences. For example, in Microsoft

Internet Explorer, perform the following steps:
1. Choose Tools ® Internet options....
2. Click Languages in the Internet Options dialog box.
3. Click Add in the Language Preference dialog box.
4. Click any language in the Add Language dialog box.
5. Click OK in the Add Language dialog box.
6. Click the language you want to see in the user interface in the Language
Preference dialog box.
7. Click the Move Up button.

Note
The language you move to the top of the list in the Language
Preference dialog box is the language you see in the user interface.
8. Click OK in the Language Preference dialog box.
9. Click OK in the Internet Options dialog box.
10. Log on and view the user interface in the language you chose.

Note
An error message is displayed if the specified language is unavailable.
Your ability to set the language for the thin client depends on the character set
encoding of the Teamcenter server host and also the character set encoding of the
Teamcenter database.
Note
To prevent mixed-language display after you change the thin client display
language, clear your Web browser cache. This prevents the interface from
displaying in mixed languages.
For more information about configuring language display during installation, see
Installing thin client Web applications.
Choose a display language for the rich client

By default, the rich client is displayed in the language specified by the operating
system.
Note
Your ability to set the language for the rich client depends on the character set
encoding of the Teamcenter server host and also the character set encoding
of the Teamcenter database.
For more information about configuring language display during installation,
see Installing rich client Web applications.
Note
If you find that Asian multibyte characters do not display correctly in the rich
client, set your system font to a font that supports Asian multibyte characters.
For example, on Microsoft Windows systems, the Arial Unicode MS font can
be set to Message Box to correct this problem.
Similarly, if you find that Asian multibyte characters do not display correctly
when you start the rich client using the native language (-nl) option, restart
your system in the appropriate locale and set your system font to a font that
supports Asian multibyte characters.
If you want to override the default language to launch the rich client in a desired
language, add the -nl argument to the rich client launch command:
TC_ROOT\portal.bat –nl locale-code
Replace TC_ROOT with the Teamcenter home directory, and replace locale-code with
the desired locale code listed in Deploying localized versions of Teamcenter.
For example, to launch the rich client Italian user interface, enter the following
from a command prompt:
D:\tc\rac\portal.bat –nl it_IT

Alternatively, on Windows systems, you can customize the properties for the
Teamcenter rich client desktop shortcut icon to specify a desired language:
1. On your desktop, right-click the Teamcenter rich client shortcut icon .
2. Choose Properties.
A properties dialog box is displayed.
3. Click the Shortcut tab.
4. In the Target box, add an -nl argument to specify the desired language.
The -nl argument accepts a single string as value. The string must be one of the
locale codes listed in Deploying localized versions of Teamcenter.
For example, to run the rich client Italian user interface:
D:\tc\rac\portal.bat
becomes:
D:\tc\rac\portal.bat —nl it_IT
Note
To prevent mixed-language display the next time you run the rich client
after you change the –nl argument value, or after you change your operating
system locale, delete the Teamcenter directory under your user directory
(C:\Documents and Settings\user-name\Teamcenter).
Environment settings for non-English locales

Teamcenter is supported in the following locales on all server platforms:
• Chinese (Simplified)
• Chinese (Traditional)
• Czech
• English
• French
• German
• Hebrew
• Italian
• Japanese
• Korean
• Polish
• Portuguese (Brazilian)
• Russian
• Spanish
To ensure correct display and processing of Teamcenter data, set the required values
in your operating system environment. Use the appropriate values for your locale
and platform.

Environment settings on Windows systems

Locale Setting Value
Database character set1 ZHS16CGB231280
Chinese (Simplified)
Server character set MS936
TC_language_default2 zh_CN
Database character set1 ZHT16BIG5
Chinese (Traditional)
TC_language_default2 zh_TW
Czech Database character set1 EE8MSWIN1250
Server character set CP1250
TC_language_default2 cs_CZ
English Database character set1 WE8MSWIN1252
TC_language_default2 en_US
French Database character set1 WE8MSWIN1252
TC_language_default2 fr_FR
German Database character set1 WE8MSWIN1252
TC_language_default2 de_DE
Hebrew Database character set1 IW8MSWIN1255
TC_language_default2 en_US
Italian Database character set1 WE8MSWIN1252
TC_language_default2 it_IT
Japanese Database character set1 JA16SJIS
TC_language_default2 ja_JP
Korean Database character set1 KO16KSC5601
TC_language_default2 ko_KR
Polish Database character set1 EE8MSWIN1250
TC_language_default2 pl_PL
Portuguese (Brazilian) Database character set1 WE8MSWIN1252
Notes:
1. Applies only to Oracle databases.

2. Set in the TC_language_default site preference.

Environment settings on Windows systems

Locale Setting Value
TC_language_default2 pt_BR
Russian Database character set1 CL8MSWIN1251

TC_language_default2 ru_RU
Spanish Database character set1 WE8MSWIN1252
TC_language_default2 es_ES
Notes:
1. Applies only to Oracle databases.

2. Set in the TC_language_default site preference.
Note
In Hebrew and Japanese locales, set the following additional variables:
1. In the TC_DATA\tc_profilevars file, set TC_XML_ENCODING to
ISO-8859-8.
2. In the TC_ROOT\iiopservers\Start_TcServer1 file

and the TC_ROOT\pool_manager\mgrstartMYDB, set
TC_CHARACTER_ENCODING_SET to ISO8859_8.
Deploying localizations
Build and deploy localizations to the Teamcenter thin client and rich client using
the Web Application Manager.
Note
For more information about applying localizations to Teamcenter, see the
Localization Guide.
Deploying thin client localizations

Use the Web Application Manager to build a localized Teamcenter thin client.
Update thin client localized text
The thin client text server files reside under the Teamcenter application root
directory in the \lang\textserver\locale-code directory. If you change one of
the text server XML files (*_locale.xml and *_errors.xml), regenerate the
webstrings.xml file:

1. Change to the
WEB_ROOT\staging-location\webapp_root\teamcenter\dhtml\common\intl
directory in the Teamcenter application root directory.
2. Copy the webstrings.xml file to the language directory.
3. Regenerate the Web tier application (file-name.ear) and deploy in an application

server.
4. Change the header encoding of the webstrings.xml file to the appropriate

language-specific character encoding value, for example, Shift-JIS for Japanese.
Note
After you complete these steps, clear your Web browser cache before you
launch the thin client.
Create a thin client localization

If you localize the thin client into a language not provided by Siemens PLM Software:
1. In the Teamcenter application root directory, create a directory for the new
language under the \lang\textserver\ folder.
For example, if you localize the user interface for Hebrew, create the iw_IL
directory.
2. Copy all files from the en_US directory to the new language directory.
3. In the new language directory, translate all XML files to the new language.
Note
Make sure the encoding specification at the top of each XML file matches
your system encoding when you save the file. Also, make sure the encoding
specified supports the desired locale.
For Hebrew on Windows systems, the encoding specification should
resemble the following example:
<?xml version="1.0" encoding="windows-1255" standalone="yes"?>
4. Edit the weblocal_locale.xml file in the new language directory to change the
value of the web_local_lang parameter from en to the new language name.
For example, if you localize the user interface for Hebrew, change the
web_local_lang parameter to he:
web_local_lang: exported "he";
5. In the \lang\textserver\no_translation directory, locate the

textserver_text.xml file and open it in a plain text editor.
6. Locate the following key for the new language:

<key id="textsrv_associatedDefaultJavaLocale_locale-code</key>
Replace lang-code with the W3C standard language code and locale-code with
the Java standard locale code.

For example, in Hebrew locales, this key would resemble the following:
<key id="textsrv_associatedDefaultJavaLocale_he">iw_IL</key>3
Replace the existing key with the following:

<key id="textsrv_encodingLocales_ISO8859_8">en_US;iw_IL</key>
<key id="textsrv_encodingLocales_NT_862">en_US;iw_IL</key>
<key id="textsrv_encodingLocales_NT_1255">en_US;iw_IL</key>
<key id="textsrv_encodingLocales_UTF8">cs_CZ;de_DE;en_US;es_ES;fr_FR;
it_IT;iw_IL;ja_JP;ko_KR;ru_RU;zh_CN;zh_TW</key>
7. Change to the WEB_ROOT\staging-location\webapp_root\ directory and

create a new language directory.
For example, if you localize the user interface for Hebrew, create the he directory.
8. Copy all files from the en directory to the new language directory.
9. In the new language directory, translate all XML files to the new language.
10. Regenerate the Web tier application (file-name.ear) as described in Installing

thin client Web applications.
Deploy the application in an application server as described in the Web
Application Deployment Guide.
Convert the thin client user interface for Hebrew

Converting the thin client user interface for the Hebrew language requires
customized development of thin client pages and Java code and definitions of
Unicode standards in the Teamcenter application.
1. Log on to the operating system as administrator.
2. Click Start and choose Settings→Control Panel.
3. In the Control Panel, choose Regional Options.
4. On the General tab, choose a locale and language setting for the system.
5. Click the Set default button and choose Hebrew as the default language.
6. Click the Input Locales tab and choose Hebrew as the input language.
7. Save all definitions.

Windows requests the Windows installation CD-ROM for the definition of all
settings.
8. Restart the system.
When installing the rich client, you must choose the Latin-Hebrew ISO8859_8
character set.
3. he is the standard W3C code for Hebrew.

You must also check that the charsets.jar and font.properties.iw files are present
in the JRE_HOME/lib directory.
Deploying rich client localizations

Deploy a localized Teamcenter rich client.
Display Siemens PLM Software-provided rich client localizations

To display a Siemens PLM Software-provided localized rich client user interface, set
the locale of the client workstation to one of the Siemens PLM Software-provided
locales. No other steps are required.
In addition to English, Siemens PLM Software provides Teamcenter rich client and
thin client user interfaces localized for the following languages:
• Chinese (Simplified)
• Chinese (Traditional)
• Czech
• French
• German
• Hebrew
• Italian
• Japanese
• Korean
• Polish
• Portuguese (Brazilian)
• Russian
• Spanish
Update rich client localized text

If you change the strings of a localized rich client user interface, you must convert
the files to Unicode and regenerate the Java archive (JAR) file.
To identify the localized user interface files you need, look for the language
and country identifier added to the base resource file. For example, for the
aif_locale.properties English resource file, which must remain in English, the
equivalent Japanese file is named aif_locale_ja_JP.properties.
Convert native .properties files to Unicode as follows:
1. Copy the base file to a temporary file name, for example, from
aif_locale.properties to aif_locale_temp.properties.
2. Edit the base_locale_temp.properties file, modifying the values to the correct

native language.
3. Save the file.
4. Run the native2ascii utility against the temporary properties file to convert it
to a Unicode properties file.
The native2ascii utility is in the \bin directory of Java SDK 1.4.
For more information, access the following URL:
http://download.oracle.com/javase/6/docs/technotes/tools/windows/native2ascii.html

For example, to convert the properties file from Japanese to Unicode, enter the
following command from the command line:
native2ascii -encoding SJIS aif_locale_temp.properties aif_locale_ja_JP.properties
The final locale-specific properties file or the output of the native2ascii file must
have the base_locale_locale-id_language-id.properties file format.
The rich client finds the value of a key in the following order:
BASE_user.properties
BASE_locale-ID_language-ID.properties
BASE_locale.properties
BASE.properties
5. Recompile the JAR file.
6. Install fonts if necessary.

For information about fonts, access the following URL:
http://java.sun.com/j2se/1.4/docs/guide/intl/font.html
For more information about converting files to unicode, see the Unicode Consortium
Web site:
http://www.unicode.org/

Chapter
21 Silent installation
Silent installation using SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Overview of SMS software distribution . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Using the SMS installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Using the Repackage Installation wizard . . . . . . . . . . . . . . . . . . . . . . 21-2
Using the Script Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Preparing to create an SMS package . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-4
Create an SMS installer-generated executable file . . . . . . . . . . . . . . . 21-4
Run the Repackage Installation wizard . . . . . . . . . . . . . . . . . . . . . . . 21-5
Customize scripts with the Script Editor . . . . . . . . . . . . . . . . . . . . . . 21-6
Create and advertise an SMS installation program . . . . . . . . . . . . . . . . . 21-6
Create an SMS package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
Create an SMS program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
Advertise the SMS program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
Silent installation using Teamcenter Environment Manager . . . . . . . . . . . . . 21-9

Silent installation using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . 21-9
Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10
Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . 21-10

Chapter
21 Silent installation
Silent installation
As an alternative to installing and configuring Teamcenter on individual hosts in
your network, you can install Teamcenter servers or two-tier rich clients silently,
using a preconfigured installation program. Silent installation suppresses most
installation prompts and requires minimal user interaction.
Siemens PLM Software provides two methods for silently installing Teamcenter,
using either Teamcenter Environment Manager or Microsoft Systems Management
Server (SMS). Choose the method that best suits your network.
Silent installation using SMS

Overview of SMS software distribution
The SMS software distribution process consists of the following tasks:
• Creating and distributing a package
• Creating and configuring a program
• Creating a program advertisement
A package contains the files and instructions SMS uses to distribute software to
client hosts from a distribution point.
A program is a set of instructions that control how the software is executed on a client
host. A program’s properties contain a command line that invokes an executable
file with the necessary arguments. For Teamcenter installation, a program might
invoke Teamcenter Environment Manager and specify a silent response file to supply
desired selections and values for the installation, resulting in a preconfigured and
noninteractive installation. An SMS package must contain at least one program.
Once a distributed package and program have been created, you must create an
advertisement to make the package available to selected clients. Advertisements
can be posted to either a single collection or to a collection and its sub-collections.
SMS provides several preconfigured collections to simplify distribution.
However, if software distribution points are selected based on discovery data or
software/hardware inventory, you must create a new collection with each new
package. You can create advertisements using the Advertisements node in the SMS
Administrator console.
You can create a distributable package either by using the SMS Installer or by
creating a silent installation with a script that contains the necessary commands

Chapter 21 Silent installation
to launch the Teamcenter installation in silent mode to distribute software to the

client host.
To do this, you install Teamcenter using Teamcenter Environment Manager,
capturing a silent response file in the process. The silent response file records the
selections and values entered during installation. After you capture and test the
silent response file, you can create a batch program (.bat) or a Visual Basic script
that contains the commands to launch TEM in silent installation mode. This script
is stored on the host from which you distribute the software.
Using the SMS installer

You can use SMS installer to create installation scripts and SMS installer-generated
executable files. SMS installer uses installation scripts to control the installation
process. These installation scripts contain script commands that each perform a
single action. These actions can be based on sophisticated conditions that are robust
and flexible. Scripted installations make installing software easy and less prone to
error. Installation scripts can move files to the correct directories, prompt the user
for information, give the user messages, and set registry keys, and so on. You can
also specify which of the following actions to perform:
• Gather information from users.
• Gather information about the current system.
• Search for files.
• Install and delete files.
• Update .ini files and the system registry.
The SMS installer has two user interfaces:

• Installation Expert
Used to automatically create a basic installation script on a reference computer.
• Script Editor
Used to view and edit an installation script generated by the Installation Expert.
You can also add user prompts and other attributes to your script. You can also
use the script editor to create new installation packages.
Using the Repackage Installation wizard

SMS installer can also be used to repackage an installation using the Repackage
Installation wizard. The Repackage Installation wizard replaces an application’s
existing setup program with a new one that you create. The wizard produces
the basic script. Using Script Editor, you can add error checking, user prompts,
branching, additional files, registry key changes, etc. The Repackage button in the
Installation Expert dialog box initializes the Repackage Installation wizard which
performs the following tasks:
• Scans the reference computer to take a snapshot of the system before installation
of the application.

Silent installation
• After the initial snapshot is complete, executes the application’s installation

program.
• After the installation is complete, scans the system to detect changes.
• Creates the installation script to duplicate the changes on another host.
When you run the Repackage Installation wizard, you specify the path to the
application’s setup program and any desired command-line arguments. You can
also specify directories, files, registry keys, and other items to monitor during
installation. During the repackaging process, SMS Installer creates lists of files,
directories, registry keys and other system settings changed during installation. If
necessary, you can modify these settings during repackaging.
Using the Script Editor

After you create an installation script with Installation Expert, you can edit the
script using Script Editor. Script Editor is a flexible and powerful tool that can be
used to create variables and branching within the installation script. In addition,
you can use Installation Expert to add the following customized functions:
• Interactive prompting for user for information.
• Adding additional files and directories to a script.
• Include other scripts to be launched during the installation process.
• Provide uninstall and rollback support in the event of a problem.
• Modify SMS Installer messages.
• Modify the registry.
• Register third-party applications and controls.
• Add your application to the Add or Remove Programs list in the Control Panel.
• Execute programs at startup.
• Provide conditional flow control of script execution.
Many customized functions can be inserted through Script Editor actions, or added
to the script by configuring installer attributes in Installation Expert. For example,
either method can be used to provide uninstall and rollback support and to add your
program to Add or Remove Programs list in the Control Panel. If you modify a
graphical user interface, Installation Expert adds the script items to your installation
script. Script Editor also supports manually adding or modifying them as well.
If you plan to use Installation Expert at any point during the script building process,
Siemens PLM Software recommends you use Installation Expert to create the basic
installation script. By using this approach, you can switch between Installation
Expert and Script Editor without losing customization due to the conversion. If you
create the script with Script Editor and switch to Installation Expert, you may
lose some script items.

Preparing to create an SMS package

Set up SMS to create a silent installation package.
Create an SMS installer-generated executable file

1. Set up a reference computer on which you want to run the wizards to create
the script.
If you are using the Repackage Installation wizard to replace an existing setup
program, the reference computer must be configured with exactly the minimum
configuration that you require for your target computers.
Note
If you use the Watch Application wizard to create a new setup program,
there are no special configuration requirements for your reference
computer.
2. Use one of the wizards to create an installation script or create the script entirely
within Script Editor. Compile the installation script and files to create the
compressed executable file, and then test the script by installing the files on a
test computer. If you want to keep the existing setup program but want to add a
script to execute it, use Script Editor to create a wrapper script.
3. Determine whether you need to use the Watch Application wizard or the
Repackage Application wizard.
• If the application already has a setup file, use the Repackage Application
wizard.
• If the application does not have a setup file, use the Watch Application
wizard.
4. On the primary site server, unpack the SMS installer files. The files are
packaged in such a way that they do not run unless SMS is installed.
5. To set up SMS installer, copy the SMS installer installation file (SMSInstl.exe)
to the reference computer and double-click the SMSInstl program.
6. To select the installation options you want, start SMS installer and edit the
SMS installer attributes. Make sure each option is set the way you want. For
information about each option, see the SMS Installer Help.
7. To automatically generate an installation script for the application, run the

Repackage Application wizard or the Watch Application wizard.
8. Use Script Editor to modify the installation script. Most scripts require some
modifications. For example, you can modify the script to prompt the user for
information, send messages to the user, search for files, install and delete files,
and update .ini files and the registry. Test the script and make adjustments to
optimize performance.
9. Using the SMS installer compiler, compile the SMS installer-generated

executable file.

Silent installation
10. Test the compiled SMS-generated executable file. SMS Installer has two test
modes:
• Test mode
Runs the installation program without installing any files.
• Run mode
Runs the installation program and installs the files.
11. Distribute the file using one of the following methods:

• Distribute it using SMS software distribution.
• Copy it onto storage media for distribution.
• Post it on your corporate intranet for distribution.
Run the Repackage Installation wizard
1. Launch SMS Installer (Start→Programs→Microsoft SMS Installer→Microsoft

SMS Installer 32).
2. Choose View→Installation Expert.
3. Click Repackage.
4. In the Repackage Installation dialog box, enter the complete path to the
installation program in the Installation Program box or click Browse to select
the program. Do not include command-line arguments in this box.
5. In the Command-Line Options box, type the necessary command line arguments.
6. In the Directory box (under Sub-Tree), indicate whether to scan subdirectories

of the directories you select. To modify how SMS Installer scans the reference
computer, click Change. Use the Files/Directories and Registry Keys tabs to
modify the settings in the Repackage Advanced Settings dialog box.
7. Click Next to start the repackaging process.

The wizard performs the initial scan of the reference computer and starts
the specified setup program. Follow the setup prompts to complete a normal
installation of the application.
8. After installation is complete, make whatever changes you want to the

installation script, application, or reference computer.
9. After making changes, click Next to complete the repackaging process.
10. Click Finish to return to the Installation Expert.
11. Save and name your installation script (File→Save As).

Customize scripts with the Script Editor

To edit a line of a script, double-click the line you want to edit. If the given item is
editable, Script Editor displays a Properties dialog box.
To add a line to a script, select the line following the position where you want to add
the item. In the Actions list, double-click the item you want to add, or drag the
item to intended position in the script.
Create and advertise an SMS installation program

1. Create an SMS package of the software you want to distribute.
2. Create an SMS program to contain the instructions SMS uses to distribute the
package.
3. Advertise the program to your SMS collection.

Note
SMS uses a three-character code to identify a software distribution site in the
SMS hierarchy. This procedure uses TCE as the site code.
Create an SMS package

1. In SMS, expand the SMS directory tree to Systems Management Server→Site
Database (TCE)→Packages. In the left pane, right-click Packages and choose
New→Package.
2. In the Package Properties dialog box, click the General tab. Specify the
following values for the package:
Property Description
Name Specifies the name of the package, for example,
Teamcenter 9.1. This box must contain a value.
Version Specifies the version of the package, for example,
1.0 This box must contain a value.
Publisher Specifies the publisher of the package, for example,
Siemens.
Language Specifies the package language, for example, the
language setting for your locale. This box must
contain a value.
Comment Contains a brief comment (up to 127 characters) to
describe the package. This box is optional.
3. Click the Data Source tab and select This package contains source files.
Use this tab to specify the package source folder (if any) and to update the
package source as needed. Package source files are copied to distribution points
to support a package, when one or more of its programs are advertised to
clients. The Source version box indicates the number of times an administrator
has updated the package source files and requested an update to distribution
points, followed by the date and time of the last update. The source version is

Silent installation
incremented each time the path in source directory is changed, or whenever you
choose the Update distribution points command in the Manage Distribution
Points Wizard. The Source version box is empty unless you select This package
contains source files.
4. Specify the network path for the package source files:

a. Click Set to open the Set Source Directory dialog box.
b. Click Local drive on site server.
c. Browse to the correct location, and then click OK.
Create an SMS program

Database (TCE)→Packages→package-name→Programs.
In the left pane, right-click Programs and choose New→Program.
2. In the Program Properties dialog box, click the General tab. Specify the
following values for the program:
Name Specifies the name to use when defining the
advertisement of the package, for example,
Teamcenter 9.1. This box must contain a value.
On the client computer, this name is displayed
in the Run Advertised Programs and the Add or
Remove Programs dialog boxes in the Control
Panel.
Comment Contains a brief comment (up to 127 characters)
to describe the program. On some client hosts,
this comment is displayed in Run Advertised
Programs dialog box in the Control Panel. On
other client hosts, this comment is displayed in
Advertised Programs Monitor or the Advertised
Programs Wizard in the Control Panel. This box
is optional.

Command line Specifies the command line for the program,
including the file name extension. This box must
contain a value.
For example, to specify a silent installation of
Teamcenter 9.1, the command line may be one of
the following:
distribution-location\tem.bat –s
distribution-location\tem.bat
–s silent-install-file-name
Note
When using the silent installation option
(–s), the silent install file must be in the
same directory as the tem.bat file.
3. In the Program Properties dialog box, click the Environment tab. Specify the
following conditions for the program:
Program can run Specifies the logon condition for running the
program. Select Whether or not a user is logged.
This enables the program to run with or without
user interaction.
Run mode Specifies the required credentials for running the
program. Choose Run with administrative rights
and select the Use Software Installation Account
check box.
This specifies that the program requires
administrative credentials on the computer to
run (This option is available only on Windows XP
Professional and Windows Server 2008 clients).
Selecting Use Software Installation Account runs
the program under an administrator-specified
account (the SMS Software Installation Account)
on Windows XP Professional and Windows Server
2008 clients. The Software Installation Account is
specified in the Software Distribution Properties
dialog box in the SMS Administrator console
(under Component Configuration).
After you create the SMS package, you can advertise the program.
Advertise the SMS program

Database (TCE)→Packages→package-name→Programs.

Silent installation
In the right pane, right-click the package-name and choose All Tasks→Distribute
Software.
2. In the Welcome dialog box, click Next.
3. In the Distribution Points dialog box, select the distribution points from which
you want to advertise, and then click Next.
4. In the Advertisement Target dialog box, chose Advertise this program to an

existing collection. Enter or browse to the collection name, and then click Next.
5. In the Advertisement Name dialog box, type a name for the advertisement, add
any additional comments you want to add about the advertisement, and click
Next.
6. In the Advertise to Subcollections dialog box, click Next.
7. In the Advertisement Schedule dialog box, enter the date and time the
advertisement should start. Choose whether to specify an expiration date for the
advertisement, and select the expiration date if necessary.
Click Next.
8. In the Assign Program dialog box, choose Yes. Assign the program, and then
click Next.
9. In the Completing the Distribute Program Wizard dialog box, click Finish.
SMS updates the Advertised Programs Monitor so the program is advertised to
its intended audience.
Silent installation using Teamcenter Environment Manager
Silent installation using TEM

Capture, manage, and launch a silent Teamcenter installation using Teamcenter
Environment Manager (TEM).
Create a silent installation configuration file

1. Log on to the Teamcenter corporate server host and browse to the root directory
of the Teamcenter software distribution image.
2. Start Teamcenter Environment Manager (tem.bat) from the Teamcenter

software distribution image.
3. In the Welcome to Teamcenter panel, select the Create silent distribution check
box, and then click Install.
4. In the Silent Installation panel, in the Silent Configuration File box, specify the
path to the silent installation file, for example, C:\silent.xml. The specified path
must be to an existing directory and the file name must end in .xml.

5. Proceed through the remaining panels to complete the Teamcenter installation.

Teamcenter Environment Manager creates the silent installation file you
specified in step 4. This file records your settings and selections during the
installation. You can use this file to silently install Teamcenter on another host
with the same settings.
Launch a silent installation

To launch a silent installation on another host, type the following command:
tem.bat –s file-name.xml
Replace file-name with the name of the silent installation configuration file.
After installation is complete, you can view a log of the installation in the
installxxx.log file under the install directory in the Teamcenter application
installation directory.
Modify the silent installation configuration file

The silent installation configuration file is XML-based, as shown in Sample silent
installation configuration file. After creating the file and establishing the file
structure using Teamcenter Environment Manager, you can change the installation
by manually modifying the values of the XML elements described in the following
table.
Caution
Siemens PLM Software recommends using an XML editor to ensure
well-formed XML code. Do not change the XML structure of the file. If XML
file structure is incorrect, or the XML code is not well-formed, installation fails.
Element Description
features Lists all the Teamcenter modules and features to be
installed. These are selected on the Features panel of
Teamcenter Environment Manager.
feature Specifies one feature of a Teamcenter module. The
code attribute identifies the feature. To define whether
Teamcenter Environment Manager installs the feature, set
the selected attribute to either true or false.
data Lists all Teamcenter Environment Manager Java classes
and values defining aspects of installation, such as the path
to the installation directory for Teamcenter application
files. For additional information, see the comments in the
configuration file. The comments describe the class and
valid values.

Silent installation
<?xml version="1.0" encoding="UTF-8" ?>

- <root>
<tem engine="2008.0.0" />
- <settings>
<installDir value="C:\\Program Files\\Siemens\\Teamcenter9" />
<sourceDir value="C:\\tc\\tc900_win" />
<application value="tceng" />
<silentMaintenance value="false" />
<installingUser value="tc_user" />
<installLanguage value="ENGLISH" />
<version value="9000.0.0.20110504" />
</settings>
- <config name="My Configuration 1" id="config1">
- <mode type="install">
- <checkpoints>
- <checkpoint value="featureProperties">
<point value="coreTemplate:foundation_template.xml" />
<point value="minDB2Version:9.5" />
<point value="feature_id:datamodel,rtserver" />
<point value="template_file:foundation_template.xml" />
<point value="minOracleVersion:10.2.0.1" />
<point value="minMSSQL2005Version:9.0" />
<point value="template_name:foundation" />
<point value="typeAnalysis:true" />
</checkpoint>
</checkpoints>
</mode>
<comments />
- <data>
- <adminUser guid="2E53CF5E50FC3AC707D1D0566F0F213B">
<password value="ENCRYPTED:1c8c4cdcccded2c2" />
<user value="infodba" />
</adminUser>
- <director guid="661AA614566CA975D92A7EBE985F3EA3">
<status value="0" />
- <script>
<temBase />
<copyFeature guid="A0CF70EB869C3A0BC6171BD22667EA52" />
<copyFeature guid="90C2AAF88A1CA61FAB397B96F6E4AAC1" />
<copyFeature guid="8C061D687B13E0CB9DC4A3348BE" />
<copyFeature guid="B176F6B6E92010FE91D9804EFB0DD613" />
<unpack feature="A0CF69C22667E3A0BC61770EB81BDA52" />
<unpack feature="90C2A1C1FAB397AF88ABE96F6A64AAC1" />
<unpack feature="8C061D87B1A3D51E13E0CB9DC46348BE" />
<unpack feature="B176FB0D2016B6E9E91D9804EF0FD613" />
<preInstall feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<preInstall feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<preInstall feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<preInstall feature="B176F6B6E9E91D9804EFB0D2010FD613" />
<install feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<install feature="90C2A1AB397AC96F6A61FF88ABE4AAC1" />
<install feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<install feature="B176F6B6E9E91D9804EFB0D2010FD613" />
<postInstall feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<postInstall feature="90C2A1C96B397AF88ABF6A61FAE4AAC1" />
<postInstall feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<postInstall feature="B176F6B6E9E91D9804EFB0D2010FD613" />
<featureInstalled feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<featureInstalled feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<featureInstalled feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<featureInstalled feature="B176F6B6E9E91D9804EFB0D2010FD613" />
</script>
</director>
- <FSCService guid="F2FCBC1E3A11EEC03DFF7F9DC9B64BD2">
<fscReadCacheDir value="$HOME\\FSCCache" />
<fscWriteCacheDir value="$HOME\\FSCCache" />
<addToBootstrap value="true" />
<fscReadCacheSize value="10" />
<serverID value="FSC_myfsc" />
<log value="" />
<fscWriteCacheSize value="10" />
</FSCService>
- <FSCMasterSettings guid="EBC3422F7E0E3A827C6BF18F1EFE1134">
<masterModel value="Simple Model" />
</FSCMasterSettings>
- <FscSiteImport guid="630BEC48A9748F927EC742A76D5868DA">
<remoteSites value="" />
</FscSiteImport>
Sample silent installation configuration file (Continued)

- <tcdata guid="4500621E2BE24BF0DD6ABF31EBA01088">
<path value="C:\\Program Files\\Siemens\\tcdata1" />
<create value="true" />
</tcdata>
- <FSCServiceFCCDefaults guid="7311DC5E94724BED0DD7419FCDE055CF">
<writeCacheSize value="1000" />
<readCacheSize value="1000" />
<cacheDirUnix value="/tmp/$USER/FCCCache" />
<partialReadCacheSize value="3000" />
<cacheDirWin value="$HOME\\FCCCache" />
</FSCServiceFCCDefaults>
- <FccSite guid="35EE6A6B3D91876B85467D5EDE51EACE">
<siteListString value="" />
</FccSite>
- <FSCServiceConnections guid="E4BDA0B52E123C9F1CB10A49F0C326F1">
<connections value="http,4545,;" />
</FSCServiceConnections>
- <OSUser guid="CA769D31FD7E1A0BBBD722E5E509E809">
<password value="ENCRYPTED:3448ee60e4c8a0c248" />
<user value="LM6S003\\yytcadm" />
</OSUser>
- <flexClient guid="7221ECFBC9555CDF997FC3F575022761">
<nX5String value="28000@svnxflex1;28000@svnxflex2" />
<port value="27000" />
<nX4String value="27000@trlic001;27000@trlic002" />
<nX5Port value="28000" />
<host value="trlic001" />
<nX5CheckBox value="true" />
<nX5Host value="svnxflex1" />
<envServerString value="28000@svnxflex1;28000@svnxflex2" />
</flexClient>
- <foundationSettings guid="LHBY67HDNDHFJTZYMYHSKED26FZD84I7">
<genClientCache value="delete" />
<genServCache value="" />
<enableGenServCache value="true" />
</foundationSettings>
- <transientVolume guid="983980098FF188A8C4BF08E8168A32A8">
<windowsVolume value="C:\\Temp\\transientVolume_tc_user" />
<unixVolume value="/tmp/transientVolume_tc_user" />
</transientVolume>
- <TcOracleSystem guid="1EF0859AC04962CBFA41C4C8C84499A1">
<password value="ENCRYPTED:3448ee60e4c8a0c248" />
<user value="system" />
<tablespaces value="tc_user_IDATA:90;tc_user_ILOG:5;tc_user_INDX:5;tc_user_TEMP:5" />
<tablespacePath value="c:\\tc_mydata" />
</TcOracleSystem>
- <volume guid="1F16971107DE44C0C7827F800EE4AEF8">
<fscModel value="Simple Model" />
<location value="C:\\Program Files\\Siemens\\volume1" />
<name value="volume" />
<hostName value="lm6s003" />
<fscId value="FSC_myfsc" />
</volume>
- <TcOracleEngine guid="F4F7C0852B27D6E56B8C64BE77FFA14C">
<createUser value="true" />
<host value="lm6s003" />
<flush value="false" />
<populate value="true" />
<service value="tc" />
<password value="ENCRYPTED:34eae6cae4e8c6be" />
<user value="tc_user" />
<create value="true" />
</TcOracleEngine>
</data>
- <features>
<add feature="A0CF69C3A0BC61770EB81BD22667EA52" name="VC 2005/2008 Redistributables" />
<add feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" name="FMS Server Cache" />
<add feature="8C061DD51E13E0CB9DC4687B1A3348BE" name="Teamcenter Foundation" />
<add feature="B176F6B6E9E91D9804EFB0D2010FD613" name="NX Integration" />
</features>
</config>
<updateManager />
<webAppManager />
</root>
Sample silent installation configuration file

Chapter
22 Installing Teamcenter patches
Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1
Patching Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Install patches on the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4

Patch the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Patch the rich client silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Patch the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . 22-4
Patch Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6
Patch the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-7
Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8

Chapter
22 Installing Teamcenter patches
Installing Teamcenter patches

On Teamcenter servers and two-tier rich clients, you install patches using the
Updates Manager, a feature of Teamcenter Environment Manager (TEM). Patches
to the Teamcenter J2EE Web tier you install using the Web Application Manager.
Teamcenter updates (maintenance packs and patches) are posted for download on
GTAC when available.
Distribution of Teamcenter updates

Teamcenter 9.1 updates are delivered in patches and in maintenance packs (MP).
Patches to Teamcenter servers and two-tier rich clients are applied using the
Updates Manager in Teamcenter Environment Manager (TEM). Patches to the
J2EE Web tier and over-the-Web (OTW) distribution servers are applied using the
Web Application Manager.
Teamcenter patches are named using the following convention:
• product-level_number_platform.zip
Contains the server, TEM rich client, and Web tier patches
• product-level_number_OTW.zip
Contains the OTW rich client patches and distribution server patches
• product-level_number_PV_all.zip
Contains the Teamcenter Visualization patches
• product-level_number_install.zip
Contains the TEM updates
Downloading Teamcenter patches

1. Locate the patches you want to apply in the Product Updates area on GTAC.
2. Download the patch files to a temporary location on your host.

Note
Make sure you download the appropriate patch file for your platform.

Chapter 22 Installing Teamcenter patches
Before you apply downloaded Teamcenter 9.1 patches to your server, you must do
the following:
• Install the base Teamcenter 9.1 release.
• Stop all Teamcenter 9.1 related processes and services (such as FSC, database
daemons, and so on).
Note
TEM does not allow you to install patches for a version of Teamcenter that
is earlier than your current installation. For example, you cannot apply a
Teamcenter 2007.1 patch to a Teamcenter 9.1 installation.
Patching Teamcenter Environment Manager

1. If the patch you downloaded contains an updated installer file (install.zip),
extract this file into your installed Teamcenter environment to update
Teamcenter Environment Manager (TEM) to the latest version:
a. Copy the patch-id_install.zip file to your TC_ROOT\install directory.
b. Open a command prompt.
c. Change to the TC_ROOT\install directory.
d. Enter the following command to extract the install.zip file, overwriting

existing files:
unzip –o install.zip
Note
If errors occur while extracting the file, do one of the following tasks:
• Add the path to your TC_ROOT\install\install directory to your
PATH environment variable and enter the unzip command again.
• Enter the unzip command with the full path to your

TC_ROOT\install directory, for example:
TC_ROOT\install\install\unzip –o install.zip
Install patches on the corporate server

1. Extract the product-level_number_platform.zip file to a temporary location.
2. If you use the .NET Web tier, shut down Microsoft Internet Information Services
(IIS) before you begin installing patches.
3. Launch TEM (Start→Programs→Teamcenter 9.1→Environment Manager).

Note
If you patched TEM in Patching Teamcenter Environment Manager, make
sure you launch the patched TEM.
4. In the Maintenance panel, choose Updates Manager and click Next.
5. In the Apply Updates panel, enter the following values.

a. Update kit location
Enter the location of patch files you extracted in step 1.
b. Backup directory
Enter the location in which you want to store backups of files replaced
during the update process.
Click Next.
Note
TEM stops all Teamcenter services during the update process. All users
logged on to the environment are notified that it will not be available until
the update process is complete. Make sure all Teamcenter clients and
processes on the host are stopped before you continue.
If you use the .NET Web tier, make sure IIS is stopped before you continue.
If these services or processes are running, the update may fail because
TEM cannot copy replacement files from the patch to the installed location.
6. In the Confirmation panel, click Start to begin patching the server.
7. Once the server is successfully patched, you must manually update your
TC_DATA directories.
a. Create a backup of your current TC_DATA directories.
b. Extract the platform\tc\data.zip file from the patch-id.zip file and copy the
contents to your TC_DATA directories.
c. Copy the tc_profilevars.bat file from the backup to the TC_DATA. directory.
8. Follow the instructions in the patch’s README file for any additional steps
required to complete the patch.
Restart all Teamcenter-related processes and services (such FSC, database daemons,
and so on).
Note
Each time you add a new feature to your installation, reapply installed
patches because the added feature’s files may have been patched previously.
Adding a feature can overwrite that feature’s patched files with the older files
from the original software distribution image.

Patching the rich client

There are multiple methods for patching the rich client. Choose a patching method
according to how you installed the client. If you installed the rich client during your
server installation with the TEM, follow the steps in Patch the rich client using
TEM. If you installed the rich client using the Over-the-Web Installer distribution
server with one or more distribution server instances, patch each distribution server
instance by following the steps in Patch the rich client using the Over-the-Web
Installer. To patch Lifecycle Visualization using the Over-the-Web Installer, follow
the steps in Patch Lifecycle Visualization.
Patch the rich client using TEM

Patch the rich client using the steps in Install patches on the corporate server. If the
rich client was installed as a part of the same environment as the corporate server,
the rich client is updated at the same time as the corporate server.
Patch the rich client silently

Teamcenter Environment Manager allows you to install patches silently, with no
prompts or user interface:
1. Patch Teamcenter Environment Manager as described in Patching Teamcenter
Environment Manager.
2. Open a command prompt.
3. Change to the TC_ROOT\install directory.
4. Type the following command:

tem.bat –p "patch-path\patch-ID_platform.zip"
Replace patch-path with the path to the downloaded patch or maintenance pack.
Replace patch-ID with the ID of the patch or maintenance pack and platform
with the platform identifier.
This procedure launches TEM and applies the patch with no user interaction
required.
Note
You must enclose the path to the patch in quotation marks (") for paths that
contain spaces in them. For example:
tem.bat —p "..\Teamcenter patches\Teamcenter9_mpnumber_platform.zip"
Patch the rich client using the Over-the-Web Installer

The patch files for any rich client installed using the OTW installer are in the
Teamcenter9_patch-ID_OTW.zip file. Instead of patching the rich client at all
installed locations, you can patch any or all distribution server instance installations
that were installed using the Web Application Manager. To ensure all rich clients
installed from the patched distribution server instance download the patched files
automatically the next time they are launched:

1. Download and unzip the Teamcenter9_patch-ID_OTW.zip file to your computer.
2. Shut down the distribution server.
4. Click the Copy ICD button. Browse to the expanded patch location to select the
icd directory, and then click OK to copy the ICD files to the Web Application
Manager.
5. Select the installed rich client instance you want to patch and click Modify.
7. Click Add and add the patch location to list of disk locations for install images.
8. Select and install patches. If you add patches to a previously patched instance,
the steps differ from the first patch installation.
Initial patch Additional patches

a. Click Add Solutions. a. Click Reinstall Solutions.
b. Select Rich Client Patch and click b. In the Reinstall Solution dialog
OK. box, click OK.1
c. In the Modify Web Application c. In the Confirm dialog box, click

dialog box, click OK to begin Yes.
patching.
d. In the Modify Required Context
d. After the patch is installed, click Parameters dialog box, click OK to
OK to close the Progress dialog begin patching.
box.
e. After the patch is installed, click
OK to close the Progress dialog
box.
9. In the Modify Web Application dialog box, click OK.
11. Copy the otwweb directory from your

WEB_ROOT\staging-location\webapp_root directory to your Web server.
12. Restart the distribution server.
After the installation is complete, the instance and the modified instance contains
the patch. Any rich clients previously installed from this instance has the patch
1. Adding patches reinstalls the patch solution with the newer files.

applied the next time the rich client is launched. Future rich client installations are
installed with the patch.
Note
Customer-specific patches are not cumulative like general Teamcenter patches
and business urgent patches are. To install customer-specific patches to the
rich client using the Over-the-Web Installer, perform the following steps:
1. Install a single customer-specific patch.
2. Deploy the rich client distribution instance.
3. Start the rich client on each host so the Over-the-Web Installer downloads
and installs the patch updates.
4. Repeat for each additional customer-specific patch.
Patch Lifecycle Visualization

Download the Lifecycle Visualization patch file (patch-id_PV_all.zip) and extract
the ZIP file into a single directory. If prompted, overwrite all files.
If you use Lifecycle Visualization as part of a two-tier rich client configuration, run
the TcVis_patch-id_win32.exe file to patch Lifecycle Visualization. Otherwise,
patch the rich client instance that includes Lifecycle Visualization by performing
the following steps:
1. Shut down the distribution server.
3. Click the Copy ICD button. Browse to the expanded patch location to select the
icd directory, and then click OK to copy the ICD files to the Web Application
Manager.
4. Select the rich client instance that contains the Teamcenter Visualization 8
(Embedded) for Rich Client 4-Tier (Installation and Configuration) solution
and click Modify.
6. Click Add and add the patch location to list of disk locations for install images.
7. Select and install patches. If you add patches to a previously patched instance,
the steps differ from the first patch installation.

Initial patch Additional patches

a. Click Add Solutions. a. Click Reinstall Solutions.
b. Select Teamcenter Visualization b. In the Reinstall Solution dialog

8 (Embedded Viewer) for Rich box, click OK.2
Client 4-Tier (installation and
Configuration) Patch and click c. In the Confirm dialog box, click
OK. Yes.
c. In the Modify Web Application d. In the Modify Required Context

dialog box, click OK to begin Parameters dialog box, click OK to
patching. begin patching.
d. After the patch is installed, click e. After the patch is installed, click
OK to close the Progress dialog OK to close the Progress dialog
box. box.
8. In the Modify Web Application dialog box, click OK.
10. Restart the distribution server.
After the installation is complete, the instance and the modified instance contains
the patch. Any rich clients previously installed from this instance has the patch
applied the next time the rich client is launched. Any future rich client installations
are installed with the patch.
Patch the Web tier

To install the Web tier, you must extract the INSTALL_TCWEB.TZ/EXE image
from the base release CD to a local directory on your machine and then run the Web
Application Manager (insweb.bat) from that local directory. You then must generate
a deployable (EAR or WAR) file and deploy that file on your Web application server.
The local directory in which you ran the Web Application Manager utility is called
WEB_ROOT.
Unzip the patch file (product-level_number_platform.zip ) to a temporary location.
This location is referenced in this procedure as WEB_FILES_LOC.
1. In Windows Explorer, browse to the WEB_FILES_LOC\Web_tier directory
and look at its contents.
2. Open the WEB_ROOT directory and run the Web Application Manager
(insweb.bat).
3. Click Copy ICDs.
4. Browse to the WEB_FILES_LOC\Web_tier\icd directory and click OK.
2. Adding patches reinstalls the patch solution with the newer files.

5. Select the Web application in the list corresponding to your Web tier installation
and click Modify.
6. In the Modify Web Application dialog box, click Modify Disk Locations.
7. In the Modify Disk Locations dialog box, click Add button to add the
WEB_FILES_LOC\Web_tier directory to the Disk Locations for Install Images
list.
8. In the Modify Disk Locations dialog box, click OK.
9. In the Modify Web Application dialog box, click Reinstall Solutions.
10. In the confirmation dialog box, click Yes to confirm the changes to the disk
location list prior to opening to the Reinstall Solutions dialog box.
11. In the Reinstall Solutions dialog box, click OK.
12. If the Modify Required Context Parameters dialog box appears, type the
appropriate values for any required context parameters and click OK.
13. The Web Application Manager regenerates the Web tier web application with
the patched files. Make sure a deployable file (EAR or WAR) is generated
during this process. If it is not, click Generate Deployable File in the Modify
Web Application dialog box.
14. After the deployable file is generated, go to the Web tier Web application’s staging
directory and find the deployable file (EAR or WAR) under the deployment
directory.
15. Take the new deployable file and deploy it to your Web application server,
replacing the previous deployment. The new deployable file contains the Web
tier patches.
Review the README file

The patch-id_pub.zip file includes a release_info directory that contains the patch
set README file. Review this README file for information about the patch and
possible additional steps required to complete the patch installation.

Chapter
23 Uninstalling Teamcenter
Uninstall Teamcenter configurations and installations . . . . . . . . . . . . . . . . . . 23-1
Uninstall TCCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Uninstalling DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2

Remove DB2 instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-3
Remove DB2 software on UNIX and Linux systems . . . . . . . . . . . . . . . . . 23-3
Remove DB2 software on Windows systems . . . . . . . . . . . . . . . . . . . . . . . 23-5
Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
Uninstall SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6

Chapter
23 Uninstalling Teamcenter
Uninstalling Teamcenter
If you need to uninstall a Teamcenter installation, remove Teamcenter configurations
using Teamcenter Environment Manager. You can then remove your database server.
Uninstall Teamcenter configurations and installations

Teamcenter Environment Manager uninstalls Teamcenter configurations. To
uninstall a Teamcenter installation, you must individually uninstall each
configuration in any order. If you have only one configuration, selecting it uninstalls
the Teamcenter installation.
1. Log on to the operating system using the user account under which you installed
Teamcenter.
2. Stop all Teamcenter services using the Services dialog box in the Windows
Control Panel.

Start→Programs→Teamcenter 9.1→Environment Manager
You can also run the tem.bat file in the install directory in the application root
directory for the Teamcenter installation.
4. In the Configuration Maintenance panel, select Remove Configuration

(uninstall), then click Next.
5. In the Old Configuration panel, select the configuration you want to remove,
6. In the Uninstall panel, select Yes to confirm that you want to uninstall the
configuration. Click Next.
7. In the Uninstall Teamcenter panel, select the Advanced Uninstall Options check
box if you want to view additional uninstall options. Otherwise, click Next.
8. In the Confirmation panel, click Start to begin the uninstallation.

Teamcenter Environment Manager removes the selected Teamcenter
configuration.
If the uninstallation is not successful, Teamcenter Environment Manager stops
processing when it encounters the error and displays a message indicating the
location of the log file containing the error.

Chapter 23 Uninstalling Teamcenter
9. If you selected the option in TEM to remove the Teamcenter database, the
database is moved to the Oracle recycle bin. To permanently remove the
database, launch SQL*Plus and enter the following command:
PURGE RECYCLEBIN;
10. Remove Teamcenter services by typing the following command in a command

prompt:
sc delete service-name
For a list of Teamcenter services, see the Services dialog box in the Windows
Control Panel.
Uninstall TCCS
If you installed Teamcenter client communication system (TCCS) as part of an
installation of the rich client or Teamcenter Microsoft Office interfaces, uninstalling
those clients automatically uninstalls TCCS from your system.
If you installed TCCS using the stand-alone installation wizard, perform the
following steps to uninstall TCCS.
1. Stop the FMS client cache (FCC) process:
a. Open a command prompt.
b. Change to the \tccs\bin directory in the TCCS installation directory.

Note
The default TCCS installation directory is C:\Program
Files\Siemens\Teamcenter9\tccs.
c. Type the following command:

fccstat -stop
After stopping the FCC process, the fccstat command reports that the FCC
is offline.
d. Close the command prompt.
2. Uninstall TCCS:
a. In the Windows Control Panel, open the Add or Remove Programs dialog
box.
b. In the list of installed programs, select and remove Teamcenter client

communication system.
c. Restart the system to unset the FMS_HOME environment variable.
Uninstalling DB2
If you no longer use your existing your DB2 instances and databases, you can
remove them.

If you want to uninstall your default DB2 copy but want to keep other DB2 copies
on your system, use the db2swtch command to choose a new default copy before
you proceed with the uninstallation. Also, if your database administration server
(DAS) is running under the copy you want to remove, move your DAS to a copy that
is not being removed. Otherwise, you must re-create the DAS using the db2admin
create command after the uninstall, and you may need to reconfigure the DAS
for some functionality to work.
Remove DB2 instances

1. Log on as a user with root privileges.
2. Type the following command:

• Windows systems:
DB2-HOME\sqllib\bin\db2idrop instance-name
• UNIX and Linux systems:

DB2-HOME/instance/db2idrop instance-name
Replace DB2-HOME with the DB2 installation directory you specified during
the DB2 installation. Replace instance-name with the login name of the DB2
instance.
Note
On UNIX systems, the default installation path is /opt/IBM/db2/Vversion.
On Linux systems, the default installation path is /opt/ibm/db2/Vversion.
The db2idrop command removes the instance entry from the list of instances and
removes the instance-home/sqllib directory. If you store any files in sqllib directory,
these files are removed by this action. If you still need these files, make a copy of
them before you remove the instance.
Optionally, as a user with root privileges, remove the instance owner’s user ID and
group (if used only for that instance). Do not remove these if you plan to re-create
the instance. Remove the database files from the system or drop the databases
before dropping the instance if you no longer need the databases. After you drop the
instance, the database files remain intact. This step is optional because the instance
owner and the instance owner group may be used for other purposes.
Remove DB2 software on UNIX and Linux systems

1. Optionally, drop all databases. You can drop databases using the Control Center
(on Linux platforms only) or the database drop command.
Note
If you drop databases without dropping instances first, database files
remain on your file systems.
2. Stop the DB2 Administration Server.

a. Log on as the DB2 administration server owner.

b. Stop the DB2 administration server by entering the db2admin stop

command.
3. Remove the DB2 administration server (DAS) by entering the following

command:
DB2-HOME/instance/dasdrop
Replace DB2-HOME with the DB2 installation directory you specified during
the DB2 installation.
Note
On UNIX systems, the default installation path is /opt/IBM/db2/Vversion.
On Linux systems, the default installation path is /opt/ibm/db2/Vversion.
4. Stop DB2 instances.

a. To obtain a list of the names of all DB2 instances associated with your
current DB2 copy, enter the following command:
DB2-HOME/bin/db2ilist
b. Log off.
c. Log on again as the owner of the instance you want to stop.
d. If the DB2 instance startup script is not included in the .profile file, enter
one of the following commands to run the startup script.
• Bash, Bourne, or Korn shells: . instance-home/sqllib/db2profile
• C shells: source instance-home/sqllib/db2cshrc
Replace instance-home with the home directory of the DB2 instance.

If you want to keep a copy of the database configuration settings, save
the database manager configuration file, db2systm, the db2nodes.cfg
file, or user-defined function or fenced stored procedure applications in
instance-home/sqllib/function.
e. Stop the DB2 database manager by entering the db2stop force command.
f. Verify that the instance is stopped by entering the db2 terminate command.
5. Remove DB2 instances as described in Remove DB2 instances.
6. Remove DB2 products.

a. Log on as a user with root privileges.
b. Access the path where the DB2 products are located.

For information about how to locate the path of the DB2 product to remove
using the db2ls command, see Listing DB2 products installed on your system
in the IBM DB2 Information Center Web site.

c. Run the db2_deinstall –a command from the DB2-HOME/install directory

or the doce_deinstall –a command from the DB2-HOME/doc/install
directory.
Remove DB2 software on Windows systems

1. Optionally, drop all databases. You can drop databases using the DB2 Control
Center or the database drop command from a command prompt.
Note
If you drop databases without removing instances first, database files
remain on your file systems.
Warning
Dropping databases after removing database instances permanently
deletes data.
2. Stop all DB2 processes and services. This can be done through the Windows
Control panel or by issuing the db2stop command from a command prompt.
If you do not stop DB2 services and processes before attempting to remove DB2
software, DB2 displays a warning that lists processes and services holding DB2
DLLs in memory.
3. Remove DB2 software by one of the following methods:

• Remove DB2 software using the Add/Remove Programs feature in the
Windows Control Panel.
• Open a command prompt and type the db2unins command.

To remove multiple DB2 products, use the /p argument:
ddb2unins /p
To remove DB2 software silently, use the /u argument:

ddb2unins /u
For more information, see the IBM DB2 documentation for the db2unins
command.
In some cases, neither of these methods successfully removes DB2 software. If

this happens, you can force removal of DB2 software by typing the following
command:
ddb2unins /f
Caution
This command removes all DB2 software and databases from your system.
Use this command only if other methods fail.

Uninstall Oracle
For information about uninstalling Oracle, see the Oracle installation guide on the
appropriate Oracle CD-ROM.
Uninstall SQL Server

1. Open the Add or Remove Programs dialog box in the Windows Control Panel.
2. Double-click Add or Remove Programs.

Windows displays the Add/Remove Programs dialog box.
3. From the list of installed programs, select SQL Server version and click Remove.
The program removes all files and directories created during the initial
installation. For more information about uninstalling SQL Server, see the SQL
Server documentation.

Part
VII Appendixes
Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Appendix
A Troubleshooting
Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . A-1

Installation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Problems/error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Update Manager FTP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Resolving Web tier connection problems . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Change the deployable file name on the corporate server . . . . . . . . . . . A-3
Change the deployable file name on the Web tier . . . . . . . . . . . . . . . . A-4
Web Application Manager needs location of Java file when installing rich
client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Make the Java jar file available for the four-tier rich client . . . . . . . . . A-4
Import of UGMASTER PDI part in GM Overlay fails . . . . . . . . . . . . . . . . A-4
Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . A-5
Troubleshooting the .NET Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Resolving thin client error on 64-bit Windows . . . . . . . . . . . . . . . . . . . . A-14
Troubleshooting Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . A-14
Troubleshooting document rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . A-17
Recovering from a corrupted database . . . . . . . . . . . . . . . . . . .... . . . . . . A-18

Recovering from a corrupted IBM DB2 database . . . . . . . . .... . . . . . . A-18
Recovering from a corrupted Oracle database . . . . . . . . . . .... . . . . . . A-18
Recovering from a corrupted Microsoft SQL Server database ... . . . . . . A-18

Appendix
A Troubleshooting
Troubleshooting
Troubleshoot problems you encounter during Teamcenter server installation.
Troubleshooting Teamcenter server installation

Find system log files or error messages to help you determine the source of the
problems you encounter. Perform the solutions provided.
Installation files
Teamcenter Environment Manager generates files in the install directory under the
Teamcenter application root directory.
• installdate-time_configuration-ID.log
Teamcenter Environment Manager generates a log file for each installation and
configuration you create. The log file contains a record of activities performed
by Teamcenter Environment Manager. Keep these files to maintain a complete
history for troubleshooting purposes.
• insautonomy.log
This file contains an installation record for Autonomy Intelligent Data Operating
Layer (IDOL) server, the default full-text search engine.
• configuration.xml
This file contains a record of the Teamcenter installation. Teamcenter
Environment Manager uses the configuration file to enable you to maintain the
installation, including adding and removing components, patching installations,
and upgrading installations.
Caution
Do not remove the configuration.xml file. Removing the
configuration.xml file results in the inability to modify the installation
using Teamcenter Environment Manager.
• uninstall.xml
This file contains a record of the Teamcenter uninstallation.
PLM00013 H Installation on Windows Servers Guide A-1

Appendix A Troubleshooting
In addition, auxiliary programs called by Teamcenter Environment Manager

generate files in the logs directory under the Teamcenter application root directory.
Most files have the format:
program-name.syslog
program-name.log
Of these files, the system log (.syslog) files usually contain the most relevant error
data.
Problems/error messages
See the following information for help resolving errors encountered during
Teamcenter installation.
Problem/error message Possible cause Solution

<<null>>\\<<null>> on Most likely indicates Start Teamcenter
host host-name does that you attempted Environment Manager
not have administrator to start Teamcenter as a user logged onto the
privileges Environment Manager system with Administrator
using the Windows runas group privileges and the
command or the Run Log on as a service right.
as menu command. For more information, see
Teamcenter Environment Required operating system
Manager cannot be and user accounts.
started as a user other
than the user logged on to
the operating system.
Online help installed for The Set the
thin client does not display WEB_core_help_server WEB_core_help_server
and WEB_help_server preference to the full path
preferences were not to the location of the online
set correctly by the help help/index.htm file.
installation program or
the installer. Set the
WEB_help_server
preference to the full
path to the location
of the online help
help/thin_client_dhtml/
book.html file.
Online help installed for Teamcenter Environment Check the
rich client (direct file Manager did not update portalHelpPage
access) does not display. the portalHelpPage property in the
property in the site_specific.properties
site_specific.properties file. If the path is not
file. present or incorrect,
manually correct it to refer
to the location of the online
help files in the file system.
A-2 Installation on Windows Servers Guide PLM00013 H

Troubleshooting
Update Manager FTP errors

The following table describes errors that can occur while connecting to the update
server or while downloading updates.
Error Resolution
Cannot contact server Host or port may be incorrect. Check Host and
Port values and try again.
Cannot log on User name or password may be incorrect. Check
User and Password values and try again.
Incorrect Path Path to the directory on the update server may
be incorrect. Check the path and try again.
Timeout Error The update manager received no response from
the update server. Try connecting later or contact
your system administrator for assistance.
Transfer Error Contact with the update server was interrupted.
Try your operation again or contact your system
administrator for assistance.
Resolving Web tier connection problems

If the Teamcenter Web tier and the corporate server do not reference the same Web
application name, the Web tier cannot connect to the Teamcenter server.
The Web application name specified in the Teamcenter Web tier must match the Web
application name specified on the corporate server.
During installation of the Teamcenter corporate server, you specify this value in the
Web Application Name box in the Default Site Web Server panel of Teamcenter
Environment Manager. The default Web application name is tc.
During installation of the Teamcenter Web tier, the Web Application Manager
assigns the Web application the default name of tc.
If you specify a Web application name other than tc during corporate server
installation, you must change the corresponding value during Web tier installation.
If the Web tier and the corporate server do not reference the same Web application
name, the Web tier cannot connect to the Teamcenter server.
To ensure the Web tier and the corporate server reference the same Web application
name, perform one of the following procedures:
Change the deployable file name on the corporate server
Using Teamcenter on a two-tier rich client host, set the

WEB_default_site_deployed_app_name preference to reflect the deployable
file name specified in Web Application Manager. (Alternatively, you can set this
preference using the preferences_manager utility from a command prompt.)
For more information about the WEB_default_site_deployed_app_name
preference, see the Preferences and Environment Variables Reference. For
information about setting preferences, see Getting Started with Teamcenter.

Change the deployable file name on the Web tier

1. In Web Application Manager, select your Web application and click Modify.
2. In the Modify Web Application dialog box, click Modify Web Application
Information.
3. Change the value in the Deployable File Name box to reflect the Web application
name you entered during corporate server installation.
4. Click Generate Deployable File to rebuild your Web application.
5. Deploy the rebuilt Web application on your Web application server.
Web Application Manager needs location of Java file when installing

rich client
Under certain circumstances, the Web Application Manager does not find the Java
jakarta-regexp-1.3.jar file required to install the four-tier rich client.
To resolve this problem, make the jakarta-regexp-1.3.jar file available to the Web
Application Manager.
Make the Java jar file available for the four-tier rich client
1. Locate the bmide\compressed_files directory in the Teamcenter software
distribution image.
2. Extract the bmide.zip file to a temporary directory. (This file contains the
jakarta-regexp-1.3.jar file.)
3. Add the temporary directory to the list of Disk Locations for Install Images in
the Web Application Manager.
4. Build your Web application EAR file using the Web Application Manager.
5. Deploy your EAR file as described in the Web Application Deployment Guide.
Import of UGMASTER PDI part in GM Overlay fails

If you attempt to create a CORP_ item, it sometimes fails in GM Overlay databases
upgraded from Engineering Process Management 9.1.3 or Engineering Process
Management 2005 to Teamcenter 9.1. This occurs when legacy action rules are not
removed from the database during the upgrade.
After upgrading to Teamcenter 9.1, follow the instructions in the Business Modeler
IDE Guide to migrate the GM Overlay action rules to extension rules and delete
the action rules. Some GM Overlay action rules have already been migrated to
extension rules and are shipped as part of the Teamcenter Automotive Edition and
GM Overlay templates. After you extract your database in step 2 of Convert action
rules to extension rules, verify the extracted action rules against the extensions in
the template. If there are no additional action rules to be converted in the Business
Modeler IDE templates, you can skip steps 3–5 in the procedure. Some of the GM
Overlay action rule names are modified in Teamcenter 2007. The table shows the
mapping of action rules to extension rules.

Troubleshooting
Engineering Process Management 9.1.3 Teamcenter 2007 – GM Overlay method

– GM Overlay action rules extensions
GMPDM_CM_baseline_preaction GMO_check_baseline_preaction
GMPDM_CM_set_pdi_comments GMO_set_baseline_comments
CUSTOM_CM_validate_sec_objs GMO_validate_sec_objs
GMPDM_check_gm_bldintent_rel GMO_check_gm_bldintent_rel
GMPDM_ask_gm_buildintent_props GMO_ask_gm_buildintent_props
GMPDM_CM_copy_forward_attrs GMO_CM_copy_forward_attrs
GMPDM_CM_cond_create_pwt_forms GMO_cond_create_pwt_forms
GMPDM_CM_cond_saveas_pwt_forms GMO_cond_saveas_pwt_forms
GMPDM_CM_copy_pwt_part_forms GMO_copy_pwt_part_forms
PWT_reset_actual_mass GMO_PWT_reset_actual_mass
GMPDM_CM_copy_cost_forms GMO_CM_copy_cost_forms
GMPDM_CM_delete_cost_form GMO_CM_delete_cost_form
GMIMAN_notifyIRCreation GMO_notify_on_ir_creation
GMPDM_delete_product_def_form GMO_delete_product_def_form_ptr
GMPDM_validate_product_def GMO_validate_product_definition_entries
Note
Deleting the legacy action rules after successfully upgrading the GM Overlay
may change expected behavior in some areas of the GM Overlay. For
example, you cannot create item types like CORP_Part, CORP_Install,
CORP_Product, and CORP_Software.
Troubleshooting four-tier architecture deployment

Identify the problem you encountered in your four-tier rich client architecture and
perform the solution described.
Problem Solution
Web-tier application fails during When a host has multiple IP addresses, the JGroups software
initialization with an error and JDK software arbitrarily choose one of them to use as
containing the following: the address to bind to for a server connection port. In some
situations, as when using a Windows Network Load Balancer,
Error during login. not all local IP addresses are accessible to other hosts on the
com.teamcenter.presentation. network. If the chosen IP address is not accessible, other
webclient.actions com. cluster peers are not able to open sockets to that port.
teamcenter.jeti.util.
JetiResourceConfiguration To avoid this error, specify a particular bind address using the
Exception: TreeCache bind.address Java system property, for example:
initialization failed
Dbind.address=123.456.78.91
Java arguments can be specified in different ways

on different application servers. For example, for a

Problem Solution
WebLogic managed server, use the WebLogic console
server/Configuration/Server Start/Arguments field.
For more information, consult the application server’s
documentation.
Error indicating no server pool Either the server manager is not started or TreeCache
communication is not occurring. Ensure that you correctly
coordinated the server manager and Web tier TreeCache
configuration settings.
For information about coordinating these settings, see the
description of the server manager context parameters in Web
tier required parameters.
If you are using TCP communication, look for the GMS
address during both application server startup and server
manager startup. The GMS address indicates the service port
obtained. It should be within the range of ports pinged by
TreeCache peers.
Delays in opening a connection The Web tier may be attempting a connection to the
from the Web tier to a Teamcenter Teamcenter server on an IP address that is unavailable.
server
If the SERVER_HOST parameter is not specified in the
server manager configuration, the Teamcenter server writes
all IP addresses found in the host’s network configuration
to its CORBA interoperable object reference (IOR). If the
host has multiple addresses and the primary address is
not reachable, the Teamcenter Web tier logs the following
warning:
The connection to the pool with ID pool—ID is not
available. Primary Address Host is IP-address and
the Primary Address Port is port; In addition to
the Primary Address, additional address(es) were
found. Please ensure that the Primary Address used
is the right one. This address can be changed by
configuring the SERVER_HOST parameter.
Inspect the Web tier log file for status messages reported
during server manager startup. If the server manager log
contains a message similar to this, set the SERVER_HOST
parameter in the serverPool.properties file to the correct
IP address for the host.
Warnings of discarded messages These warnings indicate that you have two clusters on the
same port (multicast) or set of ports (TCP).
Your environment is working because you used different
names for each cluster, but this is not an optimal environment
for performance. Siemens PLM Software recommends
configuring a different port or set of ports for each
environment.

Troubleshooting
Problem Solution
Error messages about the server These messages indicate that the pool ID is in use by another
manager pool ID server manager in the TreeCache cluster. Either place the
server managers in different clusters or configure a distinct
pool ID.
Occasionally, TreeCache instances fail to accept connections
and report handleJoin errors. Typically this error disappears
if you restart one or more cluster members.
handleJoin errors occur at To get additional information, increase the logging level for
startup the tree cache and jgroups classes for both the application
server and server manager:
1. Copy the log4j.xml file in the server manager run-time
directory (TC_ROOT\pool_manager) to the application
server instance startup directory.
By default, the server manager run-time directory
includes a log4j.xml file, but it logs only the warning level
information. The default configuration sends log output
to the console and the following files:
TC_ROOT\pool_manager\logs\ServerManager\
process\serverManager.log
APPSERVER_ROOTlogs\WebTier\processWebTier.log
2. Edit log4j.xml so that more information is logged at run

time. For example, to increase the log4j output for the
JBossCache and jgroup classes to the INFO level, edit
the file:
<logger name="org.jboss.cache" additivity="false">
<level value="INFO"/>
<appender-ref ref="WebTierAppender"/>
<appender-ref ref="ProcessConsoleAppender"/>
</logger>
<logger name="org.jgroups" additivity="false">
<level value="INFO"/>
<appender-ref ref="WebTierAppender"/>
<appender-ref ref="ProcessConsoleAppender"/>
</logger>
The JMX HTTP adaptor allows you to view the status of the
server pool and dynamically change the pool configuration
values (the values are not persistent). Access this functionality
from the following URL:
http://host-name:jmx-port
Replace host-name with the name of the host running the
server manager. Replace jmx-port with the number of the
port running the JMX HTTP adaptor. This port number is
defined on the JMX HTTP Adaptor Port parameter when
you install the server manager.

Problem Solution
Configuration is correct, but Determine from logs whether users are frequently losing a
run-time errors occur server due to the server timing out and are then having a new
server assigned.
Server startup can consume a great amount of CPU. Consider
increasing timeout values and/or the pool size.
TreeCache connection failure Terminating a server manager instance by sending it a signal
after restarting or redeploying does not clean up the TreeCache data stored in other four-tier
components regarding the terminated pool. When this server
manager is restarted, it cleans up this information. However,
termination of a server manager in this way sometimes leaves
the TreeCache communication mechanisms in a corrupted
state and the server manager is not able to rejoin the
TreeCache cluster. The problem can be resolved by stopping
all four-tier components (the application servers and server
managers) in the TreeCache cluster and then restarting them
all. This problem can usually be avoided by shutting the
server manager down cleanly through the server manager
Administrative Interface. For information about using the
server manager administrative interface, see the System
A similar problem can occur after the Teamcenter Web tier
application is redeployed on the application server without
stopping and restarting the application server. In this case, an
extra TreeCache instance from the earlier deployment might
still be running in the application server and this can interfere
with proper functioning of the TreeCache. This can usually be
resolved by stopping and restarting the application server.
Due to a Java run-time issue on Linux, these problems are
more likely if the four-tier component is run with the nohup
command on Linux and the process is terminated by sending
it a signal.
TreeCache initialization fails The following error messages in the log files indicate that the
when starting the server TreeCache port is already in use:
manager or Web tier application FATAL - None - 2007/07/27-16:11:13,244 UTC - host- TreeCache
initialization failed:
com.teamcenter.jeti.serverassigner.ServerAssigner
org.jgroups.ChannelException: failed to start protocol stack
Caused by: java.lang.Exception: exception caused by TCP.start():
java.net.BindException: No available port to bind to
This error indicates that the TreeCache local service port you
have configured is already in use either by another TreeCache
instance or by some other process. To resolve this problem,
choose a different port and restart/redeploy the reconfigured
server manager or Web tier application.

Troubleshooting
Problem Solution
CFI_error displays when running When you run AIE Export in batch mode, Teamcenter displays
AIE export in batch mode a CFI error. This error occurs because jt.exe (Microsoft Task
Scheduler) file is missing from the %WINDOWS% directory.
To resolve this problem, perform the following steps:
1. Download the jt.zip utility from the following Web site:
ftp://ftp.microsoft.com/reskit/win2000
2. Extract the jt.exe file from the jt.zip file and copy it to
your TC_ROOT\bin directory.
Server manager is not If your server manager is joining a existing TreeCache
used/recognized by the Web cluster, the TreeCache Peers parameter for the server
tier application when the manager must contain the host name and port number of
manager is restarted without a Web application server running the Web tier application
restarting the Web tier or the host/port pair of a server manager that has the Web
application server configured as a peer.
In a simple environment with one manager and one Web tier
instance, you should configure the server manager to have the
Web tier instance as a peer and the Web tier application must
contain the server manager host and local service port in the
TreeCache Peers context parameter. This allows you to start
the server manager or the application server independently.
For information about installing the server manager, see
Installing the server manager. For information about
starting and managing the server manager, see the System
For information about Web application context parameters,
see Web tier context parameters.
A server manager crash occurs An error message, similar to the following, appears in the
with an error in the Java output Java output and is identified in the hs_err_* file as an error
that indicates the JVM detected in a compiler thread.
an unexpected error #
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (11) at pc=ab2727b4, pid=183, tid=9
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0.03 jinteg:02.13.06-15:
# 51 PA2.0 (aCC_AP) mixed mode)
# Problematic frame:
# V [libjvm.sl+0xa727b4]
#
# An error report file with more information is saved as
# hs_err_pid183.log
#
# Please report this error to HP customer support.
#
./run.sh[175]: 183 Abort(coredump)
Excerpt from the hs_err_* file:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6da225d6, pid=1272,
# tid=3168
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_05-b05 mixed mode)
# Problematic frame:

Problem Solution
# V [jvm.dll+0x1e25d6]
#
--------------- T H R E A D ---------------
Current thread (0x26a0adb0): JavaThread "CompilerThread1" daemon [
_thread_in_native, id=3168]
.
.
.
Current CompileTask:
opto:1020 s! org.jacorb.orb.Delegate.request(Lorg/omg/CORBA/Object;
Ljava/lang/String;Z)Lorg/omg/CORBA/portable/OutputStream; (266 bytes)
This is due to a known Java defect affecting the JVM. It may

occur when there are enough calls to the server to cause the
JRE to dynamically compile the relevant CORBA method.
Sun recommends the following workarounds:
• Add the JVM parameter –XX:-EliminateLocks. (Some
versions of Java do not support this parameter.)
• Use the .hotspot_compiler file to disable the compilation

of the jacorb Delegate.request() method. See the
documentation for your Java version to determine the
proper location and contents of this file.
• Move to a later JVM.

During a server manager On some platforms or machines, the jgroups code used
startup or J2EE Web application by TreeCache in the Teamcenter server manager or the
deployment the following error Teamcenter J2EE application may fail to initialize when
message is received when using using mcast mode. This may be caused by using IPv6. This
multicast mode: is to known to occur when using a Linux host but may also
java.net.BindException: occur in other configurations.
Can’t assign requested address
The following is a typical exception message with this error:
ERROR - 2007/07/29-00:55:20,866 UTC - cili6008 - Error initializing
JBoss Cache com.teamcenter.jeti.serversubpoolmanager.
ServerPoolManager
org.jgroups.ChannelException: failed to start protocol stack
at org.jgroups.JChannel.connect(JChannel.java:393)
at org.jboss.cache.TreeCache.startService(TreeCache.java:
1249)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(Service
MBeanSupport.java:274)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.
java:181)
at com.teamcenter.jeti.SharedStore.init(SharedStore.java:144)
at com.teamcenter.jeti.serversubpoolmanager.ServerPoolManager.init
Cache(ServerPool Manager.java:2092)
at com.teamcenter.jeti.serversubpoolmanager.ServerPoolManager.fini
shInit(ServerPoolManager.java:449)
at com.teamcenter.jeti.serversubpoolmanager.ServerManager.main(Ser
verManager.java:1480)
Caused by: java.lang.Exception: exception caused by UDP.start():
java.net.BindException: Cannot assign requested address
at org.jgroups.stack.Protocol.handleSpecialDownEvent(Protocol.java
:600)
at org.jgroups.stack.DownHandler.run(Protocol.java:117)
If this occurs during server manager startup, uncomment the

last line in the following block of the mgrstart script file, and
restart the server manager.
# Uncomment this line to tell Java to prefer IPv4 addresses.
# This can fix socket errors on systems that do not have a fully
# functional IPv6 configuration. A similar change may be needed
# in the startup script for a J2EE application server.
#JVM_ARGS="${JVM_ARGS} -Djava.net.preferIPv4Stack=true"
If this error occurs during J2EE application deployment,

consult your application server vendor’s documentation for the

Troubleshooting
Problem Solution
proper JVM arguments settings. Another possible solution
is to use TCP mode instead of mcast mode for both the
Teamcenter server manager and J2EE application.
A CORBA COMM_FAILURE This error usually indicates one of the following:
error is reported in the Web tier
1. The Teamcenter server has terminated while processing
a request.
2. The Teamcenter server encountered a serious error (for

example, failed memory allocation) while attempting to
process a request.
The message generally does not indicate a problem in the

Web tier itself. Teamcenter server syslog files may contain
information useful in diagnosing the root cause of Teamcenter
server failures.
After publishing an item to A Teamcenter Web application deployed on a Sun Java System
an ODS, the Sun Java System Application Server can become unresponsive. This can occur
Application Server becomes especially when:
unresponsive.
• You publish and item to the default ODS site that is also
the site publishing the item.
• You attempt to view the published item’s details in the

home folder.
To correct this problem, ensure that you have set the Thread
Count and Initial Thread Count to at least the minimum
values required (25 and 15 respectively) and restart the
application server.
Note
Depending on Teamcenter Web tier activity, you may
have to set these values higher than the minimum to
get the best performance.
Client-side Java session cookies Multiple applications deployed in the same WebLogic domain
are overwritten by Web tier can cause client session cookies to overwrite each other. To
applications deployed in the avoid this, deploy your Teamcenter Web application in a
same domain on a WebLogic domain by itself or ensure each application has a separate
application server. cookie path.
To set your Web application session cookie path:
1. Navigate to the
WEB-ROOT/staging-directory/webapp_root/WEB-INF
directory for the application.
Note
WEB_ROOT is the location where you installed
the Web Application Manager (insweb), and

Problem Solution
staging-directory is the directory where the specific
Web application was generated.
For information about building J2EE Web
applications with the Web Application Manager, see
J2EE Web tier installation.
2. Open the weblogic.xml file and add the following

elements:
<session-param>
<param-name>CookiePath</param-name>
<param-value>/deployable-name</param-value>
</session-param>
Replace deployable-name with the deployable file name

set in the Web Application Manager, for example, tc.
3. Launch the Web Application Manager (insweb).
4. Select the Web application name and click Modify.
5. In the Modify Web Application dialog box, click Generate

Deployable File.
6. In the Generate Deployable File dialog box, click OK.

The Web Application Manager displays the status of
the installation in the Progress dialog box. When the
installation is complete, click OK to close the Progress
dialog box.
7. Click OK to close the Modify Web Application dialog box.

During peak activity, the Web The Teamcenter Web application is using all available
tier encounters errors obtaining connections in the connection pool. To avoid this, increase
JCA connections. the number of available connections by increasing the
Max_Pool_Size context parameter value in the Web
application EAR file.
To set your Web application maximum connection pool size:
1. Launch the Web Application Manager (insweb).
For information about building J2EE Web applications
with the Web Application Manager, see J2EE Web tier
installation.
2. Select the Web application name and click Modify.
3. In the Modify Web Application dialog box, click Modify

Context Parameters.

Troubleshooting
Problem Solution
4. In the Modify Context Parameters dialog box, locate

Max_Pool_Size, double-click the Value column, and type
a larger number.
5. Click OK and click Generate Deployable File.
6. In the Generate Deployable File dialog box, click OK.

The Web Application Manager displays the status of
the installation in the Progress dialog box. When the
installation is complete, click OK to close the Progress
dialog box.
7. Click OK to close the Modify Web Application dialog box.
8. Redeploy the EAR file in your application server.

Chinese characters are If you use a nonnative language operating system version of
displayed as square blocks Windows, you must install and enable the Multilingual User
in the Teamcenter rich client. Interface (MUI) pack to ensure the language font is displayed
properly.
1. Download and install the MUI pack for Windows from
Microsoft.
2. Open the Regional and Language Options dialog box in

the Windows Control Panel.
3. In the Languages tab, set the required language for the

menus and dialogs.
4. In the Advanced tab and the Regional Options tab, set

the required language.
During successive calls to get During large Global Services transactions, such as a
activity status in the Global replication manager transaction during site consolidation
Services user interface, out of orchestration, you may encounter a Java out of memory
memory errors are displayed. error from the application server. This usually is caused by
repeated checks on activity status (AuditActivity business
object) from the Global Services user interface.
The Java virtual machine (JVM) size grows with each call
to get the status. To avoid this, reduce the application
server’s Java memory property to between 1200m and 1500m
(-Xmx1200m or -Xmx1500m, respectively).
Troubleshooting the .NET Web tier

Find solutions to problems in your .NET Web tier installation.

Resolving thin client error on 64-bit Windows

When installing the Teamcenter server on a host running 64-bit Windows Server
2008, you may encounter the following error during the thin client installation:
Unable to run aspnet_regiis.exe -s
To correct this problem, perform the following steps.

1. Open a command prompt and type the following command:
SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
This installs ASP .NET 2.0 and the script maps at the IIS root.
For more information about the ASP .NET
IIS Registration Tool (Aspnet_regiis.exe), see
http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx.
2. In the command window, type the following:

SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\
aspnet_regiis.exe -s W3SVC/IIS_Web_Site_Identifier/
ROOT/"virtual_directory_or_web_application_name"
IIS_Web_Site_Identifier is the actual ID that references the Web site and can be
found in the IIS Manager column called Identifier.
virtual_directory_or_web_application_name is the name of the Web application.
For example, aspnet_regiis.exe -s W3SVC/806598041/ROOT/”tc”).
This installs the script map to the specified application root path.
3. Resume the Teamcenter installation.
Troubleshooting Teamcenter online help

After you create the virtual directory and restart IIS as described in Install online
help on the .NET Web tier, your Web browser may display the following error when
you access Teamcenter online help:
This page cannot be displayed.
If this happens, verify the values of the following Teamcenter preferences to make
sure the path to the online help is correct:
WEB_help_server
WEB_core_help_server
If the problem persists after verifying these preferences, move the help directory
that contains the online help files into the tc Web deployment directory under the
TC_ROOT\net_webtier directory.
Troubleshooting document rendering

If you are not successful rendering document revisions to translate dataset files, your
administrator should review your installation and configuration systematically and
verify the following requirements are met.

Troubleshooting
• Installation of Teamcenter lifecycle visualization Convert software is required by

the previewservice feature.
o You must select the Convert feature; the Print feature is optional.
o The destination installation directory name must not contain spaces.
o To accommodate high levels of input and output, modify the vvcp.ini file on
Windows systems, or the vvcp.platform.cfg file on UNIX systems.
FileCheckWait=600
FileCheckWaitForZero=30
o When the installation is complete, verify the Convert option prepare.exe

program exists under the VVCP installation directory.
For more information about verifying this part of the setup, see the
Dispatcher Server Translators Reference Guide.
• Installation of Ghostscript 8.53 software required by the previewservice

feature.
o A free Ghostscript installer is available at the following link:

http://ftp.ugs.com/open-source/ghostscript/gs853
o On UNIX platforms, after you install Ghostscript, set the PSPath setting
in the Convert and Print configuration file (vvcp.ini) to the location of the
Ghostscript application.
For example: *PSPath: /apps/gs853/bin/gs.
o Set AllowOpenApplication=on to support the use of applications, such as

Microsoft Word, that may already be open when the Convert process begins.
• Installation of the Adobe LiveCycle ES 8.2.1 software required by the

pdfgenerator utility.
Ensure native application support for LiveCycle PDF Generator ES is enabled.
When configuring the Result Watched folder directory:
o Do not append %Y/%M/%D in the result folder directory.

For example:
Result Folder: result

Include File Pattern: *
o Path
Specify the location of the watched folder directory.
Adobe LiveCycle creates this directory if it does not already exist; use a
short path.

Note
The input directory is created under the specified Path directory
location. This is the watched folder input directory.
For example, if the path is:
D:\LCWatchedFolder
The watched folder input directory path is:

D:\LCWatchedFolder\input
o Wait Time
Duration in milliseconds to wait for before picking up the file/folder. Increase
this number for large file.
o Operation Name
Select CreatePDF.
o Input Parameter Mappings

For inputDocument, select Variable and enter *.*
o Output Parameter Mappings

For Result, enter %F.pdf
After LiveCycle PDF Generator ES is installed, you must create and configure
the Adobe LiveCycle Watched Folder Endpoint as described in Adobe LiveCycle
Endpoint Management documentation. The specified watched folder input and
result directory locations are needed during the installation of PdfGenerator
translator.
For more information, see the Dispatcher Server Translators Reference Guide.
After the watched folder endpoints are set, you may also need to modify the
default applications extension file type settings to specify additional filename
extensions for file types for generating PDF output.
For more information about these configuration tasks, see the Adobe LiveCyle
ES documentation.
• You must enable the RenderMgtTranslator service and one or both of the
following services:
o PreviewService
o PdfGenerator
Configure translation services by enabling and configuring translators using

TEM.
For more information about setting up and configuring translators, see the
Dispatcher Server Translators Reference Guide.
o PreviewService

Troubleshooting
Required Teamcenter Visualization Convert 8. Ghostscript v 8.53, and

source authoring applications such as Microsoft Office application (2003,
2007) are also required.
o PdfGenerator
Requires Adobe LiveCycle PDF Generator ES. The configuration file must
specify the Adobe watched folder input and watched folder result directory
location. Source authoring applications such as Microsoft Office application
(2003, 2007) and Adobe Acrobat 8.x are also required.
o RenderMgtTranslator
Required for either PreviewService, PdfGenerator, or any other service
to be added.
• Use Business Modeler IDE to set up and deploy IRDC and dispatcher service
configuration objects to the Teamcenter database.
Troubleshooting Teamcenter Integration for NX

Teamcenter Integration for NX may be unresponsive in a four-tier rich client if you
specify an incorrect value for Web Application Name during installation of the
Teamcenter corporate server.
During corporate server installation, TEM prompts for the Web application name
in the Default Site Web Server panel. The Web application name you enter is
used to populate the WEB_default_site_deployed_app_name preference in the
Teamcenter database. When you build the Teamcenter Integration for NX Web
application in Web Application Manager, you specify the actual name of the Web
application.
If the name of the deployed Web application does not match the value specified in
TEM, the Web application fails to connect to the Teamcenter server.
If you experience problems starting Teamcenter Integration for NX from the four-tier
rich client, inspect the ugs_router system log for messages that resemble the
following example:
INTEROP: Executing: O:\win32\ugnx5.0.0.22\ugii\ugraf.exe -pim=yes -
http_url=http://AcmeCorp:8080/tc/aiws/aiwebservice -soa_url=http://AcmeCorp:8080/tc"-
http_cookie=IMAN=08100000000000madakash45b765e1cd0ea854705e5f8f; path=/;" -
http_vmid=b6e51c5aaaf5b200:-58275229:1104f3e3952:-8000 "-role=ALL" -
portalinfo=localhost:2377:PROCESS_COMMAND_LINE -
invoke=com.teamcenter.rac.commands.objectschanged.ObjectsChangedCommand+-uids=%s+-
src=madakash@4Tier_w__NX :madakash@4Tier_w__NX 4-tier
INTEROP: Waiting for UG/Manager V23.0 1 to start up...
This message results from the rich client expecting a Web application named tc but
being unable to find it.
To resolve this problem, set the WEB_default_site_deployed_app_name preference
to the correct name of the deployed Web application. You can update this preference
using the preferences manager from the command line or from within the rich client.
For information about using the preferences manager, see the Preferences and
Environment Variables Reference.

Recovering from a corrupted database

If you attempt to install Teamcenter using a database that is only partially installed,
Teamcenter Environment Manager (TEM) allows you to drop all existing data before
beginning a new installation.
If the Teamcenter database is corrupted beyond repair, you can alternatively delete
the database and repeat the installation using an empty database. To do this,
perform the appropriate procedure, depending on your database vendor:
• Recovering from a corrupted IBM DB2 database
• Recovering from a corrupted Oracle database
• Recovering from a corrupted Microsoft SQL Server database
Recovering from a corrupted IBM DB2 database

1. Use either of the following tools to delete a corrupted database in an IBM
DB2-based installation:
• IBM Control Center
In the Control Center application, select the database you want to delete
from the list of databases, right-click the database and then select Drop.
This also deletes the appropriate data files.
• Command Line Editor tool

Start the command line utility and then type the following command:
DROP DATABASE TC
2. Create a new DB2 database for Teamcenter.

For more information, see Create a DB2 database for Teamcenter
3. Launch TEM and reinstall Teamcenter.
Recovering from a corrupted Oracle database

1. Delete the database using Oracle Database Configuration Assistant (DBCA).
2. Create a new empty database using the appropriate DBCA template file.
Recovering from a corrupted Microsoft SQL Server database

1. Remove the corrupted database using the Microsoft SQL Server Management
Studio. Right-click the appropriate database in the tree view and choose Delete.
This removes the database and the associated data files.

TEM creates a new database during installation.

Appendix
B Distribution media
Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Teamcenter documentation distribution image . . . . . . . . . . . . . . . . . . . . . . . B-2

Appendix
B Distribution media
Distribution media
Siemens PLM Software distributes the following software and documentation
images for Teamcenter 9.1:
Image Description
Teamcenter software Contains Teamcenter software for your operating system
(Hewlett-Packard HP-UX, IBM AIX, Sun Solaris, Linux,
Apple Macintosh, or Microsoft Windows). The software
distribution image includes Teamcenter installation
programs (Teamcenter Environment Manager and Web
Application Manager) and required files for Teamcenter
features such as Security Services.
For a detailed description of the contents of this image, see
Teamcenter software distribution image.
Note
Teamcenter software distribution images can
contain multiple ZIP files. For example, the
software distribution image for Windows consists
of two files named Tcn_win_1_of_2.zip and
Tcn_win_2_of_2.zip. If you download software
distribution images for Teamcenter, you must
download all files in the set to obtain the complete
image. After you download files, extract all ZIP files
to a common directory to assemble the image before
you begin installation.
Teamcenter Contains the archive file required for installing Teamcenter
documentation online help (tchelp.jar), Teamcenter documentation in PDF
format, and Teamcenter documentation in HTML format.
For a detailed description of the contents of this image, see
Teamcenter documentation distribution image.
Rich client Contains the files required to install the Teamcenter rich
over-the-Web client over-the-Web on all supported operating systems,
including a rich client distribution server and Over-the-Web
Installer.
Visualization Contains the files required to install Teamcenter lifecycle
visualization on all supported operating systems.
PLM00013 H Installation on Windows Servers Guide B-1

Appendix B Distribution media
Image Description
Oracle Contains directories, files, and scripts used to install Oracle
Enterprise Edition. The contents of this image are identical
to the Oracle Enterprise Edition CD-ROM distributed by
Oracle.
Teamcenter software distribution image

The following table describes the directories in the Teamcenter software distribution
image:
Directory Description
additional_applications Contains directories containing applications such
as the Teamcenter EDA client, Teamcenter client
communication system (TCCS), Security Services,
and the Siemens PLM Software Common Licensing
Server.
additional_documentation Contains instructions for installing Oracle RDBMS.
advanced_installations Contains the resource_management
subdirectory that contains Resource Manager
application files for Teamcenter manufacturing
process management.
bmide Contains the Business Modeler IDE.
cci Contains the CCI client.
install Contains files required for installing Teamcenter.
localization Contains localization and internationalization files
for the rich client and the thin client.
logmanager Contains the log manager application.
mappingdesigner Contains the mapping manager application.
portal Contains Teamcenter rich client files.
tc Contains the Teamcenter software files.
Web_tier Contains the Web Application Manager program
and supporting files for generating the Web tier
application and the rich client distribution server
and instance WAR files.
The base directory of the Teamcenter software distribution image also contains
Teamcenter Environment Manager program (tem.bat) that installs Teamcenter
executables and data directories.
Teamcenter documentation distribution image

The Teamcenter documentation distribution image contains the archive file required
for installing Teamcenter online help (tchelp.jar) plus the following directories:
B-2 Installation on Windows Servers Guide PLM00013 H

Distribution media
• PDF
Contains the Teamcenter online help library in PDF format. To display the
online help library index page, open the index.htm file.
• javadoc
Contains documentation for Teamcenter user interface components you can
use in your rich client customizations. This documentation is also provided in
the JavaDoc.zip file in the root directory of the Teamcenter documentation
distribution image.
For more information about this documentation, see the Client Customization
Programmer’s Guide.
• additional_documentation
Contains additional documentation for use with Teamcenter. This includes
guides for using the Siemens PLM Software common licensing server.
Note
If you want to view the Teamcenter online help library in HTML format,
expand the tchelp.jar from the Teamcenter documentation distribution
image to a local directory. To display the online help library index page, open
the index.htm file in the help directory.
If you use popup blocker software, configure it to allow popups within the
Teamcenter online help library.
PLM00013 H Installation on Windows Servers Guide B-3

Appendix
C Solutions and features reference
Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14

Appendix
C Solutions and features reference
Solutions and features reference

Teamcenter Environment Manager (TEM) provides solutions and features you can
include in Teamcenter server or client configurations. The Web Application Manager
provides rich client solutions you can add to rich client distribution instance.
Teamcenter solutions
Solutions are preselected groups of features that provide starting points for
recommended Teamcenter configurations. You can add features or deselect features
in the Features panel in Teamcenter Environment Manager (TEM). For information
about a solution, point to the solution name in the list. TEM displays a description.
Solution Features
Corporate Server Teamcenter Foundation
FMS Server Cache
NX UG Integration
Dispatcher (Dispatcher Server) Dispatcher Server
Volume Server FMS Server Cache
Rich Client 2-tier Teamcenter Rich Client 2-tier
Rich Client 4-tier Teamcenter Rich Client 4-tier
Multisite Collaboration Proxy Server Multisite Collaboration IDSM Service
Multisite Collaboration ODS Service
EDA Standalone Client EDA Standalone Client
Mentor Board Station Support
Mentor PADS Support
Cadence Allegro Support
Gateway for EDA Library
Mentor Board Station Library Support
Mentor Expedition Library Support
Cadence Allegro Library Support
Mentor PADS Library Support
Business Modeler IDE Business Modeler IDE Standalone
Global Services Teamcenter Foundation
J2EE Based Server Manager
FMS Server Cache
Global Services Framework
Global Services Preferences
PLM00013 H Installation on Windows Servers Guide C-1

Appendix C Solutions and features reference
Teamcenter features
TEM provides the following features and feature groups in the Features panel.
Features are grouped by related applications. For information about a feature, point
to the feature name in the list. TEM displays a description of the feature.
Note
• Some features are disabled because they require other features. To enable
a feature, select its prerequisite features. For information about feature
prerequisites, see the feature description.
• Some features cannot be installed in the same configuration, so selecting

one disables the other.
Teamcenter features
Feature/Subfeature Description
Base Install Base Teamcenter server and client components.
Teamcenter Foundation Installs the complete Teamcenter application root directory (TC_ROOT),
including the Teamcenter server process (tcserver), and either creates
a data directory for storing database-specific files or configures this
installation to connect to an existing data directory.
If you create a data directory, you also provide information about the
database to use with this installation. If you specify a new database,
Teamcenter Environment Manager populates the database and creates a
volume.
Installing Teamcenter Foundation is optional only when you install the

following components: the Multi-Site Collaboration proxy servers, File
Management System, online help, or sample files. When you install these
components, Teamcenter Environment Manager creates an TC_ROOT
directory, but populates it with only the subdirectories necessary for these
components to run.
Teamcenter Rich Client (Shared Disk Deployment) Installs the rich client in a shared location. This client can be run from
multiple hosts.
Teamcenter Rich Client 2-tier Installs a two-tier rich client and optionally configures it for use with
additional features and applications, such as Teamcenter lifecycle
visualization and NX Manager.
Teamcenter Rich Client 4-tier Installs a four-tier rich client and optionally configures it for use with
additional features and applications, such as Teamcenter lifecycle
visualization and NX Manager.
Business Modeler IDE 2-tier Installs the two-tier Business Modeler IDE client. This client connects to
the Teamcenter server using IIOP.
Business Modeler IDE 4-tier Installs the four-tier Business Modeler IDE client. This client connects to
a Teamcenter server in a four-tier environment using HTTP.
Business Modeler IDE Standalone Installs only the Business Modeler IDE client without requiring a
connection to a Teamcenter server.
Teamcenter Rich Client (Lite Edition) Installs a rich client and configures it for use with the NX Manager
feature. This feature requires NX Manager for Rich Client.
Server Enhancements Additional features for Teamcenter servers.
C-2 Installation on Windows Servers Guide PLM00013 H

Teamcenter features
J2EE Based Server Manager Installs the process that manages the pool of Teamcenter server processes.
This option is applicable only when you are deploying the Web tier. This
feature requires Teamcenter Foundation and FMS Server Cache features.
For a smaller site, you can install the server manager and Teamcenter
servers on the same host as the Web tier application. For deployment
options for larger sites, you can install the server manager on a separate
host.
.NET Based Server Manager Installs the process that manages the pool of Teamcenter server processes.
This option is applicable only when you are deploying the Web tier. This
feature requires Teamcenter Foundation and FMS Server Cache features.
Full Text Search Engine Installs Autonomy Intelligent Data Operating Layer (IDOL) server, the
default full-text search engine, and configures searching for the local
database.
Autonomy IDOL enables users to retrieve objects from the Teamcenter

database based on search criteria. It allows users to specify searches on
metadata values, as well as full text retrieval searches on both metadata
and common forms of text data.
IDOL works with the IDOL server, DiSH server and File System Fetch as
three services installed. The IDOL installer does not support the silent
install option.
Online Help Installs the Teamcenter Help Library files on the local host:
When TEM prompts you for the location of the Teamcenter help files,
enter the path to the Teamcenter documentation distribution image, which
contains the online help files (tchelp.jar).
Note
For information about installing online help using as part of a

Web tier application, see Installing Teamcenter online help.
Sample files Installs sample source code for customizing Teamcenter and generating
reports.
This component is optional. You can install the sample files individually;
you need not install any other components.
Teamcenter Security Services Configures Security Services for Teamcenter. These services eliminate
prompts for logon credentials when users switch Teamcenter products
within a user session.
Prerequisite:
Installation and configuration of Security Services.
For information about Security Services, see the Security Services

Installation/Customization guide.
Required information:
• Application ID for this instance of Teamcenter in the Security

Services application registry.
• Complete URL of the Security Services logon Service Web application.
• Complete URL of the Security Services Identity Service Web

application.

Teamcenter features
Database Daemons Optional database support services.
Action Manager Service Monitors the database for the creation of action objects and dispatches
events that have a specific execution time and events the Subscription
Manager daemon fails to process.
Installing the Action Manager service is required to enable the rich client
Subscription Monitor application.
Subscription Manager Service Monitors the database event queue for the creation of subscription event
objects.
Installing the Subscription Manager service is required to enable the rich

client Subscription Monitor application.
Task Manager Service Checks user inboxes for tasks that have passed due dates, notifies the
delegated recipients, and marks those tasks as late.
Installing the Task Monitor service is required to enable notification

of late tasks.
Tesselation Manager Service Tessellates UGMASTER and UGALTREP datasets to the JT
(DirectModel) dataset and attaches the JT dataset back to the item
revision and UGMASTER and UGALTREP dataset.
Installing the Tessellation service is required to create the tessellated

representations in Repeatable Digital Validation (RDV) that enable users
of the DesignContext application to quickly visualize components in
context. The tessellated representations are created during the workflow
release process, ensuring that JT files of the DirectModel datasets are
updated as the NX files are released.
Teamcenter Shared Metadata Cache Service Installs the Shared Metadata Cache Service.
File Management File management features.
FMS Server Cache Installs the File Management System FSC server and file caches. You
must install an FSC server on each host that runs a server manager and
on each host that is to provide volume services.
You can optionally choose to install the FSC as a configuration server or a

performance cache server.
Hierarchical Storage Management (HSM) Adds support for third-party hierarchical storage management software.
Teamcenter Web Tier Features to support the Teamcenter .NET Web tier.
ASP .NET State Service Installs the middle tier processes that communicate with Teamcenter
server processes.
Web Tier for .NET Installs the middle tier processes that communicate with Teamcenter
server processes.
Extensions Extensions to Teamcenter server and client functionality.
Teamcenter Integration for NX Installs Teamcenter Integration for NX. This feature requires a local
installation of NX and it is supported with the two-tier rich client
architecture only.
For more information, see Install NX and Teamcenter Integration for NX

or NX Integration.
Weld Management Installs the template that manages NX welding features in Teamcenter.
Aerospace and Defense Aerospace and Defense features.

Teamcenter features
Aerospace and Defense Foundation Installs Aerospace and Defense functionality for the Teamcenter server.
This feature requires Teamcenter Foundation and Vendor Management.
For more information about this feature, see the Aerospace and Defense
Solution Guide.
Aerospace and Defense Change Installs the change management functionality for the Aerospace
Management and Defense Foundation feature. This feature requires Teamcenter
Foundation and Aerospace and Defense Foundation.
Solution Guide.
Aerospace and Defense Foundation Training Installs the Aerospace and Defense Foundation training program for
the Aerospace and Defense Foundation feature. This feature requires
Teamcenter Foundation, Vendor Management, and Aerospace and
Defense Foundation.
Solution Guide.
Automotive Teamcenter Automotive Edition and additional supporting features.
Teamcenter Automotive Edition Installs the optional Teamcenter Automotive Edition application.
GM Overlay Installs the Teamcenter Automotive Edition GM Overlay application.
Installing GM Overlay requires that you also install Teamcenter

Automotive Edition.
Configure AutoCAD Integration for GM Configures AutoCAD Integration/AutoCAD Manager to operate in a
Overlay Teamcenter Automotive Edition GM Overlay environment. Choose this
option only when you add GM Overlay to a Teamcenter environment that
includes AutoCAD Integration. If you attempt to include this configuration
before installing GM Overlay and the standard AutoCAD Integration,
the install fails. Both GM Overlay and the base AutoCAD integration
must be installed and functioning before you choose this option. Requires
Teamcenter Foundation and GM Overlay.
GM Customization for DPV Installs GM-specific LOVs and GRM rules for DPV.
Wire Harness Configuration in GM Overlay Configures wire harness configuration for a Teamcenter Automotive
Edition GM Overlay environment. Requires Teamcenter Foundation,
Wire Harness Configuration, Teamcenter Automotive Edition, and GM
Overlay.
GM PAD/TWP Customization Installs additional GM data types for PAD/TWP Customization. This
feature requires Teamcenter Foundation, GM Overlay, Customization for
eM-Server Integration, and PAD/TWP Customization.
BOM Management Features that support Product Master Management.
Product Master Manager Installs Product Master Manager, a rich client application that allows
users to view and manage a complete set of LOUs, LOAs, and parts for
a vehicle program. Users work with items in a work in progress (WIP)
area and optionally add them to a package to allow effective collaboration
with other users.
Note
This feature requires postinstall setup to complete configuration.
For more information about installing Product Master Manager,

see Installing and Upgrading Product Master Management in the
Product Master Management online help collection.

Teamcenter features
CAD BOM Alignment Configures the Teamcenter installation to interact and share visual data
with Product Master Management. Configuring this feature allows designs
managed by this installation of Teamcenter to be related to parts and use
or parts in products that are managed by Product Master Management.
Note
This feature requires postinstall setup to complete configuration.
Behavior Model Management Features that support behavior model management.

Common Framework Features that provide the core behavior modeling functionality.
For more information about these features, see the Behavior Modeling
Tool Integration Guide.
Installs the behavior modeling framework that provides integration to
the behavior modeling tool.
Behavior Modeling Common Client
Tool Integration Guide
Installs the behavior modeling framework that provides integration to the
Teamcenter Behavior Modeling Teamcenter behavior modeling tool.
Framework
This feature requires Teamcenter Foundation or a rich client or a two-tier
Business Modeler IDE client.
MATLAB Integration Features that provide the Teamcenter integration to MATLAB, which
allows you to manage your MATLAB model data in Teamcenter.
Tool Integration Guide.
Installs the MATLAB integration connector that allows you to manage
MATLAB Integration Connector MATLAB models in Teamcenter.
This feature requires the Behavior Modeling Common Client feature.

Installs the Teamcenter MATLAB integration data model.
Teamcenter MATLAB Integration This feature requires the Teamcenter Behavior Modeling Framework
feature and also Teamcenter Foundation or a rich client or a two-tier
Business Modeler IDE client.
Consumer Packaged Goods Features to support Consumer Packaged Goods.
Brand Management Installs the Brand Management template for Consumer Packaged Goods.
For information about installing this feature, see Getting Started with
Consumer Packaged Goods.
CPG Materials Installs Consumer Packaged Goods objects such as raw materials,
formulated materials, and so on.
Finished Product Management Installs the Finished Product Management functionality for Consumer
Packaged Goods.

Teamcenter features
Packaging and Artwork Installs packaging and artwork functionality for Consumer Packaged
Goods.
Specification Manager Installs the Specification Manager feature. For more information about
installing this feature, see the Specification Manager Guide.
Finished Product Management to CPG Provides a bridge between finished products and Consumer Packaged
Materials Bridge Goods materials.
Packaging and Artwork to Finished Product Provides a bridge between Packaging and Artwork and Finished Product
Management Bridge Management for Consumer Packaged Goods.
Content and Document Management Content and document management features.
Acrobat/Reader Plugin Installs the Teamcenter plug-in for Adobe Acrobat and Adobe Acrobat
Reader. This solution is optional.
For information about using the Adobe Acrobat/Reader plug-in, see Getting
Started with Document Management.
Content Management Base Installs the data model for Content Management.
For information about configuring this feature and using Content

Management, see the Content Management Guide.
Content Management DITA Enables management of documentation for the DITA standard in Content
Management.

Content Management S1000D Enables management of documentation for the S1000D standard in
Content Management.

Content Management S1000D 4.0 Enables management of documentation for the S1000D 4.0 standard in
Content Management.

Engineering Process Management Engineering Process Management features.
NX Integration Installs default data types and loads template NX data to support
Teamcenter Integration for NX/NX Integration, the Teamcenter
integration with Siemens PLM Software NX.
NX Manager for Rich Client Installs Teamcenter Integration for NX for the rich client. This feature
requires Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Spatial Search Installs Spatial Search capabilities of the cacheless search engine.
For more information about configuring and using Spatial Search, see the
Getting Started with RDV guide.
This feature requires Dispatcher Server.

Teamcenter features
Bounding box generation from JT Enables generation of bounding box data from JT files, providing
secondary data for the cacheless search engine. For more information
about configuring and using cacheless search, see the Getting Started
with RDV guide.
This feature requires Dispatcher Server. Also, during Teamcenter

installation, you must install the Spatial Search translator
(JtToBboxAndTso).
Trueshape generation from JT Enables generation of Trushape data from JT files, providing secondary
data for the cacheless search engine.
For more information about configuring and using cacheless search, see
the Getting Started with RDV guide.
This feature requires Dispatcher Server. Also, during Teamcenter

installation, you must install the Spatial Search translator
(JtToBboxAndTso).
Bounding box generation from NX Enables generation of bounding box data when saving NX files, providing
secondary data for the cacheless search engine.
QPL for Repeatable Digital Validation Installs and configures QPL files used in conjunction with the rich client
DesignContext application.
For QPL-based DesignContext, installing Repeatable Digital Validation

(RDV) services is required. For Appearance-based DesignContext,
installing RDV services is not required. QPL is not required if you use
cacheless search.
• The path to the location of an installed NX application.
• The type of search engine to use, either an NX-based engine or a

JT-based engine.
• Database configuration for use with Repeatable Digital Validation.
DesignContext is available for both the rich client and thin client.
Enterprise Knowledge Foundation Enterprise Knowledge Foundation features.
Remote Workflow Configures linking between Teamcenter sites for remote workflow
operations.
This option is applicable only when you are deploying the four-tier
architecture.
Prerequisites:
• Remote Workflow components, including Application Registry, must

be separately installed and configured.
• The Web tier application, including the optional Remote Workflow

parameters, must be installed and configured as described in
Installing rich client Web applications.
• Host name and port number of the Java servlet running the
Teamcenter Application Registry.

Teamcenter features
• The host name and port number of the host running a Web tier
application.
• If you are linking to Teamcenter portfolio, program and project

management, the chooser servlet name.
Teamcenter Client for Microsoft Office Installs the Teamcenter Client for Microsoft Office.
For information about installing this feature, see the Installation on

Dispatcher Client for Rich Client Installs Dispatcher Client for the rich client. This feature requires
Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Dispatcher (Translation Management).
Change Management Provides a flexible change management framework that integrates with
other Teamcenter products.
For more information about using Change Management, see the Change
Manager Guide.
Note
If you install this feature, you may need to set the

HiddenPerspectives preference in the rich client.
For more information, see the Preferences and Environment

Contract Data Management Installs Contract Data Management, which allows you to manage, initiate
review processes, and monitor correspondence for procurement documents,
such as design information, drawings, status reports, purchase orders,
and so on.
For more information about Contract Data Management, see the Aerospace
and Defense Solution Guide.
Render Document for Rich Client Provides Render Management capabilities for the rich client. This feature
requires Dispatcher Client for Rich Client.
For more information about configuring and using Render Management

capabilities, see the My Teamcenter Guide.
For information about installing Dispatcher features, see Getting Started

with Dispatcher (Translation Management). For information about
installing and configuring file translators for the Dispatcher Server, see
the Dispatcher Server Translators Reference Guide.
Dispatcher Server Installs the following Dispatcher Server components: scheduler, module
and administration client.
Issue Management Installs Issue Manager, which allows you to track problems, or issues, with
products by managing the review, approval, and implementation of issues.
For more information, see the Issue Manager Guide.

Teamcenter features
Dispatcher Client Installs an integration of the Dispatcher Server and Teamcenter that
enables rich client users to translate Teamcenter data files to various
visualization format for viewing in Teamcenter. This feature requires
Teamcenter Foundation.
Penetration Request Management Installs the penetration request management feature.
This feature requires the Change Management and Issue Management

features and also Teamcenter Foundation or a rich client.
Lifecycle Visualization Features to support Lifecycle Visualization.
Teamcenter Visualization (Embedded) for Installs the embedded viewer for the rich client. This feature requires
Rich Client Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Teamcenter Visualization (Stand-alone) for Installs stand-alone application viewer for the rich client. This feature
Rich Client requires Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Localization Features that support localization of Teamcenter.
Classification L10N Installs the classification localization template, which enables localization
in the Classification environment.
For more information, see the Localization Guide.
Note
The classification localization template is not supported with

IBM DB2 databases.
Maintenance Repair and Overhaul Teamcenter maintenance, repair, and overhaul features.
As-Built Management Installs the As-Built template for Teamcenter maintenance, repair, and
overhaul.
For information about installing, configuring, and using this feature, see
the As-Built Manager Guide.
As-Maintained Management Installs the As-Maintained feature to support the As-Maintained physical
structure management
Service Planning Installs the Service Planner application that supports service planning
capabilities within Teamcenter. Service Planner requires a separate
license and is installed as an optional overlay to standard Teamcenter.
For information about using Service Planner, see the Service Planner
Guide.
As-Built and As-Maintained Alignment Enables interoperability of data created by the As-Built Management and
As-Maintained Management features.

Teamcenter features
Service Event Management Installs Service Event Management to support service process
management for Teamcenter maintenance, repair, and overhaul.
For more information about using Service Manager, see the Service
Manager Guide.
Service Planning and Service Processing Enables interoperability of data created by the As-Built Management and
Alignment As-Maintained Management features.
Service Request Processing Installs the Service Planning and Service Processing Alignment module to
support using discrepancies in Service Planner.
For more information about using Service Planner, see the Service
Manager Guide.
Service Scheduler Installs Service Scheduler, which supports scheduling within Teamcenter.
Service Scheduler lets companies define, schedule, and implement services
for their products. Service Scheduler is a separately licensed application
that is installed as an optional overlay on top of standard Teamcenter
and Service Manager.
For more information about using Service Scheduler, see the Service
Scheduler Guide.
Manufacturing Process Management Teamcenter manufacturing process management features.
Configure Resource Browser and NC Installs libraries for the Resource Browser and NC Package Browser
Package Browser applications.
MTM Data Card Installs the Methods Time Measurement (MTM) data card system.
For more information, see Getting Started with Manufacturing.

Customization for Process Simulate Installs additional data types for Process Simulate Integration
Integration Customization.
Customization for eM-Server Integration Installs additional data types for Tecnomatix server integration
customization.
Work Instructions Installs the work instructions feature.
For information about using work instructions, see the Resource Manager
Guide.
Database Configuration for DPV Installs the database configuration for DPV. This feature requires
Teamcenter Foundation, GM Overlay, and Customization for eM-Server
Integration.
eBOP reports Customization Installs additional data types for eBOP Reports Customization. This
feature requires Teamcenter Foundation and Customization for
eM-Server Integration.
PAD/TWP Customization Installs additional data types for PAD/TWP Customization. This feature
requires Teamcenter Foundation, GM Overlay, and Customization for
eM-Server Integration.
Install Libraries for AI SOA Client Installs sample source code and executables that assist in developing an
Application Interface (AI) service client.
For more information about the AI service, see the Services Guide.
Mechatronics Process Management Features to support Mechatronics Process Management.

Teamcenter features
Installs the client for Teamcenter EDA, the application that integrates
EDA Standalone Client
ECAD applications with Teamcenter.
ECAD Part Library for Rich Client Enables ECAD part library menus in the rich client.
EDA for Business Modeler IDE Integrates Teamcenter EDA with the Business Modeler IDE.
EDA Server and Rich Client Support Installs the dataset types and transfer modes required to support
Teamcenter EDA, the application that integrates ECAD applications with
Teamcenter.
For complete information about installing Teamcenter EDA, see Getting

Started with Electronic (EDA) Lifecycle Management.
EMPS - Foundation Installs electronic design and manufacturing types to support ECAD
translation and PCB design collaboration using Teamcenter embedded
viewer.
ESM Base Installs ESS base types and updates preferences. Without these, ESS
operations do not work from any interface (rich client, thin client, custom
utilities, and other clients).
SCM ClearCase for Foundation Installs ClearCase types and sets Teamcenter preferences to enable
the integration between Teamcenter and the IBM ClearCase software
configuration management (SCM) tool.
For more information about installation, see the Teamcenter ClearCase

Integration Guide.
Wire Harness Configuration Installs Teamcenter schema support for wire harnesses.
Calibration and Configuration Data Installs the Calibration and Configuration Data Management
Management (CCDM) feature, which allows you to manage the calibration and
configuration-related parameter data of embedded systems. CCDM allows
you to define, create, view, update, and delete parameter data, and to
group related parameter definitions together and associate parameter
values to a project.
For more information about the CCDM solution, see the Embedded
Software Solutions Guide.
ECAD Part Library Management Installs ECAD part types to support ECAD part library management.
This feature requires Teamcenter Foundation, Vendor Management, and
EDA Server Support.
ESM Processor Installs ESS processor types and updates preferences. Without these, ESS
ESM Software Installs ESS software types and updates preferences. Without these, ESS
Embedded Software Design Data Installs Embedded Software Design Data Management. For more
Management information about this feature, see the Embedded Software Solutions
Guide.
EMPS - ECAD Translation Installs EMPS – ECAD translation, which allows conversion of a PCB
design into the XFATF format. ECAD translation support 36 different
CAD formats. This feature requires EMPS - Foundation and Dispatcher
Server.
ECAD Design Management ECAD design management features for Teamcenter EDA.
Mentor Board Station Support Installs support for using Mentor Graphics Board Station software with
the EDA client. Separate installation of Mentor Graphics Board Station is
required. This feature requires EDA Standalone Client.

Teamcenter features
Mentor PADS Support Installs support for the using Mentor Graphics PADS product line (PADS
Layout and PADS Logic) with the EDA client, enabling you to manage
data that PADS programs create. This feature requires EDA Standalone
Client. You must also install Mentor PADS software.
Cadence Allegro Support Installs support for using Cadence Allegro software with the EDA client.
Separate installation of Cadence Allegro Design Entry is required. This
feature requires EDA Standalone Client.
ECAD Library Management ECAD library management features for Teamcenter EDA.
Gateway for EDA Library Installs the gateway for EDA library, which allows you to integrate ECAD
part metadata databases into Teamcenter. This feature requires EDA
Standalone Client.
Mentor Board Station Library Support Installs support for using Mentor Graphics Board Station library with the
EDA client. Separate installation of Mentor Graphics Board Station is
required. This feature requires EDA Standalone Client.
Mentor Expedition Library Support Installs support for using Mentor Expedition Library with the EDA client.
Separate installation of Mentor Expedition is required. This feature
requires EDA Standalone Client.
Cadence Allegro Library Support Installs support for using Cadence Allegro library with the EDA client.
Separate installation of Cadence Allegro Design Entry is required. This
Mentor PADS Library Support Installs support for the using Mentor Graphics PADS library with the
EDA client. Separate installation of Mentor PADS is required. This
Platform Extensability Platform extensability features.
Global Services Global Services features.
Global Services Framework Creates Global Services Framework.
Global Services Preferences Installs Global Services Preferences.
Multisite Collaboration IDSM Service Installs the distributed services manager (IDSM) required to replicate
data between multiple Teamcenter sites, enabling the exchange of data
objects with other Teamcenter databases over a wide area network (WAN).
Multisite Collaboration ODS Service Installs the object directory service (ODS) required to replicate data
between multiple Teamcenter sites, enabling the exchange of data objects
with other Teamcenter databases over a wide area network (WAN).
Global Services Monitoring GUI for Installs a rich client and configures it for use with the Global Services
Rich Client Monitoring GUI for Rich Client feature. This feature requires Teamcenter
Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Mapping Designer Installs the Mapping Designer client. Mapping Designer is dependent on
third-party external eclipse plug-ins from Altova MapForce. The Altova
Mapforce eclipse plug-ins are dependent on the MapForce client. Requires
MapForce Professional client and MapForce eclipse plug-ins. Download
these plug-ins from Altova at the following URL:
http://www.altova.com/download_archive.html
A valid license for the MapForce client is required to run Mapping

Designer.
This feature requires the Business Modeler IDE Client feature.

Catia Non BOM Installs the CATIA Non BOM feature.

Teamcenter features
ERP Connect Installs the ERP Connect Toolkit interface that integrates Teamcenter
with other Enterprise Resource Planning (ERP)-supported applications,
such as BAAN.
Portfolio, Program and Project Management Portfolio, Program and Project Management features.
Workflow to Scheduling Integration Allows workflow to send updates to the related tasks in a schedule.
This feature requires a four-tier installation and Dispatcher to be
installed/configured. This feature requires Teamcenter Foundation.
Note
This feature also requires the Schedule Manager translator

(SchMgrTrans). For information about installing and
configuring this translator, see the Dispatcher Server Translators
Reference Guide.
Reporting and Analytics Features to support Teamcenter reporting and analytics.

Teamcenter for Reporting and Analytics Installs the Teamcenter reporting and analytics (TcRA) integration. TcRA
is a standalone reporting application that introduces a new folder in Report
Builder called TcRA Reports, which contains reports created with TcRA.
Dashboard Installs the Teamcenter reporting and analytics dashboard interface.
For more information about installing this feature, see Installing

Teamcenter reporting and analytics.
Supplier Relationship Management Supplier Relationship Management features.
Installs the Supplier Relationship Management integration.
SRM Integration
For more information about this feature, see the Data Exchange Guide.
Vendor Management Installs the optional Vendor Management solution.
Systems Engineering and Requirements Features that support Systems Engineering and Requirements
Management Management.
Teamcenter Extensions for Microsoft Office Installs Teamcenter Extensions for Microsoft Office.
For information about installing this feature, see the Installation on

Requirements Management Installs the Requirements Management functionality for Systems
Engineering and Requirements Management.
For information about using Requirements Management, see Getting

Started with Systems Engineering.
Systems Engineering Installs the Systems Engineering application, which provides capabilities
such as functional modeling and budgets.
This feature requires the Teamcenter Foundation feature and also a rich
client or a two-tier Business Modeler IDE client.
For information using Systems Engineering, see Getting Started with

Systems Engineering.
Rich client solutions

You can add rich client solutions to a rich client distribution instance. These solutions
add functionality to the four-tier rich client installed using the Over-the-Web

Installer. For information about creating a rich client distribution instance, see
Install a rich client distribution instance.
Over-the-Web Installer Installs the program that installs the rich client over
the Web. This solution is required.
Microsoft Visual C++ Installs the Microsoft Visual C++ libraries required
2005/2008 Redistributables for the rich client and for the FMS client cache (FCC).
Teamcenter client Installs Teamcenter client communication system
communication system (TCCS).
TCCS contains the FMS client cache (FCC), which
uploads files from a Teamcenter client workstation to
a Teamcenter volume and also downloads requested
files from the volume to a client workstation. An
FCC provides the following advantages:
• Improved file transfer performance
• File streaming
Installing an FCC supports the Lifecycle

Visualization file streaming technology, which
downloads portions of JT files over the network as
they are needed and improves network performance.
Office Client for Microsoft Installs Teamcenter Client for Microsoft Office,
Office which provides the capability to manage Teamcenter
workspace objects in real time. Client for Office
provides access to Teamcenter objects directly
through Microsoft Office Word, Excel, PowerPoint,
and Outlook in Microsoft Office 2007 or 2010.
This solution adds a custom Teamcenter ribbon to
Microsoft Office applications.
For information about features and use of Client for
Office, see the Client for Microsoft Office Guide.
Standalone EDA Client Installs the client for Teamcenter EDA, the
application that integrates ECAD applications with
Teamcenter.
Add-ons for Standalone Installs the dataset types and transfer modes
EDA Client required to support Teamcenter EDA, the application
that integrates ECAD applications with Teamcenter.
For more information about installing Teamcenter
EDA, see Getting Started with Electronic (EDA)
Lifecycle Management.
Rich Client 4-Tier Installs the rich client software required for the
four-tier architecture. This solution is required.

ADS Foundation for Rich Installs Aerospace and Defense functionality for the
Client 4-Tier rich client.
For more information about Aerospace and Defense,
see the Aerospace and Defense Solution Guide.
As-Built Manager Adds As-Built functionality for the four-tier rich
client. As-Built is part of Teamcenter maintenance,
repair, and overhaul.
For information about installing, configuring, and
using this solution, see the As-Built Manager Guide.
As-Maintained Installs Service Event Management to support
Management for Service service process management for As-Maintained
Manager functionality of Teamcenter maintenance, repair,
and overhaul.
For information about installing, configuring, and
using this feature, see the As-Built Manager Guide.
CAD-BOM Alignment Installs CAD-BOM alignment, which allows
(CBAExt) for Rich Client Teamcenter to interact and share visual data with
4-Tier Product Master Management.
CPG Materials for Rich Installs CPG Materials support for Consumer
Client 4-Tier Packaged Goods.
For information about installing this solution, see
Getting Started with Consumer Packaged Goods.
Calibration and Installs Calibration and Configuration Data
Configuration Data Management (CCDM), which allows rich client users
Management (CCDM) to manage the calibration and configuration-related
for Rich Client 4-Tier parameter data of embedded systems. CCDM allows
you to define, create, view, update, and delete
parameter data, and to group related parameter
definitions together and associate parameter values
to a project.
For more information about the CCDM solution, see
the Embedded Software Solutions Guide.
Content Management Base Installs Content Management and enables
+S1000D for Rich Client management of documentation for the S1000D
4-Tier standard.
Content Management is the application used to
manage technical documentation using SGML and
XML information stored in a Teamcenter database.
For information about configuring this feature
and using Content Management, see the Content
Management Guide.

Contract Management for Installs Contract Data Management, which allows
Rich Client 4-Tier you to manage, initiate review processes, and
monitor correspondence for procurement documents,
such as design information, drawings, status reports,
purchase orders, and so on. This solution is optional.
For more information about Contract Data
Management, see the Aerospace and Defense Solution
Guide.
Dashboard Installs the Reporting and Analytics Dashboard
interface.
For more information about installing this feature,
see Installing Teamcenter reporting and analytics.
Dispatcher Client for Rich Installs Dispatcher Client for the rich client.
Client
For information about using this feature, see Getting
Started with Dispatcher (Translation Management).
EDA for Rich Client 4-Tier Configures the rich client to use Teamcenter EDA, the
(Configuration Only) application that integrates ECAD applications with
Teamcenter. Separate installation of the stand-alone
EDA client (using Teamcenter Environment
Manager) is required. This solution is optional.
ESDDM for Rich Client Installs Embedded Software Solutions Design Data
4-Tier Management support for the rich client.
For more information about this feature, see the
Embedded Software Solutions Guide.
Embedded Software Installs Embedded Software Solutions support for
Manager for Rich Client the rich client.
4-Tier
Embedded Software Solutions Guide.
GDIS for Rich Client 4-Tier Installs the Global Dimensional Information System
plug-in for Dimensional Planning and Validation
(DPV). This solution is optional.
For more information about this feature, see
the Dimensional Planning and Validation
GM Overlay for Rich Client Installs the Teamcenter Automotive Edition–GM
4-Tier Overlay application. This solution is optional.
GS Monitoring GUI for Rich Configures the rich client for use with the Global
Client 4-Tier Services Monitoring GUI for Rich Client feature.
MTM Data Card for Rich Installs the Methods Time Measurement (MTM)
Client data card system. This solution is optional.
For more information, see Getting Started with
Manufacturing.

NX Manager for Rich Client Configures the rich client to use Teamcenter
4-Tier Integration for NX or NX Integration, the application
that integrates Teamcenter with NX. Separate
installation of the Teamcenter Integration for NX or
NX Integration executables is required (as part of
NX installation). This solution is optional.
Product Master Installs Product Master Manager, a rich client
Management (PMM) for application that allows users to view and manage
Rich Client 4-Tier a complete set of LOUs, LOAs, and parts for a
vehicle program. Users work with items in a work in
progress (WIP) area and optionally add them to a
package to allow effective collaboration with other
users.
Note
This feature requires postinstall setup to
complete configuration.
For more information about installing Product
Master Management, see Installing and
Upgrading Product Master Management in
the Product Master Management online help
collection.
Requirements Installs Requirements Management functionality
Management for Systems Engineering and Requirements
Management.
For information about using Requirements
Management, see Getting Started with Systems
Engineering.
SCM ClearCase for Rich Installs the integration between Teamcenter and the
Client 4-Tier IBM ClearCase software configuration management
(SCM) tool and configures the rich client for its
use. Separate installation of ClearCase software is
required. This solution is optional.
SRM Integration for Rich Installs the Supplier Relationship Management
Client 4-Tier integration.
For more information about this solution, see the
Data Exchange Guide.
Service Planning Installs the Service Planner application that
supports service planning capabilities within
Teamcenter. Service Planner requires a separate
license and is installed as an optional overlay to
standard Teamcenter.
For information about using Service Planner, see the
Service Planner Guide.

Specification Manager for Installs Specification Manager functionality for the
Rich Client 4-Tier rich client.
Specification Manager Guide.
Systems Engineering Installs the Systems Engineering application, which
provides capabilities such as functional modeling
and budgets.
This feature requires the rich client.
For information using Systems Engineering, see
Getting Started with Systems Engineering.
Teamcenter Applications Installs Teamcenter Extensions for Microsoft Office
for Microsoft Office and the Teamcenter Plugin for Microsoft Project,
which allows Microsoft Project users to exchange
data directly with Schedule Manager. Separate
installation of Microsoft Office is required.
For information about installing these features on
a rich client host, see the Installation on Windows
Clients Guide.
Teamcenter Plugin for Installs the Teamcenter Plugin for Microsoft Project
Microsoft Project allows Microsoft Project users to exchange data
directly with Schedule Manager.
For information about using the Teamcenter Plugin
for Microsoft Project, see the Schedule Manager
Guide.
Teamcenter Visualization 9 Configures the rich client to use the embedded viewer
(Embedded) for Rich Client when Teamcenter lifecycle visualization is separately
4-Tier (Configuration Only) installed on the client workstation. This solution is
optional.
Teamcenter Visualization Installs the embedded viewer and configures the rich
9 (Embedded) for Rich client. This solution is optional.
Client 4-Tier (Install and
Configuration)
Teamcenter Visualization Configures the Teamcenter lifecycle visualization
9 (Stand-alone) for Rich application (the stand-alone application viewer).
Client 4-Tier Separate installation of Teamcenter lifecycle
visualization is required. This solution is optional.
Vendor Management for Installs Vendor Management support for the rich
Rich Client 4-Tier client.

Render Document for Rich Provides Render Management capabilities for the
Client rich client. This feature requires Dispatcher Client
for Rich Client.
For more information about installing and
configuring Render Management capabilities, see
Installing Render Management.
For information about installing Dispatcher features,
see Getting Started with Dispatcher (Translation
Management).
Rich Client 4-Tier Lite Installs the lite edition of the four-tier rich client.
Edition This solution is optional.
Service Processing Installs the Service Processing Extensions for the
Extensions for Service rich client. This functionality is available only if you
Manager have purchased and have a license for Service Event
Management.
For more information about using Service Manager,
see the Service Manager Guide.
As-Built and As-Maintained Installs the operability functionality between
Alignment for Service the As-Built Management and As-Maintained
Manager Management applications. This functionality is
available only if you have purchased and have a
license for As-Built Management and As-Maintained
Management.
Service Event Management Installs the Service Event Management functionality
Extensions for Service for the rich client. This functionality is available only
Manager if you have purchased and have a license for Service
Event Management.
Service Request Manager Installs service request processing for Teamcenter
maintenance, repair, and overhaul.
Service Scheduling Installs Service Scheduler, which supports scheduling
within Teamcenter. Service Scheduler lets companies
define, schedule, and implement services for their
products. Service Scheduler is a separately licensed
application that is installed as an optional overlay on
top of standard Teamcenter and Service Manager.
For more information about using Service Scheduler,
see the Service Scheduler Guide.

Appendix
D Web tier context parameters

Appendix
D Web tier context parameters
The following tables describe Web tier context parameters provided by Teamcenter
Web tier solutions.
Web tier required parameters

General parameters
DEPLOYABLE-FILE-NAME Name of the deployable file you are creating for the
Web tier application. The name is configurable; Web
Application Manager adds the file extension.
TcEngEncoding Teamcenter character encoding set for localization.
This value must match the encoding specified for the
Teamcenter server.
For example, if the Teamcenter server is running
using ISO8859_1 encoding, specify ISO8859_1 also
for this parameter.
TcEngLocale Locale of the Teamcenter server for localization of
Web tier messages. This locale must match the locale
of the Teamcenter server.
For example, if Teamcenter server is running in the
Russian locale, specify ru_RU for this parameter.
PLM00013 H Installation on Windows Servers Guide D-1

Appendix D Web tier context parameters

TreeCache parameters
TreeCache Cluster Name Name of a cluster of components accessing a shared
global server pool.
You must supply the same name as specified for
the server manager (installed using Teamcenter
Environment Manager).
TreeCache Mode Communication protocol mode between TreeCache
peers, either TCP or multicast.
You must supply the same mode as specified for
TreeCache Cluster Port Required only when the TreeCache communication
mode is Mcast.
Port used for multicast communication between the
application server and the server manager.
You must supply the same port number as specified
for the server manager (installed using Teamcenter
When configuring multiple environments, use a
different port number for each environment.
Local Service Port Required only when the TreeCache communication
mode is TCP.
Specifies the TCP port at which this TreeCache
cluster member provides the TreeCache service.
If you install the Web tier application on the same
host as the server manager, the local service port for
the Web tier application must be different from the
local service port for the server manager.
TreeCache Peers Required only when the TreeCache communication
mode is TCP.
Specifies a list of addresses (host name and
port number pairs) to ping for peer members of
the TreeCache cluster in TCP communication
mode. It is a comma-separated list of the form
host1[port1],host2[port2],.. Do not use the form
host1:port1, ... because the colon character (:) is
not permitted.
For each host/port pair, this cluster member pings
the port you specify.
D-2 Installation on Windows Servers Guide PLM00013 H

Web tier context parameters

In addition, the TreeCache may find more than one

peer based on a single host/port pair (for example, if
multiple peers on a single host have the same local
service port value).
Once established, peers exchange data regarding
available server pools. This cluster member pings
each host/port pair in the list. To be found, a peer
must have a matching service port. (See Local
Service Port in this table.)
• As a minimum, specify the service port for all
Java 2 Enterprise Edition (J2EE) application
server hosts and server manager hosts you want
this Teamcenter server to communicate with.
• For each host, you can include more than one

host/port pair in the list.
It is not necessary to include all members of the
cluster in this list. For example, you may include
only a subset of the server managers and none of
the application servers. In this case, the cluster
connects only when one or more of the designated
managers is running. This technique reduces
pinging and thereby improves performance.
For small configurations, all members should
be included in the peers list. For larger
configurations, it is recommended that the
number of pinged ports be limited to no more
than six. All members should ping at least the
same subset of primary server managers so that
TreeCaches connect and data is shared.
Connection Timeout Required only when the TreeCache communication
mode is TCP.
Maximum time in milliseconds that a TreeCache
cluster member waits for peer responses to TCP
pings.
The larger the value you specify, the more slowly
the first server manager starts.
Typically, you supply this same value for the

Connection Timeout parameter specified for


MAX_POOL_SIZE Specifies the maximum number of concurrent
connections to Teamcenter servers allowed by the
application server. If you do not specify a value,
the Web tier application uses the application server
default value.
Note
This parameter applies to WebLogic, JBoss,
and Oracle Application Server. For other
application servers, the maximum pool size
must be set using the application server
console.
For information, see the Web Application
Deployment Guide.
Enterprise Application Registration ID used to register the application’s EJB and
ID J2C Connector. If you want to deploy multiple
Teamcenter Web tier applications in a single
application server instance, each application must
be assigned a unique ID.
LogVolumeName Name of the log volume.
LogVolumeLocation Log volume location, the root directory under which
log files are created. The default location logs
represent a child folder beneath the default root
directory of the target application server instance.
This location varies depending on the application
server vendor.
Note
If the path you enter contains backslash
characters (\) as path delimiters, use double
backslash characters (\\) to represent single
backslash characters.


Security Services parameters
IS_SSO_ENABLED Specifies whether Security Services is enabled for
this instance of Teamcenter.
SSO_APPLICATION_ID Application ID assigned to this instance of
Teamcenter in the Security Services application
registry. This information is required only when you
are configuring the optional Security Services.
This ID is determined when Security Services is
installed and configured. For information, see
the Security Services Installation/Customization
manual.
SSO_logon_SERVICE_URL Complete URL of the Security Services logon Service
Web application. This information is required only
when you configure the optional Security Services.
This URL is determined when Security Services
is installed and configured. For information, see
manual.
SSO_SERVICE_URL Complete URL of the Security Services Identity
Service Web application. This information is
required only when you configure the optional
Security Services.
This URL is determined when Security Services
is installed and configured. For information, see
manual.
Web tier optional parameters

General parameters
webmaster E-mail address of the administrator to whom
questions and comments about this application are
addressed.


staticResourceClientCache Maximum time in seconds that a client can use a
ExpiryTime locally cached static content (for example, images or
Javascript) before requesting a fresh copy from the
server.
Setting this value too low causes the client to
unnecessarily request content. Setting this value too
high risks stale content. Typical values range from
several hours to one day.
Setting the value to 0 is valid and causes the client to
always ask for static content.
The default value is 28800 seconds (8 hours).
compressResponse Specifies whether a response to the client can be
compressed if the requesting client supports it.
Compressing the response typically yields faster
response time to the client but requires additional
processing in the Web container.
Set this parameter value based on trial and error for
your instance of the server, bandwidth, and client
access environment.
The default value is true.
cacheCompressedStatic Specifies whether responses for static resources are
ResourceOnServer cached on the server. This parameter is used only
when the compressResponse parameter is set to
true.
If the value is set to true, compressed responses for
static resources are cached on the server, memory
permitting.
If the value is set to false, the compression occurs each
time the client requests a static resource.
The default value is true.
responseCompression Threshold in bytes beyond which the server should
Threshold compress responses sent back to the client.
Typically compressing smaller responses does not
yield much compression - so all responses equal to
or smaller than this value will be sent to the client
uncompressed.
Setting the value to 0 is valid and causes the server to
compress every response sent to the client (assuming
other parameters permit compression).


The default value is 500 bytes. Change this value only

if absolutely required.
calculateResponseTime Specifies whether the group of response time filters
are on (by setting to true) or off (by setting to false).
These filters are used for instrumentation purposes
(for example, the average time spent in processing a
request from a rich client or thin client).
The response time filters should remain turned off
unless you are collecting statistics.
The default value is false.
TreeCache Parameters1
PROCESS_MAX_PER_ Maximum number of server processes per user. The
USER default value (0) turns off the constraint, that is,
specifies that there is no limit on the number of
processes per user.
QUERY_TIMEOUT Maximum time in seconds per request. The default
value (0) turns off the constraint, that is, specifies that
there is no time limit on the request.
SOFT_TIMEOUT_EDIT Time-out for edit mode servers in a busy pool.
SOFT_TIMEOUT_READ Time-out for read mode servers in a busy pool.
SOFT_TIMEOUT_ Time-out for stateless servers in a busy pool.
STATELESS
HARD_TIMEOUT_EDIT Load insensitive time-out for edit mode servers.
HARD_TIMEOUT_READ Load insensitive time-out for read mode servers.
HARD_TIMEOUT_ Load insensitive time-out for stateless servers.
STATELESS
Application Interface Web Service parameters
AIWS_teamcenter_linking_ Name for user for logging on to Teamcenter on behalf
user_name of a remote Teamcenter application.
The default value is infodba.
AIWS_teamcenter_linking_ Password for user for logging on to Teamcenter on
user_passwd behalf of remote Teamcenter application.
Legacy URL support parameters
The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jboss.org/jgroups.


requestRedirectedTo Specifies the protocol and server, port, or domain for
accessing the thin client. The default value is the
server, port, or domain in the requested, original URL.
Use this parameter to change the protocol and server,
port, or domain information from the requested,
original URL. For example, you could use this
parameter to change a requested http://acme:8080
URL to http://web.acme.com. A typical use for this
parameter is in a cluster configuration.
replacementFor CGIBIN_IMAN Specifies the replacement for cgi-bin/iman in the
URL. Do not change the default value of tc/webclient
(this value is currently the only supported value).
redirectionWaitTime Specifies an integer representing the number of
seconds to display the URL message to users before
redirecting their requests to the new URL. The default
value is 10 seconds. The minimum value is 0.
Global Services context parameters

Enterprise application parameters
ApplicationInstance Specifies the name uniquely identifying the
application instance within the application server.
SSOAppID Specifies the unique value used to identify the Global
Services application to the Security Services single
sign-on (SSO) server.
LogFileLocation Specifies the name and location of the logging
configuration file. By default, this is the log4j.xml
file. If you are using the standard Global Services
logging configuration, do not change parameter
value. If you are going to customize the logging
configuration, you must create the custom file and
provide the complete path, including the file name,
as the parameter value.
TcGSBOSJNDI Specifies the Global Services business object server
(BOS) connector EJB JNDI name. The default value
is typically used.
TcGSDORJNDI Specifies the data object repository connector EJB
JNDI name. This connector is used to manage data
in the Global Services datastore. The default value
is typically used.


TcGSJDBCJNDI Specifies the JDBC connector EJB JNDI name.
This connector can be used to manage data in the
Global Services datastore or to connect any JDBC
compatible database. The default value is typically
used.
TcGSMessageServerJNDI Specifies the Global Services message server EJB
JNDI name. The default value is typically used.
TcGSNotifierReactorJNDI Specifies the Global Services notifier reactor EJB
JNDI name. The default value is typically used.
globalservices.webservices.url Specifies the URL of the Global Services Web
services WAR file within the Global Services Ode
BPEL enterprise application, for example:
globalservices.webservices.url =
http://localhost:8080/tcgs-ws
This is used by services that must send HTTP SOAP

requests to other web services.
globalservices.ode.url Specifies the URL to the Global Services Ode BPEL
enterprise application, for example:
globalservices.ode.url =
http://localhost:8080/tcgs-ode
This is used by services that must send HTTP SOAP

requests to BPEL processes.
Security proxy parameters
(This solution is optional.)
global.services.proxy.service.URL Specifies the base URL for the secured enterprise
application (Global Services). For example:
http://host:port/TcGS
host and port are the application server host and the
port number used to connect to the Global Services
application, and TcGS is the context-root for the
application.
global.services.proxy.user Specifies the Global Services user the proxy client
uses to execute calls to the server.
global.services.proxy.password Specifies the password associated with the Global
Services proxy user.


global.services.proxy.client.IPs Provides a comma-separated list of authorized client
IP addresses or host names. The IP addresses can
contain digit-matching wildcards as follows:
? matches any single digit
* matches zero or more digits
For example:
192.168.0.*
matches all IP addresses from 192.168.0.0 through

192.168.0.255 and:
192.168.0.??
matches the addresses from 192.168.0.0 through

192.168.0.99.
The wildcards match digits only. Therefore, an
expression like 192.168.*.* is valid. However, an
expression like 192.168.* is not.
Also, because the * character matches zero or more
digits, the expression 192.168.1.2* matches the
following addresses:
192.168.1.2
192.168.1.20 through 192.168.1.29
192.168.1.200 through 192.168.1.255
Connector parameters
(The connector solutions are optional.)
RAC.OSGi.plugin.URL.suffix Specifies the suffix to the Global Services URL
used to call the connector OSGi plug-in through
the Jetty plug-in. The default value is typically
used. If you change the value, you must update
RAC_OSGi_PLUGIN_URL parameter in the
TeamcenterRACOSGiConfig.xml file.
TcGSConnectorJNDI Specifies the Global Services connector EJB JNDI
name. This connector provides a connection to other
instances of Global Services.
TcGSRACJNDI Specifies the Teamcenter rich client connector EJB
JNDI name.
TcGSSOAJNDI Specifies the Teamcenter services-oriented
architecture (SOA) connector EJB JNDI name.
TeamcenterConnectorJNDI Specifies the Teamcenter 2005 connector EJB JNDI
name.
TcGSEngJNDI Specifies the Engineering Process Management
connector EJB JNDI name.


TcGSEntJNDI Specifies the Teamcenter Enterprise connector EJB
JNDI name.
TcGSOMfgJNDI Specifies the Oracle Manufacturing connector EJB
JNDI name.
TcGSSAPJNDI Specifies the SAP connector EJB JNDI name.

Appendix
E Glossary

Appendix
E Glossary
architecture
Set of decisions, patterns, and principles for a product suite. The architecture
provides a framework for application development within that product suite and is
independent of specific functions.
assigned FSC
FMS server cache assigned as the volume or cache server for an FMS client cache.
Each FMS client cache requires an assigned FSC to provide it with access to files. An
assigned FSC is typically the FSC nearest to the client host. In small deployments,
an assigned FSC can also serve as the parent FSC.
build platform
Platform required to build a customization. Compare with certified platform and
supported platform.
certified platform
Platform the base product is certified to operate on. Compare with supported
platform.
client tier
Teamcenter architectural tier that comprises the Teamcenter clients, Teamcenter
integrations with third-party applications, and the third-party applications
associated with the integrations.
connector
See Global Services connector.
connector to Teamcenter
Enterprise JavaBean that connects Global Services with Teamcenter. The optional
connector to Teamcenter is provided as a part of the Global Services connectors and
supports both two-tier and four-tier deployment configurations.
connector to Teamcenter Enterprise

Enterprise JavaBean that connects Global Services with Teamcenter Enterprise.
The optional connector to Teamcenter Enterprise is provided as a part of the Global
Services connectors.
PLM00013 H Installation on Windows Servers Guide E-1

Appendix E Glossary
corporate server
Host computer at the center of a Teamcenter network. This host contains the
Teamcenter application root directory, Teamcenter data directory, licensing, File
Management System (FMS), and volumes. For installations that include the Web
tier (four-tier architecture), the corporate server also contains the Teamcenter server
manager. Multiple application clients can map to or mount the corporate server.
distribution server
See rich client distribution server.
distribution server instance

See rich client distribution server instance.
eM-Planner interface
Interface between Teamcenter manufacturing process management and Tecnomatix
eM-Planner that allows data exchange.
enterprise tier
Teamcenter architectural tier that comprises a configurable pool of Teamcenter
C++ server processes and a server manager. Larger sites can distribute the pool of
server processes across multiple hosts. Smaller sites can run the pool of servers on
the same host as the Web tier.
environment variables script

Teamcenter script (tc_profilevars) that sets variables for the Teamcenter
environment. This script sets all Teamcenter environment variables except
TC_ROOT and TC_DATA.
ERP Connect Toolkit

Teamcenter toolkit that can be configured to create an interface between Teamcenter
and ERP systems.
ERP Connect to SAP

Teamcenter integration that allows the controlled, auditable transfer of product
information from Teamcenter to SAP.
facility
Physical location in an enterprise (for example, manufacturing plant or design
center). One facility can comprise multiple sites. Compare with site.
FCC
See FMS client cache (FCC).
FCC configuration file

File that configures an individual FMS client cache (fcc.xml). The FCC configuration
file defines such values as the parent FMS server cache location and the location and
size of the client caches. Values defined in the FCC configuration file can override
default values defined in the FSC configuration file.
E-2 Installation on Windows Servers Guide PLM00013 H

Glossary
File Management System (FMS)

System that manages uploading and downloading file data between clients and
volumes in both two-tier and four-tier architecture deployments. FMS provides
volume servers for file management, a shared server-level performance cache for
shared data access between multiple users, a client-based private user cache for rich
clients, and a transient datastore mechanism for transporting reports, PLM XML,
and other non-volume data between the enterprise and client tiers. FMS file caching
enables placing the data close to the user, while maintaining a central file volume
and database store.
FMS
See File Management System (FMS).
FMS client cache (FCC)

FMS process that runs on a client host, uploading files to an FMS server cache
process, requesting files from an FMS server cache process, and caching files on
the client host. The FCC process manages two caches of whole files: a write cache
containing files uploaded to a Teamcenter volume and a read cache containing files
downloaded from a Teamcenter volume. It also manages one segment file cache for
Teamcenter lifecycle visualization. Each Teamcenter rich client host requires a
local FMS client cache.
FMS master configuration file

File that configures FMS (fmsmaster.xml). The FMS master configuration file
describes the FMS network and defines groups of server caches. It can also define
default values for server caches and client caches, such as maximum sizes. Values
defined in the server cache configuration file and in the client cache configuration file
can override the default values defined in the master configuration file.
FMS master host

Host that contains the FMS master configuration file (fmsmaster.xml). This file is
optionally mounted at each FSC server.
FMS server cache (FSC)

FMS process that runs on a server host and performs as a volume server (when
running on a host where a volume is located or directly mounted) or a cache server
(when running on a host where a volume is not located or directly mounted) and a
configuration server. As a volume or cache server, the FSC checks all file access
requests for a ticket that Teamcenter generates to authorize file access. As a cache
server, it manages two segment file caches, one for downloading files and one for
uploading files. As a configuration server, it provides FMS configuration information
to file client caches and other FSCs. As a transient server, it delivers PLM XML and
other transient files to clients. A minimum of one FSC must be deployed in any
Teamcenter installation. Multiple FSCs can be deployed, with each FSC performing
one designated purpose as either a volume, a cache, or a configuration server.
four-tier architecture
Teamcenter architecture that includes four tiers: resource tier, client tier, Web tier,
and enterprise tier.
four-tier deployment
Deployment of the Teamcenter four-tier architecture. The Web tier, enterprise tier,
resource tier, and client tier can each be hosted on the same or separate computers.

Appendix E Glossary
FSC
See FMS server cache (FSC).
FSC configuration file

File that configures an individual FMS server cache (fsc.xml). The FSC
configuration file defines such values as the address of the master FSC, the
maximum sizes of the segment file caches, and the upload timeout value. It can also
define default values for FCCs and other FSCs.
FSC group
Group of server caches defined in the FMS master configuration file.
Global Services connector

Global Services component that accesses information from a data source. Each
connector accesses information from a particular type of data source. For example,
Global Services provides a connector for communicating with JDBC-compliant
databases. Global Services offers optional connectors.
One implementation of a connector can communicate with multiple data sources by
using different connector configuration files.
Global Services connectors are Enterprise JavaBeans. Enterprise customizers can
create connectors to data sources using the Global Services connector APIs.
Global Services Foundation

Web application that enables your enterprise to access information stored in
virtually any type of electronic data source that manages your enterprise data.
Running on a standard commercial Web application server, the server components
of Global Services Foundation enable communication among the data sources and
between users and the data sources. All components of Global Services Foundation
use standard Web technology: Extensible Markup Language (XML), Extensible
Stylesheet Language (XSL), and the Sun Java programming language. Users access
Global Services Foundation from a commercial Web browser using the standard
technologies of Web browsers, primarily support for HyperText Markup Language
(HTML) forms and small Java applets.
group preference
Teamcenter preference applying to an entire group.
heterogeneous network environment

Teamcenter network environment in which the database server, corporate server,
and Teamcenter clients are provided by multiple vendors and can be a mixture
of UNIX and Microsoft Windows nodes.
Compare with homogeneous network environment.
homogeneous network environment

Teamcenter network environment in which the database server, corporate server,
and all Teamcenter clients are provided by one vendor (for example, all Sun
Microsystems or all Dell systems).
Compare with heterogeneous network environment.

Glossary
I-deas
Siemens PLM Software’s integrated CAD/CAM/CAE solution that is used to design,
analyze, test, and manufacture products.
IDSM server
Integrated Distributed Services Manager, a network node that runs a daemon process
to handle the transfer of data objects among sites in a Multi-Site Collaboration
network. One IDSM server node must be designated for each Teamcenter database
from which objects are published; each server node can act for one database only.
JT cache
Data Integration Services Adapter cache of JT files managed by the JT cache service
and accessible to Teamcenter lifecycle visualization users. See also world access
cache and limited access cache.
JT cache populator
Stand-alone Data Integration Services Adapter utility that prepopulates the JT
cache with JT part and assembly files.
Lifecycle Visualization
Siemens PLM Software suite that provides enterprise-wide product visualization
capabilities. Lifecycle Visualization can be configured for use with both the
Teamcenter rich client and thin client as a stand-alone application.
The software suite includes Teamcenter lifecycle visualization base, Teamcenter
lifecycle visualization standard, Teamcenter lifecycle visualization professional, and
Teamcenter lifecycle visualization mockup.
limited access cache

Data Integration Services Adapter cache of JT files that are accessible only to
privileged users. The limited access cache is managed by the JT cache service.
Permission checks are performed when a user accesses a file from the limited access
cache. Compare with world access cache.
local server
Set of processes required to serve a single rich client installed on the same host
computer as the rich client. Teamcenter Integration for NX/NX Integration
configuration requires a local server.
manifest file
File that records and maintains information about the rich client image files,
including a list of the files and a version for each file. The Over-the-Web Installer
consults the manifest file to determine which files to download.

Appendix E Glossary
master FSC
FMS server cache that reads the master configuration file directly from the FMS
master host. An FSC is configured either to read the master configuration file
directly from the master host or to download it from another FSC with access to it.
Mentor Graphics Integration

Teamcenter integration that allows users to store and manage Mentor Graphics
Design Manager objects in Teamcenter.
Multi-Site Collaboration
Teamcenter capability that allows the exchange of data objects among several
Teamcenter databases. Transfer of objects among databases is controlled by daemon
processes running on designated servers. Objects are replicated by exporting them
from their original database and importing them into the requesting database.
Configuration of Multi-Site Collaboration is optional.
Multi-Site Collaboration network

Network of independent Teamcenter sites that are within the same enterprise and
share data using Multi-Site Collaboration.
My Teamcenter
Teamcenter rich client application that is the main access point for managing
product information. My Teamcenter provides the functionality for creating objects
in the Teamcenter database, querying the database for objects, checking in and
checking out objects, and managing tasks. Users can also open objects, automatically
launching the related application.
Each user has a personal My Teamcenter window that displays product information
as graphical objects. Although users share product information across the enterprise,
they organize this information individually in personal workspaces.
naming service
Service that maintains a list of names and the objects associated with them. For
the Teamcenter rich client, the naming service maintains a list of servers and the
objects and methods used by those services. The naming service is an integral part
of the server directory.
NS
See naming service.
NX Integration
Integration between Teamcenter and NX. NX Integration users have full access
to the Teamcenter user interface from NX, and they can also access NX from the
Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter
functionality available. Teamcenter Integration for NX excludes certain Teamcenter
functionality, such as workflow and product structure editing.

Glossary
object chooser
Displays objects appropriate for linking with another Teamcenter product. In
determining the objects to display, the object chooser considers the security rights of
the person accessing the Teamcenter product. See also remote workflow.
object directory services server

Multi-Site Collaboration network node that runs a daemon process to handle
publication of data objects within a Multi-Site Collaboration environment. One
ODS server node must be designated for each object directory services site and each
server node can act only for one object directory services site.
object directory services site

Site with the database that maintains a record of each object in a Multi-Site
Collaboration network. At least one Teamcenter database on a Multi-Site
Collaboration network must be designated as an ODS site. This site is used to store
publication records for the data objects.
object launcher
Launches another Teamcenter product from a linked object. Each Teamcenter
product has an object launcher. See also remote workflow.
ODBC driver
Teamcenter integration that allows ODBC-compliant applications such as Actuate
Report Writer, Crystal Reports, Microsoft Excel, and Access to extract data from a
Teamcenter database for building reports.
ODS server
See object directory services server.
ODS site
See object directory services site.
Oracle home
Directory in which Oracle software is installed on the Oracle server node.
Oracle server
Single installation of Oracle able to service queries from several Teamcenter
workstations. The ORACLE_SERVER environment variable defines this Oracle
service node. For large-scale installations, the Oracle server is typically a dedicated
high performance workstation that is optimized specifically for running Oracle
software.
Oracle system identifier (SID)

Alphanumeric word used to identify a collection of processes and associated memory
structures as belonging to a particular Oracle database instance. The ORACLE_SID
environment variable defines the Teamcenter-Oracle system identifier.
Over-the-Web Installer
Installation program that downloads the rich client software from a distribution
server instance to the user’s workstation over the Web.

Appendix E Glossary
persistent object manager (POM)

Interface between Teamcenter objects and the Relational Database Management
System (RDBMS). The persistent object manager provides definition of classes
by inheritance from other classes and definition of attributes, manipulation of
in-memory objects and support for their saving and retrieval to and from the
underlying RDBMS, support for applications accessing the same data concurrently,
protection against the deletion of data used by more than one application, and
support for the access control lists attributed to objects.
POM
See persistent object manager (POM).
preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many
aspects of a session, such as user logon names and the columns displayed by default
in a properties table.
published object
Object available to other sites in a Multi-Site Collaboration network. Publishing an
object creates a record in the ODS site database that can be read and searched by
other sites. Until an object is published, it can be seen only by the owning site.
QPL
See quick part locator.
QPL server
Quick part locator server. It provides a qpl daemon that can be used with
DesignContext in the rich client. The qpl daemon coexists with all Teamcenter
daemons. Without this daemon DesignContext does not work.
quick part locator

Component of Repeatable Digital Validation (RDV) that creates and queries tables in
a Teamcenter database. The quick part locator enables rapid lookup of components
in an assembly. The tables cache precomputed results of location, attributes, and
spatial relationship of all components in a product assembly. The quick part locator
provides one of the search engines used by DesignContext.
RDV
See Repeatable Digital Validation.
remote workflow
Teamcenter component that enables users to create links between Teamcenter
objects and objects in other Teamcenter products, such as Teamcenter portfolio,
program and project management. Users can then launch the linked Teamcenter
product from within either the rich client or the thin client.

Glossary
Repeatable Digital Validation

Combination of software and processes that enables on-demand digital mockups for
use throughout the product development lifecycle. Repeatable Digital Validation
services are required for using QPL-based DesignContext.
resource tier
Teamcenter architectural tier comprising the database server, database, file servers,
and volumes.
rich client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server.
rich client distribution server

Software that manages the connection between distribution server instances, the
Web server, and the user’s workstation when a rich client is deployed over the Web.
The Over-the-Web Installer contacts the distribution server for the rich client files
to download to the user’s workstation.
rich client distribution server instance

Rich client software to be installed on user’s workstations over the Web.
Administrators create one instance for each server.
role preference
Teamcenter preference applying to an entire role.
Security Services
Services that eliminate prompts for logon credentials when users switch Teamcenter
products within a user session. Authentication is performed by an external identity
service provider, such as lightweight directory access protocol (LDAP), instead of
the Teamcenter product. At a site that deploys multiple Teamcenter products and
Security Services, users log on once to access all participating Teamcenter products.
server manager
Process that manages a pool of Teamcenter server processes in a deployment of
the four-tier architecture. The server manager starts and times out a configurable
number of server processes to communicate with the Teamcenter database. A
server assigner process assigns available server processes to user sessions. The
server manager communicates with the Web tier application using either TCP or
multicast protocol.
server pool
Pool of Teamcenter server processes running in the enterprise tier. A small
deployment may have only one pool of server processes. For larger deployments, the
pool of server processes is distributed as subpools across multiple hosts, with a
server manager for each subpool. Server pools are applicable for deployments of the
Teamcenter four-tier architecture only.
site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
networking capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site.

Appendix E Glossary
site ID
Unique identifier of a Teamcenter site. The site ID is used to generate internal
identifiers for Teamcenter objects that must be unique throughout an enterprise.
Once established, site IDs should not be modified.
site name
Unique name of a Teamcenter site stored in the database as a user-defined character
string.
site preference
Teamcenter preference that applies to the entire site.
Solid Edge Manager

Teamcenter integration that enables users to use Teamcenter to manage files from
within Solid Edge.
STEP Translator
Teamcenter application that enables users to import product information into a
Teamcenter database and to export Teamcenter data via STEP-compliant physical
files.
supported platform
Platform configuration supported by GTAC.
system administrator
Teamcenter user who is a member of the system administration group.
Teamcenter Application Registry

Independent Web-based service that allows a Teamcenter product to look up other
available Teamcenter products for launching a linked object. Administrators can
register and unregister installed instances of a Teamcenter product in the registry.
Teamcenter application root directory

Directory location of the Teamcenter shared binary executables. The TC_ROOT
environment variable defines this location. Generally, the contents of this directory
change only with a new version of Teamcenter.
Teamcenter data directory

Directory location of the Teamcenter shared data subdirectories and files. The
TC_DATA environment variable defines this location. Each data directory is
associated with a single database instance.
Teamcenter Engineering Visualization

Optional Teamcenter rich client component that provides enterprise-wide product
visualization capabilities and is embedded in the rich client interface. Four
Teamcenter Engineering Visualization products provide different visualization
capabilities. Teamcenter Engineering Visualization Base provides basic 2D and 3D
viewing. Teamcenter Engineering Visualization Standard, Teamcenter Engineering
Visualization Base, and Teamcenter Engineering Professional provide increasing
functionality.

Glossary
Teamcenter Environment Manager (TEM)

Tool with a wizard-style interface that installs Teamcenter servers and two-tier and
four-tier rich clients. TEM also performs maintenance operations, such as upgrading
servers, applying maintenance packs, and installing patches. Teamcenter installers
launch TEM using the tem.bat command (on Windows systems) or the tem.sh
command (on UNIX or Linux systems).
Teamcenter file structure

File structure of an installed Teamcenter node; it separates homogeneously shared
binary executables from heterogeneously shared data.
Teamcenter Integration for NX

NX-based entry-level set of Teamcenter data management functions, such as
vaulting, checking in, checking out, revision management, attribute synchronization,
and searching CAD data. Teamcenter Integration for NX manages NX files and
their data without exposing the user to full Teamcenter functionality. Teamcenter
Integration for NX users have only limited access to the Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter
functionality available. Teamcenter Integration for NX excludes certain Teamcenter
functionality, such as workflow and product structure editing.
Teamcenter Integration for NX I-deas

Product that integrates Teamcenter and I-deas to provide a single data management
environment for users. Teamcenter Integration for NX I-deas users author their
data in I-deas and manage the data in Teamcenter. Teamcenter Integration for NX
I-deas includes the My Teamcenter user interface and the I-deas Data Services (IDS)
and Team Data Sharing (TDS) modules. See also I-deas.
Teamcenter Integration for NX I-deas host

Teamcenter host that functions as the gateway through which the Migration Wizard
initiates communications with the TDS server for data migration processing.
Teamcenter manufacturing process management

Teamcenter manufacturing process design and management system. Teamcenter
manufacturing process management comprises several user applications, for
example, Plant Designer, Manufacturing Process Planner, Part Planner, Report
Generator, and Resource Manager.
TEM
See Teamcenter Environment Manager (TEM).
tessellation
Process that translates a CAD file to a visualization file.
thin client
Teamcenter user interface that provides a streamlined browser-based view of
product information stored in a Teamcenter database. The thin client is configured
in the Web tier, which creates and serves its Web pages to the client.
transient volume
Operating system directory controlled by Teamcenter and used to store temporary
data for transport of reports, PLM XML, and other nonvolume data between the Web
tier and client tier in a deployment of the Teamcenter four-tier architecture.

Appendix E Glossary
two-tier architecture
Teamcenter architecture that includes a resource tier and a client tier. The resource
tier comprises the database server and database. The client tier comprises the
Teamcenter rich client, third-party applications that integrate with the rich client,
and a local server. This architecture supports only the Teamcenter rich client.
two-tier deployment
Deployment of the Teamcenter two-tier architecture. In a typical deployment of the
two-tier architecture, the rich client and its local server are installed on a user’s
workstation as are third-party applications that integrate with the rich client. The
database server and the Teamcenter corporate server are installed on one or more
separate computers.
user preference
Teamcenter preference applying to a specific user.
visualization
Ability to display a realistic, real time, graphical visualization of geometric data.
volume
Operating system directory controlled by Teamcenter and used to store the files
managed by Teamcenter. When a user performs an action that causes Teamcenter
to create a file, the file is created in the Teamcenter volume. Users cannot directly
access the files in Teamcenter volumes; they must do so via a Teamcenter session.

Graphical installation utility that generates supporting Web files (WAR and EAR
format) for a named Web application. Web Application Manager also installs the rich
client distribution server and creates distribution server instances.
Web tier
Teamcenter architectural tier that comprises a Java application running in a Java
2 Enterprise Edition (J2EE) application server. The Web tier is responsible for
communication between the client tier and enterprise tier.
world
All users regardless of group or role.
world access cache

Data Integration Services Adapter cache of JT files that are accessible to all users.
The world access cache is managed by the JT cache service. No permission checks
are performed when a user accesses a file from the world access cache. Compare
with limited access cache.

Glossary
XML object list

Data Integration Services Adapter file that is formatted in XML and provides a list
of the parts and assemblies to be populated into the JT cache.

Index
A B
Action manager . . . . . . . . . . . . . . . . . . 8-1 Backup
Action Manager Service . . . . . . . . . . . . C-4 Oracle databases . . . . . . . . . . . . . . . . 4-2
Adding features . . . . . . . . . . . . . . . . . 19-2 Base Install
additional_applications directory . . . . . B-2 Features . . . . . . . . . . . . . . . . . . . . . C-2
advanced_installations directory . . . . . B-2 Behavior Modeling Common Client . . . . C-6
Aerospace and Defense Best installation practices . . . . . . . . . . . 6-4
Aerospace and Defense Change Bounding box generation from JT . . . . . C-8
Management . . . . . . . . . . . . . . . . C-5 Bounding box generation from NX . . . . C-8
Aerospace and Defense Foundation . . C-5 Brand Management . . . . . . . . . . . . . . C-6
Aerospace and Defense Foundation Business Modeler IDE
Training . . . . . . . . . . . . . . . . . . . C-5 Client . . . . . . . . . . . . . . . . . . . . . . . C-1
Rich client . . . . . . . . . . . . . . . . . . . . C-16 Installing . . . . . . . . . . . . . . . . . . . . 12-1
AI SOA client . . . . . . . . . . . . . . . . . . . C-11 Mapping Designer . . . . . . . . . . . . . . C-13
AIX platforms Solution . . . . . . . . . . . . . . . . . . . . . C-1
Platform support . . . . . . . . . . . . . . . . 1-1 Business Modeler IDE 2-tier . . . . . . . . C-2
System requirements . . . . . . . . . . . . . 1-1 Business Modeler IDE 4-tier . . . . . . . . C-2
Apache HTTP Server . . . . . . . . . . . . . 10-37 Business Modeler IDE Standalone . . . . C-2
Apache Tomcat . . . . . . . . . . . . . . . . . 10-37
Apple Macintosh platforms C
Platform support . . . . . . . . . . . . . . . . 1-1
System requirements . . . . . . . . . . . . . 1-1 CAD BOM Alignment . . . . . . . . . . . . . C-6
Application server hangs after publishing an CAD Part Library for Rich Client . . . . . C-12
item . . . . . . . . . . . . . . . . . . . . . . . . . A-11 Cadence Allegro Library Support . . . . . C-1,
Application server stops responding . . . A-11 C-13
Application servers Cadence Allegro Support . . . . . . . C-1, C-13
HTTPServerTable . . . . . . . . 10-24, 10-30 Calibration and Configuration Data
Teamcenter application server . . . . . 2-20 Management . . . . . . . . . . . . . . . . . . . C-12
Web tier . . . . . . . . . . . . . . . . . . . . . 1-12 Cannot assign requested address . . . . . A-11
ApplicationInstance . . . . . . . . . . . . . 10-13 Catia Non BOM . . . . . . . . . . . . . . . . . C-13
ApplicationInstance context cc_integration directory . . . . . . . . . . . . B-2
parameter . . . . . . . . . . . . . . . . . . . . . D-8 Certification database . . . . . . . . . . . 1-1, 3-1
As-Built and As-Maintained Change Management . . . . . . . . . . . . . C-9
Alignment . . . . . . . . . . . . . . . . . . . . . C-10 Chinese characters in Windows . . 1-3, A-13
As-Built Management . . . . . . . . . . . . . C-10 CIFS volume data access . . . . . . . . . . . 2-20
As-Maintained Management . . . . . . . . C-10 Classification L10N . . . . . . . . . . . . . . . C-10
ASP .NET State Service . . . . . . . . . . . . C-4 ClearCase . . . . . . . . . . . . . . . . . . . . . C-12
AutoCAD integration, GM Overlay . . . . C-5 Client tier
Automatic logon, four-tier . . . . . . . . . . . 2-6 Four-tier . . . . . . . . . . . . . . . . . . . . . 1-12
Automotive Edition . . . . . . . . . . . . . . . C-5 Two-tier . . . . . . . . . . . . . . . . . . . . . 1-10
Autonomy Client, Business Modeler IDE 2-tier . . . C-2
IDOL server . . . . . . . . . . . . . . . . . . C-3 Client, Business Modeler IDE 4-tier . . . C-2
Autonomy Intelligent Data Operating Layer Client, Business Modeler IDE
(IDOL) . . . . . . . . . . . . . . . . . . . . . . . C-3 Standalone . . . . . . . . . . . . . . . . . . . . C-2
PLM00013 H Installation on Windows Servers Guide Index-1

Index
Clients SSOAppID . . . . . . . . . . . . . . 10-13, D-8

FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-13 TcGSBOSJNDI . . . . . . . . . . . 10-13, D-8
Four-tier clients . . . . . . . . . . . . . . . . 1-12 TcGSConnectorJNDI . . . . . . . . . . . D-10
Rich client installation . . . . . . . . . . . . 2-8 TcGSDORJNDI . . . . . . . . . . . 10-13, D-8
Thin client . . . . . . . . . . . . . . . . . . . . 2-11 TcGSEngJNDI . . . . . . . . . . . . . . . . D-10
Two-tier clients . . . . . . . . . . . . . . . . 1-10 TcGSEntJNDI . . . . . . . . . . . . . . . . D-11
COMM_FAILURE error . . . . . . . . . . . . A-11 TcGSJDBCJNDI . . . . . . . . . . 10-13, D-9
Commands TcGSMessageServerJNDI . . . . 10-13, D-9
CREATE DB . . . . . . . . . . . . . . . . . . . 3-6 TcGSNotifierReactorJNDI . . . 10-13, D-9
create_database . . . . . . . . . . . . . . 3-7–3-8 TcGSOMfgJNDI . . . . . . . . . . . . . . D-11
dasdrop . . . . . . . . . . . . . . . . . . . . . . 23-3 TcGSRACJNDI . . . . . . . . . . . . . . . D-10
db2admin . . . . . . . . . . . . . . . . . . . . 23-2 TcGSSAPJNDI . . . . . . . . . . . . . . . D-11
db2idrop . . . . . . . . . . . . . . . . . . . . . 23-3 TcGSSOAJNDI . . . . . . . . . . . . . . . D-10
db2licm . . . . . . . . . . . . . . . . . . . . . . . 3-4 TeamcenterConnectorJNDI . . . . . . . D-10
db2set . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Contract Data Management . . . . . . . . . C-9
db2stop . . . . . . . . . . . . . . . . . . . . . . 23-5 CookiePath parameter . . . . . . . . . . . . . A-12
db2swtch . . . . . . . . . . . . . . . . . . . . . 23-2 CORBA error in Web tier . . . . . . . . . . . A-11
insweb . . . . . . . . . . . . . . . . . . . . . . 10-2 CORP item creation fails . . . . . . . . . . . A-4
insweb.bat . . . . . . . . . . . . 22-4, 22-6–22-7 Corporate server
Configuration Features . . . . . . . . . . . . . . . . . . . . . C-1
Databases . . . . . . . . . . . . . . . . . . . . . 4-8 Installing . . . . . . . . . . . . . . . . . . . . . 7-5
Heterogeneous environment . . . . . . . . 8-4 Corrupted database, recovery . . . . . . . . A-18
Multi-Site Collaboration . . . . . . . . . . . 8-2 CPG Materials . . . . . . . . . . . . . . . . . . C-6
Oracle Net . . . . . . . . . . . . . . . . . . . . . 4-5 Customer-specific patches . . . . . . . . . . 22-6
Teamcenter manufacturing process Customization for eM-Server
management . . . . . . . . . . . . . . . . 14-1 Integration . . . . . . . . . . . . . . . . . . . . C-11
Configure Resource Browser and NC Package Customization for Process Simulate
Browser . . . . . . . . . . . . . . . . . . . . . . C-11 Integration . . . . . . . . . . . . . . . . . . . . C-11
Connecting . . . . . . . . . . . . . . . . . . . . . . 3-6 customScripts.log file . . . . . . . . . . . . . . 4-10
Connectivity
Sample database . . . . . . . . . . . . . . . . 3-6 D
Connector support files . . . . . . . . . . . . 10-6
Consumer Packaged Goods dasdrop command . . . . . . . . . . . . . . . . 23-3
Brand Management . . . . . . . . . . . . . C-6 Dashboard . . . . . . . . . . . . . . . . . . . . . C-14
CPG Materials . . . . . . . . . . . . . . . . . C-6 Database administration server
Packaging and Artwork . . . . . . . . . . C-7 (DAS) . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Content and Document Management . . C-7 Database Configuration Assistant . . . 2-18,
Content Management . . . . . . . . . . . . . C-7 4-8
Content Management Base feature . . C-7 Database Configuration for DPV . . . . . C-11
Content Management DITA feature . . C-7 Database daemons
Content Management S1000D 4.0 Installation . . . . . . . . . . . . . . . . . . . C-4
feature . . . . . . . . . . . . . . . . . . . . C-7 Starting . . . . . . . . . . . . . . . . . . . . . . 8-1
Content Management S1000D Database Daemons . . . . . . . . . . . . . . . C-4
feature . . . . . . . . . . . . . . . . . . . . C-7 Action Manager Service . . . . . . . . . . C-4
Content Management DITA . . . . . . . . . C-7 Subscription Manager Service . . . . . . C-4
Content Management S1000D . . . . . . . C-7 Task Manager Service . . . . . . . . . . . C-4
Content Management S1000D 4.0 . . . . . C-7 Teamcenter Shared Metadata Cache
Context parameters Service . . . . . . . . . . . . . . . . . . . . C-4
ApplicationInstance . . . . . . . . 10-13, D-8 Tesselation Manager Service . . . . . . . C-4
global.services.proxy.password . . . . . D-9 Database services . . . . . . . . . . . . . . . . C-4
global.services.proxy.client.IPs . . . . D-10 Databases
global.services.proxy.user . . . . . . . . . D-9 Adding data directory to
LogFileLocation . . . . . . . . . . . 10-13, D-8 installation . . . . . . . . . . . . . . . . . 19-3
RAC.OSGi.plugin.URL.suffix . . . . . D-10 Adding database to installation . . . . . 19-4
Index-2 Installation on Windows Servers Guide PLM00013 H

Index
Creation Distribution server instance

SQL script . . . . . . . . . . . . . . . . . 5-2 Installation . . . . . . . . . . . . . 10-19, 10-28
Data imports . . . . . . . . . . . . . . . . . . . 4-4 Web deployment . . . . . . . . . . . . . . 10-35
Multiple database access Documentation distribution image . . . . B-1
Four-tier rich clients . . . . . . . . . 19-5 Download URL, IBM DB2 . . . . . . . . 3-1–3-2
Overview . . . . . . . . . . . . . . . . . 19-5 DPV
RDV . . . . . . . . . . . . . . . . . . . . . . . . 2-18 GM Customization . . . . . . . . . . . . . . C-5
Recovering from a corrupted ds_manifest.mf file . . . . . . . . . . . . . . 10-31
database . . . . . . . . . . . . . . . . . . . A-18
Sample . . . . . . . . . . . . . . . . . . . . . . . 3-5 E
Shutting down . . . . . . . . . . . . . . . . . . 4-2
Site planning . . . . . . . . . . . . . . . . . . 2-18 eBOP reports Customization . . . . . . . . C-11
Teamcenter . . . . . . . . . . . . . . . . . 3-6–3-8 ECAD design management
Templates . . . . . . . . . . . . . . . . . 2-18, 4-8 Cadence Allegro Support . . . . . . . . . C-13
Unpopulating in IBM DB2 . . . . . . . . A-18 Mentor Board Station Support . . . . . C-12
Unpopulating in Microsoft SQL Mentor PADS Support . . . . . . . . . . . C-13
Server . . . . . . . . . . . . . . . . . . . . A-18 ECAD library management
Unpopulating in Oracle . . . . . . . . . . A-18 Cadence Allegro Library Support . . . . C-13
DB2, see IBM DB2 Gateway for EDA Library . . . . . . . . . C-13
DB2 support . . . . . . . . . . . . . . . . . . . . . 1-2 Mentor Board Station Library
db2admin account . . . . . . . . . . . . . . . . . 3-2 Support . . . . . . . . . . . . . . . . . . . C-13
db2admin command . . . . . . . . . . . . . . 23-2 Mentor PADS Library Support . . . . . C-13
db2admns group . . . . . . . . . . . . . . . . . . 3-2 Mentor Support . . . . . . . . . . . . . . . . C-13
db2ese.lic file . . . . . . . . . . . . . . . . . . . . 3-4 ECAD Part Library Management . . . . . C-12
db2idrop command . . . . . . . . . . . . . . . 23-3 EDA
db2licm command . . . . . . . . . . . . . . . . . 3-4 Dataset types . . . . . . . . . . . . . . . . . C-12
db2set command . . . . . . . . . . . . . . . . . . 3-4 Server . . . . . . . . . . . . . . . . . . . . . . . 15-1
db2stop command . . . . . . . . . . . . . . . . 23-5 Server support . . . . . . . . . . . . . . . . . C-12
db2swtch command . . . . . . . . . . . . . . . 23-2 Standalone client . . . . . . . . . . . . . . . C-1
db2users group . . . . . . . . . . . . . . . . . . . 3-2 .eda files . . . . . . . . . . . . . . . . . . . . . . . 15-1
dbscripts directory . . . . . . . . . . . . . . . . 4-8 EDA for Business Modeler IDE . . . . . . C-12
Destination directories . . . . . . . . . . . . . 6-2 EDA Server Support . . . . . . . . . . . . . . C-12
Directories EDA Server Support feature . . . . . . . . 15-1
WEB_ROOT . . . . . . . . . . . . . . . . . . 10-2 EDA Stand-alone Client . . . . . . . . . . . C-12
Web_tier . . . . . . . . . . . . . 10-2–10-3, 10-9 EDAComp type . . . . . . . . . . . . . . . . . . 15-2
Dispatcher . . . . . . . . . . . . . . . . . . . . . C-1 EDASchem type . . . . . . . . . . . . . . . . . 15-2
Dispatcher Client . . . . . . . . . . . . . . . C-10 Embedded Software Solutions
Dispatcher Client for Rich Client . . . . C-9 Embedded Software Design Data
Dispatcher Server . . . . . . . . . . . . . . C-9 Management . . . . . . . . . . . . . . . . C-12
Dispatcher Client for Rich Client . . . . . C-9 Embedded viewer . . . . . . . . . . . . . . . . C-10
Dispatcher installation . . . . . . . . . . . . 15-2 Embedded visualization for rich
Dispatcher Server . . . . . . . . . . . . . . . . C-9 client . . . . . . . . . . . . . . . . . . . . . . . . C-10
Installation . . . . . . . . . . . . . . . . . . . C-1 EMPS – ECAD Translation . . . . . . . . . C-12
Installing . . . . . . . . . . . . . . . . . . . . 15-1 EMPS - Foundation . . . . . . . . . . . . . . . C-12
dist_server.jar file . . . . . . . . . . 10-39–10-40 Enterprise Knowledge Foundation
Distributed services manager, see IDSM features . . . . . . . . . . . . . . . . . . . . . . C-8
server and IDSM proxy server Enterprise tier . . . . . . . . . . . . . . . . . . 1-12
Distribution media . . . . . . . . . . . . . . . B-1 Environment variables
Distribution server TC_DATA . . . . . . . . . . 2-2, 7-9, 19-3–19-4
Adding Web components . . . . . . . . . 10-40 TC_ROOT . . . . . . . . . . . . . . 2-2, 6-3, 7-7
Changing contents . . . . . . . . . . . . . 10-40 TCP_NODELAY . . . . . . . . . . . . . . . . 6-2
Installation . . . . . . . . . . . . . . . . . . 10-19 UGS_LICENSE_SERVER . . . . . . . . . 6-2
Starting . . . . . . . . . . . . . . . . . . . . 10-38 ERP Connect Toolkit . . . . . . . . . . . . . . C-14
Stopping . . . . . . . . . . . . . . . . . . . . 10-39 Error log files . . . . . . . . . . . . . . . . . . . . 4-9

Index
Error logs . . . . . . . . . . . . . . . . . . . . . . A-1 Catia Non BOM . . . . . . . . . . . . . . . . C-13

Error messages . . . . . . . . . . . . . . . . . . A-2 Change Management . . . . . . . . . . . . C-9
Errors Classification L10N . . . . . . . . . . . . . C-10
COMM_FAILURE . . . . . . . . . . . . . . A-11 Configure AutoCAD Integration for GM
IPv6 . . . . . . . . . . . . . . . . . . . . . . . . A-11 Overlay . . . . . . . . . . . . . . . . . . . C-5
Java . . . . . . . . . . . . . . . . . . . . . . . . A-10 Configure Resource Browser and NC
java.net.BindException . . . . . . . . . . . A-11 Package Browser . . . . . . . . . . . . . C-11
mcast . . . . . . . . . . . . . . . . . . . . . . . A-11 Content and Document
Pool ID not available . . . . . . . . . . . . A-6 Management . . . . . . . . . . . . . . . . C-7
Restarting server manager . . . . . . . . A-9 Content Management Base . . . . . . . . C-7
Server manager . . . . . . . . . . . . . . . . A-10 Content Management DITA . . . . . . . C-7
SERVER_HOST parameter . . . . . . . A-6 Content Management S1000D . . . . . . C-7
TreeCache . . . . . . . . . . . . . . . . . . . . A-8 Content Management S1000D 4.0 . . . C-7
ESS Base . . . . . . . . . . . . . . . . . . . . . . C-12 Contract Data Management . . . . . . . C-9
ESS Processor . . . . . . . . . . . . . . . . . . . C-12 Corporate server . . . . . . . . . . . . . . . C-1
ESS Software . . . . . . . . . . . . . . . . . . . C-12 CPG Materials . . . . . . . . . . . . . . . . . C-6
Export Customization for eM-Server
Oracle databases . . . . . . . . . . . . . . . . 4-2 Integration . . . . . . . . . . . . . . . . . C-11
Customization for Process Simulate
F Integration . . . . . . . . . . . . . . . . . C-11
Dashboard . . . . . . . . . . . . . . . . . . . . C-14
Failed to start new thread error . . . . . . A-13 Database Configuration for DPV . . . . C-11
FAT partitions . . . . . . . . . . . . . . . . . . . 6-3 Database Daemons . . . . . . . . . . . . . C-4
FCC . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Action Manager Service . . . . . . . C-4
FCC for rich client . . . . . . . . . . . . . . . . C-15 Subscription Manager Service . . . C-4
Features Task Manager Service . . . . . . . . C-4
Aerospace and Defense Change Teamcenter Shared Metadata Cache
Management . . . . . . . . . . . . . . . . C-5 Service . . . . . . . . . . . . . . . . . C-4
Aerospace and Defense Foundation . . C-5 Tesselation Manager Service . . . . C-4
Aerospace and Defense Foundation Dispatcher . . . . . . . . . . . . . . . . . . . C-9
Training . . . . . . . . . . . . . . . . . . . C-5 Dispatcher Client . . . . . . . . . . . 15-1, C-10
As-Built and As-Maintained Dispatcher Client for Rich Client . . . . C-9
Alignment . . . . . . . . . . . . . . . . . C-10 Dispatcher Server . . . . . . . . . . 15-1, C-1
As-Built Management . . . . . . . . . . . C-10 eBOP reports Customization . . . . . . . C-11
As-Maintained Management . . . . . . . C-10 ECAD Design Management . . . . . . . C-12
ASP .NET State Service . . . . . . . . . . C-4 ECAD Library Management . . . . . . . C-13
Automotive . . . . . . . . . . . . . . . . . . . C-5 ECAD Part Library Management . . . C-12
Base Install . . . . . . . . . . . . . . . . . . . C-2 EDA for Business Modeler IDE . . . . . C-12
Behavior Modeling Common Client . . C-6 EDA Server and Rich Client
Bounding box generation from JT . . . C-8 Support . . . . . . . . . . . . . . . . . . . C-12
Bounding box generation from NX . . . C-8 EDA Server Support . . . . . . . . . . . . 15-1
Brand Management . . . . . . . . . . . . . C-6 EDA Stand-alone Client . . . . . . . . . . C-12
Business Modeler IDE . . . . . . . . . . . C-1 EDA Standalone Client . . . . . . . . . . C-1
Business Modeler IDE 2-tier . . . . . . . C-2 Embedded Software Design Data
Business Modeler IDE 4-tier . . . . . . . C-2 Management . . . . . . . . . . . . . . . . C-12
Business Modeler IDE Standalone . . . C-2 EMPS – ECAD Translation . . . . . . . . C-12
CAD BOM Alignment . . . . . . . . . . . . C-6 EMPS - Foundation . . . . . . . . . . . . . C-12
CAD Part Library for Rich Client . . . C-12 Enterprise Knowledge Foundation . . . C-8
Cadence Allegro Library Support . . . . C-1, ERP Connect . . . . . . . . . . . . . . . . . . C-14
C-13 ESS Base . . . . . . . . . . . . . . . . . . . . C-12
Cadence Allegro Support . . . . . C-1, C-13 ESS Processor . . . . . . . . . . . . . . . . . C-12
Cadence Translation Support . . . . . . 15-1 ESS Software . . . . . . . . . . . . . . . . . C-12
Calibration and Configuration Data Extensions . . . . . . . . . . . . . . . . . . . C-4
Management . . . . . . . . . . . . . . . . C-12 Extensions for Office . . . . . . . . . . . . C-14

Index
File Management . . . . . . . . . . . . . . . C-4 Packaging and Artwork . . . . . . . . . . C-7

Finished Product Management . . . . . C-6 Packaging and Artwork to Finished Product
Finished Product Management to CPG Management Bridge . . . . . . . . . . C-7
Materials Bridge . . . . . . . . . . . . . C-7 PAD/TWP Customization . . . . . . . . . C-11
FMS Server Cache . . . . . . . . . . . C-1, C-4 Penetration Request Management . . . C-10
Full Text Search Engine . . . . . . . . . . C-3 Platform Extensability . . . . . . . . . . . C-13
Gateway for EDA Library . . . . . C-1, C-13 Product Master Manager . . . . . . . . . C-5
Global Services . . . . . . . . . . . . C-1, C-13 QPL for Repeatable Digital
Global Services Framework . . . C-1, C-13 Validation . . . . . . . . . . . . . . . . . . C-8
Global Services Monitoring GUI for Rich Remote Workflow . . . . . . . . . . . . . . . C-9
Client . . . . . . . . . . . . . . . . . . . . . C-13 Render Document for Rich Client . . . C-9
Global Services Preferences . . . C-1, C-13 Requirements Management . . . . . . . C-14
GM Customization for DPV . . . . . . . . C-5 Rich Client (Lite Edition) . . . . . . . . . C-2
GM Overlay . . . . . . . . . . . . . . . . . . . C-5 Rich Client 2-tier . . . . . . . . . . . . . . . C-2
GM PAD/TWP Customization . . . . . . C-5 Rich Client 4-tier . . . . . . . . . . . . . . . C-2
Hierarchical Storage Management Rich Client, Dispatcher Client . . . . . . C-9
(HSM) . . . . . . . . . . . . . . . . . . . . C-4 Sample Files . . . . . . . . . . . . . . . . . . C-3
Install Libraries for AI SOA Client . . C-11 SCM ClearCase for Foundation . . . . . C-12
Issue Management . . . . . . . . . . . . . . C-9 Server Enhancements . . . . . . . . . . . C-2
J2EE Based Server Manager . . . . . 15-1, Service Event Management . . . . . . . C-11
C-1, C-3 Service Planning . . . . . . . . . . . . . . . C-10
Lifecycle Visualization . . . . . . . . . . . C-10 Service Planning and Service Processing
Maintenance, Repair, and Alignment . . . . . . . . . . . . . . . . . C-11
Overhaul . . . . . . . . . . . . . . . . . . C-10 Service Request Processing . . . . . . . . C-11
Manufacturing Process Service Scheduler . . . . . . . . . . . . . . C-11
Management . . . . . . . . . . . . . . . . C-11 Spatial Search . . . . . . . . . . . . . . . . . C-7
Mapping Designer . . . . . . . . . . . . . . C-13 Specification Manager . . . . . . . . . . . C-7
MATLAB Integration Connector . . . . C-6 SRM Integration . . . . . . . . . . . . . . . C-14
Mechatronics Process Supplier Relationship
Management . . . . . . . . . . . . . . . . C-11 Management . . . . . . . . . . . . . . . . C-14
Mentor Board Station Library Systems Engineering . . . . . . . . . . . . C-14
Support . . . . . . . . . . . . . . . C-1, C-13 Systems Engineering and Requirements
Mentor Board Station Support . . . . . C-1, Management . . . . . . . . . . . . . . . . C-14
C-12 Teamcenter Automotive Edition . . . . C-5
Mentor Expedition Library Support . . C-1, Teamcenter Behavior Modeling
C-13 Framework . . . . . . . . . . . . . . . . . C-6
Mentor PADS Library Support . . . . . C-1, Teamcenter Client for Microsoft
C-13 Office . . . . . . . . . . . . . . . . . . . . . C-9
Mentor PADS Support . . . . . . . C-1, C-13 Teamcenter Extensions for Microsoft
Mentor Translation Support . . . . . . . 15-1 Office . . . . . . . . . . . . . . . . . . . . . C-14
Microsoft Office Teamcenter for Reporting and
Client for Office . . . . . . . . . . . . . C-9 Analytics . . . . . . . . . . . . . . . . . . C-14
Extensions for Office . . . . . . . . . C-14 Teamcenter Foundation . . . . . . . C-1–C-2
Microsoft Office client . . . . . . . . . . . . C-9 Teamcenter Manufacturing . . . . . . . . C-11
MTM Data Card . . . . . . . . . . . . . . . C-11 Teamcenter MATLAB Integration . . . C-6
Multisite Collaboration IDSM Teamcenter Rich Client (Shared Disk
Service . . . . . . . . . . . . . . . . C-1, C-13 Deployment) . . . . . . . . . . . . . . . . C-2
Multisite Collaboration ODS Teamcenter Rich Client 2-tier . . . . . . C-1
Service . . . . . . . . . . . . . . . . C-1, C-13 Teamcenter Rich Client 4-tier . . . . . . C-1
.NET Based Server Manager . . . . . . . C-3 Teamcenter Security Services . . . . . . C-3
NX Integration . . . . . . . . . . . . . . . . C-7 Teamcenter Visualization (Embedded) for
NX Manager for Rich Client . . . . . . . C-7 Rich Client . . . . . . . . . . . . . . . . . C-10
NX UG Integration . . . . . . . . . . . . . C-1 Teamcenter Visualization (Stand-alone) for
Online Help . . . . . . . . . . . . . . . . . . . C-3 Rich Client . . . . . . . . . . . . . . . . . C-10

Index
Teamcenter Web Tier . . . . . . . . . . . . C-4 Global Services EPSync Reactor . . . . . 10-11

Tecnomatix . . . . . . . . . . . . . . . . . . . C-11 Global Services Framework . . . . . C-1, C-13
Trueshape generation from JT . . . . . C-8 Global Services Global Services
Vendor Management . . . . . . . . . . . . C-14 Connector . . . . . . . . . . . . . . . . . . . . 10-12
Web Tier for .NET . . . . . . . . . . . . . . C-4 Global Services installation . . . . . . . . . 10-9
Weld Management . . . . . . . . . . . . . . C-4 Global Services Java memory error . . . . A-13
Wire Harness Configuration . . . . . . . C-12 Global Services Monitoring GUI for Rich
Wire Harness Configuration in GM Client . . . . . . . . . . . . . . . . . . . . . . . . C-13
Overlay . . . . . . . . . . . . . . . . . . . C-5 Global Services MS Messaging . . . . . . 10-11
Work Instructions . . . . . . . . . . . . . . C-11 Global Services Ode BPEL web
Workflow to Scheduling application . . . . . . . . . . . . . . . . . . . 10-12
Integration . . . . . . . . . . . . . . . . . C-14 Global Services Preferences . . . . . C-1, C-13
File Management features . . . . . . . . . . C-4 Global Services Security Proxy . . . . . . 10-12
File Management System Global Services solutions
Installation . . . . . . . . . . . . . . . . C-1, C-4 Axis2 Services . . . . . . . . . . . . . . . . 10-11
Installation overview . . . . . . . . . . . . 2-11 EPSync Reactor . . . . . . . . . . . . . . . 10-11
Volume server . . . . . . . . . . . . . . . . . C-1 Global Services BPEL Framework . . 10-12
Files Global Services Security Proxy . . . . 10-12
db2ese.lic . . . . . . . . . . . . . . . . . . . . . 3-4 Global Services user interface . . . . . 10-11
hs_err_* . . . . . . . . . . . . . . . . . . . . . A-10 JMS messaging . . . . . . . . . . . . . . . 10-11
INSTALL_TCWEB.EXE . . . . . . . . . . 10-2 Teamcenter 2007 or later . . . . . . . . 10-10
jakarta-regexp-1.3.jar . . . . . . . . . . . . A-4 Teamcenter 2007 through Teamcenter
mti.jar . . . . . . . . . . . . . . . . . . . . . . 10-7 2007.1 MP4 (full rich client
mtiems.jar . . . . . . . . . . . . . . . . . . . . 10-7 functionality) . . . . . . . . . . . . . . 10-11
Finished Product Management . . . . . . . C-6 Teamcenter 2007.1 MP5 through MP8 (full
Finished Product Management to CPG rich client functionality) . . . . . . . 10-11
Materials Bridge . . . . . . . . . . . . . . . . C-7 Teamcenter 8 or later (full rich client
FMS functionality) . . . . . . . . . . . . . . 10-11
FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-13 Teamcenter 9.1 Global Services Framework
FSC . . . . . . . . . . . . . . . . . . . . . . . . 2-12 - Data Exchange . . . . . . . . . . . . 10-12
Master configuration file . . . . . . . . . . 2-13 Teamcenter 9.1 Global Services Framework
See File Management System . . . . . . 2-11 - Global Services Connector . . . . 10-12
FMS Client Cache . . . . . . . . . . . . . . . . C-15 Teamcenter 9.1 Global Services Framework
FMS server cache . . . . . . . . . . . . . . . . C-1 - Teamcenter Sourcing . . . . . . . . 10-12
Installing to a non-local path . . . . . 6-3, 7-7 Teamcenter Engineering . . . . . . . . . 10-11
Fms_BootStrap_Urls preference . . . . . . . 7-4 Teamcenter Engineering 2005 through
Four-tier architecture 2007 . . . . . . . . . . . . . . . . . . . . . 10-11
Installation overview . . . . . . . . . . . . . 2-5 Teamcenter Enterprise . . . . . . . . . . 10-11
Overview . . . . . . . . . . . . . . . . . . . . . 1-12 Web services . . . . . . . . . . . . . . . . . 10-11
Troubleshooting deployment . . . . . . . A-5 Global Services Teamcenter 2007 Rich Client
FSC Connector . . . . . . . . . . . . . . . . . . . . 10-11
Installation overview . . . . . . . . . . . . 2-12 Global Services Teamcenter 2007.1 Rich Client
Installing to a non-local path . . . . . 6-3, 7-7 Connector . . . . . . . . . . . . . . . . . . . . 10-11
Transient server . . . . . . . . . . . . . . . 2-12 Global Services Teamcenter 8 Rich Client
Full Text Search Engine . . . . . . . . . . . C-3 Connector . . . . . . . . . . . . . . . . . . . . 10-11
Global Services Teamcenter Engineering
G 2005/2007 Connector . . . . . . . . . . . . 10-11
Global Services Teamcenter Engineering V9
Gateway for EDA Library . . . . . . C-1, C-13 Connector . . . . . . . . . . . . . . . . . . . . 10-11
Genius4000 data migration . . . . . . . . 14-10 Global Services Teamcenter Enterprise
Global Services . . . . . . . . . . . . . . . . . . 2-17 Connector . . . . . . . . . . . . . . . . . . . . 10-11
Features . . . . . . . . . . . . . . . . . . . . . C-1 Global Services Teamcenter SOA
Global Services Axis2 Services . . . . . . 10-11 Connector . . . . . . . . . . . . . . . . . . . . 10-10
Global Services Data Exchange . . . . . 10-12

Index
Global Services Teamcenter Windows . . . . . . . . . . . . . . . . . . . 3-2

Sourcing . . . . . . . . . . . . . . . . . . . . . 10-12 IBM DB2 support . . . . . . . . . . . . . . . . . 1-2
Global Services User Interface . . . . . . 10-11 ICD files, copying
Global Services Web Services Global Services . . . . . . . . . . . . . . . . 10-9
Connector . . . . . . . . . . . . . . . . . . . . 10-11 Teamcenter Web tier . . . . . . . . . . . . 10-3
global.services.proxy.client.IPs context IDOL . . . . . . . . . . . . . . . . . . . . . . . . . C-3
parameter . . . . . . . . . . . . . . . . . . . . D-10 IDOL server, Autonomy . . . . . . . . . . . . C-3
global.services.proxy.password context IDSM proxy server . . . . . . . . . . . . . . . . 2-3
parameter . . . . . . . . . . . . . . . . . . . . . D-9 IDSM server . . . . . . . . . . . . . . . . . . . . . 2-3
global.services.proxy.user context IDSM Service . . . . . . . . . . . . . . . . . . . C-13
parameter . . . . . . . . . . . . . . . . . . . . . D-9 IDSM_permitted_sites preference . . . . . . 8-3
GM Customization for DPV . . . . . . . . . C-5 images directory . . . . . . . . . . . . . . . . 10-35
GM Overlay . . . . . . . . . . . . . . . . . . . . C-5 Imports . . . . . . . . . . . . . . . . . . . . . . . . 4-4
CORP item creation fails . . . . . . . . . A-4 infodba . . . . . . . . . . . . . . . . . . . . . 1-6, 2-20
GM Overlay, AutoCAD integration . . . . C-5 Install images for connectors . . . . . . . . 10-6
GM Overlay, Wire Harness Install Libraries for AI SOA Client . . . . C-11
Configuration . . . . . . . . . . . . . . . . . . C-5 INSTALL_TCWEB.EXE file . . . . . . . . . 10-2
GM PAD/TWP Customization . . . . . . . . C-5 Installation
Groups Best practices . . . . . . . . . . . . . . . . . . 6-4
db2adms . . . . . . . . . . . . . . . . . . . . . . 3-2 Creating a configuration . . . . . . . . . . 19-1
db2users . . . . . . . . . . . . . . . . . . . . . . 3-2 Distribution server . . . . . . . . . . . . . 10-19
Distribution server instance . . . . . . 10-28
H IBM DB2
Windows . . . . . . . . . . . . . . . . . . . 3-1
Hebrew language . . . . . . . . . . . . . . . . 20-8 Modifying a configuration . . . . . . . . . 19-2
Heterogeneous environment . . . . . . . . . . 8-4 Oracle . . . . . . . . . . . . . . . . . . . . 2-18, 4-4
Heterogeneous network environment . . 2-20 Over-the-Web . . . . . . . . . . . . 1-11, 10-19
Hewlett-Packard HP-UX platforms Proxy server . . . . . . . . . . . . . . . . . . . 8-3
Platform support . . . . . . . . . . . . . . . . 1-1 Quick preconfigured . . . . . . . . . . . 7-5–7-6
System requirements . . . . . . . . . . . . . 1-1 Rich client instance . . . . . . . . . . . . 10-22
Hierarchical Storage Management Silent . . . . . . . . . . . . . . . . . . . . . . . 21-9
(HSM) . . . . . . . . . . . . . . . . . . . . . . . C-4 SQL Server . . . . . . . . . . . . . . . . . . . . 5-1
HP-UX platforms Teamcenter servers . . . . . . . . . . . . . . 7-1
Platform support . . . . . . . . . . . . . . . . 1-1 Using TEM . . . . . . . . . . . . . . 1-11, 10-19
System requirements . . . . . . . . . . . . . 1-1 Web Application Manager . . . . . . . . . 10-2
hs_err_* . . . . . . . . . . . . . . . . . . . . . . . A-10 Installation directory . . . . . . . . . . . . . . 15-2
HSM . . . . . . . . . . . . . . . . . . . . . . . . . C-4 installed.html file . . . . . . . . . . . . . . . 10-35
HTML pages . . . . . . . . . . . . . . . . . . . 10-19 installfailed.html file . . . . . . . . . . . . . 10-35
Installing
I Business Modeler IDE . . . . . . . . . . . 12-1
Dispatcher Client . . . . . . . . . . . . . . . 15-2
IBM AIX platforms Dispatcher Server . . . . . . . . . . . . . . 15-1
Platform support . . . . . . . . . . . . . . . . 1-1 EDA server . . . . . . . . . . . . . . . . . . . 15-1
System requirements . . . . . . . . . . . . . 1-1 EDA server support . . . . . . . . . . . . . 15-1
IBM DB2 Server Manager . . . . . . . . . . . . . . . . 15-2
Certified versions . . . . . . . . . . . . . . . . 3-1 Templates . . . . . . . . . . . . . . . . . . . . 13-1
Download URL . . . . . . . . . . . . . . 3-1–3-2 installing.html file . . . . . . . . . . . . . . . 10-36
Installation . . . . . . . . . . . . . . . . . . . . 3-1 insweb command . . . . . . . . . . . . . . . . . 10-2
Windows . . . . . . . . . . . . . . . . . . . 3-1 insweb.bat command . . . . . . 22-4, 22-6–22-7
License . . . . . . . . . . . . . . . . . . . . . . . 3-3 insweb.bat file . . . . . . . . 10-19, 10-28, 10-40
Requirements . . . . . . . . . . . . . . . . . . 3-1 Integrations
Software image . . . . . . . . . . . . . . . . . 3-1 Microsoft Office . . . . . . . . . . . . . . . . C-14
Unpopulating database . . . . . . . . . . A-18 Internationalization
Users and groups webstrings.xml file . . . . . . . . . . . . . . 20-6

Index
IPv6 mcast mode . . . . . . . . . . . . . . . . . A-11 Install graphic macros . . . . . . . . . . . 14-7

Issue Management . . . . . . . . . . . . . . . C-9 Install in another language . . . . . . . . 14-4
Installation . . . . . . . . . . . . . . . . . . . 14-1
J Updating from earlier version . . . . . . 14-7
Mapping Designer . . . . . . . . . . . . . . . . C-13
J2EE based server manager . . . . . . . . 1-12, Master configuration file . . . . . . . . . . . 2-13
2-2, 7-6, 11-8 MATLAB Integration Connector . . . . . . C-6
J2EE Based Server Manager . . . . . C-1, C-3 Max_Pool_Size parameter . . . . . . . . . . A-13
J2EE Based Server Manager feature . . 15-2 mcast error . . . . . . . . . . . . . . . . . . . . . A-11
J2EE Web tier Mechatronics Process Management
Server manager . . . . . . . . . . . . . . . . . 2-2 features . . . . . . . . . . . . . . . . . . . . . . C-11
Server manager, starting . . . . . . . . . 11-8 Media, distribution . . . . . . . . . . . . . . . B-1
jakarta-regexp-1.3.jar file . . . . . . . . . . . A-4 Mentor Board Station Library
Java error . . . . . . . . . . . . . . . . . . . . . A-10 Support . . . . . . . . . . . . . . . . . . C-1, C-13
Java out of memory error . . . . . . . . . . . A-13 Mentor Board Station Support . . . C-1, C-12
Java Runtime Environment . . . . . . . . . 10-2 Mentor Expedition Library support . . . C-13
java.lang.OutOfMemoryError . . . . . . . . A-13 Mentor Expedition Library Support . . . C-1
java.net.BindException . . . . . . . . . . . . A-11 Mentor PADS Library Support . . . . . . . C-1
JBoss Cache TreeCache . . . . . . . . . . . 10-5, Mentor PADS Support . . . . . . . . . C-1, C-13
11-1, 19-8, D-7 Microsoft IIS . . . . . . . . . . . . . . . . . . 10-38
JCA connection parameter . . . . . . . . . . A-13 Microsoft Office client . . . . . . . . . . . . . C-9
Microsoft Office extensions . . . . . . . . . . C-14
L Microsoft SQL Server, see SQL Server
Unpopulating database . . . . . . . . . . A-18
launcherror.html file . . . . . . . . . . . . . 10-36 Microsoft Windows platforms
Libraries . . . . . . . . . . . . . . . . . . . . . . C-11 Platform support . . . . . . . . . . . . . . . . 1-1
Licenses, IBM DB2 . . . . . . . . . . . . . . . . 3-3 System requirements . . . . . . . . . . . . . 1-1
Linux platforms Migration, Genius4000 data . . . . . . . . 14-10
Platform support . . . . . . . . . . . . . . . . 1-1 Mixed-language display
System requirements . . . . . . . . . . . . . 1-1 Thin client . . . . . . . . . . . . . . . . . . . . 20-3
Listener processes . . . . . . . . . . 4-2–4-3, 4-5 MRO As-Built and As-Maintained
listener.ora file . . . . . . . . . . . . . . . . 4-3, 4-5 Alignment . . . . . . . . . . . . . . . . . . . . . C-10
Localization MRO As-Built Management . . . . . . . . . C-10
Converting to Unicode . . . . . . . . . . . 20-9 MRO As-Maintained Management . . . . C-10
Hebrew language . . . . . . . . . . . . . . . 20-8 MS SQL Server, see SQL Server
Rich client . . . . . . . . . . . . . . . . . . . . 20-9 mti.jar file . . . . . . . . . . . . . . . . . . . . . 10-7
Thin client . . . . . . . . . . . . . . . . . . . . 20-9 mtiems.jar file . . . . . . . . . . . . . . . . . . 10-7
localization directory . . . . . . . . . . . . . . B-2 MTM Data Card . . . . . . . . . . . . . . . . . C-11
LogFileLocation . . . . . . . . . . . . . . . . 10-13 Multi-Site Collaboration
LogFileLocation context parameter . . . . D-8 IDSM service . . . . . . . . . . . . . . . . . . C-1
Logon, automatic . . . . . . . . . . . . . . . . . 2-6 Installation . . . . . . . . . . . . . . . . . . . C-1
Installing to a non-local path . . . . . 6-3, 7-7
M ODS service . . . . . . . . . . . . . . . . . . . C-1
Postinstallation tasks . . . . . . . . . . . . . 8-2
Macintosh platforms Proxy server . . . . . . . . . . . . . . . . . . C-1
Platform support . . . . . . . . . . . . . . . . 1-1 Wide area networks . . . . . . . . . . . . . . 8-2
System requirements . . . . . . . . . . . . . 1-1 Multiple database access
Maintenance packs . . . . . . . . . . . . . . . 22-1 Four-tier rich clients . . . . . . . . . . . . . 19-5
Maintenance, Repair, and Overhaul . . . C-10 Overview . . . . . . . . . . . . . . . . . . . . . 19-5
Manifest file . . . . . . . . . . . . . . . . . . . 10-31 Multiple EAR file support . . . . . . . . . 10-18
Manufacturing Process Management . . C-11
Manufacturing Resource Library N
Classes deleted at 9.1 . . . . . . . . . . . 14-10
Configure NX Library . . . . . . . . . . . . 14-5 native2ascii utility . . . . . . . . . . . . . . . 20-9

Index
.NET based server manager . . . . . . . . 1-12, PDF . . . . . . . . . . . . . . . . . . . . . . . . B-3

2-2, 7-6, 11-7 Rich client . . . . . . . . . . . . . . . . . . . . 18-7
.NET Based Server Manager tchelp.jar file . . . . . . . 7-1, 7-11, 10-4, C-3
NET Based Server Manager . . . . . . . C-3 Troubleshooting . . . . . . . . . . . . . . . . A-2
.NET State Service . . . . . . . . . . . . . . . C-4 Online Help . . . . . . . . . . . . . . . . . . . . C-3
NET Web tier . . . . . . . . . . . . . . . . . . . C-4 Operating system accounts . . . . . . 1-6, 2-20
ASP .NET State Service . . . . . . . . . . C-4 Operating system support . . . . . . . . . . . 1-1
.NET Web tier . . . . . . . . . . . . . . . . . . . C-4 Operating systems supported . . . . . . . . . 1-1
ASP .NET State Service . . . . . . . . . . C-4 Oracle
Differences from J2EE Web tier . . . . . 1-8 Data imports . . . . . . . . . . . . . . . . . . . 4-4
Online help . . . . . . . . . . . . . . . . 9-6, 18-8 Database Configuration Assistant . . 2-18,
Server manager . . . . . . . . . . 1-12, 2-2, 7-6 4-8
Server manager, starting . . . . . . . . . 11-7 Database creation . . . . . . . . . . . . . . . 4-8
Windows . . . . . . . . . . . . . . . . . . . . . 1-12 Database export . . . . . . . . . . . . . . . . . 4-2
Network Folders Database planning . . . . . . . . . . . . . . 2-18
Description . . . . . . . . . . . . . . . . . . . 1-10 Database upgrades . . . . . . . . . . . . 4-2–4-4
Networks Installation . . . . . . . . . . . . . . . . 2-18, 4-4
Client installation . . . . . . . . . . . . . . 2-20 Listener processes . . . . . . . . 4-2–4-3, 4-5
Heterogeneous network Net configuration . . . . . . . . . . . . . . . . 4-5
environment . . . . . . . . . . . . . . . . 2-20 Preinstallation tasks . . . . . . . . . . . . . 4-2
Homogeneous network Required version . . . . . . . . . . . . . . . . 4-7
environment . . . . . . . . . . . . . . . . 2-19 Shutting down database . . . . . . . . . . . 4-2
Site planning . . . . . . . . . . . . . . . . . . . 2-1 Site planning . . . . . . . . . . . . . . . . . . 2-18
NFS volume data access . . . . . . . . . . . 2-20 Software distribution image . . . . . . . B-2
Not enough storage is available to process this Terminating Oracle sessions . . . . . . . . 4-2
command error . . . . . . . . . . . . . . . . . A-13 Uninstallation . . . . . . . . . . . . . . . . . 23-6
NTFS partitions . . . . . . . . . . . . . . . . . . 6-3 Unpopulating database . . . . . . . . . . A-18
NX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Oracle Net Assistant . . . . . . . . . . . . . . . 4-5
NX Integration . . . . . . . . . . . . . . . . . . C-7 Oracle SQL*Plus . . . . . . . . . . . . . . . . . . 4-3
NX Library OracleTNSListener . . . . . . . . . . . . . . . . 4-5
Configure with shared MACH OracleTNSListener process . . . . . . . 4-2, 4-5
directory . . . . . . . . . . . . . . . . . . . 14-6 otw_installer.jar file . . . . . . . . . . . . . . 10-35
NX Manager for Rich Client . . . . . . . . . C-7 otw.html file . . . . . . . . . . . . . . . . . . . 10-36
NX UG Integration . . . . . . . . . . . . . . . C-1 Over-the-Web Installer . . . . . . . . . . . 10-19,
10-23, 10-29, 10-35, 22-4, 22-6
O Over-the-Web rich client . . . . . . . . . . 10-19
Object directory services, see ODS server and P

ODS proxy server
ODS proxy server . . . . . . . . . . . . . . . . . 2-3 Packaging and Artwork . . . . . . . . . . . . C-7
ODS server . . . . . . . . . . . . . . . . . . . . . . 2-3 Packaging and Artwork to Finished Product
ODS Service . . . . . . . . . . . . . . . . . . . . C-13 Management Bridge . . . . . . . . . . . . . C-7
ODS_permitted_sites preference . . . . . . . 8-3 PAD/TWP Customization . . . . . . . . . . . C-11
ODS_searchable_sites preference . . . . . . 8-3 PADS library support . . . . . . . . . . . . . C-13
ODS_site preference . . . . . . . . . . . . . . . 8-3 PADS support . . . . . . . . . . . . . . . . . . . C-13
Online help . . . . . . . . . . . . . . . . . . . . . 10-2 Parameters
Configuring for .NET Web tier . . . 9-6, 18-8 CookiePath . . . . . . . . . . . . . . . . . . . A-12
Configuring on IIS . . . . . . . . . . . 9-6, 18-8 global.services.proxy.service.URL . . . D-9
Distribution image . . . . . . . . . . . . . . B-2 Max_Pool_Size . . . . . . . . . . . . . . . . . A-13
Enabling search . . . . . . . . . . . . . . . . 18-9 Web tier . . . . . . . . . . . . . . . . . . . . . D-1
HTML . . . . . . . . . . . . . . . . . . . . . . . B-3 Password, valid characters . . . . . . 19-3, 19-5
Installation . . . . . . . . . . . . . . . 10-4, C-3 Patches . . . . . . . . . . . . . . . . . . . . . . . 22-1
Installation alternatives . . . . . . . . . . 2-18 Patching
Over-the-Web access . . . . . . . . . . . . . 18-7 Customer-specific patches . . . . . . . . . 22-6

Index
Patching rich client R

Customer-specific patches . . . . . . . . . 22-6
Described . . . . . . . . . . . . . . . . . . . . 22-4 RAC.OSGi.plugin.URL.suffix context
Silently . . . . . . . . . . . . . . . . . . . . . . 22-4 parameter . . . . . . . . . . . . . . . . . . . . D-10
Using Over-the-Web Installer . . . . . . 22-4 RDV
Patching Teamcenter lifecycle Database instance . . . . . . . . . . . . . . 2-18
visualization . . . . . . . . . . . . . . . . . . . 22-6 QPL server . . . . . . . . . . . . . . . . . . . . 2-4
Patching the server . . . . . . . . . . . . . . . 22-2 README file . . . . . . . . . . . . . . . . . . . 22-8
Patching thin client . . . . . . . . . . . . . . . 22-7 Red Hat Linux platforms
Penetration Request Management . . . . C-10 Platform support . . . . . . . . . . . . . . . . 1-1
Platform support . . . . . . . . . . . . . . . . . . 1-1 System requirements . . . . . . . . . . . . . 1-1
Database servers . . . . . . . . . . . . . . . . 1-2 Remote Method Invocation . . . . 10-21, 10-39
POM transmit schema files . . . . . . . . . . 8-3 Remote workflow
Pool manager, starting . . . . . . . . . . . . . 11-7 Site planning . . . . . . . . . . . . . . . . . . 2-17
portal directory . . . . . . . . . . . . . . . . . . B-2 Remote Workflow . . . . . . . . . . . . . . . . C-9
portalHelpPage property . . . . . . . . . . . A-2 Installation . . . . . . . . . . . . . . . . . . . C-9
Postinstallation tasks . . . . . . . . . . . . . . 8-1 Removing features . . . . . . . . . . . . . . . 19-2
Postupgrade tasks . . . . . . . . . . . . . . . . . 8-1 Render Document for Rich Client . . . . . C-9
Preferences Render Manager
Fms_BootStrap_Urls . . . . . . . . . . . . . 7-4 Installation . . . . . . . . . . . . . . . . . . . C-9
IDSM_permitted_sites . . . . . . . . . . . . 8-3 Required features . . . . . . . . . . . . . . C-9
ODS_permitted_sites . . . . . . . . . . . . . 8-3 Repeatable Digital Validation . . . . . . . . C-8
ODS_searchable_sites . . . . . . . . . . . . 8-3 Requirements
ODS_site . . . . . . . . . . . . . . . . . . . . . . 8-3 Database . . . . . . . . . . . . . . . . . . . . . . 1-1
TC_publishable_classes . . . . . . . . . . . 8-3 Database, IBM DB2 . . . . . . . . . . . . . . 3-1
TC_transfer_area . . . . . . . . . . . . . . . . 8-3 IBM DB2 . . . . . . . . . . . . . . . . . . . . . . 3-1
WEB_core_help_server . . 18-10, A-2, A-14 Java . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
WEB_default_site_deployed_app_ Operating systems . . . . . . . . . . . . . . . 1-1
name . . . . . . . . . . . . . . . . . . . . . A-3 Requirements Management . . . . . . . . . C-14
WEB_help_server . . . . . 18-10, A-2, A-14 Resource Manager, Genius4000 data
Preinstallation tasks . . . . . . . . . . . . . . . 6-1 migration . . . . . . . . . . . . . . . . . . . . 14-10
Prerequisite software . . . . . . . . . . . . . . 1-1 Resource tier
Problem Reports (PRs) . . . . . . . . . . . . . 22-8 Four-tier . . . . . . . . . . . . . . . . . . . . . 1-13
Product Master Management Two-tier . . . . . . . . . . . . . . . . . . . . . 1-11
CAD BOM Alignment . . . . . . . . . . . . C-6 Reverse proxy configuration
Product Master Manager . . . . . . . . . C-5 SiteMinder . . . . . . . . . . . . . . . . . . 10-34
Product Master Manager . . . . . . . . . . . C-5 WebSEAL . . . . . . . . . . . . . . . . . . . 10-34
Profile variables . . . . . . . . . . . . . . . . . . 3-4 Rich client
Programs Deployment over the Web . . . . . . . . 10-19
Web Application Manager . . . . . . . . 22-4, Description . . . . . . . . . . . . . . . . . . . 1-10
22-6–22-7 Four-tier . . . . . . . . . . . . . . . . . . C-1–C-2
Properties, portalHelpPage . . . . . . . . . A-2 Installing patches . . . . . . . . . . . . . . 22-4
Proxy server . . . . . . . . . . . . . . . . . . . . . 8-3 Language display configuration . . . . . 20-2
Proxy WAR file (WebLogic) . . . . . 10-6, 10-13 Localization . . . . . . . . . . . . . . . 20-6, 20-9
Publishing to default ODS hangs application Online help . . . . . . . . . . . . . . . 18-7, A-2
server . . . . . . . . . . . . . . . . . . . . . . . . A-11 Overview . . . . . . . . . . . . . . . . . . . . . 1-10
Two-tier . . . . . . . . . . . . . . . . . . C-1–C-2
Q Rich Client (Lite Edition) . . . . . . . . . . . C-2
Rich Client (Shared Disk Deployment) . . C-2
QPL for Repeatable Digital Validation . . C-8 Rich client distribution server, see Distribution
QPL server . . . . . . . . . . . . . . . . . . . . . . 2-4 server
Quick preconfigured installation . . . . 7-5–7-6 Rich client distribution server instance, see
Distribution server instance
Rich client instance

Index
Deployment . . . . . . . . . . . . . . . . . . 10-35 Session cookies overwritten on the

Installation . . . . . . . . . . . . . . . . . . 10-22 client . . . . . . . . . . . . . . . . . . . . . . . . A-12
Rich client instance, four-tier . . . . . . . 10-28 Shared Disk Deployment, rich client . . . C-2
Rich client solutions, patching . . . . . . . 22-4 Silent installation . . . . . . . . . . . . . . . . 21-9
RMI registry Silent patching . . . . . . . . . . . . . . . . . . 22-4
Port number . . . . . . . . . . . . . . . . . 10-21 Site planning . . . . . . . . . . . . . . . . . . . . 2-1
Starting . . . . . . . . . . . . . . . . . . . . 10-39 SiteMinder . . . . . . . . . . . . . . . . . . . . 10-34
Stopping . . . . . . . . . . . . . . . . . . . . 10-39 Software distribution image . . . . . . . . . B-1
Software requirements . . . . . . . . . . . . . 1-1
S Application servers . . . . . . . . . . . . . 10-2
Java . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Sample database . . . . . . . . . . . . . . . 3-5–3-6 Solutions
Sample files . . . . . . . . . . . . . . . . . . . . C-3 Business Modeler IDE . . . . . . . . . . . C-1
Sample Files . . . . . . . . . . . . . . . . . . . . C-3 Corporate Server . . . . . . . . . . . . . . . C-1
SCM ClearCase for Foundation . . . . . . C-12 Dispatcher (Dispatcher Server) . . . . . C-1
Scripts EDA Standalone Client . . . . . . . . . . C-1
Create_database.sql . . . . . . . . . . . . . . 5-3 Global Services . . . . . . . . . . . . . . . . C-1
Security Services . . . . . . . . . . . . . . . . 2-17 Multisite Collaboration Proxy
Server Server . . . . . . . . . . . . . . . . . . . . C-1
Installing patches . . . . . . . . . . . . . . 22-2 Rich Client 2-tier . . . . . . . . . . . . . . . C-1
Server Enhancements Rich Client 4-tier . . . . . . . . . . . . . . . C-1
Features . . . . . . . . . . . . . . . . . . . . . C-2 Volume Server . . . . . . . . . . . . . . . . . C-1
Server installation . . . . . . . . . . . . . . . 15-1 Spatial Search . . . . . . . . . . . . . . . . . . C-7
Server manager Specification Manager . . . . . . . . . . . . . C-7
J2EE . . . . . . . . . . . . . . . . . . . . . . . C-3 Specifying a specific bind address when a host
J2EE based . . . . . . . . . . . . . 1-12, 2-2, 7-6 has multiple IP addresses . . . . . . . . . A-6
J2EE based, starting . . . . . . . . . . . . 11-8 SQL Server . . . . . . . . . . . . . . . . . . . . . 2-19
J2EE based, troubleshooting . . . . . . . A-6 Create_database.sql script . . . . . . . . . 5-3
.NET . . . . . . . . . . . . . . . . . . . . . . . . C-3 Database creation, SQL script . . . . . . . 5-2
.NET based . . . . . . . . . . . . . 1-12, 2-2, 7-6 Installation . . . . . . . . . . . . . . . . . . . . 5-1
.NET based, starting . . . . . . . . . . . . 11-7 Uninstallation . . . . . . . . . . . . . . . . . 23-6
Server manager error . . . . . . . . . . . . . A-10 SQL*Plus utility . . . . . . . . . . . . . . . . . . 4-3
Server manager restart error . . . . . . . . A-9 SRM Integration . . . . . . . . . . . . . . . . . C-14
Server manager, starting . . . . . . . . . . . 11-7 SSOAppID . . . . . . . . . . . . . . . . . . . . 10-13
SERVER_HOST parameter . . . . . 11-1, A-6 SSOAppID context parameter . . . . . . . D-8
Server, patching . . . . . . . . . . . . . . . . . 22-2 Stand-alone application viewer . . . . . . . C-10
serverPool.properties file . . . . . . . 11-1, A-6 Stand-alone Applications
Service Event Management . . . . . . . . . C-11 EDA Stand-alone Client . . . . . . . . . . C-12
Service Planning . . . . . . . . . . . . . . . . . C-10 start_rmi.bat file . . . . . . . . . . . . . . . . 10-39
Service Planning and Service Processing start_server.bat file . . . . . . . . . . . . . . 10-39
Alignment . . . . . . . . . . . . . . . . . . . . . C-11 stop_server.bat file . . . . . . . . . . . . . . 10-39
Service Request Processing . . . . . . . . . C-11 Subscription manager . . . . . . . . . . . . . . 8-1
Service Scheduler . . . . . . . . . . . . . . . . C-11 Subscription Manager Service . . . . . . . C-4
Services Sun Java System . . . . . . . . . . . . . . . 10-37
Action Manager . . . . . . . . . . . . . . . . C-4 Sun Java System Application Server
ASP .NET State Service . . . . . . . . . . C-4 hangs . . . . . . . . . . . . . . . . . . . . . . . . A-11
IDSM Service . . . . . . . . . . . . . . . . . C-13 Sun Java System Application Server is
ODS Service . . . . . . . . . . . . . . . . . . C-13 unresponsive . . . . . . . . . . . . . . . . . . . A-11
Subscription Manager . . . . . . . . . . . C-4 Sun Solaris platforms
Task Manager . . . . . . . . . . . . . . . . . C-4 Platform support . . . . . . . . . . . . . . . . 1-1
Teamcenter Shared Metadata Cache System requirements . . . . . . . . . . . . . 1-1
Service . . . . . . . . . . . . . . . . . . . . C-4 Support files
Tesselation Manager . . . . . . . . . . . . C-4 mtiems.jar . . . . . . . . . . . . . . . . . . . . 10-7
Session cookies . . . . . . . . . . . . . . . . . . A-12 Teamcenter Enterprise connector . . . 10-7

Index
SUSE Linux platforms Teamcenter client communication

Platform support . . . . . . . . . . . . . . . . 1-1 system . . . . . . . . . . . . . . . . . . . . . . . C-15
System requirements . . . . . . . . . . . . . 1-1 Teamcenter Client for Microsoft Office . . C-9
Systems Engineering . . . . . . . . . . . . . . C-14 Teamcenter database . . . . . . . . . . . . 3-6–3-8
Systems Engineering and Requirements Teamcenter Engineering 2005/2007 . . . 10-7
Management Teamcenter Engineering Portal
Requirements Management . . . . . . . C-14 directory . . . . . . . . . . . . . . . . . . . . . . 10-7
Systems Engineering . . . . . . . . . . . . C-14 Teamcenter engineering process management
URLs, migrating to Teamcenter 9.1 . . 10-15
T Teamcenter Engineering V9
connector . . . . . . . . . . . . . . . . . . . . . 10-7
Task Manager Service . . . . . . . . . . . . . C-4 Teamcenter Enterprise connector, required
Task monitor . . . . . . . . . . . . . . . . . . . . 8-1 files . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
TC_auto_login preference . . . . . . . . . . . 2-6 Teamcenter Environment Manager . . . . 7-1,
TC_DATA environment variable . . . . . . 2-2, 22-2, 22-4
7-9, 19-3–19-4 Installation log files . . . . . . . . . . . . . A-1
TC_publishable_classes preference . . . . . 8-3 Removing features . . . . . . . . . . . . . . 19-2
TC_ROOT environment variable . . . . . 2-2, Uninstalling . . . . . . . . . . . . . . . . . . 23-1
6-3, 7-7 Teamcenter Extensions for Microsoft
TC_transfer_area preference . . . . . . . . . 8-3 Office . . . . . . . . . . . . . . . . . . . . . . . . C-14
TCCS . . . . . . . . . . . . . . . . . . . . . . . . . C-15 Teamcenter for Reporting and
Stand-alone uninstallation . . . . . . . . 23-2 Analytics . . . . . . . . . . . . . . . . . . . . . C-14
TcGSBOSJNDI . . . . . . . . . . . . . . . . . 10-13 Teamcenter Foundation . . . . . . . . . C-1–C-2
TcGSBOSJNDI context parameter . . . . D-8 Teamcenter Integration for NX/NX Integration
TcGSConnectorJNDI context Configuration . . . . . . . . . . . . . . C-1, C-7
parameter . . . . . . . . . . . . . . . . . . . . D-10 Overview . . . . . . . . . . . . . . . . . . . . . . 6-4
TcGSDORJNDI . . . . . . . . . . . . . . . . 10-13 Teamcenter lifecycle visualization . . . . . 22-6
TcGSEngJNDI context parameter . . . D-10 Embedded viewer . . . . . . . . . . . . . . . C-10
TcGSEntJNDI context parameter . . . . D-11 Installation . . . . . . . . . . . . . . . . . . . 2-15
TcGSJDBCJNDI . . . . . . . . . . . . . . . . 10-13 Stand-alone application viewer . . . . . C-10
TcGSJDBCJNDIl context parameter . . . D-9 Teamcenter Linking . . . . . . . . . . . . . . 2-17
TcGSMessageServerJNDI . . . . . . . . . 10-13 See also Remote workflow
TcGSMessageServerJNDI context Teamcenter maintenance, repair, and
parameter . . . . . . . . . . . . . . . . . . . . . D-9 overhaul . . . . . . . . . . . . . . . . . . . . . . C-10
TcGSNotifierReactorJNDI . . . . . . . . . 10-13 Teamcenter manufacturing process
TcGSNotifierReactorJNDI context management . . . . . . . . . . . . . . . . . . . 14-1
parameter . . . . . . . . . . . . . . . . . . . . . D-9 Configure Resource Browser and NC
TcGSOMfgJNDI context parameter . . D-11 Package Browser . . . . . . . . . . . . . C-11
TcGSRACJNDI context parameter . . . D-10 MTM Data Card . . . . . . . . . . . . . . . C-11
TcGSSAPJNDI context parameter . . . D-11 Teamcenter MATLAB Integration . . . . C-6
TcGSSOAJNDI context parameter . . . D-10 Teamcenter Rich Client (Shared Disk
TCP_NODELAY environment Deployment) . . . . . . . . . . . . . . . . . . . C-2
variable . . . . . . . . . . . . . . . . . . . . . . . 6-2 Teamcenter Security Services . . . . . . . . C-3
Teamcenter Teamcenter Shared Metadata Cache
Installation . . . . . . . . . . . . . . . . . . . . 7-1 Service . . . . . . . . . . . . . . . . . . . . . . . C-4
Uninstallation . . . . . . . . . . . . . . . . . 23-1 Teamcenter visualization for rich
Teamcenter administrator password . . 19-3, client . . . . . . . . . . . . . . . . . . . . . . . . C-10
19-5 Teamcenter Web Tier . . . . . . . . . . . . . C-4
Teamcenter application server . . . . . . . 2-20 TeamcenterConnectorJNDI context
Teamcenter Automotive Edition . . . . . . C-5 parameter . . . . . . . . . . . . . . . . . . . . D-10
Teamcenter Automotive Edition–GM Tecnomatix . . . . . . . . . . . . . . . . . . . . . C-11
Overlay . . . . . . . . . . . . . . . . . . . . . . C-5 Templates
Teamcenter Behavior Modeling Installing . . . . . . . . . . . . . . . . . . . . 13-1
Framework . . . . . . . . . . . . . . . . . . . . C-6 Updating . . . . . . . . . . . . . . . . . . . . . 13-4

Index
Templates, database . . . . . . . . . . . 2-18, 4-8 Unpopulation of Microsoft SQL Server

Tesselation Manager Service . . . . . . . . C-4 database . . . . . . . . . . . . . . . . . . . . . . A-18
Thin client Unpopulation of Oracle database . . . . . A-18
Description . . . . . . . . . . . . . . . . . . . 1-10 Update a template . . . . . . . . . . . . . . . 13-4
FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-14 Upgrade
Fms_BootStrap_Urls preference . . . . . 7-4 Oracle databases . . . . . . . . . . . . . 4-2–4-4
Hebrew language . . . . . . . . . . . . . . . 20-8 URLs, Teamcenter engineering process
Installation . . . . . . . . . . . . . . . . . . . . 2-6 management . . . . . . . . . . . . . . . . . . 10-15
Installation overview . . . . . . . . . . . . 2-11 User Account Control (UAC) . . . . . . . . . 1-2
Installing patches . . . . . . . . . . . . . . 22-7 User accounts . . . . . . . . . . . . . . . . 1-6, 2-20
Language display configuration . . . . . 20-2 Users
Localization . . . . . . . . . . . 20-6–20-7, 20-9 db2admin . . . . . . . . . . . . . . . . . . . . . 3-2
Localized text . . . . . . . . . . . . . . . . . 20-6 Utilities
Migrating legacy URLs . . . . . . . . . . 10-15 native2ascii . . . . . . . . . . . . . . . . . . . 20-9
Online help . . . . . . . . . . . . . . . . . . . A-2 Teamcenter Environment
Upgrading legacy URLs . . . . . . . . . 10-15 Manager . . . . . . . . . . . . . . . 22-2, 22-4
Thin client solutions, patching . . . . . . . 22-7
tnsnames.ora file . . . . . . . . . . . . . . . . . . 4-3
Tomcat . . . . . . . . . . . . . . . . . . . . . . . 10-37 V
Translation service . . . . . . . . . . . . . . . C-10
Variables
Translation Services for Rich Client . . . C-9
DB2_CREATE_DB_ON_PATH . . . . . . 3-7
TreeCache initialization fails . . . . . . . . A-8
Vendor Management . . . . . . . . . . . . . . C-14
TreeCache initialization failure . . . . . . A-6
Viewable files . . . . . . . . . . . . . . . . . . . 15-1
TreeCache local service port . . . . . . . . . A-8
Visualization
TreeCache parameters . . . . . . . . . . . . 10-5,
Dispatcher Server . . . . . . . . . . . . . . 15-1
11-1, 19-8, D-7
Embedded viewer . . . . . . . . . . . . . . . C-10
TreeCache peers . . . . . . . . . . . . . . . . . A-9
Stand-alone application viewer . . . . . C-10
Troubleshooting
Volume Server . . . . . . . . . . . . . . . . . . C-1
Four-tier deployment . . . . . . . . . . . . A-5
Volumes . . . . . . . . . . . . . . . . . . . . . . . 2-20
No administrator privileges error . . . A-2
Online help . . . . . . . . . . . . . . . . . . . A-2
Server installation . . . . . . . . . . . . . . A-1 W
Server manager . . . . . . . . . . . . . . . . A-6
Trueshape generation from JT . . . . . . . C-8 Web Application Manager . . . . . . . . . . 22-6
Two-tier architecture Installation . . . . . . . . . . . . . . . . . . . 10-2
Deployment . . . . . . . . . . . . . . . . . . . 1-12 Launching . . . . . . . . . . . . . . . . . . . . 10-2
Installation overview . . . . . . . . . . . . . 2-4 Patching . . . . . . . . . . . . . . . . . . . . . 22-4
Overview . . . . . . . . . . . . . . . . . . . . . 1-10 Web servers
Deploying Web components . . . . . . . 10-35
Deployment . . . . . . . . . . . . . . . . . . 10-19
U Supported servers . . . . . . . . . . . . . 10-35
Web tier
UAC, Windows Server 2008 . . . . . . . . . . 1-2 connection problems . . . . . . . . . . A-3, A-6
UGS_LICENSE_SERVER environment Features . . . . . . . . . . . . . . . . . . . . . C-4
variable . . . . . . . . . . . . . . . . . . . . . . . 6-2 Generating application . . . . . . . 10-3, 10-9
Unexpected error detected by J2EE . . . . . . . . . . . . . . . . . . . . . . . 1-12
HotSpot . . . . . . . . . . . . . . . . . . . . . . A-10 Legacy thin client URLs . . . . . . . . . 10-15
Unicode . . . . . . . . . . . . . . . . . . . . . . . 20-9 Multiple applications . . . . . . . . . . . 10-18
Uninstallation Proxy WAR file (WebLogic) . . . 10-6, 10-13
Oracle . . . . . . . . . . . . . . . . . . . . . . . 23-6 Shared application server
SQL Server . . . . . . . . . . . . . . . . . . . 23-6 instance . . . . . . . . . . . . . . . . . . 10-18
TCCS . . . . . . . . . . . . . . . . . . . . . . . 23-2 Web Tier for .NET . . . . . . . . . . . . . . . . C-4
Teamcenter . . . . . . . . . . . . . . . . . . . 23-1 Web tier installation problems . . . . . . . A-4
Unpopulation of IBM DB2 database . . . A-18 Web tier requirements . . . . . . . . . . . . . . 1-1

Index
WEB_core_help_server preference . . . 18-10, webstrings.xml file . . . . . . . . . . . . . . . 20-6

A-2, A-14 Weld Management . . . . . . . . . . . . . . . C-4
WEB_default_site_deployed_app_name Windows
preference . . . . . . . . . . . . . . . . . . . . . A-3 Chinese characters . . . . . . . . . . 1-3, A-13
WEB_help_server preference . . . . . . . 18-10, Windows platforms
A-2, A-14 Platform support . . . . . . . . . . . . . . . . 1-1
Web_tier directory . . . . . . . 10-3, 10-9, 10-21 System requirements . . . . . . . . . . . . . 1-1
Web-tier initialization failure when using Windows UAC . . . . . . . . . . . . . . . . . . . 1-2
Windows Network Load Balancer . . . . A-6 Wire Harness Configuration . . . . . . . . . C-12
webapp_root directory . . . . . . . . . . . . 10-31, Wiring Harness Design Tools
10-35, 10-38–10-39 Integration . . . . . . . . . . . . . . . . . . . . C-12
WebLogic Work Instructions . . . . . . . . . . . . . . . . C-11
Overwritten session cookie . . . . . . . . A-12 Workflow to Scheduling Integration . . . C-14
WebSEAL . . . . . . . . . . . . . . . . . . . . . 10-34
WebSphere . . . . . . . . . . . . . . . . . . . . 10-38

Team Center 9.1 Installation - Server - Windows PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Team Center 9.1 Installation - Server - Windows PDF

Uploaded by

Copyright:

Available Formats

Teamcenter 9.

Installation on Windows Servers Guide

This software and related documentation are proprietary to Siemens Product

2 Installation on Windows Servers Guide PLM00013 H

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

Part I: Getting started with Teamcenter server installation

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Part II: Database server installation

IBM DB2 installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Microsoft SQL Server installation and configuration . . . . . . . . . . . . . . 5-1

Part III: Teamcenter server installation

Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

PLM00013 H Installation on Windows Servers Guide 3

Install the licensing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Part IV: Web tier installation

.NET Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Part V: Adding features

Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Install the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Installing a custom solution or third-party template . . . . . . . . . . . . . . 13-1

4 Installation on Windows Servers Guide PLM00013 H

Install EDA server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Installing Teamcenter reporting and analytics . . . . . . . . . . . . . . . . . . 16-1

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Installing Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Part VI: Additional configuration and maintenance

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . 19-1

Deploying localized versions of Teamcenter . . . . . . . . . . . . . . . . . . . . . 20-1

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

PLM00013 H Installation on Windows Servers Guide 5

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1

Part VII: Appendixes

Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

6 Installation on Windows Servers Guide PLM00013 H

Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Platform support for Teamcenter servers and clients . . . . . . . . . . . . . . 1-2

PLM00013 H Installation on Windows Servers Guide 7

I Getting started with Teamcenter

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

PLM00013 H Installation on Windows Servers Guide

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-9

PLM00013 H Installation on Windows Servers Guide

Platform support for Teamcenter servers and clients

PLM00013 H Installation on Windows Servers Guide 1-1

Notes about platform support

• For information about installing Teamcenter on Windows clients, see the

• For information about installing Teamcenter on UNIX or Linux servers, see