Teamcenter Installation on Windows Servers Guide. Publication Number PLM00013 J

Transcription

1 Teamcenter 10.1 Installation on Windows Servers Guide Publication Number PLM00013 J

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 Installation on Windows Servers Guide PLM00013 J

3 Contents Proprietary and restricted rights notice Part I: Getting started with Teamcenter server installation Getting started Getting started System requirements Enabling Teamcenter installation Configuring Teamcenter installation Starting Teamcenter installation Interfaces: Teamcenter installation tools Basic concepts about Teamcenter installation Site planning Site planning Installation and deployment overview Other considerations Part II: Database server installation IBM DB2 installation and configuration IBM DB2 installation and configuration Install IBM DB Create a DB2 sample database Verify connectivity with the sample database Creating a DB2 database for Teamcenter Oracle installation and configuration Preparing the Oracle server Upgrade an Oracle server and database Install Oracle server Configure Oracle software Create an Oracle database Microsoft SQL Server installation and configuration Microsoft SQL Server installation and configuration Install Microsoft SQL Server Create an SQL Server database Part III: Teamcenter server installation Teamcenter preinstallation tasks Obtain a Teamcenter license file PLM00013 J Installation on Windows Servers Guide 3

4 Contents Install the licensing server Select destination directories Install a volume server Install NX and Teamcenter Integration for NX or NX Integration Best installation practices Teamcenter server installation Before you start Install a Teamcenter corporate server Teamcenter postinstallation tasks Teamcenter postinstallation tasks Start database daemons Configure Multi-Site Collaboration Configure heterogeneous operating system environment Part IV: Web tier installation.net Web tier installation NET Web tier installation Before you start Install the.net Web tier Start the Web client Configuring online help J2EE Web tier installation J2EE Web tier installation J2EE Web tier prerequisites Install the Web Application Manager Installing thin client Web applications Installing rich client Web applications Part V: Adding features Installing the server manager Gather required information Install the.net server manager Install the J2EE server manager Start the server manager Install the Business Modeler IDE Installing a custom solution or third-party template Installing a custom solution or third-party template Install a template using TEM Update the database using TEM Manufacturing Manufacturing Install the Manufacturing Resource Library Installation on Windows Servers Guide PLM00013 J

5 Contents Updating the Manufacturing Resource Library from an earlier version Planning data migration from Genius4000 to Resource Manager Install EDA server support Install EDA server support Installing Teamcenter reporting and analytics Installing Teamcenter reporting and analytics Before you begin Create the Reporting and Analytics database Configure the Reporting and Analytics license file Install Reporting and Analytics Install Remote Reporting and Analytics Deploy Reporting and Analytics Complete Reporting and Analytics installation Installing Render Management Installing Render Management Installing Teamcenter online help Installing Teamcenter online help Install online help Configure online help access for Teamcenter clients Part VI: Additional configuration and maintenance Managing installations and configurations Managing installations and configurations Create a configuration Modify a configuration Add an existing Teamcenter database Add or configure a database Change the Oracle password Configure multiple databases for a four-tier rich client Migrate Teamcenter to a different JRE Deploying localized versions of Teamcenter Deploying localized versions of Teamcenter Configuring client display language Environment settings for non-english locales Deploying localizations Creating a custom distribution Overview of custom distributions Create a silent distribution Create a compact distribution Installing Teamcenter patches Installing Teamcenter patches Distribution of Teamcenter updates PLM00013 J Installation on Windows Servers Guide 5

