TEM (Teamcenter Environment Manager) VS DC (Deployment Center )

 TEM (Teamcenter Environment Manager) VS DC (Deployment Center )


The long-time Time Close Friend of Teamcenter Professionals, TEM, will be removed (from TC2506) or deprecated (from TC13.2).
TEM is going to be removed from TC2506, and everyone knows Everything about it, so we will not discuss it further.
Our New friend who is going to replace TEM is DC (Deployment Center) is having more Responsibility and more Features than TEM (Great Power Comes with Great Responsibility)
For the last many Releases, DC has been in the Development/Implementation phase and has gone through Functionality, bugs, and the Defect Cycle before Becoming Good enough To Replace TEM.
The Siemens PD Team may want to create an Application like Facebook for TC Deployment (Or For a Different Siemens Portfolio Application). All Can be Deployed Using DC.
Possibilities are many but the motto is Ease of Implementation and everything under one location and one person administration.
What Can be the Motto of DC Implementation from Siemens's Perspective?
Web-Based Deployment Tool (Available Everywhere) : DC is web-based application and can be available everywhere.
Centralized Orchestration for all TC Environment (Integrate DC with CICD Tools like Jenkins, Azure DevOps, and many more): no need to go and access TC Environment or Servers for any Deployment and feature install or remove.
All Deployment can be Schema or Non-schema All we can do is integrate DC with CICD tools with different approaches. The approach can vary from Organization to Organization and project to project.
UI Base Deployment /Quick Deploy utility Deployment: We can select a Feature from DC's UI or create a Quick Deploy Template to Generate a Deployment kit (no need for UI Bases Deployment Center). Everything can be done via an XML template.
Scalable Environment: We can easily Create the different TC environments Needed for Different Admin Operations like New Environment Creation for Development, Testing, UAT, or Upgrade Operations.
Security: DC is accessible via the Web hence may be a Security vulnerability for all Credentials of the TC environment hence risk can come (DC Vault Come to help )

What amazes me are below Points :
1. Auto war file creation, just copy the created war file and Deploy it.
2. Quick Deploy Utility: do everything in XML and Start deploy
3. Convert env created from TEM to DC by send_configuration_to_dc Utility
4. Diagnostic Checks Everywhere where needed during deployment
5. Password Protected via vault
6. Create a new TC env with no more time. (a little hard in TEM).

There are many Points to add but limits word scope. Add your Thoughts and Comments.
Teamcenter plm DeploymentCenter automation cicd DCwithJenkins

Comments

Post a Comment

Popular posts from this blog

What is a Dispatcher or translator in Teamcenter PLM(Siemens)

  translator is someone who convert one form of data to another form of data i.e. in . layman Term. like Language Translator converts one language to another language and vice versa. but in Teamcenter we are using Dispatcher to Perform different industrial Requirement like 1.CAD Drawing to PDF 2.CAD part to JT 3.Async service (background process) 4.Data share in Supplier connect/Supplier portal Multisite setup 5. MS word to PDF and many more depends on the Teamcenter module and their Dispatcher implementation. What will be the different Requirement and scenarios to convert the data in industry:- Scenario 1 : CAD Engineer Working on NX Software applied one release flag on item revision and after applying release flag on revision for next validation the part is in going to material department ,Purchase Department for validation but this departments not have the access to CAD Software due to NX license COST and material department not need CAD Software. An...
Read more

What is a Teamcenter Upgrade ?

  What is a Teamcenter Upgrade ? process of moving from an older version of the Teamcenter software to a newer version (Major Version Change) Example : TC12 to TC14 ,TC2306,TC2412 etc. What Changes are made from Siemens's Side that we should make to upgrade the Teamcenter Environment? 1. Siemens stopped Support to the Lower Version of Teamcenter: we cannot take any help if something fails in the older version as support stops from Siemens. if something fails we have to continue our work in the same condition without any help 2. Software Version changes in TC Architecture Stack causing software need to upgrade: Teamcenter upgrades ensure compatibility with the latest operating systems, browsers, databases, and third-party tools like NX, Solid Edge, and CAD systems Database. Oracle or MSSQL upgraded their Software with new Features and Stopped support to older versions. Web Tier Oracle WebLogic, Tomcat, and JBOSS  upgraded their version with new features. Upgrade in JAVA Ver...
Read more