Installation Server Unix

Teamcenter 8.3

Installation on UNIX and LinuxServers Guide

Publication NumberPLM00011 F

Proprietary and restricted rights notice

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

© 2010 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 F

Contents

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

Part I: Getting started

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Enabling Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Interfaces: Teamcenter installation tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Basic concepts about Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . 1-7

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

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

Part II: Database server installation

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

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

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

Set shell limits and parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Upgrade Oracle server and databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Install Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Configure an Oracle database for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Part III: Teamcenter server installation

Teamcenter preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

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

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

PLM00011 F Installation on UNIX and Linux Servers Guide 3

Contents

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

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Run the postinstallation tasks program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Start Teamcenter database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Back up new installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Part IV: Web tier installation

J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

J2EE Web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Installing thin client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Installing rich client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

Part V: Adding features

Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Install the J2EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

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

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

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

Install a template using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Update the database using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Populate the database for Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Planning data migration from Genius4000 to Resource Manager . . . . . . . . . . 12-1Migrate Genius4000 data to Resource Manager . . . . . . . . . . . . . . . . . . . . . . . 12-3

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

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

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Prerequisites for rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1


Contents

Install Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2Complete Render Management installation . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

Installing Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Install online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Configure online help access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

Part VI: Additional configuration and maintenance

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . 16-1

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

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

Configuring client display language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2Environment settings for non-English locales . . . . . . . . . . . . . . . . . . . . . . . . 17-3Deploying localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

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

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

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

Installing Teamcenter maintenance packs . . . . . . . . . . . . . . . . . . . . . . 20-1

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1

Uninstall Teamcenter configurations and installations . . . . . . . . . . . . . . . . . . 21-1Uninstalling DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5

Part VII: Appendixes

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

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

Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . B-1Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . B-5Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9


Contents

Troubleshooting document rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . B-12Recovering from a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13

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

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

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

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

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

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

Figures

Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Two-tier deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Four-tier deployment (enterprise and Web tiers on same host) . . . . . . . . 1-14Four-tier deployment (enterprise and Web tiers on separate hosts with HTTPserver) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Four-tier deployment (multiple enterprise tier hosts and Web tierhosts) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Four-tier deployment (load balancing) . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Basic File Management System deployment . . . . . . . . . . . . . . . . . . . . 2-11Multiple databases (four-tier rich client) . . . . . . . . . . . . . . . . . . . . . . . 16-5Unicode homogeneous server platform configuration . . . . . . . . . . . . . . 17-5Sample silent installation configuration file . . . . . . . . . . . . . . . . . . . . . 18-4

Tables

Required hard disk space for Teamcenter configurations . . . . . . . . . . . . 1-3Rich client optional parameter values . . . . . . . . . . . . . . . . . . . . . . . . . 8-29Lifecycle Visualization (embedded viewer) parameter and tablevalues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Lifecycle Visualization (stand-alone application viewer) parameter and tablevalues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31Teamcenter Integration for NX parameter and table values . . . . . . . . . 8-31Content Management System for Rich Client 4-Tier values . . . . . . . . . . 8-31Environment settings on UNIX and Linux systems (UTF-8) . . . . . . . . . 17-5


Contents

Environment settings on UNIX and Linux systems (non-UTF-8) . . . . . . 17-8Teamcenter features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2Web tier required parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1Web tier optional parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-5Global Services context parameters . . . . . . . . . . . . . . . . . . . . . . . . . . E-9


Part

I Getting started

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

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

PLM00011 F 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-4Software integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

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

Configuring Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Starting Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

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

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

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

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

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


Chapter

1 Getting started

This guide describes how to install Teamcenter 8.3 on UNIX and Linux servers.This includes installation of Teamcenter servers using Teamcenter EnvironmentManager and 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.3.

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.3 server host runs one of the following supportedplatforms:

• Microsoft Windows1• Hewlett-Packard HP-UX• IBM AIX• Sun Solaris• SUSE Linux

For information about supported platform versions, see the Siemens PLM SoftwareCertification Database:


1. For information about installing Teamcenter on Windows servers, see the Installation on Windows Servers Guide.

PLM00011 F Installation on UNIX and Linux Servers Guide 1-1

Chapter 1 Getting started

Note

• On Sun Solaris systems, the Teamcenter rich client and Business ModelerIDE client require cairo, a free 2D graphics software for advanced userinterface rendering. Without cairo, the relation links between objects arenot visible in the UML editor in the Business Modeler IDE or in the richclient Relation Browser. Obtain cairo 1.4.10 from the following URL:

http://cairographics.org

• Teamcenter installation tools (Teamcenter Environment Manager andWeb Application Manager) require the ISO8859–1 character set. Makesure this character set is available on your host. If you are uncertain orwant to verify this character set, see Verify required character set.

• If your Teamcenter database server is IBM DB2, all Teamcenter serversand two-tier rich clients in your network must run operating systemssupported for Teamcenter with IBM DB2. IBM DB2 databases aresupported only with Teamcenter servers running on Microsoft Windows,IBM AIX, or SUSE Linux platforms.

• Teamcenter servers are supported on both HP-UX PA-RISC and HP-UXItanium platforms.

• The 64-bit IBM AIX platform is supported for Teamcenter serverprocesses.

The Teamcenter rich client on IBM AIX (32-bit and 64-bit) has passed allproduct validation testing but officially is supported only on test systemsat release. This is because the rich client includes a prerelease version of athird-party partner library that will be replaced in a subsequent version.

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

1-2 Installation on UNIX and Linux Servers Guide PLM00011 F

Getting started

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

Database

Teamcenter requires a relational database management system (RDBMS) for storingTeamcenter data. Before you install a Teamcenter, you must install an IBM DB2or Oracle database server and make sure your Teamcenter corporate server hosthas access to 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 or IBM DB2 installation and configuration.

Web browser

The Teamcenter thin client and four-tier rich client require a Web browser.Teamcenter 8.3 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 Teamcenter thin client is supported on Apple Safaribrowsers. No rich clients are supported on Macintosh.

For information about versions supported, see the Siemens PLM SoftwareCertification Database:


Note

No 64-bit Java plug-in is available for 64-bit Mozilla Firefox on Linuxplatforms. If you use the four-tier rich client on Linux platforms, you mustinstall 32-bit Mozilla Firefox and the Java plug-in before you install thefour-tier rich client.





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.3 integrations to other Siemens PLM Software products orthird-party software, install those products before you install Teamcenter 8.3.

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

• Teamcenter software distribution images can contain multiple ZIP files.For example, the software distribution image for Windows consistsof two files named Tcn_win_1_of_2.zip and Tcn_win_2_of_2.zip. Ifyou download software distribution images for Teamcenter, you mustdownload all files in the set to obtain the complete image. After youdownload files, extract all ZIP files to a common directory to assemble theimage before you begin installation.

• If you mount the Teamcenter software distribution image on a remoteNFS server, you must launch Teamcenter Environment Manager on thelocal server node.

Hewlett-Packard HP-UX considerations

Hewlett-Packard HP-UX systems require special configuration to support Java.You must perform these steps to enable Teamcenter clients and installation 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



Getting started

Linux considerations

On Linux systems, make sure your system is set to use the ISO8859-1 character setrather than the default UTF-8 character set. Teamcenter installation tools requirethis 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

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

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.

2. You create this directory when you install the Web Application Manager as described in J2EE Web tier installation.



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.

Web Application Manager

You launch the Web Application Manager by entering the insweb command. TheWeb Application Manager allows you to create multiple Web applications that


Getting started

contain 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 files3 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 IBM DB2, Oracle, and Microsoft SQL Server databases.

For information about installing a database server for Teamcenter, see Oracleinstallation and configuration or IBM DB2 installation 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.

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:

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

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


• Teamcenter shared binary executables and files• Teamcenter shared data subdirectories and files• Database connection• Teamcenter volume• Additional optional Teamcenter features such as File Management System (FMS)

Additional servers

A Teamcenter network requires one corporate server configuration. 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 interfaceprovides 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.

If you install the Teamcenter proxy server for WebDAV, you can also map a networkdrive to Teamcenter, enabling access to Teamcenter objects through commonWindows actions like Open and Save As.For more information, see the Installation on Windows Clients Guide.


Getting started

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.

Rich Client

(Local TC Server)

VolumeResource Tier

Client Tier

Database

Rich Client

(Local TC Server)

Rich Client

(Local TC Server)

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) manages the rich client access tovolumes:

• The FMS server cache (FSC) process run on the server hosting the volume.



• The FMS client cache (FCC) process runs on the rich client host.

For more information about FMS and two-tier rich client architecture, see FileManagement System installation.

Database

Teamcenter Server

Teamcenter Files (application root)

2-Tier Rich Client

Database Server

VolumeFCC FSC

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.


Getting started

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 Enterprise Edition(J2EE) application server, such as Oracle 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

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

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:


Getting started

• 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) manages the rich client access tovolumes:

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

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.



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

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


Getting started

HTTP Server

Database

Database Server

TC Server n

TC Server n+1

TC Server n+2

Server Manager


Thin Client 4-Tier Rich Client


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



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

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


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

HTTP Server

Load Balancing

Four-tier deployment (load balancing)



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 generally consists of installing a database server, aTeamcenter server, an optional Web tier, and Teamcenter clients.

Installing a database server

Install a database server (IBM DB2 or Oracle) according to the vendor’sdocumentation and the Teamcenter guidelines provided in IBM DB2 installationand configuration or 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-3Two-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Four-tier architecture installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Rich client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Thin client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10File Management System installation . . . . . . . . . . . . . . . . . . . . . . . . 2-10Installing File Management System . . . . . . . . . . . . . . . . . . . . . . 2-10Creating volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Lifecycle Visualization installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Global Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Remote workflow installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Security Services installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Teamcenter online help installation . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Oracle server considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Network environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Homogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Heterogeneous network environment . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Required operating system and user accounts . . . . . . . . . . . . . . . . . . . . . 2-19


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 can include server and client hosts from more than onevendor with each host running one of several supported operating systems.

The roles described in the following table are not restricted to one host on theTeamcenter network. A host often performs more than one of these roles. A role canbe performed by more than one host in the network.

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.

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_DATA


Chapter 2 Site planning

Network node Roleenvironment 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).

To install volumes on multiple hosts for the samedatabase, install a server that points to the databaseand install FMS on any system that services 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.

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.

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

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 ODS

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

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 IBM DB2 or Oracle tools.

For the installation procedures, see Database server installation.

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

For the installation procedures, see Teamcenter server installation.

3. Install the rich client on a client workstation using Teamcenter EnvironmentManager.

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

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.


Site planning

Install the resource tier using the third-party database server software (IBMDB2 or Oracle).

For the installation procedures, see 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 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.

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

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



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


Site planning

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.

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



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

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.


Site planning

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

• Remote workflow

When you choose this option, the rich client is enabled to support the linkingof objects between Teamcenter and other applications such as Teamcenter’sportfolio, program and project management. Separate installation of remoteworkflow components and Teamcenter Application Registry are required.

Note

Remote workflow requires the Web tier application, a component of thefour-tier architecture. To enable Teamcenter’s Integration for MicrosoftOffice for a two-tier rich client, you can connect the two-tier rich clienteither to a deployment of the Web 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 Webapplications. Instructions for installing the rich client over the Web on a client host



are in the Installation on UNIX and Linux Clients Guide and the Installation onWindows 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, Mozilla Firefox, and Safari. No aspect of thethin client is installed on a user workstation other than the required third-partyWeb browser.

File Management System installation

File Management System (FMS) downloads and uploads file data for the rich client,embedded viewer, and the thin client configured with Lifecycle Visualization.Multi-Site Collaboration also uses FMS servers to transfer data.

Note

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

If the FSC does not manage any volumes, that is, if it is purely a cache server,it can run as any user that is convenient.

Installing File Management System

FMS provides the following functions:

• Volume server for file management

• Shared server-level performance cache for shared data access between 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:

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


Site planning

FCC

SYSTEMS

Vol 1

Vol 2

Vol 3FCC

FCC

LAN

TC Server FSC Server

Rich Client

Rich Client

Visualization Client

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.

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.


Site planning

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

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 and LinuxClients Guide or Installation on Windows Clients Guide.

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 File ManagementSystem (FMS). FMS provides the volume services after 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)


Site planning

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 Installationon UNIX and Linux Clients Guide and the Installation on Windows ClientsGuide.

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

Note

• The Teamcenter rich client supports only the 32-bit embedded viewer.On 64-bit systems, you must install the 32-bit version of LifecycleVisualization if you want to use the embedded viewer in the rich client.

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

Global Services installation

Global Services provides the additional components that enable a Teamcenter site toexchange BOM data with a Teamcenter Enterprise site:

• The Teamcenter connector extracts BOM data from Teamcenter.

• The Teamcenter Enterprise Connector extracts BOM data from TeamcenterEnterprise.

To enable users to exchange data between Teamcenter and Teamcenter Enterprise,you must install and configure Global Services, the Teamcenter and TeamcenterEnterprise connectors.

Global Services is available in the Web_tier/tcgs directory on the Teamcentersoftware distribution image. For installation information, see Install Global Services.



Remote workflow installation

Remote workflow enables users to create links between Teamcenter objects andobjects in Teamcenter’s portfolio, program and project management. Users canlaunch the linked 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 step 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 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 by


Site planning

specifying 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 Teamcenter online help on a Web server or in a directory on a networkfile system to provide online help to Teamcenter rich client and thin client hosts.

For more information, see Installing Teamcenter online help.

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

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.



Note

QPL and a separate RDV database are required if you use cacheless search.

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 corporate server,and all Teamcenter clients are all UNIX nodes provided by one vendor (for example,Sun Microsystems).

When deploying the two-tier architecture, you can install Teamcenter 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.


Site planning

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

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 using



Teamcenter Environment Manager to install Teamcenter and populate a database.Teamcenter Environment Manager refers to this user as DB user.

Note

If Oracle and Teamcenter applications or files are shared using NFS/CIFS,you must standardize the user and group IDs of the Teamcenter and 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

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

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


Chapter

3 IBM DB2 installation andconfiguration

Install IBM DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Install the DB2 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Register the DB2 server license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Set DB2 profile variables for Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 3-4

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

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

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


Chapter

3 IBM DB2 installation andconfiguration

Install IBM DB2, verify installation and connectivity with a sample database, andthen configure a database for Teamcenter.

Before you begin installing DB2, make sure your host meets or exceeds the systemsoftware and hardware requirements for DB2 servers and IBM data server clientsfor your platform:

http://www-01.ibm.com/software/data/db2/9/sysreqs.html

For information about the IBM DB2 versions that Siemens PLM Software certifiesfor use with Teamcenter, see the Siemens PLM Software certification database:


Note

If your Teamcenter database server is IBM DB2, all Teamcenter servers andtwo-tier rich clients in your network must run operating systems supportedfor Teamcenter with IBM DB2. IBM DB2 databases are supported only withTeamcenter servers running on Microsoft Windows, IBM AIX, or SUSE Linuxplatforms.

After you prepare your DB2 server host, install a Teamcenter-supported versionof IBM DB2.

Note

For more information about installing and using DB2 software, including theDB2 Control Center, see the IBM DB2 Information Center:

http://publib.boulder.ibm.com/infocenter/db2luw/v9//index.jsp

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

Install the DB2 server

1. Create the following groups and users for DB2:

Groups: db2insgp, db2fengp, db2dasgp


http://www-01.ibm.com/software/data/db2/9/sysreqs.html


Chapter 3 IBM DB2 installation and configuration

Users: db2inst1, db2fenc1, db2das1

DB2 uses the operating system’s native user authentication.

Note

User names and group names must not exceed 8 characters.

2. Prepare the software installation media:

• If you use an IBM DB2 software CD or DVD, insert the disc and mountif necessary.

• If you use downloaded images, download the appropriate DB2 image for yourplatform from an IBM partner site such as the following:

https://www14.software.ibm.com/webapp/dswdown/dswdown.wss/web/resultsActionCat#anchor

For example, if you use SUSE Linux Enterprise Server (SLES) 9 ServicePack 3, download the DB2_ESE_V95_Linux_x86-64 image.

Extract the image to an authorized directory on the Linux/UNIX file system.

Note

– The IBM DB2 server can be installed from the root user account ora nonroot user account. Root installation offers full functionalityof the DB2 for Linux, UNIX, and Windows (LUW) edition. Rootinstallation also permits multiple versions of the DB2 server to beinstalled on the same host, where nonroot installation allows onlyone instance, image, and version on a single system.

– For more information about downloading and installing DB2, seethe following link:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp

3. Change to the directory in which you extracted the DB2 installation image.

4. In the IBM DB2 installation image, launch the db2set shell script to launchthe IBM DB2 installation program.

5. In the DB2 Setup Launchpad dialog box, click Install a Product.

6. Under DB2 Enterprise Server Edition Version version, click Install New.

This launches the DB2 Setup - DB2 Enterprise Server Edition installationwizard.

7. Proceed to the Software License Agreement dialog box. After you accept thelicense terms, click Next.

8. In the Select the installation type dialog box, select the type of installation youwant to perform. The Typical option is sufficient for the Teamcenter server’sneeds.




IBM DB2 installation and configuration

9. In the Select the installation, response file creation, or both dialog box, selectthe appropriate option. If you do not want to save your installation settings ina response file, select the first option in the list (Install DB2 Enterprise ServerEdition on this computer).

10. In the Select the installation folder dialog box, enter an installation directoryor accept the default directory shown.

11. In the Set the DB2 copy name dialog box, accept the default value for DB2copy name and make sure Set this as the default DB2 copy on my computer isselected.

12. In the Set up a DB2 instance dialog box, click Create the default DB2 instance.

13. In the Set up partitioning options for the default DB2 instance dialog box,click Single partition instance.

14. In the Configure DB2 instances dialog box, accept the existing values shown.

15. In the Set user information for the default DB2 instance dialog box, type andconfirm the password for the database user account.

Accept the default database user name shown. If multiple domains are available,select the appropriate domain in the Domain list. Otherwise, accept the defaultsetting.

Make sure Use the same user name and password for the remaining DB2instances is selected.

16. In the Prepare the DB2 tools catalog dialog box, clear the Prepare the DB2tools catalog check box.

17. In the Set up notifications dialog box, clear the Set up your DB2 server to sendnotifications check box.

18. In the Enable operating system security for DB2 objects dialog box, accept thedefault values shown.

If multiple domains are available, select the appropriate domain for the DB2users group. Otherwise, accept the default setting.

19. In the Start copying files dialog box, click Install to begin installing the DB2server.

20. When the DB2 installation program displays the Setup is complete dialog box,click Next.

21. In the Install additional products dialog box, click Finish.

Register the DB2 server license

1. Register your DB2 license key by typing the following command:DB2–home/sqllib/adm/db2licm —a license-file

Replace DB2-home with the home directory of the DB2 instance owner. Replacelicense-file with the path to your DB2 license file.



The default license file is DB2-image/db2/license/db2ese.lic. ReplaceDB2-image with the path to your IBM DB2 installation media.

2. To verify the license registration, enter the following command:db2licm —l

Set DB2 profile variables for Teamcenter

1. Change to the sqllib/adm directory and type the following command:db2set DB2_SNAPSHOT_NOAUTH=on

Note

This command is necessary to enable TEM to install Teamcenter with aDB2 database.

2. Restart the DB2 server.

For more information, see the System Administration Guide.

Create a DB2 sample databaseTo verify the installation of the DB2 server, create a sample database you can useto verify database connectivity.

Note

The sample database is for testing and verification only. It cannot be used byTeamcenter.

Using the DB2 First Steps application, create the sample database by one of thefollowing methods:

• Using default sample tables

• Using your own parameters and tables

Create a sample database using default sample tables

1. Launch the DB2 First Steps application:db2fs

Note

The DB2 First Steps application requires a Web browser. Make sure aTeamcenter-supported version of Mozilla Firefox or Microsoft InternetExplorer is installed on the DB2 server host.

2. In the DB2 First Steps application, in the options on the left side, click DatabaseCreation.

3. In the Database Creation dialog box, click Create SAMPLE Database.This launches the Create SAMPLE Database wizard.



4. In the Create SAMPLE Database dialog box, click SQL objects and data only.(This is the default option.)

Click OK.The wizard creates the sample database.

5. When database creation is complete, click OK to close the wizard.

Create a sample database using your own parameters and tables

1. In the DB2 First Steps application, in the options on the left side, click DatabaseCreation.

2. In the Database Creation dialog box, click Create your own Database.

This launches the Create Your Own Database wizard.

3. In the Specify a name for your new database dialog box, click option.

4. In the Specify where to store your data dialog box, enter one or more storagepaths for the database, or accept the default location shown.

5. In the Select your maintenance strategy dialog box, choose whether you want tospecify a time period for database maintenance. This is optional and does notdirectly affect Teamcenter operation.

6. In the Provide a valid SMTP server dialog box, click Next. No options in thisdialog box are required for Teamcenter.

7. In the Review the actions that will take place when you click Finish dialogbox, click Finish.

The wizard creates the database.

Verify connectivity with the sample database1. In the DB2 First Steps application, click Database Administration, and thenclick Basic administration tasks.

2. In the Basic administration tasks dialog window, click Start DB2 Control Center.

This launches the DB2 Control Center.

3. When the Control Center prompts you to choose a view, click Advanced.

4. In the Control Center tree (under Object View), expand All Databases.

5. In the All Databases branch, expand SAMPLE.

If DB2 displays database objects, access to the database is verified.

6. Close the DB2 Control Center.

7. Close the DB2 First Steps application.



After you verify DB2 database connectivity, you can remove the sample databaseto free disk space. However, if you use the sample applications, keep the sampledatabase.

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

Create a DB2 Teamcenter database

Using the DB2 Command Line Processor, enter the following command:db2 CREATE DB db-name AUTOMATIC STORAGE YES ON ’path’ USING CODESET

UTF-8 TERRITORY US PAGESIZE 32 K

Replace db-name with the name or alias of the database to be created. Replace pathwith the path or drive on which to create the database. This is also the storage pathor drive associated with the database.

For example:db2 CREATE DB tcdb2 AUTOMATIC STORAGE YES ON ’D:’ USING CODESET

UTF-8 TERRITORY US PAGESIZE 32 K

Create a DB2 Teamcenter database user

DB2 uses the underlying operating system security to manage user IDs andpasswords. The Teamcenter database user and password must be established atthe operating system level. For information about creating a DB2 user, see theDB2 documentation from IBM.

Set DB2 database configuration parameters

Optionally, set DB2 database configuration parameters for Teamcenter. SiemensPLM Software recommends setting the following parameters for each database inthe instance on which you run your Teamcenter application. For other parameters,accept the default settings.

Parameter Description Value

STMTHEAP Statement heap 100000

APPLHEAPSZ Default application heap 16000

LOGBUFSZ Log buffer size 512

LOGPRIMARY Number of primary log files 20

LOGSECOND Number of secondary log files 5

LOGFILSIZ Log file size 4096

UTIL_HEAP_SZ Maximum memory for utilities 150000

Database configuration parameters can be set using the DB2 Control Center or theupdate database configuration command in the DB2 command line processor.For example:



db2 UPDATE DB CFG FOR db-name USING STMTHEAP 100000

After you change database configuration parameters, enter a DB2 TERMINATEcommand to ensure the changes take effect.

For more information on modifying configuration parameters, see the IBM DB2technical documentation.

Archive DB2 database log files

Optionally, you may archive DB2 database log files by setting the LOGRETAINand USEREXIT database parameters.

The LOGRETAIN database parameter is not enabled by default, and its behavioris affected by the value of the USEREXIT parameter.

Set USEREXIT to one of the following values:

ON Enables the user exit program to archive log files whenthey are full, and also to retrieve log files when rollforward operations are used to restore a database.

OFF Disables archiving via the user exit program.

Set LOGRETAIN to one of the following values:

NO Specifies log files are not retained. The database managerdeletes log files in the log path directory and creates newlog files.

If USEREXIT is set to OFF, you can perform onlybackup (restore) recovery, not roll forward recovery. Thismay affect your data recovery process for your productionenvironment database.

The default value is NO.

RECOVERY Specifies all log files are kept on the system for thedatabase administrator to archive or delete.

Make sure your database administrator reviews the settings for the LOGRETAINand USEREXIT parameters.

For more information about these parameters, see the IBM documentation.

After you complete configuring your database, you can install a Teamcenter serverusing Teamcenter Environment Manager (TEM). During installation, TEM createsdatabase objects and populates Teamcenter data.


Chapter

4 Oracle installation andconfiguration

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

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

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

Configuring Oracle software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Configure Oracle server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Configure Oracle Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

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


Chapter

4 Oracle installation andconfiguration

Your Oracle database server must be a version certified for Teamcenter 8.3. Forinformation about the Oracle versions that Siemens PLM Software certifies for usewith Teamcenter 8.3, 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.3, 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 4 Oracle installation and configuration

Set shell limits and parametersOracle RDBMS extensively uses UNIX resources such as shared memory, swapmemory, and semaphore for interprocess communication. Insufficient parametersettings cause problems during installation and instance startup. The greater theamount of data stored in memory, the faster a database operates. In addition, bymaintaining data in memory, the UNIX kernel reduces disk I/O activity.

On all UNIX and Linux platforms supported for Teamcenter 8.3, 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 settingsdescribed in the following sections. The recommended kernel parameter settingsare for a typical Oracle database 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 the following table areset to the 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 requires.

4. Press F10 to exit.

AIX shell limit Minimum value

Soft FILE size –1 (unlimited)

Soft CPU time –1 (unlimited)

This is the default value.

Soft DATA segment –1 (unlimited)

Soft STACK size –1 (unlimited)


Oracle installation and configuration

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

Set HP-UX kernel parameters

Set kernel parameters as described in the following table. Set parameters using themethod described in your HP-UX documentation.

Caution

