Teamcenter Enterprise: Guidelines for Setup and …

1 Erich Brauchli PLM-ConsultingErich Brauchli PLM-ConsultinTeamcenter enterprise : Guidelines for Setup and Configuration 2. March 2008 ( ) / Erich Brauchli g Teamcenter enterprise : Guidelines for Setup and Configuration Volume ITI-MTI-B Written by Erich Brauchli March 2, 2008 Version Reflecting Teamcenter enterprise 2005 Email: Internet: (Total 41 pages) Entire List of Teamcenter enterprise Documents: ITI-MTI-A Guidelines for Planing and Operation ITI-MTI-B Guidelines for Setup and Configuration ITI-MTI-C Guidelines for Oracle Setup and DB Configuration ITI-MTI-D Guidelines for Customizing ITI-MTI-E Rules D:\Dokument\Metaphase\Programming Guide\ ITI-MTI-B page 1/41 Teamcenter enterprise : Guidelines for Setup and Configuration 2.

2 March 2008 ( ) / Erich Brauchli Erich Brauchli PLM-ConsultingErich Brauchli PLM-Consulting D:\Dokument\Metaphase\Programming Guide\ ITI-MTI-B page 2/41 Content 1 A small history of Teamcenter enterprise .. 3 2 Distributed Teamcenter enterprise .. 3 Oracle ..3 OS-Username trusted User ..4 IP-Port ..4 License File / 3 Distributed Services .. 5 Service Service configuration name ..7 arguments ..7 path ..9 Service arguments ..9 Configuration recommendations ..10 starting Observation and correction Special 4 Sample Configuration .. 12 Sample.

3 12 Sample of ..13 ..14 Sample Sample Special Platform specific ..19 Windows: ..19 AIX ..19 5 European Language Support in Oracle .. 20 6 Mail / Notifications .. 20 Variables in Config File ..20 7 Hostnames and Communication .. 21 8 File System access and Shared Disks .. 22 File Systems Locations - Data Files ..24 System part of other File System Items ..24 Data ..25 File System Item Class Structure ..25 Spaces and Locations ..26 Overview and Identification ..26 Vaults and Vault Work Locations ..28 File Systems ..28 System System Proxy Shared drives versus Replicated Vault Locations ..31 Drives or mounted file systems.

4 31 Replicated Vault 9 Data Integrity Mechanisms .. 32 Data Integrity Failure Sources with Teamcenter enterprise ..32 Instrumented Integrity Utilities ..33 Reasonable Frequency ..34 Non Instrumented Checks ..35 Vault Location Consistency ..35 Data Dictionary Database Schema Consistency ..35 Recovery Options ..35 Recovery ..35 Partial Recovery ..35 10 Upgrade of Metaphase 3 Instances created under Metaphase 36 Configuration File ..36 File ..36 Distributed Databases ..36 11 Teamcenter Instance Migration / Data Migration .. 36 Definition of the TERM migration ..36 Scenarios ..37 Upgrade Migration ..38 of a Test Migration from a lower release to a higher one.

5 38 Productive Upgrade Teamcenter enterprise : Guidelines for Setup and Configuration 2. March 2008 ( ) / Erich Brauchli Erich Brauchli PLM-ConsultingErich Brauchli PLM-Consulting D:\Dokument\Metaphase\Programming Guide\ ITI-MTI-B page 3/41 1 A small history of Teamcenter enterprise 1990: the two companies SDRC (Structural Dynamics Research Corporation1) and CDC (Control Data Corporation2) decided to strengthen their relative CAD support systems3 (DMCS and EDL4) into a common new PLM product in a modern world wide distributed context. Under the lead of chief design architect Jim Heppelman the new common company Metaphase Technology (owned 50% by each of the two parent companies) did build a PDM software from scratch, in new object oriented architecture, but with a development crew built out engineers of the two parent products.

6 1994: First Release a revolutionary PDM product Metaphase 2. 1996: SDRC became 100% owner of Metaphase Technology. 2001: SDRC was purchased by EDS subsidiary UGS Corporation. 2004: EDS sold off UGS Corporation. 2007: UGS Corporation was purchased by Siemens AG and is now Siemens PLM Solutions The product was branded as Metaphase to , then Collaboration Foundation 1 to 2, then Teamcenter enterprise and later and will continue in the next years as such original version as well as soon in a new common platform together with Teamcenter Engineering and other Teamcenter application. 2 Distributed Teamcenter enterprise Oracle Before you install any Teamcenter enterprise , check carefully the installed Oracle and SqlNet installations.

7 On any side log in as Oracle administrator and try to create a database link to any other used Oracle system, then try the access to the remote system doing a select * from dba_users @ dblinkname; If this does not work, do not continue with Teamcenter ! Teamcenter s msqlora service will only login into the Oracle user named in the DDB variable in your config file. All other databases, even local ones, are addressed through the respective database links5. If this verification runs as os user oracle but not as the Teamcenter trusted user , this may have one of the following causes: has no read permission set for others . Oracle Variables or path is not fully set up for the Teamcenter trusted user.

8 Caution under Windows: do not follow sample connections in SqlNet, which are not TCP connections. 1 ) Founded 1967 by professor Dr. Jason R. Lemon from University of Cinncinati. 2 ) Founded 1957 by William C. Norris in Minneapolis. 3 ) Rather CAD drawing management systems. 4 ) EDL = Engineering Data Library, 1990-1994 branded as Metaphase 1. 5 ) Except usage of DOT-Notation , more details see volume ITI-MIT-C, chapter Usage of DOT notation . Teamcenter enterprise : Guidelines for Setup and Configuration 2. March 2008 ( ) / Erich Brauchli Erich Brauchli PLM-ConsultingErich Brauchli PLM-Consulting D:\Dokument\Metaphase\Programming Guide\ ITI-MTI-B page 4/41 OS-Username trusted User If on your system exists already a Teamcenter enterprise installation: you must install and run the new environment as another os-user.

9 This user is the Teamcenter trusted user , the owner of the Teamcenter enterprise Application. The Teamcenter background processes can only determine to which installation they belong through the os-username under which they are started. Any mismatch here may either not work, or corrupt your database. Each Teamcenter enterprise installation runs under its own unique OS-user name; it is recommended to be the same over all servers of the Teamcenter enterprise instance. IP-Port Obviously each Teamcenter enterprise installation must run with its own unique IP-port within the entire network. This means all software servers and clients on all machines, which communicate with each other as one common Teamcenter enterprise system must have exactly one IP-port number declared as VC_MUX_IPPORT6, which may not be used by any other Teamcenter enterprise environment in your network, nor by any other service in your network.

10 It is recommended to enter the used IP-port in the /etc/services file, just for documentation purpose ( Teamcenter enterprise does not look up their, because you may run more than one Teamcenter enterprise system on one host, so they must run different on IP-ports). Each Teamcenter enterprise installation has its own unique IP-Port number; which is mandatory the same over all servers and clients of the Teamcenter enterprise instance. Note for AIX: On AIX cluster systems ( SP line) the default Teamcenter enterprise is in the IBM reserved range for Cluster communication. IBM requests any application port to be higher that 20'000. License File / Port The port number on the license file must be different from any config IP-port.