Teamcenter Upgrade Guide. Publication Number PLM00129 H

Transcription

1 Teamcenter 10.1 Upgrade Guide Publication Number PLM00129 H

2 Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management Software Inc 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 Inc. 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 Upgrade Guide PLM00129 H

3 Contents Proprietary and restricted rights notice Getting started with Teamcenter upgrade Getting started with Teamcenter upgrade Supported upgrades Release information System requirements Enabling Teamcenter installation Interfaces: Teamcenter installation tools Basic concepts about Teamcenter upgrade Preparing the Teamcenter network Obtain a Teamcenter license file Install the licensing server Upgrading database servers Upgrading a Teamcenter corporate server Upgrade overview Prepare the corporate server for upgrade Upgrade a template project to the current data model format Upgrade a test system Upgrade volume servers Upgrade production systems Complete the upgrade Upgrading Teamcenter clients Upgrading a two-tier rich client Upgrading a four-tier rich client Upgrading Teamcenter Express or Teamcenter Rapid Start to Teamcenter Overview Upgrade Teamcenter Express 9.1 to Teamcenter Upgrade Teamcenter Rapid Start 10.1 to Teamcenter Troubleshooting A-1 Using the upgrade log viewer A-1 Troubleshooting Teamcenter upgrade A-3 Glossary B-1 Index Index-1 PLM00129 H Upgrade Guide 3

4 Contents Figures Tables Teamcenter Environment Manager Web Application Manager Access Manager rule tree example Teamcenter release bulletins Platform support for Teamcenter servers and clients Required hard disk space for Teamcenter configurations Upgrade Guide PLM00129 H

5 Chapter 1 Getting started with Teamcenter upgrade Getting started with Teamcenter upgrade Supported upgrades Release information System requirements Where to find system requirements Platforms System hardware Database Web browser Java Runtime Environment Web tier support Software integrations Enabling Teamcenter installation Locate Teamcenter distribution images Interfaces: Teamcenter installation tools Teamcenter Environment Manager Web Application Manager Basic concepts about Teamcenter upgrade Templates How templates are supplied Loading templates Upgrade Database Features panel Business Modeler IDE PLM00129 H Upgrade Guide

6

7 Chapter 1 Getting started with Teamcenter upgrade Getting started with Teamcenter upgrade This guide describes how to upgrade installations of Teamcenter to Teamcenter This includes upgrade of the Teamcenter Web tier and two-tier and four-tier rich clients. This guide assumes you have a thorough working knowledge of your operating system and general knowledge of Teamcenter use. Supported upgrades Teamcenter 10.1 supports upgrades from Teamcenter 8 and all later versions and MPs. This includes: Teamcenter 8 and all MP versions Teamcenter 8.1 through 8.3 and all MP versions Teamcenter 9.1 and all MP versions. To upgrade from earlier versions, you must first upgrade to one of these supported versions, and then upgrade to Teamcenter Release information Before you begin upgrading, read the following documentation deliverables to learn about new features in Teamcenter 10.1 and issues that may affect your upgrade: What s New Contains information about new features in Teamcenter Teamcenter 10.1 Release Bulletin Contains release notes and other information about issues that may affect your upgrade. In addition, read the release bulletins for all Teamcenter versions since your current Teamcenter version level to learn about new features and issues that may affect your upgrade. These release bulletins are available on GTAC: PLM00129 H Upgrade Guide 1-1

8 Chapter 1 Getting started with Teamcenter upgrade Teamcenter release bulletins Title Teamcenter 9.1 Release Bulletin Teamcenter 8.3 Release Bulletin Teamcenter 8 MP1 Release Bulletin 1 Location docs/teamcenter/9.1/pdf/pdf/tc_9_1_release_bulletin.pdf docs/teamcenter/8.3/pdf/pdf/tc_8_3_release_bulletin.pdf docs/teamcenter/8/en/pdf/pdf/tc_8_release_bulletin.pdf Note You must have a WebKey account to access GTAC. System requirements Where to find system requirements For information about versions of operating systems, third-party software, Teamcenter software, and system hardware certified for your platform, see the Siemens PLM Software Certification Database: certification/teamcenter.shtml Note Some software requirements differ for non-english locales. When viewing the certification database, make sure you note any exceptions for your locale. Platforms Determine from the following table which Teamcenter 10.1 servers and clients are supported on your operating system. Bullet characters ( ) denote supported servers and clients. 1. Includes release notes and new feature information for Teamcenter 8 and Teamcenter 8 MP Upgrade Guide PLM00129 H