6 Contents Downloading Teamcenter patches Patch Teamcenter Environment Manager Install patches on the corporate server Patching the rich client Patch the Web tier Review the README file Uninstalling Teamcenter Uninstalling Teamcenter Uninstall Teamcenter configurations and installations Uninstall TCCS Uninstalling DB Uninstall Oracle Uninstall SQL Server Part VII: Appendixes Troubleshooting A-1 Troubleshooting A-1 Troubleshooting Teamcenter server installation A-1 Troubleshooting four-tier architecture deployment A-8 Troubleshooting the.net Web tier A-16 Troubleshooting document rendering A-17 Troubleshooting Teamcenter Integration for NX A-19 Recovering from a corrupted database A-20 Distribution media B-1 Distribution media B-1 Teamcenter software distribution image B-2 Teamcenter documentation distribution image B-2 Solutions and features reference C-1 Solutions and features reference C-1 Teamcenter solutions C-1 Teamcenter features C-1 Rich client solutions C-16 Web tier context parameters D-1 Glossary E-1 Index Index-1 Figures Teamcenter Environment Manager Web Application Manager Two-tier architecture Two-tier deployment Installation on Windows Servers Guide PLM00013 J

7 Contents Tables Four-tier architecture Four-tier deployment (enterprise and Web tiers on same host) Four-tier deployment (enterprise and Web tiers on separate hosts with HTTP server) Four-tier deployment (multiple enterprise tier hosts and Web tier hosts) Four-tier deployment (load balancing) Two-tier architecture installation Four-tier architecture installation Rich client installation Basic File Management System deployment Browsing for the template files Selecting the new feature Viewing the templates to be installed Starting a full model update Selecting the template for update Teamcenter HTML online help collection Teamcenter PDF online help collection Multiple databases (four-tier rich client) Sample silent installation configuration file Platform support for Teamcenter servers and clients Required hard disk space for Teamcenter configurations Rich client optional parameter values Lifecycle Visualization (embedded viewer) parameter and table values Lifecycle Visualization (stand-alone application viewer) parameter and table values Teamcenter Integration for NX parameter and table values Content Management System for Rich Client 4-Tier values Environment settings on Windows systems Teamcenter features C-2 Web tier required parameters D-1 Web tier optional parameters D-5 Global Services context parameters D-7 PLM00013 J Installation on Windows Servers Guide 7

8

9 Part I Getting started with Teamcenter server installation This guide describes how to install Teamcenter 10.1 on Microsoft Windows servers. This includes installation of Teamcenter servers using Teamcenter Environment Manager and the Teamcenter Web tier using the Web Application Manager. This guide assumes you have a thorough working knowledge of your operating system and general knowledge of Teamcenter use. Getting started Site planning PLM00013 J Installation on Windows Servers Guide

10

11 Chapter 1 Getting started Getting started System requirements Where to find system requirements Platforms System hardware Database Java Runtime Environment Web browser Web tier support Software integrations Enabling Teamcenter installation Locate Teamcenter distribution images Configuring Teamcenter installation Starting Teamcenter installation Interfaces: Teamcenter installation tools Teamcenter Environment Manager Web Application Manager Basic concepts about Teamcenter installation Database server Teamcenter servers Corporate server Additional servers Teamcenter clients Rich client Thin client Teamcenter network architectures Two-tier architecture Four-tier architecture Selecting and configuring features Basic tasks in Teamcenter installation Installing a database server Installing a Teamcenter server Installing the Web tier Installing Teamcenter clients PLM00013 J Installation on Windows Servers Guide

12

13 Chapter 1 Getting started Getting started Verify you have installed supported versions of all prerequisite software and plan your Teamcenter network before you begin installing servers. 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. Platform support for Teamcenter servers and clients PLM00013 J Installation on Windows Servers Guide 1-1

14 Chapter 1 Getting started Operating System Corporate server Web tier Rich client Thin client Business Modeler IDE client TCCS 1 Microsoft Windows (desktop platforms) 2 Microsoft Windows (server platforms) 3 Sun Solaris Hewlett-Packard HP-UX 4 IBM AIX SUSE Linux Red Hat Linux 5 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. For information about installing Teamcenter on Windows clients, see the Installation on Windows Clients Guide. For information about installing Teamcenter on UNIX or Linux servers, see the Installation on UNIX and Linux Servers Guide. 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. Microsoft Windows Make sure the C:\Temp directory exists, and grant full access permissions to this directory for all users. 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. 1. Teamcenter client communication system (TCCS) is installed with the rich client. This column refers to the stand-alone TCCS application. 2. 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. 3. Microsoft Windows server platforms include Windows Server Itanium platforms only. PA-RISC hardware is not supported. 5. Only 64-bit Red Hat Linux is supported. 1-2 Installation on Windows Servers Guide PLM00013 J

