SIEMENS

Teamcenter 11.2

Windows Server
Installation
PLM00013 • 11.2
Contents

Part I: Getting started with Teamcenter server installation

Requirements and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Where to find system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
System hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Web tier support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Teamcenter help requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Software integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Locate Teamcenter distribution images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Create the Teamcenter administrative user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
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-10
Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Teamcenter network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
File Management System (FMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Selecting and configuring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Basic tasks in Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Teamcenter help overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Install the Siemens PLM Documentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Install Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Configuring online help during Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Installing localized online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Configuring language support for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Teamcenter localizations provided by Siemens PLM Software . . . . . . . . . . . . . . . . . . . . 2-11
Choose the character set for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Verify that your locale is supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Configuring a UTF-8 environment for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Configuring a non-UTF-8 environment for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Installation and deployment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Planning the Teamcenter network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

PLM00013 11.2 Windows Server Installation 3

 Contents
Contents

Installing Teamcenter components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Oracle server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
MS SQL server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Network environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Required operating system and user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Part II: Database server installation

IBM DB2 installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

IBM DB2 installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

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-4
About DB2 sample databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Create a sample database using default sample tables . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Create a sample database using your own parameters and tables . . . . . . . . . . . . . . . . . . 3-5
Verify connectivity with the sample database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Creating 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-7

Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Preparing the Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Upgrade an Oracle server and database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Export an Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Terminate Oracle sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Back up an Oracle installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Upgrading an Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Configure Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Configure Oracle Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Configure Oracle listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Create an Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Microsoft SQL Server installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Install Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Create an SQL Server database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Part III: Teamcenter server installation

Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

4 Windows Server Installation PLM00013 11.2

 Contents

Obtain a Teamcenter license file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Install the licensing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Select destination directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Install a volume server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Install NX and Teamcenter Integration for NX or NX Integration . . . . . . . . . . . . . . . . . . . . . . . 6-5
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Best installation practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Install a Teamcenter corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Start database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Configure online help access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Overview of Multi-Site Collaboration configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Prepare the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Install a proxy server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Configure heterogeneous operating system environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Back up new installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Terminate Teamcenter sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Back up existing Teamcenter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Back up Teamcenter databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Part IV: Web tier installation

.NET web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

.NET web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Install required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Configure Microsoft IIS on Windows Server 2008/2012 . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Install the .NET web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Start the web client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Java EE web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Overview of Java EE web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Java EE web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Install thin client web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Build the Teamcenter Web Tier web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Build additional web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Sharing an application server instance for multiple four-tier environments . . . . . . . . . . . 10-15
Install rich client web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Planning rich client distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

PLM00013 11.2 Windows Server Installation 5

 Contents
Contents

Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19

Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Managing the rich client distribution server and instances . . . . . . . . . . . . . . . . . . . . . . 10-37

Part V: Adding features

Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Install the .NET server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Install the Java EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Start the .NET-based server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Launch the Teamcenter Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

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

Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Introduction to Manufacturing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Installing and configuring the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . 14-1
Configure Manufacturing Resource Library users, groups, and roles . . . . . . . . . . . . . . . . 14-1
Install the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Import part family templates when you use custom item IDs . . . . . . . . . . . . . . . . . . . . . 14-6
Configure NX Library using the installation wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Configure the NX Library when using a shared MACH directory . . . . . . . . . . . . . . . . . . . 14-7
Configure graphics builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Updating the Manufacturing Resource Library from an earlier version . . . . . . . . . . . . . . . . . . 14-9
Update the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Deleted classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11
Planning data migration from Genius4000 to Resource Manager . . . . . . . . . . . . . . . . . . . . 14-12

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-4
Deploy Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Complete Reporting and Analytics installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5

6 Windows Server Installation PLM00013 11.2

 Contents

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Part VI: Additional configuration and maintenance

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Create a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Modify a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Add an existing Teamcenter database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Add or configure a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Change the Oracle password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
How to change the Oracle password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Encrypt the password file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Encrypt the database connection string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Configure multiple databases for a four-tier rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Multiple database overview (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Multiple database example (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Migrate Teamcenter to a different JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11

Deploying localized versions of Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Deploying localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Deploying thin client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Deploying rich client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Configuring client display language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Choose a display language for the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Choose a display language for the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Choose the default language for the Teamcenter server process . . . . . . . . . . . . . . . . . . 19-8
Add multibyte character support in an English rich client . . . . . . . . . . . . . . . . . . . . . . . . 19-8

Creating a custom distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Overview of custom distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Create a silent distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Create a compact distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Using Updates Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1
Patch Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Migrate trace links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
Install patches on a Teamcenter server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Choosing the patching method for the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Patch the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6

PLM00013 11.2 Windows Server Installation 7

 Contents
Contents

Patch the rich client silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7

Patch the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
Patch Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Patch the web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10
Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-11

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Uninstall Teamcenter configurations and installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Uninstall TCCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2
Uninstalling IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Before uninstalling DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Remove DB2 instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Remove DB2 software on UNIX and Linux systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Remove DB2 software on Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-5
Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-5
Uninstall SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6
Uninstall Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6

Part VII: Appendixes

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Problems/error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Update Manager FTP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Resolving web tier connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Java exception errors during command-line updates . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Web Application Manager needs location of Java file when installing rich client . . . . . . . . . A-6
Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Troubleshooting the .NET web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Resolving thin client error on 64-bit Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Resolving .NET server manager port conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
Finding Oracle errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
View additional information about an Oracle error message . . . . . . . . . . . . . . . . . . . . . . A-16
Tuning WebSphere JVM memory consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Troubleshooting document rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18
Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Recovering a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Overview of recovery from a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Recovering from a corrupted IBM DB2 database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Recovering from a corrupted Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22
Recovering from a corrupted Microsoft SQL Server database . . . . . . . . . . . . . . . . . . . . A-22

Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Teamcenter distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

8 Windows Server Installation PLM00013 11.2

 Contents

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-1
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15

Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Deploying Teamcenter help in an existing web server . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

Figures

Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
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
Teamcenter online help on the PLM Documentation Server . . . . . . . . . . . . . . . . . . . . . 2-2
Siemens PLM Documentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Unicode homogeneous server platform configuration . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Basic File Management System deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Multiple databases (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Sample silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

Tables

Platform support for Teamcenter servers and clients . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Required hard disk space for Teamcenter configurations . . . . . . . . . . . . . . . . . . . . . . 1-4
Environment settings on non-UTF-8 systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Rich client optional parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Lifecycle Visualization (embedded viewer) parameter and table values . . . . . . . . . . . 10-24
Lifecycle Visualization (stand-alone application viewer) parameter and table values . . 10-25
Teamcenter Integration for NX parameter and table values . . . . . . . . . . . . . . . . . . . 10-25
JVM options for tuning the WebSphere Application Server memory usage . . . . . . . . . . A-17

PLM00013 11.2 Windows Server Installation 9

 Contents
Contents

Teamcenter features . . . . . . . . . . .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Web tier required parameters . . . . .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Web tier optional parameters . . . . .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Global Services context parameters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7

10 Windows Server Installation PLM00013 11.2

Part I: Getting started with Teamcenter server installation

Installation of Teamcenter 11.2 on Microsoft Windows servers includes installation of Teamcenter

servers using Teamcenter Environment Manager and the Teamcenter web tier using the Web
Application Manager.
Installing Teamcenter 11.2 requires a thorough working knowledge of your operating system and
general knowledge of Teamcenter use.

Requirements and overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

PLM00013 11.2 Windows Server Installation

Chapter 1: Requirements and overview

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Where to find system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
System hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Web tier support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Teamcenter help requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Software integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Locate Teamcenter distribution images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Create the Teamcenter administrative user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

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-10
Corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Additional servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Teamcenter network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
File Management System (FMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
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

PLM00013 11.2 Windows Server Installation

Chapter 1: Requirements and overview

System requirements

Where to find system requirements

For versions of system software and hardware certified for running Teamcenter on your platform, see
the Siemens PLM Software certifications page on GTAC:
http://www.plm.automation.siemens.com/locale/support/gtac/certifications.shtml
This site lists certified software versions for:
• Operating systems
• Databases
• C++ compilers
• Web servers
• Java
• Other third-party software
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 11.2 servers and clients are supported on your
operating system. Bullet characters (•) denote supported servers and clients.

Platform support for Teamcenter servers and clients

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

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 7 and Windows 8.
3. Microsoft Windows server platforms include Windows Server 2008 and Windows Server 2012.

PLM00013 11.2 Windows Server Installation 1-1

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

Platform support for Teamcenter servers and clients

Business
Modeler
Corporate Web Rich Thin IDE
Operating system server tier client client client TCCS1
Oracle Solaris • •
IBM AIX • •
SUSE Linux • • • • • •
Red Hat Linux4 • • • • • •
Apple Macintosh Mac OS • •

Notes about platform support

General notes
• The hardware and software certifications page on GTAC lists supported operating system
versions.

• For information about tuning operating system performance for Teamcenter 11.2, see the
Teamcenter Deployment Guide in the Documentation page on the GTAC support site.

• 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.
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,

4. Only 64-bit Red Hat Linux is supported.

1-2 Windows Server Installation PLM00013 11.2

 Requirements and overview

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.

• 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.

Related topics

• UNIX and Linux Server Installation

• Windows Client Installation

• Linux Client Installation

• Macintosh Client Installation

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.

• 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.
Installation of the two-tier rich client is described in the client installation guides for Windows
and 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.

PLM00013 11.2 Windows Server Installation 1-3

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

Required hard disk space for Teamcenter configurations

Corporate Two-tier
Platform server rich client Web tier
IBM AIX 2.0 GB Not supported 3 GB
SUSE Linux 2.0 GB 300 MB 3 GB
Red Hat Linux 2.0 GB 300 MB 3 GB
Oracle 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 one of the following supported database
systems:
• IBM DB2

• Oracle

• Microsoft SQL Server

The hardware and software certifications site on GTAC lists supported database versions. If your
database server is not a supported version, upgrade your database server to a supported version
before you install Teamcenter.
Choose a database management system that suits the platforms of your Teamcenter servers and
clients, and make sure your Teamcenter corporate server host has access to the database server.
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 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.

Java Runtime Environment

Teamcenter Environment Manager (TEM) requires a supported Java Runtime Environment (JRE).
Download and install a certified JRE before you install Teamcenter. For certified JRE versions, see
the hardware and software certifications page on GTAC.
Before you launch TEM to install Teamcenter, set the JRE64_HOME environment variable to the
location of a supported 64-bit Java JRE. After installation is complete, TEM no longer requires
this variable.
TEM verifies the JRE version during launch and cancels installation if a certified JRE is not available
on the host.

1-4 Windows Server Installation PLM00013 11.2

 Requirements and overview

Note

Alternatively, you can specify the Java JRE location by one of the following methods:
• Set the JRE_HOME environment variable to the location of a supported 64-bit Java JRE.

• Launch TEM in a command prompt using the -jre argument to specify the location of a
supported 64-bit Java JRE:
tem -jre JRE-path

For example:
tem -jre c:\apps\jre1.7

Web browser
A web browser is required if you use the following:
• Teamcenter online help
• Teamcenter thin client
• Over-the-Web Installer5

For these products, Teamcenter supports the following web browsers:

• Windows systems: Microsoft Internet Explorer and Mozilla Firefox
• Linux systems: Mozilla Firefox
• Macintosh systems: Apple Safari
Note

Teamcenter online help is also supported on Google Chrome on all supported platforms.

The hardware and software certifications page on GTAC lists supported browser versions.

Web tier support

Install the required software for the Teamcenter web tier you use:
• Java EE web tier
Java Runtime Environment (JRE)
Install a supported JRE on the host where you build Teamcenter web applications.
Java EE 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 and add the required role services.

5. The Over-the-Web Installer can be used to install the Teamcenter four-tier rich client and Teamcenter Microsoft Office interfaces.

PLM00013 11.2 Windows Server Installation 1-5

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

Microsoft .NET framework

Install the .NET framework on all Teamcenter hosts.

The hardware and software certifications page on GTAC lists supported versions of these products.
Note

Some web application servers require special configuration for use with Teamcenter.

Teamcenter help requirements

The Siemens PLM Documentation Server requires a supported 64-bit Java Runtime Environment
(JRE) on the PLM Documentation Server host. The PLM Documentation Server does not support
32-bit Java.
Make sure the JAVA_HOME system environment variable points to a 64-bit JRE on the PLM
Documentation Server host.
If you deploy Teamcenter help in an existing web server, you must have a supported web server with
a servlet container. This can be Apache Tomcat, Jetty, or any web server listed on the hardware and
software certifications page on GTAC. .
Viewing Teamcenter help requires a supported web browser.
Viewing Teamcenter PDF help files requires a PDF reader or web browser plug-in.
For information about supported web browsers and Java versions, see the hardware and software
certifications page on GTAC.

Software integrations
If you use Teamcenter integrations to other Siemens PLM Software products or third-party software,
install those products before you install Teamcenter.
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.6

Locate Teamcenter distribution images

Locate the Teamcenter software and documentation distribution images and make sure they are
accessible to your host.
From the download page on GTAC, download the Teamcenter software distribution files for Windows:
Tcversion_win64_1_of_2.zip
Tcversion_win64_2_of_2.zip

Expand both ZIP files for your platform to a common directory to assemble the full software
distribution before you begin installation.

6. Installation of the Siemens PLM Software Common Licensing Server is described in the server installation guides for Windows and
UNIX/Linux.

1-6 Windows Server Installation PLM00013 11.2

 Requirements and overview

In addition, download the rich client over-the-web distribution image (Tcversion_otw.zip) from the
GTAC download page.
Note

• Use a commercial unzip utility such as 7-Zip to expand files.

• Contents of Teamcenter distribution images are described in Teamcenter distribution

media.

Create the Teamcenter administrative user account

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.

Teamcenter installation tools

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

PLM00013 11.2 Windows Server Installation 1-7

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

Teamcenter Environment Manager

Teamcenter Environment Manager also performs maintenance operations, such as upgrading
servers, applying service packs, and installing patches.
You launch Teamcenter Environment Manager using the tem.bat command.

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

Web Application Manager

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

1-8 Windows Server Installation PLM00013 11.2

 Requirements and overview

Web Application Manager

You launch the Web Application Manager by entering the insweb command. The Web Application
Manager allows you to create 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 files7 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. .
Note

The .NET web tier is installed using Teamcenter Environment Manager, not the Web
Application Manager.

Basic concepts about Teamcenter installation

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

7. A deployable file is a web archive (WAR) file.

PLM00013 11.2 Windows Server Installation 1-9

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

to a database server or a database client. Teamcenter supports IBM DB2, Oracle, and Microsoft
SQL Server databases.
For configuration settings and tuning methods to optimize Teamcenter performance with Oracle
or Microsoft SQL Server, 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 database performance issues and diagnosis, and configuration and tuning
guidelines.
Note

Teamcenter servers and two-tier rich clients on Linux hosts cannot connect to Microsoft SQL
Server database servers.

Teamcenter servers

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 Teamcenter Extensions for Microsoft Office.
• Rich client
The rich client is a platform-independent client implementation (Java application) for users who
interact with Teamcenter frequently. It is extendable to run standard Teamcenter and customized
applications.
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 the 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 architecture.

1-10 Windows Server Installation PLM00013 11.2

 Requirements and overview

Teamcenter network architectures

Two-tier architecture
The two-tier architectural model comprises the following tiers:
• Client tier
The client tier comprises the Teamcenter rich clients.
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.

• Resource tier
The resource tier comprises a database server, database, volumes, and file servers.

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.

PLM00013 11.2 Windows Server Installation 1-11

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

Two-tier deployment

Related topics

• File Management System (FMS)

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.)

• Java EE web tier

The Java EE web tier is a Java application that runs in a Java Enterprise Edition (Java EE)
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 hardware
and software certifications page on GTAC.

• Enterprise tier

1-12 Windows Server Installation PLM00013 11.2

 Requirements and overview

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 Java EE 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.

Four-tier architecture

PLM00013 11.2 Windows Server Installation 1-13

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

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 Java EE 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 Java EE based server manager
and the web tier application.8
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 Java EE 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.

8. This is not required if you use the .NET web tier and the .NET based server manager.

1-14 Windows Server Installation PLM00013 11.2

 Requirements and overview

Four-tier deployment (enterprise and web tiers on same host)

PLM00013 11.2 Windows Server Installation 1-15

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

Four-tier deployment (enterprise and web tiers on separate hosts with HTTP server)

1-16 Windows Server Installation PLM00013 11.2

 Requirements and overview

Four-tier deployment (multiple enterprise tier hosts and web tier hosts)

PLM00013 11.2 Windows Server Installation 1-17

 Chapter
Chapter 1: 1: Requirements
Requirements and overview
and overview

Four-tier deployment (load balancing)

1-18 Windows Server Installation PLM00013 11.2

 Requirements and overview

Related topics
• Rich client installation

File Management System (FMS)

File Management System (FMS) is a file storage, caching, distribution, and access system. FMS
provides global, secure, high-performance and scalable file management. Use FMS to centralize
data storage volumes on reliable backup file servers, while keeping data close to users in shared
data caches. This enables centralized storage and wide distribution of file assets to the needed
locations within a single standard file management system. FMS provides WAN acceleration to
effectively move large files across WAN assets.
Teamcenter client installation programs installs FMS executables and an FMS client cache (FCC) on
client hosts and sets the FMS_HOME environment variable in the user environment.
FMS downloads files to client hosts from Teamcenter volumes and uploads files from client hosts to
Teamcenter volumes. FMS_HOME points to the location of the FMS executables on the client host.
All Teamcenter clients installed on a host use the FMS executables defined in FMS_HOME.
If other users on a client host want to use the same installed client environment, they must manually
set FMS_HOME in their user environments. Using the same installed environment shares only the
binaries and run-time content; the file cache contents remain private to the user.

Selecting and configuring features

If you install the rich client using Teamcenter Environment Manager (TEM), you can select features in
the Features panel. For a description of any feature, point to that feature in the list.

Basic tasks in Teamcenter installation

Installing a database server

Install one of the following supported database servers:
• IBM DB2

• Oracle

• Microsoft SQL Server

Installing a Teamcenter server

Install one or more Teamcenter servers.

Installing the web tier

Install the .NET web tier or the Java EE web tier.

Installing Teamcenter clients

Install Teamcenter clients on Windows, Linux, or Macintosh hosts.

PLM00013 11.2 Windows Server Installation 1-19

Chapter 2: Site planning

Installing Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Teamcenter help overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Install the Siemens PLM Documentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Install Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Configuring online help during Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Installing localized online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Configuring language support for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Teamcenter localizations provided by Siemens PLM Software . . . . . . . . . . . . . . . . . . . . 2-11
Choose the character set for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Verify that your locale is supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Configuring a UTF-8 environment for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Overview of UTF-8 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Configure UTF-8 environment settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Configuring a non-UTF-8 environment for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Installation and deployment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Planning the Teamcenter network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Installing Teamcenter components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Thin client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
File Management System installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
FMS installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Installing File Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Creating volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Lifecycle Visualization installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Global Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Remote workflow installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Security Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36

Oracle server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
MS SQL server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Network environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Homogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Heterogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Required operating system and user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

PLM00013 11.2 Windows Server Installation

Chapter 2: Site planning

Installing Teamcenter help

Teamcenter help overview
Siemens PLM Software provides two sources of online help for Teamcenter:
• GTAC Documentation site
GTAC site that hosts online help for Teamcenter and other Siemens PLM Software products. A
WebKey account is required to access this site.
Teamcenter online help is available on the GTAC Documentation site at:

https://support.industrysoftware.automation.siemens.com/docs/teamcenter/

• Siemens PLM Documentation Server

Web application installed on your local host or intranet. The PLM Documentation Server can host
online help for multiple languages and multiple Siemens PLM Software products.

When deployed on your local intranet, the PLM Documentation Server can host online help for multiple
languages and multiple Siemens PLM Software products. It provides a fast, powerful, server-based
search engine and significantly improved overall performance over previous Teamcenter help.

PLM00013 11.2 Windows Server Installation 2-1

 Chapter
Chapter 2: 2: Site planning
Site planning

Teamcenter online help on the PLM Documentation Server

The PLM Documentation Server contains a dedicated Jetty web server and Solr search engine and is
independent of the Teamcenter web tier, so you can install online help before you begin Teamcenter
installation. All Teamcenter help features can be installed on a single PLM Documentation Server,
and you can add localized Teamcenter help and also help for other Siemens PLM Software products
you use.

2-2 Windows Server Installation PLM00013 11.2

 Site planning

Siemens PLM Documentation Server

Installing Teamcenter help on your local network requires two steps:

1. Installing the PLM Documentation Server.

2. Installing Teamcenter documentation.

After you install Teamcenter documentation, you can configure online help access for Teamcenter
clients during Teamcenter installation or after installation. Teamcenter clients can then access help on
the PLM Documentation Server through the client Help menus.

Rich client help menu Thin client help menu

PLM00013 11.2 Windows Server Installation 2-3

 Chapter
Chapter 2: 2: Site planning
Site planning

Note

• The Teamcenter PDF help collection and the Teamcenter developer references are not
accessible though Teamcenter client Help menus.

• Teamcenter documentation cannot be accessed through a drive letter or UNC path

(\\host-name). It is viewed only in a web browser using HTTP or HTTPS protocol.

If you use Teamcenter documentation in multiple languages, you can install all languages on the
same PLM Documentation Server. The PLM Documentation Server displays the appropriate
language according to each user's web browser language settings.
Before you install Teamcenter help, make sure your host meets PLM Documentation Server
requirements.

Additional Teamcenter documentation

The following documentation deliverables are provided by Teamcenter but are not installed in the
PLM Documentation Server:
• Teamcenter Client for Microsoft Office
The Teamcenter Client for Microsoft Office contains its own online help, which is displayed in
Microsoft Office.

• Business Modeler IDE online help

The Business Modeler IDE client contains its own online help, which is displayed in the Business
Modeler IDE.

• Teamcenter Data Model Report

The Teamcenter Data Model Report is a report of all standard Teamcenter data model
elements. The report is provided in the Teamcenter documentation distribution image. To view
the data model report, expand the DataModelReport.zip file to a local directory and open
help\en_US\custom\DataModelReport\index.html.

Install the Siemens PLM Documentation Server

1. In the Teamcenter documentation distribution image, browse to the splmdocserver\wntx64
directory and double-click the setup.exe program icon.
This launches the Siemens PLM Documentation Server installation wizard.

2. Select a language for the installation user interface, and then click OK.
The wizard displays the welcome dialog box.

2-4 Windows Server Installation PLM00013 11.2

 Site planning

3. Proceed to the Destination Folder dialog box. Accept the default destination folder (C:\Program
Files\Siemens\PLM Documentation Server\), or click Change to enter a different folder.

4. Proceed to the Ready to Install the Program dialog box. Accept the default port for the PLM
Documentation Server (8181), or click Change Port to specify a different port.

5. Click Install to begin installing the PLM Documentation Server.

6. In the InstallShield Wizard Completed dialog box, click Finish to exit the wizard.
Note

For additional information about installing the PLM Documentation Server, including
advanced installation options, see the splmdocserver_install.pdf document in the
splmdocserver\wntx64 directory in the documentation distribution image.

Stopping and starting the Siemens PLM Documentation Server

The PLM Documentation Server starts automatically when installation is complete and whenever
you restart Windows. If necessary, you can stop or start the Siemens PLM Documentation Server
service in the Services dialog box in the Windows Control Panel.

Install Teamcenter online help

Teamcenter provides three online help collections, installable as features in the Teamcenter
documentation installer:
• Teamcenter online help

PLM00013 11.2 Windows Server Installation 2-5

 Chapter
Chapter 2: 2: Site planning
Site planning

Provides the Teamcenter help library. This collection can be accessed from Teamcenter client
Help menus.

• Teamcenter developer references

Contains developer references for Teamcenter customization:

o C++ API Reference

o Integration Toolkit (ITK) Function Reference
o Services Reference

• Teamcenter PDF online help

Provides the Teamcenter help library in PDF format.
Note

You must install the Siemens PLM Documentation Server before you install online help.

1. In the Teamcenter documentation distribution image, double-click the tchelp.exe program icon
to launch the Teamcenter documentation installation wizard.

2. Select a language for the installation user interface, and then click OK.
The wizard displays the Introduction dialog box.

3. Proceed to the Choose Install Set dialog box. Select an option:

• Typical installs the Teamcenter online help library.

2-6 Windows Server Installation PLM00013 11.2

 Site planning

• Custom installs the Teamcenter online help library and allows you to add the following
help features:

o Teamcenter PDF help collection

o Teamcenter developer references.1

Note

You can also add help features later using the maintenance options provided by the
Teamcenter documentation installer.

4. If you chose the Custom option, select the additional features you want to install.

5. Proceed to the Pre-Installation Summary dialog box. If you are satisfied with your selections,
click Install to begin installing Teamcenter documentation.

The Teamcenter documentation installer installs Teamcenter help into the PLM Documentation
Server and updates the online help search database.

6. When installation is complete, the Teamcenter documentation installer displays the Online
Help Locations dialog box.

Record the Teamcenter Online Help URL. You use this URL to configure online help access for
Teamcenter clients.

1. Developer references include the C++ API Reference, the Integration Toolkit (ITK) Function Reference, and the Services Reference.

PLM00013 11.2 Windows Server Installation 2-7

 Chapter
Chapter 2: 2: Site planning
Site planning

If you install additional help features, bookmark the URLs for those help collections and provide
them to users in your Teamcenter network.
Online help URLs are based on the host and port of the PLM Documentation Server and the
Teamcenter version or SP level.

Help feature URL Example

Teamcenter online help http://host:port/tdoc/tc/version/help/ http://myhost:8181/tdoc/tc/11.2/help/
Teamcenter developer references http://host:port/tdoc/tc/version/tcrefs/ http://myhost:8181/tdoc/tc/11.2/tcrefs/
Teamcenter PDF online help http://host:port/tdoc/tc/version/PDF/ http://myhost:8181/tdoc/tc/11.2/PDF/

Note

Help URLs are valid only for help features that are installed.

7. Click Next to proceed to the Install Complete dialog box. Then, click Done to exit the installer.

Adding online help features

You can add help features after installation by launching the Teamcenter documentation installer in
maintenance mode.
1. In the Add or Remove Programs dialog box in the Windows Control Panel, right-click Siemens
Teamcenter version Documentation and choose Uninstall/Change.

2. Select the Add Features or Remove Features option in the Teamcenter documentation installer.

Configuring online help during Teamcenter installation

During Teamcenter installation, enter the online help URL to enable Help menu options in Teamcenter
clients.
• Teamcenter Foundation
Teamcenter Foundation settings supply the online help URL to the thin client and to four-tier
rich clients installed through TEM.
TEM displays the Foundation Settings panel during installation of Teamcenter Foundation.
In the Foundation Settings panel:

1. Click the Advanced button .

2. Click the Online Help tab.

2-8 Windows Server Installation PLM00013 11.2

 Site planning

3. Select the Enable Online Help check box.

4. In the PLM Document Server URL box, type the Teamcenter online help URL.

• Two-tier rich client

For the two-tier rich client, the online help URL is supplied by the Rich Client Settings panel in
TEM. During two-tier rich client installation, select the Enable Online Help check box, and
then type the online help URL in the Web server URL box.

• Rich client distribution instance

For rich clients installed using the Over-the-Web Installer, the online help URL is supplied by
context parameters in the rich client distribution instance.

When you create the rich client distribution instance, type values for the following context
parameters.

PLM00013 11.2 Windows Server Installation 2-9

 Chapter
Chapter 2: 2: Site planning
Site planning

Context parameter Value

RichClientHelpWebServer http://host:port/tdoc/tc/version
host and port are the host name and port of the PLM
Documentation Server. version is the Teamcenter version
or SP level.
RichClientHelpLocation /help
This is the subpath to the Teamcenter online help.

Installing localized online help

You can install localized (non-English) online help using the same process as for installing English
online help.
Download the localized documentation distribution image for the language you want to install. In that
image, launch the tchelp.exe program.
In the Choose Install Set dialog box, the list of help features shows the language of the Teamcenter
documentation you are installing, for example:

2-10 Windows Server Installation PLM00013 11.2

 Site planning

Note

You must install the Siemens PLM Documentation Server before you install online help. The
Siemens PLM Documentation Server installer is provided only in the English documentation
distribution image. It is not provided in localized documentation distribution images.
The Teamcenter online help library and the Teamcenter PDF help collection are localized for
all supported locales. The Teamcenter developer references are available in English only.

Viewing localized online help

The PLM Documentation Server displays localized Teamcenter help according to the language
settings in your web browser.
When you open a Teamcenter help collection, the PLM Documentation Server detects your web
browser's language settings. For example, if your browser is configured to display in German, the
PLM Documentation Server determines whether the German version of the current collection is
installed, and if so, it displays the German version of the content. If the German version is not
installed, the PLM Documentation Server displays the default (English) help collection.
If you have multiple languages configured in your web browser, the PLM Documentation Server
chooses the first available help collection it finds from the list of preferred languages in the web
browser settings.
For information about configuring language settings in your web browser, see your web browser
documentation.

Configuring language support for Teamcenter

Teamcenter localizations provided by Siemens PLM Software
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
Italian it_IT
Japanese ja_JP
Korean ko_KR
Polish pl_PL
Portuguese (Brazilian) pt_BR
Russian ru_RU
Spanish es_ES

PLM00013 11.2 Windows Server Installation 2-11

 Chapter
Chapter 2: 2: Site planning
Site planning

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

Localizing Teamcenter in Hebrew

Siemens PLM Software does not provide a Hebrew translation but provides recommended
configuration settings for Hebrew locales. In Hebrew locales, set the locale code to en_US. This
allows data entry in Hebrew, but user interface text is in English.

Choose the character set for Teamcenter

Choosing the correct character set for Teamcenter and the Teamcenter database is critical. If a
Teamcenter client user enters a character that is not recognized by the Teamcenter database, the
character is misinterpreted or corrupted when the user's data is checked into the Teamcenter
database.
Determine the character set your Teamcenter network requires based on the following considerations.

Language support

Determine the languages you must support, considering both initial needs and future needs. If you
support one language currently but anticipate supporting additional languages in the future, choose
a character set that accommodates those future requirements.
Some character sets support groups of languages. The standard localizations provided with
Teamcenter support the following language groups:
• Western European:
English
French
German
Italian
Portuguese (Brazilian)
Spanish

• Eastern European:
Czech
Polish

• Japanese: Japanese

• Chinese (Simplified): Chinese (Simplified)

• Chinese (Traditional): Chinese (Traditional)

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.

2-12 Windows Server Installation PLM00013 11.2

 Site planning

• Korean: Korean

• Russian: Russian

If your current and future language support requirements are within a single language group, you
can choose a non-UTF-8 character set for your Teamcenter network. But, if your language support
requirements extend beyond a single language group, you must choose the UTF-8 character set.
For example, if all your Teamcenter hosts run in western European locales, you may choose a
non-UTF-8 character set or UTF-8. If you have hosts running in western European and Japanese
locales, you must choose UTF-8.
The UTF-8 character set supports all languages supported by standard Teamcenter.

Character support
Determine what special or extended characters you must support in Teamcenter data, and choose a
character set that supports them. For example:
En dash (–) or em dash (—)
These characters are part of Windows 1252 code page, but not part of the ISO8859_1 character
set. However, the UTF-8 character set supports these characters.
Currency symbols such as the euro (€)
This symbol is in the we8iso8859p15 character set, but not in the we8iso8859p1 character set.

Platform and database

• Platform
Choose a character set that accommodates the platforms in your Teamcenter network. For
example, if your Teamcenter server is a Linux host but your client hosts are Windows, and you
use default character sets on each, data corruption can result because the default character sets
for these platforms are not compatible. Choose a character set supported on both platforms.
The UTF-8 character set accommodates all platforms Teamcenter supports.

• Database
Teamcenter supports only the UTF-8 character set with IBM DB2 databases. If your database is
IBM DB2, your Teamcenter database must be UTF-8.
Oracle supports UTF-8 and non-UTF-8 character sets on all platforms.
Microsoft SQL Server does not provide native support for UTF-8. However, you can configure
Teamcenter to use UTF-8 with a Microsoft SQL Server database. The Enable UTF-8 option in
Teamcenter Environment Manager (TEM) enables the Teamcenter server to convert character
encoding to and from UTF-8 when interacting with the database.

Verify that your locale is supported

If you do not use UTF-8, ensure the locale you want to use is supported on your host. Perform the
following steps to set the Windows system locale and install the required language packs:
1. Open the Regional and Language Options dialog box in the Windows Control Panel.

PLM00013 11.2 Windows Server Installation 2-13

 Chapter
Chapter 2: 2: Site planning
Site planning

2. In the Languages tab, set the required language for the menus and dialog boxes.

3. In the Region and Language dialog box, click the Administrative tab.

4. Under Language for non-Unicode programs, click Change system locale.

5. In the Region and Language Settings dialog box, verify the correct locale (language and
country) is selected. If not, choose the correct locale.

6. Close all dialog boxes and restart your system to install and configure the required language pack.

Configuring a UTF-8 environment for Teamcenter

Overview of UTF-8 configuration

Teamcenter supports the Unicode UTF-8 character set on Windows, UNIX, and Linux hosts that are
configured to process UTF-8.
Set the required values for your platform, locale, and database type before you begin installing
Teamcenter.
Enable UTF-8 support for Teamcenter servers and clients during Teamcenter installation:
• Teamcenter servers
With UTF-8 support configured on your host, Teamcenter Environment Manager (TEM) can
create a UTF-8-enabled Teamcenter database during Teamcenter installation.
If you use Microsoft SQL Server, select the Enable UTF-8 option in the Foundation Database
panel in TEM.

• Two-tier rich client

If the Teamcenter database is configured for the UTF-8 character set, UTF8 is selected by default
in the TcServer Character Encoding Settings panel in TEM.

• Four-tier rich client

When installing the Teamcenter web tier, in the TcServer Character Encoding Settings panel
in TEM, select UTF8.
The four-tier rich client can run on any platform (Windows, UNIX, or Linux) running any language
character set.
Make sure you set the system locale and install the appropriate fonts to ensure correct character
display.

• Thin client
Make sure UTF-8 support is configured on the web tier host.
The thin client can run on any platform (Windows, UNIX, or Linux) running any language
character set. The Teamcenter web tier converts client character encoding to and from UTF-8
as it passes through the web tier.

2-14 Windows Server Installation PLM00013 11.2

 Site planning

The following example shows a Teamcenter configuration for restricted Unicode UTF-8 character
set support with clients displaying multiple locales. Servers in this configuration run a Unicode
UTF-8 character set operating system.
On Windows platforms, if the database is configured for the UTF-8 character set, the Teamcenter
server operates in UTF-8 mode independent of the system locale.

Unicode homogeneous server platform configuration

PLM00013 11.2 Windows Server Installation 2-15

 Chapter
Chapter 2: 2: Site planning
Site planning

Note

• Teamcenter does not support Unicode Supplementary Characters.3

• If you import translated content in languages that require multibyte characters, such as
Russian and Chinese Simplified, you must configure your Teamcenter installation to
support the UTF-8 character set to ensure that titles and other properties on this content
display correctly in your environment.

Configure UTF-8 environment settings

If you use UTF-8, select the appropriate database character set when you install your database server.

Database vendor Database character set

Oracle al32utf8 or utf84
IBM DB2 utf8

For Microsoft SQL Server, no special setting is needed during database server installation. If you
select the Enable UTF-8 option in TEM (in the Foundation Database panel), the Teamcenter server
converts character encoding to and from UTF-8. This allows Teamcenter to use UTF-8 with Microsoft
SQL Server's (non-UTF-8) internal encoding.5
In Hebrew locales, set the following additional variables:
1. In the TC_DATA/tc_profilevars file, set TC_XML_ENCODING to UTF-8.

2. In two-tier environments, set TC_CHARACTER_ENCODING_SET to UTF8 in the following files:

• TC_ROOT/iiopservers/Start_TcServer1
• TC_ROOT/pool_manager/mgrstartMYDB

Do not set the TC_XML_ENCODING or TC_CHARACTER_ENCODING_SET environment variables

in the system environment. TEM sets these values in the Teamcenter configuration.

Configuring a non-UTF-8 environment for Teamcenter

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.

3. Unicode Supplementary Characters are characters in the Unicode Character Standard outside of the Basic Multilingual Plane (BMP),
that is, characters with codepoint values larger than 0xFFFF.
4. Oracle recommends al32utf8. UTF8 supports only supports Unicode Version 3.0 and earlier.
5. Microsoft SQL Server does not provide native support for UTF-8 character set encoding.

2-16 Windows Server Installation PLM00013 11.2

 Site planning

Environment settings on non-UTF-8 systems

Value
Locale Setting IBM AIX Oracle Solaris Linux Microsoft Windows
Chinese Database character zhs16cgb231280 or zhs16cgb231280 or zhs16cgb231280 or zhs16cgb231280 or
(Simplified), set (Oracle) zhs16gbk zhs16gbk zhs16gbk zhs16gbk
GB2312-80
Database collation N/A N/A N/A chinese_prc_bin
encoding
(MS SQL Server)1
LANG and zh_CN zh zh_CN N/A
LC_ALL2
Chinese Database character zhs16cgb231280 or zhs16cgb231280 or zhs16cgb231280 or zhs16cgb231280 or
(Simplified), GBK set (Oracle) zhs16gbk zhs16gbk zhs16gbk zhs16gbk
encoding
Database collation N/A N/A N/A chinese_prc_bin
(MS SQL Server)1
LANG and Zh_CN.GB18030 zh_CN.GB18030 zh_CN.gb18030 N/A
LC_ALL2
Chinese Database character zht16big5 or zht16big5 or zht16big5 or zht16big5 or
(Traditional) set (Oracle) zht16mswin950 zht16mswin950 zht16mswin950 zht16mswin950
Database collation N/A N/A N/A chinese_taiwan_stroke_bin
(MS SQL Server)1
LANG and Zh_TW.big5 zh_TW.BIG5 zh_TW N/A
LC_ALL2
Czech Database character ee8mswin1250 ee8mswin1250 ee8mswin1250 ee8mswin1250
set (Oracle)
Database collation N/A N/A N/A czech_bin
(MS SQL Server)1
LANG and cs_CZ.ISO8859-2 cs_CZ.ISO8859-2 cs_CZ N/A
LC_ALL2
English Database character we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or
set (Oracle) we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or
we8mswin12524 we8mswin12524 we8mswin12524 we8mswin12524
Database collation N/A N/A N/A latin1_general_bin
(MS SQL Server)1
LANG and en_US.ISO8859-1 en_US.iso88591 or en_US or N/A
LC_ALL2 or en_US.ISO8859-15 en_US.iso885915
en_US.ISO8859-15
French Database character we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or
set (Oracle) we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or
we8mswin12524 we8mswin12524 we8mswin12524 we8mswin12524
Database collation N/A N/A N/A latin1_general_bin
(MS SQL Server)1

Notes:

1. The database collation you select during Microsoft SQL Server installation determines the database character set.
2. Set LANG and LC_ALL in the system environment variables. These variables must have identical values to function properly.
3. we8iso8859p15 contains additional characters, including the euro symbol (€).
4. we8mswin1252 contains more characters than ISO-8859-15.
5. No ISO-8859-15 equivalent is available for this locale.
6. Siemens PLM Software does not provide a Hebrew translation. The configuration settings shown allow data entry in Hebrew,
but user interface text is in English.

PLM00013 11.2 Windows Server Installation 2-17

 Chapter
Chapter 2: 2: Site planning
Site planning

Environment settings on non-UTF-8 systems

Value
Locale Setting IBM AIX Oracle Solaris Linux Microsoft Windows
LANG and fr_FR.ISO8859-15 fr_FR.ISO8859-1 or fr_FR5 N/A
LC_ALL2 fr_FR.ISO8859-15
German Database character we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or
set (Oracle) we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or
we8mswin12524 we8mswin12524 we8mswin12524 we8mswin12524
Database collation N/A N/A N/A latin1_general_bin
(MS SQL Server)1
LANG and de_DE.ISO8859-15 de_DE.iso88591 or de_DE5 N/A
LC_ALL2 de_DE.ISO8859-15
Hebrew Database character iw8iso8859p8 or iw8iso8859p8 or iw8iso8859p8 or iw8iso8859p8 or
set (Oracle) iw8mswin1255 iw8mswin1255 iw8mswin1255 iw8mswin1255
Database collation N/A N/A N/A hebrew_bin
(MS SQL Server)1
LANG and HE_IL.UTF-8 he_IL.UTF-8 iw_IL.utf8
N/A
LC_ALL2
Italian Database character we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or
set (Oracle) we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or
we8mswin12524 we8mswin12524 we8mswin12524 we8mswin12524
Database collation N/A N/A N/A latin1_general_bin
(MS SQL Server)1
LANG and it_IT.ISO8859-15 it_IT.ISO8859-1 or it_IT5 N/A
LC_ALL2 it_IT.ISO8859-15
Japanese (EUC) Database character ja16euc ja16euc ja16euc ja16euc
set (Oracle)
Database collation N/A N/A N/A N/A
(MS SQL Server)1
LANG and ja_JP.IBM-eucJP ja_JP.eucJP ja_JP.eucjp N/A
LC_ALL2
Japanese (Shift-JIS) Database character ja16sjis ja16sjis ja16sjis ja16sjis
set (Oracle)
Database collation N/A N/A N/A japanese_bin
(MS SQL Server)1
LANG and Ja_JP.PCK ja_JP.SJIS ja_JP.PCK
N/A
LC_ALL2
Korean Database character ko16ksc5601 ko16ksc5601 ko16ksc5601 ko16ksc5601
set (Oracle)
Database collation N/A N/A N/A korean_wansung_bin
(MS SQL Server)1

Notes:

1. The database collation you select during Microsoft SQL Server installation determines the database character set.
2. Set LANG and LC_ALL in the system environment variables. These variables must have identical values to function properly.
3. we8iso8859p15 contains additional characters, including the euro symbol (€).
4. we8mswin1252 contains more characters than ISO-8859-15.
5. No ISO-8859-15 equivalent is available for this locale.
6. Siemens PLM Software does not provide a Hebrew translation. The configuration settings shown allow data entry in Hebrew,
but user interface text is in English.

2-18 Windows Server Installation PLM00013 11.2

 Site planning

Environment settings on non-UTF-8 systems

Value
Locale Setting IBM AIX Oracle Solaris Linux Microsoft Windows
LANG and ko_KR.IBM-eucKR ko_KR.eucKR ko_KR.EUC N/A
LC_ALL2
Polish Database character ee8mswin1250 ee8mswin1250 ee8mswin1250 ee8mswin1250
set (Oracle)
Database collation N/A N/A N/A polish_bin
(MS SQL Server)1
LANG and pl_PL.ISO8859-2 pl_PL.iso88592 pl_PL.ISO8859-2 N/A
LC_ALL2
Portuguese Database character we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or
(Brazilian) set (Oracle) we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or
we8mswin12524 we8mswin12524 we8mswin12524 we8mswin12524
Database collation N/A N/A N/A latin1_general_bin
(MS SQL Server)1
LANG and pt_BR.ISO8859-15 pt_BR.ISO8859-1 pt_BR5 N/A
LC_ALL2 or
pt_BR.ISO8859-15
Russian Database character cl8mswin1251 or cl8mswin1251 or cl8mswin1251 or cl8mswin1251 or
set (Oracle) cl8iso8859p5 cl8iso8859p5 cl8iso8859p5 cl8iso8859p5
Database collation N/A N/A N/A cyrillic_general_bin
(MS SQL Server)1
LANG and ru_RU.ISO8859-5 ru_RU.ISO8859-5 ru_RU N/A
LC_ALL2
Spanish Database character we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or we8iso8859p1 or
set (Oracle) we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or we8iso8859p153 or
we8mswin12524 we8mswin12524 we8mswin12524 we8mswin12524
Database collation N/A N/A N/A latin1_general_bin
(MS SQL Server)1
LANG and es_ES.ISO8859-15 es_ES.ISO8859-1 es_ES5 N/A
LC_ALL2 or
es_ES.ISO8859-15

Notes:

1. The database collation you select during Microsoft SQL Server installation determines the database character set.
2. Set LANG and LC_ALL in the system environment variables. These variables must have identical values to function properly.
3. we8iso8859p15 contains additional characters, including the euro symbol (€).
4. we8mswin1252 contains more characters than ISO-8859-15.
5. No ISO-8859-15 equivalent is available for this locale.
6. Siemens PLM Software does not provide a Hebrew translation. The configuration settings shown allow data entry in Hebrew,
but user interface text is in English.

In Hebrew locales, set the following additional variables:

1. In the TC_DATA/tc_profilevars file, set TC_XML_ENCODING to ISO-8859-8.

2. In two-tier environments, set TC_CHARACTER_ENCODING_SET to ISO8859_8 in the following

files:
• TC_ROOT/iiopservers/Start_TcServer1
• TC_ROOT/pool_manager/mgrstartMYDB

PLM00013 11.2 Windows Server Installation 2-19

 Chapter
Chapter 2: 2: Site planning
Site planning

Do not set the TC_XML_ENCODING or TC_CHARACTER_ENCODING_SET environment variables

in the system environment. TEM sets these values in the Teamcenter configuration.
Note

Teamcenter supports only the UTF-8 character set with IBM DB2 databases.

Installation and deployment overview

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.
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, or TC_ROOT. The TC_ROOT
environment variable in Teamcenter configuration files 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, or TC_DATA. The TC_DATA environment variable in
Teamcenter configuration files contains 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.

2-20 Windows Server Installation PLM00013 11.2

 Site planning

Network node Role

• 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.6
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 Teamcenter
server 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.

The following table describes additional network nodes you can include in your network.

Network node Role

Multi-Site Collaboration Network node that runs a daemon process to publish data objects within
ODS server a Multi-Site Collaboration environment. 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.

6. Teamcenter provides server managers based on the Java EE and the Microsoft .NET platforms. Install the appropriate server manager
for the web tier you use.

PLM00013 11.2 Windows Server Installation 2-21

 Chapter
Chapter 2: 2: Site planning
Site planning

Network node Role

Multi-Site Collaboration Network node running daemon processes that perform proxy services
ODS proxy server for ODS servers within a Multi-Site 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 Collaboration Network node running a daemon process that transfers data objects
IDSM server among databases (sites) in a Multi-Site 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 Collaboration Network node running daemon processes that perform proxy services
IDSM proxy server for IDSM servers.
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.
Quick part locator (QPL) Component of Repeatable Digital Validation (RDV). The QPL server
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

Two-tier architecture installation

The primary components of a two-tier installation require three general installation tasks:
1. Install the database server using IBM DB2, Oracle, or MS SQL Server tools.

2. Install Teamcenter executables and files, create and/or populate the database, and configure a
volume using Teamcenter Environment Manager.

2-22 Windows Server Installation PLM00013 11.2

 Site planning

3. Install the rich client on a Windows or Linux client workstation using Teamcenter Environment
Manager.

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 installation software(IBM DB2,
Oracle, or MS SQL Server).

2. Install the enterprise tier using Teamcenter Environment Manager, being sure to choose the
server manager component.

PLM00013 11.2 Windows Server Installation 2-23

 Chapter
Chapter 2: 2: Site planning
Site planning

Teamcenter Environment Manager installs the pool of Teamcenter servers and the server
manager, creates and or populates the database, and configures a volume.7

3. Install the Java EE web tier as an web archive (WAR) file using the Web Application Manager
and deploy the WAR file in a Java EE application server.8
Note

The thin client is installed as part of the web tier for access by clients.

4. Install a third-party application server and deploy the Teamcenter WAR file.8

5. If you are deploying the rich client, install the distribution server for the Over-the-Web Installer,
and then install a rich client distribution instance.

6. Install the rich client using the Over-the-Web Installer on a Windows or Linux host.

Note

The automatic logon feature is not supported in four-tier Teamcenter deployments.

7. Teamcenter provides server managers based on the Java EE and the Microsoft .NET platforms. Install the appropriate server manager
for the web tier you use.
8. This is not necessary if you use the .NET web tier and the .NET based server manager.

2-24 Windows Server Installation PLM00013 11.2

 Site planning

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.

PLM00013 11.2 Windows Server Installation 2-25

 Chapter
Chapter 2: 2: Site planning
Site planning

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.

2-26 Windows Server Installation PLM00013 11.2

 Site planning

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)

PLM00013 11.2 Windows Server Installation 2-27

 Chapter
Chapter 2: 2: Site planning
Site planning

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.

• 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.

Related topics

• Solutions and features reference

• Planning rich client distribution

• Linux Client Installation

• Windows Client Installation

2-28 Windows Server Installation PLM00013 11.2

 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
a web archive (WAR) 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 component of the thin client is installed on a user
workstation other than the required third-party web browser.

File Management System installation

FMS installation considerations

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

Overview of FMS installation

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.

PLM00013 11.2 Windows Server Installation 2-29

 Chapter
Chapter 2: 2: Site planning
Site planning

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.)

2-30 Windows Server Installation PLM00013 11.2

 Site planning

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:
• 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.

Related topics
• File Management System

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

PLM00013 11.2 Windows Server Installation 2-31

 Chapter
Chapter 2: 2: Site planning
Site planning

• 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.
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.

• 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.

Installing an FCC for use with the thin client and Teamcenter lifecycle visualization is described in
the Teamcenter client installation guides for Windows, Linux, and Macintosh.

2-32 Windows Server Installation PLM00013 11.2

 Site planning

Related topics

• File Management System

Creating volumes

Using Teamcenter Environment Manager installation program, you create two types of Teamcenter
volumes:
• Standard volumes
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.

Related topics

• Create a volume

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)

PLM00013 11.2 Windows Server Installation 2-33

 Chapter
Chapter 2: 2: Site planning
Site planning

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.
Installation of TCCS is described in the appropriate Teamcenter client installation guides for Windows,
Linux, and Macintosh.
For information about installing Lifecycle Visualization, see the Teamcenter lifecycle visualization
Installation Guide in the Lifecycle Visualization online help library.
Lifecycle Visualization features provided with Teamcenter are installed through TEM and the Web
Application Manager. You can also patch Lifecycle Visualization using TEM.
Note

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.
For more information about software requirements for Lifecycle Visualization, see the Siemens
PLM Software certification site:
http://support.industrysoftware.automation.siemens.com/certification/tc_vis.shtml

2-34 Windows Server Installation PLM00013 11.2

 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.

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.

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.

3. If you are deploying the four-tier architecture:

PLM00013 11.2 Windows Server Installation 2-35

 Chapter
Chapter 2: 2: Site planning
Site planning

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.

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.

Other considerations

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 hardware and software certifications site on GTAC.
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 and simple queries. Such a configuration also makes the fine-tuning of the
database easier.
Note

A separate RDV database are not required if you use cacheless search.

MS SQL server considerations

If you use Microsoft SQL Server, install the MS SQL Server database server before you begin
installing Teamcenter. For certified versions of MS SQL Server, see the hardware and software
certifications site on GTAC.
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

2-36 Windows Server Installation PLM00013 11.2

 Site planning

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.

Network environment considerations

Homogeneous network environment

In a homogeneous environment, all hosts run the same platform, for example, a corporate server,
web tier, and Teamcenter clients all running on Microsoft Windows or all running on SUSE Linux.
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, hosts do not all run the same platform, for example, a corporate
server may run on a UNIX host, a web application server on a Linux host, and workstations on
Microsoft Windows.
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.
Configure File Management System for volume access for all clients.
Make sure your Windows and UNIX server configurations contain identical sets of Teamcenter
features. For example, if you install features or custom templates on a UNIX server, you must install
the same features and templates on your Windows server.

PLM00013 11.2 Windows Server Installation 2-37

 Chapter
Chapter 2: 2: Site planning
Site planning

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
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

The password must not be empty nor contain any whitespace characters such as space,
tab, newline, carriage return, form feed, or vertical tab.
In addition, the password must not contain any of the following characters:
!@$%=&'":;.<>(){}

2-38 Windows Server Installation PLM00013 11.2

 Site planning

Caution

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.

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.

PLM00013 11.2 Windows Server Installation 2-39

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:
hardware and software certifications
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.

IBM DB2 installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Microsoft SQL Server installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

PLM00013 11.2 Windows Server Installation

Chapter 3: IBM DB2 installation and configuration

IBM DB2 installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

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-4

About DB2 sample databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Create a sample database using default sample tables . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Create a sample database using your own parameters and tables . . . . . . . . . . . . . . . . . . 3-5

Verify connectivity with the sample database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Creating 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-7

PLM00013 11.2 Windows Server Installation

Chapter 3: IBM DB2 installation and configuration

IBM DB2 installation considerations

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 hardware and software certifications site on GTAC.
Note

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.

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

1. Prepare the software installation media:
• 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

Expand the image to a local directory.

PLM00013 11.2 Windows Server Installation 3-1

 Chapter
Chapter 3: 3: IBM DB2
IBM installation
DB2 installation and configuration
and configuration

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.

3-2 Windows Server Installation PLM00013 11.2

 IBM DB2 installation and configuration

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.

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.

PLM00013 11.2 Windows Server Installation 3-3

 Chapter
Chapter 3: 3: IBM DB2
IBM installation
DB2 installation and configuration
and configuration

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
11.2 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.

Create a DB2 sample database

About DB2 sample databases
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:

3-4 Windows Server Installation PLM00013 11.2

 IBM DB2 installation and configuration

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.

PLM00013 11.2 Windows Server Installation 3-5

 Chapter
Chapter 3: 3: IBM DB2
IBM installation
DB2 installation and configuration
and configuration

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.

Creating a DB2 database for Teamcenter

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:

db2 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:

db2 CREATE DB tcdb2 AUTOMATIC STORAGE YES ON 'D:' USING CODESET

UTF-8 TERRITORY US PAGESIZE 32 K

3-6 Windows Server Installation PLM00013 11.2

 IBM DB2 installation and configuration

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:

PLM00013 11.2 Windows Server Installation 3-7

 Chapter
Chapter 3: 3: IBM DB2
IBM installation
DB2 installation and configuration
and configuration

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.

3-8 Windows Server Installation PLM00013 11.2

Chapter 4: Oracle installation and configuration

Preparing the Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Upgrade an Oracle server and database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Export an Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
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-2
Back up an Oracle installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Upgrading an Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Oracle server upgrade methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Upgrade using the Oracle installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Upgrade by uninstalling/reinstalling Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Configure Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Configure Oracle Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Configure Oracle listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Create an Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

PLM00013 11.2 Windows Server Installation

Chapter 4: Oracle installation and configuration

Preparing the Oracle server

Your Oracle database server must be a version certified for Teamcenter 11.2. For information about
the Oracle versions that Siemens PLM Software certifies for use with Teamcenter 11.2, Oracle disk
space requirements, and operating system and service patch requirements, see the hardware and
software certifications page on GTAC.
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.

• If you have an Oracle server installed, but it is not a version certified for Teamcenter 11.2,
upgrade your Oracle server.

3. Configure Oracle software for Teamcenter.

4. Create a database for Teamcenter.

Related topics
• Install Oracle server

• Upgrade an Oracle server and database

Upgrade an Oracle server and database

Export an Oracle database

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\expdp db-user/password full=y file=file-name.dmp log=export.log

PLM00013 11.2 Windows Server Installation 4-1

 Chapter
Chapter 4: 4: Oracle
Oracle installation
installation and configuration
and configuration

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.

If you have multiple databases, repeat this procedure for each database.
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

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

Shut down Oracle using Windows Control Panel

1. Log on to the operating system as a user with administrator privileges.

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

1. Log on to the operating system as a user with administrator privileges.

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.
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:

4-2 Windows Server Installation PLM00013 11.2

 Oracle installation and configuration

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 an Oracle server

Oracle server upgrade methods

You can upgrade your Oracle server and databases two ways:
• Upgrade using the Oracle installer

• Upgrade by uninstalling/reinstalling Oracle

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. Then, configure Oracle and create an Oracle database.

4. After Oracle installation is complete, import your Teamcenter database from the Oracle dump file
into the new Oracle database. Enter the following command on a single line:
ORACLE_HOME\bin\imp
db-user/password fromuser=db-user touser=db-user file=file-name.dmp log=import.log

PLM00013 11.2 Windows Server Installation 4-3

 Chapter
Chapter 4: 4: Oracle
Oracle installation
installation and configuration
and configuration

Replace db-user with the Teamcenter database user account name, password with the database
user account password, file-name with the full path and name of the dump file that contains the
exported data, and import with the name of the log file.

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. In the Oracle RDBMS installation media, launch the setup program.

Note

If you install the Oracle RDBMS from a DVD, the system displays the Autorun dialog box
when you insert the DVD.

4. In the Configure Security Updates dialog box, specify whether and how you want to be informed
about security updates from Oracle, and then click Next.

5. In the Download Software Updates dialog box, specify whether and how you want to download
software updates for Oracle software, and then click Next.

6. In the Select Installation Option dialog box, select Install database software only, and then
click Next.

7. In the Grid Installation Options dialog box, select Single instance database installation,
and then click Next.

8. In the Select Product Languages dialog box, select the languages you want the Oracle instance
to support, and then click Next.

4-4 Windows Server Installation PLM00013 11.2

 Oracle installation and configuration

9. In the Select Database Edition dialog box, select the database edition to install, and then
click Next.
Note

Teamcenter supports Enterprise Edition and Standard Edition.

10. In the Specify Oracle Home User dialog box, specify the system account you use to install
Oracle. This can be an existing system account or a new system account.

11. 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 12c or later into an existing Oracle home directory that contains
Oracle 11g or earlier software.

12. In the Summary dialog box, review the information to ensure you have sufficient disk space,
and then click Install.

13. In the Install Product dialog box, monitor the success of the installation stages.

14. When the Finish dialog box displays the The installation of Oracle Database was successful
message, click Close to complete the installation.

Configure Oracle software

Configure Oracle Net
Teamcenter uses Oracle Net protocols to communicate with an Oracle database. These protocols
require that you run a listener process (OracleTNSListener) on the Oracle server to listen for
remote connect requests and that all clients can translate the service alias identifying the server and
database.

Configure Oracle listener

1. Start Oracle Net Manager. Choose Start→All Programs→Oracle -
instance-name→Configuration and Migration Tools→Net Manager, or search for
Net Manager.

2. Create the listener.ora file:

a. Expand the Local icon.

b. Select the Listeners folder and choose Edit→Create.

PLM00013 11.2 Windows Server Installation 4-5

 Chapter
Chapter 4: 4: Oracle
Oracle installation
installation and configuration
and configuration

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\12.1.0\dbhome_1. This command creates and starts the
service if it does not exist. If the service exists, the command starts it.

Create an Oracle database

Create an Oracle database instance using Siemens PLM Software-provided templates with Oracle
Database Configuration Assistant (DBCA). The templates populate the database with the required

4-6 Windows Server Installation PLM00013 11.2

 Oracle installation and configuration

Oracle user accounts and tablespaces. The templates create a single database user (infodba) per
Oracle system identifier (SID).
Note

• 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.

• 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
11.2, see the hardware and software certifications page on GTAC.

1. Make sure you have access to the Teamcenter software distribution image.

2. Log on to the Oracle server host as a user who is a member of the ORA_instance-name_DBA
group. This may be the user who installed Oracle on the server host or one assigned to
ORA_instance-name_DBA by a member of the ORA_instance-name_DBA group.

3. 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

4. Start Oracle Database Configuration Assistant (DBCA):

Start→All Programs→Oracle – instance-name→Configuration And Migration Tools
→Database Configuration Assistant
Alternatively, search for Database Configuration Assistant.

5. In the Database Operation dialog box, select Create Database and click Next.

6. In the Creation Mode dialog box, click Advanced Mode and click Next.

7. In the Database Template dialog box, in the list of templates, select the Teamcenter_Oracle.dbt
template and click Next.

8. 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.

PLM00013 11.2 Windows Server Installation 4-7

 Chapter
Chapter 4: 4: Oracle
Oracle installation
installation and configuration
and configuration

9. In the Management Options dialog box, accept the default selections, and then click Next.

10. 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.

11. In the Network Configuration dialog box, verify the listener you created and started is running
and selected in the Listener Selection tab.
If the listener is not running, start the listener and make sure it is selected before you continue.

12. In the Storage Options dialog box, select the following options:
• Under Database Files, select File System and choose Use Database File Locations
from Template.

• Under Recovery Related Files, select the Specify Fast Recovery Area check box and
accept the default values.

13. In the Database Options dialog box, click Next.

14. In the Initialization Parameters dialog box, click Next.

15. In the Create Options dialog box, select Create Database and click Next.

16. The Prerequisite Checks dialog box validates your selections and then displays the Summary
dialog box. Verify your selections, and then click Finish to begin creating the database.
When the database is created, DBCA displays a window containing information about the created
database.

17. In the Progress Page dialog box, click Close to exit DBCA.

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.

4-8 Windows Server Installation PLM00013 11.2

Chapter 5: Microsoft SQL Server installation and configuration

Install Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Create an SQL Server database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

PLM00013 11.2 Windows Server Installation

Chapter 5: Microsoft SQL Server installation and configuration

Install Microsoft SQL Server

You can install Microsoft SQL Server and configure a database for Teamcenter using the following
steps, but keep in mind these steps may vary depending on your selections and your edition of
SQL Server.
Note

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 hardware and software certifications page on GTAC.
1. Log on to an account with system administrator privileges.

2. Launch the Microsoft SQL Server Installation Center application (setup.exe).

3. In the SQL Server Installation Center dialog box, click Installation in the navigation pane
on the left side.

4. Click New SQL Server stand-alone installation or add features to an existing installation.
The SQL Server Installation Center launches the SQL Server Setup wizard.

5. Proceed through the pre-installation tests and other initial setup panes to the Setup Support
Files pane. Click Install to install SQL Server setup support files.
After setup support files are installed, the wizard displays the Setup Support Rules pane.
Click Next.

6. In the Setup Role pane, accept the default selection (SQL Server Feature Installation) and
click Next.

7. In the Feature Selection pane, select Instance Features→Database Engine Services and any
other features you want to include.
Click Next.

8. In the Instance Configuration pane, select 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.

PLM00013 11.2 Windows Server Installation 5-1

 Chapter
Chapter 5: 5: Microsoft
Microsoft
SQL SQL Server
Server installation
installation and configuration
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.

9. Enter remaining instance configuration values, and then click Next,

10. Proceed to the Server Configuration pane.

a. Click the Service Accounts tab.

b. Enter account information for starting SQL Server services.

Note

The SQL Server Setup wizard validates user accounts for SQL Server services. Make
sure the accounts you enter exist on the host.

c. Click the Collation tab.

d. On the Collation tab, click Customize.

The wizard displays a customization dialog box for database engine collation.

e. Select Windows Collation designator and sort order.

f. In the Collation designator box, select Latin1_General and then select Binary.

g. Click OK.

h. In the Server Configuration pane, click Next.

11. Proceed to the Database Engine Configuration pane.

a. Click the Account Provisioning tab.

b. Under Authentication Mode, select Mixed Mode and define a password for the SQL
Server sa logon account.

c. Specify at least one SQL Server administrator account.

d. Click Next.

12. Proceed to the Ready to Install pane and click Install to install.

Teamcenter requires TCP/IP protocol to be enabled, but this protocol is disabled by default when you
install Microsoft SQL Server. Before you install Teamcenter, make sure you enable TCP/IP protocol.
For more information about enabling TCP/IP protocol in Microsoft SQL Server, see the Microsoft
online help resources on the Internet.

5-2 Windows Server Installation PLM00013 11.2

 Microsoft SQL Server installation and configuration

Note

The following article contains information about enabling TCP/IP protocol for Microsoft SQL
Server 2012:
http://technet.microsoft.com/en-us/library/hh231672(v=sql.110).aspx

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 Microsoft SQL Server Management Studio:

Start→Programs→Microsoft SQL Server→SQL Server Management Studio

Alternatively, search the start menu for 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.

5. Browse to the tc\db_scripts\mssql directory in the Teamcenter 11.2 software distribution image.

6. Select the create_database.sql.template file and click Open.

If SQL Server Management Studio prompts you to log on, enter the system administrator (sa)
logon name and password.

7. Edit the database template (create_database.sql.template) to replace the necessary values.

The following table describes the database parameters to replace in the template. Within the
template file, there are also comments on values that must be replaced.

Parameter Example value Description

@DB_NAME@ TC Name of the database to create.
@DATA_PATH@ D:\MSSQL_DATA Path to the directory in which to place the data file.
@USER_NAME@ infodba Database logon name for the Teamcenter database.
@PASSWORD@ infodba Password for the database logon name.

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.

PLM00013 11.2 Windows Server Installation 5-3

 Chapter
Chapter 5: 5: Microsoft
Microsoft
SQL SQL Server
Server installation
installation and configuration
and configuration

Parameter Example value Description

@COLLATION@ Latin1_General_BIN Collation sequence you want the Teamcenter database to use. Choose
the appropriate collation for your locale. The collation value must end
with _BIN.3.

Collation defines the alphabet or language whose rules are applied

when data is sorted or compared. The collation value determines the
character set used by the database server.
@LANGUAGE@ us_english Database language.

8. Save the newly modified file as filename.sql, removing the _template extension.

9. Open the new file in Microsoft SQL Server Management Studio.

10. In the SQL Editor toolbar, click Execute (or choose Query→Execute to begin creating the
database.

11. 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.

3. Do not use the default collation value that ends with _CI_AS.

5-4 Windows Server Installation PLM00013 11.2

Part III: Teamcenter server installation

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

Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

PLM00013 11.2 Windows Server Installation

Chapter 6: Teamcenter preinstallation tasks

Obtain a Teamcenter license file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

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

Select destination directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Install a volume server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Install NX and Teamcenter Integration for NX or NX Integration . . . . . . . . . . . . . . . . . . . . . . . 6-5

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Best installation practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

PLM00013 11.2 Windows Server Installation

Chapter 6: Teamcenter preinstallation tasks

Obtain a Teamcenter license file

To obtain a Teamcenter license file, you must provide the composite host ID of your Teamcenter
license server host.
A composite host ID (CID) is a unique identifier used as the host ID on the SERVER line of the
license file. It is distinguished from the default FlexNet host ID by the COMPOSITE keyword. It is
the host ID that associates a permanent license file with a specific server. When the CID is used
as the license server host ID, the SERVER line reads as follows:
SERVER serverA COMPOSITE=37B5ED1AC61D 28000

To obtain a composite host ID for your license server, run the getcid utility on your license server
host. Download this utility from GTAC:
1. Open the GTAC web site.

2. Click License Management→Download CID Utility.

3. On the Download CID Utility page, click NX and Other Products.

4. On the FTP site, click the directory corresponding to the platform type of your license server,
for example, wntx64lnx64.

5. On the resulting page, download the getcid.exe utility.

Run the getcid.exe utility on the target license server (or on all three servers in a redundant
configuration). The utility provides the CID for license server as a 12-digit hexadecimal number.
For example:
$ getcid.exe
The Siemens PLM Software licensing composite hostid is:
”COMPOSITE=37B5ED1AC61D”

After you obtain the CID, enter it into your customer record to generate a permanent license file.
You can enter your CID using either your WebKey account or by calling your customer services
representative. After the CID is entered into your customer record, you are sent a permanent license
file to install on your license server.

Install the licensing server

Before you install Teamcenter, you must install the Siemens PLM License 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.

PLM00013 11.2 Windows Server Installation 6-1

 Chapter
Chapter 6: 6: Teamcenter
Teamcenter preinstallation
preinstallation taskstasks

For descriptions of the available license types, see your license agreement documentation.
This procedure assumes you have obtained a Teamcenter license file.
1. Obtain a Teamcenter 11.2 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.
If you choose to install Teamcenter using a temporary license file, edit the temporary license file
to reflect your designated Teamcenter corporate server host.
a. Open the license file in a plain text editor and locate the following line in the file:
SERVER YourHostname ANY 28000

b. 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.

c. Save the changes to the license file.

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.
Record the host name and port for the license server. Teamcenter Environment Manager (TEM)
prompts you for these values during Teamcenter server installation.

2. Set the SPLM_LICENSE_SERVER environment variable to the following value on the designated
Teamcenter corporate server host:
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.
The first entry in the value of this variable is designated as the default local license server during
corporate server upgrade. TEM verifies that the specified license server exists and is running
a supported version of the Siemens PLM Software common licensing server. If the configured
license server is not valid, the upgrade is stopped until a valid license server is installed.

3. Set the TCP_NODELAY environment variable to 1 on the licensing server host. This helps
optimize logon time when launching Teamcenter.

4. Change to the additional_applications directory in the Teamcenter software distribution image.

5. Copy the Siemens PLM License Server installation program

(SPLMLicenseServer_version_setup.exe) to a temporary directory on your local hard drive.

6. Launch the Siemens PLM License Server installation program:

a. Launch the SPLMLicenseServer_version_setup.exe program.

1. Port 28000 is registered for the Siemens PLM License Server with the Internet Assigned Numbers Authority (IANA). For more
information, see http://www.iana.org/assignments/port-numbers.

6-2 Windows Server Installation PLM00013 11.2

 Teamcenter preinstallation tasks

b. 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 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.

Information about installing the Siemens PLM Software Common Licensing Server is available in
the Licensing Server documentation in the product download page on GTAC. This documentation is
available under Siemens PLM Licensing→Product updates→Documentation.

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.

• The Teamcenter installation directory must be in a location excluded from real-time virus scanning.

Real-time virus scanning prevents Teamcenter from updating the persistent object manager
(POM) schema during installation, causing installation errors.

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.

PLM00013 11.2 Windows Server Installation 6-3

 Chapter
Chapter 6: 6: Teamcenter
Teamcenter preinstallation
preinstallation taskstasks

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.

3. In the Welcome to Teamcenter panel, select Teamcenter.

4. Proceed to the Install/Upgrade Options panel. Click Install.

5. (Optional) In the Media Locations panel, enter paths to any Teamcenter patches or service
packs you want to apply during installation.

6. Proceed to the Configuration panel. Enter a unique ID and description for the new Teamcenter
configuration.

7. 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 the
complete list of features.

8. Proceed to the Features panel. This panel shows the FMS Server Cache feature preselected by
the Volume Server solution.

9. In the Installation Directory box, enter the absolute path to the directory where you want to
install the volume server.

10. 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.

11. Proceed to the File System Cache Service (FSC) panel. Enter required values for the FMS

server cache (FSC) service. For information about required values, click the help button .

12. Proceed through the remaining panels, entering required values for the volume server.

13. 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.

14. When installation is complete, close TEM.

6-4 Windows Server Installation PLM00013 11.2

 Teamcenter preinstallation tasks

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 about using Teamcenter with NX, see the installation guides distributed with
NX. Installing Teamcenter varies depending on whether you have a license for NX Integration or
Teamcenter Integration for NX.

Related topics
• Getting started

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. Install a Teamcenter corporate server.
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.
A Teamcenter corporate server contains the Teamcenter Foundation and FMS Server Cache
features as a minimum.

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 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.

PLM00013 11.2 Windows Server Installation 6-5

 Chapter
Chapter 6: 6: Teamcenter
Teamcenter preinstallation
preinstallation taskstasks

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.

6-6 Windows Server Installation PLM00013 11.2

Chapter 7: Teamcenter server installation

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Install a Teamcenter corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

PLM00013 11.2 Windows Server Installation

Chapter 7: Teamcenter server installation

Before you start

• Locate the Teamcenter software distribution image for your platform. If you install Teamcenter
online help, locate the Teamcenter documentation distribution image.

• 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:

◊ 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:

PLM00013 11.2 Windows Server Installation 7-1

 Chapter
Chapter 7: 7: Teamcenter
Teamcenter server
server installation
installation

• 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 the volume location not be under the Teamcenter
application root directory. Doing so can cause problems when upgrading to a new version
of Teamcenter.

• Select the features to install. Point to any feature to view a description.1

• 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 Java EE and the Microsoft .NET
platforms. Install the appropriate server manager for the web tier you use.

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.

1. For further descriptions of server features, see Teamcenter features.

7-2 Windows Server Installation PLM00013 11.2

 Teamcenter server installation

Data Description
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.
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.

PLM00013 11.2 Windows Server Installation 7-3

 Chapter
Chapter 7: 7: Teamcenter
Teamcenter server
server installation
installation

Data Description
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
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.

7-4 Windows Server Installation PLM00013 11.2

 Teamcenter server installation

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.

2. Specify the path to the required Java Runtime Environment (JRE) by setting the JRE64_HOME
environment variable on your host.2

3. 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.

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.

Note

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

4. In the Welcome to Teamcenter, select Teamcenter.

5. Proceed to the Install/Upgrade Options 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.

• Upgrade
Upgrades an existing Teamcenter configuration.

Click Install to begin installing a corporate server.

2. Alternatively, you can specify the JRE path when you launch TEM from a command prompt using the -jre JRE-path argument.

PLM00013 11.2 Windows Server Installation 7-5

 Chapter
Chapter 7: 7: Teamcenter
Teamcenter server
server installation
installation

Note

The Install/Upgrade Options panel also provides these installation options:

• Create environment for upgrade testing
TEM can create a copy of an existing Teamcenter environment for upgrade testing
only. The copied environment cannot be used as a production database.

• Create custom distribution

To simplify installations of Teamcenter on multiple hosts, TEM can create a silent
distribution or a compact distribution. Compact distribution is recommended only for
Teamcenter client configurations, not for servers.

6. In the Media Locations panel, enter paths to any Teamcenter patches or service packs you want
to apply during installation. This step is optional.

7. 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.

8. In the Solutions panel, select the Corporate Server solution.

9. Proceed to the Features panel. This panel shows the corporate server features preselected
by the Corporate Server solution:
Teamcenter Foundation
FMS Server Cache
NX Part Family Classification Integration

10. Select any additional features you want to include in your configuration.
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.

7-6 Windows Server Installation PLM00013 11.2

 Teamcenter server installation

Note

• If you are deploying the Java EE web tier or the .NET web tier, select the appropriate
server manager feature, Java EE Based Server Manager or .NET Based Server
Manager (under Server Enhancements).

• You can also install custom features by 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 provided in the client installation
guides for Windows and Linux.

11. In the Installation Directory box, enter the path to a new directory where you want to install
Teamcenter.
The Installation Directory value is the Teamcenter application root directory (TC_ROOT).
Do not set the TC_ROOT environment variable in the system environment. TEM sets this
variable as required in Teamcenter configuration files. Setting this variable in the operating
system can cause conflicts if you install multiple Teamcenter configurations.
The installation directory must meet the following requirements:

• The directory must not already exist on your system. (TEM creates the directory during
installation.)

• The path to the installation directory must not exceed 64 characters.

• The directory must be in a location excluded from real-time virus scanning.3

Note

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.

12. 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.

13. In the Operating System User panel, type the password for the operating system account
under which you install Teamcenter.

3. Real-time virus scanning prevents Teamcenter from updating the persistent object manager (POM) schema during installation, causing
installation errors.

PLM00013 11.2 Windows Server Installation 7-7

 Chapter
Chapter 7: 7: Teamcenter
Teamcenter server
server installation
installation

14. 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.
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.

15. 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:

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 and the database user.

• Create new data directory using existing populated database:

a. Proceed to the Foundation Database panel.

7-8 Windows Server Installation PLM00013 11.2

 Teamcenter server installation

b. Select the appropriate database server vendor (IBM DB2, Oracle, or MS 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.

16. In the Data Directory box, enter a location for the Teamcenter data directory.
The Teamcenter data directory is called the TC_DATA directory. TEM stores this location as the
TC_DATA variable in Teamcenter configuration files. 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 as a system environment variable. Setting this variable in the operating
system can cause conflicts if you install more than one configuration.

17. Proceed to the Volume Information 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.

18. Proceed to the Foundation Settings 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.
Caution

PLM00013 11.2 Windows Server Installation 7-9

 Chapter
Chapter 7: 7: Teamcenter
Teamcenter server
server installation
installation

Value Description

You cannot define the path as a UNC path,

for example, \\server\shared-transient-folder .
You must use a direct path location.
This is partly due to the fact that some ZIP
archive utilities do not accept UNC paths,
resulting in failure of exports to Excel or
Word.
Windows clients Specifies the location for a transient volume for
Windows client hosts.
UNIX clients Specifies the location for a transient volume for
Linux client hosts.
Generate server cache Specifies you want to generate a shared server
cache. If you select this option, TEM runs the
generate_client_meta_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 Teamcenter
server installation.
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 Teamcenter
server installation.
Production Environment Specifies your new environment is to be used as a
live environment where you will store your product
data.

7-10 Windows Server Installation PLM00013 11.2

 Teamcenter server installation

Value Description
Test Environment Specifies your new environment is to be used
for development, testing, or training. Selecting
Test Environment enables the bulk loader tool to
copy data from another environment (such as a
production environment) into this test environment.
Note

If you designate this environment as a test

environment, the designation cannot be
changed.
Additionally, a test environment cannot
participate in Multi-Site sharing with a
production environment.

For advanced Teamcenter Foundation options, click Advanced.

19. If you want to configure Teamcenter online help, click Advanced in the Foundation Settings
panel and perform the following steps:
a. Click the Online Help tab.

b. Select the Enable Online Help check box.

c. In the PLM Document Server URL box, type the Teamcenter online help URL.

20. Proceed to the Flex License Client panel. Enter settings for the Siemens PLM License Server.
Note

The Siemens PLM License Server must be installed before you begin Teamcenter
installation.

21. Proceed to the Teamcenter Administrative User panel. During a corporate server installation,
the values in this panel are read-only.

22. Proceed to the Password Security panel. In the Administrative Password Directory box,
enter the directory in which to place Teamcenter password files. TEM locks access to this
directory to all users except the user performing Teamcenter installation.

23. Proceed through any remaining panels, entering the required information for the features you
selected.

For information about these panels, click the help button .

24. 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.

PLM00013 11.2 Windows Server Installation 7-11

 Chapter
Chapter 7: 7: Teamcenter
Teamcenter server
server installation
installation

Note

If an error occurs during installation, follow the instructions in the error message displayed
by TEM or see the available troubleshooting solutions.

25. When installation is complete, close TEM.

Note

After installation, you can find Teamcenter in the list of installed programs in the Windows
control panel. The program name is displayed as Teamcenter 11.2 (x64) (TC_ROOT).

Related topics
• Teamcenter Upgrade

• About quick preconfigured installation in TEM

7-12 Windows Server Installation PLM00013 11.2

Chapter 8: Teamcenter postinstallation tasks

Start database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Configure online help access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Overview of Multi-Site Collaboration configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Prepare the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Install a proxy server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Configure heterogeneous operating system environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Back up new installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Terminate Teamcenter sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Back up existing Teamcenter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Back up Teamcenter databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

PLM00013 11.2 Windows Server Installation

Chapter 8: Teamcenter postinstallation tasks

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

If the services do not start automatically, see the available troubleshooting solutions.
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.

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.

Configure online help access

To configure Teamcenter online help after Teamcenter installation, or to change online help access for
Teamcenter clients, perform the following procedures where appropriate.

PLM00013 11.2 Windows Server Installation 8-1

 Chapter
Chapter 8: 8: Teamcenter
Teamcenter postinstallation
postinstallation taskstasks

• Thin client

To configure online help for the Teamcenter thin client, set the following preferences.

Preference Value
WEB_core_help_server http://host:port/tdoc/tc/version/help/
host and port are the host name and port of the PLM
Documentation Server. version is the Teamcenter
version or SP level. For example:
http://myhost:8181/tdoc/tc/11.2/help/
WEB_help_server http://host:port/tdoc/tc/version/help/
#filename:thin_client_dhtml:getting_started
host and port are the host name and port of the PLM
Documentation Server. version is the Teamcenter
version or SP level.
This preference specifies the location of the thin
client online help. The part of this value preceding
the hash symbol (#) should match the value of the
WEB_core_help_server preference.

• Four-tier rich client installed through TEM

To configure online help for a Teamcenter rich client you installed using TEM (not using the
Over-the-Web Installer), set preferences the same as for the thin client.

• Two-tier rich client

To configure online help for a two-tier rich client, launch TEM in maintenance mode and proceed
to the Feature Maintenance panel. Under Teamcenter rich client→Rich Client 2-tier, select
Modify settings.

Next, in the Rich Client Settings panel, select the Enable Online Help check box, and then
type the online help URL in the Web server URL box.

8-2 Windows Server Installation PLM00013 11.2

 Teamcenter postinstallation tasks

Note

Alternatively, you can configure online help for a two-tier rich client by setting the following
values in the site_specific.properties file for on the rich client host.

Property Value
portalHelpWebServer http://

This value specifies the protocol for online help access.

portalHelpPage host:port/tdoc/tc/version/help/

host and port are the host name and port of the PLM Documentation
Server. version is the Teamcenter version or SP level. For example:

myhost:8181/tdoc/tc/11.2/help/

• Rich client distribution instance

To configure online help for rich clients installed using the Over-the-Web Installer, modify your rich
client distribution instance in the Web Application Manager. In the Modify Web Application dialog
box, click Modify Context Parameters, and then set the rich client help content parameters.

Context parameter Value

RichClientHelpWebServer http://host:port/tdoc/tc/version
host and port are the host name and port of the PLM
Documentation Server. version is the Teamcenter version
or SP level.
RichClientHelpLocation /help
This is the subpath to the Teamcenter online help.

PLM00013 11.2 Windows Server Installation 8-3

 Chapter
Chapter 8: 8: Teamcenter
Teamcenter postinstallation
postinstallation taskstasks

Configure Multi-Site Collaboration

Overview of Multi-Site Collaboration configuration
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.
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.

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.

8-4 Windows Server Installation PLM00013 11.2

 Teamcenter postinstallation tasks

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

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.

Configure heterogeneous operating system environment

If you are adding Windows Teamcenter clients to a UNIX or Linux 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 the following files in the separate Teamcenter data directories:

• POM schema files (TC_DATA\pom_schema_server_sid)

• POM transmit files (\pom_transmit\*.sch)

• Dataset definition files (TC_DATA\gs_info\*.des)

3. Make sure your Windows and UNIX server configurations contain identical sets of Teamcenter
features. For example, if you install features or custom templates on a UNIX server, you must
install the same features and templates on your Windows server.

PLM00013 11.2 Windows Server Installation 8-5

 Chapter
Chapter 8: 8: Teamcenter
Teamcenter postinstallation
postinstallation taskstasks

4. 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 Linux clients you want to connect to the
database.

Back up new installations

Terminate Teamcenter sessions

1. Instruct all users to close and log off of Teamcenter sessions, including tcserver processes.

2. Open a Teamcenter command prompt:

Windows systems:
From the Start menu, choose Programs→Teamcenter, and open a command prompt.

UNIX and Linux systems:

Enter the following commands:
TC_ROOT=/usr/Siemens/Teamcenter11; export TC_ROOT
TC_DATA=/usr/Siemens/Teamcenter11/teamcenterdata; export TC_DATA
. $TC_DATA/tc_profilevars

This example assumes that Teamcenter is installed under the usr/Siemens/Teamcenter11

directory.
Sourcing the tc_cshvars file creates a csh subshell in which Teamcenter environment
variables are set.

3. Use the clearlocks utility to remove locks on the database:

%TC_BIN%\clearlocks -u=infodba -p=infodba-password -g=dba -assert_all_dead

4. Stop all Teamcenter services, including FMS.

Back up existing Teamcenter data

Back up the following directories:
• The Teamcenter application root directory on each installed workstation

• The Teamcenter data directory for each configured database

• The Teamcenter volume directories for each configured database

These are the only directories affected by Teamcenter installation. If you created other directories
that contain data used by your existing Teamcenter installation, such as a separate POM transmit
schema directory, Siemens PLM Software recommends that you back up these directories as a
precautionary measure.

8-6 Windows Server Installation PLM00013 11.2

 Teamcenter postinstallation tasks

Back up Teamcenter databases

Back up your Oracle server and databases:
1. Export existing Oracle databases.
For information, see Export an Oracle database.

2. Terminate Teamcenter-Oracle sessions.

For information, see Terminate Teamcenter sessions.

3. Back up the Oracle installation.

For information, see Back up an Oracle installation.

PLM00013 11.2 Windows Server Installation 8-7

Part IV: Web tier installation

Install the Teamcenter web tier, which manages communication between the Teamcenter clients
and the enterprise tier.

.NET web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Java EE web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

PLM00013 11.2 Windows Server Installation

Chapter 9: .NET web tier installation

.NET web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Install required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Configure Microsoft IIS on Windows Server 2008/2012 . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Install the .NET web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Start the web client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

PLM00013 11.2 Windows Server Installation

Chapter 9: .NET web tier installation

.NET web tier installation

The Teamcenter .NET web tier is an alternative to the Teamcenter Java EE web tier for Microsoft
Windows systems. The .NET web tier supports four-tier Teamcenter deployments and does not
require a Java EE application server.

Before you start

Install required software
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.
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 hardware and software
certifications page on GTAC.

Configure Microsoft IIS on Windows Server 2008/2012

If you use Microsoft Internet Information Services (IIS) on a Windows Server 2008/2012 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/2012 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.

5. In the Role Services table, verify that all of the following required role services are installed on
your host:

PLM00013 11.2 Windows Server Installation 9-1

 Chapter
Chapter 9: 9: .NET .NET webinstallation
web tier tier installation

Web Server
Common HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection

Application Development
ASP.NET version
.NET Extensibility
ASP
CGI
ISAPI Extensions
ISAPI Filters
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.

9-2 Windows Server Installation PLM00013 11.2

 .NET web tier installation

Caution

Make sure the WebDav Publishing role is not installed.

Install the .NET web tier

1. Launch Teamcenter Environment Manager (TEM).

If you create a new Teamcenter configuration, launch TEM from the Teamcenter software
distribution image. If you want to add the .NET-based server manager to an existing configuration,
launch TEM in maintenance mode.

2. Launch Teamcenter Environment Manager. In the Windows start menu, click

Programs→Teamcenter 11.2, 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. Alternatively, you can create a new configuration and select the Web
Tier for .NET feature in the Features panel.

• For a description of any TEM panel, click the help button in the panel.

3. In the Maintenance panel, select Configuration Manager.

4. In the Configuration Maintenance panel, select Perform maintenance on an existing

configuration.

5. In the Old Configuration panel, select the configuration to which you want to add the .NET
web tier.

6. In the Feature Maintenance panel, select Add/Remove Features.

7. In the Features panel, under Server Enhancements→Teamcenter Web Tier, select Web
Tier for .NET.

8. Proceed to the Multiplexing Proxy panel. Accept the default values or type new values for the
Teamcenter multiplexing proxy (MUX).

Value Description
Port Specifies the TCP/IP port on which the MUX listens
for web tier requests. This is the Jetty server
connector port.
TECS Admin Port Specifies the port used by the Teamcenter Enterprise
Communication System (TECS).

PLM00013 11.2 Windows Server Installation 9-3

 Chapter
Chapter 9: 9: .NET .NET webinstallation
web tier tier installation

Note

The MUX listens on a single port for incoming requests from the .NET web tier, forwarding
those requests to an appropriate Teamcenter server using operating system named-pipe
communication protocol, and then streaming the response back to web tier. The MUX runs
as an application within the Teamcenter Enterprise Communication System (TECS). The
TECS container is based on the Teamcenter client communication system (TCCS)
container used in the client tier.

9. In the .NET Server Manager panel, enter the required values to configure the .NET server
manager.

For information about .NET server manager values, click the help button .

10. In the Server Manager Performance Tuning panel, accept the default performance tuning
values or optionally enter your own preferred values.

11. In the TcServer Character Encoding Settings panel, make sure the values reflect the character
set you use for Teamcenter. If you are not sure, accept the default settings.

12. Proceed to the .NET Web Tier panel. 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.
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.
Note

TEM examines settings in your Microsoft Internet Information Services (IIS). If any required
settings or roles are missing, you must correct them in IIS before you continue.

13. In the Internet Information Services (IIS) Settings panel, accept the default settings, or specify
IIS settings for the .NET web tier:

1. For information about installing the .NET server manager, see Install the .NET server manager.

9-4 Windows Server Installation PLM00013 11.2

 .NET web tier installation

Parameter Description
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 Pool Specifies whether to use an existing application 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.
Alternatively, you can create a new application pool.
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.

For more information about these values, click the help button .

14. In the Confirmation panel, click Start to begin installing the .NET web tier.

15. 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.

• Install Teamcenter clients.

PLM00013 11.2 Windows Server Installation 9-5

Chapter 10: Java EE web tier installation

Overview of Java EE web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Java EE web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Install thin client web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Build the Teamcenter Web Tier web application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Build additional web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Special-use web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Install Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Supporting files locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Generate web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Build a proxy WAR file for WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Migrate legacy thin client URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Sharing an application server instance for multiple four-tier environments . . . . . . . . . . . 10-15

Install rich client web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16

Planning rich client distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Rich client distribution instance requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Install a rich client distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
Configuring TCCS, Security Services, and proxy settings . . . . . . . . . . . . . . . . . . . 10-30
Configure TCCS for the rich client distribution instance . . . . . . . . . . . . . . . . . . 10-30
Configure Security Services for the rich client distribution instance . . . . . . . . . . 10-32
Configure reverse proxy settings for the rich client distribution instance . . . . . . . 10-32
Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Deploy the distribution server instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Publish information for users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Start and stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Start the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Managing the rich client distribution server and instances . . . . . . . . . . . . . . . . . . . . . . 10-37
Change the distribution server contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-37
Add components to the distribution server instance . . . . . . . . . . . . . . . . . . . . . . . 10-37
Run the distribution server as a service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39

PLM00013 11.2 Windows Server Installation

Chapter 10: Java EE web tier installation

Overview of Java EE web tier installation

Java EE 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.

The Web Application Manager generates a web archive (WAR) file.

7. Deploy the web application on a supported Java EE application server.

PLM00013 11.2 Windows Server Installation 10-1

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Note

If your network includes client hosts running on an IPv6 network, the Java EE web tier must
be deployed in an application server that supports an IPv6 URL as an external endpoint and
uses IPv4 addresses to support all communication with the Teamcenter enterprise tier, such as
communication with the Java EE server manager.
A typical environment for the Java EE web tier is a dual-stack machine that supports both
IPv4 and IPv6 addresses in which the application server accepts HTTP requests from either
IPv4 or IPv6.
Teamcenter enterprise tier server components that communicate with other server components
in the same network are assumed to be on an IPv4 network and are not supported on IPv6.
Teamcenter IPv6 support is limited to clients or integrations that use Teamcenter client
communication system (TCCS) and Teamcenter components that communicate with clients
on IPv6-enabled networks.

Related topics
• Web Application Deployment

Java EE web tier prerequisites

Before you install the Java EE web tier, make sure you complete the following tasks:
• Install the Teamcenter server and server manager using Teamcenter Environment Manager.

• Install a supported third-party Java EE application server and the Java Runtime Environment
(JRE) on the web tier host.1

• If you use Security Services with the rich client or thin client, install Security Services.

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.
7-Zip displays a self-extractor dialog box.

3. In the Unzip To Folder box, type the path to WEB_ROOT, and then click Unzip.
After 7-Zip 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 hardware and software certifications page on GTAC.

10-2 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Install thin client web applications

Build the Teamcenter Web Tier web application
The Teamcenter Web Tier application is the thin client web application that provides essential
Teamcenter functionality. You can add additional thin client solutions, including custom solutions,
according to your needs.
After you build the Teamcenter web Tier application, you can build additional special-use web
applications.
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 11.2 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. Enter software locations:

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

B. In the Disk Location to Add box, enter the path to the Web_tier directory on the
Teamcenter 11.2 software distribution image:
image-location\Web_tier
Click OK to close the Add Disk Location dialog box.
Note

To modify a location or remove a location from the Disk Locations for Install Images
list, click Modify or Remove.

Note

Do not change the default solution type (Thin Client) shown in the Solution Type box.

PLM00013 11.2 Windows Server Installation 10-3

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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 – 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 Services Installs the Teamcenter service-oriented architecture
WSDL/SOAP Support (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.

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.

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
Web Tier web application, you must supply values for the following context parameters:

10-4 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

TreeCache Cluster Name2 Max_Capacity

TreeCache Mode Enterprise Application Lookup ID

TreeCache Cluster Port (when using Deployable File Name

multicast communication protocol)
IS_SSO_ENABLED
Local Service Port (when using TCP
communication protocol) SSO_APPLICATION_ID

TreeCache Peers (when using TCP SSO_LOGIN_SERVICE_URL

communication protocol)
SSO_SERVICE_URL
Connection Timeout
TcLocale
LogVolumeName

LogVolumeLocation

Enterprise Application Registration ID

If the PLM Documentation Server and Teamcenter help are installed, set context parameters to
configure online help.

Context parameter Value

RichClientHelpWebServer http://host:port/tdoc/tc/version
host and port are the host name and port of the PLM
Documentation Server. version is the Teamcenter version
or SP level.
RichClientHelpLocation /help
This is the subpath to the Teamcenter online help.

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.

2. 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.

PLM00013 11.2 Windows Server Installation 10-5

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Note

Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names
in URLs wherever possible so the domain name system (DNS) can determine which
IP address to use.
If you must use IP addresses and your network uses IPv6 addresses, enclose the literal
IPv6 address in square brackets, for example:
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc

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.war) generated during installation. This file is in the deployment
directory under the specified staging location.

12. Deploy the web application.3

Note

If your network includes client hosts running on an IPv6 network, the Java EE web tier must
be deployed in an application server that supports an IPv6 URL as an external endpoint and
uses IPv4 addresses to support all communication with the Teamcenter enterprise tier, such as
communication with the Java EE server manager.
A typical environment for the Java EE web tier is a dual-stack machine that supports both
IPv4 and IPv6 addresses in which the application server accepts HTTP requests from either
IPv4 or IPv6.
Teamcenter enterprise tier server components that communicate with other server components
in the same network are assumed to be on an IPv4 network and are not supported on IPv6.
Teamcenter IPv6 support is limited to clients or integrations that use Teamcenter client
communication system (TCCS) and Teamcenter components that communicate with clients
on IPv6-enabled networks.

Related topics

• Web Application Deployment

3. Web Application Deployment provides deployment procedures specific to various supported application servers. Choose the appropriate
procedure for the application server you use.

10-6 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Build additional web applications

Special-use web applications

You can build any number of additional thin client web applications with subsets of solutions suited
to your Teamcenter users. The following table describes some thin client web applications you can
build for certain special use cases.

Feature Application Description

Global Services Global Services application Provides the application directory functionality
directory application required by Global Services.
Global Services Enterprise Provides essential Global Services functionality.
application You can add Global Services connectors and
other components to this application.
Thin client Proxy WAR file for Provides support for WebLogic Express as a
deployed on WebLogic application front-end HTTP listener for the thin client.
WebLogic
Express
Legacy thin client Legacy URL support Upgrades legacy thin client URLs to Teamcenter
support application 11.2. If you are upgrading a previous Teamcenter
installation that includes the thin client, generate
the legacy URL management application.

Install Global Services

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
}

PLM00013 11.2 Windows Server Installation 10-7

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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 11.2 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.

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.

1. Launch the Web Application Manager (insweb.bat).

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:

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.

10-8 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

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
11.2 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.

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

7. Create the Global Services enterprise application:

a. In the Name box, type a name for the application, for example, Global Services Enterprise
Application.

b. Accept the default value for Staging Location or enter a different directory.

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.4

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
11.2 Global Services Framework - Enterprise Application solution.

c. Optionally, select sets of additional solutions according to how you use Global Services:

4. A distributable file is required only if you deploy the web tier application in a cluster configuration.

PLM00013 11.2 Windows Server Installation 10-9

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

If you use these products Select these solutions

Teamcenter 2007 or later Teamcenter 11.2 Global Services Framework -
Teamcenter SOA Connector
Teamcenter Enterprise Teamcenter 11.2 Global Services Framework -
Teamcenter Enterprise Connector
Apache-based web services Teamcenter 11.2 Global Services Framework -
Axis2 Services
JMS messaging Teamcenter 11.2 Global Services Framework -
JMS Messaging
EPSync Manager Teamcenter 11.2 Global Services Framework -
EPSync Reactor
Global Services user interface (for a Teamcenter - Web Tier Infrastructure
configuration that does not contain
standalone user interface solution) Teamcenter 11.2 Global Services Framework -
User Interface
Server-to-server communications Teamcenter 11.2 Global Services Framework -
for global workflow Security Proxy
Global Services orchestration Teamcenter 11.2 Global Services Framework -
Ode BPEL Enterprise Application
Note

This solution must be created and deployed

separately from the Teamcenter 11.2
Global Services Framework - Enterprise
Application solution.
Teamcenter Sourcing Teamcenter 11.2 Global Services Framework -
Teamcenter Sourcing
Teamcenter and Teamcenter Teamcenter 11.2 Global Services Framework -
Enterprise (to share data) Data Exchange
Teamcenter Substance Compliance Teamcenter 11.2 Global Services Framework –
CPM Connector for Substance Compliance

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.

9. If you selected a connector that requires supporting files, click Modify Disk Locations and
add the path to any supporting files.

10. Click OK.

10-10 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

The Web Application Manager displays the Modify Required Context Parameters dialog box.

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:
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.
Note

For a description of these parameters, see Global Services context parameters.

ApplicationInstance TcGSJDBCJNDI
SSOAppID TcGSMessageServerJNDI
LogFileLocation TcGSNotifierReactorJNDI
TcGSBOSJNDI TcGSDORJNDI

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 Global Services context parameters, see Global Services context
parameters.

12. Click OK to begin building the web application.

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.

13. Click Exit to exit the Web Application Manager.

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.
Deploy the web application.5

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:
1. Launch the Web Application Manager (insweb.bat).

2. Click Add to begin creating the web application.

Web Application Manager displays the Add Web Application dialog box.

3. Create the proxy WAR file web application:

5. Web Application Deployment provides deployment procedures specific to various supported application servers. Choose the
appropriate procedure for the application server you use.

PLM00013 11.2 Windows Server Installation 10-11

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

a. In the Name box, type the name of this application, for example, WebLogic Proxy.

b. Accept the default value for Staging Location or enter a different directory.

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.6
Note

Do not change the default solution type (Thin Client) in the Solution Type box.

4. Click OK.
The Web Application Manager displays the Modify Required Context Parameters dialog box.

5. Enter values for the following required context parameters:

Parameter Description
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.

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.

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.

7. Click Exit to exit the Web Application Manager.

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.
Deploy the web application.7

6. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier web application.
7. Web Application Deployment provides deployment procedures specific to various supported application servers. Choose the appropriate
procedure for the application server you use.

10-12 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Migrate legacy thin client URLs

If you migrate web tier applications to Teamcenter 11.2 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 11.2 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 WAR file. For example, if the web tier WAR file is named tc.war, 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.

1. Launch the Web Application Manager (insweb.bat).

2. Click Add.
Web Application Manager displays the Add Web Application dialog box.

PLM00013 11.2 Windows Server Installation 10-13

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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.8
Note

Do not change the default solution type (Thin Client) in the Solution Type box.

4. Click OK.
The Web Application Manager displays the Modify Required Context Parameters dialog box.

5. Enter values for the following required context parameters:

Parameter Description
TcEngLocale Specifies a locale for messages displayed to the user.
This locale must match the locale specified for the
Teamcenter Enterprise Tier web application.
expiryDateOfResource Specifies the date the URL message expires. This
MovedNotification 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.

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.

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. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier web application.

10-14 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

7. Click Exit to exit the Web Application Manager.

8. Locate the deployable file (cgi-bin.war) generated during installation. This file is in the
deployment directory under the specified staging location.
Deploy the web application.9

Note

After installation, you can optionally modify the following context parameters for legacy URL
support:
requestRedirectedTo
replacementFor CGIBIN_IMAN
redirectionWaitTime

Sharing an application server instance for multiple four-tier environments

Teamcenter supports deploying more than one instance of the same Teamcenter web tier application
(WAR file) into one application server instance. Multiple WAR 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 (WAR files) deployed in
a single application server instance.

Client Resource
tier Web tier Enterprise tier tier
Clients Single application server instance Server managers Databases

Client A ←→ http://host:port/tc01 ←→ svrmgr11 ←→ DB1

←→ http://host:port/tc02 ←→ svrmgr2 ←→ DB2
Client 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.

2. Create web applications. 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.

9. The Web Application Deployment provides deployment procedures specific to various supported application servers. Choose the
appropriate procedure for the application server you use.

PLM00013 11.2 Windows Server Installation 10-15

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Context parameter Description

Enterprise Application Identifier for the web application. If you want to deploy
Registration ID multiple Teamcenter web tier applications in a single
application server instance, each application must be
assigned a unique ID.
Enterprise Application Lookup ID Specifies the ID by which the Teamcenter presentation
tier accesses the application identified by the Enterprise
Application Registration ID parameter. If you deploy
your WAR file with other WAR 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 WAR files in the web application server instance.

Note

Multiple WAR file deployment is not supported on JBoss. If you use JBoss as your web
application server, you must deploy each WAR file in a separate application server instance.

Install rich client web applications

Planning rich client distribution

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.

2. Install a rich client distribution instance or 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.

4. Start the distribution server.

10-16 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

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.

• If your network includes client hosts running on an IPv6 network, the Java EE web tier
must be deployed in an application server that supports an IPv6 URL as an external
endpoint and uses IPv4 addresses to support all communication with the Teamcenter
enterprise tier, such as communication with the Java EE server manager.
A typical environment for the Java EE web tier is a dual-stack machine that supports
both IPv4 and IPv6 addresses in which the application server accepts HTTP requests
from either IPv4 or IPv6.
Teamcenter enterprise tier server components that communicate with other server
components in the same network are assumed to be on an IPv4 network and are not
supported on IPv6. Teamcenter IPv6 support is limited to clients or integrations that use
Teamcenter client communication system (TCCS) and Teamcenter components that
communicate with clients on IPv6-enabled networks.

Install the rich client distribution server

1. Expand the rich client over-the-web software distribution image (Teamcenter-version_otw.zip) to
a drive on your local host.

2. Start the Web Application Manager:

a. Browse to the WEB_ROOT 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.

3. Copy web tier solution ICDs:

a. Click Copy ICDs.

b. In the Copy ICD Files dialog box, click Browse.

c. Browse to the icd directory of the Teamcenter 11.2 over-the-web software distribution. Select
the icd directory, and then click Open.
In the Copy ICD Files, click OK to load ICD files.

PLM00013 11.2 Windows Server Installation 10-17

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Note

The Web Application Manager displays a Progress dialog box while it copies ICD files.
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
entered.
If the ICD files are not copied successfully, repeat these steps 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.

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

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

5. In the Name box, type the name of this application, for example, Teamcenter OTW Distribution
Server.

6. 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 install the distribution server software in a directory under the WEB_ROOT
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.

7. Optionally, in the Description box, type a brief description of this distribution server.

8. Click the 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, 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.

10. 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 a through c.

11. Click OK.

The Web Application Manager displays the Modify Required Context Parameters dialog box.

10-18 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

12. 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 Port Specifies the port on which the distribution server 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.

13. Click OK.

The Web Application Manager begins installing the distribution server and displays a Progress
dialog box.

14. When the Progress dialog box indicates that installation is complete, click OK.
The Web Application Manager displays the Teamcenter Web Application Manager dialog
box with the distribution server software you installed listed as an application in the Web
Applications box.

15. 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

Rich client distribution instance requirements

For each unique rich client configuration, you must create a distribution server instance.
Before you build a rich client distribution instance, ensure that the following software is installed
and configured:
• Teamcenter corporate server

• Rich client distribution server

PLM00013 11.2 Windows Server Installation 10-19

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

If you use Security Services with the rich client, make sure Security Services is installed and
configured.
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

Note

If you include Lifecycle Visualization in your rich client distribution instance, and you use
downloaded software images instead of a DVD:
1. Download the version_Vis_ALL.zip file.
Replace version with the current Teamcenter version level.

2. Expand the version_Vis_ALL.zip archive to a directory on your local host.

3. When building your rich client distribution instance, enter the location of this directory
in the context parameter in the Web Application Manager.

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.

• Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names
in URLs wherever possible so the domain name system (DNS) can determine which
IP address to use.
If you must use IP addresses and your network uses IPv6 addresses, enclose the literal
IPv6 address in square brackets, for example:

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

Parameter Description
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.

10-20 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Parameter Description
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 Linux client systems. This
location must be available for Linux client hosts.
RichClientHelpWebServer URL specifying the path to the Teamcenter online help
installed on the PLM Documentation Server. Set this value
to:
http://host:port/tdoc/tc/version
host and port are the host name and port of the PLM
Documentation Server. version is the Teamcenter version
or SP level.
RichClientHelpLocation Set to /help.
This is the subpath to the Teamcenter online help.
HTTPUseGZip Indicates whether the rich client prefers responses
from the Java EE 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.

PLM00013 11.2 Windows Server Installation 10-21

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Parameter Description
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.
JREWindows64Location Specifies the path to the Java Runtime Environment (JRE)
on the client host during installation of the rich client
through the Over-the-Web Installer on 64-bit versions of
Windows.
By default, the Over-the-Web Installer uses the value of the
JRE64_HOME environment variable on the target client
host. Change the value of this context parameter if you
want to specify a different path.
JREUNIXLocation Specifies the path to the Java Runtime Environment (JRE)
on the client host during installation of the rich client
through the Over-the-Web Installer on Linux systems.
By default, the Over-the-Web Installer uses the value of the
JRE_HOME environment variable on the target client host.
Change the value of this context parameter if you want
to specify a different path.

10-22 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

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

Parameter Description
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
installed and configured. You must provide the same
URL used to configure Security Services on the web
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
installed and configured. You must provide the same
URL used to configure Security Services on the web
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.

PLM00013 11.2 Windows Server Installation 10-23

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Rich client optional parameter values

Parameter Description
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

Parameter Description
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.

10-24 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

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

Parameter Description
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 Linux 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 Linux clients.

Teamcenter Integration for NX parameter and table values

Parameter Description
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 Linux client hosts.
Users install the NX application on client hosts using the NX
installation program. This location must be the same for all
Linux 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.

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. Expand the rich client over-the-web software distribution image (Teamcenter-version_otw.zip) to
a drive on your local host.10

10. If you expanded the over-the-web software distribution image when you installed the rich client distribution server, skip this step.

PLM00013 11.2 Windows Server Installation 10-25

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

2. If you use Teamcenter lifecycle visualization, make sure the Lifecycle Visualization software
distribution is available from your host. The Over-the-Web Installerrequires this to install Lifecycle
Visualization viewers.

3. Start the Web Application Manager:

a. Browse to the WEB_ROOT 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.

4. Copy web tier solution ICDs:11

a. Click Copy ICDs.

b. In the Copy ICD Files dialog box, click Browse.

c. Browse to the icd directory of the Teamcenter 11.2 over-the-web software distribution image.
Select the icd directory, and then click Open.
In the Copy ICD Files, click OK to load ICD files.
Note

The Web Application Manager displays a Progress dialog box while it copies ICD files.
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
entered.
If the ICD files are not copied successfully, repeat these steps 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. In the Teamcenter Web Application Manager dialog box, click Add.

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

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

Choose a name that uniquely identifies this web application instance.

7. 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.

11. If you copied solution ICD files when you installed the rich client distribution server, skip this step.

10-26 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

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.

8. Optionally, in the Description box, type a brief description of this instance.

9. Enter software locations:

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

b. In the Add Disk Location dialog box, enter the locations of the following software
distributions. For each location, enter the path in the Disk Location to Add box, and then
click Apply.

• Teamcenter 11.2 over-the-web software distribution image.

• Teamcenter lifecycle visualization software distribution image.

Note

If you install Lifecycle Visualization on multiple platforms, add locations of software

distributions for each platform.

c. Click OK to close the Add Disk Location dialog box.

Note

To modify a location or remove a location from the Disk Locations for Install Images list,
click Modify or Remove.

10. 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/2010/2012 Redistributables
Teamcenter client communication system
Rich Client 4-Tier

11. If you want to include additional solutions in the distribution instance, click Solutions and select
the solutions you want installed with the rich client.

12. When you are satisfied with your selections in the Add Web Application dialog box, click OK.
The Web Application Manager displays the Modify Required Context Parameters dialog box.

13. Enter a value for each parameter and click OK.

PLM00013 11.2 Windows Server Installation 10-27

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Note

• The path specified in the WindowsLocation context parameter must not contain
any of the following special characters:
#~!@$%^&*()_+=
If the WindowsLocation contains any of these characters, the Over-the-Web Installer
fails to install the rich client.

• 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.

• For descriptions of rich client required parameters, see Rich client distribution instance
requirements. The rich client required parameters vary, depending on the solutions
you install with the rich client.

The Web Application Manager displays the Modify Required Table dialog boxes for the
HTTPServerTable and the ParentFSCAddressTable.

14. For each table, type the values for each parameter. To add another row to the table, click Add
Row.
Note

Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names
in URLs wherever possible so the domain name system (DNS) can determine which
IP address to use.
If you must use IP addresses and your network uses IPv6 addresses, enclose the literal
IPv6 address in square brackets, for example:
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc

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

10-28 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Table Description

• 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.

• 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.

Note

If you use Teamcenter client communication system (TCCS), you do not need to supply
values

15. 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 7).

• Creates the manifest file (ds_manifest.mf) in the staging location directory (named in step 7).
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.

16. When the Progress dialog box indicates that installation is complete, click OK.
The Web Application Manager displays the Teamcenter Web Application Manager dialog box.

17. Click Exit to exit the Web Application Manager.

To make the rich client distribution instance available to client hosts, deploy the distribution instance
on a supported web application server.

PLM00013 11.2 Windows Server Installation 10-29

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

Configuring TCCS, Security Services, and proxy settings

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 handle
Switch 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.

10-30 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Context Parameter Description

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.

PLM00013 11.2 Windows Server Installation 10-31

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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

Note

Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names in
URIs and URLs wherever possible so the domain name system (DNS) can determine
which IP address to use.
If you must use IP addresses and your network uses IPv6 addresses, enclose the literal
IPv6 address in square brackets, for example:
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc

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

1. Launch the Web Application Manager.

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.

5. Exit the Web Application Manager and redeploy the rich client distribution instance.

Installing and configuring Security Services is described in Security Services

Installation/Customization.

Related topics
• Installing Security Services

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:

10-32 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

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 distribution server instance

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 hardware and software certifications
page on GTAC.
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

PLM00013 11.2 Windows Server Installation 10-33

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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 provided by the web server vendor.
The following examples use the name of the instance for the web component directory name:

10-34 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Web server Deployment

Apache HTTP Server 1. In the conf configuration file, find the HTTP document 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
Sun Java System 1. In the config configuration file, find the HTTP document root directory.
For example:
<VARS docroot="document-root-path">

2. Create the instance-name directory under the HTTP document base

directory.

3. Copy the rich client web components to the instance-name directory.

4. Publish the following URL:

http://host-name/instance-name/otw.html
IBM WebSphere 1. Find the document root directory (HTTP server core settings in the
administration server console).

2. Create the instance-name directory under the HTTP document root

directory.

3. Copy the web components to the instance-name directory.

4. Publish the following URL:

http://host-name/instance-name/otw.html
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:

http://host-name/instance-name/otw.html

PLM00013 11.2 Windows Server Installation 10-35

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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

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.

10-36 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

The operating system facilities stop the RMI registry server.

Managing the rich client distribution server and instances

Change the distribution server contents

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.

1. 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.

Add components to the distribution server instance

1. Launch 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 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.

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

5. In the Web Applications list, select the distribution server instance you want to add components
to and click Modify.
The Web Application Manager displays the Modify Web Application dialog box.

6. Click Modify Disk Locations.

The Web Application Manager displays the Modify Disk Locations dialog box.

PLM00013 11.2 Windows Server Installation 10-37

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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

• The required rich client parameters vary, depending on the applications you are
installing with the rich client instance.

• 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 Progress
dialog box.

11. When installation is complete, click OK to close the Progress dialog box.
The Web Application Manager displays the Modify Web Application 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.

10-38 Windows Server Installation PLM00013 11.2

 Java EE web tier installation

Note

For descriptions of the optional parameters, see Rich client optional parameter values.

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

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:

PLM00013 11.2 Windows Server Installation 10-39

 Chapter
Chapter 10:10:Java Java EE tier
EE web webinstallation
tier installation

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

10-40 Windows Server Installation PLM00013 11.2

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.

Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Install the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Installing a custom solution or third-party template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Install EDA server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Installing Teamcenter reporting and analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

PLM00013 11.2 Windows Server Installation

Chapter 11: Installing the server manager

Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Install the .NET server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Install the Java EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

Start the .NET-based server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Launch the Teamcenter Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8

PLM00013 11.2 Windows Server Installation

Chapter 11: Installing the server manager

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.
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.

1. 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.jgroups.org/.

PLM00013 11.2 Windows Server Installation 11-1

 Chapter
Chapter 11:11:Installing
Installing the server
the server manager
manager

Data Description
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 running.
This method reduces pinging and thereby improves
performance.

11-2 Windows Server Installation PLM00013 11.2

 Installing the server manager

Data Description

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 processes Target number of server processes to be available in this pool
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).

PLM00013 11.2 Windows Server Installation 11-3

 Chapter
Chapter 11:11:Installing
Installing the server
the server manager
manager

If you create a new Teamcenter configuration, launch TEM from the Teamcenter software
distribution image. If you want to add the .NET-based server manager to an existing configuration,
launch TEM in maintenance mode.

2. Proceed to 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 Multiplexing Proxy (MUX) panel.
Note

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

4. In the Multiplexing Proxy panel, accept the default values or type new values for the Teamcenter
multiplexing proxy (MUX).

Value Description
Port Specifies the TCP/IP port on which the MUX listens
for web tier requests. This is the Jetty server
connector port.
TECS Admin Port Specifies the port used by the Teamcenter Enterprise
Communication System (TECS).

Note

The MUX listens on a single port for incoming requests from the web tier, forwarding
those requests to an appropriate Teamcenter server using operating system named-pipe
communication protocol, and then streaming the response back to web tier. The MUX runs
as an application within the Teamcenter Enterprise Communication System (TECS). The
TECS container is based on the Teamcenter client communication system (TCCS)
container used in the client tier.

5. Proceed to the .NET Server Manager panel.

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 Specify 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.

For information about other .NET server manager values, click the help button .

2. For information about installing a Teamcenter corporate server, see Install a Teamcenter corporate server.

11-4 Windows Server Installation PLM00013 11.2

 Installing the server manager

6. In the Server Manager Performance Tuning panel, enter values for the following required
parameters:

Parameter Description
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.
Target Servers 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. In the TcServer Character Encoding Settings panel, make sure the values reflect the character
set you use for Teamcenter. If you are not sure, accept the default settings.

8. Proceed through remaining panels until you reach the Confirmation panel. Click Start to begin
installing the Teamcenter server with the .NET server manager.

9. When installation completes, exit TEM.

Install the Java EE server manager

1. Launch Teamcenter Environment Manager (TEM).
If you create a new Teamcenter configuration, launch TEM from the Teamcenter software
distribution image. If you want to add the Java EE server manager to an existing configuration,
launch TEM in maintenance mode.

2. Proceed to the Features panel. Under Server Enhancements, select Java EE based Server
Manager.

PLM00013 11.2 Windows Server Installation 11-5

 Chapter
Chapter 11:11:Installing
Installing the server
the server manager
manager

3. Proceed to the TcServer Character Encoding Settings panel. Make sure the values reflect the
character set you use for Teamcenter. If you are not sure, accept the default settings.

For information about the values in this panel, click the help button .

4. In the Multiplexing Proxy panel, accept the default values or type new values for the Teamcenter
multiplexing proxy (MUX).

Value Description
Port Specifies the TCP/IP port on which the MUX listens
for web tier requests. This is the Jetty server
connector port.
TECS Admin Port Specifies the port used by the Teamcenter Enterprise
Communication System (TECS).

Note

The MUX listens on a single port for incoming requests from the web tier, forwarding
those requests to an appropriate Teamcenter server using operating system named-pipe
communication protocol, and then streaming the response back to web tier. The MUX runs
as an application within the Teamcenter Enterprise Communication System (TECS). The
TECS container is based on the Teamcenter client communication system (TCCS)
container used in the client tier.

5. Proceed to the Communication Configuration panel and enter the required values:
a. In the Pool ID and JMX RMI Port boxes, type a name and port for the server pool.

b. In the Assignment Service Port box, type a port number for the server manager assignment
service.

c. In the Server Host box, type the logical host name of the server manager host. This value
allows you to control which IP address is used when connecting to Teamcenter servers.

d. Under Startup Mode, select one of the following:

• Service/Daemon
Specifies you want to run the server manager as a Windows service. This is the default
mode.

• Command Line
Specifies you want to run the server manager manually from a command line.

Enter remaining values as needed in the Server Manager for Java EE panel. For more

information about fields in this panel, click the help button .

6. Proceed to the Server Manager TreeCache Configuration panel.

Enter required values for the server manager TreeCache configuration or accept the default
values shown.

11-6 Windows Server Installation PLM00013 11.2

 Installing the server manager

7. Proceed through remaining panels to the Confirmation panel. Click Start to begin installing the
Teamcenter server with the Java EE-based server manager.

8. When installation completes, exit TEM.

9. After you install the Java EE server manager, install the Teamcenter Management Console using
the appropriate steps for Windows platforms.

You can install multiple Java EE server manager services on the same host. Each server manager
service has its own configuration directory:
TC_ROOT\pool_manager\confs\config-name
Replace config-name with the name of the server manager configuration.
The server manager configuration directory contains configuration files, log files, and server manager
scripts. These include the following.

File/Directory Description
mgrstart Script that launches the Java EE server manager in console mode.
mgrstop Script that stops the Java EE server manager when started from a
command line.
If you run the Java EE server manager as a Windows service, stop
the service using the Windows services manager.
Note

You can also stop the server manager using the Teamcenter
Management Console.
mgr.output If you run the Java EE server manager as a Windows service, this
file contains all output from the Java EE server manager.
This file is not used if you run the server manager from the command
line.
logs Directory that contains all Java EE server manager log files.

If you run the Java EE server manager as a Windows service, the server manager starts automatically.
Note

If you experience connection delays during server manager startup, see the available
troubleshooting solutions.

Related topics
• Server manager

PLM00013 11.2 Windows Server Installation 11-7

 Chapter
Chapter 11:11:Installing
Installing the server
the server manager
manager

Start the server manager

Start the .NET-based server manager

If you install the .NET based Server Manager feature, you must start the server manager to enable
four-tier rich clients to connect to the corporate server.
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 11.2→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. 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.

Tip

You can view the .NET server manager with the .NET server manager administrative interface.

Launch the Teamcenter Management Console

Start the Teamcenter Management Console using the appropriate steps for Windows platforms.

3. You can change a service's startup type in the Services dialog window in the Windows Control Panel.

11-8 Windows Server Installation PLM00013 11.2

Chapter 12: Install the Business Modeler IDE

PLM00013 11.2 Windows Server Installation

Chapter 12: 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, so that Business Modeler IDE has enough memory to run.
Before running TEM, you must have the proper version of JRE installed and have set the JRE_HOME
environment variable or the JRE64_HOME environment variable.
Note

The Business Modeler IDE can be installed on Windows, SUSE Linux, and Red Hat Linux
systems.

Caution

Never install the Business Modeler IDE on the same machine as the corporate server. Doing
so could have unintended consequences, especially during upgrade. Always install the
Business Modeler IDE on a separate machine.

PLM00013 11.2 Windows Server Installation 12-1

Chapter 13: Installing a custom solution or third-party template

Installing a custom solution or third-party template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Install a template using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Update the database using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

PLM00013 11.2 Windows Server Installation

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. You can also use this procedure to install a third-party template.
Note

You can also install a template using the tem command line utility, for example:
tem -install -features=feature-name -path=location-of-template-files -pass=password

Warning

You should on a regular basis so that you can restore it in the event of a template installation
failure.

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 Linux, 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.

PLM00013 11.2 Windows Server Installation 13-1

 Chapter
Chapter 13:13:Installing
Installing a custom
a custom solution
solution or third-party
or third-party template
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.

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 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.

13-2 Windows Server Installation PLM00013 11.2

 Installing a custom solution or third-party template

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.

12. In the Confirmation panel, click Start. The new template is installed.

PLM00013 11.2 Windows Server Installation 13-3

 Chapter
Chapter 13:13:Installing
Installing a custom
a custom solution
solution or third-party
or third-party template
template

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
LD_LIBRARY_PATH (Solaris or Linux) or LIBPATH (AIX), 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 in the Teamcenter Environment
Manager (TEM).
Note

You can also update a template using the tem command line utility, for example.
tem -update -full
-templates=template-name-1,template-name-2 -path=location-of-template-files -pass=password

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.

4. In the Configuration Maintenance panel, choose Perform maintenance on an existing

configuration and click Next.

13-4 Windows Server Installation PLM00013 11.2

 Installing a custom solution or third-party template

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.

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 .

PLM00013 11.2 Windows Server Installation 13-5

 Chapter
Chapter 13:13:Installing
Installing a custom
a custom solution
solution or third-party
or third-party template
template

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.

13-6 Windows Server Installation PLM00013 11.2

Chapter 14: Manufacturing

Introduction to Manufacturing installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Installing and configuring the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . 14-1

Configure Manufacturing Resource Library users, groups, and roles . . . . . . . . . . . . . . . . 14-1
Install the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Import part family templates when you use custom item IDs . . . . . . . . . . . . . . . . . . . . . 14-6
Configure NX Library using the installation wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Configure the NX Library when using a shared MACH directory . . . . . . . . . . . . . . . . . . . 14-7
Configure graphics builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8

Updating the Manufacturing Resource Library from an earlier version . . . . . . . . . . . . . . . . . . 14-9

Update the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Deleted classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11

Planning data migration from Genius4000 to Resource Manager . . . . . . . . . . . . . . . . . . . . 14-12

PLM00013 11.2 Windows Server Installation

Chapter 14: Manufacturing

Introduction to Manufacturing installation

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.

Installing and configuring the Manufacturing Resource Library

Configure Manufacturing Resource Library users, groups, and roles

If you have already defined your own database user, group, and role settings in the Organization
application, you can use those existing users to populate the Manufacturing Resource Library (MRL).
If not, run the MRL installation setup to populate the following user structure.

Perform the following task before installing the Manufacturing Resource Library.
Note

Before you begin this task, in the Organization application, ensure that a default volume is
assigned to the application user that you specify in this installation procedure.

1. In the resource_management directory, click Setup.exe.

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.

PLM00013 11.2 Windows Server Installation 14-1

 Chapter
Chapter 14:14:Manufacturing
Manufacturing

3. Click Next.
Teamcenter displays the Setup Type Selection dialog box.

4. Select Manufacturing Resources — Configure MRL Users and click Next.

Tip

Press the F1 key to see the help for each page in the installation wizard.

5. Click Next.
Teamcenter displays the Choose TC_ROOT Directory dialog box.

6. Select one or more of the following:

• Create and Configure TC/MRL Users
Creates and configures MRL-specific users:

CAMUser01
Planner01
TOOLAdmin01
MFGAdmin01

• Create Manufacturing Admin User in DBA Group

Creates and configures the MFGAdmin01 user in the dba group.

• Assign Manufacturing Applications to MRL Users

Assigns the created MRL users to Teamcenter applications as follows.

CAMUser01: Part Planner, Resource Manager

Planner01: Classification, Part Planner, Resource Manager

TOOLAdmin01: Resource Manager

MFGAdmin01: Organization, Classification Admin, Classification, Part Planner,

Resource Manager

7. Select 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.
Teamcenter requires two types of user accounts to configure the ownership of MRL objects
correctly: an administrative account and an application user account. The administrative user is
used to populate the database with the classification hierarchy. The application user account is
used to import sample resources and part family templates.

8. Enter the name, password, and group of valid Teamcenter logon accounts.

9. Click Next and complete the user configuration.

14-2 Windows Server Installation PLM00013 11.2

 Manufacturing

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.
Before you begin with the MRL installation, you must configure the users, groups, and roles in
the database .
To populate the Manufacturing Resource Library on the Teamcenter server:
1. In the advanced_installations directory in the Teamcenter software distribution image, locate
the advanced_installations.zip file and unzip it to a local 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. In the resource_management directory, click Setup.exe.

Teamcenter displays the Teamcenter Configuration Setup dialog box.

3. Click Next.
Teamcenter displays a notification that you must check for the most recent version of the
resource library.

4. Click Next.
Teamcenter displays the Setup Type Selection dialog box.

5. Select Manufacturing Resources — Database Population.

6. Click Next.
Teamcenter displays the Choose TC_ROOT Directory dialog box.

7. 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.

8. 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.

9. Enter the user name, password, and group of two valid Teamcenter logon accounts in the next
two steps.
Teamcenter requires two types of user accounts to configure the ownership of MRL objects
correctly: an administrative account and an application user account. The administrative user is

PLM00013 11.2 Windows Server Installation 14-3

 Chapter
Chapter 14:14:Manufacturing
Manufacturing

used to populate the database with the classification hierarchy. The application user account is
used to import sample resources and part family templates.
Teamcenter uses the application account to populate the database with Manufacturing Resource
Library (MRL) data such as sample resources items. This user is the owner of the content
including sample data for tools, machines, and fixtures. If part family templates (PFTs) are
imported, the PFT items are also owned by this user. This is important to consider as only users
in the same group are able to create part family members (generate 3D models).

10. Click Next.

Teamcenter displays the Manufacturing Resource Library — Content Selection dialog box.

11. Specify which types of data you want to load. You can choose from the following:
• Tools (Assemblies and Components)

• Machines

• Fixtures

• Factory Resources

• Factory Conveyors

• Factory Robots

• Factory Weld Guns

• Machining Data Library

• Manufacturing Process Setups

• Vendor Catalogs

12. Click Next.

Teamcenter displays the Load CLASS HIERARCHY for Module(s) dialog box.

13. 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.

14. Click Next.

15. If you chose to load the tools module, specify whether to import GCS data.
This step loads the guided component search rules required to identify matches in a guided
component search in Resource Manager.
Teamcenter displays the Load SAMPLE DATA for Module(s) dialog box.

16. Select the sample data to be imported into the database and click Next.
Teamcenter displays the Support GRAPHIC BUILDER dialog box.

14-4 Windows Server Installation PLM00013 11.2

 Manufacturing

17. 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 9. When
users create graphics in the Classification application, they must belong to the same group
specified here.
Note

If your company uses custom item IDs, you cannot use the installer to import the part
family templates. You must import them using scripts delivered with the installation image.

18. Click Next.

Teamcenter displays the Set ITEM TYPE dialog box.

19. 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 NC Tool Tools (components,
assemblies) ,
Mfg0MENCMachine NC Machine Machines
,
Mfg0MEResource Resource Fixtures, devices
,
Mfg0MEEquipment Equipment Factory resources
,
Mfg0MERobot Robot Factory robots
,
Mfg0Conveyor Conveyor Factory conveyors
Resource ,

20. Click Next.

Teamcenter displays the Set ITEM TYPE dialog box again with new item types.

21. Enter the item types for weld guns and robots and click Next.
Teamcenter displays the Overwrite Existing Data dialog box.

PLM00013 11.2 Windows Server Installation 14-5

 Chapter
Chapter 14:14:Manufacturing
Manufacturing

22. 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.

23. Click Next.

Teamcenter displays the Confirmation dialog box.

24. Confirm that all your selections are correct and then click Start.
Teamcenter installs the specified classification hierarchies and data into your database.

Import part family templates when you use custom item IDs
By default, the Manufacturing Resource Library installer creates items that are associated with the
part family template that have the same ID as the name of the part family template. If your company
uses custom IDs, you cannot use the installer to import the part family templates. You must import
them using scripts delivered with the installation image.
1. Locate the scripts in the following directory:
advanced_installations\resource_management\MRL\PartFamilyTemplates

2. Rename the part family templates located in the Parts subdirectory to reflect your custom
item IDs.

3. Adjust the PFT_3_Sample_TC101_assign_pfts.bat script to reflect the new IDs.

4. Adjust the PFT_MRL_import_one_pft.bat script and specify the correct user, password, and
group.

5. Run the PFT_0_MRL_PartFamily_Templates.bat script to install the part family templates

with the new IDs.

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.
1. In the advanced_installations directory in the Teamcenter software distribution image, locate
the advanced_installations.zip file and unzip it to a local 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.

14-6 Windows Server Installation PLM00013 11.2

 Manufacturing

2. In the resource_management directory, click Setup.exe.

Teamcenter displays the welcome dialog box for the Manufacturing Resource Library installer.
Proceed to the Setup Type Selection dialog box.

3. Click Configure NX-CAM.

Teamcenter displays the NX Base Directory dialog box.

4. Enter the path to the directory where NX is installed (UGII_BASE_DIR) and click Next.
Teamcenter displays the LANGUAGE Selection dialog box.

5. Select the language in which you want the NX Library selection dialog boxes to appear and
click Next.
Teamcenter displays the Confirmation dialog box.

6. 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.

7. 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:

PLM00013 11.2 Windows Server Installation 14-7

 Chapter
Chapter 14:14:Manufacturing
Manufacturing

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.

Configure graphics builder

To use the following features in Teamcenter, you must configure the NX graphics builder:
• Part family member creation

• NX auto assembly

• 3D model import for catalog data

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.
Teamcenter displays the Setup Type Selection dialog box.

3. Select Configure Fixture TCL Graphic Macros.

4. Click Next.
Teamcenter displays the Choose TC_ROOT Directory dialog box.

5. 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.

6. 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.

7. Enter the user name, password, and group of a valid Teamcenter administrative login account.

14-8 Windows Server Installation PLM00013 11.2

 Manufacturing

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.
The installation procedure modifies the NXGraphicsBuilder preference and copies required files
into Teamcenter directories (TC_ROOT\bin\nx_graph\TCL_Create_Graphics).

9. Verify that this path is the correct path or modify it by clicking Browse.
Teamcenter displays the Confirmation dialog box.

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

Update the Manufacturing Resource Library

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:
1. In the advanced_installations directory in the Teamcenter software distribution image, locate
the advanced_installations.zip file and unzip it to a local directory.

2. In the resource_management directory, click Setup.exe.

Teamcenter displays the Teamcenter Configuration Setup dialog box.

3. Click Next.
Teamcenter displays a notification that you must check for the most recent version of the
resource library.

4. Click Next.
Teamcenter displays the Setup Type Selection dialog box.

5. Select Manufacturing Resources – Database Population.

6. Click Next.
Teamcenter displays the Choose TC_ROOT Directory dialog box.

PLM00013 11.2 Windows Server Installation 14-9

 Chapter
Chapter 14:14:Manufacturing
Manufacturing

7. Select 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.

8. Select 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.

9. Enter the user name, password, and group of a valid Teamcenter login account.
The plmxml_import utility uses this logon information to import the data into the Teamcenter
database.

10. Click Next.

Teamcenter displays the Manufacturing Resource Library – Content Selection dialog box.

11. 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)

