Bonita Studio

Discover what Bonita Studio is, as well as its main features.

What Bonita Studio is

Bonita Studio is the central tool to design processes, data models and applications.
It is suited for both citizen developers (business analysts, project managers, power users) and application developers, with back-end java developers working in Bonita Studio and collaborating with front-end developers working in the UI Designer.

Bonita Studio contains a Bonita Runtime (Tomcat, UI Designer, Bonita Portal, Bonita Engine, and an h2 database), suitable for testing an application that is in development.
When you run a process, it is automatically deployed onto the development platform.

Bonita Studio is not intended for any use other than development. As a consequence, the Bonita stack embedded into the Bonita Studio can not be used for production purposes.

Main features

Architecture overview

Bonita Studio architecture

troubleshooting-icon Troubleshooting

Log files

In case of trouble when running Bonita Studio, you might want to take a look at log files.

Studio log file can be displayed from Bonita Studio in "Help" -> "Show Bonita Studio log" menu.

If Studio fails to start, you can open the log file manually. File is named .log and is located in <studio_folder>/workspace/.metadata folder.
Note that folder might be hidden and file might not be displayed if you choose to hide file extensions in your file manager.

JVM terminated. Exit code=1

If when launching the Studio you get an error message "JVM terminated. Exit code=1" it might be because you try to launch Bonita Studio with a version of the JVM that is not supported. See above "Configure Bonita Studio to use a specific JVM" how to force the JVM to use.

OutOfMemory error in Bonita Studio

After installation, you might see an OutOfMemory error in Bonita Studio. This error sometimes occurs when importing a large process definition.
The log messages are similar to the following:

!ENTRY org.bonitasoft.studio.importer 4 0 2014-04-25 09:43:49.467
!ERROR Import has failed for file Autorisation Engagement Depenses-2.0.bos

!ENTRY org.bonitasoft.studio.importer 4 0 2014-04-25 09:43:49.470
!ERROR
!STACK 0
java.lang.reflect.InvocationTargetException
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded

To fix this issue, you need to increase the memory allocated to the JVM that runs Bonita Studio.

Edit the *.ini file that corresponds to the executable you use to launch the Studio and modify this line: -Xmx512m to -Xmx1024m (or higher).

Then restart Bonita Studio.

OutOfMemory error in Bonita Studio embedded Tomcat server

When using connectors having a large amount of dependencies you may encounter some memory issue with the default -Xmx used for the tomcat server.
You can increase this value in Studio preferences -> Server settings -> Tomcat Maximum memory allocation.

Bonita Studio installation fail due to JVM errors

A given Bonita Studio version can only run with some specifics Java versions (hardware and software requirements).
If you encounter some issues related to the JVM during the installation, ensure first that a valid Java version is available. You can for exemple type java -version on a terminal, and informations about the main Java version used will be displayed.
If the problem persists, the easiest way to solve it is to remove the installed Java versions, to download the last stable build of the required Java version on the Oracle website and to install it properly.
Those issues can be related to bad Java installations, or to incompatibilities between a given Java version and Bitrock (Bitrock is the install builder used to install Bonita, it has the responsibility to detect the JRE used to install Bonita. Some defects on a given version could lead to incompatibility).

java.security.cert.CertificateException: No subject alternative DNS name matching github-releases.githubusercontent.com found.

Bonita Studio needs to retrieve some remote assets from Github. If the download of those assets fails with the above exception, it may be due to an out of date install of Java.
Install the latest supported Java package to fix this issue.