From 0ee6623c617f13e80988e24f2a8e0bd758ff3c51 Mon Sep 17 00:00:00 2001 From: JeremJR Date: Fri, 7 Dec 2018 16:52:14 +0100 Subject: [PATCH] update Bonita and migration tool versions --- bonita/content.md | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/bonita/content.md b/bonita/content.md index da92ba3a7..17d4f978d 100644 --- a/bonita/content.md +++ b/bonita/content.md @@ -14,7 +14,7 @@ Bonita (called Bonita BPM till 7.5) is an open-source business process managemen $ docker run --name bonita -d -p 8080:8080 %%IMAGE%% ``` -This will start a container running the [Tomcat Bundle](https://documentation.bonitasoft.com/bonita/7.7/tomcat-bundle) with Bonita Engine + Bonita Portal. With no environment variables specified, it's as like if you have launched the bundle on your host using startup.{sh|bat} (with security hardening on REST and HTTP APIs, cf Security part). Bonita uses a H2 database here. +This will start a container running the [Tomcat Bundle](https://documentation.bonitasoft.com/bonita/7.8/tomcat-bundle) with Bonita Engine + Bonita Portal. With no environment variables specified, it's as like if you have launched the bundle on your host using startup.{sh|bat} (with security hardening on REST and HTTP APIs, cf Security part). Bonita uses a H2 database here. You can access the Bonita Portal on http://localhost:8080/bonita and login using the default credentials: install / install @@ -24,7 +24,7 @@ You can access the Bonita Portal on http://localhost:8080/bonita and login using PostgreSQL is the recommanded database. -[Set max_prepared_transactions to 100](https://documentation.bonitasoft.com/bonita/7.7/database-configuration#toc5): +[Set max_prepared_transactions to 100](https://documentation.bonitasoft.com/bonita/7.8/database-configuration#toc5): mkdir -p custom_postgres echo '#!/bin/bash' > custom_postgres/bonita.sh @@ -47,7 +47,7 @@ $ docker run --name bonita_postgres --link mydbpostgres:postgres -d -p 8080:8080 There are known issues with the management of XA transactions by MySQL engine and driver: see MySQL bugs [17343](http://bugs.mysql.com/bug.php?id=17343) and [12161](http://bugs.mysql.com/bug.php?id=12161) for more details. Thus, using MySQL database in a production environment is not recommended. -[Increase the packet size](https://documentation.bonitasoft.com/bonita/7.7/database-configuration#toc5) which is set by default to 1M: +[Increase the packet size](https://documentation.bonitasoft.com/bonita/7.8/database-configuration#toc5) which is set by default to 1M: mkdir -p custom_mysql echo "[mysqld]" > custom_mysql/bonita.cnf @@ -157,9 +157,9 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat ```console cd bonita_migration - wget https://release.ow2.org/bonita/bonita-migration-distrib-2.35.0.zip + wget https://release.ow2.org/bonita/bonita-migration-distrib-2.36.0.zip wget https://download.forge.ow2.org/bonita/BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip - unzip bonita-migration-distrib-2.35.0.zip + unzip bonita-migration-distrib-2.36.0.zip unzip BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip ``` @@ -174,13 +174,13 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat ```console cd bonita_migration - wget https://release.ow2.org/bonita/bonita-migration-distrib-2.35.0.zip - unzip bonita-migration-distrib-2.35.0.zip + wget https://release.ow2.org/bonita/bonita-migration-distrib-2.36.0.zip + unzip bonita-migration-distrib-2.36.0.zip ``` - Configure the migration tool - cd bonita-migration-distrib-2.35.0 + cd bonita-migration-distrib-2.36.0 edit the migration tool config to point towards the copy of bonita home and db @@ -212,17 +212,17 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat - If >= 7.3.0 ```console - $ docker run --name=bonita_7.7.5_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 %%IMAGE%%:7.7.5 + $ docker run --name=bonita_7.8.0_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 %%IMAGE%%:7.8.0 ``` - Reapply specific configuration if needed, for example with a version >= 7.3.0 : ```console - $ docker exec -ti bonita_7.7.5_postgres /bin/bash + $ docker exec -ti bonita_7.8.0_postgres /bin/bash ``` ```console - $ cd /opt/bonita/BonitaCommunity-7.7.5-Tomcat-8.5.31/setup + $ cd /opt/bonita/BonitaCommunity-7.8.0-Tomcat-8.5.34/setup $ ./setup.sh pull $ TENANT_LOGIN=tech_user $ TENANT_PASSWORD=secret @@ -242,10 +242,10 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat ``` ```console - $ docker restart bonita_7.7.5_postgres + $ docker restart bonita_7.8.0_postgres ``` -For more details regarding Bonita migration, see the [documentation](https://documentation.bonitasoft.com/bonita/7.7/migrate-from-an-earlier-version-of-bonita-bpm). +For more details regarding Bonita migration, see the [documentation](https://documentation.bonitasoft.com/bonita/7.8/migrate-from-an-earlier-version-of-bonita-bpm). ## Security @@ -253,11 +253,11 @@ This Docker image activates both static and dynamic authorization checks by defa - REST API authorization - - [Static authorization checking](https://documentation.bonitasoft.com/bonita/7.7/rest-api-authorization#toc1) + - [Static authorization checking](https://documentation.bonitasoft.com/bonita/7.8/rest-api-authorization#toc1) - - [Dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.7/rest-api-authorization#toc2) + - [Dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.8/rest-api-authorization#toc2) -- [HTTP API](https://documentation.bonitasoft.com/bonita/7.7/rest-api-authorization#toc10) +- [HTTP API](https://documentation.bonitasoft.com/bonita/7.8/rest-api-authorization#toc10) For specific needs you can override this behavior by setting HTTP_API to true and REST_API_DYN_AUTH_CHECKS to false: @@ -271,7 +271,7 @@ When you start the `bonita` image, you can adjust the configuration of the Bonit ### `PLATFORM_PASSWORD` -This environment variable [is recommended](https://documentation.bonitasoft.com/bonita/7.7/tomcat-bundle#toc3) for you to use the Bonita image. It sets the platform administrator password for Bonita. If it is not specified, the default password `platform` will be used. +This environment variable [is recommended](https://documentation.bonitasoft.com/bonita/7.8/tomcat-bundle#toc3) for you to use the Bonita image. It sets the platform administrator password for Bonita. If it is not specified, the default password `platform` will be used. ### `PLATFORM_LOGIN` @@ -279,7 +279,7 @@ This optional environment variable is used in conjunction with `PLATFORM_PASSWOR ### `TENANT_PASSWORD` -This environment variable [is recommended](https://documentation.bonitasoft.com/bonita/7.7/tomcat-bundle#toc3) for you to use the Bonita image. It sets the tenant administrator password for Bonita. If it is not specified, the default password `install` will be used. +This environment variable [is recommended](https://documentation.bonitasoft.com/bonita/7.8/tomcat-bundle#toc3) for you to use the Bonita image. It sets the tenant administrator password for Bonita. If it is not specified, the default password `install` will be used. ### `TENANT_LOGIN` @@ -287,7 +287,7 @@ This optional environment variable is used in conjunction with `TENANT_PASSWORD` ### `REST_API_DYN_AUTH_CHECKS` -This optional environment variable is used to enable/disable [dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.7/rest-api-authorization#toc2) on Bonita REST API. The default value is `true`, which will activate dynamic authorization checking. +This optional environment variable is used to enable/disable [dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.8/rest-api-authorization#toc2) on Bonita REST API. The default value is `true`, which will activate dynamic authorization checking. ### `HTTP_API` @@ -321,7 +321,7 @@ These variables are used in conjunction to create a new user, set that user's pa ### `BIZ_DB_NAME`, `BIZ_DB_USER`, `BIZ_DB_PASS` -These variables are used in conjunction to create a new user, set that user's password and create the `bonita` [business database](https://documentation.bonitasoft.com/bonita/7.7/define-and-deploy-the-bdm#toc1). +These variables are used in conjunction to create a new user, set that user's password and create the `bonita` [business database](https://documentation.bonitasoft.com/bonita/7.8/define-and-deploy-the-bdm#toc1). `BIZ_DB_NAME` default value is `businessdb`. @@ -353,7 +353,7 @@ For example, you can increase the log level : mkdir -p custom_bonita echo '#!/bin/bash' > custom_bonita/bonita.sh - echo 'sed -i "s/^org.bonitasoft.level = WARNING$/org.bonitasoft.level = FINEST/" /opt/bonita/BonitaCommunity-7.7.5-Tomcat-8.5.31/server/conf/logging.properties' >> custom_bonita/bonita.sh + echo 'sed -i "s/^org.bonitasoft.level = WARNING$/org.bonitasoft.level = FINEST/" /opt/bonita/BonitaCommunity-7.8.0-Tomcat-8.5.34/server/conf/logging.properties' >> custom_bonita/bonita.sh chmod +x custom_bonita/bonita.sh docker run --name bonita_custom -v "$PWD"/custom_bonita/:/opt/custom-init.d -d -p 8080:8080 %%IMAGE%% @@ -362,5 +362,5 @@ Note: There are several ways to check the `bonita` logs. One of them is ```console $ docker exec -ti bonita_custom /bin/bash -tail -f /opt/bonita/BonitaCommunity-7.7.5-Tomcat-8.5.31/server/logs/bonita.`date +%Y-%m-%d`.log +tail -f /opt/bonita/BonitaCommunity-7.8.0-Tomcat-8.5.34/server/logs/bonita.`date +%Y-%m-%d`.log ```