12. 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.

13. 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.

14. 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-10 Windows Server Installation PLM00013 11.2

 Manufacturing

15. Click Next.

Teamcenter displays the Import Guided Component Search (GCS) Data dialog box.

16. Click Yes to load the guided component search (GCS) data or No to ignore this step.
Teamcenter displays the Confirm Selections dialog box.

17. Confirm that all your selections are correct and then click Start.
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

• Removes obsolete classes and attributes

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

PLM00013 11.2 Windows Server Installation 14-11

 Chapter
Chapter 14:14:Manufacturing
Manufacturing

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 onward, 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 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.

14-12 Windows Server Installation PLM00013 11.2

 Manufacturing

For more information about using the migration utility, see the Installation on Windows Servers Guide
in the Teamcenter 8.x (or earlier) installation.

PLM00013 11.2 Windows Server Installation 14-13

Chapter 15: Install EDA server support

Install EDA server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

PLM00013 11.2 Windows Server Installation

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.

1. Launch Teamcenter Environment Manager. In the Windows start menu, click

Programs→Teamcenter 11.2, and then right-click Environment Manager and 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.

• 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:

PLM00013 11.2 Windows Server Installation 15-1

 Chapter
Chapter 15:15:Install
Install
EDA EDA server
server support
support

• Java EE 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.

