Page History

Upload Base build

Base builds only need to be uploaded for new Major releases of FEWS or in case changes can not be fixed with a regular patch.jar. The upload base build page allows uploading the base build and shows a list with all uploaded builds. A OC/CM/FSS will always start up with the boot build (installed build at the host) and then will restart with a base build that is compatible with the active patch. It is NOT POSSIBLE to fix issues that occur before the restart of the OC/CM/FSS by uploading a new base build. In this case the base build should be INSTALLED as boot build at the OC/CM/FSS host machine. An OC/CM restarts immediately with the active patch and boot build. A FSS will restart with the active patch and base build when it is woken up. This means that also all the issues while sleeping can not be fixed by uploading a new base build.

Delete Base builds

It is possible to delete a Base Build when it is no longer used by a patch.jar in the Delft-FEWS configuration or by the uploaded config management patch. In the action column it is possible to delete a base build. In the following example the stable 2021.02 (106458) base build is no longer used and can be deleted. Deleting a base build requires AI_ADMIN privileges. If the basebuild is in use, a tooltip is displayed over the cross button that indicates the patch that is compatible with the basebuild. In order to enable removal of a base build via the Admin Interface, first all patches need to be removed from the RootConfigFiles using the Config Manager application. See also Distribution of patch.jar in the live system - 2021.02 and later. If the latest base build is used and the patch jar is no longer referred to in the client config xml files of the root config files, the patch uploaded via the Admin Interace will be used by the MC, CM, FSS and OC.