Do not change the kernel parameter settings if the parameters were set foranother program and the values are greater than the levels Oracle requires.

Note

You can view kernel parameters using the kctune command.

HP-UX kernelparameter

Minimum 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 9 or earlier, set kernel parameters to meet or exceed the recommendedOracle settings. Use the procedure provided in your Solaris documentation to setkernel parameters.

On Solaris 10, set kernel parameters using the Solaris resource control facility. Thefollowing table describes Solaris 10 resource control values for a single databaseinstance.

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



Solaris 10 resourcecontrol Description

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.oracleNAME 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 in thefollowing table by adding the following lines to the /etc/security/limits.conf file:

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

SUSE Linux shell limitItem inlimits.conf

Minimumhard limit

Maximum number of open file descriptors nofile 65536

Maximum number of processes availableto a single user

nproc 16384



Caution

Do not change the shell limit values if they were set for another programand the values are greater than the levels Oracle requires.

2. Add or edit the following line in the /etc/pam.d/login file:session required /lib/security/pam_limits.so

3. Change the oracle user default shell startup file:

• For the Bourne, Bash, or Korn shell, add the following lines to the/etc/profile.local file:

if [ $USER = "oracle" ]; 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.local file:

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

endif

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:export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib

SUSE Linux:

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

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. If you use 64-bit Hewlett-Packard HP-UX, create the following symbolic linksbefore you begin Oracle installation:

# cd /usr/lib

# ln -s libX11.3 libX11.sl# ln -s libXIE.2 libXIE.sl# ln -s libXext.3 libXext.sl# ln -s libXhp11.3 libXhp11.sl# ln -s libXi.3 libXi.sl# ln -s libXm.4 libXm.sl# ln -s libXp.2 libXp.sl



# ln -s libXt.3 libXt.sl# ln -s libXtst.2 libXtst.sl

5. Insert the Oracle RDBMS 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.

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

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

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

9. In the Welcome window, click Next.

10. If Oracle Universal Installer displays the Specify Inventory Directory andCredentials window, enter the directory where you want to install inventory filesand 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).

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

12. In the Select Installation Type dialog box, select Enterprise Edition and clickNext.

13. 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 or later into an existing Oracle home thatcontains Oracle 9i or earlier software.

14. 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 check box for the failed check.

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

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

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

18. 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 server1. 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.3, see the Siemens PLMSoftware certification 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 database 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 the appropriate template (forOracle 10g or 11g) and click Next.

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.

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

Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Teamcenter postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1


Chapter

5 Teamcenter preinstallation tasks

Install the licensing server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Select destination directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Verify required character set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Ensure correct mode on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Install a volume server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

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

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


Chapter

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

Teamcenter provides four types of 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.

• occasional user is a user that infrequently performs author actions andotherwise requires only consumer privileges.

• viewer is a user that views, queries, and prints information but does notparticipate in approval or authoring processes.

Install the ugslmd license daemon:

1. Obtain a Teamcenter 8.3 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 5 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. Set the TCP_NODELAY environment variable to 1. This helps optimize logontime when launching Teamcenter.

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

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

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

additional_documentation directory on the Teamcenter 8.3 documentationdistribution image.

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 Teamcenter on a local disk to configure File Management System filecaches 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.3,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 ISO8859-1 mode, rather than the default UTF-8 mode.

Install a volume serverBy default, you can create volumes only on local disks, but if you want to write filesto volumes residing on remote disks (shared across the network), you can createa stand-alone volume server.

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

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.

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 the FMS Server Cachefeature preselected by the Volume Server solution.

8. In the Installation Directory box, enter the absolute path to the directory whereyou want to install the volume server.


Teamcenter preinstallation tasks

9. Proceed to the Operating System User panel. Type the password for theoperating system account to which you logged on to install the volume server.

10. Proceed to the FSC Service panel. Enter required values for the FMS servercache (FSC) service. For information about required values, click Help.

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

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

13. When installation is complete, close TEM.

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

6 Teamcenter server installation

Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

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


Chapter

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

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

• Obtain the information required to install File Management System.

Note

• If you install File Management System, the FMS server cache (FSC) 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

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


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 FoundationFMS 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 Installing a customsolution or third-party template.

• If you install Teamcenter Automotive Edition and GM Overlay withthe rich client, make sure you complete the required postinstallationsteps.

For more information, see the Installation on Windows Clients Guideand the Installation on UNIX and Linux 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. In the following panels, enter the required values to configure the FMS servercache:

FSC ServiceFSC Service: ConnectionsFSC Service: FCC DefaultsFSC Service: Additional SitesFSC Service: Additional Group SitesFSC Deployment Model

For information about these panels, click Help.

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.

Select the database engine (IBM DB2 or Oracle), and then enter the databaseserver information.

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

Note

• TEM attempts to connect to the database server. If the connectionfails, you cannot continue with installation until you correctlyconfigure a database for Teamcenter.

For information about preparing a database for Teamcenter, seeIBM DB2 installation and configuration or Oracle installation andconfiguration.

• If you use Oracle, Teamcenter Environment Manager (TEM) verifiesyour Oracle version during installation. If your Oracle server does notmeet the minimum required version, TEM does not allow installationto 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. TEM displays additional panels to create and configure the Teamcenterdatabase. These panels vary according to the database engine you select.

16. Proceed to the Volume Specification panel.

In the Volume Name box, type a name for the Teamcenter volume you wantTEM to create.

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.

3. For information about supported database servers for Teamcenter 8.3, see the Siemens PLM Software certification database(http://support.ugs.com/online_library/certification/).




Note

Siemens PLM Software recommends not defining the volume locationunder the Teamcenter application root directory. Doing so leads tocomplications when upgrading to a later version of Teamcenter.

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

18. Proceed to the Default Site Web Server panel.

If you have an existing deployment of the Teamcenter Web tier, you mayoptionally define settings that enable rich client users to generate and viewbookmark files that interact with Lifecycle Visualization and enable thin clientusers to receive Teamcenter notifications.


19. Proceed to the Flex License Client panel. Enter settings for the Siemens PLMSoftware Common Licensing Server. The Common Licensing Server must beinstalled before you begin Teamcenter installation.

For more information, see Install the licensing server.

20. Proceed to the Teamcenter Administrative User panel. During a corporate serverinstallation, the values in this panel are read-only.


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

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

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

24. When installation is complete, close TEM.


Chapter

7 Teamcenter postinstallation tasks

Run the postinstallation tasks program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Start Teamcenter database daemons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Configure Multi-Site Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Prepare the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . 7-2Configure Multi-Site Collaboration daemons . . . . . . . . . . . . . . . . . . . . . . 7-3

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


Chapter

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

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

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


Chapter 7 Teamcenter postinstallation tasks

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.

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.


Teamcenter postinstallation tasks

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.

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


Chapter 7 Teamcenter postinstallation tasks

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.

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.

5. Stop all Teamcenter services, including FMS and TCFS services.


Teamcenter postinstallation tasks

6. If you use TCFS, remove the TCFS entry from the /etc/services file. This mustbe done for the Teamcenter upgrade to succeed.

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 Web tier installation

J2EE Web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1


Chapter

8 J2EE Web tier installation

J2EE Web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

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

Installing thin client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2Build the Teamcenter Web Tier Web application . . . . . . . . . . . . . . . . . . . 8-3Build additional Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Install Global Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Supporting files locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Generate Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Generate the Web application for Content Management . . . . . . . . . . . 8-15Build a proxy WAR file for WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . 8-17Migrate legacy thin client URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

Sharing an application server instance for multiple four-tierenvironments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21

Installing rich client Web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . . 8-25Rich client distribution instance requirements . . . . . . . . . . . . . . . . . . 8-25Install a rich client distribution instance . . . . . . . . . . . . . . . . . . . . . . 8-32

Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Before you start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Deploy the distribution server instance . . . . . . . . . . . . . . . . . . . . . . . 8-35Publish information for users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Start and stop the rich client distribution server . . . . . . . . . . . . . . . . 8-38Start the rich client distribution server . . . . . . . . . . . . . . . . . . . . 8-38Stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . . 8-39

Managing the rich client distribution server and instances . . . . . . . . . . . . 8-39Change the distribution server contents . . . . . . . . . . . . . . . . . . . . . . 8-39Add components to the distribution server instance . . . . . . . . . . . . . . 8-39Run the distribution server as a service . . . . . . . . . . . . . . . . . . . . . . . 8-41


Chapter

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

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


Chapter 8 J2EE Web tier installation

• 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.3 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 Installing Teamcenter online help.

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

For information about installing this application, see Build the Teamcenter WebTier Web application.

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

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

8. Enter values for required context parameters.

2. The Teamcenter documentation distribution image contains the tchelp.jar file that contains the online help files.



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 the following table.

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.jgroup.org.4. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choosethe appropriate procedure for the application server you use.


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

http://www.jgroups.org/


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.3. If you are upgradinga previous 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, make sure 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.3 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 files. 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 coexist with each other or any other GlobalServices connector.

• Teamcenter 2007 rich client connector

If you are installing the Teamcenter 2007 rich client connector, the connectorrequires access to dependent external JAR files. 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.

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 8.3Global 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:



Note

If you are installing the Teamcenter gateway for Oracle Manufacturing,you must repeat this procedure selecting the Teamcenter 8.3 GlobalServices Framework – Gateway for Oracle Manufacturing (Engineering)Application Directory and Teamcenter 8.3 Global Services Framework –Teamcenter Rich Client OSGi Plug-in solutions in step 7.

If you are installing the Teamcenter 8 Rich Client Connector, you mustrepeat this procedure selecting the Teamcenter 8.3 Global ServicesFramework – Teamcenter Rich Client OSGi Plug-In solutions in step 7.

If you are installing the Teamcenter 2007.1 Rich Client Connector, youmust repeat this procedure selecting the Teamcenter 8.3 Global ServicesFramework – Teamcenter 2007.1 Rich Client OSGi Plug-In solutions instep 7.

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.1 Global Services Framework – Application Directorysolution.

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.The Web Application Manager displays the Add Web Application dialog box.

7. Create the Global Services enterprise application:

a. In the Name box, type a name for the application, for example, 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.3 Global Services Framework – Enterprise Applicationsolution.

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

If you use these products Select these solutions

Teamcenter 2007 or later Teamcenter 8.3 Global Services Framework- Teamcenter SOA Connector

Teamcenter 8 or later (fullrich client functionality)

Teamcenter 8.3 Global Services Framework- Teamcenter 8 Rich Client Connector

Note

You must also create a separateWeb application containing theTeamcenter 8.3 Global ServicesFramework – Teamcenter 8 RichClient OSGi Plug-in solutions asdescribed in step 4 of this procedure.

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



If you use these products Select these solutionsTeamcenter 2007.1 MP5through MP8 (full rich clientfunctionality)

Teamcenter 8.3 Global Services Framework- Teamcenter 2007.1 Rich Client Connector

Note

You must also create a separateWeb application containing theTeamcenter 8 Global ServicesFramework – Teamcenter 2007.1Rich Client OSGi Plug-In solution asdescribed in step 4 of this procedure.

Teamcenter 2007 through2007.1 MP4 (full rich clientfunctionality)

Teamcenter 8.3 Global Services Framework- Teamcenter 2007 Rich Client Connector

Teamcenter Engineering(2005 through 2007)

Teamcenter 8.3 Global ServicesFramework - Teamcenter Engineering2005/2007 Connector

Teamcenter Engineering(prior to 2005)

Teamcenter 8.3 Global Services Framework- Teamcenter Engineering V9 Connector

Teamcenter Enterprise Teamcenter 8.3 Global Services Framework- Teamcenter Enterprise Connector

Web services Teamcenter 8.3 Global Services Framework- WebServices Connector

Apache-based Web services Teamcenter 8.3 Global Services Framework- Axis2 Services

JMS messaging Teamcenter 8.3 Global Services Framework- JMS Messaging

EPSync Manager Teamcenter 8.3 Global Services Framework- EPSync Reactor

Teamcenter Engineering V9with Oracle Manufacturing

Teamcenter 8.3 Global Services Framework- Gateway for Oracle Manufacturing(Engineering)

Note

You must also create a separateWeb application containing theTeamcenter 8.3 Global ServicesFramework - Gateway for OracleManufacturing (Engineering)Application Directory solution, asdescribed in step 4 of this procedure.



If you use these products Select these solutionsTeamcenter Engineering2005 or 2007 with OracleManufacturing

Teamcenter 8.3 Global Services Framework- Oracle Manufacturing Connector

Teamcenter 8.3 Global ServicesFramework - Teamcenter Engineering2005/2007 Connector

Teamcenter 8.3 Global Services Framework- Gateway for Oracle Manufacturing(Engineering)

Note

You must also create a separateWeb application containing theTeamcenter 8.3 Global ServicesFramework - Gateway for OracleManufacturing (Engineering)Application Directory solution and asdescribed in step 4 of this procedure.

Teamcenter Enterprise withOracle Manufacturing


Teamcenter 8.3 Global Services Framework- Teamcenter Enterprise Connector

Teamcenter 8.3 Global Services Framework- Gateway for Oracle Manufacturing(Enterprise)

Teamcenter 8.3 with OracleManufacturing


Teamcenter 8.3 Global Services Framework- Gateway for Oracle Manufacturing(Teamcenter)

Teamcenter 8.3 Global Services Framework- Gateway for Oracle Manufacturing UsingSOA Connector (Teamcenter)

Note

You must also create a separateWeb application containing theTeamcenter 8.3 Global ServicesFramework - Gateway for OracleManufacturing (Engineering)Application Directory solution andTeamcenter 8.3 Global ServicesFramework – Teamcenter Rich ClientOSGi Plug-in solutions as describedin step 4 of this procedure.



If you use these products Select these solutions

Oracle Manufacturing Teamcenter 8.3 Global Services Framework- Oracle Manufacturing Connector

Global Services userinterface (for a configurationthat does not containstandalone user interfacesolution)

Teamcenter - Web Tier Infrastructure

Teamcenter 8.3 Global Services Framework- User Interface

Server-to-servercommunications for globalworkflow

Teamcenter 8.3 Global Services Framework- Security Proxy

Global Services orchestration Teamcenter 8.3 Global Services Framework- Ode BPEL Enterprise Application

Note

This solution must be createdand deployed separately from theTeamcenter 8.3 Global ServicesFramework - Enterprise Applicationsolution.

Multiple instances of GlobalServices you want to connect.

Teamcenter 8.3 Global Services Framework- Teamcenter Global Services Connector

Teamcenter Sourcing Teamcenter 8.3 Global Services Framework- Teamcenter Sourcing

Teamcenter and TeamcenterEnterprise (to share data)

Teamcenter 8.3 Global Services Framework- Data Exchange

Note

• Some solutions require other solutions, and some solutions areincompatible with others. When you select a solution, the WebApplication Manager automatically selects prerequisite solutionsand disables incompatible solutions.

• If you are installing the Teamcenter Enterprise Connectorfor Teamcenter Enterprise 2005 SR1 or an earlier release ofTeamcenter Enterprise, ensure that you copy themtiems.jar fileto the same location as the mti.jar file. For more information,see Supporting files locations.

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

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

Note

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

ApplicationInstanceSSOAppIDLogFileLocationTcGSBOSJNDI

TcGSJDBCJNDITcGSMessageServerJNDITcGSNotifierReactorJNDITcGSDORJNDI

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


The Web Application Manager displays the installation status in the Progressdialog box. When the installation is complete, click OK to close the Progressdialog box.


14. Locate the deployable files (by the names you specified in step 7) generatedduring installation. This file is in the deployment directory under the specifiedstaging location.


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.


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



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 and selectone of the following:

• Teamcenter Content Management System

• Teamcenter Content Management S1000D System

• Teamcenter Content Management DITA System

• Teamcenter Content Management DITA and S1000D System

• Teamcenter Content Management DITA and S1000D System forWebLogic

Note

Select the S1000D or DITA options only if you have already installedthose features.

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.

Tip

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

6. Click OK.






Note

For the ServerHomeDirectory value, type the name of the directorythat will be used to store cached and temporary files during ContentManagement web server processing. For most installations, you canaccept the default value.




10. Locate the deployable file generated during installation (by the name youspecified in step 15). 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

7. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Webapplication.



Note


4. Click OK.


5. Enter values for the following required context parameters:

Parameter Description

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.3 from Teamcenter’sengineering process management 2005 or earlier, you must update the link yoursite uses to access the thin client and the links users saved to objects managed inTeamcenter. Teamcenter 8.3 changes part of the thin client URL from /cgi-bin/imanto /file-name/webclient. The file-name reference is replaced with the name of theWeb tier EAR file. For example, if the Web tier EAR file is named tc.ear, the valueis /tc.

To manage this change, install the legacy URL support application (cgi-bin.war)and deploy it on the server where the Teamcenter Enterprise Tier Web 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.



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.

9. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Webapplication.




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.

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.

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 6 and 7, 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 steps6 through 8.

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

Note

If you include Lifecycle Visualization in your rich client distributioninstance, and you use downloaded software images instead of a DVD:

1. Download the common.tar.gz file and the appropriateplatform-specific .gz archives (for Sun Solaris, IBM AIX, or Linux).

2. Extract all these files into a single directory.

3. When building your rich client distribution instance, enter the locationof this directory in the TcVisInstallImageUnixLocation contextparameter in the Web Application Manager.

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.

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.



Parameter DescriptionWindowsLocation Location on the client host where you want the

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

UnixLocation Location on the client host where you want theOver-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 the followingtables.



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.



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.

Lifecycle Visualization (embedded viewer) parameter and table values


EmbVisLicenseLevel License level for the embedded viewer: Mockup,Professional, Standard, or Base.

The Base license is available for all users of the 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.



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.

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.

Content Management System for Rich Client 4-Tier values


CMSWebAppServerTable The list of the locations of the Content Management Webservers. 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 Rich clientdistribution instance requirements. The other required parametersvary, depending on the applications you are installing with the richclient instance. For descriptions, see Rich client distribution instancerequirements.

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

• Creates the manifest file (ds_manifest.mf) in the staging location directory(named in step 10).

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 Rich client optionalparameter values.


21. Click OK.The Web Application Manager displays the Teamcenter Web ApplicationManager dialog box.


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.3 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 Rich clientdistribution instance requirements. The other required parametersvary, depending on the applications you are installing with the richclient instance. For descriptions, see Rich client distribution instancerequirements.

• 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 Rich client optionalparameter values.


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

V Adding features

Installing the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

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

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

Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

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

Installing Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Installing Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1


Chapter

9 Installing the server manager

Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Install the J2EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Start the server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Start the J2EE-based server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6


Chapter

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

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.

If your server manager host has only one IP address, you donot need to provide a value for this box. If the server host hasmultiple IP addresses and you want the server manager touse a specific address when connecting to Teamcenter servers,you must provide the address or the logical host name of theserver manager host.

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

Communication protocol The communication protocol mode between TreeCache peers,either TCP or multicast mode.

The Web tier application must use this same mode.

Multicast configuration If you are using multicast mode, ensure that the network 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.jgroups.org/.




Chapter 9 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 Teamcenter DeploymentGuide available 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 Server Enhancements, selectJ2EE based 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:

Field/Option Description

Max Servers inSub-Pool

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

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

Tip

If necessary to maintain the minimum number ofwarm servers, while not exceeding the maximumnumber of server processes, the server managertimes out servers in use.

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


Installing the server manager

Field/Option Description

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

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

0700 3, 1700 2

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

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

• If the number of server processes exceeds thespecified target, only the minimum number of warmservers is maintained and servers are terminated asthey time out.

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

Tip

Setting this value to 0 allows an unlimited numberof logons.

Check CPU Load Specifies whether you want the server manager to controlserver processes based on the CPU load of the local host.

Tip

This option applies only to Sun Solaris systems.

CPU Load Limit Specifies a limit for the CPU load of the local host.

When the CPU load of this host exceeds the specifiedlimit, the assigner skips assigning from the subpool.

CPU Interval Specifies the interval in seconds between checks of theCPU load of the local host.

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.



Note

If you experience connection delays during server manager startup, seeTroubleshooting four-tier architecture deployment for possible solutions.

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

10 Install the Business Modeler IDE

Install the Business Modeler IDE as a stand-alone application . . . . . . . . . . . . 10-1

Install the Business Modeler IDE to an existing Eclipse environment . . . . . . . 10-4

Allocate memory to the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . 10-6

Start the Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8


Chapter

10 Install the Business Modeler IDE

To install the Business Modeler IDE, you can install it as a stand-alone application,or if you already have Eclipse installed, install it into your Eclipse environment.After you install the Business Modeler IDE, allocate additional memory so thatBusiness Modeler 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 Base Install, select one of the following:

• Business Modeler IDE 2-tier

Connects to a Teamcenter server in a two-tier environment using IIOP(over a network).

• Business Modeler IDE 4-tier

Connects to a Teamcenter server in a four-tier environment using HTTP.

When you select one of these options, a server connection profile is added inthe Business Modeler IDE.

For more information, see the Business Modeler IDE Guide.

b. (Optional) Select Extensions→Platform Extensibility→GlobalServices→Mapping Designer.

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

c. (Optional) Select Extensions→Mechatronics Process Management→EDAfor Business Modeler IDE.

This installs the EDA Derived Data configuration tool into the BusinessModeler IDE. This tool is used to configure Teamcenter EDA, an applicationthat integrates Teamcenter with electronic CAD (E-CAD) design applications,such as Cadence and Mentor Graphics.


Chapter 10 Install the Business Modeler IDE

Note

If you install this option, you must ensure that theExtensions→Mechatronics Process Management→EDA Server andRich Client Support option is also installed to the server.

In addition, later in the installation process when you select templatesto install to the Business Modeler IDE, you must select the EDA Serverand Rich Client Support template (edaserver_template.xml).

d. In the Installation Directory box, enter the location where you want to installthe Business Modeler IDE. The Business Modeler IDE files are installed to abmide subdirectory.

e. Click Next.

4. If you selected the Business Modeler IDE 2-tier option, perform the followingsteps 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.

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.

5. If you selected the Business Modeler IDE 4-tier option, perform the followingsteps 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 Middle-tier Servers table if you wantto add another server to connect to.

c. Click Next.

6. 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.3, use Java Development Kit 1.6.0_14 (JDK 6 Update 14). ClickNext.

7. Perform the following steps in the Business Modeler IDE Client panel:a. Click the Add button to the right of the table to select the templates toinstall. Templates contain the data model for Teamcenter solutions. The


Install the Business Modeler IDE

Teamcenter Foundation template is installed by default. The Foundationtemplate contains the data model used for core Teamcenter functions. Allcustomer templates must extend the Foundation template.

Select the same templates that were installed on the server so that youcan see the same data model definitions in the Business Modeler IDE thatwere installed on the server.

Tip

Make sure that you select the same templates that are on theserver. To find the templates installed on the server, look in theTC_DATA\model directory on the server.

Note

If you installed the EDA option to the Business Modeler IDE,select the EDA Server and Rich Client Support template(edaserver_template.xml).

b. If you have any templates of your own to install or a template from athird-party, click the Browse button and browse to the directory where thetemplates are located.

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.3, if a baseline was taken.

• lang\template-name_template\language_locale.xmlContains the text that is displayed in the Business Modeler IDE userinterface for all languages.

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



For instructions about how to run the Business Modeler IDE, see Start theBusiness Modeler IDE.

Install the Business Modeler IDE to an existing Eclipse environmentIf you already have an 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.5.0 (Galileo) package installed. To downloadEclipse, see the following URL:

http://www.eclipse.org/downloads/packages/

Siemens PLM Software recommends that you install Eclipse Classic 3.5.0.

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.

After unzipping the plug-ins, verify their installation at ECLIPSE_HOME.

4. Create a LocalSites directory on your computer, and create the followingsubdirectories: CDT, DTP, EMF, GEF, JDT, and WTP.

5. Perform the following steps to extract the remaining plug-ins from theadditional_applications\bmide_plugins directory.

a. Extract each of the following archive files into its corresponding LocalSitessubdirectory. These archives contain plug-ins required by the BusinessModeler IDE.

• cdt-master-version.zip

Unzip to the CDT directory. This contains the C/C++ DevelopmentToolkit (CDT) plug-ins. CDT provides the capability to work withprojects that use C or C++ as a programming language.

• dtp-sdk_version.zip

Unzip to theDTP directory. This contains the Data Tools Platform (DTP)plug-ins. DTP provides a number of tools for working with data sources.

• eclipse-JDT-SDK-version.zip

Unzip to the JDT directory. This contains the Java Development Tools(JDT) plug-ins. JDT provides tools for implementing a Java IDE.

• emf-xsd-SDK-version.zip



Unzip to the EMF directory. This contains the Eclipse ModelingFramework (EMF) plug-ins. EMF is a modeling framework and codegeneration facility for building tools and other applications based ona structured data model.

• GEF-ALL-version.zip

Unzip to the GEF directory. This contains the Graphical EditingFramework (GEF) plug-ins. GEF allows developers to take an existingapplication model and create a graphical editor.

• wtp-sdk-R-version.zip

Unzip to the WTP directory. This contains the Web Tools Platform(WTP) plug-ins. WTP helps you develop Web and Java EE applications.

b. If you need language support, create the required subdirectories underLocalSites and extract the appropriate language pack to the correspondingsubdirectory:

• NLpack1-GEF-SDK-version.zip

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

• NLpack2-GEF-SDK-version.zip

Contains the GEF language pack for Czech, Hungarian, Polish, andRussian.

• NLpack2a-GEF-SDK-version.zip

Contains the GEF language pack for Danish, Dutch, Finnish, Greek,Norwegian, Portuguese, Swedish, and Turkish.

• NLpackBidi-GEF-SDK-version.zip

Contains the GEF language pack for Arabic and Hebrew.

6. Launch Eclipse by running the eclipse file from the eclipse directory. WhenEclipse opens, set the workspace if asked, and close the Welcome tab if itappears.

7. Install the remaining plug-ins using the Eclipse installation feature.

For more information about installing plug-ins to Eclipse, see the followingarticle:

http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.user/tasks/tasks-124.htm

a. Choose Help→Install New Software from the top menu bar.

The Available Software dialog box is displayed.

b. Clear the Group items by category check box.


http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.user/tasks/tasks-124.htm


Note

You must clear this check box to see the plug-in items to be installed.

c. In the Available Software dialog box, click the Add button to the right of theWork with box.

The Add Site dialog box is displayed.

d. In the Add Site dialog box, click the Local button and browse to eachsubdirectory under the LocalSites directory, for example, CDT\eclipse,DTP\eclipse, and so on.

As you add each site, type a name for each in the Name box in the Add Sitedialog box. As you add sites, the plug-in items display on the AvailableSoftware dialog box.

e. In the Available Software dialog box, click the arrow in the Work with boxand choose each site in turn (for example, CDT, DTP, and so on).

The plug-in items are displayed in the pane.

Note

You must clear the Group items by category check box to see theplug-in items. If you leave it selected, you may see the message:

There are no categorized items

Select the Hide items that are already installed check box to only seeuninstalled features.

f. Select all the items for the site and click Next to install them.

Install all the sites (CDT, DTP, and so on).

8. Install the Business Modeler IDE development templates using TeamcenterEnvironment Manager (TEM).

In the Select Features panel, choose Extensions→PlatformExtensibility→Business Modeler Templates. 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.

For instructions about how to run the Business Modeler IDE, see Start the BusinessModeler IDE.

Allocate memory to the Business Modeler IDEAllocate memory to the Business Modeler IDE so that it has enough to launch andrun.



Note

If you perform operational data updates, you must have a minimum of 4 GBof RAM on the system running the Business Modeler IDE to allow for otherprocesses.

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. Ifyour system has more memory that you can allocate to the Business ModelerIDE, you can set the value higher.

Caution

Because Java standards require that no more than 25 percent of total RAM beallocated to virtual memory, if the amount allocated to the Business ModelerIDE is higher than 25 percent of total RAM, memory disk swapping occurs,with possible performance degradation.

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

For instructions about how to run the Business Modeler IDE, see Start the BusinessModeler IDE.



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.

Run the bmide.sh file in the install-location/bmide/client directory.

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

You must have a minimum of 4 GB of RAM on the system running theBusiness Modeler IDE to allow for other processes.

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 theWorkbench button in the right side of theWelcomewindow.

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

11 Installing a custom solution orthird-party template

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

Update the database using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3


Chapter

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

Warning

You should back up your data on a regular basis so that you can restore it inthe event of a template installation failure.

For more information, see the Business Modeler IDE Guide.

1. Copy the template files from the packaging directory on your Business 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.


Chapter 11 Installing a custom solution or third-party template

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 onlythe installable template (feature) file. Select your template’s feature file(feature_template-name.xml) and click the Select button.

The template appears as a new feature under Extensions in the Select Featurespanel.

You can change the location of the feature in the Select Features panel and adda new group to place the feature under.

9. Select the new template in the Select Features panel. 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.

Note

If the installation fails because of invalid data model, perform thefollowing 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 filesto the server 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 modeand continue 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.


Installing a custom solution or third-party template

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

Note

To have libraries read on the user system, the TC_LIBRARY environmentvariable must be set to the platform-specific shared library path. Thisenvironment variable is set to the LD_LIBRARY_PATH (Solaris, Linux,or HP-UX Itanium), LIB_PATH (AIX), or SHLIB_PATH (HP-UX)environment variable, depending on the platform detected when theTeamcenter session is initiated.

Update the database using TEMIf 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.

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 for working with the Business ModelerIDE Client option under Business Modeler only if you want to add orupdate a dependent template to your Business Modeler IDE.

7. Click Next

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

The Update Database panel displays currently installed templates.

9. Click the Browse button to navigate to the directory where the packagedtemplate files are located. Select the updated template-name_template.zip file.

10. Select your template on the table and click Next.

11. In the Confirm Selections panel, click Next.


Chapter 11 Installing a custom solution or third-party template

The new template is installed.

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

12 Manufacturing

Populate the database for Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Planning data migration from Genius4000 to Resource Manager . . . . . . . . . . 12-1

Migrate Genius4000 data to Resource Manager . . . . . . . . . . . . . . . . . . . . . . . 12-3


Chapter

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

Populate the database for ManufacturingTo install the Manufacturing Resource Library on a UNIX server, you must use aWindows rich client. If you do not have one in your network, you must add onetemporarily. After you do this, start the setup program on the Windows installationCD-ROM in the following directory:

advanced_installations\resource_management\server

For more information about installation the Manufacturing Resource Library, seethe Installation on Windows Servers Guide.

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.


http://support.plms-eds.com

Chapter 12 Manufacturing

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

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




Manufacturing

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


Chapter 12 Manufacturing

Software GTAC FTP server. Use the migration procedure described in theInstallation on Windows Servers Guide.


Chapter

13 Installing Teamcenter’s reportingand analytics

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Create the Reporting and Analytics database . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Configure the Reporting and Analytics license file . . . . . . . . . . . . . . . . . . . . . 13-2

Install Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Install Remote Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Deploy Reporting and Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Complete Reporting and Analytics installation . . . . . . . . . . . . . . . . . . . . . . . 13-5


Chapter

13 Installing Teamcenter’s reportingand analytics

Install and configure Teamcenter’s reporting and analytics in a new or existingTeamcenter configuration.

Before you beginDownload the Teamcenter’s reporting and analytics software distribution image(TeamcenterReportingAndAnalytics-8.n-platform.tar ) from the Siemens PLMSoftware FTP site.

Reporting and Analytics requires additional preinstallation steps. For informationabout steps to perform before you install Reporting and Analytics, see the currentversion of the Teamcenter Reporting and Analytics Deployment Guide in theReporting and Analytics software distribution image.

Create the Reporting and Analytics databaseReporting and Analytics requires an Oracle, Microsoft SQL Server, or IBM DB2database for Reporting and Analytics metadata. Your database administrator mustcreate this database before you launch Teamcenter Environment Manager (TEM) toinstall 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 13 Installing Teamcenter’s reporting and analytics

For more information about creating the metadata database for Reporting andAnalytics, see Pre Installation Steps in the Teamcenter Reporting and AnalyticsDeployment Guide for the current version of Reporting and Analytics.

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.

Note

For information about starting the Reporting and Analytics license server, seethe Teamcenter’s reporting and analytics Deployment Guide in the Reportingand Analytics software distribution image.

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 TcRA Install Options and General Settings panel. Select oneor more of the following options to include in your Reporting and Analyticsinstallation:

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.


Installing Teamcenter’s reporting and analytics

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.

The remaining sequence of TEM panels varies according to the options you select.

4. Enter the required information in TEM for the selected Reporting and Analyticsoptions.

Note

For more information about TEM panels, click Help in the given TEMpanel.

Selected option TEM panel Tasks

Create licenseserver

TcRA License Server Settings Enter the location of the Reporting andAnalytics license file (license.dat), thelicense authentication time-out in seconds,and license keystore settings for theReporting and Analytics license server.

Create WAR file TcRA WAR Settings Type the Web application context, servername, and port for the Reporting andAnalytics Web application.

Create licenseserver

TcRA License Settings Type the host and port of the Reporting andAnalytics license server.

Create metadata TcRA Metadata Settings Specify metadata settings for the Reportingand Analytics integration.

Note

The values you type under OracleTablespace Names must match thenames of the Oracle tablespaces youcreated in Create the Reporting andAnalytics database.

Any or none TcRA Database Selection Specify the database engine you use forReporting and Analytics (Oracle, MicrosoftSQL Server, or IBM DB2) and type therequired values for the Reporting andAnalytics database you created in Create theReporting and Analytics database.

Create WAR file TcRA WAR and MetadataSettings

Type an owner for Reporting and Analyticsmetadata and select your Web applicationserver vendor (WebSphere or WebLogic).(for Oracle WebLogic).



Selected option TEM panel Tasks

Create WAR file TcRA Authentication Settings Select the Reporting and Analyticsauthentication method (eQube, SSO, orWindows NTLM) and specify relatedsettings.

Note

Selecting SSO Authenticationrequires that you install Teamcenterwith Security Services enabled andconfigure the LDAP server before youinstall Reporting and Analytics.

For information about installingSecurity Services, see the SecurityServices Installation/Customizationguide.

Create WAR file TcRA WAR SMTP Properties Specify SMTP settings to enable usersto receive e-mail messages generated byReporting and Analytics.

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

During installation, TEM prompts you for the location of the TCRA2008.zip file.

When installation is complete, close TEM.

Install Remote Reporting and AnalyticsInstall Remote Reporting and Analytics as described in Deployment of Remote TcRA8.1 with Tc8 in the Teamcenter’s reporting and analytics software distribution image.

Deploy Reporting and AnalyticsDeploy the Reporting and Analytics WAR file as described in the Teamcenter’sreporting and analytics Deployment Guide in the Reporting and Analytics softwaredistribution image.

Note

Before you deploy the Reporting and Analytics WAR file, make sure thatRemote Reporting and Analytics is installed and running.

For more information, see Deployment of Remote TcRA 8.1 with Tc8 in theReporting and Analytics software distribution image.


Installing Teamcenter’s reporting and analytics

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

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

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

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.

3. Log on to the Reporting and Analytics administrative console using user nameADMIN and password ADMIN.

Click Manage Instance→Properties, and then set the following values asappropriate:

• SMTP Host

• Authentication required for SMTP (Set to True or False)

• SMTP User ID

• SMTP User Password



4. If Reporting and Analytics is installed with Security Services enabled, set thefollowing values for the Teamcenter connection (Connection 1):

• Set the user ID and password values to the LDAP user ID and password.

• Under Advanced Properties, set SSO Enabled to yes, and set the SSOApplication ID to the Teamcenter application ID.

Note

For information about using the Reporting and Analytics integration, see theReport Builder Guide.


Chapter

14 Installing Render Management

Prerequisites for rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Install Render Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Complete Render Management installation . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4Render document options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5Validating pdfgenerator by translating files from the command line . . . . . . 14-5Viewing document rendering logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5


Chapter

14 Installing Render Management

During installation using Teamcenter Environment Manager (TEM), along with theselections made to support general installation, your administrator must select toinstall the following features to support document rendering. The administrator canaccept default values unless otherwise directed.

Note

This topic describes an installation using a single server machine. Installationin a distributed configuration using multiple server machines is supported.

Prerequisites for renderingThe prerequisites for rendering documents in Teamcenter include the following:

• Install and configure one or both of the following:

– Teamcenter 8.3 lifecycle visualization Convert and Print, Ghostscript version8.53 (Asian font version) and MS Office XP, 2003 or 2007.

– Adobe LifeCycle PDF Generator ES version 8.2.1, Adobe Acrobat, and asource format authoring application (for example, MS Office: 2003, XP, or2007).

Note

For information about downloading GhostScript, see the following URL:

http://www.ghostscript.com/

• Install document render functionality by installing and configuring a DispatcherServer and Dispatcher Client, under Corporate Server, in TeamcenterEnvironment Manager (TEM).

For more information, see Getting Started with Dispatcher (TranslationManagement) and the Dispatcher Server Translators Reference Guide.

• Install and configure the previewservice, rendermgttranslator, andpdfgenerator (supported by default only on Windows) translators.

For information about verifying that translators are configured for rendermanagement, see the Dispatcher Server Translators Reference Guide.

• Set up item revision definition configuration (IRDC) and dispatcher serviceconfiguration objects and deploy to the Teamcenter database.


Chapter 14 Installing Render Management

For more information about working with document management IRDC objectsand dispatcher service configuration objects, see the Business Modeler IDEGuide.

The software needed for rendering is dictated by the available input formats and therequired output formats.

Input format1 Output format Required software

MS Office, PostScript PDF Teamcenter 8.3 lifecyclevisualization Convert,Ghostscript version 8.53 (Asianfont version) and MS Office: XP,2003 or 2007

MS Office PostScript Teamcenter 8.3 lifecyclevisualization Convert,Ghostscript version 8.53 (Asianfont version) and MS Office: XP,2003 or 2007

MS Office TIF Teamcenter 8.3 lifecyclevisualization Convert,Ghostscript version 8.53 (Asianfont version) and MS Office: XP,2003 or 2007

DXF, HPGL, Text,PostScript, PDF

Thumbnail(JPEG)

Teamcenter 8.3 lifecyclevisualization Convert,Ghostscript version 8.53 (Asianfont version)

MS Office (includingMicrosoft Project),PostScript, EncapsulatedPostScript (.eps), AdobePhotoshop (.psd),WordPerfect, Rich Text,Bitmap, GIF, JPEG, TIFFand multipage TIF

PDF Adobe LifeCycle PDF GeneratorES version 8.2.1, Adobe Acrobatand source format authoringapplication (for example, MSOffice 2003, XP, or 2007)

Install Render ManagementStart TEM and perform or verify the following selections:

1. In the Select Features panel, select the following features:

• Under Server Enhancements, select Sample files.

• Under Enterprise Knowledge Foundation, select Dispatcher Server,Dispatcher Client, Dispatcher Client for Rich Client, and Render Documentfor Rich Client.

1. Supported MS Office formats include Microsoft Word, Excel, PowerPoint, WordX, ExcelX and PPTX, unless otherwise noted.


Installing Render Management

Note

The docmgt_samples.xml file includes DispatcherServiceConfiginstances an administrator must deploy after creating a Business ModelerIDE template project.

Record the installation directory used for the Dispatcher Server andDispatcher Client. This is required in a later step. For example, you canuse:

C:\Program Files\Siemens\Teamcenter8\tc8rendering

2. In the Dispatcher Components panel, specify the Dispatcher root directory. Forexample, you can use:

C:\Program Files\Siemens\Teamcenter8\dispatcher

3. In the Dispatcher Components panel, select Install Module, and then enter aStaging Directory and Port for the module.

4. In the Dispatcher Settings, select Install Documentation, Start DispatcherServices, and Start Dispatcher Services as Windows Service.

5. In the Select Translators panel, under Document Management (DocMgt)Translators, select PdfGenerator and RenderMgtTranslator. Also, under TcVisTranslators, select PreviewService Translator.

6. In the Translator Settings panel, under TcVis Translators, enter the installationlocation for Teamcenter’s lifecycle visualization, and the Vis License value.Under Document Management (DocMgt) Translators, enter the paths to thewatched folder input and output directories, and a maximum wait time.

Note

The watched folder input and output directories must point to thesame location as the Adobe LiveCycle watched folder input and resultdirectories, respectively.

For more information about configuring these directories, see the AdobeLiveCycle ES documentation.

TEM updates the following files with the specified information:Dispatcher\Module\Translators\previewservice\previewservice.bat

and:

Dispatcher\Module\Translators\docmgt_translators\.....config\pdfgenerator_config.properties

7. For Dispatcher Client, specify and record a password.

To complete the configuration:

1. Verify that pdftranslator.bat is installed in the dispatcher root directory:

Dispatcher\Module\translators\docmgt_translators\pdfgenerator\pdftranslator.bat


http://www.adobe.com/products/livecycle/


Chapter 14 Installing Render Management

2. Verify the pdfgenerator_config.properties file under the dispatcher rootdirectory sets full paths for the Adobe PDF Generator ES watched input andresults folders:

For example, in:Dispatcher\Module\translators\docmgt_translators\

config\pdfgenerator_config.properties

Set:

• WatchedFolderInputDir=//pdfgenerator_server/LCWatchedFolder/input

• WatchedFolderResultDir=//pdfgenerator_server/LCWatchedFolder/result

Note

These case-sensitive paths can be in a shared network directory, butmust point to the same locations as the Adobe LiveCycle watchedfolder directories configured for GeneratePDFService WatchedFolderEndpoint. See the relevant documentation at the Adobe website,http://www.adobe.com/products/acrobat/, for instructions on how to set upWatchedFolder directories.

Caution

Windows services typically do not support mapped drives.

Complete Render Management installationAfter installation, the administrator can:

• Specify which translator to use in file conversion when there are multipletranslation services that can perform the conversion for rich client documentrendering on demand, during checkin, and in a workflow task using BusinessModeler IDE to configure IRDC and DispatcherServiceConfig businessobjects.

• Use Business Modeler IDE to set up necessary IRDC object configurations. Anitem revision must be under IRDC control for rendering to occur. For example,an IRDC configuration specifies dataset types to translate, and whether torender the item revision at checkin.

For more information about configuring IRDC objects, see the Business ModelerIDE Guide.

• Use Business Modeler IDE to select the service for file translation by settingDispatcherServiceConfig sort order priority for the previewservice serviceand for the pdfgenerator service. The service with the higher sort orderpriority is selected when you have multiple translation services defined with thesame settings for Source Dataset Type Name and Derived Dataset Type Name.You can also deselect the Service Available setting for a translation service tomake the service unavailable.

• Create access rules to grant access privileges to the dispatcher proxy user toupdate attributes of the dispatcher request object.


http://www.adobe.com/products/acrobat/

Installing Render Management

For more information about creating access rules, see Getting Started withDispatcher (Translation Management).

• Start the dispatcher services for the scheduler, module, and dispatcher client.

For more information about starting dispatcher services, see Getting Startedwith Dispatcher (Translation Management).

Render document options

After successful configuration, a My Teamcenter user in rich client can performsome or all of the following operations, depending on the setup of the IRDC andDispatcher service configuration.

• Use the Translation®Render Document menu command translation.

• Render a document revision during checkin.

• Render a document revision using the workflow task action handler.

• Use the Translate®Administration Console menu command to view the statusof the translation.

Validating pdfgenerator by translating files from the command line

You can use the pdfgenerator utility to translate files from the command line. Usethis to validate pdfgenerator translator.

Note

This utility works only on Windows.

For more information, see the Utilities Reference.

Viewing document rendering logs

• If you have set up Log Manager, you can see the document render logs in theLog Manager directory.

For more information about Log Manager, see Getting Started with Dispatcher(Translation Management).

• If you have configured logging for dispatcher requests, you can see the documentrender logs in the Request Administration Console.

For more information about using the Request Administration Console, seeGetting Started with Dispatcher (Translation Management).


Chapter

15 Installing Teamcenter online help

Install online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Install online help to a local host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Install online help to a network location . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Install online help to a Web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Configure online help access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3Configure online help for the thin client . . . . . . . . . . . . . . . . . . . . . . . . . 15-4Configure online help for the rich client using TEM . . . . . . . . . . . . . . . . . 15-4Configure online help for the rich client using Web Application Manager . . 15-5


Chapter

15 Installing Teamcenter online help

Teamcenter provides an online help collection that contains guides for all Teamcenterapplications and clients. This collection can be viewed in a Web browser.

Note

Teamcenter online help requires a supported Web browser and the appropriateJava plug-in for your platform.

For information about supported Web browsers and Java versions, see theSiemens PLM Software Certification Database:


Teamcenter provides two ways to access online help:

• Web server

Online help is installed on a Web server and accessed using HTTP protocol.

• Direct access

Online help is installed on a local host or a network file location and accessedusing FILE protocol. This is option is not available for the thin client.


Chapter 15 Installing Teamcenter online help

Install the online help collection using the method that suits your Teamcenternetwork. Then, if necessary, configure access to online help.

For information about using online help in Teamcenter client interfaces, see the RichClient Interface Guide or the Thin Client Interface Guide.

Install online helpInstall the online help collection on a local host, a network location, or a Web server.

Install online help to a local host

1. Launch Teamcenter Environment Manager (TEM). Create a new configurationor select the existing configuration to which you want to add online help.

2. Proceed to the Select Features panel.

3. Under Server Enhancements, select the Online Help feature.

4. Proceed through the remaining panels to the Confirm Selections panel, andthen click Next to install the online help feature.

During installation, TEM prompts for the location of the online help files. Enterthe path to the location that contains the tchelp.jar file on the Teamcenterdocumentation distribution image.

Install online help to a network location

1. Install Teamcenter online help on a host in your network using one of thefollowing methods:

• Install Teamcenter online help using Teamcenter Environment Manager(TEM) as described in Install online help to a local host.

This places online help files in the TC_ROOT/help directory.

• Extract the tchelp.jar file from the Teamcenter 8.3 documentationdistribution image to a directory on the host.

This places online help files in a subdirectory named help.

2. Set permissions for the online help directory (help) to allow access to Teamcenterhosts.

Install online help to a Web server

You install online help on a Web server as part of a thin client Web application. Thisprovides online help for the thin client that can also be accessed by rich client hostsas described in Configure online help access.


2. Click Add to create a new Web application.


Installing Teamcenter online help

3. In the Add Web Application dialog box, type a name and enter a staging locationfor the online help Web application.

In the Solution Type box, select Thin Client.

4. In the Disk Locations for Install Images box, enter the path to the tchelp.jarfile, which contains the contents of the online help collection.

Note

The tchelp.jar file is on the Teamcenter 8.3 documentation distributionimage.

5. Click Solutions.

6. In the Select Solutions dialog box, select the Teamcenter - Online Help solution,and then click OK.

7. In the Add Web Application dialog box, click OK.

8. In the Modify Required Context Parameters dialog box, click OK.

The Web Application Manager builds the online help Web application.

9. Locate the deployable file generated during installation. This file is in thedeployment directory under the specified staging location.


Configure online help accessAfter you install online help on a local directory, a network location, or a Web server,you can configure access to that online help from other rich client hosts and otherthin client Web applications.

Note

• If you install online help using TEM as described in Install online help toa local host, no further configuration is needed to access to online help onyour local host.

• If you install online help for thin client users as described in Install onlinehelp to a Web server, no further configuration is required to enable onlinehelp access for the given thin client Web application.




Configure online help for the thin clientNote

This procedure assumes you have an existing deployed thin client Webapplication that contains the Teamcenter - Online Help solution. The followingsteps describe how to configure a separate thin client Web application toaccess the existing Web-deployed online help.

For information about creating a thin client Web application that containsTeamcenter online help, see Install online help to a Web server.


2. Add or modify a thin client Web application.

When you choose solutions, do not include the Teamcenter - Online Help solution.

3. After the Web Application Manager builds the Web application, locate thedeployable file in the deployment directory under the specified staging location.Deploy the Web application as described in the Web Application DeploymentGuide.2

4. Launch Teamcenter and modify the following Teamcenter preferences to addthe full path to the online help files:

WEB_help_serverWEB_core_help_server

When you install online help as part of a thin client Web application, the helpURLs are automatically configured correctly using a relative path to the helpfiles.

Configure online help for the rich client using TEM

1. Launch TEM and create a new Teamcenter configuration.

2. In the Select Features panel, select the two-tier or four-tier rich client, butdo not select the Online Help feature.

Note

For more information about installing a two-tier rich client, see theInstallation on UNIX and Linux Clients Guide.

For more information about installing a four-tier rich client using TEM,see the Installation on UNIX and Linux Clients Guide.

3. Proceed to the Online Help panel.

4. In the Online Help panel, specify how you want the rich client to access onlinehelp.



Installing Teamcenter online help

• Direct access from a network file location:

1. Select Direct Access.

2. In the Help Files Directory box, enter the path to the installed onlinehelp, for example, /tc/help.

• Access from a Web server:

1. Select Via Web Server.

2. In the URL Location box, type the URL to the location of the Teamcenteronline help collection, for example, http://host:port/tc/help.

3. Proceed through the remaining panels to complete the rich client installation.

Note

The Online Help panel is not displayed when you launch TEM in maintenancemode. If you select Do not configure Online Help when you install therich client, you cannot configure access to online help for that Teamcenterconfiguration later.

Configure online help for the rich client using Web ApplicationManager


2. Create or modify a rich client distribution instance.

In the Modify Required Context Parameters dialog box, specify how you wantthe rich client to access online help by setting context parameters as follows.

• Direct access from a network file location.

Context parameter Value

RichClientHelpWebServer Specify file://.RichClientHelpLocation Specify the path to the location that contains

the online help collection for both Windowsand UNIX systems.3

• Access from a Web server.


RichClientHelpWebServer Specify http://host-name:port, replacinghost-name and port with the host nameand port for the deployed thin client Webapplication that contains the online help (theTeamcenter - Online Help solution).

3. The Web Application Manager adds index.htm to this path.




RichClientHelpLocation Specify the subpath to the deployed Webapplication, for example, tc/help.4

For more information about these parameters, see Rich client distributioninstance requirements.

Note

For more information about creating a rich client distribution instance,see Install rich client distribution instances.

For more information about modifying an existing rich client distributioninstance, see Add components to the distribution server instance.

3. After you set context parameters, click OK.

The Web Application Manager builds the rich client distribution instance.

4. Locate the deployable file generated during installation. This file is in thedeployment directory under the specified staging location.


5. Launch Teamcenter and modify the following Teamcenter preferences to addthe full path to the online help files:

WEB_help_serverWEB_core_help_server

When you install online help as part of a thin client Web application, the helpURLs are automatically configured correctly using a relative path to the helpfiles.

4. The Web Application Manager adds index.htm to this path.5. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choosethe appropriate procedure for the application server you use.


Part

VI Additional configuration andmaintenance

Managing installations and configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

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

Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Installing Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Installing Teamcenter maintenance packs . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Uninstalling Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1


Chapter

16 Managing installations andconfigurations

Create a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Modify a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Add an existing Teamcenter database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Add or configure a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

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


Chapter

16 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 (TEM):

a. Change to the install directory in the Teamcenter application root directoryfor your Teamcenter installation.


2. In the Maintenance panel, choose Configuration Manager.

3. In the Configuration Maintenance panel, choose Create new configuration.

4. In the New Configuration panel, type a description and unique ID for the newconfiguration.

5. In the Solutions panel, optionally select one or more solutions.

For a description of a solution, point to the solution name in TEM or seeTeamcenter solutions.

Note

Solutions are preselected groups of features that provide starting pointsfor recommended Teamcenter configurations. You can add features ordeselect features in the Select Features panel in Teamcenter EnvironmentManager (TEM).

6. In the Select Features panel, select features to include in the configuration.

For a description of a feature, point to the feature name in TEM or seeTeamcenter features.


Chapter 16 Managing installations and configurations

7. Proceed through the remaining panels in TEM, entering the required informationfor the features you selected. For information about each panel, click Help.

8. When TEM displays the Confirm Selections panel, click Next to begininstallation.

Modify a configurationAdd Teamcenter features to an existing configuration, or remove them from aconfiguration:


a. Change to the install directory in the Teamcenter application root directoryfor your Teamcenter installation.


2. In the Maintenance panel, choose Configuration Manager.

3. In the Configuration Maintenance panel, choose Perform maintenance on anexisting configuration.

4. In the Configuration Selection panel, select the configuration you want tomodify.

Teamcenter Environment Manager displays the Configure Components panel.

5. In the Feature Maintenance panel, choose Add/Remove Features.

Note

The Feature Maintenance panel provides a variety of options, dependingon the features in your configuration.

For information about other options, see the Teamcenter EnvironmentManager online help.

6. In the Select Features panel, select features to add to the configuration, ordeselect features you want to remove.

7. Proceed through the remaining panels in TEM, entering the required informationfor the features you selected. For information about each panel, click Help.

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


Managing installations and configurations

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.

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 (IBM DB2 or Oracle).

• 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, seeDatabase 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. 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. For example, to configure richclient 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


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.

1. For more information about configuring JBoss Cache TreeCache and setting TreeCache parameters, see www.jboss.org/jbosscache.The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jgroups.org.





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

17 Deploying localized versionsof Teamcenter

Configuring client display language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2Choose a display language for the thin client . . . . . . . . . . . . . . . . . . . . . . 17-2Choose a display language for the rich client . . . . . . . . . . . . . . . . . . . . . . 17-2

Environment settings for non-English locales . . . . . . . . . . . . . . . . . . . . . . . . 17-3Environment settings for UTF-8 environments . . . . . . . . . . . . . . . . . . . . 17-4Environment settings for non-UTF-8 environments . . . . . . . . . . . . . . . . . 17-7

Deploying localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10Deploying thin client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10Update thin client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10Create a thin client localization . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11Convert the thin client user interface for Hebrew . . . . . . . . . . . . . . . 17-13

Deploying rich client localizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13Display Siemens PLM Software-provided rich client localizations . . . 17-13Update rich client localized text . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13


Chapter

17 Deploying localized versionsof Teamcenter

Siemens PLM Software provides localized versions of Teamcenter in the followinglanguages:

Language Locale code

Chinese (Simplified) zh_CN

Chinese (Traditional) zh_TW

Czech cz_CZ

English en_US

French fr_FR

German de_DE

Hebrew en_US1

Italian it_ITJapanese ja_JPKorean ko_KR

Polish pl_PLRussian ru_RU

Spanish es_ES

Use the appropriate locale codes to deploy Teamcenter localizations or launchTeamcenter clients in a desired locale.

If you provide your own localizations for locales not provided by Siemens PLMSoftware, use the appropriate Java standard locale codes similar to the locale codesin the preceding table.2

For more information about localizing Teamcenter, see the Localization Guide.

1. The locale code for Hebrew is en_US because Siemens PLM Software does not yet provide a Hebrew translation. The en_US codeallows data entry in Hebrew, but interface text is in English.2. Standard locale codes are composed of a two lowercase character language code from the ISO 639-1 standard, followed by anunderscore, followed by a two uppercase character country code from the ISO 3166-1-alpha-2 standard.


Chapter 17 Deploying localized versions of Teamcenter

Configuring client display languageBy default, Teamcenter clients display in the language specified by your operatingsystem locale settings. If you want to override the default language, perform theappropriate procedure to choose the display language for the thin client or the richclient.

Choose a display language for the thin client

At each logon, you can choose between multiple languages, depending on yourcompany’s policy and installation. There are two ways you can specify the language:

• Specify the language in the URL. For example:

– To specify French, type http://sdlc:7001/tc/webclient?lang=fr in the URL.

– To specify Russian, type http://sdlc:7001/tc/webclient?lang=ru in the URL.

Note

When specifying a language in the URL, use standard W3C localeidentifiers.

For more information, see the following URL:

http://www.w3.org/TR/ltli/

• Specify the language in your browser preferences.

Your ability to set the language for the thin client depends on the character setencoding of the Teamcenter server host and also the character set encoding of theTeamcenter database.

Note

To prevent mixed-language display after you change the thin client displaylanguage, clear your Web browser cache. This prevents the interface fromdisplaying in mixed languages.

For more information about configuring language display during installation, seeInstalling thin client Web applications.

Choose a display language for the rich client

By default, the rich client is displayed in the language specified by the operatingsystem.

Note

Your ability to set the language for the rich client depends on the character setencoding of the Teamcenter server host and also the character set encodingof the Teamcenter database.

For more information about configuring language display during installation,see Installing rich client Web applications.


Deploying localized versions of Teamcenter

Note

If you find that Asian multibyte characters do not display correctly in the richclient, set your system font to a font that supports Asian multibyte characters.For example, on Microsoft Windows systems, the Arial Unicode MS font canbe set to Message Box to correct this problem.

Similarly, if you find that Asian multibyte characters do not display correctlywhen you start the rich client using the native language (-nl) option, restartyour system in the appropriate locale and set your system font to a font thatsupports Asian multibyte characters.

If you want to override the default language to launch the rich client in a desiredlanguage, add the -nl argument to the rich client launch command:

TC_ROOT/start_portal –nl locale-code

Replace TC_ROOT with the Teamcenter home directory, and replace locale-code withthe desired locale code listed in Deploying localized versions of Teamcenter.

For example, to launch the rich client Italian user interface, enter the followingfrom a command prompt:

/tc/rac/start_portal –nl it_IT

Note

To prevent mixed-language display the next time you run the rich clientafter you change the –nl argument value, or after you change your operatingsystem locale, delete the Teamcenter directory under your user directory($HOME/Teamcenter3).

Environment settings for non-English localesTeamcenter is supported in the following locales on all server platforms:

• Chinese (Simplified)• Chinese (Traditional)• Czech• English• French• German• Hebrew• Italian• Japanese• Korean• Polish• Russian• Spanish

3. $HOME is your user home directory.



To ensure correct display and processing of Teamcenter data, set the required valuesin your operating system environment. Use the appropriate values for your localeand platform.

Environment settings for UTF-8 environments

Support for the Unicode UTF-8 character set in Teamcenter is restricted to UNIX orLinux platforms that are configured to run the Unicode UTF-8 operating system. Anew database installation is required with Unicode UTF-8 character set support.

You must configure your Teamcenter installation to run the UTF-8 character set,observing the following considerations:

• Your platform administrator must configure the system to run the UnicodeUTF-8 character set operating system using CDE (Common DesktopEnvironment) on UNIX systems, or KDE on Linux systems. This is required sothat all software running in this operating system environment understands thedefault character set is UTF-8.

• If you use Linux, your Linux platform administrator must configure the machineto run Unicode UTF-8 character set operating system by default. This enablesall software running on this platform operating system to understand the defaultUTF-8 character set.

• Make sure you configure your operating system to run Unicode UTF-8 beforeyou configure a Teamcenter two-tier or four-tier server installation to run theUTF-8 character set.

• You must configure the Teamcenter thin client to connect to a four-tier UTF-8server installation running on a Unicode UTF-8 UNIX or Linux operatingsystem.

The thin client can be run in a Web browser on any Siemens PLM Softwaresupported platform and language character set encoding operating system.

• A new Teamcenter installation may configure support for the Unicode UTF-8character set to install a new database configured with Unicode UTF-8 characterset support.

Note

• The thin client or the four-tier rich client can run on any platform(Windows, UNIX, or Linux) running any language character set.

• Rich client hosts must have the appropriate fonts installed for charactersto display properly.

Warning

If your Teamcenter database server uses the UTF-8 character set, you mustnot install your Teamcenter corporate server on a Windows host. Teamcenterdata from a UTF-8 database may display incorrectly in a two-tier rich client onWindows and can become corrupted if you modify data using a Windows-basedcorporate server or two-tier rich client.



The following illustration shows a sample Teamcenter configuration for restrictedUnicode UTF-8 character set support with clients displaying multiple locales. UNIXservers in this configuration run a Unicode UTF-8 character set operating system.

Unicode homogeneous server platform configuration

Environment settings on UNIX and Linux systems (UTF-8)Value

Locale SettingIBM AIX HP HP-UX

SunSolaris Linux

Database character set1 UTF8 UTF8 UTF8 UTF8Chinese(Simplified)

Server character set UTF-8 UTF-8 UTF-8 UTF-8

LANG and LC_ALL2 ZH_CN.UTF-8 zh_CN.utf8 zh_CN.UTF-8 zh_CN.utf8

TC_language_default3 zh_CN zh_CN zh_CN zh_CN

Database character set1 UTF8 UTF8 UTF8 UTF8Chinese(Traditional)


LANG and LC_ALL2 ZH_TW.UTF-8 zh_TW.utf8 zh_TW.UTF-8 zh_TW.utf8

TC_language_default3 zh_TW zh_TW zh_TW zh_TW

Czech Database character set1 UTF8 UTF8 UTF8 UTF8

Notes:

1. Applies only to Oracle databases.2. Set in the system environment variables.3. Set in the TC_language_default site preference.





SunSolaris Linux


LANG and LC_ALL2 CS_CZ.UTF-8 cs_CZ.utf8 cs_CZ.UTF-8 cs_CZ.utf8

TC_language_default3 cs_CZ cs_CZ cs_CZ cs_CZ

English Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 EN_US.UTF-8 en_US.utf8 en_US.UTF-8 en_US.utf8

TC_language_default3 en_US en_US en_US en_US

French Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 FR_FR.UTF-8 fr_FR.utf8 fr_FR.UTF-8 fr_FR.utf8

TC_language_default3 fr_FR fr_FR fr_FR fr_FR

German Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 DE_DE.UTF-8 de_DE.utf8 de_DE.UTF-8 de_DE.utf8

TC_language_default3 de_DE de_DE de_DE de_DE

Hebrew Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 HE_IL.UTF-8 iw_IL.utf8 he_IL.UTF-8 he_IL.utf8


Italian Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 IT_IT.UTF-8 it_IT.utf8 it_IT.UTF-8 it_IT.utf8

TC_language_default3 it_IT it_IT it_IT it_IT

Japanese Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 JA_JP.UTF-8 ja_JP.utf8 ja_JP.UTF-8 ja_JP.utf8

TC_language_default3 ja_JP ja_JP ja_JP ja_JP

Korean Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 KO_KR.UTF-8 ko_KR.utf8 ko_KR.UTF-8 ko_KR.utf8

TC_language_default3 ko_KR ko_KR ko_KR ko_KR

Polish Database character set1 UTF8 UTF8 UTF8 UTF8


Notes:






SunSolaris Linux

LANG and LC_ALL2 PL_PL.UTF-8 pl_PL.utf8 pl_PL.UTF-8 pl_PL.utf8

TC_language_default3 pl_PL pl_PL pl_PL pl_PL

Russian Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 RU_RU.UTF-8 ru_RU.utf8 ru_RU.UTF-8 ru_RU.utf8

TC_language_default3 ru_RU ru_RU ru_RU ru_RU

Spanish Database character set1 UTF8 UTF8 UTF8 UTF8


LANG and LC_ALL2 ES_ES.UTF-8 es_ES.utf8 es_ES.UTF-8 es_ES.utf8

TC_language_default3 es_ES es_ES es_ES es_ES

Notes:


Note

• To verify the character set in your server environment, enter thelocale charmap command.

• In Hebrew locales, set the following additional variables:

1. In the TC_DATA/tc_profilevars file, set TC_XML_ENCODING toUTF-8.

2. In the TC_ROOT/iiopservers/Start_TcServer1 fileand the TC_ROOT/pool_manager/mgrstartMYDB, setTC_CHARACTER_ENCODING_SET to UTF8.

Environment settings for non-UTF-8 environments

For non-English locales on UNIX systems, you must specify the system locale whenlogging on to the system using CDE (Common Desktop Environment) on UNIXsystems or KDE on Linux systems. The LANG and LC_ALL environment variablesmust be identical to function properly. Set these and other values as described inthe following table.



Environment settings on UNIX and Linux systems (non-UTF-8)

Value

Locale Setting IBM AIX HP HP-UX Sun Solaris Linux

Database characterset1

ZHS16CGB231280or ZHS16GBK




Chinese(Simplified)

Server character set UTF-8 CGB2312-80 CGB2312-80 CGB2312-80

LANG and LC_ALL2 ZH_CN.UTF-8 zh.GBK zh_CN.GBK zh_CN.gbk

TC_language_default3 zh_CN zh_CN zh_CN zh_CN


ZHT16BIG5 ZHT16BIG5 ZHT16BIG5 ZHT16BIG5Chinese(Traditional)

Server character set BIG5 BIG5 BIG5 BIG5

LANG and LC_ALL2 Zh_TW.big5 zh_TW.big5 zh_TW.BIG5 zh_TW

TC_language_default3 zh_TW zh_TW zh_TW zh_TW

Czech Database characterset1

EE8ISO8859P2 EE8ISO8859P2 EE8ISO8859P2 EE8ISO8859P2

Server character set ISO8859-2 ISO8859-2 ISO8859-2 ISO8859-2

LANG and LC_ALL2 cs_CZ.ISO8859-2 cs_CZ.iso88592 cs_CZ.ISO8859-2 cs_CZ

TC_language_default3 cs_CZ cs_CZ cs_CZ cs_CZ

English Database characterset1

WE8ISO8859P1 WE8ISO8859P1 WE8ISO8859P1 WE8ISO8859P1


LANG and LC_ALL2 en_US.ISO8859-1 en_US.iso88591 en_US.ISO8859-1 en_US


French Database characterset1



LANG and LC_ALL2 fr_FR.ISO8859-1 fr_FR.iso88591 fr_FR.ISO8859-1 fr_FR

TC_language_default3 fr_FR fr_FR fr_FR fr_FR

German Database characterset1



LANG and LC_ALL2 de_DE.ISO8859-1 de_DE.iso88591 de_DE.ISO8859-1 de_DE

TC_language_default3 de_DE de_DE de_DE de_DE

Hebrew Database characterset1

IW8ISO8859P8 IW8ISO8859P8 IW8ISO8859P8 IW8ISO8859P8

Notes:

1. Applies only to Oracle databases.2. Set in the system environment variables.3. Set the TC_language_default site preference.




Value



LANG and LC_ALL2 iw_IL iw_IL.iso88598 he_IL.ISO8859-8 iw_IL


Italian Database characterset1



LANG and LC_ALL2 it_IT.ISO8859-1 it_IT.iso88591 it_IT.ISO8859-1 it_IT

TC_language_default3 it_IT it_IT it_IT it_IT


JA16EUC JA16EUC JA16EUC JA16EUCJapanese(EUC)

Server character set EUC EUC EUC EUC

LANG and LC_ALL2 ja_JP.IBM-eucJP ja_JP.eucJP ja_JP.eucJP ja_JP.eucjp



JA16SJIS JA16SJIS JA16SJIS JA16SJISJapanese(Shift-JIS)

Server character set Shift-JIS Shift-JIS Shift-JIS Shift-JIS

LANG and LC_ALL2 Ja_JP.PCK ja_JP.SJIS ja_JP.PCK ja_JP.sjis


Korean Database characterset1

KO16KSC5601 KO16KSC5601 KO16KSC5601 KO16KSC5601

Server character set KSC5601 KSC5601 KSC5601 KSC5601

LANG and LC_ALL2 ko_KR.IBM-eucKR ko_KR.eucKR ko_KR.EUC ko_KR

TC_language_default3 ko_KR ko_KR ko_KR ko_KR

Polish Database characterset1

EE8ISO8859P2 EE8ISO8859P2 EE8ISO8859P2 EE8ISO8859P2


LANG and LC_ALL2 pl_PL.ISO8859-2 pl_PL.iso88592 pl_PL.ISO8859-2 pl_PL

TC_language_default3 pl_PL pl_PL pl_PL pl_PL

Russian Database characterset1

CL8ISO8859P5 CL8ISO8859P5 CL8ISO8859P5 CL8ISO8859P5


LANG and LC_ALL2 ru_RU.ISO8859-5 ru_RU.iso88595 ru_RU.ISO8859-5 ru_RU

TC_language_default3 ru_RU ru_RU ru_RU ru_RU

Spanish Database characterset1



Notes:





Value


LANG and LC_ALL2 es_ES.ISO8859-1 es_ES.iso88591 es_ES.ISO8859-1 es_ES

TC_language_default3 es_ES es_ES es_ES es_ES

Notes:


Note

• To verify the character set in your server environment, enter thelocale charmap command.

• In Hebrew locales, set the following additional variables:

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

2. In the TC_ROOT/iiopservers/Start_TcServer1 fileand the TC_ROOT/pool_manager/mgrstartMYDB, setTC_CHARACTER_ENCODING_SET to ISO8859_8.

Deploying localizationsBuild and deploy localizations to the Teamcenter thin client and rich client usingthe Web Application Manager.

Note

For more information about applying localizations to Teamcenter, see theLocalization Guide.

Deploying thin client localizations

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

Update thin client localized text

The thin client text server files reside under the Teamcenter application rootdirectory in the /lang/textserver/locale-code directory. If you change one of the text



server XML files (*_locale.xml and *_errors.xml), regenerate the webstrings.xmlfile:

1. Change to theWEB_ROOT/staging-location/webapp_root/teamcenter/dhtml/common/intldirectory in the Teamcenter application root directory.

2. Copy the webstrings.xml file to the language directory.

3. Regenerate the Web tier application (file-name.ear) and deploy in an applicationserver.

4. Change the header encoding of the webstrings.xml file to the appropriatelanguage-specific character encoding value, for example, Shift-JIS for Japanese.

Note

After you complete these steps, clear your Web browser cache before youlaunch the thin client.

Create a thin client localization

If you localize the thin client into a language not provided by Siemens PLM Software:

1. In the Teamcenter application root directory, create a directory for the newlanguage under the /lang/textserver/ directory.

For example, if you localize the user interface for Hebrew, create the iw_ILdirectory.

2. Copy all files from the en_US directory to the new language directory.

3. In the new language directory, translate all XML files to the new language.

Note

Make sure the encoding specification at the top of each XML file matchesyour system encoding when you save the file. Also, make sure the encodingspecified supports the desired locale.

For Hebrew on Windows systems, the encoding specification shouldresemble the following example:

<?xml version="1.0" encoding="windows-1255" standalone="yes"?>

4. Edit the weblocal_locale.xml file in the new language directory to change thevalue of the 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";

5. In the /lang/textserver/no_translation directory, locate thetextserver_text.xml file and open it in a plain text editor.

6. Locate the following key for the new language:<key id="textsrv_associatedDefaultJavaLocale_locale-code</key>



Replace lang-code with the W3C standard language code and locale-code withthe Java standard locale code.

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

Replace the existing key with the following:

<key id="textsrv_encodingLocales_ISO8859_8">en_US;iw_IL</key><key id="textsrv_encodingLocales_NT_862">en_US;iw_IL</key><key id="textsrv_encodingLocales_NT_1255">en_US;iw_IL</key><key id="textsrv_encodingLocales_UTF8">cs_CZ;de_DE;en_US;es_ES;fr_FR;

it_IT;iw_IL;ja_JP;ko_KR;ru_RU;zh_CN;zh_TW</key>

Note

On UNIX and Linux systems, after you complete this step, remove sharedmemory backing store files.

7. Change to the WEB_ROOT/staging-location/webapp_root/intl/ directory andcreate a new language directory.

For example, if you localize the user interface for Hebrew, create the he directory.

8. Copy all files from the en directory to the new language directory.

9. In the new language directory, translate all XML files to the new language.

10. Regenerate the webstrings.xml file:

a. Change to the /web/htdocs/tc/intl/ directory in the Teamcenter applicationroot directory.

b. Copy the web_gen_xml.dat file to theWEB_ROOT/staging-location/webapp_root/intl directory.

c. WEB_ROOT\staging-location

Change to the WEB_ROOT/staging-location/webapp_root/intl directory.

d. Run theweb_gen_xml utility that uses theweb_gen_xml.dat file as input.

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

e. Copy the webstrings.xml file to the language directory.

11. Regenerate the Web tier application (file-name.ear) as described in Installingthin client Web applications.

Deploy the application in an application server as described in the WebApplication Deployment Guide.

4. he is the standard W3C code for Hebrew.



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 localizations

Deploy a localized Teamcenter rich client.

Display Siemens PLM Software-provided rich client localizations

To display a Siemens PLM Software-provided localized rich client user interface, 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)• Czech• French• German• Hebrew• Italian• Japanese• Korean• Polish• Russian• Spanish

