Smart PLM Deployment: Deva Prasanna Nandyala, @HCL Technologies, Booth #337

Smart PLM Deployment
09 May 2017, Tuesday
Deva Prasanna Nandyala, @HCL Technologies, Booth #337
Brought to you by:
#PLMConx
Geometric is now part of HCL Technologies
2
Brief Introduction
15+ years of experience in PLM Solution Architecture,

implementations in Automobile and Aerospace industry
Automotive industry (Europe, Asia Pacific & North America) ~ 10+
years Deva Prasanna Nandyala
• Requirement analysis, Functional specification and solution architecture Sr. Solution Architect - PLM
• Engineering process (CAD Mgmt, EBOM Mgmt, Design Release,
Supplier/Partner collaboration, Digital validations etc..)
• Manufacturing Processes (Assembly, BIW) Geometric Europe GmbH
An HCL Technologies Company
• Technology consulting (Teamcenter) for engineering and manufacturing Frankfurter Ring 17
processes 80807 Munich, Germany
Tel: +49 89 37 42 665 00
• IT concepts for Teamcenter infrastructure Mob: +49-173 6289 604
• Application integrations www.hcltech.com
www.hcl.com
• Best practices, Deployment strategy
• Migration concepts for Teamcenter higher versions
American Aerospace OEM: CAD/PLM development
(5 years)
• PLM/CAD tools development
• Priliminary Design
3 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

Contents
 Motivation
 Deployment Challenges
 Teamcenter Rollout Types
 Rollout : Major Version Upgrade
 Smart Upgrade Process Overview
 Identify Component templates & Instantiation
 Traditional Vs Smart deployment
 Smart upgrade – Use existing DB
 Smart upgrade – Use new DB
 Rollout: Minor Upgrade (Patch)
 Rollout: New Features/Enhancements
 Deployment Automation
 Tools used
 Benefits

Motivation
Too
many
sites!!
Too
many Too
Servers!! much
effort!!
Short time Can I

window!! deploy
without
errors??
How can I rollout my release in short time window, but with high quality?

5
Deployment Challenges
Deployment Window Deployment Efforts Risk

• Short Deployment window – • In traditional TC deployment, • High Risk of Rollback due to
In most cases only 16 - 20 most of the components will complex steps involved in
hours window available for be deployed manually. deployment.
deployment tasks.
• Manual deployment requires • Shorter window for validation
• Post deployment, sufficient huge effort. may results into leakage of
time would require for blocker issues which will
Validation before system • High Coordination Effort for impact business continuity
handover to Users. smooth global deployment

6
Teamcenter Rollout Types
1. Major upgrade (Teamcenter version upgrade)

• Introduction of new Teamcenter versions
• Once in 1-2 years
• Very high efforts for upgrading large and horizontally scaled-up environments
2. Minor Upgrade (Teamcenter patches)

• Introduction of new Teamcenter patch updates for OOTB issues, features
• 1-2 times in a year (half-yearly or yearly)
• High efforts for patching large and horizontally scaled-up environments
3. New Features/Enhancements
• Regular deployments with new features and functionalities
• 2-4 times in a year (quarterly or half-yearly)
• Relatively low effort for the rollout

Contents
1. Major upgrade (Teamcenter version upgrade)

• Introduction of new Teamcenter versions
• Once in 1-2 years
• Very high efforts for upgrading large and horizontally scaled-up environments
8 Copyright © 2017 HCL Technologies Limited | www.hcltech.com 8

Smart Upgrade Process Overview
1 Identify Templates & Manage
2 Automate Instantiation
3 Install parallel setup prior to rollout
Upgrade existing DB on the rollout

4 week end
Re-configure parallel setup point to

5 upgraded DB

Identify Component Templates
Templates
1
•1 Teamcenter App Server

4
•2 Teamcenter SSO Server
2 •3 AWC App Server
3
•4 Business Logic Server
5 •5 Dispatcher Client
7
•6 Dispatcher Module
6
•7 FSC Server
•8 Basic Gateway Service
•9 Gateway Service
8 9

Template Instantiation
Identify components for which "Template" can be created

SVN
and multiple instances can be instantiated using the
template V1 V1 V1
BLS VOL 2T
 Business logic server
Automated
 Volume server Scripts
 Web application server
Instantiate Instantiate Instantiate
 FSC cache server etc..,
Templates can be created by installing one of the test
environments
Automated scripts to instantiate the instance from the 1 1
3 1 2 2
template.
2
Script reads a configuration file for all the inputs required
for the creation of instance and populate the template Production Staging
with these inputs
Template
All the instances can be created much before the rollout
Instance
week end

