Skip to content

Commit

Permalink
Update Bonita and Migration Tool versions
Browse files Browse the repository at this point in the history
  • Loading branch information
@benjaminParisel
benjaminParisel committed Jun 23, 2020
1 parent aeaaf6a commit 7c33f40
Showing 1 changed file with 22 additions and 22 deletions.
44 changes: 22 additions & 22 deletions bonita/content.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.10/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 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

Expand All @@ -24,7 +24,7 @@ You can access the Bonita Portal on http://localhost:8080/bonita and login using

PostgreSQL is the recommended database.

[Set max_prepared_transactions to 100](https://documentation.bonitasoft.com/bonita/7.10/database-configuration#toc5):
[Set max_prepared_transactions to 100](https://documentation.bonitasoft.com/bonita/7.11/database-configuration#toc5):

```console
$ mkdir -p custom_postgres
Expand All @@ -49,7 +49,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.10/database-configuration#toc5) which is set by default to 1M:
[Increase the packet size](https://documentation.bonitasoft.com/bonita/7.11/database-configuration#toc5) which is set by default to 1M:

```console
$ mkdir -p custom_mysql
Expand Down Expand Up @@ -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://release.ow2.org/bonita/bonita-migration-distrib-2.51.0.zip
wget https://release.ow2.org/bonita/bonita-migration-distrib-2.52.0.zip
wget https://download.forge.ow2.org/bonita/BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
unzip bonita-migration-distrib-2.51.0.zip
unzip bonita-migration-distrib-2.52.0.zip
unzip BonitaBPMCommunity-7.2.4-Tomcat-7.0.67.zip
```

Expand All @@ -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://release.ow2.org/bonita/bonita-migration-distrib-2.51.0.zip
unzip bonita-migration-distrib-2.51.0.zip
wget https://release.ow2.org/bonita/bonita-migration-distrib-2.52.0.zip
unzip bonita-migration-distrib-2.52.0.zip
```

- Configure the migration tool

```console
$ cd bonita-migration-distrib-2.51.0
$ cd bonita-migration-distrib-2.52.0
```

edit the migration tool config to point towards the copy of bonita home and db
Expand Down Expand Up @@ -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.10.5_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 %%IMAGE%%:7.10.5
$ docker run --name=bonita_7.11.0_postgres --link mydbpostgres:postgres -e "DB_NAME=newbonitadb" -e "DB_USER=newbonitauser" -e "DB_PASS=newbonitapass" -d -p 8081:8080 %%IMAGE%%:7.11.0
```

- Reapply specific configuration if needed, for example with a version >= 7.3.0 :

```console
$ docker exec -ti bonita_7.10.5_postgres /bin/bash
$ docker exec -ti bonita_7.11.0_postgres /bin/bash
```

```console
$ cd /opt/bonita/BonitaCommunity-7.10.5/setup
$ cd /opt/bonita/BonitaCommunity-7.11.0/setup
$ ./setup.sh pull
$ TENANT_LOGIN=tech_user
$ TENANT_PASSWORD=secret
Expand All @@ -258,26 +258,26 @@ The `-v /my/own/datadir:/opt/bonita` part of the command mounts the `/my/own/dat
```

```console
$ docker restart bonita_7.10.5_postgres
$ docker restart bonita_7.11.0_postgres
```

- Specific consideration regarding migration to Java 11 in Bonita 7.9

Bonita 7.9 docker image runs with Java 11. If you are migrating from an earlier version which runs Java 8, you should validate on a test environment that your custom code is compatible. Aside from just code incompatibility, special attention has to be given to the dependencies of the custom code, as they might not work in Java 11.

For more details regarding Bonita migration, see the [documentation](https://documentation.bonitasoft.com/bonita/7.10/migrate-from-an-earlier-version-of-bonita-bpm).
For more details regarding Bonita migration, see the [documentation](https://documentation.bonitasoft.com/bonita/7.11/migrate-from-an-earlier-version-of-bonita-bpm).

## Security

This Docker image activates both static and dynamic authorization checks by default on REST API. To be consistent, it also deactivates the HTTP API.

- REST API authorization

- [Static authorization checking](https://documentation.bonitasoft.com/bonita/7.10/rest-api-authorization#toc1)
- [Static authorization checking](https://documentation.bonitasoft.com/bonita/7.11/rest-api-authorization#toc1)

- [Dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.10/rest-api-authorization#toc2)
- [Dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.11/rest-api-authorization#toc2)

- [HTTP API](https://documentation.bonitasoft.com/bonita/7.10/rest-api-authorization#toc10)
- [HTTP API](https://documentation.bonitasoft.com/bonita/7.11/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:

Expand All @@ -291,23 +291,23 @@ 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.10/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.11/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`

This optional environment variable is used in conjunction with `PLATFORM_PASSWORD` to define the username for the platform administrator. If it is not specified, the default user `platformAdmin` will be used.

### `TENANT_PASSWORD`

This environment variable [is recommended](https://documentation.bonitasoft.com/bonita/7.10/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.11/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`

This optional environment variable is used in conjunction with `TENANT_PASSWORD` to define the username for the tenant administrator. If it is not specified, the default user of `install` will be used.

### `REST_API_DYN_AUTH_CHECKS`

This optional environment variable is used to enable/disable [dynamic authorization checking](https://documentation.bonitasoft.com/bonita/7.10/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.11/rest-api-authorization#toc2) on Bonita REST API. The default value is `true`, which will activate dynamic authorization checking.

### `HTTP_API`

Expand Down Expand Up @@ -341,7 +341,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.10/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.11/define-and-deploy-the-bdm#toc1).

`BIZ_DB_NAME` default value is `businessdb`.

Expand Down Expand Up @@ -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.10.5/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.0/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%%
Expand All @@ -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.10.5/server/logs/bonita.`date +%Y-%m-%d`.log
tail -f /opt/bonita/BonitaCommunity-7.11.0/server/logs/bonita.`date +%Y-%m-%d`.log
```

Since Bonita 7.9 bonita logs are redirected towards standard output and directly accessible using
Expand Down

0 comments on commit 7c33f40

Please sign in to comment.