Shearrow, Charles A.

Topics covered include: The Frugal Times Historical Upgrade Process; Planning for Possible Constraints; PTC Compatibility Matrix; In-Place Upgrade Process; Pre-Upgrade Activities; Upgrade Activities; Post Upgrade Activities; Results of the Upgrade; Tips for an Upgrade On a Shoestring Budget

NASA Technical Reports Server

Successful Strategies for Rapidly 
Upgrading PTC Windchill 9.1 to 
Windchill 10.1 on a Light Budget
Dr. Charles A. (Chip) Shearrow
Senior Systems Engineer, Operations Supervisor
PTC Live Global 2013, June 9 – 12, Anaheim California
https://ntrs.nasa.gov/search.jsp?R=20130013841 2019-08-29T15:29:20+00:00Z
2Biography
Dr. Charles A. (Chip) Shearrow
Public  Release #  xxxx
• 1991-June 2000:  Ohio Northern University (Advanced Robotics and 
Automation)
• 1998- Summer:  Proposal for the Design Data Management System
• 1999- Summer:  NASA-JSC Directors Grant for Virtual Simulation
• June 2000- 2011:  Indyne, Inc. at NASA-JSC (Pro/E User, Intralink 
Administrator, Workflows, Training,  Operations Lead, Supervisor, Senior 
Systems Engineer)
• January 19, 2011- Present:  MEI Technologies at NASA-JSC (IRD 
Operations Supervisor, Senior Systems Engineer)
• Email- Charles.a.shearrow@nasa.gov
• MEI Technologies - http://www.meitechinc.com
3Introduction
Public  Release #  xxxx
• The Frugal Times
• Historical Upgrade Process
• Planning for Possible Constraints
• PTC Compatibility Matrix
• In-Place Upgrade Process
• Pre-Upgrade Activities
• Upgrade Activities
• Post Upgrade Activities
• Results of the Upgrade
• Tips for an Upgrade On a Shoestring Budget
• Questions
4The Frugal Times
Public  Release #  xxxx
• Economic uncertainty
– Economy
– Continuing Resolution
– Shift to commercial space flight
• Budget restraints
– Personnel reductions
– Environment reductions
– New equipment guidelines 
• Still need to maintain corporate operations
– Operations for Johnson Space Center
– Managing engineering data for International Space Station flights
– Operations for general research
– Managing engineering data for Multi Purpose Crew Vehicle (MPCV)
– Staying current with software and hardware
5Historical Upgrade Process
Public  Release #  xxxx
• Purchase/ obtain new servers for the upgraded environments
• Establish additional network and storage resources
• Establish the new system environments
• Integrate Active Directory (AD) authentication with webserver
• Load Windchill and integration custom code
• Run WinDU reports and repair data if needed
• Load systems with production data
• Regression test systems 
• Train users
• Perform many runs against the database
• Release system to users                  (8.0 to 9.1 took 15 months to complete)
6Planning for Possible Constraints
Things to Consider:
Public  Release #  xxxx
• Age of the current hardware
– Speed and capability of the current 
servers to support new software
– When is the refresh planned 
• Technological Changes
– Traditional racked servers?
– Virtual servers local?
– Virtual servers remote?
– Cloud services?
• Budget challenges
– Reduced services
– Reduced personnel
– Customer initiated paradigm shift
• User Environment
– Constantly changing with no control 
of the changes and their timing
• Corporate events
– Management tasks
– Contracts changing
– Personnel changes
– Environmental changes
– Policy changes
• Software compatibility between:
– Current and upgraded  PDMLink 
system
– CAD software and PDMLink
– Web browser and CAD software
– Workstation OS and web browser
• Critical software release dates
– Contracts using the system
– Major events with projects
– User training
– PTC release dates
7PTC Compatibility Matrix
Quick View
Public  Release #  xxxx
PDMLink 9.1 M50
Current
PDMLink 9.1 M50
Transition
PDMLink 10.1 M30 
Upgraded 
Solaris OS 10
03/05
Solaris OS 10
08/11
Solaris OS 10
08/11
Java 1.6.0_18 Java 1.6.0_33 Java 1.6.0_33
Oracle 10.2.0.4 Oracle 11.2.0.3 Oracle 11.2.0.3
DS 1.2 DS 1.3 DS 1.3
Tomcat 6.0.20 Tomcat 6.0.20 Integrated in 
Method Server
Apache 2.2.15 Apache 2.2.21 Apache 2.2.21
CAD Workers     
WF4
CAD Workers     
WF5
CAD Workers     
Creo 2
Reference: Windchill90M080SoftwareMatrices081909.pdf
8PTC Compatibility Matrix
Public  Release #  xxxx
9In Place Upgrade Process
All activities performed in all existing environments
Public  Release #  xxxx
• Pre-upgrade Activities
– Run WinDU reports to insure data transferability
– Upgrade server
– Upgrade Windchill components
– Upgrade database
– Build migration installation
• Upgrade Activities
– Move migration installation
– Run migration tool
– Upgrade Apache
– Test upgrade
• Post Upgrade Activities
– Establish keyword index
– Bulk publish viewables
– Rerun WinDU reports
10
Pre-Upgrade Activities
Public  Release #  xxxx
• Run WinDU reports
– To insure data integrity for migration
– Roughly 14 million objects including
Apollo, Shuttle, Station to Multi 
Purpose Crew Vehicle (MPVC) or Orion
• Upgrade server
– Solaris upgrade from version10 03/05
to Solaris 10 08/11
– Upgrade file system to ZFS for file 
system and volume management, 
snapshots and clones, continuous 
integrity checking and automatic repair
– Java upgrade from 1.6.0_18 to 
1.6.0_27 for compatibility and security
• Upgrade Database
– From Oracle 10.2.0.4 to 11.2.0.3+
• Build Migration Installation
– To be used for the upgrade manager
– Testing the upgraded customizations 
• Directory Service (DS) Upgrade
– From 1.2 to 2.3  
• PSM Install
– Monitor usage before and during rollout 
– Tuneing of the new system
• MCAD Workers Upgrade
– From WF4 to Creo2
• Customizations Upgrade
– From 9.1 M50 to 10.1 M30
– Minimize moving forward 
customizations 
All performed in place on existing environments
11
Upgrade Activities
Public  Release #  xxxx
• Move 10.1 System
– Move to the master servers file system for speed
– Can be done on a live system
– Live system is stopped once to test migration system
– Test functionality
• Apache Upgrade to 2.2.21
– Place in environment
– Test for functionality
• Run Upgrade Manager
– Backup database and code base
– Redirect resources between 9.1 and 10.1 PDMLink
– Run upgrade
– Test upgraded system
12
Post Upgrade Activities
Public  Release #  xxxx
• Viewable Regeneration
– Bulk publish all the CAD objects in the system 
• Indexing Generation 
– Reindex the system with SOL (new indexing software)
• Documents first
• Larger files second
• Zip and last
• WinDU Reports for 10.1 
– Run to insure data integrity after upgrade
– Create a baseline for future loads
• Resource Return
– Return virtuals used for upgrade
– Return storage copies used for upgrade
13
Results of The Upgrade
Public  Release #  xxxx
• System outage started on Thursday April 4th at 5:00pm
– Ended on XXXX
• Backups ran from xxx to xxx
• Upgrade Manager ran from xxx to xxx
• Regeneration of Viewables
– ran from xxx to xxx
• Regeneration of Keyword Index Status
– XXX
• WinDU Reports for 10.1 results
– XXX
14
Tips for An Upgrade On A Shoestring Budget
Public  Release #  xxxx
• Upgrade current system components in place                                    
avoiding the purchase of new hardware
• Migration environment can be a virtual machine                                    
zoned on one of the existing servers
• Transferring the migration environment to the same server as the 
environment to be upgraded eliminates all the network slowness
• The only extra resource needed was the storage for the production 
database and for the data to be placed against the staging environment 
for a one to one comparison run against the production environment.
• Coordinate the upgrade with everyone from the users to management to 
avoid scheduling pitfalls and software incompatibilities
• To use the updated DS with 9.1, you will have to obtain a “fix” from PTC
15
Tips for An Upgrade On A Shoestring
Public  Release #  xxxx
• Upgrade
16
Questions
Public  Release #  xxxx
l iveglobal.ptc.com 


