Upgrade
In the first step, change BI Point images to new ones that are compatible with 2023.2 release (files named bipoint-images-(…)). After changing the images, change also the update-images.sh script in the folder with already installed BI Point application. The previous files are not needed and can be deleted
Once the script and the BI Point images are changed, execute the following command:
| sh update-images.sh |
After executing the script, the message below will be displayed. Press the Enter key to confirm it.
Next, select the 2023.2 release image location. If it was already changed in the same folder that contains the update-images.sh script, then press Enter to confirm the default location.
After loading individual images:
The additional scripts will be updated:
The docker-compose.yml will also be updated as shown in the message below, which is displayed during execution of the updating script:
The above update step has overwritten the following:
- BI Point image number in the docker-compose file
In the next step, deactivate the containers in order to update the database. After executing the docker-compose down command, the containers will be deleted:
| docker-compose down |
Next step, delete the ae_db container (after executing again the docker-compose command, a data volume will be created in the version compatible with Postgres 12). The command in this case is as follows:
The final step is to migrate the BI Point database:
To perform the migration, we first remove the containers:
| docker-compose -f docker-compose.yml -f docker-compose.migrator.yml down |
Next, we start the “bipoint_db” image:
| docker-compose -f docker-compose.yml -f docker-compose.migrator.yml up -d bipoint_db |
Wait until the “bipoint_db” is running and in a healthy state (check using docker-compose ps). Then, start the migrator container:
| docker-compose -f docker-compose.yml -f docker-compose.migrator.yml up bipoint_migrator |
At this point, the database container and the bipoint_migrator container will be running, with the migrator applying migration scripts and plugins.
After the migration is complete, the bipoint_migrator container will shut down. You can then restart the BI Point containers with the following command:
| docker-compose up -d |
Manual upgrade
Prior to database migration, make a backup copy of your database. Execute the following command in the container:
| docker exec -u postgres <name of the old database container> pg_dump -d bipoint > ./dump |
The above command creates a backup copy.
After the backup copy is created, modify the docker-compose.yml and overwrite the following values as shown in the figure below (sample command of the text editor):
| Nano docker-compose.yml |
After the docker-compose.yml is changed, execute the update-images.sh script.
| sh update-images.sh |
Once the script is executed, execute the command below:
| docker-compose down |
Next, restart only the database container:
| docker-compose up -d bipoint_db |
Then, follow the steps below:
| echo “drop database bipoint;” | docker exec -i -u postgres <container name> psql
echo “create database bipoint;” | docker exec -i -u postgres <container name> psql cat ./dump | docker exec -i -u postgres <container name> psql -d bipoint |
After the backup copy is restored from the dump file, you can proceed to the migration tool step.
In order to migrate the database, first delete the containers:
| docker-compose -f docker-compose.yml -f docker-compose.migrator.yml down |
Then, run only the bipoint_db image:
| docker-compose -f docker-compose.yml -f docker-compose.migrator.yml up -d bipoint_db |
After the bipoint_db image is run (the image status can be checked on a current basis using the docker-compose ps command) and its status shows healthy, you can run the migration tool image:
| docker-compose -f docker-compose.yml -f docker-compose.migrator.yml up bipoint_migrator |
After the migration is completed successfully, the message below will be displayed:
Finally, run the containers using the command below:
| sudo docker-compose up -d |