Teamcenter Traditional Upgrade Vs Smart Upgrade
Traditional Deployment
4-8 weeks Around 1 week Around 48 hours
Integration Rollout Prep Rollout

Go Live/
Integration Testing Packaging Rollout Plan Backup Deploy Validate
Rollback
Re-install all servers Upgrade DB

Around 16-20 hours duration
Clone Environment Deployment

4-8 weeks Around 1 week Around 48 hours
Integration Rollout Prep Rollout

Go Live/
Integration Testing Packaging Rollout Plan Backup Deploy Validate
Rollback
Create Templates
Create new Intg Svrs Use tool to create new Prod Svrs with
Upgrade DB Configuration to change DB & Volume
using tool Tool new DB & Volume Tool
Upgrade DB & update Around 6-8 hours duration
config.

Tc Upgrade using Clone Environment Approach (Use Existing DB)
Preparation Rollout
Install Dummy Backup DB Upgrade DB Configure
Around 1 week Around 4 Hours Around 6 Hours Around 4 Hours
Tc BLS#1 Tc BLS#2 Tc BLS#1 Tc BLS#2 Tc BLS#1 Tc BLS#2
Tc BLS#1 Tc BLS#2
Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Active
Ver.A Ver.B Ver.A Ver.B
TcSS Tc Vol#1 TcSS Tc Vol#1 TcSS Tc Vol#1 Inactive

TcSS Tc Vol#1
Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B
Server
Tc 2-Tier Tc Vol#2 Tc 2-Tier Tc Vol#2 Tc 2-Tier Tc Vol#2 for DB
Tc 2-Tier Tc Vol#2
Ver.A Ver.A Ver.B Ver.A Ver.B upgrade
Ver.A Ver.B Ver.A Ver.B Ver.A Ver.B Ver.B Ver.B
Ver.A Ver.B Ver.A
Tc 2-Tier WAS#1 Tc 2-Tier WAS#1 Tc 2-Tier WAS#1

Tc 2-Tier WAS#1
Ver. Ver. Ver. Ver. Ver. Ver.

Ver. Ver.
A B A B A B
A B
PROD PROD New Dummy PROD PROD New Dummy PROD PROD New Dummy
PROD PROD New Dummy
DB Volume DB Volume DB Volume DB Volume DB Volume DB Volume
DB Volume DB Volume
Use new Port Numbers for new
services to avoid any conflict PROD DB Backup
Install New Components with New DB Configure New Components to PROD DB

Take Backup of PROD DB Upgrade PROD DB
& Dummy Volume & PROD Volume

Tc Upgrade using Clone Environment Approach (Use New DB)
Preparation Rollout
Tc BLS#1 Tc BLS#2

TcSS Tc Vol#1
Server
Tc 2-Tier Tc Vol#2 Tc 2-Tier Tc Vol#2 Tc 2-Tier Tc Vol#2 for DB
Tc 2-Tier Tc Vol#2
Ver.A Ver.A Ver.B Ver.A Ver.B upgrade
Ver.A Ver.B Ver.A

Tc 2-Tier WAS#1

Ver. Ver.
A B A B A B
A B
PROD PROD New Dummy
DB Volume DB Volume
Use new Port Numbers for new Export Import
DB DB
Install New Components with New DB Upgrade PROD DB & Import to New Configure New Components to PROD
Take Backup of PROD DB
& Dummy Volume DB Volume

Contents
2. Minor Upgrade (Teamcenter patches)

• Introduction of new Teamcenter patch updates for OOTB issues, features
• 1-2 times in a year (half-yearly or yearly)
• High efforts for patching large and horizontally scaled-up environments

Tc patching using Clone Environment Approach
Preparation Rollout
Tc BLS#1 Tc BLS#2

TcSS Tc Vol#1
Server
Tc 2-Tier Tc Vol#2 Tc 2-Tier Tc Vol#2 Tc 2-Tier Tc Vol#2 for
Tc 2-Tier Tc Vol#2
Ver.A Ver.A Ver.B Ver.A Ver.B patch
Ver.A Ver.B Ver.A

Tc 2-Tier WAS#1

Ver. Ver.
A B A B A B
A B
PROD PROD New Dummy
DB Volume DB Volume
Use new Port Numbers for new
Install New Components with New DB Configure New Components to PROD DB
Take Backup of PROD DB Patch Master Component List
& Dummy Volume & PROD Volume

Contents
3. New Features/Enhancements
• Regular deployments with new features and functionalities
• 2-4 times in a year (quarterly or half-yearly)
• Relatively low effort for the rollout

Deployment Automation
• Automate all the steps in the deployment process Client-Tier

• Wherever possible execute steps in parallel Configurations
Server-Tier Get Latest Build Deploy
• This will lead to drastic reduction in efforts and duration
Web-Tier from SVN
• Chances of error will be very less as manual steps are very less
Stop Services Cleanup Backup Deploy Binaries