Update rich client localized text

If you change the strings of a localized rich client user interface, you must convertthe files to Unicode and regenerate the 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 Java SDK 1.4.

For more information, access the following URL:

http://java.sun.com/j2se/1.4/docs/tooldocs/win32/native2ascii.html

For example, to convert the properties file from Japanese to Unicode, enter 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 more information about converting files to unicode, see the Unicode ConsortiumWeb site:

http://www.unicode.org/


Chapter

18 Silent installation

Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1

Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . 18-2


Chapter

18 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 18 Silent installation

Modify the silent installation configuration fileThe silent installation configuration file is XML-based, as shown in Sample silentinstallation configuration file. After creating the file and establishing the filestructure using Teamcenter Environment Manager, you can change the installationby manually modifying the values of the XML elements described in the followingtable.

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.

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>

Sample silent installation configuration file (Continued)

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

Sample silent installation configuration file

Chapter

19 Installing Teamcenter patches

Distribution of Teamcenter updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Downloading Teamcenter patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1

Patching Teamcenter Environment Manager . . . . . . . . . . . . . . . . . . . . . . . . . 19-2

Install patches on the corporate server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2

Patching the rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3Patch the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4Patch the rich client silently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4Patch the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . 19-4Patch Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5

Patch the Web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6

Review the README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8


Chapter

19 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.3 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_all.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 19 Installing Teamcenter patches

Before you apply downloaded Teamcenter 8.3 patches to your server, you must dothe following:

• Install the base Teamcenter 8.3 release.

• Stop all Teamcenter 8.3 related processes and services (such as FSC, databasedaemons, and so on).

• If your server configuration includes a two-tier rich client with EngineeringProcess Management Visualization, uninstall this feature using TEM.

Note

TEM does not allow you to install patches for a version of Teamcenter thatis earlier than your current installation. For example, you cannot apply aTeamcenter 2007.1 patch to a Teamcenter 8.3 installation.

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 patch-id_install.zip file to your TC_ROOT/install directory.

b. Open a command prompt.

c. Change to the TC_ROOT/install directory.

d. Enter the following command to extract the install.zip file, 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/install directory to yourPATH environment variable and enter the unzip command again.

• Enter the unzip 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. Stop all Teamcenter services before you begin the update process.

2. Launch TEM (TC_ROOT/install/tem.sh).


Installing Teamcenter patches

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

4. In the Apply Updates panel, enter the location of the patch file you downloadedin the Update kit location box. Also, enter the location where you want to storebackups of files replaced during the update process.

Click Next.

Note

All users logged on to the environment are notified that it will not beavailable until the update process is complete. Make sure all Teamcenterclients and processes on the host are stopped before you continue. IfTeamcenter services or processes are running, the update may fail becauseTEM cannot copy replacement files from the patch to the installed location.

5. In the Confirm Selections panel, click Next to begin patching the server.

6. 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 platform/tc/data directory from the patch-id.zip file and copythe contents to your TC_DATA directories.

c. Copy the tc_profilevars file from the backup to the TC_DATA. directory.

7. 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 FSC, database daemons,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.

Patching the rich clientThere are multiple methods 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-WebInstaller. To patch Lifecycle Visualization using the Over-the-Web Installer, followthe steps in Patch Lifecycle Visualization.



Patch the rich client using TEM

Patch the rich client using the steps in Install patches on the corporate server. If 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. Patch Teamcenter Environment Manager as described in Patching TeamcenterEnvironment Manager.

2. Open a command prompt.

3. Change to the TC_ROOT/install directory.

4. 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_patch-ID_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_patch-ID_OTW.zip file to your computer.

2. Shut down the distribution server.


4. Click the Copy ICD button. Browse to the expanded patch location to select 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.




7. Click Add and add the patch location to list of disk locations for install images.

8. Select and install patches. If you add patches to a previously patched instance,the steps differ from the first patch installation.

Initial patch Additional patches

a. Click Add Solutions.

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.


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 the Lifecycle Visualization patch file (patch-id_PV_all.zip).

2. Extract the ZIP file into a single directory. If prompted, overwrite all files.

3. Shut down the distribution server.


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

1. Adding patches reinstalls the patch solution with the newer files.



6. Select the rich client instance that contains the Teamcenter Visualization 8(Embedded) for Rich Client 4–Tier (Installation and Configuration) solutionand click Modify.



8. Click Add and add the patch location to list of disk locations for install images.

9. Select and install patches. If you add patches to a previously patched instance,the steps differ from the first patch installation.

Initial patch Additional patches

a. Click Add Solutions.

b. Select Teamcenter Visualization8 (Embedded Viewer) for RichClient 4–Tier (installation andConfiguration) 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.2

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.

10. In the Modify Web Application dialog box, click OK.


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

2. Adding patches reinstalls the patch solution with the newer files.



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_number_platform.zip file. If you have not patched the server, accessthe files by unzipping the patch file contents to a temporary location, referred toas 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, click OK.

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 patch-id_pub.zip file includes a release_info directory that contains the patchset README file. Review this README file for information about the patch andpossible additional steps required to complete the patch installation.


