Component Interaction Teamcenter Engineering System Component Interaction The following slide shows how processes are connected and provides an overview to illustrate the following points: Portal clients connect to imanserver similar to the way Web clients connect to a Web server. Motif clients connect directly with the Oracle database and Teamcenter Engineering data vaults using SQLNet and NFS (or iMANFS) respectively. Custom clients using the apiserver process are similar to Motif clients.
Dedicated Oracle Servers Oracle to run stand alone is the goal, is the preferred way to run oracle, ‘best practices’. One development env, a matching production env. Have had instances with d0ora2 where a stand alone environment would have prevented downtime. Stand alone server is the cdf and minos model. Prevents competition for resources with the database, decreasing potential downtime.
The critical decision for the Teamcenter Engineering implementation team is the sizing and placement of Oracle, vault and application servers. (for example, Portal, Web). Again, this is highly dependent on network infrastructure and Teamcenter Engineering usage profiles. Network traffic between the Teamcenter Engineering shared servers and the Oracle server is proportionally greater than that between a server and its clients. Therefore, the network connection between Teamcenter Engineering servers and the Oracle server should be high bandwidth and low latency. Teamcenter Engineering server communication with the clients is more tolerant of low-speed, high-latency networks. Planning Teamcenter Engineering Servers
Teamcenter Engineering Portal Servers Portal implementations have a variety of configuration options, as previously described. Like the Teamcenter Engineering Web server, the Teamcenter Engineering Portal server is also computationally intensive and is best served by a machine with a high SPECint rate (throughput) rating. Portal servers also require significant amount of memory (multiple gigabytes) to support large numbers of users.
Development Environment The TeamCenter development environment will mirror the production environment to enable routine testing and application of patches, etc. 1 database server machine, 1 NT for other apps. Potentially servering dev, int, and train databases.
One license vs. duals Pros: –1 license to support Cons: –1 license to mess up both production and development. This is not in line with dsg’s standards and procedures. –Working with vendor to supply a dev license for free, limiting # of users, but non temporary. –Dual licenses will allow us to separate out developers and trainers from production.
Ideas Licenses product users desc A001 24 Core Master Modeler A002 21 Core Drafting A003 20 Surfacing Set A004 20 Assembly Set A009 8 Simulation Modeling Set A010 5 Simulation Solution Set A052 1 Sheet Metal A054 1 Model Solution - Nonlinear A055 1 Laminate Composites A061 1 TMG Thermal A083 1 Drafting Symbols Catalog A084 1 Standard Parts Catalog A086 1 Material Data Catalog - MDLA A088 1 Material Data Catalog - MIL5 A103 1 STEP Data Translator A107 5 ABAQUS Data Translator A108 5 ANSYS Data Translator A121 1 Autocad Data Translator A145 5 Response Analysis A156 1 Mechanism Simulation A172 19 Mechanism Design A180 25 Master Notation A200 25 Take home Licensing A314 95 Artisan Drafting A646 1 VRML Annotation A801 25 Update Training