Upgrading to windchill 11 - · PDF file# L I V E W O R X 11 •Windchill 11 –Will be...
-
Upload
phungkhuong -
Category
Documents
-
view
218 -
download
1
Transcript of Upgrading to windchill 11 - · PDF file# L I V E W O R X 11 •Windchill 11 –Will be...
liveworx.com # L I V E W O R X
UPGRADING TO WINDCHILL 11.0
Andy Hermanson & Leo Schleicher Windchill System Adminstrators
2 # L I V E W O R X
AGENDA
1. Introduction – Daktronics – Speakers
2. Why are we upgrading?
3. Current State
4. Future State
5. How do we get there?
6. Conclusion
7. Q/A
Daktronics is
the world leader
in dynamic
audio-visual
communications
systems
# L I V E W O R X 6
• Lives in Garretson, SD – Love to hunt, fish and shooting sports. – 2 Kids
• Windchill Admin - ~2 years
• Former MCAD Admin - ~3 years
• 8 years Mechanical Design
• 12 years with PTC products
ANDY HERMANSON
# L I V E W O R X 7
• Lives in Brandon, SD – I enjoy football, computers, spending time with my wife and 2 children.
• 4 Years working in IT and Technical Support at Daktronics
• Windchill System Administrator since November 2016
• 4 Years in Mechanical Design in the automotive industry
• Setup, maintain, and troubleshoot Windchill systems
LEO SCHLEICHER
# L I V E W O R X 8
• New Features – Change Management
• Improved flexible change links
– ECAD Workgroup Managers – Classification integration into keyword search
• Bug Fixes – Nonconformance bug fixes.
• Tool and application support – Newer versions of Creo, AutoCAD, CreoView adapters. – We upgrade Creo quickly with each new release. – We upgrade AutoCAD every two years, which drives Windchill upgrade
• Business Requirements – We try to stay current with CPS patches. – Upgrade to support new versions of Windows Server.
WHY ARE WE UPGRADING TO WINDCHILL 11?
# L I V E W O R X 9
• Production Windchill Setup – Currently on Windchill 10.2 M030 CPS23 – Production server is in Brookings with replication servers in China, Ireland and Belgium
• Windchill Application Server – Running Windows Server 2008 R2 on 7 year old physical hardware. – 8 cores, 96 GB RAM with a 7+ TB Vault drive – 8 Method Servers, 2 Background Method Servers
• Oracle setup – Running Windows Server 2008 R2 – Oracle 11g – 8 core, 48 GB RAM, 600 GB Database
STATE OF CURRENT WINDCHILL PRODUCTION ENVIRONMENT
# L I V E W O R X 10
• Test Windchill Environments – User Acceptance Testing – Test environment – Development environment
• Test environment setup – Running Windows Server 2012 R2 virtual machines on test environments – Oracle 12c – 2-4 Method servers per system
• All environments total 34 systems – App and Oracle Servers – Publisher servers – System Monitor – ThingWorx – Replication Servers
STATE OF CURRENT WINDCHILL TEST ENVIRONMENTS
# L I V E W O R X 11
• Windchill 11 – Will be on Windchill 11 M030 CPS?? – Production server is in Brookings with replication servers in China, Ireland and Belgium – Expected implementation date - October 2017
• Windchill Application Server – Running Windows Server 2016 on new VM cluster – 12 cores, 128 GB RAM with a 10+ TB Vault drive – 8 Method Servers, 2 Background Method Servers
• Database Server – Running Windows Server 2016 – SQL Server 2016 – 12 cores, 128 GB RAM 1TB Database Storage
FUTURE STATE OF WINDCHILL ENVIRONMENT
# L I V E W O R X 12
• Use WinDU to clean up database and system using the system health check.
• Use WinDU Mandatory Upgrade tasks.
• Use PTC knowledge base articles to correctly identify and run the appropriate WinRU tasks to minimize issues during the upgrade process.
• FTHealer patch to fix family table errors.
• Contact PTC Support with any errors or assistance.
WINDU/ WINRU MAINTENANCE
# L I V E W O R X 13
• Understand how the WCA (Windchill Configuration Assistant) works and what it’s modifying in the system.
• Run the WCA on a regular maintenance schedule.
• We run our quarterly on our production environments. – Verify that everything is setup and ran before your migration.
WCA
# L I V E W O R X 14
• Separate install of the Index Sever after Windchill is installed.
• Out of the box indexing server setup required modification to be setup as a service.
• Install_solr_service.bat file needs to be modified as it points to SolrServer.exe and needs to be changed to SolrServer-64.exe.
INDEX SERVER INSTALL
# L I V E W O R X 15
WORKGROUP MANAGERS
• Workgroup Managers are no longer part of the installers and are
installed separately.
• Individual Workgroup Managers and versions can be installed as
necessary.
# L I V E W O R X 16
• Ran into issues with LDAP
• Vault Configuration
• OIR Issues with Migration
UPGRADE MANAGER
# L I V E W O R X 17
• Understanding of how your company LDAP works.
• We struggled with getting the upgrade manager to work because of this.
UPGRADE MANAGER - LDAP
# L I V E W O R X 18
• To get the errors to go away on Vaults and File Servers page, you need to click on a different tab and click back on Vaults and File Servers.
UPGRADE MANAGER – VAULTS AND FILE SERVERS
# L I V E W O R X 19
• We encountered a problem with OIR’s where the Site level OIR was disabled and the Org level OIR was enabled.
– We had modified the Change Activity OIR at the Org level and enabled it. – We disabled the Change Activity at the Site level. – When running the migration tool, the migration would error.
• The solution was to disable the Org level OIR and enable the Site level OIR on the Windchill 10.2 system prior to backing up the database.
– After the 10.2 database is imported into the Windchill 11.0 system, the migrator will run successfully because of this solution.
– Once the Windchill 11.0 system is up and running, you can change the Org and Site levels back.
MIGRATOR ISSUES
# L I V E W O R X 20
• On Windows Server 2012 R2, we noticed that we had to have everything setup to run as Administrator to get it to work correctly, which was different than Server 2008.
• We setup the Windchill Server service as a dependent to Windchill DS to ensure they startup in the correct order on reboot.
• Oracle 12c required us to create it’s own administration account that wasn’t required on previous Oracle versions.
• Clean up vaults by removing unreferenced files and re-vaulting which will reduce file transfer times.
TIPS AND GOTCHAS
# L I V E W O R X 21
• Migration Time – Database Size – 500GB – 2-3 Hours
• Help from vendors – Fishbowl – LDAP and Vault configuration – PTC ticket to solve the OIR issues
• Timeline – Going to go live with Production environment in October 2017. – Switching to SQL database this summer.
HOW DO WE GET THERE?
# L I V E W O R X 22
• Questions?
CONCLUSION
23 # L I V E W O R X
WE WANT YOUR FEEDBACK Please remember to complete
your evaluation by selecting
the session in your mobile app.
Survey
liveworx.com # L I V E W O R X