Chapter

20 Installing Teamcentermaintenance packs


Chapter

20 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

21 Uninstalling Teamcenter

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

Uninstalling DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Remove DB2 instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2Remove DB2 software on UNIX and Linux systems . . . . . . . . . . . . . . . . . 21-3Remove DB2 software on Windows systems . . . . . . . . . . . . . . . . . . . . . . . 21-4

Uninstall Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5


Chapter

21 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 21 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 Oracle recycle bin. To permanently remove thedatabase, launch SQL*Plus and enter the following command:

PURGE RECYCLEBIN;

Uninstalling DB2If you no longer use your existing your DB2 instances and databases, you canremove them.

If you want to uninstall your default DB2 copy but want to keep other DB2 copieson your system, use the db2swtch command to choose a new default copy beforeyou proceed with the uninstallation. Also, if your database administration server(DAS) is running under the copy you want to remove, move your DAS to a copy thatis not being removed. Otherwise, you must re-create the DAS using the db2admincreate command after the uninstall, and you may need to reconfigure the DASfor some functionality to work.

Remove DB2 instances

1. Log on as a user with root privileges.

2. Type the following command:

• Windows systems:

DB2-HOME\sqllib\bin\db2idrop instance-name

• UNIX and Linux systems:

DB2-HOME/instance/db2idrop instance-name

Replace DB2-HOME with the DB2 installation directory you specified duringthe DB2 installation. Replace instance-name with the login name of the DB2instance.

Note

On UNIX systems, the default installation path is /opt/IBM/db2/Vversion.On Linux systems, the default installation path is /opt/ibm/db2/Vversion.

The db2idrop command removes the instance entry from the list of instances andremoves the instance-home/sqllib directory. If you store any files in sqllib directory,these files are removed by this action. If you still need these files, make a copy ofthem before you remove the instance.


Uninstalling Teamcenter

Optionally, as a user with root privileges, remove the instance owner’s user ID andgroup (if used only for that instance). Do not remove these if you plan to re-createthe instance. Remove the database files from the system or drop the databasesbefore dropping the instance if you no longer need the databases. After you drop theinstance, the database files remain intact. This step is optional because the instanceowner and the instance owner group may be used for other purposes.

Remove DB2 software on UNIX and Linux systems

1. Optionally, drop all databases. You can drop databases using the Control Center(on Linux platforms only) or the database drop command.

Note

If you drop databases without dropping instances first, database filesremain on your file systems.

2. Stop the DB2 Administration Server.

a. Log on as the DB2 administration server owner.

b. Stop the DB2 administration server by entering the db2admin stopcommand.

3. Remove the DB2 administration server (DAS) by entering the followingcommand:

DB2-HOME/instance/dasdrop

Replace DB2-HOME with the DB2 installation directory you specified duringthe DB2 installation.

Note

On UNIX systems, the default installation path is /opt/IBM/db2/Vversion.On Linux systems, the default installation path is /opt/ibm/db2/Vversion.

4. Stop DB2 instances.

a. To obtain a list of the names of all DB2 instances associated with yourcurrent DB2 copy, enter the following command:

DB2-HOME/bin/db2ilist

b. Log off.

c. Log on again as the owner of the instance you want to stop.

d. If the DB2 instance startup script is not included in the .profile file, enterone of the following commands to run the startup script.

• Bash, Bourne, or Korn shells: . instance-home/sqllib/db2profile

• C shells: source instance-home/sqllib/db2cshrc

Replace instance-home with the home directory of the DB2 instance.

If you want to keep a copy of the database configuration settings, savethe database manager configuration file, db2systm, the db2nodes.cfg


Chapter 21 Uninstalling Teamcenter

file, or user-defined function or fenced stored procedure applications ininstance-home/sqllib/function.

e. Stop the DB2 database manager by entering the db2stop force command.

f. Verify that the instance is stopped by entering the db2 terminate command.

5. Remove DB2 instances as described in Remove DB2 instances.

6. Remove DB2 products.

a. Log on as a user with root privileges.

b. Access the path where the DB2 products are located.

For information about how to locate the path of the DB2 product to removeusing the db2ls command, see Listing DB2 products installed on your systemin the IBM DB2 Information Center Web site.

c. Run the db2_deinstall –a command from the DB2-HOME/install directoryor the doce_deinstall –a command from the DB2-HOME/doc/installdirectory.

Remove DB2 software on Windows systems

1. Optionally, drop all databases. You can drop databases using the DB2 ControlCenter or the database drop command from a command prompt.

Note

If you drop databases without removing instances first, database filesremain on your file systems.

Warning

Dropping databases after removing database instances permanentlydeletes data.

2. Stop all DB2 processes and services. This can be done through the WindowsControl panel or by issuing the db2stop command from a command prompt.

If you do not stop DB2 services and processes before attempting to remove DB2software, DB2 displays a warning that lists processes and services holding DB2DLLs in memory.

3. Remove DB2 software by one of the following methods:

• Remove DB2 software using the Add/Remove Programs feature in theWindows Control Panel.

• Open a command prompt and type the db2unins command.To remove multiple DB2 products, use the /p argument:

ddb2unins /p

To remove DB2 software silently, use the /u argument:ddb2unins /u


http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.uprun.doc/doc/t0023264.htm

Uninstalling Teamcenter

For more information, see the IBM DB2 documentation for the db2uninscommand.

In some cases, neither of these methods successfully removes DB2 software. Ifthis happens, you can force removal of DB2 software by typing the followingcommand:

ddb2unins /f

Caution

This command removes all DB2 software and databases from your system.Use this command only if other methods fail.

Uninstall OracleFor information about uninstalling Oracle, see the Oracle installation guide on theappropriate Oracle 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 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.

PLM00011 F Installation on UNIX and Linux Servers Guide A-1

Appendix A Glossary

connector to Teamcenter EnterpriseEnterprise JavaBean that connects Global Services with Teamcenter Enterprise.The optional connector to Teamcenter Enterprise is provided as a part of the GlobalServices connectors.

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 F

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, Production Serverprovides a connector for communicating with JDBC-compliant databases. GlobalServices offers optional connectors to Teamcenter, Teamcenter Enterprise, OracleManufacturing, and SAP. One implementation of a connector can communicate withmultiple data sources through the use of connector configuration 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

Lifecycle VisualizationSiemens PLM Software suite that provides enterprise-wide product visualizationcapabilities. Lifecycle Visualization can be configured for use with both theTeamcenter 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.

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.


Appendix A Glossary

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.

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.


Glossary

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 Teamcenterfunctionality 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 remote workflow.

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

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.


Appendix A Glossary

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.

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 other classes and definition of attributes, manipulation ofin-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.


Glossary

remote workflowTeamcenter component that enables users to create links between Teamcenterobjects and objects in other Teamcenter products, such as Teamcenter’s portfolio,program and project management. Users can then launch the linked Teamcenterproduct from within either the rich client or the thin client.

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.

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.


Appendix A Glossary

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.

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

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 manufacturing process managementTeamcenter manufacturing process design and management system. Teamcenter’smanufacturing process management comprises several user applications, forexample, Plant Designer, Manufacturing Process Planner, Part Planner, ReportGenerator, 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.


Glossary

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.

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 Environment Manager (TEM)Tool with a wizard-style interface that installs Teamcenter servers and two-tier andfour-tier rich clients. TEM also performs maintenance operations, such as upgradingservers, applying maintenance packs, and installing patches. Teamcenter installerslaunch TEM using the tem.bat command (on Windows systems) or the tem.shcommand (on UNIX or Linux systems).

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.

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.

TEMSee Teamcenter Environment Manager (TEM).


Appendix A Glossary

tessellationProcess that translates a CAD file to a visualization file.

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.


Glossary

worldAll users regardless of group or role.

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. Comparewith limited 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-2Resolving 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-3

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-9View additional information about an Oracle error message . . . . . . . . . . B-10

Troubleshooting document rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10

Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . B-12

Recovering from a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13Recovering from a corrupted IBM DB2 database . . . . . . . . . . . . . . . . . . B-13Recovering from a corrupted Oracle database . . . . . . . . . . . . . . . . . . . . B-13


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

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.

Update Manager FTP errors

The following table describes errors that can occur while connecting to the updateserver or while downloading updates.

B-2 Installation on UNIX and Linux Servers Guide PLM00011 F

Troubleshooting

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.3. This occurs when legacy action rules are notremoved from the database during the upgrade.

After upgrading to Teamcenter 8.3, 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.

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


Troubleshooting

Engineering Process Management 9.1.3– GM Overlay action rules

Teamcenter 2007 – GM Overlay methodextensions

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

Web-tier application fails duringinitialization with an errorcontaining the following:

Error during login.com.teamcenter.presentation.webclient.actions com.teamcenter.jeti.util.JetiResourceConfigurationException: TreeCacheinitialization failed

When a host has multiple IP addresses, the JGroups softwareand JDK software arbitrarily choose one of them to use asthe address to bind to for a server connection port. In somesituations, as when using a Windows Network Load Balancer,not all local IP addresses are accessible to other hosts on thenetwork. If the chosen IP address is not accessible, othercluster peers are not able to open sockets to that port.

To avoid this error, specify a particular bind address usingthe bind.address Java system property, for example:

Dbind.address=123.456.78.91

Java arguments can be specified in different wayson different application servers. For example, for aWebLogic managed server, use the WebLogic consoleserver/Configuration/Server Start/Arguments field.



Problem Solution

For more information, consult the application server’sdocumentation.

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 Webtier required parameters.

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.

Delays in opening a connectionfrom the Web tier to a Teamcenterserver

The Web tier may be attempting a connection to theTeamcenter server on an IP address that is unavailable.

If the SERVER_HOST parameter is not specified in theserver manager configuration, the Teamcenter server writesall IP addresses found in the host’s network configurationto its CORBA interoperable object reference (IOR). If thehost has multiple addresses and the primary address isnot reachable, the Teamcenter Web tier logs the followingwarning:

The connection to the pool with ID pool—ID is notavailable. Primary Address Host is IP-address andthe Primary Address Port is port; In addition tothe Primary Address, additional address(es) werefound. Please ensure that the Primary Address usedis the right one. This address can be changed byconfiguring the SERVER_HOST parameter.

Inspect the Web tier log file for status messages reportedduring server manager startup. If the server manager logcontains a message similar to this, set the SERVER_HOSTparameter in the serverPool.properties file to the correctIP address for the host.

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.


Troubleshooting

Problem Solution

Occasionally, TreeCache instances fail to accept connectionsand report handleJoin errors. Typically this errordisappears if you restart one or more cluster members.

handleJoin errors occur atstartup

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

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.



Problem Solution

Configuration is correct, butrun-time errors occur

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.


Troubleshooting

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.



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 document renderingIf you are not successful rendering document revisions to translate dataset files, youradministrator should review your installation and configuration systematically andverify the following requirements are met.

• Installation of Teamcenter’s lifecycle visualization Convert software is requiredby the previewservice feature.

– You must select the Convert feature; the Print feature is optional.

– The destination installation directory name must not contain spaces.

– To accommodate high levels of input and output, modify the vvcp.ini file onWindows systems, or the vvcp.platform.cfg file on UNIX systems.

FileCheckWait=600FileCheckWaitForZero=30

– When the installation is complete, verify the Convert option prepare.exeprogram exists under the VVCP installation directory.

For more information about verifying this part of the setup, see theDispatcher Server Translators Reference Guide.

• Installation of Ghostscript 8.53 software required by the previewservicefeature.

– A free Ghostscript installer is available at the following link:

http://ftp.ugs.com/open-source/ghostscript/gs853

– On UNIX platforms, after you install Ghostscript, set the PSPath settingin the Convert and Print configuration file (vvcp.ini) to the location of theGhostscript application.

For example: *PSPath: /apps/gs853/bin/gs.

– Set AllowOpenApplication=on to support the use of applications, such asMSWord, that may already be open when the Convert process begins.


Troubleshooting

• Installation of the Adobe LiveCycle ES 8.2.1 software required by thepdfgenerator utility.

Ensure native application support for LiveCycle PDF Generator ES is enabled.

When configuring the Result Watched folder directory:

– Do not append %Y/%M/%D in the result folder directory.

For example:

Result Folder: result

Include File Pattern: *

– Path

Specify the location of the watched folder directory.

Adobe LiveCycle creates this directory if it does not already exist; use ashort path.

Note

The input directory is created under the specified Path directorylocation. This is the watched folder input directory.

For example, if the path is:

D:\LCWatchedFolder

The watched folder input directory path is:

D:\LCWatchedFolder\input

– Wait Time

Duration in milliseconds to wait for before picking up the file/folder. Increasethis number for large file.

– Operation Name

Select CreatePDF.

– Input Parameter Mappings

For inputDocument, select Variable and enter *.*

– Output Parameter Mappings

For Result, enter %F.pdf

After LiveCycle PDF Generator ES is installed, you must create and configurethe Adobe LiveCycle Watched Folder Endpoint as described in Adobe LiveCycleEndpoint Management documentation. The specified watched folder input andresult directory locations are needed during the installation of PdfGeneratortranslator.

For more information, see the Dispatcher Server Translators Reference Guide.

After the watched folder endpoints are set, you may also need to modify thedefault applications extension file type settings to specify additional filenameextensions for file types for generating PDF output.



For more information about these configuration tasks, see the Adobe LiveCyleES documentation.

• You must enable the RenderMgtTranslator service and one or both of thefollowing services:

– PreviewService

– PdfGenerator

Configure translation services by enabling and configuring translators usingTEM.

For more information about setting up and configuring translators, see theDispatcher Server Translators Reference Guide.

– PreviewService

Required Teamcenter Visualization Convert 8. Ghostscript v 8.53, andsource authoring applications such as Microsoft Office application (2003,2007) are also required.

– PdfGenerator

Requires Adobe LiveCycle PDF Generator ES. The configuration file mustspecify the Adobe watched folder input and watched folder result directorylocation. Source authoring applications such as Microsoft Office application(2003, 2007) and Adobe Acrobat 8.x are also required.

– RenderMgtTranslator

Required for either PreviewService, PdfGenerator, or any other serviceto be added.

• Use Business Modeler IDE to set up and deploy IRDC and dispatcher serviceconfiguration objects to the Teamcenter database.

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




Troubleshooting

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 databaseIf you attempt to install Teamcenter using a database that is only partially installed,Teamcenter Environment Manager (TEM) allows you to drop all existing data beforebeginning a new installation.

If the Teamcenter database is corrupted beyond repair, you can alternatively deletethe database and repeat the installation using an empty database. To do this,perform the appropriate procedure, depending on your database vendor:

• Recovering from a corrupted IBM DB2 database

• Recovering from a corrupted Oracle database

Recovering from a corrupted IBM DB2 database

1. Use either of the following tools to delete a corrupted database in an IBMDB2-based installation:

• IBM Control Center

In the Control Center application, select the database you want to deletefrom the list of databases, right-click the database and then select Drop.This also deletes the appropriate data files.

• Command Line Editor tool

Start the command line utility and then type the following command:

DROP DATABASE TC

2. Create a new DB2 database for Teamcenter.

For more information, see Create a DB2 database for Teamcenter

3. Launch TEM and reinstall Teamcenter.

Recovering from a corrupted Oracle database

1. Delete the database using Oracle Database Configuration Assistant (DBCA).



2. Create a new empty database using the appropriate DBCA template file.

3. Launch TEM and reinstall Teamcenter.


Appendix

C Distribution media

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

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


Appendix

C Distribution media

Siemens PLM Software distributes the following software and documentationimages for Teamcenter 8.3:

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.

Note

Teamcenter software distribution images can containmultiple ZIP files. For example, the softwaredistribution image for Windows consists of two filesnamed Tcn_win_1_of_2.zip and Tcn_win_2_of_2.zip.If you download software distribution images forTeamcenter, you must download all files in the setto obtain the complete image. After you downloadfiles, extract all ZIP files to a common directory toassemble the image before you begin installation.

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.

PLM00011 F Installation on UNIX and Linux Servers Guide C-1

Appendix C Distribution media

Teamcenter software distribution imageThe following table describes the directories in the Teamcenter software distributionimage:

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

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:

C-2 Installation on UNIX and Linux Servers Guide PLM00011 F

Distribution media

• PDF

Contains the Teamcenter online help library in PDF format. To display theonline help library index page, open the index.htm file.

• javadoc

Contains documentation for Teamcenter user interface components you canuse in your rich client customizations. This documentation is also provided inthe JavaDoc.zip file in the root directory of the Teamcenter documentationdistribution image.

For more information about this documentation, see the Rich ClientCustomization Programmer’s Guide.

• additional_documentation

Contains additional documentation for use with Teamcenter. This includesguides for using the Siemens PLM Software common licensing server.

Note

If you want to view the Teamcenter online help library in HTML format,expand the tchelp.jar from the Teamcenter documentation distributionimage to a local directory. To display the online help library index page, openthe index.htm file in the help directory.

If you use popup blocker software, configure it to allow popups within theTeamcenter online help library.

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

Solution Features

Corporate Server Teamcenter FoundationFMS Server CacheNX UG Integration

Dispatcher (Dispatcher Server) Dispatcher ServerVolume Server FMS Server CacheRich Client 2-tier Teamcenter Rich Client 2-tierRich Client 4-tier Teamcenter Rich Client 4-tierMultisite Collaboration Proxy Server Multisite Collaboration IDSM Service

Multisite Collaboration ODS ServiceEDA Standalone Client EDA Standalone Client

Mentor PADS SupportMentor Board Station Library SupportCadence Allegro SupportMentor Expedition Library SupportMentor Board Station Library SupportMentor PADS Library SupportCadence Allegro Library Support

Business Modeler IDE Business Modeler IDE 2-tierGlobal Services Teamcenter Foundation

J2EE Based Server ManagerFMS Server CacheGlobal Services FrameworkGlobal Services Preferences

PLM00011 F Installation on UNIX and Linux Servers Guide D-1

Appendix D Solutions and features reference

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.

Teamcenter featuresFeature/Subfeature Description

Base Install Base Teamcenter server and client components.

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,online help, or sample files. When you install these components, TeamcenterEnvironment Manager creates an TC_ROOT directory, but populates it with onlythe subdirectories necessary for these components to run.

Teamcenter Rich Client (Shared DiskDeployment)

Installs the rich client in a shared location. This client can be run from multiplehosts.

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.

Business Modeler IDE 2-tier Installs the two-tier Business Modeler IDE client. This client connects to theTeamcenter server using IIOP.

Business Modeler IDE 4-tier Installs the four-tier Business Modeler IDE client. This client connects to aTeamcenter server in a four-tier environment using HTTP.

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.

Server Enhancements Additional features for Teamcenter servers.

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

D-2 Installation on UNIX and Linux Servers Guide PLM00011 F

Solutions and features reference


.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 feature requiresTeamcenter Foundation and FMS Server Cache features.

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, aswell as full text retrieval searches on both metadata and common forms of text data.

IDOL works with the IDOL server, DiSH server and File System Fetch as threeservices installed. The IDOL installer does not support the silent install option.

Online Help Installs the Teamcenter Help Library files on the local host:

When TEM prompts you for the location of the Teamcenter help files, enter 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 Installing Teamcenter online help.

Sample files Installs sample source code for customizing Teamcenter and generating reports.

This component is optional. You can install the sample files individually; you neednot install any other components.

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.

Required information:

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

Database Daemons Optional database support services.

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.




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.

File Management File management features.

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.

Hierarchical Storage Management(HSM)

Adds support for third-party hierarchical storage management software.

Teamcenter Web Tier Features to support the Teamcenter .NET Web tier.

ASP .NET State Service Installs the middle tier processes that communicate with Teamcenter serverprocesses.

Web Tier for .NET Installs the middle tier processes that communicate with Teamcenter serverprocesses.

Client Enhancements Teamcenter server configurations for rich client enhancements.

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.

Extensions Extensions to Teamcenter server and client functionality.

Aerospace and Defense Aerospace and Defense features.

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 Aerospace and Defense SolutionGuide guide.

Aerospace and Defense ChangeManagement

Installs the change management functionality for the Aerospace and DefenseFoundation feature. This feature requires Teamcenter Foundation and Aerospaceand Defense Foundation.


Aerospace and Defense FoundationTraining

Installs the Aerospace and Defense Foundation training program for the Aerospaceand Defense Foundation feature. This feature requires Teamcenter Foundation,Vendor Management, and Aerospace and Defense Foundation.


Automotive Teamcenter Automotive Edition and additional supporting features.

Teamcenter Automotive Edition Installs the optional Teamcenter Automotive Edition application.




GM Overlay Installs the Teamcenter Automotive Edition GM Overlay application.

Installing GM Overlay requires that you also install Teamcenter AutomotiveEdition.

Configure AutoCAD Integration forGM Overlay

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.

GM Customization for DPV Installs GM-specific LOVs and GRM rules for DPV.

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.

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.

BOM Management Features that support Product Master Management.

CAD BOM Alignment Configures the Teamcenter installation to interact and share visual data withProduct Master Management. Configuring this feature allows designs managed bythis installation of Teamcenter to be related to parts and use or parts in productsthat are managed by Product Master Management.

Note

This feature requires postinstall setup to complete configuration.

Consumer Packaged Goods Features to support Consumer Packaged Goods.

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

For information about installing this feature, see Getting Started with ConsumerPackaged Goods.

CPG Materials Installs Consumer Packaged Goods objects such as raw materials, formulatedmaterials, and so on.


Finished Product Management Installs the Finished Product Management functionality for Consumer PackagedGoods.


Packaging and Artwork Installs packaging and artwork functionality for Consumer Packaged Goods.


Specification Manager Installs the Specification Manager feature. For more information about installingthis feature, see the Specification Manager Guide.

Finished Product Management toCPG Materials Bridge

Provides a bridge between finished products and Consumer Packaged Goodsmaterials.





Packaging and Artwork to FinishedProduct Management Bridge

Provides a bridge between Packaging and Artwork and Finished ProductManagement for Consumer Packaged Goods.


Content and Document Management Content and document management features.

Acrobat/Reader Plugin Installs the Teamcenter plug-in for Adobe Acrobat and Adobe Acrobat Reader.This solution is optional.

For information about using the Adobe Acrobat/Reader plug-in, see Getting Startedwith Document Management.

MS Office for Rich Client Installs the application that integrates Teamcenter with Teamcenter’s Integrationfor Microsoft Office. Separate installation of Microsoft Office is required. Thissolution is optional.

Content Management Base Installs the data model for Content Management.

For information about configuring this feature, see Content ManagementAdministration Guide.

Content Management DITA Enables management of documentation for the DITA standard in ContentManagement.

For information about configuring this feature, see Content ManagementAdministration Guide. For information about using Content Management, see theContent Management 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.

Engineering Process Management Engineering Process Management features.

NX Integration Installs default data types and loads template NX data to support TeamcenterIntegration for NX/NX Integration, the Teamcenter integration with Siemens PLMSoftware NX.

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.

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, youmust 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, youmust install the Spatial Search translator (JtToBboxAndTso).

Bounding box generation from NX Enables generation of bounding box data when saving NX files, providing secondarydata for the cacheless search engine.

QPL for Repeatable DigitalValidation

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.

Enterprise Knowledge Foundation Enterprise Knowledge Foundation features.

Remote Workflow Configures linking between Teamcenter sites for remote workflow operations.

This option is applicable only when you are deploying the four-tier architecture.

Prerequisites:

• Remote Workflow components, including Application Registry, must beseparately installed and configured.

• The Web tier application, including the optional Application Interface WebService (AIWS) and Remote Workflow parameters, must be installed andconfigured as described in Installing rich client Web applications.


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

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.

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.

For information about installing this feature, see Getting Started with Dispatcher(Translation Management).




Change Management Provides a flexible change management framework that integrates with otherTeamcenter products.

For more information about using Change Management, see the Change ManagerGuide.

Note

If you install this feature, you may need to set the HiddenPerspectivespreference in the rich client.

For more information, see the Preferences and Environment VariablesReference.

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.

Dispatcher Server Installs the following Dispatcher Server components: scheduler, module andadministration client.


Issue Management Installs Issue Manager, which allows you to track problems, or issues, with productsby managing the review, approval, and implementation of issues.

For more information, see the Issue Manager Guide.

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.


Lifecycle Visualization Features to support Lifecycle Visualization.

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.

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.

Localization Features that support localization of Teamcenter.

Classification L10N Installs the classification localization template, which enables localization in theClassification environment.

For more information, see the Localization Guide.

Note

The classification localization template is not supported with IBM DB2databases.




Maintenance Repair and Overhaul Teamcenter’s maintenance, repair, and overhaul features.

As-Built Management 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.

As-Maintained Management Installs the As-Maintained feature to support the As-Maintained physical structuremanagement


Service Planning Installs the Service Planner application that supports service planning capabilitieswithin Teamcenter. Service Planner requires a separate license and is installed asan optional overlay to standard Teamcenter.

For information about using Service Planner, see the Service Planner Guide.

As-Built and As-MaintainedAlignment

Enables interoperability of data created by the As-Built Management andAs-Maintained Management features.


Service Event Management Installs Service Event Management to support service process management forTeamcenter’s maintenance, repair, and overhaul.

For more information about using Service Manager, see the Service Manager Guide.

Service Planning and ServiceProcessing Alignment

Enables interoperability of data created by the As-Built Management andAs-Maintained Management features.


Service Request Processing Installs the Service Planning and Service Processing Alignment module to supportusing discrepancies in Service Planner.

For more information about using Service Planner, see the Service Manager Guide.

Manufacturing Process Management Teamcenter’s manufacturing process management features.

Configure Resource Browser andNC Package Browser

Installs libraries for the Resource Browser and NC Package Browser applications.

MTM Data Card Installs the Methods Time Measurement (MTM) data card system.

For more information, see Getting Started with Manufacturing.

Customization for Process SimulateIntegration

