TABLE OF CONTENTS
- Before the upgrade
- Upgrading your fw Server (running on macOS Mojave or later versions)
- Upgrading your Windows or Linux hosted farmerswife Server
- Upgrading your farmerswife Clients
- Direct Client Desktop application installer download links
Before the upgrade
STEP 1
Have your "Version 7.2" license at hand
If you don't have your new farmerswife (fw) 7.2 license yet, request it from license@farmerswife.com.
To be eligible for a 7.2 license you need to have a current support subscription with us.
STEP 2
Check your running farmerswife version
Every farmerswife version contains a specific upgrade code. To ensure data integrity you may need to do several fw-Server-side-only upgrade steps, if you are upgrading from older versions.
For the upgrade to 7.2 please make sure to be on at least 7.1 Release version.
Please contact support@farmerswife.com in case you are running a version below 6.8.
IMPORTANT changes in this (and previous) version:
- Native macOS 10.15 Catalina (and later) support
Since v6.6 we provide "64bit" installers for macOS fw Server and Client, which can be used on macOS Mojave, Catalina, Big Sur, Monterey, Ventura and Sonoma.
!! We no longer support 32bit fw Server and Client apps on Mac and Windows !!
!! 7.2 requires Java / OpenJDK v17 to be installed !!
If you are running older OS versions than Mojave, you will need to upgrade first to a newer operating system. macOS 10.14 Mojave is the best practice starting point for the fw Server app to be smoothly upgraded on Mac from versions below v6.6! - "Built-in PDF Printer" on the 64bit fw Server AND fw Client apps on Windows and Mac.
STEP 3
Download the "Public Installers"
Go to our Release installers page and browse into the “7.2 Release" folder.
Download the farmerswife Server Installer for your Operating System, and the farmerswife Client Installers for the fw Client app OS platforms in your environment if required. Or distribute the below listed "direct download links".
STEP 4
Inform your colleagues about this new version before you start the upgrade process.
Upgrading your fw macOS Server (running on macOS Mojave or later versions)
- Use the "Full Backup Now" button located on the running farmerswife Server application to perform the "Full Backup" right before the upgrade.
- Copy the downloaded farmerswife Server package to the machine hosting the fw Server.
NOTE: Ensure the compressed ".zip" installer file is downloaded and un-zipped within the "Downloads" folder on you Mac. Then move the "farmerswife64 Server" app to the "Applications" folder. - Un-zip (if still needed) and rename it to include "NEW" in the package name.
- Place it in the same location as the previous running farmerswife Server, i.e. within the "Applications" folder.
- Quit the running farmerswife Server.
- Rename the previous farmerswife Server, to include "OLD" in the package name.
- On both packages do <Control> + click and select "Show Package Contents" in the pop-up menu.
- In the OLD package select the "system" and "files" folders and use <Control> + click and select "Copy 2 Items" in the pop-up menu.
- Within the NEW farmerswife Server package use <Control> + click and select "Paste 2 Items".
Note: The "files" folder might not even exist within your fw Server's package, since it was possibly broken out to reside on some mounted storage device within your network. Ensure that this Volume is properly mounted. - Copy over any customised files.
If any of the below points apply, you will need to migrate from the OLD farmerswife Server package > "Show PackageContents" > ... to the new one.
a) browse to ..."html_templates"
Compare your customised files from within the "html_templates" with the new ones from us.
There might be new functionality available; you'll need to adapt this. Only migrate the customized files.
b) Have you SSLed your farmerswife system in the past?
=> use your own logged instructions in regards to which of these files "server.pem, skey.pem, keystore, jetty.xml" have to be migrated or protected during the upgrade; if you SSLed them, they should have been manually set to be "Read Only" by you in the past.
IMPORTANT: Since v6.8 the "jetty.xml" is no longer used for locally SSLing the built-in Jetty web server!
Use these updated SSLing-instructions.
c) 3rd party integration scripts ... browse to ... fw Server app package > Show Package Contents > contents > lib > scripts > ...
Only copy the actual integration script files from the sub-folder within the new farmerswife Server package. - Now copy the new v7.2 license files into the "system" folder of the NEW farmerswife server.
- On the 1st start-up only, right-mouse click and use "Open" to launch the fw Server and allow it to run to start the actual upgrade process.
Note: The upgrade itself might require a couple of "Forced Shutdowns" for it to finish; this depends on your usage of the system.
From now on you can simply double click on the NEW farmerswife Server package icon to launch it. - If everything upgrades with no error, remove or update any Dock or Desktop links. And if needed remove the OLD Server package.
If you have any problems, contact us at support@farmerswife.com. - After the upgrade, start the farmerswife Server as usual.
- Once you've successfully upgraded, please let us know by sending a short email to support@farmerswife.com.; this is very helpful information for us to provide the best support to you.
Upgrading your Windows or Linux hosted farmerswife Server
- Log In to the host machine with the same admin user as on the initial installation of the fw Server application.
- Use the "Full Backup Now" button located on the running farmerswife Server application to perform the "Full Backup" right before the upgrade.
- Copy the NEW farmerswife Server installer ".exe" on Windows or ".bin" file to the machine hosting the WIFE Server.
=> On Windows this is a .exe file
=> On Linux this is a ".bin" file; use in a command shell: chmod +x Linux64_... to make it executable; more detailed info here: Server and Client installation Linux - Quit the running farmerswife Server.
- IMPORTANT: Check any customised files are read-only so they are not overwritten by default ones during the upgrade process (e.g. some files within "html_templates", or within /lib/scripts?)
Have you SSLed your farmerswife system in the past?
Use your own logged instructions in regards to which of these files "server.pem, skey.pem, keystore, jetty.xml" have to be migrated or protected during the upgrade; if you SSLed them, they should have been manually set to be "Read Only" by you in the past.
IMPORTANT: Since v6.8 the "jetty.xml" is no longer used for locally SSLing the built-in Jetty web server!
Use these updated SSLing-instructions.
During the installation process, choose "Ignore" as the Installation Wizard is not allowed to modify these read-only files. - Copy the new v7.2 license files (license.dat and license.txt) into the "system" folder of your farmerswife Server app.
- Double click to run the installer file in the same manner as the previous installation (i.e. If you used "Run As Administrator" on Windows, then you need to do so as Admin again).
- Follow the instructions of the install wizard.
IMPORTANT: While installing make sure the previous installation path is correctly set.
And do a "Full Installation", i.e. ensure to include and install "HTML Templates"!
If you have any problems, contact us at support@farmerswife.com. - After the upgrade, start the farmerswife Server as usual.
Once you've successfully upgraded, please let us know by sending a short email to support@farmerswife.com; this is very helpful information for us to provide the best support to you.
Upgrading your farmerswife Clients
The auto-upgrade functionality is supported if you are upgrading from version 7.1 SP5.
Below are the details of how the upgrade is supported on various servers and clients:
For full installs OS admin user permissions Read, Write AND Execute are necessary.
- If your farmerswife Server is macOS 64bit (Mojave, Catalina, Big Sur, Monterey) or Windows (64bit):
- Windows fw Clients will perform an auto upgrade when they first connect to the upgraded Server.
- macOS (Mojave, Catalina, Big Sur, Monterey) fw clients will perform a full install by downloading the installer .dmg when they first connect to the upgraded Server.
- If you have a mix of Admin and Standard users on a Mac, make sure to be logged-in as a Standard user. Then after mounting the .dmg file, drag-and-drop it to the Applications folder. You then need to authenticate with the Admin users credentials! The farmerswife Client will not work for the Standard user, if installed while being logged-in as the Admin user.
- If your farmerswife Server or fw Clients are or running a macOS version earlier than Mojave, or a Windows 32 bit, or Linux your clients will NOT upgrade automatically!
Package distribution on Windows - "/SILENT" and "/VERYSILENT" support
farmerswife does not support .msi files. For Windows we only provide .exe files.
You can use these "silent commands" when installing/upgrading the farmerswife Client application on Windows. If you use in "cmd" on Windows: "fw_client_72.exe /SILENT" or "fw_client_72.exe /VERYSILENT" this will install it using this legacy default location. C:\Program Files (x86)\farmerswife Client.
Use this on Windows > CMD
C:\_fw_installer>fw_client_72.exe /VERYSILENT /DIR="C:\Program Files\farmerswife Client"
... and it will then be using "Inno Setup" to install it as expected.
Please refer to these links and try it out on your end what works best for you:
http://www.jrsoftware.org/ishelp/index.php?topic=setupcmdline
http://stackoverflow.com/questions/71203/is-it-feasible-sensible-to-wrap-an-innosetup-installer-inside-an-msi-for-easier?rq=1
Direct Client Desktop application installer download links
macOS Mojave, Catalina, Big Sur, Monterey, Ventura, Sonoma, Sequoia "64bit" fw Client Retina optimized:
macOS Mojave, Catalina, Big Sur, Monterey, Ventura and Sonoma "64bit" fw Client non-retina:
fw_client_v702-nonretina.dmg
Windows "64bit" fw Client:
fw_client_v702.exe
Linux "32bit" fw Client:
Please contact support@farmerswife.com. if you need use the fw Client app on Linux.
For your reference below are the fw client desktop app installation instructions:
- Mac Client Installation
- Windows Client Installation