15 Getting started 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. 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 Install a Teamcenter corporate server. 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). PLM00013 J Installation on Windows Servers Guide 1-3

16 Chapter 1 Getting started 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 J2EE Web tier installation. 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 IBM DB2 installation and configuration, Oracle installation and configuration, or Microsoft SQL Server installation and configuration. 6. Itanium platforms only. PA-RISC hardware is not supported. 1-4 Installation on Windows Servers Guide PLM00013 J

17 Getting started 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 32-bit Java Set the JRE_HOME environment variable to the location of the 32-bit Java JRE. o 64-bit Java Set the JRE64_HOME environment variable to the location of the 64-bit Java JRE. Note 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 browser The Teamcenter thin client and Over-the-Web Installer 7 require a Web browser. Teamcenter 10.1 supports the following Web browsers: Windows systems: Microsoft Internet Explorer and Mozilla Firefox Linux systems: Mozilla Firefox Macintosh systems: Apple Safari 7. The Over-the-Web Installer installs the four-tier Teamcenter rich client and Teamcenter Microsoft Office interfaces. PLM00013 J Installation on Windows Servers Guide 1-5

18 Chapter 1 Getting started For information about versions supported, see the Siemens PLM Software Certification Database. Web tier support Install the required software for the Teamcenter Web tier you use: J2EE Web tier 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 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. 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. For descriptions of Teamcenter distribution images, see Distribution media. 1-6 Installation on Windows Servers Guide PLM00013 J

19 Getting started 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. Configuring Teamcenter installation Before you install Teamcenter, create an operating system logon account for Teamcenter. This account must belong to the Administrators group and must be granted the Log on as a service right. Teamcenter services run on the server as this user account. Log on using this account when you install the Teamcenter corporate server and when you perform maintenance such as upgrading or installing updates using Teamcenter Environment Manager. Starting Teamcenter installation To begin installing Teamcenter installation, launch the appropriate Teamcenter installation tool: Teamcenter Environment Manager To install the Teamcenter corporate server, launch Teamcenter Environment Manager using the tem.bat command from the Teamcenter software distribution image. Web Application Manager To begin installing the Teamcenter J2EE Web tier, launch the Web Application Manager using the insweb command from the install directory in the WEB_ROOT directory. 8 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. 8. You create this directory when you install the Web Application Manager as described in J2EE Web tier installation. PLM00013 J Installation on Windows Servers Guide 1-7

20 Chapter 1 Getting started 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. Web Application Manager The Web Application Manager is a tool that installs thin client and rich client solutions and builds Teamcenter J2EE Web applications. 1-8 Installation on Windows Servers Guide PLM00013 J

21 Getting started 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 J2EE Web tier installation. Note The.NET Web tier is installed using Teamcenter Environment Manager, not the Web Application Manager. Basic concepts about Teamcenter installation Determine the Teamcenter servers and network architectures suit your needs and which features you want to install. Database server A Teamcenter network requires access to a database server. 9. A deployable file is a Web archive (WAR) or enterprise archive (EAR) file, depending on the solutions it contains. PLM00013 J Installation on Windows Servers Guide 1-9