Installs additional data types for Process Simulate Integration Customization.

Customization for eM-ServerIntegration

Installs additional data types for Tecnomatix server integration customization.

Database Configuration for DPV Installs the database configuration for DPV. This feature requires TeamcenterFoundation, GM Overlay, and Customization for eM-Server Integration.

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.

Install Libraries for AIWS Client Installs sample source code and executables that assist in developing an ApplicationInterface Web Service (AIWS) client.

For more information, see the Application Interface Web Service (AIWS)Configuration and Customization Guide.

Mechatronics Process Management Features to support Mechatronics Process Management.

EDA Standalone Client Installs the client for Teamcenter EDA, the application that integrates ECADapplications with Teamcenter.

ECAD Part Library for Rich Client Enables ECAD part library menus in the rich client.

EDA for Business Modeler IDE Integrates Teamcenter EDA with the Business Modeler IDE.

Calibration and Configuration DataManagement

Installs the Calibration and Configuration Data Management (CCDM) feature,which allows you to manage the calibration and configuration-related parameterdata of embedded systems. CCDM allows you to define, create, view, update, anddelete parameter data, and to group related parameter definitions together andassociate parameter values to a project.

For more information about the CCDM solution, see the Embedded SoftwareSolutions Guide.

EDA Server and Rich Client Support Installs the dataset types and transfer modes required to support Teamcenter EDA,the application that integrates ECAD applications with Teamcenter.

For complete information about installing Teamcenter EDA, see the Getting Startedwith Electronic (EDA) Lifecycle Management.

EMPS - Foundation Installs electronic design and manufacturing types to support ECAD translationand PCB design collaboration using Teamcenter embedded viewer.

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

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.

Wire Harness Configuration Installs Teamcenter schema support for wire harnesses.

ECAD Part Library Management Installs ECAD part types to support ECAD part library management. This featurerequires Teamcenter Foundation, Vendor Management, and EDA Server Support.

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

Embedded Software Design DataManagement

Installs Embedded Software Design Data Management. For more informationabout this feature, see the Embedded Software Solutions Guide.

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.

ECAD Design Management ECAD design management features for Teamcenter EDA.




Mentor Board Station Support Installs support for using Mentor Graphics Board Station software with the EDAclient. Separate installation of Mentor Graphics Board Station is required. Thisfeature requires EDA Standalone Client.

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

Cadence Allegro 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 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 Expedition LibrarySupport

Installs support for using Mentor Expedition Library with the EDA client.Separate installation of Mentor Expedition is required. This feature requires EDAStandalone Client.

Cadence Allegro LibrarySupport

Installs support for using Cadence Allegro library with the EDA client. Separateinstallation of Cadence Allegro Design Entry is required. This feature requiresEDA 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.

Platform Extensability Platform extensability features.

Global Services Global Services features.

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.


• URL to the Global Services-Enterprise application.

Global Services Framework Creates Global Services Framework.

Global Services Preferences Installs Global Services Preferences.

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 ODSService

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

Global Services MonitoringGUI for Rich 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.




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.

Catia Non BOM Installs the CATIA Non BOM feature.

ERP Connect Installs the ERP Connect Toolkit interface that integrates Teamcenter with otherEnterprise Resource Planning (ERP)-supported applications, such as BAAN.

Oracle ManufacturingIntegration

Installs the Oracle Manufacturing integration to Teamcenter.

Portfolio, Program and ProjectManagement

Portfolio, Program and Project Management features.

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.

Note

This feature also requires the Schedule Manager translator(SchMgrTrans). For information about installing and configuring thistranslator, see the Dispatcher Server Translators Reference Guide.

Reporting and Analytics Features to support Teamcenter’s reporting and analytics.

Teamcenter for Reporting andAnalytics

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.

Supplier Relationship Management Supplier Relationship Management features.

SRM IntegrationInstalls the Supplier Relationship Management integration.

For more information about this feature, see the Data Exchange Guide.

Vendor Management Installs the optional Vendor Management solution.

Systems Engineering and RequirementsManagement

Features that support Systems Engineering and Requirements Management.

Teamcenter Extensions forMicrosoft Office

Installs Teamcenter’s Extensions for Microsoft Office.

For information about installing this feature, see the Installation on WindowsClients Guide.

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.

Microsoft Visual C++ 2005Redistributable

Installs the Microsoft Visual C++ libraries requiredfor the rich client and for the FMS Client Cache(FCC).

FMS Client Cache Installs the FMS client cache (FCC) on richclient hosts. An FCC uploads files from yourworkstation to a Teamcenter volume and downloadsrequested files from the volume to the rich clientworkstation. Installing the FCC provides thefollowing advantages:

• Improved file transfer performance• File streaming

Installing an FCC supports the LifecycleVisualization file streaming technology, whichdownloads portions of JT files over the network asthey are needed and improves network performance.

Installs the rich client software required for thefour-tier architecture. This solution is required.

ADS Foundation for RichClient 4-Tier

Installs Aerospace and Defense functionality for therich client.

For more information about Aerospace and Defense,see the Aerospace and Defense Solution Guide guide.

As-Built Manager 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 solution, see the As-Built Manager Guide.

As-MaintainedManagement for ServiceManager

Installs Service Event Management to supportservice process management for As-Maintainedfunctionality 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 solution, seeGetting Started with Consumer Packaged Goods.




Calibration andConfiguration DataManagement (CCDM)for Rich Client 4-Tier

Installs Calibration and Configuration DataManagement (CCDM), which allows rich client usersto manage the calibration and configuration-relatedparameter data of embedded systems. CCDM allowsyou to define, create, view, update, and deleteparameter data, and to group related parameterdefinitions together and associate parameter valuesto a project.

For more information about the CCDM solution, seethe Embedded Software Solutions Guide.

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.

Contract Management forRich Client 4-Tier

Installs Contract Data Management, which allowsyou to manage, initiate review processes, andmonitor correspondence for procurement documents,such as design information, drawings, status reports,purchase orders, and so on. This solution is optional.

For more information about Contract DataManagement, see the Aerospace and Defense SolutionGuide.

Dispatcher Client for RichClient

Installs Dispatcher Client for the rich client.

For information about using this feature, see GettingStarted with Dispatcher (Translation Management).

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.

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 Teamcenter’s Integration for MicrosoftOffice, which provide the capability to manageTeamcenter workspace objects in real time.Integration for Office provides access to Teamcenterobjects directly through Microsoft Office Word, Excel,and PowerPoint in Microsoft Office 2003. CustomTeamcenter menus and toolbars are added to theseMicrosoft Office products.

For information about using Integration for Office,see the Integration for Microsoft Office Guide.

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.

MTM Data Card for RichClient

Installs the Methods Time Measurement (MTM)data card system. This solution is optional.

For more information, see Getting Started withManufacturing.

Office Client for MicrosoftOffice

Installs Teamcenter’s Client for Microsoft Office,which provides the capability to manage Teamcenterworkspace objects in real time. Client for Officeprovides access to Teamcenter objects directlythrough Microsoft Office Word, Excel, PowerPoint,and Outlook in Microsoft Office 2007. This solutionadds a custom Teamcenter ribbon to Microsoft Officeapplications.

Note

Client for Office is not available for the two-tierTeamcenter rich client.

For information about features and use of Client forOffice, see the Client for Microsoft Office Guide.

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.

SRM Integration for RichClient 4-Tier

Installs the Supplier Relationship Managementintegration.

For more information about this solution, see theData Exchange Guide.




Service Planning Installs the Service Planner application thatsupports service planning capabilities withinTeamcenter. Service Planner requires a separatelicense and is installed as an optional overlay tostandard Teamcenter.

For information about using Service Planner, see theService Planner Guide.

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 Plugin forMicrosoft Project

Installs the Teamcenter Plugin for Microsoft Projectallows Microsoft Project users to exchange datadirectly with Schedule Manager.

For information about using the Teamcenter Pluginfor Microsoft Project, see the Schedule ManagerGuide.

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

Provides Render Management capabilities for therich client. This feature requires Dispatcher Clientfor Rich Client.

For more information about installing andconfiguring Render Management capabilities, seeInstalling Render Management.

For information about installing Dispatcher features,see Getting Started with Dispatcher (TranslationManagement).

Rich Client 4-Tier LiteEdition

Installs the lite edition of the four-tier rich client.This solution is optional.

Service ProcessingExtensions for ServiceManager

Installs the Service Processing Extensions for therich client. This functionality is available only if youhave purchased and have a license for Service EventManagement.

For more information about using Service Manager,see the Service Manager Guide.

As-Built and As-MaintainedAlignment for ServiceManager

Installs the operability functionality betweenthe As-Built Management and As-MaintainedManagement applications. This functionality isavailable only if you have purchased and have alicense for As-Built Management and As-MaintainedManagement.


Service Event ManagementExtensions for ServiceManager

Installs the Service Event Management functionalityfor the rich client. This functionality is available onlyif you have purchased and have a license for ServiceEvent Management.


Service Request Manager Installs service request processing for Teamcenter’smaintenance, repair, and overhaul.



Appendix

E Web tier context parameters


Appendix

E Web tier context parameters

The following tables describe Web tier context parameters provided by TeamcenterWeb tier solutions.

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

E-2 Installation on UNIX and Linux Servers Guide PLM00011 F

Web tier context parameters