• Stop Batch Jobs • Run Clearlocks • Database Backup • Deploy Jar and DLL files
• Stop Dispatcher • Remove all users from DB • Volume Backup (Incremental) • Deploy EAR & WAR files
• Stop WAS & Pool Servers • TC_ROOT, TC_DATA Backup • Deploy XML files
Start Update Configurations Deploy BMIDE Template

Configurations
• Start Pool Servers & WAS • Update Preferences, LOVs • Package custom BMIDE
Preferences template
• Start Dispatcher & Batch jobs • Update Style sheets, etc…
Organization • Generate model.xml
Workflow • Update database
Ruletree
Classification Get Latest Upload in
Queries from SVN TC
Stylesheets
Configurations Get Latest Package Deploy
BMIDE from SVN

Tools
# Tool Phase Tool Functionality

1 SVN Cko Build Check out source code from SVN
This is used to build Client-Tier, Server-Tier, Web-Tier, Configurations, Gateway, SOA Services, Dispatcher taskprep etc…
2 Build Build from source code
This tool executed from a single server to stop different processes in multi server architecture environment.
3 Start & stop Deploy It can stop in 5 minutes vs. 20 minutes of manual work. No need to login to each server and stop services.
4 Backup Deploy To take backup of tc_root , tc_data
5 Clone Tool Deploy Copies Teamcenter environment from source environment to target server.
6 Server Patch Deploy Applies patch on server without opening UI and user interactions. It can be scheduled for night time on servers.
Security Server
7 Deploy Applies patch on server without opening UI and user interactions. Time required will be reduced from 10 min to 1 min.
Patch
8 Web Tier Patch Deploy Applies patch on server without opening UI and user interactions. Time will be reduced from 10 min. to 1 min.
9 BMIDE Deploy Deploy This updates BMIDE template in silent mode and then updates database. No need of any UI/ user interaction.
Configuration This is used to deploy libraries and configurations (Preferences, Workflow, Queries, Rule Tree, etc… ). Copies libraries,
10 Deploy
Deploy exe, lang folder, text server files to multiple servers. Admin will receive a html report in via email

Case Study: Clone Environment Approach at European Automotive Company
Major Benefits
• 50% to 60% reduction in deployment duration
• Up to 60% reduction in deployment efforts
• Zero error in deployment
• Integration env consistent with production env as same templates are used.

Continuous Integration Process
3.
Automatic
Deploy
1. Automatic Code Build (B)

2. 4. 2. Code Quality Check (Q)
Code Quality Automatic
Check Testing 3. Automatic Deploy (D)
Continuous 4. Automatic Testing (T)
Integration 5. Manage Packages in Repository (P)
5.
1. Manage
Automatic Packages in
Code Build Repository

Continous Integration Architecture for Teamcenter Agile rollout
Jenkins
Server Linux
Jenkins as the master build server SVN
(Master build)
Project-1 2
Repository
Configuration of Jenkins jobs for Configuration
C ++ Qua lity Checks
Ja va Quality Checks
Project-1
4 t1 t2 t3
various development teams BRANCH_p1 Build 1
Check-out
Project-1
Auto Regression
Quality Chk 2 TC ENV 1 Test
BRANCH_p2 t1 t2 t3
Jenkins integration with the below Deploy 3 1 3
ART TC-INT
TRUNK Auto Test 4
TC_ROOT
needs to configured SOA_LIB t1 t2 t3
Project-2 B,Q,D,T
 Sonar for quality checks
Configuration
 ALM for auto regression test Build 1
TC ENV 2
Auto Regression Legend:
Test B: Automatic Build
Quality Chk 2
 Nexus for managing packages 1 3
Q: Quality Check
Check-in Deploy 3 TC_ROOT
ART D: Automatic Deploy
T: Automatic Testing
Configure Windows Slave for Auto Test 4 SOA_LIB
P: Manage Packages
Jenkins with TC-INT

B,Q,D,T
Configuration
 UFT (Unified Functional Testing) Build 1
PRE-INT
INT
Auto Regression
Test
 ALM integration Quality Chk 2 1 3
TC_ROOT ART
5
Deploy 3 SOA_LIB ART

Project-1 Project-2 Auto Test 4
Manage Pkg 5 B,Q,D,T,P D,T,P
3
Jenkins Slave
Windows
ALM Integration
Agile Rollout with Continuous Integration
Continuous Integration 0.5 week 3 weeks

0.5 week
 Complete automation of build, BF0 BF1 BF2 BF3

deploy Go-Live
Every Week
 Code quality checks are part of CI BuildDeployTest