9 Getting started with Teamcenter upgrade Platform support for Teamcenter servers and clients Operating System Corporate server Web tier Rich client Thin client Business Modeler IDE client TCCS 2 Microsoft Windows (desktop platforms) 3 Microsoft Windows (server platforms) 4 Sun Solaris Hewlett-Packard HP-UX 5 IBM AIX SUSE Linux Red Hat Linux 6 Apple Macintosh Mac OS Notes about platform support General notes For information about versions of operating systems certified for Teamcenter 10.1, see the Siemens PLM Software Certification Database. If your Teamcenter database server is IBM DB2, all Teamcenter servers and two-tier rich clients in your network must run operating systems supported for Teamcenter with IBM DB2. IBM DB2 databases are supported only with Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE Linux platforms. Teamcenter installation tools (Teamcenter Environment Manager and Web Application Manager) require the ISO character set. Make sure this character set is available on your host. If you are uncertain or want to verify this character set, see Verify required character set. Microsoft Windows Make sure the C:\Temp directory exists, and grant full access permissions to this directory for all users. 2. Teamcenter client communication system (TCCS) is installed with the rich client. This column refers to the stand-alone TCCS application. 3. Microsoft Windows desktop platforms include Windows XP and Windows 7.For information about installing Teamcenter on Windows clients, see the Installation on Windows Clients Guide. 4. Microsoft Windows server platforms include Windows Server Itanium platforms only. PA-RISC hardware is not supported. 6. Only 64-bit Red Hat Linux is supported. PLM00129 H Upgrade Guide 1-3

10 Chapter 1 Getting started with Teamcenter upgrade On Windows Server and Windows 7, disable Windows User Account Control (UAC) before you install Teamcenter. This option is available in the Control Panel User Accounts dialog box. Windows UAC can interfere with Teamcenter installation programs. Siemens PLM Software recommends turning off UAC for administrative users only. For more information, see Microsoft Windows documentation. Disable the Windows TCP scaling feature. Open a command prompt and enter the following command: netsh interface tcp set global autotuninglevel=disabled Siemens PLM Software recommends setting this parameter before installing Teamcenter because most client network infrastructures use one or more switches or routers. By default, Windows enables TCP window scaling, but some routers do not support this feature. This can cause installation failures that are difficult to diagnose and correct. For more information, see Microsoft Windows documentation. Teamcenter applications are provided in 32-bit and 64-bit versions. Use the appropriate Teamcenter software distribution image for your platform. If you use a nonnative language operating system version of Windows, you must install and enable the Multilingual User Interface (MUI) pack to ensure the language font is displayed properly. 1. Download and install the MUI pack for Windows from Microsoft. 2. Open the Regional and Language Options dialog box in the Windows Control Panel. 3. In the Languages tab, set the required language for the menus and dialogs. 4. In the Advanced tab and the Regional Options tab, set the required language. Sun Solaris Teamcenter executables are 64-bit applications. Teamcenter 10.1 is supported only on 64-bit Solaris. Hewlett-Packard HP-UX Teamcenter is supported on HP-UX on Itanium platforms only. No Teamcenter servers or clients are supported on HP-UX PA-RISC platforms. Hewlett-Packard HP-UX systems require special configuration to support Java. You must perform these steps to enable Teamcenter clients and installation tools on HP-UX systems. For more information, see the Hewlett-Packard guidelines at the following URL: 1-4 Upgrade Guide PLM00129 H

11 Getting started with Teamcenter upgrade IBM AIX The 64-bit IBM AIX platform is supported for Teamcenter server processes. Linux Make sure Linux host names do not exceed 31 characters in length. Host names longer than 31 characters cause Teamcenter corporate server installation to fail during saving of the POM schema file in the TC_DATA directory. Note Teamcenter installation tools do not require fully qualified domain names for host names. If your fully qualified domain name exceeds 31 characters, use the server short host name instead. For more information, see the GTAC solutions document on GTAC. On Linux systems, make sure your system is set to use the ISO character set rather than the default UTF-8 character set. Teamcenter installation tools require this setting. System hardware Make sure your Teamcenter host has the required amount of disk space available. Required hard disk space for Teamcenter configurations shows the required disk space for the following common Teamcenter configurations: Corporate server The corporate server contains the features included in the Corporate Server solution in Teamcenter Environment Manager (TEM). Additional features may require additional disk space. For more information, see the appropriate server installation guide (for Windows or UNIX/Linux). Two-tier rich client The two-tier rich client contains the features included in the Rich Client 2-tier solution in Teamcenter Environment Manager (TEM). Additional features may require additional disk space. For more information, see the appropriate Teamcenter client installation guide (for Windows or Linux). Web tier The Web tier includes the Web Application Manager, a distribution server, and a distribution server instance that contains the Over-the-Web installer and Rich Client 4-tier solutions. Additional solutions may require additional disk space. For more information, see the appropriate server installation guide (for Windows or UNIX/Linux). PLM00129 H Upgrade Guide 1-5

