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 #1094 from Bonitasoft-Community/master 

update Bonita and migration tool version, apply product renaming (rem…
This commit is contained in:
yosifkit 2017-12-14 12:09:21 -06:00 committed by GitHub
parent e0ab4e5d0d 97ec76231b
commit f0975f00af
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 30 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bonita/README-short.txt
View File

@ -1 +1 @@
Bonita BPM is an open-source business process management and workflow suite
Bonita is an open-source business process management and workflow suite

52
bonita/content.md
View File

@ -1,6 +1,6 @@
# What is Bonita BPM?
# What is Bonita?
Bonita BPM is an open-source business process management and workflow suite created in 2001. It was started in France National Institute for Research in Computer Science, and then had incubated several years inside of the French computer science company Groupe Bull. Since 2009, the development of Bonita is supported by a company dedicated to this activity: Bonitasoft.
Bonita (called Bonita BPM till 7.5) is an open-source business process management and workflow suite created in 2001. It was started in France National Institute for Research in Computer Science, and then had incubated several years inside of the French computer science company Groupe Bull. Since 2009, the development of Bonita is supported by a company dedicated to this activity: Bonitasoft.
> [wikipedia.org/wiki/Bonita_BPM](http://en.wikipedia.org/wiki/Bonita_BPM)
@ -14,17 +14,17 @@ Bonita BPM is an open-source business process management and workflow suite crea
$ docker run --name bonita -d -p 8080:8080 %%IMAGE%%
```
This will start a container running the [Tomcat Bundle](http://documentation.bonitasoft.com/?page=tomcat-bundle) with Bonita BPM Engine + Bonita BPM 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 BPM uses a H2 database here.
This will start a container running the [Tomcat Bundle](https://documentation.bonitasoft.com/bonita/7.6/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 BPM Portal on http://localhost:8080/bonita and login using the default credentials: install / install
You can access the Bonita Portal on http://localhost:8080/bonita and login using the default credentials: install / install
## Link Bonita BPM to a database
## Link Bonita to a database
### PostgreSQL
PostgreSQL is the recommanded database.
[Set max_prepared_transactions to 100](http://documentation.bonitasoft.com/?page=database-configuration#toc4):
[Set max_prepared_transactions to 100](https://documentation.bonitasoft.com/bonita/7.6/database-configuration#toc4):
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](http://documentation.bonitasoft.com/?page=database-configuration#toc4) which is set by default to 1M:
[Increase the packet size](https://documentation.bonitasoft.com/bonita/7.6/database-configuration#toc4) which is set by default to 1M:
mkdir -p custom_mysql
echo "[mysqld]" > custom_mysql/bonita.cnf
@ -73,7 +73,7 @@ $ docker run --name bonita_mysql --link mydbmysql:mysql -d -p 8080:8080 %%IMAGE%
$ docker run --name=bonita -e "TENANT_LOGIN=tech_user" -e "TENANT_PASSWORD=secret" -e "PLATFORM_LOGIN=pfadmin" -e "PLATFORM_PASSWORD=pfsecret" -d -p 8080:8080 %%IMAGE%%
```
Now you can access the Bonita BPM Portal on localhost:8080/bonita and login using: tech_user / secret
Now you can access the Bonita Portal on localhost:8080/bonita and login using: tech_user / secret
## %%STACK%%
@ -103,7 +103,7 @@ Note that users on host systems with SELinux enabled may see issues with this. T
$ chcon -Rt svirt_sandbox_file_t /my/own/datadir
```
## Migrate from an earlier version of Bonita BPM
## Migrate from an earlier version of Bonita
- Stop the container to perform a backup
@ -163,9 +163,9 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
```console
cd bonita_migration
wget http://download.forge.ow2.org/bonita/bonita-migration-distrib-2.25.0.zip
wget http://download.forge.ow2.org/bonita/BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
unzip bonita-migration-distrib-2.25.0.zip
wget https://download.forge.ow2.org/bonita/bonita-migration-distrib-2.26.0.zip
wget https://download.forge.ow2.org/bonita/BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
unzip bonita-migration-distrib-2.26.0.zip
unzip BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
```
@ -180,13 +180,13 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
```console
cd bonita_migration
wget http://download.forge.ow2.org/bonita/bonita-migration-distrib-2.25.0.zip
unzip bonita-migration-distrib-2.25.0.zip
wget https://download.forge.ow2.org/bonita/bonita-migration-distrib-2.26.0.zip
unzip bonita-migration-distrib-2.26.0.zip
```
- Configure the migration tool
cd bonita-migration-distrib-2.25.0
cd bonita-migration-distrib-2.26.0
edit the migration tool config to point towards the copy of bonita home and db
@ -228,7 +228,7 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
```
```console
$ cd /opt/bonita/BonitaBPMCommunity-7.5.4-Tomcat-7.0.76/setup
$ cd /opt/bonita/BonitaCommunity-7.6.0-Tomcat-8.5.23/setup
$ ./setup.sh pull
$ TENANT_LOGIN=tech_user
$ TENANT_PASSWORD=secret
@ -251,7 +251,7 @@ $ chcon -Rt svirt_sandbox_file_t /my/own/datadir
$ docker restart bonita_7.5.4_postgres
```
For more details regarding Bonita migration, see the [documentation](http://documentation.bonitasoft.com/?page=migrate-from-an-earlier-version-of-bonita-bpm).
For more details regarding Bonita migration, see the [documentation](https://documentation.bonitasoft.com/bonita/7.6/migrate-from-an-earlier-version-of-bonita-bpm).
## Security
@ -259,11 +259,11 @@ This Docker image activates both static and dynamic authorization checks by defa
- REST API authorization
- [Static authorization checking](http://documentation.bonitasoft.com/?page=rest-api-authorization#toc1)
- [Static authorization checking](https://documentation.bonitasoft.com/bonita/7.6/rest-api-authorization#toc1)
- [Dynamic authorization checking](http://documentation.bonitasoft.com/?page=rest-api-authorization#toc2)
- [Dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.6/rest-api-authorization#toc2)
- [HTTP API](http://documentation.bonitasoft.com/?page=rest-api-authorization#toc9)
- [HTTP API](https://documentation.bonitasoft.com/bonita/7.6/rest-api-authorization#toc9)
For specific needs you can override this behavior by setting HTTP_API to true and REST_API_DYN_AUTH_CHECKS to false:
@ -277,7 +277,7 @@ When you start the `bonita` image, you can adjust the configuration of the Bonit
### `PLATFORM_PASSWORD`
This environment variable [is recommended](http://documentation.bonitasoft.com/?page=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.6/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`
@ -285,7 +285,7 @@ This optional environment variable is used in conjunction with `PLATFORM_PASSWOR
### `TENANT_PASSWORD`
This environment variable [is recommended](http://documentation.bonitasoft.com/?page=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.6/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`
@ -293,7 +293,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](http://documentation.bonitasoft.com/?page=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.6/rest-api-authorization#toc2) on Bonita REST API. The default value is `true`, which will activate dynamic authorization checking.
### `HTTP_API`
@ -327,7 +327,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](http://documentation.bonitasoft.com/?page=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.6/define-and-deploy-the-bdm#toc1).
`BIZ_DB_NAME` default value is `businessdb`.
@ -359,7 +359,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/BonitaBPMCommunity-7.5.4-Tomcat-7.0.76/server/conf/logging.properties' >> custom_bonita/bonita.sh
echo 'sed -i "s/^org.bonitasoft.level = WARNING$/org.bonitasoft.level = FINEST/" /opt/bonita/BonitaCommunity-7.6.0-Tomcat-8.5.23/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%%
@ -368,5 +368,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/BonitaBPMCommunity-7.5.4-Tomcat-7.0.76/server/logs/bonita.`date +%Y-%m-%d`.log
tail -f /opt/bonita/BonitaCommunity-7.6.0-Tomcat-8.5.23/server/logs/bonita.`date +%Y-%m-%d`.log
```

6
bonita/license.md
View File

@ -1,5 +1,5 @@
Bonita BPM image includes two parts :
Bonita image includes two parts :
- Bonita BPM Engine under [LGPL v2.1](https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html)
- Bonita Engine under [LGPL v2.1](https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html)
- Bonita BPM Portal under [GPL v2.0](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html)
- Bonita Portal under [GPL v2.0](http://www.gnu.org/licenses/old-licenses/gpl-2.0.html)

BIN
bonita/logo.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 4.3 KiB

After

Width:  |  Height:  |  Size: 5.6 KiB