Server Unix

Teamcenter 8
Installation on UNIX and Linux

Servers Guide
Publication Number
PLM00011 C
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2009 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
All trademarks belong to their respective holders.
2 Installation on UNIX and Linux Servers Guide PLM00011 C

Contents
Part I: Getting started
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installation and deployment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Part II: Database server installation
Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Set shell limits and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Upgrade Oracle server and databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Configure an Oracle database for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Part III: Teamcenter server installation
Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Install the licensing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Select destination directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Verify required character set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Ensure correct mode on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Install a volume server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Install NX and Teamcenter Integration for NX or NX Integration . . . . . . . . . . 4-5
Best installation practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Install a Teamcenter corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Run the postinstallation tasks program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Modifying the services file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Start Teamcenter database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
PLM00011 C Installation on UNIX and Linux Servers Guide 3

Contents
Back up new installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Part IV: Adding features
Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Install the J2EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Install the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Install the Business Modeler IDE as a stand-alone application . . . . . . . . . . . . 8-1
Install the Business Modeler IDE to an existing Eclipse environment . . . . . . . 8-3
Allocate memory to the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . 8-5
Start the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Installing a custom solution or third-party template . . . . . . . . . . . . . . . 9-1

Install a template using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Update a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Install the Manufacturing content kit . . . . . . . . . . . . . . . . . . . .... . . . . . . . 10-1
Populate the sample database for Manufacturing . . . . . . . . . . .... . . . . . . . 10-2
Install the Manufacturing Tooling Library . . . . . . . . . . . . . . . .... . . . . . . . 10-2
Planning data migration from Genius4000 to Resource Manager ... . . . . . . . 10-6
Migrate Genius4000 data to Resource Manager . . . . . . . . . . . . .... . . . . . . . 10-8
Installing Teamcenter’s reporting and analytics . . . . . . . . . . . . . . . . . 11-1

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Create the Reporting and Analytics database . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Configure the Reporting and Analytics license file . . . . . . . . . . . . . . . . . . . . . 11-2
Install Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Deploy Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Complete Reporting and Analytics installation . . . . . . . . . . . . . . . . . . . . . . . 11-5
Part V: Web tier installation
J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

J2EE Web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Installing thin client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Installing rich client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Part VI: Additional configuration and maintenance
Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . 13-1

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

Contents
Localizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Configure rich client language display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Environment settings for non-English locales . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Deploying thin client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Deploying rich client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . 15-2
Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Patching Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Install patches on the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Patch the distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Patch the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
Installing Teamcenter maintenance packs . . . . . . . . . . . . . . . . . . . . . . 17-1
Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Uninstall Teamcenter configurations and installations . . . . . . . . . . . . . . . . . . 18-1

Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Part VII: Appendixes
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . B-1

Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . B-5
Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . B-9
Recovering from a corrupted Oracle-based database . . . . . . . . . . . . . . . . . . . B-10
Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Teamcenter documentation distribution image . . . . . . . . . . . . . . . . . . . . . . . C-2
Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

