Upgrade Teamcenter Guide
Upgrade Teamcenter Guide
Upgrade Guide
Publication Number
PLM00129 H
Proprietary and restricted rights notice
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Using the upgrade log viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting Teamcenter upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
Tables
Supported upgrades
Teamcenter 10.1 supports upgrades from Teamcenter 8 and all later versions and
MPs. This includes:
• Teamcenter 8 and all MP versions
To upgrade from earlier versions, you must first upgrade to one of these supported
versions, and then upgrade to Teamcenter 10.1.
Release information
Before you begin upgrading, read the following documentation deliverables to learn
about new features in Teamcenter 10.1 and issues that may affect your upgrade:
• What’s New
Contains information about new features in Teamcenter 10.1.
In addition, read the release bulletins for all Teamcenter versions since your current
Teamcenter version level to learn about new features and issues that may affect your
upgrade. These release bulletins are available on GTAC:
http://support.industrysoftware.automation.siemens.com
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.
1. Includes release notes and new feature information for Teamcenter 8 and Teamcenter 8 MP1.
• 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.
Microsoft Windows
• Make sure the C:\Temp directory exists, and grant full access permissions
to this directory for all users.
2. Teamcenter client communication system (TCCS) is installed with the rich client. This column refers to the stand-alone TCCS
application.
3. 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.
4. Microsoft Windows server platforms include Windows Server 2008.
5. Itanium platforms only. PA-RISC hardware is not supported.
6. Only 64-bit Red Hat Linux is supported.
• Disable the Windows TCP scaling feature. Open a command prompt and
enter the following command:
netsh interface tcp set global autotuninglevel=disabled
• Teamcenter applications are provided in 32-bit and 64-bit versions. Use the
appropriate Teamcenter software distribution image for your platform.
2. Open the Regional and Language Options dialog box in the Windows
Control Panel.
3. In the Languages tab, set the required language for the menus and
dialogs.
4. In the Advanced tab and the Regional Options tab, set the required
language.
Sun Solaris
Teamcenter executables are 64-bit applications. Teamcenter 10.1 is supported
only on 64-bit Solaris.
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 the appropriate server installation guide (for Windows
or UNIX/Linux).
• Web tier
The Web tier includes the Web Application Manager, a distribution server, and a
distribution server instance that contains the Over-the-Web installer and Rich
Client 4-tier solutions. Additional solutions may require additional disk space.
For more information, see the appropriate server installation guide (for Windows
or UNIX/Linux).
Database
Teamcenter requires a relational database management system (RDBMS) for storing
Teamcenter data. Before you install a Teamcenter, you must install an IBM DB2,
Oracle, or Microsoft SQL Server 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
Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE Linux
platforms.
For information about installing a database server for Teamcenter, see Upgrading
database servers.
Web browser
The Teamcenter thin client and Over-the-Web Installer8 require a Web browser.
Teamcenter 10.1 supports the following Web browsers:
The Teamcenter thin client requires a Web browser. Teamcenter 10.1 supports the
following Web browsers:
For information about versions supported, see the Siemens PLM Software
Certification Database.
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.
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.
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.
9. A deployable file is a Web archive (WAR) or enterprise archive (EAR) file, depending on the solutions it contains.
Templates
A template is a container that holds data model definitions. A template can contain
any number of business objects, classes, lists of values, and business rules. Any
Teamcenter feature that adds definitions to the data model has an associated
template. In addition, templates can be supplied to you from another Teamcenter
site, partner, or third party.
Caution You must have access to all templates used at your site before beginning
the upgrade of the corporate server. This is very important. During
the corporate server upgrade, you load all templates used by your site.
Templates can only be loaded during the upgrade of the corporate server.
They cannot be loaded after the upgrade. Failing to load all templates
your site depends on causes problems in managing the data model and
can result in loss of data, time, and money.
Loading templates
Before you upgrade the corporate server, you must have access to all templates on
which your site depends.
• After you select the template, it is listed in the Upgrade Database Feature panel.
To obtain a composite host ID for your license server, run the getcid utility on your
license server host. Download this utility from GTAC:
1. Open the GTAC Web site:
http://support.industrysoftware.automation.siemens.com
4. On the FTP site, click the directory corresponding to the platform type of your
license server, for example, wntx64.
5. On the resulting page, download the getcid.exe utility (Windows systems) or the
getcid utility (UNIX/Linux systems).
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.
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.
port@host
Replace port with the port number and host with the host name of the license
server, for example, 28000@tchost. The port and host values must match those
you specified in the SERVER line of the Teamcenter license file.
UNIX/Linux systems:
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.
• After upgrade is completed, you must contact your database vendor for processes
and tools to convert your existing database character set encoded data to Unicode
UTF-8 character set encoded data for storage to a new database.
For more information about environment settings for your locale, platform, and
character set, see the following topics:
• For information about environment settings for non-UTF-8 UNIX and Linux
systems, see the Installation on UNIX and Linux Servers Guide.
• For information about environment settings for UTF-8 UNIX and Linux systems,
see the Installation on UNIX and Linux Servers Guide.
• For information about environment settings for Windows systems, see the
Installation on Windows Servers Guide.
On all UNIX and Linux platforms supported for Teamcenter 10.1, set the process
memory size (the ulimit user environment parameter) to unlimited before
installing Oracle.
To avoid errors during installation, or operation errors after installation, review
kernel parameter settings to ensure that they meet the recommended Oracle settings
described in the following sections. The recommended kernel parameter settings
are for a typical Oracle database environment. If you previously tuned kernel
parameters to levels that meet other application needs, continue to use those values.
Initially, you can set kernel parameters as described in the Oracle documentation.
For some operating systems, kernel parameters may need adjustment according to
available system memory. The Oracle installation program issues warnings if kernel
parameters do not meet minimum requirements.
Note The recommended values are minimum values. For production database
systems, Oracle recommends that you tune the values to optimize
system performance. For more information, see the operating system
documentation.
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.
Set kernel parameters as described in the following table. Set parameters using the
method described in your HP-UX documentation.
Caution Do not change the kernel parameter settings if the parameters were set
for another program and the values are greater than the levels Oracle
requires.
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.
• For the C shell (csh or tcsh), add the following lines to the
/etc/csh.logon.local file:
if ( $USER == "oracle" ) then
2. Export the contents of your 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
full path and name of the dump file to contain the exported data; replace export
with the name of the log file to contain export output.
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.
4. Click Stop.
Replace password with the password for the sys user account.
Oracle starts the Oracle SQL*Plus utility.
Note The sys user must be in the Oracle sysdba group for the Oracle system
identifier (SID) used by Teamcenter. To connect as internal (without
a password), the account must be part of the ORA_DBA local group
in Windows.
shutdown
4. Exit SQL*Plus:
exit
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
• On Sun Solaris systems, the oratab file in either the /var/opt/oracle directory,
or the /etc directory on other UNIX or Linux platforms.
2. When the Oracle installer prompts you to upgrade existing databases, enter the
required information about the databases you want to upgrade.
For more information, see the procedure for installing an Oracle server in the
appropriate server installation guide (for Windows or UNIX/Linux).
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. Internal integer IDs used by SQL Server can differ between sites.
3 Upgrading a Teamcenter
corporate server
3 Upgrading a Teamcenter
corporate server
Upgrade overview
Before you upgrade your production systems to Teamcenter 10.1, perform an
upgrade on a test system. The upgrade process consists of the following tasks:
1. Upgrade a template project to the current data model format.
You must upgrade your template project in the Business Modeler IDE before you
upgrade a test database or your production systems because the XML formats of
template files can change between product releases. Your custom template project
must be modified to fit the new XML format.
Always test the upgrade process on a test system that reflects your production
system before you begin upgrading your production system. Upgrading a test system
can reveal issues that may prevent an upgrade from completing successfully. After
you resolve these issues on the test system, your can proceed with upgrading your
production system. This helps minimize downtime for your production environment.
Note • Make sure you have access to the Business Modeler IDE Guide during
upgrade.
• In addition, make sure you have access to the Business Modeler IDE Best
Practices Guide available from GTAC.
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. Perform any steps recommended in the report to resolve site inconsistency errors.
Role Group
Project Administrator Project Administration
Upgrade may fail if these groups and roles are not present.
Before running the utility, make sure you have administrative privileges. The utility
reports duplicates based on data conditions.
The cleanup_psdata utility cleans up part structure data such as duplicate variant
objects by removing references to them. You specify the type of data to be cleaned up
using command line arguments, such as -duplicate_variants.
The utility operates in two modes:
• Reporting mode only
This mode generates a file named duplicate_variants_report_timestamp.csv,
which contains a report of all duplicate variant objects with UIDs of variant
options, variant revisions, numbers of expressions referring to duplicate options,
and other information.
Syntax:
cleanup_psdata [-u=user-name] [-p=password] [-g=group-name]
-duplicate_variants -report_file_path=path
Replace path with a valid local drive path for the report files.
Replace path with a valid local drive path for the report files.
3. After export is complete, verify files on the Autonomy host and determine how
many files were generated (file-name-n.idx.gz). This information is needed when
importing indexed data into the new Autonomy database.
1. Instruct all users to close and log off of Teamcenter sessions, including tcserver
processes.
3. Use the clearlocks utility to check for nodes connected to the database and
remove locks on the database:
Windows systems:
%TC_BIN%\clearlocks -u=infodba -p=infodba-password -g=dba
-assert_all_dead
4. On UNIX and Linux systems, 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.
• Import wizard
If your template project is not already in the workspace, import it into the new
version of the Business Modeler IDE:
1. Choose File®Import.
For more information about importing a template, see the Business Modeler
IDE Guide.
2. In the Template Project Upgrade dialog box, click the arrow in the Project
box to select the project to upgrade.
3. Click Finish.
The project is upgraded to the new data model format. The Console view
displays success or failure messages for the upgrade.
After upgrade, open the Project Files folder and check for any error or
warning messages in the log in the output\upgrade folder.
Caution After a template project is upgraded, it cannot be used for installation or
upgrade in a previous version of Teamcenter. To find out the version the
template has been upgraded to, see the ProjectInfo.xml file found at
the bottom of the Project Files folder and view the migratedRelease
value in the file.
Upgrading the custom template may be part of a larger process when you upgrade to
the latest version of Teamcenter:
1. Import the older project into the latest version of the Business Modeler IDE.
This updates the data model to the latest data model version.
upgrade failures and minimize downtime when implementing the upgrade on your
production system.
You can create a test environment two ways:
• Copy a Teamcenter environment using TEM.
1. Copy your Teamcenter database using the utilities and documentation provided
by your database vendor.
2. Copy any volumes that contain any data you may want to access before or after
the test upgrade.
It is not necessary to copy any volume data, but volume data not copied would
not be available in the copied environment.
Note There are three possible scenarios for copying volume data:
• Copying no data
TEM creates empty volumes to represent the actual volumes. New
data can be created in these volume, but no existing data would be
available in the copied environment.
3. Launch TEM, select Create environment for upgrade testing, and then click
Install.
5. In the Test Environment Location panel, enter the installation directory for
the test environment.
Note TEM does not prompt you to select features. Features are installed in the
test configuration based on the data models installed in the database.
You can add additional features after the copy process is complete.
6. In the File System Cache Service (FSC) panel, type the required values for
creating the FSC. The FSC must be a master FSC.
The copy process creates its own FSC to support the volumes.
This panel appears the same as in a typical Teamcenter installation.
7. In the Foundation Database panel, enter the database information for the copy
of the database you created in step 1.
After you enter access information to the copied database, TEM determines
which features are installed from the data models registered with the database.
If any features are not included in the Teamcenter software distribution image,
locate those features in the following step.
8. In the Database Configuration panel, examine the list of features found in the
database. If any feature is missing a Path value, click Browse to locate those
features.
All features in this list must be located before you can continue.
10. In the Teamcenter Administrative User panel, type the user name and password
for the Teamcenter administrative user (infodba by default).
11. In the Flex License Server panel, enter access information for the Teamcenter
license server.
12. In the Confirmation panel, review the information shown, and then click Start to
begin creating the test environment.
Note If you install a rich client that points to the TC_DATA directory of a
copied corporate server environment, set the TC_SKIP_CLIENT_CACHE
variable to TRUE in the appropriate rich client launch file:
• Linux systems: TC_ROOT/portal/start_portal
Set this variable before you launch the rich client that points to the copied
server environment.
If your original corporate server environment contains a rich client before
you create the copy of the environment, this step is not necessary to launch
that rich client. However, if you add an additional rich client, you must set
TC_SKIP_CLIENT_CACHE to TRUE before you launch the additional
client.
1. Copy your Teamcenter database using the utilities and documentation provided
by your database vendor.
2. Copy any volumes that contain any data you may want to access before or after
the test upgrade.
It is not necessary to copy any volume data, but volume data not copied would
not be available in the copied environment.
3. Create volumes to replace the production volumes. The upgrade process requires
access to volumes. As a minimum, all the same directories need to be re-created
in the test system. If possible, obtain a complete copy of each volume. Multiple
volumes from different volume servers can be consolidated for upgrade testing
if necessary. This is recommended because it reduces the number of volume
servers needed for testing.
Note • If you upgrade from Teamcenter 8.3 or earlier and you want to be
able to log on to the test environment after completing the test
upgrade, perform one of the following steps:
o Copy the default volume directory for the Teamcenter
administrative user (infodba) to your test environment. This
ensures all administrative data is available to the client host
during logon.
4. Launch the rich client and log into the Organization application and change
the host and location of all volumes to the new location for the volumes setup
in step 3.
Warning Not performing this step causes the test upgrade to modify the
production volume, not the test volume.
6. Launch TEM from the test environment’s TC_ROOT directory and add the FSC
server. If the volumes for the test environment are being served from different
systems, you must install FSCs on the appropriate systems.
Note Consolidating volumes onto a single host can make this step easier.
7. Run the index verifier utility (index_verifier) to verify all database indexes are
present. This can prevent potential performance problems caused by missing
database indexes after upgrade. The index_verifier utility can find and create
missing indexes immediately or perform a dry run to identify missing indexes
so you can create them later using index_verifier or a database vendor utility
such as SQL*Plus for Oracle, SQL Server Management Studio or sqlcmd for
Microsoft SQL Server, or the Command Line Processor (CLP) for DB2.
Windows systems:
b. Optionally, run index_verifier with the DRYRUN option to find (but not
create) missing indexes:
%TC_BIN%\index_verifier -u=infodba -p=infodba-password -g=dba
-o=DRYRUN > missing_indexes.sql
b. Optionally, run index_verifier with the DRYRUN option to find (but not
create) missing indexes:
$TC_BIN/index_verifier -u=infodba -p=infodba-password -g=dba
-o=DRYRUN > missing_indexes.sql
For more information about the index_verifier utility, see the Utilities
Reference.
After you complete these steps, you can begin upgrading the test environment.
Note If you use Teamcenter Integration for I-deas, make sure you run the
TcII.bat script (on Windows systems) or the TcII.sh script (on UNIX or
Linux systems) before you launch Teamcenter Environment Manager
(TEM) to upgrade the corporate server. This sets the CLASSPATH
variable and other variables required to enable TEM to find installation
files for Teamcenter Integration for I-deas.
The TcII.bat/sh script is on the Teamcenter Integration for I-deas
software distribution image.
4. In the Old Application Root panel, enter the path to your Engineering Process
Management root (TC_ROOT) directory.
6. In the Configuration panel, type a description and an ID for the new corporate
server.
Click Browse to add any custom features not included in the table. Browse to
the locations of feature files for custom features.
In the New Application Root Directory box, enter the root directory for the new
corporate server. This is the TC_ROOT directory for the upgraded Teamcenter
installation.
8. In the Operating System User panel, type the password for the operating system
user performing the upgrade.
9. In the Teamcenter Administrative User panel, type the password for the
Teamcenter administrator (infodba) account.
10. Proceed to the Upgrade Information panel and enter the required values.
Value Description
Old TC_DATA Location Specifies the path to the TC_DATA directory
for the corporate server to be upgraded. Verify
that the path shown is correct.
New TC_DATA Location Specifies the path you want to use for the
new TC_DATA directory on the upgraded
(Teamcenter 10.1) corporate server.
Database User Specifies the user name of the Engineering
Process Management database user. This is
also the name of the Teamcenter 10.1 database
user.
The Engineering Process Management
database user must have database
administrator (DBA) rights on the server.
Database Password Specifies the password for the database user.
11. Proceed to the Upgrade Database Features panel. This panel contains a table of
feature templates found in the database with the status of each in the Status
column.
When TEM prompts you for the custom template, click the Browse button and
navigate to the newly packaged template and libraries.
Features whose status is Upgrade are included in the Teamcenter 10.1 software
distribution image and are to be upgraded to Teamcenter 10.1.
If your site depends on templates from asynchronously released features or on
templates supplied by other sites, partners, or third parties, click the Browse
button to locate the template package (ZIP) file for each missing template.
You must provide paths to all feature templates before you can proceed with
upgrade. The Next button is disabled until valid paths are provided for all
templates.
Warning Failure to locate the correct paths for all template packages results
in migration issues with your custom data model to the Business
Modeler IDE, possible corruption of data, and problems with the
Teamcenter server.
12. In the Upgrade Options panel, select how you want to manage errors
encountered during upgrade.
• Stop database upgrade at first error
This option stops Teamcenter upgrade when the first error occurs.
Note Siemens PLM Software strongly recommends this option when
upgrading production systems.
Using the upgrade errors report displayed in TEM, you can address multiple
issues preventing a successful upgrade before you attempt an upgrade again.
You can also submit the upgrade errors log file to Siemens PLM Software
customer support for further analysis.
If you want to generate a client cache, click Generate client cache. This option
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.
If you select this option, TEM runs the generate_client_meta_cache utility at
the end of the install, upgrade, or update action. If you do not select this option,
but a client cache already exists, the old client cache is deleted.
For more information about the generate_client_meta_cache utility, see the
Utilities Reference.
13. In the Flex License Client panel, enter the license server and license file
information.
15. Allow time for the remaining pre-upgrade diagnostic tests to complete.
If any test fails, click the appropriate View button to view details of the failed
test. Click Review to view complete results of the pre-upgrade diagnostics.
Perform any recommended steps in the diagnostic reports to resolve the failures.
After performing these steps, click Run to perform pre-diagnostic tests again.
TEM does not allow the upgrade to proceed until pre-diagnostic failures are
resolved.
Note For more information about resolving pre-upgrade diagnostic failures,
see the Teamcenter Data Model and Upgrade Issues Catalog on GTAC:
http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
You must have a WebKey account to access the Web site.
If all diagnostic tests are successful (the Results column displays Passed for all
tests), click Next to continue.
16. In the Confirmation panel, review your selections. If you need to make a change,
click Back. When you are ready to begin upgrade, click Start.
The Upgrade Features panel displays the status of the upgrade.
Note If your configuration includes the Online Help feature, TEM prompts
you for the location of the Teamcenter 10.1 tchelp.jar file during the
upgrade.
18. Run the clean_backpointer utility on your database. This utility removes
relation_type object references and ImanRelation primary and secondary
object references from the backpointer table.
As of Teamcenter 9.1, these objects are stored in the ImanRelation table to
improve performance. Run the clean_backpointer utility after upgrading
from a version previous to Teamcenter 9.1 if your previous deployment
stored relation_type object references and ImanRelation primary and
secondary object backpointer references the backpointer table, rather than the
ImanRelation table.
Because the utility’s cleanup operation may be time-consuming, this process is
not run during the upgrade process. You must run this utility manually, after
upgrade, on an upgraded database.
For more information about this utility, see the Utilities Reference or the System
Administration Guide.
1. Open TEM in the new version and upgrade the production database.
During the upgrade, TEM automatically installs the dependent templates from
the new version.
2. When TEM prompts for the custom template, click the Browse button and
navigate to the newly packaged template and libraries.
1. Start TEM.
Windows systems:
Click Start and choose Programs→Teamcenter 10.1→Environment Manager.
Alternatively, you can run the tem.bat file in the install directory in the
application root directory for the Teamcenter installation.
UNIX systems:
a. Access the install directory in the Teamcenter application root directory for
the Teamcenter installation or configuration you want to modify.
4. Perform the remaining steps as for upgrading the Teamcenter corporate server.
Replace host with the host name of the Autonomy server and port with the index
port used by the server. (The default port number is 9001.) Replace path and
file-name with the Autonomy export path and file name you specified in Export
indexed data from earlier Autonomy database. Replace config-ID with the ID of
the Teamcenter configuration.
For example:
http://myhost:9001/DREADD?C:\backup\output-0.idx.gz
&DREDbName=FTS_MYDB
This imports existing Autonomy indexed data (output-0.idx.gz) into the new
Autonomy IDOL 7.3.4 database (FTS_MYDB).
Note The name of the Autonomy database is also stored in the
TC_fts_database_name preference.
3. Start Access Manager and add rules introduced to Teamcenter since your
previous version:
o If your legacy Teamcenter version is earlier than Teamcenter 2007.1
MP1, add the Inactive Sequence rule:
a. Select the Has Class (POM_object) root node.
Leave the Read and Copy blank (unset). They must be blank.
o If your previous installation was earlier than Teamcenter 8.3, add the
Translation rule:
a. Select the Has Class (POM_object) root node.
• If you have few or no custom rules, use the standard Teamcenter 10.1 rule tree
and then manually add your custom rules.
1. Create a backup of your existing rule tree using the Access Manager Export
action.
For more information, see the Access Manager Guide.
4. Import the standard Teamcenter 10.1 rule tree using the am_install_tree
utility. Use the mode=replace_all argument to overwrite the legacy rule
tree with the Teamcenter 10.1 rule tree. The utility automatically creates
ACLs and privileges during import.
For more information about the am_install_tree utility, see the Utilities
Reference.
5. Manually add your custom rules into the rule tree in the appropriate
locations.
For more information, see the Access Manager Guide.
Teamcenter 10.1 adds localization support for Access Manager. This includes
locale-specific display names of access control list (ACL) objects, privilege names,
and accessor type values such as group names and role names. This localization
capability is provided using text server XML files. The rule tree import/export
functionality supports XML format input files.
The am_install_tree utility supports both ASCII text format and XML format rule
tree file in Teamcenter 10.1. However, export in the Access Manager application
generates the output file only in XML format. This allows exported ACL name
translations to be migrated to other sites.
For more information about the am_install_tree utility, see the Utilities Reference.
A Teamcenter 10.1 XML Access Manager rule tree resembles the following example.
<rule_tree>
<tree_node>
<rule_name>Has Class</rule_name>
<rule_argument>POM_object</rule_argument>
<acl_name></acl_name>
<tree_node>
<rule_name>Has Bypass</rule_name>
<rule_argument>true</rule_argument>
<acl_name>Bypass</acl_name>
</tree_node>
<tree_node>
<rule_name>Has Status</rule_name>
<rule_argument></rule_argument>
<acl_name>Vault</acl_name>
</tree_node>
<tree_node>
<rule_name>Has Class</rule_name>
<rule_argument>POM_application_object</rule_argument>
<acl_name>Working</acl_name>
<tree_node>
<rule_name>Has Class</rule_name>
<rule_argument>Dataset</rule_argument>
<acl_name>Dataset ACL</acl_name>
</tree_node>
</tree_node>
</tree_node>
</rule_tree>
</Tc_data_access_config>
Replace export-file with a path and file to contain the exported preferences, for
example, post_upgraded_site_preferences.xml.
Replace export-file with the file you exported in step 1. Replace output-file
with a path and file to contain the script output. Replace report-file with a
path and file to contain the results of the preferences upgrade.
The report-file file contains names of preferences that failed to upgrade
successfully.
3. Correct all preferences reported in the report-file file in step b. Write the
corrections in an input XML file, for example, corrected_site_preferences.xml.
Replace input-file with the corrected preferences file you created in step 3.
For more information about these preferences, see the Preferences and Environment
Variables Reference.
• CommercialPart_DefaultChildProperties
• VendorRevision_DefaultChildProperties
Removing these revision_list values can prevent some rich client performance
problems after upgrade.
Siemens PLM Software recommends that you do not modify the default scope rules.
If necessary, you can create a copy of the default rules and modify the copy as needed.
For more information about changes to default scope rules, see the Data Exchange
Guide.
Find the persistent class and persistent attribute for traversing to the secondary
object and update by replacing the clause using the persistent class/attribute.
Update by replacing the clause with list of clauses. Each new clause uses
the exact class name of the secondary object and attribute name to reach the
secondary object.
Tip The TC XML schema differs from PLM XML schema used in releases prior
to Teamcenter 8.3. However, you can control which schema is used for
your custom reports by setting the TIE_fast_traversal preference value to
false. This allows your custom reports to run without modification. As an
alternative, you can add the opt_fast_traversal option, with its value set
to false, to your transfer option set.
o On Microsoft SQL:
ALTER TABLE DIS_MEASMT_EVENT ADD INSERTION_DATE_TIME DATETIME;
For help with any panel in TEM, click the help button .
1. Start Teamcenter Environment Manager (TEM).
Windows systems:
From the Windows start menu, choose Programs®Teamcenter 10.1,
right-click Environment Manager, and then choose Run as administrator.
4. In the Old Application Root panel, enter the path to your previous Teamcenter
two-tier rich client root directory (TC_ROOT).
6. In the Old Configuration panel, select the configuration that contains the
two-tier rich client you want to upgrade.
7. In the Configuration panel, type a description and an ID for the new corporate
server.
9. Proceed to the File Client Cache panel and specify FMS client cache (FCC)
settings.
Value Description
Use current FCC Select this option if you want to keep your existing FCC
location.
Use new FCC Select this option if you want to use the proposed new
FCC location.
TEM sets the FMS_HOME environment variable on this host to point to the
selected location.
To specify advanced settings for Teamcenter client communication system
(TCCS), click Advanced.
Note In Teamcenter 10.1, FMS supports UTF-8 encoding. Client applications
can use existing 8-bit encoding (native), UTF-8 encoding (8-bit Unicode)
or Unicode wide character (wchar) APIs. The UTF-8 and Unicode
(wchar) FCC and FSC and UTF-8 APIs operate consistently with any
client locale or native encoding. After a client application migrates to the
new Unicode APIs, the native encodings of the FCC and FSC no longer
need to match that of the Unicode client application.
On Windows systems, Windows 7 or later is required for full UTF-8
support. UTF-8 is not supported on Windows XP and earlier versions.
For more information about administering FMS, see the System
Administration Guide.
10. In the FCC Parents panel, specify settings for the parent FMS server caches
(FSCs) used by the FMS client cache (FCC). FSCs are used in the priority you
specify.
The FSC assignment mode box specifies how you want to assign FSCs.
To add an FSC to the list, click Add. TEM adds a row to the table of FSC values.
Double-click the Protocol, Host, Port, or Priority boxes to enter values.
To modify a value in the table, double-click the box and enter the new value.
To remove an FSC from the table, select the row and click Delete.
11. In the 2-tier server settings panel, specify values required for the rich client to
access your Teamcenter server. Make sure that the TC_DATA value points to the
TC_DATA directory for your upgraded corporate server.
12. In the Rich Client Settings panel, specify settings for online help access.
If you want to specify Security Services settings or other advanced rich client
settings, click Advanced.
14. Allow time for the remaining pre-upgrade diagnostic tests to complete.
If any test fails, click the appropriate View button to view details of the failed
test. Click Review to view complete results of the pre-upgrade diagnostics.
Perform any recommended steps in the diagnostic reports to resolve the failures.
After performing these steps, click Run to perform pre-diagnostic tests again.
TEM does not allow the upgrade to proceed until pre-diagnostic failures are
resolved.
Note For more information about resolving pre-upgrade diagnostic failures,
see the Teamcenter Data Model and Upgrade Issues Catalog on GTAC:
http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
You must have a WebKey account to access the Web site.
If all diagnostic tests are successful (the Results column displays Passed for all
tests), click Next to continue.
15. In the Confirmation panel, review your selections. If you need to make a change,
click Back. When you are ready to begin upgrade, click Start.
The Upgrade Features panel displays the status of the upgrade.
Note If your configuration includes the Online Help feature, TEM prompts
you for the location of the Teamcenter 10.1 tchelp.jar or other online
help files file during the upgrade.
o Windows systems:
Uninstall the rich client using the program list in the Windows Control
Panel. Find Teamcenter 10.1 or Teamcenter 10.1 (x64) (for the 64-bit rich
client ) in the program list and uninstall the program.
o Linux systems:
Uninstall the rich client using TEM.
For more information, see Uninstall the rich client using TEM.
4. In the Old Configuration panel, select the configuration you want to remove,
then click Next.
5. In the Uninstall panel, select Yes to confirm that you want to uninstall the
configuration. Click Next.
6. In the Uninstall Teamcenter panel, select the Advanced Uninstall Options check
box if you want to view additional uninstall options. Otherwise, click Next.
After stopping the FCC process, the fccstat command reports that the FCC
is offline.
4. After the uninstallation script is finished, remove the rich client root installation
directory.
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Overview
You can upgrade from Teamcenter Express or Teamcenter Rapid Start to Teamcenter.
For information about upgrading a Teamcenter Express environment to a
Teamcenter Rapid Start environment, see the Teamcenter Rapid Start for Windows
Installation Guide.
• Before upgrading, ensure that all Teamcenter user sessions are terminated.
• Ensure that you have write permission on the default volume of the
administrative user (infodba).
• All customizations done outside the database (for example, portal properties)
must be moved forward manually. All customizations done within the database
are carried over by reusing the same database.
• Before upgrading the client, be sure that the server you plan to connect to has
been upgraded to Teamcenter 10.1.
• If you have custom templates (custom objects), migrate them to the compatible
versions using the steps described in Upgrade a template project to the current
data model format. Note the following:
o Make sure that custom templates have been deployed using TEM.
o Ensure that you have access to the Business Modeler IDE projects of the
custom templates deployed on the server.
o Ensure that you have the latest package templates for all of your Business
Modeler IDE projects. If you have performed any changes since the previous
TEM deployment of the templates, you must redeploy them.
• Import wizard
If your template project is not already in the workspace, import it into the new
version of the Business Modeler IDE:
1. Choose File®Import.
For more information about importing a template, see the Business Modeler
IDE Guide.
2. In the Template Project Upgrade dialog box, click the arrow in the Project
box to select the project to upgrade.
3. Click Finish.
The project is upgraded to the new data model format. The Console view
displays success or failure messages for the upgrade.
After upgrade, open the Project Files folder and check for any error or
warning messages in the log in the output\upgrade folder.
Caution After a template project is upgraded, it cannot be used for installation or
upgrade in a previous version of Teamcenter. To find out the version the
template has been upgraded to, see the ProjectInfo.xml file found at
the bottom of the Project Files folder and view the migratedRelease
value in the file.
Upgrading the custom template may be part of a larger process when you upgrade to
the latest version of Teamcenter:
1. Import the older project into the latest version of the Business Modeler IDE.
This updates the data model to the latest data model version.
4. Click Upgrade.
5. In the Old Application Root dialog box, browse to the path of the application
directory of the previous installation and click Next.
TEM displays the Old Configuration panel.
Note Record the description and ID you enter for this configuration. When
uninstalling this configuration or performing other maintenance tasks,
you must select this configuration from a list. In addition, installation
log file names use this ID.
8. Click Next.
TEM displays the New Application Root panel.
9. Verify that the status on all features is valid. If there are any warning messages,
you must resolve them before continuing.
If you see a warning message regarding a feature’s XML file, click the feature
and use the Browse button to locate the XML file. Note that the feature’s XML
file may reside in a location different from the corresponding Business Modeler
IDE project location.
Note If the custom template directory is on a shared network drive, be sure
that you have write permission to the shared path.
When upgrading to Teamcenter 10.1, you may need to download the AutoCAD
and SEECOverlay templates from GTAC and then browse to them on the New
Application Root panel.
11. In the Operating System User panel, enter the valid credentials for the
operating system user and click Next.
TEM displays the Teamcenter Administrative User panel.
12. Enter the Teamcenter user name and password and click Next.
TEM displays the Upgrade Information panel.
13. Enter the paths to the old TC_DATA and new TC_DATA directories. Then, enter
the user name and password for the Teamcenter database.
16. Verify that the features you want to upgrade are displayed and click Next. If all
of the features are not displayed, click Browse to locate them.
TEM displays the Upgrade Options panel.
Note Siemens PLM Software recommends that you select this option only
if you are upgrading a test environment.
21. Enter the path to the directory where the encrypted password files are kept.
24. In the FCC Parents panel, specify settings for the parent FMS server caches
(FSCs) used by the FMS client cache (FCC). FSCs are used in the priority you
specify.
• The FSC assignment mode box specifies how you want to assign FSCs.
• To add an FSC to the list, click Add. TEM adds a row to the table of FSC
values. Double-click the Protocol, Host, Port or Priority boxes to enter
values.
• To modify a value in the table, double-click the box and enter the new value.
• To remove an FSC from the table, select the row and click Delete.
26. In the 2-tier server settings panel, specify values required for the rich client to
access your Teamcenter server. Make sure that the TC_DATA value points to the
TC_DATA directory for your upgraded corporate server. For more information
click the Help button.
31. Select the Business Modeler IDE templates you want to install. To install
additional templates, click Browse and locate the desired templates.
35. Specify a path for new TC_ROOT and TC_DATA directory or choose the default.
TEM displays the Dispatcher Components panel.
36. In the Dispatcher Components panel, specify settings for the Dispatcher
components.
For more information about Dispatcher component settings, see the Dispatcher
Server Installation Guide.
TEM displays the Dispatcher Settings panel.
37. Specify Dispatcher settings, such as debug level, log directory, and how you
want to start the Dispatcher services.
For more information about Dispatcher component settings, see the Dispatcher
Server Installation Guide.
39. Select the translators you want to enable in the Dispatcher Module and click
Next.
TEM displays the Translator Settings panel.
40. In the Translator Settings panel, enter the home path of the translators you
selected on the Select Translators panel and the path to their license files.
42. Specify the Dispatcher client settings on the next two panels.
For more information, see the Dispatcher Server Installation Guide.
44. Specify a directory for storing the diagnostic log files and click Run.
Once completed, you can click Review to see the details of the tests.
46. Review the feature and configuration information and click Start.
TEM begins installing Teamcenter.
If the upgrade is successful, TEM displays the Upgrade Features: Successful
panel.
Note If a problem occurs, TEM displays a message that includes the path to
the log file that describes the problem.
4. Click Upgrade.
5. In the Old Application Root dialog box, browse to the path of the application
directory of the previous installation and click Next.
TEM displays the Old Configuration panel.
8. Click Next.
TEM displays the New Application Root panel.
9. Verify that the status on all features is valid. If there are any warning messages,
you must resolve them before continuing.
If you see a warning message regarding a feature’s XML file, click the feature
and use the Browse button to locate the XML file. Note that the feature’s XML
file may reside in a location different from the corresponding Business Modeler
IDE project location.
12. In the FCC Parents panel, specify settings for the parent FMS server caches
(FSCs) used by the FMS client cache (FCC). FSCs are used in the priority you
specify.
• The FSC assignment mode box specifies how you want to assign FSCs.
• To add an FSC to the list, click Add. TEM adds a row to the table of FSC
values. Double-click the Protocol, Host, Port or Priority boxes to enter
values.
• To modify a value in the table, double-click the box and enter the new value.
• To remove an FSC from the table, select the row and click Delete.
TEM displays the 4-tier server configurations panel if you are upgrading
a four-tier client. TEM displays the 2-tier server settings panel if you are
upgrading a two-tier client.
14. In the 2-tier server settings panel, specify values required for the rich client to
access your Teamcenter server. Make sure that the TC_DATA value points to the
TC_DATA directory for your upgraded corporate server. For more information,
click the Help button.
17. Specify the location for installing Teamcenter Visualization Embedded and the
source of the installation images and click Next.
TEM displays the License Level for Teamcenter Visualization (Embedded)
panel.
Overview
Teamcenter Rapid Start 10.1 is a configuration of Teamcenter with the same
database schema. Teamcenter Rapid Start has the following unique features that
are not available in Teamcenter:
• Smart codes utility
• Server Print
• 4 Tier
• ETS
• Reports
• Queries
• Statuses
• ACL
• Ensure that you have write permission on the default volume of the
administrative user (infodba).
• All customizations done outside the database (for example, portal properties)
must be moved forward manually. All customizations done within the database
are carried over by reusing the same database.
• Before upgrading the client, be sure that the server you plan to connect to has
been upgraded to Teamcenter 10.1.
• If you have custom templates (custom objects), migrate them to the compatible
versions using the steps described in Upgrade a template project to the current
data model format. Note the following:
o Make sure that custom templates have been deployed using TEM.
o Ensure that you have access to the Business Modeler IDE projects of the
custom templates deployed on the server.
o Ensure that you have the latest package templates for all of your Business
Modeler IDE projects. If you have performed any changes since the previous
TEM deployment of the templates, you must redeploy them.
3. In the Maintenance panel, select Uninstall Teamcenter Rapid Start and click
Next.
The Configuration Display panel shows all configurations in the Teamcenter
Rapid Start installation.
5. In the Complete Uninstallation panel, select Remove all files including user
files. Do not select Remove databases (Database, volume and TC_DATA),
since the database, volume, and TC_DATA are required for the Teamcenter
installation. Click Next.
6. In the warning panel that appears, select I want to permanently remove these
items and click OK.
4. Enter a unique description and ID for this software configuration or accept the
defaults.
Note Record the description and ID you enter for this configuration. When
uninstalling this configuration or performing other maintenance tasks,
you must select this configuration from a list. In addition, installation
log file names use this ID.
5. Click Next.
TEM displays the Test Environment Location panel.
7. In the File System Cache Service (FSC) panel, type a unique identifier and port
for the FMS server cache in the FSC ID and Port text boxes.
A Teamcenter network must have at least one master FSC. If you want to
designate the current FSC as an FSC master, select Enable configuration
master. Otherwise, type the URL to the parent FSC in the FSC Parent URL
text box.
For advanced FSC configuration options, click Advanced.
8. Click Next.
TEM displays the Operating System User panel.
11. Enter information for the production database server. Enter the Teamcenter
Rapid Start database name that you want to use for the Teamcenter installation.
TEM displays the Database Configuration panel.
14. Enter the path to the existing Teamcenter Rapid Start 10.1 volume directory
and click Next.
TEM displays the Teamcenter Administrative User panel.
15. Enter the administrative password for the Teamcenter application and click
Next.
TEM displays the Flex License Client panel.
16. Enter the license port number and server name and click Next.
• Uninstall the existing Teamcenter Rapid Start 10.1 client and install a new
Teamcenter 10.1 client.
A Troubleshooting
A Troubleshooting
Use the upgrade log viewer to diagnose and address upgrade failures:
1. In the Pre-Upgrade and Upgrade sections in the top pane, find the description of
a step that failed during the upgrade process.
2. In the Navigate Logs pane, locate the step in the list, with the names of the
logs generated by that step.
4. Review the log contents to find details about the step that failed and the steps
that preceded it.
• GTAC
Provides support resources for all Siemens PLM Software products.
Submit information from the upgrade log viewer about specific upgrade failures
to Siemens PLM Software support on GTAC:
http://support.industrysoftware.automation.siemens.com
Windows systems:
TC_ROOT\install\upgrade_logs\install_upgrade_logs_package-ID.zip
Note To access the upgrade log viewer outside TEM, open the following location in
a Web browser:
Windows systems:
TC_ROOT\install\upgrade_display_results.html
http://java.sun.com/products/plugin/
index.html#download
http://java.com/en/download/help/
enable_browser.jsp
http://java.com/en/download/help/
enable_panel.jsp
Incorrect Internet Explorer browser Ensure that installing on demand is enabled:
setting
Tools→Internet Options→Advanced→
Install on Demand
Tools→Internet Options→Security→
Custom Level→Scripting of Java Applets
Errors when uploading FMS_HOME environment variable Uninstall the rich client as described in Uninstall the rich client.
or downloading files does not point to the location of the Then reinstall the rich client.
File Management System (FMS)
client executables Caution Always uninstall a rich client using this procedure
before installing a new rich client.
Incomplete installation of FMS client
cache executables
Incompatible configurations of FMS If two rich clients are installed on the workstation, report the
errors to the Teamcenter administrator.
When two rich clients are installed on the same workstation, FMS
uses the FMS_HOME value set during the first installation. The
configuration of the file client cache (FCC) to a file server cache
(FSC) must support both deployments, especially if the second
deployment is to a different database.
Teamcenter displays Teamcenter administrator did not Contact the Teamcenter administrator.
an error message when include online help when configuring
you attempt to access your rich client
Teamcenter online help
If you run this utility on a later database, you get the following
error, which you can ignore:
Type IMAN_drawing for Class ImanRelation does not exist
TABLESPACE
_NAME FILE_NAME
SYSTEM D:\ORACLE\ORADATA\SYSTEM01.DBF
UNDOTBS1 D:\ORACLE\ORADATA\UNDOTBS01.DBF
SYSAUX D:\ORACLE\ORADATA\SYSAUX01.DBF
IDATA D:\ORACLE\ORADATA\IDATA01.DBF
ILOG D:\ORACLE\ORADATA\ILOG01.DBF
INDX D:\ORACLE\ORADATA\INDX01.DBF
To help ensure the upgrade is successful, make sure the redo logs
are sized properly (100M each) and reside on a separate disk from
the data. If necessary, resize the redo logs.
2. Log on to Oracle:
sqlplus /nolog
connect system/password as sysdba;
3. Find the list of the redo log groups and see where the files
reside.
SELECT GROUP#,TYPE,STATUS,MEMBER FROM V$LOGFILE;
4. Create the new redo logs as follows. You can change the drive
where you can create these, but redo logs should reside on a
separate disk from the data.
ALTER DATABASE ADD LOGFILE GROUP 4 (’E:\ORACLE\ORADATA\DPVPERF\
REDO04.LOG’) SIZE 100M;
ALTER DATABASE ADD LOGFILE GROUP 5 (’E:\ORACLE\ORADATA\DPVPERF\
REDO05.LOG’) SIZE 100M;
ALTER DATABASE ADD LOGFILE GROUP 6 (’E:\ORACLE\ORADATA\DPVPERF\
REDO06.LOG’) SIZE 100M;
Rich client startup Wait time for hierarchy tree Set the TC_show_checkedout_icon preference to FALSE.
performance is slow checked-out icon display.
Note Users and administrators can set the
TC_show_checkedout_icon preference to
TRUE to enhance usability or to FALSE to enhance
rich client startup performance.
FCC in Engineering Engineering Process Management Configure the Engineering Process Management FCC to use its
Process Management FCC attempting to use JRE from own JRE.
hangs after upgrade to Teamcenter 10.1.
Teamcenter 10.1 Different versions of Teamcenter work with different versions of
Java. For example, Teamcenter engineering process management
2005 SR1 works with Java 1.4, Teamcenter 8.3 works with Java
1.5, and so on.
<FSCMasterSettings guid="guid">
<masterModel value="Simple Model" />
</FSCMasterSettings>
If you manually demoted an FSC to a nonmaster, you must perform the following
steps:
1. Remove the <FSCMasterSettings> section from the <data> section of the
configuration.xml file.
The <masterList> value must be the current FSC’s parent FSC. The (0) at the
end indicates it is a priority 0 connection.
B Glossary
B 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.
ClearCase Integration
Teamcenter integration to the IBM Rational ClearCase software configuration
management tool.
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
managers (Teamcenter File Services and File Management System), and volumes.
For installations that include the Web tier (four-tier architecture), the corporate
server also contains the Teamcenter server manager. Multiple application clients
can map to or mount the corporate server.
distribution server
See rich client distribution server.
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
See File Management System (FMS).
four-tier architecture
Teamcenter architecture that includes four tiers: resource tier, client tier, Web tier,
and enterprise tier.
four-tier deployment
Deployment of the Teamcenter four-tier architecture. The Web tier, enterprise tier,
resource tier, and client tier can each be hosted on the same or separate computers.
FSC
See FMS server cache (FSC).
FSC 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
Siemens PLM Software suite that provides enterprise-wide product visualization
capabilities. Lifecycle Visualization can be configured for use with both the
Teamcenter rich client and thin client as a stand-alone application.
The software suite includes Teamcenter lifecycle visualization base, Teamcenter
lifecycle visualization standard, Teamcenter lifecycle visualization professional, and
Teamcenter lifecycle visualization mockup.
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
Teamcenter rich client application that is the main access point for managing
product information. My Teamcenter provides the functionality for creating objects
in the Teamcenter database, querying the database for objects, checking in and
checking out objects, and managing tasks. Users can also open objects, automatically
launching the related application.
Each user has a personal My Teamcenter window that displays product information
as graphical objects. Although users share product information across the enterprise,
they organize this information individually in personal workspaces.
naming service
Service that maintains a list of names and the objects associated with them. For
the Teamcenter rich client, the naming service maintains a list of servers and the
objects and methods used by those services. The naming service is an integral part
of the server directory.
NS
See naming service.
NX Integration
Integration between Teamcenter and NX. NX Integration users have full access
to the Teamcenter user interface from NX, and they can also access NX from the
Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user
interface in NX. The difference between the two products is the level of Teamcenter
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.
role preference
Teamcenter preference applying to an entire role.
Security Services
Services that eliminate prompts for logon credentials when users switch Teamcenter
products within a user session. Authentication is performed by an external identity
service provider, such as lightweight directory access protocol (LDAP), instead of
the Teamcenter product. At a site that deploys multiple Teamcenter products and
Security Services, users log on once to access all participating Teamcenter products.
server manager
Process that manages a pool of Teamcenter server processes in a deployment of
the four-tier architecture. The server manager starts and times out a configurable
number of server processes to communicate with the Teamcenter database. A
server assigner process assigns available server processes to user sessions. The
server manager communicates with the Web tier application using either TCP or
multicast protocol.
server pool
Pool of Teamcenter server processes running in the enterprise tier. A small
deployment may have only one pool of server processes. For larger deployments, the
pool of server processes is distributed as subpools across multiple hosts, with a
server manager for each subpool. Server pools are applicable for deployments of the
Teamcenter four-tier architecture only.
site
Individual installation of Teamcenter comprising a single Teamcenter database,
all users accessing that database, and additional resources such as hardware,
networking capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site.
site ID
Unique identifier of a Teamcenter site. The site ID is used to generate internal
identifiers for Teamcenter objects that must be unique throughout an enterprise.
Once established, site IDs should not be modified.
site name
Unique name of a Teamcenter site stored in the database as a user-defined character
string.
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.
transient volume
Operating system directory controlled by Teamcenter and used to store temporary
data for transport of reports, PLM XML, and other nonvolume data between the Web
tier and client tier in a deployment of the Teamcenter four-tier architecture.
two-tier architecture
Teamcenter architecture that includes a resource tier and a client tier. The resource
tier comprises the database server and database. The client tier comprises the
Teamcenter rich client, third-party applications that integrate with the rich client,
and a local server. This architecture supports only the Teamcenter rich client.
two-tier deployment
Deployment of the Teamcenter two-tier architecture. In a typical deployment of the
two-tier architecture, the rich client and its local server are installed on a user’s
workstation as are third-party applications that integrate with the rich client. The
database server and the Teamcenter corporate server are installed on one or more
separate computers.
user preference
Teamcenter preference applying to a specific user.
visualization
Ability to display a realistic, real time, graphical visualization of geometric data.
volume
Operating system directory controlled by Teamcenter and used to store the files
managed by Teamcenter. When a user performs an action that causes Teamcenter
to create a file, the file is created in the Teamcenter volume. Users cannot directly
access the files in Teamcenter volumes; they must do so via a Teamcenter session.
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.
C F
Certification database . . . . . . . . . . . . . . 1-2 FMS_HOME environment variable . . . . A-3
Character set, ISO8859–1 . . . . . . . . . . . 3-3 Four-tier architecture
Character sets Troubleshooting . . . . . . . . . . . . . . . . A-3
ISO8859-1 . . . . . . . . . . . . . . . . . . . . . 1-5 FSC master diagnostic failure
UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Troubleshooting . . . . . . . . . . . . . . . . A-6
Chinese characters in Windows . . . . . . . 1-4 FSC upgrade . . . . . . . . . . . . . . . . . . . 3-17
Composite host ID . . . . . . . . . . . . . . . . . 2-1 FUNCTION relation . . . . . . . . . . . . . . 3-24
Custom reports . . . . . . . . . . . . . . . . . . 3-24
ATTRIBUTE or REFBY relations
selectors . . . . . . . . . . . . . . . . . . . 3-25 G
opt_fast_traversal option . . . . . . . . . 3-25 getcid utility . . . . . . . . . . . . . . . . . . . . . 2-1
process_definition run-time
property . . . . . . . . . . . . . . . . . . . 3-25
H
Property value evaluation . . . . . . . . . 3-25
PROPERTY, FUNCTION, OCCTYPE Hewlett-Packard HP-UX platforms
relations . . . . . . . . . . . . . . . . . . . 3-25 System requirements . . . . . . . . . . . . . 1-2
Related property or Object run-time Hewlett-Packard HP-UX platforms
properties . . . . . . . . . . . . . . . . . . 3-25 Platform support . . . . . . . . . . . . . . . . 1-2
Wildcard characters . . . . . . . . . . . . . 3-25 Hewlett-Packard HP-UX, Java
configuration . . . . . . . . . . . . . . . . . . . . 1-4
D HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Kernel parameter requirements . . . . . 2-6
Database size issues . . . . . . . . . . . . . . A-5 HP-UX platforms
Databases Platform support . . . . . . . . . . . . . . . . 1-2