Tc14.2.0.0 README
Tc14.2.0.0 README
Tc14.2.0.0 README
Teamcenter 14.2.0.0
Contents
2 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2 INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 Deprecation announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4 Obsolescence announcements: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 RELEASE NOTES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Service Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 INTRODUCTION
Tc14.0.0.0 is the base version (major release) of the Tc14.0..0 product. Future patches against this release stream will
be cumulative.
Problem Report (PR) corrections are indicated in the Tcrelease-level_README.CSV file provided with this kit.
Technical Documentation updates, submitted too late to be included in the normal Documentation, may be included in
this README.
You can also install Teamcenter help on your local network. See the Siemens Documentation Installer on Support
Center.
Siemens distributes the following software images for the Teamcenter 14.0.0.0 release:
Teamcenter is translated into the following language locales on all server-supported platforms:
Chinese (Simplified)
Chinese (Traditional)
Czech
English
French
German
Italian
Japanese
Korean
Polish
Portuguese (Brazilian)
Russian
Spanish
2.2 INSTALLATION
Installation:
For installation / Upgrade instructions, reference the appropriate Documentation located on Support Center:
Teamcenter Upgrade
Deployment Center:
Starting with Teamcenter 13.0 and Active Workspace 5.0 (Teamcenter 13.0), the respective kits for these releases
(hosted on Support Center) will contain the Deployment Center installer in them. The Deployment Center installer can be
found under the install\DeploymentCenter\ directory in these kits. This installer corresponds to latest version of
Deployment Center. The same Deployment Center version is also posted as a separate download on the Support Center
site to accommodate pre 13.x/5.x releases.
To find which versions of Teamcenter can be upgraded to Teamcenter 14.x, reference the Teamcenter Interoperability
(Compatibility) Matrix located under the Teamcenter Support White Pages on Support Center.
https://support.sw.siemens.com/en-US/product/282219420/download/PL20200617155641511
If your initial environment is not supported for direct upgrade to Teamcenter 14.x, you must upgrade to a supported initial
version, and then upgrade to Teamcenter 14.x.
For information about versions of operating systems, third-party software, and Teamcenter software that are certified for
your platform,
Reference the following Document located on Support Center : Teamcenter Hardware and Software Certifications
https://support.sw.siemens.com/en-US/product/282219420/knowledge-base/PL8017193
The Teamcenter Hardware and Software Certifications document, on Support Center, describes versions of operating
systems and third-party software certified for use with Teamcenter:
Certified software has been tested by Siemens to ensure its compatibility with Teamcenter. Third-party software includes
databases, compilers, web browsers, and other software used with Teamcenter.
Siemens recommends using only certified operating systems and third-party software, but if you use software versions
that are not certified, be aware of the following considerations:
● Earlier versions
3 | Page Polarion ALM 21 R2 2022-11-22 09:21
Lifecycle Collaboration Software Program
Teamcenter 14.2 README (rev. 16923128)
Although Teamcenter may run using earlier software versions than those certified, we strongly discourage using earlier
versions, and we do not provide support for doing so.
● Later versions
Siemens makes a reasonable effort to support Teamcenter on later operating systems and software, and works with
customers to resolve compatibility issues. However, we usually do not test adequately to immediately certify the later
version.
Operating systems
Operating system manufacturers typically assure run-time binary compatibility between successive versions of their
operating systems. Some assure compatibility when relinking or rebuilding executables and libraries with later versions
of compilers.
To determine Teamcenter compatibility with operating systems and compilers, Siemens tests:
If later versions of compilers are not compatible with earlier versions, you must link all Teamcenter customizations using
the compiler version certified for the Teamcenter release. This also applies to installation of Teamcenter patches.
Software
If a software manufacturer guarantees that a later version of its product is binary-compatible with the preceding version,
Siemens expects Teamcenter to function properly with the later version. Our experience has found few problems running
Teamcenter with software versions later than those certified.
If Siemens discovers incompatible versions of third-party software, we post Software Field Bulletins (SFBs) on Support
Center. This information is also available from your Teamcenter provider.
Support Center is the vehicle for Teamcenter communication. It provides a single repository of current, accurate, version-
controlled Teamcenter information that is accessible through the Internet by authorized users. Maintained within Support
Center is a wealth of information for the diverse mix of customers and employees in the Teamcenter community.
Information in Support Center includes, but is not limited to, the following:
● Enhancement requests
● Patches
● Shareware customizations
Support Center can be accessed from the Siemens website or directly through its web server at the following website:
https://support.sw.siemens.com/en-US
You must have a valid account to access Support Center. To register for a new account, go to:
https://support.sw.siemens.com/register
4 | Page Polarion ALM 21 R2 2022-11-22 09:21
Lifecycle Collaboration Software Program
Teamcenter 14.2 README (rev. 16923128)
Your Support Center account is your single point of authentication which allows customers to access product information
and associated support tools
See: SFB-TEAMCENTER-8007006
The Lifecycle Collaboration Software (LCS) business segment is implementing a 2 year End of Standard Maintenance
(EoSM) policy for the Teamcenter Platform and Teamcenter Applications.
This means that patches will only be provided for a given Teamcenter release during the 2 years following its release
date.
Customers using a Teamcenter release that has passed its EoSM date are able to receive PLM Support and
have rights to upgrade to future releases, provided that they are under a current Maintenance,
Enhancement, and Support (ME&S) contract.
Definitions:
Standard ME&S:
Siemens provides full ME&S, giving customers the right to maintenance releases and patches, upgrades to new
releases, and PLM Support
Date when Siemens no longer provides maintenance releases and patches for the given software release.
Customers may still upgrade to new releases and access PLM Support
Issues may be submitted but are evaluated against the latest software release. Any required corrections are
delivered within a software release under Standard ME&S or a future release
Effectivity:
This policy applies to Major (e.g. 12) and Point releases (12.1, 12.2, etc) and is in effect for all Teamcenter product
releases from 11.3 onward and includes equivalent Active Workspace product releases.
All dates will be maintained on Support, in a single document, and updated as new releases are planned.
The document will be located on Support Center under the "Teamcenter Support White Papers Certification" section
Titled:
Teamcenter_EoSM_Schedule_<date>
https://support.sw.siemens.com/en-US/product/282219420/download/PL20200617155641511
SUPPORT ANNOUNCEMENTS
3 Deprecation announcements
As Siemens PLM Software enhances Teamcenter, some features are deprecated or obsoleted.
● Obsolete features are either removed from Teamcenter or may be removed without further notice.
If a feature you use is deprecated, read the deprecation announcement to learn of any replacement feature. Migrate to
the replacement feature as soon as possible to avoid problems when the deprecated feature becomes obsolete.
Description: CAPA Schedule and CAPA Forms were deprecated in the Teamcenter 12.4 release. The cpa0_migrate
_capa_schedulemigration utility was provided to migrate the existing data.
The below objects are no longer supported in Problem Solving (earlier known as CAPA) and will not be created in
Teamcenter 14.0 and later:
CAPA Schedules
C2Containment
C2Corrective
C2Investigation
C2Preventive
C2Verification
CAPA Forms
C2CapaResolution
C2CapaCause
Replacement -
Description: The following table summarizes the methods that are deprecated from the classes defined in com.teamce
nter.rac.kernel plugin. The equivalent SOA operations can be used as a replacement for these methods.
public void setAttributes( String solvername, String analysistype, String solutiontype, TCComponentCA
String solutionstep, TCComponentCAEAnalysisRevision analysisRev ) EAnalysisRevision
Type
public TCComponentCAEAnalysis create( String item_id, String revid, String type, String TCComponentCA
name, String description, TCComponentForm itemMasterForm, TCComponentForm EAnalysisType
itemRevMasterForm )
public void setRelations( String primaryItemID, String primaryItemRevID, String RelationT TCComponentCA
ypes, int numIRsOfEachRelationType, String secondaryItemIDs, String secondaryItemRe EItemRevisionType
vIDs )
) uctureMapRevisio
nType
Replacement You can use equivalent SOA operations for the deprecated methods.
Description: The script upgrade_preferences_file.pl helped customers to migrate their custom preference files to the
new format starting Tc10.1. Today we do not support Tc10.1. The upgrade path Tc10.x -> Tc14.x is also not supported.
Description: The legacy code associated with the RACcom.teamcenter.rac.cae.ase plugin is deprecated and will
Replacement If you want to use the Simulation Process Data Management functionality, use com.teamcenter.rac.tcsim.*
plugins.
Description: The following legacy business objects are no longer used by Teamcenter Simulation. They are deprecated
in Teamcenter 14.2 and will be fully obsoleted in Teamcenter 16.0.
CAEBCItem None
CAEBCItemRevision None
CAEConnItem None
CAEConnItemRevision None
CAELoadItem None
CAELoadItemRevision None
CAEAttachmentWindow None
Replacement You can use the artifacts as documented by the Simulation Process Data Management functionality.
4 Obsolescence announcements:
Starting wiTeamcenter Visualization 15.0, VisView Convert & Print support for processing
PostScript files will be obsoleted
This notice is to inform customers that starting with Teamcenter (Visualization) 15.0 VisView convert &
Print, we will no longer support processing PostScript files.
Siemens Digital Industries Software will continue to support processing PostScript files through
Teamcenter Visualization VisView Convert & Print 13.x and 14.x series per the standard Teamcenter
deprecation policy. After the deprecation period, the processing of PostScript files will be obsoleted and
removed from the product
5 RELEASE NOTES
Administration
Release Note Title: Teamcenter Management Console command line Error and Warning messages Release Note: To
increase security, the Management Console has been updated to use Jetty 9.4.48 version for Teamcenter
14.2. Changes in the newer Jetty 9.4.48 result in additional error and warning messages in the Jetty command window
regarding the module path of the Management Console application. These error and warning messages can be
completely ignored.
For example:
How to work around or avoid: No workaround needed. These messages do not reflect an actual security weakness
and do not affect functionality.
Service Dispatcher
Release Note Title: TLS less than version 1.2 disabled for Service Dispatcher use on Windows server Release Note: T
o reduce security risk, use of TLS versions prior to version 1.2 is disabled by default for the microservice framework
service dispatcher running on a Windows host. Use of TLS versions prior to 1.2 can be re-enabled if desired.
How to work around or avoid: For a microservice node hosted on Windows and running Service Dispatcher, to allow
Service Dispatcher to use a TLS less than version 1.2, do the following:
Example:
# Protocols to exclude
# This is a comma-separated string, with no spaces.
# Example:
# excludeProtocols=TLSv1,TLSv1.1
excludeProtocols=TLSv1,TLSv1.1
How to work around or avoid: The solution to this issue is to use Java11 for the Web tier. If for some reason
Java11 cannot be used for the web tier, the JVM option -Dkeystore.pkcs12.legacy may be set in the
jwt_config_tool (generate_keystore.bat) or may be set before starting Deployment Center. The option
configures the java keytool to generate backwards-compatible .p12 files.
Example for generate_keystore.bat:
"%JAVA_HOME%binjava" -Dkeystore.pkcs12.legacy -cp "lib*"
com.teamcenter.jwt.tools.JwtConfigTool %1
Example for Deployment Center (dcserver.bat):
start %DC_WINDOW_TITLE% /SEPARATE "%DC_JAVA_HOME%binjava" -
Dkeystore.pkcs12.legacy -DDC_LOG_DIR="%DC_SERVER_DIR%logs" -
DDCDB_URL=%DCDB_URL% -Djava.library.path="%DC_SERVER_DIR%nativelibs" -cp
"%DC_SERVER_DIR%/shared_libraries/;%JETTY_HOME%/"
org.eclipse.jetty.start.Main
General
Release Note Title: Configuration change needed on Windows 11 to launch Notepad Application for text datasets from
Teamcenter Release Note: In Windows 11, the Windows Notepad application is converted to a Universal Windows
Platform (UWP) app. Teamcenter does not currently support launching this type of application. Additional steps are
required to enable Teamcenter to launch text datasets with Notepad in Windows 11. How to work around or avoid: To
enable launching of text datasets from Teamcenter with Notepad in Windows 11, update the Windows registry using the
following steps.
Configuration
Release Note Title: Changes to default values of preferences in Teamcenter Product Configurator Release Note: The
default values of the following preferences are changed in Teamcenter 14.2 release:
Preference Name Old Default New Default New Default Used in Used in Overri
Value Value after value after AW? RAC? de
Upgrade New
Installation
Cfg0EnableFreeFormRuleSupport False True True NA Yes Yes
These default preferences values are applicable only for new installations. Changing the default value should not
affect existing customers when an upgrade is performed.
NOTE: In the Override column of the table, the new values of the preferences for those marked as Yes (highlighted
in yellow color) are applicable for both upgrade and fresh installation scenarios. However, for the rest of the
preferences, the new values are applicable only for fresh installation scenarios.
1. Download the Fixed Version from Microsoft’s Download the WebView2 Runtime site.
2. Decompress the WebView2 Runtime package using the command-line command expand {path to the package} -
F: {path to the destination folder} or by using a decompression tool such as WinRAR. Avoid decompressing
through File Explorer. It may not generate the correct folder structure.
3. Include all the decompressed Fixed Version binaries in your app package, for deployment on the target machine
during your app's installation.
4. Use the org.eclipse.swt.browser.EdgeDir system property to set the directory of the fixed version of WebView2.
Visualization
Release Note Title: Teamcenter Visualization: 2D File Format Deprecation Notice Release Note: This notice is to
inform customers that starting with Teamcenter Visualization 2312 (previously referred to as TcVis15.0), we will no
longer support the 2D file formats listed in the table below.
Siemens Digital Industries Software will continue to support these 2D file formats through Teamcenter lifecycle
visualization 13.x and Teamcenter lifecycle visualization 14.x series per the standard Teamcenter deprecation policy.
After the deprecation period, these file formats will be obsoleted and removed from the product. How to work around
or avoid: N/A
For a listing of the closed problem reports, see the Tc14.2.0.0_README.CSV file.
To report any serious problems about this product, please contact PLM Support:
· Phone:
- Outside the United States and Canada: Contact your local support office.
· Web:
- You can also log incident reports on the Web at: https://support.sw.siemens.com/en-US