In addition, the TreeCache may find more than onepeer based on a single host/port pair (for example, ifmultiple 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.

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

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



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.

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.

globalservices.webservices.url Specifies the URL of the Global Services Webservices WAR file within the Global Services OdeBPEL enterprise application, for example:

globalservices.webservices.url =http://localhost:8080/tcgs-ws

This is used by services that must send HTTP SOAPrequests to other web services.

globalservices.ode.url Specifies the URL to the Global Services Ode BPELenterprise application, for example:

globalservices.ode.url =http://localhost:8080/tcgs-ode

This is used by services that must send HTTP SOAPrequests to BPEL processes.

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 Teamcenter Enterprise connector EJBJNDI 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.

Ode BPEL Web application parameters(This solution is optional.)

APP_SERVER_PORT Specifies the HTTP port used by the applicationserver where the ODE service runs. Typically, this isthe Global Services application server.


Index

A

Action manager daemon . . . . . . . . . . . . 7-1Action Manager Service . . . . . . . . . . . . D-3Adding features . . . . . . . . . . . . . . . . . 16-2additional_applications directory . . . . . C-2advanced_installations directory . . . . . C-2Aerospace and DefenseAerospace and Defense ChangeManagement . . . . . . . . . . . . . . . . D-4

Aerospace and Defense Foundation . . D-4Aerospace and Defense FoundationTraining . . . . . . . . . . . . . . . . . . . D-4

Rich client . . . . . . . . . . . . . . . . . . . D-13AIWS client . . . . . . . . . . . . . . . . . . . D-10AIXConfiguration parameters . . . . . . . . . . 4-3Daemon startup scripts . . . . . . . . . . . 7-1Kernel parameters . . . . . . . . . . . . . . . 4-3Shell limits . . . . . . . . . . . . . . . . . . . . 4-2

Apache HTTP Server . . . . . . . . . . . . . . 8-37Apache Tomcat . . . . . . . . . . . . . . . . . . 8-37APP_SERVER_PORT parameter . . . . . E-13Apple Macintosh platformsSystem requirements . . . . . . . . . . . . . 1-3

Application Interface Web Service, see AIWSclientApplication serversHTTPServerTable . . . . . . . . . . 8-28, 8-34Teamcenter application server . . . . . 2-18Web tier . . . . . . . . . . . . . . . . . . . . . 1-11

ApplicationInstance . . . . . . . . . . . . . . 8-15ApplicationInstance contextparameter . . . . . . . . . . . . . . . . . . . . . E-9As-Built and As-MaintainedAlignment . . . . . . . . . . . . . . . . . . . . . D-9As-Built Management . . . . . . . . . . . . . D-9As-Maintained Management . . . . . . . . D-9ASP .NET State Service . . . . . . . . . . . . D-4AutoCAD integration, GM Overlay . . . . D-5Automatic logon, four-tier . . . . . . . . . . . 2-5Automotive Edition . . . . . . . . . . . . . . . D-4AutonomyIDOL server . . . . . . . . . . . . . . . . . . D-3

Autonomy Intelligent Data Operating Layer(IDOL) . . . . . . . . . . . . . . . . . . . . . . . D-3

B

Backing up installations . . . . . . . . . . . . 7-4Backing up Teamcenter data . . . . . . . . . 7-5BackupOracle databases . . . . . . . . . . . . . . . . 4-7

Base InstallFeatures . . . . . . . . . . . . . . . . . . . . . D-2

Best installation practices . . . . . . . . . . . 5-5Bounding box generation from JT . . . . . D-6Bounding box generation from NX . . . . D-7Brand Management . . . . . . . . . . . . . . D-5Business Modeler IDEClient . . . . . . . . . . . . . . . . . . . . . . . D-1Installing . . . . . . . . . . . . . . . . 10-1, 10-4Mapping Designer . . . . . . . . . . . . . D-12Solution . . . . . . . . . . . . . . . . . . . . . D-1Start . . . . . . . . . . . . . . . . . . . . . . . . 10-8

Business Modeler IDE 2-tier . . . . . . . . D-2Business Modeler IDE 4-tier . . . . . . . . D-2

C

CAD BOM Alignment . . . . . . . . . . . . . D-5CAD Part Library for Rich Client . . . . D-10Cadence Allegro Library Support . . . . . D-1,D-11Cadence Allegro Support . . . . . . . D-1, D-11cairoRequirements . . . . . . . . . . . . . . . . . . 1-2

Calibration and Configuration DataManagement . . . . . . . . . . . . . . . . . . D-10Catia Non BOM . . . . . . . . . . . . . . . . D-12cc_integration directory . . . . . . . . . . . . C-2Certification database . . . . . . . . . . . 1-1, 3-1Change Management . . . . . . . . . . . . . D-8Character set, ISO8859–1 . . . . . . . . . . . 5-3Character setsISO8859-1 . . . . . . . . . . . . . . . . . . . . . 1-5UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 1-5

CIFS volume data access . . . . . . . . . . . 2-18

PLM00011 F Installation on UNIX and Linux Servers Guide Index-1

Index

Classification L10N . . . . . . . . . . . . . . . D-8ClearCase . . . . . . . . . . . . . . . . . . . . D-10Client Enhancements . . . . . . . . . . . . . D-4Client for Office . . . . . . . . . . . . . . . . . D-7Client tierFour-tier . . . . . . . . . . . . . . . . . . . . . 1-10Two-tier . . . . . . . . . . . . . . . . . . . . . . 1-9

Client, Business Modeler IDE 2-tier . . . D-2Client, Business Modeler IDE 4-tier . . . D-2ClientsFCC . . . . . . . . . . . . . . . . . . . . . . . . 2-12Four-tier clients . . . . . . . . . . . . . . . . 1-10Rich client installation . . . . . . . . . . . . 2-7Thin client . . . . . . . . . . . . . . . . . . . . 2-10Two-tier clients . . . . . . . . . . . . . . . . . 1-9

CommandsCREATE DB . . . . . . . . . . . . . . . . . . . 3-6create_database . . . . . . . . . . . . . . 3-6–3-7dasdrop . . . . . . . . . . . . . . . . . . . . . . 21-3db2admin . . . . . . . . . . . . . . . . . . . . 21-2db2idrop . . . . . . . . . . . . . . . . . . . . . 21-2db2licm . . . . . . . . . . . . . . . . . . . . . . . 3-3db2set . . . . . . . . . . . . . . . . . . . . . . . . 3-4db2stop . . . . . . . . . . . . . . . . . . . . . . 21-4db2swtch . . . . . . . . . . . . . . . . . . . . . 21-2insweb . . . . . . . . . . . . . . . 8-2, 19-4–19-6

ConfigurationDatabases . . . . . . . . . . . . . . . . . . . . 4-16Multi-Site Collaboration . . . . . . . . . . . 7-2Multi-Site Collaboration daemons . . . . 7-3Oracle Net . . . . . . . . . . . . . . . . . . . . 4-15Teamcenter’s manufacturing processmanagement . . . . . . . . . . . . . . . . 12-1

Configure Resource Browser and NC PackageBrowser . . . . . . . . . . . . . . . . . . . . . . D-9Connecting . . . . . . . . . . . . . . . . . . . . . . 3-5ConnectivitySample database . . . . . . . . . . . . . . . . 3-5

Connector support files . . . . . . . . . . . . . 8-6Consumer Packaged GoodsBrand Management . . . . . . . . . . . . . D-5CPG Materials . . . . . . . . . . . . . . . . . D-5Packaging and Artwork . . . . . . . . . . D-5

Content and Document Management . . D-6Content Management . . . . . . . . . . . . . D-6Content Management Base feature . . D-6Content Management DITA feature . . D-6Content Management S1000Dfeature . . . . . . . . . . . . . . . . . . . . D-6

Content Management DITA . . . . . . . . . D-6Content Management installation . . . . 8-15Content Management S1000D . . . . . . . D-6Context parametersAPP_SERVER_PORT . . . . . . . . . . . . E-13

ApplicationInstance . . . . . . . . . 8-15, E-9global.services.proxy.password . . . . . E-10global.services.tceng2omfg.password . . . . . . . . . . E-12

global.services.teamcenter.password . . . . . . . . . . E-12

global.services.proxy.client.IPs . . . . . E-11global.services.proxy.user . . . . . . . . . E-10global.services.tceng2omfg.user . . . . . E-12global.services.teamcenter.user . . . . . E-12globalservices.OMfg.password . . . . . . E-12globalservices.OMfg.user . . . . . . . . . E-12globalservices.tceng2omfg.engdateinformat . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.engdateoutformat . . . . . . . . . . . . E-12

globalservices.tceng2omfg.JNDI_NAME . . . . . . . . . . . . . . . . . . . . E-13

globalservices.tceng2omfg.maxobjects . . . . . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.OmfgDateInFormat . . . . . . . . . . . E-12

globalservices.tceng2omfg.OmfgDateOutFormat . . . . . . . . . . E-12

globalservices.tceng2omfg.OmfgDateTimeInFormat . . . . . . . E-13

globalservices.tceng2omfg.ORACLE_CONFIG_NAME . . . . . . . . . . . . . E-13

globalservices.tceng2omfg.StagingDirectory . . . . . . . . . . . . . E-12

globalservices.tceng2omfg.UpdateAttrFile . . . . . . . . . . . . . . E-13

globalservices.tceng2omfg.XSLName . . . . . . . . . . . . . . . . . . E-13

globalservices.tceng2omfg.url . . . . . . E-12LogFileLocation . . . . . . . . . . . . 8-15, E-9RAC.OSGi.plugin.URL.suffix . . . . . . E-11SSOAppID . . . . . . . . . . . . . . . 8-15, E-9TcGSBOSJNDI . . . . . . . . . . . . 8-15, E-9TcGSConnectorJNDI . . . . . . . . . . . . E-11TcGSDORJNDI . . . . . . . . . . . . 8-15, E-9TcGSEngJNDI . . . . . . . . . . . . . . . . . E-11TcGSEntJNDI . . . . . . . . . . . . . . . . . E-12TcGSJDBCJNDI . . . . . . . . . . . 8-15, E-10TcGSMessageServerJNDI . . . . . 8-15, E-10TcGSNotifierReactorJNDI . . . . 8-15, E-10TcGSOMfgJNDI . . . . . . . . . . . . . . . E-12TcGSRACJNDI . . . . . . . . . . . . . . . . E-11TcGSSAPJNDI . . . . . . . . . . . . . . . . E-12TcGSSOAJNDI . . . . . . . . . . . . . . . . E-11TeamcenterConnectorJNDI . . . . . . . . E-11

CORP item creation fails . . . . . . . . . . . B-4Corporate serverFeatures . . . . . . . . . . . . . . . . . . . . . D-1

Index-2 Installation on UNIX and Linux Servers Guide PLM00011 F

Index

Installing . . . . . . . . . . . . . . . . . . . . . 6-5Windows, UTF-8 issues . . . . . . . . . . 17-4

Corrupted database, recovery . . . . . . . . B-13CPG Materials . . . . . . . . . . . . . . . . . . D-5Customization for eM-ServerIntegration . . . . . . . . . . . . . . . . . . . . D-9Customization for Process SimulaterIntegration . . . . . . . . . . . . . . . . . . . . D-9customScripts.log file . . . . . . . . . . . . . . 4-18

D

dasdrop command . . . . . . . . . . . . . . . . 21-3Database administration server(DAS) . . . . . . . . . . . . . . . . . . . . . . . . 21-2Database Configuration Assistant . . . 2-17,4-16Database Configuration for DPV . . . . . D-9Database daemonsInstallation . . . . . . . . . . . . . . . . . . . D-3Starting manually . . . . . . . . . . . . . . . 7-1

Database Daemons . . . . . . . . . . . . . . . D-3Action Manager Service . . . . . . . . . . D-3Subscription Manager Service . . . . . . D-3Task Manager Service . . . . . . . . . . . D-4Tesselation Manager Service . . . . . . . D-4

Database services . . . . . . . . . . . . . . . . D-3DatabasesAdding data directory toinstallation . . . . . . . . . . . . . . . . . 16-2

Adding database to installation . . . . . 16-3Data imports . . . . . . . . . . . . . . . . . . . 4-9Multiple database accessFour-tier rich clients . . . . . . . . . 16-4Overview . . . . . . . . . . . . . . . . . 16-4

RDV . . . . . . . . . . . . . . . . . . . . . . . . 2-17Recovering from a corrupteddatabase . . . . . . . . . . . . . . . . . . . B-13

Sample . . . . . . . . . . . . . . . . . . . . . . . 3-4Site planning . . . . . . . . . . . . . . . . . . 2-17Teamcenter . . . . . . . . . . . . . . . . . 3-6–3-7Templates . . . . . . . . . . . . 2-17, 4-16–4-17Unpopulating in IBM DB2 . . . . . . . . B-13Unpopulating in Oracle . . . . . . . . . . B-13

DB2, see IBM DB2DB2 support . . . . . . . . . . . . . . . . . . . . . 1-2db2admin command . . . . . . . . . . . . . . 21-2db2das1 account . . . . . . . . . . . . . . . . . . 3-1db2dasgp group . . . . . . . . . . . . . . . . . . . 3-1db2ese.lic file . . . . . . . . . . . . . . . . . . . . 3-3db2fenc1 account . . . . . . . . . . . . . . . . . . 3-1db2fengp group . . . . . . . . . . . . . . . . . . . 3-1db2idrop command . . . . . . . . . . . . . . . 21-2db2insgp group . . . . . . . . . . . . . . . . . . . 3-1

db2inst1 account . . . . . . . . . . . . . . . . . . 3-1db2licm command . . . . . . . . . . . . . . . . . 3-3db2set command . . . . . . . . . . . . . . . . . . 3-4db2stop command . . . . . . . . . . . . . . . . 21-4db2swtch command . . . . . . . . . . . . . . . 21-2dbscripts directory . . . . . . . . . . . . . . . 4-17dbshut utility . . . . . . . . . . . . . . . . . . . . 4-9Destination directories . . . . . . . . . . . . . 5-3DirectoriesWEB_ROOT . . . . . . . . . . . . . . . . . . . 8-2Web_tier . . . . . . . . . . . 8-2–8-3, 8-9, 8-15

Dispatcher . . . . . . . . . . . . . . . . . . . . . D-1Dispatcher Client . . . . . . . . . . . . . . . D-8Dispatcher Client for Rich Client . . . . D-7Dispatcher Server . . . . . . . . . . . . . . D-8

Dispatcher Client for Rich Client . . . . . D-7Dispatcher Server . . . . . . . . . . . . . . . . D-8Installation . . . . . . . . . . . . . . . . . . . D-1

dist_server.jar file . . . . . . . . . . . . . . . . 8-39Distributed services manager, see IDSMserver and IDSM proxy serverDistribution media . . . . . . . . . . . . . . . C-1Distribution serverAdding Web components . . . . . . . . . . 8-39Changing contents . . . . . . . . . . . . . . 8-39Installation . . . . . . . . . . . . . . . 8-22–8-23Starting . . . . . . . . . . . . . . . . . . . . . 8-38Stopping . . . . . . . . . . . . . . . . . . . . . 8-38

Distribution server instanceInstallation . . . . . . . . . . . . . . . 8-22, 8-32Web deployment . . . . . . . . . . . . . . . 8-35

Documentation distribution image . . . . C-1Download URL, IBM DB2 . . . . . . . . 3-1–3-2DPVGM Customization . . . . . . . . . . . . . . D-5

ds_manifest.mf file . . . . . . . . . . . . . . . 8-34

E

eBOP reports Customization . . . . . . . . D-9ECAD design managementCadence Allegro Support . . . . . . . . D-11Mentor Board Station Support . . . . D-11Mentor PADS 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-10EDADataset types . . . . . . . . . . . . . . . . D-10Server support . . . . . . . . . . . . . . . . D-10


Index

Standalone client . . . . . . . . . . . . . . . D-1EDA for Business Modeler IDE . . . . . D-10EDA Server Support . . . . . . . . . . . . . D-10EDA Stand-alone Client . . . . . . . . . . D-10eIntegrator Admin . . . . . . . . . . . . . . D-11Embedded Software SolutionsEmbedded Software Design DataManagement . . . . . . . . . . . . . . . D-10

Embedded viewer . . . . . . . . . . . . . . . . D-8Embedded visualization for rich client . . D-8EMPS – ECAD Translation . . . . . . . . D-10EMPS - Foundation . . . . . . . . . . . . . . D-10Enterprise Knowledge Foundationfeatures . . . . . . . . . . . . . . . . . . . . . . D-7Enterprise tier . . . . . . . . . . . . . . . . . . 1-11Environment settings, non-English localesNon-UTF-8 environmentsLinux . . . . . . . . . . . . . . . . 17-4, 17-7UNIX . . . . . . . . . . . . . . . . 17-4, 17-7

Environment variablesORACLE_HOME . . . . . . . . . . . . . . . . 4-8PATH . . . . . . . . . . . . . . . . . . . . . 4-7–4-8TC_DATA . . . . . . . . . . . . . . . . . . 2-2, 6-7TC_ROOT . . . . . . . . . . . . . . 2-2, 5-4, 6-6TCP_NODELAY . . . . . . . . . . . . . . . . 5-2TNS_ADMIN . . . . . . . . . . . . . . . . . . 4-15UGS_LICENSE_SERVER . . . . . . . . . 5-2

ERP Connect Toolkit . . . . . . . . . . . . . D-12Error logs . . . . . . . . . . . . . . . . . . . . . . B-1Error messages . . . . . . . . . . . . . . . . . . B-2ErrorsPool ID not available . . . . . . . . . . . . B-6SERVER_HOST parameter . . . . . . . B-6

ESS Base . . . . . . . . . . . . . . . . . . . . . D-10ESS Processor . . . . . . . . . . . . . . . . . . D-10ESS Software . . . . . . . . . . . . . . . . . . D-10ExportOracle databases . . . . . . . . . . . . . . . . 4-7

F

FCC . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12FCC for rich client . . . . . . . . . . . . . . . D-13FeaturesAerospace and Defense ChangeManagement . . . . . . . . . . . . . . . . D-4

Aerospace and Defense Foundation . . D-4Aerospace and Defense FoundationTraining . . . . . . . . . . . . . . . . . . . D-4

As-Built and As-MaintainedAlignment . . . . . . . . . . . . . . . . . D-9

As-Built Management . . . . . . . . . . . D-9As-Maintained Management . . . . . . . D-9

ASP .NET State Service . . . . . . . . . . D-4Automotive . . . . . . . . . . . . . . . . . . . D-4Base Install . . . . . . . . . . . . . . . . . . . D-2Bounding box generation from JT . . . D-6Bounding box generation from NX . . . D-7Brand Management . . . . . . . . . . . . . D-5Business Modeler IDE . . . . . . . . . . . D-1Business Modeler IDE 2-tier . . . . . . . D-2Business Modeler IDE 4-tier . . . . . . . D-2CAD BOM Alignment . . . . . . . . . . . . D-5CAD Part Library for Rich Client . . D-10Cadence Allegro Library Support . . . . D-1,D-11

Cadence Allegro Support . . . . . D-1, D-11Calibration and Configuration DataManagement . . . . . . . . . . . . . . . D-10

Catia Non BOM . . . . . . . . . . . . . . . D-12Change Management . . . . . . . . . . . . D-8Classification L10N . . . . . . . . . . . . . D-8Client Enhancements . . . . . . . . . . . . D-4Configure AutoCAD Integration for GMOverlay . . . . . . . . . . . . . . . . . . . D-5

Configure Resource Browser and NCPackage Browser . . . . . . . . . . . . . D-9

Content and DocumentManagement . . . . . . . . . . . . . . . . D-6

Content Management Base . . . . . . . . D-6Content Management DITA . . . . . . . D-6Content Management S1000D . . . . . . D-6Corporate server . . . . . . . . . . . . . . . D-1CPG Materials . . . . . . . . . . . . . . . . . D-5Customization for eM-ServerIntegration . . . . . . . . . . . . . . . . . D-9

Customization for Process SimulateIntegration . . . . . . . . . . . . . . . . . D-9

Database Configuration for DPV . . . . D-9Database Daemons . . . . . . . . . . . . . D-3Action Manager Service . . . . . . . D-3Subscription Manager Service . . . D-3Task Manager Service . . . . . . . . D-4Tesselation Manager Service . . . . D-4

Dispatcher . . . . . . . . . . . . . . . . . . . D-8Dispatcher Client . . . . . . . . . . . . . . . D-8Dispatcher Client for Rich Client . . . . D-7Dispatcher Server . . . . . . . . . . . . . . D-1eBOP reports Customization . . . . . . . D-9ECAD Design Management . . . . . . D-10ECAD Library Management . . . . . . D-11ECAD Part Library Management . . D-10EDA for Business Modeler IDE . . . . D-10EDA Server and Rich ClientSupport . . . . . . . . . . . . . . . . . . D-10

EDA Stand-alone Client . . . . . . . . . D-10


Index

EDA Standalone Client . . . . . . . . . . D-1Embedded Software Design DataManagement . . . . . . . . . . . . . . . D-10

EMPS – ECAD Translation . . . . . . . D-10EMPS - Foundation . . . . . . . . . . . . D-10Enterprise Knowledge Foundation . . . D-7ERP Connect . . . . . . . . . . . . . . . . . D-12ESS Base . . . . . . . . . . . . . . . . . . . D-10ESS Processor . . . . . . . . . . . . . . . . D-10ESS Software . . . . . . . . . . . . . . . . D-10Extensions . . . . . . . . . . . . . . . . . . . D-4Extensions for Office . . . . . . . . . . . D-12File Management . . . . . . . . . . . . . . . D-4Finished Product Management . . . . . D-5Finished Product Management to CPGMaterials Bridge . . . . . . . . . . . . . D-5

FMS Server Cache . . . . . . . . . . . D-1, D-4Full Text Search Engine . . . . . . . . . . D-3Global Services . . . . . . . . . . . . D-1, D-11Global Services Adapter . . . . . . . . . D-11Global Services Framework . . . D-1, D-11Global Services Monitoring GUI for RichClient . . . . . . . . . . . . . . . . . . . . D-11

Global Services Preferences . . . D-1, D-11GM Customization for DPV . . . . . . . . D-5GM Overlay . . . . . . . . . . . . . . . . . . . D-5GM PAD/TWP Customization . . . . . . D-5Hierarchical Storage Management(HSM) . . . . . . . . . . . . . . . . . . . . D-4

Install Libraries for AIWS Client . . . D-10Issue Management . . . . . . . . . . . . . . D-8J2EE Based Server Manager . . . D-1–D-2Lifecycle Visualization . . . . . . . . . . . D-8Maintenance, Repair, and Overhaul . . D-9Manufacturing ProcessManagement . . . . . . . . . . . . . . . . D-9

Mapping Designer . . . . . . . . . . . . . D-12Mechatronics ProcessManagement . . . . . . . . . . . . . . . D-10

Mentor Board Station LibrarySupport . . . . . . . . . . . . . . . D-1, D-11

Mentor Board Station Support . . . . D-11Mentor Expedition LibrarySupport . . . . . . . . . . . . . . . D-1, D-11

Mentor PADS Library Support . . . . . D-1,D-11

Mentor PADS Support . . . . . . . D-1, D-11Microsoft OfficeClient for Office . . . . . . . . . . . . . D-7Extensions for Office . . . . . . . . D-12

Microsoft Office client . . . . . . . . . . . . D-7MTM Data Card . . . . . . . . . . . . . . . D-9Multisite Collaboration IDSMService . . . . . . . . . . . . . . . . D-1, D-11

Multisite Collaboration ODSService . . . . . . . . . . . . . . . . D-1, D-11

.NET Based Server Manager . . . . . . . D-3NX Integration . . . . . . . . . . . . . . . . D-6NX Manager for Rich Client . . . . . . . D-6NX UG Integration . . . . . . . . . . . . . D-1Office Client for Microsoft Office . . . . D-7Online Help . . . . . . . . . . . . . . . . . . . D-3Oracle Manufacturing Integration . . D-12Packaging and Artwork . . . . . . . . . . D-5Packaging and Artwork to Finished ProductManagement Bridge . . . . . . . . . . D-6

PAD/TWP Customization . . . . . . . . D-10Platform Extensability . . . . . . . . . . D-11QPL for Repeatable DigitalValidation . . . . . . . . . . . . . . . . . . D-7

Remote Workflow . . . . . . . . . . . . . . . D-7Render Document for Rich Client . . . D-8Rich Client (Lite Edition) . . . . . . . . . D-2Rich Client 2-tier . . . . . . . . . . . . . . . D-2Rich Client 4-tier . . . . . . . . . . . . . . . D-2Rich Client, Dispatcher Client . . . . . . D-7Sample Files . . . . . . . . . . . . . . . . . . D-3SCM ClearCase for Foundation . . . . D-10Server Enhancements . . . . . . . . . . . D-2Service Event Management . . . . . . . D-9Service Planning . . . . . . . . . . . . . . . D-9Service Planning and Service ProcessingAlignment . . . . . . . . . . . . . . . . . D-9

Service Request Processing . . . . . . . . D-9Single Sign-on for Rich Client . . . . . . D-4Spatial Search . . . . . . . . . . . . . . . . . D-6Specification Manager . . . . . . . . . . . D-5SRM Integration . . . . . . . . . . . . . . D-12Supplier RelationshipManagement . . . . . . . . . . . . . . . D-12

Systems Engineering and RequirementsManagement . . . . . . . . . . . . . . . D-12

Teamcenter Automotive Edition . . . . D-4Teamcenter Extensions for MicrosoftOffice . . . . . . . . . . . . . . . . . . . . D-12

Teamcenter for Reporting andAnalytics . . . . . . . . . . . . . . . . . D-12

Teamcenter Foundation . . . . . . . D-1–D-2Teamcenter Manufacturing . . . . . . . . D-9Teamcenter Rich Client (Shared DiskDeployment) . . . . . . . . . . . . . . . . D-2

Teamcenter Rich Client 2-tier . . . . . . D-1Teamcenter Rich Client 4-tier . . . . . . D-1Teamcenter Security Services . . . . . . D-3Teamcenter Visualization 8 (Embedded) forRich Client . . . . . . . . . . . . . . . . . D-8

Teamcenter Visualization 8 (Stand-alone)for Rich Client . . . . . . . . . . . . . . D-8


Index

Teamcenter Web Tier . . . . . . . . . . . . D-4Tecnomatix . . . . . . . . . . . . . . . . . . . D-9Trueshape generation from JT . . . . . D-7Vendor Management . . . . . . . . . . . D-12Web Tier for .NET . . . . . . . . . . . . . . D-4Wire Harness Configuration . . . . . . D-10Wire Harness Configuration in GMOverlay . . . . . . . . . . . . . . . . . . . D-5

Workflow to SchedulingIntegration . . . . . . . . . . . . . . . . D-12

File Management features . . . . . . . . . . D-4File Management SystemInstallation . . . . . . . . . . . . . . . . D-1, D-4Installation overview . . . . . . . . . . . . 2-10Volume server . . . . . . . . . . . . . . . . . D-1

Filesdb2ese.lic . . . . . . . . . . . . . . . . . . . . . 3-3INSTALL_TCWEB.TZ . . . . . . . . . . . . 8-2jakarta-regexp-1.3.jar . . . . . . . . . . . . B-4mti.jar . . . . . . . . . . . . . . . . . . . . . . . 8-7mtiems.jar . . . . . . . . . . . . . . . . . . . . . 8-7ojdbc14.jar . . . . . . . . . . . . . . . . . . . . 8-9

Finished Product Management . . . . . . . D-5Finished Product Management to CPGMaterials Bridge . . . . . . . . . . . . . . . . D-5FMSFCC . . . . . . . . . . . . . . . . . . . . . . . . 2-12FSC . . . . . . . . . . . . . . . . . . . . . . . . 2-11Master configuration file . . . . . . . . . . 2-12See File Management System . . . . . . 2-10FMS Client Cache . . . . . . . . . . . . . . . D-13FMS server cache . . . . . . . . . . . . . . . . D-1Fms_BootStrap_Urls preference . . . . . . . 6-4Four-tier architectureInstallation overview . . . . . . . . . . . . . 2-4Overview . . . . . . . . . . . . . . . . . . . . . 1-10Troubleshooting deployment . . . . . . . B-5

FSCInstallation overview . . . . . . . . . . . . 2-11Transient server . . . . . . . . . . . . . . . 2-11

Full Text Search Engine . . . . . . . . . . . D-3

G

genius2mrm_copy_files.ucl script . . . . . 12-2Genius4000 data migration . . . . . . . . . 12-1Global Services . . . . . . . . . . . . . 2-15, D-11Features . . . . . . . . . . . . . . . . . . . . . D-1

Global Services Adapter . . . . . . . . . . . D-11Global Services Axis2 Services . . . . . . . 8-12Global Services Data Exchange . . . . . . 8-14Global Services EPSync Reactor . . . . . . 8-12Global Services Framework . . . . . D-1, D-11

Global Services Gateway for OracleManufacturing (Engineering) . . . . . . . 8-12Global Services Gateway for OracleManufacturing (Enterprise) . . . . . . . . 8-13Global Services Global ServicesConnector . . . . . . . . . . . . . . . . . . . . . 8-14Global Services installation . . . . . . . . . . 8-9Global Services Monitoring GUI for RichClient . . . . . . . . . . . . . . . . . . . . . . . D-11Global Services MS Messaging . . . . . . . 8-12Global Services Ode BPEL webapplication . . . . . . . . . . . . . . . . . . . . 8-14Global Services Oracle ManufacturingConnector . . . . . . . . . . . . . . . . . 8-13–8-14Global Services Preferences . . . . . D-1, D-11Global Services Security Proxy . . . . . . . 8-14Global Services solutionsAxis2 Services . . . . . . . . . . . . . . . . . 8-12EPSync Reactor . . . . . . . . . . . . . . . . 8-12Global Services BPEL Framework . . . 8-14Global Services Security Proxy . . . . . 8-14Global Services user interface . . . . . . 8-14JMS messaging . . . . . . . . . . . . . . . . 8-12Oracle Manufacturing . . . . . . . 8-12, 8-14Teamcenter 2007 or later . . . . . . . . . 8-11Teamcenter 2007 through Teamcenter2007.1 MP4 (full rich clientfunctionality) . . . . . . . . . . . . . . . 8-12

Teamcenter 2007.1 MP5 through MP8 (fullrich client functionality) . . . . . . . . 8-12

Teamcenter 8 Global Services Framework- Data Exchange . . . . . . . . . . . . . 8-14

Teamcenter 8 Global Services Framework- Global Services Connector . . . . . 8-14

Teamcenter 8 Global Services Framework- Teamcenter Sourcing . . . . . . . . . 8-14

Teamcenter 8 or later (full rich clientfunctionality) . . . . . . . . . . . . . . . 8-11

Teamcenter Engineering . . . . . . . . . . 8-12Teamcenter Engineering 2005 through2007 . . . . . . . . . . . . . . . . . . . . . . 8-12

Teamcenter Enterprise . . . . . . . . . . . 8-12Teamcenter Gateway for OracleManufacturing . . . . . . . . . . . . . . 8-13

Web services . . . . . . . . . . . . . . . . . . 8-12Global Services Teamcenter 2007 Rich ClientConnector . . . . . . . . . . . . . . . . . . . . . 8-12Global Services Teamcenter 2007.1 Rich ClientConnector . . . . . . . . . . . . . . . . . . . . . 8-12Global Services Teamcenter 8 Rich ClientConnector . . . . . . . . . . . . . . . . . . . . . 8-11Global Services Teamcenter Engineering2005/2007 Connector . . . . . . . . . . . . . 8-12


Index

Global Services Teamcenter Engineering V9Connector . . . . . . . . . . . . . . . . . . . . . 8-12Global Services Teamcenter EnterpriseConnector . . . . . . . . . . . . . . . . . . . . . 8-12Global Services Teamcenter SOAConnector . . . . . . . . . . . . . . . . . . . . . 8-11Global Services Teamcenter Sourcing . . 8-14Global Services User Interface . . . . . . . 8-14Global Services Web ServicesConnector . . . . . . . . . . . . . . . . . . . . . 8-12global.services.tceng2omfg.passwordparameter . . . . . . . . . . . . . . . . . . . . . E-12global.services.teamcenter.passwordparameter . . . . . . . . . . . . . . . . . . . . . E-12global.services.proxy.client.IPs contextparameter . . . . . . . . . . . . . . . . . . . . . E-11global.services.proxy.password contextparameter . . . . . . . . . . . . . . . . . . . . . E-10global.services.proxy.user contextparameter . . . . . . . . . . . . . . . . . . . . . E-10global.services.tceng2omfg.userparameter . . . . . . . . . . . . . . . . . . . . . E-12global.services.teamcenter.userparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.OMfg.passwordparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.OMfg.user parameter . . . E-12globalservices.tceng2omfg.engdateinformatparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.engdateoutformatparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.JNDI_NAMEparameter . . . . . . . . . . . . . . . . . . . . . E-13globalservices.tceng2omfg.maxobjectsparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.OmfgDateInFormatparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.OmfgDateOutFormat parameter . . . . . E-12globalservices.tceng2omfg.OmfgDateTimeInFormatparameter . . . . . . . . . . . . . . . . . . . . . E-13globalservices.tceng2omfg.ORACLE_CONFIG_NAME parameter . . . . . . . . E-13globalservices.tceng2omfg.StagingDirectoryparameter . . . . . . . . . . . . . . . . . . . . . E-12globalservices.tceng2omfg.UpdateAttrFileparameter . . . . . . . . . . . . . . . . . . . . . E-13globalservices.tceng2omfg.XSLNameparameter . . . . . . . . . . . . . . . . . . . . . E-13globalservices.tceng2omfg.urlparameter . . . . . . . . . . . . . . . . . . . . . E-12GM Customization for DPV . . . . . . . . . D-5GM Overlay . . . . . . . . . . . . . . . . . . . . D-5

CORP item creation fails . . . . . . . . . B-4GM Overlay, AutoCAD integration . . . . D-5GM Overlay, Wire HarnessConfiguration . . . . . . . . . . . . . . . . . . D-5GM PAD/TWP Customization . . . . . . . . D-5Groupsdb2dasgp . . . . . . . . . . . . . . . . . . . . . . 3-1db2fengp . . . . . . . . . . . . . . . . . . . . . . 3-1db2insgp . . . . . . . . . . . . . . . . . . . . . . 3-1

H

Hebrew language . . . . . . . . . . . . . . . 17-13Heterogeneous network environment . . 2-18Hewlett-Packard HP-UX, Javaconfiguration . . . . . . . . . . . . . . . . . . . . 1-4Hierarchical Storage Management(HSM) . . . . . . . . . . . . . . . . . . . . . . . D-4Homogeneous network environment . . . 2-18HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Kernel parameter requirements . . . . . 4-3

HP-UX, kernel parameters . . . . . . . . . . B-9HSM . . . . . . . . . . . . . . . . . . . . . . . . . D-4HTML pages . . . . . . . . . . . . . . . . . . . . 8-23

I

IBM DB2Certified versions . . . . . . . . . . . . . . . . 3-1Download URL . . . . . . . . . . . . . . 3-1–3-2Installation . . . . . . . . . . . . . . . . . . . . 3-1Linux . . . . . . . . . . . . . . . . . . . . . 3-1UNIX . . . . . . . . . . . . . . . . . . . . . 3-1

License . . . . . . . . . . . . . . . . . . . . . . . 3-3Requirements . . . . . . . . . . . . . . . . . . 3-1Software image . . . . . . . . . . . . . . . . . 3-1Unpopulating database . . . . . . . . . . B-13Users and groupsUNIX, Linux . . . . . . . . . . . . . . . . 3-1

IBM DB2 support . . . . . . . . . . . . . . . . . 1-2ICD files, copyingGlobal Services . . . . . . . . . . . . . . . . . 8-9Teamcenter Web tier . . . . . . . . . . . . . 8-3

IDOL . . . . . . . . . . . . . . . . . . . . . . . . . D-3IDOL server, Autonomy . . . . . . . . . . . . D-3IDSM proxy server . . . . . . . . . . . . . . . . 2-3IDSM server . . . . . . . . . . . . . . . . . . . . . 2-3IDSM Service . . . . . . . . . . . . . . . . . . D-11IDSM_permitted_sites preference . . . . . . 7-3images directory . . . . . . . . . . . . . . . . . 8-35Imports . . . . . . . . . . . . . . . . . . . . . . . . 4-9infodba . . . . . . . . . . . . . . . . . . . . . 1-5, 2-19Install images for connectors . . . . . . . . . 8-6Install Libraries for AIWS Client . . . . D-10


Index

INSTALL_TCWEB.EXE file . . . . . . . . . . 8-2InstallationBest practices . . . . . . . . . . . . . . . . . . 5-5Creating a configuration . . . . . . . . . . 16-1Distribution server . . . . . . . . . . . . . . 8-23Distribution server instance . . . . . . . 8-32IBM DB2Linux . . . . . . . . . . . . . . . . . . . . . 3-1UNIX . . . . . . . . . . . . . . . . . . . . . 3-1

Modifying a configuration . . . . . . . . . 16-2Oracle . . . . . . . . . . . . . . . . . . . 2-17, 4-10Over-the-Web . . . . . . . . . . . . . . 1-9, 8-23Rich client instance . . . . . . . . . . . . . 8-25Silent . . . . . . . . . . . . . . . . . . . . . . . 18-1Teamcenter servers . . . . . . . . . . . . . . 6-1Using TEM . . . . . . . . . . . . . . . . 1-9, 8-23Web Application Manager . . . . . . . . . . 8-2

installed_programs.dat file . . . . . . . . . . . 5-5installed.html file . . . . . . . . . . . . . . . . 8-35installfailed.html file . . . . . . . . . . . . . . 8-35InstallingBusiness Modeler IDE . . . . . . . 10-1, 10-4Templates . . . . . . . . . . . . . . . . . . . . 11-1

installing.html file . . . . . . . . . . . . . . . . 8-35insweb command . . . . . . . . . . . . . 8-2, 8-23,8-32, 8-39, 19-4–19-6IntegrationsMicrosoft Office . . . . . . . . . . . . D-7, D-12

Internationalizationweb_gen_xml utility . . . . . . . . . . . . 17-10web_gen_xml.dat file . . . . . . . . . . . 17-10webstrings.xml file . . . . . . . . . . . . . 17-10

ISO8859-1 character set . . . . . . . . . . . . 1-5ISO8859-1 mode . . . . . . . . . . . . . . . . . . 5-4ISO8859–1 character set . . . . . . . . . . . . 5-3Issue Management . . . . . . . . . . . . . . . D-8

J

J2EE based server manager . . . . . . . . 1-11,2-2, 6-6, 9-6J2EE Based Server Manager . . . . . D-1–D-2jakarta-regexp-1.3.jar file . . . . . . . . . . . B-4Java . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Java Runtime Environment . . . . . . . . . . 8-2JBoss Cache TreeCache . . 8-5, 9-1, 16-7, E-8

K

Kernel parameters . . . . . . . . . . . . 4-2, B-9

L

launcherror.html file . . . . . . . . . . . . . . 8-35

LaunchingBusiness Modeler IDE . . . . . . . . . . . 10-8

Libraries . . . . . . . . . . . . . . . . . . . . . D-10Licenses, IBM DB2 . . . . . . . . . . . . . . . . 3-3Licensing levelAuthor . . . . . . . . . . . . . . . . . . . . . . . 5-1Consumer . . . . . . . . . . . . . . . . . . . . . 5-1

Linux considerations . . . . . . . . . . . . . . . 1-5Listener processes . . . . . . . . . . 4-8–4-9, 4-15listener.ora file . . . . . . . . . . . . . . . 4-9, 4-15LocalizationConverting to Unicode . . . . . . . . . . 17-13Hebrew language . . . . . . . . . . . . . . 17-13Rich client . . . . . . . . . . . . . . . . . . . 17-13Thin client . . . . . . . . . . . . . . . . . . . 17-13

localization directory . . . . . . . . . . . . . . C-2LogFileLocation . . . . . . . . . . . . . . . . . 8-15LogFileLocation context parameter . . . . E-9Logon, automatic . . . . . . . . . . . . . . . . . 2-5

M

Macintosh platformsSystem requirements . . . . . . . . . . . . . 1-3

Maintenance packs . . . . . . . . . . . . . . . 19-1Maintenance, Repair, and Overhaul . . . D-9Manifest file . . . . . . . . . . . . . . . . . . . . 8-34Manufacturing Process Management . . D-9Mapping Designer . . . . . . . . . . . . . . . D-12Master configuration file . . . . . . . . . . . 2-12Mechatronics Process Managementfeatures . . . . . . . . . . . . . . . . . . . . . D-10Media, distribution . . . . . . . . . . . . . . . C-1Memory management . . . . . . . . . . . . . 10-6Mentor Board Station LibrarySupport . . . . . . . . . . . . . . . . . . D-1, D-11Mentor Board Station Support . . . . . . D-11Mentor Expedition Library support . . D-11Mentor Expedition Library Support . . . D-1Mentor PADS Library Support . . . . . . . D-1Mentor PADS Support . . . . . . . . . D-1, D-11Microsoft Office client . . . . . . . . . . . . . D-7Microsoft Office extensions . . . . . . . . . D-12Migration, Genius4000 data . . . . . . . . . 12-1Mixed-language displayThin client . . . . . . . . . . . . . . . . . . . . 17-2

MRO As-Built and As-MaintainedAlignment . . . . . . . . . . . . . . . . . . . . . D-9MRO As-Built Management . . . . . . . . . D-9MRO As-Maintained Management . . . . D-9mti.jar file . . . . . . . . . . . . . . . . . . . . . . 8-7mtiems.jar file . . . . . . . . . . . . . . . . . . . 8-7MTM Data Card . . . . . . . . . . . . . . . . . D-9Multi-Site Collaboration


Index

Configuring daemons . . . . . . . . . . . . . 7-3IDSM service . . . . . . . . . . . . . . . . . . D-1Installation . . . . . . . . . . . . . . . . . . . D-1Local disk installation . . . . . . . . . . . . 5-3ODS service . . . . . . . . . . . . . . . . . . . D-1Postinstallation tasks . . . . . . . . . . . . . 7-2Proxy server . . . . . . . . . . . . . . . . . . D-1Wide area networks . . . . . . . . . . . . . . 7-2

Multiple database accessFour-tier rich clients . . . . . . . . . . . . . 16-4Overview . . . . . . . . . . . . . . . . . . . . . 16-4

Multiple EAR file support . . . . . . . . . . 8-21

N

native2ascii utility . . . . . . . . . . . . . . 17-14.NET based server manager . . . . . . . . . 1-11.NET Based Server ManagerNET Based Server Manager . . . . . . . D-3.NET State Service . . . . . . . . . . . . . . . D-4NET Web tier . . . . . . . . . . . . . . . . . . . D-4ASP .NET State Service . . . . . . . . . . D-4

.NET Web tier . . . . . . . . . . . . . . . . . . . D-4ASP .NET State Service . . . . . . . . . . D-4Server manager . . . . . . . . . . . . . . . . 1-11Windows . . . . . . . . . . . . . . . . . . . . . 1-11

Network FoldersDescription . . . . . . . . . . . . . . . . . . . . 1-8

NetworksClient installation . . . . . . . . . . . . . . 2-18Heterogeneous networkenvironment . . . . . . . . . . . . . . . . 2-18

Homogeneous networkenvironment . . . . . . . . . . . . . . . . 2-18

Site planning . . . . . . . . . . . . . . . . . . . 2-1NFS volume data access . . . . . . . . . . . 2-18NX . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5NX Integration . . . . . . . . . . . . . . . . . . D-6NX Manager for Rich Client . . . . . . . . . D-6NX UG Integration . . . . . . . . . . . . . . . D-1

O

Object directory services, see ODS server andODS proxy serverODS proxy server . . . . . . . . . . . . . . . . . 2-3ODS server . . . . . . . . . . . . . . . . . . . . . . 2-3ODS Service . . . . . . . . . . . . . . . . . . . D-11ODS_permitted_sites preference . . . . . . . 7-3ODS_searchable_sites preference . . . . . . 7-3ODS_site preference . . . . . . . . . . . . . . . 7-3ojdbc14.jar file . . . . . . . . . . . . . . . . . . . 8-9Online help . . . . . . . . . . . . . . . . . . . . . . 8-2Distribution image . . . . . . . . . . . . . . C-2

HTML . . . . . . . . . . . . . . . . . . . . . . . C-3Installation . . . . . . . . . . . . . . . . 8-4, D-3Installation alternatives . . . . . . 2-17, 15-1Over-the-Web access . . . . . . . . . . . . . 15-2PDF . . . . . . . . . . . . . . . . . . . . . . . . C-3Rich client . . . . . . . . . . . . . . . . . . . . 15-2tchelp.jar file . . . . . . . . . 6-1, 6-9, 8-4, D-3Troubleshooting . . . . . . . . . . . . . . . . B-2

Online Help . . . . . . . . . . . . . . . . . . . . D-3Operating system accounts . . . . . . 1-5, 2-19Operating system support . . . . . . . . . . . 1-1OracleData imports . . . . . . . . . . . . . . . . . . . 4-9Database Configuration Assistant . . 2-17,4-16

Database creation . . . . . . . . . . . . . . 4-16Database export . . . . . . . . . . . . . . . . . 4-7Database planning . . . . . . . . . . . . . . 2-17Database upgrades . . . . . . . . . . . . 4-7, 4-9Installation . . . . . . . . . . . . . . . 2-17, 4-10Kernel parameters . . . . . . . . . . . . . . . 4-2Listener processes . . . . . . . . 4-8–4-9, 4-15Net configuration . . . . . . . . . . . . . . . 4-15oerr utility . . . . . . . . . . . . . . . . . . . . B-9Required version . . . . . . . . . . . . 4-16, 6-7Semaphore resources . . . . . . . . . . . . . 4-2Shared memory resources . . . . . . . . . . 4-2Site planning . . . . . . . . . . . . . . . . . . 2-17Software distribution image . . . . . . . C-1Uninstallation . . . . . . . . . . . . . . . . . 21-5Unpopulating database . . . . . . . . . . B-13

Oracle Manufacturing Integration . . . D-12Oracle Net Assistant . . . . . . . . . . . . . . 4-15ORACLE_HOME environmentvariable . . . . . . . . . . . . . . . . . . . . . . . 4-8oratab utility . . . . . . . . . . . . . . . . . . . . 4-9otw_installer.jar file . . . . . . . . . . . . . . . 8-35otw.html file . . . . . . . . . . . . . . . . . . . . 8-36Over-the-Web Installer . . . . . . . 8-23, 8-27,8-33, 8-35, 19-4–19-5Over-the-Web rich client . . . . . . . . . . . 8-22

P

Packaging and Artwork . . . . . . . . . . . . D-5Packaging and Artwork to Finished ProductManagement Bridge . . . . . . . . . . . . . D-6PAD/TWP Customization . . . . . . . . . . D-10PADS library support . . . . . . . . . . . . D-11PADS support . . . . . . . . . . . . . . . . . . D-11Parametersglobal.services.proxy.service.URL . . . E-10Kernel . . . . . . . . . . . . . . . . . . . . . . B-9Web tier . . . . . . . . . . . . . . . . . . . . . E-1


Index

Patches . . . . . . . . . . . . . . . . . . . . . . . 19-1Patching rich clientDescribed . . . . . . . . . . . . . . . . . . . . 19-3Silently . . . . . . . . . . . . . . . . . . . . . . 19-4Using Over-the-Web Installer . . . . . . 19-4

Patching Teamcenter’s lifecyclevisualization . . . . . . . . . . . . . . . . . . . 19-5Patching the server . . . . . . . . . . . . . . . 19-2Patching thin client . . . . . . . . . . . . . . . 19-6PATH environment variable . . . . . . . 4-7–4-8Platform support . . . . . . . . . . . . . . . . . . 1-1Database servers . . . . . . . . . . . . . . . . 1-2

POM transmit schema files . . . . . . . . . . 7-3portal directory . . . . . . . . . . . . . . . . . . C-2portalHelpPage property . . . . . . . . . . . B-2Postinstallation tasks . . . . . . . . . . . . . . 7-1Postupgrade tasks . . . . . . . . . . . . . . . . . 7-1PreferencesFms_BootStrap_Urls . . . . . . . . . . . . . 6-4IDSM_permitted_sites . . . . . . . . . . . . 7-3ODS_permitted_sites . . . . . . . . . . . . . 7-3ODS_searchable_sites . . . . . . . . . . . . 7-3ODS_site . . . . . . . . . . . . . . . . . . . . . . 7-3TC_publishable_classes . . . . . . . . . . . 7-3TC_transfer_area . . . . . . . . . . . . . . . . 7-3WEB_core_help_server . . . 15-4, 15-6, B-2WEB_default_site_deployed_app_name . . . . . . . . . . . . . . . . . . . . . B-3

WEB_help_server . . . . . . 15-4, 15-6, B-2Preinstallation tasks . . . . . . . . . . . . . . . 5-1Prerequisite software . . . . . . . . . . . . . . 1-1PrerequisitesCharacter set . . . . . . . . . . . . . . . . . . . 5-3GM Overlay . . . . . . . . . . . . . . . . . . . . 5-3

Problem Reports (PRs) . . . . . . . . . . . . . 19-8ProgramsWeb Application Manager . . . . . 19-4–19-6

Properties, portalHelpPage . . . . . . . . . B-2Proxy WAR file (WebLogic) . . . . . . . 8-6, 8-17

Q

QPL for Repeatable Digital Validation . . D-7QPL server . . . . . . . . . . . . . . . . . . . . . . 2-3

R

RAC.OSGi.plugin.URL.suffix contextparameter . . . . . . . . . . . . . . . . . . . . . E-11rc.ugs file . . . . . . . . . . . . . . . . . . . . . . . 7-1rc.ugs.actionmgrd script . . . . . . . . . . . . . 7-1rc.ugs.subscriptionmgrd script . . . . . . . . 7-1rc.ugs.task_monitor script . . . . . . . . . . . 7-1RDV

Database instance . . . . . . . . . . . . . . 2-17QPL server . . . . . . . . . . . . . . . . . . . . 2-3

README file . . . . . . . . . . . . . . . . . . . 19-8Remote Method Invocation . . . . . . 8-25, 8-38Remote workflowSite planning . . . . . . . . . . . . . . . . . . 2-16

Remote Workflow . . . . . . . . . . . . . . . . D-7Installation . . . . . . . . . . . . . . . . . . . D-7

Removing features . . . . . . . . . . . . . . . 16-2RenderFormats . . . . . . . . . . . . . . . . . . . . . 14-2Prerequisites . . . . . . . . . . . . . . . . . . 14-1Translators . . . . . . . . . . . . . . . . . . . 14-1

Render Document for Rich Client . . . . . D-8Render ManagerInstallation . . . . . . . . . . . . . . . . . . . D-8Required features . . . . . . . . . . . . . . D-8

Repeatable Digital Validation . . . . . . . . D-7RequirementsDatabase . . . . . . . . . . . . . . . . . . . . . . 1-1Database, IBM DB2 . . . . . . . . . . . . . . 3-1IBM DB2 . . . . . . . . . . . . . . . . . . . . . . 3-1Java . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Operating systems . . . . . . . . . . . . . . . 1-1

Resource Manager, Genius4000 datamigration . . . . . . . . . . . . . . . . . . . . . 12-1Resource tierFour-tier . . . . . . . . . . . . . . . . . . . . . 1-11Two-tier . . . . . . . . . . . . . . . . . . . . . . 1-9

Rich clientDeployment over the Web . . . . . . . . . 8-22Description . . . . . . . . . . . . . . . . . . . . 1-8Four-tier . . . . . . . . . . . . . . . . . . D-1–D-2Installing patches . . . . . . . . . . . . . . 19-3Language display configuration . . . . . 17-2Localization . . . . . . . . . . . . . 17-10, 17-13Online help . . . . . . . . . . . . . . . 15-2, B-2Overview . . . . . . . . . . . . . . . . . . . . . . 1-8Two-tier . . . . . . . . . . . . . . . . . . D-1–D-2

Rich Client (Lite Edition) . . . . . . . . . . . D-2Rich Client (Shared Disk Deployment) . . D-2Rich client distribution server, seeDistributionserverRich client distribution server instance, seeDistribution server instanceRich client instanceDeployment . . . . . . . . . . . . . . . . . . . 8-35Installation . . . . . . . . . . . . . . . . . . . 8-25

Rich client instance, four-tier . . . . . . . . 8-32Rich client solutions, patching . . . . . . . 19-3RMI registryPort number . . . . . . . . . . . . . . . . . . 8-25Starting . . . . . . . . . . . . . . . . . . . . . 8-38Stopping . . . . . . . . . . . . . . . . . . . . . 8-39


Index

S

Sample database . . . . . . . . . . . . . . . 3-4–3-5Sample files . . . . . . . . . . . . . . . . . . . . D-3Sample Files . . . . . . . . . . . . . . . . . . . . D-3SCM ClearCase for Foundation . . . . . D-10Security Services . . . . . . . . . . . . . . . . 2-16Semaphore resources . . . . . . . . . . . . . . . 4-2ServerInstalling patches . . . . . . . . . . . . . . 19-2

Server EnhancementsFeatures . . . . . . . . . . . . . . . . . . . . . D-2

Server managerJ2EE . . . . . . . . . . . . . . . . . . . . . . . D-2J2EE based . . . . . . . . . . . . . 1-11, 2-2, 6-6J2EE based, starting . . . . . . . . . . . . . 9-6J2EE based, troubleshooting . . . . . . . B-6.NET . . . . . . . . . . . . . . . . . . . . . . . . D-3.NET based . . . . . . . . . . . . . . . . 1-11, 2-2

SERVER_HOST parameter . . . . . . 9-1, B-6Server, patching . . . . . . . . . . . . . . . . . 19-2serverPool.properties file . . . . . . . . 9-1, B-6Service Event Management . . . . . . . . . D-9Service Planning . . . . . . . . . . . . . . . . . D-9Service Planning and Service ProcessingAlignment . . . . . . . . . . . . . . . . . . . . . D-9Service Request Processing . . . . . . . . . D-9ServicesAction Manager . . . . . . . . . . . . . . . . D-3ASP .NET State Service . . . . . . . . . . D-4IDSM Service . . . . . . . . . . . . . . . . D-11ODS Service . . . . . . . . . . . . . . . . . D-11Subscription Manager . . . . . . . . . . . D-3Task Manager . . . . . . . . . . . . . . . . . D-4Tesselation Manager . . . . . . . . . . . . D-4

Shared Disk Deployment, rich client . . . D-2Shared memory resources . . . . . . . . . . . 4-2Silent installation . . . . . . . . . . . . . . . . 18-1Silent patching . . . . . . . . . . . . . . . . . . 19-4Single sign-on for rich client . . . . . . . . . D-4Site planning . . . . . . . . . . . . . . . . . . . . 2-1Software distribution image . . . . . . . . . C-1Software requirements . . . . . . . . . . . . . 1-1Application servers . . . . . . . . . . . . . . 8-2Java . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

SolutionsBusiness Modeler IDE . . . . . . . . . . . D-1Corporate Server . . . . . . . . . . . . . . . D-1Dispatcher (Dispatcher Server) . . . . . D-1EDA Standalone Client . . . . . . . . . . D-1Global Services . . . . . . . . . . . . . . . . D-1Multisite Collaboration ProxyServer . . . . . . . . . . . . . . . . . . . . D-1

Rich Client 2-tier . . . . . . . . . . . . . . . D-1

Rich Client 4-tier . . . . . . . . . . . . . . . D-1Volume Server . . . . . . . . . . . . . . . . . D-1

Spatial Search . . . . . . . . . . . . . . . . . . D-6Specification Manager . . . . . . . . . . . . . D-5Specifying a specific bind address when a hosthas multiple IP addresses . . . . . . . . . B-6SRM Integration . . . . . . . . . . . . . . . . D-12SSOAppID . . . . . . . . . . . . . . . . . . . . . 8-15SSOAppID context parameter . . . . . . . E-9Stand-alone application viewer . . . . . . . D-8Stand-alone ApplicationsEDA Stand-alone Client . . . . . . . . . D-10

start_rmi file . . . . . . . . . . . . . . . . . . . 8-38start_server file . . . . . . . . . . . . . . . . . . 8-38StartingBusiness Modeler IDE . . . . . . . . . . . 10-8

stop_server file . . . . . . . . . . . . . . . . . . 8-39Subscription manager daemon . . . . . . . . 7-1Subscription Manager Service . . . . . . . D-3Sun ONE . . . . . . . . . . . . . . . . . . . . . . 8-37Sun Solariscario required . . . . . . . . . . . . . . . . . . 1-2

Support filesmtiems.jar . . . . . . . . . . . . . . . . . . . . . 8-7Oracle manufacturing connector . . . . . 8-9Teamcenter Enterprise connector . . . . 8-7

System requirementscairo . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

T

Task Manager Service . . . . . . . . . . . . . D-4Task monitor daemon . . . . . . . . . . . . . . 7-1TC_auto_login preference . . . . . . . . . . . 2-5TC_DATA environment variable . . . . 2-2, 6-7TC_publishable_classes preference . . . . . 7-3TC_ROOT environment variable . . . . . 2-2,5-4, 6-6TC_transfer_area preference . . . . . . . . . 7-3TcGSBOSJNDI . . . . . . . . . . . . . . . . . . 8-15TcGSBOSJNDI context parameter . . . . E-9TcGSConnectorJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-11TcGSDORJNDI . . . . . . . . . . . . . . . . . 8-15TcGSEngJNDI context parameter . . . . E-11TcGSEntJNDI context parameter . . . . . E-12TcGSJDBCJNDI . . . . . . . . . . . . . . . . . 8-15TcGSJDBCJNDIl context parameter . . . E-10TcGSMessageServerJNDI . . . . . . . . . . 8-15TcGSMessageServerJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-10TcGSNotifierReactorJNDI . . . . . . . . . . 8-15TcGSNotifierReactorJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-10


Index

TcGSOMfgJNDI context parameter . . . E-12TcGSRACJNDI context parameter . . . . E-11TcGSSAPJNDI context parameter . . . . E-12TcGSSOAJNDI context parameter . . . . E-11TCP_NODELAY environmentvariable . . . . . . . . . . . . . . . . . . . . . . . 5-2TeamcenterInstallation . . . . . . . . . . . . . . . . . . . . 6-1Uninstallation . . . . . . . . . . . . . . . . . 21-1

Teamcenter application server . . . . . . . 2-18Teamcenter Automotive Edition . . . . . . D-4Teamcenter database . . . . . . . . . . . . 3-6–3-7Teamcenter Engineering 2005/2007 . . . . 8-8Teamcenter Engineering Portaldirectory . . . . . . . . . . . . . . . . . . . . . . . 8-7Teamcenter Engineering V9 connector . . 8-7Teamcenter Enterprise connector, requiredfiles . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Teamcenter Environment Manager . . . . 6-1,19-2–19-3Installation log files . . . . . . . . . . . . . B-1Removing features . . . . . . . . . . . . . . 16-2Uninstalling . . . . . . . . . . . . . . . . . . 21-1

Teamcenter Environment Manager (TEM)Install the Business Modeler IDE . . . 10-1

Teamcenter Extensions for MicrosoftOffice . . . . . . . . . . . . . . . . . . . . . . . D-12Teamcenter File ServicesHeterogeneous environments . . . . . . 2-18Local disk installation . . . . . . . . . . . . 5-3Volume server . . . . . . . . . . . . . . . . . D-1

Teamcenter File Services server . . . . . . 2-14Teamcenter for Reporting andAnalytics . . . . . . . . . . . . . . . . . . . . D-12Teamcenter Foundation . . . . . . . . . D-1–D-2Teamcenter Integration for NX/NX IntegrationConfiguration . . . . . . . . . . . . . . D-1, D-6Overview . . . . . . . . . . . . . . . . . . . . . . 5-5

Teamcenter Linking . . . . . . . . . . . . . . 2-16See also Remote workflow

Teamcenter Rich Client (Shared DiskDeployment) . . . . . . . . . . . . . . . . . . . D-2Teamcenter Security Services . . . . . . . . D-3Teamcenter visualization for richclient . . . . . . . . . . . . . . . . . . . . . . . . D-8Teamcenter Web Tier . . . . . . . . . . . . . D-4Teamcenter’s Automotive Edition–GMOverlay . . . . . . . . . . . . . . . . . . . . . . D-5Teamcenter’s Client for MicrosoftOffice . . . . . . . . . . . . . . . . . . . . . . . . D-7Teamcenter’s engineering processmanagement URLs, migrating to Teamcenter8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18Teamcenter’s lifecycle visualization . . . . 19-5

Embedded viewer . . . . . . . . . . . . . . . D-8Installation . . . . . . . . . . . . . . . . . . . 2-14Stand-alone application viewer . . . . . D-8

Teamcenter’s maintenance, repair, andoverhaul . . . . . . . . . . . . . . . . . . . . . . D-9Teamcenter’s manufacturing processmanagement . . . . . . . . . . . . . . . . . . . 12-1Configure Resource Browser and NCPackage Browser . . . . . . . . . . . . . D-9

Manufacturing Resource Libraryinstallation . . . . . . . . . . . . . . . . . 12-1

MTM Data Card . . . . . . . . . . . . . . . D-9TeamcenterConnectorJNDI contextparameter . . . . . . . . . . . . . . . . . . . . . E-11Tecnomatix . . . . . . . . . . . . . . . . . . . . . D-9TemplatesInstalling . . . . . . . . . . . . . . . . . . . . 11-1Updating . . . . . . . . . . . . . . . . . . . . . 11-3

Templates, database . . . . . . . . . . 2-17, 4-17Terminating Teamcenter sessions . . . . . . 7-4Tesselation Manager Service . . . . . . . . D-4Thin clientDescription . . . . . . . . . . . . . . . . . . . . 1-8FCC . . . . . . . . . . . . . . . . . . . . . . . . 2-13Fms_BootStrap_Urls preference . . . . . 6-4Hebrew language . . . . . . . . . . . . . . 17-13Installation . . . . . . . . . . . . . . . . . . . . 2-5Installation overview . . . . . . . . . . . . 2-10Installing patches . . . . . . . . . . . . . . 19-6Language display configuration . . . . . 17-2Localization . . . . . . . . 17-10–17-11, 17-13Localized text . . . . . . . . . . . . . . . . 17-10Migrating legacy URLs . . . . . . . . . . . 8-18Online help . . . . . . . . . . . . . . . . . . . B-2Upgrading legacy URLs . . . . . . . . . . 8-18

Thin client solutions, patching . . . . . . . 19-6TNS_ADMIN environment variable . . . 4-15tnslsnr process . . . . . . . . . . . . . . . 4-8, 4-15tnsnames.ora file . . . . . . . . . . . . . . 4-9, 4-15Tomcat . . . . . . . . . . . . . . . . . . . . . . . . 8-37Translation service . . . . . . . . . . . . . . . D-8Translation Services for Rich Client . . . D-7TreeCache initialization failure . . . . . . B-6TreeCache parameters . . . 8-5, 9-1, 16-7, E-8Troubleshooting . . . . . . . . . . . . . . . . . B-2Four-tier deployment . . . . . . . . . . . . B-5Online help . . . . . . . . . . . . . . . . . . . B-2Oracle . . . . . . . . . . . . . . . . . . . . . . . B-9Server installation . . . . . . . . . . . . . . B-1Server manager . . . . . . . . . . . . . . . . B-6

Trueshape generation from JT . . . . . . . D-7Tutorials . . . . . . . . . . . . . . . . . . . . . . 10-8Two-tier architectureDeployment . . . . . . . . . . . . . . . . . . . 1-10


Index

Installation overview . . . . . . . . . . . . . 2-4Overview . . . . . . . . . . . . . . . . . . . . . . 1-9

UUGS_LICENSE_SERVER environmentvariable . . . . . . . . . . . . . . . . . . . . . . . 5-2Unicode . . . . . . . . . . . . . . . . . . . . . . 17-13UninstallationOracle . . . . . . . . . . . . . . . . . . . . . . . 21-5Teamcenter . . . . . . . . . . . . . . . . . . . 21-1

Unpopulation of IBM DB2 database . . . B-13Unpopulation of Oracle database . . . . . B-13Update a template . . . . . . . . . . . . . . . 11-3UpgradeOracle databases . . . . . . . . . . . . . 4-7, 4-9

URLs, Teamcenter’s engineering processmanagement . . . . . . . . . . . . . . . . . . . 8-18User accounts . . . . . . . . . . . . . . . . 1-5, 2-19Usersdb2das1 . . . . . . . . . . . . . . . . . . . . . . 3-1db2fenc1 . . . . . . . . . . . . . . . . . . . . . . 3-1db2inst1 . . . . . . . . . . . . . . . . . . . . . . 3-1

UTF-8Incorrect data display on Windows . . 17-4Possible data corruption . . . . . . . . . . 17-4

UTF-8 character set . . . . . . . . . . . . . . . 1-5UTF-8 mode . . . . . . . . . . . . . . . . . . . . . 5-4Utilitiesnative2ascii . . . . . . . . . . . . . . . . . . 17-14Teamcenter EnvironmentManager . . . . . . . . . . . . . . . 19-2–19-3

web_gen_xml . . . . . . . . . . . . . . . . . 17-10

VVendor Management . . . . . . . . . . . . . D-12VisualizationEmbedded viewer . . . . . . . . . . . . . . . D-8Stand-alone application viewer . . . . . D-8Volume Server . . . . . . . . . . . . . . . . . . D-1Volumes . . . . . . . . . . . . . . . . . . . . . . . 2-18

WWeb Application Manager . . . . . . . . . . 19-5

Installation . . . . . . . . . . . . . . . . . . . . 8-2Launching . . . . . . . . . . . . . . . . . . . . . 8-2Patching . . . . . . . . . . . . . . . . . . . . . 19-4

Web serversDeploying Web components . . . . . . . . 8-35Deployment . . . . . . . . . . . . . . . . . . . 8-22Supported servers . . . . . . . . . . . . . . 8-35

Web tierconnection problems . . . . . . . . . . B-3, B-6Features . . . . . . . . . . . . . . . . . . . . . D-4Generating application . . . . . 8-3, 8-9, 8-15J2EE . . . . . . . . . . . . . . . . . . . . . . . 1-11Legacy thin client URLs . . . . . . . . . . 8-18Multiple applications . . . . . . . . . . . . 8-21Proxy WAR file (WebLogic) . . . . . 8-6, 8-17Shared application server instance . . 8-21

Web Tier for .NET . . . . . . . . . . . . . . . . D-4Web tier installation problems . . . . . . . B-4Web tier requirements . . . . . . . . . . . . . . 1-1WEB_core_help_server preference . . . 15-4,15-6, B-2WEB_default_site_deployed_app_namepreference . . . . . . . . . . . . . . . . . . . . . B-3web_gen_xml utility . . . . . . . . . . . . . 17-10web_gen_xml.dat file . . . . . . . . . . . . . 17-10WEB_help_server preference . . . . . . . 15-4,15-6, B-2WEB_ROOT directory . . . . . . . . . . . . . . 8-2Web_tier directory . . . . . . . . . . . . . . . . 8-3,8-9, 8-15, 8-23–8-24, 8-32, 8-39Web-tier initialization failure when usingWindows Network Load Balancer . . . . B-6webapp_root directory . . . . . 8-34–8-35, 8-38WebSphere . . . . . . . . . . . . . . . . . . . . . 8-38webstrings.xml file . . . . . . . . . . . . . . 17-10Welcome window . . . . . . . . . . . . . . . . . 10-8WindowsUTF-8 display incorrect . . . . . . . . . . 17-4

Wire Harness Configuration . . . . . . . . D-10Wiring Harness Design ToolsIntegration . . . . . . . . . . . . . . . . . . . D-10Workflow to Scheduling Integration . . D-12


Installation Server Unix

Documents

Transcript of Installation Server Unix