docker-library
/
docs
mirror of https://github.com/docker-library/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1829 from Bonitasoft-Community/master 

Bonita: adapt documentation to version 7.11.3
This commit is contained in:
yosifkit 2020-11-06 11:13:23 -08:00 committed by GitHub
parent 6bd5857106 57311a9e67
commit b44d5fb45c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
bonita/content.md
View File

@ -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 [Bonita runtime](https://documentation.bonitasoft.com/bonita/7.11/tomcat-bundle): a 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 [Bonita runtime](https://documentation.bonitasoft.com/bonita/7.11/tomcat-bundle): a Tomcat bundle with Bonita Engine + Bonita Portal. With no environment variables specified, it's as 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
@ -47,7 +47,7 @@ $ docker run --name bonita_postgres --link mydbpostgres:postgres -d -p 8080:8080
### MySQL
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.
There are known issues with the management of XA transactions by MySQL engine and driver: see MySQL bug [17343](http://bugs.mysql.com/bug.php?id=17343)
[Increase the packet size](https://documentation.bonitasoft.com/bonita/7.11/database-configuration#toc5) which is set by default to 1M:
@ -167,9 +167,9 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
```console
cd bonita_migration
wget https://github.com/bonitasoft/bonita-platform-releases/releases/download/7.11.0/bonita-migration-distrib-2.52.0.zip
wget https://github.com/bonitasoft/bonita-platform-releases/releases/download/7.11.2/bonita-migration-distrib-2.53.0.zip
wget https://download.forge.ow2.org/bonita/BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
unzip bonita-migration-distrib-2.52.0.zip
unzip bonita-migration-distrib-2.53.0.zip
unzip BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
```
@ -184,14 +184,14 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
```console
cd bonita_migration
wget https://github.com/bonitasoft/bonita-platform-releases/releases/download/7.11.0/bonita-migration-distrib-2.52.0.zip
unzip bonita-migration-distrib-2.52.0.zip
wget https://github.com/bonitasoft/bonita-platform-releases/releases/download/7.11.2/bonita-migration-distrib-2.53.0.zip
unzip bonita-migration-distrib-2.53.0.zip
```
- Configure the migration tool
```console
$ cd bonita-migration-distrib-2.52.0
$ cd bonita-migration-distrib-2.53.0
```
edit the migration tool config to point towards the copy of bonita home and db
@ -228,17 +228,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.11.2_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 %%IMAGE%%:7.11.2
$ docker run --name=bonita_7.11.3_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 %%IMAGE%%:7.11.3
```
- Reapply specific configuration if needed, for example with a version >= 7.3.0 :
```console
$ docker exec -ti bonita_7.11.2_postgres /bin/bash
$ docker exec -ti bonita_7.11.3_postgres /bin/bash
```
```console
$ cd /opt/bonita/BonitaCommunity-7.11.2/setup
$ cd /opt/bonita/BonitaCommunity-7.11.3/setup
$ ./setup.sh pull
$ TENANT_LOGIN=tech_user
$ TENANT_PASSWORD=secret
@ -258,7 +258,7 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
```
```console
$ docker restart bonita_7.11.2_postgres
$ docker restart bonita_7.11.3_postgres
```
- Specific consideration regarding migration to Java 11 in Bonita 7.9
@ -382,7 +382,7 @@ For example, you can increase the log level :
```console
$ 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.11.2/server/conf/logging.properties' >> custom_bonita/bonita.sh
$ echo 'sed -i "s/^org.bonitasoft.level = WARNING$/org.bonitasoft.level = FINEST/" /opt/bonita/BonitaCommunity-7.11.3/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%%
@ -400,7 +400,7 @@ Note: There are several ways to check the `bonita` logs. Till Bonita 7.8, one of
```console
$ docker exec -ti bonita_custom /bin/bash
tail -f /opt/bonita/BonitaCommunity-7.11.2/server/logs/bonita.`date +%Y-%m-%d`.log
tail -f /opt/bonita/BonitaCommunity-7.11.3/server/logs/bonita.`date +%Y-%m-%d`.log
```
Since Bonita 7.9 bonita logs are redirected towards standard output and directly accessible using

2
bonita/stack.yml
View File

@ -3,7 +3,7 @@ version: '3'
services:
db:
image: postgres:9.3
image: postgres:11
environment:
POSTGRES_PASSWORD: example
restart: always