Bonita WildFly bundle
You will find here the mandatory and optional steps needed to install and configure the WildFly bundle to run the Bonita platform.
The WildFly bundle is a zip archive that contains the Red Hat WildFly Java EE application server packaged with Bonita and Bonita platform setup tool. The WildFly bundle is a regular zip archive based on the WildFly zip distribution.
WARNING: Starting from Bonita 7.9.0 the Wildfly bundle is deprecated. It will be removed in a future release. Check the Release Note for more details.
For the Community edition:
Go to the Bonitasoft website and get the Bonita Community edition WildFly bundle.
For a Subscription edition:
Go to the Customer Portal and download the Bonita Subscription edition WildFly bundle.
The folder where you unzip the WildFly bundle is known as `<WILDFLY_HOME>`. We recommend the following locations:
/opt/Bonita. Make sure that Linux user account used to execute WildFly is the owner of the folders and files.
Whatever location you choose, do not leave blank spaces in the path to the directory, nor in the folder name.
The WildFly bundle is based on a standard WildFly installation with the following additions:
server/bin/standalone.conf: script to configure JVM system properties on Linux systems.
server/bin/standalone.conf.bat: script to configure JVM system properties on Windows systems.
server/modules/system/layers/base/sun/jdk/main/module.xml: list of base jdk module necessary for WildFly and Bonita to execute.
server/standalone/deployments/bonita-all-in-one-[version].ear: Bonita Portal (web application) and EJB3 API.
setup/: a tool to manage Bonita Platform configuration, stored in database instead of filesystem. Also ships a tool to centralize all the required WildFly bundle configuration.
setup/wildfly-templates/standalone.xml: WildFly context configuration for Bonita Portal. It defines data sources used by Bonita Engine.
tools/request_key_utils: folder containing the script to generate license request keys (Subscription editions only).
LDAP-Synchronizer: folder containing the tool to synchronize your organization in Bonita with your LDAP (Subscription editions only).
tools/cas-``cas.version`-module`: folder containing module files and description to enable CAS dependency to bonita EAR (Subscription editions only).
start-bonita.bat: script to start the bundle on Windows.
start-bonita.sh: script to start the bundle on Linux.
Beginning with version 7.3.0, Bonita Platform configuration, including the license file, is stored in the same database as the Bonita Engine data, namely in the
First, request a license. If this is the first time you generate a license, you need to generate a request key.
On the server where you installed Bonita Platform:
Go to the
generateRequestKey.batscript (for Windows) or the
generateRequestKey.shscript (for Linux)
Copy your request key and go to the Customer Portal license request page.
Fill in the details in the form, copy the request key in the Request Key field, and submit.
Note: keep the brackets () in the key; if the key is separated by a line break, remove it and put the key on a single line.
The license file will be sent to you by email.
When you receive your license:
If this is your first installation, copy the file to the
<WILDFLY_HOME>/setup/platform_conf/licenses folder before starting the bundle.
If this is a license update, use the Platform setup tool.
As a security precaution, we strongly recommend that before you start your application server, you change the default username and password used for the platform administrator and for the default tenant administrator.
The username and password for the platform administrator are defined in the file
<WILDFLY_HOME>/setup/platform_conf/initial/platform_engine/bonita-platform-community-custom.properties, by the following properties:
platformAdminUsernamedefines the username (default
platformAdminPassworddefines the password (default
This password is used for platform-level administration tasks, such as creating a tenant.
Each tenant has an administrator, with a tenant-specific username and password. The tenant administrator is also known as the tenant technical user.
When the platform is created, default values for the tenant administrator username and password are defined in the file
<WILDFLY_HOME>/setup/platform_conf/initial/tenant_template_engine/bonita-tenant-community-custom.properties, by the following properties:
userNamedefines the username (default
userPassworddefines the password (default
When you create a tenant, the tenant administrator is created with the default username and password, unless you specify new values.
Change these tenant-specific credentials for an existing tenant by updating the
userPassword properties in
For the default tenant, the tenant administrator username and password must also be changed in file
If you just want to try Bonita Platform with the embedded H2 database (only for development and testing phases of your project), you can skip this paragraph. For production, you are recommended to use one of the supported databases, with the following steps.
<WILDFLY_HOME>/setup/database.propertiesand modify the properties to suit your databases (Bonita internal database & Business Data database). Beware of backslash characters.
If you use Oracle database, copy your jdbc driver in
<WILDFLY_HOME>\start-bonita.bat(Windows system) or
<WILDFLY_HOME>/start-bonita.sh (Unix system)to run Bonita WildFly bundle (see WildFly start script)
The start-bonita script does the following:
For advanced server configuration needs: check out Bundle configuration to finely tune your WildFly bundle, using templates used by Bonita.
WildFly can be started by executing the following script:
Once you have your WildFly bundle up and running, complete these first steps to get Bonita Platform fully operational.
To update the configuration after the first run please take a look at the Platform setup tool
To update the licenses after the first run, take a look at the platform setup tool
Issue: When I restart the WildFly bundle, the Bonita application starts and then stops with message
WFLYSRV0009: Undeployed "bonita-all-in-one-...
Potential cause: There are too many elements to restart.
Solution: Increase the WildFly application deployment timeout in file
standalone.xml in folder
setup/wildlfy-templates. Look for
'<deployment-scanner ... deployment-timeout="600" ...'
and change it to a higher value (in seconds).
My Oracle database drivers do not seem to be taken into account when I put them in
Driver file must respect some naming convention.
For Oracle, rename it so that the name contains at least the word
ojdbc (case insensitive)
Issue: When I run
start-bonita.bat, I get the error message
Invalid Java version (1.7) < 1.8. Please set JAVA or JAVA_HOME variable to a JDK / JRE 1.8+
Cause: Bonita 7.4+ WildFly bundle requires Java 1.8 to run
Solution: Ensure your running environment has a JDK or JRE 1.8 installed and set either JAVA or JAVA_HOME environment variable to point to it.
Issue: When I start the Wildfly bundle configured to use a Microsoft SQL Server database, I get the error message
Cause: The WildFly configuration has not been properly updated
Solution: In the <WILDFLY_HOME>/server/modules/com/sqlserver/main/module.xml file, add
<module name="javax.xml.bind.api"/> in the list of dependencies