Note: The exemplary installation described below was carried out on Ubuntu distribution. To begin BI Point installation, use the following command to run the setup script available in the folder with the setup wizard image:

sh first-setup.sh

If the user running the script does not have administrator privileges (root), the command needs to be preceded with ‘sudo’ (permission to this function is necessary in order to carry out the installation):

sudo sh first-setup.sh

After the command is executed, the BI Point setup wizard will check whether all the necessary components are installed. The setup wizard requires a network tool - Curl. It is used to execute network queries and commands. Note: In the case of other distributions, it is necessary to get a relevant command as part of package installation. In order to install the curl tool, execute the following command (the exemplary command below is running on Debian and Ubuntu distributions):

sudo apt install curl

In order to install the curl tool, execute the following command (the exemplary command below is running on Debian and Ubuntu distributions):

Docker Docker – compose Installation of supporting scripts Generation of a docker-compose.yml file Installation of BI Point image

The first step is the execution of the setup script for the Docker component: The next step is the installation of a Docket-compose component: Finally, the images are installed: You will be asked to select the path to the package containing BI Point images on the server. You need to select the location of the file with .tar.gz extension (if you ran the setup script from the folder containing the BI Point image (a .tar.gz file), select the Enter key to confirm the suggested path). Upon confirmation, the setup wizard will process the following:

• Loading BI Point images

After the images are loaded, it will be possible to run the Key Manager and install BI Point application. Upon confirmation, the Key Manager application will be installed on Linux system. Note: You only need one instance of the Key Manager per network. If you installed the Key Manager with a license for BI Point on another server (Windows or Linux), then you can skip this step (by typing n) and in the latter installation step you will be asked to provide appropriate parameters (server and key number). If you added the Key Manager to the docker-compose.yml file while executing the script, then after running the Key Manager for the first time, you need to add your license key via the manager tool from the key manager image, e.g.: Prior to executing the commands, make sure to include the container names of the Key Manager:

• Adding a license key

docker exec -i KM_Container_Name manager addkey clientid=<client id> pin=<pin> key=<key>

• Deleting the license key

docker exec -i KM_Container_Name manager deleteinstallation key=12341241234

• Releasing the license

docker exec -i KM_Container_Name manager releaseuser user="<user>"

In the following step, the supporting scripts are installed: After that, you will be asked to specify the configuration parameters of the application. Setup parameters:

Port of BI Point application BI Point version (ERP Standard BI, CEE BI,CEE BI Smart, Optima BI, XL BI, XL BI Start, BI Point Standalone) Server of the license key manager (depending on the option selected in step [4]) License key number

After the configuration parameters are specified, execute the following command:

sudo docker-compose up -d

The command is responsible for running containers and volumes. After the containers are run, the import of connections, data models and standard reports begins. After the installation is completed, the BI Point website can be run via a web browser. The default user is admin (password – admin).

Verification of the import status

In order to verify the current import status of the standard content of BI Point application, you need to verify the name of the appropriate container by using the following command:

sudo docker ps

Next, execute the last fragment of the log of the selected container by using this command:

sudo docker logs bipoint_bipoint1 --tail 10

The above message indicates that the import process has completed.

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