Teamcenter 2007 Installation Mt00300

Teamcenter 2007
Enterprise Knowledge Management
Installation on UNIX and Linux

Servers
Publication Number
MT00300 L3
Teamcenter 2007
Installation on UNIX and Linux

Servers
This product is intended for use only as described in this document.

Siemens PLM Software cannot be responsible for the proper functioning
of undescribed features and parameters.
Publication Number
MT00300 L3
Manual History
Manual Metaphase Publication

Revision Version Date
A 3.0 October 1997
B 3.1 December 1998
B1 3.1 December 1998
C 3.2 November 1999
D 3.2.1 January 2001
D1 3.2.1 March 2001
Manual Enterprise Knowledge Publication

Revision Management Date
Version
E 1.0 June 2001
F 2.0 November 2001
G 3.0 September 2002
H 3.1 April 2003
H1 3.1 April 2003
I 4.0 December 2003
I1 4.0 February 2005
J 2005 (5.0) July 2005
K 2005 SR1 June 2006
L 2007 November 2007
L1 2007 MP01 May 2008
L2 2007 MP02 December 2008
L3 2007 MP03 July 2009
This edition obsoletes all previous editions.
2 Installation on UNIX and Linux Servers MT00300 L3

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 9
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Enterprise Knowledge Management Manual Set . . . . . . . . . . . . . . . . . . . . . . 16
Submitting Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Part I: Preparing to Install Enterprise Knowledge Management
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Enterprise Knowledge Management Installation Process . . . . . . . . . . . . . . . . 1-1
Enterprise Knowledge Management Network Architecture . . . . . . . . . . . . . . . 1-1
Installation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Required References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Enterprise Knowledge Management and Compatible Third-Party Software
Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ................ . . . 2-1
Software Requirements . . . . . . . . . . . . . . . . . . . . . ................ . . . 2-2
Hardware Requirements . . . . . . . . . . . . . . . . . . . . ................ . . . 2-3
Special Considerations for Non-English Locales . . . . ................ . . . 2-5
Creating the Enterprise Knowledge Management Trusted User . . . . . . 3-1
Installing Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Oracle and Enterprise Knowledge Management Terminology . . . . . . . . . . . . . 4-1
Oracle Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Setting Database Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Obtaining Oracle Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Planning Enterprise Knowledge Management Database Configuration . . . . . . 4-6
Verifying Oracle Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Determining Character Set Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Configuring a Distributed-Database Environment . . . . . . . . . . . . . . . . . . . . . 4-9
Part II: Installing the Enterprise Tier
Preparing the Enterprise Knowledge Management Environment . . . . . 5-1

Setting System Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Copying Installation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Installing Enterprise Knowledge Management Licenses . . . . . . . . . . . . . . . . . 5-2
MT00300 L3 Installation on UNIX and Linux Servers 3

Contents
Installing Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . . 6-1

Before Installing Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . 6-1
Installing the Enterprise Knowledge Management Corporate Server . . . . . . . . 6-2
Completing the Enterprise Knowledge Management Installation . . . . . . . . . . 6-7
Verifying Linux Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Performing Optional Postinstallation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Configuring Enterprise Knowledge Management . . . . . . . . . . . . . . . . . 7-1

Configuring the Enterprise Knowledge Management Indexed Search Engine . . 7-2
Setting Configuration Variables for Teamcenter Security Services . . . . . . . . . . 7-5
Loading Administrative Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Part III: Installing the Web Tier
Installing the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Creating the WEB_ROOT Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Launching the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Installing Thin Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Creating Thin Client Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Modifying Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Configuring Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Deploying an Enterprise Knowledge Management Web Application . . 10-1

Deploying the Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Configuring the Web Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Web Tier Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Verifying the Enterprise Knowledge Management Thin Client Web
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Part IV: Additional Configuration and Maintenance
Setting Up Administrative Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Product Data Management Life Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Change Management and Rapid Change Management Life Cycles . . . . . . . . . 11-2
CMII Life Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Request for Quote (RFQ) Life Cycle and Templates . . . . . . . . . . . . . . . . . . . . 11-6
Part Request Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Vaults and Related Administrative Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Administrative Data for Change Management and Rapid Change
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Valid Values for Reviewer List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Documents Required for Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Automatic Part Revision and PartDoc Relation . . . . . . . . . . . . . . . . . . . . . . 11-14
Setting Up Translation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Configuring Translation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Setting Up the Translation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

Contents
Installing Local Area and Work Group Servers . . . . . . . . . . . . . . . . . . 13-1

Preparing the Server Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Adding the Host and User to the Configuration . . . . . . . . . . . . . . . . . . . . . . . 13-2
Configuring the License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Running the Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Executing the pushall Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Installing a Special Services Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Installing Vis Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Completing Special Services Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Adding Server Solutions and Components . . . . . . . . . . . . . . . . . . . . . . 15-1

Adding Server Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Adding an Enterprise Knowledge Management Component . . . . . . . . . . . . . . 15-3
Adding the Enterprise Knowledge Management Indexed Search Engine . . . . . 15-6
Reinstalling a Server Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Configuring Legacy Web-Based Products . . . . . . . . . . . . . . . . . . . . . . . 16-1

Updating Java Security for e!Vista Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Configuring e!Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Configuring Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Launching Web-Based Enterprise Knowledge Management Products . . . . . . . 16-6
Part V: Appendixes
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Installation Utility and Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . B-1
Communications Multiplexor (MUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Search Engine Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
Oracle Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

How the Configuration Editor Creates an Oracle User . . . . . . . . . . . . . . . . . . C-1
Oracle Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Oracle Distributed Setup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Utility Program Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Sample Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Installing and Running Enterprise Knowledge Management Using

NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Client/Server Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
MUX Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
olaunch Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Sockets and FIFOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Running netstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Contents
Running the MUX and Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Installing Maintenance Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Downloading a Maintenance Pack . . . . . . . . . . . . . . . . . . . . ......... . . . E-1
Installing Maintenance Packs . . . . . . . . . . . . . . . . . . . . . . . ......... . . . E-2
Using Maintenance Pack Manager Options . . . . . . . . . . . . . . ......... . . . E-3
Manually Configuring Download Locations . . . . . . . . . . . . . . ......... . . . E-4
Patching Enterprise Knowledge Management Thin Client and Rich Client
Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ......... . . . E-8
Uninstalling Enterprise Knowledge Management . . . . . . . . . . . . . . . . . F-1

Uninstalling the Search Engine Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Uninstalling Enterprise Knowledge Management Servers . . . . . . . . . . . . . . . F-2
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Figures
1-1. Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1-2. Database Interaction With Enterprise Knowledge Management . . . . . . 1-4
1-3. Distribution of Enterprise Knowledge Management Clients . . . . . . . . . 1-6
1-4. Network Model for Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1-5. Web Application Server in the Enterprise Knowledge Management
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1-6. Enterprise Knowledge Management Installation Utility . . . . . . . . . . . . 1-10
1-7. Enterprise Knowledge Management Configuration Editor . . . . . . . . . . 1-10
1-8. Teamcenter Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . 1-11
4-1. Oracle Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
5-1. Sample License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
6-1. Enterprise Knowledge Management Installation Utility . . . . . . . . . . . . 6-3
6-2. Enterprise Knowledge Management Installation Dialog Window . . . . . . 6-3
6-3. Enterprise Knowledge Management Home Collection . . . . . . . . . . . . . . 6-8
7-1. Enterprise Knowledge Management Configuration Editor . . . . . . . . . . 7-1
7-2. Modify Database Information Dialog Window . . . . . . . . . . . . . . . . . . . 7-2
9-1. Modify Web Application Dialog Window . . . . . . . . . . . . . . . . . . . . . . . 9-6
9-2. Modify Context Parameters Dialog Window . . . . . . . . . . . . . . . . . . . . . 9-6
15-1. Add Component Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
15-2. Reinstall Server Solutions Dialog Window . . . . . . . . . . . . . . . . . . . . . . 15-7
16-1. Setting the ONLINE_DOC_URL Configuration Variable . . . . . . . . . . . 16-5
16-2. e!Vista OMF Login Dialog Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
B-1. Translation Troubleshooting Flowchart . . . . . . . . . . . . . . . . . . . . . . . . B-6
C-1. Sample Program for Creating an Oracle User . . . . . . . . . . . . . . . . . . . C-1
C-2. Sample .login file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
C-3. Sample .profile file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
D-1. Sample root.sh File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Tables
1. Enterprise Knowledge Management Installation and Conversion . . . . . 16

Contents
2. Enterprise Knowledge Management Modules and Solutions . . . . . . . . . 16

3. Teamcenter Industry-Focused Solutions . . . . . . . . . . . . . . . . . . . . . . . 17
4. Global Services Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5. Application Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1-1. Enterprise Knowledge Management Sample Configuration
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
2-1. Minimum Enterprise Knowledge Management Hardware
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2-2. Character Encoding Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2-3. Setting LANG and LC_ALL (UTF-8 Environments) . . . . . . . . . . . . . . . 2-7
2-4. Setting LANG and LC_ALL (Non-UTF-8 Environments) . . . . . . . . . . . 2-8
2-5. Setting NLS_LOCALE and NLS_LANG (UTF-8 Environments) . . . . . . 2-9
2-6. Setting NLS_LOCALE and NLS_LANG (Non-UTF-8 Environments) . . . 2-10
4-1. Oracle Installation Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4-2. Environment Variables for Oracle With Enterprise Knowledge
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4-3. Oracle Server Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4-4. Enterprise Knowledge Management Default Database Settings . . . . . . 4-6
4-5. Supported Character Set Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
6-1. Required Server Solutions for Thin Client Solutions . . . . . . . . . . . . . . . 6-4
7-1. Configuration Variables for Indexed Search . . . . . . . . . . . . . . . . . . . . . 7-3
9-1. Context Parameters for Product Data Management . . . . . . . . . . . . . . . 9-3
9-2. Context Parameters: Authentication and Proxies for File Transfers . . . . 9-9
9-3. Context Parameters for Teamcenter Conferencing Solution . . . . . . . . . . 9-10
9-4. Conferencing Options Enabled on Thin Clients . . . . . . . . . . . . . . . . . . 9-11
9-5. Context Parameters for Over-the-Web WebPD Installer . . . . . . . . . . . . 9-13
9-6. Context Parameters for Teamcenter Interface . . . . . . . . . . . . . . . . . . . 9-15
9-7. Context Parameters for Teamcenter Project Integration . . . . . . . . . . . . 9-15
9-8. Context Parameters for Content Management . . . . . . . . . . . . . . . . . . . 9-16
11-1. Creating Vaults and Message Access Rules . . . . . . . . . . . . . . . . . . . . . 11-8
11-2. Administrative Data for Reviewer List . . . . . . . . . . . . . . . . . . . . . . . 11-10
11-3. Documents Required for Release Attributes . . . . . . . . . . . . . . . . . . . . 11-11
11-4. Sample AdmVal Class Object Data . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
11-5. Release Required Document Attributes . . . . . . . . . . . . . . . . . . . . . . . 11-14
11-6. Sample Data for Automatic Revision . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
12-1. Translation Configuration Control Object Fields . . . . . . . . . . . . . . . . . 12-3
12-2. CATIA Translation Configuration Control Object Fields . . . . . . . . . . . . 12-5
12-3. Pro/ENGINEER Part and Drawing Translation Configuration Control Object
Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
12-4. NX and Rich Client Translation Configuration Control Object Fields . . . 12-7
12-5. I-deas Enterprise and IMI Translation Configuration Control Object
Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
12-6. Common Translation Environment Configuration Variables . . . . . . . . 12-11
12-7. C9S Translator and C9S Drawing Translator Mappings . . . . . . . . . . . 12-11
15-1. Enterprise Knowledge Management Component Installation Scripts . . . 15-5
16-1. Web Server Virtual Directories for e!Vista . . . . . . . . . . . . . . . . . . . . . . 16-2
16-2. Launch URLs for Web-Based Enterprise Knowledge Management
Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
C-1. Contents of Oracle Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
C-2. Parameters in Sample listener.ora Files . . . . . . . . . . . . . . . . . . . . . . . C-4
C-3. Parameters in Sample tnsnames.ora Files . . . . . . . . . . . . . . . . . . . . . . C-6
E-1. Patch Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Preface
This manual provides instructions for installing Teamcenter server components on

UNIX systems. Enterprise Knowledge Management belongs to the Siemens PLM
Software portfolio of digital product lifecycle management software and services.
For information about installing Enterprise Knowledge Management on client
hosts,1 see the Client Installation manual.
For information about upgrading an existing Enterprise Knowledge Management
server installation, see the appropriate upgrade guide (for upgrading from
Teamcenter Enterprise 2005 SR1, Teamcenter Enterprise 3.1, or Teamcenter
Enterprise 3.0).
For information about installing application integrations, such as AutoCAD,
FrameMaker, Pro/ENGINEER, and others, see the installation/user guide for each
integration.
Audience
This manual is intended for the person who installs Enterprise Knowledge
Management servers. It assumes that you are familiar with the following tasks
and concepts:
• Basic operating system use, including setting environment variables, starting

and stopping services, and setting file permissions.
• Client-server network architecture.
• Basic database usage and terminology.
• Basic Enterprise Knowledge Management usage, services (such as the MUX and
dispatcher), and terminology (such as the Enterprise Knowledge Management
trusted user).
If you install Enterprise Knowledge Management thin client and rich client solutions,
you must be familiar with basic use and administration of a Web application server.
If you install legacy Web-based Enterprise Knowledge Management products, you
must also be familiar with basic Web server administration tasks, such as creating
virtual directories.
1. The Enterprise Knowledge Management classic client is automatically installed on Enterprise Knowledge Management server hosts.

Preface
Organization
This manual is organized into five parts:
• Part I, Preparing to Install Enterprise Knowledge Management, provides an
overview of Enterprise Knowledge Management installation and describes
procedures to perform before you begin installing Enterprise Knowledge
Management.
• Part II, Installing the Enterprise Tier, describes how to install the enterprise
tier, which consists of the Enterprise Knowledge Management corporate server
and supporting software.
• Part III, Installing the Web Tier, describes how to install the thin client and
the rich client and how to deploy an Enterprise Knowledge Management Web
application on a Web application server.
• Part IV, Additional Configuration and Maintenance, describes how to install

additional Enterprise Knowledge Management servers and how to add server
solutions, components, and other features to your Enterprise Knowledge
Management installation.
• Part V, Appendixes, provides supporting information.
Part I – Preparing to Install Enterprise Knowledge Management

Part I contains the following chapters:
Chapter 1 Overview provides an overview of the installation process.

Chapter 2 System Requirements describes the hardware and software
required for Enterprise Knowledge Management and
considerations for non-English locales.
Chapter 3 Creating the Enterprise Knowledge Management Trusted User
describes how to create an Enterprise Knowledge Management
user group and primary user (or trusted user) and a home
directory for the Enterprise Knowledge Management software.
Chapter 4 Installing Oracle describes how to install and configure Oracle
for use with Enterprise Knowledge Management.

Preface
Part II – Installing the Enterprise Tier

Part II contains the following chapters:
Chapter 5 Preparing the Enterprise Knowledge Management Environment

describes how to prepare your corporate host before you install
Enterprise Knowledge Management.
Chapter 6 Installing Enterprise Knowledge Management describes how
to install Enterprise Knowledge Management on the corporate
server host.
Chapter 7 Configuring Enterprise Knowledge Management describes
tasks you must perform to complete the Enterprise Knowledge
Management installation process.
Part III – Installing the Web Tier

Part III contains the following chapters:
Chapter 8 Installing the Web Application Manager describes how to install

the Web Application Manager, a tool that installs thin client and
rich client Web applications.
Chapter 9 Installing Thin Client Solutions describes how to install and
configure Teamcenter’s enterprise knowledge management thin
client solutions.
Chapter 10 Deploying an Enterprise Knowledge Management Web Application
describes how to deploy an Enterprise Knowledge Management
Web application on supported Web application servers.
Part IV – Additional Configuration and Maintenance

Part IV contains the following chapters:
Chapter 11 Setting Up Administrative Data describes how to load

administrative data to support standard life cycles provided with
certain Enterprise Knowledge Management features.
Chapter 12 Setting Up Translation Environment describes how to configure
the translation service to set up translation control objects for
Teamcenter.
Chapter 13 Installing Local Area and Work Group Servers describes how to
install Enterprise Knowledge Management on servers other than
the Enterprise Knowledge Management corporate server (local
area servers and work group servers) using the installation script.
Chapter 14 Installing a Special Services Host describes how to install a
special services host to distribute services that support document
management features.

Preface
Chapter 15 Adding Server Solutions and Components describes how to

add Enterprise Knowledge Management server solutions to an
installation or to reinstall previously installed server solution. It
also describes how to add Enterprise Knowledge Management
components such as online manuals.
Chapter 16 Configuring Legacy Web-Based Products describes additional
procedures to complete installation of Web-based Enterprise
Knowledge Management products such as e!Vista and the online
manuals library for the classic client.
Part V – Appendixes
Part V contains the following appendixes:
Appendix A Glossary defines Enterprise Knowledge Management terms.

Appendix B Troubleshooting provides assistance for troubleshooting your
Enterprise Knowledge Management installation.
Appendix C Oracle Reference provides information about Enterprise
Knowledge Management interaction with Oracle during
installation and describes sample UNIX startup files provided
with Enterprise Knowledge Management.
Appendix D Installing and Running Enterprise Knowledge Management
Using NFS contains information about installing and running
Enterprise Knowledge Management using the Network File
System (NFS).
Appendix E Installing Maintenance Packs describes how to obtain and install
Enterprise Knowledge Management product patches.
Appendix F Uninstalling Enterprise Knowledge Management describes how
to uninstall Enterprise Knowledge Management.
Conventions
This guide uses the conventions described in the following sections.
Note, Caution, and Warning Icons

The following icons represent note, caution, and warning messages:
A note icon identifies general instructions or comments that need to be

emphasized.
A caution icon identifies practices that can either produce results contrary to
what you expect or result in damage to software or data.
A warning icon identifies practices that could result in permanent loss of

data or software.

Preface
Browser and Window Examples

The examples of browsers and dialog windows in this manual may appear different
from those you see on your screen:
• The examples reflect Enterprise Knowledge Management as initially installed
at your site. Your enterprise may customize the browsers and windows so they
appear different from the examples.
• The examples may reflect an earlier version of the product. The functionality,
however, remains the same.
• The examples reflect individual Enterprise Knowledge Management modules. If

you install additional modules, your windows and browsers reflect the additional
modules.
• The examples reflect Enterprise Knowledge Management installed on a UNIX

platform using MOTIF window manager. If you run Enterprise Knowledge
Management on a different platform or use a different window manager, the
browsers and windows may appear different from the examples.
Names and Values

This manual represents system names, file names, and values in fonts that help you
interpret the name or value. For example:
Change or add the parameter to the initsid.ora file.
The conventions are:
Bold Bold font represents unvarying text or numbers within a name or

value. Capitalization is as it appears.
Italic Italic font represents text or numbers that vary within a name or
value. The characters in italic text describe the entry. Letters are
shown in lowercase, but the varying text may include uppercase
letters.
In initsid.ora, sid identifies a varying portion of the name (a
unique system ID). For example, the name of the file might be:
initBlue5.ora
text-text A hyphen separates two words that describe a single entry.

Preface
Command Line Entries, File Contents, and Code

This manual represents command line input and output, the contents of system files,
and computer code in fonts that help you understand how to enter text or to interpret
displayed text. For example, the following line represents a command entry:
msqlora -u system/system-password
Monospace Monospace font represents text or numbers you enter on a

command line, the computer’s response, the contents of system
files, and computer code.
Capitalization and spacing are shown exactly as you must enter
the characters or as the computer displays the characters.
Italic Italic font represents text or numbers that vary. The words in
italic text describe the entry.
The words are shown in lowercase letters, but the varying text
may include uppercase letters. When entering text, use the case
required by the system.
For the preceding example, you might substitute the following for
system-password:
KLH3b
text-text A hyphen separates two words that describe a single entry.

Preface
Syntax Definitions
This manual uses a set of conventions to define the syntax of Enterprise Knowledge
Management language statements, commands, and functions. Following is a sample
syntax format for a MODeL statement:
define value set value-set-name {’[’value [, value ...] ’]’ | date}
Bold Bold text represents keywords. Enter keywords as shown, in either

all uppercase or all lowercase characters—do not mix uppercase and
lowercase letters. In the define value set statement, the following
words are keywords:
define value set
Italic Italic text represents values that you supply.
| A vertical bar represents a choice between mutually exclusive
elements. In the define value set statement, you can enter either
value or date.
[] Brackets represent optional elements. In the define value set
statement, you are not required to enter the following element:
[, value ...]
{text} Braces surround mutually exclusive elements that are required. In
the define value set statement, you must enter either value or date.
’[’ Single quotation marks enclose a bracket when it represents a
character that you enter rather than the symbol for optional
elements. In the define value set statement, one pair of brackets is
enclosed in single quotation marks:
’[’value [, value...] ’]’
These brackets do not represent an optional element. You must
enter the brackets.
... An ellipsis indicates that you can repeat the preceding element.
In the define value set statement, you can repeat the following
element:
[, value ...]
text-text A hyphen separates two words that describe a single value. In the
define value set statement, the following words represent a single
value:
value-set-name
You enter the name of a value set.

Preface
Enterprise Knowledge Management Manual Set

The manuals in the following list contain information about Enterprise Knowledge
Management, Enterprise Knowledge Management modules, and application
integrations.
Enterprise Knowledge Management products and manuals are released at

different times. Inclusion in this list does not imply that a product or manual
is available at the latest product level.
Table 1. Enterprise Knowledge Management Installation and Conversion

Publication
Manual Title Number
Client Installation MT00301
Installation on UNIX and Linux Servers MT00300
Installation on Windows Servers MT00316
Localization Guide MT00389
Network and Database Configuration Guide MT00395
Release Bulletin MT00302
Rich Client Installation and Configuration MT00403
Rich Client Release Notes SDO-356
Teamcenter Enterprise 2005 SR1 to Enterprise Knowledge MT00374
Management 2007 Upgrade Guide
Teamcenter Enterprise 4.0 to Enterprise Knowledge MT00312
Teamcenter Enterprise 5.0 to Enterprise Knowledge MT00348
Table 2. Enterprise Knowledge Management Modules and Solutions

Publication
Manual Title Number
Administrator’s Manual for Content Management MT00427
Advanced Product Configurator User’s Manual MT00354
Change Control Manager to Change Management Migration SDO-244
Guide
API Reference MT00324
Change Control Manager User’s/Administrator’s Manual MT00362
Content Management User’s Guide MT00421
Document Management Menu Interface User’s Manual MT00394
Enterprise Services Reference MT00346
e!Vista Task Customization MT00379

Preface
Table 2. Enterprise Knowledge Management Modules and Solutions

Publication
Manual Title Number
Handler Reference MT00355
Life Cycle Manager User’s Manual MT00310
MetaSM Administrator’s Manual MT00375
MetaSM User’s Manual MT00381
MODeL Reference MT00323
Object Management Framework User’s Manual MT00306
Part Family Manager User’s/Administrator’s Manual MT00357
Records Management Application User’s/Administrator’s MT00402
Manual
Research Knowledge Management Installation/Administration MT00423
Manual
Rich Client Customization MT00380
Server Customization MT00321
Administrator’s Manual MT00305
Administrator’s Manual for Change Management MT00353
Administrator’s Manual for Life Cycles MT00309
Administrator’s Manual for Part Families MT00386
Administrator’s Manual for Parts and Documents MT00401
Administrator’s Manual for Product Configuration MT00413
Administrator’s Manual for Reports MT00422
Data Migration MT00398
Enterprise Knowledge Management IDE User’s Guide MT00397
Thin Client Customization MT00343
Web Services Reference MT00412
Table 3. Teamcenter Industry-Focused Solutions

Publication
Manual Title Number
Aerospace and Defense Installation and Administrator’s MT00387
Manual
Aerospace and Defense Release Notes SDO-264
Automotive Supplier Installation and Administrator’s Manual MT00352
Automotive Supplier Release Notes SDO-272
Consumer and Packaged Goods Installation and MT00385
Administrator’s Manual

Preface
Table 3. Teamcenter Industry-Focused Solutions

Publication
Manual Title Number
Consumer and Packaged Goods Release Notes SDO-325
High Tech Electronics Installation and Administrator’s Manual MT00359
High Tech Electronics Release Notes MT00360
Installation and Administrator’s Manual for Retail MT00425
Table 4. Global Services Documentation

Publication
Manual Title Number
Global Services Installation EB00120
Global Services Configuration and Administration EB00101
Global Services Customization EB00102
Connector Documentation
Connector to Enterprise Knowledge Management EB00107
Connector to Oracle Manufacturing EB00109
Connector to SAP EB00110
Connector to Engineering Process Management EB00115
Solution Documentation
Engineering Process Management/Oracle Manufacturing EB00123
Solution Configuration and Administration Manual
Engineering Process Management/Oracle Manufacturing EB00124
Solution User’s Guide
Enterprise Knowledge Management/SAP Solution Installation EB00113
and Administration
Enterprise Knowledge Management/SAP Solution User’s EB00114
Guide
Table 5. Application Integrations

Publication
Manual Title Number
AutoCAD Integration Installation/User’s Guide MT00330
Cadence Integration Installation/User’s Guide MT00350
ClearCase Integration Installation Guide MT00335
ClearCase Integration User’s Guide MT00334
DOORS Integration Installation/User’s Guide MT00344
I-deas Enterprise Data Migration Guide MT00336

Preface
Table 5. Application Integrations

Publication
Manual Title Number
I-deas Enterprise Installation and Administration Guide MT00313
Mentor Graphics Integration Installation/User’s Guide MT00333
NX Integration Installation/User’s Guide MT00320
Oracle Manufacturing Integration Installation and MT00318
Administration Guide
Oracle Manufacturing Integration User’s Guide MT00319
Pro/ENGINEER Integration Installation/User’s Guide MT00328
Pro/INTRALINK Integration Installation/User’s Guide MT00396
SAP Integration Installation Guide MT00363
SAP Integration Programming and Customization Guide MT00365
SAP Integration User’s and Administrator’s Manual MT00364
EDA Installation/User’s Guide MT00400
Enterprise Knowledge Management/Oracle Manufacturing EB00111
Solution Installation and Administration
Enterprise Knowledge Management/Oracle Manufacturing EB00112
Solution User’s Guide
Teamcenter Link Installation and Customization EB00116
Submitting Comments
Portions of Teamcenter software are provided by third-party vendors. Special
agreements with these vendors require Siemens PLM Software to handle all problem
reports concerning the software they provide. Please submit all comments directly to
Siemens PLM Software.
Please feel free to give us your opinion of the usability of this manual, to suggest
specific improvements, and to report errors. Mail your comments to:
Siemens PLM Software Technical Communications
5939 Rice Creek Parkway
Shoreview, MN 55126
U.S.A.
To submit an incident report, you can use the Siemens PLM Software GTAC online
support tools at the following URL:
http://support.ugs.com

Preface
Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens Product
Lifecycle Management Software Inc.
© 2009 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
All trademarks belong to their respective holders.

Part
I Preparing to Install Enterprise

Knowledge Management
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Creating the Enterprise Knowledge Management Trusted User . . . . . . . . . . . 3-1
Installing Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
MT00300 L3 Installation on UNIX and Linux Servers

Chapter
1 Overview
Enterprise Knowledge Management Installation Process . . . . . . . . . . . . . . . . 1-1
Enterprise Knowledge Management Network Architecture . . . . . . . . . . . . . . . 1-1

Sample Enterprise Knowledge Management Configuration . . . . . . . . . . . . 1-2
Network and Database Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Distribution of Enterprise Knowledge Management Clients . . . . . . . . . . . 1-4
Network Architecture for Web Applications . . . . . . . . . . . . . . . . . . . . . . . 1-7
Installation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Enterprise Knowledge Management Installation Utility . . . . . . . . . . . . . . 1-10
Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Required References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Installation Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Chapter
1 Overview
This chapter describes the Enterprise Knowledge Management installation process

and provides examples and other references to help you plan your installation.
This chapter describes the following topics:

• The Enterprise Knowledge Management installation process.
• Enterprise Knowledge Management network architecture.
• Software used during Enterprise Knowledge Management installation.
• How to plan your Enterprise Knowledge Management installation.
• Additional references required during Enterprise Knowledge Management

installation.
This chapter also provides an Installation Worksheet, on which you can record
important information needed during installation.
Enterprise Knowledge Management Installation Process

The procedures in this manual are designed to be performed chapter-by-chapter,
in the order presented.
This manual describes how to install Enterprise Knowledge Management on server
hosts only. For information about installing Enterprise Knowledge Management on
a workstation host, see the Client Installation manual.
The following sections provide information about Enterprise Knowledge
Management network architecture, installation tools, and guidelines for planning
your installation.
Enterprise Knowledge Management Network Architecture

This section describes the Enterprise Knowledge Management network hierarchy
and database interaction.
Typically, Enterprise Knowledge Management is distributed throughout a network
in order to optimize Enterprise Knowledge Management processing and improve
throughput. The Enterprise Knowledge Management database server program uses
products like Oracle Net to communicate with the databases on remote nodes.
MT00300 L3 Installation on UNIX and Linux Servers 1-1

Chapter 1 Overview
This manual describes how to install Enterprise Knowledge Management

software on the corporate server host, then on local area server or work group
server hosts. It does not include how to add hosts to the Enterprise Knowledge
Management network. For information about adding hosts, see the Network
and Database Configuration Guide.
Sample Enterprise Knowledge Management Configuration

Figure 1-1 illustrates a sample Enterprise Knowledge Management configuration.
SYSTEMS
Administrative database
Corporate Server Corporate user database
Key database
Operational database*
AcmeCorp Local Area Server
Work Group Servers

SYSTEMS
Administrative database*
User database* Operational database*
WrkGrp1 AreaSvr
User database* User database*
Workstation1 Workstation2 WrkGrp2 WrkGrp3
* Not in default configuration,

but can be added. Workstation4 Workstation5 Workstation6
Workstation3
Figure 1-1. Sample Configuration

This sample demonstrates how to distribute the client and server roles of Enterprise
Knowledge Management across hosts using a simple, straightforward configuration
that includes a corporate server, a local area server, three work group servers, and
six workstations. These components apply generally to any Enterprise Knowledge
The sample configuration:
• Demonstrates the distributed Enterprise Knowledge Management architecture.
• Provides corporate-level and work-group-level database assets.1
• Configures the system to partition administrative functions.
• Partitions the system to maximize reliability and integrity.
1. This is not in the default installation but can be added later.
1-2 Installation on UNIX and Linux Servers MT00300 L3

Overview
• Provides a realistic configuration that can be implemented at a single

geographical site.
The Enterprise Knowledge Management hosts in the sample configuration are listed
in table 1-1.
Table 1-1. Enterprise Knowledge Management Sample Configuration

Components
Host Type Description Databases on Host
Corporate server An Enterprise Knowledge Administrative
Management corporate server Corporate user
is a large, reliable server. The Key
corporate server stores common Operational2
information that other server
hosts must be able to access
and modify. It also runs a few
low-usage server programs that
operate best when centralized
rather than distributed on other
hosts.
Local area server An Enterprise Knowledge Administrative2
Management local area server Operational2
provides services to networks
geographically separated from
the corporate server. Local area
servers are also useful in local
networks to reduce the load on
heavily used corporate servers.
Work group server An Enterprise Knowledge User2
Management work group server
is a small to medium server
to serve workstation hosts. A
work group server runs one or
more object servers or database
servers. It can also run a few
low-usage server programs.
Workstation An Enterprise Knowledge None
Management workstation
runs Enterprise Knowledge
Management client programs.
Network and Database Architecture

Before you install Enterprise Knowledge Management, you or your database
administrator must install and configure database software on your corporate server
2. This is not in the default installation but can be added later.

Chapter 1 Overview
host. This section provides an overview of database interaction with the Enterprise
Knowledge Management server.
Chapter 4, Installing Oracle, describes how to install and configure Oracle for
Enterprise Knowledge Management.3
The Enterprise Knowledge Management corporate server must have access to a
database server or a database client. Typically, database software (server or client)
is installed on the same host as the Enterprise Knowledge Management corporate
server. Figure 1-2 shows a three-host configuration with a database server on one
host, a database client and Enterprise Knowledge Management corporate server on
a second host, and an Enterprise Knowledge Management client on a third host.
SYSTEMS SYSTEMS
Database Database Server Database Client

Teamcenter Enterprise
Corporate Server
Teamcenter
Enterprise Client
Figure 1-2. Database Interaction With Enterprise Knowledge Management

In this example, the Enterprise Knowledge Management installation process
invokes the database client to create Enterprise Knowledge Management databases
on the database server host.
Distribution of Enterprise Knowledge Management Clients

All Enterprise Knowledge Management clients interact, directly or indirectly,
with the Enterprise Knowledge Management corporate server. In large networks,
corporate server operations can be distributed to local area servers or work group
servers, which in turn service Enterprise Knowledge Management clients.
Enterprise Knowledge Management clients are installed on either of the following
two types of hosts:
Managed host
A host that is known to Enterprise Knowledge Management. Enterprise
Knowledge Management communications software (MUX and dispatcher) is
installed on this host, and the host is defined in the Enterprise Knowledge
Management configuration on the corporate server.
3. This information is also contained in an appendix in the Network and Database Configuration Guide that describes how to install
and configure Oracle for Enterprise Knowledge Management.

Overview
Unmanaged host
A host that is not known to Enterprise Knowledge Management. This host is
not defined in the Enterprise Knowledge Management configuration, and no
Enterprise Knowledge Management communications software is installed on it.
Enterprise Knowledge Management clients are served by the following types of

servers:
Enterprise Knowledge Management server
Enterprise Knowledge Management software that services database and
transaction requests from Enterprise Knowledge Management clients. An
Enterprise Knowledge Management network contains one corporate server, but
may additionally contain multiple local area servers or work group servers.
Web application server

Server program in a distributed network that provides the business logic
for Enterprise Knowledge Management. The Web application server runs
Web applications built from Enterprise Knowledge Management thin client
solutions (such as Product Data Management and Change Management) that
manage transactions with Enterprise Knowledge Management servers. The
Web application server serves thin client interfaces to unmanaged hosts in
an Enterprise Knowledge Management network. To access the thin client, a
client host needs only a Web browser and the Java™ SE Runtime Environment
installed.
For more information about network architecture for Enterprise Knowledge
Management Web applications, see Network Architecture for Web Applications,
later in this chapter.
Web server
Server program that serves files to clients running Web browsers using
Hypertext Transfer Protocol (HTTP). In an Enterprise Knowledge Management
network, the Web server also distributes Java applets (such as e!Vista tasks,
described later in this manual) that provide user interfaces to Enterprise
Knowledge Management that run on client hosts. For information about setting
up a Web server for Web-based Enterprise Knowledge Management products,
see chapter 16, Configuring Legacy Web-Based Products.
Figure 1-3 shows various Enterprise Knowledge Management clients and how they
are served within an Enterprise Knowledge Management network.

Chapter 1 Overview
SYSTEMS
Web Application
Server
Thin Client Rich Client
SYSTEMS
Special Services
Host
Teamcenter
Enterprise
Server
Classic e!Vista e!Vista

Teamcenter (Managed) (Unmanaged)
Enterprise
SYSTEMS
Web Server
Figure 1-3. Distribution of Enterprise Knowledge Management Clients

The following paragraphs describe the Enterprise Knowledge Management clients
shown in figure 1-3:
• Thin client
Unmanaged host that accesses Enterprise Knowledge Management thin client
solutions through a Web browser. Enterprise Knowledge Management thin
client solutions are contained in Web applications that run on a Web application
server.4
• Rich client
Web application interface to Enterprise Knowledge Management with
integrations to CAD authoring tools and additional optional capabilities.
4. An Enterprise Knowledge Management administrator builds Web applications using the Teamcenter Web Application Manager. For
more information about the Web Application Manager, see chapter 9, Installing Thin Client Solutions.

Overview
• Classic client
Enterprise Knowledge Management software installed on a managed host
that provides a proprietary browser interface, the Enterprise Knowledge
Management home collection, that allows you to locate, view, create, and modify
database data and operating system files in the directories that you register
with Enterprise Knowledge Management. The classic client communicates
with the Enterprise Knowledge Management server through locally installed
communications software (MUX and dispatcher).
• e!Vista managed client

Host that contains Enterprise Knowledge Management communications software
(MUX and dispatcher) and launches the e!Vista client through a Web browser.5
• e!Vista unmanaged client

Host that accesses e!Vista through a Web browser but has no Enterprise
Knowledge Management communications software installed. Thus, no
file systems or objects on the host are accessible to Enterprise Knowledge
Management servers.
• Special services host

Managed host that contains applications and services that support document
management functions.
For information about installing Enterprise Knowledge Management clients, see

the Client Installation manual.
Network Architecture for Web Applications

Teamcenter Toolkit and Teamcenter’s enterprise knowledge management solutions
use a three-tiered network architecture. This architecture is based on Sun’s Java
Platform, Enterprise Edition (J2EE™) application model. The goal of J2EE is
to define a standard of functionality for implementing and deploying enterprise
applications. Such applications are typically configured as a client tier that provides
the user interface, one or more middle-tier modules that provide client services and
business logic for an application, and a back-end enterprise information system that
provides data management. Figure 1-4 shows the three tiers of the environment for
Teamcenter Toolkit and Teamcenter’s enterprise knowledge management.
5. For information about installing e!Vista on a Web server and configuring a Web server to service e!Vista clients, see chapter 16,
Configuring Legacy Web-Based Products.

Chapter 1 Overview
Client Tier Web Tier EIS Tier

Web Application Dispatcher Enterprise Business
Browser Services Logic
Web Actions
Teamcenter
Enterprise
Servers
Business Data
View Processing
View Rendering
Figure 1-4. Network Model for Web Applications

The functions of these tiers are as follows:
• The client tier is where Web clients usually run inside a browser and use the
services of the browser to represent content provided by the Web tier.
• The Web tier is the interface between Web clients on the client tier and
the Enterprise Knowledge Management server network on the enterprise
information system tier.
• The enterprise information system tier is where the Enterprise Knowledge

Management servers reside.
The Enterprise Knowledge Management Web tier requires a host containing a Web
application server. The Web application server communicates with the Enterprise
Knowledge Management server and services requests issued through a Web browser
as shown in figure 1-5.

Overview
SYSTEMS SYSTEMS
Teamcenter Web Application Server

Enterprise
Corporate Server
Web Browser
Figure 1-5. Web Application Server in the Enterprise Knowledge

Management Network
You can install the following Enterprise Knowledge Management 2007 products
on the Web application server:
• Thin client solutions
Web-based interfaces to Enterprise Knowledge Management based on a Web
application engine that integrates JavaServer Pages™ (JSP™) technology into
thin client Enterprise Knowledge Management applications. Solutions can be
installed as delivered or customized to suit your users.
• Rich client solutions

Web interfaces built on the rich client architecture that provide enhanced
capabilities to the rich client.
• Teamcenter Toolkit
Web-based toolkit for developing and deploying interfaces to Enterprise
Knowledge Management. Because the Web application engine manages
implementation details such as authentication, session management, and page
navigation, Web developers with little or no Enterprise Knowledge Management
knowledge can design applications that seamlessly integrate with the application
server.
The Enterprise Knowledge Management Web tier cannot be installed on a Web

server such as Apache HTTP Server. The Web tier requires a Web application
server that includes a servlet engine and server-side Java functionality. For
information about Web application servers supported for use with Enterprise
Knowledge Management 2007, see chapter 2, System Requirements.
For information about installing thin client solutions, see chapter 9, Installing Thin
Client Solutions.
Installation Tools
This section describes software you use to install Enterprise Knowledge Management
and supporting applications on the Enterprise Knowledge Management corporate
server host.

Chapter 1 Overview
Enterprise Knowledge Management Installation Utility

The Enterprise Knowledge Management installation utility (figure 1-6) is an
application that gathers information necessary to install or upgrade6 your Enterprise
Knowledge Management corporate server.
Figure 1-6. Enterprise Knowledge Management Installation Utility

The installation utility is integrated with the Enterprise Knowledge Management
Configuration Editor (figure 1-7), a utility for customizing and updating Enterprise
Knowledge Management after installation.
Figure 1-7. Enterprise Knowledge Management Configuration Editor

You launch the installation utility by entering the cfgedit2 command.
6. For instructions on upgrading an existing Enterprise Knowledge Management server installation, see the appropriate upgrade
guide (for upgrading from Enterprise Knowledge Management 2005 SR1, Enterprise Knowledge Management 3.1, or Enterprise
Knowledge Management 3.0).

Overview
The installation utility allows you to customize database information and to select
Enterprise Knowledge Management server solutions and components to install.
The installation utility installs the Enterprise Knowledge Management software
and automatically configures your corporate server, then launches the Configuration
Editor, allowing you to perform additional steps to complete the installation.
After initial installation is complete, the cfgedit2 command launches the
Configuration Editor. You can run the Configuration Editor any time after
installation to further modify your Enterprise Knowledge Management installation
as needed. For information about using the Configuration Editor, see the Network
and Database Configuration Guide and also the Configuration Editor Online Help.
Web Application Manager

The Web Application Manager (figure 1-8) is a utility that installs thin client and rich
client solutions and builds Enterprise Knowledge Management Web applications.
Figure 1-8. Teamcenter Web Application Manager

You launch the Web Application Manager by entering the insweb command.
The Web Application Manager allows you to create multiple Web applications that
contain different sets of Enterprise Knowledge Management solutions. This enables
you to create Web applications for different groups of users in your network. Your
Web applications can access the same Enterprise Knowledge Management corporate
server, but provide different subsets of Enterprise Knowledge Management
functionality.
The Web Application Manager creates separate staging locations and separate
deployable files7 for each Web application. Some Enterprise Knowledge Management
solutions require other solutions and some solutions may not be combined with other
solutions in the same Web application.
For more information about using the Web Application Manager, see chapter 9,
Installing Thin Client Solutions.
7. A deployable file is a Web archive (.WAR) or enterprise archive (.EAR) file, depending on the solutions it contains.

Chapter 1 Overview
Planning Your Installation

Most Enterprise Knowledge Management installations are more complex than
the samples presented in this chapter, and they require thorough planning and
understanding of Enterprise Knowledge Management architecture, terms, and
concepts. Before you begin installing Enterprise Knowledge Management, consider
the following questions:
• Which Enterprise Knowledge Management interface or interfaces will you
install (classic client, thin client, rich client, or e!Vista)?
• Which Enterprise Knowledge Management server solutions will you install?
• Is your database software installed and operational? Will you use a single
database or distributed databases? (For more information about single versus
distributed databases, see the Network and Database Configuration Guide.)
• Will you install the Enterprise Knowledge Management indexed search? Which
database will contain your search collections?
• If you are installing Teamcenter’s enterprise knowledge management thin client

or rich client solutions, is your Web application server installed and operational?8
• If you are installing legacy Web-based products (such as e!Vista), is your Web
server installed and operational?8
• What other servers (local area servers or work group servers) will you include in
your Enterprise Knowledge Management network?
• Will you install any special services hosts to distribute document management
services?
Required References
In addition to this manual, be sure you also have the following manuals and
references available during Enterprise Knowledge Management installation:
• Release Bulletin
This manual contains the latest information about Enterprise Knowledge
Management 2007, including issues that may affect your installation. Read this
manual before you begin an Enterprise Knowledge Management installation.
• Network and Database Configuration Guide

This manual is essential to planning and configuring your Enterprise Knowledge
Management network. It provides information to assist in the following tasks:
– Determining how to configure the components of Enterprise Knowledge

Management client/server architecture: corporate servers, local area servers,
work group servers, and workstations.
8. For information about Siemens PLM Software-supported Web servers and Web application servers, see chapter 2, System
Requirements.

Overview
– Determining whether you want to install a single Enterprise Knowledge

Management database or distributed databases.
– Understanding the components of a distributed-database environment, and
how to manage distributed databases.
• Administrator’s Manual for Parts and Documents

This manual provides assistance in managing some Enterprise Knowledge
Management features, specifically, the Enterprise Knowledge Management
search engine.
• Installation Worksheet
This worksheet, next in this chapter, is where you can record vital information
you will need during Enterprise Knowledge Management installation. This
information is also useful after installation is complete, so keep it as a reference
for future use.
Installation Worksheet
Use this worksheet to record important information about your Enterprise Knowledge
Management installation. Throughout this manual, you will be instructed to enter values on this
worksheet and also to obtain values here when they are needed.
Oracle Users, Groups, and Directories
Oracle UNIX User Group Oracle UNIX User
Group Name: dba User Name:
Group ID: User ID:
Password:
Oracle Administrator Account Proper Name:
User Name: (Default: system) Home Directory:
Password: Default Shell:
ORACLE_SID ORACLE_HOME
or Oracle Net TNS_ADMIN
Service Name
(TWO_TASK):
Enterprise Knowledge Management Users, Groups, and Directories

Enterprise Knowledge Management UNIX Enterprise Knowledge Management Trusted
User Group User
Group Name: User Name:
Group ID: User ID:

Chapter 1 Overview
Password:
Proper Name:
Home Directory
(MTI_ROOT):
Default Shell:
Corporate Server Host Information

Host Name: Instance Name:
FLEXnet Port Number:
Port Number: (Default: 8575)
Search Engine Server

Search Engine IDOLA Port: (Default: 7702)
Host Name: IDOLI Port: (Default: 7703)
IDOLS Port: (Default: 7704)
FSF Port: (Default: 7705)
FSFS Port: (Default: 7705)

Overview
e!Vista Path and Virtual Directories

e!Vista Path:
Value of DOCS_LOCAL_DIR:
Virtual Directory for e!Vista Documents:
Name (Alias):
Path:
Virtual Directory for e!Vista CGI Programs:
Name (Alias):
Path:
Online Documentation Information

Online Documentation Path:
Online Documentation URL:
Enterprise Knowledge Management Web Applications

Web Application Name: Web Application Name:
(Default: TC)
WAR File WAR File Name:
Name:
Launch URL: Launch URL:

Chapter
2 System Requirements
Enterprise Knowledge Management and Compatible Third-Party Software

Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Web Tier Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Special Considerations for Non-English Locales . . . . . . . . . . . . . . . . . . . . . . . 2-5

Platform Support for Non-English Locales . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Invalid Character Replacement for Non-UTF-8 Multibyte Locales . . . . . . . 2-5
Environment Settings for Non-English Locales . . . . . . . . . . . . . . . . . . . . 2-6

Chapter
2 System Requirements
This chapter defines the software and hardware requirements for running Enterprise
Knowledge Management.

• Information about Enterprise Knowledge Management and compatible
third-party software versions.
• System software and hardware requirements for your Enterprise Knowledge

Management corporate server.
• Considerations for non-English locales.
Enterprise Knowledge Management and Compatible Third-Party

Software Versions
This chapter documents the minimum version of operating systems, compilers,
databases, client browsers, and other third-party software with which Enterprise
Knowledge Management 2007 is compatible. Because Enterprise Knowledge
Management releases are asynchronous with the release of compatible third-party
software, it is possible for Enterprise Knowledge Management customers to acquire
and install a newer version of third-party software before Siemens PLM Software
has the opportunity to certify it.
Siemens PLM Software’s standard policy with respect to new versions of the
operating systems, compilers, databases, client browsers, and other third-party
software relies on the manufacturers’ guarantees. If the manufacturer guarantees
that the new version of its product is binary-compatible with the preceding version,
Siemens PLM Software expects our products to function properly when running on
the new version. Our experience shows that virtually no problems are encountered
when executing Enterprise Knowledge Management with a third-party version later
than the version on which we completed our certification testing.
Siemens PLM Software will make a reasonable effort to support Enterprise
Knowledge Management running on a later version and to work with you to resolve
any difficulty that may arise but will not, in most cases, complete the testing
required to state Enterprise Knowledge Management software is certified.

Chapter 2 System Requirements
Enterprise Knowledge Management compatibility with operating systems and

compilers involves these two considerations:
• Compatibility for runtime.
• Compatibility for relinking customizations.
Typically, operating system manufacturers assure runtime binary compatibility

between the successive versions of their operating systems. We make a reasonable
effort to support Enterprise Knowledge Management running on a later version of
an operating system. To a lesser degree, operating system manufacturers provide
similar assurances when relinking or rebuilding executables and libraries with
new versions of the compilers. In cases where compatibility does not exist between
old and new compiler versions, all customization incorporated into the Enterprise
Knowledge Management base product must be linked using the version of the
compiler with which Enterprise Knowledge Management has been released. This
also applies to the installation of Enterprise Knowledge Management patches.
To summarize, Enterprise Knowledge Management may run on a newer version of
an operating system, but customizations may need to be compiled and linked on
an earlier version.
If Siemens PLM Software discovers incompatible versions of third-party

software, we will post bulletins in the UGAnswer section of GTAC. This
information is also available from your Enterprise Knowledge Management
provider.
Software Requirements
The Enterprise Knowledge Management is supported on the following platforms:
• Microsoft Windows (limited server support)1

• Hewlett-Packard HP-UX
• IBM AIX
• Sun Solaris
• SUSE Linux2
• Macintosh (limited client support)3
For information about versions of operating systems, third-party software, and

Teamcenter software that are certified for your platform, see the Siemens PLM
Software Certification Database:
http://support.ugs.com/online_library/certification/
To use the certification database, choose the platform and products you use, then
click Show Certifications.
1. No Enterprise Knowledge Management servers are supported on Windows 98 or Windows XP systems.

2. Only thin client is supported on Linux platforms.
3. Some client functionality is supported on Macintosh platforms. No Enterprise Knowledge Management servers are supported on
Macintosh platforms.

System Requirements
• The Siemens PLM Software Certification Database also provides

information on certain hardware certified for use with Enterprise
• Some software requirements differ for non-English locales. When viewing

the Siemens PLM Software certification database, make sure you note any
exceptions for your locale.
• Enterprise Knowledge Management CAD integrations are not supported

on IBM AIX platforms.
Web Tier Requirements

Enterprise Knowledge Management Web applications (thin client and rich client)
require a Siemens PLM Software-supported Web application server. For information
about supported Web application servers, see the Siemens PLM Software
Certification Database.
Hardware Requirements
Table 2-1 lists the minimum hardware requirements for the Enterprise Knowledge
Management corporate server host. For more information about planning system
resources, see the Network and Database Configuration Guide.
Table 2-1. Minimum Enterprise Knowledge Management Hardware Requirements

Component Minimum Requirement
Memory Workstation (client) hosts: 25 MB of physical memory for the
classic client plus 16 MB for each 1000 objects queried and
simultaneously displayed (or 500 objects expanded)4
Server hosts: 200 MB of physical memory
• For database server and client memory
requirements for your platform, see your Oracle
documentation.
• These requirements apply only to Enterprise

Knowledge Management. Additional memory
is required for the operating system and other
applications you use with Enterprise Knowledge
Management. For those requirements, see the
software vendor’s documentation.
• Extensively customized systems require more

memory.
4. Forty-eight MB of physical memory is required to run e!Vista.


Disk Space Corporate server: 900 MB for the corporate server with
the Enterprise Knowledge Management Foundation server
solution only. Additional server solutions require additional
disk space. If you install components, an additional 30 MB of
disk space is required for e!Vista, 190 MB for support files,
and 90 MB for online manuals.
Work group server: 340 MB
Workstation (client): 140 MB
Database server:
Oracle products: 3 GB (approximately)5
Oracle Databases (Minimum):
For single database: 200 MB
For distributed databases: 200 MB for each database (A
typical installation includes three Teamcenter databases:
administrative, key, and user.)
Swap space for server machines 100 MB minimum. The 100 MB covers the following
minimum number of servers:
1 OS_SERV
1 omfsvr
1 msqlddb
1 mserv
1 rserv
1 nlsserv
1 uidserv
1 mloader
1 notifserv
1 registry
1 postserv
1 mgrsvr
1 scheduleserv
30 MB each for each additional server.

Example:
Additional Memory Required

Servers
3 OS_SERV 90 MB (3x30=90)
5 omfsvr 150 MB (5x30=150)
5 msqlddb 150 MB (5x30=150)
Total Swap Space Required:
5. For database server and client disk space requirements for your platform, see your Oracle documentation.

System Requirements

100 MB + 90 MB + 150 MB + 150 MB = 490 MB

The values shown here are minimum requirements; for
optimal performance, use more memory. For every megabyte
of RAM memory you add, you can reduce the amount of
configured swap space by the same amount.
Special Considerations for Non-English Locales

This section describes exceptions to software requirements for non-English locales.
It also describes additional configuration required to run Enterprise Knowledge
Management in certain locales.
Platform Support for Non-English Locales

Enterprise Knowledge Management 2007 is supported in the following locales on all
server platforms stated in Software Requirements, earlier in this chapter:
• French
• German
• Hebrew
• Italian
• Japanese
• Korean
• Russian
• Simplified Chinese
• Spanish
• Traditional Chinese
Invalid Character Replacement for Non-UTF-8 Multibyte Locales

This section describes character conversion in multibyte locales using character
sets other than UTF-8.
If you use UTF-8, skip this section. Enterprise Knowledge Management
supports UTF-8 in all locales listed in Platform Support for Non-English
Locales, earlier in this section.
When running in a multibyte locale using a character set other than UTF-8,
characters received by Enterprise Knowledge Management must fall within the
valid external encoding specification byte ranges noted in table 2-2. Characters that
do not fall within the valid byte ranges are not supported and are not convertible.
Upon entry into Enterprise Knowledge Management, all characters are checked
for conformance to the external encoding specification and, if necessary, converted
to an internal encoding specification within Enterprise Knowledge Management.
Characters that fall within the internal encoding specification are not converted

and are used directly within Enterprise Knowledge Management. Table 2-2 shows
Enterprise Knowledge Management internal and external encoding specifications.
Table 2-2. Character Encoding Specifications

External Encoding Specification Internal Encoding Specification
First Second First Second
Supported Byte Byte Supported Byte Byte
Range Range Range Range
Language Method Character Sets Method Character Sets
Japanese SJIS JIS-Roman/ASCII 000–127 N/A JEUC JIS-Roman/ASCII 000–127 N/A

Half-Width Katakana 161–223 N/A JIS X 0208-1990 161–254 161–254
Two-byte characters 129–159, 64–126, Half-Width Katakana 142 161–223
224–239 128–252
JIS X 212-1990 Not supported
Korean No conversion necessary KS C KS-Roman/ASCII 000–127 N/A
KS C 5601-1992 161–254 161–254
Simplified No conversion necessary GB2312-80 0 000–127 N/A
Chinese
1 161–254 161–254
Traditional BIG5 0 000–127 N/A EUC-TW 0 000–127 N/A
Chinese
1 161–254 64–126 1 161–254 161–254
2 161–254 161–254 2 142 161–162
3 161–254 161–254
• Not all character sets are equivalent. In some cases, a platform or user
can define additional characters and add them to the base character set.
These additional characters are not convertible and are not supported.
• Any character encoded in the external encoding method that cannot be

converted into a character encoded in the internal encoding method for
a given locale is replaced by the question mark (?) character. Because
unsupported characters can comprise two or more bytes, multiple bytes
may be replaced by a single byte, and the byte length of the string
shortened. Within Enterprise Knowledge Management, and upon output
to the system, resulting strings contain these question marks in place
of the original characters.
Environment Settings for Non-English Locales

This section describes environment variables to set in non-English locales.
In non-English locales, you must specify the system locale by setting the LANG and
LC_ALL environment variables. These two variables must be identical to function
properly.
In UTF-8 environments, set LANG and LC_ALL as specified in table 2-3. In
non-UTF-8 multibyte locales, set the LANG and LC_ALL environment variables to
the values shown in table 2-4.

System Requirements
Table 2-3. Setting LANG and LC_ALL (UTF-8 Environments)

Language Operating System Value of LANG and LC_ALL
English (U.S.) IBM AIX EN_US.UTF-8
Hewlett-Packard HP-UX univ.utf8
Sun Solaris en_US.UTF-8
French IBM AIX FR_FR.UTF-8
Sun Solaris fr_FR.UTF-8
German IBM AIX DE_DE.UTF-8
Sun Solaris de_DE.UTF-8
Hebrew IBM AIX HE_IL.UTF-8
Sun Solaris he_IL.UTF-8
Italian IBM AIX IT_IT.UTF-8
Sun Solaris it_IT.UTF-8
Russian IBM AIX RU_RU.UTF-8
Sun Solaris ru_RU.UTF-8
Spanish IBM AIX ES_ES.UTF-8
Sun Solaris es_ES.UTF-8
Japanese IBM AIX JA_JP.UTF-8
Sun Solaris ja_JP.UTF-8
Korean IBM AIX KO_KR.UTF-8
Sun Solaris ko_KR.UTF-8
Simplified IBM AIX ZH_CN.UTF-8
Chinese
Sun Solaris zh_CN.UTF-8
Traditional IBM AIX ZH_TW.UTF-8
Chinese
Sun Solaris zh_TW.UTF-8

Table 2-4. Setting LANG and LC_ALL (Non-UTF-8 Environments)

Encoding Value of LANG
Language Operating System Method and LC_ALL
French IBM AIX ISO8859–1 fr_FR, fr_FR.ISO8859–1, or
fr_FR.ISO8859–15
ISO8859–15
Hewlett-Packard HP-UX ISO8859–1 fr_FR.iso88591 or fr_FR.iso885915
ISO8859–15
Sun Solaris ISO8859–1 fr, fr_FR, fr_FR.ISO8859–1, or
fr_FR.ISO8859–15
ISO8859–15
German IBM AIX ISO8859–1 de_DE, de_DE.ISO8859–1, or
de_DE.ISO8859–15
ISO8859–15
Hewlett-Packard HP-UX ISO8859–1 de_DE.iso88591 or
de_DE.iso885915
ISO8859–15
Sun Solaris ISO8859–1 de, de_DE, de_DE.ISO8859–1 or
de_DE.ISO8859–15
ISO8859–15
Hebrew IBM AIX ISO8859–8 iw_IL or iw_IL.ISO8859–8
Hewlett-Packard HP-UX ISO8859–8 iw_IL.iso88598
Sun Solaris ISO8859–8 he or he_IL
Italian IBM AIX ISO8859–1 it_IT, it_IT.ISO8859–1, or
it_IT.ISO8859–15
ISO8859–15
Hewlett-Packard HP-UX ISO8859–1 it_IT.iso88591 or it_IT.iso885915
ISO8859–15
Sun Solaris ISO8859–1 it, it_IT, it_IT.ISO8859–1 or
it_IT.ISO8859–15
ISO8859–15
Russian IBM AIX ISO8859–5 ru_RU or ru_RU.ISO8859–5
Hewlett-Packard HP-UX ISO8859–5 ru_RU.iso88595
Sun Solaris ISO8859–5 ru or ru_Ru or ru_RU.ISO8859–5
Spanish IBM AIX ISO8859–1 es_ES, es_ES.ISO8859–1, or
es_ES.ISO8859–15
ISO8859–15
Hewlett-Packard HP-UX ISO8859–1 es_ES.iso88591 or es_ES.iso885915
ISO8859–15
Sun Solaris ISO8859–1 es, es_ES, es_ES.ISO8859–1, or
es_ES.ISO8859–15
ISO8859–15

System Requirements
Table 2-4. Setting LANG and LC_ALL (Non-UTF-8 Environments)

Encoding Value of LANG
Language Operating System Method and LC_ALL
Japanese IBM AIX JEUC ja_JP
IBM AIX SJIS Ja_JP
Hewlett-Packard HP-UX JEUC ja_JP.eucJP
Hewlett-Packard HP-UX SJIS ja_JP.SJIS
Sun Solaris JEUC ja or japanese
Sun Solaris SJIS ja_JP.PCK
Korean IBM AIX KS C ko_KR
Hewlett-Packard HP-UX KS C ko_KR.eucKR
Sun Solaris KS C ko or korean
Simplified IBM AIX GB2312-80 zh_CN
Chinese Hewlett-Packard HP-UX GB2312-80 zh_CN.hp15CN
Sun Solaris GB2312-80 zh
Traditional IBM AIX BIG5 zh_TW
Chinese Hewlett-Packard HP-UX BIG5 zh_TW.big5
Sun Solaris BIG5 zh_TW.BIG5
To display multibyte character strings correctly on platforms that support multiple

encodings of a given language, the specified system locale for a shell must match
the windowing system.
Make sure that the NLS_LOCALE and NLS_LANG system environment variables
are set correctly for your locale as shown in table 2-5 (if you use UTF-8) or table
2-6 (if you do not use UTF-8).
Table 2-5. Setting NLS_LOCALE and NLS_LANG (UTF-8 Environments)

Value of
Language NLS_LOCALE Value of NLS_LANG
English en_us american_america.utf8 or
(U.S.) american_america.al32utf8
French fr_fr french_france.utf8 or
french_france.al32utf8
German de_de german_germany.utf8 or
german_germany.al32utf8
Hebrew en_us hebrew_israel.utf8 or
hebrew_israel.al32utf8
Italian it_it italian_italy.utf8 or italian_italy.al32utf8
Russian ru_ru russian_cis.utf8 or russian_cis.al32utf8

Table 2-5. Setting NLS_LOCALE and NLS_LANG (UTF-8 Environments)

Value of
Spanish es_es spanish_spain.utf8 or
spanish_spain.al32utf8
Japanese jp_jp japanese_japan.utf8 or
japanese_japan.al32utf8
Korean ko_ko korean_korea.utf8 or
korean_korea.al32utf8
Chinese simplified chinese_china.utf8 or simplified
(Simplified) zh_cn chinese_china.al32utf8
Chinese traditional chinese_taiwan.utf8 or
(Traditional) zh_tw traditional chinese_taiwan.al32utf8
Table 2-6. Setting NLS_LOCALE and NLS_LANG (Non-UTF-8

Environments)
Value of
English (U.S.) en_us american_america.weiso8859p1
american_america.weiso8859p15
French fr_fr french_france.weiso8859p1
french_france.weiso8859p15
German de_de german_germany.weiso8859p1
german_germany.weiso8859p15
Hebrew en_us hebrew_israel.iw8iso8859p8
Italian it_it italian_italy.we8iso8859p1
italian_italy.we8iso8859p15
Russian ru_ru russian_cis.cl8iso8859p5
Spanish es_es spanish_spain.we8iso8859p1
spanish_spain.we8iso8859p15
Japanese jp_jp japanese_japan.ja16euc
Korean ko_ko korean_korea.ko16ksc5601
Simplified simplified
Chinese zh_cn chinese_china.zhs16cgb231280
Traditional traditional chinese_taiwan.zht32euc
Chinese zh_tw
When setting NLS_LANG for Simplified Chinese or Traditional Chinese

locales, enclose the language name in quotation marks. For example, in
a Simplified Chinese locale in non-UTF-8 environments, enter the value
for NLS_LANG as “simplified chinese”_china.zhs16cgb231280. When
displaying environment variables, the operating system omits quotation
marks, as shown in table 2-6.

Chapter
3 Creating the Enterprise

Trusted User

Chapter
3 Creating the Enterprise

Trusted User
Before you install the Enterprise Knowledge Management corporate server, you
must create the Enterprise Knowledge Management trusted user account. This is
the account you log in to when you install Enterprise Knowledge Management.
This procedure requires root privileges. If you do not have root privileges on the
corporate server host, your system administrator must perform this procedure.
Create the trusted user account:
1. Create a UNIX user group for Enterprise Knowledge Management users

(pdmusr or a designated existing group) and assign it a group ID number. Add
the following entry to your UNIX group file:
group-name:*:group-ID:
For example, the following entry assigns the number 111111 to the pdmusr
group:
pdmusr:*:111111:
2. Create a UNIX user (pdm or other user) and assign it a user ID number,
proper name, home directory, and default shell, and assign it to the Enterprise
Knowledge Management user group. Add the following entry to your UNIX
password file:
username::user-ID:group-ID:proper-name:user-home-dir:shell
For example, the following entry creates a UNIX user named pdm with the
proper name Enterprise Knowledge Management Trusted User:
pdm::222222:111111:Enterprise Knowledge Management Trusted User:/usr/pdm:/bin/csh
3. Assign a password to the Enterprise Knowledge Management trusted user. Use

whatever utilities are provided with your operating system to create a password
for the Enterprise Knowledge Management trusted user.

Chapter 3 Creating the Enterprise Knowledge Management Trusted User
4. Add root to list of users in the Enterprise Knowledge Management user group.
For example:
pdmusr:*:111111:pdm,root
5. Create a home directory for the Enterprise Knowledge Management software,

referred to in this manual as MTI_ROOT. Enter the following command:
mkdir MTI_ROOT
For example:
mkdir /usr/pdm
The path to MTI_ROOT must not contain spaces.
6. Assign the Enterprise Knowledge Management trusted user to the Enterprise

Knowledge Management home directory by entering the following command:
chown username MTI_ROOT
For example:
chown pdm /usr/pdm
7. Assign the Enterprise Knowledge Management user group to the Enterprise

Knowledge Management home directory by entering the following command:
chgrp group-name MTI_ROOT
For example:
chgrp pdmusr /usr/pdm

Chapter
4 Installing Oracle
Oracle and Enterprise Knowledge Management Terminology . . . . . . . . . . . . . 4-1
Oracle Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Setting Database Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Obtaining Oracle Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Planning Enterprise Knowledge Management Database Configuration . . . . . . 4-6
Verifying Oracle Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Determining Character Set Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Configuring a Distributed-Database Environment . . . . . . . . . . . . . . . . . . . . . 4-9

Chapter
4 Installing Oracle
This chapter describes how to install and configure Oracle for use with Enterprise
Knowledge Management 2007.
These procedures require root privileges. If you do not have root privileges on your
system, these procedures may need to be performed by your system administrator or
by your Oracle administrator.

• Oracle and Enterprise Knowledge Management database terminology.
• Oracle installation requirements for Enterprise Knowledge Management.
• How to set environment variables for Oracle.
• How to obtain Oracle server information for Enterprise Knowledge Management

installation.
• How to plan your Enterprise Knowledge Management database configuration.
• How to verify Oracle installation.
• How to determine character set values for your locale.
• How to configure a distributed-database environment on your Oracle server.
Oracle and Enterprise Knowledge Management Terminology

Before you install Oracle and Enterprise Knowledge Management, it is important to
understand how Enterprise Knowledge Management database terminology differs
from Oracle terminology. For example:
• Enterprise Knowledge Management refers to an Oracle database a database
server.
• Enterprise Knowledge Management refers to an Oracle user as a database.

Chapter 4 Installing Oracle
Figure 4-1 shows the Enterprise Knowledge Management default databases

(administrative, key, and corporate user1) as three Oracle users in one Oracle
database.
Oracle Database
Oracle User
administrative
Oracle User
key
Oracle User
corporate user
Figure 4-1. Oracle Instance

Table 4-1 describes additional terms related to Oracle installation.
Table 4-1. Oracle Installation Terms

Term Description
Oracle owner Specifies the Oracle UNIX user name. You create
this user name during Oracle installation.
ORACLE_HOME Specifies the path to the directory containing the
Oracle software. You create this directory during
Oracle installation.
Oracle SID Specifies the Oracle system identifier, a unique
8-character name for the Oracle instance.
The Oracle SID must be unique across the
network on which you intend to run Oracle and
system account Specifies the Oracle administrator account.
Enterprise Knowledge Management uses
this account to create Enterprise Knowledge
Management databases.
Oracle Net service name Specifies an alias used by the Oracle client to
access the Oracle server.
1. In a default installation, these databases will be named admm70a, keym70a, and sum70a, respectively.

Installing Oracle
Oracle Installation Requirements

Before you install Enterprise Knowledge Management, you must install an Oracle
server or an Oracle client on the Enterprise Knowledge Management corporate
server host. Enterprise Knowledge Management 2007 supports Oracle 10g products.
Create the necessary Oracle groups, users, and directories, and install the
Oracle server or client according to the installation procedures in your Oracle
documentation. Install your Oracle server and clients using the Oracle installer,
accepting all default options unless instructed otherwise by your Oracle
administrator.
• The default sizes used by the Create DB Objects option in the Oracle
installer are sufficient to run Enterprise Knowledge Management. During
Enterprise Knowledge Management installation, Enterprise Knowledge
Management adds its own tablespaces for the databases it creates.
• On IBM AIX systems, make sure you enable asynchronous I/O before
installing Enterprise Knowledge Management. This ensures correct
linking with Oracle-related Enterprise Knowledge Management
executables. To determine whether asynchronous I/O is enabled, enter the
following UNIX command:
lsdev -C -t aio
If asynchronous I/O is enabled, the operating system displays the

following response:
aio0 Available Asynchronous I/O
If asynchronous I/O is not enabled, contact your system or database

administrator to correct this before continuing with your Enterprise
Knowledge Management installation. For more information, see the
Oracle Installation Guide for AIX-Based Systems.
For additional information about configuring Oracle for Enterprise Knowledge

Management, see the Oracle database administration appendix in the Network and
Database Configuration Guide.
Setting Database Environment Variables

After you install Oracle, set the system environment variables listed in table 4-2 in
the UNIX startup file (.cshrc, .login, or .profile) for the Enterprise Knowledge
Management trusted user.
Table 4-2. Environment Variables for Oracle With Enterprise Knowledge

Management
Environment Variable Definition
DB_VENDOR Set to ORA (this must be uppercase).

Table 4-2. Environment Variables for Oracle With Enterprise Knowledge

Management
Environment Variable Definition
ORACLE_HOME Set to the path to the directory where Oracle software
is installed.2
ORACLE_SID If you are installing Enterprise Knowledge
Management on an Oracle server host, set this
variable to the name of the Oracle instance. This
variable is not required on Oracle client hosts.
TWO_TASK If you are installing Enterprise Knowledge
Management on an Oracle client host, set this
variable to the Oracle Net service name for the
Oracle database. This variable is not required on
Oracle server hosts.
PATH Add the path to your Oracle software:
$ORACLE_HOME/bin3
Add the paths to the system tar and uncompress
commands, if they are not already present.
Do not add the path to any other tar
commands, such as the GNU tar command.
Furthermore, make sure that PATH references
the system tar command before any other tar
command.
Shared libraries path Add the path to the $ORACLE_HOME/lib directory
to the appropriate variable for your platform:
Sun Solaris: LD_LIBRARY_PATH
Hewlett-Packard HP-UX: SHLIB_PATH
IBM AIX: LIBPATH
NLS_LANG Set to a value that reflects the character set specified
in the Oracle server NLS_CHARACTERSET
parameter. For more information, see Determining
Character Set Values, later in this chapter.
To ensure your system contains all required environment variables for

Enterprise Knowledge Management, you can use the sample .login and
.profile startup files provided with Enterprise Knowledge Management.
These files are available after you copy Enterprise Knowledge Management
installation files in chapter 5, Preparing the Enterprise Knowledge
Management Environment. For more information about using sample startup
files, see appendix C, Oracle Reference.
When updating your system startup file, observe the following considerations:
2. This setting is included in the installation documentation supplied by Oracle.

Installing Oracle
• Do not set the csh noclobber option in either your .login or .cshrc file.
• If you use a .cshrc file, do not include cd commands. The Enterprise Knowledge
Management installation program assumes that the .cshrc file does not change
the environment from the environment displayed at the operating system
prompt, or changes it correctly to match the environment displayed at the
operating system prompt.
• If your startup file modifies the PATH environment variable, make sure the
Oracle coraenv command is the last command in your startup file:
source $ORACLE_HOME/bin/coraenv
Obtaining Oracle Server Information

Table 4-3 describes information about the Oracle server required by Enterprise
Knowledge Management. You must enter or verify these values during installation
of the corporate server in chapter 6, Installing Enterprise Knowledge Management.
Table 4-3. Oracle Server Values

Value Description
Default database server Specifies the Oracle instance name or alias
for the database server in which Enterprise
Knowledge Management creates databases.3 If
your corporate server host is an Oracle client
host, the Enterprise Knowledge Management
installation utility obtains this value from the
TWO_TASK environment variable. If your
corporate server host is an Oracle server host,
this value is obtained from the ORACLE_SID
environment variable.
System account user name Specifies the user name for the Oracle
administrator account (also called the system
account). The default value is system.
If you use an Oracle user account other than the
system account4 to create databases, the user
account must have the following privileges to
allow creation of databases during Enterprise
Knowledge Management installation:
CREATE USER
CREATE TABLESPACE
ALTER USER
3. Recall that in Enterprise Knowledge Management, Oracle databases are called database servers, and that Oracle users are called
databases.
4. If you are not an Oracle administrator, you may not have access to the Oracle system account. In this case, your system administrator
must create an Oracle UNIX user account that the Enterprise Knowledge Management installation utility can use to create databases
during Enterprise Knowledge Management installation.

Table 4-3. Oracle Server Values

Value Description
System account password Specifies the password for the Oracle
administrator account. The default value in the
Enterprise Knowledge Management installation
utility is manager.
Oracle does not allow manager as the system
account password during Oracle installation.
The Enterprise Knowledge Management
installation utility prompts you to enter the
correct system account password If you do not
modify the default value.
If your corporate server host is an Oracle client host, make sure you obtain
these values from your Oracle server administrator before you install Enterprise
Planning Enterprise Knowledge Management Database Configuration

By default, the Enterprise Knowledge Management installation utility creates three
distributed databases as described in table 4-4:
Table 4-4. Enterprise Knowledge Management Default Database Settings

Setting Value
Databases Three distributed databases on the default
database server:
• adminstance-name5 (administrative)
• keyinstance-name (key)
• suinstance-name (corporate user)

Tablespace names database-namespace
Tablespace location $ORACLE_HOME/dbs6
If you want to use different database settings, you can modify these settings during
Enterprise Knowledge Management installation. For example, you could choose one
of the following configurations:
• Use different names for the databases Enterprise Knowledge Management
creates.
5. For example, if the instance name is m70a, this databases are named admm70a, keym70a, and sum70a. If you change the Enterprise
Knowledge Management instance name, the installation utility changes the default database names accordingly.
6. The installation utility uses this default location unless you enter a value in the Tablespace Location field. (The default location is not
displayed.) Contact your database administrator to obtain the correct location for tablespace data files.

Installing Oracle
• Use existing databases instead of having Enterprise Knowledge Management

create them.
• Use a single database instead of distributed databases.
Before you install Enterprise Knowledge Management, determine the database

configuration you want to use.
Verifying Oracle Installation

To verify that Oracle is installed and your host has access to the Oracle server,
perform the following steps:
1. Start SQL*Plus by entering the following command:
sqlplus system
SQL*Plus displays the following prompt:

Enter password:
2. Enter the password for the Oracle administrator account. You obtained this
password in Obtaining Oracle Server Information, earlier in this chapter.
3. If SQL*Plus displays a confirmation message followed by the SQL> prompt,

access to the Oracle instance is verified. If not, contact your Oracle administrator
or your Oracle documentation for possible solutions.
4. Verify that the Oracle instance is running by entering the following command:
select sysdate from dual;
If SQL*Plus displays the system date, the Oracle instance is running. If not,
contact your Oracle administrator or your Oracle documentation for possible
solutions.
5. Close SQL*Plus by entering the following command:

exit
Do not continue with Enterprise Knowledge Management installation unless

the Oracle instance is accessible and running.
Determining Character Set Values

To ensure correct processing of non-text data in Enterprise Knowledge Management,
make sure the NLS_LANG system environment variable is set correctly for your
locale.
On the Oracle client,7 the NLS_LANG environment variable specifies a locale
and a character set for the Oracle client session.8 On the Oracle server, the
7. An Oracle client host is a host on which the msql executable is running.

8. NLS_LANG values typically specify a language, country, and character set in the format language_country.character-set.

NLS_CHARACTERSET parameter specifies the character set for the Oracle

instance. The character sets specified in NLS_LANG and NLS_CHARACTERSET
must match.
The Enterprise Knowledge Management server invokes the Oracle client during
startup, sending the NLS_LANG setting to the Oracle server. If the character
set specified in NLS_LANG differs from that in the NLS_CHARACTERSET
parameter, Oracle converts characters sent from the Oracle client (in char,
varchar2, and CLOB data types) into the Oracle server’s specified character set.
For data that is not pure text, Oracle may convert characters incorrectly.
To prevent erroneous character conversion, set the Oracle client NLS_LANG variable
to reflect the character set specified in the Oracle server NLS_CHARACTERSET
parameter. Table 4-5 lists NLS_CHARACTERSET values corresponding to
NLS_LANG values for supported locales.
Table 4-5. Supported Character Set Values

Oracle Server
NLS_CHARACTERSET
Values Oracle Client NLS_LANG Values
utf8 or al32utf8 american_america.utf8 or
american_america.al32utf8
french_france.utf8 or french_france.al32utf8
german_germany.utf8 or
german_germany.al32utf8
hebrew_israel.utf8 or hebrew_israel.al32utf8
italian_italy.utf8 or italian_italy.al32utf8
spanish_spain.utf8 or spanish_spain.al32utf8
russian_cis.utf8 or russian_cis.al32utf8
japanese_japan.utf8 or japanese_japan.al32utf8
korean_korea.utf8 or korean_korea.al32utf8
simplified chinese_china.utf8 or simplified
chinese_china.al32utf8
traditional chinese_taiwan.utf8 or traditional
chinese_taiwan.al32utf8
we8iso8859p1 american_america.we8iso8859p1
french_france.we8iso8859p1
german_germany.we8iso8859p1
we8iso8859p15 american_america.we8iso8859p15
french_france.we8iso8859p15
german_germany.we8iso8859p15
cl8iso8859p5 russian_cis.cl8iso8859p5
iw8iso8859p8 hebrew_israel.iw8iso8859p8
us7ascii american_america.us7ascii
ja16euc japanese_japan.ja16euc

Installing Oracle
Table 4-5. Supported Character Set Values

Oracle Server
NLS_CHARACTERSET
Values Oracle Client NLS_LANG Values
ko16ksc5601 korean_korea.ko16ksc5601
zhs16cgbz31280 simplified chinese_china.zhs16cgb231280
zht32euc traditional chinese_taiwan.zht32euc
When setting NLS_LANG for non-UTF-8 Simplified Chinese or Traditional

Chinese locales, enclose the language name in quotation marks. For
example, in a Simplified Chinese locale, enter the value for NLS_LANG
as “simplified chinese”_china.zhs16cgb231280. When displaying
environment variables, the operating system omits quotation marks, as shown
in table 2-6.
Set the NLS_LANG environment variable:
1. Start SQL*Plus and log in to the Oracle server as described in Verifying Oracle
Installation, earlier in this chapter.
2. Enter the following command:

select parameter, value from v$nls_parameters where parameter=’NLS_CHARACTERSET’;
SQL*Plus displays the following output:
PARAMETER VALUE
----------------------- -----------------------
NLS_CHARACTERSET value
Note the value displayed for the NLS_CHARACTERSET parameter.
3. Close SQL*Plus.
4. On the Oracle client host, set the NLS_LANG environment variable to

the appropriate value from table 4-5 that specifies your locale and the
NLS_CHARACTERSET value you found in step 2.
Perform this procedure on the corporate server host whether the host contains
an Oracle client or an Oracle server.
Configuring a Distributed-Database Environment

If you are installing Enterprise Knowledge Management in a distributed-database
environment, you must configure your Oracle server and clients by performing the
following procedures.
Configure the Oracle server:

1. Ensure that the Oracle instance is running using the procedure described in
Verifying Oracle Installation, earlier in this chapter.

2. Update the Oracle setup files:

a. Locate the following files in your $ORACLE_HOME/network/admin
directory:
listener.ora
sqlnet.ora
tnsnames.ora
Open these files in a plain text editor such as vi.
b. Edit the files to reflect your host and Oracle installation.

For examples of these files and information about how to edit them, see
Oracle Distributed Setup Files in appendix C, Oracle Reference.
c. Save each of these files in your $ORACLE_HOME/network/admin

directory.
If you save the Oracle setup files to a different directory, you must set
the TNS_ADMIN system environment variable to the path containing
these files.
3. Stop and restart the Oracle listener process by entering the following commands:
lsnrctl stop LISTENER_HOSTNAME
lsnrctl start LISTENER_HOSTNAME
Replace HOSTNAME with the name of the Oracle server host.
4. Update the Oracle initialization file:

a. Shut down the Oracle server.
b. Locate the initSID.ora file (where SID is the Oracle instance name) in your
$ORACLE_HOME/dbs directory. Open this file in a plain text editor such
as vi.
c. Add the following line to the file:

global_names = FALSE
d. Locate the open_links parameter in the file. Change its value to at least
the number of Enterprise Knowledge Management databases plus 2. For
example, if you use the three default databases (administrative, key, and
corporate user), set this parameter to 5 or higher. (The default value is 4.)
e. Locate the open_cursors parameter in the file. Ensure that it is set to a

value between 200 and 500.
(The open_cursors parameter should be set to a minimum of 200 for normal
Enterprise Knowledge Management operations. If you are performing
clustering, increase open_cursors to 500.)
f. Save the changes to the initSID.ora file and close the text editor.
g. Restart the Oracle server.

Installing Oracle
If Oracle issues error number 2020 while Enterprise Knowledge

Management 2007 is running, the value of the open_links parameter
is set too low. Repeat this procedure setting a higher value for the
open_links parameter.
5. Verify access to the Oracle instance as described in Verifying Oracle Installation,

earlier in this chapter.
Configure the Oracle client:
1. Locate the following files in the $ORACLE_HOME/network/admin directory

on the Oracle server host:
listener.ora
sqlnet.ora
tnsnames.ora
2. Copy these files to the $ORACLE_HOME/network/admin directory on the

Oracle client host.9
9. An Oracle client host is any host on which the msql executable is run.

Part
II Installing the Enterprise Tier
Preparing the Enterprise Knowledge Management Environment . . . . . . . . . . 5-1
Installing Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . . . . . . 6-1
Configuring Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . . . . . 7-1

Chapter
5 Preparing the Enterprise

Environment
Setting System Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Installing Enterprise Knowledge Management Licenses . . . . . . . . . . . . . . . . . 5-2

Setting the LM_LICENSE_FILE Environment Variable . . . . . . . . . . . . . . 5-3
Configuring the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Starting the License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Using the Enterprise Knowledge Management License Manager
Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Using an Existing License Manager Daemon . . . . . . . . . . . . . . . . . . . 5-6

Chapter
5 Preparing the Enterprise

Environment
This chapter describes how to prepare your system environment for Enterprise
Knowledge Management installation by setting Enterprise Knowledge Management
environment variables and starting the FLEXnet Manager license manager. After
completing these procedures, you can begin installing Enterprise Knowledge
Management as described in chapter 6, Installing Enterprise Knowledge
Management.

• How to set system environment variables required for Enterprise Knowledge
Management.
• How to copy Enterprise Knowledge Management installation files to your host.
• How to install Enterprise Knowledge Management licenses and start the license
manager.
Setting System Environment Variables

Set the following system environment variables on your Enterprise Knowledge
Management corporate server host. Use whatever method and startup file (.login,
.profile, or .cshrc) are appropriate for your platform.
• PATH
To ensure Enterprise Knowledge Management can access required applications,
add the following entries to your PATH system environment variable:
– Web browser path

Add the path to an Enterprise Knowledge Management-supported Web
browser.
– C compiler
If you customize Enterprise Knowledge Management and if your PATH
statement includes paths to more than one C compiler, ensure that the path

to the Enterprise Knowledge Management-required compiler precedes that

for any other compiler. (For compiler requirements, see chapter 2, System
Requirements.)
For example, on the Sun Solaris platform, ensure that the PATH statement
lists the path to the Sun C compiler before the path to any other C compiler,
such as /usr/ucb/cc.
• VC_HOSTNAME (Optional)
If you want to assign your Enterprise Knowledge Management corporate server
host a name other than the physical server host name, set VC_HOSTNAME to
the name you want Enterprise Knowledge Management to use. If this variable is
not defined in the system environment, Enterprise Knowledge Management uses
the physical host name as the corporate server host name.
Copying Installation Files

Before you install Enterprise Knowledge Management, you must copy installation
files from the Enterprise Knowledge Management distribution image to your host.
1. Log in as the Enterprise Knowledge Management trusted user. (You created this
user in chapter 3, Creating the Enterprise Knowledge Management Trusted User.)
2. Locate the Enterprise Knowledge Management software distribution image for

your platform on your local computer or network.
3. Change to the MTI_ROOT directory. (You created this directory in chapter 3,

Creating the Enterprise Knowledge Management Trusted User.)
4. Enter the following commands to copy Enterprise Knowledge Management

installation files to your host:
cat image-path/CoreMethodServers/platform/INSTALL_BASE.TZ |
uncompress -c | tar xvf -
cat image-path/CoreMethodServers/platform/INSTALL_CFGEDIT.TZ |
uncompress -c | tar xvf -
Replace image-path with the full path to the Enterprise Knowledge Management
distribution image.
Installing Enterprise Knowledge Management Licenses

The Enterprise Knowledge Management installation utility verifies available
licenses before installing Enterprise Knowledge Management. This section describes
how to install the Enterprise Knowledge Management license file provided by your
Enterprise Knowledge Management vendor.
Siemens PLM Software provides the Macrovision FLEXnet Manager license manager
with Enterprise Knowledge Management. You installed the license manager when
you copied Enterprise Knowledge Management installation files to your system. If
you use a previously installed FLEXnet license manager for other applications on
your network, you may use your existing license manager or the license manager
provided with Enterprise Knowledge Management. This manual assumes you use
the license manager provided with Enterprise Knowledge Management.

Preparing the Enterprise Knowledge Management Environment
If you use a previously installed FLEXnet license manager, you may use the
same license manager daemon (lmgrd) to manage the Enterprise Knowledge
Management license file in any of the following configurations:
• Single license server node, single daemon, single license file.
• Single license server node, single daemon, multiple license files.
• Single license server node, multiple daemons, multiple license files.
• Multiple license server nodes, running one daemon and one license file
each.
For information about using an existing license manager daemon to manage

multiple license files, see the FLEXnet Licensing End User Manual in your
FLEXnet software directory or at MTI_ROOT/htmlman/EndUser/TOC.htm
after Enterprise Knowledge Management installation is complete. For more
information about Enterprise Knowledge Management licensing, see the
Administrator’s Manual.
Setting the LM_LICENSE_FILE Environment Variable

Enterprise Knowledge Management requires the LM_LICENSE_FILE environment
variable to contain the path to the Enterprise Knowledge Management license file
on all server hosts.
Using whatever method and startup file (.login, .profile, or .cshrc) are appropriate
for your platform, set LM_LICENSE_FILE to the following path:
MTI_ROOT/install/licenses.mti1
Replace MTI_ROOT with the path to your Enterprise Knowledge Management
home directory.
After you set LM_LICENSE_FILE, source your startup file to initiate the changes
to your system environment. Log in as the Enterprise Knowledge Management
trusted user.
Enterprise Knowledge Management executes programs that use the
X-Window System. To ensure proper operation, make sure each user’s PATH
environment variable includes the X11 bin directory.
Configuring the License File

To configure the license file for your Enterprise Knowledge Management installation,
perform the following steps:
1. Open the license file in a plain text editor. Figure 5-1 shows an example of an
Enterprise Knowledge Management license file.
1. On a local area or work group server, set LM_LICENSE_FILE to port@host-name as described in chapter 13, Installing Local Area and
Work Group Servers.

################################################################################
# #
# UGS Corp. #
# License File #
# #
# Sold-To/Install: 82621 WebKey Access Code: QVYYH372KT #
# Contact Name: JOHN SMITH Created: 06/09/2005 #
# Customer Name: ACME CORP #
# E-mail Address: john.smith@acmecorp.com Version: 4 #
################################################################################
#
# Enterprise license files containing the TS_OK attribute
# to enable use of a Terminal Server client in an
# Enterprise 3.1 and later environment can be requested
# by submitting an email to DSOM@ugs.com.
#
SERVER YourHostname ag63bc5 8575
VENDOR mtid
INCREMENT acd mtid 50.0 permanent uncounted C1B8FFCC9B93 HOSTID=ANY \
SUPERSEDE ISSUED=09-jun-2005 ck=86
INCREMENT apc mtid 50.0 permanent uncounted DEC434597452 HOSTID=ANY \
INCREMENT author mtid 50.0 permanent 175 979C9A7B8010 HOSTID=ANY \
SUPERSEDE DUP_GROUP=UHD ISSUED=09-jun-2005 ck=115
INCREMENT c9t mtid 50.0 permanent uncounted 97FACDF581B2 HOSTID=ANY \
INCREMENT ccf mtid 50.0 permanent uncounted 7D28653FB13D HOSTID=ANY \
INCREMENT ccm mtid 50.0 permanent uncounted D40EF4BDB821 HOSTID=ANY \
INCREMENT cms mtid 50.0 permanent uncounted 402FEA959642 HOSTID=ANY \
INCREMENT cnf mtid 50.0 permanent uncounted 97FACDF581B2 HOSTID=ANY \
INCREMENT consumer mtid 50.0 permanent 275 EA685A2B9192 HOSTID=ANY \
SUPERSEDE DUP_GROUP=UHD ISSUED=09-jun-2005 ck=108
INCREMENT dmm mtid 50.0 permanent uncounted 7D28653FB13D HOSTID=ANY \
INCREMENT lcm mtid 50.0 permanent uncounted 62E536E4687E HOSTID=ANY \
INCREMENT omf mtid 50.0 permanent uncounted D40EF4BDB821 HOSTID=ANY \
INCREMENT psm mtid 50.0 permanent uncounted 402FEA959642 HOSTID=ANY \
INCREMENT vpd mtid 50.0 permanent uncounted AB58DB71B961 HOSTID=ANY \
FEATURE server_id mtid 40.0 permanent 1 3B8FC5A2D73F \
VENDOR_STRING="82621 - ACME CORP" user_info=QVYYH372KT \
ISSUER=UGS ck=90
Figure 5-1. Sample License File
2. Locate the lines in the license file that resemble the following:
SERVER YourHostname ag63bc5 8575
VENDOR mtid
3. Replace YourHostname with the name of the host on which you run the license
manager.
The value 8575 in the SERVER line specifies the default port used by the
license manager. If this port is in use by another program on your system,
replace 8575 with the port number you want the license manager to use.2
4. To the line that begins VENDOR mtid, add the path to the license manager
daemon mtid. (In a default installation, this value is MTI_ROOT/install/mtid.)
For example:
VENDOR mtid /tc50a/install/mtid
Make sure you include a space before the path to the license manager
daemon.
2. Valid port numbers are values between 1024 and 65535. For a list of assigned port numbers, see the /etc/services file.

Preparing the Enterprise Knowledge Management Environment
5. Name the file licenses.mti and save it in your MTI_ROOT/install directory.
If you change your license manager host, you must generate a new license file.
You can generate a new permanent license file by following the instructions at
the Siemens PLM Software License Management site:
http://www.ugs.com/Support/LicenseManagement
You must have a Siemens PLM Software WEBKEY account to use this service.
You must also provide the lmhostid value for your license manager host. You
can find this value by entering the lmutil lmhostid command from your
FLEXnet Manager directory.
Starting the License Manager

This section describes how to start FLEXnet Manager. Perform one of the following
procedures, depending on which license manager daemon you use.
Using the Enterprise Knowledge Management License Manager Daemon

To start the license manager, enter the following command:
lmgrd
If the license manager starts successfully, FLEXnet displays a message similar to

the following:
17:45:57 (lmgrd) -----------------------------------------------
17:45:57 (lmgrd) Please Note:
17:45:57 (lmgrd)
17:45:57 (lmgrd) This log is intended for debug purposes only.
17:45:57 (lmgrd) In order to capture accurate license
17:45:57 (lmgrd) usage data into an organized repository,
17:45:57 (lmgrd) please enable report logging.
.
.
.
17:45:57 (lmgrd) Contact Macrovision at
17:45:57 (lmgrd) www.macrovision.com for more details on how to
17:45:57 (lmgrd) obtain an evaluation copy of FLEXnet Manager
17:45:57 (lmgrd) for your enterprise.
17:45:57 (lmgrd)
17:45:57 (lmgrd) -----------------------------------------------
17:45:57 (lmgrd)
17:45:57 (lmgrd)
17:45:57 (lmgrd) pid 5416
17:45:57 (lmgrd) Done rereading
17:45:57 (lmgrd) FLEXnet Licensing (v10.1.3) started on AcmeCorp (Sun) (6/9/2005)
17:45:57 (lmgrd) Copyright (c) 1988-2004 by Macrovision Corporation. All rights reserved.
17:45:57 (lmgrd) US Patents 5,390,297 and 5,671,412.
17:45:57 (lmgrd) World Wide Web: http://www.macrovision.com
17:45:57 (lmgrd) License file(s): /tc50a/install/licenses.mti
17:45:57 (lmgrd) lmgrd tcp-port 8575
17:45:57 (lmgrd) Starting vendor daemons ...
17:45:57 (lmgrd) Started mtid (pid 4156)
17:45:58 (mtid) FLEXnet Licensing version 10.1.3
17:45:58 (mtid) Server started on AcmeCorp for: omf
17:45:58 (mtid) psm apc ccm
17:45:58 (mtid) dmm lcm pfm
17:45:58 (mtid) vpd smm ccf
17:45:58 (mtid) cms d5u d6p
17:45:58 (mtid) d7s d8i acd
17:45:58 (mtid) pro tds ids
17:45:58 (mtid) clg mdv ace
17:45:58 (mtid) c9t b8e cnf
17:45:58 (mtid) b2a ecs asb
17:45:58 (mtid) asm author consumer
17:45:58 (lmgrd) mtid using TCP-port 2426

• You can check the license manager daemon status at any time by entering
the following command:
lmutil lmstat -a
• If necessary, you can shut down the license manager by entering the
following command:
lmutil lmdown
Using an Existing License Manager Daemon
If you use a previously installed FLEXnet Manager daemon, start the license
manager using whatever method is required by your FLEXnet administrator.
For information about using an existing license manager daemon to manage
multiple license files, see the FLEXnet Licensing End User Manual in your FLEXnet
software directory or at MTI_ROOT/htmlman/EndUser/TOC.htm after Enterprise
Knowledge Management installation is complete. For more information about
Enterprise Knowledge Management licensing, see the Administrator’s Manual.

Chapter
6 Installing Enterprise Knowledge

Management
Before Installing Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . 6-1

Before Installing on Linux or Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Before Installing on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Before Installing on HP-UX Itanium . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Prerequisites for Enterprise Knowledge Management on HP-UX
Itanium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Installing the Enterprise Knowledge Management Corporate Server . . . . . . . . 6-2
Completing the Enterprise Knowledge Management Installation . . . . . . . . . . 6-7
Verifying Linux Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Performing Optional Postinstallation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Restricting Access to the Server Launching Program . . . . . . . . . . . . . . . . 6-9
Setting Shared Library Permissions on AIX Systems . . . . . . . . . . . . . . . . 6-10
Automating Database and Services Startup . . . . . . . . . . . . . . . . . . . . . . 6-10

Chapter
6 Installing Enterprise Knowledge

Management
This chapter describes how to install and configure your Enterprise Knowledge
Management corporate server using the Enterprise Knowledge Management
installation utility. For information about installing Enterprise Knowledge
Management on a local area or work group server, see chapter 13, Installing Local
Area and Work Group Servers.
For instructions on upgrading an existing Enterprise Knowledge Management
server installation, see the appropriate upgrade guide (for Enterprise Knowledge
Management 2005 SR1, 3.1, or 3.0).
Before Installing Enterprise Knowledge Management

The sections that follow describe prerequisites for Enterprise Knowledge
Management corporate server on Linux, AIX, and HP-UX Itanium systems.
Before Installing on Linux or Solaris

Before you install the Enterprise Knowledge Management corporate server on a
Linux or a Solaris system, Siemens PLM Software recommends that you prepend
the PATH variable to the MTI_ROOT/bin path to avoid database issues when you
use the dropdb command to delete a database.
Run the following command to prepend the PATH variable:
setenv PATH $MTI_ROOT/bin:$MTI_ROOT/install:$PATH
Before Installing on AIX

The tcp_nodelay kernel TCP/IP parameter on AIX systems is set to zero (0) by
default. There is a possibility for some network latency because of this when
communicating between Enterprise layers over AIX-to-AIX TCP/IP interfaces.
Before you install the Enterprise Knowledge Management corporate server on an
AIX system, Siemens PLM Software recommends that you set the tcp_nodelay
kernel parameter to 1.
Example:
tcp_nodelay=1
For more information, see AIX documentation.

Chapter 6 Installing Enterprise Knowledge Management
Before Installing on HP-UX Itanium

Enterprise Knowledge Management for HP-UX Itanium® is a 64 bit application
for 64 bit HP-UX Itanium. The installation procedure for installing Enterprise
Knowledge Management on HP-UX Itanium is similar to installing Enterprise
Knowledge Management on any other UNIX/Linux platform.
For converting 32 bit custom modules to 64 bit custom modules on 64 bit
HP-UX Itanium, no changes are required if you use standard method-level
APIs. If you use low-level C/C++ functions during customization, follow
the standard porting procedures for porting 32 bit applications to 64 bit
applications.
For more information about migrating applications from a 32 bit platform to a
64 bit platform, see HP-UX Itanium documentation.
For information about integrations, solutions, software, clients and CAD tools
not supported on HP-UX Itanium, see Release Bulletin for Enterprise Knowledge
Management 2007.
Prerequisites for Enterprise Knowledge Management on HP-UX Itanium
Before installing Enterprise Knowledge Management on HP-UX Itanium, install

the LDAP-UX integration bundle that provides access to the directory services of an
LDAP directory server. For more information, see the following site:
http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?
productNumber=J4269AA
Installing the Enterprise Knowledge Management Corporate Server

This section describes how to launch the Enterprise Knowledge Management
installation utility, define the contents and settings of your corporate server, then
begin installation.
Launch the Enterprise Knowledge Management installation utility:

1. Change to the MTI_ROOT/install directory and enter the following command:
cfgedit2
This command launches the Enterprise Knowledge Management installation

utility (figure 6-1).

Installing Enterprise Knowledge Management
Figure 6-1. Enterprise Knowledge Management Installation Utility
2. Click Install. The installation utility displays the Enterprise Knowledge

Management Installation dialog window (figure 6-2).
Figure 6-2. Enterprise Knowledge Management Installation Dialog Window
3. Define the settings and content for your corporate server and begin installation
as described in the following procedures.
Enter instance information:
1. In the Instance Name field, enter a 1–5 character name (alphanumeric

characters only) for the Enterprise Knowledge Management instance. The
default instance name is m70a.
You can run multiple instances of Enterprise Knowledge Management on
a single host with unique instance names for each.1
2. In the Port Number field, enter the IP port used by the Enterprise Knowledge
Management MUX for this instance. The default value for this field is 7701.
The MUX port number must be different from the port used by the FLEXnet
license manager, which by default is 8575.2
Enter disk locations:

1. If the Disk Locations for Install Images field does not contain the correct path to
the Enterprise Knowledge Management software distribution image, select the
default path shown and click Modify to correct the path.
2. If you are installing additional Enterprise Knowledge Management software

from multiple disk locations, click Add to add locations of other software images.
If necessary, remove paths by selecting them in the list and clicking Remove.
1. Enterprise Knowledge Management runs separate MUX and dispatcher services for each instance.
2. Valid port numbers are values between 1024 and 65535.

The installation utility searches disk locations in the order they are
displayed in the Disk Locations for Install Images field and installs each
software component from the first directory in which it finds the files
needed.
Select server solutions:
1. If you want to add server solutions, click Solutions.

The Teamcenter’s Foundation server solution is required and is selected
by default, as shown in the Selected Server Solutions field.
2. Select the server solutions you want to add.

If you use any of the thin client solutions (on the Web tier) listed in table 6-1,
make sure you select the corresponding server solutions shown.
Table 6-1. Required Server Solutions for Thin Client Solutions

Thin Client Solution Required Server Solutions
Authorized Data Access Authorized Data Access
Change Management Change Management
Rapid Change Management
Teamcenter Conferencing Interface Conferencing Server
Global Data Synchronization Global Data Synchronization
Part Family Manager Part Family Manager
Design Configurator Product Configurator
Product Configurator
Model Option Manager
Product Designer
Teamcenter’s portfolio, program and Project Integration
project management Integration
Program Execution Program Execution
Records Management Application Records Management Application
Valid Value Editor Valid Value Editor
Prerequisite server solutions are shown in brackets ([ ]) and are selected

automatically for each server solution.
Enter database information:
1. Click Advanced Database Information.
2. In the Modify Database Information dialog window, click the Database Servers
tab.
3. In the Database Servers field, select your database server, then click Modify.

4. In the Modify Database Server dialog window, enter the password for the Oracle
administrator account in the System Password field.3
5. Enter any other values you need to modify in the Modify Database Server dialog
window, then click OK.
6. If you want to modify the default database configuration, click the Databases
tab and enter the changes you want to make. Otherwise, click OK.
For information about the default Enterprise Knowledge Management database
configuration, see Planning Enterprise Knowledge Management Database
Configuration in chapter 4, Installing Oracle.
For information about modifying database information, see the Network and
Select components:
1. If you want to add e!Vista, online documentation, or support files to your
corporate server, click Add Component. Otherwise, skip the remaining steps in
this procedure and proceed to Begin installation:, next in this section.
2. In the Add Component dialog window, select the components you want to install:
Product Description
e!Vista Server libraries for e!Vista. This is required if your
corporate host contains a Web server that will serve
e!Vista clients.
Online documentation Library of manuals for all Enterprise Knowledge
Management products, accessible through a Web
browser.
Support files Software libraries needed to customize the Enterprise
Knowledge Management server solutions you install.
3. If you want to change the installation path for a component, click Browse to
choose a different path. Otherwise, click OK.
Specify advanced encryption settings:

1. If you want to specify advanced encryption settings, click Advanced Encryption
Settings. Otherwise, skip the remaining steps in this procedure and proceed to
Begin installation:, next in this section.
Teamcenter’s enterprise knowledge management supports encryption and
decryption of user and database passwords using federal information processing
standards (FIPS) 140-2 compliant algorithms.
2. In the Advanced Encryption Settings window, select the Enable FIPS 140-2
checkbox to enable the FIPS security algorithm.
3. In the Key File Directory field, specify the directory where the key file is stored.
3. You obtained this password from your database administrator in Obtaining Oracle Server Information in chapter 4, Installing Oracle.

4. In the Key File Name field, specify the name of the key file.
5. From the Encryption Mode dropdown list, select the FIPS or Domestic option.
The default option is FIPS. It provides the maximum security as it uses certified
algorithms.
6. Click OK to enable FIPS.

Begin installation:
1. In the Enterprise Knowledge Management Installation dialog window, click

OK to begin the installation.
The installation utility launches the Enterprise Knowledge Management
Configuration Editor to perform installation processes, which include the
following:
a. Generating supporting files.
b. Launching the Enterprise Knowledge Management installation script
(insmenu).
c. Building the optimized MODeL file.
d. Building the optimized form file.
e. Building the optimized text file.
f. Creating databases, if specified.
A status dialog window displays the progress of the installation.
2. When installation is complete, click OK to close the status dialog window.
When installation is complete, Enterprise Knowledge Management displays

the Configuration Editor, which allows you to further configure the Enterprise
Knowledge Management network. For information about configuring Enterprise
Knowledge Management, see chapter 7, Configuring Enterprise Knowledge
Management.
• If installation fails or if the Configuration Editor displays error messages,
see appendix B, Troubleshooting, for possible solutions.
• The Enterprise Knowledge Management osql, bulkdump, and bldrora

utilities in the MTI_ROOT/bin directory allow access to information
in Enterprise Knowledge Management databases. After you complete
Enterprise Knowledge Management installation, Siemens PLM Software
recommends restricting access to these utilities to allow only the owner or
a specific group of users to execute them.
For more information about securing network access to the database,
see the information about using database utilities in the Network and

Completing the Enterprise Knowledge Management Installation

Install the Enterprise Knowledge Management network services:
1. Log in as root.
2. Change to the MTI_ROOT/install directory and source the root.sh script :4

cd MTI_ROOT/install
./root.sh
Automate the setting of Enterprise Knowledge Management environment

variables:
1. Open your system startup file (.login, .cshrc, or .profile) in a plain text editor.
2. Add the following statements to your startup file:
.login or .cshrc file:

if ( -f MTI_ROOT/config/pdmsetup ) then
source MTI_ROOT/config/pdmsetup
endif
.profile file:
if [ -r MTI_ROOT/config/pdmsetup.sh ]; then
. /MTI_ROOT/config/pdmsetup.sh
fi
• Perform this procedure for every Enterprise Knowledge Management

user.
• Because the Enterprise Knowledge Management classic client uses

the X-Window System, Siemens PLM Software recommends that
each user’s startup file add the path to the X11 bin directory to the
system path.
3. If you are installing on a Windows system, skip this procedure.

Open your system startup file (.login, .cshrc, or .profile) in a plain text editor.
Launch the classic client:
1. Verify the license manager status by entering the following command from the
install directory under MTI_ROOT:
lmutil lmstat -a
If necessary, restart the license manager as described in Starting the License

Manager in chapter 5, Preparing the Enterprise Knowledge Management
Environment.
4. The installation script creates the root.sh script in the MTI_ROOT/install directory during Enterprise Knowledge Management
installation.

2. Run the Enterprise Knowledge Management setup file (pdmsetup) to set

Enterprise Knowledge Management environment variables:5
C shells: source MTI_ROOT/config/pdmsetup
Korn and Bourne shells: . /MTI_ROOT/config/pdmsetup.sh
3. Start the Enterprise Knowledge Management network:6

netstart
4. Launch the classic client:

omf &
If installation is successful, the classic client displays the Enterprise Knowledge

Management Home Collection (figure 6-3).
Figure 6-3. Enterprise Knowledge Management Home Collection

If the classic client does not launch, check the installation log for errors or see
appendix B, Troubleshooting.
Verifying Linux Installations

Classic client is not supported on the SUSE Linux platform. After you install the
Enterprise Knowledge Management server on SUSE Linux, you can install the
thin client on any other machine and connect to the server to verify the server
installation. Alternatively, you can install Enterprise Knowledge Management
5. If you automated setting of Enterprise Knowledge Management environment variables, this is performed automatically when you
log in.
6. The netstart command starts the Enterprise Knowledge Management communication services (MUX and dispatcher) and generates
network status log files in the directory from which you enter the command. The log files are named muxlog.n, dsplog.n, and dspout.n,
where n denotes a session number.

foundation on any other machine, connect to the server and perform normal
operations such as check in or check out to verify the server installation.
Performing Optional Postinstallation Steps

The following tasks are not required by Enterprise Knowledge Management, but
Siemens PLM Software recommends that you perform these to automate startup of
certain programs and services and to address system security issues.
Restricting Access to the Server Launching Program

The olaunch executable represents a potential security problem. This executable is
used to launch OS servers that run as different users and therefore is installed as a
set-UID program owned by root. Public access to the olaunch program can be a
security problem because it can be used to launch other programs as well. Access to
olaunch should be restricted to the owner of the dispatcher process. This is usually
the Enterprise Knowledge Management trusted user.
Access can be restricted in one of two ways: either by a control file or by file/directory
permissions.
• If the /etc/olaunch.usr file exists, olaunch only allows itself to be used by the
users listed in that file. The file is expected to contain UNIX user names listed
one per line. The name of the user running the installation procedures is put
into this file by the root.sh script output of the installation procedures, but
is not required by olaunch.
• Access also can be restricted by denying other users execute access to the
olaunch file. Since olaunch is owned by root, it is not effective to allow only
owner-execute permission on the file itself, because the Enterprise Knowledge
Management trusted user must execute it. However, if the Enterprise Knowledge
Management trusted user is a member of a trustworthy group, olaunch can be
assigned to that group and can be given owner and group execute permission
only. If group permits are not sufficient to restrict access, olaunch can be moved
to a directory to which only the Enterprise Knowledge Management trusted
user has search permission. If this is done, the configuration variable for the
OS_SERV entry in the service configuration map (service.cfg) must be updated
to the new path.
Generally, it is considered a security risk to allow someone to start an
Enterprise Knowledge Management operating system server (OS_SERV)
as root. The Enterprise Knowledge Management software includes checks
to disallow this.
Siemens PLM Software does not recommend validating the UNIX root
account on any host as any Enterprise Knowledge Management user. It is
more common to validate other UNIX users to have Enterprise Knowledge
Management super user privileges. At a minimum, this would include the
UNIX user that is the Enterprise Knowledge Management trusted user.
If you must run as root, you must circumvent the Enterprise Knowledge
Management security check by placing the file olaunch.su in the /etc
directory. The file need not contain anything; it must simply exist in this
directory.

Setting Shared Library Permissions on AIX Systems

If other file permission on AIX shared libraries is set to read, updates to those
shared libraries (such as installing an Enterprise Knowledge Management patch or
a new custom server) do not take effect until you issue the AIX slibclean command.
Examine the file permissions on the shared libraries (the .so files in MTI_ROOT/bin)
to verify that the permissions are what you intend. If other file permission is set to
read, you must issue the slibclean command whenever you update (by installing a
patch or installing a new custom server, for example) any of the shared library files.
If you do not issue the slibclean command, the dlopen command can fail when
you attempt to use it to open libraries. For more information about the slibclean
command and the dlopen function, see the UNIX man pages.
For more information about setting file permissions, see the discussion of the umask
command in the Oracle administration appendix in the Network and Database
Configuration Guide.
Automating Database and Services Startup

The procedure in this section applies to an Oracle server host only (not a client host).
In some installations, starting Oracle during startup of the operating system is more
convenient than starting the database manually. This section describes how to
automate Oracle startup.
For Oracle startup information, see Oracle’s platform-specific installation guide for
uses of the Oracle scripts dbstart and dbshut. On some platforms, Oracle does not
recommend using the dbshut script. Note that the dbstart script only starts the
database. It does not start the SQL*Net listener program. If you want the listener,
as well, to come up automatically, you must create your own script for this and
add it to the startup sequence after dbstart. You also need to create a script to
stop the listener.
The following is a sample script for dbstart_listener:
#!/bin/csh
lsnrctl start LISTENER_HOSTNAME
The following example is a sample dbshut_listener script:

#!/bin/csh
lsnrctl stop LISTENER_HOSTNAME
For Enterprise Knowledge Management, you can create a script (called pdmstart)
to start the MUX communication program and dispatcher. This is a simple script
that is run by the Enterprise Knowledge Management account. For example:
pdmstart
#!/bin/csh
cd $MTI_ROOT
netstart
An example of the entry in the startup script follows:

su - pdm -c MTI_ROOT/config/pdmstart
If Enterprise Knowledge Management startup is added to the procedures, it

must start after Oracle is started and must stop before Oracle is shut down.

A shutdown script for Enterprise Knowledge Management is another simple script

that needs to run before you run the Oracle dbshut script. The following is a sample
Enterprise Knowledge Management script:
pdmstop
#!/bin/csh
dspstop
muxstop
The entry in the shutdown script resembles the following example:

su - pdm -c MTI_ROOT/config/pdmstop

Chapter
7 Configuring Enterprise
Configuring the Enterprise Knowledge Management Indexed Search Engine . . 7-2

Installing the Indexed Search Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Configuring Indexed Search Languages . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Setting Configuration Variables for Teamcenter Security Services . . . . . . . . . . 7-5
Loading Administrative Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Chapter
7 Configuring Enterprise
This chapter describes how to configure certain Enterprise Knowledge Management

features using the Configuration Editor. These features include the following:
• Indexed search
• Administrative data
You can configure your Enterprise Knowledge Management network using the
Configuration Editor (figure 7-1).
Figure 7-1. Enterprise Knowledge Management Configuration Editor

The Configuration Editor allows you to set Enterprise Knowledge Management
configuration variables, change database settings, map services, and perform many
other configuration tasks on your Enterprise Knowledge Management corporate
server.
To launch the Configuration Editor, change to the MTI_ROOT/install directory and
enter the cfgedit2 command.

Chapter 7 Configuring Enterprise Knowledge Management
Configuring the Enterprise Knowledge Management Indexed Search

Engine
The Enterprise Knowledge Management indexed search engine enables you to
retrieve objects from the database based on search criteria. It allows you to specify
searches on metadata values, as well as full text retrieval searches on both metadata
and common forms of text data.
Installing the Indexed Search Engine

To install the indexed search engine, perform the following steps:
1. Launch the Configuration Editor.
2. Make sure the Enterprise Knowledge Management software distribution image

is available at the path specified in the Disk Locations for Install Images field.
3. Click Modify Database Information. The Configuration Editor displays the

Modify Database Information dialog window (figure 7-2).
Figure 7-2. Modify Database Information Dialog Window
4. Click the Search Engines notebook card.
5. Click Add.
6. In the Name field, enter a name for the Autonomy IDOL search engine. The
default name is DRE followed by a number, for example, DRE1.
You must have administrative privileges to install a search engine.

When you install Autonomy IDOL search engine, only one IDOL server
can run at a time on a machine. To install another IDOL server on the
same machine, you must stop the DiSH service for the other IDOL server.
This is because the IDOL server requires the DiSH service for retrieving
license information and two DiSH services cannot run on a single port.

Configuring Enterprise Knowledge Management
7. In the Search Engine Host field, select the host on which you want the search
engine service to run.1
8. Under Default Language, select a default language for your site.
9. If you want the search engine to use different port numbers than the default
values shown, consult your network administrator for available port numbers,
then update the port numbers you want to change.
10. Select the databases you want to index for search by selecting the database
names and clicking Add or Remove.
11. Click OK. The Configuration Editor launches the search engine installer.
12. When the search engine installation is complete, close the Modify Database
Information dialog window.
13. Activate the search engine by setting the SEARCH_ENGINE_USE

configuration variable (in the Configuration Editor) to a value of ALL.2
For more information about managing the Enterprise Knowledge Management

indexed search engine, see the Administrator’s Manual for Parts and Documents.
• For information about removing the Enterprise Knowledge Management
indexed search engine, see appendix F, Uninstalling Enterprise Knowledge
Management.
Configuring Indexed Search Languages

Several configuration variables are used together to configure the languages in
which data is to be indexed and searched.
Table 7-1. Configuration Variables for Indexed Search

Variable Description
SE_SUPPORTED_ Specifies the set of languages Enterprise Knowledge
LANGUAGES Management supports for indexing and searching
via the search engine. Do not change the value of
this configuration variable from the default value.
Enterprise Knowledge Management supports
the following languages for indexing and
searching:
• English • Italian
• French • Spanish
• German • Finnish
1. The indexed search can engine can be installed on your corporate server or on a local area or work group server, but is not supported
on workstation (client) hosts. The Search Engine Host field displays all server hosts in your network.
2. Valid values for the SEARCH_ENGINE_USE configuration variable are ALL, INDEX, PAUSE, or NONE. For descriptions of these values
and how to set them, see the Configuration Editor Online Help or the Network and Database Configuration Guide.

Chapter 7 Configuring Enterprise Knowledge Management
Table 7-1. Configuration Variables for Indexed Search

• Chinese • Danish
(Simplified) • Norwegian
• Chinese • Swedish
(Traditional) • Japanese (SJIS)
• Korean
• Hebrew
SE_LANGUAGES Specifies the set of languages in which you want
to allow indexing and searching via the search
engine. The default value is “English”. You can
add languages to this value as a comma-separated
list of values, enclosed in double quotation marks.
Values in the list must be chosen only from the list
of values in the SE_SUPPORTED_LANGUAGES
variable and must be spelled exactly the same
as those values, including capitalization. If you
want to include a language that has variants (such
as Chinese, which has simplified and traditional
variants), specify only the base language (such
as Chinese). Enterprise Knowledge Management
determines the variant using other system
information.
SE_DEFAULT_INDEX_ Specifies the default language for search indexing.
LANGUAGES The default value is “English”. If you want
to specify a different default index language,
choose a value from the list of values in the
SE_SUPPORTED_LANGUAGES variable.
SE_DEFAULT_INDEX_LANGUAGES must
contain one value only, enclosed in double quotation
marks, for example, “French”.
You can assign host-specific or site-specific values
for this variable. This allows you to specify a default
search language according to locale, for example,
specifying “Japanese” as the default language for
hosts located in Japan.
For navigation bar searches and identifier searches (searches defined by a

user’s attribute choices in the Advanced Search page), if a user specifies
no search preference, the search engine uses the language specified by the
SE_DEFAULT_INDEX_LANGUAGES variable as the search language.
If a user specifies a search language, that selection overrides the value in
SE_DEFAULT_INDEX_LANGUAGES.
The values specified in the SE_LANGUAGES variable determine the selection of
search language checkboxes on the Limits tab of Advanced Search pages. Individual
users can specify search language preferences using My Preferences settings.
User’s language preferences determine which search language checkboxes are
automatically preselected in search pages. If a user does not specify a search

Configuring Enterprise Knowledge Management
language preference, the thin client preselects the language specified in the
SE_DEFAULT_INDEX_LANGUAGES variable.
The classic client does not use the SE_LANGUAGES or search preferences.
The classic client performs all searches using all languages.
Setting Configuration Variables for Teamcenter Security Services

If you use Teamcenter Security Services, set the SSO_SERVICE_URL configuration
variable to the URL to the Single Sign-On Login Service Web application. This value
must match the value of the mwau.login.sso.service.url context parameter you
set when you install Product Data Management on the Web tier.
For more information about setting context parameters, see Modifying Context
Parameters in chapter 9, Installing Thin Client Solutions.
Loading Administrative Data

In addition to performing the procedures in this chapter, you can create and load
administrative items for certain Enterprise Knowledge Management features. For
more information, see chapter 11, Setting Up Administrative Data.

Part
III Installing the Web Tier
Installing the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Installing Thin Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Deploying an Enterprise Knowledge Management Web Application . . . . . . . . . 10-1

Chapter
8 Installing the Web Application

Manager
Creating the WEB_ROOT Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Launching the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Chapter
8 Installing the Web Application

Manager
This chapter describes how to install the Teamcenter Web Application Manager,
which you use to install Enterprise Knowledge Management Web applications.
Before you install the Web Application Manager, install a Siemens PLM
Software-supported Web application server on your Web application server
host. For information about Web application servers certified for your
platform, see the Siemens PLM Software Certification Database:
Creating the WEB_ROOT Directory

Create a root directory on the Web application server host for the Web Application
Manager and the thin client solutions you install (for example, /tcweb). This
directory is referenced as WEB_ROOT.

Copy installation files for the Web Application Manager and the Teamcenter
presentation tier:
1. Locate the Enterprise Knowledge Management software distribution image for
your platform on your local computer or network.
2. Change to the WEB_ROOT directory.
3. Enter the following commands to copy Web Application Manager installation

files to your host:
cat image-path/INSTALL_TCWEB.TZ | uncompress -c | tar xvf -
cat image-path/INSTALL_TC_PTIER_BASE.TZ | uncompress -c | tar xvf -
Replace image-path with the full path to the Enterprise Knowledge Management
distribution image.

Chapter 8 Installing the Web Application Manager
Launching the Web Application Manager

To launch the Web Application Manager, change to the WEB_ROOT directory and
enter the insweb command.
After you install and launch the Web Application Manager, you can install thin
client solutions as described in chapter 9, Installing Thin Client Solutions., next in
this chapter.

Chapter
9 Installing Thin Client Solutions
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Creating Thin Client Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Modifying Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Modifying Context Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Adding Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Reinstalling Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Generating a Deployable File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Configuring Nonapplet Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
Authentication and Proxies for File Transfers . . . . . . . . . . . . . . . . . . . . . 9-9
Configuring Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Configuring Teamcenter Conferencing Solution . . . . . . . . . . . . . . . . . . . . 9-10
Configuring Online Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Configuring Over-the-Web WebPD Installer . . . . . . . . . . . . . . . . . . . . . . . 9-12
Configuring Teamcenter Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Configuring Teamcenter Project Integration . . . . . . . . . . . . . . . . . . . . . . 9-15
Configuring Teamcenter Content Management . . . . . . . . . . . . . . . . . . . . 9-16

Chapter
9 Installing Thin Client Solutions
This chapter describes how to install thin client solutions using the Teamcenter
Web Application Manager.
This chapter describes how to create and modify thin client Web applications, and
how to configure thin client solutions.
Before You Begin

Before you begin installing Enterprise Knowledge Management thin client solutions,
make sure you complete the following tasks:
• Install the Web Application Manager as described in chapter 8, Installing the
Web Application Manager.
• Make sure your corporate server contains the prerequisite server solutions
for all thin client solutions you want to install. If necessary, add any missing
prerequisite server solutions to the corporate server as described in chapter 15,
Adding Server Solutions and Components.
• If you use the following Teamcenter products, install Application Registry1 as

described in the Teamcenter Application Registry Installation manual:
– Teamcenter Interface thin client solutions2
– Enterprise Knowledge Management integrations with other Teamcenter
products (such as Teamcenter’s portfolio, program and project management
or Teamcenter’s systems engineering and requirements management)
– Global Services
Creating Thin Client Web Applications

This section describes how to install Enterprise Knowledge Management thin client
solutions on your Web application server host using the Web Application Manager.
1. Application Registry is provided in the Teamcenter Enterprise Services software distribution image.
2. Teamcenter Interface thin client solutions integrate Enterprise Knowledge Management with other Teamcenter products such as
Teamcenter’s portfolio, program and project management using Application Registry.

Chapter 9 Installing Thin Client Solutions
Launch the Web Application Manager:

1. Change to the WEB_ROOT directory.
2. Enter the insweb command.

Copy solution installation files:
1. Click Copy ICDs.
2. In the Copy ICD Files dialog window, click Browse to locate and select the
INSTALL_ENTERPRISE.JAR file. Alternatively, you can enter the path to
the INSTALL_ENTERPRISE.JAR file, including the file name in the path.3
3. Click OK to copy ICD files.
Create a Web application:

1. Click Add to begin creating a new Web application.
2. Enter values for the Name and Staging Location fields for your Web application
and, optionally, a description of the Web application.
3. Make sure the Disk Locations for Install Images field contains the correct path
to the Enterprise Knowledge Management files. (This is the path from which you
copied installation files in Copy solution installation files:, earlier in this section.)
If necessary, select the path shown and click Modify to correct it.
If you are installing solutions from multiple disk locations, click Add to add
additional paths. If necessary, remove paths from the list by selecting them
and clicking Remove.
For each selected solution, the Web Application Manager searches disk locations
in the order shown in the Disk Locations for Install Images field and installs
from the first directory in which it finds the files needed.
4. Click Solutions.
5. Select the solutions you want to install.

Some solutions contain mutually exclusive components and must be
deployed separately from other solutions. The Web Application Manager
disables solutions that are incompatible with selected solutions.
If a solution requires other solutions, the Web Application Manager
automatically selects prerequisite solutions.
6. If you want to further configure your Web application, click Advanced Web
Application Options. The Advanced Web Application Options dialog window
allows you to specify the following options:
• File name for the deployable file.4
3. The INSTALL_ENTERPRISE.JAR file is in the image-path/UNIX directory in the Enterprise Knowledge Management Web clients
distribution image.
4. The Web Application Manager builds a deployable WAR or EAR file, depending on the Thin client solutions you select.

Installing Thin Client Solutions
• Whether to copy ICD files locally.
• Web application session timeout, in minutes.
• Whether to make the Web application distributable.
For information about these options, see the Web Application Manager Help.
7. After you make your selections, click OK.
8. Enter values for the required Enterprise Knowledge Management context

parameters described in table 9-1.
After you finish entering values, click OK. The Web Application Manager installs
the selected solutions.
Table 9-1. Context Parameters for Product Data Management

Parameter Description
compressResponse Specifies whether the response to the client can
be compressed if the requesting client supports it.
Enter true or false.
cacheCompressedStaticResource Specifies whether responses for static resources
OnServer should be cached on the server. Enter true or
false.
This parameter is used only if the
compressResponse parameter is set to
true.
responseCompressionThreshold Specifies the threshold, in bytes, beyond which the
server should compress responses sent back to the
client. Enter the threshold number in bytes.
Change this value only if absolutely necessary.
staticResourceClientCache Specifies the maximum time (in seconds) for which
ExpiryTime the client can use locally cached static content.
Enter the number of seconds after which the locally
cached files should expire.
MUXHost Specifies the MUX host name. Enter the host
name of the machine that runs the MUX used by
your Web application server host.
MUXPort Specifies the MUX port number. Enter the port
number used by the MUX on your corporate server
host. The default value is 7701.
mwau.allow.applets Specifies whether to allow Enterprise Knowledge
Management clients to download applets. The
default value is true. For more information
about this parameter, see Configuring Nonapplet
Operation, later in this chapter.
mwau.allow.cascading.menus Specifies whether to enable cascading menus in
the navigation bar. The default value is true.

Table 9-1. Context Parameters for Product Data Management

mwau.login.sharedlogin.use_ Specifies whether the shared login feature in the
client_cache MWAU Login Manager should cache credentials
on client hosts.5 for the Web application you are
building. Set to true or false. The default value
is false.
mwau.login.sharedlogin.force_web_ Specifies whether to force web browser clients to
browser_login log in even if shared login in the MWAU Login
Manager caches credentials on client hosts. Set to
true or false. The default value is false.
mwau.login.sso.enable Specifies whether to enable single sign-on. Set to
true or false. The default value is false.
mwau.login.sso.application.id Specifies the application ID by which Teamcenter
Security Services will recognize your Web
application. Set this parameter if you use
Teamcenter Security Services. The default value
is TCEnterprise.
mwau.login.sso.login.service.url Specifies the URL to the Web application that
contains the Single Sign-On Login Service thin
client solution. Set this parameter if you use
Teamcenter Security Services. Make sure this
value matches the value you specified in the
SSO_SERVICE_URL configuration variable on
the corporate server.6
mwau.login.sso.service.url Specifies the URL to the Web application that
contains the Single Sign-On Service thin client
solution. Set this parameter if you use Teamcenter
Security Services.
mwau.allow.activex Specifies whether to allow Enterprise Knowledge
Management clients to download ActiveX controls.
The default value is true. This parameter
affects Windows hosts running Microsoft Internet
Explorer. For more information about this
parameter, see Configuring Nonapplet Operation,
mwau.allow.native.urlcon Specifies whether to use Java URLConnection.
Set this parameter if you use a native Windows
Authentication environment. Enter true or false.
5. Shared login reduces the number of authentication operations you perform when working in a session with multiple components
or applications that are integrated with Enterprise Knowledge Management. For example, if you use Product Data Management,
shared login functionality allows you to share an established client credential in a secured way among applets and Microsoft Office
applications that run on the client machine.
6. You set this configuration variable in Setting Configuration Variables for Teamcenter Security Services in chapter 7, Configuring

• To set a context parameter, double-click the current value in the Value

column, then enter the new value.
• Depending on the solutions you select, additional context parameters

may be required. For more information, see Configuring Solutions,
• For more information about the Single Sign-On Login Service and
Single Sign-On Service thin client solutions, see the Security Services
Installation/Customization manual.
Build and deploy the Web application:
1. After solution installation is complete, build a deployable file:
a. If you select Automatically Build Deployable File7 in the Advanced Web
Application Options dialog window, you can skip this procedure.
In the Modify Web Application dialog window, click Generate Deployable
File.
b. Enter a name for the deployable file in the Deployable File Name field
(alphanumeric characters only), then click OK.
If you plan to deploy multiple Web applications from the same staging
location, make sure you give each deployable file a unique name.
c. When deployable file generation is complete, click OK to close the Progress

dialog window.
2. Deploy the Web application as described in chapter 10, Deploying an Enterprise

Knowledge Management Web Application.
For convenience, record the name of your Web application, the name of the
deployable file, and the launch URL on the Installation Worksheet in chapter
1, Overview.
For more information about modifying and customizing Web applications, see
the Thin Client Customization manual.
Modifying Web Applications

To modify an installed Web application, perform the following steps:
1. Launch the Web Application Manager.
2. In the Web Applications list, select the application you want to modify and
then click Modify.
The Web Application Manager displays the Modify Web Application dialog
window (figure 9-1).
7. If you select this option, the Web Application Manager automatically builds a deployable file after you install Enterprise Knowledge
Management solutions.

Figure 9-1. Modify Web Application Dialog Window
The following sections describe some of the procedures you can perform from the
Modify Web Applications dialog window.
Modifying Context Parameters

To modify context parameters for the selected Web application, perform the following
steps:
1. In the Modify Web Application dialog window, click Modify Context Parameters.
The Web Application Manager displays the Modify Context Parameters dialog
window (figure 9-2).
Figure 9-2. Modify Context Parameters Dialog Window
2. In the Name column, select the context parameter you want to change.

The Req field indicates whether the selected context parameter is required.
Required context parameters must contain a value.
The Description for Selected Parameter field contains a description of the
selected context parameter.
3. In the Value column, double-click the current value and then change the value.
4. When you finish modifying context parameters, click OK.
If you use Oracle Application Server 10g, Siemens PLM Software recommends
that you set the compressionResponseWrapperImplComplyWithSpec
context parameter to false to disable servlet specifications. By default,
this value is set to true. This context parameter works in conjunction
with compressResponse context parameter and is applicable only if
compressResponse is set to true. compressResponse is set to true by
default.
Changes to context parameters do not take effect until you generate a
deployable file and deploy the Web application on your Web application
server. For more information, see Generating a Deployable File, later in this
chapter, and chapter 10, Deploying an Enterprise Knowledge Management
Web Application.
Adding Solutions
To add solutions to the selected Web application, perform the following steps:
1. In the Modify Web Application dialog window, click Add Solutions.
2. Select the solutions you want to add, then click OK.

The Web Application Manager installs the selected solutions. The Progress
dialog window displays the progress of the installation.
3. When installation is complete, click OK to close the Progress dialog window.
To complete installation of new solutions, perform the procedures in

Configuring Solutions, later in this chapter, and chapter 10, Deploying an
Enterprise Knowledge Management Web Application.
Reinstalling Solutions
The Web Application Manager allows you to reinstall a previously installed
Teamcenter’s enterprise knowledge management solution. This is helpful if you
want to install a later version of a solution than the version currently installed. To
reinstall a solution, perform the following steps:
1. In the Modify Web Application dialog window, click Reinstall Solutions.
The Web Application Manager displays the Reinstall Solutions dialog window.
2. In the Solutions Available For Re-Installation field, select the solutions you want
to install, then click OK. If you click OK without selecting any solutions, the Web
Application Manager reinstalls all solutions in the list.

If the Web Application Manager does not detect any solution components that
are newer than those already installed, it displays the following prompt:
No new components detected. Do you want to force reinstallation
of all components for the selected solutions?
If you want to continue with the reinstallation, click Yes. Otherwise, click No to
cancel reinstallation.
To complete the reinstallation, perform the procedures in chapter 10,
Deploying an Enterprise Knowledge Management Web Application.
Generating a Deployable File

To manually create a deployable file8 for your Web application, perform the following
steps:
1. If you select Automatically Build Deployable File9 in the Advanced Web
Application Options dialog window, you can skip this procedure.
In the Modify Web Application dialog window, click Generate Deployable File.
2. Enter a name for the deployable file in the Deployable File Name field
(alphanumeric characters only), then click OK.
If you plan to deploy multiple Web applications from the same staging
location, make sure you give each deployable file a unique name.
3. When deployable file generation is complete, click OK to close the Progress

dialog window.
For more information about modifying and customizing Web applications, see the
Thin Client Customization manual.
Configuring Nonapplet Operation

Enterprise Knowledge Management thin client solutions such as Product Data
Management support nonapplet operation. This offers enhanced security by not
requiring applets to be downloaded to thin client hosts. The Java SE Runtime
Environment (JRE) is not required on client hosts if nonapplet operation is enabled.
If you use Mozilla browsers, you must configure nonapplet operation because
Mozilla does not support applets.
To enable nonapplet operation, set the following context parameters to false in

the Web Application Manager:
mwau.allow.applets
mwau.allow.activex
mwau.login.sharedlogin.use_client_cache
8. Depending on the solutions you select, the deployable file will be either a Web archive (WAR) or enterprise archive (EAR) file.
9. If you select this option, the Web Application Manager automatically builds a deployable file after you install Enterprise Knowledge
Management solutions.

Nonapplet operation disables some Enterprise Knowledge Management

functionality, including the following:
• Microsoft Office interface10
• Online Manuals solution
• Shared login
Authentication and Proxies for File Transfers

To configure authentication and proxies for file transfers, set the context parameters
as described in table 9-2.
Table 9-2. Context Parameters: Authentication and Proxies for File

Transfers
Parameter Value Description
mwau.allow.native.urlcon true • Good support for authentication
and proxies
mwau.allow.native. false • Faster mode
urlcon.limited.to.http.1_0 • Large files supported
• Works in HTTP 1.1 networks
only
This is the default setting for 2007.1

MP releases and 2009 releases.
mwau.allow.native.urlcon true • Good support for authentication
and proxies
mwau.allow.native. true • Slower mode
urlcon.limited.to.http.1_0 • Large files not supported
• Works in HTTP 1.0 or 1.1
networks
mwau.allow.native.urlcon false • Poor support for authentication
and proxies
mwau.allow.native. ignored • Slower mode
urlcon.limited.to.http.1_0 • Large files not supported
• Works in HTTP 1.0 or 1.1
networks
This is similar to the default mode

in 5.0 and 2005 SR1 releases.
10. Microsoft Office interface menu options are still displayed in Microsoft Office applications if the Microsoft Office interface was
activated before nonapplet operation was enabled. For information about activating the Microsoft Office interface to Enterprise
Knowledge Management, see the Client Installation manual.

Configuring Solutions
This section describes additional procedures to configure thin client solutions using
the Web Application Manager.
Configuring Teamcenter Conferencing Solution

To configure Teamcenter Conferencing Solution, perform the following steps:
1. Make sure your Web application server has access to the Teamcenter Conference
Server. The Teamcenter Conference Server is provided on the Teamcenter
Enterprise Services software distribution image. For information about
installing the Teamcenter Conference Server, see the Conferencing Server
Installation Guide.
2. Set the context parameters as described in table 9-3.
Table 9-3. Context Parameters for Teamcenter Conferencing Solution

conference.showlink Specifies the method for running the
conferencing client. Set this value to
application if you want to enable
Teamcenter Conferencing Solution to
install the Application Sharing client
application on client hosts. Set this value
to applet if you want all client hosts to
use only the conferencing applet, which
provides limited conferencing features.
conference.host Specifies the host name of the conference
server.
conference.port Specifies the port number used by
the conference server. Siemens PLM
Software recommends using the default
value (443).
conference.meetingkeyname Specifies the value of the name attribute
for the meetingKey tag defined
in the confConfig.xml file on the
Teamcenter Conferencing server. For
more information, see the Installing the
Teamcenter Conferencing Server chapter
in the Teamcenter Conferencing Server
Installation and Upgrade Guide.

Table 9-3. Context Parameters for Teamcenter Conferencing Solution

conference.meetingkeyvalue Specifies the value of the value attribute
for the meetingKey tag defined in the
confConfig.xml file on the Teamcenter
Conferencing server.
The
conference.meetingkeyname
and
conference.meetingkeyvalue
must match their corresponding
attributes in the confConfig.xml
to enable conferencing.
conference.refreshratesec Specifies an interval, in seconds, at which
the thin client refreshes the contents of
the Meetings page.
3. On the corporate server, assign users to conferencing user groups.

To enable conferencing options on thin client hosts, you must add users to
either the conference host grp group or the conference viewer grp group.
Table 9-4 describes which conferencing options are available on thin client
hosts, depending on the group to which a user is assigned and the value of the
conference.showlink context parameter.
Table 9-4. Conferencing Options Enabled on Thin Clients

Value of conference.showlink
Context Parameter
Group application applet
conference host grp Create Join view-only
Join interactive
Join view-only
conference viewer grp Join interactive Join view-only
Join view-only
No conference group No conferencing options No conferencing options
assignment
Configuring Online Manuals

If you installed Online Manuals, perform the following steps to enable the Online
Manuals link in the navigation bar that provides access to online manuals.
1. After you create a Web application containing the Online Manuals solution,
generate a .WAR file and deploy the .WAR file on your Web application server.

2. In each Web application in which you want to enable the Online Manuals link in
the navigation bar, set the onlineDocsDeploymentURL context parameter to the
location of the installed online manuals:
http://host-name:port-number/Web-application-name/teamcenter/onlinedocs/
defaultlocale/mtibooks
Replace host-name with the name of your Web application server host.
Replace port-number with the port number used by your Web application server.
Replace Web-application-name with the name of the application that contains
the Online Manuals solution.
For example, if your host-name is AcmeCorp, your Web
application server uses port 7001, and your application
name is TCENTDOCS, set onlineDocsDeploymentURL to
http://AcmeCorp:7001/TCENTDOCS/teamcenter/onlinedocs/
defaultlocale/mtibooks.
3. Rebuild and deploy each Web application for which you enable the Online
Manuals link
The Online Manuals solution uses applets. If you enable nonapplet operation,
the Online Manuals solution is disabled. For more information about
nonapplet operation, see Configuring Nonapplet Operation, earlier in this
chapter.
After you complete installation of the Online Manuals solution, you can access the
online manuals collection from the thin client by pulling down the Help menu and
choosing Online Manuals.
Configuring Over-the-Web WebPD Installer

The Over-the-Web WebPD Installer solution automatically installs document
management components and other client-side enhancements on Enterprise
Knowledge Management client hosts when needed.11 These components include
the following:
• Tool agent and other data transfer tools
• Adobe Acrobat plug-in
• Adobe Illustrator plug-in
• Microsoft Office interface
• Microsoft Outlook integration
• File Management Services (FMS) client cache, or FCC
For example, if a client host initiates a view action on an Adobe PDF file, and WebPD
is configured to install the Adobe plug-in for Enterprise Knowledge Management,
WebPD installs the plug-in on the client if the plug-in is not already present. WebPD
also updates the plug-in if an older version is installed on the client.
11. Alternatively, you can install these components manually using the WebPD standalone installation program on Windows client hosts
or the dminstall installation program on UNIX client hosts. For more information about these programs, see the Client Installation
manual.

Using the Web Application manager, you can enable or disable automatic installation
of client components, and you can configure the behavior of the Over-the-web WebPD
Installer solution.
To configure automatic installation of WebPD components, set the context
parameters in table 9-5 using the procedure described in Modifying Context
Parameters, earlier in this chapter.
Table 9-5. Context Parameters for Over-the-Web WebPD Installer

webpd.overtheweb Specifies whether to enable automatic
installation of WebPD components. Acceptable
values are true and false. The default value
is true.
webpd.verbose Specifies the level of prompting displayed
during installation of document management
components. The following values are
acceptable:
• VERBOSE
• INFORMATION
• QUIET
VERBOSE and INFORMATION levels prompt

users to initiate the installation. The QUIET
level informs the user that installation has been
initiated, but requires no user interaction. The
default value is VERBOSE.
webpd.msoffice Specifies whether to install the Microsoft Office
interface during automatic installation of
document management components. Acceptable
values are true and false. The default value
is true.
webpd.adobe Specifies whether to install the Adobe Acrobat
plug-in for Enterprise Knowledge Management
during automatic installation of document
management components. Acceptable values
are true and false. The default value is true.
webpd.outlook Specifies whether to install the integration to
Microsoft Outlook. The default value is true.
webpd.os Contains a list of operating systems on which
you want to automatically install document
management components. Acceptable values
are WIN98, NT,WIN2000, XP, and WIN2003.
The default value is WIN2000,XP,WIN2003.
webpd.targetdir Specifies the target directory in which to
install document management components
on Windows client hosts. The default value
is C:\Program Files\Siemens PLM
Software\Teamcenter 2007\Enterprise\.

Table 9-5. Context Parameters for Over-the-Web WebPD Installer

webpd.removeapps Specifies which applications to automatically
uninstall to avoid component conflicts during
installation of WebPD. Valid values are as
follows:
• WINCLNT: Specifies to uninstall the
Windows classic client, if it is detected.
• PATS: Specifies to uninstall the document
management print and translation services
(PATS), if detected.
• NONE: Specifies to not uninstall software
during WebPD installation.
The default value is NONE.

webpd.fcc.install Specifies to install the FMS client cache (FCC)
during WebPD installation or update. The
default value is false.
webpd.fcc.targetdir Specifies the target directory in which to install
the FCC on Windows client hosts. The default
value is C:\Program Files\Siemens PLM
Software\FMS.
webpd.fcc.cacheloc Specifies the cache directory for the FCC. The
default value is $HOME/fcccache.
webpd.fcc.read Specifies the default read cache size used by the
cachesize FCC. The default value is 100.
webpd.fcc.write Specifies the default write cache size used by
cachesize the FCC. The default value is 100.
webpd.fcc.parenthost Specifies the FSC parent host value to be used
by the FCC client for FMS.
webpd.fcc.parent Specifies the port used by the FCC client to
hostport communicate with FMS. This value must be
integer between 1 and 65535.
• The WebPD integration with Microsoft Outlook requires additional steps

on each client host to complete installation. For more information about
these steps, see the Client Installation manual.
• If you disable automatic installation of client components, you must

install these components manually on each client host using the WebPD
standalone installation program on Windows client hosts or the dminstall
installation program on UNIX client hosts. For more information about
these programs, see the Client Installation manual.
• For more information about using FMS, see the Network and Database
Configuration Guide manual.

Configuring Teamcenter Interface

To configure the Teamcenter Interface solution, set the context parameters as
described in table 9-6.
Table 9-6. Context Parameters for Teamcenter Interface

TeamcenterApplication Specifies the URL of the Teamcenter
RegistryURL Application Registry. The registry contains
the GUIDs for available Teamcenter Project
and Teamcenter Requirements application
instances to which you can connect.
(This registry must be installed to enable
Teamcenter Interface object linking.)
TeamcenterEnterprise Specifies the GUID for this Teamcenter
InstanceGUID Enterprise application instance which
is registered in Teamcenter Application
Registry. If you did not enter a GUID when
registering this Teamcenter Enterprise
instance, the registry generates a GUID.
You can look up the GUID for this
instance using the Administration Editor
(with the Teamcenter Interface Enabled
Administration Editor solution added to it).
TeamcenterProject Set to true to display the Projects tab in the
InterfaceIntegration thin client.
TeamcenterRequirement Set to true to display the Requirements tab
InterfaceIntegration in the thin client.
Configuring Teamcenter Project Integration

To configure the Teamcenter Project Integration, set the context parameters as
Table 9-7. Context Parameters for Teamcenter Project Integration

TeamcenterProject Specifies the value of the GUID used by
IntegrationGUID Teamcenter Project. This must match the
value defined in the Teamcenter Application
Registry.
TeamcenterProject Specifies the path and file name of the log
IntegrationLog file to which Teamcenter Project Integration
errors are stored.
TeamcenterProject Specifies the Enterprise Knowledge
IntegrationUserName Management user name used to create and
update Enterprise tasks, submit to life cycles,
and create Project links.

Table 9-7. Context Parameters for Teamcenter Project Integration

TeamcenterProject Contains a scrambled password for the
IntegrationUserPassword Enterprise Knowledge Management user.
For more information about configuring the Teamcenter Project Integration, see the
Teamcenter Interoperability Enterprise—Project manual.
Configuring Teamcenter Content Management

To configure Teamcenter Content Management, set the context parameters as
Table 9-8. Context Parameters for Content Management

Translation_Publishtool Specifies the tool used to create documents
for translation. For example, XSL
Formatter.
Translation_Defaultstyle Specifies the default style type to be used
for translation.
Translation_LanguageName Specifies the master language of the
content management system.
ProcessingData_TopicTypeName Specifies the smallest processing data tag
that can be used by other schemas.
MUXHost Specifies the MUX host name. Enter the
host name of the machine that runs the
MUX used by Product Data Management.
MUXPort Specifies the MUX port number. Enter the
port number used by the MUX on Product
Data Management.
Vault Specifies the vault on the Enterprise
Knowledge Management server to which
the objects created in Product Data
Management are transferred.
VaultLocation Location where the files are transferred.
The required location selection rule has to
be created. For more information about
how to write location selection rules,
see the Writing Rules chapter in the
Administrator’s Manual.
MaxBlobSize Files smaller than the MaxBlobSize are
stored as blobs and not as data items.
For more information about configuring Teamcenter Content Management, see the
Teamcenter Administrator’s Manual for Content Management.

Chapter
10 Deploying an Enterprise
Web Application
Deploying the Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Configuring the Web Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Web Tier Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Java Heap Sizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Active Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Server Housecleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
JSP Page Recompilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Servlet Check Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Chapter
10 Deploying an Enterprise
Web Application
This chapter describes how to deploy a thin client Web application on a Web
application server. It also describes how to configure your Web application server for
optimal performance with Enterprise Knowledge Management Web applications,
and it describes how to verify installation of your Web applications.
Make sure you generate a deployable file for your thin client Web application before
you begin the procedures in this chapter.
Some thin client solutions require additional installation steps on client hosts.
For information about these client-side installation steps, see the Client
Installation manual.
Deploying the Web Application

Before you start your Web application on the Web application server, you must deploy
the deployable file (Web-application-name.WAR or Web-application-name.EAR)1
generated by Web Application Manager. The method you use depends on the Web
application server you use.
The Web Application Manager places the deployable file in the staging directory. For
example, if your WEB_ROOT directory is /webbase and your Web-application-name
is TC, this file is /webbase/staging/TC.WAR.
Deploy the WAR or EAR file as documented for your Web application server. Make
sure you define the context root as the name of your Web application, for example,
TC.
Start the Web application if it does not start automatically. Some Web application
servers must be restarted to load configuration changes.
1. The deployable file is a Web archive (.WAR) or enterprise archive .EAR file, depending on the solutions it contains.

Make sure you consult your Web application server documentation for any
additional configuration steps that may be required to complete deployment
of Web applications.
Configuring the Web Application Server

Some Web application servers require special configuration for use with Enterprise
Knowledge Management. The Enterprise Knowledge Management software
installation process creates a directory structure that accommodates various Web
application servers. If you use one of the following Web application servers, perform
the appropriate procedure in this section to configure the application server to use
Teamcenter Visual Cache components:
• Sun Java System Application Server 8
• Sun Java System Web Server 6.1
Sun Java System application server and Sun Java System Web server do not
support spaces in file names or directory names.
Configure Sun Java System Application Server 8:

1. In the Sun Java System Application Server, open the administration console.
2. Deploy your WAR files for your Enterprise Knowledge Management Web
applications.
For appropriate Web application names, context values, and WAR files,
see the AdapterWars.txt file in the WEB_ROOT\Siemens PLM
Software\Teamcenter2007\DataAccess directory.
For information about deploying WAR files, see your Sun Java System
Application Server documentation.
3. For each Web application you deploy, set the Java Virtual Environment (JVM)
environment variable to the home directory of each application.
4. In the Sun server.policy file, add the following lines after the last entry in
the file:
permission java.util.PropertyPermission "*", "read, write";
permission java.io.FilePermission "WEB_ROOT\Siemens PLM Software\
Teamcenter2007\DataAccess\Products\-",
"read, write, delete, execute";
permission java.security.SecurityPermission "insertProvider.SunJCE";
permission java.security.SecurityPermission "insertProvider.SunJSSE";
Replace WEB_ROOT with the directory that contains the Web Application
Manager.
5. If you print using the Visual Cache browser, add the following line to the file:
permission java.io.FilePermission "VVCP_INSTALL_DIR\
Siemens PLM Software\Teamcenter2007\Visualization\VVCP\-", "execute";
6. Save the file and restart your Web application server.

Deploying an Enterprise Knowledge Management Web Application
Configure Sun Java System Application Server 6.1:

1. Deploy your WAR files for your Enterprise Knowledge Management Web
applications.
For appropriate Web application names, context values, and WAR files,
see the AdapterWars.txt file in the WEB_ROOT\Siemens PLM
Software\Teamcenter2007\DataAccess directory.
For information about deploying WAR files and setting environment
variables for the JVM, see your Sun Java System Application Server
documentation.
2. From the Server Manager Web page, set adapter home directories for your Web
applications.
3. Set user access controls for read, write, and delete access:
a. From the Server Manager Web page, choose the Preferences tab, then
click Restrict Access. The application server displays the Access Control
List Management Web page.
b. Click Edit Access Control, under A, and select a resource. The application
server displays the Access Control Rules dialog window.
c. From the Allow anyone row, choose the Rights column and click the
currently assigned value. The application server displays the Access Rights
dialog window.
d. Click All Access Rights and then click Update.
e. From the Allow all row, choose the Rights column and click the currently
assigned value. The application server displays the Access Rights dialog
window.
f. Click All Access Rights and then click Update.
g. When finished, click Submit from the Access Control Rules Web page.
Open the magnus.conf file and add the following line to the end of the file:
Init fn="register-http-method" methods="PROPFIND,OPTIONS,SEARCH,MKCOL,COPY,LOGOUT"
4. In the obj.conf file, locate the *~magnus-internal/* expression and modify

it as follows:
Service method="(GET|HEAD|POST|PROPFIND|OPTIONS|SEARCH|MKCOL|COPY|LOGOUT)"
type=*~magnus-internal/* fn="send-file"
5. In Sun server.policy file, add the following lines after the last entry in the file:
permission java.io.FilePermission "WEB_ROOT\Siemens PLM Software\Teamcenter2007\
DataAccess\Products\-", "read, write, delete, execute";
Replace WEB_ROOT with the directory that contains the Web Application
Manager.
6. If you print using the Visual Cache browser, add the following line to the file:

permission java.io.FilePermission "VVCP_INSTALL_DIR

\Siemens PLM Software\Teamcenter2007\Visualization\VVCP\-", "execute";
7. Save the file and restart your Web application server.
Web Tier Performance Tuning

J2EE server application engines require server-specific performance tuning in order
to provide efficient performance. The Web application servers used by Teamcenter’s
enterprise knowledge management have default tuning parameter values that are
not suitable for a production environment. System administrators must configure
resource utilization, performance, and monitoring with respect to Teamcenter’s
enterprise knowledge management thin client solutions and Teamcenter Toolkit.
This section discusses important Web application server considerations when
deploying your Web applications.
• The procedures in this section are essential to ensuring acceptable
performance of Web applications. If you do not perform these procedures,
access to your Web applications will be much slower than necessary,
resulting in potential timeouts and overall inefficiency.
• For more information about improving performance of Teamcenter’s

enterprise knowledge management thin client solutions, see the Network
and Database Configuration Guide manual.
This section discusses the following topics:

• Java heap sizing
• Active sessions
• Server housecleaning
• JSP page recompilation
• Servlet check intervals
Teamcenter’s enterprise knowledge management thin client solutions are special

types of Enterprise Knowledge Management clients. These thin client clients have
distinct resource load demands and require configurations different from those of
the classic client or e!Vista. For example, a configuration parameter on the Web
application server can instruct a Teamcenter’s enterprise knowledge management
solution when to invoke the Java garbage collector as an application call. Like all
Enterprise Knowledge Management clients, a thin client client can also benefit from
local access to data-distribution services such as mserv.
Siemens PLM Software recommends that client hosts accessing Teamcenter’s
enterprise knowledge management thin client solutions use a separate MUX from
other Enterprise Knowledge Management clients. This dedicated MUX can reside on
the same host with the Web application server or on another server.
The following sections describe some of the most important Web application server
tuning and monitoring considerations for production deployment.
The specific configuration mechanism is dependent upon the Web application
server.

Java Heap Sizing

The Java heap configuration needs careful tuning because it can affect memory
swapping and CPU demand. In general, a higher load demand requires a larger
upper limit on the Java heap size. Many application servers have default values that
are much too low to support production level heap demand.
• Setting a value too high may promote memory swapping on servers with too
little RAM.
• A large heap size can also put undo demand on a server with an underpowered
CPU because of Java garbage collection processes.
The Java heap minimum value must be large enough to support the concurrent
Java heap memory demand to server client requests to Teamcenter’s enterprise
knowledge management. A reasonable value to start with is 256 megabytes.
For example, some versions of BEA WebLogic Server use a startup command line
script with the –mx parameter on the java command, and WebSphere uses –Xmx
and other OS specific parameters.
Active Sessions
With most Web application servers, a parameter controls the number of concurrent
active sessions. Setting this parameter value higher commits additional server
resources.
As a general rule, servers with more CPU and memory resources can support more
active sessions. Selecting a good value is difficult and may require iterative steps.
Siemens PLM Software recommends starting with the application server’s default
value.
For example, BEA WebLogic Server uses the CacheSize parameter in the
weblogic.xml file to provide this capability.
Server Housecleaning
How often the application server performs housecleaning checks needs to be
balanced between client activity and CPU utilization.
• Setting a value too low commits resources needed for active clients.
• Setting a value too high ties up unneeded CPU resources performing the
housecleaning.
For example, BEA WebLogic Server uses the InvalidationIntervalSecs parameter

in the weblogic.xml file to provide this capability.
JSP Page Recompilation

Runtime JSP page compilation is a high-CPU activity that also leads to significant
response time delays for the request that triggers it. Typically a JSP page needs this
compilation only once per Web server startup. Most Web servers only perform this
compilation on an as-demand basis (that is, for the first request that needs it.)

Web servers usually support dynamic checking of changed JSP pages. The default
interval is usually much too often for production deployments.
A tuning parameter is used to control how often the application server checks for
changed files that need recompilation. For a production server, these files are not
expected to change often, so a higher value than the default is recommended in
that situation. The mechanism for this configuration can vary dependent upon
the particular J2EE application server.
The performance cost to simply check for recompilation (excluding the compilation)
can be very high. So setting a value of about once a day (86400 seconds) or higher, or
even fully disabling these checks, is recommended for production.
For example, BEA WebLogic Server uses the pageCheckSeconds parameter
in the weblogic.xml file to provide this capability, and WebSphere Server uses
minTimeBetweenStat parameter set from its administrative console.
Servlet Check Interval

Enterprise Knowledge Management can have many of its dynamic JSP page
references implemented as individual servlets, in addition to the controller servlets.
The performance cost for simply checking that servlets are out-of-date can be high.
For a production server this check interval should be set to a value of about once a
day (86400 seconds) or higher.
For example, BEA WebLogic Server uses the system console interface under the Web
Application→Web-application-name→Configuration→Files tab to set the Reload
Period. (This sets the ServletReloadCheckSecs in its internal config.xml file for
the application). WebSphere Server uses the Reload Interval and AutoReload
parameters.

Application
To verify the installation of your Web application, perform the following steps:
1. Make sure that your Web application server is running.
2. Open a Web browser and enter the following URL:

http://host-name:port-number/Web-application-name/controller/home
Replace host-name with the name of your Web application server host.
Replace port-number with the port number used by your Web application server.
Replace Web-application-name with the name you entered for your Web
application.of the Web application that contains the Product Data Management
thin client solution.
For example, if your host-name is AcmeCorp, your Web application server uses
port 7001 and your application name is TC, your Web application launch URL is
http://AcmeCorp:7001/TC/controller/home.
Enterprise Knowledge Management displays the login page.

3. Enter your user name and password, then click OK. If the login succeeds,
Enterprise Knowledge Management displays the user interface and opens your
worklist.
• If you encounter errors during Enterprise Knowledge Management

installation or startup, see appendix B, Troubleshooting, for possible
solutions.
• Some Web application servers require that the URL end with a slash (/).
On other Web application servers, the trailing slash is optional.
• If you customize the thin client and want to use an Extensible Markup
Language (XML) parser in your customization, use an Siemens PLM
Software-supported XML parser.
For information about supported Web application servers and XML
parsers, see the Siemens PLM Software Certification Database:

Part
IV Additional Configuration and

Maintenance
Setting Up Administrative Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Setting Up Translation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Installing Local Area and Work Group Servers . . . . . . . . . . . . . . . . . . . . . . . 13-1
Installing a Special Services Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Adding Server Solutions and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Configuring Legacy Web-Based Products . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Chapter
11 Setting Up Administrative Data
Product Data Management Life Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Change Management and Rapid Change Management Life Cycles . . . . . . . . . 11-2
CMII Life Cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Setting Up Administrative Data for the CMII Solution . . . . . . . . . . . . . . . 11-2
Request for Quote (RFQ) Life Cycle and Templates . . . . . . . . . . . . . . . . . . . . 11-6
Part Request Life Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Vaults and Related Administrative Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Valid Values for Reviewer List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Documents Required for Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Automatic Part Revision and PartDoc Relation . . . . . . . . . . . . . . . . . . . . . . 11-14

Chapter
11 Setting Up Administrative Data
In addition to the general administrative configuration you perform according to

the requirements of your site, you must also create administrative data to support
standard life cycles provided with certain Enterprise Knowledge Management
features. This chapter describes how to create these administrative objects and
settings.
This chapter describes the following tasks:

• Loading the Product Data Management life cycles.
• If you use Change Management or Rapid Change Management, loading

additional life cycle data.
• If you use the CMII solution, creating life cycles and performing the required
administration tasks.
• Loading the request for quote (RFQ) life cycle and templates.
• Loading the part request life cycle.
• Creating vaults, vault locations, and other related data.
• Setting up reviewer list functionality.
• Creating an AdmVal class object.
• Creating an AdmDcPrt class object.
This chapter does not discuss general administrative procedures such as creating
users and assigning them to appropriate groups and roles as required by your site.
For general information about Enterprise Knowledge Management administration,
see the Administrator’s Manual.
This chapter assumes that your site stores work-in-progress in vaults. Alternatively,
your site can store work-in-progress in an object called a team. A team is a group of
users working on a common design task and sharing data. The team is created as an
object in the database to which users are associated through team role assignments.
Access to data is granted to a team, not to a specific team member, and the team
roles determine which members have various types of access to the data.
Your site can use vaults, teams, or both. Siemens PLM Software recommends that
you make this decision before you perform the steps in this chapter. If you use teams,
you may want to modify the steps in this chapter.

Chapter 11 Setting Up Administrative Data
For information about XML reports framework and related administrative items,
refer the Enterprise Knowledge Management Administrator’s Manual for Reports.
Product Data Management Life Cycles

Create life cycles by following the instructions in following file:
MTI_ROOT/samples/edt/README-PartAndDocLC.txt
The user who loads the life cycle data must be a trusted user. Data is loaded directly
into the database using .sh files.
Change Management and Rapid Change Management Life Cycles

If you use Change Management or Rapid Change Management, create life cycles by
following the instructions in following file:
MTI_ROOT/samples/cms/README-ChangeManagmtLC.txt
You load the same life cycles regardless of whether you use Change Management or
Rapid Change Management. In Rapid Change Management, change requests use
a different classification value than in Change Management. Thus, they take a
different path through the life cycles, but they do not use separate life cycles.
The user who loads the life cycle data must be a trusted user. Data is loaded directly
into the database using .sh files.
CMII Life Cycles

If you use the CMII solution, create life cycles by following instructions in the
MTI_ROOT\samples\cm2\README-CM2LifeCycle.txt file.
For more information about CMII life cycles, see the Teamcenter Enterprise
Administrator’s Manual for Change Management.
Setting Up Administrative Data for the CMII Solution

If you use CMII, perform the following steps:
You perform these tasks in addition to the setup you performed in the previous
sections (see Vaults and Related Administrative Data and Administrative
Data for Change Management and Rapid Change Management in chapter
11, Setting Up Administrative Data).
1. Set up the vaults, vault locations, and location selection rules.

a. Create the administrative data as described in the Vaults and Related
Administrative Data section in chapter 11, Setting Up Administrative Data.
b. Create the administrative data as described in the Administrative Data for

Change Management and Rapid Change Management section in chapter
11, Setting Up Administrative Data.

Setting Up Administrative Data
c. Create a vault for the major change items (problem reports, enterprise
change requests, enterprise change notices, and change information) as
follows:
1) Create a vault named ChangeItemVault.
2) Create a vault location named ChangeItemVault Loc.
3) Create a vault location rule as follows:

Condition name: TRUE
Class name: FSItem
Owner: ChangeItemVault
Vault location: ChangeItemVault Loc
Priority: 100
2. Set up users, groups, and role assignments.

The group assignments in this section indicate the minimum group
assignments required for the CMII functionality. Additional group
assignments may be required for your implementation.
a. Requestor
A requestor is a user who creates a change item. Requestors may belong to
other groups as appropriate for their role. Requestors must be in the author
grp group or the creator grp group to create any other change items.
• A requestor may be designated as an author or a consumer.

If designated as an author, the requestor must belong to all of the
following groups:
– author grp or creator grp
– CMS originator grp or PR originator grp
– user grp
If designated as a consumer, the requestor must belong to all of the

following groups:
– PR originator grp
– consumer grp
Do not assign the requestor any role for CMII. Assign the
requestor to other roles as appropriate.
• Dynamic participant: $obj.WbsOriginator
b. Change Specialist I
A Change Specialist I is a user who manages problem reports, enterprise
change requests, and their processing through the Change Review Board
meeting. The Change Specialist I chairs the Change Review Board
meeting.

• Change Specialist I users must belong to all of the following groups:

– CMS admin grp
– CMS originator grp
– user grp
The Change Specialist I user may be assigned to the

DefaultChangeSpec1 role, if required.
• Dynamic participant: $obj.cm2ChgSpec1
c. Change Specialist II
A Change Specialist II is a user who manages enterprise change notices
and their processing, from execution through closure. The Change
Specialist II chairs the Change Implementation Board meeting.
• Change Specialist II users must belong to all of the following groups:

– CMS admin grp
– user grp
The Change Specialist II user may be assigned to the

DefaultChangeSpec2 role as appropriate.
d. Change Specialist III

A Change Specialist III is a user who manages the validation and release
of the items that result from the execution of the change.
• Change Specialist III users must belong to all of the following groups:
– CMS admin grp
– user grp
The Change Specialist III user may be assigned to the

DefaultChangeSpec3 role as appropriate.
e. Document Creator
A document creator is a user who creates the content of a business item and
is responsible for analyzing and executing changes affecting their items.

• The document creator must belong to all of the following groups:

– CMS analyst grp
– user grp
The document creator user may be assigned to the

DefaultChangeAnalyst role as appropriate.
• Dynamic participant: $obj.tx0Author
f. Designated User
A designated user validates the content of a business item after execution
of a change.
• The designated user may be designated as an author or a consumer.

If designated as an author, the designated user must belong to all of
the following groups:
– Review List grp
– user grp
If designated as a consumer, the designated user must belong to all of

– Review List grp

– consumer grp
The designated user may be assigned to the Review List role

as appropriate.
• Dynamic participant: $obj.ReviewList
g. Change Review Board

The people who decide whether a proposed change will be implemented.
The Change Review Board makes a business decision regarding the cost
and priority of the change.
• A Change Review Board member may be designated as an author or

a consumer.
If designated as an author, the board member must belong to all of the
following groups:
– CMS review board grp
– user grp

If designated as a consumer, the board member must belong to all of

– CMS review board grp

– consumer grp
Change Review Board members may be assigned the

DefaultReviewBoard role as appropriate.
• Dynamic Participant = $obj.WbsReviewBoard
h. Change Implementation Board

The Change Implementation Board (CIB) comprises the people who decide
how, when, and by whom a proposed change is to be implemented.
• A Change Implementation Board member may be designated as an

author or a consumer.
If designated as an author, the board member must belong to all of the
following groups:
– CMS implementation board grp
– user grp
If designated as a consumer, the board member must belong to all of

– CMS implementation board grp

– consumer grp
Change Implementation Board members may be assigned the

DefaultImplementationBoard role as appropriate.
• Dynamic participant: $obj.WbsReviewBoard
3. To enable the intended functioning of CMII reports, set up the default

configuration context as follows:
• Life Cycle State List: Released
• Effective Revision: Last Revision With State
Request for Quote (RFQ) Life Cycle and Templates

If you use the request for quote (RFQ) feature, load the RFQ life cycle by following
the instructions in following file:
MTI_ROOT/samples/vms/README-SupplierRFQLC.txt
You must be logged in as the Enterprise Knowledge Management trusted user to

load the RFQ life cycle. The RFQ life cycle installer loads data directly into the
database using .sh files.

Part Request Life Cycle

If you use the part request life cycle, load the part request life cycle by following the
instructions in the following file:
MTI_ROOT/samples/vm/README-PartRequestLC.txt
For more information about the part request life cycle, see the Administrator’s
Manual for Parts and Documents.
Vaults and Related Administrative Data

To create administrative data, perform the following steps:
1. Create the following vaults and vault locations:
Vault Vault Location

WIPVault WIPVault Loc
Released Vault Released Vault Loc
Archive Vault Archive Vault Loc
Template Vault Template Vault Loc
2. Create location selection rules for each vault and vault location combination. For
example, enter the following data in the Create Location Selection Rule dialog
window:
Field Name Data Entered

Condition Name TRUE
Class Name FSItem
Inherit ? Check box (TRUE)
User/Vault/External System WIP Vault
Work/Vault Location/Staging WIP Vault Loc
Area
Host Name Select appropriate host. For example,
Pcoa145
Priority 100
For more information about location selection rules, see the Administrator’s
Manual.
3. Identify the users that require frozen object manipulation access and add
them to either the Admin Power User grp group or Admin Power User
grpAdmin Power User Role role. Query for the ADMIN_POWER_USER
and ADMIN_POWER_USER_WI_PROJECT conditions and modify each as
required. For example:
Condition Name Condition Statement

ADMIN_POWER_USER $eUserName=’User1’ OR
$e.UserName=’User2...;

Condition Name Condition Statement

ADMIN_POWER_USER_ ($o.ProjectName=’EngDocs’ OR
$o.ProjectName=’First Project’ AND
WI_PROJECT $e.UserName=’User3’) OR
($o.ProjectName=’Next Project’ AND
$e.UserName=’User4’);
4. Query for the FrozenManipulationAllowed condition and modify the

condition statement to the following:
$e.UsrName=’super user’
OR ADMIN_POWER_USER(o,e)
OR ADMIN_POWER_USER_WI_PROJECT(o,e)
OR $e.AllowFrozenRel=’createPartDoc’;
The standard lcm_claim_work_allowed condition is set to (1=1), which
requires your users to claim all tasks in their inbox or worklist. To disable this
option, set the condition to 1=0. You must run rulefile after adding or modifying
conditions. For more information about conditions, see the Administrator’s
Manual.

Management
If you use Change Management or Rapid Change Management, perform the
following steps. You perform these tasks in addition to the setup you performed in
the previous section (see Vaults and Related Administrative Data, earlier in this
chapter).
1. Create the vaults and message access rules listed in table 11-1.
Table 11-1. Creating Vaults and Message Access Rules

Vault Allow Users This Access
UnitIncorporationTransferVault All of the following:
• Transfer (Accept Transfer)
• Freeze (Baseline_grp)
• Revise (Revision_grp)
DateIncorporationTransferVault All of the following:
• Transfer (Accept Transfer)
• Freeze (Baseline_grp)
• Revise (Revision_grp)
TaskTransferVault Transfer (Accept Transfer)
StrategyTransferVault Transfer (Accept Transfer)
(required only for Change Management)

You must create the vaults and allow users access to them because after an
effectivity, task, or (in the case of Change Management) strategy is created, it is
automatically transferred to a vault.1
2. Create any message access rules that users require to perform their tasks. For
example:
• The SubmitItemSync message is in the Submit_grp group. Write a rule
restricting access to the SubmitItemSync message if you do not want users
to have all of the submit group access. You can write this rule against the
message or the group.
• Write a message access rule for each vault that a user must access when
performing the submit action. This is required because the submit action
transfers an object to a vault and then performs the submit.
Condition Name: Condition name used for your vault

Class Name: Applicable class name for items in
your vault
Inherit: +
Message/Message Group Name: Submit_grp
Participant: Your group name
• Optionally, write message access rules to allow analysts and change

administrators to update effectivities that they do not own. The standard
product does not allow users to update effectivities that they do not own.
3. Optionally, make classes available for subscription (such as the CmChNtIt

and CmChRqIt classes, for example).
For more information about using the publish/subscribe feature to define
subscribable classes, see the chapter on managing events in the Administrator’s
Manual.
4. Create vault locations and write location selection rules as required for your
system. Vault locations are required to store the data items that users can
attach to objects called change information items.
Valid Values for Reviewer List

Table 11-2 describes the reviewer list administrative data. The third column
shows the administrative tasks that must be performed to use the reviewer list
functionality.
1. The items are automatically transferred to a vault if you use the thin client interface. If, however, you use the classic client or e!Vista
interface, the effectivities, tasks, and strategies are not automatically transferred to a vault.

Table 11-2. Administrative Data for Reviewer List

Class Identifier Task
DynPrtcp $obj.ReviewList Assign this user as a dynamic participant
in life cycle processes.
UsrGrp Review List grp Used with the ValidReviewListGroupC
class constant. Assign users to this group
to define the valid value set for objects
not assigned to a project.
Role Review List role Used with the ValidReviewListRoleC
class constant. Create role assignments
to define the valid value set for objects
assigned to a project. You can use the
wildcard character (*) to assign the role
for all projects.
MsgGrp AssignReviewListMsgs Contains messages used to update
reviewer list. Edit the message access
rules to grant or deny access to this
message group based on your business
requirements.
Event AssignReviewList Optionally, used to set up notifications
when the reviewer list is updated.
TaskTool Assign Review List Optionally, used to launch the reviewer
Tool list dialog from the inbox using the
Smart Open functionality.
The following example illustrates the use of valid values for a reviewer list:
1. Create the following objects:
user1
user2
user3
user4
group1
project p1
2. Drop user4 on group1 to create the Contain Users/Is in Group relationship.
3. Make the following assignments:

a. Assign user1 to the Review List grp.
b. Assign user2 to play the Review List role for all projects by creating a role
assignment using wildcard character (*) as the project.
c. Assign user3 to play the Review List role for project p1 by creating a
role assignment.
d. Assign group1 to play the Review List role for project p1 by creating a
role assignment.

This example results in the following values:

• For an object that is not assigned to a project, user1 is the only valid value for
the reviewer list.
• For an object assigned to project p1, the valid values for reviewers are user2,
user3, and user4.
• If an object is assigned to a project other than p1, the reviewer list contains
user2 as a minimum.
Documents Required for Release

You must create an AdmVal class object in the database for each combination of
part class and type and document class and type that requires document validations.
The Product Data Management life cycles require this object.
All attributes are required. The following example shows the AdmVal class object
and table 11-3 describes the object attributes:
Object AdmVal
{
PartClass
PartType
DocumentClass
DocumentType
RequiredDocIndicator
FrozenDocIndicator
LifeCycleState
SubmitDocIndicator
RulePriority
}
Table 11-3. Documents Required for Release Attributes

Attribute Description
PartClass Part class value or Part.
PartType Specifies part type. Valid values are
EdtAnyType or EdtAny.
DocumentClass Related document class value or Generic
Document.
DocumentType Specifies document type. Valid values are
RequiredDocIndicator Indicator if document must be related (+ or –).
FrozenDocIndicator Indicator if document must be frozen (+ or –).
LifeCycleState Required life cycle state of related document (life
cycle state value or Any).
SubmitDocIndicator Indicator if related document should be
submitted to its life cycle (+ or –).
RulePriority Order of row placement in C structure.

Table 11-3. Documents Required for Release Attributes

Notes:
• Values specified must be Enterprise Knowledge Management internal names,
not translated values. For example, Specification Document is entered as
the SpcDoc class and a Released life cycle state is entered as LcsReleased.
• If the value Any is used in a column, a match for that column is automatic.
• The document obtained from the PartDoc relation for validation checks is the
first document instance that is not superseded.
Each of the standard release process life cycles incorporates a validation message
process. Table 11-4 contains sample AdmVal class object data.
Table 11-4. Sample AdmVal Class Object Data

Col 1 Col. 2 Col. 3 Col. 4 Col. 5 Col. 6 Col. 7 Col. 8 Col. 9
Part Document Doc Frozen Req’d Auto- Rule
Class Type Class Type Req’d Doc Req’d LC State submit Doc? Priority
Assembly T-Custom DesDoc Electrical + + LcsReleased – 1
Component T-Custom Document Standards – – Any + 2
Assembly Any Any Electrical + + LcsAuthorized – 3
• The first row of data causes the following to occur when a T-Custom type
assembly is submitted to the validation life cycle.
The + in column 5 requires the assembly to have at least one related Electrical
type design document. Columns 6 and 7 require the electrical design document
to be frozen (column 6) and at the released (LcsReleased) life cycle state
(column 7).
Column 8 indicates that the document is not autosubmitted to a life cycle. If the
column 8 value is set to +, columns 6 and 7 are not enforced because the result of
submitting the document to its life cycle could freeze the document and change
its life cycle state.
• The second row of data causes the following to occur when a T-Custom type
component is submitted to the validation life cycle.
The – in column 5 indicates that a Standards type general document does not
require a related component. However, if a document of this type is related,
the specifications in columns 6 through 8 are enforced. If there is no related
document, no validation error occurs.
Columns 6 and 7 specify that the Standards general document need not be
frozen (if it is frozen, no validation error occurs) and that the life cycle state
does not matter.
Column 8 indicates that the document is autosubmitted to a life cycle, causing
columns 6 and 7 to be ignored.

• The third row of data is included to show you how the C structure performs.
This row causes the following to occur when an assembly, regardless of type, is
submitted to the validation life cycle.
The + in column 5 requires that at least one Electrical type document of any
class, is related to the assembly.
Additionally, columns 6 and 7 require that an Electrical document of any class
be frozen (column 6) and at the Authorized life cycle state (column 7).
Column 8 indicates that the document is not autosubmitted to a life cycle and
therefore columns 6 and 7 must be enforced.
It is also very important that you know how the logic works when evaluating the C
structure, particularly when using the Any value. The part class and type of the
part object, and the document class and type for the document object, are evaluated
for each row of the structure. If a value is set to Any, the match for that column
is automatic. Once a match is made for all four columns, the remaining columns
are processed as described previously.
Unlike other C structure processing, every row in the structure is evaluated for the
related document. The example demonstrates the need to process each row in the
structure, and the need to ensure the entries in the structure are consistent. A
related Electrical design document meets the requirements of column 5, both in row
1 and row 3 of the structure. Row 1 requires that an Electrical design document
is related, and row 3 requires that at least one Electrical document, regardless of
class, is related to an assembly, regardless of type. Because the document satisfies
requirements in both rows, each row is processed. The life cycle state requirement is
different for rows 1 and 3, and because the last column indicates the document is not
autosubmitted, those life cycle states are enforced. The result is that the validation
always fail, as the Electrical design document is required to have two different
life cycle states (Released and Authorized), which is impossible. Therefore, it is
important, particularly when using the Any value for a column, that you understand
the processing logic.
In this case, the last row must be replaced with additional rows, one for each
document class, so that the Any value for the document class is not used and does
not match for a design document. If there is no match in the C structure, Enterprise
Knowledge Management assumes that there are no validation requirements for
the document and it is not processed.
All documents that satisfy the criteria are evaluated. If any document does not
satisfy the requirements, the message process fails and a single custom notification
message is generated and sent to the submitter that contains all detected errors.
Additionally, there must be at least one AdmVal class object found in the database
or the message process fails with a validation error.
The latest revision of the document is determined by the one that is not marked
superseded. Multiple open revisions are not supported. Additionally, any bulk
loading of multiple revisions of a document must ensure the superseded flag is set
appropriately. There can be no more that 1000 AdmVal objects. The C structure is
limited to 1000 rows and a validation error occurs if more than 1000 are found. This
capability only works in the context of the release validation message process.
All rows in the structure are processed. You must ensure that contradictory
validations are not defined in the C structure. You can use wildcards; however,
failure to prevent contradictory validations results in the inability to release parts.
Siemens PLM Software recommends the following strategy for defining the structure:

1. Define all documents (class/type) that must be related and released for each
class/type of part.
2. Define the release requirements for any documents (class/type) that may be
related for each class/type of part.
3. Define all documents (class/type) that must be related for each class/type of part.
Automatic Part Revision and PartDoc Relation

An AdmDcPrt class object must be created in the database for each combination of
document class/type and part class/type for which this revise functionality is desired.
The Product Data Management life cycles require this object.
The object and required attributes are as follows:
Object AdmDcPrt
{
DocumentClass
DocumentType
PartClass
PartType
RevisedFirstIndicator
RelateFrozen
RulePriority
}
Table 11-5 contains the attribute names and the valid values for each.
Table 11-5. Release Required Document Attributes

DocumentClass Related document class value or Any.
DocumentType Specifies related document type. Valid values are
PartClass Part class value or Any.
PartType Specifies part type attribute value. Valid values are
RevisedFirstIndicator Indicator if related part must be revised first (+ or –).
RelateFrozen Indicator if revised document must be related to a
frozen part (+ or –).
RulePriority Order of AdmDcPrt objects returned for processing.
Notes:
• Values specified must be Enterprise Knowledge Management internal names,
not translated values. For example, Specification Document is entered as
the SpcDoc class and a Released life cycle state is entered as LcsReleased.
• If the value Any is used for an attribute, a match for all values is automatic.
• The part, obtained from the PartDoc relation for processing, is the first part
instance that is not superseded.

Table 11-6 describes how the revision automation code works using sample data.
Table 11-6. Sample Data for Automatic Revision

Column 1 Column 2 Column 3 Column 4 Column 5 Column 6 Column 7
Part Document Revise Relate Rule
Class Type Class Type First Indicator Frozen Priority
Assembly T-Custom DesDoc Electrical + + 1
Component T-Custom Document Standards – + 2
Assembly Any Any Electrical – – 3
When a document is revised, the AdmDcPrt class is queried for objects where the
DocumentClass and DocumentType attributes match the class and type of the
document being revised, or where the attribute value equals Any.
• If no objects are returned, a standard Enterprise Knowledge Management
revision occurs.
• If objects are returned, they are sorted in ascending order according to the
RulePriority value, and processed in that order for each nonsuperseded part
which is related, through the PartDoc relation, to the document being revised.
Processing of the AdmDcPrt objects continue, until the part class and part type
attributes of the AdmDcPrt object match the class and type of the related part
(or if an attribute value is set to Any).
• If no match is found, that related part is not processed, and the next related
part is processed.
• If a match is found, no further AdmDcPrt objects are processed; instead, that

object alone is used to determine the revise behavior of the document and related
part.
If the RevisedFirstIndicator attribute on that AdmDcPrt object is set to +, the

related part (if frozen) is revised before the document and checked into the vault
specified by the WIPVaultC class constant. The only exception to this is if the part
has attached data items. In this case, the part is not revised, as on unmanaged
hosts, and the checkin of the part and its associated data items might fail.
• If the RevisedFirstIndicator attribute is set to –, the part is not revised first.
• If the RelateFrozen attribute is set to +, a PartDoc relation is created between

the revised document and its related frozen part.
– If the nonsuperseded part is frozen, the relation is created directly to this
part.
– If not frozen, the relation is created to the frozen predecessor of the part.
• If the RelateFrozen attribute is set to –, Enterprise Knowledge Management

does not create the PartDoc relation to the frozen part.
For design documents, the order in which objects are processed is based on the
RulePriority attribute. When an electrical design document is revised, a related

T-Custom assembly is revised first (object with RulePriority equal to 1). If any
Electrical type document class object is revised, any related assembly, regardless
of the type, is not revised first (object with RulePriority equal to 3). Therefore,
Enterprise Knowledge Management revises the related T-Custom assembly for
electrical design documents, and does not revise assemblies for any other classes
of Electrical type documents.
If you switch the RulePriority values for object 1 and 3, no assemblies are revised
first for any class of documents, provided the documents are Electrical. Not even
the design document causes a revision of the T-Custom assembly. No revision
occurs because a match for the design document occurs with the object containing
the new RulePriority value of 1 first, due to the Any value for document class,
and no further processing takes place. It is important, particularly when using the
Any value, that you understand and set the RulePriority attribute according
to the processing logic.
The latest revision of the document is determined by the one that is not marked
superseded. Multiple open revisions are not supported. Additionally, any bulk
loading of multiple revisions of a document must ensure the superseded flag is set
appropriately. The RulePriority attribute makes a difference in the processing
order of the AdmDcPrt objects. You can use wildcards; however, you must take care
to ensure the revision occurs properly.

Chapter
12 Setting Up Translation
Environment
Configuring Translation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Setting Up Translation Configuration Control Objects . . . . . . . . . . . . . . . 12-2
Setting Up CATIA Control Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Setting Up Pro/ENGINEER Control Objects . . . . . . . . . . . . . . . . . . . 12-6
Setting Up NX and Rich Client Control Objects . . . . . . . . . . . . . . . . . 12-7
Setting Up I-deas Enterprise and IMI Control Objects . . . . . . . . . . . . 12-8
Creating TCTS_HOME Variable and visfiles Directory . . . . . . . . . . . . . . . 12-8
Editing the Translation Service Configuration File . . . . . . . . . . . . . . . . . . 12-9
Generating the Trusted User Password . . . . . . . . . . . . . . . . . . . . . . 12-10
Editing the Enterprise Knowledge Management Configuration File . . . . . 12-10
Enabling C9T Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Editing Configuration Variables and Mappings . . . . . . . . . . . . . . . . 12-10
Enabling BOM Preview for Translators . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Enabling the Local File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
Setting Up the Translation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14

Chapter
12 Setting Up Translation
Environment
This chapter describes how to configure the translation service to set up translation
control objects for Enterprise Knowledge Management.
Translation Management is the integration of the translation solution toolkit

services and Teamcenter. Translation Management enables My Teamcenter
users to translate data files that are managed by Teamcenter to 3D or 2D
file formats. For more information about Translation Management, see the
Teamcenter Getting Started with Translation Management guide.
Configuring Translation Service

The following sections describe the prerequisites for the translation service and how
to set up the translation control objects.
Prerequisites
Prerequisites for translation service are as follows:
• Install the Enterprise Knowledge Management CAD integration and CAD
translation environment modules required to support the CAD translations
needed for your site. Enterprise Knowledge Management supports CAD
integrations for the following CAD software:
– NX
– I-deas®
– Pro/ENGINEER
– CATIA
Install server solutions for CAD integration and translation environment

according to the documentation provided with each integration.
Enterprise Knowledge Management CAD translation uses the Common
Translation Environment module (C9T) included in the Enterprise
Knowledge Management Foundation server solution.

Chapter 12 Setting Up Translation Environment
• Ensure that the translation server, scheduler, and modules are running.
• Install, set up the licenses, and configure all the required translators.
• Enable all the required translators for the translation server.
• Ensure that all prerequisite software is up and running or can be launched as

needed.
Siemens PLM Software recommends that you use only the JPG option
instead of the default JPG_AND_PDF option in the translator.xml file
for the PreviewService translator.
For more information about implementing the PreviewService translator,
see the Translation Solution Toolkit Translators Reference Guide.
Setting Up Translation Configuration Control Objects

This section describes how to set up translation configuration control objects.
These objects control how Enterprise Knowledge Management submits tasks to
the translation service.
To set up translation configuration control objects:
1. Log in to Enterprise Knowledge Management classic client.
Ensure that you are a member of the TessTrans admin grp group. You must
be a member of this group to configure translation configuration control objects.
2. Query for translation configuration control objects that were installed by the
C9T modules. These objects control how translation occurs. Pull down the Query
menu and choose the following options:
Administrative Classes→Translation Services Admin Items→
Translation Configuration Control
Click OK.
3. Select a translation configuration control object for your CAD application, pull
down the Info menu and choose the Update option.
4. Revise the fields in table 12-1 that contain the change_on_install value, and
enter values for other fields as needed.
For information about configuration control object fields that are unique to:
• CATIA translations, see Setting Up CATIA Control Objects.
• Pro/ENGINEER part and drawing translations, see Setting Up

Pro/ENGINEER Control Objects.
• NX and rich client translations, see Setting Up NX and Rich Client Control
Objects.
• I-deas Enterprise and IMI translations, see Setting Up I-deas Enterprise and
IMI Control Objects.

Setting Up Translation Environment
Table 12-1. Translation Configuration Control Object Fields

Field Value
Name The default value is C9CfgCt. This is the
name of the translation configuration control
object.
Staging Host Name Enter the name of the translation host system
where the translation service is running.
Staging Directory Path Enter the staging directory for translation.
This must be a valid Enterprise Knowledge
Management work location.
Generated Visualization File Enter the name of the translation host system
Staging Host where the translation service is running.
Generated Visualization File Enter the staging directory for the generated
Staging Directory visualization files. This must be a valid
Enterprise Knowledge Management work
location.
This value must match the DownloadDir
value in the TranslationService.config file.
For more information, see Installing and
Configuring the Translation Service chapter in
the Translation Solution Toolkit Installation
Guide.
Translation Service Name This value is provided by the translation
configuration control object and corresponds
to a translator in the translator.xml file on
the translation server.
Translation Script Name Enter the name of the translation service
script file: runTranslationService.bat or
runTranslationService.sh.
Translation Script Path Enter the path to the translation service script
file.
Translation Task Vault Enter the Enterprise Knowledge Management
vault to store the translation task objects.
Ensure this vault has a valid vault location
to store task log files.
Translation Task VaultLoc Enter the Enterprise Knowledge Management
task vault location to store the task logs.
Visualization File Vault Enter the Enterprise Knowledge Management
vault where the visualization files are to be
checked in.

Table 12-1. Translation Configuration Control Object Fields

Field Value
Visualization File VaultLoc1 Enter the Enterprise Knowledge Management
vault location where the visualization files are
to be checked in.
Condition Attribute Value Leave this field blank for all translators except
UG drawing files.
For UG drawing files, set this value to + (plus).
Service Provider Enter Siemens PLM Software. Siemens PLM
Software is the default value.
Applies to the Class This value is provided by the translation
configuration control object and corresponds
to the CAD class that gets translated into
visualization files. Valid values include
D5UgFls (NX), a2aItm (I-deas), ProData
(Pro/ENGINEER), and others.
Translation Condition Leave this field blank for all translators except
Attribute UG drawing files.
For UG drawing files, set this value to
D5Drawing Data.
BI-Preview Relation The default value is BitToVis.
Preview-Source Relation Enter the C9SrcPvw value if you want to
create the preview relation (optional).
Preview-Visualization Leave blank
Relation
Visualization-Source Relation The default value is ItmToVis.
BI-Visualization Relation The default value is BitToVis.
Translation Target The default value is ItmToVisSourceOfVis.
Relationship
Tesselation on Checkin? Enter True if you want to create translation
files at checkin.
Is Translatable? True is the default value. It indicates that the
class can be translated and that the control
object is active.
The Staging Directory Path and Generated Visualization File Staging

Directory can be the same or different; however, these directories must
be created by the same user who is a member of the TessTrans admin
grp group.
1. If you do not specify the Visualization File Vault and Visualization File VaultLoc, Enterprise Knowledge Management copies the visualization
files to the location of the respective CAD file.

The translation control object appends temporary directories to the staging

directory after the translation server completes a translation. For example,
if you have specified D:\FileSys\VisStg as the staging directory, then the
control object adds the D:\FileSys\VisStg\TS\aaaaa-10000 directory after the
translation server completes the translation.
Do not delete or modify the directory appended by the translation control
object.
5. Click OK to save the updated translation configuration control object.
Setting Up CATIA Control Objects
Table 12-2 describes fields that are unique to CATIA translations.
Table 12-2. CATIA Translation Configuration Control Object Fields

CATIA V4 CATIA V4
(assembly-based (file-based
Field translations) translations) CATIA V5
Translation Service name catiav4tojt ugsplm_catiatojtv5
Service Name for AsciiToJt
translator2
Applies to Class Assembly x0CTMod x0CatPrt
x0CatPrd
BI-Vis Relation BitToVis BitToVis BitToVis
BI-Preview BitToVis BitToVis BitToVis
Relation
Preview Source Not applicable C9SrcPvw C9SrcPvw
Relation
Preview Vis C9VisPvw C9VisPvw C9VisPvw
Relation3
Vis-Src Relation Not applicable ItmToVis ItmToVis
Translation Target BitToVisSource ItmToVisSource ItmToVisSource
Relationship OfVis OfVis OfVis
2. The translation server standard installation does not include this translator. You must install, configure, and include the service
name for this translator on the translation server before using it.
3. Optional field

Setting Up Pro/ENGINEER Control Objects

Table 12-3 describes fields that are unique to Pro/ENGINEER part and drawing
translations.
Table 12-3. Pro/ENGINEER Part and Drawing Translation Configuration

Control Object Fields
Field Pro/ENGINEER Pro/ENGINEER Drawing
Part
Translation Service proetojt proetodxf
Name
Applies to Class ProData ProDrw
BI-Vis Relation BitToVis BitToVis
BI-Preview Relation ProToVis C9BitPvw
Preview Source Relation C9ProPvw C9ProPvw
Preview Vis Relation4 C9VisPvw C9VisPvw
Vis-Src Relation ProToVis ItmToVis
Translation Target ProToVisSource ItmToVisSource
Relationship OfVis OfVis
4. Optional field

Setting Up NX and Rich Client Control Objects

Table 12-4 describes fields that are unique to NX and rich client translations.
PreviewService is used for translating UG drawings and PreviewService
requires CGM data saved in part files. Therefore, in NX4 and NX5, be sure
to check the Save CGM Data in Part checkbox in the Miscellaneous pane
(File→Utilities→Customer Defaults→Drafting→General→Miscellaneous).
Table 12-4. NX and Rich Client Translation Configuration Control Object

Fields
Field NX (D5U) rich client
Translation Service Name nxtopv (for parts and For information about
assemblies) mappings used by CAD and
drawing translators, see
previewservice (for table 12-7.
drawings)
Applies to Class D5UgFls (for parts) GnCAFile
D5pNonMs (for
drawings)
BI-Vis Relation BitToVis BitToVis
BI-Preview Relation BitToVis BitToVis
Preview Source Relation C9SrcPvw C9SrcPvw
Preview Vis Relation5 C9VisPvw C9VisPvw
Vis-Src Relation ItmToVis ItmToVis
Translation Target ItmToVisSource ItmToVisSource
Relationship OfVis OfVis
5. Optional field

Setting Up I-deas Enterprise and IMI Control Objects
Table 12-5 shows fields that are unique to I-deas Enterprise and IMI translations.
Table 12-5. I-deas Enterprise and IMI Translation Configuration Control

Object Fields
I-deas I-deas
Enterprise (IDS Enterprise (CDS
Field mode) mode) IMI (A2Z)
Translation ideastojt For information ideastojt
Service Name about mappings
used by CAD
and drawing
translators, see
table 12-7.
Applies to Class IDSFile GnCAFile a2aItm
BI-Vis Relation BitToVis BitToVis BitToVis
BI-Preview BitToVis BitToVis BitToVis
Relation
Preview Source C9SrcPvw C9SrcPvw C9SrcPvw
Relation
Preview Vis C9VisPvw C9VisPvw C9VisPvw
Relation6
Vis-Src Relation ItmToVis ItmToVis ItmToVis
Translation Target ItmToVisSource ItmToVisSource ItmToVisSource
Relationship OfVis OfVis OfVis
Creating TCTS_HOME Variable and visfiles Directory

To set the TCTS_HOME environment variable and create the visualization file
download directory:
1. Create a TCTS_HOME environment variable and set it to the
TranslationService directory.
The translation service fails if the TCTS_HOME environment variable is

missing or incorrect.
2. Create a visfiles directory on the machine where you have installed the
translation service to store the visualization files downloaded from the
translation server. For example, D:\visfiles.
This directory must be defined as a work location in Enterprise Knowledge

Management.
6. Optional field

Editing the Translation Service Configuration File

To edit the TranslationService.config file:
Back up the TranslationService.config file before starting the translation
service for the first time. The translation service overwrites this file and
removes all the comments and unused variables.
1. Open the TranslationService.config file from the TranslationService/conf

directory.
2. Edit the SrcFileExtensions attribute to define the source file extensions for
your translation process.
For example:
SrcFileExtensions=.prt,.asm,.pkg,.mdf,.par,.SLDPRT,.SLDASM,.ipt,.stp,
.iam,.SLDDRW,.idw,.dft,.CATPart,.CATProduct
If you have a CATIA product structure that contains products and

parts, add the .CATPart and .CATProduct file extensions to the
SrcFileExtensions attribute as shown in the example above.
3. Edit the DownloadDir property to specify the location where the visualization
files are placed before being transferred to the PDM system. For example:
DownloadDir=d:/work/visfiles
For Windows, use the forward slash (/) path separator to specify the download
directory.
The DownloadDir value must match the Generated Visualization
File Staging Directory field value in the conguration control objects.
For more information about translation configuration control object fields,
see table 12-1.
4. Change the User value to a Teamcenter Enterprise user designated for

translation. This user must be a member of the TessTrans admin grp group.
If the client requires a password to log into Teamcenter, you must generate
an encrypted password. For more information, see Generating the Trusted
User Password later in this chapter.
5. Optionally, edit the BomPreviewMapping property to specify whether the

StandardMapper (BasicPostProcessor) must use bill of materials (BOM)-based
preview mapping.
If a translator outputs a BOM file, the client service can use this file to provide
more robust data mapping to the PDM server. To enable BOM-based preview
mapping, set:
BomPreviewMapping=1
In addition, you must configure the BasicPostProcessor mapper class in

the PostProcessor.xml file for BOM-based preview mapping. For details,
see Enabling BOM Preview for Translators later in this chapter.

Generating the Trusted User Password

If the client requires a password to log into Enterprise Knowledge Management, you
must generate an encrypted password for the TranslationService.config file.
To generate the Enterprise Knowledge Management trusted user password:
1. Using the command prompt, change to TranslationService/bin directory and
enter the following command as appropriate for your operating system:
• Windows:
encryptPass.bat password
• UNIX:
encryptPass.sh password
Where, password is the Enterprise Knowledge Management trusted user

password for the client service.
The encrypted password is stored in the TranslationService.pwf file in the
TranslationService\cache directory.
When you run this script, it removes any comments and unused variables
from the TranslationService.config file. You must back up this file
before you run the script. After you run the script, see the backup copy to
view the fully commented file, including optional properties.
2. Save the TranslationService.config file.
Editing the Enterprise Knowledge Management Configuration File

The sections that follow describe how to enable C9T logging and edit configuration
variables and translator mappings.
Enabling C9T Logging

To enable C9T logging:
1. Open the config.cfg file from the MTI_ROOT\config directory where you have
installed Enterprise Knowledge Management.
2. To enable translation logging, set the C9T_LOG property to true.

When set to true, a CADfilename_VersionNumber.txt file is created in the
staging location to log the translation information.
Where CAD filename is the filename of the CAD part which gets translated and
version number is its version number.
For more information about staging location, see Setting Up Translation
Configuration Control Objects.
If C9T encounters any problems in creating this log file, it prints the information
in the dispatcher trace.
Editing Configuration Variables and Mappings

To edit configuration variables and translator mappings:

1. Open the config.cfg file from the MTI_ROOT\config directory where you have
installed Enterprise Knowledge Management.
2. Optionally, edit configuration variables as described in table 12-6.
Table 12-6. Common Translation Environment Configuration

Variables
C9SFILE Specifies the CAD file extensions to be copied for the
EXTENSIONS translations to the staging location.
Enter a comma separated string of CAD file extension
names. For example, set C9SFILEEXTENSIONS to
step,stp,prt,asm,par,model,
mdf,drw,CATPart,CATProduct.
C9CleanStg Specifies whether the part files must be deleted from
the staging location. The part files are deleted from
the staging location only if the status of the translation
task changes to TASK_TRANSLATION_ERROR.
C9CheckJPEG Set the C9CheckJPEG attribute to TRUE to have
JPEG files, even though JT files are available,
attached to a part file.
If you want to attach a .JPEG file, set this to TRUE.
When only JT files and not JPEG files are
attached to a part file and if this attribute is
set to FALSE, you must delete the JT files and
submit the part for translation by choosing the
Prepare Visualization Files option to attach
both the JT and JPEG files.
TRUE or FALSE values are case sensitive.
c9SkipTaskDelete Specifies whether translation tasks should be deleted.
If you do not want the translation tasks to be deleted,
set this to TRUE.
Siemens PLM Software recommends that you
set this attribute to TRUE for CATIA V4
translations.
3. Optionally, edit mappings used by CAD and drawing translators as described

in table 12-7.
Table 12-7. C9S Translator and C9S Drawing Translator Mappings

C9SDRAWINGTRANSLATOR
Field C9STRANSLATORMAP MAP
Ug nxtopv previewservice

Table 12-7. C9S Translator and C9S Drawing Translator Mappings

C9SDRAWINGTRANSLATOR
Field C9STRANSLATORMAP MAP
Ideas ideastojt ideastojt
ProE proetojt proetodxf
Catia catiatojt catiatojt

SEdge solidedgetojt solidedgetodxf
SWork solidworkstojt swtodxf
CatiaV4 catiatojt catiatojt
CatiaV5 ugsplm_catiatojtv5 ugsplm_catiatojtv5
Inv invtojt invtodxf
When you create a test/customization environment, you must

copy the C9SFILEEXTENSIONS, C9STRANSLATORMAP, and
C9SDRAWINGTRANSLATORMAP configuration variables to the
config.cfg file in the test/customization environment.
Enabling BOM Preview for Translators

Some translators generate BOM files. A BOM file contains a map of the input and
the resultant output file for a particular translation. If a translator generates a
BOM file, the translation service can use it to provide more robust data mapping
to the PDM server.
This section provides an example of how to enable BOM preview for the IdeasToJt
translator.
To enable BOM preview file mapping for the IdeasToJt translator:
1. Open the TranslationService.config file from the
TranslationServer\TranslationService\conf directory.
a. Edit the BomPreviewMapping property to set it to 1. By default, it is
set to 0.
For more information, see section on Editing the Translation Service
Configuration File earlier in this chapter.
b. Save the TranslationService.config file.
2. If you use the C9T module, open the PostProcessor.xml file from the
TranslationService/conf directory using a text editor, and perform the
following procedures:
a. Uncomment the following c9t dbhelper name:

to
<dbhelper name="com.edsplm.tc.ent.c9transESHelper.c9t.ESUtilHelper"/>

b. Comment out the following test dbhelper name:

<dbhelper name="com.teamcenter.translationservice.
test.TestDBHelperImpl"/>
to

c. To configure the correct BOM file name created by PreviewService, edit

the default bomfile name property to specify the BOM file name from the
previewservice.bat file in the Module\Translators\previewservice
directory.
Example:
<Defaultbomfiles>
<bomfile name="visFile.bom" type="visfile"/>
<bomfile name="previewfile.bom" type="previewfile"/>
<bomfile name="drawingfile.bom" type="drawingfile"/>
</Defaultbomfiles>
If the BOM file name in the previewservice.bat file is jt2jpeg.bom,

change to:
<Defaultbomfiles>
<bomfile name="visFile.bom" type="visfile"/>
<bomfile name="jt2jpeg.bom" type="previewfile"/>
<bomfile name="drawingfile.bom" type="drawingfile"/>
</Defaultbomfiles>
d. Save the PostProcessor.xml file.
Enabling the Local File Server

The local file server is an alternative to the file server for translation solutions
using the client service. It bypasses the transfer of translation source files from the
client service staging directory to the module staging location. This may increase
throughput in some cases.
To use the local file server, the module and the client service must be on the
same physical machine. It is possible to configure the local file server to use
a shared directory with read/write access; however, this can cause excessive
network traffic and slow down the translations.
In addition, the staging directory must be a defined work location.
Typically, the translation module stages files in a temporary results directory,

which the module automatically deletes when the translation is complete. When
you implement the local file server, the translation module stages the files in the
visfiles directory that you created for the client service.
You must first disable the standard file server before you can enable the local file
server.
To disable the standard file server and enable the local file server.
1. Open the transmodule.properties file from the Module/conf directory.

2. Comment the FileServer.URL property by prefixing a # sign before the property.

Example:
#FileServer.URL=http://localhost:8080/
TranslationServer/FileServer
3. Ensure that the FileServer.Local property is uncommented. By default, it

is uncommented.
4. Save the transmodule.properties properties file.
Setting Up the Translation Service

Applications can use a translation service to request translation jobs from the
translation server.
This section provides simplified instructions to help you get the translation service
up and running for Enterprise Knowledge Management.
To set up the translation service for Enterprise Knowledge Management:
1. Ensure that the translation server is installed and working properly.
For information about installing and configuring the translation service, see the
Teamcenter Translation Solution Toolkit Installation Guide.
2. Ensure that the TranslationService directory exists on your system.
3. Set the TCTS_HOME environment variable on your system to point to the

TranslationService directory.
4. Extract the INSTALL_TCTS.EXE or INSTALL_TCTS.TZ file (in the

Enterprise Knowledge Management software distribution image) to the
TranslationServer\TranslationService\lib directory. The file you have
extracted contains the following files:
sdrc_evista.jar
teamcenter_es.jar
TranslationServiceES.jar
5. Add the following event handler in the TranslationService.config file in the

TranslationServer\TranslationService\conf directory. The event handler
looks for translation server events before communicating with the C9T module.
EventHandler=com.edsplm.tc.ent.c9transESHelper.
c9t.c9ESUtilHelper
6. Log in to the Enterprise Knowledge Management classic client and add

translation administrators and users to the proper user groups:
• TessTrans admin grp: Grants administrative rights to set up translation
configuration control objects and manage deletion of translation tasks.
• TessTrans user grp: Grants user rights to submit CAD files for translation.
7. Start the translation service:

a. Change to the TranslationServer\TranslationService\bin directory.
b. Run the runTranslationService.bin or runTranslationService.sh file

with the –start command, as follows:
runTranslationService –start
A new prompt window is displayed.
c. Check the TranslationService.txt file from the

TranslationServer\TranslationService\logs\TSTK\process directory
to check for any errors. Do not continue unless the translation service
loads successfully.
To use the Log Manager, you must have the Digital Dashboard
installed. For more information about the Log Manager and Digital
dashboard, see the Business Modeler IDE Guide.

Chapter
13 Installing Local Area and

Work Group Servers
Preparing the Server Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Adding the Host and User to the Configuration . . . . . . . . . . . . . . . . . . . . . . . 13-2
Configuring the License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Running the Installation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Completing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Executing the pushall Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6

Chapter
13 Installing Local Area and

Work Group Servers
This chapter describes how to install Enterprise Knowledge Management on local

area server and work group server hosts.

• Preparing the local area or work group server host.
• Configuring the license manager.
• Running the installation script.
• Completing the installation.
• Executing the pushall command.
Preparing the Server Host

Before you install a local area or work group server, you must prepare the server
host by performing the following procedures:
1. Create the Enterprise Knowledge Management trusted user.
Create the Enterprise Knowledge Management trusted user account on the
local area or work group server host. Use the same procedure you used on
the corporate server host in chapter 3, Creating the Enterprise Knowledge
Management Trusted User.
2. Install the database manager.

You or your database administrator must install database software on the
local area or workgroup server host. Use the same procedures and information
provided in chapter 4, Installing Oracle.1
1. This information is also contained in an appendix in the Network and Database Configuration Guide that describes how to install
and configure Oracle for Enterprise Knowledge Management.

Chapter 13 Installing Local Area and Work Group Servers
Adding the Host and User to the Configuration

Add the local area or workgroup server to your configuration by performing the
following steps on the corporate server:
1. Using the Configuration Editor, add the local area or workgroup server host to
the Enterprise Knowledge Management network.2 This creates a configuration
file (config.cfg) for the host. For more information about adding hosts to a
configuration, see the Network and Database Configuration Guide.
2. From a command prompt, reload the Enterprise Knowledge Management

configuration on the corporate host by entering the following command:
muxstop -r
3. Using Enterprise Knowledge Management, create a host object for the client
host in Object Management Framework (OMF). Enter the host name exactly as
it was entered in the Configuration Editor, including capitalization.
4. Create a user object in OMF for the Enterprise Knowledge Management trusted
user on the client host. The user name must exactly match the name of the
trusted user you created on the host.
Alternatively, you can choose an existing user on the host as the trusted user
for that host.
5. Validate the trusted user on the client host you created or chose in step 3-3.
6. From a command prompt, update the rules cache to initiate the client host and
user by entering the following command:
rulefile -r
7. Push the updated rules cache to all hosts that run mloader by entering the
following command:
pushf -rf hosts_mloader
8. Broadcast the rules change to all hosts in the network by entering the following
command:
rulefile -R

Copy the INSTALL_BASE.TZ file to your local area or workgroup server host using
the method you used on the corporate server host. (See Copying Installation Files in
chapter 5, Preparing the Enterprise Knowledge Management Environment.)
If you have installed solutions on the corporate server, be sure to copy the
installation files from the solution distribution image to your local area or
workgroup server host.
2. The Configuration Editor runs only on the corporate server host.

Installing Local Area and Work Group Servers
Configuring the License Manager

Configure access to the license manager by either of the following methods:
• Using the Corporate License File
Set the LM_LICENSE_FILE environment variable in your startup file (.login,
.profile, or .cshrc) to the following value:3
port@host-name
Replace port with the port used by the license manager. By default, this is 8575.
If your license manager uses a different port, use the value you recorded on the
Installation Worksheet in chapter 1, Overview.4
Replace host-name with the name of the host on which the license manager runs.
Typically, this is the corporate server host.5
For example, if the license manager uses port 8575 on a corporate host
named AcmeCorp, the value of LM_LICENSE_FILE should be set to
8575@AcmeCorp.
• Using a Local Copy of the Corporate License File

This method reduces traffic between the local area server and the host running
the license manager daemon.
1. Copy the corporate licenses.mti file6 to the MTI_ROOT/config directory on

the local area or work group server.
2. Set the LM_LICENSE_FILE environment variable in your startup file

(.login, .profile, or .cshrc) to MTI_ROOT/config.
After you configure the license manager, proceed to Running the Installation Script,
next in this chapter.
3. This step is not required on a workstation (client) host.

4. For more information about the FLEXnet Manager port number, see Installing Enterprise Knowledge Management Licenses in
chapter 5, Preparing the Enterprise Knowledge Management Environment.
5. host-name may be a host other than the Enterprise Knowledge Management corporate server if a FLEXnet Manager license manager
daemon was installed by another application before you installed Enterprise Knowledge Management. For more information, see
Installing Enterprise Knowledge Management Licenses in chapter 6, Installing Enterprise Knowledge Management.
6. In a default installation, the corporate license file is in the MTI_ROOT/config directory on the corporate server host.

Running the Installation Script

• Make sure no Enterprise Knowledge Management MUX or dispatcher
services are running on the host before you run the installation script.
• Make sure that the MTI_ROOT environment variable is not set in your
environment. If this environment variable is defined, the installation
script generates a warning.7
• When the installation script prompts you for paths, enter only paths
beginning with a drive letter or a single backslash (\). Do not enter paths
that begin with two backslash characters.
Running the installation script:

1. Copy configuration files from the corporate server to each local area server and
each work group server. (The Configuration Editor generates these files when
you add a host to your configuration.) Configuration files are in the following
directories on the corporate server:
MTI_ROOT/install/hosts/common
MTI_ROOT/install/hosts/target-host-name
Replace target-host-name with the name of the local area or work group server
host.
Copy all files in these directories to the MTI_ROOT/install directory on the
local area or work group server.
2. Change to the MTI_ROOT/install directory.
3. Start the Enterprise Knowledge Management installation script:

esvm insmenu
4. The installation program displays the following prompt:

Enter the disk location of the install images. [path]:
Enter the path to the Enterprise Knowledge Management software distribution

image.
At each installation prompt, you can press enter to accept the default
value shown in square brackets ( [ ] ) or else enter a new value.
5. Indicate the Enterprise Knowledge Management components you want to install:

Will you be installing on this host:
Prompt Response
The support files Answer N.8
[Y/N] [N] ?
7. The MTI_ROOT environment variable is automatically defined in the pdmsetup file.

8. Support files are software libraries needed to customize Enterprise Knowledge Management server components.

Installing Local Area and Work Group Servers
Prompt Response
e!Vista? Answer N unless the client host
[Y/N] [Y] ?
is a Web server host that services
e!Vista clients. If you answer Y, the
installation program prompts you for
a location in which to install e!Vista
files.
The online documentation locally If you want to install the online
[Y/N] [N] ?
manuals collection for all Enterprise
Knowledge Management products,
enter Y.
Otherwise, answer N and then skip to
step 7-7.
You can add the support files, e!Vista, or online manuals after your server
installation is complete by entering the following command from the
install directory beneath MTI_ROOT:
esvm script-name
Replace script-name with insSupport, insEvista, or insDocs.
6. If you choose to install online manuals locally, the installation script displays
the following prompt:
Enter the location for the online documentation [default-path]:
Enter the path to the directory you want to contain the online manuals, or press
enter to accept the default-path shown.
7. The installation script prompts you to confirm your responses:

Are your answers correct [Y/N] [Y]?
If you want to change your responses, answer N to reenter all your responses.
Otherwise, press enter to begin installation.
8. During installation, the MetaWeb postinstallation script prompts you for

destination directories for MetaWeb files and templates. Enter the directories
you want to use or press enter to accept the default paths shown. If you do not
use MetaWeb, accept the default values.
Depending on the server solutions installed on your corporate server, the
installation script may display additional installation prompts.
When installation is complete, the installation script displays a notice stating that
installation was successful, followed by an instruction to run the root.sh . This
procedure is described in Completing the Installation, next in this chapter.
Completing the Installation

Complete the installation of the local area or work group server as you completed
installation of the corporate server, performing the steps described in Completing the

Enterprise Knowledge Management Installation in chapter 6, Installing Enterprise

Knowledge Management. These steps include the following:
1. Running the Enterprise Knowledge Management setup file (pdmsetup).
2. Starting Enterprise Knowledge Management network services (MUX and

dispatcher).
3. Launching the classic client.
Executing the pushall Command

If you have one or more local area servers in your configuration, propagate your
Enterprise Knowledge Management configuration to the local area servers using
the pushall command.
The Configuration Editor generates the pushall file when you click Generate
Files in the Configuration Editor after adding hosts to your configuration. The
pushall file contains individual pushf commands that push the MODeL file,
the rules cache, dialog window definitions, and NLS text definitions to all
remote hosts where mloader is run.
Execute the pushall command:
1. Ensure that the Enterprise Knowledge Management MUX and dispatcher

services are running on all servers in your network.
2. Log in to the corporate server as the Enterprise Knowledge Management trusted

user.
3. Source the MTI_ROOT/config/pdmsetup file.

pushall
5. On each host on which mloader is run, enter the following commands to reload
the Enterprise Knowledge Management configuration:
muxstop -r
dspstop -ra
For more information about the pushall command, see the Administrator’s Manual.

Chapter
14 Installing a Special Services Host
Installing Vis Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Completing Special Services Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Setting Configuration Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Mapping Special Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Chapter
14 Installing a Special Services Host
This chapter describes how to configure Enterprise Knowledge Management print

and translation services to service Enterprise Knowledge Management clients. It
also describes how to install and configure third-party applications to be distributed
through a special services host.

• Configuring special services.
• Completing special services configuration.
Installing Vis Products

Enterprise Knowledge Management print and translation services require Vis
products to perform certain actions. To install Vis products required on the special
services host, perform the following steps:
Vis products are not supported on Linux platforms.
You must install Ghostscript before installing Vis products if you want to
use the 2D Postscript Converter option. You can download Ghostscript from
the following location:
http://ftp.ugs.com/open-source/ghostscript
Be sure to set the PSPath setting in the Convert and Print configuration file
to the full path of the gs_dir/bin/gs launch script.
1. Launch UGS Teamcenter Visualization for UNIX as described in the Teamcenter

Visualization Installation Guide.
2. Install the Convert, Print, and PDM Client Integration components using
the procedure described in the Teamcenter Visualization Installation Guide.
3. After installation is complete, add the path to UGS Teamcenter Visualization to

your system PATH environment variable.
On UNIX hosts, if multiple versions of X11 are installed, make sure the shared
object libraries of each version of X11 are available from the path specified by
the LD_LIBRARY_PATH (or SHLIB_PATH) environment variable.

Chapter 14 Installing a Special Services Host
Completing Special Services Configuration

This section contains procedures you must perform using the Configuration Editor
on the corporate server host to enable Enterprise Knowledge Management clients to
access the special services host.
Setting Configuration Variables

Enterprise Knowledge Management special services require certain configuration
variable settings. For information about setting configuration variables for special
services, see the Administrator’s Manual for Parts and Documents.
Mapping Special Services

To provide access to special services, you must define service mappings on the
corporate server. After service mappings are defined, the special services host
can service translate, print, and render requests from Enterprise Knowledge
Management clients.
For information about mapping special services, see the Administrator’s Manual for
Parts and Documents.

Chapter
15 Adding Server Solutions

and Components
Adding Server Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Installing Server Solutions on the Corporate Server . . . . . . . . . . . . . . . . . 15-1
Updating Local Area and Work Group Servers . . . . . . . . . . . . . . . . . . . . . 15-2
Updating Classic Client Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Adding an Enterprise Knowledge Management Component . . . . . . . . . . . . . . 15-3

Adding a Component to the Corporate Server . . . . . . . . . . . . . . . . . . . . . 15-4
Adding a Component to a Local Area or Work Group Server . . . . . . . . . . . 15-5
Adding the Enterprise Knowledge Management Indexed Search Engine . . . . . 15-6

Verifying Search Engine Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Reinstalling a Server Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7

Chapter
15 Adding Server Solutions

and Components
This chapter describes how to add Enterprise Knowledge Management server

solutions or components to any Enterprise Knowledge Management server (corporate
server, local area server, or work group server).

• Adding Enterprise Knowledge Management server solutions.
• Adding Enterprise Knowledge Management components, such as e!Vista.
• Adding the Enterprise Knowledge Management indexed search engine.
• Reinstalling modules previously installed on your corporate server.
Adding Server Solutions

This section describes how to add server solutions to your Enterprise Knowledge
Installing Server Solutions on the Corporate Server

To install server solutions on your Enterprise Knowledge Management corporate
server, perform the following steps:
If your Enterprise Knowledge Management license file requires an update for
the server solutions you want to install, make sure you copy the updated
license file to the directory specified by the LM_LICENSE_FILE system
environment variable, then stop and restart the license manager.
1. Stop the MUX and dispatcher services by entering the following commands:
dspstop
muxstop
2. Launch the Configuration Editor by changing to the MTI_ROOT/install

directory and entering the cfgedit2 command.

Chapter 15 Adding Server Solutions and Components
3. Make sure the disk locations list includes the locations of the software
distribution images for the server solutions you want to add. If necessary, add or
modify disk locations by clicking Modify Disk Locations.
4. Click Add Server Solutions.
5. Select the server solutions you want to install.
6. Click OK.
Depending on the server solutions you select, the Configuration Editor
may display additional prompts during installation.
When the installation is complete, exit the Configuration Editor.
7. Restart the MUX and dispatcher by entering the following commands:

muxstart
dspstart
Updating Local Area and Work Group Servers

Update local area and work group servers by performing the following steps:
1. If you changed the license manager configuration on the corporate server, verify
that the LM_LICENSE_FILE system environment variable is set correctly on
the local area or work group server.
2. Copy configuration files from the corporate server to each local area server and
each work group server. (The Configuration Editor generates these files when
you add a host to your configuration.) Configuration files are in the following
directories on the corporate server:
MTI_ROOT/install/hosts/common
MTI_ROOT/install/hosts/target-host-name
Replace target-host-name with the name of the local area or work group server
host.
Copy all files in these directories to the MTI_ROOT/install directory on the
local area or work group server.
3. Run the Enterprise Knowledge Management setup file (pdmsetup) to set

Enterprise Knowledge Management environment variables:1
C shells: source MTI_ROOT/config/pdmsetup
Korn and Bourne shells: . /MTI_ROOT/config/pdmsetup.sh
4. From a command prompt, start the installation script by entering the following
command:
esvm insmenu
1. If you automated setting of Enterprise Knowledge Management environment variables, this is performed automatically when you
log in.

Adding Server Solutions and Components
5. Answer the installation script prompts. Accept all default paths shown (unless
the location of the install images has changed). After you answer all necessary
prompts, the installation script displays the following prompt:
Enterprise Knowledge Management Installation Prompts Completed Previously
You have made the following selections:
Installation (MTI_ROOT) directory: path
Location of the install images: path
Are your answers correct [Y/N] [Y]?
6. Enter Y.
The installation script installs the selected server solutions on the host.
7. Propagate configuration changes to local area servers by running the pushall

command on the corporate server. For information about the pushall command,
see Executing the pushall Command in chapter 13, Installing Local Area and
Work Group Servers.
Updating Classic Client Hosts

On each classic client host, perform the following steps:
1. Transfer client configuration files from the corporate server.
2. Run the Enterprise Knowledge Management setup file (pdmsetup).
3. Run the installation script (insmenu).
For more information about these procedures, see steps 2 through 4 in Updating
Local Area and Work Group Servers, earlier in this chapter.
Adding an Enterprise Knowledge Management Component

The Configuration Editor allows you to add the following components to your
configuration after your initial Enterprise Knowledge Management installation is
complete:
Product Description
e!Vista Server libraries for e!Vista. This is required if your
corporate host contains a Web server that will serve
e!Vista clients.
Online documentation Library of manuals for all Enterprise Knowledge
Management products, accessible through a Web browser.
Support files Software libraries needed to customize the Enterprise
Knowledge Management modules you installed.
On your corporate server, you can add these components using the Configuration
Editor. On a local area or work group server, you can add a component using a special
installation script. The following sections describe how to add these components to
an existing Enterprise Knowledge Management server.

Enterprise Knowledge Management 2007 does not support reinstalling a

component after it is installed.
Adding a Component to the Corporate Server

To add any of these components to your corporate server, perform the following steps:
1. Launch the Configuration Editor:
Enter the following command:
cfgedit2
The Configuration Editor displays the Enterprise Knowledge Management

Configuration Editor dialog window.
2. Click Add Component.

The Configuration Editor displays the Add Component dialog window
(figure 15-1).
Figure 15-1. Add Component Dialog Window
3. Select the components you want to install and specify paths for those components
that require them, then click OK.
The Configuration Editor installs the selected components, then displays the
Enterprise Knowledge Management Configuration Editor dialog window.
4. Click Generate Files.

The Configuration Editor displays the Enterprise Knowledge Management
Configuration Editor Status dialog window. When file generation is complete,
the dialog window contains the following text:
Finished generating files.
Click the <OK> button to continue.
5. Click OK.
6. In the Configuration Editor dialog window, click Exit.
7. If you installed e!Vista or online documentation, perform the procedures

described in chapter 16, Configuring Legacy Web-Based Products.
8. Stop and restart the MUX and dispatcher by entering the following commands:

muxstop -r
Adding a Component to a Local Area or Work Group Server

Table 15-1 lists installation scripts for adding components to an existing Enterprise
Knowledge Management local area or work group server.
Table 15-1. Enterprise Knowledge Management Component Installation

Scripts
Component Installation Script
e!Vista insEvista
Online documentation insDocs
Support files insSupport
To add an Enterprise Knowledge Management component to an existing local area

or work group server, perform the following steps:
1. Stop the MUX and dispatcher by entering the following commands:
dspstop
muxstop

is available on your local host or network.
4. Enter the following command to start the component installation script:

esvm script-name
Replace script-name with the script name from table 15-1 corresponding to the
component you want to install.
5. If you are installing e!Vista, answer the following prompt:

Enter the location for the e!Vista files [default-path]:
Enter the location in which to create the e!Vista directory tree. Typically, this is
beneath the Web server’s document root, but can be any path accessible to the
Web server.
The default path is MTI_ROOT/evista.
6. If you are installing online documentation, answer the following prompt:

Enter the location for the online Documentation [default-path]:
Enter the path to the directory you want to contain the online documentation,
ore press enter to accept the default-path shown.
The default path is MTI_ROOT/docs.
7. The installation script displays your answers to previous prompts and asks
you to confirm your selections.

If you want to change your selections, enter N. The installation script repeats
the previous prompts, allowing you to change your answers. If you are satisfied
with your selections, enter Y.
The installation script installs the selected component.
8. If you installed e!Vista or online documentation, perform the procedures

described in chapter 16, Configuring Legacy Web-Based Products.
9. Restart the MUX and dispatcher by entering the following commands:

muxstart
dspstart
Adding the Enterprise Knowledge Management Indexed Search Engine

You can install the Enterprise Knowledge Management search engine on any
Enterprise Knowledge Management server host (corporate, local area, or work
group) by performing the following steps:
1. Create a search engine and configure it to run on the designated server host by
performing the steps in Configuring the Enterprise Knowledge Management
Indexed Search Engine in chapter 7, Configuring Enterprise Knowledge
Management.
For reference, record the search engine host name and port numbers on the
Installation Worksheet in chapter 1, Overview.
If your search engine host is the corporate server, skip the remaining steps in
this section and proceed to Verifying Search Engine Status, later in this chapter.
Otherwise perform the remaining steps to install the search engine service.
2. Copy all files in the MTI_ROOT/install/hosts/target-host-name directory on

the corporate server to the MTI_ROOT/install directory on the local area or
work group server. (Replace target-host-name with the host name of the local
area or work group server.) Use any file transfer method (such as FTP2 or the
UNIX cp command) to transfer files.
The MTI_ROOT/install/hosts/target-host-name directory contains configuration
files for the server, including the insdre.sav file, which contains search engine
configuration information.
Perform the remaining steps in this procedure on the search engine server host.
4. Enter the following command to launch the search engine installer:

./insautonomy
If the search engine installer does not launch successfully, the installer
displays a message that identifies the problem encountered. If this
occurs, perform whatever steps are necessary to correct the error and
then relaunch the installer.
2. If you use FTP, make sure you set the file transfer mode to ASCII.

5. If the installation is successful, the installer automatically starts the search

engine service and displays a confirmation message.
If the search engine is unable to start and displays an error message, the port
numbers you assigned to the search engine may be in use by another program.
If this occurs, see appendix B, Troubleshooting, for possible solutions.
Verifying Search Engine Status

To verify that the search engine service started successfully, enter the following
command:
ps -ef | grep search-engine–name
If the search engine failed to start, see appendix B, Troubleshooting, for possible
solutions.
Reinstalling a Server Solution

To reinstall a server solution you installed previously, perform the following steps:
1. Launch the Configuration Editor by changing to the MTI_ROOT/install
directory and entering the cfgedit2 command.
2. Click Reinstall Server Solution.

The Configuration Editor displays the Reinstall Server Solutions dialog window
(figure 15-2).
Figure 15-2. Reinstall Server Solutions Dialog Window
3. Select one or more server solutions from the list of server solutions available for
reinstallation, then click OK.

• If your reinstall a server solution that contains custom modules

that add or modify functionality of standard modules, and the
changes include modifying or deleting custom classes or attributes,
the reinstall server solution process does not automatically add new
classes or attributes. Furthermore, the Configuration Editor does not
perform the following database alterations:
– Delete or modify definitions of existing attributes.
– Delete classes.
To complete reinstallation of custom server solutions, you must

perform these changes manually using the alterdb command. For
more information about using the alterdb command, see the Server
Customization manual.
• If you do not select a server solution from the list before clicking OK,
all server solutions in the list are reinstalled.
The Configuration Editor displays a confirmation dialog window containing a

message similar to the following:
Do you want to reload the initial objects contained in the
data files for the selected modules?
4. Click Yes if you want the Configuration Editor to reload the .dat files3 for all
modules in the selected solution. Otherwise, click No.
If the Enterprise Knowledge Management Foundation server solution is
selected for reinstallation and you answer Yes to the confirmation dialog
window described in the previous step, the Configuration Editor replaces
.dat files for all modules in the solution, including OMF. All default
administrative data in the databases is deleted and reloaded.
The Configuration Editor displays the Configuration Editor Status dialog

window while it reinstalls the selected server solutions.
When reinstallation is complete, the dialog window contains the following
message:
Click the <OK> button to continue.
5. Close the Configuration Editor.

When you reinstall a server solution, the Configuration Editor creates a
new mtiinstance-name.ini file in the system root directory and renames
the previous mtiinstance-name.ini file to mtiinstance-name.old.
3. The .dat files are the xxxadmdb.dat files (xxx is the three-letter identifier for the given module) placed in the MTI_ROOT/dbinit directory
when a given module is installed. These files typically contain default data for each module that is loaded into the database during the
installation process.

6. Stop and restart the MUX and dispatcher by entering the following commands:
dspstop
muxstop
muxstart
dspstart

Chapter
16 Configuring Legacy Web-Based

Products
Updating Java Security for e!Vista Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Configuring e!Vista . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Configuring Online Documentation . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . 16-3

Enabling Symbol Fonts . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . 16-3
Making Online Documentation Web-Accessible . . . . .. . . . . . . . . . . . . . . 16-3
Step 1: Creating the docs Virtual Directory . . . . .. . . . . . . . . . . . . . . 16-4
Step 2: Setting the ONLINE_DOC_URL Variable . . . . . . . . . . . . . . . 16-4
Step 3: Updating the e!Vista Launch Page . . . . . .. . . . . . . . . . . . . . . 16-5
Launching Web-Based Enterprise Knowledge Management Products . . . . . . . 16-6

Entering a Launch URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Logging In to Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . 16-7
Logging In Through an e!Vista Task . . . . . . . . . . . . . . . . . . . . . . . . . 16-7

Chapter
16 Configuring Legacy Web-Based

Products
This chapter provides additional procedures to perform if you installed any of the
following Enterprise Knowledge Management products on your corporate server:
• e!Vista
• Online documentation library
• How to update Java security for e!Vista tasks.
• How to configure Web-based Enterprise Knowledge Management products.
• How to launch Web-based Enterprise Knowledge Management products from a

Web browser.
Before you perform any procedures in this chapter, ensure that an Siemens PLM
Software-supported Web server is installed and operational on your corporate
server host. For information about supported Web servers, see chapter 2, System
Requirements.
This chapter does not describe how to install thin client solutions. For information
about installing thin client solutions, see chapter Installing Thin Client Solutions.
Updating Java Security for e!Vista Tasks

This section describes how to update the Java security file for use with Web-based
Enterprise Knowledge Management products.
If you do not use any e!Vista tasks, skip this section.
Each host from which e!Vista is launched must refer to the Enterprise Knowledge
Management java.policy file in its local java.security file. Perform the following
steps to update the java.security to reference the Enterprise Knowledge
Management java.policy file:

Chapter 16 Configuring Legacy Web-Based Products
1. Open the following file in a plain text editor such as vi:

JRE-path/lib/security/java.security
Replace JRE-path with the path to the Java SE Runtime Environment (JRE)
or the Java SE Software Development Kit (SDK).
2. Locate in the file a set of policy.url statements similar to the following:

policy.url.1=path
policy.url.2=path
policy.url.3=path
3. Add the following policy.url statement after the existing policy.url statements:
policy.url.sequence=http://Web-server/instance-namedocs/java/classes/java.policy
Replace sequence with the next number in the policy.url sequence. Replace
Web-server with the name of your Web server host. Replace instance-name with
the Enterprise Knowledge Management instance name. For example:
policy.url.4=http://AcmeCorp/m70adocs/java/classes/java.policy
4. Save the changes to the java.security file and close the file.
Update the java.security file on each host that accesses e!Vista.
Configuring e!Vista
If you use e!Vista, create the virtual directories shown in table 16-1 on your Web
server. Replace e!Vista-path with the path to your e!Vista home directory and replace
instance-name with the name of your Enterprise Knowledge Management instance.
Make sure you set access permissions as specified.
Table 16-1. Web Server Virtual Directories for e!Vista

Physical Access
Alias1 Type Directory Path Permissions
instance-namedocs2 Document e!Vista-path Read
instance-namecgi CGI e!Vista-path/cgi-bin Read, execute
Obtain the exact virtual directory names and paths from the Installation Worksheet
in chapter 1, Overview. (You recorded this information in chapter 6, Installing
Enterprise Knowledge Management.)
You must have administrative access to the Web server to create virtual
directories.
For information about creating virtual directories on your Web server, see the
documentation for your Web server.
1. The alias is the name used to access the virtual directory.

2. For example, if your Enterprise Knowledge Management instance name is m70a, this alias is m70adocs.

Configuring Legacy Web-Based Products
Stop and restart your Web server to activate the virtual directories after you create
them.
Configuring Online Documentation

This section describes how to make the Enterprise Knowledge Management online
manuals library available through the classic client and e!Vista. To configure the
online manuals library, perform the procedures described in the following sections.
This section does not describe installing online manuals for access through
the thin client or the rich client. For information about installing the Online
Manuals thin client solution, see chapter 9, Installing Thin Client Solutions.
Online manuals are not available through the rich client.
Enabling Symbol Fonts

Enterprise Knowledge Management online documentation requires
ISO-8859-compliant symbol fonts. If you use Netscape, you must enable these fonts
by performing the following steps:
1. Enter the following command to change to your home directory:
cd $HOME
2. Add the following line to your .Xdefaults file:

Netscape*documentFonts.charset*adobe-specific: iso-8859-1

xrdb .Xdefaults
Making Online Documentation Web-Accessible

The Enterprise Knowledge Management installation process makes online
documentation available only to hosts that have access to the file system containing
the online documentation.3 If you want to make online documentation accessible on
all hosts in your network, you must perform the following steps:
1. Create the docs virtual directory on your Web server.
2. Change the value of the ONLINE_DOC_URL configuration variable to a Web

address.
3. If you use e!Vista, update the e!Vista launch page.
These steps are described in the following sections.
3. Online documentation is invoked through the Help→Online Manuals option in classic Enterprise Knowledge Management and the
Online Manuals option in e!Vista.

Step 1: Creating the docs Virtual Directory
Create a virtual document directory named docs on your Web server with the
following properties:
Alias: docs
Directory path: MTI_ROOT/docs4
Access permission: Read
You must have administrative access to the Web server to create virtual
directories.
After you create the docs virtual directory, stop and restart your Web server to
activate the virtual directory.
For information about creating virtual directories on your Web server, see the
documentation for your Web server. For specific Web server product and version
requirements, see chapter 2, System Requirements.
Step 2: Setting the ONLINE_DOC_URL Variable
Set the ONLINE_DOC_URL variable by performing the following steps:

1. Launch the Configuration Editor:
Enter the following command:
cfgedit2
Enterprise Knowledge Management displays the Configuration Editor dialog

window.
2. Click Modify Configuration Variables.
3. In the Configuration Hierarchy field, select the Global group (at the top of the
hierarchy).
4. Click Modify Class Configuration Variables.

The Configuration Editor displays the Modify Class Configuration Variables
dialog window.
5. Locate the ONLINE_DOC_URL configuration variable (figure 16-1).
4. If you installed online documentation in a different directory, set this directory path to the path you chose for the online
documentation. You recorded this path on the Installation Worksheet in chapter 1, Overview.

Figure 16-1. Setting the ONLINE_DOC_URL Configuration Variable
6. Change the value of ONLINE_DOC_URL to the following value:

http://Web-server/docs/en_us/index.html
Replace Web-server with the name of your Web server.
7. Click OK to close the Modify Class Configuration Variables dialog window.
8. Click OK to close the Modify Configuration Variables dialog window.
9. Click Generate Files on the Enterprise Knowledge Management Configuration

Editor dialog window.
The Configuration Editor generates configuration files for all hosts in the
configuration. For information about how to move these files to other hosts, see
chapter 13, Installing Local Area and Work Group Servers.
10. Click OK to close the Enterprise Knowledge Management Configuration Editor

Status dialog window.
11. Click Exit to close the Configuration Editor.
Step 3: Updating the e!Vista Launch Page
The e!Vista launch page contains HTML links to the online documentation library.
To update these links with the Web-accessible online documentation URL, perform
the following steps:
1. Open the following file in a plain text editor such as vi:

e!Vista-path/en_us/omf/general/launch/eVista.html5
5. The default e!Vista-path is MTI_ROOT/evista.

2. Locate the following line in the file:

<TD>
<FONT size="4" face="Helvetica,Arial"><A href="file://MTI_ROOT/docs/en_us/index.html"
Manuals</A></FONT></TD>
3. Replace file://MTI_ROOT/docs/en_us/index.html with the following address:

/docs/en_us/index.html
4. Save the file and close the text editor.
Launching Web-Based Enterprise Knowledge Management Products

To launch any Web-based Enterprise Knowledge Management product through a
Web browser, you must enter the correct launch URL, then log in to Enterprise
Knowledge Management. The following sections describe launch procedures for each
Web-based Enterprise Knowledge Management product.
Before attempting to launch any Web-based Enterprise Knowledge

Management product, be sure that the following programs and services are
running:
• Enterprise Knowledge Management MUX and dispatcher services on the
corporate server host
• Web server6
Entering a Launch URL

Table 16-2 lists the default URLs for launching Web-based Enterprise Knowledge
Management products. Find the URL for the product you want to launch, then
enter the URL into your Web browser. For convenience, you can bookmark these
URLs in your browser.
Table 16-2. Launch URLs for Web-Based Enterprise Knowledge Management Products
Product URL
e!Vista Launch Page http://Web-server/instance-namedocs/en_us/omf/general/launch/eVista.html
Home Collection7 http://Web-server/instance-namedocs/en_us/omf/general/launch/HomeCollection.html
Online Manuals9 http://Web-server/docs/en_us/index.html
Report Writer9 http://Web-server/instance-namedocs/en_us/omf/general/launch/ReportWriter2.html
6. If your Web server is installed on a host separate from the corporate server host, MUX and dispatcher services must be running
on that host as well.
7. This page can be opened directly through this URL or from the e!Vista launch page.

In the URLs in table 16-2, replace Web-server with the name of your Web server and
replace instance-name with the name of your Enterprise Knowledge Management
instance.
For example, if your Web server is named AcmeCorp and the name of your
Enterprise Knowledge Management instance is m70a, the URL to the e!Vista
Launch Page is as follows:
http://AcmeCorp/m70adocs/en_us/omf/general/launch/eVista.html
In non-English locales, replace en_us with your locale identifier in each of the
launch URLs in table 16-2.
Logging In to Enterprise Knowledge Management

This section describes how to log in to Enterprise Knowledge Management through
any of the Web-based products listed in table 16-2.
Logging In Through an e!Vista Task
You can launch an e!Vista task such as the Home Collection directly through the
task URLs in table 16-2 or from the e!Vista launch page.
To log in to Enterprise Knowledge Management from the e!Vista launch page, click
the link corresponding to the task you want to launch.
e!Vista displays an e!Vista title screen and then displays the OMF Login dialog
window (figure 16-2). (A task URL sends you directly to this dialog window.)
Figure 16-2. e!Vista OMF Login Dialog Window

Enter your user name and password, then click OK.
If e!Vista login is not successful, see appendix B, Troubleshooting, or the
Administrator’s Manual, for possible solutions.

Part
V Appendixes
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Oracle Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Installing and Running Enterprise Knowledge Management Using NFS . . . . . D-1
Installing Maintenance Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Uninstalling Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . . . . F-1

Appendix
A Glossary

Appendix
A Glossary
This appendix defines Enterprise Knowledge Management terms.
Administration Editor
Graphical user interface that permits Enterprise Knowledge Management
administrators to perform administrative tasks, such as setting up and managing
users, groups, rules, locations, and vaults.
Administrative Database
Type of Enterprise Knowledge Management database in a distributed-database
environment. The administrative database contains all objects created in the
administrative class, such as users, groups, rules, projects, and vaults, and all
administrative relation objects, such as access on, mount from, user-to-group, and
user-to-host. Compare with Corporate User Database, Key Database, Life Cycle
Manager Database, Operational Database, and User Database.
Administrator
Person who manages participant validation, host configuration, communications,
and database maintenance.
Advanced Product Configurator

Module that allows an enterprise to manage product structures by identifying
relationships between parts, alternate parts, substitute parts, and optional parts. In
addition, it supports revision level and structure effectivities.
APC
See Advanced Product Configurator.
Browser
Window that displays icons representing objects managed by Enterprise Knowledge
Management. A user can perform actions on an object by choosing menu options
and dropping icons on other icons or on other browsers. A user can also display
graphically the relationships between objects. Compare with Dialog Window.
Button
User interface control that performs the indicated action.
MT00300 L3 Installation on UNIX and Linux Servers A-1

Appendix A Glossary
Cache
Buffer holding copies of database tables or results of previous operations for quick
access.
CCF
See Change Control Framework.
CCM
See Change Control Manager.
Change Control Framework

Module that provides a framework for Enterprise Knowledge Management
industry-specific change management solutions.
Change Control Manager

Module that provides the capability to specify, control, track, and report changes
to enterprise objects, such as product data, life cycle processes, and Enterprise
Knowledge Management customizations.
Change Information Item

Business item that provides supporting information about a particular change item.
Examples of change information items include markups or notes of a conversation
with a customer about a particular change proposal. Change information items are
specific to the change item they support. They are related to change items through
the Supports relationship.
Change information items are owned and controlled by the change item they
support. One change information item can support only one change item, whereas a
change item may be supported by many change information items.
Change Management Solution

Module that implements a change management solution under a CMII template.
This solution is built on the framework provided by Change Control Framework.
See also Change Control Framework.
Child Class
Class below a parent class in the class hierarchy. Child classes inherit attributes and
messages from their parent. See also Parent Class and Class Hierarchy.
Class
Set of objects with common attributes and messages.
Class Constant
Named attribute of the class that describes the class as a whole rather than separate
instances of the class. A class constant is a class-wide value.
Class Hierarchy
Set of all classes in the system ordered according to parent-child relations. See also
Child Class and Parent Class.
Classic Client
Siemens PLM Software’s proprietary client/server interface to Enterprise Knowledge
Management—a collaborative product management family of products. See also
Client.
A-2 Installation on UNIX and Linux Servers MT00300 L3

Glossary
Click
To press the mouse button down and then release.
Client
1. Executable program that requests the services of a server to complete an action.
2. Application that serves a user in a client-server system. In Enterprise

Knowledge Management, a GUI presentation program is called a client because
this program implements the client role of client/server computing. See also
Rich Client and Thin Client.
Client
Role played by a software component of a system when it requests particular services
be performed on its behalf by another entity, a server. In the case of data migration,
the Migration Wizard is a client that gathers user input and requests services from
the TDS sever. See also Server.
CMS
See Change Management Solution.
Collection
Group of GTAC items that pertain to similar topics. A collection can contain other
collections and information items.
Configuration Editor
Series of screens used to collect data about an Enterprise Knowledge Management
configuration. During installation, it generates files used by the installation script.
After installation, the administrator must use it to perform such tasks as adding
new modules, modifying host and database information, and modifying configuration
variables and service settings.
Configuration Variable
Variable in the Enterprise Knowledge Management configuration file. Configuration
variables control Enterprise Knowledge Management runtime behavior and aspects
of the appearance and behavior of the Enterprise Knowledge Management user
interface. Some Enterprise Knowledge Management configuration values can also
be specified as operating system environment variables.
Corporate Server
Host computer at the center of an Enterprise Knowledge Management collaborative
product management network. This host holds certain database tables that all
other Enterprise Knowledge Management server hosts must be able to access and
update. Each Enterprise Knowledge Management network has one and only one
corporate server.
Corporate User Database

Enterprise Knowledge Management database in a distributed-database environment.
The corporate user database is a user database located on the corporate server. It
contains items owned by the OMF administrator and business items and files that
are either entered at the corporate level or migrated as completed products out of
the user databases. There is only one corporate user database in an Enterprise
Knowledge Management network. Compare with Administrative Database, Key
Database, Life Cycle Manager Database, Operational Database, and User Database.

Appendix A Glossary
Cost
Business item that is related to a part, package, change request, or change notice
and represents a monetary value. Typically, a document attached to the cost item
includes the price to build or procure the related business item.
Customization
Customer modification of Enterprise Knowledge Management behavior or
appearance.
Database Server
Process that presents a defined interface between method servers and the database.
Compare with Method Server.
Dialog Window
Window or form that Enterprise Knowledge Management displays to gather
information from a user or display information to a user. Compare with Browser.
Direct Connection Bridge

Network view bridge in which one host in each network view is selected as the
gateway.
Dispatcher
Continuously running process that manages processes in service pools based on a
configuration file and service demand.
Distributed Databases
Configuration in which Enterprise Knowledge Management data is distributed
among multiple databases; usually, the databases are distributed among multiple
hosts. See also Administrative Database, Corporate User Database, Key Database,
Life Cycle Manager Database, Operational Database, and User Database.
Document Manager
Enterprise Knowledge Management Document Manager; module that provides
enhanced document management capability including full-text retrieval and
indexing, viewing and markup of files without native authoring applications, and a
simplified user interface that is integrated with Microsoft Office applications.
Document Manager Administrator

Person responsible for configuring and maintaining the Document Manager system.
The Document Manager administrator creates Document Manager control objects,
configures Document Manager services and support applications, and assigns
Document Manager users to groups controlling access to documents and Document
Manager functions.
e!Vista
Siemens PLM Software’s Java-enabled interface to Enterprise Knowledge
Management. The e!Vista emulation of the classic client has a Web browser
interface. See also Classic Client.

Glossary
e!Vista Task
Java-enabled window or set of windows that support a specific user task in
Enterprise Knowledge Management. See also e!Vista.
FTR
See Full-Text Retrieval.
FTR Index
Index of document content created by Document Manager to allow users to search
for and retrieve documents based on text content (words and phrases). See also
Full-Text Retrieval.
FTR Index Collection

Collection of full-text retrieval (FTR) index data for documents. Each Enterprise
Knowledge Management user database can have one or more index collections. See
also Full-Text Retrieval.
Full-Text Retrieval
Search feature that allows users to search for and retrieve documents by entering
words or phrases contained in the documents.
Global Technical Access Center

Repository of Enterprise Knowledge Management product data management
information accessible on the World Wide Web. Information is organized into
collections.
Graphical User Interface

A graphics-oriented means of interaction between users and computers that uses
windows, menus, and icons and allows direct manipulation of objects.
GUI
See Graphical User Interface.
Help
Online information describing how to use Enterprise Knowledge Management
products.
Home Browser
Browser that begins a user interactive (browser) session. It allows a user to create
other windows.
Industry Standard Classes

Module that provides classes for use in other Enterprise Knowledge Management
modules and in application interfaces.

Appendix A Glossary
Inheritance
Characteristics of a class passed from parent to child. These include attributes,
messages, keys, display name, indexes, and class constants. The child or children
can override some of these characteristics. The inheritor can define the behavior and
data structure of its instances as a subset of the definition of another class or classes.
Installation
Separately administered Enterprise Knowledge Management implementation. An
enterprise can have more than one installation. For example, the divisions of a
multinational company may have different Enterprise Knowledge Management
installations—a European installation and a South American installation.
Geographically separated locations (sites) are not necessarily separate installations.
One installation can encompass databases in different sites.
Instance
Object that behaves in a manner specified by a class.
insweb
Command that launches the Web Application Manager. See Web Application
Manager.
Integrator Toolkit
Module that provides a set of tools and toolkits for customizing the classic client.
Key Database
Type of database in an Enterprise Knowledge Management distributed-database
environment. The key database contains the set of all keys for all classes and
guarantees data uniqueness across all databases in an Enterprise Knowledge
Management network. There is only one key database in an Enterprise Knowledge
Management network. Compare with Administrative Database, Corporate User
Database, Life Cycle Manager Database, Operational Database, and User Database.
LCM
See Life Cycle Manager.
Life Cycle Manager

Module that manages the enterprise’s product information workflow, from the macro
view (the life cycle) to the micro view (processes that move work items between
states in the life cycle).
Life Cycle Manager Database

environment when Enterprise Knowledge Management includes Life Cycle
Manager. The Life Cycle Manager database contains administrative information
about life cycles, including life cycle steps and processes. When Enterprise
Knowledge Management includes Life Cycle Manager, an Enterprise Knowledge
Management network can have multiple Life Cycle Manager databases. Compare
with Administrative Database, Corporate User Database, Key Database, Operational
Database, and User Database.

Glossary
Local Area Server

Server that provides services usually provided by the corporate server in the
following situations:
• For a site that is geographically separated from the corporate server.
• For a local site that needs to reduce the load on the corporate server.
Maintenance Pack
A grouping of patch sets created by a patch build and uploaded to the Global
Technical Access Center (GTAC) for availability to customers. A maintenance pack
is identified by a four-number identifier, yyww, where yy represents the last two
digits of the year and ww represents digits corresponding to the week in the year in
which the maintenance pack is delivered.
Managed Host
Computer that is part of an Enterprise Knowledge Management network and is
described in the host map of the configuration file. The multiplexor, dispatcher, and
OS (operating system) server may run on a managed host, which can be either an
Enterprise Knowledge Management client or an Enterprise Knowledge Management
server. Compare with Unmanaged Host.
Method Server
Server whose purpose is to execute a set of methods grouped by class. Marketing,
application integration, and customization needs dictate the grouping of class
methods into individual method servers. Compare with Database Server.
Mixin Configuration Variables

Named group of configuration variables that can be applied across several
configuration classes as a restricted form of multiple inheritance. The named groups
(for example, UNIX and WINDOWS) provide a central place to change a setting for
all hosts of the designated type.
MODeL
Enterprise Knowledge Management object definition language. MODeL statements
define an in-memory dictionary that stores the object class hierarchy, the attributes
of each object, and the messages sent to each object. The system compiles MODeL
statements into a downloadable image.
Module
A separately installable part of Enterprise Knowledge Management.
msql
Structured Query Language interfaced database server. This is a vendor-independent
database management system for methods.
MTI_ROOT
Environment variable whose value is the path to the home directory of the
Enterprise Knowledge Management software. The value of MTI_ROOT is created
during the Enterprise Knowledge Management installation process and maintained
in the pdmsetup file.

Appendix A Glossary
MUX
Multiplexing communications program used by Enterprise Knowledge Management
to manage logical connections between processes. The MUX program maps the
connection as seen by the process to the physical connection that a pool makes
available as needed.
Native Language Support

Set of internationalization functions and files available on a system. An NLS system
is composed of a database and a toolkit that allows users to localize the product.
Network View
Set of Enterprise Knowledge Management hosts that can communicate with each
other through a common protocol, such as TCP/IP. All hosts within the view must
be able to directly communicate with each other without encountering a firewall,
router, or protocol bridge.
Network View Bridge

Gateway for hosts in two network views to communicate with hosts in both views.
See also Direct Connection Bridge, Overlap Bridge, and Routing Bridge.
NLS
See Native Language Support.
Object
Instance of a class. MODeL statements define classes; object layer functions (obj
and oi prefixes) instantiate them.
Object Management Framework

Module that provides the framework for Enterprise Knowledge Management. It
brings together the tools and information needed to complete activities on a daily
basis. Within Object Management Framework, each piece of information is an object
represented by an icon that users can directly manipulate.
Object Server
See Method Server.
OMF
See Object Management Framework.
Operating System Server

Process (OS_SERV) running as a user that provides services to methods at the
level of the operating system.
Operational Database
environment. The operational database contains event processing information:
event queues, an event log, and a mail log. An Enterprise Knowledge Management
network can have multiple operational databases. Compare with Administrative
Database, Corporate User Database, Key Database, Life Cycle Manager Database,
and User Database.

Glossary
Overlap Bridge
Network view bridge in which the two network views overlap to share common hosts.
One of these common hosts is then selected to be the gateway.
Parent Class
Class above a child class in the class hierarchy. A parent class can have one or more
child classes beneath it. See also Child Class and Class Hierarchy.
Part Family Manager

Module that provides the capability to organize and classify parts used in products.
PFM
See Part Family Manager.
Quote
Response to an RFQ. A document that contains the price to build or procure the
business item that is the subject of the RFQ. See Request for Quote.
RDBMS
See Relational Database Management System.
Relational Database Management System

Software stores information in relations, implementing the rules of relational
algebra, and using ANSI SQL to manipulate the data.
Replica Database
In a distributed-database environment, an Enterprise Knowledge Management
database that is a member of a replica set and contains objects of the classes
designated by the replicate MODeL statement. Each replica database contains an
exact reproduction of the replicated objects in the other databases in the replica
set. When a replicated object is created, updated, or deleted, the information is
automatically reproduced in all the replica databases belonging to the replica set.
See also Replica Set.
Replica Set
In a distributed-database environment, a set of databases created by the define
replica set MODeL statement. Each database in the set is called a replica database.
See also Replica Database.
Request for Quote

Document that is sent to a supplier that requests a price to build or procure a
business item. See RFQ.
Restricted Client
e!Vista client that is limited in capability because it cannot escape Java-imposed
security restrictions for applets. Among other limitations, it cannot connect to the
MUX on the client host. Compare with Unrestricted Client.

Appendix A Glossary
RFQ
See Request for Quote.
Rich Client
Web application interface to Enterprise Knowledge Management with integrations
to CAD authoring tools and additional optional capabilities.
Routing Bridge
Network view bridge in which two network views route their connections through
one or more views that already have a network view bridge defined between them.
Server
System software component that performs a specifically defined set of software
services on behalf of one or more clients. In a typical Enterprise Knowledge
Management installation, servers are centralized on dedicated managed hosts
that support a large number of clients. Clients are distributed on managed and
unmanaged hosts which are connected to the servers via various networking
techniques. See also Client.
Server Host
Host computer that runs either an RDBMS or one or more Enterprise Knowledge
Management database servers or method servers.
Service
Process managed by the dispatcher, for example, method server, data distribution
server, and background client. See also Dispatcher.
Subclass
See Child Class.
Task
See e!Vista Task.
Task-Focused Interface
Another name for an e!Vista task. See e!Vista Task.
Teamcenter Security Services

Services that eliminate prompts for login credentials when users switch Teamcenter
products within a user session. Authentication is performed by an external identity
service provider, such as lightweight directory access protocol (LDAP), instead of
the product. At a site that deploys multiple Teamcenter products and Teamcenter
Security Services, users log in once to access all participating Teamcenter products.
Text Field
Control in which a user can enter text.
Thin Client
Web browser interface to Enterprise Knowledge Management.
Transaction Server
See Database Server.

Glossary
Trusted User
OS user who starts the MUX and dispatcher and owns Enterprise Knowledge
Management servers.
Unmanaged Host
Computer that is not part of the configured Enterprise Knowledge Management
network and does not have multiplexor, dispatcher, or OS (operating system) server
software. Compare with Managed Host.
Unrestricted Client
e!Vista client that escapes Java-imposed security restrictions for applets and has full
client capability. Among other capabilities, it can connect to the MUX on the client
host. Compare with Restricted Client.
User Database
environment. A user database contains the objects owned by users and vaults.
An Enterprise Knowledge Management network has at least one user database
(the corporate user database) and can have multiple user databases. Compare
with Administrative Database, Corporate User Database, Key Database, Life Cycle
Manager Database, and Operational Database.
Utility
Tool or application that indirectly supports the enterprise. Typically runs in the
background with no windows.
Visualization/Markup
Module that provides classes and attributes supporting visualization and markup of
files.
Web Application Manager

The program that installs the Web components required for Enterprise Knowledge
Management. You run the Web Application Manager with the insweb command.
Work Group Server

Host computer that runs one or more method servers or database servers. It may
also run RDBMS software in a distributed-database environment or access the
database on the corporate server using RDBMS-provided client/server technology.
Workstation
Host computer that runs an Enterprise Knowledge Management GUI client program.
X-Window System
The X-Window System is a network-based graphics window system. It was developed
by MIT and is an industry standard used for developing GUI applications on UNIX
platforms.

Appendix
B Troubleshooting
Installation Utility and Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . B-1

Installation Utility Is Not Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Unable to Start the Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . B-2
Restarting the Configuration Editor After a Failed Installation . . . . . . . . . B-2
Installation Script Fails (Cannot Load Object Data) . . . . . . . . . . . . . . . . . B-3
Installation Script Fails During MODeL Generation . . . . . . . . . . . . . . . . B-3
MODeL Viewer Does Not Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Communications Multiplexor (MUX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
Troubleshooting Enterprise Knowledge Management Configuration . . . . . B-7
Search Engine Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

Search Engine Cannot Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Search Engine Installation Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10

Structured Query Language Utility (msql) Cannot Log In . . . . . . . . . . . . B-10
Recovering an Oracle Instance From Deleted Data Files . . . . . . . . . . . . . B-11
Oracle Timeout Connection Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11

Appendix
B Troubleshooting
This appendix describes solutions to problems that you may encounter during
the installation process. Sections in this appendix are grouped by the Enterprise
Knowledge Management products or product areas to which they pertain.
Installation Utility and Configuration Editor

This section provides steps to take if you encounter problems starting or using the
Configuration Editor or the Enterprise Knowledge Management installation utility.
Installation Utility Is Not Enabled

If the Enterprise Knowledge Management installation utility detects an existing
Enterprise Knowledge Management installation, the utility may display the
Configuration Editor dialog window or an error message.
When you enter the cfgedit2 command, the installation utility searches for a
configuration file (config.cfg) in the location defined by PDM_CONFIG (if it
is set) or in the MTI_ROOT/config directory (if PDM_CONFIG is not set). If
the installation utility finds a configuration file, the utility assumes Enterprise
Knowledge Management has been previously installed and it launches the
Configuration Editor.
If you are performing a new Enterprise Knowledge Management 2007 installation,
determine whether the PDM_CONFIG environment variable is set and whether a
config.cfg file exists in the config directory under MTI_ROOT.
To re-enable the installation utility, delete the existing Enterprise Knowledge
Management configuration by performing the following steps:
1. Delete the config.cfg file from the MTI_ROOT/config directory.
2. Unset the PDM_CONFIG environment variable if it is set.
After you perform these steps, the installation utility is enabled the next time you
enter the cfgedit2 command.
MT00300 L3 Installation on UNIX and Linux Servers B-1

Appendix B Troubleshooting
Unable to Start the Configuration Editor

The following error appears if the DB_VENDOR environment variable is not set:
Unable to start Configuration Editor:
DB_VENDOR needs to be set in environment
To fix the error, set the DB_VENDOR environment variable to ORA (the value
must be uppercase). For more information about setting database environment
variables, see the Oracle administration appendix in the Network and Database
The following error occurs if the PATH does not contain the bin directory under the
JRE_HOME location:
cfgedit[15] : jre: not found.
To fix the error, add the path to the Java executables to the PATH statement in the
startup file. On most systems, the path to the Java executables is Java-path/bin,
where Java-path is the path to the home directory of the Java SE Runtime
Environment (JRE) or the Java SE Software Development Kit (SDK). For detailed
information about setting up the environment, see Setting System Environment
Variables in chapter 5, Preparing the Enterprise Knowledge Management
Environment.
Restarting the Configuration Editor After a Failed Installation

The Configuration Editor can attempt to recover a failed Enterprise Knowledge
Management installation rather than completely reinstalling Enterprise Knowledge
Management.
If an error occurs during Enterprise Knowledge Management installation on the
corporate host, the Configuration Editor displays a red dialog window describing
the error. Click OK to dismiss this dialog window and exit the Configuration Editor.
If the error dialog window contains a suggestion for correcting the error, perform
whatever procedure the error dialog window recommends. You can then restart the
Configuration Editor (cfgedit2).
If the previous installation failed prior to the database creation and initialization
processes, the Configuration Editor displays the following message:
Previously incomplete install operation detected -
do you wish to restart and complete the operation?
• If you click Yes:

If the previous installation failed prior to executing the database commands, the
Configuration Editor gives you the option to restart the installation from the
beginning. If the previous installation failed after executing database commands,
the Configuration Editor continues from the point at which the error occurred.
• If you click No:

The Configuration Editor terminates.
If the previous installation failed during database creation or initialization, the

Configuration Editor displays the following message upon restarting:
Previously incomplete database install detected -
do you wish to modify database information before continuing?
B-2 Installation on UNIX and Linux Servers MT00300 L3

Troubleshooting
• If you click Yes:

The Configuration Editor displays the Modify Database Information dialog
window, allowing you to change database information.1 When you are satisfied
with your changes, click OK. The Configuration Editor removes files generated
during the failed installation and restarts database creation and initialization
using the new database information.
• If you click No:

The Configuration Editor resumes database creation and initialization from the
step at which the previous installation failed.
Installation Script Fails (Cannot Load Object Data)

If an error occurs during database loading, the Configuration Editor may display
the following message:
Error:Could not load Object Data for #USR#.
See fatal error above or reference bulk loader documentation
for interpreting retry file (#REF#).
The cause of this error is usually that the database server is down, the database
is full, or the database is not accessible from the account. See your database
administrator to resolve the problem. After you resolve the problem, restart the
Configuration Editor (cfgedit2) to resume installation.
If the error is a result of exceeding the number of soft (100) errors (caused by too
many duplicate data rows), see the bulk loader documentation for information about
how to fix your original input file. When the original input file is correct, rerun the
installation script. For more information about using bulk loader, see the Network
and Database Configuration Guide.
Installation Script Fails During MODeL Generation

If you receive the following error, one possible cause is a host name discrepancy:
Regenerating optimized MODeL file.
*** Error: cannot find file in :
%s>
low_prn: NULL string pointer argument encountered.
*** Exiting with dstat = 1758504

Failure in running MODeL
Enterprise Knowledge Management Installation has failed
If the first name listed for the corporate server in the /etc/hosts file (this is the
name used by the Configuration Editor) is different from the host name used by the
MUX and dispatcher (which is the result of the uname –n command), MODeL
generation fails.
To fix the error, ensure that the first host name listed in the /etc/hosts file on the
corporate server matches the results of the uname –n (or hostname) command.
1. For more information about the Modify Database Information dialog window, see the Network and Database Configuration Guide.

In the Configuration Editor, use the official name of the host as returned by
the UNIX uname –n command. Do not use an alias.
MODeL Viewer Does Not Launch

On Sun Solaris platforms, the libsunmath.so.1 library is required to launch
MODeL viewer. If this library is not available, MODeL viewer fails to launch and
displays the following error:
mvi: fatal: libsunmath.so.1: open failed: No such file or directory
To resolve this error, make sure the libsunmath.so.1 library is present on

your system and verify that the path to libsunmath.so.1 is included in the
LD_LIBRARY_PATH environment variable.
Communications Multiplexor (MUX)

This section provides steps to take if you encounter problems starting the Enterprise
Knowledge Management MUX.
When the following problem occurs:
% muxstart
Mux started.
*** Find TcpMux: rresvport: Permission denied
*** processCfgRecv: unable to load configuration from rs1
Mux daemon is up.
You need to run root.sh in the install directory as root. This program sets the
set-uid bit to root for the muxd and olaunch executables.
When the following problem occurs:
% muxstart
Mux started.
*** InitTcpXprt: port 7701: bind: Address already in use
*** muxd: program aborting...
Mux daemon is up.
Ensure that no other MUX is running on the host and that no other process is using
the MUX port:
netstat -a | grep 7701
2. Enter one of the following commands:

System V:
ps -ef | grep mux
Berkeley:
ps ax | grep mux
If neither command returns anything, try to start the MUX again.

Troubleshooting
Translation
This section describes how to troubleshoot the translation server that is used to
translate CAD files into visualization files (for example, JT and JPEG). It also
describes how to troubleshoot the translation service that handles the translation
requests between Enterprise Knowledge Management and the translation server.
For translation troubleshooting specific to the rich client, see the documentation
for the rich client.
Error-free translation is entirely dependent on proper installation and setup. See
the following for installation or troubleshooting information:
• For information about setting up the translation environment, see chapter 12,
Setting Up Translation Environment.
• For more information about troubleshooting translation, see the Troubleshooting

Translation appendix in the Translation Solution Toolkit Installation Guide.
You can also use the flowchart in figure to isolate a problem to the proper area.

Teamcenter Enterprise
Translation Failure
Teamcenter Translation After reconfiguring

Enterprise Service
Does the model get Does the model get Does the service
successfully submitted from successfully submitted from start up and connect without
the Classic Client Prepare Yes the service to the translation No errors to the translation server?
Visualization action? server?
Yes
After
After reconfiguring 2
reconfiguring
No Yes
No
This problem may be that some/all of
the required c9 translation
1 components are not installed and/or Does the failure This problem may be that the service
occur after the generated files is not configured properly in
properly configured. Yes
get returned to the translation
TranslationService.config.
service?
No
Translation 2
Server
Can you log in to

the admin client without any Can the failed file be The file should work when submitted
errors in the startup window? Yes translated from within the admin Yes
from Teamcenter Enterprise to the
client? translation server.
After
reconfiguring
No No
The entered URL is incorrect or the

translation server is not configured Does the admin client test
No model translate to zip file?
correctly. Properly configure the
translation server.
Yes
Translator
After reconfiguring
The translator may not configured

Can the failed file be manually Do other models translate? properly. Reconfigure the translator.
translated? No No
Yes Yes
The file should work when submitted This may be a true translator failure
from Teamcenter Enterprise. If the that needs to be resolved by the
translation still fails, the problem may translator company.
1 be with the translation service or the
Teamcenter Enterprise configuration.
Figure B-1. Translation Troubleshooting Flowchart

Troubleshooting
Troubleshooting Enterprise Knowledge Management Configuration

If you have verified that the translation server and translation service are running
without errors, and that the translators are set up properly, then the problem could
be with how your translation configuration control objects are set up. Translation
configuration control objects control how Enterprise Knowledge Management
submits jobs to the translation service.
It is very important that these objects are set up correctly. For information about
how to set up translation configuration control objects, see chapter 12, Setting Up
Translation Environment.
There are a few settings to watch out for in these objects:
• The Staging Directory Path and Generated Visualization File Staging Directory
must point to valid Enterprise Knowledge Management work locations.
• When you are using the translation service, the Translation Script Name must
list the runtranslationService.sh file, and the Translation Script Path must
contain the path to that file.
• The Is Translatable? field should be set to True.
• If you want to have translation occur at checkin, the Tesselation on Checkin?

field must be set to True.
Perform the following steps to debug the Enterprise Knowledge Management

configuration:
1. Review the translation configuration control object created for the translation.
To find these objects in the classic client, pull down the Query menu and choose
the following options:
Translation Services Translation Task
2. To test the translation without checkin, place a CAD part into your work location
and register it. Then select the CAD part, pull down the Action menu, and
choose the Prepare Visualization Files option.
If translation is successful, visualization files are created and placed into the
vault and vault location specified in the translation configuration control object.
However, visualization and preview files relationships are not created with
any associated Enterprise Knowledge Management assemblies. In this case,
you must create the has visualization files and has preview files relationships
yourself.
If translation is not successful, open the translation services prompt and view
the progress messages. You can also look at the MTI log files in the logs directory
to look for error messages. Review the translation configuration files and your
Enterprise Knowledge Management setup for problems.
3. To test translation at checkin, first ensure that the Tesselation on Checkin?

field is set to true in the translation configuration control object for the type of
CAD part you want to translate.
Place a CAD part into your work location and register it, attach the CAD part to
an assembly, and check in the assembly with the attached part.

If translation is successful, visualization files are created and placed into the
vault and vault location specified in the translation configuration control object.
In addition, the proper visualization and preview file relationships are created.
If translation is not successful, open the translation services prompt and view
the progress messages. You can also look at the MTI log files in the logs directory
to look for error messages. Review the translation configuration files and your
Enterprise Knowledge Management setup for problems.
4. Review the translation task XML file created for each translation. This XML
file is placed in the directory where translation files are downloaded (specified
by the DownloadDir= value in the TranslationService.config file.) These
XML files contain information about the CAD files, requested translation, files
names, and other information needed for the translation. These files can be
useful in tracking down problems.
5. Review the tesselation request objects created for each translation. Pull down
the Query menu and choose the following options:
Translation Services Translation Task
If a translation request completes, the Request Status on the object is
COMPLETE_STATUS. If translation does not complete, it has another status,
such as NEW_STATUS. Take steps to correct the problems that led to the
translation failure, then rerun the translation. To rerun translation, select the
tesselation request object for that translation, pull down the Action menu, and
choose the following options:
Translation Admin Actions→Restart Processing
For more information about translation administration, see the Administrator’s
Manual for Parts and Documents.
Search Engine Server

This section provides steps to take if you encounter problems installing or
configuring the search engine.
Search Engine Cannot Start

If the search engine installation succeeds but the search engine
cannot start, check the search engine’s service log file, located in the
MTI_ROOT/autonomy/search-engine-name/IDOL/service.log file. If the port
numbers assigned to the search engine are in use by another program, the
service.log file contains a message similar to the following:
SERVICE: Service Control Thread couldn’t bind to port host 9063. Check that
the port is not already in use and ServiceHost is set correctly (if set).
If you determine the search engine port numbers conflict with another program,
perform the following procedures:
1. Change the port numbers for your search engine in the Configuration Editor
using the same method you used to configure in the search engine initially.

Troubleshooting
2. Close the Configuration Editor.
3. If your search engine is installed on a local area or work group server, copy
all files in the MTI_ROOT/install/hosts/target-host-name directory on the
corporate server to the MTI_ROOT/install directory on the local area or work
group server. (Replace target-host-name with the host name of the local area or
work group server.) Use any file transfer method (such as FTP2 or Network
Neighborhood) to transfer files.
The MTI_ROOT/install/hosts/target-host-name directory contains configuration
files for the server.
Perform the remaining steps in this procedure on the search engine server host.
4. In a plain text editor, open the MTI_ROOT/autonomy/

search-engine-name/IDOL/search-engine-name.cfg file.3 (Replace
search-engine-name with the name of the search engine for which you modified
search engine port information.) Edit the file as follows:
• Locate the [SERVICE] tag. Change the SERVICEPORT value to the new
value you entered for the Service Port in the Configuration Editor.
• Locate the [SERVER] tag:

– Change the INDEXPORT value to the new value you entered for the
IDOLI Port in the Configuration Editor.
– Change the SERVICEPORT value to the new value you entered for the
IDOLS Port in the Configuration Editor.
– Change the PORT value to the new value you entered for the IDOLA
Port in the Configuration Editor.
5. Save the search-engine-name.cfg file and close the text editor.
6. Start the search engine by entering the following commands:

cd MTI_ROOT/bin
drestart search-engine-name
The search engine service displays message indicating the service startup has
been initiated.
Search Engine Installation Fails

If the search engine installer does not launch successfully, the installer displays a
message that identifies the problem encountered. If this occurs, perform whatever
steps are necessary to correct the error and then relaunch the installer by performing
is available on your local host or network.
2. If you use FTP, make sure you set the file transfer mode to ASCII.
3. By default, the search engine is named DREn, for example, DRE1.

2. Source the MTI_ROOT/config/pdmsetup file to set Enterprise Knowledge

Management environment variables.
4. Enter the following command to launch the search engine installer:

./insautonomy
5. If the installation is successful, the installer automatically starts the search

engine service and displays the following message:
The search engine service displays message indicating the service startup has
been initiated.
Database Configuration
This section provides steps to take if you encounter problems affecting database
interaction with Enterprise Knowledge Management.
Structured Query Language Utility (msql) Cannot Log In

After you start the dispatcher, you may receive the following error:
msql (-19) Error occurred
This error occurs for one of the following reasons:

• The database is not available and running. Make sure the database is available
and running.
• One of these values is not accurate:

– The PWF configuration variable.
– The DDB Default value.
Ensure that the PWF configuration variable and the DDB Default value (in the
Configuration Editor’s Modify Enterprise Knowledge Management Database
dialog window) are set to the correct values.
• The file specified by the PWF configuration variable is corrupt or is not valid.
Remove or rename the file and unset the PWF configuration variable.

Troubleshooting
Recovering an Oracle Instance From Deleted Data Files

After deleting data files, you must make changes to Oracle. The following procedure
outlines this process. If you need additional information about any of these steps,
refer to your Oracle documentation.
From SQL*DBA, enter the following commands:
shutdown immediate
startup mount
alter database datafile missing-file-path offline drop;
shutdown immediate
startup open
drop tablespace table-name
Replace missing-file-path with the path name of the missing file and replace
table-name with the table name of the deleted data file.
Oracle Timeout Connection Dropped

If you receive the oracle time-out connection dropped error while running the
database server (msql) and Oracle Net, you can increase the time out parameter
in the listener.ora file4 for the host on which the database server is timing out.
The following example shows how to bring down the Oracle Net listener, change
the parameter, and restart the listener. The next msql server you start connects
to the updated listener.
lsnrctl stop LISTENER
Change the default value of 10 to 60 in listener.ora:

CONNECT_TIMEOUT_LISTENER_HOST1 = 60
Restart the listener:

lsnrctl start LISTENER
4. This file is in the $ORACLE_HOME/network/admin directory.

Appendix
C Oracle Reference
How the Configuration Editor Creates an Oracle User . . . . . . . . . . . . . . . . . . C-1
Oracle Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Oracle Net Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . C-1
queuesize Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
SDU and TDU Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
listener.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
tnsnames.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
tcp.nodelay Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
break_poll_skip Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Oracle Distributed Setup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4

Oracle listener.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Oracle sqlnet.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Oracle tnsnames.ora File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Utility Program Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Sample Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7

Appendix
C Oracle Reference
This appendix provides additional information about using Enterprise Knowledge

Management with Oracle.
How the Configuration Editor Creates an Oracle User

Before you run the Enterprise Knowledge Management installation utility, you must
decide whether to create Enterprise Knowledge Management databases yourself or
let the Configuration Editor create them for you. Figure C-1 shows an example of
how the Configuration Editor creates an Oracle user1 and tablespace. If the method
does not meet your site’s specifications, create the Oracle user or users yourself
before you run the installation utility.
create tablespace USERspace datafile

’oracle data file location/USERspace.dbf’ size 60M reuse;
create user USER identified by oracle

default tablespace USERspace
temporary tablespace USERspace
quota unlimited on USERspace;
grant connect to USER;
alter user USER default role all;
Figure C-1. Sample Program for Creating an Oracle User
Oracle Performance Tuning

This section provides information needed to optimize Oracle performance for
Oracle Net Performance Considerations

Oracle Net connections between servers can be tuned using the parameters listed in
table C-1 to improve Oracle Net throughput. Tuning these parameters affects the
performance of the Oracle Net layer only.
1. Recall that Enterprise Knowledge Management databases are Oracle users.
MT00300 L3 Installation on UNIX and Linux Servers C-1

Appendix C Oracle Reference
Table C-1. Contents of Oracle Parameter Files

Parameter File Parameters
listener.ora SDU, TDU, queuesize
protocol.ora tcp.nodelay
sqlnet.ora break_poll_skip
tnsnames.ora SDU, TDU
In addition to Oracle performance tuning, network performance tuning may be

needed by your network administrator. Settings in the parameter files in table
C-1 can affect the frequency and size of packet shipping across the network.
The following sections describe the parameters in table C-1.
queuesize Parameter
The queuesize is set in the listener.ora file.
If you want the listener to handle large volumes of concurrent connection requests,
you can specify a listener queue size for its TCP/IP or IPC listening end points. The
default number of concurrent connection requests is operating-system specific. On
Solaris platforms, for example, the default is 5. On Windows servers, the default
is 50, and on Windows workstations, the default is 5.
This parameter is used only for very high-volume databases, where the listener
spawns thousands of connections per hour. The number of expected simultaneous
connections should be equal to the size of the queuesize parameter. The following
example shows the queuesize parameters setting in the listener.ora file:
LISTENER =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = omf10g)
(PORT = 1521)
(QUEUESIZE = 32)
)
)
A consideration when setting this parameter is that it preallocates resources for

anticipated requests, therefore using more system memory and resources.
SDU and TDU Parameters

The session data unit (SDU) and transport date unit (TDU) parameters are set in
the listener.ora and tnsnames.ora files. SDU specifies the size of the packets to
send over the network. Ideally, SDU should not surpass the size of the maximum
transmission unit (MTU). MTU is a fixed value that depends on the actual network
implementation used. Oracle recommends that SDU be set equal to MTU.
The TDU is the default packet size used within Oracle Net to group data together.
The TDU parameter should ideally be a multiple of the SDU parameter. The default
value for SDU and TDU combined is 2048, and the maximum value is 32767 bytes.
The following considerations apply when setting SDU and TDU:
C-2 Installation on UNIX and Linux Servers MT00300 L3

Oracle Reference
• Do not set SDU greater than TDU. Doing so wastes network resources by
shipping wasted space in each packet.
• If your users connect via dial-up modem lines, consider setting SDU and TDU
to smaller values because of the frequent resends that occur over modem
connections.
• On fast network connections (T1 or T3 lines), you should set SDU and TDU
equal to the MTU value for your network. On standard ethernet networks,
the default MTU size is set to 1,514 bytes. On standard token ring networks,
the default MTU size is 4,202 bytes. The SDU and TDU settings are a direct
function of the connection speed between the hosts. For fast T1 lines, set SDU,
TDU, and MTU to the same value. For slower modem lines, experiment with
smaller values of SDU and TDU.
The following examples show these parameters on a token ring network with an
MTU of 4202 bytes:
listener.ora
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SDU = 4202)
(TDU = 4202)
(SID_NAME = ora10g)
(GLOBAL_DBNAME = ora10g.WORLD)
)
)
tnsnames.ora
ORCL.WORLD =
(DESCRIPTION =
(SDU=4202)
(TDU=4202)
(ADDRESS =
(PROTOCOL = TCP)
(HOST = omf10g)
(PORT = 1521)
)
(CONNECT_DATA = (SID = ora10g))
)
tcp.nodelay Parameter
The tcp.nodelay parameters is set in the protocol.ora file.

Oracle Net, by default, waits until the buffer is full before transmitting data.
Therefore, requests are not always sent immediately to their destinations. This is
most common when large amounts of data are streamed from one end to another,
and Oracle Net does not transmit the packet until the buffer is full. Adding a
protocol.ora file and specifying a tcp.nodelay to stop buffer flushing delays can
remedy this problem.

The protocol.ora file can be specified to indicate no data buffering for all TCP/IP
implementations. The parameter can be used both on the client and server. The
tcp.nodelay setting in protocol.ora is as follows:
tcp.nodelay = yes
Specifying this parameter causes TCP buffering to be skipped so that every request
is sent immediately. Keep in mind, however, that network traffic can increase due
to smaller and more frequent packet transmission, therefore causing slowdowns in
the network.
Set the tcp.nodelay parameter only if you encounter TCP timeouts. Setting
tcp.nodelay can provide significant performance improvement in high-volume
traffic between database servers.
break_poll_skip Parameter
The break_poll_skip parameter is set in the sqlnet.ora file.
This client-only sqlnet.ora parameter indicates the number of packets to be skipped
before checking for a user-initiated break. This parameter affects the amount of
CPU resources used by the Oracle Net client and functions only with servers that
support in-band breaks. The default value is four, and the results of modifying
the value are as follows:
• The higher you set the break_poll_skip value, the less frequently the system
checks whether control-c is pressed, and the less CPU resources are consumed.
• Conversely, the lower the value is set, the more frequently the system checks for
control-c and the more CPU resources are consumed.
Oracle Distributed Setup Files

This section contains examples of the Oracle listener.ora, sqlnet.ora, and
tnsnames.ora files.
Oracle listener.ora File

The listener.ora file is the configuration file of the Oracle Net background process
call translator. The following file examples for Oracle 9 and Oracle 10 systems
contain the system-specific values shown table C-2. If you use these files, replace
these values with values that reflect your system.
Table C-2. Parameters in Sample listener.ora Files

LISTENER_HOST1 Listener name.
host1 Host running Oracle and the listener process.
1521 Listening port number.
sid1 Oracle system identifier (SID).
sid1_tcp tnsname for this instance.
/usr/oracle Oracle home directory.

Oracle Reference
File Example for Oracle 10g:

A version 10 listener is required for an Oracle Database 10g database.
Previous versions of the listener are not supported for use with an Oracle
Database 10g database. However, it is possible to use a version 10 listener
with previous versions of the Oracle database.
###########
# LISTENER.ORA Network Configuration File:
# /db/app/oracle/product/10.1.0/network/admin/listener.ora
# Generated by Oracle configuration tools.
###########
LISTENER_HOST1 =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = host1)
(PORT = 1521)
(QUEUESIZE=20)
)
(ADDRESS =
(PROTOCOL = IPC)
(KEY = sid1)
)
)
SID_LIST_LISTENER_HOST1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = sid1.world)
(ORACLE_HOME = /db/app/oracle/product/10.1.0)
(SID_NAME = sid1)
)
)
TRACE_LEVEL_LISTENER_HOST1 = OFF
TRACE_FILE_LISTENER_HOST1 = listener_sid1.trc
TRACE_DIRECTORY_LISTENER_HOST1 = /db/app/oracle/product/10.1.0/network/log
Oracle sqlnet.ora File

The Oracle sqlnet.ora file is a trace configuration file for Oracle Net. Use this file
to debug Oracle Net if you have a problem with Oracle communication between
hosts using Oracle Net.


Configure local naming as the first method specified in the
NAMES.DIRECTORY_PATH parameter in the sqlnet.ora file. This
parameter specifies the order of naming methods Oracle Net uses to resolve
connect identifiers to connect descriptors.
###########
# FILENAME: sqlnet.ora
# NETWORK.: Siemens PLM Software
###########
NAMES.DIRECTORY_PATH= (TNSNAMES)
NAMES.DEFAULT_DOMAIN = world
TRACE_LEVEL_CLIENT = OFF
TRACE_FILE_CLIENT = ora_client.trc
TRACE_LEVEL_SERVER = OFF
TRACE_FILE_SERVER = ora_server.trc
Oracle tnsnames.ora File

The Oracle tnsnames.ora file is the configuration file used to identify all the Oracle
Net connections in your network. A TNS alias name must be given to every Oracle
instance that you want to communicate with in your network. These aliases must
be unique across the network.
The following file examples for Oracle 9 and Oracle 10 systems contain the
system-specific values shown table C-3. If you use these files, replace these values
with values that reflect your system.
Table C-3. Parameters in Sample tnsnames.ora Files

host1 Host running Oracle and the listener process.
sid1_tcp.world Unique alias names.
sid2_tcp.world
sid3_tcp.world
TCP Communication protocol.
1521 Listening port numbers.
1523
1527

Oracle Reference

############
# FILENAME: tnsnames.ora
# NETWORK.: Siemens PLM Software
###########
sid1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = host1)
(PORT = 1521))
)
(CONNECT_DATA =
(SID = sid1)
(SERVER = DEDICATED)
)
)
Utility Program Descriptions

This section describes utility programs used during Enterprise Knowledge
bldrora
Loads objects from a load file into the database.
rulefile
Regenerates the rules cache.
credbora
Creates or drops databases.
For complete descriptions of these utilities, see the Network and Database
Sample Startup Files

This section describes how to use the sample UNIX startup files provided with
Enterprise Knowledge Management provides sample .login and .profile UNIX
startup files. To ensure your environment contains all variables required for
Enterprise Knowledge Management, you can edit one of these sample files to reflect
your corporate server or you can copy the significant portions into your existing
startup file.
When you copy Enterprise Knowledge Management installation files in chapter
5, Preparing the Enterprise Knowledge Management Environment. these sample
startup files are copied to your MTI_ROOT/install directory as _login and _profile.
Edit the appropriate file to reflect your system, then save the file as the .login or
.profile file for the Enterprise Knowledge Management trusted user.
When editing sample startup files, observe the following considerations:

• The sample .login file and .profile files allow all users to access the Enterprise
Knowledge Management software. If you previously restricted access by creating
a special group for the Enterprise Knowledge Management software, you need to
use a more restrictive umask command.
• All references to Oracle apply only if you are installing one or more Enterprise
Knowledge Management databases on this host.
• Do not set the csh noclobber option in either your .login or .cshrc file.
• If your startup file modifies the PATH environment variable, make sure the
Oracle coraenv command is the last command in your startup file:
Figures C-2 and C-3 show the sample .login and .profile files provided with
#!/bin/csh
# .login file for Teamcenter Enterprise trusted user
# bcprt
# This software and related documentation are proprietary to UGS Corp.
# COPYRIGHT 2005 UGS CORP. ALL RIGHTS RESERVED
# ecprt
###########################################################
Please note - you can not use this file as-is. You must
edit it to reflect your environment.
Areas requiring special attention are bracketed with << >>
###########################################################
set path = ( . $path <<X11 and other favorite directories>> )
# Allow all users to access the Teamcenter Enterprise software.
# Use a value such as "27" to restrict access to the group.
umask 22
### ORACLE SECTION
# Need ORACLE only if installing a database server
setenv ORACLE_HOME /usr/<<change to your oracle home>>
setenv ORACLE_SID <<change to your oracle sid>>
setenv DB_VENDOR ORA
# If you are on the machine where Oracle is installed
set path=($path $ORACLE_HOME/bin )
set ORAENV_ASK=NO
unset ORAENV_ASK
setenv ORACLE_AUTOLOGIN 0
# Else If you are accessing oracle thru sqlnet
setenv TWO_TASK <<change to your two task alias>>
###########################################################
Please note: The following lines should be uncommented as
soon as the installation is complete
###########################################################
#if ( -f <<change to Teamcenter Enterprise Home>>/config/pdmsetup ) then
# source <<change to Teamcenter Enterprise Home>>/config/pdmsetup
#endif
Figure C-2. Sample .login file

Oracle Reference
#!/bin/sh
# .profile file for Teamcenter Enterprise trusted user
# bcprt
# This software and related documentation are proprietary to UGS Corp.
# COPYRIGHT 2005 UGS CORP. ALL RIGHTS RESERVED
# ecprt
##########################################################
Please note - you can not use this file as-is. You must
edit it to reflect your environment.
Areas requiring special attention are bracketed with << >>
##########################################################
PATH=.:<X11 and other favorite directories>;
export PATH
# Allow all users to access the Teamcenter Enterprise software.
# Use a value such as "27" to restrict access to the group.
umask 22
### ORACLE SECTION
# Need ORACLE only if installing a database server
ORACLE_HOME=/usr/<<change to your oracle home>>
export ORACLE_HOME
ORACLE_SID=<<change to your oracle sid>>
export ORACLE_SID
DB_VENDOR="ORA"; export DB_VENDOR
# If you are on a mchine where Oracle is installed
PATH=$PATH:$ORACLE_HOME/bin
ORAENV_ASK=NO
. $ORACLE_HOME/bin/oraenv
unset ORAENV_ASK
ORACLE_AUTOLOGIN=0; export ORACLE_AUTOLOGIN
# Else If you are accessing oracle thru sqlnet
TWO_TASK=<<change to your two task alias>>
export TWO_TASK
###########################################################
Please note: The following lines should be uncommented as
soon as the installation is complete
###########################################################
#if [ -r <<change to Teamcenter Enterprise Home>>/config/pdmsetup.sh ]; then
# . <<change to Teamcenter Enterprise Home>>/config/pdmsetup.sh
#fi
Figure C-3. Sample .profile file

Appendix
D Installing and Running

Enterprise Knowledge
Management Using NFS
Client/Server Trust . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
MUX Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
olaunch Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Sockets and FIFOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Running netstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Running the MUX and Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Appendix
D Installing and Running

Enterprise Knowledge
Management Using NFS
This appendix contains information about installing and running Enterprise

Knowledge Management using the Network File System (NFS).
You can install Enterprise Knowledge Management on an NFS server and execute
its binaries from an NFS client. This appendix describes installation issues that you
must accommodate in your Enterprise Knowledge Management deployment strategy
when installing Enterprise Knowledge Management in an NFS environment.
Client/Server Trust
The Enterprise Knowledge Management installation procedure assumes that
read/write access and complete trust exists between the NFS client and server. Keep
the following points in mind if you install Enterprise Knowledge Management in an
NFS environment where there is less trust between client and server:
• You must perform some installation steps manually.
• Installing Enterprise Knowledge Management in an environment where no

trust exists between client and server affects some Enterprise Knowledge
Management functions and can result in reduced functionality and decreased
performance.
• To run from a read-only mount, you must adjust your Enterprise Knowledge
Management configuration.
• When running the Enterprise Knowledge Management installation procedure on

an NFS client host, the NFS server must trust the NFS client’s root privileges
as defined in the server’s /etc/exports directives (–root=host1:host2:hostn).
This assumption is built into the root.sh file, which expects to run as root
on the NFS client.
The root.sh file attempts to change the ownership and mode of muxd (called
the MUX) and olaunch (installed onto the NFS server) to be set-UID programs
owned by root.
MT00300 L3 Installation on UNIX and Linux Servers D-1

Appendix D Installing and Running Enterprise Knowledge Management Using NFS
If you want to install Enterprise Knowledge Management on an NFS client

whose root privileges the NFS server does not trust, you must manually perform
the commands that root.sh automates and you must perform some of these
commands on the NFS server instead of the NFS client. For more information
about the root.sh file, see the sample shown in figure D-1.
#!/bin/sh
# Setting File protections for Enterprise Knowledge Management 2007
# make muxd and olaunch set-uid root for securitycd MTI_ROOT/bin || exit $?
echo "Setting muxd file protections"
if [ -f muxd ] ; then
chown root muxd || exit $?
chmod 4755 muxd || exit $?
fi
echo "Setting olaunch file protections"
if [ -f olaunch ] ; then
chown root olaunch || exit $?
chmod 4755 olaunch || exit $?
fi
echo "Copying olaunch security file to /etc"
if [ -f /etc/olaunch.usr ] ; then
cd MTI_ROOT/install || exit $?
cp /etc/olaunch.usr olaunch.usr.old || exit $?
sort -u olaunch.usr.old olaunch.usr > /etc/olaunch.usr || exit $?
else
cp MTI_ROOT/install/olaunch.usr /etc/olaunch.usr || exit $?
fi
test -f apcroot.sh && . apcroot.sh
test -f ccmroot.sh && . ccmroot.sh
test -f dmmroot.sh && . dmmroot.sh
test -f iscroot.sh && . iscroot.sh
test -f lcmroot.sh && . lcmroot.sh
test -f pfmroot.sh && . pfmroot.sh
test -f psmroot.sh && . psmroot.sh
test -f tktroot.sh && . tktroot.sh
test -f wwwroot.sh && . wwwroot.sh
echo Completed root.sh successfully.
Figure D-1. Sample root.sh File
MUX Considerations
Enterprise Knowledge Management uses privileges in the MUX to acquire a
reserved TCP port number for outgoing connections. This serves as a signal to other
MUX programs that it is trustworthy (since under UNIX, only a privileged process
can make an outgoing connection from ports numbered lower than 1024). For more
information about assigned port numbers, see the TCP/IP standards document
RFC 1700, Assigned Numbers.
If the MUX does not have privileges, it can perform TCP communications
only if the VC_MUX_RESERVED_IPPORT_REQUIRED configuration
variable has a value of 0 (the default value is 1; you can change it in the
Configuration Editor). This variable must be set consistently throughout an
Enterprise Knowledge Management installation; you will encounter problems
if VC_MUX_RESERVED_IPPORT_REQUIRED is set to 1 on some hosts in
your installation and 0 on other hosts. For more information about configuration
variables, see the Network and Database Configuration Guide.
olaunch Considerations
Enterprise Knowledge Management uses privileges in olaunch to start the
operating system server (OS_SERV) and the GUI server as certain OS users. The
ability to start an operating system server as another user is an important part of
the way Enterprise Knowledge Management accesses files. Enterprise Knowledge
D-2 Installation on UNIX and Linux Servers MT00300 L3

Installing and Running Enterprise Knowledge Management Using NFS
Management is always able to start an operating system server on the NFS client
host as the user logged in to the OMF client on that host; however, if Enterprise
Knowledge Management cannot start operating system servers as another OS
user, the person on that host may have limited access to other users’ files. If you
define Enterprise Knowledge Management file systems to include access from these
clients, you may need to allow anonymous (nobody) access to work/vault locations
and staging areas.
Siemens PLM Software does not recommend this configuration because
it allows (accidental or deliberate) destruction of the contents of these
directories, defeating one of the larger benefits of collaborative product
management technology.
The need for the ability to start a GUI server is related to application interfaces
running on the client host, and is an issue only if the user is not running the OMF
client when an application interface needs to interact with the user.
The root.sh file generated by the Enterprise Knowledge Management installation
procedure adds the operating system username of the trusted user to the
/etc/olaunch.usr file. This is optional. If you set up olaunch to run as a set-UID
program owned by root, and the olaunch.usr file does not exist, any user on
that host can invoke olaunch and it can invoke any command as any user. To
restrict which users can invoke it, and increase the security on the host, place the
appropriate operating system user names in this file, one per line. For additional
information about olaunch access permissions, see Restricting Access to the Server
Launching Program in chapter 7, Configuring Enterprise Knowledge Management.
Sockets and FIFOs

If you set up the MUX (muxd) as a set-UID program owned by root, and clients in
your NFS environment do trust NFS servers to honor this when executing programs
from the NFS server, the NFS server must trust the NFS client’s root privileges.
When the MUX is set up as a set-UID program owned by root, it attempts to create
a UNIX-domain socket or FIFO on the NFS server owned by root for a split-second
before its ownership is changed to the real user who started the MUX (normally the
Enterprise Knowledge Management trusted user on the NFS client).
If the MUX is unable to create this socket or FIFO, it aborts. You can control the
location of this file, and if you put it on the NFS client, it removes the need for the
server to trust the client. This is a good idea in an NFS environment because socket
and FIFO files cannot be meaningfully shared between client and server. Putting
them in a location shared over the network invites confusion. If you intend to
restrict the NFS client to read-only access of the Enterprise Knowledge Management
installation on the NFS server, you must change the configuration to put the
socket and FIFO in a local directory. Putting them in a shared location on the NFS
server does not accomplish network sharing—you still need to start the MUX and
dispatcher on the client host.
Socket and FIFO files are controlled by Enterprise Knowledge Management
configuration variables:
• VC_MUX_SOCK for sockets.
• VC_MUX_FIFO for FIFOs.
MT00300 L3 Installation on UNIX and Linux Servers D-3

Appendix D Installing and Running Enterprise Knowledge Management Using NFS
A MUX running on UNIX uses only one of these variables. Depending on the
platform (and for future compatibility) Siemens PLM Software recommends that you
change both variables.
When you change the VC_MUX_FIFO or VC_MUX_SOCK variables, consider
the following:
• The Enterprise Knowledge Management installation procedure places these
files under MTI_ROOT in order to separate and protect them. The socket and
FIFO files are unique to a particular Enterprise Knowledge Management
installation. If you are running more than one version of Enterprise Knowledge
Management on the host, placing these files in MTI_ROOT means they are
naturally separated. Alternatively, you can concatenate characters to the names
to make them unique. Placing them in MTI_ROOT also protects them from
inadvertent destruction which is more likely in a shared location such as /tmp.
• If you place the files in a shared location, make sure that automated and manual
maintenance of this directory does not destroy them. If these files are removed
while the MUX is running, the MUX does not abort but appears to have died
when anyone attempts to connect to it on the local host. Existing clients are not
affected, only new ones. The typical symptoms in this case are that muxstat
reports the MUX is unavailable, yet muxstart fails. You should be able to find
the MUX (shown as muxd) in the ps(1) output and confirm that it is functioning
normally by entering a muxping command from another host.
• When considering where to locate the socket and FIFO files, remember that
these files must be writable by every Enterprise Knowledge Management user,
so they must be in a directory that permits this.
Running netstart
When starting Enterprise Knowledge Management using the netstart command
from a shared directory, you must either modify it to separate the log files it produces
on a host basis (such as including the host name in the name of each file) or have
procedures in place to ensure they are separated.
The netstart log files are not designed to be shared among multiple hosts while they
are active. They are formatted to allow combining them after they are inactive. If
the NFS client does not have write access to the NFS server, you must either modify
the netstart script or create a procedure that stores the netstart log files locally.
Running the MUX and Dispatcher

Depending on the status of the NFS client host, you can have the primary user
be responsible for starting the MUX and dispatcher as necessary, rather than
automating this in the system startup script. If the host does not contain registered
Enterprise Knowledge Management shared file locations (vault locations or staging
areas), any user can start the MUX and dispatcher. If the MUX is not set up as a
set-UID program owned by root, you must either adjust file permissions where the
socket or FIFO is located to allow anyone to create it, or change the configuration
to put it somewhere publicly writable.
D-4 Installation on UNIX and Linux Servers MT00300 L3

Appendix
E Installing Maintenance Packs
Downloading a Maintenance Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Installing Maintenance Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Using Maintenance Pack Manager Options . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

Modifying Patch Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
Managing Download Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
Viewing Maintenance Pack Information . . . . . . . . . . . . . . . . . . . . . . . . . E-4
Uninstalling and Reinstalling Maintenance Packs . . . . . . . . . . . . . . . . . . E-4
Removing Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4
Manually Configuring Download Locations . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

Downloading Maintenance Packs Manually . . . . . . . . . . . . . . . . . . . . . . . E-5
Using a Patch Repository Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7
Patching Enterprise Knowledge Management Thin Client and Rich Client

Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-8

Appendix
E Installing Maintenance Packs
This appendix describes how to install Enterprise Knowledge Management

product patches. Enterprise Knowledge Management patches are distributed as
maintenance packs and are installed using the Maintenance Pack Manager.
The Maintenance Pack Manager installs product patches on managed Enterprise

Knowledge Management server and client hosts. The procedures in this appendix
apply to all Enterprise Knowledge Management hosts except where otherwise noted.
Downloading a Maintenance Pack

To download a maintenance pack:
1. Launch the Maintenance Pack Manager by changing to the MTI_ROOT/patching
directory and entering the following command:
mpm
On the corporate server, you can also launch the Maintenance Pack
Manager from the Configuration Editor by clicking Maintenance Pack
Manager.
2. To download a maintenance pack, click Download Maintenance Pack.

This button is enabled only if you have defined patch server settings. If you have
not defined patch server settings, proceed to step 3.
3. In the Modify Patch Server Settings dialog window, enter patch server settings
as described in table E-1.
Table E-1. Patch Server Settings

Field Description
Patch Server Name Specifies the host name or URL to the patch
server. The default value is the URL to the
patch server on GTAC (ftp.ugs.com).
Port Number Specifies the port number used by the
Maintenance Pack Manager. The default
value is 21.
MT00300 L3 Installation on UNIX and Linux Servers E-1

Appendix E Installing Maintenance Packs
Table E-1. Patch Server Settings

Field Description
Content File Location Specifies the relative path to the directory on
the patch server that contains content files1
for the maintenance pack. The default value is
the designated path on the GTAC server that
contains maintenance packs for Enterprise
Knowledge Management 2007. If you use the
patch server on GTAC, do not change this
value.
User Name Specifies the user name for the Siemens PLM
Software WebKey account you use to download
patches.
Password Specifies the password for the Siemens PLM
Software WebKey account you use to download
patches.
4. In the Download Maintenance Pack dialog window, choose a maintenance pack

from the Maintenance Pack to Download list.
If you want to download the maintenance pack to a directory other than the path
specified in the Download Location field, enter the directory you want to use.
5. Select the types of patch sets you want to download (managed host2, thin client,
or rich client) and the platforms for the maintenance pack you want.
6. Click OK. The Maintenance Pack Manager downloads the specified maintenance
pack.
Installing Maintenance Packs

The following patch sets cannot be installed using the Maintenance Pack
Manager:
• Thin client or rich client patch sets.
Install these patch sets according to the instructions in Patching
Enterprise Knowledge Management Thin Client and Rich Client Solutions,
later in this appendix.
• INSTALL_BASE
INSTALL_WINCLNT
INSTALL_WEBPD
INSTALL_PATS
1. Content files are text files that contain paths to the patch set files on the patch server. Content files are named
product-id_package-id_CONTENTS.txt.
2. Managed hosts are hosts known to the Enterprise Knowledge Management network, such as server hosts and workstation (classic
client) hosts.
E-2 Installation on UNIX and Linux Servers MT00300 L3

Install these patch sets according the to instructions in the readme files
that accompany them.
To install a maintenance pack you downloaded using the Maintenance Pack

Manager, perform the following steps:
Some Linux platforms do not include the compress utility, which is required
by the Teamcenter installation scripts while installing patches. Ensure
that you have a compress utility and include the path to this utility before
installing patches on the Linux platform.
1. Click Install Maintenance Pack.
2. Choose a download type.

In the Install Maintenance Pack – Choose Download Type dialog window, select
Maintenance Pack Manager.
If you download maintenance packs manually, see Downloading
Maintenance Packs Manually, later in this appendix.
3. Choose a maintenance pack to install.

If you do not want to back up files replaced in the patching process, deselect
Backup Current Installation. If you want to back up files to a directory other
than the Backup Location shown, enter a different directory.
4. Click OK. The Maintenance Pack Manager installs the selected maintenance
pack.
Using Maintenance Pack Manager Options

This section describes additional Maintenance Pack Manager options. Some of these
options are not enabled until after you download and install a maintenance pack.
Modifying Patch Server Settings

By default, the Maintenance Pack Manager is configured to use the patch server on
GTAC. To use a different patch server, click Modify Patch Server Settings. Enter
patch server settings as described in Downloading a Maintenance Pack, earlier
in this appendix.
If you want to restore patch server settings to their initial GTAC values, click
Restore GTAC Defaults.
Managing Download Locations

If you want to change or remove download locations for patch sets, click Manage
Download Locations. The Manage Download Locations dialog window displays a
table of download locations for each maintenance pack and platform.
If you want to move downloaded maintenance packs, you can manually move the
contents of a download location, then update the appropriate path in the Manage

Download Locations dialog window. The Maintenance Pack Manager does not move
maintenance pack files.
If you want to free disk space, you may remove downloaded maintenance packs by
selecting one or more locations and clicking Remove. This deletes the physical disk
locations and all files in them from your host.
If you remove the download location for the active maintenance pack on the
Maintenance Pack Manager host, you will not be able to reinstall the package
using the Reinstall Active Maintenance Pack option.3
Viewing Maintenance Pack Information

To view information about downloaded or installed maintenance packs, click View
Maintenance Pack Information. The View Maintenance Pack Information dialog
window allows you to view the synopsis, full description, or special instructions for
a selected maintenance pack.
To view information about a maintenance pack you have installed, click Installed
Maintenance Pack, then select the maintenance pack you want to view. Similarly,
to view information about maintenance packs that you have downloaded but not
installed, click Downloaded Maintenance Pack.
In the Viewing Maintenance Pack field, choose Synopsis, Full Descriptions, or
Special Instructions from the dropdown menu.
Uninstalling and Reinstalling Maintenance Packs

If you want to uninstall a maintenance pack and restore files backed up during the
patching process, click Uninstall Active Maintenance Pack.
If you suspect a maintenance pack was not successfully installed, you can reinstall
the active patch set by clicking Reinstall Active Maintenance Pack.
Removing Backups
To free disk space, you can remove backups of files replaced during maintenance
pack installations by clicking Remove Backups. In the Remove Backups dialog
window, select one or more backups to remove, then click OK.
If you remove the backup for the active maintenance pack on the Maintenance
Pack Manager host, you cannot reinstall the package using the Reinstall
Active Maintenance Pack option.
Manually Configuring Download Locations

This section provides additional options for downloading maintenance packs.
3. For more information about this option, see Uninstalling and Reinstalling Maintenance Packs, later in this appendix.

Downloading Maintenance Packs Manually

If you download a maintenance pack manually (not using the Maintenance Pack
Manager), you may install it using the Maintenance Pack Manager. For example,
if you download a maintenance pack directly from GTAC using FTP, or if you copy
a maintenance pack from another host in your network, install it by performing
the following procedures:
Download a maintenance pack manually:
1. Obtain the list of modules installed on your Teamcenter Enterprise server from
the MTI_ROOT/install/selected.dat file.
2. Create a directory for the maintenance pack you want to download. This
directory is referenced in this procedure as PKG-LOC.
3. Log in to the GTAC server using your WebKey account.

http://ftp.ugs.com/teamcenter_enterprise/patch/
4. Locate the following directory on the GTAC FTP site:

teamcenter_enterprise/patch/release-id/mpm
Download the contents file (release-id_package-id_CONTENTS.txt) from this
directory to your local PKG-LOC directory.
5. For each installed module you found in step 1, download and extract TAR files
for submodule patch sets:
a. For each submodule you want to patch, locate the following directory on
the GTAC FTP site:
teamcenter_enterprise/patch/release-id/module_submodule/package-id
b. Locate the appropriate TAR files for the platforms you use. Download the
files to your local PKG-LOC directory.
c. Extract the downloaded TAR files to your local PKG-LOC directory.

Extracting patch set TAR files creates a
release-id_module_submodule_package-id subdirectory that contains a
README file, a BOM file, and an image file (TZ for UNIX/Linux platforms).

For example, a patch set TAR file for Enterprise Knowledge

Management OMF module (OMF), client submodule
(CLNT), for UNIX/Linux platforms would be named
ReleaseVersion_OMF_CLNT_package-id_<platform>.tar. Extracting this
file would create a PKG-LOC/ReleaseVersion_OMF_CLNT_package-id
directory that contains the following files:
• ReleaseVersion_OMF_CLNT_package-id.README
• ReleaseVersion_OMF_CLNT_package-id_<platform>.BOM
• ReleaseVersion_OMF_CLNT_package-id_<platform>.TZ
After you extract the TAR file, you can delete the TAR file from the PKG-LOC
directory.
6. Create a download_locs.xml file in the MTI_ROOT\patching\mpm_files

directory and include the following parameters for this file.
This file is automatically generated if you use Maintenance Pack Manager
to automatically download and install patches.
• download-loc mp=: Set it to the version for which you have manually
downloaded the maintenance pack. For example, MP02.
• bucket=: Set it to the platform for which you have manually downloaded
the maintenance pack. For example, windows.
• dir=: Set it to the location where you have manually downloaded the patches.
For example, MTI_ROOT\patching\downloads\MP02\windows.
Sample download_locs.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<root>
<download-loc mp="MP02" bucket="windows" dir="MTI_ROOT\patching\
downloads\MP02\windows" />
</root>
Install a manually downloaded maintenance pack:

2. In the Install Maintenance Pack – Choose Download Type dialog window, select
Manual Process.
3. In the Download Location field, enter the path to the downloaded maintenance
pack or Browse to the download location.
4. Click OK.
5. In the Install Maintenance Pack – Manual Download dialog window, select

Maintenance Pack to Install.

If you do not want to back up files replaced in the patching process, deselect
Backup Current Installation. If you want to back up files to a directory other
than the Backup Location shown, enter a different directory.
6. Click OK to begin installing the selected maintenance pack.
Using a Patch Repository Server

If you want to conserve bandwidth by distributing downloaded maintenance packs
from a host in your network, you can set up a patch repository server by performing
Create the patch repository:

1. Designate a host for the patch repository server. This does not need to be an
Enterprise Knowledge Management managed host, but should be a host in the
same domain as the hosts you want to serve.
2. Create a patch repository directory, for example, patchrep.
3. Extract the INSTALL_BASE.TZ file from the Enterprise Knowledge

Management software distribution image to the patchrep directory.4
4. Delete the contents of the patchrep/install directory, but do not delete the
directory.
5. Copy the loaded.dat and selected.dat5 files from the MTI_ROOT/install

directory on the corporate server to the patchrep/install directory on the
patch repository host.
6. Download a maintenance pack as described in Downloading a Maintenance

Pack, earlier in this appendix.
7. Set permissions on the Download Location directory you specified so users can
copy files from this directory.
Install a maintenance pack from the patch repository:

1. Launch the Maintenance Pack Manager on a managed Enterprise Knowledge
Management host.
3. In the Install Maintenance Pack – Choose Download Type dialog window, select
Manual Process.
4. In the Download Location field, enter the path to the patch repository, then
click OK.
4. For more information about copying the INSTALL_BASE.TZ file, see Copying Installation Files in chapter 5, Preparing the Enterprise
Knowledge Management Environment.
5. These files provide information about the content of the corporate server to the Maintenance Pack Manager. The Maintenance Pack
Manager uses this information to determine which patch sets to download.

Patching Enterprise Knowledge Management Thin Client and Rich

Client Solutions
To install patches to Enterprise Knowledge Management thin client solutions or rich
client solutions, perform the following steps:
1. Download the required thin client or rich client patch sets for your site as
described in Downloading a Maintenance Pack, earlier in this appendix.
2. Extract the required thin client or rich client patch sets into your WEB_ROOT
directory. The extraction utility automatically creates a directory beneath your
WEB_ROOT directory named images_build-ID for the extracted files.
3. Launch the Web Application Manager by entering the insweb command from
your WEB_ROOT directory.
4. In the Web Applications field, select the Web application in which you want to
apply the patched solution and then click Modify.
5. Click Modify Disk Locations.
6. Add the path to the patched solution (WEB_ROOT/images_build-ID) to the list

of disk locations. Click OK to close the Modify Disk Locations dialog window.
If you have selected the Copy Main ICD Files Locally option, the
Maintenance Pack Manager prompts you to copy the ICD files to an
appropriate directory. Be sure to select Yes to copy the files.
7. Click Reinstall Solutions.

The Web Application Manager displays the Reinstall Solutions dialog window.
The Solutions Available for Reinstallation field contains the names of the
patched solutions available.
8. Select the patched solutions you want to reinstall, then click OK. The Web
Application Manager installs the patched solutions.
Make sure to patch all solutions in your Web application at the same time.6
For more information about reinstalling solutions, see Launching the Web
Application Manager in chapter 9, Installing Thin Client Solutions.
6. Some solutions may not have patch sets available. Install all available patch sets for the solutions you have installed.

Appendix
F Uninstalling Enterprise
Uninstalling the Search Engine Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Uninstalling Enterprise Knowledge Management Servers . . . . . . . . . . . . . . . F-2

Removing Enterprise Knowledge Management Environment Settings and
Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Removing Enterprise Knowledge Management Databases and Groups . . . F-2
Removing Enterprise Knowledge Management Directories and Files . . . . . F-3

Appendix
F Uninstalling Enterprise
This appendix describes how to uninstall Enterprise Knowledge Management

servers and Enterprise Knowledge Management features.
Before you perform procedures in this appendix, enter the following commands to
stop the MUX and dispatcher:
dspstop
muxstop
Uninstalling the Search Engine Service

To remove the Enterprise Knowledge Management search engine service, perform
Remove the search engine from the Enterprise Knowledge Management

configuration:
1. Launch the Configuration Editor.
2. Click Modify Database Information. The Configuration Editor displays the

Modify Database Information dialog window.
3. Click the Search Engines notebook card.
4. In the Name field, select the search engine you want to remove and click Remove.
The Configuration Editor prompts you to confirm the removal of the selected
search engine. Click Yes
5. After the Configuration Editor finishes removing the search engine, exit the
Configuration Editor.
Remove search engine directories:
2. Delete the MTI_ROOT/autonomy directory.
MT00300 L3 Installation on UNIX and Linux Servers F-1

Appendix F Uninstalling Enterprise Knowledge Management
Uninstalling Enterprise Knowledge Management Servers

This section describes how to uninstall an Enterprise Knowledge Management
server.
Removing Enterprise Knowledge Management Environment Settings

and Services
The following list contains tasks to perform to remove Enterprise Knowledge
Management environment settings and services from your system:
• Remove Enterprise Knowledge Management entries in UNIX startup files.
• Remove the Enterprise Knowledge Management MUX and dispatcher.
Removing Enterprise Knowledge Management Databases and Groups

Perform the following steps to remove Enterprise Knowledge Management databases
and user groups:
1. If you do not know the names of the databases used by your Enterprise
Knowledge Management corporate server,1 obtain the list by performing the
following steps:
a. Launch the Configuration Editor (using cfgedit2).
b. Click Modify Database Information.

The Configuration Editor displays the Modify Database Information dialog
window.
c. Click the Databases tab.

The Configuration Editor displays the names of all Enterprise Knowledge
Management databases.
d. If you use Oracle, find the tablespace names of each database by performing
1) Select a database and click Modify.
The Configuration Editor displays the Modify Database dialog window.
2) Find the tablespace name in the Tablespace field.
3) Repeat for each database.
e. Record the names of each database (and, if you use Oracle, tablespaces for
each database).
f. Close the Configuration Editor.
1. If you installed Enterprise Knowledge Management in a distributed-database environment, the default database names are
admm70a, keym70a, and sum70a.
F-2 Installation on UNIX and Linux Servers MT00300 L3

Uninstalling Enterprise Knowledge Management
2. Ask your database administrator to remove the databases, or remove them

yourself by performing the following steps:
a. Change to your MTI_ROOT/bin directory.
b. Enter the following command:

credbora -d -a admin-user -s system-password -n
database-name -g tablespace-name
Use the following values in the credbora command:
admin-user Name of the Oracle administrator account. The

default name is system.
system-password Password for the Oracle administrator account.
database-name Name of the database you want to remove.
tablespace-name Name of the tablespace for the database you want
to remove.
Use extreme caution when removing databases. Make sure you enter
all command line arguments correctly.
For more information about the credbora command, see the Network and
3. Remove the Enterprise Knowledge Management trusted user.
4. Remove the pdm user group (pdmusr), if one exists.
Removing Enterprise Knowledge Management Directories and Files

Perform the following tasks to remove Enterprise Knowledge Management programs
and files from your system:
• Remove all files in the MTI_ROOT directory (your Enterprise Knowledge
Management home directory) and its subdirectories, then remove the directories.
• Remove Web server virtual directories (instance-namedocs, instance-namecgi,

docs, cgi-bin, and pub).
MT00300 L3 Installation on UNIX and Linux Servers F-3

Index
A Autonomy service
Adding to existing server . . . . . . . . . 15-6
Account password, Oracle system . . . . . . 4-2 Adding to local area server . . . . . . . . 15-6
Adding components Adding to work group server . . . . . . . 15-6
e!Vista . . . . . . . . . . . . . . . . . . . . . . 15-1 Configuration variables . . . . . . . . . . . 7-3
Online documentation . . . . . . . . . . . 15-1 Configuring . . . . . . . . . . . . . . . . . . . . 7-2
Support files . . . . . . . . . . . . . . . . . . 15-1 Installation command . . . . . . . . . . . . 15-6
Adding search engine Installation file . . . . . . . . . . . . . . . . B-10
Local area server . . . . . . . . . . . . . . . 15-6 Removing . . . . . . . . . . . . . . . . . . . . . F-1
Work group server . . . . . . . . . . . . . . 15-6 Troubleshooting . . . . . . . . . . . . . B-8–B-9
Adding search engine service . . . . . . . . 15-6 Verifying status . . . . . . . . . . . . . . . . 15-7
AdmDcPrt class . . . . . . . . . . . . . . . . 11-14
AdmDcPrt class attribute set to Any . . 11-14
Admin Power User grp . . . . . . . . . . . . 11-7 B
Admin Power User Role . . . . . . . . . . . . 11-7 Backups, removing . . . . . . . . . . . . . . . E-4
ADMIN_POWER_USER condition . . . . 11-7 BIG5 encoding . . . . . . . . . . . . . . . . 2-5–2-6
ADMIN_POWER_USER_WI_PROJECT bldrora utility . . . . . . . . . . . . . . . . 6-6, C-7
condition . . . . . . . . . . . . . . . . . . . . . . 11-7 blkload utility . . . . . . . . . . . . . . . . . . . C-7
Administrative database BOM preview, enabling for
Disk space requirements . . . . . . . . . . . 2-4 translators . . . . . . . . . . . . . . . . . . . 12-12
Sample configuration . . . . . . . . . . . . . 1-2 break_poll_skip parameter . . . . . . . . . . C-1
AdmVal class attribute set to Any . . . . 11-12 Browser and window examples . . . . . . . . 13
AdmVal class attributes . . . . . . . . . . . 11-11 Bulk loader utility . . . . . . . . . . . . . . . . C-7
AdmVal object structure . . . . . . . . . . 11-13 bulkdump utility . . . . . . . . . . . . . . . . . . 6-6
Adobe Acrobat plugin, installation . . . . 9-12
AIX, before installing . . . . . . . . . . . . . . 6-1
C
Aliases
e!Vista cgi . . . . . . . . . . . . . . . . . . . . 16-2 C compiler . . . . . . . . . . . . . . . . . . . . . . 5-1
e!Vista docs . . . . . . . . . . . . . . . . . . . 16-2 C++ compiler . . . . . . . . . . . . . . . . . . . . 5-1
Application integrations . . . . . . . . . . . . . 9 C9T logging, enabling . . . . . . . . . . . . 12-10
Application sharing client . . . . . . . . . . 9-10 cat command . . . . . . . . . . . . . . . . . 5-2, 8-1
Attributes cd command . . . . . . . . . . . . . . . . . . . . . 4-5
AdmVal class . . . . . . . . . . . . . . . . . 11-11 cfgedit2 command . . . . . . . . . . . . . . . . . 6-2
DocumentClass . . . . . . . . . . 11-11, 11-14 cfgedit2 file . . . . . . . . . . . . . . . . . . . . . B-2
DocumentType . . . . . . . . . . 11-11, 11-14 cfgedit2.bat file . . . . . . . . . . . . . . . . . . . 6-2
FrozenDocIndicator . . . . . . . . . . . . 11-11 cgi virtual directory . . . . . . . . . . . . . . . 16-2
LifeCycleState . . . . . . . . . . . . . . . . 11-11 Change Management life cycles . . . . . . 11-2
PartClass . . . . . . . . . . . . . . 11-11, 11-14 Character replacement
PartType . . . . . . . . . . . . . . . 11-11, 11-14 Japanese . . . . . . . . . . . . . . . . . . . . . . 2-5
RelateFrozen . . . . . . . . . . . . . . . . . 11-14 Korean . . . . . . . . . . . . . . . . . . . . . . . 2-5
RequiredDocIndicator . . . . . . . . . . . 11-11 Simplified Chinese . . . . . . . . . . . . . . . 2-5
RevisedFirstIndicator . . . . . . . . . . . 11-14 Traditional Chinese . . . . . . . . . . . . . . 2-5
RulePriority . . . . . . . . . . . . 11-11, 11-14 Character sets . . . . . . . . . . . . . . . . . . . 4-7
SubmitDocIndicator . . . . . . . . . . . . 11-11 Half-Width Katakana . . . . . . . . . . . . . 2-5
Audience . . . . . . . . . . . . . . . . . . . . . . . . 9 JIS X 0208-1990 . . . . . . . . . . . . . . . . 2-5
MT00300 L3 Installation on UNIX and Linux Servers Index-1

Index
JIS-Roman/ASCII . . . . . . . . . . . . . . . 2-5 ADMIN_POWER_USER_WI_

KS C 5601-1992 . . . . . . . . . . . . . . . . . 2-5 PROJECT . . . . . . . . . . . . . . . . . . 11-7
KS-Roman/ASCII . . . . . . . . . . . . . . . . 2-5 FrozenManipulationAllowed . . . . . . . 11-8
Two-byte characters . . . . . . . . . . . . . . 2-5 lcm_claim_work_allowed . . . . . . . . . 11-8
Chinese locales Conferencing Solution
Environment settings . . . . . . . . . . . . . 2-6 Client applet . . . . . . . . . . . . . . . . . . 9-10
Platform support . . . . . . . . . . . . . . . . 2-5 Client application . . . . . . . . . . . . . . 9-10
Classes Context parameters . . . . . . . . . . . . . 9-10
AdmDcPrt . . . . . . . . . . . . . . . . . . . 11-14 Conferencing, required server solution . . 6-4
AdmVal . . . . . . . . . . . . . . . . . . . . . 11-11 config.cfg file . . . . . . . . . . . . . . . . . . . . B-1
CmChNtIt . . . . . . . . . . . . . . . . . . . . 11-9 Configuration Editor
CmChRqIt . . . . . . . . . . . . . . . . . . . . 11-9 Component installation . . . . . . . . . . 15-4
Classic client . . . . . . . . . . . . . . . . . . . . 1-7 Search engine configuration . . . . . . . . 7-2
Client tier . . . . . . . . . . . . . . . . . . . . . . 1-7 Configuration files
Client/server trust . . . . . . . . . . . . . . . . D-1 Deleting . . . . . . . . . . . . . . . . . . . . . B-1
CmChNtIt class . . . . . . . . . . . . . . . . . 11-9 Transferring . . . . . . . . . . . . . . 13-4, 15-2
CmChRqIt class . . . . . . . . . . . . . . . . . 11-9 Configuration variables
Code conventions . . . . . . . . . . . . . . . . . 14 Document management . . . . . . . . . . 14-2
Command line entry conventions . . . . . . 14 Online documentation . . . . . . . . . . . 16-3
Commands ONLINE_DOC_URL . . . . . . . . . . . . 16-3
cd . . . . . . . . . . . . . . . . . . . . . . . 4-5, C-8 PWF . . . . . . . . . . . . . . . . . . . . . . . . B-10
cfgedit2 . . . . . . . . . . . . . . . . . . . . 1-9, 6-2 Search engine . . . . . . . . . . . . . . . . . . 7-3
coraenv . . . . . . . . . . . . . . . . . . . 4-5, C-8 SEARCH_ENGINE_USE . . . . . . . . . . 7-3
credbora . . . . . . . . . . . . . . . . . . . . . . F-2 Security services . . . . . . . . . . . . . . . . 7-5
drestart . . . . . . . . . . . . . . . . . . . . . . B-9 VC_MUX_RESERVED_IPPORT_
dspstop . . . . . . . . . . . . . . . . . . . 13-4, F-1 REQUIRED . . . . . . . . . . . . . . . . D-2
insautonomy . . . . . . . . . . . . . . 15-6, B-10 Configuration variables, editing . . . . . 12-10
insweb . . . . . . . . . . . . 1-11, 8-2, 9-1, E-8 Configuring
lmdown . . . . . . . . . . . . . . . . . . . . . . . 5-6 Translation service . . . . . . . . . . . . . 12-1
lmgrd . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Configuring Autonomy service . . . . . . . . 7-2
lmstat . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Configuring online documentation . . . . 16-3
lmutil . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Configuring search engine . . . . . . . . . . . 7-2
mpm . . . . . . . . . . . . . . . . . . . . . . . . E-1 Connection dropped error . . . . . . . . . . B-11
muxstop . . . . . . . . . . . . . . . . . . 13-4, F-1 Content Management
netstart . . . . . . . . . . . . . . . . . . . . . . D-4 Context parameters . . . . . . . . . . . . . 9-16
OMF . . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Context parameter
pdmsetup . . . . . . . . . . . . . . . . . . . . B-10 MaxBlobSize . . . . . . . . . . . . . . . . . . 9-16
pushall . . . . . . . . . . . . . . . . . . 13-6, 15-3 MUXHost . . . . . . . . . . . . . . . . . . . . 9-16
pushf . . . . . . . . . . . . . . . . . . . 13-6, 15-3 MUXPort . . . . . . . . . . . . . . . . . . . . 9-16
uname . . . . . . . . . . . . . . . . . . . . . . B-4 ProcessingData_TopicTypeName . . . . 9-16
unmask . . . . . . . . . . . . . . . . . . . . . . C-8 Translation_Defaultstyle . . . . . . . . . 9-16
xrdb . . . . . . . . . . . . . . . . . . . . . . . . 16-3 Translation_LanguageName . . . . . . . 9-16
Communications multiplexor Translation_Publishtool . . . . . . . . . . 9-16
Described . . . . . . . . . . . . . . . . . . . . . 1-2 Vault . . . . . . . . . . . . . . . . . . . . . . . 9-16
Problems starting . . . . . . . . . . . . . . B-4 VaultLocation . . . . . . . . . . . . . . . . . 9-16
Compiler . . . . . . . . . . . . . . . . . . . . . . . 5-1 Context parameters
Components For Product Data Management . . . . . . 9-3
e!Vista . . . . . . . . . . . . . . . . . . . . . . . 6-5 Modifying . . . . . . . . . . . . . . . . . . . . . 9-6
Online documentation . . . . . . . . . . . . 6-5 Required . . . . . . . . . . . . . . . . . . . . . . 9-6
Support files . . . . . . . . . . . . . . . . . . . 6-5 Control object fields, translation
Components, installing . . . . . . . . . . . . 15-1 configuration . . . . . . . . . . . . . . . . . . . 12-2
Conditions Conventions
ADMIN_POWER_USER . . . . . . . . . . 11-7 Browser and window examples . . . . . . 13
Index-2 Installation on UNIX and Linux Servers MT00300 L3

Index
Caution icons . . . . . . . . . . . . . . . . . . . 12 DateIncorporationTransferVault

Code . . . . . . . . . . . . . . . . . . . . . . . . . 14 vault . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Command line entries . . . . . . . . . . . . 14 DB_VENDOR variable . . . . . . . . . 4-3, B-2
File contents . . . . . . . . . . . . . . . . . . . 14 Default license file . . . . . . . . . . . . . . . . . 5-2
Names . . . . . . . . . . . . . . . . . . . . . . . 13 Defining . . . . . . . . . . . . . . . . . . . . . . 11-13
Note icons . . . . . . . . . . . . . . . . . . . . . 12 Deleting configuration files . . . . . . . . . B-1
Syntax definitions . . . . . . . . . . . . . . . 15 Dialog windows
Values . . . . . . . . . . . . . . . . . . . . . . . . 13 Add Component . . . . . . . . . . . . . . . . 15-4
Warning icons . . . . . . . . . . . . . . . . . . 12 Modify Class Configuration
Copying installation files . . . . . 5-2, 8-1, 9-2 Variables . . . . . . . . . . . . . . . . . . 16-4
coraenv command . . . . . . . . . . . . . 4-5, C-8 Directories
Corporate server . . . . . . . . . . . . . . . . . . 1-3 Enterprise Knowledge Management
Adding components . . . . . . . . . . . . . 15-1 home . . . . . . . . . . . . . . . . . . . . . . 5-2
Adding modules . . . . . . . . . . . . . . . . 15-1 MTI_ROOT . . . . . . . . . . . . . . . . . 3-2, 5-2
Disk space requirements . . . . . . . . . . . 2-4 WEB_ROOT . . . . . . . . . . . . . . . . . . . 8-1
Sample configuration . . . . . . . . . . . . . 1-2 X11 . . . . . . . . . . . . . . . . . . . . . . . 5-3, 6-7
Corporate user database Disk space requirements . . . . . . . . . . . . 2-4
Disk space requirements . . . . . . . . . . . 2-4 Database . . . . . . . . . . . . . . . . . . . . . . 2-3
In sample configuration . . . . . . . . . . . 1-2 Documentation . . . . . . . . . . . . . . . . . 2-3
Creating Servers . . . . . . . . . . . . . . . . . . . . . . . 2-3
AdmDcPrt class object . . . . . . . . . . 11-14 Workstations . . . . . . . . . . . . . . . . . . . 2-3
AdmVal class object . . . . . . . . . . . . 11-11 Distribution image, locating . . . . . . . 5-2, 8-1
Product Data Management location docs virtual directory . . . . . . . . . . . . . . 16-2
selection rules . . . . . . . . . . . . . . . 11-7 Document management
Product Data Management vaults . . . 11-7 Services . . . . . . . . . . . . . . . . . . . . . 14-2
Vaults . . . . . . . . . . . . . . . . . . . . . . . 11-8 Variables . . . . . . . . . . . . . . . . . . . . . 14-2
credbora command . . . . . . . . . . . . . . . . F-2 Documentation
credbora utility . . . . . . . . . . . . . . . . . . C-7 Configuring . . . . . . . . . . . . . . . . . . . 16-3
cshrc file . . . . . . . . . . . . . . . . . . . . 4-5, C-8 Enabling symbol fonts . . . . . . . . . . . 16-3
Installing . . . . . . . . . . . . . . . . . . . . . 6-5
D Installing on client host . . . . . . . . . . 13-5
Manual set . . . . . . . . . . . . . . . . . . . . 16
Database vendors, Oracle . . . . . . . . . . . . 1-1 Setting ONLINE_DOC_URL . . . . . . . 16-3
Databases Sharing on file server . . . . . . . . . . . . 13-5
Administrative . . . . . . . . . . . . . . 1-3, 4-1 DocumentClass attribute . . . . . 11-11, 11-14
Disk space requirements . . . . . . . 2-4 DocumentType attribute . . . . . 11-11, 11-14
Sample configuration . . . . . . . . . . 1-2 Download locations, patch sets . . . . . . . E-3
Corporate user DownloadDir property,
Described . . . . . . . . . . . . . . . 1-3, 4-1 TranslationService.config file . . . . . . . 12-9
Disk space requirements . . . . . . . 2-4 Downloading maintenance pack . . . . . . E-1
Sample configuration . . . . . . . . . . 1-2 DRE service
Disk space requirements . . . . . . . . . . . 2-4 Adding to existing server . . . . . . . . . 15-6
Key . . . . . . . . . . . . . . . . . . . . . . . 1-3, 4-1 Configuring . . . . . . . . . . . . . . . . . . . . 7-2
Disk space requirements . . . . . . . 2-4 Installation command . . . . . . . . . . . . 15-6
Sample configuration . . . . . . . . . . 1-2 removing . . . . . . . . . . . . . . . . . . . . . . F-1
Operational Troubleshooting . . . . . . . . . . . . . B-8–B-9
Disk space requirements . . . . . . . 2-4 Verifying status . . . . . . . . . . . . . . . . 15-7
Sample configuration . . . . . . . . . . 1-2 drestart command . . . . . . . . . . . . . . . . B-9
Oracle . . . . . . . . . . . . . . . . . . . . . 1-3, 4-1 Dropping databases . . . . . . . . . . . . . . . . F-2
Removing . . . . . . . . . . . . . . . . . . . . . F-2 Dump and load security . . . . . . . . . . . . . 6-6
Server, sample configuration . . . . . . . . 1-2
User E
Disk space requirements . . . . . . . 2-4
Sample configuration . . . . . . . . . . 1-2 e!Vista

Index
Installing . . . . . . . . . . . . . . . . . . . . . 6-5 ORACLE_HOME . . . . . . . . . . . . . . . . 4-4

Starting . . . . . . . . . . . . . . . . . . . . . 16-6 ORACLE_SID . . . . . . . . . . . . . . . . . . 4-4
Virtual directories PATH . . . . . . . . . . . . . . . . . . . . . . . . 5-1
cgi . . . . . . . . . . . . . . . . . . . . . . 16-2 PDM_CONFIG . . . . . . . . . . . . . . . . B-1
docs . . . . . . . . . . . . . . . . . . . . . 16-2 SHLIB_PATH . . . . . . . . . . . . . . . . . . 4-4
e!Vista client . . . . . . . . . . . . . . . . . . . . 1-7 TNS_ADMIN . . . . . . . . . . . . . . . 4-9–4-10
Adding aliases . . . . . . . . . . . . . . . . . 16-2 TWO_TASK . . . . . . . . . . . . . . . . . . . 4-4
Web server configuration . . . . . . . . . 16-2 Errors
e!Vista tasks . . . . . . . . . . . . . . . . . . . . . 1-7 Error occurred in msql . . . . . . . . . . . B-10
EAR file Oracle timeout connection dropped . . B-11
Building . . . . . . . . . . . . . . . . . . . 9-5, 9-8 Starting the MUX . . . . . . . . . . . . . . B-4
Deploying . . . . . . . . . . . . . . . . . . . . 10-1 esvm utility . . . . . . . . . . . . . . . . . . . . 13-4
Effectivities . . . . . . . . . . . . . . . . . . . . 11-9 EUC-TW encoding . . . . . . . . . . . . . . . . . 2-5
Enabling installation utility . . . . . . . . . B-1 Event handler, editing . . . . . . . . . . . . 12-14
Enabling symbol fonts . . . . . . . . . . . . . 16-3 Event posting service . . . . . . . . . . . . . . 1-2
Encoding Example of automatic part revision and
BIG5 . . . . . . . . . . . . . . . . . . . . . . 2-5–2-6 PartDoc relation . . . . . . . . . . . . . . . 11-15
GB2312-80 . . . . . . . . . . . . . . . . . 2-5–2-6 Example of documents required for
JEUC . . . . . . . . . . . . . . . . . . . . . 2-5–2-6 release . . . . . . . . . . . . . . . . . . . . . . 11-12
KS C . . . . . . . . . . . . . . . . . . . . . . 2-5–2-6 Example of valid values for reviewer
S-JIS . . . . . . . . . . . . . . . . . . . . . 2-5–2-6 list . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
UTF-8 . . . . . . . . . . . . . . . . . . . . . . . . 2-6 exports file . . . . . . . . . . . . . . . . . . . . . D-1
Encryption settings, FIPS . . . . . . . . . . . 6-5
Enterprise information system tier . . . . . 1-7 F
Creating UNIX user . . . . . . . . . . . . . . 3-1 FIFOs . . . . . . . . . . . . . . . . . . . . . . . . D-3
Shutdown . . . . . . . . . . . . . . . . . . . . 6-10 File contents conventions . . . . . . . . . . . . 14
Startup . . . . . . . . . . . . . . . . . . . . . . 6-10 File transfers
Trusted user, olaunch executable . . . . . 6-9 Authentication and proxies . . . . . . . . . 9-9
Vendor daemon . . . . . . . . . . . . . . . . . 5-2 Files
Enterprise Knowledge cfgedit2 . . . . . . . . . . . . . . . . . . . . . . B-2
Management Foundation server config.cfg . . . . . . . . . . . . . . . . . . . . . B-1
solution . . . . . . . . . . . . . . . . . . . . . . 15-2 cshrc . . . . . . . . . . . . . . . . . . . . . 4-5, C-8
Enterprise Knowledge Management home EAR . . . . . . . . . . . . . . . . . . 9-5, 9-8, 10-1
directory . . . . . . . . . . . . . . . . . . . . . . . 3-2 exports . . . . . . . . . . . . . . . . . . . . . . D-1
Enterprise Knowledge Management inautonomy.exe . . . . . . . . . . . . . . . . B-10
port . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 insautonomy . . . . . . . . . . . . . . . . . . 15-6
Environment settings insdre.sav . . . . . . . . . . . . . . . . 15-6, B-8
Japanese . . . . . . . . . . . . . . . . . . . . . . 2-6 insweb . . . . . . . . . . . . . . . . . . . . 8-2, 9-1
Korean . . . . . . . . . . . . . . . . . . . . . . . 2-6 licenses.mti . . . . . . . . . . . . . . . . . . . . 5-2
Simplified Chinese . . . . . . . . . . . . . . . 2-6 listener.ora . . . . . . . . . . . . . . . 4-9–4-10,
Traditional Chinese . . . . . . . . . . . . . . 2-6 B-11, C-1–C-2, C-4
Environment variables lmgrd . . . . . . . . . . . . . . . . . . . . . . . . 5-2
DB_VENDOR . . . . . . . . . . . . . . 4-3, B-2 loaded.dat . . . . . . . . . . . . . . . . . . . . E-7
JRE_HOME . . . . . . . . . . . . . . . . . . B-2 .login . . . . . . . . . . . . . . . . . . . . . . . C-7
LANG . . . . . . . . . . . . . . . . . . . . . . . . 2-6 MODeL . . . . . . . . . . . . . . . . . . . . . . 13-6
LC_ALL . . . . . . . . . . . . . . . . . . . . . . 2-6 mtid (Enterprise Knowledge Management
LD_LIBRARY_PATH . . . . . . . . . 4-4, B-4 vendor daemon) . . . . . . . . . . . . . . 5-2
LIBPATH . . . . . . . . . . . . . . . . . . . . . 4-4 .profile . . . . . . . . . . . . . . . . . . . . . . C-7
LM_LICENSE_FILE . . . . . . . . . 5-3, 13-3 protocol.ora . . . . . . . . . . . . . . . . C-1, C-3
MTI_ROOT . . . . . . . . . . . . . . . . . . . 13-4 root.sh . . . . . . . . . . . . . . . . . . . . . . D-1
NLS_LANG . . . . . . . . . . . . . 2-6, 4-4, 4-7 selected.dat . . . . . . . . . . . . . . . . B-1, E-7
NLS_LOCALE . . . . . . . . . . . . . . . . . . 2-6 sqlnet.ora . . . . . . . 4-9–4-10, C-1, C-4–C-5

Index
Startup . . . . . . . . . . . . . . . . . . . . . . C-7 INSTALL_BASE.TZ file . . . . . . . . . . . . . 5-2

Temporary license file . . . . . . . . . . . . 5-2 INSTALL_CFGEDIT.TZ file . . . . . . . . . . 5-2
tnsnames.ora . . . . . 4-9–4-10, C-1–C-2, C-6 INSTALL_ENTERPRISE.JAR file . . . . . 9-2
WAR . . . . . . . . . . . . . . . . . . 9-5, 9-8, 10-1 INSTALL_PATS maintenance pack . . . E-3
.Xdefaults . . . . . . . . . . . . . . . . . . . . 16-3 INSTALL_TC_PTIER_BASE.TZ file . . . . 8-1
FIPS, specifying encryption settings . . . . 6-5 INSTALL_TCWEB.TZ file . . . . . . . . . . . 8-1
FLEXnet Manager license manager INSTALL_WEBPD maintenance pack . . E-3
Configuring . . . . . . . . . . . . . . . . . . . . 5-3 INSTALL_WINCLNT maintenance
Daemon . . . . . . . . . . . . . . . . . . . . . . 5-2 pack . . . . . . . . . . . . . . . . . . . . . . . . . E-3
Shutting down . . . . . . . . . . . . . . . . . . 5-3 Installation
Starting . . . . . . . . . . . . . . . . . . . . . . 5-2 Adding components . . . . . . . . . . . . . 15-1
Utility . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Adding modules . . . . . . . . . . . . . . . . 15-1
FMS client cache, installation . . . . . . . 9-12 Adobe Acrobat plugin . . . . . . . . . . . . 9-12
Fonts, for online documentation . . . . . . 16-3 Answers to prompts . . . . . . . . . . . . . . 4-2
French locales, platform support . . . . . . . 2-5 Application integrations . . . . . . . . . . . . 9
Frozen object manipulation . . . . . . . . . 11-7 Client without server . . . . . . . . . . . . . . 9
FrozenDocIndicator attribute . . . . . . . 11-11 Copying installation files . . . 5-2, 8-1, 9-2
FrozenManipulationAllowed Creating Oracle user . . . . . . . . . . . . C-1
condition . . . . . . . . . . . . . . . . . . . . . . 11-8 Enterprise Knowledge Management client
FSF port . . . . . . . . . . . . . . . . . . . 7-3, B-9 without server . . . . . . . . . . . . . . . . . 9
FSFS port . . . . . . . . . . . . . . . . . . . . . . 7-3 FMS client cache (FCC) . . . . . . . . . . 9-12
Installing Server Solutions . . . . . . . . 15-1
G Microsoft Office interface . . . . . . . . . 9-12
Microsoft Outlook integration . . . . . . 9-12
GB2312-80 encoding . . . . . . . . . . . . 2-5–2-6 NFS considerations . . . . . . . . . . . . . D-1
German locales, platform support . . . . . . 2-5 Nonapplet support . . . . . . . . . . . . . . . 9-8
Groups Online documentation . . . . . . . . . . . 13-5
MsgGrp . . . . . . . . . . . . . . . . . . . . . 11-10 Oracle . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Review List grp . . . . . . . . . . . . . . . 11-10 Patches . . . . . . . . . . . . . . . . . . . . . . . 5-1
GTAC patch server . . . . . . . . . . . . . . . E-3 Tool Agent . . . . . . . . . . . . . . . . . . . . 9-12
Vis View Convert . . . . . . . . . . . . . . . 14-1
H Vis View Print . . . . . . . . . . . . . . . . . 14-1
WebPD . . . . . . . . . . . . . . . . . . . . . . 9-12
Hardware requirements . . . . . . . . . . . . . 2-3 Installation files
Hosts INSTALL_BASE.TZ . . . . . . . . . . . . . . 5-2
Managed . . . . . . . . . . . . . . . . . . . . . . 1-4 INSTALL_CFGEDIT.TZ . . . . . . . . . . . 5-2
Unmanaged . . . . . . . . . . . . . . . . . . . . 1-4 INSTALL_ENTERPRISE.JAR . . . . . . 9-2
INSTALL_TC_PTIER_BASE.TZ . . . . . 8-1
I INSTALL_TCWEB.TZ . . . . . . . . . . . . 8-1
Installation files, locating . . . . . . . . . 5-2, 8-1
Icon conventions . . . . . . . . . . . . . . . . . . 12 Installation scripts
IDOLA port . . . . . . . . . . . . . . . . . 7-3, B-9 insDocs . . . . . . . . . . . . . . . . . . 13-5, 15-5
IDOLI port . . . . . . . . . . . . . . . . . . 7-3, B-9 insEvista . . . . . . . . . . . . . . . . . 13-5, 15-5
IDOLS port . . . . . . . . . . . . . . . . . 7-3, B-9 insmenu . . . . . . . . . . . . . . . . . 13-4, B-3
Indexed search . . . . . . . . . . . . . . . . . . 15-6 insSupport . . . . . . . . . . . . . . . 13-5, 15-5
Indexed search service Prompts . . . . . . . . . . . . . . . . . . . . . 13-4
Configuration variables . . . . . . . . . . . 7-3 Installation tools
Installing . . . . . . . . . . . . . . . . . . . . . 7-2 Configuration Editor . . . . . . . . . . . . . 1-9
insautonomy command . . . . . . . . 15-6, B-10 Installation utility . . . . . . . . . . . . . . . 1-9
insautonomy file . . . . . . . . . . . . . . . . . B-10 Web Application Manager . . . . . . . . . 1-11
insdre.sav file . . . . . . . . . . . . . . . 15-6, B-8 Installation utility
insmenu script . . . . . . . . . . . . . . . . . . B-3 Definition . . . . . . . . . . . . . . . . . . . . . 1-9
INSTALL_BASE maintenance pack . . . E-3 Errors starting . . . . . . . . . . . . . . . . B-1

Index
Overview . . . . . . . . . . . . . . . . . . . . . . 1-9 License manager daemon . . . . . . . . . 5-5–5-6

Installing License manager status . . . . . . . . . . . . . 5-6
Maintenance packs . . . . . . . . . . . . . E-2 licenses.mti file . . . . . . . . . . . . . . . . . . . 5-2
Vis products . . . . . . . . . . . . . . . . . . 14-1 Life cycles
Instance recovery . . . . . . . . . . . . . . . . B-10 Change Management . . . . . . . . . . . . 11-2
insweb command . . . . . . . . . . . 8-2, 9-1, E-8 LcsReleased state . . . . . . . . . . . . . 11-12
Invalid character replacement Part Request life cycle . . . . . . . . . . . 11-7
Japanese . . . . . . . . . . . . . . . . . . . . . . 2-5 Product Data Management . . . . . . . . 11-2
Korean . . . . . . . . . . . . . . . . . . . . . . . 2-5 Request for quote (RFQ) . . . . . . . . . . 11-6
Simplified Chinese . . . . . . . . . . . . . . . 2-5 LifeCycleState attribute . . . . . . . . . . 11-11
Traditional Chinese . . . . . . . . . . . . . . 2-5 Linux, before installing . . . . . . . . . . . . . 6-1
InvalidationIntervalSecs parameter . . . 10-5 Listener
Restarting . . . . . . . . . . . . . . . . . . . . 4-10
J Starting . . . . . . . . . . . . . . . . . . . . . 4-10
Stopping . . . . . . . . . . . . . . . . . . . . . 4-10
J2EE model Listener process . . . . . . . . . . . . . . . . . 4-10
Client tier . . . . . . . . . . . . . . . . . . . . . 1-7 listener.ora file . . . . . . . . . 4-9, C-1–C-2, C-4
Enterprise information system tier . . . 1-7 LM_LICENSE_FILE environment
Web tier . . . . . . . . . . . . . . . . . . . . . . 1-7 variable . . . . . . . . . . . . . . . . . . . . . . . 5-3
Japanese character set . . . . . . . . . . . . . 2-5 LM_LICENSE_FILE variable . . . . 5-3, 13-3
Japanese locales lmgrd command . . . . . . . . . . . . . . . . . . 5-3
Environment settings . . . . . . . . . . . . . 2-6 lmgrd file . . . . . . . . . . . . . . . . . . . . . . . 5-2
Invalid character replacement . . . . . . . 2-5 Local area server . . . . . . . . . . . . . . . . . 1-3
Platform support . . . . . . . . . . . . . . . . 2-5 Local file server, enabling . . . . . . . . . . 12-13
Java heap sizing . . . . . . . . . . . . . . . . . 10-5 Location selection rules . . . . . . . . . . . . 11-9
JavaServer Pages (JSP) . . . . . . . . . . . . . 1-7 .login file . . . . . . . . . . . . . . . . . . . . . . C-7
JEUC encoding . . . . . . . . . . . . . . . . 2-5–2-6 Login notes, OMF verification . . . . . . . . 6-8
JRE_HOME variable . . . . . . . . . . . . . . B-2 lsnrctl command . . . . . . . . . . . . . . . . . 4-10
K M
Key database Macrovision license manager . . . . . . . . . 5-2
Disk space requirements . . . . . . . . . . . 2-4 Maintenance pack
Sample configuration . . . . . . . . . . . . . 1-2 Downloading . . . . . . . . . . . . . . . . . . E-1
Korean character set . . . . . . . . . . . . . . . 2-5 Rich client . . . . . . . . . . . . . . . . . . . . E-8
Korean locales Maintenance packs
Environment settings . . . . . . . . . . . . . 2-6 Downloading, manually . . . . . . . . . . E-5
Invalid character replacement . . . . . . . 2-5 INSTALL_BASE . . . . . . . . . . . . . . . E-3
Platform support . . . . . . . . . . . . . . . . 2-5 INSTALL_PATS . . . . . . . . . . . . . . . E-3
KS C encoding . . . . . . . . . . . . . . . . 2-5–2-6 INSTALL_WEBPD . . . . . . . . . . . . . E-3
INSTALL_WINCLNT . . . . . . . . . . . . E-3
L Installing . . . . . . . . . . . . . . . . . . . . E-2
Installing, from patch repository . . . . E-7
Launching Reinstalling . . . . . . . . . . . . . . . . . . . E-4
e!Vista . . . . . . . . . . . . . . . . . . . . . . 16-6 Rich client . . . . . . . . . . . . . . . . . . . . E-3
lcm_claim_work_allowed condition . . . . 11-8 Thin client . . . . . . . . . . . . . . . . . E-3, E-8
LcsReleased life cycle state . . . . . . . . 11-12 Uninstalling . . . . . . . . . . . . . . . . . . E-4
LD_LIBRARY_PATH variable . . . . . . . B-4 Viewing readme files . . . . . . . . . . . . E-4
License file . . . . . . . . . . . . . . . . . . . . . . 5-3 Managed hosts . . . . . . . . . . . . . . . . . . . 1-4
License manager . . . . . . . . . . . . . . 5-3, 15-1 manager account password . . . . . . . . . . 4-2
FLEXnet daemon . . . . . . . . . . . . . . . . 5-2 Managing patch download locations . . . E-3
Shutting down . . . . . . . . . . . . . . . . . . 5-6 Manual organization . . . . . . . . . . . . . . . 10
Starting . . . . . . . . . . . . . . . . . . . . . . 5-2 Manual set . . . . . . . . . . . . . . . . . . . . . . 16
Variables . . . . . . . . . . . . . . . . . . . . . . 5-2 Memory requirements . . . . . . . . . . . . . . 2-3

Index
Message access rules . . . . . . . . . . 11-8–11-9 Installation . . . . . . . . . . . . . . . . . . . 13-5

Message groups, Submit_grp . . . . . . . . 11-9 Installing . . . . . . . . . . . . . . . . . . . . . 6-5
Microsoft Office interface, Installing on client host . . . . . . . . . . 13-5
installation . . . . . . . . . . . . . . . . . . . . 9-12 Sharing on file server . . . . . . . . . . . . 13-5
Microsoft Outlook integration, ONLINE_DOC_URL variable . . . . . . . . 16-3
installation . . . . . . . . . . . . . . . . . . . . 9-12 open_cursors parameter . . . . . . . . . . . . 4-10
MODeL viewer, errors . . . . . . . . . . . . . B-4 open_links parameter . . . . . . . . . . . . . 4-10
Modifying context parameters . . . . . . . . 9-6 Operating system requirements
Modifying patch server settings . . . . . . E-3 Japanese . . . . . . . . . . . . . . . . . . . . . . 2-5
Modules Korean . . . . . . . . . . . . . . . . . . . . . . . 2-5
Installing . . . . . . . . . . . . . . . . . . . . 15-1 Simplified Chinese . . . . . . . . . . . . . . . 2-5
msql cannot log in error . . . . . . . . . . . . B-10 Traditional Chinese . . . . . . . . . . . . . . 2-5
mti file (Enterprise Knowledge Management Operational database
vendor daemon) . . . . . . . . . . . . . . . . . . 5-2 Disk space requirements . . . . . . . . . . . 2-4
MTI_ROOT directory . . . . . . . . . . . . 3-2, 5-2 Sample configuration . . . . . . . . . . . . . 1-2
MTI_ROOT variable . . . . . . . . . . . . . . 13-4 Options
MUX and NFS . . . . . . . . . . . . . . . . . . D-2 Add component . . . . . . . . . . . . . . . . 15-4
MUX port . . . . . . . . . . . . . . . . . . . . . . . 6-3 Create DB Objects . . . . . . . . . . . . . . . 4-3
MUX service, problems starting . . . . . . B-4 Oracle . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
muxd program . . . . . . . . . . . D-1, D-3–D-4 Adding to UNIX initialization . . . . . . 6-10
Answers to installation prompts . . . . . 4-2
N Configuration file . . . . . . . . . . . . . . . C-4
Disk space requirements . . . . . . . . . . . 2-4
Name conventions . . . . . . . . . . . . . . . . . 13 Error number 2020 . . . . . . . . . . . . . 4-11
netstart command . . . . . . . . . . . . . . . . D-4 Installation prompt answers . . . . . . . . 4-2
Network architecture Installing . . . . . . . . . . . . . . . . . . . . . 4-3
Enterprise Knowledge Management Instance recovery . . . . . . . . . . . . . . . B-10
clients . . . . . . . . . . . . . . . . . . . . . 1-4 listener.ora . . . . . . . . . . . . . . . . . . . C-4
Web applications . . . . . . . . . . . . . . . . 1-7 Network connections configuration
Network File System . . . . . . . . . . . . . . D-1 file . . . . . . . . . . . . . . . . . . . . . . . C-6
Network services Prompts . . . . . . . . . . . . . . . . . . . . . . 4-2
Installing . . . . . . . . . . . . . . . . . . . . . 6-7 Sample user creation . . . . . . . . . . . . C-1
NFS SQL*Plus . . . . . . . . . . . . . . . . . . . . . 4-7
Client/server trust . . . . . . . . . . . . . . D-1 sqlnet.ora . . . . . . . . . . . . . . . . . . . . C-5
FIFOs . . . . . . . . . . . . . . . . . . . . . . . D-3 Terminology . . . . . . . . . . . . . . . . 1-3, 4-1
MUX and dispatcher usage . . . . . . . . D-4 Timeout connection dropped error . . . B-11
MUX considerations . . . . . . . . . . . . . D-2 tnsnames.ora . . . . . . . . . . . . . . . . . . C-6
netstart usage . . . . . . . . . . . . . . . . . D-4 Trace configuration file . . . . . . . . . . . C-5
olaunch considerations . . . . . . . . . . . D-2 User creation . . . . . . . . . . . . . . . . . . C-1
Sockets . . . . . . . . . . . . . . . . . . . . . . D-3 User creation by installation
NLS_CHARACTERSET parameter . . . . . 4-7 program . . . . . . . . . . . . . . . . . . . C-1
NLS_LANG variable . . . . . . . . . . . . 4-4, 4-7 Verification . . . . . . . . . . . . . . . . . . . . 4-7
Nonapplet functionality . . . . . . . . . . . . . 9-8 Oracle character set . . . . . . . . . . . . . . . 4-7
ORACLE HOME prompt . . . . . . . . . . . . 4-2
O Oracle instance . . . . . . . . . . . . . . . . . . . 4-2
ORACLE owner prompt . . . . . . . . . . . . . 4-2
$obj.ReviewList dynamic Oracle parameter files
participant . . . . . . . . . . . . . . . . . . . 11-10 listener.ora . . . . . . . . . . . . . . . . C-1–C-2
olaunch, NFS considerations . . . . . . . . D-2 protocol.ora . . . . . . . . . . . . . . . . C-1, C-3
OMF object server . . . . . . . . . . . . . . . . . 1-2 sqlnet.ora . . . . . . . . . . . . . . C-1, C-4–C-5
Online documentation tcp.nodelay . . . . . . . . . . . . . . . . . . . C-3
Configuring . . . . . . . . . . . . . . . . . . . 16-3 tnsnames.ora . . . . . . . . . . . . C-1–C-2, C-6
Fonts, enabling . . . . . . . . . . . . . . . . 16-3 Oracle parameters

Index
break_poll_skip . . . . . . . . . . . . . C-1, C-4 insweb . . . . . . . . . . . . . . . . . . . . 8-2, 9-1

open_cursors . . . . . . . . . . . . . . . . . . 4-10 Maintenance Pack Manager . . . . . . . E-1
open_links . . . . . . . . . . . . . . . . . . . . 4-10 Web Application Manager . . . . . . . . . E-8
queuesize . . . . . . . . . . . . . . . . . C-1–C-2 WebPD . . . . . . . . . . . . . . . . . . . . . . 9-12
SDU . . . . . . . . . . . . . . . . . . . . . C-1–C-2 protocol.ora file . . . . . . . . . . . . . . . C-1, C-3
tcp.nodelay . . . . . . . . . . . . . . . . C-1, C-3 pushall command . . . . . . . . . . . . 13-6, 15-3
TDU . . . . . . . . . . . . . . . . . . . . . C-1–C-2 pushf command . . . . . . . . . . . . . . 13-6, 15-3
Oracle performance tuning . . . . . . . . . . C-1 PWF variable . . . . . . . . . . . . . . . . . . . B-10
ORACLE SID prompt . . . . . . . . . . . . . . 4-2
ORACLE_HOME variable . . . . . . . . . . . 4-4 Q
ORACLE_SID variable . . . . . . . . . . . . . 4-4
queuesize parameter . . . . . . . . . . . C-1–C-2
P
R
pageCheckSeconds parameter . . . . . . . 10-5
Parameters, open cursors . . . . . . . . . . . 4-10 Re-enabling installation utility . . . . . . . B-1
PartClass attribute . . . . . . . . . 11-11, 11-14 Reinstalling maintenance packs . . . . . . E-4
PartDoc relation . . . . . . 11-12, 11-14–11-15 Reinstalling server solutions . . . . . . . . 15-7
Participants, LCM Dynamic . . . . . . . . 11-10 RelateFrozen attribute . . . . . . . . . . . 11-14
PartType attribute . . . . . . . . . 11-11, 11-14 Relations, PartDoc . . . . 11-12, 11-14–11-15
Passwords, SYSTEM . . . . . . . . . . . . . . . 4-2 Removing databases and groups . . . . . . . F-2
Patch . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Removing Enterprise Knowledge Management
Patch repository server . . . . . . . . . . . . E-7 directories . . . . . . . . . . . . . . . . . . . . . . F-3
Patch server settings . . . . . . . . . . . . . . E-3 Removing Enterprise Knowledge Management
Patching rich client solutions . . . . . . . . E-8 services . . . . . . . . . . . . . . . . . . . . . . . F-2
Patching thin client solutions . . . . . . . . E-8 Removing patch set backups . . . . . . . . E-4
Path command . . . . . . . . . . . . . . . . . . . 5-1 Removing search engine service . . . . . . . F-1
PATH variable . . . . . . . . . . . . . . . . . . . 5-1 Request for quote (RFQ)
PDM_CONFIG variable . . . . . . . . . . . . B-1 Life cycles . . . . . . . . . . . . . . . . . . . . 11-6
pdmsetup command . . . . . . . . . . . . . . B-10 Templates . . . . . . . . . . . . . . . . . . . . 11-6
pdmusr group . . . . . . . . . . . . . . . . . . . . 3-2 Required context parameters . . . . . . . . . 9-6
Platform support RequiredDocIndicator attribute . . . . . 11-11
Japanese locales . . . . . . . . . . . . . . . . 2-5 Requirements
Korean locales . . . . . . . . . . . . . . . . . . 2-5 Hardware . . . . . . . . . . . . . . . . . . 2-1, 2-3
Simplified Chinese locales . . . . . . . . . . 2-5 Locales . . . . . . . . . . . . . . . . . . . . . . . 2-1
Traditional Chinese locales . . . . . . . . . 2-5 Software . . . . . . . . . . . . . . . . . . . . . . 2-1
Ports Review List role . . . . . . . . . . . . . . . . 11-10
Enterprise Knowledge Management . . 6-3 RevisedFirstIndicator attribute . . . . . 11-14
FSF port . . . . . . . . . . . . . . . . . . 7-3, B-9 Rich client
FSFS port . . . . . . . . . . . . . . . . . . . . . 7-3 Downloading patches . . . . . . . . . . . . E-3
IDOLA port . . . . . . . . . . . . . . . . 7-3, B-9 Installing patches . . . . . . . . . . . . . . E-8
IDOLI port . . . . . . . . . . . . . . . . 7-3, B-9 Rich client solutions, patching . . . . . . . E-8
IDOLS port . . . . . . . . . . . . . . . . 7-3, B-9 Role . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
MUX . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 root.sh file . . . . . . . . . . . . . . . . . . . . . D-1
Search engine . . . . . . . . . . . . . . . . . . 7-3 rulefile utility . . . . . . . . . . . . . . . . . . . C-7
Postinstallation steps . . . . . . . . . . . . . . 6-9 RulePriority attribute . . . . . . . 11-11, 11-14
Prepare Visualization Files option . . . . B-7 Rules cache . . . . . . . . . . . . . . . . . . . . C-7
Privileged operations server . . . . . . . . . . 1-2 Rules, Product Data Management location
Product Data Management life cycles . . 11-2 selection . . . . . . . . . . . . . . . . . . . . . . 11-7
Product Data Management vaults . . . . 11-7 Running installation script . . . . . . . . . 13-4
.profile file . . . . . . . . . . . . . . . . . . . . . C-7
Programs S
Bulk loader . . . . . . . . . . . . . . . . . . . C-7
Configuration Editor . . . . . . . . . . . . E-1 Samples

Index
Oracle user creation . . . . . . . . . . . . . C-1 Setting up trusted user . . . . . . . . . . . . . 3-1

root.sh file . . . . . . . . . . . . . . . . . . . . D-1 Simplified Chinese character set . . . . . . . 2-5
Scripts Simplified Chinese locales
insmenu . . . . . . . . . . . . . . . . . . . . . B-3 Environment settings . . . . . . . . . . . . . 2-6
Installation . . . . . . . . . . . . . . . 13-4, B-3 Invalid character replacement . . . . . . . 2-5
root.sh . . . . . . . . . . . . . . . . . . . . . . B-4 Platform support . . . . . . . . . . . . . . . . 2-5
SDU parameter . . . . . . . . . . . . . . . . . C-1 Single sign-on service . . . . . . . . . . . . . . 9-4
Search engine See also Security services
Activating . . . . . . . . . . . . . . . . . . . . . 7-3 SJIS encoding . . . . . . . . . . . . . . . . . 2-5–2-6
Adding to existing server . . . . . . . . . 15-6 Sockets . . . . . . . . . . . . . . . . . . . . . . . D-3
Adding to local area server . . . . . . . . 15-6 Solaris, before installing . . . . . . . . . . . . 6-1
Adding to work group server . . . . . . . 15-6 Solutions, adding . . . . . . . . . . . . . . . . . 9-7
Configuration variables . . . . . . . . . . . 7-3 Special services host
Configuring . . . . . . . . . . . . . . . . . . . . 7-2 Description . . . . . . . . . . . . . . . . . . . . 1-6
Installation command . . . . . . . . . . . . 15-6 SQL*Plus . . . . . . . . . . . . . . . . . . . . . . . 4-7
Removing . . . . . . . . . . . . . . . . . . . . . F-1 sqlnet.ora file . . . . . . . . . . 4-9, C-1, C-4–C-5
Troubleshooting . . . . . . . . . . . . . B-8–B-9 SSO_SERVICE_URL variable . . . . . . . . 7-5
Verifying status . . . . . . . . . . . . . . . . 15-7 Starting
Search engine service . . . . . . . . . 15-6–15-7 e!Vista . . . . . . . . . . . . . . . . . . . . . . 16-6
SEARCH_ENGINE_USE configuration Listener . . . . . . . . . . . . . . . . . . . . . 4-10
variable . . . . . . . . . . . . . . . . . . . . . . . 7-3 Startup file, editing . . . . . . . . . . . . . . . C-7
Security Strategies . . . . . . . . . . . . . . . . . . . . . . 11-9
Client/server trust . . . . . . . . . . . . . . D-1 StrategyTransferVault vault . . . . . . . . 11-8
olaunch executable . . . . . . . . . . . . . . . 6-9 SubmitDocIndicator attribute . . . . . . 11-11
Security services SubmitItemSync message . . . . . . . . . . 11-9
Application ID . . . . . . . . . . . . . . . . . . 9-4 Support files, installing . . . . . . . . . . . . . 6-5
Configuration variables . . . . . . . . . . . 7-5 Swap space . . . . . . . . . . . . . . . . . . . . . . 2-5
Context parameters . . . . . . . . . . . . . . 9-4 Syntax definition conventions . . . . . . . . . 15
Enabling . . . . . . . . . . . . . . . . . . . . . . 9-4 SYSTEM account password prompt . . . . 4-2
Installation/customization manual . . . 9-5 System hardware requirements . . . . . . . 2-3
Login service URL . . . . . . . . . . . . . . . 9-4 System identifiers, Oracle . . . . . . . . . . . 4-2
Service URL . . . . . . . . . . . . . . . . . . . 9-4
Web application settings . . . . . . . . . . . 9-4 T
Security, restricting access
Dump . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Tags
Load . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 SERVER . . . . . . . . . . . . . . . . . . . . . B-9
Server launch . . . . . . . . . . . . . . . . . . 6-9 SERVICE . . . . . . . . . . . . . . . . . . . . B-9
Security, UNIX trusted user . . . . . . . . . . 3-1 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Server solutions TaskTransferVault vault . . . . . . . . . . . 11-8
Enterprise Knowledge tcp.nodelay parameter . . . . . . . . . . . . . C-1
Management Foundation . . . . . . . 15-2 TDU parameter . . . . . . . . . . . . . . . . . C-1
Installing . . . . . . . . . . . . . . . . . . . . 15-1 Teamcenter Conferencing Solution
Reinstalling . . . . . . . . . . . . . . . . . . . 15-7 Context parameters . . . . . . . . . . . . . 9-10
Required for solutions . . . . . . . . . . . . 6-4 Required server solution . . . . . . . . . . . 6-4
Selecting . . . . . . . . . . . . . . . . . . . . . 15-2 Teamcenter Project Integration
SERVER tag . . . . . . . . . . . . . . . . . . . . B-9 Context parameters . . . . . . . . . . . . . 9-15
Servers Teamcenter Security Services . . . . . . . . . 9-4
Corporate . . . . . . . . . . . . . . . . . . . . . 1-3 See also Security services
Local area . . . . . . . . . . . . . . . . . . . . . 1-3 Teamcenter Toolkit
Web application server . . . . . . . . . . . . 1-5 Active sessions . . . . . . . . . . . . . . . . . 10-5
Web server . . . . . . . . . . . . . . . . . . . . 1-5 Java heap sizing . . . . . . . . . . . . . . . 10-5
SERVICE tag . . . . . . . . . . . . . . . . . . . B-9 JSP recompilation . . . . . . . . . . . . . . 10-5
Setting context parameters . . . . . . . . . . 9-6 Network architecture . . . . . . . . . . . . . 1-7

Index
Server housecleaning . . . . . . . . . . . . 10-5 Search engine installation fails . . . . . B-9

Teamcenter’s enterprise knowledge Translation errors . . . . . . . . . . . . . . B-5
management Unable to start Configuration
Network architecture . . . . . . . . . . . . . 1-7 Editor . . . . . . . . . . . . . . . . . . . . B-2
Required server solutions . . . . . . . . . . 9-1 Troubleshooting search engine
Solutions . . . . . . . . . . . . . . . . . . . . . . 1-7 service . . . . . . . . . . . . . . . . . . . . B-8–B-9
Temporary license file . . . . . . . . . . . . . . 5-2 Trusted user
Terminology, Oracle and Enterprise Assigning to directory . . . . . . . . . . . . . 3-2
Knowledge Management . . . . . . . . 1-3, 4-1 Setting up . . . . . . . . . . . . . . . . . . . . . 3-1
Thin client Trusted user password, generating . . . 12-10
Downloading patches . . . . . . . . . . . . E-3 TWO_TASK variable . . . . . . . . . . . . . . . 4-4
Installing patches . . . . . . . . . . . . . . E-8
Thin client solutions U
Adding to Web application . . . . . . . . . 9-7
Copying ICD files . . . . . . . . . . . . . . . . 9-2 UGAnswer . . . . . . . . . . . . . . . . . . . . . . 2-2
Thin client solutions, patching . . . . . . . E-8 uname command . . . . . . . . . . . . . . . . . B-4
Third-party products, support UNC paths . . . . . . . . . . . . . . . . . . . . . 13-4
information . . . . . . . . . . . . . . . . . . . . . 2-2 Uninstalling
Timeout connection dropped error . . . . B-11 Databases and groups . . . . . . . . . . . . F-2
TNS_ADMIN variable . . . . . . . . . . 4-9–4-10 Directories . . . . . . . . . . . . . . . . . . . . F-3
tnsnames.ora file . . . . . . . . 4-9, C-1–C-2, C-6 Environment settings . . . . . . . . . . . . . F-2
Trace configuration file . . . . . . . . . . . . C-5 Files . . . . . . . . . . . . . . . . . . . . . . . . . F-3
Traditional Chinese character set . . . . . . 2-5 Search engine service . . . . . . . . . . . . . F-1
Traditional Chinese locales Services . . . . . . . . . . . . . . . . . . . . . . F-2
Environment settings . . . . . . . . . . . . . 2-6 Uninstalling Enterprise Knowledge
Invalid character replacement . . . . . . . 2-5 Management . . . . . . . . . . . . . . . . . . . . F-1
Platform support . . . . . . . . . . . . . . . . 2-5 Uninstalling maintenance packs . . . . . . E-4
Translation configuration, control object UnitIncorporationTransferVault
parameters . . . . . . . . . . . . . . . . . . . . 12-2 vault . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Translation control objects UNIX
Parameters . . . . . . . . . . . . . . . . . . . 12-2 Initialization, Oracle . . . . . . . . . . . . 6-10
Setting up . . . . . . . . . . . . . . . . . . . . 12-2 Security . . . . . . . . . . . . . . . . . . . . . . 3-1
Translation environment Server security . . . . . . . . . . . . . . . . . 6-9
Service . . . . . . . . . . . . . . . . . . . . . 12-14 Setup
Translation control objects . . . . . . . . 12-2 Oracle . . . . . . . . . . . . . . . . . . . . . 3-1
Troubleshooting . . . . . . . . . . . . . . . . B-5 Trusted user . . . . . . . . . . . . . . . . 3-1
Translation service User group access . . . . . . . . . . . . . . . 3-1
Configuration overview . . . . . . . . . . . 12-1 User setup . . . . . . . . . . . . . . . . . . . . . 3-1
Setting up . . . . . . . . . . . . . . . . . . . 12-14 Unmanaged hosts . . . . . . . . . . . . . . . . . 1-4
TranslationService.config unmask command . . . . . . . . . . . . . . . . C-8
Editing . . . . . . . . . . . . . . . . . . . . . . 12-9 User database
Event handler . . . . . . . . . . . . . . . . 12-14 Disk space requirements . . . . . . . . . . . 2-4
Translator mappings, editing . . . . . . . 12-10 Sample configuration . . . . . . . . . . . . . 1-2
Troubleshooting User group . . . . . . . . . . . . . . . . . . . . 11-10
Installation script fails . . . . . . . . . . . B-3 User group, Enterprise Knowledge
Installation utility not enabled . . . . . B-1 Management . . . . . . . . . . . . . . . . . . . . 3-1
MODeL viewer . . . . . . . . . . . . . . . . B-4 User property, TranslationService.config
msql cannot log in . . . . . . . . . . . . . . B-10 file . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
MUX problems . . . . . . . . . . . . . . . . B-4 UTF-8 . . . . . . . . . . . . . . . . . . . . . . 2-6, 4-7
Oracle timeout connection dropped . . B-11 Utilities
Recovering Oracle instance . . . . . . . . B-10 bldrora . . . . . . . . . . . . . . . . . . . 6-6, C-7
Restarting Configuration Editor . . . . B-2 blkload . . . . . . . . . . . . . . . . . . . . . . C-7
Search engine cannot start . . . . . . . . B-8 Bulk load . . . . . . . . . . . . . . . . . . . . C-7

Index
bulkdump . . . . . . . . . . . . . . . . . . . . . 6-6 VC_MUX_FIFO variable . . . . . . . . . . . D-3

Configuration Editor . . . . . . . . . . . . E-1 VC_MUX_RESERVED_IPPORT_REQUIRED
credbora . . . . . . . . . . . . . . . . . . . . . C-7 variable . . . . . . . . . . . . . . . . . . . . . . D-2
esvm . . . . . . . . . . . . . . . . . . . . . . . . 13-4 VC_MUX_SOCK variable . . . . . . . . . . D-3
Maintenance Pack Manager . . . . . . . E-1 Verification, Oracle . . . . . . . . . . . . . . . . 4-7
rulefile . . . . . . . . . . . . . . . . . . . . . . C-7 Verifying installation . . . . . . . . . . . . . . 10-6
Oracle . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Thin client . . . . . . . . . . . . . . . . . . . . 10-1
V Viewing maintenance pack
information . . . . . . . . . . . . . . . . . . . . E-4
Value conventions . . . . . . . . . . . . . . . . . 13 Virtual directories
Value set to Any . . . . . . . . . . . 11-12, 11-14 e!Vista cgi . . . . . . . . . . . . . . . . . . . . 16-2
Variables e!Vista docs . . . . . . . . . . . . . . . . . . . 16-2
DB_VENDOR . . . . . . . . . . . . . . 4-3, B-2 Vis View Convert, installation . . . . . . . 14-1
JRE_HOME . . . . . . . . . . . . . . . . . . B-2 Vis View Print, installation . . . . . . . . . 14-1
LANG . . . . . . . . . . . . . . . . . . . . . . . . 2-6
LC_ALL . . . . . . . . . . . . . . . . . . . . . . 2-6
LD_LIBRARY_PATH . . . . . . . . . 4-4, B-4 W
LIBPATH . . . . . . . . . . . . . . . . . . . . . 4-4
License manager . . . . . . . . . . . . . . . . 5-2 WAR file
LM_LICENSE_FILE . . . . . . . . . 5-3, 13-3 Building . . . . . . . . . . . . . . . . . . . 9-5, 9-8
MTI_ROOT . . . . . . . . . . . . . . . . . . . 13-4 Deploying . . . . . . . . . . . . . . 9-5, 9-8, 10-1
NLS_LANG . . . . . . . . . . . . . . . . . 2-6, 4-4 Generating . . . . . . . . . . . . . . . . . . . . 9-8
NLS_LOCALE . . . . . . . . . . . . . . . . . . 2-6 Web Application Manager
ONLINE_DOC_URL . . . . . . . . . . . . 16-3 Adding solutions . . . . . . . . . . . . . . . . 9-2
ORACLE_HOME . . . . . . . . . . . . . . . . 4-4 Adding Solutions . . . . . . . . . . . . . . . . 9-7
ORACLE_SID . . . . . . . . . . . . . . . . . . 4-4 Context parameters . . . . . . . . . . . . . 9-12
PATH . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Generating deployable file . . . . . . 9-5, 9-8
PDM_CONFIG . . . . . . . . . . . . . . . . B-1 Generating WAR file . . . . . . . . . . . . . 9-8
PWF . . . . . . . . . . . . . . . . . . . . . . . . B-10 Launching . . . . . . . . . . . . . . . . . . . . . 8-2
SEARCH_ENGINE_USE . . . . . . . . . . 7-3 Reinstalling solutions . . . . . . . . . . . . . 9-7
SHLIB_PATH . . . . . . . . . . . . . . . . . . 4-4 Required server solutions . . . . . . . . . . 9-1
Special services configuration . . . . . . 14-2 Web Application Manager, launching . . . 9-1
TNS_ADMIN . . . . . . . . . . . . . . . 4-9–4-10 Web application server
TWO_TASK . . . . . . . . . . . . . . . . . . . 4-4 Performance tuning . . . . . . . . . . . . . 10-4
VC_MUX_FIFO . . . . . . . . . . . . . . . . D-3 Web application verification . . . . . . . . . 10-6
VC_MUX_RESERVED_IPPORT_ Web servers
REQUIRED . . . . . . . . . . . . . . . . D-2 Adding aliases . . . . . . . . . . . . . . . . . 16-2
VC_MUX_SOCK . . . . . . . . . . . . . . . D-3 Configuring . . . . . . . . . . . . . . . . . . . 16-2
Vault locations . . . . . . . . . . . . . . . . . . 11-9 e!Vista . . . . . . . . . . . . . . . . . . . . . . 16-2
Archive Vault Loc . . . . . . . . . . . . . . . 11-7 Web tier . . . . . . . . . . . . . . . . . . . . 1-7, 10-4
Released Vault Loc . . . . . . . . . . . . . . 11-7 WEB_ROOT directory . . . . . . . . . . . . . . 8-1
Template Vault Loc . . . . . . . . . . . . . 11-7 WebPD
WIP Vault Loc . . . . . . . . . . . . . . . . . 11-7 Context parameters . . . . . . . . . . . . . 9-12
Vaults . . . . . . . . . . . . . . . . . . . . . . . . 11-9 Installation, automatic . . . . . . . . . . . 9-12
Archive Vault . . . . . . . . . . . . . . . . . 11-7 Installation, manual . . . . . . . . . . . . . 9-12
DateIncorporationTransferVault . . . . 11-8 WebPD components
Product Data Management . . . . . . . . 11-7 Adobe Acrobat plugin . . . . . . . . . . . . 9-12
Released Vault . . . . . . . . . . . . . . . . . 11-7 FMS client cache (FCC) . . . . . . . . . . 9-12
StrategyTransferVault . . . . . . . . . . . 11-8 Microsoft Office interface . . . . . . . . . 9-12
TaskTransferVault . . . . . . . . . . . . . . 11-8 Microsoft Outlook integration . . . . . . 9-12
Template Vault . . . . . . . . . . . . . . . . 11-7 Tool agent . . . . . . . . . . . . . . . . . . . . 9-12
UnitIncorporationTransferVault . . . . 11-8 Window examples . . . . . . . . . . . . . . . . . 13
WIP Vault . . . . . . . . . . . . . . . . . . . . 11-7 Work group server . . . . . . . . . . . . . . . . . 1-3

Index
X .Xdefaults file . . . . . . . . . . . . . . . . . . . 16-3

X11 . . . . . . . . . . . . . . . . . . . . . . . . 5-3, 6-7

Teamcenter 2007 Installation Mt00300

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Teamcenter 2007 Installation Mt00300

Hochgeladen von

Copyright:

Verfügbare Formate

Teamcenter 2007

Enterprise Knowledge Management

Installation on UNIX and Linux

Installation on UNIX and Linux

This product is intended for use only as described in this document.

Manual Metaphase Publication

Manual Enterprise Knowledge Publication

This edition obsoletes all previous editions.

2 Installation on UNIX and Linux Servers MT00300 L3

Part I: Preparing to Install Enterprise Knowledge Management

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Creating the Enterprise Knowledge Management Trusted User . . . . . . 3-1

Installing Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Part II: Installing the Enterprise Tier

Preparing the Enterprise Knowledge Management Environment . . . . . 5-1

MT00300 L3 Installation on UNIX and Linux Servers 3

Installing Enterprise Knowledge Management . . . . . . . . . . . . . . . . . . . 6-1

Configuring Enterprise Knowledge Management . . . . . . . . . . . . . . . . . 7-1

Part III: Installing the Web Tier

Installing the Web Application Manager . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Installing Thin Client Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Deploying an Enterprise Knowledge Management Web Application . . 10-1

Part IV: Additional Configuration and Maintenance

Setting Up Administrative Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Setting Up Translation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

4 Installation on UNIX and Linux Servers MT00300 L3

Installing Local Area and Work Group Servers . . . . . . . . . . . . . . . . . . 13-1

Installing a Special Services Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Adding Server Solutions and Components . . . . . . . . . . . . . . . . . . . . . . 15-1

Configuring Legacy Web-Based Products . . . . . . . . . . . . . . . . . . . . . . . 16-1

Oracle Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Installing and Running Enterprise Knowledge Management Using

MT00300 L3 Installation on UNIX and Linux Servers 5

Running the MUX and Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4

Installing Maintenance Packs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Uninstalling Enterprise Knowledge Management . . . . . . . . . . . . . . . . . F-1

1-1. Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

1. Enterprise Knowledge Management Installation and Conversion . . . . . 16

6 Installation on UNIX and Linux Servers MT00300 L3

2. Enterprise Knowledge Management Modules and Solutions . . . . . . . . . 16

MT00300 L3 Installation on UNIX and Linux Servers 7

This manual provides instructions for installing Teamcenter server components on

• Basic operating system use, including setting environment variables, starting

• Client-server network architecture.

• Basic database usage and terminology.

MT00300 L3 Installation on UNIX and Linux Servers 9

• Part IV, Additional Configuration and Maintenance, describes how to install

• Part V, Appendixes, provides supporting information.

Part I – Preparing to Install Enterprise Knowledge Management

Chapter 1 Overview provides an overview of the installation process.

10 Installation on UNIX and Linux Servers MT00300 L3

Part II – Installing the Enterprise Tier

Chapter 5 Preparing the Enterprise Knowledge Management Environment

Part III – Installing the Web Tier

Chapter 8 Installing the Web Application Manager describes how to install

Part IV – Additional Configuration and Maintenance

Chapter 11 Setting Up Administrative Data describes how to load

MT00300 L3 Installation on UNIX and Linux Servers 11

Chapter 15 Adding Server Solutions and Components describes how to

Appendix A Glossary defines Enterprise Knowledge Management terms.

Note, Caution, and Warning Icons

A note icon identifies general instructions or comments that need to be

A warning icon identifies practices that could result in permanent loss of

12 Installation on UNIX and Linux Servers MT00300 L3