Confirm your Windchill on its new server.
Note: This is not meant to be an all-inclusive, fully detailed guide to transition Windchill to your private Azure cloud. PTC has many options for additional Windchill-specific help, which are the Support team, your PTC Customer Success Manager, Success Management, or any of our well-qualified partner service providers. For further questions about Azure, please contact your Microsoft representative.
Before you begin, complete these steps:
Thoroughly vet the application in a test/QA environment following the testing plan you created during planning:
Rely on your current test plan for issue identfication and resolution management.
The final smoke test will help you determine whether the application is ready to deploy. If any issues arose during the unit, functional and/or user acceptance testing; re-test to ensure they’re fixed. Run through several test scenarios, like adding a new user or interacting with a Mashup. Double-check your integrations for data leakage.
Test the application in a test/QA environment with a few existing users to ensure their experience has not changed. PTC recommends that you take time to set user expectations as appropriate to testing for an infrastructure transition. The Azure-based system should have pre-defined performance and other metrics, and the users must understand those targets and cautioned against anecdotal observations or comparisons of performance against the on-premises system. Technical validation vs normal user day to day validation.
User Acceptance Testing should address questions like:
You may learn essential insights during this phase and choose to act on them later. If the system is missing portions of the end user’s needs, you will need to evaluate additional training or ways to stop that gap.
Once assets are connected, and data is flowing, perform a variety of load tests to check whether system load, performance, and availability are acceptable. For example, if you expect data to travel from an asset through the application in 5 seconds, verify the application is delivering that level of performance. Be sure your server is large enough to handle the data. Be realistic about your expectations: the faster your system, the higher your server and associated network costs.
It’s important to stress test the system. Test the user load and device input load. Simulate several scenarios—including less-likely situations when the system is processing more data than expected. For example, if your application is expected to process 10 megabytes per minute, apply a factor of safety to be sure you can handle times of unusually high demand in a cost-effective manner. While these scenarios may be uncommon, we recommend you prepare the system to handle them.
Did you find this helpful?
Find step-by-step instructions and information about moving Windchill to Azure cloud in the Help Centers.
Visit the PTC Windchill Community to get product assistance, share ideas, and browse information about using Windchill.
Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.