Hi @NERaj
I was hoping some of our community members would weigh in regarding the question of stability around ThingWorx 10.x, but since no one has responded, I'm happy to provide some insights.
From reviewing the cases that have been opened, the majority of questions/issues revolve around installation/upgrade. An analysis of these cases has led to a few documentation improvements (still pending). To avoid some of the issues that have been reported, here are some pointers:
- When planning an implementation or upgrade, always check Release Advisor for determining compatibility with JIRA, the RDBMS, and the operating system (include Tomcat if manually installing ThingWorx). We're often asked if our products will work with a specific version of java, Tomcat, o/s, or database not listed in Release Advisor. Keep in mind, that if it's not listed, it isn't supported. Even if you get it to work initially, you may discover issues down the road as you utilize different features within the product.
- If upgrading, always create adequate backups to include database dumps, VM snapshots, etc. before starting the process. You will want the ability to revert if something goes wrong.
- Always read the installation/upgrade documentation in the Help Center.
Many of the ThingWorx 10.x cases that have been opened are not specific to the 10.x release. These can range from configuration issues, troubleshooting error messages, etc. Always read the Help Center documentation and if you find something that isn't clear, let us know so we can submit an improvement request.
From the cases we've received so far, ThingWorx 10.x appears very stable. This latest release contains security improvements, bug fixes, and new features, making it the best choice when deciding on the version for installation or upgrade. That being said, when upgrading, it is always recommended to build an environment specifically for testing your upgrade procedures and fully regression testing your mashups, connections, etc. before upgrading Prod. It's recommended that you refresh this environment from Prod in order to assess timings needed for the actual Prod upgrade.
Regards.
--Sharon