22 Chapter 1 Getting started Before you install Teamcenter, you or your database administrator must install and configure a database server to store Teamcenter data. The Teamcenter corporate server must have access to a database server or a database client. Teamcenter supports IBM DB2, Oracle, and Microsoft SQL Server databases. For information about installing a database server for Teamcenter, see IBM DB2 installation and configuration, Oracle installation and configuration, or Microsoft SQL Server installation and configuration. For Oracle configuration settings and tuning methods to optimize Teamcenter performance, see the Teamcenter Deployment Guide, available in the documentation section of Siemens PLM Software s support site. The Teamcenter Deployment Guide also provides an in-depth review of Oracle database performance issues and diagnosis, and configuration and tuning guidelines. For Microsoft SQL Server configuration settings and tuning methods to optimize Teamcenter performance, see the Teamcenter Deployment Guide, available in the documentation section of Siemens PLM Software s support site. The Teamcenter Deployment Guide also provides an in-depth review of Microsoft SQL database performance issues and diagnosis, and configuration and tuning guidelines. Note Teamcenter servers and two-tier rich clients on Linux hosts cannot connect to Microsoft SQL Server database servers. Teamcenter servers You can install different types of Teamcenter servers according to the features you use and your load distribution needs. Corporate server A Teamcenter corporate server installation includes the following components: Teamcenter shared binary executables and files Teamcenter shared data subdirectories and files Database connection Teamcenter volume Additional optional Teamcenter features such as File Management System (FMS) Additional servers A Teamcenter network requires one corporate server configuration. Additional servers are optional, but can help balance network loads and facilitate heterogeneous networks (networks with hosts running different operating systems). Teamcenter clients Teamcenter provides clients suited to various uses and network configurations. These clients include the rich client, the thin client, and specialized clients such as Teamcenter Client for Microsoft Office and Teamcenter Extensions for Microsoft Office Installation on Windows Servers Guide PLM00013 J

23 Getting started Rich client The rich client is a platform-independent client implementation (Java application) for users who interact with Teamcenter frequently. It is extendable and able to run both Teamcenter and customer-written applications. Customers can also extend the standard user interface. The rich client application is deployed on each user workstation using Teamcenter Environment Manager or the Over-the-Web Installer, depending on which Teamcenter network architecture you use. The rich client is supported in both architectural models described in Two-tier architecture and Four-tier architecture. Thin client The thin client provides access to Teamcenter through a standard commercial Web browser, such as Microsoft Internet Explorer or Mozilla Firefox. The user interface provides a streamlined browser-based view of product information stored in a Teamcenter database. The thin client is supported only in the four-tier architectural model described in Four-tier architecture. Teamcenter network architectures Teamcenter provides two architecture models for deployment: two-tier and four-tier. Two-tier architecture The two-tier architectural model comprises the following tiers: Client tier The client tier comprises the Teamcenter rich clients. In a deployment of the two-tier architecture, the Teamcenter server runs on the client workstation. Note The two-tier rich client is installed only through TEM. Over-the-Web installation is supported only for the four-tier rich client. Some Teamcenter client features, such as Teamcenter Integration for NX, Lifecycle Visualization, and Teamcenter Client for Microsoft Office, require the Web tier, a component of the four-tier architecture. To enable these features for a two-tier rich client, you can connect the two-tier rich client to a deployment of the Web tier. For information about functionality you can add to a rich client and which add-ons require the Web tier, see Rich client installation. Resource tier The resource tier comprises a database server, database, volumes, and file servers. PLM00013 J Installation on Windows Servers Guide 1-11

24 Chapter 1 Getting started Two-tier architecture In the two-tier model, you deploy the Teamcenter rich client, which includes the local server, and the optional applications that integrate with the rich client on the client workstation. Typically, the database server, volumes, and file servers are installed on one or more separate hosts. Teamcenter File Management System (FMS) manages the rich client access to volumes: The FMS server cache (FSC) process run on the server hosting the volume. The FMS client cache (FCC) process runs on the rich client host. For more information about FMS and two-tier rich client architecture, see File Management System installation Installation on Windows Servers Guide PLM00013 J

