Introduction to Teamcenter PLM Customization
Teamcenter PLM provides a variety of mechanisms for customization catering to different business requirements. Teamcenter PLM customization is based on the base framework of APIs provided by Teamcenter PLM Solution. In this blog let’s discuss available customization options and architecture of Teamcenter PLM
Teamcenter PLM Customization Components & Architecture
Teamcenter PLM customization architecture can be broadly classified based on Teamcenter PLM technical architecture. It can be categorized into three layers as shown below.
- Server Customization is the core of all customization as most of the Business logic is written in this layer. Server customization mainly deals with all business transaction as it interacts with database through Persistence Object Model (POM) API.
- Server customization is done through C based API provided by Teamcenter PLM. This API is also called Integration Toolkit (ITK). SOA customization and BMIDE extension options are also available for customization on Teamcenter PLM Server
- As shown in the diagram, all BMIDE extension is in server side. Because most BMIDE extension overrides or changes object behavior based on business requirement. This can be only accomplished in server layer; hence all extension is implemented by using core ITK API provided in server layer.
- Web Layer is Teamcenter based J2EE deployment layer which basically communicates between Server and client.
- Client Layer is portal or thin client customization which usually deals with user interface and data of the results retrieved from the server request.
- SOA Client and Server is Service Oriented Architecture (SOA) Application Programming Interface (API) for calling SOA services.
- FMS is resource layer supporting actual file transfer between client and server through FMS framework.
Teamcenter PLM Customization Areas
Based on above Customization components, Teamcenter PLM Customization can be categorized in the following areas.
- Server Customization
- Portal Customization
- Web or Thin Client Customization
- SOA based Customization
- BMIDE Extension Customization
Server Customization: Server side customization is the most frequently performed customization, as all business logic is written in server layer. All requests pass through server layer for all Teamcenter PLM transactions. Hence server layer is core of Teamcenter PLM customization. As discussed in Teamcenter PLM Customization Layers, Teamcenter PLM provide C based application program interfaces (APIs) called Integration Toolkit (ITK) for server side customization. Integration Toolkit (ITK) provides hundreds of APIs for processing various business process based customizations on Teamcenter PLM functionality. ITK is categorized by various modules and functionalities of Teamcenter PLM. Extension mechanisms are provided by Integration Toolkit (ITK) to plug in custom code based on various Teamcenter PLM events and object statuses.
Portal Customization: Teamcenter PLM Client layer is written on Java Foundation Classes (JFC) and eclipse Standard Widget Toolkit (SWT). Teamcenter PLM core client APIs are written in Java Foundation Classes framework, it will be ported to eclipse Standard Widget Toolkit framework. Teamcenter PLM supports both JFC and SWT customization, but it is recommended to do customization in SWT to align with Teamcenter PLM technology roadmap. The Portal Customization can be done extending out of the box (OOTB) plug-in or developing our own plug-in. Teamcenter PLM client API also provides object interface component which is an encapsulation of Teamcenter PLM data model through client object model. Teamcenter PLM client object Interface component also form interface layer between client and server.
SOA Customization: SOA Customization is also called Teamcenter PLM services. It is a standard SOA based services provided by Teamcenter PLM for integrating with third party as well custom client. Teamcenter PLM provides framework to create your own custom SOA services.
BMIDE Extension Customization: This is mainly Teamcenter PLM server customization using Teamcenter PLM BMIDE. BMIDE provides various extension customization mechanisms for implementing desired behavior in Teamcenter PLM. Examples of BMIDE extension is pre-action or post-action operation for a Business object, Runtime property etc. These extensions are implemented in BMIDE environment by writing C or C++ server code mainly using ITK API. BMIDE framework creates stub code and other required classes for extension implementation. Developer is only required to implement base logic of the extension.
Teamcenter PLM Dispatcher module also can be customized for required translation behavior. Dispatcher client is required to be implemented for extracting and loading translated file from Teamcenter PLM. The Dispatcher Client Framework is based on Teamcenter PLM SOA service. Most of the OOTB SOA API is used apart from Dispatcher API which encapsulates most of complex Teamcenter PLM SOA API calls.
Teamcenter PLM Training
- Teamcenter PLM Functional Training (URL: https://plmcoach.com/teamcenter-functional-training/)
- Teamcenter PLM Deployment Training (URL: https://plmcoach.com/teamcenter-deployment/)
- Teamcenter PLM Administration Training (URL: https://plmcoach.com/teamcenter-administration/)
- Teamcenter PLM Business Modeler Administration Training (URL: https://plmcoach.com/teamcenter-business-modeler/)
- Teamcenter PLM Server Side (ITK) Customization Training (URL: https://plmcoach.com/teamcenter-server-customization/)
- Teamcenter PLM Client Side (RAC) Customization Training (URL: https://plmcoach.com/teamcenter-client-customization/)
- Teamcenter PLM Active Workspace (AWC) Customization Training (URL: https://plmcoach.com/teamcenter-active-workspace-customization/)
Teamcenter PLM Development Technologies
- C++ – For Teamcenter PLM Server Side Programming
- Java – For Teamcenter PLM Client Side Programming
- AngularJS – For Teamcenter PLM Active Workspace Programming
Teamcenter PLM References on Web
- Siemens PLM Software (URL: https://www.plm.automation.siemens.com/global/en/products/teamcenter/)
Checkout Video on Teamcenter PLM Architecture: