I recently updated our plants' WindowMaker application and encountered difficulties when trying to deploy the changes to the live runtime. While attempting to deploy the main Galaxy_ViewEng along with two terminal ViewEngs from the deployment window, a message stating "Changes made to runtime, restart application required" popped up on the live HMI. However, the new graphics were not pushed after this notification. Any suggestions on effectively deploying changes via the Archestra IDE would be highly welcomed.
Just a quick heads up, this is indeed a managed application.
To optimize your website's performance, it is essential to redeploy the template generated by $IntouchViewApp instead of $ViewEngine. Unless you are utilizing OMI, evident from your mention of WindowMaker, in which case you should be using the template from $ViewApp. This step will ensure a smoother user experience and better search engine visibility.
I'm glad that solution worked! Thank you!
It sounds like you've encountered a classic issue with updating the WindowMaker application. Have you checked if all the modifications were properly saved before the deployment? Occasionally, Graphic Toolbox glitches could cause this issue, so a quick restart of the graphic editor might solve the problem. If you're still having trouble, try splitting the deployment into smaller parts. Instead of deploying the main Galaxy_ViewEng along with the terminal ViewEngs simultaneously, deploy them one at a time. Make sure you click "apply" and "ok" after deploying each change. This way, the IDE gets a chance to absorb each modification separately which tends to be more reliable. If these suggestions don’t help, let us know, so we could explore other probable causes.
It sounds like you're running into a common issue with the deployment process! I've found that sometimes the update doesn’t fully push to the live runtime if there are pending state changes or if other components are still in use. One thing you could try is to make sure that all ViewEngs are in a proper state before deploying—maybe even shut down the live application completely, deploy your changes, and then restart everything. Also, ensure that you're deploying in “update” mode rather than “replace,” which can sometimes help with graphic updates not appearing. Good luck!
It sounds like you’re dealing with a tricky deployment issue! One thing I’ve found helpful is to double-check that all your changes are saved and compiled correctly in Archestra before trying to deploy. Sometimes, re-running the deployment after a clean restart of both the IDE and the live application can help clear up any residual glitches. Also, ensure that you're not in a 'ghost' state—if other users are connected to the HMI, their sessions might be blocking the updates. If you’re still having issues, it could be worth looking into the event logs for any clues. Good luck!
âś… Work Order Management
âś… Asset Tracking
âś… Preventive Maintenance
âś… Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: To resolve deployment issues, ensure that the changes are properly saved and synchronized within the Archestra IDE before attempting to deploy. Additionally, consider restarting the application after receiving the notification to ensure that the new graphics are pushed successfully.
Answer: Answer: If changes made in WindowMaker are not reflecting in the live runtime, try restarting the application as prompted by the message "Changes made to runtime, restart application required." This step can help in pushing the new graphics effectively.
Answer: Answer: To effectively deploy the main Galaxy_ViewEng and terminal ViewEngs, ensure that all necessary changes are saved and synchronized in the Archestra IDE before initiating the deployment process. Restart the application if prompted to do so for the changes to take effect in the live HMI.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.