Server Unix

Teamcenter 8

Installation on UNIX and LinuxServers Guide

Publication NumberPLM00011 C

Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens ProductLifecycle 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-1Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-6

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

Installation and deployment overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Part II: Database server installation

Oracle installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Set shell limits and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Upgrade Oracle server and databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Configure an Oracle database for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Part III: Teamcenter server installation

Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

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

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

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

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Run the postinstallation tasks program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Modifying the services file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Start Teamcenter database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Configure 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-1Install the J2EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

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

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

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

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

Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Install the Manufacturing content kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1Populate the sample database for Manufacturing . . . . . . . . . . . . . . . . . . . . . 10-2Install the Manufacturing Tooling Library . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2Planning data migration from Genius4000 to Resource Manager . . . . . . . . . . 10-6Migrate Genius4000 data to Resource Manager . . . . . . . . . . . . . . . . . . . . . . . 10-8

Installing Teamcenter’s reporting and analytics . . . . . . . . . . . . . . . . . 11-1

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

Part V: Web tier installation

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

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

Part VI: Additional configuration and maintenance

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . 13-1

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


Contents

Localizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

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

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

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

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1Patching Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . 16-2Install patches on the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3Patch the distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6Patch the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8

Installing Teamcenter maintenance packs . . . . . . . . . . . . . . . . . . . . . . 17-1

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

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

Part VII: Appendixes

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . B-1Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . B-5Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . B-9Recovering from a corrupted Oracle-based database . . . . . . . . . . . . . . . . . . . B-10

Distribution media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Teamcenter software distribution image . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1Teamcenter documentation distribution image . . . . . . . . . . . . . . . . . . . . . . . C-2

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

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


Contents

Web tier context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

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

Figures

Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