25 Getting started Two-tier deployment Four-tier architecture The four-tier architecture model comprises the following tiers: Client tier The client tier comprises the Teamcenter rich client, thin client, and other clients such as Teamcenter Client for Microsoft Office. Note The rich client can be deployed with additional functionality, such as Lifecycle Visualization, Teamcenter Client for Microsoft Office, and Teamcenter Integration for NX or NX Integration (Teamcenter Integration for NX/NX Integration 3 is not supported.) For information about the functionality you can add, see Rich client installation. J2EE Web tier The J2EE Web tier is a Java application that runs in a Java 2 Enterprise Edition (J2EE) application server, such as Oracle WebLogic, and is responsible for communication between the client tier and enterprise tier. For information about supported application servers, see the Siemens PLM Software Certification Database: certification/teamcenter.shtml PLM00013 J Installation on Windows Servers Guide 1-13

26 Chapter 1 Getting started Enterprise tier The enterprise tier comprises a configurable pool of Teamcenter C++ server processes and a server manager. The enterprise tier retrieves data from and stores data in the database. A server manager manages a pool of Teamcenter server processes. You must install a server manager whenever you deploy the Web tier. Note Teamcenter provides server managers based on the J2EE and the Microsoft.NET platforms. Install the appropriate server manager for the Web tier you use. Resource tier The resource tier comprises a database server, database, volumes, and file servers Installation on Windows Servers Guide PLM00013 J

27 Getting started Four-tier architecture You can design deployments that host the Web tier, resource tier, and enterprise tiers on the same computer or on separate computers: Smaller sites can run the pool of servers and the server manager on the same host as the Web tier. Larger sites can distribute the pool of server processes across multiple hosts and optionally include an HTTP server to serve static files or multiple HTTP servers to support load balancing. For a multihost configuration, the server pool consists of multiple subpools, one or more for each host. Each subpool is managed by one server manager process. The Web tier balances the load across the server pools. PLM00013 J Installation on Windows Servers Guide 1-15

28 Chapter 1 Getting started The Teamcenter J2EE based server manager and Web tier application both employ the JBoss cache, a tree-structured cache, to provide replication and transaction context. You must configure the JBoss cache (called TreeCache in Teamcenter) in both the J2EE based server manager and the Web tier application. 10 To ensure communication between the Web tier and the server manager, you must coordinate the values you specify for each component. For some values, you must provide the identical value when configuring the Web tier application. If you are setting up multiple Web tier environments with separate domains, you must configure: A minimum of one server manager for each Web tier deployment. A separate TreeCache cluster for each environment. To configure a separate TreeCache cluster, Siemens PLM Software recommends configuring a different port (multicast) or set of ports (TCP) for each cluster. The JMX HTTP adapter allows you to view the status of the server pool and dynamically alter the pool configuration values (the values are not persistent). Access this functionality from the following URL: Replace host-name with the name of the host running the server manager. Replace jmx-port with the number of the port running the JMX HTTP adapter. This port number is defined when you install the J2EE based server manager. The first time you log on to the adapter, use manager for both the user name and the password. You can change the user name and password to unique values using the adapter. Teamcenter File Management System (FMS) manages the rich client access to volumes: The FMS client cache (FCC) process runs on the rich client host. The FMS server cache (FSC) process runs on each server hosting a volume and each server hosting a pool of Teamcenter servers (TcServer). Note If you install File Management System, the FMS server cache (FSC) and the server manager must run on the same host server, with the same user ID. 10. This is not required if you use the.net Web tier and the.net based server manager Installation on Windows Servers Guide PLM00013 J

29 Getting started Four-tier deployment (enterprise and Web tiers on same host) PLM00013 J Installation on Windows Servers Guide 1-17

30 Chapter 1 Getting started Four-tier deployment (enterprise and Web tiers on separate hosts with HTTP server) 1-18 Installation on Windows Servers Guide PLM00013 J

31 Getting started Four-tier deployment (multiple enterprise tier hosts and Web tier hosts) PLM00013 J Installation on Windows Servers Guide 1-19

32 Chapter 1 Getting started Four-tier deployment (load balancing) 1-20 Installation on Windows Servers Guide PLM00013 J