Note

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

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).

15-2 Windows Server Installation PLM00013 11.2

Chapter 16: Installing Teamcenter reporting and analytics

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-4

Deploy Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4

Complete Reporting and Analytics installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5

PLM00013 11.2 Windows Server Installation

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.
After you complete these steps and install Reporting and Analytics, you can begin using the Reporting
and Analytics integration in Report Builder.

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.
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.

PLM00013 11.2 Windows Server Installation 16-1

 Chapter
Chapter 16:16:Installing
Installing Teamcenter
Teamcenter reporting
reporting and analytics
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.

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.

16-2 Windows Server Installation PLM00013 11.2

 Installing Teamcenter reporting and analytics

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 Enter the location of the Reporting and
server Settings 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.
Create WAR file TcRA Authentication Select the Reporting and Analytics
Settings 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.
Create WAR file TcRA License Settings Type the host and port of the Reporting and
Analytics license server.

PLM00013 11.2 Windows Server Installation 16-3

 Chapter
Chapter 16:16:Installing
Installing Teamcenter
Teamcenter reporting
reporting and analytics
and analytics

Selected option TEM panel Tasks

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.

16-4 Windows Server Installation PLM00013 11.2

 Installing Teamcenter reporting and analytics

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 preference with
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.

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.

PLM00013 11.2 Windows Server Installation 16-5

 Chapter
