Teamceniter 9.1 Release Bulletin Publication Number ‘PLM00001 I (01-087184-090)Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management Software Inc. © 2012 Siemens Product Lifecycle Management Software Inc. All Rights Reserved. ‘Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter is a trademark or registered trademark of Siemens Product Lifecycle Management Software Ine. or its subsidiaries in the United States and in other countries All other trademarks, registered trademarks, or service marks belong to their respective holders. 2 Teamconter 94 Releage Sullein PLwp0001 1(01-037134-080)Contents Propeietary and restricted rights notice .... Before you begin .......5 1a Installing or upgrading Teamcenter 1 ‘Teameenter and compatible third-party software versions 13 Global Technical Access Center (GTAC) 14 Available Teameenter 9.1 platforms 15 Hardware, software, and disk space requirements 16 LT Using documentation : Support and certification announcements . .. re | Deprecated feature announcements 21 Obsolete feature announcements oar What’snew oe. eeece eee eeeee ene ee ene fevee eee eeee Bal New Teamcenter applications and solutions 34 New, revised, and obsoleted Teamcenter documentation 32 New Teamcenter 9.1 Help Library 36 Installing Teameenter BT Configuring Teameenter 3-16 Administering Teamcenter 3-19 Using Teameenter interfaces 332 ‘Managing changes and workflows 341 ‘Managing content, reports, and schedules 342, Systems Engineering 348 Sharing data 3-65 ‘Managing product structures and collaborative product development 3-69 ‘Managing manufacturing data 3-75 ‘Managing Mechatronics data 3-88 Visualizing products 3-88 Managing CAE data 3-95 Repeatable Digital Validation 3-97 Managing quality data 3.98 ‘Managing maintenance, repair, and overhaul 3-100 Customizing Teamcenter ‘Teamcenter industry solutions Product Master Management Release notes 6... s6se sees eee ‘Teameenter 9.1 product release notes ‘Teamcenter 9, 1 documentation release notes 4-19. Index .... PLwp0001 1(01-037134-080) Teamcenter 91 Release Bulletin 3Chapter 1 Before you begin Installing or upgrading Teameenter 1 ‘Teameenter and compatible third-party software versions 13 Global Technical Access Center (GTAC) 14 Available Teameenter 9.1 platforms 165 Hardware, software, and disk space requirements 16 Using documentation ut Using PDF files Lt Using HTML files 18 PLwp0001 1(01-037134-080) Teamcenter 91 Release BulletinChapter 1 Before you begin This release bulletin contains the following information: * Support and certification announcements Important announcements about the release, including a list of deprecated and obsolete features For more information, see Support and certification announcements, © What's new announcements Descriptions of new features. For more information, see What's new. * Release notes Workarounds for known problems. For more information, see Release notes. Installing or upgrading Teamcenter This bulletin contains information usefull for customers who are installing or upgrading Teameenter, * Ifyou are Installing Teamcenter for the first time, see the following © Brief articles describing new installation features For more information, see What's new. © Release notes describing workarounds for known installation problems For more information, see Installation and upgrade release notes. Also see the Installation on UNIX and Linux Servers Guide or Installation on Windows Servers Guide PLwp0001 1(01-037134-080) Teamcenter 9.1 Release Bulletin 4-4Chapter 1 Before you begin * Ifyou are upgrading from Engineering Process Management or an earlier version of Teamcenter, see the following © Announcements of the deprecation or obsoletion of Teameenter features, For more information, see Support and certification announcements, Caution ‘The deprecation or obsoletion of features such as preferences can impact your upgrade. Before upgrading, take steps to accommodate the removal of these features © Release notes describing workarounds for known upgrade problems For more information, see Installation and upgrade release notes. Also see the Upgrade Guide For more information about installing or upgrading Teameenter, see the following * Installation of Teameenter patches and maintenance packs and patch installation information is documented in Installing Teamcenter patches in the Installation on UNIX and Linux Servers Guide and the Installation on Windows ‘Servers Guide * For general guidelines and best practices for a Teamcenter system administrator to follow when deploying a new or upgrading an existing Teamcenter system, see the latest available version of the Teamcenter Deployment Guide, To obtain a copy, go to the following Web site ‘http://support industrysoftware, automation, siemens comvdocs/teamcenter/ Note ‘You must have a WebKey account to access the Web site 4:2. Teamoonter 91 Reteage Bullen PLwp0001 1(01-037134-080)Before you begin Teamcenter and compatible third-party software versions The Siemens PLM Software Certification Database (http://support.industrysoftware. automation. siemens com/certification/teamcenter shtml) documents the minimum version of operating systems, compilers, databases, client browsers, and other third-party software with which this product is compatible. Because Teamcenter releases are asynchronous with the release of compatible third-party software, Teamcenter customers can acquire and install a newer version of third-party software before Siemens PLM ‘Software has the opportunity to certify it Siemens PLM Software's standard policy with respect to new versions of operating systems, compilers, databases, client browsers, and other third-party software relies on the manufacturers guarantees, If the manufacturer guarantees that the new version of its product is binary-compatible with the preceding version, Siemens PLM Software expects our products to function properly when running on the new version, Our experience shows that virtually no problems are encountered when executing Teamcenter with a third-party version later than the version on which we completed our certification testing, Siemens PLM Software will make a reasonable effort to support Teameenter running ona later version and to work with you to resolve any difficulty that may arise but, will not, in most cases, complete the testing required to state Teamcenter software is certified, ‘Teamcenter compatibility with operating systems and compilers involves these two considerations: * Compatibility for run time * Compatibility for relinking customizations and paths ‘Typically, operating system manufacturers assure run time binary compatibility between the successive versions of their operating systems We make a reasonable effort to support Teamcenter running on a later version of an operating system. To a lesser degree, operating system manufacturers provide similar assurances when relinking or rebuilding executables and libraries with new versions of the compilers. In cases where compatibility does not exist between old and new compiler versions, all customization incorporated into the Teamcenter base product must be linked using the version of the compiler with which Teamcenter has been released. This also applies to the installation of Teamcenter patches ‘To summarize, Teameenter may run on a newer version of an operating system, but customizations and patches may need to be compiled and linked on an earlier version. For information about the lowest version of software with which this product runs, see the certifications on GTAC, Although Teameenter may run using a lower level of software, keep in mind that we strongly discourage running at lower levels and that we do not provide support to anyone doing so, Note If Siemens PLM Software discovers incompatible versions of third-party software, we will post bulletins on GTAC. This information is also available from your Teameenter provider. PLwp0001 1(01-037134-080) Teamcenter 9.1 Release Bulletin 4-3Chapter 1 Before you begin Global Technical Access Center (GTAC) GTAC is the vehicle for Teamventer communication, It provides a single repository of current, accurate, version-controlled Teamcenter information that is accessible through the Internet by authorized users Maintained within GTAC is a wealth of information for the diverse mix of customers and employees in the Teamcenter community, Information in GTAC includes, but is not limited to, the following: © Certification announcements and bulletins * Frequently asked questions * Product defect reports * Enhancement requests * Patches and technical documentation * Shareware customizations © Tips pertaining to Teamcenter customization, performance, and administration * Product information, customer success stories, and user conference presentations GTAC can be accessed from the Siemens PLM Software Web site or directly through its Web server at the following Web site: ‘http://support industrysoftware. automation. siemens.com ‘You must have a WebKey account to access GTAC. A customer WebKey account is a single point of authentication that allows customers ta access product information and associated support tools. WebKey accounts are strictly limited to Siemens PLM Software employees and to people or companies who belong to the Teamcenter community through contractual agreements with Siemens PLM Software pertaining to Teameenter. Requests for access to GTAC using a WebKey account can be directed to the following Web site ‘https://plmapps.industrysoftware automation siemens com/webkey/ 4-4 Teamconter 91 Reteage Sullein PLwp0001 1(01-037134-080)Before you begin Available Teamcenter 9.1 platforms ‘The following distribution images are available as part of Teamcenter 9.1: ‘Teamcenter 9.1 for HP-UX Itanium ‘Teamcenter 9.1 for IBM AIX ‘Teamcenter 9.1 for Sun Solaris Spare ‘Teamcenter 9.1 for Microsoft Windows ‘Teamcenter 9.1 for Linux 64 ‘Teamcenter 9.1 for Over-the-Web installation, All Platforms ‘Teamcenter 9.1 Embedded Visualization, All Platforms ‘Teameenter 9.1 Publications, All Platforms ‘Teameenter 9.1 is translated into the following language locales on all server-supported platforms Chinese (Simplified) Chinese (Traditional) Czech English French German Hebrew Italian Japanese Worean Polish Portuguese (Brazilian) Russian Spanish PLwp0001 1(01-037134-080) Teamcenter 0.1 Release Bulletin 1-5Chapter 1 Before you begin Hardware, software, and disk space requirements For information about system hardware and software requirements for Teameenter 9.1, see the Siemens PLM Software Certification Database http//support industry software.automation siemens com/certification/teamcenter shtm! ‘The following table shows the required disk space for the platforms certified by ‘Teameenter, Required hard disk space for Teamcenter configurations Corporate Two-tier Platform server tich client Web tier Hewlett-Packard HP-UX! 3.0 GB ‘Not supported 3GB IBM AIX 20GB 450 MB 3GB SUSE Linux 20GB 300 MB 3GB Red Hat Linux 20GB 300 MB 3GB Sun Solaris 25GB Not supported 3GB Microsoft Windows 15GB 450 MB 45GB ‘TWaiua potions only: PA-RISC hardware is uct supported +6 ‘Teamconter 91 Release Bulletin PLwp0001 1(01-037134-080)Before you begin Using documentation ‘Teamcenter documentation is delivered in PDF and HTML format. Using PDF files ‘The PDF directory on the documentation distribution media contains Adobe PDF versions of the Teamcenter online help, From this directory, open the index.htm file ina Web browser to view the Teamcenter PDF Help Collection. You can view, search, and print individual guides or selected pages from within your Web browser. Viewing PDF files requires Adobe Reader, which you can download free from Adobe at http:/wwwadobe.com, Viewing PDF files in a Web browser requires the appropriate Adobe Reader plug-in for your Web browser Ifyou want to open PDF files directly, browse to the following directory on the documentation distribution media: Windows or Macintosh systems PDF\index.htm UNIX or Linux systems: PDF/index.htm Ifyou want to share the PDF collection on your network, copy the top-level PDF directory from the documentation distribution media to a network location and set file permissions as necessary to allow viewing Make sure you copy the complete contents of the PDF directory to ensure the collection and search features are available Searching the PDF help collection ‘To search the entire PDF collection, click Search collection using Adobe Reader in the Teameenter PDF Help Collection page. This opens the search index for the collection in Adobe Reader. In the Search dialog box in Adobe Reader, type the text you want to find. ‘The Search collection using Adobe Reader option is available only on a local host or over a network file system. If you share the Teamcenter PDF Help Collection on a Web (HTTP) server, you cannot search the entire PDF collection, For collection search capability, open the PDF collection in a Web browser from a Jocal host or file system, using a URL with file protocol, for example © Local host: filev//D:Wfpdt/index.htm. * Network host (UNC path} file:iM/host-namefpatiindex.htm. Ifyour Web browser is not configured to open Adobe Acrobat catalog index (,pdx) files, the browser may prompt you to choose an application to open the file. If this occurs, select Adobe Acrobat Reader to open the index. PLwp0001 1(01-037134-080) Teamcenter 0.1 Release Bulletin 4-7Chapter 1 Before you begin ‘To open the PDF collection search directly, open the PDF index file, tehelp.pdx, in the directory that contains the PDF files Note If you encounter errors opening the PDF collection search, you may need to upgrade Adobe Reader or your Web browser. Using HTML files Documentation in HTML format is installed when you select the Online Help option in the Features panel in Teamcenter Environment Manager (TEM) ‘The Teamcenter online help requires a Web browser that supports Java for the search to work. The browser version and Java specification required for online help depends on the operating system you are using, For information about certified browsers and Java versions for your operating system, see the Siemens PLM Software Certification Database ‘http://support industrysoftware, automation, siemens comvcertification/teameenter shtml Note © Some features of the online help system require the display of popup windows, for example, viewing footnotes. Ifa popup blocker utility is installed on the Web server or client workstation, you must configure the utility to allow popup windows from the online help domain. Otherwise, the online help system does not function correctly. © Ifyou want to view the Teamcenter online help brary in HTML format, expand the tehelp,jar file from the Teamcenter documentation distribution image to a local directory. To display the online help library index page, open the index.html file in the help directory. Additional online help features, such as Teameenter developer references, can also be installed. For more information, see Installing Teamecenter online help in the appropriate server installation guide (for Windows or UNIX/Linux) 448 Teamconter 91 Release Bulletin PLwp0001 1(01-037134-080)Chapter PLwp0001 1(01-037134-080) Support and certification announcements Deprecated feature announcements General deprecated feature announcements Deprecated utilities Deprecated ITK functions Deprecated services Deprecated Java classes Deprecated Global Services features Deprecated data model Deprecated Systems Engineering data model Deprecated Schedule Manager data model Deprecated Content Management data model Deprecated Workflow handlers Obsolete feature announcements General obsolete feature announcements Obsolete utilities Obsolete preferences and environment variables Obsolete ITK functions Obsolete data model Obsolete Workflow data model Obsolete Workflow handlers qT 17 OT -30 36 38 38 38 Teamcenter 9.1 Release BulletinChapter Support and certification announcements Certification announcements include notices about recommended use of this version, as well as announcements of the deprecation or obsolescence of features Deprecated feature announcements As Siemens PLM Software enhances Teamcenter, some features are deprecated or obsoleted. Deprecation identifies items that will be removed in a future version of Teamcenter. ‘The following features will be no longer certified or supported in a future version of Teamcenter. General deprecated feature announcements ‘The following features are deprecated in Teamcenter 9.1 * My Teameenter (2007) is deprecated (First published Teameenter 8 ) ‘The My Teameenter (2007) application in the rich client will be removed in ‘Teameenter 10 Siemens PLM Software recommends that deployments using My Teamcenter (2007) migrate any custom functionality to the My Teameenter application. ‘The My Teamcenter (2007) application continues to be available in Teamcenter 91 ‘My Teameenter (2007) is enabled by removing the My Teamcenter (2007) value from the HiddenP erspectives preference. For more information about the My Teamcenter (2007) application, see the My Teamcenter Guide PLwp0001 1(01-037134-080) Teamcenter 9.1 Release Bulletin 24Chapter2 Support and certification announcements * Integration for Adobe Ilusteator is deprecated (First published Teameenter 9.1) Due to fundamental changes in Teamcenter architecture, and planned alternate use cases for this functionality in industry templates, Siemens PLM Software will not support the Adobe Illustrator integration. Beginning with Teamcenter 10, support for this integration is obsolete. As of this notice, Siemens PLM. Software recommends that no new usage of this application should begin and users should transition away from its usage. * Audit Manager file storage mode is deprecated (First published Teameenter 9.1) File storage mode in Audit Manager is deprecated and will be removed in ‘Teamcenter 11. Siemens PLM Software recommends that new deployments using Audit Manager persist audit history in the database only. File storage mode will continue to be available in Teameenter 10. Audit Manager file storage mode is enabled when the TC_audit_manager preference is set to ON and an audit definition is set to select File for Storage Type For more information about storage type, see the Audit Manager Guide. * Legacy workflow, user administration, and CICO (checkin or checkout) audit files are deprecated (First published Teamcenter 8.1) Legacy workflow, user administration, and checkout audit files are deprecated and will be removed in Teameenter 11, Siemens PLM Software recommends new customers migrate to Audit Manager using audit definitions that specify Database for Storage Type. Legacy audit file storage mode is the logging enabled when the ‘TC_audit_manager preference is set to OFF, If the TC_audit_manager preference is set to OFF, several Teamcenter features append entries to legacy audit files in a Teamcenter volume: Checkin or checkout (CICO) Workflow ‘User administration Others ‘The strategic Teamcenter direction for event auditing is the comprehensive and configurable Audit Manager. The audit files identified in our documentation as legacy audit files are inconsistent with that strategy are not being enhanced and are less efficient in performance and resource consumption, Each will be removed in a future Teameenter version. Siemens PLM Software recommends that customers configure Audit Manager to record these events during this transition period For more information about storage type, see the Audit Manager Guide. 22 Teameonter@ 4 Release Suletin PLwp0001 1(01-037134-080)‘Support and certification announcements * NC Package Browser is deprecated (First published Teameenter 9.1) ‘The NC Package Browser is deprecated. If you need a solution for connecting between Teameenter and MCIS DNC, Siemens PLM Software recommends using Shop Floor Connect, For more information, contact your Siemens PLM Software representative, * Deprecation of Cold Backup and Hot Backup utilities (First published Teameenter 9.0) ‘The Cold Backup and Restore utility performs integrated cold backup and restore operations on the Microsoft SQL Server database and Teameenter volumes. ‘The Hot Backup and Recovery utility performs integrated hot backup and recovery operations on the Microsoft SQL Server database and Teamcenter volumes One shortfall of these utilities is that the restore operation is not a targeted operation, When restoring databases and volumes, all objects are rolled back to a point in time, potentially removing a significant amount of valid data simply to repair what could be a small problem, Also, these utilities assume all volumes are accessible directly from the machine on which the backup is executed (the database server) and that there is space to take copies of all volume files. ‘These utilities (Cold Backup and Restore, Hot Backup and Recovery) will be removed in a future version of Teameenter. Only the wrapper functionality will be removed from Teameenter, The underlying command line utilities for both utilities will remain, ‘Siemens PLM Software recommends that customers migrate away from the Cold Backup and Restore utility and the Hot Backup and Recovery utility and use more robust and fiexible procedures with third-party backup and restore tools, + RDVUseNewVariantModel global constant is deprecated (First published Teameenter 8.2) ‘The RDVUseNewVariantModel global constant is deprecated and will be obsolete in Teameenter 9.1 In Teameenter §.2 and later installations, the RDVUseNewVariantModel global constant should be set to true PLwp0001 1(01-037134-080) Teamcenter 0.1 Release Bulletin 23Chapter 2 ‘Support and certification announcements Deprecation of certification for Teamcenter Network Folders (First published Teamcenter §.3) Due to fundamental changes in the way Microsoft Windows 7 implements specific functions required for Network Folders functionality, and the existence of alternate use cases for the Network Folders functionality, Siemens PLM Software does not support Network Folders on the Windows 7 platform, Beginning with ‘Teamcenter 10, support for Teamcenter Network Folders is obsolete on all Windows platforms. As of this notice, Siemens PLM Software recommends that no new usage of this application should begin and users should transition away from the usage of Network Folders, Network Folders functionality is already available by other existing Teameenter functionality. Deprecation of the te.h header file (First published Teamcenter 8.1) In Teameenter 8.1, the teh file is deprecated and will be removed in Teamcenter 10. This include file is being split into two include files, Code that calls one or more of the following methods should be changed from #inelude to #include : ITK_init_feom_epp ITK_initialize_te ITK init_module ITK_auto_login Code that does not call one of these methods should be changed from #inelude to #include . Deprecation of global variables defined in appe.h (First published Teameenter § MP1) ‘The external global variables defined in the appeih file are deprecated, and replacement getter methods will be provided in Teamcenter 8.1. All the customizations that require these variables must use the replacement getter functions. ‘The apprih file defines external global variables such as the APPR_attr_op_like variable, This causes the dependency of the libappe module with other modules that use these external variables These external variables should be removed. 24 Teameonter@ 1 Release Suletin PLwp0001 1(01-037134-080)‘Support and certification announcements * Deprecation of Change Viewer (First published Teameenter § MP1) ‘The Change Viewer application is deprecated and will be removed from ‘Teameenter 10. Change Viewer is renamed Change Viewer Classic and a new Change Manager application is added. If you are new to Teamcenter or have not previously used Change Viewer Classic, use the new Change Manager application, Ifyou use Change Viewer Classic, you have options to migrate your change processes to Change Manager For more information about migrating to Change Manager, see Migrating to Change Manager in the Change Manager Guide Also, if you previously used Change Viewer Classic and need to continue to use it in the short term, two preferences are available to enable Change Viewer Classic functionality: Enable_Create_Classic_Change Enable_Show_Classic_Change ‘To access preferences in the rich client, choose EditOptions—Index For more information about these preferences, see the Preferences and. Environment Variables Reference and Change Manager preferences in the Change Manager Guide Incremental change is unaffected with the following exceptions: © Double-clicking an incremental change in My Teamcenter does not open it in Change Viewer Classic, The Summary pane is displayed instead. 0 The Send To-CM Viewer shortcut menu command is not available. © Set the incremental change effectivity in Structure Manager instead of Change Viewer Classic. © Initiate workflows in the application where you are accessing your incremental change instead of Change Viewer Classic PLwp0001 1(01-037134-080) Teamcenter 0.1 Release Buletin 25Chapter2 Support and certification announcements ‘The deprecation of Change Viewer Classic is accompanied by the deprecation of the following business objects Deprecated Workfiow templates Checklist Task: Impact Analysis Prepare ECO CMII Change Notice CMII Change Request MII WA Deprecated queries CM - BOM Changes CM - Change Forms CM - Change Progress CMII CN Type CMI CR Ty} Change Revision Deprecated reports: Classic CM - BOM Changes Classic CM Change Forms Classic CM Change Progress ECO Details Report ECO Signoff Details Handlers for Change Viewer Classic are also deprecated. For information about these related deprecations, see Deprecated Workflow handlers, * Support for running Teamcenter on Hewlett-Packard HP-UX is deprecated (First published Teameenter 9.1) Running Teameenter on the HP-UX operating system, including HP-UX on Itanium hardware, is deprecated and will be obsolete in a future version of ‘Teamcenter, This includes all Teamcenter clients and servers, Siemens PLM Software recommends migrating to another supported platform and operating system, For information about operating system versions certified with Teameenter 9.1, see the Siemens PLM Software certification database: ‘http://support industrysoftware, automation, siemens comycertification/teameenter shtml 26 Teamconter@ 1 Release Suletin PLwp0001 1(01-037134-080)‘Support and certification announcements * Deprecation of rich client on IBM AIX operating systems (First published Teameenter 2007.1) ‘The Teamcenter rich client is deprecated on IBM AIX systems: This applies only to the Teameenter rich client, The Teameenter thin client and ‘Teamcenter server-side components will continue to be certified on IBM AIX Demand has decreased for Teamcenter clients on UNIX-based operating systems, UNIX hardware vendors now concentrate on servers instead of desktops Siemens PLM Software recommends using either Windows-based or SUSE Linux-based systems for Teamcenter rich client, Certification for the rich client on AIX will be discontinued at Teamcenter 10. See the following site for specific operating system version certification: ‘http://support industrysoftware, automation, siemens comycertification/teameenter shtml * Deprecation of schematics in Steucture Manager (First published Teameenter 8) ‘The ability to view schematic diagrams in the Structure Manager viewer is deprecated, Replacement of this functionality is targeted in a future release based on an integration with Microsoft Visio and Teamcenter, PLwp0001 1(01-037134-080) Teamcenter 0.1 Release uletin 27Chapter2 Support and certification announcements Deprecated ut ‘Teameenter command line utilities are used by administrators to manage ‘Teameenter installations. For more information about utilities, see the Utilities Reference ‘The following utilities are deprecated in Teameenter 9.1 * Deprecation of the te_config_attr_mapping utility (First published Teameenter 9.1) ‘The te_config_attr_mapping utility is deprecated and is replaced by the bmide_manage_batch_lovs utility. * Deprecated Workflow utilities (First published Teamcenter §.3) The following utilities were deprecated in Teamcenter engineering process management 9,1 and are obsolete in Teameenter 8.3: © upgrade_workflow_objects There is no replacement utility. © upgrade_motif_workflow templates There is no replacement utility. © append_procedure Use the plmxml_import utility instead. 28 Teameonter@ 1 Release Suletin PLwp0001 1(01-037134-080)‘Support and certification announcements Deprecated ITK functions ‘The Integration Toolkit (IT) is a set of C functions provided by Siemens PLM Software that you can use to integrate third-party or user-developed applications with Teamcenter. For information about deprecated and obsolete ITKK functions and their replacement functions, see the Integration Toolkit Function Reference. Choose the Deprecated menu option on the top menu bar. * Deprecation of PIE_init_module (First published Teameenter 8.3i) ‘The PIE_init_module I'TK function is deprecated in Teamcenter 9 and will be removed at Teameenter 10, * Deprecation of askLOVLength0) (First published Teameenter 8.2) ‘The askLOVLength() ITK function is deprecated because it always executes a server call Use the getLOVSize() function IT instead, which is published and based on the rich client ListOfValuesinfo cache, Deprecated services ‘Teamcenter Services are a collection of Teamcenter operations used by system administrators to connect their company’s applications to Teamcenter. For the list of deprecated services, see the Services Reference in the Teamcenter HTML Collection. Choose the Deprecated menu command on the top menu bar of each set of API documentation, Deprecated Java classes Java classes are used to compose the rich client, and are documented in Javadoc found on the Teameenter installation media. For the list of deprecated Java classes, see the Javadoe. Choose the Deprecated menu command on the top menu bar of each set of Javadoc. * Deprecation of the unpublished TCDnDAdapter.java class (First published Teameenter 8.2) ‘The unpublished TCDnDAdapter.java Java class will be removed in a future version of Teameenter * Deprecation of the unpublished NevalEViewer,java class (First published Teameenter 9.1) ‘The unpublished NevalEViewer,java Java class will be removed in a future version of Teameenter. NevalEViewer,java is a Swing-based Java class presented in various applications in the rich client that embeds Microsoft Office documents into the rich client for viewing and editing NevalEViewer,java is replaced by a SWT-based counterpart PLwp0001 1(01-037134-080) Teamcenter 9.1 Release Sulletin 29Chapter2 Support and certification announcements Deprecated Global Services features ‘The following Global Services features are deprecated. * Deprecation of the GS2GS Connector (First published Teamcenter §.3) The GS2GS connector is deprecated. The BPEL process partner links functionality of Global Services provides the same functionality as the GS2GS connector, Use the bundled ODE BPEL engine to accomplish the same functionality as the GS2GS connector * Deprecation of the Global Services Framework - Web Services Connector (First published Teameenter 8.2) ‘The Teameenter Global Services Framework — Web Services Connector is deprecated. This connector’s functionality is replaced by the BPEL process partner links functionality of Global Services. ‘The Web Services Connector will be obsolete at Teameenter 10 + Deprecation of the Global Services Connector (First published Teamcenter 8.1) ‘The Teamcenter 8,1 Global Services — Global Services Connector is deprecated. ‘This connector will be removed in a future version of Global Services, This comnector’s functionality is replaced by partner links provided through the Teamcenter 8.1 Global Services Framework - Ode BPEL web application solution. * Deprecation of the Global Services BPEL engine endpoint (First published Teameenter 8.1) ‘The BPEL 1.1 engine Global Services supplies is deprecated will be removed at a future version, This functionality is replaced by the ODE BPEL 2.2 engine supplied through the Teamcenter 8.1 Global Services Framework - Ode BPEL web application solution. As a result, the following Global Services invocation endpoint is also deprecated beep: //host: port/tegs-context-root /controller/invoke The new endpoint is beep: //host: port/tegs-context-root/processes/process ‘Your clients must call this new endpoint in a future version. For the deprecation period, the old endpoint forwards appropriately to the new endpoint ‘There are two significant changes for calling the new endpoint: 1. The URL must contain the process binding name 2 A simple object access protocol (SOAP) header must contain the security credentials ‘The following is an example of an existing data-teansfer call to Data Exchange: beep: //localhost:7001/tegs /controller/index 240. Thamcenter @1 Reloage Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements With the following SOAP message soapene:Envelope mins: seapenv=-netp://achenas xml soap org/ seap/ envely “Snine ssdWtncep./ ewww 22g) 2001/ Mr Schema ERIN Ss iSheep:// umes wd on g/ 200L/AML Schema’ snstance"> ea Be saacenguentpmineerncy://eyancgntes con ghobalegevice/ pea ‘euino sfer="hteep //teamcenver com gl obalservices/ eranster/ £007°0E' chine sting tbat die sents ere re te ee eek genie ‘Sefed! Last oh jeceMandl ec/xtex: a> slate Shgeceninee? Schall sone sadzess; sonevoehes~addcessc/ ematl> Seeanster"formais/3 SSMERAT Season aaa sronnene Sey amtneweneeehttp/[40eg ongeepen. ns/vee/2004/03/ SETTERS Shiny eeerne tn: //4oce,gente-open. xs/nas/2004/08/ Onshs yeu Td="Usernametoxen: 226336605 cit iemapniumcmemee SbBepltgdghaasacsenOcsadcefecee Pacteese TE SEE Se grid See apes orszon en ettsee SS Tp eaaetva hae rer secede etter ee a ee tbe ar reaecee ante dgeez>heep'/ anew WS 049/2008/8bJadduenesng/none SOEMEEEE ase spss omen. cpleeoee(neeig> legate ‘Vaaeareransfer-zequest smins=*hevp: //veancentez.con/ glebal sezvices/ process/ 2007-06" ooSofaeciceiees laren oumeser con ebelacey raat Sueseee ties =fib1838¢/manceessiee= 1a SEHCTESESIY sic a> Sgrowp"idsegeoupsl group tas queens nt eEet? sige i09S07¢/ xfer: aitenid> engi ;. IEEE SDAP Tbh gecemanat ec/xter: a> Schall SoneSaddress; vome-ovher~addzess Se SMCS hoaracockeaaies aS PLwp0001 1(01-037134-080) Teamcenter 0.1 Release Bulletin 2-14Chapter2 Support and certification announcements * Deprecation of the Global Services Teamcenter 2007 Rich Client Connector (First published Teamcenter 8) ‘The Teamcenter § Global Services — Teamcenter 2007 Rich Client Connector is deprecated, This connector will be removed in a future release of Global Services In most cases, you can use the Teameenter § Global Services — Teameenter 8 SOA connector in place of this connector. * Deprecation of the Global Services Teamcenter Engineering 2005/2007 Connector (First published Teamcenter 8) ‘The Teamcenter § Global Services - Teameenter Engineering 2005/2007 Connector is deprecated. This connector will be removed when Teamcenter Engineering 2007 is no longer supported, * Deprecation of the Global Services Teamcenter Engineering v9 Connector (First published Teameenter 8) ‘The Teamcenter § Global Services — Teamcenter Engineering v9 Connector is deprecated, This connector will be removed when Teamcenter Engineering V9 is no longer supported * Deprecation of the Global Services Teamcenter 8 Connector (First published Teameenter 8) The Teamcenter § Global Services — Teamcenter § Connector is deprecated. This connector will be removed in a future release of Global Services. * Deprecation of the Global Services SAP Connector (First published Teameenter 8) ‘The Teamcenter 8 Global Services - SAP Connector is deprecated, This connector will be removed in a future release of Global Services. 242. Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements Deprecated data model ‘The following data model items have been deprecated. You can view data model items using the Business Modeler IDE. For more information about data model, see the Business Modeler IDE Guide. Deprecated Systems Engineering data model ‘The following Systems Engineering data model is deprecated. * TeaceLink class is deprecated (First published Teameenter 8.2) ‘The TeaceLink class, as extended from the ManagedRelation class, is deprecated since Teamcenter 8.0, The class feature has been migrated to the new trace link FND_‘TraceLink class under the TCRelation class Also, 2 migration utility has been provided and all trace link instances will be migrated to new trace links during database upgrade. Deprecated Schedule Manager data model (First published Teamcenter 8.2) ‘The Schedule Manager data model includes some business objects and some business object properties that are no longer used. These are marked as deprecated and will be removed at a later date * Deprecated Schedule Manager business objects Deprecated business object Replacement business object ‘ScheduleDeliverable ‘TaskDeliverable ‘SchDeliverable SchTaskDeliverable * Deprecated Schedule Manager properties on business objects Business object Deprecated property Replacement property Schedule ‘act_date_preference None base_schedule_cost None dates linked None vights_mask None sch_deliverable_taglist schedule_deliverable_taglist ScheduleRevision act_date_preference None archive_notification_events None dates linked None vights_mask None ScheduleTask baseline_var_cost None ms_integration_link None PLwp0001 1(01-037134-080) task_deliverable_taglist sch_task_deliverable_taglist ‘Teamconter 9.1 Releage Sulltin 249Chapter 2 ‘Support and certification announcements Business object Deprecated property Replacement property TaskSchedulingFormInfo _ task_deliverable_taglist _sch_task_deliverable_taglist TCCalendar tecal_dese None TCCalendarEvent event_expiry_date None event_type None first_recur_end None num_recurrences None recur_days_of_week None vecur_interval None recur_month None recur_weeks_of_month None TimeSheetEntry time_category None Deprecated Content Management data model (Revised at Teamcenter 8.3) ‘The Content Management data model includes some business objects and some business object properties that are no longer used. These are marked as deprecated and will be removed as specified * Deprecated Content Management run-time properties on business objects ‘There is no migration planned for the following properties, they are simply not needed without the separate Content Management Web server. These properties will be removed at Teameenter 9.0 ‘The isFeozen, lockOwner and inLifeCy cle run-time properties are being deleted from all classes where they are currently used: DC_ComposedDocRevision DC_EstEntAdminRevision. DCt_ItemRevision DC_ProcedureRevision DC_PublicationRevision DC_ReviewerDocRevision DC_TopicRevision DC_UnparsedDocRevision (only for the isFrozen and inLifeCycle properties) 244 Teamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements * Deprecated Content Management properties on business objects ‘These properties have string names that will be deprecated and replaced by tag reference properties to other objects ‘These deprecated properties will be removed at a future release when they are no longer needed for upgrade purposes, Business object Deprecated property Replacement property DC_ComposedDocRevision topicReference ctm0PublicationTagref languageRef ctm0LanguageTagref DC_ProcTool gephePrioReference etm0GraphgicPriovity Tagret DC_PublicationRevision masterLanguageRef ctm0MasterLanguageTagref styleTypeRef ctm0StyleTypeTagref templateRef ctm0TemplateTagref topicTypeRef etm0TopicTypeTagref DC_ReviewerDocRevision _topicReference ctm0PublicationTagref languageRef ctm0LanguageTagret DC_TopicRevision masterLanguageRef ctm0MasterLanguageTagref templateRef ctm0TemplateTagref topicTypeRef emt0TopicTypeTagref DC_TeansfPolTbl tpProcedure ctm0ProcedureTagref tpStyleSheet None, Always use procedures tpToolName etm0ToolTagref DCt_GrapheTrnsitnRevision languageRef ctm0LanguageTagref DCtTranslationRevision _ languageRef ctm0LanguageTagref topicReference None, Not used. DCt_XmlAtteMapTbl xamProcedure ctm0ProcedureTagref GrphicOptRevision. languageRef Fnd0LanguageRef GraphicRevision masterLanguageRef Fnd0LanguageRef LanguagesTbl language Fnd0LanguageRef ‘TeanslationOrderRevision _topicReference Fnd0ItemRevTagref translOfficeReference Fnd0TenslOfficeTagref translResponsible Fnd0TensiRespblTagref ‘TeansltnOfficeRevision teanslResponsible Fnd0TensiRespblTagref styleTypeRef etm0StyleTypeTagref PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Releage Sulltin 248Chapter2 Support and certification announcements Deprecated Workflow handlers ‘The following Workflow handlers and tasks are deprecated. * check-process-completion (First published Teameenter 8.2) ‘The Syne task and related check-process-completion handler is deprecated and will be obsolete in Teamcenter 10. Obtain equivalent functionality by creating subprocesses from parent processes, For more information, see the Workflow Designer Guide * CONTMGMTnotify (First published Teameenter 9.1) ‘The CONTMGMT-notify handler is deprecated and will be obsolete in a future version of Teameenter. For more information, see the Workflow Designer Guide * Deprecated handlers for Change Viewer Classic (First published Teameenter 9.1) ‘The following action and rule handlers are deprecated due to the deprecation of Change Viewer Classic. Deprecated action handlers 0 ECM-add affected-irs-as-target o ECM-att-new-status-for-aff-revs o ECM-attach-components-to-change o ECM.-copy-end.item-effectivity 0 ECM-create-base-revrule-form o ECM-notify-competing-changes 0 ECM-set-base-reveule o ECM-start-new-sub-process Deprecated rule handlers: 0 ECM-check-target-is-ec o ECM.is-all-affected-irs-released o ECM.is-all-affected-irs-target 0 ECM-is-valid-ee-process For more information about the deprecation of Change Viewer Classic, see Deprecation of Change Viewer. 248 Thamconter @1 Releage Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements Obsolete feature announcements As Siemens PLM Software enhances Teamcenter, some features are deprecated or obsoleted. Obsolescence identifies items that are either removed from Teamcenter or may be removed without further notice, ‘The following features are no longer supported in Teamcenter. General obsolete feature announcements ‘The following features are obsolete in Teameenter 9.1 * Obsolete Content Management business objects ‘There is no migration planned for the following business objects; they are not needed without the separate Content Management Web server. These objects are obsolete at Teameenter 9.0. Deprecated business object Replacement business object DCt_CacheInd None DCt_CntntRevwitm None DCt_CntntRevwitmRevision. None DCt_CompPolicy None DCt_CompPolTbl None DCt_Permissions None DC_PublParamTbl None DCt_SearchCriteria None DCt_Workspace None * Report Designer is obsolete (First published Teameenter 9.1) ‘Support for Report Designer is discontinued in Teameenter 9.1, Customers are encouraged to use the Report Builder application to develop reports. For more information about Report Builder, see the Report Builder Guide * Headless application support is obsolete (First published Teameenter 8.2) Use of the rich client Java libraries (including the Java kernel APIs) is supported only for additions and extensions to the rich client itself Alternative clients, such as headless applications (whether they present a user interface or not), are supported only by the Teamcenter Services client libraries Allinstructions for performing headless customizations have been removed from the Client Customization Programmer's Guide For more information about Teameenter Services, see the Services Guide. PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 247Chapter 2 ‘Support and certification announcements Support for XML-based manufacturing reports is obsolete (First published Teameenter 8.3) Beginning with Teamcenter 9, manufacturing reports in the Manufacturing Process Planner application no longer support the option to use XML-based reports Only PLM XML-based reports are supported. PLM XML is currently the default schema; it can be overridden by modifying the emereport properties file as described in the Customizing reports topic of the Report Generator Guide. If you are using this setting and have created custom reports, you must migrate your custom style sheets to PLM XML Support for Visio 2003 in TePublish is obsolete (First published Teameenter 8.3) Beginning with Teamcenter 9, Teamcenter Publish no longer supports Microsoft Visio 2003. Visio 2007 and Visio 2010 (32-bit only) are certified. Support for Sun Java System Application Server is obsolete (First published Teameenter 8.3) In Teameenter 9, Sun Java System (which is being rebranded as Sun Glassfish) is no longer certified on any operating systems supported by Teamcenter. This termination of certification applies to both the Glassfish Server Open Source Edition and the commercially licensed Oracle Glassfish Server Additionally, the GTAC certification tables indicate that the Sun Java System is certified for ‘Teameenter 2007.x and Teameenter §.x. This certification, however, is limited to Microsoft Windows and Sun Solaris operating systems Other operating system platforms are not certified. Following are the certifications © For Teameenter 2007.1 and 2007.2, Sun Java Web Server 6.1 SPS is supported on Windows and Solaris. o For Teamcenter 8.x, Sun Java System Application Server 9, 1 is supported on Windows and Solaris Application Integration Environment (AIE) is obsolete (First published Teameenter 8.2) ‘The Application Integration Environment (AIE) is obsolete and is no longer supported in Teamcenter 9. Instead of ATE, the Teamcenter Services framework must be used for integrating applications with Teamcenter. For more information about the Teameenter Services framework, see the Services Guide. 248 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements * Support for Microsoft Office 2003 is obsolete (First published Teamcenter 8.1) ‘The following integration options for Teamcenter are no longer certified for Microsoft Office 2003 © Teameenter Client for Microsoft Office © Teameenter Extensions for Microsoft Office o Teameenter Compatibility ‘These integrations are certified for Microsoft Office 2007 and 2010. * Genius4000 to Resource Manager migration program is obsolete (First published Teameenter 8.1) ‘The Genius4000 to Resource Manager migration program is no longer delivered starting with Teamcenter 9, If you must migrate Genius4000 data from ‘Teamcenter 9 onwards, you must do so by installing Teamcenter 8.x (or earlier) and migrating the data using the Genius data migration utility found in that installation. Once the data is migrated, you can do one of the following © Upgrade the Teamcenter § database to the appropriate Teamcenter version, o Export the migrated data and import it into the appropriate Teamcenter version. * elntegrator Admin application is obsolete (First published Teameenter § MP1) ‘The eIntegrator Admin application (IM12860) is no longer provided in ‘Teameenter 9, Instead of elntegrator Admin, use the functionality in Global Services to perform live exchange and to map data with external databases, * Support for Hewlett-Packard HP-UX on PA-RISC hardware is obsolete (First published Teamcenter 2007.1) Running Teameenter on the HP-UX operating system on PA-RISC hardware is no longer supported. This includes all Teamcenter clients and servers. Hewlett-Packard has discontinued HP-UX on the PA-RISC hardware platform and is moving server implementations to the HP-UX Integrity platform based on the Intel Itanium? platform. More information about HP-UX PA-RISC deprecation is available on the Hewlett-Packard Web site ‘http:/fn7 1028. www hp.com/ERC/downloads/4AA0-5390ENW. pdf ‘The HP-UX Integrity platform is certified for Teamcenter servers. See the following site for specific operating system version certification and restrictions: ‘http//support.ugs comvcertification/teameenter shtml PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 243Chapter 2 ‘Support and certification announcements Support for rich client on Solaris is obsolete (First published Teameenter 2007.1) ‘The Teamcenter rich client is no longer supported on Sun Solaris operating systems ‘This applies only to the rich client, The Teameenter thin client and Teamcenter server-side components are still certified on Solaris Siemens PLM Software recommends using either Windows-based or SUSE Linux-based systems for Teamcenter rich client. See the following site for specific operating system version certification: ‘http//support.ugs comvcertification/teameenter shtml Application Interface Web Service (AIWS) is obsolete (First published Teamcenter 2007.1) ‘The Teamcenter Application Interface Web Service is obsolete, Use the AI Service provided as part of the Teamcenter service-oriented architecture (SOA) to develop new clients with the same application integration constructs. For more information about SOA, see the Services Guide Digital Dashboard plug-in to Business Modeler IDE is obsolete (First published Teamcenter 8.1) ‘The third-party component upon which the Business Modeler IDE Digital Dashboard plug-in is based is obsolete and is no longer available in a version compatible with the content of Teamcenter 8.1. Asa result, the plug-in has been. obsoleted and removed from the distribution Other log file analysis tools and scripts can be applied to log files either as written by the Teamcenter process or after collection by the Log Manager in the log volume. Siemens PLM Software intends to enhance log files to use industry standard formats in future versions of Teamcenter This enables the use of commercial and open source log file analysis tools Image Import utility is obsolete (First published Teamcenter 2007.15) ‘Support for the Image Import utility is obsolete in Teameenter §.1. The Image Import utility is located on the Teamcenter installation CD-ROM in the additional_applications folder JT assembly format for import and export is obsolete (First published Teamcenter 8) Export and import of a JT assembly format using PLM XML is obsolete and was removed after Teameenter 8.1. Instead, use the PLM XML format rather than the JT assembly format, This exports and imports JT files, along with the PLM. XML file containing the item information and assembly relationships 220 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements * Certification for SUSE Linux Enterprise Server (SLES) 9.0 is obsolete (First published Teamcenter 8) Certification for version 9,0 of SUSE Linux Enterprise Server (SLES) is discontinued at Teameenter 8,1. Teamcenter will certify only version 10 SP2 and later for both clients and servers starting with Teamcenter 8.1 For a listing of certified platforms for Teamcenter, see the certification table at the following URL: ‘http//support.ugs comvcertification/teameenter shtml * Certification for AIX 82-bit servers and clients is obsolete (First published Teamcenter 8) ‘Teameenter will certify only 64-bit servers and clients on the AIX operating system starting with Teameenter 8.1, For a listing of certified platforms for ‘Teamcenter, see the certification table at the following URL: ‘http//support.ugs comvcertification/teameenter shtml PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 224Chapter2 Support and certification announcements * The AutoCopyRel and AutoRevise business object constants are now obsolete (First published Teamcenter 8) In Teameenter 2007.1, the AutoCopyRel and AutoRevise business object constants were introduced to support the requirement to automatically revise and relate the related object during a Revise operation of an ItemRevision business object, These two constants are now obsolete. Beginning in Teamcenter 8, do not use the AutoCopyRel and AutoRevise business object constants. The functionality provided by these two business object constants are replaced by deep copy rules. In Teamcenter 8 the deep copy mules are enhanced to support this behavior using the Relate To Latest and Revise and Relate to Latest actions. Beep in mind the following upgrade considerations: © Upgrading from Engineering Process Management to Teamcenter 8 Ifyou are upgrading from Engineering Process Management to Teamcenter 8, you do not have to do anything, since these constants were available only in Teameenter 2007.1 © Upgrading from Teameenter 2007.1 to Teameenter 8 Ifyou are upgrading from Teamcenter 2007.1 to Teameenter 8, you may have constant attachments for the AutoCopyRel and AutoRevise business object constants, Per the new upgrade process, the customer template project, must first be upgraded in the Business Modeler IDE client before upgrading the database, During upgrade of the customer template project in the Business Modeler IDE client, migration utilities are written to automatically handle converting the AutoCopyRel and AutoRevise constants to deep copy rules, After upgrading the customer template project, the same template is packaged and supplied during database upgrade, The database upgrade process ensures that your AutoCopy Rel and AutoRevise business objects constants are correctly converted to deep copy rules, Therefore, the customer upgrading from Teamcenter 2007.1 to Teamcenter 8 does not have any other manual steps to perform, By following the standard Teamcenter upgrade process, the system ensures that your current behavior supported by the business objects continues to be supported by deep copy rules after upgrade of your template and database. For more information, see the Business Modeler IDE Guide. 222. Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements + Maturity_Level preferences are obsolete (First published Teamcenter 8) All preferences of the item-revision-business-objectMaturity_Level format (such as DesignRevision_Maturity_Level) are replaced by the Maturity Statuses business object constant, In Teameenter 2007.1, the item-revision-business-object Maturity_Level preference was introduced to configure maturity status for ItemRevision objects ‘This preference is obsolete in Teamcenter § and is replaced by the ‘Maturity Statuses business object constant ‘The capability to configure the determination of the maturity status of an ItemRevision object is supported through the Maturity Statuses business object constant in the Business Modeler IDE instead of the item-revision-business-object Maturity _Level preference. Beep in mind the following upgrade considerations: © Upgrading from Engineering Process Management to Teamcenter 8 No action is required because the item-revision-business-objectMaturity_Level preference was introduced only in Teameenter 2007.1 © Upgrading from Teameenter 2007.1 to Teameenter 8 Migration utilities are written to convert the item-revision-business-objectMaturity_Level preferences to Maturity Statuses business object constant attachments If you have preferences that use the item-revision-business-object Maturity_Level format, you must follow the steps to migrate these preferences as described in the Migrate preferences to data modet objects topic in the Business Modeler IDE Guide As part of the steps performed prior to the upgrade process, you would extract the preferences from your database and perform migration in the Business Modeler IDE using the Preferences Migration wizard. After the preference migration in the Business Modeler IDE, a file named cleanup_preferences.txt is generated. This file must be invoked from your custom upgrade script to remove the preferences from your database. For more information, see the Business Modeler IDE Guide. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 223Chapter2 Support and certification announcements * Data Integration Services (DIS) Adapter (First published Teameenter 8) ‘The Data Integration Services Adapter (DIS Adapter) has been completely removed from Teamcenter. Teamcenter's integration with the Lifecycle Visualization viewers is now based upon a service-oriented architecture (SOA). ‘This new integration is installed automatically with Teameenter and no additional steps are required to work with visualization data in the Teamcenter 8 managed environment, Lifecycle Visualization viewers from earlier releases are not supported by and cannot communicate with Teamcenter 8. However, the Teamcenter § stand-alone viewers can communicate with DIS-enabled servers from previous Teameenter releases. * Obsolete Web tier context parameters (First published Teameenter 8) ‘The following Web tier context parameters are obsolete in Teameenter 8 AdapterAdministeator EnableAutoSaveLocation FileUploadD irectory JtCache.BatchPopulate dtCache.BatchPopulateFirstTime dtCache.BatchPopulateIntervalHours dtCache.Limited.BackupIntervalMinutes JtCache.Limited.Capacity MB dtCache.Limited.CleanFirstTime dtCache.Limited.CleanIntervalHours dtCache.Limited.Enable dtCache.Limited.Path dtCache.Limited SisterStatusNameList dtCache.Limited SisterSynchInterval dtCache.Limited.StatusName JtCache.Populator.BackupIntervalMinutes dtCache.Populator.Path JtCache.Populator.QueueName dtCache.World.BackupIntervalMinutes dtCache.World.Capacity MB dtCache.World.CleanFirstTime dtCache.World.CleanIntervalHours dtCache.World.Enable dtCache.World.Path dJtCache.World.PopulatorUser dtCache.World.SisterStatusNameList dtCache.World.SisterSynchInterval dtCache.World.StatusName Mask.RefSetNames.ItemRev PasswordFile SessionPurgeFrequency SessionTimeout ‘TeEngExcludeFiles ‘TeEngExcludeFilesExtFcomSave 224 Teamconter @1 Releage Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements ‘TeEngExcludeObjectTypes ‘TeEngExcludeTypesFromSave ‘TcEngMetaDataStamp ‘TeEngProperties WVLDirectModel.Document WVLImageView.Document WLPDFViewDocument VL TempFolder WLVissDLayer WLVisView.Session WLVisView.SessionPackage * Obsolete live Excel export functionality (First published Teameenter 8) ‘Teamcenter Extensions for Microsoft Office does not generate a live Excel sheet for the Excel 2008 application, However, it continues to generate a static sheet for Excel 2003, Users should have Excel 2007 installed to use the live feature. * Certification for Teamcenter EMC Content Storage media type is obsolete (First published Teamcenter 2007) Certification for the EMC-based Content Storage media type is no longer included in Teameenter Backup and recovery functionality remains as a supported capability in Teamcenter but without certification for the EMC Content Storage media type. The following features are impacted: © Content Storage media type in the rich client © Content Storage media type usage in Backup/Revovery applications (object_backup and object_cecover utilities) © Content Storage type usage in audit logging o EMC Business Modeler user exits © Content Storage type integration code in the ar_content_storage_media_api.c and ar_content_storage_media.h files * Obsolete bookmark launch functionality for Lifecycle Visualization (First published Teamcenter Engineering 2005 SR1) ‘The legacy functionality that launches Lifecycle Visualization from the rich client and thin client using bookmarks is obsolete. This functionality is superseded by the functionality that launches Lifecycle Visualization using the VVI file, which is based on the PLM XML launch mechanism and Data Integration Services Adapter technology. The IMAN_show_open_in_pv_button preference that enables the functionality is also removed. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 225Chapter2 Support and certification announcements * Adobe will no longer certify Explorer (First published Teamcenter 2007.14) As of January 2009, Adobe will no longer certify or enhance its SVG Viewer plug-in for Internet Explorer Siemens PLM Software is planning to replace this technology in the thin client, but we recommend that you continue to use it to enable the visualization of workflow processes and supersedure part history. its SVG Viewer plug-in for Internet * Removal of Multiple View Editor (MVE) (First published Teamcenter 2007.1) ‘The Teamcenter Multiple View Editor is removed from Teameenter § due to the low customer base implementation and duplication of functionality in ‘Multi-Structure Manager * Users can no longer change a translation request priovity (First published Teameenter 2007.1) ‘Users can no longer change the priority of a submitted translation request in the translation administrator console, Administrators can change priorities as well as translation execution times in the translation administrator console, * Property rules are replaced by the property constants framework (First published 2007.1) Property rules are replaced with the property constants framework. Property constants data model elements support true inheritance of every feature of the property rule, The existing property rules data model did not allow you to override a specific feature of the rule without also setting the other features Once a property rule is created, all features are set and any inherited rule subsequently created from a higher business object in the hierarchy likely would not pass its new feature values past this property rule to business objects below. The new property constants provide a robust framework to support custom overrides on every feature of the rule. Migration utilities are incorporated in the upgrade scripts to perform migration of all existing property rule objects in your database to the property constants framework The existing functions used to retrieve the property rules on the server are deprecated 228 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements Obsolete uti ies ‘Teameenter command line utilities are used by administrators to manage ‘Teameenter 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 * append_procedure Use the plmxml_impoct utility instead. * batchmode_clearance_analysis.pl ‘This script is replaced by the analyze_managed_produet.pl script, which is included in the stand-alone Teamcenter lifecycle visualization mockup installation. * generate _loadfsccache tickets (First published Teameenter 8.2) ‘The generate _loadfsccache_tickets is obsolete and is replaced by the load_fsccache utility. + import_dfa_file (First published Teameenter 2007.13) ‘The import_dfa_file utility is obsolete, Use the Business Modeler IDE to create and manage the objects that were previously managed by this utility, * object_backup Use the Hot Backup over FMS feature instead. * object_recover Use the Hot Backup over FMS feature instead. © purge_mirror_volumes Use the Hot Backup over FMS feature instead. PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 227Chapter 2 ‘Support and certification announcements ‘The following utilities are also obsolete * apply_naming rule * bmide_upgrade_baselines * business_cules dtdxml2pimxml * create_ai type * create_change_types * ereate_cost_form * ereate_snap_shot_view_form * datasettype_cleanup * deepeopyrules_migration ° erm * gmpdm_get_location_info + imanhelp + impoct_export_business_cules * input_notetype_default + install_bmf_cules + install_lovs + install_type_display_cules + install_types + make_datasettype * migeate_action_rules to_bmf * migeate_alias + migeate_complex_property_cules + migeate_type_display_prefs * reset_protection * cundtCacheClean * cundtCachelnit * cundtCachePopulator 228 Thamconter @.1 Release Sulltin PLwp0001 1(01-037134-080)‘Support and certification announcements + sb * teerp_schema + upgeade_ar * update_class_property + upgeade_motif_workflow_templates * upgeade_nx_cam_templates + upgeade_types * upgeade_validation_objects + upgeade_workflow_objects PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 223Chapter2 Support and certification announcements Obsolete preferences and environment variables Preferences are special environment variables stored in the Teameenter database that are read during application usage. To work with preferences, in the rich client, choose Edit-Options and choose Index at the bottom of the Options dialog box. For more information about preferences, see the Preferences and Environment Variables Reference ‘The following environment variables are obsolete + TC_LOCALIZATION_DIR ‘The following preferences are obsolete: * ASSIGNED_DATASET_ID_MODIFIABLE * ASSIGNED_DATASET_REV_MODIFIABLE * ASSIGNED_ITEM_ALTREV_MODIFIABLE * BMF_BYPASS_ALL_EXTENSION_RULES * BMF_ENABLE_DEBUG * BMF_SUPPRESS EXTENSION _RULES_DISPLAY * BOM _line_full_pcops * BYPASS_RULES * CATIA check_in_generate_ data_priority * CATIA_on_demand_generate_vis_data_priority * CATIA_V4_on_demand_generate_vis data_peiority * Cfg_Att_add_props_of_form_types * CM_ChangeNoticeRevision_displayed_pseudofolders * CM_ChangeRequestRevision_displayed_pseudofolders * CM_Cm0DevRgstRevision_displayed_pseudofolders * CM _default_displayed_pseudofolders * CM_ProblemReportRevision_displayed_pseudofolders * _createprops * DEEPCOPY keep _name_list * _DisplayProperties * EDA CadenceBOMOptionDefault * EDA Gateway CombinedBOMOptionDefault 290 Thamcenter @1 Reloage Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements * EDA GatewayPcbBOMOptionDefault * EDA GatewaySchematicBOMOptionDefault * EDA GenerateViewable * EDA MentorBOMOptionDefault * EDA _PadsBOMOptionDefault * EDA Secondaryltems * ETS_available * ETS_home * GMS offline_use_TcGS ‘This preference is for internal Siemens PLM Software use only. * GMS _site_checkin_after_import ‘This preference was for internal Siemens PLM Software use only. * ICS _classify_immediately_NX Use the Reuse Library when classifying in NX. * IDEAS _check_in_generate_vis data_priovity * IDEAS import from_tdm_default_gen_vis data_peiority * IDEAS _import_from_tdm_gen_vis_data_display * IDEAS import from_tdm_gen_vis_data_input * IDEAS import from_tdm_options default_gen_vis_data_peiority * IDEAS _import_translation_service_name * IDEAS _on_demand generate_vis_data_priority * IDEAS teanslation_dataset_type_names * IDEAS translation_service name + IMAN __Volume * IMAN_NFS_IMPORT_EXPORT_PERF * IMPORT _EXPORT_USING_TCFS + ItemCreation.NoMasterForm For workarounds, see the release note about this obsolete preference in the Business Modeler IDE release notes later in this guide, PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 234Chapter 2 ‘Support and certification announcements ItemCreation.NoRevMasterForm For workarounds, see the release note about this obsolete preference in the Business Modeler IDE release notes later in this guide, _Maturity_Level All preferences of this type are replaced by the Maturity Statuses business object constant. For more information, see the Business Modeler IDE Guide MSE_ICS_default_occurrences_ types map NX Interop_Type NX_on_demand_generate_ data_peiority NX_tocgm_on_demand_generate_vis data_peiority NX_tocgm_translation_service_name NX translation_service_name PortalDesignContextCLRServers Use the RDVClearanceProxy Servers preference instead. PROE_on_demand_generate_vis_data_priovity PROE translation_service_name PSE_absoce_compound_properties PSE_add_props of_item_form_types PSE_add_props_of rev_form_types PUBLISHEDOBJECT object_extended_attrs QRY_display_details QRY_number_of favorites QRY_output QRY_output_options QRYColumnsShowWidthPref QUOTA_active QUOTA logging level QUOTA_minimum lifetime QUOTA_unload_percentage 292 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements * QUOTA _unload_threshold * RDV_variant_overlays_mode * _relation_peimary All preferences of this type are replaced by relation properties, For more information, see the Business Modeler IDE Guide * REQ avoid_default_Full_Text_creation * REQ default_styles template * SFRVolume_NT + SFRVolume_UNX * Show_ME_line_linked_icons ‘This preference is replaced by the MELineLinkedIconsProperty preference * ShowNewAliasMenu * TC_always_try_volume_server * TC_CURSOR_CACHE * TC_CURSOR_LNSZ * TC_CURSOR_NUM * TC_CURSOR_SQL * TC_CURSOR_STAT * TC_DIS SDMarkup_dstype * TC_DIS_ SDMarkup relationship * TC_DIS_AutoCreate_ITEM * TC_DIS_image_capture_dstype * TC_DIS_image_capture relationship * TC_DIS_ITEM_AutoCreated_TypeName * TC_DIS_markup_dstype * TC_DIS_markup relationship * TC_DIS_save_plmxml_dstype * TC_DIS_save_plmsml_relationship * TC_DIS_session_dstype PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 233Chapter 2 ‘Support and certification announcements ‘TC_DIS_session_relationship TC_Export_Bucket_Size TC_force_nfs_access ‘TC_negotiate_nfs_access ‘TC_register_internal_service_modules TC_Security_Level TC_show_open_in_pv_button TC_Socket_Bucket_Size TC_validate_nfs_accessibility TC_VALIDATION_MANDATORY_CHECKERS, TC_VALIDATION_PROGRAM TC_vmu_version TC_VOLUME_ACCESS_LOG ‘TeSequenceldVisible ‘Teacelink_deepcopy_on_Revise ‘Teacelink_deepcopy_on_SaveAs UGSideastojt_IdeasAssembly_ets_nr_types UGSideastojt_IdeasDrawing ets_nr_types UGSideastojt_IdeasPart_ets_nr_types UGSnstocgmdirect_ets_ds types UGSnxtocgmdirect_UGALTREP_ets_nr_types UGSnxtocgmdirect_UGMASTER ets_nr_types UGSnstocgmdirect_UGPART_ets_nr_types UGSnxtocgmdirect_UGSCENARIO_ets_nr_types UGSnstopvdirect_ets_ds_types UGSnstopvdirect_UGALTREP_ets_nr_types UGSnstopvdirect_UGMASTER ets_nr_types UGSnstopvdirect_UGPART_ets_nr_types 294 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements * UGSproeto; * UGSproetojt_ProPrt_ets_nr_types _ets_ds types * _viewerprops * View_line_display_props * view_view_valid_occurrencetypes PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 235Chapter 2 ‘Support and certification announcements Obsolete ITK functions ‘The Integration Toolkit (ITI) is a set of C functions provided by Siemens PLM Software that you can use to integrate third-party or user-developed applications with Teamcenter, For information about deprecated and obsolete IT funetions and their replacement functions, see the Integration Toolkit Function Reference. Choose the Deprecated menu command on the top menu bar. * Obsolete Workflow ITK functions (First published Teamcenter §.3) ‘The following Workflow ITIK functions were deprecated in Teamcenter engineering process management 9,1 and are obsolete in Teamcenter 8.3 ‘The Cascade Release (CR) model (and some of its IT functions) was a simple model of a workflow process that only inchided review tasks (release level in older terminology) in series This meant that you could assume that there was an active review task, that there would only ever be one review active at any time, and that they were all top level tasks not contained in another parent task (like'a route task or other organizational parent tasks). ‘That simple model has been obsolete for many releases Currently, a workflow process can include zero to many review tasks, and zero to many task types active at any one time, These tasks may be hierarchically deeper than top level in a parent/child task hierarchy, Code using the obsolete OR API (that assumes there is one top-level active review task at any time) against current workflows is incorrect and should be rewritten to consider the reality of the newer features Newer code must get the tasks of the EPMJob object and check their status and task type before operating on them. Replace calls to the CR_ask_current_release_level function with the following calls 1. Use the EPM_ask_root_task function (to get the root task from the EPMdJob object) Use the EPM_get_type_tasks function (to get subtasks of type review task) or the EPM_ask_sub_tasks function (to get all subtasks) 3. Use the EPM_ask_state function to check state of the task Ifitis in a started state that may be one of several started tasks that you need to process Obsolete Workflow ITK function Replacement ITK function ‘CR_add_reference_objects EPM_ask_coot_task EPM_add_attachments CR_add_target_objects EPM_ask_root_task EPM_add_attachments CR_ask_current_celease_level EPM_ask_root_task EPM get_type_tasks or EPM_ask_sub_tasks EPM_ask_state EPM_ask_review_task_name 298 Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)‘Support and certification announcements Obsolete Workflow ITK function Replacement ITK function CR_ask_reference_objects CR_ask_release_levels CR_ask_target_objects CR_create_job CR_demote_job CR_demote_target_objects CR initialize job CR initiate CR_promote_job CR_promote_target_objects CR_remove_reference_objects CR_remove_target_objects CR_set_decision EPM _create_job EPM_initialize_job PLwp0001 1(01-037134-080) EPM_ask_root_task EPM_ask_attachments EPM get_type_tasks EPM_ask_root_task EPM_ask_attachments EPM_create_process EPM_ask_root_task EPM get_type_tasks (or EPM_ask_sub_tasks) EPM_ask_state EPM_demote_task EPM_ask_root_task EPM get_type_tasks (or EPM_ask_sub_tasks) EPM_ask_state EPM_demote_task EPM_create_process EPM_create_process EPM_ask_root_task EPM get_type_tasks or EPM_ask_sub_tasks) EPM _ask_state EPM_promote_task EPM_ask_root_task EPM get_type_tasks or EPM_ask_sub_tasks) EPM _ask_state EPM_promote_task EPM_ask_root_task EPM_remove_attachments EPM_ask_root_task EPM_remove_attachments EPM_ask_root_task EPM get_type_tasks or EPM_ask_sub_tasks) EPM _ask_state EPM_set_decision EPM_create_process EPM_create_process ‘Teamconter 9.1 Releage Sulltin 297Chapter2 Support and certification announcements Obsolete data model ‘The following data model items obsolete, You can view data model items using the Business Modeler IDE. For more information about data model, see the Business Modeler IDE Guide. Obsolete Workflow data model (First published Teameenter 8.3) ‘The following Workflow data model objects are obsolete and are no longer used. * Obsolete Workfiow business objects Obsolete business object Replacement business object EPMInheritance None EPMTaskDefinition EPMTaskTemplate EPMTaskStatus ReleaseStatus OLD_EPMBRHandlec EPMBRHandler OLD_EPMBusinessRule EPMBusinessRule OLD_EPMHandler EPMHandler ReleaseLevel EPMReviewTask ReleaseLevelDefinition EPMReviewTaskTemplate RLMAccessDefinition None SignoffList None Obsolete Workflow handlers ‘The following Workflow handlers are obsolete * EPM.attach-item-revision-targets ‘This handler is replaced by the EPM-attach-related-objects handler. For more information, see the Workflow Designer Guide 298 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)Chapter PLw00001 1(01-037134-080) What’s new New Teamcenter applications and solutions New, revised, and obsoleted Teamcenter documentation New Teamcenter 9.1 Help Library Installing Teameenter Quick preconfigured Teameenter installation Simplified Teamcenter installation process ‘Teamcenter executables are 64-bit on 64-bit Solaris Silent mode enhancements in TEM ‘Teameenter clients use Teamcenter client communication system (recs) ‘Teameenter clients support connections through a forward proxy ‘TCS supports 401-based authentication ‘TCCS supports form-based challenge Upgrade diagnostics ‘TEM provides cumulative error log during upgrade Business Modeler IDE generates accurate baseline file Automatic backup of data model comparisons during upgrade ‘Template version check before upgrade Upgrade log viewer Configuring Teameenter Business Modeler IDE ‘Updating a live production server Displaying lists of values (LOVs) based on a project ‘Managing LOVs through a batch utility Creating reports Backing up projects ‘Training videos Creating a common template Refactoring the create operation ‘Adding or changing icons on business objects Administering Teamcenter Sharing a TeServer instance FCC moves into Teamcenter client communication system (TOCS) Sharing server cache ‘Support for controlling access based on compound property values Server changes to support the use of keys Caching rich client metadata Audit Manager enhancements eamcenter 91 Release BulletinConfiguring dynamic logging and debugging 3-24 Monitoring critical event data 3-25 Restarting warm servers 3-25 Configuration and reporting features added for managing license types... 3-26 NX Check-Mate and NX RDDV validation agent objects installed automatically 3-27 Updating the backpointer table after upgrade 3.27 Cleaning the POM_TIMESTAMP table 3-28 Bnhanee monitoring and logging of all tiers through J2BE server manager 3-28 System logging enhancements 3-29 Base services File Management System logging and monitoring 3-30 Password file argument available for POM utilities 3-30 ‘Teamcenter supports Kerberos authentication 331 ‘Teamcenter supports applet-free authentication 331 Using Teameenter interfaces 3:32 User interface changes to support the use of object IDs 332 Requirements management features in Client for Office 3-34 Optional feature selection in the Client for Office installer 3-35 Using view networks in the rich client 3-35 Using the rich client Launch Pad 336 Updates to the thin client user interface 336 Updates to thin client functionality 3-37 Office attribute exchange 338 ‘Simple search for business objects 339 ‘Marisup disposition 339 Viewer view framework enhancements 3-40 ‘Thin client XRT style sheet enhancements 3-40 ‘Managing changes and workflows 3-41 Replicating workflow templates 341 EPM_multiple_processes_targets preference default value is ON 341 ‘Support for penetration requests in Issue Manager 341 Managing content, reports, and schedules 342, Creating custom visual reports 342, Embedded dashboard 3-43 View reports based on office templates 3-43 Customizing status indicators 3-43 Viewing the new state column 3-44 Updating a schedule without saving it to the database 3-44 Loading partial schedules for quicker access 345 Creating a Program View without creating a dataset 345 Updating execution data for schedule tasks 345 Creating dependencies across multiple schedules 346 ‘Schedule Manager enhancements 346 Content Management re-engineering 3-47 Systems Engineering 348 New Systems Engineering and Requirements Management perspective... 3-48 Funetion view 348 Requirements management enhancements 349 Requirements management features in Client for Office 3-51 eamcontr 94 Releage Bulletin PLw00001 1[01-037134-080)Duplicating requirement specification structures ‘Trace link enhancements Diagram view Budgets Migration from Systems Engineering and Requirements Management Data dictionary Behavior Modeling tool integration and MATLAB integration Hierarchical numbering of requirements in Systems Engineering Excel report access Excel report access through URLs Generate an Exetel report and its URL Access an Excel report through its URL Live Excel and live Word options Live Excel and live Word options for resolving edit conflicts ‘TC_setProperties ‘Traceability Matrix view General enhancements for Systems Engineering Sharing data 3 Item identification key arguments in data sharing utilities 3 Bulk loader 3 Sharing global organization data 3 Export configured BOM to a TC XML file 3 Export a briefcase file without Global Services 3 Selecting the template and partition for RFx events 3 Enhanced logging support in Multi-Site 3 ‘Managing product structures and collaborative product development 3-69 Controlling structure expansion 3-69 Carrying forward incremental change elements during cut, copy, and paste actions 3-69 Change in default behavior with in-context (absolute occurrence) GRM overrides 3-70 Managing memory for BOM expansion 3-71 ‘Managing BOM run-time properties 3-72, Cloning structures with CAD part families and multilevel CAD dependency relationships Displaying decimal places for quantities ‘Managing manufacturing data 3-75 Dynamic framework in Manufacturing Process Management applications Standard text and work instruction enhancements Update multiple product views Additional supported manufacturing features Viewing and assigning parts, resources, and manufacturing features in the PERT view Integrating TiCon in Teamcenter ‘Managing structure configuration Finding occurrence group lines in other structure Using the structure search on occurrence groups Managing 3D PDF reports Selecting objects by type Balancing a production line in Manufacturing Process Planner PLwp0001 1(01-037134-080) oamcenter 91 Release BulletinEnterprise bill of process 3-82 Dynamic framework in Resource Manager 3-84 ‘Manufacturing Resource Library enhancements 3-84 Resource Manager enhancements 3-85 ‘Multiple perspectives in Manufacturing Process Planner 3-85 ‘Managing Mechatronics data 3-88 EDA Part Library Usability Automation 3-88 CCODM phase 2 enhancement 3-85 Visualizing products Base and above FMS partial file cache DGN file type enhancements Raster file type enhancements Load large models using background processing Read-only 3D markups and 3D GD&T markups Print dashed lines on 2D files Print a specific date and time PMI cross section enhancements Change the base font in ECAD documents View 2D or 3D documents in multiple viewing windows Clone the 8D Viewing window Standard and above ‘Teameenter visual issues Save Teamcenter product views 3D measurement enhancements Professional and above Visual report enhancements Part transformation enhancements Visual report enhancements See-Thru viewing enhancement Coordinate systems enhancements Mockup only ‘Export saved filters Cache-less search Managing CAE data 3-95 ‘Simulation tool launch and batch meshing enhancements 3-95 ‘Structure map enhancements 3-95 CAE Manager enhancements 3-96 Repeatable Digital Validation 3-97 Using cacheless search with Multi-Site Collaboration and NX 3.97 Managing quality data 3-98 Report Definition Language file management 3-98 ‘Simplified bill of process and bill of record creation 3-98 DPV engineering workbook 3-98 Parsing scripts 3-99 Managing maintenance, repair, and overhaul 3-100 ‘Managing Maintenance, Repair, and Overhaul data 3-100 Service scheduling 3-100 eamcontr 94 Releage Bulletin PLw00001 1[01-037134-080)Customizing Teamcenter Removing multiple inheritance in the business object Impl C++ classes ‘Upgrading the rich client framework from Eclipse 3.5 to 3.6 Querying for compound properties on types Style sheets Style sheet enhancements visibleWhen parameter Label text tag Font style tagging ‘URL tagging: ‘Teameenter industry solutions Aerospace and Defense Set the Commercial and Government Entity Code or location code Product Master Management Product Master Management in the rich client 3-101 3-101 3-101 3-102 3-102 3-102 3-103 3-104 3-105 3-105 3-106 3-106 3-106 3-107 3-107 PLwp0001 1(01-037134-080) Teamcenter 91 Release BulletinChapter 3 What’s new New Teamcenter applications and solutions ‘Teameenter 9.1 includes three new applications, a new integration, and two reworked applications. * New applications: © Product Master Manager and Product Master Manager Administration The rich client includes two new application perspectives, Product Master Manager and Product Master Manager Administration. Use of these applications requires the installation of the optional Product Master Management functionality in your Teamcenter server and client environments. Product Master Management allows original equipment manufacturers in the automotive, truck, and heavy machinery manufacturing sectors to manage their bill of materials data. For more information about Product Master Management, see the Product ‘Master Management collection. Note that deployment of Product Master Management for pilot or production purposes requires the approval of a designated Siemens PLM Software product management representative © Service Scheduler Service Scheduler supports service scheduling capabilities within ‘Teameenter, Service Scheduler lets users create and manage service schedules and the associated activities and record information about the implementation of the service For more information, see Service scheduling. * New integration © Behavior Modeling Tool Integration Behavior Modeling Tool Integration is a new integration associated with the new behavior modeling integration (Systems Engineering), For more information, see the Behavior Modeling Tool Integration Guide. * Reworked applications o Systems Engineering and Requirements Management New functionality for the Systems Engineering perspective includes a Function (functional modeling) view that allows you to create and manage functions in a similar way to product (physical) and requirements structures (the functionality of the previous Requirements Manager application is now part of this application) PLwp0001 1(01-037134-080) Teamcenter 9.1 Release Bulletin 34Chapters What's now For more information, see Systems Engineering, as welll as Getting Started with Systems Engineering and the Systems Engineering Guide © Content Management Content Management has been re-engineered to eliminate the Web application server and enable the Content Management rich client to work: directly with Teamcenter objects and the Teamcenter server, For more information, see Content Management re-enginecring, as well as the Content Management Guide New, revised, and obsoleted Teamcenter documentation ‘The following tables list new, revised, or obsolete Teamcenter documentation deliverables for Teamcenter 9.1, New Teamcenter documentation Name Description Behavior Modeling Tool Integration Guide ClearanceDB Administration Guide Collaborative Product Development Guide Getting Started with ‘Systems Engineering Getting Started with Workflow My Teamcenter Guide 32 Teameonter 9.1 Release Buletin ‘This guide documents the Teamcenter mechanism available to integrate with MATLAB Simulink. MATLAB Simulink is a tool used to manage model data and model lif cycle, With the Teameenter integration with MATLAB, MATLAB Simulink is used as the primary model authoring tool while the generated or authored model data is managed within ‘Teameenter, ‘This guide documents ClearanceDB, an optional module for Teamcenter lifecycle visualization which you can configure to work with product data managed in Teameenter. ClearanceDB enables you to analyze and manage clearance issues according to rules and conditions based on part metadata, ‘This guide describes how to coordinate in real time during the design cycle of a product. ‘This guide describes the systems engineering tasks that you can perform in Teamcenter. ‘This guide overviews the processes and procedures supporting workflow that you can perform in ‘Teameenter, ‘The content of this guide is extracted and updated from the previous version of the Rich Client Interface Guide. ‘The My Teamcenter Guide contains information about working with information, results, and workflows in the My Teameenter application, PLwp0001 1(01-037134-080)What's new New Teamcenter documentation Name Description ‘Relation Browser Guide Service Scheduler Guide Teamcenter Data Model Report Using Product Master Manager Administrator and Using Product Master Manager ‘The content of this guide is extracted and updated from the previous version of the Rich Client Interface Guide. ‘The Relation Browser Guide contains information about using Relation Browser application, ‘This guide documents the Service Scheduler application, Scheduler lets users create and manage service schedules and the associated activities and record information about the implementation of the service ‘This guide contains automatically generated documentation on data model objects in Teamcenter, such as business objects, classes, attributes, properties, lists of values (LOVs), and so forth, This guide can be installed from the Online Help panel in ‘Teameenter Environment Manager (TEM). ‘To generate your own data model report, run the bmide_generate_datamodel_doc_report utility. ‘These guides describe the Product Master ‘Management functionality in Teameenter Revised Teamcenter documentation Name Description Client Customization Programmer's Guide (Rich Client Customization Programmer's Guide and Thin Client Customization Programmer's Guide) Content Management Guide PLwp0001 1(01-037134-080) ‘The Rich Client Customization Programmer's Guide is renamed to Client Customization Programmer's Guide, In addition, the content of the Thin Client Customization Programmer's Guide is moved into the renamed manual. This change reflects a move away from separate customizations needed per client type. Increasingly, enhancements to client-independent framework tools (such as the Business Modeler IDE and XML rendering style sheets) allow the same user interface appearance and behavior to be seen on all clients connecting to a Teamcenter server. ‘This guide now combines the content from both the former Content Management Guide and the Content Management Administration Guide Teamcenter 0.1 Release Bulletin 39Chapters What's now Revised Teamcenter documentation Name Description ‘Customizing Teamcenter Help Collection category NX Remote Manager Guide(Application Integration Enutronment) Rich Client Interface Guide ‘Systems Engineering Guide Embedded Software Solutions Guide ‘The following references for developers are moved from the Customizing Teamcenter Help Collection category to a new category of the Teamcenter Help Collection deliverables called Developer References for Customization: © C++ API Reference * Integrator Toolkit (ITK) Function Reference * Services Reference In addition, these developer references are now an optional part of the Help. Using TEM, you can decide to install or not install these references, If you know you do not need these, not installing them will greatly reduce the disk space required by the Teamcenter 9.1 Help Library. ‘This guide is renamed from the previous title Application Integration Environment, Content is reworked to contain only the Remote Manager functionality. ‘The Rich Client Interface Guide is reduced in scope. ‘This guide provides information about managing the rich client interface, searching in Teamcenter, using the Application Interface Viewer, and working with ‘Teameenter options and preferences, ‘This guide documents the new Systems Engineering perspective, Content that was previously found in the Requirements Manager Guide is now in this new guide. ‘This guide now includes content from the former ClearCase Integration Guide. 94 Teameonter@ 1 Release Buletin PLwp0001 1(01-037134-080)What's new Obsolete Teameenter documentation Name Description Content Management Administration Guide Gateway for Oracle Manufacturing Configuration Guide Integration for Microsoft Office Guide Requirements Manager Guide ClearCase Integration Guide Content from this guide is now included in the Content Management Guide. ‘This guide is removed because this product is replace by the TC10316 Teamcenter Gateway for Oracle EBS, which is available for download from GTAC. See the 40 Kit. This kit includes the documentation, ‘This guide is removed because this integration is obsolete ‘This guide is replaced by the new Systems Engineering Guide. ‘This guide is removed and the content is now included in the Embedded Software Solutions Guide. PLwp0001 1(01-037134-080) Teamcenter 0.1 Release Bulletin 95Chapters What's now New Teamcenter 9.1 Help Library ‘Teameenter 9.1 uses 2 new interface to display help. Links to related topics now appear in the pane on the right, Search functionality and a bread-crumb trail are available at the top of the online help window. These new features are designed to help you find the content you need more quickly. For a demonstration of the Teameenter 9.1 Help Library interface features, see the ‘Teameenter Help Tour. For more information about Teameenter 9.1 Help Library behavior and commands, see Getting Started with Teamcenter. As always, take advantage of the feedback link at the bottom of the browser window to send us your feedback. ‘Was this information usefull ¥) — X. Note The PDF version of the Teameenter 9.1 Help Library is not yet available in this new interface 26 Teamconter@ 1 Release Suletin PLwp0001 1(01-037134-080)What's new Installing Teamcenter Quick preconfigured Teamcenter installation ‘Teameenter Environment Manager (TEM) provides a set of predefined common ‘Teameenter configurations that require minimal user input to install ‘The Quick Preconfigured Install button is added to the Welcome to Teamcenter panel in TEM. Secret ey Ines Clicking this button allows you to choose one of four common Teameenter configurations PLwp0001 1(01-037134-080) Teamcenter 0.1 Release uletin 37Chapters What's now aa Rot In the past, some of these configurations required as many as 18 panels in TEM to configure, A quick preconfigured installation requires only four panels. For the four common Teameenter configurations provided by this feature, the simplified installation process should not even require the Teamcenter installation guides. Help for each panel in the quick preconfigured installation process is provided from the help button For more information, see Teamcenter Environment Manager Help, the Teamcenter server installation guides (for Windows and UNIX/Linux), and the client installation guides (for Windows and UNIX/Linux), 38 Teamconter 9.1 Release Buletin PLwp0001 1(01-037134-080)What's new Simplified Teamcenter installation process ‘Teameenter Environment Manager (TEM) provides improved navigation and a simplified sequence of panels Beginning with a simplified weleome panel, TEM provides more efficient and intuitive processes for installing, maintaining, upgrading, and patching Teamcenter. Secret ee eer errey ey Ines ‘Some features, like the FMS server cache (FSC), previously required a series of six or more TEM panels to install. These features can now be installed with a default configuration from a single panel, providing advanced configuration options from an Advanced button. PLwp0001 1(01-037134-080) Teamcenter 9.1 Release uletin 39Chapters What's now [oro Lipase 5 For more information, see the Teamcenter server installation guides (for Windows and UNIX/Linux) and the client installation guides (for Windows and UNIX/Linux), 340. Thamcenter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new Teamcenter executables are 64-bit on 64-bit Solaris ‘Teamcenter executables for 64-bit Sun Solaris platforms are 64-bit. In previous versions, Teamcenter executables were 32-bit but ran on both 32- and 64-bit Solaris Teamcenter executables for 64-bit Solaris are now 64-bit applications For more information, see the Installation on UNIX and Linux Servers Guide. Note The Teamcenter rich client is not supported on Sun Solaris platforms Silent mode enhancements in TEM TEM can now perform certain configuration maintenance actions in silent mode. ‘Silent mode in TEM suppresses prompts and requires minimal user interaction, TEM provides the capability to capture inputs during a TEM session into a silent distribution file that can be used to perform similar installations on other ‘Teameenter hosts. Previous Teamcenter versions supported silent mode for installing and patching ‘Teameenter, Teamcenter now adds the capability to add or remove features in silent mode, You can create a silent distribution file by selecting the Create Silent Distribution check box in the Feature Maintenance panel in TEM. For more information about silent installation and configuration, see the Teamcenter server installation guides (for Windows and UNIX/Linux), Teamcenter clients use Teamcenter client communication system (Tccs) ‘The FMS client cache (FCC) is now generalized into a new Teameenter client communication system (TCCS), TCCS provides a single point of access to the Internet for Teamcenter clients and provides a single point of network-related configuration. Itincorporates the forward proxy support library and also the existing reverse proxy support from previous Teameenter versions, Teamcenter clients connect directly to TCOS through a secure pipe, as the FOC provided in previous Teameenter versions. For more information, see the Teamcenter server installation guides (for Windows and UNIX/Linux) and also the System Administration Guide PLwp0001 1(01-037134-080) Teamcenter 9.1 Release Bulletin 3-14Chapters What's now Teamcenter clients support connections through a forward proxy This feature allows Teamcenter four-tier clients to access the Teamcenter Web tier and File Management System (FMS) connections through a centralized network: access point called Teamcenter client communication system (TCCS), This provides for a single configuration with support for forward proxy servers. The existing reverse proxy support is now available through TCCS, Clients connect to TCCS through a secure pipe Forward proxy support in Teamcenter includes support of proxy autoconfiguration (PAC) files, It can be configured during installation or can automatically detect the proxy settings of the user's Web browser configuration, All Teamcenter clients connecting to TCCS can share a single proxy configuration. ‘The new feature is transparently active in all Teamcenter clients that integrate with TCCS. For more information, see the Teamcenter server installation guides (for Windows and UNIX/Linux) and also the System Administration Guide TCCS supports 401-based authentication ‘Teamcenter client communication system (TCCS) detects 401 challenges from reverse proxy servers or forward proxy servers ‘This feature is available for rich clients that use TCCS communication in four-tier deployments. For more information, see the Teamcenter server installation guides (for Windows and UNIX/Linux) and also the System Administration Guide TCCS supports form-based challenge ‘Teamcenter client communication system (TCCS) supports form-based challenge from reverse proxy servers (IBM WebSEAL and CA SiteMinder). TCCS can detect form-based challenges in a configurable manner TCCS allows you to specify some fields for form-based challenge in a TCCS configuration. TCCS matches the form-based challenge with the format you specify in the TCCS configuration. ‘This feature is available for rich clients that use TCCS communication in four-tier deployments. For more information, see the Teamcenter server installation guides (for Windows and UNIX/Linux) and also the System Administration Guide 942. Thamcenter @1 Releage Bulletin PLwp0001 1(01-037134-080)What's new Upgrade diagnostics TEM provides cumulative error log during upgrade At the beginning of the upgrade process, TEM provides two options for how to proceed when an error is encountered during Teameenter upgrade: * Stop database upgrade at first error ‘This option stops Teameenter upgrade when the first error occurs, * Stop database upgrade after accumulating all errors This option allows the database upgrade to continue when an error is encountered, and report all errors at the end of the upgrade process. ‘The option to accumulate upgrade errors allows Teamcenter to continue with the upgrade process and fail the upgrade at the end. TEM then provides a report of all errors encountered during the upgrade. Using the upgrade errors report displayed in TEM, you can address multiple issues preventing a successfull upgrade before you attempt an upgrade again. You can also submit the upgrade errors log file to ‘Siemens PLM Software customer support for further analysis, Caution Siemens PLM Software strongly recommends using this option only when upgrading a test environment, Errors during database upgrade could render the database unusable For more information about using Teameenter upgrade error logs, see the Upgrade Guide. Business Modeler IDE generates accurate baseline file ‘The Business Modeler IDE is enhanced to generate an accurate Teamcenter baseline file for the upgrade process ‘This feature in the Business Modeler IDE provides administrators the capability to automatically generate an accurate baseline file that can be used to upgrade other sites, ‘The baseline file is automatically generated when the extracted custom template is, successfully loaded in the Business Modeler IDE. For more information about baseline files, see the Business Modeler IDE Guide For more information about Teamcenter upgrade, see the Upgrade Guide. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 343Chapters What's new Automatic backup of data model comparisons during upgrade Business Modeler IDE utilities perform data model comparisons at various stages of a Teameenter upgrade, generating delta files each time, Teamcenter automatically backs up these delta files from each data model comparison performed during an upgrade. After upgrade, these files are available under the logs\compare_history directory. These files can be useful in diagnosing the stage in which an upgrade failure occurred. For more information, see the Upgrade Guide Template version check before upgrade ‘To prevent upgrade errors due to incorrect template versions, Teameenter verifies, that custom templates and any dependent asynchronous templates have been upgraded to the latest version of Teamcenter before starting an upgrade. If any incorrect versions are detected, Teamcenter reports these problems and does not start the upgrade ‘Typically, a Teamcenter administrator upgrades custom templates in the latest version of the Business Modeler IDE before upgrading the corporate server, The administrator then selects the upgraded templates during the upgrade in TEM In previous Teamcenter versions, if the administrator did not upgrade a custom template or mistakenly chose an old version of a custom template, data model errors could occur during upgrade. This Teamcenter TEM enhancement ensures template versions are validated before upgrade begins Note This feature applies only to upgrades from Teameenter 2007 or later, not to upgrades from Engineering Process Management. For more information, see the Upgrade Guide 2:44 Teamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Upgrade log viewer ‘Teamcenter provides an upgrade log viewer ta help analyze upgrade errors and issues. At the end of the upgrade process, the Upgrade Features panel in TEM displays the ‘results of each step in the upgrade process. Clicking the Navigate Logs button in this panel opens the upgrade log viewer ‘The upgrade log viewer is a dynamic interface that includes * Results of each step in the upgrade process * Links to log files for each step. * Detailed contents of log files Information in the upgrade log can be usefull in resolving upgrade issues and can also be helpful in communicating issues to Siemens PLM Software customer support. ‘For more information, see the Upgrade Guide. PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 345Chapters What's new Configuring Teamcenter Business Modeler IDE Updating a live production server ‘You can use the live update functionality in the Business Modeler IDE to revise nonschema data such as lists of values (LOVs) without shutting down the production server, ‘Typically, Business Modeler IDE developers create a template that contains the data model extensions. The server administrator then uses Teameenter Environment ‘Manager (TEM) to update the production database with the custom template Previously, if further updates needed to be made to the custom template in the database (for example, new LOV values needed to be added), the developer first updated the custom template in the Business Modeler IDE with the new LOV values, and then the server administrator shut down the production server and used TEM to install the template to update the production database. However, the recommendation to shut down the production server each time prior to updating the custom template in the database was too restrictive for administrators who wanted to update live data (for example, LOV values) on a regular basis. Therefore, the live updates functionality was devised to allow administrators to update nonschema data on running production servers. For more information, see the Business Modeler IDE Guide. Displaying lists of values (LOVs) based on a project Administrators can set up Teameenter to display different lists of values (LOVs) on an object's property depending on the project the object is assigned to. For example, ifan item is assigned to project A, the Color property shows one set of colors to choose from in the LOV, and if the item is assigned to project B, the Color property shows another set of colors Administrators use the Business Modeler IDE to create conditions that define which list of values to display for a project, The conditions are limited to using the following project properties in their definitions owning. project, project_list, owning user, and owning group. For more information, see the Business Modeler IDE Guide and the Project and Program Guide Note Beginning with Teamcenter 9.0, the ability to place conditions directly on LOVs or sub-LOVs is deprecated. Now, when you create LOVs or sub-LOVs, the Condition box is disabled, Disabling this box saves on performance, because ifan LOV has many values, evaluating every condition directly on the LOV or sub-LOV can cause performance problems However, you can apply conditions to LOVs when you attach them to properties For more information, see the Business Modeler IDE Guide, 248 Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Managing LOVs through a batch utility ‘You can externally manage list of value (LOV) values in the Teamcenter database rather than in your template. Such LOVs are known as externally managed LOVs, ‘The values for LOVs that are marked as managed externally can be updated using the bmide_manage_batch_lovs utility. This utility requires an XML file as input that conforms fo the batch utility file schema. The values from an external enterprise resource planning (ERP) system or any CSV file can be used to create the required XML file that can be used as input to the utility, For more information, see the Business Modeler IDE Guide. Creating reports ‘You can create reports on the data model by choosing File--New—-Other—Business Modeler IDE—Reports. You can create the following types of reports: * Compare Two Data Models Provides the data model differences between two data models. For example, the report can show the differences between the data model in your Business Modeler IDE and the data model that has been deployed to a Teamicenter database * Condition Usage Provides the details of a condition and all model elements that use the condition. * Data Model Provides the details on categories of model elements, for example, LOVs, GRM rules, deep copy rules, naming rules, and so on. * Data Model Documentation Generates a report of all data model elements for all templates in the data model set. Note You can also obtain a report of the COTS data model in the Teamcenter Data Model Report provided in the Teamcenter HTML documentation collection. This guide can be installed from the Online Help panel in ‘Teamcenter Environment Manager (TEM) For more information, see the Business Modeler IDE Guide. Backing up projects ‘You can maintain a regular backup of your Business Modeler IDE project so that you can restore it if necessary, For example, when deployment of a template to a database fails, you can restore the project data ta the state it was in prior to failure Use the Project Backup dialog box to set project backup. To access this dialog box, in the Navigator view, select the project and choose Project-Properties—Teamcenter—Project Backup. For more information, see the Business Modeler IDE Guide. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 347Chapters What's now Training videos ‘Training videos are added to the Business Modeler IDE Guide to instruct the user how to perform basic tasks, such as creating a project and custom data model objects ‘The videos are available only in the HTML version of the guide. For more information, see the Business Modeler IDE Guide. Creating a common template When you upgrade from Engineering Process Management and you have multiple sites containing custom data model, you must create a template that contains all the data model common to all sites and create additional templates that contain data model unique to each site, Use the bmide_commontemplategenerator utility to generate the common template and the site-specific templates. For more information, see the Business Modeler IDE Guide and the Utilities Reference Refactoring the create operation Logically, the create operation creates objects and the save operation commits the data to the database. This pattern has been consistent for single objects, but in the past, it was not followed for compound objects like the Item business object. During the creation of compound objects, there were several database queries and commitments performed during the create operation, resulting in performance degradation and referential integrity issues Now the logical integrity of the create and save operations is enforced. Any failures during the create operation do not result in dangling objects in the database if the create operation does not commit any data to the database. ‘The create methods for the following business objects are refactored to use the deferred save operation: Item ItemRevision Dataset Form Ifyou have custom code for create operations on these business objects or their children, you must ensure that it starts the save operation following the create operation, Therefore, if you have postactions attached to the legacy create messages that query the database for the newly created objects in the current create operation, you must move the postactions to the save message, This ensures that the refactored code accesses the in memory data instead of accessing the database. For more information, see the Business Modeler IDE Guide. ‘Adding or changing icons on business objects Icons are images placed on business object instances to identify them in the user interface, To add or change icons on business object types, use the Fnd0lcon business object constant in the Business Modeler IDE, The icon definitions are placed on the server and used by the rich client, Previously, you had to perform a customization to add the icons, Now it is done entirely through the Business Modeler IDE. 248 Thamcenter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new ‘You can change the default icon for an existing business object or add an icon to a newly created business object. You can also use a property rendering XML file to overlay icons on the base icon conditionally based on property values. For example, you can decorate the icon with images to designate the business object's state (status, remote, checked out, process, and 50 on). For more information, see the Business Modeler IDE Guide. Note You must use a different method to change the business object icons on the thin client, For instructions about changing business object icons in the thin client, see the Client Customization Programmer's Guide Administering Teamcenter Sharing a TcServer instance A TeServer instance can sometimes be shared by multiple applications on the same machine, If clients log on with the same user from applications that use sharing, the server is shared, and the clients stay synchronized While the TeServer architecture does not support threading service requests from different users, it can support multiple sessions (client applications) for a single user. In the rich client, this sharing is enabled by default, In a four-tier environment, whether the rich client connects to the same TeServer as other clients on the same machine can be controlled by the shareSession property in the site_specifie.properties file, This file can be found in the following location: Teamcenterinstall-location/portal/plugins/configuration_version/ Enabling the shareSession property sets the OPT_SHARED_DISCRIMINATOR connection option to true in the rich client, To disable this sharing, set the shareSession property to false. The rich client always sets the OPT_SHARED_EVENTS fiag on the connection to true Ina custom Teameenter Services client application, this sharing is disabled by default, To enable this sharing, set the new OPT_SHARED EVENTS parameter on the connection object to true before initiating a logon. The OPT_SHARED_DISCRIMINATOR fiag can also be enabled to configure the application to easily connect to the same server as other Teamcenter applications running on the same desktop. (Use this for client applications when sharing a ‘TeServer instance in a four-tier environment, Two-tier clients usually share a server without special setup.) For more information about using the OPT_SHARED_EVENTS and OPT_SHARED_DISCRIMINATOR options in a custom Teameenter Services client application, see the Services Guide. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 343Chapters What's new FCC moves into Teamcenter client communication system (TCCS) In Teameenter 9.1, the FMS client cache (FCC) is generalized into a new Teamcenter client communication system (TCCS). TCCS provides a single point of access to the Internet for Teamcenter clients and provides a single point of network-related configuration. It incorporates the forward proxy support library and also the existing reverse proxy support from previous Teamcenter versions, Teamcenter clients connect directly to TCCS through a secure pipe, as the FCC provided in previous Teamcenter versions ‘The inclusion of the FCC within TCCS results in the following changes: * Starting or stopping TCCS or any of its container applications starts and stops TCCS and all its container applications, For example, the startfee command starts the starttces script. © Setting the initialize parameter of the FMSClientCache element to true in the tees.xml file enables FCC functionality when TCCS starts ‘This is the default value * The only tees.aml file the FCC accesses is the one stored in the TCCS configuration directory. Any other tees.xml files are ignored. * HTTP configuration parameters in the tees.xml file are available for FCC connection to the FMS server cache (FSC) © The feexml file contains a reference to the FSC URL. * The FCC connects to the FSC URL specified in the fce.xml file. The connection is through TCCS. For more information, see the Teamcenter server installation guides (for Windows and UNIX/Linux) and also the System Administration Guide Sharing server cache ‘The memory footprint is reduced for TeServer instances because metadata is moved to shared memory. Types, property descriptors, and constants are placed in a shared cache that is shared by all TeServer instances, A Generate Server Cache check box is added to the Foundation Settings panel in the ‘Teamcenter Environment Manager (TEM) to run the generate_metadata_cache utility. For more information, see the Teamcenter Environment Manager Help When you perform a deployment from the Business Modeler IDE, the server metadata cache is generated when you select the Generate Server Cache? check box on the Deploy dialog box. To force generation of the shared server metadata cache, run the generate_metadata_cache utility. For more information about generating server metadata cache from the Business Modeler IDE, see the Business Modeler IDE Guide, For more information about managing the shared server metadata cache, see the System Administration Guide 320. Thamcenter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new Support for controlling access based on compound property values In the past, Access Manager rule evaluation only supported persistent attribute values of Teameenter business objects, It could not support compound properties, run time properties, and so on. With the introduction of the Has Property rule condition, you can now define an Access Manager rule based on a compound property value For more information about using Has Property, see the Security Administration Guide. Server changes to support the use of keys The -key and -arch_key arguments are added to some utilities These arguments specify the key IDs of the item to act on, using the following format: cept teinkeyVali] [,keyAtte2akeyVal2]..[, keyAt tallseeyValll] ‘The -key argument is added to the apn_medic utility. The -arch_key argument is added to the following utilities: rdv_migrate_architecture redv_migeate_part_solutions For more information, see the Utilities Reference. Caching rich client metadata ‘Metadata is cached on the client computer, eliminating server calls for the cached metadata. The cache is placed at the following location on the client machine home-path\ Teancenter\PAC\session\wetacache For example, on a Windows machine, the client metadata cache is in the following location: C:\Documents and Settings\user-name\Teamcenter\PAC\session\metacache This new functionality has the following features: * Caching refresh notification Notifies you when the cache is refreshed. When you log on to the rich client, a check is made for new metadata on the server. If new metadata is found, the cache on the rich client is refreshed, and the following message is displayed: Synchronizing the Rich Client install files with the Teamcenter Server For more information, see the Rich Client Interface Guide. * ClientCache folder Stores cached metadata in the database. If you are logged on to the rich client as adatabase administrator (DBA), you see the folder under the Home location For more information, see the Rich Client Interface Guide. Warning If the administrator moves, renames or deletes this folder, then all clients fall back to a non-client-cached mode. PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 324Chapters What's new seachtet |Q? AB mY = Home WetaDatastamp Templates & (S RequirementsManagement Templates © Ws office Templates # © CAM Machining Knowledge | CAM Express Tutorials CAM Seto Templates & © Lnigraphics UDF parts © Unigraphies seed parts 8 Walbox ‘GB hewstutt ClientCache folder generate_client_meta_cache utility Caches metadata to improve client interaction with the server The utility is usually run during installation and upgrade, and when deploying from the Business Modeler IDE. Metadata is cached and refreshed automatically, but you can regenerate the cache using this utility. This utility should be run after ‘a style sheet is edited, if the text server files are updated, or if the client cache folder has been deleted, For more information, see the Utilities Reference. Generate Client Cache check box A Generate Client Cache check box is added to the Foundation Settings panel in the Teameenter Environment Manager (TEM) to run the generate_client_meta_cache utility. For more information, see the Teamcenter Environment Manager Help A Generate Client Cache? check box is added to the Business Modeler IDE to run the generate_client_meta_cache utility, For more information, see the Business Modeler IDE Guide. 2:22. Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Deploy the Template to Teamcenter Server Cc the Frish button to depoy the template to Teamceniter server, Project: bmide_project Server Profle: User 1D: Password: Group: Rok: Connect! |Generate Client Cache? (cenerat Server Cache? Generate Client Cache check box in the Business Modeler IDE © Environment variables 0 TC_SKIP_CLIENT_CACHE Causes the rich client to run in legacy mode and avoid downloading or using a local client meta cache. o AUX PATH Adds auxiliary path information needed by applications launched from the rich client, For more information, see the Preferences and Environment Variables Reference. PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 323Chapters What's now Audit Manager enhancements ‘The following new features are added to Audit Manager: * Search audit logs for old value of property that changed during an event, * Ability to configure and store Teamcenter object attributes for tracking * Display of attribute value changes * Server customization APIs to store NX part history to audit logs. * View NX part history in audit query. * Create audit logs when component is added or removed from a structure. * Anew event type named Detach is available when creating audit definition objects This event maps to item, item revisions and their subtypes. When you use this event in the audit definition object, audit logs are created when an object is detached from its parent object. * Track changes to attributes on components (occurrences). * Project based search for audit logs * You can only see audit log for the object you have read access to, For more information, see the Audit Manager Guide Configuring dynamic logging and debugging ‘The J2BE server pool administration interface allows administrators of four-tier environments to dynamically change the logging configuration of individual ‘Teameenter servers in the pool without restarting the pool When a problem is reported, you can use the J2EE server manager administration interface to identify the business logic server for the user's session and view the system log file If the log file does not contain sufficient information, you can change the logging level of the business logic server and/or other system components, re-execute the task, and capture the information in the log file Note This functionality is not available for the NBT server manager administrative interface Enhanced logging capabilities allow you to: * Use JMX interfaces to the server manager and the Web Tier to change their logging configuration, * Dynamically adjust levels of Teamcenter server debugging aids such as SQL. logging, journaling levels, and the levels of log entries reported by Teamcenter server code, 324 Teamconter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new For more information about using the server manager administrative interface, see the System Administration Guide Monitoring critical event data ‘The JOBE server manager administration interface allows administrators of four-tier environments to monitor critical event data and receive notification when critical events exceed specified thresholds, This information is useful for determining the cause of an issue, as well as allowing you to take corrective action. Monitoring is available for the: © Web tier © Teameenter server manager * Business logic server Note This functionality is not available for the NBT server manager administrative interface Web tier monitoring can be configured through the J2BE server manager administrative interface or by manually editing the webtierMonitorConfig.xml file, This file should be stored in the EAR file, application sever startup directory, or someplace on the application server classpath (allowing settings to be tailored to a machine if required. ) Server manager monitoring can be configured through the J2EE server manager administrative interface or by manually configuring the poolMonitorConfig.xml file in the TC_ROOT/pool_manager directory. Business logic server monitoring can be configured through the J2EE server manager administrative interface or by manually configuring the serverMonitorConfig.xml file in the TC_DATA directory. For more information about monitoring the Teamcenter server, see the System Administration Guide. Restarting warm servers Administrators can use the Restart Warm Servers button to recycle warm servers in all server manager pools without shutting down the server manager. This is usefull for updating cached values on a warm server. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 325Chapters What's new Example In a four-tier configuration, with Host A and Host B using a common ‘Teamcenter database Changes made to site preferences on Host A effect all existing Teamcenter server processes running on Host A. Because Host B caches preferences when it starts, the changes to site preferences are not received by Host B if it was ‘running when the changes are made through Host A. The changes are not received by Host B until it receives a new Teamcenter server. In a fourtier environment, the server manager can be configured with additional warm servers, ready for use by the next host to logon, Warm, servers cache preferences when they are started Ifwarm servers are configured, and Host B logs off and then logs on through a ‘warm server, it still does not receive the preference changes because the warm server cached the preference settings when it started. ‘To ensure that all hosts receive the latest information at logon, use the Restart Warm Servers button. This operation stops and restarts all warm servers, ensuring each warm server receives the latest preference settings. ‘This button is available in both the J2EE and the NET server manager administration interfaces For more information about using the button in the J2EE interface, see the System Administration Guide. For more information about using the button in the NBT interface, see the System Administration Guide. Configuration and reporting features added for managing license types ‘Teamcenter provides the capability of generating a license usage report based on usage by all Teamcenter. The license usage is recorded on a monthly basis. There are four new license preferences \_notifier_list * LicenseUsage_admi * LicenseUsage_days_warning level * LicenseUsage_hours warning level * LicenseUsage_show_userid_in_report For complete information about using the License Usage Audit Tool and the COTS Admin - License Usage report and the corresponding report style sheet to output usage reports in Microsoft Excel, see the System Administration Guide. For descriptions of the available license types, see your license agreement documentation. 2.28 Thamconter @1 Release Sulltin PLwp0001 1(01-037134-080)What's new NX Check-Mate and NX RDDV validation agent objects installed automatically NX Check-Mate and NX RDDV validation agent objects are now added automatically when you install Teameenter, They are also added when you upgrade your database if they do not already exist For more information, see the Validation Manager Guide Updating the backpointer table after upgrade In Teameenter 9.1, relation_type object references and ImanRelation primary and secondary object references are no longer stored in the backpointer table. They are stored only in the ImanRelation table. Note Where-referenced queries now search the ImanRelation table for ImanRelation references, rather than searching the backpointer table ‘This significant reduction in the size of the backpointer table can improve product performance, To take advantage of this performance improvement, sites upgrading from previous versions must run the new clean_backpointer utility on their ‘Teamcenter database after upgrade. ‘The utility scans the backpointer table for relation_type object references and ImanRelation primary and secondary object references, confirms their existence in the ImanRelation table, and deletes the instances from the backpointer table. Because the utility's cleanup operation may be time-consuming, this process is not run during the upgrade process. You must run this utility manually, after upgrade, to remove relation_type object references and ImanRelation primary and secondary object references from your upgraded database. For more information about updating the backpointer table, see the System Administration Guide. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 327Chapters What's new Cleaning the POM_TIMESTAMP table ‘Timestamps of modified objects are now stored in the new POM_TIMESTAMP table as well as the PPOM_OBJECT table, (Previously, this timestamp information was only stored in the larger PPOM_OBJECT table.) Storing timestamp records in the new table improves product performance. Bach time an object is modified during a Teamcenter session, a timestamp record is created. Typically, records older than the time specified by the ‘TC_TIMESTAMP_THRESHOLD environment variable are deleted from the table when a user logs off However, if an operation continues after a user logs off, or there is an error during the session, records remain in the table. ‘The table must be periodically cleaned of these accumulated records Specify how often the table is cleaned using the TC_TIMESTAMP_THRESHOLD environment variable. By default, this environment variable is set to 96 hours (four days), The optimum. cleaning time varies by site, Variables include how quickly table size grows at your site and user requirements. For example, if there are users at your site who must be logged on for many days consecutively, the setting must be increased. For more information about cleaning the POM_TIMESTAMP table, see the System Administration Guide. Enhance monitoring and logging of alll tiers through J2EE server manager ‘The Teamcenter logging and monitoring infrastructures support a notification mechanism based on JMX technology that provides: * Automatic metric and logger configuration changes. * Traceability of request processing through all tiers (client, Web, enterprise) using log correlation IDs. © Automatic collection of metrics for a specific alert. ‘You can enable logging of JMX notifications of alerts from Teamcenter and the alerts can automatically enable additional metrics or loggers when the alert occurs, The log correlation ID is extended to all tiers and logged to aid you in tracking the request flow across the tiers for troubleshooting purposes. JMX MBeans in the J2BE Server Manager and Web tier provide this feature. You can monitor and administer this feature using the Server Manager Administration interface (HTML adapter) or any third-party JMX administrative client, You can dynamically change the logging level for any active teserver process for the current session only. The settings in the logger.properties file are maintained and used in subsequent teserver sessions, For more information, see the System Administration Guide 3.28 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new System logging enhancements ‘A new logging system allows you to write information to the Teameenter system log (syslog) file. The system provides hierarchical loggers with configurable priority levels (FATAL, ERROR, WARN, INFO, DEBUG, TRACE). All system log files now contain the following standard fields: * Priority level © Date/time in UTC format © Log correlation ID of the client request © Enmor code (when applicable) * Message © Logger name * Caller‘s file and line number (if specified) ‘You must configure loggers to write messages of the desired priority levels, Loggers can be configured in the logger.properties XML file or using the server manager administrative interface. For more information about configuring system loggers, see the System Administration Guide. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 323Chapters What's new Base services File Management System logging and monitoring ‘The base JMX logging and monitoring capabilities of Teamcenter are extended to the base services File Management System (FMS) and dispatcher components. You can use this logging and monitoring information to identify the cause of an issue or critical event in a Teameenter distributed environment, You can: * Configure FMS monitoring using and XML configuration file or through an administrative interface. * Configure FMS to identify and respond to critical events * Configure the dispatcher to display critical and history data related to its job processing. For more information, see the System Administration Guide Password file argument available for POM utilities ‘The -pf argument can now be used with all published POM utilities that use the user, password, and group (-u, -p and -g) arguments, (This argument is mutually exclusive with the -p argument.) Previously, the -pf was available for most core utilities but not for POM utilities ‘The -pf argument provides enhanced password security by placing the unencrypted password in a text file that must be secured using operating system-level security. ‘This is stronger security than is provided by the -p argument, in which passwords are placed on the utility program command line, allowing a user to run ps -ef to display all running utilities and gain access to the utilities passwords Use the -pf argument to specify the name and location of the password file, The file must be 2 single-line ASCII file containing the password in clear text. If this argument is used without a value, or if for any reason the password cannot be retrieved, the system assumes a null value and uses the -u value to be the password ‘This argument is now available for the following POM utilities: * install * clearlocks * index_verifier * clean_backpointer For more information about managing password files for utilities, see the Utilities Reference 390 Thamcenter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Teamcenter supports Kerberos authentication ‘Teamcenter supports authentication using Kerberos protocol. Kerberos, a network authentication protocol, provides authentication for client/server applications by using secret-key cryptography. With the Kerberos protocol, a client, proves its identity to a server (and Vice versa) across an insecure network connection. Kerberos allows a user to be authenticated without sending the user's password over the network Instead, encrypted tickets derived from the password and secret Key information are sent over the network. For more information about Kerberos authentication, see Security Services Installation | Customization. Teamcenter supports applet-free authentication ‘Teameenter rich clients that use TCCS can connect to Teameenter Security Services without using a Web browser or session applet through applet-free signon. On Windows hosts, applet-free sign-on with Kerberos protocol provides zero sign-on functionality, which allows you to launch Teamcenter without encountering a logon form. In applet-free mode, the TOCS process challenges the user for credentials to create a Teameenter Security Services session, A Web browser is not launched at authentication, and there is no session applet window that is kept open to hold the session information, For this mode, the access to the Teamcenter Security Services Login Service requires HTTP 401-based authentication. Form-based authentication is not supported with this mode, A browser-based client cannot share an applet-free single sign-on session with rich clients, If a browser-based client is launched, the applet is instantiated and a second sign-on challenge appears For more information about applet-free mode, see Security Services Installation / Customization. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 3.34Chapters Using Teamcente! What's new iterfaces User interface changes to support the use of object IDs ‘The following changes are made to the rich client and thin client user interface framework: * Changed object ID display Previously, the item_id property alone was used to display an item ID. Now the object string (object_steing property) is displayed instead of the item_id property. The object string is based on the DisplayName business object constant assigned to each item type in the Business Modeler IDE. Administrators can use the DisplayName business object constant in the Business Modeler IDE to change how an object ID is displayed in the user interface, For more information about the Display Name business object constant, see the Business Modeler IDE Guide © Addition of custom columns In the rich client, the Open By Name dialog box is enhanced to allow end users to customize the columns displayed. The context menu includes the following new menu commands Remove this column Insert column(s) Save Column Configuration Apply a Column Configuration ‘To access the Open by Name dialog box in the rich client, in Structure Manager, click the Open by Name button in the bottom left corner of the perspective (You can also choose Tools—Manage Global Alternates and click the button to add the item as a global alternate, You can also access the Open by Name dialog box from My Teamcenter by clicking the arrow on the far right of the Impact Analysis tab menu.) For more information about the Open by Name dialog box, see the Structure Manager Guide. 292. Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new (esa ins (Gira) Object ag is aad ‘Owne| Enable Column Selection Copy Selected Data $1 cort < i Hh tutto Fitter ener search criteria and = Remove this column + Insert columns) Til Save Column Configuration Apply a Colurm Confguraton Print Table > Column management in the Open by Name dialog box In the thin client, a Configure button is added to the Find by Name dialog box, Clicking this button displays the Column Management dialog box, which allows users td insert or remove columns © Modified quick add box ‘The Structure Manager quick add box and its associated command button behavior is modified. This box appears at the bottom of the Structure Manager perspective, ‘The quick add box no longer validates each keystroke, Previously, as the user typed, the client checked if an item existed with the currently entered item ID. If'so, the + button was enabled; if not, the + button was disabled. Due to performance issues, this validation is no longer performed. The + button is always enabled and must be pressed to perform an action on the item ID entered, Ifyou click the + button and there are no matches for the entered text, the following dialog box appears PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 333Chapters What's now Glos 8 Quick add box. For more information about using the quick add box, see the Structure Manager Guide. Requirements management features in Client for Office ‘You can export a requirements structure to Microsoft Word, save the exported document to disk, and work on it while offline, You can check out the requirements structure when exporting, then add, modify, or delete requirements and their subtypes while offline. When you reconnect to Teamcenter, the changes are synchronized to the database and you can then check in the structure While offline, you can: * View the requirements structure. * Add and remove elements from the requirement structure loaded in Word, © Modify properties of requirements and subtypes. * View and edit requirement content * Move or re-parent objects in the structure. * Create new requirements and subtypes in Microsoft Word. Note While the Word document is offline and disconnected from Teameenter, you cannot: © Create trace links between objects. © Create new requirement specifications © Create workflow from requirements objects Find these enhancements in Microsoft Word on four-tier system configurations. Additional buttons are provided in the ribbon, and a requirements management tab is provided in the browse view For more information, see the Systems Engineering Guide, the Extensions for Microsoft Office Guide, and the Client for Microsoft Guide section of the Teamcenter 9 documentation release notes located in the Teamcenter 9.1 Release Bulletin. 394 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new ‘You can also export a live spreadsheet from the thin client as an alternative to exporting a static spreadsheet, Find this enhancement in My Teameenter and ‘Systems Engineering in the thin client when you choose Tools —-Export to Excel For more information, see the Thin Olient Interface Guide Note © The capabilities to work offfine and manage requirements in Word that were provided in previous version are merged as part of this enhancement © Requirements management features are optional when Client for Office is installed through its installation wizard. For more information about using the stand-alone installation wizard, see the Installation on Windows Clients Guide Optional feature selection in the Client for Office installer ‘Some features are optional in the Client for Office stand-alone installation wizard. * Optional features can be selected or bypassed in the Teamcenter wizard * Options include features for managing requirements through Client for Office. For more information about using the stand-alone installation wizard, see the Installation on Windows Clients Guide Using view networks in the rich client ‘The Teameenter rich client is based on the third-party Eclipse framework, Enhancements to the Eclipse framework allow you to do the following in the rich client: * Display multiple views of the same data, for example, to configure the same structure with different effectivities and compare the results in adjacent views. * Designate views as primary and secondary, according to the data they contain, ‘Typically, the administrator or rich client customizer performs these tasks. Users can establish or remove explicit associations between primary and secondary views * Reposition and resize views in the current session, You can also undock views and move them around the viewing area, © Save such networks of related views for retrieval in later sessions Note At this time, data in a view network is not restored when the view network is retrieved. * Reset your current desktop arrangement to the default as-saved state. * Use the Open With shortcut menu command to open selected objects in a new view PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 335Chapters What's new * Use the Reveal Related Views shortcut menu command to bring to the front all views that are associated with the selected view * Display composite tooltips that provide information about the primary or secondary view that is the source of the data shown in a view, * Display a list of most recently used views, ‘* Use colors and patterns to distinguish between related views ‘These enhancements are available only in selected applications that are implemented as Eclipse perspectives Other applications continue to function in the same way as in previous versions For more information about the rich client and view networks, see the Rich Client Interface Guide Using the rich client Launch Pad Note By default, the Launch Pad perspective is hidden and not available to the user unless an administrator removes if from the HiddenPerspectives preference value list, ‘The Launch Pad perspective provides a visual desktop to place items and notes, called nodes, for quick reference in either a carousel or grid display mode Nodes can be images, URLs, lists, and other Teamcenter data that has some relationship to the current context, with emphasis on Teameenter data that allows easy access to and visualization of relevant data. * In carousel mode, nodes are arranged in a circle with simulated depth, You can click and drag nodes to rotate nodes left or right to bring a new node forward to become the active node * Ingrid mode, nodes are arranged in rows and columns For information about using the Launch Pad perspective, see the Rich Client Interface Guide For information about customizing the Launch Pad perspective, see the Client Customization Programmer's Guide. Updates to the thin client user interface ‘The layout of the thin client user interface more closely resembles the rich client user interface © The menu bar is moved to the top of the thin client window. * Menu commands are reordered to be consistent with the rich client and respond in context to the currently selected object in the hierarchy and detail displays * Three panes are provided below the menu bar for navigation, component hierarchies, and data. 3.98 Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Context tools include: * Context menus with common actions available © Context toolbars, also with common actions available, Lists of values support includes: * Automatic completion is available to filter and select values © Interdependent and dependent LOVs are updated automatically based on current selections * Copy and paste, remove and delete, and view and open for typed and untyped references are available. ‘The default layout for thin client applications has a header bar containing menus and session information above three panes, arranged side-by-side © Navigation pane ‘The navigation pane is displayed on the left side of the Teamcenter window and is enhanced to work like the rich client navigation pane. You can expand and collapse the entire pane and pane groups, select what is displayed in primary and secondary areas, and configure the display of applications * Component pane ‘The component pane displays component hierarchies in a tree view and behaves like the component view in the rich client, You can resize this pane to be wider or narrower © Data pane ‘The data pane displays information in Overview, Details, Attached Files, Impact Analysis, and Viewer tabs You can configure the columns in the Details tab. Note Some thin client applications arrange the tree pane and the data pane horizontally. Users cannot change the layout configuration for a thin client application. Updates to thin client functionality ‘The thin client is enhanced in the following ways: * Streamlined dataset creation: o You can upload data files during dataset creation, © You can drag-and-drop files from operating system windows to the File field during dataset creation, * Enhanced object creation using the New® Recent menu command, This menu command displays recently created object types, * Greater consistency in business object creation dialog boxes PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 337Chapters What's new + Enhanced behavior for Save As operations. * Enhanced expansion for child objects includes relations represented by pseudofolders * Enhanced deployment resulting from updated proxy support and protocol switching * Support for viewing 2D images and 3D models in the Viewer view in My ‘Teameenter and Structure Manager. Available visualization capabilities inelude panning, zooming, and rotating 2D images and 3D models Note The thin client embedded viewer is enabled by default only if Teamcenter lifecycle visualization base is installed on the system. * The thin client workflow process viewer requires Adobe Flash Player installation. The Adobe Flash Player, which is used for rendering, replaces the ‘Adobe Scalable Vector Graphics (SVG) Viewer used in previous versions of ‘Teameenter, ‘The process viewer is supported by SVG Web for Internet Explorer and by native SVG for the Firefox and Safari browsers. For information about using the thin client, see the Thin Client Interface Guide. Office attribute exchange ‘Teamcenter provides attribute exchange between Microsoft Office files and ‘Teameenter objects. The Microsoft Office files are stored in Teamcenter as datasets in order for the exchange to work. There are two tasks for exchanging document properties: 1. Configure attribute exchange. 2. Perform attribute exchange. ‘You can configure attribute exchange mappings to a single dataset, The mappings are not applied to any other datasets unless this dataset is a part of an item revision document control (RDC) template, In that case, when a Teamcenter object is created with this IRDC template, the dataset is duplicated in the newly created object, 50 the attribute exchange mappings are applied. For more information about IRDC templates, see the Business Modeler IDE Guide. When you open and check out an Teamcenter dataset, Teameenter performs the attribute exchange and updates the Office file with the new attribute values from ‘Teameenter, When you save an Office file, Teameenter performs the attribute exchange and updates the Office file if needed and provides feedback of any invalid modification or failure. Attribute or document properties exchanged depend on the configured exchange direction For more information, see Client for Microsoft Office Guide. 3:98 Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Simple search for business objects ‘Teameenter introduces the Simple Search view that allows you to search by business object property values in the rich client, This search method provides an additional way to view results in the Search Results view. My Teamcenter in the rich client provides the following search mechanisms * The Search box, at the top of the navigation pane and in the Getting Started application, lets you perform a quick search and display results in a Quick Open Results dialog box. Search Enter RemID to seach J v ‘The quick search is based on a single criterion, such as item ID, keyword, item name, or dataset name, which you select from the menu. You can also select Advanced to display the Search view © The rich client Search A view and Simple Search ) view display results in a Search Results * view 0 The Search “ view lets you use queries created in the Query Builder application to search Teamcenter databases for metadata and full-text search indexes. o The Simple Search “4 view, lets you create searches based on business object property values. Note For information about using the Simple Search view, see the Rich Client Interface Guide. Markup disposition ‘Markup Manager allows you to add dispositions on marlups and generate a report, ‘You can’ 1. Create, update and delete disposition comments for markups 2, Seta status on dispositions. Valid status values are: + ‘5.None + Flaccepted + Ficancelled + completed + '© opened + Fi Rejected PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 333Chapters What's new For more information, see Client for Microsoft Office Guide. Viewer view framework enhancements ‘The framework for the Viewer view in the rich client is enhanced. The viewer framework uses preferences to configure the Viewer view to traverse the data model and present a viewer for the selected business object type. When an object is selected in the rich client, the preference configuration is read and the correct target viewer is presented. For information about how to use preferences to configure the Viewer view, see the My Teamcenter Guide. For information about how to define a custom viewer, see the Client Customization Programmer's Guide Thin client XRT style sheet enhancements ‘The thin client summary data pane more closely resembles the rich client Summary view by supporting configuration of the displayed information through their shared eXtensible Markup Language (XML) Rendering Template (XRT) style sheets, For information about the thin client data pane, see the Thin Olient Interface Guide For the thin client summary data pane, customizers define groupings of related ‘Teameenter objects (object sets) using XRT style sheet configuration, Object sets can include: * Data views ‘Users can switch between list, table, and thumbnail views of object set information * Command buttons Object set command buttons let the user perform actions in the context of the data grouping Users can perform actions such as Add, Cut, and Copy in an object set Note For information about creating object sets, see the Client Custom Programmer's Guide 240. Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new ig changes and workflows Replicating workflow templates Ifyou have a Multi-Site configuration, you can replicate your workflow templates, including those under construction, on several Teameenter sites by using the data_share utility and update them with the data_syne utility. You cannot edit the replicas, only the template at the owning site, Also, handlers attached to the templates must exist at all sites where the templates are replicated For more information, see the Workflow Designer Guide EPM_multiple_processes_targets preference default value is ON ‘The default value for the EPM_multiple_peocesses_targets preference is now ON. This allows multiple processes for the same objects. Prior to Teameenter 8.2, the default value was OFF For more information, see the Preferences and Environment Variables Reference. Support for penetration requests in Issue Manager Within the standard Issue Manager interface, you can now view and manage requests for the penetration of structures that were generated in NX For example, you can view and search for the penetration requests. For more information, see the Issue Manager Guide PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 3.44Chapters What's now Managing content, reports, and schedules Creating custom visual reports ‘You can create and define custom visual reports which require complex logic to compute results using Report Builder, These reports run in the NX Visual Client. ‘The complex logic required to compute results is implemented using custom methods, To help you create the custom visual reports, sample visual reports are provided in the TC_ROOT/sample/visualrepoct folder For more information, see the Report Builder Guide ‘The following visual reports are provided: * Overall Status in Change Process ‘Shows status of parts currently in a change process. Colors all parts according to their overall status in a change process © Overall Status in Workflow ‘Shows status of parts currently in a workflow process, Colors all parts according to their overall status in workflow. * Affected by Problem Report ‘Shows parts that are affected by a specified problem report, Colors all parts that are affected by the specified problem report by its relationship ta the specified problem report, * Affected by Change Request ‘Shows parts that are affected by a specified change request. Colors all parts that are affected by the specified change request by its relationship to the specified change request. * Affected by Change Notice ‘Shows parts that are affected by a specified change notice, Colors all parts that are affected by the specified change notice by its relationship to the specified change notice. * Has Higher Revision ‘Shows parts that have higher revisions Colors all parts that have higher revisions than the one that is currently configured in the visual reporting client. 242. Thamconter @1 Release Sulltin PLwp0001 1(01-037134-080)What's new * Rule Evaluation Result ‘Shows parts that satisfy a specified validation rule ItemRevision, Colors all parts whose validation results do not satisfy the specified validation rule + Check-Mate Result ‘Shows parts that have Check-Mate results. Colors all parts according to their Check-Mate overall result. This report is not available in Report Builder To use this report, import the TC_9_0.00_VR_RPT_VAL_RESULT.xml file into Teamcenter using the import _export_reports utility. * Requirements Validation status Shows parts that have not fulfilled all their requirements. Colors all parts according to the requirement validation status. This report is not available in Report Builder To use this report, import the TC_9_0_00_VR_RPT_REQ VAL_STATUS.xml file into Teameenter using the import_export_ceports utility. Embedded dashboard A dashboard application is added to Teamcenter which shows contents of the ‘Teameenter Reporting and Analytics (TeRA) dashboard. For more information, see the Report Builder Guide View reports based on office templates ‘You can view reports which have Microsoft Office templates attached to the report definition object. If the Office Live feature is enabled, you can also see the report, content in the live mode. For more information, see the Report Builder Guide Customizing status indicators A new column displays status indicators ‘This new column displays in the tree table of a program view and Schedule Manager application Use the six icons already provided in Teamcenter for status indicators or use the status indicators options screen to customize the status indicators For more information, see the Schedule Manager Guide. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 3.43Chapters What's now Viewing the new state column A new column displays state. ‘This new column displays in the task execution view, Schedule Manager tree table, program view tree table, properties dialog, My Tasks dialog, or from the task details tab on the Timesheets dialog State values are set relative to the status values, as follows * The Not Started state has the same status value. * The In Progress state has three possible status values: © In Progress o Late o Needs Attention * The Complete state has the same status value. © The Closed state has the Abandoned status value. For more information, see the Schedule Manager Guide. Updating a schedule without saving it to the database ‘You can enter into a deferred session and lock the schedule in the Schedule Manager application, You can do multiple updates to the schedule without saving it to the database, While working in this deferred mode, most changes are not saved to the database until you save or cancel the operation. Live operations include: Costing, Schedule Membership, and Schedule Task Deliverables. While you are in deferred mode, other users see the schedule is locked by you. ‘To specify the time-out in minutes before the deferred session expires, set the SM_DEFERRED_TIMEOUT preference, Time-out is optional. ‘To specify the notification time in minutes before you are warned that the deferred session is about to expire, set the SM_DEFERRED_NOTIFICATION TIME preference ‘To specify whether the timer button is displayed or not, set the SM_DEFERRED_SHOW_TIMEOUT preference, For more information about working in a deferred session in the Schedule Manager application, see the Schedule Manager Guide. 244 Thamcenter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new Loading partial schedules for quicker access ‘You can load partial schedules for quicker access to your information. ‘To enable partial schedule reload, set the SM_Structure_Partial_Context preference For more information about this preference, see the Preferences and Environment Variables Reference For more information about loading partial schedules in Schedule Manager, see the Schedule Manager Guide Creating a Program View without creating a dataset ‘To create a program view, you no longer have to create a dataset first, A new wizard helps you quickly create and configure a program view. The wizard makes it easy to: * Choose the properties you want to see * Select multiple schedules ‘+ Import a previously exported dataset, ‘To specify available schedule attributes in the column chooser of the program view, set the ScheduleAvailableAttributes preference ‘To specify available schedule task attributes in the column chooser of the program view, set the ScheduleTaskAvailableAttributes preference For more information about these preferences, see the Preferences and Environment Variables Reference For more information about using program views in Schedule Manager, see the ‘Schedule Manager Guide Updating execution data for schedule tasks ‘To quickly update execution data for a task in My Teamcenter, use the Schedule Task Execution view Set the SM_EXEC_VIEW_PROPERTIES preference to specify the properties displayed in the Schedule Task Execution view and the order in which they are displayed. For information about the Schedule Task Execution view, see the Schedule Manager Guide PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 3.45Chapters What's new Creating dependencies across multiple schedules ‘You can create dependencies between tasks in different schedules, including the top-level summary tasks in the Schedule Manager application. These schedules may be part of the same master schedule or in entirely separate schedules For information about creating cross-sthedule dependencies, see the Schedule Manager Guide. Schedule Manager enhancements ‘Schedule Manager functionality is enhanced in the following ways * Allows customers to use the Business Modeler IDE to define custom statuses and custom rules affecting statuses, For more information, see the Business Modeler IDE Guide and the Schedule Manager Guide. * Adds the capability to import and export scheduling data using PLM XML Export Import Administration. For more information, see the Schedule Manager Guide * Adds services and IT APIs for basic Schedule Manager functionality. For more information about Schedule Manager services, see the Services Reference in the Teameenter HTML Help Collection, For more information about Schedule Manager ITKs, see the Integration Tool hit Function Reference 248. Thamconter @1 Reloage Sulltin PLwp0001 1(01-037134-080)What's new Content Management re-ent eering Content Management has been re-engineered to eliminate the Web application server and enable the Content Management rich client to work directly with ‘Teamcenter objects and the Teameenter server, The re-engineering has improved the performance of the Content Management application. ‘The interface includes the following: * The Content Management perspective provides the functionality for managing both author and administrative data in Content Management, * The Publication Structure view is used to navigate, create, and maintain the structure of a publication with XML or SGML components * The Preview view displays the published content of an XML or SGML. publication. * The Summary view displays the property information of the selected object. * When a component is selected in the Home component view or the Publication Structure view, the Details view displays the objects at the level below the selected object, which may be system objects used to support the selected object. * The Impact Analysis view provides graphical where-used and where-referenced search capabilities Content Management enhancements enable you to) © Manage content for versions 2.3 and 4.0 of the $1000D standard. * Create objects, perform searches, and manage item revisions with standard ‘Teameenter features. © Manage languages and graphic priority lists using the Organization application. * Export and import Content Management administration data using the PLM XML Export Import function, * Set user permissions using Access Manager * Perform application administration functions, such as setting preferences, using standard Teameenter features. * Publish content through a publishing server using Teameenter Dispatcher. For more information, see the Content Management Guide PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 3.87Chapters Systems Eni What's new eering New Systems Engineering and Requirements Management perspective ‘The new Systems Engineering perspective allows you to perform many of the tasks that are available in standalone Systems Engineering and Requirements Management, The Requirements Manager application provided in previous versions is replaced with the Requirement view in the Systems Engineering perspective ‘New Diagram, Notes, Budget, and Trace link views are provided ‘The Systems Engineering perspective includes the following features © Save and recall views ‘You can save the current structure view, including column names, width, and filter, Multiple views can be saved with different names, A saved view can be recalled for a future session, The saved view can also be applied when you export the structure to Microsoft Excel. * Publish column configuration An administrator with a DBA role can save column configurations and publish them for other users. The publish action converts the administrator's configuration preferences to site-level preferences. © Define and apply a filter ‘You can optionally filter the structure using values shown in the structure Microsoft Bxcel-like filtering capabilities are provided by two columns, one containing a conditional value (for example, = or contains) and the other a default control (for example, All, Blank, or Non-Blank). For example, you can filter the structure by an item name equal to a specified value, Parent lines not matching the filter are unavailable. * Revise multiple objects ‘You can revise multiple selected objects in a single action. In previous versions, you could only revise one object at a time, Likewise, you can submit multiple objects to a workflow * Update common modifiable properties ‘You can select multiple items or item revisions, and then update common modifiable properties in one action, Each modified value is applied to all selected objects The objects may be of different types For more information about these enhancements, see the Systems Engineering Guide, Function view ‘The new Systems Engineering perspective includes a Funetion view for functional modeling, allowing you to create and manage functions in a similar way to product (physical) and requirements structures. The process of creating a functional model is sometimes referred to as functional decomposition 248° Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new ‘The Funetion view is synchronized with the Diagram view, described in Diagram view, Changes made in one view are reflected in the other view automatically. ‘The Function view allows you to create, reuse, and delete * Functions © Interfaces ‘You can also set the direction of and move interfaces, © Connections © Nonconnection relations For more information about the Funetion view, see the Systems Engineering Guide Requirements management enhancements ‘The following usability enhancements are made to the management of requirements * Creating derived requirements ‘You can create a derived requirement from another requirement, Teameenter associates the derived requirement with the original requirement using a trace link. * Creating objects with one click ‘You can create requirements structures rapidly with the Quick Create view Required properties are populated with preconfigured values, * Using Microsoft Windows shortcut commands ‘You can navigate requirements structures and create requirements objects using Microsoft Windows shortcut keys, for example, Page Up and Page Down. © Deep copy a structure ‘You can duplicate an existing requirements structure to a selected level. This enhancement behaves in a similar way to the deep copy feature in Structure ‘Manager. © Reorganizing requirements structures ‘You can rearrange the structure using Move Up, Move Down, Promote, and Demote commands Teamcenter updates the Number property for structure lines to match the modified sequence. You can also rearrange the structure by editing the Number property directly. * Showing multiline text ‘You can optionally configure the structure tree to show multiple lines of text, for example, allowing you to enter longer item descriptions * Navigating to the Teamcenter object ‘You can select an object in the where-used, trace link, or diagram view, and then choose Go to. The selected object is highlighted in the structure PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 3.43Chapters What's now * Identifying trace links and attachments with icons, Unique icons are provided in the requirements structure to allow easy identification of trace links and attachments, Placing your cursor over one of these icons displays a tooltip with detailed information. * Checking objects in or out automatically Objects are checked in or out automatically when you update their properties. * Adding references to supporting information When working with requirements in Microsoft Word, you can paste reference links to image files, JT files, and Excel spreadsheets You can click a reference link to go to the Teamcenter dataset, © Comparing requirements ‘You can compare two different versions of the same requirements structure or two different structures. * Viewing the requirements structure in Relation Browser ‘You can expand, collapse, and print the requirements structure from Relation Browser, © Applying variants to a requirements structure ‘You can create variant rules and apply them to filter the structure elements in or out, You can apply the variant rules when you export a structure to Microsoft Word or Excel © Managing markups ‘You can use Microsoft Word to add comments to a requirement, paragraph, or note, You can add comments when connected to Teamcenter or when working offline. Multiple users can use Markup Manager to view your comments © Importing an existing specification When you import a specification that already exists in Teameenter, the existing information is updated, rather than overwritten * Using properties in headers and footers ‘You can select a specification, requirement, or paragraph, and then substitute the values in the header and ‘oter of an exported document. For more information, see the Systems Engineering Guide and the Client for Microsoft Office Guide 360. Thamconter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Requirements management features in Client for Office ‘You can export a requirements structure to Microsoft Office Word, save the exported document to disk, and work on it while offine, You can check out the requirements structure when exporting, then add, modify, or delete requirements and their subtypes while offline, When you reconnect to Teameentey, the changes are synchronized to the database and you can then check in the structure While offline, you can: * View the requirements structure. * Add and remove elements from the requirement structure loaded in Word, © Modify properties of requirements and subtypes. * View and edit requirement content * Move or re-parent objects in the structure. * Create new requirements and subtypes in Microsoft Word. Note While the Word document is offline and disconnected from Teameenter, you cannot: © Create trace links between objects. © Create new requirement specifications © Create workflow from requirements objects Find these enhancements in Microsoft Word on four-tier system configurations. Additional buttons are provided in the ribbon, and a requirements management tab is provided in the browse view For more information, see the Systems Engineering Guide, the Extensions for Microsoft Office Guide, and the Client for Microsoft Guide section of the Teamcenter 9 documentation release notes located in the Teamcenter 9.1 Release Bulletin. ‘You can also export a live spreadsheet from the thin client as an alternative to exporting a static spreadsheet, Find this enhancement in My Teameenter and ‘Systems Engineering in the thin client when you choose Tools —-Export to Excel For more information, see the Thin Client Interface Guide. Note © The capabilities to work offline and manage requirements in Word that were provided in previous versions are merged as part of this enhancement, * Requirements management features are optional when Client for Office is installed through the Teamcenter MSI installer, Optional features can be selected or bypassed in the installer, PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 354Chapters What's new Duplicating requirement specification structures This feature allows you to make an identical copy of a requirement specification structure or substructure, placing the copy in your Teamcenter clipboard. You can then paste the copy in the Systems Engineering Requirement view to create a new structure, Note Trace links in the source structure are preserved in the copy. ‘You can select either of the following * The requirement specification at the peal level of the structure * A requirement at any level below the peak ‘Then, you choose File—-Duplicate to display the Duplicate dialog box, in which the selected object becomes the root item. In the dialog box, you can select one of the following for duplication: * The root item and all lower level items. * Only the root item, with lower level items being referenced but not duplicated. * Items in the projects to which the root item belongs Also, you can assign the duplicated items to selected projects, using the lists in the Duplicate dialog box * Projects to which the root item is assigned and for which you have access privileges (displayed by default) * Projects for which you have access privileges and that are available for assignment to the root item ‘You can add available projects to the list of assigned projects, and you can remove assigned projects from that list. For more information, see the Systems Engineering Guide 362. Thamcenter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new Trace link enhancements A trace link establishes a directional relationship between two objects, for example, a requirement and the part that satisfies the requirement. The following enhancements are made to the creation and analysis of trace links © Creating and managing trace links in-context ‘You can define an in-context BOM line (absolute occurrence) as the source or destination object. You can connect a workspace object and an absolute occurrence with 2 trace link. ‘You can create in-context trace links within a product structure, a manufacturing structure, or between the two structures Similarly, you create in-context trace links between the requirements structure and the other two structures, For example, you may want to associate a requirement with a connection in the context of one of its interfaces The requirement is not satisfied by the connection in the context of its other interface, therefore this trace lini must be added in the correct context, © Revising item revisions with trace links Ifyou revise an item revision with a trace link, Teameenter carries forward the trace link to the new revision according to the current revision rule. Ifyou move an absolute occurrence that has a trace link attached within the same context, Teamcenter also moves the trace link If you move an absolute occurrence to’a different context, the trace link is not preserved Ifyou baseline a structure containing trace links, the trace links are captured and are visible if you reopen the baseline and apply the relevant revision rule, * Running trace reports ‘You can select multiple objects and run a trace report. For each selected object, the report shows the defining and complying trace links and also the corresponding source or destination. You can export saved trace reports to Microsoft Excel * Run accountability checks against requirements ‘The existing accountability check mechanism is incorporated in Systems Engineering You can run accountability checks between a requirements structure and a process structure, a part structure, or a product structure. This allows you to identify if all requirements are satisfied in the product and manufacturing structures * Viewing trace links in Relation Browser Ifyou open a workspace object or an absolute occurrence in Relation Browser, you see the trace link and any secondary object. For more information about these enhancements, see the Systems Engineering Guide, PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 353Chapters What's new Diagram view ‘The Systems Engineering perspective includes a Diagram view for Microsoft Office Visio diagramming, which allows you to * Create and edit diagram stencils. A diagram stencil defines the content and application domain for individual diagrams. It holds information about the diagram members, relations, and the application domain for a diagram. It has an associated Visio template file that holds the stencil or the collection of shapes applicable for an application domain. Stencils are typically created by Teamcenter administrators but may be created by other users, * Create diagrams A diagram is the graphical representation of a function and its underlying structure, using the relevant membership and relationship rules. A diagram is based on a diagram stencil, which supplies the membership and relationship rules for the diagram. The membership rule determines the set of related objects that appears on each diagram created from the stencil * Save diagrams in the Teamcenter database. * Open and close diagrams from the associated function. ‘The Diagram view allows you to create, remove, delete, and restore * Functions Create a function by dragging the shape associated with the function class onto the Visio diagram, This action creates a function object in Teamcenter and an occurrence of it under the root object of the diagram, © Interfaces Create an interface object by dragging the shape associated with the interface class onto the function shape on the Visio diagram. This action creates an interface object in Teameenter and an occurrence of it under the selected funetion object © Connections Create a connection object by dragging the shape associated with the connection class from the Visio stencil onto the Visio diagram, You can then glue the connection shape endpoints to the glue points on the function shapes or interface shapes on the Visio diagram. © Nonconnection relations Create a nonconnection relation by dragging the shape representing a trace link. onto the Visio diagram and attaching it to the glue points of the two shapes you want to relate. 354 Thamconter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new ‘You can also add a function or connection that occurs outside the functional structure ofa diagram to the diagram using copy and paste actions This view is synchronized with the functional modeling view, described in Function view, Changes made in one view are reflected in the other view automatically. For example, you can edit properties in Visio and the changes are reflected in the functional modeling view. You can also jump directly from a Visio diagram to the corresponding object in the functional modeling view For more information about the Visio diagramming view, see the Systems Engineering Guide, For information about creating templates, see the Application Administration Guide. Note ‘To use this feature, you must install Visio 2007 (Standard or Professional) on the client machine, Support for later versions of Visio is provided in a future version of Teamcenter. Currently, the Visio diagramming view can only be associated with the Systems Engineering perspective, In future versions, it is possible to associate it with other perspectives Budgets ‘You can create and manage budgets in a requirements structure. Budget information may include the cost of an assembly, the weight of an assembly, or the product's total power consumption, ‘The Systems Engineering perspective includes a Budget view that allows you to * Create a budget definition. Create a budget and associate it with the structure. You can specify an expression to roll leaf level values up to the top level of the structure © Export a budget to Excel Export budget values to Excel to perform complex calculations that are not possible in Teamcenter, for example, to derive the estimated cost and the actual cost of an assembly. If you modify Excel cell values, you can save the changes back to Teameenter, * View budget values, View existing budget values and modify the rollup expression. * Remove a budget from structure Delete instances of a particular budget definition from the structure, This action does not remove the budget from the system entirely. For more information about budgets, see the Systems Engineering Guide PLwp0001 1(01-037134-080) ‘Teamconter 9.1 Release Bulletin 385Chapters What's new Migration from Systems Engineering and Requirements Management ‘You can migrate existing standalone Systems Engineering and Requirements Management requirements data to Teamcenter Systems Engineering The migration process uses the third-party Altova Mapforce tool to map the elements of the Systems Engineering and Requirements Management schema to Teamcenter Systems Engineering A sample project, mapping schema, and sample mapping are provided on the installation media to assist you with configuring the migration process. ‘The following elements can be migrated: * Requirements and paragraphs, including subtypes, rich text, and properties Only latest working revisions of these elements are migrated. * Folders. * Internal trace links + Notes * Change approvals to Teamcenter custom notes * Groups to Teameenter folders No other elements are migrated, including building blocks, ports, connections, MATLAB models, diagrams, spreadsheets, change logs, shortcuts, and proxy objects. ‘You must re-create any supporting data manually in Teamcenter, including object templates, document templates, document stylesheets, Excel templates, search scripts, saved views, Visio templates, and users. For more information, see the Data Exchange Guide and the Business Modeler IDE Guide Data dictionary ‘The new data dictionary functionality is a central repository of data (building blocks and components) that you can create and search based on a given criteria and reuse it in multiple designs across projects. Once you have created your data dictionary, you can set it up asa library, define access rights, and add signals. You can further ‘manage the dictionary by modifying or deleting it as required Key applications that work with data dictionary include, Classification Administration, Teamcenter Project, Structure Manager, and Systems Engineering and Requirements Management, For more information about managing data dictionaries, see Getting Started with Mechatronics Process Management, Systems Engineering Guide, and Classification Administration Guide. 258. Thamcenter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new Behavior Modeling tool integration and MATLAB integration ‘Teamcenter provides a framework for integration with behavior modeling tools, With this integration, you can use the behavior modeling tool for model authoring and Teameenter for model management and leverage other Teamcenter benefits. As part of this integration framework, Teamcenter supports integration with MATLAB Simulink MATLAB Simulink allows you to create models of dynamic and embedded systems using predefined blocks, You can also simulate the behavior of your models and view the results of the simulation using Simulink Using this integration, you can open, save, insert, check-out, check-in and revise models that are located in Teamcenter from the Matlab Simulink application, For more information, see the Behavior Modeling Tool Integration Guide Hierarchical numbering of requirements in Systems Engineering A new property, Number, automatically shows each requirements level and sequence within a requirement specification structure. For example, assume that requirements A, B, and C occupy the first level, directly under the requirement, specification object, Also, each requirement has three children at the next lower level. In this example, the Number column values are: * 1 for requirement A, with 1.1, 1.2, and 13 for its children © 2 for requirement 5, with 2.1, 2.2, and 23 for its children * 3 for requirement C, with 8.1, 3.2, and 3.3 for its children ‘The Number column values are adjusted automatically when users do any of the following * Move requirements up and down within their current levels. * Promote and demote requirements to higher and lower levels * Add or remove requirements in the structure. For more information, see the Systems Engineering Guide PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 357Chapters What's new Excel report access Excel report access through URLS When you export Teamcenter object data to Microsoft Office Excel, you can place the export file's URL in your Windows Clipboard. You can then paste the URL into an e-mail message, for example, and send the message to recipients such as your manager or colleagues, Recipients can access the export file, which can serve as a report on a selected object, by clicking the URL. If you generate the export file in live Excel, recipients also can modify the data in Teamcenter directly from the report, It is not necessary for recipients to run the Teamcenter rich client, ‘You can export the objects from + My Teameenter © Multi-Structure Manager * Systems Engineering * Structure Manager * The Details view in any perspective 358° Thamcenter @1 Reloage Bulletin PLwp0001 1(01-037134-080)What's new Generate an Excel report and its URL 1. Select the object to export, Caution Do not select multiple objects 2 Doone of the following to display the Export to Excel dialog box: In My Teamcenter, Multi-Structure Manager, Systems Engineering, or ‘Structure Manager, choose ToolsExport—-Objects to Excel In the Details view, click the Export Objects to Excel button on the toolbar. 3. In the Export to Excel dialog box, select the options for the export. PLwp0001 1(01-037134-080) Under Output, select one of the following: © Static Snapshot generates a standard Excel file, without Teamcenter live Excel capability. © Live integration with Excel (Interactive) generates a live Excel file from which you can edit Teamcenter data in real time while the Teameenter client is running Live integration with Excel (Bulk mode) generates a live Excel file in which you can accumulate changes and later connect the file to the ‘Teameenter server, at which time the changes are applied in Teamcenter Caution Do not select Work Offline and Import Under Output Template: a Select Use Excel Template to activate the template list b, In the list, select the template that specifies the data that you want to export, Caution ‘Do not select Export All Visible Columns. Note © Depending on the perspective or view from which you displayed the dialog box, some options may not appear or may occur in a different order * Ifyou displayed the dialog box from the Details view, select Export Selected Objects under Object Selection Caution ‘Do not select Export All Objects in View. ‘Teamconter 9.1 Releage Sulltin 259Chapters 4 What's new Click Generate URL Note © Generate URL is unavailable if you selected more than one object to export. © Generate URL becomes unavailable when you select any of the following dialog box options © Work Offline and Import 0 Export All Visible Columns 0 Export All Objects in View One or more of these options may not appear, depending on the perspective or view from which you displayed the dialog box, ‘The export file is generated and the URL Generated message is displayed, confirming that the URL is in your Windows Clipboard and showing the URL details Access an Excel report through its URL 1 Click the URL, Note For example, you may receive the URL in an e-mail message from a subordinate. Or, the URL may be inserted in an Office document that is, attached to a message or stored on a shared drive, ‘The Teamcenter Login page is displayed. Enter your Teamcenter user name and password. ‘The report opens in a new Excel window. 260. Thamcenter @1 Release Bulletin PLwp0001 1(01-037134-080)What's new Live Excel and live Word options Live Excel and live Word options for resolving edit conflicts When a user exports objects to live Excel or live Word without checking them out, other users can modify the same objects after the export file is generated, Through the TC_setProperties site preference, the exporting user can be warned of edit conflicts and given options for resolution. Depending on the TC_setProperties preference value, the following options can be presented when the user saves changes in the export file: * Overwrite another user's changes, saving all changes to Teamcenter * Discard the changes that conflict with another user's, saving all other changes to ‘Teameenter, * Caneel all changes made in the export file. For more information, see TO_setProperties. PLwp0001 1(01-037134-080) ‘Teamconter 91 Release Bulletin 364