Contents
Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1-1. Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1-2. Two-tier deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
1-3. Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1-4. Four-tier deployment (enterprise and Web tiers on same host) . . . . . . . . 1-13
1-5. Four-tier deployment (enterprise and Web tiers on separate hosts with HTTP
server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
1-6. Four-tier deployment (multiple enterprise tier hosts and Web tier
hosts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
1-7. Four-tier deployment (load balancing) . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2-1. Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2-2. Basic File Management System deployment . . . . . . . . . . . . . . . . . . . . 2-12
13-1. Multiple databases (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . 13-5
15-1. Sample silent installation configuration file . . . . . . . . . . . . . . . . . . . . . 15-4
Tables
Required hard disk space for Teamcenter configurations . . . . . . . . . . . . 1-2

2-1. Basic Teamcenter network nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2-2. Additional Teamcenter network nodes . . . . . . . . . . . . . . . . . . . . . . . . 2-3
3-1. AIX minimum shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3-2. HP-UX minimum kernel parameter values for single database
instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3-3. Solaris 10 minimum resource control values for single database
instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3-4. SUSE Linux minimum shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
5-1. Required File Management System information . . . . . . . . . . . . . . . . . 5-3
7-1. Required server manager information . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
11-1. TEM panels for Reporting and Analytics installation . . . . . . . . . . . . . . 11-3
12-1. Additional Teamcenter Web applications . . . . . . . . . . . . . . . . . . . . . . . 12-5
12-2. Context parameters for shared deployment . . . . . . . . . . . . . . . . . . . . 12-18
12-3. Rich client required parameter and table values . . . . . . . . . . . . . . . . 12-22
12-4. Rich client optional parameter values . . . . . . . . . . . . . . . . . . . . . . . . 12-25
12-5. Teamcenter’s lifecycle visualization (embedded viewer) parameter and table
values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
12-6. Teamcenter’s lifecycle visualization (stand-alone application viewer)
parameter and table values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
12-7. Teamcenter Integration for NX parameter and table values . . . . . . . . 12-27
12-8. Content Management System for Rich Client 4-Tier . . . . . . . . . . . . . . 12-27
14-1. UNIX Environment Settings for Non-English Locales . . . . . . . . . . . . . 14-2
15-1. Silent installation XML elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Contents
B-1. Installation problems and error messages . . . . . . . . . . . . . . . . . . . . . . B-2

B-2. Update Manager FTP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
D-1. Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
D-2. Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
E-1. Web tier required parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
E-2. Web tier optional parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5
E-3. Global Services context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . E-9

Part
I Getting started
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Site planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
PLM00011 C Installation on UNIX and Linux Servers Guide

Chapter
1 Getting started
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
System hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Web tier support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Software integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Hewlett-Packard HP-UX considerations . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Linux considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-6

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

Chapter
1 Getting started
This guide describes how to install Teamcenter 8 on UNIX and Linux servers. This
includes installation of Teamcenter servers using Teamcenter Environment Manager
and the Teamcenter Web tier using the Web Application Manager.
This guide assumes you have a thorough working knowledge of your operating
system and general knowledge of Teamcenter use.
Prerequisites
Install prerequisite software and verify that your hardware is supported for
Teamcenter 8.
For information about versions of operating systems, third-party software,
Teamcenter software, and system hardware certified for your platform, see the
Siemens PLM Software Certification Database:
http://support.ugs.com/online_library/certification/
To use the certification database, choose the platform and products you use, and
then click Show Certifications.
Note
Some software requirements differ for non-English locales. When viewing the
certification database, make sure you note any exceptions for your locale.
Platforms
Make sure your Teamcenter 8 server host runs one of the following supported
platforms:
• Microsoft Windows1
• Hewlett-Packard HP-UX
• IBM AIX
• Sun Solaris
• SUSE Linux
• Apple Macintosh Mac OS2
For information about supported platform versions, see the certification database.
1. For information about installing Teamcenter on Windows servers, see the Installation on Windows Servers Guide.
2. Limited client support only. For information about installing Teamcenter on Macintosh clients, see the Installation on UNIX,
Linux, and Macintosh Clients Guide.
PLM00011 C Installation on UNIX and Linux Servers Guide 1-1

Chapter 1 Getting started
Note
The Teamcenter thin client and FMS client cache (FCC) are supported on
Macintosh platforms. No Teamcenter servers or rich clients are supported
on Macintosh.
Teamcenter installation tools (Teamcenter Environment Manager and Web
Application Manager) require the ISO8859–1 character set. Make sure this
character set is available on your host. If you are uncertain or want to verify
this character set, see Verify required character set.
System hardware
Make sure your Teamcenter host has the required amount of disk space available.
Required hard disk space for Teamcenter configurations shows the required disk
space for the following common Teamcenter configurations:
• Corporate server
The corporate server contains the features included in the Corporate Server
solution in Teamcenter Environment Manager (TEM). Additional features may
require additional disk space.
For more information, see Install a Teamcenter corporate server.
• Two-tier rich client

The two-tier rich client contains the features included in the Rich Client 2–tier
solution in Teamcenter Environment Manager (TEM). Additional features may
require additional disk space.
For more information, see the appropriate Teamcenter client installation guide
(for Windows or UNIX/Linux).
• Web tier
The Web tier includes the Web Application Manager, a distribution server, and a
distribution server instance that contains the Over-the-Web installer and Rich
Client 4–tier solutions. Additional solutions may require additional disk space.
For more information, see J2EE Web tier installation.
Required hard disk space for Teamcenter configurations

Corporate Two-tier
Platform server rich client Web tier
Hewlett-Packard HP-UX (Itanium) 3.0 GB Not supported 3 GB
Hewlett-Packard HP-UX 3.0 GB Not supported 3 GB
IBM AIX 2.0 GB 450 MB 3 GB
SUSE Linux 2.0 GB 300 MB 3 GB
Sun Solaris 2.5 GB 300 MB 3 GB
Microsoft Windows 1.5 GB 450 MB 4.5 GB
1-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Getting started
Database
Teamcenter requires a relational database management system (RDBMS) for storing
Teamcenter data. Before you install a Teamcenter, you must install an Oracle
database server and make sure your Teamcenter corporate server host has access
to the server.
For information about supported database server versions, see the certification
database.
For information about installing a database server for Teamcenter, see Oracle
installation and configuration.
Web browser
The Teamcenter thin client and four-tier rich client require a Web browser.
Teamcenter 8 supports the following Web browsers:
• Windows systems: Microsoft Internet Explorer and Mozilla Firefox
• UNIX and Linux systems: Mozilla Firefox
• Macintosh systems: Apple Safari
On Macintosh systems, the thin client is supported on Apple Safari browsers. No

rich clients are supported on Macintosh.
For information about versions supported, see the certification database.
Web tier support

If you use the Teamcenter J2EE Web tier, install the following software:
Java Runtime Environment (JRE)
Install a supported JRE on the host where you build Teamcenter Web
applications.
J2EE application server

Install a supported J2EE application server on the host where you deploy
Teamcenter Web applications.
For supported versions of these products, see the certification database.
Software integrations
If you use Teamcenter 8 integrations to other software products, install those
products before you install Teamcenter 8. These include the following Teamcenter
integrations:
Teamcenter’s lifecycle visualization
NX Integration
SCM ClearCase for Rich Client
Some Siemens PLM Software products require separate licenses from your Siemens
PLM Software representative. Siemens PLM Software products are licensed using
the Siemens PLM Software Common Licensing Server.

For more information about the Common Licensing Server, see Install the licensing
server.
Enabling Teamcenter installation

After you install prerequisite software, locate the Teamcenter software and
documentation distribution images and make sure they are accessible to your client
host. For descriptions of Teamcenter distribution images, see Distribution media.
Note
If you mount the Teamcenter software distribution image on a remote NFS
server, you must launch Teamcenter Environment Manager on the local
server node.
Hewlett-Packard HP-UX considerations

Hewlett-Packard HP-UX systems require special configuration to support Java.
You must perform these steps to enable Teamcenter clients and installation tools
on HP-UX systems. For more information, see the Hewlett-Packard guidelines at
the following URL:
http://www.hp.com/products1/unix/java/infolibrary/prog_guide/configuration.html
Linux considerations
On Linux systems, make sure your system is set to use the ISO8559-1 character
set rather than the default UTF-8 character set. Teamcenter installation tools
require this setting.
Configuring Teamcenter installation

Before you install Teamcenter, create an operating system logon account for
Teamcenter. Teamcenter services run on the server as this user account.
Log on using this account when you install the Teamcenter corporate server and
when you perform maintenance such as upgrading or installing updates using
Teamcenter Environment Manager.
Starting Teamcenter installation

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

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

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

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

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

The Web Application Manager is a tool that installs thin client and rich client
solutions and builds Teamcenter J2EE Web applications.
3. You create this directory when you install the Web Application Manager as described in J2EE Web tier installation.


You launch the Web Application Manager by entering the insweb command. The
Web Application Manager allows you to create multiple Web applications that
contain different sets of Teamcenter solutions. This enables you to create Web
applications for different groups of users in your network. Your Web applications
can access the same Teamcenter corporate server, but provide different subsets of
Teamcenter functionality. The Web Application Manager creates separate staging
locations and separate deployable files4 for each Web application. Some Teamcenter
solutions require other solutions and some solutions may not be combined with other
solutions in the same Web application. For more information about using the Web
Application Manager, see J2EE Web tier installation.
Basic concepts about Teamcenter installation

Determine the Teamcenter servers and network architectures suit your needs and
which features you want to install.
Database server
A Teamcenter network requires access to a database server.
Before you install Teamcenter, you or your database administrator must install and
configure a database server to store Teamcenter data. The Teamcenter corporate
server must have access to a database server or a database client. Teamcenter
supports Oracle or Microsoft SQL Server databases.
For information about installing a database server for Teamcenter, see Oracle
installation and configuration.
For Oracle configuration settings and tuning methods to optimize Teamcenter
performance, see the Teamcenter Deployment Guide, available in the documentation
section of Siemens PLM Software’s support site. The Teamcenter Deployment
Guide also provides an in-depth review of Oracle database performance issues and
diagnosis, and configuration and tuning guidelines.
4. A deployable file is a Web archive (WAR) or enterprise archive (EAR) file, depending on the solutions it contains.

Getting started
For Microsoft SQL Server configuration settings and tuning methods to optimize
Teamcenter performance, see the Teamcenter Deployment Guide, available in the
documentation section of Siemens PLM Software’s support site. The Teamcenter
Deployment Guide also provides an in-depth review of Microsoft SQL database
performance issues and diagnosis, and configuration and tuning guidelines.
Note
Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannot
connect to Microsoft SQL Server database servers.
Teamcenter servers
You can install different types of Teamcenter servers according to the features you
use and your load distribution needs.
Corporate server
A Teamcenter corporate server installation includes the following components:
• Teamcenter shared binary executables and files
• Teamcenter shared data subdirectories and files
• Database connection
• Teamcenter volume
• Additional optional Teamcenter features such as File Management System
(FMS) and Teamcenter File Services (TCFS)
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’s Client for Microsoft Office and Network Folders.
Rich client
The rich client is a platform-independent client implementation (Java application)
for users who interact with Teamcenter frequently. It is extendable and able to run
both Teamcenter and customer-written applications. Customers can also extend the
standard user interface.
The rich client application is deployed on each user workstation using Teamcenter
Environment Manager or the Over-the-Web Installer, depending on which
Teamcenter network architecture you use. The rich client is supported in both
architectural models described in Two-tier architecture and Four-tier architecture.
Thin client
The thin client provides access to Teamcenter through a standard commercial Web
browser, such as Microsoft Internet Explorer or Mozilla Firefox. The user interface

provides a streamlined browser-based view of product information stored in a

Teamcenter database.
The thin client is supported only in the four-tier architectural model described in
Four-tier architecture.
Network Folders
Teamcenter’s Network Folders is an extension (plug-in) to Microsoft Windows

Explorer. Network Folders provides access to Teamcenter through Windows
Explorer. Users unfamiliar with the rich client and thin client interfaces can perform
document management of Teamcenter objects from Windows Explorer without
launching Teamcenter.
Network Folders is supported only on Microsoft Windows platforms and only in the
four-tier architecture model described in Four-tier architecture.
Teamcenter network architectures

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

• Client tier
The client tier comprises the Teamcenter rich clients.
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’s Integration for Microsoft Office,
require the Web tier, a component of the four-tier architecture. To enable
these features for a two-tier rich client, you can connect the two-tier rich
client to a deployment of the Web tier. For information about functionality
you can add to a rich client and which add-ons require the Web tier, see
Rich client installation.
• Resource tier
The resource tier comprises a database server, database, volumes, and file
servers.

Getting started
Rich Client Rich Client Rich Client

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

Tier
Figure 1-1. 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) and Teamcenter File Services (TCFS)
manage the rich client access to volumes:
• The FMS server cache (FSC) process and TCFS run on the server hosting the
volume.
• The FMS client cache (FCC) process runs on the rich client host.
For more information about FMS and TCFS and two-tier rich client architecture, see
File Management System installation.

TCFS
2-Tier Rich Client
FCC FSC Volume
Teamcenter
Server
Teamcenter Files
(application root)
Database
Database
Server
Figure 1-2. Two-tier deployment
Four-tier architecture
The four-tier architecture model comprises the following tiers:

• Client tier
The client tier comprises the Teamcenter rich client, thin client, and other clients
such as Teamcenter’s Client for Microsoft Office.
Note
The rich client can be deployed with additional functionality, such as
Lifecycle Visualization, Teamcenter’s Integration for Microsoft Office, and
Teamcenter Integration for NX or NX Integration 4.0.1. (Teamcenter
Integration for NX/NX Integration 3 is not supported.)
For information about the functionality you can add, see Rich client
installation.
• J2EE Web tier

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

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

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

Tier Teamcenter EAR
Teamcenter Server
Enterprise Servers Manager
Tier
Resource
Tier Volume Database
Figure 1-3. Four-tier architecture

You can design deployments that host the Web tier, resource tier, and enterprise
tiers on the same computer or on separate computers:
• Smaller sites can run the pool of servers and the server manager on the same
host as the Web tier.

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

To configure a separate TreeCache cluster, Siemens PLM Software recommends
configuring a different port (multicast) or set of ports (TCP) for each cluster.
The JMX HTTP adapter allows you to view the status of the server pool and
dynamically alter the pool configuration values (the values are not persistent).
Access this functionality from the following URL:
http://host-name:jmx-port
Replace host-name with the name of the host running the server manager. Replace
jmx-port with the number of the port running the JMX HTTP adapter. This port
number is defined when you install the J2EE based server manager.
The first time you log on to the adapter, use manager for both the user name
and the password. You can change the user name and password to unique values
using the adapter.
Teamcenter File Management System (FMS) and Teamcenter File Services (TCFS)
manage 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).
• TCFS runs on each server hosting a volume.
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.

Getting started
Thin Client 4-Tier Rich Client

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

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

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

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

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

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

Getting started
Selecting and configuring features

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

Installing a Teamcenter network consists of the following general tasks:
Installing a database server
Install a database server according to the vendor’s documentation and the

Teamcenter guidelines provided in Oracle installation and configuration.
Installing a Teamcenter server

Install one or more Teamcenter servers as described in Teamcenter server
installation.
Installing the Web tier
Install the J2EE Web tier as described in J2EE Web tier installation.
Installing Teamcenter clients
Install Teamcenter clients as described in the appropriate client installation guide

(for Windows or UNIX and Linux).

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

Planning the Teamcenter network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Installing Teamcenter components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Thin client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
File Management System installation . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Installing File Management System . . . . . . . . . . . . . . . . . . . . . . 2-11
Installing Teamcenter File Services . . . . . . . . . . . . . . . . . . . . . . . 2-15
Creating volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Lifecycle Visualization installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Global Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Teamcenter Linking installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Security Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Teamcenter online help installation . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Configuring online help for thin clients . . . . . . . . . . . . . . . . . . . . 2-18
Configure direct file access for rich clients . . . . . . . . . . . . . . . . . . 2-19
Configure over-the-Web access for rich clients . . . . . . . . . . . . . . . . 2-19
Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Oracle server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Network environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Homogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Heterogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Required operating system and user accounts . . . . . . . . . . . . . . . . . . . . . 2-22

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

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

A Teamcenter network table 2-1 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 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.
Table 2-1. Basic Teamcenter network nodes

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

Chapter 2 Site planning

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

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

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

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

corporate server.
1. Teamcenter provides server managers based on the J2EE and the Microsoft .NET platforms. The .NET Web tier is supported
only on Windows platforms.

Site planning

Network node Role
Web-tier application Teamcenter service node that contains an installation of the
server Teamcenter Web tier application deployed in a third-party
application server.
Teamcenter clients Hosts containing an installation of the Teamcenter
rich client executables and connected to a Teamcenter
corporate server or application server. Hosts accessing the
Teamcenter thin client over the Web.
Table 2-2. Additional Teamcenter network nodes

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

Table 2-2. Additional Teamcenter network nodes

Network node Role
Multi-Site Network node running daemon processes that perform
Collaboration IDSM proxy services for IDSM servers.
proxy server
Typically, the IDSM proxy server node is connected between
a firewall and the IDSM server nodes. IDSM requests
originating from external sites go through the firewall
directly into the proxy server node, which relays the IDSM
requests to the IDSM servers. In this way, the proxy server
protects the IDSM servers from direct access from external
sites. It also simplifies firewall management because the
firewall manages only one TCP/IP port for all external
IDSM requests.
Quick part locator Component of Repeatable Digital Validation (RDV).
(QPL) server The QPL server provides a qpl daemon used with
DesignContext. This daemon coexists with all other
Teamcenter daemons. For QPL-based DesignContext,
QPL server setup is required. For Appearance-based
DesignContext, QPL server setup is not required.
Installing Teamcenter components

Your installation process depends on the network architecture and Teamcenter
features you use.
Two-tier architecture installation
The primary components of a two-tier installation require three general installation

tasks:
1. Install the database and database server using Oracle or MS SQL Server tools.
For the installation procedures, see part II, Database server installation.
2. Install Teamcenter executables and files, create and/or populate the database,
and configure a volume using Teamcenter Environment Manager.
For the installation procedures, see part III, Teamcenter server installation.
3. Install the rich client on a client workstation using Teamcenter Environment

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

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

A four-tier installation involves installation tasks for each tier:
1. Install the resource tier using the third-party database server software, either
Oracle or MS SQL Server.
For the installation procedures, see part II, Database server installation.
2. Install the enterprise tier using Teamcenter Environment Manager, being sure
to choose the server manager component.
Teamcenter Environment Manager installs the pool of Teamcenter servers and
the server manager, creates and or populates the database, and configures a
volume.2
For the installation procedures, see part III, Teamcenter server installation.
3. Generate the J2EE Web tier as an enterprise archive (EAR) file using the Web
Application Manager and deploy the EAR file in a J2EE application server.
2. Teamcenter provides server managers based on the J2EE and the Microsoft .NET platforms. The .NET Web tier is supported
only on Windows platforms.

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

Site planning
6 Thin Client 4-Tier Rich Client

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

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

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

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

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

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

Site planning
Open Web page
Created by Web application manager

using 'Distribution Server' instance otw.html
installing.html
otw_installer.jar
Uses - instance = "web application name" Check that client
server_name = "hostname:rmi port" installed is current
and install or update.
Example - instance = "Teamcenter 2 Tier OTW
server_name = "hostname:12001"
Distribution Server
Exe - start_server
Uses - webapps.dat
RMI
Created by Web application manager
Exe - start_rmi
using 'Distribution Server'
Figure 2-1. 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’s lifecycle visualization (embedded viewer)

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

• Teamcenter’s lifecycle visualization (stand-alone application viewer)

When you choose this option, the rich client is enabled to launch Teamcenter’s
lifecycle visualization. Users must independently install Teamcenter’s lifecycle
visualization executable files on the client hosts. All client hosts installing a
distribution instance must have Teamcenter’s lifecycle visualization installed
in the same location.
Note
The Teamcenter’s lifecycle visualization integration requires the
presentation tier application, a component of the four-tier architecture. To
enable Teamcenter’s 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’s Automotive Edition–GM Overlay

When you choose this option, the Teamcenter’s Automotive Edition–GM Overlay
executable files are included in the distribution instance.
• Teamcenter’s Integration for Microsoft Office

When you choose this option, the Teamcenter’s Integration for Microsoft Office
executable files are included in the distribution instance.
• Teamcenter Linking
When you choose this option, the rich client is enabled to support the linking
of objects between Teamcenter, Teamcenter’s portfolio, program and project
management, and Teamcenter’s systems engineering and requirements
management. Separate installation of Teamcenter Linking components and
Teamcenter Application Registry are required.
Note
Teamcenter Linking requires the presentation tier application, a
component of the four-tier architecture. To enable Teamcenter’s
Integration for Microsoft Office 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 EDA.
When you choose this option, the rich client is configured for use with Teamcenter
EDA. The Teamcenter EDA stand-alone client must also be installed.
• SCM ClearCase
When you choose this option, the executable files are included in the distribution
instance for the integration between Teamcenter and the IBM Rational
ClearCase software configuration management (SCM) tool.
For a complete list of available Teamcenter features for the rich client, see Solutions
and features reference.
For information about creating, deploying, and updating the rich client distribution
server and rich client distribution instances, see Installing rich client Web

Site planning
applications. Instructions for installing the rich client over the Web on a client
host are in the Installation on UNIX, Linux, and Macintosh Clients Guide and the
Installation on Windows Clients Guide.
Thin client installation

The Teamcenter thin client is a Web browser-based application. You install the thin
client as part of the Web tier application. To install the Web tier, you use the Web
Application Manager to create and install an enterprise archive (EAR) file that you
then deploy in a third-party application server on the Web tier host.
Users access the thin client from the Web tier host using a third-party Web browser
such as Microsoft Internet Explorer, Netscape, and Mozilla. No aspect of the thin
client is installed on a user workstation other than the required third-party Web
browser.
File Management System installation

Teamcenter requires installing two file management systems:
• File Management System (FMS)
FMS downloads and uploads file data for the rich client, embedded viewer, and
the thin client configured with Teamcenter’s lifecycle visualization. Multi-Site
Collaboration also uses FMS servers to transfer data.
• Teamcenter File Services (TCFS)

The Teamcenter Organization application uses TCFS to create volumes and
perform other administrative functions. TCFS also supports file access for NX
4.0.0 or earlier and Teamcenter’s lifecycle visualization 5.0 or earlier when
you use these products with Teamcenter. (NX 4.0.1 and Teamcenter’s lifecycle
visualization 6.0 and later use 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.
You install both FMS and TCFS on Teamcenter server hosts using Teamcenter
Environment Manager. Both FMS and TCFS must run as the same operating
system user for the purpose of accessing volume data. This does not require them
to run on the same host or operating system, but they must run as the same user
for file permissions access to the volume. If the FMS server cache is not managing
any volumes, that is, if it is purely a cache server, it can run as any user that is
convenient.
Installing File Management System

FMS provides the following functions:
• Volume server for file management
• Shared server-level performance cache for shared data access between multiple
users
• Client-based private user cache for rich clients

• Transient data store mechanism for transporting reports, PLM XML, and other
nonvolume data between the Web and client tiers in the four-tier architecture
FMS caching enables placing the data close to the user, while maintaining a central
file volume and database store.
FMS requires the installation of FMS server cache (FSC) and FMS client cache
(FCC) components (figure 2-2):
• The FSC component provides a server process and file caches for Teamcenter
server hosts.
• The FCC component provides a client process and file caches for rich clients
on user workstations.
Rich Client
FCC Vol 1
LAN SYSTEMS
Rich Client
FCC Vol 2
TC Server
FSC Server
Visualization
Client
Vol 3
FCC
Figure 2-2. 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.

Site planning
Any deployment of Teamcenter requires a minimum of one FSC server. You can
deploy multiple FSC servers, each performing a multiple roles or each performing
a designated purpose as either a volume, a cache, or a configuration server. When
you install multiple volumes on different hosts for the same database, the multiple
FSC servers are linked through a common master FSC. (You can manually configure
more than one master FSC.)
You must install an FSC server on:
• Each host running a Teamcenter server manager.
• Each host that will contain a Teamcenter volume.
FSC servers and caches are configured using XML-based files, in a hierarchical
structure:
• FMS master configuration file (fmsmaster_fsc_id.xml)
The master configuration file describes the File Management System network
and defines FSC groups. It is the highest file in the hierarchy and can define
default values for FSCs and FCCs, such as the maximum sizes of the caches.
Each installation of Teamcenter requires one FMS master configuration file.
At least one FSC server reads this file and is called the master FSC. Other
FSC servers in the network download FMS configuration information from the
master FSC server.
If you install only one FSC server in a Teamcenter network, it is the master.
• FSC configuration file (fscfsc_id.xml)

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

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

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

• Caches files on the client host
The FCC process manages three file caches:

• A write cache containing whole files uploaded to a Teamcenter volume
• A read cache containing whole files downloaded from a Teamcenter volume
• A segment cache for Teamcenter’s 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’s lifecycle visualization
6.0 or later is installed on the workstation and used with the rich client, it
optionally uses the FCC.
When you create the rich client instance to be installed on user workstations,
you configure the location of the cache on the workstation and the maximum size
of files downloaded from the volume or uploaded to the volume. Installing the
rich client instance on a workstation simultaneously installs the FCC process
and caches. No additional configuration steps are required.
For information on configuring the FCC while creating the rich client instance,
see Installing rich client Web applications. Configuring the FCC this way
may be the only configuration you require, but you can take advantage of
additional configuration options by manually configuring the FCC. For manual
configuration information, see the Preferences and Environment Variables
Reference.
• 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’s 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:
– 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.
– File streaming
Teamcenter’s lifecycle visualization 6.0 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.
– 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.
– Deployment flexibility

Site planning
FMS components support a multitude of deployment configurations. This

enables administrators to geographically locate volumes and shared FSC
servers close to client workstations, providing the ability to tune the system
for optimal file transfer performance.
For information on installing an FCC for use with the thin client and
Teamcenter’s lifecycle visualization, see the Installation on UNIX, Linux, and
Macintosh Clients Guide or Installation on Windows Clients Guide.
Installing Teamcenter File Services

The Teamcenter Organization application uses Teamcenter File Services (TCFS) to
create volumes and perform other administrative functions. TCFS also supports file
access for NX 4.0 or earlier and Teamcenter’s lifecycle visualization 5.0 or earlier
when you use these products with Teamcenter.
You control the security modes for file access by setting the TC_Security_Level
preference. For more information about this preference and about TCFS
configuration, see the Teamcenter Preferences and Environment Variables Reference.
Creating volumes
Using Teamcenter Environment Manager installation program, you create two
types of Teamcenter volumes:
• Standard volumes
Standard volumes are UNIX directories 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 Teamcenter File
Services (TCFS) and File Management System (FMS):
– When creating a volume, you must install and configure TCFS. TCFS runs
a daemon process that allows access to Teamcenter volumes through the
Teamcenter Organization application. There can be multiple TCFS server
nodes within the network, and each node can control volume access for more
than one database.
– FMS provides the volume services once the volume is created.
• Transient volumes
A transient volume is a UNIX directory that Teamcenter uses to store temporary
data for transport of reports, PLM XML, and other data between the Web tier
and client tier in a deployment of the four-tier architecture. One transient
volume is required per Teamcenter server host.
You can create a transient volume directory on a server host when installing
Teamcenter and populating a Teamcenter database (the installation program
adds the definition to the fmsmaster_fsc_id.xml configuration file). For
examples of manually configuring transient volumes that cannot be accomplished
using the installation program, see the Preferences and Environment Variables
Reference.

Note
Teamcenter uses transient volumes only in a deployment of the four-tier
architecture. For a deployment of the two-tier architecture, Teamcenter
stores this data into a temporary directory on the rich client host, rather
than in a defined transient volume. The temporary directory is defined
either by the start_server script or by the Transient_Volume_RootDir
on the client host.
Teamcenter administrators can also create volumes using the rich client
Organization application. For information about creating volumes after installation
of Teamcenter, see the Organization Guide.
Lifecycle Visualization installation
For enterprise-wide product visualization capability, you can configure two Siemens
PLM Software products with Teamcenter:
• Lifecycle Visualization embedded viewer (rich client only)

The Lifecycle Visualization embedded viewer is embedded in the rich client user
interface. The embedded viewer provides full 2D visualization capabilities and
3D viewing and is available to all Teamcenter users.
The embedded viewer is installed on user workstations over the Web as part of
a rich client distribution instance. The license level is configured as part of
the rich client distribution image. All users installing a rich client distribution
image that includes Lifecycle Visualization must have administration privileges
on the workstation.
• Lifecycle Visualization stand-alone application viewer (rich client and thin client)
The Lifecycle Visualization stand-alone application viewer is launched from
either the Teamcenter rich client user interface or the thin client user interface.
Users can also run it as a stand-alone application. The suite includes the
embedded viewer and Teamcenter’s lifecycle visualization mockup.
The stand-alone application viewer is individually installed on each client
workstation using the Teamcenter’s 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 File Management System:
– When configured with the rich client, Lifecycle Visualization uses

Teamcenter volumes and FMS, including the FSC and the FCC installed
with the rich client on client workstations.
– When installed as a stand-alone application, Lifecycle Visualization can use

Teamcenter volumes and FMS if users install the stand-alone FCC on the
workstation. Installing a stand-alone FCC is described in the Installation on
UNIX, Linux, and Macintosh Clients Guide and the Installation on Windows
Clients Guide.

Site planning
– When configured with the thin client, Lifecycle Visualization uses

Teamcenter volumes and the FSC. Optionally, users can install an FCC on
their workstations for use with their Lifecycle Visualization installation.
Earlier supported versions of Lifecycle Visualization use TCFS only to manage

file access and volumes.
Note
You can configure both Lifecycle Visualization products 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.
Global Services installation

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

data from Teamcenter’s enterprise knowledge management.
To enable users to exchange data between Teamcenter and Teamcenter’s enterprise

knowledge management, you must install and configure Global Services, the
Teamcenter and Teamcenter’s enterprise knowledge management connectors.
Global Services is available in the additional_applications/tcgs directory on the
Teamcenter software distribution image. For installation information, see Install
Global Services.
Teamcenter Linking installation

Teamcenter Linking enables users to create links between Teamcenter objects and
objects in Teamcenter’s systems engineering and requirements management and
Teamcenter’s 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
21-1.
For information, see Teamcenter server installation.
b. Create a two-tier Teamcenter rich client distribution instance, configuring

Security Services for the client by specifying the same Teamcenter
application ID, Security Services Login Service URL, and Identity Service
Web URL as specified when configuring Security Services on the corporate
server.
For information, see Install rich client distribution instances.
3. If you are deploying the four-tier architecture:

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

You can install and configure Teamcenter online help for access directly from a file
system (rich clients only) or over the Web (thin clients and rich clients).
Configuring online help for thin clients

The Web tier application serves the online help to thin client users. You can install
the help files on a server host either as part of generating the Web tier application or
separately using Teamcenter Environment Manager.
Part of Web tier application:
When generating the Web tier application using Web Application Manager,
choose the option to install the online help files.
Separate from Web tier application:

Site planning
1. Install the help files using Teamcenter Environment Manager.
2. Generate the Web tier application using Web Application Manager, but do not
choose the option to install the online help files.
3. Modify the following Teamcenter preferences to add the full path to the help files:
WEB_help_server
WEB_core_help_server
When you install the help files as part of the Web tier application, the help URLs
are automatically configured correctly using a relative path to the help files.
Configure direct file access for rich clients
You can install and configure online help so that two-tier and four-tier rich clients
access the help directly from files installed in the file system of a server host. You
cannot configure direct file access for the thin client.
1. Install the online help on a server host using Teamcenter Environment Manager.
2. When creating a two-tier or four-tier rich client distribution instance, supply the
following values for the online help context parameters:
Context parameter Value

RichClientHelpWebServer Specify file://.
RichClientHelpLocation Specify the full path to the help files for both
Windows and UNIX systems.
For information, see table 12-3 and Install rich client distribution instances.
Configure over-the-Web access for rich clients
When you deploy the Teamcenter four-tier architecture, you can configure four-tier
and two-tier rich clients to access online help served over-the-Web by the Web tier
application. When you do not deploy the four-tier architecture, you can deploy the
presentation tier application to serve online help over-the-Web to two-tier rich clients.
You can install the help files on a server host either as part of or separate from
the Web or presentation tier application. Perform one of the following procedures,
depending on how you want to access online help.
Configure online help as part of Web tier or presentation tier application
1. Generate the Web tier or presentation tier application using Web Application
Manager and choose the option to install the online help files.
2. Create a two-tier or four-tier rich client distribution instance, supplying the



RichClientHelpWebServer Specify http://host-name:port, replacing
host-name and port with the name of the host and
the port where the Web tier or presentation tier
application files are deployed in an application
server.
RichClientHelpLocation Specify the full path to the installed help files
index.htm file.
Configure online help separate from the Web tier or presentation tier application
1. Install the help files using Teamcenter Environment Manager.
2. Generate the Web tier or presentation tier application using the Web Application
Manager, but do not choose the option to install the online help files.
3. Modify the following Teamcenter preferences to add the full path to the help files:
WEB_help_server
When you install the help files as part of the Web tier or presentation tier
application, the help URLs are automatically configured correctly using a
relative path to the help files.
4. Create a two-tier or four-tier rich client distribution instance, supplying the


RichClientHelpWebServer Specify http://host-name:port, replacing
host-name and port with the name of the host and
the port where the Web tier or presentation tier
application files are deployed in an application
server
RichClientHelpLocation Specify the full path to the installed help files
index.htm file.
Other considerations
Certain issues regarding distribution of database and license servers can affect
planning of your Teamcenter network.

Site planning
Oracle server considerations

Determine whether to create a new Oracle database and/or upgrade existing Oracle
databases. You must install Oracle Server if a certified version is not installed on the
system. For certified versions of Oracle, see the Siemens PLM Software Certification
Database:
You must also:
• Identify the systems to be Oracle database servers. Usually, such systems
are dedicated high-capacity servers, specifically tuned for Oracle. An Oracle
database server must be directly accessible on the network by each workstation
running Teamcenter.
• Install Oracle on each database server or NFS-mount Oracle to each database

server.
• Create databases locally on servers.
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.
For information about installing Oracle Server, creating Oracle database instances,
and upgrading Oracle databases, see Oracle installation and configuration.
Network environment considerations

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

In a homogeneous environment, the database server, Teamcenter application server,
Teamcenter data server, and all Teamcenter clients are all UNIX nodes provided by
one vendor (for example, Sun Microsystems).
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 NFS 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 NFS to other Teamcenter
clients to provide access to the database-specific information.

Heterogeneous network environment
In a heterogeneous environment, the database server, Teamcenter application server,

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

Site planning
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
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
If Oracle and Teamcenter applications or files are shared using NFS/CIFS,
you must standardize the user and group IDs of the Teamcenter and Oracle
accounts to give them the same access privileges on all systems.
Each user and group is identified by an alphanumeric name and an ID
number. The ID number is retained with the file information when a file
is exported across a network. If the ID numbers do not match for a user or
group, file access privileges may be unintentionally granted to the wrong user,
or not granted at all, on an NFS/CIFS client.

Part
II Database server installation
Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Chapter
3 Oracle installation and

configuration
Set shell limits and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Set AIX shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Set AIX system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Set AIX kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Set HP-UX kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Set Solaris kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Set SUSE Linux shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Upgrade Oracle server and databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Export Oracle databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Terminate Oracle sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Back up an Oracle installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Upgrading the Oracle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Upgrade using the Oracle installer . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Upgrade by uninstalling/reinstalling Oracle . . . . . . . . . . . . . . . . . . . 3-10
Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Configure Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Configure Oracle Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Configure an Oracle database for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Choose how to create the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Create a database using Teamcenter Environment Manager . . . . . . . . . . . 3-16
Create a database instance using Teamcenter templates . . . . . . . . . . . . . 3-17

Chapter
3 Oracle installation and

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

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

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

Oracle database for Teamcenter.

Chapter 3 Oracle installation and configuration
Set shell limits and parameters

Oracle 10g extensively uses UNIX resources such as shared memory, swap memory,
and semaphore for interprocess communication. Insufficient parameter settings
cause problems during installation and instance startup. The greater the amount of
data stored in memory, the faster a database operates. In addition, by maintaining
data in memory, the UNIX kernel reduces disk I/O activity.
On all UNIX and Linux platforms supported for Teamcenter 8, set the process
memory size (the ulimit user environment parameter) to unlimited before
installing Oracle.
To avoid errors during installation, or operation errors after installation, review
kernel parameter settings to ensure that they meet the recommended Oracle 10g
settings described in the following sections. The recommended kernel parameter
settings are for a typical Oracle 10g environment. If you previously tuned kernel
parameters to levels that meet other application needs, continue to use those values.
Initially, you can set kernel parameters as described in the Oracle documentation.
For some operating systems, kernel parameters may need adjustment according to
available system memory. The Oracle installation program issues warnings if kernel
parameters do not meet minimum requirements.
Note
The recommended values are minimum values. For production database
systems, Oracle recommends that you tune the values to optimize system
performance. For more information, see the operating system documentation.
Set AIX shell limits

1. Type the following command:
# smit chuser
2. In the User NAME box, type the user name of the Oracle software owner, for
example, oracle.
3. Scroll down the list and ensure that the values shown in table 3-1 are set to
the minimum values.
Caution
Do not change the shell limit values if they were set for another program
and the values are greater than the levels Oracle 10g requires.
4. Press F10 to exit.
Table 3-1. AIX minimum shell limits

Shell limit Minimum value
Soft FILE size –1 (unlimited)
Soft CPU time –1 (unlimited)
This is the default value.

Oracle installation and configuration
Table 3-1. AIX minimum shell limits

Shell limit Minimum value
Soft DATA segment –1 (unlimited)
Soft STACK size –1 (unlimited)
Set AIX system parameters

# smit chgsys
2. Ensure that the value shown for Maximum number of PROCESSES allowed
per user is greater than or equal to 2048.
Note
For production systems, this value should be at least 128 plus the sum
of the PROCESSES and PARALLEL_MAX_SERVERS initialization
parameters for each database running on the system.
3. Press F10 to exit.
Set AIX kernel parameters

Siemens PLM Software recommends setting kernel parameters to meet or exceed
the recommended Oracle 10g settings.
Set HP-UX kernel parameters

Set kernel parameters as described in table 3-2. Set parameters using the method
described in your HP-UX documentation.
Caution
Do not change the kernel parameter settings if the parameters were set
for another program and the values are greater than the levels Oracle 10g
requires.
Note
You can view kernel parameters using the kctune command.
Table 3-2. HP-UX minimum kernel parameter values for single database
instance
Minimum value
Kernel parameter or formula Purpose
executable_stack 0 Defines whether program stacks are
executable by default.

instance
Minimum value
ksi_alloc_max 33600 Defines the system-wide limit of queued
signals that can be allocated.
max_thread_proc 3000 Defines the maximum number of kernel
threads allowed per process. You may
need to increase the value if required by
your application. Setting it to a default
or low value may lead to an out of
memory error for certain applications.
maxdsiz 206385136 Defines the maximum data segment
size in bytes for 32-bit systems. Setting
this value too low may cause the
processes to run out of memory.
maxdsiz_64bit 4294967296 Defines the maximum data segment
size in bytes for 64-bit systems. Setting
this value too low may cause the
processes to run out of memory.
maxssiz 134217728 Defines the maximum stack segment
size in bytes for 32-bit systems.
maxssiz_64bit 1073741824 (1 GB) Defines the maximum stack segment
size in bytes for 64-bit systems.
maxswapchunks 16384 Defines the maximum number of swap
chunks where SWCHUNK is the swap
chunk size (1 KB blocks). SWCHUNK
is 2048 by default. It specifies the
maximum amount of configurable swap
space on the system.
Note
This parameter does not exist in
HP-UX 11.23 or later.
maxuprc ((nproc*9)/10) Defines the maximum number of user
processes.
msgmap (msgtql + 2) Defines the maximum number of
message map entries.
msgmni (nproc) Defines the number of message queue
identifiers.
msgseg 32767 Defines the number of segments
available for messages.
msgtql (nproc) Defines the number of message headers.
ncsize (ninode + 1024) Defines the directory name lookup
cache (DNLC) space needed for inodes.

instance
Minimum value
nfile 65536 Defines the maximum number of open
files. This parameter is managed
automatically by the system.
nflocks 4096 Defines the maximum number of file
locks available on the system. This
parameter is managed automatically
by the system.
ninode (8 * nproc + 2048) Defines the maximum number of open
inodes.
nkthread (((nproc * 7) / 4) + Defines the maximum number of kernel
16) threads supported by the system.
nproc 4200 Defines the maximum number of
processes.
semmap (semmni + 2) Defines the maximum number of
semaphore map entries.
Note
This parameter does not exist in
HP-UX 11.23 or later.
semmni 4200 Defines the maximum number of
semaphore sets in the entire system.
semmns (semmni * 2) Defines the maximum number of
semaphores in the system. The default
value of semmns is 128, which is, in
most cases, too low for Oracle software.
semmnu (nproc – 4) Defines the number of semaphore undo
structures.
semvmx 32767 Defines the maximum value of a
semaphore.
shmmax Physical memory Defines the maximum allowable size of
size one shared memory segment.
To avoid performance degradation, the
shmmax setting must be greater than
or equal to the size of the SGA.
shmmni 512 Defines the maximum number of
shared memory segments in the entire
system.
shmseg 512 Defines the maximum number of
shared memory segments one process
can attach.

instance
Minimum value
vps_ceiling 64 Defines the maximum system-selected
page size in kilobytes.
Set Solaris kernel parameters

On Solaris 10, set kernel parameters using the Solaris resource control facility. Set
resource controls as described in table 3-3.
On Solaris 9 or earlier, set kernel parameters to meet or exceed the recommended
Oracle 10g settings. Use the procedure provided in your Solaris documentation to
set kernel parameters.
Table 3-3. Solaris 10 minimum resource control values for single database
instance
Resource control Description
process.max-sem-ids Oracle recommends setting this resource control to
100, but the Solaris default value (128) is adequate,
so it is not necessary to change this setting.
project.max-shm-memory Defines the maximum shared memory (shm) for the
Oracle server. Oracle recommends a value of 4 GB,
but for Teamcenter servers, set this resource control
to a value greater than the total SGA + PGA memory
size of all instances on the system.
project.max-shm-ids Oracle recommends setting this resource control to
100, but the Solaris default value (200) is adequate,
so it is not necessary to change this setting.
Set parameters for the project user.oracle account (oracle) instead of the project
user.root recommended by Oracle documentation. To work with Solaris resource
control, use the following CLI command:
prtctl –n control—name –i project user.oracle
For example:
sun2:(root)# prctl -n project.max-sem-ids -i project user.oracle
project: 100: user.oracle
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-sem-ids
privileged 128 - deny -
system 16.8M max deny -
sun2:(root)# prctl -n project.max-shm-memory -i project user.oracle
project.max-shm-memory
privileged 3.92GB - deny -
system 16.0EB max deny -
sun2:(root)# prctl -n project.max-sem-ids -i project user.oracle


project.max-sem-ids
privileged 128 - deny -
system 16.8M max deny
Set SUSE Linux shell limits

1. Increase shell limits for the oracle user to the minimum values listed table 3-4
by adding the following lines to the etc/security/limits.conf file:
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
Caution
Do not change the shell limit values if they were set for another program
and the values are greater than the levels Oracle 10g requires.
2. Add or edit the following line in the etc/pam.d/logon file:

session required /lib/security/pam_limits.so
3. Change the oracle user default shell startup file:

• For the Bourne, Bash, or Korn shell, add the following lines to the
etc/profile.local file:
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
• For the C shell (csh or tcsh), add the following lines to the etc/csh.logon.local
file:
if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
endif
Table 3-4. SUSE Linux minimum shell limits

Item in Minimum hard
Shell limit limits.conf limit
Maximum number of open file descriptors nofile 65536
Maximum number of processes available to nproc 16384
a single user

Upgrade Oracle server and databases

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

1. Either log on to the Oracle server as oracle or switch the user to oracle:
su - oracle
2. Set the PATH environment variable to include the Oracle bin directory:
export PATH=$PATH:ORACLE_HOME/bin
3. Manually set the shared library path:

IBM AIX:
export LIBPATH=${LIBPATH}:${ORACLE_HOME}/lib
Hewlett-Packard HP-UX:
export SHLIB_PATH=${SHLIB_PATH}:${ORACLE_HOME}/lib
Sun Solaris:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib
SUSE Linux:
4. Export the contents of the Teamcenter Oracle database to the dump file:
ORACLE_HOME/bin/exp db-user/password full=y
file=file-name.dmp log=export.log
Replace db-user with the Teamcenter database user account name; replace
password with the database user account password; replace file-name with the
name of the dump file to contain the exported data; replace export with the name
of the log file to contain export output.
5. Store the dump file in a safe place.
Caution
Siemens PLM Software strongly recommends backing up the dump file on
tape or another disk. If the dump file becomes corrupted or lost, all data from
the existing database is lost.
Terminate Oracle sessions

Before installing Oracle, you must terminate all Oracle sessions and Oracle
processes.
1. Either log on to the Oracle server as oracle or switch the user to oracle as
follows:
su - oracle

2. Set the ORACLE_HOME environment variable to point to the location of the

Oracle files. For example:
export ORACLE_HOME=/u01/app/oracle/product/oracle-version
Replace the path with the system path to the Oracle files.
3. Define ORACLE_HOME/bin in the PATH variable:

export PATH=${PATH}:${ORACLE_HOME}/bin
4. Manually set the shared library path:

IBM AIX:
export LIBPATH=${LIBPATH}:${ORACLE_HOME}/lib
export SHLIB_PATH=${SHLIB_PATH}:${ORACLE_HOME}/lib
Sun Solaris:
SUSE Linux:
5. If a tnslsnr listener process is running, terminate it. For example:

$ORACLE_HOME/bin/lsnrctl stop listener-name
Replace listener-name with the name of the listener process.
6. Shut down all Oracle database instances using the dbshut utility. Shut down
database instances listed in the oratab file:
$ORACLE_HOME/bin/dbshut
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 oratab file in either the /var/opt/oracle directory (Sun Solaris systems) or
the /etc directory (all other platforms).
• The Oracle Net listener.ora and tnsnames.ora configuration filesin either

the /var/opt/oracle directory (Sun Solaris system) or the /etc directory (all
other platforms).

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

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

and importing existing databases from a dump file
Upgrade using the Oracle installer

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

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

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

You can install Oracle from the Oracle software distribution images supplied by
Siemens PLM Software or Oracle Corporation.
If you install Oracle from a hard disk, copy the entire contents of the Oracle CD-ROM
directory to the hard disk.
You can install Oracle application files on NFS file systems. However, Oracle
Corporation does not support Oracle database files on an NFS-mounted file system.
To ensure data integrity, create database files on local disk drives.
If you install Oracle from an NFS-mounted directory from a remote NFS server, you
must execute the installation program on the local server node.

Caution
• Do not run Oracle Universal Installer as the root user.
• Oracle Universal Installer automatically installs the Oracle-supplied

version of Java Runtime Environment (JRE). This version is required
to run Oracle Universal Installer and several Oracle assistants. Do not
modify the JRE except by using a patch provided by Oracle Support
Services.
1. Log on to the server host as the oracle user.
2. Record the name of the Oracle database server host. Teamcenter Environment
Manager requires this name during corporate server installation.
3. If Oracle was previously installed on the host, search for the following Oracle
Net configuration files in the etc and var/opt/oracle directories and either
remove them or relocate them to the corresponding network/admin directory
in the Oracle home directory:
listener.ora
tnsnames.ora
sqlnet.ora
This step is required for compliance with the standard of storing Oracle Net
configuration files in the network/admin directory.
4. Insert the Oracle 10.1.0.2 component CD-ROM and mount it if required:

IBM AIX:
/usr/sbin/mount -rv cdrfs device–name /cdrom
Replace device-name with the name of the CD-ROM device, for example,
dev/cd0; replace /cdrom with the CD-ROM mount-point directory.
/usr/sbin/mount -F cdfs -o rr device–name /cdrom
Note
Replace device-name with the name of the CD-ROM device, for example,
dev/dsk/c0t0d0; replace cdrom with the CD-ROM mount-point directory.
Sun Solaris:
/usr/sbin/mount -r -F hsfs device–name /cdrom
Note
Use the preceding command if Solaris does not mount the CD-ROM
automatically. Replace device-name with the name of the CD-ROM device,
for example, dev/dsk/c0t6d0s2; replace /cdrom with the CD-ROM mount
point directory.
SUSE Linux:
mount -t iso9660 device–name mount-directory

Note
Use the preceding command if SUSE Linux does not mount the CD-ROM
automatically. Replace device-name with the name of the CD-ROM device,
for example, dev/cdrom; replace mount-directory with the CD-ROM
mount-point directory, for example, media/cdrom.
5. On IBM AIX only, run the rootpre.sh script as root user in a shell window.
Copy the rootpre directory from the CD-ROM to a directory on a local hard disk
and run rootpre.sh from disk. Enter the following commands:
cp –r /CDROM/rootpre /tmp
cd /tmp/rootpre
chmod 755 *
./rootpre.sh
Replace CDROM with your CD-ROM mount point.

The rootpre.sh script configures the AIX Asynchronous I/O and Oracle
Post-Wait Kernel Extension.
Note
• If you do not perform this step, Oracle or Teamcenter programs can
fail with unresolved symbols.
• For more information about this issue, see SFB-TC_Engineering-1111

available on the Siemens PLM Software GTAC Web site:
http://support.ugs.com
This SFB is applies only to previous releases of Oracle.
6. If the /tmp directory does not have at least 400 MB of free space, set the TEMP
and TMPDIR environment variables to a directory that meets this requirement:
$ export TEMP=directory-path
$ export TMPDIR=directory-path
Replace directory-path with the path to the directory with sufficient space, for
example, disk/tmp
7. Start Oracle Universal Installer from the CD-ROM mount-point directory as

the oracle user:
$ umask 022
$ unset TNS_ADMIN
$ unset ORACLE_HOME
$ export ORACLE_BASE=/disk1/oracle
$ cd $HOME
$ /mount-directory/runInstaller
Replace mount-directory with the CD-ROM mount-point directory. This example

sets the ORACLE_BASE variable to the top level of the Oracle installation.
8. In the Welcome window, click Next.
9. If Oracle Universal Installer displays the Specify Inventory Directory and

Credentials window, enter the directory where you want to install inventory files

and the operating system group name for the group that owns the inventory
directory; click Next.
Note
Siemens PLM Software recommends:
• Use the default directory (oraInventory) in the Oracle base directory.
• Use the default of the group the oracle account belongs to (dba).
10. If Oracle Universal Installer prompts you to run the orainstRoot.sh script, run
it in a separate terminal window as the root user and then click Continue:
$ORACLE_BASE/oraInventory/orainstRoot.sh
11. In the Select Installation Type dialog box, select Enterprise Edition and click
Next.
12. In the Specify Home Details dialog box, enter the directory path in which to
install the Oracle products in the Destination box and click Next.
Note
Do not install Oracle 10g software into an existing Oracle home that
contains Oracle 9i or earlier software.
13. In the Product-Specific Prerequisite Checks dialog box, verify that all the
prerequisite checks succeeded and click Next.
Note
If a check fails, review the displayed cause of the failure for that check,
correct the problem, and rerun the check.
A check occasionally fails erroneously, for example, when you install a
later patch that obsoletes a listed patch. When you are satisfied that
the system meets a requirement, manually verify the requirement by
selecting the checkbox for the failed check.
14. In the Select Configuration Option dialog box, select Install database software
only and click Next.
15. In the Summary dialog box, review the information to ensure you have sufficient
disk space and click Install.
Oracle Universal Installer displays a progress meter that adjusts at the
completion of each installation and relinking phase.
If you are installing from CD-ROM, Oracle Universal Installer prompts you
to insert subsequent CD-ROMs when they are required. If you encounter
errors, see the Oracle Database Installation Guide for UNIX Systems for
troubleshooting information.
When Oracle Universal Installer completes installing Oracle products, it creates
the root.sh script in the Oracle home directory and prompts you to run the script.
16. Log on as the root user and run the root.sh script in the Oracle home directory.

The root.sh script sets the necessary file permissions for Oracle products and
performs other related root-related configuration activities.
17. After the root.sh script completes successfully, click OK in the Oracle Universal
Installer Setup Privileges dialog box.
Configuring Oracle software

Configure Oracle server processes and Oracle Net.
Configure Oracle server

1. In the window in which you started Oracle Universal Installer, start Oracle
Net Manager:
export ORACLE_HOME=/disk1/oracle/OraHome_1
$ORACLE_HOME/bin/netmgr
2. Create the listener.ora file:
a. Expand the Local icon.
b. Select the Listeners folder and choose Edit→Create.
c. Accept the default listener name (LISTENER).
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 on which 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:

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:

File→Exit
4. In the same window in which you started Oracle Net Manager, start the listener
service:
$ORACLE_HOME/bin/lsnrctl start LISTENER
Configure Oracle Net

Teamcenter uses Oracle Net protocols to communicate with an Oracle database.
These protocols require that a listener process (tnslsnr) run on the Oracle server
to listen for remote connect requests and that all clients can translate the service
alias identifying the server and database.
If your site uses Oracle Net Assistant for other databases, Siemens PLM Software
recommends that you copy the listener.ora and tnsnames.ora files containing
entries for your designated Teamcenter database and install these copies on the
Oracle server. Reload or restart the listener process so that it listens for connect
requests to the new database.
Teamcenter Environment Manager copies the tnsnames.ora file and stores it
in the Teamcenter data directory. Teamcenter uses the Oracle TNS_ADMIN
environment variable to locate the tnsnames.ora file. However, if the system
uses the TNS_ADMIN variable to locate configuration files created by Oracle Net
Assistant, this setting overrides Teamcenter settings. In this case, you must use
Oracle Net Assistant to add entries for Teamcenter databases to existing Oracle
Net configuration files.
For more information, see the System Administration Guide.
Configure an Oracle database for Teamcenter

Create and configure databases for Teamcenter.

Choose how to create the database

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

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

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

Note
Teamcenter Environment Manager (TEM) verifies your Oracle version during
installation. If your Oracle server does not meet the minimum required
version, TEM does not allow installation to proceed. For information about
supported database servers for Teamcenter 8, see the Siemens PLM Software
certification database:
1. Create a multipurpose database using Oracle DBCA. For information, see the
Oracle documentation.
Tip
Record the following information that you must provide when installing
the Teamcenter corporate server:
• Password of the database system user
DBCA creates the system user with a password of manager. You
can change the password.
• Absolute path to the tablespace directory on the database server host.

This is the path on the Oracle server where data files are stored.

2. Install a Teamcenter corporate server using Teamcenter Environment Manager

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

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

Note
Make sure you have access to the Teamcenter software distribution image.
1. Log on to the Oracle server host as the oracle user.
2. Copy the Siemens PLM Software-supplied Oracle 10g 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:
cp /cdrom/tc/db_scripts/oracle/* ORACLE_HOME/assistants/dbca/templates
3. Open a shell window and set the ORACLE_BASE environment variable. For
example:
export ORACLE_BASE=/disk1/oracle
Note
By default, Oracle creates database files in the oradata directory in
the directory pointed to by the ORACLE_BASE environment variable.
Before running Oracle Database Configuration Assistant (DBCA), you can
set the ORACLE_BASE environment variable to the directory where
you want database files to reside.
4. Start Oracle Database Configuration Assistant (DBCA):

ORACLE_HOME/bin/dbca
5. In the Welcome dialog box, click Next.
6. In the Operations dialog box, select Create a database and click Next.
7. In the Database Templates dialog box, select Teamcenter Oracle 10g 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.
9. In the Management Options dialog box, 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 Storage Options dialog box, select File System and click Next.
12. In the Database File Locations dialog box, select Use Database File Locations
from Template and click Next.
13. In the Recovery Configuration dialog box, select Specify Flash Recovery Area
and click Next.
14. In the Database Content dialog box, click Next.
15. In the Initialization Parameters dialog box, click Next.
16. In the Database Storage dialog box, click Next.
17. In the Create Options dialog box, select Create Database and click Finish.
18. In the Confirmation dialog box, click OK to start creating the database.
When the database is created, DBCA displays a window containing information
about the created database.
19. Click Exit.
After the database is created, check for possible errors in the installation log files.
The log files are in the admin/SID/create directory in the Oracle base directory
or, if you did not define the ORACLE_BASE environment variable, in the Oracle
home directory.

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.
• The first time Oracle Universal Installer runs, it creates the

ORACLE_BASE/oraInventory/logs directory, containing an inventory of
installed components and performed actions. The most recent log file is
named installActions.log. Names of previous installation sessions are in
the form installActionsdate-time.log. For example:
installActions2008-07-14_09-00-56-am.log
You can also view a list of installed components by choosing Installed

Products on any Oracle Universal Installer window. Do not delete or
manually alter the Inventory directory or its contents. Doing so can
prevent Oracle Universal Installer from locating products you installed
on the system.

Part
III Teamcenter server installation
Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Chapter
4 Teamcenter preinstallation tasks
Install the licensing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Select destination directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Verify required character set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Ensure correct mode on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Install a volume server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Install NX and Teamcenter Integration for NX or NX Integration . . . . . . . . . . 4-5
Best installation practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Chapter
4 Teamcenter preinstallation tasks
Perform the appropriate procedures to prepare your Teamcenter server host.
Install the licensing server

Before you install Teamcenter, you must install the Siemens PLM Software Common
Licensing Server to distribute licenses to Teamcenter hosts.
Teamcenter employs named user licensing, which ties each user in the system to an
available license and ensures the total number of active authors and consumers in
the system is always less than or equal to the number of author/consumer licenses
purchased.
There are two levels of Teamcenter user licenses, corresponding to different roles
within an organization:
• author is a user that creates or modifies data for product and process
information.
• consumer is a user that views, approves, rejects, or comments on product and

process information.
Install the ugslmd license daemon:

1. Obtain a Teamcenter 8 license file from Siemens PLM Software. Save the
license file in a directory accessible to the license server host. This procedure
assumes the license file is named tc.lic, but you may give the license file any
name you choose.
2. Open the license file in a plain text editor and locate the following line in the file:
SERVER YourHostname ANY 28000
3. Replace YourHostname with the host name of the designated license server
host. Update your Siemens PLM Software customer service representative with
your license server host information.

Chapter 4 Teamcenter preinstallation tasks
Note
• Siemens PLM Software recommends you do not change the license
server port from its default value (280001) unless it is necessary to
resolve a port conflict.
• Keep note of the host name and port for the license server. Teamcenter
Environment Manager (TEM) prompts you for these values during
Teamcenter server installation.
4. Save the changes to the license file.
5. Set the UGS_LICENSE_SERVER environment variable to the following value:

port@host
Replace port with the port number and host with the host name of the license
server, for example, 28000@tchost. The port and host values must match those
you specified in the SERVER line of the Teamcenter license file.
6. Extract the Siemens PLM Software Common License Server software:

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

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

program:
a. Change to the directory in which you extracted the ugslicensing.zip
archive.
b. Open the ugslicensing_install.ans file and edit the contents to specify the
destination directory and path to the Teamcenter license file.
c. Execute the ugslicensing_install command.
Caution
The Siemens PLM Software Common License Server must be running
and two or more seats must be available on that license server during
Teamcenter server installation. Otherwise, database creation fails because
the make_user utility cannot create the required users in the database.
For more information, see the Installing UGS Licensing for UNIX, Installing
UGS Licensing for Windows, and UGS Licensing User Guide documents in the
additional_documentation directory on the Teamcenter 8 documentation
distribution image.
1. Port 28000 is registered for the Common Licensing Server with the Internet Assigned Numbers Authority (IANA). For more
information, see http://www.iana.org/assignments/port-numbers.

Teamcenter preinstallation tasks
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.
• Install NX FLEXlm files on local drives to ensure that NX FLEXlm services are
started when the system is restarted.
You can install NX FLEXlm files independently of the Teamcenter application
root directory hierarchy using Teamcenter Environment Manager.
• Install Teamcenter on a local disk to configure Teamcenter File Services, File

Management System file caches, and/or Multi-Site Collaboration services
• You can select automounted NFS directories, but you must supply the automount
link name for the Teamcenter application root directory. Do not supply the
automounted directory (for example, /tmp/mnt/node-name).
Verify required character set

Teamcenter installation tools require the ISO8859-1 character set. To verify that
this character set is loaded, run the locale –a command in a shell. If the output does
not list ISO8859-1, you must add this character set before you install Teamcenter.
1. Set or export the LC_ALL environment variable by typing
LC_ALL=en_US.ISO8859-1 or the equivalent command for your platform.
2. Verify the setting using the echo command or equivalent. Make sure the correct
value for LC_ALL is displayed.
3. Run the locale command and make sure the LANG variable and all the LC_x
variables are set the same as LC_ALL.
4. If LANG is still set to C, manually export LANG to be the same value as LC_ALL.
5. Launch Teamcenter Environment Manager (tem.sh) from the current shell.
Alternatively, your system administrator may modify the date file (named
TIMEZONE in the etc directory), which can preset this environment, so every time
you log on and launch a shell, the environment is preset.
The recommended method, however, is to log on to the system using the Common
Desktop Environment (CDE) with the minimum required locale (ISO8859-1) by
choosing Option→Language→en_US.ISO8859-1 during logon.
If the ISO8859-1 character set is not loaded on your machine, contact your system
administrator to have it installed before you install the GM Overlay.
This requirement is due to changes in the installation process for Teamcenter 8,
which uses XML files rather than .dat files and associated scripts. Because of this,
GM Overlay data is transformed from .dat files into XML files.
To read and parse the XML files correctly, the system must be able to process
non-English (non-ASCII) locale characters. To facilitate this, the system must be
first loaded with the fonts for that locale.

Note
Ensure the ISO8859-1 character set is loaded before you add any Teamcenter
features to your configuration that contains the GM Overlay. If the ISO8859-1
character set is not loaded, lists of values (LOVs) for GM Overlay are
corrupted during feature installation. Upgrade of the GM Overlay feature
fails if the ISO8859-1 character set is not loaded.
Ensure correct mode on Linux

Before installing Teamcenter on the Linux operating system, ensure that the system
is operating in the ISO8559-1 mode, rather than the default UTF-8 mode.
Install a volume server

When you install Teamcenter File Services (TCFS), TEM assigns ownership of the
TCFS service to the operating system user who installed TCFS and automatically
grants logon rights to this user. This ownership cannot be changed after installation.
By default, you can create volumes only on local disks. If the Teamcenter server is
to write files to volumes residing on remote disks (shared across the network), the
TCFS service must be run by a user with access rights across the network. Usually
this is a domain user account (a user name of the form domain-name\user-name).
If you want the TCFS service and volume to be owned by a separate user from the
Teamcenter corporate server, you must install TCFS first, before you begin your
corporate server installation.
1. Log on to the operating system with the user account you want to own the TCFS
volume.
2. Start Teamcenter Environment Manager (TEM):

a. Change to the root directory of the Teamcenter software distribution image.
b. Run the tem.sh script.

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

The language you select is used only for the installation program.
Teamcenter Environment Manager displays the Getting Started panel.
3. Select Create a new installation of the product and click Next.
4. Proceed to the New Configuration panel.
5. Enter a unique ID and description for the new Teamcenter configuration.
6. Proceed to the Solutions panel. Select the Volume Server solution.

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

In the Name box, type the name under which the TCFS process runs. In the Port
box, type the port the TCFS process uses.
Note
The TCFS port number must be unique among the services defined in the
services file, and must be the same on every node that accesses the same
version of NX FLEXlm, Teamcenter File Services, and the database 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 FSC Service panel. Enter required values for the FMS server
cache (FSC) service. For information about required values, click Help.
12. Proceed through the remaining panels, entering required values for the volume
server. For information about these panels, click Help.
13. Proceed to the Confirm Selections 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.
After you install your volume server, you can log on to the operating system using the
account under which you want to install your Teamcenter corporate server. When
you install your Teamcenter corporate server as described in Install a Teamcenter
corporate server, clear (do not install) the Teamcenter File Services feature. When
TEM prompts your for the name and port number of the TCFS service, enter the
values you entered when you installed your volume server.
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.
When installing NX, allow the installation to modify system files so that it can create
an installed_programs.dat file under the ugs directory. You can use this installed
installed_programs.dat file as a sample for use on other UNIX workstations of the
same type to access NX using Teamcenter Integration for NX or NX Integration from
a local server environment. NX can be installed on a mount point.
Teamcenter Integration for NX and NX Integration provide the same NX user
interface and are both installed with NX. For information, 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.
Best installation practices

A Teamcenter network requires one corporate server configuration. Additional
servers are optional, but can help balance network loads and facilitate heterogeneous
networks (networks with hosts running different operating systems).
If you install the optional servers, Siemens PLM Software recommends installing
in the following order:
1. Perform a full installation of Teamcenter on a corporate server host.

The corporate server is a network node used as an application file server (from
the Teamcenter application root directory) and database-specific configuration
file server (from the Teamcenter data directory). Run Teamcenter Environment
Manager and install the Teamcenter executables and the directory containing
the database-specific configuration files. Teamcenter can also run locally on
this network node.
2. Optionally install additional Teamcenter servers to provide the following

capabilities:
• Run Teamcenter executables and point to the existing data directory on

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

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

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

Chapter
5 Teamcenter server installation
Teamcenter Environment Manager (TEM) installs the Teamcenter shared

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

• Locate the Teamcenter software distribution image for your platform. If
you install Teamcenter online help, locate the Teamcenter documentation
distribution image.1
• On the local host, create the Teamcenter operating system user account.
Note
All Teamcenter services run as this user account.
• 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:
– The type of database server used for this installation of Teamcenter.
– 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:

o Name of the database
o Name of a system data source (DSN) to be created by Teamcenter

Environment Manager
1. The Teamcenter documentation distribution image contains the tchelp.jar file needed by the online help feature.

Chapter 5 Teamcenter server installation
◊ Whether you can create a database user or must use an existing

database user:
o 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.
o If you must use an existing database user:

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

This parent directory must exist before installation. Only the parent directory
should exist; the volume directory is created during installation.
Note
Siemens PLM Software recommends not defining the volume location
under the Teamcenter application root directory. Doing so leads to
complications when upgrading to a new version of Teamcenter.
• Determine the user for running the Teamcenter File Services (TCFS) service,
either a user with a local system account or a user with network access. If the
Teamcenter data directory, Teamcenter application root directory, or volume
directory is on a network share, you must specify a user that has network access.
• Select the features to install. Point to any feature to view a description.2
• Obtain the information required to install File Management System (table 5-1).
Note
• If you install File Management System, the FMS server cache (FSC) and
the server manager must run on the same host server, with the same
user ID.
• Teamcenter provides server managers based on the J2EE and the

Microsoft .NET platforms. The .NET Web tier is supported only on
Windows platforms.
2. For further descriptions of server features, see Teamcenter features.

Teamcenter server installation
Table 5-1. Required File Management System information

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

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


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

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

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

cache used by the embedded viewer and the stand-alone
application viewer on rich client hosts.
This default setting can be overridden by the FMS client
cache configuration file.
– 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.
– If rich client users in the network deploy Lifecycle

Visualization, Siemens PLM Software recommends


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

1. Log on to the operating system with the Teamcenter user account you created for
installing and maintaining the Teamcenter installation.
2. Start Teamcenter Environment Manager (TEM):

a. Change to the root directory of the Teamcenter software distribution image.

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

The language you select is used only for the installation program.
Teamcenter Environment Manager displays the Getting Started panel.
3. Select Create a new installation of the product and click Next.
4. Proceed to the New Configuration panel.
5. Enter a unique ID and description for the new Teamcenter configuration.

Note
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.
6. Proceed to the Solutions panel. Select the Corporate Server solution.

Note
For descriptions of solutions, point to the solution in the list or click Help
or see Solutions and features reference.
7. Proceed to the Select Features panel. This panel shows four corporate server
features preselected by the Corporate Server solution:
Teamcenter Foundation

FMS Server Cache

NX Integration
8. If you are deploying the J2EE Web tier, select the J2EE Based Server Manager
feature.
9. Select any additional features you want to include in your configuration. For
descriptions of features, point to the feature in the list or click Help or see
Solutions and features reference.
Note
• You can add features to the corporate server configuration during
installation or you can add them later using TEM in maintenance
mode.
• If you want to install a custom solution, see Install a template using

TEM.
• If you install Teamcenter Automotive Edition and GM Overlay, make

sure you install the GM Overlay for Rich Client feature on two-tier
rich client hosts, and complete the required postinstallation steps.
For more information about installing the GM Overlay for Rich
Client feature, see the Installation on Windows Clients Guide and the
Installation on UNIX, Linux, and Macintosh Clients Guide.
10. In the Installation Directory box, enter the absolute path to the directory where
you want to install Teamcenter.
Note
• You must install Teamcenter in a new directory. If you want to
upgrade an existing installation, return to the Getting Started panel
and select an upgrade installation. For information about upgrading,
see the Upgrade Guide.
• The Installation Directory value is the Teamcenter application root

directory stored in by the TC_ROOT environment variable.
Do not set TC_ROOT in the system environment. TEM sets this
variable as required in various scripts. Setting this variable in the
operating system can cause conflicts if you install more than one
configuration.
11. Proceed to the TCFS Service panel.

In the Name box, type the name under which the TCFS process runs. In the Port
box, type the port the TCFS process uses.
Note
The TCFS port number must be unique among the services defined in the
services file, and must be the same on every node that accesses the same
version of NX FLEXlm, Teamcenter File Services, and the database server.

12. Proceed to the Operating System User panel. Type the password for the
operating system account to which you logged on to install Teamcenter.
13. Proceed to the Configure TC_DATA panel. Choose whether to create a new
data directory or connect to an existing one, and then enter the location of the
data directory.
This Data Directory Location value is referenced as the Teamcenter data
directory or the TC_DATA directory. This value is stored in the TC_DATA
environment variable. Each data directory is associated with a single database
user within a database instance.
Note
Do not set TC_DATA in the system environment. TEM sets this variable
as required in various scripts. Setting this variable in the operating
system can cause conflicts if you install more than one configuration.
14. Proceed to the Database Engine Selection panel.

Enter the database server information.
You can either connect to an existing database user or create a database user.
Enter the database user and password, and then click Next.
• If the database user exists, TEM connects to the database.
• If the database user does not exist, TEM asks whether you want to create
the database user:
a. Click Create. TEM displays the Create Oracle Database panel.
b. Enter the required values to create the database user, and then click
Next.
Note
• For detailed descriptions of the values on this panel, click the Help
button.
• 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.3
• Teamcenter servers and two-tier rich clients on UNIX or Linux hosts

cannot connect to Microsoft SQL Server database servers. Keep this
in mind if your network contains Windows and UNIX or Linux hosts.
15. Proceed to the Volume Specification panel.

In the Volume Name box, type a name for the Teamcenter volume you want
TEM to create.
3. For information about supported database servers for Teamcenter 8, see the Siemens PLM Software certification database
(http://support.ugs.com/online_library/certification/).

Specify whether to create a local volume, and then enter volume location
information. In the Volume Location box, type the absolute path to the directory
for the volume, ensuring that the parent directory exists.
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.
16. Proceed to the Transient Volume Settings panel.

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.
Specify a transient volume location for Windows hosts, UNIX hosts, or both.
Note
For more information about transient volumes, see the System
Administration Guide.
17. Proceed through the remaining panels, entering the required information for the
features you selected. For information about these panels, click Help.
18. When you complete entering information for optional features, TEM displays the
Database Template Summary panel, which lists templates to be applied when
TEM populates the database during installation. This panel is for information
only. Click Next to accept and continue.
19. Proceed to the Confirm Selections 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 Teamcenter corporate
server.
Note
• If you chose the Online Help feature, TEM prompts for the location of
the online help files during installation. Enter the path to the location
of tchelp.jar file on the Teamcenter documentation distribution
image.
• If an error occurs during installation, follow the instructions in the

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

Chapter
6 Teamcenter postinstallation tasks
Run the postinstallation tasks program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Modifying the services file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Start Teamcenter database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Prepare the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . 6-2
Configure Multi-Site Collaboration daemons . . . . . . . . . . . . . . . . . . . . . . 6-4
Back up new installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Terminate Teamcenter sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Back up existing Teamcenter data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Back up Teamcenter databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Chapter
6 Teamcenter postinstallation tasks
Perform the appropriate procedures to complete installation of Teamcenter features.
Run the postinstallation tasks program

If you installed the corporate server without root privileges, a user with root
privileges must run the root_post_install_tasks.sh program in the install
directory in the Teamcenter application installation directory.
Modifying the services file

When you configure Teamcenter File Services, and have root privileges, Teamcenter
Environment Manager adds the following services information to the etc/services
file:
tcfs port-no./tcp # Siemens PLM Software Teamcenter services
This is the port on which the tcfs service runs.

Teamcenter Environment Manager prompts you to enter the port number. The
TCFS service name and port number must the same for each database using the
service. Teamcenter Environment Manager allows you to set up customized TCFS
services for each configuration. The service name and port number must be unique
for each configuration.
Systems that use Network Information Services (Yellow Pages) or NIS Plus obtain
services information indirectly from the etc/services file on the NIS master
node.Teamcenter Environment Manager can add these services only to the NIS
master, not the client. You must update this file in one of the following ways:
• Run Teamcenter Environment Manager on the NIS master.
• Manually add these entries to the NIS master etc/services file and propagate
the changes to all NIS clients before installing any clients.
Start Teamcenter database daemons

You can start Teamcenter database daemons manually by executing the following
startup files:
Database daemon Daemon startup script name

Action manager rc.ugs.actionmgrd

Chapter 6 Teamcenter postinstallation tasks
Database daemon Daemon startup script name

Subscription manager rc.ugs.subscriptionmgrd
Task monitor rc.ugs.task_monitor
The installation program creates these startup files in different directories

depending upon the operating system. For all systems except AIX, the script resides
in the column labelled Script Location. There is a corresponding symbolic link
located in the Startup Directory column. The symbolic links also have different
S prefix numbers depending on the operating system.
For AIX systems, the startup directory is /etc, and one file (rc.ugs) calls all the
daemon startup scripts if they are installed and have execute permissions set.
The following table list the locations of the startup scripts.
Operating system Script location Startup directory

IBM AIX /etc Not applicable; see rc.ugs
file
Hewlett-Packard HP-UX /sbin/init.d /sbin/rc3.d/S905script-name
Sun Solaris /etc/init.d /etc/rc2.d/S95script-name
Configure Multi-Site Collaboration

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

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

This database stores records about the data objects published by other databases
in the Multi-Site Collaboration environment (that is, made public to the other
databases).
This can be one of the databases identified in step 1 or it can be a dedicated
database. The database must be populated with Teamcenter data.

Teamcenter postinstallation tasks
3. For each database identified in step 2, identify a network node local to that
database to act as the ODS server.
The ods daemon 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
daemon 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. For more information, see Organization Guide.
6. Using the information obtained in steps 2 through 5, populate each database site
table with information about the other sites using the Organization application
in the Teamcenter rich client.
The node for each site is the name of the network node to run the necessary
Multi-Site Collaboration daemons (idsm and/or ods). If the site is an ODS
database, check the ODS site flag. To publish objects from the ODS database,
define the site of the ODS database in the site table and configure the ODS
server as an IDSM server.
7. For each database identified in step 1 and step 2, edit the site preference for
the database and modify the following preferences to reflect the Multi-Site
Collaboration environment:
ODS_permitted_sites (ODS database only)
ODS_site (Non-ODS databases)
ODS_searchable_sites
ODS_searchable_sites_excluded
IDSM_permitted_sites
IDSM_permitted_users_from_site_site-name
IDSM_permitted_transfer_sites
IDSM_permitted_transfer_users_from_site_site-name
IDSM_permitted_checkout_sites
IDSM_permitted_checkout_users_from_site_site-name
Fms_BootStrap_Urls
TC_publishable_classes
TC_transfer_area
For more information about these preferences, see the Teamcenter Preferences
and Environment Variables Reference.
8. For each database identified in step 1 and step 2, copy all POM transmit schema
files for that database into the POM transmit schema directories for each of the
other databases.

Chapter 6 Teamcenter postinstallation tasks
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
installation program on that node to configure and start the Multi-Site
Collaboration daemons.
Configure Multi-Site Collaboration daemons

Configure the Multi-Site Collaboration daemons:
1. As a user with root privileges, run the root_post_install_tasks.sh program in
the install directory in the Teamcenter application root directory.
2. At the command line, execute the following command:

execute ps -ef | grep -v grep | grep inetd
This script obtains the current process ID of the inetd daemon.
3. At the command line, execute the following command:

kill -HUP process-id
Replace process-id with the inetd daemon ID obtained in step 5-2.
This procedure adds the idsm daemon entry to the inetd.conf file and forces the
inetd daemon to reload its configuration. As a result, the Multi-Site Collaboration
daemons are launched to complete the installation.
Back up new installations

Siemens PLM Software strongly recommends backing up new Teamcenter and
Oracle installations before using them.
1. Terminate Teamcenter sessions.
For information, see Terminate Teamcenter sessions.
2. Back up existing Teamcenter data.

For information, see Back up existing Teamcenter data.
3. Export existing Oracle databases.

For information, see Export Oracle databases.
4. Terminate Teamcenter-Oracle sessions.

For information, see Terminate Oracle sessions.
5. Back up the Oracle installation.

For information, see Back up an Oracle installation.

Teamcenter postinstallation tasks
Terminate Teamcenter sessions

1. Instruct all users to close and log off of Teamcenter sessions, including tcserver
processes.
2. Set Teamcenter environment variables by entering the following commands:

TC_ROOT=/usr/Siemens/Teamcenter8; export TC_ROOT
TC_DATA=/usr/Siemens/Teamcenter8/teamcenterdata; export TC_DATA
. $TC_DATA/tc_profilevars
This example assumes that Teamcenter is installed under the

usr/Siemens/Teamcenter8 directory.
Sourcing the iman_cshvars file creates a csh subshell in which Teamcenter
environment variables are set.
3. Use the clearlocks utility to check for nodes connected to the database:
$TC_ROOT/bin/clearlocks -node_names
4. Note the node names returned, and then type the following command for each
node name returned:
$TC_ROOT/bin/clearlocks -assert_dead node-name
Replace node-name with a returned node name.
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.
Back up Teamcenter databases

Back up your Oracle server and databases:
1. Export existing Oracle databases.
For information, see Export Oracle databases.
2. Terminate Teamcenter-Oracle sessions.

For information, see Terminate Oracle sessions.
3. Back up the Oracle installation.

For information, see Back up an Oracle installation.

Part
IV Adding features
Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Install the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Installing a custom solution or third-party template . . . . . . . . . . . . . . . . . . . 9-1
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Installing Teamcenter’s reporting and analytics . . . . . . . . . . . . . . . . . . . . . . . 11-1

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

Start the J2EE-based server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Chapter
7 Installing the server manager
If you install the J2EE-based Web tier, install the J2EE-based server manager.
Gather required information

The following table describes information required to configure the server manager.
Table 7-1. Required server manager information

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. The value entered in this
box is written to 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.jboss.org/jgroups.

Chapter 7 Installing the server 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.

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 Target number of server processes to be available in this pool
processes or subpool during specified times.
You specify these values as time and integer pairs separated
by commas. For example:
0700 3, 1700 2
This value sets the target number of server processes as 3
between 7 a.m. and 5 p.m. and as 2 between 5 p.m. and 7 a.m.
• If the number of server processes is below the specified
target, warm servers are added to reach this number.
In this case, the number of warm servers exceeds the
minimum.
• If the number of server processes exceeds the specified

target, only the minimum number of warm servers is
maintained and servers are terminated as they time out.
Number of logons Number of logons the server manager allows per minute for
this pool or subpool. The default value, 0, allows unlimited
logons per minute.
CPU load Whether you want the server manager to control server
processes based on the CPU load of the local host.
This option is relevant only for Sun Solaris systems.
Note
For server pool sizing recommendations, see the Web Tier Deployment Guide
available on GTAC.

Install the J2EE server manager

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

update, entering configuration values as needed2 until you reach the Server
Manager for J2EE panel.
Note
For information about fields in TEM panels, click the Help buttons in
each panel.
4. In the Pool ID and JMX HTTP Adaptor Port boxes, type a name and port for the
server pool.
Enter the remaining values in the panel as described in Gather required
information.
5. Click Next.
TEM displays the Server Manager for J2EE Performance Tuning panel.
6. Enter values for the following required parameters:
Parameter Description
Max Servers in Sub-Pool 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 in Sub-Pool
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.
2. For information about installing a Teamcenter corporate server, see Install a Teamcenter corporate server.

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

are optional. Type values for these parameters as needed.
7. Proceed through remaining panels until you reach the Confirm Selections
panel. Click Next to begin installing the Teamcenter server with the J2EE-based
server manager.
8. When installation completes, exit TEM.
Start the server manager

If you install the J2EE based Server Manager feature, you must start the server
manager to enable four-tier rich clients to connect to the corporate server.
Start the J2EE-based server manager

1. Open a command prompt.
2. Change to the TC_ROOT/pool_manager directory.
3. Type the following command to start the server manager:

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

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

4. Launch the server manager user interface from

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

Chapter
8 Install the Business Modeler IDE
Install the Business Modeler IDE as a stand-alone application . . . . . . . . . . . . 8-1
Install the Business Modeler IDE to an existing Eclipse environment . . . . . . . 8-3
Allocate memory to the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . 8-5
Start the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Chapter
8 Install the Business Modeler IDE
To install the Business Modeler IDE, you must install it as a stand-alone application.
If you already have Eclipse installed, install it into your Eclipse environment. After
you install the Business Modeler IDE, allocate additional memory so that Business
Modeler IDE has enough memory to run.
Install the Business Modeler IDE as a stand-alone application

1. Start Teamcenter Environment Manager (TEM).
2. Proceed to the Solutions panel. In the Solutions panel, select Business Modeler
IDE, and then click Next.
3. Perform the following steps in the Select Features panel:

a. Under Business Modeler IDE, select the following:
• Business Modeler Templates
Installs templates for different Teamcenter solutions. These templates
are only used within the Business Modeler IDE to extend the Teamcenter
data model.
• Client
Installs the IDE as a client on your machine.
• Mapping Designer (optional)

Installs the Mapping Designer data model mapping tool into the
Business Modeler IDE.
• Digital Dashboard (optional)

Installs the Digital Dashboard application into the Business Modeler
IDE. The Digital Dashboard is used by system administrators to examine
log files.
• Configure Teamcenter Servers

Select these options to automatically create a server connection profile
for deployment of data model changes to a server:
– 2 Tier Teamcenter Server Configuration
Select this option if you want to connect to a server in a two-tier
environment over a network using IIOP protocol.

Chapter 8 Install the Business Modeler IDE
– 4 Tier Teamcenter Server Configuration

Select this option if you want to connect to a server in a four-tier
environment using HTTP protocol.
When you select one of these options, a server connection profile is added
in the Business Modeler IDE.
For more information, see the Business Modeler IDE Guide.
Caution
In most instances, only use these options to connect to a test server
rather than a production server. However, you can also deploy
operational data such as LOVs and rules to production servers.
b. In the Installation Directory, enter the location where you want to install
the Business Modeler IDE. The Business Modeler IDE files are installed to a
bmide subdirectory.
c. Click Next.
4. Perform the following steps in the Business Modeler IDE Templates panel:
a. Select the templates to install. Templates contain the data model for
Teamcenter solutions.
Select the same templates that were installed on the server so that you can
see the same data model definitions in the Business Modeler IDE that were
installed on the server. At a minimum, select the Teamcenter Foundation
check box. The Foundation template contains the data model used for core
Teamcenter functions. All customer templates must extend the Foundation
template.
Note
Make sure that you select the same templates that are on the server.
b. If you have any templates of your own to install or a template from a third
party, click the Browse button and browse to the directory where the
templates are located.
c. Click Next.
5. In the Java Development Kit dialog box, click the browse button to locate
the JDK installed on your system. The kit is used for creating services. For
Teamcenter 8, use Java Development Kit 1.5 (5.0). Click Next.
6. If you selected the 2 Tier Teamcenter Server Configuration option, perform the
following steps in the IIOP Servers Settings panel:
a. In the Connection Port box, type the server port number. The default is 1572.
b. Click the arrow in the Server Activation Mode box to select the mode to use
when connecting to the server. NORMAL is the default.
If you want to allow multiple concurrent user sessions to the two-tier rich
client, select PER_CLIENT.

Install the Business Modeler IDE
c. Click the ellipse button to the right of the Server Config Folder box to
select the folder where you want this configuration saved. The default is
TC_ROOT\iiopservers.
d. Click the Edit button to the right of the TcServers box to change the server
connection profile settings, or click the Add button to add another server
to connect to.
e. Click Next.
7. If you selected the 4 Tier Teamcenter Server Configuration option, perform the
following steps in the Middle-tier Servers Settings panel:
a. Leave the Compress (gzip) the responses from the Web application servers
check box selected if you want faster connection performance from the server.
b. Click the Add button to the right of the Multi-tier Servers table if you want
to add another server to connect to.
c. Click Next.
8. Complete the remaining panels to finish the installation in Teamcenter

Environment Manager. When the installation is complete, exit Teamcenter
Environment Manager.
9. Verify the installed files in the install-location/bmide directory.

The following data model files are placed into the
install-location/bmide/templates folder:
• baselines\template-name_tcbaseline.xml
Contains a snapshot of the template’s data model taken at the release of
Teamcenter 8, if a baseline was taken.
• template-name_dependency.xml
Lists the other templates that this template is built on top of, for example,
the Foundation template.
• template-name_template.xml
Contains the data model for this template, including business objects,
classes, properties, attributes, lists of values (LOVs), and so on.
• master.xml
Lists the template XML files included in the data model, for example, the
foundation_template.xml file.
Install the Business Modeler IDE to an existing Eclipse environment

If you already have Eclipse installed, you can install the Business Modeler IDE
into your Eclipse environment. Install the Business Modeler IDE to an Eclipse
environment if you want to install additional plug-ins to aid in your configuration
work.

For more information about Eclipse, see the following URL:

http://www.eclipse.org
1. Ensure you have an Eclipse 3.3 (Europa) package installed. To download Eclipse,
see the following URL:
http://www.eclipse.org/downloads/packages/release/europa/winter
You can install the Business Modeler IDE to any Eclipse 3.3 package.
2. In the Teamcenter software distribution image, change to the following

directory:
additional_applications/bmide_plugins
3. Extract the bmide_plugins.zip file to your Eclipse directory (ECLIPSE_HOME).

This archive contains the Business Modeler IDE plug-ins.
4. Extract the following archive files to your Eclipse directory. These archive
contain plug-ins needed by the Business Modeler IDE.
Note
Install these only if your Eclipse environment does not already have the
plug-ins.
• cdt-master-4.0.3.zip
Contains the C/C++ Development Toolkit (CDT) plug-ins. CDT provides
the capability to work with projects that use C or C++ as a programming
language.
• dtp-sdk_1.5.zip
Contains the Data Tools Platform (DTP) plug-ins. DTP provides a number of
tools for working with data sources.
• eclipse-JDT-SDK-3.3.zip
Contains the Java Development Tools (JDT) plug-ins. JDT provides tools for
implementing a Java IDE.
• emf-sdo-xsd-SDK-2.3.0.zip
Contains the Eclipse Modeling Framework (EMF) plug-ins. EMF is a
modeling framework and code generation facility for building tools and other
applications based on a structured data model.
• GEF-SDK-3.3.zip
Contains the Graphical Editing Framework (GEF) plug-ins. GEF allows
developers to take an existing application model and create a graphical
editor.
• wtp-sdk-R-2.0.zip
Contains the Web Tools Platform (WTP) plug-ins. WTP helps you develop
Web and Java EE applications.

5. If you need language support, extract the appropriate language pack to your
Eclipse directory:
• NLpack1-GEF-SDK-3.2.zip
Contains the GEF language pack for German, Spanish, French, Italian,
Japanese, Korean, Portuguese (Brazil), Traditional Chinese, and Simplified
Chinese.
• NLpack2-GEF-SDK-3.2.zip
Contains the GEF language pack for Czech, Hungarian, Polish, and Russian.
• NLpack2a-GEF-SDK-3.2.zip
Contains the GEF language pack for Danish, Dutch, Finnish, Greek,
Norwegian, Portuguese, Swedish, and Turkish.
• NLpackBidi-GEF-SDK-3.2.zip
Contains the GEF language pack for Arabic and Hebrew.
6. After unzipping the plug-ins, verify their installation at ECLIPSE_HOME.
7. Install the Business Modeler IDE development templates using Teamcenter

Environment Manager (TEM).
In the Select Features window, choose Business Modeler IDE→Business
Modeler Templates (do not choose Client). The templates are installed under
the Installation Directory location in a subdirectory.
Note
Make sure that you select the same templates that are on the server.
Allocate memory to the Business Modeler IDE

Allocate memory to the Business Modeler IDE so that it has enough to launch and
run. You can allocate memory in the following ways:
• BusinessModelerIDE.ini file
To increase the memory allocated to the Business Modeler IDE, open the
install-location/bmide/client/BusinessModelerIDE.ini file and change the
–Xmx512M value to a higher number to allocate maximum Java heap size. For
example, if you have 2 GB available to dedicate for this purpose, set the value to
-Xmx2048M. Do this only if your machine has the available memory.
The Xms value in this file sets the initial Java heap size, and the Xmx value sets
the maximum Java heap size.
• BMIDE_SCRIPT_ARGS environment variable

To allocate the memory required by scripts during installation, update, or
load of templates with large data models, create a BMIDE_SCRIPT_ARGS
environment variable. Set the BMIDE_SCRIPT_ARGS variable to
–Xmx1024M to allocate 1 GB of RAM to the Business Modeler IDE scripts. If

your system has more memory that you can allocate to the Business Modeler
IDE, you can set the value higher.
Caution
If you set the Xmx value to a higher value than the RAM your system has,
you may get the following error when you launch the Business Modeler IDE:
Could not create the Java virtual machine.
Set the Xmx value to a setting that your system supports, in

both the BMIDE_SCRIPT_ARGS environment variable and the
BusinessModelerIDE.ini file.
Note
If you are running the Business Modeler IDE in an Eclipse environment, run
the following command to increase virtual memory to 1 GB:
eclipse.exe -vmargs -Xmx1024M
Start the Business Modeler IDE

1. You can start the Business Modeler IDE in several ways, depending on how
you installed it:
• Start the stand-alone application.
Note
To ensure that you have enough memory to run the Business Modeler
IDE, allocate memory in the BusinessModelerIDE.ini file and in a
BMIDE_SCRIPT_ARGS environment variable.
• Start from an Eclipse environment.

Navigate to the directory where Eclipse is installed and execute the Eclipse
command.
Note
To ensure that you have enough memory to run Eclipse, you can run
the Eclipse.exe command with a virtual memory argument. For
example, the following command increases virtual memory to 1 GB:
Eclipse.exe —vmargs —Xmx1024M
When you start the Business Modeler IDE for first time, the Welcome window
is displayed.
2. Click one of the buttons in the Welcome window to learn more about the
Business Modeler IDE:
• The Overview button provides links to online help topics.

• The Tutorials button provides links to tutorials.

3. To work in the IDE, click the Workbench button in the right side of the
Welcome window.
The Workbench is the main window in Eclipse. The Workbench window shows
one or more perspectives. A perspective is an arrangement of views (such as the
Navigator) and editors. At the top of the Workbench is a toolbar that allows you
to open new perspectives and move between ones already open. The name of the
active perspective is shown in the title of the window.
Note
You can access the Welcome window again later by choosing
Help→Welcome from the Business Modeler IDE.
4. Choose Window→Open Perspective→Other→Business Modeler IDE.

The Business Modeler IDE perspective is displayed.
Note
If a perspective fails to open, it could be that not enough memory is being
allocated to the Business Modeler IDE.
5. In the Business Modeler IDE perspective, click the Business Objects tab to
open the Business Objects view. This view displays the business objects (types)
defined in the data model. Use this view to create new business objects to
represent parts, documents, and so on.

Chapter
9 Installing a custom solution or

third-party template
Install a template using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Update a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Chapter
9 Installing a custom solution or

third-party template
Install a template using TEM

After you package extensions, install the resulting template to a production
environment using Teamcenter Environment Manager (TEM). You can also use this
procedure to install a third-party template.
1. Copy the template files from the packaging directory on your Business Modeler
IDE client to a directory that is accessible by the server.
By default, packaged template files are located in the Business Modeler IDE
workspace directory in the folder under the project.
On UNIX, users must have permissions to the workspace directory.
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 Selection 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.
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 Select 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

Chapter 9 Installing a custom solution or third-party template
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 Teamcenter Corporate Server
on the Select Features panel.
9. Select the new template in the Select Features panel under Teamcenter
Corporate Server. Click Next.
10. In the Teamcenter Administrative User panel, enter your username 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 Confirm Selections panel, click Next. The new template is installed.
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.
Update a template
If you already installed a template as a new feature and want to update it because
you have added more data model definitions to it, perform the following steps:
1. Copy the packaged template files from the packaging directory on your
Business Modeler IDE client to a directory that is accessible by the server.
By default, packaged template files are located in the Business Modeler IDE
workspace directory in the folder under the project. .
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.

Installing a custom solution or third-party template
5. The Configuration Selection panel displays the installed configuration. Click

Next.
6. In the Feature Maintenance panel, under the Teamcenter Foundation section,

select Update the database. Click Next.
Note
Use the Add/Update Templates option under Business Modeler
Templates only if you want to add or update a dependent template to
your Business Modeler IDE.
7. In the Teamcenter Administrative User panel, enter your user name and
password to log on to the server. Click Next.
8. The Database Updater panel displays currently installed templates in the

Applied Templates table. Click the Browse button in the lower right corner of
the panel and locate the directory where the packaged template files are located.
Select the updated template-name_template.zip file.
The template appears as an option on the Candidate Templates table.
9. Select your template on the Candidate Templates table and click Next.
10. In the Confirm Selections panel, click Next.

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

Chapter
10 Manufacturing
Install the Manufacturing content kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Populate the sample database for Manufacturing . . . . . . . . . . . . . . . . . . . . . 10-2
Install the Manufacturing Tooling Library . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Configure NX CAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Planning data migration from Genius4000 to Resource Manager . . . . . . . . . . 10-6
Migrate Genius4000 data to Resource Manager . . . . . . . . . . . . . . . . . . . . . . . 10-8

Chapter
10 Manufacturing
To populate the database with sample Teamcenter’s manufacturing process

management data, make sure that the Teamcenter corporate server is installed on
the installation host and the Teamcenter database is configured or upgraded.
Install the Manufacturing content kit

Note
This option populates a database with sample data in a predetermined
classification hierarchy. Use it for creating and maintaining a sample
database, not for importing data to a working database. To import other data,
you must use the SML utility (smlutility), the ICS utility (icsutility), or
PLM XML.
1. Obtain the Teamcenter software distribution image and navigate to the

advanced_installations\resource_management\server directory.
2. Click Setup.exe.
Teamcenter displays the Setup Configuration Type Selection dialog box.
3. Click Resource Manager – Database Population and click Next.

Teamcenter displays the Choose TC_ROOT Directory dialog box.
4. 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.
5. Choose the path to the directory containing the database-specific data files and
click Next. The path must point to an existing TC_DATA directory.
Teamcenter displays the Content Selection dialog box.
6. Select which kind of examples you want to load into the database. You can select
tools, machines, fixtures, weld guns, robots, or NX CAM templates. If you select
tools, Teamcenter loads a subset of the Manufacturing Tooling Library containing
20 sample tool assemblies, and the corresponding catalog and customer classes.
7. Click Next.
Teamcenter displays the Overwrite Existing Data dialog box.

Chapter 10 Manufacturing
8. 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 intact.
9. Click Next.
Teamcenter displays the Name and Password dialog box.
10. Type the user name, password, and group name of the valid Teamcenter
installation account under which you want to install the data and click Next.
Teamcenter displays the Confirm Selections dialog box.
11. Confirm that all your selections are correct and then click Next.
Teamcenter installs the specified classification hierarchies and data into your
database. When the setup is complete, the name and location of the install log
are displayed.
Populate the sample database for Manufacturing

To populate the sample database on a UNIX server, you must use a Windows rich
client. If you do not have one in your network, you must add one temporarily. Once
you have done this, start the setup found on the Windows installation CD-ROM
under: cdrom\advanced_installations\resource_management\server
Alternatively, you can move a copy of your UNIX database and Teamcenter volume
to a Windows client, load the Resource Manager with default data on Windows, and
then move the populated database and volume back to UNIX.
Install the Manufacturing Tooling Library

1. Obtain the Manufacturing Tooling Library installation DVD.
2. Click Setup.exe.
3. Click Import Manufacturing Tooling Library Data.
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.
Teamcenter displays the Content Selection dialog box.
7. Specify which types of data you want to load. You can choose from the following:

Manufacturing
• Catalog Hierarchy and Data

This loads the complete classification hierarchy of thousands of classes and
more than 30,000 catalog components. This is original vendor data that you
can use to create tools and assemblies. The catalog hierarchy and data will
be updated by Siemens PLM Software at regular intervals in the future.
• Customer Hierarchy
This structure contains two classification hierarchies—one for your
components, and one for the assemblies you create. You can fill this
hierarchy with your customer-specific data, mapping data from the catalog
hierarchy where necessary. This hierarchy will not be automatically updated
by Siemens PLM Software in the future.
• Customer Sample Data

This loads approximately 20 sample tool assemblies and their component
parts into the customer hierarchy. These assemblies contain 3D graphics
and image files.
Note
The objects created by loading the sample data are all of the Item
item type. To load the sample data, your database should support
this item type.
8. Click Next.
Teamcenter displays the Overwrite Existing Data dialog box.
9. 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.
10. Click Next.

Teamcenter displays the Language Selection dialog box.
11. Select the language in which the classification hierarchy and data should be
displayed in the user interface and click Next.
If you select English, Teamcenter displays the Measurement Unit dialog box.
12. Select whether you want to install the metric or the imperial (inch) version of
the data.
Note
The 20 sample tool assemblies are available only in metric. If you select
inch, they are loaded into the database but not converted into inch.
This can cause the data to appear incorrectly but does not affect the
classification hierarchies.
13. Click Next.

Teamcenter displays the Name and Password dialog box.

14. Type the user name, password, and group name of the valid Teamcenter
installation account under which you want to install the data and click Next.
15. Confirm that all your selections are correct and then click Next.
Teamcenter installs the specified classification hierarchies and data into your
database. When the setup is complete, the name and location of the install log
are displayed.
Configure NX CAM
When you install the manufacturing tooling data, you must configure NX CAM so
that the new data appears in the library selection dialog boxes when searching
for classified tools in NX CAM.
1. Start the setup program as described in Install the Manufacturing Tooling
Library or Install the Manufacturing content kit.
2. Click Configure NX Library.

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

click Next.
• If you are installing the Teamcenter Manufacturing content kit, Teamcenter
opens the Confirm Selections dialog box. Proceed to step 5.
• If you are installing the Manufacturing Tooling Library, Teamcenter displays

the Language Selection dialog box.

Manufacturing
4. Select the language in which you want the NX Library selection dialog boxes to
appear and click Next.
5. Confirm your selections and click Next.

Teamcenter performs the following actions:
• Updates the image files in the UGII_BITMAP_PATH directory

(UGII_BASE_DIR\UGII\symbols\). When installing the content kit, it
copies 20 image files. When installing the Manufacturing Tooling Library,
Teamcenter copies about one thousand image files into this directory.
• Copies a new event handler file.

– If you are installing the Manufacturing Tooling Library, the file is copied
to UGII_BASE_DIR\MACH\resource\library\tool\inclass\
dbc_mfg_toollib_customer_tlas.tcl.
– If you are installing the Teamcenter Manufacturing content kit, the file is
copied to UGII_BASE_DIR\MACH\resource\library\tool\inclass\
dbc_mfg_toollib_sample_customer_tlas.tcl.
• Copies a new definition file.

– If you are installing the Manufacturing Tooling Library, the file is copied
to UGII_BASE_DIR\MACH\resource\library\tool\inclass\
dbc_mfg_toollib_customer_tlas_eng.def.
– If you are installing the Teamcenter Manufacturing content kit, the file is
copied to UGII_BASE_DIR\MACH\resource\library\tool\inclass\
dbc_mfg_toollib_sample_customer_tlas_eng.def.
• Appends new materials to the existing

tool_materials.dat material library file found in
UGII_BASE_DIR\MACH\resource\library\feeds_speeds\ascii\
tool_materials.dat.
• Adjusts the LIBRARY_TOOL entry in the

cam_part_planner_library.dat configuration file found in
UGII_BASE_DIR\MACH\resource\configuration\
cam_part_planner_library.dat to point to the new Manufacturing
Tooling Library or Teamcenter Manufacturing content kit event handler
and definition file.
• Creates backup copies for all NX files that are modified.
6. Select the cam_part_planner_library.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.

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.
If you are running Genius4000 solely on a UNIX system with no Microsoft Windows
client, you can perform only part of the migration on the UNIX system. You must
use a Windows system to perform the remainder of the process.
On the UNIX system, you create a migration directory structure and copy it to the
Windows system using a script provided with the Teamcenter’s manufacturing
process management Genius2MRM Migration kit. Download the kit from the FTP
server on Siemens PLM Software GTAC online support
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.
This is the only step in the migration procedure that is performed on
a UNIX system.
Step 3: Import the Resource Manager data into the 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.
Begin migration on the UNIX system:

1. Download the Teamcenter’s manufacturing process management Genius2MRM
Migration kit from the FTP server on Siemens PLM Software GTAC online
support.

Manufacturing
2. Copy the genius2mrm_copy_files.ucl script from the

UGS/GeniusToMRM/Genius4000/genius_base/ucl directory to the UNIX
system (for example, use ftp in ASCII mode).
3. Log on to the UNIX system where Genius4000 is installed.
4. Set the Genius4000 environment in the shell:

GENIUS_BASE_DIR=/genius-root-directory/
export GENIUS_BASE_DIR
. {GENIUS_BASE_DIR}exe/genius_env_setup.ksh
Replace genius-root-directory with the directory where Genius4000 is installed.
5. Set the following Genius4000 environment variable:

GENIUS_BATCH_USE_UG=True
export GENIUS_BATCH_USE_UG
6. Execute the ucl script:

genius_batch genius2mrm_copy_files.ucl genius-modules output-directory
Replace genius-modules with the names of the Genius4000 modules whose data
you want to copy. Separate the modules with commas. For example:
genius_batch genius2mrm_copy_files.ucl TCM,TAM,FCM output-directory
Replace output-directory with the name of the directory to which the files are
copied. If this directory does not exist, the script creates it. The output directory
and subdirectories contain the class graphics.
This creates the following structure:
g4_files
g4_files/ClassGraphics
g4_files/ClassGraphics/Images
g4_files/SampleDataGraphics
g4_files/GeniusTolGraphics
The script loops over the specified modules and, for each class and resource ID,
checks for the existence of corresponding documents in the GENIUS_DATA_DIR.
The following occurs:
• Class-specific graphics are copied to ClassGraphics/Images.
• If part family templates exist, they are placed in ClassGraphics.
• Instance-specific files (documents for each resource ID) are copied to

SampleDataGraphics.
• If the system finds a PRT file for an instance, it ignores any additional TOL
file.
• If there is only a TOL file for one resource (and no NX part file), this TOL file
is automatically converted to a PRT file and placed in GeniusTolGraphics.
In most cases, NX part files in GENIUS_DATA_DIR consist of 3D data. If there

is only a TOL file, the graphics probably only exist in a 2D format. Later in the

conversion step, you can convert the original part files to JT files and the PRT
files which were converted from TOL files to CGM files.
7. Create one compressed container-file from the output structure. Create either
a tar file or a zip file. For example:
zip —r g4_files.zip g4_files
or
tar —cvf g4_files.tar g4_files
8. Copy the container file to Windows using, for example, ftp in binary mode.
9. Extract the container file into the Windows MRM import structure.
When you complete this procedure, continue the migration process on the Windows
system. For information, see the instructions for configuring Teamcenter’s
manufacturing process management in the Installation on Windows Servers Guide.
Migrate Genius4000 data to Resource Manager

Convert Genius4000 data to Resource Manager using the Genius4000 to Resource
Manager migration kit. This kit is available for download on the Siemens PLM
Software GTAC FTP server.

Chapter
11 Installing Teamcenter’s reporting

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

Chapter
11 Installing Teamcenter’s reporting

and analytics
Install and configure Teamcenter’s reporting and analytics (Reporting and Analytics)
in a new or existing Teamcenter configuration.
Before you begin

Download the Teamcenter’s reporting and analytics
(Reporting and Analytics) software distribution image
(TeamcenterReportingAndAnalytics-2007-platform.tar ) from the Siemens
PLM Software FTP site.
TcRA requires additional preinstallation steps. For information about steps to
perform before you install Teamcenter’s reporting and analytics (Reporting and
Analytics), see the Teamcenter’s reporting and analytics 2007 Deployment Guide in
the Reporting and Analytics software distribution image.
Create the Reporting and Analytics database

Reporting and Analytics requires an Oracle 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.

Chapter 11 Installing Teamcenter’s reporting and analytics
For more information about creating the metadata database for Reporting and
Analytics, see Pre Installation Steps in the Teamcenter Environment Manager 2007
Deployment Guide.
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
On Sun Solaris and Hewlett-Packard HP-UX systems, the Reporting and
Analytics license server uses the host’s HOSTID value address to identify the
host. On Linux systems, the license server uses the host’s MAC address.
You must supply this information when you request an eQube license file
from eQ Technologic.
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.
3. Proceed to the Reporting and Analytics Install Options and General Settings
panel. Select one or more of the following options to include in your Reporting
and Analytics installation:
Create license server Specifies you want to install a Reporting and

Analytics license server. If you select this
option, TEM later prompts for the location of
the eQube license file (license.dat). If you do
not select this option, TEM later prompts for
the location of the Reporting and Analytics
license server.
Create WAR file Specifies you want to generate a Reporting
and Analytics WAR file.
Create metadata Specifies you want to populate the metadata
database for Reporting and Analytics. Select
this only during the first installation of
Reporting and Analytics. If you are upgrading
from a previous version of Reporting and
Analytics or adding additional hosts, do not
select this option.
4. Enter the required information in the TEM panels described in table 11-1,
depending on the options you select.

Installing Teamcenter’s reporting and analytics
Table 11-1. TEM panels for Reporting and Analytics installation

TEM panel Description
Reporting and Analytics In the License File box, enter the location
License Server Settings of the Reporting and Analytics license file
(license.dat). This panel is displayed only if
you select Create license server.
Reporting and Analytics WAR In the Web Application Context box, type
Settings the application name for the Reporting and
Analytics Web application. This name is
included in the URL for the Web application:
http://host-name:port/context-name/rest-of-path
For example, if the Web application context
is Reporting and Analytics, a resulting URL
could be as follows:
http://AcmeCorp:7001/TcRA/BuildNPlay
This panel is displayed only if you select
Create WAR file.
Reporting and Analytics In the License Server Host box, type the
License Settings the IP address or the fully qualified name of
the Reporting and Analytics license server
host. In the License Server Port box, enter
the port on which the license server accepts
connections. This panel is displayed only if
you do not select Create license server.
Reporting and Analytics In the Database Engine Selection box,
Database Selection choose your database vendor (Oracle or
MS SQL Server 2005, and then enter the
required information about the Reporting
and Analytics database you created in Create
the Reporting and Analytics database. For
information about fields in this panel, click
Help.
Reporting and Analytics WAR Specify Reporting and Analytics WAR and
and Metadata Settings metadata settings:
Enable SSO If you use Reporting and

Analytics with Security
Services, select this
check box. This option
requires that you install
Teamcenter with Security
Services enabled and
configure the LDAP
server before you install
Reporting and Analytics.
For information about
installing Security

Chapter 11 Installing Teamcenter’s reporting and analytics
Table 11-1. TEM panels for Reporting and Analytics installation

TEM panel Description
Services, see the
Security Services
Installation/Customization
guide.
Metadata Owner Type the user name for
the owner of Reporting
and Analytics metadata.
By default, this is the
database user name
for the Reporting and
Analytics database.
Web Application Specifies the vendor of the
Server Web application server
on which you deploy
Reporting and Analytics.
Options are WebSphere
(for IBM WebSphere)
and WebLogic (for BEA
WebLogic).
This panel is displayed only if you do not

select Create WAR file.
Reporting and Analytics In the Teamcenter 4–tier URL box, type the
Metadata Settings URL to the Teamcenter 4-tier rich client
(http://host:port/context-root).
In the next four boxes, type the user name,
password, group, and role of the Teamcenter
user who administers Reporting and
Analytics.
Under Oracle Tablespace Names, type the
names of the Oracle tablespaces you created in
Create the Reporting and Analytics database.
This panel is displayed only if you select
Create metadata.
Note
If you select Enable SSO in the Reporting and Analytics WAR
and Metadata Settings, TEM displays additional panels to gather
configuration information for Security Services. For information about
these panels, click Help.
5. Proceed through the remaining TEM panels and begin installing Reporting
and Analytics.

Installing Teamcenter’s reporting and analytics
During installation, TEM prompts you for the location of the TCRA_2007.zip
file.
When installation is complete, close TEM.
Deploy Reporting and Analytics

Deploy Reporting and Analytics as described in the Teamcenter’s reporting and
analytics 2007 guide in the Reporting and Analytics software distribution image.
Complete Reporting and Analytics installation

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

with Teamcenter.
For information about setting preferences, see Getting Started with Teamcenter.
2. Test connections to Reporting and Analytics applications. Log on to Reporting

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

http://host:port/Reporting and Analytics-context/BuildNPlay
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.
Note
For information about using the Reporting and Analytics integration, see the
Report Builder Guide.

Part
V Web tier installation
J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

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

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

Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . 12-19
Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Rich client distribution instance requirements . . . . . . . . . . . . . . . . . 12-22
Install a rich client distribution instance . . . . . . . . . . . . . . . . . . . . . 12-28
Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Deploy the distribution server instance . . . . . . . . . . . . . . . . . . . . . . 12-31
Publish information for users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34
Start and stop the rich client distribution server . . . . . . . . . . . . . . . 12-34
Start the rich client distribution server . . . . . . . . . . . . . . . . . . . 12-34
Stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . 12-35
Managing the rich client distribution server and instances . . . . . . . . . . . 12-35
Change the distribution server contents . . . . . . . . . . . . . . . . . . . . . 12-35
Add components to the distribution server instance . . . . . . . . . . . . . 12-35
Run the distribution server as a service . . . . . . . . . . . . . . . . . . . . . . 12-37

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

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

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

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

Chapter 12 J2EE Web tier installation
J2EE Web tier prerequisites

Before you install the J2EE Web tier, make sure you complete the following tasks:
• Install the Teamcenter server and server manager using Teamcenter
Environment Manager as described in Teamcenter server installation.
• Install a supported third-party J2EE application server and the Java Runtime
Environment (JRE) on the Web tier host.1
• If you want to install Teamcenter online help for the Web tier, obtain the
Teamcenter 8 documentation distribution image.
Note
Alternatively, you can install online help using Teamcenter Environment
Manager rather than installing it as part of the Web tier.
For information, see Teamcenter online help installation.
• If you use Security Services with the rich client or thin client, install Security
Services as described in Security Services installation.
Install the Web Application Manager

1. Create a home directory for the Teamcenter Web tier, for example, /tcweb. This
directory is referenced as WEB_ROOT.
2. Change to the WEB_ROOT directory.
3. Type the following command to extract Web Application Manager files to your
host:
cat image-path/INSTALL_TCWEB.TZ | uncompress -c | tar xvf -
Replace image-path with the full path to the Teamcenter software distribution
image.
4. To launch the Web Application Manager, change to the WEB_ROOT directory

and enter the following command:
insweb
Installing thin client Web applications

The first thin client Web application you build is the Teamcenter Web Tier
application, which provides essential thin client functionality. To this application
you can add additional thin client solutions, including custom solutions, according
to your needs.
1. For information about supported application servers and Java versions, see the Siemens PLM Software Certification Database
(http://support.ugs.com/online_library/certification/).

J2EE Web tier installation
For information about installing this application, see Build the Teamcenter Web
Tier Web application.
After you build the Teamcenter Web Tier application, you can build additional
Web applications to support Teamcenter features you use, as described in Build
additional Web applications.
Build the Teamcenter Web Tier Web application

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

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

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

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

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

distribution image to the Disk Locations for Install Images box:
image-location/Web_tier
Use the Add or Modify buttons to add a location or modify an existing one.
Note
Do not change the default solution type (Thin Client) shown in the
Solution Type box.
5. Select the solutions to include in the Teamcenter Web Tier Web application:
a. Click Solutions.
b. In the Select Solutions dialog box, select the following required solutions:
Teamcenter – Server Adapter
Teamcenter Web Tier Infrastructure

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

8. Enter values for required context parameters.

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

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

Depending on the Teamcenter features you use, build one or more of the Web tier
applications described in table 12-1.
Table 12-1. Additional Teamcenter Web applications

Feature Application Description
Global Global Services Provides the application directory
Services application directory functionality required by Global Services.
application For information about installing this
application, see Install Global Services.
4. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose
the appropriate procedure for the application server you use.

Table 12-1. Additional Teamcenter Web applications

Feature Application Description
Global Services Provides essential Global Services
Enterprise application functionality. You can add Global Services
connectors and other components to
this application. For information about
installing this application, see Install
Global Services.
Content Content Management Provides the application for Content
Management Base Management Base, an optional
Teamcenter solution. For information
about installing this application see
Generate the Web application for Content
Management.
Content Management Provides the application for Content
S1000D Management S1000D, an optional
Teamcenter solution. For information
about installing this application see
Generate the Web application for Content
Management.
Thin client Proxy WAR file for Provides support for WebLogic Express
deployed on WebLogic application as a front-end HTTP listener for the thin
WebLogic client.
Express
For information about installing this
application, see Build a proxy WAR file
for WebLogic.
Legacy thin Legacy URL support Upgrades legacy thin client URLs to
client support application Teamcenter 8. If you are upgrading a
previous Teamcenter installation that
includes the thin client, generate the
legacy URL management application.
For information about installing this
application, see Migrate legacy thin client
URLs.
Install Global Services
You build Global Services Web applications using the Web Application Manager.
Supporting files locations
Several Global Services connectors require that you provide the location to files that
are provided by the connector’s back-end system or from some other source. The
location must be accessible to the Web Application Manager as you must enter the
path to the file in the Disk Locations for Install Images box. If you plan to include
the connector in your Web application, ensure the files identified for the connector
are available, and note the path to the file for use in Generate Web applications.

Note
As an alternative to having the directories containing dependent connector
files accessible to the Web Application Manager, you can copy the dependent
files to an accessible location. However, if you do not keep the files in the
paths indicated in the ICD file, you must edit the ICD file for the connector
to eliminate or correct the path. For example, the Teamcenter Enterprise
connector ICD has the following dependent file entry:
[COPYFILE]
{
[FROM]
enterprise/mti.jar
[TO]
lib/enterprise
}
If you copy the mti.jar file to a Web Application Manager accessible location,
it must be in the enterprise directory under the location set in the Disk
Location to Add box. Alternatively, you can edit the ICD file to remove
enterprise/ from the [FROM] section.
• Teamcenter Enterprise connector

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

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

• Teamcenter Engineering 2005/2007 connector

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

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

If you are installing the Teamcenter 2007 rich client connector, the connector
requires access to dependent external JAR les. These files are located in the
portal\plugins directory for the Teamcenter server installation and must be
available to the Web Application Manager during the install process. The files
used from this directory are:
– com.teamcenter.rac.aifrcp_2007.1.0.jar
– com.teamcenter.rac.kernel_2007.1.0.jar
– com.teamcenter.rac.util_2007.1.0.jar
– icctstubs.jar
– tcgatewaystubs.jar
– TcSoaClient_2007.1.0.jar
– TcSoaCommon_2007.1.0.jar
– com.teamcenter.rac.external_2007.1.0\TcGatewayWebService.jar
– xmldto.jar
– configuration_2007.1.0\portal.properties
– configuration_2007.1.0\portal_locale.properties
– configuration_2007.1.0\portal_user.properties
– configuration_2007.1.0\site_specific.properties
– org.eclipse.jface_3.2.0.I20060605-1400.jar
– org.eclipse.ui.workbench_3.2.0.I20060605-1400.jar
– org.eclipse.core.commands_3.2.0.I20060605-1400.jar

The following files must also be available to the Web Application Manager in
the indicated directory path:
– WEB-INF\lib\JETIGateway-ejb-client.jar
– pool_manager\JETIUtil.jar
– teamcenter\dhtml\apps\fms\fscproxy.jar
• Oracle Manufacturing connector

This solution requires the ojdbc14.jar file location. You must download this file
from Oracle’s Web site.
• SAP connector
This solution requires the jco.jar file location. This file is included in the
JCO package that you must download (includes installation instructions
and documentation) from http://service.sap.com/connectors. This Web site
requires a valid SAP Services Marketplace login account. If you do not
have a valid account, visit http://service.sap.com to register. Unzip the
JCO package file that you downloaded and extract the jCO.jar file and
supporting library files it contains. If you are installing on Windows, extract
the librfc32.dll and jRFC12.dll files. If you are installing on UNIX,
extract the librfccm.so and libjRFC12.so files. After you create the
Global Services enterprise application, copy the files you extracted to the
WEB_ROOT/application-directory-staging-directory/webapp_root/lib directory.
Generate Web applications

Note
Some solutions require other solutions, and some solutions are incompatible
with others. When you select a solution, the Web Application Manager
automatically selects prerequisite solutions and disables incompatible
solutions. For example, Teamcenter – Server Adapter and Teamcenter 8
Global Services Framework – Enterprise Application are 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:

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

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

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

7. Create the Global Services enterprise application:

a. In the Name box, type a name for the application, for example, Global
Services Enterprise Application.
c. Click Advanced Web Application Options. Type a name for the deployable
file in the Deployable File Name box (alphanumeric characters only)..

If you require the deployable file to be a distributable file, select the

Distributable option.5
d. (Optional) Enter the application’s description in the Description box.

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

a. Click Solutions.
b. In the Select Solutions dialog box, clear all preselected solutions and select
the Teamcenter 8 Global Services Framework – Enterprise Application
Core Library solution.
9. If you selected a connector that requires supporting files (see Supporting files
locations), click Modify Disk Locations and add the path to any supporting files.
10. Click OK.


For most context parameters, accept the default values shown. At a minimum,
Global Services requires values for the following context parameters:
Note
For a description of these parameters, see Web tier context parameters.
ApplicationInstance TcGSJDBCJNDI
SSOAppID TcGSMessageServerJNDI
LogFileLocation TcGSNotifierReactorJNDI
TcGSBOSJNDI TcGSDORJNDI
For more information about Global Services context parameters, see Global
Services context parameters.

dialog box.
5. A distributable file is required only if you deploy the Web tier application in a cluster configuration.

14. Locate the deployable file (by the name you specified in step 7) generated during
installation. This file is in the deployment directory under the specified staging
location.
Guide.6
Generate the Web application for Content Management
Use the Web Application Manager to generate the Web application for Content
Management, an optional Teamcenter solution.
2. Click Add to begin creating the Content Management application.

3. Create the application directory application:

a. In the Name box, type a name for the application, for example, Content
Management Base.
c. Accept the default value for Disk Locations for Install Images.
d. Click Solutions.
e. In the Select Solutions dialog box, clear all preselected solutions and
select only the Teamcenter Content Management S1000D System or
Teamcenter Content Management System.
Note
Select the Teamcenter Content Management S1000D System option
only if you have already installed the Content Management System
S1000D feature.
4. Click OK to begin installing the solution.

dialog box.
5. In the Add Web Applications dialog box, click Advanced Web Application
Options. Type a name for the deployable file in the Deployable File Name box
(alphanumeric characters only). Click OK.

Tip
It is recommended that you use the same name you entered to name the
application in step 3.
6. Click OK.


dialog box.
10. Locate the deployable file generated during installation (by the name you
specified in step 5). This file is in the directory under the specified staging
location.
Deploy the Web application as described in Web Application Deployment Guide.
Build a proxy WAR file for WebLogic

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

3. Create the proxy WAR file Web application:

a. In the Name box, type the name of this application, for example, WebLogic
Proxy.
c. Optionally, type a description of the application in Description box.
d. Click Advanced Web Application Options. Type a name for the deployable
file in the Deployable File Name box (alphanumeric characters only).
e. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image.

f. Click Solutions. In the Select Solutions dialog box, clear all preselected
solutions and select only the Teamcenter – Web Tier Proxy solution.7
Note
box.
4. Click OK.
5. Enter values for the following required context parameters:
WebLogicHost Host name of the WebLogic server running
the Web tier. The proxy forwards the request
to this server.
WebLogicPort Port number of the WebLogic server instance
running the Web tier. The proxy forwards the
request to this server.
6. Click OK to begin building the Web application. The Web Application Manager
displays the status of the installation in the Progress dialog box. When the
installation is complete, click OK to close the Progress dialog box.
8. Locate the deployable file by the name you entered in step 3. This file is in the
deployment directory under the specified staging location.
Guide.8
Migrate legacy thin client URLs

If you migrate Web tier applications to Teamcenter 8 from Teamcenter’s 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 8 changes part of the thin client URL from /cgi-bin/iman to
/file-name/webclient. The file-name reference is replaced with the name of the Web
tier EAR file. For example, if the Web tier EAR file is named tc.ear, the value is /tc.
7. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Web
application.

To manage this change, install the legacy URL support application (cgi-bin.war)
and deploy it on the server where the Teamcenter Enterprise Tier Web application
runs.
Note
• Install the Teamcenter – Legacy URL (cgi-bin) Support thin client
solution in a separate Web application. This solution is not compatible
with other Teamcenter thin client solutions.
• Deploy the application so that it intercepts legacy requests and redirects

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

a. In the Name box, type the name of this application, for example, Legacy
URL Support.

b. Optionally, in the Description box, type a description of the application.
c. Accept the default value for Staging Location or enter a different directory.
d. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image.
e. Click Solutions. In the Select Solutions dialog box, deselect all preselected
solutions and select only the Teamcenter – Legacy URL (cgi-bin) Support
solution.9
Note
box.
4. Click OK.
5. Enter values for the following required context parameters:
TcEngLocale Specifies a locale for messages displayed to
the user. This locale must match the locale
specified for the Teamcenter Enterprise Tier
Web application.
expiryDateOfResource Specifies the date the URL message expires.
MovedNotification This parameter must contain a value.
Enter a value in month-day-year format
(mm-dd-yyyy), for example, 12–10–2007, or
enter one of the following keywords:
NEVER
Specifies that the URL message never
expires.
NOW
Specifies that no message or notification
regarding the resource move is displayed
to the user. The user is immediately
redirected to the new URL.
9. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Web
application.

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

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

perform the following tasks:
1. Install multiple server managers with unique TreeCache settings.

For information about installing a server manager, see Installing the server
manager.
2. Create Web applications as described in Build the Teamcenter Web Tier Web
application. Assign each application a unique name.
3. Set the following Web tier context parameters to unique values for each Web
application.
Table 12-2. Context parameters for shared deployment

Context parameter Description
DEPLOYABLE-FILE-NAME Name of the deployable file you are creating
for the Web tier application.
Enterprise Application Identifier for the Web application. This ID
Registration ID is used to register the application’s EJB and
J2C connector. If you want to deploy multiple
Teamcenter Web tier applications in a single
application server instance, each application
must be assigned a unique ID.
Enterprise Application Specifies the ID by which the Teamcenter
Lookup ID presentation tier accesses the application
identified by the Enterprise Application
Registration ID parameter. If you deploy your
EAR file with other EAR files in the same
application server instance, these two IDs
should be set to the same value for a given
application.
4. Deploy Web application EAR files in the Web application server instance.
For more information, see the Web Application Deployment Guide.
Note
Multiple EAR file deployment is not supported on JBoss. If you use JBoss as
your Web application server, you must deploy each EAR file in a separate
application server instance.
Installing rich client Web applications

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

2. Install a rich client distribution instance or instances.

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

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

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

1. Start the Web Application Manager:
a. Change to the Web_tier directory.
b. Enter the following command:

insweb
The Web Application Manager displays the Teamcenter Web Application

Manager dialog box.
2. Click Copy ICDs.

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


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

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

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

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

14. Type values for the following context parameters:

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

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

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

Rich client distribution instance requirements

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

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

RMI Port Port number used by the rich client distribution server.
This value was determined when the distribution server
was installed. The default is 12099.
WindowsLocation Location on the client host where you want the
Over-the-Web Installer to download rich client files on
Microsoft Windows systems by default.
The drive must exist on the client hosts prior to
rich client installation, and users must have write
permission to it. For example, if the installation location
is F:\Teamcenter8\rich_client, every Windows
client host must have an F drive, and users must have
permissions to create Teamcenter8\rich_client.


UnixLocation Location on the client host where you want the
Over-the-Web Installer to download rich client files on
UNIX systems by default.
The mount must exist on the client hosts prior to rich
client installation, and users must have write permission
to it.
WebBrowserUnixLocation Location of a Web browser on UNIX systems. This
location must be available for UNIX client hosts.
RichClientHelpWebServer URL specifying the name of the host and the port where
the Web tier or presentation tier application files are
deployed in an application server. This parameter works
together with the RichClientHelpLocation parameter to
determine how rich client users access help:
• To enable accessing help over the Web, set the
parameter value to http://host-name:port. Do
not supply the remainder of the path to the
help files (that information is supplied in the
RichClientHelpLocation parameter).
• To enable accessing help using direct file access, set

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

path to the installed help library index.htm file.
HTTPUseGZip Indicates whether the rich client prefers responses
from the J2EE server in a compressed (gzipped)
form. Compressing responses reduces the bandwidth
requirement significantly, and should be considered,
especially in lower bandwidth network environment.
When set to true, the server may send responses without
compression depending on the server configuration.
When set to false, the server never compresses responses
for this rich client.


ParentFSCAddressTable List of addresses (host name and port) of the FMS file
server caches (FSC) to act as the parents of the installed
FMS file client cache.
For information on the FMS file client cache and FMS file
server cache, see Installing File Management System.
HTTPServerTable List of Web tier application servers; the first server in the
list is the default server for logon. Requires the following
information for each server:
URI
URL of the Web tier SOAP endpoint. The value
depends on where the Web tier application is
deployed. Typically it has the form:
http://host-name:port/tc/webclient
Name
Display name of the URL for the rich client graphical
user interface.
SSOAppID
Provides the Teamcenter application ID and sets the
TC_SSO_APP_ID environment variable for Security
Services.
The value you provide in this context parameter is
used only when Security Services is enabled and
either multiple Teamcenter sites are served by a
single identity provider or the Security Services
service is configured to use an ID other than TC.
When the multiple sites have different sets of users
authorized to use the application for each installation,
or different identifications in each installation, this
value identifies which installation is authenticated.
Depending on the solutions you include in your rich client distribution instance, you
may need to provide values for the additional parameters shown in tables 12-3
through 12-8.

Table 12-4. Rich client optional parameter values

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

Table 12-4. Rich client optional parameter values

FMSProxyHTTPPort Number of port for HTTP proxy server for File
Management System (FMS) communication. If you
do not specify a port number, the rich client does not
communicate with FMS using an HTTP proxy server.
To configure an HTTP proxy server, you must
also specify a value for the FMSProxyHTTPHost
parameter.
FMSProxyHTTPSHost Name of HTTPS proxy server host for File
Management System (FMS) communication. If
you do not specify a host, the rich client does not
communicate with FMS using an HTTPS proxy
server.
To configure an HTTPS proxy server, you must
also specify a value for the FMSProxyHTTPSPort
parameter.
FMSProxyHTTPSPort Number of port for HTTPS proxy server for File
Management System (FMS) communication. If you
do not specify a port number, the rich client does
not communicate with FMS using an HTTPS proxy
server.
To configure an HTTPS proxy server, you must
also specify a value for the FMSProxyHTTPSHost
parameter.
Table 12-5. Teamcenter’s lifecycle visualization (embedded viewer) parameter and

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

Table 12-6. Teamcenter’s lifecycle visualization (stand-alone application viewer)

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

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

CMSWebAppServerTable The list of the location(s) of the Content Management web
server(s). The entries correspond to the associated Teamcenter
URI sequences. Leave the field blank if the Teamcenter URI
does not have a corresponding Content Management Web
Server URL.

Install a rich client distribution instance

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

insweb

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

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

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

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

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

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

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

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

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

Note
• For descriptions of the rich client required parameters, see table 12-3.
The other required parameters vary, depending on the applications
you are installing with the rich client instance. For descriptions, see
tables 12-5 through 12-7.
• The required parameters must have values specified. If a required

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

Table Description
ParentFSCAddressTable Type a list of addresses (host name and port) of the
FMS file server caches (FSC) to act as the parents
of the installed FMS file client cache.
For information on the FMS file client cache
and FMS file server cache, see Installing File
Management System.
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
graphical user interface.
16. When you complete each table, click OK.

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

(named in step 6).
The manifest file records and maintains information about the rich client
image files, including a list of the files and a version for each file. The
Over-the-Web Installer consults the manifest file to determine which files
to download.
17. When the Progress dialog box indicates that installation is complete, click OK.
Manager dialog box.
18. If you want to configure the optional Security Services, ensure that the rich client
distribution instance is selected in the Web Applications box and click Modify.
The Web Application Manager displays the Modify Web Application dialog box.
19. Click Modify Context Parameters.

Web Application Manager displays the Modify Context Parameters dialog box.
20. Type values for the optional parameters and click OK.

Note
For descriptions of the optional parameters, see table 12-4.
21. Click OK.

Manager dialog box.
Repeat this procedure for each additional rich client distribution instance you want
to create.
Deploying the distribution instance

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

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

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

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

automatically.
– 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 directory there. For detailed deployment
information, see the documentation for the Web server. The following examples use
the name of the instance for the Web component directory name:

Web server Deployment

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

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

directory.
4. Publish the following URL:

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



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

directory.

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

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

directory.


Web server Deployment

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

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

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’s lifecycle
visualization or NX, the locations in which users must install Teamcenter’s
lifecycle visualization and NX.
Start and stop the rich client distribution server

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

1. Go to the staging location directory you created for the distribution server.
This is the directory containing the distribution server application and
administration utilities.
2. In the webapp_root subdirectory find and run the start_rmi program file.
The start_rmi program file starts the Java remote method invocation (RMI)
registry.
3. In the webapp_root subdirectory, find and run the start_server program file.
The start_server 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 using the control-C
keys on the distribution server console. 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 program file and the dist_server.jar file in the webapp_root
subdirectory of the distribution server staging location. To stop the distribution
server, enter the following command:
stop_server host-name:port-number
Replace host-name with the name of the computer where the distribution server is
running. Replace port-number with the port number.
The stop_server program prints the results of the remote shutdown. If the
results include Java exceptions, errors occurred. Usually exceptions occur when no
distribution server is running on the specified host.
To stop the RMI registry, use the operating system facilities.
The operating system facilities stop the RMI registry server.
Managing the rich client distribution server and instances

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

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

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

1. Launch the Web Application Manager:

insweb


Manager dialog box.
2. Click Copy ICDs.

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

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

The Web Application Manager displays the Modify Disk Locations dialog box.
7. Ensure the paths to the installation images of components you want to add are
listed in the Disk Locations for Install Images box.
For example, if you intend to add the embedded viewer to the rich client, enter
the paths to the Teamcenter’s lifecycle visualization installation images for each
operating system.
Note
For each instance, the Over-the-Web Installer requires access to the
installation images files for all operating systems.
8. Click Add Solutions.

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

If the solution you are adding has required parameters, the Web Application
Manager displays the dialog boxes as necessary.
10. Provide the information for the required parameters and click OK.

Note
• For descriptions of the rich client required parameters, see table 12-3.
The other required parameters vary, depending on the applications
you are installing with the rich client instance. For descriptions, see
tables 12-5 through 12-7.
• The required parameters must have values specified. If a required

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

Part
VI Additional configuration and

maintenance
Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Localizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Installing Teamcenter maintenance packs . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Chapter
13 Managing installations and

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

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

Chapter
13 Managing installations and

configurations
A Teamcenter configuration is a collection of features associated with one Teamcenter

data directory. The collection of configurations that share the same Teamcenter
application root directory is a Teamcenter installation.
When you installed Teamcenter executables using Teamcenter Environment
Manager from the software distribution image, you created the first configuration.
You can create a new Teamcenter configuration or modify features in your existing
Teamcenter configuration using Teamcenter Environment Manager.
Create a configuration
1. Start Teamcenter Environment Manager:
a. Access the install directory in the Teamcenter application root directory for
the Teamcenter installation or configuration you want to modify.

Teamcenter Environment Manager displays the Select Configuration panel.
2. In the Select Configuration panel, choose the Create new configuration option
and click Next.
Teamcenter Environment Manager displays the Configuration panel.
3. Enter a description of and unique ID for the configuration you are creating and
click Next.
Teamcenter Environment Manager displays the Select Components panel.
4. Select the components to include in the configuration and click Next.

From this point, the procedure is the same as for the first configuration in an
installation. Teamcenter Environment Manager displays additional panels
depending on the components you are including in the configuration.
5. When Teamcenter Environment Manager displays the Confirm Selections

panel, click Next to begin installation.

Chapter 13 Managing installations and configurations
Modify a configuration
Add Teamcenter features to an existing configuration, or remove them from a
configuration:
1. From the install directory of the Teamcenter application root directory of the
configuration, start the tem.sh program.
2. From the Select Configuration panel, choose the Perform maintenance on an

existing configuration option.
3. From the list of configurations, select the configuration you want to modify and
click Next.
Teamcenter Environment Manager displays the Configure Components panel.
4. Select the Add/Remove Features option and click Next.

Teamcenter Environment Manager displays the Select Components panel.
The components with a checkmark are installed with the configuration. The
components without a checkmark are not installed with the configuration.
5. To add a feature, select it; to remove a feature, deselect it. Click Next.
If a feature you are adding requires additional information, Teamcenter
Environment Manager displays additional panels.

panel, click Next 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.
Because you are using a database already configured for Teamcenter, you need not
install File Management System and Teamcenter File Services.
The Teamcenter data directory you want to reference must exist.
1. In the install directory of the Teamcenter application root directory of the
2. In the Select Configuration panel, choose the Create new configuration option.
3. In the Configuration panel, enter a description of and unique ID for the

configuration you are creating.
4. In the Select Components panel, select the Teamcenter Foundation component

only.
5. In the Configure Data panel, select Connect to an existing data directory and
enter the full path to the existing data directory in the Data Directory Location
box.

Managing installations and configurations
6. In the Confirm Selections panel, review your selections and click Next 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 Teamcenter File
Services and create a data directory.
Prerequisites:
• A database server must be installed, either Oracle Server or MS SQL Server.
• A database instance must exist, either a specific instance configured for

Teamcenter or a multipurpose instance to be configured in this procedure.
For information about installing a database server and database instances, see part
II, Database server installation.
1. In the install directory of the Teamcenter application root directory of the
2. In the Select Configuration panel, choose the Create new configuration option.
3. In the Configuration panel, fill in the description and ID for the new
configuration.
4. In the Select Components panel, select the following components:

File Management System
5. In the Configure Data panel, select Create new data directory and fill in the
Data Directory Location box with the path to a new data directory.
6. In the Database Configuration panel, fill in the values to create a new database.
7. In the Volume Specification panel, fill in the values to create a Teamcenter

volume for this database.
8. Fill in the Transient Volume Settings panel.
9. Fill in the FSC Service panel.
10. Fill in the FSC Master Settings panel.
11. Fill in the TCFS Service panel.

panel, click Next to add the database.

Configure multiple databases for a four-tier rich client

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

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

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

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

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

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

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

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

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

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

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

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

TreeCache cluster name: TreeCache cluster name:
TreeCache mode: TCP TreeCache mode: TCP
Note
Make sure you choose distinct sets of ports for each EAR file.
3. Deploy each Web tier EAR file in a third-party application server in a separate
domain.

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

Chapter
14 Localizing Teamcenter
Configure rich client language display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Environment settings for non-English locales . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Deploying thin client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Update thin client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Create a thin client localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Convert the thin client user interface for Hebrew . . . . . . . . . . . . . . . . . . . 14-5
Deploying rich client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5

Display Siemens PLM Software-provided rich client localizations . . . . . . . 14-5
Update rich client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5

Chapter
14 Localizing Teamcenter
Configure and deploy localized versions of Teamcenter.
Configure rich client language display

By default, the rich client displays in the language specified by your operating
system settings.
If you change your operating system locale, to ensure the rich client interface is
updated with the new locale, delete the Teamcenter directory in your user directory
($HOME/Teamcenter).
If you want the rich client user interface to display in a different language than
the operating system, you can override the client workstation’s locale setting by
performing the following steps:
1. Close any open rich client sessions.
2. Open the TC_ROOT/portal/teamcenter.ini file in a plain text editor.
3. Add the following line to the beginning of the teamcenter.ini file:

-nl
language-identifier
Replace language-identifier with the appropriate code for your intended locale:
Language Code
Chinese (Simplified) cn
Chinese (Traditional) tw
English en
French fr
German de
Italian it
Japanese jp
Korean kr
Russian ru
Spanish es

Chapter 14 Localizing Teamcenter
For example, if your client workstation’s locale is set to German, you can set the
rich client user interface to display in English by adding the following line to
the teamcenter.ini file:
-nl
en
4. Save the changes to the teamcenter.ini file.
5. Change to your user home directory ($HOME) and delete the Teamcenter
directory.
6. Restart the rich client.
Environment settings for non-English locales

For non-English locales on UNIX systems, you must specify the system locale by
setting the LANG and LC_ALL environment variables using the Common Desktop
Environment (CDE). These two variables must be identical to function properly.
Set the LANG and LC_ALL environment variables to the values shown in table
14-1.
Table 14-1. UNIX Environment Settings for Non-English Locales

Language Operating System Character Set Value of LANG and LC_ALL
French IBM AIX ISO8859–1 fr_FR or fr_FR.ISO8859–1
Hewlett-Packard HP-UX ISO8859–1 fr_FR.iso8859
Sun Solaris ISO8859–1 fr or fr_FR or fr_FR.ISO8859–1
German IBM AIX ISO8859–1 de_DE or de_DE.ISO8859–1
Hewlett-Packard HP-UX ISO8859–1 de_DE.iso88591
Sun Solaris ISO8859–1 de or de_DE or
de_DE.ISO8859–1
Hebrew IBM AIX ISO8859–8 iw_IL or iw_IL.ISO8859–8
Hewlett-Packard HP-UX ISO8859–8 iw_IL.iso88598
Sun Solaris ISO8859–8 he or he_IL
Italian IBM AIX ISO8859–1 it_IT or it_IT.ISO8859–1
Hewlett-Packard HP-UX ISO8859–1 it_IT.iso88591
Sun Solaris ISO8859–1 it or it_IT or it_IT.ISO8859–1
Russian IBM AIX ISO8859–5 ru_RU or ru_RU.ISO8859–5
Hewlett-Packard HP-UX ISO8859–5 ru_RU.iso88595
Sun Solaris ISO8859–5 ru or ru_Ru or ru_RU.ISO8859–5

Localizing Teamcenter
Table 14-1. UNIX Environment Settings for Non-English Locales

Language Operating System Character Set Value of LANG and LC_ALL
Spanish IBM AIX ISO8859–1 es_ES or es_ES.ISO8859–1
Hewlett-Packard HP-UX ISO8859–1 es_ES.iso88591
Sun Solaris ISO8859–1 es or es_ES or es_ES.ISO8859–1
Japanese IBM AIX JEUC ja_JP
IBM AIX SJIS Ja_JP
Hewlett-Packard HP-UX JEUC ja_JP.eucJP
Hewlett-Packard HP-UX SJIS ja_JP.SJIS
Sun Solaris JEUC ja or japanese
Sun Solaris SJIS ja_JP.PCK
Korean IBM AIX KS C ko_KR
Hewlett-Packard HP-UX KS C ko_KR.eucKR
Sun Solaris KS C ko or korean
Simplified IBM AIX GB2312-80 zh_CN
Chinese
Hewlett-Packard HP-UX GB2312-80 zh_CN.hp15CN
Sun Solaris GB2312-80 zh
Traditional IBM AIX BIG5 zh_TW
Chinese
Hewlett-Packard HP-UX BIG5 zh_TW.big5
Sun Solaris BIG5 zh_TW.BIG5
Deploying thin client localizations

Use the Web Application Manager to build a localized Teamcenter thin client.
Update thin client localized text

The thin client text server files reside under the Teamcenter application root
directory in the /lang/textserver/language-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\htdocs\tc\intl\ directory in the Teamcenter application
root directory.
2. Copy the web_gen_xml.dat file to the

Web_tier/staging-location/webapp_root/intl/directory.
3. Change to the Web_tier/staging-location/webapp_root/intl/directory.

4. Run the web_gen_xml utility that uses the web_gen_xml.dat as input.

This utility creates a webstrings.xml file that contains the new language string
translations.
5. Copy the webstrings.xml file to the language directory.
6. Regenerate the Web tier application (file-name.ear) and deploy in an application

server.
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/ directory.
For example, if you localize the user interface for Hebrew, create the he directory.
2. Copy all files from the en directory to the new language directory.
3. In the new language directory, translate all XML files to the new language.
4. Edit the weblocal.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";
Caution
Do not change the web_char_encoding parameter from UTF-8. All
languages must be UTF-8 encoding.
5. Change to the Web_tier\staging_location\webapp_root\intl\ directory

and create a new language directory.
For example, if you localize the user interface for Hebrew, create the he directory.
6. Copy all files from the en directory to the new language directory.
7. In the new language directory, translate all XML files to the new language.
8. Regenerate the webstrings.xml file:

a. Change to the \web\htdocs\tc\intl\ directory in the Teamcenter
application root directory.
b. Copy the web_gen_xml.dat file to the

Web_tier/staging-location/webapp_root/intl/directory.
c. Change to the Web_tier/staging-location/webapp_root/intl/directory.
d. Run the web_gen_xml utility that uses the web_gen_xml.dat as input.

This utility creates a webstrings.xml file that contains the new language
string translations.

Localizing Teamcenter
e. Copy the webstrings.xml file to the language directory.
9. Regenerate the Web tier application (file-name.ear) and deploy 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.
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 a localized Teamcenter rich client.
Display Siemens PLM Software-provided rich client localizations

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

If you change the strings of a localized rich client user interface contained in the
portal_localization.jar file, 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 SDK 1.4. For more
information, access the following URL:
http://java.sun.com/j2se/1.4/docs/tooldocs/win32/native2ascii.html
For example, to convert the properties file from Japanese to Unicode, enter the
following command from the command line:
native2ascii -encoding SJIS aif_locale_temp.properties aif_locale_ja_JP.properties
The final locale-specific properties file or the output of the native2ascii file must
have the base_locale_locale-id_language-id.properties file format.
The rich client finds the value of a key in the following order:
BASE_user.properties
BASE_locale-ID_language-ID.properties
BASE_locale.properties
BASE.properties
5. Recompile the JAR file.
6. Install fonts if necessary.

For information about fonts, access the following URL:
http://java.sun.com/j2se/1.4/docs/guide/intl/font.html
For additional information, access the following URL:

http://www.unicode.org/

Chapter
15 Silent installation
Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . 15-2

Chapter
15 Silent installation
As an alternative to installing and configuring Teamcenter on individual hosts in

your network, you can install Teamcenter servers or two-tier rich clients silently,
using a preconfigured installation program. Silent installation suppresses most
installation prompts and requires minimal user interaction.
Capture, manage, and launch a silent Teamcenter installation using Teamcenter
Environment Manager.
Create a silent installation configuration file

1. Log on to the Teamcenter corporate server host and change to the root directory
of the Teamcenter software distribution image.
2. Start Teamcenter Environment Manager (tem.sh) from the Teamcenter software

distribution image.
3. In the Getting Started panel, select the Set up a silent installation distribution
check box. Click Next in the following panels until you reach the Silent
Installation panel.
4. In the Silent Installation panel, in the Silent Configuration File box, specify the
path to the silent installation file, for example, silent.xml. The specified path
must be to an existing directory and the file name must end in .xml.
5. Proceed through the remaining panels to complete the Teamcenter installation.

Teamcenter Environment Manager creates the silent installation file you
specified in step 4. This file records your settings and selections during the
installation. You can use this file to silently install Teamcenter on another host
with the same settings.
Launch a silent installation

To launch a silent installation on another host, type the following command:
tem.sh –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.

Chapter 15 Silent installation
Modify the silent installation configuration file

The silent installation configuration file is XML-based (figure 15-1). 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 in the file (table 15-1).
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.
Table 15-1. Silent installation XML elements

Element Description
moduleset Lists all the Teamcenter modules and features that
Teamcenter Environment Manager can install. These are
the modules and features listed on the Select Features
panel of Teamcenter Environment Manager.
module Specifies one Teamcenter module. The code attribute
identifies the module. To define whether Teamcenter
Environment Manager installs the module, set the
selected attribute to either true or false.
feature Specifies one feature of a Teamcenter module. The
code attribute identifies the feature. To define whether
Teamcenter Environment Manager installs the feature, set
the selected attribute to either true or false.
data Lists all Teamcenter Environment Manager Java classes
and values defining aspects of installation, such as the path
to the installation directory for Teamcenter application
files. For additional information, see the comments in the
configuration file. The comments describe the class and
valid values.

Silent installation
<?xml version="1.0" encoding="UTF-8"?>

<config>
<control>
<moduleset>
<module code="tem" installed="false" selected="true">
<feature code="temcore" installed="false" selected="true" currentstep="0" />
</module>
<module code="fnd" installed="false" selected="true">
<feature code="fndbase" installed="false" selected="true" currentstep="0" />
<feature code="fndportal" installed="false" selected="true" currentstep="0" />
<feature code="fndfms" installed="false" selected="true" currentstep="0" />
<feature code="fndhelp" installed="false" selected="false" currentstep="0" />
<feature code="fndsso" installed="false" selected="false" currentstep="0" />
<feature code="fndfts" installed="false" selected="false" currentstep="0" />
<feature code="fndmultisite" installed="false" selected="false" currentstep="0" />
<feature code="fndflex" installed="false" selected="false" currentstep="0" />
<feature code="fndsm" installed="false" selected="false" currentstep="0" />
<feature code="fndclear" installed="false" selected="false" currentstep="0" />
<feature code="fndets" installed="false" selected="false" currentstep="0" />
<feature code="fndkbl" installed="false" selected="false" currentstep="0" />
<feature code="fndsamp" installed="false" selected="false" currentstep="0" />
</module>
<module code="cad" installed="false" selected="true">
<feature code="cadnxug" installed="false" selected="true" currentstep="0" />
</module>
<module code="linking" installed="false" selected="false">
<feature code="linking" installed="false" selected="false" currentstep="0" />
</module>
<module code="rdv" installed="false" selected="false">
<feature code="rdvcore" installed="false" selected="false" currentstep="0" />
</module>
<module code="tcae" installed="false" selected="false">
<feature code="tcaecore" installed="false" selected="false" currentstep="0" />
<feature code="tcaegmo" installed="false" selected="false" currentstep="0" />
</module>
</moduleset>
</control>
<data>
<com.teamcenter.install.tem.struct.Repository>

<rootDir value="e:\Program Files\Siemens\Teamcenter8" />

<shortRootDir value="e:\Program Files\Siemens\Teamcenter8" />
</com.teamcenter.install.tem.struct.Repository>
<com.teamcenter.install.tceng.struct.TcengRepository>

<dataUser value="infodba" />

<dataPassword value="infodba" />

<dataDir value="e:\Program Files\Siemens\Teamcenter8\teamcenterdata" />

<shortDataDir value="E:\PROGRA~1\Siemens\TEAMCE~1" />

<dataCreateTcdata value="false" />

<encodingSetting value="ISO8859_1" />

<helpDirect value="true" />

<helpPath value="" />

<helpWeb value="false" />

<helpUrl value="" />
</com.teamcenter.install.tceng.struct.TcengRepository>
Figure 15-1. Sample silent installation configuration file (Continued)

Chapter 15 Silent installation
<com.teamcenter.install.tceng.struct.Volume>

<volumeNeeded value="false" />
<volumeName value="volume1" />
<volumeHost value="cii3w098" />

<volumeLocation value="" />

<transientVolLoc value="e:\Program Files\Siemens\Teamcenter8\TransientVolume" />

<transientVolName value="TransientVolume" />
</com.teamcenter.install.tceng.struct.Volume>
<com.teamcenter.install.tceng.struct.Sfms>

<sfmsNeeded value="false" />

<sfmsRunLocal value="true" />
<sfmsPort value="1528" />

<sfmsUser value="" />
<sfmsPassword value="" />
</com.teamcenter.install.tceng.struct.Sfms>
<com.teamcenter.install.tceng.struct.Fms>

<installFsc value="false" />

<serverID value="FSC_AcmeCorp" />

<fscPort value="4444" />

<fscReadCache value="$HOME/FSCCache" />

<fscWriteCache value="$HOME/FSCCache" />

<specifyMaster value="false" />

<fscMasterHost value="cii3w098" />

<fscMasterPort value="4444" />

<fccCache value="e:\Program Files\Siemens\Teamcenter8\FCCCache" />
<fccWriteCacheSize value="100" />
<fccReadCacheSize value="100" />

<fccParentFscHost value="AcmeCorp" />
<fccParentFscPort value="4444" />
</com.teamcenter.install.tceng.struct.Fms>
</data>
</config>
Figure 15-1. Sample silent installation configuration file

Chapter
16 Installing Teamcenter patches
Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Patching Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Install patches on the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Patch the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Patch the rich client silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Patch the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . 16-4
Patch Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Patch the distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Patch the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8

Chapter
16 Installing Teamcenter patches
On Teamcenter servers and two-tier rich clients, you install patches using the
Updates Manager, a feature of Teamcenter Environment Manager (TEM). Patches
to the Teamcenter J2EE Web tier you install using the Web Application Manager.
Teamcenter updates (maintenance packs and patches) are posted for download on
GTAC when available.
Distribution of Teamcenter updates

Teamcenter 8 updates are delivered in patches and in maintenance packs (MP).
Patches to Teamcenter servers and two-tier rich clients are applied using the
Updates Manager in Teamcenter Environment Manager (TEM). Patches to the
J2EE Web tier and over-the-Web (OTW) distribution servers are applied using the
Web Application Manager.
Note
Maintenance packs require special configuration steps similar to an upgrade.
For information about applying maintenance packs, see the Upgrade Guide.
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_platform.zip
Contains the Teamcenter Visualization patches
Downloading Teamcenter patches

1. Locate the patches you want to apply in the Product Updates area on GTAC.
2. Download the patch files to a temporary location on your host.

Note
Make sure you download the appropriate patch file for your platform.

Chapter 16 Installing Teamcenter patches
Before you apply downloaded Teamcenter 8 patches to your server, you must do
the following:
• Install the base Teamcenter 8 release.
• Stop all Teamcenter 8 related processes and services (such as TCFS, FSC,
database daemons, and so on).
• If your server configuration includes a two-tier rich client with Engineering

Process Management Visualization, uninstall this feature using TEM.
Patching Teamcenter Environment Manager

1. If the patch you downloaded contains an updated installer file (install.zip),
extract this file into your installed Teamcenter environment to update
Teamcenter Environment Manager (TEM) to the latest version:
a. Copy the install.zip file to your TC_ROOT/install directory.
b. Open a command prompt.
c. Change to the TC_ROOT/install directory.
d. Enter the following command to extract the install.zip file, overwriting

existing files:
unzip –o install.zip
Note
If errors occur while extracting the file, do one of the following tasks:
• Add the path to your TC_ROOT/install directory to your PATH
environment variable and enter the unzip command again.
• Enter the unizip command with the full path to your

TC_ROOT/install directory, for example:
TC_ROOT/install/install/unzip –o install.zip
e. Add execute permissions back to the tem.sh shell script with the following
command:
chmod 755 tem.sh
Install patches on the corporate server

1. Launch TEM (TC_ROOT/nstall/tem.sh).
2. In the Maintenance panel, choose Updates Manager and click Next.
3. In the Apply Updates panel, enter the location of the patch file you downloaded
in the Update file box. Click Next.

Installing Teamcenter patches
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 Teamcenter
services or processes are running, the update may fail because TEM
cannot copy replacement files from the patch to the installed location.
4. In the Confirm Selections panel, click Next to begin patching the server.
5. Once the server is successfully patched, you must manually update your
TC_DATA directories.
a. Create a backup of your current TC_DATA directories.
b. Extract the Teamcenter8\data directory from the

Teamcenter8_MPnumber_platform.zip file and copy the contents to your
TC_DATA directories.
c. Copy the tc_profilevars file from the backup to the TC_DATA. directory.
6. Follow the instructions in the patch’s README file for any additional steps
required to complete the patch.
Restart all Teamcenter-related processes and services (such as TCFS, 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.
Update your database’s version information:

1. Open a Teamcenter command prompt.

install —set_version “INFORMATION MANAGER VTeamcenter-version”
Replace Teamcenter-version with the full version and patch level of the
Teamcenter installation. If you are not sure what value to use, contact your
Teamcenter support representative.
Patching the rich client

There are two multiple for patching the rich client. Choose a patching method
according to how you installed the client. If you installed the rich client during your
server installation with the TEM, follow the steps in Patch the rich client using
TEM. If you installed the rich client using the Over-the-Web Installer distribution
server with one or more distribution server instances, patch each distribution server
instance by following the steps in Patch the rich client using the Over-the-Web

Installer. To patch Lifecycle Visualization using the Over-the-Web Installer, follow

the steps in Patch Lifecycle Visualization.
Note
If the patch you downloaded contains a file named portal_patch.jar that
is empty, this is intentional. This file is obsolete and is provided only as a
placeholder.
Patch the rich client using TEM

Patch the rich client using the steps in Install patches on the corporate server. If the
rich client was installed as a part of the same environment as the corporate server,
the rich client is updated at the same time as the corporate server.
Patch the rich client silently

Teamcenter Environment Manager allows you to install patches silently, with no
prompts or user interface:
1. Open a command prompt.
2. Change to the TC_ROOT/install directory.

tem.sh –p "patch-path/Teamcenter8_mpnumber_platform.zip"
Replace patch-path with the path to the downloaded maintenance pack. Replace
number with the maintenance pack ID and platform with the platform identifier.
This procedure launches TEM and applies the patch with no user interaction
required.
Note
You must enclose the path to the patch in quotation marks (") for paths that
contain spaces in them. For example:
tem.sh —p "/../Teamcenter patches/Teamcenter8_mpnumber_platform.zip"
Patch the rich client using the Over-the-Web Installer

The patch files for any rich client installed using the OTW installer are in the
Teamcenter8_MPnumber_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 Teamcenter8_MPnumber_OTW.zip file to your
computer.
2. Shut down the distribution server.

4. Click the Copy ICD button. Browse to the expanded patch location to select the
icd directory, and then click OK to copy the ICD files to the Web Application
Manager.
5. Select the installed rich client instance you want to patch and click Modify.
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 MP patch Additional MP patches

a. Click Add Solutions. a. Click Reinstall Solutions.
b. Select Rich Client Patch and click b. In the Reinstall Solution dialog
OK. box, click OK.1
c. In the Modify Web Application c. In the Confirm dialog box, click

dialog box, click OK to begin Yes.
patching.
d. In the Modify Required Context
d. After the patch is installed, click Parameters dialog box, click OK to
OK to close the Progress dialog begin patching.
box.
e. After the patch is installed, click
OK to close the Progress dialog
box.
9. In the Modify Web Application dialog box, click OK.
10. Exit the Web Application Manager.
11. 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 Lifecycle Visualization

1. Download Lifecycle Visualization patches for all platforms:
• Teamcenter8_MPnumber_PV_aix.zip
• Teamcenter8_MPnumber_PV_hpp.zip
1. Adding patches reinstalls the patch solution with the newer files.

• Teamcenter8_MPnumber_PV_sol.zip
• Teamcenter8_MPnumber_PV_win.zip
2. Extract all ZIP files into a single directory. If prompted, overwrite all files.
3. If the MP contains an updated installer file (install.zip), extract this file to the
WEB_ROOT directory to update the Web Application Manager to the latest
version.
4. Follow the steps in Patch the rich client using the Over-the-Web Installer with the
following exceptions:
a. In step 5, select the instance that contains the Engineering Visualization
Patch.
b. In step 8, select the Engineering Visualization (Install and Configure)

solution.
c. Repeat steps 5 through 9, selecting the instance that contains the

Teamcenter Visualization (Install and Configure) solution and selecting the
Teamcenter Visualization solution.
Patch the distribution server

If you have an over-the-Web rich client distribution server set up, you have to extract
the INSTALL_TCWEB.TZ/EXE image from the Teamcenter software distribution
image to a local directory on your machine and then run the Web Application
Manager (insweb) from that local directory. During that setup, you installed the
distribution server itself to a staging location in the Web Application Manager,
designated as STAGING_LOC.
1. Unzip the Teamcenter8_MPnumberrc_otw_common.zip file to the
OTW_MP_LOC temporary directory.
2. Shut down your running distribution server.

a. In a command prompt, change the directory to the
STAGING_LOC\webapp_root directory where your distribution server is
installed.
b. Type the following command:

stop_server host:rmi_port
Replace host with the name of the host where you have the RMI registry and
distribution server running and rmi_port with the port number that you
used for starting the RMI registry (the default is 12099).
c. If the shutdown is successful, you should see output similar to the following
in your console where you issued the start_server command:
Loading of com.teamcenter.install.otw.common.TextBundle_en_US ...
attempted.
Loading of com.teamcenter.install.otw.common.TextBundle succeeded.
Shutdown() call successful

3. Copy the OTW_MP_LOC\dist_server.jar file to the

STAGING_LOC\webapp_root directory.
4. Restart your distribution server.

a. In a console window, change the directory to the
STAGING_LOC\webapp_root directory.
b. Run start_server.
c. Your distribution server should restart with the patches applied.
Patch the Web tier

To install the Web tier, you must extract the INSTALL_TCWEB.TZ/EXE image
from the base release CD to a local directory on your machine and then run the Web
Application Manager (insweb) from that local directory. You then must generate a
deployable (EAR or WAR) file and deploy that file on your Web application server.
The local directory in which you ran the Web Application Manager utility is called
WEB_ROOT.
The patch files for a Web Tier installation are in one of two places. They
are in the TC_ROOT\additional_patch_info\Web_tier directory if the
files were put there as TEM was patching the server or the files are in the
Teamcenter8_MPnumber_platform.zip file. If you have not patched the server,
access the files by unzipping the patch file contents to a temporary location, referred
to as PATCH_LOC.
Note
Because the files can be in either place, the location is referred to as
WEB_FILES_LOC in this procedure.
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).
3. Click Copy ICDs.
4. Browse to the WEB_FILES_LOC\Web_tier\icd directory and click OK.
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, select the solutions that you want to patch
and click OK.
The information on which solutions need to be patched for a particular MP
release should be listed in the Special Release Notes section of the README
document in the release_info directory.
12. If the Modify Required Context Parameters dialog box appears, type the
appropriate values for any required context parameters and click OK.
13. The Web Application Manager regenerates the Web tier web application with
the patched files. Make sure a deployable file (EAR or WAR) is generated
during this process. If it is not, click Generate Deployable File in the Modify
Web Application dialog box.
14. After the deployable file is generated, go to the Web tier Web application’s staging
directory and find the deployable file (EAR or WAR) under the deployment
directory.
15. Take the new deployable file and deploy it to your Web application server,
replacing the previous deployment. The new deployable file contains the Web
tier patches.
Review the README file

The README file in the release_info directory contains the following information:
• A list of problem reports (PRs), with short descriptions, fixed in this MP release.
• A list of patched files that are related to each PR fix.
• A Special Release Notes section that has additional steps you need to take to
apply various patches or additional information on what configuration needs to
be performed for the patches.
Review this README file to determine if you need to take additional action after
patching your files.

Chapter
17 Installing Teamcenter
maintenance packs

Chapter
17 Installing Teamcenter
maintenance packs
Teamcenter maintenance packs (MPs) are issued for Teamcenter releases and made
available for download on GTAC. MPs can be installed two ways:
• Applied to an existing Teamcenter installation
Maintenance packs contain the latest cumulative set of product updates,
including patches and enhancements, to be applied to an existing Teamcenter
installation as a single package.
• Full installation
A maintenance pack contains a complete Teamcenter installation package and
can be installed on a host with no existing Teamcenter software.
To install a maintenance pack as a complete new Teamcenter installation, perform

the procedures in this guide, beginning with Getting started.
To apply a maintenance pack to an existing Teamcenter installation, perform the
procedures in the Upgrade Guide. When selecting a path in the Getting Started
panel in Teamcenter Environment Manager (TEM), choose Install an MP to an
existing installation.

Chapter
18 Uninstalling Teamcenter
Uninstall Teamcenter configurations and installations . . . . . . . . . . . . . . . . . . 18-1
Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

Chapter
18 Uninstalling Teamcenter
If you need to uninstall a Teamcenter installation, remove Teamcenter configurations

using Teamcenter Environment Manager. You can then remove your database server.
Uninstall Teamcenter configurations and installations

Teamcenter Environment Manager uninstalls Teamcenter configurations. To
uninstall a Teamcenter installation, you must individually uninstall each
configuration in any order. If you have only one configuration, selecting it uninstalls
the Teamcenter installation.
1. Start Teamcenter Environment Manager:
a. Access the install directory in the Teamcenter application root directory for
the Teamcenter installation or configuration you want to uninstall.

Teamcenter Environment Manager displays the Select Configuration panel.
2. Select Perform maintenance on an existing configuration.
3. Select the configuration to uninstall from the displayed list.
4. Click Next.
Teamcenter Environment Manager displays the Configure Components panel.
5. Select Uninstall Teamcenter and click Next.

Note
Teamcenter Environment Manager uninstalls only the configuration you
selected.
Teamcenter Environment Manager displays the Uninstall panel.
6. Select Yes to confirm uninstallation and click Next.

If the configuration includes Teamcenter Foundation, Teamcenter Environment
Manager displays the Uninstall Teamcenter Foundation panel.
7. If this configuration of Teamcenter Foundation includes a unique database,

data directory, or volume directory, indicate whether you want to uninstall
them and click Next.
Teamcenter Environment Manager displays the Confirm Selections panel.

Chapter 18 Uninstalling Teamcenter
8. After checking the selections for uninstallation, click Next to begin the process.
Teamcenter Environment Manager removes the selected Teamcenter
configuration.
If the uninstallation is not successful, Teamcenter Environment Manager stops
processing when it encounters the error and displays a message indicating the
location of the log file containing the error.
9. If you selected the option in TEM to remove the Teamcenter database, the
database is moved to the Oracle10g recycle bin. To permanently remove the
database, launch SQL*Plus and enter the following command:
PURGE RECYCLEBIN;
Uninstall Oracle
For information about uninstalling Oracle, see the Oracle10g Installation Guide on
the Oracle 10g CD-ROM.

Part
VII Appendixes
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Appendix
A Glossary

Appendix
A Glossary
Application Interface Web Service

Teamcenter extensions to a Web service such as gSOAP or WebLogic. These
extensions allow Teamcenter to share data in a collaboration context with another
application. Application Interface Web Service includes a SOAP server. Application
Interface Web Service components are installed and deployed as part of the Web tier.
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, such as Teamcenter’s Integration for
Microsoft Office and Teamcenter Engineering 2007 Integration for AutoCAD, and
the third-party applications themselves, such as Microsoft Office and AutoCAD.
Connector
See Global Services Connector.
Connector to Enterprise Knowledge Management

Enterprise JavaBean that connects Global Services with Enterprise Knowledge
Management. The optional connector to Enterprise Knowledge Management is
provided as a part of the Global Services connectors.
PLM00011 C Installation on UNIX and Linux Servers Guide A-1

Appendix A Glossary
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.
Corporate Server
Host computer at the center of a Teamcenter network. This host contains the
Teamcenter application root directory, Teamcenter data directory, licensing, file
managers (Teamcenter File Services and File Management System), and volumes.
For installations that include the Web tier (four-tier architecture), the corporate
server also contains the Teamcenter server manager. Multiple application clients
can map to or mount the corporate server.
Distribution Server
See Rich Client Distribution Server.
Distribution Server Instance

See Rich Client Distribution Server Instance.
eIntegrator Admin
Teamcenter application that provides a simple integration mechanism you can use
to integrate external data with Teamcenter. eIntegrator Admin maps external data
systems into equivalent objects in its database. The data can then be imported into
the database as forms.
eM-Planner Interface
Interface between Teamcenter’s 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.
A-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Glossary
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, 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’s 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

Appendix A Glossary
uploading files. As a configuration server, it provides FMS configuration information

to file client caches and other FSCs. As a transient server, it delivers PLM XML and
other transient files to clients. A minimum of one FSC must be deployed in any
Teamcenter installation. Multiple FSCs can be deployed, with each FSC performing
one designated purpose as either a volume, a cache, or a configuration server.
Four-Tier Architecture
Teamcenter architecture that includes four tiers: resource tier, client tier, Web tier,
and enterprise tier.
Four-Tier Deployment
Deployment of the Teamcenter four-tier architecture. The Web tier, enterprise tier,
resource tier, and client tier can each be hosted on the same or separate computers.
FSC
See FMS Server Cache (FSC).
FSC Configuration File

File that configures an individual FMS server cache (fsc.xml). The FSC
configuration file defines such values as the address of the master FSC, the
maximum sizes of the segment file caches, and the upload timeout value. It can also
define default values for FCCs and other FSCs.
FSC Group
Group of server caches defined in the FMS master configuration file.
Global Services Adapter

eIntegrator Admin adapter connects eIntegrator Admin to Teamcenter Global
Services, a Web-based application enabling clients to access information stored in
virtually any type of data source that manages site data.
Global Services Connector

Global Services component that accesses information from a data source through
an Enterprise JavaBeans component called a connector. Each connector accesses
information from a particular type of data source. For example, Production
Server provides a connector for communicating with JDBC-compliant databases.
Global Services offers optional connectors to Teamcenter, Enterprise Knowledge
Management, Oracle Manufacturing, and SAP. One implementation of a connector
can communicate with multiple data sources through the use of connector
configuration files.
Global Services Foundation

Web application that enables your enterprise to access information stored in
virtually any type of electronic data source that manages your enterprise data.
Running on a standard commercial Web application server, the server components
of Global Services Foundation enable communication among the data sources and
between users and the data sources. All components of Global Services Foundation
use standard Web technology: Extensible Markup Language (XML), Extensible
Stylesheet Language (XSL), and the Sun Java programming language. Users access
Global Services Foundation from a commercial Web browser using the standard
technologies of Web browsers, primarily support for HyperText Markup Language
(HTML) forms and small Java applets.

Glossary
Group Preference
Teamcenter preference applying to an entire group.
Heterogeneous Network Environment

Teamcenter network environment in which the database server, corporate server,
and Teamcenter clients are provided by multiple vendors and can be a mixture
of UNIX and Microsoft Windows nodes.
Compare with Homogeneous Network Environment.
Homogeneous Network Environment

Teamcenter network environment in which the database server, corporate server,
and all Teamcenter clients are provided by one vendor (for example, all Sun
Microsystems or all Dell systems).
Compare with Heterogeneous Network Environment.
I-deas
Siemens PLM Software’s integrated CAD/CAM/CAE solution that is used to design,
analyze, test, and manufacture products.
IDSM Server
Integrated Distributed Services Manager, a network node that runs a daemon process
to handle the transfer of data objects among sites in a Multi-Site Collaboration
network. One IDSM server node must be designated for each Teamcenter database
from which objects are published; each server node can act for one database only.
JT Cache
Data Integration Services Adapter cache of JT files managed by the JT cache service
and accessible to Teamcenter’s lifecycle visualization users. See also World Access
Cache and Limited Access Cache.
JT Cache Populator
Stand-alone Data Integration Services Adapter utility that prepopulates the JT
cache with JT part and assembly files.
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.

Appendix A Glossary
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.
Multi-Site Collaboration Network

Network of independent Teamcenter sites that are within the same enterprise and
share data using Multi-Site Collaboration.
My Teamcenter
Teamcenter rich client application that is the main access point for managing
product information. My Teamcenter provides the functionality for creating objects
in the Teamcenter database, querying the database for objects, checking in and
checking out objects, and managing tasks. Users can also open objects, automatically
launching the related application.
Each user has a personal My Teamcenter window that displays product information
as graphical objects. Although users share product information across the enterprise,
they organize this information individually in personal workspaces.
Naming Service
Service that maintains a list of names and the objects associated with them. For
the Teamcenter rich client, the naming service maintains a list of servers and the
objects and methods used by those services. The naming service is an integral part
of the server directory.
NS
See Naming Service.
NX Integration
Integration between Teamcenter and NX. NX Integration users have full access
to the Teamcenter user interface from NX, and they can also access NX from the
Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter

Glossary
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 Teamcenter Linking.
Object Directory Services Server

Multi-Site Collaboration network node that runs a daemon process to handle
publication of data objects within a Multi-Site Collaboration environment. One
ODS server node must be designated for each object directory services site and each
server node can act only for one object directory services site.
Object Directory Services Site

Site with the database that maintains a record of each object in a Multi-Site
Collaboration network. At least one Teamcenter database on a Multi-Site
Collaboration network must be designated as an ODS site. This site is used to store
publication records for the data objects.
Object Launcher
Launches another Teamcenter product from a linked object. Each Teamcenter
product has an object launcher. See also Teamcenter Linking.
ODBC Driver
Teamcenter integration that allows ODBC-compliant applications such as Actuate
Report Writer, Crystal Reports, Microsoft Excel, and Access to extract data from a
Teamcenter database for building reports.
ODS Server
See Object Directory Services Server.
ODS Site
See Object Directory Services Site.
Oracle Home
Directory in which Oracle software is installed on the Oracle server node.
Oracle Server
Single installation of Oracle able to service queries from several Teamcenter
workstations. The ORACLE_SERVER environment variable defines this Oracle
service node. For large-scale installations, the Oracle server is typically a dedicated
high performance workstation that is optimized specifically for running Oracle
software.
Oracle System Identifier (SID)

Alphanumeric word used to identify a collection of processes and associated memory
structures as belonging to a particular Oracle database instance. The ORACLE_SID
environment variable defines the Teamcenter-Oracle system identifier.
Over-the-Web Installer
Installation program that downloads the rich client software from a distribution
server instance to the user’s workstation over the Web.

Appendix A Glossary
Persistent Object Manager (POM)

Interface between Teamcenter objects and the Relational Database Management
System (RDBMS). The persistent object manager provides definition of classes
by inheritance from existing classes and definition of attributes, manipulation
of in-memory objects and support for their saving and retrieval to and from the
underlying RDBMS, support for applications accessing the same data concurrently,
protection against the deletion of data used by more than one application, and
support for the access control lists attributed to objects.
POM
See Persistent Object Manager (POM).
Preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many
aspects of a session, such as user logon names and the columns displayed by default
in a properties table.
Published Object
Object available to other sites in a Multi-Site Collaboration network. Publishing an
object creates a record in the ODS site database that can be read and searched by
other sites. Until an object is published, it can be seen only by the owning site.
QPL
See Quick Part Locator.
QPL Server
Quick part locator server. It provides a qpl daemon that can be used with
DesignContext in the rich client. The qpl daemon coexists with all Teamcenter
daemons. Without this daemon DesignContext does not work.
Quick Part Locator

Component of Repeatable Digital Validation (RDV) that creates and queries tables in
a Teamcenter database. The quick part locator enables rapid lookup of components
in an assembly. The tables cache precomputed results of location, attributes, and
spatial relationship of all components in a product assembly. The quick part locator
provides one of the search engines used by DesignContext.
RDV
See Repeatable Digital Validation.
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.

Glossary
Rich Client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server.
Rich Client Distribution Server

Software that manages the connection between distribution server instances, the
Web server, and the user’s workstation when a rich client is deployed over the Web.
The Over-the-Web Installer contacts the distribution server for the rich client files
to download to the user’s workstation.
Rich Client Distribution Server Instance

Rich client software to be installed on user’s workstations over the Web.
Administrators create one instance for each server.
Role Preference
Teamcenter preference applying to an entire role.
Security Services
Services that eliminate prompts for logon credentials when users switch Teamcenter
products within a user session. Authentication is performed by an external identity
service provider, such as lightweight directory access protocol (LDAP), instead of
the Teamcenter product. At a site that deploys multiple Teamcenter products and
Security Services, users log on once to access all participating Teamcenter products.
Server Manager
Process that manages a pool of Teamcenter server processes in a deployment of
the four-tier architecture. The server manager starts and times out a configurable
number of server processes to communicate with the Teamcenter database. A
server assigner process assigns available server processes to user sessions. The
server manager communicates with the Web tier application using either TCP or
multicast protocol.
Server Pool
Pool of Teamcenter server processes running in the enterprise tier. A small
deployment may have only one pool of server processes. For larger deployments, the
pool of server processes is distributed as subpools across multiple hosts, with a
server manager for each subpool. Server pools are applicable for deployments of the
Teamcenter four-tier architecture only.
Site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
networking capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site.
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.

Appendix A Glossary
Site Preference
Teamcenter preference that applies to the entire site.
Solid Edge Manager

Teamcenter integration that enables users to use Teamcenter to manage files from
within Solid Edge.
STEP Translator
Teamcenter application that enables users to import product information into a
Teamcenter database and to export Teamcenter data via STEP-compliant physical
files.
Supported Platform
Platform configuration supported by GTAC.
System Administrator
Teamcenter user who is a member of the system administration group.
TCFS
See Teamcenter File Services (TCFS).
Teamcenter’s Integration for Microsoft Office

Teamcenter integration that enables users to browse Teamcenter directly and create
objects in Teamcenter, check objects in and out of Teamcenter, and save files in
Teamcenter. The Teamcenter’s Integration for Microsoft Office consists of ActiveX
controls plugged into Microsoft Office.
Teamcenter’s lifecycle visualization

Siemens PLM Software suite that provides enterprise-wide product visualization
capabilities. Teamcenter’s lifecycle visualization can be configured for use with both
the Teamcenter rich client and thin client as a stand-alone application.
The software suite includes Teamcenter’s lifecycle visualization base, Teamcenter’s
lifecycle visualization standard, Teamcenter’s lifecycle visualization professional,
and Teamcenter’s lifecycle visualization mockup.
Teamcenter’s manufacturing process management

Teamcenter manufacturing process design and management system. Teamcenter’s
manufacturing process management comprises several user applications, for
example, Plant Designer, Manufacturing Process Planner, Multiple View Editor,
Part Planner, Report Generator, and Resource Manager.
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.

Glossary
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 File Services (TCFS)

File services that enable the Organization application to create volumes and perform
other administrative functions. TCFS also supports file access for legacy versions of
NX and Teamcenter’s lifecycle visualization.
Teamcenter File Structure

File structure of an installed Teamcenter node; it separates homogeneously shared
binary executables from heterogeneously shared data.
Teamcenter Integration for NX

NX-based entry-level set of Teamcenter data management functions, such as
vaulting, checking in, checking out, revision management, attribute synchronization,
and searching CAD data. Teamcenter Integration for NX manages NX files and
their data without exposing the user to full Teamcenter functionality. Teamcenter
Integration for NX users have only limited access to the Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter
functionality available. Teamcenter Integration for NX excludes certain Teamcenter
functionality, such as workflow and product structure editing.
Teamcenter Integration for NX I-deas

Product that integrates Teamcenter and I-deas to provide a single data management
environment for users. Teamcenter Integration for NX I-deas users author their
data in I-deas and manage the data in Teamcenter. Teamcenter Integration for NX
I-deas includes the My Teamcenter user interface and the I-deas Data Services (IDS)
and Team Data Sharing (TDS) modules. See also I-deas and My Teamcenter.
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 Linking
Teamcenter component that enables users to create links between Teamcenter
objects and objects in other Teamcenter products, such as Teamcenter’s systems
engineering and requirements management and Teamcenter’s portfolio, program
and project management. Users can then launch the linked Teamcenter product
from within either the rich client or the thin client.
Tessellation
Process that translates a CAD file to a visualization file.

Appendix A Glossary
Thin Client
Teamcenter user interface that provides a streamlined browser-based view of
product information stored in a Teamcenter database. The thin client is configured
in the Web tier, which creates and serves its Web pages to the client.
Transient Volume
Operating system directory controlled by Teamcenter and used to store temporary
data for transport of reports, PLM XML, and other nonvolume data between the Web
tier and client tier in a deployment of the Teamcenter four-tier architecture.
Two-Tier Architecture
Teamcenter architecture that includes a resource tier and a client tier. The resource
tier comprises the database server and database. The client tier comprises the
Teamcenter rich client, third-party applications that integrate with the rich client,
and a local server. This architecture supports only the Teamcenter rich client.
Two-Tier Deployment
Deployment of the Teamcenter two-tier architecture. In a typical deployment of the
two-tier architecture, the rich client and its local server are installed on a user’s
workstation as are third-party applications that integrate with the rich client. The
database server and the Teamcenter corporate server are installed on one or more
separate computers.
User Preference
Teamcenter preference applying to a specific user.
Visualization
Ability to display a realistic, real time, graphical visualization of geometric data.
Volume
Operating system directory controlled by Teamcenter and used to store the files
managed by Teamcenter. When a user performs an action that causes Teamcenter
to create a file, the file is created in the Teamcenter volume. Users cannot directly
access the files in Teamcenter volumes; they must do so via a Teamcenter session.

Graphical installation utility that generates supporting Web files (WAR and EAR
format) for a named Web application. Web Application Manager also installs the rich
client distribution server and creates distribution server instances.
Web Tier
Teamcenter architectural tier that comprises a Java application running in a Java
2 Enterprise Edition (J2EE) application server. The Web tier is responsible for
communication between the client tier and enterprise tier. The Web tier application
also includes the Application Interface Web Service (AIWS), WebDAV service, and
thin client.
World
All users regardless of group or role.

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

Appendix
B Troubleshooting
Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . B-1

Installation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Problems/error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Update Manager FTP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Resolving Web tier connection problems . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Change the deployable file name on the corporate server . . . . . . . . . . . B-3
Change the deployable file name on the Web tier . . . . . . . . . . . . . . . . B-4
Web Application Manager needs location of Java file when installing rich
client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Make the Java jar file available for the four-tier rich client . . . . . . . . . B-4
Import of UGMASTER PDI part in GM Overlay fails . . . . . . . . . . . . . . . . B-4
Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . B-5
Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

View additional information about an Oracle error message . . . . . . . . . . . B-9
Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . B-9
Recovering from a corrupted Oracle-based database . . . . . . . . . . . . . . . . . . . B-10

Remove the Teamcenter infodba schema . . . . . . . . . . . . . . . . . . . . . . . . B-10

Appendix
B Troubleshooting
Troubleshoot problems you encounter during Teamcenter server installation.
Troubleshooting Teamcenter server installation

Find system log files or error messages to help you determine the source of the
problems you encounter. Perform the solutions provided.
Installation files
Teamcenter Environment Manager generates files in the install directory under the
Teamcenter application root directory.
• installdate-time_configuration-ID.log
Teamcenter Environment Manager generates a log file for each installation and
configuration you create. The log file contains a record of activities performed
by Teamcenter Environment Manager. Keep these files to maintain a complete
history for troubleshooting purposes.
• insautonomy.log
This file contains an installation record for Autonomy Intelligent Data Operating
Layer (IDOL) server, the default full-text search engine.
• configuration.xml
This file contains a record of the Teamcenter installation. Teamcenter
Environment Manager uses the configuration file to enable you to maintain the
installation, including adding and removing components, patching installations,
and upgrading installations.
Caution
Do not remove the configuration.xml file. Removing the
configuration.xml file results in the inability to modify the installation
using Teamcenter Environment Manager.
• uninstall.xml
This file contains a record of the Teamcenter uninstallation.
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:
PLM00011 C Installation on UNIX and Linux Servers Guide B-1

Appendix B Troubleshooting
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.
Table B-1. Installation problems and error messages

Problem/error message Possible cause Solution
<<null>>\\<<null>> on Most likely indicates Start Teamcenter
host host-name does that you attempted Environment Manager
not have administrator to start Teamcenter as a user logged onto the
privileges Environment Manager system with Administrator
using the Windows runas group privileges and the
command or the Run Log on as a service right.
as menu command. For more information, see
Teamcenter Environment Required operating system
Manager cannot be and user accounts.
started as a user other
than the user logged on to
the operating system.
Online help installed for The Set the
thin client does not display WEB_core_help_server WEB_core_help_server
and WEB_help_server preference to the full path
preferences were not to the location of the online
set correctly by the help help/index.htm file.
installation program or
the installer. Set the
WEB_help_server
preference to the full
path to the location
of the online help
help/thin_client_dhtml/
book.html file.
Online help installed for Teamcenter Environment Check the
rich client (direct file Manager did not update portalHelpPage
access) does not display. the portalHelpPage property in the
property in the site_specific.properties
site_specific.properties file. If the path is not
file. present or incorrect,
manually correct it to refer
to the location of the online
help files in the file system.
B-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Troubleshooting
Update Manager FTP errors

Table B-2 describes errors that can error while connecting to the update server
or while downloading updates.
Table B-2. Update Manager FTP errors

Error Resolution
Cannot contact server Host or port may be incorrect. Check Host and
Port values and try again.
Cannot log on User name or password may be incorrect. Check
User and Password values and try again.
Incorrect Path Path to the directory on the update server may
be incorrect. Check the path and try again.
Timeout Error The update manager received no response from
the update server. Try connecting later or contact
your system administrator for assistance.
Transfer Error Contact with the update server was interrupted.
Try your operation again or contact your system
administrator for assistance.
Resolving Web tier connection problems

If the Teamcenter Web tier and the corporate server do not reference the same Web
application name, the Web tier cannot connect to the Teamcenter server.
The Web application name specified in the Teamcenter Web tier must match the Web
application name specified on the corporate server.
During installation of the Teamcenter corporate server, you specify this value in the
Web Application Name box in the Default Site Web Server panel of Teamcenter
Environment Manager. The default Web application name is tc.
During installation of the Teamcenter Web tier, the Web Application Manager
assigns the Web application the default name of tc.
If you specify a Web application name other than tc during corporate server
installation, you must change the corresponding value during Web tier installation.
If the Web tier and the corporate server do not reference the same Web application
name, the Web tier cannot connect to the Teamcenter server.
To ensure the Web tier and the corporate server reference the same Web application
name, perform one of the following procedures:
Change the deployable file name on the corporate server

Using Teamcenter on a two-tier rich client host, set the
WEB_default_site_deployed_app_name preference to reflect the deployable file
name specified in Web Application Manager. (Alternatively, you can set this
preference using the preferences_manager utility from a command prompt.)
For more information about the WEB_default_site_deployed_app_name preference,
see the Preferences and Environment Variables Reference. For information about
setting preferences, see Getting Started with Teamcenter.

Change the deployable file name on the Web tier

1. In Web Application Manager, select your Web application and click Modify.
2. In the Modify Web Application dialog box, click Modify Web Application
Information.
3. Change the value in the Deployable File Name box to reflect the Web application
name you entered during corporate server installation.
4. Click Generate Deployable File to rebuild your Web application.
5. Deploy the rebuilt Web application on your Web application server.
Web Application Manager needs location of Java file when installing

rich client
Under certain circumstances, the Web Application Manager does not find the Java
jakarta-regexp-1.3.jar file required to install the four-tier rich client.
To resolve this problem, make the jakarta-regexp-1.3.jar file available to the Web
Application Manager.
Make the Java jar file available for the four-tier rich client
1. Locate the bmide/compressed_files directory in the Teamcenter software
distribution image.
2. Extract the bmide.zip file to a temporary directory. (This file contains the
jakarta-regexp-1.3.jar file.)
3. Add the temporary directory to the list of Disk Locations for Install Images in
the Web Application Manager.
4. Build your Web application EAR file using the Web Application Manager.
5. Deploy your EAR file as described in the Web Application Deployment Guide.
Import of UGMASTER PDI part in GM Overlay fails

If you attempt to create a CORP_ item, it sometimes fails in GM Overlay databases
upgraded from Engineering Process Management 9.1.3 or Engineering Process
Management 2005 to Teamcenter 8. This occurs when legacy action rules are not
removed from the database during the upgrade.
After upgrading to Teamcenter 8, follow the instructions in the Business Modeler
IDE Guide to migrate the GM Overlay action rules to extension rules and delete
the action rules. Some GM Overlay action rules have already been migrated to
extension rules and are shipped as part of the Teamcenter Automotive Edition and
GM Overlay templates. After you extract your database in step 2 of Convert action
rules to extension rules, verify the extracted action rules against the extensions in
the template. If there are no additional action rules to be converted in the Business
Modeler IDE templates, you can skip steps 3–5 in the procedure. Some of the GM
Overlay action rule names are modified in Teamcenter 2007. The table shows the
mapping of action rules to extension rules.

Troubleshooting
Engineering Process Management 9.1.3 Teamcenter 2007 – GM Overlay method

– GM Overlay action rules extensions
GMPDM_CM_baseline_preaction GMO_check_baseline_preaction
GMPDM_CM_set_pdi_comments GMO_set_baseline_comments
CUSTOM_CM_validate_sec_objs GMO_validate_sec_objs
GMPDM_check_gm_bldintent_rel GMO_check_gm_bldintent_rel
GMPDM_ask_gm_buildintent_props GMO_ask_gm_buildintent_props
GMPDM_CM_copy_forward_attrs GMO_CM_copy_forward_attrs
GMPDM_CM_cond_create_pwt_forms GMO_cond_create_pwt_forms
GMPDM_CM_cond_saveas_pwt_forms GMO_cond_saveas_pwt_forms
GMPDM_CM_copy_pwt_part_forms GMO_copy_pwt_part_forms
PWT_reset_actual_mass GMO_PWT_reset_actual_mass
GMPDM_CM_copy_cost_forms GMO_CM_copy_cost_forms
GMPDM_CM_delete_cost_form GMO_CM_delete_cost_form
GMIMAN_notifyIRCreation GMO_notify_on_ir_creation
GMPDM_delete_product_def_form GMO_delete_product_def_form_ptr
GMPDM_validate_product_def GMO_validate_product_definition_entries
Note
Deleting the legacy action rules after successfully upgrading the GM Overlay
may change expected behavior in some areas of the GM Overlay. For
example, you cannot create item types like CORP_Part, CORP_Install,
CORP_Product, and CORP_Software.
Troubleshooting four-tier architecture deployment

Identify the problem you encountered in your four-tier rich client architecture and
perform the solution described.
Problem Solution
Error indicating no server pool Either the server manager is not started or TreeCache
communication is not occurring. Ensure that you correctly
coordinated the server manager and Web tier TreeCache
configuration settings.
For information about coordinating these settings, see the
description of the server manager context parameters in
table E-1.
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.

Problem Solution
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.
handleJoin errors occur at Occasionally, TreeCache instances fail to accept connections
startup and report handleJoin errors. Typically this error
disappears if you restart one or more cluster members.
Configuration is correct, but To get additional information, increase the logging level for
run-time errors occur the tree cache and jgroups classes for both the application
server and server manager:
1. Copy the log4j.xml file in the server manager run-time
directory (TC_ROOT/pool_manager) to the application
server instance startup directory.
By default, the server manager run-time directory
includes a log4j.xml file, but it logs only the warning
level information. The default configuration sends log
output to the console and the following files:
TC_ROOT/pool_manager/logs/ServerManager
/process/serverManager.log
APPSERVER_ROOT/logs/WebTier/processWebTier.log
2. Edit log4j.xml so that more information is logged at run

time. For example, to increase the log4j output for the
JBossCache and jgroup classes to the INFO level,
edit the file:
<logger
name="org.jboss.cache" additivity="false">
<level value="INFO"/>
<appender-ref ref="WebTierAppender"/>
<appender-ref ref="ProcessConsoleAppender"/>
</logger>
<logger name="org.jgroups" additivity="false">
<level value="INFO"/>
<appender-ref ref="WebTierAppender"/>
<appender-ref ref="ProcessConsoleAppender"/>
</logger>
The JMX HTTP adaptor allows you to view the status

of the server pool and dynamically change the pool
configuration values (the values are not persistent). Access
this functionality from the following URL:
http://host-name:jmx-port

Troubleshooting
Problem Solution
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.
Elevated CPU usage Determine from logs whether users are frequently losing a
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.
Either the server manager fails to Check the internet protocol configuration on the server
start when employing multicast manager host. By default, Java prefers to use Internet
TreeCache mode or the following Protocol Version 6 (IPv6) addresses. Incomplete IPv6
error message is received: configuration can cause Java socket exceptions that prevent
Exception in thread "main" the server manager from starting.
java.net.SocketException:
Can’t assign requested For example, an IBM AIX server might be configured to have
address an IPv6 loopback address ::1 but no IPv6 ethernet address.
Detect this problem on AIX with the command:
netstat –ni
If this is the case, either complete the IPv6 upgrade
configuration as documented in the IBM System
Management Guide or uncomment the following line in the
mgrstart script:
#JVM_ARGS="${JVM_ARGS} -Djava.net.preferIPv4Stack=true"
This line adds the –Djava.net.preferIPv4Stack=true Java

option, instructing the JVM to use IPv4 addresses for the
server manager.
Note
If the Web application server is running on the same
host as the server manager, add this Java option to the
Web application startup script also.
On a machine with multiple IP addresses, it may be

necessary to configure the address used by the TreeCache.
This address can be added to the TreeCacheTCP.xml file
(for TCP mode) or the TreeCacheMcast.xml file (for Mcast
mode). In the server manager, this file can be found in the
TC_ROOT/pool_manager directory. In the J2EE application
it can be found in the file JETIServerAccessor.jar in
the staging area of the Web Application Manager. For
Mcast mode, locate the UDP configuration line and add
bind_addr=desired-address. For TCP mode, locate the TCP
configuration line and add bind_addr=desired-address.

Problem Solution
Out-of-memory messages from Review and adjust as necessary the settings for the following
Web application server running kernel parameters:
on HP-UX platform
max_thread_proc
maxfiles
maxusers
Particularly, the default max_thread_proc value of 64 is
not sufficient for running the Web application server. The
optimum values depend on the traffic level and machine
capabilities.
TreeCache connection failure Terminating a server manager instance by sending it a signal
after restarting or redeploying does not clean up the TreeCache data stored in other four-tier
components regarding the terminated pool. When this server
manager is restarted, it cleans up this information. However,
termination of a server manager in this way sometimes
leaves the TreeCache communication mechanisms in a
corrupted state and the server manager is not able to rejoin
the TreeCache cluster. The problem can be resolved by
stopping all four-tier components (the application servers
and server managers) in the TreeCache cluster and then
restarting them all. This problem can usually be avoided
by shutting the server manager down cleanly through the
server manager Administrative Interface. For information
about using the server manager administrative interface, see
the System Administration Guide.
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.
Troubleshooting Oracle
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.

Troubleshooting
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.
This command displays cause and action messages that you can use to
troubleshoot the problem.
Troubleshooting Teamcenter Integration for NX

Teamcenter Integration for NX may be unresponsive in a four-tier rich client if you
specify an incorrect value for Web Application Name during installation of the
Teamcenter corporate server.
During corporate server installation, TEM prompts for the Web application name in
the Default Site Web Server panel. The Web application name you enter is used to
populate the WEB_default_site_deployed_app_name preference in the Teamcenter
database. When you build the Teamcenter Integration for NX Web application in
Web Application Manager, you specify the actual name of the Web application.
If the name of the deployed Web application does not match the value specified in
TEM, the Web application fails to connect to the Teamcenter server.
If you experience problems starting Teamcenter Integration for NX from the four-tier
rich client, inspect the ugs_router system log for messages that resemble the
following example:
INTEROP: Executing: O:\win32\ugnx5.0.0.22\ugii\ugraf.exe -pim=yes -
http_url=http://AcmeCorp:8080/tc/aiws/aiwebservice -soa_url=http://AcmeCorp:8080/tc"-
http_cookie=IMAN=08100000000000madakash45b765e1cd0ea854705e5f8f; path=/;" -
http_vmid=b6e51c5aaaf5b200:-58275229:1104f3e3952:-8000 "-role=ALL" -
portalinfo=localhost:2377:PROCESS_COMMAND_LINE -
invoke=com.teamcenter.rac.commands.objectschanged.ObjectsChangedCommand+-uids=%s+-
src=madakash@4Tier_w__NX :madakash@4Tier_w__NX 4-tier
INTEROP: Waiting for UG/Manager V23.0 1 to start up...
This message results from the rich client expecting a Web application named tc but
being unable to find it.
To resolve this problem, set the WEB_default_site_deployed_app_name preference
to the correct name of the deployed Web application. You can update this preference
using the preferences manager from the command line or from within the rich client.
For information about using the preferences manager, see the Preferences and
Environment Variables Reference.

Recovering from a corrupted Oracle-based database

If an Oracle-based Teamcenter database is corrupted beyond repair, you can either:
• Delete the database using Oracle Database Configuration Assistant (DBCA).
• Remove the Teamcenter infodba schema (unpopulate the database).
Remove the Teamcenter infodba schema

1. Log on to the server as the oracle user.
2. Get a new shell window, set the ORACLE_HOME and ORACLE_SID

environment variables, and start the Oracle SQL*Plus utility. For example:
export ORACLE_HOME=/disk1/oracle/OraHome_1
export ORACLE_SID=tceng
$ORACLE_HOME/bin/sqlplus /nolog
3. Log on to the SQL*Plus utility as sysdba:

connect / as sysdba
4. Run the Siemens PLM Software-supplied tceng_unpopulate_db.sql script

that was copied to the Oracle templates directory:
@$ORACLE_HOME/assistants/dbca/templates/tceng_unpopulate_db.sql
Note
If you receive an error message about not being able to drop the user,
for example:
ORA-01940 cannot drop a user that is currently connected
either try to terminate all current Teamcenter connections to the database

or restart the database before running tceng_unpopulate_db.sql again.
For example:
shutdown immediate;
startup;
@$ORACLE_HOME/assistants/dbca/templates/tceng_unpopulate_db.sql
5. Exit the SQL*Plus utility.
6. Reconfigure the database either using Teamcenter Environment Manager to

populate it with new, empty Teamcenter tables or by importing a backup copy of
the database (if the database was already in production).
You could also recycle the unpopulated database instance for other use as all
Teamcenter tables are removed.

Appendix
C Distribution media
Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter documentation distribution image . . . . . . . . . . . . . . . . . . . . . . . C-2

Appendix
C Distribution media
Siemens PLM Software distributes the following software and documentation

images for Teamcenter 8:
Image Description
Teamcenter software Contains Teamcenter software for your operating
system (Hewlett-Packard HP-UX, IBM AIX, Sun Solaris,
SUSE Linux, Apple Macintosh, or Microsoft Windows).
The software distribution image includes Teamcenter
installation programs (Teamcenter Environment Manager
and Web Application Manager) and required files for
Teamcenter features such as Security Services.
For a detailed description of the contents of this image, see
Teamcenter software distribution image.
Teamcenter Contains the archive file required for installing Teamcenter
documentation online help (tchelp.jar), Teamcenter documentation in PDF
format, and Teamcenter documentation in HTML format.
For a detailed description of the contents of this image, see
Teamcenter documentation distribution image.
Rich client Contains the files required to install the Teamcenter rich
over-the-Web client over-the-Web on all supported operating systems,
including a rich client distribution server and Over-the-Web
Installer.
Visualization Contains the files required to install Teamcenter’s 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:
PLM00011 C Installation on UNIX and Linux Servers Guide C-1

Appendix C Distribution media
Directory Description
additional_applications The additional_applications contains directories
containing applications such as the Teamcenter
EDA client, File Management System client cache
(FCC), Security Services, and the Siemens PLM
Software Common Licensing Server.
additional_documentation Contains instructions for installing Oracle 10.
advanced_installations Contains the resource_management
subdirectory that contains Resource Manager
application files for Teamcenter’s manufacturing
process management.
An additional subdirectory, cc_integration,
contains Teamcenter’s manufacturing process
management components required when installing
the Multi-Structure Manager integration with
Tecnomatix eMPower.
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.
rac_esddm Embedded Software Design Data Management
support for the rich client.
rac_tcgsactions Global Services support for the rich client.
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.sh) that installs Teamcenter
executables and data directories.
Teamcenter documentation distribution image

The Teamcenter documentation distribution image contains the archive file required
for installing Teamcenter online help (tchelp.jar) plus the following directories:
• HTML
Contains the Teamcenter online help library. To display the online help library
index page, open the index.htm file in the help directory.
C-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Distribution media
• PDF
Contains the Teamcenter online help library in PDF format. To display the
online help library index page, open the index.htm file.
Note
If you use popup blocker software, configure it to allow popups within the
Teamcenter online help library.
PLM00011 C Installation on UNIX and Linux Servers Guide C-3

Appendix
D Solutions and features reference
Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12

Appendix
D 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 Select Features panel in Teamcenter Environment Manager (TEM). For
information about a solution, point to the solution name in the list. TEM displays
a description.
Table D-1. Teamcenter solutions

Solution Features
Corporate Server Teamcenter File Services
FMS Server Cache
NX UG Integration
Business Modeler IDE Business Modeler Templates
Client
Dispatcher (Dispatcher Server) Dispatcher Server
EDA Standalone Client EDA Standalone Client
PADS Support
Mentor Support
Cadence Support
Mentor Expedition Library Support
Mentor Board Station Library Support
Mentor PADS Library Support
Cadence Allegro Library Support
Global Services Teamcenter Foundation
FMS Server Cache
J2EE Based Server Manager
Global Services Framework
Global Services Preferences
Log Manager Query Service Log Manager Query Service
Multisite Collaboration Proxy Server Multisite Collaboration IDSM Service
Multisite Collaboration ODS Service
PLM00011 C Installation on UNIX and Linux Servers Guide D-1

Appendix D Solutions and features reference
Table D-1. Teamcenter solutions

Solution Features
Rich Client 2-tier Teamcenter Rich Client 2-tier
Rich Client 4-tier Teamcenter Rich Client 4-tier
Volume Server Teamcenter File Services
FMS Server Cache
Teamcenter features
TEM provides the following features and feature groups in the Select Features
panel. Features are grouped by related applications. For information about a feature,
point to the feature name in the list. TEM displays a description of the feature.
Note
• Some features are disabled because they require other features. To enable
a feature, select its prerequisite features. For information about feature
prerequisites, see the feature description.
• Some features cannot be installed in the same configuration, so selecting

one disables the other.
Table D-2. Teamcenter features

Feature/Subfeature Description
Teamcenter Corporate Server Teamcenter corporate server features.
Teamcenter File Services Installs the Teamcenter File Services (TCFS) service that enables administrators
to create volumes using the rich client Organization application and to perform
other administrative functions. TCFS also supports file access for legacy NX and
Teamcenter’s lifecycle visualization products.
You must install the TCFS service on each host that is to provide volume services,
including hosts where you want to enable administrators to create a volume at
a later date.
When you also install File Management System, the operating system user
running TCFS must be the same operating system user running FMS.
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,
Teamcenter File Services, 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.
D-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Solutions and features reference

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.
When you also install TCFS, the operating system user running FMS must be the
same operating system user running TCFS.
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.
NX UG Integration Installs default data types and loads template NX data to support Teamcenter
Integration for NX/NX Integration, the Teamcenter integration with Siemens
PLM Software NX.
Log Manager Query Service Installs the Log Manager Query Service.
J2EE Based Server Manager Installs the process that manages the pool of Teamcenter server processes. This
option is applicable only when you are deploying the Web tier. This feature
requires Teamcenter Foundation and FMS Server Cache features.
For a smaller site, you can install the server manager and Teamcenter servers on
the same host as the Web tier application. For deployment options for larger sites,
you can install the server manager on a separate host.
.NET Based Server Manager Installs the process that manages the pool of Teamcenter server processes. This
option is applicable only when you are deploying the Web tier. This feature
requires Teamcenter Foundation and FMS Server Cache features.
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.
Finished Product Management Installs the Finished Product Management template.
Oracle Manufacturing Integration Installs the Oracle Manufacturing integration to Teamcenter.
Global Services Adapter Configures eIntegrator Admin to use the adapter that connects eIntegrator Admin
to Teamcenter Global Services, a Web-based application enabling clients to access
information stored in virtually any type of data source that manages site data.
Prerequisite:
Install and configure Global Services.
Required information:
• URL to the Global Services-Enterprise application.


Teamcenter Security Services Configures Security Services for Teamcenter. These services eliminate prompts for
logon credentials when users switch Teamcenter products within a user session.
Prerequisite:
Installation and configuration of Security Services.
For information about Security Services, see the Security Services

Installation/Customization guide.
• 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.

Vendor Management Installs the optional Vendor Management solution.
CAD-BOM Alignment Configures the Teamcenter installation to interact and share visual data with
Bill-of-Materials Management. Configuring this feature allows designs managed
by this installation of Teamcenter to be related to parts and use or parts in
products that are managed by Bill-of-Materials Management.
Note
This feature requires postinstall setup to complete configuration.
Wire Harness Configuration Installs Teamcenter schema support for wire harnesses.
Global Services Framework Creates Global Services Framework.
Packaging and Artwork Installs the Packaging and Artwork template for Consumer Packaged Goods.
For information about installing this feature, see Getting Started with Consumer
Packaged Goods.
Online Help Installs the Teamcenter Help Library files on the local host:
When TEM prompts you for the location of the Teamcenter help files, enter the
path to the Teamcenter documentation distribution image, which contains the
online help files (tchelp.jar).
Note
For information about installing online help using as part of a Web tier
application, see Teamcenter online help installation.
Content Management Base Installs the data model for Content Management.
For information about configuring this feature, see Content Management

Administration Guide.
Brand Management Installs the Brand Management template for Consumer Packaged Goods.
Packaged Goods.


Teamcenter Linking Configures linking between Teamcenter, Teamcenter’s portfolio, program and
project management, and Teamcenter’s systems engineering and requirements
management so that objects in one of these applications can be shared by another.
This option is applicable only when you are deploying the four-tier architecture.
Prerequisites:
• Teamcenter Linking components, including Application Registry, must be

separately installed and configured.
• The Web tier application, including the optional Application Interface Web
Service (AIWS) and Teamcenter Linking parameters, must be installed and
configured as described in .
• 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’s portfolio, program and project management,

the chooser servlet name.
Specification Manager Installs the Specification Manager feature. For more information about installing
this feature, see the Specification Manager Guide.
CPG Materials Installs CPG Materials functionality for Consumer Packaged Goods.
Packaged Goods.
Teamcenter Visualization Installs the data model for Teamcenter’s lifecycle visualization.
This feature requires Teamcenter Foundation.

EDA Server Support Installs the dataset types and transfer modes required to support Teamcenter
EDA, the application that integrates ECAD applications with Teamcenter.
For complete information about installing Teamcenter EDA, see the Getting
Started with Electronic (EDA) Lifecycle Management.
Hierarchical Storage Management (HSM) Adds support for third-party hierarchical storage management software.
ERP Connect Installs the ERP Connect Toolkit interface that integrates Teamcenter with other
Enterprise Resource Planning (ERP)-supported applications, such as BAAN.
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.
SCM ClearCase for Foundation Installs ClearCase types and sets Teamcenter preferences to enable the integration
between Teamcenter and the IBM ClearCase software configuration management
(SCM) tool.
For more information about installation, see the Teamcenter ClearCase Integration
Guide.


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.
Global Services Preferences Installs Global Services Preferences.
Embedded Software Design Data Installs Embedded Software Design Data Management. For more information
Management about this feature, see the Embedded Software Solutions Guide.
ECAD Part Library Management Installs ECAD part types to support ECAD part library management. This feature
requires Teamcenter Foundation, Vendor Management, and EDA Server Support.
Aerospace and Defense Foundation Installs Aerospace and Defense functionality for the Teamcenter server. This
feature requires Teamcenter Foundation and Vendor Management.
For more information about this feature, see the Getting Started with Aerospace
and Defense guide.
Content Management S1000D Enables management of documentation for the S1000D standard in Content
Management.
For information about configuring this feature, see Content Management

Administration Guide. For information about using Content Management, see the
Content Management Guide.
Aerospace and Defense Training Installs the Aerospace and Defense training program for the Aerospace and
Defense Foundation feature. the for the Teamcenter server. This feature requires
Teamcenter Foundation, Vendor Management, and Aerospace and Defense
Foundation.
For more information about this feature, see the Getting Started with Aerospace
and Defense guide.
Dispatcher Server Installs the following Dispatcher Server components: scheduler, module and
administration client.
For information about installing this feature, see Getting Started with Dispatcher
(Translation Management).
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.
EMPS - Foundation Installs electronic design and manufacturing types to support ECAD translation
and PCB design collaboration using Teamcenter embedded viewer.
EMPS - ECAD Translation Installs EMPS – ECAD translation, which allows conversion of a PCB design into
the XFATF format. ECAD translation support 36 different CAD formats. This
feature requires EMPS - Foundation and Dispatcher Server.
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.


Wire Harness Configuration in GM Configures wire harness configuration for a Teamcenter Automotive Edition
Overlay GM Overlay environment. Requires Teamcenter Foundation, Wire Harness
Configuration, Teamcenter Automotive Edition, and GM Overlay.
Configure AutoCAD Integration for GM Configures AutoCAD Integration/AutoCAD Manager to operate in a Teamcenter
Overlay 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.
Install Libraries for AIWS Client Installs sample source code and executables that assist in developing an
Application Interface Web Service (AIWS) client.
For more information, see the Application Interface Web Service (AIWS)
Configuration and Customization Guide.
Database Configuration for DPV Installs the DPV (GDIS Database Configuration) application.
GM Customization for DPV Installs GM-specific LOVs and GRM rules for DPV.
QPL for Repeatable Digital Validation Installs and configures QPL files used in conjunction with the rich client
DesignContext application.
For QPL-based DesignContext, installing Repeatable Digital Validation (RDV)

services is required. For Appearance-based DesignContext, installing RDV services
is not required. QPL is not required if you use cacheless search.
• The path to the location of an installed NX application.
• The type of search engine to use, either an NX-based engine or a JT-based

engine.
• Database configuration for use with Repeatable Digital Validation.
DesignContext is available for both the rich client and thin client.
Embedded Software Manager for Data types for Embedded Software Solutions.
Foundation
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).
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).
Teamcenter MRO Teamcenter’s maintenance, repair, and overhaul features.
MRO As-Built Installs the As-Built template for Teamcenter’s maintenance, repair, and overhaul.
For information about installing, configuring, and using this feature, see the
As-Built Manager Guide.


Teamcenter Manufacturing Teamcenter’s manufacturing process management (Manufacturing Process
Management) features.
Install Libraries for Resource Installs libraries for the Resource Browser application.
Browser
Comprehensive Manufacturing Additional data types for Teamcenter’s manufacturing process management.
Types
Customization for Process Installs additional data types for Process Simulate Integration Customization.
Simulate Integration
Customization for eM-Server Installs additional data types for Tecnomatix server integration customization.
Integration
eBOP reports Customization Installs additional data types for eBOP Reports Customization. This feature
requires Teamcenter Foundation and Customization for eM-Server Integration.
PAD/TWP Customization Installs additional data types for PAD/TWP Customization. This feature
requires Teamcenter Foundation, GM Overlay, and Customization for eM-Server
Integration.
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.
Structure Search Structure search features.
Spatial Search Installs Spatial Search capabilities of the cacheless search engine.
For more information about configuring and using Spatial Search, see the Getting
Started with RDV guide.
This feature requires Dispatcher Server.

Bounding box generation from JT Enables generation of bounding box data from JT files, providing secondary data
for the cacheless search engine. For more information about configuring and using
cacheless search, see the Getting Started with RDV guide.
This feature requires Dispatcher Server. Also, during Teamcenter installation,

you must install the Spatial Search translator (JtToBboxAndTso).
Trueshape generation from JT Enables generation of Trushape data from JT files, providing secondary data for
the cacheless search engine.
For more information about configuring and using cacheless search, see the Getting
Started with RDV guide.
This feature requires Dispatcher Server. Also, during Teamcenter installation,

you must install the Spatial Search translator (JtToBboxAndTso).
Bounding box generation from NX Enables generation of bounding box data when saving NX files, providing
secondary data for the cacheless search engine.
Database Daemons Optional database support services.
Database Daemons Task Manager Checks user inboxes for tasks that have passed due dates, notifies the delegated
Service recipients, and marks those tasks as late.
Installing the Task Monitor service is required to enable notification of late tasks.


Database Daemons Tesselation Tessellates UGMASTER and UGALTREP datasets to the JT (DirectModel)
Manager Service 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.
Database Daemons Action Manager Monitors the database for the creation of action objects and dispatches events
Service 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.
Database Daemons Subscription Monitors the database event queue for the creation of subscription event objects.
Manager Service
Installing the Subscription Manager service is required to enable the rich client
Subscription Monitor application.
Multisite Services Services to support Multi-Site Collaboration.
Multisite Collaboration IDSM Installs the distributed services manager (IDSM) required to replicate data
Service 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).
Rich Client Teamcenter rich client features.
Teamcenter Rich Client 2-tier Installs a two-tier rich client and optionally configures it for use with additional
features and applications, such as Teamcenter’s lifecycle visualization and NX
Manager.
Teamcenter Rich Client 4-tier Installs a four-tier rich client and optionally configures it for use with additional
features and applications, such as Teamcenter’s lifecycle visualization and NX
Manager.
Rich Client (Shared Disk Deployment) Installs the rich client in a shared location. This client can be run from multiple
hosts.
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.
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.
Render Document for Rich Client Provides Render Management capabilities for the rich client. This feature requires
Dispatcher Client for Rich Client.
For more information about configuring and using Render Management

capabilities, see the Rich Client Interface Guide.
For information about installing Dispatcher features, see Getting Started with
Dispatcher (Translation Management). For information about installing and
configuring file translators for the Dispatcher Server, see the Dispatcher Server
Translators Reference Guide.
Rich Client Add-Ons Add-on features for the Teamcenter rich client.


Teamcenter Extensions for Installs Teamcenter’s Extensions for Microsoft Office. For information about
Microsoft Office installing this feature, see the Installation on Windows Clients Guide.
Office Client for Microsoft Office Installs the Teamcenter’s Client for Microsoft Office. For information about
installing this feature, see the Installation on Windows Clients Guide.
Embedded Software Manager for Installs Embedded Software Solutions for the rich client. This feature requires
Rich Client Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Installs CPG Materials support for Consumer Packaged Goods.
CPG Materials for Rich Client
Packaged Goods.
Teamcenter Single Sign-on for Rich Installs Teamcenter single sign-on for the rich client. This feature requires
Client Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
ECAD Part Library for Rich Client Enables ECAD part library menus in the rich client.
NX Manager for Rich Client Installs Teamcenter Integration for NX for the rich client. This feature requires
Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Global Services Monitoring GUI for Installs a rich client and configures it for use with the Global Services Monitoring
Rich Client GUI for Rich Client feature. This feature requires Teamcenter Rich Client 2-tier or
Teamcenter Rich Client 4-tier.
Content Management System for Installs Content Management functionality for the rich client. This feature
Rich Client requires Teamcenter Rich Client 4-tier.
Teamcenter Visualization 8 Installs the embedded viewer for the rich client. This feature requires Teamcenter
(Embedded) for Rich Client Rich Client 2-tier or Teamcenter Rich Client 4-tier.
GM Overlay for Rich Client Installs the GM Overlay for the rich client. This feature requires Teamcenter Rich
Client 2-tier or Teamcenter Rich Client 4-tier.
EDA for Rich Client Installs Teamcenter EDA for the rich client. This feature requires Teamcenter
Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Vendor Management for Rich Client Installs Vendor Management support for the rich client.
Installs Specification Manager functionality for the rich client.
Specification Manager for Rich
Client For more information about installing this feature, see the Specification Manager
Guide.
SCM ClearCase for Rich Client Installs SCM ClearCase for the rich client. This feature requires Teamcenter Rich
Client 2-tier or Teamcenter Rich Client 4-tier.
InstallsEmbedded Software Design Data Management support for the rich client.
For more information about this feature, see the Embedded Software Solutions
Embedded Software Design Data Guide.
Management for Rich Client
This feature requires Teamcenter Rich Client 2-tier or Teamcenter Rich Client
4-tier.
Teamcenter Visualization 8 Installs stand-alone application viewer for the rich client. This feature requires
(Stand-alone) for Rich Client Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
AsBuiltManager for Rich Client Installs the As-Built functionality for the rich client. As-Built is part of
Teamcenter’s maintenance, repair, and overhaul.
For information about installing, configuring, and using this feature, see the
As-Built Manager Guide.
Teamcenter Web Tier Features to support the Teamcenter .NET Web tier.
ASP .NET State Service Installs the middle tier processes that communicate with Teamcenter server
processes.


Web Tier for .NET Installs the middle tier processes that communicate with Teamcenter server
processes.
Business Modeler IDE Business Modeler IDE features.
Business Modeler Templates Installs the Business Modeler IDE templates.
Client Installs the Business Modeler IDE client.
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.

Digital Dashboard Installs the Digital Dashboard feature.
Configure Teamcenter Servers Teamcenter server configurations for Business Modeler IDE features.
2 Tier Teamcenter Server Configures the two-tier Teamcenter Server so that Business Modeler IDE can
Configuration connect to the Teamcenter Server.
4 Tier Teamcenter Server Configures the four-tier Teamcenter Server so that Business Modeler IDE can
Configuration connect to the Teamcenter Server.
Stand-alone Applications Stand-alone Teamcenter EDA applications.
EDA Standalone Client Installs the client for Teamcenter EDA, the application that integrates ECAD
applications with Teamcenter.
ECAD Design Management ECAD design management features for Teamcenter EDA.
PADS Support Installs support for the using Mentor Graphics PADS product line (PADS Layout
and PADS Logic) with the EDA client, enabling you to manage data that PADS
programs create. This feature requires EDA Standalone Client. You must also
install Mentor PADS software.
Mentor Support Installs support for using Mentor Graphics Board Station software with the EDA
client. Separate installation of Mentor Graphics Board Station is required. This
feature requires EDA Standalone Client.
Cadence Support Installs support for using Cadence Allegro software with the EDA client. Separate
installation of Cadence Allegro Design Entry is required. This feature requires
EDA Standalone Client.
ECAD Library Management ECAD library management features for Teamcenter EDA.
Mentor Expedition Library Support Installs support for using Mentor Expedition Library with the EDA client.
Separate installation of Mentor Expedition is required. This feature requires
Mentor Board Station Library Installs support for using Mentor Graphics Board Station library with the EDA
Support client. Separate installation of Mentor Graphics Board Station is required. This
feature requires EDA Standalone Client.
Mentor PADS Library Support Installs support for the using Mentor Graphics PADS library with the EDA client.
Separate installation of Mentor PADS is required. This feature requires EDA
Standalone Client.
Cadence Allegro Library Support Installs support for using Cadence Allegro library with the EDA client. Separate
installation of Cadence Allegro Design Entry is required. This feature requires

Rich client solutions

You can add rich client solutions to a rich client distribution instance. These solutions
add functionality to the four-tier rich client installed using the Over-the-Web
Installer. For information about creating a rich client distribution instance, see
Install a rich client distribution instance.
Over-the-Web Installer Installs the program that installs the rich client over
the Web. This solution is required.
Rich Client 4–Tier Installs the rich client software required for the
four-tier architecture. This solution is required.
As-Built Manager for Rich Adds As-Built functionality for the four-tier rich
Client 4-Tier client. As-Built is part of Teamcenter’s maintenance,
repair, and overhaul.
For information about installing, configuring, and
using this feature, see the As-Built Manager Guide.
CPG Materials for Rich Installs CPG Materials support for Consumer
Client 4-Tier Packaged Goods.
For information about installing this feature, see
Getting Started with Consumer Packaged Goods.
Content Management Installs Content Management, the application used
System for Rich Client to manage technical documentation using SGML and
4-Tier XML information stored in a Teamcenter database.
This solution is optional.
EDA for Rich Client 4–Tier Configures the rich client to use Teamcenter EDA, the
(Configuration Only) application that integrates ECAD applications with
Teamcenter. Separate installation of the stand-alone
EDA client (using Teamcenter Environment
Manager) is required. This solution is optional.
ESDDM for Rich Client Installs Embedded Software Solutions Design Data
4-Tier Management support for the rich client.
For more information about this feature, see the
Embedded Software Solutions Guide.
Embedded Software Installs Embedded Software Solutions support for
Manager for Rich Client the rich client.
4–Tier
Embedded Software Solutions Guide.
Embedded Translation Installs Dispatcher Client for the rich client.
Services for Rich Client
4–Tier For information about using this feature, see Getting
Started with Dispatcher (Translation Management).
GM Overlay for Rich Client Installs the Teamcenter’s Automotive Edition–GM
4–Tier Overlay application. This solution is optional.
GS Monitoring GUI for Rich Configures the rich client for use with the Global
Client 4–Tier Services Monitoring GUI for Rich Client feature.

MS Office Integration for Installs the application that integrates Teamcenter
Rich Client 4–Tier with Teamcenter’s Integration for Microsoft Office.
Separate installation of Microsoft Office is required.
This solution is optional.
NX Manager for Rich Client Configures the rich client to use Teamcenter
4–Tier Integration for NX or NX Integration, the application
that integrates Teamcenter with NX. Separate
installation of the Teamcenter Integration for NX or
NX Integration executables is required (as part of
NX installation). This solution is optional.
SCM ClearCase for Rich Installs the integration between Teamcenter and the
Client 4–Tier IBM ClearCase software configuration management
(SCM) tool and configures the rich client for its
use. Separate installation of ClearCase software is
required. This solution is optional.
Specification Manager for Installs Specification Manager functionality for the
Rich Client 4–Tier rich client.
Specification Manager Guide.
Teamcenter Applications Installs Teamcenter’s Extensions for Microsoft Office
for Microsoft Office and the Teamcenter Plugin for Microsoft Project,
which allows Microsoft Project users to exchange
data directly with Schedule Manager. Separate
installation of Microsoft Office is required.
For information about installing these features on
a rich client host, see the Installation on Windows
Clients Guide.
Teamcenter Visualization 8 Configures the rich client to use the embedded
(Embedded) for Rich Client viewer when Teamcenter’s lifecycle visualization is
4–Tier (Configuration Only) separately installed on the client workstation. This
solution is optional.
Teamcenter Visualization Installs the embedded viewer and configures the rich
8 (Embedded) for Rich client. This solution is optional.
Client 4–Tier (Install and
Configuration)
Teamcenter Visualization Configures the Teamcenter’s lifecycle visualization
8 (Stand-alone) for Rich application (the stand-alone application viewer).
Client 4–Tier Separate installation of Teamcenter’s lifecycle
visualization is required. This solution is optional.
Vendor Management for Installs Vendor Management support for the rich
Rich Client 4–Tier client.

Render Document for Rich Installs Render Management capabilities for the rich
Client client.
For more information about configuring and using
Render Management capabilities, see the Rich Client
Interface Guide.
For information about installing Dispatcher features,
see Getting Started with Dispatcher (Translation
Management). For information about installing and
configuring file translators for the Dispatcher Server,
see the Dispatcher Server Translators Reference
Guide.
Rich Client 4–Tier Lite Installs the lite edition of the four-tier rich client.
Edition This solution is optional.

Appendix
E Web tier context parameters

Appendix
E Web tier context parameters
Tables E-1 through E-3 describe Web tier context parameters provided by
Teamcenter Web tier solutions.
Table E-1. Web tier required parameters

General parameters
DEPLOYABLE-FILE-NAME Name of the deployable file you are creating for the
Web tier application. The name is configurable; Web
Application Manager adds the file extension.
TcEngEncoding Teamcenter character encoding set for localization.
This value must match the encoding specified for the
Teamcenter server.
For example, if the Teamcenter server is running
using ISO8859_1 encoding, specify ISO8859_1 also
for this parameter.
TcEngLocale Locale of the Teamcenter server for localization of
Web tier messages. This locale must match the locale
of the Teamcenter server.
For example, if Teamcenter server is running in the
Russian locale, specify ru_RU for this parameter.
webdav.useHybrid Specifies whether users must enter a name and
password in a Microsoft application even when
logged on through a Teamcenter application.
This parameter is used when a site enables users to
install the Teamcenter Teamcenter’s Integration for
Microsoft Office on workstations.
PLM00011 C Installation on UNIX and Linux Servers Guide E-1

Appendix E Web tier context parameters

TreeCache parameters
TreeCache Cluster Name Name of a cluster of components accessing a shared
global server pool.
You must supply the same name as specified for
the server manager (installed using Teamcenter
Environment Manager).
TreeCache Mode Communication protocol mode between TreeCache
peers, either TCP or multicast.
You must supply the same mode as specified for
TreeCache Cluster Port Required only when the TreeCache communication
mode is Mcast.
Port used for multicast communication between the
application server and the server manager.
You must supply the same port number as specified
for the server manager (installed using Teamcenter
When configuring multiple environments, use a
different port number for each environment.
Local Service Port Required only when the TreeCache communication
mode is TCP.
Specifies the TCP port at which this TreeCache
cluster member provides the TreeCache service.
If you install the Web tier application on the same
host as the server manager, the local service port for
the Web tier application must be different from the
local service port for the server manager.
TreeCache Peers Required only when the TreeCache communication
mode is TCP.
Specifies a list of addresses (host name and
port number pairs) to ping for peer members of
the TreeCache cluster in TCP communication
mode. It is a comma-separated list of the form
host1[port1],host2[port2],.. Do not use the form
host1:port1, ... because the colon character (:) is
not permitted.
For each host/port pair, this cluster member pings
the port you specify.
In addition, the TreeCache may find more than one
peer based on a single host/port pair (for example, if
E-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Web tier context parameters

multiple peers on a single host have the same local
service port value).
Once established, peers exchange data regarding
available server pools. This cluster member pings
each host/port pair in the list. To be found, a peer
must have a matching service port. (See Local
Service Port in this table.)
• As a minimum, specify the service port for all
Java 2 Enterprise Edition (J2EE) application
server hosts and server manager hosts you want
this Teamcenter server to communicate with.
• For each host, you can include more than one

host/port pair in the list.
It is not necessary to include all members of the
cluster in this list. For example, you may include
only a subset of the server managers and none of
the application servers. In this case, the cluster
connects only when one or more of the designated
managers is running. This technique reduces
pinging and thereby improves performance.
For small configurations, all members should
be included in the peers list. For larger
configurations, it is recommended that the
number of pinged ports be limited to no more
than six. All members should ping at least the
same subset of primary server managers so that
TreeCaches connect and data is shared.
Connection Timeout Required only when the TreeCache communication
mode is TCP.
Maximum time in milliseconds that a TreeCache
cluster member waits for peer responses to TCP
pings.
The larger the value you specify, the more slowly
the first server manager starts.
Typically, you supply this same value for the

Connection Timeout parameter specified for


MAX_POOL_SIZE Specifies the maximum number of concurrent
connections to Teamcenter servers allowed by the
application server. If you do not specify a value,
the Web tier application uses the application server
default value.
Note
This parameter applies to WebLogic, JBoss,
and Oracle Application Server. For other
application servers, the maximum pool size
must be set using the application server
console.
For information, see the Web Application
Deployment Guide.
Enterprise Application Registration ID used to register the application’s EJB and
ID J2C Connector. If you want to deploy multiple
Teamcenter Web tier applications in a single
application server instance, each application must
be assigned a unique ID.
LogVolumeName Name of the log volume.
LogVolumeLocation Log volume location, the root directory under which
log files are created. The default location logs
represent a child folder beneath the default root
directory of the target application server instance.
This location varies depending on the application
server vendor.
Note
If the path you enter contains backslash
characters (\) as path delimiters, use double
backslash characters (\\) to represent single
backslash characters.


Security Services parameters
IS_SSO_ENABLED Specifies whether Security Services is enabled for
this instance of Teamcenter.
SSO_APPLICATION_ID Application ID assigned to this instance of
Teamcenter in the Security Services application
registry. This information is required only when you
are configuring the optional Security Services.
This ID is determined when Security Services is
installed and configured. For information, see
the Security Services Installation/Customization
manual.
SSO_logon_SERVICE_URL Complete URL of the Security Services logon Service
Web application. This information is required only
when you configure the optional Security Services.
This URL is determined when Security Services
is installed and configured. For information, see
manual.
SSO_SERVICE_URL Complete URL of the Security Services Identity
Service Web application. This information is
required only when you configure the optional
Security Services.
This URL is determined when Security Services
is installed and configured. For information, see
manual.
Table E-2. Web tier optional parameters

General Parameters
webmaster E-mail address of the administrator to whom
questions and comments about this application are
addressed.


staticResourceClientCache Maximum time in seconds that a client can use a
ExpiryTime locally cached static content (for example, images or
Javascript) before requesting a fresh copy from the
server.
Setting this value too low causes the client to
unnecessarily request content. Setting this value too
high risks stale content. Typical values range from
several hours to one day.
Setting the value to 0 is valid and causes the client to
always ask for static content.
The default value is 28800 seconds (8 hours).
compressResponse Specifies whether a response to the client can be
compressed if the requesting client supports it.
Compressing the response typically yields faster
response time to the client but requires additional
processing in the Web container.
Set this parameter value based on trial and error for
your instance of the server, bandwidth, and client
access environment.
The default value is true.
cacheCompressedStatic Specifies whether responses for static resources are
ResourceOnServer cached on the server. This parameter is used only
when the compressResponse parameter is set to
true.
If the value is set to true, compressed responses for
static resources are cached on the server, memory
permitting.
If the value is set to false, the compression occurs each
time the client requests a static resource.
The default value is true.
responseCompression Threshold in bytes beyond which the server should
Threshold compress responses sent back to the client.
Typically compressing smaller responses does not
yield much compression - so all responses equal to
or smaller than this value will be sent to the client
uncompressed.
Setting the value to 0 is valid and causes the server to
compress every response sent to the client (assuming
other parameters permit compression).


The default value is 500 bytes. Change this value only

if absolutely required.
calculateResponseTime Specifies whether the group of response time filters
are on (by setting to true) or off (by setting to false).
These filters are used for instrumentation purposes
(for example, the average time spent in processing a
request from a rich client or thin client).
The response time filters should remain turned off
unless you are collecting statistics.
The default value is false.


TreeCache Parameters1
PROCESS_MAX_PER_ Maximum number of server processes per user. The
USER default value (0) turns off the constraint, that is,
specifies that there is no limit on the number of
processes per user.
QUERY_TIMEOUT Maximum time in seconds per request. The default
value (0) turns off the constraint, that is, specifies that
there is no time limit on the request.
SOFT_TIMEOUT_EDIT Time-out for edit mode servers in a busy pool.
SOFT_TIMEOUT_READ Time-out for read mode servers in a busy pool.
SOFT_TIMEOUT_ Time-out for stateless servers in a busy pool.
STATELESS
HARD_TIMEOUT_EDIT Load insensitive time-out for edit mode servers.
HARD_TIMEOUT_READ Load insensitive time-out for read mode servers.
HARD_TIMEOUT_ Load insensitive time-out for stateless servers.
STATELESS
Application Interface Web Service Parameters
AIWS_teamcenter_linking_ Name for user for logging on to Teamcenter on behalf
user_name of a remote Teamcenter application.
The default value is infodba.
For more information about AIWS, see the Application
Interface Web Service (AIWS) Configuration and
Customization Guide.
AIWS_teamcenter_linking_ Password for user for logging on to Teamcenter on
user_passwd behalf of remote Teamcenter application.
For more information about AIWS, see the Application
Interface Web Service (AIWS) Configuration and
Customization Guide.
Legacy URL support parameters


requestRedirectedTo Specifies the protocol and server, port, or domain for
accessing the thin client. The default value is the
server, port, or domain in the requested, original URL.
Use this parameter to change the protocol and server,
port, or domain information from the requested,
original URL. For example, you could use this
parameter to change a requested http://acme:8080
URL to http://web.acme.com. A typical use for this
parameter is in a cluster configuration.
replacementFor CGIBIN_IMAN Specifies the replacement for cgi-bin/iman in the
URL. Do not change the default value of tc/webclient
(this value is currently the only supported value).
redirectionWaitTime Specifies an integer representing the number of
seconds to display the URL message to users before
redirecting their requests to the new URL. The default
value is 10 seconds. The minimum value is 0.
Table E-3. Global Services context parameters

Enterprise application parameters
ApplicationInstance Specifies the name uniquely identifying the
application instance within the application server.
SSOAppID Specifies the unique value used to identify the Global
Services application to the Security Services single
sign-on (SSO) server.
LogFileLocation Specifies the name and location of the logging
configuration file. By default, this is the log4j.xml
file. If you are using the standard Global Services
logging configuration, do not change parameter
value. If you are going to customize the logging
configuration, you must create the custom file and
provide the complete path, including the file name,
as the parameter value.
TcGSBOSJNDI Specifies the Global Services business object server
(BOS) connector EJB JNDI name. The default value
is typically used.
TcGSDORJNDI Specifies the data object repository connector EJB
JNDI name. This connector is used to manage data
in the Global Services datastore. The default value
is typically used.


TcGSJDBCJNDI Specifies the JDBC connector EJB JNDI name.
This connector can be used to manage data in the
Global Services datastore or to connect any JDBC
compatible database. The default value is typically
used.
TcGSMessageServerJNDI Specifies the Global Services message server EJB
JNDI name. The default value is typically used.
TcGSNotifierReactorJNDI Specifies the Global Services notifier reactor EJB
JNDI name. The default value is typically used.
Security proxy parameters
(This solution is optional.)
global.services.proxy.service.URL Specifies the base URL for the secured enterprise
application (Global Services). For example:
http://host:port/TcGS
host and port are the application server host and the
port number used to connect to the Global Services
application, and TcGS is the context-root for the
application.
global.services.proxy.user Specifies the Global Services user the proxy client
uses to execute calls to the server.
global.services.proxy.password Specifies the password associated with the Global
Services proxy user.
global.services.proxy.client.IPs Provides a comma-separated list of authorized client
IP addresses or host names. The IP addresses can
contain digit-matching wildcards as follows:
? matches any single digit
* matches zero or more digits
For example:
192.168.0.*
matches all IP addresses from 192.168.0.0 through

192.168.0.255 and:
192.168.0.??
matches the addresses from 192.168.0.0 through

192.168.0.99.
The wildcards match digits only. Therefore, an
expression like 192.168.*.* is valid. However, an
expression like 192.168.* is not.
Also, because the * character matches zero or more
digits, the expression 192.168.1.2* matches the
following addresses:


192.168.1.2
192.168.1.20 through 192.168.1.29
192.168.1.200 through 192.168.1.255
Connector parameters
(The connector solutions are optional.)
RAC.OSGi.plugin.URL.suffix Specifies the suffix to the Global Services URL
used to call the connector OSGi plug-in through
the Jetty plug-in. The default value is typically
used. If you change the value, you must update
RAC_OSGi_PLUGIN_URL parameter in the
TeamcenterRACOSGiConfig.xml file.
TcGSConnectorJNDI Specifies the Global Services connector EJB JNDI
name. This connector provides a connection to other
instances of Global Services.
TcGSRACJNDI Specifies the Teamcenter rich client connector EJB
JNDI name.
TcGSSOAJNDI Specifies the Teamcenter services-oriented
architecture (SOA) connector EJB JNDI name.
TeamcenterConnectorJNDI Specifies the Teamcenter 2005 connector EJB JNDI
name.
TcGSEngJNDI Specifies the Engineering Process Management
connector EJB JNDI name.
TcGSEntJNDI Specifies the Enterprise Knowledge Management
connector EJB JNDI name.
TcGSOMfgJNDI Specifies the Oracle Manufacturing connector EJB
JNDI name.
TcGSSAPJNDI Specifies the SAP connector EJB JNDI name.
Teamcenter gateway to Oracle Manufacturing parameters
(This solution is optional.)
global.services.teamcenter.user Specifies the user that the gateway solution uses to

perform actions in Teamcenter.
global.services.teamcenter.password Specifies the password associated with the user
that the gateway solution uses to perform actions
in Teamcenter.
global.services.tceng2omfg.user Specifies the user that the gateway solution uses to
perform actions in Teamcenter.
global.services.tceng2omfg.password Specifies the password associated with the user
in Teamcenter.


globalservices.tceng2omfg. Specifies the location of staging directory. This
StagingDirectory directory is used to extract the PLM XML from
Teamcenter.
globalservices.OMfg.user Specifies the user that the gateway solution uses to
perform actions in Oracle Manufacturing.
globalservices.OMfg.password Specifies the password associated with the user
in Oracle Manufacturing.
globalservices.tceng2omfg.url Specifies the URL to this Global Services instance.
This value is used by Teamcenter to get status
information on specific exchanges.
globalservices.tceng2omfg.maxobjects Specifies the maximum number of rows of objects
to retrieve from the Global Services activity status
table to be displayed in the user interface.
globalservices.tceng2omfg. Specifies the format of date values sent from
engdateoutformat Teamcenter.
globalservices.tceng2omfg. Specifies the format of date values sent to
engdateinformat Teamcenter.
globalservices.tceng2omfg. Specifies the format of date values sent from Oracle
OmfgDateOutFormat Manufacturing.
globalservices.tceng2omfg. Specifies the format of date values sent to Oracle
OmfgDateInFormat Manufacturing.
globalservices.tceng2omfg. Specifies the format of date and time values sent to
OmfgDateTimeInFormat Oracle Manufacturing.
globalservices.tceng2omfg.XSLName Specifies the name of the style sheet applied to the
PLM XML file to convert it to an XML business
object.
globalservices.tceng2omfg. Specifies the name of the XML mapping file that lists
UpdateAttrFile all the attributes from Oracle Manufacturing that
can be updated in Teamcenter.
globalservices.tceng2omfg. Specifies the JNDI name of the connector Global
JNDI_NAME Services uses to connect to Teamcenter.
globalservices.tceng2omfg. Specifies the name of the configuration file that
ORACLE_CONFIG_NAME contains the configuration data required to connect
to Oracle Manufacturing.

Index
Numerics/Symbols Autonomy Intelligent Data Operating Layer

(IDOL) . . . . . . . . . . . . . . . . . . . . . . . D-6
2 Tier Teamcenter Server
Configuration . . . . . . . . . . . . . . . . . D-11
4 Tier Teamcenter Server B
Configuration . . . . . . . . . . . . . . . . . D-11 Backing up installations . . . . . . . . . . . . 6-4
Backing up Teamcenter data . . . . . . . . . 6-5
A Backup
Oracle databases . . . . . . . . . . . . . . . . 3-8
Action manager daemon . . . . . . . . . . . . 6-1 Best installation practices . . . . . . . . . . . 4-6
Action Manager Service . . . . . . . . . . . . D-9 Bounding box generation from JT . . . . . D-8
Adding features . . . . . . . . . . . . . . . . . 13-2 Bounding box generation from NX . . . . D-8
additional_applications directory . . . . . C-2 Brand Management . . . . . . . . . . . . . . D-4
advanced_installations directory . . . . . C-2 Business Modeler IDE . . . . . . . . . . . . D-11
Aerospace and Defense Client . . . . . . . . . . . . . . . . . . . . . . . D-1
Aerospace and Defense Foundation . . D-6 Digital Dashboard . . . . . . . . . . . . . D-11
Aerospace and Defense Training . . . . D-6 Four-tier server configuration . . . . . D-11
AIWS client . . . . . . . . . . . . . . . . . . . . D-7 Installing . . . . . . . . . . . . . . . . . . 8-1, 8-3
AIX Mapping Designer . . . . . . . . . . . . . D-11
Configuration parameters . . . . . . . . . . 3-3 Solution . . . . . . . . . . . . . . . . . . . . . D-1
Daemon startup scripts . . . . . . . . . . . 6-2 Start . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Kernel parameters . . . . . . . . . . . . . . . 3-3 Templates . . . . . . . . . . . . . . . . D-1, D-11
Shell limits . . . . . . . . . . . . . . . . . . . . 3-2 Two-tier server configuration . . . . . D-11
Apache HTTP Server . . . . . . . . . . . . . 12-33 Business Modeler IDE client . . . . . . . . D-1
Apache Tomcat . . . . . . . . . . . . . . . . . 12-33 Business Modeler IDE Client . . . . . . . D-11
Apple Macintosh platforms Business Modeler Templates . . . . D-1, D-11
Platform support . . . . . . . . . . . . . . . . 1-2
System requirements . . . . . . . . . . 1-2–1-3
C
Application Interface Web Service, see AIWS
client CAD Part Library for Rich Client . . . . D-10
Application servers CAD-BOM Alignment . . . . . . . . . . . . . D-4
HTTPServerTable . . . . . . . . 12-24, 12-30 Cadence Allegro Library Support . . . . . D-1,
Teamcenter application D-11
server . . . . . . . . . . . . . . . . . 2-21–2-22 Cadence Support . . . . . . . . . . . . . D-1, D-11
Web tier . . . . . . . . . . . . . . . . . . . . . 1-10 cc_integration directory . . . . . . . . . . . . C-2
ApplicationInstance . . . . . . . . . . . . . 12-11 Certification database . . . . . . . . . . . . . . 1-1
ApplicationInstance context Character set, ISO8859–1 . . . . . . . . . . . 4-3
parameter . . . . . . . . . . . . . . . . . . . . . E-9 Character sets
As-Built . . . . . . . . . . . . . . . . . . . D-7, D-10 ISO8559-1 . . . . . . . . . . . . . . . . . . . . . 1-4
ASP .NET State Service . . . . . . . . . . . D-10 UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 1-4
AutoCAD integration, GM Overlay . . . . D-7 CIFS volume data access . . . . . . . . . . . 2-22
Automatic logon, four-tier . . . . . . . . . . . 2-6 ClearCase . . . . . . . . . . . . . . . . . . . . . D-5
Automotive Edition . . . . . . . . . . . . . . . D-6 Client for Office . . . . . . . . . . . . . . . . D-10
Autonomy Client tier
IDOL server . . . . . . . . . . . . . . . . . . D-6 Four-tier . . . . . . . . . . . . . . . . . . . . . 1-10
PLM00011 C Installation on UNIX and Linux Servers Guide Index-1

Index
Two-tier . . . . . . . . . . . . . . . . . . . . . . 1-8 globalservices.tceng2omfg.

Client, Business Modeler IDE . . . . . . D-11 maxobjects . . . . . . . . . . . . . . . . . E-12
Clients globalservices.tceng2omfg.
FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-13 OmfgDateInFormat . . . . . . . . . . . E-12
Four-tier clients . . . . . . . . . . . . . . . . 1-10 globalservices.tceng2omfg.
Rich client installation . . . . . . . . . . . . 2-8 OmfgDateOutFormat . . . . . . . . . . E-12
Thin client . . . . . . . . . . . . . . . . . . . . 2-11 globalservices.tceng2omfg.
Two-tier clients . . . . . . . . . . . . . . . . . 1-8 OmfgDateTimeInFormat . . . . . . . E-12
Commands globalservices.tceng2omfg.ORACLE_
insweb . . . . . . . . . . . . . . 12-2, 16-4–16-7 CONFIG_NAME . . . . . . . . . . . . . E-12
Comprehensive Manufacturing Types . . D-8 globalservices.tceng2omfg.
Configuration StagingDirectory . . . . . . . . . . . . . E-12
Databases . . . . . . . . . . . . . . . . . . . . 3-17 globalservices.tceng2omfg.
Multi-Site Collaboration . . . . . . . . . . . 6-2 UpdateAttrFile . . . . . . . . . . . . . . E-12
Multi-Site Collaboration daemons . . . . 6-4 globalservices.tceng2omfg.
Oracle Net . . . . . . . . . . . . . . . . . . . . 3-15 XSLName . . . . . . . . . . . . . . . . . . E-12
Teamcenter’s manufacturing process globalservices.tceng2omfg.url . . . . . . E-12
management . . . . . . . . . . . . . . . . 10-1 LogFileLocation . . . . . . . . . . . . 12-11, E-9
Connector support files . . . . . . . . . . . . 12-6 RAC.OSGi.plugin.URL.suffix . . . . . . E-11
Consumer Packaged Goods SSOAppID . . . . . . . . . . . . . . . 12-11, E-9
Brand Management . . . . . . . . . . . . . D-4 TcGSBOSJNDI . . . . . . . . . . . . 12-11, E-9
CPG Materials . . . . . . . . . . . . . . . . . D-5 TcGSConnectorJNDI . . . . . . . . . . . . E-11
CPG Materials for Rich Client . . . . . D-10 TcGSDORJNDI . . . . . . . . . . . . 12-11, E-9
Packaging and Artwork . . . . . . . . . . D-4 TcGSEngJNDI . . . . . . . . . . . . . . . . . E-11
Content Management . . . . . . . . . . . . . D-4 TcGSEntJNDI . . . . . . . . . . . . . . . . . E-11
Content Management Base feature . . D-4 TcGSJDBCJNDI . . . . . . . . . . 12-11, E-10
Content Management S1000D TcGSMessageServerJNDI . . . . 12-11, E-10
feature . . . . . . . . . . . . . . . . . . . . D-6 TcGSNotifierReactorJNDI . . . 12-11, E-10
Content Management System for Rich TcGSOMfgJNDI . . . . . . . . . . . . . . . E-11
Client . . . . . . . . . . . . . . . . . . . . D-10 TcGSRACJNDI . . . . . . . . . . . . . . . . E-11
Content Management installation . . . 12-12 TcGSSAPJNDI . . . . . . . . . . . . . . . . E-11
Content Management S1000D . . . . . . . D-6 TcGSSOAJNDI . . . . . . . . . . . . . . . . E-11
Content Management System for Rich TeamcenterConnectorJNDI . . . . . . . . E-11
Client . . . . . . . . . . . . . . . . . . . . . . . D-10 CORP item creation fails . . . . . . . . . . . B-4
Context parameters Corporate server
ApplicationInstance . . . . . . . . . 12-11, E-9 Features . . . . . . . . . . . . . . . . . . D-1–D-2
global.services.proxy.password . . . . . E-10 Installing . . . . . . . . . . . . . . . . . . . . . 5-5
global.services. CPG Materials . . . . . . . . . . . . . . . . . . D-5
tceng2omfg.password . . . . . . . . . . E-11 CPG Materials for Rich Client . . . . . . D-10
global.services. Customization for eM-Server
teamcenter.password . . . . . . . . . . E-11 Integration . . . . . . . . . . . . . . . . . . . . D-8
global.services.proxy.client.IPs . . . . . E-11 Customization for Process Simulater
global.services.proxy.user . . . . . . . . . E-10 Integration . . . . . . . . . . . . . . . . . . . . D-8
global.services.tceng2omfg.user . . . . . E-11 customScripts.log file . . . . . . . . . . . . . . 3-19
global.services.teamcenter.user . . . . . E-11
globalservices.OMfg.password . . . . . . E-12 D
globalservices.OMfg.user . . . . . . . . . E-12
globalservices.tceng2omfg. Database Configuration Assistant . . . 2-21,
engdateinformat . . . . . . . . . . . . . E-12 3-17
globalservices.tceng2omfg. Database Configuration for DPV . . . . . D-7
engdateoutformat . . . . . . . . . . . . E-12 Database daemons
globalservices.tceng2omfg.JNDI_ Installation . . . . . . . . . . . . . . . . . . . D-8
NAME . . . . . . . . . . . . . . . . . . . . E-12 Starting manually . . . . . . . . . . . . . . . 6-1
Index-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Index
Database Daemons . . . . . . . . . . . . . . . D-8 E

Action Manager Service . . . . . . . . . . D-9 eBOP reports Customization . . . . . . . . D-8
Subscription Manager Service . . . . . . D-9 ECAD design management
Task Manager Service . . . . . . . . . . . D-8 Cadence Support . . . . . . . . . . . . . . D-11
Tesselation Manager Service . . . . . . . D-9 Mentor Support . . . . . . . . . . . . . . . D-11
Database services . . . . . . . . . . . . . . . . D-8 PADS Support . . . . . . . . . . . . . . . . D-11
Databases ECAD library management
Adding data directory to Cadence Allegro Library Support . . . D-11
installation . . . . . . . . . . . . . . . . . 13-2 Mentor Board Station Library
Adding database to installation . . . . . 13-3 Support . . . . . . . . . . . . . . . . . . D-11
Data imports . . . . . . . . . . . . . . . . . . 3-10 Mentor PADS Library Support . . . . D-11
Multiple database access Mentor Support . . . . . . . . . . . . . . . D-11
Four-tier rich clients . . . . . . . . . 13-4 ECAD Part Library Management . . . . . D-6
Overview . . . . . . . . . . . . . . . . . 13-4 EDA
RDV . . . . . . . . . . . . . . . . . . . . . . . . 2-21 Dataset types . . . . . . . . . . . . . . . . . D-5
Site planning . . . . . . . . . . . . . . . . . . 2-21 Server support . . . . . . . . . . . . . . . . . D-5
tceng_unpopulate_db.sql script . . . . . B-10 Standalone client . . . . . . . . . . . . . . . D-1
Templates . . . . . . . . . . . . . . . . 2-21, 3-17 EDA for Rich Client . . . . . . . . . . . . . D-10
Unpopulating in Oracle . . . . . . . . . . B-10 EDA Server Support . . . . . . . . . . . . . . D-5
dbscripts directory . . . . . . . . . . . . . . . 3-17 EDA Stand-alone Client . . . . . . . . . . D-11
dbshut utility . . . . . . . . . . . . . . . . . . . . 3-9 eIntegrator Admin . . . . . . . . . . . . . . . D-3
Destination directories . . . . . . . . . . . . . 4-3 Embedded Software Solutions
Digital Dashboard . . . . . . . . . . . . . . . D-11 Embedded Software Design Data
Directories Management . . . . . . . . . . . . . . . . D-6
WEB_ROOT . . . . . . . . . . . . . . . . . . 12-2 Embedded Software Design Data
Web_tier . . . . . . . . 12-2–12-3, 12-9, 12-12 Management for Rich Client . . . . D-10
Dispatcher . . . . . . . . . . . . . . . . . . . . . D-1 ESS . . . . . . . . . . . . . . . . . . . . . . . . D-7
Dispatcher Client . . . . . . . . . . . . . . . D-6 Embedded Software Solutions for Rich
Dispatcher Client for Rich Client . . . . D-9 Client . . . . . . . . . . . . . . . . . . . . . . . D-10
Dispatcher Server . . . . . . . . . . . . . . D-6 Embedded viewer . . . . . . . . . . . . . . . D-10
Dispatcher Client for Rich Client . . . . . D-9 Embedded visualization for rich
Dispatcher Server . . . . . . . . . . . . . . . . D-6 client . . . . . . . . . . . . . . . . . . . . . . . D-10
Installation . . . . . . . . . . . . . . . . . . . D-1 EMPS – ECAD Translation . . . . . . . . . D-6
dist_server.jar file . . . . . . . . . . . . . . . 12-35 EMPS - Foundation . . . . . . . . . . . . . . . D-6
Distributed services manager, see IDSM Enterprise tier . . . . . . . . . . . . . . . . . . 1-10
server and IDSM proxy server Environment variables
Distribution media . . . . . . . . . . . . . . . C-1 LANG . . . . . . . . . . . . . . . . . . . . . . . 14-2
Distribution server LC_ALL . . . . . . . . . . . . . . . . . . . . . 14-2
Adding Web components . . . . . . . . . 12-35 ORACLE_HOME . . . . . . . . . . . . . . . . 3-9
Changing contents . . . . . . . . . . . . . 12-35 PATH . . . . . . . . . . . . . . . . . . . . . 3-8–3-9
Installation . . . . . . . . . . . . . 12-18–12-19 TC_DATA . . . . . . . . . . . . . . . . . . 2-2, 5-7
Patching Web components . . . . . . . . . 16-6 TC_ROOT . . . . . . . . . . . . . . 2-2, 4-5, 5-6
Starting . . . . . . . . . . . . . . . . . . . . 12-34 TNS_ADMIN . . . . . . . . . . . . . . . . . . 3-15
Stopping . . . . . . . . . . . . . . . . . . . . 12-34 ERP Connect Toolkit . . . . . . . . . . . . . . D-5
Distribution server instance Error log files . . . . . . . . . . . . . . . . . . . 3-18
Installation . . . . . . . . . . . . . 12-19, 12-28 Error logs . . . . . . . . . . . . . . . . . . . . . . B-1
Web deployment . . . . . . . . . . . . . . 12-31 Error messages . . . . . . . . . . . . . . . . . . B-2
Documentation distribution image . . . . C-1 ESS Base . . . . . . . . . . . . . . . . . . . . . . D-7
DPV ESS Processor . . . . . . . . . . . . . . . . . . . D-7
Database configuration . . . . . . . . . . . D-7 ESS Software . . . . . . . . . . . . . . . . . . . D-7
GM Customization . . . . . . . . . . . . . . D-7 Export
ds_manifest.mf file . . . . . . . . . . . . . . 12-30 Oracle databases . . . . . . . . . . . . . . . . 3-8

Index
F EDA for Rich Client . . . . . . . . . . . . D-10

EDA Server Support . . . . . . . . . . . . D-5
FCC . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 EDA Stand-alone Client . . . . . . . . . D-11
Features EDA Standalone Client . . . . . . . . . . D-1
2 Tier Teamcenter Server Embedded Software Design Data
Configuration . . . . . . . . . . . . . . D-11 Management . . . . . . . . . . . . . . . . D-6
4 Tier Teamcenter Server Embedded Software Design Data
Configuration . . . . . . . . . . . . . . D-11 Management for Rich Client . . . . D-10
Add-Ons, Rich Client . . . . . . . . . . . . D-9 Embedded Software Manager for
Aerospace and Defense Foundation . . D-6 Foundation . . . . . . . . . . . . . . . . . D-7
Aerospace and Defense Training . . . . D-6 Embedded Software Manager for Rich
ASP .NET State Service . . . . . . . . . D-10 Client . . . . . . . . . . . . . . . . . . . . D-10
Bounding box generation from JT . . . D-8 EMPS – ECAD Translation . . . . . . . . D-6
Bounding box generation from NX . . . D-8 EMPS - Foundation . . . . . . . . . . . . . D-6
Brand Management . . . . . . . . . . . . . D-4 ERP Connect . . . . . . . . . . . . . . . . . . D-5
Business Modeler IDE . . . . . . . . . . D-11 ESS . . . . . . . . . . . . . . . . . . . . D-7, D-10
Business Modeler IDE client . . . . . . . D-1 ESS Base . . . . . . . . . . . . . . . . . . . . D-7
Business Modeler Templates . . . . . . . D-1 ESS Processor . . . . . . . . . . . . . . . . . D-7
CAD Part Library for Rich Client . . D-10 ESS Software . . . . . . . . . . . . . . . . . D-7
CAD-BOM Alignment . . . . . . . . . . . . D-4 Extensions for Microsoft Office . . . . D-10
Cadence Allegro Library Support . . . . D-1, Finished Product Management . . . . . D-3
D-11 FMS Server Cache . . . . . . . . . . . D-1–D-3
Cadence Support . . . . . . . . . . . D-1, D-11 Full Text Search Engine . . . . . . . . . . D-6
Client, Business Modeler IDE . . . . . D-11 Global Services . . . . . . . . . . . . . . . . D-1
Comprehensive Manufacturing Global Services Adapter . . . . . . . . . . D-3
Types . . . . . . . . . . . . . . . . . . . . . D-8 Global Services Framework . . . . D-1, D-4
Configure AutoCAD Integration for GM Global Services Monitoring GUI for Rich
Overlay . . . . . . . . . . . . . . . . . . . D-7 Client . . . . . . . . . . . . . . . . . . . . D-10
Content Management Base . . . . . . . . D-4 Global Services Preferences . . . . D-1, D-6
Content Management S1000D . . . . . . D-6 GM Customization for DPV . . . . . . . . D-7
Content Management System for Rich GM Overlay . . . . . . . . . . . . . . . . . . . D-6
Client . . . . . . . . . . . . . . . . . . . . D-10 GM Overlay for Rich Client . . . . . . . D-10
Corporate server . . . . . . . . . . . . . . . D-1 GM PAD/TWP Customization . . . . . . D-8
CPG Materials . . . . . . . . . . . . . . . . . D-5 Hierarchical Storage Management
CPG Materials for Rich Client . . . . . D-10 (HSM) . . . . . . . . . . . . . . . . . . . . D-5
Customization for eM-Server Install Libraries for AIWS Client . . . . D-7
Integration . . . . . . . . . . . . . . . . . D-8 Install Libraries for Resource
Customization for Process Simulate Browser . . . . . . . . . . . . . . . . . . . D-8
Integration . . . . . . . . . . . . . . . . . D-8 J2EE Based Server Manager . . . D-1, D-3
Database Configuration for DPV . . . . D-7 Log Manager Query Service . . . . D-1, D-3
Database Daemons . . . . . . . . . . . . . D-8 Maintenance, Repair, and Overhaul . . D-7
Action Manager Service . . . . . . . D-9 Manufacturing Process
Subscription Manager Service . . . D-9 Management . . . . . . . . . . . . . . . . D-8
Task Manager Service . . . . . . . . D-8 Mapping Designer . . . . . . . . . . . . . D-11
Tesselation Manager Service . . . . D-9 Mentor Board Station Library
Digital Dashboard . . . . . . . . . . . . . D-11 Support . . . . . . . . . . . . . . . D-1, D-11
Dispatcher . . . . . . . . . . . . . . . . . . . D-6 Mentor Expedition Library
Dispatcher Client . . . . . . . . . . . . . . . D-6 Support . . . . . . . . . . . . . . . D-1, D-11
Dispatcher Client for Rich Client . . . . D-9 Mentor PADS Library Support . . . . . D-1,
Dispatcher Server . . . . . . . . . . . . . . D-1 D-11
eBOP reports Customization . . . . . . . D-8 Mentor Support . . . . . . . . . . . . D-1, D-11
ECAD Design Management . . . . . . D-11 Microsoft Office
ECAD Library Management . . . . . . D-11 Client for Office . . . . . . . . . . . . D-10
ECAD Part Library Management . . . D-6

Index
Extensions for Microsoft Office . . D-10 Teamcenter Visualization 8 (Embedded) for

Microsoft Office client . . . . . . . . . . . D-10 Rich Client . . . . . . . . . . . . . . . . D-10
MRO As-Built . . . . . . . . . . . . . D-7, D-10 Teamcenter Visualization 8 (Stand-alone)
Multi-Site Collaboration . . . . . . . . . . D-9 for Rich Client . . . . . . . . . . . . . D-10
Multisite Collaboration IDSM Teamcenter Web Tier . . . . . . . . . . . D-10
Service . . . . . . . . . . . . . . . . . D-1, D-9 Tecnomatix . . . . . . . . . . . . . . . . . . . D-8
Multisite Collaboration ODS Trueshape generation from JT . . . . . D-8
Service . . . . . . . . . . . . . . . . . D-1, D-9 Vendor Management . . . . . . . . . . . . D-4
.NET Based Server Manager . . . . . . . D-3 Vendor Management for Rich
NX Manager for Rich Client . . . . . . D-10 Client . . . . . . . . . . . . . . . . . . . . D-10
NX UG Integration . . . . . . . . . . D-1, D-3 Web Tier for .NET . . . . . . . . . . . . . D-11
Office Client for Microsoft Office . . . D-10 Wire Harness Configuration . . . . . . . D-4
Online Help . . . . . . . . . . . . . . . . . . . D-4 Wire Harness Configuration in GM
Oracle Manufacturing Integration . . . D-3 Overlay . . . . . . . . . . . . . . . . . . . D-7
Packaging and Artwork . . . . . . . . . . D-4 Workflow to Scheduling Integration . . D-3
PAD/TWP Customization . . . . . . . . . D-8 File Management System . . . . . . . . . . 2-15
PADS Support . . . . . . . . . . . . . D-1, D-11 Installation . . . . . . . . . . . . . . . . D-1–D-3
QPL for Repeatable Digital Installation overview . . . . . . . . . . . . 2-11
Validation . . . . . . . . . . . . . . . . . . D-7 Volume server . . . . . . . . . . . . . . . . . D-2
Render Document for Rich Client . . . D-9 File security . . . . . . . . . . . . . . . . . . . . 2-15
Rich Client . . . . . . . . . . . . . . . . . . . D-9 Files
Rich Client (Lite Edition) . . . . . . . . . D-9 INSTALL_TCWEB.TZ . . . . . . . . . . . 12-2
Rich Client (Shared Disk jakarta-regexp-1.3.jar . . . . . . . . . . . . B-4
Deployment) . . . . . . . . . . . . . . . . D-9 jCO.jar . . . . . . . . . . . . . . . . . . . . . . 12-9
Rich Client 2-tier . . . . . . . . . . . . . . . D-9 jRFC12.dll . . . . . . . . . . . . . . . . . . . . 12-9
Rich Client 4-tier . . . . . . . . . . . . . . . D-9 libjRFC12.so . . . . . . . . . . . . . . . . . . 12-9
Rich Client Add-Ons . . . . . . . . . . . . D-9 librfc32.dll . . . . . . . . . . . . . . . . . . . . 12-9
Rich Client, Dispatcher Client . . . . . . D-9 librfccm.so . . . . . . . . . . . . . . . . . . . . 12-9
Sample Files . . . . . . . . . . . . . . . . . . D-3 mti.jar . . . . . . . . . . . . . . . . . . . . . . 12-7
SCM ClearCase for Foundation . . . . . D-5 mtiems.jar . . . . . . . . . . . . . . . . . . . . 12-7
SCM ClearCase for Rich Client . . . . D-10 ojdbc14.jar . . . . . . . . . . . . . . . . . . . 12-9
Single Sign-on for Rich Client . . . . . D-10 teamcenter.ini . . . . . . . . . . . . . . . . . 14-1
Spatial Search . . . . . . . . . . . . . . . . . D-8 Finished Product Management . . . . . . . D-3
Specification Manager . . . . . . . . . . . D-5 FMS
Specification Manager for Rich FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Client . . . . . . . . . . . . . . . . . . . . D-10 FSC . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Stand-alone Applications . . . . . . . . D-11 Master configuration file . . . . . . . . . . 2-13
Structure Search . . . . . . . . . . . . . . . D-8 See File Management System . . . . . . 2-11
Teamcenter Automotive Edition . . . . D-6 FMS server cache . . . . . . . . . . . . . . . . D-2
Teamcenter Corporate Server . . . . . . D-2 Fms_BootStrap_Urls preference . . . . . . . 5-4
Teamcenter Extensions for Microsoft Four-tier architecture
Office . . . . . . . . . . . . . . . . . . . . D-10 Installation overview . . . . . . . . . . . . . 2-5
Teamcenter File Services . . . . . . D-1–D-2 Overview . . . . . . . . . . . . . . . . . . . . . 1-10
Teamcenter for Reporting and Troubleshooting deployment . . . . . . . B-5
Analytics . . . . . . . . . . . . . . . . . . D-5 FSC
Teamcenter Foundation . . . . . . . D-1–D-2 Installation overview . . . . . . . . . . . . 2-12
Teamcenter Linking . . . . . . . . . . . . . D-5 Transient server . . . . . . . . . . . . . . . 2-12
Teamcenter Manufacturing . . . . . . . . D-8 Full Text Search Engine . . . . . . . . . . . D-6
Teamcenter Rich Client . . . . . . . . . . D-9
Teamcenter Rich Client 2-tier . . . . . . D-2 G
Teamcenter Rich Client 4-tier . . . . . . D-2
Teamcenter Security Services . . . . . . D-4 GDIS database configuration . . . . . . . . D-7
Teamcenter Visualization . . . . . . . . . D-5 genius2mrm_copy_files.ucl
script . . . . . . . . . . . . . . . . . . . . 10-6–10-7

Index
Genius4000 data migration . . . . . . . . . 10-6 CORP item creation fails . . . . . . . . . B-4

Global Services . . . . . . . . . . . . . . 2-17, D-3 GM Overlay for Rich Client . . . . . . . . D-10
Features . . . . . . . . . . . . . . . . . . . . . D-1 GM Overlay, AutoCAD integration . . . . D-7
Global Services Adapter . . . . . . . . . . . . D-3 GM Overlay, Wire Harness
Global Services Framework . . . . . . D-1, D-4 Configuration . . . . . . . . . . . . . . . . . . D-7
Global Services installation . . . . . . . . . 12-9 GM PAD/TWP Customization . . . . . . . . D-8
Global Services Monitoring GUI for Rich
Client . . . . . . . . . . . . . . . . . . . . . . . D-10 H
Global Services Preferences . . . . . . D-1, D-6
global.services.tceng2omfg.password Hebrew language . . . . . . . . . . . . . . . . 14-5
parameter . . . . . . . . . . . . . . . . . . . . . E-11 Heterogeneous network environment . . 2-22
global.services.teamcenter.password Hewlett-Packard HP-UX, Java
parameter . . . . . . . . . . . . . . . . . . . . . E-11 configuration . . . . . . . . . . . . . . . . . . . . 1-4
global.services.proxy.client.IPs context Hierarchical Storage Management
parameter . . . . . . . . . . . . . . . . . . . . . E-11 (HSM) . . . . . . . . . . . . . . . . . . . . . . . D-5
global.services.proxy.password context Homogeneous network environment . . . 2-21
parameter . . . . . . . . . . . . . . . . . . . . . E-10 HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
global.services.proxy.user context Kernel parameter requirements . . . . . 3-3
parameter . . . . . . . . . . . . . . . . . . . . . E-10 HP-UX, kernel parameters . . . . . . . . . . B-8
global.services.tceng2omfg.user HSM . . . . . . . . . . . . . . . . . . . . . . . . . D-5
parameter . . . . . . . . . . . . . . . . . . . . . E-11 HTML pages . . . . . . . . . . . . . . . . . . . 12-19
global.services.teamcenter.user
parameter . . . . . . . . . . . . . . . . . . . . . E-11 I
globalservices.OMfg.password
parameter . . . . . . . . . . . . . . . . . . . . . E-12 ICD files, copying
globalservices.OMfg.user parameter . . . E-12 Global Services . . . . . . . . . . . . . . . . 12-9
globalservices.tceng2omfg.engdateinformat Teamcenter Web tier . . . . . . . . . . . . 12-3
parameter . . . . . . . . . . . . . . . . . . . . . E-12 IDOL . . . . . . . . . . . . . . . . . . . . . . . . . D-6
globalservices.tceng2omfg.engdateoutformat IDOL server, Autonomy . . . . . . . . . . . . D-6
parameter . . . . . . . . . . . . . . . . . . . . . E-12 IDSM proxy server . . . . . . . . . . . . . . . . 2-4
globalservices.tceng2omfg.JNDI_NAME IDSM server . . . . . . . . . . . . . . . . . . . . . 2-3
parameter . . . . . . . . . . . . . . . . . . . . . E-12 IDSM Service . . . . . . . . . . . . . . . . . . . D-9
globalservices.tceng2omfg.maxobjects IDSM_permitted_sites preference . . . . . . 6-3
parameter . . . . . . . . . . . . . . . . . . . . . E-12 images directory . . . . . . . . . . . . . . . . 12-31
globalservices.tceng2omfg.OmfgDateInFormat Imports . . . . . . . . . . . . . . . . . . . . . . . 3-10
parameter . . . . . . . . . . . . . . . . . . . . . E-12 infodba . . . . . . . . . . . . . . . . . . . . . 1-4, 2-22
globalservices.tceng2omfg. Install images for connectors . . . . . . . . 12-6
OmfgDateOutFormat parameter . . . . . E-12 Install Libraries for AIWS Client . . . . . D-7
globalservices.tceng2omfg. INSTALL_TCWEB.EXE file . . . . . . . . . 12-2
OmfgDateTimeInFormat Installation
parameter . . . . . . . . . . . . . . . . . . . . . E-12 Best practices . . . . . . . . . . . . . . . . . . 4-6
globalservices.tceng2omfg.ORACLE_ Creating a configuration . . . . . . . . . . 13-1
CONFIG_NAME parameter . . . . . . . . E-12 Distribution server . . . . . . . . . . . . . 12-19
globalservices.tceng2omfg.StagingDirectory Distribution server instance . . . . . . 12-28
parameter . . . . . . . . . . . . . . . . . . . . . E-12 Modifying a configuration . . . . . . . . . 13-2
globalservices.tceng2omfg.UpdateAttrFile Oracle . . . . . . . . . . . . . . . . . . . 2-21, 3-10
parameter . . . . . . . . . . . . . . . . . . . . . E-12 Over-the-Web . . . . . . . . . . . . . 1-8, 12-19
globalservices.tceng2omfg.XSLName Rich client instance . . . . . . . . . . . . 12-21
parameter . . . . . . . . . . . . . . . . . . . . . E-12 Silent . . . . . . . . . . . . . . . . . . . . . . . 15-1
globalservices.tceng2omfg.url Teamcenter File Services . . . . . . . . . . 4-4
parameter . . . . . . . . . . . . . . . . . . . . . E-12 Teamcenter servers . . . . . . . . . . . . . . 5-1
GM Customization for DPV . . . . . . . . . D-7 Using TEM . . . . . . . . . . . . . . . 1-8, 12-19
GM Overlay . . . . . . . . . . . . . . . . . . . . D-6 Web Application Manager . . . . . . . . . 12-2

Index
installed_programs.dat file . . . . . . . . . . . 4-6 listener.ora file . . . . . . . . . . . . . . . 3-9, 3-15

installed.html file . . . . . . . . . . . . . . . 12-31 Locale setting . . . . . . . . . . . . . . . . . . . 14-1
installfailed.html file . . . . . . . . . . . . . 12-31 Locale setting, overriding . . . . . . . . . . . 14-1
Installing Localization
Business Modeler IDE . . . . . . . . . 8-1, 8-3 Converting to Unicode . . . . . . . . . . . 14-5
Templates . . . . . . . . . . . . . . . . . . . . . 9-1 Hebrew language . . . . . . . . . . . . . . . 14-5
installing.html file . . . . . . . . . . . . . . . 12-31 Rich client . . . . . . . . . . . . . . . . . . . . 14-5
insweb command . . . . . . . . . . . . . . . . 12-2, Thin client . . . . . . . . . . . . . . . . . . . . 14-5
12-19, 12-28, 12-35, 16-4–16-7 localization directory . . . . . . . . . . . . . . C-2
Integrations Log Manager Query Service . . . . . . . . . D-1
ClearCase . . . . . . . . . . . . . . . . . . . D-10 Installation . . . . . . . . . . . . . . . . D-1, D-3
Microsoft Office . . . . . . . . . . . . . . . D-10 LogFileLocation . . . . . . . . . . . . . . . . 12-11
SCM ClearCase . . . . . . . . . . . . . . . D-10 LogFileLocation context parameter . . . . E-9
Internationalization Logon, automatic . . . . . . . . . . . . . . . . . 2-6
web_gen_xml utility . . . . . . . . . . . . . 14-3
web_gen_xml.dat file . . . . . . . . . . . . 14-3 M
webstrings.xml file . . . . . . . . . . . . . . 14-3
ISO8559-1 character set . . . . . . . . . . . . 1-4 Macintosh platforms
ISO8559-1 mode . . . . . . . . . . . . . . . . . . 4-4 Platform support . . . . . . . . . . . . . . . . 1-2
ISO8859–1 character set . . . . . . . . . . . . 4-3 System requirements . . . . . . . . . . 1-2–1-3
Maintenance packs . . . . . . . . . . . . . . . 16-1
J Maintenance, Repair, and Overhaul . . . D-7
Manifest file . . . . . . . . . . . . . . . . . . . 12-30
J2EE based server manager . . . . . . . . 1-10, Manufacturing content kit . . . . . . . . . . 10-1
2-2, 5-6, 7-5 Manufacturing Process Management . . D-8
J2EE Based Server Manager . . . . . D-1, D-3 Manufacturing Tooling Library . . . . . . 10-2
jakarta-regexp-1.3.jar file . . . . . . . . . . . B-4 Mapping Designer . . . . . . . . . . . . . . . D-11
Java . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Master configuration file . . . . . . . . . . . 2-13
Java Runtime Environment . . . . . . . . . 12-2 Media, distribution . . . . . . . . . . . . . . . C-1
JBoss Cache TreeCache . . . . . . . . . . . . 7-1, Memory management . . . . . . . . . . . . . . 8-5
12-5, 13-7, E-8 Mentor Board Station Library
jCO.jar file . . . . . . . . . . . . . . . . . . . . . 12-9 Support . . . . . . . . . . . . . . . . . . D-1, D-11
jRFC12.dll file . . . . . . . . . . . . . . . . . . 12-9 Mentor Expedition Library support . . D-11
Mentor Expedition Library Support . . . D-1
K Mentor PADS Library Support . . . . . . . D-1
Mentor support . . . . . . . . . . . . . . . . . D-11
Kernel parameters . . . . . . . . . . . . 3-2, B-8 Mentor Support . . . . . . . . . . . . . . . . . D-1
Microsoft Office client . . . . . . . . . . . . D-10
L Microsoft Office extensions . . . . . . . . . D-10
Migration, Genius4000 data . . . . . . . . . 10-6
LANG variable . . . . . . . . . . . . . . . . . . 14-2 MRO As-Built . . . . . . . . . . . . . . . D-7, D-10
launcherror.html file . . . . . . . . . . . . . 12-31 mti.jar file . . . . . . . . . . . . . . . . . . . . . 12-7
Launching mtiems.jar file . . . . . . . . . . . . . . . . . . 12-7
Business Modeler IDE . . . . . . . . . . . . 8-6 Multi-Site Collaboration . . . . . . . . . . . D-9
LC_ALL variable . . . . . . . . . . . . . . . . 14-2 Configuring daemons . . . . . . . . . . . . . 6-4
libjRFC12.so file . . . . . . . . . . . . . . . . . 12-9 IDSM service . . . . . . . . . . . . . . . . . . D-1
Libraries . . . . . . . . . . . . . . . . . . . . . . D-7 Installation . . . . . . . . . . . . . . . . . . . D-1
librfc32.dll file . . . . . . . . . . . . . . . . . . 12-9 Local disk installation . . . . . . . . . . . . 4-3
librfccm.so file . . . . . . . . . . . . . . . . . . . 12-9 ODS service . . . . . . . . . . . . . . . . . . . D-1
Licensing level Postinstallation tasks . . . . . . . . . . . . . 6-2
Author . . . . . . . . . . . . . . . . . . . . . . . 4-1 Proxy server . . . . . . . . . . . . . . . . . . D-1
Consumer . . . . . . . . . . . . . . . . . . . . . 4-1 Wide area networks . . . . . . . . . . . . . . 6-2
Linux considerations . . . . . . . . . . . . . . . 1-4 Multi-site services . . . . . . . . . . . . . . . . D-9
Listener processes . . . . . . . . . . 3-8–3-9, 3-15 Multiple database access

Index
Four-tier rich clients . . . . . . . . . . . . . 13-4 Online Help . . . . . . . . . . . . . . . . . . . . D-4

Overview . . . . . . . . . . . . . . . . . . . . . 13-4 Operating system accounts . . . . . . 1-4, 2-22
Multiple EAR file support . . . . . . . . . 12-17 Operating system support . . . . . . . . . . . 1-1
Oracle
N Data imports . . . . . . . . . . . . . . . . . . 3-10
Database Configuration Assistant . . 2-21,
native2ascii utility . . . . . . . . . . . . . . . 14-6 3-17
.NET based server manager . . . . . . . . . 1-10 Database creation . . . . . . . . . . . . . . 3-17
.NET Based Server Manager Database export . . . . . . . . . . . . . . . . . 3-8
NET Based Server Manager . . . . . . . D-3 Database planning . . . . . . . . . . . . . . 2-21
.NET State Service . . . . . . . . . . . . . . D-10 Database upgrades . . . . . . . . . . . 3-8, 3-10
NET Web tier . . . . . . . . . . . . . . . . . . D-11 Installation . . . . . . . . . . . . . . . 2-21, 3-10
ASP .NET State Service . . . . . . . . . D-10 Kernel parameters . . . . . . . . . . . . . . . 3-2
.NET Web tier . . . . . . . . . . . . . . . . . . D-11 Listener processes . . . . . . . . 3-8–3-9, 3-15
ASP .NET State Service . . . . . . . . . D-10 Net configuration . . . . . . . . . . . . . . . 3-15
Server manager . . . . . . . . . . . . . . . . 1-10 oerr utility . . . . . . . . . . . . . . . . . . . . B-8
Windows . . . . . . . . . . . . . . . . . . . . . 1-10 Required version . . . . . . . . . . . . 3-16, 5-7
Network Folders Semaphore resources . . . . . . . . . . . . . 3-2
Description . . . . . . . . . . . . . . . . . . . . 1-8 Shared memory resources . . . . . . . . . . 3-2
Network Information Services . . . . . . . . 6-1 Site planning . . . . . . . . . . . . . . . . . . 2-21
Networks Software distribution image . . . . . . . C-1
Client installation . . . . . . . . . . . . . . 2-22 Uninstallation . . . . . . . . . . . . . . . . . 18-2
Heterogeneous network Unpopulating database . . . . . . . . . . B-10
environment . . . . . . . . . . . . . . . . 2-22 Oracle Manufacturing Integration . . . . D-3
Homogeneous network Oracle Net Assistant . . . . . . . . . . . . . . 3-15
environment . . . . . . . . . . . . . . . . 2-21 ORACLE_HOME environment
Site planning . . . . . . . . . . . . . . . . . . . 2-1 variable . . . . . . . . . . . . . . . . . . . . . . . 3-9
NFS volume data access . . . . . . . . . . . 2-22 oratab utility . . . . . . . . . . . . . . . . . . . . 3-9
NIS Plus . . . . . . . . . . . . . . . . . . . . . . . 6-1 otw_installer.jar file . . . . . . . . . . . . . . 12-31
NX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 otw.html file . . . . . . . . . . . . . . . . . . . 12-32
NX Manager for Rich Client . . . . . . . . D-10 Over-the-Web Installer . . . . . . . . . . . 12-19,
NX UG Integration . . . . . . . . . . . . D-1, D-3 12-22–12-23, 12-29, 12-31, 16-4–16-6
Over-the-Web rich client . . . . . . . . . . 12-18
O
P
Object directory services, see ODS server and
ODS proxy server Packaging and Artwork . . . . . . . . . . . . D-4
ODS proxy server . . . . . . . . . . . . . . . . . 2-3 PAD/TWP Customization . . . . . . . . . . . D-8
ODS server . . . . . . . . . . . . . . . . . . . . . . 2-3 PADS library support . . . . . . . . . . . . D-11
ODS Service . . . . . . . . . . . . . . . . . . . . D-9 PADS Support . . . . . . . . . . . . . . D-1, D-11
ODS_permitted_sites preference . . . . . . . 6-3 Parameters
ODS_searchable_sites preference . . . . . . 6-3 global.services.proxy.service.URL . . . E-10
ODS_site preference . . . . . . . . . . . . . . . 6-3 Kernel . . . . . . . . . . . . . . . . . . . . . . B-8
ojdbc14.jar file . . . . . . . . . . . . . . . . . . 12-9 Web tier . . . . . . . . . . . . . . . . . . . . . E-1
Online help . . . . . . . . . . . . . . . . . . . . . 12-2 Patches . . . . . . . . . . . . . . . . . . . . . . . 16-1
Distribution image . . . . . . . . . . . . . . C-2 Patching rich client
File access . . . . . . . . . . . . . . . . . . . . 2-19 Described . . . . . . . . . . . . . . . . . . . . 16-3
Installation . . . . . . . . . . . . . . . 12-4, D-4 Silently . . . . . . . . . . . . . . . . . . . . . . 16-4
Installation alternatives . . . . . . . . . . 2-18 Using Over-the-Web Installer . . . . . . 16-4
Over-the-Web access . . . . . . . . . . . . . 2-19 Patching Teamcenter’s lifecycle
Rich client . . . . . . . . . . . . . . . . . . . . 2-19 visualization . . . . . . . . . . . . . . . . . . . 16-5
tchelp.jar file . . . . . . . . 5-1, 5-8, 12-4, D-4 Patching the server . . . . . . . . . . . . . . . 16-2
Thin client . . . . . . . . . . . . . . . . . . . . 2-18 Patching thin client . . . . . . . . . . . . . . . 16-7
Troubleshooting . . . . . . . . . . . . . . . . B-2 PATH environment variable . . . . . . . 3-8–3-9

Index
Platform support . . . . . . . . . . . . . . . . . . 1-1 Repeatable Digital Validation . . . . . . . . D-7

POM transmit schema files . . . . . . . . . . 6-3 Requirements
portal directory . . . . . . . . . . . . . . . . . . C-2 Database . . . . . . . . . . . . . . . . . . . . . . 1-1
portal_localization.jar file . . . . . . . . . . 14-5 Java . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
portalHelpPage property . . . . . . . . . . . B-2 Operating systems . . . . . . . . . . . . . . . 1-1
Postinstallation tasks . . . . . . . . . . . . . . 6-1 Resource Browser, libraries . . . . . . . . . D-8
Postupgrade tasks . . . . . . . . . . . . . . . . . 6-1 Resource Manager, Genius4000 data
Preferences migration . . . . . . . . . . . . . . . . . . . . . 10-6
Fms_BootStrap_Urls . . . . . . . . . . . . . 5-4 Resource tier
IDSM_permitted_sites . . . . . . . . . . . . 6-3 Four-tier . . . . . . . . . . . . . . . . . . . . . 1-11
ODS_permitted_sites . . . . . . . . . . . . . 6-3 Two-tier . . . . . . . . . . . . . . . . . . . . . . 1-8
ODS_searchable_sites . . . . . . . . . . . . 6-3 Rich client
ODS_site . . . . . . . . . . . . . . . . . . . . . . 6-3 Deployment over the Web . . . . . . . . 12-18
TC_publishable_classes . . . . . . . . . . . 6-3 Description . . . . . . . . . . . . . . . . . . . . 1-7
TC_Security_Level . . . . . . . . . . . . . . 2-15 Four-tier . . . . . . . . . . . . . . . . . . D-2, D-9
TC_transfer_area . . . . . . . . . . . . . . . . 6-3 Installing patches . . . . . . . . . . . . . . 16-3
WEB_core_help_server . . . 2-19–2-20, B-2 Language display configuration . . . . . 14-1
WEB_default_site_deployed_app_ Localization . . . . . . . . . . . . . . . . . . . 14-5
name . . . . . . . . . . . . . . . . . . . . . B-3 Online help . . . . . . . . . . . . . . . 2-19, B-2
WEB_help_server . . . . . . 2-19–2-20, B-2 Overview . . . . . . . . . . . . . . . . . . . . . . 1-7
Preinstallation tasks . . . . . . . . . . . . . . . 4-1 Two-tier . . . . . . . . . . . . . . . . . . D-2, D-9
Prerequisite software . . . . . . . . . . . . . . 1-1 Rich Client (Lite Edition) . . . . . . . . . . . D-9
Prerequisites Rich Client (Shared Disk Deployment) . . D-9
Character set . . . . . . . . . . . . . . . . . . . 4-3 Rich Client Add-Ons . . . . . . . . . . . . . . D-9
GM Overlay . . . . . . . . . . . . . . . . . . . . 4-3 Rich client distribution server, see Distribution
Problem Reports (PRs) . . . . . . . . . . . . . 16-8 server
Programs Rich client distribution server instance, see
Web Application Manager . . . . . 16-4–16-7 Distribution server instance
Properties, portalHelpPage . . . . . . . . . B-2 Rich client instance
Proxy WAR file (WebLogic) . . . . . 12-6, 12-13 Deployment . . . . . . . . . . . . . . . . . . 12-31
Installation . . . . . . . . . . . . . . . . . . 12-21
Q Rich client instance, four-tier . . . . . . . 12-28
Rich client solutions, patching . . . . . . . 16-3
QPL for Repeatable Digital Validation . . D-7 RMI registry
QPL server . . . . . . . . . . . . . . . . . . . . . . 2-4 Port number . . . . . . . . . . . . . . . . . 12-21
Starting . . . . . . . . . . . . . . . . . . . . 12-34
R Stopping . . . . . . . . . . . . . . . . . . . . 12-35
RAC.OSGi.plugin.URL.suffix context S
parameter . . . . . . . . . . . . . . . . . . . . . E-11
rc.ugs file . . . . . . . . . . . . . . . . . . . . . . . 6-2 Sample files . . . . . . . . . . . . . . . . . . . . D-3
rc.ugs.actionmgrd script . . . . . . . . . . . . . 6-1 Sample Files . . . . . . . . . . . . . . . . . . . . D-3
rc.ugs.subscriptionmgrd script . . . . . . . . 6-2 SCM ClearCase for Foundation . . . . . . D-5
rc.ugs.task_monitor script . . . . . . . . . . . 6-2 SCM ClearCase for Rich Client . . . . . D-10
RDV Security Services . . . . . . . . . . . . . . . . 2-17
Database instance . . . . . . . . . . . . . . 2-21 Semaphore resources . . . . . . . . . . . . . . . 3-2
QPL server . . . . . . . . . . . . . . . . . . . . 2-4 Server
README file . . . . . . . . . . . . . . . . . . . 16-8 Installing patches . . . . . . . . . . . . . . 16-2
Remote Method Invocation . . . . 12-21, 12-34 Server manager
Removing features . . . . . . . . . . . . . . . 13-2 J2EE . . . . . . . . . . . . . . . . . . . . . . . D-3
Render Document for Rich Client . . . . . D-9 J2EE based . . . . . . . . . . . . . 1-10, 2-2, 5-6
Render Manager J2EE based, starting . . . . . . . . . . . . . 7-5
Installation . . . . . . . . . . . . . . . . . . . D-9 .NET . . . . . . . . . . . . . . . . . . . . . . . . D-3
Required features . . . . . . . . . . . . . . D-9 .NET based . . . . . . . . . . . . . . . . 1-10, 2-2

Index
Server, patching . . . . . . . . . . . . . . . . . 16-2 mtiems.jar . . . . . . . . . . . . . . . . . . . . 12-7

Services Oracle manufacturing connector . . . . 12-9
Action Manager . . . . . . . . . . . . . . . . D-9 SAP connector . . . . . . . . . . . . . . . . . 12-9
ASP .NET State Service . . . . . . . . . D-10 Teamcenter Enterprise connector . . . 12-7
IDSM Service . . . . . . . . . . . . . . . . . D-9
ODS Service . . . . . . . . . . . . . . . . . . D-9 T
Subscription Manager . . . . . . . . . . . D-9
Task Manager . . . . . . . . . . . . . . . . . D-8 Task Manager Service . . . . . . . . . . . . . D-8
Tesselation Manager . . . . . . . . . . . . D-9 Task monitor daemon . . . . . . . . . . . . . . 6-2
Shared Disk Deployment, rich client . . . D-9 TC_auto_login preference . . . . . . . . . . . 2-6
Shared memory resources . . . . . . . . . . . 3-2 TC_DATA environment variable . . . . 2-2, 5-7
Silent installation . . . . . . . . . . . . . . . . 15-1 TC_publishable_classes preference . . . . . 6-3
Silent patching . . . . . . . . . . . . . . . . . . 16-4 TC_ROOT environment variable . . . . . 2-2,
Single sign-on for rich client . . . . . . . . D-10 4-5, 5-6
Site planning . . . . . . . . . . . . . . . . . . . . 2-1 TC_Security_Level preference . . . . . . . 2-15
Software distribution image . . . . . . . . . C-1 TC_transfer_area preference . . . . . . . . . 6-3
Software requirements . . . . . . . . . . . . . 1-1 tceng_unpopulate_db.sql script . . . . . . . B-10
Application servers . . . . . . . . . . . . . 12-2 TCFS . . . . . . . . . . . . . . . . . . . . . . D-1–D-2
Java . . . . . . . . . . . . . . . . . . . . . . . . 12-2 tcfs service . . . . . . . . . . . . . . . . . . . . . . 6-1
Solutions TcGSBOSJNDI . . . . . . . . . . . . . . . . . 12-11
Business Modeler IDE . . . . . . . . . . . D-1 TcGSBOSJNDI context parameter . . . . E-9
Corporate Server . . . . . . . . . . . . . . . D-1 TcGSConnectorJNDI context
Dispatcher (Dispatcher Server) . . . . . D-1 parameter . . . . . . . . . . . . . . . . . . . . . E-11
EDA Standalone Client . . . . . . . . . . D-1 TcGSDORJNDI . . . . . . . . . . . . . . . . 12-11
Global Services . . . . . . . . . . . . . . . . D-1 TcGSEngJNDI context parameter . . . . E-11
Log Manager Query Service . . . . . . . D-1 TcGSEntJNDI context parameter . . . . . E-11
Multisite Collaboration Proxy TcGSJDBCJNDI . . . . . . . . . . . . . . . . 12-11
Server . . . . . . . . . . . . . . . . . . . . D-1 TcGSJDBCJNDIl context parameter . . . E-10
Rich Client 2-tier . . . . . . . . . . . . . . . D-2 TcGSMessageServerJNDI . . . . . . . . . 12-11
Rich Client 4-tier . . . . . . . . . . . . . . . D-2 TcGSMessageServerJNDI context
Volume Server . . . . . . . . . . . . . . . . . D-2 parameter . . . . . . . . . . . . . . . . . . . . . E-10
Spatial Search . . . . . . . . . . . . . . . . . . D-8 TcGSNotifierReactorJNDI . . . . . . . . . 12-11
Specification Manager . . . . . . . . . . . . . D-5 TcGSNotifierReactorJNDI context
Specification Manager for Rich parameter . . . . . . . . . . . . . . . . . . . . . E-10
Client . . . . . . . . . . . . . . . . . . . . . . . D-10 TcGSOMfgJNDI context parameter . . . E-11
SQL*Plus utility . . . . . . . . . . . . . . . . . B-10 TcGSRACJNDI context parameter . . . . E-11
SSOAppID . . . . . . . . . . . . . . . . . . . . 12-11 TcGSSAPJNDI context parameter . . . . E-11
SSOAppID context parameter . . . . . . . E-9 TcGSSOAJNDI context parameter . . . . E-11
Stand-alone application viewer . . . . . . D-10 Teamcenter
Stand-alone Applications Installation . . . . . . . . . . . . . . . . . . . . 5-1
EDA Stand-alone Client . . . . . . . . . D-11 Uninstallation . . . . . . . . . . . . . . . . . 18-1
start_rmi file . . . . . . . . . . . . . . . . . . 12-34 Teamcenter application server . . . 2-21–2-22
start_server file . . . . . . . . . . . . . . . . . 12-34 Teamcenter Automotive Edition . . . . . . D-6
Starting Teamcenter Engineering 2005/2007 . . . 12-8
Business Modeler IDE . . . . . . . . . . . . 8-6 Teamcenter Engineering Portal
Starting Teamcenter’s Integration for directory . . . . . . . . . . . . . . . . . . . . . . 12-7
Microsoft Office . . . . . . . . . . . . . . . . . 10-2 Teamcenter Engineering V9
stop_server file . . . . . . . . . . . . . . . . . 12-35 connector . . . . . . . . . . . . . . . . . . . . . 12-7
Structure Search . . . . . . . . . . . . . . . . . D-8 Teamcenter Enterprise connector, required
Subscription manager daemon . . . . . . . . 6-2 files . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Subscription Manager Service . . . . . . . D-9 Teamcenter Environment Manager . . . . 5-1,
Sun ONE . . . . . . . . . . . . . . . . . . . . . 12-33 16-2, 16-4
Support files Installation log files . . . . . . . . . . . . . B-1

Index
Removing features . . . . . . . . . . . . . . 13-2 Templates, database . . . . . . . . . . 2-21, 3-17

Uninstalling . . . . . . . . . . . . . . . . . . 18-1 Terminating Teamcenter sessions . . . . . . 6-5
Teamcenter Environment Manager Tesselation Manager Service . . . . . . . . D-9
(TEM) . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Thin client
Teamcenter File Services Description . . . . . . . . . . . . . . . . . . . . 1-7
Heterogeneous environments . . . . . . 2-22 FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Installation . . . . . . . . . . . . . 4-4, D-1–D-2 Fms_BootStrap_Urls preference . . . . . 5-4
Installation overview . . . . . . . . . . . . 2-11 Hebrew language . . . . . . . . . . . . . . . 14-5
Local disk installation . . . . . . . . . . . . 4-3 Installation . . . . . . . . . . . . . . . . . . . . 2-6
Security levels . . . . . . . . . . . . . . . . . 2-15 Installation overview . . . . . . . . . . . . 2-11
Volume server . . . . . . . . . . . . . . . . . D-2 Installing patches . . . . . . . . . . . . . . 16-7
Teamcenter File Services server . . . . . . 2-15 Localization . . . . . . . . . . . . . . . 14-4–14-5
Teamcenter for Reporting and Localized text . . . . . . . . . . . . . . . . . 14-3
Analytics . . . . . . . . . . . . . . . . . . . . . D-5 Migrating legacy URLs . . . . . . . . . . 12-14
Teamcenter Foundation . . . . . . . . . D-1–D-2 Online help . . . . . . . . . . . . . . . 2-18, B-2
Teamcenter Integration for NX/NX Integration Upgrading legacy URLs . . . . . . . . . 12-14
Configuration . . . . . . . . . . . . . . D-1, D-3 Thin client solutions, patching . . . . . . . 16-7
Overview . . . . . . . . . . . . . . . . . . . . . . 4-5 TNS_ADMIN environment variable . . . 3-15
Teamcenter Linking . . . . . . . . . . . . . . D-5 tnslsnr process . . . . . . . . . . . . . . . 3-9, 3-15
Installation . . . . . . . . . . . . . . . . . . . D-5 tnsnames.ora file . . . . . . . . . . . . . . 3-9, 3-15
Site planning . . . . . . . . . . . . . . . . . . 2-17 Tomcat . . . . . . . . . . . . . . . . . . . . . . . 12-33
Teamcenter Security Services . . . . . . . . D-4 Translation service . . . . . . . . . . . . . . . D-6
Teamcenter Visualization . . . . . . . . . . D-5 Translation Services for Rich Client . . . D-9
Teamcenter visualization for rich TreeCache parameters . . 7-1, 12-5, 13-7, E-8
client . . . . . . . . . . . . . . . . . . . . . . . D-10 Troubleshooting . . . . . . . . . . . . . . . . . B-2
Teamcenter Web Tier . . . . . . . . . . . . D-10 Four-tier deployment . . . . . . . . . . . . B-5
Teamcenter’s Automotive Edition–GM Online help . . . . . . . . . . . . . . . . . . . B-2
Overlay . . . . . . . . . . . . . . . . . . . . . . D-6 Oracle . . . . . . . . . . . . . . . . . . . . . . . B-8
Teamcenter’s Client for Microsoft Server installation . . . . . . . . . . . . . . B-1
Office . . . . . . . . . . . . . . . . . . . . . . . D-10 Trueshape generation from JT . . . . . . . D-8
Teamcenter’s engineering process Tutorials . . . . . . . . . . . . . . . . . . . . . . . 8-6
management URLs, migrating to Teamcenter Two-tier architecture
8 . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14 Deployment . . . . . . . . . . . . . . . . . . . 1-10
Teamcenter’s Extensions for Microsoft Installation overview . . . . . . . . . . . . . 2-4
Office . . . . . . . . . . . . . . . . . . . . . . . D-10 Overview . . . . . . . . . . . . . . . . . . . . . . 1-8
Teamcenter’s lifecycle visualization . . . . 16-5
Embedded viewer . . . . . . . . . . . . . . D-10 U
Installation . . . . . . . . . . . . . . . . . . . 2-16
Stand-alone application viewer . . . . D-10 UGS_LICENSE_SERVER environment
Teamcenter’s maintenance, repair, and variable . . . . . . . . . . . . . . . . . . . . . . . 4-2
overhaul . . . . . . . . . . . . . . . . . . . . . . D-7 Unicode . . . . . . . . . . . . . . . . . . . . . . . 14-5
Teamcenter’s manufacturing process Uninstallation
management . . . . . . . . . . . . . . . . . . . 10-1 Oracle . . . . . . . . . . . . . . . . . . . . . . . 18-2
Comprehensive manufacturing Teamcenter . . . . . . . . . . . . . . . . . . . 18-1
types . . . . . . . . . . . . . . . . . . . . . D-8 UNIX SAP library files . . . . . . . . . . . . 12-9
Resource Browser . . . . . . . . . . . . . . D-8 Unpopulation of Oracle database . . . . . B-10
Sample data population . . . . . . . . . . 10-2 Update a template . . . . . . . . . . . . . . . . 9-2
TeamcenterConnectorJNDI context Upgrade
parameter . . . . . . . . . . . . . . . . . . . . . E-11 Oracle databases . . . . . . . . . . . . 3-8, 3-10
Tecnomatix . . . . . . . . . . . . . . . . . . . . . D-8 URLs, Teamcenter’s engineering process
Templates management . . . . . . . . . . . . . . . . . . 12-14
Installing . . . . . . . . . . . . . . . . . . . . . 9-1 User accounts . . . . . . . . . . . . . . . . 1-4, 2-22
Updating . . . . . . . . . . . . . . . . . . . . . . 9-2 UTF-8 character set . . . . . . . . . . . . . . . 1-4

Index
UTF-8 mode . . . . . . . . . . . . . . . . . . . . . 4-4 Legacy thin client URLs . . . . . . . . . 12-14

Utilities Multiple applications . . . . . . . . . . . 12-17
native2ascii . . . . . . . . . . . . . . . . . . . 14-6 Proxy WAR file (WebLogic) . . . 12-6, 12-13
Teamcenter Environment Shared application server
Manager . . . . . . . . . . . . . . . 16-2, 16-4 instance . . . . . . . . . . . . . . . . . . 12-17
web_gen_xml . . . . . . . . . . . . . . . . . . 14-3 Web Tier for .NET . . . . . . . . . . . . . . . D-11
Web tier installation problems . . . . . . . B-4
V Web tier requirements . . . . . . . . . . . . . . 1-1
Vendor Management . . . . . . . . . . . . . . D-4
preference . . . . . . . . . . . . . 2-19–2-20, B-2
Vendor Management for Rich Client . . D-10
WEB_default_site_deployed_app_name
Visualization
preference . . . . . . . . . . . . . . . . . . . . . B-3
Embedded viewer . . . . . . . . . . . . . . D-10
web_gen_xml utility . . . . . . . . . . . . . . 14-3
Stand-alone application viewer . . . . D-10
web_gen_xml.dat file . . . . . . . . . . . . . . 14-3
Teamcenter Visualization . . . . . . . . . D-5
WEB_help_server preference . . . 2-19–2-20,
Volume Server . . . . . . . . . . . . . . . . . . D-2
B-2
Volumes . . . . . . . . . . . . . . . . . . . . . . . 2-22
WEB_ROOT directory . . . . . . . . . . . . . 12-2
Web_tier directory . . . . . . . . . . . 12-3, 12-9,
W 12-12, 12-19–12-20, 12-28, 12-35
Web Application Manager . . . . . . 16-5–16-6 webapp_root directory . . 12-30–12-31, 12-34
Installation . . . . . . . . . . . . . . . . . . . 12-2 WebSphere . . . . . . . . . . . . . . . . . . . . 12-34
Launching . . . . . . . . . . . . . . . . . . . . 12-2 webstrings.xml file . . . . . . . . . . . . . . . 14-3
Patching . . . . . . . . . . . . . . . . . . . . . 16-4 Welcome window . . . . . . . . . . . . . . . . . . 8-6
Web servers Windows SAP DLL files . . . . . . . . . . . . 12-9
Deploying Web components . . . . . . . 12-31 Wire Harness Configuration . . . . . . . . . D-4
Deployment . . . . . . . . . . . . . . . . . . 12-18 Wiring Harness Design Tools
Supported servers . . . . . . . . . . . . . 12-31 Integration . . . . . . . . . . . . . . . . . . . . D-4
Web tier Workflow to Scheduling Integration . . . D-3
connection problems . . . . . . . . . . . . . B-3
Features . . . . . . . . . . . . . . . . . . . . D-10 Y
Generating application . . . . . . . . . . 12-3,
12-9, 12-12 Yellow Pages . . . . . . . . . . . . . . . . . . . . . 6-1
J2EE . . . . . . . . . . . . . . . . . . . . . . . 1-10

Server Unix

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Server Unix

Hochgeladen von

Copyright:

Verfügbare Formate

Teamcenter 8

Installation on UNIX and Linux

This software and related documentation are proprietary to Siemens Product

2 Installation on UNIX and Linux Servers Guide PLM00011 C

Part I: Getting started

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

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

Part II: Database server installation

Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Part III: Teamcenter server installation

Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

PLM00011 C Installation on UNIX and Linux Servers Guide 3

Back up new installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Part IV: Adding features

Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

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

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

Installing Teamcenter’s reporting and analytics . . . . . . . . . . . . . . . . . 11-1

Part V: Web tier installation

J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Part VI: Additional configuration and maintenance

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . 13-1

4 Installation on UNIX and Linux Servers Guide PLM00011 C

Localizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Configure rich client language display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Installing Teamcenter maintenance packs . . . . . . . . . . . . . . . . . . . . . . 17-1

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

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

Part VII: Appendixes

Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . B-1

Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

PLM00011 C Installation on UNIX and Linux Servers Guide 5

Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Required hard disk space for Teamcenter configurations . . . . . . . . . . . . 1-2

6 Installation on UNIX and Linux Servers Guide PLM00011 C

B-1. Installation problems and error messages . . . . . . . . . . . . . . . . . . . . . . B-2

PLM00011 C Installation on UNIX and Linux Servers Guide 7

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

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

PLM00011 C Installation on UNIX and Linux Servers Guide

Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-6

PLM00011 C Installation on UNIX and Linux Servers Guide

PLM00011 C Installation on UNIX and Linux Servers Guide 1-1

• Two-tier rich client

Required hard disk space for Teamcenter configurations

1-2 Installation on UNIX and Linux Servers Guide PLM00011 C

On Macintosh systems, the thin client is supported on Apple Safari browsers. No

Web tier support

J2EE application server

For supported versions of these products, see the certification database.