> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/on-premise/deployment-overview/how-to-prepare-for-the-update.md). # How to prepare for the update? Verify Java and MySQL versions meet current requirements. Upgrade software components before platform updates to prevent service failure ## What to check before the Navixy On-Premise update? The main thing to check is that you are using the software required by the latest version. This mainly applies to Java and MySQL versions. Check the software requirements instruction: [Server software](/docs/on-premise/on-premise/how-to-guide/requirements/server-software.md). Since the platform code is being upgraded to meet modern requirements and support new features, using outdated software will prevent the platform services from running properly. Therefore, the software must be upgraded in advance before the platform update. Please note: in most cases, new versions of Java and MySQL are backward compatible with the old version of Navixy, so updating these components in advance doesn't cause any operational problems. ## Do I need to update the hardware? In general, no. Although the platform is gradually becoming more capable and gaining new features, resource consumption is not increasing dramatically. Hardware upgrades should only be performed when you are clearly experiencing a shortage of resources, as confirmed by monitoring or internal tools on the server. ## Do I need to notify the Navixy team about the upcoming update? This isn't necessary. If you are experienced in administration, have considered all requirements, and have performed platform updates before, then you don't need a Navixy technical specialist's presence. The update is a routine process, and is mostly automated. If you are performing the update for the first time and are afraid of making mistakes, contact Navixy technical support, inform them of your plans, and coordinate the update time. Engineers will be in touch to assist you urgently when needed. ## Links * [Server software requirements](/docs/on-premise/on-premise/how-to-guide/requirements/server-software.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/qna/on-premise/deployment-overview/how-to-prepare-for-the-update.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.