Greetings! I am a new user on iFix and I have successfully created a digital alarm that is functioning properly in the alarm banner on the primary development computer. I am now wondering how to deploy the changes made to the application to the client terminal applications. I have noticed the project path in the runtime settings. Should I simply shut down iFix and restart it? I am hesitant to do so because the programming laptop with iFix installed requires login credentials to shut down. I do not want to risk shutting down something on the terminals that I may not be able to restart. I have inherited this site without any handoff, so I am working without access to passwords or usernames. Any insights or advice would be greatly appreciated.
Could you provide more details about the setup? It typically involves one server and multiple clients. If the alarms are not functioning on the client side, it may be due to a missing alarm app. It is crucial to have the "Alarm Network Service" running on the server. To verify or adjust these settings, utilize the ICU utility.
Harryting asked for further details on the setup of the system. It consists of a primary node, a secondary node, and two client terminals. One of the client terminals is only for runtime use, while the other allows access to the workspace. The alarm updates in the tag database when viewed from the workspace, but does not reflect in the client's runtime display. The issue may be due to a missing alarm app. To resolve this, ensure that the "Alarm Network Service" is running on the server and use the ICU utility for configuration. It seems that on the primary node, entering runtime mode triggers the alarm updates, while on the client machine, this action is not causing the alarm to appear in the banner. Consider shutting down iFix and relaunching it to update any changes.
Are you trying to locate the alarm in the alarm summary object, or is it a textual alert that appears on the screen when activated? Find out more about where to find the alarm and how it displays on your screen.
The alarm summary object is functioning correctly on the primary node, but it is not updating in other applications. While the alarm tag updates in the tag database accessible from the client machine, it does not reflect in the application's alarm summary object.
I may not have a clear recollection of iFix, so please bear with me. Let's clarify the terminology first. You mentioned having "Primary and Secondary" nodes, but I believe you meant to say you have a redundant server pair in addition to two client machines. In iFix, both the server and client are referred to as nodes, so do you have a total of four nodes or just two (one server and one client)? Also, let's revisit the initial changes you made. Did you add a DA or DI alarm? Are other existing alarms displaying correctly on all machines?
Hello and welcome to iFix! It seems like you're doing great so far. With regards to deployment, shutting down and restarting iFix is generally not necessary. You should be able to deploy the changes directly from your development environment. However, every setup is unique, so it's hard to give definite advice without specific details. Given you don't have full access and are working with an inherited site, I'd recommend proceeding with caution. Perhaps contacting software support for more guided assistance or trying to recover any lost credentials might be your best bet. They should be able to help you navigate any potential issues and make sure your deployment goes smoothly without affecting your client terminals. Best of luck!
Hey there! It sounds like you're making great progress with your alarm project! For deployment, you typically don't need to shut down iFix entirely. Instead, you might want to check if you can simply publish or transfer the changes from the development environment to the client terminals without shutting everything down. Look for an option in the iFix environment that allows you to update the runtime settings or push changes to clients—sometimes that can be done on-the-fly. If you're unsure, it might be a good idea to consult any existing documentation on your system or even reach out to your colleagues if there are any left who might have the credentials or experience to help you out without risking a shutdown. Good luck!
Hey there! It sounds like you're making great progress with your digital alarm in iFix! To deploy your changes to the client terminals without shutting down everything unnecessarily, you can try using the "Update" or "Deploy" feature within iFix, which often allows you to send changes to client applications without needing a full restart. If that’s not an option or you’re unsure, you might want to consult the iFix documentation or look for a "Publish" option in the settings. Additionally, since you've inherited the site without proper handoff, it might be worth reaching out to your IT department for help with any missing credentials—they might be able to assist you with a safe restart or help get you set up with new access. 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: - To deploy changes from the primary server to client terminals in iFix, you can utilize the project path in the runtime settings. Avoid shutting down iFix on the primary server to prevent any disruptions on the client terminals.
Answer: - It is not necessary to shut down and restart iFix on the primary server to deploy changes to client terminals. Utilize the project path in the runtime settings for deployment without disruption.
Answer: - If you do not have access to login credentials for iFix on the programming laptop, seek assistance from your IT department or the previous administrator to ensure a smooth deployment process without any issues related to access restrictions.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.