Escolar Documentos
Profissional Documentos
Cultura Documentos
Installation
Student Guide
December 2010
MT25350 Teamcenter 8.3
Publication Number
MT25350_S_0830
Teamcenter Installation
MT25350_S_0830
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
13
14
14
14
15
15
15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1-2
. 1-3
. 1-4
. 1-6
. 1-7
. 1-8
. 1-9
1-10
1-11
1-12
1-13
1-14
1-15
1-16
1-17
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2-2
. 2-3
. 2-4
. 2-5
. 2-6
2-12
2-13
2-14
2-18
Teamcenter Installation
Contents
Oracle users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How the database stores data . . . . . . . . . . . . . . . . . . . .
Tables required by Teamcenter . . . . . . . . . . . . . . . . . . .
Control files and redo files . . . . . . . . . . . . . . . . . . . . . . .
Choosing how to create the database . . . . . . . . . . . . . . .
Create a database using TEM . . . . . . . . . . . . . . . . . . . .
Create a database using the DBCA and TC templates . .
Create a database using the DBCA and TC templates . .
Accessing the database from a client . . . . . . . . . . . . . . . . . .
Information needed to access the database from a client
tnsnames.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start and stop Oracle instances . . . . . . . . . . . . . . . . . . . . .
Start and stop Oracle instances: Oracle Server processes
(OracleServiceSID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start and stop Oracle instances: Database instance . . . . . .
SQL*Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connect to a database using nolog . . . . . . . . . . . . . . . . .
Connect to a database using a connect descriptor . . . . . .
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-19
2-20
2-21
2-23
2-24
2-25
2-26
2-27
2-33
2-34
2-35
2-36
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-37
2-38
2-39
2-40
2-41
2-42
2-43
2-44
.................
.................
.................
.................
.................
Server Management
.................
.................
.................
.................
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3-2
. 3-3
. 3-4
. 3-5
3-25
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-26
3-27
3-28
3-29
Teamcenter Installation
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4-2
. 4-3
. 4-4
4-17
4-21
4-27
4-28
4-29
4-30
4-34
MT25350_S_0830
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-35
4-36
4-37
4-38
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 5-2
. 5-3
. 5-4
. 5-5
. 5-6
. 5-9
5-10
5-11
5-12
5-13
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 6-2
. 6-3
. 6-4
. 6-5
. 6-6
. 6-7
. 6-8
. 6-9
6-10
6-11
6-12
6-13
6-14
6-15
6-16
6-17
6-18
6-19
6-23
6-24
6-25
6-42
6-43
6-44
6-45
6-46
6-47
Teamcenter Installation
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 7-2
. 7-3
. 7-4
. 7-5
. 7-6
7-14
7-16
7-18
7-19
7-20
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 8-2
. 8-4
. 8-5
. 8-6
. 8-9
8-10
8-11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9-2
. 9-3
. 9-4
. 9-6
. 9-7
. 9-8
. 9-9
9-10
9-11
9-12
9-13
9-18
9-19
9-21
9-23
9-24
9-25
9-26
9-27
9-28
Teamcenter Installation
MT25350_S_0830
Contents
Server manager . . . . . . . . . . . . . . . . . . . . . . .
Installing the .NET server manager . . . . . . . .
Starting the .NET server manager . . . . . . . . .
.NET Web tier . . . . . . . . . . . . . . . . . . . . . . . .
Internet Information System (IIS) . . . . . . . . .
Installing .NET Web tier . . . . . . . . . . . . . . . .
Launch the thin client . . . . . . . . . . . . . . . . . .
.NET server manager administrative interface
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Review questions . . . . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 10-3
. 10-4
. 10-7
. 10-8
. 10-9
10-13
10-16
10-18
10-19
10-20
10-21
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 11-2
. 11-3
. 11-4
. 11-5
. 11-8
. 11-9
11-12
11-13
11-14
11-15
11-16
11-17
11-18
11-19
11-23
11-24
11-25
11-26
11-27
.
.
.
.
.
.
.
.
.
.
. 12-2
. 12-3
. 12-4
. 12-8
. 12-9
12-12
12-13
12-14
12-15
12-16
Contents
install utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
install ayt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
install ask_version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
install lock_db . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
install encrypt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
POM schema file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Regenerate the POM schema file . . . . . . . . . . . . . . . . . . . . . . .
POM schema transmit file . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing the POM schema transmit file . . . . . . . . . . . . . . . . .
Regenerate the POM schema transmit file . . . . . . . . . . . . . . . .
list_users utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Repairing and cleaning up corrupt datasets . . . . . . . . . . . . . . .
Run dataset_cleanup to report corrupt datasets . . . . . . . . . . . .
Run dataset_cleanup to purge corrupt datasets . . . . . . . . . . . .
clearlocks utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fccstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fscadmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fscadmin syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
fscadmin functions and subfunctions . . . . . . . . . . . . . . . . . . . . . .
fscadmin examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standard volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create a volume using the rich client Organization application
Purge volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing volume details and delete unreferenced files . . . . . . . .
Running review_volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Volume information in XML for third-party backup systems . .
Run backup_xmlinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 13-3
. 13-4
. 13-5
. 13-6
. 13-7
. 13-8
. 13-9
13-10
13-11
13-12
13-13
13-14
13-15
13-16
13-17
13-18
13-19
13-21
13-22
13-23
13-24
13-25
13-26
13-30
13-31
13-32
13-33
13-34
13-35
13-36
13-37
Teamcenter Installation
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 14-2
. 14-3
. 14-6
14-12
14-13
. . . 14-14
. . . 14-15
. . . 14-16
. . . 14-17
. . . 14-18
. . . 14-19
MT25350_S_0830
Contents
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
Installing and accessing Teamcenter online help . . . . . . . . . . . . . 15-1
Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Install online help so that it is directly accessible from a network
location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Install online as part of a J2EE Teamcenter Web tier application . . . . . 15-4
Install online help directly on IIS Web server . . . . . . . . . . . . . . . . . . . . 15-5
Use TEM to configure a rich client for accessing online help . . . . . . . . . 15-7
Use Web Application Manager to configure a rich client for accessing online
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-10
Launch Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
Teamcenter interfaces with Microsoft Office . . . . . . . . . . . . . . . . . 16-1
Client for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Client for Microsoft Office required software . . . . . . . . . . . . . . . . . . .
Client for Microsoft Office installation options . . . . . . . . . . . . . . . . .
Install Client for Microsoft Office using TEM . . . . . . . . . . . . . . . . . .
Install Client for Microsoft Office using the Web Application Manager
Install Client for Microsoft Office using the wizard . . . . . . . . . . . . . .
Extensions for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extensions for Microsoft Office required software . . . . . . . . . . . . . . .
Extensions for Microsoft Office installation options . . . . . . . . . . . . . .
Install Extensions for Microsoft Office using TEM . . . . . . . . . . . . . . .
Install Extensions for Microsoft Office using the Web Application
Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install Extensions for Microsoft Office using the wizard . . . . . . . . . .
Integration for Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration for Microsoft Office required software . . . . . . . . . . . . . . .
Integration for Microsoft Office installation options . . . . . . . . . . . . . .
Install Integration for Microsoft Office using TEM . . . . . . . . . . . . . .
Integration for Microsoft Office using the Web Application Manager .
Network Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install Network Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Review questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
. 16-2
. 16-3
. 16-4
. 16-5
. 16-8
. 16-9
16-16
16-17
16-18
16-19
.
.
.
.
.
.
.
.
.
.
.
.
16-21
16-22
16-23
16-24
16-25
16-26
16-27
16-28
16-29
16-32
16-33
16-35
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 17-8
17-12
17-13
17-14
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
18-2
18-3
18-4
18-5
18-6
.
.
.
.
.
.
.
.
.
.
. 18-7
. 18-8
. 18-9
18-10
18-11
Teamcenter Installation
MT25350_S_0830
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 20-4
. 20-5
. 20-6
. 20-7
. 20-8
. 20-9
20-10
20-11
20-12
20-13
20-15
20-16
20-17
Teamcenter Installation
11
Course overview
Course objectives
The overall objective for this course is to install Teamcenter and its
components.
To create an additional site and configure both the two-tier and the
four-tier rich client to access the new site
Teamcenter Installation
13
Course overview
Key benefits
Key benefits for completing the course objectives include:
An additional site can be created and both the two-tier and the four-tier
rich client can be configured to access the new site
Prerequisites
Audience
The audience for this course includes:
User profile
Installer
System administrator
14
Teamcenter Installation
Job goal
Install, upgrade, migrate, and configure
software
Maintain servers and users
MT25350_S_0830
Course overview
Database administrator
Maintain databases
Learning tracks
Learning tracks for Teamcenter are found on the Siemens PLM Software
training Web site:
http://training.ugs.com/tracks/index.shtml
Material
Student Guide
Student Workbook
In the thin client, choose HelpWeb Collection to access the thin client
help, or choose HelpGeneral Collection to access the full library.
Teamcenter Installation
15
Lesson
Purpose
This lesson presents an overview of the Teamcenter two-tier architecture,
four-tier architecture, and File Management System.
Objectives
After you complete this lesson, you should be able to:
Access the Web site that lists the hardware and software requirements
for Teamcenter.
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
1-1
Teamcenter architectures
There are two different architectures you can set up for your sites Teamcenter
environment. You can set up one or both within a single environment.
1-2
Two-tier architecture
Four-tier architecture
Teamcenter Installation
MT25350_S_0830
Rich client.
Optional applications that integrate with the rich client such as NX.
Volumes.
File servers.
Teamcenter Installation
1-3
The client tier hosts client applications, processes user interface input
and output, and secure file caches.
Available clients include:
1-4
Thin client.
Rich client.
Teamcenter Installation
MT25350_S_0830
The Web tier handles client installs, processes logon requests, routes client
requests to business logic, serves static content to clients, and handles
communication between the client and enterprise tiers.
The Web tier application can be either:
The enterprise tier hosts business logic, applies security rules, retrieves
data from and stores data in the database, and serves dynamic content to
clients.
The enterprise tier is composed of:
Transient volumes.
Standard volumes.
Teamcenter Installation
1-5
Client options
Teamcenter provides clients suited to various uses and network
configurations. These clients include:
1-6
Rich client
Thin client
Teamcenter Installation
MT25350_S_0830
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.
The rich client is supported in two-tier and four-tier architectural models. It
is deployed on user workstations using:
A Web browser is required if the four-tier rich client is installed using the
Over-the-Web Installer and to display the online help. Supported browsers:
Teamcenter Installation
1-7
Thin client
The thin client provides access to Teamcenter through a standard commercial
Web browser. 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.
The thin client is supported for the following Web browsers:
1-8
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
1-9
File management
Files managed by Teamcenter are stored in volumes.
Users cannot directly access files in a volume; instead these files are accessed
via a Teamcenter session.
File access requested by a client is managed by File Management System
(FMS).
1-10
Teamcenter Installation
MT25350_S_0830
Volumes
Standard volume
A Teamcenter-controlled directory that stores files managed by Teamcenter.
Users cannot directly access files in a volume; they must do so via a
Teamcenter session. When a user creates a file from the rich client, the file is
created in a volume.
At least one standard Teamcenter volume is required per database. You can
optionally create multiple volumes for a database.
Transient volume
A Teamcenter-controlled directory that stores temporary data for transport
of reports, PLM XML, and other non-volume data between the Web tier and
client tier in the four-tier architecture.
One transient volume is required per database.
For a deployment of the two-tier architecture, Teamcenter stores temporary
data in a temporary directory on the rich client host.
Teamcenter Installation
1-11
FMS
File Management System (FMS) handles:
1-12
File transfer between volumes and clients for both the two-tier and the
four-tier architectures
File access for NX and Lifecycle Visualization when you use these
products with Teamcenter
Transient data storage for transporting reports, PLM XML, and other
non-volume data between the Web and client tiers in the four-tier
architecture
File caching on both file servers and rich clients in order to improve file
transfer performance
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
1-13
Both accounts:
1-14
Teamcenter Installation
MT25350_S_0830
Activities
In the Teamcenter architecture overview section of the activities, do the
following activities using the Administrator account:
Teamcenter Installation
1-15
Review questions
1. The _________ tier stores persistent metadata and files managed by the
environment.
Select one answer.
Client
Enterprise
Resource
Web
Client
Enterprise
Resource
Web
1-16
Two-tier
Four-tier
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Web site that lists the hardware and software requirements for
Teamcenter
Teamcenter Installation
1-17
Lesson
Purpose
This lesson provides basic concepts about the Oracle server, listener, and
database, how they work with Teamcenter, and how to create them.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
2-1
Oracle overview
The resource tier of both the two-tier and the four-tier architectures stores
persistent metadata. This is accomplished using a relational database
management system (RDBMS). An RDBMS stores metadata so that it can be
retrieved and manipulated.
Teamcenter supports two RDBMSs:
Oracle
Microsoft SQL
For a list of supported RDBMS versions, refer to the GTAC Web site:
http://support.ugs.com
This lesson discusses setting up Oracle as a sites RDBMS.
2-2
Teamcenter Installation
MT25350_S_0830
Oracle architecture
The major components of an Oracle installation are:
Server
Provides application files, controls access to the database, and handles
failure recovery.
Database
Stores metadata.
Listener
Listens for requests made of the database.
Teamcenter Installation
2-3
Oracle instance
Teamcenter supports non clustered databases only. For non clustered
databases, each Oracle database is associated with an instance. When a
database is started, Oracle allocates a memory area called the System Global
Area and starts one or more Oracle processes. This combination of the System
Global Area and Oracle processes is called an instance. The memory and
processes of an instance manage the data and serve the users.
2-4
Teamcenter Installation
MT25350_S_0830
Oracle server
The Oracle server:
OUI
Oracle Universal Installer (OUI) is a Java-based graphical user interface
(GUI) application that enables the installation of the Oracle server and
related components from a DVD-ROM, multiple DVD-ROMs, or the Web.
OUI performs component-based installations and enables different levels of
integrated bundle, suite, and Web-based installations, as well as complex
logic in a single package. The installation engine is easily portable across all
Java-enabled platforms, and platform-specific issues can be encapsulated
from the overall installation process.
DBA operating system account
Ensure the operating system user account under which you install the Oracle
database server has system administrator privileges. This account should
be in the operating systems Administrators group. If so, when Oracle is
installed, this account is automatically added to the Windows ORA_DBA
local group, giving it SYSDBA privileges.
Install location
You can install the Oracle server and application files on shared directories.
However, Oracle Corporation does not support database files on shared
directories. To ensure data integrity, create database files on local disk drives.
Teamcenter Installation
2-5
2-6
Teamcenter Installation
MT25350_S_0830
3. In the Select Installation Type dialog box, select Enterprise Edition and
then click Next.
Teamcenter Installation
2-7
4. In the Install Location dialog box, provide a name and the path in which
to install the server.
2-8
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
2-9
7. In the Summary dialog box, review your selections and then click Install.
The Install dialog box reports the status of the installation.
2-10
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
2-11
Listener
The Oracle listener:
2-12
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
2-13
Create a listener
1. Start the Oracle Net Configuration Assistant by choosing StartAll
ProgramsOracle - OraDb11g_home1Configuration and Migration
ToolsNet Configuration Assistant.
2. In the Welcome dialog box, select Listener configuration and click Next.
3. In the Listener Configuration, Listener dialog box, select Add and click
Next.
2-14
Teamcenter Installation
MT25350_S_0830
4. In the Listener Configuration, Listener Name dialog box, type the listener
name in the Listener name box. The default is LISTENER. Record the
value you use. Click Next.
Teamcenter Installation
2-15
2-16
Teamcenter Installation
MT25350_S_0830
2-17
Database
A database:
2-18
Teamcenter Installation
MT25350_S_0830
Oracle users
To support Teamcenter, the database must have the following Oracle user
accounts:
Teamcenter Installation
2-19
2-20
Teamcenter Installation
MT25350_S_0830
SYSTEM
SYSAUX
TEMP
UNDOTBS
IDATA
INDX
ILOG
Tablespace
SYSTEM
SYSAUX
TEMP
UNDOTBS
Description
The SYSTEM tablespace is always created at
database creation. Oracle uses it to manage the
database. It contains the data dictionary, which is the
central set of tables and views used as a read-only
reference describing a particular database. It also
contains various tables and views that contain
administrative information about the database. These
are all contained in the SYS schema and can only be
accessed by SYS user or other administrative users
with the required privilege.
This is an auxiliary tablespace to the SYSTEM
tablespace. Some components and products that, prior
to Oracle database 10g, used the SYSTEM tablespace
or their own tablespaces now use the SYSAUX
tablespace. This reduces the load on the SYSTEM
tablespace and reduces maintenance because there
are fewer tablespaces to monitor and maintain. Every
Oracle database 10g or later must have a SYSAUX
tablespace.
This is Oracles scratchpad area. During large queries
and sorts this tablespace is used heavily. Its size needs
to be set proportional to the number of concurrent
Teamcenter users and the amount of metadata.
This tablespace permits Oracle to maintain undo
information. Its use expands with the amount of
metadata. UNDOTBS is moderate, though typically
heavier than that of SYSTEM.
Teamcenter Installation
2-21
Tablespace
IDATA
INDX
ILOG
2-22
Teamcenter Installation
Description
This tablespace stores all of the Teamcenter metadata.
It is the most actively accessed tablespace and receives
the most growth.
The database administrator has the option of
separating the indexes from the IDATA tablespace
thus reducing the load created by IDATA.
The Teamcenter logging functionality creates a
separate tablespace to store Teamcenter loggings
required tables and indexes.
MT25350_S_0830
Teamcenter Installation
2-23
Teamcenter-provided templates
Use the templates provided by Teamcenter to manually create a database
in the Oracle Database Configuration Assistant (DBCA).
2-24
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
2-25
2-26
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
2-27
8. In the Management Options dialog box, accept the defaults and click Next.
2-28
Teamcenter Installation
MT25350_S_0830
9. In the Database Credentials dialog box, supply passwords for the Oracle
users. You can define one password for all users or different passwords
for each.
Record the passwords you define. You need the password for the infodba
Oracle user to install Teamcenter.
10. In the Storage Options dialog box, accept the default, which is to use the
file system for database storage and click Next.
11. In the Database File Location dialog box, accept the default, which is to
use the location defined in the template and click Next.
12. In the Recovery Configuration dialog box, accept the default recovery
area and size and click Next.
13. In the Database Content dialog box, accept the defaults and click Next.
Teamcenter Installation
2-29
2-30
Teamcenter Installation
MT25350_S_0830
15. In the Database Storage dialog box, define the path and initial size of
each tablespace, control file, and redo log.
To do this, select the entity in the left-hand pane and type the desired
values in the right-hand pane. Click Next.
16. In the Creation Options dialog box, select Create Database and click
Finish.
Teamcenter Installation
2-31
2-32
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
2-33
2-34
Service name
Teamcenter Installation
MT25350_S_0830
tnsnames.ora
The tnsnames.ora file is located in ORACLE_HOME\network\admin.
An excerpt from a tnsnames.ora file follows:
prod =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = harris01) (PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = prod)
)
)
Teamcenter Installation
2-35
Listener
A single listener can support multiple databases.
2-36
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
2-37
2-38
Teamcenter Installation
MT25350_S_0830
SQL*Plus
SQL*Plus is a tool included with Oracle that can be used to:
Teamcenter Installation
2-39
2-40
Teamcenter Installation
MT25350_S_0830
Connect descriptor
db-user/password@Net-Service-name is called a connect descriptor.
db-user is the name of the Oracle user associated with the database.
password is the password for the Oracle user associated with the database.
Net-Service-name has the same value as the SID, but it is not the SID or
the service name.
Teamcenter Installation
2-41
Activities
If you chose to install Oracle, use the dba account to perform the following
activities in the Oracle server, listener, and database (Oracle only) section:
2-42
Teamcenter Installation
MT25350_S_0830
Review questions
1. The Oracle _________ monitors remote connection requests made of the
database.
Select one answer.
Database server
Listener
Universal Installer
FTP
HTTP
IIOP
SQL*Net8
3. You can create and configure an Oracle database for use with Teamcenter
by first creating a general purpose database using the Oracle Database
Configuration Assistant and then configuring that database using
Teamcenter Environment Manager.
Select one answer.
True
False
Bin
Data file
Folder
Table
Teamcenter Installation
2-43
Summary
The following topics were taught in this lesson:
2-44
Oracle listener
Oracle database
Teamcenter Installation
MT25350_S_0830
Lesson
MS SQL Server
Purpose
This lesson provides basic concepts about the MS SQL Server and database,
how they work with Teamcenter, and how to create them.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
3-1
MS SQL Server
Oracle
Microsoft SQL
For a list of supported RDBMS versions, refer to the GTAC Web site:
http://support.ugs.com
This lesson discusses setting up Microsoft SQL Server as a sites RDBMS.
3-2
Teamcenter Installation
MT25350_S_0830
MS SQL Server
MS SQL architecture
The major components of a Microsoft SQL Server installation are:
Server
Provides application files, controls access to the database, and handles
failure recovery.
Database
Stores metadata.
Teamcenter Installation
3-3
MS SQL Server
3-4
Teamcenter Installation
MT25350_S_0830
MS SQL Server
Teamcenter Installation
3-5
MS SQL Server
3. In the Setup Support Rules dialog box, review the report to ensure that
all rules passed and then click OK.
3-6
Teamcenter Installation
MT25350_S_0830
MS SQL Server
4. In the Product Key dialog box, select either Specify a free edition or
Enter the product key and then click Next.
Teamcenter Installation
3-7
MS SQL Server
5. In the License Terms dialog box, read the license terms and select I
accept the license terms and click Next.
3-8
Teamcenter Installation
MT25350_S_0830
MS SQL Server
7. In the Setup Support Rules dialog box, review the report and click Next.
Teamcenter Installation
3-9
MS SQL Server
8. In the Feature Selection dialog box, select the features you need, select a
Shared features directory, and then click Next.
Database Engine Service is the only feature required by Teamcenter.
3-10
Teamcenter Installation
MT25350_S_0830
MS SQL Server
Teamcenter Installation
3-11
MS SQL Server
10. In the Disk Space Requirements dialog box, verify that you have enough
disk space and click Next.
3-12
Teamcenter Installation
MT25350_S_0830
MS SQL Server
11. In the Service Accounts tab of the Server Configuration dialog box,
define the user accounts and startup type for the SQL Server services.
Teamcenter Installation
3-13
MS SQL Server
12. In the Collation tab of the Server Configuration dialog box, define the
collation used by the database engine and the analysis server. Change the
collation type by clicking Customization.
3-14
Teamcenter Installation
MT25350_S_0830
MS SQL Server
13. In the Customize the SQL Server 2008 Database Engine Collation dialog
box:
Select Binary.
Click OK.
Teamcenter Installation
3-15
MS SQL Server
14. In the Customize the SQL Server 2008 Analysis Service Collation dialog
box:
3-16
Select Binary.
Click OK.
Teamcenter Installation
MT25350_S_0830
MS SQL Server
15. In the Server Configuration dialog box, ensure that both Database Engine
and Analysis Service are set to Latin1_General_BIN and then click Next.
Teamcenter Installation
3-17
MS SQL Server
Click Next.
17. In the Error and Usage Reporting dialog box, select the options you want
to use. None of these are used by Teamcenter.
3-18
Teamcenter Installation
MT25350_S_0830
MS SQL Server
18. In the Installation Rules dialog box, verify that there are no errors or
warnings and click Next.
Teamcenter Installation
3-19
MS SQL Server
19. In the Ready to Install dialog box, review your selections and click Install.
3-20
Teamcenter Installation
MT25350_S_0830
MS SQL Server
Teamcenter Installation
3-21
MS SQL Server
3-22
Teamcenter Installation
MT25350_S_0830
MS SQL Server
24. Expand SQL Server Network Configuration and select Protocols for
MSSQLSERVER.
25. You receive a warning saying that any changes made will not take affect
until the service is stopped and restarted. Click OK.
26. Right-click TCP/IP and select Enabled.
Teamcenter Installation
3-23
MS SQL Server
3-24
Teamcenter Installation
MT25350_S_0830
MS SQL Server
Teamcenter Installation
3-25
MS SQL Server
3-26
Teamcenter Installation
MT25350_S_0830
MS SQL Server
Activity
If you chose to install Microsoft SQL Server, use the dba account to perform
the following activities in the Install the Microsoft SQL Server (SQL Server
only) section:
Teamcenter Installation
3-27
MS SQL Server
Review questions
1. When installing the MS SQL Server for use with Teamcenter, you must
install at least the Database Engine Service feature.
Select one answer.
True
False
2. You can create and configure an MS SQL database for use with
Teamcenter automatically using _________ .
Select one answer.
Universal Installer
3-28
configure_database.sql
connect_database.sql
create_database.sql
install_database.sql
Teamcenter Installation
MT25350_S_0830
MS SQL Server
Summary
The following topics were taught in this lesson:
Teamcenter Installation
3-29
Lesson
IBM DB2
Purpose
This lesson provides basic concepts about the IBM DB2 server and database,
how they work with Teamcenter, and how to create them.
Objectives
After you complete this lesson, you should be able to:
Describe how to install the IBM Data server driver for ODBC, CLI, and
.NET.
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
4-1
IBM DB2
DB2 overview
The resource tier of both the two-tier and the four-tier architectures stores
persistent metadata. This is accomplished using a relational database
management system (RDBMS). An RDBMS stores metadata so that it can be
retrieved and manipulated.
Teamcenter supports three RDBMSs:
IBM DB2
Microsoft SQL
Oracle
For a list of supported RDBMS versions, refer to the GTAC Web site:
http://support.ugs.com
This lesson discusses setting up Microsoft SQL Server as a sites RDBMS.
4-2
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-3
IBM DB2
4-4
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-5
IBM DB2
5. In the Software License Agreement dialog box, select I accept the terms
in the license agreement and click Next.
4-6
Teamcenter Installation
MT25350_S_0830
IBM DB2
6. In the Select the installation type dialog box, select Typical and click Next.
Teamcenter Installation
4-7
IBM DB2
7. In the Select the installation, response file creation, or both dialog box,
select the appropriate option. If you do not want to save your installation
settings in a response file, select the first option in the list, Install DB2
Enterprise Server Edition on this computer.
4-8
Teamcenter Installation
MT25350_S_0830
IBM DB2
8. In the Select the installation folder dialog box, enter a location in the
Directory box and then click Next.
9. In the Set user information for the DB2 Administration Server dialog box:
Make sure Use the same user name and password for the remaining
DB2 instances is selected.
Click Next.
DB2 uses the operating systems native user authentication and creates
the following user and groups automatically during installation:
User: db2admin
Teamcenter Installation
4-9
IBM DB2
4-10
Teamcenter Installation
MT25350_S_0830
IBM DB2
11. In the Prepare the DB2 tools catalog dialog box, clear the Prepare the
DB2 tools catalog and click Next.
Teamcenter Installation
4-11
IBM DB2
12. In the Set up notifications dialog box, clear Set up your DB2 server to
send notifications and then click Next.
4-12
Teamcenter Installation
MT25350_S_0830
IBM DB2
13. In the Enable operating system security for DB2 objects dialog box,
accept the defaults and click Next.
Teamcenter Installation
4-13
IBM DB2
4-14
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-15
IBM DB2
4-16
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-17
IBM DB2
3. In the Select Instance dialog box, select your DB2 server instance and
click OK.
4-18
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-19
IBM DB2
5. In the Add License dialog box, browse to your license file, select it, and
click OK.
4-20
Teamcenter Installation
MT25350_S_0830
IBM DB2
Install IBM Data Server Driver for ODBC, CLI, and .NET
All Teamcenter servers and two-tier rich clients depend on the IBM DB2 open
database connectivity (ODBC) and call-level interface (CLI) drivers. These
drivers must be installed on each machine that runs a Teamcenter server or
two-tier rich client before the Teamcenter software is installed.
1. In the Teamcenter distribution image, double-click
additional_applications\db2_files\DSDRIVER.exe
2. Click Next.
Teamcenter Installation
4-21
IBM DB2
3. Select I accept the terms in the license agreement and click Next.
4-22
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-23
IBM DB2
5. Use the default driver name or enter a different name. Select Set this
as the default IBM database client interface copy on this computer.
Then click Next.
4-24
Teamcenter Installation
MT25350_S_0830
IBM DB2
6. Click Install.
Teamcenter Installation
4-25
IBM DB2
7. Click Finish.
4-26
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-27
IBM DB2
4-28
Teamcenter Installation
MT25350_S_0830
IBM DB2
Statement heap
Default application heap
Log buffer size
Number of primary log
files
Number of secondary log
files
Log file size
Maximum memory for
utilities
100000
16000
512
20
5
4096
150000
Teamcenter Installation
4-29
IBM DB2
3. In the Control Center dialog box, expand All Databases and select the
approprate database.
4-30
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-31
IBM DB2
4-32
Teamcenter Installation
MT25350_S_0830
IBM DB2
9. When you are finished modifying parameters, click OK. A DB2 Message
dialog box appears stating that the parameters were successfully updated.
Click Close.
Teamcenter Installation
4-33
IBM DB2
4-34
Teamcenter Installation
MT25350_S_0830
IBM DB2
Teamcenter Installation
4-35
IBM DB2
Activities
If you chose to install IBM DB2, use the dba account to perform the following
activities in the IBM DB2 (DB2 only) section:
4-36
Install IBM Data Server Driver for ODBC, CLI, and .NET
Teamcenter Installation
MT25350_S_0830
IBM DB2
Review questions
1. The IBM DB2 server installation creates which operating system user
groups:
Select two answers.
administrators
db2admns
db2leaders
db2users
2. The IBM DB2 open database connectivity (ODBC) drivers and call-level
interface (CLI) drivers must be installed on all of the following except:
Select one answer.
Corporate servers
File servers
3. You can modify database parameters using either the Control Center
or the update db cfg command.
Select one answer.
True
False
Teamcenter Installation
4-37
IBM DB2
Summary
The following topics were taught in this lesson:
4-38
How to install the IBM Data server driver for ODBC, CLI, and .NET.
Teamcenter Installation
MT25350_S_0830
Lesson
Purpose
This lesson explains the function of the Common Licensing Server and how
to install it.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Installing the license server topic in the Installation on UNIX and Linux
Servers Guide
Teamcenter Installation
5-1
5-2
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
5-3
5-4
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
5-5
5-6
Teamcenter Installation
MT25350_S_0830
5. In the Destination Folder dialog box, select the location in which to install
the Common Licensing Server. If you need to select a location other than
the default, click Change. After selecting the location, click Next.
6. In the LICENSE FILE dialog box, select the license file by clicking Browse
and navigating to the file. After selecting the file, click Next.
Teamcenter Installation
5-7
5-8
Teamcenter Installation
MT25350_S_0830
If you use multiple license servers for redundancy, separate the license server
list using commas not colons or semicolons.
Using commas assumes that all servers in the list contain the same
complete license file. When the first server is down, it checks only the
next server in the list.
For example:
UGS_LICENSE_SERVER=28000@ahsun014,28000@osnsun3,28000@vpdmsgi1
Teamcenter Installation
5-9
5-10
Teamcenter Installation
MT25350_S_0830
Activity
Perform the activity in the Common Licensing Server section using the
infodba account: Install the license server.
Teamcenter Installation
5-11
Review questions
1. The Common Licensing Server must be installed and two or more seats
must be available on that license server during Teamcenter server
installation otherwise, database creation fails.
Select one answer.
True
False
2. ________ tie(s) each user in the system to an available license and ensures
the total number of active authors and consumers in the system is always
less than or equal to the number of licenses purchased.
Select one answer.
Access rules
Database licensing
Fishing licenses
5-12
LICENSE_SERVER_ROOT
PLM_LICENSE_SERVER
TC_ROOT
UGS_LICENSE_SERVER
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Teamcenter Installation
5-13
Lesson
Corporate server
Purpose
This lesson explains the function of the Teamcenter corporate server and
how to install it.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
6-1
Corporate server
Corporate server
The corporate server is at the center of a Teamcenter site. It is the first
configuration you install for the two-tier and the four-tier architecture. It is
the first volume server.
It contains site-specific information (in TC_DATA) including, but not
limited to the data model, the default Teamcenter preferences, the RDBMS
connection information, and the dataset definitions.
The corporate server contains:
6-2
Teamcenter Installation
MT25350_S_0830
Corporate server
Teamcenter Installation
6-3
Corporate server
6-4
File transfer between volumes and clients for both the two-tier and the
four-tier architectures
File access for NX and Lifecycle Visualization when you use these
products with Teamcenter
File caching on both file servers and rich clients to improve file transfer
performance
Teamcenter Installation
MT25350_S_0830
Corporate server
FMS provides file caching on both file servers and rich clients. Both of these
components are required.
Teamcenter Installation
6-5
Corporate server
FSC
You must install an FSC server on each host that contains a volume.
Note
Server manager requires a transient volume. Therefore, each machine
running a server manager also needs an FSC server.
You can configure an FSC server to perform any combination of the following
functions. One or more FSC servers can be created for a site. When using
multiple FSC servers, they are linked by a master FSC server.
Volume server
Configuration server
Volume server
When running on a host where a volume is located or directly mounted, the
FSC server acts as a volume server.
It checks all file access requests for a ticket that Teamcenter generates to
authorize file access.
Performance cache server
When running on a host where a volume is not located or directly mounted,
the FSC server acts as a performance cache server. It manages two segment
caches, one for downloading files and one for uploading files.
It checks all file access requests for a ticket that Teamcenter generates to
authorize file access.
Configuration server
As a configuration server, the FSC server provides FMS configuration
information to the FMS client caches and other FSC servers.
Transient server (four-tier architecture only)
As a transient server, the FSC servers delivers PLM XML and other transient
files to clients.
6-6
Teamcenter Installation
MT25350_S_0830
Corporate server
Configuring FSCs
FSC servers and caches are configured using hierarchical XML-based files.
These files are created by Teamcenter Environment Manager (TEM) when
the FSC servers are created. You can configure your FMS network by using
TEM to modify these configuration values or by directly editing the XML files.
Teamcenter Installation
6-7
Corporate server
6-8
Teamcenter Installation
MT25350_S_0830
Corporate server
Teamcenter Installation
6-9
Corporate server
6-10
Teamcenter Installation
MT25350_S_0830
Corporate server
FCC
The FCC process runs on a client host and performs the following functions:
Teamcenter Installation
6-11
Corporate server
FCC installation
Rich client
The rich client requires an FCC. The FCC is automatically installed with
each rich client.
When creating the distribution server instance (the rich client software
to be installed on the client computer), you configure the location of the
cache on the workstation and the maximum size of files downloaded from
the volume or uploaded to the volume. Installing the rich client instance
on a workstation simultaneously installs the FCC process and caches. No
additional configuration steps are required.
Thin client
The thin client does not use the FCC.
However, if you install the FCC, Lifecycle Visualization and NX use it to
upload and download files from the volume.
6-12
Teamcenter Installation
MT25350_S_0830
Corporate server
File streaming
Deployment flexibility
Teamcenter Installation
6-13
Corporate server
This example shows a single server. All clients connect to this server. The
server manages all volumes.
6-14
Teamcenter Installation
MT25350_S_0830
Corporate server
This example shows multiple servers. Each server serves just one volume.
All clients can connect to all servers. To which server that a client connects
depends on which volume the client needs to reach.
Teamcenter Installation
6-15
Corporate server
This example shows multiple file servers with a caching server. Each server
servers only one volume. All clients connect to a caching server to obtain files.
The caching server can connect to all volume servers. The server to which the
caching server connects depends on which volume needs to be accessed.
6-16
Teamcenter Installation
MT25350_S_0830
Corporate server
This example shows a WAN with multiple file servers and a caching server.
Each server servers just one volume. All clients connect to a caching server
at their site to obtain files. The caching server on the client site connects to
a caching server on the server site. The caching server on the server site
can connect to all volume servers. The server to which the caching server
connects depends on which volume needs to be accessed.
Teamcenter Installation
6-17
Corporate server
Solutions
Teamcenter Environment Manager (TEM) is used to install the corporate
server. During installation, TEM prompts you to select solutions to install.
Each solution has a sets of associated features. You can select additional
features or deselect features.
The available solutions are:
6-18
Corporate Server
Installs the corporate server and allows you to create and populate a
database.
Volume Server
Installs the service that support a stand-alone volume server.
Global Services
Installs the Global Services database, preferences, and dependent
features.
Teamcenter Installation
MT25350_S_0830
Corporate server
Features
Commonly used features include:
Teamcenter Foundation
FMS Server Cache
NX UG Integration
J2EE Based Server Manager
.NET Based Server Manager
Database Daemons
Dispatch Server
Component
Teamcenter
Foundation
Description
Installs the complete Teamcenter application root
directory (TC_ROOT), including the Teamcenter
server process (tcserver), and either creates a
data directory for storing database-specific files or
configures this installation to connect to an existing
data directory.
If you create a data directory, you also provide
information about the database to use with this
installation. If you specify a new database, Teamcenter
Environment Manager populates the database and
creates a volume.
Teamcenter Installation
6-19
Corporate server
Component
NX UG Integration
Description
Configures the database to support Teamcenter
Integration for NX, the Teamcenter integration with
NX.
Database
Daemons
6-20
Teamcenter Installation
MT25350_S_0830
Corporate server
Component
Description
Service that checks user inboxes for tasks that
have passed due dates, notifies the delegated
recipients, and marks the task as late.
Installing the Task Manager Service is required to
enable notification of late tasks.
Dispatcher Server
Full Text Search
Engine
Online Help
Teamcenter Installation
6-21
Corporate server
Component
Wire Harness
Configuration
Sample files
Teamcenter
Security Service
Description
Installs Teamcenter schema support for wire
harnesses.
Installs sample source code for customizing
Teamcenter and generating reports.
This component is optional. You can install the sample
files individually; you need not install any other
components.
Configures Security Services for Teamcenter. These
services eliminate prompts for login credentials when
users switch Teamcenter products within a user
session.
Prerequisite:
Installation and configuration of Security Services.
For information about Security Services, see the
Security Services Installation/Customization
manual.
Required information:
Multisite
Installs the distributed services manager (IDSM) and
Collaboration ODS object directory service (ODS) required to replicate
and IDSM Services data between multiple Teamcenter sites, enabling
the exchange of data objects with other Teamcenter
databases over a wide area network (WAN).
If you are installing the IDSM and ODS in proxy mode,
selecting the Teamcenter Foundation component is
optional. If you are not installing in proxy mode, you
must select Teamcenter Foundation for installation.
6-22
Teamcenter Installation
MT25350_S_0830
Corporate server
Configurations
A configuration is a set of one or more solutions and features that you
choose to install. It is associated with one Teamcenter data directory. Each
configuration has an associated unique ID that you define during installation.
A single host can have one or more configurations installed on it.
Examples of configurations are the corporate server and the two-tier rich
client.
A collection of configurations that share the same Teamcenter application
root directory is a Teamcenter installation.
Teamcenter Installation
6-23
Corporate server
6-24
Teamcenter Installation
MT25350_S_0830
Corporate server
3. In the Getting Started dialog box, select Create a new installation of the
product and click Next.
Teamcenter Installation
6-25
Corporate server
6. In the Solutions dialog box, select the solutions you want to install. To
create a corporate server, select at a minimum the Corporate Server
solution. After making your selection, click Next.
6-26
Teamcenter Installation
MT25350_S_0830
Corporate server
In the Installation Directory box, type the path for the TC_ROOT
directory.
Click Next.
Teamcenter Installation
6-27
Corporate server
8. In the FSC Service dialog box, you configure the FSC service ID along
with read and write directory locations and sizes. Notice that This FSC
is an FMS master is selected because this is the first FSC you create.
Click Next.
9. In the FSC Service: Connections dialog box, you define the ports on
which the FSC service listens. It can listen on multiple port. Click Next.
6-28
Teamcenter Installation
MT25350_S_0830
Corporate server
10. In the FSC Service: FCC Defaults dialog box, you define the directory
location, maximum read and write cache sizes, maximum segment read
cache size, and external sites accessible by a client. Click Next.
11. In the FSC Service: Additional Sites dialog box, you can add additional
sites. Click Next.
Teamcenter Installation
6-29
Corporate server
12. In the FSC Service: Additional Group Sites dialog box, you can define
additional FSC groups.
13. In the FSC Deployment Model dialog box, you select the FSC deployment
model, either Simple Model or Failover Model. Click Next.
14. In the Operating System User dialog box, type and confirm the password
of the operating system account that you are using to install the corporate
server, and then click Next.
6-30
Teamcenter Installation
MT25350_S_0830
Corporate server
Type the location of the new data directory in the Data Directory
Location box. A default location is provided.
Click Next.
16. In the Database Engine box of the Database Engine Selection dialog box,
select a database engine IBM DB2, Oracle, or MS SQL Server. You are
presented with the fields appropriate for the database data engine you
selected.
Teamcenter Installation
6-31
Corporate server
17. If you chose Oracle in the Database Engine box, complete this step. If you
made a different selection, skip this step.
You can either connect to an existing database by entering the values for
the existing database or create a new database by entering new values.
6-32
In the Database Server box, type the name of the computer on which
you installed the Oracle server.
In the Service box, type the SID of the database instance you created.
In the Port box, type the port number you assigned to the listener.
The default is 1521.
In the Database User box, type the name of the database user that
owns the database. The templates create a user called infodba. This
is the Oracle user that was created when you created the database.
Click Next.
Teamcenter Installation
MT25350_S_0830
Corporate server
18. If you are creating a new Oracle database, the Create Database dialog
box appears. If you are not creating a new Oracle database, skip this step.
Click Create in the Create Database dialog box.
19. If you chose MS SQL Server in the Database Engine box, complete this
step. Otherwise, skip this step.
You can either connect to an existing database by entering the values for
the existing database or create a new database by entering new values.
In the Database Server box, type the name of the computer on which
you installed MS SQL Server.
Teamcenter Installation
6-33
Corporate server
Port and provide the port number in the associated field if you
chose default instance when creating the database server.
Click Next.
20. If you are creating a new MS SQL database, the Create Database dialog
box appears and you should proceed with the remainder of this step.
Otherwise, skip this step.
Click Create in the Create Database dialog box.
6-34
Teamcenter Installation
MT25350_S_0830
Corporate server
In the Database System User box, provide the system user name.
The default is sa.
Click Next.
22. If you selected IBM DB2 in the Database Engine box, complete this step.
Otherwise, skip this step.
You can either connect to an existing database by entering the values for
the existing database or create a new database by entering new values.
Complete the Database Engine Selection dialog box as follows:
In the Database box, enter the name of the database you created.
In the Database User box, enter the name of the operating system
account you created for the Teamcenter database.
6-35
Corporate server
6-36
Teamcenter Installation
MT25350_S_0830
Corporate server
23. If you are creating a new DB2 database, the Create Database dialog
box appears and you should proceed with the remainder of this step.
Otherwise, skip this step.
Click Create in the Create Database dialog box.
24. Complete the Create IBM DB2 Database dialog box:
In the Create IBM DB2 Database box, enter the database directory.
25. In the Volume Specification dialog box, type the volume name and
location. Click Next.
Teamcenter Installation
6-37
Corporate server
26. In the Transient Volume Settings dialog box, type the location of the
transient volume in the appropriate operating system box and click Next.
27. In the Default Site Web Server dialog box, select whether or not to define
default values for a Web server. This is used in environments that employ
the four-tier architecture. Click Next to proceed.
6-38
Teamcenter Installation
MT25350_S_0830
Corporate server
28. In the Flex License Client dialog box, provide information on how the
Common Licensing Server will be accessed.
29. In the Teamcenter Administrative User dialog box, the user name and
password are populated but not editable. Click Next.
30. In the Database Template Summary dialog box, the templates that will
be applied to the database are listed. Click Next.
Teamcenter Installation
6-39
Corporate server
31. In the Confirm Selection dialog box, you can scroll through the list of
selections you made to ensure they are correct. If you need to modify any
selection, click Prev. If your selections are correct, click Next to begin
the installation.
32. The Install Features dialog box displays the status of the installation.
Click the Show Details button to display details of the installation process.
33. If you selected to install online help, during the installation you are
prompted for the location of the tchelp.jar file. This file is located on the
Teamcenter Publications DVD. Browse to and then select this file to
continue the installation.
6-40
Teamcenter Installation
MT25350_S_0830
Corporate server
34. When the installation is complete, you see the Install Features:
Successful message.
Click Close in the Install Features dialog box to close TEM.
Teamcenter Installation
6-41
Corporate server
tc_profilevars.bat
This file is used to set environment variables used by Teamcenter.
tnsnames.ora
This file is used by Teamcenter to communicate with the Oracle server.
6-42
Teamcenter Installation
MT25350_S_0830
Corporate server
tc_profilevars.bat file
tc_profilevars.bat is a batch file that sets several environment variables
used by Teamcenter.
It is located under TC_DATA.
A portion of the file follows:
TC_DB_CONNECT
username:password@service_name
Contains the Oracle user and encrypted password used by Teamcenter to
access the database along with the Oracle service name.
UGS_LICENSE_SERVER
portnumber@servername
Points to the Common Licensing Server.
Teamcenter Installation
6-43
Corporate server
tnsnames.ora file
The tnsnames.ora file is a standard file used by Oracle clients. It provides
information needed by Teamcenter to communicate with the Oracle server. It
is located directly under TC_DATA.
A portion of the file follows:
6-44
(PROTOCOL=TCP)
(Host=vmserver)
(Port=1521)
(SERVICE_NAME = tcdev)
Teamcenter Installation
MT25350_S_0830
Corporate server
Activity
Perform the activity in the Corporate server section using the infodba
account: Install the corporate server.
Teamcenter Installation
6-45
Corporate server
Review questions
1. _________ contains the Teamcenter binary executables and files.
Select one answer.
TC_BASE
TC_DATA
TC_HOME
TC_ROOT
TC_BASE
TC_DATA
TC_HOME
TC_ROOT
Application
Corporate
Data
Volume
6-46
True
False
Teamcenter Installation
MT25350_S_0830
Corporate server
Summary
The following topics were taught in this lesson:
Teamcenter Installation
6-47
Lesson
Purpose
This lesson describes the two-tier architecture, demonstrates how to install
the two-tier rich client, and demonstrates how to start the two-tier rich client.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Installing the rich client topic in the Installation on UNIX and Linux
Clients Guide
Teamcenter Installation
7-1
7-2
Rich client.
Optional applications that integrate with the rich client such as NX.
Volumes.
File servers.
Teamcenter Installation
MT25350_S_0830
Data server exports the Teamcenter data directory to the rich client. It
communicates with the rich client using NFS and CIFS.
Teamcenter Installation
7-3
7-4
Teamcenter Installation
MT25350_S_0830
1. Install the database and database server using Oracle, MS SQL Server,
or DB2 tools.
2. Install the Teamcenter corporate server, create and/or populate the
database, and configure a volume using TEM.
3. Install the rich client on the client host using TEM.
Teamcenter Installation
7-5
3. In the Getting Started dialog box, select Create a new installation of the
product and click Next.
7-6
Teamcenter Installation
MT25350_S_0830
5. In the New Configuration dialog box, type a description and a unique ID,
and click Next.
6. In the Solutions dialog box, select the Rich Client 2-tier solution and
click Next.
Teamcenter Installation
7-7
7. In the Select Features dialog box, select the features to install, provide
the path of the installation directory, and then click Next.
8. In the FCC Settings dialog box, provide the setting used by the FCC. You
must select a value for FMS_HOME Setting.
7-8
Teamcenter Installation
MT25350_S_0830
9. In the FCC Parents dialog box, provide information about the FCCs FSC
parent. Click the Add button to add a parent. You must provide the
protocol, the host name of the parent, and the port used to connect to
the parent.
10. In the TcServer Character Encoding Settings dialog box, select the
encoding used when the TcServer accesses the database, and then click
Next.
Teamcenter Installation
7-9
11. In the 2tier Teamcenter server configurations dialog box, define how the
rich client connects to the database.
The TcServers list contains the databases to which this rich client can
connect. There can be one or more entries in this list. Click Add to add
an entry. The TC_DATA box is the path of the TC_DATA directory to use.
The Connection Name box is the value the user selects in the rich client
logon dialog box to connect to the database.
12. In the Rich ClientSettings dialog box, define the run-time temporary
folder and the rich client Web server if needed. Click Next.
7-10
Teamcenter Installation
MT25350_S_0830
13. In the Online Help dialog box, select how the rich client accesses the
online help and then click Next.
14. In the Rich Client 2tier Settings dialog box, enter the URL for the
Teamcenter Web tier. This value is required only if the two-tier rich client
must contact the Web tier.
Teamcenter Installation
7-11
15. In the Confirm Selections dialog box, review your selections. To change
any selections, click Prev and make the necessary changes. If your
selections are correct, click Next to begin the installation.
16. The Install Features dialog box displays the status of the installation.
7-12
Teamcenter Installation
MT25350_S_0830
17. When the installation is complete, the Install Features dialog box displays
the Install Features: Successful message.
Click Close in the Install Features dialog box.
Teamcenter Installation
7-13
7-14
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
7-15
The following files are used to start and configure the two-tier rich client.
They can be modified as needed.
two-tier-root\portal\portal.bat
This file is used to launch the two-tier rich client. It is the target of the
desktop icon, Teamcenter 8, created during the installation.
It starts two files: Teamcenter.exe and start_imr.bat.
two-tier-root\portal\Teamcenter.exe
This is the executable for the two-tier rich client application.
two-tier-root\iiopservers\start_imr.bat
This file is run in the TAO IMR window. It gets configuration information
from client_specific.properties and site_specific.properties.
The start_imr.bat file runs the start_TcServer1.bat file.
two-tier-root\iiopservers\start_TcServer1.bat
This file starts the TcServer.
two-tier-root\portal\templates\client_specific.properties
This file contains the server descriptions of the different databases that
are displayed in the rich client logon dialog box.
7-16
Teamcenter Installation
MT25350_S_0830
two-tier-root\portal\templates\site_specific.properties
This file is an additional properties file that can be used to modify the
two-tier rich client properties.
Teamcenter Installation
7-17
Activities
In the Two-tier rich client section, do the following activities using the
infodba account:
7-18
Create a dataset
Teamcenter Installation
MT25350_S_0830
Review questions
1. In the two-tier architecture, the client tier contains the Teamcenter server
and executables.
Select one answer.
True
False
2. The correct order in which a two-tier environment must be set up is: first
install the resource tier (for example, Oracle), then install the rich client
on the client host, and finally install the corporate server.
Select one answer.
True
False
Configuration Assistant
OUI
Over-the-Web Installer
TEM
Teamcenter Installation
7-19
Summary
The following topics were taught in this lesson:
7-20
Teamcenter Installation
MT25350_S_0830
Lesson
Purpose
This lesson describes the components of the four-tier architecture and how
they are installed.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Web tier installation topic in the Installation on UNIX and Linux Servers
Guide
Teamcenter Installation
8-1
The client tier hosts client applications, processes user interface input
and output, and secure file caches.
Available clients include:
8-2
Thin client.
Rich client.
Teamcenter Installation
MT25350_S_0830
The Web tier handles client installs, processes logon requests, routes client
requests to business logic, serves static content to clients, and handles
communication between the client and enterprise tiers.
The Web tier application can be either:
The enterprise tier hosts business logic, applies security rules, retrieves
data from and stores data in the database, and serves dynamic content to
clients.
The enterprise tier is composed of:
Transient volumes.
Standard volumes.
Teamcenter Installation
8-3
8-4
Teamcenter Installation
MT25350_S_0830
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 multi-host 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.
Teamcenter Installation
8-5
8-6
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
8-7
5. Install a four-tier rich client using the Web Application Manager and
the Over-the-Web installer.
A rich client installed using this method can point to a Teamcenter Web
tier/server manager that is either J2EE-based or .NET based.
a. Distribution server: Using the Web Application Manager, create a
distribution server. Only one distribution server is needed to manage
multiple distribution server instances.
b. Distribution server instance: Using the Web Application manager,
create a distribution server instance. A distribution server instance
contains the Over-the-Web installer and the rich client software that
is to be installed.
Create one distribution server instance for each four-tier rich client
configuration that is needed at your site.
c. Deploy the files that launch the Over-the-Web installer on an HTTP
Web server such as Apache.
d. Download and install the four-tier rich client.
On the client machine, open a Web browser and accesses the URL
for the files that launch Over-the-Web installer.
8-8
Teamcenter Installation
MT25350_S_0830
Activities
There are no activities for this lesson.
Teamcenter Installation
8-9
Review questions
1. The four-tier architecture is composed of the resource tier, the enterprise
tier, the Web tier, and the client tier.
Select one answer.
True
False
True
False
TEM
4. A four-tier rich client installed using TEM can communicate with either a
J2EE-based Teamcenter Web tier or a .NET-based Teamcenter Web tier.
Select one answer.
8-10
True
False
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Teamcenter Installation
8-11
Lesson
Purpose
This lesson describes the components of the J2EE-based server manager and
Web tier and how they are installed.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Web tier installation topic in the Installation on UNIX and Linux Servers
Guide
Teamcenter Installation
9-1
Teamcenter Installation
MT25350_S_0830
Server manager
Server manager
The server manager starts and times out a configurable number of
Teamcenter server processes to communicate with the Teamcenter database.
A server assigner process assigns available server processes to user sessions.
The server manager communicates with the Web tier application using either
TCP or multicast protocol.
If you are using a J2EE-based Teamcenter Web tier, you must use the
J2EE-based server manager. This is installed using TEM and selecting the
J2EE Based Server Manager feature. The J2EE-based server manager must
be started manually.
Server pool
The server pool is a pool of Teamcenter server processes running in the
enterprise tier. A small deployment may have only one pool of server
processes. For larger deployments, the pool of server processes is distributed
as subpools across multiple hosts, with a server manager for each subpool.
Server pools are applicable for deployments of the Teamcenter four-tier
architecture only.
Teamcenter Installation
9-3
9-4
Teamcenter Installation
MT25350_S_0830
6. In the Server Manager for J2EE Performance Tuning dialog box, set
values for the servers managed by the server manager.
7. In the Confirm Selection dialog box, you can scroll through the list of
selections you made to ensure they are correct. Click Next to begin
installing.
8. When the installation is complete, the Install Features: Successful
message appears. Click Close.
Teamcenter Installation
9-5
9-6
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
9-7
9-8
Rich client distribution instance (which includes the rich client software
and the Over-the-Web Installer)
Teamcenter Installation
MT25350_S_0830
3. In the Unzip To Folder box, type the location to which the Web Application
Manager is to be installed.
4. Click Unzip. The files in the zip file are extracted to the location you
selected.
5. Click Close.
Teamcenter Installation
9-9
9-10
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
9-11
After you build the Teamcenter Web Tier application, you can build additional
thin client solutions, including custom solutions, according to your needs.
9-12
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
9-13
4. In the Add Web Application dialog box, define the Web application.
a. In the Name box, type a unique name for the Web tier application.
b. In the Staging Location box, type the location in which to create the
Web tier application.
9-14
Teamcenter Installation
MT25350_S_0830
e. In the Disk Locations for Install Images section, provide the location
of the install images. If you need to add paths in the list, click Add. If
you need to modify a path in the list, select the path in the list and
click Modify.
f.
Note that the Solution Type box has a value of Thin Client and that
it is currently the only choice. This is because you have only copied
ICD files for the thin client. Later topics show how to copy the ICD
files required for the distribution server and the distribution server
instance.
Teamcenter Installation
9-15
5. In the Modify Context Parameters dialog box, set the required parameters.
To set a context parameter, double-click the Value box for the given
parameter and type the new value. To view a description of any context
parameter, click the parameter name in the Modify Required Context
Parameters dialog box.
After setting required context parameters, click OK.
9-16
Teamcenter Installation
MT25350_S_0830
6. The Progress dialog box appears and displays the status of the
installation. When the installation is complete, it displays the Click OK
to continue message.
The Web application you created is now in the Web Application list of the
Web Application Manager.
Teamcenter Installation
9-17
9-18
Teamcenter Installation
MT25350_S_0830
3. Start JBoss:
a. Open a Command Prompt window.
b. Type:
set JAVA_HOME=JAVA_HOME
c. Change directory to jboss-4.2.2.GA\bin.
d. Type:
run b HOSTNAME
Teamcenter Installation
9-19
9-20
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
9-21
9-22
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
9-23
9-24
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
9-25
Activities
If you chose to install the J2EE Teamcenter Web tier, use the infodba
account to perform the following activities in the J2EE-based server manager
and Web tier (J2EE only) section:
9-26
Install JBoss
Start JBoss
Teamcenter Installation
MT25350_S_0830
Review questions
1. Either the J2EE server manager or the .NET server manager can be used
with the J2EE Teamcenter Web tier.
Select one answer.
True
False
Application Manager
Universal Installer
Over-the-Web installer
Server manager
True
False
Teamcenter Installation
9-27
Summary
The following topics were taught in this lesson:
9-28
Teamcenter Installation
MT25350_S_0830
Lesson
Purpose
This lesson describes the components of the four-tier architecture and how
they are installed.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Web tier installation topic in the Installation on UNIX and Linux Servers
Guide
Teamcenter Installation
10-1
10-2
Teamcenter Installation
MT25350_S_0830
Server manager
Server manager
The server manager starts and times out a configurable number of
Teamcenter server processes to communicate with the Teamcenter database.
A server assigner process assigns available server processes to user sessions.
The server manager communicates with the Web tier application using either
TCP or multicast protocol.
If you are using a .NET-based Teamcenter Web tier, you must use the
.NET-based server manager. This is installed using TEM and selecting the
.NET Based Server Manager feature. The .NET-based server manager is
installed as a Windows service.
Server pool
The server pool is a pool of Teamcenter server processes running in the
enterprise tier. A small deployment may have only one pool of server
processes. For larger deployments, the pool of server processes is distributed
as subpools across multiple hosts, with a server manager for each subpool.
Server pools are applicable for deployments of the Teamcenter four-tier
architecture only.
Teamcenter Installation
10-3
3. In the Operating System User dialog box, provide the password for the
account that installs and maintains Teamcenter.
10-4
Teamcenter Installation
MT25350_S_0830
4. In the .NET Server Manager dialog box, provide configuration values for
the server manager.
6. In the TcServer Character Encoding Settings dialog box, select the type
of encoding that TcServer uses to access the database.
Teamcenter Installation
10-5
10-6
Teamcenter Installation
MT25350_S_0830
pool-id
Replace pool-id with the server pool ID you entered when you installed
the .NET-based server manager.
Teamcenter Installation
10-7
10-8
Is deployed on IIS
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
10-9
5. In the Select Server Roles dialog box, select Web Server (IIS) and click
Next.
10-10
Teamcenter Installation
MT25350_S_0830
7. In the Select Role Services dialog box, select the following. If you receive
a popup window asking if you want to add required role services, click
Add Required Role Services. After making the selections click Next.
Web Server
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection
Application Development
ASP.NET
.NET Extensibility
ASP
CGI
ISAPI Extensions
HTTP Logging
Logging Tools
Request Monitor
Tracing
Teamcenter Installation
10-11
Security
Basic Authentication
Windows Authentication
Digest Authentication
URL Authorization
Request Filtering
Performance
Management Tools
10-12
Teamcenter Installation
MT25350_S_0830
10-13
4. In the .NET Web Tier Client Integration panel, enter the necessary values
to configure the .NET Web tier client integrations.
10-14
Teamcenter Installation
MT25350_S_0830
10-15
10-16
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
10-17
The .NET server manager and IIS Web server must be running.
10-18
Teamcenter Installation
MT25350_S_0830
Activities
If you chose to install the .NET-based Web tier, use the infodba account to
perform the following activities in the .NETbased server manager and Web
tier (.NET only) section:
Install IIS
Teamcenter Installation
10-19
Review questions
1. The .NET server manager is installed as a Windows service.
Select one answer.
True
False
10-20
Application Manager
Universal Installer
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Teamcenter Installation
10-21
Lesson
Purpose
This lesson describes the four-tier rich client and how it is installed.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Web tier installation topic in the Installation on UNIX and Linux Servers
Guide
Install a four-tier rich client topic in the Installation on UNIX and Linux
Clients Guide
Teamcenter Installation
11-1
Over-the-Web installer
TEM
11-2
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-3
Distribution server
The distribution server:
11-4
Teamcenter Installation
MT25350_S_0830
2. Copy the ICD files needed to create the distribution server and the
distribution server instance by clicking Copy ICDs and selecting the icd
directory on the Over-the-Web installation DVD. After the files are copied,
click OK in the Progress dialog box.
3. Begin creating the distribution server by clicking Add.
Teamcenter Installation
11-5
When you select Distribution Server as the Solution Type, the only
available solution is Distribution Server.
11-6
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-7
Contains:
Over-the-Web Installer
The Over-the-Web Installer copies the rich client software to the client
machine.
11-8
Must be created for each unique four-tier rich client configuration needed
at your site.
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-9
11-10
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-11
Apache Tomcat
Sun ONE
IBM WebSphere
Microsoft IIS
For a full list of supported Web servers and versions, refer to GTAC:
http://support.ugs.com/
For details about installing and configuring a specific Web server, see that
products documentation.
For details about deploying a Teamcenter distribution instance on a specific
Web server, see the Installation on Windows Servers Guide or the Installation
on UNIX and Linux Servers Guide.
11-12
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-13
11-14
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-15
Teamcenter Installation
MT25350_S_0830
The location on user workstation in which the rich client will be installed
Users must have write permissions for this location.
For four-tier rich client instances that include support for Lifecycle
Visualization or NX, the location in which users must install those
products
Users must have administrative permissions for this location.
Teamcenter Installation
11-17
11-18
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-19
6. In the Solutions dialog box, select the Rich Client 4tier solution and
click Next.
7. In the Select Features dialog box, select any additional features that are
needed. In the Installation Directory box, type the location in which the
rich client software is to be installed. Click Next.
11-20
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
11-21
10. Define the URI and connection name that the rich client uses to connect
to the Web tier application. You can define connections to more than one
Web tier application. The rich client can connect to both J2EE and .NET
Teamcenter Web tiers.
11. Define the location of the run-time temporary folder for the rich client.
13. In the Confirm Selections dialog box, review your selections and click
Next to begin the installation.
14. When the Install Features dialog box displays the Install Features:
Successful message, click Close.
11-22
Teamcenter Installation
MT25350_S_0830
Web app server on which the Web tier is deployed (J2EE or .NET)
FSC service
So that a rich client installed using the Over-the-Web Installer can check
for updates:
Teamcenter Installation
11-23
The rich clients installed using TEM, the desktop icon name is
Teamcenter 8.
2. In the Teamcenter Login dialog box, type a user name, password, group
(optional), role (optional), select a database, and click Login.
11-24
Teamcenter Installation
MT25350_S_0830
Activities
If you chose to install the J2EEbased Web tier, use the infodba account to
perform the following activities in the Four-tier rich client section:
If you chose to install the .NETbased Web tier, use the infodba account to
perform the following activities in the Four-tier rich client section:
Teamcenter Installation
11-25
Review questions
1. _________ is used to create a distribution server and distribution server
instances.
Select one answer.
Application Manager
Universal Installer
True
False
3. The _________ contains the Over-the-Web Installer and the rich client
software to be installed on the client.
Select one answer.
Server manager
4. A four-tier rich client installed using TEM can only communicate with a
.NET Teamcenter Web tier.
Select one answer.
11-26
True
False
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Teamcenter Installation
11-27
Lesson
Purpose
This lesson demonstrates how to install the Business Modeler IDE.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Install the Business Modeler IDE topic in the Business Modeler IDE Guide
Teamcenter Installation
12-1
As a stand-alone application
This method installs the Eclipse platform.
12-2
Teamcenter Installation
MT25350_S_0830
Prerequisites
The following are required on the machine that runs the Business Modeler
IDE:
Eclipse 3.5
This is required only if you install the Business Modeler IDE into an
existing Eclipse installation.
Administrator rights
Users of the Business Modeler IDE must be members of the database
administrators (dba) group on the Teamcenter server. Use the
Organization application in the Teamcenter rich client to add a user to
the dba group.
Teamcenter Installation
12-3
12-4
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
12-5
4. If you selected the Business Modeler IDE 2tier feature, perform the
following steps in the IIOP Servers Settings panel:
a. In the Connection Port box, type the server port number. The default
is 1572.
b. Click the arrow in the Server Activation Mode box to select the mode
to use when connecting to the server. NORMAL is the default.
To allow multiple concurrent user sessions to the two-tier rich client,
select PER_CLIENT.
c. Click the ellipse button to the right of the Server Config Folder box to
select the folder where you want this configuration saved. The default
is TC_ROOT\iiopservers.
d. Click the Edit button to the right of the TcServers box to change
the server connection profile settings, or click the Add button to add
another server to connect to.
e. Click Next.
5. If you selected the Business Modeler IDE 4tier feature, perform the
following steps in the Middle-tier Servers Settings panel:
a. Leave the Compress (gzip) the responses from the Web application
servers check box selected if you want faster connection performance
from the server.
b. Click the Add button to the right of the Multi-tier Servers table if you
want to add another server to connect to.
c. Click Next.
12-6
Teamcenter Installation
MT25350_S_0830
6. Perform the following steps in the Business Modeler IDE Client panel:
a. Click the Add button to the right of the table to select the templates to
install.
Templates contain the data model for Teamcenter solutions. The
Teamcenter Foundation template is installed by default. This
template contains the data model used for core Teamcenter functions.
All customer templates must extend this template.
You must select the same templates that were installed on the
corporate server. This will ensure that the same data model definitions
that were installed on the corporate server are available in the
Business Modeler IDE .
b. If you have any templates of your own to install or a template from
a third-party, click the Browse button and browse to the directory
where the templates are located.
c. Click Next.
7. In the Java Development Kit dialog box, click the Browse button to locate
the JDK installed on your system. The kit is used for creating services.
For Teamcenter 8.3, use Java Development Kit 1.6.0_14 (JDK 6 Update
14). Click Next.
8. In the Confirm Selections dialog box, review your selections and click
Next to install.
9. When the installation is complete, click Close.
Teamcenter Installation
12-7
baselines\template-name_tcbaseline.xml
Contains a snapshot of the templates data model taken at the release of
Teamcenter 8.3.
lang\template-name_template\language_locale.xml
Contains the text that is displayed in the Business Modeler IDE user
interface for all languages.
template-name_dependency.xml
Lists the other templates that this template is built on top of, for example,
the Teamcenter Foundation template.
template-name_template.xml
Contains the data model for this template, including business objects,
classes, properties, attributes, lists of values (LOVs), and so on.
master.xml
Lists the template XML files included in the data model, for example, the
foundation_template.xml file.
12-8
Teamcenter Installation
MT25350_S_0830
cdt-master-version.zip
Unzip to the CDT directory. This contains the C/C++ Development
Toolkit (CDT) plug-ins. CDT provides the capability to work with
projects that use C or C++ as a programming language.
dtp-sdk_version.zip
Unzip to the DTP directory. This contains the Data Tools Platform
(DTP) plug-ins. DTP provides a number of tools for working with
data sources.
Teamcenter Installation
12-9
eclipse-JDT-SDK-version.zip
Unzip to the JDT directory. This contains the Java Development
Tools (JDT) plug-ins. JDT provides tools for implementing a Java
IDE.
emf-sdo-xsd-SDK-version.zip
Unzip to the EMF directory. This contains the Eclipse Modeling
Framework (EMF) plug-ins. EMF is a modeling framework and
code generation facility for building tools and other applications
based on a structured data model.
GEF-SDK-version.zip
Unzip to the GEF directory. This contains the Graphical Editing
Framework (GEF) plug-ins. GEF allows developers to take an
existing application model and create a graphical editor.
wtp-sdk-R-version.zip
Unzip to the WTP directory. This contains the Web Tools Platform
(WTP) plug-ins. WTP helps you develop Web and Java EE
applications.
NLpack1-GEF-SDK-version.zip
Contains the GEF language pack for German, Spanish, French,
Italian, Japanese, Korean, Portuguese (Brazil), Traditional
Chinese, and Simplified Chinese.
NLpack2-GEF-SDK-version.zip
Contains the GEF language pack for Czech, Hungarian, Polish,
and Russian.
NLpack2a-GEF-SDK-version.zip
Contains the GEF language pack for Danish, Dutch, Finnish,
Greek, Norwegian, Portuguese, Swedish, and Turkish.
NLpackBidi-GEF-SDK-version.zip
Contains the GEF language pack for Arabic and Hebrew.
6. Launch Eclipse by running the eclipse file from the eclipse directory.
When Eclipse opens, set the workspace if asked, and close the Welcome
tab if it appears.
12-10
Teamcenter Installation
MT25350_S_0830
Select all the items for the site and click Next to install them.
Install all the sites (CDT, DTP, and so on).
Teamcenter Installation
12-11
BusinessModelerIDE.ini file
The file is located in install-location/bmide/client/.
The Xms value in this file sets the initial Java heap size.
The Xmx value in this file sets the maximum Java heap size. The
default value is Xmx512M indicating that 512 MBs are allocated for the
maximum Java heap size. If you have more RAM available to dedicate
for this purpose, increase the value. Do this only if your machine has
the available memory.
12-12
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
12-13
Activities
In the Installi the Business Modeler IDE section, do the following activities
using the infodba account:
12-14
Teamcenter Installation
MT25350_S_0830
Review questions
1. The Business Modeler IDE is built on top of Eclipse, which is a generic
platform for tool development that is extended using its plug-in and
extension point technology.
Select one answer.
True
False
A hammer
Universal Installer
True
False
4. You can allocate memory to the Business Modeler IDE by setting Java
heap size values in which two places?
Select two answers.
BusinessModelerIDE.ini file
Teamcenter Installation
12-15
Summary
The following topics were taught in this lesson:
12-16
Teamcenter Installation
MT25350_S_0830
Lesson
Purpose
This lesson describes some of the tasks involved in administering the
in-production system.
Objectives
After you complete this lesson, you should be able to:
13-1
Help topics
Additional information for this lesson can be found in:
13-2
Utilities Reference
Teamcenter Installation
MT25350_S_0830
install utility
The install utility performs a variety of Teamcenter and database system
administration functions including:
Determine if the user can connect to the database using the current
TC_DB_CONNECT string.
Teamcenter Installation
13-3
install ayt
The install ayt command tests if the user can connect to the database
specified by the TC_DB_CONNECT variable.
If the test is successful, the command returns the message Site is already
installed. By default, no log file is generated if the command is successful.
To generate a log file, set the TC_KEEP_SYSTEM_LOG variable to TRUE.
The log file will be written to the location specified by the TC_TMP_DIR
variable and will be named install-aytnnnnnnn.syslog. Both the
TC_KEEP_SYSTEM_LOG and the TC_TMP_DIR variables can be set in
the tc_profilevars.bat file.
If the test is not successful, the command returns the message (check_db)
Failed to connect and a log file is generated regardless of the value of
TC_KEEP_SYSTEM_LOG.
To run the install ayt command:
1. Open a Teamcenter command prompt by choosing Start All Programs
Teamcenter 8 Command Prompt.
2. Type install ayt.
13-4
Teamcenter Installation
MT25350_S_0830
install ask_version
The install ask_version command returns the current version of
Teamcenter stored in the database.
To run the command:
1. Open a Teamcenter command prompt by choosing Start All Programs
Teamcenter 8 Command Prompt.
2. Type install ask_version.
Teamcenter Installation
13-5
install lock_db
The install lock_db locks the site against further log ins. Users can only
log in if they specify the dba group during log in. Users currently logged in
are not kicked off the system.
The lock remains in place until unlocked with the install unlock_db
command.
To lock the site:
1. Open a Teamcenter command prompt by choosing Start All Programs
Teamcenter 8 Command Prompt.
2. Type install lock_db u=infodba p=infodba g=dba.
To unlock the site:
1. Open a Teamcenter command prompt by choosing Start All Programs
Teamcenter 8 Command Prompt.
2. Type install unlock_db u=infodba p=infodba g=dba.
13-6
Teamcenter Installation
MT25350_S_0830
install encrypt
The install encrypt command reads the TC_DB_CONNECT variable and
outputs that connect string with the password encrypted.
To change the password that Teamcenter uses to connect to the database:
1. Open a Teamcenter command prompt by choosing Start All Programs
Teamcenter 8 Command Prompt.
2. In the Teamcenter command prompt, set the password by typing:
set TC_DB_CONNECT=infodba:password@SID
password is the value of the new password and SID is the database
system identifier.
3. Type:
install encrypt
The output of this command is in then form:
infodba:encrypted-password@SID
4. Open tc_profilevars.bat and edit the TC_DB_CONNECT string with
the new encrypted password output by the install encrypt command.
5. Save and close the tc_profilevars.bat file.
Teamcenter Installation
13-7
13-8
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
13-9
13-10
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
13-11
13-12
Teamcenter Installation
MT25350_S_0830
list_users utility
The list_users utility is used to create a list of users currently logged on to
Teamcenter and which node they are using. This information is useful if
database maintenance is necessary and all users currently logged on must
be notified.
1. Choose StartAll ProgramsTeamcenter 8ID_ID Command Prompt
to open a Command Prompt window and source environment variables.
2. In the Command Prompt window, type:
list_users -u=username -p=password -g=group
Teamcenter Installation
13-13
Datasets
A dataset is identified as corrupted if any of the following problems are found:
13-14
The dataset is an orphan (that is, the dataset refers to the anchor, but
the anchor does not go to dataset).
Teamcenter Installation
MT25350_S_0830
The dataset is not archived and the associated operating system file does
not exist.
Teamcenter Installation
13-15
Where:
user: Teamcenter users ID, optional
password: users password, optional
group: users group, optional
rf is the output report file name.
b is the anchor to start at, default is 1.
e is the anchor to end at, default is last.
13-16
Teamcenter Installation
MT25350_S_0830
Where:
user: Teamcenter users ID, optional
password: users password, optional
group: users group, optional
if is the input report file name.
of is the output report file name.
a: is used to remove empty revision anchors.
Teamcenter Installation
13-17
clearlocks utility
The clearlocks utility can be used to:
verbose
Displays a summary of processes and states:
one_pass
Executes the utility once and stops. This is the default if no other
arguments are supplied.
retry time
Continuously executes the utillity. time specifies the time in seconds
before the next execution.
node_names
Creates a report of all network nodes that are logged on to the database.
assert_dead nodename
Clears all process locks, dead or alive originating from nodename.
assert_all_dead
Clears all process locks, dead or alive.
h
Displays help for this utility.
13-18
Teamcenter Installation
MT25350_S_0830
fccstat
The fccstat utility can be used to:
help or h or ?
Displays help for this utility. Help can be localized if the FCC is running.
x
Prints FCC cache statistics summary, including whole file read, whole file
write, and segment cache statistics. In addition, this option displays all
offline FSC connections. Offline FSC connections are those that have been
attempted and failed but have not yet been restored to service.
status
Prints FCC status and statistics summary, including whole file read,
whole file write, and segment cache statistics, as well as client request
statistics, FSC upload and download statistics, and the currently active
assigned FSC. Assigned FSCs are listed as active by default, even if they
have never been used. FSC addresses that have been attempted and
failed, but have not yet been restored to service, are reported as offline.
config
Displays the name of the local FCC configuration file used for
bootstrapping.
purge
Purges all files from the FCC cache, including the segment cache extent
files.
clear
Purges the cache completely. This removes all data but retains the
segment cache extent files.
Teamcenter Installation
13-19
reconfig
Reloads the FCC configuration. Use this option to update a running FCC
with changes made to the local FCC XML configuration files.
restart
Stops (if running) and restarts the FCC, effectively reloading the
configuration. Environment variables still override any configuration file
settings or changes.
start
Starts the FCC if it is not already started.
stop
Shuts down the FCC process immediately if no other clients are connected
or if all connected clients are idle. Otherwise, a warning message is
displayed.
kill
Immediately and unconditionally shuts down the FCC process.
13-20
Teamcenter Installation
MT25350_S_0830
fscadmin
The fscadmin utility monitors and controls File Management System FSC
servers. It can be used to:
Shutdown a server
Teamcenter Installation
13-21
fscadmin syntax
Syntax:
fscadmin [h] [k keyfile] [-s serveraddr] [-f tickets-file] [command]
Arguments for fscadmin:
h
Displays help for this utility.
k
[Optional] Specifies a file containing the encryption key required by this
system. A key file is a text file containing an ASCII-HEX encryption key.
This is generally the same key file referenced in the fmsmaster.xml file
for this system.
s
Specifies the protocol server for the FSC and the port you wish to
communicate with.
f
Specifies the name of the tickets file. The tickets file is created using the
generate_loadfsccache_tickets utility.
command
Command is a formatted string with the following fields:
FSCID/FUNCTION[/SUBFUNCTION/]
FSCID
The FSC with the given ID, as defined in the master configuration, for
which this command is intended. A period (.) can be used to indicate the
local (current) FSC you are connecting to, as indicated by the -s parameter.
FUNCTION[/SUBFUNCTION/]
The functions and subfunctions are described in the following topic.
13-22
Teamcenter Installation
MT25350_S_0830
cachesummary
Summary of the read and write caches (number of files, bytes, hits,
misses).
loadfsccache/filelist
Uses -f option to upload a file of tickets that should be populated into
the specified FSC.
log
Dumps the current logfile contents.
purgecache
Purges the caches, reclaiming disk space.
shutdown
Stops the FSC when it becomes idle (when all current file transfers are
complete). The FSC will reject all new incoming file requests.
shutdown/maxwait/xxx
Stops the FSC when it becomes idle (when all current file transfers are
complete) or when a maximum number of seconds have been exceeded.
The FSC will reject all new incoming file requests. If the server does
not become idle, xxx is the number of seconds to wait before forcing the
shutdown.
status
Displays simple status about the FSC (FSCID, site, running time) and also
prints the number of concurrent admin and file-based connections. This
also shows the remaining time before a forced shutdown, if one is pending.
version
Prints the versions of the FSC JAR files.
Teamcenter Installation
13-23
fscadmin examples
cachesummary
The following command returns the statistics of the caches:
fscadmin s http://server:port ./cachesummary
Example output:
Cache summary: myfsc-FSCReadMap
Files: 0, Bytes: 0, Hits: 0, Misses: 0
Cache summary: myfsc-FSCWriteMap
Files: 0, Bytes: 0, Hits: 0, Misses: 0
loadfsccache/filelist
The following command prepopulates FSC:
fscadmin s http://server:port -f ticketsfile ./loadfsccache/filelist
purgecache
The following command purges the FSC cache.
fscadmin s http://server:port ./purgecache
shutdown/maxwait/xxx
The following command causes an idle shutdown, waiting no more than
1 hour:
fscadmin s http://server:port ./shutdown/maxwait/3600
13-24
Teamcenter Installation
MT25350_S_0830
Standard volumes
A standard volume:
Is the location in which a file is created when a user creates a file from
the rich client.
At least one standard volume is required per database. You create this
first standard volume in TEM while installing the corporate server.
You can create additional standard volumes using the rich client
Organization application.
Teamcenter Installation
13-25
4. Select Volumes in the list or select a particle volume to open the volume
dialog box.
If you select Volumes, the dialog box is not populated. You can provide the
information for a new volume and click Create to create a new volume.
If you select a particular volume, the information for this volume
populates the dialog box. You can perform any of the following:
You define:
a. Volume Name specifies the volumes name.
b. Node Name specifies the machine hosting the volume.
13-26
Teamcenter Installation
MT25350_S_0830
FSC Path Name specifies the path to the FMS server cache (FSC).
This field is not required.
j.
Accessors specifies the groups and users that have access to the
volume.
Teamcenter Installation
13-27
13-28
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
13-29
Purge volumes
A Teamcenter user can delete a Teamcenter object but may not have sufficient
privilege to delete the physical file associated with the object. While such
orphaned files are not harmful, they consume disk space and can accumulate
over a period of time.
The purge_volumes utility deletes files related to deleted Teamcenter objects.
1. Choose StartAll ProgramsTeamcenter 8ID_ID Command Prompt
to open a Command Prompt window and source environment variables.
2. In the Command Prompt window, type:
purge_volumes -u=user -p=password -g=group -f s=sleepTime
Where:
user: Teamcenter user ID
password: users password
group: users group
f: forces delete without prompting.
s: is for looping.
13-30
With s the utility loops, waiting between runs for sleepTime seconds.
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
13-31
Running review_volumes
1. Choose StartAll ProgramsTeamcenter 8ID_ID Command Prompt
to open a Command Prompt window and source environment variables.
2. In the Command Prompt window type:
review_volumes -u=user -p=password -g=group
-v=volume -rf=file -if=file -of=file -zf=file
Example:
review_volumes u=infodba p=infodba g=dba rf=review
Where:
user: Teamcenter user ID
password: users password
group: users group
volume: Teamcenter volume
file: file name
rf: report file name (required)
if: input report file name
of: output file name
zf: archive file name
13-32
Teamcenter Installation
MT25350_S_0830
backup.xml
backup.dtd
Teamcenter Installation
13-33
Run backup_xmlinfo
1. Choose StartAll ProgramsTeamcenter 8ID_ID Command Prompt
to open a Command Prompt window and source environment variables.
2. In the Command Prompt window, type:
backup_xmlinfo -u=user -p=password -g=group
Where:
user: Teamcenter users ID, optional
password: users password, optional
group: users group, optional
13-34
Teamcenter Installation
MT25350_S_0830
Activities
In the Administer the in-production system section, do the following activities
using the infodba account:
Create a volume
Teamcenter Installation
13-35
Review questions
1. You can create additional volumes using the Organization application.
Select one answer.
True
False
True
False
3. One way that a dataset is identified as corrupted is that the dataset has
no reference to a file managed by Teamcenter.
Select one answer.
True
False
13-36
clearlocks
install
list_users
password
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Purge volumes
Teamcenter Installation
13-37
Lesson
Purpose
This lesson describes how to install and prepopulate an FSC performance
cache server.
Objectives
After you complete this lesson, you should be able to:
Update the FMS master with the FSC performance cache server.
Help topics
Additional information for this lesson can be found in:
Utilities Reference
Teamcenter Installation
14-1
14-2
Enables placing the data close to the user, while maintaining a central file
volume and database store.
Checks all file access requests for a ticket that Teamcenter generates to
authorize file access.
Manages two segment caches, one for downloading files and one for
uploading files.
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
14-3
Click Next.
9. In the FSC Service: Connections dialog box, set the protocol and port
for the service.
14-4
Teamcenter Installation
MT25350_S_0830
10. In the FSC Non-Master Settings dialog box, enter the protocol, hostname,
and port of the FSC master.
11. In the Operating System User dialog box, enter the password of the
operating system account being used to install the performance cache
server.
12. In the Confirm Selections dialog box, verify your selections and click Next.
13. When the Install Features: Successful message is displayed, click Close.
Teamcenter Installation
14-5
6. The FSC Service displays the messages: An FSC is installed and FSC is
configured as a master. Click Next.
7. In the FSC Service: FCC Defaults dialog box you can change FCC client
setting if necessary. Click Next.
14-6
Teamcenter Installation
MT25350_S_0830
8. In the FSC Groups dialog box you can add, edit, and delete Fsc groups if
necessary. Click Next.
9. In the FSC Servers dialog box, add the performance cache server by
clicking Add.
Teamcenter Installation
14-7
10. In the Create/Edit FSC Server dialog box, enter information for the
performance cache server:
a. In the FSC ID box, enter the FSC ID. This is the value you entered in
the Server ID box in the FSC Service dialog box in TEM when creating
the performance cache server.
b. In the FSC Group box, select the FSC group to which the performance
cache server is to be a member.
c. In the Host box, enter the host on which the performance cache server
is installed.
d. In the Server Type box, select Non-Master FSC Server.
e. Select the protocol and port for the performance cache server. You
defined these in the FSC Service: Connections dialog box in TEM
when creating the performance cache server.
f.
14-8
Click OK.
Teamcenter Installation
MT25350_S_0830
11. In the FSC Servers dialog box, verify that the performance cache server is
now listed and click Next.
12. In the FSC Client Map dialog box, select an FSC group and click Edit.
Teamcenter Installation
14-9
13. In the FSC ID list, select the ID of the performance cache server and click
OK.
14. In the FSC Client Map dialog box, verify that the performance cahe server
is listed and click Next.
15. In the File Store Group dialog box, you can assign volumes to files stores
groups if needed. Click Next.
16. In the Volume Query dialog box, click Next.
17. In the Confirm Selections dialog box, verify your selections and click Next.
18. When the Install Features: Successful message is displayed, click Close.
14-10
Teamcenter Installation
MT25350_S_0830
19. Open the FMS master file in a plain text editor. This file is in
TC_ROOT\fsc.
20. Before the line:
</fccdefaults>
add this line:
<property name=FCC_EnableDirectFSCRouting value=false
overridable=false />
21. Save and close the file.
22. Stop and restart the FSC services.
Teamcenter Installation
14-11
14-12
Or, generate a tickets file using the load_fsccache command with the
f=list option. Then load the tickets file using the load_fsccache
command with the f=load option.
Teamcenter Installation
MT25350_S_0830
Use the -item option to specific the item. This option requires that you
use the items ID as the value for the -item option.
Use the -rev_rule option to specify the revision rule to use. You can use
Latest Working or you can substitute your own revision rule. For more
information on revision rules, refer to the Structure Manager Guide.
Teamcenter Installation
14-13
14-14
Teamcenter Installation
MT25350_S_0830
Use plmxml to specify the file containing the list of files to generate
tickets for.
For example:
load_fsccache u=infodba p=infodba g=dba
f=list plmxml=J:\temp\export_000004.xml
output_file=J:\temp\000004_readticket.xml
Teamcenter Installation
14-15
14-16
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
14-17
Activities
In the FMS performance cache server section, do the following activities using
the infodba account:
14-18
Teamcenter Installation
MT25350_S_0830
Review questions
1. To install a performance cache server, in TEM select the ____ feature.
Select one answer.
FMS Process
Performance Cache
2. A performance cache server checks all file access requests for a ticket that
Teamcenter generates to authorize file access.
Select one answer.
True
False
plmxml_export
load_fsccache f=list
load_fsccache f=load
Teamcenter Installation
14-19
Summary
The following topics were taught in this lesson:
14-20
Updating the FMS master with the FSC performance cache server.
Teamcenter Installation
MT25350_S_0830
Lesson
Purpose
This lesson describes how to install and access Teamcenter online help.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
15-1
Web server
Online help is installed on a Web server and accessed using HTTP
protocol.
Direct access
Online help is installed on a local host or a network file location and
accessed using FILE protocol. This is option is not available for the thin
client.
15-2
Teamcenter Installation
MT25350_S_0830
Install Teamcenter online help using TEM. You can create a new
configuration or add online help to an existing one. This places online
help files in the TC_ROOT\help directory. To do this, add the Online
Help feature in the Select Features dialog box in TEM.
2. Set permissions for the online help directory (help) to allow access by
Teamcenter hosts.
Teamcenter Installation
15-3
15-4
Teamcenter Installation
MT25350_S_0830
Click OK.
In the Connections list, under Sites, select the help virtual directory.
In the File name extension box of the Add MIME Type dialog box,
enter:
.cfs
Be sure to include the dot (.) at the beginning of the string.
Click OK.
Follow the same steps to add the extension .jqf with the type set to
application/octet-stream.
In the MIME Types list, locate the .prm extension and verify that its
MIME Type value is application/octet-stream.
Teamcenter Installation
15-5
5. In the IIS Manager dialog box, right-click the server name, choose All
Tasks, and then choose Restart IIS.
6. Ensure that Restart Internet Services on HOST is selected, and then
click OK.
15-6
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
15-7
15-8
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
15-9
15-10
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
15-11
Current Application for help on the application you are running only.
15-12
Teamcenter Installation
MT25350_S_0830
Activities
If you chose to install the J2EE Teamcenter Web tier, do the following
activities using the infodba account in the Teamcenter online help section:
If you chose to install the .NET Teamcenter Web tier, do the following
activities using the infodba account in the Teamcenter online help section:
Teamcenter Installation
15-13
Review questions
1. You can launch Teamcenter online help from a rich client.
Select one answer.
True
False
Distribution server
15-14
True
False
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Teamcenter Installation
15-15
Lesson
Purpose
This lesson describes how to install Teamcenter integrations with Microsoft
Office.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
16-1
Client for Office is independent of the Teamcenter rich client and thin
client. You can work in Client for Office while either Teamcenter client is
running. Or, you can work solely through Client for Office without running a
Teamcenter client. Client for Office requires either the J2EE or the .NET the
four-tier Teamcenter server configuration.
16-2
Teamcenter Installation
MT25350_S_0830
Libraries:
If you are installing Client for Office as a plugin for Microsoft Office separate
from the four-tier rich client, the installation wizard checks for the required
versions of these libraries on your host and installs them if they are not
present.
If you are installing Client for Office using TEM or the Over-the-Web Installer,
you must install the prerequisite software before you install Client for Office.
Teamcenter Installation
16-3
16-4
If the four-tier rich client is installed using TEM, add the Office Client
for Microsoft Office feature.
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
16-5
16-6
Host is the machine running the Teamcenter Web tier. This can be
either a J2EE or a .NET four-tier server configuration.
Port is the port used by the Web application server on which the
Teamcenter Web tier is deployed.
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
16-7
Install Client for Microsoft Office using the Web Application Manager
1. Launch the Web Application Manager.
2. You can add Client for Microsoft Office to either an existing distribution
server instance or create a new distribution server instance:
16-8
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
16-9
16-10
Teamcenter Installation
MT25350_S_0830
Host is the machine running the Teamcenter Web tier. This can be
either a J2EE or a .NET four-tier server configuration.
Port is the port used by the Web application server on which the
Teamcenter Web tier is deployed.
Teamcenter Installation
16-11
16-12
Teamcenter Installation
MT25350_S_0830
10. (Optional) In the Teamcenter FCC Proxy Settings dialog box, you can
define an HTTP proxy and/or an HTTPS proxy.
11. In the Teamcenter FCC Parent settings panel, add an FCC parent by
clicking Add.
Teamcenter Installation
16-13
12. Add the information for the FCC parent to which the FCC will connect.
Then click OK.
16-14
Teamcenter Installation
MT25350_S_0830
13. The FCC parent is now listed in the Teamcenter FCC Parent settings
panel. Click Next.
14. In the Choose Destination Location panel, select the folder in which to
install Office Client and then click Next.
15. In the Start Copying Files dialog box, click Next.
16. In the InstallShield Wizard Complete dialog box, click Finish.
Teamcenter Installation
16-15
16-16
Teamcenter Installation
MT25350_S_0830
Libraries:
If you are installing Extensions for Office as a plugin for Microsoft Office
separate from a rich client, the installation wizard checks for the required
versions of these libraries on your host and installs them if they are not
present.
If you are installing Extensions for Office using TEM or the Over-the-Web
Installer, you must install the prerequisite software before you install Client
for Office.
Teamcenter Installation
16-17
16-18
If the four-tier rich client is installed using TEM, add the Teamcenter
Extensions for Microsoft Office feature.
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
16-19
4. In the 4-tier Teamcenter server configuration panel, enter the URL of the
Teamcenter Web tier and the connection name to use.
16-20
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
16-21
Teamcenter Installation
MT25350_S_0830
Integration for Office is independent of the Teamcenter rich client and thin
client. You can work in Integration for Office while either Teamcenter client
is running. Or, you can work solely in Integration for Office without running
a Teamcenter client.
Teamcenter Installation
16-23
16-24
Teamcenter Installation
MT25350_S_0830
If the rich client is installed using TEM, add the MS Office for Rich Client
feature.
If the rich client is installed using the Over-the-Web installer, add the
MS Office Integration for Rich Client 4-Tier solution to the distribution
server instance.
Teamcenter Installation
16-25
3. In the MS Office for Rich Client panel, enter the URL for webdav. The
general form is:
http://HOSTNAME:port/tc-app-name/webdav
HOSTNAME is the machine running the Web application server on which
the Teamcenter Web tier application is deployed.
port is the port of the Web application server on which the Teamcenter
Web tier application is deployed.
tc-app-name is the name of the deployed Teamcenter Web tier application.
16-26
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
16-27
Network Folders
Teamcenters Network Folders allows you to manage Teamcenter workspace
objects directly through Microsoft Windows Explorer in Microsoft Windows
2000, XP, Vista, and 7. Custom Teamcenter menu commands are added to
Windows Explorer.
Network Folders is independent of the Teamcenter rich client and thin
client. You can work in Network Folders while either Teamcenter client is
running. Or, you can work solely through Network Folders without running
a Teamcenter client.
Network Folders requires that either the J2EE or the .NET four-tier
Teamcenter server configuration is installed.
16-28
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
16-29
5. The browser displays a Web page with information about Network Folders.
16-30
Teamcenter Installation
MT25350_S_0830
6. You can verify that Network Folders was installed by opening Windows
Explorer. In the list of drives, you will see one called Teamcenter.
Teamcenter Installation
16-31
Activities
If you chose to install the J2EE Teamcenter Web tier, do the following
activities using the infodba account in the Microsoft Office interfaces section:
J2EE only: Install Microsoft Office interfaces in a four-tier rich client that
was installed using the Over-the-Web Installer
J2EE only: Test the Microsoft Office interfaces in a four-tier rich client
that was installed using the Over-the-Web Installer
If you chose to install the .NET Teamcenter Web tier, do the following
activities using the infodba account in the Microsoft Office interfaces section:
16-32
.NET only: Test Microsoft Office interfaces in a four-tier rich client that
was installed using TEM
Teamcenter Installation
MT25350_S_0830
Review questions
1. Teamcenters ____ adds the custom Teamcenter ribbon to Microsoft Office
2007 applications such as Word.
Select one answer.
Network Folders
Network Folders
Network Folders
Teamcenter Installation
16-33
16-34
Network Folders
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Teamcenter Installation
16-35
Lesson
17 Embedded visualization
Purpose
This lesson demonstrates how to add embedded visualization to two-tier and
four-tier rich clients.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
17-1
Embedded visualization
Embedded visualization
The Teamcenter rich client has an embedded viewer with basic capabilities
called the Foundation viewer. This view requires no installation beyond the
basic rich client installation.
Teamcenter has a viewer with additional capabilities beyond that of the
Foundation viewer. This is the Lifecycle Visualization application. This
viewer can be embedded in the rich client to provide enterprise-wide product
visualization capabilities.
To incorporate the Lifecycle Visualization viewer into a rich client, you must:
For a rich client (two-tier or four-tier) installed using TEM, add the
Teamcenter Visualization 8 (Embedded) for Rich Client feature to the
configuration using TEM.
You can install Teamcenter 8.3 Lifecycle Visualization application on
the client machine before running TEM. Or you can have TEM install
the viewer.
17-2
Teamcenter Installation
MT25350_S_0830
Embedded visualization
Teamcenter Installation
17-3
Embedded visualization
17-4
Teamcenter Installation
MT25350_S_0830
Embedded visualization
Teamcenter Installation
17-5
Embedded visualization
9. in the Confirm Selections dialog box, review your selections and click
Next.
17-6
Teamcenter Installation
MT25350_S_0830
Embedded visualization
Teamcenter Installation
17-7
Embedded visualization
17-8
Teamcenter Installation
MT25350_S_0830
Embedded visualization
Teamcenter Installation
17-9
Embedded visualization
5. In the Add Solutions dialog box, select one of the following and then
click OK.
17-10
Teamcenter Installation
MT25350_S_0830
Embedded visualization
TcVisWindowsLocation
This is the location on the client in which the embedded viewer
was installed. This is used only if the Teamcenter Visualization 8
(Embedded) for Rich Client 4tier (Configuration only) solution is
selected.
TcVisUnixLocation
This is the location on the client in which the embedded viewer
was installed. This is used only if the Teamcenter Visualization 8
(Embedded) for Rich Client 4tier (Configuration only) solution is
selected.
EmbVisLicenseLevel
This is used to set the license level for the embedded viewer. Options
are Base, Standard, Professional, Mockup.
Teamcenter Installation
17-11
Embedded visualization
Activities
If you chose to install the J2EE Web tier, use the infodba account to perform
the following activities in the Embedded visualization section:
If you chose to install the .NET Web tier, use the infodba account to perform
the following activities in the Embedded visualization section:
17-12
.NET only: Add embedded visualization to a four-tier rich client that was
installed using TEM
Teamcenter Installation
MT25350_S_0830
Embedded visualization
Review questions
1. Teamcenter has a viewer that can be added to the rich client to provide
enterprise-wide product visualization capabilities and is embedded in the
rich client interface.
Select one answer.
True
False
True
False
Teamcenter Installation
17-13
Embedded visualization
Summary
The following topics were taught in this lesson:
17-14
Add the embedded visualization feature to a rich client using the Web
Application Manager
Teamcenter Installation
MT25350_S_0830
Lesson
Purpose
This lesson demonstrates how to add Teamcenter Integration for NX to
two-tier and four-tier rich clients.
Objectives
After you complete this lesson, you should be able to:
Install NX.
Add the NX Manager for Rich Client feature to a rich client using TEM.
Add the NX Manager for Rich Client 4Tier solution to a four-tier rich
client using the Web Application Manager.
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
18-1
18-2
Teamcenter Installation
MT25350_S_0830
Install NX 7.5.2
1. Start the installation program by double-clicking Launch.exe from the
NX 7.5 installation image.
2. Click Install NX.
3. In the UGS NX7.5 - InstallShield Wizard dialog box, select the installation
language and click OK.
4. In the Welcome dialog box, click Next.
5. In the Setup Type dialog box, select Typical and click Next.
6. Choose a destination directory and the click Next.
7. Set the port and server used to connect to the license server. Type
28000@hostname where hostname is the name of the computer on which
the license server is installed.
Click Next.
8. Select the language in which you wish to run NX and click Next.
9. Review the settings and then click Install.
NX installs.
10. When the installation is completed, click Finish.
11. Click Exit to install the install wizard.
12. Install the NX 7.5.2 update by double-click run_ugsupdate.exe in the NX
7.5.2 update image.
13. If you receive a Security Warning dialog box, click Run.
14. A Command Prompt window opens to execute the update.
15. When the update is complete, the Command Prompt window displays the
message Press any key to continue. Press any key.
The NX application is installed on the client machine.
Teamcenter Installation
18-3
NX templates
Templates are used to begin model and drawing construction. The templates
are available in the File New dialog box. They function as a basis for
creating/developing/modeling an item. The templates are grouped by tabs.
The templates are specific to the type of item you want to create. When you
create an item using a template, the associated application for the template is
opened. For example, if you use a drawing template, the Drafting application
is opened, or if you create an assembly, the Add Component dialog box
is displayed.
The templates are located in the UGII_BASE_DIR\ugii\templates
directory.
18-4
Teamcenter Installation
MT25350_S_0830
Install NX templates
After Teamcenter and NX are installed, you can install the NX templates.
1. Choose StartAll ProgramsTeamcenter
8config_id_config_idCommand Prompt.
The value of config_id is the value of ID you provided when creating the
Teamcenter configuration in TEM.
2. In the Command Prompt window, enter the following command:
%UGII_BASE_DIR%\ugii\templates\sample\tcin_template_setup.bat
-u=infodba -p=infodba
Teamcenter Installation
18-5
Add NX Manager for Rich Client feature to a rich client using TEM
1. Start TEM for the rich client (two-tier or four-tier) to which you want to
add the NX Manager for Rich Client feature.
2. Select Configuration Manager and click Next.
3. In the Configuration Maintenance dialog box, select Perform maintenance
on an existing configuration and click Next.
4. In the Configuration Selection dialog box, select the configuration to
which the feature is to be added and click Next.
5. In the Feature Maintenance dialog box, select Add/Remove Features
and click Next.
6. In the Select Features dialog box, expand ExtensionsEngineering
Process Management, select NX Manager for Rich Client, and then click
Next.
7. In the NX Manager for Rich Client dialog box, provide the path to the NX
installation and click Next.
8. In the Confirm Selection dialog box, confirm your selections and begin
the installation and click Next.
9. When the installation is complete, the Install Features: Complete
message appears. Click Close.
18-6
Teamcenter Installation
MT25350_S_0830
NXWindowsLocation
The location on Windows clients in which NX is installed.
NXUnixLocation
The location on UNIX clients in which NX is installed.
NXVersion
The version of NX that is installed on the client.
Teamcenter Installation
18-7
18-8
Teamcenter Installation
MT25350_S_0830
Activities
If you chose to install the J2EE Web tier, use the infodba account to perform
the following activities in the Teamcenter Integration for NX section:
All: Install NX
J2EE only: Download NX Manager for Rich Client to a four-tier rich client
that was installed using the Over-the-Web Installer
If you chose to install the .NET Web tier, use the infodba account to perform
the following activities in the Teamcenter Integration for NX section:
All: Install NX
Teamcenter Installation
18-9
Review questions
1. NX 7.5.2 uses the Teamcenter Common Licensing Server.
Select one answer.
True
False
18-10
tcin_template_setup.bat
NX
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Install NX
Add the NX Manager for Rich Client feature to a rich client using TEM
Teamcenter Installation
18-11
Lesson
Purpose
The purpose of this lesson is to illustrate how to create an additional
Teamcenter site.
Objectives
After you complete this lesson, you should be able to:
Configure FMS master to include the initial and the additional sites.
Create a J2EE server manager and J2EE Teamcenter Web tier application
for the new site
Create a .NET server manager and .NET Teamcenter Web tier application
for the new site
Modify a four-tier rich client that was installed using the Over-the-Web
Installer to point to both sites
Modify a four-tier rich client that was installed using TEM to point to
both sites
Help topics
Additional information for this lesson can be found in:
19-1
19-2
Add, remove, and modify database topic in the Installation on UNIX and
Linux Clients Guide
Teamcenter Installation
MT25350_S_0830
For four-tier rich clients installed using TEM, modify the four-tier
rich client using TEM.
Teamcenter Installation
19-3
19-4
Teamcenter Installation
MT25350_S_0830
7. In the Scan for Sites dialog box, verify that there is an FSC entry for
the new site and click OK.
8. In the FSC Service: Additional Sites dialog box the new site is now listed.
Click Next.
9. In the FSC Service: Additional Group Sites dialog box, click Next.
10. A Status Message dialog box appears informing you that the FMS service
must be restarted for changes to take affect. Click Close.
11. Click Next in the Confirmation dialog box to begin the installation.
12. When the installation is complete, the Install Features: Success
messages appears. Click Close.
13. Restart the FSC services for the initial and the additional corporate server.
Teamcenter Installation
19-5
19-6
Teamcenter Installation
MT25350_S_0830
7. In the TC_DATA box of the Edit dialog box, type the path to the TC_DATA
directory of the additional site.
In the Connection Name box, type a connection name. This is the value
displayed in the rich client log on page.
Click OK in the Edit dialog box.
Teamcenter Installation
19-7
J2EE server manager and Teamcenter Web tier application for the
new site
The new site must have its own server manager and Teamcenter Web tier
application. The following values must be unique for both the existing site
and the new site:
19-8
The Tree Cache Cluster Name used at each site must be unique. This
value is used when installing the server manager and when creating the
Teamcenter Web tier application.
If Multicast Mode is used, the new server manager must have a unique
TreeCache Cluster Port value. Any Teamcenter Web tier applications
that connect to this server manager must use the same value as the
server manager.
If TCP Mode is used, the new server manager must have a unique Local
Service Port value. Additionally, The Teamcenter Web tier application
must have its own unique Local Service Port value.
Teamcenter Installation
MT25350_S_0830
J2EE server manager and Teamcenter Web tier application for the
new site
For example, if the first site uses the following values:
Teamcenter Installation
19-9
Enter a JMX HTTP Adaptor Port. The new server manager can use
the same port as the first server manager.
Enter the name of the machine on which the new server manager is
installed in the Server Host box.
If you are using Multicast Mode, enter a unique value for TreeCache
Cluster Port.
If you are using TCP Mode, enter a unique value for Local Service
Port.
In the TreeCache Peers list, enter the Host and Port values for any
Teamcenter Web tier applications that will need to connect to this
server manager.
Host is the machine on which the Teamcenter Web tier application
is deployed.
19-10
Port is the local service port of the Teamcenter Web tier application.
Teamcenter Installation
MT25350_S_0830
9. In the Server Manager for J2EE Performance Tuning dialog box, set the
number of minimum warm servers, maximum started servers, server
targets, logins per minute, and CPU load. Click Next.
10. Click Next in the Confirmation dialog box to begin the installation.
11. When the installation is complete, the Install Features: Success
messages appears. Click Close.
Teamcenter Installation
19-11
Create the J2EE Teamcenter Web tier application for the new site
1. Start the Web Application Manager.
2. Click Add.
3. In the Add Web Application dialog box, provide a unique Name, a unique
Staging Location, and a Description.
4. In the Add Web Application dialog box, click Advanced Web Application
Options and provide a unique value for the Deployable File Name and
click OK.
5. In the Add Web Application dialog box, ensure that the path to Web_tier
in the Teamcenter distribution image is listed in the Disk Locations for
Install Images list.
6. In the Add Web Application dialog box, select Thin Client for Solution
Type.
7. In the Add Web Application dialog box, select the following for Selected
Solutions:
19-12
Teamcenter Installation
MT25350_S_0830
If Mcast is selected, set TreeCache Cluster Port to the value used for
TreeCache Cluster Port when installing the server manager to which
this Teamcenter Web tier application will connect. If Mcast is not
selected, the TreeCache Cluster Port value is not used.
If TCP is selected, set Local Service Port for the Teamcenter Web
tier application to a unique value. If TCP is not selected, the Local
Service Port value is not used.
If TCP is selected, set TreeCache Peers to the values for the new
server manager. The general form is host[port]. host is the machine on
which the new server manager is installed. port is the local service
port of the new server manager.
Teamcenter Installation
19-13
.NET server manager and Teamcenter Web tier application for the new
site
The new site must have its own server manager and Teamcenter Web tier
application. The following values must be unique for both the existing site
and the new site:
19-14
The new Teamcenter Web tier application must have a unique name.
Teamcenter Installation
MT25350_S_0830
.NET server manager and Teamcenter Web tier application for the new
site
For example, if the first site uses the following values:
Teamcenter Installation
19-15
Select Specify Server Host dialog box and enter the name of the
machine on which the new server manager is installed.
8. In the Server Manager for J2EE Performance Tuning dialog box, set the
number of minimum warm servers, maximum started servers, server
targets, logins per minute, and CPU load. Click Next.
9. In the TcServer Character Encoding Settings dialog box, set the encoding
type and click Next.
10. Click Next in the Confirmation dialog box to begin the installation.
19-16
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
19-17
19-18
Teamcenter Installation
MT25350_S_0830
8. In the .NET Web Tier Client Integration dialog box, click Next.
9. In the Internet Information System (IIS) settings dialog box, enter the
appropriate information. The Virtual Directory Name box sets the name
of the Teamcenter Web tier application. This must be unique.
10. In the Confirm Selections dialog box, click Next.
11. When the installation is complete, close TEM.
Teamcenter Installation
19-19
4. In the Modify Tables dialog box, select HTTPServerTable and click OK.
19-20
Teamcenter Installation
MT25350_S_0830
URI
The general form is http://host:port/tc-web-tier-app-name
host is the machine on which the Web application server is running.
port is the port of the Web application server.
tc-web-tier-app-name is the name of the new Teamcenter Web tier
application.
Name
Is the connection name displayed in the rich client login page.
SSOAppID
(Optional) Provides the Teamcenter application ID and sets the
TC_SSO_APP_ID environment variable for Security Services.
7. The new sites Teamcenter Web tier application is added. Click OK.
Teamcenter Installation
19-21
19-22
Teamcenter Installation
MT25350_S_0830
Modify a four-tier rich client installed using TEM to point to both sites
1. Start the TEM for the four-tier rich client.
2. In the Maintenance dialog box, select Configuration Manager and click
Next.
3. In the Configuration Maintenance dialog box, select Perform maintenance
on an existing configuration and click Next.
4. In the Configuration Selection dialog box, select the configuration you
want to modify and click Next.
5. In the Feature Maintenance dialog box, select Modify 4tier Teamcenter
server configurations and click Next.
6. In the Modify 4tier Teamcenter server configurations dialog box, click
Add to add a row to the Middle-tier servers list.
7. In the URI box of the new row, enter the URI of the new Teamcenter Web
tier application.
The general form is http://host:port/tc-web-tier-app-name
host is the machine on which the Web application server is running.
port is the port of the Web application server.
tc-web-tier-app-name is the name of the new Teamcenter Web tier
application.
8. In the Connection Name box of the new row, enter a connection name.
This is the value displayed in the rich client login page.
9. In the Modify 4tier Teamcenter server configurations dialog box, click
Next.
10. In the Confirm Selections dialog box, click Next.
11. When the Install Features: Successful message appears, the installation
is complete. Click Close.
Teamcenter Installation
19-23
Activities
In the Create an additional site section, do the following activities using the
dba account:
In the Create an additional site section, do the following activities using the
infodba account:
19-24
Teamcenter Installation
MT25350_S_0830
.NET only: Modify the four-tier rich client to point to both databases
(Do this activity only if you installed the .NET Web tier.)
Teamcenter Installation
19-25
Review questions
1. You can add information about the new sites FSC to the FMS master file
by selecting _________ in the Teamcenter Environment Manager.
Select one answer.
Add FSC
Update FSC
3. Each new site that uses the four-tier architecture must have its own
server manager and Teamcenter Web tier application.
Select one answer.
True
False
4. Each new site that uses the four-tier architecture must have unique
values for which of the following if TCP mode is used?
Select one answer.
19-26
Teamcenter Installation
MT25350_S_0830
5. When creating a new Teamcenter Web tier application for a new site
that uses TCP, set TreeCache Peers to the values for the ________ local
service port.
Select one answer.
Teamcenter Installation
19-27
Summary
The following topics were taught in this lesson:
19-28
Configuring FMS master to include the initial and the additional sites.
Modifying a four-tier rich client that was installed using the Over-the-Web
Installer to point to both sites
Modifying a four-tier rich client that was installed using TEM to point
to both sites
Teamcenter Installation
MT25350_S_0830
Lesson
20 Understanding Multi-Site
Collaboration
Purpose
The purpose of this lesson is to introduce you to Multi-Site Collaboration
concepts.
Objectives
After you complete this lesson, you should be able to:
Help topics
Additional information for this lesson can be found in:
Teamcenter Installation
20-1
20-2
Teamcenter Installation
MT25350_S_0830
Historical overview
During product development, the engineering sites in Detroit and London
occasionally share small amounts of data with one another and with their
suppliers in So Paulo and Tokyo. This is accomplished by manually
exporting product information as objects, transferring these objects using File
Transfer Protocol (FTP) or removable media (DAT) to the desired site, and
manually importing them into the databases.
After product development completes, engineering data is manually exported
and transferred to the Detroit manufacturing site and imported into that
database.
Although this solution can work acceptably on a limited basis, it requires too
much touch labor and too many ad hoc arrangements to be viable for routinely
sharing large amounts of product information across this enterprise.
To clearly understand the issues involved with sharing product information
across an entire enterprise, consider how the XYZ Widget Corporation may
share data without the benefit of Multi-Site Collaboration.
The following graphic shows that the XYZ Widget Corporation has
engineering sites in Detroit and London, a manufacturing site in Detroit, and
suppliers in Tokyo and So Paulo. Each of these sites currently stores their
product information in separate databases.
Teamcenter Installation
20-3
20-4
Teamcenter Installation
MT25350_S_0830
Teamcenter Installation
20-5
Site
Comprises a single database that includes all users accessing that database
and any additional non-Teamcenter resources such as hardware, networking
capabilities, and third-party software applications (tools) required to
implement Teamcenter at that site. For this discussion, think of each site
as a single database and its users.
Facility
Physical location (for example, manufacturing plant, design center, and
so forth) in your enterprise. It is extremely important not to confuse sites
and facilities. Sites are databases; facilities are buildings. One facility can
comprise multiple sites.
Network
For independent sites within the same enterprise to share data, Multi-Site
Collaboration implements an environment that can best be described as a
federation of sites. Each site is truly independent, yet is able to operate
and share data within a larger entity called the Multi-Site Collaboration
network. Multi-Site Collaboration intentionally imposes as few restrictions
and limitations on autonomous site activity as possible.
20-6
Teamcenter Installation
MT25350_S_0830
Publishing
Makes objects available to other sites.
Unpublishing
Makes objects available only to the owning site.
data_share utility
Used to publish and unpublish objects.
Teamcenter Installation
20-7
Remote query
When a user a remote query to search for published objects, a scan of the
publication records (ODS) is performed to find the records that match the
search criteria. References to remote data objects are retrieved.
20-8
Teamcenter Installation
MT25350_S_0830
Data integrity
As an object is replicated to various sites, how do you determine which
object is the latest version of an object? This is especially true if users are
allowed to modify replicated objects.
Security
Without proper security controls, replicated product information could fall
into the hands of people not authorized to have it.
Teamcenter Installation
20-9
Data replication
Replicas of remote objects are created locally.
20-10
Teamcenter Installation
MT25350_S_0830
When you export an object, you must specify which sites are authorized
to import it.
This ensures that no unauthorized replicas are made and stores tracking
information with the master object.
Teamcenter Installation
20-11
20-12
Teamcenter Installation
MT25350_S_0830
Synchronization
A replication-based solution must ensure that replicas are kept up-to-date
when the master object is modified. Multi-Site Collaboration addresses this
by maintaining export records and providing synchronization facilities:
Export records
data_sync utility
sync_on_demand utility
Automatic synchronization
Export records
When an object is exported, export records are created for each target site
specified. Each export record contains the site ID of each target site and the
date of the last export to that site. Export records are always associated (and
stored) with the master object. For items, a special item export record is also
created to record the import/export options used so that these same options
can be used to synchronize the item.
data_sync utility
When the master object is modified, replicas can be updated by a system
administrator through this utility. The process of keeping replicated data
up-to-date is called synchronization. Optionally, synchronization may be
limited to visualization data that is directly or indirectly related to datasets.
For additional information, see the Utilities Reference.
sync_on_demand utility
The end user may update replicated objects as they require using this utility.
A component, assembly, or object can be selected for a synchronization report
that allows users to determine if synchronization is required and to select the
specific components to synchronized.
For additional information, see the Utilities Reference.
Automatic synchronization
The end user who replicates an object may specify that the replica be
synchronized automatically when the master object is modified. The replica
is then synchronized automatically using the Multi-Site Collaboration
automatic synchronization functionality.
Teamcenter Installation
20-13
20-14
Teamcenter Installation
MT25350_S_0830
Version interoperability
When a Multi-Site Collaboration site is upgraded to a new version, it is not
necessary to upgrade all other sites in the Multi-Site Collaboration network
at the same time. When a new major version is released, it is interoperable
with all sites running earlier versions as long as the difference in major
version numbers is not more than 2.
Although interoperability is guaranteed, there can be some limitations. For
example, transfer of ownership of certain types of objects from a higher
release version to a lower one may not be allowed. In most cases, new features
introduced in a new release are not available when communicating with a
remote site running an earlier version. The version of the server dictates
what the client can do.
Teamcenter Installation
20-15
Review questions
1. The Multi-Site Collaboration solution provides semiautomated, real-time
data sharing across an entire enterprise.
Select one answer.
True
False
Locator
Transporter
20-16
True
False
Teamcenter Installation
MT25350_S_0830
Summary
The following topics were taught in this lesson:
Synchronization
Object ownership
Teamcenter Installation
20-17
Lesson
21 Course summary
During this course, you met the course objectives by accomplishing the
following:
You used the Web Application Manager to create the components of the
Teamcenter J2EE Web tier.
You used Web tier application, the distribution server, and the distribution
server instance to successfully set up the J2EE Web tier.
Teamcenter Installation
21-1
Index
B
Business Modeler IDE
Installing . . . . . . . . . . . . . . 12-4, 12-9
Start . . . . . . . . . . . . . . . . . . . . 12-13
I
Installing
Business Modeler IDE . . . . 12-4, 12-9
S
Start the Business Modeler IDE . . 12-13
T
Teamcenter Environment Manager
(TEM) . . . . . . . . . . . . . . . . . . . . . 12-4
L
Launch the Business Modeler
IDE . . . . . . . . . . . . . . . . . . . . . . 12-13
Teamcenter Installation
Index-1
Course agenda
Day 1
Morning
Introduction
Course overview
Lesson 1
Lesson 2
Lesson 3
Lesson
Lesson
Afternoon Lesson
Lesson
6
7
8
9
Lesson 10
Day 3
Morning
Lesson 11
Lesson
Lesson
Afternoon Lesson
Lesson
Lesson
Day 4
Morning
12
13
14
15
16
Lesson 17
Lesson 18
Lesson 19
Afternoon Lesson 20
Day 5
Morning Lesson 20
Afternoon Lesson 21
Lesson 22
Student profile
Course evaluation