Upgrade the Version 2.x to 2.6
All required components to upgrade the boom software are part of the server installation package
available on the download page.
The upgrade of the boom server/agent can be performed independent from the GUI upgrade.
The boom Agent can only be updated after the server update has been performed successfully.
Upgrade Server
Upgrade Agent
Upgrade Client/UI
Server Upgrade Example
boom Server Upgrade
After downloading the latest package, unzip
the package into a temporary folder. This folder MUST be outside the current server installation folder!
Linux/Unix
The upgrade process must be performed by a user that has administrative rights (i.e. root).
As a first step you have to change the permissions of the upgrade script in oder to be able to execute the script.
Chance permission by entering the following command: chmod 750 upgrade.sh
Run the upgrade script "upgrade.sh" by entering ./upgrade.sh
Upgrade Steps:
|
The script will first ask for the current server installation directory.
Please enter the directory where the boom server that you want to upgrade is running. |
|
If the boom server is running, it should be stopped before the upgrading process will start. |
|
You have the possibility to backup the current installation. |
|
Update rc scripts (Unix only). |
|
Update the database. |
|
Update the deployments. |
|
Update the packages. |
|
Update HTML files. |
|
Update the libraries. |
|
Update actions (default boom Action Groups will be replaced). |
|
Update all services. |
|
Update node groups (skip if any customizations exist). |
|
Update others:
/boom_server/ORACLE_SQL/db.props
/boom_server/ORACLE_SQL/step1_create_boom_db.sql
/boom_server/ux-daemon.cfg/boom_srv |
|
Update main files:
/boom_server/boom_server.jar
/boom_server/boom_server.plist
/boom_server/copyrights
/boom_server/readme
/boom_server/boom_srv.cmd
/boom_server/booms_service_setup.exe
/boom_server/step1create_boom_db.sql
/boom_server/upgrade_mysqldb.sql
/boom_server/upgrade_oracledb.sql
|
|
Import Policies and Assignments:
First of all the upgrade script will analysis the policies and assignments that needs to be imported. All Conflicts will be
recognized and displayed. Each conflicting policy will be imported as next version.
Any conflicts that will be recognized for assignment will also be displayed. For each conflict you can decide if you want to
replace the existing assignment with new one or if you want to import the new assignment with a new unique name.
After all assignment conflicts have been processed, you will be asked if you want to perform the import. |
After the script has been started it will guide you through the complete server upgrade process. All information that are displayed
in square brackets [] will be taken by the script as default values if no other data is entered by the user.
For more detailed information about the Linux upgrade process see the following server upgrade example.
Windows
To start the upgrade process on a windows system, you have to run the upgrade.cmd from a Windows command line interface.
Open the cmd.exe console, switch to the directory where the upgrade package is located and run the upgrade script:
C:\BOOM\boom_server>upgrade.cmd
Upgrade Steps:
All steps that will be performed during the upgrade are identically to the Unix upgrade steps as described above.
For more detailed information about the windows upgrade process see the server upgrade example.
Agent Upgrade
The boom agent can only be updated if the upgrade process of the server has been successfully finished. All Agent information
belonging to the upgrade process is placed inside the server. The agent upgrade can be performed by simple re-deploying the agent from the server via
the boom User Interface.
boom Client/UI Upgrade
The UI packages are placed on the server and can be downloaded from its built-in web server. To download the UI packages point your browser
to the following address: http://<server-name>:8888
Upgrade Steps:
|
Download the UI package that suits you platform and unzip the package. |
|
Replace the old User Interface with the new boomgui package. |
|
Start the user interface by executing the boomgui program. |
No further steps are necessary. Java needs to be in the current user's search path in order to startup the GUI.
Note: If there is an older client version installed, run "boomgui -clean" to empty precompiled classes and hashes
otherwise unpredictable behaviour can occur.
|