Chapter 16:16:Installing
Installing Teamcenter
Teamcenter reporting
reporting and analytics
and analytics

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.

16-6 Windows Server Installation PLM00013 11.2

Chapter 17: Installing Render Management

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

PLM00013 11.2 Windows Server Installation

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.

PLM00013 11.2 Windows Server Installation 17-1

Part VI: Additional configuration and maintenance

Create additional Teamcenter configurations, apply patches, or uninstall Teamcenter as described in

the appropriate topics.

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Deploying localized versions of Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Creating a custom distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

PLM00013 11.2 Windows Server Installation

Chapter 18: Managing installations and configurations

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Create a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Modify a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

Add an existing Teamcenter database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3

Add or configure a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4

Change the Oracle password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5

How to change the Oracle password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Encrypt the password file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Encrypt the database connection string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6

Configure multiple databases for a four-tier rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7

Multiple database overview (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Multiple database example (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Step 1: Install the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Step 2: Deploy the web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Step 3: Configure the rich client instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-10

Migrate Teamcenter to a different JRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11

PLM00013 11.2 Windows Server Installation

Chapter 18: 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 (TEM) 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.

Caution

If you create a desktop shortcut to TEM, make sure the working directory (or Start in location)
for the shortcut is TC_ROOT\install. If the working directory for the shortcut is incorrect, TEM
displays errors during installation or updating of a configuration.

Create a configuration
1. Launch Teamcenter Environment Manager (TEM). In the Windows start menu, choose
Programs→Teamcenter 11.2, and then right-click Environment Manager and choose Run as
administrator.

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.

• If you create a desktop shortcut to TEM, make sure the working directory (or Start in
location) for the shortcut is TC_ROOT\install. If the working directory for the shortcut
is incorrect, TEM displays errors during installation or updating of a configuration.

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 the solutions reference.

PLM00013 11.2 Windows Server Installation 18-1

 Chapter
Chapter 18:18:Managing
Managing installations
installations and configurations
and configurations

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).

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 the features reference.

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:
1. Launch Teamcenter Environment Manager. In the Windows start menu, click
Programs→Teamcenter 11.2, and then right-click Environment Manager and choose Run as
administrator.
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 select Run
as administrator.

2. In the Maintenance panel, choose Configuration Manager.

3. In the Configuration Maintenance panel, choose Perform maintenance on an 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 panel vary depending on the features in your
configuration.

6. In the Features panel, select features to add to the configuration, or deselect features you
want to remove.

18-2 Windows Server Installation PLM00013 11.2

 Managing installations and configurations

Note

If you remove a feature that added data model objects to the Teamcenter database, the
data model is not removed when you remove the feature. Relations and objects created
using the removed feature persist in the database.
If no instances of the feature's data model objects were created in the database, you can
attempt to remove the template. For more information, see How to remove a template in
the latest version of the Business Modeler IDE Best Practices Guide at the Teamcenter
documentation site on GTAC.

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.

1. Launch Teamcenter Environment Manager. In the Windows start menu, choose

Programs→Teamcenter 11.2, and then right-click Environment Manager and choose Run as
administrator.

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 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.

PLM00013 11.2 Windows Server Installation 18-3

 Chapter
Chapter 18:18:Managing
Managing installations
installations and configurations
and configurations

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.
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.

7. In the Teamcenter Administrative User panel, enter the password for the Teamcenter
administrator.
Caution

The password must not be empty nor contain any whitespace characters such as space,
tab, newline, carriage return, form feed, or vertical tab.
In addition, the password must 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 , MS SQL Server, or Oracle).

