Expecco Update Settings
Patches are provided on a per-release base, as a collection of individual hot fix files. Once installed as patch, these are loaded whenever the expecco application is started. Downloaded hot-fix files are stored in the "patches" directory, which is below the expecco installation directory (typically "\programs\expecco" or "/opt/expecco").
In order to protect against malware, patches are cryptographically signed by eXept, and expecco will refuse to install any hot-fix if it does not contain a corresponding signature.
FTP vs. HTTP
Please notice that expecco versions before 2.10.1 only supported FTP-access to the update server. This lead to problems with some customers, where FTP access was blocked in a firewall, and they had to install patches manually.
However, starting with 2.11, HTTP patch file installation is supported and now the default mechanism. A patch is available for 2.10, which adds HTTP support. After installation of this patch, the default mechanism will be HTTP, and FTP is only tried as a fallback (and can be enforced for backward compatibility, in case you have already setup your own FTP-patch service in your lab).
If you are running 2.10, and you have no FTP-access, it is a good idea to load this patch first:
- open a web browser on "http://download.exept.de/download/expecco/2.10.0/patches",
- save "0015_PatchPerHTTP.expeccoPatch" to a file
- install this patch ("Extras" -> "Maintenance" -> "Install Patch from File")
then install the other patches via the regular software update dialog ("Extras -> Settings -> Software Updates).
The default setup which is used if the dialog's fields are left empty/unchanged, accesses eXept's public HTTP server ("http://download.exept.de").
Customers with a special maintenance contract may use a non-public, customer-specific account to access additional hot-fixes. You will then be given a secret username/password combination by eXept for access to your customer-specific hot-fixes.
Company Local Setup
If your infrastructure does not allow/provide access to the public internet (for example, due to security considerations), you may also setup your own company-internal HTTP or FTP service for the test hosts, and manually copy hot-fix files there. For this, change the "Update Host" field to name your company-internal server. Of course, your server admin has to maintain the patches files there, keep track of new patches as provided by eXept and install them on the server.
If such a setup is not possible, transport the patches to your machine (into any folder) and select the "Install Patches from File" function from the "Extras"->"Maintenance" menu.
Automatic vs. Manual Patch Updating
You can manually check and/or install new updates or configure expecco to automatically check and/or install them periodically.
The default setup is to never do this automatically (i.e. expecco will not try to contact any outside service).
- For manual updates,
select "Never" in the "Check for Updates" list, and press the "Check for Updates Now" button.
- For automatic checking, but no automatic installation,
choose a time period ("At Every Start", "Daily", "Weekly", etc.) in the "Check for Updates" list, but do NOT check the "Install without Confirmation" checkbox below. With this setting, you will get an information dialog once in a while, when new updates are available.
- For automatic checking AND automatic installation,
check the "Install without Confirmation" checkbox. New updates will be installed automatically whenever available (depending on your chosen checking period).
Expecco as a Patches Server (18.1 aka 2.12)
Expecco itself includes an HTTP server framework, which can deliver patches to other expeccos in your LAN. For this, the patches must be present in some folder on the serving machine, so you have to get them once manually as described above (but only once).
To start the service, expecco vsn 18.1 contains menu items under "Extras" - "Web-Services" - "Patch Service".
Users of previous expecco versions, can execute the following code fragment (for example, in a workspace or as an elementary block) to start the patch service manually:
|server fileService| server := HTTPServer startServerOnPort:8089. fileService := server addFileServiceWithRootLinkName:(ExpeccoPreferences default expeccoUpdateDirectory) rootDirectory:<pathToYourPatchesFolder> defaultFileName:nil. fileService directoryListingAllowed:true.
Then, other expeccos within your company should be configured to use the above machine/port as patches server, setting
as patches host in their "Update Settings" dialog. Of course, any other port may be used beside 8089.
This helps closed-test-lab customers, where expecco hosts are cut off the internet for security reasons.
Uninstalling a Patch
Although unlikely, it may happen that you want to remove a patch. For this, remove the corresponding file from the patches folder (below the expecco installation folder) and restart expecco.