12 Chapter 1 Getting started with Teamcenter upgrade Required hard disk space for Teamcenter configurations Platform Corporate server Two-tier rich client Web tier Hewlett-Packard HP-UX GB Not supported 3 GB IBM AIX 2.0 GB Not supported 3 GB SUSE Linux 2.0 GB 300 MB 3 GB Red Hat Linux 2.0 GB 300 MB 3 GB Sun Solaris 2.5 GB Not supported 3 GB Microsoft Windows 1.5 GB 450 MB 4.5 GB Database Teamcenter requires a relational database management system (RDBMS) for storing Teamcenter data. Before you install a Teamcenter, you must install an IBM DB2, Oracle, or Microsoft SQL Server database server and make sure your Teamcenter corporate server host has access to the server. For information about supported database server versions, see the certification database: certification/teamcenter.shtml Choose a database management system that suits the platforms of your Teamcenter servers and clients. When planning your network, consider the following limitations: Teamcenter servers and two-tier rich clients on UNIX or Linux hosts cannot connect to Microsoft SQL Server database servers. If your Teamcenter database server is IBM DB2, all Teamcenter servers and two-tier rich clients in your network must run operating systems supported for Teamcenter with IBM DB2. IBM DB2 databases are supported only with Teamcenter servers running on Microsoft Windows, IBM AIX, or SUSE Linux platforms. For information about installing a database server for Teamcenter, see Upgrading database servers. Web browser The Teamcenter thin client and Over-the-Web Installer 8 require a Web browser. Teamcenter 10.1 supports the following Web browsers: The Teamcenter thin client requires a Web browser. Teamcenter 10.1 supports the following Web browsers: 7. Itanium platforms only. PA-RISC hardware is not supported. 8. The Over-the-Web Installer installs the four-tier Teamcenter rich client and Teamcenter Microsoft Office interfaces. 1-6 Upgrade Guide PLM00129 H

13 Getting started with Teamcenter upgrade Windows systems: Microsoft Internet Explorer and Mozilla Firefox Linux systems: Mozilla Firefox Macintosh systems: Apple Safari For information about versions supported, see the Siemens PLM Software Certification Database. Java Runtime Environment Teamcenter Environment Manager (TEM) requires a supported Java Runtime Environment (JRE). You must download and install the required JRE before you install Teamcenter. For information about required versions of the JRE for Teamcenter, see the Siemens PLM Software certification database: certification/teamcenter.shtml TEM verifies the required version of Java is available on the host. If the required version is not present, TEM does not launch. Before you launch TEM to install Teamcenter, specify the location of the JRE by one of the following methods: Set the appropriate environment variable on your host: o o Note 32-bit Java Set the JRE_HOME environment variable to the location of the 32-bit Java JRE. 64-bit Java Set the JRE64_HOME environment variable to the location of the 64-bit Java JRE. You must use the appropriate Teamcenter software distribution image (32-bit or 64-bit) for the JRE you use. Use the -jre argument to specify the JRE location when you launch TEM from a command prompt: tem jre JRE-path For example: tem jre c:\apps\jre1.7 TEM stores the JRE location during Teamcenter installation. After installation is complete, TEM no longer requires the JRE_HOME or JRE64_HOME environment variable or the -jre argument. Web tier support Install the required software for the Teamcenter Web tier you use: J2EE Web tier PLM00129 H Upgrade Guide 1-7

14 Chapter 1 Getting started with Teamcenter upgrade Java Runtime Environment (JRE) Install a supported JRE on the host where you build Teamcenter Web applications. J2EE application server Install a supported application server on the host where you deploy Teamcenter Web applications..net Web tier Microsoft Internet Information Server (IIS) Install IIS on your Teamcenter corporate server host. Microsoft.NET framework Install the.net framework on all Teamcenter hosts. For supported versions of these products, see the certification database: certification/teamcenter.shtml If you use the Teamcenter J2EE Web tier, install the following software: Java Runtime Environment (JRE) Install a supported JRE on the host where you build Teamcenter Web applications. J2EE application server Install a supported J2EE application server on the host where you deploy Teamcenter Web applications. For supported versions of these products, see the certification database: certification/teamcenter.shtml Note Some Web application servers require special configuration for use with Teamcenter. For more information, see the Web Application Deployment Guide. Software integrations If you use Teamcenter 10.1 integrations to other Siemens PLM Software products or third-party software, install those products before you install Teamcenter Some Siemens PLM Software products require separate licenses from your Siemens PLM Software representative. Siemens PLM Software products are licensed using the Siemens PLM Software Common Licensing Server. For more information about the Common Licensing Server, see Install the licensing server. 1-8 Upgrade Guide PLM00129 H