Successful Strategies for Rapidly Upgrading PTC Windchill 9.1 to Windchill 10.1 on a Light Budget

Successful Strategies for Rapidly 
Upgrading PTC Windchill 9.1 to 
Windchill 10.1 on a Light Budget
Dr. Charles A. (Chip) Shearrow
Senior Systems Engineer, Operations Supervisor
PTC Live Global 2013, June 9 – 12, Anaheim California
https://ntrs.nasa.gov/search.jsp?R=20130012744 2019-08-31T00:46:45+00:00Z
2Biography
Dr. Charles A. (Chip) Shearrow
Public  Release #  xxxx
• 1991-June 2000:  Ohio Northern University (Advanced Robotics and 
Automation)
• 1998- Summer:  Proposal for the Design Data Management System
• 1999- Summer:  NASA-JSC Directors Grant for Virtual Simulation
• June 2000- 2011:  Indyne, Inc. at NASA-JSC (Pro/E User, Intralink 
Administrator, Workflows, Training,  Operations Lead, Supervisor, Senior 
Systems Engineer)
• January 19, 2011- Present:  MEI Technologies at NASA-JSC (IRD 
Operations Supervisor, Senior Systems Engineer)
• Email- Charles.a.shearrow@nasa.gov
• MEI Technologies - http://www.meitechinc.com
3Introduction
Public  Release #  xxxx
• The Frugal Times
• Historical Upgrade Process
• Planning for Possible Constraints
• PTC Compatibility Matrix
• In-Place Upgrade Process
• Pre-Upgrade Activities
• Upgrade Activities
• Post Upgrade Activities
• Results of the Upgrade
• Tips for an Upgrade On a Shoestring Budget
• Questions
4The Frugal Times
Public  Release #  xxxx
• Economic uncertainty
– Economy
– Continuing Resolution
– Shift to commercial space flight
• Budget restraints
– Personnel reductions
– Environment reductions
– New equipment guidelines 
• Still need to maintain corporate operations
– Operations for Johnson Space Center
– Managing engineering data for International Space Station flights
– Operations for general research
– Managing engineering data for Multi Purpose Crew Vehicle (MPCV)
– Staying current with software and hardware
5Historical Upgrade Process
Public  Release #  xxxx
• Purchase/ obtain new servers for the upgraded environments
• Establish additional network and storage resources
• Establish the new system environments
• Integrate Active Directory (AD) authentication with webserver
• Load Windchill and integration custom code
• Run WinDU reports and repair data if needed
• Load systems with production data
• Regression test systems 
• Train users
• Perform many runs against the database
• Release system to users                  (8.0 to 9.1 took 15 months to complete)
6Planning for Possible Constraints
Things to Consider:
Public  Release #  xxxx
• Age of the current hardware
– Speed and capability of the current 
servers to support new software
– When is the refresh planned 
• Technological Changes
– Traditional racked servers?
– Virtual servers local?
– Virtual servers remote?
– Cloud services?
• Budget challenges
– Reduced services
– Reduced personnel
– Customer initiated paradigm shift
• User Environment
– Constantly changing with no control 
of the changes and their timing
• Corporate events
– Management tasks
– Contracts changing
– Personnel changes
– Environmental changes
– Policy changes
• Software compatibility between:
– Current and upgraded  PDMLink 
system
– CAD software and PDMLink
– Web browser and CAD software
– Workstation OS and web browser
• Critical software release dates
– Contracts using the system
– Major events with projects
– User training
– PTC release dates
7PTC Compatibility Matrix
Quick View
Public  Release #  xxxx
PDMLink 9.1 M50
Current
PDMLink 9.1 M50
Transition
PDMLink 10.1 M30 
Upgraded 
Solaris OS 10
03/05
Solaris OS 10
08/11
Solaris OS 10
08/11
Java 1.6.0_18 Java 1.6.0_33 Java 1.6.0_33
Oracle 10.2.0.4 Oracle 11.2.0.3 Oracle 11.2.0.3
DS 1.2 DS 1.3 DS 1.3
Tomcat 6.0.20 Tomcat 6.0.20 Integrated in 
Method Server
Apache 2.2.15 Apache 2.2.21 Apache 2.2.21
CAD Workers     
WF4
CAD Workers     
WF5
CAD Workers     
Creo 2
Reference: Windchill90M080SoftwareMatrices081909.pdf
8PTC Compatibility Matrix
Public  Release #  xxxx
9In Place Upgrade Process
All activities performed in all existing environments
Public  Release #  xxxx
• Pre-upgrade Activities
– Run WinDU reports to insure data transferability
– Upgrade server
– Upgrade Windchill components
– Upgrade database
– Build migration installation
• Upgrade Activities
– Move migration installation
– Run migration tool
– Upgrade Apache
– Test upgrade
• Post Upgrade Activities
– Establish keyword index
– Bulk publish viewables
– Rerun WinDU reports
10
Pre-Upgrade Activities
Public  Release #  xxxx
• Run WinDU reports
– To insure data integrity for migration
– Roughly 14 million objects including
Apollo, Shuttle, Station to Multi 
Purpose Crew Vehicle (MPVC) or Orion
• Upgrade server
– Solaris upgrade from version10 03/05
to Solaris 10 08/11
– Upgrade file system to ZFS for file 
system and volume management, 
snapshots and clones, continuous 
integrity checking and automatic repair
– Java upgrade from 1.6.0_18 to 
1.6.0_27 for compatibility and security
• Upgrade Database
– From Oracle 10.2.0.4 to 11.2.0.3+
• Build Migration Installation
– To be used for the upgrade manager
– Testing the upgraded customizations 
• Directory Service (DS) Upgrade
– From 1.2 to 2.3  
• PSM Install
– Monitor usage before and during rollout 
– Tuneing of the new system
• MCAD Workers Upgrade
– From WF4 to Creo2
• Customizations Upgrade
– From 9.1 M50 to 10.1 M30
– Minimize moving forward 
customizations 
All performed in place on existing environments
11
Upgrade Activities
Public  Release #  xxxx
• Move 10.1 System
– Move to the master servers file system for speed
– Can be done on a live system
– Live system is stopped once to test migration system
– Test functionality
• Apache Upgrade to 2.2.21
– Place in environment
– Test for functionality
• Run Upgrade Manager
– Backup database and code base
– Redirect resources between 9.1 and 10.1 PDMLink
– Run upgrade
– Test upgraded system
12
Post Upgrade Activities
Public  Release #  xxxx
• Viewable Regeneration
– Bulk publish all the CAD objects in the system 
• Indexing Generation 
– Reindex the system with SOL (new indexing software)
• Documents first
• Larger files second
• Zip and last
• WinDU Reports for 10.1 
– Run to insure data integrity after upgrade
– Create a baseline for future loads
• Resource Return
– Return virtuals used for upgrade
– Return storage copies used for upgrade
13
Results of The Upgrade
Public  Release #  xxxx
• System outage started on Thursday April 4th at 5:00pm
– Ended on XXXX
• Backups ran from xxx to xxx
• Upgrade Manager ran from xxx to xxx
• Regeneration of Viewables
– ran from xxx to xxx
• Regeneration of Keyword Index Status
– XXX
• WinDU Reports for 10.1 results
– XXX
14
Tips for An Upgrade On A Shoestring Budget
Public  Release #  xxxx
• Upgrade current system components in place                                    
avoiding the purchase of new hardware
• Migration environment can be a virtual machine                                    
zoned on one of the existing servers
• Transferring the migration environment to the same server as the 
environment to be upgraded eliminates all the network slowness
• The only extra resource needed was the storage for the production 
database and for the data to be placed against the staging environment 
for a one to one comparison run against the production environment.
• Coordinate the upgrade with everyone from the users to management to 
avoid scheduling pitfalls and software incompatibilities
• To use the updated DS with 9.1, you will have to obtain a “fix” from PTC
15
Tips for An Upgrade On A Shoestring
Public  Release #  xxxx
• Upgrade
16
Questions
Public  Release #  xxxx
l iveglobal.ptc.com 


Successful Strategies for Rapidly Upgrading PTC Windchill 9.1 to Windchill 10.1 on a Light Budget

Abstract

Similar works

Full text

Available Versions

NASA Technical Reports Server

NASA Technical Reports Server