1-1. Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91-2. Two-tier deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-101-3. Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111-4. Four-tier deployment (enterprise and Web tiers on same host) . . . . . . . . 1-131-5. Four-tier deployment (enterprise and Web tiers on separate hosts with HTTP

server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-141-6. Four-tier deployment (multiple enterprise tier hosts and Web tier

hosts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-151-7. Four-tier deployment (load balancing) . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2-1. Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92-2. Basic File Management System deployment . . . . . . . . . . . . . . . . . . . . 2-1213-1. Multiple databases (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . 13-515-1. Sample silent installation configuration file . . . . . . . . . . . . . . . . . . . . . 15-4

Tables

Required hard disk space for Teamcenter configurations . . . . . . . . . . . . 1-22-1. Basic Teamcenter network nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12-2. Additional Teamcenter network nodes . . . . . . . . . . . . . . . . . . . . . . . . 2-33-1. AIX minimum shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23-2. HP-UX minimum kernel parameter values for single database

instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33-3. Solaris 10 minimum resource control values for single database

instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63-4. SUSE Linux minimum shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75-1. Required File Management System information . . . . . . . . . . . . . . . . . 5-37-1. Required server manager information . . . . . . . . . . . . . . . . . . . . . . . . . 7-111-1. TEM panels for Reporting and Analytics installation . . . . . . . . . . . . . . 11-312-1. Additional Teamcenter Web applications . . . . . . . . . . . . . . . . . . . . . . . 12-512-2. Context parameters for shared deployment . . . . . . . . . . . . . . . . . . . . 12-1812-3. Rich client required parameter and table values . . . . . . . . . . . . . . . . 12-2212-4. Rich client optional parameter values . . . . . . . . . . . . . . . . . . . . . . . . 12-2512-5. Teamcenter’s lifecycle visualization (embedded viewer) parameter and table

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

parameter and table values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2712-7. Teamcenter Integration for NX parameter and table values . . . . . . . . 12-2712-8. Content Management System for Rich Client 4-Tier . . . . . . . . . . . . . . 12-2714-1. UNIX Environment Settings for Non-English Locales . . . . . . . . . . . . . 14-215-1. Silent installation XML elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2


Contents

B-1. Installation problems and error messages . . . . . . . . . . . . . . . . . . . . . . B-2B-2. Update Manager FTP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3D-1. Teamcenter solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1D-2. Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2E-1. Web tier required parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1E-2. Web tier optional parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5E-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-1Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1System hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Web tier support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Software integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Hewlett-Packard HP-UX considerations . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Linux considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-6Database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Teamcenter servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Additional servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Network Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Teamcenter network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Selecting and configuring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Basic tasks in Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Installing a database server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Installing a Teamcenter server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Installing the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Installing Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17


Chapter

1 Getting started

This guide describes how to install Teamcenter 8 on UNIX and Linux servers. Thisincludes installation of Teamcenter servers using Teamcenter Environment Managerand the Teamcenter Web tier using the Web Application Manager.

This guide assumes you have a thorough working knowledge of your operatingsystem and general knowledge of Teamcenter use.

PrerequisitesInstall prerequisite software and verify that your hardware is supported forTeamcenter 8.

For information about versions of operating systems, third-party software,Teamcenter software, and system hardware certified for your platform, see theSiemens PLM Software Certification Database:

http://support.ugs.com/online_library/certification/

To use the certification database, choose the platform and products you use, andthen click Show Certifications.

Note

Some software requirements differ for non-English locales. When viewing thecertification database, make sure you note any exceptions for your locale.

Platforms

Make sure your Teamcenter 8 server host runs one of the following supportedplatforms:

• 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 onMacintosh platforms. No Teamcenter servers or rich clients are supportedon Macintosh.

Teamcenter installation tools (Teamcenter Environment Manager and WebApplication Manager) require the ISO8859–1 character set. Make sure thischaracter set is available on your host. If you are uncertain or want to verifythis 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 diskspace for the following common Teamcenter configurations:

• Corporate server

The corporate server contains the features included in the Corporate Serversolution in Teamcenter Environment Manager (TEM). Additional features mayrequire 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–tiersolution in Teamcenter Environment Manager (TEM). Additional features mayrequire 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 adistribution server instance that contains the Over-the-Web installer and RichClient 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

PlatformCorporateserver

Two-tierrich 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 storingTeamcenter data. Before you install a Teamcenter, you must install an Oracledatabase server and make sure your Teamcenter corporate server host has accessto the server.

For information about supported database server versions, see the certificationdatabase.

For information about installing a database server for Teamcenter, see Oracleinstallation 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. Norich 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 Webapplications.

J2EE application server

Install a supported J2EE application server on the host where you deployTeamcenter 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 thoseproducts before you install Teamcenter 8. These include the following Teamcenterintegrations:

Teamcenter’s lifecycle visualizationNX IntegrationSCM ClearCase for Rich Client

Some Siemens PLM Software products require separate licenses from your SiemensPLM Software representative. Siemens PLM Software products are licensed usingthe Siemens PLM Software Common Licensing Server.







For more information about the Common Licensing Server, see Install the licensingserver.

Enabling Teamcenter installationAfter you install prerequisite software, locate the Teamcenter software anddocumentation distribution images and make sure they are accessible to your clienthost. For descriptions of Teamcenter distribution images, see Distribution media.

Note

If you mount the Teamcenter software distribution image on a remote NFSserver, you must launch Teamcenter Environment Manager on the localserver 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 toolson HP-UX systems. For more information, see the Hewlett-Packard guidelines atthe 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 characterset rather than the default UTF-8 character set. Teamcenter installation toolsrequire this setting.

Configuring Teamcenter installationBefore you install Teamcenter, create an operating system logon account forTeamcenter. Teamcenter services run on the server as this user account.

Log on using this account when you install the Teamcenter corporate server andwhen you perform maintenance such as upgrading or installing updates usingTeamcenter Environment Manager.

Starting Teamcenter installationTo begin installing Teamcenter installation, launch the appropriate Teamcenterinstallation tool:

• Teamcenter Environment Manager

To install the Teamcenter corporate server, launch Teamcenter EnvironmentManager using the tem.sh command from the Teamcenter software distributionimage.

• Web Application Manager


Getting started

To begin installing the Teamcenter J2EE Web tier, launch the Web ApplicationManager using the insweb command from the install directory in theWEB_ROOT directory.3

Interfaces: Teamcenter installation toolsTeamcenter installation tools (Teamcenter Environment Manager and the WebApplication Manager) enable you to build and manage your Teamcenter installation.

Teamcenter Environment Manager

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

Teamcenter Environment Manager

Teamcenter Environment Manager also performs maintenance operations, such asupgrading 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 clientsolutions 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.



Web Application Manager

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

Basic concepts about Teamcenter installationDetermine the Teamcenter servers and network architectures suit your needs andwhich 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 andconfigure a database server to store Teamcenter data. The Teamcenter corporateserver must have access to a database server or a database client. Teamcentersupports Oracle or Microsoft SQL Server databases.

For information about installing a database server for Teamcenter, see Oracleinstallation and configuration.

For Oracle configuration settings and tuning methods to optimize Teamcenterperformance, see the Teamcenter Deployment Guide, available in the documentationsection of Siemens PLM Software’s support site. The Teamcenter DeploymentGuide also provides an in-depth review of Oracle database performance issues anddiagnosis, 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.


http://support.ugs.com/docs/teamcenter/

Getting started

For Microsoft SQL Server configuration settings and tuning methods to optimizeTeamcenter performance, see the Teamcenter Deployment Guide, available in thedocumentation section of Siemens PLM Software’s support site. The TeamcenterDeployment Guide also provides an in-depth review of Microsoft SQL databaseperformance issues and diagnosis, and configuration and tuning guidelines.

Note

Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannotconnect to Microsoft SQL Server database servers.

Teamcenter servers

You can install different types of Teamcenter servers according to the features youuse 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. Additionalservers are optional, but can help balance network loads and facilitate heterogeneousnetworks (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 asTeamcenter’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 runboth Teamcenter and customer-written applications. Customers can also extend thestandard user interface.

The rich client application is deployed on each user workstation using TeamcenterEnvironment Manager or the Over-the-Web Installer, depending on whichTeamcenter network architecture you use. The rich client is supported in botharchitectural models described in Two-tier architecture and Four-tier architecture.

Thin client

The thin client provides access to Teamcenter through a standard commercial Webbrowser, such as Microsoft Internet Explorer or Mozilla Firefox. The user interface


http://support.ugs.com/docs/teamcenter/


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

The thin client is supported only in the four-tier architectural model described inFour-tier architecture.

Network Folders

Teamcenter’s Network Folders is an extension (plug-in) to Microsoft WindowsExplorer. Network Folders provides access to Teamcenter through WindowsExplorer. Users unfamiliar with the rich client and thin client interfaces can performdocument management of Teamcenter objects from Windows Explorer withoutlaunching Teamcenter.

Network Folders is supported only on Microsoft Windows platforms and only in thefour-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 onthe client workstation.

Note

The two-tier rich client is installed only through TEM. Over-the-Webinstallation 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 enablethese features for a two-tier rich client, you can connect the two-tier richclient to a deployment of the Web tier. For information about functionalityyou can add to a rich client and which add-ons require the Web tier, seeRich client installation.

• Resource tier

The resource tier comprises a database server, database, volumes, and fileservers.


Getting started

Rich Client

(Local TC Server)

VolumeResource Tier

Client Tier

Database

Rich Client

(Local TC Server)

Rich Client

(Local TC Server)

Figure 1-1. Two-tier architecture

In the two-tier model, you deploy the Teamcenter rich client, which includes thelocal server, and the optional applications that integrate with the rich client on theclient workstation. Typically, the database server, volumes, and file servers areinstalled 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 thevolume.

• 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, seeFile Management System installation.



Database

Teamcenter Server

Teamcenter Files (application root)

2-Tier Rich Client

Database Server

VolumeFCC FSC

TCFS

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 clientssuch as Teamcenter’s Client for Microsoft Office.

Note

The rich client can be deployed with additional functionality, such asLifecycle Visualization, Teamcenter’s Integration for Microsoft Office, andTeamcenter Integration for NX or NX Integration 4.0.1. (TeamcenterIntegration for NX/NX Integration 3 is not supported.)

For information about the functionality you can add, see Rich clientinstallation.

• J2EE Web tier

The J2EE Web tier is a Java application that runs in a Java 2 EnterpriseEdition (J2EE) application server, such as BEA WebLogic, and is responsible forcommunication between the client tier and enterprise tier. For information aboutsupported application servers, see the Siemens PLM Software CertificationDatabase:


• Enterprise tier


Getting started

The enterprise tier comprises a configurable pool of Teamcenter C++ serverprocesses and a server manager. The enterprise tier retrieves data from andstores data in the database.

A server manager manages a pool of Teamcenter server processes. You mustinstall a server manager whenever you deploy the Web tier.

Note

Teamcenter provides server managers based on the J2EE and theMicrosoft .NET platforms. The .NET Web tier is supported only onWindows platforms.

• Resource tier

The resource tier comprises a database server, database, volumes, and fileservers.

Resource Tier

Web Tier

Client Tier

Enterprise Tier

Teamcenter

ServersServer

Manager

Application Server

Teamcenter EAR

Volume Database

Rich Client Thin Client WebDAV Client

Figure 1-3. Four-tier architecture

You can design deployments that host the Web tier, resource tier, and enterprisetiers on the same computer or on separate computers:

• Smaller sites can run the pool of servers and the server manager on the samehost as the Web tier.



• Larger sites can distribute the pool of server processes across multiple hostsand optionally include an HTTP server to serve static files or multiple HTTPservers to support load balancing.

For a multihost configuration, the server pool consists of multiple subpools, oneor 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 employthe JBoss cache, a tree-structured cache, to provide replication and transactioncontext. You must configure the JBoss cache (called TreeCache in Teamcenter) inboth the J2EE based server manager and the Web tier application.

To ensure communication between the Web tier and the server manager, you mustcoordinate the values you specify for each component. For some values, you mustprovide the identical value when configuring the Web tier application.

If you are setting up multiple Web tier environments with separate domains, youmust 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 recommendsconfiguring 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 anddynamically 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. Replacejmx-port with the number of the port running the JMX HTTP adapter. This portnumber 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 nameand the password. You can change the user name and password to unique valuesusing 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 andeach 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 theserver manager must run on the same host server, with the same user ID.


Getting started

Database Server

Database

TC Server n

TC Server n+1

TC Server n+2

Server Manager

Starts server processes for multiple users.

Thin Client 4-Tier Rich Client

Third-Party Application Server

tc.ear

Volume

FSC

FCC

FSC TCFS

Figure 1-4. Four-tier deployment (enterprise and Web tiers on same host)



HTTP Server

Database

Database Server

TC Server n

TC Server n+1

TC Server n+2

Server Manager


Thin Client 4-Tier Rich Client


tc.ear

Figure 1-5. Four-tier deployment (enterprise and Web tiers on separate hosts withHTTP server)


Getting started

Database Server

Database

TC Server n

Server Manager

Thin Client

4-Tier Rich Client


tc.ear

HTTP Server


tc.ear

TC Server n

Server Manager

TC Server n

Server Manager

Figure 1-6. Four-tier deployment (multiple enterprise tier hosts and Web tier hosts)



Database Server

Database

TC Server n

Server Manager

Thin Client

4-Tier Rich Client


tc.ear

HTTP Server


tc.ear

TC Server n

Server Manager

TC Server n

Server Manager

HTTP Server

Load Balancing

Figure 1-7. Four-tier deployment (load balancing)


Getting started

Selecting and configuring features

The Select Features panel in Teamcenter Environment Manager provides manyfeatures you can include in your Teamcenter server. For a complete list of availablefeatures, see Teamcenter features. Some Teamcenter features require additionalconfiguration after Teamcenter installation is complete. For information aboutadditional 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 theTeamcenter guidelines provided in Oracle installation and configuration.

Installing a Teamcenter server

Install one or more Teamcenter servers as described in Teamcenter serverinstallation.

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-1Planning the Teamcenter network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Installing Teamcenter components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Thin client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11File Management System installation . . . . . . . . . . . . . . . . . . . . . . . . 2-11Installing File Management System . . . . . . . . . . . . . . . . . . . . . . 2-11Installing Teamcenter File Services . . . . . . . . . . . . . . . . . . . . . . . 2-15Creating volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Lifecycle Visualization installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Global Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Teamcenter Linking installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Security Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Teamcenter online help installation . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Configuring online help for thin clients . . . . . . . . . . . . . . . . . . . . 2-18Configure direct file access for rich clients . . . . . . . . . . . . . . . . . . 2-19Configure over-the-Web access for rich clients . . . . . . . . . . . . . . . . 2-19

Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Oracle server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Network environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Homogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Heterogeneous 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 yourinstallation.

Installation and deployment overviewDetermine the network architecture you want to use and the components you wantto install.

Planning the Teamcenter network

A Teamcenter network table 2-1 can include server and client hosts from more thanone 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 Teamcenternetwork. A host often performs more than one of these roles. A role can be performedby 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 installationof RDBMS software and services queries from severalTeamcenter servers.

For large-scale installations, the database server istypically a dedicated high-performance server systemthat is optimized specifically for running database serversoftware.


Chapter 2 Site planning


Network node Role

Corporate server Teamcenter service node at the center of a Teamcenternetwork. The corporate server contains installations of thefollowing Teamcenter components:

• The Teamcenter shared binary executables.

This installation directory is referred to as theTeamcenter application root directory. The TC_ROOTenvironment variable points to this location.

A Teamcenter application root directory can beNFS/CIFS-mounted to more than one application client.

• The Teamcenter shared data subdirectories and files.

This installation directory is referred to as theTeamcenter data directory. The TC_DATAenvironment variable defines this location. Each datadirectory is associated with a single database instance,but multiple data directories can point to a singledatabase instance.

The data directory is exported with full write accessand mounted via NFS/CIFS by other Teamcenter nodes.

• A minimum of one Teamcenter volume and FileManagement System (FMS) and Teamcenter FileServices (TCFS).

To install volumes on multiple hosts for the samedatabase, install a server that points to the databaseand install File Management System (FMS) andTeamcenter File Services (TCFS) on any systemservicing a volume.

• The server manager process required when theTeamcenter network includes the Web tier.1

The server manager starts and stops Teamcenterservers, informing a server assigner of its actions sothat the assigner can assign available servers to usersessions.

Multiple application clients can map to or mount thecorporate server.

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


Site planning


Network node Role

Web-tier applicationserver

Teamcenter service node that contains an installation of theTeamcenter Web tier application deployed in a third-partyapplication server.

Teamcenter clients Hosts containing an installation of the Teamcenterrich client executables and connected to a Teamcentercorporate server or application server. Hosts accessing theTeamcenter thin client over the Web.

Table 2-2. Additional Teamcenter network nodes

Network node Role

Multi-SiteCollaboration ODSserver

Network node that runs a daemon process to publish dataobjects within a Multi-Site Collaboration environment.Configuration of Multi-Site Collaboration is optional.

Publication of a data object makes the object visible toother databases. At least one Teamcenter database on thenetwork must be designated as an ODS database: thisdatabase stores publication records for the data objects.One ODS server node must be designated for each ODSdatabase, and each server node can only act for onedatabase.

Multi-SiteCollaboration ODSproxy server

Network node running daemon processes that performproxy services for ODS servers within a Multi-SiteCollaboration environment. Configuration of Multi-SiteCollaboration is optional.

Typically, the proxy server node is connected betweena firewall and the ODS server nodes. ODS requestsoriginating from external sites go through the firewalldirectly into the proxy server node, which relays the ODSrequests to the ODS servers. In this way, the proxy serverprotects the ODS servers from direct access from externalsites. It also simplifies firewall management because thefirewall manages only one TCP/IP port for all external ODSrequests.

Note

A node can act both as an ODS proxy server andIDSM proxy server at the same time.

Multi-SiteCollaboration IDSMserver

Network node running a daemon process that transfersdata objects among databases (sites) in a Multi-SiteCollaboration environment. You must designate one IDSMserver node for each Teamcenter database from whichobjects are published. Each server node can act only forone database.



Table 2-2. Additional Teamcenter network nodes

Network node Role

Multi-SiteCollaboration IDSMproxy server

Network node running daemon processes that performproxy services for IDSM servers.

Typically, the IDSM proxy server node is connected betweena firewall and the IDSM server nodes. IDSM requestsoriginating from external sites go through the firewalldirectly into the proxy server node, which relays the IDSMrequests to the IDSM servers. In this way, the proxy serverprotects the IDSM servers from direct access from externalsites. It also simplifies firewall management because thefirewall manages only one TCP/IP port for all externalIDSM requests.

Quick part locator(QPL) server

Component of Repeatable Digital Validation (RDV).The QPL server provides a qpl daemon used withDesignContext. This daemon coexists with all otherTeamcenter daemons. For QPL-based DesignContext,QPL server setup is required. For Appearance-basedDesignContext, QPL server setup is not required.

Installing Teamcenter components

Your installation process depends on the network architecture and Teamcenterfeatures you use.

Two-tier architecture installation

The primary components of a two-tier installation require three general installationtasks:

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

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


Site planning

Teamcenter Server

Exe - start_TcServer1

Teamcenter Files

Installed at TC_ROOT

2-Tier Rich Client

Exe - portal

Installed by TEM

Corporate server installation using Teamcenter Environment Manager.

Database

Database Server

2

1

4

3

Implementation Repository

Exe - start_imr

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, eitherOracle or MS SQL Server.

For the installation procedures, see part II, Database server installation.

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

Teamcenter Environment Manager installs the pool of Teamcenter servers andthe server manager, creates and or populates the database, and configures avolume.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 WebApplication 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 supportedonly 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 andconfigure 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 ClientsGuide or Installation on UNIX, Linux, and Macintosh Clients Guide.

Note

The automatic logon feature is not supported in four-tier Teamcenterdeployments. For more information about the automatic logon feature, see thePreferences and Environment Variables Reference.


Site planning

Database

Database Server

TC Server n

Exe - tcserver

TC Server n+1

Exe - tcserver

TC Server n+2

Exe - tcserver

Server Manager Exe - mgrstart Uses - tc_root

tc_data

Teamcenter Servers and Server Manager installed using Teamcenter Environment Manager (TEM)


Thin Client

Exe - http://host:port/tc/webclient

Uses - http://host:port/tc/webclient

4-Tier Rich Client

Exe - portal starts otwportal

Uses - http://host:port/tc/webclient

Installed as part of the Web tier.

Installed on Client Host Over the Web


tc.ear

EAR File Generated Using Web Application Manager (insweb) Deployed in Third-Party Application Server Software Port number used by clients

1

2

3

4

5

6

Four-tier architecture installation



Rich client installation

The Teamcenter rich client is a Java application that runs on client hosts. Thetwo-tier rich client is installed on each client host using a stand-alone instance ofTeamcenter Environment Manager. The four-tier rich client is installed using adistributed instance of the Over-the-Web Installer.

To install the two-tier rich client, you launch Teamcenter Environment Manager onyour client host, select the client components you want to install, and then proceedwith installation.

To install the four-tier rich client, you use a Web browser open the URL of aWeb application server that serves the Over-the-Web Installer. The four-tier richclient installs silently, with no prompts. Teamcenter administrators configureall installation options and provide all the information necessary to completeinstallation using Web Application Manager.

To enable over-the-Web installation for the four-tier rich client, you install thefollowing components on a server host (figure 2-1):

• A rich client distribution server.

The distribution server software manages the connection between a rich clientdistribution instance and the Over-the-Web Installer. The Over-the-WebInstaller contacts the distribution server for the rich client files to download tothe user’s workstation.

Only one rich client distribution server is required to manage multiple richclient distribution instances.

• A rich client distribution instance or instances.

A rich client distribution instance contains the Over-the-Web Installer and therich 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 applicationserver.

After you install and deploy a rich client distribution server and distributioninstances, you can change the distribution server contents, add components toa distribution instance, and patch components in a distribution instance usingWeb Application Manager. The next time users start a rich client installed fromthat distribution instance, the rich client startup process checks for updates anddownloads them to the client hosts.


Site planning

otw_installer.jar

Created by Web application manager using 'Distribution Server'

installing.html

Uses - instance = "web application name" server_name = "hostname:rmi port" Example - instance = "Teamcenter 2 Tier OTW server_name = "hostname:12001"

Created by Web application manager using 'Distribution Server' instance

Open Web page

Check that client installed is current and install or update.

RMI

Exe - start_rmi

Distribution Server

Exe - start_server Uses - webapps.dat

otw.html

Figure 2-1. Rich client installation

When configuring a rich client distribution instance (for a four-tier rich client) or alocal rich client instance (for a two-tier rich client), you can add the functionality tothe 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 withTeamcenter. Users must separately install NX executable files on the clienthosts. All client hosts installing from a particular distribution instance musthave NX installed in the same location.

Note

Configuring Teamcenter Integration for NX requires additional manualsteps to be performed by the user as prompted by the Over-the-WebInstaller.

• Teamcenter’s lifecycle visualization (embedded viewer)

When you choose this option, Teamcenter’s lifecycle visualization executable filesare 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’slifecycle visualization. Users must independently install Teamcenter’s lifecyclevisualization executable files on the client hosts. All client hosts installing adistribution instance must have Teamcenter’s lifecycle visualization installedin the same location.

Note

The Teamcenter’s lifecycle visualization integration requires thepresentation tier application, a component of the four-tier architecture. Toenable Teamcenter’s lifecycle visualization for a two-tier rich client, youcan connect the two-tier rich client either to a deployment of the Web tieror 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 Overlayexecutable files are included in the distribution instance.

• Teamcenter’s Integration for Microsoft Office

When you choose this option, the Teamcenter’s Integration for Microsoft Officeexecutable files are included in the distribution instance.

• Teamcenter Linking

When you choose this option, the rich client is enabled to support the linkingof objects between Teamcenter, Teamcenter’s portfolio, program and projectmanagement, and Teamcenter’s systems engineering and requirementsmanagement. Separate installation of Teamcenter Linking components andTeamcenter Application Registry are required.

Note

Teamcenter Linking requires the presentation tier application, acomponent of the four-tier architecture. To enable Teamcenter’sIntegration for Microsoft Office for a two-tier rich client, you can connectthe two-tier rich client either to a deployment of the Web tier or to adeployment of the presentation tier application.

• Teamcenter EDA.

When you choose this option, the rich client is configured for use with TeamcenterEDA. The Teamcenter EDA stand-alone client must also be installed.

• SCM ClearCase

When you choose this option, the executable files are included in the distributioninstance for the integration between Teamcenter and the IBM RationalClearCase software configuration management (SCM) tool.

For a complete list of available Teamcenter features for the rich client, see Solutionsand features reference.

For information about creating, deploying, and updating the rich client distributionserver and rich client distribution instances, see Installing rich client Web


Site planning

applications. Instructions for installing the rich client over the Web on a clienthost are in the Installation on UNIX, Linux, and Macintosh Clients Guide and theInstallation on Windows Clients Guide.

Thin client installation

The Teamcenter thin client is a Web browser-based application. You install the thinclient as part of the Web tier application. To install the Web tier, you use the WebApplication Manager to create and install an enterprise archive (EAR) file that youthen 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 browsersuch as Microsoft Internet Explorer, Netscape, and Mozilla. No aspect of the thinclient is installed on a user workstation other than the required third-party Webbrowser.

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, andthe thin client configured with Teamcenter’s lifecycle visualization. Multi-SiteCollaboration also uses FMS servers to transfer data.

• Teamcenter File Services (TCFS)

The Teamcenter Organization application uses TCFS to create volumes andperform other administrative functions. TCFS also supports file access for NX4.0.0 or earlier and Teamcenter’s lifecycle visualization 5.0 or earlier whenyou use these products with Teamcenter. (NX 4.0.1 and Teamcenter’s lifecyclevisualization 6.0 and later use File Management System.)

Note

If you install File Management System, the FMS server cache (FSC) and theserver manager must run on the same host server, with the same user ID.

You install both FMS and TCFS on Teamcenter server hosts using TeamcenterEnvironment Manager. Both FMS and TCFS must run as the same operatingsystem user for the purpose of accessing volume data. This does not require themto run on the same host or operating system, but they must run as the same userfor file permissions access to the volume. If the FMS server cache is not managingany volumes, that is, if it is purely a cache server, it can run as any user that isconvenient.

Installing File Management System

FMS provides the following functions:

• Volume server for file management

• Shared server-level performance cache for shared data access between multipleusers

• Client-based private user cache for rich clients



• Transient data store mechanism for transporting reports, PLM XML, and othernonvolume 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 centralfile 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 Teamcenterserver hosts.

• The FCC component provides a client process and file caches for rich clientson user workstations.

FCC

SYSTEMS

Vol 1

Vol 2

Vol 3FCC

FCC

LAN

TC Server FSC Server

Rich Client

Rich Client

Visualization Client

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 ofthe following functions:

• Volume server or performance cache server

When running on a host where a volume is located or directly mounted on thecomputer hosting the FSC, the FSC acts as a volume server.

When running on a host where a volume is not located or directly mounted, theFSC acts as a performance cache server.

As a volume or cache server, the FSC checks all file access requests for a ticketthat Teamcenter generates to authorize file access. As a cache server, it managestwo segment caches, one for downloading files and one for uploading files.

• Configuration server

As a configuration server, the FSC provides FMS configuration information tothe 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 filesto clients.


Site planning

Any deployment of Teamcenter requires a minimum of one FSC server. You candeploy multiple FSC servers, each performing a multiple roles or each performinga designated purpose as either a volume, a cache, or a configuration server. Whenyou install multiple volumes on different hosts for the same database, the multipleFSC servers are linked through a common master FSC. (You can manually configuremore 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 hierarchicalstructure:

• FMS master configuration file (fmsmaster_fsc_id.xml)

The master configuration file describes the File Management System networkand defines FSC groups. It is the highest file in the hierarchy and can definedefault 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. OtherFSC servers in the network download FMS configuration information from themaster 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 specifiesthe address of the master FSC (for downloading FMS network information) anddefines such values as the maximum sizes of the server segment file cachesand the upload timeout value.

This file can either inherit values from the master file or override them. It canalso define default values for FCCs.

• The FCC configuration file defines values for the FCC on client hosts, such as themaximum sizes of the caches.

It can either inherit values from the FSC configuration file or override them.

The Teamcenter installation program, Teamcenter Environment Manager, installsand initially configures the FSC servers, segment file caches, master configurationfile, and FSC configuration file or files. For small deployments of Teamcenter, thismay be the only installation and configuration required. For large deployments, youcan 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 followingfunctions:

• 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 richclient or thin client:

• The rich client requires an FCC, and the Over-the-Web Installer automaticallyinstalls an FCC with each rich client.

The rich client uploads files to the Teamcenter volume and downloads files fromthe Teamcenter volume using the FCC. If Teamcenter’s lifecycle visualization6.0 or later is installed on the workstation and used with the rich client, itoptionally 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 sizeof files downloaded from the volume or uploaded to the volume. Installing therich client instance on a workstation simultaneously installs the FCC processand 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 waymay be the only configuration you require, but you can take advantage ofadditional configuration options by manually configuring the FCC. For manualconfiguration information, see the Preferences and Environment VariablesReference.

• The thin client does not use the FCC. Workstations that access the thin clientdo not require its installation.

However, if you install the FCC, Teamcenter’s lifecycle visualization 6.0 and NX4.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 applicationsdirect access to files over a high-performance network connection.

– File streaming

Teamcenter’s lifecycle visualization 6.0 uses proprietary file streamingtechnology to download appropriate portions of the JT files over the networkas they are needed. FMS supports segment file transfer to keep networkloads 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 beshared by groups of users.

– Deployment flexibility


Site planning

FMS components support a multitude of deployment configurations. Thisenables administrators to geographically locate volumes and shared FSCservers close to client workstations, providing the ability to tune the systemfor optimal file transfer performance.

For information on installing an FCC for use with the thin client andTeamcenter’s lifecycle visualization, see the Installation on UNIX, Linux, andMacintosh Clients Guide or Installation on Windows Clients Guide.

Installing Teamcenter File Services

The Teamcenter Organization application uses Teamcenter File Services (TCFS) tocreate volumes and perform other administrative functions. TCFS also supports fileaccess for NX 4.0 or earlier and Teamcenter’s lifecycle visualization 5.0 or earlierwhen you use these products with Teamcenter.

You control the security modes for file access by setting the TC_Security_Levelpreference. For more information about this preference and about TCFSconfiguration, see the Teamcenter Preferences and Environment Variables Reference.

Creating volumes

Using Teamcenter Environment Manager installation program, you create twotypes of Teamcenter volumes:

• Standard volumes

Standard volumes are UNIX directories Teamcenter uses to store files managedby Teamcenter. Users cannot directly access the files in these volumes; they mustdo so via a Teamcenter session. One standard Teamcenter volume is requiredper database. You can optionally create multiple volumes for a database.

You create a standard volume when installing Teamcenter and populating aTeamcenter database. Volumes require the installation of Teamcenter FileServices (TCFS) and File Management System (FMS):

– When creating a volume, you must install and configure TCFS. TCFS runsa daemon process that allows access to Teamcenter volumes through theTeamcenter Organization application. There can be multiple TCFS servernodes within the network, and each node can control volume access for morethan 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 temporarydata for transport of reports, PLM XML, and other data between the Web tierand client tier in a deployment of the four-tier architecture. One transientvolume is required per Teamcenter server host.

You can create a transient volume directory on a server host when installingTeamcenter and populating a Teamcenter database (the installation programadds the definition to the fmsmaster_fsc_id.xml configuration file). Forexamples of manually configuring transient volumes that cannot be accomplishedusing the installation program, see the Preferences and Environment VariablesReference.



Note

Teamcenter uses transient volumes only in a deployment of the four-tierarchitecture. For a deployment of the two-tier architecture, Teamcenterstores this data into a temporary directory on the rich client host, ratherthan in a defined transient volume. The temporary directory is definedeither by the start_server script or by the Transient_Volume_RootDiron the client host.

Teamcenter administrators can also create volumes using the rich clientOrganization application. For information about creating volumes after installationof Teamcenter, see the Organization Guide.

Lifecycle Visualization installation

For enterprise-wide product visualization capability, you can configure two SiemensPLM Software products with Teamcenter:

• Lifecycle Visualization embedded viewer (rich client only)

The Lifecycle Visualization embedded viewer is embedded in the rich client userinterface. The embedded viewer provides full 2D visualization capabilities and3D viewing and is available to all Teamcenter users.

The embedded viewer is installed on user workstations over the Web as part ofa rich client distribution instance. The license level is configured as part ofthe rich client distribution image. All users installing a rich client distributionimage that includes Lifecycle Visualization must have administration privilegeson the workstation.

• Lifecycle Visualization stand-alone application viewer (rich client and thin client)

The Lifecycle Visualization stand-alone application viewer is launched fromeither 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 theembedded viewer and Teamcenter’s lifecycle visualization mockup.

The stand-alone application viewer is individually installed on each clientworkstation using the Teamcenter’s lifecycle visualization distribution images.The rich client distribution instance can be configured with the informationrequired to enable the rich client to integrate with Lifecycle Visualizationapplications already installed on client workstations.

Lifecycle Visualization uses File Management System:

– When configured with the rich client, Lifecycle Visualization usesTeamcenter volumes and FMS, including the FSC and the FCC installedwith the rich client on client workstations.

– When installed as a stand-alone application, Lifecycle Visualization can useTeamcenter volumes and FMS if users install the stand-alone FCC on theworkstation. Installing a stand-alone FCC is described in the Installation onUNIX, Linux, and Macintosh Clients Guide and the Installation on WindowsClients Guide.


Site planning

– When configured with the thin client, Lifecycle Visualization usesTeamcenter volumes and the FSC. Optionally, users can install an FCC ontheir workstations for use with their Lifecycle Visualization installation.

Earlier supported versions of Lifecycle Visualization use TCFS only to managefile access and volumes.

Note

You can configure both Lifecycle Visualization products for use with a richclient. If you configure both products, you must install the embedded viewer ina separate directory from the stand-alone application viewer. The embeddedviewer and the stand-alone application viewer require separate license files.

Global Services installation

Global Services provides the additional components that enable a Teamcenter site toexchange 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 BOMdata from Teamcenter’s enterprise knowledge management.

To enable users to exchange data between Teamcenter and Teamcenter’s enterpriseknowledge management, you must install and configure Global Services, theTeamcenter and Teamcenter’s enterprise knowledge management connectors.

Global Services is available in the additional_applications/tcgs directory on theTeamcenter software distribution image. For installation information, see InstallGlobal Services.

Teamcenter Linking installation

Teamcenter Linking enables users to create links between Teamcenter objects andobjects in Teamcenter’s systems engineering and requirements management andTeamcenter’s portfolio, program and project management. Users can launch thelinked Teamcenter product from within the Teamcenter rich client.

Security Services installation

Security Services eliminates the need for multiple authentication challenges as usersmove from one Teamcenter application to another. Authentication is performed byan 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 configuringTeamcenter:

• Application ID for this instance of Teamcenter in the Security Servicesapplication 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/Customizationmanual provided in PDF format on the Teamcenter documentation distributionimage.

2. If you are deploying the two-tier architecture:

a. Install Security Services on the Teamcenter corporate server, specifying theTeamcenter application ID and the URLs of the Security Services LoginService Web and Identity Service Web applications as determined in step21-1.

For information, see Teamcenter server installation.

b. Create a two-tier Teamcenter rich client distribution instance, configuringSecurity Services for the client by specifying the same Teamcenterapplication ID, Security Services Login Service URL, and Identity ServiceWeb URL as specified when configuring Security Services on the corporateserver.

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, specifyingthe Teamcenter application ID and the URLs of the Security Services LoginService and Identity Service Web applications as determined in step 21-1.

When you configure the Web tier application to enable Security Services, theTeamcenter 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 richclient distribution instance, configuring Security Services for the client byspecifying the same Teamcenter application ID, Security Services logonService URL, and Identity Service Web URL as specified when configuringSecurity 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 filesystem (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 installthe help files on a server host either as part of generating the Web tier application orseparately 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 notchoose 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_serverWEB_core_help_server

When you install the help files as part of the Web tier application, the help URLsare 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 clientsaccess the help directly from files installed in the file system of a server host. Youcannot 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 thefollowing values for the online help context parameters:

Context parameter Value

RichClientHelpWebServer Specify file://.

RichClientHelpLocation Specify the full path to the help files for bothWindows 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-tierand two-tier rich clients to access online help served over-the-Web by the Web tierapplication. When you do not deploy the four-tier architecture, you can deploy thepresentation 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 fromthe 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 ApplicationManager and choose the option to install the online help files.

2. Create a two-tier or four-tier rich client distribution instance, supplying thefollowing values for the online help context parameters:




RichClientHelpWebServer Specify http://host-name:port, replacinghost-name and port with the name of the host andthe port where the Web tier or presentation tierapplication files are deployed in an applicationserver.

RichClientHelpLocation Specify the full path to the installed help filesindex.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 ApplicationManager, 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_serverWEB_core_help_server

When you install the help files as part of the Web tier or presentation tierapplication, the help URLs are automatically configured correctly using arelative path to the help files.

4. Create a two-tier or four-tier rich client distribution instance, supplying thefollowing values for the online help context parameters:


RichClientHelpWebServer Specify http://host-name:port, replacinghost-name and port with the name of the host andthe port where the Web tier or presentation tierapplication files are deployed in an applicationserver

RichClientHelpLocation Specify the full path to the installed help filesindex.htm file.


Other considerationsCertain issues regarding distribution of database and license servers can affectplanning of your Teamcenter network.


Site planning

Oracle server considerations

Determine whether to create a new Oracle database and/or upgrade existing Oracledatabases. You must install Oracle Server if a certified version is not installed on thesystem. For certified versions of Oracle, see the Siemens PLM Software CertificationDatabase:


You must also:

• Identify the systems to be Oracle database servers. Usually, such systemsare dedicated high-capacity servers, specifically tuned for Oracle. An Oracledatabase server must be directly accessible on the network by each workstationrunning Teamcenter.

• Install Oracle on each database server or NFS-mount Oracle to each databaseserver.

• 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 databaseinstance is required (for example, to support testing, training, or RDV). If you areinstalling RDV services, Siemens PLM Software recommends strongly that youcreate a new database instance on an Oracle server with database partitions on aseparate disk drive. RDV requires extensive data warehousing with large uploadsand simple queries. Such a configuration also makes the fine-tuning of the databaseeasier.

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 aheterogeneous 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 byone vendor (for example, Sun Microsystems).

When deploying the two-tier architecture, you can install Teamcenter applicationexecutable files on a single application server host, export the Teamcenterapplication root directory structure from the Teamcenter application server, andmount it using NFS on client workstations to run Teamcenter locally. Typically, theTeamcenter application server is also the Teamcenter data server. Similarly, you canexport the data directory structure and mount it using NFS to other Teamcenterclients 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 vendorsand can be a mixture of UNIX and Microsoft Windows nodes.

Installation considerations for a heterogeneous environment are the same as fora homogeneous environment, except that you must install Teamcenter for eachtype of workstation on the network, resulting in a Teamcenter application directorystructure for each different type of workstation. You can configure one Teamcenterapplication server to serve many Teamcenter directory structures for differentplatforms.

Teamcenter volume data must be accessible by all Teamcenter clients in aheterogeneous network. For clients that do not use File Management System, youcan usually share volume data using NFS and CIFS. When all clients use FileManagement System, do not share the volume. Instead, configure File ManagementSystem for volume access for all clients. For more information, see File ManagementSystem installation.

Note

• The Teamcenter root directory is platform-specific. The files within itcan be shared only between systems of the same platform type. Forheterogeneous Teamcenter environments that include Windows clients orWindows volume servers, configure File Management System to allow allclients to communicate with all volume servers.

The Teamcenter root directory is specific to Windows or UNIX systems(endien-specific). Maintain separate Teamcenter data directories onWindows and UNIX systems.

• Teamcenter servers and two-tier rich clients on UNIX or Linux hostscannot connect to Microsoft SQL Server database servers. Keep this inmind 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: itis a responsibility logon. log on with this account name to install or upgradeTeamcenter or install patches.

• Teamcenter administrative user account

Teamcenter requires an administrative user account named infodba.Teamcenter Environment Manager automatically creates this account when youinstall Teamcenter on a server host. This account is used by the Teamcenteradministrator to access the Teamcenter system administration functions toperform setup and maintenance tasks, such as creating Teamcenter users andlogons.


Site planning

When you are populating a database during installation, you must use apassword of infodba for this account. After installation, change the infodbapassword immediately.

Caution

Never use the infodba user to create working data or initiate workflowprocesses. This user ID has special behavior in the system: using it tocreate data or initiate workflow processes can cause unpredictable andundesirable behaviors.

If you require a user with high-level privileges to create data, create anew user ID and add that user to the DBA group and other groups asappropriate.

The infodba user is to be used only for the specific tasks and activitiesdescribed in the technical documentation for administrators.

In addition, Teamcenter requires a database user to be the owner ofTeamcenter-created tables and to perform tasks required by Teamcenter. You createthis database user either using the templates provided for Oracle databases or usingTeamcenter 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 Oracleaccounts to give them the same access privileges on all systems.

Each user and group is identified by an alphanumeric name and an IDnumber. The ID number is retained with the file information when a fileis exported across a network. If the ID numbers do not match for a user orgroup, 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 andconfiguration

Set shell limits and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Set AIX shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Set AIX system parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Set AIX kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Set HP-UX kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Set Solaris kernel parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Set SUSE Linux shell limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

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

Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Configure Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Configure Oracle Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Configure an Oracle database for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 3-15Choose how to create the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Create a database using Teamcenter Environment Manager . . . . . . . . . . . 3-16Create a database instance using Teamcenter templates . . . . . . . . . . . . . 3-17


Chapter

3 Oracle installation andconfiguration

Your Oracle database server must be a version certified for Teamcenter 8. Forinformation about the Oracle versions that Siemens PLM Software certifies foruse with Teamcenter 8, Oracle disk space requirements, and operating system andservice patch requirements, see the Siemens PLM Software Certification Database:


Perform the following tasks to prepare an Oracle database server and configure anOracle database for Teamcenter:

1. Choose a name for the Teamcenter user account. Teamcenter uses this accountas the owner of all Teamcenter-created tables. This account is used by thedatabase administrator to perform tasks required by Teamcenter.

Tip

If you use the Siemens PLM Software-supplied templates to create theTeamcenter 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 ofOracle.

For more information, see Install Oracle server.

• If you have an Oracle server installed, but it is not a version certified forTeamcenter 8, upgrade your Oracle server. For more information, seeUpgrade 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 anOracle database for Teamcenter.


Chapter 3 Oracle installation and configuration

Set shell limits and parametersOracle 10g extensively uses UNIX resources such as shared memory, swap memory,and semaphore for interprocess communication. Insufficient parameter settingscause problems during installation and instance startup. The greater the amount ofdata stored in memory, the faster a database operates. In addition, by maintainingdata in memory, the UNIX kernel reduces disk I/O activity.

On all UNIX and Linux platforms supported for Teamcenter 8, set the processmemory size (the ulimit user environment parameter) to unlimited beforeinstalling Oracle.

To avoid errors during installation, or operation errors after installation, reviewkernel parameter settings to ensure that they meet the recommended Oracle 10gsettings described in the following sections. The recommended kernel parametersettings are for a typical Oracle 10g environment. If you previously tuned kernelparameters 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 toavailable system memory. The Oracle installation program issues warnings if kernelparameters do not meet minimum requirements.

Note

The recommended values are minimum values. For production databasesystems, Oracle recommends that you tune the values to optimize systemperformance. 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, forexample, oracle.

3. Scroll down the list and ensure that the values shown in table 3-1 are set tothe minimum values.

Caution

Do not change the shell limit values if they were set for another programand 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

1. Type the following command:

# smit chgsys

2. Ensure that the value shown forMaximum number of PROCESSES allowedper user is greater than or equal to 2048.

Note

For production systems, this value should be at least 128 plus the sumof the PROCESSES and PARALLEL_MAX_SERVERS initializationparameters 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 exceedthe recommended Oracle 10g settings.

Set HP-UX kernel parameters

Set kernel parameters as described in table 3-2. Set parameters using the methoddescribed in your HP-UX documentation.

Caution

Do not change the kernel parameter settings if the parameters were setfor another program and the values are greater than the levels Oracle 10grequires.

Note

You can view kernel parameters using the kctune command.

Table 3-2. HP-UX minimum kernel parameter values for single databaseinstance

Kernel parameterMinimum valueor formula Purpose

executable_stack 0 Defines whether program stacks areexecutable by default.





ksi_alloc_max 33600 Defines the system-wide limit of queuedsignals that can be allocated.

max_thread_proc 3000 Defines the maximum number of kernelthreads allowed per process. You mayneed to increase the value if required byyour application. Setting it to a defaultor low value may lead to an out ofmemory error for certain applications.

maxdsiz 206385136 Defines the maximum data segmentsize in bytes for 32-bit systems. Settingthis value too low may cause theprocesses to run out of memory.

maxdsiz_64bit 4294967296 Defines the maximum data segmentsize in bytes for 64-bit systems. Settingthis value too low may cause theprocesses to run out of memory.

maxssiz 134217728 Defines the maximum stack segmentsize in bytes for 32-bit systems.

maxssiz_64bit 1073741824 (1 GB) Defines the maximum stack segmentsize in bytes for 64-bit systems.

maxswapchunks 16384 Defines the maximum number of swapchunks where SWCHUNK is the swapchunk size (1 KB blocks). SWCHUNKis 2048 by default. It specifies themaximum amount of configurable swapspace on the system.

Note

This parameter does not exist inHP-UX 11.23 or later.

maxuprc ((nproc*9)/10) Defines the maximum number of userprocesses.

msgmap (msgtql + 2) Defines the maximum number ofmessage map entries.

msgmni (nproc) Defines the number of message queueidentifiers.

msgseg 32767 Defines the number of segmentsavailable for messages.

msgtql (nproc) Defines the number of message headers.

ncsize (ninode + 1024) Defines the directory name lookupcache (DNLC) space needed for inodes.





nfile 65536 Defines the maximum number of openfiles. This parameter is managedautomatically by the system.

nflocks 4096 Defines the maximum number of filelocks available on the system. Thisparameter is managed automaticallyby the system.

ninode (8 * nproc + 2048) Defines the maximum number of openinodes.

nkthread (((nproc * 7) / 4) +16)

Defines the maximum number of kernelthreads supported by the system.

nproc 4200 Defines the maximum number ofprocesses.

semmap (semmni + 2) Defines the maximum number ofsemaphore map entries.

Note

This parameter does not exist inHP-UX 11.23 or later.

semmni 4200 Defines the maximum number ofsemaphore sets in the entire system.

semmns (semmni * 2) Defines the maximum number ofsemaphores in the system. The defaultvalue of semmns is 128, which is, inmost cases, too low for Oracle software.

semmnu (nproc – 4) Defines the number of semaphore undostructures.

semvmx 32767 Defines the maximum value of asemaphore.

shmmax Physical memorysize

Defines the maximum allowable size ofone shared memory segment.

To avoid performance degradation, theshmmax setting must be greater thanor equal to the size of the SGA.

shmmni 512 Defines the maximum number ofshared memory segments in the entiresystem.

shmseg 512 Defines the maximum number ofshared memory segments one processcan attach.





vps_ceiling 64 Defines the maximum system-selectedpage size in kilobytes.

Set Solaris kernel parameters

On Solaris 10, set kernel parameters using the Solaris resource control facility. Setresource controls as described in table 3-3.

On Solaris 9 or earlier, set kernel parameters to meet or exceed the recommendedOracle 10g settings. Use the procedure provided in your Solaris documentation toset kernel parameters.

Table 3-3. Solaris 10 minimum resource control values for single databaseinstance

Resource control Description

process.max-sem-ids Oracle recommends setting this resource control to100, 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 theOracle server. Oracle recommends a value of 4 GB,but for Teamcenter servers, set this resource controlto a value greater than the total SGA + PGA memorysize of all instances on the system.

project.max-shm-ids Oracle recommends setting this resource control to100, 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 projectuser.root recommended by Oracle documentation. To work with Solaris resourcecontrol, 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.oracleproject: 100: user.oracleNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-sem-ids

privileged 128 - deny -system 16.8M max deny -

sun2:(root)# prctl -n project.max-shm-memory -i project user.oracleproject: 100: user.oracleNAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.max-shm-memory

privileged 3.92GB - deny -system 16.0EB max deny -

sun2:(root)# prctl -n project.max-sem-ids -i project user.oracleproject: 100: user.oracle



NAME PRIVILEGE VALUE FLAG ACTION RECIPIENTproject.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-4by adding the following lines to the etc/security/limits.conf file:

oracle soft nproc 2047oracle hard nproc 16384oracle soft nofile 1024oracle hard nofile 65536

Caution

Do not change the shell limit values if they were set for another programand 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 theetc/profile.local file:

if [ $USER = "oracle" ]; thenif [ $SHELL = "/bin/ksh" ]; then

ulimit -p 16384ulimit -n 65536

elseulimit -u 16384 -n 65536

fifi

• For the C shell (csh or tcsh), add the following lines to the etc/csh.logon.localfile:

if ( $USER == "oracle" ) thenlimit maxproc 16384limit descriptors 65536

endif

Table 3-4. SUSE Linux minimum shell limits

Shell limitItem inlimits.conf

Minimum hardlimit

Maximum number of open file descriptors nofile 65536

Maximum number of processes available toa single user

nproc 16384



Upgrade Oracle server and databasesBack up your Oracle database, install a certified Oracle version, and upgrade yourdatabases.

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:

export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib

4. Export the contents of the Teamcenter Oracle database to the dump file:

ORACLE_HOME/bin/exp db-user/password full=yfile=file-name.dmp log=export.log

Replace db-user with the Teamcenter database user account name; replacepassword with the database user account password; replace file-name with thename of the dump file to contain the exported data; replace export with the nameof 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 ontape or another disk. If the dump file becomes corrupted or lost, all data fromthe existing database is lost.

Terminate Oracle sessions

Before installing Oracle, you must terminate all Oracle sessions and Oracleprocesses.

1. Either log on to the Oracle server as oracle or switch the user to oracle asfollows:

su - oracle



2. Set the ORACLE_HOME environment variable to point to the location of theOracle 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

Hewlett-Packard HP-UX:

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

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) orthe /etc directory (all other platforms).

• The Oracle Net listener.ora and tnsnames.ora configuration filesin eitherthe /var/opt/oracle directory (Sun Solaris system) or the /etc directory (allother platforms).



Note

These are the only Teamcenter directories affected by Oracle installation.If you created other directories containing data used by Oracle, such as anadministration script directory, Siemens PLM Software recommends thatyou 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 therequired 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 thenew Oracle database.

Install Oracle serverYou can install Oracle from the Oracle software distribution images supplied bySiemens PLM Software or Oracle Corporation.

If you install Oracle from a hard disk, copy the entire contents of the Oracle CD-ROMdirectory to the hard disk.

You can install Oracle application files on NFS file systems. However, OracleCorporation 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, youmust 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-suppliedversion of Java Runtime Environment (JRE). This version is requiredto run Oracle Universal Installer and several Oracle assistants. Do notmodify the JRE except by using a patch provided by Oracle SupportServices.

1. Log on to the server host as the oracle user.

2. Record the name of the Oracle database server host. Teamcenter EnvironmentManager requires this name during corporate server installation.

3. If Oracle was previously installed on the host, search for the following OracleNet configuration files in the etc and var/opt/oracle directories and eitherremove them or relocate them to the corresponding network/admin directoryin the Oracle home directory:

listener.oratnsnames.orasqlnet.ora

This step is required for compliance with the standard of storing Oracle Netconfiguration 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.

Hewlett-Packard HP-UX:/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-ROMautomatically. Replace device-name with the name of the CD-ROM device,for example, dev/dsk/c0t6d0s2; replace /cdrom with the CD-ROM mountpoint directory.

SUSE Linux:

mount -t iso9660 device–name mount-directory



Note

Use the preceding command if SUSE Linux does not mount the CD-ROMautomatically. Replace device-name with the name of the CD-ROM device,for example, dev/cdrom; replace mount-directory with the CD-ROMmount-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 diskand run rootpre.sh from disk. Enter the following commands:

cp –r /CDROM/rootpre /tmpcd /tmp/rootprechmod 755 *./rootpre.sh

Replace CDROM with your CD-ROM mount point.

The rootpre.sh script configures the AIX Asynchronous I/O and OraclePost-Wait Kernel Extension.

Note

• If you do not perform this step, Oracle or Teamcenter programs canfail with unresolved symbols.

• For more information about this issue, see SFB-TC_Engineering-1111available 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 TEMPand 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, forexample, disk/tmp

7. Start Oracle Universal Installer from the CD-ROM mount-point directory asthe 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 examplesets 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 andCredentials window, enter the directory where you want to install inventory files



and the operating system group name for the group that owns the inventorydirectory; 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, runit 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 clickNext.

12. In the Specify Home Details dialog box, enter the directory path in which toinstall the Oracle products in the Destination box and click Next.

Note

Do not install Oracle 10g software into an existing Oracle home thatcontains Oracle 9i or earlier software.

13. In the Product-Specific Prerequisite Checks dialog box, verify that all theprerequisite 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 alater patch that obsoletes a listed patch. When you are satisfied thatthe system meets a requirement, manually verify the requirement byselecting the checkbox for the failed check.

14. In the Select Configuration Option dialog box, select Install database softwareonly and click Next.

15. In the Summary dialog box, review the information to ensure you have sufficientdisk space and click Install.Oracle Universal Installer displays a progress meter that adjusts at thecompletion of each installation and relinking phase.

If you are installing from CD-ROM, Oracle Universal Installer prompts youto insert subsequent CD-ROMs when they are required. If you encountererrors, see the Oracle Database Installation Guide for UNIX Systems fortroubleshooting information.

When Oracle Universal Installer completes installing Oracle products, it createsthe 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 andperforms other related root-related configuration activities.

17. After the root.sh script completes successfully, click OK in the Oracle UniversalInstaller Setup Privileges dialog box.

Configuring Oracle softwareConfigure Oracle server processes and Oracle Net.

Configure Oracle server

1. In the window in which you started Oracle Universal Installer, start OracleNet 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 acceptingthe default port number (1521).

Tip

Record the number of the port on which the Oracle database serverlistener for entry during corporate server installation. TeamcenterEnvironment 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), chooseGeneral.

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_TIMEparameter. This value determines how often the Oracle serverchecks for aborted client connections. Teamcenter requires that thisparameter be set to a nonzero value, and the recommended valueis 10 (10 minutes).

j. Save the listener information:

File→Save Network Configuration

Oracle Net Manager saves the listener information and creates thenetwork/admin/listener.ora and network/admin/sqlnet.ora files inthe Oracle home directory.

3. Exit Oracle Net Manager:

File→Exit

4. In the same window in which you started Oracle Net Manager, start the listenerservice:

$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 serverto listen for remote connect requests and that all clients can translate the servicealias identifying the server and database.

If your site uses Oracle Net Assistant for other databases, Siemens PLM Softwarerecommends that you copy the listener.ora and tnsnames.ora files containingentries for your designated Teamcenter database and install these copies on theOracle server. Reload or restart the listener process so that it listens for connectrequests to the new database.

Teamcenter Environment Manager copies the tnsnames.ora file and stores itin the Teamcenter data directory. Teamcenter uses the Oracle TNS_ADMINenvironment variable to locate the tnsnames.ora file. However, if the systemuses the TNS_ADMIN variable to locate configuration files created by Oracle NetAssistant, this setting overrides Teamcenter settings. In this case, you must useOracle Net Assistant to add entries for Teamcenter databases to existing OracleNet configuration files.

For more information, see the System Administration Guide.

Configure an Oracle database for TeamcenterCreate and configure databases for Teamcenter.



Choose how to create the database

Siemens PLM Software provides two methods for creating a Teamcenter databaseconfigured with required user accounts and tablespaces:

• Create a database instance using Siemens PLM Software-provided templateswith Oracle DBCA. The templates populate the database with the requiredOracle user accounts and tablespaces.

Tip

– The templates create a single database user (infodba) per Oraclesystem identifier (SID).

– For best performance and reliability, database parameters set byTeamcenter templates should be customized to suit your installation.This can be performed by your Oracle administrator after Teamcenterinstallation is complete.

• Create a multipurpose Oracle database instance manually using OracleDatabase Configuration Assistant (DBCA). Then use Teamcenter EnvironmentManager to configure the database and populate it with the Oracle user accountsand required table spaces.

Tip

An advantage to creating a multipurpose database instance is that youcan create multiple Teamcenter databases using a single Oracle SID,simplifying administration.

Create a database using Teamcenter Environment ManagerNote

Teamcenter Environment Manager (TEM) verifies your Oracle version duringinstallation. If your Oracle server does not meet the minimum requiredversion, TEM does not allow installation to proceed. For information aboutsupported database servers for Teamcenter 8, see the Siemens PLM Softwarecertification database:


1. Create a multipurpose database using Oracle DBCA. For information, see theOracle documentation.

Tip

Record the following information that you must provide when installingthe Teamcenter corporate server:

• Password of the database system user

DBCA creates the system user with a password of manager. Youcan 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 Manageras described in Teamcenter server installation. To configure a database duringthe 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 thedatabase to use with this installation. When you specify a new database,Teamcenter Environment Manager populates the database and creates avolume.

Create a database instance using Teamcenter templatesNote

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 Teamcentersoftware distribution image to the templates directory of the Oracleinstallation. 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. Forexample:

export ORACLE_BASE=/disk1/oracle

Note

By default, Oracle creates database files in the oradata directory inthe directory pointed to by the ORACLE_BASE environment variable.Before running Oracle Database Configuration Assistant (DBCA), you canset the ORACLE_BASE environment variable to the directory whereyou 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 clickNext.

8. In the Database Identification dialog box, either accept the default databasename 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 theGlobal Database Name box.

Tip

Record the SID of the Oracle instance for entry during corporate serverinstallation. 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 AllAccounts, 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 Locationsfrom Template and click Next.

13. In the Recovery Configuration dialog box, select Specify Flash Recovery Areaand 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 informationabout 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 directoryor, if you did not define the ORACLE_BASE environment variable, in the Oraclehome directory.



Note

• Review the customScripts.log file carefully. This log file is the outputfrom running the custom Teamcenter steps.

• The database creation process creates Teamcenter objects (for example, thedatabase user account, default tablespaces, and create log tables/indexes)by executing the Siemens PLM Software-supplied script in the Oraclehome directory:

/assistants/dbca/templates/tc_create_user_ilog.sql

If this script did not execute successfully, execute it again using the OracleSQL*Plus utility. Log on to SQL*Plus as sysdba.

• The first time Oracle Universal Installer runs, it creates theORACLE_BASE/oraInventory/logs directory, containing an inventory ofinstalled components and performed actions. The most recent log file isnamed installActions.log. Names of previous installation sessions are inthe 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 InstalledProducts on any Oracle Universal Installer window. Do not delete ormanually alter the Inventory directory or its contents. Doing so canprevent Oracle Universal Installer from locating products you installedon 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 serverBefore you install Teamcenter, you must install the Siemens PLM Software CommonLicensing Server to distribute licenses to Teamcenter hosts.

Teamcenter employs named user licensing, which ties each user in the system to anavailable license and ensures the total number of active authors and consumers inthe system is always less than or equal to the number of author/consumer licensespurchased.

There are two levels of Teamcenter user licenses, corresponding to different roleswithin an organization:

• author is a user that creates or modifies data for product and processinformation.

• consumer is a user that views, approves, rejects, or comments on product andprocess information.

Install the ugslmd license daemon:

1. Obtain a Teamcenter 8 license file from Siemens PLM Software. Save thelicense file in a directory accessible to the license server host. This procedureassumes the license file is named tc.lic, but you may give the license file anyname 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 serverhost. Update your Siemens PLM Software customer service representative withyour license server host information.


Chapter 4 Teamcenter preinstallation tasks

Note

• Siemens PLM Software recommends you do not change the licenseserver port from its default value (280001) unless it is necessary toresolve a port conflict.

• Keep note of the host name and port for the license server. TeamcenterEnvironment Manager (TEM) prompts you for these values duringTeamcenter 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 licenseserver, for example, 28000@tchost. The port and host values must match thoseyou 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 theTeamcenter software distribution image.

b. Extract the contents of the ugslicensing.zip archive to a temporarydirectory on your hard drive.

7. Launch the Siemens PLM Software Common License Server installationprogram:

a. Change to the directory in which you extracted the ugslicensing.ziparchive.

b. Open the ugslicensing_install.ans file and edit the contents to specify thedestination directory and path to the Teamcenter license file.

c. Execute the ugslicensing_install command.

Caution

The Siemens PLM Software Common License Server must be runningand two or more seats must be available on that license server duringTeamcenter server installation. Otherwise, database creation fails becausethemake_user utility cannot create the required users in the database.

For more information, see the Installing UGS Licensing for UNIX, InstallingUGS Licensing for Windows, and UGS Licensing User Guide documents in theadditional_documentation directory on the Teamcenter 8 documentationdistribution image.

1. Port 28000 is registered for the Common Licensing Server with the Internet Assigned Numbers Authority (IANA). For moreinformation, see http://www.iana.org/assignments/port-numbers.


Teamcenter preinstallation tasks

Select destination directoriesSelect destination directories for Teamcenter using the following guidelines:

• Ensure that all directories and files are owned and writable by the operatingsystem user installing Teamcenter over an existing installation.

• Install NX FLEXlm files on local drives to ensure that NX FLEXlm services arestarted when the system is restarted.

You can install NX FLEXlm files independently of the Teamcenter applicationroot directory hierarchy using Teamcenter Environment Manager.

• Install Teamcenter on a local disk to configure Teamcenter File Services, FileManagement System file caches, and/or Multi-Site Collaboration services

• You can select automounted NFS directories, but you must supply the automountlink name for the Teamcenter application root directory. Do not supply theautomounted directory (for example, /tmp/mnt/node-name).

Verify required character setTeamcenter installation tools require the ISO8859-1 character set. To verify thatthis character set is loaded, run the locale –a command in a shell. If the output doesnot list ISO8859-1, you must add this character set before you install Teamcenter.

1. Set or export the LC_ALL environment variable by typingLC_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 correctvalue for LC_ALL is displayed.

3. Run the locale command and make sure the LANG variable and all the LC_xvariables 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 (namedTIMEZONE in the etc directory), which can preset this environment, so every timeyou log on and launch a shell, the environment is preset.

The recommended method, however, is to log on to the system using the CommonDesktop Environment (CDE) with the minimum required locale (ISO8859-1) bychoosing Option→Language→en_US.ISO8859-1 during logon.If the ISO8859-1 character set is not loaded on your machine, contact your systemadministrator 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 processnon-English (non-ASCII) locale characters. To facilitate this, the system must befirst loaded with the fonts for that locale.



Note

Ensure the ISO8859-1 character set is loaded before you add any Teamcenterfeatures to your configuration that contains the GM Overlay. If the ISO8859-1character set is not loaded, lists of values (LOVs) for GM Overlay arecorrupted during feature installation. Upgrade of the GM Overlay featurefails if the ISO8859-1 character set is not loaded.

Ensure correct mode on LinuxBefore installing Teamcenter on the Linux operating system, ensure that the systemis operating in the ISO8559-1 mode, rather than the default UTF-8 mode.

Install a volume serverWhen you install Teamcenter File Services (TCFS), TEM assigns ownership of theTCFS service to the operating system user who installed TCFS and automaticallygrants 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 isto write files to volumes residing on remote disks (shared across the network), theTCFS service must be run by a user with access rights across the network. Usuallythis 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 theTeamcenter corporate server, you must install TCFS first, before you begin yourcorporate server installation.

1. Log on to the operating system with the user account you want to own the TCFSvolume.

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 InstallLanguage 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 Helpor see Solutions and features reference.

7. Proceed to the Select Features panel. This panel shows two features preselectedby the Volume Server solution:

Teamcenter File ServicesFMS Server Cache

8. In the Installation Directory box, enter the absolute path to the directory whereyou 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 Portbox, type the port the TCFS process uses.

Note

The TCFS port number must be unique among the services defined in theservices file, and must be the same on every node that accesses the sameversion of NX FLEXlm, Teamcenter File Services, and the database server.

10. Proceed to the Operating System User panel. Type the password for theoperating 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 servercache (FSC) service. For information about required values, click Help.

12. Proceed through the remaining panels, entering required values for the volumeserver. For information about these panels, click Help.

13. Proceed to the Confirm Selections panel. Verify the information you entered. Ifyou want to change any values, click Back to return to the panels you want tochange. 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 theaccount under which you want to install your Teamcenter corporate server. Whenyou install your Teamcenter corporate server as described in Install a Teamcentercorporate server, clear (do not install) the Teamcenter File Services feature. WhenTEM prompts your for the name and port number of the TCFS service, enter thevalues you entered when you installed your volume server.

Install NX and Teamcenter Integration for NX or NX IntegrationInstalling NX is not a prerequisite for installing or using Teamcenter. However,if this is a new installation of both Teamcenter and NX, Siemens PLM Softwarestrongly recommends installing NX prior to installing Teamcenter.

When installing NX for use with Teamcenter, you must install the TeamcenterIntegration for NX or NX Integration executables. Although installed independently,



Teamcenter Integration for NX and NX Integration cannot be used until Teamcenteris configured.

When installing NX, allow the installation to modify system files so that it can createan installed_programs.dat file under the ugs directory. You can use this installedinstalled_programs.dat file as a sample for use on other UNIX workstations of thesame type to access NX using Teamcenter Integration for NX or NX Integration froma local server environment. NX can be installed on a mount point.

Teamcenter Integration for NX and NX Integration provide the same NX userinterface and are both installed with NX. For information, see the installation guidesdistributed with NX. Installing Teamcenter varies depending on whether you have alicense for NX Integration or Teamcenter Integration for NX.

Best installation practicesA Teamcenter network requires one corporate server configuration. Additionalservers are optional, but can help balance network loads and facilitate heterogeneousnetworks (networks with hosts running different operating systems).

If you install the optional servers, Siemens PLM Software recommends installingin 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 (fromthe Teamcenter application root directory) and database-specific configurationfile server (from the Teamcenter data directory). Run Teamcenter EnvironmentManager and install the Teamcenter executables and the directory containingthe database-specific configuration files. Teamcenter can also run locally onthis network node.

2. Optionally install additional Teamcenter servers to provide the followingcapabilities:

• Run Teamcenter executables and point to the existing data directory onthe corporate server host or a another Teamcenter server. This server cancontain a Teamcenter application root directory structure on a network nodethat 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 adatabase-specific configuration file (Teamcenter data directory) server whenthe Teamcenter application root directory is mapped from a Teamcenterapplication server. Teamcenter can also be run locally on this system. Youare creating an additional Teamcenter database for use with an existingTeamcenter application root directory.

Note

Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannotconnect to Microsoft SQL Server database servers. Keep this in mind whenplanning 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 sharedexecutables and files and the Teamcenter data directory. TEM provides a wizardinterface that allows you to define a Teamcenter configuration, select features, andenter the information needed to install the features you select.

Before you start• Locate the Teamcenter software distribution image for your platform. Ifyou install Teamcenter online help, locate the Teamcenter documentationdistribution 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 forlicensing processes.

• Ensure that a database server is installed for Teamcenter and obtain thefollowing 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 TeamcenterEnvironment 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 existingdatabase user:

o If you can create a database user, obtain the following informationabout 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 directoryshould exist; the volume directory is created during installation.

Note

Siemens PLM Software recommends not defining the volume locationunder the Teamcenter application root directory. Doing so leads tocomplications 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 theTeamcenter data directory, Teamcenter application root directory, or volumedirectory 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) andthe server manager must run on the same host server, with the sameuser ID.

• Teamcenter provides server managers based on the J2EE and theMicrosoft .NET platforms. The .NET Web tier is supported only onWindows 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 mustbe on the local host.

If you are installing a volume on the host, FMS does notuse the read cache; Siemens PLM Software recommendsaccepting the default cache size (10 megabytes). Do notspecify 0; specifying 0 creates a file cache with a default sizelarger than 10 megabytes.

If you are not installing a volume on this host, FMS actsas a cache server. In this case, Siemens PLM Softwarerecommends increasing the value to 1000 megabytes.However, choose a size that represents the maximum sizeof the data that must be processed. If you choose 1000megabytes, and a user requests a 3 gigabyte assembly, therequest 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 mustbe on the local host.

If you are installing a volume on this host, FMS does notuse the write cache; Siemens PLM Software recommendsaccepting the default cache size (10 megabytes). Do notspecify 0; specifying 0 creates a file cache with a default sizelarger than 10 megabytes.

If you are not installing a volume on this host, FMS actsas a cache server. In this case, Siemens PLM Softwarerecommends increasing the value to 512 megabytes or more.However, choose a size that represents the maximum size ofthe data that must be processed.

Communication mode betweenFMS components?

Either HTTP or HTTPS.

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, itmust be the master host. Each Teamcenter network musthave at least one master configuration file and one FSCdesignated to read this file.




Data Description

Add the URL of the local hostto the list of servers defined inthe Fms_BootStrap_Urls sitepreference?

This preference is used only by the Teamcenter thin client.

When searching for an assigned FMS server cache to managefile downloads, thin clients contact FSC servers defined inthe Fms_BootStrap_Urls preference in the order they arelisted. The server responds with the FSC server assigned tothe thin client, and all subsequent communication is withthat assigned server cache.

If there is only the thin client and one FSC server in thenetwork, you must select this option. Each Teamcenternetwork must have at least one server listed in theFms_BootStrap_Urls preference for thin client use. Forfailover purposes, you can include multiple servers.

Default settings for the FCC? • Location of the cache directory for all Windows systemsand for all UNIX systems.

• Default maximum size in megabytes of whole filesdownloaded from the volume to rich client hosts. Userscannot download a file whose size exceeds the value youset for this value. This default setting can be overriddenby the FMS client cache configuration file.

Choose a size large enough to accommodate the largestwhole file that users download from the volume. If theuser requests a 3-gigabyte assembly when the cache sizeis set to 1000 megabytes, the request fails.

• Default maximum size in megabytes of whole filesuploaded to a volume from rich client hosts. Users cannotupload a file whose size exceeds the value you set for thisvalue. This default setting can be overridden by the FMSclient cache configuration file.

Choose a size large enough to accommodate the largestwhole file that users upload to the volume.

• Default maximum size in megabytes of the segment filecache used by the embedded viewer and the stand-aloneapplication viewer on rich client hosts.

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

– If no or few rich client users in the network deployLifecycle Visualization, Siemens PLM Softwarerecommends setting this cache size to 10 megabytes.Do not specify 0; specifying 0 creates a file cache witha default size larger than 10 megabytes.

– If rich client users in the network deploy LifecycleVisualization, Siemens PLM Software recommends




Data Descriptionsetting this cache size in the range of 2000 megabytesto 4000 megabytes.

The cache size is initially small, expanding to themaximum size only if a user launches LifecycleVisualization to view a file of that size. The initialsize of the cache is proportional to the value specify.

Install a Teamcenter corporate server1. Log on to the operating system with the Teamcenter user account you created forinstalling 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 InstallLanguage 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 whenyou 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 Helpor see Solutions and features reference.

7. Proceed to the Select Features panel. This panel shows four corporate serverfeatures preselected by the Corporate Server solution:

Teamcenter FoundationTeamcenter File Services



FMS Server CacheNX Integration

8. If you are deploying the J2EE Web tier, select the J2EE Based Server Managerfeature.

9. Select any additional features you want to include in your configuration. Fordescriptions of features, point to the feature in the list or click Help or seeSolutions and features reference.

Note

• You can add features to the corporate server configuration duringinstallation or you can add them later using TEM in maintenancemode.

• If you want to install a custom solution, see Install a template usingTEM.

• If you install Teamcenter Automotive Edition and GM Overlay, makesure you install the GM Overlay for Rich Client feature on two-tierrich client hosts, and complete the required postinstallation steps.For more information about installing the GM Overlay for RichClient feature, see the Installation on Windows Clients Guide and theInstallation on UNIX, Linux, and Macintosh Clients Guide.

10. In the Installation Directory box, enter the absolute path to the directory whereyou want to install Teamcenter.

Note

• You must install Teamcenter in a new directory. If you want toupgrade an existing installation, return to the Getting Started paneland select an upgrade installation. For information about upgrading,see the Upgrade Guide.

• The Installation Directory value is the Teamcenter application rootdirectory stored in by the TC_ROOT environment variable.

Do not set TC_ROOT in the system environment. TEM sets thisvariable as required in various scripts. Setting this variable in theoperating system can cause conflicts if you install more than oneconfiguration.

11. Proceed to the TCFS Service panel.

In the Name box, type the name under which the TCFS process runs. In the Portbox, type the port the TCFS process uses.

Note

The TCFS port number must be unique among the services defined in theservices file, and must be the same on every node that accesses the sameversion of NX FLEXlm, Teamcenter File Services, and the database server.



12. Proceed to the Operating System User panel. Type the password for theoperating system account to which you logged on to install Teamcenter.

13. Proceed to the Configure TC_DATA panel. Choose whether to create a newdata directory or connect to an existing one, and then enter the location of thedata directory.

This Data Directory Location value is referenced as the Teamcenter datadirectory or the TC_DATA directory. This value is stored in the TC_DATAenvironment variable. Each data directory is associated with a single databaseuser within a database instance.

Note

Do not set TC_DATA in the system environment. TEM sets this variableas required in various scripts. Setting this variable in the operatingsystem 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 createthe database user:

a. Click Create. TEM displays the Create Oracle Database panel.

b. Enter the required values to create the database user, and then clickNext.

Note

• For detailed descriptions of the values on this panel, click the Helpbutton.

• Teamcenter Environment Manager (TEM) verifies your Oracle versionduring installation. If your Oracle server does not meet the minimumrequired version, TEM does not allow installation to proceed.3

• Teamcenter servers and two-tier rich clients on UNIX or Linux hostscannot connect to Microsoft SQL Server database servers. Keep thisin 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 wantTEM 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 locationinformation. In the Volume Location box, type the absolute path to the directoryfor the volume, ensuring that the parent directory exists.

Siemens PLM Software recommends not defining the volume location under theTeamcenter application root directory. Doing so leads to complications whenupgrading to a later version of Teamcenter.

16. Proceed to the Transient Volume Settings panel.

A transient volume is an operating system directory controlled by Teamcenterand used to store temporary data for transport of reports, PLM XML data, andother nonvolume data between the enterprise tier and client tier in a deployedfour-tier architecture. All four-tier clients that access the corporate server youare 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 SystemAdministration Guide.

17. Proceed through the remaining panels, entering the required information for thefeatures you selected. For information about these panels, click Help.

18. When you complete entering information for optional features, TEM displays theDatabase Template Summary panel, which lists templates to be applied whenTEM populates the database during installation. This panel is for informationonly. 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 wantto change. Otherwise, click Next to begin installing the Teamcenter corporateserver.

Note

• If you chose the Online Help feature, TEM prompts for the location ofthe online help files during installation. Enter the path to the locationof tchelp.jar file on the Teamcenter documentation distributionimage.

• If an error occurs during installation, follow the instructions in theerror message displayed by TEM or see Troubleshooting for possiblesolutions.

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-2Prepare the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . 6-2Configure Multi-Site Collaboration daemons . . . . . . . . . . . . . . . . . . . . . . 6-4

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


Chapter

6 Teamcenter postinstallation tasks

Perform the appropriate procedures to complete installation of Teamcenter features.

Run the postinstallation tasks programIf you installed the corporate server without root privileges, a user with rootprivileges must run the root_post_install_tasks.sh program in the installdirectory in the Teamcenter application installation directory.

Modifying the services fileWhen you configure Teamcenter File Services, and have root privileges, TeamcenterEnvironment Manager adds the following services information to the etc/servicesfile:

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. TheTCFS service name and port number must the same for each database using theservice. Teamcenter Environment Manager allows you to set up customized TCFSservices for each configuration. The service name and port number must be uniquefor each configuration.

Systems that use Network Information Services (Yellow Pages) or NIS Plus obtainservices information indirectly from the etc/services file on the NIS masternode.Teamcenter Environment Manager can add these services only to the NISmaster, 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 propagatethe changes to all NIS clients before installing any clients.

Start Teamcenter database daemonsYou can start Teamcenter database daemons manually by executing the followingstartup 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 directoriesdepending upon the operating system. For all systems except AIX, the script residesin the column labelled Script Location. There is a corresponding symbolic linklocated in the Startup Directory column. The symbolic links also have differentS prefix numbers depending on the operating system.

For AIX systems, the startup directory is /etc, and one file (rc.ugs) calls all thedaemon 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.ugsfile

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 CollaborationMulti-Site Collaboration allows the exchange of Teamcenter data objects betweendatabases. Each database should be easily accessible via TCP/IP, either over theInternet or the company intranet. Configuration of Multi-Site Collaboration isoptional.

Coordinate configuration of Multi-Site Collaboration with the system administratorsof the other Teamcenter databases to be part of the Multi-Site Collaborationenvironment. Information about all participating Teamcenter database sites mustbe stored in each database and in the site preference files. In addition, you mustidentify the network nodes to run Multi-Site Collaboration server processes for thesedatabases 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 areanetwork:

1. Identify all Teamcenter databases to be part of the Multi-Site Collaborationenvironment.

2. Identify the Teamcenter database to act as the ODS database.

This database stores records about the data objects published by other databasesin the Multi-Site Collaboration environment (that is, made public to the otherdatabases).

This can be one of the databases identified in step 1 or it can be a dedicateddatabase. 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 thatdatabase to act as the ODS server.

The ods daemon runs on this system to listen for publication queries fromother databases.

4. For each database identified at step 1, identify a network node local to thatdatabase to act as the IDSM for that database.

When other databases request an object published from this database, the idsmdaemon 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 bechanged. 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 namedOrganization 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 forthe local database are listed first. For more information, see Organization Guide.

6. Using the information obtained in steps 2 through 5, populate each database sitetable with information about the other sites using the Organization applicationin the Teamcenter rich client.

The node for each site is the name of the network node to run the necessaryMulti-Site Collaboration daemons (idsm and/or ods). If the site is an ODSdatabase, 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 ODSserver as an IDSM server.

7. For each database identified in step 1 and step 2, edit the site preference forthe database and modify the following preferences to reflect the Multi-SiteCollaboration environment:

ODS_permitted_sites (ODS database only)ODS_site (Non-ODS databases)ODS_searchable_sitesODS_searchable_sites_excludedIDSM_permitted_sitesIDSM_permitted_users_from_site_site-nameIDSM_permitted_transfer_sitesIDSM_permitted_transfer_users_from_site_site-nameIDSM_permitted_checkout_sitesIDSM_permitted_checkout_users_from_site_site-nameFms_BootStrap_UrlsTC_publishable_classesTC_transfer_area

For more information about these preferences, see the Teamcenter Preferencesand Environment Variables Reference.

8. For each database identified in step 1 and step 2, copy all POM transmit schemafiles for that database into the POM transmit schema directories for each of theother 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 Teamcenterinstallation program on that node to configure and start the Multi-SiteCollaboration 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 inthe 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 theinetd daemon to reload its configuration. As a result, the Multi-Site Collaborationdaemons are launched to complete the installation.

Back up new installationsSiemens PLM Software strongly recommends backing up new Teamcenter andOracle 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 tcserverprocesses.

2. Set Teamcenter environment variables by entering the following commands:

TC_ROOT=/usr/Siemens/Teamcenter8; export TC_ROOTTC_DATA=/usr/Siemens/Teamcenter8/teamcenterdata; export TC_DATA. $TC_DATA/tc_profilevars

This example assumes that Teamcenter is installed under theusr/Siemens/Teamcenter8 directory.

Sourcing the iman_cshvars file creates a csh subshell in which Teamcenterenvironment 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 eachnode 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 createdother directories that contain data used by your existing Teamcenter installation,such as a separate POM transmit schema directory, Siemens PLM Softwarerecommends 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-5Start 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 informationThe 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 globalserver pool. This name must be unique for this database andcorporate server.

You must supply this same name for the TreeCache clustername 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 servermanager host has multiple IP addresses, the server hostname allows you to control which IP address is used whenconnecting to Teamcenter servers. The value entered in thisbox 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 onwhich the server manager and Web tier run are configured toallow 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.


http://www.jboss.org/jbosscache/

http://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 memberattempts to provide the TreeCache service. If the port isin use, the application fails to start and issues an errorabout having no port to bind to. Select an available portand retry.

This port can vary from the port specified for the Webtier application.

If you use multiple TreeCaches on the same host (forexample, a server manager and a Web tier application),the TreeCaches must use different local service ports.Depending on the network configuration, specifying thesame local service port for each component may causeproblems when they are on different machines.

• Maximum time in milliseconds that a TreeCache clustermember waits for peer responses to TCP pings.

The larger the value you specify, the more slowly thefirst server manager starts.

Typically, you supply this same value for theConnection Timeout parameter when configuring theWeb tier application.

• A list of addresses (host name and port number pairs) toping for peer members of the TreeCache cluster in TCPcommunication mode.

This cluster member pings each host/port pair in thelist. To be found, a peer must have a matching serviceport (see the Local Service Port context parameter).Once a peer is found, the peers exchange data regardingavailable server pools.

Note

You can include more than one address on a givenhost. It is not necessary to include all members ofthe cluster in this list. However, it is importantthat when each cluster member after the first isstarted, it should ping a member that is alreadyin the cluster.

For example, it is valid to include only a subset ofthe server managers and none of the applicationservers. In this case, the cluster connects onlywhen one or more of the designated managers isrunning. This method reduces pinging and therebyimproves performance.


Installing the server manager


Data Description

For small configurations, all members (servermanagers and web tiers) should be included inthe peers list. For larger configurations, it isrecommended that the number of pinged ports belimited to no more than six. All members shouldping at least the same subset of primary servermanagers so that tree caches connect and data isshared.

Maximum servers in pool Maximum number of Teamcenter server processes allowedto run in this pool (for a single-host configuration) or in thissubpool (for a multihost configuration).

Minimum warm servers Minimum number of Teamcenter server processes in this poolthat are started but not logged onto.

If necessary to maintain the minimum number of warmservers, while not exceeding the maximum number of serverprocesses, the server manager times out servers in use.

Target number of serverprocesses

Target number of server processes to be available in this poolor subpool during specified times.

You specify these values as time and integer pairs separatedby commas. For example:

0700 3, 1700 2

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

• If the number of server processes is below the specifiedtarget, warm servers are added to reach this number.In this case, the number of warm servers exceeds theminimum.

• If the number of server processes exceeds the specifiedtarget, only the minimum number of warm servers ismaintained and servers are terminated as they time out.

Number of logons Number of logons the server manager allows per minute forthis pool or subpool. The default value, 0, allows unlimitedlogons per minute.

CPU load Whether you want the server manager to control serverprocesses 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 Guideavailable on GTAC.



Install the J2EE server manager1. Launch Teamcenter Environment Manager (TEM). Create a new Teamcenterconfiguration or choose an existing configuration to which you want to add theJ2EE-based server manager.

2. Proceed to the Select Features panel. Under Corporate Server, select J2EEbased Server Manager.

3. Proceed through other panels as for a typical corporate server installation orupdate, entering configuration values as needed2 until you reach the ServerManager for J2EE panel.

Note

For information about fields in TEM panels, click the Help buttons ineach panel.

4. In the Pool ID and JMX HTTP Adaptor Port boxes, type a name and port for theserver pool.

Enter the remaining values in the panel as described in Gather requiredinformation.

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 Teamcenterserver processes allowed to run in the serverpool. Single-host configurations can contain asingle server pool. If you create a multi-hostconfiguration, you can create a server pool andsubpools. The total number of servers is notallowed to exceed the Max Servers in Sub-Poolvalue.

Min Warm Servers Specifies the minimum number of Teamcenterserver processes in the server pool that are startedbut not logged onto. The server manager may timeout servers as needed, but maintains the minimumready (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 tobe available in the server pool or subpool duringspecified times. Specify these values as time andinteger pairs separated by commas. For example, avalue of 0700 3, 1700 2 sets the target number ofserver processes as 3 servers from 7 a.m. until 5p.m. and 2 servers from 5 p.m. until 7 a.m.

If the number of server processes is below thespecified target, warm servers are added to reachthis number. In this case, the number of warmservers exceeds the minimum. If the numberof server processes exceeds the specified target,only the minimum number of warm servers ismaintained and servers are terminated as theytime out.

The remaining parameters in the Server Manager Performance Tuning panelare optional. Type values for these parameters as needed.

7. Proceed through remaining panels until you reach the Confirm Selectionspanel. Click Next to begin installing the Teamcenter server with the J2EE-basedserver manager.

8. When installation completes, exit TEM.

Start the server managerIf you install the J2EE based Server Manager feature, you must start the servermanager 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. Forexample:

mgrstartMYDB

The server manager displays several messages during startup. The servermanager started successfully if you see a message similar to the following thatcontains an IP address and a port number:

-------------------------------------------------------GMS: address is 153.172.61.24:17800-------------------------------------------------------



4. Launch the server manager user interface fromhttp://manager_host:jmx_http_adaptor_port.

Replace manager_host with the machine on which the manager is running, andjmx_http_adaptor_port with the number of the port running a Java ManagementExtension (JMX) HTTP adaptor. (You define this in Teamcenter EnvironmentManager when you set the JMX HTTP Adaptor Port.)

5. To log on, use the default user ID (manager) and password (manager). Youcan change these values using the Change_Authentication operation on thePool Manager page.

The server manager displays the Agent View page. Bookmark this page forfuture reference.

Note

Running the J2EE-based server manager as a daemon, as opposed tomanually executing the server manager, is not supported.

For information about configuring the server manager see the System AdministrationGuide. Also, for information about using the server manager interface, see theSystem 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. Afteryou install the Business Modeler IDE, allocate additional memory so that BusinessModeler IDE has enough memory to run.

Install the Business Modeler IDE as a stand-alone application1. Start Teamcenter Environment Manager (TEM).

2. Proceed to the Solutions panel. In the Solutions panel, select Business ModelerIDE, 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 templatesare only used within the Business Modeler IDE to extend the Teamcenterdata model.

• Client

Installs the IDE as a client on your machine.

• Mapping Designer (optional)

Installs the Mapping Designer data model mapping tool into theBusiness Modeler IDE.

• Digital Dashboard (optional)

Installs the Digital Dashboard application into the Business ModelerIDE. The Digital Dashboard is used by system administrators to examinelog files.

• Configure Teamcenter Servers

Select these options to automatically create a server connection profilefor 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-tierenvironment over a network using IIOP protocol.


Chapter 8 Install the Business Modeler IDE

– 4 Tier Teamcenter Server ConfigurationSelect this option if you want to connect to a server in a four-tierenvironment using HTTP protocol.

When you select one of these options, a server connection profile is addedin 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 serverrather than a production server. However, you can also deployoperational data such as LOVs and rules to production servers.

b. In the Installation Directory, enter the location where you want to installthe Business Modeler IDE. The Business Modeler IDE files are installed to abmide 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 forTeamcenter solutions.

Select the same templates that were installed on the server so that you cansee the same data model definitions in the Business Modeler IDE that wereinstalled on the server. At a minimum, select the Teamcenter Foundationcheck box. The Foundation template contains the data model used for coreTeamcenter functions. All customer templates must extend the Foundationtemplate.

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 thirdparty, click the Browse button and browse to the directory where thetemplates are located.

c. Click Next.

5. In the Java Development Kit dialog box, click the browse button to locatethe JDK installed on your system. The kit is used for creating services. ForTeamcenter 8, use Java Development Kit 1.5 (5.0). Click Next.

6. If you selected the 2 Tier Teamcenter Server Configuration option, perform thefollowing 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 usewhen connecting to the server. NORMAL is the default.If you want to allow multiple concurrent user sessions to the two-tier richclient, select PER_CLIENT.


Install the Business Modeler IDE

c. Click the ellipse button to the right of the Server Config Folder box toselect the folder where you want this configuration saved. The default isTC_ROOT\iiopservers.

d. Click the Edit button to the right of the TcServers box to change the serverconnection profile settings, or click the Add button to add another serverto connect to.

e. Click Next.

7. If you selected the 4 Tier Teamcenter Server Configuration option, perform thefollowing steps in the Middle-tier Servers Settings panel:a. Leave the Compress (gzip) the responses from the Web application serverscheck 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 wantto add another server to connect to.

c. Click Next.

8. Complete the remaining panels to finish the installation in TeamcenterEnvironment Manager. When the installation is complete, exit TeamcenterEnvironment Manager.

9. Verify the installed files in the install-location/bmide directory.The following data model files are placed into theinstall-location/bmide/templates folder:

• baselines\template-name_tcbaseline.xmlContains a snapshot of the template’s data model taken at the release ofTeamcenter 8, if a baseline was taken.

• template-name_dependency.xmlLists the other templates that this template is built on top of, for example,the Foundation template.

• template-name_template.xmlContains the data model for this template, including business objects,classes, properties, attributes, lists of values (LOVs), and so on.

• master.xmlLists the template XML files included in the data model, for example, thefoundation_template.xml file.

Install the Business Modeler IDE to an existing Eclipse environmentIf you already have Eclipse installed, you can install the Business Modeler IDEinto your Eclipse environment. Install the Business Modeler IDE to an Eclipseenvironment if you want to install additional plug-ins to aid in your configurationwork.



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

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 archivecontain plug-ins needed by the Business Modeler IDE.

Note

Install these only if your Eclipse environment does not already have theplug-ins.

• cdt-master-4.0.3.zip

Contains the C/C++ Development Toolkit (CDT) plug-ins. CDT providesthe capability to work with projects that use C or C++ as a programminglanguage.

• dtp-sdk_1.5.zip

Contains the Data Tools Platform (DTP) plug-ins. DTP provides a number oftools for working with data sources.

• eclipse-JDT-SDK-3.3.zip

Contains the Java Development Tools (JDT) plug-ins. JDT provides tools forimplementing a Java IDE.

• emf-sdo-xsd-SDK-2.3.0.zip

Contains the Eclipse Modeling Framework (EMF) plug-ins. EMF is amodeling framework and code generation facility for building tools and otherapplications based on a structured data model.

• GEF-SDK-3.3.zip

Contains the Graphical Editing Framework (GEF) plug-ins. GEF allowsdevelopers to take an existing application model and create a graphicaleditor.

• wtp-sdk-R-2.0.zip

Contains the Web Tools Platform (WTP) plug-ins. WTP helps you developWeb and Java EE applications.



5. If you need language support, extract the appropriate language pack to yourEclipse directory:

• NLpack1-GEF-SDK-3.2.zip

Contains the GEF language pack for German, Spanish, French, Italian,Japanese, Korean, Portuguese (Brazil), Traditional Chinese, and SimplifiedChinese.

• 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 TeamcenterEnvironment Manager (TEM).

In the Select Features window, choose Business Modeler IDE→BusinessModeler Templates (do not choose Client). The templates are installed underthe 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 IDEAllocate memory to the Business Modeler IDE so that it has enough to launch andrun. You can allocate memory in the following ways:

• BusinessModelerIDE.ini file

To increase the memory allocated to the Business Modeler IDE, open theinstall-location/bmide/client/BusinessModelerIDE.ini file and change the–Xmx512M value to a higher number to allocate maximum Java heap size. Forexample, 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 setsthe maximum Java heap size.

• BMIDE_SCRIPT_ARGS environment variable

To allocate the memory required by scripts during installation, update, orload of templates with large data models, create a BMIDE_SCRIPT_ARGSenvironment 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 ModelerIDE, 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, inboth the BMIDE_SCRIPT_ARGS environment variable and theBusinessModelerIDE.ini file.

Note

If you are running the Business Modeler IDE in an Eclipse environment, runthe following command to increase virtual memory to 1 GB:

eclipse.exe -vmargs -Xmx1024M

Start the Business Modeler IDE1. You can start the Business Modeler IDE in several ways, depending on howyou installed it:

• Start the stand-alone application.

Note

To ensure that you have enough memory to run the Business ModelerIDE, allocate memory in the BusinessModelerIDE.ini file and in aBMIDE_SCRIPT_ARGS environment variable.

• Start from an Eclipse environment.

Navigate to the directory where Eclipse is installed and execute the Eclipsecommand.

Note

To ensure that you have enough memory to run Eclipse, you can runthe Eclipse.exe command with a virtual memory argument. Forexample, 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 windowis displayed.

2. Click one of the buttons in the Welcome window to learn more about theBusiness 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 theWelcome window.

The Workbench is the main window in Eclipse. The Workbench window showsone or more perspectives. A perspective is an arrangement of views (such as theNavigator) and editors. At the top of theWorkbench is a toolbar that allows youto open new perspectives and move between ones already open. The name of theactive perspective is shown in the title of the window.

Note

You can access the Welcome window again later by choosingHelp→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 beingallocated to the Business Modeler IDE.

5. In the Business Modeler IDE perspective, click the Business Objects tab toopen the Business Objects view. This view displays the business objects (types)defined in the data model. Use this view to create new business objects torepresent parts, documents, and so on.


Chapter

9 Installing a custom solution orthird-party template

Install a template using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Update a template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2


Chapter

9 Installing a custom solution orthird-party template

Install a template using TEMAfter you package extensions, install the resulting template to a productionenvironment using Teamcenter Environment Manager (TEM). You can also use thisprocedure to install a third-party template.

1. Copy the template files from the packaging directory on your Business ModelerIDE client to a directory that is accessible by the server.

By default, packaged template files are located in the Business Modeler IDEworkspace directory in the folder under the project.

On UNIX, users must have permissions to the workspace directory.

2. Start Teamcenter Environment Manager (TEM).

3. In the Maintenance panel, choose Configuration Manager and click Next.

4. In the Configuration Maintenance panel, choose Perform maintenance on anexisting configuration and click Next.

5. In the Configuration Selection pane, select the configuration from which thecorporate server was installed. Click Next.

6. In the Feature Maintenance panel, under the Teamcenter section, selectAdd/Remove Features. Click Next.

Note

If you already installed a template to the database and want to updatethe template, under the Teamcenter Foundation section, select Updatethe database. This option should not be used to install a new templatebut only to update an already installed template.

Use the Add/Update templates for working within the Business ModelerIDE client option under Business Modeler Templates only if you want toadd a dependent template to your Business Modeler IDE.

7. In the Select Features panel, click the Browse button on the lower right sideof the panel.

8. Browse to the directory where you have copied the template files. In theFiles 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 Serveron the Select Features panel.

9. Select the new template in the Select Features panel under TeamcenterCorporate Server. Click Next.

10. In the Teamcenter Administrative User panel, enter your username andpassword to log on to the server. Click Next.

11. The Database Template Summary panel displays the list of templates that areinstalled 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 packagingdirectory and unzip it to a temporary location. Copy the following files to theserver in the TC_ROOT/install/template-name folder:

template-name_template.xmltemplate-name_dependency.xmltemplate-name_tcbaseline.xml (if the file exists)

c. Launch Teamcenter Environment Manager in the maintenance mode andcontinue with recovery.

13. To verify the installation of the new template, confirm that the TC_DATAdirectory on the Teamcenter server contains the new template files.

Also log on to the server and confirm that you can create instances of your newdata model.

Update a templateIf you already installed a template as a new feature and want to update it becauseyou have added more data model definitions to it, perform the following steps:

1. Copy the packaged template files from the packaging directory on yourBusiness Modeler IDE client to a directory that is accessible by the server.

By default, packaged template files are located in the Business Modeler IDEworkspace directory in the folder under the project. .

2. Start Teamcenter Environment Manager (TEM).

3. In the Maintenance panel, choose Configuration Manager and click Next.

4. In the Configuration Maintenance panel, choose Perform maintenance on anexisting configuration and click Next.


Installing a custom solution or third-party template

5. The Configuration Selection panel displays the installed configuration. ClickNext.

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 ModelerTemplates only if you want to add or update a dependent template toyour Business Modeler IDE.

7. In the Teamcenter Administrative User panel, enter your user name andpassword to log on to the server. Click Next.

8. The Database Updater panel displays currently installed templates in theApplied Templates table. Click the Browse button in the lower right corner ofthe 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 confirmthat 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-2Configure 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 processmanagement data, make sure that the Teamcenter corporate server is installed onthe installation host and the Teamcenter database is configured or upgraded.

Install the Manufacturing content kitNote

This option populates a database with sample data in a predeterminedclassification hierarchy. Use it for creating and maintaining a sampledatabase, not for importing data to a working database. To import other data,you must use the SML utility (smlutility), the ICS utility (icsutility), orPLM XML.

1. Obtain the Teamcenter software distribution image and navigate to theadvanced_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 mustpoint 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 andclick 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 selecttools, machines, fixtures, weld guns, robots, or NX CAM templates. If you selecttools, Teamcenter loads a subset of the Manufacturing Tooling Library containing20 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 updateyour existing classification data, select the Overwrite existing data check box. Ifyou leave this check box cleared, Teamcenter inserts only missing data into theclassification 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 Teamcenterinstallation 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 yourdatabase. When the setup is complete, the name and location of the install logare displayed.

Populate the sample database for ManufacturingTo populate the sample database on a UNIX server, you must use a Windows richclient. If you do not have one in your network, you must add one temporarily. Onceyou have done this, start the setup found on the Windows installation CD-ROMunder: cdrom\advanced_installations\resource_management\server

Alternatively, you can move a copy of your UNIX database and Teamcenter volumeto a Windows client, load the Resource Manager with default data on Windows, andthen move the populated database and volume back to UNIX.

Install the Manufacturing Tooling Library1. Obtain the Manufacturing Tooling Library installation DVD.

2. Click Setup.exe.Teamcenter displays the Setup Configuration Type Selection dialog box.

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 mustpoint 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 andclick 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 andmore than 30,000 catalog components. This is original vendor data that youcan use to create tools and assemblies. The catalog hierarchy and data willbe updated by Siemens PLM Software at regular intervals in the future.

• Customer Hierarchy

This structure contains two classification hierarchies—one for yourcomponents, and one for the assemblies you create. You can fill thishierarchy with your customer-specific data, mapping data from the cataloghierarchy where necessary. This hierarchy will not be automatically updatedby Siemens PLM Software in the future.

• Customer Sample Data

This loads approximately 20 sample tool assemblies and their componentparts into the customer hierarchy. These assemblies contain 3D graphicsand image files.

Note

The objects created by loading the sample data are all of the Itemitem type. To load the sample data, your database should supportthis 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 updateyour existing classification data, select the Overwrite existing data check box. Ifyou leave this check box cleared, Teamcenter inserts only missing data into theclassification 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 bedisplayed 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 ofthe data.

Note

The 20 sample tool assemblies are available only in metric. If you selectinch, they are loaded into the database but not converted into inch.This can cause the data to appear incorrectly but does not affect theclassification hierarchies.

13. Click Next.

Teamcenter displays the Name and Password dialog box.



14. Type the user name, password, and group name of the valid Teamcenterinstallation account under which you want to install the data and click Next.

Teamcenter displays the Confirm Selections dialog box.

15. Confirm that all your selections are correct and then click Next.

Teamcenter installs the specified classification hierarchies and data into yourdatabase. When the setup is complete, the name and location of the install logare displayed.

Configure NX CAM

When you install the manufacturing tooling data, you must configure NX CAM sothat the new data appears in the library selection dialog boxes when searchingfor classified tools in NX CAM.

1. Start the setup program as described in Install the Manufacturing ToolingLibrary or Install the Manufacturing content kit.

Teamcenter displays the Setup Configuration Type Selection dialog box.

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

• If you are installing the Teamcenter Manufacturing content kit, Teamcenteropens the Confirm Selections dialog box. Proceed to step 5.

• If you are installing the Manufacturing Tooling Library, Teamcenter displaysthe Language Selection dialog box.


Manufacturing

4. Select the language in which you want the NX Library selection dialog boxes toappear and click Next.

Teamcenter displays the Confirm Selections dialog box.

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, itcopies 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 copiedto 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 iscopied 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 copiedto 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 iscopied to UGII_BASE_DIR\MACH\resource\library\tool\inclass\dbc_mfg_toollib_sample_customer_tlas_eng.def.

• Appends new materials to the existingtool_materials.dat material library file found inUGII_BASE_DIR\MACH\resource\library\feeds_speeds\ascii\tool_materials.dat.

• Adjusts the LIBRARY_TOOL entry in thecam_part_planner_library.dat configuration file found inUGII_BASE_DIR\MACH\resource\configuration\cam_part_planner_library.dat to point to the new ManufacturingTooling Library or Teamcenter Manufacturing content kit event handlerand definition file.

• Creates backup copies for all NX files that are modified.

6. Select the cam_part_planner_library.dat configuration file when workingin NX CAM.

When you retrieve a tool from the Teamcenter database in NX CAM, the libraryselection dialogs now show the classification structure from the customerassembly hierarchy, including images corresponding to the new tooling data. Youcan search for and retrieve your customer-specific tool assembly data.



Planning data migration from Genius4000 to Resource ManagerThe data in a Genius4000 installation is composed of database instances andassociated files, such as graphics files, part files, and text documents residing ona file system.

If you are running Genius4000 solely on a UNIX system with no Microsoft Windowsclient, you can perform only part of the migration on the UNIX system. You mustuse a Windows system to perform the remainder of the process.

On the UNIX system, you create a migration directory structure and copy it to theWindows system using a script provided with the Teamcenter’s manufacturingprocess management Genius2MRM Migration kit. Download the kit from the FTPserver on Siemens PLM Software GTAC online support

Converting Genius4000 data to Resource Manager-compliant data involves thefollowing steps:

Step 1: Export data from the Genius4000 database.

This step performs two functions:

• Export the contents of the Genius4000 database to SML ASCII filesusing the standard Genius SML Export function. The SML ASCIIfiles are stored in an interim export directory where they are used asinput for the conversion process.

• Copy all associated files residing in the Genius4000 file system to theResource Manager import directories. Where necessary, these filesare 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 andconverts them into formats required by Resource Manager. You havesome choice as to the final file types the system creates.

File conversion converts TOL files of records that do not have anassociated NX part file to NX part files. Since such files generally contain2D graphics that cannot be converted to JT format, they are copied toan intermediate directory (GeniusTolGraphics) and converted to CGMformat in a later conversion step. It also modifies the color tables ofHPGL files so that the embedded viewer displays them with the samecolors previously used by Genius4000 and UNC8500i.

This is the only step in the migration procedure that is performed ona 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 anexisting Resource Manager database. This procedure is similar to thatrequired to install the small or full manufacturing content kit.

Begin migration on the UNIX system:

1. Download the Teamcenter’s manufacturing process management Genius2MRMMigration kit from the FTP server on Siemens PLM Software GTAC onlinesupport.


http://support.plms-eds.com



Manufacturing

2. Copy the genius2mrm_copy_files.ucl script from theUGS/GeniusToMRM/Genius4000/genius_base/ucl directory to the UNIXsystem (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=Trueexport 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 datayou 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 arecopied. If this directory does not exist, the script creates it. The output directoryand subdirectories contain the class graphics.

This creates the following structure:

g4_filesg4_files/ClassGraphicsg4_files/ClassGraphics/Imagesg4_files/SampleDataGraphicsg4_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 toSampleDataGraphics.

• If the system finds a PRT file for an instance, it ignores any additional TOLfile.

• If there is only a TOL file for one resource (and no NX part file), this TOL fileis 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 thereis 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 PRTfiles which were converted from TOL files to CGM files.

7. Create one compressed container-file from the output structure. Create eithera 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 Windowssystem. For information, see the instructions for configuring Teamcenter’smanufacturing process management in the Installation on Windows Servers Guide.

Migrate Genius4000 data to Resource ManagerConvert Genius4000 data to Resource Manager using the Genius4000 to ResourceManager migration kit. This kit is available for download on the Siemens PLMSoftware GTAC FTP server.


Chapter

11 Installing Teamcenter’s reportingand 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 reportingand analytics

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

Before you beginDownload the Teamcenter’s reporting and analytics(Reporting and Analytics) software distribution image(TeamcenterReportingAndAnalytics-2007-platform.tar ) from the SiemensPLM Software FTP site.

TcRA requires additional preinstallation steps. For information about steps toperform before you install Teamcenter’s reporting and analytics (Reporting andAnalytics), see the Teamcenter’s reporting and analytics 2007 Deployment Guide inthe Reporting and Analytics software distribution image.

Create the Reporting and Analytics databaseReporting and Analytics requires an Oracle database for Reporting and Analyticsmetadata. Your database administrator must create this database before you launchTeamcenter Environment Manager (TEM) to install Reporting and Analytics.

TEM creates the required table structure for Reporting and Analytics, but thedatabase user and tablespaces must exist before you install Reporting and Analytics.Metadata tables are divided into three categories based on the number of rows theywill hold and the growth potential. These tables can be stored in the same tablespaceor in separate tablespaces for better performance and manageability. Siemens PLMSoftware recommends creating the following tablespaces:

Tablespace Description

Small Typical number of rows 1000. Minimum size 50MB Growthis very slow

Medium Typical number of rows 10000. Minimum size 150MBGrowth is Slow.

Large Typically 1000000 rows or more. Minimum size 500MBGrowth 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 andAnalytics, see Pre Installation Steps in the Teamcenter Environment Manager 2007Deployment Guide.

Configure the Reporting and Analytics license fileReporting and Analytics requires an eQube license file (license.dat) on the hostwhere the Reporting and Analytics license server runs. TEM requires the location ofthe license file to install the Reporting and Analytics license server during Reportingand Analytics installation.

Note

On Sun Solaris and Hewlett-Packard HP-UX systems, the Reporting andAnalytics license server uses the host’s HOSTID value address to identify thehost. On Linux systems, the license server uses the host’s MAC address.You must supply this information when you request an eQube license filefrom eQ Technologic.

Install Reporting and Analytics1. Launch TEM.

2. Create a new Teamcenter configuration or select an existing configuration towhich you want to add Reporting and Analytics.

3. Proceed to the Reporting and Analytics Install Options and General Settingspanel. Select one or more of the following options to include in your Reportingand Analytics installation:

Create license server Specifies you want to install a Reporting andAnalytics license server. If you select thisoption, TEM later prompts for the location ofthe eQube license file (license.dat). If you donot select this option, TEM later prompts forthe location of the Reporting and Analyticslicense server.

Create WAR file Specifies you want to generate a Reportingand Analytics WAR file.

Create metadata Specifies you want to populate the metadatadatabase for Reporting and Analytics. Selectthis only during the first installation ofReporting and Analytics. If you are upgradingfrom a previous version of Reporting andAnalytics or adding additional hosts, do notselect 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 DescriptionReporting and AnalyticsLicense Server Settings

In the License File box, enter the locationof the Reporting and Analytics license file(license.dat). This panel is displayed only ifyou select Create license server.

Reporting and Analytics WARSettings

In the Web Application Context box, typethe application name for the Reporting andAnalytics Web application. This name isincluded in the URL for the Web application:

http://host-name:port/context-name/rest-of-path

For example, if the Web application contextis Reporting and Analytics, a resulting URLcould be as follows:

http://AcmeCorp:7001/TcRA/BuildNPlay

This panel is displayed only if you selectCreate WAR file.

Reporting and AnalyticsLicense Settings

In the License Server Host box, type thethe IP address or the fully qualified name ofthe Reporting and Analytics license serverhost. In the License Server Port box, enterthe port on which the license server acceptsconnections. This panel is displayed only ifyou do not select Create license server.

Reporting and AnalyticsDatabase Selection

In the Database Engine Selection box,choose your database vendor (Oracle orMS SQL Server 2005, and then enter therequired information about the Reportingand Analytics database you created in Createthe Reporting and Analytics database. Forinformation about fields in this panel, clickHelp.

Reporting and Analytics WARand Metadata Settings

Specify Reporting and Analytics WAR andmetadata settings:

Enable SSO If you use Reporting andAnalytics with SecurityServices, select thischeck box. This optionrequires that you installTeamcenter with SecurityServices enabled andconfigure the LDAPserver before you installReporting and Analytics.

For information aboutinstalling Security


Chapter 11 Installing Teamcenter’s reporting and analytics

Table 11-1. TEM panels for Reporting and Analytics installation

TEM panel DescriptionServices, see theSecurity ServicesInstallation/Customizationguide.

Metadata Owner Type the user name forthe owner of Reportingand Analytics metadata.By default, this is thedatabase user namefor the Reporting andAnalytics database.

Web ApplicationServer

Specifies the vendor of theWeb application serveron which you deployReporting and Analytics.Options are WebSphere(for IBM WebSphere)and WebLogic (for BEAWebLogic).

This panel is displayed only if you do notselect Create WAR file.

Reporting and AnalyticsMetadata Settings

In the Teamcenter 4–tier URL box, type theURL 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 Teamcenteruser who administers Reporting andAnalytics.

Under Oracle Tablespace Names, type thenames of the Oracle tablespaces you created inCreate the Reporting and Analytics database.

This panel is displayed only if you selectCreate metadata.

Note

If you select Enable SSO in the Reporting and Analytics WARand Metadata Settings, TEM displays additional panels to gatherconfiguration information for Security Services. For information aboutthese panels, click Help.

5. Proceed through the remaining TEM panels and begin installing Reportingand Analytics.


Installing Teamcenter’s reporting and analytics

During installation, TEM prompts you for the location of the TCRA_2007.zipfile.

When installation is complete, close TEM.

Deploy Reporting and AnalyticsDeploy Reporting and Analytics as described in the Teamcenter’s reporting andanalytics 2007 guide in the Reporting and Analytics software distribution image.

Complete Reporting and Analytics installation1. Set the TC_RA_server_parameters preference using the rich client. Set thefollowing values:

Value DescriptionHost Specifies the host on which you deploy the

Reporting and Analytics WAR file.

Port Specifies the port used by the Reporting andAnalytics Web application.

Context Specifies the name of the Reporting andAnalytics WAR file

ServletName Specifies the name of the Reportingand Analytics servlet, for example,BuildNPlay/eQTIntegrationController.

This preference must be set to enable Reporting and Analytics to communicatewith Teamcenter.

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

2. Test connections to Reporting and Analytics applications. Log on to Reportingand 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 andAnalytics 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 Reportingand Analytics software distribution image.

Note

For information about using the Reporting and Analytics integration, see theReport 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-2Build the Teamcenter Web Tier Web application . . . . . . . . . . . . . . . . . . . 12-3Build additional Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Install Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Supporting files locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6Generate Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

Generate the Web application for Content Management . . . . . . . . . . 12-12Build a proxy WAR file for WebLogic . . . . . . . . . . . . . . . . . . . . . . . . 12-13Migrate legacy thin client URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

Sharing an application server instance for multiple four-tierenvironments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17

Installing rich client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . 12-19Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . 12-21Rich client distribution instance requirements . . . . . . . . . . . . . . . . . 12-22Install a rich client distribution instance . . . . . . . . . . . . . . . . . . . . . 12-28

Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31Deploy the distribution server instance . . . . . . . . . . . . . . . . . . . . . . 12-31Publish information for users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34Start and stop the rich client distribution server . . . . . . . . . . . . . . . 12-34Start the rich client distribution server . . . . . . . . . . . . . . . . . . . 12-34Stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . 12-35

Managing the rich client distribution server and instances . . . . . . . . . . . 12-35Change the distribution server contents . . . . . . . . . . . . . . . . . . . . . 12-35Add components to the distribution server instance . . . . . . . . . . . . . 12-35Run the distribution server as a service . . . . . . . . . . . . . . . . . . . . . . 12-37


Chapter

12 J2EE Web tier installation

J2EE Web tier installation begins with installing the Teamcenter Web ApplicationManager, a tool that builds thin client and rich client Web applications. With thistool, you can build thin client applications that distribute the Teamcenter thin clientto run in Web browsers on client hosts. The Web Application Manager also enablesyou to install a rich client distribution server and build rich client distributioninstances that install the four-tier rich client over a network onto client hosts.

Building Web applications with the Web Application Manager consists of thefollowing 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 andbehavior of Web tier solutions. Most Web tier solutions provide usable defaultvalues you can modify as needed after installation, but some parameters mustbe set during installation to enable the selected solutions.

6. Generate a deployable file.

Depending on the solutions you select, the Web Application Manager generateseither 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 ApplicationDeployment Guide.


Chapter 12 J2EE Web tier installation

J2EE Web tier prerequisitesBefore you install the J2EE Web tier, make sure you complete the following tasks:

• Install the Teamcenter server and server manager using TeamcenterEnvironment Manager as described in Teamcenter server installation.

• Install a supported third-party J2EE application server and the Java RuntimeEnvironment (JRE) on the Web tier host.1

• If you want to install Teamcenter online help for the Web tier, obtain theTeamcenter 8 documentation distribution image.

Note

Alternatively, you can install online help using Teamcenter EnvironmentManager 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 SecurityServices as described in Security Services installation.

Install the Web Application Manager1. Create a home directory for the Teamcenter Web tier, for example, /tcweb. Thisdirectory is referenced as WEB_ROOT.

2. Change to the WEB_ROOT directory.

3. Type the following command to extract Web Application Manager files to yourhost:

cat image-path/INSTALL_TCWEB.TZ | uncompress -c | tar xvf -

Replace image-path with the full path to the Teamcenter software distributionimage.

4. To launch the Web Application Manager, change to the WEB_ROOT directoryand enter the following command:

insweb

Installing thin client Web applicationsThe first thin client Web application you build is the Teamcenter Web Tierapplication, which provides essential thin client functionality. To this applicationyou can add additional thin client solutions, including custom solutions, accordingto 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 WebTier Web application.

After you build the Teamcenter Web Tier application, you can build additionalWeb applications to support Teamcenter features you use, as described in Buildadditional 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 Teamcentersoftware 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, TeamcenterWeb Tier.

b. In the Staging Location box, enter the path to the location where youwant the application files to reside. Typically, this is a directory under theWEB_ROOT directory. Web Application Manager creates the directory youspecify 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 softwaredistribution 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 theSolution 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 areincompatible with others. When you select a solution, the WebApplication Manager automatically selects prerequisite solutions anddisables incompatible solutions.

c. Optionally, select one or more of the following additional solutions:

Solution Description

Teamcenter – GM Overlay Provides the Teamcenter’s AutomotiveEdition–GM Overlay for the Teamcenterthin client.

Teamcenter – Online Help Provides Teamcenter online help for thethin client.

Note

If you select this solution, you mustadd the path to the Teamcenterdocumentation distribution image tothe list of Disk Locations for InstallImages as in step 4.2

Teamcenter ServicesWSDL/SOAP Support

Installs the Teamcenter service-orientedarchitecture (SOA), which provides theability to develop task-specific clients,utilities, and system integrations for theTeamcenter server. The Teamcenter SOAalso ships with WS-I compliant WSDL filesfor all operations, supporting open industrystandards.

For more information, see the ServicesGuide.

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 applicationin a cluster configuration.

7. Click OK.

The Web Application Manager displays the Modify Required ContextParameters 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 theTeamcenter Enterprise Tier Web application, you must supply values for thefollowing context parameters:

TreeCache Cluster Name3TreeCache ModeTreeCache 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 IDLogVolumeNameLogVolumeLocation

To set a context parameter, double-click the Value box for the given parameterand enter the new value. To view a description of any context parameter, clickthe 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 theProgress dialog box. When the installation is complete, click OK to close theProgress dialog box.

10. Click Exit to exit the Web Application Manager.

11. Locate the deployable file (tc.ear) generated during installation. This file is inthe deployment directory under the specified staging location.

Deploy the Web application as described in the Web Application DeploymentGuide.4

Build additional Web applications

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

Table 12-1. Additional Teamcenter Web applications

Feature Application Description

GlobalServices

Global Servicesapplication directoryapplication

Provides the application directoryfunctionality required by Global Services.For information about installing thisapplication, see Install Global Services.

3. For more information about configuring JBoss Cache TreeCache and setting TreeCache parameters, see www.jboss.org/jbosscache.The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jboss.org/jgroups.4. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choosethe appropriate procedure for the application server you use.





Table 12-1. Additional Teamcenter Web applications

Feature Application Description

Global ServicesEnterprise application

Provides essential Global Servicesfunctionality. You can addGlobal Servicesconnectors and other components tothis application. For information aboutinstalling this application, see InstallGlobal Services.

ContentManagement

Content ManagementBase

Provides the application for ContentManagement Base, an optionalTeamcenter solution. For informationabout installing this application seeGenerate the Web application for ContentManagement.

Content ManagementS1000D

Provides the application for ContentManagement S1000D, an optionalTeamcenter solution. For informationabout installing this application seeGenerate the Web application for ContentManagement.

Thin clientdeployed onWebLogicExpress

Proxy WAR file forWebLogic application

Provides support for WebLogic Expressas a front-end HTTP listener for the thinclient.

For information about installing thisapplication, see Build a proxy WAR filefor WebLogic.

Legacy thinclient support

Legacy URL supportapplication

Upgrades legacy thin client URLs toTeamcenter 8. If you are upgrading aprevious Teamcenter installation thatincludes the thin client, generate thelegacy URL management application.

For information about installing thisapplication, seeMigrate legacy thin clientURLs.

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 thatare provided by the connector’s back-end system or from some other source. Thelocation must be accessible to the Web Application Manager as you must enter thepath to the file in the Disk Locations for Install Images box. If you plan to includethe connector in your Web application, ensure the files identified for the connectorare available, and note the path to the file for use in Generate Web applications.



Note

As an alternative to having the directories containing dependent connectorfiles accessible to the Web Application Manager, you can copy the dependentfiles to an accessible location. However, if you do not keep the files in thepaths indicated in the ICD file, you must edit the ICD file for the connectorto eliminate or correct the path. For example, the Teamcenter Enterpriseconnector ICD has the following dependent file entry:

[COPYFILE]{[FROM]enterprise/mti.jar[TO]lib/enterprise

}

If you copy themti.jar file to a Web Application Manager accessible location,it must be in the enterprise directory under the location set in the DiskLocation to Add box. Alternatively, you can edit the ICD file to removeenterprise/ from the [FROM] section.

• Teamcenter Enterprise connector

This solution requires theMTI_ROOT\evista\java\classes directory location.This directory contains the mti.jar file and mtiems.jar files required forconnecting to Teamcenter Enterprise. The mtiems.jar file contains the importand 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.jarfile is not available in this directory. However, after you install theTeamcenter 8 Global Services – Application Directory solution, theWEB_ROOT\application-directory-staging-directory\webapp_root\lib\enterprisedirectory for that solution contains a version of this file containingonly a manifest file.

The easiest approach is to copy the required JAR files (mti.jar andmtiems.jarto WEB_ROOT\application-directory-staging-directory\ webapp_root\lib\ enterprise directory and add this location to the disk locations for installimages in the Web Application Manager.

• Teamcenter Engineering v9 connector

If you are installing the Teamcenter Engineering V9 connector, the TeamcenterEngineering Portal client directory must be available to the host where theconnector is being installed. This directory contains resources that the connectorrequires 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, itrequires access to external dependent JAR les. These files are located inthePortal directory for the Teamcenter Engineering server instance and mustbe available to the Web Application Manager during the install process. Thisdirectory is a first-level subdirectory under the Teamcenter Engineering serverbase directory. The files used from this directory are:

– portal.jar– portal_patch.jar– fscproxy.jar– icctstubs.jar– tcgatewaystubs.jar– xmldto.jar– xercesImpl.jar– client_specic.properties– portal.properties– portal_locale.properties– portal_user.properties– site_specic.properties

The Teamcenter Engineering 2005/2007 connector can access multipleEngineering 2005 or 2007 instances; however, as with all Global Servicesconnectors, it requires that all instances be the same version.

Note

The Teamcenter Engineering 2005/2007 connector and TeamcenterEngineering V9 connector can co-exist with each other or any other GlobalServices connector.

• Teamcenter rich client connector

If you are installing the Teamcenter 2007 rich client connector, the connectorrequires access to dependent external JAR les. These files are located in theportal\plugins directory for the Teamcenter server installation and must beavailable to the Web Application Manager during the install process. The filesused 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 inthe 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 filefrom Oracle’s Web site.

• SAP connector

This solution requires the jco.jar file location. This file is included in theJCO package that you must download (includes installation instructionsand documentation) from http://service.sap.com/connectors. This Web siterequires a valid SAP Services Marketplace login account. If you do nothave a valid account, visit http://service.sap.com to register. Unzip theJCO package file that you downloaded and extract the jCO.jar file andsupporting library files it contains. If you are installing on Windows, extractthe librfc32.dll and jRFC12.dll files. If you are installing on UNIX,extract the librfccm.so and libjRFC12.so files. After you create theGlobal Services enterprise application, copy the files you extracted to theWEB_ROOT/application-directory-staging-directory/webapp_root/lib directory.

Generate Web applications

Note

Some solutions require other solutions, and some solutions are incompatiblewith others. When you select a solution, the Web Application Managerautomatically selects prerequisite solutions and disables incompatiblesolutions. For example, Teamcenter – Server Adapter and Teamcenter 8Global Services Framework – Enterprise Application are incompatiblesolutions.

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 distributionimage, 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:


http://service.sap.com/connectors

http://service.sap.com


Note

If you are installing the Teamcenter gateway for Oracle Manufacturing,you must repeat this procedure selecting the Teamcenter 8 GlobalServices Framework – Gateway for Oracle Manufacturing ApplicationDirectory and Teamcenter 8 Global Services Framework – Teamcenter8 Rich Client OSGi Plug-in solutions in step g.

If you are installing the Teamcenter 8 Rich Client Connector, youmust repeat this procedure selecting the Teamcenter 8 Global ServicesFramework – Teamcenter 8 Rich Client Plug-in solutions in step g.

a. In the Name box, type a name for the application, for example, ApplicationDirectory.

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 theWeb_tierdirectory on the Teamcenter software distribution image.

d. Click Advanced Web Application Options.

e. In the Advanced Web Application Options dialog box, clear theAutomatically Build Deployable File check box.

f. Click Solutions.

g. In the Select Solutions dialog box, clear all preselected solutions and selectthe Teamcenter 8 Global Services Framework – Application Directory CoreLibrary solution.

Note

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

5. Click OK to begin installing the solution.

The Web Application Manager displays the installation status in the Progressdialog box. When the installation is complete, click OK to close the Progressdialog 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, GlobalServices Enterprise Application.


c. Click Advanced Web Application Options. Type a name for the deployablefile in the Deployable File Name box (alphanumeric characters only)..



If you require the deployable file to be a distributable file, select theDistributable 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 theSolution 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 selectthe Teamcenter 8 Global Services Framework – Enterprise ApplicationCore Library solution.

9. If you selected a connector that requires supporting files (see Supporting fileslocations), 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.

ApplicationInstanceSSOAppIDLogFileLocationTcGSBOSJNDI

TcGSJDBCJNDITcGSMessageServerJNDITcGSNotifierReactorJNDITcGSDORJNDI


For more information about Global Services context parameters, see GlobalServices context parameters.



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 duringinstallation. This file is in the deployment directory under the specified staginglocation.


Generate the Web application for Content Management

Use the Web Application Manager to generate the Web application for ContentManagement, 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, ContentManagement 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 andselect only the Teamcenter Content Management S1000D System orTeamcenter Content Management System.

Note

Select the Teamcenter Content Management S1000D System optiononly if you have already installed the Content Management SystemS1000D feature.

4. Click OK to begin installing the solution.


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

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



Tip

It is recommended that you use the same name you entered to name theapplication in step 3.

6. Click OK.







10. Locate the deployable file generated during installation (by the name youspecified in step 5). This file is in the directory under the specified staginglocation.

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 generatea proxy WAR file:


2. Click Add to begin creating the Web application.

Web Application Manager displays the Add Web Application dialog box.

3. Create the proxy WAR file Web application:

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


c. Optionally, type a description of the application in Description box.

d. Click Advanced Web Application Options. Type a name for the deployablefile in the Deployable File Name box (alphanumeric characters only).

e. Make sure the Disk Locations for Install Images box includes the path totheWeb_tier directory on the Teamcenter software distribution image.



f. Click Solutions. In the Select Solutions dialog box, clear all preselectedsolutions and select only the Teamcenter – Web Tier Proxy solution.7

Note


4. Click OK.


5. Enter values for the following required context parameters:


WebLogicHost Host name of the WebLogic server runningthe Web tier. The proxy forwards the requestto this server.

WebLogicPort Port number of the WebLogic server instancerunning the Web tier. The proxy forwards therequest to this server.


6. Click OK to begin building the Web application. The Web Application Managerdisplays the status of the installation in the Progress dialog box. When theinstallation 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 thedeployment directory under the specified staging location.


Migrate legacy thin client URLs

If you migrate Web tier applications to Teamcenter 8 from Teamcenter’s engineeringprocess management 2005 or earlier, you must update the link your site uses toaccess 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 Webtier 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 Webapplication.8. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choosethe appropriate procedure for the application server you use.



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

Note

• Install the Teamcenter – Legacy URL (cgi-bin) Support thin clientsolution in a separate Web application. This solution is not compatiblewith other Teamcenter thin client solutions.

• Deploy the application so that it intercepts legacy requests and redirectsthem to the new URL location.

For example, if the original requests are going to port 9090, deploy thecgi-bin.war application on port 9090. If the original requests are going toserver1, deploy the cgi-bin.war application on server1.

When the cgi-bin.war file is deployed, users who access a legacy /cgi-bin/imanURL 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/w8PJDvpRxBRxDDNew URL: http://host:port/tc/webclient/w8PJDvpRxBRxDDYou will be redirected to the new URL automatically in nn seconds or you mayclick the above link manually. If possible, update your links to reflectthe new location.This notification message will be displayed each time an old URL is requestedprior to month-day-year. After this time, requested resources that havemoved will be automatically redirected to the new URL without notification.

When you create cgi-bin.war using Web Application Manager, you control aspectsof the application:

• Whether the application displays the Siemens PLM Software URL messagebefore redirecting users to the new URL. When you choose not to display theSiemens PLM Software URL message, the application redirects users to the newURL but displays no informative message.

• The period of time (in seconds) the application displays the Siemens PLMSoftware 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 theinformative message.

• The protocol or the port, server, and domain portion of the requested, legacyURL. The application changes the Siemens PLM Software-provided portion ofthe URL and passes through the site-provided portion of the legacy URL.


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

3. Create the legacy URL support application Web application:

a. In the Name box, type the name of this application, for example, LegacyURL 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 totheWeb_tier directory on the Teamcenter software distribution image.

e. Click Solutions. In the Select Solutions dialog box, deselect all preselectedsolutions and select only the Teamcenter – Legacy URL (cgi-bin) Supportsolution.9

Note


4. Click OK.


5. Enter values for the following required context parameters:

Parameter DescriptionTcEngLocale Specifies a locale for messages displayed to

the user. This locale must match the localespecified for the Teamcenter Enterprise TierWeb application.

expiryDateOfResourceMovedNotification

Specifies the date the URL message expires.This parameter must contain a value.Enter a value in month-day-year format(mm-dd-yyyy), for example, 12–10–2007, orenter one of the following keywords:

NEVERSpecifies that the URL message neverexpires.

NOWSpecifies that no message or notificationregarding the resource move is displayedto the user. The user is immediatelyredirected 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 Webapplication.



The Web Application Manager displays the status of the installation in theProgress dialog box. When the installation is complete, click OK to close theProgress dialog box.


8. Locate the deployable file (cgi-bin.war) generated during installation. This fileis in the deployment directory under the specified staging location.


Note

After installation, you can optionally modify the following context parametersfor legacy URL support:

requestRedirectedToreplacementFor CGIBIN_IMANredirectionWaitTime

For information about these context parameters, see Web tier contextparameters.

Sharing an application server instance for multiple four-tierenvironments

Teamcenter supports deploying more than one instance of the same TeamcenterWeb tier application (EAR file) into one application server instance. Multiple EARfiles can be configured to run as discrete applications, each with a unique entrypoint. This allows you to connect each application to a different enterprise tierwithout the need to manage multiple application server instances. The followingexample shows a possible scenario with three Web applications (EAR files) deployedin a single application server instance.

Clienttier Web tier Enterprise tier

Resourcetier

Clients Single application serverinstance

Server managers Databases

ClientA ¬® http://host:port/tc01 ¬® svrmgr11 ¬® DB1

¬® http://host:port/tc02 ¬® svrmgr2 ¬® DB2ClientB ¬® 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.

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



For information about installing a server manager, see Installing the servermanager.

2. Create Web applications as described in Build the Teamcenter Web Tier Webapplication. Assign each application a unique name.

3. Set the following Web tier context parameters to unique values for each Webapplication.

Table 12-2. Context parameters for shared deployment

Context parameter Description

DEPLOYABLE-FILE-NAME Name of the deployable file you are creatingfor the Web tier application.

Enterprise ApplicationRegistration ID

Identifier for the Web application. This IDis used to register the application’s EJB andJ2C connector. If you want to deploy multipleTeamcenter Web tier applications in a singleapplication server instance, each applicationmust be assigned a unique ID.

Enterprise ApplicationLookup ID

Specifies the ID by which the Teamcenterpresentation tier accesses the applicationidentified by the Enterprise ApplicationRegistration ID parameter. If you deploy yourEAR file with other EAR files in the sameapplication server instance, these two IDsshould be set to the same value for a givenapplication.

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 asyour Web application server, you must deploy each EAR file in a separateapplication server instance.

Installing rich client Web applicationsPreparing the Teamcenter Web tier to distribute the four-tier rich client to clienthosts over a network requires the following tasks:

1. Install a rich client distribution server.

The rich client distribution server manages the connection between rich clientdistribution server instances and the Over-the-Web Installer. The Over-the-WebInstaller contacts the distribution server for the rich client files to downloadto 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 pagesthat 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 EnvironmentManager (TEM). Over-the-Web installation is supported only for the four-tierrich 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 ApplicationManager 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 softwaredistribution image and click OK.

Note

Ensure that the icd folder is in the Source box of the Copy ICD Filesdialog box.

The Web Application Manager displays a Progress dialog box and copies andloads the ICD files.

4. To ensure that ICD files are copied, check the Progress dialog box. When ICDfiles are copied, a list of ICD files follows the Copying ICD files... notice. Ifno files are listed, Web Application Manager did not find files to copy in thedirectory you supplied.

If the copy was not successful, repeat steps 2 and 3, ensuring that you includethe icd directory in the path. Not including the icd directory is the mostcommon reason ICD files are not copied.

5. Click OK in the Progress 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, TeamcenterOTW Distribution Server.

8. In the Staging Location box, type the path to the location where you want thedistribution server software and administration files to reside.

Typically, you would install the distribution server software in a directory undertheWeb_tier directory, the directory in which you installed the Web ApplicationManager on your hard drive.

Note

• This directory must be empty. The Web Application Manager createsthe 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 distributionserver.

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 thinclient over-the-Web software distribution image and click OK.

The Web Application Manager displays the Add Web Application dialog box withthe 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 SelectedSolutions box.

Note

If Distribution Server is not in the Solution Type list, the requiredICD files were not copied correctly. To copy the ICD files, repeat steps2 through 4.

13. Click OK.


14. Type values for the following context parameters:



Parameter ValueRMI 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 typicallyavailable.

Note

Record the RMI port number for future use. It isrequired when creating the distribution serverinstance.

Remote Object Port Specifies the port on which the distribution serverlistens for over-the-Web installers. The default value,0, allows the distribution server to pick an availableport at runtime. If you want to use a specific port,enter a nonzero port number. This is helpful if, forexample, a firewall exists between distribution serverand over-the-Web installation clients.

File Transfer Port Specifies the port the distribution server uses to transferfiles to client hosts. The default value, 0, allows thedistribution server to pick an available port at runtime.If you want to use a specific port, enter a nonzeroport number. This is helpful if, for example, a firewallexists between the distribution server and over-the-Webinstallation clients.

15. Click OK.

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

16. When the Progress dialog box indicates that installation is complete, click OK.

The Web Application Manager displays the Teamcenter Web ApplicationManager dialog box with the distribution server software you installed listed asan application in the Web Applications box.

17. Either click Exit to exit the Web Application Manager or click Add to begininstalling the rich client distribution server instance.

Install rich client distribution instances

The Teamcenter rich client instance you install works only in a deployment of thefour-tier architecture.

For each unique rich client configuration, you must create a distribution serverinstance.



Rich client distribution instance requirements

Before you build a rich client distribution instance, ensure that the followingsoftware 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 isinstalled and configured.

For information, see Security Services installation and the Security ServicesInstallation/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 forall supported Windows, UNIX, and Linux platforms. The Web ApplicationManager 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 valueswhen building the rich client distribution instance.

Note

Required parameters must have values specified. If a required parameterhas no significance for your deployment (for example, a UNIX location in anenvironment of all Windows systems), accept the default value.

Table 12-3. Rich client required parameter and table values

Parameter DescriptionRMI Port Port number used by the rich client distribution server.

This value was determined when the distribution serverwas installed. The default is 12099.

WindowsLocation Location on the client host where you want theOver-the-Web Installer to download rich client files onMicrosoft Windows systems by default.

The drive must exist on the client hosts prior torich client installation, and users must have writepermission to it. For example, if the installation locationis F:\Teamcenter8\rich_client, every Windowsclient host must have an F drive, and users must havepermissions to create Teamcenter8\rich_client.




Parameter DescriptionUnixLocation Location on the client host where you want the

Over-the-Web Installer to download rich client files onUNIX systems by default.

The mount must exist on the client hosts prior to richclient installation, and users must have write permissionto it.

WebBrowserUnixLocation Location of a Web browser on UNIX systems. Thislocation must be available for UNIX client hosts.

RichClientHelpWebServer URL specifying the name of the host and the port wherethe Web tier or presentation tier application files aredeployed in an application server. This parameter workstogether with the RichClientHelpLocation parameter todetermine how rich client users access help:

• To enable accessing help over the Web, set theparameter value to http://host-name:port. Donot supply the remainder of the path to thehelp files (that information is supplied in theRichClientHelpLocation parameter).

• To enable accessing help using direct file access, setthis parameter to file://.

RichClientHelpLocation Path to the Teamcenter Help Library files. This parameterworks together with the RichClientHelpWebServerparameter to determine how rich client users access help:

• To enable accessing help using direct file access, setthe value of this parameter to the full path to the helpfiles. You must supply paths for Windows, UNIX, andLinux systems.

• To enable accessing help over the Web, enter the fullpath to the installed help library index.htm file.

HTTPUseGZip Indicates whether the rich client prefers responsesfrom the J2EE server in a compressed (gzipped)form. Compressing responses reduces the bandwidthrequirement significantly, and should be considered,especially in lower bandwidth network environment.

When set to true, the server may send responses withoutcompression depending on the server configuration.

When set to false, the server never compresses responsesfor this rich client.





ParentFSCAddressTable List of addresses (host name and port) of the FMS fileserver caches (FSC) to act as the parents of the installedFMS file client cache.

For information on the FMS file client cache and FMS fileserver cache, see Installing File Management System.

HTTPServerTable List of Web tier application servers; the first server in thelist is the default server for logon. Requires the followinginformation for each server:

URIURL of the Web tier SOAP endpoint. The valuedepends on where the Web tier application isdeployed. Typically it has the form:

http://host-name:port/tc/webclient

NameDisplay name of the URL for the rich client graphicaluser interface.

SSOAppIDProvides the Teamcenter application ID and sets theTC_SSO_APP_ID environment variable for SecurityServices.

The value you provide in this context parameter isused only when Security Services is enabled andeither multiple Teamcenter sites are served by asingle identity provider or the Security Servicesservice is configured to use an ID other than TC.

When the multiple sites have different sets of usersauthorized to use the application for each installation,or different identifications in each installation, thisvalue identifies which installation is authenticated.

Depending on the solutions you include in your rich client distribution instance, youmay need to provide values for the additional parameters shown in tables 12-3through 12-8.



Table 12-4. Rich client optional parameter values


TeamcenterSSOService Complete URL of the Security Services IdentityService Web application. This information is requiredonly when you configure the rich client to log on usingthe optional Security Services.

This URL is determined when Security Services isinstalled and configured. You must provide the sameURL used to configure Security Services on the Webtier.

TeamcenterSSOlogonURL Complete URL of the Security Services logon ServiceWeb application. This information is required onlywhen you configure the rich client to log on using theoptional Security Services.

This URL is determined when Security Services isinstalled and configured. You must provide the sameURL used to configure Security Services on the Webtier.

TeamcenterSSOAppID Application ID assigned to this instance of Teamcenterin the Security Services application registry. Thisinformation is required only when you configurethe rich client to log on using the optional SecurityServices and when multiple Teamcenter sites areeither served by a single identity provider or theSecurity Services service is configured to use an IDother than TC.

This ID is determined when Security Services isinstalled and configured. You must provide the sameURL used to configure Security Services on the Webtier.

When the multiple sites have different sets of usersauthorized to use the Teamcenter application foreach installation, or different identifications in eachinstallation, this value identifies which installation isauthenticated.

FMSProxyHTTPHost Name of HTTP proxy server host for File ManagementSystem (FMS) communication. If you do not specify ahost, the rich client does not communicate with FMSusing an HTTP proxy server.

To configure an HTTP proxy server, you must alsospecify a value for the FMSProxyHTTPPort parameter.



Table 12-4. Rich client optional parameter values


FMSProxyHTTPPort Number of port for HTTP proxy server for FileManagement System (FMS) communication. If youdo not specify a port number, the rich client does notcommunicate with FMS using an HTTP proxy server.

To configure an HTTP proxy server, you mustalso specify a value for the FMSProxyHTTPHostparameter.

FMSProxyHTTPSHost Name of HTTPS proxy server host for FileManagement System (FMS) communication. Ifyou do not specify a host, the rich client does notcommunicate with FMS using an HTTPS proxyserver.

To configure an HTTPS proxy server, you mustalso specify a value for the FMSProxyHTTPSPortparameter.

FMSProxyHTTPSPort Number of port for HTTPS proxy server for FileManagement System (FMS) communication. If youdo not specify a port number, the rich client doesnot communicate with FMS using an HTTPS proxyserver.

To configure an HTTPS proxy server, you mustalso specify a value for the FMSProxyHTTPSHostparameter.

Table 12-5. Teamcenter’s lifecycle visualization (embedded viewer) parameter andtable values


EmbVisLicenseLevel License level for the embedded viewer: Mockup,Professional, Standard, or Base.

The Base license is available for all users of the richclient. The other license levels are purchased separately.

EmbVisUnixLocation Location on a UNIX system of the installed embeddedviewer Web application to be configured with this richclient.

EmbVisWindowsLocation Location on a Windows system of the installed embeddedviewer Web application to be configured with this richclient.



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


TcVisWindowsLocation Full path to the stand-alone application viewer installationlocation on Windows client hosts.

Users install the stand-alone application viewer on clienthosts using the Teamcenter’s lifecycle visualizationinstallation program. This location must be the same forall Windows clients.

TcVisUnixLocation Full path to the stand-alone application viewer installationlocation on UNIX client hosts.

Users install the stand-alone application viewer on clienthosts using the Teamcenter’s lifecycle visualizationinstallation program. This location must be the same forall UNIX clients.

Table 12-7. Teamcenter Integration for NX parameter and table values


NXWindowsLocation Full path to the NX installation location on Windows clienthosts.

Users install the NX application on client hosts using the NXinstallation program. This location must be the same for allWindows 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 NXinstallation program. This location must be the same for allUNIX clients installing this instance.

NXVersion Version of NX installed on client hosts.

Users install the Teamcenter Integration for NX application onclient hosts using the NX installation program. This versionmust be the same for all clients installing this instance. Thedefault 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 webserver(s). The entries correspond to the associated TeamcenterURI sequences. Leave the field blank if the Teamcenter URIdoes not have a corresponding Content Management WebServer URL.



Install a rich client distribution instance

Install the rich client instance on the same host and in the same directory as thedistribution server.

1. Start the Web Application Manager:




2. Enter the path to the icd directory in the rich client over-the-Web distributionimage and click OK.

The Web Application Manager displays a Progress dialog box and copies theICD files.

3. When copying is complete, click OK.


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 toinstall the rich client image files for downloading to clients.

Typically, you would install the rich client distribution instance files in adirectory under theWeb_tier directory, the directory in which you installed theWeb Application Manager on your hard drive.

Note

• This directory must be empty. The Web Application Manager createsthe directory if it does not exist.

• Note the staging location path of this distribution server instancefor 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 Imagesbox.

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



• Enter the path to the icd directory in the rich client over-the-Web installationimage.

• Enter the paths to the Teamcenter’s lifecycle visualization installationimages for each operating system.

Note

For each instance, the Over-the-Web Installer requires access to theinstallation images files for all operating systems.

10. Click OK.

Web Application Manager displays the Add Web Application dialog box with thepaths 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 Installerand Rich Client 4–Tier solutions. These solutions are required.

12. If you want to include additional solutions in the distribution instance, clickSolutions 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 dialogbox, 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 applicationsyou are installing with the rich client instance. For descriptions, seetables 12-5 through 12-7.

• The required parameters must have values specified. If a requiredparameter has no significance for your deployment (for example, aUNIX location in an environment of all Windows systems), retainthe default value.

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

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



Table Description

ParentFSCAddressTable Type a list of addresses (host name and port) of theFMS file server caches (FSC) to act as the parentsof the installed FMS file client cache.

For information on the FMS file client cacheand FMS file server cache, see Installing FileManagement System.

HTTPServerTable Type a list of Web tier application servers; the firstserver in the list is the default server for logon.Requires the following information for each server:

URIURL of the Web-tier SOAP endpoint. The valuedepends on where the Web tier application isdeployed. Typically it has the form:

http://host-name:port/tc/webclient

NameDisplay name of the URL for the rich clientgraphical user interface.

16. When you complete each table, click OK.

When you complete setting values for the last table, the Web ApplicationManager displays a Progress dialog box and performs the following tasks:

• Extracts the rich client image files into the webapp_root directory underthe 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 clientimage files, including a list of the files and a version for each file. TheOver-the-Web Installer consults the manifest file to determine which filesto download.

17. When the Progress dialog box indicates that installation is complete, click OK.


18. If you want to configure the optional Security Services, ensure that the rich clientdistribution instance is selected in theWeb 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.



Repeat this procedure for each additional rich client distribution instance you wantto 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 HTTPServer. You can also use an application server, such as IBM WebSphere, but it isnot 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/otwwebdirectory 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 installationcompletes 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-WebInstaller.

• launcherror.html file



Contains the English version of the HTML page displayed to the user when theOver-the-Web Installer cannot install the rich client due to one of the followingproblems:

– The connection to the Web is not available or the user has not providedpermissions to install.

– The required Java Plug-in is not available and cannot be installedautomatically.

– 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 forinstalling 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, andT_Chinese). The subdirectories contain localized versions of the installing.htmland error.html files. To use a localized version of the installation, deploy thelocalized installing.html and error.html files rather than the English versions.

Note

Before deploying a localized installing.html file, you must edit it asfollows:

1. Using a text editor, find the following two lines and in each replacechange_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_serverwith 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 quotationmarks.

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 aunique directory in the Web server documentation root for each instance and copyall the files in the webapp_root/otwweb directory there. For detailed deploymentinformation, see the documentation for the Web server. The following examples usethe name of the instance for the Web component directory name:


Web server Deployment

Apache HTTPServer

1. In the conf configuration file, find the HTTP documentroot directory:

DocumentRoot “document-root-path”

2. Create the instance-name directory under the HTTPdocument root directory.

3. Copy the rich client Web file to the instance-namedirectory.

4. Publish the following URL:

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

Apache Tomcat 1. In the server.xml configuration file, find the HTTPdocument base directory. For example:





2. Create the instance-name directory under the HTTPdocument base directory.

3. Copy the rich client Web components to the instance-namedirectory.


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

Sun ONE 1. In the config configuration file, find the HTTP documentroot directory. For example:

<VARS docroot="document-root-path">

2. Create the instance-name directory under the HTTPdocument base directory.

3. Copy the rich client Web components to the instance-namedirectory.


Web server Deployment

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

2. Create the instance-name directory under the HTTPdocument 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 followinginformation:

• URL where the Web components are located.

• The location in which the rich client will be installed on user workstations. Usersmust have write permissions for this location.

• For rich client instances that include support for Teamcenter’s lifecyclevisualization or NX, the locations in which users must install Teamcenter’slifecycle 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 followingsections.

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 andadministration 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 followingmessage:

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-Ckeys on the distribution server console. The distribution server stops, and cleanupprogress is reported.

To stop a rich client distribution server from a remote computer, or if you changedthe port number the RMI registry is running on, you must have file access tothe stop_server program file and the dist_server.jar file in the webapp_rootsubdirectory of the distribution server staging location. To stop the distributionserver, enter the following command:

stop_server host-name:port-number

Replace host-name with the name of the computer where the distribution server isrunning. Replace port-number with the port number.

The stop_server program prints the results of the remote shutdown. If theresults include Java exceptions, errors occurred. Usually exceptions occur when nodistribution 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 andconfigured, you can change the distribution server contents, add components to adistribution server instance, and patch components in a distribution server instance.

Note

To allow automatic updating of a rich client when users start a Teamcentersession, 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 staginglocation 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:






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 distributionimage and click OK.

The Web Application Manager displays a Progress dialog box and copies theICD files.

4. When copying is complete, click OK.


5. In theWeb Applications list, select the distribution server instance you want toadd 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 arelisted in the Disk Locations for Install Images box.

For example, if you intend to add the embedded viewer to the rich client, enterthe paths to the Teamcenter’s lifecycle visualization installation images for eachoperating system.

Note

For each instance, the Over-the-Web Installer requires access to theinstallation 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 ApplicationManager 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 applicationsyou are installing with the rich client instance. For descriptions, seetables 12-5 through 12-7.

• The required parameters must have values specified. If a requiredparameter has no significance for your deployment (for example, aUNIX location in an environment of all Windows systems), retainthe default value.

The Web Application Manager begins installation of the solutions and displays aProgress dialog box.

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, clickModify Context Parameters.

The Web Application Manager displays the Modify Context Parameters dialogbox.

Note

If you change a context parameter, the Over-the-Web Installer cannotautomatically 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 embeddedviewer 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 uninstallthe 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 andmaintenance

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 andconfigurations

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


Chapter

13 Managing installations andconfigurations

A Teamcenter configuration is a collection of features associated with one Teamcenterdata directory. The collection of configurations that share the same Teamcenterapplication root directory is a Teamcenter installation.

When you installed Teamcenter executables using Teamcenter EnvironmentManager from the software distribution image, you created the first configuration.

You can create a new Teamcenter configuration or modify features in your existingTeamcenter configuration using Teamcenter Environment Manager.

Create a configuration1. Start Teamcenter Environment Manager:

a. Access the install directory in the Teamcenter application root directory forthe 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 optionand click Next.

Teamcenter Environment Manager displays the Configuration panel.

3. Enter a description of and unique ID for the configuration you are creating andclick 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 aninstallation. Teamcenter Environment Manager displays additional panelsdepending on the components you are including in the configuration.

5. When Teamcenter Environment Manager displays the Confirm Selectionspanel, click Next to begin installation.


Chapter 13 Managing installations and configurations

Modify a configurationAdd Teamcenter features to an existing configuration, or remove them from aconfiguration:

1. From the install directory of the Teamcenter application root directory of theconfiguration, start the tem.sh program.

2. From the Select Configuration panel, choose the Perform maintenance on anexisting configuration option.

3. From the list of configurations, select the configuration you want to modify andclick 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. Thecomponents 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, TeamcenterEnvironment Manager displays additional panels.

6. When Teamcenter Environment Manager displays the Confirm Selectionspanel, click Next to begin installation.

Add an existing Teamcenter databaseYou can add a Teamcenter database to an installation by creating a configurationthat references an existing Teamcenter data directory and its configured database. Adata directory is associated with one (and only one) database instance.

Because you are using a database already configured for Teamcenter, you need notinstall 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 theconfiguration, start the tem.sh program.

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 theconfiguration you are creating.

4. In the Select Components panel, select the Teamcenter Foundation componentonly.

5. In the Configure Data panel, select Connect to an existing data directory andenter the full path to the existing data directory in the Data Directory Locationbox.


Managing installations and configurations

6. In the Confirm Selections panel, review your selections and click Next to addthe database.

Add or configure a databaseYou can simultaneously configure a Teamcenter database and add it to aninstallation by creating a new configuration. Because you are configuring a database,you must also install and configure File Management System and Teamcenter FileServices 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 forTeamcenter or a multipurpose instance to be configured in this procedure.

For information about installing a database server and database instances, see partII, Database server installation.

1. In the install directory of the Teamcenter application root directory of theconfiguration, start the tem.sh program.

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

4. In the Select Components panel, select the following components:

Teamcenter FoundationFile Management SystemTeamcenter File Services

5. In the Configure Data panel, select Create new data directory and fill in theData 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 Teamcentervolume 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.

12. When Teamcenter Environment Manager displays the Confirm Selectionspanel, click Next to add the database.



Configure multiple databases for a four-tier rich clientConfigure 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 aTeamcenter corporate server, including a server manager, for each database anddeploy a Web tier EAR file for each server manager (figure 13-1). For example, toconfigure rich client access to two databases, configure:

• In the enterprise tier, install two corporate servers with server managers andconnect each server to a different database.

• In the Web tier, deploy two Web tier files, each connecting to one of the servermanagers.



TcData1

TC Server n

TreeCache= ClusterTcData1

TcData2

Four-Tier Rich Client

TcHost1 TcHost2

FMS FSC_TcHost2

<fmsworld> <multisiteimport siteid="400783129"> <defaultfscimport fscid="FSC_TcHost2 fscaddress="TcHost2:4444" priority="0"/> </multisiteimport>

tc.ear

Server Manager



tc.ear

FSC Parent= TcHost1:4444

http://appserver:7001/tc/webclient http://appserver:7002/tc/webclient

TC Server n

Server Manager


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



Note

For the complete procedure, see Teamcenter server installation.

1. Using Teamcenter Environment Manager, install Teamcenter in a corporateserver 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 TreeCachecluster name of ClusterTcData1.

2. Using Teamcenter Environment Manager, install Teamcenter in a corporateserver 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 TreeCachecluster name of ClusterTcData2.

3. On TcHost1, edit the FMS master file to make FMS aware of the FSC onTcHost2:

a. Go to the fms directory in the Teamcenter application root directory.

b. Open the fmsmaster_FSC_service-id.xml file and find the following lines:

<fmsworld><multisiteimport siteid="othersite"><fscimport fscid="otherfsc" fscaddress="host:4444"><volumeimport volumeid="othervol" /></fscimport>

</multisiteimport>

c. Edit the lines, adding the bold text and deleting the indicated text:

Original:<fmsworld><multisiteimport siteid="othersite"><defaultfscimport fscid="otherfsc" fscaddress="host:4444" priority=”0”/><volumeimport volumeid="othervol" /></fscimport>

</multisiteimport>

Revised:

<fmsworld><multisiteimport siteid="othersite"><defaultfscimport fscid="otherfsc" fscaddress="host:4444" priority=”0”/>

</multisiteimport>

d. In the revised section:

• Replace the value for the siteid parameter with the FMS enterpriseID of the FSC on TcHost2. This value is in the FMS master file onTcHost2 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 andport number of host 2. This value is in the FMS master file on TcHost2in 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 managerof TcHost1 by specifying the same values for the TreeCache cluster name andTreeCache mode.1

For example:

TcHost1 server manager Web tier application

TreeCache cluster name:ClusterTcData1


TreeCache mode: TCP TreeCache mode: TCP

2. Generate the Web tier EAR file, configuring it to connect to the server managerof TcHost 2 by specifying identical values for the TreeCache cluster name andTreeCache mode.

For example:

TcHost 2 server manager Web tier application



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






Users who install this rich client instance, can choose from two databases, TcData1and 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 portnumber 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 deployedWeb 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-3Update thin client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3Create a thin client localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4Convert the thin client user interface for Hebrew . . . . . . . . . . . . . . . . . . . 14-5

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


Chapter

14 Localizing Teamcenter

Configure and deploy localized versions of Teamcenter.

Configure rich client language displayBy default, the rich client displays in the language specified by your operatingsystem settings.

If you change your operating system locale, to ensure the rich client interface isupdated 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 thanthe operating system, you can override the client workstation’s locale setting byperforming 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:

-nllanguage-identifier

Replace language-identifier with the appropriate code for your intended locale:

Language Code

Chinese (Simplified) cn

Chinese (Traditional) twEnglish enFrench frGerman deItalian itJapanese jpKorean krRussian ruSpanish es


Chapter 14 Localizing Teamcenter

For example, if your client workstation’s locale is set to German, you can set therich client user interface to display in English by adding the following line tothe teamcenter.ini file:

-nlen

4. Save the changes to the teamcenter.ini file.

5. Change to your user home directory ($HOME) and delete the Teamcenterdirectory.

6. Restart the rich client.

Environment settings for non-English localesFor non-English locales on UNIX systems, you must specify the system locale bysetting the LANG and LC_ALL environment variables using the Common DesktopEnvironment (CDE). These two variables must be identical to function properly.

Set the LANG and LC_ALL environment variables to the values shown in table14-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

Hewlett-Packard HP-UX

Sun Solaris

ISO8859–1

ISO8859–1

ISO8859–1

fr_FR or fr_FR.ISO8859–1

fr_FR.iso8859

fr or fr_FR or fr_FR.ISO8859–1

German IBM AIX


Sun Solaris

ISO8859–1

ISO8859–1

ISO8859–1

de_DE or de_DE.ISO8859–1

de_DE.iso88591

de or de_DE orde_DE.ISO8859–1

Hebrew IBM AIX


Sun Solaris

ISO8859–8

ISO8859–8

ISO8859–8

iw_IL or iw_IL.ISO8859–8

iw_IL.iso88598

he or he_IL

Italian IBM AIX


Sun Solaris

ISO8859–1

ISO8859–1

ISO8859–1

it_IT or it_IT.ISO8859–1

it_IT.iso88591

it or it_IT or it_IT.ISO8859–1

Russian IBM AIX


Sun Solaris

ISO8859–5

ISO8859–5

ISO8859–5

ru_RU or ru_RU.ISO8859–5

ru_RU.iso88595

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


Sun Solaris

ISO8859–1

ISO8859–1

ISO8859–1

es_ES or es_ES.ISO8859–1

es_ES.iso88591

es or es_ES or es_ES.ISO8859–1

Japanese IBM AIX

IBM AIX



Sun Solaris

Sun Solaris

JEUC

SJIS

JEUC

SJIS

JEUC

SJIS

ja_JP

Ja_JP

ja_JP.eucJP

ja_JP.SJIS

ja or japanese

ja_JP.PCK

Korean IBM AIX


Sun Solaris

KS C

KS C

KS C

ko_KR

ko_KR.eucKR

ko or korean

SimplifiedChinese

IBM AIX


Sun Solaris

GB2312-80

GB2312-80

GB2312-80

zh_CN

zh_CN.hp15CN

zh

TraditionalChinese

IBM AIX


Sun Solaris

BIG5

BIG5

BIG5

zh_TW

zh_TW.big5

zh_TW.BIG5

Deploying thin client localizationsUse 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 rootdirectory in the /lang/textserver/language-code directory. If you change oneof the text server XML files (*_locale.xml and *_errors.xml), regenerate thewebstrings.xml file:

1. Change to the \web\htdocs\tc\intl\ directory in the Teamcenter applicationroot directory.

2. Copy the web_gen_xml.dat file to theWeb_tier/staging-location/webapp_root/intl/directory.

3. Change to theWeb_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 stringtranslations.

5. Copy the webstrings.xml file to the language directory.

6. Regenerate the Web tier application (file-name.ear) and deploy in an applicationserver.

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 newlanguage 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 ofthe web_local_lang parameter from en to the new language name.

For example, if you localize the user interface for Hebrew, change theweb_local_lang parameter to he:

web_local_lang: exported "he";

Caution

Do not change the web_char_encoding parameter from UTF-8. Alllanguages must be UTF-8 encoding.

5. Change to the Web_tier\staging_location\webapp_root\intl\ directoryand 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 Teamcenterapplication root directory.

b. Copy the web_gen_xml.dat file to theWeb_tier/staging-location/webapp_root/intl/directory.

c. Change to theWeb_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 languagestring 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 applicationserver.

Convert the thin client user interface for Hebrew

Converting the thin client user interface for the Hebrew language requirescustomized development of thin client pages and Java code and definitions ofUnicode standards in the Teamcenter application.

When installing the rich client, you must choose the Latin-Hebrew ISO8859_8character set.

You must also check that the charsets.jar and font.properties.iw files are presentin the JRE_HOME/lib directory.

Deploying rich client localizationsDeploy 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, setthe locale of the client workstation to one of the Siemens PLM Software-providedlocales. No other steps are required.

In addition to English, Siemens PLM Software provides Teamcenter rich client andthin client user interfaces localized for the following languages:

Chinese (Simplified)Chinese (Traditional)FrenchGermanItalianJapaneseKoreanRussianSpanish

Update rich client localized text

If you change the strings of a localized rich client user interface contained in theportal_localization.jar file, you must convert the files to Unicode and regeneratethe Java archive (JAR) file.

To identify the localized user interface files you need, look for the languageand country identifier added to the base resource file. For example, for theaif_locale.properties English resource file, which must remain in English, theequivalent 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, fromaif_locale.properties to aif_locale_temp.properties.



2. Edit the base_locale_temp.properties file, modifying the values to the correctnative language.

3. Save the file.

4. Run the native2ascii utility against the temporary properties file to convert itto a Unicode properties file.

The native2ascii utility is in the \bin directory of SDK 1.4. For moreinformation, 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 thefollowing 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 musthave 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.propertiesBASE_locale-ID_language-ID.propertiesBASE_locale.propertiesBASE.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 inyour network, you can install Teamcenter servers or two-tier rich clients silently,using a preconfigured installation program. Silent installation suppresses mostinstallation prompts and requires minimal user interaction.

Capture, manage, and launch a silent Teamcenter installation using TeamcenterEnvironment Manager.

Create a silent installation configuration file1. Log on to the Teamcenter corporate server host and change to the root directoryof the Teamcenter software distribution image.

2. Start Teamcenter Environment Manager (tem.sh) from the Teamcenter softwaredistribution image.

3. In the Getting Started panel, select the Set up a silent installation distributioncheck box. Click Next in the following panels until you reach the SilentInstallation panel.

4. In the Silent Installation panel, in the Silent Configuration File box, specify thepath to the silent installation file, for example, silent.xml. The specified pathmust 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 youspecified in step 4. This file records your settings and selections during theinstallation. You can use this file to silently install Teamcenter on another hostwith the same settings.

Launch a silent installationTo 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 theinstallxxx.log file under the install directory in the Teamcenter applicationinstallation directory.


Chapter 15 Silent installation

Modify the silent installation configuration fileThe silent installation configuration file is XML-based (figure 15-1). After creatingthe file and establishing the file structure using Teamcenter Environment Manager,you can change the installation by manually modifying the values of the XMLelements in the file (table 15-1).

Caution

Siemens PLM Software recommends using an XML editor to ensurewell-formed XML code. Do not change the XML structure of the file. If XMLfile 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 thatTeamcenter Environment Manager can install. These arethe modules and features listed on the Select Featurespanel of Teamcenter Environment Manager.

module Specifies one Teamcenter module. The code attributeidentifies the module. To define whether TeamcenterEnvironment Manager installs the module, set theselected attribute to either true or false.

feature Specifies one feature of a Teamcenter module. Thecode attribute identifies the feature. To define whetherTeamcenter Environment Manager installs the feature, setthe selected attribute to either true or false.

data Lists all Teamcenter Environment Manager Java classesand values defining aspects of installation, such as the pathto the installation directory for Teamcenter applicationfiles. For additional information, see the comments in theconfiguration file. The comments describe the class andvalid 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-3Patch the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4Patch the rich client silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4Patch the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . 16-4Patch 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 theUpdates Manager, a feature of Teamcenter Environment Manager (TEM). Patchesto the Teamcenter J2EE Web tier you install using the Web Application Manager.Teamcenter updates (maintenance packs and patches) are posted for download onGTAC when available.

Distribution of Teamcenter updatesTeamcenter 8 updates are delivered in patches and in maintenance packs (MP).Patches to Teamcenter servers and two-tier rich clients are applied using theUpdates Manager in Teamcenter Environment Manager (TEM). Patches to theJ2EE Web tier and over-the-Web (OTW) distribution servers are applied using theWeb 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 patches1. 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 dothe 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 EngineeringProcess Management Visualization, uninstall this feature using TEM.

Patching Teamcenter Environment Manager1. If the patch you downloaded contains an updated installer file (install.zip),extract this file into your installed Teamcenter environment to updateTeamcenter 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, overwritingexisting 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 PATHenvironment variable and enter the unzip command again.

• Enter the unizip command with the full path to yourTC_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 followingcommand:

chmod 755 tem.sh

Install patches on the corporate server1. 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 downloadedin the Update file box. Click Next.


Installing Teamcenter patches

Note

TEM stops all Teamcenter services during the update process. All userslogged on to the environment are notified that it will not be availableuntil the update process is complete. Make sure all Teamcenter clientsand processes on the host are stopped before you continue. If Teamcenterservices or processes are running, the update may fail because TEMcannot 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 yourTC_DATA directories.

a. Create a backup of your current TC_DATA directories.

b. Extract the Teamcenter8\data directory from theTeamcenter8_MPnumber_platform.zip file and copy the contents to yourTC_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 stepsrequired to complete the patch.

Restart all Teamcenter-related processes and services (such as TCFS, FSC, databasedaemons, and so on).

Note

Each time you add a new feature to your installation, reapply installedpatches because the added feature’s files may have been patched previously.Adding a feature can overwrite that feature’s patched files with the older filesfrom the original software distribution image.

Update your database’s version information:

1. Open a Teamcenter command prompt.

2. Type the following command:install —set_version “INFORMATION MANAGER VTeamcenter-version”

Replace Teamcenter-version with the full version and patch level of theTeamcenter installation. If you are not sure what value to use, contact yourTeamcenter support representative.

Patching the rich clientThere are two multiple for patching the rich client. Choose a patching methodaccording to how you installed the client. If you installed the rich client during yourserver installation with the TEM, follow the steps in Patch the rich client usingTEM. If you installed the rich client using the Over-the-Web Installer distributionserver with one or more distribution server instances, patch each distribution serverinstance 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, followthe steps in Patch Lifecycle Visualization.

Note

If the patch you downloaded contains a file named portal_patch.jar thatis empty, this is intentional. This file is obsolete and is provided only as aplaceholder.

Patch the rich client using TEM

Patch the rich client using the steps in Install patches on the corporate server. If therich 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 noprompts or user interface:

1. Open a command prompt.

2. Change to the TC_ROOT/install directory.

3. Type the following command:tem.sh –p "patch-path/Teamcenter8_mpnumber_platform.zip"

Replace patch-path with the path to the downloaded maintenance pack. Replacenumber with the maintenance pack ID and platform with the platform identifier.

This procedure launches TEM and applies the patch with no user interactionrequired.

Note

You must enclose the path to the patch in quotation marks (") for paths thatcontain 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 theTeamcenter8_MPnumber_OTW.zip file. Instead of patching the rich client at allinstalled locations, you can patch any or all distribution server instance installationsthat were installed using the Web Application Manager. To ensure all rich clientsinstalled from the patched distribution server instance download the patched filesautomatically the next time they are launched:

1. Download and unzip the Teamcenter8_MPnumber_OTW.zip file to yourcomputer.

2. Shut down the distribution server.




4. Click the Copy ICD button. Browse to the expanded patch location to select theicd directory, and then click OK to copy the ICD files to the Web ApplicationManager.

5. Select the installed rich client instance you want to patch and click Modify.The Web Application Manager displays the Modify Web Application dialog box.

6. Click Modify Disk Locations.

7. Click Add and add the patch location to list of disk locations for install images.

8. Select and install patches. If you add patches to a previously patched instance,the steps differ from the first patch installation.

Initial MP patch Additional MP patches

a. Click Add Solutions.

b. Select Rich Client Patch and clickOK.

c. In the Modify Web Applicationdialog box, click OK to beginpatching.

d. After the patch is installed, clickOK to close the Progress dialogbox.

a. Click Reinstall Solutions.

b. In the Reinstall Solution dialogbox, click OK.1

c. In the Confirm dialog box, clickYes.

d. In the Modify Required ContextParameters dialog box, click OK tobegin patching.

e. After the patch is installed, clickOK to close the Progress dialogbox.

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 containsthe patch. Any rich clients previously installed from this instance has the patchapplied the next time the rich client is launched. Any future rich client installationsare 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 theWEB_ROOT directory to update the Web Application Manager to the latestversion.

4. Follow the steps in Patch the rich client using the Over-the-Web Installer with thefollowing exceptions:

a. In step 5, select the instance that contains the Engineering VisualizationPatch.

b. In step 8, select the Engineering Visualization (Install and Configure)solution.

c. Repeat steps 5 through 9, selecting the instance that contains theTeamcenter Visualization (Install and Configure) solution and selecting theTeamcenter Visualization solution.

Patch the distribution serverIf you have an over-the-Web rich client distribution server set up, you have to extractthe INSTALL_TCWEB.TZ/EXE image from the Teamcenter software distributionimage to a local directory on your machine and then run the Web ApplicationManager (insweb) from that local directory. During that setup, you installed thedistribution 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 theOTW_MP_LOC temporary directory.

2. Shut down your running distribution server.

a. In a command prompt, change the directory to theSTAGING_LOC\webapp_root directory where your distribution server isinstalled.

b. Type the following command:stop_server host:rmi_port

Replace host with the name of the host where you have the RMI registry anddistribution server running and rmi_port with the port number that youused for starting the RMI registry (the default is 12099).

c. If the shutdown is successful, you should see output similar to the followingin 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 theSTAGING_LOC\webapp_root directory.

4. Restart your distribution server.

a. In a console window, change the directory to theSTAGING_LOC\webapp_root directory.

b. Run start_server.

c. Your distribution server should restart with the patches applied.

Patch the Web tierTo install the Web tier, you must extract the INSTALL_TCWEB.TZ/EXE imagefrom the base release CD to a local directory on your machine and then run the WebApplication Manager (insweb) from that local directory. You then must generate adeployable (EAR orWAR) file and deploy that file on your Web application server.The local directory in which you ran the Web Application Manager utility is calledWEB_ROOT.

The patch files for a Web Tier installation are in one of two places. Theyare in the TC_ROOT\additional_patch_info\Web_tier directory if thefiles were put there as TEM was patching the server or the files are in theTeamcenter8_MPnumber_platform.zip file. If you have not patched the server,access the files by unzipping the patch file contents to a temporary location, referredto as PATCH_LOC.

Note

Because the files can be in either place, the location is referred to asWEB_FILES_LOC in this procedure.

1. In Windows Explorer, browse to the WEB_FILES_LOC\Web_tier directoryand look at its contents.

2. Open theWEB_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 installationand 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 theWEB_FILES_LOC\Web_tier directory to the Disk Locations for Install Imageslist.

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 disklocation list prior to opening to the Reinstall Solutions dialog box.

11. In the Reinstall Solutions dialog box, select the solutions that you want to patchand click OK.

The information on which solutions need to be patched for a particular MPrelease should be listed in the Special Release Notes section of the READMEdocument in the release_info directory.

12. If the Modify Required Context Parameters dialog box appears, type theappropriate values for any required context parameters and click OK.

13. The Web Application Manager regenerates the Web tier web application withthe patched files. Make sure a deployable file (EAR or WAR) is generatedduring this process. If it is not, click Generate Deployable File in the ModifyWeb Application dialog box.

14. After the deployable file is generated, go to the Web tier Web application’s stagingdirectory and find the deployable file (EAR or WAR) under the deploymentdirectory.

15. Take the new deployable file and deploy it to your Web application server,replacing the previous deployment. The new deployable file contains the Webtier patches.

Review the README fileThe 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 toapply various patches or additional information on what configuration needs tobe performed for the patches.

Review this README file to determine if you need to take additional action afterpatching your files.


Chapter

17 Installing Teamcentermaintenance packs


Chapter

17 Installing Teamcentermaintenance packs

Teamcenter maintenance packs (MPs) are issued for Teamcenter releases and madeavailable 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 Teamcenterinstallation as a single package.

• Full installation

A maintenance pack contains a complete Teamcenter installation package andcan be installed on a host with no existing Teamcenter software.

To install a maintenance pack as a complete new Teamcenter installation, performthe procedures in this guide, beginning with Getting started.

To apply a maintenance pack to an existing Teamcenter installation, perform theprocedures in the Upgrade Guide. When selecting a path in the Getting Startedpanel in Teamcenter Environment Manager (TEM), choose Install an MP to anexisting 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 configurationsusing Teamcenter Environment Manager. You can then remove your database server.

Uninstall Teamcenter configurations and installationsTeamcenter Environment Manager uninstalls Teamcenter configurations. Touninstall a Teamcenter installation, you must individually uninstall eachconfiguration in any order. If you have only one configuration, selecting it uninstallsthe Teamcenter installation.

1. Start Teamcenter Environment Manager:

a. Access the install directory in the Teamcenter application root directory forthe 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 youselected.

Teamcenter Environment Manager displays the Uninstall panel.

6. Select Yes to confirm uninstallation and click Next.If the configuration includes Teamcenter Foundation, Teamcenter EnvironmentManager 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 uninstallthem 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 Teamcenterconfiguration.

If the uninstallation is not successful, Teamcenter Environment Manager stopsprocessing when it encounters the error and displays a message indicating thelocation of the log file containing the error.

9. If you selected the option in TEM to remove the Teamcenter database, thedatabase is moved to the Oracle10g recycle bin. To permanently remove thedatabase, launch SQL*Plus and enter the following command:

PURGE RECYCLEBIN;

Uninstall OracleFor information about uninstalling Oracle, see the Oracle10g Installation Guide onthe 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

A

Application Interface Web ServiceTeamcenter extensions to a Web service such as gSOAP or WebLogic. Theseextensions allow Teamcenter to share data in a collaboration context with anotherapplication. Application Interface Web Service includes a SOAP server. ApplicationInterface Web Service components are installed and deployed as part of the Web tier.

ArchitectureSet of decisions, patterns, and principles for a product suite. The architectureprovides a framework for application development within that product suite and isindependent of specific functions.

Assigned FSCFMS 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. Anassigned FSC is typically the FSC nearest to the client host. In small deployments,an assigned FSC can also serve as the parent FSC.

B

Build PlatformPlatform required to build a customization. Compare with Certified Platform andSupported Platform.

C

Certified PlatformPlatform the base product is certified to operate on. Compare with SupportedPlatform.

Client TierTeamcenter architectural tier that comprises the Teamcenter clients, Teamcenterintegrations with third-party applications, such as Teamcenter’s Integration forMicrosoft Office and Teamcenter Engineering 2007 Integration for AutoCAD, andthe third-party applications themselves, such as Microsoft Office and AutoCAD.

ConnectorSee Global Services Connector.

Connector to Enterprise Knowledge ManagementEnterprise JavaBean that connects Global Services with Enterprise KnowledgeManagement. The optional connector to Enterprise Knowledge Management isprovided as a part of the Global Services connectors.

PLM00011 C Installation on UNIX and Linux Servers Guide A-1

Appendix A Glossary

Connector to TeamcenterEnterprise JavaBean that connects Global Services with Teamcenter. The optionalconnector to Teamcenter is provided as a part of the Global Services connectors andsupports both two-tier and four-tier deployment configurations.

Corporate ServerHost computer at the center of a Teamcenter network. This host contains theTeamcenter application root directory, Teamcenter data directory, licensing, filemanagers (Teamcenter File Services and File Management System), and volumes.For installations that include the Web tier (four-tier architecture), the corporateserver also contains the Teamcenter server manager. Multiple application clientscan map to or mount the corporate server.

D

Distribution ServerSee Rich Client Distribution Server.

Distribution Server InstanceSee Rich Client Distribution Server Instance.

E

eIntegrator AdminTeamcenter application that provides a simple integration mechanism you can useto integrate external data with Teamcenter. eIntegrator Admin maps external datasystems into equivalent objects in its database. The data can then be imported intothe database as forms.

eM-Planner InterfaceInterface between Teamcenter’s manufacturing process management andTecnomatix eM-Planner that allows data exchange.

Enterprise TierTeamcenter architectural tier that comprises a configurable pool of TeamcenterC++ server processes and a server manager. Larger sites can distribute the pool ofserver processes across multiple hosts. Smaller sites can run the pool of servers onthe same host as the Web tier.

Environment Variables ScriptTeamcenter script (tc_profilevars) that sets variables for the Teamcenterenvironment. This script sets all Teamcenter environment variables exceptTC_ROOT and TC_DATA.

ERP Connect ToolkitTeamcenter toolkit that can be configured to create an interface between Teamcenterand ERP systems.

ERP Connect to SAPTeamcenter integration that allows the controlled, auditable transfer of productinformation from Teamcenter to SAP.

A-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Glossary

F

FacilityPhysical location in an enterprise (for example, manufacturing plant or designcenter). One facility can comprise multiple sites. Compare with Site.

FCCSee FMS Client Cache (FCC).

FCC Configuration FileFile that configures an individual FMS client cache (fcc.xml). The FCC configurationfile defines such values as the parent FMS server cache location and the location andsize of the client caches. Values defined in the FCC configuration file can overridedefault values defined in the FSC configuration file.

File Management System (FMS)System that manages uploading and downloading file data between clients andvolumes in both two-tier and four-tier architecture deployments. FMS providesvolume servers for file management, a shared server-level performance cache forshared data access between multiple users, a client-based private user cache for richclients, and a transient datastore mechanism for transporting reports, PLM XML,and other nonvolume data between the enterprise and client tiers. FMS file cachingenables placing the data close to the user, while maintaining a central file volumeand database store.

FMSSee File Management System (FMS).

FMS Client Cache (FCC)FMS process that runs on a client host, uploading files to an FMS server cacheprocess, requesting files from an FMS server cache process, and caching files onthe client host. The FCC process manages two caches of whole files: a write cachecontaining files uploaded to a Teamcenter volume and a read cache containing filesdownloaded from a Teamcenter volume. It also manages one segment file cache forTeamcenter’s lifecycle visualization. Each Teamcenter rich client host requires alocal FMS client cache.

FMS Master Configuration FileFile that configures FMS (fmsmaster.xml). The FMS master configuration filedescribes the FMS network and defines groups of server caches. It can also definedefault values for server caches and client caches, such as maximum sizes. Valuesdefined in the server cache configuration file and in the client cache configuration filecan override the default values defined in the master configuration file.

FMS Master HostHost that contains the FMS master configuration file (fmsmaster.xml). This file isoptionally mounted at each FSC server.

FMS Server Cache (FSC)FMS process that runs on a server host and performs as a volume server (whenrunning 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 aconfiguration server. As a volume or cache server, the FSC checks all file accessrequests for a ticket that Teamcenter generates to authorize file access. As a cacheserver, 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 informationto file client caches and other FSCs. As a transient server, it delivers PLM XML andother transient files to clients. A minimum of one FSC must be deployed in anyTeamcenter installation. Multiple FSCs can be deployed, with each FSC performingone designated purpose as either a volume, a cache, or a configuration server.

Four-Tier ArchitectureTeamcenter architecture that includes four tiers: resource tier, client tier, Web tier,and enterprise tier.

Four-Tier DeploymentDeployment 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.

FSCSee FMS Server Cache (FSC).

FSC Configuration FileFile that configures an individual FMS server cache (fsc.xml). The FSCconfiguration file defines such values as the address of the master FSC, themaximum sizes of the segment file caches, and the upload timeout value. It can alsodefine default values for FCCs and other FSCs.

FSC GroupGroup of server caches defined in the FMS master configuration file.

G

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

Global Services ConnectorGlobal Services component that accesses information from a data source throughan Enterprise JavaBeans component called a connector. Each connector accessesinformation from a particular type of data source. For example, ProductionServer provides a connector for communicating with JDBC-compliant databases.Global Services offers optional connectors to Teamcenter, Enterprise KnowledgeManagement, Oracle Manufacturing, and SAP. One implementation of a connectorcan communicate with multiple data sources through the use of connectorconfiguration files.

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


Glossary

Group PreferenceTeamcenter preference applying to an entire group.

H

Heterogeneous Network EnvironmentTeamcenter network environment in which the database server, corporate server,and Teamcenter clients are provided by multiple vendors and can be a mixtureof UNIX and Microsoft Windows nodes.

Compare with Homogeneous Network Environment.

Homogeneous Network EnvironmentTeamcenter network environment in which the database server, corporate server,and all Teamcenter clients are provided by one vendor (for example, all SunMicrosystems or all Dell systems).

Compare with Heterogeneous Network Environment.

I

I-deasSiemens PLM Software’s integrated CAD/CAM/CAE solution that is used to design,analyze, test, and manufacture products.

IDSM ServerIntegrated Distributed Services Manager, a network node that runs a daemon processto handle the transfer of data objects among sites in a Multi-Site Collaborationnetwork. One IDSM server node must be designated for each Teamcenter databasefrom which objects are published; each server node can act for one database only.

J

JT CacheData Integration Services Adapter cache of JT files managed by the JT cache serviceand accessible to Teamcenter’s lifecycle visualization users. See also World AccessCache and Limited Access Cache.

JT Cache PopulatorStand-alone Data Integration Services Adapter utility that prepopulates the JTcache with JT part and assembly files.

L

Limited Access CacheData Integration Services Adapter cache of JT files that are accessible only toprivileged 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 accesscache. Compare with World Access Cache.

Local ServerSet of processes required to serve a single rich client installed on the same hostcomputer as the rich client. Teamcenter Integration for NX/NX Integrationconfiguration requires a local server.


Appendix A Glossary

M

Manifest FileFile 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 Installerconsults the manifest file to determine which files to download.

Master FSCFMS server cache that reads the master configuration file directly from the FMSmaster host. An FSC is configured either to read the master configuration filedirectly from the master host or to download it from another FSC with access to it.

Mentor Graphics IntegrationTeamcenter integration that allows users to store and manage Mentor GraphicsDesign Manager objects in Teamcenter.

Multi-Site CollaborationTeamcenter capability that allows the exchange of data objects among severalTeamcenter databases. Transfer of objects among databases is controlled by daemonprocesses running on designated servers. Objects are replicated by exporting themfrom their original database and importing them into the requesting database.Configuration of Multi-Site Collaboration is optional.

Multi-Site Collaboration NetworkNetwork of independent Teamcenter sites that are within the same enterprise andshare data using Multi-Site Collaboration.

My TeamcenterTeamcenter rich client application that is the main access point for managingproduct information. My Teamcenter provides the functionality for creating objectsin the Teamcenter database, querying the database for objects, checking in andchecking out objects, and managing tasks. Users can also open objects, automaticallylaunching the related application.

Each user has a personal My Teamcenter window that displays product informationas graphical objects. Although users share product information across the enterprise,they organize this information individually in personal workspaces.

N

Naming ServiceService that maintains a list of names and the objects associated with them. Forthe Teamcenter rich client, the naming service maintains a list of servers and theobjects and methods used by those services. The naming service is an integral partof the server directory.

NSSee Naming Service.

NX IntegrationIntegration between Teamcenter and NX. NX Integration users have full accessto the Teamcenter user interface from NX, and they can also access NX from theTeamcenter user interface.

Teamcenter Integration for NX and NX Integration have the identical userinterface in NX. The difference between the two products is the level of Teamcenter


Glossary

functionality available. Teamcenter Integration for NX excludes certain Teamcenterfunctionality, such as workflow and product structure editing.

O

Object ChooserDisplays objects appropriate for linking with another Teamcenter product. Indetermining the objects to display, the object chooser considers the security rights ofthe person accessing the Teamcenter product. See also Teamcenter Linking.

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

Object Directory Services SiteSite with the database that maintains a record of each object in a Multi-SiteCollaboration network. At least one Teamcenter database on a Multi-SiteCollaboration network must be designated as an ODS site. This site is used to storepublication records for the data objects.

Object LauncherLaunches another Teamcenter product from a linked object. Each Teamcenterproduct has an object launcher. See also Teamcenter Linking.

ODBC DriverTeamcenter integration that allows ODBC-compliant applications such as ActuateReport Writer, Crystal Reports, Microsoft Excel, and Access to extract data from aTeamcenter database for building reports.

ODS ServerSee Object Directory Services Server.

ODS SiteSee Object Directory Services Site.

Oracle HomeDirectory in which Oracle software is installed on the Oracle server node.

Oracle ServerSingle installation of Oracle able to service queries from several Teamcenterworkstations. The ORACLE_SERVER environment variable defines this Oracleservice node. For large-scale installations, the Oracle server is typically a dedicatedhigh performance workstation that is optimized specifically for running Oraclesoftware.

Oracle System Identifier (SID)Alphanumeric word used to identify a collection of processes and associated memorystructures as belonging to a particular Oracle database instance. TheORACLE_SIDenvironment variable defines the Teamcenter-Oracle system identifier.

Over-the-Web InstallerInstallation program that downloads the rich client software from a distributionserver instance to the user’s workstation over the Web.


Appendix A Glossary

P

Persistent Object Manager (POM)Interface between Teamcenter objects and the Relational Database ManagementSystem (RDBMS). The persistent object manager provides definition of classesby inheritance from existing classes and definition of attributes, manipulationof in-memory objects and support for their saving and retrieval to and from theunderlying RDBMS, support for applications accessing the same data concurrently,protection against the deletion of data used by more than one application, andsupport for the access control lists attributed to objects.

POMSee Persistent Object Manager (POM).

PreferenceConfiguration variable stored in a Teamcenter database and read when a Teamcentersession is initiated. Preferences allow administrators and users to configure manyaspects of a session, such as user logon names and the columns displayed by defaultin a properties table.

Published ObjectObject available to other sites in a Multi-Site Collaboration network. Publishing anobject creates a record in the ODS site database that can be read and searched byother sites. Until an object is published, it can be seen only by the owning site.

Q

QPLSee Quick Part Locator.

QPL ServerQuick part locator server. It provides a qpl daemon that can be used withDesignContext in the rich client. The qpl daemon coexists with all Teamcenterdaemons. Without this daemon DesignContext does not work.

Quick Part LocatorComponent of Repeatable Digital Validation (RDV) that creates and queries tables ina Teamcenter database. The quick part locator enables rapid lookup of componentsin an assembly. The tables cache precomputed results of location, attributes, andspatial relationship of all components in a product assembly. The quick part locatorprovides one of the search engines used by DesignContext.

R

RDVSee Repeatable Digital Validation.

Repeatable Digital ValidationCombination of software and processes that enables on-demand digital mockups foruse throughout the product development lifecycle. Repeatable Digital Validationservices are required for using QPL-based DesignContext.

Resource TierTeamcenter architectural tier comprising the database server, database, file servers,and volumes.


Glossary

Rich ClientJava-based user interface to Teamcenter installed on user workstations. The richclient accesses Teamcenter databases using a remote or local server.

Rich Client Distribution ServerSoftware that manages the connection between distribution server instances, theWeb 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 filesto download to the user’s workstation.

Rich Client Distribution Server InstanceRich client software to be installed on user’s workstations over the Web.Administrators create one instance for each server.

Role PreferenceTeamcenter preference applying to an entire role.

S

Security ServicesServices that eliminate prompts for logon credentials when users switch Teamcenterproducts within a user session. Authentication is performed by an external identityservice provider, such as lightweight directory access protocol (LDAP), instead ofthe Teamcenter product. At a site that deploys multiple Teamcenter products andSecurity Services, users log on once to access all participating Teamcenter products.

Server ManagerProcess that manages a pool of Teamcenter server processes in a deployment ofthe four-tier architecture. The server manager starts and times out a configurablenumber of server processes to communicate with the Teamcenter database. Aserver assigner process assigns available server processes to user sessions. Theserver manager communicates with the Web tier application using either TCP ormulticast protocol.

Server PoolPool of Teamcenter server processes running in the enterprise tier. A smalldeployment may have only one pool of server processes. For larger deployments, thepool of server processes is distributed as subpools across multiple hosts, with aserver manager for each subpool. Server pools are applicable for deployments of theTeamcenter four-tier architecture only.

SiteIndividual 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 toimplement Teamcenter at that site.

Site IDUnique identifier of a Teamcenter site. The site ID is used to generate internalidentifiers for Teamcenter objects that must be unique throughout an enterprise.Once established, site IDs should not be modified.

Site NameUnique name of a Teamcenter site stored in the database as a user-defined characterstring.


Appendix A Glossary

Site PreferenceTeamcenter preference that applies to the entire site.

Solid Edge ManagerTeamcenter integration that enables users to use Teamcenter to manage files fromwithin Solid Edge.

STEP TranslatorTeamcenter application that enables users to import product information into aTeamcenter database and to export Teamcenter data via STEP-compliant physicalfiles.

Supported PlatformPlatform configuration supported by GTAC.

System AdministratorTeamcenter user who is a member of the system administration group.

T

TCFSSee Teamcenter File Services (TCFS).

Teamcenter’s Integration for Microsoft OfficeTeamcenter integration that enables users to browse Teamcenter directly and createobjects in Teamcenter, check objects in and out of Teamcenter, and save files inTeamcenter. The Teamcenter’s Integration for Microsoft Office consists of ActiveXcontrols plugged into Microsoft Office.

Teamcenter’s lifecycle visualizationSiemens PLM Software suite that provides enterprise-wide product visualizationcapabilities. Teamcenter’s lifecycle visualization can be configured for use with boththe Teamcenter rich client and thin client as a stand-alone application.

The software suite includes Teamcenter’s lifecycle visualization base, Teamcenter’slifecycle visualization standard, Teamcenter’s lifecycle visualization professional,and Teamcenter’s lifecycle visualization mockup.

Teamcenter’s manufacturing process managementTeamcenter manufacturing process design and management system. Teamcenter’smanufacturing process management comprises several user applications, forexample, Plant Designer, Manufacturing Process Planner, Multiple View Editor,Part Planner, Report Generator, and Resource Manager.

Teamcenter Application RegistryIndependent Web-based service that allows a Teamcenter product to look up otheravailable Teamcenter products for launching a linked object. Administrators canregister and unregister installed instances of a Teamcenter product in the registry.

Teamcenter Application Root DirectoryDirectory location of the Teamcenter shared binary executables. The TC_ROOTenvironment variable defines this location. Generally, the contents of this directorychange only with a new version of Teamcenter.


Glossary

Teamcenter Data DirectoryDirectory location of the Teamcenter shared data subdirectories and files. TheTC_DATA environment variable defines this location. Each data directory isassociated with a single database instance.

Teamcenter Engineering VisualizationOptional Teamcenter rich client component that provides enterprise-wide productvisualization capabilities and is embedded in the rich client interface. FourTeamcenter Engineering Visualization products provide different visualizationcapabilities. Teamcenter Engineering Visualization Base provides basic 2D and 3Dviewing. Teamcenter Engineering Visualization Standard, Teamcenter EngineeringVisualization Base, and Teamcenter Engineering Professional provide increasingfunctionality.

Teamcenter File Services (TCFS)File services that enable the Organization application to create volumes and performother administrative functions. TCFS also supports file access for legacy versions ofNX and Teamcenter’s lifecycle visualization.

Teamcenter File StructureFile structure of an installed Teamcenter node; it separates homogeneously sharedbinary executables from heterogeneously shared data.

Teamcenter Integration for NXNX-based entry-level set of Teamcenter data management functions, such asvaulting, checking in, checking out, revision management, attribute synchronization,and searching CAD data. Teamcenter Integration for NX manages NX files andtheir data without exposing the user to full Teamcenter functionality. TeamcenterIntegration for NX users have only limited access to the Teamcenter user interface.

Teamcenter Integration for NX and NX Integration have the identical userinterface in NX. The difference between the two products is the level of Teamcenterfunctionality available. Teamcenter Integration for NX excludes certain Teamcenterfunctionality, such as workflow and product structure editing.

Teamcenter Integration for NX I-deasProduct that integrates Teamcenter and I-deas to provide a single data managementenvironment for users. Teamcenter Integration for NX I-deas users author theirdata in I-deas and manage the data in Teamcenter. Teamcenter Integration for NXI-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 HostTeamcenter host that functions as the gateway through which the Migration Wizardinitiates communications with the TDS server for data migration processing.

Teamcenter LinkingTeamcenter component that enables users to create links between Teamcenterobjects and objects in other Teamcenter products, such as Teamcenter’s systemsengineering and requirements management and Teamcenter’s portfolio, programand project management. Users can then launch the linked Teamcenter productfrom within either the rich client or the thin client.

TessellationProcess that translates a CAD file to a visualization file.


Appendix A Glossary

Thin ClientTeamcenter user interface that provides a streamlined browser-based view ofproduct information stored in a Teamcenter database. The thin client is configuredin the Web tier, which creates and serves its Web pages to the client.

Transient VolumeOperating system directory controlled by Teamcenter and used to store temporarydata for transport of reports, PLM XML, and other nonvolume data between the Webtier and client tier in a deployment of the Teamcenter four-tier architecture.

Two-Tier ArchitectureTeamcenter architecture that includes a resource tier and a client tier. The resourcetier comprises the database server and database. The client tier comprises theTeamcenter 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 DeploymentDeployment of the Teamcenter two-tier architecture. In a typical deployment of thetwo-tier architecture, the rich client and its local server are installed on a user’sworkstation as are third-party applications that integrate with the rich client. Thedatabase server and the Teamcenter corporate server are installed on one or moreseparate computers.

U

User PreferenceTeamcenter preference applying to a specific user.

V

VisualizationAbility to display a realistic, real time, graphical visualization of geometric data.

VolumeOperating system directory controlled by Teamcenter and used to store the filesmanaged by Teamcenter. When a user performs an action that causes Teamcenterto create a file, the file is created in the Teamcenter volume. Users cannot directlyaccess the files in Teamcenter volumes; they must do so via a Teamcenter session.

W

Web Application ManagerGraphical installation utility that generates supporting Web files (WAR and EARformat) for a named Web application. Web Application Manager also installs the richclient distribution server and creates distribution server instances.

Web TierTeamcenter architectural tier that comprises a Java application running in a Java2 Enterprise Edition (J2EE) application server. The Web tier is responsible forcommunication between the client tier and enterprise tier. The Web tier applicationalso includes the Application Interface Web Service (AIWS), WebDAV service, andthin client.

WorldAll users regardless of group or role.


Glossary

World Access CacheData 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 checksare performed when a user accesses a file from the world access cache. Compare withLimited Access Cache.

X

XML Object ListData Integration Services Adapter file that is formatted in XML and provides a listof the parts and assemblies to be populated into the JT cache.


Appendix

B Troubleshooting

Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . B-1Installation files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Problems/error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2Update Manager FTP errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3Resolving Web tier connection problems . . . . . . . . . . . . . . . . . . . . . . . . . B-3Change the deployable file name on the corporate server . . . . . . . . . . . B-3Change the deployable file name on the Web tier . . . . . . . . . . . . . . . . B-4

Web Application Manager needs location of Java file when installing richclient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4Make 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-8View additional information about an Oracle error message . . . . . . . . . . . B-9

Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . B-9

Recovering from a corrupted Oracle-based database . . . . . . . . . . . . . . . . . . . B-10Remove the Teamcenter infodba schema . . . . . . . . . . . . . . . . . . . . . . . . B-10


Appendix

B Troubleshooting

Troubleshoot problems you encounter during Teamcenter server installation.

Troubleshooting Teamcenter server installationFind system log files or error messages to help you determine the source of theproblems you encounter. Perform the solutions provided.

Installation files

Teamcenter Environment Manager generates files in the install directory under theTeamcenter application root directory.

• installdate-time_configuration-ID.log

Teamcenter Environment Manager generates a log file for each installation andconfiguration you create. The log file contains a record of activities performedby Teamcenter Environment Manager. Keep these files to maintain a completehistory for troubleshooting purposes.

• insautonomy.log

This file contains an installation record for Autonomy Intelligent Data OperatingLayer (IDOL) server, the default full-text search engine.

• configuration.xml

This file contains a record of the Teamcenter installation. TeamcenterEnvironment Manager uses the configuration file to enable you to maintain theinstallation, including adding and removing components, patching installations,and upgrading installations.

Caution

Do not remove the configuration.xml file. Removing theconfiguration.xml file results in the inability to modify the installationusing Teamcenter Environment Manager.

• uninstall.xml

This file contains a record of the Teamcenter uninstallation.

In addition, auxiliary programs called by Teamcenter Environment Managergenerate 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.syslogprogram-name.log

Of these files, the system log (.syslog) files usually contain the most relevant errordata.

Problems/error messages

See the following information for help resolving errors encountered duringTeamcenter installation.

Table B-1. Installation problems and error messages

Problem/error message Possible cause Solution<<null>>\\<<null>> onhost host-name doesnot have administratorprivileges

Most likely indicatesthat you attemptedto start TeamcenterEnvironment Managerusing the Windows runascommand or the Runas menu command.Teamcenter EnvironmentManager cannot bestarted as a user otherthan the user logged on tothe operating system.

Start TeamcenterEnvironment Manageras a user logged onto thesystem with Administratorgroup privileges and theLog on as a service right.For more information, seeRequired operating systemand user accounts.

Online help installed forthin client does not display

TheWEB_core_help_serverand WEB_help_serverpreferences were notset correctly by theinstallation program orthe installer.

Set theWEB_core_help_serverpreference to the full pathto the location of the onlinehelp help/index.htm file.

Set theWEB_help_serverpreference to the fullpath to the locationof the online helphelp/thin_client_dhtml/book.html file.

Online help installed forrich client (direct fileaccess) does not display.

Teamcenter EnvironmentManager did not updatethe portalHelpPageproperty in thesite_specific.propertiesfile.

Check theportalHelpPageproperty in thesite_specific.propertiesfile. If the path is notpresent or incorrect,manually correct it to referto the location of the onlinehelp 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 serveror while downloading updates.

Table B-2. Update Manager FTP errors

Error Resolution

Cannot contact server Host or port may be incorrect. Check Host andPort values and try again.

Cannot log on User name or password may be incorrect. CheckUser and Password values and try again.

Incorrect Path Path to the directory on the update server maybe incorrect. Check the path and try again.

Timeout Error The update manager received no response fromthe update server. Try connecting later or contactyour system administrator for assistance.

Transfer Error Contact with the update server was interrupted.Try your operation again or contact your systemadministrator for assistance.

Resolving Web tier connection problems

If the Teamcenter Web tier and the corporate server do not reference the same Webapplication name, the Web tier cannot connect to the Teamcenter server.

The Web application name specified in the Teamcenter Web tier must match the Webapplication name specified on the corporate server.

During installation of the Teamcenter corporate server, you specify this value in theWeb Application Name box in the Default Site Web Server panel of TeamcenterEnvironment Manager. The default Web application name is tc.During installation of the Teamcenter Web tier, the Web Application Managerassigns the Web application the default name of tc.If you specify a Web application name other than tc during corporate serverinstallation, you must change the corresponding value during Web tier installation.If the Web tier and the corporate server do not reference the same Web applicationname, the Web tier cannot connect to the Teamcenter server.

To ensure the Web tier and the corporate server reference the same Web applicationname, 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 theWEB_default_site_deployed_app_name preference to reflect the deployable filename specified in Web Application Manager. (Alternatively, you can set thispreference using the preferences_manager utility from a command prompt.)

For more information about theWEB_default_site_deployed_app_name preference,see the Preferences and Environment Variables Reference. For information aboutsetting 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 ApplicationInformation.

3. Change the value in the Deployable File Name box to reflect the Web applicationname 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 installingrich client

Under certain circumstances, the Web Application Manager does not find the Javajakarta-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 WebApplication Manager.

Make the Java jar file available for the four-tier rich client

1. Locate the bmide/compressed_files directory in the Teamcenter softwaredistribution image.

2. Extract the bmide.zip file to a temporary directory. (This file contains thejakarta-regexp-1.3.jar file.)

3. Add the temporary directory to the list of Disk Locations for Install Images inthe 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 databasesupgraded from Engineering Process Management 9.1.3 or Engineering ProcessManagement 2005 to Teamcenter 8. This occurs when legacy action rules are notremoved from the database during the upgrade.

After upgrading to Teamcenter 8, follow the instructions in the Business ModelerIDE Guide to migrate the GM Overlay action rules to extension rules and deletethe action rules. Some GM Overlay action rules have already been migrated toextension rules and are shipped as part of the Teamcenter Automotive Edition andGM Overlay templates. After you extract your database in step 2 of Convert actionrules to extension rules, verify the extracted action rules against the extensions inthe template. If there are no additional action rules to be converted in the BusinessModeler IDE templates, you can skip steps 3–5 in the procedure. Some of the GMOverlay action rule names are modified in Teamcenter 2007. The table shows themapping of action rules to extension rules.


Troubleshooting

Engineering Process Management 9.1.3– GM Overlay action rules

Teamcenter 2007 – GM Overlay methodextensions

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 Overlaymay change expected behavior in some areas of the GM Overlay. Forexample, you cannot create item types like CORP_Part, CORP_Install,CORP_Product, and CORP_Software.

Troubleshooting four-tier architecture deploymentIdentify the problem you encountered in your four-tier rich client architecture andperform the solution described.

Problem Solution

Error indicating no server pool Either the server manager is not started or TreeCachecommunication is not occurring. Ensure that you correctlycoordinated the server manager and Web tier TreeCacheconfiguration settings.

For information about coordinating these settings, see thedescription of the server manager context parameters intable E-1.

If you are using TCP communication, look for the GMSaddress during both application server startup and servermanager startup. The GMS address indicates the serviceport obtained. It should be within the range of ports pingedby TreeCache peers.



Problem Solution

Warnings of discarded messages These warnings indicate that you have two clusters on thesame port (multicast) or set of ports (TCP).

Your environment is working because you used differentnames for each cluster, but this is not an optimal environmentfor performance. Siemens PLM Software recommendsconfiguring a different port or set of ports for eachenvironment.

Error messages about the servermanager pool ID

These messages indicate that the pool ID is in use by anotherserver manager in the TreeCache cluster. Either place theserver managers in different clusters or configure a distinctpool ID.

handleJoin errors occur atstartup

Occasionally, TreeCache instances fail to accept connectionsand report handleJoin errors. Typically this errordisappears if you restart one or more cluster members.

Configuration is correct, butrun-time errors occur

To get additional information, increase the logging level forthe tree cache and jgroups classes for both the applicationserver and server manager:

1. Copy the log4j.xml file in the server manager run-timedirectory (TC_ROOT/pool_manager) to the applicationserver instance startup directory.

By default, the server manager run-time directoryincludes a log4j.xml file, but it logs only the warninglevel information. The default configuration sends logoutput 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 runtime. For example, to increase the log4j output for theJBossCache and jgroup classes to the INFO level,edit the file:

<loggername="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 statusof the server pool and dynamically change the poolconfiguration values (the values are not persistent). Accessthis functionality from the following URL:

http://host-name:jmx-port


Troubleshooting

Problem Solution

Replace host-name with the name of the host running theserver manager. Replace jmx-port with the number of theport running the JMX HTTP adaptor. This port number isdefined on the JMX HTTP Adaptor Port parameter when youinstall the server manager.

Elevated CPU usage Determine from logs whether users are frequently losing aserver due to the server timing out and are then having anew server assigned.

Server startup can consume a great amount of CPU. Considerincreasing timeout values and/or the pool size.

Either the server manager fails tostart when employing multicastTreeCache mode or the followingerror message is received:Exception in thread "main"java.net.SocketException:Can’t assign requestedaddress

Check the internet protocol configuration on the servermanager host. By default, Java prefers to use InternetProtocol Version 6 (IPv6) addresses. Incomplete IPv6configuration can cause Java socket exceptions that preventthe server manager from starting.

For example, an IBM AIX server might be configured to havean 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 upgradeconfiguration as documented in the IBM SystemManagement Guide or uncomment the following line in themgrstart script:

#JVM_ARGS="${JVM_ARGS} -Djava.net.preferIPv4Stack=true"

This line adds the –Djava.net.preferIPv4Stack=true Javaoption, instructing the JVM to use IPv4 addresses for theserver manager.

Note

If the Web application server is running on the samehost as the server manager, add this Java option to theWeb application startup script also.

On a machine with multiple IP addresses, it may benecessary 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 Mcastmode). In the server manager, this file can be found in theTC_ROOT/pool_manager directory. In the J2EE applicationit can be found in the file JETIServerAccessor.jar inthe staging area of the Web Application Manager. ForMcast mode, locate the UDP configuration line and addbind_addr=desired-address. For TCP mode, locate the TCPconfiguration line and add bind_addr=desired-address.



Problem Solution

Out-of-memory messages fromWeb application server runningon HP-UX platform

Review and adjust as necessary the settings for the followingkernel parameters:

max_thread_procmaxfilesmaxusers

Particularly, the default max_thread_proc value of 64 isnot sufficient for running the Web application server. Theoptimum values depend on the traffic level and machinecapabilities.

TreeCache connection failureafter restarting or redeploying

Terminating a server manager instance by sending it a signaldoes not clean up the TreeCache data stored in other four-tiercomponents regarding the terminated pool. When this servermanager is restarted, it cleans up this information. However,termination of a server manager in this way sometimesleaves the TreeCache communication mechanisms in acorrupted state and the server manager is not able to rejointhe TreeCache cluster. The problem can be resolved bystopping all four-tier components (the application serversand server managers) in the TreeCache cluster and thenrestarting them all. This problem can usually be avoidedby shutting the server manager down cleanly through theserver manager Administrative Interface. For informationabout using the server manager administrative interface, seethe System Administration Guide.

A similar problem can occur after the Teamcenter Web tierapplication is redeployed on the application server withoutstopping and restarting the application server. In this case,an extra TreeCache instance from the earlier deploymentmight still be running in the application server and thiscan interfere with proper functioning of the TreeCache.This can usually be resolved by stopping and restarting theapplication server.

Due to a Java run-time issue on Linux, these problems aremore likely if the four-tier component is run with the nohupcommand on Linux and the process is terminated by sendingit a signal.

Troubleshooting OracleWhen Oracle detects an error, an error code is displayed in the system consolewindow 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, theadditional 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 totroubleshoot the problem.

Troubleshooting Teamcenter Integration for NXTeamcenter Integration for NX may be unresponsive in a four-tier rich client if youspecify an incorrect value for Web Application Name during installation of theTeamcenter corporate server.

During corporate server installation, TEM prompts for the Web application name inthe Default Site Web Server panel. The Web application name you enter is used topopulate theWEB_default_site_deployed_app_name preference in the Teamcenterdatabase. When you build the Teamcenter Integration for NX Web application inWeb 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 inTEM, the Web application fails to connect to the Teamcenter server.

If you experience problems starting Teamcenter Integration for NX from the four-tierrich client, inspect the ugs_router system log for messages that resemble thefollowing 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-tierINTEROP: Waiting for UG/Manager V23.0 1 to start up...

This message results from the rich client expecting a Web application named tc butbeing unable to find it.

To resolve this problem, set theWEB_default_site_deployed_app_name preferenceto the correct name of the deployed Web application. You can update this preferenceusing the preferences manager from the command line or from within the rich client.

For information about using the preferences manager, see the Preferences andEnvironment Variables Reference.



Recovering from a corrupted Oracle-based databaseIf 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_SIDenvironment variables, and start the Oracle SQL*Plus utility. For example:

export ORACLE_HOME=/disk1/oracle/OraHome_1export 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 scriptthat 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 databaseor 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 topopulate it with new, empty Teamcenter tables or by importing a backup copy ofthe database (if the database was already in production).

You could also recycle the unpopulated database instance for other use as allTeamcenter 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 documentationimages for Teamcenter 8:

Image Description

Teamcenter software Contains Teamcenter software for your operatingsystem (Hewlett-Packard HP-UX, IBM AIX, Sun Solaris,SUSE Linux, Apple Macintosh, or Microsoft Windows).The software distribution image includes Teamcenterinstallation programs (Teamcenter Environment Managerand Web Application Manager) and required files forTeamcenter features such as Security Services.

For a detailed description of the contents of this image, seeTeamcenter software distribution image.

Teamcenterdocumentation

Contains the archive file required for installing Teamcenteronline help (tchelp.jar), Teamcenter documentation in PDFformat, and Teamcenter documentation in HTML format.

For a detailed description of the contents of this image, seeTeamcenter documentation distribution image.

Rich clientover-the-Web

Contains the files required to install the Teamcenter richclient over-the-Web on all supported operating systems,including a rich client distribution server and Over-the-WebInstaller.

Visualization Contains the files required to install Teamcenter’s lifecyclevisualization on all supported operating systems.

Oracle Contains directories, files, and scripts used to install OracleEnterprise Edition. The contents of this image are identicalto the Oracle Enterprise Edition CD-ROM distributed byOracle.

Teamcenter software distribution imageThe following table describes the directories in the Teamcenter software distributionimage:

PLM00011 C Installation on UNIX and Linux Servers Guide C-1

Appendix C Distribution media

Directory Description

additional_applications The additional_applications contains directoriescontaining applications such as the TeamcenterEDA client, File Management System client cache(FCC), Security Services, and the Siemens PLMSoftware Common Licensing Server.

additional_documentation Contains instructions for installing Oracle 10.

advanced_installations Contains the resource_managementsubdirectory that contains Resource Managerapplication files for Teamcenter’s manufacturingprocess management.

An additional subdirectory, cc_integration,contains Teamcenter’s manufacturing processmanagement components required when installingthe Multi-Structure Manager integration withTecnomatix eMPower.

bmide Contains the Business Modeler IDE.

cci Contains the CCI client.

install Contains files required for installing Teamcenter.

localization Contains localization and internationalization filesfor 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 Managementsupport 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 programand supporting files for generating the Web tierapplication and the rich client distribution serverand instance WAR files.

The base directory of the Teamcenter software distribution image also containsTeamcenter Environment Manager program (tem.sh) that installs Teamcenterexecutables and data directories.

Teamcenter documentation distribution imageThe Teamcenter documentation distribution image contains the archive file requiredfor installing Teamcenter online help (tchelp.jar) plus the following directories:

• HTML

Contains the Teamcenter online help library. To display the online help libraryindex 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 theonline help library index page, open the index.htm file.

Note

If you use popup blocker software, configure it to allow popups within theTeamcenter 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 caninclude in Teamcenter server or client configurations. The Web Application Managerprovides rich client solutions you can add to rich client distribution instance.

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

Table D-1. Teamcenter solutions

Solution Features

Corporate Server Teamcenter File ServicesTeamcenter FoundationFMS Server CacheNX UG Integration

Business Modeler IDE Business Modeler TemplatesClient

Dispatcher (Dispatcher Server) Dispatcher ServerEDA Standalone Client EDA Standalone Client

PADS SupportMentor SupportCadence SupportMentor Expedition Library SupportMentor Board Station Library SupportMentor PADS Library SupportCadence Allegro Library Support

Global Services Teamcenter FoundationFMS Server CacheJ2EE Based Server ManagerGlobal Services FrameworkGlobal Services Preferences

Log Manager Query Service Log Manager Query ServiceMultisite 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-tierRich Client 4-tier Teamcenter Rich Client 4-tierVolume Server Teamcenter File Services

FMS Server Cache

Teamcenter featuresTEM provides the following features and feature groups in the Select Featurespanel. 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 enablea feature, select its prerequisite features. For information about featureprerequisites, see the feature description.

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

Table D-2. Teamcenter featuresFeature/Subfeature Description

Teamcenter Corporate Server Teamcenter corporate server features.

Teamcenter File Services Installs the Teamcenter File Services (TCFS) service that enables administratorsto create volumes using the rich client Organization application and to performother administrative functions. TCFS also supports file access for legacy NX andTeamcenter’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 ata later date.

When you also install File Management System, the operating system userrunning TCFS must be the same operating system user running FMS.

Teamcenter Foundation Installs the complete Teamcenter application root directory (TC_ROOT), includingthe Teamcenter server process (tcserver), and either creates a data directoryfor storing database-specific files or configures this installation to connect to anexisting data directory.

If you create a data directory, you also provide information about the database touse with this installation. If you specify a new database, Teamcenter EnvironmentManager populates the database and creates a volume.

Installing Teamcenter Foundation is optional only when you install the followingcomponents: the Multi-Site Collaboration proxy servers, File Management System,Teamcenter File Services, online help, or sample files. When you install thesecomponents, 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 installan FSC server on each host that runs a server manager and on each host thatis to provide volume services.

You can optionally choose to install the FSC as a configuration server or aperformance cache server.

When you also install TCFS, the operating system user running FMS must be thesame operating system user running TCFS.

Workflow to Scheduling Integration Allows workflow to send updates to the related tasks in a schedule. This featurerequires a four-tier installation and Dispatcher to be installed/configured. Thisfeature requires Teamcenter Foundation.

NX UG Integration Installs default data types and loads template NX data to support TeamcenterIntegration for NX/NX Integration, the Teamcenter integration with SiemensPLM 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. Thisoption is applicable only when you are deploying the Web tier. This featurerequires Teamcenter Foundation and FMS Server Cache features.

For a smaller site, you can install the server manager and Teamcenter servers onthe 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. Thisoption is applicable only when you are deploying the Web tier. This featurerequires 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; youneed 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 Adminto Teamcenter Global Services, a Web-based application enabling clients to accessinformation 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 forlogon 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 ServicesInstallation/Customization guide.


• Application ID for this instance of Teamcenter in the Security Servicesapplication 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 withBill-of-Materials Management. Configuring this feature allows designs managedby this installation of Teamcenter to be related to parts and use or parts inproducts 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 ConsumerPackaged 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 thepath to the Teamcenter documentation distribution image, which contains theonline help files (tchelp.jar).

Note

For information about installing online help using as part of a Web tierapplication, see Teamcenter online help installation.

Content Management Base Installs the data model for Content Management.

For information about configuring this feature, see Content ManagementAdministration Guide.

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





Teamcenter Linking Configures linking between Teamcenter, Teamcenter’s portfolio, program andproject management, and Teamcenter’s systems engineering and requirementsmanagement 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 beseparately installed and configured.

• The Web tier application, including the optional Application Interface WebService (AIWS) and Teamcenter Linking parameters, must be installed andconfigured as described in .


• Host name and port number of the Java™ servlet running the TeamcenterApplication 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 installingthis feature, see the Specification Manager Guide.

CPG Materials Installs CPG Materials functionality for Consumer 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 TeamcenterEDA, the application that integrates ECAD applications with Teamcenter.

For complete information about installing Teamcenter EDA, see the GettingStarted 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 otherEnterprise Resource Planning (ERP)-supported applications, such as BAAN.

Teamcenter for Reporting and Analytics Installs the Teamcenter Reporting and Analytics (TcRA) integration. TcRA is astandalone reporting application that introduces a new folder in Report Buildercalled TcRA Reports, which contains reports created with TcRA.

SCM ClearCase for Foundation Installs ClearCase types and sets Teamcenter preferences to enable the integrationbetween Teamcenter and the IBM ClearCase software configuration management(SCM) tool.

For more information about installation, see the Teamcenter ClearCase IntegrationGuide.




Full Text Search Engine Installs Autonomy Intelligent Data Operating Layer (IDOL) server, the defaultfull-text search engine, and configures searching for the local database.

Autonomy IDOL enables users to retrieve objects from the Teamcenter databasebased 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 oftext data.

IDOL works with the IDOL server, DiSH server and File System Fetch as threeservices installed. The IDOL installer does not support the silent install option.

Global Services Preferences Installs Global Services Preferences.

Embedded Software Design DataManagement

Installs Embedded Software Design Data Management. For more informationabout this feature, see the Embedded Software Solutions Guide.

ECAD Part Library Management Installs ECAD part types to support ECAD part library management. This featurerequires Teamcenter Foundation, Vendor Management, and EDA Server Support.

Aerospace and Defense Foundation Installs Aerospace and Defense functionality for the Teamcenter server. Thisfeature requires Teamcenter Foundation and Vendor Management.

For more information about this feature, see the Getting Started with Aerospaceand Defense guide.

Content Management S1000D Enables management of documentation for the S1000D standard in ContentManagement.

For information about configuring this feature, see Content ManagementAdministration Guide. For information about using Content Management, see theContent Management Guide.

Aerospace and Defense Training Installs the Aerospace and Defense training program for the Aerospace andDefense Foundation feature. the for the Teamcenter server. This feature requiresTeamcenter Foundation, Vendor Management, and Aerospace and DefenseFoundation.

For more information about this feature, see the Getting Started with Aerospaceand Defense guide.

Dispatcher Server Installs the following Dispatcher Server components: scheduler, module andadministration 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 richclient users to translate Teamcenter data files to various visualization format forviewing in Teamcenter. This feature requires Teamcenter Foundation.


EMPS - Foundation Installs electronic design and manufacturing types to support ECAD translationand PCB design collaboration using Teamcenter embedded viewer.

EMPS - ECAD Translation Installs EMPS – ECAD translation, which allows conversion of a PCB design intothe XFATF format. ECAD translation support 36 different CAD formats. Thisfeature 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 AutomotiveEdition.




Wire Harness Configuration in GMOverlay

Configures wire harness configuration for a Teamcenter Automotive EditionGM Overlay environment. Requires Teamcenter Foundation, Wire HarnessConfiguration, Teamcenter Automotive Edition, and GM Overlay.

Configure AutoCAD Integration for GMOverlay

Configures AutoCAD Integration/AutoCAD Manager to operate in a TeamcenterAutomotive Edition GM Overlay environment. Choose this option only when youadd GM Overlay to a Teamcenter environment that includes AutoCAD Integration.If you attempt to include this configuration before installing GM Overlay and thestandard AutoCAD Integration, the install fails. Both GM Overlay and the baseAutoCAD integration must be installed and functioning before you choose thisoption. Requires Teamcenter Foundation and GM Overlay.

Install Libraries for AIWS Client Installs sample source code and executables that assist in developing anApplication 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 clientDesignContext application.

For QPL-based DesignContext, installing Repeatable Digital Validation (RDV)services is required. For Appearance-based DesignContext, installing RDV servicesis 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-basedengine.

• Database configuration for use with Repeatable Digital Validation.

DesignContext is available for both the rich client and thin client.

Embedded Software Manager forFoundation

Data types for Embedded Software Solutions.

ESM Base Installs ESS base types and updates preferences. Without these, ESS operationsdo not work from any interface (rich client, thin client, custom utilities, and otherclients).

ESM Processor Installs ESS processor types and updates preferences. Without these, ESSoperations 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, ESSoperations 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 theAs-Built Manager Guide.




Teamcenter Manufacturing Teamcenter’s manufacturing process management (Manufacturing ProcessManagement) features.

Install Libraries for ResourceBrowser

Installs libraries for the Resource Browser application.

Comprehensive ManufacturingTypes

Additional data types for Teamcenter’s manufacturing process management.

Customization for ProcessSimulate Integration

Installs additional data types for Process Simulate Integration Customization.

Customization for eM-ServerIntegration

Installs additional data types for Tecnomatix server integration customization.

eBOP reports Customization Installs additional data types for eBOP Reports Customization. This featurerequires Teamcenter Foundation and Customization for eM-Server Integration.

PAD/TWP Customization Installs additional data types for PAD/TWP Customization. This featurerequires Teamcenter Foundation, GM Overlay, and Customization for eM-ServerIntegration.

GM PAD/TWP Customization Installs additional GM data types for PAD/TWP Customization. This featurerequires Teamcenter Foundation, GM Overlay, Customization for eM-ServerIntegration, 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 GettingStarted with RDV guide.

This feature requires Dispatcher Server.

Bounding box generation from JT Enables generation of bounding box data from JT files, providing secondary datafor the cacheless search engine. For more information about configuring and usingcacheless 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 forthe cacheless search engine.

For more information about configuring and using cacheless search, see the GettingStarted 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, providingsecondary data for the cacheless search engine.

Database Daemons Optional database support services.

Database Daemons Task ManagerService

Checks user inboxes for tasks that have passed due dates, notifies the delegatedrecipients, and marks those tasks as late.

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




Database Daemons TesselationManager Service

Tessellates UGMASTER and UGALTREP datasets to the JT (DirectModel)dataset and attaches the JT dataset back to the item revision and UGMASTERand UGALTREP dataset.

Installing the Tessellation service is required to create the tessellatedrepresentations in Repeatable Digital Validation (RDV) that enable users ofthe DesignContext application to quickly visualize components in context. Thetessellated representations are created during the workflow release process,ensuring that JT files of the DirectModel datasets are updated as the NX filesare released.

Database Daemons Action ManagerService

Monitors the database for the creation of action objects and dispatches eventsthat have a specific execution time and events the Subscription Manager daemonfails to process.

Installing the Action Manager service is required to enable the rich clientSubscription Monitor application.

Database Daemons SubscriptionManager Service

Monitors the database event queue for the creation of subscription event objects.

Installing the Subscription Manager service is required to enable the rich clientSubscription Monitor application.

Multisite Services Services to support Multi-Site Collaboration.

Multisite Collaboration IDSMService

Installs the distributed services manager (IDSM) required to replicate databetween multiple Teamcenter sites, enabling the exchange of data objects withother Teamcenter databases over a wide area network (WAN).

Multisite Collaboration ODS Service Installs the object directory service (ODS) required to replicate data betweenmultiple Teamcenter sites, enabling the exchange of data objects with otherTeamcenter 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 additionalfeatures and applications, such as Teamcenter’s lifecycle visualization and NXManager.

Teamcenter Rich Client 4-tier Installs a four-tier rich client and optionally configures it for use with additionalfeatures and applications, such as Teamcenter’s lifecycle visualization and NXManager.

Rich Client (Shared Disk Deployment) Installs the rich client in a shared location. This client can be run from multiplehosts.

Dispatcher Client for Rich Client Installs Dispatcher Client for the rich client. This feature requires TeamcenterRich 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. Thisfeature requires NX Manager for Rich Client.

Render Document for Rich Client Provides Render Management capabilities for the rich client. This feature requiresDispatcher Client for Rich Client.

For more information about configuring and using Render Managementcapabilities, see the Rich Client Interface Guide.

For information about installing Dispatcher features, see Getting Started withDispatcher (Translation Management). For information about installing andconfiguring file translators for the Dispatcher Server, see the Dispatcher ServerTranslators Reference Guide.

Rich Client Add-Ons Add-on features for the Teamcenter rich client.




Teamcenter Extensions forMicrosoft Office

Installs Teamcenter’s Extensions for Microsoft Office. For information aboutinstalling this feature, see the Installation on Windows Clients Guide.

Office Client for Microsoft Office Installs the Teamcenter’s Client for Microsoft Office. For information aboutinstalling this feature, see the Installation on Windows Clients Guide.

Embedded Software Manager forRich Client

Installs Embedded Software Solutions for the rich client. This feature requiresTeamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.

CPG Materials for Rich Client

Installs CPG Materials support for Consumer Packaged Goods.


Teamcenter Single Sign-on for RichClient

Installs Teamcenter single sign-on for the rich client. This feature requiresTeamcenter 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 requiresTeamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.

Global Services Monitoring GUI forRich Client

Installs a rich client and configures it for use with the Global Services MonitoringGUI for Rich Client feature. This feature requires Teamcenter Rich Client 2-tier orTeamcenter Rich Client 4-tier.

Content Management System forRich Client

Installs Content Management functionality for the rich client. This featurerequires Teamcenter Rich Client 4-tier.

Teamcenter Visualization 8(Embedded) for Rich Client

Installs the embedded viewer for the rich client. This feature requires TeamcenterRich 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 RichClient 2-tier or Teamcenter Rich Client 4-tier.

EDA for Rich Client Installs Teamcenter EDA for the rich client. This feature requires TeamcenterRich Client 2-tier or Teamcenter Rich Client 4-tier.

Vendor Management for Rich Client Installs Vendor Management support for the rich client.

Specification Manager for RichClient

Installs Specification Manager functionality for the rich client.

For more information about installing this feature, see the Specification ManagerGuide.

SCM ClearCase for Rich Client Installs SCM ClearCase for the rich client. This feature requires Teamcenter RichClient 2-tier or Teamcenter Rich Client 4-tier.

Embedded Software Design DataManagement for Rich Client

InstallsEmbedded Software Design Data Management support for the rich client.For more information about this feature, see the Embedded Software SolutionsGuide.

This feature requires Teamcenter Rich Client 2-tier or Teamcenter Rich Client4-tier.

Teamcenter Visualization 8(Stand-alone) for Rich Client

Installs stand-alone application viewer for the rich client. This feature requiresTeamcenter 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 ofTeamcenter’s maintenance, repair, and overhaul.

For information about installing, configuring, and using this feature, see theAs-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 serverprocesses.




Web Tier for .NET Installs the middle tier processes that communicate with Teamcenter serverprocesses.

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 onthird-party external eclipse plug-ins from Altova MapForce. The Altova Mapforceeclipse plug-ins are dependent on the MapForce client. Requires MapForceProfessional client and MapForce eclipse plug-ins. Download these plug-ins fromAltova 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 ServerConfiguration

Configures the two-tier Teamcenter Server so that Business Modeler IDE canconnect to the Teamcenter Server.

4 Tier Teamcenter ServerConfiguration

Configures the four-tier Teamcenter Server so that Business Modeler IDE canconnect 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 ECADapplications 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 Layoutand PADS Logic) with the EDA client, enabling you to manage data that PADSprograms create. This feature requires EDA Standalone Client. You must alsoinstall Mentor PADS software.

Mentor Support Installs support for using Mentor Graphics Board Station software with the EDAclient. Separate installation of Mentor Graphics Board Station is required. Thisfeature requires EDA Standalone Client.

Cadence Support Installs support for using Cadence Allegro software with the EDA client. Separateinstallation of Cadence Allegro Design Entry is required. This feature requiresEDA 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 requiresEDA Standalone Client.

Mentor Board Station LibrarySupport

Installs support for using Mentor Graphics Board Station library with the EDAclient. Separate installation of Mentor Graphics Board Station is required. Thisfeature 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 EDAStandalone Client.

Cadence Allegro Library Support Installs support for using Cadence Allegro library with the EDA client. Separateinstallation of Cadence Allegro Design Entry is required. This feature requiresEDA Standalone Client.



Rich client solutionsYou can add rich client solutions to a rich client distribution instance. These solutionsadd functionality to the four-tier rich client installed using the Over-the-WebInstaller. For information about creating a rich client distribution instance, seeInstall a rich client distribution instance.


Over-the-Web Installer Installs the program that installs the rich client overthe Web. This solution is required.

Rich Client 4–Tier Installs the rich client software required for thefour-tier architecture. This solution is required.

As-Built Manager for RichClient 4-Tier

Adds As-Built functionality for the four-tier richclient. As-Built is part of Teamcenter’s maintenance,repair, and overhaul.

For information about installing, configuring, andusing this feature, see the As-Built Manager Guide.

CPG Materials for RichClient 4-Tier

Installs CPG Materials support for ConsumerPackaged Goods.

For information about installing this feature, seeGetting Started with Consumer Packaged Goods.

Content ManagementSystem for Rich Client4-Tier

Installs Content Management, the application usedto manage technical documentation using SGML andXML information stored in a Teamcenter database.This solution is optional.

EDA for Rich Client 4–Tier(Configuration Only)

Configures the rich client to use Teamcenter EDA, theapplication that integrates ECAD applications withTeamcenter. Separate installation of the stand-aloneEDA client (using Teamcenter EnvironmentManager) is required. This solution is optional.

ESDDM for Rich Client4-Tier

Installs Embedded Software Solutions Design DataManagement support for the rich client.

For more information about this feature, see theEmbedded Software Solutions Guide.

Embedded SoftwareManager for Rich Client4–Tier

Installs Embedded Software Solutions support forthe rich client.

For more information about this feature, see theEmbedded Software Solutions Guide.

Embedded TranslationServices for Rich Client4–Tier

Installs Dispatcher Client for the rich client.

For information about using this feature, see GettingStarted with Dispatcher (Translation Management).

GM Overlay for Rich Client4–Tier

Installs the Teamcenter’s Automotive Edition–GMOverlay application. This solution is optional.

GS Monitoring GUI for RichClient 4–Tier

Configures the rich client for use with the GlobalServices Monitoring GUI for Rich Client feature.




MS Office Integration forRich Client 4–Tier

Installs the application that integrates Teamcenterwith Teamcenter’s Integration for Microsoft Office.Separate installation of Microsoft Office is required.This solution is optional.

NX Manager for Rich Client4–Tier

Configures the rich client to use TeamcenterIntegration for NX or NX Integration, the applicationthat integrates Teamcenter with NX. Separateinstallation of the Teamcenter Integration for NX orNX Integration executables is required (as part ofNX installation). This solution is optional.

SCM ClearCase for RichClient 4–Tier

Installs the integration between Teamcenter and theIBM ClearCase software configuration management(SCM) tool and configures the rich client for itsuse. Separate installation of ClearCase software isrequired. This solution is optional.

Specification Manager forRich Client 4–Tier

Installs Specification Manager functionality for therich client.

For more information about this feature, see theSpecification Manager Guide.

Teamcenter Applicationsfor Microsoft Office

Installs Teamcenter’s Extensions for Microsoft Officeand the Teamcenter Plugin for Microsoft Project,which allows Microsoft Project users to exchangedata directly with Schedule Manager. Separateinstallation of Microsoft Office is required.

For information about installing these features ona rich client host, see the Installation on WindowsClients Guide.

Teamcenter Visualization 8(Embedded) for Rich Client4–Tier (Configuration Only)

Configures the rich client to use the embeddedviewer when Teamcenter’s lifecycle visualization isseparately installed on the client workstation. Thissolution is optional.

Teamcenter Visualization8 (Embedded) for RichClient 4–Tier (Install andConfiguration)

Installs the embedded viewer and configures the richclient. This solution is optional.

Teamcenter Visualization8 (Stand-alone) for RichClient 4–Tier

Configures the Teamcenter’s lifecycle visualizationapplication (the stand-alone application viewer).Separate installation of Teamcenter’s lifecyclevisualization is required. This solution is optional.

Vendor Management forRich Client 4–Tier

Installs Vendor Management support for the richclient.




Render Document for RichClient

Installs Render Management capabilities for the richclient.

For more information about configuring and usingRender Management capabilities, see the Rich ClientInterface Guide.

For information about installing Dispatcher features,see Getting Started with Dispatcher (TranslationManagement). For information about installing andconfiguring file translators for the Dispatcher Server,see the Dispatcher Server Translators ReferenceGuide.

Rich Client 4–Tier LiteEdition

Installs the lite edition of the four-tier rich client.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 byTeamcenter Web tier solutions.

Table E-1. Web tier required parameters


General parameters

DEPLOYABLE-FILE-NAME Name of the deployable file you are creating for theWeb tier application. The name is configurable; WebApplication Manager adds the file extension.

TcEngEncoding Teamcenter character encoding set for localization.This value must match the encoding specified for theTeamcenter server.

For example, if the Teamcenter server is runningusing ISO8859_1 encoding, specify ISO8859_1 alsofor this parameter.

TcEngLocale Locale of the Teamcenter server for localization ofWeb tier messages. This locale must match the localeof the Teamcenter server.

For example, if Teamcenter server is running in theRussian locale, specify ru_RU for this parameter.

webdav.useHybrid Specifies whether users must enter a name andpassword in a Microsoft application even whenlogged on through a Teamcenter application.

This parameter is used when a site enables users toinstall the Teamcenter Teamcenter’s Integration forMicrosoft 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 sharedglobal server pool.

You must supply the same name as specified forthe server manager (installed using TeamcenterEnvironment Manager).

TreeCache Mode Communication protocol mode between TreeCachepeers, either TCP or multicast.

You must supply the same mode as specified forthe server manager (installed using TeamcenterEnvironment Manager).

TreeCache Cluster Port Required only when the TreeCache communicationmode is Mcast.

Port used for multicast communication between theapplication server and the server manager.

You must supply the same port number as specifiedfor the server manager (installed using TeamcenterEnvironment Manager).

When configuring multiple environments, use adifferent port number for each environment.

Local Service Port Required only when the TreeCache communicationmode is TCP.

Specifies the TCP port at which this TreeCachecluster member provides the TreeCache service.

If you install the Web tier application on the samehost as the server manager, the local service port forthe Web tier application must be different from thelocal service port for the server manager.

TreeCache Peers Required only when the TreeCache communicationmode is TCP.

Specifies a list of addresses (host name andport number pairs) to ping for peer members ofthe TreeCache cluster in TCP communicationmode. It is a comma-separated list of the formhost1[port1],host2[port2],.. Do not use the formhost1:port1, ... because the colon character (:) isnot permitted.

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

In addition, the TreeCache may find more than onepeer 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 localservice port value).

Once established, peers exchange data regardingavailable server pools. This cluster member pingseach host/port pair in the list. To be found, a peermust have a matching service port. (See LocalService Port in this table.)

• As a minimum, specify the service port for allJava 2 Enterprise Edition (J2EE) applicationserver hosts and server manager hosts you wantthis Teamcenter server to communicate with.

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

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

For small configurations, all members shouldbe included in the peers list. For largerconfigurations, it is recommended that thenumber of pinged ports be limited to no morethan six. All members should ping at least thesame subset of primary server managers so thatTreeCaches connect and data is shared.

Connection Timeout Required only when the TreeCache communicationmode is TCP.

Maximum time in milliseconds that a TreeCachecluster member waits for peer responses to TCPpings.

The larger the value you specify, the more slowlythe first server manager starts.

Typically, you supply this same value for theConnection Timeout parameter specified forthe server manager (installed using TeamcenterEnvironment Manager).





MAX_POOL_SIZE Specifies the maximum number of concurrentconnections to Teamcenter servers allowed by theapplication server. If you do not specify a value,the Web tier application uses the application serverdefault value.

Note

This parameter applies to WebLogic, JBoss,and Oracle Application Server. For otherapplication servers, the maximum pool sizemust be set using the application serverconsole.

For information, see the Web ApplicationDeployment Guide.

Enterprise Application RegistrationID

ID used to register the application’s EJB andJ2C Connector. If you want to deploy multipleTeamcenter Web tier applications in a singleapplication server instance, each application mustbe assigned a unique ID.

LogVolumeName Name of the log volume.

LogVolumeLocation Log volume location, the root directory under whichlog files are created. The default location logsrepresent a child folder beneath the default rootdirectory of the target application server instance.This location varies depending on the applicationserver vendor.

Note

If the path you enter contains backslashcharacters (\) as path delimiters, use doublebackslash characters (\\) to represent singlebackslash characters.





Security Services parameters

IS_SSO_ENABLED Specifies whether Security Services is enabled forthis instance of Teamcenter.

SSO_APPLICATION_ID Application ID assigned to this instance ofTeamcenter in the Security Services applicationregistry. This information is required only when youare configuring the optional Security Services.

This ID is determined when Security Services isinstalled and configured. For information, seethe Security Services Installation/Customizationmanual.

SSO_logon_SERVICE_URL Complete URL of the Security Services logon ServiceWeb application. This information is required onlywhen you configure the optional Security Services.

This URL is determined when Security Servicesis installed and configured. For information, seethe Security Services Installation/Customizationmanual.

SSO_SERVICE_URL Complete URL of the Security Services IdentityService Web application. This information isrequired only when you configure the optionalSecurity Services.

This URL is determined when Security Servicesis installed and configured. For information, seethe Security Services Installation/Customizationmanual.

Table E-2. Web tier optional parameters


General Parameters

webmaster E-mail address of the administrator to whomquestions and comments about this application areaddressed.





staticResourceClientCacheExpiryTime

Maximum time in seconds that a client can use alocally cached static content (for example, images orJavascript) before requesting a fresh copy from theserver.

Setting this value too low causes the client tounnecessarily request content. Setting this value toohigh risks stale content. Typical values range fromseveral hours to one day.

Setting the value to 0 is valid and causes the client toalways ask for static content.

The default value is 28800 seconds (8 hours).

compressResponse Specifies whether a response to the client can becompressed if the requesting client supports it.

Compressing the response typically yields fasterresponse time to the client but requires additionalprocessing in the Web container.

Set this parameter value based on trial and error foryour instance of the server, bandwidth, and clientaccess environment.

The default value is true.

cacheCompressedStaticResourceOnServer

Specifies whether responses for static resources arecached on the server. This parameter is used onlywhen the compressResponse parameter is set totrue.

If the value is set to true, compressed responses forstatic resources are cached on the server, memorypermitting.

If the value is set to false, the compression occurs eachtime the client requests a static resource.

The default value is true.

responseCompressionThreshold

Threshold in bytes beyond which the server shouldcompress responses sent back to the client.

Typically compressing smaller responses does notyield much compression - so all responses equal toor smaller than this value will be sent to the clientuncompressed.

Setting the value to 0 is valid and causes the server tocompress every response sent to the client (assumingother parameters permit compression).





The default value is 500 bytes. Change this value onlyif absolutely required.

calculateResponseTime Specifies whether the group of response time filtersare 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 arequest from a rich client or thin client).

The response time filters should remain turned offunless you are collecting statistics.

The default value is false.





TreeCache Parameters1

PROCESS_MAX_PER_USER

Maximum number of server processes per user. Thedefault value (0) turns off the constraint, that is,specifies that there is no limit on the number ofprocesses per user.

QUERY_TIMEOUT Maximum time in seconds per request. The defaultvalue (0) turns off the constraint, that is, specifies thatthere 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_STATELESS

Time-out for stateless servers in a busy pool.

HARD_TIMEOUT_EDIT Load insensitive time-out for edit mode servers.

HARD_TIMEOUT_READ Load insensitive time-out for read mode servers.

HARD_TIMEOUT_STATELESS

Load insensitive time-out for stateless servers.

Application Interface Web Service Parameters

AIWS_teamcenter_linking_user_name

Name for user for logging on to Teamcenter on behalfof a remote Teamcenter application.

The default value is infodba.

For more information about AIWS, see the ApplicationInterface Web Service (AIWS) Configuration andCustomization Guide.

AIWS_teamcenter_linking_user_passwd

Password for user for logging on to Teamcenter onbehalf of remote Teamcenter application.

For more information about AIWS, see the ApplicationInterface Web Service (AIWS) Configuration andCustomization Guide.

Legacy URL support parameters







Parameter DescriptionrequestRedirectedTo Specifies the protocol and server, port, or domain for

accessing the thin client. The default value is theserver, 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 thisparameter to change a requested http://acme:8080URL to http://web.acme.com. A typical use for thisparameter is in a cluster configuration.

replacementFor CGIBIN_IMAN Specifies the replacement for cgi-bin/iman in theURL. Do not change the default value of tc/webclient(this value is currently the only supported value).

redirectionWaitTime Specifies an integer representing the number ofseconds to display the URL message to users beforeredirecting their requests to the new URL. The defaultvalue is 10 seconds. The minimum value is 0.

Table E-3. Global Services context parameters


Enterprise application parameters

ApplicationInstance Specifies the name uniquely identifying theapplication instance within the application server.

SSOAppID Specifies the unique value used to identify the GlobalServices application to the Security Services singlesign-on (SSO) server.

LogFileLocation Specifies the name and location of the loggingconfiguration file. By default, this is the log4j.xmlfile. If you are using the standard Global Serviceslogging configuration, do not change parametervalue. If you are going to customize the loggingconfiguration, you must create the custom file andprovide 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 valueis typically used.

TcGSDORJNDI Specifies the data object repository connector EJBJNDI name. This connector is used to manage datain the Global Services datastore. The default valueis typically used.





TcGSJDBCJNDI Specifies the JDBC connector EJB JNDI name.This connector can be used to manage data in theGlobal Services datastore or to connect any JDBCcompatible database. The default value is typicallyused.

TcGSMessageServerJNDI Specifies the Global Services message server EJBJNDI name. The default value is typically used.

TcGSNotifierReactorJNDI Specifies the Global Services notifier reactor EJBJNDI 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 enterpriseapplication (Global Services). For example:

http://host:port/TcGS

host and port are the application server host and theport number used to connect to the Global Servicesapplication, and TcGS is the context-root for theapplication.

global.services.proxy.user Specifies the Global Services user the proxy clientuses to execute calls to the server.

global.services.proxy.password Specifies the password associated with the GlobalServices proxy user.

global.services.proxy.client.IPs Provides a comma-separated list of authorized clientIP addresses or host names. The IP addresses cancontain 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 through192.168.0.255 and:

192.168.0.??

matches the addresses from 192.168.0.0 through192.168.0.99.

The wildcards match digits only. Therefore, anexpression like 192.168.*.* is valid. However, anexpression like 192.168.* is not.

Also, because the * character matches zero or moredigits, the expression 192.168.1.2* matches thefollowing addresses:





192.168.1.2192.168.1.20 through 192.168.1.29192.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 URLused to call the connector OSGi plug-in throughthe Jetty plug-in. The default value is typicallyused. If you change the value, you must updateRAC_OSGi_PLUGIN_URL parameter in theTeamcenterRACOSGiConfig.xml file.

TcGSConnectorJNDI Specifies the Global Services connector EJB JNDIname. This connector provides a connection to otherinstances of Global Services.

TcGSRACJNDI Specifies the Teamcenter rich client connector EJBJNDI name.

TcGSSOAJNDI Specifies the Teamcenter services-orientedarchitecture (SOA) connector EJB JNDI name.

TeamcenterConnectorJNDI Specifies the Teamcenter 2005 connector EJB JNDIname.

TcGSEngJNDI Specifies the Engineering Process Managementconnector EJB JNDI name.

TcGSEntJNDI Specifies the Enterprise Knowledge Managementconnector EJB JNDI name.

TcGSOMfgJNDI Specifies the Oracle Manufacturing connector EJBJNDI 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 toperform actions in Teamcenter.

global.services.teamcenter.password Specifies the password associated with the userthat the gateway solution uses to perform actionsin Teamcenter.

global.services.tceng2omfg.user Specifies the user that the gateway solution uses toperform actions in Teamcenter.

global.services.tceng2omfg.password Specifies the password associated with the userthat the gateway solution uses to perform actionsin Teamcenter.





globalservices.tceng2omfg.StagingDirectory

Specifies the location of staging directory. Thisdirectory is used to extract the PLM XML fromTeamcenter.

globalservices.OMfg.user Specifies the user that the gateway solution uses toperform actions in Oracle Manufacturing.

globalservices.OMfg.password Specifies the password associated with the userthat the gateway solution uses to perform actionsin Oracle Manufacturing.

globalservices.tceng2omfg.url Specifies the URL to this Global Services instance.This value is used by Teamcenter to get statusinformation on specific exchanges.

globalservices.tceng2omfg.maxobjects Specifies the maximum number of rows of objectsto retrieve from the Global Services activity statustable to be displayed in the user interface.

globalservices.tceng2omfg.engdateoutformat

Specifies the format of date values sent fromTeamcenter.

globalservices.tceng2omfg.engdateinformat

Specifies the format of date values sent toTeamcenter.

globalservices.tceng2omfg.OmfgDateOutFormat

Specifies the format of date values sent from OracleManufacturing.

globalservices.tceng2omfg.OmfgDateInFormat

Specifies the format of date values sent to OracleManufacturing.

globalservices.tceng2omfg.OmfgDateTimeInFormat

Specifies the format of date and time values sent toOracle Manufacturing.

globalservices.tceng2omfg.XSLName Specifies the name of the style sheet applied to thePLM XML file to convert it to an XML businessobject.

globalservices.tceng2omfg.UpdateAttrFile

Specifies the name of the XML mapping file that listsall the attributes from Oracle Manufacturing thatcan be updated in Teamcenter.

globalservices.tceng2omfg.JNDI_NAME

Specifies the JNDI name of the connector GlobalServices uses to connect to Teamcenter.

globalservices.tceng2omfg.ORACLE_CONFIG_NAME

Specifies the name of the configuration file thatcontains the configuration data required to connectto Oracle Manufacturing.


Index

Numerics/Symbols

2 Tier Teamcenter ServerConfiguration . . . . . . . . . . . . . . . . . D-114 Tier Teamcenter ServerConfiguration . . . . . . . . . . . . . . . . . D-11

A

Action manager daemon . . . . . . . . . . . . 6-1Action Manager Service . . . . . . . . . . . . D-9Adding features . . . . . . . . . . . . . . . . . 13-2additional_applications directory . . . . . C-2advanced_installations directory . . . . . C-2Aerospace and DefenseAerospace and Defense Foundation . . D-6Aerospace and Defense Training . . . . D-6

AIWS client . . . . . . . . . . . . . . . . . . . . D-7AIXConfiguration parameters . . . . . . . . . . 3-3Daemon startup scripts . . . . . . . . . . . 6-2Kernel parameters . . . . . . . . . . . . . . . 3-3Shell limits . . . . . . . . . . . . . . . . . . . . 3-2

Apache HTTP Server . . . . . . . . . . . . . 12-33Apache Tomcat . . . . . . . . . . . . . . . . . 12-33Apple Macintosh platformsPlatform support . . . . . . . . . . . . . . . . 1-2System requirements . . . . . . . . . . 1-2–1-3

Application Interface Web Service, see AIWSclientApplication serversHTTPServerTable . . . . . . . . 12-24, 12-30Teamcenter applicationserver . . . . . . . . . . . . . . . . . 2-21–2-22

Web tier . . . . . . . . . . . . . . . . . . . . . 1-10ApplicationInstance . . . . . . . . . . . . . 12-11ApplicationInstance contextparameter . . . . . . . . . . . . . . . . . . . . . E-9As-Built . . . . . . . . . . . . . . . . . . . D-7, D-10ASP .NET State Service . . . . . . . . . . . D-10AutoCAD integration, GM Overlay . . . . D-7Automatic logon, four-tier . . . . . . . . . . . 2-6Automotive Edition . . . . . . . . . . . . . . . D-6AutonomyIDOL server . . . . . . . . . . . . . . . . . . D-6

Autonomy Intelligent Data Operating Layer(IDOL) . . . . . . . . . . . . . . . . . . . . . . . D-6

BBacking up installations . . . . . . . . . . . . 6-4Backing up Teamcenter data . . . . . . . . . 6-5BackupOracle databases . . . . . . . . . . . . . . . . 3-8

Best installation practices . . . . . . . . . . . 4-6Bounding box generation from JT . . . . . D-8Bounding box generation from NX . . . . D-8Brand Management . . . . . . . . . . . . . . D-4Business Modeler IDE . . . . . . . . . . . . D-11Client . . . . . . . . . . . . . . . . . . . . . . . D-1Digital Dashboard . . . . . . . . . . . . . D-11Four-tier server configuration . . . . . D-11Installing . . . . . . . . . . . . . . . . . . 8-1, 8-3Mapping Designer . . . . . . . . . . . . . D-11Solution . . . . . . . . . . . . . . . . . . . . . D-1Start . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Templates . . . . . . . . . . . . . . . . D-1, D-11Two-tier server configuration . . . . . D-11

Business Modeler IDE client . . . . . . . . D-1Business Modeler IDE Client . . . . . . . D-11Business Modeler Templates . . . . D-1, D-11

CCAD Part Library for Rich Client . . . . D-10CAD-BOM Alignment . . . . . . . . . . . . . D-4Cadence Allegro Library Support . . . . . D-1,D-11Cadence Support . . . . . . . . . . . . . D-1, D-11cc_integration directory . . . . . . . . . . . . C-2Certification database . . . . . . . . . . . . . . 1-1Character set, ISO8859–1 . . . . . . . . . . . 4-3Character setsISO8559-1 . . . . . . . . . . . . . . . . . . . . . 1-4UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 1-4

CIFS volume data access . . . . . . . . . . . 2-22ClearCase . . . . . . . . . . . . . . . . . . . . . D-5Client for Office . . . . . . . . . . . . . . . . D-10Client tierFour-tier . . . . . . . . . . . . . . . . . . . . . 1-10

PLM00011 C Installation on UNIX and Linux Servers Guide Index-1

Index

Two-tier . . . . . . . . . . . . . . . . . . . . . . 1-8Client, Business Modeler IDE . . . . . . D-11ClientsFCC . . . . . . . . . . . . . . . . . . . . . . . . 2-13Four-tier clients . . . . . . . . . . . . . . . . 1-10Rich client installation . . . . . . . . . . . . 2-8Thin client . . . . . . . . . . . . . . . . . . . . 2-11Two-tier clients . . . . . . . . . . . . . . . . . 1-8

Commandsinsweb . . . . . . . . . . . . . . 12-2, 16-4–16-7

Comprehensive Manufacturing Types . . D-8ConfigurationDatabases . . . . . . . . . . . . . . . . . . . . 3-17Multi-Site Collaboration . . . . . . . . . . . 6-2Multi-Site Collaboration daemons . . . . 6-4Oracle Net . . . . . . . . . . . . . . . . . . . . 3-15Teamcenter’s manufacturing processmanagement . . . . . . . . . . . . . . . . 10-1

Connector support files . . . . . . . . . . . . 12-6Consumer Packaged GoodsBrand Management . . . . . . . . . . . . . D-4CPG Materials . . . . . . . . . . . . . . . . . D-5CPG Materials for Rich Client . . . . . D-10Packaging and Artwork . . . . . . . . . . D-4

Content Management . . . . . . . . . . . . . D-4Content Management Base feature . . D-4Content Management S1000Dfeature . . . . . . . . . . . . . . . . . . . . D-6

Content Management System for RichClient . . . . . . . . . . . . . . . . . . . . D-10

Content Management installation . . . 12-12Content Management S1000D . . . . . . . D-6Content Management System for RichClient . . . . . . . . . . . . . . . . . . . . . . . D-10Context parametersApplicationInstance . . . . . . . . . 12-11, E-9global.services.proxy.password . . . . . E-10global.services.tceng2omfg.password . . . . . . . . . . E-11

global.services.teamcenter.password . . . . . . . . . . E-11

global.services.proxy.client.IPs . . . . . E-11global.services.proxy.user . . . . . . . . . E-10global.services.tceng2omfg.user . . . . . E-11global.services.teamcenter.user . . . . . E-11globalservices.OMfg.password . . . . . . E-12globalservices.OMfg.user . . . . . . . . . E-12globalservices.tceng2omfg.engdateinformat . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.engdateoutformat . . . . . . . . . . . . E-12

globalservices.tceng2omfg.JNDI_NAME . . . . . . . . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.maxobjects . . . . . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.OmfgDateInFormat . . . . . . . . . . . E-12

globalservices.tceng2omfg.OmfgDateOutFormat . . . . . . . . . . E-12

globalservices.tceng2omfg.OmfgDateTimeInFormat . . . . . . . E-12

globalservices.tceng2omfg.ORACLE_CONFIG_NAME . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.StagingDirectory . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.UpdateAttrFile . . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.XSLName . . . . . . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.url . . . . . . E-12LogFileLocation . . . . . . . . . . . . 12-11, E-9RAC.OSGi.plugin.URL.suffix . . . . . . E-11SSOAppID . . . . . . . . . . . . . . . 12-11, E-9TcGSBOSJNDI . . . . . . . . . . . . 12-11, E-9TcGSConnectorJNDI . . . . . . . . . . . . E-11TcGSDORJNDI . . . . . . . . . . . . 12-11, E-9TcGSEngJNDI . . . . . . . . . . . . . . . . . E-11TcGSEntJNDI . . . . . . . . . . . . . . . . . E-11TcGSJDBCJNDI . . . . . . . . . . 12-11, E-10TcGSMessageServerJNDI . . . . 12-11, E-10TcGSNotifierReactorJNDI . . . 12-11, E-10TcGSOMfgJNDI . . . . . . . . . . . . . . . E-11TcGSRACJNDI . . . . . . . . . . . . . . . . E-11TcGSSAPJNDI . . . . . . . . . . . . . . . . E-11TcGSSOAJNDI . . . . . . . . . . . . . . . . E-11TeamcenterConnectorJNDI . . . . . . . . E-11

CORP item creation fails . . . . . . . . . . . B-4Corporate serverFeatures . . . . . . . . . . . . . . . . . . D-1–D-2Installing . . . . . . . . . . . . . . . . . . . . . 5-5

CPG Materials . . . . . . . . . . . . . . . . . . D-5CPG Materials for Rich Client . . . . . . D-10Customization for eM-ServerIntegration . . . . . . . . . . . . . . . . . . . . D-8Customization for Process SimulaterIntegration . . . . . . . . . . . . . . . . . . . . D-8customScripts.log file . . . . . . . . . . . . . . 3-19

D

Database Configuration Assistant . . . 2-21,3-17Database Configuration for DPV . . . . . D-7Database daemonsInstallation . . . . . . . . . . . . . . . . . . . D-8Starting manually . . . . . . . . . . . . . . . 6-1

Index-2 Installation on UNIX and Linux Servers Guide PLM00011 C

Index

Database Daemons . . . . . . . . . . . . . . . D-8Action Manager Service . . . . . . . . . . D-9Subscription Manager Service . . . . . . D-9Task Manager Service . . . . . . . . . . . D-8Tesselation Manager Service . . . . . . . D-9

Database services . . . . . . . . . . . . . . . . D-8DatabasesAdding data directory toinstallation . . . . . . . . . . . . . . . . . 13-2

Adding database to installation . . . . . 13-3Data imports . . . . . . . . . . . . . . . . . . 3-10Multiple database accessFour-tier rich clients . . . . . . . . . 13-4Overview . . . . . . . . . . . . . . . . . 13-4

RDV . . . . . . . . . . . . . . . . . . . . . . . . 2-21Site planning . . . . . . . . . . . . . . . . . . 2-21tceng_unpopulate_db.sql script . . . . . B-10Templates . . . . . . . . . . . . . . . . 2-21, 3-17Unpopulating in Oracle . . . . . . . . . . B-10

dbscripts directory . . . . . . . . . . . . . . . 3-17dbshut utility . . . . . . . . . . . . . . . . . . . . 3-9Destination directories . . . . . . . . . . . . . 4-3Digital Dashboard . . . . . . . . . . . . . . . D-11DirectoriesWEB_ROOT . . . . . . . . . . . . . . . . . . 12-2Web_tier . . . . . . . . 12-2–12-3, 12-9, 12-12

Dispatcher . . . . . . . . . . . . . . . . . . . . . D-1Dispatcher Client . . . . . . . . . . . . . . . D-6Dispatcher Client for Rich Client . . . . D-9Dispatcher Server . . . . . . . . . . . . . . D-6

Dispatcher Client for Rich Client . . . . . D-9Dispatcher Server . . . . . . . . . . . . . . . . D-6Installation . . . . . . . . . . . . . . . . . . . D-1

dist_server.jar file . . . . . . . . . . . . . . . 12-35Distributed services manager, see IDSMserver and IDSM proxy serverDistribution media . . . . . . . . . . . . . . . C-1Distribution serverAdding Web components . . . . . . . . . 12-35Changing contents . . . . . . . . . . . . . 12-35Installation . . . . . . . . . . . . . 12-18–12-19Patching Web components . . . . . . . . . 16-6Starting . . . . . . . . . . . . . . . . . . . . 12-34Stopping . . . . . . . . . . . . . . . . . . . . 12-34

Distribution server instanceInstallation . . . . . . . . . . . . . 12-19, 12-28Web deployment . . . . . . . . . . . . . . 12-31

Documentation distribution image . . . . C-1DPVDatabase configuration . . . . . . . . . . . D-7GM Customization . . . . . . . . . . . . . . D-7

ds_manifest.mf file . . . . . . . . . . . . . . 12-30

EeBOP reports Customization . . . . . . . . D-8ECAD design managementCadence Support . . . . . . . . . . . . . . D-11Mentor Support . . . . . . . . . . . . . . . D-11PADS Support . . . . . . . . . . . . . . . . D-11

ECAD library managementCadence Allegro Library Support . . . D-11Mentor Board Station LibrarySupport . . . . . . . . . . . . . . . . . . D-11

Mentor PADS Library Support . . . . D-11Mentor Support . . . . . . . . . . . . . . . D-11

ECAD Part Library Management . . . . . D-6EDADataset types . . . . . . . . . . . . . . . . . D-5Server support . . . . . . . . . . . . . . . . . D-5Standalone client . . . . . . . . . . . . . . . D-1

EDA for Rich Client . . . . . . . . . . . . . D-10EDA Server Support . . . . . . . . . . . . . . D-5EDA Stand-alone Client . . . . . . . . . . D-11eIntegrator Admin . . . . . . . . . . . . . . . D-3Embedded Software SolutionsEmbedded Software Design DataManagement . . . . . . . . . . . . . . . . D-6

Embedded Software Design DataManagement for Rich Client . . . . D-10

ESS . . . . . . . . . . . . . . . . . . . . . . . . D-7Embedded Software Solutions for RichClient . . . . . . . . . . . . . . . . . . . . . . . D-10Embedded viewer . . . . . . . . . . . . . . . D-10Embedded visualization for richclient . . . . . . . . . . . . . . . . . . . . . . . D-10EMPS – ECAD Translation . . . . . . . . . D-6EMPS - Foundation . . . . . . . . . . . . . . . D-6Enterprise tier . . . . . . . . . . . . . . . . . . 1-10Environment variablesLANG . . . . . . . . . . . . . . . . . . . . . . . 14-2LC_ALL . . . . . . . . . . . . . . . . . . . . . 14-2ORACLE_HOME . . . . . . . . . . . . . . . . 3-9PATH . . . . . . . . . . . . . . . . . . . . . 3-8–3-9TC_DATA . . . . . . . . . . . . . . . . . . 2-2, 5-7TC_ROOT . . . . . . . . . . . . . . 2-2, 4-5, 5-6TNS_ADMIN . . . . . . . . . . . . . . . . . . 3-15

ERP Connect Toolkit . . . . . . . . . . . . . . D-5Error log files . . . . . . . . . . . . . . . . . . . 3-18Error logs . . . . . . . . . . . . . . . . . . . . . . B-1Error messages . . . . . . . . . . . . . . . . . . B-2ESS Base . . . . . . . . . . . . . . . . . . . . . . D-7ESS Processor . . . . . . . . . . . . . . . . . . . D-7ESS Software . . . . . . . . . . . . . . . . . . . D-7ExportOracle databases . . . . . . . . . . . . . . . . 3-8


Index

F

FCC . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Features2 Tier Teamcenter ServerConfiguration . . . . . . . . . . . . . . D-11

4 Tier Teamcenter ServerConfiguration . . . . . . . . . . . . . . D-11

Add-Ons, Rich Client . . . . . . . . . . . . D-9Aerospace and Defense Foundation . . D-6Aerospace and Defense Training . . . . D-6ASP .NET State Service . . . . . . . . . D-10Bounding box generation from JT . . . D-8Bounding box generation from NX . . . D-8Brand Management . . . . . . . . . . . . . D-4Business Modeler IDE . . . . . . . . . . D-11Business Modeler IDE client . . . . . . . D-1Business Modeler Templates . . . . . . . D-1CAD Part Library for Rich Client . . D-10CAD-BOM Alignment . . . . . . . . . . . . D-4Cadence Allegro Library Support . . . . D-1,D-11

Cadence Support . . . . . . . . . . . D-1, D-11Client, Business Modeler IDE . . . . . D-11Comprehensive ManufacturingTypes . . . . . . . . . . . . . . . . . . . . . D-8

Configure AutoCAD Integration for GMOverlay . . . . . . . . . . . . . . . . . . . D-7

Content Management Base . . . . . . . . D-4Content Management S1000D . . . . . . D-6Content Management System for RichClient . . . . . . . . . . . . . . . . . . . . D-10

Corporate server . . . . . . . . . . . . . . . D-1CPG Materials . . . . . . . . . . . . . . . . . D-5CPG Materials for Rich Client . . . . . D-10Customization for eM-ServerIntegration . . . . . . . . . . . . . . . . . D-8

Customization for Process SimulateIntegration . . . . . . . . . . . . . . . . . D-8

Database Configuration for DPV . . . . D-7Database Daemons . . . . . . . . . . . . . D-8Action Manager Service . . . . . . . D-9Subscription Manager Service . . . D-9Task Manager Service . . . . . . . . D-8Tesselation Manager Service . . . . D-9

Digital Dashboard . . . . . . . . . . . . . D-11Dispatcher . . . . . . . . . . . . . . . . . . . D-6Dispatcher Client . . . . . . . . . . . . . . . D-6Dispatcher Client for Rich Client . . . . D-9Dispatcher Server . . . . . . . . . . . . . . D-1eBOP reports Customization . . . . . . . D-8ECAD Design Management . . . . . . D-11ECAD Library Management . . . . . . D-11ECAD Part Library Management . . . D-6

EDA for Rich Client . . . . . . . . . . . . D-10EDA Server Support . . . . . . . . . . . . D-5EDA Stand-alone Client . . . . . . . . . D-11EDA Standalone Client . . . . . . . . . . D-1Embedded Software Design DataManagement . . . . . . . . . . . . . . . . D-6

Embedded Software Design DataManagement for Rich Client . . . . D-10

Embedded Software Manager forFoundation . . . . . . . . . . . . . . . . . D-7

Embedded Software Manager for RichClient . . . . . . . . . . . . . . . . . . . . D-10

EMPS – ECAD Translation . . . . . . . . D-6EMPS - Foundation . . . . . . . . . . . . . D-6ERP Connect . . . . . . . . . . . . . . . . . . D-5ESS . . . . . . . . . . . . . . . . . . . . D-7, D-10ESS Base . . . . . . . . . . . . . . . . . . . . D-7ESS Processor . . . . . . . . . . . . . . . . . D-7ESS Software . . . . . . . . . . . . . . . . . D-7Extensions for Microsoft Office . . . . D-10Finished Product Management . . . . . D-3FMS Server Cache . . . . . . . . . . . D-1–D-3Full Text Search Engine . . . . . . . . . . D-6Global Services . . . . . . . . . . . . . . . . D-1Global Services Adapter . . . . . . . . . . D-3Global Services Framework . . . . D-1, D-4Global Services Monitoring GUI for RichClient . . . . . . . . . . . . . . . . . . . . D-10

Global Services Preferences . . . . D-1, D-6GM Customization for DPV . . . . . . . . D-7GM Overlay . . . . . . . . . . . . . . . . . . . D-6GM Overlay for Rich Client . . . . . . . D-10GM PAD/TWP Customization . . . . . . D-8Hierarchical Storage Management(HSM) . . . . . . . . . . . . . . . . . . . . D-5

Install Libraries for AIWS Client . . . . D-7Install Libraries for ResourceBrowser . . . . . . . . . . . . . . . . . . . D-8

J2EE Based Server Manager . . . D-1, D-3Log Manager Query Service . . . . D-1, D-3Maintenance, Repair, and Overhaul . . D-7Manufacturing ProcessManagement . . . . . . . . . . . . . . . . D-8

Mapping Designer . . . . . . . . . . . . . D-11Mentor Board Station LibrarySupport . . . . . . . . . . . . . . . D-1, D-11

Mentor Expedition LibrarySupport . . . . . . . . . . . . . . . D-1, D-11

Mentor PADS Library Support . . . . . D-1,D-11

Mentor Support . . . . . . . . . . . . D-1, D-11Microsoft OfficeClient for Office . . . . . . . . . . . . D-10


Index

Extensions forMicrosoft Office . . D-10Microsoft Office client . . . . . . . . . . . D-10MRO As-Built . . . . . . . . . . . . . D-7, D-10Multi-Site Collaboration . . . . . . . . . . D-9Multisite Collaboration IDSMService . . . . . . . . . . . . . . . . . D-1, D-9

Multisite Collaboration ODSService . . . . . . . . . . . . . . . . . D-1, D-9

.NET Based Server Manager . . . . . . . D-3NX Manager for Rich Client . . . . . . D-10NX UG Integration . . . . . . . . . . D-1, D-3Office Client for Microsoft Office . . . D-10Online Help . . . . . . . . . . . . . . . . . . . D-4Oracle Manufacturing Integration . . . D-3Packaging and Artwork . . . . . . . . . . D-4PAD/TWP Customization . . . . . . . . . D-8PADS Support . . . . . . . . . . . . . D-1, D-11QPL for Repeatable DigitalValidation . . . . . . . . . . . . . . . . . . D-7

Render Document for Rich Client . . . D-9Rich Client . . . . . . . . . . . . . . . . . . . D-9Rich Client (Lite Edition) . . . . . . . . . D-9Rich Client (Shared DiskDeployment) . . . . . . . . . . . . . . . . D-9

Rich Client 2-tier . . . . . . . . . . . . . . . D-9Rich Client 4-tier . . . . . . . . . . . . . . . D-9Rich Client Add-Ons . . . . . . . . . . . . D-9Rich Client, Dispatcher Client . . . . . . D-9Sample Files . . . . . . . . . . . . . . . . . . D-3SCM ClearCase for Foundation . . . . . D-5SCM ClearCase for Rich Client . . . . D-10Single Sign-on for Rich Client . . . . . D-10Spatial Search . . . . . . . . . . . . . . . . . D-8Specification Manager . . . . . . . . . . . D-5Specification Manager for RichClient . . . . . . . . . . . . . . . . . . . . D-10

Stand-alone Applications . . . . . . . . D-11Structure Search . . . . . . . . . . . . . . . D-8Teamcenter Automotive Edition . . . . D-6Teamcenter Corporate Server . . . . . . D-2Teamcenter Extensions for MicrosoftOffice . . . . . . . . . . . . . . . . . . . . D-10

Teamcenter File Services . . . . . . D-1–D-2Teamcenter for Reporting andAnalytics . . . . . . . . . . . . . . . . . . D-5

Teamcenter Foundation . . . . . . . D-1–D-2Teamcenter Linking . . . . . . . . . . . . . D-5Teamcenter Manufacturing . . . . . . . . D-8Teamcenter Rich Client . . . . . . . . . . D-9Teamcenter Rich Client 2-tier . . . . . . D-2Teamcenter Rich Client 4-tier . . . . . . D-2Teamcenter Security Services . . . . . . D-4Teamcenter Visualization . . . . . . . . . D-5

Teamcenter Visualization 8 (Embedded) forRich Client . . . . . . . . . . . . . . . . D-10

Teamcenter Visualization 8 (Stand-alone)for Rich Client . . . . . . . . . . . . . D-10

Teamcenter Web Tier . . . . . . . . . . . D-10Tecnomatix . . . . . . . . . . . . . . . . . . . D-8Trueshape generation from JT . . . . . D-8Vendor Management . . . . . . . . . . . . D-4Vendor Management for RichClient . . . . . . . . . . . . . . . . . . . . D-10

Web Tier for .NET . . . . . . . . . . . . . D-11Wire Harness Configuration . . . . . . . D-4Wire Harness Configuration in GMOverlay . . . . . . . . . . . . . . . . . . . D-7

Workflow to Scheduling Integration . . D-3File Management System . . . . . . . . . . 2-15Installation . . . . . . . . . . . . . . . . D-1–D-3Installation overview . . . . . . . . . . . . 2-11Volume server . . . . . . . . . . . . . . . . . D-2

File security . . . . . . . . . . . . . . . . . . . . 2-15FilesINSTALL_TCWEB.TZ . . . . . . . . . . . 12-2jakarta-regexp-1.3.jar . . . . . . . . . . . . B-4jCO.jar . . . . . . . . . . . . . . . . . . . . . . 12-9jRFC12.dll . . . . . . . . . . . . . . . . . . . . 12-9libjRFC12.so . . . . . . . . . . . . . . . . . . 12-9librfc32.dll . . . . . . . . . . . . . . . . . . . . 12-9librfccm.so . . . . . . . . . . . . . . . . . . . . 12-9mti.jar . . . . . . . . . . . . . . . . . . . . . . 12-7mtiems.jar . . . . . . . . . . . . . . . . . . . . 12-7ojdbc14.jar . . . . . . . . . . . . . . . . . . . 12-9teamcenter.ini . . . . . . . . . . . . . . . . . 14-1

Finished Product Management . . . . . . . D-3FMSFCC . . . . . . . . . . . . . . . . . . . . . . . . 2-13FSC . . . . . . . . . . . . . . . . . . . . . . . . 2-12Master configuration file . . . . . . . . . . 2-13See File Management System . . . . . . 2-11

FMS server cache . . . . . . . . . . . . . . . . D-2Fms_BootStrap_Urls preference . . . . . . . 5-4Four-tier architectureInstallation overview . . . . . . . . . . . . . 2-5Overview . . . . . . . . . . . . . . . . . . . . . 1-10Troubleshooting deployment . . . . . . . B-5

FSCInstallation overview . . . . . . . . . . . . 2-12Transient server . . . . . . . . . . . . . . . 2-12

Full Text Search Engine . . . . . . . . . . . D-6

G

GDIS database configuration . . . . . . . . D-7genius2mrm_copy_files.uclscript . . . . . . . . . . . . . . . . . . . . 10-6–10-7


Index

Genius4000 data migration . . . . . . . . . 10-6Global Services . . . . . . . . . . . . . . 2-17, D-3Features . . . . . . . . . . . . . . . . . . . . . D-1

Global Services Adapter . . . . . . . . . . . . D-3Global Services Framework . . . . . . D-1, D-4Global Services installation . . . . . . . . . 12-9Global Services Monitoring GUI for RichClient . . . . . . . . . . . . . . . . . . . . . . . D-10Global Services Preferences . . . . . . D-1, D-6global.services.tceng2omfg.passwordparameter . . . . . . . . . . . . . . . . . . . . . E-11global.services.teamcenter.passwordparameter . . . . . . . . . . . . . . . . . . . . . E-11global.services.proxy.client.IPs contextparameter . . . . . . . . . . . . . . . . . . . . . E-11global.services.proxy.password contextparameter . . . . . . . . . . . . . . . . . . . . . E-10global.services.proxy.user contextparameter . . . . . . . . . . . . . . . . . . . . . E-10global.services.tceng2omfg.userparameter . . . . . . . . . . . . . . . . . . . . . E-11global.services.teamcenter.userparameter . . . . . . . . . . . . . . . . . . . . . E-11globalservices.OMfg.passwordparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.OMfg.user parameter . . . E-12globalservices.tceng2omfg.engdateinformatparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.engdateoutformatparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.JNDI_NAMEparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.maxobjectsparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.OmfgDateInFormatparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.OmfgDateOutFormat parameter . . . . . E-12globalservices.tceng2omfg.OmfgDateTimeInFormatparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.ORACLE_CONFIG_NAME parameter . . . . . . . . E-12globalservices.tceng2omfg.StagingDirectoryparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.UpdateAttrFileparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.XSLNameparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.urlparameter . . . . . . . . . . . . . . . . . . . . . E-12GM Customization for DPV . . . . . . . . . D-7GM Overlay . . . . . . . . . . . . . . . . . . . . D-6

CORP item creation fails . . . . . . . . . B-4GM Overlay for Rich Client . . . . . . . . D-10GM Overlay, AutoCAD integration . . . . D-7GM Overlay, Wire HarnessConfiguration . . . . . . . . . . . . . . . . . . D-7GM PAD/TWP Customization . . . . . . . . D-8

H

Hebrew language . . . . . . . . . . . . . . . . 14-5Heterogeneous network environment . . 2-22Hewlett-Packard HP-UX, Javaconfiguration . . . . . . . . . . . . . . . . . . . . 1-4Hierarchical Storage Management(HSM) . . . . . . . . . . . . . . . . . . . . . . . D-5Homogeneous network environment . . . 2-21HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Kernel parameter requirements . . . . . 3-3

HP-UX, kernel parameters . . . . . . . . . . B-8HSM . . . . . . . . . . . . . . . . . . . . . . . . . D-5HTML pages . . . . . . . . . . . . . . . . . . . 12-19

I

ICD files, copyingGlobal Services . . . . . . . . . . . . . . . . 12-9Teamcenter Web tier . . . . . . . . . . . . 12-3

IDOL . . . . . . . . . . . . . . . . . . . . . . . . . D-6IDOL server, Autonomy . . . . . . . . . . . . D-6IDSM proxy server . . . . . . . . . . . . . . . . 2-4IDSM server . . . . . . . . . . . . . . . . . . . . . 2-3IDSM Service . . . . . . . . . . . . . . . . . . . D-9IDSM_permitted_sites preference . . . . . . 6-3images directory . . . . . . . . . . . . . . . . 12-31Imports . . . . . . . . . . . . . . . . . . . . . . . 3-10infodba . . . . . . . . . . . . . . . . . . . . . 1-4, 2-22Install images for connectors . . . . . . . . 12-6Install Libraries for AIWS Client . . . . . D-7INSTALL_TCWEB.EXE file . . . . . . . . . 12-2InstallationBest practices . . . . . . . . . . . . . . . . . . 4-6Creating a configuration . . . . . . . . . . 13-1Distribution server . . . . . . . . . . . . . 12-19Distribution server instance . . . . . . 12-28Modifying a configuration . . . . . . . . . 13-2Oracle . . . . . . . . . . . . . . . . . . . 2-21, 3-10Over-the-Web . . . . . . . . . . . . . 1-8, 12-19Rich client instance . . . . . . . . . . . . 12-21Silent . . . . . . . . . . . . . . . . . . . . . . . 15-1Teamcenter File Services . . . . . . . . . . 4-4Teamcenter servers . . . . . . . . . . . . . . 5-1Using TEM . . . . . . . . . . . . . . . 1-8, 12-19Web Application Manager . . . . . . . . . 12-2


Index

installed_programs.dat file . . . . . . . . . . . 4-6installed.html file . . . . . . . . . . . . . . . 12-31installfailed.html file . . . . . . . . . . . . . 12-31InstallingBusiness Modeler IDE . . . . . . . . . 8-1, 8-3Templates . . . . . . . . . . . . . . . . . . . . . 9-1

installing.html file . . . . . . . . . . . . . . . 12-31insweb command . . . . . . . . . . . . . . . . 12-2,12-19, 12-28, 12-35, 16-4–16-7IntegrationsClearCase . . . . . . . . . . . . . . . . . . . D-10Microsoft Office . . . . . . . . . . . . . . . D-10SCM ClearCase . . . . . . . . . . . . . . . D-10

Internationalizationweb_gen_xml utility . . . . . . . . . . . . . 14-3web_gen_xml.dat file . . . . . . . . . . . . 14-3webstrings.xml file . . . . . . . . . . . . . . 14-3

ISO8559-1 character set . . . . . . . . . . . . 1-4ISO8559-1 mode . . . . . . . . . . . . . . . . . . 4-4ISO8859–1 character set . . . . . . . . . . . . 4-3

J

J2EE based server manager . . . . . . . . 1-10,2-2, 5-6, 7-5J2EE Based Server Manager . . . . . D-1, D-3jakarta-regexp-1.3.jar file . . . . . . . . . . . B-4Java . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Java Runtime Environment . . . . . . . . . 12-2JBoss Cache TreeCache . . . . . . . . . . . . 7-1,12-5, 13-7, E-8jCO.jar file . . . . . . . . . . . . . . . . . . . . . 12-9jRFC12.dll file . . . . . . . . . . . . . . . . . . 12-9

K

Kernel parameters . . . . . . . . . . . . 3-2, B-8

L

LANG variable . . . . . . . . . . . . . . . . . . 14-2launcherror.html file . . . . . . . . . . . . . 12-31LaunchingBusiness Modeler IDE . . . . . . . . . . . . 8-6

LC_ALL variable . . . . . . . . . . . . . . . . 14-2libjRFC12.so file . . . . . . . . . . . . . . . . . 12-9Libraries . . . . . . . . . . . . . . . . . . . . . . D-7librfc32.dll file . . . . . . . . . . . . . . . . . . 12-9librfccm.so file . . . . . . . . . . . . . . . . . . . 12-9Licensing levelAuthor . . . . . . . . . . . . . . . . . . . . . . . 4-1Consumer . . . . . . . . . . . . . . . . . . . . . 4-1

Linux considerations . . . . . . . . . . . . . . . 1-4Listener processes . . . . . . . . . . 3-8–3-9, 3-15

listener.ora file . . . . . . . . . . . . . . . 3-9, 3-15Locale setting . . . . . . . . . . . . . . . . . . . 14-1Locale setting, overriding . . . . . . . . . . . 14-1LocalizationConverting to Unicode . . . . . . . . . . . 14-5Hebrew language . . . . . . . . . . . . . . . 14-5Rich client . . . . . . . . . . . . . . . . . . . . 14-5Thin client . . . . . . . . . . . . . . . . . . . . 14-5

localization directory . . . . . . . . . . . . . . C-2Log Manager Query Service . . . . . . . . . D-1Installation . . . . . . . . . . . . . . . . D-1, D-3

LogFileLocation . . . . . . . . . . . . . . . . 12-11LogFileLocation context parameter . . . . E-9Logon, automatic . . . . . . . . . . . . . . . . . 2-6

M

Macintosh platformsPlatform support . . . . . . . . . . . . . . . . 1-2System requirements . . . . . . . . . . 1-2–1-3

Maintenance packs . . . . . . . . . . . . . . . 16-1Maintenance, Repair, and Overhaul . . . D-7Manifest file . . . . . . . . . . . . . . . . . . . 12-30Manufacturing content kit . . . . . . . . . . 10-1Manufacturing Process Management . . D-8Manufacturing Tooling Library . . . . . . 10-2Mapping Designer . . . . . . . . . . . . . . . D-11Master configuration file . . . . . . . . . . . 2-13Media, distribution . . . . . . . . . . . . . . . C-1Memory management . . . . . . . . . . . . . . 8-5Mentor Board Station LibrarySupport . . . . . . . . . . . . . . . . . . D-1, D-11Mentor Expedition Library support . . D-11Mentor Expedition Library Support . . . D-1Mentor PADS Library Support . . . . . . . D-1Mentor support . . . . . . . . . . . . . . . . . D-11Mentor Support . . . . . . . . . . . . . . . . . D-1Microsoft Office client . . . . . . . . . . . . D-10Microsoft Office extensions . . . . . . . . . D-10Migration, Genius4000 data . . . . . . . . . 10-6MRO As-Built . . . . . . . . . . . . . . . D-7, D-10mti.jar file . . . . . . . . . . . . . . . . . . . . . 12-7mtiems.jar file . . . . . . . . . . . . . . . . . . 12-7Multi-Site Collaboration . . . . . . . . . . . D-9Configuring daemons . . . . . . . . . . . . . 6-4IDSM service . . . . . . . . . . . . . . . . . . D-1Installation . . . . . . . . . . . . . . . . . . . D-1Local disk installation . . . . . . . . . . . . 4-3ODS service . . . . . . . . . . . . . . . . . . . D-1Postinstallation tasks . . . . . . . . . . . . . 6-2Proxy server . . . . . . . . . . . . . . . . . . D-1Wide area networks . . . . . . . . . . . . . . 6-2

Multi-site services . . . . . . . . . . . . . . . . D-9Multiple database access


Index

Four-tier rich clients . . . . . . . . . . . . . 13-4Overview . . . . . . . . . . . . . . . . . . . . . 13-4

Multiple EAR file support . . . . . . . . . 12-17

N

native2ascii utility . . . . . . . . . . . . . . . 14-6.NET based server manager . . . . . . . . . 1-10.NET Based Server ManagerNET Based Server Manager . . . . . . . D-3.NET State Service . . . . . . . . . . . . . . D-10NET Web tier . . . . . . . . . . . . . . . . . . D-11ASP .NET State Service . . . . . . . . . D-10

.NET Web tier . . . . . . . . . . . . . . . . . . D-11ASP .NET State Service . . . . . . . . . D-10Server manager . . . . . . . . . . . . . . . . 1-10Windows . . . . . . . . . . . . . . . . . . . . . 1-10

Network FoldersDescription . . . . . . . . . . . . . . . . . . . . 1-8

Network Information Services . . . . . . . . 6-1NetworksClient installation . . . . . . . . . . . . . . 2-22Heterogeneous networkenvironment . . . . . . . . . . . . . . . . 2-22

Homogeneous networkenvironment . . . . . . . . . . . . . . . . 2-21

Site planning . . . . . . . . . . . . . . . . . . . 2-1NFS volume data access . . . . . . . . . . . 2-22NIS Plus . . . . . . . . . . . . . . . . . . . . . . . 6-1NX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5NX Manager for Rich Client . . . . . . . . D-10NX UG Integration . . . . . . . . . . . . D-1, D-3

O

Object directory services, see ODS server andODS proxy serverODS proxy server . . . . . . . . . . . . . . . . . 2-3ODS server . . . . . . . . . . . . . . . . . . . . . . 2-3ODS Service . . . . . . . . . . . . . . . . . . . . D-9ODS_permitted_sites preference . . . . . . . 6-3ODS_searchable_sites preference . . . . . . 6-3ODS_site preference . . . . . . . . . . . . . . . 6-3ojdbc14.jar file . . . . . . . . . . . . . . . . . . 12-9Online help . . . . . . . . . . . . . . . . . . . . . 12-2Distribution image . . . . . . . . . . . . . . C-2File access . . . . . . . . . . . . . . . . . . . . 2-19Installation . . . . . . . . . . . . . . . 12-4, D-4Installation alternatives . . . . . . . . . . 2-18Over-the-Web access . . . . . . . . . . . . . 2-19Rich client . . . . . . . . . . . . . . . . . . . . 2-19tchelp.jar file . . . . . . . . 5-1, 5-8, 12-4, D-4Thin client . . . . . . . . . . . . . . . . . . . . 2-18Troubleshooting . . . . . . . . . . . . . . . . B-2

Online Help . . . . . . . . . . . . . . . . . . . . D-4Operating system accounts . . . . . . 1-4, 2-22Operating system support . . . . . . . . . . . 1-1OracleData imports . . . . . . . . . . . . . . . . . . 3-10Database Configuration Assistant . . 2-21,3-17

Database creation . . . . . . . . . . . . . . 3-17Database export . . . . . . . . . . . . . . . . . 3-8Database planning . . . . . . . . . . . . . . 2-21Database upgrades . . . . . . . . . . . 3-8, 3-10Installation . . . . . . . . . . . . . . . 2-21, 3-10Kernel parameters . . . . . . . . . . . . . . . 3-2Listener processes . . . . . . . . 3-8–3-9, 3-15Net configuration . . . . . . . . . . . . . . . 3-15oerr utility . . . . . . . . . . . . . . . . . . . . B-8Required version . . . . . . . . . . . . 3-16, 5-7Semaphore resources . . . . . . . . . . . . . 3-2Shared memory resources . . . . . . . . . . 3-2Site planning . . . . . . . . . . . . . . . . . . 2-21Software distribution image . . . . . . . C-1Uninstallation . . . . . . . . . . . . . . . . . 18-2Unpopulating database . . . . . . . . . . B-10

Oracle Manufacturing Integration . . . . D-3Oracle Net Assistant . . . . . . . . . . . . . . 3-15ORACLE_HOME environmentvariable . . . . . . . . . . . . . . . . . . . . . . . 3-9oratab utility . . . . . . . . . . . . . . . . . . . . 3-9otw_installer.jar file . . . . . . . . . . . . . . 12-31otw.html file . . . . . . . . . . . . . . . . . . . 12-32Over-the-Web Installer . . . . . . . . . . . 12-19,12-22–12-23, 12-29, 12-31, 16-4–16-6Over-the-Web rich client . . . . . . . . . . 12-18

P

Packaging and Artwork . . . . . . . . . . . . D-4PAD/TWP Customization . . . . . . . . . . . D-8PADS library support . . . . . . . . . . . . D-11PADS Support . . . . . . . . . . . . . . D-1, D-11Parametersglobal.services.proxy.service.URL . . . E-10Kernel . . . . . . . . . . . . . . . . . . . . . . B-8Web tier . . . . . . . . . . . . . . . . . . . . . E-1

Patches . . . . . . . . . . . . . . . . . . . . . . . 16-1Patching rich clientDescribed . . . . . . . . . . . . . . . . . . . . 16-3Silently . . . . . . . . . . . . . . . . . . . . . . 16-4Using Over-the-Web Installer . . . . . . 16-4

Patching Teamcenter’s lifecyclevisualization . . . . . . . . . . . . . . . . . . . 16-5Patching the server . . . . . . . . . . . . . . . 16-2Patching thin client . . . . . . . . . . . . . . . 16-7PATH environment variable . . . . . . . 3-8–3-9


Index

Platform support . . . . . . . . . . . . . . . . . . 1-1POM transmit schema files . . . . . . . . . . 6-3portal directory . . . . . . . . . . . . . . . . . . C-2portal_localization.jar file . . . . . . . . . . 14-5portalHelpPage property . . . . . . . . . . . B-2Postinstallation tasks . . . . . . . . . . . . . . 6-1Postupgrade tasks . . . . . . . . . . . . . . . . . 6-1PreferencesFms_BootStrap_Urls . . . . . . . . . . . . . 5-4IDSM_permitted_sites . . . . . . . . . . . . 6-3ODS_permitted_sites . . . . . . . . . . . . . 6-3ODS_searchable_sites . . . . . . . . . . . . 6-3ODS_site . . . . . . . . . . . . . . . . . . . . . . 6-3TC_publishable_classes . . . . . . . . . . . 6-3TC_Security_Level . . . . . . . . . . . . . . 2-15TC_transfer_area . . . . . . . . . . . . . . . . 6-3WEB_core_help_server . . . 2-19–2-20, B-2WEB_default_site_deployed_app_name . . . . . . . . . . . . . . . . . . . . . B-3

WEB_help_server . . . . . . 2-19–2-20, B-2Preinstallation tasks . . . . . . . . . . . . . . . 4-1Prerequisite software . . . . . . . . . . . . . . 1-1PrerequisitesCharacter set . . . . . . . . . . . . . . . . . . . 4-3GM Overlay . . . . . . . . . . . . . . . . . . . . 4-3

Problem Reports (PRs) . . . . . . . . . . . . . 16-8ProgramsWeb Application Manager . . . . . 16-4–16-7

Properties, portalHelpPage . . . . . . . . . B-2Proxy WAR file (WebLogic) . . . . . 12-6, 12-13

Q

QPL for Repeatable Digital Validation . . D-7QPL server . . . . . . . . . . . . . . . . . . . . . . 2-4

R

RAC.OSGi.plugin.URL.suffix contextparameter . . . . . . . . . . . . . . . . . . . . . E-11rc.ugs file . . . . . . . . . . . . . . . . . . . . . . . 6-2rc.ugs.actionmgrd script . . . . . . . . . . . . . 6-1rc.ugs.subscriptionmgrd script . . . . . . . . 6-2rc.ugs.task_monitor script . . . . . . . . . . . 6-2RDVDatabase instance . . . . . . . . . . . . . . 2-21QPL server . . . . . . . . . . . . . . . . . . . . 2-4

README file . . . . . . . . . . . . . . . . . . . 16-8Remote Method Invocation . . . . 12-21, 12-34Removing features . . . . . . . . . . . . . . . 13-2Render Document for Rich Client . . . . . D-9Render ManagerInstallation . . . . . . . . . . . . . . . . . . . D-9Required features . . . . . . . . . . . . . . D-9

Repeatable Digital Validation . . . . . . . . D-7RequirementsDatabase . . . . . . . . . . . . . . . . . . . . . . 1-1Java . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Operating systems . . . . . . . . . . . . . . . 1-1

Resource Browser, libraries . . . . . . . . . D-8Resource Manager, Genius4000 datamigration . . . . . . . . . . . . . . . . . . . . . 10-6Resource tierFour-tier . . . . . . . . . . . . . . . . . . . . . 1-11Two-tier . . . . . . . . . . . . . . . . . . . . . . 1-8

Rich clientDeployment over the Web . . . . . . . . 12-18Description . . . . . . . . . . . . . . . . . . . . 1-7Four-tier . . . . . . . . . . . . . . . . . . D-2, D-9Installing patches . . . . . . . . . . . . . . 16-3Language display configuration . . . . . 14-1Localization . . . . . . . . . . . . . . . . . . . 14-5Online help . . . . . . . . . . . . . . . 2-19, B-2Overview . . . . . . . . . . . . . . . . . . . . . . 1-7Two-tier . . . . . . . . . . . . . . . . . . D-2, D-9

Rich Client (Lite Edition) . . . . . . . . . . . D-9Rich Client (Shared Disk Deployment) . . D-9Rich Client Add-Ons . . . . . . . . . . . . . . D-9Rich client distribution server, seeDistributionserverRich client distribution server instance, seeDistribution server instanceRich client instanceDeployment . . . . . . . . . . . . . . . . . . 12-31Installation . . . . . . . . . . . . . . . . . . 12-21

Rich client instance, four-tier . . . . . . . 12-28Rich client solutions, patching . . . . . . . 16-3RMI registryPort number . . . . . . . . . . . . . . . . . 12-21Starting . . . . . . . . . . . . . . . . . . . . 12-34Stopping . . . . . . . . . . . . . . . . . . . . 12-35

S

Sample files . . . . . . . . . . . . . . . . . . . . D-3Sample Files . . . . . . . . . . . . . . . . . . . . D-3SCM ClearCase for Foundation . . . . . . D-5SCM ClearCase for Rich Client . . . . . D-10Security Services . . . . . . . . . . . . . . . . 2-17Semaphore resources . . . . . . . . . . . . . . . 3-2ServerInstalling patches . . . . . . . . . . . . . . 16-2

Server managerJ2EE . . . . . . . . . . . . . . . . . . . . . . . D-3J2EE based . . . . . . . . . . . . . 1-10, 2-2, 5-6J2EE based, starting . . . . . . . . . . . . . 7-5.NET . . . . . . . . . . . . . . . . . . . . . . . . D-3.NET based . . . . . . . . . . . . . . . . 1-10, 2-2


Index

Server, patching . . . . . . . . . . . . . . . . . 16-2ServicesAction Manager . . . . . . . . . . . . . . . . D-9ASP .NET State Service . . . . . . . . . D-10IDSM Service . . . . . . . . . . . . . . . . . D-9ODS Service . . . . . . . . . . . . . . . . . . D-9Subscription Manager . . . . . . . . . . . D-9Task Manager . . . . . . . . . . . . . . . . . D-8Tesselation Manager . . . . . . . . . . . . D-9

Shared Disk Deployment, rich client . . . D-9Shared memory resources . . . . . . . . . . . 3-2Silent installation . . . . . . . . . . . . . . . . 15-1Silent patching . . . . . . . . . . . . . . . . . . 16-4Single sign-on for rich client . . . . . . . . D-10Site planning . . . . . . . . . . . . . . . . . . . . 2-1Software distribution image . . . . . . . . . C-1Software requirements . . . . . . . . . . . . . 1-1Application servers . . . . . . . . . . . . . 12-2Java . . . . . . . . . . . . . . . . . . . . . . . . 12-2

SolutionsBusiness Modeler IDE . . . . . . . . . . . D-1Corporate Server . . . . . . . . . . . . . . . D-1Dispatcher (Dispatcher Server) . . . . . D-1EDA Standalone Client . . . . . . . . . . D-1Global Services . . . . . . . . . . . . . . . . D-1Log Manager Query Service . . . . . . . D-1Multisite Collaboration ProxyServer . . . . . . . . . . . . . . . . . . . . D-1

Rich Client 2-tier . . . . . . . . . . . . . . . D-2Rich Client 4-tier . . . . . . . . . . . . . . . D-2Volume Server . . . . . . . . . . . . . . . . . D-2

Spatial Search . . . . . . . . . . . . . . . . . . D-8Specification Manager . . . . . . . . . . . . . D-5Specification Manager for RichClient . . . . . . . . . . . . . . . . . . . . . . . D-10SQL*Plus utility . . . . . . . . . . . . . . . . . B-10SSOAppID . . . . . . . . . . . . . . . . . . . . 12-11SSOAppID context parameter . . . . . . . E-9Stand-alone application viewer . . . . . . D-10Stand-alone ApplicationsEDA Stand-alone Client . . . . . . . . . D-11

start_rmi file . . . . . . . . . . . . . . . . . . 12-34start_server file . . . . . . . . . . . . . . . . . 12-34StartingBusiness Modeler IDE . . . . . . . . . . . . 8-6

Starting Teamcenter’s Integration forMicrosoft Office . . . . . . . . . . . . . . . . . 10-2stop_server file . . . . . . . . . . . . . . . . . 12-35Structure Search . . . . . . . . . . . . . . . . . D-8Subscription manager daemon . . . . . . . . 6-2Subscription Manager Service . . . . . . . D-9Sun ONE . . . . . . . . . . . . . . . . . . . . . 12-33Support files

mtiems.jar . . . . . . . . . . . . . . . . . . . . 12-7Oracle manufacturing connector . . . . 12-9SAP connector . . . . . . . . . . . . . . . . . 12-9Teamcenter Enterprise connector . . . 12-7

T

Task Manager Service . . . . . . . . . . . . . D-8Task monitor daemon . . . . . . . . . . . . . . 6-2TC_auto_login preference . . . . . . . . . . . 2-6TC_DATA environment variable . . . . 2-2, 5-7TC_publishable_classes preference . . . . . 6-3TC_ROOT environment variable . . . . . 2-2,4-5, 5-6TC_Security_Level preference . . . . . . . 2-15TC_transfer_area preference . . . . . . . . . 6-3tceng_unpopulate_db.sql script . . . . . . . B-10TCFS . . . . . . . . . . . . . . . . . . . . . . D-1–D-2tcfs service . . . . . . . . . . . . . . . . . . . . . . 6-1TcGSBOSJNDI . . . . . . . . . . . . . . . . . 12-11TcGSBOSJNDI context parameter . . . . E-9TcGSConnectorJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-11TcGSDORJNDI . . . . . . . . . . . . . . . . 12-11TcGSEngJNDI context parameter . . . . E-11TcGSEntJNDI context parameter . . . . . E-11TcGSJDBCJNDI . . . . . . . . . . . . . . . . 12-11TcGSJDBCJNDIl context parameter . . . E-10TcGSMessageServerJNDI . . . . . . . . . 12-11TcGSMessageServerJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-10TcGSNotifierReactorJNDI . . . . . . . . . 12-11TcGSNotifierReactorJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-10TcGSOMfgJNDI context parameter . . . E-11TcGSRACJNDI context parameter . . . . E-11TcGSSAPJNDI context parameter . . . . E-11TcGSSOAJNDI context parameter . . . . E-11TeamcenterInstallation . . . . . . . . . . . . . . . . . . . . 5-1Uninstallation . . . . . . . . . . . . . . . . . 18-1

Teamcenter application server . . . 2-21–2-22Teamcenter Automotive Edition . . . . . . D-6Teamcenter Engineering 2005/2007 . . . 12-8Teamcenter Engineering Portaldirectory . . . . . . . . . . . . . . . . . . . . . . 12-7Teamcenter Engineering V9connector . . . . . . . . . . . . . . . . . . . . . 12-7Teamcenter Enterprise connector, requiredfiles . . . . . . . . . . . . . . . . . . . . . . . . . 12-7Teamcenter Environment Manager . . . . 5-1,16-2, 16-4Installation log files . . . . . . . . . . . . . B-1


Index

Removing features . . . . . . . . . . . . . . 13-2Uninstalling . . . . . . . . . . . . . . . . . . 18-1

Teamcenter Environment Manager(TEM) . . . . . . . . . . . . . . . . . . . . . . . . 8-1Teamcenter File ServicesHeterogeneous environments . . . . . . 2-22Installation . . . . . . . . . . . . . 4-4, D-1–D-2Installation overview . . . . . . . . . . . . 2-11Local disk installation . . . . . . . . . . . . 4-3Security levels . . . . . . . . . . . . . . . . . 2-15Volume server . . . . . . . . . . . . . . . . . D-2

Teamcenter File Services server . . . . . . 2-15Teamcenter for Reporting andAnalytics . . . . . . . . . . . . . . . . . . . . . D-5Teamcenter Foundation . . . . . . . . . D-1–D-2Teamcenter Integration for NX/NX IntegrationConfiguration . . . . . . . . . . . . . . D-1, D-3Overview . . . . . . . . . . . . . . . . . . . . . . 4-5

Teamcenter Linking . . . . . . . . . . . . . . D-5Installation . . . . . . . . . . . . . . . . . . . D-5Site planning . . . . . . . . . . . . . . . . . . 2-17

Teamcenter Security Services . . . . . . . . D-4Teamcenter Visualization . . . . . . . . . . D-5Teamcenter visualization for richclient . . . . . . . . . . . . . . . . . . . . . . . D-10Teamcenter Web Tier . . . . . . . . . . . . D-10Teamcenter’s Automotive Edition–GMOverlay . . . . . . . . . . . . . . . . . . . . . . D-6Teamcenter’s Client for MicrosoftOffice . . . . . . . . . . . . . . . . . . . . . . . D-10Teamcenter’s engineering processmanagement URLs, migrating to Teamcenter8 . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14Teamcenter’s Extensions for MicrosoftOffice . . . . . . . . . . . . . . . . . . . . . . . D-10Teamcenter’s lifecycle visualization . . . . 16-5Embedded viewer . . . . . . . . . . . . . . D-10Installation . . . . . . . . . . . . . . . . . . . 2-16Stand-alone application viewer . . . . D-10

Teamcenter’s maintenance, repair, andoverhaul . . . . . . . . . . . . . . . . . . . . . . D-7Teamcenter’s manufacturing processmanagement . . . . . . . . . . . . . . . . . . . 10-1Comprehensive manufacturingtypes . . . . . . . . . . . . . . . . . . . . . D-8

Resource Browser . . . . . . . . . . . . . . D-8Sample data population . . . . . . . . . . 10-2

TeamcenterConnectorJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-11Tecnomatix . . . . . . . . . . . . . . . . . . . . . D-8TemplatesInstalling . . . . . . . . . . . . . . . . . . . . . 9-1Updating . . . . . . . . . . . . . . . . . . . . . . 9-2

Templates, database . . . . . . . . . . 2-21, 3-17Terminating Teamcenter sessions . . . . . . 6-5Tesselation Manager Service . . . . . . . . D-9Thin clientDescription . . . . . . . . . . . . . . . . . . . . 1-7FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-14Fms_BootStrap_Urls preference . . . . . 5-4Hebrew language . . . . . . . . . . . . . . . 14-5Installation . . . . . . . . . . . . . . . . . . . . 2-6Installation overview . . . . . . . . . . . . 2-11Installing patches . . . . . . . . . . . . . . 16-7Localization . . . . . . . . . . . . . . . 14-4–14-5Localized text . . . . . . . . . . . . . . . . . 14-3Migrating legacy URLs . . . . . . . . . . 12-14Online help . . . . . . . . . . . . . . . 2-18, B-2Upgrading legacy URLs . . . . . . . . . 12-14

Thin client solutions, patching . . . . . . . 16-7TNS_ADMIN environment variable . . . 3-15tnslsnr process . . . . . . . . . . . . . . . 3-9, 3-15tnsnames.ora file . . . . . . . . . . . . . . 3-9, 3-15Tomcat . . . . . . . . . . . . . . . . . . . . . . . 12-33Translation service . . . . . . . . . . . . . . . D-6Translation Services for Rich Client . . . D-9TreeCache parameters . . 7-1, 12-5, 13-7, E-8Troubleshooting . . . . . . . . . . . . . . . . . B-2Four-tier deployment . . . . . . . . . . . . B-5Online help . . . . . . . . . . . . . . . . . . . B-2Oracle . . . . . . . . . . . . . . . . . . . . . . . B-8Server installation . . . . . . . . . . . . . . B-1

Trueshape generation from JT . . . . . . . D-8Tutorials . . . . . . . . . . . . . . . . . . . . . . . 8-6Two-tier architectureDeployment . . . . . . . . . . . . . . . . . . . 1-10Installation overview . . . . . . . . . . . . . 2-4Overview . . . . . . . . . . . . . . . . . . . . . . 1-8

U

UGS_LICENSE_SERVER environmentvariable . . . . . . . . . . . . . . . . . . . . . . . 4-2Unicode . . . . . . . . . . . . . . . . . . . . . . . 14-5UninstallationOracle . . . . . . . . . . . . . . . . . . . . . . . 18-2Teamcenter . . . . . . . . . . . . . . . . . . . 18-1

UNIX SAP library files . . . . . . . . . . . . 12-9Unpopulation of Oracle database . . . . . B-10Update a template . . . . . . . . . . . . . . . . 9-2UpgradeOracle databases . . . . . . . . . . . . 3-8, 3-10

URLs, Teamcenter’s engineering processmanagement . . . . . . . . . . . . . . . . . . 12-14User accounts . . . . . . . . . . . . . . . . 1-4, 2-22UTF-8 character set . . . . . . . . . . . . . . . 1-4


Index

UTF-8 mode . . . . . . . . . . . . . . . . . . . . . 4-4Utilitiesnative2ascii . . . . . . . . . . . . . . . . . . . 14-6Teamcenter EnvironmentManager . . . . . . . . . . . . . . . 16-2, 16-4

web_gen_xml . . . . . . . . . . . . . . . . . . 14-3

VVendor Management . . . . . . . . . . . . . . D-4Vendor Management for Rich Client . . D-10VisualizationEmbedded viewer . . . . . . . . . . . . . . D-10Stand-alone application viewer . . . . D-10Teamcenter Visualization . . . . . . . . . D-5

Volume Server . . . . . . . . . . . . . . . . . . D-2Volumes . . . . . . . . . . . . . . . . . . . . . . . 2-22

WWeb Application Manager . . . . . . 16-5–16-6Installation . . . . . . . . . . . . . . . . . . . 12-2Launching . . . . . . . . . . . . . . . . . . . . 12-2Patching . . . . . . . . . . . . . . . . . . . . . 16-4

Web serversDeploying Web components . . . . . . . 12-31Deployment . . . . . . . . . . . . . . . . . . 12-18Supported servers . . . . . . . . . . . . . 12-31

Web tierconnection problems . . . . . . . . . . . . . B-3Features . . . . . . . . . . . . . . . . . . . . D-10Generating application . . . . . . . . . . 12-3,12-9, 12-12

J2EE . . . . . . . . . . . . . . . . . . . . . . . 1-10

Legacy thin client URLs . . . . . . . . . 12-14Multiple applications . . . . . . . . . . . 12-17Proxy WAR file (WebLogic) . . . 12-6, 12-13Shared application serverinstance . . . . . . . . . . . . . . . . . . 12-17

Web Tier for .NET . . . . . . . . . . . . . . . D-11Web tier installation problems . . . . . . . B-4Web tier requirements . . . . . . . . . . . . . . 1-1WEB_core_help_serverpreference . . . . . . . . . . . . . 2-19–2-20, B-2WEB_default_site_deployed_app_namepreference . . . . . . . . . . . . . . . . . . . . . B-3web_gen_xml utility . . . . . . . . . . . . . . 14-3web_gen_xml.dat file . . . . . . . . . . . . . . 14-3WEB_help_server preference . . . 2-19–2-20,B-2WEB_ROOT directory . . . . . . . . . . . . . 12-2Web_tier directory . . . . . . . . . . . 12-3, 12-9,12-12, 12-19–12-20, 12-28, 12-35webapp_root directory . . 12-30–12-31, 12-34WebSphere . . . . . . . . . . . . . . . . . . . . 12-34webstrings.xml file . . . . . . . . . . . . . . . 14-3Welcome window . . . . . . . . . . . . . . . . . . 8-6Windows SAP DLL files . . . . . . . . . . . . 12-9Wire Harness Configuration . . . . . . . . . D-4Wiring Harness Design ToolsIntegration . . . . . . . . . . . . . . . . . . . . D-4Workflow to Scheduling Integration . . . D-3

Y

Yellow Pages . . . . . . . . . . . . . . . . . . . . . 6-1


Server Unix

Documents

Transcript of Server Unix