Deploy your IoT applications for testing and follow your DevOps and testing processes. Then decide whether to promote your solution to production.
Before you begin, complete these steps:
Deploy your ThingWorx applications to your test or QA environments and follow your DevOps processes. Make sure you know:
Be aware of the capacity you need in each environment to test as you go. Some of your environments may be temporary but serve specific purposes. Document your work through this process.
Make sure users have access to the right components within the application. Have several users log in to ThingWorx in a test/QA environment. They should verify they have access to everything they need. Test the user permissions for each user group (administrator, developer, user, etc.). If someone can’t access a mashup or if they have too much access, change their permissions.
Also, verify that each environment shows the appropriate data for each user group. You may need to strip production data from some environments. Do this to prepare for testing, especially user acceptance testing.
Transition your integrations to start feeding data into ThingWorx. After you turn on the integrations, verify the data is flowing from the asset/tool/system as expected. Make sure you’re not receiving extraneous data.
If you’re moving from a legacy system, compare the data from the old system with what you see in ThingWorx. The data should be identical. Monitor the data for several hours before you continue through deployment.
Follow the testing plan you created earlier to thoroughly test the application(s) and verify the package. Testing is an iterative process. If you find issues, go back to your development environment to fix them. Do not make any changes to code in environments other than your development environment. Remember to document code as you write and record test results.
Test the application in a test/QA environment with a few potential users (service technicians or other available participants) to make sure that what you built meets their needs. User acceptance testing should answer questions like:
You may get insights during testing and choose to act on them later. If the application does not meet all user needs, decide whether to pause deployment or to launch as-is.
Once you perform testing in your test or QA environment and you’ve verified test results, decide whether to promote the code to production. Going to production will “publish” your application, deploying it to the field. Make sure you have a backup in place before you promote to production. If you followed a DevOps process, your work should already be backed up.
To promote to production, the developer/architect will import data and entities to the production server. If issues come up, do not make changes to the application in the production environment.
Once the technical team successfully deploys the application, give an update to the project team members and stakeholders. The application is now collecting real data, communicating with your assets, and is available for use.
In addition to the recommended resources named above, PTC offers Success Services that fit seamlessly into your Success Path, making it even easier to reach your desired business outcome.Rapid Outcome
Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.