\n Strategies for updating to a new release\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/managing-terminals\/maintain-performance","articleFields":{"description":"Understand maintenance calls, automatic reboots, configuration changes, and software releases.","feedback_component":true,"last_edit_on":"28-10-2021 13:33"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/managing-terminals\/maintain-performance","title":"Maintain performance","content":"To ensure your terminals continue to perform well and are using up-to-date settings and software, several events happen automatically on the terminals:\n\nMaintenance calls: every couple of hours, the terminal contacts our platform to check for configuration changes and software updates. The terminal doesn't implement or install anything yet (with a few exceptions).\nRebooting: for security reasons, the terminal must clear its cache regularly. To achieve this, the terminal reboots once every 24 hours at the restart hour.\nConfiguration changes: any configuration changes that the terminal discovered during a maintenance call, are implemented when the terminal reboots at the restart hour.\nSoftware updates: if the terminal is set to automatically update to new releases, any software update that the terminal discovered during a maintenance call is installed when the terminal reboots at the restart hour.\n\nThese events do not interfere with accepting payments or other daily operations. Below we explain the events in more detail, and describe what you need to do.\nRequirements\nBefore you begin, take into account the following requirements.\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nA Terminal API integration with payment terminals, or a standalone solution .\n\n\nSetup steps\nEnsure that your terminal is turned on and connected to the network during at least one maintenance interval (three hours) before the restart hour (at 6:00 AM by default).\n\n\n\nMaintenance calls\nEvery day, the terminal contacts our platform a few times to check for updates. We refer to this as maintenance calls. During a maintenance call, the terminal is informed of any changes in the configuration. For example, terminal settings that you configured in your Customer Area. If the terminal is set to automatically update to new releases, it is also informed of software updates that we have made available.\nYou won't notice when maintenance calls happen, because:\n\nOn average a maintenance call takes only 1.8 seconds.\nAny changes and software updates are not installed yet, with a few exceptions.\nThe terminal doesn't make maintenance calls while it is doing a payment or other operation.\n\nTerminals are scheduled to make a maintenance call regularly; by default every three hours. We refer to this period as the maintenance interval. When the terminal is busy at the time it is scheduled to make a maintenance call, it waits for a minute and tries again, and so on until it has succeeded in making a maintenance call. When the terminal has succeeded in making a maintenance call, it waits until the next scheduled maintenance call.\nRebooting at the restart hour\nRebooting means the terminal is power cycled: it turns off and on again. Then the software restarts. This process takes about two minutes. Power cycling clears the terminal's cache, which is important for security reasons.\nWhen the terminal reboots, it also installs any configuration change or software update that the terminal was informed of during a maintenance call. Installing the software can take up to 30 minutes.\nTo ensure the terminal's cache is cleared regularly and the terminal is updated, we have programmed the terminal to reboot once every 24 hours, at the so-called restart hour. By default, the restart hour is at 6:00 AM in the timezone of the terminal.\nSet the restart hour\nTo ensure the terminal reboots during a period when the terminal is not in use, you can change the restart hour in your Customer Area. Considerations for changing the restart hour are:\n\nYour opening hours\nOperational events\n\nFor this task, you need to be the \n admin\n user.\nTo change the restart hour:\n\nLog in to your Customer Area.\nOptionally select the merchant account, store, or terminal that you want to set the restart hour for.\nGo to In-person payments > Terminal settings > Hardware.\nIn the Maintenance section, select one of the Restart hour values.\nAt the bottom of the page, select Save.\n\nConfiguration changes\nConfiguration changes can be terminal settings that you updated in your Customer Area or through API requests, but can also be platform-wide changes initiated by us. For example, an update to the contactless CVM limits. Configuration changes are implemented during the restart of the Adyen application, either when the terminal reboots at the restart hour, or when triggered manually.\nConfiguration update at restart hour\nThe terminal receives configuration changes when it makes a maintenance call. The terminal then implements the changes when the Adyen application restarts during reboot at the restart hour. There are a few exceptions:\n\nChanges initiated by us that must be applied as soon as possible. With these changes, we add an instruction to the terminal to restart after the maintenance call. Restarting takes about 30 seconds.\nInstalling or uninstalling Android apps on Android terminals. The terminal carries out these changes immediately.\nUpdating the configuration manually on the physical terminal.\n\nUpdate the configuration manually\nIf you want configuration changes to take effect immediately, you can update the configuration manually:\n\nOn the terminal, open the Admin menu.\nSelect Config > Update.\n\nThe terminal retrieves the updated configuration and then restarts.\nAutomatic configuration update\nYou can enable a setting that restarts the Adyen application installed on the payment terminal as soon as the configuration is updated. This lets the terminal automatically apply the configuration update without restarting other applications you might have installed on the terminal. This can be useful for unattended terminals attached to a vending machine, token dispenser, parking payment systems, or similar.\nTo enable automatic configuration update:\n\n\nMake a PATCH request to the \/terminalSettings endpoint for the company account, merchant account, store or terminal.\nIn the request body, specify a terminalInstructions object with:\n\n\n\nParameter\nData type\nDescription\n\n\n\n\n adyenAppRestart\nBoolean\nIndicates whether the Adyen app on the payment terminal restarts automatically when the configuration is updated.\n\n\n\n\n\n\nThe response returns all terminal settings at the level where you made the request.\n\n\nSoftware updates\nBy default, the Adyen software on the terminal is updated automatically. When there is a new release, the terminal learns about this during a maintenance call. When the terminal reboots at the restart hour, it downloads and installs the new software package.\nWe can also enable background downloading for you. Android terminals use this by default. With background downloading, the terminal downloads new software after the maintenance call. This reduces the chance that the software update fails because the internet connection is down at the reboot hour.\nApart from updating automatically, you can decide to participate in our beta program.\nFor more information about update strategies and the release cycle, see Update to a new release\nWhat you need to do\nIt is important that:\n\nThe terminal makes at least one maintenance call every day to receive information about any changes.\nFor this, the terminal must be turned on and have a network connection.\nThe terminal reboots every day.\nTo reboot automatically, the terminal needs to be turned on at the restart hour. To download updates when it reboots, the terminal also needs to have a network connection.\n\nThis means you must ensure that your terminal is turned on and connected to the network during at least one maintenance interval (three hours) before the restart hour (at 6:00 AM by default).\nIn practice, we recommend you keep your terminals turned on and connected to the network overnight.\nSee also\n\n\n Managing terminals\n \n Strategies for updating to a new release\n \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Terminais","lvl2":"Gerenciando terminais","lvl3":"Maintain performance"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/point-of-sale","lvl2":"https:\/\/docs.adyen.com\/pt\/point-of-sale\/managing-terminals","lvl3":"\/pt\/point-of-sale\/managing-terminals\/maintain-performance"},"levels":4,"category":"In-person payments","category_color":"green","tags":["Maintain","performance"]},"articleFiles":{"automatic-configuration-update-0535871400.js":"automatic-configuration-update-0535871400.js<\/p>"}}