• A database instance must exist, either a specific instance configured for Teamcenter or a
multipurpose instance to be configured in this procedure.

1. Launch Teamcenter Environment Manager. In the Windows start menu, choose

Programs→Teamcenter 11.2, and then right-click Environment Manager and choose Run as
administrator.
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 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.)

18-4 Windows Server Installation PLM00013 11.2

 Managing installations and configurations

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.
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.
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.

7. In the Teamcenter Administrative User panel, enter the password for the Teamcenter
administrator.
Caution

The password must not be empty nor contain any whitespace characters such as space,
tab, newline, carriage return, form feed, or vertical tab.
In addition, the password must not contain any of the following characters:
!@$%=&'":;.<>(){}

8. In the Confirmation panel, review your selections and click Start to add the database.

Change the Oracle password

How to change the Oracle password
If you use an Oracle database and want to change the password Teamcenter uses to connect to
the database, you can do this two ways using the install utility:
• Encrypt the password file using the -encryptpwf argument.

• Encrypt the database connection string using the -encrypt argument.

Encrypt the password file

To encrypt a password file, you set a temporary environment variable to the password you want to
encrypt, and then generate an encrypted password file using the -encryptpwf argument for the
install utility.
1. Open a Teamcenter command prompt.

2. Create a temporary environment variable and set it to the password you want to encrypt:
set variable-name=password

For example:

PLM00013 11.2 Windows Server Installation 18-5

 Chapter
Chapter 18:18:Managing
Managing installations
installations and configurations
and configurations

set temp_pw=mypassword

Note

For security, choose a unique and obscure name for the environment variable, and delete
the variable promptly after completing this procedure.

3. Type the following command:

install -encryptpwf —e=variable-name —f=password-file

Replace variable-name with the name of the environment variable you created. Replace
password-file with the path and name of the password file to create. For example:
install -encryptpwf —e=temp_pw —f=pwd.txt

This command generates an encrypted password file that can be used for connecting to the
Teamcenter database. The password file can also be used with Teamcenter utilities that use
the password file (-pf) argument.

4. Delete the temporary environment variable you created in step 2.

Caution

This step is important for security.

Encrypt the database connection string

To encrypt the database connection string, you must temporarily set the TC_DB_CONNECT
environment variable and then re-encrypt the connection string using the -encrypt argument for
the install utility.
1. Open a Teamcenter command prompt.

2. Set the TC_DB_CONNECT environment variable:

set TC_DB_CONNECT=”db-user:password@database-ID”

Replace db-user with the database user name (the Oracle user). Replace password with the new
database password. Replace database-ID with the Oracle database name.

3. Type the following command:

install -encrypt

This command generates a new database connection string with the new Oracle password
encrypted . Copy the new database connection string.

4. Open the TC_DATA\tc_profilevars.bat file in a plain text editor.

5. Locate the following line in the file:

set TC_DB_CONNECT=connection-string

6. Replace the existing connection-string with the string generated by the install -encrypt command.

7. Save the changes to the tc_profilevars.bat file.

18-6 Windows Server Installation PLM00013 11.2

 Managing installations and configurations

Configure multiple databases for a four-tier rich client

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 WAR 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.

PLM00013 11.2 Windows Server Installation 18-7

 Chapter
Chapter 18:18:Managing
Managing installations
installations and configurations
and configurations

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)

Step 1: Install the corporate server

To enable a rich client to access two databases, install and configure two corporate servers:
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).

18-8 Windows Server Installation PLM00013 11.2

 Managing installations and configurations

• 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>
<multisiteimport siteid="othersite">
<defaultfscimport fscid="otherfsc" fscaddress="host:4444" priority=”0”/>
<volumeimport volumeid="othervol" />
</fscimport>
</multisiteimport>

Revised:
<fmsworld>
<multisiteimport siteid="othersite">
<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>

PLM00013 11.2 Windows Server Installation 18-9

 Chapter
Chapter 18:18:Managing
Managing installations
installations and configurations
and configurations

e. On TcHost1, stop and restart the FSC service.

Step 2: Deploy the web tier

Deploy and configure the web tier WAR files to connect to the server managers:
1. Generate the web tier WAR 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: ClusterTcData1 TreeCache cluster name: ClusterTcData1
TreeCache mode: TCP TreeCache mode: TCP

2. Generate the web tier WAR 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: ClusterTcData2 TreeCache cluster name: ClusterTcData2
TreeCache mode: TCP TreeCache mode: TCP

Note

Make sure you choose distinct sets of ports for each WAR file.

3. Deploy each web tier WAR file in a third-party application server in a separate domain.

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:
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:

1. 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.jgroups.org.

18-10 Windows Server Installation PLM00013 11.2

 Managing installations and configurations

URI Name
http://appserver:7001/tc/webclient TcData1
http://appserver:7002/tc/webclient TcData2

Migrate Teamcenter to a different JRE

The Java Runtime Environment (JRE) used by Teamcenter and Teamcenter Environment Manager
(TEM) is set by TEM during Teamcenter installation. If you upgrade or install a new JRE, you must
migrate Teamcenter to the new JRE using TEM.

Caution

Do not remove your previous JRE until after you complete migrating Teamcenter to the
new JRE. If you removed your old JRE before performing this procedure, problems or error
messages may occur, and TEM cannot start.

To change the JRE used by Teamcenter and TEM, perform the following steps.

1. Start Teamcenter Environment Manager (TEM):

Start→Programs→Teamcenter 11.2→Environment Manager

Alternatively, you can run the tem.bat file in the install directory in the application root directory
for the Teamcenter installation.

2. In the Maintenance panel, select Migrate Teamcenter to another JRE and then click Next.

3. The Migrate Teamcenter to another JRE panel lists Teamcenter services that depend on the
JRE and must be shut down before the migration can begin.

After you make sure these services are shut down, select All features from the above list
have been shut down, and then click Next.

4. In the JRE Location panel, enter the path to the JRE you want Teamcenter to use.

Caution

Make sure you specify a 64-bit JRE.

Note

Depending on the features in your configuration, TEM may prompt you for the operating
system user password.

5. In the Confirmation panel, click Start to migrate Teamcenter to the specified JRE.

If you encounter problems migrating Teamcenter to the new JRE, see the available troubleshooting
solutions.

PLM00013 11.2 Windows Server Installation 18-11

Chapter 19: Deploying localized versions of Teamcenter

Deploying localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Deploying thin client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Update thin client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Create a thin client localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Convert the thin client user interface for Hebrew . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Deploying rich client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Deploy rich client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Display Siemens PLM Software-provided rich client localizations . . . . . . . . . . . . . . . 19-4
Update rich client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4

Configuring client display language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5

Choose a display language for the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Choose a display language for the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Choose the default language for the Teamcenter server process . . . . . . . . . . . . . . . . . . 19-8
Add multibyte character support in an English rich client . . . . . . . . . . . . . . . . . . . . . . . . 19-8

PLM00013 11.2 Windows Server Installation

Chapter 19: Deploying localized versions of Teamcenter

Deploying localizations
Deploying thin client localizations

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.war) 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"?>

PLM00013 11.2 Windows Server Installation 19-1

 Chapter
Chapter 19:19:Deploying
Deploying localized
localized versions
versions of Teamcenter
of Teamcenter

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>1

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.war) .

Deploy the application in an application server.

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.

1. he is the standard W3C code for Hebrew.

19-2 Windows Server Installation PLM00013 11.2

 Deploying localized versions of Teamcenter

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.
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 rich client localizations

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

PLM00013 11.2 Windows Server Installation 19-3

 Chapter
Chapter 19:19:Deploying
Deploying localized
localized versions
versions of Teamcenter
of Teamcenter

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/

Related topics
• Teamcenter Localization

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.