Integration (INTEG Env)
PROD Rollout
in INTEG environment Plan & Prep Integration (INT
process
D,T
 Regression testing D,P
 Manage Packages Every day

BuildDeployTest
Every day build-deploy-test in in PRE-INT Pre-Integration (STAGING env) Pre-Integration (STAGING env)
environment
PRE-INT environment B,Q,D,T
Legend:
Every week build-deploy-test in B: Automatic Build
Q: Quality Check
INT environment D: Automatic Deploy
T: Automatic Testing
Manual
SVN
P: Manage Packages Merge
Agile PROD Rollout every month
Every day
Feature 1: Development (SCRUM team)
All development teams must be BuildDeployTest
in Poejct‘s TEST
forced to use same CI process for environment
Feature 2: Development (SCRUM team)
better quality

Benefits
TIME COST QUALITY

• Signification reduction in • Significant reduction in total • Almost No errors due to high
deployment duration Efforts and Cost due to high automation
automation
• Ensures Business Continuity • Sufficient time for validation
• Low Coordination Efforts after deployment
• Quick rollback if needed
• Consistency between • Low Risk as Most of the
• Agile rollout enables more no. Production and Integration is validation can be done in
of deployments in less time maintained as same advance
templates are used
• High quality of deliverables
due to CI process

For any discussion, please contact:
Deva Prasanna Nandyala

Sr. Solution Architect - PLM
Geometric Europe GmbH
An HCL Technologies Company
Email: DevaPrasanna.Nandyala@hcl.com
Phone: +49 173 6289 604

Thank You
Your feedback is important.
Please fill out the Session Survey in the Mobile App.

• Locate the session in the app
• Select “Take Survey”
Deva Prasanna Nandyala, @HCL Technologies, Booth #337

Brought to you by:
#PLMConx

Smart PLM Deployment: Deva Prasanna Nandyala, @HCL Technologies, Booth #337

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Smart PLM Deployment: Deva Prasanna Nandyala, @HCL Technologies, Booth #337

Uploaded by

Copyright:

Available Formats

Smart PLM Deployment

09 May 2017, Tuesday

Deva Prasanna Nandyala, @HCL Technologies, Booth #337

Brought to you by:

15+ years of experience in PLM Solution Architecture,

3 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

4 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

Short time Can I

5 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

Deployment Window Deployment Efforts Risk

6 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

1. Major upgrade (Teamcenter version upgrade)

2. Minor Upgrade (Teamcenter patches)

7 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

1. Major upgrade (Teamcenter version upgrade)

8 Copyright © 2017 HCL Technologies Limited | www.hcltech.com 8

1 Identify Templates & Manage

3 Install parallel setup prior to rollout

Upgrade existing DB on the rollout

Re-configure parallel setup point to

9 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

•1 Teamcenter App Server

10 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

Identify components for which "Template" can be created

11 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

Integration Rollout Prep Rollout

Re-install all servers Upgrade DB

Clone Environment Deployment

Integration Rollout Prep Rollout

12 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

TcSS Tc Vol#1 TcSS Tc Vol#1 TcSS Tc Vol#1 Inactive

Tc 2-Tier WAS#1 Tc 2-Tier WAS#1 Tc 2-Tier WAS#1

Ver. Ver. Ver. Ver. Ver. Ver.

Install New Components with New DB Configure New Components to PROD DB

13 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

TcSS Tc Vol#1 TcSS Tc Vol#1 TcSS Tc Vol#1 Inactive

Tc 2-Tier WAS#1 Tc 2-Tier WAS#1 Tc 2-Tier WAS#1

Ver. Ver. Ver. Ver. Ver. Ver.

14 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

2. Minor Upgrade (Teamcenter patches)

15 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

TcSS Tc Vol#1 TcSS Tc Vol#1 TcSS Tc Vol#1 Inactive

Tc 2-Tier WAS#1 Tc 2-Tier WAS#1 Tc 2-Tier WAS#1

Ver. Ver. Ver. Ver. Ver. Ver.

16 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

17 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

• Automate all the steps in the deployment process Client-Tier

Stop Services Cleanup Backup Deploy Binaries

Start Update Configurations Deploy BMIDE Template

18 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

# Tool Phase Tool Functionality

4 Backup Deploy To take backup of tc_root , tc_data

19 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

20 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

1. Automatic Code Build (B)

21 Copyright © 2017 HCL Technologies Limited | www.hcltech.com

various development teams BRANCH_p1 Build 1

needs to configured SOA_LIB t1 t2 t3

Jenkins with TC-INT

Deploy 3 SOA_LIB ART

Continuous Integration 0.5 week 3 weeks

 Complete automation of build, BF0 BF1 BF2 BF3

 Manage Packages Every day