The update of the Bundles is done in two phases, update the Maven repository, and reinstall the Bundles in the Fuse client.
3.1. Update Maven repository
Updating the Maven repository consists of transferring the new compiled binaries to the repository in order to be accessible from the Fuse client. We can find, depending on the system, two repositories, local or remote (Nexus). In the case of a local repository, we must copy the compiled binaries to their corresponding .m2 folder of the local server, overwriting the previous version of them. In the case of a Nexus repository, it is necessary to have the access credentials and compile the Bundles directly on said repository by means of the corresponding Maven sentence.
3.2. Reinstall the Bundles in the Fuse client.
Although the repositories have been updated, the Fuse Bundles are maintained in the version they had at the time of installation, so it is necessary to reinstall the Bundles.
To maintain the integrity of the entire system, and ensure a proven operation, it is advisable to update all the Bundles, even if they have not been modified by the new version., Since the interdependencies between Bundles could remain disparate as soon as to the version with which they work.
- The first step is to open the Fuse console, using the "client" script that we will find in the folder of Fuse binaries.
- The second step is to uninstall all Bundles of solution B + SII using the command uninstall + pid. example.: uninstall 238-324.
- The third step requires restarting the fuse service, for this we turn off the instance using the shutdown -f command, and restart the service with the following commands: sudo systemctl stop fuseSIIProd.serviceand sudo systemctl start fuseSIIProd.service.
- The fourth step takes us back to the Fuse client, where we will reinstall all the Bundles, based on the Bundles installation script in the Annex.