tc 8 release bulletin

Teamcenter 8

Release Bulletin

Publication NumberPLM00001 C

Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens ProductLifecycle 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-2Global Technical Access Center (GTAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Available Teamcenter 8 platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Hardware, software, and disk space requirements . . . . . . . . . . . . . . . . . . . . . 1-4Support announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

What’s new for Teamcenter 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

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

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

Teamcenter 8 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Teamcenter 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-5Deprecated feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Deprecated ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Deprecated utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Deprecated services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Deprecated Java classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Obsolete feature announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Obsolete ITK functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Obsolete utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37Obsolete preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41Obsolete environment variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43Obsolete 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 UNIXand Linux Servers Guide or Installation on Windows Servers Guide.

• If you are upgrading from Engineering Process Management or Teamcenter2007, see the Upgrade Guide.

• Maintenance pack and patch installation information is in the Installation onUNIX and Linux Servers Guide and the Installation on Windows Servers Guide.If you are installing a maintenance pack on to an existing installation, see theInstalling Teamcenter maintenance packs topic, or if you are installing a patchon to an existing installation, see the Installing Teamcenter patches topic.

Note that you can create a new installation of Teamcenter from a maintenancepack version. If you do so, see either the first-time installation instructions orthe upgrading instructions, whichever is appropriate for your situation.

• For general guidelines and best practices for a Teamcenter system administratorto follow when deploying a new or upgrading an existing Teamcenter system, seethe 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 forTeamcenter 8. This topic also appears in the online help collection.

To review notes about known software problems and their workarounds, seeTeamcenter 8 release notes and Carried forward release notes.

To review notes about corrections or additions to the published documentation, seeTeamcenter 8 documentation release notes.

PLM00001 C Teamcenter 8 Release Bulletin 1-1

Chapter 1 Before you begin

Teamcenter and compatible third-party software versionsThe Siemens PLM Software Certification Database(http://support.ugs.com/online_library/certification/) documents the minimumversion of operating systems, compilers, databases, client browsers, and otherthird-party software with which this product is compatible. Because Teamcenterreleases are asynchronous with the release of compatible third-party software,Teamcenter customers can acquire and install a newer version of third-partysoftware before Siemens PLM Software has the opportunity to certify it.

Siemens PLM Software’s standard policy with respect to new versions of operatingsystems, compilers, databases, client browsers, and other third-party software relieson the manufacturers’ guarantees. If the manufacturer guarantees that the newversion of its product is binary-compatible with the preceding version, SiemensPLM Software expects our products to function properly when running on the newversion. Our experience shows that virtually no problems are encountered whenexecuting Teamcenter with a third-party version later than the version on whichwe completed our certification testing.

Siemens PLM Software will make a reasonable effort to support Teamcenter runningon a later version and to work with you to resolve any difficulty that may arise butwill not, in most cases, complete the testing required to state Teamcenter software iscertified.

Teamcenter compatibility with operating systems and compilers involves thesetwo considerations:

• Compatibility for runtime.

• Compatibility for relinking customizations and paths.

Typically, operating system manufacturers assure run time binary compatibilitybetween the successive versions of their operating systems. We make a reasonableeffort to support Teamcenter running on a later version of an operating system. Toa lesser degree, operating system manufacturers provide similar assurances whenrelinking 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 linkedusing the version of the compiler with which Teamcenter has been released. Thisalso applies to the installation of Teamcenter patches.

To summarize, Teamcenter may run on a newer version of an operating system, butcustomizations 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 mayrun using a lower level of software, keep in mind that we strongly discouragerunning at lower levels and that we do not provide support to anyone doing so.

Note

If Siemens PLM Software discovers incompatible versions of third-partysoftware, we will post bulletins on GTAC. This information is also availablefrom your Teamcenter provider.

1-2 Teamcenter 8 Release Bulletin PLM00001 C

http://support.ugs.com/online_library/certification/

Before you begin

Global Technical Access Center (GTAC)GTAC is the vehicle for Teamcenter communication. It provides a single repositoryof current, accurate, version-controlled Teamcenter information that is accessiblethrough the Internet by authorized users. Maintained within GTAC is a wealth ofinformation for the diverse mix of customers and employees in the Teamcentercommunity.

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 throughits 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 asingle point of authentication that allows customers to access product informationand associated support tools. WebKey accounts are strictly limited to Siemens PLMSoftware employees and to people or companies who belong to the Teamcentercommunity through contractual agreements with Siemens PLM Software pertainingto Teamcenter. Requests for access to GTAC using a WebKey account can be directedto the following Web site:

https://plmapps.ugs.com/webkey/



Available Teamcenter 8 platformsThe following distribution images are available as part of Teamcenter 8:

Teamcenter 8 for HP RiscTeamcenter 8 for HP ItaniumTeamcenter 8 for IBM AIXTeamcenter 8 for Sun Solaris SparcTeamcenter 8 for Microsoft WindowsTeamcenter 8 for Linux SUSE 64Teamcenter 8 for Over-the-Web installation, All PlatformsTeamcenter 8 Embedded Visualization, All PlatformsTeamcenter 8 Publications, All Platforms

Teamcenter 8 is supported in the following locales on all server-supported platforms:

Chinese SimplifiedChinese TraditionalCzechEnglishFrenchGermanHebrewItalianJapaneseKoreanRussianSpanish

Hardware, software, and disk space requirementsFor information about system hardware and software requirements for Teamcenter8, see the Siemens PLM Software Certification Database:


The following table shows the required disk space for the platforms supported byTeamcenter.

PlatformCorporateserver

Two-tier richclient Web tier

Hewlett-PackardHP-UX (Itanium)

3.0 GB Not supported 3.0 GB

Hewlett-PackardHP-UX

3.0 GB Not supported 3.0 GB

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 announcementsAs Siemens PLM Software enhances Teamcenter, some features are deprecated orobsoleted. Deprecation identifies items that will be removed in a future version ofTeamcenter. Obsolescence identifies items that are either removed from Teamcenteror 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 discontinueat Teamcenter 8.1. Teamcenter will support only version 10 SP2 and higher forboth clients and servers starting with Teamcenter 8.1.

For a listing of supported platforms for Teamcenter, see the certification tableat 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 operatingsystem starting with Teamcenter 8.1. For a listing of supported platforms forTeamcenter, see the certification table at the following URL:


• Deprecation of the Global Services Teamcenter 2007 Rich ClientConnector


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

• Deprecation of the Global Services Teamcenter Engineering 2005/2007Connector


The Teamcenter 8 Global Services – Teamcenter Engineering 2005/2007Connector is deprecated. This connector will be removed when TeamcenterEngineering 2007 is no longer supported.

• Deprecation of the Global Services Teamcenter Engineering v9Connector




The Teamcenter 8 Global Services – Teamcenter Engineering v9 Connector isdeprecated. This connector will be removed when Teamcenter Engineering V9is no longer supported.

• Deprecation of the Global Services Teamcenter 8 Connector


The Teamcenter 8 Global Services – Teamcenter 8 Connector is deprecated. Thisconnector 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. Thisconnector 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 2003beginning at Teamcenter 8.1.

• Deprecation of TraceLink class


The TraceLink class is deprecated and will be removed in Teamcenter 9.0. Itwas originally defined under theManagedRelations class in Teamcenter 2007.The trace link functionality is now migrated to the FND_TraceLink class underthe IMAN_Relation class. Users should use the FND_TraceLink class for allcustomization 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 andwill be removed after Teamcenter 8.1. Instead, use the PLM XML format ratherthan the JT assembly format. This will export and import JT files, along withthe 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 Designerapplication. Report Designer will still be supported in Teamcenter 8, however,support will be dropped in a future version. Customers are encouraged to usethe 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 locatedon the Teamcenter installation CD-ROM in the additional_applications folder.


Before you begin

• Deprecation of support for the Hewlett-Packard HP-UX operatingsystem 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 thedeprecation of HP-UX on the PA-RISC hardware platform and is moving serverimplementations to the HP-UX Integrity platform based on the Intel Itanium2platform. More information about HP-UX PA-RISC deprecation is available onthe 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 thefollowing 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 operatingsystems. UNIX hardware vendors now concentrate on servers instead ofdesktops. Support for the HP-UX PA-RISC rich client is discontinued withTeamcenter 8 and support for the Solaris and AIX rich client will be discontinuedwith Teamcenter 9. This change is a result of issues with third-party softwaredependencies on the HP-UX PA-RISC platform.

Only the Teamcenter rich client on UNIX systems is deprecated. The Teamcenterthin 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 SUSELinux-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 bediscontinued at Teamcenter 9. Use service-oriented architecture (SOA) todevelop new clients instead of AIWS. For more information about SOA, see theServices 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 eitherTeamcenter Environment Manager or by using push install technology, such asMicrosoft Systems Management Server (SMS).

On the Windows platform, a new, more firewall friendly pull mechanism will beintroduced 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 includedin Teamcenter. Backup and recovery functionality remains as a supportedcapability in Teamcenter but without support for the EMC Content Storagemedia 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 thear_content_storage_media_api.c and ar_content_storage_media.hfiles

• Deprecation of schematics in Structure Manager


The ability to view schematic diagrams in the Structure Manager viewer isdeprecated. Replacement of this functionality is targeted in a future releasebased 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 ToolkitFunction Reference.



Deprecated utilities

Teamcenter command line utilities are used by administrators to manageTeamcenter installations. For more information about utilities, see the UtilitiesReference.

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 andobject_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. Theimport_dfa_file utility corrupts data model objects managed by the BusinessModeler IDE. If you use this utility, you may corrupt the data model and the datamay become inaccurate. Use the Business Modeler IDE to create and managethe objects that were previously managed by this utility.


Before you begin

Deprecated services

Teamcenter Services are a collection of Teamcenter operations used by systemadministrators to connect their company’s applications to Teamcenter. For librariesand documentation (which includes the list of deprecated services), see thesoa_client.zip file on the Teamcenter software distribution image. The servicesdocumentation is also presented as the Services Reference in the Teamcenter HTMLCollection.

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 getAttachedPropDescsin the Core library.

– Teamcenter::Services::Core::LovService::getAttachedLOVs (const std::vector< LOVInfo > &inputs)=0

Deprecated as of Teamcenter 2007; replaced with getAttachedPropDescsin 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 fromsession0701.

– Teamcenter::Services::Core::SessionService::getPreferences (const std::string &prefScope, const std::vector<std::string > &prefNames)=0



Deprecated as of Teamcenter 2007; replaced with getPreferences fromsession0701.

– Teamcenter::Services::Core::_2006_03::Session::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 operationinstead.

– Teamcenter::Services::Core::SessionService::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 operationinstead.

– Teamcenter::Services::Core::_2006_03::Session::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::loginSSOoperation instead.

– Teamcenter::Services::Core::SessionService::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::loginSSOoperation 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 CADlibrary.

– Teamcenter::Services::Cad::DatamanagementService::createOrUpdateParts (const std::vector<Teamcenter::Services::Cad::_2007_01::Datamanagement::PartInfo >&info)=0

See createOrUpdateParts from datamanagement0712 in the CADlibrary.

– Teamcenter::Services::Cad::_2007_01::Datamanagement::getAvailableTypes (const std::vector< std::string > &classes)=0

Deprecated as of Teamcenter 2007; see getAvailableTypes fromdatamanagement0706 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 fromdatamanagement0706 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 SR1MP2 and will be supported for two more releases only. This operation isreplaced with getEngineeringDataFromRoutine2.

– Teamcenter::Services::Productionmanagement::EngineeringdataqueryService::getEngineeringDataFromRoutine (const std::vector<Teamcenter::Services::Productionmanagement::_2007_06::Engineeringdataquery::RoutineIdVer > &routineIdVer)=0

getEngineeringDataFromRoutine is deprecated in Teamcenter 2007 SR1MP2 and will be supported for two more releases only. This operation isreplaced with getEngineeringDataFromRoutine2.

– Teamcenter::Services::Productionmanagement::_2007_12::Engineeringdataquery::getEngineeringDataFromRoutine2 (const std::vector<Teamcenter::Services::Productionmanagement::_2007_12::Engineeringdataquery::RoutineIdVer2 > &routineIdVer)=0

getEngineeringDataFromRoutine2 is deprecated in Teamcenter 2007SR1 MP3 and will be supported for two more releases only. This operation isreplaced with getEngineeringDataFromRoutine3.

– Teamcenter::Services::Productionmanagement::EngineeringdataqueryService::getEngineeringDataFromRoutine2 (const std::vector<Teamcenter::Services::Productionmanagement::_2007_12::Engineeringdataquery::RoutineIdVer2 > &routineIdVer)=0

getEngineeringDataFromRoutine2 is deprecated in Teamcenter 2007SR1 MP3 and will be supported for two more releases only. This operation isreplaced with getEngineeringDataFromRoutine3.

– Teamcenter::Services::Productionmanagement::_2007_06::Engineeringdataquery::getFeatureAttributeDataOfCluster (const std::vector<Teamcenter::Services::Productionmanagement::_2007_06::Engineeringdataquery::ClusterIdentifier > &clusterIdentifier)=0

getFeatureAttributeDataOfCluster is deprecated in Teamcenter 2007SR1 MP2 and will be supported for two more releases only. This operation isreplaced with getFeatureAttributeDataOfCluster2.



– Teamcenter::Services::Productionmanagement::EngineeringdataqueryService::getFeatureAttributeDataOfCluster (const std::vector<Teamcenter::Services::Productionmanagement::_2007_06::Engineeringdataquery::ClusterIdentifier > &clusterIdentifier)=0

getFeatureAttributeDataOfCluster is deprecated in Teamcenter 2007SR1 MP2 and will be supported for two more releases only. This operation isreplaced with getFeatureAttributeDataOfCluster2.

• ProjectManagement

– Teamcenter::Services::Projectmanagement::_2007_01::Schedulemanagement::copySchedules (const std::vector< ScheduleCopyContainer >&scheduleCopyContainer)=0

Deprecated as of Teamcenter 2007; replaced with copySchedules fromschedulemanagement0706.

– Teamcenter::Services::Projectmanagement::SchedulemanagementService::copySchedules (const std::vector< ScheduleCopyContainer >&scheduleCopyContainer)=0

Deprecated as of Teamcenter 2007; replaced with copySchedules fromschedulemanagement0706.

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

– Teamcenter::Services::Query::_2007_01::Savedquery::retrieveQueryCriterias (const std::vector< std::string >&queryCriteriaNames)=0

Deprecated as of Teamcenter 2007; replaced with retrieveSearchCriteriafrom savedquery0706.

– Teamcenter::Services::Query::SavedqueryService::retrieveQueryCriterias (const std::vector< std::string >&queryCriteriaNames)=0

Deprecated as of Teamcenter 2007; replaced with retrieveSearchCriteriafrom savedquery0706.


Before you begin

– Teamcenter::Services::Query::_2007_01::Savedquery::saveQueryCriterias (const std::vector< SaveQueryCriteriaInfo >&queryCriterias)=0

Deprecated as of Teamcenter 2007; replaced with saveSearchCriteriafrom savedquery0706.

– Teamcenter::Services::Query::SavedqueryService::saveQueryCriterias (const std::vector< SaveQueryCriteriaInfo >&queryCriterias)=0

Deprecated as of Teamcenter 2007; replaced with saveSearchCriteriafrom savedquery0706.

• 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 fromcrfreports0806 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 fromcrfreports0806 in Reports library.

• ServiceData

– Teamcenter::Soa::Server::ServiceData::addUpdatedObject (const BusinessObjectRef<Teamcenter::BusinessObject > obj)

Use the addUpdatedObject( obj, propNames ) method to specify theexact 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 theexact properties that have been updated.

• StructureManagement

– Teamcenter::Services::Cad::_2007_01::Structuremanagement::createOrUpdateAbsoluteStructure (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateAbsoluteStructureInfo > &info, conststd::string &bomViewTypeName, bool complete, constTeamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateAbsoluteStructurePref &pref)=0



See createOrUpdateAbsoluteStructure fromstructuremanagement0712 in the CAD library.

– Teamcenter::Services::Cad::StructuremanagementService::createOrUpdateAbsoluteStructure (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateAbsoluteStructureInfo > &info, conststd::string &bomViewTypeName, bool complete, constTeamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateAbsoluteStructurePref &pref)=0

See createOrUpdateAbsoluteStructure fromstructuremanagement0712 in the CAD library.

– Teamcenter::Services::Cad::_2007_01::Structuremanagement::createOrUpdateRelativeStructure (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateRelativeStructureInfo > &inputs, conststd::string &bomViewTypeName, bool complete, constTeamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateRelativeStructurePref &pref)=0

See createOrUpdateRelativeStructure fromstructuremanagement0712 in the CAD library.

– Teamcenter::Services::Cad::StructuremanagementService::createOrUpdateRelativeStructure (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateRelativeStructureInfo > &inputs, conststd::string &bomViewTypeName, bool complete, constTeamcenter::Services::Cad::_2007_01::Structuremanagement::CreateOrUpdateRelativeStructurePref &pref)=0

See createOrUpdateRelativeStructure fromstructuremanagement0712 in the CAD library.

– Teamcenter::Services::Cad::_2007_06::Structuremanagement::createOrUpdateVariantConditions (const std::vector<Teamcenter::Services::Cad::_2007_06::Structuremanagement::CreateOrUpdateVariantCondInput > &inputObjects)=0

Deprecated as of Teamcenter 2007 SR1 MP1. SeecreateOrUpdateVariantConditions2.

– Teamcenter::Services::Cad::StructuremanagementService::createOrUpdateVariantConditions (const std::vector<Teamcenter::Services::Cad::_2007_06::Structuremanagement::CreateOrUpdateVariantCondInput > &inputObjects)=0

Deprecated as of Teamcenter 2007 SR1 MP1, seecreateOrUpdateVariantConditions2.

– Teamcenter::Services::Cad::_2007_01::Structuremanagement::deleteAssemblyArrangements (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::DeleteAssemblyArrangementsInfo > &info, const std::string&bomViewTypeName)=0


Before you begin

See deleteAssemblyArrangements from structuremanagement0712 inthe CAD library.

– Teamcenter::Services::Cad::StructuremanagementService::deleteAssemblyArrangements (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::DeleteAssemblyArrangementsInfo > &info, const std::string&bomViewTypeName)=0

See deleteAssemblyArrangements from structuremanagement0712 inthe CAD library.

– Teamcenter::Services::Cad::_2007_01::Structuremanagement::deleteRelativeStructure (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::DeleteRelativeStructureInfo > &inputs,const std::string &bomViewTypeName, constTeamcenter::Services::Cad::_2007_01::Structuremanagement::DeleteRelativeStructurePref &pref)=0

See deleteRelativeStructure from structuremanagement0712 in theCAD library.

– Teamcenter::Services::Cad::StructuremanagementService::deleteRelativeStructure (const std::vector<Teamcenter::Services::Cad::_2007_01::Structuremanagement::DeleteRelativeStructureInfo > &inputs,const std::string &bomViewTypeName, constTeamcenter::Services::Cad::_2007_01::Structuremanagement::DeleteRelativeStructurePref &pref)=0

See deleteRelativeStructure from structuremanagement0712 in theCAD 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 inCore::DispatcherManagement using the DispatcherRequest object andno 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 inCore::DispatcherManagement using the DispatcherRequest object andno 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 nowobsolete


In Teamcenter 2007.1, the AutoCopyRel and AutoRevise business objectconstants were introduced to support the requirement to automatically reviseand relate the related object during a Revise operation of an ItemRevisionbusiness object. These two constants are now obsolete.

Beginning in Teamcenter 8, do not use the AutoCopyRel and AutoRevisebusiness object constants. The functionality provided by these two businessobject constants are replaced by deep copy rules. In Teamcenter 8 the deep copyrules are enhanced to support this behavior using the Relate To Latest andRevise 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 Teamcenter8, you do not have to do anything, since these constants were available onlyin Teamcenter 2007.1.

– Upgrading from Teamcenter 2007.1 to Teamcenter 8

If you are upgrading from Teamcenter 2007.1 to Teamcenter 8, you may haveconstant attachments for the AutoCopyRel and AutoRevise businessobject constants. Per the new upgrade process, the customer template projectmust first be upgraded in the Business Modeler IDE client before upgradingthe database. During upgrade of the customer template project in theBusiness Modeler IDE client, migration utilities are written to automaticallyhandle converting the AutoCopyRel and AutoRevise constants to deepcopy rules. After upgrading the customer template project, the sametemplate is packaged and supplied during database upgrade. The databaseupgrade process ensures that your AutoCopyRel and AutoRevise businessobjects constants are correctly converted to deep copy rules. Therefore, thecustomer upgrading from Teamcenter 2007.1 to Teamcenter 8 does not haveany other manual steps to perform. By following the standard Teamcenterupgrade process, the system ensures that your current behavior supportedby the business objects continues to be supported by deep copy rules afterupgrade 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 (suchas DesignRevision_Maturity_Level) are replaced by theMaturityStatusesbusiness object constant.



In Teamcenter 2007.1, the item-revision-business-objectMaturity_Levelpreference was introduced to configure maturity status for ItemRevisionobjects. This preference is obsolete in Teamcenter 8 and is replaced by theMaturityStatuses business object constant.

The capability to configure the determination of the maturity status ofan ItemRevision object is supported through the MaturityStatusesbusiness object constant in the Business Modeler IDE instead of theitem-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 theitem-revision-business-objectMaturity_Level preference was introducedonly in Teamcenter 2007.1.

– Upgrading from Teamcenter 2007.1 to Teamcenter 8

Migration utilities are written to convert theitem-revision-business-objectMaturity_Level preferences toMaturityStatuses business object constant attachments. If you havepreferences that use the item-revision-business-objectMaturity_Levelformat, you must follow the steps to migrate these preferences as describedin the Migrate preferences to data model objects topic in the BusinessModeler IDE Guide.

As part of the steps performed prior to the upgrade process, you wouldextract the preferences from your database and perform migration inthe Business Modeler IDE using the Preferences Migration wizard. Afterthe preference migration in the Business Modeler IDE, a file namedcleanup_preferences.txt is generated. This file must be invoked from yourcustom 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 completelyremoved from Teamcenter. Teamcenter’s integration with the LifecycleVisualization viewers is now based upon a service-oriented architecture (SOA).This new integration is installed automatically with Teamcenter and noadditional steps are required to work with visualization data in the Teamcenter8 managed environment.

Lifecycle Visualization viewers from earlier releases are not supported by andcannot communicate with Teamcenter 8. However, the Teamcenter 8 stand-aloneviewers can communicate with DIS-enabled servers from previous Teamcenterreleases.


Before you begin

• Obsolete Web tier context parameters


The following Web tier context parameters are obsolete in Teamcenter 8:

AdapterAdministratorEnableAutoSaveLocationFileUploadDirectoryJtCache.BatchPopulateJtCache.BatchPopulateFirstTimeJtCache.BatchPopulateIntervalHoursJtCache.Limited.BackupIntervalMinutesJtCache.Limited.CapacityMBJtCache.Limited.CleanFirstTimeJtCache.Limited.CleanIntervalHoursJtCache.Limited.EnableJtCache.Limited.PathJtCache.Limited.SisterStatusNameListJtCache.Limited.SisterSynchIntervalJtCache.Limited.StatusNameJtCache.Populator.BackupIntervalMinutesJtCache.Populator.PathJtCache.Populator.QueueNameJtCache.World.BackupIntervalMinutesJtCache.World.CapacityMBJtCache.World.CleanFirstTimeJtCache.World.CleanIntervalHoursJtCache.World.EnableJtCache.World.PathJtCache.World.PopulatorUserJtCache.World.SisterStatusNameListJtCache.World.SisterSynchIntervalJtCache.World.StatusNameMask.RefSetNames.ItemRevPasswordFileSessionPurgeFrequencySessionTimeoutTcEngExcludeFilesTcEngExcludeFilesExtFromSaveTcEngExcludeObjectTypesTcEngExcludeTypesFromSaveTcEngMetaDataStampTcEngPropertiesVVI.DirectModel.DocumentVVI.ImageView.DocumentVVI.PDFView.DocumentVVI.TempFolderVVI.Vis3DLayerVVI.VisView.SessionVVI.VisView.SessionPackage



• Obsolete Excel sheet functionality


Teamcenter Extensions for Microsoft Office does not generate a live Excel sheetfor the Excel 2003 application. However, it continues to generate a static sheetfor 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 clientand thin client using bookmarks is obsolete. This functionality is superseded bythe functionality that launches Lifecycle Visualization using the VVI file, whichis based on the PLM XML launch mechanism and Data Integration ServicesAdapter technology. The IMAN_show_open_in_pv_button preference thatenables the functionality is also removed.

• Adobe will no longer support its SVG Viewer plug-in for InternetExplorer


As of January 2009, Adobe will no longer support or enhance its SVG Viewerplug-in for Internet Explorer. Siemens PLM Software is planning to replace thistechnology in the thin client, but we recommend that you continue to use it toenable 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 tothe low customer base implementation and duplication of functionality inMulti-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 inthe translation administrator console.

Administrators can change priorities as well as translation execution times inthe 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 everyfeature of the property rule. The existing property rules data model did notallow you to override a specific feature of the rule without also setting the otherfeatures. Once a property rule is created, all features are set and any inheritedrule subsequently created from a higher business object in the hierarchy likelywould not pass its new feature values past this property rule to business objectsbelow. The new property constants provide a robust framework to supportcustom overrides on every feature of the rule.

Migration utilities are incorporated in the upgrade scripts to perform migrationof all existing property rule objects in your database to the property constantsframework. The existing functions used to retrieve the property rules onthe server are deprecated. For the complete list of deprecated property rulefunctions, see Obsolete ITK functions.



Obsolete ITK functions

The following functions are obsolete in Teamcenter 8. All of these functions arereplaced 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 ChangeManagement

ECM_add_formtype()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 –cascade release

CR_create_status_type()

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

AE_add_datasettype_file_ref()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 – ApplicationInterface

AIType_create()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 ProcessManagement – GDE link

GDELinkType_add_subtype()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 – generalcomponent relation

GCR_create_relation_type()

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_requiredPROPDESC_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_valuewith signature.

AOM_UIF_is_enabled CONSTANTS_get_property_constant_valuewith signature.

AOM_UIF_is_required CONSTANTS_get_property_constant_valuewith 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_namesandAOM_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, followedby 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 andITEM_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 orGRM_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 orGRM_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, andAOM_unlock

ITEM_update_rev_attachment GRM_find_relation, followed by AOM_delete,GRM_create_relation, AOM_save, andAOM_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_valuewith signature.

PROPDESC_is_modifiable CONSTANTS_get_property_constant_valuewith signature.

PROPDESC_is_required CONSTANTS_get_property_constant_valuewith 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 byWSOM_eff_ask_ranges.

WSOM_eff_set_range WSOM_eff_set_date_range orWSOM_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 orWSOM_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 orWSOM_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 ToolkitFunction Reference.


Before you begin

Obsolete utilities

Teamcenter command line utilities are used by administrators to manageTeamcenter 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 partsin GPDS and generates two outputfiles.

Business Modeler apply_naming_rule Creates and maintains namingrules for the naming rules checker.

business_rules_dtdxml2plmxml Converts an XML file conformingto a specified DTD into a valid PLMXML file pertaining to a specifiedPLM XML schema definition file.

deepcopyrules_migration Migrates deep copy rules existingin a Teamcenter’s engineeringprocess management 8.1 databasepreference file to Teamcenter 2007database rules.

grm Provides means to manipulateconstraint rules.

import_export_business_rules Imports and exports businessrules to and from the Teamcenterdatabase.

install_bmf_rules Installs extensions and operationsfor all messages defined in thesystem.

install_type_display_rules Creates system-level type displayrules.

migrate_action_rules_to_bmf Migrates action rules definedfor a site and converts them toextension rules.

migrate_alias Migrates alias data to aliasidentifier data without modifyingor deleting the existing data. Onlyalias data owned by the local sitecan be migrated. You can qualifywhat data is migrated.




migrate_complex_property_rules Creates complex property rulesin the database correspondingto those stored in the preferencevariables prior to EngineeringProcess Management 2005 SR1.

ChangeManagement

create_change_types Provides a means for siteadministrators to define one ormore change type definitions fromthe command line. This utilitycreates change types according tothe information contained in aninput file.

Customization tc_erp_schema Updates the database with newclasses and attributes. Oncemade, these updates cannot bereversed; therefore, you shouldcarefully analyze what form typesand attributes are required tosend data to SAP. Once attributesare created for a form type, theycan not be removed or modified.However, you can create new formtypes to correct the attributesrequired, but this preventspreviously created and populatedform types from being correctlyread or sent to ERP, because theydo not correspond to the newdefinitions in the mapping file.

Data sharing upgrade_nx_cam_templates Imports NX/CAM templates intothe Teamcenter database.

Migration migrate_type_display_prefs In the Teamcenter’s engineeringprocess management 8.0 thinclient interface, only thoseform type values listed in theFormTypePref preference aredisplayed. This utility considersthe preference values stored atthe site level and creates typedisplay rules so that only the typeslisted under the site preferenceare displayed in the object creationdialog boxes. Then the utilitytraverses the group hierarchy andconsiders the preference valuesin the group preference files andcreates type display rules.

Product structure input_notetype_default Inputs default values for notetypes.


Before you begin


Visualization batchmode_clearance_analysis.pl Performs clearance analysison a product structure andstores all issue and resultsdata in the clearance database.This script is replaced by theanalyze_managed_product.plscript, which is included in thestand-alone Teamcenter’s lifecyclevisualization mockup installation.

runJtCacheClean Physically removes orphaned filesfrom the cache used by the JTcache service.

runJtCacheInit Initializes user sessions for theTeamcenter Data IntegrationServices Adapter JT cachepopulator.

runJtCachePopulator Runs the Teamcenter DataIntegration Services Adapter JTcache populator.

Volume anddatabasemanagement

create_ai_type Creates and updates applicationinterface types for Tecnomatix.

create_cost_form Creates a cost form type for theCME Cost Reports; creates a POMtype = CostDataClass and aForm type = CostDataFormwith a cost field = CostAmount.

create_snap_shot_view_form Creates the SnapShotClass formfor the SnapShotView dataset.

datasettype_cleanup Locates corrupt dataset types andremoves them from the database.

install_lovs Creates the default lists of values(LOVs).

install_types Adds new types to existing classesand may also be used to deletetypes, provided that they are notreferenced by other objects. Thisutility is initially run as part ofthe installation program to installpredefined object types.

make_datasettype Defines new dataset types andtools for Teamcenter.




Schema browser (character mode) The sb utility is a character-mode(VT100) utility used to view(browse) the Persistent ObjectModel (POM) class hierarchy(schema) as well as to createand manage object classes andattributes. The utility operatesin two modes: browser mode andcommand mode.

update_class_property Updates the schema to changesome of class properties.

upgrade_ar Disables follow-on-export ofthe items_tag attribute ofthe ItemRevision class andthe child_bv and child_itemattributes of the PSOccurrenceclass.

upgrade_types Upgrades an existing databaseto create imantypes for allworkspaceobjects, formtypes,and datasettypes. Checks forduplicate types, and ensures thereare no clashes between type andclass names.

upgrade_validation_objects Upgrades the validation objectsto Teamcenter Engineering 10 orlater.


Before you begin

Obsolete preferences

Preferences are special environment variables stored in the Teamcenter databasethat 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 EnvironmentVariables 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 businessobject 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 andEnvironment Variables Reference.

The following environment variables are obsolete:

• TC_CURSOR_CACHE

Master variable for the POM minimize query parsing functionality. Validvalues are enabled, enable, true , and on. If set to a value other than oneof the valid values, the feature is inactive and the other POM query parsingenvironment variables have no affect on the system. Additional POM queryparsing 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 isthe number of database cursors available to the server for processing SQLstatements.

• TC_CURSOR_SQL

Determines the size of the SQL statement pool for each Teamcenter server. TheSQL statement pool is where the server keeps track of SQL statements that havealready been processed. If a SQL statement has recently been executed, or hasbeen executed a sufficient number of times, the SQL entry in the pool points tothe cursor in the cursor pool that last executed the SQL statement. When thisvariable is set equal to the value of TC_CURSOR_NUM variable, the leastrecently used algorithm determines which cursor is the next available cursor.Otherwise, the cursor associated with the SQL statement that has the lowestexecution count is designated the next available cursor.

• TC_CURSOR_LNSZ

Determines the maximum line size used when dumping SQL statements tothe system log (see the TC_CURSOR_STAT variable.) If dumping an SQLstatement to the system log file would cause the length of the line to exceed thisvalue, attributes are removed from the select statements and replaced withthree periods (…). If the cursor and the SQL statement queues are not beingdumped, this parameter has no affect on the system.

• TC_CURSOR_STAT

Dumps basic operational information about the efficiency of the configuration tothe system log file. It can also be used to enable extensive SQL statement poolvalidation. This variable is a bit mapped variable that accepts multiple values.The following are four configuration examples for dumping all information atserver termination:

TC_CURSOR_STAT = 1 256 512 1024TC_CURSOR_STAT = 1793TC_CURSOR_STAT = 0x0001 0x0100 0x0200 0x0400TC_CURSOR_STAT = 0x0701



• TC_LOCALIZATION_DIR

Defines the localization to be used by the TextServer process. It is replacedby the nlsDefaultLang function, which checks the locale used by the servermachine 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 ofTeamcenter or Engineering Process Management, there are several changes youneed to know about.

• Starting in Teamcenter 2007, the beginning of package names changed fromcom.ugsolutions to com.teamcenter. In addition, the term iman in packagenames was removed. In most instances, the term rac replaced it.

• Starting in Teamcenter 2007, the packages are contained in Eclipse plug-insinstead of the portal.jar file.

• Starting in Teamcenter 2007, the term IMAN in class names was changed inmost instances to TC.

• Starting in Teamcenter 8, classes withMenuBar or ToolBar in the name areno longer used.

For example, the AbstractIMANApplication class in thecom.ugsolutions.iman.common package in Teamcenter Engineering2005 is the AbstractTCApplication class in the com.teamcenter.rac.commonpackage in the com.teamcenter.rac.common.jar plug-in in Teamcenter 8.

For more specific information about the changes in the packages, plug-ins, andclasses since Teamcenter Engineering 2005, contact GTAC to obtain a detailedspreadsheet.


Chapter

2 What’s new for Teamcenter 8

New Teamcenter applications and solutions . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

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

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

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

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


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

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

Managing changes and workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Workflow participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Failure paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Classifying data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Multi-unit support in Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37

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

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

Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Structure clone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Teamcenter 8 Release Bulletin PLM00001 C

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

Managing Mechatronics data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47Wiring harness options and variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47Embedded Software Design Data Management . . . . . . . . . . . . . . . . . . . . 2-47

Visualizing products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48General enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48New SOA-based visualization integration . . . . . . . . . . . . . . . . . . . . . 2-48Lifecycle Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-492D and 3D thumbnail previews . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49.vfz collaboration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50Enhanced work session support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50Session attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-503D PMI enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50Improved product structure loading . . . . . . . . . . . . . . . . . . . . . . . . . 2-51Improved rendering when generating 2D images from 3D views . . . . . 2-513D snapshot improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-51

2D improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-513D improvements for Standard, Professional, and Mockup . . . . . . . . . . . . 2-52Markup and callout enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52Enhanced support for NX advanced assembly functionality . . . . . . . . . 2-53Enhancement for displaying attributes and PMI . . . . . . . . . . . . . . . . 2-53Part report enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54

3D improvements for Professional and Mockup . . . . . . . . . . . . . . . . . . . . 2-54New Direct Model-based swept volumes . . . . . . . . . . . . . . . . . . . . . . 2-54Key change in navigation explore mode . . . . . . . . . . . . . . . . . . . . . . . 2-54

Enhancements for ECAD Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55Working with schematic documents . . . . . . . . . . . . . . . . . . . . . . . . . 2-55Cross probing PCB and schematic documents . . . . . . . . . . . . . . . . . . 2-55Net and page connector navigation . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55PCB measurement markups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55Design for Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56ECAD reporting capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56Printing ECAD documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56

Enhancements for ClearanceDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56

Managing CAE data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57CAE Manager – Inspector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Enhanced simulation process launch . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57Launch simulation process remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58

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


Managing quality data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-60DPV Help included in Teamcenter Help collection . . . . . . . . . . . . . . . . . . 2-60

Managing Maintenance, Repair, and Overhaul data . . . . . . . . . . . . . . . . . . . . 2-61As-Built Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61

Customizing Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62Service-oriented architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62New Workflow operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62Feature enhancements in SOA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62New operation for Teamcenter Publish . . . . . . . . . . . . . . . . . . . . . . . 2-63WSDL support in Teamcenter services . . . . . . . . . . . . . . . . . . . . . . . 2-63Alternate ID support for NX Integration . . . . . . . . . . . . . . . . . . . . . . 2-63Occurrence override support for NX Integration . . . . . . . . . . . . . . . . . 2-64Support for adding objects to projects . . . . . . . . . . . . . . . . . . . . . . . . 2-64CAM support for NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64Miscellaneous new services for the NX Integration . . . . . . . . . . . . . . . 2-65Support for features in the NX Integration . . . . . . . . . . . . . . . . . . . . 2-65Baselines for the NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66Lifecycle Visualization product structure loading performanceimprovements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66New change management service . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66

Rich client debugging tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67Teamcenter supports UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67

Teamcenter industry solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68Parts list management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68Owning organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69Enhanced naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69Revision naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69Sample program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-69Properties on relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70Program-level security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70

Consumer Packaged Goods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71Package and brand management . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71Interspec integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71Specification Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72

Performing integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73Teamcenter Gateway for Electronic Design Automation (EDA) . . . . . . . . . 2-73Managing part library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73Support for Mentor Graphics PADS . . . . . . . . . . . . . . . . . . . . . . . . . 2-73Support for OrRCAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73SOA communication layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-73Teamcenter Gateway for EDA client logging . . . . . . . . . . . . . . . . . . . 2-74Teamcenter Gateway for EDA application . . . . . . . . . . . . . . . . . . . . . 2-74

NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75Managing NX Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75NX/requirements integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75

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


Repeating tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77Load balancing based on CPU usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77See 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 documentationInstalling TeamcenterConfiguring TeamcenterAdministering TeamcenterUsing Teamcenter interfacesManaging changes and workflowsClassifying dataManaging documents, reports, requirements, and schedulesSharing dataManaging product structuresManaging manufacturing dataManaging Mechatronics dataVisualizing productsManaging CAE dataRepeatable Digital ValidationManaging quality dataManaging Maintenance, Repair, and Overhaul dataCustomizing TeamcenterTeamcenter industry solutionsPerforming integrationsManaging translations

New Teamcenter applications and solutionsSeveral new applications are available in Teamcenter 8. For each of these, thereis 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 documentationThe following are new documentation features in Teamcenter 8.

New Teamcenter documentation

The following table lists new Teamcenter documentation deliverables in Teamcenter8.

Name Description

Frequently AskedQuestions

Discusses commonly asked questions aboutTeamcenter. Links throughout the answers guide youto further information within the Teamcenter 8 HelpLibrary.

Upgrade Guide Provides instructions for upgrading to Teamcenter 8from the following Teamcenter versions:

• Teamcenter Engineering 9.1.3

• Teamcenter Engineering 2005

• Teamcenter Engineering 2005 SR1

• Teamcenter 2007

Teamcenter EnvironmentManager Help

Provides all the online help text that is displayedwhen using the Teamcenter Environment Manager(TEM) user interface, organized for reference fromthe Teamcenter 8 Help Library.

Client for Microsoft OfficeGuide

Teamcenter’s Client for Microsoft Office givesusers access to Teamcenter objects directly throughMicrosoft Office Word, Excel, PowerPoint, andOutlook. Users can navigate Teamcenter, display andinsert Teamcenter data, and interact with that datawithout running a Teamcenter client.

Content Management:

• Content ManagementGuide

• Content ManagementAdministration Guide

Set of guides that support your tasks using theContent Management feature. Content Managementis a single source publishing system for the creationof technical documentation. Technical publicationsmaintained in the system consist of objects, calledtopics, and their relationships, which are stored inthe Teamcenter database along with any associatedgraphics used in the publications.


What’s new for Teamcenter 8

Name Description

Teamcenter’s LifecycleVisualization:

• Getting Started withProduct Visualization

• Working with 3DModels

• Working with 2DImages

• Using the ECADViewer

• ECAD QuickTour

Set of guides that support your tasks using LifecycleVisualization.

Tecnomatix DimensionalPlanning and Validation:

• Getting Started withDimensional Planningand Validation

• Dimensional Planningand ValidationAdministration Guide

Set of guides that support your tasks using theTecnomatix Dimensional Planning and Validation(DPV) product. DPV enables the extended enterpriseto collect, manage, dimensionally analyze, and reporton quality measurement information.

As-Built Manager Guide As-Built Manager is the first of a series of capabilitiesfor managing Maintenance, Repair, and Overhaul(MRO) processes and is a separately licensedapplication that is installed as an optional overlayon top of the standard Teamcenter product.This application allows you to manage theas-built configuration of an asset realized from aproduct definition structure, such as a design ormanufacturing structure.

C++ API Reference (HTMLonly)

Provides Doxygen metamodel documentation forTeamcenter developers. The C++ API Referencecontains C++ API documentation for the Foundationtemplate only.

Thin Client CustomizationProgrammer’s Guide

Describes the inner workings of the thin client andways Teamcenter programmers can extend or changeits functionality.

Getting Started withAerospace and Defense

Aerospace and Defense provides a data modeltemplate that supports the aerospace and defensemanufacturing industry.

Getting Started withConsumer Packaged Goods

Consumer Packaged Goods provides a data modeltemplate that supports customers who manufactureconsumer packaged goods, for example, detergentsor beverages.



Name Description

Specification ManagerGuide

The Specification Manager application allows you toview and work with specifications. In the ConsumerPackaged Goods and food and beverage industries,specifications capture the complete definition ofproducts and how to manufacture them. Thesespecifications are developed, reviewed, and eventuallyapproved, which drives the product release process.

Services Reference Teamcenter Services Reference providesdocumentation on APIs for services and operations;it supplements the Services Guide deliverable in theTeamcenter 8 Help Library.

Renamed Teamcenter documentation

The following table lists renamed Teamcenter documentation deliverables inTeamcenter 8.

New title Previous title

What’s New for Teamcenter8

Release Highlights

Getting Started withTeamcenter

Getting Started with Teamcenter 2007

Getting Started withElectronic (EDA) LifecycleManagement

EDA Integration Guide

Getting Started withDispatcher (TranslationManagement)

Getting Started with Translation Management

Installation on UNIX,Linux, and MacintoshClients Guide

Installing UNIX and Linux Client Guide

Dispatcher ServerInstallation Guide

Translation Solution Toolkit Installation Guide

Dispatcher ServerTranslators ReferenceGuide

Translation Solution Toolkit Translators ReferenceGuide.

Validation Manager Guide Validation Guide

Rich Client Interface Guide My Teamcenter Guide

Extensions for MicrosoftOffice Guide

Teamcenter Extensions for Microsoft Office Guide

Microsoft Office Guide

• Integration forMicrosoft Office Guide

• Network Folders Guide

Teamcenter Integrations for Microsoft Office Guide

Microsoft Office and Network Folders Guide.



New title Previous title

Change Viewer Guide Change Management Guide

Data Exchange Guide Teamcenter Data Exchange Guide

Gateway for OracleManufacturingConfiguration Guide

Teamcenter Gateway for Oracle ManufacturingConfiguration Guide

Gateway for OracleManufacturing Guide

Teamcenter Gateway for Oracle Manufacturing Guide

Multi-Structure ManagerGuide

Collaboration Context Guide

Structure Manager Guide Product Structure Editor (PSE)

Plant Designer Guide Factory Structure Editor (FSE) Guide

Manufacturing ProcessPlanner Guide

Manufacturing Structure Editor (MSE) Guide

Embedded SoftwareSolutions Guide

Embedded Software Manager Guide

Teamcenter help for MS Office integrations available from within MSOffice interface

For customers who purchase Client for Office, you can access help for the Teamcenterfeatures from within the MS Office interface. Click the Help button on theTeamcenter 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 alink where you can provide feedback about the documentation. Previously, thisfunctionality was offered by way of the Feedback icon in the help interface. SiemensPLM 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 associatedPDF file.



Installing TeamcenterThe following are new Teamcenter installation features.

Teamcenter 8 software distributed in multiple ZIP files

Teamcenter 8 software distribution images can contain multiple ZIP files. Forexample, the software distribution image for Windows consists of two filesnamed Tc8_win_1_of_2.zip and Tc8_win_2_of_2.zip. If you download softwaredistribution images for Teamcenter 8, you must download all files in the set to obtainthe complete image. After you download files, extract all ZIP files to a commondirectory to assemble the image before you begin installation.

For more information about installing Teamcenter 8, see the appropriate Teamcenterinstallation 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 theInstallation on UNIX, Linux, and Macintosh Clients Guide.

Note

Teamcenter 8 supports only 64-bit Intel Macintosh processors. G4 and G5processors 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-UXplatforms.

For information about installing Teamcenter rich clients, see the appropriateTeamcenter 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 youuse Oracle as your RDBMS, Teamcenter Environment Manager (TEM) verifies yourOracle version during installation. If your Oracle server does not meet the minimumrequired version (10.2.0.1), TEM does not install Teamcenter 8.

For more information about installing a database server for Teamcenter 8, see theappropriate Teamcenter installation guide (for Windows or UNIX/Linux).

For information about supported database servers for Teamcenter 8, see the SiemensPLM 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 applicationservers, Web servers, and Web browsers. For the latest supported versions, seethe information available on the Web at:


For information about deploying Teamcenter Web applications, see the WebApplication 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 supportfor Microsoft Word 2007, Excel 2007, and PowerPoint 2007 files. These filesuse extensions docx, xlsx, and pptx, respectively, and are represented withinTeamcenter asMSWordX,MSExcelX, andMSPowerPointX types.

For information about installing the full-text search feature, see the appropriateTeamcenter 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 andensures the total number of active authors and consumers in the system is alwaysless than or equal to the number of author/consumer licenses purchased.

There are two levels of Teamcenter user licenses that correspond to the differentroles within a company:

• Author is a user that creates or modifies data for product and processinformation.

• Consumer is a user that views, approves, rejects, or comments on product andprocess information.

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



Configuring TeamcenterThe 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 ishandled. 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 forevery item revision business object for which you want standardized behavior.

Administrators use the Business Modeler IDE to create IRDCs. In the Extensionsview 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 richclient, see the Rich Client Interface Guide.

Alternate ID enhancements

Alternate identifiers store information, such as part numbers and attributes, aboutthe same part from different perspectives. Alternate ID rules govern how alternateIDs 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 allof 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 foralternate 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 replacedby alias ID rules. If you have ever used Alias business objects, you mustmigrate Alias business objects to the new Identifier business objects beforeupgrading to Teamcenter 8.

For more information about alias ID rules, see the Business Modeler IDEGuide.



Building and packaging C++ customization code from the Business Modeler IDE

Previously, for each new business object and operation, the majority of code in theC/C++ layer was standard boilerplate code that was written manually. There is nowa mechanism to autogenerate all the boilerplate code. Users of the Business ModelerIDE can simply create operations on business objects, and the Business Modeler IDEautogenerates boiler plate code. Users can concentrate on writing their businesslogic implementations in the generated C/C++ files.

A new Code Generation folder in the Business Modeler IDE contains the followingdata 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 manualthat 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. Thisframework provides the capability to define C++ interface/API for each businessobject, paving the way for true object-oriented benefits such as inheritance as well asoverriding of operations. Existing code is refactored in Teamcenter 8 to conform tothe new framework. The refactoring does the following:

• Changes all the business object classes to fit into the new metamodel frameworkparadigm

• 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. Tocreate the code that uses the new framework, right-click a project in the BusinessModeler IDE and choose Generate Code.




More consistent business rules inheritance

Object-oriented inheritance of business rules is enhanced. Business rules are definedin 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 theBusiness Modeler IDE user interface. For example, this feature provides a newGRM Rules tab on business objects. To access the new GRM Rules tab, right-clicka business object in the Business Objects view, choose Open, and click the GRMRules 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 thebusiness 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. Whenyou define operations, you can activate extension points such as pre/post methods.

After you define a service, the boilerplate is generated automatically. The only taskremaining is to implement the behavior, and that is simplified by providing operationoutlines to start with. Once the service implementation is complete, you can startthe 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 becopied when a user performs a save as or revise operation on an item revision. InTeamcenter 8, deep copy rules are enhanced to support defining condition-basedrules, to propagate relations when the secondary side item revision is revised orsaved, and to revise automatically the related item revision objects.

You can configure deep copy rules in the Business Modeler IDE by right-clicking anItem 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 andsave as operations of an ItemRevision were hard coded. They are now exposed inthe Foundation template as explicit deep copy rules on the ItemRevision businessobject. This allows you to override the default deep copy behavior. Previously,the save as operation on an item object carried forward only certain relations ofthe item revision. In Teamcenter 8, when a save as operation is performed on anitem object, the old item revision relations are carried forward based on the deepcopy rules in the database. Therefore, the deep copy rules in the database are thedeciding factor for copying relations even during save as operation on an item. Oneexception is that when a deep copy rule specifies the Copy As Object action andthe other side object to be copied is an item revision, the system always performsthe Copy As Reference action.


Addition of conditions to Teamcenter

Conditions are statements that resolve to true or false. Conditions can be usedto evaluate business objects or user sessions to deliver only certain results. TheTeamcenter condition engine utilizes the CLIPS (C Language Integrated ProductionSystem) 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, andso on, and the properties on those objects. Using the CreateDescriptor tab in theBusiness Modeler IDE, customers can make properties on items required as well asvisible 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 itemssuch that they are auto-exposed in the creation dialog boxes in the rich client andthin 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 tothe first pattern in the naming rule. The Item create dialog box in the rich clientis enhanced to present the user with a list of patterns with defined counters in thenaming rule attached to the item_id property. The next item ID is generated perthe selected pattern in the list.

This feature can be used to define auto-numbering rules with multiple patterns for agiven object in the context of a program.

For more information, see the Business Modeler IDE Guide and Getting Started withAerospace and Defense.

Revision naming rules

Administrators can define revision naming rules with initial, secondary, andsupplemental 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 withthe next set of revision options as specified in the revision naming rule attached tothe item_revision_id property.


Mapping Designer support for MapForce 2008

The Mapping Designer is an application that administrators use to map data modelfrom one product lifecycle management (PLM) system to another, for example,Enterprise Knowledge Management to Teamcenter, or Teamcenter to EnterpriseKnowledge Management.

The Teamcenter Mapping Designer supports MapForce 2008 and the MapForce2008 Eclipse plug-in.

For directions about how to install MapForce 2008, see the Business Modeler IDEGuide.

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 TeamcenterThe following are new Teamcenter administration features.

User access logging

User access logging records information from failed authentication attempts fornamed users, allowing administrators to analyze failed attempts.

The user_auth_audit command line utility configures (adds users to User AccessLogging 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 uploadtimes from clients by uploading files to a temporary volume. Users can continue towork on their files from the temporary location. The system moves the files to itsfinal destination according to administer-defined criteria. Files are accessible toFMS 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 longerthan desired. Store and forward functionality allows you to define a default localvolume (an initial upload volume) for users or groups. When users upload files,they are temporarily uploaded to the defined initial FMS volume, returning controlto the user in the client. In the background, the files are transferred to the finaldestination volume. This allows you to place an FMS volume on the remote usersLAN, ensuring quick uploads into the FMS of this temporary volume. All filetransfers 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_Forwardsite 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 (TranslationManagement).



Accessing multiple FMS databases through a single FCC

You can access multiple File Management System (FMS) databases through a singleFMS client cache (FCC). Teamcenter supports multiple installations on the samemachine to access multiple Teamcenter site IDs (databases).

For example, consider a part supplier with multiple customers, requiring access toeach customer’s PLM data, where the customers are in direct competition with eachother. The part supplier’s FCC loads configuration information from its local fcc.xmlfile on startup. Its FCC also downloads configuration information from the primarysite. Using these two sources of configuration information, the FCC determines fromwhich 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 multipledatabases by including valid configuration elements referencing at least oneparent FSC that supports each of the other databases to which the client mayconnect.

For more information about configuration examples, see the SystemAdministration Guide.

• The proper multisite FCC client configuration must be present in theFMS_HOME directory from which the FCC is started. Siemens PLM Softwarerecommends that you use a single FMS_HOME environment variable setting topoint to the combined configuration.

• FSC servers for all databases must be online, properly configured, of the properversion, and functional.

For more information about accessing multiple FMS databases through a singleFCC, see the System Administration Guide.



Automatic FCC reconfiguration

FMS client caches (FCCs) now detect changes to the master configuration file. Whenyou reconfigure the master configuration file, the changes are propagated throughall necessary FMS server caches (FSCs), both masters and slaves. Then the FCCdetects the changes and attempts to reconfigure itself, without user interaction orinterruption of FCC client application service.

Note

Some FCCDefaults parameters still require manually restarting the FCC. Ifthe reconfiguration attempt fails, the traditional method of shutting down allFile Management System (FMS) applications and running fccstat –restartupdates these changes.

For more information about which parameters require a manual restart of theFCC, see the System Administration Guide.

No administrative interaction is required for automatic FCC reconfiguration. FCCreconfiguration events are recorded in the FCC log file. The fccstat utility is storedin the FMS_HOME/bin directory.

For more information about automatically reconfiguring the FCC, see the SystemAdministration Guide.

Manual FCC reconfiguration

The FMS client cache (FCC) now attempts to update its configuration file when yourun fccstat –reconfig. This method is useful for activating changes to the fcc.xmlfile without shutting down Teamcenter or other FCC client applications, and withoutstopping and restarting the FCC.

Note

Some FCCDefaults parameters still require manually restarting the FCC. Ifthe reconfiguration attempt fails, the traditional method of shutting down allFile Management System (FMS) applications and running fccstat —restartupdates these changes.

For more information about which parameters require a manual restart of theFCC, see the System Administration Guide.

The fcc.xml file is located in the FMS_HOME directory. The fccstat utility is storedin the FMS_HOME/bin directory.

For more information about manually reconfiguring the FCC, see the SystemAdministration Guide.



Performing hot backup

Teamcenter’s integrated backup and recovery functionality allows you to usethird-party backup systems to perform hot backups, enabling Teamcenter to operatecontinually in a 24x7 environment. Use this functionality to back up and/or restoremetadata and math data.

During hot backup, third-party backup systems require the Teamcenter filesystem (volumes) and the Teamcenter database to be synchronized. Run thebackup_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 canstore in-process data until production volumes are backed up. Use normal mode torestore Teamcenter to normal, write access, mode.

Note

The backup and recovery functionality has been available since TeamcenterEngineering 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-onlymode. This behavior is corrected in Teamcenter 2007.1 MP3.

The –f=move, –f=remove, –m=caution, –f=allcnt and –force arguments areremoved from the backup_modes utility. This functionality is now performedthrough 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 EnvironmentVariables Reference.

Additionally, the blobbyVolume_NT preference and the blobbyVolume_UNXpreference are modified. The preferences are stored only in the tc_preferences.xmlfile. They are no longer also stored in the tcfs_preferences.xml file, therefore, thepreference values do not need to be synchronized between the two XML files. Thevalid value for these preferences is a single string specifying the alternate volumelocation. The maximum character length of this string is increased from 15 to 32characters.

For more information about these two preferences, see the Preferences andEnvironment Variables Reference.



Locking site preferences

You can lock site preferences before modifying them. To ensure multiple siteadministrators do not make simultaneous changes to site preferences (overwritingeach others settings) a Lock and Unlock button has been added to the Optionsdialog box, allowing you to lock site preferences before modification.

To lock site preferences, click Edit→Options to access the dialog box. The lockbuttons appear on the Index and Search tabs of the dialog box.

For more information about locking site preferences, see Getting Started withTeamcenter.

Shared memory for site preferences

Shared memory for site preferences is available in a four-tier configuration. Thisfunctionality is implemented by default.

This shared memory functionality connects all Teamcenter servers for a particularversion to the shared memory created by the first Teamcenter server. A backingstore file is created with a .mem extension. The backing store file contains datafor preferences definitions, site preference off-the-shelf values, and site preferenceoverlay values. If the file is deleted, another is automatically created by the nextTeamcenter 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-tierconfiguration immediately affect all existing Teamcenter server processes on a host.

Note

When changes are made from a different host using the same database, thechanges are updated on that host, but not on the first host. The next newTeamcenter server processes begun on the first host updates the sharedmemory segment and the changes affect all the processes on that host.

For more information about shared memory for site preferences, see the SystemAdministration Guide.



Rendition and translation capabilities

Rendition and translation capabilities are available for Document Revision andDataset objects in Teamcenter. Microsoft Office dataset types such as MSWord,MSExcel, MSPowerPoint and MSProject can be translated to a variety of otherderived 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 aDocument 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, isspecified by the item revision definition configuration (IRDC) object associatedwith 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 onthe input file format and desired translated output file format.

When you select a dataset to translate on-demand, the file associated with thedataset is translated. The translated file format is determined by the Dispatchertranslation 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 thetranslated file such as moving files from the translation server to the Teamcentervolume and creating the relationship between the Document Revision or thesource 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 theDispatcher service configuration and IRDC objects.

• For information about creating IRDC objects, see the Business Modeler IDEGuide.

• For information about Dispatcher service configuration, see the BusinessModeler IDE Guide.

For information about working with document management and IRDCs in the richclient, see the Rich Client Interface Guide.



Site definition improvements

Teamcenter 8 adds and updates the site definition pane used to define a site toclarify the use of the information as it applies to RPC or HTTP enabled sites. Thesite definition pane includes the following new or updated boxes:

• Site Node

Stores the node value Multi-Site Collaboration uses for remote calls in RPCmode. Prior to Teamcenter 8, this field stored the node name as well as theURL for SOA calls based on whether this site was used for standard Multi-SiteCollaboration or HTTP enabled Multi-Site.

• SOA URL

Stores the URL for SOA calls to this site. The URL is used for HTTP enabledMulti-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 sitecheck box allows master objects which have been replicated to the site to be deletedeven 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 GlobalServices (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 basedon the validation rule set.

The Validation Manager administrative user (Teamcenter user with ValidationManager administrator’s role) can perform validation rule set management tasksincluding:

• Create

• Modify

• Delete rule set and rules

The Validation Manager user can start validation with the enhanced capabilitiesof selecting items, item revisions, folders, dataset types, and checkers as well asvalidation rule sets. The Validation Manager utility is started from the rich client sothe user can monitor when the process finishes. The View Result pane is enhancedwith features to allow the user to evaluate the validation results based on validationrule 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. TheValidation Manager administrator’s role is added and can be deployed duringinstallation or upgrade. Users with the administrator’s role can perform validationdata and validation rule set management tasks. A simple and straightforwardmessage is shown from workflow or baseline operations to inform the user whichparts failed which checks and for what reason. The EPM_check_RDDV_resultsworkflow rule handler checks RDDV results and returns EPM_go if compound resultstatus 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 theValidation 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 choosingan Excel template to associate with the objects. The data specified in the template isextracted from the Teamcenter database to a new Excel spreadsheet.

Note

The user can choose to export the data in the property columns that arecurrently displayed in the view. A template is not associated with thisoperation.

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 isapplied to the data, and boilerplate text and graphics. Also, a template can containVisual Basic macros that users can run from the generated spreadsheet.

A default template is provided. The Teamcenter administrator can modify thedefault template and can create custom templates.

Note

• Users can choose Excel templates when exporting data from both the richclient and the thin client.

• Administrative actions in configuring export templates, such as creating,importing, modifying, copying, and deleting templates, can be done only inthe 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 followingmust be installed on the user’s computer:

• Microsoft Office Excel 2007

• Microsoft Office Excel 2003 with the Compatibility Pack for the Word, Excel, andPowerPoint 2007 file formats

For more information about exporting objects to a new live Excel file, see theExtensions for Microsoft Office Guide.

For more information about configuring export templates, see the ApplicationAdministration Guide.



Templates for document export

Export template functionality supports exporting Teamcenter object data toMicrosoft Office Word.

Export templates let the administrator customize the export process using twotemplate types:

• A specification export template determines which objects to export, theirstructure 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 tableof contents, and headers and footers.

• An object export template determines the properties that are exported for theobjects. This template can also contain standard text, or boilerplate, in whichproperty values can be inserted.

The administrator can create, import, modify, copy, and delete templates. Theseadministrative actions on templates are performed in My Teamcenter in theTeamcenter rich client. Administrators can create use the Business Modeler IDEto create item revision definition configuration (IRDC) objects. Then IRDC objectscan associate default templates with the following Specification and Specificationelement business objects and their subtypes. In a given export operation, the usercan select a different set of templates to override IRDC associations.

For more information about configuring export templates, see the ApplicationAdministration Guide.



Content Management administration

Content Management is a single-source publishing application used to createtechnical documentation using SGML and XML information stored in a Teamcenterdatabase.

The Content Management rich client provides both the Content and Administrationperspectives, which are used for authoring and administrative tasks respectively.The Administration perspective enables you to create the following so that theapplication can be used for authoring publications:

• Schema objects. You can create your own schemas or DTDs or use the S1000Dstandard, which is an optional component of Content Management.

• Topic and publication types and publication structures, which are related toschemas.

• XML attribute mappings to facilitate the transfer of topic attributes from thedatabase 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 selectionby the user.

• Translation objects necessary to manage the translations of publications andtopics.

• Graphic priority lists used to determine the priority with which graphic optionsor formats are selected for use with XML content when it is opened with anediting application or rendered by a publishing application.

• Other objects, including procedures, composition policy tables, transformationpolicies, and graphic attribute mappings.

Sample files are provided for these objects and also for some samplecontent. 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_datadirectories.

For more information, see the Content Management Administration Guide.



Security Services WebSEAL proxy support

WebSEAL processes form-based challenges for Teamcenter clients and providesclients with an authorized WebSEAL session cookie. This allows the client tocontinue operations without processing additional form-based authenticationchallenges from WebSEAL.

Security Services shares its authorized WebSEAL junction cookie with client-sideTeamcenter applications that are facing a form-based authentication challenge fromWebSEAL. Providing the authenticated WebSEAL session cookie from the SecurityServices session allows the Teamcenter application to share the authorization in thesession 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 tothe WebSEAL form-based authentication challenge. After authentication, SecurityServices is provisioned with an authorized WebSEAL session cookie.

This feature only works with the WebSEAL forms authentication mechanism andthe following global WebSEAL stanzas declarations:

ssl-id-sessions=notcp-session-cookie-name=PD-H-SESSIONssl-session-cookie-name=PD-S-SESSION

In addition, the WebSEAL junction protecting the Security Services Login Servicemust be configured to pass the WebSEAL session cookie the Security ServicesLogin Service servlet.

Note

The Integration for CATIA 6.7.2 and Integration for Pro/ENGINEER 5.7.3are supported with WebSEAL. Support for other CAD integrations will beadded 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 aWebSEAL proxy server with FMS clients in the field at service offices or at supplieroffices.

FMS clients automatically detect and respond to forms authentication challengesfrom the WebSEAL proxy, provide the required WebSEAL session cookie, andmaintain the network connections to the backoffice FSC server. The FMS clientsthat support this feature are Java based interactive clients such as the Java FCCand the UploadApplet (Web client).

This feature only works with the WebSEAL forms authentication mechanism.

FMS clients interoperate with the Security Services integration to share requiredWebSEAL session cookies that maintain the connection through WebSEAL tobackend FSC servers. This feature utilizes WebSEAL forms authentication tonegotiate credentials authentication. After a Teamcenter application on the user’sworkstation negotiates the WebSEAL authentication, the follow-on Teamcenterapplications 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 inHTTP messages.

FMS provides path extensions to simplify configuration of reverse proxies to properlyroute FMS traffic to backend FMS server caches (FSCs).

The original FMS URL contextless form (protocol://host:port) only provided the hostname, address, and listening port number.

The new URL form consists of a standard URL path based on FMS configurationvalues, such as fmsenterpriseid, fscgroupid, and fscid. This additional pathinformation provides reverse proxy servers an easy method of mapping to FSCsbehind the firewall based on the incoming FMS URL path. These maps are explicitlyconfigured 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 suitablefor 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 inreverse 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 internallyby the system. Administrators should not have to manage FMS URLs that arethis 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 requiretwo-way authentication. This ensures that only clients with certificates that can beauthorized by the FSC servers can connect.

Two-way SSL protects an FSC connection by only allowing clients that are configuredwith 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 toeach other. This provides symmetric authentication between the FSCs and ensuresthat only FSCs that are configured with appropriate certificates can communicatewith each other. All other connection requests are denied.




Using Teamcenter interfacesThe 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, includingsupport 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 ClientInterface Guide and the Thin Client Interface Guide.

For more information about viewing vendor parts associated with commercial partsin 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 meansthe 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 ManagerGuide.



Teamcenter rich client perspectives and views

Within the Teamcenter rich client user interface, functionality is providedin perspectives and views. Use perspectives and views to rearrange how thefunctionality is presented.

Perspectives Are containers for a set of views and editors that exist within theperspective.

• A perspective exists in a window along with any number ofother perspectives, but only one perspective can be displayedat a time.

• You can add and rearrange views to display multiple sets ofinformation simultaneously within a perspective.

• You can save a rearranged perspective with the current name,or create a new perspective by saving the new arrangement ofviews with a new name.

Views Enable you to navigate a hierarchy of information, displayinformation about selected objects, open an editor, or displayproperties.

• Views that work with related information typically react toselection changes in other views.

• Changes to data made in a view can be saved immediately.

• Any view can be opened in any perspective, and anycombination of views can be saved in a current perspectiveor in a new perspective.

Note

If your site has online help installed, you can access application and viewhelp from the rich client Help menu or by pressing F1. Some views, such asCommunication Monitor, Print Object, Outline, Palette, and Progress, arenot specifically associated with a particular perspective.

For additional information about unassociated views, see the Rich ClientCustomization Programmer’s Guide.

For more information about perspectives and views and changing the layout of yourrich client window, see the Rich Client Interface Guide.



My Teamcenter functionality refactored

The functionality for finding, creating, and viewing data in the rich client issupported by perspectives and views, with each application consisting of a singleperspective that by default displays one or more views:

• The My Teamcenter application lets you navigate, browse, and work with yourdata in Summary, Details, Impact Analysis, and Viewer views.

• The Relation Browser application lets you navigate through the relations on anobject in terms of predecessors and successors in a hierarchy. The default viewsprovided by the Relation Browser perspective include the Relation Browserview, the Image Thumbnail Preview view, the Graph Overview view, and theProperties view.

• The My Teamcenter (2007) application, which is deprecated in the currentrelease, 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 Resultsview in all perspectives except the My Teamcenter (2007) perspective.

Note

The My Teamcenter Guide from previous versions is now the Rich ClientInterface Guide. This guide has been expanded to describe both theMy Teamcenter and My Teamcenter (2007) perspectives, as well as theRelation Browser application perspective, and a broad range of features andfunctionality available in these contexts.

For additional information about using the My Teamcenter, Relation Browser, andMy 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 InterfaceGuide.

For information about using search in the thin client, see the Thin Client InterfaceGuide.

Note

Search in My Teamcenter (2007) does not display a progress dialog and doesnot support cancel functionality.



Search for items by owning organization

You can search for items based on the owning organization in My Teamcenter. TheOwning Organization ID option is added to the Item search form. Your currentorganization 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 thelocale used by the Teamcenter server pool manager. The only constraints are thatrequested locales are properly installed on the server side (which may not be truefor customized locales), and that the server side system can cope with the localeencoding (the locale is supported by the encoding on the server machine and thelocale 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 themachine where the rich client was running, the locale defined at middle-tierinstallation, and the server locale specified by the TC_language_defaultenvironment variable located in the tc_profilevars file. All processes in apool manager used the same tc_profilevars file, and therefore the samelanguage. Therefore, in a globally distributed enterprise with one poolmanager running on a server machine located in country A with locale L_A,all Teamcenter server processes spawned from the pool manager ran withlocale L_A. Therefore, all client connections were served with only locale L_A.

This feature is enabled by default. Administrators can modify the way multilanguageoperates using the TC_language_default preference to define the default localethe Teamcenter server uses when clients connect without a specified locale. Thissituation can occur on thin client, or SOA clients other than the rich client.Administrators can use the TC_language_data_entry preference to define thelist of locales in which users may input data entries. The value of this preferenceis left empty by default. If no value is entered, a warning message displays after auser logs into rich client or thin client when the requested locale conflicts with thedatabase encoding. (This conflict could result in loss of data if the data is entered inthe wrong locale.) If values have been entered, a warning message always displaysafter a user logs into rich client or thin client, stating that data must be enteredusing 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 8Properties dialog box.

For more information, see the Rich Client Interface Guide.

• From the thin client, users can define their language choice either in thebrowser’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 ClientInterface Guide.

Microsoft Office client

Teamcenter’s Client for Microsoft Office is embedded in Microsoft Office applicationsand is independent of the Teamcenter rich client and thin client. Client for Officeconsists of specialized Teamcenter views in Office applications. Users can displaythe views by clicking buttons on the Teamcenter ribbon. Client for Office gives usersaccess to Teamcenter directly from Word, Excel, PowerPoint, and Outlook. Users cannavigate Teamcenter, display and insert Teamcenter data, and interact with thatdata 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 otherOffice documents.

• In Outlook, save e-mail to Teamcenter and compose Outlook messages containingTeamcenter data.



Client for Office can be installed with the four-tier Teamcenter rich client orseparately 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 theprimary interop assemblies that does not require access to the Microsoft Officeinstallation media.

• Microsoft .NET Framework 3.5

• Microsoft Visual Studio 2008, Tools for Office runtime, and Tools for theMicrosoft Office System Language Package

• Teamcenter FMS client cache (FCC)

To install the prerequisite applications, the installing user must have administrativeaccess to the local computer. Administrative access is not required to install theembedded client add-in.

For more information about Client for Office, see the Client for Microsoft Office Guide.

Enhancements to Organization and Portfolio, Program and ProjectManagement allow you to find users or projects more quickly

Search fields are added to the Organization application (for selecting from existingusers 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 OrganizationGuide.

For more information about the Organization Group wizard, see the OrganizationGuide.

For more information about searching for existing projects, see the Project Guide.



Managing changes and workflowsThe following are new Change Viewer and Workflow features.

Workflow participants

You can assign participants to an item revision or engineering change revision andconfigure workflow handlers to use those participants when you initiate a workflowprocess on the revision. You can also easily select specific members, all members, orany member of a group. To select the participants to attach to an item revision orengineering change revision, choose the Tools→Assign Participantsmenu 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 InterfaceGuide 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 toaccept values other than fixed numbers.

• auto-assign

Assigns the single responsible_party attribute for a single assignee task. Ifgiven $PROPOSED_RESPONSIBLE_PARTY as an argument, the handlerassigns the user specified for Participants Responsible Party as theresponsible party.

• auto-assign-rest

Modified to have the same incremental behavior as the auto-assign handlerand to support the new –assignee argument.

• CR-assign-team-selector

Modified to have the same incremental behavior as the auto-assign handlerand 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 ofthe 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, andPrepare 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 inthe process template, it must be done at design time.

When you create a workflow, you can configure each path as either a success path ora failure path. A task follows the appropriate path based on the task outcome. Thesuccess path is followed when the task state transitions to Complete or when a taskis promoted and it transitions to a Skipped state. A task is Complete when thetask’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 allerrors or for specified errors. If no error occurs, the process follows the successpath.

• 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 stateis 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 asUnable-to-Complete.

– A manual Condition task is marked as Unable-to-Complete.

– A Validate task encounters an error that the task has been configured torecognize.

• 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 theuser, allowing branching on an arbitrary number of results. The result enteredby the user is displayed on the Condition path line as a string label, indicatingthat 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 resultattribute of the Condition task. This handler sets the results used by theprocess to decide which paths to follow. There is no limit to the number ofcondition paths that can be configured when used in conjunction with theEPM-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, whichmight 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 specifiedpercentage 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 ViewerGuide.

Classifying dataThe following are new Classification application features.

Multi-unit support in Classification

When creating classification classes, you can define whether a class contains onlymetric objects, only nonmetric objects, or both. If you specify that a class can containboth, 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 theobject 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.6centimeters.

Specify whether a class supports multiple units of measurement in the class detailspane in Classification Administration.

Enter attributes in multiple units or search for attribute values of differing units inthe Classification application.

For more information, see the Classification Administration Guide and theClassification Guide.



Managing documents, reports, requirements, and schedulesThe following are new Teamcenter features for reports, requirements, and schedules.

Requirements integration

Users can create a tracelink from a requirement in Requirements Manager to ascheduled task in Schedule Manager. When the task completes, a workflow istriggered to get approval of a signoff team. Users can also check the status on thetarget 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 thatwork on saved query objects. PLM XML closure rules are used for the processingof the saved query objects. For summary reports, a Closure Rule box and a ReportFormat box are added to the Create Report Definition Template dialog box. A ReportFormat 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 assub schedule templates into this schedule template. The new schedule templatebecomes a master schedule template and the inserted schedule templates becomesub schedule templates. The first user to start working on a task (where there ismore than one resource assigned) becomes a privileged user. Users can search andattach any PLM item as a deliverable. The user can also search for particular itemsand attach them as a target deliverable or reference.


Scheduling extensions

Users can create a schedule and insert other schedule as subschedules into thisschedule. The new schedule becomes the master schedule and the inserted schedulesbecome subschedules. When creating a master schedule, a user can import otherschedules as subschedules.

Functionality such as copy/paste, baseline, dependencies, and assignments isincluded. Schedule membership in the master schedule includes all membership insubschedules.

Using Business Modeler IDE, sites can extend schedule and task attributes to addcustom attributes and support all operations that are available to items. Managerscan 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 schedulesand 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 featuresof 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 inthe 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 databaseconnectivity for exported documents.

This feature lets you change object property values in the database by editing thosevalues in the document. Changes are applied in the database when you save theedits 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, theirstructure in the document, and the formatting applied to the objects. Thistemplate can also contain layout elements such as a title page, a table ofcontents, and headers and footers.

• An object export template determines the properties that are exported for theobjects. This template can also contain standard text, or boilerplate, in whichproperties can be inserted.

For more information about exporting objects to Microsoft Office Word, see theRequirements Manager Guide.



Content Management

Content Management is a single-source publishing application used to createtechnical documentation using SGML and XML information stored in theTeamcenter database.

Source is separated into content, structure, and format, so content may be used inmany publications with different structures and media deliverables. The publicationstructures are validated by structure rules called schemas or DTDs. ContentManagement supports many types of schemas, including the S1000D standard, anoptional component of Content Management. The publication layout is implementedwith stylesheets, which allows the same content to be available for different mediasuch as print or Web applications.

Publications are created by composing small subsets of information called datamodules or topics. These may be maintained by the author or other participants inthe product creation process. The content data module or topic may be as small asnecessary for optimum reuse in other publications. They are related to each otherbased on the schema or DTD, which is similar to the table of contents of a book oran online help navigation tree.

Topic and data module relationships may be created and updated in the ContentManagement interface or within an XML/SGML editing tool. Content Managementworks with these editing tools: Altova XMLSpy, Arbortext Epic Editor, structuredFrameMaker, and XMetaL Author.

Additional features of Content Management enable you to:

• Integrate workflows.

• Track publication versions.

• Incorporate graphics into publications from the Teamcenter database. Eachgraphic may be stored in different formats to use for different types of output.

• Manage multiple language versions of publications at the level of the datamodule or topic, to reduce translation costs.

The Content Management rich client provides both the Content and Administrationperspectives, which are used for authoring and administrative tasks respectively.

The Content perspective contains multiple views that can be rearranged, includingcontent and graphics previews, a query browser for searching the database, currentworkspace, structure expansion and editing, a local graphics cache, and object statusinformation. 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 dataThe 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.orgWeb site.

PLM XML performance improvements

You can improve the performance of your PLM XML exports by setting the followingpreference:

• PLMXML_export_packed_bom_<transfer-mode-name>

If you set this preference to TRUE, it improves the PLM XML exportperformance 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 XMLfile with a packed BOM into Teamcenter. Set this preference to TRUE only ifyou plan to use the XML file in a third-party application.

For more information about this preference, see the Preferences and EnvironmentVariables Reference.

Backward compatible schema mapping for extended attributes

Teamcenter 8 introduces a new storage class for each subtype. Multi-SiteCollaboration maps item attributes between Teamcenter 8 and the followingTeamcenter 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 itssubtype (subclasses). Any customizations related to attributes in the master formsfor the earlier Teamcenter product are not imported as the attributes for the mainclass in Teamcenter 8.

For information about sharing data between Teamcenter product versions, see theMulti-Site Collaboration Guide.


http://www.plmxml.org


Global Services Data Exchange solution application server support

The Teamcenter 8 Global Services – Data Exchange Web application solution can bedeployed on the following application servers:

• JBoss

• WebSphere

• WebLogic

For information about versions of application servers certified for the Teamcenter 8Global Services – Data Exchange Web application solution, see the Siemens PLMSoftware Certification Database:


To use the certification database, choose the platform you use and Teamcenter 8, andthen click Show Certifications.

For information about Teamcenter 8 Global Services – Data Exchange, see the DataExchange Guide.

Global Services SOA connection pooling

Global Services supports an option for connectivity through the Global ServicesSOA Connector using pooled connections. Connection pooling reuses TcServerinstances across multiple sessions run by the same named user. This option allowfaster performance and better scalability in situations where a single user is runningmultiple Global Services sessions. This approach is especially valuable for DataExchange environments with large numbers of concurrent transactions.

For information about configuring connection pooling, see the Global ServicesConfiguration Guide.

Global Services Teamcenter 8 rich client connector

Global Services provides a rich client connector for Teamcenter 8 based on the OSGiframework as defined by the OSGi Alliance (formerly know as the Open ServicesGateway initiative). This connector replaces the deprecated Global Services richclient 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, seethe Global Services Configuration Guide.



Managing product structuresThe following are new product structure features.

Structure clone

You can clone an existing product structure to create a new structure, for example, ifthe new product structure is very similar to the existing product structure. As analternative to cloning a structure, you can create a product structure template anduse it as the basis of the new product structure. You can clone the entire productstructure from the top level down, or you can clone a selected subassembly. It is notnecessary to open the CAD tool to create the clone.

The cloning operation uses Business Modeler IDE deep copy rules to determine howdatasets 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 isa part family member and if you choose to include part family masters and partfamily members in the clone.

To create a structure clone, select the desired top level or subassembly in StructureManager and choose Tools→Duplicate. Teamcenter displays the Duplicate dialogbox, allowing you to define display and naming options for the clone.

For more information about the structure clone feature, see the Structure ManagerGuide.

Managing manufacturing dataThe following are new features for managing manufacturing data.

Time management

You can manage and analyze times of process plans in Manufacturing ProcessPlanner. You can store individual times for each activity, or the cumulative timerequired for operations or processes in a process structure. The Time pane providesinformation specific to the process or operation, and allows you to perform a timeanalysis. You can add activities to operations and store individual times for eachactivity. The time analysis calculates total work and total duration of descendents ofa selected process or operation. In addition, it calculates the time required for eachcategory of activity (for example, value-added or nonvalue-added) and portraysthese in a pie chart. Once calculated, you can store the cumulative time requiredfor operations or processes in the process structure. For selected operations, youcan create activities and edit their time data directly in the Activity section of theTime 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 baseimage and markups) but are more than just image captures. You can have one ormany snapshots associated with a BOM line in your product structure. When youselect a BOM line, Teamcenter displays the attached image dataset in the 2D Viewerpane. If there are multiple image datasets attached, you can select the desiredimage dataset. You can:

• Use 2D snapshots to load base images and markups into the 2D viewer andrestore 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 inMulti-Structure Manager or Manufacturing Process Planner.

For more information, see theMulti-Structure Manager Guide or theManufacturingProcess Planner Guide.

Find checked-out objects

You can see a list of objects that you have checked out of the database inManufacturing Process Planner. You can specify that Teamcenter shows you thislist each time you exit, or you can use the Tools→CheckInOut→Find Checked-Outin 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 theselected 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 Planneror Multi-Structure Manager, use the View®Show Unconfigured AssignedOccurrences menu command to show assigned objects that were configured out ofthe structures to which the objects were assigned. Unconfigured variants of assignedobjects are shown in the composition structure when:

• The Show Unconfigured Assigned Occurrences menu command is not checkedin the composition structure and the Show Unconfigured Variants menucommand of the assigned objects is checked.

• The Show Unconfigured Assigned Occurrences menu command is checkedin the composition structure.

Unconfigured variants of assigned objects are not shown in the composition structurewhen:

• The Show Unconfigured Assigned Occurrences menu command is not checkedin the composition structure and the Show Unconfigured Variants menucommand of the assigned objects is not checked.

Note

This command does not automatically refresh. Any changes to the assignedobjects are not reflected in the structure until you execute this command again.

Executing the Show Unconfigured Assigned Occurrences menu command takesthe 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 incrementalchange into consideration. When cloning, Teamcenter handles incremental changesin the following way:

• Incremental changes that are currently effective are merged with the currentlyactive incremental change.

• Incremental changes that are effective in the future are carried forward to thenewly-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 ManufacturingProcess Planner, Multi-Structure Manager, Part Planner, or Plant Designer, thedialog boxes used to create these objects are now based on the standard TeamcenterNew Item dialog boxes that you are familiar with from My Teamcenter or StructureManager.

You create structures from a template (clone structures) using the File→New→FromTemplate menu commands.


Manufacturing preferences in preference hierarchy

You can modify certain manufacturing preferences directly in the preferencehierarchy.

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 thenencrypted for all classes and views where the attribute is used. You cannot searchfor 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 PADprocess level. This pane displays PAD properties and PSD processes directly underthe selected PAD process. You can also create new child MEPSD items using thisnew pane.

Note

MEPAD and MEPSD items types are only available if you install the GMOverlay.

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 parentMEPAD item from the PAD user interface at theMEPSD process item.

Note

The functionality to create a new MEPSD item from the existing PAD userinterface has been moved to the new PAD user interface at the MEPADprocess item level.


Managing Mechatronics dataThe following are new features for Mechatronics Process Management.

Wiring harness options and variants

The wire harness integration framework now allows users to exchange data (optionsand variants) with ECAD and MCAD applications. It also provides SOA servicesthat help users publish, retrieve, and edit the wire harness structure.

For more information about options and variants, see the Wiring Harness DesignTools Integration Guide.

Embedded Software Design Data Management

The Embedded Software Design Data Management functionality helps users managedesign data (source code, object files, third party libraries) of embedded softwarecomponents. Users can create, update, and delete software design data components.They can also define dependencies and associate specifications, source code, testcases to software design data component.

For more information about working with Embedded Software Design DataManagement, see the Embedded Software Solutions Guide.



Visualizing productsTeamcenter’s lifecycle visualization delivers advanced visualization capabilitieswhich 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 productconfigurations:

• 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 upona Service-Oriented Architecture (SOA). This new integration offers improved supportfor the visualization software components, including both the stand-alone viewersand the new Lifecycle Viewer. It is installed automatically with Teamcenter and noadditional steps are required to work with visualization data in the Teamcenter 8managed environment.

The Data Integration Services (DIS) Adapter has been completely removed fromTeamcenter. Existing functionality from previous releases, such as the ability to loadand save PLM XML, is retained in the new SOA-based integration.

Lifecycle Visualization viewers from earlier releases are not supported by and cannotcommunicate with Teamcenter 8. However, the Teamcenter 8 stand-alone viewerscan communicate with DIS-enabled servers from previous Teamcenter releases.For information on working with Teamcenter’s lifecycle visualization, see GettingStarted with Product Visualization.

For information on configuration options for the viewers, see ConfiguringTeamcenter’s lifecycle visualization.



Lifecycle Viewer

The Lifecycle Viewer is a full-fledged visualization client within Teamcenter. Itprovides nearly all of the visualization tools offered by the stand-alone viewer, manyof which are not available in the embedded viewers within Teamcenter applicationssuch as My Teamcenter.

The Lifecycle Viewer is available in the same product configurations as thestand-alone viewer, Base, Standard, Professional, and Mockup. Features availablevary depending upon the licensing level. The Base configuration is automaticallyinstalled with the rich client.

Using the Lifecycle Viewer, you can:

• Work within a comprehensive user interface that provides access to many of theoptions previously available only with the stand-alone products, including menusand 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 .vfzcollaboration files.

For information on working with the Lifecycle Viewer, see Getting Started withProduct Visualization.

2D and 3D thumbnail previews

Display 2D raster images and JT parts in the Image Thumbnail Preview and theJT Preview views. When you select compatible objects associated with items,item revisions, and datasets within the My Teamcenter tree or the trees of otherapplications, the associated image or JT part is displayed in the appropriate previewviewer. These views are displayed by default with appropriate applications suchas 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 ane-mail to send to other members of your organization. You can specify to packageonly the session contents of the active Viewing window or the contents of all openViewing 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 datafrom existing collaboration files. You can view .vfz collaboration files in any viewerservice 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 worksession 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, seeWorking with Product Manufacturing Information(PMI).



Improved product structure loading

The performance and behavior of the Teamcenter product structure loadingmechanisms used for visualization have been improved. The visualizationapplication now “pulls” needed product structure elements, on demand, directlyfrom 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 Openingvisualization datasets.

Improved rendering when generating 2D images from 3D views

Lifecycle Visualization now uses a tiled rendering scheme when generating 2Dimages from 3D views. 2D images are now generated at pixel resolutions beyond thecapabilities of the underlying graphics hardware. The pixel resolution for the ExportImage and Print command for 3D views is now only limited by the amount of freeapplication 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 calledproduct 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 providecommonality with 2D snapshot menu commands.

For more information, see the Structure Manager Guide, Manufacturing ProcessPlanner 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 mergedinto a single area of functionality. The user interfaces for these features havebeen combined, with much of the callout user interface being moved into themarkup 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 fromwithin 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 LifecycleVisualization (prior to 8) when loaded from layer files and duringconferencing. Old text markups will be displayed and converted to thenew 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 advancedgeometry concepts that are generated from NX design data. Specific improvementsare in the areas of PMI at the assembly level, reference sets, arrangements, andpromotions. These enhancements are in both the stand-alone Lifecycle Visualizationand Lifecycle Viewer products.

Note

To take full advantage of this capability, the NX data must be created by NX6.0.3 or later. Also, manage the data using Teamcenter 8.

For information on viewing NX advanced assembly functionality, see Viewing NXadvanced 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 LifecycleVisualization. The attributes to be displayed can be configured in theTeamcenter Integration dialog box (File→Preferences→Teamcenter Integration,on the Attributes page).

• The display of attributes has been improved to include displaying multi-lineattributes. 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 theattributes 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 TeamcenterIntegration Attributes Preferences. For information on using PMI, see Working withProduct Manufacturing Information (PMI).



Part report enhancements

Enhancements to part report feature includes:

• The menu containing the Part Report option now appears in the Lifecycle Viewerof the Teamcenter Portal Rich Client (RAC) Embedded Viewer, in addition to inthe stand-alone Teamcenter Visualization viewer.

• Teamcenter object attributes (metadata) are now listed for inclusion in the PartReport.

• Part reports can now be generated as XML output files in the Computer-AidedAcquisition and Logistics Support Department of Defense (CALS) format.

• The user can now choose which element type attributes (part, leaf component, orend 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 newDirectModel-based implementation. A swept volume is a graphical representation ofthe volume and path of a part as it moves through 3D space. Swept volumes are nowgenerated in a faster, more efficient and intuitive manner than in previous releases.In addition, the visualization API has been updated to provide an automatedmechanism for generating swept volumes.

To generate swept volumes, your machine must have a graphics card with a 24-bitdepth 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 windowhave changed.

Function Previous key New keyIncrease Translation A TDecrease Translation Z GIncrease Rotation S RDecrease 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 ECADViewer.

Cross probing PCB and schematic documents

Use cross probing to find common parts that are included in the schematic design orPCB. During the design process you may need to verify similarities of and differencesbetween schematic and PCB documents. You can also determine how the schematicdesign 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 navigationand highlight a net, a marker displays on a navigation point of the net. You canthen navigate along the net moving the marker from key point to key point. Whennavigating nets on the schematic, you can navigate to different pages, dependingon the path of the net.

For information on using the net and page connector navigation, see Navigate netsand page connectors.

PCB measurement markups

ECAD measurement tools provide options for distance, radial, clearance, and lengthmeasurements. When you save these measurements to your database or file system,they become part of the PCB data session. Measurement tools are also availablewhen you checkout the PCB as read-only. You can still create measurements eventhough 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 adefault or customized set of manufacturing rules. When you run the DFA test,both the manufacturing rules and the results are displayed. The analysis displaysreflects in three broad categories; as expected (within the established threshold),as warnings, or as violations. You can highlight a warning or violation object andit is displayed in the Viewing window.

For information on using Design for Assembly, seeWorking with Design for Assembly.

ECAD reporting capability

As you review and analyze ECAD documents, you may find it useful to generatespecific reports for your records or for use when you collaborate with others. Yougenerate reports for several ECAD objects (Bus, Nets, Parts, and so forth) by selectingthe report template that meets your needs. You can preview the report before it isgenerated and you can customize the template. You can also specify default outputformats (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. Additionalprinting options are also available such as setting page headers, footers, andwatermarks. 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 beensimplified to make the ICM system easier to install and maintain. In addition, thenumber of configuration files and environment variables has been reduced.

For information on installing and configuring the Teamcenter Integrated ClearanceManagement (ICM) system, see the ClearanceDB Administration Guide in thestand-alone Teamcenter’s lifecycle visualization Help collection.



Managing CAE dataTeamcenter for Simulation provides simulation process and data managementcapabilities for CAE engineers and CAE analysts performing analysis work. Itconsists of two applications, the CAE Manager and the CAE Structure Designer.

The following are new and changed Teamcenter’s simulation process managementfeatures:

CAE Manager – Inspector

This enhancement allows you to update a CAE model structure to reflect changes tothe related product structure. It permits you to:

• Add or remove CAE model components if components are added to or removedfrom the product structure.

• Create new CAE model components to reflect additions or revisions in theproduct structure.

• Link CAE model components to corresponding product components.

• Revise a CAE model component and replace the BOM line with a later revisionif components of the product structure are revised.

You can choose whether to make the necessary changes in the current revision ofthe CAE model structure or a new revision.

Use the CAE Manager – Inspector to compare a CAE model structure and aproduct 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 integrateexternal simulation processes with Teamcenter for Simulation. It allows you toconfigure the integration of external simulation processes and tools (includingcommercial CAE preprocessors, solvers, and postprocessors, as well as anycommercial or custom-built compute tools used for CAE tasks) with Teamcenterfor Simulation. Configured processes may be invoked from the rich client and theprocess 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 menucommand in CAE Manager, and then select the desired tool from the displayedlist of configured tools and processes.




Launch simulation process remotely

This enhancement allows Teamcenter for Simulation to launch any configuredsimulation tool that can run in a batch mode on a remote compute resource, thatis, on a machine other than the client. The Teamcenter simulation administratorcan configure this feature to interact with a load balancing system. This capabilityleverages the Teamcenter Dispatcher service.

To launch a simulation process, choose the Tools→Launch Simulation Tool menucommand in CAE Manager, and then select the desired tool from the displayed list ofconfigured tools and processes. To monitor a simulation process, use the translationadministrator console in My Teamcenter.




Repeatable Digital ValidationThe 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 withTeamcenter is enhanced to allow easier installation and configuration. Also, thefollowing usability enhancements in DesignContext allow easier identification andanalysis of clearance issues.

• Simplifies the commands available on the Toolsmenu. The Tools→ClearanceDBcommand is renamed as Tools→Clearance Analysis and other commands areremoved.

• Introduces a new Clearance Analysis dialog window that shows the clearanceanalysis options in DesignContext. It includes a progress bar and a progressstatus message.

• Adds a Show Issues button to display information about the progress of thecurrent clearance calculation. An Abort button on the progress window allowsthe 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 thedatabase connection used by the proxy server to connect to the clearancedatabase. At the same time, the existing PortalDesignContextCLRServers,CLR_Timeout_Limit, and CLR_Wait_Time preferences are no longer requiredand 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 cachelessquick search mechanism.

It allows the user to make spatial searches based on box volumes, planes, proximityto objects, and size using the cacheless search engine. Attribute searches,classification searches, and saved queries are also supported. QPL and appearancesearches are also available as before.

To use the cacheless search mechanism, set thePortalDesignContextSearchEnginePreference site preference toCachelessSearchEngine. Users initiate searches and store, compare, and managesearch results in the same way as in previous releases. Revision and variant rulesmay be used to limit search results to a particular product configuration.

Teamcenter requires NX part data to create the bounding box data it uses toconstruct the search indexes needed for spatial searches.

Find this enhancement when you configure searches for the DesignContextapplication.

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

Managing quality dataDimensional Planning and Validation (DPV) is a quality management solutionyou can easily integrate into your Teamcenter environment. DPV enables theextended enterprise to collect, manage, dimensionally analyze, and report on qualitymeasurement information. This report generation solution provides rapid accessto design and manufacturing information that directly influence’s your enterprise’squality 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 AdministrationGuide and Getting Started with Dimensional Planning and Validation.



Managing Maintenance, Repair, and Overhaul dataThe following new application is available for managing Maintenance, Repair, andOverhaul data.

As-Built Manager

As-Built Manager is a separately licensed application that is installed as an optionaloverlay on top of the standard Teamcenter product. This application allows you tomanage the as-built configuration of an asset realized from a product definitionstructure, such as a design or manufacturing structure. You can use As-BuiltManager to:

• Create the as-built physical product instantiation for any configured productstructure.

• Store and manage additional information about the as-built physical partstructure that is not tracked on the product definition structure, such as serialnumbers and lot numbers.

• Reconcile the as-built structure with a configured product definition structure toidentify parts that are missing, alternates, substitutes, or deviations.

• Compare the as-built structure to the product definition structure or to anotheras-built structure.

• View the as-designed product structure and the as-built physical structureconfiguration side-by-side or by using the embedded viewer available in therich 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 ManagementMaintenance, Repair, and Overhaul (MRO) system using Data Exchange.

For more information about As-Built Manager, see the As-Built Manager Guide.



Customizing TeamcenterThe following are new Teamcenter customization features.

Service-oriented architecture (SOA)

Teamcenter APIs are moving to service-oriented architecture (SOA) to improvestandardization. SOA provides an environment that enables network callableinterfaces into the Teamcenter server.

New Workflow operations

New operations are added to the Workflow service. This feature has no impacton Teamcenter end users. Workflow will work the same way as it did prior to thenew operations.

The new operations are included in the soa_client.zip archive file on the installationsource.

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) forboth 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 thecurrent 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 toconnect to Teamcenter will experience more robust communication between theirclient and the server.

The new functionality is included in the soa_client.zip archive file on theinstallation 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 theirproduct documents. The software allows customers to take snapshots of assembliesand then display assembly breakdown diagrams with all the parts labeled. Endusers should see no difference in how Teamcenter Publish works.

The new operation is included in the soa_client.zip archive file on the installationsource.


WSDL support in Teamcenter services

A .NET WSDL interface for the .NET Web tier is now supplied. Previously, the J2EEWeb 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 J2EESOAP endpoint is provided at the .NET Web Tier.

You can connect your WSDL based client to the .NET Web tier. Once the serviceis 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 SOAoperations are supplied:

listAlternateIdDisplayRulescreateAlternateIdentifiersgetContextsAndIdentifierTypesvalidateAlternateIdssetAndEvaluateIdDisplayRule





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, toretrieve occurrence override information for their bills of materials (BOMs).

The getAbsoluteOccurrenceOverrides operation is newin the CAD:StructureManagement service, and thecreateOrUpdateAbsoluteStructure is revised.

The new and revised operations are included in the soa_client.zip archive file onthe installation source.


Support for adding objects to projects

The assignOrRemoveObjects operation is added to the ProjectLevelSecurityservice in the service oriented architecture (SOA) framework. This operation allowsobjects to be added to and removed from projects.

To utilize this operation, click the My Projects link in the Quick Links navigationbar of the Teamcenter rich client. When you add or remove objects in projects, youuse the assignOrRemoveObjects operation.

For more information about assigning and removing objects in projects, see theRich Client Interface Guide. The new and revised operations are included in thesoa_client.zip archive file on the installation source. For more information aboutthis new operation, see the Services Reference.

CAM support for NX Integration

The NX Integration has service operations for CAM functions. These operationsallow NX Integration to query, create, and modify CAM data model in Teamcenter.

The following new SOA operations are supplied in the DataManagement service:

expandFoldersForCADcreateOrUpdateMEActivityFolderscreateOrUpdateMENXObjects

The following new SOA operations are supplied in the StructureManagementservice:

createOrUpdateRelativeStructureexpandPSOneLevelexpandPSAllLevelsdeleteRelativeStructure





Miscellaneous new services for the NX Integration

The NX Integration has miscellaneous new operations, and revisions to existingoperations.

Revisions are made to the following operations in the StructureManagementservice:

createOrUpdateRelativeStructuredeleteRelativeStructurecreateOrUpdateAbsoluteStructuredeleteAssemblyArrangements

The following new operations are added to the Session service:

getFavoritessetFavoritessetUserSessionState

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 thereare heavyweight and lightweight features. Heavyweight features are represented inTeamcenter by parts that are a subclass of the Item business object. Lightweightfeatures are represented in Teamcenter by the general design element (GDE)business objects that contain information about the feature. A GDE occurrence linksthe GDE and the parent item revision. Features may contain a JT file to representthe feature during visualization.

The createOrUpdateGDELink SOA operation is added to the DataManagementservice, and the expandPSOneLevel and expandPSAllLevels operations areadded to the StructureManagement service.


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. Administratorscan use the baseline workflow to baseline items. The following elements are now inTeamcenter:

• 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 LifecycleVisualization. As a result of this enhancement, users should see faster loadingof visualization data in Teamcenter. This enhancement only makes architecturalchanges, and provides new SOA operations, ITK interfaces, and a preference. It doesnot make any customer-facing UI changes.

The following new operations are added:

getDisplayStringexpandPSOneLevelReconfigureBOMWindows

The following new ITK functions are added:

libbom/BOM_line_find_preferred_JT_refsetlibbom/BOM_line_get_JTHint_stringlibbom/BOM_line_ask_occ_for_clone_stable_uidlibbom/BOM_line_get_all_occurrences

The new preference is JTContentHintPropertyPolicy.

For more information about the ITK functions, see the Integration Toolkit FunctionReference.

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

The ChangeManagement service is included in the soa_client.zip archive file onthe installation source.

For more information, see the Services Reference.



Rich client debugging tools

Three new tools are added to the rich client interface to help you debugcustomizations that you make:

• Print ObjectDisplays the internal object values of the selected workspace object in a dialogbox.

• Communications ProfilerReports bursts of communication from the client to the server. It watches for athreshold of server calls in a span of time and reports the list of server callsand their timing.

• Performance MonitorDisplays 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 CustomizationProgrammer’s Guide.

Teamcenter supports UTF-8

UTF-8, an ASCII-compatible multi-byte encoding standard, provides the followingbenefits:

• Multilingual data can coexist in a single Teamcenter installation.

• The Teamcenter user interface can be localized and launched in differentlanguages on different clients.

• Multilingual data can be shared and updated across the different clients withoutcorrupting any data.

To use UTF-8, set environment settings (LC_ALL, LANG, NLS_LANG, andTC_language_default) to accommodate the environment and upgrade theTeamcenter environment from a legacy database to a UTF-8 database.



Teamcenter industry solutionsThe following are new features in Teamcenter industry solution applications.

Aerospace and Defense

Aerospace and Defense provides a data model template that supports the aerospaceand 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 Aerospaceand Defense solution. It allows users to manage parts, assemblies, drawings, andparts 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 datamanagement best practices:

– Managing multiple assemblies or parts with similar configuration or designby 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 theirparts 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 technicalinformation, 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 apart or assembly. Technical documents serve as source documents for creatingparts and assemblies for a product.

• Assembly drawings

In document-centric programs, a source document must be specified to create anassembly drawing. It represents the drawing that details one or more assemblieson a given technical document.



• Standard parts

Standard parts may be used in multiple programs. The design of a standard partis controlled by a specification published by a military, industry or companyauthority. Programs can be enabled to use only preferred standard parts intheir assemblies.

Find these objects in the rich client, including My Teamcenter and StructureManager.

For more information, see Getting Started with Aerospace and Defense.

Owning organization

Organizations provide an industry-compliant format for uniquely identifyingentities, including the Commercial and Government Entity (CAGE).

Organizations, which are Teamcenter groups that model legal corporations orcompanies whose members can be granted access to classified data, are defined inthe Organization application.

The owning organization attribute on business model objects allows users to createand maintain data within the context of an organization. Administrators canconfigure whether or not the data must be created in the context of an organizationand 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 tothe first pattern in the naming rule. The Item create dialog box in the rich clientis enhanced to present the user with a list of patterns with defined counters in thenaming rule attached to the item_id property. The next item ID is generated perthe selected pattern in the list.

This feature can be used to define auto-numbering rules with multiple patterns for agiven object in the context of a program.


Revision naming rules

Administrators can define revision naming rules with initial, secondary, andsupplemental 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 withthe next set of revision options as specified in the revision naming rule attached tothe item_revision_id property.


Sample program

When the Aerospace and Defense Training Program template is installed, a sampleprogram 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 Trainingprogram. 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 setup 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 ageneric framework for managing data on object associations (relations). Both therich client and thin client are enhanced to manage properties on relations. Theproperties added on a relation in the Business Modeler IDE are automaticallyexposed in the rich client and the thin client through appropriate user interfaceswithout writing any code.

For more information, see Getting Started with Aerospace and Defense and theBusiness 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 controlthe 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 deepcopy rules for a specific program.

• Identification of preferred standard parts for a program.

In addition, administrators can configure Teamcenter to display the Projectapplication as Program in the user interface.

For more information, see Getting Started with Aerospace and Defense and theSecurity Administration Guide.



Consumer Packaged Goods

Consumer Packaged Goods is a group of solutions that supports customers withpackage design, brand management, finished product management and formulamanagement.

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

• Finished product management

Finished product management allows you to create, classify and manage finishedproducts 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 artifactslike marketing briefs, design briefs, package roughs, copies, package items andso 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 SIMATICIT Interspec product, a specifications authoring tool.

This integration implements additional data model objects and feature enhancementsto permit Teamcenter to interact with Interspec. Objects that can be representedinclude BOMs, formulated materials, raw materials, ingredients, and chemicals.

Teamcenter controls the overall development process and acts as the masterrepository of all released specifications. Interspec provides specification authoringand modeling capabilities and enforces regulatory rules. Read-only copies ofspecifications are automatically saved into Teamcenter when they are created orwhen they reach a certain maturity state. The save triggers can be configured inthe Interspec workflow. Specifications are attached to Consumer Packaged Goodsbusiness 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 applicationfor viewing specifications that were originally authored in Interspec. You can use theSpecification Manager to view the structure of a specification (for example, the BOMand referenced specifications) or send them to Interspec for updating or viewing ofspecification details; you cannot update specifications in the Specification Manager.

Find the Interspec integration in the Consumer Packaged Goods solution. Find theSpecification Manager in the Teamcenter rich client.



For more information, see Getting Started with Consumer Packaged Goods and theSpecification Manager Guide.

Specification Manager

The Specification Manager application allows you to view and work withspecifications or formulas. In the Consumer Packaged Goods and food and beverageindustry, specifications capture the complete definition of products and how tomanufacture them. These specifications are developed, reviewed, and eventuallyapproved 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 SpecificationManager application.

• Opens specifications from Specification Manager in Interspec.

For more information, see the Specification Manager Guide.



Performing integrationsThe 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 DesignAutomation (EDA) application.

Managing part library

Part library is a catalog system of parts that helps designers to search/locate/accessparts and use them in the design. Administrators can now manage a part library inTeamcenter and exchange part library data between Teamcenter and ECAD librarytools. You can access the part library functionality from the Tools→Import→FromECAD Library and Tools→Export→To ECAD Library menu in the rich client andfrom 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 forPADS Layout and PADS Logic tools. You can manage data that your PADS programscreate. The Teamcenter menu items are available in the PADS menu. This allowsyou to perform Teamcenter operations like saving, checking in, checking out fromTeamcenter servers, while executing design tasks from their PADS product.

For more information about working with Mentor PADS, see Getting Started withElectronic (EDA) Lifecycle Management.

Support for OrRCAD

Teamcenter supports Cadence OrCAD product line. This includes support for OrCADCapture and OrCAD Layout tools. You can launch the Cadence OrCAD applicationthrough the Teamcenter Gateway for EDA application and can extract BOM, createa viewable file, perform check in and check out.

For more information about working with OrCAD, see Getting Started withElectronic (EDA) Lifecycle Management.

SOA communication layer

Teamcenter Gateway for EDA uses service-oriented arhitecture (SOA) as thecommunication layer instead of AIWS.

For more information about SOA, see Getting Started with Electronic (EDA) LifecycleManagement.



Teamcenter Gateway for EDA client logging

You can specify a log file name and log level for logging Teamcenter Gateway forEDA client errors, warnings, and other operational information. This can be used tosubmit 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 isused for library integrations such as Cadence Allegro library and Mentor Expeditionlibrary. The gateway is also used to interface with ECAD library tools where thelibrary tool does not provide a user interface. The interface provides a menu ofECAD-Teamcenter integrations actions similar to that of the embedded integration.

For more information about working with Teamcenter Gateway for EDA, see GettingStarted with Electronic (EDA) Lifecycle Management.



NX Integration

These topics are part of the Teamcenter NX Integration. For more information aboutthe Teamcenter NX Integration, see the appropriate integration guide.

Managing NX Drawings

Teamcenter NX Integration supports NX 7.0 drawings being populated into a defaultTeamcenter drawing type supported by two new relations: DrawingOf, between thedrawing and its principal assembly, and DrawingUsing, between the drawing andthe 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 adrawing 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 youcreate 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 torequirements in Relation Browser.

• Search for trace links in the Relation Browser.

For more information about using trace links, see the Requirements Manager Guide.



Managing translationsDispatcher, previously known as Translation Management, is the integration ofthe Dispatcher Server and Teamcenter. Dispatcher enables Teamcenter users totranslate data files that are managed by Teamcenter to 3D or 2D file formats.

Note

The names of Dispatcher and its components are changed from previousversions of the application.

New name Old name

Dispatcher Translation Management

Dispatcher Server Translation Solution Toolkit (TSTK)

Dispatcher client Translation service

Request administrationconsole

Translator administrator console

Translation intelligent licensing

Translation processes running on a dispatcher module may be dependent on theavailability of licenses for the translator. When a process fails due to a licenseissue, the module sends back an error to the scheduler; however, the module hasno knowledge of why the process failed.

A new configuration file, TaskConfiguration.xml, is included in the scheduler tohold information about a particular service and the maximum number of processesthat can run at a given time. This allows administrators to control the number ofprocesses and manage license availability for the specified processes across modulesat 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 schedulerfails due to some reason, such as a power outage, all translation tasks are stored inthe 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 functionalityincreases the load on the Dispatcher Server.


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



Chapter

3 Teamcenter 8 release notes

Teamcenter 8 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Installation and upgrade release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Lifecycle Visualization installation release notes . . . . . . . . . . . . . . . . 3-6Online help installation release notes . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Usage release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Client for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17Lifecycle Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Manufacturing Process Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Multi-Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Requirements Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Schedule Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23Structure Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

Administration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29Customization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31Internationalization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

Teamcenter 8 documentation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38Using documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38Using PDF files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38Using HTML files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

Access Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40Business Modeler IDE Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40C++ API Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43Dispatcher Server Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43ERP Connect Integration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44Getting Started with Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . 3-44Getting Started with Dispatcher (Translation Management) . . . . . . . . . . . 3-45Global Services Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47Installation on UNIX and Linux Servers Guide . . . . . . . . . . . . . . . . . . . . 3-48General documentation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48Environment settings for non-English locales (UNIX and Linuxsystems) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50Environment settings for non-UTF-8 environments . . . . . . . . . . . 3-50Environment settings for UTF-8 environments . . . . . . . . . . . . . . . 3-54

Installation on Windows Servers Guide . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58General documentation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58Environment settings for non-English locales (Windows systems) . . . . 3-60

Multi-Site Collaboration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63Preferences and Environment Variables Reference . . . . . . . . . . . . . . . . . . 3-68ETS_update_state_delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69


PLMXML_put_pie_log_in_syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70TC_NX_Foreign_Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71TC_ugmaster_name_separator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

Rich Client Interface Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72Schedule Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74Security Services Installation/Customization . . . . . . . . . . . . . . . . . . . . . . 3-77Services Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77Structure Manager Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78Clarification of Change to Replace command behavior . . . . . . . . . . . . 3-78

Teamcenter Environment Manager Help . . . . . . . . . . . . . . . . . . . . . . . . . 3-78Upgrade Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78Utilities Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80dispatcher_create_rqst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81

What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83Workflow Designer Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85CONTMGMT-notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91Adding a Validate task to a workflow process . . . . . . . . . . . . . . . . . . . 3-92Inserting a Validate task into a workflow process . . . . . . . . . . . . . 3-93Finding error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98Task behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99


Chapter

3 Teamcenter 8 release notes

Release notes are comprised of product release notes (known problems in the softwareand workarounds) and documentation release notes (corrections to documentation).

Teamcenter 8 product release notesThe 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 ofhosts, are displayed in table format. If you do not press Enter after entering avalue in one of these tables, the value may not be saved. For example, in the FSCService Additional Group Sites panel, if you enter a value in the FSC ID columnand 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 EnvironmentManager.

• Alias objects must be migrated to Identifier objects


Alias object functionality is completely removed. The new alternative to Aliasobject functionality is AliasId (Identifier) functionality.

How to work around or avoid

You must migrate Alias objects to Identifier functionality if your enterpriseever created Alias objects.

1. Migrate Alias business objects in the database.

You must use themigrate_alias utility to migrate Alias business objects toIdentifier business objects.

Use themigrate_alias utility to migrate Alias data. See the documentationfor the migrate_alias utility in the documentation set for the version ofTeamcenter 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 versionsof Teamcenter, you must perform migration in earlier releases only.For example, if you are upgrading from Teamcenter Engineering 2005SR1 to Teamcenter 8, perform migration in the Engineering 2005SR1 release itself. If you are upgrading from Teamcenter 2007 toTeamcenter 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 objectcustomizations.

– You have also created a template project for your customizations in theBusiness Modeler IDE.

– You have executed the migrate_alias utility on your Teamcenter 2007database.

If you are a customer belonging to such a scenario, you must fix your customtemplate project to ensure that the Alias related data model objects areremoved. This cleanup must be done in your Teamcenter 2007 templateproject before working with the Teamcenter 8 Business Modeler IDE.

Customization example:

– A customer created subtypes of the Alias business object, whereSupplier is a secondary business object that is a subtype of Alias, andSupplier1 is a primary business object that is a subtype of Alias.

– A customer defined an LOV named SupplierList and attached it to thecontext type property on the Supplier business object.

If the customer template with the above two customizations directly importsa project into Teamcenter 8 Business Modeler IDE, the client fails thecustomer template import and displays the following errors in the consoleview:

Model Error: D:\workdir\thog_mp6_test\mp6temp\extensions\business_objects.xmlLine:3 Column:130 Undefined Class Alias (parentClassName)in TcClass Supplier1.

Model Error: D:\workdir\thog_mp6_test\mp6temp\extensions\business_objects.xmlLine:4 Column:86 Undefined Business Object Alias (parentTypeName)in TcStandardType Supplier.

Model Error: D:\workdir\thog_mp6_test\mp6temp\extensions\business_objects.xmlLine:5 Column:91 Undefined Business Object Alias (parentTypeName)in TcStandardType Supplier1.

Model Error: D:\workdir\thog_mp6_test\mp6temp\extensions\business_objects.xmlLine: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 theAlias business object customizations.

b. Reload the data model using the Reload Data Modelmenu command andensure 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, thedefault queries for locales other than English are not installed. Locale clientsalways 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, theDispatcher client fails to start up, and displays an access denied exception.


Disable Security Services for the Dispatcher client. All the other components canstill be Security Services enabled, but the Dispatcher client should be installedon a separate machine that is not Security Services enabled. If they must beon the same machine, a new TC_DATA location should be associated with aDispatcher 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 clientis installed.


1. After the rich client installation, remove the following plug-in JAR files fromthe Teamcenter-installation-root/portal/plugins directory:

com.teamcenter.rac.cme.cmereport_8000.0.0com.teamcenter.rac.padpdf_8000.0.0jfreechartcom.teamcenter.rac.accessmanager_8000.0.0com.teamcenter.rac.aif.registryeditor_8000.0.0com.teamcenter.rac.appearanceconfiguration_8000.0.0com.teamcenter.rac.architecturemodeler_8000.0.0com.teamcenter.rac.auditmanager_8000.0.0com.teamcenter.rac.authorization_8000.0.0com.teamcenter.rac.cae.ase_8000.0.0com.teamcenter.rac.caese_8000.0.0com.teamcenter.rac.caese_dm_8000.0.0com.teamcenter.rac.charts_8000.0.0com.teamcenter.rac.classification.icadmin_8000.0.0com.teamcenter.rac.classification.icm_8000.0.0com.teamcenter.rac.cme.collaborationcontext_8000.0.0com.teamcenter.rac.cme.fse_8000.0.0com.teamcenter.rac.cme.mpp_8000.0.0com.teamcenter.rac.cme.mrm_8000.0.0com.teamcenter.rac.cme.pmp_8000.0.0com.teamcenter.rac.commands.report.reportdesigner_8000.0.0com.teamcenter.rac.commandsuppression_8000.0.0com.teamcenter.rac.crf_8000.0.0com.teamcenter.rac.databaseutilities_8000.0.0com.teamcenter.rac.designcontext_8000.0.0com.teamcenter.rac.dpv_8000.0.0com.teamcenter.rac.ecmanagement_8000.0.0com.teamcenter.rac.edalib_8000.0.0com.teamcenter.rac.eintegrator.eintadmin_8000.0.0com.teamcenter.rac.organization_8000.0.0com.teamcenter.rac.plmxmlexportimportadministrationcom.teamcenter.rac.project_8000.0.0com.teamcenter.rac.pse_8000.0.0com.teamcenter.rac.querybuilder_8000.0.0com.teamcneter.rac.requirementsmanager.win.embeddedword_8000.0.0com.teamcenter.rac.requirementsmanager_8000.0.0com.teamcenter.rac.schedule_8000.0.0com.teamcenter.rac.setupwizard_8000.0.0com.teamcenter.rac.smb_8000.0.0com.teamcenter.rac.subscriptionmonitor_8000.0.0com.teamcenter.rac.tctdv_8000.0.0com.teamcenter.rac.tdv_8000.0.0com.teamcenter.rac.tracelinks.ui_8000.0.0com.teamcenter.rac.ui.advanced_8000.0.0



com.teamcenter.rac.validation_8000.0.0com.teamcenter.rac.vis_8000.0.0com.teamcenter.rac.vm_8000.0.0com.teamcenter.rac.workflow.processdesigner_8000.0.0com.teamcenter.rac.workflow.processviewer_8000.0.0PLMContainerProxyscheduling_rac_interface_8000.0.0

2. Do not install the following rich client add-ons:

GM Overlay for Rich ClientSCM ClearCase for Rich ClientEmbedded 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 ClientLite 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 LifecycleVisualization.

• Embedded viewer installation reports file registration error


During installation or uninstallation of the Teamcenter embedded viewer, ifMicrosoft Visio is not present on the host, the installer displays the followingerror:

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, theinstallation 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 clientviewers are released together and you must use the same release version foreach. For example, mixing an earlier Teamcenter 8 rich client installation witha later Lifecycle Visualization installation may cause the rich client viewer tostop working.


The versions must remain in tandem, or you must copy theSingleEmbeddedViewer.jar file from the Program folder in LifecycleVisualization to the plugins folder in the rich client. The old JAR file must becompletely replaced. Upgrading the rich client installation to a later version ofthe viewer automatically upgrades any stand-alone viewer already installed.

• Over-the-Web Installer nonroot user installation of LifecycleVisualization not interoperable with NX


Lifecycle Visualization places files in a root folder used by NX to determineinteroperability. The folder usually needs to be created by a user with rights tothe root folder. However, the Over-the-Web Installer does not require users tohave access rights to the root. Although the warning is written to the LifecycleVisualization install.log file, no warning is displayed by the Over-the-WebInstaller.


Either run the Over-the-Web Installer as a user with rights to the root, or createthe ugs directory before starting the Over-the-Web Installer and give read andwrite permissions on the ugs directory to the user running the Over-the-WebInstaller.



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 thanare supported by the ISO standard for DVD creation. As a result, the PUBS kitmust be zipped into a ZIP file on the DVD.


Before installing the online help for Teamcenter, the PUBS ZIP file must beunzipped.

• 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 securitysetting that prevents the help from launching correctly from a UNC path (file:///).


To change this setting, you must change the value of thesecurity.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 totrue 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 thevalue is set to false.

• WebLogic 9.1 deployment of Teamcenter with online help fails


When installers of Teamcenter thin client include the Teamcenter - Online Helpsolution and attempt to deploy the tc.war or tc.ear files using WebLogic 9.1, thedeployment 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 theTeamcenter 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 saveadministration data even if the ICS_admin_requires_dba preference is setto True.


You can protect Classification Administration data by restricting write privilegesto non-dba users through Access Manager.

To protect the classification hierarchy, click on the SAM Classification Rootnode in the classification hierarchy panel and create an ACL to revoke writeprivileges to non-dba users.

You can protect dictionary attributes, key LOVs, and views by revoking writeprivileges 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 TeamcenterBOM entities available in Teamcenter 8


Preferences related to CAD BOM Alignment should not be available becauseCAD BOM Alignment and Teamcenter BOM are not supported in Teamcenter 8.Additionally, line of usage query in Multi-Structure Manager (formerly calledCollaboration Context) should not be available in Teamcenter 8.


Users should not attempt to perform CAD BOMAlignment actions in Teamcenter8. Users should not provide values for preferences that start with Usage.

• Rich client Checkout Explorer dialog box does not support remotecomponents


The rich client Checkout Explorer dialog box does not display the components ofa BOM view revision if it contains any remote components. Remote componentsare 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 revisionto 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 butare 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, Vista32-bit, Vista 64-bit, or Server 2003), the Find in Display box and the Where andDepth lists may be missing from the Impact Analysis view toolbar. This is anEclipse problem.


In the Microsoft Windows Display Properties dialog box, click the Appearancetab and change the selection in the Windows and buttons list from WindowsClassic style to Windows XP style.

In the case of Windows Server 2003, before accessing theWindows XP style fromthe Display Properties dialog box, ensure that the Themes service is started(this is disabled by default). Perform the following steps to enable themes onWindows 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 selectAutomatic 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 withthe space characters


If an item’s footprint or symbol ID field contains spaces, the ECAD librarycannot 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) andBriefcase to import parts into Teamcenter. TIE does not allow updating existingpart properties. If a part is imported from two libraries, it is assigned only to thefirst imported library. When users synchronize with a second library, although apart 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 thebase unit, and its attribute value is saved into the database.

However, the Classification import/export layer does not provide APIs to accesssubunits other than the base unit. This leads to ECAD library integrationsfailing during import when the value is not in the base unit.


Avoid using unit bundles for ECAD attributes in ECAD tools as well as inClassification.

• 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-8client 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 characterset as the text file; otherwise, data loss can occur. Also, when these text files arenot 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 iscompatible with Teamcenter 8 and is not compatible with previous versions.

• Unsuccessful logon on Windows Vista clients when enabled for SecurityServices using TcSS


When logging on using the Teamcenter rich client on Windows Vista, thefollowing message appears:

Login was unsuccessful.:Unable to detect SSO session

This message indicates that the rich client is unable to find the Security Servicessession file on the client machine. Vista introduced the concept of the InternetExplorer sandbox where data is stored on the client machine on behalf of anuntrusted URL in an area sequestered from any other applications. Therefore,when Internet Explorer runs in the sandbox, the Security Services sessionfile is written inside the Internet Explorer security sandbox context. Otherapplications 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 InternetExplorer to avoid running in the security sandbox when it creates the sessionfile, leaving the file visible to other processes running for the user.



• Incorrect file name displayed in thin client file download dialog box inInternet Explorer 6.0


An incorrect file name is displayed in the file download dialog box whenattempting to view a file with a .prt extension from a UGPART dataset from thethin client in Internet Explorer 6.0.


This appears to be a problem with compression in Internet Explorer 6.0. Onepotential workaround is to upgrade to Internet Explorer 7.0 or use a differentbrowser such as Mozilla.

If Internet Explorer 6.0 must be used, another potential workaround is todisable file transfer compression for files with a .prt extension in the FMSsubsystem. To do so, add the FSC_DoNotCompressExtensions property tothe <fscdefaults> element of the fmsmaster configuration files and include theprt 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 theconfiguration 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-tierclient, it may appear that no tools are configured when they actually are. Thismay occur when a user tries to launch a tool using Tools→Launch SimulationTool from CAE Manager, or when an administrator tries to configure a tool usingEdit→Configure Simulation Tools from CAE Manager.


Users of this capability must either be using a two-tier client or a speciallyconfigured four-tier client that provides access to the TC_DATA folder of theTeamcenter installation. This problem will be addressed in a future version toallow 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 UNIXsystems. This failure can be caused by other services that the FSC processdepends on which have not yet reached an operational state.

For example, the ypbind service can take additional time to start. Because thisservice was not operational at the time an attempt was made to start the FSCservice, the su operation failed to switch to the required user to start the FSC.


Correct the reason that the ypbind service is launching slowly. BecauseSiemens PLM Software software is not directly contributing to the slow launchof ypbind service, this resolution must be investigated by the respective ITdepartments on a case-by-case basis.

A workaround is to add a pause in the startup script. A sleep value of 120 secondswas found to be sufficient in test systems. The sleep command must be added tothe startup script in the rcname.d directory. Do not modify the rc scripts underthe $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 toboot later in the boot order did not provide sufficient time to allow theypbind 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 alreadyassigned 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.474227823seconds.


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 toNotepad 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 copiedand pasted to Notepad without problem.



• Teamcenter Publish is not supported in Teamcenter 8


Lifecycle Visualization crashes when a publishing page dataset is selected anddisplayed.


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 wheninvoked from a Windows based platform (Windows 2003 server or WindowsXP client).


Perform remote import in the foreground mode. Remote import in backgroundmode 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 Explorer6, ActiveX is used to support menus.


Internet Explorer 6 requires theWEB_use_activex_lov preference to be set toyes.



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 panesmay not accept keyboard character input. Whitespace keys (like the spacebar and arrows) work, but letter keys are not recognized. Copy and paste arefunctional using the clipboard. This occurs in the Advanced Search criteriainput fields and the Check-In task pane. Other controls or task panes mayexhibit similar behavior.


This is a known issue with the Microsoft .NET 3.5 run time. Installing the .NET3.5 Service Pack 1 addresses the issue.

There is a manual workaround. If the text entry control does not displaykeyboard 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, editsthe e-mail, and clicks the Save button on the Teamcenter menu. The changescannot 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 arequirement in the embedded Microsoft Word window and makes edits thathe wants to save.

When the requirement dataset is opened in the embedded Microsoft Wordwindow, the Client for Office add-ins tab is displayed. When the user attempts tosave the requirement dataset using the Client for Office menu, Client for Officecode does not recognize the Teamcenter object context and does not know wherethis dataset came from within Teamcenter.


Do not use Teamcenter menu. When the document is opened from the richclient, the Office Live add-in application disables the Office save user interfaceand presents its own save button. The user should use this save button (notthe Teamcenter save user interface).

• Input not accepted from task panes

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




The problem is fixed by the .NET Framework 3.5 Service Pack 1, found at thefollowing 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 notwork 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 launchesthe Office application. Client for Office (add-in) loads and the Teamcenter tabis displayed. The user edits the document and clicks the Save button in theTeamcenter menu. The rich client client and Client for Office (add-in) are not yetintegrated, and therefore have no mechanism by which to transfer Teamcenterobjects back and forth.


Choose Save As to save a copy of the file to Teamcenter as a new dataset. Ordo not use the Save button on the Teamcenter menu, but use the standardOffice Save button, and the file is uploaded to the rich client when the Officeapplication closes.

• Expanding a folder is slow in Client for Office


Expanding a folder in Client for Office using the Browse navigation controlresults in a slow response when the folder contains a large number of childobjects. An inefficient algorithm causes the rendering of the list of folder objectsto take a long time.


The Folder View navigation control can be used and does not display thisperformance issue.

• Unsupported query type error in Client for Office


In Client for Office, if you perform an advanced search by selecting theChecked-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 isrunning on Windows or LINUX platforms


S1000D is supported only if the Content Management Web server is running onWindows or LINUX, because the SGML parser is not available on the otherplatforms.



• 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, thefollowing permissions are inoperable:

xdShowViewContentInboxxdShowPdmViewxdShowPdmResourcesViewxdShowProjectOrgansiationFolderView


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 cannotbe turned off


If the user sends a valid object to the Lifecycle Visualization viewer and switchesto another perspective while the viewer is loading up, the viewer area isdisplayed in the current perspective. The toolbars and menus associated withthe 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 defaultlayout.

• Multiple documents open in rich client Lifecycle Visualization causesauthentication dialog box


A logon dialog box sometimes appears when opening multiple documentssimultaneously in the rich client Lifecycle Visualization viewer.


If you do not have Security Services installed, log on with the dialog box andproceed 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 theLifecycle Visualization viewer is a single document. You should not see thelogon dialog box for the rest of the session. Otherwise, the logon dialog boxmay 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 partmay not be immediately visible in the 3D Viewing window.


Performing a Fit All operation (for example, Navigation→Fit All) in the 3DViewing 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, andthese documents are all closed at once (for example, by using File→Close), adialog 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 tooperate normally.

• Lifecycle Viewer corrupts the Customize Toolbar


If the Lifecycle Viewer is opened within the My Teamcenter perspective, it opensall 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 ofoperations 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 calculateallocated 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 2007in Multi-Site configuration


In a four-tier Multi-Site environment, remote checkout of an assembly betweenTeamcenter 8 and a Teamcenter version earlier than Teamcenter 2007.1.MP7fails if the assembly contains stubs.


Upgrade the pre-Teamcenter 2007.1.MP7 environment to Teamcenter2007.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 NX6.0.3


When the part is saved from Teamcenter Integration for NX, the bounding boxobjects 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 boxobjects are created when a part is saved.


To generate the bounding box objects for NX parts, run thecreate_or_update_bbox_and_tso utility with the appropriate command linearguments.

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 specialcharacters, the document paragraphs that contain these special characters arenot imported as body clear text. It results in errors messages when expandingthe requirements structure in Requirements Manager.


When users get an invalid xml error, they can remove the clear text property onthe bomline. After this property is removed, users do not see any exception onthe bomline. Users are able to view the clear text but can edit the requirement.

• Trace link options do not appear in the Manufacturing Process Plannerwindow


Trace link commands such as Start Link, End Link and Traceability Report arenot available from manufacturing applications.


Currently, users must use the My Teamcenter or Structure Manager applicationto create trace links.



• Cascading LOVs are not supported in Excel Live and Word Live


Cascading lists of values (LOVs), including hierarchical and interdependentLOVs, 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 inContext Manager and export to Excel.

• Multichoice properties are not supported in Live Word


Editing of multichoice property values is not supported from the embedded WordLive 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 expectedresults 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 cannotbe modified in Schedule Manager


Certain properties for summary tasks in the Properties dialog box cannot bemodified. For example, the Description box cannot be modified.


Certain properties like description can be updated through inline editing on thetask 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 masterboundary date.

– Updating the start and finish of a master schedule does not update the lateststart or earliest finish dates (the calculated fields) of the subschedules.

– Removing a subschedule from a master does not reset the earliestfinish/latest start attributes to null if it is not part of any master. (There isno 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 amaster does not reset the earliest finish/latest start attributes to null.

Note

The Latest Start and Earliest Finish dates are system calculated fields andexist primarily in the case of master and subschedules. They sometimesdo not get updated when schedules are removed or schedule dates areupdated. 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. Onlythe 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 relationshipshould 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 createoption selected, the saved schedule is opened in Schedule Manager. However,the associated scheduling menus and the toolbar are sometimes not visible. Asimilar problem occurs with program views during Save As and Create actionswith the Open on create option selected.


Do not select the Open On Create option while performing the Save As action orcreating a program view. Then open the schedule or program view after creation.

Another solution is to switch to the My Teamcenter application and then switchback to Schedule Manager. Then the menus and toolbars appear.

• Problems with duplicate subschedules in the same master in ScheduleManager


In Schedule Manager, the same subschedule exists more than once in a masterschedule and subschedule structure.

– Data from the subschedule is included more than once at the top-levelrollups such as Work Estimate and Work Complete. (There is no workaround for this problem.)

– Cut, copy, and paste functionality may not place the tasks in the desiredlocation if the duplicated subschedule is selected as the target of the paste.

– Updates to the duplicated subschedule or its tasks do not get reflectedproperly in the user interface.


To resolve the cut, copy, and paste problem, do not select the subschedule itselfas the target of the paste, but select a task or milestone that is a sibling to thesubschedule.

To resolve the update problem, manually refresh the schedule after making achange inside a duplicated subschedule.



Note

Adding duplicate subschedules to the same master is prevented.Duplicates can only exist as subschedules of existing subschedules inthe master.

Siemens PLM Software recommends that you do not create mastersubstructures where the same subschedule is used more than once. Thistype of structure is not supported.

• Choose a schedule template dialog box


In the template dialog box for status and priority property, internal values aredisplayed instead of the string values.


The mapping between internal integer values and the actual string values forStatus and Priority properties is as follows:

– Status

Value Description0 Not started

1 In progress

2 Needs attention

3 Complete

4 Abandoned

5 Late

– Priority

Value Description0 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 dialogbox. 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 inRequirements Manager in thin client


Creation of items in Structure Manager, and creation of requirements orparagraphs in Requirements Manager, fails in the thin client. Teamcenterdisplays 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 RequirementsManager, 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 ofReleased 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 thatis 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 TeamcenterEDA, and the CCA of a schematic design is revised in the rich client, asubsequent save of that schematic design fails with a message regarding theBVR not being checked out on the original item revision. This problem is due tononsynchronization of the cache with the object in the rich client.


Refresh the cache with the latest data from Teamcenter by performing a purgecache 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 theCopyAsReference deep copy rule for the EDA dataset, the old design is openedand cached.


When revising in the rich client, ensure the EDA dataset is using theCopyAsObject 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 performthe revision.



Administration release notes

The following release notes pertain to the system administration of Teamcenter andthe use of the administration applications.

• data_sync utility with –cp option receives failed to delete checkpointdataset error


When a exported assembly is synchronized using the data_sync utility withthe –cp option for checkpoint, the command may fail with this error message:Failed to delete checkpoint dataset. Error - 14104. This occurs becauseTCFS and FSC both access this database, and TCFS attempts to delete thecheckpoint dataset while FSC still controls it. Though the data_sync utilityshows a failure, the data_sync utility actually works successfully.


Change the FSC_MaximumIdleFileHandleAgeMs FSC configurationelement, which is set to 10,000 milliseconds (10 seconds) by default. Change it to1000 milliseconds to solve this issue.

• Specification transfer from Interspec to Teamcenter


Specification transfer from Interspec to Teamcenter fails when thePS_Find_Number_Validation preference is set to true.

The preference PS_Find_Number_Validation determines whether Teamcentervalidates find numbers. If validation is enabled with this preference, an errorappears when the find number is zero or not unique within the parent structure.

Specifications transferred from Interspec to Teamcenter do not have findnumbers. Therefore, this preference must be set to false. This is the defaultsetting for the preference and should not be changed if the Interspec-Teamcenterintegration 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 ifthe item_id attribute contains non-English characters. This problem occurson UNIX systems when the IDSM daemon is not started with the identicalTeamcenter execution environment settings. By default, the IDSM serverprocess 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 IDSMstartup script file located in TC_BIN:

LANG=en_US.UTF-8LC_ALL=en_US.UTF-8



• TcXml import fails when QSEARCH is set to true


TcXml imports fail when cacheless search (QSEARCH) preferences are set totrue. 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 leveland set them to false for users making TcXml imports. Set the followingpreferences to false:

QS_QSEARCH_ENABLED=falseQSEARCH_update_enabled=falseQS_SPATIAL_ENABLED=falseQS_BBOX_GENERATION_ENABLED=falseQS_BBOX_GENERATION_FROM_NX_ENABLED=falseQS_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 alsoidentified as 11i v3.


Configure the ODS for nonmultiprocess operation or deploy multiprocess ODSon 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 CAEItem wizard


Custom attributes on the primary business object for CAE Items cannot beaccessed from the New CAE Item wizard in My Teamcenter, CAE Manager, orCAE Structure Designer applications.


Use the Business Objects view in the Business Modeler IDE to view Item orItemRevision business objects.

Item is the most common business object under which you create a new businessobject. Use the Item business object or its children when you want to createbusiness objects to represent product parts. When you create a business objectusing Item (or one of its children) as the parent, in addition to the new businessobject, you can also create an item master form, an item revision, and an itemrevision master form.


Attributes that are defined on an item master form or a revision master form arepresented on the New CAE Item wizard. The method of putting attributes onthese forms should continue to be used when creating custom item types that aresubtypes 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 internalserver code and defined as explicit deep copy rules in the Foundation template.This affects the ITK behavior for the Revise and Save As operations ofItemRevision business objects.


The ITK changes do not affect any existing customer code. You must be aware ofthe changes in the ITK behavior for future custom code changes.

Prior to Teamcenter 8, some of the deep copy rules applied during the Reviseand Save As operations of an ItemRevision business object were hard coded.They are now exposed in the Foundation template as explicit deep copy ruleson the ItemRevision business object. This allows customers to override thedefault deep copy behavior.

Beginning at Teamcenter 8, a call to any one of the following ITK automaticallyinvokes the ITEM_perform_deepcopy ITK.

ITEM_copy_revITEM_copy_itemITEM_copy_item_with_mastersITEM_copy_rev_with_master



This change is to ensure that customers always perform a deep copy after anItemRevision business object is revised or saved.

If any old custom code (prior to Teamcenter 8) invokes theITEM_perform_deepcopy ITK, the custom code remains unaffected. This isbecause the ITEM_perform_deepcopy ITK first checks if the object is alreadyrevised or saved. If yes, the deep copied objects are returned without performingdeep copy again. If no, deep copy rules are applied.

Therefore, beginning in Teamcenter 8, there is no requirement for customercode to invoke the ITEM_perform_deepcopy ITK after a call to any one ofthe ITK listed above.

Previously, the Save As operation on an Item object carried forward only certainrelations of the associated ItemRevision object. Beginning in Teamcenter 8,when a Save As operation is performed on an Item object, the old relations of theassociated ItemRevision object are carried forward based on the deep copy rulesin the database. Therefore, the deep copy rules in the database is the decidingfactor 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 ageneric deep copy rule to perform the Copy As Object action for all its relatedobjects, and if the related other side object happens to be an ItemRevisionobject, 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 codeon Windows platforms only. The Business Modeler IDE should provide theoption to generate multiple platform makefiles.


If you intend to build the same custom server code on multiple platforms, youcan 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 codeand build server code.

For more information, see Build server code on Windows.

2. For the additional platforms, first copy the new template directory andsubdirectories, 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 choosingFile→Import→Business Modeler IDE→Import a Business Modeler IDETemplate 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→BuildConfiguration. Change the settings in the Build Configuration dialogbox for your platform.

c. In the left pane of the Properties dialog box, choose Teamcenter→CodeGeneration. Change the settings in the Code Generation dialog box foryour location, for example, in the Base Path box.

Note

If you are moving from Windows to UNIX, select the Folders checkbox and change the back slashes to forward slashes.

6. Modify the .project file to update the source folder and generated sourcefolder location.

7. Generate code by right-clicking the template project in the Business Objectsview and choosing Generate Code→C++ Classes.

Note

If moving fromWindows to UNIX, first update the C++ build commandin C/C++ Development Tools (CDT) to use make.

This generates all the C++ code and the makefiles on the new platform. Buildingfrom CDT or a command line using the makefiles is now set up for the newtemplate and its libraries. Successive builds for the same libraries can beshortened by copying the generated C++ code to the additional platforms andreusing the same makefiles.

• Default value for the Enabled property constant is not honored


In the Business Modeler IDE, the default value for the Enabled propertyconstant 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 BusinessModeler IDE, the property has default settings for Enabled and Modifiableproperty constants, as shown in the following figure.

Default new custom property settings

Change the setting for the Modifiable constant from Read toWrite, as shownin 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 (suchas the rich client, thin client, or Excel Live). The system does not honor theuser setting and allows users to edit the property value in the user interface.


Override the attachment for the Enabled property constant even though itsvalue matches with the default value.

1. Change the Enabled property constant value from false to true, as shown inthe following figure. Note that the Overridden column for enabled constantis checked.

Enabled constant changed to true

2. Save the data model.

3. Change the Enabled property constant value back to false, as shown inthe following figure. The property constants table displays that the valueis false and it has been overridden.



Enabled constant changed back to false

Note the difference between the Enabled constant in the first figure and thelast figure. In the first figure, the value for the Enabled constant is false andthe Overridden column is not checked. But in the last figure, the value forthe Enabled constant is false and the Overridden column is checked. Thismeans 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. Theproperty is not be editable in the user interface, and it can still be modifiedprogrammatically.

This workaround is not only for customer-defined properties, but is also intendedfor 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 isMicrosoft’s extension of Shift JIS to include NEC special characters (row 13),NEC selection of IBM extensions (rows 89 to 92), and IBM extensions (rows115 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 innon-English locales.



• Oracle database character set setting for corporate server installationand upgrade


Upgrade of the GM Overlay template and its dependent templates fails witherror 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 thatcontains characters that are not compatible with, or supported by, the characterset (NLS_CHARACTERSET) in the Oracle database.

If the GM Overlay template contains German characters, when it is deployed toa database that does not support the German character set (WE8MSWIN1252),German characters such as umlauts and the double s (ß) are stored as differentcharacters in the database. This causes the Business Modeler IDE comparatorto generate an incorrect delta file.

By default, when an Oracle database instance is created, it is set with theWE8MSWIN1252 character set (option 1) unless the database administratorspecifically selects a different character set (option 3).



If the database administrator accepts the default character set in theInitialization Parameters dialog box during Oracle database instance creation,there are no issues with installing the GM Overlay template. However, if thedatabase administrator changes the Oracle database character set to anythingother than WE8MSWIN1252, installation or upgrade of the GM Overlaytemplate most likely fails.

To verify whether the character set is set correctly, run the following SQLcommand:

SQL> select * from NLS_DATABASE_PARAMETERS;

Note

This problem can occur if any template having non-ASCII characters isdeployed to an Oracle database that has the character set to a value otherthan WE8MSWIN1252.

For information about how to modify the database character set to work aroundthe problem, see the Oracle documentation.



Teamcenter 8 documentation release notesThe following documentation additions and changes will be incorporated in a futureversion 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 PDFversions of the Teamcenter online help. You can view these guides using AdobeAcrobat 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 orentire guides. You can also search the complete online help collection by eitherof 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 FullReader 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 thePDF\pdf\tc2008.pdx file in the documentation distribution media.

If you copy the PDF online help collection from the documentation installationmedia to a local drive and you want to be able to search the collection, make sureyou 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 topicis PDF/pdf.


http://www.adobe.com


Using HTML files

The HTML directory on the documentation installation media contains HTMLversions of the manuals.

The Teamcenter online help requires a Web browser that supports Java for thesearch to work. The browser version and Java specification required for online helpdepends on the operating system you are using. For information about supportedbrowsers and Java versions for your operating system, see the Siemens PLMSoftware Certification Database:


Note

Several features of the online help system require the display of popupwindows; for example, searching the online help collection and viewinggraphics. If a popup blocker utility is installed on the Web server or clientworkstation, you must configure the utility to allow popup windows from theonline help domain. Otherwise, the online help system does not functioncorrectly.



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 statementstopic:

– Do not modify access control lists (ACLs) referenced by rules on the SystemObjects branch. Adding new rules, deleting rules, or in any way modifyingexisting rules on the Systems Objects branch of the rule tree may resultin unpredictable behavior or loss of data. Modifying the Systems Objectsbranch of the rule tree is not supported unless specifically advised to do soby 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 orWorkspaceObject to makethat business object the highest (root) object displayed in the Business Objectsview. 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 thebusiness object that is the highest (root) object displayed in the BusinessObjects view:– BusinessObjectDisplays all business objects, including run-time business objects.

– POM_objectDisplays the business objects available for creating new business objecttypes.

– WorkspaceObjectDisplays the objects that can be displayed in the end user workspace.

– ItemDisplays the most commonly used business objects such as Item andDocument that are used to represent work objects to be tracked inTeamcenter.

4. Click Apply.

5. Click OK.



• Correction to note about relation properties

The following corrected note will be added to Migrate preferences to data modelobjects.

Note

If you are upgrading from an earlier version of Teamcenter to Teamcenter8, you should verify that all of your relation properties are now managedin the Business Modeler IDE. To verify, look in your preferences for each<relation_type>_relation_primary preference that you added, and addit 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, cannotbe attached at child business objects. User exit attached extensions getdefined 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 attachedto that property at child business objects. They can be attached to thatproperty at the same business object. However, extensions defined fora business object itself (not to its property) can be attached to a childbusiness 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, andprocedures used to satisfy requirements. A specification relationship canonly be established with an item revision, not an item. The reason for thisis that although requirements may remain fairly constant for a product(item), actual manufacturing methods, designs, processes, and proceduresmay change drastically from model to model (item revisions). Extendthe IMAN_specification business object to create your own specificationrelations.



– Requirement relations

Requirement relations are criteria that must be satisfied by this item oritem revision. However, requirements often do not specify how this criteriashould be satisfied. For example, a requirements relation may specifymaximum weight for an item revision but not how to construct it. Extendthe IMAN_requirement business object to create your own specificationrelations.

– Manifestation relations

Manifestation relations are nondefining snapshots of a particular aspectof 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 asthe item revision does not change. If the item revision does change, the NCprogram files may no longer be accurate and might need to be re-created.Extend the IMAN_manifestation business object to create your ownspecification relations.

– Reference relations

Reference relations describe a general nondefining relationship of aworkspace object to an item or item revision. This relation type can bethought of as a miscellaneous relation type. Typical examples of referencerelations are white papers, field reports, trade articles, customer letters, labnotes, and so on. Extend the IMAN_reference business object to createyour own specification relations.

• Addition to convert secondary business objects to primary topic

The following documentation will be added to Convert secondary business objectsto primary.

– The following will be placed at the end of the topic.

The following business objects are converted from secondary to primarybusiness objects in Teamcenter 8:

◊ Requirements Manager

RequirementsSpecRequirementParagraphSpecElement

◊ Aerospace and Defense

DrawingADSPartADSDesignADSDrawingADSTechDocument



◊ Document Manager

Document

◊ Structure Manager

PartDesign

– The following note will be placed in step 2 of the procedure:

Note

The Convert to primary context sensitive menu item is enabled only ifthe selected business object satisfies the following conditions:

◊ The seleceted object is a secondary business object and a custombusiness object.

◊ The parent of the selected object is a primary business object.

◊ The selected object is not derived under the ItemRevisionhierarchy.

– The following sentence will be placed in step 3 of the procedure after theexample of the business_model_updater utility:

Replace file-name with the name of the active extension file that containsthe data model definition for the converted business objects, such as thebusiness_objects.xml file.

C++ API Reference

The following release notes pertain to the C++ API Reference, an autogenerateddocument containing C++ signatures for Teamcenter APIs.

• C++ API Reference contains API for Foundation only

C++ API Reference contains C++ API documentation for the Foundationtemplate only. C++ API documentation for other features will appear in laterTeamcenter 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 Servicesis enabled on the host. If your Teamcenter configuration includes SecurityServices, you must configure the Dispatcher client to bypass Security Services.

For more information, see the Getting Started with Dispatcher (TranslationManagement) 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 informationabout the ERP Connect Toolkit switch is omitted.

–BOM_Pack_with_diff_seq_no

Indicates the sequence number, by default, is ignored while packing theBOM in ERP Connect Toolkit.

If set to Y, the sequence number is considered; if the sequence numbers of alloccurrences 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 relationproperties

The following information replaces the procedure in the Execute a saved querybased on properties on relations topic:

1. Open My Teamcenter.

2. Locate the quick search box at the top of the navigationpane.

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 Searchesfolder, and select the appropriate properties on the relations search query.

Note

Searches for properties on relations must first be created using theQuery Builder application. After you create the searches, they appearin the System Defined Searches folder.

For information about creating searches based on properties onrelations, 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 querybased 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 ClientInterface Guide.

2. Locate the quick search box at the top of the navigationpane.

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

Note

Searches for properties on relations must first be created using theQuery Builder application. After you create the searches, they appearin the System Defined Searches folder.

For information about creating searches based on properties onrelations, 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 (TranslationManagement).

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

Note

If you run the dispatcher client as a service, Siemens PLM Softwarerecommends running the scheduler and modules also as a service.

1. If you use Teamcenter, set the TC_DATA and TC_ROOT system variablesas appropriate.

Examples:

TC_DATA=C:\Progra~1\Siemens\tcdata

TC_ROOT=C:\Progra~1\Siemens\Teamcenter8



Note

When you install Teamcenter, TEM automatically sets theFMS_HOME system variable.

The Dispatcher Client service fails to start as a Windows service if youdo not set the TC_DATA and TC_ROOT system variables.

2. Run the runDispatcherClientWinService.bat file from theDispatcherClient\bin directory.

3. From the Windows Services console, right-click DispatcherClientversionservice and choose Properties.

4. In the Log On pane, select the This account option to assign a logon accountfor the Dispatcher Client service.

Note

You must provide administrator privileges for the Dispatcher Clientservice.

5. Start the Dispatcher Scheduler.

6. Start the DispatcherClientversion service.

Note

Start the scheduler and modules before you start the dispatcher client toavoid connection delays and translation failures.


The Dispatcher client cannot start if Security Services is enabled on the host. Ifyour Teamcenter configuration includes Security Services, you must configurethe 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=Tc8SSOrem set TC_SSO_SERVICE=http://host:port/ssoService8rem 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:

CopyDispatcher-home\Dispatcherclient\bin\runDispatcherClient.batto runDispatcherClient_nonsso.bat

UNIX systems:

CopyDispatcher-home/Dispatcherclient/bin/runDispatcherClient.sh torunDispatcherClient_nonsso.sh

4. In the runDispatcherClient_nonsso file, modify the TC_DATA variableto point to the TC_DATA_nonsso directory.

5. Run the runDispatcherClient_nonsso.bat file (Windows systems) orrunDispatcherClient_nonsso.bat file (UNIX systems) to start or stop theDispatcher client. This script runs the Dispatcher client without SecurityServices.

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

Global Services provides themaximum.query.objects parameter and propertythat can be used to avoid Java virtual machine (JVM) memory error conditions.You can set the parameter in a Global Services connector configuration file, oryou can set the property in the globalservices.properties file. Global Servicessets 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 overriddenfor specific connectors. You can use the max_objects_limit parameter in theGlobal Services business object definition (BOD) to set the maximum value that auser can select from the Max Objects list on the BOD query form. The existingmax_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 ServersGuide.

General documentation notes

The following notes contain general corrections and additions to the Installation onUNIX and Linux Servers Guide.

• Using downloaded Lifecycle Visualization software distribution images

In J2EE Web tier installation in the Rich client distribution instancerequirements topic, the following note will be added to the bulleted paragraphabout the Lifecycle Visualization software distribution image:

Note

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

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

2. Extract all these files into a single directory.

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

• Installing Teamcenter patches

The following corrections apply to Installing Teamcenter patches.

– In Distribution of Teamcenter updates, the correct name of the LifecycleVisualization (referenced as Teamcenter Visualization) patch file isproduct-level_number_PV_all.zip.

– Patching Teamcenter Environment Manager refers to the patch file asinstall.zip. The actual file name is patch-id_install.zip.

– In Patching Teamcenter Environment Manager, in step 1, substep d, thenote should read as follows:

Note

◊ Add the path to your TC_ROOT/install/install directory to yourPATH environment variable and enter the unzip command again.

◊ Enter the unzip command with the full path to yourTC_ROOT/install/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 isTC_ROOT/install/tem.sh.

– In Install patches on the corporate server, step 3, the note incorrectly statesTEM stops Teamcenter services during the update process. On UNIX andLinux systems, you must manually stop all Teamcenter services beforeinstalling patches.

– In Install patches on the corporate server, step 5, substep b should read asfollows:

Extract the platform/tc/data directory from the patch-id.zip file and copythe contents to your TC_DATA directories.

– At the end of Install patches on the corporate server, the two steps thatdescribe 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 fileshould be deleted. The portal_patch.jar file is no longer included in patches.

– In Patch Lifecycle Visualization, step 1, the list of platform-specific patchfiles should be replaced with one file: patch-id_PV_all.xip. This file containsLifecycle 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 Installerwith the following exceptions:

1. In step 5, select the instance that contains the TeamcenterVisualization 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 )Patchsolution.

3. Repeat steps 5 through 9, selecting the instances that contain theTeamcenter Visualization 8 (Embedded Viewer) for Rich Client4–Tier (installation and Configuration) solution and selecting theTeamcenter Visualization 8 (Embedded Viewer) for Rich Client4–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 containsthe patch set README file. Review this README file for informationabout the patch and possible additional steps required to complete the patchinstallation.

Environment settings for non-English locales (UNIX and Linux systems)

Note

This topic replaces the Environment settings for non-English locales topic inthe Installation on UNIX and Linux Servers Guide.

Teamcenter 8 is supported in the following locales on all server platforms:

• English• French• German• Italian• Spanish• Czech

• Hebrew• Russian• Japanese• Korean• Simplified Chinese• Traditional Chinese

To ensure correct display and processing of Teamcenter data, set the requiredvalues in your system environment and your Teamcenter configuration. Use theappropriate values for your locale and platform.

Note

To display multibyte character strings correctly on platforms that supportmultiple encodings of a given language, the specified system locale for a shellmust match the windowing system.

Environment settings for non-UTF-8 environments

For non-English locales on UNIX systems, specify the system locale by setting theLANG and LC_ALL environment variables using the Common Desktop Environment(CDE) at login to the system. These two variables must be identical to functionproperly. 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_ENCODING_SET2 3 4

ISO8859_1 ISO8859_1 ISO8859_1 ISO8859_1

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



ISO8859_1 ISO8859_1 ISO8859_1 ISO8859_1

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



ISO8859_1 ISO8859_1 ISO8859_1 ISO8859_1

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



ISO8859_1 ISO8859_1 ISO8859_1 ISO8859_1

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



ISO8859_1 ISO8859_1 ISO8859_1 ISO8859_1

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



ISO8859_2 ISO8859_2 ISO8859_2 ISO8859_2

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



ISO8859_5 ISO8859_5 ISO8859_5 ISO8859_5

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



ISO8859_8 ISO8859_8 ISO8859_8 ISO8859_8


Character set EUC EUC EUC EUCJapanese(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


EUC_JP EUC_JP EUC_JP EUC_JP

TC_language_default5 jp jp jp jp

Character set Shift-JIS Shift-JIS Shift-JIS Shift-JISJapanese(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


SJIS SJIS SJIS SJIS


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


EUC_KR EUC_KR EUC_KR EUC_KR

TC_language_default5 kr kr kr kr

Character set CGB2312-80 CGB2312-80 CGB2312-80 CGB2312-80SimplifiedChinese

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


GBK GBK GBK GBK

TC_language_default5 cn cn cn cn

Character set BIG5 BIG5 BIG5 BIG5TraditionalChinese

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


Big5 Big5 Big5 Big5

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 UNIXor 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 (CommonDesktop Environment) to configure the system to run Unicode UTF-8 characterset operating system. This is required so that all software running in thisoperating system environment understands the default character set is UTF-8.

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

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

• You must configure the Teamcenter thin client to connect to a four-tier UTF-8server installation that is running on a UNIX or a Linux platform that is runningthe Unicode UTF-8 operating system.

The thin client may be run in a Web browser that is running on any SiemensPLM Software supported platform and language character set encodingoperating system.

• You must configure the Teamcenter rich client to connect to a four-tier UTF-8server installation that is running on a UNIX or a Linux platform that isrunning the Unicode UTF-8 operating system. The rich client may be installedover-the-Web to a Windows platform that is running any Siemens PLM Softwaresupported language character set encoding operating system. The rich clientmay be installed over-the-Web to a UNIX or Linux platform that must berunning the Unicode UTF-8 character set encoding operating system.

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

Note

If your Teamcenter database server uses the UTF-8 character set, yourTeamcenter 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 restrictedUnicode UTF-8 character set support with clients displaying multiple locales.



Unicode homogeneous server platform configuration

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

Locale Value IBM AIX HP HP-UXSunSolaris 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:






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:






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

Character set UTF-8 UTF-8 UTF-8 UTF-8SimplifiedChinese


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

Character set UTF-8 UTF-8 UTF-8 UTF-8TraditionalChinese


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 onWindows 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 thenameMSSQLSERVER. Teamcenter’s persistent object manager (POM)utilities cannot connect to an instance with this name. If you use a defaultinstance, make sure you connect to the instance using a port connectionrather than the name.

If you use a named instance, make sure the instance has a unique nameother than MSSQLSERVER.

• Online help search configuration for Microsoft IIS

If you install the Teamcenter online help collection on Microsoft InternetInformation Server (IIS), you must enable certain MIME types on the server toenable 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, andthen click OK.

Note

If you want to serve all files, regardless of the file name extension, you cantype an asterisk (*) in step 6. You should only use the wildcard mappingto the IIS MIME map as a temporary solution during troubleshooting. Ifyou determine that a missing MIME type is the cause of the issue, removethe wildcard mapping and add the specific mapping for the MIME typethat 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 LifecycleVisualization (referenced as Teamcenter Visualization) patch file isproduct-level_number_PV_all.zip.

– Patching Teamcenter Environment Manager refers to the patch file asinstall.zip. The actual file name is patch-id_install.zip. Also, you shouldextract this file to your TC_ROOT\install directory, not TC_ROOT.

– In Patching Teamcenter Environment Manager, in step 1, substep d, thenote should read as follows:

Note

◊ Add the path to your TC_ROOT\install\install directory to yourPATH environment variable and enter the unzip command again.

◊ Enter the unzip command with the full path to yourTC_ROOT\install\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 asfollows:

Extract the platform\tc\data directory from the patch-id.zip file and copythe contents to your TC_DATA directories.

– At the end of Install patches on the corporate server, the two steps thatdescribe 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 fileshould be deleted. The portal_patch.jar file is no longer included in patches.



– In Patch Lifecycle Visualization, step 1, the list of platform-specific patchfiles should be replaced with one file: patch-id_PV_all.xip. This file containsLifecycle 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 Installerwith the following exceptions:

1. In step 5, select the instance that contains the TeamcenterVisualization 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 )Patchsolution.

3. Repeat steps 5 through 9, selecting the instances that contain theTeamcenter Visualization 8 (Embedded Viewer) for Rich Client4–Tier (installation and Configuration) solution and selecting theTeamcenter Visualization 8 (Embedded Viewer) for Rich Client4–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 containsthe patch set README file. Review this README file for informationabout the patch and possible additional steps required to complete the patchinstallation.

Environment settings for non-English locales (Windows systems)

Note

This topic replaces the Environment settings for non-English locales topic inthe Installation on Windows Servers Guide.

Teamcenter 8 is supported in the following locales on all server platforms:

• English• French• German• Italian• Spanish• Czech

• Hebrew• Russian• Japanese• Korean• Simplified Chinese• Traditional Chinese



To ensure correct display and processing of Teamcenter data, set the requiredvalues in your system environment and your Teamcenter configuration. Use theappropriate values for your locale and platform.

For non-English locales on Windows systems, specify the system locale by settingthe LANG and LC_ALL environment variables using the Windows Control Panel.These two variables must be identical to function properly. Set these and othervalues as described in the following table.

Environment settings on Windows systemsLocale 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:

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



Environment settings on Windows systemsLocale 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

Character set MS936 MS936 MS936SimplifiedChinese

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

Character set MS950 MS950 MS950TraditionalChinese

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:

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



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 thetc_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 TeamcenterEnvironment Manager (TEM) when you install a proxy server. TEMcreates this directory under the TC_ROOT directory and namesthe directory using the value you specify in the ID box in the NewConfiguration 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 defaultportmapper bypass setup, use the rpcinfo system utility to verify thatthere is no existing IDSM RPC configuration on the host. Any existingconfiguration must be removed to avoid conflicts with the default bypassportmapper configuration.

• IDSM launching utility

The UNIX configuration procedure in this topic is missing the following stepbetween steps 4 and 5:

4a. Type the following command to set the IDSM rpc program number usingthe –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 otherthan the default value. If you use this argument, you must set theTC_daemon-name_site-name_prog_number site preference to the value youspecify. 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 interoperabilitybetween versions. Teamcenter 8 interoperates with Teamcenter 2007,Teamcenter Engineering 2005, Teamcenter Engineering 2007, and Teamcenter’sengineering 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 processmanagement 2008

Teamcenter 8

Certain functional limitations, configuration requirements, and schemachanges are inherent to interoperability because the data model evolves toprovide increased functionality. In most cases, schema differences are handledtransparently by Multi-Site Collaboration. However, some schema changesrequire new Teamcenter 8 features to be temporarily disabled until all sitesare 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 intoprevious versions; they are ignored.

– New attributes in Teamcenter 8 added to POM classes that existed inearlier versions are exported from Teamcenter 8 but not imported intoearlier versions. When you import these attributes from earlier versions toTeamcenter 8, they are assigned null values.

– If a new type is added in Teamcenter 8, such as a relation type or datasettype and is exported to earlier versions, the type must be defined at theearlier version site using an appropriate tool. An appropriate tool may beBusiness Modeler IDE for a Teamcenter site or the install_types utility inEngineering Process Management. For relation types, you can define theITEM_do_not_export_relation_if_type_excluded site preference at theTeamcenter 8 site to list the new relation types added in Teamcenter 8 thatshould 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 mustfirst be upgraded to Teamcenter 8.

Teamcenter 8 clients cannot publish to an ODS server running an earlierversion.

– Teamcenter 8 sites that must share data with any Teamcenter Engineeringversions (Teamcenter Engineering 2005 SR1, Teamcenter Engineering 2007,and Teamcenter’s engineering process management 2008), cannot uselonger IDs and names. Verify that the TC_Allow_Longer_ID_Name sitepreference is either not defined or set to FALSE. You can set this preferenceto TRUE when all participating sites are at Teamcenter 2007 or later.

– Teamcenter 8 sites that must share data with earlier versions musttemporarily disable the sequence feature that was introduced in Teamcenter2007, by setting the TCCheckoutReserveOnly site preference toWorkspaceObject. By default, the sequence feature is for all subclasses ofWorkspaceObject. You can disable or modify this preference for specificclasses once all participating sites are at Teamcenter 2007 or later.

– For Teamcenter 8 and sites that predate Teamcenter 8, set theTC_ALLOW_INCOMPATIBLE_TYPES environment variable to TRUE.

– Several allocation schema changes are made in Teamcenter 2007.To exchange allocations data, sites that predate Teamcenter2007 and that interoperate with Teamcenter 8 must run theupgrade_data_v1001mpx_multisite.default script on the version thatpredates Teamcenter 2007.

The upgrade_data_v1001mpx_multisite.default script, which isavailable with Teamcenter Engineering 2005 SR1 MP3 and subsequentversions, makes the following changes to the allocations schema:

◊ Modifies the properties of Allocation attributes source_absOcc_tag,target_absOcc_tag, andmap_rev_tag to allow null values.

◊ Modifies the properties of AllocationMap attributes source_bv_tagand target_bv_tag to allow null values.

◊ Introduces the ManagedRelation class, a subclass ofWorkspaceObject.

– For Teamcenter Engineering 2005 SR1, Teamcenter Engineering 2007, andTeamcenter’s engineering process management 8 sites to interoperate withTeamcenter 8 sites, the administrator must make the following schemachange 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 ItemRevisionvariant_expression_block POM_null_is_valid +



install -mod_attr infodba infodba dba PSOccurrencevariant_condition POM_attr_follow_on_export +

install -set_attr infodba infodba dba PSOccurrencevariant_condition NULLTAG

install -mod_attr infodba infodba dba PSOccurrencevariant_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 8sites, the administrator must make the following schema change manuallyat the Teamcenter 2007 site:

◊ Make valid the resource_tag attribute from ScheduleMember withNULL.

install -mod_attr -u=infodba -p=infodba -g=dbaScheduleMember 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 transmitfiles after making these schema changes. The new transmit files mustbe distributed to the other sites.

– Modifying a remote checked-out assembly is not saved

When using Teamcenter Integration for NX assemblies in a multisiteTeamcenter configuration, you cannot save a remote checked-out assembly.

Use Multi-Site Collaboration import/export with transfer ownership insteadof checkout to make these changes.

– Remote checkin behavior

If you attach a local object to a replica using remote checkout, upon remotecheckin, the attached local object can be transferred with ownership, can besent as replica, or cannot be sent at all. You can configure this behavior fromthe user interface and preference.

From the Remote Checkin dialog box advanced options, you can select arelation to be transferred with ownership. The option to send a replica isnot yet available in the user interface. Therefore, a relation listed in theTC_remote_checkin_relation_send_as_replica preference is sent as areplica.

When you select a particular relation from the user interface, the followingtable explains the local attached behavior.



Relationincluded inuser interface

Relationspecified inpreference 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 addedwhen it exchanges data with Teamcenter 8 may be problematic when thefollowing occur:

◊ A Teamcenter 8 site has been upgraded from Teamcenter Engineering2005 SR1 or Teamcenter 2007.

◊ The upgraded Teamcenter 8 still exchanges data with TeamcenterEngineering 2005 SR1 or Teamcenter 2007 sites.

◊ There are new subtypes created in the earlier Teamcenter Engineering2005 SR1 and Teamcenter 2007 after the other sites in the federation areupgraded to Teamcenter 8.

The administrator should contact GTAC for assistance.

– Data exchange between Teamcenter 8 sites and Teamcenter 2007 MP1x orMP2x sites may generate errors in the following situations:

◊ Execute data_share –remote_import from the Teamcenter 8 site for anobject owned at a Teamcenter 2007 MP1x or MP2x site. The followingerror 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 owningTeamcenter 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 8site for an object owned by a Teamcenter 2007 MP1x or MP2x site. Thefollowing error message is generated:

POM INTERNAL ERROR - please report this.

In these situations, the Teamcenter version does not support data exchangewith Teamcenter 8. If possible, the administrator should upgrade the siteto Teamcenter 2007.1 MP3 or a later version. Otherwise, the administratorshould contact GTAC for assistance.



Preferences and Environment Variables Reference

The following release notes pertain to the Preferences and Environment VariablesReference. 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_importpreferences are obsolete. These preferences were for internal Siemens PLMSoftware 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 withDatasetType are reversed and a note is added.

• TC_ugmaster_name_separator preference

The TC_ugmaster_name_separator preference is new.



ETS_update_state_delay

DESCRIPTIONSpecifies the delay time in seconds after which a dispatcher request object can beupdated.

When there are multiple dispatcher clients in a translation server installation,multiple dispatcher clients can update the state of the same dispatcher requestobject. The delay time makes sure that only one dispatcher client updates thedispatcher request object.

Note

If you set a high delay time, the performance of the dispatcher request maybe affected. Siemens PLM Software recommends that the delay time shouldnot be greater than 5 seconds.

VALIDVALUES

Must be a single positive integer.

DEFAULTVALUES

0

SCOPESite preference.



PLMXML_put_pie_log_in_syslog

DESCRIPTIONSpecifies whether the contents of the PLM XML import/export (PIE) log file is copiedto the syslog file or not. This PIE log file is in the same location as the PLM XMLfile of the same name and contains the results of any PLM XML import or exporttransaction.

VALIDVALUES

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.

DEFAULTVALUES

FALSE

SCOPEUser preference.



TC_NX_Foreign_Datasets

DESCRIPTIONSpecifies the non-NX dataset types available to NX when it lists the datasets inan item revision.

Note

Specifying dataset types in this preference only makes the dataset typesavailable to NX, it does not enable the application to read the dataset type.

VALIDVALUES

The value format is four keywords and their values. The keywords are:

DatasetTypeNamedReferenceNamedReferenceFormatNamedReferenceTemplate

The format informs NX precisely which named references of the dataset contain theCAD data. Values are enclosed in quotation marks.

Valid values for the NamedReferenceFormat keyword are BINARY or TEXT. Thenamed 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 linefor each dataset type.

DEFAULTVALUES

None.

SCOPEAll.



TC_ugmaster_name_separator

DESCRIPTIONSpecifies the separator character used when generating dataset IDs from the parentitem ID and revision for UGMASTER datasets created through the NX Integrationor 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.

DEFAULTVALUES

None.

SCOPESite 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 bydrag-and-drop topic.

On Microsoft Windows systems, you cannot create a new dataset by dragging afile from the Windows Desktop or from the Desktop folder at the top of WindowsExplorer.

1. Navigate to the Desktop folder within your user profile directory.

Note

The Desktop folder in your user profile directory is typically locatedon 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 andconfiguration descriptions.

In subsequent releases of the documentation set, much of this information willbe relocated to installation, configuration, and administration guides.



Note

– The PdfGenerator translator (under Document Management(DocMgt) Translators in TEM) is not supported on UNIX or Linuxsystems.

– If you install render management on a 64-bit Sun Solaris host, youmust install the 64-bit version of Teamcenter 8 lifecycle visualizationConvert. The Sun Solaris 64-bit installation image can be downloadedfrom the Teamcenter Visualization/JT Translators area of theSiemens PLM Software FTP site. The image is also available on theTeamcenter 8 lifecycle visualization DVD provided with Teamcenter8, SAP number 80-033077-080.

• Online help access from views

Online help is not always installed, and for some views, online help is notavailable from the Help®Current Application menu command, the F1 key, orboth.

When online help for a view is not available from the function key or menucommand, 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 applicationperspectives®Rich client views.

4. Locate the view for which you are seeking online help and click the linkto display additional information.

• Create an ad hoc Classification search

Step 9 of the Create an ad hoc Classification search procedure incorrectly statesthat values for the classification search criteria can be changed in either thesearch pane or the Adhoc Classification Query dialog box.

The values for the classification search criteria can only be changed in the AdhocClassification Query dialog box.

• Search for data using Classification attributes

To search for data using Classification attributes, create an ad hoc Classificationsearch.

For more information about creating an ad hoc Classification search, see theCreate 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 informationwill be added:

– Although support for schedules in a multisite environment is available inTeamcenter 8, the multisite schedule feature is not interoperable with sitesusing earlier versions of Teamcenter.

– You must replicate all resources (users, groups, roles, and disciplines) to allsites using the dsa_util utility. When you export a user using the dsa_utilutility, the associated groups, roles, disciplines, and calendars (both resourceand its base) are also exported.

– Base calendar names must be unique across all sites. Siemens PLM Softwarerecommends you use the site name or another unique identifier as part ofthe name for base calendars. Base calendars are exported to other siteswhen users with resource calendars that refer to these base calendars areexported 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 musthave an Author license.

– Add the SchDeliverable and SchTaskDeliverable values to theTCCheckoutReserveOnly site preference.

– Custom values added to LOVs associated with billing code, billing subcode,cost currency, and time zone properties at any site cannot be automaticallysynchronized across all sites. Therefore, these values must be maintainedmanually at other sites using Business Modeler IDE to avoid inconsistenciesas follows:

◊ In the Business Modeler IDE, update the custom values for the LOVsassociated with billing code, billing subcode, cost currency, and timezone properties.

◊ Deploy the changes through Teamcenter Environment Manager (TEM).

– Naming rules must be created and attached to the ItemID property ofSchedule and ScheduleTask classes. The rule for ItemID must contain aunique identifier such as SiteID to prevent issues with duplicate IDs.



Note

Attach the rule only to the ItemID property and not to the Nameproperty.

– You must manually synchronize changes to bill rates at any one site acrossall sites by interactively updating bill rate data using the Bill Rates dialogbox. Access this dialog box by choosing Schedule→Bill Rates in ScheduleManager.

– Resource graph

To generate an accurate resource graph for a user at a site, all schedules inwhich the user has resource assignments must exist on that site. SiemensPLM Software recommends exporting all schedules to all sites that needto view resource graphs for users.

– Program view

To be viewed on a remote site, all schedules referenced by a program viewmust 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 usingimport/export of templates.

◊ The ProjectTrans service used by Schedule Manager is configured toretry 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 asis, especially in a multisite environment. If there are any translationrequest failures beyond the five default retries, you must manuallyresubmit the translation requests from the Translation Admin Consoleor increase the NoOfTries value.

– You must select the relations highlighted in the following figure duringremote 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, Transferin, and Remote checkout access privileges as shown in these figures.

◊ Also, site administrators must add System Administrator accesscontrol entry (ACE) tables in the Scheduling Objects and SchedulingExecution Objects ACLs and give that user Read,Write, and Deleteaccess privileges as shown in the following figures.

◊ You only need to change the Scheduling Objects ACL rule once. It thenapplies 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 Executionform.



The following figure illustrates the access changes for the Task Schedulingform.

The following figure illustrates the access changes for the Cost form.

Security Services Installation/Customization

The following notes pertain to the Security Services Installation/Customizationguide.


On Windows systems, the Dispatcher client cannot start if Security Services isenabled on the host. If your Teamcenter configuration includes the Dispatcherclient, you must configure it to bypass Security Services.


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 APIdocumentation for C++ (cpp/docs). The services C++ API documenation can befound 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 Buildingand editing product structure topic.

During prototyping or other changes, you may delete an item or part andsubsequently add another item or part in the product structure.

To convert the separate delete and add operations into a single replacementoperation during BOM comparison:

1. Open two product structure windows side-by-side and configure two differentBOM view revisions (BVRs) showing the individual operations. For example,configure a BVR showing the deleted part in one window and a second BVRshowing 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 replacementoperation, replacing the occurrence thread of the added part with the occurrencethread 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, thefollowing note should be added to the description of the Named Instance box:

Note

A default instance in a Microsoft SQL Server installation uses thenameMSSQLSERVER. Teamcenter’s persistent object manager (POM)utilities cannot connect to an instance with this name. If you use a defaultinstance, make sure you connect to the instance using a port connectionrather than the name.

If you use a named instance, make sure the instance has a unique nameother 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 setrequired values in your system environment and your Teamcenter configuration.

If your Teamcenter servers run UNIX or Linux and use the Unicode UTF-8character set, you must configure your operating system and your Teamcenterconfiguration to use Unicode UTF-8, observing the following considerationsduring Teamcenter upgrade:

– An existing Teamcenter installation must not configure Unicode UTF-8character set support with an upgrade to Teamcenter 8. An existingTeamcenter installation is required to complete an upgrade to Teamcenter 8under its existing database character set encoding.

– After upgrade is completed, you must contact your database vendor forprocesses and tools to convert your existing database character set encodeddata to Unicode UTF-8 character set encoded data for storage to a newdatabase.

For more information about environment settings for your locale, platform, andcharacter set, see the following topics:

– For information about environment settings for non-UTF-8 UNIX and Linuxsystems, see Environment settings for non-UTF-8 environments.

– For information about environment settings for UTF-8 UNIX and Linuxsystems, see Environment settings for UTF-8 environments.

– For information about environment settings for Windows systems, seeEnvironment 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 asfollows:

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 withthe ID of the Teamcenter configuration. 9001 is the server index port usedby the new Autonomy server.

This command uses index port 9001 to import your existing Autonomyindexed 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 theTC_fts_database_name preference.



Utilities Reference

The following release notes pertain to the Utilities Reference. A complete descriptionof 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 linearguments.

SYNTAXThe syntax of the dispatcher_create_rqst utility has two forms:

dispatcher_create_rqst–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:

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

–p Specifies the password corresponding with the user ID.

–g Specifies the group to which the user specified by the –uargument belongs.

–i Specifies the item.

–r Specifies the item revision.



–rn Specifies the relation name to be used to find the dataset for thegiven item revision. This argument is optional. If the relationis 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 noversion 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 3corresponding to low, medium and high translation schedulerpriority.

–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 dispatcherrequests. 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 datasetrelated to the Block/A item revision, enter the following command on a singleline:

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, enterthe following command on a single line:

dispatcher_create_rqst –u=infodba –p=infodba –g=dba–i=Block –r=A –dv=2 –dt=IdeasPart –pr=2 –pn=Siemens



–tn=ideastojt —ty=COMMAND_LINE

• To create two ideastojt dispatcher requests with a priority of 2, enter thefollowing command on a single line:

dispatcher_create_rqst –u=infodba –p=infodba –g=dba–f=ctrl –dt=IdeasPart,IdeasAssembly –pr=2 –pn-Siemens–tn=ideastojt —ty=COMMAND_LINE

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 orIdeasAssembly type dataset, associated with item revision Block/A byan IMAN_specification relation.

– One request for the latest version of the Asm dataset, an IdeasPart orIdeasAssembly type dataset associated with item revision Asm/A by anIMAN_specification relation.

Note

All parts in the file are subject to the same translation, because thetranslator 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 clientstopic.

Note

In Teamcenter 2007, localization was desynchronized between all tiers.Client, middle tier, and server could each use a different locale: thelocale of the machine where the rich client was running, the localedefined at middle-tier installation, and the server locale specified bythe TC_LOCALIZATION_DIR environment variable located in thetc_profilevars file. All processes in a pool manager used the sametc_profilevars file, and therefore, the same language. Therefore, in aglobally distributed enterprise with one pool manager running on a servermachine located in country A with locale L_A, all Teamcenter serverprocesses 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 processtemplate

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 Statustemplate to use as the base for the quick-release template. The TCM ReleaseStatus template consists of an Add Status task.

Basing your new quick release template on the TCM Release Status templateautomatically populates the Start task with the required create-statusand add-status handlers.

When you choose a template in the Based on Process Template box, taskinformation is displayed for the selected process template in the TaskHierarchy View, the Name and Description boxes, and the Task Flow View.This information can be viewed within the New Process dialog box; it cannotbe modified.

You can click the Task Attributes, Task Handlers, and Task Signoff buttonsto view the selected process template’s task attribute, task handler, and tasksignoff 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

DESCRIPTIONInforms 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 iftheMail_internal_mail_activated preference is set to True.

Note

The –report argument on the CR-notify handler differentiates theCR-notify handler from the notify handler. In notification e-mail, the–report argument appends a report describing the signoff data associatedwith the perform-signoff task. Therefore, you should use the CR-notifyhandler on the perform-signoff task, whereas the notify handler is moregeneric and can be used on any type of task.

SYNTAXnotify–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–recipientSpecifies the task reviewers receiving notification. Accepts one of the followingvalues:

• 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. Sendsnotification 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 issent to all members, subscribed members, or none based on the preferenceEPM_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 thespecified type. The type value is optional. Ifnot 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 currentreviewer and sends e-mail to all of them.

• $PROPOSED_REVIEWERS



Sends e-mail to all members assigned as the proposed reviewers of the firsttarget 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 thefirst 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 typevalue 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 rolespecified in the argument value and send a notification to them. The projectteam 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 isassigned 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 isassigned as a reviewer, and no signoff decision has been made for this resourcepool assignment, all members of that resource pool are notified.

When this argument is used along with $RESPONSIBLE_PARTY, and if aresource pool is assigned as responsible party, the e-mail is sent to all membersof that resource pool.

• $RESOURCE_POOL_NONE

Identifies all members of the resource pool.




When this argument is used along with $REVIEWERS or $UNDECIDED, andif a resource pool is assigned as a reviewer, e-mail is not sent to members orsubscribers of the resource pool.

When this argument is used along with $RESPONSIBLE_PARTY, and if aresource pool is assigned as responsible party, the e-mail is not sent to membersor 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 poolis assigned as a reviewer, the e-mail is sent to users who have subscribed tothe resource pool.

When this argument is used along with $UNDECIDED, and if a resource pool isassigned as a reviewer and no signoff decision has been made for this resourcepool assignment, e-mail is sent to users who have subscribed to the resource pool.

When this argument is used along with $RESPONSIBLE_PARTY, and if aresource pool is assigned as a responsible party, the e-mail is sent to users whohave subscribed to the resource pool.

Note

If the $RESOURCE_POOL_XXXXX argument is not defined andthe $REVIEWERS, $UNDECIDED, or $RESPONSIBLE_PARTYarguments are used for a case where assignments are made to resourcepools, the e-mail is sent using the EPM_resource_pool_recipientspreference.

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 argumenttakes precedence over preference value.

If this argument is not defined and the EPM_resource_pool_recipientspreference is not set, subscribed is considered the default value.

–subjectDisplays the task name enclosed in brackets, followed by the string identified by thisargument, on the OS mail’s subject line.



–commentsEmbeds user-defined comments in the body of the e-mail.

–urlInserts a DHTML link to the process into the notification e-mail, based on the valuefor –url. If no value is specified for –url, both links are added into the notificatione-mail.

If the –url argument is not defined, the notification e-mail contains links dependingon 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 isnot set in preference file, rich client and thin client links are added to the notificatione-mail as a default. The URL is generated only when theWEB_default_site_serverpreference is set to the thin client server node name.

Note

Rich client URL functionality must be enabled for links to rich client workflowprocesses to launch the rich client.

–attachmentAdds an attachment to a Teamcenter mail. This argument does not have any affecton 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.

PLACEMENTWhen $REVIEWERS or $UNDECIDED is used as the keyword, place on the Startor Complete action of the perform-signoff task.

RESTRICTIONSNone.

EXAMPLES• This example sends an e-mail with the subject Lower Right SubassemblyReview to all users on the design and qualityControl address lists. Thecomment 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 thatcontains 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 reportany concerns directly to the Product Manager

–attachment $TARGET, $PROCESS

• This example sends an e-mail to the designated responsible party for the task. Ifthe 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 ofthe group manufacturing, and members of the address list purchasing asrecipients of an e-mail with the subjectManufacturing Release ProcedureCompleted.

Argument Values

–subject Manufacturing Release Procedure Completed

–recipient OS:peters, OS:john, User:smith,Group:manufacturing, Role:manager,DistributionList:purchasing



CONTMGMT-notify

DESCRIPTIONNotifies the translation office through e-mail that a translation order is created.

SYNTAXCONTMGMT-notify[–subject=string][–comments=string][–attachment=$TARGET | $PROCESS | $REFERENCE][–url= [ {rich | dhtml | html} ] ][log]

ARGUMENTS–subjectDisplays the task name enclosed in brackets, followed by the string identified by thisargument, on the OS mail’s subject line.

–commentsEmbeds user-defined comments in the body of the e-mail.

–attachmentCauses an attachment to be included in a separate Teamcenter mail. (This argumentdoes not have any effect on the OS mail.) The type of attachment is one of thefollowing:

• $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 thevalue for –url. If no value is specified for –url, both links are added into thenotification e-mail.

If the –url argument is not defined, the notification e-mail contains linksdepending 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 preferenceis 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 theWEB_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 clientworkflow processes to launch the rich client.

logRecords the notify activity in the workflow audit file.

PLACEMENTPlace on the Start action of any task.

RESTRICTIONSNone.

Note

To specify multiple attachments, you must call the –attachment argumentmultiple times.

EXAMPLES• This example sends an e-mail with the subject Translation Order Submittedto the translation office. The comment described in the example appears in thebody of the e-mail text. In addition to the e-mail, the translation office alsoreceives a Teamcenter mail that contains both the workflow target attachmentsand 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 duringyour workflow process and to define how the process continues when errors occurand when they do not.

You do this by configuring both a success path and a failure path for the Validatetask. The success path is followed if no error occurs. The failure path is followedwhen 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 workflowhandler. Configure the task to follow a failure path by pairing a workflow handlerand an error code. Place a handler to be validated on the Validate task and thenadd the respective error code to the task path’s error list (or set the task path tofail on any error.)

Example

At Design, Inc., employees check out documents that are targets of workflowsand sometimes neglect to check them back in. Teamcenter does not allowusers 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 processis initiated. When the workflow reaches the review stage, and the requiredtargets are checked out, the workflow cannot complete.

In this example, this situation is anticipated and the Validate task is used toprovide a correction. The task is placed before the review stage of the workflowand configured to verify that all targets are checked in. If so, a success path isfollowed. If not, the workflow follows a failure path that includes an additionalDo task assigned to a manager. The Do task instructs the manager to get thetargets checked in, and then complete the Do task. After the error conditionis 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 byplacing 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 canpair any handler and error code to generate similar behavior. The task acceptsboth 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 tofollow a failure path when a target is not checked in. Typically, Teamcenter doesnot allow you to initiate a process on a target that is checked out. However, becausesituations arise in which targets are checked out after a process is initiated, thisvalidation can be a useful check.

Note

The following process is an example of how the Validate task is configuredto branch down a failure path when errors occur. You can pair any handlerand error code to generate similar behavior. The tasks accepts both shippedhandlers 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 andclick OK.

Alternatively, select an existing process you want to add the task to from theProcess 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 placethe 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 processtemplate. For example:

6. Link the existing Do task to the new Validate task.

Note

By default, the Validate task contains no handlers, allowing you toconfigure performance as required. In this example, you configurethe task to check whether the target is checked in by adding theCR-assert-targets-checked-in handler to the Start action.

7. In the Process Flow view, ensure the Validate task is still selected. In theTemplate 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 handlerarguments 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 buttonon the toolbar, then double-clicking in the Process Flow view to place the newtask 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 toFailure.



16. Create a success path between the Validate task and the Success task byplacing the cursor in the body of the Validate task and dragging it to the bodyof Success.

A line appears between the two tasks. If you leave this path unconfigured, itis a success path.

17. Create a failure path between the Validate task and the Failure task by placingthe 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 whenany error occurs. (If you select this option, skip to step 23.)

• Select Set Error Codes to specify which error codes you want the Validatetask to check. If you select this option, the Set Error Codes dialog boxdisplays.

19. In the Set Error Codes dialog box, type an EPM error code you want tocause the process to follow the failure path. For example, type 32009(RES_OBJECT_IS_RESERVED) to ensure the failure path is followedwhenever a target is not checked in.



Note

For more information about finding EPM error codes, see Finding errorcodes.

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 errorsyou 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 thisexample, an additional Do task is required on the failure path. The task isadded and renamed Check in Targets. The task instructions direct a manager toget 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 tothe 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, dependingon 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 ToolkitFunction 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 taskto 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 theEPM_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 andwhat errors are received.

Failure criteria youspecified Error thrown (if any) Task behavior

Fail if any error Any error Failure path is followed.

Fail if error on error listoccurs Error on error list Failure path is followed.

Fail if error on error listoccurs Error not on error list

Process halts. Taskremains in Started stateand an error displays.

No failure path configured Any errorProcess stops. Taskremains in Started stateand an error displays.

Regardless of whetherfailure path wasconfigured, and whethererrors occurred

No errors occurSuccess path followed.If no success path wasconfigured, process stops.


Chapter

4 Carried forward release notes

Release notes carried forward from Teamcenter 2007 . . . . . . . . . . . . . . . . . . . 4-1Teamcenter 2007 product release notes . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Installation release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Upgrade release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Usage release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Managing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Managing reports, requirements, and schedules . . . . . . . . . . . . . . 4-16Managing manufacturing data . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Sharing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Teamcenter Automotive Edition–GM Overlay . . . . . . . . . . . . . . . . 4-29

Administration release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33Teamcenter File Services and FMS administration . . . . . . . . . . . . 4-34Teamcenter Integration for NX . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37Security Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Customization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45Integration Toolkit (ITK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45Service-oriented architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46

Teamcenter interfaces release notes . . . . . . . . . . . . . . . . . . . . . . . . . 4-47Rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47Thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48

Teamcenter integrations release notes . . . . . . . . . . . . . . . . . . . . . . . . 4-49Teamcenter EDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49Teamcenter’s Client for Microsoft Office . . . . . . . . . . . . . . . . . . . . 4-50Teamcenter’s Integration for Microsoft Office and Teamcenter’s NetworkFolders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51

Internationalization release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51Platform-specific release notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52UNIX platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52Hewlett-Packard HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57IBM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59SUSE Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61

Release notes for Teamcenter-related products . . . . . . . . . . . . . . . . . . 4-62Teamcenter’s lifecycle visualization (Lifecycle Visualization) releasenotes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62Teamcenter’s reporting and analytics release notes . . . . . . . . . . . . 4-65Managing Teamcenter’s mechatronics process managementdata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66


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


Chapter

4 Carried forward release notes

The following notes are carried forward from previous versions. These notes stillapply to the current version.

Release notes carried forward from Teamcenter 2007The following notes are carried forward from Teamcenter 2007. These notes stillapply to the current version.

Teamcenter 2007 product release notes

The following release notes pertain to the upgrade, installation, administration, datasharing, 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 operatingsystem, 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 .NETIIS Registration Tool (Aspnet_regiis.exe), seehttp://msdn.microsoft.com/en-us/library/k6h9cz8h(VS.80).aspx.


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 -sW3SVC/IIS_Web_Site_Identifier/ROOT/"virtual_directory_or_web_application_name"

IIS_Web_Site_Identifier is the actual ID that references theWeb site and can be found in the IIS Manager column calledIdentifier. virtual_directory_or_web_application_name is thename of the Web application. For example, aspnet_regiis.exe -sW3SVC/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-tierconfiguration as a common installation for more than one operating system user,after the first user has logged on, subsequent users get a Permission Deniedexception 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-tierrich 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 atWindows reboot

(First published Engineering 2005 SR1)

Teamcenter File Services (TCFS) does not always automatically start onWindows reboot.


Increase the ServicesPipeTimeout value in the registry to 120,000milliseconds. 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 theHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control registrysubkey.

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 servicetimes 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 previousversion of Teamcenter Engineering or Teamcenter 2007.

• Orphan types reinstated


Classes and types installed by Teamcenter’s engineering process managementprior to version 9.1.3 that are now obsolete were not removed from the databaseduring upgrades to later versions. New databases installed for version 9.1.3 orlater do not have these obsolete classes and types. The result is data modeldiscrepancies between databases and must be corrected by deleting specific typesand reinstating others to the foundation template so that all data models areconsistent regardless of the upgrade or install path.

Note

Types in Engineering Process Management are called business objectsin Teamcenter.


– Upgrading your database from Engineering Process Management to anyversion of Teamcenter.

If you upgraded your database from Engineering Process Management toany version of Teamcenter, the upgrade attempts to remove the followingdefinitions if there are no instances. If there are instances, Teamcenterassumes you are still using them so they are not deleted. After the upgrade,the post_bmideupgradetotc utility extracts these definitions if they existand places them into your custom template. If you find the types listed inthe following code, their ownership has been transferred from Teamcenter toyour custom template. You may keep them or delete them.

<TcStandardType typeName="IMAN_analysis" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_basis" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_derivation" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_evolution" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_markup" parentTypeName="ImanRelation"ypeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_master_model" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_model" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_nc_data" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_revision" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_structure" parentTypeName="ImanRelation"typeClassName="ImanRelation"/>

<TcStandardType typeName="IMAN_structure_model" parentTypeName="ImanRelation"typeClassName="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"typeClassName="Form"/>

<TcForm typeName="EquipmentRevision" parentTypeName="Form"typeClassName="Form"/>

<TcForm typeName="EquipmentRevision Master" parentTypeName="Form"typeClassName="Form"/>



– Upgrading your database from Engineering Process Management to anyversion of Teamcenter prior to 2007.1 MP4 and then to Teamcenter 2007.1MP4 or later.

If you upgraded your database from Engineering Process Management toTeamcenter 2007.1 MP1, MP2, or MP3, your custom Business ModelerIDE template likely has some or all of the reinstated classes and types init because the upgrade process required you to extract a custom templatewith the post_bmideupgradetotc utility. Because these classes and typesexisted in your database, yet none had any XML representation in thefoundation template, the utility pulled them into your template. If you planto continue using one of these versions of Teamcenter, do not remove theseXML definitions from your custom template. It will be fixed once you move toa later version. When you upgrade this database to Teamcenter 2007.1 MP4or later, these classes and types have XML representation in the foundationtemplate. Since both your template and the foundation template have thesame definitions, these names will collide. Typically you see these collisionsoccur during an upgrade, when installing a new feature on the server usingTeamcenter Environment Manager or when using Business Modeler IDE. Tofix this, remove these definitions manually from the XML source files in yourcustom Business Modeler IDE template.

1. Install the most recent version of the Business Modeler IDE client andthe templates that you require. For example, if you are upgrading toTeamcenter 2007.1 MP4, install the Teamcenter2007.1 MP4 BusinessModeler IDE client and templates.

2. Import your previous Business Modeler IDE custom template projectinto the new Business Modeler IDE client.

3. During the import, the custom data model is validated against the newout-of-the-box template definitions. Any collisions are shown in theConsole view in the Business Modeler IDE client. A collision in theBusiness Modeler IDE for a class or type looks similar to the following:

Model Error: business_objects.xml Line:19 Column:57 A Class isalready defined with the name "POM_index". Choose another name.

Model Error: business_objects.xml Line:45 Column:111 A BusinessObject is already defined with the name "CORCoreDList". Chooseanother name.

4. For each collision, check if the colliding definition is in the list ofreinstated types that follows. Note that name collisions can occur forother reasons, such as defining a custom type that has the same name asa out-of-the-box type. These kinds of collisions that you created must befixed in a different manner. If the collision listed in the Console viewmatches one of the definitions listed below, then manually remove theXML definition from your source file.

Note

Some of the XML definitions listed many not appear in yourtemplate. 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"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="start_pos" attributeType="POM_int" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="char_type" attributeType="POM_string" maxStringLength="1"isArray="false" followOnExport="false" isNullsAllowed="true" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="init_value" 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="max_value" 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="next_id" 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"/>

</TcClass>

<TcClass className="NameFields" parentClassName="POM_application_object" isExportable="true"isUninstantiable="false" isUninheritable="false" applicationName="INFOMANAGEV200">

<TcAttribute attributeName="type_name" attributeType="POM_string" maxStringLength="32"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="property_name" attributeType="POM_string" maxStringLength="32"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="case" attributeType="POM_int" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="rule_tag" attributeType="POM_typed_reference" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="true" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="NameRules"/>

</TcClass>

<TcClass className="NameRules" parentClassName="POM_application_object" isExportable="true"isUninstantiable="false" isUninheritable="false" applicationName="INFOMANAGEV200">

<TcAttribute attributeName="rule_name" attributeType="POM_string" maxStringLength="32"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="true"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="pattern" attributeType="POM_string" maxStringLength="240"isArray="true" followOnExport="false" isNullsAllowed="true" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="-1"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="autogen" attributeType="POM_logical" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<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"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="mapped" attributeType="POM_logical" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

</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"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<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"isUninstantiable="false" isUninheritable="false" applicationName="POM">


</TcClass>

<TcClass className="POM_column" parentClassName="POM_rdbms_dd" isExportable="false"isUninstantiable="false" isUninheritable="false" applicationName="POM">


<TcAttribute attributeName="object" attributeType="POM_typed_reference" maxStringLength="0"



isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="POM_rdbms_dd"/>

<TcAttribute attributeName="type" attributeType="POM_int" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="length" attributeType="POM_int" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

<TcAttribute attributeName="nulls_allowed" attributeType="POM_logical" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

</TcClass>

<TcClass className="POM_index" parentClassName="POM_rdbms_dd" isExportable="false"isUninstantiable="false" isUninheritable="false" applicationName="POM">


<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"/>

<TcAttribute attributeName="table" attributeType="POM_typed_reference" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false" typedRefClassName="POM_table"/>

<TcAttribute attributeName="unique" attributeType="POM_logical" maxStringLength="0"isArray="false" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="true" isPublicWrite="false" isCandidateKey="false" arrayLength="0"isTransient="false" exportAsString="false" noBackpointer="false"/>

</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"isArray="true" followOnExport="false" isNullsAllowed="false" isUnique="false"isPublicRead="false" isPublicWrite="false" isCandidateKey="false" arrayLength="16"isTransient="false" exportAsString="false" noBackpointer="false"/>

</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 inthe Business Modeler IDE and choose Reload Data Model. The customdata model is reloaded and validated against the out-of-the-box templatedata model.

6. If there are any issues, they are displayed in the Console view inthe Business Modeler IDE. Fix the errors, and then repeat step 5.Repeat these steps until all errors are fixed. Contact GTAC if you needassistance.



• Teamcenter upgrade fails with custom types


If you have a custom type name with the same name as the parent class, thecustom type is identified and added to the custom templates, but the upgradefails. For example, you have a custom storage_media type that belongs to thestorage_media class.


Before upgrading to Teamcenter 2007, rename the custom type name to anythingother than the parent class. For example, rename the storage_media type tostorage_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 thedatabase 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_objectlast_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 theppom_application_object table. You can determine the table size with thefollowing 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.DBFINDX D:\ORACLE\ORADATA\INDX01.DBF

In this case, all data files are located in the D:\ORACLE\ORADATAdirectory.



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 (100Meach) 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 /nologconnect 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.LOG2 ONLINE E:\ORACLE\ORADATA\DPVPERF\REDO02.LOG1 ONLINE STALE E:\ORACLE\ORADATA\DPVPERF\REDO01.LOG

4. Create the new redo logs as follows. You can change the drive where you cancreate 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;ALTER DATABASE DROP LOGFILE GROUP 2;ALTER DATABASE DROP LOGFILE GROUP 3;

Note

If the group number is the current group and you cannot drop it, runthe command to force the log switch to make group 4, 5, or 6 current.



• Databases dating from before iMAN version 4 may have twoIMAN_Drawing relation types


Before iMAN 4.0, an IMAN_drawing relation was defined but never used. Atversion 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 anIMAN_drawing relation defined. If so, the Business Modeler IDE does not findit in the out-of-the-box set of definitions and includes it in the customer-templatedefinition.


If you have a pre-4.0 version database, before running the Teamcenter 2007upgrade:

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, whichyou 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 aremoved


By default, the Inch and Metric templates are associated in the Unigraphicsseed parts folder in the infodba user Home folder. If these templates are movedto a different folder, the nxmgr_add_note_types utility fails when it runs aspart of an upgrade and the database becomes inaccessible.


Move the templates back to the Unigraphics seed parts folder before startingthe upgrade.



• Missing database index

(First published Engineering 9.0)

After you upgrade a database, a problem resulting from a missing databaseindex can cause performance problems.


After upgrading a database, execute the following commands:

Windows systems:set TC_ROOT=tc-root-directoryset TC_DATA=tc-data-directorycall %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-directoryexport 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 MicrosoftWord, Teamcenter displays an error.


Use Notepad, Wordpad, or another text editor to open text files.

• Microsoft Office documents open externally instead of in the Viewerpane


If you have Microsoft Office 2007 installed and you select a MSWord, MSWordX,MSPowerpoint, MSPowerpointX, MSExcel, or MSExcelX dataset in MyTeamcenter and switch to the Viewer pane, the document is opened externallyin its application (for example, in PowerPoint) and not embedded in the Viewerpane.


By default, Microsoft Office 2007 prevents Office 2007 documents from beingembedded in another application. For example, if you try to view a Worddocument within Internet Explorer, it opens the document in Microsoft Wordand not within Internet Explorer.

– To enable embedded viewing in Microsoft Windows Vista, you must changeregistry 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 windowcheck 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 andclick the Save button on the Word toolbar within the Viewer pane, the changesare not saved to the dataset.


Click the Save button at the top of the Viewer pane. The Save button on theWord toolbar within the Viewer pane saves the document to the client machinebut 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 Viewbutton, it sometimes appears briefly and then disappears.


Either click the top line to make the parts visible again or load the productview 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, thevalidation report gives wrong Total Number, Target, and User results.


Use VO – Validation Results search criteria to query the validation results.

Managing product structures

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 ismade under new IC revision


If you change an attribute on a BOM line under a new revision of an IC thatalready has an IC-tracked change, the change is not displayed and the attributeis rolled back to its original value. Refreshing the BOM line also fails to displaythe new value.


Close Structure Manager and reopen the structure.



• Implemented By and Realized By relationships are not displayed whencopied in another structure


If you copy a product structure containing Implemented By or Realized Byrelationships and paste it in another product structure, the relationships are notdisplayed in the new structure.


Re-create the Implemented By and Realized By relationships in the newstructure.

• Separation of view and edit properties in Manufacturing ProcessPlanner and Structure Manager


In Manufacturing Process Planner and Structure Manager, there are notseparate dialog boxes for the view and edit properties functionality for BOM lineproperties as there are for properties in My Teamcenter.


Use the Properties dialog box to edit properties.

• Rebaselining an unchanged Structure Manager structure does notcreate a new baseline


If the ITEM_smart_baseline preference is set to ON and a user tries to createa baseline for an assembly that has not changed after a previous baseline, a newbaseline is not created. No informational message is displayed in the client toindicate 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 ifclients are inactive. If a server times out and is killed, Structure Managerclient-pending changes are lost.


Four-tier administrators should set the time-out in a way that a time-out doesnot occur for a server in edit mode. For Structure Manager, this corresponds toan active SAVE button in at least one BOM dialog box, which represents at leastone Structure Manager session with unsaved changes. The default is 8 hoursfor a server in EDIT mode. If sessions are up overnight, a 24-hour time-out (orlonger 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 withvalues outside the variability of architecture breakdown element


You can incorrectly modify named variant expressions (NVEs) with valuesoutside of the variability of architecture breakdown elements (ABEs) on whichthey are already applied. Modifying NVEs outside the variability of ABEs doesnot cause severe problems, such as a server crash or internal error.


Do not modify NVEs outside the variability of the ABEs. You can also removethe 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 searchresults


In Search Results in the Edit menu of the Property Selection dialog box, whenobtaining ImanFile references, the entry for the byte size is missing and thefile size appears twice. The second file size is actually for the property path ofbyte_size. If you select the one for Dataset.ref_list.byte_size, the resultingProperty Finder Formatter (PFF) column displayed still has Title of File Sizeand has file size data. Thus, the byte size column and data cannot be displayedin Search Results.


PFF cannot display byte sizes in the display tables. Use the properties table orviewer 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 packedBOM line. Microsoft Excel Import prevents you from updating the property onpacked reference designators.


Unpack the BOM line and set a unique value on each occurrence. To updatethe property on packed reference designators, unpack the rows in Excel beforeimporting.

• Duplicate reference designators created during import


Duplicate reference designator values are imported when the default valueis provided in the control file. If you enter default values for the referencedesignator columns, a warning is displayed about duplicate referencedesignators.


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 displaysSave dialog box out of sequence


The following steps cause the Save dialog box to appear after Schedule Managercloses 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.



Managing manufacturing data

This section contains release notes pertaining to Teamcenter’s manufacturingprocess 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 thehierarchy, it returns no results.


Click the Search button below the hierarchy to use the Search dialog boxinstead.

• Graphics builder preference name change


The graphics builder preference name has changed from UGGraphicsBuilderto NXGraphicsBuilder. Adjust the following preferences and define both assite 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 componentsearch (GCS).

• Import of Manufacturing Tooling Library and Resource Managersample data


When you import the Manufacturing Tooling Library or Resource Managersample data, it is imported using the item item type. You cannot import it usinga 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 untilall CPs are generated and the Edit button is active.

• Updating connection types and connection point definitions takesseveral 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 notimmediately appear on the assigned line in the process window.


Choose View→Refresh.

• Assigned occurrence for GDE link is not accurate after ManufacturingProcess Planner is reopened


If you use a GDE and then remove the GDE line, the assigned occurrence showsthe link is broken. If you close and reopen the Manufacturing Process Plannerapplication, 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 BOMline columns


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


Add the property to the BOM line columns to display it in the property list withthe localized label.



Publish

The following release note pertains to the use of Publish.

• Portfolio page list update does not reflect modular variantconfigurations


When a structure that is configured with modular variants is used to generate alist of pages in a portfolio, unconfigured pages can appear when the portfolio isupdated.


Use classic variants to configure structures, or cut the unwanted pages fromthe 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 olditem revisions share the same dataset. You cannot transfer that dataset usingData Exchange.


Currently, there is no work around for this problem. This problem will beresolved in a future maintenance release. Contact GTAC for further informationabout availability.

• Customization may alter behavior of monitoring interface


If the behavior of the monitoring interface changes, it may be because of yourcustomizations. If it does fail, compare your mapping to the Teamcenterout-of-the-box (OOTB) mapping.


Currently, there is no work around for this problem. This problem will beresolved in a future patch. Contact GTAC for further information aboutavailability.



• Remote import that transfers ownership in Global Services fails toupdate ownership in ODS


If you perform a remote import that transfers ownership using Global Services,it fails to update the ownership in ODS.


Currently, there is no work around for this problem. This problem will beresolved in a future patch. Contact GTAC for further information aboutavailability.

• 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 synchronizedwith the source site.


The sequences feature for item revisions must be turned off by setting thefollowing site preference:

TCCheckoutReserveOnly=

Item

ItemRevision

This ensures that sequences are not created when an item revision is createdor checked in. This must be set immediately after you install the Teamcenterserver before any sequences are created in the Teamcenter database. For moreinformation about this site preference, see the Preferences and EnvironmentVariables Reference.

• Object Directory Services (ODS) operations not supported betweenTeamcenter 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 includespublishing objects to the ODS, remote search operations, and remote importoperations based on remote search results.



• Teamcenter to Teamcenter and Briefcase transfers through DataExchange support NX and JT CAD data only


Standard Teamcenter Data Exchange supports exporting and importing CADdata 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 KnowledgeManagement 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 KnowledgeManagement, subsequent transfers of the replica from Teamcenter causethe release status in Teamcenter to overwrite the LCS state in EnterpriseKnowledge Management.


Customized the system to create a local LCS attribute and use that for the localrelease.

• Data Exchange does not support the continue on error feature


If an error occurs during a Data Exchange transfer process, the entiretransaction is rolled back. Partial rollbacks are not supported. You can selectthe Continue On Error option in some Data Exchange interfaces; however, theoption 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 9and Teamcenter Engineering 2005/2007 connectors in the same EAR file


Global Services does not support including these two connectors in the same Webapplication (EAR file).


Using the Web Application Manager, build a Web application (EAR file) with allof the required Global Services solutions but without one of the TeamcenterEngineering connectors. Build a second EAR file that contains the TeamcenterEngineering connector not included in the first EAR file. Ensure that you providedifferent Deployable File Name values. The two EAR files can be deployed in thesame application server without causing errors. For more information about Webtier installation, see the Installation on Windows Servers Guide or Installationon 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 inthe Insert form


Several of the nonmandatory boxes (for example, Part Name) of the Teamcenterassembly BOD are autopopulated by Teamcenter.


Currently, Global Services does not have a capability to suppress suchautopopulated fields from the Insert form. Therefore, do not enter information inthese 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 becausethe 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 tothe 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.xml2006/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 configuratonhierarchy object: org.apache.log4j.Hierarchy@1e0cf702006/11/13-16:45:59,887UTC 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 LOCATIONConverted XML written to d:\stagingDir\lib\am.xml</clinit></clinit></clinit>


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



Multi-Site Collaboration

The following release notes pertain to Multi-Site Collaboration.

• Default Oracle parameter must be changed for optimal Multi-SiteCollaboration functionality


The Multi-Site Collaboration ensure_site_consistency utility may fail torecover failed transfer operations due to locked objects associated with deadprocesses.


The Oracle SQLNET.EXPIRE_TIME parameter must be set to a validvalue. The recommended value is 10. It must not be 0 or unset. TheSQLNET.EXPIRE_TIME parameter is used to set a time interval, in minutes,to determine how often a probe should be sent verifying that client/serverconnections are active.

• Sharing data with pre-Teamcenter 2007.1 MP3 databases causes variantexpression 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 anearlier version of Teamcenter or Teamcenter Engineering, you may receiveerrors if you use an item revision variant expression block or an occurrencevariant condition.


Run the following utilities on the pre-Teamcenter 2007.1 MP3 database:

install -mod_attr infodba infodba dba ItemRevision variant_expression_blockPOM_attr_follow_on_export +

install —mod_attr infodba infodba dba ItemRevision variant_expression_blockPOM_null_is_valid +

install —mod_attr infodba infodba dba PSOccurrence variant_conditionPOM_attr_follow_on_export +

install —set_attr infodba infodba dba PSOccurrence variant_conditionNULLTAG

install —mod_attr infodba infodba dba PSOccurrence variant_conditionPOM_null_is_valid —

• Multi-Site Collaboration in HTTP mode requires a single SSO domain


When a Teamcenter Multi-Site Collaboration site is configured for HTTPtransport mode (Is HTTP Enabled check box), all of the participating Multi-SiteCollaboration sites must be configured in the same Security Services IdentityService.


Configure all Teamcenter sites in the Multi-Site Collaboration network in theapplication registry of a single Security Services instance. For information aboutconfiguring Security Services, see Security Services Installation/Customization.



• Remote checkin behavior


If you attach a local object to a replica using remote checkout, upon remotecheckin the attached local object can be transferred with ownership, can be sentas replica, or can be opted not to be sent at all. You can configure this behaviorfrom the user interface and preference. From the Remote Checkin dialog boxadvanced 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_replicapreference is sent as replica.


When you select a particular relation from the user interface, the following tableexplains the behavior to local attached behavior.

Relation includedin user interface

Relation specifiedin 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 engineeringchange object back to the master site. In the case where the only incrementalchanges made are attachment deletes, the engineering change object is notautomatically transferred to the master site and the delete actions are not bevisible in Structure Manager.


Manually transfer the ownership of the engineering change object back to themaster site.



• dsa_util utility does not change externally managed user constructs toremote


The dsa_util utility does not recognize externally managed users, groups, roles,persons, and group members with a datasource attribute value greater than0 and convert them to remotely managed (for example, managed by an LDAPexternal directory at a remote site). Because the dsa_util utility is the only wayuser constructs can be converted to remotely managed, no user construct objectsin the Organization user interface appear as remotely managed.



• Multisite licenses

(First published Engineering 2005)

Prior to Teamcenter Engineering 2005, the Multi-Site Collaboration Serverlicense was checked only when the Object Directory Services (ODS) serverprocess starts up. Starting with Teamcenter Engineering 2005, all multisiteoperations, such as remote import, publication and remote search, checks theMulti-Site Collaboration server license to make sure that this license waspurchased. If the Multi-Site Collaboration server license is not available, usersget an error message when performing multisite operations. Make certain theMulti-Site Collaboration server license, as well as the multisite user licenses, areavailable 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 orTools→Export→Objects and clicking the PLM XML button, the Vendor Roleinformation associated with a vendor revision is not processed.


Run either the tcplmxml_import or the tcplmxml_export utility from thecommand line to transfer vendor management objects from one Multi-SiteCollaboration 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 Overlayupgrade


If your Engineering Process Management installation includes TeamcenterAutomotive Edition with the GM Overlay and AutoCAD Integration features,you must fix application names on certain AIE classes before you upgrade toTeamcenter. If you do not do this, the Business Modeler IDE console reportserrors while importing the customer template. These errors are similar to thefollowing example:

Model Error: business_objects.xml Line:2622 Column:60 Change TcClassis not supported.

The line number cited in the error message corresponds to an AIE class datamodel element in the customer template.


The Teamcenter site administrator must fix AIE class application names byperforming the following steps on the database server before you upgrade toTeamcenter 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 Managementdatabase.

3. Perform the following steps for each of the following classes:

AIEBATCHOPERATIONAIECOMPONENTINFOAIEDATASETINFOAIEEXPORTASSEMBLYAIEEXPORTNODEAIEEXPORTOPERATIONAIEIMPORTOPERATION



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. Makesure 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 inthe 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 commandat the acg prompt:

commit;

4. After you complete these steps for all classes in the list, enter the followingcommand:

exit

• Naming rule error occurs after upgrading a Teamcenter Engineering9.1.3 database containing GM Overlay


If you upgrade the Teamcenter Engineering 9.1.3 GM Overlay database and asite item ID prefix is different than one in the GM Overlay template (GMO), anerror occurs when the custom-generated template is loaded in the BusinessModeler IDE.


1. Before upgrading, log on to the database and note your item ID prefix andID 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 IDprefix 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 andthe 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 preferencepoints to parent node


If you set the LDAP_member_list_attr preference to point to a node on the treethat contains a direct parent of the node being processed, it causes an infiniteloop that crashes the ldapsync utility. For example, if a parent node has onechild node and that child node uses the LDAP_member_list_attr preference topoint back to the parent, it causes an infinite loop.


Ensure the LDAP_member_list_attr preference does not point to a node thatcauses an infinite loop.

• Protecting data synchronized from an external LDAP directory


When a user construct object (user, group, role, person, or group membership) issynchronized from LDAP to Teamcenter (externally managed), the synchronizedattributes of that object should be updated only in the LDAP externaldirectory, not in Teamcenter. Therefore, the Organization application makesall synchronized attributes read-only for externally managed user constructs.For internally managed user construct objects (created in Teamcenter), theseattributes remain updateable. The Organization application symbols aredifferent for internally managed user constructs than for externally manageduser constructs to help clarify this behavior difference. However, otheradministrative tools for updating user, person, group, role, and group memberinformation, such as themake_user command line utility and custom utilitiesthat call the ITK APIs, do not have any controls prohibiting externally manageduser constructs from being updated. User constructs synchronized from LDAPare updated each time the ldapsync utility is run and attribute changes madeby other utilities are overwritten by the ldapsync utility if those attributes aremapped for synchronization.


Teamcenter administrators are responsible for ensuring synchronized data forexternally managed user construct objects does not get overwritten by otherutilities. If it does get overwritten, the changes are lost the next time theldapsync utility is run to update the synchronized data.



• Reversing accidental externalization of internally managed userconstructs


When a user construct object (user, group, role, person, or group membership)exists in both LDAP and in Teamcenter, the default ldapsync utilitysynchronization behavior is to set the datasource attribute on that userconstruct in Teamcenter to externally manage and synchronize that object withTeamcenter. This is particularly useful for updating user and person Teamcenterobjects that were synchronized from LDAP in previous Teamcenter versions toset the new datasource attribute correctly. However, some customers may notwant internally managed user construct objects to be converted to externallymanaged. Because externalization of these objects is the default behavior, youmust 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 theexternalize sync flag in the preferences file. See the Preferences and EnvironmentVariables Reference for more details on the externalize synchronization flagin 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 fromexternally managed to internally managed. However, the make_user utilityis updated with a special option to set the datasource attribute on specifieduser construct objects. Use this feature to reset user construct objects thatwere mistakenly externalized during a synchronization process. This option isintentionally left undocumented in themake_user utility because it should notbe used for any reason except to correct a synchronization error.

The make_user command line option, –datasource=value, sets the specifieddata source value (0=Internal, 1=External, 2 =Remote) on the specified user,person, group, role, and group membership objects. By setting the datasourceattribute to 0 on a user, person, group, role, or group membership object, theobject is returned to internally managed.

Themake_user utility also allows attributes to be specified in an input file forbatch processing, and datasource is supported as an attribute for updatinguser, person, group, role, and group membership objects. For more informationabout the make_user input file for batch processing, see the make_userdocumentation 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 CPUusage 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 heapmemory settings (–Xms and –Xmx) are often too small. Increase the Javamemory 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 tablein 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 FileServices and FMS.

Note

For release note information about using FMS with IBM AIX, see FCC isnot 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 errormay be displayed that says the file is corrupt or not a valid archive.


Either use a different browser, such as Mozilla, or disable file transfercompression for ZIP files.

To disable file transfer compression for ZIP files, add theFSC_DoNotCompressExtensions property to the fscdefaultselement 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 jtand zip are contained within the value.

Once you change the files, either reload the configuration files or stop and startthe 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 PLMSoftware; 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 validatewhether 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 againstthe type specified on the function call. The caller must ensure that the file fortransfer is of the specified type.



• FMS configuration


The following error message appears when the values specified for theTransient_Volume_RootDir preference have identical values:

Duplicate transientvolume configuration elements were found for attribute idwith value attribute_value


The Transient_Volume_RootDir preference allows the configuration oftransient volume locations for multiple platforms. Typically, one valuerepresents the location of a transient volume on a UNIX system and the other atransient volume on a Windows system. The distinction is made based on thepath name separator (/ for UNIX, \ for Windows).

If you use only one platform, you can delete the other value. Multiple valuescan 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 FSCprocess is not able to resolve the host name for the local IBM AIX host resultingin 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 usingthe 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 toIP 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 connectiondeclarations.

◊ 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 FMSmaster 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 IPaddresses.

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 theaddress field of all parentfsc declarations.

3. If IBM AIX-hosted FSCs support HTTPS connections:

a. Issue each HTTPS-supporting IBM AIX-hosted FSC a certificatecontaining 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-dotnotation form.

c. Install this new certificate in the trusted certificate store of eachpeer FSC and client, unless they are configured to accept self-signedcertificates.

4. After making these changes, follow the normal procedures for propagatingnew FMS configuration changes to your site.



To maintain these changes as IBM AIX-hosted FSCs are added to the site, youmust do the following:

1. Configure the IBM AIX-hosted FSCs in FMS by IP address rather thandomain 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 tothe parent FSC in the FCC configuration by IP address rather than domainname.

4. Follow the normal procedures for propagating new fmsmaster.xml changesto 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 toopen it from Teamcenter. This occurs when the NX installation procedure writesincorrect content into the /ugs/installed_programs.dat file.


Replace the following two lines at the start of your /ugs/installed_programs.datfile:

[HKEY_LOCAL_MACHINE\Software\Unigraphics \cSolutions\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 PDMmenu command, a connection under a harness could move out from underthe harness on subsequent exports to Teamcenter. This typically happens inconnection 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 System9.1 application server with Internet Explorer, the Export Status window is notupdated with the Download hyperlink when the operation is complete. Also, ifthe 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 downloadattempt


In the thin client, if you click the hyperlink to download an NX assembly inthe Export Status window and then click the Cancel button, the Downloadhyperlink is no longer available.


Always click the Save button after clicking the Download hyperlink.

• Download hyperlink is not available for the first subassembly if asecond subassembly is exported too soon


If you export a second NX subassembly before the first subassembly export hascompleted in the same Structure Manager window, the Export Status window isnot updated with the Download hyperlink for the first subassembly.


Either wait for the first subassembly export to finish before attempting to exportthe 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 deletethe wire from the new revision.


Release the electrical harness when you release the item containing the electricalharness.



• Harness structure corrupted after adding a harness and connection


A new harness structure is corrupted after you add a harness and connectionusing the NX Export to PDM menu command.

The harness structure from the previous revision is corrupted after you deletethe wire from the new revision.


Use variants and options instead of multiple, duplicate harnesses within onepart 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 runningbatch scripts. Therefore, if you run the ugs_update.bat file to upgrade NX5.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.batfile.

• NX does not launch from four-tier Teamcenter client on 64-bit WindowsXP


When you attempt to launch an assembly into NX from a four-tier Teamcenterclient 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 theTeamcenter installation source in the additional_applications folder, or alsocan 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 runapplications developed with Visual C++ on a computerthat does not have Visual C++ 2005 installed.

The runner.exe application in Teamcenter is this kind of executable. You needto have administrator credentials to install the vcredist_x86.exe file.


http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en


• Opening a UGMASTER dataset type in NX 4.0.4.2 fails if usingNX_Interop_Type set to plmxml with NX 4.x


The UGMASTER dataset type does not open in an NX session if the TeamcenterNX_Interop_Type option is set to plmxml. The NX 4 session opens, but thepart 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. Whenusing NX 4, do not change this value.

• Bookmark error occurs when creating a dataset in Teamcenter andusing Teamcenter Integration for NX 5


When creating a dataset in Teamcenter and using Teamcenter Integration forNX 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 attemptsto open the UGMASTER dataset. This error may prevent the new part frombeing saved to the database.


Install the NX 5 templates. Siemens PLM Software recommends that allcustomers who intend to use NX 5 install the templates, regardless of thisparticular error.

• Item IDs can be created that are invalid in Teamcenter Integrationfor 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 NXInformation 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 volumevalue from the user’s assigned group. At times, the value from this implicitassignment does not get passed to the Teamcenter Integration for NX importoperation. This message indicates the Teamcenter value did not pass properly tothe Teamcenter Integration for NX import function.


Manually set the default volume using the Default Volume button in the Groupspane in the Organization application. This explicitly assigns the volume nameto the user. The value from the explicit assignment is provided to the clonefunction and imports function correctly.

Security Services

The following release notes pertain to Security Services.

Note

For additional Security Services release notes, see the Security ServicesRelease Notes (SecurityServicesReleaseNotes.pdf file) in the ssosubdirectory of the additional_applications directory of the Teamcenter2007 software distribution image. This document describes featuresintroduced with the latest version of Security Services. It also containsgeneral notes and descriptions of known defects.

• Customization of the default search string used in the WebSEAL logonpage FORM causes authentication to fail


After Teamcenter rich client, FMS client cache (FCC), or Teamcenter’s lifecyclevisualization client startup, any action that requires authorization initiates arequest to the IBM Tivoli WebSEAL server. WebSEAL sends an authenticationchallenge response to the Teamcenter application, which attempts to detectthe WebSEAL form authentication event prior to initiating Security Services.This detection process performs a search within the WebSEAL HTML responseto find a specific string. The default search string used in the WebSEAL logonpage 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, theauthentication process between Security Services and WebSEAL fails.




– FMS client cache (FCC)

Provides a configuration property within the fcc.properties.template filethat can be used to redefine the search string.

Change the fcc.properties.template file name to fcc.properties, and thenedit 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 searchstring.

Set the following system or user environment variable prior to starting theLifecycle 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 thefollowing property in the site_specific.properties file prior to startingthe 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 includedin the installation with WebSEAL, the file attachments with thedataset may fail during open or edit operations. To avoid this error,ensure the useMSOfficeIntegration property is set to false in theclient_specific.properties file.

• Extra logon challenge in some WebLogic deployments


If you deploy the Login Service and Teamcenter Web client on the same WebLogicserver instance but on different ports (same host), you get an extra challengewhen you log on.


Deploy the two Web components on the same port or on different WebLogicinstances.



Utilities

The following release notes pertain to utilities.

• data_sync utility with –restart option fails on HTTP Multi-Site betweenWindows and Solaris


If you have an HTTP-based Multi-Site environment and run the data_syncutility with the –restart option on a Windows platform, it fails to invoke theother site tcserver if it is on a Solaris platform.


Delete the existing checkpoint transaction and run the data_sync utilitywithout 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 anyintermediate 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 defaultdelimiter 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 objectsmanaged by the Business Modeler IDE


The smlutility –install utility with the following suboptions corrupts datamodel 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 theClassification-specific parts of the Teamcenter data model. This is controlled bythe Business Modeler IDE. If you use the smlutility –install utility, you maycorrupt the data model and the data may become inaccurate.


The only option still allowed is ICS_UTIL. However, do not use this optionbecause 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) areincluded. The header files previously located in the include directory are movedinto subdirectories. Therefore, you must add the subdirectory to your includecalls 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, theheader files have been duplicated in the main include directory. They onlycontain an include statement of their counterparts in the subdirectories. Theduplicated header files in the main include directory are deprecated and will beremoved from a future version.

Siemens PLM Software provides a Perl script to help you convert your includestatements. The prerequisite for this tool is Perl 5.8.0 or later, and you must runit on a Windows machine. You can use this tool either before or after using theTeamcenter Namespace Deployment tool.

1. Access the GTAC server and download theTeamcenter_2007_HeaderInclusionFormat tool into a dedicateddirectory.

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

The tool decides which files to process and parses them. Once parsed, thefiles to be modified are checked out using the command specified in step 5.The updated files replace the existing files. The tool generates statistics tohelp you track how the tool performed.



7. To validate everything is modified according to the new standard, copy theinclude 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 theworkspace. If there are any include-related compilation errors, check thefiles for incomplete conversions.

• Call EINT_init_module function before other eIntegrator Admin ITKfunctions


If you are using eIntegrator Admin in a batch program, you must call theEINT_init_module function first before you call other eIntegrator Admin ITKfunctions.

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 thanthe version you already have.


The libcurl library in Teamcenter is named libtccurl. Use the libtccurl librarywhen 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 Officedocument in the rich client


If you install the rich client on a virtual drive and try to visualize MicrosoftOffice 2007 documents in the embedded viewer, you see a red background insteadof 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 thePowerPoint application by double-clicking the dataset while it is still open inthe Viewer pane, changes made and saved in the application are not saved tothe 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 mostUNIX X servers


On most UNIX/Linux systems, modal dialogs may be hidden behind the mainapplication window. Because the dialogs are modal, no keyboard or mouseinteraction is permitted with any other part of the user interface except forthe modal dialog box.


Manually find and bring the modal dialog box to the top. When finished withmodal 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 Statusdialog box closes


If you close the thin client Export Status dialog box, the NX export request keepsprocessing instead of deleting the request.


Do not delete a request in the thin client. Use the translator administrationconsole in the rich client.

• PLM XML import/export does not handle import/export of filesassociated with a dataset


Thin client PLM XML import/export of datasets does not handle transfer ofassociated files attached to a dataset, such as UG NX assemblies and part files.

When a dataset is imported/exported through the thin client PLM XMLimport/export, its associated files cannot be imported/exported along with thePLM XML file containing the dataset definitions.


Use Teamcenter rich client PLM XML import/export to import/export datasetsand their associated files.

• Name and description values not set through initial value on a propertyrule


Prepopulation of the Name and Description boxes from the initial valuedefinition 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 ina 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 maygenerate 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 touse a Teamcenter EDA integration command, you may get a failure during theTeamcenter logon.


Currently, Mentor Board Station 2005 is not supported on Solaris 10. The launcherror is known to Mentor Graphics, but there is no known solution for it. MentorBoard Station 2006 and above is supported on Solaris 10. Teamcenter EDA nowsupports both Mentor Board Station 2005 (BS2005) and Mentor Board Station2006 (2006BSXE); however, only Mentor Board Station 2006 is supported forSolaris 10.

The version of Mentor Board Station is determined at run time and the EDAintegration 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 Graphicsand Cadence, with Teamcenter. When using the Teamcenter EDA client withMentor Graphics on a UNIX platform, Teamcenter EDA actions fail. The launchof the Design Manager may also fail.

During the installation of the Mentor Graphics support option within TeamcenterEDA, files are installed that provide extensions to the Mentor Graphics DesignManager product. Because of delivery limitations, these files do not contain thecorrect operating system file permissions. This condition only occurs on UNIXplatforms (Sun Solaris and Hewlett-Packard HP-UX).

Because some of the files contain incorrect permissions, the user encounterserrors that report that Teamcenter EDA tasks cannot be called because of theseincorrect permissions.




You must manually edit the installation to allow these Mentor Graphicsextensions to be used. Perform the following procedures for each UNIX clientthat 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/binchmod 755 mti_bom mti_dmgr mti_xbom

cd $TCEDAECAD_ROOT/Mentor_BoardStation/libchmod 755 libMTI*

– Hewlett-Packard HP-UX systems:

cd $MGC_HOME/binchmod 755 mti_bom mti_dmgr mti_xbom mti_ipc_server mti_run_ipc_server


– UNIX systems:

cd $MGC_HOME/binchmod 755 mti_bom mti_dmgr mti_xbom*


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 theSummary and Custom properties to Teamcenter OfficeDocForm


If you click the Save button in Microsoft Office 2007, the Office properties, suchas Author and Title, are not synchronized with the Teamcenter OfficeDocFormattached to the dataset as a named reference. The properties are synchronized ifyou use Office 2003 or an earlier version.


In Office 2007, click the Save to Teamcenter button in the Custom Toolbarssection 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 Officeand 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 attachrelation to the original item revision.


If a revision contains datasets with the attach relation, use the rich client orthin client to revise the item.

Internationalization release notes

The following release note pertains to internationalization:

• Thin client (DHTML) displays non-Western European text incorrectlywith Apache 2 HTTP Server

(First published Engineering 8.1.1)

Apache 2 defaults to Western European encoding. As a result, Web DHTMLdisplays non-Western European text incorrectly when Apache 2.x is used asthe HTTP server.


This problem does not occur with Apache 1.3.20. As a work around, SiemensPLM Software recommends that you comment out the encoding string in thehttpd.conf file (iso-8859-1).



Platform-specific release notes

This section contains release notes pertaining only to the following platforms:

UNIX platformsHewlett-Packard HP-UXSun SolarisIBM AIXMicrosoft WindowsSUSE 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_checkfunction has failed due to a time-out. For example, the data_share utility mayreturn the following:

***ERROR: No site available for processingERROR STACK:

100202: The IDSM request to site M0417Ha on host hpis04 failed.: RPC: 1832-008 Timed out

100107: Attempted function idsm_version_checkat 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 11igenerates errors release note to resolve the text server shared memory IDSMerror messages.

– In the $TC_BIN/run_tc_idsm script, set theTC_NO_TEXTSRV_SHARED_MEMORY environment variable to TRUE.This disables the shared memory functionality and reverts the systembehavior 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, youmay not be able to change the text in normally editable boxes. This also mayoccur in the Summary pane after opening the Properties dialog box.How to work around or avoid

– 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-1character 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 typingLC_ALL=en_US.ISO8859-1 or the equivalent command for your platform.

2. Verify the setting using the echo command or equivalent. Make sure thecorrect value for LC_ALL is displayed.

3. Run the locale command and make sure the LANG variable and all theLC_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 asLC_ALL.

5. Launch Teamcenter Environment Manager (tem.sh) from the current shell.

Alternatively, your system administrator may modify the date file (namedTIMEZONE in the etc directory), which can preset this environment, so everytime you log on and launch a shell, the environment is preset.

The recommended method, however, is to log on to the system using the CommonDesktop Environment (CDE) with the minimum required locale (ISO8859-1) bychoosing Option→Language→en_US.ISO8859-1 during logon.

If the ISO8859-1 character set is not loaded on your machine, contact yoursystem administrator to have it installed before you install the GM Overlay.

This requirement is due to changes in the installation process for Teamcenter2007, which uses XML files rather than .dat files and associated scripts. Becauseof this, GM Overlay data is transformed from .dat files into XML files.

To read and parse the XML files correctly, the system must be able to processnon-English (non-ASCII) locale characters. To facilitate this, the system must befirst loaded with the fonts for that locale.

Note

Ensure the ISO8859-1 character set is loaded before you add anyTeamcenter features to your configuration that contains the GM Overlay.If the ISO8859-1 character set is not loaded, lists of values (LOVs) for GMOverlay 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 onHP-UX 11.11, you may get the following error when UNIX system sharedmemory segments and semaphores interprocess communication resources arelow:

open: Not enough space(17739|1) init_acquire failed: Not enough spaceACE_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 controlinterprocess communication between the Teamcenter server processes.

Type the ipcs –sb command in a shell to display a list of shared memorysegments and semaphores currently allocated to the system. This list includesall the shared memory segments and semaphore sets allocated, their identifyingnumber, the owner, and the number of semaphores in each set.

Occasionally, unexpected termination of Teamcenter processes leaves sharedmemory segments and semaphore resources locked. If Teamcenter is notrunning, but the ipcs –sb command lists shared memory segments andsemaphores owned by the owner that started the pool manager, these resourcesmust be freed. If this is not done, shared memory segments and semaphoreresources may not be sufficient on the UNIX system to allow the text serverto use interprocess communication.



Freeing shared memory segments and semaphores

Freeing shared memory segments and semaphores is done by either using theipcrm command or by restarting the system. Normally, system administratorsdo not want to restart the system only to free shared memory segments andsemaphore resources. Shared memory segments and semaphores can be freed byperforming the following procedure:

Warning

Do not attempt to free shared memory segments and semaphore resourcesfrom 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 segmentsowned 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 fromthe list.

4. Type the following command to display a list of semaphores owned byTeamcenter:

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 mustrefresh 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_DIRenvironment variable value specifies the directory where the store backingfiles are stored. If you do not set this variable, its value is set by thetc_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 TEMPdirectory is used.



The shared memory files are created under theV2007.1.0.last-build-date/database-site-ID/language directory located inthe temporary repository. The language directory is extracted from theTC_LOCALIZATION_DIR environment variable. Server error messagesare saved in the emh_text.xml.mem file. Server strings are saved inthe tc_text.xml.mem file.

At the next process startup, the system finds the shared memory state is nolonger initialized, reads the XML text files, and populates the shared memorycache, thus creating and populating the shared memory backing store file.

Note

You can disable shared memory functionality and revertsystem behavior to in-process text storage by setting theTC_NO_TEXTSRV_SHARED_MEMORY environment variable toTRUE.

Text server errors involving UNIX shared memory segments and semaphoresoften indicate insufficient interprocess communication resources on that UNIXsystem. Shared memory segments and semaphores resources may need to befreed before the text server can use interprocess communication.

In this case, the text server automatically reverts to using tcserver memory toprovide text services. At a time when interprocess communication resources areavailable, the text server automatically uses interprocess communication againfor new tcserver processes.

• Cannot change values in Properties dialog box on AIX or HP-UXtwo-tier client


If your two-tier client is on the AIX 5.3 or HP-UX 11.11 platform and you checkout a dataset using the Tools→Check-In/Out→Check-Out menu command, andthen view its properties, you cannot change anything in the dialog box, eventhough the dialog box is not labeled as read-only.

Also, if you select the dataset, view its properties with the View→Propertiesmenu command, and then click the Check-Out and Edit button, you can changethe Name and Description boxes, but if you close and reopen the dialog box, youcannot make changes.


If you are using the AIX platform, make your changes on the Summary pane. Ifyou 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 formultiple interface cards


If multiple interface cards be connected to a common subnet and configured toboot with nonunique MAC addresses, any multicast activity can severely disruptnetwork communications to and from that machine.

Teamcenter 2007 has a JETI pool manager that can be configured to usea multicast protocol for high performance management of its shared poolconfiguration state.

Sun Solaris machines must have the EEPROM local-mac-address? set to true.

In particular, Sun Solaris machines with multiple interface cards installed mustbe configured to boot with unique MAC addresses. To identify these, perform oneof 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 MACaddress, and shows that the system is booted with local-mac-address?set to false:

# prtconf -pv | grep local-mac-addresslocal-mac-address?: ’false’

local-mac-address: 0003bb7d.7c51local-mac-address: 0003bb7d.7c51

– As a root user, run ifconfig –a. As this user, the MAC address is shownfollowing the ether tag. (If run as a nonroot user, the inet addressinformation is still shown, which is useful information.)

The following is an example of cards that boot with nonunique MACaddresses and are configured on the same subnet:

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1inet 127.0.0.1 netmask ff000000

ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2inet 123.123.12.101 netmask ffffff00 broadcast 123.123.12.255ether 0:3:bb:7d:7c:51





For the cards to boot with unique MAC addresses, the EEPROMlocal-mac-address? must be set to true and the machine rebooted.

For example, as root user:

init 0ok setenv local-mac-address? Trueok 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-addresslocal-mac-address?: ’true’

local-mac-address: 0003bb7d.7c51local-mac-address: 0003bb7d.7c52

– (Alternative) As a root user, run ifconfig –a:

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1inet 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-UXtwo-tier client


If your two-tier client is on the AIX 5.3 or HP-UX 11.11 platform and you checkout a dataset using the Tools→Check-In/Out→Check-Out menu command, thenview its properties, you cannot change anything in the dialog box, even thoughthe dialog box is not labeled as read-only.

Also, if you select the dataset, view its properties with the View→Propertiesmenu command, then click the Check-Out and Edit button, you can change theName and Description boxes, but if you close and reopen the dialog box, youcannot make changes.


If you are using the AIX platform, make your changes on the Summary pane. Ifyou 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 Editordialog box in Structure Manager or when a component is selected in the Viewertab, 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→EditColor/Translucency menu command. The Material, Preview, and Colorssections should appear. Once they appear, they always appear when youopen the dialog box.

– Select a part in the Viewer tab, and then open the Appearance Editor dialogbox with the 3D Appearance toolbar. The Material, Preview, and Colorsections 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 twoor three times. Once the sections display, they always appear when youopen the dialog box.

– Exit Teamcenter and then remove the Visualization UNIX registry in youruser 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 theAppearance 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 clienton Windows systems.




This may happen when a non-native language operating system version ofWindows is used and the Multilingual User Interface (MUI) pack is not installedor if this is not enabled from the Languages tab in Regional and LanguageOptions in the Windows Control Panel. If you are using a non-native languageoperating system, you must do the following to make sure the language fontis displayed properly:

1. Install the MUI pack for Windows. Once installed, you should see theLanguages used in menus and dialogs list in the Languages tab ofRegional 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 RegionalOptions 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 accesslog and other files contained in the TC_TMP_DIR directory on the server host.To ensure that temporary files from different users remain separate, Windowscan assign each user their own TEMP directory. This can be seen when uniquetemporary directories are created, such as C:\Temp\1 and C:\Temp\2, insteadof the shared C:\Temp. Each of the temporary directories is accessible only bythe owner of the directory and administrators. In this case, TC_TMP_DIR isaccessible only to the operating system user running the Teamcenter server andthe computer administrator.


You can stop the creation of the subdirectories by changing the Use temporaryfolders per session setting to No in the Windows 2003 Terminal ServicesConfiguration. This sets the C:\Temp directory as the temporary directorywith read permissions for everyone.

• Critical messages displayed in WebLogic 9.1 console when runningWebDAV


Critical messages are displayed in the WebLogic 9.1 console when runningWebDAV.


To remove these messages, follow the instructions provided by BEA: Steps forSmart Update:

http://e-docs.bea.com/common/docs91/smart_update/quickrefax.html

After applying the patch, add the–Dweblogic.servlet.security.EnforceValidBasicAuthCredentials=falseparameter to the end of the call command in the startWebLogic.cmd file foryour 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 eachedit 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 settingwhen 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 LOVvalue/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 andvalidation of the appearance_updater process fails because of a knownlimitation in starting and returning status from another process.


This happens only at the initial validation stage of the appearance updatemanager startup. To work around this, set the following configuration parameterin the .appr_update_env file:

updater.validation = 0



Release notes for Teamcenter-related products

This chapter contains general notes and describes known problems forTeamcenter-related products.

Teamcenter’s lifecycle visualization (Lifecycle Visualization) release notes

The following release notes pertain to the use of Teamcenter’s lifecycle visualizationthrough Teamcenter.

• Cannot view NX assembly, UGALTREP, or UGPART files using LifecycleVisualization


If you add the UGMASTER while creating a UGALTREP or UGPART, theUGALTREP or UGPART is handled as an assembly .prt file. Assembly .prtfiles cannot be directly visualized using Lifecycle Visualization.


Tessellate the .prt files into JT assemblies. JT assemblies can be viewed withoutproblems.

Administration and usage release notes

The following is a list of release notes pertaining to the administration and use ofLifecycle Visualization.

• .vvi file not found on Windows Vista machines if Lifecycle Visualizationis set to run as administrator


If you double-click a .vvi file in Windows Explorer on a Vista machine or sendit from Structure Manager within Teamcenter, you may see the following errormessage:

Windows cannot find "filename.vvi". Make sure you typed thename correctly, and then try again.


Ensure the Lifecycle Visualization executable VisView.exe is not set to runas an administrator by right-clicking either the VisView.exe file in WindowsExplorer or the Lifecycle Visualization shortcut and choosing Properties. InPrivilege Level, ensure the Run as Administrator check box is cleared.

• .vvx file type not recognized as a file associated with LifecycleVisualization


Certain file types, including .vvx files, do not appear to be associated withLifecycle Visualization after running the application.


Run Lifecycle Visualization as an administrator at least once to register theentire 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 extensionsbecause of file format changes. This file extension includes HP CoCreate ME10/ME 30 files.

• iSeries interoperation not supported


If you purchased a Named User Visualization license, you have access to iSeriesfor the thin client, but not the rich client. The license does not include supportof interoperability between iSeries and NX using PLM XML interoperabilityfunctionality.

• Some product views created in Teamcenter 2005 SR1 do not retrieveafter upgrade to Teamcenter 2007


Product views created in Teamcenter 2005 SR1 that were captured after turningon the entire assembly at the root node do not appear when they are launchedafter upgrading to Teamcenter 2007. Product views captured after the visibilitystate 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 LifecycleVisualization, 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 temporarygraphics artifacts on Windows Vista


If you click and drag markup entities in Lifecycle Visualization, a gray shadowfollows the trail of the mouse and disappears when you release the left mousebutton.


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 notpersist and can be displayed only one at a time. However, you can save thesemeasurements 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 oropen the Preferences dialog box on the 2D measurements toolbar and ensurethat 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 ofthis instability, this feature is not automatically enabled.

Note

The View NX .prt file as 2D preference is valid only when this featureis enabled.


To enable this feature, follow the instructions in the Customize therich client properties files topic of the Rich Client CustomizationProgrammer’s Guide to make the following changes to thecom/teamcenter/rac/common/tcviewer/tcviewer.propertiesfile:

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 followingthree 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. Forthis reason, Siemens PLM Software strongly recommends that you use theugtopv utility to translate UGMASTER datasets into JT parts.

Users generally view assemblies in Structure Manager (Structure Manager). Ifyou must use My Teamcenter to view assemblies, execute the ugtopv commandwith the generate_assembly_jt option. Otherwise, you can view componentparts only.

Note

Do not use the MIMIC option during translation.

Platform-specific

This section contains Lifecycle Visualization release notes pertaining to specificplatforms.



• Embedded Visualization installation and uninstallation fail on WindowsVista with an IO exception


The Embedded Visualization installation and uninstallation fail with an IOexception if the Teamcenter Environment Manager (TEM) installer (tem.bat) isnot launched with the Run As Administrator menu command from the shortcutmenu 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 MicrosoftWindows 2000/XP Professional


When using the rich client, users may see random gray patches where the userinterface is not repainted. This results from known problems in the followinggraphics cards used with Microsoft Windows 2000 and XP Professional platforms:

NVidia Quadro 2 Pro GraphicsNVidia Quadro 4 500 GoGLELSA 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 Xbootclasspathdefinition 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 queriesfor a Teamcenter 2007 connection


The != and IS NULL operators do not work when running saved queries for aTeamcenter 2007 connection. They do not work in ad-hoc flow from BuildNPlaybecause saved queries work only for the = operator.




The administrator should select only the = operator when saving the reportdefinition build on saved queries.

• All operators appear in the interface for both saved and databasequeries


All operators appear in the interface for both saved queries and databasequeries, even though only the = operator works for saved queries.


The administrator should select only the = operator when saving the reportdefinition 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 connectionin mapper


No field name appears in error message when creating a connection in themapper.


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’smechatronics process management (Mechatronics Process Management) data.

• SCM version object fails to display the SCM configuration rule at thereplica site


You cannot view the SCM configuration rule at the replica site because theBrowse button is unavailable.


Open the Properties dialog box to see the SCM configuration rule. Scroll barsare 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 aGDE element under a checked out structure at a replica site, it fails.



• Hierarchical GDE structure at remote site cannot be remotely checkedout


When a hierarchical GDE structure is replicated at a remote site using multisitefunctionality, 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 samplefiles) to create Mechatronics Process Management objects in the database andthen 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 thirdparties.

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-bitplatform for the thin client, moving the browser scroll bar makes the graphics inthe 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 viewedpage.



Microsoft

The following release note pertains to Microsoft.

• Microsoft SQL Server database migration utility cannot connect tothe Oracle database


The Microsoft SQL Server database migration utility, which migrates anOracle-based Teamcenter database to SQL Server, cannot connect to the OracleSID 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. Todownload 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 Webbrowser:

– Using the Adobe Scalable Vector Graphics (SVG) Viewer:

◊ In My Teamcenter, click View→Process to view the process in the SVGviewer.

◊ In the Structure Manager application, select a supersedure and clickView→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 usingthe Microsoft XML parser.

◊ Click Edit link next to a dataset object to edit data sets using MicrosoftOffice applications (Microsoft Office integration).

– Tree expansion state and search results are not retained in the browserwhen the Back button is used. This state preservation is an enhancement inTeamcenter 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 thenetwork card has a power saving option enabled, this configuration can causethe rich client server to fail intermittently. The syslog file has an error messagesimilar 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

2D measurements . . . . . . . . . . . . . . . . 4-632D snapshots . . . . . . . . . . . . . . . . . . . 2-443D snapshot improvements . . . . . . . . . 2-51

A

Access Manager . . . . . . . . . . . . . . . . . . 3-8Access Manager Guide . . . . . . . . . . . . . 3-40Action handlersCONTMGMT-notify . . . . . . . . . . . . . 3-91notify . . . . . . . . . . . . . . . . . . . . . . . 3-85

Ad hoc Classification search . . . . . . . . . 3-73Add Status task . . . . . . . . . . . . . . . . . 3-84adhoc-signoffs handler . . . . . . . . . . . . . 2-33Administration release notes . . . . . . . 3-29,3-31, 4-31Aerospace and DefenseOwning organization . . . . . . . . . . . . 2-69Parts list management . . . . . . . . . . . 2-68Program-level security . . . . . . . . . . . 2-70Properties on relation . . . . . . . . . . . . 2-70Revision naming rules . . . . . . . 2-12, 2-69Sample program . . . . . . . . . . . . . . . 2-69

AIE class names, fixing . . . . . . . . . . . . 4-29AIWS, deprecating . . . . . . . . . . . . . . . . 1-7AIX64-bit . . . . . . . . . . . . . . . . . . . . . . . . 1-5Appearance Editor dialog box . . . . . . 4-59Properties dialog box . . . . . . . . 4-56, 4-58Release notes . . . . . . . . . . . . . . . . . . 4-58Structure Manager . . . . . . . . . . . . . . 4-59

Alias business objects . . . . . . . . . . . . . . 3-1Alternate IDsEnhancements . . . . . . . . . . . . . . . . . . 2-8NX Integration . . . . . . . . . . . . . . . . 2-63

Apache Web servers . . . . . . . . . . . . . . 4-51Appearance Editor dialog box . . . . . . . . 4-59Appearance update manager . . . . . . . . 4-61Application Interface Web Service,deprecating . . . . . . . . . . . . . . . . . . . . . 1-7Application server support . . . . . . . . . . . 2-7As-Built Manager . . . . . . . . . . . . . . . . . 3-9Assigned occurrence . . . . . . . . . . . . . . 4-20

Attribute encryption in ResourceManager . . . . . . . . . . . . . . . . . . . . . . 2-46Attributes, custom . . . . . . . . . . . . . . . . 3-31Authentication error . . . . . . . . . . . . . . 3-18auto-assign handler . . . . . . . . . . . . . . . 2-33auto-assign-rest handler . . . . . . . . . . . 2-33Autogenerating code . . . . . . . . . . . . . . . 2-9Automotive Edition upgrade . . . . . . . . 4-29

BBackup, hot . . . . . . . . . . . . . . . . . . . . 2-16Baselines . . . . . . . . . . . . . . . . . . . . . . 2-66Baselines for requirementsmanagement . . . . . . . . . . . . . . . . . . . 2-39Bill rates in Schedule Manager . . . . . . . 3-26BMIDE client . . . . . . . . . . . . . . . . . . . 3-36bmide_postupgradetotc utility . . . . . . . 4-30Boilerplate code . . . . . . . . . . . . . . . . . . 2-9BOM line columns . . . . . . . . . . . . . . . . 4-20bomwriter utility . . . . . . . . . . . . . . . . . 4-43BookmarksError . . . . . . . . . . . . . . . . . . . . . . . 4-40Launch . . . . . . . . . . . . . . . . . . . . . . 1-22

Build server code . . . . . . . . . . . . . . . . 3-32Business Modeler IDE . . . . . . . . . 3-36, 4-29Alternate IDs . . . . . . . . . . . . . . . . . . 2-8Autogenerating code . . . . . . . . . . . . . . 2-9Boilerplate code . . . . . . . . . . . . . . . . . 2-9Build server code . . . . . . . . . . . . . . . 3-32Business object constants . . . . . . . . . 1-19Business Objects view . . . . . . . . . . . 3-40Business rules inheritance . . . . . . . . 2-10C++ support . . . . . . . . . . . . . . . . . . . 2-9Conditions . . . . . . . . . . . . . . . . . . . . 2-11Deep copy enhancements . . . . . . . . . 2-11Deep copy rules . . . . . . . . . . . . . . . . 3-31Enabled property constant . . . . . . . . 3-33Enhanced naming rules . . . . . . 2-12, 2-69Item revision definition configuration(IRDC) . . . . . . . . . . . . . . . . . . . . . 2-8

Property rules . . . . . . . . . . . . . . . . . 1-23Required and visible properties . . . . . 2-11Revision naming rules . . . . . . . 2-12, 2-69Services . . . . . . . . . . . . . . . . . . . . . 2-10

PLM00001 C Teamcenter 8 Release Bulletin Index-1

Index

Business Modeler IDE client . . . . . . . . 3-36Business Modeler IDE GuideConvert secondary business objects toprimary . . . . . . . . . . . . . . . . . . . 3-42

Documentation release notes . . . . . . . 3-40Preferences . . . . . . . . . . . . . . . . . . . 3-40Relation business objects . . . . . . . . . 3-41Relation properties . . . . . . . . . . . . . . 3-41User exits . . . . . . . . . . . . . . . . . . . . 3-41

Business Objects view preference . . . . . 3-40Business rules inheritance . . . . . . . . . . 2-10business_objects.xml error . . . . . . . . . . 4-29

C

C++ API Reference . . . . . . . . . . . . . . . 3-43C++ support . . . . . . . . . . . . . . . . . . . . . 2-9Cacheless search DesignContext . . . . . . 2-60CAD BOM Alignment . . . . . . . . . . . . . . 3-8CAE items . . . . . . . . . . . . . . . . . . . . . 3-31CAE Manager . . . . . . . . . . . . . . . . . . . 3-12CAE Manager — Inspector . . . . . . . . . . 2-57Calendars in Schedule Manager . . . . . . 3-24CAM support . . . . . . . . . . . . . . . . . . . 2-64Cascading LOVs in RequirementsManager . . . . . . . . . . . . . . . . . . . . . . 3-22Cautionary statements . . . . . . . . . . . . 3-40Certification database . . . . . . . . . . . . . . 1-4Change management service . . . . . . . . 2-66Change TcClass is not supportederror . . . . . . . . . . . . . . . . . . . . . . . . . 4-29Checked-out objects, find on exit . . . . . . 2-44Checkout Explorer dialog box . . . . . . . . . 3-8Chinese characters in Windows . . . . . . 4-59ClassificationAttribute search . . . . . . . . . . . . . . . . 3-73Import and export failure . . . . . . . . . 3-10NXGraphicsBuilder . . . . . . . . . . . . . 4-18Quick search . . . . . . . . . . . . . . . . . . 4-18Release notes . . . . . . . . . . . . . . . . . . 4-18UGGraphicsBuilder . . . . . . . . . . . . . 4-18

Classification Administration . . . . . . . . . 3-8Classification, multiunit support . . . . . 2-37Clearance database integration . . . . . . 2-59Client for Office . . . . . . . . . . . . . . . . . 3-16Query error . . . . . . . . . . . . . . . . . . . 3-16

Client support for Macintosh . . . . . . . . . 2-6CloningIncremental change . . . . . . . . . . . . . 2-45Structure . . . . . . . . . . . . . . . . . . . . 2-43

Code page 932 . . . . . . . . . . . . . . . . . . . 3-36Component library management . . . . . 2-73Condition task . . . . . . . . . . . . . . . . . . 2-35Conditions . . . . . . . . . . . . . . . . . . . . . 2-11

Connection pooling, Global Services . . . 2-42Connections . . . . . . . . . . . . . . . . . . . . 4-37Consumer Packaged Goods . . . . . . . . . 2-71Content ManagementS1000D . . . . . . . . . . . . . . . . . . . . . . 3-17Tool tips . . . . . . . . . . . . . . . . . . . . . 3-17User interface . . . . . . . . . . . . . . . . . 3-17

Continue on error not supported in DataExchange . . . . . . . . . . . . . . . . . . . . . 4-23CONTMGMT-notify handler . . . . . . . . 3-91Convert secondary business objects toprimary . . . . . . . . . . . . . . . . . . . . . . 3-42Convert, Lifecycle Visualization 64-bit . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73CopyAsReference deep copy rule . . . . . . 3-28CR-assign-team-selector handler . . . . . 2-33CR-fill-in-reviewers handler . . . . . . . . . 2-33CR-notify handler . . . . . . . . . . . . . . . . 2-33Create reports, saved queries . . . . . . . . 2-38CreatingQuick-release process template . . . . . 3-84Request objects . . . . . . . . . . . . . . . . 3-81

Custom types . . . . . . . . . . . . . . . . . . . . 4-9CustomizationAttributes . . . . . . . . . . . . . . . . . . . . 3-31Release notes . . . . . . . . . . . . . . . . . . 4-45

D

Data Exchange . . . . . . . . . . . . . . . . . . 4-26Briefcase transfers . . . . . . . . . . . . . . 4-23Continue on error feature notsupported . . . . . . . . . . . . . . . . . . 4-23

Dataset, transferring . . . . . . . . . . . . 4-21Local actions on replicas . . . . . . . . . . 4-23Monitoring interface . . . . . . . . . . . . . 4-21Object Directory Services . . . . . . . . . 4-22Ownership not updated in ODS . . . . . 4-22Release notes . . . . . . . . . . . . . . . . . . 4-21

Data Exchange Web applicationsolution . . . . . . . . . . . . . . . . . . . . . . 2-42Data Integration Services Adapter (DISAdapter) . . . . . . . . . . . . . . . . . . . . . . 1-20Data synchronization . . . . . . . . . . . . . 4-31data_share utility . . . . . . . . . . . . . . . . 3-29data_sync utility . . . . . . . . . . . . . 3-29, 4-43DatabaseQuery . . . . . . . . . . . . . . . . . . . . . . . 4-66Upgrades . . . . . . . . . . . . . . . . . . . . 4-12

DatasetsAttaching . . . . . . . . . . . . . . . . . . . . 4-51Transferring . . . . . . . . . . . . . . . . . . 4-21

Debugging tools, Rich client . . . . . . . . . 2-67Deep copy ehancements . . . . . . . . . . . . 3-31

Index-2 Teamcenter 8 Release Bulletin PLM00001 C

Index

Deep copy enhancements . . . . . . . . . . . 2-11Default volumes value . . . . . . . . . . . . . 4-41default_queries utility . . . . . . . . . . . . . . 3-3DeprecationAIWS . . . . . . . . . . . . . . . . . . . . . . . . 1-7AIX 64-bit server support . . . . . . . . . . 1-5announcements . . . . . . . . . . . . . . . . . 1-5Application Interface Web Service . . . . 1-7Bookmark launch . . . . . . . . . . . . . . . 1-22Business object constants . . . . . . . . . 1-19Excel 2003 . . . . . . . . . . . . . . . . . . . . . 1-6Functions . . . . . . . . . . . . . . . . . . . . . 1-9Global Services connectors . . . . . . 1-5–1-6HP-UX OS on PA-RISC hardware . . . . 1-7Image Import utility . . . . . . . . . . . . . . 1-6IMAN_show_open_in_pv_button . . . . 1-22Java classes . . . . . . . . . . . . . . . . . . . 1-18object_backup utility . . . . . . . . . . . . 1-10object_recover utility . . . . . . . . . . . . 1-10Over-the-Web installer . . . . . . . . . . . . 1-8Report Designer . . . . . . . . . . . . . . . . . 1-6Rich client on UNIX-based operatingsystems . . . . . . . . . . . . . . . . . . . . 1-7

Schamtics in Structure Manager . . . . . 1-8SVG Viewer plug-in . . . . . . . . . . . . . 1-22Teamcenter EMC Content Storage mediatype . . . . . . . . . . . . . . . . . . . . . . . 1-8

Teamcenter Services . . . . . . . . . . . . 1-11TraceLink class . . . . . . . . . . . . . . . . . 1-6Utilities . . . . . . . . . . . . . . . . . . . . . 1-10

DesignContextCacheless search . . . . . . . . . . . . . . . 2-60Clearance database integration . . . . . 2-59

DHTML thin client . . . . . . . . . . . . . . . 4-51Disk space requirements . . . . . . . . . . . . 1-4Dispatcher client . . . . . . . . . . . . . . 3-3, 3-45Dispatcher ServerTranslation . . . . . . . . . . . . . . . . . . . 2-18Translation request priority . . . . . . . 1-22

Dispatcher Server InstallationGuide . . 3-43,3-77dispatcher_create_rqst utility . . . . . . . . 3-81Document managementIRDC . . . . . . . . . . . . . . . . . . . . . . . . 2-8Render . . . . . . . . . . . . . . . . . . . . . . 2-18

Documentation release notesAccess Manager Guide . . . . . . . . . . . 3-40Business Modeler IDE Guide . . . . . . 3-40C++ API Reference . . . . . . . . . . . . . . 3-43Dispatcher Server InstallationGuide . . . . . . . . . . . . . . . . . 3-43, 3-77

ERP Connect Integration Guide . . . . 3-44Firefox . . . . . . . . . . . . . . . . . . . . . . . 3-7

Getting Started with Aerospace andDefense . . . . . . . . . . . . . . . . . . . 3-44

Getting Started with Dispatcher(Translation Management) . . . . . . 3-45

In general . . . . . . . . . . . . . . . . . . . . 3-38Installation on UNIX and Linux ServersGuide . . . . . . . . . . . . . . . . . 3-48, 3-58

Installation on Windows ServersGuide . . . . . . . . . . . . . . . . . . . . . 3-58

Online help search issue . . . . . . . . . . 3-58Preferences and Environment VariablesReference . . . . . . . . . . . . . . . . . . 3-68

Rich Client Interface Guide . . . . . . . . 3-72Schedule Manager Guide . . . . . . . . . 3-74Services Reference . . . . . . . . . . . . . . 3-77Structure Manager Guide . . . . . . . . . 3-78Teamcenter Environment ManagerHelp . . . . . . . . . . . . . . . . . . . . . . 3-78

Upgrade Guide . . . . . . . . . . . . . . . . 3-78Utilities Reference . . . . . . . . . . . . . . 3-80Workflow Designer Guide . . . . . . . . . 3-84ZIP file . . . . . . . . . . . . . . . . . . . . . . . 3-7

Docx files in Requirements Manager . . . 3-21Download hyperlink not available . . . . . 4-38Drag and drop . . . . . . . . . . . . . . . . . . 3-72dsa_util utility . . . . . . . . . . . . . . . . . . 4-28Duplicate schedules . . . . . . . . . . . . . . . 3-24

E

ECAD libraryImport failure . . . . . . . . . . . . . 3-10, 3-30Spaces in field values . . . . . . . . . . . . 3-10

EDA client logging . . . . . . . . . . . . . . . 2-73Editing a GDE element . . . . . . . . . . . . 4-67EIM_check_error . . . . . . . . . . . . . . . . 4-70EINT_init_module function . . . . . . . . . 4-46eIntegrator Admin customization . . . . . 4-46ELSA Synergy graphics card . . . . . . . . 4-65Embedded Software Design DataManagement . . . . . . . . . . . . . . . . . . . 2-47Embedded Visualization installation anduninstallation . . . . . . . . . . . . . . . . . . 4-65Enabled property constant . . . . . . . . . . 3-33EnhancedDocument generation . . . . . . . . . . . . 2-39Export to Excel . . . . . . . . . . . . . . . . 2-21Naming rules . . . . . . . . . . . . . . 2-12, 2-69Simulation process launch . . . . . . . . 2-57

ensure_site_consistency utility . . . . . . . 4-26Environment settings, non-English localesnon-UTF-8 environmentsLinux . . . . . . . . . . . . . . . . 3-50, 3-54


Index

UNIX . . . . . . . . . . . . . . . . 3-50, 3-54Windows . . . . . . . . . . . . . . . . . . 3-60

Environment variablesLANG . . . . . . . . . . . . . . . . . . . . . . . 3-50LC_ALL . . . . . . . . . . . . . . . . . . . . . 3-50Obsolete . . . . . . . . . . . . . . . . . . . . . 1-43UTF-8 . . . . . . . . . . . . . . . . . . . . . . . 2-67

EPM-check-object-properties handler . . 2-33EPM-check-related-objects handler . . . . 2-33EPM-create-sub-process handler . . . . . 2-33EPM-set-task-result-to-propertyhandler . . . . . . . . . . . . . . . . . . . . . . . 2-35ERP Connect Integration Guide . . . . . . 3-44Error does not appear . . . . . . . . . . . . . 4-66Ethernet MAC addresses, SunSolaris . . . . . . . . . . . . . . . . . . . . . . . 4-57ETS_update_state_delaypreference . . . . . . . . . . . . . . . . . 3-68–3-69Excel 2003 deprecation . . . . . . . . . . . . . 1-6Excel LiveCascading LOVs . . . . . . . . . . . . . . . 3-22Manufacturing Process Planner . . . . 3-22Excel live sheet, obsolete . . . . . . . . . . . 1-22Export Status dialog box . . . . . . . . . . . 4-48Exporting vendor management . . . . . . . 4-28Extensions for Microsoft Office . . . . . . . 2-21Externalization, accidental . . . . . . . . . 4-32Extra logon challenge . . . . . . . . . . . . . 4-42

F

Fail action . . . . . . . . . . . . . . . . . . . . . 2-35Failure paths . . . . . . . . . . . . . . . . . . . 2-35FCCAutomatic configuration . . . . . . . . . . 2-15Manual configuration . . . . . . . . . . . . 2-15

Feature support . . . . . . . . . . . . . . . . . 2-65File Management SystemAbrupt termination . . . . . . . . . . . . . 4-35Configuration . . . . . . . . . . . . . . . . . 4-35IMF_fmsfile_import ITK functions . . . 4-34IMF_import_file ITK functions . . . . . 4-34

Files, store and forward . . . . . . . . . . . . 2-13Firefox Web browserGraphics disappear . . . . . . . . . . . . . 4-68Launching documentation . . . . . . . . . 3-7Release notes . . . . . . . . . . . . . . . . . . 4-68Teamcenter help . . . . . . . . . . . . . . . 4-68

FMS database access . . . . . . . . . . . . . . 2-14FMS URL path extensions . . . . . . . . . . 2-26Folder expansion slow in Client forOffice . . . . . . . . . . . . . . . . . . . . . . . . 3-16format argument . . . . . . . . . . . . . . . . . 4-43FSC failure . . . . . . . . . . . . . . . . . . . . . 3-13

FSC_DoNotCompressExtensionsproperty . . . . . . . . . . . . . . . . . . . . . . 3-12Full-text search for Microsoft Officedocuments . . . . . . . . . . . . . . . . . . . . . 2-7FunctionsDeprecated . . . . . . . . . . . . . . . . . . . . 1-9Obsolete . . . . . . . . . . . . . . . . . . . . . 1-24

Future enhancements . . . . . . . . . . . . . 4-19

G

Gateway application . . . . . . . . . . . . . . 2-74GDELink . . . . . . . . . . . . . . . . . . . . . . . . 4-20Structure . . . . . . . . . . . . . . . . . . . . 4-67

Getting Started with Aerospace andDefense . . . . . . . . . . . . . . . . . . . . . . 3-44Getting Started with Dispatcher (TranslationManagement) . . . . . . . . . . . . . . . . . . 3-45Global ServicesAutopopulated nonmandatoryfields . . . . . . . . . . . . . . . . . . . . . 4-24

Conversion tool shows an error . . . . . 4-25ItemRevision sequences . . . . . . . . . . 4-22max_objects_limit element . . . . . . . . 3-47maximum.query.objects parameter . . 3-47NoSuchMethodError exception . . . . . 4-24Ownership not updated in ODS . . . . . 4-22Query limit precedence . . . . . . . . . . . 3-47Release notes . . . . . . . . . . . . . . . . . . 4-24Sample BOD does not display revisionnumber . . . . . . . . . . . . . . . . . . . 4-24

Sample Teamcenter Item BOD . . . . . 4-24SOA connection pooling . . . . . . . . . . 2-42Teamcenter 8 rich client connector . . . 2-42Global Services connectorsSAP Connector . . . . . . . . . . . . . . . . . 1-6Teamcenter 2007 Rich ClientConnector . . . . . . . . . . . . . . . . . . . 1-5

Teamcenter 8 Connector . . . . . . . . . . . 1-6Teamcenter Engineering 2005/2007Connector . . . . . . . . . . . . . . . . . . 1-5

Teamcenter Engineering v9Connector . . . . . . . . . . . . . . . . . . . 1-5

Global Technical Access Center(GTAC) . . . . . . . . . . . . . . . . . . . . . 1-2–1-3globalservices.properties file . . . . . . . . . 3-47GM Overlay . . . . . . . . . . . . . . . . 3-36, 4-29Character set . . . . . . . . . . . . . . . . . . 4-53Release notes . . . . . . . . . . . . . . . . . . 4-29UNIX . . . . . . . . . . . . . . . . . . . . . . . 4-53Upgrade . . . . . . . . . . . . . . . . . . . . . 4-29

gmo_change_item_id_naming_ruleutility . . . . . . . . . . . . . . . . . . . . . . . . 4-30


Index

GMS_offline_use_TcGS preference . . . . 3-68GMS_site_checkin_after_importpreference . . . . . . . . . . . . . . . . . . . . . 3-68Graphics cardsELSA Synergy . . . . . . . . . . . . . . . . . 4-65NVidia Quadro 2 Pro Graphics . . . . . 4-65NVidia Quadro 4 500 GoGL . . . . . . . 4-65

Graphics disappear . . . . . . . . . . . . . . . 4-68GRM Rules tab . . . . . . . . . . . . . . . . . . 2-10Guided component searchAdding connection point definitions . . 4-19Release notes . . . . . . . . . . . . . . . . . . 4-19

H.h files . . . . . . . . . . . . . . . . . . . . . . . . 4-45Hardware requirements . . . . . . . . . . . . . 1-4HarnessConnection list . . . . . . . . . . . . . . . . . 4-37Structure . . . . . . . . . . . . . . . . 4-38–4-39

Header files . . . . . . . . . . . . . . . . . . . . 4-45Help, technical . . . . . . . . . . . . . . . . . . . 1-3HP-UX . . . . . . . . . . . . . . . . . . . . . . . . 4-54ODS . . . . . . . . . . . . . . . . . . . . . . . . 3-30PA-RISC hardware . . . . . . . . . . . . . . . 1-7Properties dialog box . . . . . . . . 4-56, 4-58Release notes . . . . . . . . . . . . . . . . . . 4-54

HTTP enabled Multi-Site Collaboration andSSO . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

IICS_GraphicsBuilder . . . . . . . . . . . . . 4-18Identifier business objects . . . . . . . . . . . 3-1IDSM servers . . . . . . . . . . . . . . . . . . . 4-52idsminetd utility . . . . . . . . . . . . . . . . . 3-63Image Import utility, deprecating . . . . . . 1-6IMAN_Drawing relation types . . . . . . . 4-11IMAN_show_open_in_pv_buttonpreference . . . . . . . . . . . . . . . . . . . . . 1-22Impact Analysis view . . . . . . . . . . . . . . 3-9Implemented By relationship . . . . . . . . 4-15Import failureClassification . . . . . . . . . . . . . . . . . . 3-10Spaces in field names . . . . . . . . . . . . 3-10TcXml . . . . . . . . . . . . . . . . . . . . . . . 3-30

import_dfa_file utility . . . . . . . . . . . . . 1-10Importing vendor management . . . . . . 4-28Incompatible Teamcenter Engineeringconnectors . . . . . . . . . . . . . . . . . . . . . 4-24Incremental change . . . . . . . . . . . 2-45, 4-14Initial value property rules . . . . . . . . . 4-48InstallationEmbedded viewer . . . . . . . . . . . . . . . . 3-6Four-tier clients . . . . . . . . . . . . . . . . . 4-2

Maintenance pack . . . . . . . . . . . . . . . 1-1Online help . . . . . . . . . . . . . . . . . . . . 3-7Teamcenter 2007 . . . . . . . . . . . . . . . . 4-1Teamcenter 8 . . . . . . . . . . . . . . . . 1-1, 3-1Thin client . . . . . . . . . . . . . . . . . . . . . 4-1

Installation on UNIX and Linux ServersGuide . . . . . . . . . . . . . . . . . . . . . . . . 3-48Installation on Windows ServersGuide . . . . . . . . . . . . . . . . . . . . . . . . 3-58Integration Toolkit, see ITKInternationalization . . . . . . . . . . . . . . . 1-4Release notes . . . . . . . . . . . . . . . . . . 4-51Thin client . . . . . . . . . . . . . . . . . . . . 4-51

Internationalization release notes . . . . . 3-36Internet Explorer . . . . . . . . . . . . . . . . 3-12Interoperability . . . . . . . . . . . . . . . . . 3-64Interspec integration . . . . . . . . . . 2-71, 3-29Invalid item IDs, Teamcenter Integration forNX . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40IRDC . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8IS NULL operator . . . . . . . . . . . . . . . . 4-65iSeries . . . . . . . . . . . . . . . . . . . . . . . . 4-63Item revision definition configuration(IRDC) . . . . . . . . . . . . . . . . . . . . . . . . 2-8ItemRevision sequences . . . . . . . . . . . . 4-22ITKRelease notes . . . . . . . . . . . . . . . . . . 4-45Revise and save as . . . . . . . . . . . . . . 3-31

JJapanese characters . . . . . . . . . . . . . . 3-36Java classesDeprecated . . . . . . . . . . . . . . . . . . . 1-18Obsolete . . . . . . . . . . . . . . . . . . . . . 1-44

LLANG variable . . . . . . . . . . . . . . . . . . 3-50Language support . . . . . . . . . . . . . . . . 2-30Large databases . . . . . . . . . . . . . . . . . . 4-9Launch simulation process remotely . . . 2-58LC_ALL variable . . . . . . . . . . . . . . . . 3-50LDAP_member_list_attr preference . . . 4-31LDAP_sync_group_flags preference . . . 4-32LDAP_sync_member_flagspreference . . . . . . . . . . . . . . . . . . . . . 4-32LDAP_sync_role_flags preference . . . . . 4-32LDAP_sync_user_flags preference . . . . 4-32ldapsync utility . . . . . . . . . . . . . . 4-31–4-32libcurl library . . . . . . . . . . . . . . . . . . . 4-46Licensing levelAuthor . . . . . . . . . . . . . . . . . . . . . . . 2-7Consumer . . . . . . . . . . . . . . . . . . . . . 2-7

Lifecycle Viewer


Index

Disabled toolbars . . . . . . . . . . . . . . . 3-19Lifecycle VisualizationAuthentication error . . . . . . . . . . . . 3-18Bookmark . . . . . . . . . . . . . . . . . . . . 4-64Data Integration Services Adapter (DISAdapter) . . . . . . . . . . . . . . . . . . . 1-20

Installation . . . . . . . . . . . . . . . . . . . . 3-6Markup layers . . . . . . . . . . . . . . . . . 4-63NX assembly files . . . . . . . . . . . . . . . 4-62Over-the-Web Installer . . . . . . . . . . . . 3-6Part not visible . . . . . . . . . . . . . . . . 3-18Persistent 2D measurements . . . . . . 4-63PRT files . . . . . . . . . . . . . . . . . 4-62, 4-64Release notes . . . . . . . . . . . . . . 3-18, 4-62Repaint problems on Windows . . . . . 4-65Software error . . . . . . . . . . . . . . . . . 3-19Teamcenter Publish . . . . . . . . . . . . . 3-14UGALTREP files . . . . . . . . . . . . . . . 4-62UGPART files . . . . . . . . . . . . . . . . . 4-62Unable to launch . . . . . . . . . . . . . . . 4-63Viewer . . . . . . . . . . . . . . . . . . . 3-6, 3-18Windows Vista . . . . . . . . . . . . . 4-63, 4-65

Lifecycle Visualization performanceimprovements . . . . . . . . . . . . . . . . . . 2-66LinuxAppearance update manager . . . . . . . 4-61IDSM servers . . . . . . . . . . . . . . . . . 4-52Release notes . . . . . . . . . . . . . . . . . . 4-61SUSE Linux Enterprise Server(SLES) . . . . . . . . . . . . . . . . . . . . . 1-5

Locale support . . . . . . . . . . . . . . . . . . 2-30Localization . . . . . . . . . . . . . . . . . . . . . 1-4Lost data, Microsoft Windows . . . . . . . . 4-61

M

Maintenance pack installation . . . . . . . . 1-1make_user utility . . . . . . . . . . . . 4-31–4-32makefiles . . . . . . . . . . . . . . . . . . . . . . 3-32ManufacturingPreferences . . . . . . . . . . . . . . . . . . . 2-46Time management . . . . . . . . . . . . . . 2-43

Manufacturing Process ManagementGuided component search . . . . . . . . . 4-19Release notes . . . . . . . . . . . . . . . . . . 4-18

Manufacturing Process Planner2D Viewer tab . . . . . . . . . . . . . . . . . 2-44Assigned occurrence . . . . . . . . . . . . . 4-20BOM line columns . . . . . . . . . . . . . . 4-20Calculate allocated time . . . . . . . . . . 3-20Excel Live . . . . . . . . . . . . . . . . . . . . 3-22Find checked-out objects on exit . . . . 2-44GDE link . . . . . . . . . . . . . . . . . . . . . 4-20

Release notes . . . . . . . . . . . . . . 3-20, 4-20Repair Broken Links dialog box . . . . . 4-20Resequence crash . . . . . . . . . . . . . . . 3-20Separation of view and edit propertiesfunctionality . . . . . . . . . . . . . . . . 4-15

Time management . . . . . . . . . . . . . . 2-43Variant condition . . . . . . . . . . . . . . . 4-20

Manufacturing Tooling Library sampledata . . . . . . . . . . . . . . . . . . . . . . . . . 4-19MapForce 2008 . . . . . . . . . . . . . . . . . . 2-12Mapper . . . . . . . . . . . . . . . . . . . . . . . 4-66Markup layers . . . . . . . . . . . . . . . . . . 4-63Master schedules . . . . . . . . . . . . . . . . 3-23max_objects_limit element . . . . . . . . . . 3-47maximum.query.objects property . . . . . 3-47ME-10 vector files . . . . . . . . . . . . . . . . 4-63Mechatronics Process ManagementEditing a GDE element . . . . . . . . . . 4-67GDE structure . . . . . . . . . . . . . . . . . 4-67Release notes . . . . . . . . . . . . . . . . . . 4-66Sample ITK program/utility . . . . . . . 4-67

Mentor PADS . . . . . . . . . . . . . . . . . . . 2-73Microsoft 2000 . . . . . . . . . . . . . . . . . . 4-60Microsoft OfficeClient . . . . . . . . . . . . . . . . . . . . . . . 2-31Documents . . . . . . . . . . . . . . . 4-13, 4-47

Microsoft Project Plugin . . . . . . . . . . . . 3-11Microsoft release notes . . . . . . . . . . . . 4-68Microsoft Windows, lost data . . . . . . . . 4-61migrate_alias utility . . . . . . . . . . . . . . . 3-1MIMIC option . . . . . . . . . . . . . . . . . . . 4-64Modal dialogs, rich client . . . . . . . . . . . 4-47Model Error, business_objects.xml . . . . 4-29Monitoring interface . . . . . . . . . . . . . . 4-21Mozilla Web browserRelease notes . . . . . . . . . . . . . . . . . . 4-69Teamcenter functionality notsupported . . . . . . . . . . . . . . . . . . 4-69

Multi language support . . . . . . . . . . . . 2-30Multi-SiteRelease notes . . . . . . . . . . . . . . . . . . 3-20

Multi-Site and Schedule Manager . . . . . 3-23Multi-Site CollaborationLicenses . . . . . . . . . . . . . . . . . . . . . 4-28Oracle parameter . . . . . . . . . . . . . . . 4-26Release notes . . . . . . . . . . . . . . . . . . 4-26Remote checkin . . . . . . . . . . . . . . . . 4-27Security Services . . . . . . . . . . . . . . . 4-26

Multi-Site Collaboration GuideInteroperability . . . . . . . . . . . . . . . . 3-64Release notes . . . . . . . . . . . . . . . . . . 3-63

Multi-Structure Manager, 2D Viewertab . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44


Index

Multi-unit support in Classification . . . 2-37Multilanguage support for clients . . . . . 3-83Multiple View Editor, removal . . . . . . . 1-22MVE, removal . . . . . . . . . . . . . . . . . . . 1-22My TeamcenterMicrosoft Office documents . . . . . . . . 4-13Perspective . . . . . . . . . . . . . . . . . . . 2-29Product view . . . . . . . . . . . . . . . . . . 4-14Release notes . . . . . . . . . . . . . . . . . . 4-13Save button . . . . . . . . . . . . . . . . . . . 4-14Text file . . . . . . . . . . . . . . . . . . . . . . 4-13Validation report . . . . . . . . . . . . . . . 4-14Viewer pane . . . . . . . . . . . . . . 4-13–4-14

N

Named variant expression . . . . . . . . . . 4-16Naming rules . . . . . . . . . . . . . . . . . . . 4-30Network cards, power saving option . . . 4-70New and changed Teamcenter 8features . . . . . . . . . . . . . . . . . . . . . . . 2-1New Content Management Permissions dialogbox . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17NoSuchMethodError exception . . . . . . . 4-24Notification of translation ordercreation . . . . . . . . . . . . . . . . . . . . . . 3-91notify handler . . . . . . . . . . . . . . . . . . . 3-85Notifying of task status . . . . . . . . . . . . 3-85NVE . . . . . . . . . . . . . . . . . . . . . . . . . 4-16NVidia Quadro 2 Pro Graphics card . . . 4-65NVidia Quadro 4 500 GoGL graphicscard . . . . . . . . . . . . . . . . . . . . . . . . . 4-65NXAssembly files . . . . . . . . . . . . . . . . . 4-62Does not launch . . . . . . . . . . . . . . . . 4-39Export . . . . . . . . . . . . . . . . . . . . . . 4-48Lifecycle Visualization . . . . . . . . . . . . 3-6Upgrade . . . . . . . . . . . . . . . . . . . . . 4-39

NX drawings . . . . . . . . . . . . . . . . . . . 2-75NX Integration . . . . . . . . . . . . . . 2-75, 3-21Alternate ID support . . . . . . . . . . . . 2-63Baselines . . . . . . . . . . . . . . . . . . . . 2-66CAM support . . . . . . . . . . . . . . . . . . 2-64Occurrence override support . . . . . . . 2-64Release notes . . . . . . . . . . . . . . . . . . 3-21Support for features . . . . . . . . . . . . . 2-65

NX/requirements integration . . . . . . . . 2-75NXGraphicsBuilder . . . . . . . . . . . . . . . 4-18nxmgr_add_note_types utility . . . . . . . 4-11

O

Object Directory Services . . . . . . . . . . . 4-22object_backup utility, deprecating . . . . . 1-10

object_recover utility, deprecating . . . . . 1-10ObsoleteEnvironment variables . . . . . . . . . . . 1-43Excel live sheet . . . . . . . . . . . . . . . . 1-22Functions . . . . . . . . . . . . . . . . . . . . 1-24Java classes . . . . . . . . . . . . . . . . . . . 1-44Preferences . . . . . . . . . . . . . . . . . . . 1-41Utilities . . . . . . . . . . . . . . . . . . . . . 1-37Web tier parameters . . . . . . . . . . . . . 1-21

Occurrence override support . . . . . . . . 2-64ODS support . . . . . . . . . . . . . . . . . . . . 3-30Online help . . . . . . . . . . . . . . . . . . 3-7, 3-73Search issue . . . . . . . . . . . . . . . . . . 3-58

Operating systems, release notes . . . . 4-52,4-64Operations, workflow . . . . . . . . . . . . . . 2-62Options and Variants . . . . . . . . . . . . . . 2-47ORA-12571 error . . . . . . . . . . . . . . . . . 4-70Oracle10g installation requirements . . . . . . 4-69ORA-12571 error . . . . . . . . . . . . . . . 4-70Parameter . . . . . . . . . . . . . . . . . . . . 4-26Power saving option error . . . . . . . . . 4-70Release notes . . . . . . . . . . . . . . . . . . 4-69SQL Server database migrationutility . . . . . . . . . . . . . . . . . . . . . 4-68

OrCAD . . . . . . . . . . . . . . . . . . . . . . . . 2-73OrganizationCreating a person . . . . . . . . . . . . . . 4-33Default volume . . . . . . . . . . . . . . . . 4-33Redundant events logged . . . . . . . . . 4-33Release notes . . . . . . . . . . . . . . . . . . 4-33Search . . . . . . . . . . . . . . . . . . . . . . 2-32

Orphan types . . . . . . . . . . . . . . . . . . . . 4-4Over-the-Web installer, deprecating . . . . 1-8Ownership not updated in ODS . . . . . . 4-22Owning organization . . . . . . . . . . 2-30, 2-69

P

PA-RISC hardware . . . . . . . . . . . . . . . . 1-7PAD . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47Parts list management . . . . . . . . . . . . 2-68Pasting links . . . . . . . . . . . . . . . . . . . 3-13PdfGenerator translator, support . . . . . 3-73PER_CLIENT setting . . . . . . . . . . . . . . 4-2Permission denied . . . . . . . . . . . . . . . . . 4-2Persistent 2D measurements . . . . . . . . 4-63Platform-specific release notes . . . 4-52, 4-64PLM XML . . . . . . . . . . . . . . . . . . . . . 2-41Import/export . . . . . . . . . . . . . . . . . 4-48Release notes . . . . . . . . . . . . . . . . . . 4-28Vendor management import andexport . . . . . . . . . . . . . . . . . . . . 4-28


Index

PLMXML_export_packed_bom_<transfername> preference . . . . . . . . 2-41PLMXML_put_pie_log_in_syslogpreference . . . . . . . . . . . . . . . . . 3-68, 3-70Pool manager . . . . . . . . . . . . . . . . . . . 4-54Positional matrix information,transferring . . . . . . . . . . . . . . . . . . . 2-57Power saving option error . . . . . . . . . . 4-70PowerPoint . . . . . . . . . . . . . . . . . . . . . 4-47PreferencesETS_update_state_delay . . . . . 3-68–3-69GMS_offline_use_TcGS . . . . . . . . . . . 3-68GMS_site_checkin_after_import . . . . 3-68IMAN_show_open_in_pv_button . . . . 1-22LDAP_sync_group_flags . . . . . . . . . . 4-32LDAP_sync_member_flags . . . . . . . . 4-32LDAP_sync_role_flags . . . . . . . . . . . 4-32LDAP_sync_user_flags . . . . . . . . . . . 4-32Lock . . . . . . . . . . . . . . . . . . . . . . . . 2-17Obsolete . . . . . . . . . . . . . . . . . . . . . 1-41PLMXML_export_packed_bom_<transfername> . . . . . . . . . . . . . 2-41

PLMXML_put_pie_log_in_syslog . . . 3-68,3-70

PS_Find_Number_Validation . . . . . . 3-29QSEARCH . . . . . . . . . . . . . . . . . . . 3-30shared memory . . . . . . . . . . . . . . . . 2-17TC_NX_Foreign_Datasets . . . . . 3-68, 3-71TC_remote_checkin_relation_send_as_replica . . . . . . . . . . . . . . . . . . . . 4-27

TC_ugmaster_name_separator . . . . 3-68,3-72

Transient_Volume_RootDir . . . . . . . . 4-35View NX .prt file as 2D . . . . . . . . . . . 4-64

Preferences and Environment VariablesReference . . . . . . . . . . . . . . . . . . . . . 3-68Preferences for Business Modeler IDEGuide . . . . . . . . . . . . . . . . . . . . . . . . 3-40preferences_manager utility . . . . . . . . . . 3-3Priority and status in ScheduleManager . . . . . . . . . . . . . . . . . . . . . . 3-25Process, creating new . . . . . . . . . . . . . 2-46Product release notes . . . . . . . . . . . . . . 3-1Product structure . . . . . . . . . . . . . . . . 2-57Product viewsEnhancements . . . . . . . . . . . . . . . . . 2-51My Teamcenter . . . . . . . . . . . . . . . . 4-14Teamcenter’s lifecycle visualizationmockup . . . . . . . . . . . . . . . . . . . 4-63

Program-level security . . . . . . . . . . . . . 2-70ProjectSearch . . . . . . . . . . . . . . . . . . . . . . 2-32Support . . . . . . . . . . . . . . . . . . . . . . 2-64

PropertiesDialog box . . . . . . . . . . . . 4-52, 4-56, 4-58Relation . . . . . . . . . . . . . . . . . . . . . 2-70Required . . . . . . . . . . . . . . . . . . . . . 2-11Synchronizing . . . . . . . . . . . . . . . . . 4-50

Property constants . . . . . . . . . . . . . . . 3-33Property constants framework . . . . . . . 1-23Property Finder Formatter search results,Report Designer . . . . . . . . . . . . . . . . 4-16PRT files . . . . . . . . . . . . . . . . . . 4-62, 4-64PS_Find_Number_Validationpreference . . . . . . . . . . . . . . . . . . . . . 3-29PublishModular variant configurations . . . . . 4-21Release notes . . . . . . . . . . . . . . . . . . 4-21

PUBS kit long filenames . . . . . . . . . . . . 3-7

Q

QSEARCH preference . . . . . . . . . . . . . 3-30Queries . . . . . . . . . . . . . . . . . . . . . . . . 3-3Query error in Client for Office . . . . . . . 3-16Quick search . . . . . . . . . . . . . . . . . . . . 4-18Quick-release process template . . . . . . 3-84

R

Realized By relationship . . . . . . . . . . . 4-15RedBackground . . . . . . . . . . . . . . . . . . . 4-47Datasets . . . . . . . . . . . . . . . . . . . . . 4-47

Reference designators . . . . . . . . . . . . . 4-17RelationBusiness objects . . . . . . . . . . . . . . . . 3-41Properties . . . . . . . . . . . . . . . . . . . . 3-41

Relationships . . . . . . . . . . . . . . . . . . . 4-15Security Services . . . . . . . . . . . . . . . . 4-41Remote import . . . . . . . . . . . . . . . . . . 3-14RemovalMultiple View Editor . . . . . . . . . . . . 1-22MVE . . . . . . . . . . . . . . . . . . . . . . . . 1-22

Render management . . . . . . . . . . . . . . 3-72With Lifecycle Visualization 64-bit . . 3-73

Render, item revision . . . . . . . . . . . . . . 2-18Rendition Management . . . . . . . . . . . . 2-18Repair Broken Links dialog box . . . . . . 4-20Repeatable Digital Validation (RDV)Named variant expression . . . . . . . . 4-16Release notes . . . . . . . . . . . . . . . . . . 4-16

Replicas and life cycle states . . . . . . . . 4-23Report DesignerDeprecating . . . . . . . . . . . . . . . . . . . . 1-6Property Finder Formatter searchresults . . . . . . . . . . . . . . . . . . . . 4-16


Index

Release notes . . . . . . . . . . . . . . . . . . 4-16Required properties . . . . . . . . . . . . . . . 2-11Requirements integration . . . . . . . . . . 2-38Requirements Manager . . . . . . . . . . . . 3-27Cascading LOVs . . . . . . . . . . . . . . . 3-22Multi choice . . . . . . . . . . . . . . . . . . . 3-22Reference designators . . . . . . . . . . . . 4-17Release notes . . . . . . . . . . . . . . 3-21, 4-17Special characters in docx files . . . . . 3-21Thin client . . . . . . . . . . . . . . . . . . . . 2-27Trace link options . . . . . . . . . . . . . . 3-21

Resource ManagerAttribute encryption . . . . . . . . . . . . . 2-46Sample data . . . . . . . . . . . . . . . . . . 4-19Updating Machine Tool Library . . . . . 2-47

Restart fails . . . . . . . . . . . . . . . . . . . . 4-43Resume command . . . . . . . . . . . . . . . . 3-74Revise operation . . . . . . . . . . . . . . . . . 3-31Revision naming rules . . . . . . . . . 2-12, 2-69Rich clientDatasets . . . . . . . . . . . . . . . . . . . . . 4-47Debugging tools . . . . . . . . . . . . . . . . 2-67Deprecated on UNIX-based operatingsystems . . . . . . . . . . . . . . . . . . . . 1-7

Impact Analysis view . . . . . . . . . . . . . 3-9Microsoft Office documents . . . . . . . . 4-47Modal dialogs . . . . . . . . . . . . . . . . . 4-47Not supported on HP-UX . . . . . . . . . . 2-6PowerPoint . . . . . . . . . . . . . . . . . . . 4-47Red background . . . . . . . . . . . . . . . . 4-47Release notes . . . . . . . . . . . . . . . . . . 4-47Repaint problems on Windows . . . . . 4-65Rich client server fails . . . . . . . . . . . 4-70Search . . . . . . . . . . . . . . . . . . . . . . 2-29Viewer . . . . . . . . . . . . . . . . . . . . . . . 3-6

Rich Client Interface Guide . . . . . . . . . 3-72Ad hoc Classification search . . . . . . . 3-73Classification attribute search . . . . . . 3-73Drag and drop . . . . . . . . . . . . . . . . . 3-72Online help . . . . . . . . . . . . . . . . . . . 3-73Render management . . . . . . . . . . . . 3-72Resume command . . . . . . . . . . . . . . 3-74

Rich Client Lite Edition . . . . . . . . . . . . . 3-4Rich client perspectives . . . . . . . . . . . . 2-28Rich client views . . . . . . . . . . . . . . . . . 2-28

S

S1000D Content Management . . . . . . . 3-17Sample program . . . . . . . . . . . . . . . . . 2-69Save As operation . . . . . . . . . . . . 3-24, 3-31Save button . . . . . . . . . . . . . . . . . . . . 4-14Saved query . . . . . . . . . . . . . . . . 4-65–4-66

Schedule ManagerBill rates . . . . . . . . . . . . . . . . . . . . . 3-26Calendar . . . . . . . . . . . . . . . . . . . . . 3-24Close button error . . . . . . . . . . . . . . 4-17Cut/Copy/Paste . . . . . . . . . . . . . . . . 4-18Duplicate schedules . . . . . . . . . . . . . 3-24Master schedules . . . . . . . . . . . . . . . 3-23Multi-Site . . . . . . . . . . . . . . . . . . . . 3-23Overwrite dialog box . . . . . . . . . . . . 4-17Release notes . . . . . . . . . . . . . . 3-23, 4-17Save As operation . . . . . . . . . . . . . . 3-24Summary task . . . . . . . . . . . . . . . . . 3-23Template chooser . . . . . . . . . . . . . . . 3-25

Schedule Manager GuideAccess changes for multisiteschedules . . . . . . . . . . . . . . . . . . 3-76

Multisite schedules . . . . . . . . . . . . . 3-74Scheduling . . . . . . . . . . . . . . . . . 2-38–2-39Enhancements . . . . . . . . . . . . . . . . . 2-39Extensions . . . . . . . . . . . . . . . . . . . 2-38Templates . . . . . . . . . . . . . . . . . . . . 2-38

Schema mapping among Teamcenter productversions . . . . . . . . . . . . . . . . . . . . . . 2-41Schematics in Structure Manager . . . . . . 1-8SCM configuration rule . . . . . . . . . . . . 4-66Search based on relation properties . . . 3-44Searching by owning organization . . . . 2-30Security ServicesDispatcher client . . . . . . . . . . . . . . . . 3-3Logon . . . . . . . . . . . . . . . . . . . . . . . 3-11

Separation of view and edit propertiesfunctionality . . . . . . . . . . . . . . . . . . . 4-15Service-oriented architecture (SOA)Alternate ID support . . . . . . . . . . . . 2-63Baselines . . . . . . . . . . . . . . . . . . . . 2-66CAM support . . . . . . . . . . . . . . . . . . 2-64Change management service . . . . . . . 2-66Connection pooling . . . . . . . . . . . . . . 2-42Enhancements . . . . . . . . . . . . . . . . . 2-62Feature support . . . . . . . . . . . . . . . . 2-65libcurl library . . . . . . . . . . . . . . . . . 4-46Lifecycle Visualization support . . . . . 2-66Miscellaneous new services . . . . . . . . 2-65New features . . . . . . . . . . . . . . . . . . 2-62Occurrence override support . . . . . . . 2-64Project support . . . . . . . . . . . . . . . . 2-64Release notes . . . . . . . . . . . . . . . . . . 4-46Teamcenter Gateway for EDA . . . . . . 2-73Teamcenter Publish . . . . . . . . . . . . . 2-63Workflow operations . . . . . . . . . . . . . 2-62WSDL support . . . . . . . . . . . . . . . . . 2-63

Services, see Service-oriented architecture(SOA)


Index

Services Reference . . . . . . . . . . . . . . . 3-77Services, creating with the Business ModelerIDE . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Showing unconfigured assignedoccurrences . . . . . . . . . . . . . . . . . . . . 2-45SimulationProcess launch, enhanced . . . . . . . . . 2-57Remote process launch . . . . . . . . . . . 2-58Structure . . . . . . . . . . . . . . . . . . . . 2-57

Simulation configuration . . . . . . . . . . . 3-12Site definition . . . . . . . . . . . . . . . . . . . 2-19smlutility utility . . . . . . . . . . . . . . . . . 4-44SOA, see Service-oriented architecture,Service-oriented architecture (SOA)Software requirements . . . . . . . . . . . . . 1-4Solaris 64-bit and LifecycleVisualization . . . . . . . . . . . . . . . . . . . 3-73Solaris, Teamcenter EDA . . . . . . . . . . . 4-49Specification Manager . . . . . . . . . . . . . 2-72Specification transfer . . . . . . . . . . . . . 3-29SQL Server database migrationutility . . . . . . . . . . . . . . . . . . . . . . . . 4-68Status and priority in ScheduleManager . . . . . . . . . . . . . . . . . . . . . . 3-25Structure Manager . . . . . . . . . . . . . . . 3-27AIX . . . . . . . . . . . . . . . . . . . . . . . . . 4-59Appearance Editor dialog box . . . . . . 4-59Baseline . . . . . . . . . . . . . . . . . . . . . 4-15Four-tier server session timeout . . . . 4-15Implemented By relationship . . . . . . 4-15Incremental change . . . . . . . . . . . . . 4-14NX export . . . . . . . . . . . . . . . . . . . . 4-48Realized By relationship . . . . . . . . . . 4-15Release notes . . . . . . . . . . . . . . 3-27, 4-14Schematics . . . . . . . . . . . . . . . . . . . . 1-8Separation of view and editproperties . . . . . . . . . . . . . . . . . . 4-15

Viewing JT assemblies . . . . . . . . . . . 4-64Structure Manager Guide . . . . . . . . . . 3-78Structures, cloning . . . . . . . . . . . . . . . 2-43Summary tab . . . . . . . . . . . . . . . . . . . 3-13Summary task in Schedule Manager . . . 3-23Sun SolarisEthernet MAC addresses . . . . . . . . . 4-57Release notes . . . . . . . . . . . . . . . . . . 4-57

Sun Solaris 64-bit . . . . . . . . . . . . . . . . 3-73Support announcements . . . . . . . . . . . . 1-5SUSE LinuxEnterprise Server (SLES) . . . . . . . . . . 1-5Release notes . . . . . . . . . . . . . . . . . . 4-61

SVG Viewer plug-in . . . . . . . . . . . . . . . 1-22Symbolic links . . . . . . . . . . . . . . . . . . 4-69System administration release notes . . . 4-31

T

TC_LOCALIZATION_DIR . . . . . . . . . . 3-83TC_NX_Foreign_Datasetspreference . . . . . . . . . . . . . . . . . 3-68, 3-71TC_remote_checkin_relation_send_as_replicapreference . . . . . . . . . . . . . . . . . . . . . 4-27TC_ugmaster_name_separatorpreference . . . . . . . . . . . . . . . . . 3-68, 3-72TCM Release Status template . . . . . . . 3-84TcXml import . . . . . . . . . . . . . . . . . . . 3-30TeamcenterDistribution in ZIP files . . . . . . . . . . . 2-6Help . . . . . . . . . . . . . . . . . . . . . . . . 4-68Services . . . . . . . . . . . . . . . . . . . . . 1-11

Teamcenter BOM . . . . . . . . . . . . . . . . . 3-8Teamcenter EDACannot revise CCA . . . . . . . . . . . . . . 3-27Cannot revise design . . . . . . . . . . . . 3-27CopyAsReference deep copy rule . . . . 3-28Mentor Board Station . . . . . . . . . . . . 4-49Release notes . . . . . . . . . . . . . . 3-27, 4-49Solaris 10 . . . . . . . . . . . . . . . . . . . . 4-49UNIX . . . . . . . . . . . . . . . . . . . . . . . 4-49

Teamcenter EMC Content Storage MediaType . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Teamcenter Environment Manager . . . . . 3-1Teamcenter Environment ManagerHelp . . . . . . . . . . . . . . . . . . . . . . . . . 3-78Teamcenter File ServicesRelease notes . . . . . . . . . . . . . . . . . . 4-34Windows reboot . . . . . . . . . . . . . . . . . 4-3

Teamcenter Integration for NXBookmark error . . . . . . . . . . . . . . . . 4-40Connections . . . . . . . . . . . . . . . . . . . 4-37Default volumes value required . . . . . 4-41Download hyperlink not available . . . 4-38Harness . . . . . . . . . . . . . . . . . . . . . 4-37Harness structure . . . . . . . . . . 4-38–4-39Invalid item IDs . . . . . . . . . . . . . . . . 4-40NX 5 . . . . . . . . . . . . . . . . . . . . . . . . 4-39NX does not launch . . . . . . . . . . . . . 4-39Release notes . . . . . . . . . . . . . . . . . . 4-37UGMASTER fails . . . . . . . . . . . . . . . 4-40Wire, deleting . . . . . . . . . . . . . . . . . 4-38

Teamcenter perspectives . . . . . . . . . . . 2-28Teamcenter Publish . . . . . . . . . . . . . . 2-63Teamcenter Publish support . . . . . . . . . 3-14Teamcenter views . . . . . . . . . . . . . . . . 2-28Teamcenter’s Client for Microsoft OfficeDataset checkout . . . . . . . . . . . . . . . 3-16Lists of values (LOVs) . . . . . . . . . . . 3-16Office Live . . . . . . . . . . . . . . . . . . . . 3-15Outlook dataset . . . . . . . . . . . . . . . . 3-15


Index

Properties, synchronizing . . . . . . . . . 4-50Release notes . . . . . . . . . . . . . . . . . . 4-50Task panes . . . . . . . . . . . . . . . . . . . 3-15Typed values do not appear . . . . . . . . 3-15

Teamcenter’s Integration for Microsoft OfficeDatasets, attaching . . . . . . . . . . . . . 4-51Teamcenter’s Network Folders . . . . . 4-51Value/description pairs display . . . . . 4-61

Teamcenter’s lifecycle visualizationiSeries . . . . . . . . . . . . . . . . . . . . . . 4-63.mi file extension . . . . . . . . . . . . . . . 4-63Product views . . . . . . . . . . . . . . . . . 4-63Release notes . . . . . . . . . . . . . . . . . . 4-62.vvi file . . . . . . . . . . . . . . . . . . . . . . 4-62.vvx file . . . . . . . . . . . . . . . . . . . . . . 4-62

Teamcenter’s manufacturing processmanagement, see Manufacturing ProcessManagementTeamcenter’s mechatronics processmanagement, see Mechatronics ProcessManagementTeamcenter’s reporting and analyticsDatabase query . . . . . . . . . . . . . . . . 4-66Error does not appear . . . . . . . . . . . . 4-66IS NULL operator . . . . . . . . . . . . . . 4-65Mapper . . . . . . . . . . . . . . . . . . . . . . 4-66Release notes . . . . . . . . . . . . . . . . . . 4-65Saved query . . . . . . . . . . . . . . 4-65–4-66

Teamcenter’s simulation processmanagement . . . . . . . . . . . . . . . . . . . 2-57Technical help . . . . . . . . . . . . . . . . . . . . 1-3TEM enforces required Oracle version . . . 2-6Templates for document export . . . . . . . 2-22Temporary graphics artifacts . . . . . . . . 4-63Text file . . . . . . . . . . . . . . . . . . . . . . . 4-13Thin clientInitial value property rules . . . . . . . . 4-48Installation issue . . . . . . . . . . . . . . . . 4-1Macintosh . . . . . . . . . . . . . . . . . . . . 2-31Non-Western European languages . . . 4-51NX export . . . . . . . . . . . . . . . . . . . . 4-48Release notes . . . . . . . . . . . . . . . . . . 4-48Structure Manager . . . . . . . . . . . . . . 4-48

Third-party productsApplications support information . . . . 1-2Compatibility . . . . . . . . . . . . . . . . . . 1-2Release notes . . . . . . . . . . . . . . . . . . 4-68Software certification . . . . . . . . . . . . . 2-7

Time management . . . . . . . . . . . . . . . 2-43Tomcat . . . . . . . . . . . . . . . . . . . . . . . . 4-33Tool tips in Content Management . . . . . 3-17Toolbars disabled in Lifecycle Viewer . . 3-19Tools menu in As-Built Manager . . . . . . 3-9

Trace link options . . . . . . . . . . . . . . . . 3-21TraceLink class deprecation . . . . . . . . . . 1-6Transient_Volume_RootDirpreference . . . . . . . . . . . . . . . . . . . . . 4-35Translate, data set . . . . . . . . . . . . . . . 2-18TranslationRequest priority . . . . . . . . . . . . . . . . 1-22Service . . . . . . . . . . . . . . . . . . . . . . 2-18

TSTK . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Two-tier mode . . . . . . . . . . . . . . . . . . . . 4-2Two-way SSL . . . . . . . . . . . . . . . . . . . 2-26Typed values do not appear in Teamcenter’sClient for Microsoft Office . . . . . . . . . . 3-15TypesCustom . . . . . . . . . . . . . . . . . . . . . . . 4-9Orphaned . . . . . . . . . . . . . . . . . . . . . 4-4

U

UGALTREP files . . . . . . . . . . . . . . . . . 4-62UGGraphicsBuilder . . . . . . . . . . . . . . . 4-18UGMASTERDatasets . . . . . . . . . . . . . . . . . . . . . 4-64Fails . . . . . . . . . . . . . . . . . . . . . . . . 4-40

UGPARTDataset . . . . . . . . . . . . . . . . . . . . . . 3-12Files . . . . . . . . . . . . . . . . . . . . . . . . 4-62

ugtopv utility . . . . . . . . . . . . . . . . . . . 4-64ugxxtojt utility . . . . . . . . . . . . . . . . . . 4-64UNIX systemsGM Overlay . . . . . . . . . . . . . . . . . . . 4-53IDSM servers . . . . . . . . . . . . . . . . . 4-52Oracle 10g installationrequirements . . . . . . . . . . . . . . . 4-69

Properties dialog box . . . . . . . . . . . . 4-52Release notes . . . . . . . . . . . . . . . . . . 4-52

Upgrade Guide . . . . . . . . . . . . . . . . . . 3-78Upgrading . . . . . . . . . . . . . . . 4-4, 4-9, 4-11Database . . . . . . . . . . . . . . . . . . . . . 4-12GM Overlay . . . . . . . . . . . . . . . 4-29–4-30Missing database index . . . . . . . . . . 4-12Naming rules . . . . . . . . . . . . . . . . . . 4-30

Usability release notes . . . . . . . . . 3-8, 4-13Use temporary folders per session . . . . 4-60UserConstruct and access . . . . . . . . . . . . 4-32Exits . . . . . . . . . . . . . . . . . . . . . . . . 3-41

User access logging . . . . . . . . . . . . . . . 2-13user_auth_audit utility . . . . . . . . . . . . 2-13UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 3-10Utilitiesbmide_postupgradetotc . . . . . . . . . . . 4-30bomwriter . . . . . . . . . . . . . . . . . . . . 4-43


Index

data_share . . . . . . . . . . . . . . . . . . . 3-29data_sync . . . . . . . . . . . . . . . . 3-29, 4-43Deprecated . . . . . . . . . . . . . . . . . . . 1-10dsa_util . . . . . . . . . . . . . . . . . . . . . . 4-28ensure_site_consistency . . . . . . . . . . 4-26gmo_change_item_id_naming_rule . . 4-30import_dfa_file . . . . . . . . . . . . . . . . 1-10ldapsync . . . . . . . . . . . . . . . . . 4-31–4-32make_user . . . . . . . . . . . . . . . 4-31–4-32migrate_alias . . . . . . . . . . . . . . . . . . . 3-1nxmgr_add_note_types . . . . . . . . . . . 4-11Obsolete . . . . . . . . . . . . . . . . . . . . . 1-37preferences_manager . . . . . . . . . . . . . 3-3Release notes . . . . . . . . . . . . . . . . . . 4-43smlutility . . . . . . . . . . . . . . . . . . . . 4-44ugtopv . . . . . . . . . . . . . . . . . . . . . . 4-64ugxxtojt . . . . . . . . . . . . . . . . . . . . . 4-64user_auth_audit . . . . . . . . . . . . . . . 2-13

Utilities Reference . . . . . . . . . . . . . . . 3-80

VValidate task . . . . . . . . . . . . . . . . . . . 2-35ValidationReports . . . . . . . . . . . . . . . . . . . . . . 4-14Rules . . . . . . . . . . . . . . . . . . . . . . . 2-20

Value/description pairs display . . . . . . . 4-61Variant conditionErrors . . . . . . . . . . . . . . . . . . . . . . . 4-26On parts . . . . . . . . . . . . . . . . . . . . . 4-20

Variant expression block errors . . . . . . 4-26Vendor managementEnhancements . . . . . . . . . . . . . . . . . 2-27Export . . . . . . . . . . . . . . . . . . . . . . 4-28Import . . . . . . . . . . . . . . . . . . . . . . 4-28

View NX .prt file as 2D preference . . . . 4-64Viewer pane . . . . . . . . . . . . . . . . 4-13–4-14Viewers, Lifecycle Visualization and richclient . . . . . . . . . . . . . . . . . . . . . 3-6, 3-18Visible properties . . . . . . . . . . . . . . . . 2-11.vvi file . . . . . . . . . . . . . . . . . . . . . . . . 4-62.vvx file . . . . . . . . . . . . . . . . . . . . . . . 4-62

WWait For Undecided Reviewers . . . . . . . 2-35Web tier context parameters, obsolete . . 1-21WEB_use_activex_lov preference . . . . . 3-14

WebKey account . . . . . . . . . . . . . . . . . . 1-3WebLogicNoSuchMethodError exception . . . . . 4-24Version 9.1 . . . . . . . . . . . . . . . . . . . . 3-7WebDAV . . . . . . . . . . . . . . . . . . . . . 4-60

WebSEAL proxy support . . . . . . . . . . . 2-25WebSEAL proxy Support . . . . . . . . . . . 2-24WindowsChinese characters . . . . . . . . . . . . . . 4-59Power saving option error . . . . . . . . . 4-70Release notes . . . . . . . . . . . . . . . . . . 4-59Repaint problems on rich client . . . . . 4-65

Windows 2003 Server, unable to access files inTC_TMP_DIR . . . . . . . . . . . . . . . . . . 4-60Windows Vista . . . . . . . . . . . . . . . . . . 3-11.vvi file . . . . . . . . . . . . . . . . . . . . . . 4-62.vvx file . . . . . . . . . . . . . . . . . . . . . . 4-62

Wire, deleting . . . . . . . . . . . . . . . . . . . 4-38Workflowadhoc-signoffs handler . . . . . . . . . . . 2-33auto-assign handler . . . . . . . . . . . . . 2-33auto-assign-rest handler . . . . . . . . . . 2-33Condition task . . . . . . . . . . . . . . . . . 2-35CR-assign-team-selector handler . . . . 2-33CR-fill-in-reviewers handler . . . . . . . 2-33CR-notify handler . . . . . . . . . . . . . . 2-33EPM-check-object-propertieshandler . . . . . . . . . . . . . . . . . . . 2-33

EPM-check-related-objects handler . . 2-33EPM-create-sub-process handler . . . . 2-33EPM-set-task-result-to-propertyhandler . . . . . . . . . . . . . . . . . . . 2-35

Fail action . . . . . . . . . . . . . . . . . . . . 2-35Failure paths . . . . . . . . . . . . . . . . . . 2-35Handlers . . . . . . . . . . . . . . . . . . . . . 2-33Participants . . . . . . . . . . . . . . . . . . . 2-33Validate task . . . . . . . . . . . . . . . . . . 2-35Wait For Undecided Reviewers . . . . . 2-35Workflow Designer Guide . . . . . . . . . . 3-84Workflow operations . . . . . . . . . . . . . . 2-62Workflow signoff task . . . . . . . . . . . . . 3-13WSDL support . . . . . . . . . . . . . . . . . . 2-63

Z

ZIP files . . . . . . . . . . . . . . . . . . . . . . . 4-34