15 Getting started with Teamcenter upgrade Enabling Teamcenter installation Locate Teamcenter distribution images Locate the Teamcenter software and documentation distribution images and make sure they are accessible to your client host. Note Teamcenter software distribution images can contain multiple ZIP files. For example, the software distribution image for Windows consists of two files named Tcn_win_1_of_2.zip and Tcn_win_2_of_2.zip. If you download software distribution images for Teamcenter, you must download all files in the set to obtain the complete image. After you download files, expand all ZIP files to a common directory to assemble the image before you begin installation. Note Teamcenter software distribution images can contain multiple ZIP files. For example, the software distribution image for Windows consists of two files named Tcn_win_1_of_2.zip and Tcn_win_2_of_2.zip. If you download software distribution images for Teamcenter, you must download all files in the set to obtain the complete image. After you download files, extract all ZIP files to a common directory to assemble the image before you begin installation. If you mount the Teamcenter software distribution image on a remote NFS server, you must launch Teamcenter Environment Manager on the local server node. Interfaces: Teamcenter installation tools Teamcenter installation tools (Teamcenter Environment Manager and the Web Application Manager) enable you to build and manage your Teamcenter installation. Teamcenter Environment Manager Teamcenter Environment Manager is a tool that installs Teamcenter servers and two-tier and four-tier rich clients. PLM00129 H Upgrade Guide 1-9

16 Chapter 1 Getting started with Teamcenter upgrade Teamcenter Environment Manager Teamcenter Environment Manager also performs maintenance operations, such as upgrading servers, applying maintenance packs, and installing patches. You launch Teamcenter Environment Manager using the tem.bat command (Windows systems) or the tem.sh command (UNIX and Linux systems). Web Application Manager The Web Application Manager is a tool that installs thin client and rich client solutions and builds Teamcenter J2EE Web applications Upgrade Guide PLM00129 H

17 Getting started with Teamcenter upgrade Web Application Manager You launch the Web Application Manager by entering the insweb command. The Web Application Manager allows you to create multiple Web applications that contain different sets of Teamcenter solutions. This enables you to create Web applications for different groups of users in your network. Your Web applications can access the same Teamcenter corporate server, but provide different subsets of Teamcenter functionality. The Web Application Manager creates separate staging locations and separate deployable files 9 for each Web application. Some Teamcenter solutions require other solutions and some solutions may not be combined with other solutions in the same Web application. For more information about using the Web Application Manager, see the appropriate server installation guide (for Windows or UNIX/Linux). Note The.NET Web tier is installed using Teamcenter Environment Manager, not the Web Application Manager. Basic concepts about Teamcenter upgrade The Teamcenter 10.1 upgrade process employs the Business Modeler IDE and database templates. It is important to be familiar with these concepts before you begin upgrading your Teamcenter installation. 9. A deployable file is a Web archive (WAR) or enterprise archive (EAR) file, depending on the solutions it contains. PLM00129 H Upgrade Guide 1-11

18 Chapter 1 Getting started with Teamcenter upgrade Templates A template is a container that holds data model definitions. A template can contain any number of business objects, classes, lists of values, and business rules. Any Teamcenter feature that adds definitions to the data model has an associated template. In addition, templates can be supplied to you from another Teamcenter site, partner, or third party. Caution You must have access to all templates used at your site before beginning the upgrade of the corporate server. This is very important. During the corporate server upgrade, you load all templates used by your site. Templates can only be loaded during the upgrade of the corporate server. They cannot be loaded after the upgrade. Failing to load all templates your site depends on causes problems in managing the data model and can result in loss of data, time, and money. How templates are supplied Templates are supplied by: The Teamcenter software distribution image Software distribution images for asynchronous Teamcenter releases and integrations Other Teamcenter sites, partners, or third parties Templates supplied on the Teamcenter software distribution image Teamcenter supplies templates to organize sets of definitions for specific industries, applications, or functional areas. Examples of templates provided by Teamcenter are Teamcenter Foundation and Wire Harness Configuration. These templates are available in the software distribution image (the installation DVD or downloaded image). For example, the Teamcenter Foundation feature and the Wire Harness Configuration feature are both installed using the software distribution image, both add definitions to the data model, and both have associated templates found in the distribution image. Templates supplied by asynchronous Teamcenter releases Some Teamcenter features are released asynchronously and are distributed separately from the Teamcenter software distribution image (the installation DVD or downloaded image) and are found on their own distribution image. An example is the CATIA integration. Templates supplied by other Teamcenter sites, partners, or third parties You can use templates created by other sites, partners, or third parties. Loading templates Before you upgrade the corporate server, you must have access to all templates on which your site depends Upgrade Guide PLM00129 H

19 Getting started with Teamcenter upgrade Templates supplied by Teamcenter on the installation kit are automatically detected by Teamcenter Environment Manager (TEM) and loaded during the upgrade. Templates supplied asynchronously by Teamcenter must be detected and loaded during the upgrade of the corporate server. This is done using the Upgrade Database Features panel in TEM during the upgrade. You must have access to these templates before beginning the corporate server upgrade. Therefore, you cannot begin your upgrade until all asynchronous features that you use are released. Templates supplied by another Teamcenter site, partner, or third party must be loaded manually during the upgrade of the corporate server. This is done using the Upgrade Database Features panel in TEM during the upgrade. You must have access to these templates before beginning the corporate server upgrade. Upgrade Database Features panel Templates are loaded into your environment during your corporate server upgrade using the Upgrade Database Features panel in TEM. All features available from the distribution image are listed. Those that you have not installed are grayed-out. Templates supplied by Teamcenter asynchronous from the kit, templates supplied by another site, partner, or third party are not listed in the Upgrade Database Features panel until you manually load them. Click the Browse button and select the templates. After you select the template, it is listed in the Upgrade Database Feature panel. Business Modeler IDE The Business Modeler IDE (Integrated Development Environment) is a tool for customizing the data model of your Teamcenter installation. Use the IDE to create business objects, classes, attributes, lists of values (LOVs), and rules. The Business Modeler IDE is built on top of the Eclipse platform. Eclipse is a generic platform for tool development that is extended via its plug-in and extension point technology. You can install the Business Modeler IDE two ways: As a stand-alone application This method installs the Eclipse platform. As part of an existing Eclipse environment PLM00129 H Upgrade Guide 1-13

20

21 Chapter 2 Preparing the Teamcenter network Obtain a Teamcenter license file Install the licensing server Upgrading database servers Upgrading database servers Configuring character settings in non-english locales Overview of shell limits and parameters Set AIX shell limits Set AIX system parameters Set AIX kernel parameters Set HP-UX kernel parameters Set Solaris kernel parameters Set SUSE Linux shell limits Upgrade an Oracle server and database Export an Oracle database Terminate Oracle sessions on Windows systems Stop the listener process Shut down an Oracle database Terminate Oracle sessions on UNIX and Linux systems Back up an Oracle installation Upgrading the Oracle server Upgrade using the Oracle installer Upgrade by uninstalling/reinstalling Oracle Upgrade Microsoft SQL Server databases PLM00129 H Upgrade Guide

22

23 Chapter 2 Preparing the Teamcenter network Obtain a Teamcenter license file To obtain a Teamcenter license file, you must provide the composite host ID of your Teamcenter license server host. A composite host ID (CID) is a unique identifier used as the host ID on the SERVER line of the license file. It is distinguished from the default FlexNet host ID by the COMPOSITE keyword. It is the host ID that associates a permanent license file with a specific server. When the CID is used as the license server host ID, the SERVER line reads as follows: SERVER servera COMPOSITE=37B5ED1AC61D To obtain a composite host ID for your license server, run the getcid utility on your license server host. Download this utility from GTAC: 1. Open the GTAC Web site: 2. Click License ManagementfiDownload CID Utility. 3. On the Download CID Utility page, click NX and Other Products. 4. On the FTP site, click the directory corresponding to the platform type of your license server, for example, wntx On the resulting page, download the getcid.exe utility (Windows systems) or the getcid utility (UNIX/Linux systems). Run the getcid utility on the target license server (or on all three servers in a redundant configuration). The utility provides the CID for license server as a 12-digit hexadecimal number. For example: $ getcid.exe The Siemens PLM Software licensing composite hostid is: COMPOSITE=37B5ED1AC61D After you obtain the CID, enter it into your customer record to generate a permanent license file. You can enter your CID using either your WebKey account or by calling your customer services representative. After the CID is entered into your customer record, you are sent a permanent license file to install on your license server. For more information about installing the Siemens PLM License Server, see Install the licensing server. PLM00129 H Upgrade Guide 2-1

24 Chapter 2 Preparing the Teamcenter network Install the licensing server Before you upgrade to Teamcenter 10.1, you must install the Siemens PLM License Server to distribute licenses to Teamcenter hosts. Even if you already use the Common Licensing Server with your current version of Teamcenter, you must install the version of the licensing server provided with Teamcenter The Siemens PLM License Server daemon, ugslmd, enforces license usage. Teamcenter 10.1 employs named user licensing, which ties each user in the system to an available license and ensures the total number of active licenses of each type in the system is always less than or equal to the number of licenses purchased. For descriptions of the available license types, see your license agreement documentation. For information about using the make_user utility with the -licenselevel argument to change license levels, see the System Administration Guide. This procedure assumes you have obtained a Teamcenter license file as described in Obtain a Teamcenter license file. Install the ugslmd license daemon: 1. Obtain a Teamcenter 10.1 license file from Siemens PLM Software. Save the license file in a directory accessible to the license server host. This procedure assumes the license file is named tc.lic, but you may give the license file any name you choose. Note If you choose to install Teamcenter using a temporary license file, edit the temporary license file to reflect your designated Teamcenter corporate server host. a. Open the license file in a plain text editor and locate the following line in the file: SERVER YourHostname ANY b. Replace YourHostname with the host name of the designated license server host. Update your Siemens PLM Software customer service representative with your license server host information. c. Save the changes to the license file. Siemens PLM Software recommends you do not change the license server port from its default value ( ) unless it is necessary to resolve a port conflict. Record the host name and port for the license server. Teamcenter Environment Manager (TEM) prompts you for these values during Teamcenter server installation. 2. Set the SPLM_LICENSE_SERVER environment variable to the following value on the designated Teamcenter corporate server host: 1. Port is registered for the Siemens PLM License Server with the Internet Assigned Numbers Authority (IANA). For more information, see Upgrade Guide PLM00129 H

