Update Cockpit
To update the RE-Cockpit, the Mail and Vault daemons, one has to download two files:
the new version of the ece.ear and a .zip file with the libraries of the daemons.
Update RE-Cockpit
Linux
- Open the directory in which the RE-environment is stored in the file explorer
- Open the folder
<Wildfly-directory>/standalone/deployments
- Copy the file
ece.ear
and save it in a different folder - Change the file name to e.g
ece_old.ear
- Change the name of the new downloaded
.ear
file toece.ear
- Move the new
ece.ear
file into the folderdeployments
to replace the oldece.ear
file - The file
ece.ear
deploys immediately
Note
If you remove the old ece.ear file from the deployment folder, the deployment will not work later anymore.
So it is crucial to copy the file, not remove it, and then replace it later with the new .ear.
Important!
If the deployment fails after replacing the ece.ear
file, try restarting WilfFly.
After the successful update of the Cockpit, one can see the new version of it in the RE-Cockpit.
Before the update:
After the update:
Update Daemons
Linux
- Open the RE-Cockpit in the browser
- Here, under Monitoring→Lifecycle, click on "Finish work and stop daemon" for the Mail and Vault daemon.
- Open the directory where the daemons are installed in the file explorer
- Rename the
lib
folder to e.glib_old
- Extract the new
lib
folder from theece-core-daemons-wrapper.zip
Copy the new
lib
folder into the directory where the daemons are installedNote
The new
lib
folder is missing the fileece-daemon-boot-apache.jar
.
Copy this file from thelib_old
folder.Open the terminal
- Change to the directory
<Install-path>Daemons/mail
- Run
./run_mail.sh
to start the Mail daemon - Open a new terminal
- Change to the directory
<Install-path>Daemons/vault
- Run
./run_vault.sh
to start the Vault daemon - Keep all the terminals open and check if the daemons started in the RE-Cockpit.
Note
If a daemon fails to start, try running ./run_....sh
once more.
After the successful update of the daemons, one can view the new version of the daemons in the RE-Cockpit.
To see the version of the daemons, one has to open the RE-Cockpit and click on Administration→Data Extension Repositories→ .
Before the Update:
After the Update: