Best Practices for the Update Process
The following items list best practices to follow when planning or implementing an update:
• Keep logs illustrating all changes made to the system (for example, the commands that were executed and the resulting output).
• Address any errors before proceeding to the next step in the update process.
• Ensure that the test system data closely emulates the production data.
• Ensure that the PTC FlexPLM source system is backed up and that the database, vault, and LDAP backups are done during the same downtime period. Failure to do this results in incompatible data in the database, vault, and LDAP backups.
• Practice the update multiple times until there are no errors before attempting the production update.
• Include post-update user testing (and even malicious user testing). This testing is critical, because many issues are discovered after the test system is updated during user testing.
• Identify issues before a production update to increase user acceptance and reduce downtime.
• Incorporate time (many weeks) into your update plan for troubleshooting issues and patch delivery.
• Do not make any changes to the system during the update. This includes applying patches or additional maintenance releases.
• Do not change hardware during the update. This introduces additional risk and difficulty in troubleshooting update issues.
• Perform the test update on one server that contains both a test source installation and a test target installation.
Follow these steps to gather the necessary materials for your update:
2. Use the following list of PTC FlexPLM images:
◦ PTC FlexPLM 11.0 M030 for Windchill PDMLink 11.0 M030
◦ Latest PTC FlexPLM rolling (cumulative) patch for PTC FlexPLM 11.0 M030 (if any exists)
3. Extract the ZIP files into a staging area of your choice for the CDs.
|
|
PTC requires sites to use the latest rolling (cumulative) patches for PTC FlexPLM. Contact PTC technical support for the latest PTC FlexPLM rolling (cumulative) patches for PTC FlexPLM 11.0 M030.
|