25 Preparing the Teamcenter network Replace port with the port number and host with the host name of the license server, for example, The port and host values must match those you specified in the SERVER line of the Teamcenter license file. 3. Set the TCP_NODELAY environment variable to 1 on the licensing server host. This helps optimize logon time when launching Teamcenter. 4. Change to the additional_applications directory in the Teamcenter software distribution image. 5. Copy the Siemens PLM License Server installation program (SPLMLicenseServer_version_setup.exe/bin) to a temporary directory on your local hard drive. 6. Launch the Siemens PLM License Server installation program: Windows systems: a. Launch the SPLMLicenseServer_version_setup.exe program. b. During license server installation, enter the following values: Destination location for the license server Location of the Teamcenter license file (tc.lic) When the installation is complete, the license server installation program starts the license daemon (ugslmd). UNIX/Linux systems: a. Launch the SPLMLicenseServer_version_setup.bin program. b. Open the ugslicensing_install.ans file and edit the contents to specify the destination directory and path to the Teamcenter license file. c. Execute the ugslicensing_install command. Caution The Siemens PLM License Server must be running and two or more seats must be available on that license server during Teamcenter server installation. Otherwise, database creation fails because the make_user utility cannot create the required users in the database. For more information, see the Installing Siemens PLM Software Licensing for UNIX, Installing Siemens PLM Software Licensing for Windows, and Siemens PLM Common Licensing User Guide documents in the additional_documentation directory on the Teamcenter 10.1 documentation distribution image. PLM00129 H Upgrade Guide 2-3

26 Chapter 2 Preparing the Teamcenter network Upgrading database servers Upgrading database servers If your database server version is not a version certified for Teamcenter 10.1, you must upgrade your database server before you upgrade Teamcenter. Siemens PLM Software supports Teamcenter 10.1 with IBM DB2, Oracle, and Microsoft SQL Server databases. For information about supported versions of IBM DB2, Oracle, and Microsoft SQL Server, see the Siemens PLM Software Certification Database: certification/teamcenter.shtml Configuring character settings in non-english locales To ensure correct display and processing of Teamcenter data, you must set required values in your system environment and your Teamcenter configuration. If your Teamcenter servers run UNIX or Linux and use the Unicode UTF-8 character set, you must configure your operating system and your Teamcenter configuration to use Unicode UTF-8, observing the following considerations during Teamcenter upgrade: An existing Teamcenter installation must not configure Unicode UTF-8 character set support with an upgrade to Teamcenter An existing Teamcenter installation is required to complete an upgrade to Teamcenter 10.1 under its existing database character set encoding. After upgrade is completed, you must contact your database vendor for processes and tools to convert your existing database character set encoded data to Unicode UTF-8 character set encoded data for storage to a new database. For more information about environment settings for your locale, platform, and character set, see the following topics: For information about environment settings for non-utf-8 UNIX and Linux systems, see the Installation on UNIX and Linux Servers Guide. For information about environment settings for UTF-8 UNIX and Linux systems, see the Installation on UNIX and Linux Servers Guide. For information about environment settings for Windows systems, see the Installation on Windows Servers Guide. Overview of shell limits and parameters If you use Oracle on a UNIX or Linux server, set shell limits and parameters as required for Teamcenter Oracle RDBMS extensively uses UNIX resources such as shared memory, swap memory, and semaphore for interprocess communication. Insufficient parameter settings cause problems during installation and instance startup. The greater the amount of data stored in memory, the faster a database operates. In addition, by maintaining data in memory, the UNIX kernel reduces disk I/O activity. 2-4 Upgrade Guide PLM00129 H

27 Preparing the Teamcenter network On all UNIX and Linux platforms supported for Teamcenter 10.1, set the process memory size (the ulimit user environment parameter) to unlimited before installing Oracle. To avoid errors during installation, or operation errors after installation, review kernel parameter settings to ensure that they meet the recommended Oracle settings described in the following sections. The recommended kernel parameter settings are for a typical Oracle database environment. If you previously tuned kernel parameters to levels that meet other application needs, continue to use those values. Initially, you can set kernel parameters as described in the Oracle documentation. For some operating systems, kernel parameters may need adjustment according to available system memory. The Oracle installation program issues warnings if kernel parameters do not meet minimum requirements. Note The recommended values are minimum values. For production database systems, Oracle recommends that you tune the values to optimize system performance. For more information, see the operating system documentation. Set AIX shell limits 1. Type the following command: # smit chuser 2. In the User NAME box, type the user name of the Oracle software owner, for example, oracle. 3. Scroll down the list and ensure that the values shown in the following table are set to the minimum values. Caution Do not change the shell limit values if they were set for another program and the values are greater than the levels Oracle requires. 4. Press F10 to exit. AIX shell limit Soft FILE size Soft CPU time Soft DATA segment Soft STACK size Minimum value 1 (unlimited) 1 (unlimited) This is the default value. 1 (unlimited) 1 (unlimited) Set AIX system parameters 1. Type the following command: # smit chgsys 2. Ensure that the value shown for Maximum number of PROCESSES allowed per user is greater than or equal to PLM00129 H Upgrade Guide 2-5

28 Chapter 2 Preparing the Teamcenter network Note For production systems, this value should be at least 128 plus the sum of the PROCESSES and PARALLEL_MAX_SERVERS initialization parameters for each database running on the system. 3. Press F10 to exit. Set AIX kernel parameters Siemens PLM Software recommends setting kernel parameters to meet or exceed the recommended Oracle settings. Set HP-UX kernel parameters Set kernel parameters as described in the following table. Set parameters using the method described in your HP-UX documentation. Caution Note Do not change the kernel parameter settings if the parameters were set for another program and the values are greater than the levels Oracle requires. You can view kernel parameters using the kctune command. HP-UX kernel parameter Minimum value or formula Purpose executable_stack 0 Defines whether program stacks are executable by default. ksi_alloc_max Defines the system-wide limit of queued signals that can be allocated. max_thread_proc 3000 Defines the maximum number of kernel threads allowed per process. You may need to increase the value if required by your application. Setting it to a default or low value may lead to an out of memory error for certain applications. maxdsiz Defines the maximum data segment size in bytes for 32-bit systems. Setting this value too low may cause the processes to run out of memory. maxdsiz_64bit Defines the maximum data segment size in bytes for 64-bit systems. Setting this value too low may cause the processes to run out of memory. maxssiz Defines the maximum stack segment size in bytes for 32-bit systems. maxssiz_64bit (1 GB) Defines the maximum stack segment size in bytes for 64-bit systems. 2-6 Upgrade Guide PLM00129 H

29 Preparing the Teamcenter network HP-UX kernel parameter Minimum value or formula Purpose maxswapchunks Defines the maximum number of swap chunks where SWCHUNK is the swap chunk size (1 KB blocks). SWCHUNK is 2048 by default. It specifies the maximum amount of configurable swap space on the system. Note This parameter does not exist in HP-UX or later. maxuprc ((nproc*9)/10) Defines the maximum number of user processes. msgmap (msgtql + 2) Defines the maximum number of message map entries. msgmni (nproc) Defines the number of message queue identifiers. msgseg Defines the number of segments available for messages. msgtql (nproc) Defines the number of message headers. ncsize (ninode ) Defines the directory name lookup cache (DNLC) space needed for inodes. nfile Defines the maximum number of open files. This parameter is managed automatically by the system. nflocks 4096 Defines the maximum number of file locks available on the system. This parameter is managed automatically by the system. ninode (8 * nproc ) Defines the maximum number of open inodes. nkthread (((nproc * 7) / 4) + 16) Defines the maximum number of kernel threads supported by the system. nproc 4200 Defines the maximum number of processes. semmap (semmni + 2) Defines the maximum number of semaphore map entries. Note This parameter does not exist in HP-UX or later. semmni 4200 Defines the maximum number of semaphore sets in the entire system. semmns (semmni * 2) Defines the maximum number of semaphores in the system. The default value of semmns is 128, which is, in most cases, too low for Oracle software. PLM00129 H Upgrade Guide 2-7

30 Chapter 2 Preparing the Teamcenter network HP-UX kernel parameter Minimum value or formula Purpose semmnu (nproc 4) Defines the number of semaphore undo structures. semvmx Defines the maximum value of a semaphore. shmmax Physical memory size Defines the maximum allowable size of one shared memory segment. To avoid performance degradation, the shmmax setting must be greater than or equal to the size of the SGA. shmmni 512 Defines the maximum number of shared memory segments in the entire system. shmseg 512 Defines the maximum number of shared memory segments one process can attach. vps_ceiling 64 Defines the maximum system-selected page size in kilobytes. Set Solaris kernel parameters On Solaris 9 or earlier, set kernel parameters to meet or exceed the recommended Oracle settings. Use the procedure provided in your Solaris documentation to set kernel parameters. On Solaris 10, set kernel parameters using the Solaris resource control facility. The following table describes Solaris 10 resource control values for a single database instance. Solaris 10 resource control process.max-sem-ids project.max-shm-memory project.max-shm-ids Description Oracle recommends setting this resource control to 100, but the Solaris default value (128) is adequate, so it is not necessary to change this setting. Defines the maximum shared memory (shm) for the Oracle server. Oracle recommends a value of 4 GB, but for Teamcenter servers, set this resource control to a value greater than the total SGA + PGA memory size of all instances on the system. Oracle recommends setting this resource control to 100, but the Solaris default value (200) is adequate, so it is not necessary to change this setting. Set parameters for the project user.oracle account (oracle) instead of the project user.root recommended by Oracle documentation. To work with Solaris resource control, use the following CLI command: prtctl n control name i project user.oracle 2-8 Upgrade Guide PLM00129 H

31 Preparing the Teamcenter network For example: sun2:(root)# prctl -n project.max-sem-ids -i project user.oracle project: 100: user.oracle NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-sem-ids privileged deny - system 16.8M max deny - sun2:(root)# prctl -n project.max-shm-memory -i project user.oracle project: 100: user.oracle NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory privileged 3.92GB - deny - system 16.0EB max deny - sun2:(root)# prctl -n project.max-sem-ids -i project user.oracle project: 100: user.oracle NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-sem-ids privileged deny - system 16.8M max deny Set SUSE Linux shell limits 1. Increase shell limits for the oracle user to the minimum values listed in the following table by adding the following lines to the /etc/security/limits.conf file: oracle soft nproc 2047 oracle hard nproc oracle soft nofile 1024 oracle hard nofile SUSE Linux shell limit Item in limits.conf Minimum hard limit Maximum number of open file descriptors nofile Maximum number of processes available to a single user nproc Caution Do not change the shell limit values if they were set for another program and the values are greater than the levels Oracle requires. 2. Add or edit the following line in the /etc/pam.d/login file: session required /lib/security/pam_limits.so 3. Change the oracle user default shell startup file: For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile.local file: if [ $USER = "oracle" ]; then if [ $SHELL = "/bin/ksh" ]; then ulimit -u ulimit -n else ulimit -u n fi fi For the C shell (csh or tcsh), add the following lines to the /etc/csh.logon.local file: if ( $USER == "oracle" ) then PLM00129 H Upgrade Guide 2-9

32 Chapter 2 Preparing the Teamcenter network endif limit maxproc limit descriptors Upgrade an Oracle server and database Export an Oracle database Windows systems: 1. Log on to the Oracle server as an administrator user. 2. Export the contents of your Teamcenter Oracle database to the dump file: ORACLE_HOME\bin\exp db-user/password full=y file=file-name.dmp log=export.log Replace db-user with the Teamcenter database user account name; replace password with the database user account password; replace file-name with the full path and name of the dump file to contain the exported data; replace export with the name of the log file to contain export output. 3. Store the dump file in a safe place. UNIX or Linux systems: 1. Either log on to the Oracle server as oracle or switch the user to oracle: su - oracle 2. Set the PATH environment variable to include the Oracle bin directory: export PATH=$PATH:ORACLE_HOME/bin 3. Manually set the shared library path: IBM AIX: export LIBPATH=${LIBPATH}:${ORACLE_HOME}/lib Hewlett-Packard HP-UX: export SHLIB_PATH=${SHLIB_PATH}:${ORACLE_HOME}/lib Sun Solaris: export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib SUSE Linux: export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib 4. Export the contents of the Teamcenter Oracle database to the dump file: ORACLE_HOME/bin/exp db-user/password full=y file=file-name.dmp log=export.log Replace db-user with the Teamcenter database user account name; replace password with the database user account password; replace file-name with the name of the dump file to contain the exported data; replace export with the name of the log file to contain export output. 5. Store the dump file in a safe place Upgrade Guide PLM00129 H

33 Preparing the Teamcenter network If you have multiple databases, repeat this procedure for each database. Caution Siemens PLM Software strongly recommends backing up the dump file on tape or another disk. If the dump file becomes corrupted or lost, all data from the existing database is lost. Terminate Oracle sessions on Windows systems If you are upgrading an Oracle installation on your Windows database server, terminate all Oracle sessions and Oracle processes prior to installation. Stop the listener process 1. Log on to the operating system as a user with administrator privileges. 2. Open the Services dialog box in the Windows Control Panel. 3. Select the Oracle TNS listener services (Oraclerelease-IDTNSListener) and click Stop. Shut down an Oracle database You can shut down an Oracle database using either the Windows Control Panel or the Oracle SQL*Plus utility. Shut down Oracle using Windows Control Panel 1. Log on to the operating system as a user with administrator privileges. 2. Open the Services dialog box in the Windows Control Panel. Windows displays the Services window. 3. Select the OracleServiceSID service. Replace SID with the system identifier of the database instance. 4. Click Stop. Shut down Oracle using SQL*Plus 1. Log on to the operating system as a user with administrator privileges. 2. Start the Oracle SQL*Plus utility: sqlplus sys/password@oracle SID as sysdba Replace password with the password for the sys user account. Oracle starts the Oracle SQL*Plus utility. Note The sys user must be in the Oracle sysdba group for the Oracle system identifier (SID) used by Teamcenter. To connect as internal (without a password), the account must be part of the ORA_DBA local group in Windows. 3. Shut down the database instance by typing the following command: PLM00129 H Upgrade Guide 2-11