Teamcenter Teamcenter has two applications based on the Eclipse framework: The Rich Client and the Business

Modeler IDE. With the Rich Client you can perform all of your PLM interaction from a single client. One of the perspectives in the Rich Client is a graphical browser that allows a user to visually navigate an assembly structure and drill down into its sub-assemblies as well as its individual components. If more detailed investigation of the component or sub-assembly is desired its 2D and 3D visual representation is just a mouse click away. The Business Modeler IDE allow codeless modification of Teamcenter business processes.

Configure PLM to Fit Your Business

Teamcenters Business Modeler IDE (BMIDE):

Empowers PLM process owners with a business process oriented user interface, wizardbased guidance and best practices that require no software development skills Extends configurability so you can specify displayed attributes and names, define new business objects, modify behavior of built-in objects and define business rules Empowers IT with applications and templates to deploy and maintain configurations, reducing or eliminating the need for custom software so that you can easily deploy multiple systems and manage the deployment of upgrades

Teamcenter BMIDE: http://www.scribd.com/doc/60452689/Creating-Your-Own-Team-Center-SOA-Services The Teamcenter Enterprise IDE is built on top of the Eclipse platform: http://www.cadfamily.com/online-help/Teamcenter/mt00397/IntroductionToTheIDE.html http://www.cadfamily.com/online-help/Teamcenter/mt00397/InstallingThePlugins.html http://www.cadfamily.com/online-help/Teamcenter/mt00343/Introduction.html#C01A3001 Teamcenter Enterprise Objects: http://www.cadfamily.com/online-help/Teamcenter/mt00321/MetaphaseObjects.html#ZAPSZ19

Service Oriented Architecture (SOA): http://www.plm.automation.siemens.com/zh_cn/Images/Siemens-PLM-Teamcenter-ServiceOriented-Architecture-wp_tcm78-24383.pdf Documentation Teamcenter Services: http://wenku.baidu.com/view/13353d0a79563c1ec5da718a.html Teamcenter Translation Framework: http://teamcenterplm.blogspot.com/2011/10/customizing-translation-services.html

down vote accepted Here's a quick, dirty, and very general explanation of a 4-tier architecture, which I'm assuming may best apply to your application: Presentation Layer : The interface to the outside world (web site) Application Layer : The mechanics necessary to create the interface(s) to the outside world (web application frameworks, web services) Business Logic Layer : The actual logic that embodies/simulates/emulates your business's processes and workflows (algorithms, transformations, approval processes, etc.) Database Layer : The database and the logic needed to query information from it In general, web services are not part of the business logic layer. That layer is usually protected as much as the database layer, because there could be trade secrets or confidential ways of doing things in there, and you usually don't want anyone accessing that directly, except programatically or through approved interfaces (such as web services). Web services, application layers, and business logic can be aptly compared to Coca-Cola and it's business. Bottles and cans are usually how Joe Blow consumes Coke's product (e.g. web site in the presentation layer), but other businesses want to be able to serve Coca-Cola to their customers as well, so Coke lets them use carbonated water and Coca-Cola syrup (e.g. web services in the application layer). Coke's secret formula (e.g. business logic layer), and Coke's distribution processes to get it into the store (e.g. application layer) are all hidden from the consumer. Joe Blow doesn't care how it gets into the store, he just knows he can get Coke from a variety of sources (web site, mobile client, etc.). And Coke doesn't want people knowing its secret formula (business logic). If you want a Coke, you have to go through a store or a restaurant (approved interfaces).
http://en.wikipedia.org/wiki/Multitier_architecture