19-4 Windows Server Installation PLM00013 11.2

 Deploying localized versions of Teamcenter

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 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/

Configuring client display language

Choose a display language for the thin client

By default, the thin client displays in the language specified by your operating system locale settings.
If you want to override the default language, you can choose the 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://myhost:7001/tc/webclient?lang=fr in the URL.

o To specify Russian, type http://myhost:7001/tc/webclient?lang=ru in the URL.

PLM00013 11.2 Windows Server Installation 19-5

 Chapter
Chapter 19:19:Deploying
Deploying localized
localized versions
versions of Teamcenter
of Teamcenter

Note

o When specifying a language in the URL, use standard W3C locale identifiers.

o Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names
in URLs wherever possible so the domain name system (DNS) can determine which
IP address to use.
If you must use IP addresses and your network uses IPv6 addresses, enclose the
literal IPv6 address in square brackets, for example:

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

• 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.

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.
You can also configure language display during Teamcenter installation.

19-6 Windows Server Installation PLM00013 11.2

 Deploying localized versions of Teamcenter

Choose a display language for the rich client

By default, the rich client is displayed in the language specified by the operating system. If you want
to override the default language, you can choose the display language for the rich client.
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.

• 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.
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 supported
locale codes.
For example, to run the rich client Italian user interface:
D:\tc\rac\portal.bat

becomes:
D:\tc\rac\portal.bat —nl it_IT

PLM00013 11.2 Windows Server Installation 19-7

 Chapter
Chapter 19:19:Deploying
Deploying localized
localized versions
versions of Teamcenter
of Teamcenter

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).

Choose the default language for the Teamcenter server process

Teamcenter server (TcServer) processes and other Teamcenter processes, and Teamcenter
command-line utilities, start in the language specified in the TC_language_default preference. To
make these display in a different preferred locale, set the TC_language_default preference to a
supported locale code.
Teamcenter allows users to select a locale on their client hosts, regardless of the locale used by the
Teamcenter server pool manager. Requested locales must be installed on the Teamcenter server
(which may not be true for customized locales) and the server system be configured to accept the
locale encoding.

Add multibyte character support in an English rich client

1. In the rich client \rac\plugins\configuration_config-name directory, create the
customer.properties file, if it does not already exist.
Note

Do not save the customer.properties file in unicode or UTF-8 format. The

customer.properties file must be in the default format (for example, ANSI) to be read
successfully by the rich client.

2. Open the customer.properties in a plain text editor.

3. Add the following line to the file to set the UseDefaultSwingFonts property.
UseDefaultSwingFonts=true

4. Save the file and exit the text editor.

5. Change to the rac\registry directory.

6. Run the genregxml.bat utility to register the change.

Note

When you run Teamcenter in a multibyte environment, make sure the TC_XML_ENCODING
environment variable is set to UTF-8 and the UGII_UTF8_MODE environment variable is set
to 1.

19-8 Windows Server Installation PLM00013 11.2

Chapter 20: Creating a custom distribution

Overview of custom distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Create a silent distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2

Create a compact distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6

PLM00013 11.2 Windows Server Installation

Chapter 20: Creating a custom distribution

Overview of custom distributions

Teamcenter supports the following custom distributions to simplify installation of Teamcenter on
multiple hosts.
• Silent distribution
A silent distribution is an XML-based configuration file you can use to install Teamcenter silently
(without user interaction) on another host. Silent installation suppresses most installation
prompts and requires minimal user interaction. As an alternative to installing and configuring
Teamcenter on individual hosts in your network, silent installation provides an efficient way to
deploy Teamcenter on multiple hosts in your network.
The silent installation configuration file records the selections and values you enter during a
Teamcenter installation and enables TEM to perform these steps noninteractively on other hosts.
You can modify a silent configuration file to change certain Teamcenter settings before installation.
Silent distributions are supported for Teamcenter servers, two-tier rich clients, and four-tier
rich clients.

• Compact distribution
A compact distribution is an installable package with a selected subset of Teamcenter client
features. It is much smaller than a full Teamcenter software distribution image and is more easily
distributed to multiple hosts in an organization.
A compact distribution is an alternative to installing Teamcenter from a full Teamcenter software
distribution image. A compact deployable package can contain a selected subset of Teamcenter
features rather than the entire set of features in the release. This reduces network loads
and simplifies large-scale Teamcenter deployments by providing an installation package that
is smaller and more easily distributed to an organization. For example, a two-tier rich client
installation can be packaged in a deployable media as small as 580 MB, where a full Teamcenter
distribution can require up to 5 GB. A four-tier rich client compact distribution can be as small as
283 MB, and a Client for Office compact distribution can be only 93 MB.
Compact distributions are supported for Teamcenter two-tier and four-tier rich clients.

Create a silent distribution

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.

PLM00013 11.2 Windows Server Installation 20-1

 Chapter
Chapter 20:20:Creating
Creating a custom
a custom distribution
distribution

3. In the Welcome to Teamcenter panel, select Teamcenter.

4. In the Install/Upgrade Options panel, select the Create custom distribution check box,
and then click Install.

5. In the Custom Distribution Options panel, select Create silent configuration file, and then
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.

6. Proceed through the remaining panels to complete the Teamcenter installation.

Teamcenter Environment Manager creates the silent installation file you specified in step 5. 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.

Caution

If you install a rich client silently using a compact distribution and your silent configuration file
requires features not included in the compact distribution, the silent installation fails. To avoid
this, make sure your silent configuration requires only features in the compact distribution, or
install using a full Teamcenter software distribution image.

Launch a silent installation

To launch a silent installation, 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. 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.

20-2 Windows Server Installation PLM00013 11.2

 Creating a custom distribution

Element Description
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.

PLM00013 11.2 Windows Server Installation 20-3

 Chapter
Chapter 20:20:Creating
Creating a custom
a custom distribution
distribution

<?xml version="1.0" encoding="UTF-8"?>

<root>
<tem engine="2008.0.0" />
<settings>
<installDir value="C:\\Program Files\\Siemens\\Teamcenter11" />
<sourceDir value="D:\\kits\\tc11.2\\win64" />
<application value="tceng" />
<silentMaintenance value="false" />
<installingUser value="osuser" />
<installLanguage value="ENGLISH" />
<aboutFullVersion value="11.2" />
<version value="11000.2.0.20150701" />
</settings>
<sourceLocations>
<coreLocations>
<directory value="D:/kits/tc11.2/win64" />
</coreLocations>
<browsedLocations />
</sourceLocations>
<config name="My Configuration 1" id="config1">
<mode type="install" clone="false">
<checkpoints>
<checkpoint value="featureProperties">
<point value="vcruntimes:vc2005,latest" />
<point value="minMSSQL2005Version:10.50" />
<point value="coreTemplate:foundation_template.xml" />
<point value="feature_id:datamodel,rtserver" />
<point value="vcruntimes:latest" />
<point value="template_file:foundation_template.xml" />
<point value="minDB2Version:9.7.4" />
<point value="minOracleVersion:11.2.0.1" />
<point value="template_name:foundation" />
<point value="typeAnalysis:true" />
</checkpoint>
</checkpoints>
</mode>
<comments />
<data>
<adminUser guid="2E53CFC3AC75665E50FF0F207D1D013B">
<password value="holrvg6fpj40nGt7ZlCM2Q" encrypt="true" />
<user value="infodba" />
</adminUser>
<director guid="661AA2A766CA975D998EBE61455F3EA3">
<saveStateOnFail value="true" />
<status value="0" />
<script>
<temBase />
<copyFeature name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<copyFeature name="Business Modeler IDE" feature="A9CECD82127A11DB9804B622A1EF5492" />
<copyFeature name="VC 2008 Redistributables" feature="DPBL8RC6MUS0LCPS10NIPGR85RI7HPHQ" />
<copyFeature name="Teamcenter File Services" feature="BC76F9D1AB7C93A848D0FE3602F59097" />
<copyFeature name="Flex License Server" feature="D1D683A8B2CE1EB821B97CD2EE5D7627" />
<copyFeature name="VC 2005 Redistributables" feature="UDR4NG0DEZ1TN9XHKG7Z8AFDPVVTZXL2" />
<copyFeature name="VC 2013 Redistributables" feature="NJCMQH3ZMYTPPPGA8BS4Q1C7OV6IXVXU" />
<copyFeature name="VC 2010 Redistributables" feature="R08U30BA5KZYSNDFKMGXKKHWEYOOVD7V" />
<copyFeature name="VC 2012 Redistributables" feature="Z9ICW073V9QXU4H5F8BK6CXG6KFYWBQZ" />
<copyFeature name="Business Modeler Templates" feature="A909338A1CB411DB8AF6B622A1EF5492" />
<copyFeature name="Digital Dashboard" feature="A9CECD82127A11DB9804B622A1EF5599" />
<copyFeature name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<copyFeature name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<copyFeature name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2
010FD613" />
<copyFeature name="Java EE Based Server Manager" feature="BF0E78AFE4280DCB08594EA2F3671BE8" />
.
.
.
<unpack name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<unpack name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<unpack name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<unpack name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2010FD
613" />
<preInstall name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<preInstall name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<preInstall name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<preInstall name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D20
10FD613" />
<install name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<install name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<install name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />

Sample silent installation configuration file (Continued)

20-4 Windows Server Installation PLM00013 11.2

 Creating a custom distribution

<install name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2010F

D613" />
<postInstall name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<postInstall name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<postInstall name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<postInstall name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2
010FD613" />
<featureInstalled name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA5
2" />
<featureInstalled name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<featureInstalled name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<featureInstalled name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804E
FB0D2010FD613" />
</script>
</director>
<FSCService guid="F2FCBCEC03DFF7F9D1E3A11EC9B64BD2">
<fscReadCacheDir value="$HOME\\FSCCache" />
<fscWriteCacheDir value="$HOME\\FSCCache" />
<addToBootstrap value="true" />
<fscReadCacheSize value="10" />
<serverID value="FSC_tchost_osuser" />
<log value="" />
<fscWriteCacheSize value="10" />
</FSCService>
<FSCMasterSettings guid="EBC3422F77C6BF18FE0E3A821EFE1134">
<masterModel value="Simple Model" />
</FSCMasterSettings>
<FscSiteImport guid="630BECF927EC742A748A97486D5868DA">
<remoteSites value="" />
</FscSiteImport>
<tcdata guid="4500621E2BE24BF0DD6ABF31EBA01088">
<serverHostLocation value="tchost" />
<path value="C:\\Program Files\\Siemens\\tcdata" />
<create value="true" />
<shareName value="" />
<dsmKeyPath value="" />
</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="35EE6A66B85467D5EDE5B3D91871EACE">
<siteListString value="" />
</FccSite>
<FSCServiceConnections guid="E4BDA0B521CB10A49F0CE123C9F326F1">
<connections value="http,4544,;" />
</FSCServiceConnections>
<OSUser guid="CA769D31FD7E122E5E509A0BBBD7E809">
<password value="+rfq6mTJVSuqaYJixkwntg" encrypt="true" />
<user value="DOMAIN\\osuser" />
</OSUser>
<flexClient guid="7221ECFBC9555CDF997FC3F575022761">
<nX5String value="28000@flexhost" />
<port value="27000" />
<nX4String value="27000@flexhost" />
<nX5Port value="28000" />
<host value="flexhost" />
<nX5Host value="flexhost" />
<nX5CheckBox value="true" />
<envServerString value="28000@flexhost" />
</flexClient>
<signatureCertificate guid="RRK3WTCSY4020QSZO90QFJWMISFAC2AX">
<replaceCerts value="false" />
<certificates value="" />
</signatureCertificate>
<foundationSettings guid="LHBY67ZYMYHSKED26FHDNDHFJTZD84I7">
<templatesToBeInstalled value="" />
<genClientCache value="generate all" />
<genServCache value="" />
<productionEnvironment value="true" />
<requestMetaCacheRebuild value="true" />
<enableGenServCache value="true" />
<quickClone value="false" />
</foundationSettings>
<transientVolume guid="983980098FF188A8C4BF08E8168A32A8">
<windowsVolume value="C:\\Temp\\transientVolume_tcdbuser" />
<unixVolume value="/tmp/transientVolume_tcdbuser" />
</transientVolume>

Sample silent installation configuration file (Continued)

PLM00013 11.2 Windows Server Installation 20-5

 Chapter
Chapter 20:20:Creating
Creating a custom
a custom distribution
distribution

<TcOracleSystem guid="1EF0859AC04962CBFA41C4C8C84499A1">
<password value="WsRDrEfD0/4vnLO0/mj2wA" encrypt="true" />
<user value="system" />
<tablespaces value="tcdbuser_IDATA:90;tcdbuser_ILOG:5;tcdbuser_INDX:5;tcdbuser_TEMP:5;tcdbuser_MM
V:5" />
<tablespacePath value="/db/oradata/tc/tcdbuser" />
</TcOracleSystem>
<security guid="ZUG63OE2YRNFD1VY13KCEZM52XFJP45D">
<adminDirectory value="$TC_ROOT\\security" />
</security>
<volume guid="1F16971107DE44C0C7827F800EE4AEF8">
<port value="4544" />
<fscModel value="Simple Model" />
<location value="C:\\Program Files\\Siemens\\volume" />
<name value="volume" />
<hostName value="tchost" />
<fscId value="FSC_tchost_osuser" />
</volume>
<TcOracleEngine guid="F4F7C0852B27D6E56B8C64BE77FFA14C">
<port value="1521" />
<createUser value="true" />
<host value="dbhost" />
<flush value="false" />
<populate value="true" />
<service value="tc" />
<uTF8Enabled value="true" />
<password value="AdxT7Jmz2/WbYF6O/eqX9g" encrypt="true" />
<user value="tcdbuser" />
<create value="true" />
</TcOracleEngine>
</data>
<features>
<add feature="A0CF69C3A0BC61770EB81BD22667EA52" name="Microsoft Visual C++ Runtimes" />
<add feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" name="FMS Server Cache" />
<add feature="8C061DD51E13E0CB9DC4687B1A3348BE" name="Teamcenter Foundation" />
<add feature="B176F6B6E9E91D9804EFB0D2010FD613" name="NX Part Family Classification Integration"
/>
</features>
</config>
<updateManager />
</root>

Sample silent installation configuration file

Create a compact distribution

Create a compact distribution, a Teamcenter installation package that contains selected features,
using Teamcenter Environment Manager (TEM).
Note

Compact distribution is recommended only for Teamcenter client configurations, not for servers.

1. Log on to the Teamcenter corporate server host and browse to the root directory of the
Teamcenter software distribution image.

2. Start TEM (tem.bat) from the Teamcenter software distribution image.

3. Proceed to the Install/Upgrade Options panel, select the Create custom distribution check
box, and then click Install.

4. In the Custom Distribution Options panel, select Create compact deployable media. Enter
the path in which to create the compact distribution and a file name for the package, for example,
C:\tc.zip.
The specified path must be to an existing directory and the file name must end in .zip.

5. Proceed through the remaining panels to complete the Teamcenter installation.

20-6 Windows Server Installation PLM00013 11.2

 Creating a custom distribution

TEM creates the compact distribution file you specified in step 4. You can use this file to install
Teamcenter clients on other hosts.

Caution

If you create a silent installation using a compact distribution and your silent configuration file
requires features not included in the compact distribution, the silent installation fails. To avoid
this, make sure your silent configuration requires only features in the compact distribution, or
install using a full Teamcenter software distribution image.

PLM00013 11.2 Windows Server Installation 20-7

Chapter 21: Installing Teamcenter patches

Using Updates Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Patch Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Migrate trace links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Install patches on a Teamcenter server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3

Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5

Choosing the patching method for the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Patch the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-6
Patch the rich client silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
Patch the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . . . . . . . . . . . . 21-8
Patch Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9

Patch the web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-10

Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-11

PLM00013 11.2 Windows Server Installation

Chapter 21: Installing Teamcenter patches

Using Updates Manager

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 Java EE web tier
you install using the Web Application Manager. Teamcenter updates (maintenance packs, service
packs, and patches) are posted for download on GTAC when available.

Distribution of Teamcenter updates

Teamcenter 11.2 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 Java EE 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.

Before you apply downloaded Teamcenter 11.2 patches to your server, you must do the following:
• Install the base Teamcenter 11.2 release.

PLM00013 11.2 Windows Server Installation 21-1

 Chapter
Chapter 21:21:Installing
Installing Teamcenter
Teamcenter patches
patches

• Stop all Teamcenter 11.2 related processes and services (such as FSC, database daemons,
and others).
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 8.3 patch to a Teamcenter
11.2 installation.

Patch Teamcenter Environment Manager

If the patch you downloaded contains an updated installer file (install.zip), expand this file into
your installed Teamcenter environment to update Teamcenter Environment Manager (TEM) to the
latest version.
1. Copy the patch-id_install.zip file to your TC_ROOT\install directory.

2. Open a command prompt.

3. Change to the TC_ROOT\install directory.

4. Enter the following command to expand the install.zip file, overwriting existing files:
unzip -o install.zip

Note

If errors occur while expanding 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

Migrate trace links

Beginning with Teamcenter 10.1.2.x patches, trace links are created on revisions of the absolute
occurrence objects. In earlier versions of Teamcenter, trace links are created on absolute occurrence
objects.
If your database contains trace links on absolute occurrence objects, run the
req_migrate_bomview_tracelinks utility before you patch the corporate server. This utility migrates
trace links on absolute occurrence objects to create trace links on the latest revision of the absolute
occurrence objects.
Note

You must have modify privileges on all the existing trace links in the database to run the
migration. If you do not have modify privileges on some of the trace links, those trace links are
not migrated, and a message is written to the log file.

21-2 Windows Server Installation PLM00013 11.2

 Installing Teamcenter patches

1. In the Teamcenter environment, open a Teamcenter command prompt.

2. Type the following command:

req_migrate_bomview_tracelinks -u=infodba -p=infodba -g=dba

The utility returns the number of trace links found in the database and lists each trace link as it is
processed. The migration is complete when the command prompt is returned.

Install patches on a Teamcenter server

Caution

If the patch contains an updated installer file (install.zip), patch Teamcenter Environment
Manager (TEM) before you begin the following steps.

1. Expand 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 11.2→Environment Manager).

Note

If you patched TEM, make sure you launch the patched TEM.

4. In the Maintenance panel, select Updates Manager and click Next.

5. In the Apply Updates panel, enter the following values, and then click Next.
a. Update kit location
Enter the location of patch files you expanded in step 1.

b. Backup directory
Enter the location in which you want to store backups of files replaced during the update
process.

6. If the patch contains enhancements to features in your configuration, TEM displays the Optional
Configuration Enhancements panel. Review the list of enhancements and decide whether to
install the enhancements:
a. Click View Enhancement Info for each feature to view information about the enhancements.
Note each feature that has enhancements.

b. If you want to install the optional feature enhancements, select Yes. Otherwise, select No.
Warning

If you select Yes, features containing data model objects may be upgraded. That is,
database model changes may occur. Siemens PLM Software recommends you back up
your database before continuing.

PLM00013 11.2 Windows Server Installation 21-3

 Chapter
Chapter 21:21:Installing
Installing Teamcenter
Teamcenter patches
patches

Note

If you select No, features containing data model objects are not updated. If you want to
perform this update at a later time, you must repeat the patch installation procedures to
reinstall the patch, and choose Yes to include the template update.

7. Click Next.

8. If any feature enhancements require the Teamcenter administrative user password, TEM displays
the Teamcenter Administrative User panel. Type the user name and password, and then
click Next.

9. In the Confirmation panel, click Start to begin patching the server.

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.

10. After the server is successfully patched, you must manually update your TC_DATA directories.
a. Create backups of your current TC_DATA directories.

b. Expand the platform\tc\data.zip file from the temporary location you created in step 1.

c. Copy the expanded contents of the data.zip file to your TC_DATA directories, overwriting
existing files.

d. Copy the tc_profilevars.bat file from the backup to the TC_DATA directory.

11. Update Business Modeler IDE templates:

a. Launch TEM in maintenance mode.

b. Select the configuration that contains the Business Modeler IDE client.

c. Select Add/Update template for working within the Business Modeler IDE client. TEM
displays all templates currently used in Business Modeler IDE client.

d. Select all templates for features for which you installed enhancements in step 6.

e. Confirm your selections and then click Start to perform the updates.

f. After TEM completes the updates, verify the latest templates are available in the
TC_ROOT/bmide/templates directory.

21-4 Windows Server Installation PLM00013 11.2

 Installing Teamcenter patches

12. If you have a custom template project created in the Business Modeler IDE client, and you
selected Yes to install enhancements in step 6, upgrade your custom template project:
a. Launch the Business Modeler IDE client.

b. Open the custom project.

c. Ensure the custom project loads successfully with no errors in the Business Modeler IDE
console view.

d. Analyze and fix any errors.

e. If you made any additional changes to the custom template to fix loading errors, package
your custom template.

f. Update the updated-feature template in the Teamcenter corporate server database:

A. Launch TEM in maintenance mode.

B. Select the configuration that contains the updated feature.

C. Select Update database (Full Model - System downtime required).

TEM displays all templates installed in your database.

D. Browse to the location of your custom template package file and select the feature file for
the updated template (for example, feature_custom.xml).

E. Confirm your selections, and then click Start.

TEM updates the database.

13. Perform any additional steps in the patch README file 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

Choosing the patching method for 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, 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 using the Over-the-Web Installer. You can also patch Lifecycle Visualization using
the Over-the-Web Installer.

PLM00013 11.2 Windows Server Installation 21-5

 Chapter
Chapter 21:21:Installing
Installing Teamcenter
Teamcenter patches
patches

Patch the rich client using TEM

Caution

If the patch contains an updated installer file (install.zip), patch Teamcenter Environment
Manager (TEM) before you begin the following steps.

1. Expand 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 11.2→Environment Manager).

Note

If you patched TEM, make sure you launch the patched TEM.

4. In the Maintenance panel, select Updates Manager and click Next.

5. In the Apply Updates panel, enter the following values, and then click Next.
a. Update kit location
Enter the location of patch files you expanded in step 1.

b. Backup directory
Enter the location in which you want to store backups of files replaced during the update
process.

6. If the patch contains enhancements to features in your configuration, TEM displays the Optional
Configuration Enhancements panel. Review the list of enhancements and decide whether to
install the enhancements:
a. Click View Enhancement Info for each feature to view information about the enhancements.
Note each feature that has enhancements.

b. If you want to install the optional feature enhancements, select Yes. Otherwise, select No.

Warning

If you select Yes, features containing data model objects may be upgraded. That is,
database model changes may occur. Siemens PLM Software recommends you back up
your database before continuing.

Note

If you select No, features containing data model objects are not updated. If you want to
perform this update at a later time, you must repeat the patch installation procedures to
reinstall the patch, and choose Yes to include the template update.

7. Click Next.

21-6 Windows Server Installation PLM00013 11.2

 Installing Teamcenter patches

8. If any feature enhancements require the Teamcenter administrative user password, TEM displays
the Teamcenter Administrative User panel. Type the user name and password, and then
click Next.

9. In the Confirmation panel, click Start to begin patching the rich client.

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.

10. Perform any additional steps in the patch README file 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.

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..

2. Expand the patch-id.zip file to a directory on your local host.

3. Open a command prompt.

4. Change to the TC_ROOT\install directory (on Windows systems) or the TC_ROOT/install

directory (on UNIX/Linux systems).

5. Type the tem.bat command:

tem.bat -p "patch-path\patch-directory" —pass=password@config

Replace patch-path and patch-directory with the full path to the location in which you expanded
the patch-id.zip file. Replace password with the Teamcenter password and config with the
Teamcenter configuration name.

This procedure launches TEM and applies the patch with no user interaction required.

PLM00013 11.2 Windows Server Installation 21-7

 Chapter
Chapter 21:21:Installing
Installing Teamcenter
Teamcenter patches
patches

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\patch-location"

Patch the rich client using the Over-the-Web Installer

The patch files for any rich client installed using the Over-the-Web (OTW) installer are in the
Teamcenterversion_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 Teamcenterversion_patch-ID_OTW.zip file to your computer.

2. Shut down the distribution server.

3. Launch the Web Application Manager (insweb.bat).

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.
The Web Application Manager displays the Modify Web Application dialog box.

6. Click Modify Disk Locations.

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 OK. b. In the Reinstall Solution dialog box, click
OK.1
c. In the Modify Web Application dialog
box, click OK to begin patching. c. In the Confirm dialog box, click Yes.

d. After the patch is installed, click OK to d. In the Modify Required Context

close the Progress dialog box. Parameters dialog box, click OK to begin
patching.

e. After the patch is installed, click OK to

close the Progress dialog box.

1. Adding patches reinstalls the patch solution with the newer files.

21-8 Windows Server Installation PLM00013 11.2

 Installing Teamcenter patches

9. In the Modify Web Application dialog box, click OK.

10. Exit the Web Application Manager.

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 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 expand 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.

2. Launch the Web Application Manager (insweb.bat).

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.
The Web Application Manager displays the Modify Web Application dialog box.

5. Click Modify Disk Locations.

6. Click Add and add the patch location to list of disk locations for install images.

PLM00013 11.2 Windows Server Installation 21-9

 Chapter
Chapter 21:21:Installing
Installing Teamcenter
Teamcenter patches
patches

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 8 b. In the Reinstall Solution dialog box, click

(Embedded Viewer) for Rich Client OK.2
4-Tier (installation and Configuration)
Patch and click OK. c. In the Confirm dialog box, click Yes.

c. In the Modify Web Application dialog d. In the Modify Required Context

box, click OK to begin patching. Parameters dialog box, click OK to begin
patching.
d. After the patch is installed, click OK to
close the Progress dialog box. e. After the patch is installed, click OK to
close the Progress dialog box.

8. In the Modify Web Application dialog box, click OK.

