Kogito is the next generation of business automation platform focused on cloud-native development, deployment and execution.
Homepage: http://kogito.kie.org
Wiki: https://github.com/kiegroup/kogito-tooling/wiki
JIRA: https://issues.jboss.org/projects/KOGITO
jBPM: https://www.jbpm.org/
Drools: https://www.drools.org/
This module contains a number of examples that you can take a look at and try out yourself. Please take a look at the readme of each individual example for more details on how the example works and how to run it yourself (either locally or on Kubernetes):
- jBPM + Quarkus Hello World: README.md
- jBPM + Quarkus: README.md
- jBPM + Spring Boot: README.md
- jBPM + Drools + Quarkus: README.md - Onboarding example combining one process and two decision services
- Polyglot Drools with GraalVM: README.md
- Drools + Quarkus: README.md
- Drools + Quarkus with Unit: README.md
In Kogito Tooling releases page you will find extensions and released tooling packages.
-
Check out the source:
git clone [email protected]:kiegroup/kogito-tooling.git
If you don't have a GitHub account use this command instead:
git clone https://github.com/kiegroup/kogito-tooling.git
-
Build with Yarn:
cd kogito-tooling yarn run init #prod yarn run build:prod # dev yarn run build # skips integration tests and production packing yarn run build:fast # skips lint and unit tests
Final artifacts will be on
packages/*/dist
directories.
NOTE: We currently pack two GWT-based editors -- BPMN and DMN. They are exploded WARs, so we don't commit them in this repo. We are currently working on automatically fetching them during the build, but we didn't do it yet. For builds to work properly, you must have the exploded WARs copied on
packages/unpacked-gwt-editors/
dmn
andbpmn
folders. You can go to the latest commit, click on the "check" icon and download the exploded WARs from the Artifacts tab. Be aware that each editor must go on its own folder.
- After you've successfully built the project following the instructions above, open the
packages/vscode-extension-pack-kogito-kie-editors
folder on VSCode. Use a new VSCode window so that thepackages/vscode-extension-pack-kogito-kie-editors
folder shows up as root in the VSCode explorer. - From there, you can Run the extension or the integration tests by using the
Debug
menu/section. You can also use the respective shortcuts (F5 to start debugging, for instance). - Remember! If you make changes to packages other than
packages/vscode-extension-pack-kogito-kie-editors
, you have to manually rebuild them before relaunching the extension on VSCode.
- After you've successfully built the project following the instructions above, open the
packages/chrome-extension-pack-kogito-kie-editors
folder on your favourite IDE. You can import the entire repo as well if you want to make changes to other packages. - Open a terminal and run
yarn run serve-envelope
onpackages/chrome-extension-pack-kogito-kie-editors
. This will start awebpack-dev-server
instance with the editors and their envelope. We use that because we don't pack the Chrome Extension bundle with the editors inside. Instead, we fetch them from GitHub pages. - Open Chrome and go to
chrome://extension
. Enable "Developer mode" on the top right corner and click on "Load unpacked". Choose thepackages/chrome-extension-pack-kogito-kie-editors/dist
folder. - From now on you can use the development version of the extension. Remember! After each change, you have to rebuild the changed modules and hit the "Refresh" button of the extension card.
All contributions are welcome! Before you start please read the Developing Drools and jBPM guide.
Here are some of the most notable ones for quick reference:
- Quarkus - Using Kogito to add business automation capabilities to an application - This guide demonstrates how your Quarkus application can use Kogito to add business automation to power it up with business processes and rules.
- Quarkus - Getting Started - Quarkus Getting Started guide