TC 8 Release Bulletin

Teamcenter 8
Release Bulletin
Publication Number
PLM00001 C
Proprietary and restricted rights notice
This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2009 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
All trademarks belong to their respective holders.
2 Teamcenter 8 Release Bulletin PLM00001 C

Contents
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Teamcenter and compatible third-party software versions . . . . . . . . . . . . . . . 1-2
Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Available Teamcenter 8 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-4
Support announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
What’s new for Teamcenter 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

New Teamcenter applications and solutions . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Teamcenter documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Installing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Configuring Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Using Teamcenter interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Classifying data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Managing documents, reports, requirements, and schedules . . . . . . . . . . . . . . 2-38
Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Managing Mechatronics data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Visualizing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Managing CAE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
Managing Maintenance, Repair, and Overhaul data . . . . . . . . . . . . . . . . . . . . 2-61
Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Teamcenter industry solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
Performing integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73
Managing translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
Teamcenter 8 release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Teamcenter 8 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Teamcenter 8 documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Carried forward release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Release notes carried forward from Teamcenter 2007 . . . . . . . . . . . . . . . . . . . 4-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
PLM00001 C Teamcenter 8 Release Bulletin 3

Chapter
1 Before you begin
Teamcenter and compatible third-party software versions . . . . . . . . . . . . . . . 1-2
Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Available Teamcenter 8 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-4
Support announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Deprecated ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Deprecated utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Deprecated services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Deprecated Java classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Obsolete ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Obsolete utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
Obsolete preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
Obsolete environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
Obsolete Java classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
PLM00001 C Teamcenter 8 Release Bulletin

Chapter
1 Before you begin
For more information about installing this version of Teamcenter, see the following:
• If you are installing Teamcenter for the first time, see the Installation on UNIX
and Linux Servers Guide or Installation on Windows Servers Guide.
• If you are upgrading from Engineering Process Management or Teamcenter

2007, see the Upgrade Guide.
• Maintenance pack and patch installation information is in the Installation on

UNIX and Linux Servers Guide and the Installation on Windows Servers Guide.
If you are installing a maintenance pack on to an existing installation, see the
Installing Teamcenter maintenance packs topic, or if you are installing a patch
on to an existing installation, see the Installing Teamcenter patches topic.
Note that you can create a new installation of Teamcenter from a maintenance
pack version. If you do so, see either the first-time installation instructions or
the upgrading instructions, whichever is appropriate for your situation.
• For general guidelines and best practices for a Teamcenter system administrator
to follow when deploying a new or upgrading an existing Teamcenter system, see
the Teamcenter Deployment Guide. To obtain a copy, go to the following Web site:
http://support.ugs.com/docs/teamcenter/
Note
You must have a WebKey to access the Web site.
To learn about new and updated functionality in Teamcenter, see What’s new for
Teamcenter 8. This topic also appears in the online help collection.
To review notes about known software problems and their workarounds, see
Teamcenter 8 release notes and Carried forward release notes.
To review notes about corrections or additions to the published documentation, see
Teamcenter 8 documentation release notes.
PLM00001 C Teamcenter 8 Release Bulletin 1-1

Chapter 1 Before you begin
Teamcenter and compatible third-party software versions

The Siemens PLM Software Certification Database
(http://support.ugs.com/online_library/certification/) documents the minimum
version of operating systems, compilers, databases, client browsers, and other
third-party software with which this product is compatible. Because Teamcenter
releases are asynchronous with the release of compatible third-party software,
Teamcenter customers can acquire and install a newer version of third-party
software before Siemens PLM Software has the opportunity to certify it.
Siemens PLM Software’s standard policy with respect to new versions of operating
systems, compilers, databases, client browsers, and other third-party software relies
on the manufacturers’ guarantees. If the manufacturer guarantees that the new
version of its product is binary-compatible with the preceding version, Siemens
PLM Software expects our products to function properly when running on the new
version. Our experience shows that virtually no problems are encountered when
executing Teamcenter with a third-party version later than the version on which
we completed our certification testing.
Siemens PLM Software will make a reasonable effort to support Teamcenter running
on a later version and to work with you to resolve any difficulty that may arise but
will not, in most cases, complete the testing required to state Teamcenter software is
certified.
Teamcenter compatibility with operating systems and compilers involves these
two considerations:
• Compatibility for runtime.
• Compatibility for relinking customizations and paths.
Typically, operating system manufacturers assure run time binary compatibility

between the successive versions of their operating systems. We make a reasonable
effort to support Teamcenter running on a later version of an operating system. To
a lesser degree, operating system manufacturers provide similar assurances when
relinking or rebuilding executables and libraries with new versions of the compilers.
In cases where compatibility does not exist between old and new compiler versions,
all customization incorporated into the Teamcenter base product must be linked
using the version of the compiler with which Teamcenter has been released. This
also applies to the installation of Teamcenter patches.
To summarize, Teamcenter may run on a newer version of an operating system, but
customizations and patches may need to be compiled and linked on an earlier version.
For information about the lowest version of software with which this product runs,
see the Siemens PLM Software Certification Database. Although Teamcenter may
run using a lower level of software, keep in mind that we strongly discourage
running at lower levels and that we do not provide support to anyone doing so.
Note
If Siemens PLM Software discovers incompatible versions of third-party
software, we will post bulletins on GTAC. This information is also available
from your Teamcenter provider.
1-2 Teamcenter 8 Release Bulletin PLM00001 C

Before you begin
Global Technical Access Center (GTAC)

GTAC is the vehicle for Teamcenter communication. It provides a single repository
of current, accurate, version-controlled Teamcenter information that is accessible
through the Internet by authorized users. Maintained within GTAC is a wealth of
information for the diverse mix of customers and employees in the Teamcenter
community.
Information in GTAC includes, but is not limited to, the following:
• Support announcements and bulletins
• Frequently asked questions
• Product defect reports
• Enhancement requests
• Patches and technical documentation
• Shareware customizations
• Tips pertaining to Teamcenter customization, performance, and administration
• Product information, customer success stories, and user conference presentations
GTAC can be accessed from the Siemens PLM Software Web site or directly through
its Web server at the following Web site:
http://support.ugs.com
You must have a WebKey account to access GTAC. A customer WebKey account is a
single point of authentication that allows customers to access product information
and associated support tools. WebKey accounts are strictly limited to Siemens PLM
Software employees and to people or companies who belong to the Teamcenter
community through contractual agreements with Siemens PLM Software pertaining
to Teamcenter. Requests for access to GTAC using a WebKey account can be directed
to the following Web site:
https://plmapps.ugs.com/webkey/

Available Teamcenter 8 platforms

The following distribution images are available as part of Teamcenter 8:
Teamcenter 8 for HP Risc

Teamcenter 8 for HP Itanium
Teamcenter 8 for IBM AIX
Teamcenter 8 for Sun Solaris Sparc
Teamcenter 8 for Microsoft Windows
Teamcenter 8 for Linux SUSE 64
Teamcenter 8 for Over-the-Web installation, All Platforms
Teamcenter 8 Embedded Visualization, All Platforms
Teamcenter 8 Publications, All Platforms
Teamcenter 8 is supported in the following locales on all server-supported platforms:
Chinese Simplified
Chinese Traditional
Czech
English
French
German
Hebrew
Italian
Japanese
Korean
Russian
Spanish
Hardware, software, and disk space requirements

For information about system hardware and software requirements for Teamcenter
8, see the Siemens PLM Software Certification Database:
http://support.ugs.com/online_library/certification/
The following table shows the required disk space for the platforms supported by
Teamcenter.
Corporate Two-tier rich

Platform server client Web tier
Hewlett-Packard 3.0 GB Not supported 3.0 GB
HP-UX (Itanium)
Hewlett-Packard 3.0 GB Not supported 3.0 GB
HP-UX
IBM AIX 2.0 GB 450 MB 3.0 GB
SUSE Linux 2.0 GB 300 MB 3.0 GB
Sun Solaris 2.5 GB 300 MB 3.0 GB
Microsoft Windows 1.5 GB 450 MB 4.5 GB

Before you begin
Support announcements
As Siemens PLM Software enhances Teamcenter, some features are deprecated or
obsoleted. Deprecation identifies items that will be removed in a future version of
Teamcenter. Obsolescence identifies items that are either removed from Teamcenter
or may be removed without further notice.
Deprecated feature announcements

The following will be no longer supported in a future version of Teamcenter:
• Deprecation of support for SUSE Linux Enterprise Server (SLES) 9.0
(First published Teamcenter 8)
Support for version 9.0 of SUSE Linux Enterprise Server (SLES) will discontinue
at Teamcenter 8.1. Teamcenter will support only version 10 SP2 and higher for
both clients and servers starting with Teamcenter 8.1.
For a listing of supported platforms for Teamcenter, see the certification table
at the following URL:
• Deprecation of support for AIX 32-bit servers and clients

Teamcenter will support only 64-bit servers and clients on the AIX operating
system starting with Teamcenter 8.1. For a listing of supported platforms for
Teamcenter, see the certification table at the following URL:
• Deprecation of the Global Services Teamcenter 2007 Rich Client

Connector
The Teamcenter 8 Global Services – Teamcenter 2007 Rich Client Connector is
deprecated. This connector will be removed in a future release of Global Services.
In most cases, you can use the Teamcenter 8 Global Services – Teamcenter 8
SOA connector in place of this connector.
• Deprecation of the Global Services Teamcenter Engineering 2005/2007

Connector
The Teamcenter 8 Global Services – Teamcenter Engineering 2005/2007
Connector is deprecated. This connector will be removed when Teamcenter
Engineering 2007 is no longer supported.
• Deprecation of the Global Services Teamcenter Engineering v9

Connector

The Teamcenter 8 Global Services – Teamcenter Engineering v9 Connector is

deprecated. This connector will be removed when Teamcenter Engineering V9
is no longer supported.
• Deprecation of the Global Services Teamcenter 8 Connector

The Teamcenter 8 Global Services – Teamcenter 8 Connector is deprecated. This
connector will be removed in a future release of Global Services.
• Deprecation of the Global Services SAP Connector

The Teamcenter 8 Global Services – SAP Connector is deprecated. This
connector will be removed in a future release of Global Services.
• Deprecation of support for Excel 2003

Teamcenter Extensions for Microsoft Office will not support Excel 2003
beginning at Teamcenter 8.1.
• Deprecation of TraceLink class

The TraceLink class is deprecated and will be removed in Teamcenter 9.0. It
was originally defined under the ManagedRelations class in Teamcenter 2007.
The trace link functionality is now migrated to the FND_TraceLink class under
the IMAN_Relation class. Users should use the FND_TraceLink class for all
customization and queries for trace link.
• Deprecation of JT assembly format for import and export

Export and import of a JT assembly format using PLM XML is deprecated and
will be removed after Teamcenter 8.1. Instead, use the PLM XML format rather
than the JT assembly format. This will export and import JT files, along with
the PLM XML file containing the item information and assembly relationships.
• Deprecation of Report Designer

(First published Teamcenter 2007.1.5)
Siemens PLM Software announces the deprecation of the Report Designer
application. Report Designer will still be supported in Teamcenter 8, however,
support will be dropped in a future version. Customers are encouraged to use
the Report Builder application to develop reports in the future.
For more information about Report Builder, see the Report Builder Guide.
• Deprecation of the Image Import utility

Siemens PLM Software announces the deprecation of the Image Import utility.
Support will be dropped in Teamcenter 8.1. The Image Import utility is located
on the Teamcenter installation CD-ROM in the additional_applications folder.

Before you begin
• Deprecation of support for the Hewlett-Packard HP-UX operating

system on PA-RISC hardware
(First published Teamcenter 2007.1)
Support for the HP-UX operating system on PA-RISC hardware is deprecated.
This includes all clients and servers. Hewlett-Packard announced the
deprecation of HP-UX on the PA-RISC hardware platform and is moving server
implementations to the HP-UX Integrity platform based on the Intel Itanium2
platform. More information about HP-UX PA-RISC deprecation is available on
the Hewlett-Packard Web site:
http://h71028.www7.hp.com/ERC/downloads/4AA0-5390ENW.pdf
Support for the HP-UX PA-RISC rich client is discontinued at Teamcenter 8.
Support for HP-UX PA-RISC servers will be discontinued at Teamcenter 9.
The HP-UX Integrity platform is supported for Teamcenter 8 servers. See the
following site for specific operating system version support and restrictions:
• Deprecation of rich client on UNIX-based operating systems

The Teamcenter rich client is deprecated for these operating systems:
– HP-UX on PA-RISC hardware
– Sun Solaris
– IBM AIX
Demand has decreased for Teamcenter clients on UNIX-based operating

systems. UNIX hardware vendors now concentrate on servers instead of
desktops. Support for the HP-UX PA-RISC rich client is discontinued with
Teamcenter 8 and support for the Solaris and AIX rich client will be discontinued
with Teamcenter 9. This change is a result of issues with third-party software
dependencies on the HP-UX PA-RISC platform.
Only the Teamcenter rich client on UNIX systems is deprecated. The Teamcenter
thin client, Teamcenter embedded clients (for example, Integration for CATIA),
or Teamcenter server-side components on UNIX will still be supported.
Siemens PLM Software recommends using either Windows-based or SUSE
Linux-based systems for Teamcenter rich client.
See the following site for specific operating system version support:
• Deprecation of Application Interface Web Service (AIWS)

The Teamcenter Application Interface Web Service is deprecated and will be
discontinued at Teamcenter 9. Use service-oriented architecture (SOA) to
develop new clients instead of AIWS. For more information about SOA, see the
Services Guide.

• Deprecation of Over-the-Web Installer

The Teamcenter Over-the-Web Installer and its distribution server is deprecated.
In a future version, you will be able to install the four-tier rich client using either
Teamcenter Environment Manager or by using push install technology, such as
Microsoft Systems Management Server (SMS).
On the Windows platform, a new, more firewall friendly pull mechanism will be
introduced before the Teamcenter Over-the-Web Installer is removed.
• Deprecation of Teamcenter EMC Content Storage media type

Support for the EMC-based Content Storage media type is no longer included
in Teamcenter. Backup and recovery functionality remains as a supported
capability in Teamcenter but without support for the EMC Content Storage
media type.
The following features are impacted:
– Content Storage media type in the rich client
– Content Storage media type usage in Backup/Recovery applications

(object_backup and object_recover utilities)
– Content Storage type usage in audit logging
– EMC Business Modeler user exits
– Content Storage type integration code in the

ar_content_storage_media_api.c and ar_content_storage_media.h
files
• Deprecation of schematics in Structure Manager

The ability to view schematic diagrams in the Structure Manager viewer is
deprecated. Replacement of this functionality is targeted in a future release
based on an integration with Microsoft Visio and Teamcenter.

Before you begin
Deprecated ITK functions

The following ITK functions are deprecated in Teamcenter 8.
Deprecated function Replacement function

HRN_ask_wire_protection_segment HRN_ask_wire_protection_segments
HRN_set_wire_protection_segment HRN_set_wire_protection_segments
HRN_unset_wire_protection_segment HRN_unset_wire_protection_segments
IMF_replace_file IMF_replace_file_and_get_new_tag
REQ_export_to_application REQ_export_to_excel
For more information about the replacement functions, see the Integration Toolkit
Function Reference.

Deprecated utilities
Teamcenter command line utilities are used by administrators to manage

Teamcenter installations. For more information about utilities, see the Utilities
Reference.
The following utilities are deprecated in Teamcenter 8.
• Deprecation of the object_backup and object_recover utilities
Siemens PLM Software announces the deprecation of the object_backup and
object_recover utilities. These utilities will be removed in Teamcenter 8.1.
They are no longer necessary because of the Hot Backup over FMS feature.
• Deprecation of the import_dfa_file utility

The import_dfa_file utility will be obsolete in Teamcenter 9. The
import_dfa_file utility corrupts data model objects managed by the Business
Modeler IDE. If you use this utility, you may corrupt the data model and the data
may become inaccurate. Use the Business Modeler IDE to create and manage
the objects that were previously managed by this utility.

Before you begin
Deprecated services
Teamcenter Services are a collection of Teamcenter operations used by system
administrators to connect their company’s applications to Teamcenter. For libraries
and documentation (which includes the list of deprecated services), see the
soa_client.zip file on the Teamcenter software distribution image. The services
documentation is also presented as the Services Reference in the Teamcenter HTML
Collection.
The following services are deprecated:
• CalendarManagement
– Teamcenter::Services::Calendarmanagement::_2007_01::
Calendarmanagement::
createTCCalendars (const std::vector< NewTCCalendar >
&newTCCalendars)=0
– Teamcenter::Services::Calendarmanagement::
CalendarmanagementService::
createTCCalendars (const std::vector< NewTCCalendar >
&newTCCalendars)=0
– Teamcenter::Services::Calendarmanagement::_2007_01::
Calendarmanagement::
updateTCCalendars (const std::vector< TCCalendarUpdate >
&tccalendarUpdates)=0
– Teamcenter::Services::Calendarmanagement::
CalendarmanagementService::
updateTCCalendars (const std::vector< TCCalendarUpdate >
&tccalendarUpdates)=0
• Core
– Teamcenter::Services::Core::_2007_06::Lov::
getAttachedLOVs (const std::vector< LOVInfo > &inputs)=0
Deprecated as of Teamcenter 2007; replaced with getAttachedPropDescs
in the Core library.
– Teamcenter::Services::Core::LovService::
getAttachedLOVs (const std::vector< LOVInfo > &inputs)=0
Deprecated as of Teamcenter 2007; replaced with getAttachedPropDescs
in the Core library.
– Teamcenter::Services::Core::_2006_03::Session::
getPreferences (const std::string &prefScope, const std::vector<
std::string > &prefNames)=0
Deprecated as of Teamcenter 2007; replaced with getPreferences from
session0701.
– Teamcenter::Services::Core::SessionService::
getPreferences (const std::string &prefScope, const std::vector<
std::string > &prefNames)=0

Deprecated as of Teamcenter 2007; replaced with getPreferences from

session0701.
login (const std::string &username, const std::string &password,
const std::string &group, const std::string &role, const std::string
&sessionDiscriminator)=0
Deprecated as of Teamcenter 8. Use the 2008_06::Session::login operation
instead.
login (const std::string &username, const std::string &password,
const std::string &group, const std::string &role, const std::string
&sessionDiscriminator)=0
Deprecated as of Teamcenter 8. Use the 2008_06::Session::login operation
instead.
loginSSO (const std::string &username, const std::string
&ssoCredentials, const std::string &group, const std::string &role,
const std::string &sessionDiscriminator)=0
Deprecated as of Teamcenter 8. Use the 2008_06::Session::loginSSO
operation instead.
loginSSO (const std::string &username, const std::string
&ssoCredentials, const std::string &group, const std::string &role,
const std::string &sessionDiscriminator)=0
Deprecated as of Teamcenter 8. Use the 2008_06::Session::loginSSO
operation instead.
• DataManagement
– Teamcenter::Services::Cad::_2007_01::Datamanagement::
createOrUpdateParts (const std::vector<
Teamcenter::Services::Cad::_2007_01::Datamanagement::PartInfo >
&info)=0
See createOrUpdateParts from datamanagement0712 in the CAD
library.
– Teamcenter::Services::Cad::DatamanagementService::
createOrUpdateParts (const std::vector<
Teamcenter::Services::Cad::_2007_01::Datamanagement::PartInfo >
&info)=0
See createOrUpdateParts from datamanagement0712 in the CAD
library.
– Teamcenter::Services::Cad::_2007_01::Datamanagement::
getAvailableTypes (const std::vector< std::string > &classes)=0
Deprecated as of Teamcenter 2007; see getAvailableTypes from
datamanagement0706 in the Core library.

Before you begin
– Teamcenter::Services::Cad::DatamanagementService::
getAvailableTypes (const std::vector< std::string > &classes)=0
Deprecated as of Teamcenter 2007; see getAvailableTypes from
datamanagement0706 in the Core library.
• ProductionManagement
– Teamcenter::Services::Productionmanagement::_2007_06::
Engineeringdataquery::
getEngineeringDataFromRoutine (const std::vector<
Teamcenter::Services::Productionmanagement::_2007_06::
Engineeringdataquery::RoutineIdVer > &routineIdVer)=0
getEngineeringDataFromRoutine is deprecated in Teamcenter 2007 SR1
MP2 and will be supported for two more releases only. This operation is
replaced with getEngineeringDataFromRoutine2.
– Teamcenter::Services::Productionmanagement::
EngineeringdataqueryService::
getEngineeringDataFromRoutine (const std::vector<
Engineeringdataquery::RoutineIdVer > &routineIdVer)=0
getEngineeringDataFromRoutine is deprecated in Teamcenter 2007 SR1
MP2 and will be supported for two more releases only. This operation is
getEngineeringDataFromRoutine2 (const std::vector<
Engineeringdataquery::RoutineIdVer2 > &routineIdVer)=0
getEngineeringDataFromRoutine2 is deprecated in Teamcenter 2007
SR1 MP3 and will be supported for two more releases only. This operation is
getEngineeringDataFromRoutine2 (const std::vector<
Engineeringdataquery::RoutineIdVer2 > &routineIdVer)=0
getEngineeringDataFromRoutine2 is deprecated in Teamcenter 2007
getFeatureAttributeDataOfCluster (const std::vector<
Engineeringdataquery::ClusterIdentifier > &clusterIdentifier)=0
getFeatureAttributeDataOfCluster is deprecated in Teamcenter 2007
replaced with getFeatureAttributeDataOfCluster2.

getFeatureAttributeDataOfCluster (const std::vector<
Engineeringdataquery::ClusterIdentifier > &clusterIdentifier)=0
getFeatureAttributeDataOfCluster is deprecated in Teamcenter 2007
replaced with getFeatureAttributeDataOfCluster2.
• ProjectManagement
– Teamcenter::Services::Projectmanagement::_2007_01::
Schedulemanagement::
copySchedules (const std::vector< ScheduleCopyContainer >
&scheduleCopyContainer)=0
Deprecated as of Teamcenter 2007; replaced with copySchedules from
schedulemanagement0706.
– Teamcenter::Services::Projectmanagement::
SchedulemanagementService::
copySchedules (const std::vector< ScheduleCopyContainer >
&scheduleCopyContainer)=0
Deprecated as of Teamcenter 2007; replaced with copySchedules from
schedulemanagement0706.
• Query
– Teamcenter::Services::Query::SavedqueryService::
executeSavedQuery (Teamcenter::Soa::Client::Model::ImanQuery
*query, const std::vector< std::string > &entries, const std::vector<
std::string > &values, int limit)=0
Deprecated as of Teamcenter 2007; replaced with executeSavedQueries
from savedquery0706.
– Teamcenter::Services::Query::_2006_03::Savedquery::
executeSavedQuery (Teamcenter::Soa::Client::Model::ImanQuery
*query, const std::vector< std::string > &entries, const std::vector<
std::string > &values, int limit)=0.
Deprecated as of Teamcenter 2007; replaced with executeSavedQueries
retrieveQueryCriterias (const std::vector< std::string >
&queryCriteriaNames)=0
Deprecated as of Teamcenter 2007; replaced with retrieveSearchCriteria
retrieveQueryCriterias (const std::vector< std::string >
&queryCriteriaNames)=0
Deprecated as of Teamcenter 2007; replaced with retrieveSearchCriteria

Before you begin
saveQueryCriterias (const std::vector< SaveQueryCriteriaInfo >
&queryCriterias)=0
Deprecated as of Teamcenter 2007; replaced with saveSearchCriteria
saveQueryCriterias (const std::vector< SaveQueryCriteriaInfo >
&queryCriterias)=0
Deprecated as of Teamcenter 2007; replaced with saveSearchCriteria
• Reports
– Teamcenter::Services::Reports::CrfreportsService::
getReportDefinitions (const std::vector<
Teamcenter::Services::Reports::_2007_01::Crfreports::ReportsCriteria
> &inputCriteria)=0
Deprecated as of Teamcenter 8, see getReportDefinitions from
crfreports0806 in the Reports library.
– Teamcenter::Services::Reports::_2007_01::Crfreports::
getReportDefinitions (const std::vector<
Teamcenter::Services::Reports::_2007_01::Crfreports::ReportsCriteria
> &inputCriteria)=0
Deprecated as of Teamcenter 8, see getReportDefinitions from
crfreports0806 in Reports library.
• ServiceData
– Teamcenter::Soa::Server::ServiceData::
addUpdatedObject (const BusinessObjectRef<
Teamcenter::BusinessObject > obj)
Use the addUpdatedObject( obj, propNames ) method to specify the
exact properties that have been updated.
– Teamcenter::Soa::Server::ServiceData::
addUpdatedObjects (const std::vector< BusinessObjectRef<
Teamcenter::BusinessObject > > &objs)
Use the addUpdatedObject( obj, propNames ) method to specify the
exact properties that have been updated.
• StructureManagement
– Teamcenter::Services::Cad::_2007_01::Structuremanagement::
createOrUpdateAbsoluteStructure (const std::vector<
Teamcenter::Services::Cad::_2007_01::Structuremanagement::
CreateOrUpdateAbsoluteStructureInfo > &info, const
std::string &bomViewTypeName, bool complete, const
CreateOrUpdateAbsoluteStructurePref &pref)=0

See createOrUpdateAbsoluteStructure from

structuremanagement0712 in the CAD library.
– Teamcenter::Services::Cad::StructuremanagementService::
createOrUpdateAbsoluteStructure (const std::vector<
CreateOrUpdateAbsoluteStructureInfo > &info, const
CreateOrUpdateAbsoluteStructurePref &pref)=0
See createOrUpdateAbsoluteStructure from
createOrUpdateRelativeStructure (const std::vector<
CreateOrUpdateRelativeStructureInfo > &inputs, const
CreateOrUpdateRelativeStructurePref &pref)=0
See createOrUpdateRelativeStructure from
createOrUpdateRelativeStructure (const std::vector<
CreateOrUpdateRelativeStructureInfo > &inputs, const
CreateOrUpdateRelativeStructurePref &pref)=0
See createOrUpdateRelativeStructure from
createOrUpdateVariantConditions (const std::vector<
CreateOrUpdateVariantCondInput > &inputObjects)=0
Deprecated as of Teamcenter 2007 SR1 MP1. See
createOrUpdateVariantConditions2.
createOrUpdateVariantConditions (const std::vector<
CreateOrUpdateVariantCondInput > &inputObjects)=0
Deprecated as of Teamcenter 2007 SR1 MP1, see
createOrUpdateVariantConditions2.
deleteAssemblyArrangements (const std::vector<
DeleteAssemblyArrangementsInfo > &info, const std::string
&bomViewTypeName)=0

Before you begin
See deleteAssemblyArrangements from structuremanagement0712 in

the CAD library.
deleteAssemblyArrangements (const std::vector<
DeleteAssemblyArrangementsInfo > &info, const std::string
&bomViewTypeName)=0
See deleteAssemblyArrangements from structuremanagement0712 in
the CAD library.
deleteRelativeStructure (const std::vector<
DeleteRelativeStructureInfo > &inputs,
const std::string &bomViewTypeName, const
Teamcenter::Services::Cad::_2007_01::Structuremanagement::D
eleteRelativeStructurePref &pref)=0
See deleteRelativeStructure from structuremanagement0712 in the
CAD library.
deleteRelativeStructure (const std::vector<
DeleteRelativeStructureInfo > &inputs,
const std::string &bomViewTypeName, const
DeleteRelativeStructurePref &pref)=0
See deleteRelativeStructure from structuremanagement0712 in the
CAD library.
• TranslationManagement
– Teamcenter::Services::Translation::_2007_06::Translationmanagement::
createTranslationRequest (const std::vector<
Teamcenter::Services::Translation::_2007_06::Translationmanagement::
CreateTranslationRequestArgs > &inputs)=0
This method is deprecated and replaced with a similar method in
Core::DispatcherManagement using the DispatcherRequest object and
no longer using the ETSTranslationRequest object.
– Teamcenter::Services::Translation::TranslationmanagementService::
createTranslationRequest (const std::vector<
Teamcenter::Services::Translation::_2007_06::Translationmanagement::
CreateTranslationRequestArgs > &inputs)=0
This method is deprecated and replaced with a similar method in
Core::DispatcherManagement using the DispatcherRequest object and
no longer using the ETSTranslationRequest object.

Deprecated Java classes
The following Java classes are deprecated in Teamcenter 8.
Deprecated class Replacement class

AbstractTCApplicationMenuBarNone.
AbstractTCApplicationToolBar None.
AIFUIApplicationMenuBar None.
iTextField TCText
iTextArea TCText (configured to work as text area)
iComboBox TCComboBox
LOVUIComponent TCLOVUIComponent
LOVComboBox TCLOVComboBox
LOVPopupButton TCLOVPopupButton
PropertySet None.

Before you begin
Obsolete feature announcements

The following are no longer supported in Teamcenter:
• The AutoCopyRel and AutoRevise business object constants are now
obsolete
In Teamcenter 2007.1, the AutoCopyRel and AutoRevise business object
constants were introduced to support the requirement to automatically revise
and relate the related object during a Revise operation of an ItemRevision
business object. These two constants are now obsolete.
Beginning in Teamcenter 8, do not use the AutoCopyRel and AutoRevise
business object constants. The functionality provided by these two business
object constants are replaced by deep copy rules. In Teamcenter 8 the deep copy
rules are enhanced to support this behavior using the Relate To Latest and
Revise and Relate to Latest actions.
Keep in mind the following upgrade considerations:
– Upgrading from Engineering Process Management to Teamcenter 8
If you are upgrading from Engineering Process Management to Teamcenter
8, you do not have to do anything, since these constants were available only
in Teamcenter 2007.1.
– Upgrading from Teamcenter 2007.1 to Teamcenter 8

If you are upgrading from Teamcenter 2007.1 to Teamcenter 8, you may have
constant attachments for the AutoCopyRel and AutoRevise business
object constants. Per the new upgrade process, the customer template project
must first be upgraded in the Business Modeler IDE client before upgrading
the database. During upgrade of the customer template project in the
Business Modeler IDE client, migration utilities are written to automatically
handle converting the AutoCopyRel and AutoRevise constants to deep
copy rules. After upgrading the customer template project, the same
template is packaged and supplied during database upgrade. The database
upgrade process ensures that your AutoCopyRel and AutoRevise business
objects constants are correctly converted to deep copy rules. Therefore, the
customer upgrading from Teamcenter 2007.1 to Teamcenter 8 does not have
any other manual steps to perform. By following the standard Teamcenter
upgrade process, the system ensures that your current behavior supported
by the business objects continues to be supported by deep copy rules after
upgrade of your template and database.
For more information, see the Business Modeler IDE Guide.

For a list of other obsolete preferences, see Obsolete preferences.
• Maturity_Level preferences are obsolete

All preferences of the item-revision-business-objectMaturity_Level format (such
as DesignRevision_Maturity_Level) are replaced by the MaturityStatuses
business object constant.

In Teamcenter 2007.1, the item-revision-business-objectMaturity_Level

preference was introduced to configure maturity status for ItemRevision
objects. This preference is obsolete in Teamcenter 8 and is replaced by the
MaturityStatuses business object constant.
The capability to configure the determination of the maturity status of
an ItemRevision object is supported through the MaturityStatuses
business object constant in the Business Modeler IDE instead of the
item-revision-business-objectMaturity_Level preference.
Keep in mind the following upgrade considerations:
– Upgrading from Engineering Process Management to Teamcenter 8
No action is required because the
item-revision-business-objectMaturity_Level preference was introduced
only in Teamcenter 2007.1.
– Upgrading from Teamcenter 2007.1 to Teamcenter 8

Migration utilities are written to convert the
item-revision-business-objectMaturity_Level preferences to
MaturityStatuses business object constant attachments. If you have
preferences that use the item-revision-business-objectMaturity_Level
format, you must follow the steps to migrate these preferences as described
in the Migrate preferences to data model objects topic in the Business
Modeler IDE Guide.
As part of the steps performed prior to the upgrade process, you would
extract the preferences from your database and perform migration in
the Business Modeler IDE using the Preferences Migration wizard. After
the preference migration in the Business Modeler IDE, a file named
cleanup_preferences.txt is generated. This file must be invoked from your
custom upgrade script to remove the preferences from your database.

For a list of other obsolete preferences, see Obsolete preferences.
• Data Integration Services (DIS) Adapter

The Data Integration Services Adapter (DIS Adapter) has been completely
removed from Teamcenter. Teamcenter’s integration with the Lifecycle
Visualization viewers is now based upon a service-oriented architecture (SOA).
This new integration is installed automatically with Teamcenter and no
additional steps are required to work with visualization data in the Teamcenter
8 managed environment.
Lifecycle Visualization viewers from earlier releases are not supported by and
cannot communicate with Teamcenter 8. However, the Teamcenter 8 stand-alone
viewers can communicate with DIS-enabled servers from previous Teamcenter
releases.

Before you begin
• Obsolete Web tier context parameters

The following Web tier context parameters are obsolete in Teamcenter 8:
AdapterAdministrator
EnableAutoSaveLocation
FileUploadDirectory
JtCache.BatchPopulate
JtCache.BatchPopulateFirstTime
JtCache.BatchPopulateIntervalHours
JtCache.Limited.BackupIntervalMinutes
JtCache.Limited.CapacityMB
JtCache.Limited.CleanFirstTime
JtCache.Limited.CleanIntervalHours
JtCache.Limited.Enable
JtCache.Limited.Path
JtCache.Limited.SisterStatusNameList
JtCache.Limited.SisterSynchInterval
JtCache.Limited.StatusName
JtCache.Populator.BackupIntervalMinutes
JtCache.Populator.Path
JtCache.Populator.QueueName
JtCache.World.BackupIntervalMinutes
JtCache.World.CapacityMB
JtCache.World.CleanFirstTime
JtCache.World.CleanIntervalHours
JtCache.World.Enable
JtCache.World.Path
JtCache.World.PopulatorUser
JtCache.World.SisterStatusNameList
JtCache.World.SisterSynchInterval
JtCache.World.StatusName
Mask.RefSetNames.ItemRev
PasswordFile
SessionPurgeFrequency
SessionTimeout
TcEngExcludeFiles
TcEngExcludeFilesExtFromSave
TcEngExcludeObjectTypes
TcEngExcludeTypesFromSave
TcEngMetaDataStamp
TcEngProperties
VVI.DirectModel.Document
VVI.ImageView.Document
VVI.PDFView.Document
VVI.TempFolder
VVI.Vis3DLayer
VVI.VisView.Session
VVI.VisView.SessionPackage

• Obsolete Excel sheet functionality

Teamcenter Extensions for Microsoft Office does not generate a live Excel sheet
for the Excel 2003 application. However, it continues to generate a static sheet
for Excel 2003. Users should have Excel 2007 installed to use the live feature.
• Obsolete bookmark launch functionality for Lifecycle Visualization

(First published Teamcenter Engineering 2005 SR1)
The legacy functionality that launches Lifecycle Visualization from the rich client
and thin client using bookmarks is obsolete. This functionality is superseded by
the functionality that launches Lifecycle Visualization using the VVI file, which
is based on the PLM XML launch mechanism and Data Integration Services
Adapter technology. The IMAN_show_open_in_pv_button preference that
enables the functionality is also removed.
• Adobe will no longer support its SVG Viewer plug-in for Internet
Explorer
As of January 2009, Adobe will no longer support or enhance its SVG Viewer
plug-in for Internet Explorer. Siemens PLM Software is planning to replace this
technology in the thin client, but we recommend that you continue to use it to
enable the visualization of workflow processes and supersedure part history.
• Removal of Multiple View Editor (MVE)

The Teamcenter Multiple View Editor is removed from Teamcenter 8 due to
the low customer base implementation and duplication of functionality in
Multi-Structure Manager.
• Users can no longer change a translation request priority

(First published Teamcenter 2007.1.)
Users can no longer change the priority of a submitted translation request in
the translation administrator console.
Administrators can change priorities as well as translation execution times in
the translation administrator console.

Before you begin
• Property rules are replaced by the property constants framework

(First published 2007.1)
Property rules are replaced with the property constants framework.
Property constants data model elements support true inheritance of every
feature of the property rule. The existing property rules data model did not
allow you to override a specific feature of the rule without also setting the other
features. Once a property rule is created, all features are set and any inherited
rule subsequently created from a higher business object in the hierarchy likely
would not pass its new feature values past this property rule to business objects
below. The new property constants provide a robust framework to support
custom overrides on every feature of the rule.
Migration utilities are incorporated in the upgrade scripts to perform migration
of all existing property rule objects in your database to the property constants
framework. The existing functions used to retrieve the property rules on
the server are deprecated. For the complete list of deprecated property rule
functions, see Obsolete ITK functions.

Obsolete ITK functions
The following functions are obsolete in Teamcenter 8. All of these functions are
replaced by the Business Modeler IDE functionality.
For more information about how to manage the data model and business rules,
see the Business Modeler IDE Guide.
Product Function name

Persistent Object Manager POM_alter_string_length()
POM_am_i_in_schema_edit()
POM_cancel_schema_edits()
POM_define_attr()
POM_define_class()
POM_modify_schema()
POM_promote_class()
POM_remove_attr()
POM_remove_class()
POM_rename_application()
POM_rename_attr()
POM_rename_class()
POM_reset_attribute_property()
POM_reset_class_property()
POM_save_class()
POM_save_schema_edits()
POM_set_attribute_bound_value()
POM_set_attribute_property()
POM_set_attr_lower_null()
POM_set_attr_lower_int()
POM_set_attr_lower_double()
POM_set_attr_lower_char()
POM_set_attr_lower_string()
POM_set_attr_lower_date()
POM_set_attr_lower_utc_date()
POM_set_attr_upper_null()
POM_set_attr_upper_int()
POM_set_attr_upper_double()
POM_set_attr_upper_char()
POM_set_attr_upper_string()
POM_set_attr_upper_date()
POM_set_attr_upper_utc_date()
POM_set_class_property()
POM_set_initial_null()
POM_set_initial_int()
POM_set_initial_double()
POM_set_initial_char()
POM_set_initial_string()
POM_set_initial_date()
POM_set_initial_utc_date()
POM_set_initial_logical()
POM_start_modify()
POM_start_schema_edit()

Before you begin

Engineering Change ECM_add_formtype()
Management ECM_add_process()
ECM_create_change_type()
ECM_delete_type()
ECM_remove_formtypes()
ECM_remove_processes()
ECM_save_type()
ECM_set_effect_shared_flag()
ECM_set_formtypes()
ECM_set_idformat()
ECM_set_processes()
ECM_set_revidformat()
ECM_set_typename()
Enterprise Process Modeling – CR_create_status_type()
cascade release
LOVs LOV_attach_properties()
LOV_attach_properties_with_dep_orders()
LOV_attach_property()
LOV_clear_values()
LOV_copy()
LOV_create()
LOV_delete()
LOV_detach_all_properties()
LOV_detach_properties()
LOV_detach_property()
LOV_insert_values_char()
LOV_insert_values_date()
LOV_insert_values_double()
LOV_insert_values_int()
LOV_insert_values_string()
LOV_insert_values_tag()
LOV_modify_values_char()
LOV_modify_values_date()
LOV_modify_values_double()
LOV_modify_values_int()
LOV_modify_values_string()
LOV_modify_values_tag()
LOV_remove_value_char()
LOV_remove_value_date()
LOV_remove_value_double()
LOV_remove_value_int()
LOV_remove_value_string()
LOV_remove_value_tag()
LOV_replace_property_lov()
LOV_save()
LOV_set_attached_properties()
LOV_set_based_on_lov_shown_indexes()
LOV_set_description()
LOV_set_name()
LOV_set_range_lower_char()
LOV_set_range_lower_date()


LOVs LOV_set_range_lower_double()
LOV_set_range_lower_int()
LOV_set_range_lower_null()
LOV_set_range_lower_string()
LOV_set_range_upper_char()
LOV_set_range_upper_date()
LOV_set_range_upper_double()
LOV_set_range_upper_int()
LOV_set_range_upper_null()
LOV_set_range_upper_string()
LOV_set_reference()
LOV_set_type()
LOV_set_value_classifications()
LOV_set_value_descriptions()
LOV_set_value_filters()
LOV_set_values_char()
LOV_set_values_date()
LOV_set_values_double()
LOV_set_values_int()
LOV_set_values_string()
LOV_set_values_tag()
Forms FORMTYPE_set_display_file_name()
FORMTYPE_add_subtype()
FORMTYPE_create()
FORMTYPE_delete()
FORMTYPE_modify()
FORMTYPE_set_def_class_name()
TE types IMANTYPE_add_subtype()
IMANTYPE_create()
IMANTYPE_delete()
IMANTYPE_hide_type()
IMANTYPE_remove_property()
IMANTYPE_save()
IMANTYPE_set_parent_type()
IMANTYPE_show_type()
TCTYPE_add_subtype()
TCTYPE_create()
TCTYPE_delete()
TCTYPE_hide_type()
TCTYPE_remove_property()
TCTYPE_save()
TCTYPE_set_parent_type()
TCTYPE_show_type()
Item ITEM_create_type()

Before you begin

Application Encapsulation – AE_add_datasettype_file_ref()
dataset AE_add_datasettype_ref()
AE_add_datasettype_subtype()
AE_add_datasettype_tool()
AE_add_datasettype_view_tool()
AE_add_oper_postaction()
AE_add_oper_postaction_param()
AE_add_oper_preaction()
AE_add_oper_preaction_param()
AE_add_tool_oper_param()
AE_add_tool_oper_ref()
AE_add_tool_param()
AE_add_tool_ref()
AE_create_datasettype()
AE_create_datasettype_with_edit_view()
AE_initialize_datasettype()
AE_remove_datasettype_file_ref()
AE_remove_datasettype_ref()
AE_remove_datasettype_tool()
AE_remove_datasettype_view_tool()
AE_remove_oper_postaction()
AE_remove_oper_postaction_param()
AE_remove_oper_preaction()
AE_remove_oper_preaction_param()
AE_remove_tool_oper_param()
AE_remove_tool_oper_ref()
AE_set_datasettype_actions()
AE_set_datasettype_def_tool()
AE_set_datasettype_def_view_tool()
AE_set_datasettype_desc()
AE_set_datasettype_name()
AE_set_datasettype_parent()
Application Encapsulation – tool AE_add_tool_input_format()
AE_add_tool_output_format()
AE_add_tool_parameter()
AE_create_tool()
AE_initialize_tool()
AE_remove_tool_parameter()
AE_set_tool_classification()
AE_set_tool_install_date()
AE_set_tool_shell()
AE_set_tool_shell_flag()
AE_set_tool_vendor()
User exits USER_add_canned_methods()
PLM XML – Application AIType_create()
Interface AIType_set_is_used_for_idc()
Multi-Structure Manager COLLABCTX_sctype_delete_data()
COLLABCTX_sctype_set_is_composition()
COLLABCTX_sctype_set_single_end_item()
COLLABCTX_set_working_context()


Mechatronics Process GDELinkType_add_subtype()
Management – GDE link GDELinkType_create()
GDELinkType_delete()
GDELinkType_modify()
GDELinkType_set_def_class_name()
GDETYPE_add_subtype()
GDETYPE_create()
GDETYPE_create_subtype()
GDETYPE_delete()
GDETYPE_modify()
GDETYPE_set_def_class_name()
GDETYPEDEF_create()
GDETYPEDEF_delete()
GDETYPEDEF_set_cardinality()
GDETYPEDEF_set_view_types()
Canned methods METHOD_CM_add_method()
METHOD_CM_init_module()
METHOD_CM_log_details()
METHOD_CM_register_function()
Product structure – general GCR_create_relation_type()
component relation
Product structure PS_create_note_type()
PS_create_occurrence_type()
PS_create_view_type()
PS_delete_note_type()
PS_delete_occurrence_type()
PS_delete_view_type()
PS_set_note_type_default_value()
PS_set_note_type_description()
PS_set_note_type_name()
PS_set_occurrence_type_name()
PS_set_view_type_name()
ID context IDCXT_create()
IDCXT_rule_create()
IDCXT_rule_set_idcontext()
IDCXT_rule_set_identifier_type()
IDCXT_rule_set_idfbl_type()
IDCXT_rule_set_rule()
IDCXT_set_description()
IDCXT_set_name()

Before you begin

Properties – naming rule NR_add_pattern()
NR_attach_property()
NR_create()
NR_delete()
NR_delete_pattern()
NR_detach_property()
NR_modify_pattern()
NR_save()
NR_set_autogen()
NR_set_counter_values()
NR_set_init_and_max()
NR_set_name()
Properties PROPDESC_set_protection()
PROPDESC_is_required
PROPDESC_is_modifiable
Unit of measure UOM_create()
UOM_initialize()
UOM_set_name()
UOM_set_symbol()
The following functions are also obsolete in Teamcenter 8.
Obsolete function Replacement function

AE_copy_dataset AE_copy_dataset_with_id
AE_create_dataset AE_create_dataset_with_id
AE_initialize_dataset AE_initialize_dataset_with_id
AOM_UIF_is_displayable CONSTANTS_get_property_constant_value
with signature.
AOM_UIF_is_enabled CONSTANTS_get_property_constant_value
with signature.
AOM_UIF_is_required CONSTANTS_get_property_constant_value
with signature.
BOM_line_add_alternate BOM_line_add_substitute
BOM_line_ask_attribute_external None.
BOM_line_ask_has_alternates BOM_line_ask_has_substitutes
BOM_line_ask_is_alternate BOM_line_ask_is_substitute
BOM_line_change_to_substitute BOM_line_change_to_replace
BOM_line_get_remote_children BOM_line_ask_remote_object
BOM_line_hide_alternates BOM_line_hide_substitutes
BOM_line_is_substitutable BOM_line_is_replaceable
BOM_line_list_alternates BOM_line_list_substitutes
BOM_line_list_related_alternates BOM_line_list_related_substitutes
BOM_line_prefer_alternate BOM_line_prefer_substitute


BOM_line_relate_alternates BOM_line_relate_substitutes
BOM_line_remove_related_alternates BOM_line_remove_related_substitutes
BOM_line_show_alternates BOM_line_show_substitutes
BOM_line_substitute BOM_line_replace
BOM_line_substitute_gde BOM_line_replace_gde
BOM_window_hide_alternates BOM_window_hide_substitutes
BOM_window_show_alternates BOM_window_show_substitutes
CFM_ask_rule_text None.
CFM_date_entry_ask_date CFM_rule_ask_date
CFM_date_entry_set_date CFM_rule_set_date
CFM_rule_ask_effective_date CFM_rule_ask_date
CFM_rule_set_effective_date CFM_rule_set_date
CFM_unitno_entry_ask_no CFM_rule_ask_unit
CFM_unitno_entry_set_no CFM_rule_set_unit
EMH_get_error_string EMH_ask_error_text or EMH_ask_errors
EPM_get_resource_pool EPM_ask_resourcepool
EPM_set_condition_task_result EPM_set_task_result
FORM_ask_file_name None.
FORM_ask_value AOM_ask_value_type
FORM_ask_values FORM_ask_prop_names
andAOM_ask_value_type
FORM_describe AOM_ask_value_type
FORM_details AOM_ask_value_type
FORM_set_value AOM_ask_value_type or AOM_UIF_set_value
FORMTYPE_ask_display_file_name None.
FORMTYPE_set_display_file_name None.
IDM_add_item_related GRM_create_relation, followed byAOM_save,
then AOM_unlock
IDM_add_revision_related GRM_create_relation, followed byAOM_save,
then AOM_unlock
IDM_ask_item ITEM_ask_item_of_rev

Before you begin

IDM_ask_item_id ITEM_ask_id
IDM_ask_item_related GRM_list_secondary_objects_only
IDM_ask_revision_id ITEM_ask_rev_id
IDM_ask_revision_related GRM_list_secondary_objects_only
IDM_copy_item_revision ITEM_copy_rev
IDM_create_item ITEM_create_item, followed
by ITEM_set_description,
ITEM_set_rev_description,
ITEM_set_rev_name, and AOM_save
IDM_exit_module None.
IDM_find_item ITEM_find_item
IDM_find_item_revision ITEM_find_rev
IDM_init_module None.
IDM_initialize_item ITEM_set_id, followed by ITEM_set_name,
ITEM_set_description, AOM_save,
ITEM_find_rev, and ITEM_set_rev_name.
IDM_initialize_item_revision ITEM_set_rev_id, ITEM_set_rev_name and
ITEM_set_rev_description
IDM_item_extent POM_instances_of_class
IDM_item_revision_extent POM_instances_of_class
IDM_remove_item_related GRM_find_relation then AOM_delete
IDM_remove_revision_related GRM_find_relation then AOM_delete
ITEM_ask_attachment_name TCTYPE_ask_name
ITEM_attach_object GRM_create_relation, followed by AOM_save,
then AOM_unlock
ITEM_attach_object_tag GRM_create_relation, followed by AOM_save,
then AOM_unlock
ITEM_attach_rev_object GRM_create_relation, followed by AOM_save,
then AOM_unlock
ITEM_attach_rev_object_tag GRM_create_relation, followed by AOM_save,
then AOM_unlock
ITEM_detach_object GRM_find_relation then AOM_delete.
ITEM_detach_object_tag GRM_find_relation then AOM_delete.
ITEM_detach_rev_object GRM_find_relation then AOM_delete.
ITEM_detach_rev_object_tag GRM_find_relation then AOM_delete.
ITEM_list_all_attachments GRM_list_relations or
GRM_list_secondary_objects
ITEM_list_all_attachments_tag GRM_list_secondary_objects_only,
ITEM_list_all_revs or ITEM_list_bom_views


ITEM_list_all_rev_attachments GRM_list_relations or
GRM_list_secondary_objects
ITEM_list_attachs_of_type GRM_list_secondary_objects_only
ITEM_list_attachs_of_type_tag GRM_list_secondary_objects_only,
ITEM_list_all_revs or ITEM_list_bom_views
ITEM_list_possible_attachments_tag None.
ITEM_list_rev_attachs_of_type GRM_list_secondary_objects_only
ITEM_update_item_attachment GRM_find_relation, followed by AOM_delete,
GRM_create_relation, AOM_save, and
AOM_unlock
ITEM_update_rev_attachment GRM_find_relation, followed by AOM_delete,
GRM_create_relation, AOM_save, and
AOM_unlock
LM_post_event LM_post_info
NR_ask_counter_values NR_ask_counter_details
NR_next_alt_id NR_next_value
NR_next_dataset_id NR_next_value
NR_next_dataset_rev_id NR_next_value
NR_next_item_id NR_next_value
NR_next_rev_id NR_next_value
NR_next_rev_id_from_alt_rule NR_next_value
NR_rule_desc NR_rule_desc_with_counters
PROP_ask_descriptor AOM_ask_descriptor
PROP_ask_lov None.
PROP_ask_max_num_elements AOM_ask_max_num_elements
PROP_ask_max_string_length AOM_ask_max_string_length
PROP_ask_name None.
PROP_ask_num_elements AOM_ask_num_elements
PROP_ask_owning_object None.
PROP_ask_property_by_name None.
PROP_ask_property_type AOM_ask_property_type
PROP_ask_value_char AOM_ask_value_char
PROP_ask_value_char_at AOM_ask_value_char_at
PROP_ask_value_chars AOM_ask_value_chars
PROP_ask_value_date AOM_ask_value_date
PROP_ask_value_date_at AOM_ask_value_date_at
PROP_ask_value_dates AOM_ask_value_dates
PROP_ask_value_double AOM_ask_value_double

Before you begin

PROP_ask_value_double_at AOM_ask_value_double_at
PROP_ask_value_doubles AOM_ask_value_doubles
PROP_ask_value_int AOM_ask_value_int
PROP_ask_value_int_at AOM_ask_value_int_at
PROP_ask_value_ints AOM_ask_value_ints
PROP_ask_value_logical AOM_ask_value_logical
PROP_ask_value_logical_at AOM_ask_value_logical_at
PROP_ask_value_logicals AOM_ask_value_logicals
PROP_ask_value_string AOM_ask_value_string
PROP_ask_value_string_at AOM_ask_value_string_at
PROP_ask_value_strings AOM_ask_value_strings
PROP_ask_value_tag AOM_ask_value_tag
PROP_ask_value_tag_at AOM_ask_value_tag_at
PROP_ask_value_tags AOM_ask_value_tags
PROP_ask_value_type AOM_ask_value_type
PROP_assign_char AOM_assign_char
PROP_assign_char_at AOM_assign_char_at
PROP_assign_chars AOM_assign_chars
PROP_assign_date AOM_assign_date
PROP_assign_date_at AOM_assign_date_at
PROP_assign_dates AOM_assign_dates
PROP_assign_double AOM_assign_double
PROP_assign_double_at AOM_assign_double_at
PROP_assign_doubles AOM_assign_doubles
PROP_assign_int AOM_assign_int
PROP_assign_int_at AOM_assign_int_at
PROP_assign_ints AOM_assign_ints
PROP_assign_logical AOM_assign_logical
PROP_assign_logical_at AOM_assign_logical_at
PROP_assign_logicals AOM_assign_logicals
PROP_assign_string AOM_assign_string
PROP_assign_string_at AOM_assign_string_at
PROP_assign_strings AOM_assign_strings
PROP_assign_tag AOM_assign_tag
PROP_assign_tag_at AOM_assign_tag_at
PROP_assign_tags AOM_assign_tags


PROP_get_value_char AOM_get_value_char
PROP_get_value_char_at AOM_get_value_char_at
PROP_get_value_chars AOM_get_value_chars
PROP_get_value_date AOM_get_value_date
PROP_get_value_date_at AOM_get_value_date_at
PROP_get_value_dates AOM_get_value_dates
PROP_get_value_double AOM_get_value_double
PROP_get_value_double_at AOM_get_value_double_at
PROP_get_value_doubles AOM_get_value_doubles
PROP_get_value_int AOM_get_value_int
PROP_get_value_int_at AOM_get_value_int_at
PROP_get_value_ints AOM_get_value_ints
PROP_get_value_logical AOM_get_value_logical
PROP_get_value_logical_at AOM_get_value_logical_at
PROP_get_value_logicals AOM_get_value_logicals
PROP_get_value_string AOM_get_value_string
PROP_get_value_string_at AOM_get_value_string_at
PROP_get_value_strings AOM_get_value_strings
PROP_get_value_tag AOM_get_value_tag
PROP_get_value_tag_at AOM_get_value_tag_at
PROP_get_value_tags AOM_get_value_tags
PROP_is_modifiable AOM_is_modifiable
PROP_list_properties AOM_list_properties
PROP_set_value_char AOM_set_value_char
PROP_set_value_char_at AOM_set_value_char_at
PROP_set_value_chars AOM_set_value_chars
PROP_set_value_date AOM_set_value_date
PROP_set_value_date_at AOM_set_value_date_at
PROP_set_value_dates AOM_set_value_dates
PROP_set_value_double AOM_set_value_double
PROP_set_value_double_at AOM_set_value_double_at
PROP_set_value_doubles AOM_set_value_doubles
PROP_set_value_int AOM_set_value_int
PROP_set_value_int_at AOM_set_value_int_at
PROP_set_value_ints AOM_set_value_ints
PROP_set_value_logical AOM_set_value_logical

Before you begin

PROP_set_value_logical_at AOM_set_value_logical_at
PROP_set_value_logicals AOM_set_value_logicals
PROP_set_value_string AOM_set_value_string
PROP_set_value_string_at AOM_set_value_string_at
PROP_set_value_strings AOM_set_value_strings
PROP_set_value_tag AOM_set_value_tag
PROP_set_value_tag_at AOM_set_value_tag_at
PROP_set_value_tags AOM_set_value_tags
PROP_string_to_tag AOM_string_to_tag
PROP_tag_to_string AOM_tag_to_string
PROP_UIF_ask_name AOM_UIF_ask_name
PROP_UIF_ask_property_by_name None.
PROP_UIF_ask_value AOM_UIF_ask_value
PROP_UIF_is_displayable AOM_UIF_is_displayable
PROP_UIF_set_value AOM_UIF_set_value
PROPDESC_is_displayable CONSTANTS_get_property_constant_value
with signature.
PROPDESC_is_modifiable CONSTANTS_get_property_constant_value
with signature.
PROPDESC_is_required CONSTANTS_get_property_constant_value
with signature.
PS_add_related_alternates PS_add_related_substitutes
PS_ask_transform PS_ask_plmxml_transform
PS_change_to_substitute PS_change_to_replace
PS_list_related_alternates PS_list_related_substitutes
PS_next_revision_name None.
PS_remove_related_alternates PS_remove_related_substitutes
PS_set_transform PS_set_plmxml_transform
SA_delete_user_objects SA_delete_user
VMS_add_mfg_part_to_comm_part None.
WSOM_ask_status WSOM_status_ask_effectivities followed by
WSOM_eff_ask_ranges.
WSOM_eff_set_range WSOM_eff_set_date_range or
WSOM_eff_set_unit_range.
WSOM_eff_set_range_type WSOM_eff_clear_ranges, then a set function.
WSOM_effectivity_ask_date_range WSOM_eff_ask_date_range
WSOM_effectivity_ask_dates WSOM_eff_ask_dates
WSOM_effectivity_ask_end_item WSOM_eff_ask_end_item


WSOM_effectivity_ask_range WSOM_eff_ask_range
WSOM_effectivity_ask_range_type WSOM_eff_ask_range_type
WSOM_effectivity_ask_ranges WSOM_eff_ask_ranges
WSOM_effectivity_ask_unit_range WSOM_eff_ask_unit_range
WSOM_effectivity_ask_units WSOM_eff_ask_units
WSOM_effectivity_create_with_text WSOM_eff_create_with_date_text or
WSOM_eff_create_with_unit_text
WSOM_effectivity_is_protected WSOM_eff_ask_is_protected
WSOM_effectivity_set_dates WSOM_eff_set_dates
WSOM_effectivity_set_end_item WSOM_eff_set_end_item
WSOM_effectivity_set_protection WSOM_eff_set_protection
WSOM_effectivity_set_range WSOM_eff_set_date_range or
WSOM_eff_set_unit_range.
WSOM_effectivity_set_range_type WSOM_eff_clear_ranges, then a set function
WSOM_effectivity_set_units WSOM_eff_set_units
For more information about the replacement functions, see the Integration Toolkit
Function Reference.

Before you begin
Obsolete utilities
Teamcenter command line utilities are used by administrators to manage

Teamcenter installations.
For more information about utilities, see the Utilities Reference.
Warning
Do not use any of these utilities or data model corruption may result.
The following utilities are obsolete in Teamcenter 8.
Product area Utility Description

Automotive gmpdm_get_location_info Populates URLs for existing parts
in GPDS and generates two output
files.
Business Modeler apply_naming_rule Creates and maintains naming
rules for the naming rules checker.
business_rules_dtdxml2plmxml Converts an XML file conforming
to a specified DTD into a valid PLM
XML file pertaining to a specified
PLM XML schema definition file.
deepcopyrules_migration Migrates deep copy rules existing
in a Teamcenter’s engineering
process management 8.1 database
preference file to Teamcenter 2007
database rules.
grm Provides means to manipulate
constraint rules.
import_export_business_rules Imports and exports business
rules to and from the Teamcenter
database.
install_bmf_rules Installs extensions and operations
for all messages defined in the
system.
install_type_display_rules Creates system-level type display
rules.
migrate_action_rules_to_bmf Migrates action rules defined
for a site and converts them to
extension rules.
migrate_alias Migrates alias data to alias
identifier data without modifying
or deleting the existing data. Only
alias data owned by the local site
can be migrated. You can qualify
what data is migrated.


migrate_complex_property_rules Creates complex property rules
in the database corresponding
to those stored in the preference
variables prior to Engineering
Process Management 2005 SR1.
Change create_change_types Provides a means for site
Management administrators to define one or
more change type definitions from
the command line. This utility
creates change types according to
the information contained in an
input file.
Customization tc_erp_schema Updates the database with new
classes and attributes. Once
made, these updates cannot be
reversed; therefore, you should
carefully analyze what form types
and attributes are required to
send data to SAP. Once attributes
are created for a form type, they
can not be removed or modified.
However, you can create new form
types to correct the attributes
required, but this prevents
previously created and populated
form types from being correctly
read or sent to ERP, because they
do not correspond to the new
definitions in the mapping file.
Data sharing upgrade_nx_cam_templates Imports NX/CAM templates into
the Teamcenter database.
Migration migrate_type_display_prefs In the Teamcenter’s engineering
process management 8.0 thin
client interface, only those
form type values listed in the
FormTypePref preference are
displayed. This utility considers
the preference values stored at
the site level and creates type
display rules so that only the types
listed under the site preference
are displayed in the object creation
dialog boxes. Then the utility
traverses the group hierarchy and
considers the preference values
in the group preference files and
creates type display rules.
Product structure input_notetype_default Inputs default values for note
types.

Before you begin

Visualization batchmode_clearance_analysis.pl Performs clearance analysis
on a product structure and
stores all issue and results
data in the clearance database.
This script is replaced by the
analyze_managed_product.pl
script, which is included in the
stand-alone Teamcenter’s lifecycle
visualization mockup installation.
runJtCacheClean Physically removes orphaned files
from the cache used by the JT
cache service.
runJtCacheInit Initializes user sessions for the
Teamcenter Data Integration
Services Adapter JT cache
populator.
runJtCachePopulator Runs the Teamcenter Data
Integration Services Adapter JT
cache populator.
Volume and create_ai_type Creates and updates application
database interface types for Tecnomatix.
management
create_cost_form Creates a cost form type for the
CME Cost Reports; creates a POM
type = CostDataClass and a
Form type = CostDataForm
with a cost field = CostAmount.
create_snap_shot_view_form Creates the SnapShotClass form
for the SnapShotView dataset.
datasettype_cleanup Locates corrupt dataset types and
removes them from the database.
install_lovs Creates the default lists of values
(LOVs).
install_types Adds new types to existing classes
and may also be used to delete
types, provided that they are not
referenced by other objects. This
utility is initially run as part of
the installation program to install
predefined object types.
make_datasettype Defines new dataset types and
tools for Teamcenter.


Schema browser (character mode) The sb utility is a character-mode
(VT100) utility used to view
(browse) the Persistent Object
Model (POM) class hierarchy
(schema) as well as to create
and manage object classes and
attributes. The utility operates
in two modes: browser mode and
command mode.
update_class_property Updates the schema to change
some of class properties.
upgrade_ar Disables follow-on-export of
the items_tag attribute of
the ItemRevision class and
the child_bv and child_item
attributes of the PSOccurrence
class.
upgrade_types Upgrades an existing database
to create imantypes for all
workspaceobjects, formtypes,
and datasettypes. Checks for
duplicate types, and ensures there
are no clashes between type and
class names.
upgrade_validation_objects Upgrades the validation objects
to Teamcenter Engineering 10 or
later.

Before you begin
Obsolete preferences
Preferences are special environment variables stored in the Teamcenter database
that are read during application usage. To work with preferences, in the rich client,
choose Edit→Options and choose Index at the bottom of the Options dialog box.
For more information about preferences, see the Preferences and Environment
Variables Reference.
The following preferences are obsolete in Teamcenter 8:
• BOM_line_full_props
• CAE_execute_server
• Cfg_Att_add_props_of_form_types
• GMS_offline_use_TcGS
These preferences are for internal Siemens PLM Software use only.
• GMS_site_checkin_after_import
This preference is for internal Siemens PLM Software use only.
• IMAN_<datasettype>_Volume preference obsoleted
• <ItemRevision-business-object>_Maturity_Level
All preferences of this type are replaced by the MaturityStatuses business
object constant.
• NX_interop_type
• PSE_absocc_compound_properties
• PSE_add_props_of_item_form_types
• PSE_add_props_of_rev_form_types
• PUBLISHEDOBJECT_object_extended_attrs
• QRYColumnsShowWidthPref
• <relationType>_relation_primary
All preferences of this type are replaced by relation properties.
• TC_DIS_AutoCreate_ITEM
• TC_DIS_ITEM_AutoCreated_TypeName
• TC_DIS_image_capture_dstype
• TC_DIS_markup_dstype

• TC_DIS_3DMarkup_dstype
• TC_DIS_session_dstype
• TC_DIS_save_plmxml_dstype
• TC_DIS_markup_relationship
• TC_DIS_3DMarkup_relationship
• TC_DIS_image_capture_relationship
• TC_DIS_session_relationship
• TC_DIS_save_plmxml_relationship
• TC_vmu_version
• TC_show_open_in_pv_button
• <type>_createprops
• <type>_viewerprops
• <type>_DisplayProperties
• View_line_display_props

Before you begin
Obsolete environment variables

Environment variables allow you to control many aspects of Teamcenter behavior.
For more information about environment variables, see the Preferences and
Environment Variables Reference.
The following environment variables are obsolete:
• TC_CURSOR_CACHE
Master variable for the POM minimize query parsing functionality. Valid
values are enabled, enable, true , and on. If set to a value other than one
of the valid values, the feature is inactive and the other POM query parsing
environment variables have no affect on the system. Additional POM query
parsing environment variables are TC_CURSOR_NUM, TC_CURSOR_SQL,
TC_CURSOR_LNSZ, and TC_CURSOR_STAT.
• TC_CURSOR_NUM
Determines the size of the cursor pool for each Teamcenter server. This is
the number of database cursors available to the server for processing SQL
statements.
• TC_CURSOR_SQL
Determines the size of the SQL statement pool for each Teamcenter server. The
SQL statement pool is where the server keeps track of SQL statements that have
already been processed. If a SQL statement has recently been executed, or has
been executed a sufficient number of times, the SQL entry in the pool points to
the cursor in the cursor pool that last executed the SQL statement. When this
variable is set equal to the value of TC_CURSOR_NUM variable, the least
recently used algorithm determines which cursor is the next available cursor.
Otherwise, the cursor associated with the SQL statement that has the lowest
execution count is designated the next available cursor.
• TC_CURSOR_LNSZ
Determines the maximum line size used when dumping SQL statements to
the system log (see the TC_CURSOR_STAT variable.) If dumping an SQL
statement to the system log file would cause the length of the line to exceed this
value, attributes are removed from the select statements and replaced with
three periods (…). If the cursor and the SQL statement queues are not being
dumped, this parameter has no affect on the system.
• TC_CURSOR_STAT
Dumps basic operational information about the efficiency of the configuration to
the system log file. It can also be used to enable extensive SQL statement pool
validation. This variable is a bit mapped variable that accepts multiple values.
The following are four configuration examples for dumping all information at
server termination:
TC_CURSOR_STAT = 1 256 512 1024

TC_CURSOR_STAT = 1793
TC_CURSOR_STAT = 0x0001 0x0100 0x0200 0x0400
TC_CURSOR_STAT = 0x0701

• TC_LOCALIZATION_DIR
Defines the localization to be used by the TextServer process. It is replaced
by the nlsDefaultLang function, which checks the locale used by the server
machine to deduct the default locale to be used by the TCServer process.
Obsolete Java classes
If you are upgrading your rich client customizations from a previous version of
Teamcenter or Engineering Process Management, there are several changes you
need to know about.
• Starting in Teamcenter 2007, the beginning of package names changed from
com.ugsolutions to com.teamcenter. In addition, the term iman in package
names was removed. In most instances, the term rac replaced it.
• Starting in Teamcenter 2007, the packages are contained in Eclipse plug-ins

instead of the portal.jar file.
• Starting in Teamcenter 2007, the term IMAN in class names was changed in
most instances to TC.
• Starting in Teamcenter 8, classes with MenuBar or ToolBar in the name are

no longer used.
For example, the AbstractIMANApplication class in the

com.ugsolutions.iman.common package in Teamcenter Engineering
2005 is the AbstractTCApplication class in the com.teamcenter.rac.common
package in the com.teamcenter.rac.common.jar plug-in in Teamcenter 8.
For more specific information about the changes in the packages, plug-ins, and
classes since Teamcenter Engineering 2005, contact GTAC to obtain a detailed
spreadsheet.

Chapter
2 What’s new for Teamcenter 8
New Teamcenter applications and solutions . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Teamcenter documentation . . . . . . . . . . . . . . . . . . . . . ......... ....... 2-2

New Teamcenter documentation . . . . . . . . . . . . . . . ......... ....... 2-2
Renamed Teamcenter documentation . . . . . . . . . . . ......... ....... 2-4
Teamcenter help for MS Office integrations available from within MS Office
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ......... ....... 2-5
User feedback link on each topic . . . . . . . . . . . . . . . ......... ....... 2-5
Access the PDF collection launch page . . . . . . . . . . ......... ....... 2-5
Installing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 2-6

Teamcenter 8 software distributed in multiple ZIP files . . . . . . . .. . . . . . 2-6
Client support for Macintosh . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 2-6
Rich client not supported on HP-UX platforms . . . . . . . . . . . . . . .. . . . . . 2-6
TEM enforces required Oracle version . . . . . . . . . . . . . . . . . . . .. . . . . . 2-6
Teamcenter 8 application server, Web server, and browser support . . . . . . 2-7
Full-text search for Microsoft Office documents . . . . . . . . . . . . . .. . . . . . 2-7
Named user licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . 2-7
Configuring Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Business Modeler IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Item revision definition configuration (IRDC) . . . . . . . . . . . . . . . . . . . 2-8
Alternate ID enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Building and packaging C++ customization code from the Business Modeler
IDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
C++ customization support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
More consistent business rules inheritance . . . . . . . . . . . . . . . . . . . . 2-10
Services can be created using the Business Modeler IDE . . . . . . . . . . . 2-10
Deep copy enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Addition of conditions to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Exposing required and visible properties during item creation . . . . . . . 2-11
Enhanced naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Revision naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Mapping Designer support for MapForce 2008 . . . . . . . . . . . . . . . . . . 2-12
Administering Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

User access logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Store and forward files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Accessing multiple FMS databases through a single FCC . . . . . . . . . . . . . 2-14
Automatic FCC reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Manual FCC reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Performing hot backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Locking site preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Shared memory for site preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Rendition and translation capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Site definition improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Validation rule and run validation and view results . . . . . . . . . . . . . . . . . 2-20
Enhancements to export to Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Templates for document export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Content Management administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Security Services WebSEAL proxy support . . . . . . . . . . . . . . . . . . . . . . . 2-24
File Management System (FMS) WebSEAL proxy support . . . . . . . . . . . . 2-25
File Management System (FMS) URL path extensions . . . . . . . . . . . . . . . 2-26
FMS server cache (FSC) SSL client credentials (two-way SSL) . . . . . . . . . 2-26
Using Teamcenter interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Vendor management enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Requirements in thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Teamcenter rich client perspectives and views . . . . . . . . . . . . . . . . . . . . . 2-28
My Teamcenter functionality refactored . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Rich client search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Search for items by owning organization . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Multilanguage support for clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Thin client on Macintosh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Microsoft Office client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Enhancements to Organization and Portfolio, Program and Project Management
allow you to find users or projects more quickly . . . . . . . . . . . . . . . . . . . 2-32
Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Workflow participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Failure paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Classifying data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37

Multi-unit support in Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
Managing documents, reports, requirements, and schedules . . . . . . . . . . . . . . 2-38

Requirements integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Create reports from saved queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Scheduling templates and deliverables enhancements . . . . . . . . . . . . . . . 2-38
Scheduling extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Scheduling enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Baselines for requirements management . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Enhancements to document generation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

PLM XML software development kit version upgraded . . . . . . . . . . . . . . . 2-41
PLM XML performance improvements . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Backward compatible schema mapping for extended attributes . . . . . . . . . 2-41
Global Services Data Exchange solution application server support . . . . . . 2-42
Global Services SOA connection pooling . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Global Services Teamcenter 8 rich client connector . . . . . . . . . . . . . . . . . . 2-42
Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Structure clone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Teamcenter 8 Release Bulletin PLM00001 C

Time management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Creating 2D snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Find checked-out objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Showing unconfigured assigned occurrences . . . . . . . . . . . . . . . . . . . . . . 2-45
Incremental change when cloning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
New Process dialog box changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Manufacturing preferences in preference hierarchy . . . . . . . . . . . . . . . . . 2-46
Encrypting attributes in Resource Manager . . . . . . . . . . . . . . . . . . . . . . 2-46
Open PAD user interface at PAD level . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Managing Mechatronics data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47

Wiring harness options and variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Embedded Software Design Data Management . . . . . . . . . . . . . . . . . . . . 2-47
Visualizing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48

General enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
New SOA-based visualization integration . . . . . . . . . . . . . . . . . . . . . 2-48
Lifecycle Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
2D and 3D thumbnail previews . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
.vfz collaboration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Enhanced work session support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Session attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
3D PMI enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Improved product structure loading . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
Improved rendering when generating 2D images from 3D views . . . . . 2-51
3D snapshot improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
2D improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51
3D improvements for Standard, Professional, and Mockup . . . . . . . . . . . . 2-52
Markup and callout enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
Enhanced support for NX advanced assembly functionality . . . . . . . . . 2-53
Enhancement for displaying attributes and PMI . . . . . . . . . . . . . . . . 2-53
Part report enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
3D improvements for Professional and Mockup . . . . . . . . . . . . . . . . . . . . 2-54
New Direct Model-based swept volumes . . . . . . . . . . . . . . . . . . . . . . 2-54
Key change in navigation explore mode . . . . . . . . . . . . . . . . . . . . . . . 2-54
Enhancements for ECAD Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
Working with schematic documents . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
Cross probing PCB and schematic documents . . . . . . . . . . . . . . . . . . 2-55
Net and page connector navigation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
PCB measurement markups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
Design for Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
ECAD reporting capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Printing ECAD documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Enhancements for ClearanceDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56
Managing CAE data . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

CAE Manager – Inspector . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Enhanced simulation process launch .. . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Launch simulation process remotely ... . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
Repeatable Digital Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59

DesignContext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
Clearance database integration enhancements . . . . . . . . . . . . . . . . . . 2-59
DesignContext on cacheless search . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60

Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60
DPV Help included in Teamcenter Help collection . . . . . . . . . . . . . . . . . . 2-60
Managing Maintenance, Repair, and Overhaul data . . . . . . . . . . . . . . . . . . . . 2-61

As-Built Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61
Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62

Service-oriented architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
New Workflow operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
Feature enhancements in SOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62
New operation for Teamcenter Publish . . . . . . . . . . . . . . . . . . . . . . . 2-63
WSDL support in Teamcenter services . . . . . . . . . . . . . . . . . . . . . . . 2-63
Alternate ID support for NX Integration . . . . . . . . . . . . . . . . . . . . . . 2-63
Occurrence override support for NX Integration . . . . . . . . . . . . . . . . . 2-64
Support for adding objects to projects . . . . . . . . . . . . . . . . . . . . . . . . 2-64
CAM support for NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
Miscellaneous new services for the NX Integration . . . . . . . . . . . . . . . 2-65
Support for features in the NX Integration . . . . . . . . . . . . . . . . . . . . 2-65
Baselines for the NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Lifecycle Visualization product structure loading performance
improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
New change management service . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Rich client debugging tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Teamcenter supports UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Teamcenter industry solutions . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68

Aerospace and Defense . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
Parts list management . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
Owning organization . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
Enhanced naming rules . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
Revision naming rules . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
Sample program . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69
Properties on relation . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Program-level security . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Consumer Packaged Goods . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71
Package and brand management . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71
Interspec integration . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71
Specification Manager . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
Performing integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73

Teamcenter Gateway for Electronic Design Automation (EDA) . . . . . . . . . 2-73
Managing part library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73
Support for Mentor Graphics PADS . . . . . . . . . . . . . . . . . . . . . . . . . 2-73
Support for OrRCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73
SOA communication layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73
Teamcenter Gateway for EDA client logging . . . . . . . . . . . . . . . . . . . 2-74
Teamcenter Gateway for EDA application . . . . . . . . . . . . . . . . . . . . . 2-74
NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75
Managing NX Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75
NX/requirements integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75
Managing translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76

Translation intelligent licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
Translation request persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76

Repeating tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
Load balancing based on CPU usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77
See error log in the Request Administration Console . . . . . . . . . . . . . . . . 2-77

Chapter
2 What’s new for Teamcenter 8
Welcome to Teamcenter 8. There are many new features available in this version;
you can find detailed descriptions of these in their related functional categories.
Teamcenter documentation
Installing Teamcenter
Configuring Teamcenter
Administering Teamcenter
Using Teamcenter interfaces
Managing changes and workflows
Classifying data
Managing documents, reports, requirements, and schedules
Sharing data
Managing product structures
Managing manufacturing data
Managing Mechatronics data
Visualizing products
Managing CAE data
Repeatable Digital Validation
Managing quality data
Managing Maintenance, Repair, and Overhaul data
Customizing Teamcenter
Teamcenter industry solutions
Performing integrations
Managing translations
New Teamcenter applications and solutions

Several new applications are available in Teamcenter 8. For each of these, there
is also online help:
• Aerospace and Defense industry solution
• Teamcenter’s Client for Microsoft Office
• Consumer Packaged Goods industry solution
• Content Management
• Lifecycle Viewer
• MRO’s As-Built Manager
• Specification Manager

Chapter 2 What’s new for Teamcenter 8
Teamcenter documentation
The following are new documentation features in Teamcenter 8.
New Teamcenter documentation

The following table lists new Teamcenter documentation deliverables in Teamcenter
8.
Name Description
Frequently Asked Discusses commonly asked questions about
Questions Teamcenter. Links throughout the answers guide you
to further information within the Teamcenter 8 Help
Library.
Upgrade Guide Provides instructions for upgrading to Teamcenter 8
from the following Teamcenter versions:
• Teamcenter Engineering 9.1.3
• Teamcenter Engineering 2005
• Teamcenter Engineering 2005 SR1
• Teamcenter 2007
Teamcenter Environment Provides all the online help text that is displayed
Manager Help when using the Teamcenter Environment Manager
(TEM) user interface, organized for reference from
the Teamcenter 8 Help Library.
Client for Microsoft Office Teamcenter’s Client for Microsoft Office gives
Guide users access to Teamcenter objects directly through
Microsoft Office Word, Excel, PowerPoint, and
Outlook. Users can navigate Teamcenter, display and
insert Teamcenter data, and interact with that data
without running a Teamcenter client.
Content Management: Set of guides that support your tasks using the
Content Management feature. Content Management
• Content Management is a single source publishing system for the creation
Guide of technical documentation. Technical publications
maintained in the system consist of objects, called
• Content Management topics, and their relationships, which are stored in
Administration Guide the Teamcenter database along with any associated
graphics used in the publications.

What’s new for Teamcenter 8
Name Description
Teamcenter’s Lifecycle Set of guides that support your tasks using Lifecycle
Visualization: Visualization.
• Getting Started with
Product Visualization
• Working with 3D
Models
• Working with 2D
Images
• Using the ECAD

Viewer
• ECAD QuickTour
Tecnomatix Dimensional Set of guides that support your tasks using the
Planning and Validation: Tecnomatix Dimensional Planning and Validation
(DPV) product. DPV enables the extended enterprise
• Getting Started with to collect, manage, dimensionally analyze, and report
Dimensional Planning on quality measurement information.
and Validation
• Dimensional Planning
and Validation
Administration Guide
As-Built Manager Guide As-Built Manager is the first of a series of capabilities
for managing Maintenance, Repair, and Overhaul
(MRO) processes and is a separately licensed
application that is installed as an optional overlay
on top of the standard Teamcenter product.
This application allows you to manage the
as-built configuration of an asset realized from a
product definition structure, such as a design or
manufacturing structure.
C++ API Reference (HTML Provides Doxygen metamodel documentation for
only) Teamcenter developers. The C++ API Reference
contains C++ API documentation for the Foundation
template only.
Thin Client Customization Describes the inner workings of the thin client and
Programmer’s Guide ways Teamcenter programmers can extend or change
its functionality.
Getting Started with Aerospace and Defense provides a data model
Aerospace and Defense template that supports the aerospace and defense
manufacturing industry.
Getting Started with Consumer Packaged Goods provides a data model
Consumer Packaged Goods template that supports customers who manufacture
consumer packaged goods, for example, detergents
or beverages.

Name Description
Specification Manager The Specification Manager application allows you to
Guide view and work with specifications. In the Consumer
Packaged Goods and food and beverage industries,
specifications capture the complete definition of
products and how to manufacture them. These
specifications are developed, reviewed, and eventually
approved, which drives the product release process.
Services Reference Teamcenter Services Reference provides
documentation on APIs for services and operations;
it supplements the Services Guide deliverable in the
Teamcenter 8 Help Library.
Renamed Teamcenter documentation

The following table lists renamed Teamcenter documentation deliverables in
Teamcenter 8.
New title Previous title

What’s New for Teamcenter Release Highlights
8
Getting Started with Getting Started with Teamcenter 2007
Teamcenter
Getting Started with EDA Integration Guide
Electronic (EDA) Lifecycle
Management
Getting Started with Getting Started with Translation Management
Dispatcher (Translation
Management)
Installation on UNIX, Installing UNIX and Linux Client Guide
Linux, and Macintosh
Clients Guide
Dispatcher Server Translation Solution Toolkit Installation Guide
Installation Guide
Dispatcher Server Translation Solution Toolkit Translators Reference
Translators Reference Guide.
Guide
Validation Manager Guide Validation Guide
Rich Client Interface Guide My Teamcenter Guide
Extensions for Microsoft Teamcenter Extensions for Microsoft Office Guide
Office Guide
Microsoft Office Guide Teamcenter Integrations for Microsoft Office Guide
• Integration for Microsoft Office and Network Folders Guide.
Microsoft Office Guide
• Network Folders Guide

New title Previous title

Change Viewer Guide Change Management Guide
Data Exchange Guide Teamcenter Data Exchange Guide
Gateway for Oracle Teamcenter Gateway for Oracle Manufacturing
Manufacturing Configuration Guide
Configuration Guide
Gateway for Oracle Teamcenter Gateway for Oracle Manufacturing Guide
Manufacturing Guide
Multi-Structure Manager Collaboration Context Guide
Guide
Structure Manager Guide Product Structure Editor (PSE)
Plant Designer Guide Factory Structure Editor (FSE) Guide
Manufacturing Process Manufacturing Structure Editor (MSE) Guide

Planner Guide
Embedded Software Embedded Software Manager Guide
Solutions Guide
Teamcenter help for MS Office integrations available from within MS

Office interface
For customers who purchase Client for Office, you can access help for the Teamcenter
features from within the MS Office interface. Click the Help button on the
Teamcenter ribbon to see the Teamcenter help.
User feedback link on each topic

At the bottom of each topic in the Teamcenter HTML help collection, you see a
link where you can provide feedback about the documentation. Previously, this
functionality was offered by way of the Feedback icon in the help interface. Siemens
PLM Software will use your feedback to help improve the content we provide to you.
Access the PDF collection launch page

Teamcenter documentation deliverables have always been available in PDF form,
but Teamcenter 8 provides an online launch page into the set of individual PDF files.
1. The Teamcenter 8 documentation distribution media contains one ZIP file.
Extract this ZIP file to a directory on your hard disk.
2. In the directory where you extracted the file, open the PDF directory.
3. Open the index.htm file and the PDF collection launches.
4. Select the documentation deliverable you want to view to open the associated
PDF file.

Installing Teamcenter
The following are new Teamcenter installation features.
Teamcenter 8 software distributed in multiple ZIP files

Teamcenter 8 software distribution images can contain multiple ZIP files. For
example, the software distribution image for Windows consists of two files
named Tc8_win_1_of_2.zip and Tc8_win_2_of_2.zip. If you download software
distribution images for Teamcenter 8, 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.
For more information about installing Teamcenter 8, see the appropriate Teamcenter
installation guide (for Windows or UNIX/Linux).
Client support for Macintosh

The FMS client cache (FCC) is supported on Macintosh clients.
For more information about installing the FCC on Macintosh hosts, see the
Installation on UNIX, Linux, and Macintosh Clients Guide.
Note
Teamcenter 8 supports only 64-bit Intel Macintosh processors. G4 and G5
processors are not supported.
Rich client not supported on HP-UX platforms

Teamcenter 8 rich clients (two-tier and four-tier) are not supported on HP-UX
platforms.
For information about installing Teamcenter rich clients, see the appropriate
Teamcenter client installation guide (for Windows or UNIX/Linux).
TEM enforces required Oracle version

Teamcenter 8 does not support Oracle versions earlier than Oracle 10.2.0.1. If you
use Oracle as your RDBMS, Teamcenter Environment Manager (TEM) verifies your
Oracle version during installation. If your Oracle server does not meet the minimum
required version (10.2.0.1), TEM does not install Teamcenter 8.
For more information about installing a database server for Teamcenter 8, see the
appropriate Teamcenter installation guide (for Windows or UNIX/Linux).
For information about supported database servers for Teamcenter 8, see the Siemens
PLM Software certification database:

Teamcenter 8 application server, Web server, and browser support

Teamcenter supports new versions of application servers and browsers.
Teamcenter supports many of the latest versions of the most popular application
servers, Web servers, and Web browsers. For the latest supported versions, see
the information available on the Web at:
For information about deploying Teamcenter Web applications, see the Web
Application Deployment Guide.
Full-text search for Microsoft Office documents

The full-text search (FTS) feature in Teamcenter 8 uses the latest version (7.3.4)
of the Autonomy IDOL engine. This enhancement adds index and query support
for Microsoft Word 2007, Excel 2007, and PowerPoint 2007 files. These files
use extensions docx, xlsx, and pptx, respectively, and are represented within
Teamcenter as MSWordX, MSExcelX, and MSPowerPointX types.
For information about installing the full-text search feature, see the appropriate
Teamcenter server installation guide (for Windows or UNIX/Linux).
For information about upgrading the full-text search feature, see the Upgrade Guide.
Named user licensing

Teamcenter includes enhancements for the enforcement of named user licensing.
Named user licensing ties every user in the system to an available license and
ensures the total number of active authors and consumers in the system is always
less than or equal to the number of author/consumer licenses purchased.
There are two levels of Teamcenter user licenses that correspond to the different
roles within a company:
• Author is a user that creates or modifies data for product and process
information.
• Consumer is a user that views, approves, rejects, or comments on product and

process information.
For more information abut named user licensing, see the Upgrade Guide and the
Installation on Windows Servers Guide.

Configuring Teamcenter
The following are new features for configuring Teamcenter.
Business Modeler IDE

The Business Modeler IDE is a tool for configuring the Teamcenter data model.
The following are new and changed Business Modeler IDE features:
Item revision definition configuration (IRDC)
An item revision definition configuration (IRDC) defines how an item revision is

handled. IRDCs standardize item revision behavior at specific times in the life cycle,
such as at item creation, checkin, checkout, save as, and revise. Create an IRDC for
every item revision business object for which you want standardized behavior.
Administrators use the Business Modeler IDE to create IRDCs. In the Extensions
view of the Business Modeler IDE, open the Document Management→IRDC folders,
right-click the IRDC folder, and choose New IRDC.
For complete directions, see the Business Modeler IDE Guide.
For directions about how to work with document management and IRDCs in the rich
client, see the Rich Client Interface Guide.
Alternate ID enhancements
Alternate identifiers store information, such as part numbers and attributes, about
the same part from different perspectives. Alternate ID rules govern how alternate
IDs are assigned, and are created in the Business Modeler IDE.
Identifier functionality is improved in the following ways:
• An alternate ID rule tab is added to the Business Modeler IDE that displays all
of the rules that are defined for a given identifiable business object.
• The deprecated Alias functionality is removed.
• Discrepancies are corrected between the rich client and the thin client for
alternate ID functionality.
You can access the alternate ID rule tab in the Business Modeler IDE.
Note
The deprecated Alias business object functionality is removed and replaced
by alias ID rules. If you have ever used Alias business objects, you must
migrate Alias business objects to the new Identifier business objects before
upgrading to Teamcenter 8.
For more information about alias ID rules, see the Business Modeler IDE
Guide.

Building and packaging C++ customization code from the Business Modeler IDE
Previously, for each new business object and operation, the majority of code in the
C/C++ layer was standard boilerplate code that was written manually. There is now
a mechanism to autogenerate all the boilerplate code. Users of the Business Modeler
IDE can simply create operations on business objects, and the Business Modeler IDE
autogenerates boiler plate code. Users can concentrate on writing their business
logic implementations in the generated C/C++ files.
A new Code Generation folder in the Business Modeler IDE contains the following
data model elements that users can create or use:
• Data types
• Libraries
• Releases
• Services
You can access this feature in the Business Modeler IDE.

For more information about the C++ API, see the C++ API Reference, a new manual
that contains documentation of the auto-generated C++ API for Teamcenter. The C++
API Reference contains C++ API documentation for the Foundation template only.
C++ customization support
A new metamodel framework in Teamcenter supports C++ extensibility. This

framework provides the capability to define C++ interface/API for each business
object, paving the way for true object-oriented benefits such as inheritance as well as
overriding of operations. Existing code is refactored in Teamcenter 8 to conform to
the new framework. The refactoring does the following:
• Changes all the business object classes to fit into the new metamodel framework
paradigm
• Refactors standard operations (for example, create is refactored in Teamcenter 8;

save, save as, revise, and delete will be refactored in subsequent versions)
• Refactors accessors of properties
The code is located in the corresponding business object .hxx and .cxx files. To
create the code that uses the new framework, right-click a project in the Business
Modeler IDE and choose Generate Code.

More consistent business rules inheritance
Object-oriented inheritance of business rules is enhanced. Business rules are defined

in the Business Modeler IDE.
The inheritance behavior of the following business rules is enhanced:
• Generic relationship management (GRM) rules
• Deep copy rules
• Extension rules
• Compound property rules
The functionality provided by this feature can be found in several places in the
Business Modeler IDE user interface. For example, this feature provides a new
GRM Rules tab on business objects. To access the new GRM Rules tab, right-click
a business object in the Business Objects view, choose Open, and click the GRM
Rules tab. This feature also allows users to view GRM rules in the UML editor.
Right-click a business object and choose Open in UML Editor, then right-click the
business object in the UML editor and choose Show→Relations.
Services can be created using the Business Modeler IDE

You can create your own services and operations in the Business Modeler IDE. When
you define operations, you can activate extension points such as pre/post methods.
After you define a service, the boilerplate is generated automatically. The only task
remaining is to implement the behavior, and that is simplified by providing operation
outlines to start with. Once the service implementation is complete, you can start
the new operations from any service-oriented architecture (SOA) client.
You can access this feature in the Business Modeler IDE. For more information,
see the Business Modeler IDE Guide.

Deep copy enhancements
Deep copy rules define whether objects belonging to an item revision can be
copied when a user performs a save as or revise operation on an item revision. In
Teamcenter 8, deep copy rules are enhanced to support defining condition-based
rules, to propagate relations when the secondary side item revision is revised or
saved, and to revise automatically the related item revision objects.
You can configure deep copy rules in the Business Modeler IDE by right-clicking an
Item Revision business object, clicking Open, and choosing the Deep Copy Rules tab.
Prior to Teamcenter 8, some of the deep copy rules applied during the revise and
save as operations of an ItemRevision were hard coded. They are now exposed in
the Foundation template as explicit deep copy rules on the ItemRevision business
object. This allows you to override the default deep copy behavior. Previously,
the save as operation on an item object carried forward only certain relations of
the item revision. In Teamcenter 8, when a save as operation is performed on an
item object, the old item revision relations are carried forward based on the deep
copy rules in the database. Therefore, the deep copy rules in the database are the
deciding factor for copying relations even during save as operation on an item. One
exception is that when a deep copy rule specifies the Copy As Object action and
the other side object to be copied is an item revision, the system always performs
the Copy As Reference action.
Addition of conditions to Teamcenter
Conditions are statements that resolve to true or false. Conditions can be used
to evaluate business objects or user sessions to deliver only certain results. The
Teamcenter condition engine utilizes the CLIPS (C Language Integrated Production
System) external rules engine to process condition.
Business analysts add conditions using the Business Modeler IDE.
Exposing required and visible properties during item creation
Customers can create items to represent their company’s parts, documents, and
so on, and the properties on those objects. Using the CreateDescriptor tab in the
Business Modeler IDE, customers can make properties on items required as well as
visible on creation in the thin client and the rich client applications.
As a result of this feature, users are able to add and configure properties on items
such that they are auto-exposed in the creation dialog boxes in the rich client and
thin client without writing any code.

Enhanced naming rules
Naming rules are enhanced to support defining counters for more than one pattern.
Multiple patterns can have counters. Previously, counters could only be applied to
the first pattern in the naming rule. The Item create dialog box in the rich client
is enhanced to present the user with a list of patterns with defined counters in the
naming rule attached to the item_id property. The next item ID is generated per
the selected pattern in the list.
This feature can be used to define auto-numbering rules with multiple patterns for a
given object in the context of a program.
For more information, see the Business Modeler IDE Guide and Getting Started with
Aerospace and Defense.
Revision naming rules
Administrators can define revision naming rules with initial, secondary, and
supplemental revision formats typically used in the Aerospace and Defense industry.
The Item Revise dialog box in the rich client is enhanced to present the user with
the next set of revision options as specified in the revision naming rule attached to
the item_revision_id property.
Mapping Designer support for MapForce 2008
The Mapping Designer is an application that administrators use to map data model
from one product lifecycle management (PLM) system to another, for example,
Enterprise Knowledge Management to Teamcenter, or Teamcenter to Enterprise
Knowledge Management.
The Teamcenter Mapping Designer supports MapForce 2008 and the MapForce
2008 Eclipse plug-in.
For directions about how to install MapForce 2008, see the Business Modeler IDE
Guide.
For information about how to obtain a license for the 2008 version of MapForce,
contact Siemens PLM Software support at:
http://support.ugs.com

Administering Teamcenter
The following are new Teamcenter administration features.
User access logging

User access logging records information from failed authentication attempts for
named users, allowing administrators to analyze failed attempts.
The user_auth_audit command line utility configures (adds users to User Access
Logging tables) and extracts reports on failed authentication events.
For more information, see the Utilities Reference.
Store and forward files

New store and forward capability improves upload performance for remote users.
This File Management System (FMS) enhancement improves end-user file upload
times from clients by uploading files to a temporary volume. Users can continue to
work on their files from the temporary location. The system moves the files to its
final destination according to administer-defined criteria. Files are accessible to
FMS at all times.
Previously, if your site had users connecting to the main FMS volumes by a WAN,
current upload time while files were transferred across the WAN could be longer
than desired. Store and forward functionality allows you to define a default local
volume (an initial upload volume) for users or groups. When users upload files,
they are temporarily uploaded to the defined initial FMS volume, returning control
to the user in the client. In the background, the files are transferred to the final
destination volume. This allows you to place an FMS volume on the remote users
LAN, ensuring quick uploads into the FMS of this temporary volume. All file
transfers are transparent to end users.
Define the default local volume using the Organization application.
For information, see the Organization Guide.
Enable store and forward functionality by setting the TC_Store_and_Forward
site preference to true.
For more information, see the Preferences and Environment Variables Reference.
You can view the status of file transfers from the Request Administration Console.
For more information, see Getting Started with Dispatcher (Translation
Management).

Accessing multiple FMS databases through a single FCC

You can access multiple File Management System (FMS) databases through a single
FMS client cache (FCC). Teamcenter supports multiple installations on the same
machine to access multiple Teamcenter site IDs (databases).
For example, consider a part supplier with multiple customers, requiring access to
each customer’s PLM data, where the customers are in direct competition with each
other. The part supplier’s FCC loads configuration information from its local fcc.xml
file on startup. Its FCC also downloads configuration information from the primary
site. Using these two sources of configuration information, the FCC determines from
which customer FMS server caches (FSCs) to request additional site data.
To use this functionality:
• Configure either your fmsmaster.xml files or fcc.xml files to support multiple
databases by including valid configuration elements referencing at least one
parent FSC that supports each of the other databases to which the client may
connect.
For more information about configuration examples, see the System
Administration Guide.
• The proper multisite FCC client configuration must be present in the

FMS_HOME directory from which the FCC is started. Siemens PLM Software
recommends that you use a single FMS_HOME environment variable setting to
point to the combined configuration.
• FSC servers for all databases must be online, properly configured, of the proper
version, and functional.
For more information about accessing multiple FMS databases through a single
FCC, see the System Administration Guide.

Automatic FCC reconfiguration

FMS client caches (FCCs) now detect changes to the master configuration file. When
you reconfigure the master configuration file, the changes are propagated through
all necessary FMS server caches (FSCs), both masters and slaves. Then the FCC
detects the changes and attempts to reconfigure itself, without user interaction or
interruption of FCC client application service.
Note
Some FCCDefaults parameters still require manually restarting the FCC. If
the reconfiguration attempt fails, the traditional method of shutting down all
File Management System (FMS) applications and running fccstat –restart
updates these changes.
For more information about which parameters require a manual restart of the
No administrative interaction is required for automatic FCC reconfiguration. FCC

reconfiguration events are recorded in the FCC log file. The fccstat utility is stored
in the FMS_HOME/bin directory.
For more information about automatically reconfiguring the FCC, see the System
Manual FCC reconfiguration

The FMS client cache (FCC) now attempts to update its configuration file when you
run fccstat –reconfig. This method is useful for activating changes to the fcc.xml
file without shutting down Teamcenter or other FCC client applications, and without
stopping and restarting the FCC.
Note
Some FCCDefaults parameters still require manually restarting the FCC. If
the reconfiguration attempt fails, the traditional method of shutting down all
File Management System (FMS) applications and running fccstat —restart
updates these changes.
For more information about which parameters require a manual restart of the
The fcc.xml file is located in the FMS_HOME directory. The fccstat utility is stored
in the FMS_HOME/bin directory.
For more information about manually reconfiguring the FCC, see the System

Performing hot backup

Teamcenter’s integrated backup and recovery functionality allows you to use
third-party backup systems to perform hot backups, enabling Teamcenter to operate
continually in a 24x7 environment. Use this functionality to back up and/or restore
metadata and math data.
During hot backup, third-party backup systems require the Teamcenter file
system (volumes) and the Teamcenter database to be synchronized. Run the
backup_modes utility in read-only mode to synchronize the volumes and database.
Use the optional blobby-volume mode to define an alternate data BLOB that can
store in-process data until production volumes are backed up. Use normal mode to
restore Teamcenter to normal, write access, mode.
Note
The backup and recovery functionality has been available since Teamcenter
Engineering 8.0; however, architectural changes to File Management System
(FMS) functionality in Teamcenter 2005 disabled hot backup capability,
preventing the FMS server cache (FSC) process from switching to read-only
mode. This behavior is corrected in Teamcenter 2007.1 MP3.
The –f=move, –f=remove, –m=caution, –f=allcnt and –force arguments are

removed from the backup_modes utility. This functionality is now performed
through FMS.
For more information about this utility, see the Utilities Reference.
Set the Tc_set_tcfsModes preference to TRUE to enable backup mode functionality.
For more information about this preference, see the Preferences and Environment
Additionally, the blobbyVolume_NT preference and the blobbyVolume_UNX
preference are modified. The preferences are stored only in the tc_preferences.xml
file. They are no longer also stored in the tcfs_preferences.xml file, therefore, the
preference values do not need to be synchronized between the two XML files. The
valid value for these preferences is a single string specifying the alternate volume
location. The maximum character length of this string is increased from 15 to 32
characters.
For more information about these two preferences, see the Preferences and
Environment Variables Reference.

Locking site preferences

You can lock site preferences before modifying them. To ensure multiple site
administrators do not make simultaneous changes to site preferences (overwriting
each others settings) a Lock and Unlock button has been added to the Options
dialog box, allowing you to lock site preferences before modification.
To lock site preferences, click Edit→Options to access the dialog box. The lock
buttons appear on the Index and Search tabs of the dialog box.
For more information about locking site preferences, see Getting Started with
Teamcenter.
Shared memory for site preferences

Shared memory for site preferences is available in a four-tier configuration. This
functionality is implemented by default.
This shared memory functionality connects all Teamcenter servers for a particular
version to the shared memory created by the first Teamcenter server. A backing
store file is created with a .mem extension. The backing store file contains data
for preferences definitions, site preference off-the-shelf values, and site preference
overlay values. If the file is deleted, another is automatically created by the next
Teamcenter server process. The backing store file is stored in the TC_TMP_DIR/
TC_VERSION_STRING/db_siteID/Preferences directory.
When using a four-tier configuration, changes to site preferences for four-tier
configuration immediately affect all existing Teamcenter server processes on a host.
Note
When changes are made from a different host using the same database, the
changes are updated on that host, but not on the first host. The next new
Teamcenter server processes begun on the first host updates the shared
memory segment and the changes affect all the processes on that host.
For more information about shared memory for site preferences, see the System

Rendition and translation capabilities

Rendition and translation capabilities are available for Document Revision and
Dataset objects in Teamcenter. Microsoft Office dataset types such as MSWord,
MSExcel, MSPowerPoint and MSProject can be translated to a variety of other
derived visualization file formats such as Adobe Postscript, Adobe PDF, and TIF.
The translation is configurable to trigger by events, workflow steps or user action.
Note
In Teamcenter, you render the item revision, but you translate the dataset.
Microsoft Office dataset types are usually attached to an item revision such as a
Document Revision object. When the Document Revision is selected for rendering,
the file associated to its attached dataset is translated.
• The desired translated output file format, also called the derived dataset, is
specified by the item revision definition configuration (IRDC) object associated
with the item type.
• The IRDC can also specify event-driven rendition such as rendition on checkin.
• A Dispatcher service configuration determines the Translator service based on

the input file format and desired translated output file format.
When you select a dataset to translate on-demand, the file associated with the
dataset is translated. The translated file format is determined by the Dispatcher
translation service you select.
For information about configuration required to enable dataset translation services,
see Getting Started with Dispatcher (Translation Management).
• The Dispatcher Server (formerly called Translation Services Tool Kit, or TSTK)
provides the translation framework to manage the translate request (submit,
delete, resubmit, and so on), moving files to and from the translation server.
• The Dispatcher Client (formerly Translation Service) also manages the

translated file such as moving files from the translation server to the Teamcenter
volume and creating the relationship between the Document Revision or the
source dataset in Teamcenter.
For more information about Dispatcher, see Getting Started with Dispatcher
(Translation Management).
The Business Modeler IDE lets the administrator create, modify, and deploy the
Dispatcher service configuration and IRDC objects.
• For information about creating IRDC objects, see the Business Modeler IDE
Guide.
• For information about Dispatcher service configuration, see the Business

Modeler IDE Guide.
For information about working with document management and IRDCs in the rich
client, see the Rich Client Interface Guide.

Site definition improvements

Teamcenter 8 adds and updates the site definition pane used to define a site to
clarify the use of the information as it applies to RPC or HTTP enabled sites. The
site definition pane includes the following new or updated boxes:
• Site Node
Stores the node value Multi-Site Collaboration uses for remote calls in RPC
mode. Prior to Teamcenter 8, this field stored the node name as well as the
URL for SOA calls based on whether this site was used for standard Multi-Site
Collaboration or HTTP enabled Multi-Site.
• SOA URL
Stores the URL for SOA calls to this site. The URL is used for HTTP enabled
Multi-Site as well as other SOA calls to the site using HTTP.
• TcGS URL
Stores the Global Services endpoint for use by Data Exchange.
Additionally, selecting the Allow deletion of replicated master objects to this site
check box allows master objects which have been replicated to the site to be deleted
even if there is a replica existing for the master object at the site.
The site_util utility includes the gms_url argument that sets the URL for Global
Services (equivalent to the TcGS URL box in the site definition pane).
For information about defining sites, see the Organization Guide.

Validation rule and run validation and view results

Users can summarize validation results and evaluate compound results status based
on the validation rule set.
The Validation Manager administrative user (Teamcenter user with Validation
Manager administrator’s role) can perform validation rule set management tasks
including:
• Create
• Modify
• Delete rule set and rules
The Validation Manager user can start validation with the enhanced capabilities
of selecting items, item revisions, folders, dataset types, and checkers as well as
validation rule sets. The Validation Manager utility is started from the rich client so
the user can monitor when the process finishes. The View Result pane is enhanced
with features to allow the user to evaluate the validation results based on validation
rule set and a button to revalidate out-of-date checks.
Results are rendered in more readable style with icons to show pass or fail status,
out-of-date or up-to-date status, and whether the evaluation passed or failed. The
Validation Manager administrator’s role is added and can be deployed during
installation or upgrade. Users with the administrator’s role can perform validation
data and validation rule set management tasks. A simple and straightforward
message is shown from workflow or baseline operations to inform the user which
parts failed which checks and for what reason. The EPM_check_RDDV_results
workflow rule handler checks RDDV results and returns EPM_go if compound result
status is pass (up-to-date and pass). Otherwise, the handler returns EPM_nogo.
For information about validation rule and run validation and view results, see the
Validation Manager Guide.

Enhancements to export to Excel

Teamcenter provides templates for exporting object data to Microsoft Office Excel.
These enhancements allow the user to customize each export operation by choosing
an Excel template to associate with the objects. The data specified in the template is
extracted from the Teamcenter database to a new Excel spreadsheet.
Note
The user can choose to export the data in the property columns that are
currently displayed in the view. A template is not associated with this
operation.
An Excel export template determines:
• The property values that are exported to the spreadsheet.
• Rules that filter the data according to specific criteria.
• The placement of the exported data in the spreadsheet.
A template can also define the spreadsheet’s overall layout, the formatting that is
applied to the data, and boilerplate text and graphics. Also, a template can contain
Visual Basic macros that users can run from the generated spreadsheet.
A default template is provided. The Teamcenter administrator can modify the
default template and can create custom templates.
Note
• Users can choose Excel templates when exporting data from both the rich
client and the thin client.
• Administrative actions in configuring export templates, such as creating,

importing, modifying, copying, and deleting templates, can be done only in
the rich client.
• The OpenXML file format is supported. Templates can have the .xlsx or
.xlsm file type.
The spreadsheet is generated in the Excel 2007 .xlsm format. One of the following
must be installed on the user’s computer:
• Microsoft Office Excel 2007
• Microsoft Office Excel 2003 with the Compatibility Pack for the Word, Excel, and
PowerPoint 2007 file formats
For more information about exporting objects to a new live Excel file, see the
Extensions for Microsoft Office Guide.
For more information about configuring export templates, see the Application

Templates for document export

Export template functionality supports exporting Teamcenter object data to
Microsoft Office Word.
Export templates let the administrator customize the export process using two
template types:
• A specification export template determines which objects to export, their
structure in the document, and the formatting that is applied to the objects.
This template can also contain layout elements such as a title page, a table
of contents, and headers and footers.
• An object export template determines the properties that are exported for the
objects. This template can also contain standard text, or boilerplate, in which
property values can be inserted.
The administrator can create, import, modify, copy, and delete templates. These
administrative actions on templates are performed in My Teamcenter in the
Teamcenter rich client. Administrators can create use the Business Modeler IDE
to create item revision definition configuration (IRDC) objects. Then IRDC objects
can associate default templates with the following Specification and Specification
element business objects and their subtypes. In a given export operation, the user
can select a different set of templates to override IRDC associations.
For more information about configuring export templates, see the Application

Content Management administration

Content Management is a single-source publishing application used to create
technical documentation using SGML and XML information stored in a Teamcenter
database.
The Content Management rich client provides both the Content and Administration
perspectives, which are used for authoring and administrative tasks respectively.
The Administration perspective enables you to create the following so that the
application can be used for authoring publications:
• Schema objects. You can create your own schemas or DTDs or use the S1000D
standard, which is an optional component of Content Management.
• Topic and publication types and publication structures, which are related to
schemas.
• XML attribute mappings to facilitate the transfer of topic attributes from the
database to XML instances.
• Style types and stylesheets to define formatting for each type of output.
• Editing and publishing tool objects to support installed applications for editing,
publishing, comparing, and viewing tools and control tool launch and selection
by the user.
• Translation objects necessary to manage the translations of publications and

topics.
• Graphic priority lists used to determine the priority with which graphic options
or formats are selected for use with XML content when it is opened with an
editing application or rendered by a publishing application.
• Other objects, including procedures, composition policy tables, transformation

policies, and graphic attribute mappings.
Sample files are provided for these objects and also for some sample
content. You can use these files as a guide for creating your own objects.
These object files and instructions for importing them are located in the
...\TC_ROOT\contmgmtbase_data and ...\TC_ROOT\contmgmts1000d_data
directories.
For more information, see the Content Management Administration Guide.

Security Services WebSEAL proxy support

WebSEAL processes form-based challenges for Teamcenter clients and provides
clients with an authorized WebSEAL session cookie. This allows the client to
continue operations without processing additional form-based authentication
challenges from WebSEAL.
Security Services shares its authorized WebSEAL junction cookie with client-side
Teamcenter applications that are facing a form-based authentication challenge from
WebSEAL. Providing the authenticated WebSEAL session cookie from the Security
Services session allows the Teamcenter application to share the authorization in the
session without further authentication challenge.
If Security Services does not presently hold an authorized WebSEAL junction cookie,
Security Services launches a Web browser in which the end user responds directly to
the WebSEAL form-based authentication challenge. After authentication, Security
Services is provisioned with an authorized WebSEAL session cookie.
This feature only works with the WebSEAL forms authentication mechanism and
the following global WebSEAL stanzas declarations:
ssl-id-sessions=no
tcp-session-cookie-name=PD-H-SESSION
ssl-session-cookie-name=PD-S-SESSION
In addition, the WebSEAL junction protecting the Security Services Login Service
must be configured to pass the WebSEAL session cookie the Security Services
Login Service servlet.
Note
The Integration for CATIA 6.7.2 and Integration for Pro/ENGINEER 5.7.3
are supported with WebSEAL. Support for other CAD integrations will be
added based on market demand.
For more information, see the Security Services Installation/Customization manual.

File Management System (FMS) WebSEAL proxy support

FMS can be deployed with FSC servers in the corporate backoffice behind a
WebSEAL proxy server with FMS clients in the field at service offices or at supplier
offices.
FMS clients automatically detect and respond to forms authentication challenges
from the WebSEAL proxy, provide the required WebSEAL session cookie, and
maintain the network connections to the backoffice FSC server. The FMS clients
that support this feature are Java based interactive clients such as the Java FCC
and the UploadApplet (Web client).
This feature only works with the WebSEAL forms authentication mechanism.
FMS clients interoperate with the Security Services integration to share required
WebSEAL session cookies that maintain the connection through WebSEAL to
backend FSC servers. This feature utilizes WebSEAL forms authentication to
negotiate credentials authentication. After a Teamcenter application on the user’s
workstation negotiates the WebSEAL authentication, the follow-on Teamcenter
applications can share the session authorization cookies.

File Management System (FMS) URL path extensions

FMS clients and server applications use path extensions on all URL addresses in
HTTP messages.
FMS provides path extensions to simplify configuration of reverse proxies to properly
route FMS traffic to backend FMS server caches (FSCs).
The original FMS URL contextless form (protocol://host:port) only provided the host
name, address, and listening port number.
The new URL form consists of a standard URL path based on FMS configuration
values, such as fmsenterpriseid, fscgroupid, and fscid. This additional path
information provides reverse proxy servers an easy method of mapping to FSCs
behind the firewall based on the incoming FMS URL path. These maps are explicitly
configured within the reverse proxy server.
The FMS URL path extensions are enabled and sent on all FMS request messages.
• Contextless form
protocol:host:port
This form can be used in configuration files and preferences, but it is not suitable
for use with reverse proxies.
• Site context form

protocol://host[:port]/tc/fms/fmsenterpriseid
This form is used to configure FMS bootstrap references. It should be used in
reverse proxy mapping tables and other bootstrap configuration points.
• FSC context form

protocol://host[:port]/tc/fms/fmsenterpriseid/fscgroup/]fscid|lbid] [/connid]
This form is used for all FMS-generated traffic and is generally used internally
by the system. Administrators should not have to manage FMS URLs that are
this specific, but it is an option if finer control is required.
FMS server cache (FSC) SSL client credentials (two-way SSL)

The FSC SSL client sets up the HTTPS listener on a specified FSC to require
two-way authentication. This ensures that only clients with certificates that can be
authorized by the FSC servers can connect.
Two-way SSL protects an FSC connection by only allowing clients that are configured
with known certificates to connect. Purchased or self-signed certificates can be used.
In a two-way SSL configuration, both the client and the server provide certificates to
each other. This provides symmetric authentication between the FSCs and ensures
that only FSCs that are configured with appropriate certificates can communicate
with each other. All other connection requests are denied.

Using Teamcenter interfaces

The following are new features for Teamcenter interfaces.
Vendor management enhancements

Teamcenter vendor management functionality is enhanced to include support for:
• Managing company locations and contacts.
• Displaying vendor parts in product structures according to rules, including

support for BOM compare to view changes to vendor part relations
• Creating configurable business rules for vendor management actions.
• Changing a vendor for a vendor part.
• Classification of commercial and vendor parts.
For more information about vendor management functionality, see the Rich Client
Interface Guide and the Thin Client Interface Guide.
For more information about viewing vendor parts associated with commercial parts
in the context of a product structure, see the Structure Manager Guide.
Requirements in thin client

Requirements Manager is available in thin client. This new functionality means
the user can:
• Import and export documents.
• Launch the Microsoft Word client for viewing and editing requirement structure.
• Generate trace reports (similar to existing where used functionality).
• Create trace links.
For more information about Requirements Manager, see the Requirements Manager
Guide.

Teamcenter rich client perspectives and views

Within the Teamcenter rich client user interface, functionality is provided
in perspectives and views. Use perspectives and views to rearrange how the
functionality is presented.
Perspectives Are containers for a set of views and editors that exist within the
perspective.
• A perspective exists in a window along with any number of
other perspectives, but only one perspective can be displayed
at a time.
• You can add and rearrange views to display multiple sets of

information simultaneously within a perspective.
• You can save a rearranged perspective with the current name,

or create a new perspective by saving the new arrangement of
views with a new name.
Views Enable you to navigate a hierarchy of information, display

information about selected objects, open an editor, or display
properties.
• Views that work with related information typically react to
selection changes in other views.
• Changes to data made in a view can be saved immediately.
• Any view can be opened in any perspective, and any

combination of views can be saved in a current perspective
or in a new perspective.
Note
If your site has online help installed, you can access application and view
help from the rich client Help menu or by pressing F1. Some views, such as
Communication Monitor, Print Object, Outline, Palette, and Progress, are
not specifically associated with a particular perspective.
For additional information about unassociated views, see the Rich Client
Customization Programmer’s Guide.
For more information about perspectives and views and changing the layout of your
rich client window, see the Rich Client Interface Guide.

My Teamcenter functionality refactored

The functionality for finding, creating, and viewing data in the rich client is
supported by perspectives and views, with each application consisting of a single
perspective that by default displays one or more views:
• The My Teamcenter application lets you navigate, browse, and work with your
data in Summary, Details, Impact Analysis, and Viewer views.
• The Relation Browser application lets you navigate through the relations on an
object in terms of predecessors and successors in a hierarchy. The default views
provided by the Relation Browser perspective include the Relation Browser
view, the Image Thumbnail Preview view, the Graph Overview view, and the
Properties view.
• The My Teamcenter (2007) application, which is deprecated in the current

release, is available to support prior customizations in the current release.
The My Teamcenter (2007) application displays by default the My Teamcenter
(2007) view within which you can access the Folders, Summary, Details, Viewer,
Referencers, and Display Data panes.
• Search in the rich client is supported by the Search view and the Search Results
view in all perspectives except the My Teamcenter (2007) perspective.
Note
The My Teamcenter Guide from previous versions is now the Rich Client
Interface Guide. This guide has been expanded to describe both the
My Teamcenter and My Teamcenter (2007) perspectives, as well as the
Relation Browser application perspective, and a broad range of features and
functionality available in these contexts.
For additional information about using the My Teamcenter, Relation Browser, and
My Teamcenter (2007) application perspectives, see the Rich Client Interface Guide.
Rich client search

For the new Search view in the rich client and for searches in the thin client:
• A progress dialog is displayed for queries that take longer than one second.
• For metadata-only queries, a Cancel button is displayed on the progress dialog.
For information about using search in the rich client, see the Rich Client Interface
Guide.
For information about using search in the thin client, see the Thin Client Interface
Guide.
Note
Search in My Teamcenter (2007) does not display a progress dialog and does
not support cancel functionality.

Search for items by owning organization

You can search for items based on the owning organization in My Teamcenter. The
Owning Organization ID option is added to the Item search form. Your current
organization ID is displayed in the text box.
For more information about performing searches, see the Rich Client Interface Guide.
Multilanguage support for clients

Teamcenter allows users to choose the locale on their clients, regardless of the
locale used by the Teamcenter server pool manager. The only constraints are that
requested locales are properly installed on the server side (which may not be true
for customized locales), and that the server side system can cope with the locale
encoding (the locale is supported by the encoding on the server machine and the
locale is compatible with the encoding of the database.)
Note
In Teamcenter 2007, localization was desynchronized between all tiers. Client,
middle-tier, and server could each use a different locale; the locale of the
machine where the rich client was running, the locale defined at middle-tier
installation, and the server locale specified by the TC_language_default
environment variable located in the tc_profilevars file. All processes in a
pool manager used the same tc_profilevars file, and therefore the same
language. Therefore, in a globally distributed enterprise with one pool
manager running on a server machine located in country A with locale L_A,
all Teamcenter server processes spawned from the pool manager ran with
locale L_A. Therefore, all client connections were served with only locale L_A.
This feature is enabled by default. Administrators can modify the way multilanguage
operates using the TC_language_default preference to define the default locale
the Teamcenter server uses when clients connect without a specified locale. This
situation can occur on thin client, or SOA clients other than the rich client.
Administrators can use the TC_language_data_entry preference to define the
list of locales in which users may input data entries. The value of this preference
is left empty by default. If no value is entered, a warning message displays after a
user logs into rich client or thin client when the requested locale conflicts with the
database encoding. (This conflict could result in loss of data if the data is entered in
the wrong locale.) If values have been entered, a warning message always displays
after a user logs into rich client or thin client, stating that data must be entered
using the specified locales.
Users can define their language choice from both the rich client and thin client:
• From the rich client, users can define their language choice in the Teamcenter 8
Properties dialog box.
For more information, see the Rich Client Interface Guide.
• From the thin client, users can define their language choice either in the
browser’s URL, or by modifying the preferred language setting for their browser.
For more information, see the Thin Client Interface Guide.

Thin client on Macintosh

Macintosh is supported in the thin client interface.
The following features are not supported on Macintosh systems:
• Process viewer
• Supercedure viewer
• Reports
• Teamcenter’s Integration for Microsoft Office
For information about the thin client interface on Macintosh, see the Thin Client
Interface Guide.
Microsoft Office client

Teamcenter’s Client for Microsoft Office is embedded in Microsoft Office applications
and is independent of the Teamcenter rich client and thin client. Client for Office
consists of specialized Teamcenter views in Office applications. Users can display
the views by clicking buttons on the Teamcenter ribbon. Client for Office gives users
access to Teamcenter directly from Word, Excel, PowerPoint, and Outlook. Users can
navigate Teamcenter, display and insert Teamcenter data, and interact with that
data without running a Teamcenter client.
For example, Client for Office provides features such as the following:
• Browse the user’s Teamcenter Home folder and worklist.
• Perform Teamcenter sign-offs, delete tasks, and select sign-off teams.
• Create new processes to place selected objects into the Teamcenter workflow.
• Perform simple and advanced searches and execute saved search queries.
• Display objects hierarchically for viewing and selection.
• Check in and check out objects and view checkout history.
• View the properties of a Teamcenter object.
• Create and edit folders, items, item revisions, and datasets.
• In Office documents, insert Teamcenter data, graphics, JT files, and embed other
Office documents.
• In Outlook, save e-mail to Teamcenter and compose Outlook messages containing

Teamcenter data.

Client for Office can be installed with the four-tier Teamcenter rich client or
separately as an add-in. Prerequisites are the following:
• Microsoft Office 2007
• Microsoft Office 2007 Primary Interop Assemblies (PIAs)

Microsoft Office provides a downloadable, redistributable package of the
primary interop assemblies that does not require access to the Microsoft Office
installation media.
• Microsoft .NET Framework 3.5
• Microsoft Visual Studio 2008, Tools for Office runtime, and Tools for the
Microsoft Office System Language Package
• Teamcenter FMS client cache (FCC)
To install the prerequisite applications, the installing user must have administrative
access to the local computer. Administrative access is not required to install the
embedded client add-in.
For more information about Client for Office, see the Client for Microsoft Office Guide.
Enhancements to Organization and Portfolio, Program and Project

Management allow you to find users or projects more quickly
Search fields are added to the Organization application (for selecting from existing
users and groups) and the Portfolio, Program and Project Management application
(for selecting from existing projects). Wildcard values are valid.
For more information about the Organization User wizard, see the Organization
Guide.
For more information about the Organization Group wizard, see the Organization
Guide.
For more information about searching for existing projects, see the Project Guide.

Managing changes and workflows

The following are new Change Viewer and Workflow features.
Workflow participants
You can assign participants to an item revision or engineering change revision and
configure workflow handlers to use those participants when you initiate a workflow
process on the revision. You can also easily select specific members, all members, or
any member of a group. To select the participants to attach to an item revision or
engineering change revision, choose the Tools→Assign Participants menu command.
In addition, you can search by users, groups, and roles in the following dialog boxes:
• Assign Participants
• Assign Responsible Party
• Delegate Signoff
• Select Signoff Team
For more information about assigning participants, see the Rich Client Interface
Guide or the Thin Client Interface Guide.
The following workflow handlers are modified to use participants:
• adhoc-signoffs
Supports the –assignee argument and modifies the –quorum argument to
accept values other than fixed numbers.
• auto-assign
Assigns the single responsible_party attribute for a single assignee task. If
given $PROPOSED_RESPONSIBLE_PARTY as an argument, the handler
assigns the user specified for Participants Responsible Party as the
responsible party.
• auto-assign-rest
Modified to have the same incremental behavior as the auto-assign handler
and to support the new –assignee argument.
• CR-assign-team-selector
Modified to have the same incremental behavior as the auto-assign handler
and to support the new –assignee argument.
• CR-fill-in-reviewers
Modified to support the new –assignee argument.

• CR-notify
Modified to support TcProject related keywords.
• EPM-check-related-objects
Modified to process keywords.
• EPM-check-related-objects
Modified to process only the first target of the specified type.
• EPM-check-object-properties
Modified to process only the first target of the specified type.
• EPM-create-sub-process
Modified the following arguments to process assemblies and related objects:
–process_assembly, –depth, –rev_rule, –relation, –include_related_types,
and –exclude_related_types.
For more information about these handlers, see the Workflow Designer Guide.

Failure paths
A failure path is an alternate course that a workflow process can follow in any of
the following scenarios:
• A task is rejected.
• The user determines that the task cannot be completed.
• There is an error.
You can configure failure paths on the following tasks:

• Do task
• Interactive EPM tasks (including form tasks)
• Legacy Change Management tasks, including Checklist, Impact Analysis, and

Prepare ECO tasks
• Manual Condition task
• Review task
• Route task
• Validate task
You do not have to configure failure paths. However, if you configure failure paths in
the process template, it must be done at design time.
When you create a workflow, you can configure each path as either a success path or
a failure path. A task follows the appropriate path based on the task outcome. The
success path is followed when the task state transitions to Complete or when a task
is promoted and it transitions to a Skipped state. A task is Complete when the
task’s handlers on the Complete action successfully execute.
You can branch success and failure paths back to a previous task in the process flow,
including the Start node, and restart a task with a Complete or Skipped task state.
The following additional features are included in Workflow:
• Validate task
Branches the workflow if an error occurs. You can set the task to branch for all
errors or for specified errors. If no error occurs, the process follows the success
path.
• Failed state
Indicates a task has failed if any of the following occurs:
– A Review task is rejected.
– A Route task is rejected.

Note
When a child Review task is rejected, its parent Route task state
is also set to Fail.
– A Do task is marked as Unable-to-Complete.
– One of the legacy Change Management tasks (Checklist, Impact Analysis,

or Prepare ECO task) is marked as Unable-to-Complete.
– An interactive EPM task (including form tasks) is marked as

Unable-to-Complete.
– A manual Condition task is marked as Unable-to-Complete.
– A Validate task encounters an error that the task has been configured to
recognize.
• Condition task improvements

Executes its query either against a target in a workflow or against a task.
You can also configure a Condition task to branch on a custom result set by the
user, allowing branching on an arbitrary number of results. The result entered
by the user is displayed on the Condition path line as a string label, indicating
that the line has been configured as a custom path.
• EPM-set-task-result-to-property handler
Reads either a task or target property and uses that value to set the result
attribute of the Condition task. This handler sets the results used by the
process to decide which paths to follow. There is no limit to the number of
condition paths that can be configured when used in conjunction with the
EPM-set-task-result-to-property handler.
• Wait For Undecided Reviewers option on Review tasks

Stops a process until all reviewers have submitted their decisions and comments,
regardless of the decision type. Reviewers can also change their decision, which
might affect the path taken after the task completes.
• Percentage of reviewers quorum option

Permits a quorum value on Review and Route tasks to be either a specified
percentage of reviewers or a specific number of reviewers.
• Comment boxes in Workflow Viewer

Permits comments to be added to the following tasks in Workflow Viewer:
– Do task
– Interactive EPM tasks (including Change Management tasks)
– select-signoff-team task
– Manual Condition task

For more information, see the Workflow Designer Guide or the Workflow Viewer
Guide.
Classifying data
The following are new Classification application features.
Multi-unit support in Classification

When creating classification classes, you can define whether a class contains only
metric objects, only nonmetric objects, or both. If you specify that a class can contain
both, you can search for an object using either of the unit systems you have defined,
and the search mechanism finds a match, regardless of the unit in which the
object is stored. For example, if you search for a bolt with a width of 5/8th inches,
the classification search mechanism finds a bolt that is stored with a width of 1.6
centimeters.
Specify whether a class supports multiple units of measurement in the class details
pane in Classification Administration.
Enter attributes in multiple units or search for attribute values of differing units in
the Classification application.
For more information, see the Classification Administration Guide and the
Classification Guide.

Managing documents, reports, requirements, and schedules

The following are new Teamcenter features for reports, requirements, and schedules.
Requirements integration
Users can create a tracelink from a requirement in Requirements Manager to a
scheduled task in Schedule Manager. When the task completes, a workflow is
triggered to get approval of a signoff team. Users can also check the status on the
target requirement in Requirements Manager.
For more information, see the Schedule Manager Guide.
Create reports from saved queries

Users of the Report Builder application can define summary report templates that
work on saved query objects. PLM XML closure rules are used for the processing
of the saved query objects. For summary reports, a Closure Rule box and a Report
Format box are added to the Create Report Definition Template dialog box. A Report
Format box is added to the item report creation dialog box.
For more information, see the Report Builder Guide.
Scheduling templates and deliverables enhancements

Users can create a schedule template and insert other schedule templates as
sub schedule templates into this schedule template. The new schedule template
becomes a master schedule template and the inserted schedule templates become
sub schedule templates. The first user to start working on a task (where there is
more than one resource assigned) becomes a privileged user. Users can search and
attach any PLM item as a deliverable. The user can also search for particular items
and attach them as a target deliverable or reference.
Scheduling extensions
Users can create a schedule and insert other schedule as subschedules into this
schedule. The new schedule becomes the master schedule and the inserted schedules
become subschedules. When creating a master schedule, a user can import other
schedules as subschedules.
Functionality such as copy/paste, baseline, dependencies, and assignments is
included. Schedule membership in the master schedule includes all membership in
subschedules.
Using Business Modeler IDE, sites can extend schedule and task attributes to add
custom attributes and support all operations that are available to items. Managers
can assign fixed costs and resource costs to tasks and schedules.

Scheduling enhancements
Enhancements in scheduling allow task ranges to be defined in minutes.
Dependencies and constraints follow minute boundaries instead of day boundaries.
In addition, Schedule Manager supports multiple time zones so different schedules
and users calendars can interpret the time of day relative to the correct time zone.
Baselines for requirements management

Requirements Manager incorporates the baseline and structure comparison features
of Structure Manager. Requirements Manager users can:
• Create baselines of requirements and requirement structures.

In the Baseline dialog box, users can enter the name of the baseline folder in
the Baseline Label box.
• Compare structures to identify differences.
Requirements Manager must be configured to use the baseline features.

For more information about using baselines, see the Structure Manager Guide.
For more information about comparing structures, see the Structure Manager Guide.
For more information about configuring baseline features in Requirements Manager,
see the Requirements Manager Guide.
Enhancements to document generation

Exporting objects to Microsoft Office Word is extended to provide database
connectivity for exported documents.
This feature lets you change object property values in the database by editing those
values in the document. Changes are applied in the database when you save the
edits in the Word document.
For each export operation, you choose two templates to associate with the data:
• A specification export template determines which objects to export, their

structure in the document, and the formatting applied to the objects. This
template can also contain layout elements such as a title page, a table of
contents, and headers and footers.
• An object export template determines the properties that are exported for the
objects. This template can also contain standard text, or boilerplate, in which
properties can be inserted.
For more information about exporting objects to Microsoft Office Word, see the
Requirements Manager Guide.

Content Management
Content Management is a single-source publishing application used to create
technical documentation using SGML and XML information stored in the
Teamcenter database.
Source is separated into content, structure, and format, so content may be used in
many publications with different structures and media deliverables. The publication
structures are validated by structure rules called schemas or DTDs. Content
Management supports many types of schemas, including the S1000D standard, an
optional component of Content Management. The publication layout is implemented
with stylesheets, which allows the same content to be available for different media
such as print or Web applications.
Publications are created by composing small subsets of information called data
modules or topics. These may be maintained by the author or other participants in
the product creation process. The content data module or topic may be as small as
necessary for optimum reuse in other publications. They are related to each other
based on the schema or DTD, which is similar to the table of contents of a book or
an online help navigation tree.
Topic and data module relationships may be created and updated in the Content
Management interface or within an XML/SGML editing tool. Content Management
works with these editing tools: Altova XMLSpy, Arbortext Epic Editor, structured
FrameMaker, and XMetaL Author.
Additional features of Content Management enable you to:
• Integrate workflows.
• Track publication versions.
• Incorporate graphics into publications from the Teamcenter database. Each

graphic may be stored in different formats to use for different types of output.
• Manage multiple language versions of publications at the level of the data

module or topic, to reduce translation costs.
The Content Management rich client provides both the Content and Administration
perspectives, which are used for authoring and administrative tasks respectively.
The Content perspective contains multiple views that can be rearranged, including
content and graphics previews, a query browser for searching the database, current
workspace, structure expansion and editing, a local graphics cache, and object status
information. The Content perspective offers the following capabilities:
• Creation of publications and publication variants
• Use of publication and content templates
• Rendering by use of standard publishing engines
• Access to workflow and release processes
• Import and export of contents
For more information, see the Content Management Guide.

Sharing data
The following are new data sharing features.
PLM XML software development kit version upgraded

Teamcenter 8 uses the PLM XML software development kit (SDK) version 7.0.0.42.
This occurs automatically and requires no action on your part.
For more information about the PLM XML SDK, see the http://www.plmxml.org
Web site.
PLM XML performance improvements

You can improve the performance of your PLM XML exports by setting the following
preference:
• PLMXML_export_packed_bom_<transfer-mode-name>
If you set this preference to TRUE, it improves the PLM XML export
performance for the specified transfer mode. But if you export a packed BOM,
you may lose data in the exported XML file. Therefore, do not import an XML
file with a packed BOM into Teamcenter. Set this preference to TRUE only if
you plan to use the XML file in a third-party application.
For more information about this preference, see the Preferences and Environment
Backward compatible schema mapping for extended attributes

Teamcenter 8 introduces a new storage class for each subtype. Multi-Site
Collaboration maps item attributes between Teamcenter 8 and the following
Teamcenter product version to allow them to exchange data:
• Teamcenter 2007
• Teamcenter Engineering 2007
• Teamcenter Engineering 2005 SR1
Attribute mapping between Teamcenter systems is based on the class and its
subtype (subclasses). Any customizations related to attributes in the master forms
for the earlier Teamcenter product are not imported as the attributes for the main
class in Teamcenter 8.
For information about sharing data between Teamcenter product versions, see the
Multi-Site Collaboration Guide.

Global Services Data Exchange solution application server support

The Teamcenter 8 Global Services – Data Exchange Web application solution can be
deployed on the following application servers:
• JBoss
• WebSphere
• WebLogic
For information about versions of application servers certified for the Teamcenter 8
Global Services – Data Exchange Web application solution, see the Siemens PLM
Software Certification Database:
To use the certification database, choose the platform you use and Teamcenter 8, and
then click Show Certifications.
For information about Teamcenter 8 Global Services – Data Exchange, see the Data
Exchange Guide.
Global Services SOA connection pooling

Global Services supports an option for connectivity through the Global Services
SOA Connector using pooled connections. Connection pooling reuses TcServer
instances across multiple sessions run by the same named user. This option allow
faster performance and better scalability in situations where a single user is running
multiple Global Services sessions. This approach is especially valuable for Data
Exchange environments with large numbers of concurrent transactions.
For information about configuring connection pooling, see the Global Services
Configuration Guide.
Global Services Teamcenter 8 rich client connector

Global Services provides a rich client connector for Teamcenter 8 based on the OSGi
framework as defined by the OSGi Alliance (formerly know as the Open Services
Gateway initiative). This connector replaces the deprecated Global Services rich
client connector for connecting to Teamcenter 8 sites.
For information about OSGi, see the OSGi Alliance Web site:
http://www.osgi.org
For information about the Global Services Teamcenter 8 rich client connector, see
the Global Services Configuration Guide.


The following are new product structure features.
Structure clone
You can clone an existing product structure to create a new structure, for example, if
the new product structure is very similar to the existing product structure. As an
alternative to cloning a structure, you can create a product structure template and
use it as the basis of the new product structure. You can clone the entire product
structure from the top level down, or you can clone a selected subassembly. It is not
necessary to open the CAD tool to create the clone.
The cloning operation uses Business Modeler IDE deep copy rules to determine how
datasets and attachments are copied.
When you open the clone, you can edit or update any of the items, item revisions,
datasets, and attachments without affecting the original structure.
The replication of part family members depends on whether the current model is
a part family member and if you choose to include part family masters and part
family members in the clone.
To create a structure clone, select the desired top level or subassembly in Structure
Manager and choose Tools→Duplicate. Teamcenter displays the Duplicate dialog
box, allowing you to define display and naming options for the clone.
For more information about the structure clone feature, see the Structure Manager
Guide.

The following are new features for managing manufacturing data.
Time management
You can manage and analyze times of process plans in Manufacturing Process
Planner. You can store individual times for each activity, or the cumulative time
required for operations or processes in a process structure. The Time pane provides
information specific to the process or operation, and allows you to perform a time
analysis. You can add activities to operations and store individual times for each
activity. The time analysis calculates total work and total duration of descendents of
a selected process or operation. In addition, it calculates the time required for each
category of activity (for example, value-added or nonvalue-added) and portrays
these in a pie chart. Once calculated, you can store the cumulative time required
for operations or processes in the process structure. For selected operations, you
can create activities and edit their time data directly in the Activity section of the
Time pane.
For more information, see the Manufacturing Process Planner Guide.

Creating 2D snapshots
2D snapshots are dynamic objects that represent a 2D scene (a view of the base
image and markups) but are more than just image captures. You can have one or
many snapshots associated with a BOM line in your product structure. When you
select a BOM line, Teamcenter displays the attached image dataset in the 2D Viewer
pane. If there are multiple image datasets attached, you can select the desired
image dataset. You can:
• Use 2D snapshots to load base images and markups into the 2D viewer and
restore the saved positioning information.
• Populate assets in technical illustrations with 2D snapshots
• Query 2D snapshots to find related item revisions and technical illustrations.
• Update 2D snapshots to reflect changes in base images and markups.
• Print 2D snapshots from Teamcenter.
You can create 2D snapshots from any file displayed in the 2D viewer in
Multi-Structure Manager or Manufacturing Process Planner.
For more information, see the Multi-Structure Manager Guide or the Manufacturing
Process Planner Guide.
Find checked-out objects

You can see a list of objects that you have checked out of the database in
Manufacturing Process Planner. You can specify that Teamcenter shows you this
list each time you exit, or you can use the Tools→CheckInOut→Find Checked-Out
in Database menu command.
In addition, you can also display a list of checked out objects in a selected structure,
using the Tools→Find Checked-Out in Structure menu command.
Teamcenter displays:
• All objects (items, item revisions, BOM views, BOM view revisions) in the
selected structure that are checked out.
• Checked-out forms and datasets attached to objects in the selected structure.
• Checked-out occurrence groups in the selected structure.
• Checked-out activities under operations in the selected structure.
• Classified-objects assigned on operations/processes in the selected structure.

Showing unconfigured assigned occurrences

When viewing composition structures in Manufacturing Process Planner
or Multi-Structure Manager, use the View®Show Unconfigured Assigned
Occurrences menu command to show assigned objects that were configured out of
the structures to which the objects were assigned. Unconfigured variants of assigned
objects are shown in the composition structure when:
• The Show Unconfigured Assigned Occurrences menu command is not checked
in the composition structure and the Show Unconfigured Variants menu
command of the assigned objects is checked.
• The Show Unconfigured Assigned Occurrences menu command is checked

in the composition structure.
Unconfigured variants of assigned objects are not shown in the composition structure
when:
• The Show Unconfigured Assigned Occurrences menu command is not checked
in the composition structure and the Show Unconfigured Variants menu
command of the assigned objects is not checked.
Note
This command does not automatically refresh. Any changes to the assigned
objects are not reflected in the structure until you execute this command again.
Executing the Show Unconfigured Assigned Occurrences menu command takes

the assigned objects and their descendents into consideration.
For more information, see Manufacturing Process Planner Guide.
Incremental change when cloning

When creating structures from a template, the cloning process now takes incremental
change into consideration. When cloning, Teamcenter handles incremental changes
in the following way:
• Incremental changes that are currently effective are merged with the currently
active incremental change.
• Incremental changes that are effective in the future are carried forward to the
newly-cloned structure or re-created under new incremental change revisions.
Find this feature in the configuration section of the New From Template dialog box.
For more information, see the Getting Started with Manufacturing.

New Process dialog box changes

When you create a new process, operation, work area, or item in Manufacturing
Process Planner, Multi-Structure Manager, Part Planner, or Plant Designer, the
dialog boxes used to create these objects are now based on the standard Teamcenter
New Item dialog boxes that you are familiar with from My Teamcenter or Structure
Manager.
You create structures from a template (clone structures) using the File→New→From
Template menu commands.
Manufacturing preferences in preference hierarchy

You can modify certain manufacturing preferences directly in the preference
hierarchy.
1. Choose Edit®Options.
Teamcenter opens the Options dialog box.
2. Click ME in the hierarchy tree.

Teamcenter displays the following three tabbed pages:
• General
Displays general Manufacturing Process Planner settings.
• PERT
Displays PERT chart settings.
• Time
Displays Time tab settings.
Encrypting attributes in Resource Manager

You can encrypt selected attribute values in the database. The values are then
encrypted for all classes and views where the attribute is used. You cannot search
for encrypted attribute values.
You can only encrypt values that have a string format.
Specify that a value is encrypted in the Classification Administration application.
For more information, see the Resource Manager Guide or the Classification Guide.

Open PAD user interface at PAD level

You can view the process assembly document (PAD) user interface at the PAD
process level. This pane displays PAD properties and PSD processes directly under
the selected PAD process. You can also create new child MEPSD items using this
new pane.
Note
MEPAD and MEPSD items types are only available if you install the GM
Overlay.
You can still invoke the existing PAD user interface from the new user interface.
1. Select a PSD process from the list of PSD processes for a selected PAD process.
2. Click the Drill Down button .
3. Click the Drill Up button to navigate to the PAD user interface of the parent
MEPAD item from the PAD user interface at the MEPSD process item.
Note
The functionality to create a new MEPSD item from the existing PAD user
interface has been moved to the new PAD user interface at the MEPAD
process item level.
Managing Mechatronics data

The following are new features for Mechatronics Process Management.
Wiring harness options and variants

The wire harness integration framework now allows users to exchange data (options
and variants) with ECAD and MCAD applications. It also provides SOA services
that help users publish, retrieve, and edit the wire harness structure.
For more information about options and variants, see the Wiring Harness Design
Tools Integration Guide.
Embedded Software Design Data Management

The Embedded Software Design Data Management functionality helps users manage
design data (source code, object files, third party libraries) of embedded software
components. Users can create, update, and delete software design data components.
They can also define dependencies and associate specifications, source code, test
cases to software design data component.
For more information about working with Embedded Software Design Data
Management, see the Embedded Software Solutions Guide.

Visualizing products
Teamcenter’s lifecycle visualization delivers advanced visualization capabilities
which you can use to view and analyze 2D and 3D product design data.
The following new features are categorized by product configuration.
General enhancements
These features are general enhancements that are available in all product
configurations:
• New SOA-based visualization integration
• Lifecycle Viewer
• 2D and 3D thumbnail previews
• .vfz collaboration files
• Enhanced work session support
• Session attachments
• 3D PMI enhancements
• Improved product structure loading
• Improved rendering when generating 2D images from 3D views
• 3D snapshot improvements
New SOA-based visualization integration
Teamcenter’s integration with the Lifecycle Visualization viewers is now based upon
a Service-Oriented Architecture (SOA). This new integration offers improved support
for the visualization software components, including both the stand-alone viewers
and the new Lifecycle Viewer. It is installed automatically with Teamcenter and no
additional steps are required to work with visualization data in the Teamcenter 8
managed environment.
The Data Integration Services (DIS) Adapter has been completely removed from
Teamcenter. Existing functionality from previous releases, such as the ability to load
and save PLM XML, is retained in the new SOA-based integration.
Lifecycle Visualization viewers from earlier releases are not supported by and cannot
communicate with Teamcenter 8. However, the Teamcenter 8 stand-alone viewers
can communicate with DIS-enabled servers from previous Teamcenter releases.
For information on working with Teamcenter’s lifecycle visualization, see Getting
Started with Product Visualization.
For information on configuration options for the viewers, see Configuring
Teamcenter’s lifecycle visualization.

Lifecycle Viewer
The Lifecycle Viewer is a full-fledged visualization client within Teamcenter. It

provides nearly all of the visualization tools offered by the stand-alone viewer, many
of which are not available in the embedded viewers within Teamcenter applications
such as My Teamcenter.
The Lifecycle Viewer is available in the same product configurations as the
stand-alone viewer, Base, Standard, Professional, and Mockup. Features available
vary depending upon the licensing level. The Base configuration is automatically
installed with the rich client.
Using the Lifecycle Viewer, you can:
• Work within a comprehensive user interface that provides access to many of the
options previously available only with the stand-alone products, including menus
and views (the equivalent of Project Workspace windows such as the Assembly).
• Insert or merge files within active Viewing windows.
• Work with multiple open datasets.
• Preserve the state of your work with session files.
• Save data as PLM XML.
• Export 2D images and 3D models as supported datasets.
• Author visualization data such as motion files, swept volumes, and .vfz
collaboration files.
For information on working with the Lifecycle Viewer, see Getting Started with
Product Visualization.
2D and 3D thumbnail previews
Display 2D raster images and JT parts in the Image Thumbnail Preview and the
JT Preview views. When you select compatible objects associated with items,
item revisions, and datasets within the My Teamcenter tree or the trees of other
applications, the associated image or JT part is displayed in the appropriate preview
viewer. These views are displayed by default with appropriate applications such
as My Teamcenter.
For information on using the Image Thumbnail Preview and the JT Preview views,
see Previewing images and .jt parts.

.vfz collaboration files
You can now quickly package your work session as a .vfz file and attach it to an
e-mail to send to other members of your organization. You can specify to package
only the session contents of the active Viewing window or the contents of all open
Viewing windows; save 3D geometry as Ultra-Lightweight Precise (ULP) JT data;
and password protect the generated .vfz file.
Authoring .vfz collaboration files requires the Professional or Mockup service level,
along with an additional .vfz collaboration file license. If you have the Standard,
Professional, or Mockup service level, you can edit, repackage, and re-send the data
from existing collaboration files. You can view .vfz collaboration files in any viewer
service level.
For information on using .vfz collaboration files, see E-mailing your work session.
Enhanced work session support
You can now work with session files from the Teamcenter managed environment.
Teamcenter session files can contain static or dynamic product structure references.
For information on working with session files, see Saving your work session.
Session attachments
You can now save attachments, such as Microsoft Office documents, with your work
session or session package.
For information on working with session files, see Saving your work session.
3D PMI enhancements
Several PMI enhancements have been added to this release. You can:
• Display PMI on faces and edges that are grouped by CAD feature.
• Translate and display filled fonts.
• Control how to view more than one part at a time.
• Use JT Inspector to validate PMI information contained in JT files.
• Display PMI information from multiple models in the PMI tree.
• Select multiple parts, faces, and edges in the 3D View.
• Use Model View selection and activation enhancements
For information on using PMI, see Working with Product Manufacturing Information
(PMI).

Improved product structure loading
The performance and behavior of the Teamcenter product structure loading

mechanisms used for visualization have been improved. The visualization
application now “pulls” needed product structure elements, on demand, directly
from the Teamcenter data model, as opposed to the previous PLM XML file based
“push model” paradigm.
For information on viewing datasets that contain product structure, see Opening
visualization datasets.
Improved rendering when generating 2D images from 3D views
Lifecycle Visualization now uses a tiled rendering scheme when generating 2D

images from 3D views. 2D images are now generated at pixel resolutions beyond the
capabilities of the underlying graphics hardware. The pixel resolution for the Export
Image and Print command for 3D views is now only limited by the amount of free
application memory, not the amount of graphics memory on the graphics card.
For information on creating 2D image captures, see Save an image of a 3D model.
3D snapshot improvements
The following enhancements are made to 3D snapshots, which are sometimes called
product views:
• You can check in and check out a 3D snapshot dataset.
• Cloning and multisite operations are supported for 3D snapshots in structures.
• Certain menu commands are renamed to enhance usability and provide

commonality with 2D snapshot menu commands.
For more information, see the Structure Manager Guide, Manufacturing Process
Planner Guide, Multi-Structure Manager Guide, and Part Planner Guide.
2D improvements
AutoCAD 2009 DWG and DFX file types are now supported.
For information on viewing 2D images, see Working with 2D Images.

3D improvements for Standard, Professional, and Mockup

These features are available only in Standard, Professional, and Mockup:
• Markup and callout enhancements
• Enhanced support for NX advanced assembly functionality
• Enhancement for displaying attributes and PMI
• Part report enhancements
Markup and callout enhancements
• Callout & Symbol Manager and the 3D Markup features have been merged
into a single area of functionality. The user interfaces for these features have
been combined, with much of the callout user interface being moved into the
markup user interface.
• New markup and callout features have been added to the Markup toolbar,
Markup menu, and markup shortcut menu, including the ability to:
– Add a new layer
– Automatically create anchored text on either selected or visible parts
– Enable text markups to be populated with pre-defined text
– Align anchored text markups
– Distribute and reposition anchored text markups
– Resequence callouts
– Display the Symbol Manager
• You can now define symbol information and access the Callouts dialog box from
within in the Markup 3D Preferences dialog box.
• You can modify a number of new text properties in the Markup 3D Preferences,
Markup Text, Edit Text, and Text Properties dialog boxes.
Note
The new text markups will not be displayed in older versions of Lifecycle
Visualization (prior to 8) when loaded from layer files and during
conferencing. Old text markups will be displayed and converted to the
new text markups.
For information on using 3D markups, see Working with 3D markups.

Enhanced support for NX advanced assembly functionality
Lifecycle Visualization clients now offer consistent visualization of advanced

geometry concepts that are generated from NX design data. Specific improvements
are in the areas of PMI at the assembly level, reference sets, arrangements, and
promotions. These enhancements are in both the stand-alone Lifecycle Visualization
and Lifecycle Viewer products.
Note
To take full advantage of this capability, the NX data must be created by NX
6.0.3 or later. Also, manage the data using Teamcenter 8.
For information on viewing NX advanced assembly functionality, see Viewing NX

advanced assembly operations.
Enhancement for displaying attributes and PMI
The following enhancements are available for displaying attributes and PMI:
• Teamcenter attributes can now be displayed directly in stand-alone Lifecycle
Visualization. The attributes to be displayed can be configured in the
Teamcenter Integration dialog box (File→Preferences→Teamcenter Integration,
on the Attributes page).
• The display of attributes has been improved to include displaying multi-line

attributes. For example, attribute sequences of DESLOG001, DESLOG002,…
can be combined into a single, multi-line attribute named DESLOG.
• When exporting PLM XML files from Lifecycle Viewer, you can now specify the
attributes you want to export even if you have not loaded them in Teamcenter
(late-loading).
• You can now view assembly-level PMI in Lifecycle Viewer.
For information on setting preferences for displaying attributes, see Teamcenter

Integration Attributes Preferences. For information on using PMI, see Working with
Product Manufacturing Information (PMI).

Part report enhancements

Enhancements to part report feature includes:
• The menu containing the Part Report option now appears in the Lifecycle Viewer
of the Teamcenter Portal Rich Client (RAC) Embedded Viewer, in addition to in
the stand-alone Teamcenter Visualization viewer.
• Teamcenter object attributes (metadata) are now listed for inclusion in the Part
Report.
• Part reports can now be generated as XML output files in the Computer-Aided
Acquisition and Logistics Support Department of Defense (CALS) format.
• The user can now choose which element type attributes (part, leaf component, or
end item) will be used to generate the report.
For information on generating part reports, see Creating part reports.
3D improvements for Professional and Mockup

These features are available only in Professional and Mockup:
• New Direct Model-based swept volumes
• Key change in navigation explore mode
New Direct Model-based swept volumes

The previous method for generating swept volumes has been replaced with a new
DirectModel-based implementation. A swept volume is a graphical representation of
the volume and path of a part as it moves through 3D space. Swept volumes are now
generated in a faster, more efficient and intuitive manner than in previous releases.
In addition, the visualization API has been updated to provide an automated
mechanism for generating swept volumes.
To generate swept volumes, your machine must have a graphics card with a 24-bit
depth buffer.
For information on generating swept volumes, see Working with path planning.
Key change in navigation explore mode

The shortcut keys used for the navigation explore mode in the 3D Viewing window
have changed.
Function Previous key New key

Increase Translation A T
Decrease Translation Z G
Increase Rotation S R
Decrease Rotation X F
For information on using the navigation explore mode, see Explore your model.

Enhancements for ECAD Viewer

New features and tools for ECAD Viewer include the following:
• Working with schematic documents
• Cross probing schematic and PCB documents
• Net and page connector navigation
• PCB measurement markups
• Design for Assembly
• ECAD reporting capability
• ECAD document print capability
Working with schematic documents

Support has been added for working with EDIF 2.0 and 3.0 schematic documents.
For information about working with schematic documents, see Using the ECAD
Viewer.
Cross probing PCB and schematic documents

Use cross probing to find common parts that are included in the schematic design or
PCB. During the design process you may need to verify similarities of and differences
between schematic and PCB documents. You can also determine how the schematic
design was implemented in a specific PCB.
For information about cross probing, see Using cross probing.
Net and page connector navigation

Net and page connector navigation is now supported. When you use net navigation
and highlight a net, a marker displays on a navigation point of the net. You can
then navigate along the net moving the marker from key point to key point. When
navigating nets on the schematic, you can navigate to different pages, depending
on the path of the net.
For information on using the net and page connector navigation, see Navigate nets
and page connectors.
PCB measurement markups

ECAD measurement tools provide options for distance, radial, clearance, and length
measurements. When you save these measurements to your database or file system,
they become part of the PCB data session. Measurement tools are also available
when you checkout the PCB as read-only. You can still create measurements even
though you are viewing a read-only PCB document. You cannot, however, save
(persist) these measurements.
For information about measurement markups, see PCB measurement markups.

Design for Assembly
Use Design for Assembly to manage an analysis of your PCB design against a
default or customized set of manufacturing rules. When you run the DFA test,
both the manufacturing rules and the results are displayed. The analysis displays
reflects in three broad categories; as expected (within the established threshold),
as warnings, or as violations. You can highlight a warning or violation object and
it is displayed in the Viewing window.
For information on using Design for Assembly, see Working with Design for Assembly.
ECAD reporting capability
As you review and analyze ECAD documents, you may find it useful to generate
specific reports for your records or for use when you collaborate with others. You
generate reports for several ECAD objects (Bus, Nets, Parts, and so forth) by selecting
the report template that meets your needs. You can preview the report before it is
generated and you can customize the template. You can also specify default output
formats (HTML, XML, Text, and CSV), or generate your own output format.
For information on using reports, see Creating reports.
Printing ECAD documents
You can use standard Windows printing features to configure printers. Additional
printing options are also available such as setting page headers, footers, and
watermarks. You can print both PCBs and schematic files.
For information about printing, see Printing ECAD documents.
Enhancements for ClearanceDB

The Teamcenter Integrated Clearance Management (ICM) architecture has been
simplified to make the ICM system easier to install and maintain. In addition, the
number of configuration files and environment variables has been reduced.
For information on installing and configuring the Teamcenter Integrated Clearance
Management (ICM) system, see the ClearanceDB Administration Guide in the
stand-alone Teamcenter’s lifecycle visualization Help collection.

Managing CAE data

Teamcenter for Simulation provides simulation process and data management
capabilities for CAE engineers and CAE analysts performing analysis work. It
consists of two applications, the CAE Manager and the CAE Structure Designer.
The following are new and changed Teamcenter’s simulation process management
features:
CAE Manager – Inspector

This enhancement allows you to update a CAE model structure to reflect changes to
the related product structure. It permits you to:
• Add or remove CAE model components if components are added to or removed
from the product structure.
• Create new CAE model components to reflect additions or revisions in the

product structure.
• Link CAE model components to corresponding product components.
• Revise a CAE model component and replace the BOM line with a later revision
if components of the product structure are revised.
You can choose whether to make the necessary changes in the current revision of
the CAE model structure or a new revision.
Use the CAE Manager – Inspector to compare a CAE model structure and a
product structure, and also to update the CAE model structure if necessary.
For more information, see the Teamcenter for Simulation Guide.
Enhanced simulation process launch

This enhancement implements a generic framework that allows you to integrate
external simulation processes with Teamcenter for Simulation. It allows you to
configure the integration of external simulation processes and tools (including
commercial CAE preprocessors, solvers, and postprocessors, as well as any
commercial or custom-built compute tools used for CAE tasks) with Teamcenter
for Simulation. Configured processes may be invoked from the rich client and the
process results stored in Teamcenter.
The Teamcenter application administrator configures the location of each process,
how it is launched, and the locations of the input files and results.
To launch a configured process, choose the Tools→Launch Simulation Tool menu
command in CAE Manager, and then select the desired tool from the displayed
list of configured tools and processes.

Launch simulation process remotely

This enhancement allows Teamcenter for Simulation to launch any configured
simulation tool that can run in a batch mode on a remote compute resource, that
is, on a machine other than the client. The Teamcenter simulation administrator
can configure this feature to interact with a load balancing system. This capability
leverages the Teamcenter Dispatcher service.
To launch a simulation process, choose the Tools→Launch Simulation Tool menu
command in CAE Manager, and then select the desired tool from the displayed list of
configured tools and processes. To monitor a simulation process, use the translation
administrator console in My Teamcenter.

Repeatable Digital Validation

The following are new Repeatable Digital Validation (RDV) features.
DesignContext
Find the following new and enhanced features in DesignContext.
Clearance database integration enhancements
The DesignContext integrated clearance management (ICM) integration with

Teamcenter is enhanced to allow easier installation and configuration. Also, the
following usability enhancements in DesignContext allow easier identification and
analysis of clearance issues.
• Simplifies the commands available on the Tools menu. The Tools→ClearanceDB
command is renamed as Tools→Clearance Analysis and other commands are
removed.
• Introduces a new Clearance Analysis dialog window that shows the clearance
analysis options in DesignContext. It includes a progress bar and a progress
status message.
• Adds a Show Issues button to display information about the progress of the
current clearance calculation. An Abort button on the progress window allows
the user to cancel the calculation if it hangs or takes an excessively long time.
• Renames the Clearance Analysis Report tabs to Targets-Target Issues,

Targets-Background Issues, and Other Target Issues.
• Adds tool tips to the Clearance Analysis Report panes.
• Renames BatchMode to Database Query and Adhoc mode to Real Time.
• Enhances the display and grouping of results for easier interpretation.
• Introduces an RDVClearanceProxyServers preference to identify the

database connection used by the proxy server to connect to the clearance
database. At the same time, the existing PortalDesignContextCLRServers,
CLR_Timeout_Limit, and CLR_Wait_Time preferences are no longer required
and are obsoleted.
All existing ICM functionality is retained.

For more information, see the DesignContext Guide and Getting Started with RDV.

DesignContext on cacheless search
This enhancement allows the RDV DesignContext application to use the cacheless
quick search mechanism.
It allows the user to make spatial searches based on box volumes, planes, proximity
to objects, and size using the cacheless search engine. Attribute searches,
classification searches, and saved queries are also supported. QPL and appearance
searches are also available as before.
To use the cacheless search mechanism, set the
PortalDesignContextSearchEnginePreference site preference to
CachelessSearchEngine. Users initiate searches and store, compare, and manage
search results in the same way as in previous releases. Revision and variant rules
may be used to limit search results to a particular product configuration.
Teamcenter requires NX part data to create the bounding box data it uses to
construct the search indexes needed for spatial searches.
Find this enhancement when you configure searches for the DesignContext
application.
For more information, see the DesignContext Guide and Getting Started with RDV.
Managing quality data

Dimensional Planning and Validation (DPV) is a quality management solution
you can easily integrate into your Teamcenter environment. DPV enables the
extended enterprise to collect, manage, dimensionally analyze, and report on quality
measurement information. This report generation solution provides rapid access
to design and manufacturing information that directly influence’s your enterprise’s
quality targets.
The following are new DPV features.
DPV Help included in Teamcenter Help collection

Help for DPV administrative tasks is now included in the Teamcenter Help collection.
For more information, see the Dimensional Planning and Validation Administration
Guide and Getting Started with Dimensional Planning and Validation.

Managing Maintenance, Repair, and Overhaul data

The following new application is available for managing Maintenance, Repair, and
Overhaul data.
As-Built Manager
As-Built Manager is a separately licensed application that is installed as an optional
overlay on top of the standard Teamcenter product. This application allows you to
manage the as-built configuration of an asset realized from a product definition
structure, such as a design or manufacturing structure. You can use As-Built
Manager to:
• Create the as-built physical product instantiation for any configured product
structure.
• Store and manage additional information about the as-built physical part
structure that is not tracked on the product definition structure, such as serial
numbers and lot numbers.
• Reconcile the as-built structure with a configured product definition structure to

identify parts that are missing, alternates, substitutes, or deviations.
• Compare the as-built structure to the product definition structure or to another

as-built structure.
• View the as-designed product structure and the as-built physical structure
configuration side-by-side or by using the embedded viewer available in the
rich client.
• Import an as-built structure from an external manufacturing execution system

(MES) or an enterprise resource planning (ERP) system in PLM XML.
• Export an as-built structure to an Enterprise Knowledge Management

Maintenance, Repair, and Overhaul (MRO) system using Data Exchange.
For more information about As-Built Manager, see the As-Built Manager Guide.

Customizing Teamcenter
The following are new Teamcenter customization features.
Service-oriented architecture (SOA)

Teamcenter APIs are moving to service-oriented architecture (SOA) to improve
standardization. SOA provides an environment that enables network callable
interfaces into the Teamcenter server.
New Workflow operations
New operations are added to the Workflow service. This feature has no impact
on Teamcenter end users. Workflow will work the same way as it did prior to the
new operations.
The new operations are included in the soa_client.zip archive file on the installation
source.
For more information about these operations, see the Services Reference.
Feature enhancements in SOA
A number of enhancements are made on the service-oriented architecture (SOA) for

both the server and client framework. Services are enhanced in the following ways:
• Inclusion of SOA service documentation for .NET
• Improved memory management in SOA client and server framework
• Dynamically set object property policies from client applications
• A server reassignment notification to the SOA client and reestablishing the

current property policy before making a new connection
• A new API in the Model Manager to return a list of objects in the CDM
• Serialization of connection object for persistence between sessions
As a result of these enhancements, customers who use an SOA-based client to

connect to Teamcenter will experience more robust communication between their
client and the server.
The new functionality is included in the soa_client.zip archive file on the
installation source.
For more information about these enhancements, see the Services Guide.

New operation for Teamcenter Publish
The createOrUpdateRelations operation is now provided for Teamcenter Publish.

Customers use Teamcenter Publish to create diagrams of part assemblies for their
product documents. The software allows customers to take snapshots of assemblies
and then display assembly breakdown diagrams with all the parts labeled. End
users should see no difference in how Teamcenter Publish works.
The new operation is included in the soa_client.zip archive file on the installation
source.
WSDL support in Teamcenter services
A .NET WSDL interface for the .NET Web tier is now supplied. Previously, the J2EE
Web tier exposed a WSDL interface to access the SOA Services over HTTP/SOAP.
The J2EE Web Tier hosted the SOAP endpoint. Now, a .NET alternative to the J2EE
SOAP endpoint is provided at the .NET Web Tier.
You can connect your WSDL based client to the .NET Web tier. Once the service
is hosted, you can:
1. Get the list of all the services hosted on the .NET Web tier.
2. Get the WSDL from the .NET Web tier.
3. Create proxies out of the WSDL.
For more information, see the Services Guide.
Alternate ID support for NX Integration
APIs for alternate IDs are now supplied in service-oriented architecture (SOA)
format, and are made available to the NX Integration. The following new SOA
operations are supplied:
listAlternateIdDisplayRules
createAlternateIdentifiers
getContextsAndIdentifierTypes
validateAlternateIds
setAndEvaluateIdDisplayRule
source.

Occurrence override support for NX Integration
SOA operations for occurrence override functions are added to the NX Integration.
These operations allow the NX Integration, as well as other CAD integrations, to
retrieve occurrence override information for their bills of materials (BOMs).
The getAbsoluteOccurrenceOverrides operation is new
in the CAD:StructureManagement service, and the
createOrUpdateAbsoluteStructure is revised.
The new and revised operations are included in the soa_client.zip archive file on
the installation source.
Support for adding objects to projects
The assignOrRemoveObjects operation is added to the ProjectLevelSecurity

service in the service oriented architecture (SOA) framework. This operation allows
objects to be added to and removed from projects.
To utilize this operation, click the My Projects link in the Quick Links navigation
bar of the Teamcenter rich client. When you add or remove objects in projects, you
use the assignOrRemoveObjects operation.
For more information about assigning and removing objects in projects, see the
Rich Client Interface Guide. The new and revised operations are included in the
soa_client.zip archive file on the installation source. For more information about
this new operation, see the Services Reference.
CAM support for NX Integration
The NX Integration has service operations for CAM functions. These operations
allow NX Integration to query, create, and modify CAM data model in Teamcenter.
The following new SOA operations are supplied in the DataManagement service:
expandFoldersForCAD
createOrUpdateMEActivityFolders
createOrUpdateMENXObjects
The following new SOA operations are supplied in the StructureManagement

service:
createOrUpdateRelativeStructure
expandPSOneLevel
expandPSAllLevels
deleteRelativeStructure

Miscellaneous new services for the NX Integration
The NX Integration has miscellaneous new operations, and revisions to existing

operations.
Revisions are made to the following operations in the StructureManagement
service:
createOrUpdateRelativeStructure
deleteRelativeStructure
createOrUpdateAbsoluteStructure
deleteAssemblyArrangements
The following new operations are added to the Session service:

getFavorites
setFavorites
setUserSessionState
In the DataManagement service, the createAppUidObjects operation is added,

and revisions are made to the createOrUpdateParts operation.
Support for features in the NX Integration
The NX Integration has service-oriented architecture (SOA) APIs for features.

In NX parlance, a feature is an object that represents a design element, and there
are heavyweight and lightweight features. Heavyweight features are represented in
Teamcenter by parts that are a subclass of the Item business object. Lightweight
features are represented in Teamcenter by the general design element (GDE)
business objects that contain information about the feature. A GDE occurrence links
the GDE and the parent item revision. Features may contain a JT file to represent
the feature during visualization.
The createOrUpdateGDELink SOA operation is added to the DataManagement
service, and the expandPSOneLevel and expandPSAllLevels operations are
added to the StructureManagement service.
source.
For more information about these new operations, see the Services Reference.

Baselines for the NX Integration
New baseline elements support baselines used in the NX Integration. Administrators

can use the baseline workflow to baseline items. The following elements are now in
Teamcenter:
• TC Default Baseline Process workflow in Workflow Designer
• Default Baseline Suffix Rule naming rule in the Business Modeler IDE
• TC Baselined status in the Business Modeler IDE
• createBaseline operation in Teamcenter Services
For more information about creating baselines, see the Workflow Designer Guide.
Lifecycle Visualization product structure loading performance improvements
Product structure loading and performance improvements are made to Lifecycle

Visualization. As a result of this enhancement, users should see faster loading
of visualization data in Teamcenter. This enhancement only makes architectural
changes, and provides new SOA operations, ITK interfaces, and a preference. It does
not make any customer-facing UI changes.
The following new operations are added:
getDisplayString
expandPSOneLevel
ReconfigureBOMWindows
The following new ITK functions are added:

libbom/BOM_line_find_preferred_JT_refset
libbom/BOM_line_get_JTHint_string
libbom/BOM_line_ask_occ_for_clone_stable_uid
libbom/BOM_line_get_all_occurrences
The new preference is JTContentHintPropertyPolicy.

For more information about the ITK functions, see the Integration Toolkit Function
Reference.
For more information about the operations, see the Services Reference.
New change management service
A new ChangeManagement service is included in the service-oriented architecture

(SOA). This service includes a number of change management-related operations,
and allows external clients to connect to Teamcenter change management
functionality.
The ChangeManagement service is included in the soa_client.zip archive file on
For more information, see the Services Reference.

Rich client debugging tools

Three new tools are added to the rich client interface to help you debug
customizations that you make:
• Print Object
Displays the internal object values of the selected workspace object in a dialog
box.
• Communications Profiler
Reports bursts of communication from the client to the server. It watches for a
threshold of server calls in a span of time and reports the list of server calls
and their timing.
• Performance Monitor
Displays the following:
– The number of SQL calls
– The number of rows returned
– The number of SQL errors
– The time elapsed executing the SQL calls
– The CPU time used on the server
– The wall clock time since the last reset
– The CPU time used on the client
– The number of server calls made by the client
You can also add comments to the log, save the log, and display a report.
For more information about these tools, see the Rich Client Customization
Programmer’s Guide.
Teamcenter supports UTF-8

UTF-8, an ASCII-compatible multi-byte encoding standard, provides the following
benefits:
• Multilingual data can coexist in a single Teamcenter installation.
• The Teamcenter user interface can be localized and launched in different

languages on different clients.
• Multilingual data can be shared and updated across the different clients without
corrupting any data.
To use UTF-8, set environment settings (LC_ALL, LANG, NLS_LANG, and

TC_language_default) to accommodate the environment and upgrade the
Teamcenter environment from a legacy database to a UTF-8 database.

Teamcenter industry solutions

The following are new features in Teamcenter industry solution applications.
Aerospace and Defense

Aerospace and Defense provides a data model template that supports the aerospace
and defense manufacturing industry.
The following are new and changed Aerospace and Defense features:
Parts list management
This enhancement provides object types and functionality needed by the Aerospace
and Defense solution. It allows users to manage parts, assemblies, drawings, and
parts lists in document-centric and part-centric programs.
These objects allow the user to create and manage:
• Document-centric programs
The new functionality supports the following document-centric program data
management best practices:
– Managing multiple assemblies or parts with similar configuration or design

by detailing them on the same drawing or document
– Mandating a source document when creating a part or assembly
– Managing configuration changes of the assemblies through revisions of their

parts list source documents
– Managing engineering changes against the source document
– Applying effectivity to the source document
• Technical documents
Aerospace and Defense technical documents comprise printed or digital technical
information, including reports, drawings, procurement specifications, parts lists,
interface control documents, and schematics.
• Parts and assemblies in a document-centric program

In document-centric programs, a source document must be specified to create a
part or assembly. Technical documents serve as source documents for creating
parts and assemblies for a product.
• Assembly drawings
In document-centric programs, a source document must be specified to create an
assembly drawing. It represents the drawing that details one or more assemblies
on a given technical document.

• Standard parts
Standard parts may be used in multiple programs. The design of a standard part
is controlled by a specification published by a military, industry or company
authority. Programs can be enabled to use only preferred standard parts in
their assemblies.
Find these objects in the rich client, including My Teamcenter and Structure
Manager.
For more information, see Getting Started with Aerospace and Defense.
Owning organization
Organizations provide an industry-compliant format for uniquely identifying
entities, including the Commercial and Government Entity (CAGE).
Organizations, which are Teamcenter groups that model legal corporations or
companies whose members can be granted access to classified data, are defined in
the Organization application.
The owning organization attribute on business model objects allows users to create
and maintain data within the context of an organization. Administrators can
configure whether or not the data must be created in the context of an organization
and also which objects must be created in the context of an organization.
For more information, see the Organization Guide.
Enhanced naming rules

Naming rules are enhanced to support defining counters for more than one pattern.
Multiple patterns can have counters. Previously, counters could only be applied to
the first pattern in the naming rule. The Item create dialog box in the rich client
is enhanced to present the user with a list of patterns with defined counters in the
naming rule attached to the item_id property. The next item ID is generated per
the selected pattern in the list.
This feature can be used to define auto-numbering rules with multiple patterns for a
given object in the context of a program.
Revision naming rules

Administrators can define revision naming rules with initial, secondary, and
supplemental revision formats typically used in the Aerospace and Defense industry.
The Item Revise dialog box in the rich client is enhanced to present the user with
the next set of revision options as specified in the revision naming rule attached to
the item_revision_id property.
Sample program
When the Aerospace and Defense Training Program template is installed, a sample
program named Training is created.

The template provides naming rules, revision naming rules, lists of values (LOVs),
and dependent LOVs for various ADS objects in the context of the Training
program. In addition, program-level security is enabled for the Training program.
The Training program can be used for user training and also as a reference to set
up other Aerospace and Defense programs.
For more information, see Getting Started with Aerospace and Defense.
Properties on relation
Properties can be defined on relation business objects. This feature provides a

generic framework for managing data on object associations (relations). Both the
rich client and thin client are enhanced to manage properties on relations. The
properties added on a relation in the Business Modeler IDE are automatically
exposed in the rich client and the thin client through appropriate user interfaces
without writing any code.
For more information, see Getting Started with Aerospace and Defense and the
Business Modeler IDE Guide.
Program-level security
Programs identify collections of resources and assets bound by a common objective.

Programs facilitate:
• Program-based segregation of data and users.
• Access control for program data that uses program-level security rules to control
the user’s access to data assigned to the program.
• Program-specific lists of values for attributes.

Each program can have a separate list of attribute values.
• Program-based business rules.

You can write naming rules, revision naming rules, extension rules, and deep
copy rules for a specific program.
• Identification of preferred standard parts for a program.
In addition, administrators can configure Teamcenter to display the Project

application as Program in the user interface.
For more information, see Getting Started with Aerospace and Defense and the
Security Administration Guide.

Consumer Packaged Goods

Consumer Packaged Goods is a group of solutions that supports customers with
package design, brand management, finished product management and formula
management.
This includes the following features:
Package and brand management

The following solutions are available:
• Brand management
With brand management, you can create, classify and manage brand-related
information.
• Finished product management

Finished product management allows you to create, classify and manage finished
products and trade items.
• Packaging and artwork

Packaging and artwork are the first things that a consumer notices on a product.
Developing or modifying a package involves creating and managing key artifacts
like marketing briefs, design briefs, package roughs, copies, package items and
so on. You can track and manage the package and artwork development process.
For more information, see Getting Started with Consumer Packaged Goods.
Interspec integration
This feature provides an integration between Teamcenter and the Siemens SIMATIC
IT Interspec product, a specifications authoring tool.
This integration implements additional data model objects and feature enhancements
to permit Teamcenter to interact with Interspec. Objects that can be represented
include BOMs, formulated materials, raw materials, ingredients, and chemicals.
Teamcenter controls the overall development process and acts as the master
repository of all released specifications. Interspec provides specification authoring
and modeling capabilities and enforces regulatory rules. Read-only copies of
specifications are automatically saved into Teamcenter when they are created or
when they reach a certain maturity state. The save triggers can be configured in
the Interspec workflow. Specifications are attached to Consumer Packaged Goods
business objects in Teamcenter, for example, the finished product or package item.
All specifications are authored in Interspec, regardless of their type, for example,
formula specifications or packaging specifications.
This feature interoperates with the Specification Manager, a rich client application
for viewing specifications that were originally authored in Interspec. You can use the
Specification Manager to view the structure of a specification (for example, the BOM
and referenced specifications) or send them to Interspec for updating or viewing of
specification details; you cannot update specifications in the Specification Manager.
Find the Interspec integration in the Consumer Packaged Goods solution. Find the
Specification Manager in the Teamcenter rich client.

For more information, see Getting Started with Consumer Packaged Goods and the
Specification Manager Guide.
Specification Manager
The Specification Manager application allows you to view and work with
specifications or formulas. In the Consumer Packaged Goods and food and beverage
industry, specifications capture the complete definition of products and how to
manufacture them. These specifications are developed, reviewed, and eventually
approved which drives the product release process.
This solution includes the following features:
• Teamcenter integrates with the Interspec specification management application.
You can view specifications structure created in Interspec in the Specification
Manager application.
• Opens specifications from Specification Manager in Interspec.
For more information, see the Specification Manager Guide.

Performing integrations
The following are new features in Teamcenter integration applications.
Teamcenter Gateway for Electronic Design Automation (EDA)

The following are new features in the Teamcenter Gateway for Electronic Design
Automation (EDA) application.
Managing part library
Part library is a catalog system of parts that helps designers to search/locate/access

parts and use them in the design. Administrators can now manage a part library in
Teamcenter and exchange part library data between Teamcenter and ECAD library
tools. You can access the part library functionality from the Tools→Import→From
ECAD Library and Tools→Export→To ECAD Library menu in the rich client and
from the Teamcenter menu in the ECAD library tools.
For more information about part library, see Getting Started with Electronic (EDA)
Lifecycle Management.
Support for Mentor Graphics PADS
Teamcenter supports Mentor Graphics PADS product line. This includes support for
PADS Layout and PADS Logic tools. You can manage data that your PADS programs
create. The Teamcenter menu items are available in the PADS menu. This allows
you to perform Teamcenter operations like saving, checking in, checking out from
Teamcenter servers, while executing design tasks from their PADS product.
For more information about working with Mentor PADS, see Getting Started with
Electronic (EDA) Lifecycle Management.
Support for OrRCAD
Teamcenter supports Cadence OrCAD product line. This includes support for OrCAD
Capture and OrCAD Layout tools. You can launch the Cadence OrCAD application
through the Teamcenter Gateway for EDA application and can extract BOM, create
a viewable file, perform check in and check out.
For more information about working with OrCAD, see Getting Started with
Electronic (EDA) Lifecycle Management.
SOA communication layer
Teamcenter Gateway for EDA uses service-oriented arhitecture (SOA) as the

communication layer instead of AIWS.
For more information about SOA, see Getting Started with Electronic (EDA) Lifecycle
Management.

Teamcenter Gateway for EDA client logging
You can specify a log file name and log level for logging Teamcenter Gateway for
EDA client errors, warnings, and other operational information. This can be used to
submit bug reports to trace problems.
For more information about logging, see Getting Started with Electronic (EDA)
Lifecycle Management.
Teamcenter Gateway for EDA application
The Teamcenter Gateway for EDA application supports file-based integrations. It is

used for library integrations such as Cadence Allegro library and Mentor Expedition
library. The gateway is also used to interface with ECAD library tools where the
library tool does not provide a user interface. The interface provides a menu of
ECAD-Teamcenter integrations actions similar to that of the embedded integration.
For more information about working with Teamcenter Gateway for EDA, see Getting
Started with Electronic (EDA) Lifecycle Management.

NX Integration
These topics are part of the Teamcenter NX Integration. For more information about
the Teamcenter NX Integration, see the appropriate integration guide.
Managing NX Drawings
Teamcenter NX Integration supports NX 7.0 drawings being populated into a default

Teamcenter drawing type supported by two new relations: DrawingOf, between the
drawing and its principal assembly, and DrawingUsing, between the drawing and
the assemblies the drawing references for illustration.
• The DrawingOf relation can be between:
– A principle assembly item revision and a drawing revision.
– A drawing dataset and an item dataset.
• The DrawingUsing relation is used at the item revision level to provide a

drawing reference to an assembly model, but not to its assembly components.
For information about managing drawings, see the Rich Client Interface Guide.
NX/requirements integration
The Requirements Manager integration with Teamcenter NX Integration lets you

create and delete trace links in Teamcenter between requirements and NX parts.
You can:
• Generate traceability reports for NX parts.
• View defining and complying relationships for NX parts in the Relation Browser.
• Follow trace link from requirements to NX parts and from NX parts to

requirements in Relation Browser.
• Search for trace links in the Relation Browser.
For more information about using trace links, see the Requirements Manager Guide.

Managing translations
Dispatcher, previously known as Translation Management, is the integration of
the Dispatcher Server and Teamcenter. Dispatcher enables Teamcenter users to
translate data files that are managed by Teamcenter to 3D or 2D file formats.
Note
The names of Dispatcher and its components are changed from previous
versions of the application.
New name Old name

Dispatcher Translation Management
Dispatcher Server Translation Solution Toolkit (TSTK)
Dispatcher client Translation service
Request administration Translator administrator console
console
Translation intelligent licensing

Translation processes running on a dispatcher module may be dependent on the
availability of licenses for the translator. When a process fails due to a license
issue, the module sends back an error to the scheduler; however, the module has
no knowledge of why the process failed.
A new configuration file, TaskConfiguration.xml, is included in the scheduler to
hold information about a particular service and the maximum number of processes
that can run at a given time. This allows administrators to control the number of
processes and manage license availability for the specified processes across modules
at a given time.
For more information, see the Dispatcher Server Installation Guide.
Translation request persistence

The scheduler uses a database to store translation tasks and events. If the scheduler
fails due to some reason, such as a power outage, all translation tasks are stored in
the database and you can restart them.

Repeating tasks
You can repeat translation tasks and specify the time interval for the repeating tasks.
Note
Repeating task functionality is an expensive option. This functionality
increases the load on the Dispatcher Server.

Management).
Load balancing based on CPU usage

The scheduler load balances translation tasks based on the CPU usage of the module.
See error log in the Request Administration Console

You can view the error log of the dispatcher request in the Request Administration
Console.
Management).

Chapter
3 Teamcenter 8 release notes
Teamcenter 8 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Installation and upgrade release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Lifecycle Visualization installation release notes . . . . . . . . . . . . . . . . 3-6
Online help installation release notes . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Usage release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Client for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Manufacturing Process Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Multi-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Requirements Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Schedule Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Administration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Customization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Internationalization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Teamcenter 8 documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Using documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Using PDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Using HTML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Access Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Business Modeler IDE Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
C++ API Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Dispatcher Server Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
ERP Connect Integration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Getting Started with Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . 3-44
Getting Started with Dispatcher (Translation Management) . . . . . . . . . . . 3-45
Global Services Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
Installation on UNIX and Linux Servers Guide . . . . . . . . . . . . . . . . . . . . 3-48
General documentation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Environment settings for non-English locales (UNIX and Linux
systems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Environment settings for non-UTF-8 environments . . . . . . . . . . . 3-50
Environment settings for UTF-8 environments . . . . . . . . . . . . . . . 3-54
Installation on Windows Servers Guide . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
General documentation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Environment settings for non-English locales (Windows systems) . . . . 3-60
Multi-Site Collaboration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Preferences and Environment Variables Reference . . . . . . . . . . . . . . . . . . 3-68
ETS_update_state_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

PLMXML_put_pie_log_in_syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
TC_NX_Foreign_Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71
TC_ugmaster_name_separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Rich Client Interface Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Schedule Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Security Services Installation/Customization . . . . . . . . . . . . . . . . . . . . . . 3-77
Services Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Structure Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Clarification of Change to Replace command behavior . . . . . . . . . . . . 3-78
Teamcenter Environment Manager Help . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Upgrade Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Utilities Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
dispatcher_create_rqst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81
What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Workflow Designer Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84
notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
CONTMGMT-notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
Adding a Validate task to a workflow process . . . . . . . . . . . . . . . . . . . 3-92
Inserting a Validate task into a workflow process . . . . . . . . . . . . . 3-93
Finding error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98
Task behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99

Chapter
3 Teamcenter 8 release notes
Release notes are comprised of product release notes (known problems in the software
and workarounds) and documentation release notes (corrections to documentation).
Teamcenter 8 product release notes

The following notes are new as of the Teamcenter 8 release.
Installation and upgrade release notes

The following release notes pertain to installation and upgrade of Teamcenter.
• Some values entered in TEM are not saved during installation
In Teamcenter Environment Manager, some values you enter, such as lists of
hosts, are displayed in table format. If you do not press Enter after entering a
value in one of these tables, the value may not be saved. For example, in the FSC
Service Additional Group Sites panel, if you enter a value in the FSC ID column
and then click Next, the value you entered may be lost.
How to work around or avoid
Press Enter after entering any value into a table in Teamcenter Environment
Manager.
• Alias objects must be migrated to Identifier objects

Alias object functionality is completely removed. The new alternative to Alias
object functionality is AliasId (Identifier) functionality.
You must migrate Alias objects to Identifier functionality if your enterprise
ever created Alias objects.
1. Migrate Alias business objects in the database.

You must use the migrate_alias utility to migrate Alias business objects to
Identifier business objects.
Use the migrate_alias utility to migrate Alias data. See the documentation
for the migrate_alias utility in the documentation set for the version of
Teamcenter you are upgrading from.
During upgrade, old Alias data is removed from the database.

Chapter 3 Teamcenter 8 release notes
Note
Because the migrate_alias utility is available only in prior versions
of Teamcenter, you must perform migration in earlier releases only.
For example, if you are upgrading from Teamcenter Engineering 2005
SR1 to Teamcenter 8, perform migration in the Engineering 2005
SR1 release itself. If you are upgrading from Teamcenter 2007 to
Teamcenter 8, perform migration in Teamcenter 2007.
2. Clean up Alias business objects customizations in a custom template project.

For example:
– You have a Teamcenter 2007 database with Alias business object
customizations.
– You have also created a template project for your customizations in the
Business Modeler IDE.
– You have executed the migrate_alias utility on your Teamcenter 2007

database.
If you are a customer belonging to such a scenario, you must fix your custom
template project to ensure that the Alias related data model objects are
removed. This cleanup must be done in your Teamcenter 2007 template
project before working with the Teamcenter 8 Business Modeler IDE.
Customization example:
– A customer created subtypes of the Alias business object, where
Supplier is a secondary business object that is a subtype of Alias, and
Supplier1 is a primary business object that is a subtype of Alias.
– A customer defined an LOV named SupplierList and attached it to the

context type property on the Supplier business object.
If the customer template with the above two customizations directly imports
a project into Teamcenter 8 Business Modeler IDE, the client fails the
customer template import and displays the following errors in the console
view:
Model Error: D:\workdir\thog_mp6_test\mp6temp\extensions\business_objects.xml
Line:3 Column:130 Undefined Class Alias (parentClassName)
in TcClass Supplier1.
Line:4 Column:86 Undefined Business Object Alias (parentTypeName)
in TcStandardType Supplier.
Line:5 Column:91 Undefined Business Object Alias (parentTypeName)
in TcStandardType Supplier1.
Line:12 Column:18 Undefined Business Object Supplier (typeName)
in TcLOVAttach SupplerList.
Project mp6temp failed to load correctly!
Please fix all errors and reload project before proceeding.

Teamcenter 8 release notes
3. Remove the old Alias customizations:

a. Use the Teamcenter 2007 Business Modeler IDE client to remove all the
Alias business object customizations.
b. Reload the data model using the Reload Data Model menu command and
ensure there are no errors reported in the Console view.
c. Import the template into the Teamcenter 8 Business Modeler IDE.
• Queries other than English not present after installation or upgrade

During installation or upgrade to Teamcenter 8.0 and Teamcenter 8.0.1, the
default queries for locales other than English are not installed. Locale clients
always display English query names.
1. Set up the proper default language using the preferences_manager utility,

for example:
preferences_manager -u=admin_user -p=password
-g=dba -mode=import -preference="TC_language_default" -action=OVERRIDE
-values=desired_language
Replace desired_language with one of the supported locales: cn, cs, de, en,
es, fr, it, jp, kr, ru, or tw.
2. Import the default queries using the default_queries utility, for example:
default_queries -u=admin_user -p=password -g=dba
• Dispatcher client does not support Security Services

When Teamcenter is installed in the Security Services enabled mode, the
Dispatcher client fails to start up, and displays an access denied exception.
Disable Security Services for the Dispatcher client. All the other components can
still be Security Services enabled, but the Dispatcher client should be installed
on a separate machine that is not Security Services enabled. If they must be
on the same machine, a new TC_DATA location should be associated with a
Dispatcher client that is not Security Services enabled.

• Rich Client Lite Edition is unavailable

When you install the Rich Client Lite Edition, the full Teamcenter rich client
is installed.
1. After the rich client installation, remove the following plug-in JAR files from
the Teamcenter-installation-root/portal/plugins directory:
com.teamcenter.rac.cme.cmereport_8000.0.0
com.teamcenter.rac.padpdf_8000.0.0
jfreechart
com.teamcenter.rac.accessmanager_8000.0.0
com.teamcenter.rac.aif.registryeditor_8000.0.0
com.teamcenter.rac.appearanceconfiguration_8000.0.0
com.teamcenter.rac.architecturemodeler_8000.0.0
com.teamcenter.rac.auditmanager_8000.0.0
com.teamcenter.rac.authorization_8000.0.0
com.teamcenter.rac.cae.ase_8000.0.0
com.teamcenter.rac.caese_8000.0.0
com.teamcenter.rac.caese_dm_8000.0.0
com.teamcenter.rac.charts_8000.0.0
com.teamcenter.rac.classification.icadmin_8000.0.0
com.teamcenter.rac.classification.icm_8000.0.0
com.teamcenter.rac.cme.collaborationcontext_8000.0.0
com.teamcenter.rac.cme.fse_8000.0.0
com.teamcenter.rac.cme.mpp_8000.0.0
com.teamcenter.rac.cme.mrm_8000.0.0
com.teamcenter.rac.cme.pmp_8000.0.0
com.teamcenter.rac.commands.report.reportdesigner_8000.0.0
com.teamcenter.rac.commandsuppression_8000.0.0
com.teamcenter.rac.crf_8000.0.0
com.teamcenter.rac.databaseutilities_8000.0.0
com.teamcenter.rac.designcontext_8000.0.0
com.teamcenter.rac.dpv_8000.0.0
com.teamcenter.rac.ecmanagement_8000.0.0
com.teamcenter.rac.edalib_8000.0.0
com.teamcenter.rac.eintegrator.eintadmin_8000.0.0
com.teamcenter.rac.organization_8000.0.0
com.teamcenter.rac.plmxmlexportimportadministration
com.teamcenter.rac.project_8000.0.0
com.teamcenter.rac.pse_8000.0.0
com.teamcenter.rac.querybuilder_8000.0.0
com.teamcneter.rac.requirementsmanager.win.embeddedword_8000.0.0
com.teamcenter.rac.requirementsmanager_8000.0.0
com.teamcenter.rac.schedule_8000.0.0
com.teamcenter.rac.setupwizard_8000.0.0
com.teamcenter.rac.smb_8000.0.0
com.teamcenter.rac.subscriptionmonitor_8000.0.0
com.teamcenter.rac.tctdv_8000.0.0
com.teamcenter.rac.tdv_8000.0.0
com.teamcenter.rac.tracelinks.ui_8000.0.0
com.teamcenter.rac.ui.advanced_8000.0.0

com.teamcenter.rac.validation_8000.0.0
com.teamcenter.rac.vis_8000.0.0
com.teamcenter.rac.vm_8000.0.0
com.teamcenter.rac.workflow.processdesigner_8000.0.0
com.teamcenter.rac.workflow.processviewer_8000.0.0
PLMContainerProxy
scheduling_rac_interface_8000.0.0
2. Do not install the following rich client add-ons:

GM Overlay for Rich Client
SCM ClearCase for Rich Client
Embedded Software Manager for Rich Client
Rich Client Lite Edition does not support these add-ons.
3. Delete the following run-time configuration before you run the Rich Client
Lite Edition:
C:\Documents and Settings\user-id\Teamcenter\RAC\8000.0.0

Lifecycle Visualization installation release notes
The following release notes pertain to installation and upgrade of Lifecycle

Visualization.
• Embedded viewer installation reports file registration error
During installation or uninstallation of the Teamcenter embedded viewer, if
Microsoft Visio is not present on the host, the installer displays the following
error:
Files(s) failed to self-register:
C:\Program Files\Common Files\UGS Shared\TcVis\VP3DGeomAssetData.dll;
C:\Program Files\Common Files\UGS Shared\TcVis\VPVisioAddin.dll

Dismiss the error message and proceed. If there are no other errors, the
installation succeeds. The error occurs because Microsoft Visio is not present.
You will not be able to view Microsoft Visio files in Teamcenter.
• Lifecycle Visualization and rich client viewer versions must match

With Teamcenter 8, the stand-alone Lifecycle Visualization and rich client
viewers are released together and you must use the same release version for
each. For example, mixing an earlier Teamcenter 8 rich client installation with
a later Lifecycle Visualization installation may cause the rich client viewer to
stop working.
The versions must remain in tandem, or you must copy the
SingleEmbeddedViewer.jar file from the Program folder in Lifecycle
Visualization to the plugins folder in the rich client. The old JAR file must be
completely replaced. Upgrading the rich client installation to a later version of
the viewer automatically upgrades any stand-alone viewer already installed.
• Over-the-Web Installer nonroot user installation of Lifecycle

Visualization not interoperable with NX
Lifecycle Visualization places files in a root folder used by NX to determine
interoperability. The folder usually needs to be created by a user with rights to
the root folder. However, the Over-the-Web Installer does not require users to
have access rights to the root. Although the warning is written to the Lifecycle
Visualization install.log file, no warning is displayed by the Over-the-Web
Installer.
Either run the Over-the-Web Installer as a user with rights to the root, or create
the ugs directory before starting the Over-the-Web Installer and give read and
write permissions on the ugs directory to the user running the Over-the-Web
Installer.

Online help installation release notes
The following release notes pertain to installation of Teamcenter online help.
• Long file names require PUBS kit to be zipped for release media
Current topic IDs in source files create HTML files that have names longer than
are supported by the ISO standard for DVD creation. As a result, the PUBS kit
must be zipped into a ZIP file on the DVD.
Before installing the online help for Teamcenter, the PUBS ZIP file must be
unzipped.
• Using Firefox 3.0.5 with the UNC path for online help
Most customers install and launch the documentation HTML using the http://
protocol, which is fully supported. However, Firefox 3.0.5 has a default security
setting that prevents the help from launching correctly from a UNC path (file:///).
To change this setting, you must change the value of the
security.fileuri.strict_origin_policy preference:
1. In the address bar, type about:config.
2. In the Filter box, type security.fileuri.

The security.fileuri.strict_origin_policy preference is displayed. It is set to
true by default.
3. Double-click the value to toggle it to false.
4. Exit the browser and restart it. If you check the settings, you see that the
value is set to false.
• WebLogic 9.1 deployment of Teamcenter with online help fails

When installers of Teamcenter thin client include the Teamcenter - Online Help
solution and attempt to deploy the tc.war or tc.ear files using WebLogic 9.1, the
deployment fails. The exception error message in WebLogic 9.1 states:
Probably the string length of the path of the file being extracted was too long
WebLogic 9.1 cannot handle long path names found in some books in the
Teamcenter online help collection.
Use WebLogic 10 or 10.3.

Usage release notes

The following release notes pertain to the usage of Teamcenter.
• Access to the Classification Administration application

Classification Administration allows non-dba users to create, modify, and save
administration data even if the ICS_admin_requires_dba preference is set
to True.
You can protect Classification Administration data by restricting write privileges
to non-dba users through Access Manager.
To protect the classification hierarchy, click on the SAM Classification Root
node in the classification hierarchy panel and create an ACL to revoke write
privileges to non-dba users.
You can protect dictionary attributes, key LOVs, and views by revoking write
privileges on the following classes using Access Manager.
Has Class(unct_dict)
Has Class(stxt)
Has Class(bldb0)
Create these rules under the in-CLASS rule node in the rule tree.
• CAD BOM Alignment (CBA) preferences and search for Teamcenter

BOM entities available in Teamcenter 8
Preferences related to CAD BOM Alignment should not be available because
CAD BOM Alignment and Teamcenter BOM are not supported in Teamcenter 8.
Additionally, line of usage query in Multi-Structure Manager (formerly called
Collaboration Context) should not be available in Teamcenter 8.
Users should not attempt to perform CAD BOM Alignment actions in Teamcenter
8. Users should not provide values for preferences that start with Usage.
• Rich client Checkout Explorer dialog box does not support remote
components
The rich client Checkout Explorer dialog box does not display the components of
a BOM view revision if it contains any remote components. Remote components
are owned at other sites and have not yet been imported using Multi-Site.
Use the view folder under the revision containing the affected BOM view revision
to select additional components to check out.

• Some Tools menu commands not supported in As-Built Manager

The following commands are visible on the As-Built Manager Tools menu but
are not supported for As-Built Manager:
– Effectivity→Revision Effectivity
– Effectivity→Effectivity Mapping
– Effectivity→Occurrence Effectivity
– Variants→Unlink Variant Item
– Variants→Update Variant Item

Do not use these commands in As-Built Manager as they are not supported.
• Impact Analysis view missing some toolbar items

If you use the rich client on some Windows operating systems (XP 32-bit, Vista
32-bit, Vista 64-bit, or Server 2003), the Find in Display box and the Where and
Depth lists may be missing from the Impact Analysis view toolbar. This is an
Eclipse problem.
In the Microsoft Windows Display Properties dialog box, click the Appearance
tab and change the selection in the Windows and buttons list from Windows
Classic style to Windows XP style.
In the case of Windows Server 2003, before accessing the Windows XP style from
the Display Properties dialog box, ensure that the Themes service is started
(this is disabled by default). Perform the following steps to enable themes on
Windows Server 2003:
1. Go to the Services applet in Administrative Tools (or click Start, then Run,
and type services.msc and click OK).
2. Find the Themes service, right-click and choose Properties, and select
Automatic instead of Disabled in the startup type box.
3. Click Apply.
4. Right-click the Themes service and choose Start.
5. Click OK.
For more information, see the following Web page:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=248433

• ECAD library does not support importing and exporting items with
the space characters
If an item’s footprint or symbol ID field contains spaces, the ECAD library
cannot import or export the item.
Use the ECAD library tool to replace the spaced with a character.
• ECAD library import cannot update properties for existing parts

The ECAD part library uses the Teamcenter Import Export module (TIE) and
Briefcase to import parts into Teamcenter. TIE does not allow updating existing
part properties. If a part is imported from two libraries, it is assigned only to the
first imported library. When users synchronize with a second library, although a
part is in the export list, it is not imported.
Manually update published part properties.
• Classification import and export fails on ECAD library items

The Classification application has the concept of unit bundles. For example,
distance is measured using units in a bundle, such as millimeters, centimeters,
meters, inches, and so on. Among units in a bundle, one of them is known as the
base unit, and its attribute value is saved into the database.
However, the Classification import/export layer does not provide APIs to access
subunits other than the base unit. This leads to ECAD library integrations
failing during import when the value is not in the base unit.
Avoid using unit bundles for ECAD attributes in ECAD tools as well as in
Classification.
• Non-English characters are not displayed correctly in a text file

(First published Teamcenter 8
Some of the characters in a text file are not displayed correctly on non-UTF-8
client connecting to a UTF-8 compliant server.
When the server is UTF-8 and the clients are non-UTF-8 clients (for example,
Japanese), text files must be edited only on a client having the same character
set as the text file; otherwise, data loss can occur. Also, when these text files are
not viewed on a system that does not have the same character set as the client,
characters may not be correctly displayed.

• Microsoft Project Plugin 8.0 support

Importing a project schedule using the MS Project integration does not work.
Use Microsoft Project Plugin 8.0. Teamcenter – Microsoft Project Plugin 8.0 is
compatible with Teamcenter 8 and is not compatible with previous versions.
• Unsuccessful logon on Windows Vista clients when enabled for Security

Services using TcSS
When logging on using the Teamcenter rich client on Windows Vista, the
following message appears:
Login was unsuccessful.:
Unable to detect SSO session
This message indicates that the rich client is unable to find the Security Services
session file on the client machine. Vista introduced the concept of the Internet
Explorer sandbox where data is stored on the client machine on behalf of an
untrusted URL in an area sequestered from any other applications. Therefore,
when Internet Explorer runs in the sandbox, the Security Services session
file is written inside the Internet Explorer security sandbox context. Other
applications and processes trying to use Security Services cannot read the file.
This includes the rich client and any other SOA clients.
Set the SSO URL as a trusted site in Internet Explorer. This allows Internet
Explorer to avoid running in the security sandbox when it creates the session
file, leaving the file visible to other processes running for the user.

• Incorrect file name displayed in thin client file download dialog box in
Internet Explorer 6.0
An incorrect file name is displayed in the file download dialog box when
attempting to view a file with a .prt extension from a UGPART dataset from the
thin client in Internet Explorer 6.0.
This appears to be a problem with compression in Internet Explorer 6.0. One
potential workaround is to upgrade to Internet Explorer 7.0 or use a different
browser such as Mozilla.
If Internet Explorer 6.0 must be used, another potential workaround is to
disable file transfer compression for files with a .prt extension in the FMS
subsystem. To do so, add the FSC_DoNotCompressExtensions property to
the <fscdefaults> element of the fmsmaster configuration files and include the
prt extension in the value as follows:
<fscdefaults>
<property name="FSC_DoNotCompressExtensions"
value="bz,bz2,cab,deb,docx,docm,ear,gif,gz,jar,jpeg,
jpg,jt,lha,lzh,lzo,mp3,mp4,mpg,prt,rar,rpm,sit,
taz,tgz,war,xlsx,xlsm,z,zip" overridable="true" />
</fscdefaults>
After you change the fmsmaster configuration files, either reload the
configuration files or stop and start the FSC servers to use the new value.
• Simulation configuration is not accessible in four-tier client

When a user attempts to access the simulation tool configuration from a four-tier
client, it may appear that no tools are configured when they actually are. This
may occur when a user tries to launch a tool using Tools→Launch Simulation
Tool from CAE Manager, or when an administrator tries to configure a tool using
Edit→Configure Simulation Tools from CAE Manager.
Users of this capability must either be using a two-tier client or a specially
configured four-tier client that provides access to the TC_DATA folder of the
Teamcenter installation. This problem will be addressed in a future version to
allow standard use of the four-tier client.

• FSC fails to start on reboot of UNIX systems

The FMS server cache (FSC) process can fail to start after a reboot of UNIX
systems. This failure can be caused by other services that the FSC process
depends on which have not yet reached an operational state.
For example, the ypbind service can take additional time to start. Because this
service was not operational at the time an attempt was made to start the FSC
service, the su operation failed to switch to the required user to start the FSC.
Correct the reason that the ypbind service is launching slowly. Because
Siemens PLM Software software is not directly contributing to the slow launch
of ypbind service, this resolution must be investigated by the respective IT
departments on a case-by-case basis.
A workaround is to add a pause in the startup script. A sleep value of 120 seconds
was found to be sufficient in test systems. The sleep command must be added to
the startup script in the rcname.d directory. Do not modify the rc scripts under
the $TC_ROOT directory as these scripts are not the ones first called.
Note
Renaming the rc script in the rcname.d directory to force the service to
boot later in the boot order did not provide sufficient time to allow the
ypbind service to start in test systems.
• Highlighting the select-signoff-team task is chatty in Workflow

The Select-signoff-team task has three resource pools and one user already
assigned in the user inbox. When the task is selected with the task view active,
the chattiness monitor catches this network call chattiness:
The last 56 calls happened in 4.674227823 seconds
On a customer WAN with 0.175 second latency, this could be 14.474227823

seconds.
Currently, there is no workaround for this problem.
• Copying from the Name box pastes a link

In the Summary tab, when you copy text from the Name box and paste it to
Notepad using Ctrl-C and Ctrl-V keys, the URL link is pasted instead of text.
Select the text in the Name box, right-click, and choose Copy. The text is copied
and pasted to Notepad without problem.

• Teamcenter Publish is not supported in Teamcenter 8

Lifecycle Visualization crashes when a publishing page dataset is selected and
displayed.
Do not view a page dataset or use work instructions.
• Remote import crashes Windows server

Remote import in background mode can fail with a marshalling error when
invoked from a Windows based platform (Windows 2003 server or Windows
XP client).
Perform remote import in the foreground mode. Remote import in background
mode works fine on all other platforms.
• WEB_use_activex_lov preference setting for Internet Explorer 6

Due to an issue supporting overlapping elements (z-index) in Internet Explorer
6, ActiveX is used to support menus.
Internet Explorer 6 requires the WEB_use_activex_lov preference to be set to
yes.

Client for Office

The following release notes pertain to usage of Client for Office.
• Keyboard input not accepted from task pane controls in Client for Office
In some conditions, the text box input controls in the Client for Office task panes
may not accept keyboard character input. Whitespace keys (like the space
bar and arrows) work, but letter keys are not recognized. Copy and paste are
functional using the clipboard. This occurs in the Advanced Search criteria
input fields and the Check-In task pane. Other controls or task panes may
exhibit similar behavior.
This is a known issue with the Microsoft .NET 3.5 run time. Installing the .NET
3.5 Service Pack 1 addresses the issue.
There is a manual workaround. If the text entry control does not display
keyboard characters, you can paste (Ctrl+V) some characters into the control.
Once this is done, the control starts to accept keyboard input as normal.
• Cannot save changes for a checked-out Outlook dataset

Using Client for Office, a user opens a Microsoft Outlook e-mail dataset, edits
the e-mail, and clicks the Save button on the Teamcenter menu. The changes
cannot be saved to the same dataset.
Choose Save As to save a copy of the e-mail to Teamcenter as a new dataset.
• No integration between Office Live and Client for Office add-ins

Using Requirements Manager within the rich client, the user opens a
requirement in the embedded Microsoft Word window and makes edits that
he wants to save.
When the requirement dataset is opened in the embedded Microsoft Word
window, the Client for Office add-ins tab is displayed. When the user attempts to
save the requirement dataset using the Client for Office menu, Client for Office
code does not recognize the Teamcenter object context and does not know where
this dataset came from within Teamcenter.
Do not use Teamcenter menu. When the document is opened from the rich
client, the Office Live add-in application disables the Office save user interface
and presents its own save button. The user should use this save button (not
the Teamcenter save user interface).
• Input not accepted from task panes

Using Client for Office, a user opens a Microsoft Office document, clicks the
Teamcenter tab, and then clicks the Browse button from the Navigation and
View ribbon. The user backspaces or tabs to the Enter Item ID box and attempts
to type a search query value. Typing text into the box results in no text being
entered, as if the text box is read-only. This same problem exists for the
advanced search query.


The problem is fixed by the .NET Framework 3.5 Service Pack 1, found at the
following URL:
http://www.microsoft.com/downloads/details.aspx
?familyid=AB99342F-5D1A-413D-8319-81DA479AB0D7&displaylang=en
• Custom cascading LOV problem

When using Client for Office, custom cascading lists of values (LOVs) do not
work when creating a new item that requires multiple levels of cascading LOVs.
Use the rich client to create these item types instead of Client for Office.
• Checked-out dataset cannot be saved

A user double-clicks a Microsoft Office dataset from the rich client and launches
the Office application. Client for Office (add-in) loads and the Teamcenter tab
is displayed. The user edits the document and clicks the Save button in the
Teamcenter menu. The rich client client and Client for Office (add-in) are not yet
integrated, and therefore have no mechanism by which to transfer Teamcenter
objects back and forth.
Choose Save As to save a copy of the file to Teamcenter as a new dataset. Or
do not use the Save button on the Teamcenter menu, but use the standard
Office Save button, and the file is uploaded to the rich client when the Office
application closes.
• Expanding a folder is slow in Client for Office

Expanding a folder in Client for Office using the Browse navigation control
results in a slow response when the folder contains a large number of child
objects. An inefficient algorithm causes the rendering of the list of folder objects
to take a long time.
The Folder View navigation control can be used and does not display this
performance issue.
• Unsupported query type error in Client for Office

In Client for Office, if you perform an advanced search by selecting the
Checked-Out Objects query, the following error message appears:
Unsupported query type

Use the rich client or thin client for searches of this type.

Content Management
The following release notes pertain to usage of Content Management.

• Incorrect tool tips in a Content Management dialog box
In the Create Language Item dialog box, tool tips do not match behavior.
• S1000D is supported only if the Content Management Web server is

running on Windows or LINUX platforms
S1000D is supported only if the Content Management Web server is running on
Windows or LINUX, because the SGML parser is not available on the other
platforms.
• Inoperable items in the Content Management user interface

The following items in the Content Management user interface are inoperable:
– Windows→Preferences→ContentManagement→Views→Inbox
– In the File→New→New Content Management Permissions dialog box, the

following permissions are inoperable:
xdShowViewContentInbox
xdShowPdmView
xdShowPdmResourcesView
xdShowProjectOrgansiationFolderView

These items will be operational in a future version.

Lifecycle Visualization
The following release notes pertain to usage of Lifecycle Visualization.

• Lifecycle Visualization viewer appears in My Teamcenter and cannot
be turned off
If the user sends a valid object to the Lifecycle Visualization viewer and switches
to another perspective while the viewer is loading up, the viewer area is
displayed in the current perspective. The toolbars and menus associated with
the viewer are also displayed in the current perspective.
1. Close the viewer area by clicking the x on top of the viewer tab.
2. Choose Window→Reset Perspective.
3. Click OK in the confirmation dialog box to reset the perspective.

The viewer is closed and the current perspective is restored to its default
layout.
• Multiple documents open in rich client Lifecycle Visualization causes

authentication dialog box
A logon dialog box sometimes appears when opening multiple documents
simultaneously in the rich client Lifecycle Visualization viewer.
If you do not have Security Services installed, log on with the dialog box and
proceed normally. To avoid the dialog box, open documents one at a time.
If you have Security Services installed, make sure the first item you open in the
Lifecycle Visualization viewer is a single document. You should not see the
logon dialog box for the rest of the session. Otherwise, the logon dialog box
may cause the system to hang.
• Part may not be visible on UNIX

On all UNIX platforms, when launching a single part into the viewer, the part
may not be immediately visible in the 3D Viewing window.
Performing a Fit All operation (for example, Navigation→Fit All) in the 3D
Viewing window renders the part correctly.

• Dialog box with errors may appear when closing several parts
In the Lifecycle Visualization viewer, when several documents are open, and
these documents are all closed at once (for example, by using File→Close), a
dialog box may appear with the following warning text:
Internal or unexpected software error

Close the dialog box. This is not a serious failure, and the software continues to
operate normally.
• Lifecycle Viewer corrupts the Customize Toolbar

If the Lifecycle Viewer is opened within the My Teamcenter perspective, it opens
all of its toolbars, and the Customize Toolbar and Restore Defaults menu items
(in the popup menu on the main toolbar ) are disabled.
Do not open the Lifecycle Viewer editor within My Teamcenter.

Manufacturing Process Planner
The following release notes pertain to usage of Manufacturing Process Planner.

• Crash on resequence of operations
In Manufacturing Process Planner, the server crashes on a resequence of
operations if a loop exists.
• Calculate allocated time

In Manufacturing Process Planner, when an item is consumed in an operation,
allocated time calculations do not always work. In addition, the calculate
allocated time feature does not consider flows.
Multi-Site
The following release notes pertain to Multi-Site implementation.

• Remote checkout fails between Teamcenter 8 and Teamcenter 2007
in Multi-Site configuration
In a four-tier Multi-Site environment, remote checkout of an assembly between
Teamcenter 8 and a Teamcenter version earlier than Teamcenter 2007.1.MP7
fails if the assembly contains stubs.
Upgrade the pre-Teamcenter 2007.1.MP7 environment to Teamcenter
2007.1.MP7.

NX Integration
The following release notes pertain to usage of NX Integration.

• Bounding box objects are not generated when a part is saved from NX
6.0.3
When the part is saved from Teamcenter Integration for NX, the bounding box
objects are not created automatically. This problem occurs only with NX 6.0.3.
Other NX versions, such as NX 5.0.x, work as expected; that is, the bounding box
objects are created when a part is saved.
To generate the bounding box objects for NX parts, run the
create_or_update_bbox_and_tso utility with the appropriate command line
arguments.
For information about this utility, see the Utilities Reference.
Requirements Manager
The following release notes pertain to usage of Requirements Manager.

• Special characters in Requirements Manager
If you import a docx file in Requirements Manager that contains special
characters, the document paragraphs that contain these special characters are
not imported as body clear text. It results in errors messages when expanding
the requirements structure in Requirements Manager.
When users get an invalid xml error, they can remove the clear text property on
the bomline. After this property is removed, users do not see any exception on
the bomline. Users are able to view the clear text but can edit the requirement.
• Trace link options do not appear in the Manufacturing Process Planner

window
Trace link commands such as Start Link, End Link and Traceability Report are
not available from manufacturing applications.
Currently, users must use the My Teamcenter or Structure Manager application
to create trace links.

• Cascading LOVs are not supported in Excel Live and Word Live
Cascading lists of values (LOVs), including hierarchical and interdependent
LOVs, cannot be edited from the Live Integration with Excel or Word.
Currently, users must use the rich client to edit these properties.
• Excel Live is not enabled in Manufacturing Process Planner

Excel Live command is not enabled in Manufacturing Process Planner.
Users can send the list of objects to My Teamcenter, or open the structure in
Context Manager and export to Excel.
• Multichoice properties are not supported in Live Word

Editing of multichoice property values is not supported from the embedded Word
Live using the keyword mechanism.
Currently, users must use the rich client to edit these properties.

Schedule Manager
The following release notes pertain to usage of Schedule Manager.
• Multi-Site support for Schedule Manager

Some Schedule Manager functionality fails while working with remote data.
Although there is no data corruption, the system does not provide expected
results in some scenarios. Some of the failures require system restart.
Do not use Multi-Site with Schedule Manager.
• Properties for the summary task in the Properties dialog box cannot
be modified in Schedule Manager
Certain properties for summary tasks in the Properties dialog box cannot be
modified. For example, the Description box cannot be modified.
Certain properties like description can be updated through inline editing on the
task tree in Schedule Manager.
• Known issues with master subschedules

Following are known issues with master subschedules:
– Subschedule boundaries cannot be extended even after extending the master

boundary date.
– Updating the start and finish of a master schedule does not update the latest
start or earliest finish dates (the calculated fields) of the subschedules.
– Removing a subschedule from a master does not reset the earliest

finish/latest start attributes to null if it is not part of any master. (There is
no workaround for this, but it does not cause any functionality problems.)

Open the subschedules directly and run the recalculate schedule operation
(Menu→Schedule→Recalculate Schedule). Removing a subschedule from a
master does not reset the earliest finish/latest start attributes to null.
Note
The Latest Start and Earliest Finish dates are system calculated fields and
exist primarily in the case of master and subschedules. They sometimes
do not get updated when schedules are removed or schedule dates are
updated. You cannot update them manually.

• Problem viewing the subschedule calendar from the master schedule

You cannot view a subschedule calendar from within a master schedule. Only
the master schedule calendar is available.
Load the subschedule separately in the Schedule Manager to view the calendar.
To update the calendar, the master schedule and subschedule relationship
should be unlinked, updated, and relinked.
• Save As operation opens Schedule Manager but no menus appear

When you use the Save As action on a schedule with the Open on create
option selected, the saved schedule is opened in Schedule Manager. However,
the associated scheduling menus and the toolbar are sometimes not visible. A
similar problem occurs with program views during Save As and Create actions
with the Open on create option selected.
Do not select the Open On Create option while performing the Save As action or
creating a program view. Then open the schedule or program view after creation.
Another solution is to switch to the My Teamcenter application and then switch
back to Schedule Manager. Then the menus and toolbars appear.
• Problems with duplicate subschedules in the same master in Schedule

Manager
In Schedule Manager, the same subschedule exists more than once in a master
schedule and subschedule structure.
– Data from the subschedule is included more than once at the top-level
rollups such as Work Estimate and Work Complete. (There is no work
around for this problem.)
– Cut, copy, and paste functionality may not place the tasks in the desired
location if the duplicated subschedule is selected as the target of the paste.
– Updates to the duplicated subschedule or its tasks do not get reflected

properly in the user interface.

To resolve the cut, copy, and paste problem, do not select the subschedule itself
as the target of the paste, but select a task or milestone that is a sibling to the
subschedule.
To resolve the update problem, manually refresh the schedule after making a
change inside a duplicated subschedule.

Note
Adding duplicate subschedules to the same master is prevented.
Duplicates can only exist as subschedules of existing subschedules in
the master.
Siemens PLM Software recommends that you do not create master
substructures where the same subschedule is used more than once. This
type of structure is not supported.
• Choose a schedule template dialog box

In the template dialog box for status and priority property, internal values are
displayed instead of the string values.
The mapping between internal integer values and the actual string values for
Status and Priority properties is as follows:
– Status
Value Description
0 Not started
1 In progress
2 Needs attention
3 Complete
4 Abandoned
5 Late
– Priority
Value Description
0 Lowest
1 Low
2 Medium low
3 Medium
4 High
5 Very high
6 Highest

• Bill rate sorting issue

In Schedule Manager, columns are not sorted correctly in the Bill Rates dialog
box. Access this dialog box by choosing Schedule→Bill Rates.

Structure Manager
The following release notes pertain to usage of Structure Manager.
• Unable to create items in Structure Manager and requirements in
Requirements Manager in thin client
Creation of items in Structure Manager, and creation of requirements or
paragraphs in Requirements Manager, fails in the thin client. Teamcenter
displays an error message during these operations.
Create an item, requirement, or paragraph in My Teamcenter, copy the object,
and paste it under the desired location in Structure Manager or Requirements
Manager, as appropriate.
Teamcenter EDA
The following release notes pertain to usage of Teamcenter EDA.
• Released Teamcenter EDA design cannot be revised
If an ECAD design managed by Teamcenter EDA is updated to status of
Released in Teamcenter, you cannot revise the design using Teamcenter EDA.
Teamcenter EDA requires a checkout lock to revise.
Use the Teamcenter rich client or thin client to revise an ECAD design that
is in a released state.
• Revising the CCA from the rich client blocks a schematic save
If a schematic design has been previously opened or saved using Teamcenter
EDA, and the CCA of a schematic design is revised in the rich client, a
subsequent save of that schematic design fails with a message regarding the
BVR not being checked out on the original item revision. This problem is due to
nonsynchronization of the cache with the object in the rich client.
Refresh the cache with the latest data from Teamcenter by performing a purge
cache and a subsequent checkout:
1. Check in (without BOM) or undo the checkout of a schematic design.
2. Choose Purge Cache using Teamcenter EDA.
3. Check out the design using Teamcenter EDA.
4. Update the design (if required).
5. Save the design back to Teamcenter.

• Revised Teamcenter EDA design cannot be opened

If a Teamcenter EDA design is revised in the rich client using the
CopyAsReference deep copy rule for the EDA dataset, the old design is opened
and cached.
When revising in the rich client, ensure the EDA dataset is using the
CopyAsObject deep copy rule. In the revise wizard:
1. Go to the Define Attached Data dialog box.
2. In the left pane labeled Source:, find the EDA dataset.
3. Click the button to the right of the dataset and choose Copy As Object.
4. Fill in the rest of the revise wizard (if required), or click Finish to perform
the revision.

Administration release notes

The following release notes pertain to the system administration of Teamcenter and
the use of the administration applications.
• data_sync utility with –cp option receives failed to delete checkpoint
dataset error
When a exported assembly is synchronized using the data_sync utility with
the –cp option for checkpoint, the command may fail with this error message:
Failed to delete checkpoint dataset. Error - 14104. This occurs because
TCFS and FSC both access this database, and TCFS attempts to delete the
checkpoint dataset while FSC still controls it. Though the data_sync utility
shows a failure, the data_sync utility actually works successfully.
Change the FSC_MaximumIdleFileHandleAgeMs FSC configuration
element, which is set to 10,000 milliseconds (10 seconds) by default. Change it to
1000 milliseconds to solve this issue.
• Specification transfer from Interspec to Teamcenter

Specification transfer from Interspec to Teamcenter fails when the
PS_Find_Number_Validation preference is set to true.
The preference PS_Find_Number_Validation determines whether Teamcenter
validates find numbers. If validation is enabled with this preference, an error
appears when the find number is zero or not unique within the parent structure.
Specifications transferred from Interspec to Teamcenter do not have find
numbers. Therefore, this preference must be set to false. This is the default
setting for the preference and should not be changed if the Interspec-Teamcenter
integration is used.
Ensure that the PS_Find_Number_Validation preference is set to false.
• UNIX IDSM issue running UTF-8 character set

The data_share utility fails, and the error states it cannot find an item if
the item_id attribute contains non-English characters. This problem occurs
on UNIX systems when the IDSM daemon is not started with the identical
Teamcenter execution environment settings. By default, the IDSM server
process is started by the UNIX idsminetd daemon in the C locale.
To establish a UNIX Teamcenter UTF-8 character set execution environment,
the following variable settings must be added in the run_tc_idsm.sh IDSM
startup script file located in TC_BIN:
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8

• TcXml import fails when QSEARCH is set to true

TcXml imports fail when cacheless search (QSEARCH) preferences are set to
true. To avoid corrupting database data, TcXml import aborts import operation.
A message is written into the importer log file.
The site administrator should define QSEARCH preferences at the user level
and set them to false for users making TcXml imports. Set the following
preferences to false:
QS_QSEARCH_ENABLED=false
QSEARCH_update_enabled=false
QS_SPATIAL_ENABLED=false
QS_BBOX_GENERATION_ENABLED=false
QS_BBOX_GENERATION_FROM_NX_ENABLED=false
QS_TRUSHAPE_GENERATION_ENABLED=false
• Multiprocess ODS is not supported on HP-UX 11.31 (11i v3)

Multiprocess ODS does not operate on HP-UX 11.31. HP-UX 11.31 is also
identified as 11i v3.
Configure the ODS for nonmultiprocess operation or deploy multiprocess ODS
on HP-UX 11.23 (11i v2).

Customization release notes

The following release notes pertain to customizing Teamcenter.
• Custom attributes for CAE items cannot be accessed from the New CAE
Item wizard
Custom attributes on the primary business object for CAE Items cannot be
accessed from the New CAE Item wizard in My Teamcenter, CAE Manager, or
CAE Structure Designer applications.
Use the Business Objects view in the Business Modeler IDE to view Item or
ItemRevision business objects.
Item is the most common business object under which you create a new business
object. Use the Item business object or its children when you want to create
business objects to represent product parts. When you create a business object
using Item (or one of its children) as the parent, in addition to the new business
object, you can also create an item master form, an item revision, and an item
revision master form.
Attributes that are defined on an item master form or a revision master form are
presented on the New CAE Item wizard. The method of putting attributes on
these forms should continue to be used when creating custom item types that are
subtypes of the CAEItem business object and its children.
• Changes to revise and save as ITK behavior

In Teamcenter 8, hard-coded deep copy rules are removed from the internal
server code and defined as explicit deep copy rules in the Foundation template.
This affects the ITK behavior for the Revise and Save As operations of
ItemRevision business objects.
The ITK changes do not affect any existing customer code. You must be aware of
the changes in the ITK behavior for future custom code changes.
Prior to Teamcenter 8, some of the deep copy rules applied during the Revise
and Save As operations of an ItemRevision business object were hard coded.
They are now exposed in the Foundation template as explicit deep copy rules
on the ItemRevision business object. This allows customers to override the
default deep copy behavior.
Beginning at Teamcenter 8, a call to any one of the following ITK automatically
invokes the ITEM_perform_deepcopy ITK.
ITEM_copy_rev
ITEM_copy_item
ITEM_copy_item_with_masters
ITEM_copy_rev_with_master

This change is to ensure that customers always perform a deep copy after an
ItemRevision business object is revised or saved.
If any old custom code (prior to Teamcenter 8) invokes the
ITEM_perform_deepcopy ITK, the custom code remains unaffected. This is
because the ITEM_perform_deepcopy ITK first checks if the object is already
revised or saved. If yes, the deep copied objects are returned without performing
deep copy again. If no, deep copy rules are applied.
Therefore, beginning in Teamcenter 8, there is no requirement for customer
code to invoke the ITEM_perform_deepcopy ITK after a call to any one of
the ITK listed above.
Previously, the Save As operation on an Item object carried forward only certain
relations of the associated ItemRevision object. Beginning in Teamcenter 8,
when a Save As operation is performed on an Item object, the old relations of the
associated ItemRevision object are carried forward based on the deep copy rules
in the database. Therefore, the deep copy rules in the database is the deciding
factor for copying relations even during save as operations on an Item object.
In Teamcenter 8, there is one action that is still hard coded. If there exists a
generic deep copy rule to perform the Copy As Object action for all its related
objects, and if the related other side object happens to be an ItemRevision
object, the system always performs the Copy As Reference action.
For more information about deep copy rules, see the Business Modeler IDE Guide.
• Build server code on multiple platforms

The build process in the Business Modeler IDE is designed to build server code
on Windows platforms only. The Business Modeler IDE should provide the
option to generate multiple platform makefiles.
If you intend to build the same custom server code on multiple platforms, you
can use the same project to generate the code and makefiles for each platform.
Perform the following steps:
1. On Windows systems, create your new project in the Business Modeler IDE,
and add new business objects, properties, and operations. Generate code
and build server code.
For more information, see Build server code on Windows.
2. For the additional platforms, first copy the new template directory and
subdirectories, for example:
C:\apps\Teamcenter8\bmide\workspace\P8000.0.0\MyTemplate
3. Delete the template_location/output/server directory.
4. Import the project into the Business Modeler IDE by choosing

File→Import→Business Modeler IDE→Import a Business Modeler IDE
Template Project.
5. Change your project properties to reflect your new location and platform:
a. In the Navigator view, right-click your project and choose Properties.

b. In the left pane of the Properties dialog box, choose Teamcenter→Build

Configuration. Change the settings in the Build Configuration dialog
box for your platform.
c. In the left pane of the Properties dialog box, choose Teamcenter→Code

Generation. Change the settings in the Code Generation dialog box for
your location, for example, in the Base Path box.
Note
If you are moving from Windows to UNIX, select the Folders check
box and change the back slashes to forward slashes.
6. Modify the .project file to update the source folder and generated source
folder location.
7. Generate code by right-clicking the template project in the Business Objects

view and choosing Generate Code→C++ Classes.
Note
If moving from Windows to UNIX, first update the C++ build command
in C/C++ Development Tools (CDT) to use make.
This generates all the C++ code and the makefiles on the new platform. Building
from CDT or a command line using the makefiles is now set up for the new
template and its libraries. Successive builds for the same libraries can be
shortened by copying the generated C++ code to the additional platforms and
reusing the same makefiles.
• Default value for the Enabled property constant is not honored

In the Business Modeler IDE, the default value for the Enabled property
constant is not honored by the system.
Perform the following steps to duplicate the error:
1. When a new custom property is added to a business object in the Business
Modeler IDE, the property has default settings for Enabled and Modifiable
property constants, as shown in the following figure.
Default new custom property settings

Change the setting for the Modifiable constant from Read to Write, as shown
in the following figure.

Modifiable constant changed to write

No changes are made to the Enabled constant, and its value is still false.
2. Deploy the data model to the Teamcenter database.

The custom property value should not be editable in the user interface (such
as the rich client, thin client, or Excel Live). The system does not honor the
user setting and allows users to edit the property value in the user interface.

Override the attachment for the Enabled property constant even though its
value matches with the default value.
1. Change the Enabled property constant value from false to true, as shown in
the following figure. Note that the Overridden column for enabled constant
is checked.
Enabled constant changed to true
2. Save the data model.
3. Change the Enabled property constant value back to false, as shown in

the following figure. The property constants table displays that the value
is false and it has been overridden.

Enabled constant changed back to false

Note the difference between the Enabled constant in the first figure and the
last figure. In the first figure, the value for the Enabled constant is false and
the Overridden column is not checked. But in the last figure, the value for
the Enabled constant is false and the Overridden column is checked. This
means the default property constant attachment value has been modified.
4. Save the data model.
5. Deploy the data model to your database and test the user interface. The
property is not be editable in the user interface, and it can still be modified
programmatically.
This workaround is not only for customer-defined properties, but is also intended
for standard Teamcenter (COTS) properties.

Internationalization release notes

The following release notes pertain to the internationalization of Teamcenter.
• Code page 932

Teamcenter does not support Japanese characters from code page 932
(abbreviated as CP932, also known by the IANA name Windows-31J). This is
Microsoft’s extension of Shift JIS to include NEC special characters (row 13),
NEC selection of IBM extensions (rows 89 to 92), and IBM extensions (rows
115 to 119). The coded character sets are JIS X0201:1997, JIS X0208:1997,
and these extensions.
• BMIDE client not completely localized

Some areas of the Business Modeler IDE client are not completely localized.
Some menu items, wizards, and other elements are displayed in English in
non-English locales.
• Oracle database character set setting for corporate server installation

and upgrade
Upgrade of the GM Overlay template and its dependent templates fails with
error 54034 (The list of values has duplicate values.)
For example, the update log may contain an error similar to the following:
Delete | TcLOVValueAttach | Discipline LOV
| 54034|The list of values has duplicate values.

This problem applies to the GM Overlay template and any template that
contains characters that are not compatible with, or supported by, the character
set (NLS_CHARACTERSET) in the Oracle database.
If the GM Overlay template contains German characters, when it is deployed to
a database that does not support the German character set (WE8MSWIN1252),
German characters such as umlauts and the double s (ß) are stored as different
characters in the database. This causes the Business Modeler IDE comparator
to generate an incorrect delta file.
By default, when an Oracle database instance is created, it is set with the
WE8MSWIN1252 character set (option 1) unless the database administrator
specifically selects a different character set (option 3).

If the database administrator accepts the default character set in the

Initialization Parameters dialog box during Oracle database instance creation,
there are no issues with installing the GM Overlay template. However, if the
database administrator changes the Oracle database character set to anything
other than WE8MSWIN1252, installation or upgrade of the GM Overlay
template most likely fails.
To verify whether the character set is set correctly, run the following SQL
command:
SQL> select * from NLS_DATABASE_PARAMETERS;
Note
This problem can occur if any template having non-ASCII characters is
deployed to an Oracle database that has the character set to a value other
than WE8MSWIN1252.
For information about how to modify the database character set to work around
the problem, see the Oracle documentation.

Teamcenter 8 documentation release notes

The following documentation additions and changes will be incorporated in a future
version of Teamcenter.
Using documentation
Teamcenter documentation is delivered in PDF and HTML format.
Using PDF files
The PDF directory on the documentation distribution media contains Adobe PDF
versions of the Teamcenter online help. You can view these guides using Adobe
Acrobat Reader, which you can download free from Adobe at http://www.adobe.com.
From Acrobat Reader you can view these guides online and print selected pages or
entire guides. You can also search the complete online help collection by either
of the following means:
• Open the PDF index file, PDF\pdf\tc2008.pdx, in Adobe Acrobat.
• In Acrobat Reader, perform the following steps:

1. Click the down arrow next to the search text box and choose Open Full
Reader Search.
2. At the bottom of the Search dialog box, click Use Advanced Search Options.
3. Under Look in, choose Select Index.
4. In the Index selection dialog box, click Add, and then browse to the
PDF\pdf\tc2008.pdx file in the documentation distribution media.
If you copy the PDF online help collection from the documentation installation
media to a local drive and you want to be able to search the collection, make sure
you copy the entire contents of the PDF\pdf directory. This ensures the index file
(tc2008.pdx) and the PDF search indexes are included.
Note
On UNIX and Linux systems, the PDF\pdf directory referenced in this topic
is PDF/pdf.

Using HTML files
The HTML directory on the documentation installation media contains HTML

versions of the manuals.
The Teamcenter online help requires a Web browser that supports Java for the
search to work. The browser version and Java specification required for online help
depends on the operating system you are using. For information about supported
browsers and Java versions for your operating system, see the Siemens PLM
Software Certification Database:
Note
Several features of the online help system require the display of popup
windows; for example, searching the online help collection and viewing
graphics. If a popup blocker utility is installed on the Web server or client
workstation, you must configure the utility to allow popup windows from the
online help domain. Otherwise, the online help system does not function
correctly.

Access Manager Guide

The following release note pertains to the Access Manager Guide.
• Correction to cautionary statement
The following information replaces the first bullet in the Cautionary statements
topic:
– Do not modify access control lists (ACLs) referenced by rules on the System
Objects branch. Adding new rules, deleting rules, or in any way modifying
existing rules on the Systems Objects branch of the rule tree may result
in unpredictable behavior or loss of data. Modifying the Systems Objects
branch of the rule tree is not supported unless specifically advised to do so
by Siemens PLM Software.
Business Modeler IDE Guide

The following release notes pertain to the Business Modeler IDE Guide.
• New Business Objects view preferences
The following information will be added to Set Business Modeler IDE preferences.
Previously, you could choose either POM_object or WorkspaceObject to make
that business object the highest (root) object displayed in the Business Objects
view. Now you can also select either the BusinessObject or Item business objects.
Perform the following steps to change the Business Object view preferences:
1. Choose Window→Preferences.
2. In the Preferences dialog box, select Teamcenter.
3. Select one of the following under Business Object View Root to set the
business object that is the highest (root) object displayed in the Business
Objects view:
– BusinessObject
Displays all business objects, including run-time business objects.
– POM_object
Displays the business objects available for creating new business object
types.
– WorkspaceObject
Displays the objects that can be displayed in the end user workspace.
– Item
Displays the most commonly used business objects such as Item and
Document that are used to represent work objects to be tracked in
Teamcenter.
4. Click Apply.
5. Click OK.

• Correction to note about relation properties

The following corrected note will be added to Migrate preferences to data model
objects.
Note
If you are upgrading from an earlier version of Teamcenter to Teamcenter
8, you should verify that all of your relation properties are now managed
in the Business Modeler IDE. To verify, look in your preferences for each
<relation_type>_relation_primary preference that you added, and add
it to your custom template in the Business Modeler IDE.
For more information, see Add a relation property.
• Addition to user exits documentation

The following note will be added to Working with user exits.
Note
User exit attachments, unlike operation extension attachments, cannot
be attached at child business objects. User exit attached extensions get
defined and executed as call back only at a particular business object.
• Addition to extensions documentation

The following note will be added to Working with extensions.
Note
Extensions defined for a property of a business object cannot be attached
to that property at child business objects. They can be attached to that
property at the same business object. However, extensions defined for
a business object itself (not to its property) can be attached to a child
business object.
• Addition to relation business objects documentation

The following note will be added to Create a relation business object.
Following are some common kinds of relation business objects you can extend:
– Specification relations
Specification relations are detailed methods, designs, processes, and
procedures used to satisfy requirements. A specification relationship can
only be established with an item revision, not an item. The reason for this
is that although requirements may remain fairly constant for a product
(item), actual manufacturing methods, designs, processes, and procedures
may change drastically from model to model (item revisions). Extend
the IMAN_specification business object to create your own specification
relations.

– Requirement relations
Requirement relations are criteria that must be satisfied by this item or
item revision. However, requirements often do not specify how this criteria
should be satisfied. For example, a requirements relation may specify
maximum weight for an item revision but not how to construct it. Extend
the IMAN_requirement business object to create your own specification
relations.
– Manifestation relations
Manifestation relations are nondefining snapshots of a particular aspect
of an item or item revision at a particular moment in time. For example,
numerically controlled (NC) program files are a common manifestation.
Consider that they represent one aspect of an item revision (that is,
machining information) and that this information is only accurate so long as
the item revision does not change. If the item revision does change, the NC
program files may no longer be accurate and might need to be re-created.
Extend the IMAN_manifestation business object to create your own
specification relations.
– Reference relations
Reference relations describe a general nondefining relationship of a
workspace object to an item or item revision. This relation type can be
thought of as a miscellaneous relation type. Typical examples of reference
relations are white papers, field reports, trade articles, customer letters, lab
notes, and so on. Extend the IMAN_reference business object to create
your own specification relations.
• Addition to convert secondary business objects to primary topic

The following documentation will be added to Convert secondary business objects
to primary.
– The following will be placed at the end of the topic.

The following business objects are converted from secondary to primary
business objects in Teamcenter 8:
◊ Requirements Manager
RequirementsSpec
Requirement
Paragraph
SpecElement
◊ Aerospace and Defense
Drawing
ADSPart
ADSDesign
ADSDrawing
ADSTechDocument

◊ Document Manager
Document
◊ Structure Manager
Part
Design
– The following note will be placed in step 2 of the procedure:
Note
The Convert to primary context sensitive menu item is enabled only if
the selected business object satisfies the following conditions:
◊ The seleceted object is a secondary business object and a custom
business object.
◊ The parent of the selected object is a primary business object.
◊ The selected object is not derived under the ItemRevision

hierarchy.
– The following sentence will be placed in step 3 of the procedure after the
example of the business_model_updater utility:
Replace file-name with the name of the active extension file that contains
the data model definition for the converted business objects, such as the
business_objects.xml file.
C++ API Reference

The following release notes pertain to the C++ API Reference, an autogenerated
document containing C++ signatures for Teamcenter APIs.
• C++ API Reference contains API for Foundation only
C++ API Reference contains C++ API documentation for the Foundation
template only. C++ API documentation for other features will appear in later
Teamcenter versions.
Dispatcher Server Installation Guide

The following notes pertain to the Dispatcher Server Installation Guide guide.
• Dispatcher client not supported with Security Services
On Windows systems, the Dispatcher client cannot start if Security Services
is enabled on the host. If your Teamcenter configuration includes Security
Services, you must configure the Dispatcher client to bypass Security Services.
For more information, see the Getting Started with Dispatcher (Translation
Management) guide.

ERP Connect Integration Guide

The following release notes pertain to the ERP Connect Integration Guide.
• ERP Connect Toolkit switch
In the Global settings topic under Mapping schema, the following information
about the ERP Connect Toolkit switch is omitted.
–BOM_Pack_with_diff_seq_no
Indicates the sequence number, by default, is ignored while packing the
BOM in ERP Connect Toolkit.
If set to Y, the sequence number is considered; if the sequence numbers of all
occurrences match, the BOM is packed.
Getting Started with Aerospace and Defense

The following release notes pertain to Getting Started with Aerospace and Defense.
• Correction to procedures for performing searches based on relation
properties
The following information replaces the procedure in the Execute a saved query
based on properties on relations topic:
1. Open My Teamcenter.
2. Locate the quick search box at the top of the navigation

pane.
3. Click the menu button and choose Advanced.

The Search pane appears.
4. In the Search pane, click the Select a Search button .

The Change Search dialog box appears.
5. In the Change Search dialog box, expand the System Defined Searches
folder, and select the appropriate properties on the relations search query.
Note
Searches for properties on relations must first be created using the
Query Builder application. After you create the searches, they appear
in the System Defined Searches folder.
For information about creating searches based on properties on
relations, see Search queries based on properties on relations.
6. Click OK.
The Search pane displays the search attributes.
7. Enter the attribute values and click the execute button .
The following information replaces the procedure in the Execute a saved query
based on properties on relation in the thin client topic:

1. Start the thin client and open My Teamcenter.

For more information about starting the thin client, see the Thin Client
Interface Guide.
2. Locate the quick search box at the top of the navigation

pane.
3. Click the menu button and choose Advanced→More.
4. In the Change Search dialog box, click the System Defined Searches tab.
5. On the System Defined Searches tab, select an appropriate relation

properties search.
Note
Searches for properties on relations must first be created using the
Query Builder application. After you create the searches, they appear
in the System Defined Searches folder.
For information about creating searches based on properties on
relations, see Search queries based on properties on relations.
The search attributes associated with the relation query appear.
6. Enter the attribute values and click Find.

The search results are displayed in the Results section.
Getting Started with Dispatcher (Translation Management)

The following release notes pertain to Getting Started with Dispatcher (Translation
Management).
• Run the dispatcher client as a Windows service
The following corrected topic will be added to Configuring Dispatcher.
On Windows systems, you can optionally configure the dispatcher client as a
Windows service.
Note
If you run the dispatcher client as a service, Siemens PLM Software
recommends running the scheduler and modules also as a service.
1. If you use Teamcenter, set the TC_DATA and TC_ROOT system variables
as appropriate.
Examples:
TC_DATA=C:\Progra~1\Siemens\tcdata
TC_ROOT=C:\Progra~1\Siemens\Teamcenter8

Note
When you install Teamcenter, TEM automatically sets the
FMS_HOME system variable.
The Dispatcher Client service fails to start as a Windows service if you
do not set the TC_DATA and TC_ROOT system variables.
2. Run the runDispatcherClientWinService.bat file from the

DispatcherClient\bin directory.
3. From the Windows Services console, right-click DispatcherClientversion

service and choose Properties.
4. In the Log On pane, select the This account option to assign a logon account
for the Dispatcher Client service.
Note
You must provide administrator privileges for the Dispatcher Client
service.
5. Start the Dispatcher Scheduler.
6. Start the DispatcherClientversion service.
Note
Start the scheduler and modules before you start the dispatcher client to
avoid connection delays and translation failures.

The Dispatcher client cannot start if Security Services is enabled on the host. If
your Teamcenter configuration includes Security Services, you must configure
the Dispatcher client to bypass Security Services:
1. Create a copy of your TC_DATA directory named TC_DATA_nonsso.
2. In the TC_DATA_nonsso directory, open the tc_profilevars.bat file

(Windows systems) or the tc_profilevars file (UNIX systems).
Remove or disable the statements that set variables for Security Services,
for example:
Windows systems:
rem set TC_SSO_APP_ID=Tc8SSO
rem set TC_SSO_SERVICE=http://host:port/ssoService8
rem set TC_SSO_LOGIN_URL=http://host:port/ssoLogin8
UNIX systems:
#TC_SSO_APP_ID=Tc8SSO; export TC_SSO_APP_ID
#TC_SSO_SERVICE=http://host:port/ssoService8; export TC_SSO_SERVICE
#TC_SSO_LOGIN_URL=http://host:port/ssoLogin8; export TC_SSO_LOGIN_URL

3. Create a copy of the runDispatcherClient file:

Windows systems:
Copy
Dispatcher-home\Dispatcherclient\bin\runDispatcherClient.bat
to runDispatcherClient_nonsso.bat
UNIX systems:
Copy
Dispatcher-home/Dispatcherclient/bin/runDispatcherClient.sh to
runDispatcherClient_nonsso.sh
4. In the runDispatcherClient_nonsso file, modify the TC_DATA variable

to point to the TC_DATA_nonsso directory.
5. Run the runDispatcherClient_nonsso.bat file (Windows systems) or

runDispatcherClient_nonsso.bat file (UNIX systems) to start or stop the
Dispatcher client. This script runs the Dispatcher client without Security
Services.
Global Services Configuration Guide

The following release notes pertain to the Global Services Configuration Guide.
• Limiting query results in Global Services
The following information will be placed in the Create and manage configuration
files topic.
Global Services provides the maximum.query.objects parameter and property
that can be used to avoid Java virtual machine (JVM) memory error conditions.
You can set the parameter in a Global Services connector configuration file, or
you can set the property in the globalservices.properties file. Global Services
sets the query limit using the following precedence:
1. The connector parameter if it is defined for the connector.
2. The property if it is defined in the globalservices.properties file.
3. The value 5000 if neither a parameter nor property is defined.
This allows you to set a Global Services site-wide limit that can be overridden
for specific connectors. You can use the max_objects_limit parameter in the
Global Services business object definition (BOD) to set the maximum value that a
user can select from the Max Objects list on the BOD query form. The existing
max_objectsparameter sets the default value in the list.

Installation on UNIX and Linux Servers Guide

The following release notes pertain to the Installation on UNIX and Linux Servers
Guide.
General documentation notes
The following notes contain general corrections and additions to the Installation on
UNIX and Linux Servers Guide.
• Using downloaded Lifecycle Visualization software distribution images
In J2EE Web tier installation in the Rich client distribution instance
requirements topic, the following note will be added to the bulleted paragraph
about the Lifecycle Visualization software distribution image:
Note
If you include Lifecycle Visualization in your rich client distribution
instance, and you use downloaded software images instead of a DVD:
1. Download the common.tar.gz file and the appropriate
platform-specific .gz archives (for Sun Solaris, IBM AIX, or Linux).
2. Extract all these files into a single directory.
3. When building your rich client distribution instance, enter the location
of this directory in the TcVisInstallImageUnixLocation context
parameter in the Web Application Manager.
• Installing Teamcenter patches

The following corrections apply to Installing Teamcenter patches.
– In Distribution of Teamcenter updates, the correct name of the Lifecycle

Visualization (referenced as Teamcenter Visualization) patch file is
product-level_number_PV_all.zip.
– Patching Teamcenter Environment Manager refers to the patch file as

install.zip. The actual file name is patch-id_install.zip.
– In Patching Teamcenter Environment Manager, in step 1, substep d, the

note should read as follows:
Note
◊ Add the path to your TC_ROOT/install/install directory to your
PATH environment variable and enter the unzip command again.
◊ Enter the unzip command with the full path to your

TC_ROOT/install/install directory, for example:
TC_ROOT/install/install/unzip –o install.zip

– In Install patches on the corporate server, step 1, the correct path to TEM is
TC_ROOT/install/tem.sh.
– In Install patches on the corporate server, step 3, the note incorrectly states
TEM stops Teamcenter services during the update process. On UNIX and
Linux systems, you must manually stop all Teamcenter services before
installing patches.
– In Install patches on the corporate server, step 5, substep b should read as

follows:
Extract the platform/tc/data directory from the patch-id.zip file and copy
the contents to your TC_DATA directories.
– At the end of Install patches on the corporate server, the two steps that
describe how to update your database’s information should be omitted.
These steps are no longer needed.
– In Patching the rich client, the first sentence should read as follows:
There are multiple methods for patching the rich client.
– In Patching the rich client, the note referring to the portal_patch.jar file
should be deleted. The portal_patch.jar file is no longer included in patches.
– In Patch Lifecycle Visualization, step 1, the list of platform-specific patch

files should be replaced with one file: patch-id_PV_all.xip. This file contains
Lifecycle Visualization patches for all platforms.
– In Patch Lifecycle Visualization, step 3, which refers to an install.zip file,

should be deleted.
– In Patch Lifecycle Visualization, step 4 should be replaced with the following:
Follow the steps in Patch the rich client using the Over-the-Web Installer
with the following exceptions:
1. In step 5, select the instance that contains the Teamcenter

Visualization 8 (Embedded Viewer) for Rich Client 4–Tier
(installation and Configuration) solution.
2. In step 8, select the Teamcenter Visualization 8 (Embedded Viewer)

for Rich Client 4–Tier (installation and Configuration )Patch
solution.
3. Repeat steps 5 through 9, selecting the instances that contain the

Teamcenter Visualization 8 (Embedded Viewer) for Rich Client
4–Tier (installation and Configuration) solution and selecting the
4–Tier (installation and Configuration )Patch solution.
– The Patch the distribution server topic should be omitted.

– In Patch the Web tier, step 11 should read as follows:

In the Reinstall Solutions dialog box, click OK.
– The Review the README file topic should be replaced with the following:
The patch-id_pub.zip file includes a release_info directory that contains
the patch set README file. Review this README file for information
about the patch and possible additional steps required to complete the patch
installation.
Environment settings for non-English locales (UNIX and Linux systems)

Note
This topic replaces the Environment settings for non-English locales topic in
the Installation on UNIX and Linux Servers Guide.
Teamcenter 8 is supported in the following locales on all server platforms:
• English • Hebrew
• French • Russian
• German • Japanese
• Italian • Korean
• Spanish • Simplified Chinese
• Czech • Traditional Chinese
To ensure correct display and processing of Teamcenter data, set the required
values in your system environment and your Teamcenter configuration. Use the
appropriate values for your locale and platform.
Note
To display multibyte character strings correctly on platforms that support
multiple encodings of a given language, the specified system locale for a shell
must match the windowing system.
Environment settings for non-UTF-8 environments
For non-English locales on UNIX systems, specify the system locale by setting the
LANG and LC_ALL environment variables using the Common Desktop Environment
(CDE) at login to the system. These two variables must be identical to function
properly. Set these and other values as described in the following table.

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

Locale Value IBM AIX HP HP-UX Sun Solaris Linux
English Character set ISO88591 ISO88591 ISO88591 ISO8859-1
Database character set WE8ISO8859P1 WE8ISO8859P1 WE8ISO8859P1 WE8ISO8859P1
LANG and LC_ALL1 en_US.ISO88591 en_US.iso88591 en_US.ISO88591 en_US.ISO8859-1
TC_XML_ENCODING2 ISO-8859-1 ISO-8859-1 ISO-8859-1 ISO-8859-1
TC_CHARACTER_ ISO8859_1 ISO8859_1 ISO8859_1 ISO8859_1
ENCODING_SET2 3 4
TC_language_default5 en en en en
French Character set ISO88591 ISO88591 ISO88591 ISO8859-1

LANG and LC_ALL1 fr_FR.ISO88591 fr_FR.iso88591 fr_FR.ISO88591 fr_FR.ISO8859-1
ENCODING_SET2 3 4
TC_language_default5 fr fr fr fr
German Character set ISO88591 ISO88591 ISO88591 ISO8859-1
LANG and LC_ALL1 de_DE.ISO88591 de_DE.iso88591 de_DE.ISO88591 de_DE.ISO8859-1
ENCODING_SET2 3 4
TC_language_default5 de de de de
Italian Character set ISO88591 ISO88591 ISO88591 ISO8859-1
LANG and LC_ALL1 it_IT.ISO88591 it_IT.iso88591 it_IT.ISO88591 it_IT.ISO8859-1
ENCODING_SET2 3 4
TC_language_default5 it it it it
Spanish Character set ISO88591 ISO88591 ISO88591 ISO8859-1
LANG and LC_ALL1 es_ES.ISO88591 es_ES.iso88591 es_ES.ISO88591 es_ES.ISO8859-1
ENCODING_SET2 3 4
TC_language_default5 es es es es
Czech Character set ISO88592 ISO88592 ISO88592 ISO8859-2
Notes:
1. Set in the system environment variables.

2. Set in the TC_DATA/tc_profilevars file.
3. Set in the TC_ROOT/iiopservers/Start_TcServer1 file.
4. Set in the TC_ROOT/pool_manager/mgrstartMYDB file.
5. Set the TC_language_default site preference.


LANG and LC_ALL1 Cs_CZ.ISO88592 Cs_CZ.iso88592 Cs_CZ.ISO88592 Cs_CZ.ISO8859-2
ENCODING_SET2 3 4
TC_language_default5 cs cs cs cs
Russian Character set ISO88595 ISO88595 ISO88595 ISO8859-5
Database character set CL8ISO8859P5 CL8ISO8859P5 CL8ISO8859P5 CL8ISO8859P5
LANG and LC_ALL1 ru_RU.ISO8859-5 ru_RU.iso88595 ru_RU.ISO88595 ru_RU.ISO8859-5
ENCODING_SET2 3 4
TC_language_default5 ru ru ru ru
Hebrew Character set ISO88598 ISO88598 ISO88598 ISO88598

Database character set IW8ISO8859P8 IW8ISO8859P8 IW8ISO8859P8 IW8ISO8859P8
LANG and LC_ALL1 iw_IL.ISO88598 iw_IL.iso88598 he_IL.ISO8859-8 he_IL.ISO8859-8
ENCODING_SET2 3 4
Japanese Character set EUC EUC EUC EUC
(EUC)
Database character set JA16EUC JA16EUC JA16EUC JA16EUC
LANG and LC_ALL1 Ja_JP ja_JP.eucJP ja_JP.eucJP ja_JP.eucJP
TC_XML_ENCODING2 Shift_JIS Shift_JIS Shift_JIS Shift_JIS
TC_CHARACTER_ EUC_JP EUC_JP EUC_JP EUC_JP
ENCODING_SET2 3 4
TC_language_default5 jp jp jp jp
Japanese Character set Shift-JIS Shift-JIS Shift-JIS Shift-JIS
(Shift-JIS)
Database character set JA16SJIS JA16SJIS JA16SJIS JA16SJIS
LANG and LC_ALL1 Ja_JP ja_JP.SJIS ja_JP.PCK ja_JP.SJIS
TC_XML_ENCODING2 Shift_JIS Shift_JIS Shift_JIS Shift_JIS
TC_CHARACTER_ SJIS SJIS SJIS SJIS
ENCODING_SET2 3 4
Korean Character set KSC5601 KSC5601 KSC5601 KSC5601
Database character set KO16KSC5601 KO16KSC5601 KO16KSC5601 KO16KSC5601
Notes:



LANG and LC_ALL1 ko_KR.eucKR ko_KR.eucKR ko_KR.EUC ko_KR.eucKR
TC_XML_ENCODING2 EUC-KR EUC-KR EUC-KR EUC-KR
TC_CHARACTER_ EUC_KR EUC_KR EUC_KR EUC_KR
ENCODING_SET2 3 4
TC_language_default5 kr kr kr kr
Simplified Character set CGB2312-80 CGB2312-80 CGB2312-80 CGB2312-80
Chinese
Database character set ZHS16CGB231280ZHS16CGB231280ZHS16CGB231280ZHS16CGB231280
LANG and LC_ALL1 zh_CN.hp15CN zh.GBK or zh_CN.GBK zh_CN.gb2312
TC_XML_ENCODING2 GB2312 GB2312 GB2312 GB2312
TC_CHARACTER_ GBK GBK GBK GBK
ENCODING_SET2 3 4
TC_language_default5 cn cn cn cn
Traditional Character set BIG5 BIG5 BIG5 BIG5

Chinese
Database character set ZHT16BIG5 ZHT16BIG5 ZHT16BIG5 ZHT16BIG5
LANG and LC_ALL1 zh_TW.big5 zh_TW.big5 zh_TW.BIG5 zh_TW.big5
TC_XML_ENCODING2 Big5 Big5 Big5 Big5
TC_CHARACTER_ Big5 Big5 Big5 Big5
ENCODING_SET2 3 4
TC_language_default5 tw tw tw tw
Notes:

Note

Environment settings for UTF-8 environments
Support for the Unicode UTF-8 character set in Teamcenter 8 is restricted to UNIX
or Linux platforms that are configured to run the Unicode UTF-8 operating system.
A new database installation is required with Unicode UTF-8 character set support.
You must configure your Teamcenter installation to run the UTF-8 character set,
observing the following considerations:
• If you use UNIX, your UNIX platforms administrator must use CDE (Common
Desktop Environment) to configure the system to run Unicode UTF-8 character
set operating system. This is required so that all software running in this
operating system environment understands the default character set is UTF-8.
• 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 that is running on a UNIX or a Linux platform that is running
the Unicode UTF-8 operating system.
The thin client may be run in a Web browser that is running on any Siemens
PLM Software supported platform and language character set encoding
operating system.
• You must configure the Teamcenter rich client to connect to a four-tier UTF-8
server installation that is running on a UNIX or a Linux platform that is
running the Unicode UTF-8 operating system. The rich client may be installed
over-the-Web to a Windows platform that is running any Siemens PLM Software
supported language character set encoding operating system. The rich client
may be installed over-the-Web to a UNIX or Linux platform that must be
running the Unicode UTF-8 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
If your Teamcenter database server uses the UTF-8 character set, your
Teamcenter corporate server cannot be installed on a Windows host. You may,
however, run the thin client or the four-tier rich client on Windows platforms.
The following illustration shows a sample Teamcenter 8 configuration for restricted

Unicode UTF-8 character set support with clients displaying multiple locales.

Unicode homogeneous server platform configuration
Environment settings on UNIX and Linux systems (UTF-8)

Sun
Locale Value IBM AIX HP HP-UX Solaris Linux
English Character set UTF-8 UTF-8 UTF-8 UTF-8
Database character set UTF8 UTF8 UTF8 UTF8
LANG and LC_ALL1 en_US.UTF-8 en_US.UTF-8 en_US.UTF-8 en_US.UTF-8
TC_XML_ENCODING2 UTF-8 UTF-8 UTF-8 UTF-8
TC_CHARACTER_ ENCODING_SET2 3 4 UTF8 UTF8 UTF8 UTF8
French Character set UTF-8 UTF-8 UTF-8 UTF-8

LANG and LC_ALL1 fr_FR.UTF-8 fr_FR.UTF-8 fr_FR.UTF-8 fr_FR.UTF-8
TC_CHARACTER_ENCODING_SET2 3 4 UTF8 UTF8 UTF8 UTF8
TC_language_default5 fr fr fr fr
German Character set UTF-8 UTF-8 UTF-8 UTF-8
LANG and LC_ALL1 de_DE.UTF-8 de_DE.UTF-8 de_DE.UTF-8 de_DE.UTF-8
Notes:



Sun
TC_language_default5 de de de de
Italian Character set UTF-8 UTF-8 UTF-8 UTF-8
LANG and LC_ALL1 It_IT.UTF-8 It_IT.UTF-8 It_IT.UTF-8 It_IT.UTF-8
TC_language_default5 it it it it
Spanish Character set UTF-8 UTF-8 UTF-8 UTF-8
LANG and LC_ALL1 es_ES.UTF-8 es_ES.UTF-8 es_ES.UTF-8 es_ES.UTF-8
TC_language_default5 es es es es
Czech Character set UTF-8 UTF-8 UTF-8 UTF-8

LANG and LC_ALL1 cs_CZ.UTF-8 cs_CZ.UTF-8 cs_CZ.UTF-8 cs_CZ.UTF-8
TC_language_default5 cs cs cs cs
Russian Character set UTF-8 UTF-8 UTF-8 UTF-8
LANG and LC_ALL1 ru_RU.UTF-8 ru_RU.UTF-8 ru_RU.UTF-8 ru_RU.UTF-8
TC_language_default5 ru ru ru ru
Hebrew Character set UTF-8 UTF-8 UTF-8 UTF-8

LANG and LC_ALL1 iw_IL.UTF-8 iw_IL.UTF-8 he_IL.UTF-8 he_IL.UTF-8
Japanese Character set UTF-8 UTF-8 UTF-8 UTF-8
Notes:



Sun
LANG and LC_ALL1 ja_JP.UTF-8 ja_JP.UTF-8 ja_JP.UTF-8 ja_JP.UTF-8
Korean Character set UTF-8 UTF-8 UTF-8 UTF-8
LANG and LC_ALL1 ko_KR.UTF-8 ko_KR.UTF-8 ko_KR.UTF-8 ko_KR.UTF-8
TC_language_default5 kr kr kr kr
Simplified Character set UTF-8 UTF-8 UTF-8 UTF-8
Chinese
LANG and LC_ALL1 zh_CN.UTF-8 zh_CN.UTF-8 zh_CN.UTF-8 zh_CN.UTF-8
TC_language_default5 cn cn cn cn
Traditional Character set UTF-8 UTF-8 UTF-8 UTF-8

Chinese
LANG and LC_ALL1 zh_TW.UTF-8 zh_TW.UTF-8 zh_TW.UTF-8 zh_TW.UTF-8
TC_language_default5 tw tw tw tw
Notes:

Note

Installation on Windows Servers Guide

The following release notes pertain to the Installation on Windows Servers Guide.
General documentation notes

The following notes contain general corrections and additions to the Installation on
Windows Servers Guide.
• Installing Microsoft SQL Server
In Install MS SQL Server, step 4, the following note should be added:
Note
A default instance in a Microsoft SQL Server installation uses the
name MSSQLSERVER. Teamcenter’s persistent object manager (POM)
utilities cannot connect to an instance with this name. If you use a default
instance, make sure you connect to the instance using a port connection
rather than the name.
If you use a named instance, make sure the instance has a unique name
other than MSSQLSERVER.
• Online help search configuration for Microsoft IIS

If you install the Teamcenter online help collection on Microsoft Internet
Information Server (IIS), you must enable certain MIME types on the server to
enable search in the online help collection.
1. On the server, choose Start→Settings→Control Panel.
2. Select Administrative Tools and then select Internet Information Services

(IIS) Manager.
3. Right-click the server name and choose Properties.
4. In the Properties dialog box, click MIME Types.
5. In the MIME Types dialog box, click New.
6. In the Extension box, type .rds.
7. In the MIME type box, type application/octet-stream and then click OK.
8. Repeat steps 5 through 7 for the following MIME types.
Extension MIME type

.fit application/octet-stream
.prm application/octet-stream
.que application/octet-stream
9. In the MIME Types dialog box, click OK.
10. In the Properties box, click OK.

11. In the IIS Manager dialog box, right-click the server name, choose All Tasks,
and then choose Restart IIS.
12. Ensure that Restart Internet Services on computer-name is selected, and

then click OK.
Note
If you want to serve all files, regardless of the file name extension, you can
type an asterisk (*) in step 6. You should only use the wildcard mapping
to the IIS MIME map as a temporary solution during troubleshooting. If
you determine that a missing MIME type is the cause of the issue, remove
the wildcard mapping and add the specific mapping for the MIME type
that you need to serve.
• Installing Teamcenter patches

The following corrections apply to Installing Teamcenter patches.
– In Distribution of Teamcenter updates, the correct name of the Lifecycle

Visualization (referenced as Teamcenter Visualization) patch file is
product-level_number_PV_all.zip.
– Patching Teamcenter Environment Manager refers to the patch file as

install.zip. The actual file name is patch-id_install.zip. Also, you should
extract this file to your TC_ROOT\install directory, not TC_ROOT.
– In Patching Teamcenter Environment Manager, in step 1, substep d, the

note should read as follows:
Note
◊ Add the path to your TC_ROOT\install\install directory to your
PATH environment variable and enter the unzip command again.
◊ Enter the unzip command with the full path to your

TC_ROOT\install\install directory, for example:
TC_ROOT\install\install\unzip –o install.zip
– In Install patches on the corporate server, step 5, substep b should read as

follows:
Extract the platform\tc\data directory from the patch-id.zip file and copy
the contents to your TC_DATA directories.
– At the end of Install patches on the corporate server, the two steps that
describe how to update your database’s information should be omitted.
These steps are no longer needed.
– In Patching the rich client, the first sentence should read as follows:
There are multiple methods for patching the rich client.
– In Patching the rich client, the note referring to the portal_patch.jar file
should be deleted. The portal_patch.jar file is no longer included in patches.

– In Patch Lifecycle Visualization, step 1, the list of platform-specific patch

files should be replaced with one file: patch-id_PV_all.xip. This file contains
Lifecycle Visualization patches for all platforms.
– In Patch Lifecycle Visualization, step 3, which refers to an install.zip file,

should be deleted.
– In Patch Lifecycle Visualization, step 4 should be replaced with the following:

Follow the steps in Patch the rich client using the Over-the-Web Installer
with the following exceptions:
1. In step 5, select the instance that contains the Teamcenter
Visualization 8 (Embedded Viewer) for Rich Client 4–Tier
(installation and Configuration) solution.
2. In step 8, select the Teamcenter Visualization 8 (Embedded Viewer)

for Rich Client 4–Tier (installation and Configuration )Patch
solution.
3. Repeat steps 5 through 9, selecting the instances that contain the

4–Tier (installation and Configuration) solution and selecting the
4–Tier (installation and Configuration )Patch solution.
– The Patch the distribution server topic should be omitted.
– In Patch the Web tier, step 11 should read as follows:

In the Reinstall Solutions dialog box, click OK.
– The Review the README file topic should be replaced with the following:
The patch-id_pub.zip file includes a release_info directory that contains
the patch set README file. Review this README file for information
about the patch and possible additional steps required to complete the patch
installation.
Environment settings for non-English locales (Windows systems)

Note
This topic replaces the Environment settings for non-English locales topic in
the Installation on Windows Servers Guide.
Teamcenter 8 is supported in the following locales on all server platforms:
• English • Hebrew
• French • Russian
• German • Japanese
• Italian • Korean
• Spanish • Simplified Chinese
• Czech • Traditional Chinese

To ensure correct display and processing of Teamcenter data, set the required
values in your system environment and your Teamcenter configuration. Use the
appropriate values for your locale and platform.
For non-English locales on Windows systems, specify the system locale by setting
the LANG and LC_ALL environment variables using the Windows Control Panel.
These two variables must be identical to function properly. Set these and other
values as described in the following table.
Environment settings on Windows systems

Locale Value Windows 2000 Windows 2003 Windows XP
English Character set CP1252 CP1252 CP1252
Database character set WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252
TC_XML_ENCODING1 ISO-8859-1 ISO-8859-1 ISO-8859-1
TC_CHARACTER_ENCODING_SET1 2 3 ISO8859_1 ISO8859_1 ISO8859_1
TC_language_default4 en en en
French Character set CP1252 CP1252 CP1252

TC_language_default4 fr fr fr
German Character set CP1252 CP1252 CP1252
TC_language_default4 de de de
Italian Character set CP1252 CP1252 CP1252
TC_language_default4 it it it
Spanish Character set CP1252 CP1252 CP1252
TC_language_default4 es es es
Czech Character set CP1250 CP1250 CP1250

Notes:


Environment settings on Windows systems

Locale Value Windows 2000 Windows 2003 Windows XP
TC_language_default4 cs cs cs
Russian Character set CP1251 CP1251 CP1251
Database character set CL8MSWIN1251 CL8MSWIN1251 CL8MSWIN1251
TC_language_default4 ru ru ru
Hebrew Character set CP1255 CP1255 CP1255

Database character set IW8MSWIN1255 IW8MSWIN1255 IW8MSWIN1255
TC_language_default4 en en en
Japanese Character set MS932 MS932 MS932
Database character set JA16SJIS JA16SJIS JA16SJIS
TC_XML_ENCODING1 Shift_JIS Shift_JIS Shift_JIS
TC_CHARACTER_ENCODING_SET1 2 3 SJIS SJIS SJIS
TC_language_default4 jp jp jp
Korean Character set MS949 MS949 MS949
Database character set KO16KSC5601 KO16KSC5601 KO16KSC5601
TC_XML_ENCODING1 EUC-KR EUC-KR EUC-KR
TC_CHARACTER_ENCODING_SET1 2 3 EUC_KR EUC_KR EUC_KR
TC_language_default4 kr kr kr
Simplified Character set MS936 MS936 MS936
Chinese
Database character set ZHS16CGB231280 ZHS16CGB231280 ZHS16CGB231280
TC_XML_ENCODING1 GB2312 GB2312 GB2312
TC_CHARACTER_ENCODING_SET1 2 3 GBK GBK GBK
TC_language_default4 cn cn cn
Traditional Character set MS950 MS950 MS950

Chinese
Database character set ZHT16BIG5 ZHT16BIG5 ZHT16BIG5
TC_XML_ENCODING1 Big5 Big5 Big5
TC_CHARACTER_ENCODING_SET1 2 3 Big5 Big5 Big5
TC_language_default4 tw tw tw
Notes:


Multi-Site Collaboration Guide

The following release notes pertain to the Multi-Site Collaboration Guide.
• Configure proxy servers
The Configure proxy servers topic is missing the following notes.
Note
Because a proxy server does not use a database, it uses the
tc_preferences_overlay.xml file to store Teamcenter site preferences.
You must manually edit this file to set the preference values.
Note
The TC_DATA directory is not explicitly defined in Teamcenter
Environment Manager (TEM) when you install a proxy server. TEM
creates this directory under the TC_ROOT directory and names
the directory using the value you specify in the ID box in the New
Configuration panel.
• Bypass portmapper service

The Bypass portmapper service topic is missing the following note:
Note
Before configuring an IDSM or ODS for a site using the default
portmapper bypass setup, use the rpcinfo system utility to verify that
there is no existing IDSM RPC configuration on the host. Any existing
configuration must be removed to avoid conflicts with the default bypass
portmapper configuration.
• IDSM launching utility

The UNIX configuration procedure in this topic is missing the following step
between steps 4 and 5:
4a. Type the following command to set the IDSM rpc program number using
the –n argument:
nohup ${TC_ROOT}/bin/idsminetd
–p=selected-IDSM-port
–n=IDSM-rpc-program-number
–r=${TC_ROOT}/bin/run_tc_idsm >
/tmp/idsminetd$$.log &
• idsminetd utility
The following information is missing from the idsminetd utility topic.
Use the –n argument to specify an rpc_prog_number value other
than the default value. If you use this argument, you must set the
TC_daemon-name_site-name_prog_number site preference to the value you
specify. For example, if you specify –n=536875586 in the idsminetd command,
set the preference as:
TC_idsm_chicago_prog_number=60003
For more information about the idsminetd utility, see the Utilities Reference.

• Interoperability
The following information will be added to the Version interoperability topic.
Siemens PLM Software supports Multi-Site Collaboration interoperability
between versions. Teamcenter 8 interoperates with Teamcenter 2007,
Teamcenter Engineering 2005, Teamcenter Engineering 2007, and Teamcenter’s
engineering process management 2008 as shown in the following table.
Source (any version of base) Target

Teamcenter 2007 Teamcenter 8
Teamcenter Engineering 2005 SR1 Teamcenter 8
Teamcenter Engineering 2007 Teamcenter 8
Teamcenter’s engineering process Teamcenter 8

management 2008
Certain functional limitations, configuration requirements, and schema

changes are inherent to interoperability because the data model evolves to
provide increased functionality. In most cases, schema differences are handled
transparently by Multi-Site Collaboration. However, some schema changes
require new Teamcenter 8 features to be temporarily disabled until all sites
are upgraded to Teamcenter 8.
There are two categories of changes: general and application-specific.
– General changes apply to all data sharing scenarios
– Application-specific changes apply only to specific classes or applications.

Application-specific changes may not be relevant to your installation.
The following are previously documented restrictions:

– Instances of classes introduced in Teamcenter 8 are not imported into
previous versions; they are ignored.
– New attributes in Teamcenter 8 added to POM classes that existed in

earlier versions are exported from Teamcenter 8 but not imported into
earlier versions. When you import these attributes from earlier versions to
Teamcenter 8, they are assigned null values.
– If a new type is added in Teamcenter 8, such as a relation type or dataset

type and is exported to earlier versions, the type must be defined at the
earlier version site using an appropriate tool. An appropriate tool may be
Business Modeler IDE for a Teamcenter site or the install_types utility in
Engineering Process Management. For relation types, you can define the
ITEM_do_not_export_relation_if_type_excluded site preference at the
Teamcenter 8 site to list the new relation types added in Teamcenter 8 that
should not be exported to the earlier version.

The following general requirements are new in Teamcenter 8:
– If an ODS is shared by Teamcenter 8 and earlier versions, the ODS site must
first be upgraded to Teamcenter 8.
Teamcenter 8 clients cannot publish to an ODS server running an earlier
version.
– Teamcenter 8 sites that must share data with any Teamcenter Engineering
versions (Teamcenter Engineering 2005 SR1, Teamcenter Engineering 2007,
and Teamcenter’s engineering process management 2008), cannot use
longer IDs and names. Verify that the TC_Allow_Longer_ID_Name site
preference is either not defined or set to FALSE. You can set this preference
to TRUE when all participating sites are at Teamcenter 2007 or later.
– Teamcenter 8 sites that must share data with earlier versions must
temporarily disable the sequence feature that was introduced in Teamcenter
2007, by setting the TCCheckoutReserveOnly site preference to
WorkspaceObject. By default, the sequence feature is for all subclasses of
WorkspaceObject. You can disable or modify this preference for specific
classes once all participating sites are at Teamcenter 2007 or later.
– For Teamcenter 8 and sites that predate Teamcenter 8, set the

TC_ALLOW_INCOMPATIBLE_TYPES environment variable to TRUE.
– Several allocation schema changes are made in Teamcenter 2007.

To exchange allocations data, sites that predate Teamcenter
2007 and that interoperate with Teamcenter 8 must run the
upgrade_data_v1001mpx_multisite.default script on the version that
predates Teamcenter 2007.
The upgrade_data_v1001mpx_multisite.default script, which is
available with Teamcenter Engineering 2005 SR1 MP3 and subsequent
versions, makes the following changes to the allocations schema:
◊ Modifies the properties of Allocation attributes source_absOcc_tag,

target_absOcc_tag, and map_rev_tag to allow null values.
◊ Modifies the properties of AllocationMap attributes source_bv_tag

and target_bv_tag to allow null values.
◊ Introduces the ManagedRelation class, a subclass of

WorkspaceObject.
– For Teamcenter Engineering 2005 SR1, Teamcenter Engineering 2007, and

Teamcenter’s engineering process management 8 sites to interoperate with
Teamcenter 8 sites, the administrator must make the following schema
change manually at the Engineering Process Management site:
◊ Make valid the is_frozen attribute from POM_object with NULL:
install -mod_attr infodba infodba dba ItemRevision
variant_expression_block POM_attr_follow_on_export +
install -mod_attr infodba infodba dba ItemRevision

variant_expression_block POM_null_is_valid +

install -mod_attr infodba infodba dba PSOccurrence

variant_condition POM_attr_follow_on_export +
install -set_attr infodba infodba dba PSOccurrence

variant_condition NULLTAG
install -mod_attr infodba infodba dba PSOccurrence

variant_condition POM_null_is_valid –
install -gen_xmit_file -u=infodba -p=infodba -g=dba
– For all Teamcenter 2007 sites that must interoperate with Teamcenter 8
sites, the administrator must make the following schema change manually
at the Teamcenter 2007 site:
◊ Make valid the resource_tag attribute from ScheduleMember with
NULL.
install -mod_attr -u=infodba -p=infodba -g=dba
ScheduleMember resource_tag POM_null_is_valid +
◊ Install gen_xmit_file, which is required after the schema changes.

install -gen_xmit_file -u=infodba -p=infodba -g=dba
Note
The administrator must regenerate the POM schema and transmit
files after making these schema changes. The new transmit files must
be distributed to the other sites.
– Modifying a remote checked-out assembly is not saved

When using Teamcenter Integration for NX assemblies in a multisite
Teamcenter configuration, you cannot save a remote checked-out assembly.
Use Multi-Site Collaboration import/export with transfer ownership instead
of checkout to make these changes.
– Remote checkin behavior

If you attach a local object to a replica using remote checkout, upon remote
checkin, the attached local object can be transferred with ownership, can be
sent as replica, or cannot be sent at all. You can configure this behavior from
the user interface and preference.
From the Remote Checkin dialog box advanced options, you can select a
relation to be transferred with ownership. The option to send a replica is
not yet available in the user interface. Therefore, a relation listed in the
TC_remote_checkin_relation_send_as_replica preference is sent as a
replica.
When you select a particular relation from the user interface, the following
table explains the local attached behavior.

Relation Relation
included in specified in
user interface preference Behavior
Yes Yes Transfer of ownership
Yes No Transfer of ownership
No Yes Sent as replica
No No Not transferred
– Interoperability of certain business objects where subtypes have been added

when it exchanges data with Teamcenter 8 may be problematic when the
following occur:
◊ A Teamcenter 8 site has been upgraded from Teamcenter Engineering
2005 SR1 or Teamcenter 2007.
◊ The upgraded Teamcenter 8 still exchanges data with Teamcenter

Engineering 2005 SR1 or Teamcenter 2007 sites.
◊ There are new subtypes created in the earlier Teamcenter Engineering

2005 SR1 and Teamcenter 2007 after the other sites in the federation are
upgraded to Teamcenter 8.
The administrator should contact GTAC for assistance.
– Data exchange between Teamcenter 8 sites and Teamcenter 2007 MP1x or

MP2x sites may generate errors in the following situations:
◊ Execute data_share –remote_import from the Teamcenter 8 site for an
object owned at a Teamcenter 2007 MP1x or MP2x site. The following
error message is generated:
Error 100403 - Operation 7 of application ITEM_APP is unsupported.
◊ Check in a replica object from a Teamcenter 8 site for an owning

Teamcenter 2007 MP1x or MP2x site. The following error is generated:
Operation 12 of application RES_APP is unsupported.
◊ Perform a remote import with transfer of ownership from Teamcenter 8

site for an object owned by a Teamcenter 2007 MP1x or MP2x site. The
following error message is generated:
POM INTERNAL ERROR - please report this.
In these situations, the Teamcenter version does not support data exchange
with Teamcenter 8. If possible, the administrator should upgrade the site
to Teamcenter 2007.1 MP3 or a later version. Otherwise, the administrator
should contact GTAC for assistance.

Preferences and Environment Variables Reference

The following release notes pertain to the Preferences and Environment Variables
Reference. A complete description of each preference follows the notes.
• ETS_update_state_delay preference
The ETS_update_state_delay preference was previously undocumented.
• GMS_site_checkin_after_import and GMS_offline_use_TcGS preferences

The GMS_offline_use_TcGS and GMS_site_checkin_after_import
preferences are obsolete. These preferences were for internal Siemens PLM
Software use only and were documented in error.
• PLMXML_put_pie_log_in_syslog preference
The definition for the PLMXML_put_pie_log_in_syslog preference is corrected.
• TC_NX_Foreign_Datasets preference
In the TC_NX_Foreign_Datasets preference, the lines beginning with
DatasetType are reversed and a note is added.
• TC_ugmaster_name_separator preference
The TC_ugmaster_name_separator preference is new.

ETS_update_state_delay
DESCRIPTION
Specifies the delay time in seconds after which a dispatcher request object can be
updated.
When there are multiple dispatcher clients in a translation server installation,
multiple dispatcher clients can update the state of the same dispatcher request
object. The delay time makes sure that only one dispatcher client updates the
dispatcher request object.
Note
If you set a high delay time, the performance of the dispatcher request may
be affected. Siemens PLM Software recommends that the delay time should
not be greater than 5 seconds.
VALID
VALUES
Must be a single positive integer.
DEFAULT
VALUES
0
SCOPE
Site preference.

PLMXML_put_pie_log_in_syslog
DESCRIPTION
Specifies whether the contents of the PLM XML import/export (PIE) log file is copied
to the syslog file or not. This PIE log file is in the same location as the PLM XML
file of the same name and contains the results of any PLM XML import or export
transaction.
VALID
VALUES
TRUE All messages that are printed to the PLM XML import/export
(PIE) log file are also recorded in the syslog file.
FALSE All messages that are printed to the PLM XML import/export
(PIE) log file are not recorded in the syslog file.
DEFAULT
VALUES
FALSE
SCOPE
User preference.

TC_NX_Foreign_Datasets
DESCRIPTION
Specifies the non-NX dataset types available to NX when it lists the datasets in
an item revision.
Note
Specifying dataset types in this preference only makes the dataset types
available to NX, it does not enable the application to read the dataset type.
VALID
VALUES
The value format is four keywords and their values. The keywords are:
DatasetType
NamedReference
NamedReferenceFormat
NamedReferenceTemplate
The format informs NX precisely which named references of the dataset contain the
CAD data. Values are enclosed in quotation marks.
Valid values for the NamedReferenceFormat keyword are BINARY or TEXT. The
named reference template must be the extension for files of that type. For example:
TC_NX_Foreign_Datasets=
DatasetType=“DirectModel” NamedReference=“JTPART”
NamedReferenceFormat=“BINARY” NamedReferenceTemplate=“jt”
DatasetType=“SE PART” NamedReference=“SE-Part”
NamedReferenceFormat=“BINARY” NamedReferenceTemplate=“par”
Note
The values are case sensitive and all of the entry must be included on one line
for each dataset type.
DEFAULT
VALUES
None.
SCOPE
All.

TC_ugmaster_name_separator
DESCRIPTION
Specifies the separator character used when generating dataset IDs from the parent
item ID and revision for UGMASTER datasets created through the NX Integration
or NX. For example, if the value is set to a slash (/), the parent item ID is NX001,
and the parent revision is A; the dataset ID is generated as NX001/A.
This preference is not added automatically during installation.
DEFAULT
VALUES
None.
SCOPE
Site preference.
Rich Client Interface Guide

The following release notes pertain to the Rich Client Interface Guide.
• Using drag-and-drop functionality in the rich client
The following information will be added to the Create a new dataset by
drag-and-drop topic.
On Microsoft Windows systems, you cannot create a new dataset by dragging a
file from the Windows Desktop or from the Desktop folder at the top of Windows
Explorer.
1. Navigate to the Desktop folder within your user profile directory.

Note
The Desktop folder in your user profile directory is typically located
on the C:\ disk:
C:\Documents and Settings\user_name\Desktop
2. Use drag-and-drop from that location.
• Render management configuration information

The Managing datasets topics contain render management installation and
configuration descriptions.
In subsequent releases of the documentation set, much of this information will
be relocated to installation, configuration, and administration guides.

Note
– The PdfGenerator translator (under Document Management
(DocMgt) Translators in TEM) is not supported on UNIX or Linux
systems.
– If you install render management on a 64-bit Sun Solaris host, you

must install the 64-bit version of Teamcenter 8 lifecycle visualization
Convert. The Sun Solaris 64-bit installation image can be downloaded
from the Teamcenter Visualization/JT Translators area of the
Siemens PLM Software FTP site. The image is also available on the
Teamcenter 8 lifecycle visualization DVD provided with Teamcenter
8, SAP number 80-033077-080.
• Online help access from views

Online help is not always installed, and for some views, online help is not
available from the Help®Current Application menu command, the F1 key, or
both.
When online help for a view is not available from the function key or menu
command, follow these steps:
1. Choose Help®Help Library.

– If help is installed, a browser displays the help collection.
– If help is not installed, a browser displays an error message.

See your administrator for assistance.
2. Expand Using Teamcenter Interfaces and choose Rich Client Interface Guide.
3. Choose Getting Started®Views available to rich client application

perspectives®Rich client views.
4. Locate the view for which you are seeking online help and click the link
to display additional information.
• Create an ad hoc Classification search

Step 9 of the Create an ad hoc Classification search procedure incorrectly states
that values for the classification search criteria can be changed in either the
search pane or the Adhoc Classification Query dialog box.
The values for the classification search criteria can only be changed in the Adhoc
Classification Query dialog box.
• Search for data using Classification attributes

To search for data using Classification attributes, create an ad hoc Classification
search.
For more information about creating an ad hoc Classification search, see the
Create an ad hoc Classification search topic in the Rich Client Interface Guide.

• Using the workflow Resume command

In the Actions menu topic, the description of the Resume command is incorrect:
The statement should read as follows:
Resume: Moves a selected task from a Suspended state to the previous state.
Schedule Manager Guide

The following notes contain additions to the Schedule Manager Guide.
• Support for multisite schedules
In the Multisite schedules topic in Manage schedules, the following information
will be added:
– Although support for schedules in a multisite environment is available in

Teamcenter 8, the multisite schedule feature is not interoperable with sites
using earlier versions of Teamcenter.
– You must replicate all resources (users, groups, roles, and disciplines) to all
sites using the dsa_util utility. When you export a user using the dsa_util
utility, the associated groups, roles, disciplines, and calendars (both resource
and its base) are also exported.
– Base calendar names must be unique across all sites. Siemens PLM Software
recommends you use the site name or another unique identifier as part of
the name for base calendars. Base calendars are exported to other sites
when users with resource calendars that refer to these base calendars are
exported through dsa_util utility.
– The user in whose authentication the IDSM and ODS services are run
(specifically for the Windows server) must be in the dba group and must
have an Author license.
– Add the SchDeliverable and SchTaskDeliverable values to the

TCCheckoutReserveOnly site preference.
– Custom values added to LOVs associated with billing code, billing subcode,
cost currency, and time zone properties at any site cannot be automatically
synchronized across all sites. Therefore, these values must be maintained
manually at other sites using Business Modeler IDE to avoid inconsistencies
as follows:
◊ In the Business Modeler IDE, update the custom values for the LOVs
associated with billing code, billing subcode, cost currency, and time
zone properties.
◊ Deploy the changes through Teamcenter Environment Manager (TEM).
– Naming rules must be created and attached to the ItemID property of

Schedule and ScheduleTask classes. The rule for ItemID must contain a
unique identifier such as SiteID to prevent issues with duplicate IDs.

Note
Attach the rule only to the ItemID property and not to the Name
property.
– You must manually synchronize changes to bill rates at any one site across
all sites by interactively updating bill rate data using the Bill Rates dialog
box. Access this dialog box by choosing Schedule→Bill Rates in Schedule
Manager.
– Resource graph
To generate an accurate resource graph for a user at a site, all schedules in
which the user has resource assignments must exist on that site. Siemens
PLM Software recommends exporting all schedules to all sites that need
to view resource graphs for users.
– Program view
To be viewed on a remote site, all schedules referenced by a program view
must be available through import/export at that site.
– Workflow integration
◊ Workflow templates must have unique names and must exist on all sites.
You can replicate workflow templates using import/export of templates.
You must propagate updates to the templates to all the sites using
import/export of templates.
◊ The ProjectTrans service used by Schedule Manager is configured to

retry failed translation requests as follows:
<ProjectTrans provider=”SIEMENS” service=”projecttrans”
isactive=”true” NoOfTries=”5” WaitTimeForReTries=”15”>
Siemens PLM Software recommends that you maintain this setting as

is, especially in a multisite environment. If there are any translation
request failures beyond the five default retries, you must manually
resubmit the translation requests from the Translation Admin Console
or increase the NoOfTries value.
– You must select the relations highlighted in the following figure during
remote import/export and remote checkin of schedules.

– You must make the following access changes at all participating sites:
Note
All ACLs shown in following figures are available in the COTS
(commercial-off-the-shelf) product.
◊ Site administrators must give Export, Import, Transfer out, Transfer

in, and Remote checkout access privileges as shown in these figures.
◊ Also, site administrators must add System Administrator access

control entry (ACE) tables in the Scheduling Objects and Scheduling
Execution Objects ACLs and give that user Read, Write, and Delete
access privileges as shown in the following figures.
◊ You only need to change the Scheduling Objects ACL rule once. It then
applies to the schedule, the scheduling form, and the cost form.
The following figure illustrates the access changes for general import/export.
The following figure illustrates the access changes for Schedule class.
The following figure illustrates the access changes for the Task Execution
form.

The following figure illustrates the access changes for the Task Scheduling
form.
The following figure illustrates the access changes for the Cost form.
Security Services Installation/Customization

The following notes pertain to the Security Services Installation/Customization
guide.

On Windows systems, the Dispatcher client cannot start if Security Services is
enabled on the host. If your Teamcenter configuration includes the Dispatcher
client, you must configure it to bypass Security Services.
Management).
Services Reference
The following release notes pertain to the Services Reference.
• Missing link to the services C++ API documentation

The first page of the Services Reference has no link to the services API
documentation for C++ (cpp/docs). The services C++ API documenation can be
found in the soa_client.zip file on the Teamcenter software distribution image.

Structure Manager Guide

The following release notes pertain to the Structure Manager Guide.
Clarification of Change to Replace command behavior

The following clarification will be made to Replacing a component in the Building
and editing product structure topic.
During prototyping or other changes, you may delete an item or part and
subsequently add another item or part in the product structure.
To convert the separate delete and add operations into a single replacement
operation during BOM comparison:
1. Open two product structure windows side-by-side and configure two different
BOM view revisions (BVRs) showing the individual operations. For example,
configure a BVR showing the deleted part in one window and a second BVR
showing the added part in the second window.
2. Select the deleted and added parts and choose Edit→Change To Replace.
Teamcenter converts the individual delete and add operations into a replacement
operation, replacing the occurrence thread of the added part with the occurrence
thread of the deleted part to keep the same occurrence thread.
Teamcenter Environment Manager Help

The following release notes pertain to the Teamcenter Environment Manager Help.
• MS SQL Server values in database engine selection
In the Database engine selection topic, under Microsoft SQL Server values, the
following note should be added to the description of the Named Instance box:
Note
A default instance in a Microsoft SQL Server installation uses the
name MSSQLSERVER. Teamcenter’s persistent object manager (POM)
utilities cannot connect to an instance with this name. If you use a default
instance, make sure you connect to the instance using a port connection
rather than the name.
If you use a named instance, make sure the instance has a unique name
other than MSSQLSERVER.
Upgrade Guide
The following release notes pertain to the Upgrade Guide.

• Configuration needed for non-English locales

To ensure correct display and processing of Teamcenter data, you must set
required values in your system environment and your Teamcenter configuration.
If your Teamcenter servers run UNIX or Linux and use the Unicode UTF-8
character set, you must configure your operating system and your Teamcenter
configuration to use Unicode UTF-8, observing the following considerations
during Teamcenter upgrade:
– An existing Teamcenter installation must not configure Unicode UTF-8

character set support with an upgrade to Teamcenter 8. An existing
Teamcenter installation is required to complete an upgrade to Teamcenter 8
under its existing database character set encoding.
– 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 Environment settings for non-UTF-8 environments.
– For information about environment settings for UTF-8 UNIX and Linux
systems, see Environment settings for UTF-8 environments.
– For information about environment settings for Windows systems, see

Environment settings for non-English locales (Windows systems).
• Importing Autonomy data into new database

In Import indexed data into new Autonomy database, step 2 should read as
follows:
Open the following URL in a Web browser:

http://host:9001/DREADD?C:\backup\output-0.idx.gz
&DREDbName=FTS_config-ID
Replace host with the Autonomy server host name. Replace config-ID with
the ID of the Teamcenter configuration. 9001 is the server index port used
by the new Autonomy server.
This command uses index port 9001 to import your existing Autonomy
indexed data (output-0.idx.gz) into the new Autonomy IDOL 7.3.4 database
(FTS_config-ID).
Repeat step 1 for each output-n.idx.gz file generated during export.
Note
The name of the Autonomy database is also stored in the
TC_fts_database_name preference.

Utilities Reference
The following release notes pertain to the Utilities Reference. A complete description
of each utility follows the notes.
• dispatcher_create_rqst utility is updated
The name of the ets_create_rqst utility is changed to dispatcher_create_rqst.
The tr argument (trigger name) changed to ty (type string).
A complete description of the dispatcher_create_rqst utility follows.

dispatcher_create_rqst
Provides the capability to create a dispatcher request using command line
arguments.
SYNTAX
The syntax of the dispatcher_create_rqst utility has two forms:
–i=item-ID
–r=revision-ID
[–rn=relation]
–dn=dataset-name
[–dv=dataset-version-number]
–dt=dataset-type-name
–pr= 1 | 2 | 3]
–pn=translator-provider-name
–tn=service-name
–ty=type-string
[–ta1=translation-argument1
[–ta2=translation-argument2
[–ta3=translation-argument3]]]
[–u=user-ID] [–p=password] [–g=group]
–verbose | –debug]
or:
–f=pathname
–dt=dataset-type-name
–pr= 1 | 2 | 3]
–pn=service-provider-name
–tn=service-name
–ty=type-string
[–u=user-ID] [–p=password] [–g=group]
–verbose | –debug]
ARGUMENTS
Note
If relation is not specified, IMAN_specification relation is used.
–u Specifies the user ID of the user who will own the dispatcher
request.
–p Specifies the password corresponding with the user ID.
–g Specifies the group to which the user specified by the –u

argument belongs.
–i Specifies the item.
–r Specifies the item revision.

–rn Specifies the relation name to be used to find the dataset for the
given item revision. This argument is optional. If the relation
is not specified, the value of IMAN_specification is used.
–dn Specifies the dataset name. This argument is optional.
–dv Specifies the dataset version. This argument is optional. If no
version number is specified, the latest version is used.
–dt Specifies the type of the dataset to be translated
–pr Specifies the translation priority. Accepted values are 1, 2, or 3
corresponding to low, medium and high translation scheduler
priority.
–pn Specifies the name of the translator provider, for example,
Siemens PLM Software.
–tn Specifies the name of the translator service, for example,
ideastojt.
–tr Specifies the type name, for example, COMMANDLINE.
–verbose Provides additional information. This argument is optional.
–f Specifies an input file used to create one or more dispatcher
requests. This argument is used in lieu of the item, revision,
relation name, dataset name, and dataset version arguments.
This argument is optional.
The format for the input file is as follows:
item-ID,revision-ID,[relation-name],[dataset-name],
[version-number]
Note
Commas are required.
–ta1 Specifies a translation argument.

ENVIRONMENT
As specified in the Utilities Reference.
FILES
As specified in Utilities Reference.
RESTRICTIONS
None.
EXAMPLES
• To create a dispatcher request for the latest version of the I-deas part dataset
related to the Block/A item revision, enter the following command on a single
line:
dispatcher_create_rqst –u=infodba –p=infodba –g=dba
–i=Block –r=A –dt=IdeasPart –pr=2 –pn=Siemens
–tn=ideastojt —ty=COMMAND_LINE
• To create a dispatcher request for version 2 of the Block/A item revision, enter
the following command on a single line:
–i=Block –r=A –dv=2 –dt=IdeasPart –pr=2 –pn=Siemens

• To create two ideastojt dispatcher requests with a priority of 2, enter the

following command on a single line:
–f=ctrl –dt=IdeasPart,IdeasAssembly –pr=2 –pn-Siemens
The lines in the input file are:

Block,A,,Block,
Asm,A,,Asm,
This creates the following:
– One request for the latest version of the Block dataset, an IdeasPart or
IdeasAssembly type dataset, associated with item revision Block/A by
an IMAN_specification relation.
– One request for the latest version of the Asm dataset, an IdeasPart or
IdeasAssembly type dataset associated with item revision Asm/A by an
IMAN_specification relation.
Note
All parts in the file are subject to the same translation, because the
translator is specified on the command line.
What’s New
The following release note pertains to the What’s New.
• Multilanguage support for clients
The following note replaces the note in the Multilanguage support for clients
topic.
Note
In Teamcenter 2007, localization was desynchronized between all tiers.
Client, middle tier, and server could each use a different locale: the
locale of the machine where the rich client was running, the locale
defined at middle-tier installation, and the server locale specified by
the TC_LOCALIZATION_DIR environment variable located in the
tc_profilevars file. All processes in a pool manager used the same
tc_profilevars file, and therefore, the same language. Therefore, in a
globally distributed enterprise with one pool manager running on a server
machine located in country A with locale L_A, all Teamcenter server
processes spawned from the pool manager ran with locale L_A. Therefore,
all client connections were served with only locale L_A.

Workflow Designer Guide

The following release notes pertain to the Workflow Designer Guide.
• Use TCM Release Status template for creating a quick-release process
template
In the Create a quick-release process template topic, step 4 should read as follows:
1. From the Based On Root Template list, select the TCM Release Status
template to use as the base for the quick-release template. The TCM Release
Status template consists of an Add Status task.
Basing your new quick release template on the TCM Release Status template
automatically populates the Start task with the required create-status
and add-status handlers.
When you choose a template in the Based on Process Template box, task
information is displayed for the selected process template in the Task
Hierarchy View, the Name and Description boxes, and the Task Flow View.
This information can be viewed within the New Process dialog box; it cannot
be modified.
You can click the Task Attributes, Task Handlers, and Task Signoff buttons
to view the selected process template’s task attribute, task handler, and task
signoff information.
• –attachment argument added to the notify action handler

The –attachment argument is added to the notify action handler.
A complete description of the notify action handler follows.

notify
DESCRIPTION
Informs users of a task’s status through e-mail.
If the –attachment argument is defined, recipients also receive Teamcenter mail.
The notify handler can send notifications to users through Teamcenter mail only if
the Mail_internal_mail_activated preference is set to True.
Note
The –report argument on the CR-notify handler differentiates the
CR-notify handler from the notify handler. In notification e-mail, the
–report argument appends a report describing the signoff data associated
with the perform-signoff task. Therefore, you should use the CR-notify
handler on the perform-signoff task, whereas the notify handler is more
generic and can be used on any type of task.
SYNTAX
notify
–recipient=
{OS:user-name | user:user | person:person| addresslist:value
| resourcepool:group::role
| allmembers:group::role
| $USER
| $REVIEWERS | $PROPOSED_REVIEWERS
| $RESPONSIBLE_PARTY
| $PROPOSED_RESPONSIBLE_PARTY
| $UNDECIDED
| $PROJECT_ADMINISTRATOR
| $PROJECT_TEAM_ADMINISTRATOR
| $PROJECT_AUTHOR | $PROJECT_MEMBER
| $TARGETOWNER | $PROCESSOWNER
| $RESOURCE_POOL_ALL | $RESOURCE_POOL_NONE
| $RESOURCE_POOL_SUBSCRIBED
[–subject=string]
[–comments=string]
[–url = [rich | dhtml]
[–attachment=$TARGET |$PROCESS | $REFERENCE]
ARGUMENTS
–recipient
Specifies the task reviewers receiving notification. Accepts one of the following
values:
• OS
Sends a notification to the OS user name specified.
user-name is a single valid user name.
• user
Sends notification to the user specified.
user is a single valid Teamcenter user ID.

• person
Sends a notification to user whose name is specified.
person is a single valid Teamcenter person.
• addresslist
Adds all members of the address list specified to the signoff member list. Sends
notification to all members of a group/role combination.
value is a valid Teamcenter address list.
• resourcepool
Sends notification to members of a group/role combination. Notification is
sent to all members, subscribed members, or none based on the preference
EPM_resource_pool_recipients.
The preference value can be overridden with:
$RESOURCE_POOL_ALL
$RESOURCE_POOL_SUBSCRIBED
$RESOURCE_POOL_NONE
You can define role in groups in the form of group, group::role or ::role.
value is a valid Teamcenter resource pool and these keywords:
$GROUP Current user’s current group.

$ROLE Current user’s current role.
$TARGETGROUP[type] Owning group of the first target object of the

specified type. The type value is optional. If
not specified, the first target is used.
$PROCESSGROUP Owning group of the process.
• allmembers
Sends notification to all members of a group/role combination.
value is all members of a Teamcenter group and role.
You can define role in groups in the form of group, group::role or ::role.
Accepts valid Teamcenter resource pool names and these keywords: $GROUP,
$ROLE, $TARGETGROUP and $PROCESSGROUP.
• $USER
Sends e-mail to the current user.
• $REVIEWERS
Builds a list of all users who are reviewers in the same task level as the current
reviewer and sends e-mail to all of them.
• $PROPOSED_REVIEWERS

Sends e-mail to all members assigned as the proposed reviewers of the first
target object in the workflow process.
• $RESPONSIBLE_PARTY
Sends e-mail to the designated responsible party for the task.
• $PROPOSED_RESPONSIBLE_PARTY
Sends e-mail to the member assigned as the proposed responsible party of the
first target object in the workflow process.
• $PROCESSOWNER
Sends e-mail to the process owner.
• $TARGETOWNER [type]
Sends e-mail to the target owner of the first target of the specified type. The type
value is optional. If it is not specified, the first target is used.
• $UNDECIDED
Sends e-mail to the users who have not set the decision for the task.
• $PROJECT_ADMINISTRATOR
$PROJECT_TEAM_ADMINISTRATOR
$PROJECT_AUTHOR
$PROJECT_MEMBER
These values dynamically evaluate project team members belonging to the role
specified in the argument value and send a notification to them. The project
team is determined by the project team associated with the first target object.
• $RESOURCE_POOL_ALL
Identifies all members of the resource pool.
This argument has an effect only when it is used along with $REVIEWERS,
$UNDECIDED, or $RESPONSIBLE_PARTY.
When this argument is used along with $REVIEWERS, and if a resource pool is
assigned as a reviewer, e-mail is sent to all the members of that resource pool.
When this argument is used along with $UNDECIDED, and if a resource pool is
assigned as a reviewer, and no signoff decision has been made for this resource
pool assignment, all members of that resource pool are notified.
When this argument is used along with $RESPONSIBLE_PARTY, and if a
resource pool is assigned as responsible party, the e-mail is sent to all members
of that resource pool.
• $RESOURCE_POOL_NONE
Identifies all members of the resource pool.

When this argument is used along with $REVIEWERS or $UNDECIDED, and

if a resource pool is assigned as a reviewer, e-mail is not sent to members or
subscribers of the resource pool.
resource pool is assigned as responsible party, the e-mail is not sent to members
or subscribers of resource pool.
• $RESOURCE_POOL_SUBSCRIBED
Identifies the users who have subscribed to resource pool.
When this argument is used along with $REVIEWERS, and if a resource pool
is assigned as a reviewer, the e-mail is sent to users who have subscribed to
the resource pool.
When this argument is used along with $UNDECIDED, and if a resource pool is
assigned as a reviewer and no signoff decision has been made for this resource
pool assignment, e-mail is sent to users who have subscribed to the resource pool.
resource pool is assigned as a responsible party, the e-mail is sent to users who
have subscribed to the resource pool.
Note
If the $RESOURCE_POOL_XXXXX argument is not defined and
the $REVIEWERS, $UNDECIDED, or $RESPONSIBLE_PARTY
arguments are used for a case where assignments are made to resource
pools, the e-mail is sent using the EPM_resource_pool_recipients
preference.
EPM_resource_pool_recipients can take one of the following values:
– all
Sends mail to all members of resource pool.
– none
Does not send a mail to members or subscribers of resource pool.
– subscribed
Sends mail to Teamcenter users who have subscribed to resource pool.
If the $RESOURCE_POOL_XXXXX argument is defined, the argument

takes precedence over preference value.
If this argument is not defined and the EPM_resource_pool_recipients
preference is not set, subscribed is considered the default value.
–subject
Displays the task name enclosed in brackets, followed by the string identified by this
argument, on the OS mail’s subject line.

–comments
Embeds user-defined comments in the body of the e-mail.
–url
Inserts a DHTML link to the process into the notification e-mail, based on the value
for –url. If no value is specified for –url, both links are added into the notification
e-mail.
If the –url argument is not defined, the notification e-mail contains links depending
on the values set in the EPM_notify_url_format preference.
EPM_notify_url_format can take the following values:
• rich
Inserts a rich client link to the process into the notification e-mail.
• dhtml
Inserts a thin client (DHTML) link to the process into the notification e-mail.
If the –url argument is not defined and the EPM_notify_url_format preference is

not set in preference file, rich client and thin client links are added to the notification
e-mail as a default. The URL is generated only when the WEB_default_site_server
preference is set to the thin client server node name.
Note
Rich client URL functionality must be enabled for links to rich client workflow
processes to launch the rich client.
–attachment
Adds an attachment to a Teamcenter mail. This argument does not have any affect
on operating system e-mail. The attachment value can be any of the following:
• $TARGET
The workflow target attachments are included in the mail.
• $PROCESS
The workflow process is included in the mail.
• $REFERENCE
The task attachments reference list is included in the mail.
PLACEMENT
When $REVIEWERS or $UNDECIDED is used as the keyword, place on the Start
or Complete action of the perform-signoff task.
RESTRICTIONS
None.
EXAMPLES
• This example sends an e-mail with the subject Lower Right Subassembly
Review to all users on the design and qualityControl address lists. The
comment described in the example appears in the body of the e-mail text.
In addition to the e-mail, the recipients also receive a Teamcenter mail that
contains both the workflow target attachments and the current process.

Argument Values
–subject Lower Right Subassembly Review
–recipient DistributionList:design,
DistributionList:qualityControl
–comments Please review new subassembly and report
any concerns directly to the Product Manager
–attachment $TARGET, $PROCESS
• This example sends an e-mail to the designated responsible party for the task. If
the responsible party is a resource pool, no e-mail is sent.
Argument Values
–recipient $RESPONSIBLE_PARTY,
$RESOURCE_POOL_NONE
• This example designates OS users peters and john, user Smith, members of
the group manufacturing, and members of the address list purchasing as
recipients of an e-mail with the subject Manufacturing Release Procedure
Completed.
Argument Values
–subject Manufacturing Release Procedure Completed
–recipient OS:peters, OS:john, User:smith,
Group:manufacturing, Role:manager,
DistributionList:purchasing

CONTMGMT-notify
DESCRIPTION
Notifies the translation office through e-mail that a translation order is created.
SYNTAX
CONTMGMT-notify
[–subject=string]
[–comments=string]
[–attachment=$TARGET | $PROCESS | $REFERENCE]
[–url= [ {rich | dhtml | html} ] ]
[log]
ARGUMENTS
–subject
Displays the task name enclosed in brackets, followed by the string identified by this
argument, on the OS mail’s subject line.
–comments
Embeds user-defined comments in the body of the e-mail.
–attachment
Causes an attachment to be included in a separate Teamcenter mail. (This argument
does not have any effect on the OS mail.) The type of attachment is one of the
following:
• $TARGET
Attaches the target to the Teamcenter mail.
• $PROCESS
Attaches the workflow process to the Teamcenter mail.
• $REFERENCE
Attaches the task attachment’s reference list to the Teamcenter mail.
• –url
Inserts a DHTML link to the process into the notification e-mail, based on the
value for –url. If no value is specified for –url, both links are added into the
notification e-mail.
If the –url argument is not defined, the notification e-mail contains links
depending on the values set in the EPM_notify_url_format preference.
EPM_notify_url_format can take the following values:
– rich
Inserts a rich client link to the process into the notification e-mail.
– dhtml
Inserts a thin client (DHTML) link to the process into the notification e-mail.
If the –url argument is not defined and the EPM_notify_url_format preference

is not set in preference file, rich client and thin client links are added to

the notification e-mail as a default. The URL is generated only when the
WEB_default_site_server preference is set to the thin client server node name.
Note
Rich client URL functionality must be enabled for links to rich client
workflow processes to launch the rich client.
log
Records the notify activity in the workflow audit file.
PLACEMENT
Place on the Start action of any task.
RESTRICTIONS
None.
Note
To specify multiple attachments, you must call the –attachment argument
multiple times.
EXAMPLES
• This example sends an e-mail with the subject Translation Order Submitted
to the translation office. The comment described in the example appears in the
body of the e-mail text. In addition to the e-mail, the translation office also
receives a Teamcenter mail that contains both the workflow target attachments
and the current process.
Argument Values
–subject Translation Order Submitted
–comments Please translate the specified topic.
–attachment $TARGET, $PROCESS
log
Adding a Validate task to a workflow process
The Validate task allows you to factor in the possibility of errors occurring during
your workflow process and to define how the process continues when errors occur
and when they do not.
You do this by configuring both a success path and a failure path for the Validate
task. The success path is followed if no error occurs. The failure path is followed
when errors occur.
When errors occur, you determine if the failure path is followed when:
• Any error occurs
• Or only when an error you specify on a list of error codes occurs

In the context of the Validate task, error means any error thrown by a workflow
handler. Configure the task to follow a failure path by pairing a workflow handler
and an error code. Place a handler to be validated on the Validate task and then
add the respective error code to the task path’s error list (or set the task path to
fail on any error.)
Example
At Design, Inc., employees check out documents that are targets of workflows
and sometimes neglect to check them back in. Teamcenter does not allow
users to initiate a process on a target that is checked out. However, at Design,
Inc., no business rules prevent users from checking out targets after a process
is initiated. When the workflow reaches the review stage, and the required
targets are checked out, the workflow cannot complete.
In this example, this situation is anticipated and the Validate task is used to
provide a correction. The task is placed before the review stage of the workflow
and configured to verify that all targets are checked in. If so, a success path is
followed. If not, the workflow follows a failure path that includes an additional
Do task assigned to a manager. The Do task instructs the manager to get the
targets checked in, and then complete the Do task. After the error condition
is corrected, the Do task’s success path traverses back into the main workflow.
The Validate task is configured to validate whether targets are checked in by
placing the CR-assert-targets-checked-in rule handler on the Start action,
and specifying the target-checked-out error in the error list.
This is one example of what the task can be configured to validate. You can
pair any handler and error code to generate similar behavior. The task accepts
both shipped handlers and custom handlers.
Inserting a Validate task into a workflow process
The following process adds a Validate task into a new process and configures it to
follow a failure path when a target is not checked in. Typically, Teamcenter does
not allow you to initiate a process on a target that is checked out. However, because
situations arise in which targets are checked out after a process is initiated, this
validation can be a useful check.
Note
The following process is an example of how the Validate task is configured
to branch down a failure path when errors occur. You can pair any handler
and error code to generate similar behavior. The tasks accepts both shipped
handlers and custom handlers.
1. Choose File→New Root Template to create a new workflow process.
2. Type a name for the new process in the New Root Template Name box and
click OK.
Alternatively, select an existing process you want to add the task to from the
Process Template list and click OK.
The process template appears in the Process Flow view.

3. Click Edit on the toolbar.

This puts the application in edit mode, allowing you to edit the process template.
4. Click the Validate task button on the toolbar.
5. Double-click the location in the Process Flow view where you want to place
the new Validate task.
A new Validate task appears, with a default name of New Validate Task #,
where # is incremented until the task name becomes unique within this process
template. For example:
6. Link the existing Do task to the new Validate task.
Note
By default, the Validate task contains no handlers, allowing you to
configure performance as required. In this example, you configure
the task to check whether the target is checked in by adding the
CR-assert-targets-checked-in handler to the Start action.
7. In the Process Flow view, ensure the Validate task is still selected. In the
Template view, click the Handlers button .
The Handlers dialog box appears.
8. In the task action tree in the left-side of the dialog box, select the Start action.
9. In the right-side of the dialog box, select Rule Handler for the handler type.

10. In the Rule Handler list, select CR-assert-targets-checked-in. No handler

arguments are required for this handler in this example.
11. Click Add to add the handler to the Start action of the new Validate task.
12. Close the Handlers dialog box.
13. In the Process Flow view, add a successor task by clicking the Do task button
on the toolbar, then double-clicking in the Process Flow view to place the new
task to the right of the Validate task.
14. Rename the Do task to Success.
15. Add a second succession task by repeating step 14 and renaming the Do task to
Failure.

16. Create a success path between the Validate task and the Success task by
placing the cursor in the body of the Validate task and dragging it to the body
of Success.
A line appears between the two tasks. If you leave this path unconfigured, it
is a success path.
17. Create a failure path between the Validate task and the Failure task by placing
the cursor in the body of the Validate task and dragging it to the body of Failure.
A line appears between the two tasks.
18. Right-click the line you have just drawn. A list provides you with two options.
Selecting either option creates a failure path.
• Select Set To Error Path to configure the task to follow the failure path when
any error occurs. (If you select this option, skip to step 23.)
• Select Set Error Codes to specify which error codes you want the Validate
task to check. If you select this option, the Set Error Codes dialog box
displays.
19. In the Set Error Codes dialog box, type an EPM error code you want to
cause the process to follow the failure path. For example, type 32009
(RES_OBJECT_IS_RESERVED) to ensure the failure path is followed
whenever a target is not checked in.

Note
For more information about finding EPM error codes, see Finding error
codes.
20. Click Add to add this error to the Results List.
21. Continue adding errors to the Results List until you have specified all the errors
you want to cause the process to follow the failure path.
22. Click OK to close the Set Error Codes dialog box.

The selected path appears as a broken line, indicating it is now a failure path.

23. Add any additional required tasks to the success and failure paths. In this
example, an additional Do task is required on the failure path. The task is
added and renamed Check in Targets. The task instructions direct a manager to
get the targets checked in and then complete the task.
24. Reconcile the success and failure paths by adding an Or task.

Link the final task in the success path and the final task in the failure path to
the Or task.
25. Link the Or task to the Finish node to complete the process.
When the process is run, either the success or failure path is followed, depending
on how you have configured the failure path.
For more information about the Validate task’s behavior, see Task behavior.
Finding error codes

All workflow error codes (EMP errors) are documented in the Integration Toolkit
Function Reference. To see the list of EPM error messages:
1. Go to the Help Library and open the Integration Toolkit Function Reference.
2. At the top of the page, click the Modules header.
3. In the Modules page, scroll down to EPM Errors and click the link.

The EPM Errors page lists every workflow error you can configure the Validate task
to confirm. You can also select errors from any other Teamcenter module.
Note
The EPH_EPM_error_base is 33000. So, for example, if you want to add the
EPM_target_object_not_attached error to the Validate task’s error list,
type 33030 into the Add or Remove Error Code box.
Task behavior
The Validate task’s behavior depends upon how its failure path is configured and
what errors are received.
Failure criteria you

Error thrown (if any) Task behavior
specified
Fail if any error Any error Failure path is followed.
Fail if error on error list
Error on error list Failure path is followed.
occurs
Process halts. Task
Fail if error on error list
Error not on error list remains in Started state
occurs
and an error displays.
Process stops. Task
No failure path configured Any error remains in Started state
and an error displays.
Regardless of whether
Success path followed.
failure path was
No errors occur If no success path was
configured, and whether
configured, process stops.
errors occurred

Chapter
4 Carried forward release notes
Release notes carried forward from Teamcenter 2007 . . . . . . . . . . . . . . . . . . . 4-1

Teamcenter 2007 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Installation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Upgrade release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Usage release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Managing reports, requirements, and schedules . . . . . . . . . . . . . . 4-16
Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Teamcenter Automotive Edition–GM Overlay . . . . . . . . . . . . . . . . 4-29
Administration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Teamcenter File Services and FMS administration . . . . . . . . . . . . 4-34
Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Customization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Integration Toolkit (ITK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Service-oriented architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Teamcenter interfaces release notes . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Teamcenter integrations release notes . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Teamcenter’s Client for Microsoft Office . . . . . . . . . . . . . . . . . . . . 4-50
Teamcenter’s Integration for Microsoft Office and Teamcenter’s Network
Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Internationalization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Platform-specific release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
UNIX platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Hewlett-Packard HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
SUSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Release notes for Teamcenter-related products . . . . . . . . . . . . . . . . . . 4-62
Teamcenter’s lifecycle visualization (Lifecycle Visualization) release
notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Teamcenter’s reporting and analytics release notes . . . . . . . . . . . . 4-65
Managing Teamcenter’s mechatronics process management
data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66

Third-party release notes for Teamcenter 2007 . . . . . . . . . . . . . . . . . . 4-68
Firefox Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Mozilla Web browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69

Chapter
4 Carried forward release notes
The following notes are carried forward from previous versions. These notes still
apply to the current version.
Release notes carried forward from Teamcenter 2007

The following notes are carried forward from Teamcenter 2007. These notes still
apply to the current version.
Teamcenter 2007 product release notes

The following release notes pertain to the upgrade, installation, administration, data
sharing, use, and customization of the Teamcenter software product. When possible,
problem notes include solutions or workarounds.
Installation release notes
The following release notes pertain to installation.

• Error during thin client installation
When installing the Teamcenter server on a Windows 2003 64-bit operating
system, you may encounter the following error during the thin client installation:
Unable to run aspnet_regiis.exe -s
1. Open a command prompt and type the following:

SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
This installs ASP .NET 2.0 and the script maps at the IIS root.
For more information about the ASP .NET
IIS Registration Tool (Aspnet_regiis.exe), see
http://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx.

Chapter 4 Carried forward release notes
2. In the command window, type the following:

SYSTEMROOT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -s
W3SVC/IIS_Web_Site_Identifier/ROOT/"
virtual_directory_or_web_application_name"
IIS_Web_Site_Identifier is the actual ID that references the
Web site and can be found in the IIS Manager column called
Identifier. virtual_directory_or_web_application_name is the
name of the Web application. For example, aspnet_regiis.exe -s
W3SVC/806598041/ROOT/”tc”).
This installs the script map to the specified application root path.
3. Resume the Teamcenter installation.
• Users after first logon get error for some actions

When Teamcenter is installed in PER_CLIENT mode with a two-tier
configuration as a common installation for more than one operating system user,
after the first user has logged on, subsequent users get a Permission Denied
exception when they perform some actions.
Currently, there is no work around for this problem.
• No 64-bit Java Plug-in for 64-bit Mozilla

There is no 64-bit Java Plug-in for 64-bit Mozilla for installing the four-tier
rich client on Linux platforms.
Install 32-bit Mozilla and the Java Plug-in and install the four-tier client.

Carried forward release notes
• Teamcenter File Services does not always automatically start at

Windows reboot
(First published Engineering 2005 SR1)
Teamcenter File Services (TCFS) does not always automatically start on
Windows reboot.
Increase the ServicesPipeTimeout value in the registry to 120,000
milliseconds. The registry entry and information is as follows:
Subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Name: ServicesPipeTimeout
Type: REG_DWORD
Data: 120000
To create this registry entry, perform these steps:
1. Choose Start→Run.
2. Type regedit, and then click OK.
3. Locate and then click the

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control registry
subkey.
4. Right-click Control, point to New, and then click DWORD Value.
5. In the New Value #1 box, type ServicesPipeTimeout, and then press Enter.
6. Right-click ServicesPipeTimeout, and then click Modify.
7. Click Decimal, type the number of milliseconds to wait until the service
times out, and click OK.
For example, to wait 120 seconds before the service times out, type 120000.
8. Close the Registry Editor and restart the computer.

Upgrade release notes
Following is a list of general release notes pertaining to upgrading from a previous

version of Teamcenter Engineering or Teamcenter 2007.
• Orphan types reinstated
Classes and types installed by Teamcenter’s engineering process management
prior to version 9.1.3 that are now obsolete were not removed from the database
during upgrades to later versions. New databases installed for version 9.1.3 or
later do not have these obsolete classes and types. The result is data model
discrepancies between databases and must be corrected by deleting specific types
and reinstating others to the foundation template so that all data models are
consistent regardless of the upgrade or install path.
Note
Types in Engineering Process Management are called business objects
in Teamcenter.
– Upgrading your database from Engineering Process Management to any

version of Teamcenter.
If you upgraded your database from Engineering Process Management to
any version of Teamcenter, the upgrade attempts to remove the following
definitions if there are no instances. If there are instances, Teamcenter
assumes you are still using them so they are not deleted. After the upgrade,
the post_bmideupgradetotc utility extracts these definitions if they exist
and places them into your custom template. If you find the types listed in
the following code, their ownership has been transferred from Teamcenter to
your custom template. You may keep them or delete them.
<TcStandardType typeName="IMAN_analysis" parentTypeName="ImanRelation"
typeClassName="ImanRelation"/>
<TcStandardType typeName="IMAN_basis" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_derivation" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_evolution" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_markup" parentTypeName="ImanRelation"
ypeClassName="ImanRelation"/>
<TcStandardType typeName="IMAN_master_model" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_model" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_nc_data" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_revision" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_structure" parentTypeName="ImanRelation"
<TcStandardType typeName="IMAN_structure_model" parentTypeName="ImanRelation"
<TcForm typeName="Item Revision Master" parentTypeName="Form"
typeClassName="Form" formStorageClassName="ItemVersionMaster"/>
<TcForm typeName="Equipment" parentTypeName="Form"
typeClassName="Form"/>
<TcForm typeName="Equipment Master" parentTypeName="Form"
<TcForm typeName="EquipmentRevision" parentTypeName="Form"
<TcForm typeName="EquipmentRevision Master" parentTypeName="Form"

– Upgrading your database from Engineering Process Management to any

version of Teamcenter prior to 2007.1 MP4 and then to Teamcenter 2007.1
MP4 or later.
If you upgraded your database from Engineering Process Management to
Teamcenter 2007.1 MP1, MP2, or MP3, your custom Business Modeler
IDE template likely has some or all of the reinstated classes and types in
it because the upgrade process required you to extract a custom template
with the post_bmideupgradetotc utility. Because these classes and types
existed in your database, yet none had any XML representation in the
foundation template, the utility pulled them into your template. If you plan
to continue using one of these versions of Teamcenter, do not remove these
XML definitions from your custom template. It will be fixed once you move to
a later version. When you upgrade this database to Teamcenter 2007.1 MP4
or later, these classes and types have XML representation in the foundation
template. Since both your template and the foundation template have the
same definitions, these names will collide. Typically you see these collisions
occur during an upgrade, when installing a new feature on the server using
Teamcenter Environment Manager or when using Business Modeler IDE. To
fix this, remove these definitions manually from the XML source files in your
custom Business Modeler IDE template.
1. Install the most recent version of the Business Modeler IDE client and
the templates that you require. For example, if you are upgrading to
Teamcenter 2007.1 MP4, install the Teamcenter2007.1 MP4 Business
Modeler IDE client and templates.
2. Import your previous Business Modeler IDE custom template project

into the new Business Modeler IDE client.
3. During the import, the custom data model is validated against the new
out-of-the-box template definitions. Any collisions are shown in the
Console view in the Business Modeler IDE client. A collision in the
Business Modeler IDE for a class or type looks similar to the following:
Model Error: business_objects.xml Line:19 Column:57 A Class is
already defined with the name "POM_index". Choose another name.
Model Error: business_objects.xml Line:45 Column:111 A Business

Object is already defined with the name "CORCoreDList". Choose
another name.
4. For each collision, check if the colliding definition is in the list of

reinstated types that follows. Note that name collisions can occur for
other reasons, such as defining a custom type that has the same name as
a out-of-the-box type. These kinds of collisions that you created must be
fixed in a different manner. If the collision listed in the Console view
matches one of the definitions listed below, then manually remove the
XML definition from your source file.
Note
Some of the XML definitions listed many not appear in your
template. You may have none, or some combination, or all of them.
$TcStandardType typeName="CORCoreDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>

<TcStandardType typeName="CNDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="CNRevDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>

<TcStandardType typeName="WACSAppDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>

<TcStandardType typeName="WAIACoreDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="ANDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="CTDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="CPRCoreDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="WAIAAppDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="WACSCoreDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="CORAppDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="CNAppDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="CPRAppDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="ITEMAppDList" parentTypeName="DistributionList" typeClassName="DistributionList"/>
<TcStandardType typeName="CM_CR_approver_list" parentTypeName="ImanRelation" typeClassName="ImanRelation"/>
<TcStandardType typeName="CM_list" parentTypeName="ImanRelation" typeClassName="ImanRelation"/>
<TcStandardType typeName="CM_state" parentTypeName="ImanRelation" typeClassName="ImanRelation"/>
<TcStandardType typeName="Change Order" parentTypeName="ImanRelation" typeClassName="ImanRelation"/>
<TcStandardType typeName="CM_decision" parentTypeName="ImanRelation" typeClassName="ImanRelation"/>
<TcStandardType typeName="ReferenceFolder" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM Context" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM Default Order Data" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM Setup routing" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CP ITEM" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM SETUP" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM Default Proposal Data" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM_Routing Slips" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM LIST" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CP PACKAGE" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CO REFERENCE" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CP Item Folder" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CO ITEM REVISION" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CO Package" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM Context Job" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CP REFERENCE" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CO WHERE USED" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM Context Routing" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="CM Package" parentTypeName="Folder" typeClassName="Folder"/>
<TcStandardType typeName="IMAN_wolf_link" parentTypeName="ImanRelation" typeClassName="ImanRelation"/>
<TcStandardType typeName="IMAN_CCContent" parentTypeName="ImanRelation" typeClassName="ImanRelation"/>
<TcStandardType typeName="NameCounters" parentTypeName="POM_application_object", typeClassName="NameCounters"/>
<TcStandardType typeName="NameFields" parentTypeName="POM_application_object" typeClassName="NameFields"/>
<TcStandardType typeName="NameRules" parentTypeName="POM_application_object" typeClassName="NameRules"/>
<TcStandardType typeName="POM_rdbms_dd" parentTypeName="POM_object" typeClassName="POM_rdbms_dd"/>
<TcStandardType typeName="POM_table" parentTypeName="POM_rdbms_dd" typeClassName="POM_table">
<TcStandardType typeName="POM_view" parentTypeName="POM_rdbms_dd" typeClassName="POM_view"/>
<TcStandardType typeName="POM_column" parentTypeName="POM_rdbms_dd" typeClassName="POM_column"/>
<TcStandardType typeName="POM_index" parentTypeName="POM_rdbms_dd" typeClassName="POM_index"/>
<TcStandardType typeName="EIM_external_backpointer" parentTypeName="POM_object", typeClassName=
"EIM_external_backpointer"/>
<TcStandardType typeName="CMMV_transform" parentTypeName="POM_object" typeClassName="CMMV_transform"/>
<TcForm typeName="CMSForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="CMIDNum"/>
<TcForm typeName="CORForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="ChangeReviewData"/>
<TcForm typeName="ChargeList" parentTypeName="Form" typeClassName="Form"/>
<TcForm typeName="CNRForm" parentTypeName="Form" typeClassName="Form"/>
<TcForm typeName="WCForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="ChangeReviewData"/>
<TcForm typeName="COForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="ChangeOrderData"/>
<TcForm typeName="CPForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="ChangeProposalData"/>
<TcForm typeName="WIForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="ChangeReviewData"/>
<TcForm typeName="ReasonList" parentTypeName="Form" typeClassName="Form"/>
<TcForm typeName="CPRForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="ChangeReviewData"/>
<TcForm typeName="CNForm" parentTypeName="Form" typeClassName="Form" formStorageClassName="ChangeNotificationData"/>
<TcForm typeName="Task Form" parentTypeName="Form" typeClassName="Form"/>
<TcDataset typeName="IMANReportData" parentTypeName="Dataset" typeClassName="Dataset">
<TcDSViewTool name="Report Viewer"/>
<TcDSEditTool name="Report Viewer"/>
</TcDataset>
<TcDataset typeName="IMANReportDesign" parentTypeName="Dataset" typeClassName="Dataset">
<TcDSViewTool name="Report Design"/>
<TcDSEditTool name="Report Design"/>
</TcDataset>
<TcClass className="NameCounters" parentClassName="POM_application_object" isExportable="true"
isUninstantiable="false" isUninheritable="false" applicationName="INFOMANAGEV200">
<TcAttribute attributeName="counter_name" attributeType="POM_string" maxStringLength="32"
isArray="false" followOnExport="false" isNullsAllowed="true" isUnique="false"
isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"
isTransient="false" exportAsString="false" noBackpointer="false"/>
<TcAttribute attributeName="no_of_chars" attributeType="POM_int" maxStringLength="0"
isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"
<TcAttribute attributeName="start_pos" attributeType="POM_int" maxStringLength="0"
<TcAttribute attributeName="char_type" attributeType="POM_string" maxStringLength="1"
<TcAttribute attributeName="init_value" attributeType="POM_string" maxStringLength="32"


<TcAttribute attributeName="max_value" attributeType="POM_string" maxStringLength="32"
<TcAttribute attributeName="next_id" attributeType="POM_string" maxStringLength="32"
</TcClass>
<TcClass className="NameFields" parentClassName="POM_application_object" isExportable="true"
<TcAttribute attributeName="type_name" attributeType="POM_string" maxStringLength="32"
<TcAttribute attributeName="property_name" attributeType="POM_string" maxStringLength="32"
<TcAttribute attributeName="case" attributeType="POM_int" maxStringLength="0"
<TcAttribute attributeName="rule_tag" attributeType="POM_typed_reference" maxStringLength="0"
isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="NameRules"/>
</TcClass>
<TcClass className="NameRules" parentClassName="POM_application_object" isExportable="true"
<TcAttribute attributeName="rule_name" attributeType="POM_string" maxStringLength="32"
isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="true"
<TcAttribute attributeName="pattern" attributeType="POM_string" maxStringLength="240"
isArray="true" followOnExport="false" isNullsAllowed="true" isUnique="false"
isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="-1"
<TcAttribute attributeName="autogen" attributeType="POM_logical" maxStringLength="0"
<TcAttribute attributeName="counter_tags" attributeType="POM_typed_reference"
maxStringLength="0" isArray="true" followOnExport="false" isNullsAllowed="true"
isUnique="false" isPublicRead="false" isPublicWrite="false" isCandidateKey="false"
arrayLength="-1" isTransient="false" exportAsString="false" noBackpointer="false"
typedRefClassName="NameCounters"/>
</TcClass>
<TcClass className="POM_rdbms_dd" parentClassName="POM_object" isExportable="false"
isUninstantiable="true" isUninheritable="false" applicationName="POM">
<TcAttribute attributeName="dbms" attributeType="POM_string" maxStringLength="33"
isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"
<TcAttribute attributeName="mapped" attributeType="POM_logical" maxStringLength="0"
</TcClass>
<TcClass className="POM_table" parentClassName="POM_rdbms_dd" isExportable="false"
isUninstantiable="false" isUninheritable="false" applicationName="POM">
<TcAttribute attributeName="name" attributeType="POM_string" maxStringLength="33"
<TcAttribute attributeName="columns" attributeType="POM_typed_reference" maxStringLength="0"
isArray="true" followOnExport="false" isNullsAllowed="false" isUnique="false"
isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="-1"
isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="POM_column"/>
</TcClass>
<TcClass className="POM_view" parentClassName="POM_rdbms_dd" isExportable="false"
</TcClass>
<TcClass className="POM_column" parentClassName="POM_rdbms_dd" isExportable="false"
<TcAttribute attributeName="object" attributeType="POM_typed_reference" maxStringLength="0"


isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="POM_rdbms_dd"/>
<TcAttribute attributeName="type" attributeType="POM_int" maxStringLength="0"
<TcAttribute attributeName="length" attributeType="POM_int" maxStringLength="0"
<TcAttribute attributeName="nulls_allowed" attributeType="POM_logical" maxStringLength="0"
</TcClass>
<TcClass className="POM_index" parentClassName="POM_rdbms_dd" isExportable="false"
<TcAttribute attributeName="columns" attributeType="POM_typed_reference" maxStringLength="0"
isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="-1"
isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="POM_column"/>
<TcAttribute attributeName="table" attributeType="POM_typed_reference" maxStringLength="0"
isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="POM_table"/>
<TcAttribute attributeName="unique" attributeType="POM_logical" maxStringLength="0"
</TcClass>
<TcClass className="EIM_external_backpointer" parentClassName="POM_object" isExportable="false"
isUninstantiable="false" isUninheritable="false" applicationName="EIM">
<TcAttribute attributeName="to_reference" attributeType="POM_untyped_reference"
maxStringLength="0" isArray="false" followOnExport="false" isNullsAllowed="false"
isUnique="false" isPublicRead="false" isPublicWrite="false" isCandidateKey="false"
arrayLength="0" isTransient="false" exportAsString="false" noBackpointer="false"/>
</TcClass>
<TcClass className="CMMV_transform" parentClassName="POM_object" isExportable="false"
isUninstantiable="false" isUninheritable="false" applicationName="CMMV">
<TcAttribute attributeName="transform" attributeType="POM_double" maxStringLength="0"
</TcClass>
<TcTool toolName="Report Design" toolMimeType="" toolSymbol="ReportDesign" toolVersion="1.0"
toolReleaseDate="">
<TcToolInputFormat formatName="BINARY"/>
<TcToolOutputFormat formatName="BINARY"/>
</TcTool>
<TcTool toolName="Report Viewer" toolMimeType="" toolSymbol="ReportViewer" toolVersion="1.0"
toolReleaseDate="">
<TcToolInputFormat formatName="BINARY"/>
<TcToolOutputFormat formatName="BINARY"/>
</TcTool>
5. When you are finished removing the collisions, right-click the project in
the Business Modeler IDE and choose Reload Data Model. The custom
data model is reloaded and validated against the out-of-the-box template
data model.
6. If there are any issues, they are displayed in the Console view in
the Business Modeler IDE. Fix the errors, and then repeat step 5.
Repeat these steps until all errors are fixed. Contact GTAC if you need
assistance.

• Teamcenter upgrade fails with custom types

If you have a custom type name with the same name as the parent class, the
custom type is identified and added to the custom templates, but the upgrade
fails. For example, you have a custom storage_media type that belongs to the
storage_media class.
Before upgrading to Teamcenter 2007, rename the custom type name to anything
other than the parent class. For example, rename the storage_media type to
storage_media_custom before you upgrade.
• Database configuration for large upgrades

If your upgrade changes or deletes a large number of records, it can fail if the
database is not sized properly. The Oracle error looks like this:
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
The following upgrade examples can lead to this error:

install -mod_attr infodba ${TC_USER_PASSWD} dba POM_application_object
owning_user POM_attr_no_pom_backpointer +
install -mod_attr infodba ${TC_USER_PASSWD} dba POM_application_object
last_mod_user POM_attr_no_pom_backpointer +
These commands update many rows in the pom_backpointer table.

The number of rows updated is approximately three times the size of the
ppom_application_object table. You can determine the table size with the
following SQL command:
SELECT COUNT(puid) FROM ppom_application_object;

You must have a large undo or rollback tablespace and a large TEMP tablespace.
Increase the size of both the TEMP and undo tablespaces to at least 5 GB each.
1. Use the following SQL command to see where the data files reside:
SELECT tablespace_name,file_name FROM dba_data_files;
The results may look like this:
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
In this case, all data files are located in the D:\ORACLE\ORADATA

directory.

2. Add a data file to the TEMP tablespace.

ALTER TABLESPACE TEMP ADD tempfile ’D:\ORACLE\ORADATA\temp2.dbf’
size 5000M;
3. Add a data file to the undo tablespace.

ALTER TABLESPACE UNDOTBS01 ADD datafile ’D:\ORACLE\ORADATA\undotbs2.dbf’
size 5000M;
To help the upgrade perform well, ensure the redo logs are sized properly (100M
each) and reside on a separate disk from the data. To resize the redo logs:
1. Set the ORACLE_SID environment variable.
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;
The results may look like this:

3 ONLINE STALE E:\ORACLE\ORADATA\DPVPERF\REDO03.LOG
2 ONLINE E:\ORACLE\ORADATA\DPVPERF\REDO02.LOG
1 ONLINE STALE E:\ORACLE\ORADATA\DPVPERF\REDO01.LOG
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;
5. Run the following command to force the log switch:

ALTER SYSTEM SWITCH LOGFILE;
6. (Optional) Drop redo log groups 1, 2, and 3:

ALTER DATABASE DROP LOGFILE GROUP 1;
Note
If the group number is the current group and you cannot drop it, run
the command to force the log switch to make group 4, 5, or 6 current.

• Databases dating from before iMAN version 4 may have two

IMAN_Drawing relation types
Before iMAN 4.0, an IMAN_drawing relation was defined but never used. At
version 7.0, an IMAN_Drawing relation was defined and used in ProductVision.
If you have a database that originated from a pre-4.0 version, you may have an
IMAN_drawing relation defined. If so, the Business Modeler IDE does not find
it in the out-of-the-box set of definitions and includes it in the customer-template
definition.
If you have a pre-4.0 version database, before running the Teamcenter 2007
upgrade:
install_types –u=infodba -p=password -g=dba -f=delete
-t=IMAN_drawing -c=ImanRelation
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
To get a complete list of types installed in your database, run the following utility:
install_types u=infodba -p=password -g=dba -f=list
This lists the several hundred types available.
• nxmgr_add_note_types utility fails during upgrade if seed parts are

moved
By default, the Inch and Metric templates are associated in the Unigraphics
seed parts folder in the infodba user Home folder. If these templates are moved
to a different folder, the nxmgr_add_note_types utility fails when it runs as
part of an upgrade and the database becomes inaccessible.
Move the templates back to the Unigraphics seed parts folder before starting
the upgrade.

• Missing database index

(First published Engineering 9.0)
After you upgrade a database, a problem resulting from a missing database
index can cause performance problems.
After upgrading a database, execute the following commands:
Windows systems:
set TC_ROOT=tc-root-directory
set TC_DATA=tc-data-directory
call %TC_DATA%\tc_profilevars
%TC_BIN%\index_verifier -u=infodba -p=password -g=dba > missing_indexes.sql
%TC_BIN%\install -acg infodba password %ORACLE_SID% < missing_indexes.sql
UNIX systems:
export TC_ROOT=tc-root-directory
export TC_DATA=tc-data-directory
. $TC_DATA/tc_profilevars
$TC_BIN/index_verifier -u=infodba -p=password -g=dba > missing_indexes.sql
$TC_BIN/install -acg infodba password $ORACLE_SID < missing_indexes.sql

Usage release notes

The following release notes pertain to the usage of Teamcenter 2007.
My Teamcenter
The following release notes pertain to My Teamcenter.
• Unable to open text file with Microsoft Word
If you choose File→Open With and attempt to open a text file with Microsoft
Word, Teamcenter displays an error.
Use Notepad, Wordpad, or another text editor to open text files.
• Microsoft Office documents open externally instead of in the Viewer

pane
If you have Microsoft Office 2007 installed and you select a MSWord, MSWordX,
MSPowerpoint, MSPowerpointX, MSExcel, or MSExcelX dataset in My
Teamcenter and switch to the Viewer pane, the document is opened externally
in its application (for example, in PowerPoint) and not embedded in the Viewer
pane.
By default, Microsoft Office 2007 prevents Office 2007 documents from being
embedded in another application. For example, if you try to view a Word
document within Internet Explorer, it opens the document in Microsoft Word
and not within Internet Explorer.
– To enable embedded viewing in Microsoft Windows Vista, you must change

registry settings. For more information, see the instructions at this link:
http://support.microsoft.com/kb/927009
– To enable embedded viewing in Windows XP:

1. Open Windows Explorer.
2. Choose Tools→Folder Options.
3. Click the File Types tab.
4. In the Registered File Types list, select the DOC extension.
5. Click the Advanced button.
6. In the Edit File Type dialog box, ensure that Browse in same window
check box is selected. Click OK.
7. Repeat steps 4–6 for the DOCX, PPT, PPTX, XLS, and XLSX extensions.

• Clicking the Save button in Viewer pane does not save dataset
(First published Teamcenter 2007.1
If you edit a Microsoft Word dataset in the My Teamcenter Viewer pane and
click the Save button on the Word toolbar within the Viewer pane, the changes
are not saved to the dataset.
Click the Save button at the top of the Viewer pane. The Save button on the
Word toolbar within the Viewer pane saves the document to the client machine
but not the dataset.
• Product view in My Teamcenter may disappear after loading

(First published Teamcenter 2007.1
After loading the product view in My Teamcenter with the Load Product View
button, it sometimes appears briefly and then disappears.
Either click the top line to make the parts visible again or load the product
view in Structure Manager.
• Validation report gives wrong Total Number, Target, and User results
(First published Teamcenter 2007
When using the validation results query to generate a validation report, the
validation report gives wrong Total Number, Target, and User results.
Use VO – Validation Results search criteria to query the validation results.
This section contains release notes pertaining to managing product structures.
Structure Manager
The following release notes pertain to Structure Manager (Structure Manager).

• Incremental change (IC) context override not seen when change is
made under new IC revision
If you change an attribute on a BOM line under a new revision of an IC that
already has an IC-tracked change, the change is not displayed and the attribute
is rolled back to its original value. Refreshing the BOM line also fails to display
the new value.
Close Structure Manager and reopen the structure.

• Implemented By and Realized By relationships are not displayed when

copied in another structure
If you copy a product structure containing Implemented By or Realized By
relationships and paste it in another product structure, the relationships are not
displayed in the new structure.
Re-create the Implemented By and Realized By relationships in the new
structure.
• Separation of view and edit properties in Manufacturing Process

Planner and Structure Manager
In Manufacturing Process Planner and Structure Manager, there are not
separate dialog boxes for the view and edit properties functionality for BOM line
properties as there are for properties in My Teamcenter.
Use the Properties dialog box to edit properties.
• Rebaselining an unchanged Structure Manager structure does not

create a new baseline
If the ITEM_smart_baseline preference is set to ON and a user tries to create
a baseline for an assembly that has not changed after a previous baseline, a new
baseline is not created. No informational message is displayed in the client to
indicate this.
• Structure Manager behavior after four-tier server session time-out

Structure Manager edits are lost if a four-tier server session time-out occurs.
There are four-tier configuration settings that cause a server to time-out if
clients are inactive. If a server times out and is killed, Structure Manager
client-pending changes are lost.
Four-tier administrators should set the time-out in a way that a time-out does
not occur for a server in edit mode. For Structure Manager, this corresponds to
an active SAVE button in at least one BOM dialog box, which represents at least
one Structure Manager session with unsaved changes. The default is 8 hours
for a server in EDIT mode. If sessions are up overnight, a 24-hour time-out (or
longer to allow for weekends) addresses most issues.

Repeatable Digital Validation (RDV)
The following release notes pertain to Repeatable Digital Validation (RDV).

• RDV incorrectly allows changes to named variant expression with
values outside the variability of architecture breakdown element
You can incorrectly modify named variant expressions (NVEs) with values
outside of the variability of architecture breakdown elements (ABEs) on which
they are already applied. Modifying NVEs outside the variability of ABEs does
not cause severe problems, such as a server crash or internal error.
Do not modify NVEs outside the variability of the ABEs. You can also remove
the NVEs and add them to the ABE again.
Managing reports, requirements, and schedules

This section contains release notes pertaining to managing reports, requirements,
and schedules.
Report Designer
The following release note pertains to the use of Report Designer.

• Byte size cannot be displayed in Property Finder Formatter search
results
In Search Results in the Edit menu of the Property Selection dialog box, when
obtaining ImanFile references, the entry for the byte size is missing and the
file size appears twice. The second file size is actually for the property path of
byte_size. If you select the one for Dataset.ref_list.byte_size, the resulting
Property Finder Formatter (PFF) column displayed still has Title of File Size
and has file size data. Thus, the byte size column and data cannot be displayed
in Search Results.
PFF cannot display byte sizes in the display tables. Use the properties table or
viewer to see this information.

Requirements Manager
The following release notes pertain to the use of Requirements Manager.
• Reference designators cannot be imported in packed format

Properties, such as Find No, that need a unique value cannot be set on a packed
BOM line. Microsoft Excel Import prevents you from updating the property on
packed reference designators.
Unpack the BOM line and set a unique value on each occurrence. To update
the property on packed reference designators, unpack the rows in Excel before
importing.
• Duplicate reference designators created during import

Duplicate reference designator values are imported when the default value
is provided in the control file. If you enter default values for the reference
designator columns, a warning is displayed about duplicate reference
designators.
Do not give default values for reference designators in the control file.
Schedule Manager
The following release notes pertain to Schedule Manager.
• Closing Schedule Manager with the close button sometime displays

Save dialog box out of sequence
The following steps cause the Save dialog box to appear after Schedule Manager
closes rather than before:
1. Create a program view dataset and send it to Schedule Manager.
2. Add a schedule to the program view.
3. Save it from the main menu.
4. Make additional changes before saving again.
5. Close Schedule Manager with the close button on the window tab.

Use the File→Close menu command instead of the close button.

• Copy/Paste does not copy all task attributes

When a task is copied and pasted, some attributes are not copied. For example,
workflows are not copied.
This section contains release notes pertaining to Teamcenter’s manufacturing

process management and managing manufacturing data.
Classification
The following release notes pertain to Classification.

• Quick search returns no results
If you search for an existing class by name in the quick search box below the
hierarchy, it returns no results.
Click the Search button below the hierarchy to use the Search dialog box
instead.
• Graphics builder preference name change

The graphics builder preference name has changed from UGGraphicsBuilder
to NXGraphicsBuilder. Adjust the following preferences and define both as
site preferences:
– ICS_GraphicsBuilder=NXGraphicsBuilder
– NXGraphicsBuilder=
ActivationMethod:TCE_Activation,
CommandLine:pathstart_nx_graphicsbuilder.bat

Guided component search
The following contains a list of release notes pertaining to the guided component
search (GCS).
• Import of Manufacturing Tooling Library and Resource Manager
sample data
When you import the Manufacturing Tooling Library or Resource Manager
sample data, it is imported using the item item type. You cannot import it using
a different item type.
• Future enhancements
(First published Teamcenter Engineering 2005)
The following will be addressed in a future version of Teamcenter:
– GCS search with DIFF and FACT operators does not work.
– GCS automatic attribute mapping does not work.

These enhancements will be available in a future version of Teamcenter.
• Adding connection point definitions takes several minutes

When you add connection point definitions (CPDs) to a class and click Save,
the system appears to hang.
Adding connection points (CPs) to instances can take several minutes. Wait until
all CPs are generated and the Edit button is active.
• Updating connection types and connection point definitions takes

several minutes
When updating connection types (CTs) or connection point definitions (CPDs),
the system hangs.
Updating CTs, CPDs, and connection points (CPs) can take several minutes.
Wait until the update is complete.

Manufacturing Process Planner
The following release notes pertain to Manufacturing Process Planner.

• Variant condition added to a part does not appear in the process window
If you add a variant condition to a part in the product structure, it does not
immediately appear on the assigned line in the process window.
Choose View→Refresh.
• Assigned occurrence for GDE link is not accurate after Manufacturing

Process Planner is reopened
If you use a GDE and then remove the GDE line, the assigned occurrence shows
the link is broken. If you close and reopen the Manufacturing Process Planner
application, the link is not broken. If you search for the object in the other pane,
the removed GDE line reappears with a Java error displayed in the Quantity box.
• Property list of criteria for broken links candidates depends on BOM

line columns
In the Repair Broken Links dialog box, the display of criteria details for the
broken link candidates search depends on the BOM line columns. The list of
available properties is the list of BOM line columns. Properties not exposed in
the BOM lines are not available in the list. Also, if any property is not exposed
as a BOM line column (for example, added from a preference), the label for it is
displayed as the internal property name.
Add the property to the BOM line columns to display it in the property list with
the localized label.

Publish
The following release note pertains to the use of Publish.

• Portfolio page list update does not reflect modular variant
configurations
When a structure that is configured with modular variants is used to generate a
list of pages in a portfolio, unconfigured pages can appear when the portfolio is
updated.
Use classic variants to configure structures, or cut the unwanted pages from
the portfolio after updating.
Sharing data
The following release notes pertain to data sharing.
Data Exchange
The following release notes pertain to Data Exchange.

• Cannot transfer a dataset shared by multiple item revisions
If you revise an item revision without revising its dataset, both the new and old
item revisions share the same dataset. You cannot transfer that dataset using
Data Exchange.
Currently, there is no work around for this problem. This problem will be
resolved in a future maintenance release. Contact GTAC for further information
about availability.
• Customization may alter behavior of monitoring interface

If the behavior of the monitoring interface changes, it may be because of your
customizations. If it does fail, compare your mapping to the Teamcenter
out-of-the-box (OOTB) mapping.
resolved in a future patch. Contact GTAC for further information about
availability.

• Remote import that transfers ownership in Global Services fails to

update ownership in ODS
If you perform a remote import that transfers ownership using Global Services,
it fails to update the ownership in ODS.
resolved in a future patch. Contact GTAC for further information about
availability.
• ItemRevision sequences not supported for Data Exchange transfers

When you export an assembly or part that contains ItemRevision sequences,
the ItemRevision object on the destination site is not properly synchronized
with the source site.
The sequences feature for item revisions must be turned off by setting the
following site preference:
TCCheckoutReserveOnly=
Item
ItemRevision
This ensures that sequences are not created when an item revision is created
or checked in. This must be set immediately after you install the Teamcenter
server before any sequences are created in the Teamcenter database. For more
information about this site preference, see the Preferences and Environment
• Object Directory Services (ODS) operations not supported between

Teamcenter and Teamcenter’s enterprise knowledge management sites
All Data Exchange operations related to the Object Directory Services (ODS)
are supported only for Teamcenter-to-Teamcenter operations. This includes
publishing objects to the ODS, remote search operations, and remote import
operations based on remote search results.

• Teamcenter to Teamcenter and Briefcase transfers through Data

Exchange support NX and JT CAD data only
Standard Teamcenter Data Exchange supports exporting and importing CAD
data only when it is NX and JT data.
Do not attempt to transfer other types of CAD data.
• Performing local actions on replicas transferred through Data Exchange

Replica objects can have the following actions applied locally:
Enterprise Knowledge
Management action Teamcenter action
Set the LCS state Release
Add attachments Add datasets or forms
Assign to a project
Add a license Add a certificate
If you locally set the LCS state on a replica in Enterprise Knowledge

Management, subsequent transfers of the replica from Teamcenter cause
the release status in Teamcenter to overwrite the LCS state in Enterprise
Knowledge Management.
Customized the system to create a local LCS attribute and use that for the local
release.
• Data Exchange does not support the continue on error feature

If an error occurs during a Data Exchange transfer process, the entire
transaction is rolled back. Partial rollbacks are not supported. You can select
the Continue On Error option in some Data Exchange interfaces; however, the
option is cleared during the export and import process.
Do not select the Continue On Error check box.

Global Services
The following release notes pertain to Global Services software.

• NoSuchMethodError exception when using Teamcenter Engineering 9
and Teamcenter Engineering 2005/2007 connectors in the same EAR file
Global Services does not support including these two connectors in the same Web
application (EAR file).
Using the Web Application Manager, build a Web application (EAR file) with all
of the required Global Services solutions but without one of the Teamcenter
Engineering connectors. Build a second EAR file that contains the Teamcenter
Engineering connector not included in the first EAR file. Ensure that you provide
different Deployable File Name values. The two EAR files can be deployed in the
same application server without causing errors. For more information about Web
tier installation, see the Installation on Windows Servers Guide or Installation
on UNIX and Linux Servers Guide.
• Sample rich client BOD does not display revision number of item
The sample rich client BOD does not display the revision number of the item.
Ignore the revision column or modify the BOD to remove the revision column.
• Autopopulated nonmandatory fields should not be populated by user in

the Insert form
Several of the nonmandatory boxes (for example, Part Name) of the Teamcenter
assembly BOD are autopopulated by Teamcenter.
Currently, Global Services does not have a capability to suppress such
autopopulated fields from the Insert form. Therefore, do not enter information in
these boxes when using the Insert form.
• Sample Teamcenter item BOD cannot be used for update

The supplied sample Teamcenter item BOD cannot be used for update because
the units of measure (UOM) attribute is not marked as updateable.
Modify the sample Teamcenter item BOD to include the following:
<default-value>null</default-value>
<update-able>true</update-able>

• Global Services conversion tool shows an error but conversion succeeds

Output from the Global Services conversion tool shows an exception similar to
the following when converting Teamcenter Integrator 7.x files:
D:\stagingDir\lib>java -jar convert.jar d:\accelis_1_dsj_7a2\
filteredsrc\core\runtime\bos\AccelisMessage.xml d:\stagingDir\lib\am.xml
2006/11/13-16:45:59,877 UTC MLD Log init: com.teamcenter.mld version 0.0.3d
(2005-06-06)2006/11/13-16:45:59,877 UTC MLD Log init: Instance configuraton
hierarchy object: org.apache.log4j.Hierarchy@1e0cf702006/11/13-16:45:59,887
UTC MLD Log init: Configured to Global log4j LoggerRepository:
org.apache.log4j.Hierarchy@b6ece5, local hierarchy: org.apache.log4j.
Hierarchy@1e0cf702006/11/13-16:45:59,897 UTC MLD Log init: Note: com.
teamcenter.mld Log initialization did not find any log4j configuration file(s)
in directory D:\stagingDir\lib\.
Failed to get data store com.edsplm.plmi.config.ConfigurationError:
FATAL ERROR CFG01040: Failed to load the configuration information.
’com.edsplm.plmi.config.ConfigurationError: FATAL ERROR CFG01040:
Failed to load the configuration information. ’
at com.edsplm._plmi.config.InitialConfig.initialize(InitialConfig.java:69)
at com.edsplm._plmi.config.InitialConfig.getInstance(InitialConfig.java:79)
at com.edsplm._plmi.config.AccelisConfig.getRuntimeLocation
(AccelisConfig.java:347)
at com.edsplm.plmi.config.AccelisDataStoreFactory.<clinit>
(AccelisDataStoreFactory.java:35)
at com.edsplm._plmi.log.LoggerFactory.<clinit>(LoggerFactory.java:44)
at com.edsplm.plmi.log.LoggerFactory.getLogger(LoggerFactory.java:80)
at com.edsplm.plmi.log.LoggerFactory.getLogger(LoggerFactory.java:52)
at com.edsplm._plmi.jaxb.JAXBUtil.<clinit>(JAXBUtil.java:34)
at com.teamcenter.globalservices.config.Convert.main(Convert.java:80)
runtime location = UNSPECIFIED LOCATION
Converted XML written to d:\stagingDir\lib\am.xml
</clinit>
</clinit>
</clinit>

No workaround is required. The conversion succeeds and the converted files are
available to use.

Multi-Site Collaboration
The following release notes pertain to Multi-Site Collaboration.

• Default Oracle parameter must be changed for optimal Multi-Site
Collaboration functionality
The Multi-Site Collaboration ensure_site_consistency utility may fail to
recover failed transfer operations due to locked objects associated with dead
processes.
The Oracle SQLNET.EXPIRE_TIME parameter must be set to a valid
value. The recommended value is 10. It must not be 0 or unset. The
SQLNET.EXPIRE_TIME parameter is used to set a time interval, in minutes,
to determine how often a probe should be sent verifying that client/server
connections are active.
• Sharing data with pre-Teamcenter 2007.1 MP3 databases causes variant

expression block and variant condition errors
(First published Teamcenter 2007.1.3
If you share data between a Teamcenter 2007.1 MP3 site and a site with an
earlier version of Teamcenter or Teamcenter Engineering, you may receive
errors if you use an item revision variant expression block or an occurrence
variant condition.
Run the following utilities on the pre-Teamcenter 2007.1 MP3 database:
install -mod_attr infodba infodba dba ItemRevision variant_expression_block

POM_attr_follow_on_export +
install —mod_attr infodba infodba dba ItemRevision variant_expression_block
POM_null_is_valid +
install —mod_attr infodba infodba dba PSOccurrence variant_condition
POM_attr_follow_on_export +
install —set_attr infodba infodba dba PSOccurrence variant_condition
NULLTAG
install —mod_attr infodba infodba dba PSOccurrence variant_condition
POM_null_is_valid —
• Multi-Site Collaboration in HTTP mode requires a single SSO domain

When a Teamcenter Multi-Site Collaboration site is configured for HTTP
transport mode (Is HTTP Enabled check box), all of the participating Multi-Site
Collaboration sites must be configured in the same Security Services Identity
Service.
Configure all Teamcenter sites in the Multi-Site Collaboration network in the
application registry of a single Security Services instance. For information about
configuring Security Services, see Security Services Installation/Customization.

• Remote checkin behavior

If you attach a local object to a replica using remote checkout, upon remote
checkin the attached local object can be transferred with ownership, can be sent
as replica, or can be opted not to be sent at all. You can configure this behavior
from the user interface and preference. From the Remote Checkin dialog box
advanced options, you can select a relation to be transferred with ownership.
The option to send as replica is not yet available in the user interface. Therefore,
a relation listed in the TC_remote_checkin_relation_send_as_replica
preference is sent as replica.
When you select a particular relation from the user interface, the following table
explains the behavior to local attached behavior.
Relation included Relation specified

in user interface in preference Behavior
Yes Yes Transfer of ownership
Yes No Transfer of ownership
No Yes Sent as replica
No No Not transferred at all
• Remote checkin/checkout and incremental change

Normally the remote checkin of BOMView and BOMViewRevision objects,
which have incremental changes made to them within Structure Manager,
results in the automatic transfer of ownership of the related engineering
change object back to the master site. In the case where the only incremental
changes made are attachment deletes, the engineering change object is not
automatically transferred to the master site and the delete actions are not be
visible in Structure Manager.
Manually transfer the ownership of the engineering change object back to the
master site.

• dsa_util utility does not change externally managed user constructs to

remote
The dsa_util utility does not recognize externally managed users, groups, roles,
persons, and group members with a datasource attribute value greater than
0 and convert them to remotely managed (for example, managed by an LDAP
external directory at a remote site). Because the dsa_util utility is the only way
user constructs can be converted to remotely managed, no user construct objects
in the Organization user interface appear as remotely managed.
• Multisite licenses
(First published Engineering 2005)
Prior to Teamcenter Engineering 2005, the Multi-Site Collaboration Server
license was checked only when the Object Directory Services (ODS) server
process starts up. Starting with Teamcenter Engineering 2005, all multisite
operations, such as remote import, publication and remote search, checks the
Multi-Site Collaboration server license to make sure that this license was
purchased. If the Multi-Site Collaboration server license is not available, users
get an error message when performing multisite operations. Make certain the
Multi-Site Collaboration server license, as well as the multisite user licenses, are
available prior to deploying multisite in Teamcenter 2007 and future versions.
PLM XML
The following release notes pertain to PLM XML.
• PLM XML import and export is not supported by vendor management
If you import or export a vendor revision by choosing Tools→Import→Objects or
Tools→Export→Objects and clicking the PLM XML button, the Vendor Role
information associated with a vendor revision is not processed.
Run either the tcplmxml_import or the tcplmxml_export utility from the
command line to transfer vendor management objects from one Multi-Site
Collaboration site to another.

Teamcenter Automotive Edition–GM Overlay
The following releases note pertain to GM Overlay.
GM Overlay upgrade
The following release notes pertain to GM Overlay upgrades.

• Business Modeler IDE reports unsupported classes during GM Overlay
upgrade
If your Engineering Process Management installation includes Teamcenter
Automotive Edition with the GM Overlay and AutoCAD Integration features,
you must fix application names on certain AIE classes before you upgrade to
Teamcenter. If you do not do this, the Business Modeler IDE console reports
errors while importing the customer template. These errors are similar to the
following example:
Model Error: business_objects.xml Line:2622 Column:60 Change TcClass
is not supported.
The line number cited in the error message corresponds to an AIE class data
model element in the customer template.
The Teamcenter site administrator must fix AIE class application names by
performing the following steps on the database server before you upgrade to
Teamcenter 2007:
1. Open a Teamcenter command shell (with the Teamcenter environment set).
2. Enter the following command:

install -acg DB-user-name DB-password DB-name
Replace DB-user-name, DB-password, and DB-name with the user name,

password, and database name for the Engineering Process Management
database.
3. Perform the following steps for each of the following classes:

AIEBATCHOPERATION
AIECOMPONENTINFO
AIEDATASETINFO
AIEEXPORTASSEMBLY
AIEEXPORTNODE
AIEEXPORTOPERATION
AIEIMPORTOPERATION

a. At the acg prompt, enter the following command:

select papplic_name from ppom_class where upper(pname)
= ’CLASS-NAME’;
Replace CLASS-NAME with the current class name from the list. Make
sure you type the class name in all upper case letters as shown in the list.
If the value returned is INFOMANAGEV200, proceed to the next class in
the list. Otherwise, proceed to step b.
b. At the acg prompt, enter the following command:

update ppom_class set papplic_name = ’INFOMANAGEV200’ where
upper(pname)= ’CLASS-NAME’;
c. At the acg prompt, enter the following command:

select papplic_name from ppom_class where upper(pname)
= ’CLASS-NAME’;
The system displays the following:

PAPPLIC_NAME
---------------------------------
INFOMANAGEV200
d. If the system displays the correct output, enter the following command
at the acg prompt:
commit;
4. After you complete these steps for all classes in the list, enter the following
command:
exit
• Naming rule error occurs after upgrading a Teamcenter Engineering

9.1.3 database containing GM Overlay
If you upgrade the Teamcenter Engineering 9.1.3 GM Overlay database and a
site item ID prefix is different than one in the GM Overlay template (GMO), an
error occurs when the custom-generated template is loaded in the Business
Modeler IDE.
1. Before upgrading, log on to the database and note your item ID prefix and
ID counter.
2. Perform the GM Overlay upgrade.
3. Run the bmide_postupgradetotc utility to generate the custom template.
4. Run the gmo_change_item_id_naming_rule utility to ensure the item ID

prefix is retained after the upgrade:
gmo_change_item_id_naming_rule —u=infodba
—p=password —g=dba —option=change_naming_rule
—prefix=ID—prefix —init_value=ID—counter —max_value=99999

Administration release notes
The following release notes pertain to the system administration of Teamcenter and
the use of the administration applications.
General
The following general release notes pertain to the administration of Teamcenter.

• ldapsync utility crashes when the LDAP_member_list_attr preference
points to parent node
If you set the LDAP_member_list_attr preference to point to a node on the tree
that contains a direct parent of the node being processed, it causes an infinite
loop that crashes the ldapsync utility. For example, if a parent node has one
child node and that child node uses the LDAP_member_list_attr preference to
point back to the parent, it causes an infinite loop.
Ensure the LDAP_member_list_attr preference does not point to a node that
causes an infinite loop.
• Protecting data synchronized from an external LDAP directory

When a user construct object (user, group, role, person, or group membership) is
synchronized from LDAP to Teamcenter (externally managed), the synchronized
attributes of that object should be updated only in the LDAP external
directory, not in Teamcenter. Therefore, the Organization application makes
all synchronized attributes read-only for externally managed user constructs.
For internally managed user construct objects (created in Teamcenter), these
attributes remain updateable. The Organization application symbols are
different for internally managed user constructs than for externally managed
user constructs to help clarify this behavior difference. However, other
administrative tools for updating user, person, group, role, and group member
information, such as the make_user command line utility and custom utilities
that call the ITK APIs, do not have any controls prohibiting externally managed
user constructs from being updated. User constructs synchronized from LDAP
are updated each time the ldapsync utility is run and attribute changes made
by other utilities are overwritten by the ldapsync utility if those attributes are
mapped for synchronization.
Teamcenter administrators are responsible for ensuring synchronized data for
externally managed user construct objects does not get overwritten by other
utilities. If it does get overwritten, the changes are lost the next time the
ldapsync utility is run to update the synchronized data.

• Reversing accidental externalization of internally managed user

constructs
When a user construct object (user, group, role, person, or group membership)
exists in both LDAP and in Teamcenter, the default ldapsync utility
synchronization behavior is to set the datasource attribute on that user
construct in Teamcenter to externally manage and synchronize that object with
Teamcenter. This is particularly useful for updating user and person Teamcenter
objects that were synchronized from LDAP in previous Teamcenter versions to
set the new datasource attribute correctly. However, some customers may not
want internally managed user construct objects to be converted to externally
managed. Because externalization of these objects is the default behavior, you
must provide a way to undo that change if it is done accidentally.
You can change the default behavior for each user construct type by removing the
externalize sync flag in the preferences file. See the Preferences and Environment
Variables Reference for more details on the externalize synchronization flag
in the following preferences:
– LDAP_sync_group_flags
– LDAP_sync_member_flags
– LDAP_sync_role_flags
– LDAP_sync_user_flags
There is no opposite unsynchronize feature to change user construct objects from

externally managed to internally managed. However, the make_user utility
is updated with a special option to set the datasource attribute on specified
user construct objects. Use this feature to reset user construct objects that
were mistakenly externalized during a synchronization process. This option is
intentionally left undocumented in the make_user utility because it should not
be used for any reason except to correct a synchronization error.
The make_user command line option, –datasource=value, sets the specified
data source value (0=Internal, 1=External, 2 =Remote) on the specified user,
person, group, role, and group membership objects. By setting the datasource
attribute to 0 on a user, person, group, role, or group membership object, the
object is returned to internally managed.
The make_user utility also allows attributes to be specified in an input file for
batch processing, and datasource is supported as an attribute for updating
user, person, group, role, and group membership objects. For more information
about the make_user input file for batch processing, see the make_user
documentation in the Utilities Reference manual.

• Slow startup or connection timeout with Apache Tomcat 5

When starting Apache Tomcat 5.0 or Tomcat 5.5, slow startup and high CPU
usage may occur. The following exception from Tomcat may also appear:
ERROR - 2005/10/25-09:16:34,185 UTC { }
Bootstrap com.teamcenter.mld.jmx.ConfigurationListener
java.net.ConnectException: Connection timed out: connect

This error occurs because the default Java JVM garbage collection and heap
memory settings (–Xms and –Xmx) are often too small. Increase the Java
memory heap and garbage collection settings of Tomcat 5 to resolve this issue.
Organization
The following release notes pertain to the Organization application.

• Redundant events logged when creating a person
When you create a person, redundant modify events are logged in the audit table
in addition to the create event when Audit Manager is turned on.
• Default volume not assigned during creation of subgroups

(First published Engineering 2005 SR1 MP1)
While creating a subgroup in a group, the default volume is not assigned.
If the TC_allow_inherited_group_volume_access preference is not set to 1,
manually set the volume for the subgroup after creating the subgroup.

Teamcenter File Services and FMS administration
The following release notes pertain to the administration of Teamcenter File

Services and FMS.
Note
For release note information about using FMS with IBM AIX, see FCC is
not always able to resolve host names.
• Internet Explorer unable to download or open certain ZIP files

If you download or open a Teamcenter ZIP file using Internet Explorer, an error
may be displayed that says the file is corrupt or not a valid archive.
Either use a different browser, such as Mozilla, or disable file transfer
compression for ZIP files.
To disable file transfer compression for ZIP files, add the
FSC_DoNotCompressExtensions property to the fscdefaults
element of the fmsmaster configuration files.
<fscdefaults>
<property name="FSC_DoNotCompressExtensions" value="bz,bz2,cab,deb,ear,
gif,gz,jar,jpeg,jpg,jt,lha,lzh,lzo,mp3,mp4,mpg,rar,rpm,sit,taz,tgz,
war,z,zip" overridable="true" />
</fscdefaults>
If the FSC_DoNotCompressExtensions property already exists, verify that jt

and zip are contained within the value.
Once you change the files, either reload the configuration files or stop and start
the FSC servers to use the new value.
For more information about this problem, see this link:
http://support.microsoft.com/kb/308090
Note
The Microsoft workaround has not been verified by Siemens PLM
Software; use the fmsmaster configuration files work around.
• IMF_import_file and IMF_fmsfile_import ITK functions

(First published Engineering 2005 SR1 MP1)
The IMF_import_file and IMF_fmsfile_import ITK APIs do not validate
whether the file is a text file or a binary file validation.
When using these APIs, FMS does not attempt to validate the type of file against
the type specified on the function call. The caller must ensure that the file for
transfer is of the specified type.

• FMS configuration
The following error message appears when the values specified for the
Transient_Volume_RootDir preference have identical values:
Duplicate transientvolume configuration elements were found for attribute id
with value attribute_value

The Transient_Volume_RootDir preference allows the configuration of
transient volume locations for multiple platforms. Typically, one value
represents the location of a transient volume on a UNIX system and the other a
transient volume on a Windows system. The distinction is made based on the
path name separator (/ for UNIX, \ for Windows).
If you use only one platform, you can delete the other value. Multiple values
can be specified but are not required.
• FCC is not always able to resolve host names

When the file server cache (FSC) is hosted on an IBM AIX system, the FSC
process is not able to resolve the host name for the local IBM AIX host resulting
in an file client cache (FCC) failure.
The failure appears as a Java exception in the FCC log file:
java.net.UnknownHostException: (hostname)

Specify host names in the FMS XML configuration files as IP addresses using
the following steps:
1. In the fmsmaster.xml file on the master FSC server:
– Change all network domain names of all IBM AIX-hosted FSC servers to
IP addresses. Only IBM AIX-hosted FSC servers require this notation.
For example, change
<fsc id="myfsc" address="myAIXserver.mydomain.com:4444”>
to:
<fsc id="myfsc" address="250.142.16.3:4444”>
and change:
<fscimport fscid="myotherAIXfsc"
fscaddress="myotherserver.anotherdomain.net:6666”>
to:
<fscimport fscid="myotherAIXfsc" fscaddress="125.71.8.1:6666”>

Substitute the correct IP address values as appropriate.

FSCs that run on an IBM AIX platform include:
◊ The address field of all IBM AIX-hosted FSC declarations.
◊ The host field of all additional IBM AIX-hosted FSC connection

declarations.
◊ The fscaddress field of all IBM AIX-hosted fscimport declarations.
◊ All address fields of all IBM AIX-hosted routing declarations.
These changes are picked up by the clientmap section of the FMS

master configuration file using the FSC ID.
2. In the fcc.xml file (or equivalent) for each user on each client workstation,
change all IBM AIX-hosted FSC server network domain names to IP
addresses.
Note
Only IBM AIX-hosted parent FSC servers require this notation.
For example, change:

<parentfsc address="myAIXserver.mydomain.com:4444" priority="0"/>
to:
<parentfsc address="250.142.16.3:4444" priority="0"/>
Substitute the correct IP address values as appropriate. This includes the

address field of all parentfsc declarations.
3. If IBM AIX-hosted FSCs support HTTPS connections:

a. Issue each HTTPS-supporting IBM AIX-hosted FSC a certificate
containing its IP address (in place of its domain name).
b. Install the new certificate and/or remove the domain-name certificate.

This allows the clients to validate the FSC’s host name in decimal-dot
notation form.
c. Install this new certificate in the trusted certificate store of each

peer FSC and client, unless they are configured to accept self-signed
certificates.
4. After making these changes, follow the normal procedures for propagating
new FMS configuration changes to your site.

To maintain these changes as IBM AIX-hosted FSCs are added to the site, you
must do the following:
1. Configure the IBM AIX-hosted FSCs in FMS by IP address rather than

domain name.
2. For HTTPS, install certificates with IP address rather than domain name.
3. As clients with IBM AIX-hosted parent FSCs are added to the site, refer to
the parent FSC in the FCC configuration by IP address rather than domain
name.
4. Follow the normal procedures for propagating new fmsmaster.xml changes

to your site after making changes.
Teamcenter Integration for NX
The following release notes pertain to Teamcenter Integration for NX.

• NX 5 and NX 6 may not start on SUSE 10 Linux platforms
On SUSE 10 Linux platforms, NX 5 or NX 6 may fail to start when you try to
open it from Teamcenter. This occurs when the NX installation procedure writes
incorrect content into the /ugs/installed_programs.dat file.
Replace the following two lines at the start of your /ugs/installed_programs.dat
file:
[HKEY_LOCAL_MACHINE\Software\Unigraphics \c
Solutions\Installed Applications]
with the following single line:

[HKEY_LOCAL_MACHINE\Software\Unigraphics Solutions\Installed Applications]
• Connections under a harness sometimes move incorrectly

If you export a connection list from NX to Teamcenter with the Export to PDM
menu command, a connection under a harness could move out from under
the harness on subsequent exports to Teamcenter. This typically happens in
connection lists that have more than one harness.

• Download hyperlink is not available after exporting an NX assembly

If you export an NX assembly in the thin client using the Sun Java System
9.1 application server with Internet Explorer, the Export Status window is not
updated with the Download hyperlink when the operation is complete. Also, if
the export request is terminated, the dialog box is not updated.
Use an application server that does not run on Sun Java System 9.1.
• Download hyperlink is not available after canceling previous download

attempt
In the thin client, if you click the hyperlink to download an NX assembly in
the Export Status window and then click the Cancel button, the Download
hyperlink is no longer available.
Always click the Save button after clicking the Download hyperlink.
• Download hyperlink is not available for the first subassembly if a

second subassembly is exported too soon
If you export a second NX subassembly before the first subassembly export has
completed in the same Structure Manager window, the Export Status window is
not updated with the Download hyperlink for the first subassembly.
Either wait for the first subassembly export to finish before attempting to export
the second subassembly or export the assembly that contains both subassemblies.
• Harness structure corrupted after wire is deleted

The harness structure from the previous revision is corrupted after you delete
the wire from the new revision.
Release the electrical harness when you release the item containing the electrical
harness.

• Harness structure corrupted after adding a harness and connection

A new harness structure is corrupted after you add a harness and connection
using the NX Export to PDM menu command.
The harness structure from the previous revision is corrupted after you delete
the wire from the new revision.
Use variants and options instead of multiple, duplicate harnesses within one
part file.
• Upgrading NX 5 to NX 5.0.2.2 fails on Microsoft Windows Vista

Microsoft Windows Vista is not a supported system configuration for running
batch scripts. Therefore, if you run the ugs_update.bat file to upgrade NX
5.0.0.25 to NX 5.0.2.2 on a Microsoft Windows Vista platform, it fails.
Turn off the Vista User Access Control (UAC) before you run the ugs_update.bat
file.
• NX does not launch from four-tier Teamcenter client on 64-bit Windows

XP
When you attempt to launch an assembly into NX from a four-tier Teamcenter
client on 64-bit Windows XP, NX does not start.
Run the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86)
installation file (vcredist_x86.exe). The vcredist_x86.exe file is located on the
Teamcenter installation source in the additional_applications folder, or also
can be downloaded from the following URL:
http://www.microsoft.com/downloads/details.aspx?
FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
As stated on the Microsoft Web site:
The Microsoft Visual C++ 2005 SP1 Redistributable Package (x86 )
installs runtime components of Visual C++ Libraries required to run
applications developed with Visual C++ on a computer
that does not have Visual C++ 2005 installed.
The runner.exe application in Teamcenter is this kind of executable. You need

to have administrator credentials to install the vcredist_x86.exe file.

• Opening a UGMASTER dataset type in NX 4.0.4.2 fails if using

NX_Interop_Type set to plmxml with NX 4.x
The UGMASTER dataset type does not open in an NX session if the Teamcenter
NX_Interop_Type option is set to plmxml. The NX 4 session opens, but the
part does not load. NX 4 is not equipped to work with this interoperability type.
The plmxml value can be used with version NX 5.
The NX_Interop_Type option is set to bkm in Teamcenter by default. When
using NX 4, do not change this value.
• Bookmark error occurs when creating a dataset in Teamcenter and

using Teamcenter Integration for NX 5
When creating a dataset in Teamcenter and using Teamcenter Integration for
NX 5, a bookmark error may occur if you select the Open On Create check box.
This bookmark error occurs when Teamcenter Integration for NX 5 attempts
to open the UGMASTER dataset. This error may prevent the new part from
being saved to the database.
Install the NX 5 templates. Siemens PLM Software recommends that all
customers who intend to use NX 5 install the templates, regardless of this
particular error.
• Item IDs can be created that are invalid in Teamcenter Integration

for NX
Teamcenter allows characters in the item ID that are not allowed in NX.
Do not create item IDs that contain the following characters:
– Any control character (less than 0x32)

– Double quote (“)
– Asterisk (*)
– Slash (/)
– Backslash (\)
– Colon (:)
– Less than (<)
– Greater than (>)
– Back tic (‘)
– Vertical bar (|)
– Delete character (0x7f)
– Tilde (~)

• NX clone import requires default volumes value from Teamcenter

While performing a Teamcenter Integration for NX import operation, the NX
Information dialog box may display the following message:
No or invalid default volume for User or Group in database.
The Teamcenter default behavior is for the user to inherit the default volume
value from the user’s assigned group. At times, the value from this implicit
assignment does not get passed to the Teamcenter Integration for NX import
operation. This message indicates the Teamcenter value did not pass properly to
the Teamcenter Integration for NX import function.
Manually set the default volume using the Default Volume button in the Groups
pane in the Organization application. This explicitly assigns the volume name
to the user. The value from the explicit assignment is provided to the clone
function and imports function correctly.
Security Services
The following release notes pertain to Security Services.

Note
For additional Security Services release notes, see the Security Services
Release Notes (SecurityServicesReleaseNotes.pdf file) in the sso
subdirectory of the additional_applications directory of the Teamcenter
2007 software distribution image. This document describes features
introduced with the latest version of Security Services. It also contains
general notes and descriptions of known defects.
• Customization of the default search string used in the WebSEAL logon

page FORM causes authentication to fail
After Teamcenter rich client, FMS client cache (FCC), or Teamcenter’s lifecycle
visualization client startup, any action that requires authorization initiates a
request to the IBM Tivoli WebSEAL server. WebSEAL sends an authentication
challenge response to the Teamcenter application, which attempts to detect
the WebSEAL form authentication event prior to initiating Security Services.
This detection process performs a search within the WebSEAL HTML response
to find a specific string. The default search string used in the WebSEAL logon
page FORM post HTML is:
<FORM action=/pkmslogin.form method=post>
The custom search string is:

<FORM method=post action=/pkmslogin.form>
If this string in the WebSEAL logon page HTML has been customized, the
authentication process between Security Services and WebSEAL fails.

– FMS client cache (FCC)

Provides a configuration property within the fcc.properties.template file
that can be used to redefine the search string.
Change the fcc.properties.template file name to fcc.properties, and then
edit the following section to uncomment the Detection Pattern property,
and redefine the pattern.
# Optional property for specifying the string pattern used for detecting
# a WebSEAL form authentication event. The string is searched for in the
# body of HTTP response message sourced by a WebSEAL revere proxy server.
com.teamcenter.fms.websealFormAuthDetectionPattern=<FORM method=post action=/pkmslogin.form?
– Teamcenter’s lifecycle visualization client

Provides an environment variable that can be used to redefine the search
string.
Set the following system or user environment variable prior to starting the
Lifecycle Visualization client:
TCVIS_FORMBASED_AUTH_CHALLENGE_KEY=<FORM method=post action=/pkmslogin.form>
– Teamcenter rich client

Provides a property that can be used to redefine the search string. Set the
following property in the site_specific.properties file prior to starting
the Teamcenter rich client:
webSealFormURL =<FORM method=post action=/pkmslogin.form>
– Teamcenter’s Integration for Microsoft Office

Not supported by WebSEAL proxy. If Integration for Office is included
in the installation with WebSEAL, the file attachments with the
dataset may fail during open or edit operations. To avoid this error,
ensure the useMSOfficeIntegration property is set to false in the
client_specific.properties file.
• Extra logon challenge in some WebLogic deployments

If you deploy the Login Service and Teamcenter Web client on the same WebLogic
server instance but on different ports (same host), you get an extra challenge
when you log on.
Deploy the two Web components on the same port or on different WebLogic
instances.

Utilities
The following release notes pertain to utilities.

• data_sync utility with –restart option fails on HTTP Multi-Site between
Windows and Solaris
If you have an HTTP-based Multi-Site environment and run the data_sync
utility with the –restart option on a Windows platform, it fails to invoke the
other site tcserver if it is on a Solaris platform.
Delete the existing checkpoint transaction and run the data_sync utility
without the –restart option.
• +asm_jt_file modifier added to –format=ajt option for bomwriter utility

In the bomwriter utility, you can add the +asm_jt_file modifier to the
–format=ajt option to output the associated JT file information for any
intermediate lines in the assembly. For example:
bomwriter —u=user —p=password
-output_file=full-path —format=ajt+native+asm_jt_file
—item=item-ID —rev=revision
For more information about the bomwriter utility, see the Utilities Reference.
• +delimiter modifier added to –format=psup option for bomwriter utility

In the bomwriter utility, you can add the +delimiter= modifier to the
–format=psup option to specify your own delimiter in output files. The default
delimiter is a comma (,). The following example sets the delimiter to a semicolon
(;):
bomwriter —u=user —p=password
-output_file=full-path —format=psup+delimiter=;
—item=item-ID —rev=revision
For more information about the bomwriter utility, see the Utilities Reference.

• smlutility utility with some options corrupts data model objects

managed by the Business Modeler IDE
The smlutility –install utility with the following suboptions corrupts data
model objects managed by the Business Modeler IDE:
– ICS
– ICS_BASE
– ICS_SYSD
– ICS_ICM
Do not use this utility with the suboptions to create or update the
Classification-specific parts of the Teamcenter data model. This is controlled by
the Business Modeler IDE. If you use the smlutility –install utility, you may
corrupt the data model and the data may become inaccurate.
The only option still allowed is ICS_UTIL. However, do not use this option
because the schema installed by this utility is not customizable.

Customization release notes

This section contains release notes pertaining to customizing Teamcenter.
Integration Toolkit (ITK)

The following release notes pertain to the Integration Toolkit (ITK).
• Header inclusion format
In Teamcenter 2007, the server code changes how header files (.h files) are
included. The header files previously located in the include directory are moved
into subdirectories. Therefore, you must add the subdirectory to your include
calls in your custom code. For example, if your include statement looks like this:
#include <genealogy.h>
It should now look like this:

#include <ecm/genealogy.h>
So your custom code can still compile while final migration takes place, the
header files have been duplicated in the main include directory. They only
contain an include statement of their counterparts in the subdirectories. The
duplicated header files in the main include directory are deprecated and will be
removed from a future version.
Siemens PLM Software provides a Perl script to help you convert your include
statements. The prerequisite for this tool is Perl 5.8.0 or later, and you must run
it on a Windows machine. You can use this tool either before or after using the
Teamcenter Namespace Deployment tool.
1. Access the GTAC server and download the

Teamcenter_2007_HeaderInclusionFormat tool into a dedicated
directory.
2. Load all source and header files you want to modify in a source code managed
(SCM) workspace.
3. Change the directory to the root of the workspace.
4. In the SCM workspace window, type:

perl full-path-to-script\Teamcenter_2007_HeaderInclusionFormat.pl
5. When prompted, type the command used by your SCM system to check out
files. You can type a non-SCM command if necessary.
When you are asked to confirm the command, type y.
6. When prompted, type the directory name where you want the log file
generated.
The tool decides which files to process and parses them. Once parsed, the
files to be modified are checked out using the command specified in step 5.
The updated files replace the existing files. The tool generates statistics to
help you track how the tool performed.

7. To validate everything is modified according to the new standard, copy the

include directory to a new _include directory. In the include directory,
delete all include files except error_bases.h, ugmath_datatypes.h,
and unidefs.h, leaving the subdirectories. Recompile your code in the
workspace. If there are any include-related compilation errors, check the
files for incomplete conversions.
• Call EINT_init_module function before other eIntegrator Admin ITK

functions
If you are using eIntegrator Admin in a batch program, you must call the
EINT_init_module function first before you call other eIntegrator Admin ITK
functions.
Service-oriented architecture
The following release notes pertain to the Teamcenter service-oriented architecture

(SOA).
• libcurl library renamed to libtccurl
Teamcenter contains a version of the libcurl library that may be different than
the version you already have.
The libcurl library in Teamcenter is named libtccurl. Use the libtccurl library
when using SOA to integrate with Teamcenter.

Teamcenter interfaces release notes
The following release notes pertain to using Teamcenter interfaces.
Rich client
The following release notes pertain to the use of the rich client.
• Embedded viewer displays red background instead of a Microsoft Office
document in the rich client
If you install the rich client on a virtual drive and try to visualize Microsoft
Office 2007 documents in the embedded viewer, you see a red background instead
of the document. This also occurs in the Web Browser application.
Install the rich client on a regular drive on the machine instead of a virtual drive.
• Saved changes in PowerPoint do not appear in the dataset

If you open a PowerPoint dataset in the Viewer pane and then open it in the
PowerPoint application by double-clicking the dataset while it is still open in
the Viewer pane, changes made and saved in the application are not saved to
the dataset.
Do any of the following:
– Use Teamcenter’s Integration for Microsoft Office.
– Make changes in the Viewer pane.
– Manually terminate the POWERPNT process.
• Teamcenter rich client modal dialogs do not function properly on most

UNIX X servers
On most UNIX/Linux systems, modal dialogs may be hidden behind the main
application window. Because the dialogs are modal, no keyboard or mouse
interaction is permitted with any other part of the user interface except for
the modal dialog box.
Manually find and bring the modal dialog box to the top. When finished with
modal dialog, close it to resume normal operation.

Thin client
The following release notes pertain to the use of the thin client.
• NX export request keeps processing after thin client Export Status
dialog box closes
If you close the thin client Export Status dialog box, the NX export request keeps
processing instead of deleting the request.
Do not delete a request in the thin client. Use the translator administration
console in the rich client.
• PLM XML import/export does not handle import/export of files

associated with a dataset
Thin client PLM XML import/export of datasets does not handle transfer of
associated files attached to a dataset, such as UG NX assemblies and part files.
When a dataset is imported/exported through the thin client PLM XML
import/export, its associated files cannot be imported/exported along with the
PLM XML file containing the dataset definitions.
Use Teamcenter rich client PLM XML import/export to import/export datasets
and their associated files.
• Name and description values not set through initial value on a property
rule
Prepopulation of the Name and Description boxes from the initial value
definition on a property rule is missing for the following dialog boxes: New Form,
New Dataset, and New Folder.
Currently, there is no work around for this problem. The problem will be fixed in
a maintenance patch.

Teamcenter integrations release notes
The following section pertains to integrations.
Teamcenter EDA
The following release notes pertain to Teamcenter EDA.

• Mentor Board Station 2005 is not supported on Solaris 10
If you start Mentor Board Station 2005 on a Solaris 10 workstation, it may
generate the following system error:
init_alt_dynld: Unable to find _elf_bndr in ls.so
Mentor Board Station 2005 continues to launch. However, if you then try to
use a Teamcenter EDA integration command, you may get a failure during the
Teamcenter logon.
Currently, Mentor Board Station 2005 is not supported on Solaris 10. The launch
error is known to Mentor Graphics, but there is no known solution for it. Mentor
Board Station 2006 and above is supported on Solaris 10. Teamcenter EDA now
supports both Mentor Board Station 2005 (BS2005) and Mentor Board Station
2006 (2006BSXE); however, only Mentor Board Station 2006 is supported for
Solaris 10.
The version of Mentor Board Station is determined at run time and the EDA
integration configures itself accordingly.
• Teamcenter EDA errors when using Mentor Graphics on UNIX

(First published EDA 2005 SR1)
Teamcenter EDA integrates ECAD design applications, such as Mentor Graphics
and Cadence, with Teamcenter. When using the Teamcenter EDA client with
Mentor Graphics on a UNIX platform, Teamcenter EDA actions fail. The launch
of the Design Manager may also fail.
During the installation of the Mentor Graphics support option within Teamcenter
EDA, files are installed that provide extensions to the Mentor Graphics Design
Manager product. Because of delivery limitations, these files do not contain the
correct operating system file permissions. This condition only occurs on UNIX
platforms (Sun Solaris and Hewlett-Packard HP-UX).
Because some of the files contain incorrect permissions, the user encounters
errors that report that Teamcenter EDA tasks cannot be called because of these
incorrect permissions.


You must manually edit the installation to allow these Mentor Graphics
extensions to be used. Perform the following procedures for each UNIX client
that contains the Teamcenter EDA client code for Mentor Graphics.
To update file permissions, enter the following in a command prompt:
– Sun Solaris systems:

cd $MGC_HOME/bin
chmod 755 mti_bom mti_dmgr mti_xbom
cd $TCEDAECAD_ROOT/Mentor_BoardStation/lib
chmod 755 libMTI*
– Hewlett-Packard HP-UX systems:

cd $MGC_HOME/bin
chmod 755 mti_bom mti_dmgr mti_xbom mti_ipc_server mti_run_ipc_server
chmod 755 libMTI*
– UNIX systems:
cd $MGC_HOME/bin
chmod 755 mti_bom mti_dmgr mti_xbom*
chmod 755 libMTI*
Teamcenter’s Client for Microsoft Office

The following release notes pertain to Teamcenter’s Client for Microsoft Office.
• Clicking the Save button in Office 2007 does not synchronize the
Summary and Custom properties to Teamcenter OfficeDocForm
If you click the Save button in Microsoft Office 2007, the Office properties, such
as Author and Title, are not synchronized with the Teamcenter OfficeDocForm
attached to the dataset as a named reference. The properties are synchronized if
you use Office 2003 or an earlier version.
In Office 2007, click the Save to Teamcenter button in the Custom Toolbars
section on the Add-Ins ribbon instead of the Office Save button.

Teamcenter’s Integration for Microsoft Office and Teamcenter’s Network Folders
The following release note pertains to Teamcenter’s Integration for Microsoft Office
and Teamcenter’s Network Folders.
• New revision does not attach the same datasets as the original revision
If you create a new revision, it does not contain datasets that have the attach
relation to the original item revision.
If a revision contains datasets with the attach relation, use the rich client or
thin client to revise the item.
Internationalization release notes
The following release note pertains to internationalization:

• Thin client (DHTML) displays non-Western European text incorrectly
with Apache 2 HTTP Server
(First published Engineering 8.1.1)
Apache 2 defaults to Western European encoding. As a result, Web DHTML
displays non-Western European text incorrectly when Apache 2.x is used as
the HTTP server.
This problem does not occur with Apache 1.3.20. As a work around, Siemens
PLM Software recommends that you comment out the encoding string in the
httpd.conf file (iso-8859-1).

Platform-specific release notes

This section contains release notes pertaining only to the following platforms:
UNIX platforms
Hewlett-Packard HP-UX
Sun Solaris
IBM AIX
Microsoft Windows
SUSE Linux
UNIX platforms
The following release notes pertain to UNIX platforms only.
• IDSM servers do not respond on UNIX or Linux platforms
Clients of the IDSM return error messages that state the idsm_version_check
function has failed due to a time-out. For example, the data_share utility may
return the following:
***ERROR: No site available for processing
ERROR STACK:
100202: The IDSM request to site M0417Ha on host hpis04 failed.
: RPC: 1832-008 Timed out
100107: Attempted function idsm_version_check

at site M0417Ha on host hpis04.
If this occurs, the IDSM syslog files contain an error message in this form:
TextServer::TextPool – error-message SharedMemory will not be used.
If you see both these error messages, apply the following workaround.
You can use one of the following methods:
– Follow the procedure in the Starting the pool manager on HP-UX 11i
generates errors release note to resolve the text server shared memory IDSM
error messages.
– In the $TC_BIN/run_tc_idsm script, set the

TC_NO_TEXTSRV_SHARED_MEMORY environment variable to TRUE.
This disables the shared memory functionality and reverts the system
behavior to in-process text storage, which impacts the IDSM servers.
• Properties dialog box may not allow editing

On UNIX platforms, if you open the Properties dialog box in the rich client, you
may not be able to change the text in normally editable boxes. This also may
occur in the Summary pane after opening the Properties dialog box.
– Close the Properties dialog box and open it again.

– Click another application or window and then click the Properties dialog box.
• Character set prerequisite for GM Overlay installation on UNIX

Installation or upgrade of the GM Overlay feature fails if the ISO8859-1
character set is not loaded.
Run the locale –a command in a shell. If the output does not include ISO8859-1,
you must add this character set before you install or use GM Overlay:
1. Set or export the LC_ALL environment variable by typing
LC_ALL=en_US.ISO8859-1 or the equivalent command for your platform.
2. Verify the setting using the echo command or equivalent. Make sure the
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.
4. If LANG is still set to C, manually export LANG to be the same value as

LC_ALL.
5. Launch Teamcenter Environment Manager (tem.sh) from the current shell.
Alternatively, your system administrator may modify the date file (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
2007, 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.

Hewlett-Packard HP-UX
The following release notes pertain to Hewlett-Packard HP-UX platforms only.

• Starting the pool manager on HP-UX 11i generates errors
If you start the pool manager with a large number of tcserver processes on
HP-UX 11.11, you may get the following error when UNIX system shared
memory segments and semaphores interprocess communication resources are
low:
open: Not enough space
(17739|1) init_acquire failed: Not enough space
ACE_Malloc_T<ACE_MEM_POOL_2, ACE_LOCK,
ACE_CB>::ACE_Malloc_T: Not enough space

To correct the resource issue:
1. Stop the pool manager and kill all running tcserver processes.
2. Free the shared memory segments and semaphores as described below.
3. Remove memory store backing files as described below.
4. Run the list_users utility on the command line.
5. Start the pool manager.
Text server uses shared memory segments and semaphores to control

interprocess communication between the Teamcenter server processes.
Type the ipcs –sb command in a shell to display a list of shared memory
segments and semaphores currently allocated to the system. This list includes
all the shared memory segments and semaphore sets allocated, their identifying
number, the owner, and the number of semaphores in each set.
Occasionally, unexpected termination of Teamcenter processes leaves shared
memory segments and semaphore resources locked. If Teamcenter is not
running, but the ipcs –sb command lists shared memory segments and
semaphores owned by the owner that started the pool manager, these resources
must be freed. If this is not done, shared memory segments and semaphore
resources may not be sufficient on the UNIX system to allow the text server
to use interprocess communication.

Freeing shared memory segments and semaphores

Freeing shared memory segments and semaphores is done by either using the
ipcrm command or by restarting the system. Normally, system administrators
do not want to restart the system only to free shared memory segments and
semaphore resources. Shared memory segments and semaphores can be freed by
performing the following procedure:
Warning
Do not attempt to free shared memory segments and semaphore resources
from Teamcenter if the text server process (tcserver) is running.
1. Log on as root.
2. Type the following command to display the list of shared memory segments
owned by Teamcenter:
ipcs —mb |grep user-id-used-to-start-pool-manager
3. Free the listed shared memory segments by typing:

ipcrm —m ID_1...—m ID_n
Replace ID_1 with the shared memory segment identifying number from
the list.
4. Type the following command to display a list of semaphores owned by

Teamcenter:
ipcs —sb |grep user-id-used-to-start-pool-manager
5. Free the listed semaphores by typing:

ipcrm —s ID_1...—s ID_n
Replace ID_1 with the semaphore identifying number from the list.
Remove memory store backing files

If you are using shared memory and have updated your XML text files, you must
refresh the shared memory cache by removing the memory store backing files.
1. Ensure the system is idle. No Teamcenter server processes can be running.
2. Remove the memory store backing files. The TC_SHARED_MEMORY_DIR

environment variable value specifies the directory where the store backing
files are stored. If you do not set this variable, its value is set by the
tc_profilevars script to be either the TEMP environment variable
(Windows) or the /tmp (UNIX) directory.
Note
On Windows, if the environment variable is not available, the TEMP
directory is used.

The shared memory files are created under the

V2007.1.0.last-build-date/database-site-ID/language directory located in
the temporary repository. The language directory is extracted from the
TC_LOCALIZATION_DIR environment variable. Server error messages
are saved in the emh_text.xml.mem file. Server strings are saved in
the tc_text.xml.mem file.
At the next process startup, the system finds the shared memory state is no
longer initialized, reads the XML text files, and populates the shared memory
cache, thus creating and populating the shared memory backing store file.
Note
You can disable shared memory functionality and revert
system behavior to in-process text storage by setting the
TC_NO_TEXTSRV_SHARED_MEMORY environment variable to
TRUE.
Text server errors involving UNIX shared memory segments and semaphores
often indicate insufficient interprocess communication resources on that UNIX
system. Shared memory segments and semaphores resources may need to be
freed before the text server can use interprocess communication.
In this case, the text server automatically reverts to using tcserver memory to
provide text services. At a time when interprocess communication resources are
available, the text server automatically uses interprocess communication again
for new tcserver processes.
• Cannot change values in Properties dialog box on AIX or HP-UX

two-tier client
If your two-tier client is on the AIX 5.3 or HP-UX 11.11 platform and you check
out a dataset using the Tools→Check-In/Out→Check-Out menu command, and
then view its properties, you cannot change anything in the dialog box, even
though the dialog box is not labeled as read-only.
Also, if you select the dataset, view its properties with the View→Properties
menu command, and then click the Check-Out and Edit button, you can change
the Name and Description boxes, but if you close and reopen the dialog box, you
cannot make changes.
If you are using the AIX platform, make your changes on the Summary pane. If
you are using the HP-UX platform, close the Properties dialog box and reopen it.

Sun Solaris
The following release notes pertain to the Sun Solaris platform only.
• Configure Sun Solaris to ensure unique Ethernet MAC addresses for
multiple interface cards
If multiple interface cards be connected to a common subnet and configured to
boot with nonunique MAC addresses, any multicast activity can severely disrupt
network communications to and from that machine.
Teamcenter 2007 has a JETI pool manager that can be configured to use
a multicast protocol for high performance management of its shared pool
configuration state.
Sun Solaris machines must have the EEPROM local-mac-address? set to true.
In particular, Sun Solaris machines with multiple interface cards installed must
be configured to boot with unique MAC addresses. To identify these, perform one
of the following procedures:
– Look for local-mac-address in the output of prtconf –pv.
For example, the following shows two devices with the same local MAC
address, and shows that the system is booted with local-mac-address?
set to false:
# prtconf -pv | grep local-mac-address
local-mac-address?: ’false’
local-mac-address: 0003bb7d.7c51
– As a root user, run ifconfig –a. As this user, the MAC address is shown
following the ether tag. (If run as a nonroot user, the inet address
information is still shown, which is useful information.)
The following is an example of cards that boot with nonunique MAC
addresses and are configured on the same subnet:
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 123.123.12.101 netmask ffffff00 broadcast 123.123.12.255
ether 0:3:bb:7d:7c:51


For the cards to boot with unique MAC addresses, the EEPROM
local-mac-address? must be set to true and the machine rebooted.
For example, as root user:
init 0
ok setenv local-mac-address? True
ok reset
After this reboot, the following shows the expected change in these commands,
showing unique MAC addresses:
– In the output of prtconf –pv:

# prtconf -pv | grep local-mac-address
local-mac-address?: ’true’
– (Alternative) As a root user, run ifconfig –a:

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
IBM AIX
The following release notes pertain to the IBM AIX platform only.
• Cannot change values in Properties dialog box on AIX or HP-UX
two-tier client
If your two-tier client is on the AIX 5.3 or HP-UX 11.11 platform and you check
out a dataset using the Tools→Check-In/Out→Check-Out menu command, then
view its properties, you cannot change anything in the dialog box, even though
the dialog box is not labeled as read-only.
Also, if you select the dataset, view its properties with the View→Properties
menu command, then click the Check-Out and Edit button, you can change the
Name and Description boxes, but if you close and reopen the dialog box, you
cannot make changes.
If you are using the AIX platform, make your changes on the Summary pane. If
you are using the HP-UX platform, close the Properties dialog box and reopen it.

• Appearance Editor dialog box on AIX 5.3 sometimes displays incorrectly

On the IBM AIX 5.3 platform, the first time you open the Appearance Editor
dialog box in Structure Manager or when a component is selected in the Viewer
tab, it may not initially display the Material, Preview, or Color sections.
There are three workarounds, listed in the order you should try them:
– Select a part in the Viewer tab, and then choose the Graphics→Edit
Color/Translucency menu command. The Material, Preview, and Colors
sections should appear. Once they appear, they always appear when you
open the dialog box.
– Select a part in the Viewer tab, and then open the Appearance Editor dialog
box with the 3D Appearance toolbar. The Material, Preview, and Color
sections should appear. If not, close the dialog box, select the part again,
and reopen the dialog box. You should only need to repeat this process two
or three times. Once the sections display, they always appear when you
open the dialog box.
– Exit Teamcenter and then remove the Visualization UNIX registry in your
user home directory. Note that you lose any preferences saved to the registry.
You should attempt this only if the previous workarounds do not work.
To remove the registry:
1. In a shell, type this command:

cd your-user-name/.eai
2. Type this command:

rm registry.def
3. Restart Teamcenter.
You should see the Material, Preview, and Color sections in the
Appearance Editor dialog box when it is opened and a part is selected.
Microsoft Windows
The following release notes pertain to Microsoft Windows platforms only.

• Chinese characters shown as blocks
Chinese characters are displayed as square blocks in the Teamcenter rich client
on Windows systems.


This may happen when a non-native language operating system version of
Windows is used and the Multilingual User Interface (MUI) pack is not installed
or if this is not enabled from the Languages tab in Regional and Language
Options in the Windows Control Panel. If you are using a non-native language
operating system, you must do the following to make sure the language font
is displayed properly:
1. Install the MUI pack for Windows. Once installed, you should see the
Languages used in menus and dialogs list in the Languages tab of
Regional and Language Options in the Control Panel.
2. In the Languages tab, set the required language for the menus and dialogs.
Note
In addition, you must also change the language on the Regional
Options and Advanced tabs.
• Unable to access files in TC_TMP_DIR on Windows 2003 Server

On some Windows 2003 Server configurations, users may not be able to access
log and other files contained in the TC_TMP_DIR directory on the server host.
To ensure that temporary files from different users remain separate, Windows
can assign each user their own TEMP directory. This can be seen when unique
temporary directories are created, such as C:\Temp\1 and C:\Temp\2, instead
of the shared C:\Temp. Each of the temporary directories is accessible only by
the owner of the directory and administrators. In this case, TC_TMP_DIR is
accessible only to the operating system user running the Teamcenter server and
the computer administrator.
You can stop the creation of the subdirectories by changing the Use temporary
folders per session setting to No in the Windows 2003 Terminal Services
Configuration. This sets the C:\Temp directory as the temporary directory
with read permissions for everyone.
• Critical messages displayed in WebLogic 9.1 console when running

WebDAV
Critical messages are displayed in the WebLogic 9.1 console when running
WebDAV.
To remove these messages, follow the instructions provided by BEA: Steps for
Smart Update:
http://e-docs.bea.com/common/docs91/smart_update/quickrefax.html
After applying the patch, add the
–Dweblogic.servlet.security.EnforceValidBasicAuthCredentials=false
parameter to the end of the call command in the startWebLogic.cmd file for
your domain. For additional technical support, contact BEA about CR266407.

• Data lost when editing Microsoft Excel datasets

When you edit a Microsoft Excel dataset and keep the Excel application running,
the dataset changes are not saved.
When editing a Microsoft Excel dataset, close the Excel application after each
edit to save the dataset. Otherwise, use Microsoft Office integration.
• Document management/network folders and Microsoft Office

Value and description pairs consistently appear regardless of the Options setting
when using Microsoft Office.
In Teamcenter rich client, you can edit an LOV preference to hide the description.
In Teamcenter’s Integration for Microsoft Office and Windows Explorer, the LOV
value/description pairs are always displayed regardless the preference setting.
SUSE Linux
The following release notes pertain only to SUSE Linux platforms.

• Appearance update manager does not start on Linux
The appr_update_manager batch file fails to start on Linux systems and
validation of the appearance_updater process fails because of a known
limitation in starting and returning status from another process.
This happens only at the initial validation stage of the appearance update
manager startup. To work around this, set the following configuration parameter
in the .appr_update_env file:
updater.validation = 0

Release notes for Teamcenter-related products

This chapter contains general notes and describes known problems for
Teamcenter-related products.
Teamcenter’s lifecycle visualization (Lifecycle Visualization) release notes

The following release notes pertain to the use of Teamcenter’s lifecycle visualization
through Teamcenter.
• Cannot view NX assembly, UGALTREP, or UGPART files using Lifecycle
Visualization
If you add the UGMASTER while creating a UGALTREP or UGPART, the
UGALTREP or UGPART is handled as an assembly .prt file. Assembly .prt
files cannot be directly visualized using Lifecycle Visualization.
Tessellate the .prt files into JT assemblies. JT assemblies can be viewed without
problems.
Administration and usage release notes

The following is a list of release notes pertaining to the administration and use of
Lifecycle Visualization.
• .vvi file not found on Windows Vista machines if Lifecycle Visualization
is set to run as administrator
If you double-click a .vvi file in Windows Explorer on a Vista machine or send
it from Structure Manager within Teamcenter, you may see the following error
message:
Windows cannot find "filename.vvi". Make sure you typed the
name correctly, and then try again.

Ensure the Lifecycle Visualization executable VisView.exe is not set to run
as an administrator by right-clicking either the VisView.exe file in Windows
Explorer or the Lifecycle Visualization shortcut and choosing Properties. In
Privilege Level, ensure the Run as Administrator check box is cleared.
• .vvx file type not recognized as a file associated with Lifecycle

Visualization
Certain file types, including .vvx files, do not appear to be associated with
Lifecycle Visualization after running the application.
Run Lifecycle Visualization as an administrator at least once to register the
entire set of file types. To run Lifecycle Visualization as an administrator,
right-click the Lifecycle Visualization shortcut and choose Run as administrator.
After the main application window displays, the application should close.

• ME-10 (.mi) vector file extension support discontinued

Siemens PLM Software no longer supports ME-10 (.mi) vector file extensions
because of file format changes. This file extension includes HP CoCreate ME
10/ME 30 files.
• iSeries interoperation not supported

If you purchased a Named User Visualization license, you have access to iSeries
for the thin client, but not the rich client. The license does not include support
of interoperability between iSeries and NX using PLM XML interoperability
functionality.
• Some product views created in Teamcenter 2005 SR1 do not retrieve

after upgrade to Teamcenter 2007
Product views created in Teamcenter 2005 SR1 that were captured after turning
on the entire assembly at the root node do not appear when they are launched
after upgrading to Teamcenter 2007. Product views captured after the visibility
state was selected at the part level, however, do appear.
Make the entire model visible after loading the product view.
• Cannot launch Lifecycle Visualization with autologin enabled

If enableAutologin=true and you attempt to launch JT data to Lifecycle
Visualization, the launch fails with the following error message:
The current user credentials are not valid.

You cannot launch Lifecycle Visualization when enableAutologin=true.
• Moving markup entities in Lifecycle Visualization creates temporary

graphics artifacts on Windows Vista
If you click and drag markup entities in Lifecycle Visualization, a gray shadow
follows the trail of the mouse and disappears when you release the left mouse
button.
Change the theme in Vista from Windows Vista to Windows Classic.
• 2D measurements do not persist

When Lifecycle Visualization is first installed, 2D measurements do not
persist and can be displayed only one at a time. However, you can save these
measurements in a markup layer.


To enable persistent measurements as in earlier Lifecycle Visualization versions,
either use the Persist Measurements button on the 2D measurements toolbar or
open the Preferences dialog box on the 2D measurements toolbar and ensure
that Persist Measurements is selected.
• Cannot automatically view NX PRT files in the 3D viewer

The capability to directly view NX files in PRT format is unstable. Because of
this instability, this feature is not automatically enabled.
Note
The View NX .prt file as 2D preference is valid only when this feature
is enabled.

To enable this feature, follow the instructions in the Customize the
rich client properties files topic of the Rich Client Customization
Programmer’s Guide to make the following changes to the
com/teamcenter/rac/common/tcviewer/tcviewer.properties
file:
1. Find the following line and modify it to add UGPART to the list:
DatasetViewer.VIEWSEARCHORDER=JTPART,UGPART,Image,Markup,Sheet,JPEG,
Graphics-Interface,Shaded-Image,Common-Graphics-Meta,Direct-Model-Data
2. To view .prt files using Lifecycle Visualization, uncomment the following

three lines:
#UGMASTER.VIEWPANEL=com.teamcenter.rac.common.tcviewer.DirectModelViewer
#UGPART.VIEWPANEL=com.teamcenter.rac.common.tcviewer.DirectModelViewer
#UGALTREP.VIEWPANEL=com.teamcenter.rac.common.tcviewer.DirectModelViewer
• Translation of UGMASTER datasets using ugtopv utility recommended

The ugxxtojt translator does not create bookmark and assembly JT files. For
this reason, Siemens PLM Software strongly recommends that you use the
ugtopv utility to translate UGMASTER datasets into JT parts.
Users generally view assemblies in Structure Manager (Structure Manager). If
you must use My Teamcenter to view assemblies, execute the ugtopv command
with the generate_assembly_jt option. Otherwise, you can view component
parts only.
Note
Do not use the MIMIC option during translation.
Platform-specific
This section contains Lifecycle Visualization release notes pertaining to specific
platforms.

• Embedded Visualization installation and uninstallation fail on Windows

Vista with an IO exception
The Embedded Visualization installation and uninstallation fail with an IO
exception if the Teamcenter Environment Manager (TEM) installer (tem.bat) is
not launched with the Run As Administrator menu command from the shortcut
menu when the Vista User Access Control (UAC) is enabled.
Either choose the Run As Administrator menu command or disable UAC.
• Rich client user interface occasionally not repainted on Microsoft

Windows 2000/XP Professional
When using the rich client, users may see random gray patches where the user
interface is not repainted. This results from known problems in the following
graphics cards used with Microsoft Windows 2000 and XP Professional platforms:
NVidia Quadro 2 Pro Graphics
NVidia Quadro 4 500 GoGL
ELSA Synergy

Add the following string in the portal.bat file in the rich client root directory:
-Dsun.java2d.noddraw=true
Enter this string exactly as shown immediately after the Xbootclasspath

definition as follows:
set JAVA_COMMAND="%JRE_HOME%\bin\java" -Xbootclasspath:%X_BOOTCLASSPATH%
-Dsun.java2d.noddraw=true
Teamcenter’s reporting and analytics release notes

The following release notes pertain to Teamcenter’s reporting and analytics
(Reporting and Analytics):
• Running saved query that has default criteria does not work
Running a saved query that has default criteria does not work correctly.
Use the default criteria as filters instead.
• != and IS NULL operators do not work when running saved queries

for a Teamcenter 2007 connection
The != and IS NULL operators do not work when running saved queries for a
Teamcenter 2007 connection. They do not work in ad-hoc flow from BuildNPlay
because saved queries work only for the = operator.


The administrator should select only the = operator when saving the report
definition build on saved queries.
• All operators appear in the interface for both saved and database
queries
All operators appear in the interface for both saved queries and database
queries, even though only the = operator works for saved queries.
The administrator should select only the = operator when saving the report
definition build on saved queries.
• Error does not appear after submitting incorrect data for a filter
After submitting incorrect data for a filter, the following error does not appear:
Value for mandatory filters for the selected dimension(s) are not set.

Click the Results tab to see the error.
• No field name appears in error message when creating a connection

in mapper
No field name appears in error message when creating a connection in the
mapper.
After you click the error message, the mapper highlights the field with the error.
Managing Teamcenter’s mechatronics process management data
This section contains release notes pertaining to managing Teamcenter’s

mechatronics process management (Mechatronics Process Management) data.
• SCM version object fails to display the SCM configuration rule at the
replica site
You cannot view the SCM configuration rule at the replica site because the
Browse button is unavailable.
Open the Properties dialog box to see the SCM configuration rule. Scroll bars
are displayed when the SCM configuration rule text exceeds the text area space.

• Editing a GDE element fails at a replica site

If you have a Multi-Site environment and you perform any editing operation on a
GDE element under a checked out structure at a replica site, it fails.
• Hierarchical GDE structure at remote site cannot be remotely checked

out
When a hierarchical GDE structure is replicated at a remote site using multisite
functionality, it cannot be remotely checked out and modified at the replica site.
Transfer the ownership of the structure to the remote site before modifying it.
• Mechatronics Process Management sample ITK program/utility issue

If you run the mechatronics_system_test program (packaged with sample
files) to create Mechatronics Process Management objects in the database and
then try to delete the data using Delete option, the program may fail.
Delete the data using the rich client.

Third-party release notes for Teamcenter 2007
This section contains release notes pertaining to components supplied by third

parties.
Firefox Web browser
The following release note pertains to the Firefox Web browser.

• Moving browser scroll bar whites-out graphics
If you use the Firefox 2.0 Web browser on a Microsoft Windows Vista 64-bit
platform for the thin client, moving the browser scroll bar makes the graphics in
the viewer disappear.
Use Internet Explorer instead of Firefox.
• Back button works incorrectly with Teamcenter help pages

If you click the Back button in the when navigating the Teamcenter help system,
Firefox returns you to the main collection page instead of the previously viewed
page.
Microsoft
The following release note pertains to Microsoft.

• Microsoft SQL Server database migration utility cannot connect to
the Oracle database
The Microsoft SQL Server database migration utility, which migrates an
Oracle-based Teamcenter database to SQL Server, cannot connect to the Oracle
SID and you receive an error.
Currently, there is no work around for this problem and it will not be fixed.
Use the Microsoft SQL Server Migration Assistant (SSMA) utility instead. To
download the utility, go to either of the following Web sites:
http://www.microsoft.com/sql/solutions/migration/default.mspx
http://www.microsoft.com/sql/solutions/migration/oracle/default.mspx

Mozilla Web browser
The following release note pertains to the Mozilla Web browser.
• Teamcenter functionality not supported

The following Teamcenter functionality is not supported by the Mozilla Web
browser:
– Using the Adobe Scalable Vector Graphics (SVG) Viewer:
◊ In My Teamcenter, click View→Process to view the process in the SVG

viewer.
◊ In the Structure Manager application, select a supersedure and click

View→Supercedure to display genealogy of the part.
– Using ActiveX objects:
◊ In the My Teamcenter and Structure Manager applications,

Actions→Generate Report generates HTML and Excel reports using
the Microsoft XML parser.
◊ Click Edit link next to a dataset object to edit data sets using Microsoft
Office applications (Microsoft Office integration).
– Tree expansion state and search results are not retained in the browser
when the Back button is used. This state preservation is an enhancement in
Teamcenter that applies only to the Internet Explorer browser.
Oracle
The following release notes pertain to Oracle.
• Oracle 10g installation requires symbolic links

Before you install Oracle 10.1.0.2 on 64-bit Hewlett-Packard HP-UX 11i (11.11),
you must create the following symbolic links:
# 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

• Power saving option of network card on Windows laptop causes error

(First published Engineering 8.1.1)
If you install Oracle and the rich client server on a Windows laptop, and the
network card has a power saving option enabled, this configuration can cause
the rich client server to fail intermittently. The syslog file has an error message
similar to the following:
*** EIM_check_error: code -12571
*** NOTE:: in line 2612 of eim_trans_util.c
+++ (EIM_trans_util) ORA-12571: TNS:packet writer failure

To resolve this problem, you must disable the network card power saving option.

Index
Numerics/Symbols Attribute encryption in Resource

Manager . . . . . . . . . . . . . . . . . . . . . . 2-46
2D measurements . . . . . . . . . . . . . . . . 4-63 Attributes, custom . . . . . . . . . . . . . . . . 3-31
2D snapshots . . . . . . . . . . . . . . . . . . . 2-44 Authentication error . . . . . . . . . . . . . . 3-18
3D snapshot improvements . . . . . . . . . 2-51 auto-assign handler . . . . . . . . . . . . . . . 2-33
auto-assign-rest handler . . . . . . . . . . . 2-33
A Autogenerating code . . . . . . . . . . . . . . . 2-9
Automotive Edition upgrade . . . . . . . . 4-29
Access Manager . . . . . . . . . . . . . . . . . . 3-8
Access Manager Guide . . . . . . . . . . . . . 3-40
Action handlers B
CONTMGMT-notify . . . . . . . . . . . . . 3-91 Backup, hot . . . . . . . . . . . . . . . . . . . . 2-16
notify . . . . . . . . . . . . . . . . . . . . . . . 3-85 Baselines . . . . . . . . . . . . . . . . . . . . . . 2-66
Ad hoc Classification search . . . . . . . . . 3-73 Baselines for requirements
Add Status task . . . . . . . . . . . . . . . . . 3-84 management . . . . . . . . . . . . . . . . . . . 2-39
adhoc-signoffs handler . . . . . . . . . . . . . 2-33 Bill rates in Schedule Manager . . . . . . . 3-26
Administration release notes . . . . . . . 3-29, BMIDE client . . . . . . . . . . . . . . . . . . . 3-36
3-31, 4-31 bmide_postupgradetotc utility . . . . . . . 4-30
Aerospace and Defense Boilerplate code . . . . . . . . . . . . . . . . . . 2-9
Owning organization . . . . . . . . . . . . 2-69 BOM line columns . . . . . . . . . . . . . . . . 4-20
Parts list management . . . . . . . . . . . 2-68 bomwriter utility . . . . . . . . . . . . . . . . . 4-43
Program-level security . . . . . . . . . . . 2-70 Bookmarks
Properties on relation . . . . . . . . . . . . 2-70 Error . . . . . . . . . . . . . . . . . . . . . . . 4-40
Revision naming rules . . . . . . . 2-12, 2-69 Launch . . . . . . . . . . . . . . . . . . . . . . 1-22
Sample program . . . . . . . . . . . . . . . 2-69 Build server code . . . . . . . . . . . . . . . . 3-32
AIE class names, fixing . . . . . . . . . . . . 4-29 Business Modeler IDE . . . . . . . . . 3-36, 4-29
AIWS, deprecating . . . . . . . . . . . . . . . . 1-7 Alternate IDs . . . . . . . . . . . . . . . . . . 2-8
AIX Autogenerating code . . . . . . . . . . . . . . 2-9
64-bit . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Boilerplate code . . . . . . . . . . . . . . . . . 2-9
Appearance Editor dialog box . . . . . . 4-59 Build server code . . . . . . . . . . . . . . . 3-32
Properties dialog box . . . . . . . . 4-56, 4-58 Business object constants . . . . . . . . . 1-19
Release notes . . . . . . . . . . . . . . . . . . 4-58 Business Objects view . . . . . . . . . . . 3-40
Structure Manager . . . . . . . . . . . . . . 4-59 Business rules inheritance . . . . . . . . 2-10
Alias business objects . . . . . . . . . . . . . . 3-1 C++ support . . . . . . . . . . . . . . . . . . . 2-9
Alternate IDs Conditions . . . . . . . . . . . . . . . . . . . . 2-11
Enhancements . . . . . . . . . . . . . . . . . . 2-8 Deep copy enhancements . . . . . . . . . 2-11
NX Integration . . . . . . . . . . . . . . . . 2-63 Deep copy rules . . . . . . . . . . . . . . . . 3-31
Apache Web servers . . . . . . . . . . . . . . 4-51 Enabled property constant . . . . . . . . 3-33
Appearance Editor dialog box . . . . . . . . 4-59 Enhanced naming rules . . . . . . 2-12, 2-69
Appearance update manager . . . . . . . . 4-61 Item revision definition configuration
Application Interface Web Service, (IRDC) . . . . . . . . . . . . . . . . . . . . . 2-8
deprecating . . . . . . . . . . . . . . . . . . . . . 1-7 Property rules . . . . . . . . . . . . . . . . . 1-23
Application server support . . . . . . . . . . . 2-7 Required and visible properties . . . . . 2-11
As-Built Manager . . . . . . . . . . . . . . . . . 3-9 Revision naming rules . . . . . . . 2-12, 2-69
Assigned occurrence . . . . . . . . . . . . . . 4-20 Services . . . . . . . . . . . . . . . . . . . . . 2-10
PLM00001 C Teamcenter 8 Release Bulletin Index-1

Index
Business Modeler IDE client . . . . . . . . 3-36 Connection pooling, Global Services . . . 2-42
Business Modeler IDE Guide Connections . . . . . . . . . . . . . . . . . . . . 4-37
Convert secondary business objects to Consumer Packaged Goods . . . . . . . . . 2-71
primary . . . . . . . . . . . . . . . . . . . 3-42 Content Management
Documentation release notes . . . . . . . 3-40 S1000D . . . . . . . . . . . . . . . . . . . . . . 3-17
Preferences . . . . . . . . . . . . . . . . . . . 3-40 Tool tips . . . . . . . . . . . . . . . . . . . . . 3-17
Relation business objects . . . . . . . . . 3-41 User interface . . . . . . . . . . . . . . . . . 3-17
Relation properties . . . . . . . . . . . . . . 3-41 Continue on error not supported in Data
User exits . . . . . . . . . . . . . . . . . . . . 3-41 Exchange . . . . . . . . . . . . . . . . . . . . . 4-23
Business Objects view preference . . . . . 3-40 CONTMGMT-notify handler . . . . . . . . 3-91
Business rules inheritance . . . . . . . . . . 2-10 Convert secondary business objects to
business_objects.xml error . . . . . . . . . . 4-29 primary . . . . . . . . . . . . . . . . . . . . . . 3-42
Convert, Lifecycle Visualization 64-
C bit . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
CopyAsReference deep copy rule . . . . . . 3-28
C++ API Reference . . . . . . . . . . . . . . . 3-43 CR-assign-team-selector handler . . . . . 2-33
C++ support . . . . . . . . . . . . . . . . . . . . . 2-9 CR-fill-in-reviewers handler . . . . . . . . . 2-33
Cacheless search DesignContext . . . . . . 2-60 CR-notify handler . . . . . . . . . . . . . . . . 2-33
CAD BOM Alignment . . . . . . . . . . . . . . 3-8 Create reports, saved queries . . . . . . . . 2-38
CAE items . . . . . . . . . . . . . . . . . . . . . 3-31 Creating
CAE Manager . . . . . . . . . . . . . . . . . . . 3-12 Quick-release process template . . . . . 3-84
CAE Manager — Inspector . . . . . . . . . . 2-57 Request objects . . . . . . . . . . . . . . . . 3-81
Calendars in Schedule Manager . . . . . . 3-24 Custom types . . . . . . . . . . . . . . . . . . . . 4-9
CAM support . . . . . . . . . . . . . . . . . . . 2-64 Customization
Cascading LOVs in Requirements Attributes . . . . . . . . . . . . . . . . . . . . 3-31
Manager . . . . . . . . . . . . . . . . . . . . . . 3-22 Release notes . . . . . . . . . . . . . . . . . . 4-45
Cautionary statements . . . . . . . . . . . . 3-40
Certification database . . . . . . . . . . . . . . 1-4 D
Change management service . . . . . . . . 2-66
Change TcClass is not supported Data Exchange . . . . . . . . . . . . . . . . . . 4-26
error . . . . . . . . . . . . . . . . . . . . . . . . . 4-29 Briefcase transfers . . . . . . . . . . . . . . 4-23
Checked-out objects, find on exit . . . . . . 2-44 Continue on error feature not
Checkout Explorer dialog box . . . . . . . . . 3-8 supported . . . . . . . . . . . . . . . . . . 4-23
Chinese characters in Windows . . . . . . 4-59 Dataset, transferring . . . . . . . . . . . . 4-21
Classification Local actions on replicas . . . . . . . . . . 4-23
Attribute search . . . . . . . . . . . . . . . . 3-73 Monitoring interface . . . . . . . . . . . . . 4-21
Import and export failure . . . . . . . . . 3-10 Object Directory Services . . . . . . . . . 4-22
NXGraphicsBuilder . . . . . . . . . . . . . 4-18 Ownership not updated in ODS . . . . . 4-22
Quick search . . . . . . . . . . . . . . . . . . 4-18 Release notes . . . . . . . . . . . . . . . . . . 4-21
Release notes . . . . . . . . . . . . . . . . . . 4-18 Data Exchange Web application
UGGraphicsBuilder . . . . . . . . . . . . . 4-18 solution . . . . . . . . . . . . . . . . . . . . . . 2-42
Classification Administration . . . . . . . . . 3-8 Data Integration Services Adapter (DIS
Classification, multiunit support . . . . . 2-37 Adapter) . . . . . . . . . . . . . . . . . . . . . . 1-20
Clearance database integration . . . . . . 2-59 Data synchronization . . . . . . . . . . . . . 4-31
Client for Office . . . . . . . . . . . . . . . . . 3-16 data_share utility . . . . . . . . . . . . . . . . 3-29
Query error . . . . . . . . . . . . . . . . . . . 3-16 data_sync utility . . . . . . . . . . . . . 3-29, 4-43
Client support for Macintosh . . . . . . . . . 2-6 Database
Cloning Query . . . . . . . . . . . . . . . . . . . . . . . 4-66
Incremental change . . . . . . . . . . . . . 2-45 Upgrades . . . . . . . . . . . . . . . . . . . . 4-12
Structure . . . . . . . . . . . . . . . . . . . . 2-43 Datasets
Code page 932 . . . . . . . . . . . . . . . . . . . 3-36 Attaching . . . . . . . . . . . . . . . . . . . . 4-51
Component library management . . . . . 2-73 Transferring . . . . . . . . . . . . . . . . . . 4-21
Condition task . . . . . . . . . . . . . . . . . . 2-35 Debugging tools, Rich client . . . . . . . . . 2-67
Conditions . . . . . . . . . . . . . . . . . . . . . 2-11 Deep copy ehancements . . . . . . . . . . . . 3-31
Index-2 Teamcenter 8 Release Bulletin PLM00001 C

Index
Deep copy enhancements . . . . . . . . . . . 2-11 Getting Started with Aerospace and

Default volumes value . . . . . . . . . . . . . 4-41 Defense . . . . . . . . . . . . . . . . . . . 3-44
default_queries utility . . . . . . . . . . . . . . 3-3 Getting Started with Dispatcher
Deprecation (Translation Management) . . . . . . 3-45
AIWS . . . . . . . . . . . . . . . . . . . . . . . . 1-7 In general . . . . . . . . . . . . . . . . . . . . 3-38
AIX 64-bit server support . . . . . . . . . . 1-5 Installation on UNIX and Linux Servers
announcements . . . . . . . . . . . . . . . . . 1-5 Guide . . . . . . . . . . . . . . . . . 3-48, 3-58
Application Interface Web Service . . . . 1-7 Installation on Windows Servers
Bookmark launch . . . . . . . . . . . . . . . 1-22 Guide . . . . . . . . . . . . . . . . . . . . . 3-58
Business object constants . . . . . . . . . 1-19 Online help search issue . . . . . . . . . . 3-58
Excel 2003 . . . . . . . . . . . . . . . . . . . . . 1-6 Preferences and Environment Variables
Functions . . . . . . . . . . . . . . . . . . . . . 1-9 Reference . . . . . . . . . . . . . . . . . . 3-68
Global Services connectors . . . . . . 1-5–1-6 Rich Client Interface Guide . . . . . . . . 3-72
HP-UX OS on PA-RISC hardware . . . . 1-7 Schedule Manager Guide . . . . . . . . . 3-74
Image Import utility . . . . . . . . . . . . . . 1-6 Services Reference . . . . . . . . . . . . . . 3-77
IMAN_show_open_in_pv_button . . . . 1-22 Structure Manager Guide . . . . . . . . . 3-78
Java classes . . . . . . . . . . . . . . . . . . . 1-18 Teamcenter Environment Manager
object_backup utility . . . . . . . . . . . . 1-10 Help . . . . . . . . . . . . . . . . . . . . . . 3-78
object_recover utility . . . . . . . . . . . . 1-10 Upgrade Guide . . . . . . . . . . . . . . . . 3-78
Over-the-Web installer . . . . . . . . . . . . 1-8 Utilities Reference . . . . . . . . . . . . . . 3-80
Report Designer . . . . . . . . . . . . . . . . . 1-6 Workflow Designer Guide . . . . . . . . . 3-84
Rich client on UNIX-based operating ZIP file . . . . . . . . . . . . . . . . . . . . . . . 3-7
systems . . . . . . . . . . . . . . . . . . . . 1-7 Docx files in Requirements Manager . . . 3-21
Schamtics in Structure Manager . . . . . 1-8 Download hyperlink not available . . . . . 4-38
SVG Viewer plug-in . . . . . . . . . . . . . 1-22 Drag and drop . . . . . . . . . . . . . . . . . . 3-72
Teamcenter EMC Content Storage media dsa_util utility . . . . . . . . . . . . . . . . . . 4-28
type . . . . . . . . . . . . . . . . . . . . . . . 1-8 Duplicate schedules . . . . . . . . . . . . . . . 3-24
Teamcenter Services . . . . . . . . . . . . 1-11
TraceLink class . . . . . . . . . . . . . . . . . 1-6 E
Utilities . . . . . . . . . . . . . . . . . . . . . 1-10
DesignContext ECAD library
Cacheless search . . . . . . . . . . . . . . . 2-60 Import failure . . . . . . . . . . . . . 3-10, 3-30
Clearance database integration . . . . . 2-59 Spaces in field values . . . . . . . . . . . . 3-10
DHTML thin client . . . . . . . . . . . . . . . 4-51 EDA client logging . . . . . . . . . . . . . . . 2-73
Disk space requirements . . . . . . . . . . . . 1-4 Editing a GDE element . . . . . . . . . . . . 4-67
Dispatcher client . . . . . . . . . . . . . . 3-3, 3-45 EIM_check_error . . . . . . . . . . . . . . . . 4-70
Dispatcher Server EINT_init_module function . . . . . . . . . 4-46
Translation . . . . . . . . . . . . . . . . . . . 2-18 eIntegrator Admin customization . . . . . 4-46
Translation request priority . . . . . . . 1-22 ELSA Synergy graphics card . . . . . . . . 4-65
Dispatcher Server Installation Guide . . 3-43, Embedded Software Design Data
3-77 Management . . . . . . . . . . . . . . . . . . . 2-47
dispatcher_create_rqst utility . . . . . . . . 3-81 Embedded Visualization installation and
Document management uninstallation . . . . . . . . . . . . . . . . . . 4-65
IRDC . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Enabled property constant . . . . . . . . . . 3-33
Render . . . . . . . . . . . . . . . . . . . . . . 2-18 Enhanced
Documentation release notes Document generation . . . . . . . . . . . . 2-39
Access Manager Guide . . . . . . . . . . . 3-40 Export to Excel . . . . . . . . . . . . . . . . 2-21
Business Modeler IDE Guide . . . . . . 3-40 Naming rules . . . . . . . . . . . . . . 2-12, 2-69
C++ API Reference . . . . . . . . . . . . . . 3-43 Simulation process launch . . . . . . . . 2-57
Dispatcher Server Installation ensure_site_consistency utility . . . . . . . 4-26
Guide . . . . . . . . . . . . . . . . . 3-43, 3-77 Environment settings, non-English locales
ERP Connect Integration Guide . . . . 3-44 non-UTF-8 environments
Firefox . . . . . . . . . . . . . . . . . . . . . . . 3-7 Linux . . . . . . . . . . . . . . . . 3-50, 3-54

Index
UNIX . . . . . . . . . . . . . . . . 3-50, 3-54 FSC_DoNotCompressExtensions

Windows . . . . . . . . . . . . . . . . . . 3-60 property . . . . . . . . . . . . . . . . . . . . . . 3-12
Environment variables Full-text search for Microsoft Office
LANG . . . . . . . . . . . . . . . . . . . . . . . 3-50 documents . . . . . . . . . . . . . . . . . . . . . 2-7
LC_ALL . . . . . . . . . . . . . . . . . . . . . 3-50 Functions
Obsolete . . . . . . . . . . . . . . . . . . . . . 1-43 Deprecated . . . . . . . . . . . . . . . . . . . . 1-9
UTF-8 . . . . . . . . . . . . . . . . . . . . . . . 2-67 Obsolete . . . . . . . . . . . . . . . . . . . . . 1-24
EPM-check-object-properties handler . . 2-33 Future enhancements . . . . . . . . . . . . . 4-19
EPM-check-related-objects handler . . . . 2-33
EPM-create-sub-process handler . . . . . 2-33 G
EPM-set-task-result-to-property
handler . . . . . . . . . . . . . . . . . . . . . . . 2-35 Gateway application . . . . . . . . . . . . . . 2-74
ERP Connect Integration Guide . . . . . . 3-44 GDE
Error does not appear . . . . . . . . . . . . . 4-66 Link . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Ethernet MAC addresses, Sun Structure . . . . . . . . . . . . . . . . . . . . 4-67
Solaris . . . . . . . . . . . . . . . . . . . . . . . 4-57 Getting Started with Aerospace and
ETS_update_state_delay Defense . . . . . . . . . . . . . . . . . . . . . . 3-44
preference . . . . . . . . . . . . . . . . . 3-68–3-69 Getting Started with Dispatcher (Translation
Excel 2003 deprecation . . . . . . . . . . . . . 1-6 Management) . . . . . . . . . . . . . . . . . . 3-45
Excel Live Global Services
Cascading LOVs . . . . . . . . . . . . . . . 3-22 Autopopulated nonmandatory
Manufacturing Process Planner . . . . 3-22 fields . . . . . . . . . . . . . . . . . . . . . 4-24
Excel live sheet, obsolete . . . . . . . . . . . 1-22 Conversion tool shows an error . . . . . 4-25
Export Status dialog box . . . . . . . . . . . 4-48 ItemRevision sequences . . . . . . . . . . 4-22
Exporting vendor management . . . . . . . 4-28 max_objects_limit element . . . . . . . . 3-47
Extensions for Microsoft Office . . . . . . . 2-21 maximum.query.objects parameter . . 3-47
Externalization, accidental . . . . . . . . . 4-32 NoSuchMethodError exception . . . . . 4-24
Extra logon challenge . . . . . . . . . . . . . 4-42 Ownership not updated in ODS . . . . . 4-22
Query limit precedence . . . . . . . . . . . 3-47
F Release notes . . . . . . . . . . . . . . . . . . 4-24
Sample BOD does not display revision
Fail action . . . . . . . . . . . . . . . . . . . . . 2-35 number . . . . . . . . . . . . . . . . . . . 4-24
Failure paths . . . . . . . . . . . . . . . . . . . 2-35 Sample Teamcenter Item BOD . . . . . 4-24
FCC SOA connection pooling . . . . . . . . . . 2-42
Automatic configuration . . . . . . . . . . 2-15 Teamcenter 8 rich client connector . . . 2-42
Manual configuration . . . . . . . . . . . . 2-15 Global Services connectors
Feature support . . . . . . . . . . . . . . . . . 2-65 SAP Connector . . . . . . . . . . . . . . . . . 1-6
File Management System Teamcenter 2007 Rich Client
Abrupt termination . . . . . . . . . . . . . 4-35 Connector . . . . . . . . . . . . . . . . . . . 1-5
Configuration . . . . . . . . . . . . . . . . . 4-35 Teamcenter 8 Connector . . . . . . . . . . . 1-6
IMF_fmsfile_import ITK functions . . . 4-34 Teamcenter Engineering 2005/2007
IMF_import_file ITK functions . . . . . 4-34 Connector . . . . . . . . . . . . . . . . . . 1-5
Files, store and forward . . . . . . . . . . . . 2-13 Teamcenter Engineering v9
Firefox Web browser Connector . . . . . . . . . . . . . . . . . . . 1-5
Graphics disappear . . . . . . . . . . . . . 4-68 Global Technical Access Center
Launching documentation . . . . . . . . . 3-7 (GTAC) . . . . . . . . . . . . . . . . . . . . . 1-2–1-3
Release notes . . . . . . . . . . . . . . . . . . 4-68 globalservices.properties file . . . . . . . . . 3-47
Teamcenter help . . . . . . . . . . . . . . . 4-68 GM Overlay . . . . . . . . . . . . . . . . 3-36, 4-29
FMS database access . . . . . . . . . . . . . . 2-14 Character set . . . . . . . . . . . . . . . . . . 4-53
FMS URL path extensions . . . . . . . . . . 2-26 Release notes . . . . . . . . . . . . . . . . . . 4-29
Folder expansion slow in Client for UNIX . . . . . . . . . . . . . . . . . . . . . . . 4-53
Office . . . . . . . . . . . . . . . . . . . . . . . . 3-16 Upgrade . . . . . . . . . . . . . . . . . . . . . 4-29
format argument . . . . . . . . . . . . . . . . . 4-43 gmo_change_item_id_naming_rule
FSC failure . . . . . . . . . . . . . . . . . . . . . 3-13 utility . . . . . . . . . . . . . . . . . . . . . . . . 4-30

Index
GMS_offline_use_TcGS preference . . . . 3-68 Maintenance pack . . . . . . . . . . . . . . . 1-1

GMS_site_checkin_after_import Online help . . . . . . . . . . . . . . . . . . . . 3-7
preference . . . . . . . . . . . . . . . . . . . . . 3-68 Teamcenter 2007 . . . . . . . . . . . . . . . . 4-1
Graphics cards Teamcenter 8 . . . . . . . . . . . . . . . . 1-1, 3-1
ELSA Synergy . . . . . . . . . . . . . . . . . 4-65 Thin client . . . . . . . . . . . . . . . . . . . . . 4-1
NVidia Quadro 2 Pro Graphics . . . . . 4-65 Installation on UNIX and Linux Servers
NVidia Quadro 4 500 GoGL . . . . . . . 4-65 Guide . . . . . . . . . . . . . . . . . . . . . . . . 3-48
Graphics disappear . . . . . . . . . . . . . . . 4-68 Installation on Windows Servers
GRM Rules tab . . . . . . . . . . . . . . . . . . 2-10 Guide . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Guided component search Integration Toolkit, see ITK
Adding connection point definitions . . 4-19 Internationalization . . . . . . . . . . . . . . . 1-4
Release notes . . . . . . . . . . . . . . . . . . 4-19 Release notes . . . . . . . . . . . . . . . . . . 4-51
Thin client . . . . . . . . . . . . . . . . . . . . 4-51
H Internationalization release notes . . . . . 3-36
Internet Explorer . . . . . . . . . . . . . . . . 3-12
.h files . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Interoperability . . . . . . . . . . . . . . . . . 3-64
Hardware requirements . . . . . . . . . . . . . 1-4
Interspec integration . . . . . . . . . . 2-71, 3-29
Harness
Invalid item IDs, Teamcenter Integration for
Connection list . . . . . . . . . . . . . . . . . 4-37
NX . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Structure . . . . . . . . . . . . . . . . 4-38–4-39
IRDC . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Header files . . . . . . . . . . . . . . . . . . . . 4-45
IS NULL operator . . . . . . . . . . . . . . . . 4-65
Help, technical . . . . . . . . . . . . . . . . . . . 1-3
iSeries . . . . . . . . . . . . . . . . . . . . . . . . 4-63
HP-UX . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Item revision definition configuration
ODS . . . . . . . . . . . . . . . . . . . . . . . . 3-30
(IRDC) . . . . . . . . . . . . . . . . . . . . . . . . 2-8
PA-RISC hardware . . . . . . . . . . . . . . . 1-7
ItemRevision sequences . . . . . . . . . . . . 4-22
Properties dialog box . . . . . . . . 4-56, 4-58
ITK
Release notes . . . . . . . . . . . . . . . . . . 4-54
Release notes . . . . . . . . . . . . . . . . . . 4-45
HTTP enabled Multi-Site Collaboration and
Revise and save as . . . . . . . . . . . . . . 3-31
SSO . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
J
I
Japanese characters . . . . . . . . . . . . . . 3-36
ICS_GraphicsBuilder . . . . . . . . . . . . . 4-18
Java classes
Identifier business objects . . . . . . . . . . . 3-1
Deprecated . . . . . . . . . . . . . . . . . . . 1-18
IDSM servers . . . . . . . . . . . . . . . . . . . 4-52
Obsolete . . . . . . . . . . . . . . . . . . . . . 1-44
idsminetd utility . . . . . . . . . . . . . . . . . 3-63
Image Import utility, deprecating . . . . . . 1-6
IMAN_Drawing relation types . . . . . . . 4-11 L
IMAN_show_open_in_pv_button LANG variable . . . . . . . . . . . . . . . . . . 3-50
preference . . . . . . . . . . . . . . . . . . . . . 1-22 Language support . . . . . . . . . . . . . . . . 2-30
Impact Analysis view . . . . . . . . . . . . . . 3-9 Large databases . . . . . . . . . . . . . . . . . . 4-9
Implemented By relationship . . . . . . . . 4-15 Launch simulation process remotely . . . 2-58
Import failure LC_ALL variable . . . . . . . . . . . . . . . . 3-50
Classification . . . . . . . . . . . . . . . . . . 3-10 LDAP_member_list_attr preference . . . 4-31
Spaces in field names . . . . . . . . . . . . 3-10 LDAP_sync_group_flags preference . . . 4-32
TcXml . . . . . . . . . . . . . . . . . . . . . . . 3-30 LDAP_sync_member_flags
import_dfa_file utility . . . . . . . . . . . . . 1-10 preference . . . . . . . . . . . . . . . . . . . . . 4-32
Importing vendor management . . . . . . 4-28 LDAP_sync_role_flags preference . . . . . 4-32
Incompatible Teamcenter Engineering LDAP_sync_user_flags preference . . . . 4-32
connectors . . . . . . . . . . . . . . . . . . . . . 4-24 ldapsync utility . . . . . . . . . . . . . . 4-31–4-32
Incremental change . . . . . . . . . . . 2-45, 4-14 libcurl library . . . . . . . . . . . . . . . . . . . 4-46
Initial value property rules . . . . . . . . . 4-48 Licensing level
Installation Author . . . . . . . . . . . . . . . . . . . . . . . 2-7
Embedded viewer . . . . . . . . . . . . . . . . 3-6 Consumer . . . . . . . . . . . . . . . . . . . . . 2-7
Four-tier clients . . . . . . . . . . . . . . . . . 4-2 Lifecycle Viewer

Index
Disabled toolbars . . . . . . . . . . . . . . . 3-19 Release notes . . . . . . . . . . . . . . 3-20, 4-20

Lifecycle Visualization Repair Broken Links dialog box . . . . . 4-20
Authentication error . . . . . . . . . . . . 3-18 Resequence crash . . . . . . . . . . . . . . . 3-20
Bookmark . . . . . . . . . . . . . . . . . . . . 4-64 Separation of view and edit properties
Data Integration Services Adapter (DIS functionality . . . . . . . . . . . . . . . . 4-15
Adapter) . . . . . . . . . . . . . . . . . . . 1-20 Time management . . . . . . . . . . . . . . 2-43
Installation . . . . . . . . . . . . . . . . . . . . 3-6 Variant condition . . . . . . . . . . . . . . . 4-20
Markup layers . . . . . . . . . . . . . . . . . 4-63 Manufacturing Tooling Library sample
NX assembly files . . . . . . . . . . . . . . . 4-62 data . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Over-the-Web Installer . . . . . . . . . . . . 3-6 MapForce 2008 . . . . . . . . . . . . . . . . . . 2-12
Part not visible . . . . . . . . . . . . . . . . 3-18 Mapper . . . . . . . . . . . . . . . . . . . . . . . 4-66
Persistent 2D measurements . . . . . . 4-63 Markup layers . . . . . . . . . . . . . . . . . . 4-63
PRT files . . . . . . . . . . . . . . . . . 4-62, 4-64 Master schedules . . . . . . . . . . . . . . . . 3-23
Release notes . . . . . . . . . . . . . . 3-18, 4-62 max_objects_limit element . . . . . . . . . . 3-47
Repaint problems on Windows . . . . . 4-65 maximum.query.objects property . . . . . 3-47
Software error . . . . . . . . . . . . . . . . . 3-19 ME-10 vector files . . . . . . . . . . . . . . . . 4-63
Teamcenter Publish . . . . . . . . . . . . . 3-14 Mechatronics Process Management
UGALTREP files . . . . . . . . . . . . . . . 4-62 Editing a GDE element . . . . . . . . . . 4-67
UGPART files . . . . . . . . . . . . . . . . . 4-62 GDE structure . . . . . . . . . . . . . . . . . 4-67
Unable to launch . . . . . . . . . . . . . . . 4-63 Release notes . . . . . . . . . . . . . . . . . . 4-66
Viewer . . . . . . . . . . . . . . . . . . . 3-6, 3-18 Sample ITK program/utility . . . . . . . 4-67
Windows Vista . . . . . . . . . . . . . 4-63, 4-65 Mentor PADS . . . . . . . . . . . . . . . . . . . 2-73
Lifecycle Visualization performance Microsoft 2000 . . . . . . . . . . . . . . . . . . 4-60
improvements . . . . . . . . . . . . . . . . . . 2-66 Microsoft Office
Linux Client . . . . . . . . . . . . . . . . . . . . . . . 2-31
Appearance update manager . . . . . . . 4-61 Documents . . . . . . . . . . . . . . . 4-13, 4-47
IDSM servers . . . . . . . . . . . . . . . . . 4-52 Microsoft Project Plugin . . . . . . . . . . . . 3-11
Release notes . . . . . . . . . . . . . . . . . . 4-61 Microsoft release notes . . . . . . . . . . . . 4-68
SUSE Linux Enterprise Server Microsoft Windows, lost data . . . . . . . . 4-61
(SLES) . . . . . . . . . . . . . . . . . . . . . 1-5 migrate_alias utility . . . . . . . . . . . . . . . 3-1
Locale support . . . . . . . . . . . . . . . . . . 2-30 MIMIC option . . . . . . . . . . . . . . . . . . . 4-64
Localization . . . . . . . . . . . . . . . . . . . . . 1-4 Modal dialogs, rich client . . . . . . . . . . . 4-47
Lost data, Microsoft Windows . . . . . . . . 4-61 Model Error, business_objects.xml . . . . 4-29
Monitoring interface . . . . . . . . . . . . . . 4-21
M Mozilla Web browser
Release notes . . . . . . . . . . . . . . . . . . 4-69
Maintenance pack installation . . . . . . . . 1-1 Teamcenter functionality not
make_user utility . . . . . . . . . . . . 4-31–4-32 supported . . . . . . . . . . . . . . . . . . 4-69
makefiles . . . . . . . . . . . . . . . . . . . . . . 3-32 Multi language support . . . . . . . . . . . . 2-30
Manufacturing Multi-Site
Preferences . . . . . . . . . . . . . . . . . . . 2-46 Release notes . . . . . . . . . . . . . . . . . . 3-20
Time management . . . . . . . . . . . . . . 2-43 Multi-Site and Schedule Manager . . . . . 3-23
Manufacturing Process Management Multi-Site Collaboration
Guided component search . . . . . . . . . 4-19 Licenses . . . . . . . . . . . . . . . . . . . . . 4-28
Release notes . . . . . . . . . . . . . . . . . . 4-18 Oracle parameter . . . . . . . . . . . . . . . 4-26
Manufacturing Process Planner Release notes . . . . . . . . . . . . . . . . . . 4-26
2D Viewer tab . . . . . . . . . . . . . . . . . 2-44 Remote checkin . . . . . . . . . . . . . . . . 4-27
Assigned occurrence . . . . . . . . . . . . . 4-20 Security Services . . . . . . . . . . . . . . . 4-26
BOM line columns . . . . . . . . . . . . . . 4-20 Multi-Site Collaboration Guide
Calculate allocated time . . . . . . . . . . 3-20 Interoperability . . . . . . . . . . . . . . . . 3-64
Excel Live . . . . . . . . . . . . . . . . . . . . 3-22 Release notes . . . . . . . . . . . . . . . . . . 3-63
Find checked-out objects on exit . . . . 2-44 Multi-Structure Manager, 2D Viewer
GDE link . . . . . . . . . . . . . . . . . . . . . 4-20 tab . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

Index
Multi-unit support in Classification . . . 2-37 object_recover utility, deprecating . . . . . 1-10

Multilanguage support for clients . . . . . 3-83 Obsolete
Multiple View Editor, removal . . . . . . . 1-22 Environment variables . . . . . . . . . . . 1-43
MVE, removal . . . . . . . . . . . . . . . . . . . 1-22 Excel live sheet . . . . . . . . . . . . . . . . 1-22
My Teamcenter Functions . . . . . . . . . . . . . . . . . . . . 1-24
Microsoft Office documents . . . . . . . . 4-13 Java classes . . . . . . . . . . . . . . . . . . . 1-44
Perspective . . . . . . . . . . . . . . . . . . . 2-29 Preferences . . . . . . . . . . . . . . . . . . . 1-41
Product view . . . . . . . . . . . . . . . . . . 4-14 Utilities . . . . . . . . . . . . . . . . . . . . . 1-37
Release notes . . . . . . . . . . . . . . . . . . 4-13 Web tier parameters . . . . . . . . . . . . . 1-21
Save button . . . . . . . . . . . . . . . . . . . 4-14 Occurrence override support . . . . . . . . 2-64
Text file . . . . . . . . . . . . . . . . . . . . . . 4-13 ODS support . . . . . . . . . . . . . . . . . . . . 3-30
Validation report . . . . . . . . . . . . . . . 4-14 Online help . . . . . . . . . . . . . . . . . . 3-7, 3-73
Viewer pane . . . . . . . . . . . . . . 4-13–4-14 Search issue . . . . . . . . . . . . . . . . . . 3-58
Operating systems, release notes . . . . 4-52,
N 4-64
Operations, workflow . . . . . . . . . . . . . . 2-62
Named variant expression . . . . . . . . . . 4-16 Options and Variants . . . . . . . . . . . . . . 2-47
Naming rules . . . . . . . . . . . . . . . . . . . 4-30 ORA-12571 error . . . . . . . . . . . . . . . . . 4-70
Network cards, power saving option . . . 4-70 Oracle
New and changed Teamcenter 8 10g installation requirements . . . . . . 4-69
features . . . . . . . . . . . . . . . . . . . . . . . 2-1 ORA-12571 error . . . . . . . . . . . . . . . 4-70
New Content Management Permissions dialog Parameter . . . . . . . . . . . . . . . . . . . . 4-26
box . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 Power saving option error . . . . . . . . . 4-70
NoSuchMethodError exception . . . . . . . 4-24 Release notes . . . . . . . . . . . . . . . . . . 4-69
Notification of translation order SQL Server database migration
creation . . . . . . . . . . . . . . . . . . . . . . 3-91 utility . . . . . . . . . . . . . . . . . . . . . 4-68
notify handler . . . . . . . . . . . . . . . . . . . 3-85 OrCAD . . . . . . . . . . . . . . . . . . . . . . . . 2-73
Notifying of task status . . . . . . . . . . . . 3-85 Organization
NVE . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 Creating a person . . . . . . . . . . . . . . 4-33
NVidia Quadro 2 Pro Graphics card . . . 4-65 Default volume . . . . . . . . . . . . . . . . 4-33
NVidia Quadro 4 500 GoGL graphics Redundant events logged . . . . . . . . . 4-33
card . . . . . . . . . . . . . . . . . . . . . . . . . 4-65 Release notes . . . . . . . . . . . . . . . . . . 4-33
NX Search . . . . . . . . . . . . . . . . . . . . . . 2-32
Assembly files . . . . . . . . . . . . . . . . . 4-62 Orphan types . . . . . . . . . . . . . . . . . . . . 4-4
Does not launch . . . . . . . . . . . . . . . . 4-39 Over-the-Web installer, deprecating . . . . 1-8
Export . . . . . . . . . . . . . . . . . . . . . . 4-48 Ownership not updated in ODS . . . . . . 4-22
Lifecycle Visualization . . . . . . . . . . . . 3-6 Owning organization . . . . . . . . . . 2-30, 2-69
Upgrade . . . . . . . . . . . . . . . . . . . . . 4-39
NX drawings . . . . . . . . . . . . . . . . . . . 2-75 P
NX Integration . . . . . . . . . . . . . . 2-75, 3-21
Alternate ID support . . . . . . . . . . . . 2-63 PA-RISC hardware . . . . . . . . . . . . . . . . 1-7
Baselines . . . . . . . . . . . . . . . . . . . . 2-66 PAD . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
CAM support . . . . . . . . . . . . . . . . . . 2-64 Parts list management . . . . . . . . . . . . 2-68
Occurrence override support . . . . . . . 2-64 Pasting links . . . . . . . . . . . . . . . . . . . 3-13
Release notes . . . . . . . . . . . . . . . . . . 3-21 PdfGenerator translator, support . . . . . 3-73
Support for features . . . . . . . . . . . . . 2-65 PER_CLIENT setting . . . . . . . . . . . . . . 4-2
NX/requirements integration . . . . . . . . 2-75 Permission denied . . . . . . . . . . . . . . . . . 4-2
NXGraphicsBuilder . . . . . . . . . . . . . . . 4-18 Persistent 2D measurements . . . . . . . . 4-63
nxmgr_add_note_types utility . . . . . . . 4-11 Platform-specific release notes . . . 4-52, 4-64
PLM XML . . . . . . . . . . . . . . . . . . . . . 2-41
O Import/export . . . . . . . . . . . . . . . . . 4-48
Release notes . . . . . . . . . . . . . . . . . . 4-28
Object Directory Services . . . . . . . . . . . 4-22 Vendor management import and
object_backup utility, deprecating . . . . . 1-10 export . . . . . . . . . . . . . . . . . . . . 4-28

Index
PLMXML_export_packed_bom_ Properties
<transfername> preference . . . . . . . . 2-41 Dialog box . . . . . . . . . . . . 4-52, 4-56, 4-58
PLMXML_put_pie_log_in_syslog Relation . . . . . . . . . . . . . . . . . . . . . 2-70
preference . . . . . . . . . . . . . . . . . 3-68, 3-70 Required . . . . . . . . . . . . . . . . . . . . . 2-11
Pool manager . . . . . . . . . . . . . . . . . . . 4-54 Synchronizing . . . . . . . . . . . . . . . . . 4-50
Positional matrix information, Property constants . . . . . . . . . . . . . . . 3-33
transferring . . . . . . . . . . . . . . . . . . . 2-57 Property constants framework . . . . . . . 1-23
Power saving option error . . . . . . . . . . 4-70 Property Finder Formatter search results,
PowerPoint . . . . . . . . . . . . . . . . . . . . . 4-47 Report Designer . . . . . . . . . . . . . . . . 4-16
Preferences PRT files . . . . . . . . . . . . . . . . . . 4-62, 4-64
ETS_update_state_delay . . . . . 3-68–3-69 PS_Find_Number_Validation
GMS_offline_use_TcGS . . . . . . . . . . . 3-68 preference . . . . . . . . . . . . . . . . . . . . . 3-29
GMS_site_checkin_after_import . . . . 3-68 Publish
IMAN_show_open_in_pv_button . . . . 1-22 Modular variant configurations . . . . . 4-21
LDAP_sync_group_flags . . . . . . . . . . 4-32 Release notes . . . . . . . . . . . . . . . . . . 4-21
LDAP_sync_member_flags . . . . . . . . 4-32 PUBS kit long filenames . . . . . . . . . . . . 3-7
LDAP_sync_role_flags . . . . . . . . . . . 4-32
LDAP_sync_user_flags . . . . . . . . . . . 4-32 Q
Lock . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Obsolete . . . . . . . . . . . . . . . . . . . . . 1-41 QSEARCH preference . . . . . . . . . . . . . 3-30
PLMXML_export_packed_bom_ Queries . . . . . . . . . . . . . . . . . . . . . . . . 3-3
<transfername> . . . . . . . . . . . . . 2-41 Query error in Client for Office . . . . . . . 3-16
PLMXML_put_pie_log_in_syslog . . . 3-68, Quick search . . . . . . . . . . . . . . . . . . . . 4-18
3-70 Quick-release process template . . . . . . 3-84
PS_Find_Number_Validation . . . . . . 3-29
QSEARCH . . . . . . . . . . . . . . . . . . . 3-30 R
shared memory . . . . . . . . . . . . . . . . 2-17
TC_NX_Foreign_Datasets . . . . . 3-68, 3-71 Realized By relationship . . . . . . . . . . . 4-15
TC_remote_checkin_relation_send_as_ Red
replica . . . . . . . . . . . . . . . . . . . . 4-27 Background . . . . . . . . . . . . . . . . . . . 4-47
TC_ugmaster_name_separator . . . . 3-68, Datasets . . . . . . . . . . . . . . . . . . . . . 4-47
3-72 Reference designators . . . . . . . . . . . . . 4-17
Transient_Volume_RootDir . . . . . . . . 4-35 Relation
View NX .prt file as 2D . . . . . . . . . . . 4-64 Business objects . . . . . . . . . . . . . . . . 3-41
Preferences and Environment Variables Properties . . . . . . . . . . . . . . . . . . . . 3-41
Reference . . . . . . . . . . . . . . . . . . . . . 3-68 Relationships . . . . . . . . . . . . . . . . . . . 4-15
Preferences for Business Modeler IDE Security Services . . . . . . . . . . . . . . . . 4-41
Guide . . . . . . . . . . . . . . . . . . . . . . . . 3-40 Remote import . . . . . . . . . . . . . . . . . . 3-14
preferences_manager utility . . . . . . . . . . 3-3 Removal
Priority and status in Schedule Multiple View Editor . . . . . . . . . . . . 1-22
Manager . . . . . . . . . . . . . . . . . . . . . . 3-25 MVE . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Process, creating new . . . . . . . . . . . . . 2-46 Render management . . . . . . . . . . . . . . 3-72
Product release notes . . . . . . . . . . . . . . 3-1 With Lifecycle Visualization 64-bit . . 3-73
Product structure . . . . . . . . . . . . . . . . 2-57 Render, item revision . . . . . . . . . . . . . . 2-18
Product views Rendition Management . . . . . . . . . . . . 2-18
Enhancements . . . . . . . . . . . . . . . . . 2-51 Repair Broken Links dialog box . . . . . . 4-20
My Teamcenter . . . . . . . . . . . . . . . . 4-14 Repeatable Digital Validation (RDV)
Teamcenter’s lifecycle visualization Named variant expression . . . . . . . . 4-16
mockup . . . . . . . . . . . . . . . . . . . 4-63 Release notes . . . . . . . . . . . . . . . . . . 4-16
Program-level security . . . . . . . . . . . . . 2-70 Replicas and life cycle states . . . . . . . . 4-23
Project Report Designer
Search . . . . . . . . . . . . . . . . . . . . . . 2-32 Deprecating . . . . . . . . . . . . . . . . . . . . 1-6
Support . . . . . . . . . . . . . . . . . . . . . . 2-64 Property Finder Formatter search
results . . . . . . . . . . . . . . . . . . . . 4-16

Index
Release notes . . . . . . . . . . . . . . . . . . 4-16 Schedule Manager

Required properties . . . . . . . . . . . . . . . 2-11 Bill rates . . . . . . . . . . . . . . . . . . . . . 3-26
Requirements integration . . . . . . . . . . 2-38 Calendar . . . . . . . . . . . . . . . . . . . . . 3-24
Requirements Manager . . . . . . . . . . . . 3-27 Close button error . . . . . . . . . . . . . . 4-17
Cascading LOVs . . . . . . . . . . . . . . . 3-22 Cut/Copy/Paste . . . . . . . . . . . . . . . . 4-18
Multi choice . . . . . . . . . . . . . . . . . . . 3-22 Duplicate schedules . . . . . . . . . . . . . 3-24
Reference designators . . . . . . . . . . . . 4-17 Master schedules . . . . . . . . . . . . . . . 3-23
Release notes . . . . . . . . . . . . . . 3-21, 4-17 Multi-Site . . . . . . . . . . . . . . . . . . . . 3-23
Special characters in docx files . . . . . 3-21 Overwrite dialog box . . . . . . . . . . . . 4-17
Thin client . . . . . . . . . . . . . . . . . . . . 2-27 Release notes . . . . . . . . . . . . . . 3-23, 4-17
Trace link options . . . . . . . . . . . . . . 3-21 Save As operation . . . . . . . . . . . . . . 3-24
Resource Manager Summary task . . . . . . . . . . . . . . . . . 3-23
Attribute encryption . . . . . . . . . . . . . 2-46 Template chooser . . . . . . . . . . . . . . . 3-25
Sample data . . . . . . . . . . . . . . . . . . 4-19 Schedule Manager Guide
Updating Machine Tool Library . . . . . 2-47 Access changes for multisite
Restart fails . . . . . . . . . . . . . . . . . . . . 4-43 schedules . . . . . . . . . . . . . . . . . . 3-76
Resume command . . . . . . . . . . . . . . . . 3-74 Multisite schedules . . . . . . . . . . . . . 3-74
Revise operation . . . . . . . . . . . . . . . . . 3-31 Scheduling . . . . . . . . . . . . . . . . . 2-38–2-39
Revision naming rules . . . . . . . . . 2-12, 2-69 Enhancements . . . . . . . . . . . . . . . . . 2-39
Rich client Extensions . . . . . . . . . . . . . . . . . . . 2-38
Datasets . . . . . . . . . . . . . . . . . . . . . 4-47 Templates . . . . . . . . . . . . . . . . . . . . 2-38
Debugging tools . . . . . . . . . . . . . . . . 2-67 Schema mapping among Teamcenter product
Deprecated on UNIX-based operating versions . . . . . . . . . . . . . . . . . . . . . . 2-41
systems . . . . . . . . . . . . . . . . . . . . 1-7 Schematics in Structure Manager . . . . . . 1-8
Impact Analysis view . . . . . . . . . . . . . 3-9 SCM configuration rule . . . . . . . . . . . . 4-66
Microsoft Office documents . . . . . . . . 4-47 Search based on relation properties . . . 3-44
Modal dialogs . . . . . . . . . . . . . . . . . 4-47 Searching by owning organization . . . . 2-30
Not supported on HP-UX . . . . . . . . . . 2-6 Security Services
PowerPoint . . . . . . . . . . . . . . . . . . . 4-47 Dispatcher client . . . . . . . . . . . . . . . . 3-3
Red background . . . . . . . . . . . . . . . . 4-47 Logon . . . . . . . . . . . . . . . . . . . . . . . 3-11
Release notes . . . . . . . . . . . . . . . . . . 4-47 Separation of view and edit properties
Repaint problems on Windows . . . . . 4-65 functionality . . . . . . . . . . . . . . . . . . . 4-15
Rich client server fails . . . . . . . . . . . 4-70 Service-oriented architecture (SOA)
Search . . . . . . . . . . . . . . . . . . . . . . 2-29 Alternate ID support . . . . . . . . . . . . 2-63
Viewer . . . . . . . . . . . . . . . . . . . . . . . 3-6 Baselines . . . . . . . . . . . . . . . . . . . . 2-66
Rich Client Interface Guide . . . . . . . . . 3-72 CAM support . . . . . . . . . . . . . . . . . . 2-64
Ad hoc Classification search . . . . . . . 3-73 Change management service . . . . . . . 2-66
Classification attribute search . . . . . . 3-73 Connection pooling . . . . . . . . . . . . . . 2-42
Drag and drop . . . . . . . . . . . . . . . . . 3-72 Enhancements . . . . . . . . . . . . . . . . . 2-62
Online help . . . . . . . . . . . . . . . . . . . 3-73 Feature support . . . . . . . . . . . . . . . . 2-65
Render management . . . . . . . . . . . . 3-72 libcurl library . . . . . . . . . . . . . . . . . 4-46
Resume command . . . . . . . . . . . . . . 3-74 Lifecycle Visualization support . . . . . 2-66
Rich Client Lite Edition . . . . . . . . . . . . . 3-4 Miscellaneous new services . . . . . . . . 2-65
Rich client perspectives . . . . . . . . . . . . 2-28 New features . . . . . . . . . . . . . . . . . . 2-62
Rich client views . . . . . . . . . . . . . . . . . 2-28 Occurrence override support . . . . . . . 2-64
Project support . . . . . . . . . . . . . . . . 2-64
S Release notes . . . . . . . . . . . . . . . . . . 4-46
Teamcenter Gateway for EDA . . . . . . 2-73
S1000D Content Management . . . . . . . 3-17 Teamcenter Publish . . . . . . . . . . . . . 2-63
Sample program . . . . . . . . . . . . . . . . . 2-69 Workflow operations . . . . . . . . . . . . . 2-62
Save As operation . . . . . . . . . . . . 3-24, 3-31 WSDL support . . . . . . . . . . . . . . . . . 2-63
Save button . . . . . . . . . . . . . . . . . . . . 4-14 Services, see Service-oriented architecture
Saved query . . . . . . . . . . . . . . . . 4-65–4-66 (SOA)

Index
Services Reference . . . . . . . . . . . . . . . 3-77 T

Services, creating with the Business Modeler
IDE . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 TC_LOCALIZATION_DIR . . . . . . . . . . 3-83
Showing unconfigured assigned TC_NX_Foreign_Datasets
occurrences . . . . . . . . . . . . . . . . . . . . 2-45 preference . . . . . . . . . . . . . . . . . 3-68, 3-71
Simulation TC_remote_checkin_relation_send_as_replica
Process launch, enhanced . . . . . . . . . 2-57 preference . . . . . . . . . . . . . . . . . . . . . 4-27
Remote process launch . . . . . . . . . . . 2-58 TC_ugmaster_name_separator
Structure . . . . . . . . . . . . . . . . . . . . 2-57 preference . . . . . . . . . . . . . . . . . 3-68, 3-72
Simulation configuration . . . . . . . . . . . 3-12 TCM Release Status template . . . . . . . 3-84
Site definition . . . . . . . . . . . . . . . . . . . 2-19 TcXml import . . . . . . . . . . . . . . . . . . . 3-30
smlutility utility . . . . . . . . . . . . . . . . . 4-44 Teamcenter
SOA, see Service-oriented architecture, Distribution in ZIP files . . . . . . . . . . . 2-6
Service-oriented architecture (SOA) Help . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Software requirements . . . . . . . . . . . . . 1-4 Services . . . . . . . . . . . . . . . . . . . . . 1-11
Solaris 64-bit and Lifecycle Teamcenter BOM . . . . . . . . . . . . . . . . . 3-8
Visualization . . . . . . . . . . . . . . . . . . . 3-73 Teamcenter EDA
Solaris, Teamcenter EDA . . . . . . . . . . . 4-49 Cannot revise CCA . . . . . . . . . . . . . . 3-27
Specification Manager . . . . . . . . . . . . . 2-72 Cannot revise design . . . . . . . . . . . . 3-27
Specification transfer . . . . . . . . . . . . . 3-29 CopyAsReference deep copy rule . . . . 3-28
SQL Server database migration Mentor Board Station . . . . . . . . . . . . 4-49
utility . . . . . . . . . . . . . . . . . . . . . . . . 4-68 Release notes . . . . . . . . . . . . . . 3-27, 4-49
Status and priority in Schedule Solaris 10 . . . . . . . . . . . . . . . . . . . . 4-49
Manager . . . . . . . . . . . . . . . . . . . . . . 3-25 UNIX . . . . . . . . . . . . . . . . . . . . . . . 4-49
Structure Manager . . . . . . . . . . . . . . . 3-27 Teamcenter EMC Content Storage Media
AIX . . . . . . . . . . . . . . . . . . . . . . . . . 4-59 Type . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Appearance Editor dialog box . . . . . . 4-59 Teamcenter Environment Manager . . . . . 3-1
Baseline . . . . . . . . . . . . . . . . . . . . . 4-15 Teamcenter Environment Manager
Four-tier server session timeout . . . . 4-15 Help . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Implemented By relationship . . . . . . 4-15 Teamcenter File Services
Incremental change . . . . . . . . . . . . . 4-14 Release notes . . . . . . . . . . . . . . . . . . 4-34
NX export . . . . . . . . . . . . . . . . . . . . 4-48 Windows reboot . . . . . . . . . . . . . . . . . 4-3
Realized By relationship . . . . . . . . . . 4-15 Teamcenter Integration for NX
Release notes . . . . . . . . . . . . . . 3-27, 4-14 Bookmark error . . . . . . . . . . . . . . . . 4-40
Schematics . . . . . . . . . . . . . . . . . . . . 1-8 Connections . . . . . . . . . . . . . . . . . . . 4-37
Separation of view and edit Default volumes value required . . . . . 4-41
properties . . . . . . . . . . . . . . . . . . 4-15 Download hyperlink not available . . . 4-38
Viewing JT assemblies . . . . . . . . . . . 4-64 Harness . . . . . . . . . . . . . . . . . . . . . 4-37
Structure Manager Guide . . . . . . . . . . 3-78 Harness structure . . . . . . . . . . 4-38–4-39
Structures, cloning . . . . . . . . . . . . . . . 2-43 Invalid item IDs . . . . . . . . . . . . . . . . 4-40
Summary tab . . . . . . . . . . . . . . . . . . . 3-13 NX 5 . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Summary task in Schedule Manager . . . 3-23 NX does not launch . . . . . . . . . . . . . 4-39
Sun Solaris Release notes . . . . . . . . . . . . . . . . . . 4-37
Ethernet MAC addresses . . . . . . . . . 4-57 UGMASTER fails . . . . . . . . . . . . . . . 4-40
Release notes . . . . . . . . . . . . . . . . . . 4-57 Wire, deleting . . . . . . . . . . . . . . . . . 4-38
Sun Solaris 64-bit . . . . . . . . . . . . . . . . 3-73 Teamcenter perspectives . . . . . . . . . . . 2-28
Support announcements . . . . . . . . . . . . 1-5 Teamcenter Publish . . . . . . . . . . . . . . 2-63
SUSE Linux Teamcenter Publish support . . . . . . . . . 3-14
Enterprise Server (SLES) . . . . . . . . . . 1-5 Teamcenter views . . . . . . . . . . . . . . . . 2-28
Release notes . . . . . . . . . . . . . . . . . . 4-61 Teamcenter’s Client for Microsoft Office
SVG Viewer plug-in . . . . . . . . . . . . . . . 1-22 Dataset checkout . . . . . . . . . . . . . . . 3-16
Symbolic links . . . . . . . . . . . . . . . . . . 4-69 Lists of values (LOVs) . . . . . . . . . . . 3-16
System administration release notes . . . 4-31 Office Live . . . . . . . . . . . . . . . . . . . . 3-15
Outlook dataset . . . . . . . . . . . . . . . . 3-15

Index
Properties, synchronizing . . . . . . . . . 4-50 Trace link options . . . . . . . . . . . . . . . . 3-21

Release notes . . . . . . . . . . . . . . . . . . 4-50 TraceLink class deprecation . . . . . . . . . . 1-6
Task panes . . . . . . . . . . . . . . . . . . . 3-15 Transient_Volume_RootDir
Typed values do not appear . . . . . . . . 3-15 preference . . . . . . . . . . . . . . . . . . . . . 4-35
Teamcenter’s Integration for Microsoft Office Translate, data set . . . . . . . . . . . . . . . 2-18
Datasets, attaching . . . . . . . . . . . . . 4-51 Translation
Teamcenter’s Network Folders . . . . . 4-51 Request priority . . . . . . . . . . . . . . . . 1-22
Value/description pairs display . . . . . 4-61 Service . . . . . . . . . . . . . . . . . . . . . . 2-18
Teamcenter’s lifecycle visualization TSTK . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
iSeries . . . . . . . . . . . . . . . . . . . . . . 4-63 Two-tier mode . . . . . . . . . . . . . . . . . . . . 4-2
.mi file extension . . . . . . . . . . . . . . . 4-63 Two-way SSL . . . . . . . . . . . . . . . . . . . 2-26
Product views . . . . . . . . . . . . . . . . . 4-63 Typed values do not appear in Teamcenter’s
Release notes . . . . . . . . . . . . . . . . . . 4-62 Client for Microsoft Office . . . . . . . . . . 3-15
.vvi file . . . . . . . . . . . . . . . . . . . . . . 4-62 Types
.vvx file . . . . . . . . . . . . . . . . . . . . . . 4-62 Custom . . . . . . . . . . . . . . . . . . . . . . . 4-9
Teamcenter’s manufacturing process Orphaned . . . . . . . . . . . . . . . . . . . . . 4-4
management, see Manufacturing Process
Management U
Teamcenter’s mechatronics process
management, see Mechatronics Process UGALTREP files . . . . . . . . . . . . . . . . . 4-62
Management UGGraphicsBuilder . . . . . . . . . . . . . . . 4-18
Teamcenter’s reporting and analytics UGMASTER
Database query . . . . . . . . . . . . . . . . 4-66 Datasets . . . . . . . . . . . . . . . . . . . . . 4-64
Error does not appear . . . . . . . . . . . . 4-66 Fails . . . . . . . . . . . . . . . . . . . . . . . . 4-40
IS NULL operator . . . . . . . . . . . . . . 4-65 UGPART
Mapper . . . . . . . . . . . . . . . . . . . . . . 4-66 Dataset . . . . . . . . . . . . . . . . . . . . . . 3-12
Release notes . . . . . . . . . . . . . . . . . . 4-65 Files . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Saved query . . . . . . . . . . . . . . 4-65–4-66 ugtopv utility . . . . . . . . . . . . . . . . . . . 4-64
Teamcenter’s simulation process ugxxtojt utility . . . . . . . . . . . . . . . . . . 4-64
management . . . . . . . . . . . . . . . . . . . 2-57 UNIX systems
Technical help . . . . . . . . . . . . . . . . . . . . 1-3 GM Overlay . . . . . . . . . . . . . . . . . . . 4-53
TEM enforces required Oracle version . . . 2-6 IDSM servers . . . . . . . . . . . . . . . . . 4-52
Templates for document export . . . . . . . 2-22 Oracle 10g installation
Temporary graphics artifacts . . . . . . . . 4-63 requirements . . . . . . . . . . . . . . . 4-69
Text file . . . . . . . . . . . . . . . . . . . . . . . 4-13 Properties dialog box . . . . . . . . . . . . 4-52
Thin client Release notes . . . . . . . . . . . . . . . . . . 4-52
Initial value property rules . . . . . . . . 4-48 Upgrade Guide . . . . . . . . . . . . . . . . . . 3-78
Installation issue . . . . . . . . . . . . . . . . 4-1 Upgrading . . . . . . . . . . . . . . . 4-4, 4-9, 4-11
Macintosh . . . . . . . . . . . . . . . . . . . . 2-31 Database . . . . . . . . . . . . . . . . . . . . . 4-12
Non-Western European languages . . . 4-51 GM Overlay . . . . . . . . . . . . . . . 4-29–4-30
NX export . . . . . . . . . . . . . . . . . . . . 4-48 Missing database index . . . . . . . . . . 4-12
Release notes . . . . . . . . . . . . . . . . . . 4-48 Naming rules . . . . . . . . . . . . . . . . . . 4-30
Structure Manager . . . . . . . . . . . . . . 4-48 Usability release notes . . . . . . . . . 3-8, 4-13
Third-party products Use temporary folders per session . . . . 4-60
Applications support information . . . . 1-2 User
Compatibility . . . . . . . . . . . . . . . . . . 1-2 Construct and access . . . . . . . . . . . . 4-32
Release notes . . . . . . . . . . . . . . . . . . 4-68 Exits . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Software certification . . . . . . . . . . . . . 2-7 User access logging . . . . . . . . . . . . . . . 2-13
Time management . . . . . . . . . . . . . . . 2-43 user_auth_audit utility . . . . . . . . . . . . 2-13
Tomcat . . . . . . . . . . . . . . . . . . . . . . . . 4-33 UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Tool tips in Content Management . . . . . 3-17 Utilities
Toolbars disabled in Lifecycle Viewer . . 3-19 bmide_postupgradetotc . . . . . . . . . . . 4-30
Tools menu in As-Built Manager . . . . . . 3-9 bomwriter . . . . . . . . . . . . . . . . . . . . 4-43

Index
data_share . . . . . . . . . . . . . . . . . . . 3-29 WebKey account . . . . . . . . . . . . . . . . . . 1-3

data_sync . . . . . . . . . . . . . . . . 3-29, 4-43 WebLogic
Deprecated . . . . . . . . . . . . . . . . . . . 1-10 NoSuchMethodError exception . . . . . 4-24
dsa_util . . . . . . . . . . . . . . . . . . . . . . 4-28 Version 9.1 . . . . . . . . . . . . . . . . . . . . 3-7
ensure_site_consistency . . . . . . . . . . 4-26 WebDAV . . . . . . . . . . . . . . . . . . . . . 4-60
gmo_change_item_id_naming_rule . . 4-30 WebSEAL proxy support . . . . . . . . . . . 2-25
import_dfa_file . . . . . . . . . . . . . . . . 1-10 WebSEAL proxy Support . . . . . . . . . . . 2-24
ldapsync . . . . . . . . . . . . . . . . . 4-31–4-32 Windows
make_user . . . . . . . . . . . . . . . 4-31–4-32 Chinese characters . . . . . . . . . . . . . . 4-59
migrate_alias . . . . . . . . . . . . . . . . . . . 3-1 Power saving option error . . . . . . . . . 4-70
nxmgr_add_note_types . . . . . . . . . . . 4-11 Release notes . . . . . . . . . . . . . . . . . . 4-59
Obsolete . . . . . . . . . . . . . . . . . . . . . 1-37 Repaint problems on rich client . . . . . 4-65
preferences_manager . . . . . . . . . . . . . 3-3 Windows 2003 Server, unable to access files in
Release notes . . . . . . . . . . . . . . . . . . 4-43 TC_TMP_DIR . . . . . . . . . . . . . . . . . . 4-60
smlutility . . . . . . . . . . . . . . . . . . . . 4-44 Windows Vista . . . . . . . . . . . . . . . . . . 3-11
ugtopv . . . . . . . . . . . . . . . . . . . . . . 4-64 .vvi file . . . . . . . . . . . . . . . . . . . . . . 4-62
ugxxtojt . . . . . . . . . . . . . . . . . . . . . 4-64 .vvx file . . . . . . . . . . . . . . . . . . . . . . 4-62
user_auth_audit . . . . . . . . . . . . . . . 2-13 Wire, deleting . . . . . . . . . . . . . . . . . . . 4-38
Utilities Reference . . . . . . . . . . . . . . . 3-80 Workflow
adhoc-signoffs handler . . . . . . . . . . . 2-33
V auto-assign handler . . . . . . . . . . . . . 2-33
auto-assign-rest handler . . . . . . . . . . 2-33
Validate task . . . . . . . . . . . . . . . . . . . 2-35
Condition task . . . . . . . . . . . . . . . . . 2-35
Validation
CR-assign-team-selector handler . . . . 2-33
Reports . . . . . . . . . . . . . . . . . . . . . . 4-14
CR-fill-in-reviewers handler . . . . . . . 2-33
Rules . . . . . . . . . . . . . . . . . . . . . . . 2-20
CR-notify handler . . . . . . . . . . . . . . 2-33
Value/description pairs display . . . . . . . 4-61
EPM-check-object-properties
Variant condition
handler . . . . . . . . . . . . . . . . . . . 2-33
Errors . . . . . . . . . . . . . . . . . . . . . . . 4-26
EPM-check-related-objects handler . . 2-33
On parts . . . . . . . . . . . . . . . . . . . . . 4-20
EPM-create-sub-process handler . . . . 2-33
Variant expression block errors . . . . . . 4-26
EPM-set-task-result-to-property
Vendor management
handler . . . . . . . . . . . . . . . . . . . 2-35
Enhancements . . . . . . . . . . . . . . . . . 2-27
Fail action . . . . . . . . . . . . . . . . . . . . 2-35
Export . . . . . . . . . . . . . . . . . . . . . . 4-28
Failure paths . . . . . . . . . . . . . . . . . . 2-35
Import . . . . . . . . . . . . . . . . . . . . . . 4-28
Handlers . . . . . . . . . . . . . . . . . . . . . 2-33
View NX .prt file as 2D preference . . . . 4-64
Participants . . . . . . . . . . . . . . . . . . . 2-33
Viewer pane . . . . . . . . . . . . . . . . 4-13–4-14
Validate task . . . . . . . . . . . . . . . . . . 2-35
Viewers, Lifecycle Visualization and rich
Wait For Undecided Reviewers . . . . . 2-35
client . . . . . . . . . . . . . . . . . . . . . 3-6, 3-18
Workflow Designer Guide . . . . . . . . . . 3-84
Visible properties . . . . . . . . . . . . . . . . 2-11
Workflow operations . . . . . . . . . . . . . . 2-62
.vvi file . . . . . . . . . . . . . . . . . . . . . . . . 4-62
Workflow signoff task . . . . . . . . . . . . . 3-13
.vvx file . . . . . . . . . . . . . . . . . . . . . . . 4-62
WSDL support . . . . . . . . . . . . . . . . . . 2-63
W
Z
Wait For Undecided Reviewers . . . . . . . 2-35
Web tier context parameters, obsolete . . 1-21 ZIP files . . . . . . . . . . . . . . . . . . . . . . . 4-34
WEB_use_activex_lov preference . . . . . 3-14

TC 8 Release Bulletin

Uploaded by

Copyright:

Available Formats

TC 8 Release Bulletin

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TC 8 Release Bulletin

Uploaded by

Copyright:

Available Formats

Teamcenter 8

This software and related documentation are proprietary to Siemens Product

2 Teamcenter 8 Release Bulletin PLM00001 C

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

What’s new for Teamcenter 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Teamcenter 8 release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Carried forward release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

PLM00001 C Teamcenter 8 Release Bulletin 3

1 Before you begin

Teamcenter and compatible third-party software versions . . . . . . . . . . . . . . . 1-2

Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Available Teamcenter 8 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-4

Support announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

PLM00001 C Teamcenter 8 Release Bulletin

1 Before you begin

• If you are upgrading from Engineering Process Management or Teamcenter

• Maintenance pack and patch installation information is in the Installation on

PLM00001 C Teamcenter 8 Release Bulletin 1-1

Teamcenter and compatible third-party software versions

• Compatibility for relinking customizations and paths.

Typically, operating system manufacturers assure run time binary compatibility

1-2 Teamcenter 8 Release Bulletin PLM00001 C

Global Technical Access Center (GTAC)

• Frequently asked questions

• Product defect reports

• Patches and technical documentation

• Tips pertaining to Teamcenter customization, performance, and administration

• Product information, customer success stories, and user conference presentations

PLM00001 C Teamcenter 8 Release Bulletin 1-3

Available Teamcenter 8 platforms

Teamcenter 8 for HP Risc

Teamcenter 8 is supported in the following locales on all server-supported platforms:

Hardware, software, and disk space requirements

Corporate Two-tier rich

1-4 Teamcenter 8 Release Bulletin PLM00001 C

Deprecated feature announcements

• Deprecation of support for AIX 32-bit servers and clients

• Deprecation of the Global Services Teamcenter 2007 Rich Client

• Deprecation of the Global Services Teamcenter Engineering 2005/2007

• Deprecation of the Global Services Teamcenter Engineering v9

PLM00001 C Teamcenter 8 Release Bulletin 1-5

The Teamcenter 8 Global Services – Teamcenter Engineering v9 Connector is

• Deprecation of the Global Services Teamcenter 8 Connector

• Deprecation of the Global Services SAP Connector

• Deprecation of support for Excel 2003

• Deprecation of TraceLink class

• Deprecation of JT assembly format for import and export

• Deprecation of Report Designer

• Deprecation of the Image Import utility

1-6 Teamcenter 8 Release Bulletin PLM00001 C

• Deprecation of support for the Hewlett-Packard HP-UX operating

• Deprecation of rich client on UNIX-based operating systems

Demand has decreased for Teamcenter clients on UNIX-based operating

• Deprecation of Application Interface Web Service (AIWS)

PLM00001 C Teamcenter 8 Release Bulletin 1-7

• Deprecation of Over-the-Web Installer

• Deprecation of Teamcenter EMC Content Storage media type

– Content Storage media type in the rich client