Teamcenter10 step-by-step installation in Linux env-teamcenter Server installation

Introduction

In the post, we'll start to deploy Two-tier Teamcenter env step by step.

We'll use the following. installation tools which enable you to build and manage your Teamcenter Installat Ion.

• teamcenter Environment Manager (TEM) : A tool that installs Teamcenter servers and Two-tier and Four-tier rich cl Ients.
• Web Application Manager (WAM): A tool that installs thin client and rich client solutions and builds Teamcenter J 2EE WEB Application.

In this post, we'll focus on the TEM to finish 2-tier deployment.

Steps

1) You launch TEM using the tem.sh command.

You need to specify the JRE home when installing TEAMCENTER10 first time. And the version of the JRE needs to be above 1.7.0_17

2) Select [Install]

3) Enter ID and description for Teamcenter configuration.

4) Select the solutions to install

You can install different types for Teamcenter servers according to the features your use. For demo purpose, we select All-in-one 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)

It is obvious, made a little mistake to select both corporate server and volume server in the below snapshot.

5) Click the features to install and specify Tc_root directory.

I Select the following features to install.

6) Specify FSC ID and port. Default setting is OK.

The default FSC ID is fsc_{hostname}_{current OS user name}.

7) Input OS user and password. All TC related services would run as the user.

8) Because The Oracle instance for Teamcenter have been created through DBCA, select [Populate database, create new DAT A directory] option.

Extended Info

9) Specify database server info and Tc_data directory.

Specify volume name and directory.

One) Set transient volume directory and options about generating server and client cache.

Specify license info.

Specify Tcserver character encoding settings. From TC10 on, it supports UTF8 fully and select UTF8 as canonical name.

Configure Server Manager for EE. Default setting is OK for demo purpose.

Configure Treecache.

Extended Info

All clients even where they don't need to maintain their state get a performance benefit from maintaining the same tcserv ER process because information is cached and there are no overhead of starting a process or connection to the database.

Both the Web tier and the Enterprise Tier need to be aware of which client are mapped to which tcserver processes to allow For the correct routing. This was achieved using a in-memory table which is gkfx between all Server Pool Managers and Web application Servers. The mapping is do based on user ID.

The Shared Cache or Tree Cache is key to the failure tolerance and horizontal scalability properties of the ARCHITECTU Re. All servers Pool Managers and all Web application Servers has a copy of the cache which is updated regularly. When a client connects, the cache was consulted to establish if there was an existing tcserver process that can being used for Connection, if not a new one is initiated.

+) Set FCC

Specify FCC Parents

Specify 2-tier server settings.

Summarize the templates to is applied to Tc database.

Click the [Start] button If the configuration is OK.