Rapid Start Installation Windows

SIEMENS
Teamcenter 11.2
Teamcenter Rapid
Start Installation for
Windows
PLM00501 • 11.2
Contents
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Teamcenter Rapid Start installation components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Teamcenter Rapid Start installation quick start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Step 1: Install prerequisite software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Step 2: Install the Teamcenter Rapid Start server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Step 3: Install Teamcenter Rapid Start clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Step 4: Install Teamcenter Rapid Start CAD integrations . . . . . . . . . . . . . . . . . . . . . . . 1-13
Step 5: Get started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Installing Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Teamcenter help overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Install the Siemens PLM Documentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Install Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Configuring online help during Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Installing localized online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Teamcenter Rapid Start server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Prepare the Rapid Start server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Locate Teamcenter Rapid Start distribution images . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Perform a Teamcenter Rapid Start server quick installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Perform a Teamcenter Rapid Start server custom installation . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Configure Microsoft IIS on Windows Server 2008/2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Installing XpresReview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Modify a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Installing the Java EE web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Overview of Java EE web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Java EE web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Install rich client web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Planning rich client distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Managing the rich client distribution server and instances . . . . . . . . . . . . . . . . . . . . . . . 3-22
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 3

Contents
Contents
Installing the Java EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Install the Java EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Launch the Teamcenter Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Teamcenter Rapid Start client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Prepare the Rapid Start client host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Perform a Teamcenter Rapid Start client quick installation . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Performing a Teamcenter Rapid Start client custom installation . . . . . . . . . . . . . . . . . . . . . . . 5-3
Install the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Install the four-tier rich client (HTTP-based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Install the two-tier rich client (IIOP-based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Install the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Install Teamcenter Plug-in for Microsoft Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Upgrading to Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Upgrade Teamcenter Express server to Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . 6-1
Upgrade Teamcenter Express client to Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . 6-4
Upgrade Business Modeler IDE template project and code to Teamcenter Rapid Start . . . . . . . 6-6
Moving to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Creating a custom distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Overview of custom distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Create a silent distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Create a compact distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Service log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
TEM reports invalid logon information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Uninstalling Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Teamcenter Rapid Start solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter Rapid Start features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Configure online help access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
4 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Contents
Installing the Full Text Search option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Figures
Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Four-tier deployment (enterprise and web tiers on same host) . . . . . . . . . . . . . . . . . . . 1-4
Four-tier deployment (enterprise and web tiers on separate hosts with HTTP server) . . . 1-5
Four-tier deployment (multiple enterprise tier hosts and web tier hosts) . . . . . . . . . . . . . 1-6
Four-tier deployment (load balancing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Two-tier deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Teamcenter online help on the PLM Documentation Server . . . . . . . . . . . . . . . . . . . . 1-14
Siemens PLM Documentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Sample silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Tables
Rich client optional parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Teamcenter Rapid Start features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 5

Chapter 1: Getting started
Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Teamcenter network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Two-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Teamcenter Rapid Start installation components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Teamcenter Rapid Start installation quick start . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 1-12

Step 1: Install prerequisite software . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 1-12
Step 2: Install the Teamcenter Rapid Start server . . . . .. . . . . . . . . . . . . . . . . . . . . . . 1-12
Step 3: Install Teamcenter Rapid Start clients . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 1-13
Step 4: Install Teamcenter Rapid Start CAD integrations . . . . . . . . . . . . . . . . . . . . . . . 1-13
Step 5: Get started . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 1-13
Installing Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Teamcenter help overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Install the Siemens PLM Documentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Install Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Configuring online help during Teamcenter installation . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Installing localized online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows

Chapter 1: Getting started
Teamcenter clients
Teamcenter Rapid Start provides a rich client and a thin client suited to various uses and network
configurations.
• Rich client
The rich client is a platform-independent client implementation (Java application) for users who
interact with Teamcenter frequently. It is extendable to run standard Teamcenter and customized
applications.
The rich client application is deployed on each user workstation using Teamcenter Environment
Manager. The rich client is supported in both the two-tier architecture and four-tier architecture.
• Thin client
The thin client provides access to Teamcenter through a standard commercial web browser, such
as Microsoft Internet Explorer or Mozilla Firefox. The user interface provides a streamlined
browser-based view of product information stored in a Teamcenter database.
The thin client is supported only in the four-tier architecture.
Teamcenter network architectures
Four-tier architecture
The four-tier architecture model comprises the following tiers:
• Client tier
The client tier comprises the Teamcenter rich client, thin client, and other clients such as
Teamcenter Client for Microsoft Office.
Note
The rich client can be deployed with additional functionality, such as Lifecycle Visualization,
Teamcenter Client for Microsoft Office, and Teamcenter Integration for NX or NX
Integration 4.0.1. (Teamcenter Integration for NX/NX Integration 3 is not supported.)
• Enterprise tier
The enterprise tier comprises a configurable pool of Teamcenter C++ server processes and a
server manager. The enterprise tier retrieves data from and stores data in the database.
A server manager manages a pool of Teamcenter server processes. You must install a server
manager whenever you deploy the web tier.
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 1-1

Chapter
Chapter 1: 1: Getting
Getting started
started
Note
Teamcenter provides server managers based on Microsoft .NET platforms. Install the
appropriate server manager for the web tier you use.
• Resource tier
The resource tier comprises a database server, database, volumes, and file servers.
Four-tier architecture
You can design deployments that host the web tier, resource tier, and enterprise tiers on the same
computer or on separate computers:
• Smaller sites can run the pool of servers and the server manager on the same host as the web tier.
1-2 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Getting started
• Larger sites can distribute the pool of server processes across multiple hosts and optionally
include an HTTP server to serve static files or multiple HTTP servers to support load balancing.
For a multihost configuration, the server pool consists of multiple subpools, one or more for
each host. Each subpool is managed by one server manager process. The web tier balances
the load across the server pools.
To ensure communication between the web tier and the server manager, you must coordinate the
values you specify for each component. For some values, you must provide the identical value when
configuring the web tier application.
If you are setting up multiple web tier environments with separate domains, you must configure:
• A minimum of one server manager for each web tier deployment.
• A separate TreeCache cluster for each environment.

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

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

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

Chapter
Getting started
started
Four-tier deployment (multiple enterprise tier hosts and web tier hosts)

Getting started
Four-tier deployment (load balancing)

Chapter
Getting started
started
Two-tier architecture
The two-tier architectural model comprises the following tiers:
• Client tier
The client tier comprises the Teamcenter rich clients.

In a deployment of the two-tier architecture, the Teamcenter server runs on the client workstation.
Note
The two-tier rich client is installed only through TEM.

Some Teamcenter client features, such as Teamcenter Integration for NX, Lifecycle
Visualization, and Teamcenter Client for Microsoft Office, require the web tier, a component
of the four-tier architecture. To enable these features for a two-tier rich client, you can
connect the two-tier rich client to a deployment of the web tier.
• Resource tier
The resource tier comprises a database server, database, volumes, and file servers.
Two-tier architecture
In the two-tier model, you deploy the Teamcenter rich client, which includes the local server, and
the optional applications that integrate with the rich client on the client workstation. Typically, the
database server, volumes, and file servers are installed on one or more separate hosts.
Teamcenter File Management System (FMS) manages the rich client access to volumes:
• The FMS server cache (FSC) process run on the server hosting the volume.
• The FMS client cache (FCC) process runs on the rich client host.

Getting started
Two-tier deployment
Teamcenter Rapid Start installation components

The following example shows a simple Teamcenter Rapid Start deployment in which all components
are distributed across two computers: a user workstation and an application/database server. The
database server and the Teamcenter Rapid Start server components can be installed on a single
machine; however, installing these components on separate machines improves performance and
increases scalability.

Chapter
Getting started
started
The following table describes the Teamcenter Rapid Start server installation components.
Server component Description

Teamcenter server The server manages CAD models, Microsoft Office
documents, bill of materials (BOM) structures, and other
files and objects in a Teamcenter Rapid Start installation.
The server controls access to the files and metadata of
objects managed by Teamcenter Rapid Start.
The Teamcenter server supports multiple client
applications, including CAD applications, a rich client
application, and a thin client running as an application on
Microsoft Internet Information Server (IIS).
Teamcenter configuration files The configuration files supply configuration settings and
site and user preference files that control the behavior of
the Teamcenter Rapid Start server and client components.
These files are installed in the TC_ROOT\TCDATA
directory by default.
The Teamcenter Rapid Start server installation optionally
configures the TCDATA directory as a network-shared
drive, allowing all client workstations at a site to share one
set of configuration information.

Getting started
Server component Description

Teamcenter files The Teamcenter files include data files, including but
not limited to CAD files, Microsoft Office documents,
visualization files, and images. The files are stored in an
encrypted format in protected directories for security.
These directories are known as volumes within Teamcenter
Rapid Start and are managed and configured using the
Teamcenter Rapid Start client.
Teamcenter database The Teamcenter Rapid Start database is a single database
instance that contains metadata describing the items,
users, files, and other objects in the Teamcenter Rapid
Start environment.
The following table describes the Teamcenter Rapid Start client installation components.
Client component Description

Teamcenter client Teamcenter Rapid Start supports the rich client in two-tier
and four-tier deployments. The rich client can access
and manage files and objects, such as items and bill of
materials structures stored in a Teamcenter Rapid Start
database.
Teamcenter thin client The thin client interface provides a streamlined
browser-based view of product information stored in a
Teamcenter Rapid Start database using Microsoft Internet
Explorer.
If you use the thin client, the Teamcenter Rapid Start
Server must be running the IIS web server and the
Teamcenter thin client must be installed during the
Teamcenter Rapid Start server installation.
CAD applications One of multiple CAD applications that can integrate with
and manage data in a Teamcenter Rapid Start instance.
Note
The CAD applications must be installed prior to

installing the Teamcenter Rapid Start client on a
workstation.
CAD managers The CAD manager component is the software interface
that integrates a CAD application with a Teamcenter Rapid
Start Server instance. It provides the glue that enables the
CAD software to manage and manipulate files and objects
in Teamcenter Rapid Start.

Chapter
Getting started
started
Teamcenter Rapid Start installation quick start

Step 1: Install prerequisite software
Install the following software on the Teamcenter Rapid Start server host:
• Microsoft Windows Server 2008 or 2012 operating system
Teamcenter Rapid Start supports only 64-bit operating systems.
• A supported database server
• A supported version of the Java runtime environment (JRE)
• A supported Java EE web application server (if you use the Java EE web tier)
• Microsoft Internet Information Services (IIS) (if you use the .NET web tier)1
For information about supported versions of operating systems, databases, and web application
servers, see the hardware and software certifications page on GTAC.
Step 2: Install the Teamcenter Rapid Start server

Once the database server is installed, you can install the Teamcenter Rapid Start server using
Teamcenter Environment Manager (TEM). Launch TEM by running the tem.bat programtem.sh script
located on the Teamcenter Rapid Start software distribution image. Using TEM, you can perform
either a quick or custom Teamcenter Rapid Start server installation.
Quick installation
The quick installation option installs the most commonly used components and is an efficient way to
get Teamcenter Rapid Start up and running. If you want to install custom options after performing the
quick installation, you can run the installation program again to add the options.
The quick server installation performs the following tasks:
• Installs the following templates: Teamcenter Foundation and Dispatcher (Translation Services).
• Installs a license server.
• Installs an administration client for system administration tasks.
• Installs a thin client for accessing Teamcenter Rapid Start through a web browser (Internet
Explorer), if Internet Information Server (IIS) is installed.
• Connects to the database server and configures a new database or connects to an existing
database, if applicable.
• Creates a default volume (directory to store and manage data files) and a Windows Service
to manage volume access.
1. You need not install IIS if you do not use the thin client.

Getting started
• Creates a network share to the configuration directory (accessible as \\SERVERNAME\tc_data)

where client workstations can access configuration information.
• Configures Dispatcher.
• Installs Business Modeler IDE for two-tier environments.
• Installs Teamcenter lifecycle visualization for two-tier environments.
Custom installation
The custom server installation allows you to select individual options for your installation.
Step 3: Install Teamcenter Rapid Start clients

Once the Teamcenter Rapid Start Server is installed, you can configure client workstations to
access the server. Install the Teamcenter Rapid Start client software using Teamcenter Environment
Manager (TEM), which allows you to choose either a quick or custom version of the client installation.
CAD applications
If you use NX, you must install it on individual workstations prior to installing the Teamcenter Rapid
Start client. The client installation detects NX and installs the appropriate CAD manager components.
If you plan to use supported integrations other than NX, they are available as separate installation
packages and are not included in the Teamcenter Rapid Start client installation.
Quick installation
The quick client installation option installs the most commonly used client components and performs
the following tasks:
• Installs the Teamcenter Rapid Start rich client application.
• Installs the embedded Teamcenter Visualization component.
Custom installation
The custom client installation allows you to select individual options in addition to the typical
installation.
Step 4: Install Teamcenter Rapid Start CAD integrations

If you use Teamcenter Rapid Start CAD integrations for Inventor or SolidWorks, install and configure
those integrations.
Step 5: Get started

Once the Teamcenter Rapid Start environment is installed, you are ready to start using Teamcenter
Rapid Start. Getting Started with Teamcenter Rapid Start describes how to add users, load data into
the Teamcenter Rapid Start database, and begin managing your data.

Chapter
Getting started
started
Installing Teamcenter help
Teamcenter help overview

Siemens PLM Software provides two sources of online help for Teamcenter:
• GTAC Documentation site
GTAC site that hosts online help for Teamcenter and other Siemens PLM Software products. A
WebKey account is required to access this site.
Teamcenter online help is available on the GTAC Documentation site at:
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/
• Siemens PLM Documentation Server

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

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

Getting started
and you can add localized Teamcenter help and also help for other Siemens PLM Software products
you use.
Siemens PLM Documentation Server

Installing Teamcenter help on your local network requires two steps:
1. Installing the PLM Documentation Server.
2. Installing Teamcenter documentation.
After you install Teamcenter documentation, you can configure online help access for Teamcenter
clients during Teamcenter installation or after installation. Teamcenter clients can then access help on
the PLM Documentation Server through the client Help menus.

Chapter
Getting started
started
Rich client help menu Thin client help menu
Note
• The Teamcenter PDF help collection and the Teamcenter developer references are not
accessible though Teamcenter client Help menus.
• Teamcenter documentation cannot be accessed through a drive letter or UNC path

(\\host-name). It is viewed only in a web browser using HTTP or HTTPS protocol.
If you use Teamcenter documentation in multiple languages, you can install all languages on the
same PLM Documentation Server. The PLM Documentation Server displays the appropriate
language according to each user's web browser language settings.
Before you install Teamcenter help, make sure your host meets PLM Documentation Server
requirements.
Additional Teamcenter documentation
The following documentation deliverables are provided by Teamcenter but are not installed in the
PLM Documentation Server:
• Teamcenter Client for Microsoft Office
The Teamcenter Client for Microsoft Office contains its own online help, which is displayed in
Microsoft Office.
• Business Modeler IDE online help

The Business Modeler IDE client contains its own online help, which is displayed in the Business
Modeler IDE.
• Teamcenter Data Model Report

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

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

Getting started
2. Select a language for the installation user interface, and then click OK.
The wizard displays the welcome dialog box.
3. Proceed to the Destination Folder dialog box. Accept the default destination folder (C:\Program
Files\Siemens\PLM Documentation Server\), or click Change to enter a different folder.
4. Proceed to the Ready to Install the Program dialog box. Accept the default port for the PLM
Documentation Server (8181), or click Change Port to specify a different port.
5. Click Install to begin installing the PLM Documentation Server.
6. In the InstallShield Wizard Completed dialog box, click Finish to exit the wizard.
Note
For additional information about installing the PLM Documentation Server, including advanced
installation options, see the splmdocserver_install.pdf document in the wntx64 (Windows
systems) or unix (UNIX/Linux systems) directory under the splmdocserver directory in the
documentation distribution image.
Stopping and starting the Siemens PLM Documentation Server
The PLM Documentation Server starts automatically when installation is complete and whenever
you restart Windows. If necessary, you can stop or start the Siemens PLM Documentation Server
service in the Services dialog box in the Windows Control Panel.

Chapter
Getting started
started
Install Teamcenter online help

Teamcenter provides three online help collections, installable as features in the Teamcenter
documentation installer:
• Teamcenter online help
Provides the Teamcenter help library. This collection can be accessed from Teamcenter client
Help menus.
• Teamcenter developer references

Contains developer references for Teamcenter customization:
o C++ API Reference

o Integration Toolkit (ITK) Function Reference
o Services Reference
• Teamcenter PDF online help

Provides the Teamcenter help library in PDF format.
Note
You must install the Siemens PLM Documentation Server before you install online help.
1. In the Teamcenter documentation distribution image, launch the Teamcenter documentation

installation wizard:
Windows systems:
Double-click the tchelp.exe program icon.
UNIX/Linux systems:
Launch the tchelp.bin program.
2. Select a language for the installation user interface, and then click OK.
The wizard displays the Introduction dialog box.

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

• Typical installs the Teamcenter online help library.
• Custom installs the Teamcenter online help library and allows you to add the following
help features:
o Teamcenter PDF help collection
o Teamcenter developer references.2
Note
You can also add help features later using the maintenance options provided by the
Teamcenter documentation installer.
2. Developer references include the C++ API Reference, the Integration Toolkit (ITK) Function Reference, and the Services Reference.

Chapter
Getting started
started
4. If you chose the Custom option, select the additional features you want to install.
5. Proceed to the Pre-Installation Summary dialog box. If you are satisfied with your selections,
click Install to begin installing Teamcenter documentation.
The Teamcenter documentation installer installs Teamcenter help into the PLM Documentation
Server and updates the online help search database.
6. When installation is complete, the Teamcenter documentation installer displays the Online
Help Locations dialog box.
Record the Teamcenter Online Help URL. You use this URL to configure online help access for
Teamcenter clients.
If you install additional help features, bookmark the URLs for those help collections and provide
them to users in your Teamcenter network.
Online help URLs are based on the host and port of the PLM Documentation Server and the
Teamcenter version or SP level.
Help feature URL Example

Teamcenter online help http://host:port/tdoc/tc/version/help/ http://myhost:8181/tdoc/tc/11.2/help/
Teamcenter developer references http://host:port/tdoc/tc/version/tcrefs/ http://myhost:8181/tdoc/tc/11.2/tcrefs/
Teamcenter PDF online help http://host:port/tdoc/tc/version/PDF/ http://myhost:8181/tdoc/tc/11.2/PDF/
Note
Help URLs are valid only for help features that are installed.

Getting started
7. Click Next to proceed to the Install Complete dialog box. Then, click Done to exit the installer.
Adding online help features
You can add help features after installation by launching the Teamcenter documentation installer in
maintenance mode.
1. In the Add or Remove Programs dialog box in the Windows Control Panel, right-click Siemens
Teamcenter version Documentation and choose Uninstall/Change.
2. Select the Add Features or Remove Features option in the Teamcenter documentation installer.
Configuring online help during Teamcenter installation

During Teamcenter installation, enter the online help URL to enable Help menu options in Teamcenter
clients.
• Teamcenter Foundation
Teamcenter Foundation settings supply the online help URL to the thin client and to four-tier
rich clients installed through TEM.
TEM displays the Foundation Settings panel during installation of Teamcenter Foundation.
In the Foundation Settings panel:
1. Click the Advanced button .
2. Click the Online Help tab.
3. Select the Enable Online Help check box.
4. In the PLM Document Server URL box, type the Teamcenter online help URL.
• Two-tier rich client

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

Chapter
Getting started
started
• Rich client distribution instance

For rich clients installed using the Over-the-Web Installer, the online help URL is supplied by
context parameters in the rich client distribution instance.
When you create the rich client distribution instance, type values for the following context
parameters.
Context parameter Value

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

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

Getting started
Note
You must install the Siemens PLM Documentation Server before you install online help. The
Siemens PLM Documentation Server installer is provided only in the English documentation
distribution image. It is not provided in localized documentation distribution images.
The Teamcenter online help library and the Teamcenter PDF help collection are localized for
all supported locales. The Teamcenter developer references are available in English only.
Viewing localized online help
The PLM Documentation Server displays localized Teamcenter help according to the language
settings in your web browser.
When you open a Teamcenter help collection, the PLM Documentation Server detects your web
browser's language settings. For example, if your browser is configured to display in German, the
PLM Documentation Server determines whether the German version of the current collection is
installed, and if so, it displays the German version of the content. If the German version is not
installed, the PLM Documentation Server displays the default (English) help collection.
If you have multiple languages configured in your web browser, the PLM Documentation Server
chooses the first available help collection it finds from the list of preferred languages in the web
browser settings.
For information about configuring language settings in your web browser, see your web browser
documentation.

Chapter 2: Teamcenter Rapid Start server installation
Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Prepare the Rapid Start server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Locate Teamcenter Rapid Start distribution images . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Perform a Teamcenter Rapid Start server quick installation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Perform a Teamcenter Rapid Start server custom installation . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Configure Microsoft IIS on Windows Server 2008/2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Installing XpresReview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Modify a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Chapter 2: Teamcenter Rapid Start server installation
Preinstallation tasks
Prepare the Rapid Start server host

• Install the prerequisite software on the Teamcenter Rapid Start server host. This includes:
o Operating system
o Database server
o Java runtime environment (JRE)
o Web server
• On the local host, create an operating system account with administrative privileges for installing
Teamcenter Rapid Start.
This user should be a member of the Administrators group.
• Obtain the Teamcenter Rapid Start license file, copy it onto the corporate server host, and
configure the file with the name of the corporate server host.
Record the location of the license file for use during corporate server installation.
• Make sure you have the following information from the database administrator:
o Name of the host on which the database server runs.
o Port number on which the database server listens.
o If you must use an existing database user, obtain the database user name and password.
• Make sure the server host is connected to the network during Rapid Start installation. During the
installation, TEM creates a default volume in the given share directory, and the share directory is
accessed using a UNC path.
• Set the JRE64_HOME environment variable to the location of a supported 64-bit Java JRE. After
installation is complete, TEM no longer requires this variable.
TEM verifies the JRE version during launch and cancels installation if a certified JRE is not
available on the host.

Chapter
Chapter 2: 2: Teamcenter
Teamcenter
RapidRapid
Start Start
serverserver installation
installation
Note
Alternatively, you can specify the Java JRE location by one of the following methods:
o Set the JRE_HOME environment variable to the location of a supported 64-bit Java
JRE.
o When you launch TEM type the following command in a command prompt using the
-jre argument to specify the location of a supported 64-bit Java JRE:
tem -jre JRE-path
For example:
tem -jre c:\apps\jre1.7
Locate Teamcenter Rapid Start distribution images

Locate the Teamcenter Rapid Start software and documentation distribution images and make
sure they are accessible to your host.
From the download page on GTAC, download the Teamcenter software distribution files for Windows:
Tcversion_win64_1_of_2.zip
Tcversion_win64_2_of_2.zip
Expand both ZIP files for your platform to a common directory to assemble the full software
distribution before you begin installation.
In addition, download the rich client over-the-web distribution image (Tcversion_otw.zip) from the
GTAC download page.
Note
• Use a commercial unzip utility such as 7-Zip to expand files.
• Contents of Teamcenter distribution images are described in the server installation guides
for Windows and UNIX/Linux.
Perform a Teamcenter Rapid Start server quick installation

Note
When performing an English installation of Teamcenter Rapid Start, all existing databases
must have Latin1 collation.
1. Log on to the workstation with the operating system user account you created for installing
2. Start Teamcenter Environment Manager (TEM) to begin installing Teamcenter Rapid Start:
a. Browse to the root directory of the Teamcenter installation media.
b. Double-click the tem.bat program icon.

Teamcenter Rapid Start server installation
TEM starts and displays the Installer Language dialog box.

Warning
Do not use the Windows Run as option to run the Teamcenter Rapid Start setup
program as a user with administrator privileges. To successfully install and configure
Teamcenter Rapid Start, you must log on as a user with administrator privileges.
c. In the Installer Language dialog box, select a language and click OK.
Your language selection applies only to the TEM session, not the Teamcenter installation.
3. In the Welcome to Teamcenter panel, select Teamcenter Rapid Start .
4. In the Install/Upgrade Options panel, click Quick Preconfigured Install.
5. In the Product Selection panel, select Teamcenter Corporate Server and Teamcenter Rich
Client 2-Tier.
If you want to add Teamcenter Rapid Start features not automatically included in the quick
preconfigured installation, select the Include additional features check box. If you select
additional features, TEM may display additional panels not described in this procedure.
6. In the Teamcenter Corporate Server and Teamcenter Rich Client 2-Tier panel, enter the
following values:
a. Type the OS User Password for the operating system user account you created for installing
b. Select Database Type according to your database vendor (Oracle, Microsoft SQL Server, or
IBM DB2).
c. Enter database access credentials and configuration values for the Teamcenter Rapid Start
database. For more information about these values, click the help button .
d. In the Character Encoding Type box, make sure the selected character set is correct for
your database server. Teamcenter clients use this character set to access the database.
Caution
To prevent data corruption, this character encoding set must match the encoding
set used by the Teamcenter database.
e. Enter the Installation Directory where you want to install Teamcenter Rapid Start.
The Installation Directory must not already exist on your system. TEM creates the directory
during installation.
The directory must also be in a location excluded from real-time virus scanning.
7. In the Select Translators panel, select the Dispatcher Server translators you want to install.
8. If you selected additional features, proceed through any remaining panels, entering the required
information for the features you selected.

Chapter
Teamcenter
RapidRapid
Start Start
installation
For information about these panels, click the help button .
9. Proceed to the Confirmation panel. Verify the information you entered.

If you want to change any values, click Back to return to the panels you want to change.
Otherwise, click Start to begin installing the Teamcenter corporate server.
Note
If an error occurs during installation, follow the instructions in the error message displayed
by TEM or see the available troubleshooting solutions.
10. When installation is complete, close TEM.
Related topics
• Non-English locale environment settings
Perform a Teamcenter Rapid Start server custom installation

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

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

Note
For information about any TEM panel, click the help button .
3. In the Welcome to Teamcenter, select Teamcenter Rapid Start.
4. Proceed to the Install/Upgrade Options panel. This panel contains the following options:
• Install
Installs a new Teamcenter configuration using a fully configurable installation process.
• Quick Preconfigured Install

Installs preconfigured corporate server and client configurations using a simplified installation
process.
• Upgrade

Upgrades an existing Teamcenter configuration.
Click Install to begin installing a corporate server.

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

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

To simplify installations of Teamcenter on multiple hosts, TEM can create a silent
distribution or a compact distribution. Compact distribution is recommended only for
Teamcenter client configurations, not for servers.
5. In the Media Locations panel, enter paths to any Teamcenter patches or service packs you want
to apply during installation. This step is optional.
6. In the Configuration panel, type a unique ID and description for the new Teamcenter Rapid
Start configuration.
The configuration ID identifies your Teamcenter Rapid Start configuration when you maintain,
upgrade, uninstall, or add features to the configuration. Installation log files are also named
based on the ID you enter.
7. In the Solutions panel, select the Corporate Server solution.
8. Proceed to the Features panel. This panel shows the corporate server features preselected
by the Corporate Server solution:
FMS Server Cache
NX Part Family Classification Integration
9. Select the Flex License Server (under Server Enhancements) and any other additional
features you want to install.
If you select additional features, TEM displays additional panels during installation that are not
described in this procedure.
For help with any panel in TEM, click the help button .
You can also add features to the corporate server later using TEM in maintenance mode.
10. In the Installation Directory box, enter the path to a new directory where you want to install
Teamcenter.
The Installation Directory value is the Teamcenter application root directory (TC_ROOT).
Do not set the TC_ROOT environment variable in the system environment. TEM sets this
variable as required in Teamcenter configuration files. Setting this variable in the operating
system can cause conflicts if you install multiple Teamcenter configurations.

Chapter
Teamcenter
RapidRapid
Start Start
installation
The installation directory must meet the following requirements:
• The directory must not already exist on your system. (TEM creates the directory during
installation.)
• The path to the installation directory must not exceed 64 characters.
• The directory must be in a location excluded from real-time virus scanning.1
11. In the Flex License Server panel, enter a path for the licensing server in the Install UGS
Licensing to box.
In the Use License File box, enter the path to your Teamcenter license file.
Make sure the License Server Installer Location box contains the path to the installer for
the licensing server.
Note
This panel appears only if you include the Flex License Server feature in your
configuration.
12. In the File System Cache (FSC) panel, type a unique identifier and port for the FMS server
cache in the FSC ID and Port boxes.
A Teamcenter network must have at least one master FSC. If you want to designate the current
FSC as an FSC master, select the Enable configuration master check box. Otherwise, type the
URL to the parent FSC in the FSC Parent URL box.
For advanced FSC configuration options, click Advanced.
13. In the Operating System User panel, type the password for the operating system account
under which you install Teamcenter Rapid Start.
14. In the Foundation panel, select how you want to create or designate the Rapid Start database
and Rapid Start data directory (TC_DATA).
Database Database TC_DATA

exists? populated? exists? Select this option
No N/A No Create and populate database, create new
data directory
No Rapid Start database or data directory exists
and you want TEM to create both. This option
is selected by default.
1. Real-time virus scanning prevents Teamcenter from updating the persistent object manager (POM) schema during installation, causing
installation errors.

Database Database TC_DATA

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

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

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

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

Chapter
Teamcenter
RapidRapid
Start Start
installation
Note
For more information about database configuration values, click the help button .
For Oracle and Microsoft SQL Server databases, the directory you specify in the Database
Path box must exist and you must have write permission to the directory.
16. In the Data Directory box, enter a location for the Rapid Start data directory.
The Rapid Start data directory is called the TC_DATA directory. TEM stores this location as the
TC_DATA variable in Teamcenter configuration files. TEM creates shared data subdirectories
and files in this location. Each data directory is associated with a single database user within
a database instance.
Do not set TC_DATA as a system environment variable. Setting this variable in the operating
system can cause conflicts if you install more than one configuration.
17. In the Share Name box, type a name for the Rapid Start share directory, or accept the default
value. TEM creates a default volume in the given share directory.
18. Proceed to the Volume Information panel.

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

for example, \\server\shared-transient-folder .
You must use a direct path location.

Value Description
This is partly due to the fact that some ZIP

archive utilities do not accept UNC paths,
resulting in failure of exports to Excel or
Word.
Windows clients Specifies the location for a transient volume for
Windows client hosts.
UNIX clients Specifies the location for a transient volume for
Linux client hosts.
Generate server cache Specifies you want to generate a shared server
cache. If you select this option, TEM runs the
generate_client_meta_cache utility at the end
of the install, upgrade, or update action. This
option reduces Rapid Start memory consumption
by moving metadata to shared memory. Types,
property descriptors, and constants are placed in
a shared cache that is shared by all Teamcenter
server instances.
This option is selected by default in a Rapid Start
server installation.
Generate client cache Specifies you want to generate a cache of data that
rich clients can download once at initial logon and
then reuse on the client host. This option reduces
server demand, reduces startup time, and improves
overall performance. When this option is selected,
TEM runs the generate_client_meta_cache utility
at the end of the install, upgrade, or update action.
If you clear this option, but a client cache already
exists, the old client cache is deleted.
This option is selected by default in a Teamcenter
server installation.
Production Environment Specifies your new environment is to be used as a
live environment where you will store your product
data.
Test Environment Specifies your new environment is to be used
for development, testing, or training. Selecting
Test Environment enables the bulk loader tool to
copy data from another environment (such as a
production environment) into this test environment.
Note
If you designate this environment as a test

environment, the designation cannot be
changed.

Chapter
Teamcenter
RapidRapid
Start Start
installation
For advanced Teamcenter Foundation options, click Advanced.
20. If you want to configure Teamcenter online help, click Advanced in the Foundation Settings
panel and perform the following steps:
a. Click the Online Help tab.
b. Select the Enable Online Help check box.
c. In the PLM Document Server URL box, type the Teamcenter online help URL.
21. Proceed to the Flex License Client panel. Enter settings for the Teamcenter Rapid Start
license server.
22. Proceed to the Password Security panel. In the Administrative Password Directory box,
enter the directory in which to place Rapid Start password files. TEM locks access to this
directory to all users except the user performing Teamcenter installation.
23. Proceed through any remaining panels, entering the required information for the features you
selected.
Otherwise, click Start to begin installing the Rapid Start corporate server.
Note
by TEM or see the available Troubleshooting.
Configure Microsoft IIS on Windows Server 2008/2012

If you use Microsoft Internet Information Services (IIS) on a Windows Server 2008/2012 host, make
sure the host is configured correctly for the Teamcenter .NET web tier by performing the following
steps:
1. Start the Windows Server 2008/2012 server manager (Start→Administrative Tools→Server
Manager).
2. In the Server Manager, expand the Server Manager (host) node.
3. Expand the Roles tree and select Web Server (IIS).
4. In the Roles pane, under Web Server (IIS), locate the Role Services table.
5. In the Role Services table, verify that all of the following required role services are installed on
your host:

Web Server
Common HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection
Application Development
ASP.NET version
.NET Extensibility
ASP
CGI
ISAPI Extensions
ISAPI Filters
Server Side Includes
Health and Diagnostics

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

Chapter
Teamcenter
RapidRapid
Start Start
installation
Caution
Make sure the WebDav Publishing role is not installed.
Installing XpresReview
If you use XpresReview with Teamcenter Rapid Start, install XpresReview on your host:
1. Browse to the additional_applications\tcrs\XpresReview directory in the Teamcenter software
distribution image.
2. Launch the XpresReview.exe installation program.
The XpresReview installer installs XpresReview and associates .pcf files with the XpresReview
application.
XpresReview is an electronic design review solution that allows you to share documents in a
collaborative environment. Using XpresReview, you can create and export a review package as a
.pcf or .zip file.
Note
In Teamcenter Rapid Start 10.1 and earlier versions, XpresReview was available as an
installable feature in TEM. If you used XpresReview with an earlier version than Teamcenter
Rapid Start 11.2, the XpresReview review package functionality remains after upgrade.
Modify a configuration
Add Teamcenter Rapid Start features to an existing configuration, or remove them from a
configuration:
1. Launch Teamcenter Environment Manager. In the Windows start menu, click
Programs→Teamcenter 11.2, and then right-click Environment Manager and choose Run as
administrator.
Note
You can also run the tem.bat file in the install directory in the application root directory
for the Teamcenter installation. Right-click the tem.bat program icon and select Run
as administrator.
2. In the Maintenance panel, choose Configuration Manager.
3. In the Configuration Maintenance panel, choose Perform maintenance on an existing

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

Note
Options in the Feature Maintenance panel vary depending on the features in your
configuration.
6. In the Features panel, select features to add to the configuration, or deselect features you
want to remove.
Note
If you remove a feature that added data model objects to the Teamcenter database, the
data model is not removed when you remove the feature. Relations and objects created
using the removed feature persist in the database.
If no instances of the feature's data model objects were created in the database, you can
attempt to remove the template. For more information, see How to remove a template in
the latest version of the Business Modeler IDE Best Practices Guide at the Teamcenter
documentation site on GTAC.
7. Proceed through the remaining panels in TEM, entering the required information for the features
you selected.
For information about each panel, click the help button .
8. When TEM displays the Confirmation panel, click Start to begin installation.

Chapter 3: Installing the Java EE web tier
Overview of Java EE web tier installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Java EE web tier prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Install the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Install rich client web applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Planning rich client distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Install the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Install rich client distribution instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Rich client distribution instance requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Install a rich client distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Configuring TCCS, Security Services, and proxy settings . . . . . . . . . . . . . . . . . . . . 3-15
Configure TCCS for the rich client distribution instance . . . . . . . . . . . . . . . . . . . 3-15
Configure Security Services for the rich client distribution instance . . . . . . . . . . . 3-17
Configure reverse proxy settings for the rich client distribution instance . . . . . . . . 3-18
Deploying the distribution instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Deploy the distribution server instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Publish information for users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Start and stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Start the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Stop the rich client distribution server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Managing the rich client distribution server and instances . . . . . . . . . . . . . . . . . . . . . . . 3-22
Change the distribution server contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Add components to the distribution server instance . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Run the distribution server as a service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Chapter 3: Installing the Java EE web tier
Overview of Java EE web tier installation

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

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

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

The Web Application Manager generates a web archive (WAR) file.
7. Deploy the web application on a supported Java EE application server.

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

Before you install the Java EE web tier, make sure you complete the following tasks:
• Install the Teamcenter Rapid Start server and server manager using Teamcenter Environment
Manager.
• Install a supported third-party Java EE application server and the Java Runtime Environment
(JRE) on the web tier host.1
• If you use Security Services with the rich client or thin client, install Security Services.
Install the Web Application Manager

1. Create a home directory for the Teamcenter web tier, for example, c:\tcweb. This directory is
referenced as WEB_ROOT.
2. In the Teamcenter software distribution image, browse to the Web_tier directory and double-click
the INSTALL_TCWEB.EXE program icon.
7-Zip displays a self-extractor dialog box.
3. In the Unzip To Folder box, type the path to WEB_ROOT, and then click Unzip.
After 7-Zip extracts the installation files, click Close to close the WinZip self-extractor dialog box.
1. For information about supported application servers and Java versions, see the hardware and software certifications page on GTAC.

Installing the Java EE web tier
4. To launch the Web Application Manager, browse to the WEB_ROOT directory and double-click
the insweb.bat program icon.
Install rich client web applications
Planning rich client distribution

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

The web components include the Over-the-Web Installer and the HTML pages that launch the
Over-the-Web Installer.
4. Start the distribution server.

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

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

Chapter
Installing the Java
the Java EE tier
EE web web tier
a. Browse to the WEB_ROOT directory.

This is the directory in which you installed the Web Application Manager on your hard drive.
b. Double-click the insweb.bat file.

The Web Application Manager displays the Teamcenter Web Application Manager dialog
box.
3. Copy web tier solution ICDs:

a. Click Copy ICDs.
b. In the Copy ICD Files dialog box, click Browse.
c. Browse to the tcrs_icd directory of the Teamcenter 11.2 over-the-web software distribution.
Select the tcrs_icd directory, and then click Open.
In the Copy ICD Files, click OK to load ICD files.
Note
The Web Application Manager displays a Progress dialog box while it copies ICD files.
When ICD files are copied, a list of ICD files follows the Copying ICD files... notice. If
no files are listed, Web Application Manager did not find files to copy in the directory you
entered.
If the ICD files are not copied successfully, repeat these steps ensuring that you include
the tcrs_icd directory in the path. Not including the tcrs_icd directory is the most common
reason ICD files are not copied.
4. In the Teamcenter Web Application Manager dialog box, click Add.

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

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

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

The Web Application Manager displays the Modify Required Context Parameters dialog box.
12. Type values for the following context parameters:
Parameter Value
RMI Port Specifies the port number used by the rich client distribution server,
a remote method invocation (RMI) registry server.
The default value, 12099, is in a range that is typically available.
Note
Record the RMI port number for future use. It is required

when creating the distribution server instance.
Remote Object Port Specifies the port on which the distribution server listens for
over-the-web installers. The default value, 0, allows the distribution
server to pick an available port at run time. If you want to use
a specific port, enter a nonzero port number. This is helpful if,
for example, a firewall exists between distribution server and
over-the-web installation clients.
File Transfer Port Specifies the port the distribution server uses to transfer files to client
hosts. The default value, 0, allows the distribution server to pick an
available port at runtime. If you want to use a specific port, enter a
nonzero port number. This is helpful if, for example, a firewall exists
between the distribution server and over-the-web installation clients.
13. Click OK.

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

Chapter
Installing the Java
the Java EE tier
EE web web tier
15. Either click Exit to exit the Web Application Manager or click Add to begin installing the rich
client distribution server instance.
Install rich client distribution instances
Rich client distribution instance requirements
For each unique rich client configuration, you must create a distribution server instance.
Before you build a rich client distribution instance, ensure that the following software is installed
and configured:
• Teamcenter Rapid Start server
• Rich client distribution server
If you use Security Services with the rich client, make sure Security Services is installed and
configured.
Make sure the Web Application Manager has access to the following software images:
• Complete rich client over-the-web software distribution image
Note
The rich client over-the-web software distribution image includes files for all supported
Windows, UNIX, and Linux platforms. The Web Application Manager requires access to all
of these to build the Over-the-Web Installer.
• Teamcenter lifecycle visualization software distribution image

Note
If you include Lifecycle Visualization in your rich client distribution instance, and you use
downloaded software images instead of a DVD:
1. Download the version_Vis_ALL.zip file.
Replace version with the current Teamcenter version level.
2. Expand the version_Vis_ALL.zip archive to a directory on your local host.
3. When building your rich client distribution instance, enter the location of this directory
in the context parameter in the Web Application Manager.
Obtain values for the required rich client parameters. You must provide these values when building
the rich client distribution instance.

Note
• Required parameters must have values specified. If a required parameter has no

significance for your deployment (for example, a UNIX location in an environment of all
Windows systems), accept the default value.
• Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names
in URLs wherever possible so the domain name system (DNS) can determine which
IP address to use.
If you must use IP addresses and your network uses IPv6 addresses, enclose the literal
IPv6 address in square brackets, for example:
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc
Parameter Description
RMI Port Port number used by the rich client distribution server. This
value was determined when the distribution server was
installed. The default is 12099.
WindowsLocation Location on the client host where you want the
Over-the-Web Installer to download rich client files on
Microsoft Windows systems by default.
The drive must exist on the client hosts prior to rich
client installation, and users must have write permission
to it. For example, if the installation location is
F:\Teamcenter\rich_client, every Windows client host
must have an F drive, and users must have permissions to
create Teamcenter\rich_client.
UnixLocation Location on the client host where you want the
Over-the-Web Installer to download rich client files on
UNIX systems by default.
The mount must exist on the client hosts prior to rich client
installation, and users must have write permission to it.
WebBrowserUnixLocation Location of a web browser on Linux client systems. This
location must be available for Linux client hosts.
RichClientHelpWebServer URL specifying the path to the Teamcenter online help
installed on the PLM Documentation Server. Set this value
to:
http://host:port/tdoc/tc/version
or SP level.
RichClientHelpLocation Set to /help.

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

JREWindows64Location Specifies the path to the Java Runtime Environment (JRE)
on the client host during installation of the rich client
through the Over-the-Web Installer on 64-bit versions of
Windows.
By default, the Over-the-Web Installer uses the value of the
JRE64_HOME environment variable on the target client
host. Change the value of this context parameter if you
want to specify a different path.
JREUNIXLocation Specifies the path to the Java Runtime Environment (JRE)
on the client host during installation of the rich client
through the Over-the-Web Installer on Linux systems.
By default, the Over-the-Web Installer uses the value of the
JRE_HOME environment variable on the target client host.
Change the value of this context parameter if you want
to specify a different path.
Depending on the solutions you include in your rich client distribution instance, you may need to
provide values for the additional parameters shown in the following tables.
Rich client optional parameter values

TeamcenterSSOService Complete URL of the Security Services Identity Service
web application. This information is required only when
you configure the rich client to log on using the optional
Security Services.
This URL is determined when Security Services is
installed and configured. You must provide the same
URL used to configure Security Services on the web
tier.
TeamcenterSSOlogonURL Complete URL of the Security Services logon Service
web application. This information is required only when
you configure the rich client to log on using the optional
Security Services.
This URL is determined when Security Services is
tier.

Chapter
Installing the Java
the Java EE tier
EE web web tier

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


FMSProxyHTTPSPort Number of port for HTTPS proxy server for File
Management System (FMS) communication. If you
do not specify a port number, the rich client does not
communicate with FMS using an HTTPS proxy server.
To configure an HTTPS proxy server, you must
also specify a value for the FMSProxyHTTPSHost
parameter.
Install a rich client distribution instance
Install the rich client instance on the same host and in the same directory as the distribution server.
1. Expand the rich client over-the-web software distribution image (Teamcenter-version_otw.zip) to
a drive on your local host.2
2. If you use Teamcenter lifecycle visualization, make sure the Lifecycle Visualization software
distribution is available from your host. The Over-the-Web Installerrequires this to install Lifecycle
Visualization viewers.
3. Start the Web Application Manager:

a. Browse to the WEB_ROOT directory.

box.
4. Copy web tier solution ICDs:3

a. Click Copy ICDs.
b. In the Copy ICD Files dialog box, click Browse.
c. Browse to the tcrs_icd directory of the Teamcenter 11.2 over-the-web software distribution
image. Select the tcrs_icd directory, and then click Open.
In the Copy ICD Files, click OK to load ICD files.
2. If you expanded the over-the-web software distribution image when you installed the rich client distribution server, skip this step.
3. If you copied solution ICD files when you installed the rich client distribution server, skip this step.

Chapter
Installing the Java
the Java EE tier
EE web web tier
Note
The Web Application Manager displays a Progress dialog box while it copies ICD files.
When ICD files are copied, a list of ICD files follows the Copying ICD files... notice. If
no files are listed, Web Application Manager did not find files to copy in the directory you
entered.
If the ICD files are not copied successfully, repeat these steps ensuring that you include
the tcrs_icd directory in the path. Not including the tcrs_icd directory is the most common
reason ICD files are not copied.
5. In the Teamcenter Web Application Manager dialog box, click Add.

The Web Application Manager displays the Add Web Application dialog box.
6. In the Name box, type a name for this instance.

Choose a name that uniquely identifies this web application instance.
7. In the Staging Location box, enter the path to the directory where you want to install the rich
client image files for downloading to clients.
Typically, you would install the rich client distribution instance files in a directory under the
Web_tier directory, the directory in which you installed the Web Application Manager on your
hard drive.
Note
• This directory must be empty. The Web Application Manager creates the directory
if it does not exist.
• Note the staging location path of this distribution server instance for later use.
8. Optionally, in the Description box, type a brief description of this instance.
9. Enter software locations:

a. Click the Add button adjacent to the Disk Locations for Install Images box.
The Web Application Manager displays the Add Disk Location dialog box.
b. In the Add Disk Location dialog box, enter the locations of the following software
distributions. For each location, enter the path in the Disk Location to Add box, and then
click Apply.
• Teamcenter 11.2 over-the-web software distribution image.
• Teamcenter lifecycle visualization software distribution image.

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

distributions for each platform.
c. Click OK to close the Add Disk Location dialog box.

Note
To modify a location or remove a location from the Disk Locations for Install Images list,
click Modify or Remove.
10. In the Solution Type list, choose Distribution Server Instance.

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

Note
• The path specified in the WindowsLocation context parameter must not contain
any of the following special characters:
#~!@$%^&*()_+=
If the WindowsLocation contains any of these characters, the Over-the-Web Installer
fails to install the rich client.
• The required parameters must have values specified. If a required parameter has no
significance for your deployment (for example, a UNIX location in an environment of
all Windows systems), retain the default value.
• For descriptions of rich client required parameters, see Rich client distribution instance
requirements. The rich client required parameters vary, depending on the solutions
you install with the rich client.
The Web Application Manager displays the Modify Required Table dialog boxes for the
HTTPServerTable and the ParentFSCAddressTable.
14. For each table, type the values for each parameter. To add another row to the table, click Add
Row.

Chapter
Installing the Java
the Java EE tier
EE web web tier
Note
Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names
IP address to use.
Table Description
HTTPServerTable Type a list of web tier application servers; the first server in
the list is the default server for logon. Requires the following
information for each server:
URI
URL of the web-tier SOAP endpoint. The value depends
on where the web tier application is deployed. Typically
it has the form:
http://host-name:port/tc/webclient
Name
Display name of the URL for the rich client user interface.
Note
• If you use Teamcenter client communication

system (TCCS), you do not need to supply
values for the HTTPServerTable table because
you specify these when you define TCCS
environments.
• If you use Security Services in applet-free mode,

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

15. When you complete each table, click OK.

When you complete setting values for the last table, the Web Application Manager displays a
Progress dialog box and performs the following tasks:
• Extracts the rich client image files into the webapp_root directory under the staging location
directory (named in step 7).
• Creates the manifest file (ds_manifest.mf) in the staging location directory (named in step 7).
The manifest file records and maintains information about the rich client image files, including
a list of the files and a version for each file. The Over-the-Web Installer consults the manifest
file to determine which files to download.
16. When the Progress dialog box indicates that installation is complete, click OK.
The Web Application Manager displays the Teamcenter Web Application Manager dialog box.
17. Click Exit to exit the Web Application Manager.
To make the rich client distribution instance available to client hosts, deploy the distribution instance
on a supported web application server.
Configuring TCCS, Security Services, and proxy settings
Configure TCCS for the rich client distribution instance

1. In the Web Application Manager, select your four-tier rich client application in the Web
Applications list, and then click Modify.
2. In the Modify Web Application dialog box, click Modify Context Parameters.
3. In the Modify Context Parameters dialog box, enter values for TCCS context parameters, and
then click OK to continue.
Context Parameter Description

Client Communication System Specifies whether to enable TCCS to handle
Switch communication between the client application and the
web tier.
If you want to enable TCCS, set this parameter to on;
otherwise, set it to off.
Client Tag Filter Specifies a pattern to apply when filtering TCCS
environments. Wildcard characters (*) are allowed.
The Client Tag Filter pattern is compared to the
Tag parameters on defined TCCS environments.
Environments that do not fit the pattern are not
available to the rich client. For example, if the
rich client Client Tag Filter value is 9.*, all TCCS
environments with Tag values beginning with 9. are
available to the rich client. Environments with Tag
values beginning with 10 are not available.

Chapter
Installing the Java
the Java EE tier
EE web web tier
Context Parameter Description

TcCSShareConfiguration Specifies whether the TCCS configuration is a private
or shared environment.
If this is a private environment, set this parameter to
false. If it is a shared environment, set this parameter
to true.
TcCSProxyConnectionType Specifies whether to use specify the proxy connection
type.
If you do not use a proxy, set this parameter to Do not
use proxy. Otherwise, accept the default value.
TcCSKerberosSupport Specifies whether to use Kerberos authentication for
Teamcenter logon.
If you use Kerberos, set this parameter to true;
otherwise, set it to false.
Note
Teamcenter supports Kerberos authentication

only on Windows client hosts.
TcCSKrb5File Specifies the path to the Kerberos configuration file
(krb5.ini). If you leave this parameter empty, the client
uses the default Kerberos configuration file.
On Windows systems, the default krb5.ini file is in
the C:\Windows directory.
TcCSAlwaysPromptForUserID Specifies whether to always prompt for a Kerberos
user name.
If you want to enable zero sign-on functionality on
Windows hosts, set this parameter to false. This
setting uses the native operating system user ID for
Kerberos authentication on the client host.
Zero sign-on allows Windows users to launch a
Teamcenter client without being prompted to log on
to Teamcenter.
4. In the Modify Web Application dialog box, click Modify Tables.
5. In the Modify Tables dialog box, select the TcCSEnvironmentTable table, and then click Modify.
6. In the Modify Table dialog box, click Add Row. Enter values for the TCCS environment and
then click OK to continue.
Value Description
Name Specifies the name of a the TCCS environment. This
name is displayed in the TCCS logon dialog after
configuration is complete.

Value Description
URI Specifies the URI to the TCCS environment. This is the
endpoint URI for the web tier deployment, for example,
http://host:port/tc.
Tag Specifies a string identifier for the TCCS environment.
When installing a rich client, you can optionally provide
a Client Tag Filter value to filter the list of environments
displayed in the rich client to those environments that
match the filter.
For example, if the Client Tag Filter value is 9*, all
TCCS environments with Tag values beginning with 9
are available to the client host. Environments with Tag
values beginning with 10 are not available.
Note
You set the Client Tag Filter value in step 3.

TcSS Application ID Specifies the ID of the Security Services application you
use with TCCS.
TcSS Login URL Specifies the URL to the Security Services application
you use with TCCS.
If you use Security Services in applet-free mode, include
/tccs at the end of the URL, for example:
http://host:port/app-name/tccs
Note
Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names in
URIs and URLs wherever possible so the domain name system (DNS) can determine
which IP address to use.
7. In the Modify Web Application dialog windows, click OK to apply your changes.
8. Exit the Web Application Manager and redeploy the rich client distribution instance.
Configure Security Services for the rich client distribution instance
1. Launch the Web Application Manager.
2. In the Web Applications box, select the web application that contains the rich client distribution
instance and click Modify.
The Web Application Manager displays the Modify Web Application dialog box.

Chapter
Installing the Java
the Java EE tier
EE web web tier
3. Click Modify Context Parameters.
Web Application Manager displays the Modify Context Parameters dialog box.
4. Type values for the Security Services context parameters, and then click OK.
5. Exit the Web Application Manager and redeploy the rich client distribution instance.
Installing and configuring Security Services is described in Security Services

Installation/Customization.
Related topics
• Installing Security Services
Configure reverse proxy settings for the rich client distribution instance
If you must connect to a Teamcenter environment through a reverse proxy server (such as WebSEAL
or SiteMinder), you may need to configure TCCS reverse proxy settings for SiteMinder or WebSEAL
by performing the following steps:
1. In the Web Application Manager, select your four-tier rich client application in the Web
Applications list, and then click Modify.
2. In the Modify Web Application dialog box, click Modify Tables.
3. In the Modify Tables dialog box, select the TcCSReverseProxyConfigurationTable table,

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

Deploying the distribution instance
Deploy the distribution server instance

Install a supported third-party web server.
A rich client distribution instance requires a web server, such as Apache HTTP Server. You can
also use an application server, such as IBM WebSphere, but it is not required. For information
about supported web servers and application servers, see the hardware and software certifications
page on GTAC.
Web Application Manager installs the following files in the webapp_root\otwweb folder under the
distribution server instance staging location.
• otw_installer.jar file
Contains the Over-the-Web Installer.
• images directory
Contains all images used by the web pages.
• installed.html file
Contains the English version of the HTML page displayed with installation completes successfully.
• installfailed.html file
Contains the English version of the HTML page displayed when installation fails.
• installing.html file
Contains the English version of the HTML page for launching the Over-the-Web Installer.
• launcherror.html file
Contains the English version of the HTML page displayed to the user when the Over-the-Web
Installer cannot install the rich client due to one of the following problems:
o The connection to the web is not available or the user has not provided permissions to install.
o The required Java Plug-in is not available and cannot be installed automatically.
o Java and or JavaScript are disabled in the web browser.
• otw.html file
Contains the logic for detecting the web browser and Java Plug-in required for installing the rich
client over the web.
• localized directory
Contains subdirectories for each supported locale other than English (French, German, Italian,
Japanese, Korean, Russian, S_Chinese, Spanish, and T_Chinese). The subdirectories contain
localized versions of the installing.html and error.html files. To use a localized version of the
installation, deploy the localized installing.html and error.html files rather than the English
versions.

Chapter
Installing the Java
the Java EE tier
EE web web tier
Note
Before deploying a localized installing.html file, you must edit it as follows:

1. Using a text editor, find the following two lines and in each replace
change_me_instance with the name of the instance:
<param name="instance" value="change_me_instance>
instance="change_me_instance"
2. Find the following two lines and in each replace change_me_server with the name
of the server host:
<param name="server_name" value="change_me_server>
server_name="change_me_server"
When editing the preceding information, do not delete the quotation marks.
For each distribution server instance you create, deploy these files in a web server. If you are creating
multiple rich client distribution instances, consider creating a unique directory in the web server
documentation root for each instance and copy all the files in the webapp_root\otwweb folder there.
For detailed deployment information, see the documentation provided by the web server vendor.
The following examples use the name of the instance for the web component directory name:
Web server Deployment

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

directory.
3. Copy the rich client web file to the instance-name directory.
4. Publish the following URL:

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

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


Web server Deployment

IBM WebSphere 1. Find the document root directory (HTTP server core settings in the
administration server console).
2. Create the instance-name directory under the HTTP document root

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

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

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

Publish information for users
To enable users to install the rich client over the web, publish the following information:
• URL where the web components are located.
• The location in which the rich client will be installed on user workstations. Users must have
write permissions for this location.
• For rich client instances that include support for Teamcenter lifecycle visualization or NX, the
locations in which users must install Teamcenter lifecycle visualization and NX.
Start and stop the rich client distribution server
Start the rich client distribution server
1. Go to the staging location directory you created for the distribution server.
This is the directory containing the distribution server application and administration utilities.
2. Ensure that the Java runtime environment (JRE) bin folder is in the Windows path. This is
the path to your JRE installation, for example:
JRE-HOME\bin

Chapter
Installing the Java
the Java EE tier
EE web web tier
3. Browse to the webapp_root subdirectory and double-click the start_rmi.bat program file.
The start_rmi.bat program file starts the Java remote method invocation (RMI) registry.
4. In the webapp_root subdirectory, double-click the start_server.bat program file.

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

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

After a rich client distribution server and server instances are installed and configured, you can
change the distribution server contents, add components to a distribution server instance, and patch
components in a distribution server instance.
Note
To allow automatic updating of a rich client when users start a Teamcenter session, do not
change the name of the distribution instance.
1. Stop the rich client distribution server.
2. Replace the existing dist_server.jar file with the new JAR file.
The dist_server.jar is in the in the webapp_root subdirectory of the staging location for the
distribution server.
3. Restart the rich client distribution server.

Add components to the distribution server instance
1. Launch the Web Application Manager:

a. Browse to the Web_tier directory.

box.
2. Click Copy ICDs.

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

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

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

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

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

Chapter
Installing the Java
the Java EE tier
EE web web tier
Note
• The required rich client parameters vary, depending on the applications you are
installing with the rich client instance.
• The required parameters must have values specified. If a required parameter has no
significance for your deployment (for example, a UNIX location in an environment of
all Windows systems), retain the default value.
The Web Application Manager begins installation of the solutions and displays a Progress
dialog box.
11. When installation is complete, click OK to close the Progress dialog box.
12. If the solution you added has optional parameters you want to modify, click Modify Context
Parameters.
The Web Application Manager displays the Modify Context Parameters dialog box.
Note
If you change a context parameter, the Over-the-Web Installer cannot automatically

update the rich client installation on user workstations. Users must uninstall the rich client
and reinstall it from this instance.
For example, if you add the Teamcenter lifecycle visualization embedded viewer solution,
and modify the PVisLicenseLevel context parameter, users must uninstall and reinstall
the rich client.
13. Type the values for the optional parameters and click OK.
Note
For descriptions of the optional parameters, see Rich client optional parameter values.
14. Exit the Web Application Manager.
15. If you changed a context parameter value, notify users that they must uninstall the rich client
and reinstall from the same instance.
Run the distribution server as a service
1. Create the service:

a. Open a command prompt and change to distribution server location, for example,
WEB_ROOT\staging\app-name\webapp_root.
Replace WEB_ROOT with your home directory for Teamcenter web applications. Replace
app-name with the staging directory for your web application that contains the distribution
server.

b. Type the following commands:

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

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

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

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

java -cp WEB_ROOT\staging\app-name\webapp_root\dist_server.jar
com.teamcenter.install.otw.ds.DistributionServer
Note
Make sure you include a space following -cp as shown in the key value.
l. Create a string value under Parameters named AppDirectory.
m. Set the AppDirectory string value to the following value:

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

a. Open the Services dialog box in the Windows Control Panel.
b. In the Services list, right-click the OTWRMI service and choose Start.
c. In the Services list, right-click the OTWDistServer service and choose Start.

Chapter
Installing the Java
the Java EE tier
EE web web tier
Note
The distribution server services start automatically when you restart Windows.
If you want to remove the distribution server services, perform the following steps:
1. In the Services dialog box in the Windows Control Panel, stop the OTWRMI and OTWDistServer
services.
2. Open a command prompt and enter the following commands:

sc delete OTWDistServer
sc delete OTWRMI

Chapter 4: Installing the Java EE server manager
Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Install the Java EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Launch the Teamcenter Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Chapter 4: Installing the Java EE server manager
Gather required information

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

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

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

Connection Timeout parameter when configuring the
web tier application.
• A list of addresses (host name and port number pairs) to
ping for peer members of the TreeCache cluster in TCP
communication mode.
This cluster member pings each host/port pair in the list. To
be found, a peer must have a matching service port (see
the Local Service Port context parameter). Once a peer is
found, the peers exchange data regarding available server
pools.
Note
You can include more than one address on a given

host. It is not necessary to include all members of
the cluster in this list. However, it is important that
when each cluster member after the first is started, it
should ping a member that is already in the cluster.
For example, it is valid to include only a subset of
the server managers and none of the application
servers. In this case, the cluster connects only when
one or more of the designated managers is running.
This method reduces pinging and thereby improves
performance.

Installing the Java EE server manager
Data Description
For small configurations, all members (server

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

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

1. Launch Teamcenter Environment Manager (TEM).

Chapter
Installing the Java
the Java EE server
EE server manager
manager
If you create a new Teamcenter configuration, launch TEM from the Teamcenter software
distribution image. If you want to add the Java EE server manager to an existing configuration,
launch TEM in maintenance mode.
2. Proceed to the Features panel. Under Server Enhancements, select Java EE based Server
Manager.
3. Proceed to the TcServer Character Encoding Settings panel. Make sure the values reflect the
character set you use for Teamcenter. If you are not sure, accept the default settings.
For information about the values in this panel, click the help button .
4. In the Multiplexing Proxy panel, accept the default values or type new values for the Teamcenter
multiplexing proxy (MUX).
Value Description
Port Specifies the TCP/IP port on which the MUX listens
for web tier requests. This is the Jetty server
connector port.
TECS Admin Port Specifies the port used by the Teamcenter Enterprise
Communication System (TECS).
Note
The MUX listens on a single port for incoming requests from the web tier, forwarding
those requests to an appropriate Teamcenter server using operating system named-pipe
communication protocol, and then streaming the response back to web tier. The MUX runs
as an application within the Teamcenter Enterprise Communication System (TECS). The
TECS container is based on the Teamcenter client communication system (TCCS)
container used in the client tier.
5. Proceed to the Communication Configuration panel and enter the required values:
a. In the Pool ID and JMX RMI Port boxes, type a name and port for the server pool.
b. In the Assignment Service Port box, type a port number for the server manager assignment
service.
c. In the Server Host box, type the logical host name of the server manager host. This value
allows you to control which IP address is used when connecting to Teamcenter servers.
d. Under Startup Mode, select one of the following:

• Service/Daemon
Specifies you want to run the server manager as a Windows service. This is the default
mode.
• Command Line
Specifies you want to run the server manager manually from a command line.

Installing the Java EE server manager
Enter remaining values as needed in the Server Manager for Java EE panel. For more
information about fields in this panel, click the help button .
6. Proceed to the Server Manager TreeCache Configuration panel.

Enter required values for the server manager TreeCache configuration or accept the default
values shown.
7. Proceed through remaining panels to the Confirmation panel. Click Start to begin installing the
Teamcenter server with the Java EE-based server manager.
8. When installation completes, exit TEM.
9. After you install the Java EE server manager, install the Teamcenter Management Console using
the appropriate steps for Windows platforms.
You can install multiple Java EE server manager services on the same host. Each server manager
service has its own configuration directory:
TC_ROOT\pool_manager\confs\config-name
Replace config-name with the name of the server manager configuration.
The server manager configuration directory contains configuration files, log files, and server manager
scripts. These include the following.
File/Directory Description
mgrstart Script that launches the Java EE server manager in console mode.
mgrstop Script that stops the Java EE server manager when started from a
command line.
If you run the Java EE server manager as a Windows service, stop
the service using the Windows services manager.
Note
You can also stop the server manager using the Teamcenter
Management Console.
mgr.output If you run the Java EE server manager as a Windows service, this
file contains all output from the Java EE server manager.
This file is not used if you run the server manager from the command
line.
logs Directory that contains all Java EE server manager log files.
If you run the Java EE server manager as a Windows service, the server manager starts automatically.
Launch the Teamcenter Management Console

Start the Teamcenter Management Console using the appropriate steps for Windows platforms.

Chapter 5: Teamcenter Rapid Start client installation
Prepare the Rapid Start client host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Perform a Teamcenter Rapid Start client quick installation . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Performing a Teamcenter Rapid Start client custom installation . . . . . . . . . . . . . . . . . . . . . . . 5-3

Install the rich client using TEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Install the four-tier rich client (HTTP-based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Install the two-tier rich client (IIOP-based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Install the rich client using the Over-the-Web Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Install Teamcenter Plug-in for Microsoft Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Chapter 5: Teamcenter Rapid Start client installation
Prepare the Rapid Start client host

Install the following software on the Teamcenter Rapid Start client host:
• Microsoft Windows Server 2008 or 2012 operating system (64-bit)
• A supported version of the Java runtime environment (JRE)
Verify that your Teamcenter Rapid Start server environment is running and is properly configured
before you install a Teamcenter Rapid Start client.
Set the JRE64_HOME environment variable on the client host to the location of a supported 64-bit
Java JRE.
Teamcenter Environment Manager (TEM) verifies the JRE version during launch and cancels
installation if a certified JRE is not available on the host. After installation is complete, TEM no
longer requires this variable.
Note
Alternatively, you can specify the Java JRE location by one of the following methods:
• Set the JRE_HOME environment variable to the location of a supported 64-bit Java JRE.
• When you launch TEM type the following command in a command prompt using the -jre
argument to specify the location of a supported 64-bit Java JRE:
tem -jre JRE-path
For example:
tem -jre c:\apps\jre1.7
Perform a Teamcenter Rapid Start client quick installation

1. Start Teamcenter Environment Manager (TEM) to begin installing Teamcenter Rapid Start:
a. Browse to the root directory of the Teamcenter installation media.
b. Double-click the tem.bat program icon.

Warning
Do not use the Windows Run as option to run the Teamcenter Rapid Start setup
program as a user with administrator privileges. To successfully install and configure
Teamcenter Rapid Start, you must log on as a user with administrator privileges.

Chapter
Teamcenter
RapidRapid
Start Start
clientclient installation
installation
2. In the Welcome to Teamcenter panel, select Teamcenter Rapid Start.
3. In the Install/Upgrade Options panel, click Quick Preconfigured Install.
4. In the Product Selection panel, select one of the following options:
• Teamcenter Rich Client 4-Tier
• Teamcenter Rich Client 2-Tier
If you want to add Teamcenter Rapid Start features not automatically included in the quick
preconfigured installation, select the Include additional features check box. If you select
additional features, TEM may display additional panels not described in this procedure.
5. Configure the rich client:
• Four-tier rich client
Proceed to the Teamcenter Rich Client 4-Tier panel. Enter the required information to
install a four-tier rich client that connects to an existing Teamcenter Rapid Start middle tier
and corporate server.
Value Description
4 Tier Server URI Specifies the URI to the rich client middle tier. Type a
URI of the following form:
http://host:port/tc
FCC Parent Specifies the URI to the FMS server cache (FSC) used
by the local FMS client cache (FCC) in your four-tier rich
client configuration. Type a URI of the following form:
http://host:port
Installation Directory Specifies the directory in which you want to install
Teamcenter. Enter a directory that does not exist. TEM
creates the directory you specify.
Proceed to the Teamcenter Rich Client 2-Tier panel. Enter the required information to install
a two-tier rich client that connects to an existing Teamcenter Rapid Start corporate server.
Value Description
Host name Type the host name of the corporate server.
Data directory Type the UNC path to data directory (TC_DATA) for the
corporate server.

Teamcenter Rapid Start client installation
Value Description
FCC Parent Specifies the URI to the FMS server cache (FSC) used
by the local FMS client cache (FCC) in your four-tier rich
client configuration. Type a URI of the following form:
http://host:port
Installation Directory Specifies the directory in which you want to install
Teamcenter. Enter a directory that does not exist. TEM
creates the directory you specify.
6. If you selected additional features, proceed through any remaining panels, entering the required
information for the features you selected.

Otherwise, click Start to begin installing the Teamcenter corporate server.
Note
by TEM or see the available troubleshooting solutions.
Related topics
• File Management System
Performing a Teamcenter Rapid Start client custom installation
Install the rich client using TEM

Note
On Windows 7 systems, the Windows User Access Control (UAC) or Least-privileged User
Account (LUA), if enabled, may interfere with configuration of some rich client features.
1. Install the prerequisite software on the client host. Teamcenter Environment Manager (TEM) does
not install the prerequisite software.
Note
Installation of the prerequisite software requires administrative privileges.
2. Set the JRE64_HOME system environment variable to the path to a supported 64-bit Java JRE,
for example, C:\Program Files\Java\jre7x64.

Chapter
Teamcenter
RapidRapid
Start Start
installation
3. Locate the Teamcenter software distribution image.

You can install the rich client from a full distribution downloaded from GTAC or from a compact
distribution created by your Teamcenter administrator.1

6. In the Install/Upgrade Options panel, click Install.
8. In the Configuration panel, type an ID and a description for the new Teamcenter configuration.
Note
The configuration ID identifies your configuration when you perform maintenance tasks in
TEM. Also, installation log files reference your configuration by this ID.
9. In the Solutions panel, select Rich Client (2-tier and 4-tier).
10. Proceed to the Features panel. In the Installation Directory box, enter the path and directory in
which you want to install the rich client. The directory must not exist. (TEM creates the directory.)
11. The Teamcenter Rich Client (2-tier and 4-tier) feature is selected by default. Select any
additional features you want to include in your rich client configuration.
For information about a feature, point to the feature in the list to display a description.
Note
• If you select additional features, TEM displays additional panels during installation
that are not described in this procedure.
• If you install the rich client from a compact distribution and you select features not
included in the compact distribution media, TEM prompts you for the location of the full
distribution media.
12. In the File Client Cache (FCC) panel, choose whether to use a new or existing FMS client
cache (FCC).
If you want to create a new FCC using the same settings as an existing FCC on your host, select
the Merge values from an existing FMS_HOME check box.
13. In the FCC Parents panel, enter access information for the FMS server cache (FSC).
1. A compact distribution package is much smaller than a full Teamcenter software image and may contain a selected subset of features.

a. Double-click the Host box, and then type the host name of the FSC.
b. Double-click the Port box, and then type the port used by the FSC. The default value is 4544.
c. In the Protocol box, select the appropriate protocol used by the FSC.
If you want to add access to additional FSCs, click Add to add a row to the table, and then
enter access information for the parent FSC. To remove a host from the list, select the row and
click Remove.
If you use multiple FSCs, assign a connection priority to each using values in the Priority column.
Note
You can configure File Management System further after installation.
14. Proceed to the Configuration Selection for Client Communication System panel.
If you are a TCCS administrator, select Shared if you want this configuration to be used by
multiple users, or select Private if this configuration is for your use only. By default, the shared
configuration is used by the system for all users connecting using TCCS.
Select whether to create a shared or private TCCS configuration. If you are not a TCCS
administrator, you can only create a Private configuration for your use only. A TCCS administrator
can create both shared and private configurations.
15. Proceed to the Environment Settings for Client Communication System panel.
To add an environment to the table of TCCS environments, click Add. TEM displays the Edit
Environment Setting dialog box.
Select 2-tier settings or 4-tier settings, and then enter the required values for the selected
deployment type.
• Two-tier deployment

Chapter
Teamcenter
RapidRapid
Start Start
installation
Value Description
Name Specifies a name for the TCCS environment.
TC_DATA Enter the path to the data directory (TC_DATA) where
you want Teamcenter Environment Manager to create
shared data subdirectories and files.2
Tag (Optional) Specifies a tag for the environment that
can be used to filter the list of TCCS environments
during rich client logon.
In the Client Tag Filter panel during rich client
installation, you can optionally provide a pattern to
filter the list of environments displayed in the rich
client to those environments that match the pattern.
Example
You create 10 environments, three on Server1

with Security Services, three on Server1
without Security Services, and four on Server2.
Tag the environments SSO, no SSO, and
Server2, respectively.
SSO App ID Specifies a Security Services (SSO) application ID.
Type an application ID if you want to add a Security
Services environment to your TCCS environment.
2. This can be the network path to the TC_DATA directory on your corporate server.

Value Description
SSO Login URL Specifies the logon URL to the Security Services
environment.
Note
You must set up the Security Services

environment before you configure TCCS.
For example, in the SSO App ID box, type the
value of the SSO_APPLICATION_ID context
parameter from the web tier installation. In
the SSO Login URL box, type the value of
the SSO_LOGIN_SERVICE_URL context
parameter.
TcServer Character Encoding Specifies the canonical name of the character
Canonical Name encoding set Teamcenter clients use to access the
database.
Caution
To prevent data corruption, this character

encoding set must match the encoding set
used by the Teamcenter database.
Single Server Specifies whether to force all client sessions for the
given user to use the same tcserver process. If set
to true, all client sessions use the same tcserver.
Setting it to false allows clients to control sharing of
tcserver processes.
• Four-tier deployment

Chapter
Teamcenter
RapidRapid
Start Start
installation
Value Description
Name Specifies a name for the TCCS environment.
URL Specifies the URL to the rich client middle tier. Type a
URL of the following form: http://host:port/tc.
Tag (Optional) Specifies a tag for the environment that
can be used to filter the list of TCCS environments
during rich client logon.
In the Client Tag Filter panel during rich client
installation, you can optionally provide a pattern to
filter the list of environments displayed in the rich
client to those environments that match the pattern.
Example
You create 10 environments, three on Server1

with Security Services, three on Server1
without Security Services, and four on Server2.
Tag the environments SSO, no SSO, and
Server2, respectively.
SSO App ID Specifies a Security Services (SSO) application ID.
Type an application ID if you want to add a Security
Services environment to your TCCS environment.

Value Description
SSO Login URL Specifies the logon URL to the Security Services
environment.
Note
You must set up the Security Services

environment before you configure TCCS.
For example, in the SSO App ID box, type the
value of the SSO_APPLICATION_ID context
parameter from the web tier installation. In
the SSO Login URL box, type the value of
the SSO_LOGIN_SERVICE_URL context
parameter.
A single TCCS configuration can contain multiple environments. For example, you may want
to install some TCCS environments with Security Services (SSO), some without SSO, or some
environments on only certain servers. If you configure multiple environments, a selection list of
environments is displayed during rich client logon.
For advanced TCCS settings, click Advanced.
16. Proceed to the Client Tag Filter panel.

If multiple TCCS environments exist in your system, you can optionally limit the TCCS
environments available to the rich client by specifying a pattern in the Client Tag Filter box. This
pattern is used to filter the list of TCCS environments, which are each identified by a unique Tag
value. Wildcard characters (*) are allowed in the Client Tag Filter box.
For example, if the Client Tag Filter value is set to 10.* in the rich client, all TCCS environments
with Tag values beginning with 10. are available to the rich client. Environments with Tag values
beginning with 11 are not available.
17. In the Rich Client Settings panel, specify online help settings.
If you want to configure online help for the rich client, select the Enable Online Help check
box, and then type the online help URL in the Web server URL box.
Note
This step assumes you installed Teamcenter online help before installing the rich client.
If not, you can install online help and configure online help access after installation is
complete.
If you want to specify Security Services settings or other advanced rich client settings, click
Advanced.
18. Proceed to the Confirmation panel and review your selections. Click Start to install the rich
client, or click Back to change your selections.
When installation is complete, close TEM.

Chapter
Teamcenter
RapidRapid
Start Start
installation
The installation places the Teamcenter rich client icon on your desktop. To start the rich client,
either double-click the desktop icon or press the following shortcut keys:
Control+Shift+F
Install the four-tier rich client (HTTP-based)

Note
Note


Note
9. In the Solutions panel, select Rich Client 4-tier.

11. The Teamcenter Rich Client 4-tier feature is selected by default. Select any additional features
you want to include in your rich client configuration.
Note
distribution media.
cache (FCC).
click Remove.
Note
14. Proceed to the 4-tier server configurations panel. In the URI column, enter the URI for the
Teamcenter web tier server. In the Connection Name column, enter a name for the rich client
connection.
Note
Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names in
URIs wherever possible so the domain name system (DNS) can determine which IP
address to use.

Chapter
Teamcenter
RapidRapid
Start Start
installation
Note
complete.
Advanced.
Control+Shift+F
Install the two-tier rich client (IIOP-based)

Note
Note



Note
9. In the Solutions panel, select Rich Client 2-tier.
11. The Teamcenter Rich Client 2-tier feature is selected by default. Select any additional features
you want to include in your rich client configuration.
Note
distribution media.
cache (FCC).
click Remove.
Note

Chapter
Teamcenter
RapidRapid
Start Start
installation
14. In the TcServer Character Encoding Settings panel, make sure the values reflect the character
set you use for Teamcenter. If you are not sure, accept the default settings.
15. In the 2-tier server settings panel, define how you will access the Teamcenter corporate server.
a. Make sure the Connection Port box reflects the port used by your Teamcenter corporate
server.
b. Specify database access for your rich client:

A. Click Add.
B. Enter the path to the data directory (TC_DATA) where you want Teamcenter Environment
Manager to create shared data subdirectories and files.5
C. Enter a unique name for the connection.
D. Click OK.
E. If you want to add access to additional databases, repeat the previous four steps to
add access information for each database.
To remove a database from the list, select the row and click Remove. To edit values for a
database connection, select the row and click Edit.
If you connect to multiple databases, assign connection priority by selecting rows and
clicking Up or Down.
Note
complete.
Advanced.
Control+Shift+F
5. This can be the network path to the TC_DATA directory on your corporate server.

Install the rich client using the Over-the-Web Installer

1. Open the URL to the Over-the-Web Installer, for example:
http://host/path/otwweb/otw.html
Obtain the URL from your Teamcenter administrator.
The Over-the-Web Installer installs the rich client.
Note
Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use host names
IP address to use.
2. Restart the operating system.
This step is required to activate the FMS_HOME environment variable set by the Over-the-Web
Installer.
3. If the rich client includes Teamcenter Automotive Edition–GM Overlay, you must complete
additional required configuration steps.
The Over-the-Web Installer places the Teamcenter rich client icon on your desktop. To start
the rich client, double-click the icon.
Each time you start the rich client, the startup process checks for updates and downloads them to
your workstation. After checking and downloading changed and new components, it starts the rich
client application using the updated components.
Note
The four-tier rich client requires the Microsoft Visual C++ 2008 redistributable libraries. If these
libraries are not present on the client host, the Over-the-Web Installer automatically installs
the libraries. You must then restart your system, and then restart the Over-the-Web Installer
to complete rich client installation.
Install Teamcenter Plug-in for Microsoft Project

1. Browse to the additional_applications\tc_ext4mso directory in the Teamcenter software
distribution image.
2. Double-click the TcMspIntegrationSetup.exe program icon to launch the Teamcenter Microsoft

Project Integration installation wizard.
3. Complete the wizard to install the integration.
4. To verify the installation completed successfully, start Microsoft Project and verify the Teamcenter
Integration button or tab is displayed.

Chapter 6: Upgrading to Teamcenter Rapid Start
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Upgrade Teamcenter Express server to Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . 6-1
Upgrade Teamcenter Express client to Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . 6-4
Upgrade Business Modeler IDE template project and code to Teamcenter Rapid Start . . . . . . . 6-6
Moving to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Chapter 6: Upgrading to Teamcenter Rapid Start
Before you begin

• To upgrade to Teamcenter Rapid Start 11.2, you must be running Teamcenter Express 5.3.x or
Teamcenter Express 9.1.x.
• Before upgrading, ensure that all Teamcenter user sessions are terminated.
• Ensure that you have write permission on the default volume of the administrative user (infodba).
• Use the database utilities to back up your database before upgrading.
• All customizations done outside the database (for example, portal properties) must be moved
forward manually. All customizations done within the database are carried over by reusing
the same database.
• Before upgrading the client, be sure that the server you plan to connect to has been upgraded to
Teamcenter Rapid Start 11.2.
• If you have custom templates (custom objects), migrate them to the compatible versions.
• The following Teamcenter Express features are replaced by Teamcenter Rapid Start features:
o Sync mapping
Replaced by the attribute exchange feature in Client for Office.
o ERP Axapta and Great Plains

Available if installed in previous environments (Teamcenter Express 5.3.x) before upgrading
to Teamcenter Rapid Start 11.2. These features are not available for new installations of
For information about the Teamcenter Rapid Start ERP integration, see the Teamcenter Rapid
Start Start add-on module list or contact your Siemens PLM Software sales representative.
o Self-Paced Training
Replaced by the Teamcenter Help Collection.
Upgrade Teamcenter Express server to Teamcenter Rapid Start

1. Save any customizations done in the existing TC_ROOT directory.
2. If you are upgrading from Teamcenter Express 5.3.x to Teamcenter Rapid Start 11.2, upgrade
the Solid Edge Embedded Client (SEEC) template as follows:
a. Download the required Solid Edge Embedded Client template from GTAC.

Chapter
Chapter 6: 6: Upgrading
Upgrading to Teamcenter
to Teamcenter RapidRapid
Start Start
Note the download location as you will need it later in this procedure.
The following table shows the paths for upgrading the Solid Edge Embedded Client (SEEC)
template.
Current Teamcenter Express

version Required SEEC template
5.3.x ST4 (SEEC 8.3)
b. In the Teamcenter Rapid Start version you are upgrading from (that is, your current
installation), open the Teamcenter Environment Manager.
c. In the Feature Maintenance panel, under Teamcenter Foundation, select Update

Database (Full Model – System downtime required) and click Next.
d. Browse to the Solid Edge template downloaded in step 2a.
3. In the Teamcenter Rapid Start 11.2 software distribution image, double-click the
UpgradetoTcRSUtility.bat file. To modify the configuration files, confirm the path of the
TC_ROOT directory for your installed version (for example, Teamcenter Express 5.3.x or
Teamcenter Express 9.1.x).
4. In the Teamcenter Rapid Start 11.2 software distribution image, double-click the tem.bat file.
5. Select the language for your installation and click OK.

Teamcenter Environment Manager (TEM) displays the Welcome to Teamcenter panel.
7. In the Install/Upgrade Options panel, click Upgrade.
8. In the Old Application Root panel, browse to the path of the application directory of the previous
installation and click Next.
9. In the Old Configuration panel, select the installation you want to upgrade and click Next.
10. In the Configuration panel, enter a unique ID and description for this software configuration.
The default ID and description values are copied from the configuration being upgraded.
Note
Record the description and ID you enter for this configuration. When uninstalling this
configuration or performing other maintenance tasks, you must select this configuration
from a list. In addition, installation log file names use this ID.
11. In the New Application Root panel, enter the installation directory for the new installation.
Verify that the status for all features is valid. If there are any warning messages, you must
resolve them before continuing.

Upgrading to Teamcenter Rapid Start
If TEM displays a warning message regarding a feature's XML file, click the feature and use the
Browse button to locate the XML file. Note that the feature's XML file may reside in a location
different from the corresponding Business Modeler IDE project location.
Note
If the custom template directory is on a shared network drive, make sure that you have
write permission to the shared path.
When upgrading to Teamcenter Rapid Start 11.2, you must first download the AutoCAD and
SEECOverlay templates from GTAC and then browse to them on the New Application Root
panel.
12. In the Operating System User panel, enter the operating system user name and password
for the user installing Rapid Start.
13. In the Flex License Server panel, enter a path for the licensing server in the Install UGS
Licensing to box.
In the Use License File box, enter the path to your Teamcenter license file.
Make sure the License Server Installer Location box contains the path to the installer for
the licensing server.
14. In the Teamcenter Administrative User panel, enter the Teamcenter user name and password.
15. In the Upgrade Information panel, enter the paths to the old TC_DATA and new TC_DATA
directories. Then, enter the user name and password for the Teamcenter database.
16. In the Upgrade Database Features panel, verify that the features you want to upgrade are
displayed. If all of the features are not displayed, click Browse to locate them.
17. In the the Upgrade Options panel, select one of the following:
• Stop database upgrade at first error
The upgrade stops when it encounters an error.
• Stop database upgrade after accumulating all errors

The database portion of the upgrade continues if it encounters an error. It creates a log file
that lists all errors that occurred.
Note
Siemens PLM Software recommends that you select this option only if you are
upgrading a test environment.
18. In the Password Security panel, enter the required values.
19. In the .NET Server Manager panel enter the required values or accept the default values shown.
If TEM displays an error message prompting you to change the pool port number, enter a
different port number.
20. In the .NET Web Tier panel, enter the required values.

Chapter
Start Start
21. In the Rich Client Settings panel, specify whether you want to install the help files locally, and
provide the URL to the Teamcenter online help.
22. In the Business Modeler IDE Client panel, select the Business Modeler IDE templates you want
to install. To install additional templates, click Browse and locate the desired templates.
23. In the the License Level for Teamcenter Visualization (Embedded) panel select the
appropriate licensing option.
24. Start the Teamcenter Express FSC service from your previous version before you continue.
25. In the Pre-Upgrade Diagnostics panel, specify a directory for storing the diagnostic log files,
and then click Run.
After the pre-upgrade diagnostics complete, click Review to see the results of the diagnostics.
Perform and recommended steps before you continue.
26. In Confirmation panel, review your selections.

If you want to change any settings before you begin upgrade, use the Back to return to previous
panels.
If you are satisfied with your selections, click Start to begin installing Teamcenter Rapid Start.
Note
If problems occur during upgrade, TEM displays a message that includes the path to the
log file that describes the problem.
27. If the upgrade is successful, TEM displays the Upgrade Features: Successful panel.
Close TEM .
28. Reapply any of the previously captured customizations.

Note
To upgrade additional databases using the same application root directory, run TEM from
the new, upgraded installation.
Upgrade Teamcenter Express client to Teamcenter Rapid Start

1. Save any customizations done in the existing TC_ROOT directory.
2. In the Teamcenter Rapid Start software distribution image, double-click the

UpgradetoTcRSUtility.bat file. To modify the configuration files, confirm the path of the
TC_ROOT directory for your current installed version, for example, Teamcenter Express 5.3.x or
Teamcenter Express 9.1.x.
3. In the Teamcenter Rapid Start software distribution image, double-click the tem.bat file.

The Welcome panel appears.


Teamcenter Environment Manager (TEM) displays the Welcome to Teamcenter panel.
7. In the Install/Upgrade Options panel, click Upgrade.
8. In the Old Application Root panel, browse to the path of the application directory of the previous
installation and click Next.
9. In the Old Configuration panel, select the installation you want to upgrade and click Next.
10. In the Configuration panel, enter a unique ID and description for this software configuration.
The default ID and description values are copied from the configuration being upgraded.
Note
Record the description and ID you enter for this configuration. When uninstalling this
configuration or performing other maintenance tasks, you must select this configuration
from a list. In addition, installation log file names use this ID.
11. In the New Application Root panel, enter the new installation directory.
12. If you are performing a two-tier client installation, type the host name of the server and the path
to the TC_DATA directory.
13. In the Rich Client Settings panel, specify whether you want to install the help files locally, and
provide the URL to the Teamcenter online help.
14. In the Teamcenter Visualization (Embedded) for Rich Client panel, click Next.
15. In the License Level for Teamcenter Visualization (Embedded) panel, select the license level.
16. If NX is installed on your host, verify the path to the installation directory and click Next.
17. In Confirmation panel, review your selections.

If you want to change any settings before you begin upgrade, use the Back to return to previous
panels.
If you are satisfied with your selections, click Start to begin installing Teamcenter Rapid Start.
Note
If problems occur during upgrade, TEM displays a message that includes the path to the
log file that describes the problem.
18. If the upgrade is successful, TEM displays the Upgrade Features: Successful panel.
Close TEM .
19. Reapply any of the previously captured customizations.

Chapter
Start Start
Note
To upgrade additional databases using the same application root directory, run Teamcenter
Environment Manager from the new, upgraded installation.
Upgrade Business Modeler IDE template project and code to

Teamcenter Rapid Start
When upgrading a Teamcenter Rapid Start environment with a custom Business Modeler IDE project,
you must manually migrate the Business Modeler IDE project before performing the upgrade.
1. Use the new version of Teamcenter Rapid Start to install a test system that represents your
existing customer production system, with no customizations. Include only Siemens PLM
Software-supplied features. You can add customizations in later steps.
For example, if the production system has only the foundation (corporate server) template and
customizations in the database, install the test system with only the foundation template of
the new version installed.
2. Install the Business Modeler IDE and dependent templates from the new version.
3. Import the customer template project created in the previous version into the new version of
Business Modeler IDE. To import a project, choose File→Import→Import Business Modeler
IDE Project wizard.
Importing the project upgrades the older customer template project elements into the new
version. Business Modeler IDE validates and loads the migrated customer template project. Any
loading or upgrade errors are displayed in the Console view.
After upgrade, open the Navigator view and check for any error or warning messages in the .log
file in the output\upgrade folder.
Note
If no migration is automatically initiated when the template project is imported, you must
manually initiate the migration.
4. Fix all errors displayed in the Business Modeler IDE Console view. After you fix the errors,
right-click the project and choose Reload Data Model to validate the custom data model. If any
errors occur after reloading the data model, redo this step until all errors are fixed.
5. Upgrade localizations.
a. After upgrading the older custom template to the newer data model, migrate the text for
properties and relations to the newer language framework using the Property Name and
Relation Name Migration Wizard.
b. Create a default set of localization files for the upgraded template project using the Default
Localization Creation Wizard.

Note
These steps migrate legacy display names from the text server into the Business
Modeler IDE. If you do not perform these steps, those properties assume the internal
names in the rich client and thin client.
6. In the Business Modeler IDE, view and evaluate the latest configurations added by each
dependent template in the new version. This allows you to determine the impact to your
configurations before you upgrade the system.
7. Some Teamcenter Rapid Start preferences are obsolete and are migrated to Business Modeler
IDE template elements. A list of preferences migrated to Business Modeler IDE elements is
provided in the Business Modeler IDE Guide.
8. Refactor create operations if they do not conform to the Teamcenter Rapid Start framework.
9. Configure your template to get the desired result in your system when your template is deployed
to the database.
10. Save changes in the customer template project along with the configurations made in the
previous version.
11. Regenerate code and recompile.
a. Regenerate the custom C++, Java, and .NET code to pick up the latest updates available
in the new version.
b. Compile and link the custom code with libraries of the new version installed in step a.
Caution
If you have any server code customizations from previous versions, you must
regenerate the code and rebuild your libraries.
12. Package the custom template project for testing by choosing New→Other→Package Template
Extensions.
The customer template is moved to the new version.
Caution
Some customizations depend on specific data in the database and cannot be used on
other databases until you create all the required data in the new database.
For example, any customization that involves the Organization module and has
customizations to display types is specific to a database. That template only works with a
database that has the same Organization structure for which the display type is set up.
For another example, if you create a custom Change Management object, it must be
configured with a workflow process template, which it gets from the database. The
template works in any database that also has the same process template.

Chapter
Start Start
Moving to Teamcenter
If you obtain a Teamcenter license file, you can convert a Teamcenter Rapid Start installation
to Teamcenter.
1. Launch Teamcenter Environment Manager in maintenance mode. In the Windows start menu,
click Programs→Teamcenter 11.2, and then right-click Environment Manager and choose
Run as administrator.
Note
You can also run the tem.bat file in the install directory in the application root directory for
the Teamcenter Rapid Start installation. Right-click the tem.bat program icon and select
2. In the Maintenance panel, select Move to Teamcenter.
3. In the Teamcenter Administrative User panel, enter the password for the Teamcenter Rapid
Start administrative user account.
The value in the User box is read-only during this step.
Caution
The password must not be empty nor contain any whitespace characters such as space,
tab, newline, carriage return, form feed, or vertical tab.
In addition, the password must not contain any of the following characters:
!@$%=&'":;.<>(){}
4. In the Configuration panel, if you want to enable all Teamcenter menus and applications for
the features installed in your configuration, select the Enable all the menus and applications
hidden by Teamcenter Rapid Start check box.
5. In the Confirmation panel, review your selections and click Start to convert your Teamcenter
Rapid Start configuration to Teamcenter.
When the conversion is complete, close TEM.

Chapter 7: Creating a custom distribution
Overview of custom distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Create a silent distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Create a silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Launch a silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Modify the silent installation configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Create a compact distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Chapter 7: Creating a custom distribution
Overview of custom distributions

Teamcenter supports the following custom distributions to simplify installation of Teamcenter on
multiple hosts.
• Silent distribution
A silent distribution is an XML-based configuration file you can use to install Teamcenter silently
(without user interaction) on another host. Silent installation suppresses most installation
prompts and requires minimal user interaction. As an alternative to installing and configuring
Teamcenter on individual hosts in your network, silent installation provides an efficient way to
deploy Teamcenter on multiple hosts in your network.
The silent installation configuration file records the selections and values you enter during a
Teamcenter installation and enables TEM to perform these steps noninteractively on other hosts.
You can modify a silent configuration file to change certain Teamcenter settings before installation.
Silent distributions are supported for Teamcenter servers, two-tier rich clients, and four-tier
rich clients.
• Compact distribution
A compact distribution is an installable package with a selected subset of Teamcenter client
features. It is much smaller than a full Teamcenter software distribution image and is more easily
distributed to multiple hosts in an organization.
A compact distribution is an alternative to installing Teamcenter from a full Teamcenter software
distribution image. A compact deployable package can contain a selected subset of Teamcenter
features rather than the entire set of features in the release. This reduces network loads
and simplifies large-scale Teamcenter deployments by providing an installation package that
is smaller and more easily distributed to an organization. For example, a two-tier rich client
installation can be packaged in a deployable media as small as 580 MB, where a full Teamcenter
distribution can require up to 5 GB. A four-tier rich client compact distribution can be as small as
283 MB, and a Client for Office compact distribution can be only 93 MB.
Compact distributions are supported for Teamcenter two-tier and four-tier rich clients.
Create a silent distribution

Create a silent installation configuration file
1. Log on to the Teamcenter corporate server host and browse to the root directory of the
Teamcenter software distribution image.
2. Start Teamcenter Environment Manager (tem.bat) from the Teamcenter software distribution
image.

Chapter
Chapter 7: 7: Creating
Creating a custom
a custom distribution
distribution
3. In the Welcome to Teamcenter panel, select Teamcenter.
4. In the Install/Upgrade Options panel, select the Create custom distribution check box,
and then click Install.
5. In the Custom Distribution Options panel, select Create silent configuration file, and then
specify the path to the silent installation file, for example, C:\silent.xml. The specified path must
be to an existing directory and the file name must end in .xml.
6. Proceed through the remaining panels to complete the Teamcenter installation.
Teamcenter Environment Manager creates the silent installation file you specified in step 5. This
file records your settings and selections during the installation. You can use this file to silently
install Teamcenter on another host with the same settings.
Caution
If you install a rich client silently using a compact distribution and your silent configuration
file requires features not included in the compact distribution, the silent installation fails. To
avoid this, make sure your silent configuration requires only features in the , or install using a
full Teamcenter software distribution image.
Launch a silent installation
To launch a , type the following command:
tem.bat -s file-name.xml
Replace file-name with the name of the silent installation configuration file.
After installation is complete, you can view a log of the installation in the installxxx.log file under the
install directory in the Teamcenter application installation directory.
Modify the silent installation configuration file
The silent installation configuration file is XML-based. After creating the file and establishing the file
structure using Teamcenter Environment Manager, you can change the installation by manually
modifying the values of the XML elements described in the following table.
Caution
Siemens PLM Software recommends using an XML editor to ensure well-formed XML code.
Do not change the XML structure of the file. If XML file structure is incorrect, or the XML code
is not well-formed, installation fails.
Element Description
features Lists all the Teamcenter modules and features to be installed. These
are selected on the Features panel of Teamcenter Environment
Manager.

Creating a custom distribution
Element Description
feature Specifies one feature of a Teamcenter module. The code attribute
identifies the feature. To define whether Teamcenter Environment
Manager installs the feature, set the selected attribute to either true
or false.
data Lists all Teamcenter Environment Manager Java classes and values
defining aspects of installation, such as the path to the installation
directory for Teamcenter application files. For additional information,
see the comments in the configuration file. The comments describe
the class and valid values.

Chapter
Creating a custom
distribution
<?xml version="1.0" encoding="UTF-8"?>

<root>
<tem engine="2008.0.0" />
<settings>
<installDir value="C:\\Program Files\\Siemens\\Teamcenter11" />
<sourceDir value="D:\\kits\\tc11.2\\win64" />
<application value="tceng" />
<silentMaintenance value="false" />
<installingUser value="osuser" />
<installLanguage value="ENGLISH" />
<aboutFullVersion value="11.2" />
<version value="11000.2.0.20150701" />
</settings>
<sourceLocations>
<coreLocations>
<directory value="D:/kits/tc11.2/win64" />
</coreLocations>
<browsedLocations />
</sourceLocations>
<config name="My Configuration 1" id="config1">
<mode type="install" clone="false">
<checkpoints>
<checkpoint value="featureProperties">
<point value="vcruntimes:vc2005,latest" />
<point value="minMSSQL2005Version:10.50" />
<point value="coreTemplate:foundation_template.xml" />
<point value="feature_id:datamodel,rtserver" />
<point value="vcruntimes:latest" />
<point value="template_file:foundation_template.xml" />
<point value="minDB2Version:9.7.4" />
<point value="minOracleVersion:11.2.0.1" />
<point value="template_name:foundation" />
<point value="typeAnalysis:true" />
</checkpoint>
</checkpoints>
</mode>
<comments />
<data>
<adminUser guid="2E53CFC3AC75665E50FF0F207D1D013B">
<password value="holrvg6fpj40nGt7ZlCM2Q" encrypt="true" />
<user value="infodba" />
</adminUser>
<director guid="661AA2A766CA975D998EBE61455F3EA3">
<saveStateOnFail value="true" />
<status value="0" />
<script>
<temBase />
<copyFeature name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<copyFeature name="Business Modeler IDE" feature="A9CECD82127A11DB9804B622A1EF5492" />
<copyFeature name="VC 2008 Redistributables" feature="DPBL8RC6MUS0LCPS10NIPGR85RI7HPHQ" />
<copyFeature name="Teamcenter File Services" feature="BC76F9D1AB7C93A848D0FE3602F59097" />
<copyFeature name="Flex License Server" feature="D1D683A8B2CE1EB821B97CD2EE5D7627" />
<copyFeature name="VC 2005 Redistributables" feature="UDR4NG0DEZ1TN9XHKG7Z8AFDPVVTZXL2" />
<copyFeature name="VC 2013 Redistributables" feature="NJCMQH3ZMYTPPPGA8BS4Q1C7OV6IXVXU" />
<copyFeature name="VC 2010 Redistributables" feature="R08U30BA5KZYSNDFKMGXKKHWEYOOVD7V" />
<copyFeature name="VC 2012 Redistributables" feature="Z9ICW073V9QXU4H5F8BK6CXG6KFYWBQZ" />
<copyFeature name="Business Modeler Templates" feature="A909338A1CB411DB8AF6B622A1EF5492" />
<copyFeature name="Digital Dashboard" feature="A9CECD82127A11DB9804B622A1EF5599" />
<copyFeature name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<copyFeature name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<copyFeature name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2
010FD613" />
<copyFeature name="Java EE Based Server Manager" feature="BF0E78AFE4280DCB08594EA2F3671BE8" />
.
.
.
<unpack name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<unpack name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<unpack name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<unpack name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2010FD
613" />
<preInstall name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<preInstall name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<preInstall name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<preInstall name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D20
10FD613" />
<install name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<install name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<install name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
Sample silent installation configuration file (Continued)

<install name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2010F

D613" />
<postInstall name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA52" />
<postInstall name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<postInstall name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<postInstall name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804EFB0D2
010FD613" />
<featureInstalled name="Microsoft Visual C++ Runtimes" feature="A0CF69C3A0BC61770EB81BD22667EA5
2" />
<featureInstalled name="FMS Server Cache" feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" />
<featureInstalled name="Teamcenter Foundation" feature="8C061DD51E13E0CB9DC4687B1A3348BE" />
<featureInstalled name="NX Part Family Classification Integration" feature="B176F6B6E9E91D9804E
FB0D2010FD613" />
</script>
</director>
<FSCService guid="F2FCBCEC03DFF7F9D1E3A11EC9B64BD2">
<fscReadCacheDir value="$HOME\\FSCCache" />
<fscWriteCacheDir value="$HOME\\FSCCache" />
<addToBootstrap value="true" />
<fscReadCacheSize value="10" />
<serverID value="FSC_tchost_osuser" />
<log value="" />
<fscWriteCacheSize value="10" />
</FSCService>
<FSCMasterSettings guid="EBC3422F77C6BF18FE0E3A821EFE1134">
<masterModel value="Simple Model" />
</FSCMasterSettings>
<FscSiteImport guid="630BECF927EC742A748A97486D5868DA">
<remoteSites value="" />
</FscSiteImport>
<tcdata guid="4500621E2BE24BF0DD6ABF31EBA01088">
<serverHostLocation value="tchost" />
<path value="C:\\Program Files\\Siemens\\tcdata" />
<create value="true" />
<shareName value="" />
<dsmKeyPath value="" />
</tcdata>
<FSCServiceFCCDefaults guid="7311DC5E94724BED0DD7419FCDE055CF">
<writeCacheSize value="1000" />
<readCacheSize value="1000" />
<cacheDirUnix value="/tmp/$USER/FCCCache" />
<partialReadCacheSize value="3000" />
<cacheDirWin value="$HOME\\FCCCache" />
</FSCServiceFCCDefaults>
<FccSite guid="35EE6A66B85467D5EDE5B3D91871EACE">
<siteListString value="" />
</FccSite>
<FSCServiceConnections guid="E4BDA0B521CB10A49F0CE123C9F326F1">
<connections value="http,4544,;" />
</FSCServiceConnections>
<OSUser guid="CA769D31FD7E122E5E509A0BBBD7E809">
<password value="+rfq6mTJVSuqaYJixkwntg" encrypt="true" />
<user value="DOMAIN\\osuser" />
</OSUser>
<flexClient guid="7221ECFBC9555CDF997FC3F575022761">
<nX5String value="28000@flexhost" />
<port value="27000" />
<nX4String value="27000@flexhost" />
<nX5Port value="28000" />
<host value="flexhost" />
<nX5Host value="flexhost" />
<nX5CheckBox value="true" />
<envServerString value="28000@flexhost" />
</flexClient>
<signatureCertificate guid="RRK3WTCSY4020QSZO90QFJWMISFAC2AX">
<replaceCerts value="false" />
<certificates value="" />
</signatureCertificate>
<foundationSettings guid="LHBY67ZYMYHSKED26FHDNDHFJTZD84I7">
<templatesToBeInstalled value="" />
<genClientCache value="generate all" />
<genServCache value="" />
<productionEnvironment value="true" />
<requestMetaCacheRebuild value="true" />
<enableGenServCache value="true" />
<quickClone value="false" />
</foundationSettings>
<transientVolume guid="983980098FF188A8C4BF08E8168A32A8">
<windowsVolume value="C:\\Temp\\transientVolume_tcdbuser" />
<unixVolume value="/tmp/transientVolume_tcdbuser" />
</transientVolume>
Sample silent installation configuration file (Continued)

Chapter
Creating a custom
distribution
<TcOracleSystem guid="1EF0859AC04962CBFA41C4C8C84499A1">
<password value="WsRDrEfD0/4vnLO0/mj2wA" encrypt="true" />
<user value="system" />
<tablespaces value="tcdbuser_IDATA:90;tcdbuser_ILOG:5;tcdbuser_INDX:5;tcdbuser_TEMP:5;tcdbuser_MM
V:5" />
<tablespacePath value="/db/oradata/tc/tcdbuser" />
</TcOracleSystem>
<security guid="ZUG63OE2YRNFD1VY13KCEZM52XFJP45D">
<adminDirectory value="$TC_ROOT\\security" />
</security>
<volume guid="1F16971107DE44C0C7827F800EE4AEF8">
<fscModel value="Simple Model" />
<location value="C:\\Program Files\\Siemens\\volume" />
<name value="volume" />
<hostName value="tchost" />
<fscId value="FSC_tchost_osuser" />
</volume>
<TcOracleEngine guid="F4F7C0852B27D6E56B8C64BE77FFA14C">
<createUser value="true" />
<host value="dbhost" />
<flush value="false" />
<populate value="true" />
<service value="tc" />
<uTF8Enabled value="true" />
<password value="AdxT7Jmz2/WbYF6O/eqX9g" encrypt="true" />
<user value="tcdbuser" />
<create value="true" />
</TcOracleEngine>
</data>
<features>
<add feature="A0CF69C3A0BC61770EB81BD22667EA52" name="Microsoft Visual C++ Runtimes" />
<add feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" name="FMS Server Cache" />
<add feature="8C061DD51E13E0CB9DC4687B1A3348BE" name="Teamcenter Foundation" />
<add feature="B176F6B6E9E91D9804EFB0D2010FD613" name="NX Part Family Classification Integration"
/>
</features>
</config>
<updateManager />
</root>
Sample silent installation configuration file
Create a compact distribution

Create a compact distribution, a Teamcenter installation package that contains selected features,
using Teamcenter Environment Manager (TEM).
1. Log on to the Teamcenter corporate server host and browse to the root directory of the
Teamcenter software distribution image.
2. Start TEM (tem.bat) from the Teamcenter software distribution image.
3. Proceed to the Install/Upgrade Options panel, select the Create custom distribution check
box, and then click Install.
4. In the Custom Distribution Options panel, select Create compact deployable media. Enter
the path in which to create the compact distribution and a file name for the package, for example,
C:\tc.zip.
The specified path must be to an existing directory and the file name must end in .zip.
5. Proceed through the remaining panels to complete the Teamcenter installation.

TEM creates the compact distribution file you specified in step 4. You can use this file to install
Teamcenter clients on other hosts.

Caution
If you create a silent installation using a compact distribution and your silent configuration file
requires features not included in the compact distribution, the silent installation fails. To avoid
this, make sure your silent configuration requires only features in the compact distribution, or
install using a full Teamcenter software distribution image.

Appendix A: Troubleshooting
Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Service log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
TEM reports invalid logon information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix A: Troubleshooting
Installation log files

The setup program generates multiple log files as it proceeds with installation or configuration. If a
problem occurs, monitor the displayed messages closely for information on which file to inspect for
error messages.
Log files generated by the Teamcenter Rapid Start setup program are stored under the
TC_ROOT\install directory. The log file is named install_TcRS_Configuration_xxxxxx.log.
In addition, a directory named logs contains files generated by auxiliary programs called by the
Teamcenter Rapid Start setup program. Most files have names of the form:
program-name.jnl
program-name.log
program-name.syslog
program-name.out
Of these files, the system log (.syslog) files usually contain the most relevant error data. If an
auxiliary program completes successfully, the syslog file is deleted automatically unless you set the
TC_KEEP_SYSTEM_LOG environment variable to any value prior to starting the installation.
If any problems are encountered during the installation, the Teamcenter Rapid Start setup program
stops and reports the name of the log file to be inspected.
The Teamcenter Rapid Start setup program reports the names of the log file and directory at the end
of the installation process. Following a successful installation, the system administrator can delete all
files under these directories.
Service log files

Log files generated by the Teamcenter File Services services are under the system root directory.
If the c:\temp directory exists, log files generated by the Multi-Site Collaboration ODS and IDSM
services are there; otherwise, they are in the system root directory. They have similar naming
conventions to the Teamcenter Rapid Start runtime log files.
TEM reports invalid logon information

During Teamcenter Rapid Start installation, when you specify the operating system user name and
password in the Operating System User panel, TEM may report the following error even though the
user credentials you enter are correct:
Invalid login information has been entered. Enter a valid password.
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows A-1

Appendix
Appendix A: A: Troubleshooting
Troubleshooting
To work around this issue for the duration of Rapid Start installation, perform the following steps to
temporarily change the Windows local group policy:
1. Click Start→Run, and then enter gpedit.msc.
2. In the Local Group Policy Editor, expand the Computer Configuration tree to the User Rights
Assignment item:
Computer Configuration→Windows Settings→Security Settings→Local
Policies→User Rights Assignment
a. Double-click Access this computer from the network. Add Everyone to the list of users
and groups granted access, and then click OK.
b. Double-click Deny access to this computer from the network. Remove Guest and
Everyone from the list of users and groups denied access, and then click OK.
These settings should allow you to complete Rapid Start installation. After Rapid Start installation is
complete, you may restore the previous local group policy settings.
If you do not want to change policies, change the logon credentials for the installation administrative
user before you proceed with Rapid Start installation.
Note
This workaround is suggested by the Microsoft Community site:

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/
logon-failure-the-user-has-not-been-granted-the/9cafeb92-ce7c-48d1-a286-f1202a5c8afb
A-2 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Appendix B: Uninstalling Teamcenter Rapid Start

Appendix B: Uninstalling Teamcenter Rapid Start
1. From the Start menu, choose Programs→Teamcenter 10→Environment Manager.
2. In the Maintenance panel, select Configuration Manager and then click Next.
3. In the Configuration Maintenance panel, select Remove configuration (uninstall) and then
click Next.
4. In the Old Configuration panel, ensure that the Teamcenter installation that you want to uninstall
is selected and then click Next.
5. In the Uninstall panel, select Yes and then click Next.
6. On servers only, in the Uninstall Teamcenter Foundation panel, you can select whether
or not you want to delete the TC_DATA directory, the database, and the volume during the
uninstallation. To delete them, select Advanced Uninstall Options, and then select REMOVE
database, TC_DATA and volume. Click Next.
The Teamcenter Visualization (Embedded) for Rich Client panel appears.
7. To uninstall Lifecycle Visualization when Teamcenter Rapid Start is uninstalled, select

Teamcenter Visualization is to be uninstalled.
If you do not select this option, Lifecycle Visualization is not uninstalled.
8. In the Confirmation panel, verify that the features you want removed are listed and then select
Start.
9. To view the details of the uninstall, click Show Details.
10. In the Uninstall Features panel, click Close.
11. Using Windows Explorer, delete the TC_ROOT installation directory.
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows B-1

Appendix C: Solutions and features reference
Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter Rapid Start solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Teamcenter Rapid Start features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Related topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Rich client solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6

Appendix C: Solutions and features reference
Solutions and features reference

Teamcenter Environment Manager (TEM) provides solutions and features you can include in
Teamcenter server or client configurations. The Web Application Manager provides rich client
solutions you can add to rich client distribution instance.
Teamcenter Rapid Start solutions

Solutions are preselected groups of features that provide starting points for recommended
Teamcenter configurations. You can add features or deselect features in the Features panel in
Teamcenter Environment Manager (TEM). For information about a solution, point to the solution
name in the list. TEM displays a description.
Solution Features
Corporate Server FMS Server Cache
Rich Client 2-tier Teamcenter Rich Client 2-tier
Rich Client 4-tier Teamcenter Rich Client 4-tier
Rich Client (2-tier and 4-tier) Teamcenter Rich Client (2-tier and 4-tier)
Business Modeler IDE Business Modeler IDE Standalone
Teamcenter Rapid Start features

TEM provides the following features and feature groups in the Features panel. Features are grouped
by related applications. For information about a feature, point to the feature name in the list. TEM
displays a description of the feature.
Note
• Some features are disabled because they require other features. To enable a feature,
select its prerequisite features. For information about feature prerequisites, see the
feature description.
• Some features cannot be installed in the same configuration, so selecting one disables
the other.
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows C-1

Appendix
Appendix C: C: Solutions
Solutions and features
and features reference
reference

Feature/Subfeature Description
Base Install Base Teamcenter server and client components.
Flex License Server Installs the license server for Teamcenter Rapid Start.
Business Modeler IDE Standalone Installs only the Business Modeler IDE client without requiring a connection to
a Teamcenter server.
Business Modeler IDE 2-tier Installs the two-tier Business Modeler IDE client. This client connects to
the Teamcenter server using IIOP.
Business Modeler IDE 4-tier Installs the four-tier Business Modeler IDE client. This client connects to a
Teamcenter server in a four-tier environment using HTTP.
Teamcenter Rich Client (2-tier and 4-tier) Installs a rich client that uses the communication infrastructure introduced in
Teamcenter 11.2.
This rich client is configurable for both two-tier and four-tier deployments. It
connects to the Teamcenter server (in a two-tier environment) or web tier
(in a four-tier environment) using Teamcenter client communication system
(TCCS). This differs from the existing two-tier rich client that connects directly
to the Teamcenter server using IIOP protocol, and the existing four-tier rich
client that connects directly to the Teamcenter web tier using HTTP protocol.
The newer TCCS-based rich client architecture provides the ability to stream
responses from the Teamcenter server (tcserver) to the client, an advantage
over the previous two- and four-tier architectures that required server
responses be completely prepared before sending.
This streaming is performed by a multiplexing proxy, or MUX, that is part of

Teamcenter Enterprise Communication System (TECS), a Java component
of the Teamcenter enterprise tier. The MUX supports four-tier communication
through its internal Jetty HTTP server, which services requests from the
Teamcenter web tier. The MUX communicates with the tcserver using
Teamcenter Transfer Protocol (TCTP).
Teamcenter Rich Client 2-tier Installs a Teamcenter two-tier rich client that communicates with the
Teamcenter corporate server using IIOP protocol. It supports most
Teamcenter features and does not require a web tier.
Note
IIOP-based communication in the two-tier rich client is deprecated

and will be removed in a future version of Teamcenter. Siemens
PLM Software recommends using the Teamcenter Rich Client
(2-tier and 4-tier) feature, which uses TCCS communication.
Teamcenter Rich Client 4-tier Installs a four-tier rich client that connects directly to the Teamcenter web tier
using HTTP protocol.
Note
This rich client is an alternative to the newer four-tier rich client

provided by the Teamcenter Rich Client (2-tier and 4-tier)
feature, which communicates with the Teamcenter web tier using
Teamcenter client communication system (TCCS).
Server Enhancements Additional features for Teamcenter servers.
C-2 Teamcenter Rapid Start Installation for Windows PLM00501 11.2


Java EE Based Server Manager Installs the process that manages the pool of Teamcenter server processes.
This option is applicable only when you are deploying the web tier. This
feature requires Teamcenter Foundation and FMS Server Cache features.
For a smaller site, you can install the server manager and Teamcenter servers
on the same host as the web tier application. For deployment options for
larger sites, you can install the server manager on a separate host.
Full Text Search Engine Installs Autonomy Intelligent Data Operating Layer (IDOL) server, the default
full-text search engine, and configures searching for the local database.
Autonomy IDOL enables users to retrieve objects from the Teamcenter

database based on search criteria. It allows users to specify searches on
metadata values, as well as full text retrieval searches on both metadata and
common forms of text data.
IDOL works with the IDOL server, DiSH server and File System Fetch as three
services installed. The IDOL installer does not support the silent install option.
Teamcenter Management Console Installs Teamcenter Management Console, an SSL-secured console for
managing and monitoring server-side components such as the Java EE
server manager and Java EE web tier. The console's tabbed interface
resembles a web application server console. Teamcenter administrators
can use the console to access multiple Teamcenter management features
from a single page.
Teamcenter Security Services Configures Security Services for Teamcenter. These services eliminate
prompts for logon credentials when users switch Teamcenter products within
a user session.
Prerequisite:
Installation and configuration of Security Services.
Required information:
• Application ID for this instance of Teamcenter in the Security Services

application registry.
• Complete URL of the Security Services logon Service web application.
• Complete URL of the Security Services Identity Service web application.

Database Daemons Optional database support services.
Action Manager Service Monitors the database for the creation of action objects and dispatches
events that have a specific execution time and events the Subscription
Manager daemon fails to process.
Installing the Action Manager service is required to enable the rich client
Subscription Monitor application.
Subscription Manager Service Monitors the database event queue for the creation of subscription event
objects.
Installing the Subscription Manager service is required to enable the rich

client Subscription Monitor application.
Task Manager Service Checks user inboxes for tasks that have passed due dates, notifies the
delegated recipients, and marks those tasks as late.
Installing the Task Monitor service is required to enable notification of late

tasks.

Appendix
reference

Tesselation Manager Service Tessellates UGMASTER and UGALTREP datasets to the JT (DirectModel)
dataset and attaches the JT dataset back to the item revision and
UGMASTER and UGALTREP dataset.
Installing the Tessellation service is required to create the tessellated

representations in Repeatable Digital Validation (RDV) that enable users of
the DesignContext application to quickly visualize components in context.
The tessellated representations are created during the workflow release
process, ensuring that JT files of the DirectModel datasets are updated
as the NX files are released.
File Management File management features.
FMS Server Cache Installs the File Management System FSC server and file caches. You must
install an FSC server on each host that runs a server manager and on each
host that is to provide volume services.
You can optionally choose to install the FSC as a configuration server or a

performance cache server.
Teamcenter Web Tier Features to support the Teamcenter .NET web tier.
Web Tier for .NET Installs the middle tier processes that communicate with Teamcenter server
processes.
Extensions Extensions to Teamcenter server and client functionality.
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.
Enterprise Knowledge Foundation Enterprise Knowledge Foundation features.
Teamcenter Client for Microsoft Office Installs the Teamcenter Client for Microsoft Office.
Dispatcher Client for Rich Client Installs Dispatcher Client for the rich client. This feature requires Teamcenter
Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Render Document for Rich Client Provides Render Management capabilities for the rich client. This feature
requires Dispatcher Client for Rich Client.
For information about installing Dispatcher features require installing and

configuring file translators for the Dispatcher Server.
Dispatcher Server Installs the following Dispatcher Server components: scheduler, module and
administration client.
Dispatcher Client Installs an integration of the Dispatcher Server and Teamcenter that enables
rich client users to translate Teamcenter data files to various visualization
format for viewing in Teamcenter.
Lifecycle Visualization Features to support Lifecycle Visualization.
Teamcenter Visualization (Embedded) for Installs the embedded viewer for the rich client. This feature requires
Rich Client Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Localization Features that support localization of Teamcenter.
Classification L10N Installs the classification localization template, which enables localization in
the Classification environment.
Note
The classification localization template is not supported with IBM

DB2 databases.
Mechatronics Process Management Features to support Mechatronics Process Management.


EDA Server Support Installs the dataset types and transfer modes required to support Teamcenter
EDA, the application that integrates ECAD applications with Teamcenter.
EMPS - Foundation Installs electronic design and manufacturing types to support ECAD
translation and PCB design collaboration using Teamcenter embedded
viewer.
ECAD Part Library Management Installs ECAD part types to support ECAD part library management.
Platform Extensability Platform extensability features.
Global Services Global Services features.
Multisite Collaboration IDSM Service Installs the distributed services manager (IDSM) required to replicate data
between multiple Teamcenter sites, enabling the exchange of data objects
with other Teamcenter databases over a wide area network (WAN).
Multisite Collaboration ODS Service Installs the object directory service (ODS) required to replicate data between
multiple Teamcenter sites, enabling the exchange of data objects with other
Teamcenter databases over a wide area network (WAN).
Portfolio, Program and Project Management Portfolio, Program and Project Management features.
Workflow to Scheduling Integration Allows workflow to send updates to the related tasks in a schedule.
This feature requires a four-tier installation and Dispatcher to be
installed/configured.
Note
This feature also requires the Schedule Manager translator

(SchMgrTrans).
Supplier Relationship Management Supplier Relationship Management features.

Vendor Management Installs the optional Vendor Management solution.
Systems Engineering and Requirements Features that support Systems Engineering and Requirements Management.
Management
Teamcenter Extensions for Microsoft Office Installs Teamcenter Extensions for Microsoft Office.
Teamcenter Integration for NX Teamcenter Integration for NX features.
Installs core functionality of Teamcenter Integration for NX. This feature
requires a local installation of NX.
Teamcenter Integration for NX is a data management tool used with NX.

When you use NX with this integration, Teamcenter runs at the same time as
a separate process, enabling NX and Teamcenter to communicate so you
can create, store, and access your NX data within a Teamcenter database.
For information about using Teamcenter Integration for NX, see Teamcenter
Integration for NX in the NX help collection.
NX Foundation Installs default data types and loads template NX data to support , the
Teamcenter integration with Siemens PLM Software NX provided through
NX Remote Manager.
NX Rich Client Integration Installs Teamcenter Integration for NX for the rich client. This feature requires
Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Related topics
• Managing variability of your entire product suite

Appendix
reference
Rich client solutions

You can add rich client solutions to a rich client distribution instance. These solutions add functionality
to the four-tier rich client installed using the Over-the-Web Installer.
Solution Description
Over-the-Web Installer Installs the program that installs the rich client over the web.
This solution is required.
Microsoft Visual C++ Installs the Microsoft Visual C++ libraries required for the rich
2005/2008/2010/2012 client and for the FMS client cache (FCC).
Redistributables
Teamcenter client Installs Teamcenter client communication system (TCCS).
communication system
TCCS contains the FMS client cache (FCC), which uploads files
from a Teamcenter client workstation to a Teamcenter volume
and also downloads requested files from the volume to a client
workstation. An FCC provides the following advantages:
• Improved file transfer performance
• File streaming
Installing an FCC supports the Lifecycle Visualization file

streaming technology, which downloads portions of JT files
over the network as they are needed and improves network
performance.
Teamcenter Client for Microsoft Installs Teamcenter Client for Microsoft Office, which provides
Office the capability to manage Teamcenter workspace objects in real
time. Client for Office provides access to Teamcenter objects
directly through Microsoft Office Word, Excel, PowerPoint,
and Outlook in Microsoft Office. This solution adds a custom
Teamcenter ribbon to Microsoft Office applications.
Rich Client 4-Tier Installs the rich client software required for the four-tier
architecture. This solution is required.
Dispatcher Client for Rich Installs Dispatcher Client for the rich client.
Client
NX Manager for Rich Client Configures the rich client to use Teamcenter Integration for NX
4-Tier or NX Integration, the application that integrates Teamcenter
with NX. Separate installation of the Teamcenter Integration for
NX or NX Integration executables is required (as part of NX
installation). This solution is optional.
Teamcenter Applications for Installs Teamcenter Extensions for Microsoft Office and the
Microsoft Office Teamcenter Plugin for Microsoft Project, which allows Microsoft
Project users to exchange data directly with Schedule Manager.
Separate installation of Microsoft Office is required.
Teamcenter Rapid Start Client Installs Teamcenter Rapid Start features for the rich client.
Teamcenter Visualization Configures the rich client to use the embedded viewer when
(Embedded) for Rich Client Teamcenter lifecycle visualization is separately installed on the
4-Tier client workstation. This solution is optional.

Appendix D: Configure online help access

Appendix D: Configure online help access
To configure Teamcenter online help after Teamcenter installation, or to change online help access for
Teamcenter Rapid Start clients, perform the following procedures where appropriate.
• Four-tier rich client installed through TEM
To configure online help for a Teamcenter rich client you installed using TEM (not using the
Over-the-Web Installer), set the following preferences.
Preference Value
WEB_core_help_server http://host:port/tdoc/tc/version/help/
Documentation Server. version is the Teamcenter
version or SP level. For example:
http://myhost:8181/tdoc/tc/11.2/help/
WEB_help_server http://host:port/tdoc/tc/version/help/
#filename:thin_client_dhtml:getting_started
Documentation Server. version is the Teamcenter
version or SP level.
This preference specifies the location of the thin
client online help. The part of this value preceding
the hash symbol (#) should match the value of the
WEB_core_help_server preference.

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

Appendix
Appendix D: D: Configure
Configure online
online help help access
access
Next, in the Rich Client Settings panel, select the Enable Online Help check box, and then
type the online help URL in the Web server URL box.
Note
Alternatively, you can configure online help for a two-tier rich client by setting the following
values in the site_specific.properties file for on the rich client host.
Property Value
portalHelpWebServer http://
This value specifies the protocol for online help access.

portalHelpPage host:port/tdoc/tc/version/help/
host and port are the host name and port of the PLM Documentation
Server. version is the Teamcenter version or SP level. For example:
myhost:8181/tdoc/tc/11.2/help/
• Rich client distribution instance

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

Configure online help access
Context parameter Value

RichClientHelpWebServer http://host:port/tdoc/tc/version
or SP level.
RichClientHelpLocation /help
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows D-3

Appendix E: Installing the Full Text Search option

Appendix E: Installing the Full Text Search option
The Full Text Search option installs the Teamcenter Rapid Start full text search engine. The full text
search engine enables users to retrieve objects from the Teamcenter Rapid Start database based on
search criteria. It allows users to specify searches on metadata values, as well as full text retrieval
searches on both metadata and common forms of text data.
This option is available when you perform a custom installation. You can also use Teamcenter
Environment Manager to add this feature after the installation in complete. Before you install or
configure the full text search engine, you must install Teamcenter Rapid Start.
1. Launch Teamcenter Environment Manager in maintenance mode. In the Windows start menu,
click Programs→Teamcenter 11.2, and then right-click Environment Manager and choose
Note
You can also run the tem.bat file in the install directory in the application root directory for
the Teamcenter Rapid Start installation. Right-click the tem.bat program icon and select
2. In the Maintenance panel, select Configuration Manager.
3. In the Configuration Maintenance panel, select Perform maintenance on an existing

configuration.
4. In the Old Configuration panel, select the installation to which you want to add the full text
search feature.
5. In the Feature Maintenance panel, select Add/Remove Features.
6. In the Features panel, under Server Enhancements, select the Full Text Search Engine
feature.
Note
If TEM cannot find one of the software media locations specified during the initial
installation or in a previous patch, TEM may display the Media Verification panel, in
which to can verify or update the locations of Teamcenter Rapid Start software distribution
images.
7. In the Teamcenter Administrative User panel, enter the password for the Teamcenter Rapid
Start administrative user account.
The value in the User box is read-only during this step.
PLM00501 11.2 Teamcenter Rapid Start Installation for Windows E-1

Appendix
Appendix E: E: Installing
Installing the Text
the Full Full Search
Text Search option
option
Caution
The password must not be empty nor contain any whitespace characters such as space,
tab, newline, carriage return, form feed, or vertical tab.
In addition, the password must not contain any of the following characters:
!@$%=&'":;.<>(){}
8. In the Full Text Search panel, enter settings for the full text search feature:
Box Description
DISH Service Configuration
ACI Port Specifies the number of the port on which Autonomy
Content Infrastructure (ACI) sends action commands to
the Autonomy server (Suir).
The default value is 20000.
Service Port Specifies the service port number.
IDOL Service Configuration
Index Port Specifies the number of the port on which the search
engine is to perform indexing.
File System Fetch Service Configuration
9. In the Confirmation panel, review your selections and click Start to convert your Teamcenter
Rapid Start configuration to Teamcenter.
When the installation is complete, close TEM.
E-2 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Siemens Industry Software
Headquarters
Europe
Granite Park One
Stephenson House
5800 Granite Parkway
Sir William Siemens Square
Suite 600
Frimley, Camberley
Plano, TX 75024
Surrey, GU16 8QD
USA
+44 (0) 1276 413200
+1 972 987 3000
Asia-Pacific
Americas
Suites 4301-4302, 43/F
Granite Park One
AIA Kowloon Tower, Landmark East
5800 Granite Parkway
100 How Ming Street
Suite 600
Kwun Tong, Kowloon
Plano, TX 75024
Hong Kong
USA
+852 2230 3308
+1 314 264 8499
About Siemens PLM Software
© 2015 Siemens Product Lifecycle Management

Siemens PLM Software, a business unit of the Siemens
Software Inc. Siemens and the Siemens logo are
Industry Automation Division, is a leading global provider
registered trademarks of Siemens AG. D-Cubed,
of product lifecycle management (PLM) software and
Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,
services with 7 million licensed seats and 71,000 customers
Parasolid, Solid Edge, Teamcenter, Tecnomatix and
worldwide. Headquartered in Plano, Texas, Siemens
Velocity Series are trademarks or registered trademarks
PLM Software works collaboratively with companies
of Siemens Product Lifecycle Management Software
to deliver open solutions that help them turn more
Inc. or its subsidiaries in the United States and in other
ideas into successful products. For more information
countries. All other trademarks, registered trademarks
on Siemens PLM Software products and services, visit
or service marks belong to their respective holders.
www.siemens.com/plm.

Rapid Start Installation Windows

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Rapid Start Installation Windows

Загружено:

Авторское право:

Доступные форматы

SIEMENS

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

Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter Rapid Start server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Preinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing the Java EE web tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

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

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 3

Installing the Java EE server manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Gather required information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Teamcenter Rapid Start client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Prepare the Rapid Start client host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Upgrading to Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Creating a custom distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Overview of custom distributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Installation log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Uninstalling Teamcenter Rapid Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Solutions and features reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Configure online help access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

4 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Installing the Full Text Search option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Four-tier architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Rich client optional parameter values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 5

Teamcenter clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter network architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter Rapid Start installation components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Teamcenter Rapid Start installation quick start . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . 1-12

Installing Teamcenter help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows

Teamcenter network architectures

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 1-1

1-2 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

• A separate TreeCache cluster for each environment.

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 1-3

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

1-4 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 1-5

1-6 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Four-tier deployment (load balancing)

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 1-7

The two-tier architectural model comprises the following tiers:

The client tier comprises the Teamcenter rich clients.

The two-tier rich client is installed only through TEM.

1-8 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Teamcenter Rapid Start installation components

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 1-9

Server component Description

1-10 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

Server component Description

Client component Description

The CAD applications must be installed prior to

PLM00501 11.2 Teamcenter Rapid Start Installation for Windows 1-11

Teamcenter Rapid Start installation quick start

• A supported database server

• A supported version of the Java runtime environment (JRE)

Step 2: Install the Teamcenter Rapid Start server

• Installs a license server.

• Installs an administration client for system administration tasks.

1-12 Teamcenter Rapid Start Installation for Windows PLM00501 11.2

• Creates a network share to the configuration directory (accessible as \\SERVERNAME\tc_data)