9. Exit the Web Application Manager.

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 expand 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 (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.

21-10 Windows Server Installation PLM00013 11.2

 Installing Teamcenter patches

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 (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 (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.

PLM00013 11.2 Windows Server Installation 21-11

Chapter 22: Uninstalling Teamcenter

Uninstall Teamcenter configurations and installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1

Uninstall TCCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2

Uninstalling IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3

Before uninstalling DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Remove DB2 instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Remove DB2 software on UNIX and Linux systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3
Remove DB2 software on Windows systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-5

Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-5

Uninstall SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6

Uninstall Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-6

PLM00013 11.2 Windows Server Installation

Chapter 22: Uninstalling Teamcenter

Uninstall Teamcenter configurations and installations

Using Teamcenter Environment Manager (TEM), you can remove a single Teamcenter configuration
or all Teamcenter configurations and software.
• Remove a configuration.
To remove a single Teamcenter configuration, use the Remove configuration option in the
Configuration Maintenance panel in TEM.

• Remove the entire Teamcenter installation.

To completely uninstall Teamcenter, use the Uninstall Teamcenter option in the Maintenance
panel in TEM. This option uninstalls the following:

o All Teamcenter configurations

o All databases created during Teamcenter installation

o All Teamcenter volumes

o All Teamcenter client communication system (TCCS) environments

TCCS cache files (cache files generated by the FSC or FCC) are not deleted. After
Teamcenter uninstallation, you can manually delete these cache files.

o Teamcenter Environment Manager (TEM)

o TC_ROOT and TC_DATA directories

If you shared TC_ROOT or TC_DATA directories, TEM may not completely remove these
directories because they may be locked by sharing. To completely uninstall these directories,
you must unshare these directories before you begin uninstallation.

To remove an entire Teamcenter installation, perform the following steps:

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.

3. Start Teamcenter Environment Manager (TEM):

Start→Programs→Teamcenter 11.2→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 Maintenance panel, select Uninstall Teamcenter, and then click Next.

PLM00013 11.2 Windows Server Installation 22-1

 Chapter
Chapter 22:22:Uninstalling
Uninstalling Teamcenter
Teamcenter

5. The Configuration Display panel shows all configurations in the Teamcenter installation. Review
the configuration details, and then click Next.

6. In the Uninstall panel, select Yes to confirm that you want to uninstall all configurations and
Teamcenter software. Click Next.

7. In the Confirmation panel, click Start to begin the uninstallation.

TEM removes the Teamcenter installation.
If the uninstallation is not successful, TEM stops processing when it encounters the error and
displays a message indicating the location of the log file containing the error.

8. 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;

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\Teamcenter11\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.

22-2 Windows Server Installation PLM00013 11.2

 Uninstalling Teamcenter

Uninstalling IBM DB2

Before 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.

PLM00013 11.2 Windows Server Installation 22-3

 Chapter
Chapter 22:22:Uninstalling
Uninstalling Teamcenter
Teamcenter

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.

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.

22-4 Windows Server Installation PLM00013 11.2

 Uninstalling Teamcenter

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.

PLM00013 11.2 Windows Server Installation 22-5

 Chapter
Chapter 22:22:Uninstalling
Uninstalling Teamcenter
Teamcenter

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.

Uninstall Teamcenter help

Uninstall Teamcenter help collections

1. In the Add or Remove Programs dialog box in the Windows Control Panel, right-click Siemens
Teamcenter version Documentation and choose Uninstall/Change.

2. Select the Uninstall Product option in the Teamcenter documentation installer.

Uninstall the PLM Documentation Server

In the Add or Remove Programs dialog box in the Windows Control Panel, right-click Siemens PLM
Documentation Server and choose Uninstall.

22-6 Windows Server Installation PLM00013 11.2

Part VII: Appendixes

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Deploying Teamcenter help in an existing web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

PLM00013 11.2 Windows Server Installation

Appendix A: Troubleshooting

Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Problems/error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Update Manager FTP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Resolving web tier connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Diagnosing web tier connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Change the deployable file name on the corporate server . . . . . . . . . . . . . . . . . . . . . A-5
Change the deployable file name on the web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Java exception errors during command-line updates . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Web Application Manager needs location of Java file when installing rich client . . . . . . . . . A-6
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Troubleshooting the .NET web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Resolving thin client error on 64-bit Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Resolving .NET server manager port conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16

Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16

Finding Oracle errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16
View additional information about an Oracle error message . . . . . . . . . . . . . . . . . . . . . . A-16

Tuning WebSphere JVM memory consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17

Troubleshooting document rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18

Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21

Recovering a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21

Overview of recovery from a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Recovering from a corrupted IBM DB2 database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-21
Recovering from a corrupted Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22
Recovering from a corrupted Microsoft SQL Server database . . . . . . . . . . . . . . . . . . . . A-22

PLM00013 11.2 Windows Server Installation

Appendix A: Troubleshooting

Troubleshooting Teamcenter server installation

Installation log 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.

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

PLM00013 11.2 Windows Server Installation A-1

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

Problem/error message Possible cause Solution

TEM does not start, reports JRE not found. JRE path is not set in the system Set the JRE_HOME or JRE64_HOME
environment. environment variable to specify the path
to the required Java Runtime Environment
(JRE).

For more information, see Java Runtime

Environment.
JRE path is set incorrectly in the system Make sure the path specified in the
environment. JRE_HOME or JRE64_HOME environment
variable is correct.

For more information, see Java Runtime

Environment.
The specified JRE has been removed from If you installed a new Java Runtime
the system. Environment (JRE) and removed the
previous JRE after you installed Teamcenter,
TEM cannot find the JRE, even if
JRE_HOME or JRE64_HOME is set
correctly.

To resolve this problem, perform the

following steps.

1. Open the following file in a plain text

editor:

TC_ROOT\install\tem_init.bat

2. Locate the following line in the file:

set TC_JRE_HOME=jre_location

3. Replace jre_location with the path to

the new JRE.

4. Save and close the file.

5. Perform the steps in Migrate

Teamcenter to a different JRE.

To avoid this problem in the future, do not

remove your previous JRE until after you
complete migrating Teamcenter to the new
JRE.

TEM reports the installation path must not The installation drive specified in the Change the Installation Directory to a path
contain spaces. Installation Directory does not support with no spaces, or to a path on a drive that
short file names (8.3 convention). TEM supports 8.3 file names.
requires this capability.
Tip

To determine whether support for

the 8.3 file name convention is
enabled for a given drive, type the
following command in a command
prompt:
fsutil 8dot3name query
drive-letter

A-2 Windows Server Installation PLM00013 11.2

 Troubleshooting

Problem/error message Possible cause Solution

Teamcenter Environment Manager (TEM) If your Microsoft SQL Server database uses Make sure the Server Browser service is
cannot connect to the Microsoft SQL Server a named instance and the Server Browser running on the database host.
database. service is not running on the database
host, TEM cannot verify the connection to
the database.

Running Teamcenter in an IPv6 network Some Teamcenter components are Find your IP address using the ping or
environment, the Teamcenter client does sensitive to link-local IPv6 addresses. You nslookup command. Make sure these
not connect to the server at all or hangs must make sure your hosts have global IPv6 commands find the a global IPv6 address,
when trying to connect to the server. addresses and use those when connecting not a link-local IPv6 address.
to the Teamcenter server. Problems can
occur if you use local-link IPv6 addresses. If not, or if you are unsure, contact your
network administrator. Make sure your host
name resolves to a global IPv6 address, not
a link-local IPv6 address.

Note

You can also view your host’s

network addresses using the
ipconfig command (on Windows
systems) or the ipconfig command
(on UNIX and Linux systems).

During logon using Kerberos authentication, The system clock time on the Teamcenter Synchronize the system clock times between
Teamcenter displays the following error: client is significantly different from the the Teamcenter client and the KDC.
system clock time at the Kerberos Key
Mechanism level:
Clock skew too great Distribution Center (KDC).

TEM displays errors like the following during If you launched TEM from a shortcut If you create a desktop shortcut to
installation of features: with an incorrect working directory, TEM TEM, make sure the working directory
encounters problems installing or updating (or Start in location) for the shortcut is
path\feature_acadgmo.xml: Error on
line 1 of document features. TC_ROOT\install.
file: path/feature_acadgmo.xml:
Premature end of file.

Database daemon services do not start. If the database daemon services run on If the database daemons run on the same
the same host as the database server, the host as the database server, perform one
These can include the following: database daemons may attempt to start of the following steps:
before the database server is fully running.
• Teamcenter Task Monitor Service • Manually start the database daemon
If this happens, the daemons fail to start.
• Teamcenter Subscription Manager services after the database server is
Service started.
• Teamcenter Action Manager
Service • Modify the startup settings for the
• Teamcenter Tesselation Manager database daemon services to create a
Service dependency on the database service.
This ensures the daemons do not start
before the database server is fully
running.

PLM00013 11.2 Windows Server Installation A-3

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

Problem/error message Possible cause Solution

During an installation or upgrade, the FMS Another service on the same host was Change the FSC settings to use a different
server cache (FSC) reports a startup failure running on the same port that the FSC is port.
with a message similar to the following: configured to use. This causes a fatal error
to the FSC and the FSC startup log shows
Installation interrupted
due to the a bind exception on the port.
following reason:
Some services, such as JBoss, allow the
Processing <upgrade>
of feature FMS FSC to bind to its port, resulting in failure of
Server Cache failed: the FSC to start, but no errors in the FSC
FSC service failed to
start with an error 1
log.

However, the FSC startup log shows no

errors and indicates the FSC is left running.

<<null>>\\<<null>> on host host-name This error most likely indicates you Start Teamcenter Environment Manager
does not have administrator privileges attempted to start Teamcenter Environment as a user logged onto the system with
Manager using the Windows runas Administrator group privileges and the Log
command or the Run as menu command. on as a service right.
Teamcenter Environment Manager cannot
be started as a user other than the user
logged on to the operating system.

Troubleshooting Teamcenter online help

Problem Solution
Online help installed for thin client does not display. The WEB_core_help_server and WEB_help_server preferences
are not set correctly.

Set the preferences to the correct values.

Online help does not display in Internet Explorer. Clicking the error Uninstall Google Chrome Frame through the Add or Remove
icon in the lower left of the browser windows displays this error: Programs dialog box in the Windows Control Panel.
‘DOMParser’ is undefined.

This error occurs when the Google Chrome Frame add-in to

Internet Explorer is installed. The Teamcenter online help collection
is not compatible with this add-in.

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.

A-4 Windows Server Installation PLM00013 11.2

 Troubleshooting

Error Resolution
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

Diagnosing 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

Change the deployable file name on the web tier

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.)

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.

PLM00013 11.2 Windows Server Installation A-5

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

5. Deploy the rebuilt web application on your web application server.

Java exception errors during command-line updates

When making updates in TEM through the command-line interface, such as adding Teamcenter
features or data model update operations, certain Java exception errors may occur.

TEM performs error checking when processing command line parameters and exits quickly if it
detects an error such as an invalid parameter setting. In such cases, a Java exception error similar
to the following may occur:
Data model update
Loading features from path
Type: FULL
Configuration: TEMFLOW1
Verifying password
Unable to locate:
alpha1_template.zip Exception while removing reference: java.lang.InterruptedException
java.lang.InterruptedException at java.lang.Object.wait(Native Method) at
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118) at
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134) at
sun.java2d.Disposer.run(Disposer.java:125) at java.lang.Thread.run(Thread.java:619)

These types of Java exception errors are not a cause for concern because TEM begins shutting down
when a problem is detected, before any data model updates are performed. These errors occur
while threads are closing. In the above example, the java.lang.InterruptedException error occurs
because the main Java thread begins to exit while the Swing (GUI) thread is waiting to close.

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.

1. Locate the bmide\compressed_files directory in the Teamcenter software distribution image.

2. Expand 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 WAR file using the Web Application Manager.

5. Deploy your WAR file.

Related topics

• Web Application Deployment

A-6 Windows Server Installation PLM00013 11.2

 Troubleshooting

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.
teamcenter.jeti.util.
cluster peers are not able to open sockets to that port.
JetiResourceConfiguration
Exception: TreeCache To avoid this error, specify a particular bind address using the
initialization failed bind.address Java system property, for example:
Dbind.address=123.456.78.91

Java arguments can be specified in different ways

on different application servers. For example, for a
WebLogic managed server, use the WebLogic console
server/Configuration/Server Start/Arguments field.
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.
See the description of the server manager context 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.
Out-of-memory If you use WebSphere and this occurs when launching NX
error during a call to from the rich client, you must modify the JVM arguments in
getAttrMappingsForDatasetType WebSphere to increase memory allocation.
Delays in opening a connection The web tier may be attempting a connection to the Teamcenter
from the web tier to a Teamcenter server on an IP address that is unavailable.
server
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.

PLM00013 11.2 Windows Server Installation A-7

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

Problem Solution

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.
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 the
startup 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>

A-8 Windows Server Installation PLM00013 11.2

 Troubleshooting

Problem Solution

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.
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.
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.

PLM00013 11.2 Windows Server Installation A-9

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

Problem Solution
TreeCache initialization fails when The following error messages in the log files indicate that the
starting the server manager or TreeCache port is already in use:
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.
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. Expand 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 cluster,
used/recognized by the web the TreeCache Peers parameter for the server manager must
tier application when the manager contain the host name and port number of a web application
is restarted without restarting the server running the web tier application or the host/port pair of a
web tier 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.
A server manager crash occurs An error message, similar to the following, appears in the Java
with an error in the Java output output and is identified in the hs_err_* file as an error in a
that indicates the JVM detected 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)

A-10 Windows Server Installation PLM00013 11.2

 Troubleshooting

Problem Solution

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:
# 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 startup On some platforms or machines, the jgroups code used
or Java EE web application by TreeCache in the Teamcenter server manager or the
deployment the following error Teamcenter Java EE application may fail to initialize when using
message is received when using mcast mode. This may be caused by using IPv6. This is to
multicast mode: known to occur when using a Linux host but may also occur
java.net.BindException: 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)

PLM00013 11.2 Windows Server Installation A-11

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

Problem Solution

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 Java EE application server.
#JVM_ARGS="${JVM_ARGS} -Djava.net.preferIPv4Stack=true"

If this error occurs during Java EE application deployment,

consult your application server vendor's documentation for the
proper JVM arguments settings. Another possible solution is to
use TCP mode instead of mcast mode for both the Teamcenter
server manager and Java EE 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 an A Teamcenter web application deployed on a Sun Java System
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.

A-12 Windows Server Installation PLM00013 11.2

 Troubleshooting

Problem Solution
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 domain
same domain on a WebLogic by itself or ensure each application has a separate cookie path.
application server.
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
staging-directory is the directory where the specific
web application was generated.

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.

PLM00013 11.2 Windows Server Installation A-13

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

Problem Solution
During peak activity, the web tier The Teamcenter web application is using all available
encounters errors obtaining JCA connections in the connection pool. To avoid this, increase
connections. the number of available connections by increasing the
Max_Capacity context parameter value in the web application
WAR file.
To set your web application maximum connection pool size:
1. Launch the Web Application Manager (insweb).

2. Select the web application name and click Modify.

3. In the Modify Web Application dialog box, click Modify

Context Parameters.

4. In the Modify Context Parameters dialog box, locate

Max_Capacity, 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 WAR 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.

A-14 Windows Server Installation PLM00013 11.2

 Troubleshooting

Problem Solution
During successive calls to get During large Global Services transactions, such as a replication
activity status in the Global manager transaction during site consolidation orchestration,
Services user interface, out of you may encounter a Java out of memory error from the
memory errors are displayed. 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).
Teamcenter web application fails The Teamcenter web application takes longer than the
to deploy on JBoss with the default 60 seconds the JBoss deployment scanner allows for
following error message: deployments. Add the deployment-timeout attribute to the
Did not receive a response
deployment-scanner element and set the value to at least 600
to the deployment operation seconds before attempting to deploy the web application.
within the allowed timeout
period [60 seconds]. Check <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
the server configuration <deployment-scanner path="deployments"
file and the server logs to relative-to="jboss.server.base.dir" s
find more about the status scan-interval="5000"
of the deployment. deployment-timeout="600"/>
</subsystem>

Troubleshooting the .NET web tier

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”).

PLM00013 11.2 Windows Server Installation A-15

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

This installs the script map to the specified application root path.

3. Resume the Teamcenter installation.

Resolving .NET server manager port conflicts

When starting the .NET Server Manager Service, Teamcenter may display a message that no
Teamcenter servers are available. This can be caused by a port conflict.
To diagnose and resolve this problem, perform the following steps.
1. Open the following file in the TC_ROOT\net_servermanager\logs directory:
TcServerManager_timestamp.log

2. Search the log file for errors similar to the following example:
2014-02-12 21:06:33 [6] ERROR Teamcenter.Enterprise.ServerManager.ServerPoolManager [(null)] - Rem

3. If you find an error that states a remoting port is already in use, another process is using the same
port as the .NET server manager.

To resolve this problem, either change the .NET server manager port to different value or stop the
other process that uses the .NET server manager port.
Note

You can use the Windows netstat utility to view all TCP ports currently in use by the system.
For example, typing netstat -a -b or netstat -aon lists the TCP ports currently in use.

Troubleshooting Oracle
Finding Oracle errors
When Oracle detects an error, an error code is displayed in the system console window and written
to the Teamcenter trace and log files. To assist troubleshooting, Oracle embeds object names,
numbers, and character strings in error messages.
The oerr utility provides additional troubleshooting information. Often, the additional information
offers a solution to the problem.

View additional information about an Oracle error message

1. Manually set the Oracle environment by entering the following command:
export ORACLE_HOME=/u01/app/oracle/product/oracle-version

Replace oracle-version with the installed Oracle version, for example, 920.

2. Enter the following command:

$ORACLE_HOME/bin/oerr facility error-number

Replace facility error-number with the Oracle error code, for example ORA 7300. ORA is the
facility and 7300 is the error number.

A-16 Windows Server Installation PLM00013 11.2

 Troubleshooting

This command displays cause and action messages that you can use to troubleshoot the problem.

Tuning WebSphere JVM memory consumption

If your Teamcenter application requires more memory than what is currently allocated in WebSphere,
out-of-memory errors can occur. For example, if you use the NX Integration and attempt to
launch NX from the rich client, Teamcenter may report an out-of-memory error during a call to
getAttrMappingsForDatasetType.
If errors like this occur, you must modify the JVM arguments in WebSphere to increase memory
allocation. For information about how to modify JVM arguments, see the IBM support article titled
Setting generic JVM arguments in WebSphere Application Server:
http://www-01.ibm.com/support/docview.wss?uid=swg21417365
Before you tune JVM arguments, use memory profiling tools to analyze your memory issues and
determine which tuning options you need to use. The following table provides some suggestions, but
these may not be suitable in all cases.

JVM options for tuning the WebSphere Application Server memory usage
Typical
Suggested
JVM option Description default
value
value
-Xms Controls the initial size of the Java heap. 50 MB 512 MB
Properly tuning this parameter reduces the overhead
of garbage collection, improving server response
time and throughput. For some applications, the
default setting for this option may be too low, resulting
in a high number of minor garbage collections.
-Xmx Controls the maximum size of the Java heap. 256 MB 1024 MB
Note

In general, increasing the minimum/maximum

heap size can improve startup, reduce the
number of garbage collection occurrences,
and increase the throughput until the heap
no longer resides in physical memory. After
the heap begins swapping to disk, Java
performance suffers drastically. Therefore,
The heap sizes should be set to values such
that the maximum amount of memory the VM
uses does not exceed the amount of available
physical RAM.

PLM00013 11.2 Windows Server Installation A-17

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

JVM options for tuning the WebSphere Application Server memory usage
Typical
Suggested
JVM option Description default
value
value
-XX:PermSize Sets the section of the heap reserved for the Client: 32 128 MB
permanent generation of the reflective data for the MB
JVM. This setting should be increased to optimize
the performance of applications that dynamically load Server: 64
and unload many classes. MB

Note

PermSize memory consumption is in addition

to the -Xmx value set by the user on the JVM
options. Setting this to a value of 128 MB
eliminates the overhead of increasing this part
of the heap.
-XX:MaxPermSize Allows for the JVM to be able to increase the N/A 256 MB
PermSize setting to the amount specified.
Initially, when a VM is loaded, the MaxPermSize
is the default value, but the VM does not actually
use that amount until it is needed. If you set both
PermSize and MaxPermSize to 256 MB, the overall
heap increases by 256 MB in addition to the -Xmx
setting.
Note

If an application needs to load or reload a

large number of classes, the following error
may result:
messageOutOfMemoryError: PermGen space

Typically, this means that the JVM started with

an insufficient maximum value for permanent
generation.

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.

• 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.

A-18 Windows Server Installation PLM00013 11.2

 Troubleshooting

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.

• Installation of Ghostscript 8.53 software required by the previewservice feature.

o A free Ghostscript installer is available at the following link:
https://download.industrysoftware.automation.siemens.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

PLM00013 11.2 Windows Server Installation A-19

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

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.
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.

o PreviewService

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 applications 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.

A-20 Windows Server Installation PLM00013 11.2

 Troubleshooting

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.

Recovering a corrupted database

Overview of recovery 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

PLM00013 11.2 Windows Server Installation A-21

 Appendix
Appendix A: A: Troubleshooting
Troubleshooting

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.

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.

3. Launch TEM and reinstall Teamcenter.

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.

2. Launch TEM and reinstall Teamcenter.

TEM creates a new database during installation.

A-22 Windows Server Installation PLM00013 11.2

Appendix B: Distribution media

Teamcenter distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Teamcenter documentation distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

PLM00013 11.2 Windows Server Installation

Appendix B: Distribution media

Teamcenter distribution media

Siemens PLM Software distributes the following software and documentation images for Teamcenter
11.2:

Image Description

Teamcenter software Contains Teamcenter software for your operating system (IBM AIX,
Oracle 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.
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, expand all
ZIP files to a common directory to assemble the image before
you begin installation.
Teamcenter Contains Teamcenter help content and also installation programs for
documentation Teamcenter help and the Siemens PLM Documentation Server.
Rich client over-the-web Contains the files required to install the Teamcenter rich 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.
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:

PLM00013 11.2 Windows Server Installation B-1

 Appendix
Appendix B: B: Distribution
Distribution mediamedia

Directory Description
additional_applications Contains directories containing applications such as
Teamcenter client communication system (TCCS), Security
Services, and the Siemens PLM Software Common Licensing
Server.
additional_documentation Contains documentation about 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 Teamcenter online help in HTML and
PDF formats. It also includes installation programs for the Siemens PLM Documentation Server and
Teamcenter documentaton.

File Description
help_install_instructions.pdf PDF document that contains instructions for installing the
PLM Documentation Server and instructions for installing
Teamcenter documentation.

B-2 Windows Server Installation PLM00013 11.2

 Distribution media

File Description
splmdocserver Directory that contains installation programs for the Siemens
PLM Documentation Server.
• Windows systems:
wntx64\setup.exe

• UNIX/Linux systems:
unix/splmdocserver.tar.Z

The wntx64 and unix directories also contain additional

installation procedures in PDF format.
tchelp.exe Teamcenter documentation installation program for Windows
platforms. You must install the PLM Documentation Server
before running this program.
tchelp.bin Teamcenter documentation installation program for
UNIX/Linux platforms. You must install the PLM
Documentation Server before running this program.
help_packages Contains Teamcenter online help content and search data to
be installed in the PLM Documentation Server:
• tc11.2_en_US_html_webServer.zip
Teamcenter online help

• tc11.2_en_US_pdf_webServer.zip
Teamcenter online help collection in PDF format

• tc11.2_en_US_tcrefs_webServer.zip
Teamcenter developer references, which include:

o C++ API Reference

o Integration Toolkit (ITK) Function Reference
o Services Reference
help_architecture Contains the PLM help server web applications and
architecture for deployment in an existing web server.
DataModelReport.zip Contains the Teamcenter Data Model Report. This reference
contains documentation on standard Teamcenter data model
objects, such as business objects, classes, attributes,
properties, lists of values (LOVs), and others.
This archive requires approximately 6.4 GB of disk space
when expanded.
JavaDoc.zip Contains documentation for Teamcenter user interface
components you can use in your rich client customizations.

Teamcenter online help must be installed into the Siemens PLM Documentation Server or an
existing web server that contains the online help architecture. Online help can then be configured
for Teamcenter clients.

PLM00013 11.2 Windows Server Installation B-3

Appendix C: Solutions and features reference

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15

Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15

PLM00013 11.2 Windows Server Installation

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 Part Family Classification Integration
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
Dispatcher (Dispatcher Server) Dispatcher Server
Rich Client (2-tier and 4-tier) Teamcenter Rich Client (2-tier and 4-tier)
Business Modeler IDE Business Modeler IDE Standalone

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.

PLM00013 11.2 Windows Server Installation C-1

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

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.
Business Modeler IDE Standalone Installs only the Business Modeler IDE client without requiring a connection to
a Teamcenter server.
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.
Teamcenter Rich Client (2-tier and 4-tier) Installs a rich client that uses the communication infrastructure introduced in
Teamcenter 11.2.

This rich client is configurable for both two-tier and four-tier deployments. It
connects to the Teamcenter server (in a two-tier environment) or web tier
(in a four-tier environment) using Teamcenter client communication system
(TCCS). This differs from the existing two-tier rich client that connects directly
to the Teamcenter server using IIOP protocol, and the existing four-tier rich
client that connects directly to the Teamcenter web tier using HTTP protocol.

The newer TCCS-based rich client architecture provides the ability to stream
responses from the Teamcenter server (tcserver) to the client, an advantage
over the previous two- and four-tier architectures that required server
responses be completely prepared before sending.

This streaming is performed by a multiplexing proxy, or MUX, that is part of

Teamcenter Enterprise Communication System (TECS), a Java component
of the Teamcenter enterprise tier. The MUX supports four-tier communication
through its internal Jetty HTTP server, which services requests from the
Teamcenter web tier. The MUX communicates with the tcserver using
Teamcenter Transfer Protocol (TCTP).
Teamcenter Rich Client (Shared Disk Installs the rich client in a shared location. This client can be run from multiple
Deployment) hosts.

C-2 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Teamcenter features
Feature/Subfeature Description
Teamcenter Rich Client 2-tier Installs a Teamcenter two-tier rich client that communicates with the
Teamcenter corporate server using IIOP protocol. It supports most
Teamcenter features and does not require a web tier.

Note

IIOP-based communication in the two-tier rich client is deprecated

and will be removed in a future version of Teamcenter. Siemens
PLM Software recommends using the Teamcenter Rich Client
(2-tier and 4-tier) feature, which uses TCCS communication.

Teamcenter Rich Client 4-tier Installs a four-tier rich client that connects directly to the Teamcenter web tier
using HTTP protocol.

Note

This rich client is an alternative to the newer four-tier rich client

provided by the Teamcenter Rich Client (2-tier and 4-tier)
feature, which communicates with the Teamcenter web tier using
Teamcenter client communication system (TCCS).

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.

Java EE 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.
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 Management Console Installs Teamcenter Management Console, an SSL-secured console for
managing and monitoring server-side components such as the Java EE
server manager and Java EE web tier. The console's tabbed interface
resembles a web application server console. Teamcenter administrators
can use the console to access multiple Teamcenter management features
from a single page.

PLM00013 11.2 Windows Server Installation C-3

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Teamcenter features
Feature/Subfeature Description
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.

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.

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 Installs the Shared Metadata Cache Service.
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.

C-4 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Teamcenter features
Feature/Subfeature Description
Web Tier for .NET Installs the middle tier processes that communicate with Teamcenter server
processes.
Extensions Extensions to Teamcenter server and client functionality.
4D Planning Installs the 4D Planning feature. 4D Planning is the capability to add a time
component to process planning to simulate and visualize construction over
an extended period of time.
Product Configurator Installs Product Configurator, a feature that enables you to formally introduce
and manage variability across your product suite.
Product Line Planning Installs Product Line Planning.
Simulation Process Management Installs Simulation Process Management, a packaged solution that provides
unique simulation process and data management capabilities for CAE
engineers and CAE analysts performing analysis work.
Symbolica Integration Installs the Teamcenter integration to Symbolica software. Symbolica is a
Siemens PLM Software product that allows you to visually create and perform
complex mathematical equations. The Symbolica integration enables you to
create, save, and revise Symbolica files within Teamcenter. These files can
also be referenced by NX part files stored within Teamcenter.

Symbolica software can be downloaded from GTAC.

Test Manager Installs the application model used to manage assembly tests for virtual
assessment processes in Automotive Edition and Aerospace and Defense.
Weld Management Installs the template that manages NX welding features in Teamcenter.
Change Management Configurator Interface Installs the configurator interface for Change Manager.
Dimensional Planning and Validation Multi Field Installs multifield key functionality in Dimensional Planning and Validation.
Key
Advanced PLM Services 4th Generation Design features.
4th Generation Design Installs 4th Generation Design (4GD) functionality for the Teamcenter server.
4GD allows users of NX CAD or Lifecycle Visualization to cooperate in real
time during the design cycle of a product.
MDConnectivity Installs support for multidisciplinary (MD) objects. This enables management
of files from piping and instrumentation diagram/drawing (P&ID) applications
in Teamcenter.
System Modeling Installs the system modeling template for multidisciplinary (MD) objects.
4th Generation Design Change Management Installs 4th Generation Design functionality for Change Manager. This feature
Integration requires Teamcenter Foundation and Change Management.
Diagramming Installs the diagramming template for multidisciplinary (MD) objects.
4th Generation Design Issue Management Installs 4th Generation Design functionality for Issue Manager. This feature
requires Teamcenter Foundation and Issue Management.
Aerospace and Defense Aerospace and Defense features.
Aerospace and Defense Foundation Installs Aerospace and Defense functionality for the Teamcenter server. This
feature requires Teamcenter Foundation and Vendor Management.
Aerospace and Defense Change Installs the change management functionality for the Aerospace and
Management Defense Foundation feature. This feature requires Teamcenter Foundation
and Aerospace and Defense Foundation.
Aerospace and Defense Foundation Installs the Aerospace and Defense Foundation training program for the
Training Aerospace and Defense Foundation feature. This feature requires
Teamcenter Foundation, Vendor Management, and Aerospace and
Defense Foundation.
Automotive Teamcenter Automotive Edition and additional supporting features.

PLM00013 11.2 Windows Server Installation C-5

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Teamcenter features
Feature/Subfeature Description
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.
Consumer Packaged Goods Features to support Consumer Packaged Goods.
Brand Management Installs the Brand Management template for 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.
Packaging and Artwork Installs packaging and artwork functionality for Consumer Packaged Goods.
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.
Content Management Base Installs the data model for Content Management.
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.
JT Editor Integration for Rich Client Installs JT editor integration for the rich client. This feature requires
Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.

C-6 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Teamcenter features
Feature/Subfeature Description
Spatial Search Installs Spatial Search capabilities of the cacheless search engine.

This feature requires Dispatcher Server.

Note

Cacheless search is installed with Teamcenter Foundation, but its

capabilities must be enabled through TEM.

Bounding box generation from JT Enables generation of bounding box data from JT files, providing secondary
data for the cacheless search engine.

This feature requires Dispatcher Server. Also, during Teamcenter

installation, you must install the Spatial Search translator (JtToBboxAndTso).

Note

Cacheless search is installed with Teamcenter Foundation, but its

capabilities must be enabled through TEM.

Trueshape generation from JT Enables generation of Trushape data from JT files, providing secondary data
for the cacheless search engine.

This feature requires Dispatcher Server. Also, during Teamcenter

installation, you must install the Spatial Search translator (JtToBboxAndTso).

Note

Cacheless search is installed with Teamcenter Foundation, but its

capabilities must be enabled through TEM.

Bounding box generation from NX Enables generation of bounding box data when saving NX files, providing
secondary data for the cacheless search engine.

Note

Cacheless search is installed with Teamcenter Foundation, but its

capabilities must be enabled through TEM.

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.

Required information:

• 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.

Note

Cacheless search is installed with Teamcenter Foundation, but its

capabilities must be enabled through TEM.

Enterprise Knowledge Foundation Enterprise Knowledge Foundation features.

PLM00013 11.2 Windows Server Installation C-7

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Teamcenter features
Feature/Subfeature Description
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.

Required information:

• Host name and port number of the Java servlet running the Teamcenter
Application Registry.

• 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.
Change Management Provides a flexible change management framework that integrates with other
Teamcenter products.

Note

If you install this feature, you may need to set the

HiddenPerspectives preference in the rich client.

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.
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.
Finish Management Installs Finish Management for Teamcenter. A finish represents a finishing
process on a part. It may be used to improve appearance, adhesion, corrosion
resistance, tarnish resistance, chemical resistance, wear resistance, and
remove burrs and so on.
Materials Management Installs the Materials Management solution, which stores approved material
and substance information imported from a third-party database (for example,
Granta, IMDS) into a material library in the Teamcenter database.
Stock Material Installs the Stock Material feature for Teamcenter.

Many parts are made from stock materials such as bar stock, tubing stock
and sheet stock. This features enables you to manage stock materials in
Teamcenter, performing actions like creating libraries of stock materials and
assigning stock materials to parts.
Work Package Management Enables management of work packages in Teamcenter.

Work packages or packages are typically collections of CAD files and

documentation that outsourcing partners require to build, test or maintain
components or subassemblies of larger products. Packages serve as
revisable collections of product information that can be used in a variety of
contexts.

C-8 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Teamcenter features
Feature/Subfeature Description
Change and Schedule Management Installs the Change and Schedule Management interface, which enables you
Interface to selectively propagate the problem, impact, solution, and reference items
related to a change object to the related plan items (schedules) leaf-level
schedule tasks.
Issue Management Installs Issue Manager, which allows you to track problems, or issues, with
products by managing the review, approval, and implementation of issues.
Render Document for Rich Client Provides Render Management capabilities for the rich client. This feature
requires Dispatcher Client for Rich Client.

For information about installing Dispatcher features require installing and

configuring file translators for the Dispatcher Server.
Dispatcher Server Installs the following Dispatcher Server components: scheduler, module and
administration client.
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.
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.
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 requires
Rich Client 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.

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 theAs-Built template for Teamcenter maintenance, repair, and
overhaul.

If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the As-Built Manager solution in your rich client
distribution instance.1

1. For more information about installing rich client distribution instances, see Install a rich client distribution instance

PLM00013 11.2 Windows Server Installation C-9

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Teamcenter features
Feature/Subfeature Description
As-Maintained Management Installs the As-Maintained feature to support the As-Maintained physical
structure management for Service Manager.

If you select this feature and you use the Over-the-Web Installer to install the
rich client, include the As-Maintained Management for Service Manager
solution in your rich client distribution instance.1
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.

If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the Service Planning solution in your rich client
distribution instance.1
As-Built and As-Maintained Alignment Enables interoperability of data created by the As-Built Management and
As-Maintained Management features of Service Manager.

If you select this feature and you use the Over-the-Web Installer to install the
rich client, include the As-Built and As-Maintained Alignment for Service
Manager solution in your rich client distribution instance. 1
Service Event Management Installs Service Event Management to support service process management
for Teamcenter maintenance, repair, and overhaul.

If you select this feature and you use the Over-the-Web Installer to install the
rich client, include the Service Event Management Extensions for Service
Manager solution in your rich client distribution instance.1
Service Planning and Service Processing If you select this feature and you use the Over-the-Web Installer to install
Alignment the rich client, include the Service Processing Extensions for Service
Manager solution in your rich client distribution instance.1
Service Request Processing Installs the Service Planning and Service Processing Alignment module to
support using discrepancies in Service Planner.

If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the Service Request Manager solution in your rich
client distribution instance.1
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.

If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the Service Scheduling solution in your rich client
distribution instance.1
MRO Automated Scheduling 1.0 MRO Automated Scheduling features.
Service Forecasting Installs the Service Forecasting plug-in to Service Scheduler.
Service Automated Scheduling Installs the Service Automated Scheduling plug-in to Service Scheduler.
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.
Customization for eM-Server Integration Installs additional data types for Tecnomatix server integration customization.
Logistic Process Planning Installs the logistic process planning feature for Manufacturing Process
Planner.
MTM Data Card Installs the Methods Time Measurement (MTM) data card system for
Manufacturing.

C-10 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Teamcenter features
Feature/Subfeature Description
Work Instructions Installs the work instructions feature for Manufacturing Process Planner.
Customization for Process Simulate Installs additional data types for Process Simulate Integration Customization.
Integration
Database Configuration for DPV Installs the database configuration for DPV. This feature requires Teamcenter
Foundation, GM Overlay, and Customization for eM-Server Integration.
MES Integration Installs the Manufacturing Execution System Integration (MES Integration),
which collects the bill of process, bill of materials, and any relevant work
instructions into a work package that is released to the MES system.
Manufacturing Characteristics Information Installs additional data types for Manufacturing Characteristics Information.
eBOP reports Customization Installs additional data types for eBOP Reports Customization. This feature
requires Teamcenter Foundation and Customization for eM-Server
Integration.
MES Issue Management Installs additional data types required for shop floor issue management when
integrating with a manufacturing execution system. This feature provides
Issue Manager support for the Manufacturing Execution System Integration
(MES 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.
Manufacturing support for 4th Generation Installs additional data types required to work with 4th Generation Design
Design (4GD) objects in Manufacturing Process Planner.
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 Reference in the
Teamcenter developer references online help collection.
Mechatronics Process Management Features to support Mechatronics Process Management.
EDA for Business Modeler IDE Integrates Teamcenter EDA with the Business Modeler IDE.
EDA Server Support Installs the dataset types and transfer modes required to support Teamcenter
EDA, the application that integrates ECAD applications with Teamcenter.
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.
Wire Harness Configuration Installs Teamcenter schema support for wire harnesses.
Calibration and Configuration Data Installs the Calibration and Configuration Data Management (CCDM) feature
Management for Embedded Software Solutions, 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.

PLM00013 11.2 Windows Server Installation C-11

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Teamcenter features
Feature/Subfeature Description
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
operations do not work from any interface (rich client, thin client, custom
utilities, and other clients).
ESM Software Installs ESS software types and updates preferences. Without these, ESS
operations do not work from any interface (rich client, thin client, custom
utilities, and other clients).
Embedded Software Design Data Installs Embedded Software Design Data Management for Embedded
Management Software Solutions.
Multi-Disciplinary Associations Installs multidisciplinary (MD) associations in Teamcenter.

Multidisciplinary (MD) objects help facilitate collaboration between various

disciplines during the product design phase.
Platform Extensability Platform extensability features.
Installs Enterprise Integration functionality for the Teamcenter Integration
Enterprise Integration
Framework.
Installs the Product Master Management integration for the Teamcenter
.PMM Integration
Integration Framework.
Installs the Substance Compliance integration for the Teamcenter Integration
Substance Compliance Integration
Framework.
Integration Framework Teamcenter Integration Framework features.
Integration Framework Core Installs the Teamcenter Integration Framework core.
SRM Integration Installs the SRM integration for the Teamcenter Integration Framework.
Global Services Global Services features.
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.

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).
Catia Non BOM Installs the CATIA Non BOM feature.
ERP Connect Installs the ERP Connect Toolkit interface that integrates Teamcenter with
other Enterprise Resource Planning (ERP)-supported applications, such as
BAAN.
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.
Linked Data Services Linked Data Services features.

C-12 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Teamcenter features
Feature/Subfeature Description
Java EE Based Linked Data Web Installs web services that allow other lifecycle tools to use Teamcenter
Services services like change management. This feature builds the OSLC WAR file
and installs the Linked Data Services (LIS) core service.
Linked Data Framework for Change Installs the change management integration module of Linked Data Services
Management Integration (LIS).
Installs the Linked Data Services (LIS) framework. This includes the data
Linked Data Framework Support
model for LIS.
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).

