Professional Documents
Culture Documents
Teamcenter - Installation On UNIX and Linux Servers Guide - PLM00011 J
Teamcenter - Installation On UNIX and Linux Servers Guide - PLM00011 J
Publication Number
PLM00011 J
Proprietary and restricted rights notice
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Install the Manufacturing Resource Library . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Planning data migration from Genius4000 to Resource Manager . . . . . . . . . . 12-2
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting Teamcenter server installation . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting four-tier architecture deployment . . . . . . . . . . . . . . . . . . . . . A-6
Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Troubleshooting document rendering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Troubleshooting Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . A-14
Recovering from a corrupted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
Tables
This guide describes how to install Teamcenter 10.1 on UNIX and Linux servers.
This includes installation of Teamcenter servers using Teamcenter Environment
Manager and the Teamcenter Web tier using the Web Application Manager.
This guide assumes you have a thorough working knowledge of your operating
system and general knowledge of Teamcenter use.
1 Getting started
1 Getting started
Getting started
Verify you have installed supported versions of all prerequisite software and plan
your Teamcenter network before you begin installing servers.
System requirements
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
Note Some software requirements differ for non-English locales. When viewing
the certification database, make sure you note any exceptions for your locale.
Platforms
Determine from the following table which Teamcenter 10.1 servers and clients are
supported on your operating system. Bullet characters (•) denote supported servers
and clients.
Business
Modeler
Corporate Web Rich Thin IDE
Operating System server tier client client client TCCS1
Microsoft Windows • • • •
(desktop platforms)2
Microsoft Windows • • •
(server platforms)3
Sun Solaris • •
Hewlett-Packard HP-UX4 • •
IBM AIX • •
SUSE Linux • • • • • •
Red Hat Linux5 • • • • • •
Apple Macintosh Mac OS • •
• If your Teamcenter database server is IBM DB2, all Teamcenter servers and
two-tier rich clients in your network must run operating systems supported
for Teamcenter with IBM DB2. IBM DB2 databases are supported only
with Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE
Linux platforms.
Sun Solaris
1. Teamcenter client communication system (TCCS) is installed with the rich client. This column refers to the stand-alone TCCS
application.
2. Microsoft Windows desktop platforms include Windows XP and Windows 7.For information about installing Teamcenter on Windows
clients, see the Installation on Windows Clients Guide.
3. Microsoft Windows server platforms include Windows Server 2008.
4. Itanium platforms only. PA-RISC hardware is not supported.
5. Only 64-bit Red Hat Linux is supported.
Hewlett-Packard HP-UX
• Teamcenter is supported on HP-UX on Itanium platforms only.
http://www.hp.com/go/hpux-java-docs
IBM AIX
• The 64-bit IBM AIX platform is supported for Teamcenter server processes.
Linux
• Make sure Linux host names do not exceed 31 characters in length. Host
names longer than 31 characters cause Teamcenter corporate server
installation to fail during saving of the POM schema file in the TC_DATA
directory.
Note Teamcenter installation tools do not require fully qualified domain
names for host names. If your fully qualified domain name exceeds
31 characters, use the server short host name instead.
For more information, see the GTAC solutions document
002-7004480 on GTAC.
• On Linux systems, make sure your system is set to use the ISO8859-1
character set rather than the default UTF-8 character set. Teamcenter
installation tools require this setting.
System hardware
Make sure your Teamcenter host has the required amount of disk space available.
Required hard disk space for Teamcenter configurations shows the required disk
space for the following common Teamcenter configurations:
• Corporate server
The corporate server contains the features included in the Corporate Server
solution in Teamcenter Environment Manager (TEM). Additional features may
require additional disk space.
For more information, see Install a Teamcenter corporate server.
The two-tier rich client contains the features included in the Rich Client 2-tier
solution in Teamcenter Environment Manager (TEM). Additional features may
require additional disk space.
For more information, see the appropriate Teamcenter client installation guide
(for Windows or Linux).
• Web tier
The Web tier includes the Web Application Manager, a distribution server, and a
distribution server instance that contains the Over-the-Web installer and Rich
Client 4-tier solutions. Additional solutions may require additional disk space.
For more information, see J2EE Web tier installation.
Database
Teamcenter requires a relational database management system (RDBMS) for storing
Teamcenter data. Before you install a Teamcenter, you must install an IBM DB2
or Oracle database server and make sure your Teamcenter corporate server host
has access to the server.
For information about supported database server versions, see the certification
database:
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
Choose a database management system that suits the platforms of your Teamcenter
servers and clients. When planning your network, consider the following limitations:
• Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannot
connect to Microsoft SQL Server database servers.
• If your Teamcenter database server is IBM DB2, all Teamcenter servers and
two-tier rich clients in your network must run operating systems supported
for Teamcenter with IBM DB2. IBM DB2 databases are supported only with
For information about installing a database server for Teamcenter, see Oracle
installation and configuration or IBM DB2 installation and configuration.
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
TEM verifies the required version of Java is available on the host. If the required
version is not present, TEM does not launch.
Before you launch TEM to install Teamcenter, specify the location of the JRE by
one of the following methods:
• Set the appropriate environment variable on your host:
o 32-bit Java
Set the JRE_HOME environment variable to the location of the 32-bit Java
JRE.
o 64-bit Java
Set the JRE64_HOME environment variable to the location of the 64-bit
Java JRE.
Note You must use the appropriate Teamcenter software distribution image
(32-bit or 64-bit) for the JRE you use.
• Use the -jre argument to specify the JRE location when you launch TEM from a
command prompt:
tem —jre JRE-path
For example:
tem –jre c:\apps\jre1.7
TEM stores the JRE location during Teamcenter installation. After installation is
complete, TEM no longer requires the JRE_HOME or JRE64_HOME environment
variable or the -jre argument.
Web browser
The Teamcenter thin client and Over-the-Web Installer7 require a Web browser.
Teamcenter 10.1 supports the following Web browsers:
• Windows systems: Microsoft Internet Explorer and Mozilla Firefox
• Linux systems: Mozilla Firefox
• Macintosh systems: Apple Safari
For information about versions supported, see the Siemens PLM Software
Certification Database.
Software integrations
If you use Teamcenter 10.1 integrations to other Siemens PLM Software products or
third-party software, install those products before you install Teamcenter 10.1.
Some Siemens PLM Software products require separate licenses from your Siemens
PLM Software representative. Siemens PLM Software products are licensed using
the Siemens PLM Software Common Licensing Server.
For more information about the Common Licensing Server, see Install the licensing
server.
7. The Over-the-Web Installer installs the four-tier Teamcenter rich client and Teamcenter Microsoft Office interfaces.
Note • Teamcenter software distribution images can contain multiple ZIP files.
For example, the software distribution image for Windows consists of
two files named Tcn_win_1_of_2.zip and Tcn_win_2_of_2.zip. If
you download software distribution images for Teamcenter, you must
download all files in the set to obtain the complete image. After you
download files, extract all ZIP files to a common directory to assemble
the image before you begin installation.
8. You create this directory when you install the Web Application Manager as described in J2EE Web tier installation.
Database server
A Teamcenter network requires access to a database server.
Before you install Teamcenter, you or your database administrator must install and
configure a database server to store Teamcenter data. The Teamcenter corporate
9. A deployable file is a Web archive (WAR) or enterprise archive (EAR) file, depending on the solutions it contains.
Teamcenter servers
You can install different types of Teamcenter servers according to the features you
use and your load distribution needs.
Corporate server
A Teamcenter corporate server installation includes the following components:
• Teamcenter shared binary executables and files
• Teamcenter shared data subdirectories and files
• Database connection
• Teamcenter volume
• Additional optional Teamcenter features such as File Management System (FMS)
Additional servers
A Teamcenter network requires one corporate server configuration. Additional
servers are optional, but can help balance network loads and facilitate heterogeneous
networks (networks with hosts running different operating systems).
Teamcenter clients
Teamcenter provides clients suited to various uses and network configurations.
These clients include the rich client, the thin client, and specialized clients such as
Teamcenter Client for Microsoft Office and Teamcenter Extensions for Microsoft
Office.
Rich client
The rich client is a platform-independent client implementation (Java application)
for users who interact with Teamcenter frequently. It is extendable and able to run
both Teamcenter and customer-written applications. Customers can also extend the
standard user interface.
The rich client application is deployed on each user workstation using Teamcenter
Environment Manager or the Over-the-Web Installer, depending on which
Teamcenter network architecture you use. The rich client is supported in both
architectural models described in Two-tier architecture and Four-tier architecture.
Thin client
The thin client provides access to Teamcenter through a standard commercial Web
browser, such as Microsoft Internet Explorer or Mozilla Firefox. The user interface
provides a streamlined browser-based view of product information stored in a
Teamcenter database.
The thin client is supported only in the four-tier architectural model described in
Four-tier architecture.
Two-tier architecture
• 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.
For more information about FMS and two-tier rich client architecture, see File
Management System installation.
Two-tier deployment
Four-tier architecture
The four-tier architecture model comprises the following tiers:
• Client tier
The client tier comprises the Teamcenter rich client, thin client, and other clients
such as Teamcenter 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.)
For information about the functionality you can add, see Rich client
installation.
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
• 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.
Note Teamcenter provides server managers based on the J2EE and the
Microsoft .NET platforms. The .NET Web tier is supported only on
Windows platforms.
• Resource tier
The resource tier comprises a database server, database, volumes, and file
servers.
Four-tier architecture
You can design deployments that host the Web tier, resource tier, and enterprise
tiers on the same computer or on separate computers:
• Smaller sites can run the pool of servers and the server manager on the same
host as the Web tier.
• Larger sites can distribute the pool of server processes across multiple hosts
and optionally include an HTTP server to serve static files or multiple HTTP
servers to support load balancing.
For a multihost configuration, the server pool consists of multiple subpools, one
or more for each host. Each subpool is managed by one server manager process.
The Web tier balances the load across the server pools.
The Teamcenter J2EE based server manager and Web tier application both employ
the JBoss cache, a tree-structured cache, to provide replication and transaction
context. You must configure the JBoss cache (called TreeCache in Teamcenter) in
both the J2EE based server manager and the Web tier application.
To ensure communication between the Web tier and the server manager, you must
coordinate the values you specify for each component. For some values, you must
provide the identical value when configuring the Web tier application.
If you are setting up multiple Web tier environments with separate domains, you
must configure:
• A minimum of one server manager for each Web tier deployment.
The JMX HTTP adapter allows you to view the status of the server pool and
dynamically alter the pool configuration values (the values are not persistent).
Access this functionality from the following URL:
http://host-name:jmx-port
Replace host-name with the name of the host running the server manager. Replace
jmx-port with the number of the port running the JMX HTTP adapter. This port
number is defined when you install the J2EE based server manager.
The first time you log on to the adapter, use manager for both the user name
and the password. You can change the user name and password to unique values
using the adapter.
Teamcenter File Management System (FMS) 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.
Four-tier deployment (enterprise and Web tiers on separate hosts with HTTP server)
Four-tier deployment (multiple enterprise tier hosts and Web tier hosts)
Install the J2EE Web tier as described in J2EE Web tier installation.
2 Site planning
2 Site planning
Site planning
Plan your Teamcenter network and identify software issues that may affect your
installation.
1. Teamcenter provides server managers based on the J2EE and the Microsoft .NET platforms. The .NET Web tier is supported
only on Windows platforms.
The following table describes additional network nodes you can include in your
network.
2. Install Teamcenter executables and files, create and/or populate the database,
and configure a volume using Teamcenter Environment Manager.
For the installation procedures, see Teamcenter server installation.
3 Exe - portal
Installed
by TEM
Implementation Repository
Exe - start_imr
Teamcenter Files
Teamcenter
Server Installed at TC_ROOT
Exe - start_TcServer1
Corporate server installation
using Teamcenter Environment
Manager.
Database
Server
1
Database
2. Install the enterprise tier using Teamcenter Environment Manager, being sure
to choose the server manager component.
Teamcenter Environment Manager installs the pool of Teamcenter servers and
the server manager, creates and or populates the database, and configures a
volume.2
For the installation procedures, see Teamcenter server installation.
2. Teamcenter provides server managers based on the J2EE and the Microsoft .NET platforms. The .NET Web tier is supported
only on Windows platforms.
3. Generate the J2EE Web tier as an enterprise archive (EAR) file using the Web
Application Manager and deploy the EAR file in a J2EE application server.
Note The thin client is installed as part of the Web tier for access by clients.
4. Install a third-party application server and deploy the Teamcenter EAR file.
5. If you are deploying the rich client, deploy the Over-the-Web Installer and
configure a rich client for installation.
For an overview, see Rich client installation.
For the installation procedures, see Installing rich client Web applications.
6. Install the rich client on a client workstation using the Over-the-Web Installer.
For the installation procedures, see either the Installation on Windows Clients
Guide or Installation on Linux Clients Guide.
Note The automatic logon feature is not supported in four-tier Teamcenter
deployments.
For more information about the automatic logon feature, see the Preferences
and Environment Variables Reference.
tc.ear
TC Server n+2
Exe - tcserver
TC Server n+1
Teamcenter Servers and
Exe - tcserver Server Manager installed using
Teamcenter Environment Manager (TEM)
1 Database
Database Server
The Teamcenter rich client is a Java application that runs on client hosts. The
two-tier rich client is installed on each client host using a stand-alone instance of
Teamcenter Environment Manager. The four-tier rich client is installed using a
distributed instance of the Over-the-Web Installer.
To install the two-tier rich client, you launch Teamcenter Environment Manager on
your client host, select the client components you want to install, and then proceed
with installation.
To install the four-tier rich client, you use a Web browser open the URL of a
Web application server that serves the Over-the-Web Installer. The four-tier rich
client installs silently, with no prompts. Teamcenter administrators configure
all installation options and provide all the information necessary to complete
installation using Web Application Manager.
To enable over-the-Web installation for the four-tier rich client, you install the
following components on a server host.
• A rich client distribution server.
The distribution server software manages the connection between a rich client
distribution instance and the Over-the-Web Installer. The Over-the-Web
Installer contacts the distribution server for the rich client files to download to
the user’s workstation.
Only one rich client distribution server is required to manage multiple rich
client distribution instances.
After you install and deploy a rich client distribution server and distribution
instances, you can change the distribution server contents, add components to
a distribution instance, and patch components in a distribution instance using
Web Application Manager. The next time users start a rich client installed from
that distribution instance, the rich client startup process checks for updates and
downloads them to the client hosts.
installing.html
otw_installer.jar
Uses - instance = "web application name" Check that client
server_name = "hostname:rmi port" installed is current
and install or update.
Example - instance = "Teamcenter 2 Tier OTW
server_name = "hostname:12001"
Distribution Server
Exe - start_server
Uses - webapps.dat
RMI
Created by Web application manager
Exe - start_rmi
using 'Distribution Server'
When you choose this option, the rich client is enabled to launch Teamcenter
lifecycle visualization. Users must independently install Teamcenter lifecycle
visualization executable files on the client hosts. All client hosts installing a
distribution instance must have Teamcenter lifecycle visualization installed
in the same location.
Note The Teamcenter lifecycle visualization integration requires the
presentation tier application, a component of the four-tier architecture.
To enable Teamcenter lifecycle visualization for a two-tier rich client,
you can connect the two-tier rich client either to a deployment of the Web
tier or to a deployment of the presentation tier application.
• Remote workflow
When you choose this option, the rich client is enabled to support the linking of
objects between Teamcenter and other applications such as Teamcenter portfolio,
program and project management. Separate installation of remote workflow
components and Teamcenter Application Registry are required.
• Teamcenter EDA
When you choose this option, the rich client is configured for use with
Teamcenter EDA.
• SCM ClearCase
When you choose this option, the executable files are included in the distribution
instance for the integration between Teamcenter and the IBM Rational
ClearCase software configuration management (SCM) tool.
For a complete list of available Teamcenter features for the rich client, see Solutions
and features reference.
For information about creating, deploying, and updating the rich client distribution
server and rich client distribution instances, see Installing rich client Web
applications. Instructions for installing the rich client over the Web on a client host
are in the Installation on Linux Clients Guide and the Installation on Windows
Clients Guide.
The Teamcenter thin client is a Web browser-based application. You install the thin
client as part of the Web tier application. To install the Web tier, you use the Web
Application Manager to create and install an enterprise archive (EAR) file that you
then deploy in a third-party application server on the Web tier host.
Users access the thin client from the Web tier host using a third-party Web browser
such as Microsoft Internet Explorer, Mozilla Firefox, and Safari. No aspect of the
thin client is installed on a user workstation other than the required third-party
Web browser.
File Management System (FMS) downloads and uploads file data for the rich client,
embedded viewer, and the thin client configured with Lifecycle Visualization.
Multi-Site Collaboration also uses FMS servers to transfer data.
Note If you install File Management System, the FMS server cache (FSC) and the
server manager must run on the same host server, with the same user ID.
If the FSC does not manage any volumes, that is, if it is purely a cache
server, it can run as any user that is convenient.
• Shared server-level performance cache for shared data access between multiple
users
• Transient data store mechanism for transporting reports, PLM XML, and other
nonvolume data between the Web and client tiers in the four-tier architecture
FMS caching enables placing the data close to the user, while maintaining a central
file volume and database store.
FMS requires the installation of FMS server cache (FSC) and FMS client cache
(FCC) components:
• The FSC component provides a server process and file caches for Teamcenter
server hosts.
• The FCC component provides a client process and file caches for rich clients
on user workstations.
Rich Client
FCC Vol 1
LAN SYSTEMS
Rich Client
FCC Vol 2
TC Server
FSC Server
Visualization
Client
Vol 3
FCC
• Configuration server
As a configuration server, the FSC provides FMS configuration information to
the FMS client caches and other FSCs.
Any deployment of Teamcenter requires a minimum of one FSC server. You can
deploy multiple FSC servers, each performing a multiple roles or each performing
a designated purpose as either a volume, a cache, or a configuration server. When
you install multiple volumes on different hosts for the same database, the multiple
FSC servers are linked through a common master FSC. (You can manually configure
more than one master FSC.)
You must install an FSC server on:
• Each host running a Teamcenter server manager.
FSC servers and caches are configured using XML-based files, in a hierarchical
structure:
• FMS master configuration file (fmsmaster_fsc_id.xml)
The master configuration file describes the File Management System network
and defines FSC groups. It is the highest file in the hierarchy and can define
default values for FSCs and FCCs, such as the maximum sizes of the caches.
Each installation of Teamcenter requires one FMS master configuration file.
At least one FSC server reads this file and is called the master FSC. Other
FSC servers in the network download FMS configuration information from the
master FSC server.
If you install only one FSC server in a Teamcenter network, it is the master.
defines such values as the maximum sizes of the server segment file caches
and the upload timeout value.
This file can either inherit values from the master file or override them. It can
also define default values for FCCs.
• The FCC configuration file defines values for the FCC on client hosts, such as the
maximum sizes of the caches.
It can either inherit values from the FSC configuration file or override them.
Installation of the FCC depends on whether the client workstation hosts the rich
client or thin client:
• The rich client requires an FCC, and the Over-the-Web Installer automatically
installs an FCC with each rich client.
The rich client uploads files to the Teamcenter volume and downloads files from
the Teamcenter volume using the FCC. If Teamcenter lifecycle visualization 6.0
or later is installed on the workstation and used with the rich client, it optionally
uses the FCC.
When you create the rich client instance to be installed on user workstations,
you configure the location of the cache on the workstation and the maximum size
of files downloaded from the volume or uploaded to the volume. Installing the
rich client instance on a workstation simultaneously installs the FCC process
and caches. No additional configuration steps are required.
For information on configuring the FCC while creating the rich client instance,
see Installing rich client Web applications. Configuring the FCC this way
may be the only configuration you require, but you can take advantage of
• The thin client does not use the FCC. Workstations that access the thin client
do not require its installation.
However, if you install the FCC, Teamcenter lifecycle visualization 6.0 and NX
4.0.1 use it to upload files to and download files from the Teamcenter volume.
Installing the FCC enables users to take advantage of FMS features:
o Improved file transfer performance
FMS is a high-performance file transfer solution that gives client applications
direct access to files over a high-performance network connection.
o File streaming
Teamcenter lifecycle visualization uses proprietary file streaming technology
to download appropriate portions of the JT files over the network as they are
needed. FMS supports segment file transfer to keep network loads down and
support this high-performance file streaming technology.
o Deployment flexibility
FMS components support a multitude of deployment configurations. This
enables administrators to geographically locate volumes and shared FSC
servers close to client workstations, providing the ability to tune the system
for optimal file transfer performance.
For information on installing an FCC for use with the thin client and Teamcenter
lifecycle visualization, see the appropriate Teamcenter client installation guide
(for Windows, Linux, or Macintosh).
Creating volumes
Using Teamcenter Environment Manager installation program, you create two
types of Teamcenter volumes:
• Standard volumes
Standard volumes are UNIX directories Teamcenter uses to store files managed
by Teamcenter. Users cannot directly access the files in these volumes; they must
do so via a Teamcenter session. One standard Teamcenter volume is required
per database. You can optionally create multiple volumes for a database.
You create a standard volume when installing Teamcenter and populating a
Teamcenter database. Volumes require the installation of File Management
System (FMS). FMS provides the volume services after the volume is created.
• Transient volumes
A transient volume is a UNIX directory that Teamcenter uses to store temporary
data for transport of reports, PLM XML, and other data between the Web tier
Teamcenter administrators can also create volumes using the rich client
Organization application.
For information about creating volumes after installation of Teamcenter, see the
Organization Guide.
• Lifecycle Visualization stand-alone application viewer (rich client and thin client)
The Lifecycle Visualization stand-alone application viewer is launched from
either the Teamcenter rich client user interface or the thin client user interface.
Users can also run it as a stand-alone application. The suite includes the
embedded viewer and Teamcenter lifecycle visualization mockup.
The stand-alone application viewer is individually installed on each client
workstation using the Teamcenter lifecycle visualization distribution images.
The rich client distribution instance can be configured with the information
required to enable the rich client to integrate with Lifecycle Visualization
applications already installed on client workstations.
b. If you are deploying the Teamcenter rich client, create a four-tier rich
client distribution instance, configuring Security Services for the client by
specifying the same Teamcenter application ID, Security Services logon
Service URL, and Identity Service Web URL as specified when configuring
Security Services for the Web tier.
For information, see Install rich client distribution instances.
Other considerations
Certain issues regarding distribution of database and license servers can affect
planning of your Teamcenter network.
You must create a database instance if one does not exist or if an additional database
instance is required (for example, to support testing, training, or RDV). If you are
installing RDV services, Siemens PLM Software recommends strongly that you
create a new database instance on an Oracle server with database partitions on a
separate disk drive. RDV requires extensive data warehousing with large uploads
and simple queries. Such a configuration also makes the fine-tuning of the database
easier.
For information about installing Oracle Server, creating Oracle database instances,
and upgrading Oracle databases, see Oracle installation and configuration.
Note QPL and a separate RDV database are not required if you use cacheless
search.
When deploying the two-tier architecture, you can install Teamcenter application
executable files on a single application server host, export the Teamcenter
application root directory structure from the Teamcenter application server, and
mount it using NFS on client workstations to run Teamcenter locally. Typically, the
Teamcenter application server is also the Teamcenter data server. Similarly, you can
export the data directory structure and mount it using NFS to other Teamcenter
clients to provide access to the database-specific information.
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
Note If your Teamcenter database server is IBM DB2, all Teamcenter servers and
two-tier rich clients in your network must run operating systems supported
for Teamcenter with IBM DB2. IBM DB2 databases are supported only
with Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE
Linux platforms.
After you prepare your DB2 server host, install a Teamcenter-supported version
of IBM DB2.
Note For more information about installing and using DB2 software, including the
DB2 Control Center, see the IBM DB2 Information Center:
http://publib.boulder.ibm.com/infocenter/db2luw/v9//index.jsp
• If you use downloaded images, download the appropriate DB2 image for your
platform from an IBM partner site such as the following:
http://www-01.ibm.com/software/data/db2/linux-unix-windows
Extract the image to an authorized directory on the Linux/UNIX file system.
Note The IBM DB2 server can be installed from the root user account or a
nonroot user account. Root installation offers full functionality of the
DB2 for Linux, UNIX, and Windows (LUW) edition. Root installation
also permits multiple versions of the DB2 server to be installed on
the same host, where nonroot installation allows only one instance,
image, and version on a single system.
3. Change to the directory in which you extracted the DB2 installation image.
4. In the IBM DB2 installation image, launch the db2set shell script to launch
the IBM DB2 installation program.
6. Under DB2 Enterprise Server Edition Version version, click Install New.
This launches the DB2 Setup - DB2 Enterprise Server Edition installation
wizard.
7. Proceed to the Software License Agreement dialog box. After you accept the
license terms, click Next.
8. In the Select the installation type dialog box, select the type of installation you
want to perform. The Typical option is sufficient for the Teamcenter server’s
needs.
9. In the Select the installation, response file creation, or both dialog box, select
the appropriate option. If you do not want to save your installation settings in
a response file, select the first option in the list (Install DB2 Enterprise Server
Edition on this computer).
10. In the Select the installation folder dialog box, enter an installation directory
or accept the default directory shown.
11. In the Set the DB2 copy name dialog box, accept the default value for DB2
copy name and make sure Set this as the default DB2 copy on my computer is
selected.
12. In the Set up a DB2 instance dialog box, click Create the default DB2 instance.
13. In the Set up partitioning options for the default DB2 instance dialog box,
click Single partition instance.
14. In the Configure DB2 instances dialog box, accept the existing values shown.
15. In the Set user information for the default DB2 instance dialog box, type and
confirm the password for the database user account.
Accept the default database user name shown. If multiple domains are available,
select the appropriate domain in the Domain list. Otherwise, accept the default
setting.
Make sure Use the same user name and password for the remaining DB2
instances is selected.
16. In the Prepare the DB2 tools catalog dialog box, clear the Prepare the DB2
tools catalog check box.
17. In the Set up notifications dialog box, clear the Set up your DB2 server to send
notifications check box.
18. In the Enable operating system security for DB2 objects dialog box, accept the
default values shown.
If multiple domains are available, select the appropriate domain for the DB2
users group. Otherwise, accept the default setting.
19. In the Start copying files dialog box, click Install to begin installing the DB2
server.
20. When the DB2 installation program displays the Setup is complete dialog box,
click Next.
Replace DB2-home with the home directory of the DB2 instance owner. Replace
license-file with the path to your DB2 license file.
The default license file is DB2-image/db2/license/db2ese.lic. Replace
DB2-image with the path to your IBM DB2 installation media.
Using the DB2 First Steps application, create the sample database by one of the
following methods:
• Using default sample tables
Note The DB2 First Steps application requires a Web browser. Make sure a
Teamcenter-supported version of Mozilla Firefox or Microsoft Internet
Explorer is installed on the DB2 server host.
2. In the DB2 First Steps application, in the options on the left side, click Database
Creation.
4. In the Create SAMPLE Database dialog box, click SQL objects and data only.
(This is the default option.)
Click OK.
The wizard creates the sample database.
2. In the Database Creation dialog box, click Create your own Database.
This launches the Create Your Own Database wizard.
3. In the Specify a name for your new database dialog box, click option.
4. In the Specify where to store your data dialog box, enter one or more storage
paths for the database, or accept the default location shown.
5. In the Select your maintenance strategy dialog box, choose whether you want to
specify a time period for database maintenance. This is optional and does not
directly affect Teamcenter operation.
6. In the Provide a valid SMTP server dialog box, click Next. No options in this
dialog box are required for Teamcenter.
7. In the Review the actions that will take place when you click Finish dialog
box, click Finish.
The wizard creates the database.
2. In the Basic administration tasks dialog window, click Start DB2 Control Center.
This launches the DB2 Control Center.
3. When the Control Center prompts you to choose a view, click Advanced.
4. In the Control Center tree (under Object View), expand All Databases.
After you verify DB2 database connectivity, you can remove the sample database
to free disk space. However, if you use the sample applications, keep the sample
database.
Replace db-name with the name or alias of the database to be created. Replace
path with the path or drive on which to create the database. This is also the
storage path or drive associated with the database.
For example:
CREATE DB tcdb2 AUTOMATIC STORAGE YES ON ’D:’ USING CODESET
UTF-8 TERRITORY US PAGESIZE 32 K
Database configuration parameters can be set using the DB2 Control Center or the
update database configuration command in the DB2 command line processor.
For example:
UPDATE DB CFG FOR db-name USING STMTHEAP 100000
Optionally, you may archive DB2 database log files by setting the LOGRETAIN
and USEREXIT database parameters.
The LOGRETAIN database parameter is not enabled by default, and its behavior
is affected by the value of the USEREXIT parameter.
Set USEREXIT to one of the following values:
Make sure your database administrator reviews the settings for the LOGRETAIN
and USEREXIT parameters.
For more information about these parameters, see the IBM documentation.
After you complete configuring your database, you can install a Teamcenter server
using Teamcenter Environment Manager (TEM). During installation, TEM creates
database objects and populates Teamcenter data.
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
Perform the following tasks to prepare an Oracle database server and configure an
Oracle database for Teamcenter:
1. Choose a name for the Teamcenter user account. Teamcenter uses this account
as the owner of all Teamcenter-created tables. This account is used by the
database administrator to perform tasks required by Teamcenter.
Tip If you use the Siemens PLM Software-supplied templates to create the
Teamcenter database, the name and password of the account is infodba.
2. Set shell limits and parameters on the Oracle server host. For more information,
see Set shell limits and parameters.
• If you have an Oracle server installed, but it is not a version certified for
Teamcenter 10.1, upgrade your Oracle server. For more information, see
Upgrade an Oracle server and database.
5. Create a database for Teamcenter. For more information, see Create an Oracle
database.
2. In the User NAME box, type the user name of the Oracle software owner, for
example, oracle.
3. Scroll down the list and ensure that the values shown in the following table are
set to the minimum values.
Caution Do not change the shell limit values if they were set for another
program and the values are greater than the levels Oracle requires.
2. Ensure that the value shown for Maximum number of PROCESSES allowed
per user is greater than or equal to 2048.
Note For production systems, this value should be at least 128 plus the sum
of the PROCESSES and PARALLEL_MAX_SERVERS initialization
parameters for each database running on the system.
Note You can view kernel parameters using the kctune command.
Solaris 10 resource
control Description
process.max-sem-ids Oracle recommends setting this resource control to
100, but the Solaris default value (128) is adequate,
so it is not necessary to change this setting.
project.max-shm-memory Defines the maximum shared memory (shm) for the
Oracle server. Oracle recommends a value of 4 GB,
but for Teamcenter servers, set this resource control
to a value greater than the total SGA + PGA memory
size of all instances on the system.
project.max-shm-ids Oracle recommends setting this resource control to
100, but the Solaris default value (200) is adequate,
so it is not necessary to change this setting.
Set parameters for the project user.oracle account (oracle) instead of the project
user.root recommended by Oracle documentation. To work with Solaris resource
control, use the following CLI command:
prtctl –n control—name –i project user.oracle
For example:
sun2:(root)# prctl -n project.max-sem-ids -i project user.oracle
project: 100: user.oracle
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-sem-ids
privileged 128 - deny -
system 16.8M max deny -
sun2:(root)# prctl -n project.max-shm-memory -i project user.oracle
project: 100: user.oracle
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-shm-memory
privileged 3.92GB - deny -
system 16.0EB max deny -
sun2:(root)# prctl -n project.max-sem-ids -i project user.oracle
project: 100: user.oracle
NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
project.max-sem-ids
privileged 128 - deny -
system 16.8M max deny
Item in Minimum
SUSE Linux shell limit limits.conf hard limit
Maximum number of open file descriptors nofile 65536
Maximum number of processes available nproc 16384
to a single user
Caution Do not change the shell limit values if they were set for another
program and the values are greater than the levels Oracle requires.
fi
• For the C shell (csh or tcsh), add the following lines to the
/etc/csh.logon.local file:
if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
endif
2. Set the PATH environment variable to include the Oracle bin directory:
export PATH=$PATH:ORACLE_HOME/bin
Hewlett-Packard HP-UX:
export SHLIB_PATH=${SHLIB_PATH}:${ORACLE_HOME}/lib
Sun Solaris:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib
SUSE Linux:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib
4. Export the contents of the Teamcenter Oracle database to the dump file:
ORACLE_HOME/bin/exp db-user/password full=y
file=file-name.dmp log=export.log
Replace db-user with the Teamcenter database user account name; replace
password with the database user account password; replace file-name with the
name of the dump file to contain the exported data; replace export with the name
of the log file to contain export output.
If you have multiple databases, repeat this procedure for each database.
Caution Siemens PLM Software strongly recommends backing up the dump file
on tape or another disk. If the dump file becomes corrupted or lost, all
data from the existing database is lost.
Replace the path with the system path to the Oracle files.
Hewlett-Packard HP-UX:
export SHLIB_PATH=${SHLIB_PATH}:${ORACLE_HOME}/lib
Sun Solaris:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib
SUSE Linux:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib
6. Shut down all Oracle database instances using the dbshut utility. Shut down
database instances listed in the oratab file:
$ORACLE_HOME/bin/dbshut
• The oratab file in either the /var/opt/oracle directory (Sun Solaris systems) or
the /etc directory (all other platforms).
2. When the Oracle installer prompts you to upgrade existing databases, enter the
required information about the databases you want to upgrade.
4. After Oracle installation is complete, import your Teamcenter database from the
Oracle dump file into the new Oracle database. Enter the following command
on a single line:
ORACLE_HOME\bin\imp
db-user/password fromuser=db-user touser=db-user file=file-name.dmp
log=import.log
Replace db-user with the Teamcenter database user account name, password
with the database user account password, file-name with the full path and name
of the dump file that contains the exported data, and import with the name
of the log file.
2. Record the name of the Oracle database server host. Teamcenter Environment
Manager requires this name during corporate server installation.
3. If Oracle was previously installed on the host, search for the following Oracle
Net configuration files in the etc and var/opt/oracle directories and either
remove them or relocate them to the corresponding network/admin directory
in the Oracle home directory:
listener.ora
tnsnames.ora
sqlnet.ora
This step is required for compliance with the standard of storing Oracle Net
configuration files in the network/admin directory.
4. If you use 64-bit Hewlett-Packard HP-UX, create the following symbolic links
before you begin Oracle installation:
# cd /usr/lib
# ln -s libX11.3 libX11.sl
# ln -s libXIE.2 libXIE.sl
# ln -s libXext.3 libXext.sl
# ln -s libXhp11.3 libXhp11.sl
# ln -s libXi.3 libXi.sl
# ln -s libXm.4 libXm.sl
# ln -s libXp.2 libXp.sl
# ln -s libXt.3 libXt.sl
# ln -s libXtst.2 libXtst.sl
Replace device-name with the name of the CD-ROM device, for example,
dev/cd0; replace /cdrom with the CD-ROM mount-point directory.
Hewlett-Packard HP-UX:
/usr/sbin/mount -F cdfs -o rr device–name /cdrom
Note Replace device-name with the name of the CD-ROM device, for example,
dev/dsk/c0t0d0; replace cdrom with the CD-ROM mount-point
directory.
Sun Solaris:
/usr/sbin/mount -r -F hsfs device–name /cdrom
Note Use the preceding command if Solaris does not mount the CD-ROM
automatically. Replace device-name with the name of the CD-ROM
device, for example, dev/dsk/c0t6d0s2; replace /cdrom with the
CD-ROM mount point directory.
SUSE Linux:
mount -t iso9660 device–name mount-directory
Note Use the preceding command if SUSE Linux does not mount the CD-ROM
automatically. Replace device-name with the name of the CD-ROM
device, for example, dev/cdrom; replace mount-directory with the
CD-ROM mount-point directory, for example, media/cdrom.
6. On IBM AIX only, run the rootpre.sh script as root user in a shell window.
Copy the rootpre directory from the CD-ROM to a directory on a local hard disk
and run rootpre.sh from disk. Enter the following commands:
cp –r /CDROM/rootpre /tmp
cd /tmp/rootpre
chmod 755 *
./rootpre.sh
7. If the /tmp directory does not have at least 400 MB of free space, set the TEMP
and TMPDIR environment variables to a directory that meets this requirement:
$ export TEMP=directory-path
$ export TMPDIR=directory-path
Replace directory-path with the path to the directory with sufficient space, for
example, disk/tmp
10. If Oracle Universal Installer displays the Specify Inventory Directory and
Credentials window, enter the directory where you want to install inventory files
and the operating system group name for the group that owns the inventory
directory; click Next.
Note Siemens PLM Software recommends:
• Use the default directory (oraInventory) in the Oracle base
directory.
• Use the default of the group the oracle account belongs to (dba).
11. If Oracle Universal Installer prompts you to run the orainstRoot.sh script, run
it in a separate terminal window as the root user and then click Continue:
$ORACLE_BASE/oraInventory/orainstRoot.sh
12. In the Select Installation Type dialog box, select Enterprise Edition and click
Next.
13. In the Specify Home Details dialog box, enter the directory path in which to
install the Oracle products in the Destination box and click Next.
Note Do not install Oracle 11g or later into an existing Oracle home that
contains Oracle 10g or earlier software.
14. In the Product-Specific Prerequisite Checks dialog box, verify that all the
prerequisite checks succeeded and click Next.
Note If a check fails, review the displayed cause of the failure for that check,
correct the problem, and rerun the check.
A check occasionally fails erroneously, for example, when you install a
later patch that obsoletes a listed patch. When you are satisfied that
the system meets a requirement, manually verify the requirement by
selecting the check box for the failed check.
15. In the Select Configuration Option dialog box, select Install database software
only and click Next.
16. In the Summary dialog box, review the information to ensure you have sufficient
disk space and click Install.
Oracle Universal Installer displays a progress meter that adjusts at the
completion of each installation and relinking phase.
If you are installing from CD-ROM, Oracle Universal Installer prompts you
to insert subsequent CD-ROMs when they are required. If you encounter
errors, see the Oracle Database Installation Guide for UNIX Systems for
troubleshooting information.
When Oracle Universal Installer completes installing Oracle products, it creates
the root.sh script in the Oracle home directory and prompts you to run the script.
17. Log on as the root user and run the root.sh script in the Oracle home directory.
The root.sh script sets the necessary file permissions for Oracle products and
performs other related root-related configuration activities.
18. After the root.sh script completes successfully, click OK in the Oracle Universal
Installer Setup Privileges dialog box.
Tip Record the number of the port used by the Oracle database server
listener for entry during corporate server installation. Teamcenter
Environment Manager requires this port number.
g. In the Naming list (to the right of the Oracle Net Configuration tree), choose
General.
4. In the same window in which you started Oracle Net Manager, start the listener
service:
$ORACLE_HOME/bin/lsnrctl start LISTENER
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
1. Make sure you have access to the Teamcenter software distribution image.
4. Open a shell window and set the ORACLE_BASE environment variable. For
example:
export ORACLE_BASE=/disk1/oracle
7. In the Operations dialog box, select Create a database and click Next.
8. In the Database Templates dialog box, select the appropriate template (for
Oracle 11g) and click Next.
9. In the Database Identification dialog box, either accept the default database
name in the Global Database Name box or type a different name and click Next.
Note The SID box is automatically filled in with the name you enter in the
Global Database Name box.
Tip Record the SID of the Oracle instance for entry during corporate server
installation. Teamcenter Environment Manager requires this name.
11. In the Database Credentials dialog box, select Use the Same Password for All
Accounts, enter and confirm the password for the SYS, SYSTEM, DBSMNP,
and SYSMAN accounts, and click Next.
12. In the Storage Options dialog box, select File System and click Next.
13. In the Database File Locations dialog box, select Use Database File Locations
from Template and click Next.
14. In the Recovery Configuration dialog box, select Specify Flash Recovery Area
and click Next.
18. In the Create Options dialog box, select Create Database and click Finish.
19. In the Confirmation dialog box, click OK to start creating the database.
When the database is created, DBCA displays a window containing information
about the created database.
If this script did not execute successfully, execute it again using the
Oracle SQL*Plus utility. Log on to SQL*Plus as sysdba.
Prepare the Teamcenter server host, install the corporate server, then perform any
required postinstallation tasks.
To obtain a composite host ID for your license server, run the getcid utility on your
license server host. Download this utility from GTAC:
4. On the FTP site, click the directory corresponding to the platform type of your
license server, for example, .
Run the getcid utility on the target license server (or on all three servers in a
redundant configuration). The utility provides the CID for license server as a
12-digit hexadecimal number. For example:
$ getcid.exe
The Siemens PLM Software licensing composite hostid is:
”COMPOSITE=37B5ED1AC61D”
After you obtain the CID, enter it into your customer record to generate a permanent
license file. You can enter your CID using either your WebKey account or by calling
your customer services representative. After the CID is entered into your customer
record, you are sent a permanent license file to install on your license server.
For more information about installing the Siemens PLM License Server, see Install
the licensing server.
Replace port with the port number and host with the host name of the license
server, for example, 28000@tchost. The port and host values must match those
you specified in the SERVER line of the Teamcenter license file.
1. Port 28000 is registered for the Siemens PLM License Server with the Internet Assigned Numbers Authority (IANA). For more
information, see http://www.iana.org/assignments/port-numbers.
b. Open the ugslicensing_install.ans file and edit the contents to specify the
destination directory and path to the Teamcenter license file.
For more information, see the Installing Siemens PLM Software Licensing for
UNIX, Installing Siemens PLM Software Licensing for Windows, and Siemens PLM
Common Licensing User Guide documents in the additional_documentation
directory on the Teamcenter 10.1 documentation distribution image.
• You can select automounted NFS directories, but you must supply the automount
link name for the Teamcenter application root directory. Do not supply the
automounted directory (for example, /tmp/mnt/node-name).
2. Verify the setting using the echo command or equivalent. Make sure the correct
value for LC_ALL is displayed.
3. Run the locale command and make sure the LANG variable and all the LC_x
variables are set the same as LC_ALL.
Alternatively, your system administrator may modify the date file (named
TIMEZONE in the etc directory), which can preset this environment, so every time
you log on and launch a shell, the environment is preset.
The recommended method, however, is to log on to the system using the Common
Desktop Environment (CDE) with the minimum required locale (ISO8859-1) by
choosing Option→Language→en_US.ISO8859-1 during logon.
If the ISO8859-1 character set is not loaded on your machine, contact your system
administrator to have it installed before you install the GM Overlay.
This requirement is due to changes in the installation process for Teamcenter 10.1,
which uses XML files rather than .dat files and associated scripts. Because of this,
GM Overlay data is transformed from .dat files into XML files.
To read and parse the XML files correctly, the system must be able to process
non-English (non-ASCII) locale characters. To facilitate this, the system must be
first loaded with the fonts for that locale.
Note Ensure the ISO8859-1 character set is loaded before you add any Teamcenter
features to your configuration that contains the GM Overlay. If the
ISO8859-1 character set is not loaded, lists of values (LOVs) for GM Overlay
are corrupted during feature installation. Upgrade of the GM Overlay
feature fails if the ISO8859-1 character set is not loaded.
3. Click Install.
7. Proceed to the Features panel. This panel shows the FMS Server Cache feature
preselected by the Volume Server solution.
8. In the Installation Directory box, enter the absolute path to the directory where
you want to install the volume server.
9. Proceed to the Operating System User panel. Type the password for the
operating system account to which you logged on to install the volume server.
10. Proceed to the FSC Service panel. Enter required values for the FMS server
cache (FSC) service. For information about required values, click Help.
11. Proceed through the remaining panels, entering required values for the volume
server. For information about these panels, click Help.
12. Proceed to the Confirmation panel. Verify the information you entered. If you
want to change any values, click Back to return to the panels you want to change.
Otherwise, click Next to begin installing the volume server.
• On the local host, create the Teamcenter operating system user account.
Note All Teamcenter services run as this user account.
• Obtain the host name of the licensing server and the port number used for
licensing processes.
• Ensure that a database server is installed for Teamcenter and obtain the
following information from the database administrator:
o The type of database server used for this installation of Teamcenter.
For Oracle database servers, the service name of the Oracle instance.
Typically, the service name is the same as the SID.
1. The Teamcenter documentation distribution image contains the tchelp.jar file needed by the online help feature.
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.
Data Description
Read cache directory and size? For FMS to operate correctly, the location you specify must
be on the local host.
If you are installing a volume on the host, FMS does not
use the read cache; Siemens PLM Software recommends
accepting the default cache size (10 megabytes). Do not
specify 0; specifying 0 creates a file cache with a default size
larger than 10 megabytes.
If you are not installing a volume on this host, FMS acts
as a cache server. In this case, Siemens PLM Software
recommends increasing the value to 1000 megabytes.
However, choose a size that represents the maximum size
of the data that must be processed. If you choose 1000
megabytes, and a user requests a 3 gigabyte assembly, the
request fails.
Data Description
Write cache and size? This cache is required when the FSC acts as a cache server.
For FMS to operate correctly, the location you specify must
be on the local host.
If you are installing a volume on this host, FMS does not
use the write cache; Siemens PLM Software recommends
accepting the default cache size (10 megabytes). Do not
specify 0; specifying 0 creates a file cache with a default size
larger than 10 megabytes.
If you are not installing a volume on this host, FMS acts
as a cache server. In this case, Siemens PLM Software
recommends increasing the value to 512 megabytes or more.
However, choose a size that represents the maximum size of
the data that must be processed.
Communication mode between Either HTTP or HTTPS.
FMS components?
Configure proxy servers? Either HTTP proxy server or HTTPS proxy server.
If you choose to configure proxy servers, you must provide:
• The name of the host running the proxy server.
Data Description
Default settings for the FCC? • Location of the cache directory for all Windows systems
and for all UNIX systems.
1. Log on to the operating system with the Teamcenter user account you created for
installing and maintaining the Teamcenter installation.
2. Specify the path to the required Java Runtime Environment (JRE) by setting the
JRE_HOME or JRE64_HOME environment variable on your host.
Note Alternatively, you can specify the JRE path when you launch Teamcenter
Environment Manager (TEM) from a command prompt using the -jre
JRE-path argument.
For more information, see Java Runtime Environment.
3. Start TEM:
a. Change to the root directory of the Teamcenter software distribution image.
c. In the Installer Language dialog box, select a language and click OK.
Your language selection applies only to the TEM session, not the Teamcenter
installation.
Note
For information about any TEM panel, click the help button .
4. Proceed to the Welcome to Teamcenter panel. This panel contains the following
options:
• Install
Installs a new Teamcenter configuration using a fully configurable
installation process.
• Upgrade
Upgrades an existing Teamcenter configuration.
For information about upgrading, see the Upgrade Guide.
• 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.
For information about creating a custom distribution, see Creating a
custom distribution.
5. In the Configuration panel, type a unique ID and description for the new
Teamcenter configuration.
The configuration ID identifies your Teamcenter configuration when you
maintain, upgrade, uninstall, or add features to the configuration. Installation
log files are also named based on the ID you enter.
7. Proceed to the Features panel. This panel shows the corporate server features
preselected by the Corporate Server solution:
Teamcenter Foundation
FMS Server Cache
NX Integration
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.
Note • If you are deploying the J2EE Web tier, select the J2EE Based
Server Manager feature (under Server Enhancements).
9. In the Installation Directory box, enter the path to a new directory where you
want to install Teamcenter.
Note • The Teamcenter installation directory must not already exist on your
system. TEM creates the directory during installation.
10. 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.
11. In the Operating System User panel, type the password for the operating system
account under which you install Teamcenter.
12. In the Foundation panel, select how you want to create or designate the
Teamcenter database and Teamcenter data directory (TC_DATA).
13. Enter the required values for your Teamcenter database according to your
selection in the Foundation panel.
• Create and populate database, create new data directory:
a. Proceed to the Foundation Database panel.
c. Enter the required values for the database server, the database user, and
the database administrator account.
c. Enter the required values for the database server and the database user.
c. Enter the required values for the database server and the database user.
help button .
For Oracle databases, the directory you specify in the Database Path box
must exist and you must have write permission to the directory.
14. In the Data Directory box, enter a location for the Teamcenter data directory.
The Teamcenter data directory is called the TC_DATA directory. This value is
stored in the TC_DATA environment variable on your system. TEM creates
shared data subdirectories and files in this location. Each data directory is
associated with a single database user within a database instance.
Do not set TC_DATA in the system environment. TEM sets this variable as
required in various scripts. Setting this variable in the operating system can
cause conflicts if you install more than one configuration.
Value Description
Transient Volume Directories Specifies transient volume locations for
Windows hosts, UNIX/Linux hosts, or both.
A transient volume is an operating system
directory controlled by Teamcenter and
used to store temporary data for transport
of reports, PLM XML data, and other
nonvolume data between the enterprise
tier and client tier in a deployed four-tier
architecture. All four-tier clients that
access the corporate server you are
installing use this transient volume.
For more information about transient
volumes, see the System Administration
Guide.
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_metadata_cache
utility at the end of the install, upgrade,
or update action. This option reduces
Teamcenter memory consumption by
moving metadata to shared memory.
Types, property descriptors, and constants
are placed in a shared cache that is shared
by all Teamcenter server instances.
This option is selected by default in a
Teamcenter server installation.
For more information about managing
shared server cache, see the System
Administration Guide.
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.
Value Description
17. Proceed to the Flex License Client panel. Enter settings for the Siemens PLM
License Server.
Note The Siemens PLM License Server must be installed before you begin
Teamcenter installation.
For more information, see Install the licensing server.
18. Proceed to the Teamcenter Administrative User panel. During a corporate server
installation, the values in this panel are read-only.
19. Proceed through the remaining panels, entering the required information for the
features you selected.
20. 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 you chose the Online Help feature, TEM prompts for the location
of the online help files during installation. Enter the path to
the location of tchelp.jar file on the Teamcenter documentation
distribution image.
3. For each database identified in step 2, identify a network node local to that
database to act as the ODS server.
The ods daemon runs on this system to listen for publication queries from
other databases.
4. For each database identified at step 1, identify a network node local to that
database to act as the IDSM for that database.
When other databases request an object published from this database, the idsm
daemon is run on this network node to export the object.
5. For each database identified in step 1, obtain the site name and site ID.
The site ID of the database is generated during installation and cannot be
changed. The site name is customizable but by default is based on the site ID.
To obtain the site name and site ID, use the administration application named
Organization in Teamcenter rich client (in the rich client application manager,
click Admin and then click the Organization symbol). Within Organization,
choose the top-level Sites node from the Organization tree. The site details for
the local database are listed first. For more information, see Organization Guide.
6. Using the information obtained in steps 2 through 5, populate each database site
table with information about the other sites using the Organization application
in the Teamcenter rich client.
The node for each site is the name of the network node to run the necessary
Multi-Site Collaboration daemons (idsm and/or ods). If the site is an ODS
database, check the ODS site flag. To publish objects from the ODS database,
define the site of the ODS database in the site table and configure the ODS
server as an IDSM server.
7. For each database identified in step 1 and step 2, edit the site preference for
the database and modify the following preferences to reflect the Multi-Site
Collaboration environment:
ODS_permitted_sites (ODS database only)
ODS_site (Non-ODS databases)
ODS_searchable_sites
ODS_searchable_sites_excluded
IDSM_permitted_sites
IDSM_permitted_users_from_site_site-name
IDSM_permitted_transfer_sites
IDSM_permitted_transfer_users_from_site_site-name
IDSM_permitted_checkout_sites
IDSM_permitted_checkout_users_from_site_site-name
Fms_BootStrap_Urls
TC_publishable_classes
TC_transfer_area
For more information about these preferences, see the Teamcenter Preferences
and Environment Variables Reference.
8. For each database identified in step 1 and step 2, copy all POM transmit schema
files for that database into the POM transmit schema directories for each of the
other databases.
This step is required to allow the import of data objects from other databases.
Devise a strategy for regularly synchronizing POM transmit schema directories.
9. For each network node identified at step 3 and step 4, run the Teamcenter
installation program on that node to configure and start the Multi-Site
Collaboration daemons.
This procedure adds the idsm daemon entry to the inetd.conf file and forces the
inetd daemon to reload its configuration. As a result, the Multi-Site Collaboration
daemons are launched to complete the installation.
3. Make sure your Windows and UNIX server configurations contain identical sets
of Teamcenter features. For example, if you install features or custom templates
on a UNIX server, you must install the same features and templates on your
Windows server.
2. Use the clearlocks utility to check for nodes connected to the database:
$TC_ROOT/bin/clearlocks -node_names
3. Note the node names returned, and then type the following command for each
node name returned:
$TC_ROOT/bin/clearlocks -assert_dead node-name
These are the only directories affected by Teamcenter installation. If you created
other directories that contain data used by your existing Teamcenter installation,
such as a separate POM transmit schema directory, Siemens PLM Software
recommends that you back up these directories as a precautionary measure.
Install the Teamcenter Web tier, which manages communication between the
Teamcenter clients and the enterprise tier.
2. Copy the necessary ICD files from the Teamcenter software distribution image.
This populates the list of solutions available to install.
Note •
Deployment of Web applications is described in the Web Application
Deployment Guide.
• Install a supported third-party J2EE application server and the Java Runtime
Environment (JRE) on the Web tier host.1
• If you want to install Teamcenter online help for the Web tier, obtain the
Teamcenter 10.1 documentation distribution image.
Note Alternatively, you can install the Teamcenter online help library using
Teamcenter Environment Manager (TEM) rather than installing it as
part of the Web tier.
Teamcenter developer references, the Teamcenter Data Model Report,
and the Teamcenter PDF help collection are not available to install on
the J2EE Web tier. These online help components can only be installed
to a local host or network file system path using TEM.
For more information, see Installing Teamcenter online help.
• If you use Security Services with the rich client or thin client, install Security
Services as described in Security Services installation.
1. For information about supported application servers and Java versions, see the Siemens PLM Software Certification Database
(http://support.industrysoftware.automation.siemens.com/ certification/teamcenter.shtml).
3. Type the following command to extract Web Application Manager files to your
host:
cat image-path/INSTALL_TCWEB.TZ | uncompress -c | tar xvf -
Replace image-path with the full path to the Teamcenter software distribution
image.
Note On Red Hat Linux systems, use the gzip command instead of
uncompress to extract INSTALL_TCWEB.TZ file:
cat image-path/INSTALL_TCWEB.TZ | gzip —d | tar xvf —
c. In the Copy ICD Files dialog box, click OK to load ICD files.
a. In the Name box, type the name of this application, for example, Teamcenter
Web Tier.
b. In the Staging Location box, enter the path to the location where you
want the application files to reside. Typically, this is a directory under the
WEB_ROOT directory. Web Application Manager creates the directory you
specify if it does not exist.
5. Select the solutions to include in the Teamcenter Web Tier Web application:
a. Click Solutions.
b. In the Select Solutions dialog box, select the following required solutions:
Teamcenter – Server Adapter
Solution Description
Teamcenter – GM Overlay Provides the Teamcenter Automotive
Edition–GM Overlay for the Teamcenter
thin client.
Teamcenter – Online Help Provides Teamcenter online help for the
thin client.
Note If you select this solution, you must
add the path to the Teamcenter
documentation distribution image
to the list of Disk Locations for
Install Images as in step 4.2
2. The Teamcenter documentation distribution image contains the tchelp.jar file that contains the online help files.
Solution Description
Teamcenter Services Installs the Teamcenter service-oriented
WSDL/SOAP Support architecture (SOA), which provides the
ability to develop task-specific clients,
utilities, and system integrations for the
Teamcenter server. The Teamcenter SOA
also ships with WS-I compliant WSDL files
for all operations, supporting open industry
standards.
For more information, see the Services
Guide.
6. If you require the deployable file for the Web application to be a distributable file,
click Advanced Web Application Options and select the Distributable option.
Note A distributable file is required only if you deploy the Web tier application
in a cluster configuration.
7. Click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
LogVolumeLocation
Enterprise Application
Registration ID
To set a context parameter, double-click the Value box for the given parameter
and enter the new value. To view a description of any context parameter, click
the parameter name in the Modify Required Context Parameters dialog box.
For more information about context parameters, see Web tier context parameters.
Note Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses,
use host names in URLs wherever possible so the domain name system
(DNS) can determine which IP address to use.
If you must use IP addresses and your network uses IPv6 addresses,
enclose the literal IPv6 address in square brackets, for example:
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc
11. Locate the deployable file (tc.ear) generated during installation. This file is in
the deployment directory under the specified staging location.
Deploy the Web application as described in the Web Application Deployment
Guide.4
Note If your network includes client hosts running on an IPv6 network, the
J2EE 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 J2EE server manager.
A typical environment for the J2EE 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.
3. For more information about configuring JBoss Cache TreeCache and setting TreeCache parameters, see www.jboss.org/jbosscache.
The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jgroup.org.
4. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose
the appropriate procedure for the application server you use.
You build Global Services Web applications using the Web Application Manager.
Several Global Services connectors require that you provide the location to files that
are provided by the connector’s back-end system or from some other source. The
location must be accessible to the Web Application Manager as you must enter the
path to the file in the Disk Locations for Install Images box. If you plan to include
the connector in your Web application, make sure the files identified for the connector
are available, and note the path to the file for use in Generate Web applications.
If you copy the mti.jar file to a Web Application Manager accessible location,
it must be in the enterprise directory under the location set in the Disk
Location to Add box. Alternatively, you can edit the ICD file to remove
enterprise/ from the [FROM] section.
d. In the Copy ICD Files dialog box, click OK to load ICD files.
a. In the Name box, type a name for the application, for example, Application
Directory.
b. Accept the default value for Staging Location or enter a different directory.
c. In the Disk Locations for Install Images box, add the path to the Web_tier
directory on the Teamcenter software distribution image.
f. Click Solutions.
g. In the Select Solutions dialog box, clear all preselected solutions and select
the Teamcenter 10.1 Global Services Framework – Application Directory
solution.
Note Do not change the default solution type (Thin Client) in the Solution
Type box.
a. In the Name box, type a name for the application, for example, Global
Services Enterprise Application.
b. Accept the default value for Staging Location or enter a different directory.
c. Click Advanced Web Application Options. Type a name for the deployable
file in the Deployable File Name box (alphanumeric characters only).
b. In the Select Solutions dialog box, clear all preselected solutions and select
the Teamcenter 10.1 Global Services Framework - Enterprise Application
solution.
5. A distributable file is required only if you deploy the Web tier application in a cluster configuration.
Note • Some solutions require other solutions, and some solutions are
incompatible with others. When you select a solution, the Web
Application Manager automatically selects prerequisite solutions
and disables incompatible solutions.
9. If you selected a connector that requires supporting files (see Supporting files
locations), click Modify Disk Locations and add the path to any supporting files.
ApplicationInstance TcGSJDBCJNDI
SSOAppID TcGSMessageServerJNDI
LogFileLocation TcGSNotifierReactorJNDI
TcGSBOSJNDI TcGSDORJNDI
To set a context parameter, double-click the Value box for the given parameter
and enter the new value. To view a description of any context parameter, click
the parameter name in the Modify Required Context Parameters dialog box.
For more information about Global Services context parameters, see Global
Services context parameters.
14. Locate the deployable files (by the names you specified in step 7) generated
during installation. This file is in the deployment directory under the specified
staging location.
Deploy the Web application as described in the Web Application Deployment
Guide.6
b. Accept the default value for Staging Location or enter a different directory.
d. Click Advanced Web Application Options. Type a name for the deployable
file in the Deployable File Name box (alphanumeric characters only).
e. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image.
6. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose
the appropriate procedure for the application server you use.
f. Click Solutions. In the Select Solutions dialog box, clear all preselected
solutions and select only the Teamcenter – Web Tier Proxy solution.7
Note Do not change the default solution type (Thin Client) in the Solution
Type box.
4. Click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
Parameter Description
WebLogicHost Host name of the WebLogic server running
the Web tier. The proxy forwards the request
to this server.
WebLogicPort Port number of the WebLogic server instance
running the Web tier. The proxy forwards the
request to this server.
To set a context parameter, double-click the Value box for the given parameter
and enter the new value. To view a description of any context parameter, click
the parameter name in the Modify Required Context Parameters dialog box.
6. Click OK to begin building the Web application. The Web Application Manager
displays the status of the installation in the Progress dialog box. When the
installation is complete, click OK to close the Progress dialog box.
8. Locate the deployable file by the name you entered in step 3. This file is in the
deployment directory under the specified staging location.
Deploy the Web application as described in the Web Application Deployment
Guide.8
If you migrate Web tier applications to Teamcenter 10.1 from Teamcenter engineering
process management 2005 or earlier, you must update the link your site uses to
access the thin client and the links users saved to objects managed in Teamcenter.
Teamcenter 10.1 changes part of the thin client URL from /cgi-bin/iman to
/file-name/webclient. The file-name reference is replaced with the name of the Web
tier EAR file. For example, if the Web tier EAR file is named tc.ear, the value is /tc.
7. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Web
application.
8. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose
the appropriate procedure for the application server you use.
To manage this change, install the legacy URL support application (cgi-bin.war)
and deploy it on the server where the Teamcenter Enterprise Tier Web application
runs.
Note • Install the Teamcenter - Legacy URL (cgi-bin) Support thin client
solution in a separate Web application. This solution is not compatible
with other Teamcenter thin client solutions.
When the cgi-bin.war file is deployed, users who access a legacy /cgi-bin/iman
URL are redirected to the /tc/webclient URL with the following message:
You have requested a resource which has moved to a new location.
Requested URL: http://host:port/cgi-bin/iman/w8PJDvpRxBRxDD
New URL: http://host:port/tc/webclient/w8PJDvpRxBRxDD
You will be redirected to the new URL automatically in nn seconds or you may
click the above link manually. If possible, update your links to reflect
the new location.
This notification message will be displayed each time an old URL is requested
prior to month-day-year. After this time, requested resources that have
moved will be automatically redirected to the new URL without notification.
When you create cgi-bin.war using Web Application Manager, you control aspects
of the application:
• Whether the application displays the Siemens PLM Software URL message
before redirecting users to the new URL. When you choose not to display the
Siemens PLM Software URL message, the application redirects users to the new
URL but displays no informative message.
• The period of time (in seconds) the application displays the Siemens PLM
Software URL message before redirecting users to the new URL.
• The date the Siemens PLM Software URL message expires. After this date,
the application redirects the users to the new URL but does not display the
informative message.
• The protocol or the port, server, and domain portion of the requested, legacy
URL. The application changes the Siemens PLM Software-provided portion of
the URL and passes through the site-provided portion of the legacy URL.
2. Click Add.
Web Application Manager displays the Add Web Application dialog box.
c. Accept the default value for Staging Location or enter a different directory.
d. Make sure the Disk Locations for Install Images box includes the path to
the Web_tier directory on the Teamcenter software distribution image.
e. Click Solutions. In the Select Solutions dialog box, deselect all preselected
solutions and select only the Teamcenter – Legacy URL (cgi-bin) Support
solution.9
Note Do not change the default solution type (Thin Client) in the Solution
Type box.
4. Click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
Parameter Description
TcEngLocale Specifies a locale for messages displayed to
the user. This locale must match the locale
specified for the Teamcenter Enterprise Tier
Web application.
expiryDateOfResource Specifies the date the URL message expires.
MovedNotification This parameter must contain a value.
Enter a value in month-day-year format
(mm-dd-yyyy), for example, 12-10-2007, or
enter one of the following keywords:
NEVER
Specifies that the URL message never
expires.
NOW
Specifies that no message or notification
regarding the resource move is displayed
to the user. The user is immediately
redirected to the new URL.
To set a context parameter, double-click the Value box for the given parameter
and enter the new value. To view a description of any context parameter, click
the parameter name in the Modify Required Context Parameters dialog box.
9. If this solution is not included in the solutions list, copy solution ICD files as described in Build the Teamcenter Web Tier Web
application.
8. Locate the deployable file (cgi-bin.war) generated during installation. This file
is in the deployment directory under the specified staging location.
Deploy the Web application as described in the Web Application Deployment
Guide.10
Note After installation, you can optionally modify the following context
parameters for legacy URL support:
requestRedirectedTo
replacementFor CGIBIN_IMAN
redirectionWaitTime
For information about these context parameters, see Web tier context
parameters.
Client Resource
tier Web tier Enterprise tier tier
Clients Single application server Server managers Databases
instance
Client ¨ ¨ ¨
http://host:port/tc01 svrmgr11 DB1
A
Client ¨ http://host:port/tc02 ¨ svrmgr2 ¨ DB2
B ¨ http://host:port/tc03 ¨ svrmgr3 ¨ DB3
2. Create Web applications as described in Build the Teamcenter Web Tier Web
application. Assign each application a unique name.
10. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose
the appropriate procedure for the application server you use.
3. Set the following Web tier context parameters to unique values for each Web
application.
4. Deploy Web application EAR files in the Web application server instance.
For more information, see the Web Application Deployment Guide.
Note Multiple EAR file deployment is not supported on JBoss. If you use JBoss as
your Web application server, you must deploy each EAR file in a separate
application server instance.
For more information, see Start the rich client distribution server.
Note • The two-tier rich client is installed only through Teamcenter
Environment Manager (TEM). Over-the-Web installation is supported
only for the four-tier rich client.
3. Enter the path to the icd directory in the rich client over-the-Web software
distribution image and click OK.
Note Ensure that the icd folder is in the Source box of the Copy ICD Files
dialog box.
The Web Application Manager displays a Progress dialog box and copies and
loads the ICD files.
4. To ensure that ICD files are copied, check the Progress dialog box. When ICD
files are copied, a list of ICD files follows the Copying ICD files... notice. If
no files are listed, Web Application Manager did not find files to copy in the
directory you supplied.
If the copy was not successful, repeat steps 2 and 3, ensuring that you include
the icd directory in the path. Not including the icd directory is the most
common reason ICD files are not copied.
7. In the Name box, type the name of this application, for example, Teamcenter
OTW Distribution Server.
8. In the Staging Location box, type the path to the location where you want the
distribution server software and administration files to reside.
Typically, you would install the distribution server software in a directory under
the Web_tier directory, the directory in which you installed the Web Application
Manager on your hard drive.
Note • This directory must be empty. The Web Application Manager creates
the directory if it does not exist.
• Note the staging location path of this distribution server for later use.
10. Click the Add button adjacent to the Disk Locations for Install Images box.
The Web Application Manager displays the Add Disk Location dialog box.
11. In the Disk Location To Add box, type the path to the icd directory in the thin
client over-the-Web software distribution image and click OK.
The Web Application Manager displays the Add Web Application dialog box with
the path you entered displayed in the Disk Locations for Install Images box.
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 Specifies the port on which the distribution server
Port 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.
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 with the distribution server software you installed listed as
an application in the Web Applications box.
17. Either click Exit to exit the Web Application Manager or click Add to begin
installing the rich client distribution server instance.
If you use Security Services with the rich client, make sure Security Services is
installed and configured.
For information, see Security Services installation and the Security Services
Installation/Customization guide.
Make sure the Web Application Manager has access to the following software images:
• Complete rich client over-the-Web software distribution image
Note The rich client over-the-Web software distribution image includes
files for all supported Windows, UNIX, and Linux platforms. The
Web Application Manager requires access to all of these to build the
Over-the-Web Installer.
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.
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 name of the host and the port where
the Web tier or presentation tier application files are
deployed in an application server. This parameter works
together with the RichClientHelpLocation parameter to
determine how rich client users access help:
• To enable accessing help over the Web, set the
parameter value to http://host-name:port. Do
not supply the remainder of the path to the
help files (that information is supplied in the
RichClientHelpLocation parameter).
Parameter Description
HTTPUseGZip Indicates whether the rich client prefers responses
from the J2EE server in a compressed (gzipped)
form. Compressing responses reduces the bandwidth
requirement significantly, and should be considered,
especially in lower bandwidth network environment.
When set to true, the server may send responses without
compression depending on the server configuration.
When set to false, the server never compresses responses
for this rich client.
ParentFSCAddressTable List of addresses (host name and port) of the FMS file
server caches (FSC) to act as the parents of the installed
FMS file client cache.
For information on the FMS file client cache and FMS file
server cache, see Installing File Management System.
HTTPServerTable List of Web tier application servers; the first server in the
list is the default server for logon. Requires the following
information for each server:
URI
URL of the Web tier SOAP endpoint. The value
depends on where the Web tier application is
deployed. Typically it has the form:
http://host-name:port/tc/webclient
Name
Display name of the URL for the rich client graphical
user interface.
SSOAppID
Provides the Teamcenter application ID and sets the
TC_SSO_APP_ID environment variable for Security
Services.
The value you provide in this context parameter is
used only when Security Services is enabled and
either multiple Teamcenter sites are served by a
single identity provider or the Security Services
service is configured to use an ID other than TC.
When the multiple sites have different sets of users
authorized to use the application for each installation,
or different identifications in each installation, this
value identifies which installation is authenticated.
Parameter Description
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.
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 32-bit
versions of Windows.
By default, the Over-the-Web Installer uses the value of
the JRE32_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.
Install the rich client instance on the same host and in the same directory as the
distribution server.
Note If your Teamcenter network contains 32-bit and 64-bit systems, you must
provide 32-bit and 64-bit rich client distribution instances.
Users with 32-bit Web browsers must use the 32-bit Over-the-Web Installer,
and users with 64-bit Web browsers must use the 64-bit Over-the-Web
Installer.
2. Enter the path to the icd directory in the rich client over-the-Web distribution
image and click OK.
The Web Application Manager displays a Progress dialog box and copies the
ICD files.
6. In the Staging Location box, enter the path to the directory where you want to
install the rich client image files for downloading to clients.
Typically, you would install the rich client distribution instance files in a
directory under the Web_tier directory, the directory in which you installed the
Web Application Manager on your hard drive.
Note • This directory must be empty. The Web Application Manager creates
the directory if it does not exist.
8. Click the adjacent Add button adjacent to the Disk Locations for Install Images
box.
The Web Application Manager displays the Add Disk Location dialog box.
9. In the Disk Location to Add box, enter the paths to the following installation
images:
• Enter the path to the icd directory in the rich client over-the-Web installation
image.
Note For each instance, the Over-the-Web Installer requires access to the
installation images files for all operating systems.
Over-the-Web Installer
Microsoft Visual C++ 2005/2008/2010 Redistributables
Teamcenter client communication system
Rich Client 4-Tier
12. If you want to include additional solutions in the distribution instance, click
Solutions and select the applications you want installed with the rich client.
For information about available rich client solutions, see Rich client solutions.
13. When you are satisfied with your selections in the Add Web Application dialog
box, click OK.
The Web Application Manager displays the Modify Required Context
Parameters dialog box.
The Web Application Manager displays the Modify Required Table dialog boxes
for the HTTPServerTable and the ParentFSCAddressTable.
15. For each table, type the values for each parameter. To add another row to the
table, click Add Row.
Note Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses,
use host names in URLs wherever possible so the domain name system
(DNS) can determine which IP address to use.
If you must use IP addresses and your network uses IPv6 addresses,
enclose the literal IPv6 address in square brackets, for example:
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc
Table Description
HTTPServerTable Type a list of Web tier application servers; the first
server in the list is the default server for logon.
Requires the following information for each server:
URI
URL of the Web-tier SOAP endpoint. The value
depends on where the Web tier application is
deployed. Typically it has the form:
http://host-name:port/tc/webclient
Name
Display name of the URL for the rich client
user interface.
Note • 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.
For more information, see Configure
TCCS for the rich client distribution
instance.
Table Description
ParentFSCAddressTable Type a list of addresses (host name and port) of the
FMS file server caches (FSC) to act as the parents
of the installed FMS file client cache.
For information on the FMS file client cache
and FMS file server cache, see Installing File
Management System.
• Extracts the rich client image files into the webapp_root directory under
the staging location directory (named in step 6).
17. When the Progress dialog box indicates that installation is complete, click OK.
The Web Application Manager displays the Teamcenter Web Application
Manager dialog box.
To make the rich client distribution instance available to client hosts, deploy the
distribution instance on a supported Web application server.
For more information, see Deploying the distribution instance.
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.
5. In the Modify Tables dialog box, select the TcCSEnvironmentTable table, and
then click Modify.
6. In the Modify Table dialog box, click Add Row. Enter values for the TCCS
environment and then click OK to continue.
Value Description
Name Specifies the name of a the TCCS environment.
This name is displayed in the TCCS logon
dialog after configuration is complete.
URI Specifies the URI to the TCCS environment.
This is the endpoint URI for the Web tier
deployment, for example, http://host:port/tc.
Tag Specifies a string identifier for the TCCS
environment.
When installing a rich client, you can
optionally provide a Client Tag Filter value to
filter the list of environments displayed in the
rich client to those environments that match
the filter.
For example, if the Client Tag Filter value
is 9*, all TCCS environments with Tag
values beginning with 9 are available to the
client host. Environments with Tag values
beginning with 10 are not available.
Note You set the Client Tag Filter value in
step 3.
TcSS Application ID Specifies the ID of the Security Services
application you use with TCCS.
Value Description
TcSS Login URL Specifies the URL to the Security Services
application you use with TCCS.
If you use Security Services in applet-free
mode, include /tccs at the end of the URL,
for example:
http://host:port/app-name/tccs
Note Whether your network uses IPv6 (128-bit) or IPv4 (32-bit) addresses, use
host names in URIs and URLs wherever possible so the domain name
system (DNS) can determine which IP address to use.
If you must use IP addresses and your network uses IPv6 addresses,
enclose the literal IPv6 address in square brackets, for example:
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc
7. In the Modify Web Application dialog windows, click OK to apply your changes.
8. Exit the Web Application Manager and redeploy the rich client distribution
instance.
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.
4. Type values for the Security Services context parameters, and then click OK.
For descriptions of Security Services context parameters, see Web tier context
parameters.
5. Exit the Web Application Manager and redeploy the rich client distribution
instance.
For more information about installing and configuring Security Services, see the
Security Services Installation/Customization.
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.
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.
• 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.
• 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.
For each distribution server instance you create, deploy these files in a Web server.
If you are creating multiple rich client distribution instances, consider creating a
unique directory in the Web server documentation root for each instance and copy
all the files in the webapp_root/otwweb directory there. For detailed deployment
information, see the documentation for the Web server. The following examples use
the name of the instance for the Web component directory name:
<!--
To enable users to install the rich client over the Web, publish the following
information:
• 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.
Note If your Teamcenter network contains 32-bit and 64-bit systems, you must
provide 32-bit and 64-bit rich client distribution instances.
Users with 32-bit Web browsers must use the 32-bit Over-the-Web Installer,
and users with 64-bit Web browsers must use the 64-bit Over-the-Web
Installer.
2. In the webapp_root subdirectory find and run the start_rmi program file.
The start_rmi program file starts the Java remote method invocation (RMI)
registry.
3. In the webapp_root subdirectory, find and run the start_server program file.
The start_server program file starts the distribution server.
When this distribution server is successfully started, it displays the following
message:
Distribution Server Started
When the distribution server is running, rich client can be installed over the Web.
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.
Note To allow automatic updating of a rich client when users start a Teamcenter
session, do not change the name of the distribution instance.
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. Enter the path to the icd directory in the Rich Client Over-the-Web distribution
image and click OK.
The Web Application Manager displays a Progress dialog box and copies the
ICD files.
5. In the Web Applications list, select the distribution server instance you want to
add components to and click Modify.
The Web Application Manager displays the Modify Web Application dialog box.
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.
10. Provide the information for the required parameters and click OK.
Note • For descriptions of the rich client required parameters, see Rich
client distribution instance requirements. The other required
parameters vary, depending on the applications you are installing
with the rich client instance. For descriptions, see Rich client
distribution instance requirements.
The Web Application Manager begins installation of the solutions and displays a
Progress dialog box.
11. When installation is complete, click OK to close the Progress dialog box.
The Web Application Manager displays the Modify Web Application dialog box.
12. If the solution you added has optional parameters you want to modify, click
Modify Context Parameters.
The Web Application Manager displays the Modify Context Parameters dialog
box.
Note If you change a context parameter, the Over-the-Web Installer cannot
automatically update the rich client installation on user workstations.
Users must uninstall the rich client and reinstall it from this instance.
For example, if you add the Teamcenter lifecycle visualization embedded
viewer solution, and modify the PVisLicenseLevel context parameter,
users must uninstall and reinstall the rich client.
13. Type the values for the optional parameters and click OK.
Note For descriptions of the optional parameters, see Rich client optional
parameter values.
The Web Application Manager displays the Modify Web Application dialog box.
15. If you changed a context parameter value, notify users that they must uninstall
the rich client and reinstall from the same instance.
V Adding features
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
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/.
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.
Data Description
recommended that the number of pinged ports be
limited to no more than six. All members should
ping at least the same subset of primary server
managers so that tree caches connect and data is
shared.
Maximum servers in pool Maximum number of Teamcenter server processes allowed
to run in this pool (for a single-host configuration) or in this
subpool (for a multihost configuration).
Minimum warm servers Minimum number of Teamcenter server processes in this pool
that are started but not logged onto.
If necessary to maintain the minimum number of warm
servers, while not exceeding the maximum number of server
processes, the server manager times out servers in use.
Target number of server Target number of server processes to be available in this pool
processes or subpool during specified times.
You specify these values as time and integer pairs separated
by commas. For example:
0700 3, 1700 2
This value sets the target number of server processes as 3
between 7 a.m. and 5 p.m. and as 2 between 5 p.m. and 7 a.m.
• If the number of server processes is below the specified
target, warm servers are added to reach this number.
In this case, the number of warm servers exceeds the
minimum.
Note For server pool sizing recommendations, see the Teamcenter Deployment
Guide available on GTAC.
2. Proceed to the Features panel. Under Server Enhancements, select J2EE based
Server Manager.
4. In the Pool ID and JMX HTTP Adaptor Port boxes, type a name and port for the
server pool.
• Command Line
Specifies you want to run the server manager manually from a command line.
6. Enter the remaining values as needed in the Server Manager for J2EE panel.
For more information about these values, see Gather required information.
7. Click Next.
TEM displays the Server Manager TreeCache Configuration panel.
9. Proceed through remaining panels until you reach the Confirmation panel. Click
Start to begin installing the Teamcenter server with the J2EE-based server
manager.
11. If you install the server manager in Service/Daemon startup mode, a user
with root privileges must run the root postinstallation tasks script to register
the server manager daemon.
In the TC_ROOT/install directory, locate and run the following script:
root_post_tasks_id.ksh
You can install multiple J2EE server manager daemons on the same host. Each
server manager daemon 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 J2EE server manager in console
mode.
mgrstop Script that stops the J2EE server manager when started
from a command line.
If you run the J2EE server manager as a daemon, stop
the service using the rc.tc.mgr_config script.
Note You can also stop the server manager using J2EE
server manager administrative interface.
For more information, see the System
Administration Guide.
mgr.output If you run the J2EE server manager as a daemon, this
file contains all output from the J2EE server manager.
This file is not used if you run the server manager from
the command line.
logs Directory that contains all J2EE server manager log files.
If you run the J2EE server manager as a daemon, the server manager starts
automatically. If you run the server manager from the command line, you must start
the server manager manually.
For information about starting the J2EE server manager manually, see Start the
J2EE-based server manager.
For information about managing the J2EE server manager, see the System
Administration Guide.
Note If you experience connection delays during server manager startup, see
Troubleshooting four-tier architecture deployment for possible solutions.
The server manager displays several messages during startup. The server
manager started successfully if you see a message similar to the following that
contains an IP address and a port number:
-------------------------------------------------------
GMS: address is 153.172.61.24:17800
-------------------------------------------------------
Replace manager_host with the machine on which the manager is running, and
jmx_http_adaptor_port with the number of the port running a Java Management
Extension (JMX) HTTP adaptor. (You define this in Teamcenter Environment
Manager when you set the JMX HTTP Adaptor Port.)
2. To log on, use the default user ID (manager) and password (manager). You
can change these values using the Change_Authentication operation on the
Pool Manager page.
The server manager displays the Agent View page. Bookmark this page for
future reference.
For information about configuring the server manager, see the System Administration
Guide. Also, for information about using the server manager interface, see the
System Administration Guide.
For information about installing the Business Modeler IDE, see the Business
Modeler IDE Guide.
2. Proceed to the Solutions panel. In the Solutions panel, select Business Modeler
IDE, and then click Next.
When you select one of these options, a server connection profile is added in
the Business Modeler IDE.
For more information, see the Business Modeler IDE Guide.
d. In the Installation Directory box, enter the location where you want to install
the Business Modeler IDE. The Business Modeler IDE files are installed to a
bmide subdirectory.
e. Click Next.
4. In the Java Development Kit dialog box, click the browse button to locate
the JDK installed on your system. The kit is used for creating services. For
Teamcenter 10.1, use Java Development Kit 7 or later. Click Next.
b. Click the Edit button to the right of the 2-tier Servers box to change the
server connection profile settings, or click the Add button to add another
server to connect to.
C. Click OK.
d. Click Next.
• If you selected the Business Modeler IDE 4-tier option, perform the following
steps in the 4-tier server configurations panel.
a. Leave the Compress (gzip) the responses from the Web application
servers check box selected if you want faster connection performance
from the server.
b. Click the Add button to the right of the 4-tier Servers table if you want
to add another server to connect to.
c. Click Next.
o If you do not want to use TCCS, ensure that the Use TcCS Environments
for 4-tier clients check box is cleared and click Next.
If this check box is cleared, the 4-tier server configurations panel is
displayed after you are finished with the current panel.
d. Select Retrieve settings from URL and type a valid proxy URL to
use a proxy autoconfiguration file.
f. Select the Use TcCS Environments for 4-tier clients check box if
you want to use TCCS, or clear it if you do not. (This check box is
automatically selected if TCCS is installed.)
h. Click Next.
6. Perform the following steps in the Business Modeler IDE Client panel:
a. Click the Add button to the right of the table to select the templates to
install. Templates contain the data model for Teamcenter solutions. The
Teamcenter Foundation template is installed by default. The Foundation
template contains the data model used for core Teamcenter functions. All
customer templates must extend the Foundation template.
Select the same templates that were installed on the server so that you
can see the same data model definitions in the Business Modeler IDE that
were installed on the server.
Tip Make sure that you select the same templates that are on the
server. To find the templates installed on the server, look in the
TC_DATA\model directory on the server.
For more information, see the Business Modeler IDE Guide.
Note If you installed the EDA option to the Business Modeler IDE,
select the EDA Server and Rich Client Support template
(edaserver_template.xml).
c. Click Next.
• icons\template-name_icons.zip
Contains the icons used by that template.
• lang\template-name_template_language_locale.xml
Contains the text that is displayed in the Business Modeler IDE user
interface for all languages.
• template-name_dependency.xml
Lists the other templates that this template is built on top of, for example,
the Foundation template.
• template-name_template.xml
Contains the data model for this template, including business objects,
classes, properties, attributes, lists of values (LOVs), and so on.
• master.xml
Lists the template XML files included in the data model, for example, the
foundation_template.xml file.
For instructions about how to run the Business Modeler IDE, see Start the
Business Modeler IDE.
1. Ensure you have an Eclipse 3.8 package installed. To download Eclipse, see
the following URL:
http://archive.eclipse.org/eclipse/downloads/drops/R-3.8-201206081200/
5. Perform the following steps to extract the remaining plug-ins from the
additional_applications/bmide_plugins directory:
a. Extract each of the following archive files into its corresponding LocalSites
subdirectory. These archives contain plug-ins required by the Business
Modeler IDE.
• cdt-master-version.zip
Unzip to the CDT directory. This contains the C/C++ Development
Toolkit (CDT) plug-ins. CDT provides the capability to work with
projects that use C or C++ as a programming language.
• dtp-sdk_version.zip
Unzip to the DTP directory. This contains the Data Tools Platform (DTP)
plug-ins. DTP provides a number of tools for working with data sources.
• eclipse-JDT-SDK-version.zip
Unzip to the JDT directory. This contains the Java Development Tools
(JDT) plug-ins. JDT provides tools for implementing a Java IDE.
• emf-xsd-SDK-version.zip
Unzip to the EMF directory. This contains the Eclipse Modeling
Framework (EMF) plug-ins. EMF is a modeling framework and code
generation facility for building tools and other applications based on
a structured data model.
• GEF-ALL-version.zip
Unzip to the GEF directory. This contains the Graphical Editing
Framework (GEF) plug-ins. GEF allows developers to take an existing
application model and create a graphical editor.
• wtp-sdk-R-version.zip
Unzip to the WTP directory. This contains the Web Tools Platform
(WTP) plug-ins. WTP helps you develop Web and Java EE applications.
• NLpack2-GEF-SDK-version.zip
Contains the GEF language pack for Czech, Hungarian, Polish, and
Russian.
• NLpack2a-GEF-SDK-version.zip
Contains the GEF language pack for Danish, Dutch, Finnish, Greek,
Norwegian, Portuguese, Swedish, and Turkish.
• NLpackBidi-GEF-SDK-version.zip
Contains the GEF language pack for Arabic and Hebrew.
6. Launch Eclipse by running the eclipse file from the eclipse directory.
When Eclipse opens, set the workspace if asked and close the Welcome tab
if it appears.
http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.user/
tasks/tasks-124.htm
a. Choose Help®Install New Software from the top menu bar.
The Available Software dialog box is displayed.
b. In the Available Software dialog box, click the Add button to the right of the
Work with box.
The Add Site dialog box is displayed.
c. In the Add Site dialog box, click the Local button and browse to each
subdirectory under the LocalSites directory, for example, CDT\eclipse,
DTP/eclipse, and so on.
As you add each site, type a name for each in the Name box in the Add Site
dialog box. As you add sites, the plug-in items display on the Available
Software dialog box.
d. In the Available Software dialog box, click the arrow in the Work with box
and choose each site in turn (for example, CDT, DTP, and so on).
The plug-in items are displayed in the pane.
Note You must clear the Group items by category check box to see the
plug-in items. If you leave it selected, you may see the message:
There are no categorized items
Select the Hide items that are already installed check box to only
see uninstalled features.
Install plug-ins
e. Select all the items for the site and click Next to install them.
Install all the sites (CDT, DTP, and so on).
g. Restart Eclipse.
8. After all the plug-ins are installed, you should be able to open the Advanced
perspective. In Eclipse, choose Window®Open Perspective®Other and select
the Advanced perspective.
-Xmx1024M value to a higher number to allocate maximum Java heap size. For
example, if you have 2 GB available to dedicate for this purpose, set the value to
-Xmx2048M. Do this only if your machine has the available memory.
The Xms value in this file sets the initial Java heap size, and the Xmx value sets
the maximum Java heap size.
For instructions about how to run the Business Modeler IDE, see Start the Business
Modeler IDE.
Note To ensure that you have enough memory to run Eclipse, you can run
the Eclipse.exe command with a virtual memory argument. For
example, the following command increases virtual memory to 2 GB:
Eclipse.exe -vmargs -Xmx2024M
When you start the Business Modeler IDE for first time, the Welcome window
is displayed.
2. Click one of the buttons in the Welcome window to learn more about the
Business Modeler IDE:
• The Overview button provides links to online help topics.
• The Tutorials button provides links to tutorials.
3. To work in the IDE, click the Workbench button in the right side of the Welcome
window.
The Workbench is the main window in Eclipse. The Workbench window shows
one or more perspectives. A perspective is an arrangement of views (such as the
Navigator) and editors. At the top of the Workbench is a toolbar that allows you
to open new perspectives and move between ones already open. The name of the
active perspective is shown in the title of the window.
Note You can access the Welcome window again later by choosing
Help®Welcome from the Business Modeler IDE.
4. Examine the BMIDE view in the Standard perspective. This view provides a
centralized location for favorites, data model elements, and project files.
Note If a perspective fails to open, it could be that not enough memory is
being allocated to the Business Modeler IDE.
1. Copy the template files from the packaging directory on your Business Modeler
IDE client to a directory that is accessible by the server.
By default, packaged template files are located in the Business Modeler IDE
workspace directory in the folder under the project.
On Linux, users must have permissions to the workspace directory.
5. In the Configuration pane, select the configuration from which the corporate
server was installed. Click Next.
Note If you already installed a template to the database and want to update
the template, under the Teamcenter Foundation section, select Update
the database. This option should not be used to install a new template
but only to update an already installed template.
Use the Add/Update templates for working within the Business Modeler
IDE client option under Business Modeler Templates only if you want to
add a dependent template to your Business Modeler IDE.
7. In the Features panel, click the Browse button on the lower right side of the
panel.
8. Browse to the directory where you have copied the template files. In the
Files of type box, ensure that Feature Files is selected so that you see only
the installable template (feature) file. Select your template’s feature file
(feature_template-name.xml) and click the Select button.
The template appears as a new feature under Extensions in the Features panel.
You can change the location of the feature in the Features panel and add a new
group to place the feature under.
10. In the Teamcenter Administrative User panel, enter your user name and
password to log on to the server. Click Next.
11. The Database Template Summary panel displays the list of templates that are
installed as part of your template install. Click Next.
12. In the Confirmation panel, click Start. The new template is installed.
Note If the installation fails because of invalid data model, perform the
following steps:
a. Fix the incorrect data model and repackage the template.
13. To verify the installation of the new template, confirm that the TC_DATA
directory on the Teamcenter server contains the new template files.
Also log on to the server and confirm that you can create instances of your new
data model.
Note To have libraries read on the user system, the TC_LIBRARY
environment variable must be set to the platform-specific shared library
path. This environment variable is set to the LD_LIBRARY_PATH
(Solaris, Linux, or HP-UX Itanium), LIBPATH (AIX), or SHLIB_PATH
(HP-UX) environment variable, depending on the platform detected
when the Teamcenter session is initiated.
7. Click Next
8. In the Teamcenter Administrative User panel, enter your user name and
password to log on to the server. Click Next.
The Update Database panel displays currently installed templates.
9. Click the Browse button to navigate to the directory where the packaged
template files are located. Select the updated feature_template-name.xml file.
Note If you are fixing a COTS template (for example, the Foundation
template) using a new template file provided in a patch, you
must copy the template’s feature_template-name.xml and the
template-name_install.zip files to the same temporary directory
containing the new template-name_template.zip file.
12. To verify the installation of the revised template, log on to the server and confirm
that you can create instances of your new data model.
12 Manufacturing
Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
12 Manufacturing
Manufacturing
To populate the database with sample Teamcenter manufacturing process
management data, make sure that the Teamcenter corporate server is installed on
the installation host and the Teamcenter database is configured or upgraded.
MACH/resource/library/tool/inclass/dbc_mrl_tooling_library_tlas.tcl
MACH/resource/library/tool/inclass/dbc_mrl_tooling_library_tlas_en.def
MACH/resource/ug_library/dbc_mrl_general.tcl
New:
LIBRARY_TOOL,${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_mrl_tooling_library_tlas_en.def,
${UGII_CAM_LIBRARY_TOOL_INCLASS_DIR}dbc_mrl_tooling_library_tlas.tcl
If you use a customized configuration file at your company, make the change in
the customized file and continue to use this file to initialize NX CAM.
• Copy all associated files residing in the Genius4000 file system to the
Resource Manager import directories. Where necessary, these files
are converted to formats required for the import step.
Step 3: Import the Resource Manager data into the Teamcenter 8.x (or earlier)
Resource Manager database.
After you convert all the data, this step imports the results into an
existing Resource Manager database. This procedure is similar to that
required to install the small or full manufacturing content kit.
Step 4: Upgrade the Teamcenter 8.x (or earlier) database to your current
Teamcenter version.
For more information about performing this procedure on a UNIX system, see the
Installation on UNIX and Linux Servers Guide in the Teamcenter 8.x (or earlier)
installation.
Tablespace Description
Small Typical number of rows 1000. Minimum size 50MB Growth
is very slow.
Medium Typical number of rows 10000. Minimum size 150MB
Growth is Slow.
Large Typically 1000000 rows or more. Minimum size 500MB
Growth very rapid with usage.
Tablespace Description
Indexes Typically 1000000 rows or more. Minimum 400MB.
For more information about creating the metadata database for Reporting and
Analytics, see Planning for Installation in the Teamcenter Reporting and Analytics
Deployment Guide for the current version of Reporting and Analytics.
Note For information about starting the Reporting and Analytics license server,
see the Teamcenter Reporting and Analytics Deployment Guide in the
Reporting and Analytics software distribution image.
Dashboard
Installs the Reporting and Analytics Dashboard application for the rich
client. Dashboard provides an embedded viewer for Reporting and Analytics
reports in the rich client.
For more information about the Reporting and Analytics Dashboard, see the
Report Builder Guide.
3. Proceed to the TcRA Install Options and General Settings panel. Select one
or more of the following options to include in your Reporting and Analytics
installation:
The remaining sequence of TEM panels varies according to the options you select.
4. Enter the required information in TEM for the selected Reporting and Analytics
options.
Note
For more information about any TEM panel, click the help button .
5. Proceed through the remaining TEM panels and begin installing Reporting
and Analytics.
During installation, TEM prompts you for the location of the TCRA2008.zip file.
When installation is complete, close TEM.
Value Description
Host Specifies the host on which you deploy the
Reporting and Analytics WAR file.
Port Specifies the port used by the Reporting and
Analytics Web application.
Context Specifies the name of the Reporting and
Analytics WAR file
ServletName Specifies the name of the Reporting
and Analytics servlet, for example,
BuildNPlay/eQTCnectIntegrationController.
If connections are not successful, you cannot create reports in Reporting and
Analytics until connection problems are resolved.
For more information about Reporting and Analytics Mapper and BuildNPlay,
see the Mapper User’s Guide and the BuildNPlay User’s Guide in the Reporting
and Analytics software distribution image.
3. Log on to the Reporting and Analytics administrative console using user name
ADMIN and password ADMIN.
Click Manage Instance→Properties, and then set the following values as
appropriate:
• SMTP Host
• SMTP User ID
4. If Reporting and Analytics is installed with Security Services enabled, set the
following values for the Teamcenter connection (Connection 1):
• Set the user ID and password values to the LDAP user ID and password.
• Under Advanced Properties, set SSO Enabled to yes, and set the SSO
Application ID to the Teamcenter application ID.
Note For information about using the Reporting and Analytics integration, see the
Report Builder Guide.
For more information about working with document management IRDC objects
and dispatcher service configuration objects, see the Business Modeler IDE
Guide.
The software needed for rendering is dictated by the available input formats and the
required output formats.
1. Supported MS Office formats include Microsoft Word, Excel, PowerPoint, WordX, ExcelX and PPTX, unless otherwise noted.
2. In the Dispatcher Components panel, specify the Dispatcher root directory. For
example, you can use:
C:\Program Files\Siemens\Teamcenter9\dispatcher
3. In the Dispatcher Components panel, select Install Module, and then enter a
Staging Directory and Port for the module.
6. In the Translator Settings panel, under TcVis Translators, enter the installation
location for Teamcenter lifecycle visualization, and the Vis License value. Under
Document Management (DocMgt) Translators, enter the paths to the watched
folder input and output directories, and a maximum wait time.
Note The watched folder input and output directories must point to the
same location as the Adobe LiveCycle watched folder input and result
directories, respectively.
For more information about configuring these directories, see the Adobe
LiveCycle ES documentation.
and:
Dispatcher\Module\Translators\docmgt_translators\
.....config\pdfgenerator_config.properties
Dispatcher\Module\translators\docmgt_translators\
config\pdfgenerator_config.properties
Set:
• WatchedFolderInputDir=//pdfgenerator_server/LCWatchedFolder/input
• WatchedFolderResultDir=//pdfgenerator_server/LCWatchedFolder/result
Note These case-sensitive paths can be in a shared network directory, but
must point to the same locations as the Adobe LiveCycle watched
folder directories configured for GeneratePDFService WatchedFolder
Endpoint. See the relevant documentation at the Adobe website,
http://www.adobe.com/products/acrobat/, for instructions on how to set
up WatchedFolder directories.
• Use Business Modeler IDE to select the service for file translation by setting
DispatcherServiceConfig sort order priority for the previewservice service
and for the pdfgenerator service. The service with the higher sort order
priority is selected when you have multiple translation services defined with the
same settings for Source Dataset Type Name and Derived Dataset Type Name.
You can also deselect the Service Available setting for a translation service to
make the service unavailable.
• Create access rules to grant access privileges to the dispatcher proxy user to
update attributes of the dispatcher request object.
For more information about creating access rules, see Getting Started with
Dispatcher (Translation Management).
• Start the dispatcher services for the scheduler, module, and dispatcher client.
For more information about starting dispatcher services, see Getting Started
with Dispatcher (Translation Management).
• If you have configured logging for dispatcher requests, you can see the document
render logs in the Request Administration Console.
For more information about using the Request Administration Console, see
Getting Started with Dispatcher (Translation Management).
http://support.industrysoftware.automation.siemens.com/
certification/teamcenter.shtml
For information about using Teamcenter online help, see Getting Started with
Teamcenter.
The following table describes various ways you can access Teamcenter online help
collections.
Notes:
2. For the PDF collection, full-collection search is not available over HTTP
protocol.
4. The HTML and PDF online help collections for the current version of
Teamcenter are available at the following URL:
http://support.industrysoftware.automation.siemens.com/docs/teamcenter
If you install online help in a rich client configuration using TEM, online help access
from the rich client is configured automatically.
If you install online help in a thin client Web application, online help access from the
thin client is configured automatically.
If you install online help on a separate host or in a separate Teamcenter
configuration, you can configure clients to access those separate online help
installations.
After online help for the rich client or thin client is installed and configured, you can
view online help from the Help menu in the client.
For more information, see Getting Started with Teamcenter.
Note The PDF online help collection is not accessible though the Help menu in
Teamcenter rich client or thin client.
• Install online help manually on a local host or network file location from the
documentation distribution image.
If you want to configure clients to access online help installed on a separate host,
see Configure online help access for Teamcenter clients.
5. Proceed to the Online Help panel. Select the online help components you want
to install.
Component Description
Teamcenter online help library Installs the Teamcenter online help library.
This component is required.
This component requires approximately 561
MB of disk space.
Teamcenter developer Adds the Teamcenter developer references
references to the online help collection. The following
references are added to the Developer
References for Customization group in the
online help library:
• C++ API Reference
• Integration Toolkit (ITK) Function
Reference
• Services Reference
Component Description
Teamcenter Data Model Adds the Teamcenter Data Model Report to the
Report Developer References for Customization group
in the online help library.
The Teamcenter Data Model Report contains
documentation on standard Teamcenter
data model objects, such as business objects,
classes, attributes, properties, lists of values
(LOVs), and others.
This component requires approximately 3.44
GB of additional disk space and requires
significantly more time to install.
Note The Teamcenter Data Model Report
is installed only to the Teamcenter
HTML Help Collection. It is not
available in PDF format, and
therefore is not installed to the PDF
collection.
Teamcenter PDF help Installs the Teamcenter online help collection
collection in PDF format on your local host.
After installation, you can open the online
help collection from the following location:
TC_ROOT/PDF/index.html
This component requires approximately 344
MB of additional disk space.
6. Proceed to the Confirmation panel, and then click Start to install online help.
During installation, TEM prompts for the location of the online help files.
Enter the path to the location that contains these files on the Teamcenter
documentation distribution image.
Note • You can later add or remove online help components using TEM in
maintenance mode:
1. Proceed to the Feature Maintenance panel.
• After you install online help using TEM, you can view online help from
the Help menu in the rich client.
For more information, see Getting Started with Teamcenter.
2. Expand online help files to a directory on your local host or a network file
location.
File Description
tchelp.jar Contains the Teamcenter online help library. This
file is required and must be expanded before any
other online help files.
This file requires approximately 561 MB of disk
space.
tcrefs.jar Contains the Teamcenter developer references.
This file is optional.
Expanding this file added the following references
to the Developer References for Customization
group in the online help library:
• C++ API Reference
• Integration Toolkit (ITK) Function Reference
• Services Reference
File Description
DataModelReport.zip Contains the Teamcenter Data Model Report. This
file is optional.
Expanding this file adds the Teamcenter Data
Model Report to the Developer References for
Customization group in the online help library.
The Teamcenter Data Model Report contains
documentation on standard Teamcenter data
model objects, such as business objects, classes,
attributes, properties, lists of values (LOVs), and
others.
This component requires approximately 3.44 GB
of additional disk space.
Note The Teamcenter Data Model Report is
installed only to the Teamcenter HTML
Help Collection. It is not available in PDF
format, and therefore is not installed to
the PDF collection.
PDF.zip Contains theTeamcenter online help library in
PDF format. This file is optional.
This component requires approximately 344 MB
of additional disk space.
3. If you want other hosts to access online help, set permissions for the HTML
online help directory (help) or the PDF online help directory (PDF) as needed
to allow access to other hosts.
After installation, you can open the online help collection from the following
locations:
• HTML online help:
help-directory/help/index.html
You can use this same method to install the online help on a Web (HTTP) server.
Rich client or thin client hosts can be configured to access the HTML online help
collection over a Web server.
For more information, see Configure online help access for Teamcenter clients.
Note The PDF online help collection cannot be accessed through the rich client or
thin client.
3. In the Add Web Application dialog box, type a name and enter a staging location
for the online help Web application.
In the Solution Type box, select Thin Client.
4. In the Disk Locations for Install Images box, enter the path to the tchelp.jar
file on the Teamcenter 10.1 documentation distribution image.
5. Click Solutions.
6. In the Select Solutions dialog box, select the Teamcenter - Online Help solution,
and then click OK.
9. Locate the deployable file generated during installation. This file is in the
deployment directory under the specified staging location.
Deploy the Web application as described in the Web Application Deployment
Guide.1
After you install online help using TEM, you can view online help from the Help
menu in the thin client.
For more information see Getting Started with Teamcenter.
Note • Additional online help components, such as the Teamcenter developer
references and Teamcenter Data Model Report, cannot be installed on
the J2EE Web tier. The Web Application Manager installs only the core
Teamcenter online help library.
• If you have additional thin client Web applications that do not contain
online help, you can configure those applications to access online help
installed in another thin client Web application.
For more information, see Configure online help for the thin client.
1. The Web Application Deployment Guide provides deployment procedures specific to various supported application servers. Choose
the appropriate procedure for the application server you use.
Preference Description
WEB_core_help_server Set to the full path to the launch page for the
online help collection, including the application
name, for example, /tc/help/index.html.
WEB_help_server Set to the URL of the thin client help, for
example, /tc/help/index.html
#filename:thin_client_dhtml:getting_started
For more information about these preferences, see the Preferences and Environment
Variables Reference.
For information about setting preferences, see the Preferences and Environment
Variables Reference.
Note This procedure assumes you have an existing deployed thin client Web
application that contains the Teamcenter - Online Help solution.
For information about creating a thin client Web application that contains
Teamcenter online help, see Install online help on the J2EE Web tier.
b. Select the two-tier or four-tier rich client, but do not select the Online
Help feature.
Note For more information about installing a two-tier or four-tier rich
client, see the Installation on Linux Clients Guide.
• Existing configuration:
3. Proceed to the Rich Client Settings panel. Select the Enable online help check
box.
4. In the Rich Client Settings panel, select the Enable online help check box, and
then specify how you want the rich client to access online help.
b. Enter the path to the installed online help, for example, /tc/help.
b. Type the URL to the location of the Teamcenter online help collection,
for example, http://host:port/tc/help.
5. Proceed to the Confirmation panel, and then click Start to update the Teamcenter
configuration.
For more information about these parameters, see Rich client distribution
instance requirements.
Note For more information about creating a rich client distribution instance,
see Install rich client distribution instances.
For more information about modifying an existing rich client distribution
instance, see Add components to the distribution server instance.
Create a configuration
1. Start Teamcenter Environment Manager (TEM):
a. Change to the install directory in the Teamcenter application root directory
for your Teamcenter installation.
4. In the Configuration panel, type a description and unique ID for the new
configuration.
8. When TEM displays the Confirmation panel, click Start to begin installation.
Modify a configuration
Add Teamcenter features to an existing configuration, or remove them from a
configuration:
1. Start Teamcenter Environment Manager (TEM):
a. Change to the install directory in the Teamcenter application root directory
for your Teamcenter installation.
4. In the Old Configuration panel, select the configuration you want to modify.
8. When TEM displays the Confirmation panel, click Start to begin installation.
4. Proceed to the Features panel. Select the Teamcenter Foundation feature only
and specify an installation directory for the new configuration the Installation
Directory box. The installation directory must not already exist on your system.
(TEM creates the directory.)
5. In the Foundation panel, select Use populated database and existing data
directory and enter the full path to the existing data directory in the Data
Directory Location box.
6. In the Data Directory box, enter a location for the Teamcenter data directory.
The directory must exist.
The Teamcenter data directory is called the TC_DATA directory. This value is
stored in the TC_DATA environment variable on your system. TEM creates
shared data subdirectories and files in this location.
Do not set TC_DATA in the system environment. TEM sets this variable as
required in various scripts. Setting this variable in the operating system can
cause conflicts if you install more than one configuration.
7. In the Teamcenter Administrative User panel, enter the password for the
Teamcenter administrator.
Caution Make sure the password does not contain space characters or any of
the following characters:
!@$%’": ;.<>(){}
8. In the Confirmation panel, review your selections and click Start to add the
database.
For information about installing a database server and database instances, see
Database server installation.
4. Proceed to the Features panel. Select the Teamcenter Foundation feature only
and specify an installation directory for the new configuration the Installation
Directory box. The installation directory must not already exist on your system.
(TEM creates the directory.)
5. In the Foundation panel, select Create new data directory using existing
populated database.
6. In the Foundation Database panel, enter access information for the existing
database.
In the Data Directory box, enter a location for the Teamcenter data directory.
The directory must exist.
The Teamcenter data directory is called the TC_DATA directory. This value is
stored in the TC_DATA environment variable on your system. TEM creates
shared data subdirectories and files in this location.
Do not set TC_DATA in the system environment. TEM sets this variable as
required in various scripts. Setting this variable in the operating system can
cause conflicts if you install more than one configuration.
7. In the Teamcenter Administrative User panel, enter the password for the
Teamcenter administrator.
Caution Make sure the password does not contain space characters or any of
the following characters:
!@$%’": ;.<>(){}
8. In the Confirmation panel, review your selections and click Start to add the
database.
2. Create a temporary environment variable and set it to the password you want to
encrypt:
set variable-name=password
For example:
set temp_pw=mypassword
Note For security, choose a unique and obscure name for the environment
variable, and delete the variable promptly after completing this
procedure.
Replace variable-name with the name of the environment variable you created.
Replace password-file with the path and name of the password file to create.
For example:
install -encryptpwf —e=temp_pw —f=pwd.txt
This command generates an encrypted password file that can be used for
connecting to the Teamcenter database. The password file can also be used with
Teamcenter utilities that use the password file (-pf) argument.
For more information about the -encryptpwf argument for the install utility, see
the Utilities Reference.
Replace db-user with the database user name (the Oracle user). Replace
password with the new database password. Replace database-ID with the Oracle
database name.
This command generates a new database connection string with the new Oracle
password encrypted . Copy the new database connection string.
6. Replace the existing connection-string with the string generated by the install
-encrypt command.
• In the Web tier, deploy two Web tier files, each connecting to one of the server
managers.
Four-Tier
Rich Client
FSC Parent=
TcHost1:4444
http://appserver:7001/tc/webclient http://appserver:7002/tc/webclient
tc.ear tc.ear
TreeCache= TreeCache=
ClusterTcData1 ClusterTcData2
<fmsworld>
<multisiteimport siteid="400783129"> FMS
<defaultfscimport fscid="FSC_TcHost2 FSC_TcHost2
fscaddress="TcHost2:4444" priority="0"/>
</multisiteimport>
Server Manager
Server Manager
TreeCache=
TreeCache= ClusterTcData2
ClusterTcData1
TC Server n TC Server n
TcHost1 TcHost2
TcData1 TcData2
To enable a rich client to access two databases, install and configure two corporate
servers:
• Select the server manager component and configure it with the TreeCache
cluster name of ClusterTcData1.
• Select the server manager component and configure it with the TreeCache
cluster name of ClusterTcData2.
3. On TcHost1, edit the FMS master file to make FMS aware of the FSC on
TcHost2:
a. Go to the fms directory in the Teamcenter application root directory.
c. Edit the lines, adding the bold text and deleting the indicated text:
Original:
<fmsworld>
<multisiteimport siteid="othersite">
<defaultfscimport fscid="otherfsc" fscaddress="host:4444" priority=”0”/>
<volumeimport volumeid="othervol" />
</fscimport>
</multisiteimport>
Revised:
<fmsworld>
<multisiteimport siteid="othersite">
<defaultfscimport fscid="otherfsc" fscaddress="host:4444" priority=”0”/>
</multisiteimport>
• Replace the value for the fscid parameter with the FSC ID on TcHost2.
This value is in the FMS master file on TcHost2 in the fsc id parameter.
• Replace the value for the fscaddress parameter with the host name and
port number of host 2. This value is in the FMS master file on TcHost2
in the fsc address parameter.
For example:
<fmsworld>
<multisiteimport siteid="400783129">
<defaultfscimport fscid="FSC_TcHost2" fscaddress="TcHost2:4444" priority=”0”/>
</multisiteimport>
1. Generate the Web tier EAR file, configuring it to connect to the server manager
of TcHost1 by specifying the same values for the TreeCache cluster name and
TreeCache mode.1
For example:
2. Generate the Web tier EAR file, configuring it to connect to the server manager
of TcHost 2 by specifying identical values for the TreeCache cluster name and
TreeCache mode.
For example:
Note Make sure you choose distinct sets of ports for each EAR file.
3. Deploy each Web tier EAR file in a third-party application server in a separate
domain.
Users who install this rich client instance, can choose from two databases, TcData1
and TcData2, when logging on to Teamcenter.
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.
1. For the ParentFSCAddressTable parameter, specify the host name and port
number of TcHost1. For example:
TcHost1:4444
TcHost1 has the site information about the FSC on TcHost2.
2. For the HTTPServerTable parameter, specify two URLs, one for each deployed
Web tier application. For example:
URI Name
http://appserver:7001/tc/webclient TcData1
http://appserver:7002/tc/webclient TcData2
To change the JRE used by Teamcenter and TEM, perform the following steps.
1. Start Teamcenter Environment Manager (TEM):
a. Change to the install directory in the Teamcenter application root directory
for the Teamcenter installation or configuration you want to modify.
2. In the Maintenance panel, select Migrate Teamcenter to another JRE and then
click Next.
3. The Migrate Teamcenter to another JRE panel lists Teamcenter services that
depend on the JRE and must be shut down before the migration can begin.
After you make sure these services are shut down, select All features from the
above list have been shut down, and then click Next.
4. In the JRE Location panel, enter the path to the JRE you want Teamcenter to
use.
Caution If you use 64-bit Teamcenter, make sure you specify a 64-bit JRE.
Similarly, for 32-bit Teamcenter, you must specify a 32-bit JRE.
Note Depending on the features in your configuration, TEM may prompt you
for the operating system user password.
If you encounter problems migrating Teamcenter to the new JRE, see Problems/error
messages.
1. The locale code for Hebrew is en_US because Siemens PLM Software does not yet provide a Hebrew translation. The en_US code
allows data entry in Hebrew, but interface text is in English.
2. Standard locale codes are composed of a two lowercase character language code from the ISO 639-1 standard, followed by an
underscore, followed by a two uppercase character country code from the ISO 3166-1-alpha-2 standard.
Note o When specifying a language in the URL, use standard W3C locale
identifiers.
For more information, see the following URL:
http://www.w3.org/TR/ltli/
http://[2001:db8:ffff:1:101:12ff:de13:1322]:9043/tc
Your ability to set the language for the thin client depends on the character set
encoding of the Teamcenter server host and also the character set encoding of the
Teamcenter database.
Note To prevent mixed-language display after you change the thin client display
language, clear your Web browser cache. This prevents the interface from
displaying in mixed languages.
For more information about configuring language display during installation, see
Installing thin client Web applications.
Note • Your ability to set the language for the rich client depends on the
character set encoding of the Teamcenter server host and also the
character set encoding of the Teamcenter database.
For more information about configuring language display during
installation, see Installing rich client Web applications.
• If you find that Asian multibyte characters do not display correctly in the
rich client, set your system font to a font that supports Asian multibyte
characters. For example, on Microsoft Windows systems, the Arial
Unicode MS font can be set to Message Box to correct this problem.
Similarly, if you find that Asian multibyte characters do not display
correctly when you start the rich client using the native language (-nl)
option, restart your system in the appropriate locale and set your system
font to a font that supports Asian multibyte characters.
If you want to override the default language to launch the rich client in a desired
language, add the -nl argument to the rich client launch command:
TC_ROOT/start_portal –nl locale-code
Replace TC_ROOT with the Teamcenter home directory, and replace locale-code with
the desired locale code listed in Deploying localized versions of Teamcenter.
For example, to launch the rich client Italian user interface, enter the following
from a command prompt:
/tc/rac/start_portal –nl it_IT
Note To prevent mixed-language display the next time you run the rich client
after you change the –nl argument value, or after you change your operating
system locale, delete the Teamcenter directory under your user directory
($HOME/Teamcenter3).
• Spanish
To ensure correct display and processing of Teamcenter data, set the required values
in your operating system environment. Use the appropriate values for your locale
and platform.
• If you use Linux, your Linux platform administrator must configure the machine
to run Unicode UTF-8 character set operating system by default. This enables
all software running on this platform operating system to understand the default
UTF-8 character set.
• Make sure you configure your operating system to run Unicode UTF-8 before
you configure a Teamcenter two-tier or four-tier server installation to run the
UTF-8 character set.
• You must configure the Teamcenter thin client to connect to a four-tier UTF-8
server installation running on a Unicode UTF-8 UNIX or Linux operating
system.
The thin client can be run in a Web browser on any Siemens PLM Software
supported platform and language character set encoding operating system.
• A new Teamcenter installation may configure support for the Unicode UTF-8
character set to install a new database configured with Unicode UTF-8 character
set support.
Note • The thin client or the four-tier rich client can run on any platform
(Windows, UNIX, or Linux) running any language character set.
• Rich client hosts must have the appropriate fonts installed for characters
to display properly.
Warning If your Teamcenter database server uses the UTF-8 character set, you
must not install your Teamcenter corporate server on a Windows host.
Teamcenter data from a UTF-8 database may display incorrectly in a
two-tier rich client on Windows and can become corrupted if you modify
data using a Windows-based corporate server or two-tier rich client.
Caution On IBM AIX systems, in locales that use commas for decimal points
(for example, French), do not set the LC_ALL environment variable.
Instead, make sure the LC_NUMERIC environment variable is set
to a value of C.
Setting LC_ALL on IBM AIX systems overrides the LC_NUMERIC
setting and causes input string errors in the rich client.
For more information about this issue, see software field bulletin
SFB-Teamcenter-5972 on GTAC:
http://support.industrysoftware.automation.siemens.com
Notes:
Notes:
Notes:
Note • To verify the character set in your server environment, enter the
locale charmap command.
Value
Notes:
Value
Notes:
Value
Notes:
Note • To verify the character set in your server environment, enter the
locale charmap command.
Deploying localizations
Build and deploy localizations to the Teamcenter thin client and rich client using
the Web Application Manager.
Note For more information about applying localizations to Teamcenter, see the
Localization Guide.
The thin client text server files reside under the Teamcenter application root
directory in the /lang/textserver/locale-code directory. If you change one of the text
server XML files (*_locale.xml and *_errors.xml), regenerate the webstrings.xml
file:
1. Change to the
WEB_ROOT/staging-location/webapp_root/teamcenter/dhtml/common/intl
directory in the Teamcenter application root directory.
2. Copy all files from the en_US directory to the new language directory.
3. In the new language directory, translate all XML files to the new language.
Note Make sure the encoding specification at the top of each XML file matches
your system encoding when you save the file. Also, make sure the
encoding specified supports the desired locale.
For Hebrew on Windows systems, the encoding specification should
resemble the following example:
<?xml version="1.0" encoding="windows-1255" standalone="yes"?>
4. Edit the weblocal_locale.xml file in the new language directory to change the
value of the web_local_lang parameter from en to the new language name.
For example, if you localize the user interface for Hebrew, change the
web_local_lang parameter to he:
web_local_lang: exported "he";
Replace lang-code with the W3C standard language code and locale-code with
the Java standard locale code.
For example, in Hebrew locales, this key would resemble the following:
<key id="textsrv_associatedDefaultJavaLocale_he">iw_IL</key>4
Note On UNIX and Linux systems, after you complete this step, remove
shared memory backing store files.
7. Change to the
WEB_ROOT/staging-locationteamcenter\dhtml\commmon\intl directory
and create a new language directory.
For example, if you localize the user interface for Hebrew, create the he directory.
8. Copy all files from the en directory to the new language directory.
9. In the new language directory, translate all XML files to the new language.
1. Copy the base file to a temporary file name, for example, from
aif_locale.properties to aif_locale_temp.properties.
4. Run the native2ascii utility against the temporary properties file to convert it
to a Unicode properties file.
The native2ascii utility is in the \bin directory of Java SDK 1.4.
For more information, access the following URL:
http://download.oracle.com/javase/6/docs/technotes/tools/windows/native2ascii.html
For example, to convert the properties file from Japanese to Unicode, enter the
following command from the command line:
native2ascii -encoding SJIS aif_locale_temp.properties aif_locale_ja_JP.properties
The final locale-specific properties file or the output of the native2ascii file must
have the base_locale_locale-id_language-id.properties file format.
The rich client finds the value of a key in the following order:
BASE_user.properties
BASE_locale-ID_language-ID.properties
BASE_locale.properties
BASE.properties
http://java.sun.com/j2se/1.4/docs/guide/intl/font.html
For more information about converting files to unicode, see the Unicode Consortium
Web site:
http://www.unicode.org/
• Italian
• Japanese
• Korean
• Polish
• Portuguese (Brazilian)
• Russian
• Spanish
4. Run the native2ascii utility against the temporary properties file to convert it
to a Unicode properties file.
The native2ascii utility is in the \bin directory of Java SDK 1.4.
For more information, access the following URL:
http://download.oracle.com/javase/6/docs/technotes/tools/windows/native2ascii.html
For example, to convert the properties file from Japanese to Unicode, enter the
following command from the command line:
native2ascii -encoding SJIS aif_locale_temp.properties aif_locale_ja_JP.properties
The final locale-specific properties file or the output of the native2ascii file must
have the base_locale_locale-id_language-id.properties file format.
The rich client finds the value of a key in the following order:
BASE_user.properties
BASE_locale-ID_language-ID.properties
BASE_locale.properties
BASE.properties
http://java.sun.com/j2se/1.4/docs/guide/intl/font.html
For more information about converting files to unicode, see the Unicode Consortium
Web site:
http://www.unicode.org/
• 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.
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.
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.
- <tcdata guid="4500621E2BE24BF0DD6ABF31EBA01088">
<path value="C:\\Program Files\\Siemens\\tcdata1" />
<create value="true" />
</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="35EE6A6B3D91876B85467D5EDE51EACE">
<siteListString value="" />
</FccSite>
- <FSCServiceConnections guid="E4BDA0B52E123C9F1CB10A49F0C326F1">
<connections value="http,4545,;" />
</FSCServiceConnections>
- <OSUser guid="CA769D31FD7E1A0BBBD722E5E509E809">
<password value="ENCRYPTED:3448ee60e4c8a0c248" />
<user value="LM6S003\\yytcadm" />
</OSUser>
- <flexClient guid="7221ECFBC9555CDF997FC3F575022761">
<nX5String value="28000@svnxflex1;28000@svnxflex2" />
<port value="27000" />
<nX4String value="27000@trlic001;27000@trlic002" />
<nX5Port value="28000" />
<host value="trlic001" />
<nX5CheckBox value="true" />
<nX5Host value="svnxflex1" />
<envServerString value="28000@svnxflex1;28000@svnxflex2" />
</flexClient>
- <foundationSettings guid="LHBY67HDNDHFJTZYMYHSKED26FZD84I7">
<genClientCache value="delete" />
<genServCache value="" />
<enableGenServCache value="true" />
</foundationSettings>
- <transientVolume guid="983980098FF188A8C4BF08E8168A32A8">
<windowsVolume value="C:\\Temp\\transientVolume_tc_user" />
<unixVolume value="/tmp/transientVolume_tc_user" />
</transientVolume>
- <TcOracleSystem guid="1EF0859AC04962CBFA41C4C8C84499A1">
<password value="ENCRYPTED:3448ee60e4c8a0c248" />
<user value="system" />
<tablespaces value="tc_user_IDATA:90;tc_user_ILOG:5;tc_user_INDX:5;tc_user_TEMP:5" />
<tablespacePath value="c:\\tc_mydata" />
</TcOracleSystem>
- <volume guid="1F16971107DE44C0C7827F800EE4AEF8">
<port value="4545" />
<fscModel value="Simple Model" />
<location value="C:\\Program Files\\Siemens\\volume1" />
<name value="volume" />
<hostName value="lm6s003" />
<fscId value="FSC_myfsc" />
</volume>
- <TcOracleEngine guid="F4F7C0852B27D6E56B8C64BE77FFA14C">
<port value="1521" />
<createUser value="true" />
<host value="lm6s003" />
<flush value="false" />
<populate value="true" />
<service value="tc" />
<password value="ENCRYPTED:34eae6cae4e8c6be" />
<user value="tc_user" />
<create value="true" />
</TcOracleEngine>
</data>
- <features>
<add feature="A0CF69C3A0BC61770EB81BD22667EA52" name="VC 2005/2008 Redistributables" />
<add feature="90C2A1C96F6A61FAB397AF88ABE4AAC1" name="FMS Server Cache" />
<add feature="8C061DD51E13E0CB9DC4687B1A3348BE" name="Teamcenter Foundation" />
<add feature="B176F6B6E9E91D9804EFB0D2010FD613" name="NX Integration" />
</features>
</config>
<updateManager />
<webAppManager />
</root>
1. Log on to the Teamcenter corporate server host and change to the root directory
of the Teamcenter software distribution image.
• product-level_number_OTW.zip
Contains the OTW rich client patches and distribution server patches
• product-level_number_PV_all.zip
Contains the Teamcenter Visualization patches
• product-level_number_install.zip
Contains the TEM updates
Before you apply downloaded Teamcenter 10.1 patches to your server, you must
do the following:
• Stop all Teamcenter 10.1 related processes and services (such as FSC, database
daemons, and so on).
Note TEM does not allow you to install patches for a version of Teamcenter that
is earlier than your current installation. For example, you cannot apply a
Teamcenter 2007.1 patch to a Teamcenter 10.1 installation.
4. Enter the following command to expand the install.zip file, overwriting existing
files:
unzip –o install.zip
Note If errors occur while expanding the file, do one of the following tasks:
• Add the path to your TC_ROOT/install/install directory to your
PATH environment variable and enter the unzip command again.
5. Add execute permissions back to the tem.sh shell script with the following
command:
chmod 755 tem.sh
2. Stop all Teamcenter services before you begin the update process.
b. Backup directory
Enter the location in which you want to store backups of files replaced
during the update process.
Click Next.
Note All users logged on to the environment are notified that it will not
be available until the update process is complete. Make sure all
Teamcenter clients and processes on the host are stopped before you
continue. If Teamcenter services or processes are running, the update
may fail because TEM cannot copy replacement files from the patch to
the installed location.
8. Once the server is successfully patched, you must manually update your
TC_DATA directories.
d. Copy the tc_profilevars file from the backup to the TC_DATA directory.
9. Follow the instructions in the patch’s README file for any additional steps
required to complete the patch.
Restart all Teamcenter-related processes and services (such FSC, database daemons,
and so on).
Note Each time you add a new feature to your installation, reapply installed
patches because the added feature’s files may have been patched previously.
Adding a feature can overwrite that feature’s patched files with the older
files from the original software distribution image.
Replace patch-path and patch-directory with the full path to the location in
which you expanded the patch-id.zip file.
This procedure launches TEM and applies the patch with no user interaction
required.
Note You must enclose the path to the patch in quotation marks (") for paths that
contain spaces in them. For example:
tem.sh —p "/../Teamcenter patches/patch-location"
4. Click the Copy ICD button. Browse to the expanded patch location to select the
icd directory, and then click OK to copy the ICD files to the Web Application
Manager.
5. Select the installed rich client instance you want to patch and click Modify.
The Web Application Manager displays the Modify Web Application dialog box.
7. Click Add and add the patch location to list of disk locations for install images.
8. Select and install patches. If you add patches to a previously patched instance,
the steps differ from the first patch installation.
b. Select Rich Client Patch and click b. In the Reinstall Solution dialog
OK. box, click OK.1
After the installation is complete, the instance and the modified instance contains
the patch. Any rich clients previously installed from this instance has the patch
1. Adding patches reinstalls the patch solution with the newer files.
applied the next time the rich client is launched. Future rich client installations are
installed with the patch.
Note Customer-specific patches are not cumulative like general Teamcenter
patches and business urgent patches are. To install customer-specific
patches to the rich client using the Over-the-Web Installer, perform the
following steps:
1. Install a single customer-specific patch.
3. Click the Copy ICD button. Browse to the expanded patch location to select the
icd directory, and then click OK to copy the ICD files to the Web Application
Manager.
4. Select the rich client instance that contains the Teamcenter Visualization 8
(Embedded) for Rich Client 4-Tier (Installation and Configuration) solution
and click Modify.
The Web Application Manager displays the Modify Web Application dialog box.
6. Click Add and add the patch location to list of disk locations for install images.
7. Select and install patches. If you add patches to a previously patched instance,
the steps differ from the first patch installation.
d. After the patch is installed, click e. After the patch is installed, click
OK to close the Progress dialog OK to close the Progress dialog
box. box.
After the installation is complete, the instance and the modified instance contains
the patch. Any rich clients previously installed from this instance has the patch
applied the next time the rich client is launched. Any future rich client installations
are installed with the patch.
2. Open the WEB_ROOT directory and run the Web Application Manager (insweb).
2. Adding patches reinstalls the patch solution with the newer files.
5. Select the Web application in the list corresponding to your Web tier installation
and click Modify.
6. In the Modify Web Application dialog box, click Modify Disk Locations.
7. In the Modify Disk Locations dialog box, click Add button to add the
WEB_FILES_LOC\Web_tier directory to the Disk Locations for Install Images
list.
10. In the confirmation dialog box, click Yes to confirm the changes to the disk
location list prior to opening to the Reinstall Solutions dialog box.
12. If the Modify Required Context Parameters dialog box appears, type the
appropriate values for any required context parameters and click OK.
13. The Web Application Manager regenerates the Web tier web application with the
patched files. Make sure a deployable file (EAR or WAR) is generated during
this process. If it is not, click Generate Deployable File in the Modify Web
Application dialog box.
14. After the deployable file is generated, go to the Web tier Web application’s staging
directory and find the deployable file (EAR or WAR) under the deployment
directory.
15. Take the new deployable file and deploy it to your Web application server,
replacing the previous deployment. The new deployable file contains the Web
tier patches.
20 Uninstalling Teamcenter
20 Uninstalling Teamcenter
Uninstalling Teamcenter
If you need to uninstall a Teamcenter installation, remove Teamcenter configurations
using Teamcenter Environment Manager. You can then remove your database server.
3. In the Maintenance panel, select Uninstall Teamcenter, and then click Next.
5. In the Uninstall panel, select Yes to confirm that you want to uninstall all
configurations and Teamcenter software. Click Next.
7. If you selected the option in TEM to remove the Teamcenter database, the
database is moved to the Oracle recycle bin. To permanently remove the
database, launch SQL*Plus and enter the following command:
PURGE RECYCLEBIN;
Uninstall TCCS
If you installed Teamcenter client communication system (TCCS) as part of an
installation of the rich client or Teamcenter Microsoft Office interfaces, uninstalling
those clients automatically uninstalls TCCS from your system.
If you installed TCCS using the stand-alone installation wizard, perform the
following steps to uninstall TCCS.
1. Stop the FMS client cache (FCC) process:
a. Change to the bin directory in the TCCS installation directory.
This launches the TCCS uninstallation wizard. Follow the instructions in the
wizard to uninstall TCCS.
4. Log off and log back on to the system to unset the FMS_HOME environment
variable.
Uninstalling DB2
If you no longer use your existing your DB2 instances and databases, you can
remove them.
If you want to uninstall your default DB2 copy but want to keep other DB2 copies
on your system, use the db2swtch command to choose a new default copy before
you proceed with the uninstallation. Also, if your database administration server
(DAS) is running under the copy you want to remove, move your DAS to a copy that
is not being removed. Otherwise, you must re-create the DAS using the db2admin
create command after the uninstall, and you may need to reconfigure the DAS
for some functionality to work.
Replace DB2-HOME with the DB2 installation directory you specified during
the DB2 installation. Replace instance-name with the login name of the DB2
instance.
Note On UNIX systems, the default installation path is
/opt/IBM/db2/Vversion. On Linux systems, the default
installation path is /opt/ibm/db2/Vversion.
The db2idrop command removes the instance entry from the list of instances and
removes the instance-home/sqllib directory. If you store any files in sqllib directory,
these files are removed by this action. If you still need these files, make a copy of
them before you remove the instance.
Optionally, as a user with root privileges, remove the instance owner’s user ID and
group (if used only for that instance). Do not remove these if you plan to re-create
the instance. Remove the database files from the system or drop the databases
before dropping the instance if you no longer need the databases. After you drop the
instance, the database files remain intact. This step is optional because the instance
owner and the instance owner group may be used for other purposes.
Replace DB2-HOME with the DB2 installation directory you specified during
the DB2 installation.
Note On UNIX systems, the default installation path is
/opt/IBM/db2/Vversion. On Linux systems, the default
installation path is /opt/ibm/db2/Vversion.
b. Log off.
d. If the DB2 instance startup script is not included in the .profile file, enter
one of the following commands to run the startup script.
• Bash, Bourne, or Korn shells: . instance-home/sqllib/db2profile
e. Stop the DB2 database manager by entering the db2stop force command.
f. Verify that the instance is stopped by entering the db2 terminate command.
2. Stop all DB2 processes and services. This can be done through the Windows
Control panel or by issuing the db2stop command from a command prompt.
If you do not stop DB2 services and processes before attempting to remove DB2
software, DB2 displays a warning that lists processes and services holding DB2
DLLs in memory.
For more information, see the IBM DB2 documentation for the db2unins
command.
ddb2unins /f
Caution This command removes all DB2 software and databases from your
system. Use this command only if other methods fail.
Uninstall Oracle
For information about uninstalling Oracle, see the Oracle installation guide on the
appropriate Oracle CD-ROM.
VII Appendixes
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
A Troubleshooting
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
A Troubleshooting
Troubleshooting
Troubleshoot problems you encounter during Teamcenter server installation.
• insautonomy.log
This file contains an installation record for Autonomy Intelligent Data Operating
Layer (IDOL) server, the default full-text search engine.
• configuration.xml
This file contains a record of the Teamcenter installation. Teamcenter
Environment Manager uses the configuration file to enable you to maintain the
installation, including adding and removing components, patching installations,
and upgrading installations.
Caution Do not remove the configuration.xml file. Removing the
configuration.xml file results in the inability to modify the
installation using Teamcenter Environment Manager.
• uninstall.xml
This file contains a record of the Teamcenter uninstallation.
Of these files, the system log (.syslog) files usually contain the most relevant error
data.
Problems/error messages
See the following information for help resolving errors encountered during
Teamcenter installation.
<<null>>\\<<null>> on host This error most likely indicates Start Teamcenter Environment
host-name does not have you attempted to start Teamcenter Manager as a user logged onto the
administrator privileges Environment Manager using system with Administrator group
the Windows runas command privileges and the Log on as a
or the Run as menu command. service right. For more information,
Teamcenter Environment Manager see Required operating system and
cannot be started as a user other user accounts.
than the user logged on to the
operating system.
Client credential too weak This problem can occur on SUSE Restart the remote procedure call
Linux 11 when executing the (RPC) portmapper service (rpcbind)
following ODS startup command: with the following options:
/ods -u=infodba kill -15 rpcbind-process
-p=infodba -g=dba rpcbind –i –w
Online help installed for rich client does not display Teamcenter Environment Manager did not
when accessing help over a network file system (direct update the portalHelpPage property in the
file access). site_specific.properties file.
Error Resolution
Cannot contact server Host or port may be incorrect. Check Host and
Port values and try again.
Cannot log on User name or password may be incorrect. Check
User and Password values and try again.
Incorrect Path Path to the directory on the update server may
be incorrect. Check the path and try again.
Timeout Error The update manager received no response from
the update server. Try connecting later or contact
your system administrator for assistance.
Transfer Error Contact with the update server was interrupted.
Try your operation again or contact your system
administrator for assistance.
During installation of the Teamcenter Web tier, the Web Application Manager
assigns the Web application the default name of tc.
If you specify a Web application name other than tc during corporate server
installation, you must change the corresponding value during Web tier installation.
If the Web tier and the corporate server do not reference the same Web application
name, the Web tier cannot connect to the Teamcenter server.
To ensure the Web tier and the corporate server reference the same Web application
name, perform one of the following procedures:
2. In the Modify Web Application dialog box, click Modify Web Application
Information.
3. Change the value in the Deployable File Name box to reflect the Web application
name you entered during corporate server installation.
Make the Java jar file available for the four-tier rich client
1. Locate the bmide/compressed_files directory in the Teamcenter software
distribution image.
2. Expand the bmide.zip file to a temporary directory. (This file contains the
jakarta-regexp-1.3.jar file.)
3. Add the temporary directory to the list of Disk Locations for Install Images in
the Web Application Manager.
4. Build your Web application EAR file using the Web Application Manager.
5. Deploy your EAR file as described in the Web Application Deployment Guide.
GMPDM_CM_cond_saveas_pwt_forms GMO_cond_saveas_pwt_forms
GMPDM_CM_copy_pwt_part_forms GMO_copy_pwt_part_forms
PWT_reset_actual_mass GMO_PWT_reset_actual_mass
GMPDM_CM_copy_cost_forms GMO_CM_copy_cost_forms
GMPDM_CM_delete_cost_form GMO_CM_delete_cost_form
GMIMAN_notifyIRCreation GMO_notify_on_ir_creation
GMPDM_delete_product_def_form GMO_delete_product_def_form_ptr
GMPDM_validate_product_def GMO_validate_product_definition_entries
Note Deleting the legacy action rules after successfully upgrading the GM Overlay
may change expected behavior in some areas of the GM Overlay. For
example, you cannot create item types like CORP_Part, CORP_Install,
CORP_Product, and CORP_Software.
Problem Solution
Web tier application fails during When a host has multiple IP addresses, the JGroups software
initialization with an error and JDK software arbitrarily choose one of them to use as
containing the following: the address to bind to for a server connection port. In some
situations, as when using a Windows Network Load Balancer,
Error during login. not all local IP addresses are accessible to other hosts on the
com.teamcenter.presentation. network. If the chosen IP address is not accessible, other
webclient.actions com. cluster peers are not able to open sockets to that port.
teamcenter.jeti.util.
JetiResourceConfiguration To avoid this error, specify a particular bind address using the
Exception: TreeCache bind.address Java system property, for example:
initialization failed
Dbind.address=123.456.78.91
Problem Solution
is the right one. This address can be changed by
configuring the SERVER_HOST parameter.
Inspect the Web tier log file for status messages reported
during server manager startup. If the server manager log
contains a message similar to this, set the SERVER_HOST
parameter in the serverPool.properties file to the correct
IP address for the host.
Warnings of discarded messages These warnings indicate that you have two clusters on the
same port (multicast) or set of ports (TCP).
Your environment is working because you used different
names for each cluster, but this is not an optimal environment
for performance. Siemens PLM Software recommends
configuring a different port or set of ports for each
environment.
Error messages about the server These messages indicate that the pool ID is in use by another
manager pool ID server manager in the TreeCache cluster. Either place the
server managers in different clusters or configure a distinct
pool ID.
Occasionally, TreeCache instances fail to accept connections
and report handleJoin errors. Typically this error disappears
if you restart one or more cluster members.
handleJoin errors occur at To get additional information, increase the logging level for
startup the tree cache and jgroups classes for both the application
server and server manager:
1. Copy the log4j.xml file in the server manager run-time
directory (TC_ROOT/pool_manager) to the application
server instance startup directory.
By default, the server manager run-time directory
includes a log4j.xml file, but it logs only the warning level
information. The default configuration sends log output
to the console and the following files:
TC_ROOT/pool_manager/logs/ServerManager/
process/serverManager.log
APPSERVER_ROOTlogs/WebTier/processWebTier.log
Problem Solution
The JMX HTTP adaptor allows you to view the status of the
server pool and dynamically change the pool configuration
values (the values are not persistent). Access this functionality
from the following URL:
http://host-name:jmx-port
Replace host-name with the name of the host running the
server manager. Replace jmx-port with the number of the
port running the JMX HTTP adaptor. This port number is
defined on the JMX HTTP Adaptor Port parameter when
you install the server manager.
Configuration is correct, but Determine from logs whether users are frequently losing a
run-time errors occur server due to the server timing out and are then having a new
server assigned.
Server startup can consume a great amount of CPU. Consider
increasing timeout values and/or the pool size.
Either the server manager Check the internet protocol configuration on the server
fails to start when employing manager host and the Web tier host and ensure that they
multicast TreeCache mode or match. Some application servers configure the Java virtual
the following error message is machine (JVM) to prefer the IPv4 stack. This is the case
received: with recent versions of JBoss. Therefore, you must alter the
Exception in thread "main" preferIPv4Stack Java property on the server manage host
java.net.SocketException: to match the Web tier configuration.
Can’t assign requested address.
By default, Java prefers to use Internet Protocol Version 6
(IPv6) addresses. Incomplete IPv6 configuration can cause
Java socket exceptions that prevent the server manager from
starting.
For example, an IBM AIX server might be configured to have
an IPv6 loopback address ::1 but no IPv6 ethernet address.
Detect this problem on AIX with the command:
netstat –ni
If this is the case, either complete the IPv6 upgrade
configuration as documented in the IBM System Management
Guide or uncomment the following line in the mgrstart script:
#JVM_ARGS="${JVM_ARGS} -Djava.net.preferIPv4Stack=true"
Problem Solution
address can be added to the TreeCacheTCP.xml file (for
TCP mode) or the TreeCacheMcast.xml file (for Mcast
mode). In the server manager, this file can be found in the
TC_ROOT/pool_manager directory. In the J2EE application
it can be found in the file JETIServerAccessor.jar in
the staging area of the Web Application Manager. For
Mcast mode, locate the UDP configuration line and add
bind_addr=desired-address. For TCP mode, locate the TCP
configuration line and add bind_addr=desired-address.
Out-of-memory messages from Review and adjust as necessary the settings for the following
Web application server running kernel parameters:
on HP-UX platform
max_thread_proc
maxfiles
maxusers
Particularly, the default max_thread_proc value of 64 is
not sufficient for running the Web application server. The
optimum values depend on the traffic level and machine
capabilities.
TreeCache connection failure Terminating a server manager instance by sending it a signal
after restarting or redeploying does not clean up the TreeCache data stored in other four-tier
components regarding the terminated pool. When this server
manager is restarted, it cleans up this information. However,
termination of a server manager in this way sometimes leaves
the TreeCache communication mechanisms in a corrupted
state and the server manager is not able to rejoin the
TreeCache cluster. The problem can be resolved by stopping
all four-tier components (the application servers and server
managers) in the TreeCache cluster and then restarting them
all. This problem can usually be avoided by shutting the
server manager down cleanly through the server manager
Administrative Interface. For information about using the
server manager administrative interface, see the System
Administration Guide.
A similar problem can occur after the Teamcenter Web tier
application is redeployed on the application server without
stopping and restarting the application server. In this case, an
extra TreeCache instance from the earlier deployment might
still be running in the application server and this can interfere
with proper functioning of the TreeCache. This can usually be
resolved by stopping and restarting the application server.
Due to a Java run-time issue on Linux, these problems are
more likely if the four-tier component is run with the nohup
command on Linux and the process is terminated by sending
it a signal.
Problem Solution
JBoss 5.1.0 GA displays an The following error message displays during JBoss startup:
error message during startup AttachmentStore MC bean (org.jboss.system.server.profileservice.
when installed on Sun Solaris repository.abstractAttachmentStore)configuration does not specify
the parameter type for constructor
operating system.
This is a known JBoss bug (JBAS-6981). You must edit the
profile.xml file for your application server instance.
Using the default server as an example, edit the
{jboss-5.1.0.GS}/server/default/conf/boodstrap/profile.xml
file as follows:
1. Locate the following parameter element in the file:
<!-- The attachment store -->
<bean name="AttachmentStore"
class="org.jboss.system.server.profileservice.
repository.AbstractAttachmentStore">
<constructor>
<parameter>
<inject bean="BootstrapProfileFactory"
property="attachmentStoreRoot" />
</parameter>
</constructor>
<property name="mainDeployer">
<inject bean="MainDeployer" />
</property>
<property name="serializer">
<inject bean="AttachmentsSerializer" />
</property>
<property name="persistenceFactory">
<inject bean="PersistenceFactory" />
</property>
.
.
.
Problem Solution
Teamcenter Web application The Teamcenter Web application takes longer than the
fails to deploy on JBoss with the default 60 seconds the JBoss deployment scanner allows for
following error messsage: deployments. Add the deployment-timeout attribute to the
deployment-scanner element and set the value to at least
Did not receive a response
to the deployment operation 600 seconds before attempting to deploy the Web application.
within the allowed timeout
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
period [60 seconds]. Check
<deployment-scanner path="deployments"
the server configuration
relative-to="jboss.server.base.dir" s
file and the server logs to
scan-interval="5000"
find more about the status
deployment-timeout="600"/>
of the deployment.
</subsystem>
Troubleshooting Oracle
When Oracle detects an error, an error code is displayed in the system console
window and written to the Teamcenter trace and log files. To assist troubleshooting,
Oracle embeds object names, numbers, and character strings in error messages.
The oerr utility provides additional troubleshooting information. Often, the
additional information offers a solution to the problem.
Replace oracle-version with the installed Oracle version, for example, 920.
Replace facility error-number with the Oracle error code, for example ORA 7300.
ORA is the facility and 7300 is the error number.
This command displays cause and action messages that you can use to
troubleshoot the problem.
o To accommodate high levels of input and output, modify the vvcp.ini file on
Windows systems, or the vvcp.platform.cfg file on UNIX systems.
FileCheckWait=600
FileCheckWaitForZero=30
o On UNIX platforms, after you install Ghostscript, set the PSPath setting
in the Convert and Print configuration file (vvcp.ini) to the location of the
Ghostscript application.
For example: *PSPath: /apps/gs853/bin/gs.
o Path
Specify the location of the watched folder directory.
Adobe LiveCycle creates this directory if it does not already exist; use a
short path.
Note The input directory is created under the specified Path directory
location. This is the watched folder input directory.
For example, if the path is:
D:\LCWatchedFolder
o Wait Time
o Operation Name
Select CreatePDF.
After LiveCycle PDF Generator ES is installed, you must create and configure
the Adobe LiveCycle Watched Folder Endpoint as described in Adobe LiveCycle
Endpoint Management documentation. The specified watched folder input and
result directory locations are needed during the installation of PdfGenerator
translator.
For more information, see the Dispatcher Server Translators Reference Guide.
After the watched folder endpoints are set, you may also need to modify the
default applications extension file type settings to specify additional filename
extensions for file types for generating PDF output.
For more information about these configuration tasks, see the Adobe LiveCyle
ES documentation.
• You must enable the RenderMgtTranslator service and one or both of the
following services:
o PreviewService
o PdfGenerator
o PreviewService
Required Teamcenter Visualization Convert 8. Ghostscript v 8.53, and
source authoring applications such as Microsoft Office application (2003,
2007) are also required.
o PdfGenerator
Requires Adobe LiveCycle PDF Generator ES. The configuration file must
specify the Adobe watched folder input and watched folder result directory
location. Source authoring applications such as Microsoft Office application
(2003, 2007) and Adobe Acrobat 8.x are also required.
o RenderMgtTranslator
Required for either PreviewService, PdfGenerator, or any other service
to be added.
• Use Business Modeler IDE to set up and deploy IRDC and dispatcher service
configuration objects to the Teamcenter database.
This message results from the rich client expecting a Web application named tc but
being unable to find it.
To resolve this problem, set the WEB_default_site_deployed_app_name preference
to the correct name of the deployed Web application. You can update this preference
using the preferences manager from the command line or from within the rich client.
For information about using the preferences manager, see the Preferences and
Environment Variables Reference.
2. Create a new empty database using the appropriate DBCA template file.
B Distribution media
B Distribution media
Distribution media
Siemens PLM Software distributes the following software and documentation
images for Teamcenter 10.1:
Image Description
Image Description
Directory Description
additional_applications Contains directories containing applications such
as Teamcenter client communication system
(TCCS), Security Services, and the Siemens PLM
Software Common Licensing Server.
additional_documentation Contains instructions for installing Oracle RDBMS.
advanced_installations Contains the resource_management
subdirectory that contains Resource Manager
application files for Teamcenter manufacturing
process management.
An additional subdirectory, cc_integration,
contains Teamcenter manufacturing process
management components required when installing
the Multi-Structure Manager integration with
Tecnomatix eMPower.
bmide Contains the Business Modeler IDE.
cci Contains the CCI client.
install Contains files required for installing Teamcenter.
localization Contains localization and internationalization files
for the rich client and the thin client.
logmanager Contains the log manager application.
mappingdesigner Contains the mapping manager application.
portal Contains Teamcenter rich client files.
tc Contains the Teamcenter software files.
Web_tier Contains the Web Application Manager program
and supporting files for generating the Web tier
application and the rich client distribution server
and instance WAR files.
The base directory of the Teamcenter software distribution image also contains
Teamcenter Environment Manager program (tem.sh) that installs Teamcenter
executables and data directories.
File Description
tchelp.jar Contains the Teamcenter online help library in
HTML format. You can install this library using
Teamcenter installation tools.
You can also install this library manually by
expanding the tchelp.jar file to your local host and
then opening the index.html file in a Web browser.
This archive requires approximately 561 MB of
disk space when expanded.
tcrefs.jar Contains the following Teamcenter developer
references:
• C++ API Reference
• Integration Toolkit (ITK) Function Reference
• Services Reference
Directory Description
PDF Contains the Teamcenter online help library in
PDF format. To open the online help library
index page, open the index.htm file.
A PDF reader or PDF Web browser plug-in is
required to view PDF files. If you use Adobe
Reader, you can search the complete online help
library by clicking the search icon on the online
help library index page.
Note The PDF directory contains the same
contents as the PDF.zip file.
additional_documentation Contains additional documentation for use with
Teamcenter. This includes guides for using the
Siemens PLM Software common licensing server.
You can install the Teamcenter online help library in HTML or PDF format to your
local host or Teamcenter network. The HTML online help library can be accessed
from the Teamcenter rich client and thin client.
For information about installing online help, see Install online help.
Teamcenter solutions
Solutions are preselected groups of features that provide starting points for
recommended Teamcenter configurations. You can add features or deselect features
in the Features panel in Teamcenter Environment Manager (TEM). For information
about a solution, point to the solution name in the list. TEM displays a description.
Solution Features
Corporate Server Teamcenter Foundation
FMS Server Cache
NX UG Integration
Dispatcher (Dispatcher Server) Dispatcher Server
Volume Server FMS Server Cache
Rich Client 2-tier Teamcenter Rich Client 2-tier
Rich Client 4-tier Teamcenter Rich Client 4-tier
Multisite Collaboration Proxy Server Multisite Collaboration IDSM Service
Multisite Collaboration ODS Service
Business Modeler IDE Business Modeler IDE Standalone
Global Services Teamcenter Foundation
J2EE Based Server Manager
FMS Server Cache
Global Services Framework
Global Services Preferences
Teamcenter features
TEM provides the following features and feature groups in the Features panel.
Features are grouped by related applications. For information about a feature, point
to the feature name in the list. TEM displays a description of the feature.
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.
Teamcenter features
Feature/Subfeature Description
Base Install Base Teamcenter server and client components.
Teamcenter Foundation Installs the complete Teamcenter application root directory (TC_ROOT),
including the Teamcenter server process (tcserver), and either creates
a data directory for storing database-specific files or configures this
installation to connect to an existing data directory.
If you create a data directory, you also provide information about the
database to use with this installation. If you specify a new database,
Teamcenter Environment Manager populates the database and creates a
volume.
J2EE Based Server Manager Installs the process that manages the pool of Teamcenter server processes.
This option is applicable only when you are deploying the Web tier. This
feature requires Teamcenter Foundation and FMS Server Cache features.
For a smaller site, you can install the server manager and Teamcenter
servers on the same host as the Web tier application. For deployment
options for larger sites, you can install the server manager on a separate
host.
.NET Based Server Manager Installs the process that manages the pool of Teamcenter server processes.
This option is applicable only when you are deploying the Web tier. This
feature requires Teamcenter Foundation and FMS Server Cache features.
Teamcenter features
Feature/Subfeature Description
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.
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.
Online Help Installs the Teamcenter Help Library files on the local host:
When TEM prompts you for the location of the Teamcenter help files, enter
the path to the Teamcenter documentation distribution image, which
contains the online help files (tchelp.jar).
Sample files Installs sample source code for customizing Teamcenter and generating
reports.
This component is optional. You can install the sample files individually;
you need not install any other components.
Teamcenter Security Services Configures Security Services for Teamcenter. These services eliminate
prompts for logon credentials when users switch Teamcenter products
within a user session.
Prerequisite:
Required information:
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.
Teamcenter features
Feature/Subfeature Description
Task Manager Service Checks user inboxes for tasks that have passed due dates, notifies the
delegated recipients, and marks those tasks as late.
For information about 4GD, see the 4th Generation Design Guide.
Teamcenter features
Feature/Subfeature Description
Advanced PLM Services 4th Generation Design features.
4th Generation Design Installs 4th Generation Design (4GD) functionality for the Teamcenter
server. 4GD allows users of NX CAD or Lifecycle Visualization to cooperate
in real time during the design cycle of a product.
For information about 4GD, see the 4th Generation Design Guide.
4th Generation Design Change Management Installs 4th Generation Design functionality for Change Manager. This
Integration feature requires Teamcenter Foundation and Change Management.
For information about this feature, see the 4th Generation Design Guide.
4th Generation Design Issue Management Installs 4th Generation Design functionality for Issue Manager. This
feature requires Teamcenter Foundation and Issue Management.
For information about this feature, see the 4th Generation Design Guide.
Aerospace and Defense Aerospace and Defense features.
Aerospace and Defense Foundation Installs Aerospace and Defense functionality for the Teamcenter server.
This feature requires Teamcenter Foundation and Vendor Management.
For more information about this feature, see the Aerospace and Defense
Solution Guide.
Aerospace and Defense Change Installs the change management functionality for the Aerospace
Management and Defense Foundation feature. This feature requires Teamcenter
Foundation and Aerospace and Defense Foundation.
For more information about this feature, see the Aerospace and Defense
Solution Guide.
Aerospace and Defense Foundation Installs the Aerospace and Defense Foundation training program for
Training the Aerospace and Defense Foundation feature. This feature requires
Teamcenter Foundation, Vendor Management, and Aerospace and
Defense Foundation.
For more information about this feature, see the Aerospace and Defense
Solution Guide.
Automotive Teamcenter Automotive Edition and additional supporting features.
Teamcenter Automotive Edition Installs the optional Teamcenter Automotive Edition application.
GM Overlay Installs the Teamcenter Automotive Edition GM Overlay application.
Teamcenter features
Feature/Subfeature Description
BOM Management Features that support Product Master Management.
Product Master Manager Installs Product Master Manager, a rich client application that allows
users to view and manage a complete set of LOUs, LOAs, and parts for a
vehicle program. Users work with items in a work in progress (WIP) area
and optionally add them to a package to allow effective collaboration with
other users.
CAD-BOM Alignment Configures the Teamcenter installation to interact and share visual data
with Product Master Management. Configuring this feature allows designs
managed by this installation of Teamcenter to be related to parts and use
or parts in products that are managed by Product Master Management.
For more information about these features, see the Behavior Modeling
Tool Integration Guide.
Installs the behavior modeling framework that provides integration to
the behavior modeling tool.
Behavior Modeling Common Client
For more information about these features, see the Behavior Modeling
Tool Integration Guide
Installs the behavior modeling framework that provides integration to the
Teamcenter Behavior Modeling Teamcenter behavior modeling tool.
Framework
This feature requires Teamcenter Foundation or a rich client or a two-tier
Business Modeler IDE client.
MATLAB Integration Features that provide the Teamcenter integration to MATLAB, which
allows you to manage your MATLAB model data in Teamcenter.
For more information about these features, see the Behavior Modeling
Tool Integration Guide.
Installs the MATLAB integration connector that allows you to manage
MATLAB Integration Connector MATLAB models in Teamcenter.
Teamcenter MATLAB Integration This feature requires the Teamcenter Behavior Modeling Framework
feature and also Teamcenter Foundation or a rich client or a two-tier
Business Modeler IDE client.
Consumer Packaged Goods Features to support Consumer Packaged Goods.
Brand Management Installs the Brand Management template for Consumer Packaged Goods.
For information about installing this feature, see Getting Started with
Consumer Packaged Goods.
Teamcenter features
Feature/Subfeature Description
CPG Materials Installs Consumer Packaged Goods objects such as raw materials,
formulated materials, and so on.
For information about installing this feature, see Getting Started with
Consumer Packaged Goods.
Finished Product Management Installs the Finished Product Management functionality for Consumer
Packaged Goods.
For information about installing this feature, see Getting Started with
Consumer Packaged Goods.
Packaging and Artwork Installs packaging and artwork functionality for Consumer Packaged
Goods.
For information about installing this feature, see Getting Started with
Consumer Packaged Goods.
Specification Manager Installs the Specification Manager feature. For more information about
installing this feature, see the Specification Manager Guide.
Finished Product Management to CPG Provides a bridge between finished products and Consumer Packaged
Materials Bridge Goods materials.
For information about installing this feature, see Getting Started with
Consumer Packaged Goods.
Packaging and Artwork to Finished Product Provides a bridge between Packaging and Artwork and Finished Product
Management Bridge Management for Consumer Packaged Goods.
For information about installing this feature, see Getting Started with
Consumer Packaged Goods.
Content and Document Management Content and document management features.
Acrobat/Reader Plugin Installs the Teamcenter plug-in for Adobe Acrobat and Adobe Acrobat
Reader. This solution is optional.
For information about using the Adobe Acrobat/Reader plug-in, see Getting
Started with Document Management.
Content Management Base Installs the data model for Content Management.
Teamcenter features
Feature/Subfeature Description
NX Integration Installs default data types and loads template NX data to support
Teamcenter Integration for NX/NX Integration, the Teamcenter integration
with Siemens PLM Software NX.
NX Manager for Rich Client Installs Teamcenter Integration for NX for the rich client. This feature
requires Teamcenter Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Spatial Search Installs Spatial Search capabilities of the cacheless search engine.
For more information about configuring and using Spatial Search, see
the Getting Started with RDV guide.
Bounding box generation from JT Enables generation of bounding box data from JT files, providing
secondary data for the cacheless search engine. For more information
about configuring and using cacheless search, see the Getting Started with
RDV guide.
Trueshape generation from JT Enables generation of Trushape data from JT files, providing secondary
data for the cacheless search engine.
For more information about configuring and using cacheless search, see
the Getting Started with RDV guide.
Bounding box generation from NX Enables generation of bounding box data when saving NX files, providing
secondary data for the cacheless search engine.
Teamcenter features
Feature/Subfeature Description
QPL for Repeatable Digital Validation Installs and configures QPL files used in conjunction with the rich client
DesignContext application.
Required information:
DesignContext is available for both the rich client and thin client.
This option is applicable only when you are deploying the four-tier
architecture.
Prerequisites:
Required information:
• Host name and port number of the Java servlet running the
Teamcenter Application Registry.
• The host name and port number of the host running a Web tier
application.
For information about installing this feature, see Getting Started with
Dispatcher (Translation Management).
Teamcenter features
Feature/Subfeature Description
Render Document for Rich Client Provides Render Management capabilities for the rich client. This feature
requires Dispatcher Client for Rich Client.
For more information about using Change Management, see the Change
Manager Guide.
Note If you install this feature, you may need to set the
HiddenPerspectives preference in the rich client.
Contract Data Management Installs Contract Data Management, which allows you to manage, initiate
review processes, and monitor correspondence for procurement documents,
such as design information, drawings, status reports, purchase orders,
and so on.
For more information about Contract Data Management, see the Aerospace
and Defense Solution Guide.
Dispatcher Server Installs the following Dispatcher Server components: scheduler, module
and administration client.
For information about installing this feature, see Getting Started with
Dispatcher (Translation Management).
Finish Management Installs Finish Management for Teamcenter. A finish represents a
finishing process on a part. It may be used to improve appearance,
adhesion, corrosion resistance, tarnish resistance, chemical resistance,
wear resistance, and remove burrs and so on.
For more information about finishes, see the Aerospace and Defense
Solution Guide.
Materials Management Installs the Materials Management solution, which stores approved
material and substance information imported from a third-party database
(for example, Granta, IMDS) into a material library in the Teamcenter
database.
Many parts are made from stock materials such as bar stock, tubing stock
and sheet stock. This features enables you to manage stock materials in
Teamcenter, performing actions like creating libraries of stock materials
and assigning stock materials to parts.
For more information about stock materials, see the Aerospace and Defense
Solution Guide.
Teamcenter features
Feature/Subfeature Description
Work Package Management Enables management of work packages Teamcenter.
For more information about packages, see the Aerospace and Defense
Solution Guide.
Change and Schedule Management Installs the Change and Schedule Management interface, which enables
Interface you to selectively propagate the problem, impact, solution, and reference
items related to a change object to the related plan items (schedules)
leaf-level schedule tasks.
For information about installing this feature, see Getting Started with
Dispatcher (Translation Management).
Issue Management Installs Issue Manager, which allows you to track problems, or issues, with
products by managing the review, approval, and implementation of issues.
Maintenance Repair and Overhaul Teamcenter maintenance, repair, and overhaul features.
Teamcenter features
Feature/Subfeature Description
As-Built Management Installs the As-Built template for Teamcenter maintenance, repair, and
overhaul.
For information about installing, configuring, and using this feature, see
the As-Built Manager Guide.
If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the As-Built Manager solution in your rich client
distribution instance.1
As-Maintained Management Installs the As-Maintained feature to support the As-Maintained physical
structure management
For information about installing, configuring, and using this feature, see
the Service Manager Guide.
If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the As-Maintained Management for Service
Manager solution in your rich client distribution instance.1
Service Planning Installs the Service Planner application that supports service planning
capabilities within Teamcenter. Service Planner requires a separate
license and is installed as an optional overlay to standard Teamcenter.
If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the Service Planning solution in your rich client
distribution instance.1
For information about using Service Planner, see the Service Planner
Guide.
As-Built and As-Maintained Alignment Enables interoperability of data created by the As-Built Management and
As-Maintained Management features.
If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the As-Built and As-Maintained Alignment for
Service Manager solution in your rich client distribution instance. 1
For information about installing, configuring, and using this feature, see
the As-Built Manager Guide. For information about the As-Maintained
feature, see the Service Manager Guide.
Service Event Management Installs Service Event Management to support service process
management for Teamcenter maintenance, repair, and overhaul.
If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the Service Event Management Extensions for
Service Manager solution in your rich client distribution instance.1
For more information about using Service Manager, see the Service
Manager Guide.
Service Planning and Service Processing If you select this feature and you use the Over-the-Web Installer to install
Alignment the rich client, include the Service Processing Extensions for Service
Manager solution in your rich client distribution instance.1
1. For more information about installing rich client distribution instances, see Install a rich client distribution instance
Teamcenter features
Feature/Subfeature Description
Service Request Processing Installs the Service Planning and Service Processing Alignment module to
support using discrepancies in Service Planner.
If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the Service Request Manager solution in your
rich client distribution instance.1
For more information about using Service Planner, see the Service
Manager Guide.
Service Scheduler Installs Service Scheduler, which supports scheduling within Teamcenter.
Service Scheduler lets companies define, schedule, and implement services
for their products. Service Scheduler is a separately licensed application
that is installed as an optional overlay on top of standard Teamcenter
and Service Manager.
If you select this feature and you use the Over-the-Web Installer to install
the rich client, include the Service Scheduling solution in your rich client
distribution instance.1
For more information about using Service Scheduler, see the Service
Scheduler Guide.
Manufacturing Process Management Teamcenter manufacturing process management features.
Configure Resource Browser and NC Installs libraries for the Resource Browser and NC Package Browser
Package Browser applications.
MTM Data Card Installs the Methods Time Measurement (MTM) data card system.
Teamcenter features
Feature/Subfeature Description
Install Libraries for AI SOA Client Installs sample source code and executables that assist in developing an
Application Interface (AI) service client.
For more information about the AI Service, see the Services Reference in
the Teamcenter HTML Help Collection.
For more information about the CCDM solution, see the Embedded
Software Solutions Guide.
ECAD Part Library Management Installs ECAD part types to support ECAD part library management.
This feature requires Teamcenter Foundation, Vendor Management, and
EDA Server Support.
ESM Processor Installs ESS processor types and updates preferences. Without these, ESS
operations do not work from any interface (rich client, thin client, custom
utilities, and other clients).
ESM Software Installs ESS software types and updates preferences. Without these, ESS
operations do not work from any interface (rich client, thin client, custom
utilities, and other clients).
Embedded Software Design Data Installs Embedded Software Design Data Management. For more
Management information about this feature, see the Embedded Software Solutions
Guide.
Platform Extensability Platform extensability features.
Global Services Global Services features.
Global Services Framework Creates Global Services Framework.
Global Services Preferences Installs Global Services Preferences.
Teamcenter features
Feature/Subfeature Description
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).
Global Services Monitoring GUI for Installs a rich client and configures it for use with the Global Services
Rich Client Monitoring GUI for Rich Client feature. This feature requires Teamcenter
Rich Client 2-tier or Teamcenter Rich Client 4-tier.
Mapping Designer Installs the Mapping Designer client. Mapping Designer is dependent on
third-party external eclipse plug-ins from Altova MapForce. The Altova
Mapforce eclipse plug-ins are dependent on the MapForce client. Requires
MapForce Professional client and MapForce eclipse plug-ins. Download
these plug-ins from Altova at the following URL:
http://www.altova.com/download_archive.html
A valid license for the MapForce client is required to run Mapping Designer.
Teamcenter features
Feature/Subfeature Description
Installs the optional Substance Compliance solution, which assists in
compliance with environmental laws, regulations, standards, and other
requirements for parts and for the parts manufactured or supplied from an
external source.
Substance Compliance
This solution requires the Teamcenter materials management solution.
This feature requires the Teamcenter Foundation feature and also a rich
client or a two-tier Business Modeler IDE client.
Solution Description
Over-the-Web Installer Installs the program that installs the rich client over
the Web. This solution is required.
Microsoft Visual Installs the Microsoft Visual C++ libraries required
C++ 2005/2008/2010 for the rich client and for the FMS client cache (FCC).
Redistributables
Solution Description
Teamcenter client Installs Teamcenter client communication system
communication system (TCCS).
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
Solution Description
4th Generation Design for Installs 4th Generation Design (4GD) support for the
Rich Client 4-Tier rich client.
4GD allows users of NX CAD or Lifecycle
Visualization to cooperate in real time during the
design cycle of a product.
For information about 4GD, see the 4th Generation
Design Guide.
As-Built Manager Adds As-Built functionality for the four-tier rich
client. As-Built is part of Teamcenter maintenance,
repair, and overhaul.
For information about installing, configuring, and
using this solution, see the As-Built Manager Guide.
This solution requires the As-Built Management
feature on the Teamcenter corporate server.
As-Maintained Installs Service Event Management to support
Management for Service service process management for As-Maintained
Manager functionality of Teamcenter maintenance, repair,
and overhaul.
For information about installing, configuring, and
using this feature, see the Service Manager Guide.
This solution requires the As-Maintained
Management feature on the Teamcenter corporate
server.
CAD-BOM Alignment Installs CAD-BOM alignment, which allows
(CBAExt) for Rich Client Teamcenter to interact and share visual data with
4-Tier Product Master Management.
CPG Materials for Rich Installs CPG Materials support for Consumer
Client 4-Tier Packaged Goods.
For information about installing this solution, see
Getting Started with Consumer Packaged Goods.
Calibration and Installs Calibration and Configuration Data
Configuration Data Management (CCDM), which allows rich client users
Management (CCDM) to manage the calibration and configuration-related
for Rich Client 4-Tier parameter data of embedded systems. CCDM allows
you to define, create, view, update, and delete
parameter data, and to group related parameter
definitions together and associate parameter values
to a project.
For more information about the CCDM solution, see
the Embedded Software Solutions Guide.
Solution Description
Change Management Installs the Change Management and Schedule
and Schedule Manager Management interface, which enables you to
Interface selectively propagate the problem, impact, solution,
and reference items related to a change object to the
related plan items (schedules) leaf-level schedule
tasks.
For more information, see the Change Manager
Guide.
Content Management Base Installs Content Management and enables
+S1000D for Rich Client management of documentation for the S1000D
4-Tier standard.
Content Management is the application used to
manage technical documentation using SGML and
XML information stored in a Teamcenter database.
For information about configuring this feature
and using Content Management, see the Content
Management Guide.
Contract Management for Installs Contract Data Management, which allows
Rich Client 4-Tier you to manage, initiate review processes, and
monitor correspondence for procurement documents,
such as design information, drawings, status reports,
purchase orders, and so on. This solution is optional.
For more information about Contract Data
Management, see the Aerospace and Defense Solution
Guide.
Dashboard Installs the Reporting and Analytics Dashboard
interface.
For more information about installing this feature,
see Installing Teamcenter reporting and analytics.
Dispatcher Client for Rich Installs Dispatcher Client for the rich client.
Client
For information about using this feature, see Getting
Started with Dispatcher (Translation Management).
ESDDM for Rich Client Installs Embedded Software Solutions Design Data
4-Tier Management support for the rich client.
For more information about this feature, see the
Embedded Software Solutions Guide.
Embedded Software Installs Embedded Software Solutions support for
Manager for Rich Client the rich client.
4-Tier
For more information about this feature, see the
Embedded Software Solutions Guide.
Solution Description
Finish Management for Installs Finish Management for Teamcenter. A finish
Rich Client 4-Tier represents a finishing process on a part. It may be
used to improve appearance, adhesion, corrosion
resistance, tarnish resistance, chemical resistance,
wear resistance, and remove burrs and so on.
For more information about finishes, see the
Aerospace and Defense Solution Guide.
GDIS for Rich Client 4-Tier Installs the Global Dimensional Information System
plug-in for Dimensional Planning and Validation
(DPV). This solution is optional.
For more information about this feature, see the
Installing the Dimensional Planning and Validation
solution in the Dimensional Planning and Validation
online help collection.
GM Overlay for Rich Client Installs the Teamcenter Automotive Edition–GM
4-Tier Overlay application. This solution is optional.
GS Monitoring GUI for Rich Configures the rich client for use with the Global
Client 4-Tier Services Monitoring GUI for Rich Client feature.
MES Integration solution Installs rich client support for the Manufacturing
for Rich Client 4-tier Execution System Integration (MES Integration),
which collects the bill of process, bill of materials, and
any relevant work instructions into a work package
that is released to the MES system.
For information about using MES Integration, see
the Manufacturing Execution System Integration
Guide.
MTM Data Card for Rich Installs the Methods Time Measurement (MTM)
Client data card system. This solution is optional.
For more information, see Getting Started with
Manufacturing.
Materials Management for Installs rich client support for Materials
Rich Client 4-Tier Management, which stores approved material and
substance information imported from a third-party
database (for example, Granta, IMDS) into a material
library in the Teamcenter database.
For more information, see the Materials Management
Solution Guide.
NX Manager for Rich Client Configures the rich client to use Teamcenter
4-Tier Integration for NX or NX Integration, the application
that integrates Teamcenter with NX. Separate
installation of the Teamcenter Integration for NX or
NX Integration executables is required (as part of
NX installation). This solution is optional.
Solution Description
Product Master Installs Product Master Manager, a rich client
Management (PMM) for application that allows users to view and manage
Rich Client 4-Tier a complete set of LOUs, LOAs, and parts for a
vehicle program. Users work with items in a work in
progress (WIP) area and optionally add them to a
package to allow effective collaboration with other
users.
Note This feature requires postinstall setup to
complete configuration.
For more information about installing
Product Master Management, see Installing
and Upgrading Product Master Management
in the Product Master Management online
help collection.
Requirements Installs Requirements Management functionality
Management for Systems Engineering and Requirements
Management.
For information about using Requirements
Management, see Getting Started with Systems
Engineering.
SCM ClearCase for Rich Installs the integration between Teamcenter and the
Client 4-Tier IBM ClearCase software configuration management
(SCM) tool and configures the rich client for its
use. Separate installation of ClearCase software is
required. This solution is optional.
SRM Integration for Rich Installs the Supplier Relationship Management
Client 4-Tier integration.
For more information about this solution, see the
Data Exchange Guide.
Service Planning Installs the Service Planner application that
supports service planning capabilities within
Teamcenter. Service Planner requires a separate
license and is installed as an optional overlay to
standard Teamcenter.
This solution requires the Service Planning feature
on the Teamcenter corporate server.
For information about using Service Planner, see the
Service Planner Guide.
Specification Manager for Installs Specification Manager functionality for the
Rich Client 4-Tier rich client.
For more information about this feature, see the
Specification Manager Guide.
Solution Description
Substance Compliance for Installs rich client support for the Teamcenter
Rich Client 4-Tier substance compliance solution. Substance
Compliance assists in compliance with environmental
laws, regulations, standards, and other requirements
for parts and for the parts manufactured by or
supplied from an external source.
This solution requires the Teamcenter materials
management solution.
For more information about Substance Compliance,
see the Substance Compliance Solution Guide.
Systems Engineering Installs the Systems Engineering application, which
provides capabilities such as functional modeling
and budgets.
This feature requires the rich client.
For information using Systems Engineering, see
Getting Started with Systems Engineering.
Teamcenter Applications Installs Teamcenter Extensions for Microsoft Office
for Microsoft Office and the Teamcenter Plugin for Microsoft Project,
which allows Microsoft Project users to exchange
data directly with Schedule Manager. Separate
installation of Microsoft Office is required.
For information about installing these features on
a rich client host, see the Installation on Windows
Clients Guide.
Teamcenter Visualization Configures the rich client to use the embedded viewer
(Embedded) for Rich Client when Teamcenter lifecycle visualization is separately
4-Tier installed on the client workstation. This solution is
optional.
Teamcenter Visualization Configures the Teamcenter lifecycle visualization
(Stand-alone) for Rich application (the stand-alone application viewer).
Client 4-Tier Separate installation of Teamcenter lifecycle
visualization is required. This solution is optional.
Vendor Management for Installs Vendor Management support for the rich
Rich Client 4-Tier client.
Work Instructions Solution Installs the Work Instructions view for the rich
for Rich Client 4-Tier client.
For information about using work instructions, see
the Manufacturing Process Planner Guide.
ADS Foundation for Rich Installs Aerospace and Defense functionality for the
Client 4-Tier rich client.
For more information about Aerospace and Defense,
see the Aerospace and Defense Solution Guide.
Solution Description
Content Management DITA Enables management of documentation for the DITA
for Rich Client 4-Tier standard in Content Management.
For information about configuring this feature
and using Content Management, see the Content
Management Guide.
Render Document for Rich Provides Render Management capabilities for the
Client rich client. This feature requires Dispatcher Client
for Rich Client.
For more information about installing and
configuring Render Management capabilities, see
Installing Render Management.
For information about installing Dispatcher features,
see Getting Started with Dispatcher (Translation
Management).
Rich Client 4-Tier Lite Installs the lite edition of the four-tier rich client.
Edition This solution is optional.
Service Processing Installs the Service Processing Extensions for the
Extensions for Service rich client. This functionality is available only if you
Manager have purchased and have a license for Service Event
Management.
This solution requires the Service Planning and
Service Processing Alignment feature on the
Teamcenter corporate server.
For more information about using Service Manager,
see the Service Manager Guide.
As-Built and As-Maintained Installs the operability functionality between
Alignment for Service the As-Built Management and As-Maintained
Manager Management applications. This functionality is
available only if you have purchased and have a
license for As-Built Management and As-Maintained
Management.
This solution requires the As-Built and
As-Maintained Alignment feature on the Teamcenter
corporate server.
For more information installing and using As-Built,
see the As-Built Manager Guide.
For more information about using Service Manager,
see the Service Manager Guide.
Solution Description
Service Event Management Installs the Service Event Management functionality
Extensions for Service for the rich client. This functionality is available only
Manager if you have purchased and have a license for Service
Event Management.
This solution requires the Service Event
Management feature on the Teamcenter corporate
server.
For more information about using Service Manager,
see the Service Manager Guide.
Service Request Manager Installs service request processing for Teamcenter
maintenance, repair, and overhaul.
This solution requires the Service Request
Processing feature on the Teamcenter corporate
server.
For more information about using Service Request
Manager, see the Service Request Manager Guide.
Service Scheduling Installs Service Scheduler, which supports scheduling
within Teamcenter. Service Scheduler lets companies
define, schedule, and implement services for their
products. Service Scheduler is a separately licensed
application that is installed as an optional overlay on
top of standard Teamcenter and Service Manager.
This solution requires the Service Scheduler feature
on the Teamcenter corporate server.
For more information about using Service Scheduler,
see the Service Scheduler Guide.
Teamcenter MATLAB Installs the Teamcenter MATLAB integration data
Integration model, which allows you to manage your MATLAB
model data in Teamcenter.
This feature requires the Behavior Modeling
Common Client solution.
For more information about these features, see the
Behavior Modeling Tool Integration Guide.
The following tables describe Web tier context parameters provided by Teamcenter
Web tier solutions.
1. For more information about configuring JBoss Cache TreeCache and setting TreeCache parameters, see www.jboss.org/jbosscache.
The TreeCache implementation also uses the JGroups toolkit. For more information about JGroups, see www.jboss.org/jgroups.
E Glossary
E Glossary
architecture
Set of decisions, patterns, and principles for a product suite. The architecture
provides a framework for application development within that product suite and is
independent of specific functions.
assigned FSC
FMS server cache assigned as the volume or cache server for an FMS client cache.
Each FMS client cache requires an assigned FSC to provide it with access to files. An
assigned FSC is typically the FSC nearest to the client host. In small deployments,
an assigned FSC can also serve as the parent FSC.
build platform
Platform required to build a customization. Compare with certified platform and
supported platform.
certified platform
Platform the base product is certified to operate on. Compare with supported
platform.
client tier
Teamcenter architectural tier that comprises the Teamcenter clients, Teamcenter
integrations with third-party applications, and the third-party applications
associated with the integrations.
connector
See Global Services connector.
connector to Teamcenter
Enterprise JavaBean that connects Global Services with Teamcenter. The optional
connector to Teamcenter is provided as a part of the Global Services connectors and
supports both two-tier and four-tier deployment configurations.
corporate server
Host computer at the center of a Teamcenter network. This host contains the
Teamcenter application root directory, Teamcenter data directory, licensing, File
Management System (FMS), and volumes. For installations that include the Web
tier (four-tier architecture), the corporate server also contains the Teamcenter server
manager. Multiple application clients can map to or mount the corporate server.
distribution server
See rich client distribution server.
eM-Planner interface
Interface between Teamcenter manufacturing process management and Tecnomatix
eM-Planner that allows data exchange.
enterprise tier
Teamcenter architectural tier that comprises a configurable pool of Teamcenter
C++ server processes and a server manager. Larger sites can distribute the pool of
server processes across multiple hosts. Smaller sites can run the pool of servers on
the same host as the Web tier.
facility
Physical location in an enterprise (for example, manufacturing plant or design
center). One facility can comprise multiple sites. Compare with site.
FCC
See FMS client cache (FCC).
• FMS file caching enables placing the data close to the user, while maintaining a
central file volume and database store.
FMS
See File Management System (FMS).
four-tier architecture
Teamcenter architecture that includes four tiers: resource tier, client tier, Web tier,
and enterprise tier. Contrast with two-tier architecture.
four-tier deployment
Deployment of the Teamcenter four-tier architecture. The Web tier, enterprise tier,
resource tier, and client tier can each be hosted on the same or separate computers.
FSC
See FMS server cache (FSC).
FSC group
Group of server caches defined in the FMS master configuration file.
group preference
Teamcenter preference applying to an entire group.
I-deas
Siemens PLM Software’s integrated CAD/CAM/CAE solution that is used to design,
analyze, test, and manufacture products.
IDSM server
Integrated Distributed Services Manager, a network node that runs a daemon process
to handle the transfer of data objects among sites in a Multi-Site Collaboration
network. One IDSM server node must be designated for each Teamcenter database
from which objects are published; each server node can act for one database only.
JT cache
Data Integration Services Adapter cache of JT files managed by the JT cache service
and accessible to Teamcenter lifecycle visualization users. See also world access
cache and limited access cache.
JT cache populator
Stand-alone Data Integration Services Adapter utility that prepopulates the JT
cache with JT part and assembly files.
Lifecycle Visualization
Visualization components available in the rich client, the thin client, and as a
stand-alone application. A scalable solution for the viewing and analysis of 2D and
3D product data, Lifecycle Visualization is available in a number of configurations
to meet the requirements of different organizations.
local server
Set of processes required to serve a single rich client installed on the same host
computer as the rich client. Teamcenter Integration for NX/NX Integration
configuration requires a local server.
manifest file
File that records and maintains information about the rich client image files,
including a list of the files and a version for each file. The Over-the-Web Installer
consults the manifest file to determine which files to download.
master FSC
FMS server cache that reads the master configuration file directly from the FMS
master host. An FSC is configured either to read the master configuration file
directly from the master host or to download it from another FSC with access to it.
Multi-Site Collaboration
Teamcenter capability that allows the exchange of data objects among several
Teamcenter databases. Transfer of objects among databases is controlled by daemon
processes running on designated servers. Objects are replicated by exporting them
from their original database and importing them into the requesting database.
Configuration of Multi-Site Collaboration is optional.
My Teamcenter
In the Teamcenter rich client and thin client, application that is the main access
point for managing product information. My Teamcenter provides the functionality
for creating objects in the Teamcenter database, querying the database for objects,
checking in and checking out objects, and managing tasks. Users can also open
objects, automatically launching the related application.
Each user has a personal My Teamcenter window that displays product information
as graphical objects. Although users share product information across the enterprise,
they organize this information individually in personal workspaces.
naming service
Service that maintains a list of names and the objects associated with them. For
the Teamcenter rich client, the naming service maintains a list of servers and the
objects and methods used by those services. The naming service is an integral part
of the server directory.
NS
See naming service.
NX Integration
Integration between Teamcenter and NX. NX Integration users have full access
to the Teamcenter user interface from NX, and they can also access NX from the
Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter
functionality available. Teamcenter Integration for NX excludes certain Teamcenter
functionality, such as workflow and product structure editing.
object chooser
Displays objects appropriate for linking with another Teamcenter product. In
determining the objects to display, the object chooser considers the security rights of
the person accessing the Teamcenter product. See also remote workflow.
object launcher
Launches another Teamcenter product from a linked object. Each Teamcenter
product has an object launcher. See also remote workflow.
ODBC driver
Teamcenter integration that allows ODBC-compliant applications such as Actuate
Report Writer, Crystal Reports, Microsoft Excel, and Access to extract data from a
Teamcenter database for building reports.
ODS server
See object directory services server.
ODS site
See object directory services site.
Oracle home
Directory in which Oracle software is installed on the Oracle server node.
Oracle server
Single installation of Oracle able to service queries from several Teamcenter
workstations. The ORACLE_SERVER environment variable defines this Oracle
service node. For large-scale installations, the Oracle server is typically a dedicated
high performance workstation that is optimized specifically for running Oracle
software.
Over-the-Web Installer
Installation program that downloads the rich client software from a distribution
server instance to the user’s workstation over the Web.
POM
See persistent object manager (POM).
preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter
session is initiated. Preferences allow administrators and users to configure many
aspects of a session, such as user logon names and the columns displayed by default
in a properties table.
published object
Object available to other sites in a Multi-Site Collaboration network. Publishing an
object creates a record in the ODS site database that can be read and searched by
other sites. Until an object is published, it can be seen only by the owning site.
QPL
See quick part locator.
QPL server
Quick part locator server. It provides a qpl daemon that can be used with
DesignContext in the rich client. The qpl daemon coexists with all Teamcenter
daemons. Without this daemon DesignContext does not work.
RDV
See Repeatable Digital Validation.
remote workflow
Teamcenter component that enables users to create links between Teamcenter
objects and objects in other Teamcenter products, such as Teamcenter portfolio,
program and project management. Users can then launch the linked Teamcenter
product from within either the rich client or the thin client.
resource tier
Teamcenter architectural tier comprising the database server, database, file servers,
and volumes.
rich client
Java-based user interface to Teamcenter installed on user workstations. The rich
client accesses Teamcenter databases using a remote or local server. Compare to
thin client.
role preference
Teamcenter preference applying to an entire role.
Security Services
Services that eliminate prompts for logon credentials when users switch Teamcenter
products within a user session. Authentication is performed by an external identity
service provider, such as lightweight directory access protocol (LDAP), instead of
the Teamcenter product. At a site that deploys multiple Teamcenter products and
Security Services, users log on once to access all participating Teamcenter products.
server manager
Process that manages a pool of Teamcenter server processes in a deployment of
the four-tier architecture. The server manager starts and times out a configurable
number of server processes to communicate with the Teamcenter database. A
server assigner process assigns available server processes to user sessions. The
server manager communicates with the Web tier application using either TCP or
multicast protocol.
server pool
Pool of Teamcenter server processes running in the enterprise tier. A small
deployment may have only one pool of server processes. For larger deployments, the
pool of server processes is distributed as subpools across multiple hosts, with a
server manager for each subpool. Server pools are applicable for deployments of the
Teamcenter four-tier architecture only.
site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
site ID
Unique identifier of a Teamcenter site. The site ID is used to generate internal
identifiers for Teamcenter objects that must be unique throughout an enterprise.
Once established, site IDs should not be modified.
site name
Unique name of a Teamcenter site stored in the database as a user-defined character
string.
site preference
Teamcenter preference that applies to the entire site.
STEP Translator
Teamcenter application that enables users to import product information into a
Teamcenter database and to export Teamcenter data via STEP-compliant physical
files.
supported platform
Platform configuration supported by GTAC.
system administrator
Teamcenter user who is a member of the system administration group.
TEM
See Teamcenter Environment Manager (TEM).
tessellation
Process that translates a CAD file to a visualization file.
thin client
Teamcenter user interface that provides a streamlined browser-based view of product
information stored in a Teamcenter database. The thin client is configured in the
Web tier, which creates and serves its Web pages to the client. Compare to rich client.
transient volume
Operating system directory controlled by Teamcenter and used to store temporary
data for transport of reports, PLM XML, and other nonvolume data between the Web
tier and client tier in a deployment of the Teamcenter four-tier architecture.
two-tier architecture
Teamcenter architecture that includes a resource tier and a client tier. The resource
tier comprises the database server and database. The client tier comprises the
Teamcenter rich client, third-party applications that integrate with the rich client,
and a local server. This architecture supports only the Teamcenter rich client.
Contrast with four-tier architecture.
two-tier deployment
Deployment of the Teamcenter two-tier architecture. In a typical deployment of the
two-tier architecture, the rich client and its local server are installed on a user’s
workstation as are third-party applications that integrate with the rich client. The
database server and the Teamcenter corporate server are installed on one or more
separate computers.
user preference
Teamcenter preference applying to a specific user.
visualization
Ability to display a realistic, real time, graphical visualization of geometric data.
volume
Operating system directory controlled by Teamcenter and used to store the files
managed by Teamcenter. When a user performs an action that causes Teamcenter
to create a file, the file is created in the Teamcenter volume. Users cannot directly
access the files in Teamcenter volumes; they must do so via a Teamcenter session.
Web tier
Teamcenter architectural tier that comprises a Java application running in a Java
2 Enterprise Edition (J2EE) application server. The Web tier is responsible for
communication between the client tier and enterprise tier.
world
All users regardless of group or role.
Kernel . . . . . . . . . . . . . . . . . . . . . . A-9 Q
Web tier . . . . . . . . . . . . . . . . . . . . . D-1 QPL for Repeatable Digital Validation . . C-9
Password, valid characters . . . . . . 16-3–16-4 QPL server . . . . . . . . . . . . . . . . . . . . . . 2-4
Patches . . . . . . . . . . . . . . . . . . . . . . . 19-1 Quick preconfigured installation . . . . 6-5–6-6
Patching
Customer-specific patches . . . . . . . . . 19-6
Patching rich client R
Customer-specific patches . . . . . . . . . 19-6 rc.ugs file . . . . . . . . . . . . . . . . . . . . . . . 7-1
Described . . . . . . . . . . . . . . . . . . . . 19-4 rc.ugs.actionmgrd script . . . . . . . . . . . . . 7-1
Silently . . . . . . . . . . . . . . . . . . . . . . 19-4 rc.ugs.subscriptionmgrd script . . . . . . . . 7-1
Using Over-the-Web Installer . . . . . . 19-4 rc.ugs.task_monitor script . . . . . . . . . . . 7-1
Patching Teamcenter lifecycle RDV
visualization . . . . . . . . . . . . . . . . . . . 19-6 Database instance . . . . . . . . . . . . . . 2-18
Patching the server . . . . . . . . . . . . . . . 19-2 QPL server . . . . . . . . . . . . . . . . . . . . 2-4
Patching thin client . . . . . . . . . . . . . . . 19-7 README file . . . . . . . . . . . . . . . . . . . 19-8
PATH environment variable . . . . . . . 4-7–4-8 Red Hat Linux
Penetration Request Management . . . . C-11 Fully qualified domain names . . . . . . . 1-3
Platform support . . . . . . . . . . . . . . . . . . 1-1 Fully-qualified domain names . . . . . . . 6-5
Database servers . . . . . . . . . . . . . . . . 1-2 Length of host name . . . . . . . . . . . 1-3, 6-5
POM transmit schema files . . . . . . . . . . 7-3 Red Hat Linux platforms
Pool manager, starting . . . . . . . . . . . . . . 9-5 Platform support . . . . . . . . . . . . . . . . 1-1
portal directory . . . . . . . . . . . . . . . . . . B-2 System requirements . . . . . . . . . . . . . 1-1
portalHelpPage property . . . . . . . . . . . A-3 Remote Method Invocation . . . . . . 8-20, 8-39
Postinstallation tasks . . . . . . . . . . . . . . 7-1 Remote workflow
Postupgrade tasks . . . . . . . . . . . . . . . . . 7-1 Site planning . . . . . . . . . . . . . . . . . . 2-16
Preferences Remote Workflow . . . . . . . . . . . . . . . . C-9
Fms_BootStrap_Urls . . . . . . . . . . . . . 6-3 Installation . . . . . . . . . . . . . . . . . . . C-9
IDSM_permitted_sites . . . . . . . . . . . . 7-3 Removing features . . . . . . . . . . . . . . . 16-2
ODS_permitted_sites . . . . . . . . . . . . . 7-3 Render
ODS_searchable_sites . . . . . . . . . . . . 7-3 Formats . . . . . . . . . . . . . . . . . . . . . 14-2
ODS_site . . . . . . . . . . . . . . . . . . . . . . 7-3 Prerequisites . . . . . . . . . . . . . . . . . . 14-1
TC_publishable_classes . . . . . . . . . . . 7-3 Translators . . . . . . . . . . . . . . . . . . . 14-1
TC_transfer_area . . . . . . . . . . . . . . . . 7-3 Render Document for Rich Client . . . . . C-10
WEB_core_help_server . . . . . . . 15-9, A-3 Render Manager
WEB_default_site_deployed_app_ Installation . . . . . . . . . . . . . . . . . . . C-10
name . . . . . . . . . . . . . . . . . . . . . A-3 Required features . . . . . . . . . . . . . . C-10
WEB_help_server . . . . . . . . . . 15-9, A-3 Repeatable Digital Validation . . . . . . . . C-9
Prerequisite software . . . . . . . . . . . . . . 1-1 Requirements
Prerequisites Database . . . . . . . . . . . . . . . . . . . . . . 1-1
Character set . . . . . . . . . . . . . . . . . . . 5-4 Database, IBM DB2 . . . . . . . . . . . . . . 3-1
GM Overlay . . . . . . . . . . . . . . . . . . . . 5-4 IBM DB2 . . . . . . . . . . . . . . . . . . . . . . 3-1
Problem Reports (PRs) . . . . . . . . . . . . . 19-8 Java . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Product Master Management Operating systems . . . . . . . . . . . . . . . 1-1
CAD-BOM Alignment . . . . . . . . . . . . C-6 Requirements Management . . . . . . . . . C-16
Product Master Manager . . . . . . . . . C-6 Resource Manager, Genius4000 data
Product Master Manager . . . . . . . . . . . C-6 migration . . . . . . . . . . . . . . . . . . . . . 12-2
Programs Resource tier
Web Application Manager . . . . . . . . 19-4, Four-tier . . . . . . . . . . . . . . . . . . . . . 1-14
19-6–19-7 Two-tier . . . . . . . . . . . . . . . . . . . . . 1-11
Properties, portalHelpPage . . . . . . . . . A-3 Reverse proxy configuration
Proxy WAR file (WebLogic) . . . . . . . 8-7, 8-12 SiteMinder . . . . . . . . . . . . . . . . . . . 8-34
WebSEAL . . . . . . . . . . . . . . . . . . . . 8-34
Rich client
Deployment over the Web . . . . . . . . . 8-17