Product Line Engineering Product Line Engineering features.

Product Line Engineering Request Installs the Product Line Engineering Request feature, which provides the
ability to validate key performance measurements of objects by system
engineers and validation engineers.
Measurable Attributes and Targets Installs Measurable Attribute and Target Management, which allows users to
manage measurable attributes (goal and measured value) for requirements,
logic blocks, connections. and so on.
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.
Reuse and Standardization Reuse and Standardization features.
Library Management Installs a data model and functionality for Library Management that supports
creating and configuring multiple libraries to meet the reuse needs of
business processes and targeted sets of users. Library Management
leverages Classification and includes a rules-based search capability for
enforcing technical constraints in the context of a design process (known as
Specifications, which is a distinct and separate feature from Specification
Manager used to support the Consumer Packaged Goods industry).

The lbrmanager command line utility is also included with this feature.

Note

Deploying the Library Management feature automatically deploys

the following prerequisite features:

• Advanced PLM Services for Applications

• Advanced PLM Services for Partitioning

• Advanced PLM Services for Realization

• Next Generation Classification foundation

Supplier Relationship Management Supplier Relationship Management features.

SRM Integration Installs the Supplier Relationship Management integration for data exchange.

PLM00013 11.2 Windows Server Installation C-13

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Teamcenter features
Feature/Subfeature Description
Vendor Management Installs the optional Vendor Management solution.
Substance Compliance Installs the optional Substance Compliance solution, which assists in
compliance with environmental laws, regulations, standards, and other
requirements for parts and for the parts manufactured or supplied from an
external source.

This solution requires the Teamcenter materials management solution.

Substance Compliance IMDS Integration Installs the International Material Data System (IMDS) integration for
Substance Compliance.
Systems Engineering and Requirements Features that support Systems Engineering and Requirements Management.
Management
Teamcenter Extensions for Microsoft Office Installs Teamcenter Extensions for Microsoft Office.
Requirements Management Installs the Requirements Management functionality for Systems Engineering
and Requirements Management.
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.
Teamcenter Integration for NX Teamcenter Integration for NX features.
Installs core functionality of Teamcenter Integration for NX. This feature
requires a local installation of NX.

Teamcenter Integration for NX is a data management tool used with NX.

When you use NX with this integration, Teamcenter runs at the same time as
NX Part Family Classification Integration
a separate process, enabling NX and Teamcenter to communicate so you
can create, store, and access your NX data within a Teamcenter database.

For information about using Teamcenter Integration for NX, see Teamcenter
Integration for NX in the NX help collection.
NX Foundation 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 provided through NX Remote Manager.
NX Rich Client Integration Installs Teamcenter Integration for NX for the rich client. This feature requires
Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Installs 4th Generation Design (4GD) support for Teamcenter Integration
for NX.
NX 4th Generation Design
4GD allows users of NX CAD or Lifecycle Visualization to cooperate in real
time during the design cycle of a product.
NX Piping and Instrumentation Diagram Installs support for managing NX piping and instrumentation diagram/drawing
(P&ID) Design (P&ID) files in Teamcenter. Teamcenter supports P&ID files as part of its
support for multi-disciplinary (MD) objects.
Miscellaneous Additional Teamcenter features.

Data Share Manager Installs the Data Share Manager, an asynchronous file upload and download
monitor for File Management System (FMS) transactions.
LOGISTICS for Rich Client Installs the logistics feature for the rich client.

C-14 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Related topics
• Managing variability of your entire product suite

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.

Solution Description
Over-the-Web Installer Installs the program that installs the rich client over the web.
This solution is required.
Data Share Manager Installs the Data Share Manager, an asynchronous file upload
and download monitor for File Management System (FMS)
transactions.
Microsoft Visual C++ Installs the Microsoft Visual C++ libraries required for the rich
2005/2008/2010/2012 client and for the FMS client cache (FCC).
Redistributables
Teamcenter client Installs Teamcenter client communication system (TCCS).
communication system
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.
Teamcenter Client for Microsoft Installs Teamcenter Client for Microsoft Office, which provides
Office 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. This solution adds a custom
Teamcenter ribbon to Microsoft Office applications.
Rich Client 4-Tier Installs the rich client software required for the four-tier
architecture. This solution is required.
4D Planning solution for Rich Installs 4D Planning functionality. 4D Planning is the capability
Client 4-Tier to add a time component to process planning to simulate and
visualize construction over an extended period of time.
4th Generation BOM Design Installs BOM design support for 4th Generation Design.
Alignment for Rich Client 4-Tier

PLM00013 11.2 Windows Server Installation C-15

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Solution Description
4th Generation BOM Installs 4G-BOM support for 4th Generation Design.
Management (4G-BOM) for
Rich Client 4-Tier
4th Generation Design for Rich Installs 4th Generation Design (4GD) support for the rich client.
Client 4-Tier
4GD allows users of NX CAD or Lifecycle Visualization to
cooperate in real time during the design cycle of a product.
As-Built Manager Adds As-Built functionality for the four-tier rich client. As-Built is
part of Teamcenter maintenance, repair, and overhaul.
This solution requires the As-Built Management feature on the
Teamcenter corporate server.
As-Maintained Management for Installs Service Event Management to support service process
Service Manager management for As-Maintained functionality of Teamcenter
maintenance, repair, and overhaul.
This solution requires the As-Maintained Management feature
on the Teamcenter corporate server.
CAD-BOM Alignment (CBAExt) Installs CAD-BOM alignment, which allows Teamcenter to
for Rich Client 4-Tier interact and share visual data with Product Master Management.
CPG Materials for Rich Client Installs CPG Materials support for Consumer Packaged Goods.
4-Tier
Calibration and Configuration Installs Calibration and Configuration Data Management
Data Management (CCDM) for (CCDM) for Embedded Software Solutions, which allows rich
Rich Client 4-Tier client users 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.
Change Management and Installs the Change Management and Schedule Management
Schedule Manager Interface interface for Change Manager, which enables you to selectively
propagate the problem, impact, solution, and reference items
related to a change object to the related plan items (schedules)
leaf-level schedule tasks.
Content Management Base + Installs Content Management and enables management of
S1000D for Rich Client 4-Tier documentation for the S1000D standard.
Content Management is the application used to manage
technical documentation using SGML and XML information
stored in a Teamcenter database.
Content Management S1000D Enables management of documentation for the S1000D 4.0
4.0 for Rich Client 4-Tier standard in Content Management .
Content Management is the application used to manage
technical documentation using SGML and XML information
stored in a Teamcenter database.

C-16 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Solution Description
Contract Management for Rich Installs Contract Data Management, which allows you to
Client 4-Tier 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.
Dispatcher Client for Rich Installs Dispatcher Client for the rich client.
Client
Dashboard Installs the Reporting and Analytics Dashboard interface.
ESDDM for Rich Client 4-Tier Installs Embedded Software Solutions Design Data
Management support for the rich client.
Embedded Software Manager InstallsEmbedded Software Solutions support for the rich client.
for Rich Client 4-Tier
Finish Management for Rich Installs Finish Management for Teamcenter. A finish represents
Client 4-Tier a finishing process on a part. It may be used to improve
appearance, adhesion, corrosion resistance, tarnish resistance,
chemical resistance, wear resistance, and remove burrs and
so on.
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 Installing the
Dimensional Planning and Validation solution in the Dimensional
Planning and Validation online help collection.
GM Overlay for Rich Client Installs the Teamcenter Automotive Edition–GM Overlay
4-Tier application. This solution is optional.
GS Monitoring GUI for Rich Configures the rich client for use with the Global Services
Client 4-Tier Monitoring GUI for Rich Client feature.
Lifecycle Interoperability Installs support for Lifecycle Interoperability Services (LIS) in
Services Framework for Rich the rich client.
Client 4-Tier
Logistics Planning solution for Installs Logistics Planning support for the rich client.
Rich Client 4-Tier
MDO for Rich Client 4-tier Installs support for multi-disciplinary objects (MDO). This
enables management of files from piping and instrumentation
diagram/drawing (P&ID) applications in Teamcenter.
MES Integration solution for Installs rich client support for the Manufacturing Execution
Rich Client 4-tier System Integration (MES Integration), which collects the bill of
process, bill of materials, and any relevant work instructions into
a work package that is released to the MES system.
MTM Data Card for Rich Client Installs the Methods Time Measurement (MTM) data card
system. This solution is optional.

PLM00013 11.2 Windows Server Installation C-17

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Solution Description
Manufacturing Product Installs additional data types for Manufacturing Characteristics
Characteristics solution Information.
for Rich Client 4-Tier
Manufacturing support for 4th Installs Manufacturing Process Management support for 4th
Generation Design for Rich Generation Design.
Client 4-Tier
Materials Management for Rich Installs rich client support for Materials Management, which
Client 4-Tier stores approved material and substance information imported
from a third-party database (for example, Granta, IMDS) into a
material library in the Teamcenter database.
NX Manager for Rich Client Configures the rich client to use Teamcenter Integration for NX
4-Tier 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 Configurator for Rich Provides Product Configurator capabilities for the rich client.
Client Product Configurator enables you to formally introduce and
manage variability across your product suite.
Product Master Management Installs Product Master Manager, a rich client application that
(PMM) for Rich Client 4-Tier 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
Management, see Installing and Upgrading Product
Master Management in the Product Master Management
online help collection.
Requirements Management Installs Requirements Management functionality for Systems
Engineering and Requirements Management.
SCM ClearCase for Rich Client Installs the integration between Teamcenter and the IBM
4-Tier 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 Client Installs the Supplier Relationship Management integration for
4-Tier data exchange.

C-18 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Solution Description
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.
This solution requires the Service Planning feature on the
Teamcenter corporate server.
Stock Material for Rich Client Installs Stock Material support for the rich client.
4-Tier
Many parts are made from stock materials such as bar stock,
tubing stock and sheet stock. The Stock Material solution
enables you to manage stock materials in Teamcenter,
performing actions like creating libraries of stock materials and
assigning stock materials to parts.
Substance Compliance IMDS Installs rich client support for the International Material Data
Integration for Rich Client System (IMDS) integration for Substance Compliance.
4-Tier
Substance Compliance for Installs rich client support for the Teamcenter substance
Rich Client 4-Tier compliance solution. Substance Compliance assists in
compliance with environmental laws, regulations, standards,
and other requirements for parts and for the parts manufactured
by or supplied from an external source.
This solution requires the Teamcenter materials management
solution.
Systems Engineering Installs the Systems Engineering application, which provides
capabilities such as functional modeling and budgets.
This feature requires the rich client.
Teamcenter Applications for Installs Teamcenter Extensions for Microsoft Office and the
Microsoft Office Teamcenter Plugin for Microsoft Project, which allows Microsoft
Project users to exchange data directly with Schedule Manager.
Separate installation of Microsoft Office is required.
Teamcenter Rapid Start Client Installs Teamcenter Rapid Start features for the rich client.
Teamcenter Visualization Configures the rich client to use the embedded viewer when
(Embedded) for Rich Client Teamcenter lifecycle visualization is separately installed on the
4-Tier client workstation. This solution is optional.
Teamcenter Visualization Configures the Teamcenter lifecycle visualization application
(Stand-alone) for Rich Client (the stand-alone application viewer). Separate installation of
4-Tier Teamcenter lifecycle visualization is required. This solution is
optional.
Test Manager for Rich Client Installs the application model used to manage assembly tests
4-Tier for virtual assessment processes in Automotive Edition and
Aerospace and Defense.
Vendor Management for Rich Installs Vendor Management support for the rich client.
Client 4-Tier

PLM00013 11.2 Windows Server Installation C-19

 Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Solution Description
Work Instructions Solution for Installs the Work Instructions view for the rich client.
Rich Client 4-Tier
4th Generation Design Change Installs the Change Manager integration for 4th Generation
Management Integration for Design.
Rich Client 4-Tier
ADS Foundation for Rich Client Installs Aerospace and Defense functionality for the rich client.
4-Tier
Content Management DITA for Enables management of documentation for the DITA standard
Rich Client 4-Tier in Content Management.
Render Document for Rich Provides Render Management capabilities for the rich client.
Client This feature requires Dispatcher Client for Rich Client.
Rich Client 4-Tier Lite Edition Installs the lite edition of the four-tier rich client. This solution
is optional.
Service Processing Extensions Installs the Service Processing Extensions for Service Manager
for Service Manager for the rich client. This functionality is available only if you have
purchased and have a license for Service Event Management.
This solution requires the Service Planning and Service
Processing Alignment feature on the Teamcenter corporate
server.
As-Built and As-Maintained Installs the operability functionality between theAs-Built
Alignment for Service Manager Management and As-Maintained Management applications for
Service Manager. This functionality is available only if you have
purchased and have a license for As-Built Management and
As-Maintained Management.
This solution requires the As-Built and As-Maintained
Alignment feature on the Teamcenter corporate server.
Service Event Management Installs the Service Event Management functionality for Service
Extensions for Service Manager for the rich client. This functionality is available only
Manager if you have purchased and have a license for Service Event
Management.
This solution requires the Service Event Management feature
on the Teamcenter corporate server.
Service Request Manager Installs service request processing for Teamcenter maintenance,
repair, and overhaul.
This solution requires the Service Request Processing feature
on the Teamcenter corporate server.

C-20 Windows Server Installation PLM00013 11.2

 Solutions and features reference

Solution Description
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.
This solution requires the Service Scheduler feature on the
Teamcenter corporate server.
Service Forecasting Installs rich client support for the Service Forecasting plug-in to
Service Scheduler.
Service Automated Scheduling Installs rich client support for the Service Automated Scheduling
plug-in to Service Scheduler .

PLM00013 11.2 Windows Server Installation C-21

Appendix D: Web tier context parameters

PLM00013 11.2 Windows Server Installation

Appendix D: Web tier context parameters

The following tables describe web tier context parameters provided by Teamcenter web tier solutions.

Web tier required parameters

Parameter Description
General parameters
TcLocale 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.
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
the server manager (installed using Teamcenter
Environment Manager).
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
Environment Manager).
When configuring multiple environments, use a
different port number for each environment.

PLM00013 11.2 Windows Server Installation D-1

 Appendix
Appendix D: D:
Web Web tier context
tier context parameters
parameters

Web tier required parameters

Parameter Description
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.
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
Platform, Enterprise Edition (Java EE) 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

D-2 Windows Server Installation PLM00013 11.2

 Web tier context parameters

Web tier required parameters

Parameter Description
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
the server manager (installed using Teamcenter
Environment Manager).
Max_Capacity Specifies the maximum number of concurrent
connections to Teamcenter servers the server pool
maintains.
Note

This parameter applies to web application

deployment on WebLogic, JBoss, and Oracle
Application Server. For other application
servers, the maximum pool size must be set
using the application server console.
LogVolumeName Name of the log volume.

PLM00013 11.2 Windows Server Installation D-3

 Appendix
Appendix D: D:
Web Web tier context
tier context parameters
parameters

Web tier required parameters

Parameter Description
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.
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.
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.
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.
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.

Web tier optional parameters

Parameter Description
General parameters

D-4 Windows Server Installation PLM00013 11.2

 Web tier context parameters

Web tier optional parameters

Parameter Description
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.

PLM00013 11.2 Windows Server Installation D-5

 Appendix
Appendix D: D:
Web Web tier context
tier context parameters
parameters

Web tier optional parameters

Parameter Description
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.
USER The 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

1. 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.jboss.org/jgroups.

D-6 Windows Server Installation PLM00013 11.2

 Web tier context parameters

Global Services context parameters

Parameter Description
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.
TCGS_WS_URL Specifies the URL of the Global Services web services
WAR file within the Global Services Ode BPEL
enterprise application, for example:
TCGS_WS_URL = http://localhost:8080/tcgs-ws

This is used by services that must send HTTP SOAP

requests to other web services.
TCGS_ODE_URL Specifies the URL to the Global Services Ode BPEL
web application, for example:
TCGS_ODE_URL = http://localhost:8080/tcgs-ode

This is used by services that must send HTTP SOAP

requests to BPEL processes.

PLM00013 11.2 Windows Server Installation D-7

 Appendix
Appendix D: D:
Web Web tier context
tier context parameters
parameters

Global Services context parameters

Parameter Description
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
TcGSSOAJNDI Specifies the Teamcenter services-oriented
architecture (SOA) connector EJB JNDI name.
TcGSEntJNDI Specifies the Teamcenter Enterprise connector EJB
JNDI name.

D-8 Windows Server Installation PLM00013 11.2

Appendix E: Deploying Teamcenter help in an
existing web server

PLM00013 11.2 Windows Server Installation

Appendix E: Deploying Teamcenter help in an
existing web server

Depending on your network or security needs, you may choose not to install the Siemens PLM
Documentation Server. In this case, you may deploy the online help architecture on an existing web
server you have already configured and are maintaining.
By default, the deployment of Solr within the PLM Help Server is not secure. This presents two
known issues:
• Solr administration could be accessible to an end user.

• Updates or deletes could be sent to the Solr server by a malicious upload attack.

To mitigate these issues, you must secure the Solr instance. Siemens PLM Software recommends
you place the PLM Help Server architecture in a location on the network where the host name and
ports are not accessible. For example, behind a firewall.
The PLM Help Server architecture can be deployed on a supported web server with a servlet
container. This can be Apache Tomcat, Jetty, or any web server listed on the Siemens PLM
Software Certification site. You can then install Teamcenter help collections using the files in the
help_packages directory in the documentation distribution image.
For information about how to deploy the PLM Help Server architecture and Teamcenter
help collections on an existing web server, see the webserver_install.pdf document in the
help_architecture\wntx64 directory in the documentation distribution image.

PLM00013 11.2 Windows Server Installation E-1

Appendix F: Glossary

PLM00013 11.2 Windows Server Installation

Appendix F: 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.

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.

PLM00013 11.2 Windows Server Installation F-1

 Appendix
Appendix F: F: Glossary
Glossary

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.

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,

F-2 Windows Server Installation PLM00013 11.2

 Glossary

and a transient datastore mechanism for transporting reports, PLM XML, and other nonvolume
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.
Contrast with two-tier architecture.

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.

FSC
See FMS server cache (FSC).

PLM00013 11.2 Windows Server Installation F-3

 Appendix
Appendix F: F: Glossary
Glossary

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 time-out 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 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 consisting of hosts that do not all run the same platform, for
example, a corporate server running on a UNIX host, a web application server running on a Linux
host, and workstations running on Microsoft Windows.
Contrast with homogeneous network environment.

homogeneous network environment

Teamcenter network environment in which all hosts run the same platform, for example, a corporate
server, web tier, and Teamcenter clients all running on Microsoft Windows or all running on SUSE
Linux.
Contrast with heterogeneous network environment.

F-4 Windows Server Installation PLM00013 11.2

 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.

Lifecycle Visualization
Visualization components available in the rich client, the thin client, and as a stand-alone application.
A scalable solution for the viewing and analysis of 2D and 3D product data, Lifecycle Visualization is
available in a number of configurations to meet the requirements of different organizations.

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.

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.

PLM00013 11.2 Windows Server Installation F-5

 Appendix
Appendix F: F: Glossary
Glossary

Multi-Site Collaboration network

Network of independent Teamcenter sites that are within the same enterprise and share data using
Multi-Site Collaboration.

My Teamcenter
In the Teamcenter rich client and thin 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.

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.

F-6 Windows Server Installation PLM00013 11.2

 Glossary

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.

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.

PLM00013 11.2 Windows Server Installation F-7

 Appendix
Appendix F: F: Glossary
Glossary

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.

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. Compare to thin client.

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.

F-8 Windows Server Installation PLM00013 11.2

 Glossary

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.

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.

PLM00013 11.2 Windows Server Installation F-9

 Appendix
Appendix F: F: Glossary
Glossary

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.

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

F-10 Windows Server Installation PLM00013 11.2

 Glossary

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, 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. Compare to rich 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.

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. Contrast with four-tier architecture.

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.

PLM00013 11.2 Windows Server Installation F-11

 Appendix
Appendix F: F: Glossary
Glossary

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.

Web Application Manager

Graphical installation utility that generates supporting web files (WAR 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 Platform, Enterprise
Edition (Java EE) 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.

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.

F-12 Windows Server Installation PLM00013 11.2

Siemens Industry Software

Headquarters
Europe
Granite Park One
Stephenson House
5800 Granite Parkway
Sir William Siemens Square
Suite 600
Frimley, Camberley
Plano, TX 75024
Surrey, GU16 8QD
USA
+44 (0) 1276 413200
+1 972 987 3000

Asia-Pacific
Americas
Suites 4301-4302, 43/F
Granite Park One
AIA Kowloon Tower, Landmark East
5800 Granite Parkway
100 How Ming Street
Suite 600
Kwun Tong, Kowloon
Plano, TX 75024
Hong Kong
USA
+852 2230 3308
+1 314 264 8499

About Siemens PLM Software

© 2015 Siemens Product Lifecycle Management

Siemens PLM Software, a business unit of the Siemens
Software Inc. Siemens and the Siemens logo are
Industry Automation Division, is a leading global provider
registered trademarks of Siemens AG. D-Cubed,
of product lifecycle management (PLM) software and
Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,
services with 7 million licensed seats and 71,000 customers
Parasolid, Solid Edge, Teamcenter, Tecnomatix and
worldwide. Headquartered in Plano, Texas, Siemens
Velocity Series are trademarks or registered trademarks
PLM Software works collaboratively with companies
of Siemens Product Lifecycle Management Software
to deliver open solutions that help them turn more
Inc. or its subsidiaries in the United States and in other
ideas into successful products. For more information
countries. All other trademarks, registered trademarks
on Siemens PLM Software products and services, visit
or service marks belong to their respective holders.
www.siemens.com/plm.