You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kie.apache.org by "pefernan (via GitHub)" <gi...@apache.org> on 2023/11/24 15:37:27 UTC
[PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
pefernan opened a new pull request, #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833
https://github.com/apache/incubator-kie-issues/issues/723
This PR includes the new `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` and including Jobs Service.
The README.md isn't finished yet... it's blocked by another issue.
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:
**WARNING! Please make sure you are opening your PR against `main` branch!**
- [ ] You have read the [contributors guide](https://github.com/kiegroup/kogito-runtimes#contributing-to-kogito)
- [ ] Pull Request title is properly formatted: `KOGITO-XYZ Subject`
- [ ] Pull Request title contains the target branch if not targeting main: `[0.9.x] KOGITO-XYZ Subject`
- [ ] Pull Request contains link to the JIRA issue
- [ ] Pull Request contains link to any dependent or related Pull Request
- [ ] Pull Request contains description of the issue
- [ ] Pull Request does not include fixes for issues other than the main ticket
<details>
<summary>
How to replicate CI configuration locally?
</summary>
Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use [build-chain tool](https://github.com/kiegroup/github-action-build-chain) to handle cross repository builds and be sure that we always use latest version of the code for each repository.
[build-chain tool](https://github.com/kiegroup/github-action-build-chain) is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See [local execution](https://github.com/kiegroup/github-action-build-chain#local-execution) details to get more information about it.
</details>
<details>
<summary>
How to retest this PR or trigger a specific build:
</summary>
- for <b>pull request checks</b>
Please add comment: <b>Jenkins retest this</b>
- for a <b>specific pull request check</b>
Please add comment: <b>Jenkins (re)run [kogito-examples] tests</b>
- for <b>quarkus branch checks</b>
Run checks against Quarkus current used branch
Please add comment: <b>Jenkins run quarkus-branch</b>
- for a <b>quarkus branch specific check</b>
Run checks against Quarkus current used branch
Please add comment: <b>Jenkins (re)run [kogito-examples] quarkus-branch</b>
- for <b>quarkus main checks</b>
Run checks against Quarkus main branch
Please add comment: <b>Jenkins run quarkus-main</b>
- for a <b>specific quarkus main check</b>
Run checks against Quarkus main branch
Please add comment: <b>Jenkins (re)run [kogito-examples] quarkus-main</b>
- for <b>quarkus lts checks</b>
Run checks against Quarkus lts branch
Please add comment: <b>Jenkins run quarkus-lts</b>
- for a <b>specific quarkus lts check</b>
Run checks against Quarkus lts branch
Please add comment: <b>Jenkins (re)run [kogito-examples] quarkus-lts</b>
- for <b>native checks</b>
Run native checks
Please add comment: <b>Jenkins run native</b>
- for a <b>specific native check</b>
Run native checks
Please add comment: <b>Jenkins (re)run [kogito-examples] native</b>
- for <b>native lts checks</b>
Run native checks against quarkus lts branch
Please add comment: <b>Jenkins run native-lts</b>
- for a <b>specific native lts check</b>
Run native checks against quarkus lts branch
Please add comment: <b>Jenkins (re)run [kogito-examples] native-lts</b>
</details>
<details>
<summary>
How to backport a pull request to a different branch?
</summary>
In order to automatically create a **backporting pull request** please add one or more labels having the following format `backport-<branch-name>`, where `<branch-name>` is the name of the branch where the pull request must be backported to (e.g., `backport-7.67.x` to backport the original PR to the `7.67.x` branch).
> **NOTE**: **backporting** is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.
Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.
> **NOTE**: this automated backporting is triggered whenever a pull request on `main` branch is labeled or closed, but both conditions must be satisfied to get the new PR created.
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1469197653
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "5432:5432"
+ volumes:
+ - ./sql:/docker-entrypoint-initdb.d:Z
+ healthcheck:
+ test: [ "CMD", "pg_isready", "-q", "-d", "kogito", "-U", "kogito-user" ]
+ timeout: 45s
+ interval: 10s
+ retries: 50
+ environment:
+ POSTGRES_USER: postgres
+ POSTGRES_PASSWORD: postgres
+
+ pgadmin:
+ container_name: pgadmin
+ image: dpage/pgadmin4:7.8
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - 8055:80
+ depends_on:
+ - postgres
+ volumes:
+ - ./pgadmin/servers.json:/pgadmin4/servers.json
+ environment:
+ PGADMIN_DEFAULT_EMAIL: user@user.org
+ PGADMIN_DEFAULT_PASSWORD: pass
+
+ data-index:
+ container_name: data-index
+ image: quay.io/kiegroup/kogito-data-index-postgresql:${KOGITO_VERSION}
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "8180:8080"
+ depends_on:
+ postgres:
+ condition: service_healthy
+ volumes:
+ - ./persistence:/home/kogito/data/protobufs/
+ environment:
+ QUARKUS_DATASOURCE_JDBC_URL: "jdbc:postgresql://postgres:5432/kogito"
+ QUARKUS_DATASOURCE_USERNAME: kogito-user
+ QUARKUS_DATASOURCE_PASSWORD: kogito-pass
+ QUARKUS_HTTP_CORS_ORIGINS: "/.*/"
+ QUARKUS_FLYWAY_MIGRATE_AT_START: "true"
+ QUARKUS_FLYWAY_BASELINE_ON_MIGRATE: "true"
+ QUARKUS_FLYWAY_TABLE: FLYWAY_DATAINDEX_SERVICE
+ QUARKUS_HIBERNATE_ORM_DATABASE_GENERATION: update
+ KOGITO_DATA_INDEX_QUARKUS_PROFILE: "http-events-support"
+ extra_hosts:
+ - "${DOCKER_GATEWAY_HOST}:host-gateway"
+
+ kogito-example-service:
+ container_name: kogito-example-service
+ image: dev.local/${USER}/kogito-example-service:1.0-SNAPSHOT
+ profiles: ["example", "full"]
+ ports:
+ - "8080:8080"
+ - "5005:5005"
+ depends_on:
+ data-index:
+ condition: service_started
+ environment:
+ QUARKUS_HTTP_CORS_ORIGINS: "/.*/"
+ QUARKUS_DATASOURCE_JDBC_URL: "jdbc:postgresql://postgres:5432/kogito"
+ QUARKUS_DATASOURCE_REACTIVE_URL: "postgresql://postgres:5432/kogito"
+ QUARKUS_DATASOURCE_USERNAME: kogito-user
+ QUARKUS_DATASOURCE_PASSWORD: kogito-pass
+ QUARKUS_DATASOURCE_DB_KIND: postgresql
+ KOGITO_JOBS_SERVICE_URL: http://${DOCKER_GATEWAY_HOST}:8080
+ KOGITO_SERVICE_URL: http://${DOCKER_GATEWAY_HOST}:8080
+ KOGITO_DATAINDEX_HTTP_URL: http://${DOCKER_GATEWAY_HOST}:8180
+ KOGITO_QUARKUS_JVM_PROPS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 -Dquarkus.datasource.reactive.url=postgresql://postgres:5432/kogito
Review Comment:
probably not needed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "martinweiler (via GitHub)" <gi...@apache.org>.
martinweiler commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1470226587
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,539 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until he gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip User Tasks.
+
+This example also demonstrates how to configure the whole *Kogito* environment using the new *Simplified Architecture* that
+enable simplifying the communication among *Kogito* services removing the need of events (Kafka/HTTP) between them. This can
+be achieved using the following *Quarkus* addons:
+- `kogito-addons-quarkus-data-index-persistence-postgresql`: enables the *Kogito Runtime* persisting directly into the
+*Data-Index* database.
+- `kogito-addons-quarkus-jobs`: enables collocating the *Jobs Service* inside the *Kogito Runtime*.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<div style="text-align:center">
+ <figure>
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png" alt="DMN Diagram">
+ <figcaption>New Hiring Offer DMN diagram</figcaption>
+ </figure>
+</div>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png" alt="DMN Type Definitions">
+ <figcaption>New Hiring Offer DMN types</figcaption>
+ </figure>
+</div>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decision.png" alt="DMN Decision">
+ <figcaption>New Hiring Offer DMN decision</figcaption>
+ </figure>
+</div>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/hiring_diagram.png" alt="Hiring Process Diagram">
+ <figcaption>Hiring Process Diagram</figcaption>
+ </figure>
+</div>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/generate_offer_assignments.png" alt="Offer assignments">
+ <figcaption><b>Generate base Offer</b> data assignments</figcaption>
+ </figure>
+</div>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *User Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/hr_interview_assignments.png" alt="HR Interview assignments">
+ <figcaption><b>HR Interviewr</b> task data assignments</figcaption>
+ </figure>
+</div>
+
+The **HR Interview** *User Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *User Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/it_interview_assignments.png" alt="IT Interview assignments">
+ <figcaption><b>IT Interviewr</b> task data assignments</figcaption>
+ </figure>
+</div>
+
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *User Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 17+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.9.3+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE_**: the docker compose template requires using _extra_hosts_ to allow the services use the host network, this may
+> carry some issues if you are using a **podman** version older than **4.7**.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
Review Comment:
in the ...(?)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1469286365
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "5432:5432"
+ volumes:
+ - ./sql:/docker-entrypoint-initdb.d:Z
+ healthcheck:
+ test: [ "CMD", "pg_isready", "-q", "-d", "kogito", "-U", "kogito-user" ]
+ timeout: 45s
+ interval: 10s
+ retries: 50
+ environment:
+ POSTGRES_USER: postgres
+ POSTGRES_PASSWORD: postgres
+
+ pgadmin:
+ container_name: pgadmin
+ image: dpage/pgadmin4:7.8
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - 8055:80
+ depends_on:
+ - postgres
+ volumes:
+ - ./pgadmin/servers.json:/pgadmin4/servers.json
+ environment:
+ PGADMIN_DEFAULT_EMAIL: user@user.org
+ PGADMIN_DEFAULT_PASSWORD: pass
+
+ data-index:
+ container_name: data-index
+ image: quay.io/kiegroup/kogito-data-index-postgresql:${KOGITO_VERSION}
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "8180:8080"
+ depends_on:
+ postgres:
+ condition: service_healthy
+ volumes:
+ - ./persistence:/home/kogito/data/protobufs/
+ environment:
+ QUARKUS_DATASOURCE_JDBC_URL: "jdbc:postgresql://postgres:5432/kogito"
+ QUARKUS_DATASOURCE_USERNAME: kogito-user
+ QUARKUS_DATASOURCE_PASSWORD: kogito-pass
+ QUARKUS_HTTP_CORS_ORIGINS: "/.*/"
+ QUARKUS_FLYWAY_MIGRATE_AT_START: "true"
+ QUARKUS_FLYWAY_BASELINE_ON_MIGRATE: "true"
+ QUARKUS_FLYWAY_TABLE: FLYWAY_DATAINDEX_SERVICE
+ QUARKUS_HIBERNATE_ORM_DATABASE_GENERATION: update
+ KOGITO_DATA_INDEX_QUARKUS_PROFILE: "http-events-support"
+ extra_hosts:
+ - "${DOCKER_GATEWAY_HOST}:host-gateway"
+
+ kogito-example-service:
+ container_name: kogito-example-service
+ image: dev.local/${USER}/kogito-example-service:1.0-SNAPSHOT
+ profiles: ["example", "full"]
+ ports:
+ - "8080:8080"
+ - "5005:5005"
+ depends_on:
+ data-index:
+ condition: service_started
+ environment:
+ QUARKUS_HTTP_CORS_ORIGINS: "/.*/"
+ QUARKUS_DATASOURCE_JDBC_URL: "jdbc:postgresql://postgres:5432/kogito"
+ QUARKUS_DATASOURCE_REACTIVE_URL: "postgresql://postgres:5432/kogito"
+ QUARKUS_DATASOURCE_USERNAME: kogito-user
+ QUARKUS_DATASOURCE_PASSWORD: kogito-pass
+ QUARKUS_DATASOURCE_DB_KIND: postgresql
+ KOGITO_JOBS_SERVICE_URL: http://${DOCKER_GATEWAY_HOST}:8080
+ KOGITO_SERVICE_URL: http://${DOCKER_GATEWAY_HOST}:8080
+ KOGITO_DATAINDEX_HTTP_URL: http://${DOCKER_GATEWAY_HOST}:8180
+ KOGITO_QUARKUS_JVM_PROPS: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=*:5005 -Dquarkus.datasource.reactive.url=postgresql://postgres:5432/kogito
Review Comment:
gosh, a leftover
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1469197309
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "5432:5432"
+ volumes:
+ - ./sql:/docker-entrypoint-initdb.d:Z
+ healthcheck:
+ test: [ "CMD", "pg_isready", "-q", "-d", "kogito", "-U", "kogito-user" ]
+ timeout: 45s
+ interval: 10s
+ retries: 50
+ environment:
+ POSTGRES_USER: postgres
+ POSTGRES_PASSWORD: postgres
+
+ pgadmin:
+ container_name: pgadmin
+ image: dpage/pgadmin4:7.8
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - 8055:80
+ depends_on:
+ - postgres
+ volumes:
+ - ./pgadmin/servers.json:/pgadmin4/servers.json
+ environment:
+ PGADMIN_DEFAULT_EMAIL: user@user.org
+ PGADMIN_DEFAULT_PASSWORD: pass
+
+ data-index:
+ container_name: data-index
+ image: quay.io/kiegroup/kogito-data-index-postgresql:${KOGITO_VERSION}
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "8180:8080"
+ depends_on:
+ postgres:
+ condition: service_healthy
+ volumes:
+ - ./persistence:/home/kogito/data/protobufs/
Review Comment:
do we need protobuf for postgresql indexing ¿?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1426824380
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
Review Comment:
Apparently that's a missing feature on `podman` prior `4.7`. I'll add a note warning about this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "porcelli (via GitHub)" <gi...@apache.org>.
porcelli commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1470283155
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
Review Comment:
@martinweiler my guess is because we have already defined the postgres dependency somewhere else and this is just aligned.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1471633626
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
Review Comment:
Upgraded to `postgres:16.1-alpine3.19`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "kie-ci3 (via GitHub)" <gi...@apache.org>.
kie-ci3 commented on PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#issuecomment-1827823515
**PR job** `#3` was: **UNSTABLE**
Possible explanation: This should be test failures
<details>
<summary><b>Reproducer</b></summary>
build-chain build full_downstream -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-examples -u https://github.com/apache/incubator-kie-kogito-examples/pull/1833 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution
</details>
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/3/display/redirect
**Test results:**
- PASSED: 371
- FAILED: 4
Those are the test failures:
<details>
<summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/3/testReport/org.kie.kogito.hr/HiringProcessIT/testCandidateNotMeetingRequirements/">org.kie.kogito.hr.HiringProcessIT.testCandidateNotMeetingRequirements</a></summary>
expected: <1> but was: <5>
</details>
<details>
<summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/3/testReport/org.kie.kogito.hr/HiringProcessIT/PR_check___Build_projects___testApprovalProcess/">PR check / Build projects / org.kie.kogito.hr.HiringProcessIT.testApprovalProcess</a></summary>
expected: <1> but was: <5>
</details>
<details>
<summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/3/testReport/org.kie.kogito.examples/DataIndexRestIT/testDataIndexRest/">org.kie.kogito.examples.DataIndexRestIT.testDataIndexRest</a></summary>
java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors<br/> [error]: Build step io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor#startKeycloakContainer threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startKeycloakContainer(KeycloakDevServicesProcessor.java:247)<br/> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br/> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)<br/> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<br/> at java.base/java.lang.reflect.Method.invoke(Method.java:566)<br/> at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)<br/> at io.quarkus.builder.BuildCon
text.run(BuildContext.java:281)<br/> at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)<br/> at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)<br/> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)<br/> at java.base/java.lang.Thread.run(Thread.java:829)<br/> at org.jboss.threads.JBossThread.run(JBossThread.java:501)<br/>Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed<br/> at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:349)<br/> at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:322)<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.lambda$startContainer$4(KeycloakDevServicesProcessor.java:372)<br/> at java.base/java.util.Optional.orElseGet(Optional.java:369)<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startContai
ner(KeycloakDevServicesProcessor.java:397)<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startKeycloakContainer(KeycloakDevServicesProcessor.java:195)<br/> ... 11 more<br/>Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception<br/> at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)<br/> at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:334)<br/> ... 16 more<br/>Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container<br/> at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:542)<br/> at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:344)<br/> at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)<br/> ... 17 more<br/>Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for lo
g output matching '.*Keycloak.*started.*'<br/> at org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)<br/> at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)<br/> at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:953)<br/> at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:485)<br/> ... 19 more<br/>
</details>
<details>
<summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/3/testReport/org.acme/AcmeExchangeResourceIT/unauthorizedTest/">org.acme.AcmeExchangeResourceIT.unauthorizedTest</a></summary>
java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors<br/> [error]: Build step io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor#startKeycloakContainer threw an exception: java.lang.RuntimeException: org.testcontainers.containers.ContainerLaunchException: Container startup failed<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startKeycloakContainer(KeycloakDevServicesProcessor.java:247)<br/> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br/> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)<br/> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<br/> at java.base/java.lang.reflect.Method.invoke(Method.java:566)<br/> at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)<br/> at io.quarkus.builder.BuildCon
text.run(BuildContext.java:281)<br/> at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)<br/> at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)<br/> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)<br/> at java.base/java.lang.Thread.run(Thread.java:829)<br/> at org.jboss.threads.JBossThread.run(JBossThread.java:501)<br/>Caused by: org.testcontainers.containers.ContainerLaunchException: Container startup failed<br/> at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:349)<br/> at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:322)<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.lambda$startContainer$4(KeycloakDevServicesProcessor.java:372)<br/> at java.base/java.util.Optional.orElseGet(Optional.java:369)<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startContai
ner(KeycloakDevServicesProcessor.java:397)<br/> at io.quarkus.oidc.deployment.devservices.keycloak.KeycloakDevServicesProcessor.startKeycloakContainer(KeycloakDevServicesProcessor.java:195)<br/> ... 11 more<br/>Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception<br/> at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)<br/> at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:334)<br/> ... 16 more<br/>Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container<br/> at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:542)<br/> at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:344)<br/> at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)<br/> ... 17 more<br/>Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for lo
g output matching '.*Keycloak.*started.*'<br/> at org.testcontainers.containers.wait.strategy.LogMessageWaitStrategy.waitUntilReady(LogMessageWaitStrategy.java:47)<br/> at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)<br/> at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:953)<br/> at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:485)<br/> ... 19 more<br/>
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "martinweiler (via GitHub)" <gi...@apache.org>.
martinweiler commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1470222164
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,539 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until he gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip User Tasks.
+
+This example also demonstrates how to configure the whole *Kogito* environment using the new *Simplified Architecture* that
Review Comment:
We agreed to use **Compact** Architecture now
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1472676721
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/src/main/resources/application.properties:
##########
@@ -0,0 +1,52 @@
+# Packaging
+#quarkus.package.type=fast-jar
+
+#https://quarkus.io/guides/openapi-swaggerui
+quarkus.http.cors=true
+quarkus.smallrye-openapi.path=/docs/openapi.json
+quarkus.swagger-ui.always-include=true
+quarkus.kogito.data-index.graphql.ui.always-include=true
+quarkus.http.test-port=0
+
+# Kogito-service
+kogito.service.url=http://localhost:8080
+
+#Job-service
+kogito.jobs-service.url=http://localhost:8080
+
+# to be reachable from the container running job-service
+kogito.dataindex.http.url=http://localhost:8180
+kogito.dataindex.ws.url=ws://localhost:8180
+
+# run create tables scripts
+quarkus.flyway.migrate-at-start=true
+quarkus.flyway.baseline-on-migrate=true
+quarkus.flyway.locations=classpath:/db/migration,classpath:/db/jobs-service
+quarkus.flyway.table=FLYWAY_RUNTIME_SERVICE
+quarkus.hibernate-orm.database.generation=update
Review Comment:
done
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/src/main/resources/application.properties:
##########
@@ -0,0 +1,52 @@
+# Packaging
+#quarkus.package.type=fast-jar
+
+#https://quarkus.io/guides/openapi-swaggerui
+quarkus.http.cors=true
+quarkus.smallrye-openapi.path=/docs/openapi.json
+quarkus.swagger-ui.always-include=true
+quarkus.kogito.data-index.graphql.ui.always-include=true
+quarkus.http.test-port=0
+
+# Kogito-service
+kogito.service.url=http://localhost:8080
+
+#Job-service
+kogito.jobs-service.url=http://localhost:8080
+
+# to be reachable from the container running job-service
+kogito.dataindex.http.url=http://localhost:8180
+kogito.dataindex.ws.url=ws://localhost:8180
+
+# run create tables scripts
+quarkus.flyway.migrate-at-start=true
+quarkus.flyway.baseline-on-migrate=true
+quarkus.flyway.locations=classpath:/db/migration,classpath:/db/jobs-service
Review Comment:
done
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1469201626
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,539 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until he gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip User Tasks.
+
+This example also demonstrates how to configure the whole *Kogito* environment using the new *Simplified Architecture* that
Review Comment:
I guess who is our target as user. If we are focusing engineers probably classic or monolith could be ok.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1469200256
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/README.md:
##########
@@ -0,0 +1,57 @@
+# Kogito and Infrastructure services
+
+To allow a quick setup of all services required to run this demo, we provide a docker compose template that starts the following services:
+- Postgresql
+- PgAdmin
+- Kogito Data Index
+- Kogito Example Service (Only available if the example has been compiled using the `container` mvn profile eg: ```mvn cleanp package -Dcontainer```)
+- Kogito Management Console
+- Kogito Task Console
+- Keycloak
Review Comment:
data audit ¿?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1411714590
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
Review Comment:
"until he gets hired."
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
+
+If you want to start only the example and the minimal Infrastructure Services (PostgreSQL, Data-Index and Jobs Service),
+you can run the same `startServices.sh` script but passing the `example` argument
+
+```shell
+sh startServices.sh example
+```
+
+### Running the example in Development mode
+
+To run the example in Development mode, just run the following command in a Terminal:
+
+```shell
+mvn clean package quarkus:dev -Pdevelopment
+```
+
+The Development Mode will embed all the needed Infrastructure Services (PostgreSQL, Data-Index & Jobs Service) and wont
Review Comment:
won't
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
Review Comment:
persist into the database the "Data-Index", simplifying the communication among services removing the need...
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
+
+If you want to start only the example and the minimal Infrastructure Services (PostgreSQL, Data-Index and Jobs Service),
+you can run the same `startServices.sh` script but passing the `example` argument
+
+```shell
+sh startServices.sh example
+```
+
+### Running the example in Development mode
+
+To run the example in Development mode, just run the following command in a Terminal:
+
+```shell
+mvn clean package quarkus:dev -Pdevelopment
Review Comment:
`2023-12-01 09:40:10,663 li-1a3d434c-313e-11b2-a85c-bf221e769faa INFO [org.kie.kogito.quarkus.workflow.deployment.devservices.DataIndexInMemoryContainer:68] (docker-java-stream-1699578725) STDOUT: 2023-12-01 08:40:10,614 ERROR [io.sma.rea.mes.provider] (executor-thread-0) SRMSG00200: The method org.kie.kogito.index.service.messaging.BlockingMessagingEventConsumer#onProcessInstanceEvent has thrown an exception: java.lang.ClassCastException: class com.fasterxml.jackson.databind.node.NullNode cannot be cast to class com.fasterxml.jackson.databind.node.ObjectNode (com.fasterxml.jackson.databind.node.NullNode and com.fasterxml.jackson.databind.node.ObjectNode are in unnamed module of loader io.quarkus.bootstrap.runner.RunnerClassLoader @6f75e721)
`
I guess this is related to the start date in a node.
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
+
+If you want to start only the example and the minimal Infrastructure Services (PostgreSQL, Data-Index and Jobs Service),
+you can run the same `startServices.sh` script but passing the `example` argument
+
+```shell
+sh startServices.sh example
+```
+
+### Running the example in Development mode
+
+To run the example in Development mode, just run the following command in a Terminal:
+
+```shell
+mvn clean package quarkus:dev -Pdevelopment
Review Comment:
it seems there is a problem.
`2023-12-01 09:31:02,337 li-1a3d434c-313e-11b2-a85c-bf221e769faa ERROR [org.kie.kogito.quarkus.workflow.devservices.DataIndexEventPublisher:71] (vert.x-eventloop-thread-1) Failed to send message to Data Index: io.vertx.core.impl.NoStackTraceThrowable: Response status code 404 is not equal to 202`
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
+
+If you want to start only the example and the minimal Infrastructure Services (PostgreSQL, Data-Index and Jobs Service),
+you can run the same `startServices.sh` script but passing the `example` argument
Review Comment:
you can run the same... script passing the example...
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
Review Comment:
Observations (no need fix)
1) does not work with podman
2) host-gateway not recognized in some version (company rhel distro)
3) keycloack realm is not being loaded (does not bind file system)
during execution got this error. Probably podamn problem
`[kogito-example-service] | 2023-12-01 08:16:17,837 ERROR [org.kie.kog.job.man.qua.VertxJobsService] (vert.x-eventloop-thread-1) Scheduling of job Job{id='94c105b2-489d-44b7-ab62-f1d8d7ec870f', correlationId='94c105b2-489d-44b7-ab62-f1d8d7ec870f', state=null, schedule=TimerSchedule{startTime='2023-12-01T08:18:17.476Z', repeatCount=0, delay=null, delayUnit='MILLIS'}, retry=null, recipient=HttpRecipient{url='http://172.17.0.1:8080/management/jobs/hiring/instances/40d71796-27f2-423a-a095-aadb12ccf078/timers/1', method='POST', headers={processInstanceId=40d71796-27f2-423a-a095-aadb12ccf078, nodeInstanceId=5e57cb85-feb4-45ba-82ac-4bd8cf0c5f07, processId=hiring, rootProcessId=null, rootProcessInstanceId=null, Content-Type=application/json}, queryParams={}, payload=org.kie.kogito.jobs.service.api.recipient.http.HttpRecipientJsonPayloadData@ed2358d0} org.kie.kogito.jobs.service.api.recipient.http.HttpRecipient@346e4a23, executionTimeout=null, executionTimeoutUnit=null} failed with respons
e code 0: io.netty.channel.ConnectTimeoutException: connection timed out: /172.17.0.1:8580
`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1469198936
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/src/main/resources/application.properties:
##########
@@ -0,0 +1,52 @@
+# Packaging
+#quarkus.package.type=fast-jar
+
+#https://quarkus.io/guides/openapi-swaggerui
+quarkus.http.cors=true
+quarkus.smallrye-openapi.path=/docs/openapi.json
+quarkus.swagger-ui.always-include=true
+quarkus.kogito.data-index.graphql.ui.always-include=true
+quarkus.http.test-port=0
+
+# Kogito-service
+kogito.service.url=http://localhost:8080
+
+#Job-service
+kogito.jobs-service.url=http://localhost:8080
+
+# to be reachable from the container running job-service
+kogito.dataindex.http.url=http://localhost:8180
+kogito.dataindex.ws.url=ws://localhost:8180
+
+# run create tables scripts
+quarkus.flyway.migrate-at-start=true
+quarkus.flyway.baseline-on-migrate=true
+quarkus.flyway.locations=classpath:/db/migration,classpath:/db/jobs-service
+quarkus.flyway.table=FLYWAY_RUNTIME_SERVICE
+quarkus.hibernate-orm.database.generation=update
+
+kogito.persistence.type=jdbc
+quarkus.datasource.db-kind=postgresql
+%prod.quarkus.datasource.username=kogito-user
+%prod.quarkus.datasource.password=kogito-pass
+%prod.quarkus.datasource.jdbc.url=${QUARKUS_DATASOURCE_JDBC_URL:jdbc:postgresql://localhost:5432/kogito}
+%prod.quarkus.datasource.reactive.url=${QUARKUS_DATASOURCE_REACTIVE_URL:postgresql://localhost:5432/kogito}
+
+quarkus.native.native-image-xmx=8g
+
+# profile to pack this example into a container, to use it execute activate the maven container profile, -Pcontainer
+%container.quarkus.container-image.build=true
+%container.quarkus.container-image.push=false
+%container.quarkus.container-image.group=${USER}
+%container.quarkus.container-image.registry=dev.local
+%container.quarkus.container-image.tag=1.0-SNAPSHOT
+%container.quarkus.jib.jvm-entrypoint=/home/kogito/kogito-app-launch.sh
+%container.quarkus.jib.base-jvm-image=quay.io/kiegroup/kogito-runtime-jvm-nightly:latest
Review Comment:
we should open a jira bout this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "martinweiler (via GitHub)" <gi...@apache.org>.
martinweiler commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1470275437
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "5432:5432"
+ volumes:
+ - ./sql:/docker-entrypoint-initdb.d:Z
+ healthcheck:
+ test: [ "CMD", "pg_isready", "-q", "-d", "kogito", "-U", "kogito-user" ]
+ timeout: 45s
+ interval: 10s
+ retries: 50
+ environment:
+ POSTGRES_USER: postgres
+ POSTGRES_PASSWORD: postgres
+
+ pgadmin:
+ container_name: pgadmin
+ image: dpage/pgadmin4:7.8
Review Comment:
same as with postgres, we might want to use a more recent version (eg. dpage/pgadmin4:8.2)?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "martinweiler (via GitHub)" <gi...@apache.org>.
martinweiler commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1470274446
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
Review Comment:
why are we using such an old version here? wouldn't it make sense to have something more recent out-of-the-box, eg. postgres:16.1-alpine3.19
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "martinweiler (via GitHub)" <gi...@apache.org>.
martinweiler commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1468205026
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,539 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until he gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip User Tasks.
+
+This example also demonstrates how to configure the whole *Kogito* environment using the new *Simplified Architecture* that
+enable simplifying the communication among *Kogito* services removing the need of events (Kafka/HTTP) between them. This can
+be achieved using the following *Quarkus* addons:
+- `kogito-addons-quarkus-data-index-persistence-postgresql`: enables the *Kogito Runtime* persisting directly into the
+*Data-Index* database.
+- `kogito-addons-quarkus-jobs`: enables collocating the *Jobs Service* inside the *Kogito Runtime*.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<div style="text-align:center">
+ <figure>
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png" alt="DMN Diagram">
+ <figcaption>New Hiring Offer DMN diagram</figcaption>
+ </figure>
+</div>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png" alt="DMN Type Definitions">
+ <figcaption>New Hiring Offer DMN types</figcaption>
+ </figure>
+</div>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decision.png" alt="DMN Decision">
+ <figcaption>New Hiring Offer DMN decision</figcaption>
+ </figure>
+</div>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/hiring_diagram.png" alt="Hiring Process Diagram">
+ <figcaption>Hiring Process Diagram</figcaption>
+ </figure>
+</div>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/generate_offer_assignments.png" alt="Offer assignments">
+ <figcaption><b>Generate base Offer</b> data assignments</figcaption>
+ </figure>
+</div>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *User Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/hr_interview_assignments.png" alt="HR Interview assignments">
+ <figcaption><b>HR Interviewr</b> task data assignments</figcaption>
+ </figure>
+</div>
+
+The **HR Interview** *User Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *User Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<div style="text-align:center">
+ <figure>
+ <img width=75% src="docs/images/it_interview_assignments.png" alt="IT Interview assignments">
+ <figcaption><b>IT Interviewr</b> task data assignments</figcaption>
+ </figure>
+</div>
+
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *User Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 17+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.9.3+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
Review Comment:
remove kafka
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1470934711
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "5432:5432"
+ volumes:
+ - ./sql:/docker-entrypoint-initdb.d:Z
+ healthcheck:
+ test: [ "CMD", "pg_isready", "-q", "-d", "kogito", "-U", "kogito-user" ]
+ timeout: 45s
+ interval: 10s
+ retries: 50
+ environment:
+ POSTGRES_USER: postgres
+ POSTGRES_PASSWORD: postgres
+
+ pgadmin:
+ container_name: pgadmin
+ image: dpage/pgadmin4:7.8
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - 8055:80
+ depends_on:
+ - postgres
+ volumes:
+ - ./pgadmin/servers.json:/pgadmin4/servers.json
+ environment:
+ PGADMIN_DEFAULT_EMAIL: user@user.org
+ PGADMIN_DEFAULT_PASSWORD: pass
+
+ data-index:
+ container_name: data-index
+ image: quay.io/kiegroup/kogito-data-index-postgresql:${KOGITO_VERSION}
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "8180:8080"
+ depends_on:
+ postgres:
+ condition: service_healthy
+ volumes:
+ - ./persistence:/home/kogito/data/protobufs/
Review Comment:
Well, that's to enable data-index index the domain models, that's not necessarily needed.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1472506670
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/src/main/resources/application.properties:
##########
@@ -0,0 +1,52 @@
+# Packaging
+#quarkus.package.type=fast-jar
+
+#https://quarkus.io/guides/openapi-swaggerui
+quarkus.http.cors=true
+quarkus.smallrye-openapi.path=/docs/openapi.json
+quarkus.swagger-ui.always-include=true
+quarkus.kogito.data-index.graphql.ui.always-include=true
+quarkus.http.test-port=0
+
+# Kogito-service
+kogito.service.url=http://localhost:8080
+
+#Job-service
+kogito.jobs-service.url=http://localhost:8080
+
+# to be reachable from the container running job-service
+kogito.dataindex.http.url=http://localhost:8180
+kogito.dataindex.ws.url=ws://localhost:8180
+
+# run create tables scripts
+quarkus.flyway.migrate-at-start=true
+quarkus.flyway.baseline-on-migrate=true
+quarkus.flyway.locations=classpath:/db/migration,classpath:/db/jobs-service
Review Comment:
I don't see the classpath for data index pgsql here.
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/src/main/resources/application.properties:
##########
@@ -0,0 +1,52 @@
+# Packaging
+#quarkus.package.type=fast-jar
+
+#https://quarkus.io/guides/openapi-swaggerui
+quarkus.http.cors=true
+quarkus.smallrye-openapi.path=/docs/openapi.json
+quarkus.swagger-ui.always-include=true
+quarkus.kogito.data-index.graphql.ui.always-include=true
+quarkus.http.test-port=0
+
+# Kogito-service
+kogito.service.url=http://localhost:8080
+
+#Job-service
+kogito.jobs-service.url=http://localhost:8080
+
+# to be reachable from the container running job-service
+kogito.dataindex.http.url=http://localhost:8180
+kogito.dataindex.ws.url=ws://localhost:8180
+
+# run create tables scripts
+quarkus.flyway.migrate-at-start=true
+quarkus.flyway.baseline-on-migrate=true
+quarkus.flyway.locations=classpath:/db/migration,classpath:/db/jobs-service
+quarkus.flyway.table=FLYWAY_RUNTIME_SERVICE
+quarkus.hibernate-orm.database.generation=update
Review Comment:
this needs to be removed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "martinweiler (via GitHub)" <gi...@apache.org>.
martinweiler commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1468192946
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,539 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until he gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip User Tasks.
+
+This example also demonstrates how to configure the whole *Kogito* environment using the new *Simplified Architecture* that
Review Comment:
Is "Simplified Architecture" the term we want to use? I know we have used it internally and it makes sense if you are aware of initial architecture design, but new users might get a wrong idea of what "simplified" means. WDYT @porcelli @kmacedovarela ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "elguardian (via GitHub)" <gi...@apache.org>.
elguardian commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1469198936
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/src/main/resources/application.properties:
##########
@@ -0,0 +1,52 @@
+# Packaging
+#quarkus.package.type=fast-jar
+
+#https://quarkus.io/guides/openapi-swaggerui
+quarkus.http.cors=true
+quarkus.smallrye-openapi.path=/docs/openapi.json
+quarkus.swagger-ui.always-include=true
+quarkus.kogito.data-index.graphql.ui.always-include=true
+quarkus.http.test-port=0
+
+# Kogito-service
+kogito.service.url=http://localhost:8080
+
+#Job-service
+kogito.jobs-service.url=http://localhost:8080
+
+# to be reachable from the container running job-service
+kogito.dataindex.http.url=http://localhost:8180
+kogito.dataindex.ws.url=ws://localhost:8180
+
+# run create tables scripts
+quarkus.flyway.migrate-at-start=true
+quarkus.flyway.baseline-on-migrate=true
+quarkus.flyway.locations=classpath:/db/migration,classpath:/db/jobs-service
+quarkus.flyway.table=FLYWAY_RUNTIME_SERVICE
+quarkus.hibernate-orm.database.generation=update
+
+kogito.persistence.type=jdbc
+quarkus.datasource.db-kind=postgresql
+%prod.quarkus.datasource.username=kogito-user
+%prod.quarkus.datasource.password=kogito-pass
+%prod.quarkus.datasource.jdbc.url=${QUARKUS_DATASOURCE_JDBC_URL:jdbc:postgresql://localhost:5432/kogito}
+%prod.quarkus.datasource.reactive.url=${QUARKUS_DATASOURCE_REACTIVE_URL:postgresql://localhost:5432/kogito}
+
+quarkus.native.native-image-xmx=8g
+
+# profile to pack this example into a container, to use it execute activate the maven container profile, -Pcontainer
+%container.quarkus.container-image.build=true
+%container.quarkus.container-image.push=false
+%container.quarkus.container-image.group=${USER}
+%container.quarkus.container-image.registry=dev.local
+%container.quarkus.container-image.tag=1.0-SNAPSHOT
+%container.quarkus.jib.jvm-entrypoint=/home/kogito/kogito-app-launch.sh
+%container.quarkus.jib.base-jvm-image=quay.io/kiegroup/kogito-runtime-jvm-nightly:latest
Review Comment:
we should open a jira bout this. the image is useless.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "kmacedovarela (via GitHub)" <gi...@apache.org>.
kmacedovarela commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1456197647
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
+
+If you want to start only the example and the minimal Infrastructure Services (PostgreSQL, Data-Index and Jobs Service),
+you can run the same `startServices.sh` script but passing the `example` argument
+
+```shell
+sh startServices.sh example
+```
+
+### Running the example in Development mode
+
+To run the example in Development mode, just run the following command in a Terminal:
+
+```shell
+mvn clean package quarkus:dev -Pdevelopment
+```
+
+The Development Mode will embed all the needed Infrastructure Services (PostgreSQL, Data-Index & Jobs Service) and wont
+require any extra step.
+
+The `development` profile includes the **Runtime Tools Quarkus Extension** that exposes a new section in the **Quarkus Dev-UI**
+unifying the **Management Console** & **Task Console** functionalities. **Quarkus Dev-UI** is available at http://localhost:8080/q/dev
+
+> **_NOTE:_** For more information about how to work with Kogito Runtime Tools Quarkus Extension, please refer to the [Kogito Documentation](https://docs.kogito.kie.org/latest/html_single/#con-runtime-tools-dev-ui_kogito-developing-process-services) page.
+
+### Starting an instance of the Hiring Process
+
+Once the service is up and running you can make use of the **Hiring** application by a sending request to `http://localhost:8080/hiring`.
+
+Sending the following valid `CandidateData` will start a process instance that will land into the *HR Interview* task:
+
+```json
+{
+ "candidateData": {
+ "name": "Jon",
+ "lastName": "Snow",
+ "email": "jon@snow.org",
+ "experience": 5,
+ "skills": [
+ "Java", "Kogito", "Fencing"
+ ]
+ }
+}
+```
+
+In a Terminal you can execute this curl command to start a **Hiring** process:
+```bash
+curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST http://localhost:8080/hiring -d '{"candidateData": { "name": "Jon", "lastName": "Snow", "email": "jon@snow.org", "experience": 5, "skills": ["Java", "Kogito", "Fencing"]}}'
+```
+
+If everything went well you may get a response like:
+```json
+{
+ "id": "628e679f-4deb-4abc-9f28-668914c64ef9",
+ "offer": {
+ "category": "Senior Software Engineer",
+ "salary": 40450
+ }
+}
+```
+
+In the server log You may find a trace like:
+```text
+New Hiring has been created for candidate: Jon Snow
+###################################
+Generated offer for candidate: Jon Snow
+Job Category: Senior Software Engineer
+Base salary: 40450
+###################################
+```
+
+Use the following `CandidateData` that don't match the minimal candidate requirements, to start a process that will automatically end:
+```json
+{
+ "candidateData": {
+ "name": "Jon",
+ "lastName": "Snow",
+ "email": "jon@snow.org",
+ "experience": 0,
+ "skills": []
+ }
+}
+```
+
+In a Terminal you can execute this curl command to start a **Hiring** process:
+```bash
+curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST http://localhost:8080/hiring -d '{"candidateData": { "name": "Jon", "lastName": "Snow", "email": "jon@snow.org", "experience": 0, "skills": []}}'
+```
+
+If everything went well you may get a response like:
+```json
+{
+ "id": "3659601a-bb59-458d-859e-7892621ad5b7",
+ "offer": null
+}
+```
+
+In the server log You may find a trace like:
+```text
+New Hiring has been created for candidate: Jon Snow
+###################################
+Candidate Jon Snow don't meet the requirements for the position but we'll keep it on records for the future!
+###################################
+```
+
+### Using Keycloak as Authentication Server
+
+In this Quickstart we'll be using [Keycloak](https://www.keycloak.org/) as *Authentication Server*. It will be started as a part of the project *Infrastructure Services*, you can check the configuration on the project [docker-compose.yml](docker-compose/docker-compose.yml) in [docker-compose](docker-compose) folder.
+
+It will install the *Kogito Realm* that comes with a predefined set of users:
+
+| Login | Password | Roles |
+| ------------- | ---------- | ------------------- |
+| admin | admin | *admin*, *managers* |
+| alice | alice | *user* |
+| jdoe | jdoe | *managers* |
+
+Once Keycloak is started, you should be able to access your *Keycloak Server* at [localhost:8480/auth](http://localhost:8480/auth) with *admin* user.
+
+> **_NOTE:_** This example uses keycloak authentication to enable security only in the consoles not in runtime.
+
+### Show active Hiring process instance at Kogito Management Console
+
+To access the Kogito Management Console just open your browser and navigate to ``http://localhost:8280``. You'll be redirected to the *Keycloak* log in page.
+
+<p align="center">
+ <img width=75% src="docs/images/keycloak-login.png">
+</p>
+
+Once there, log in using any of the users specified in the [Using Keycloak as Authentication Server](#using-keycloak-as-authentication-server)
+
+<p align="center">
+ <img width=75% src="docs/images/mc_list.png">
+</p>
+
+> **_NOTE:_** For more information about how to work with Kogito Management Console, please refer to the [Kogito Documentation](https://docs.kogito.kie.org/latest/html_single/#con-management-console_kogito-developing-process-services) page.
+
+Check the process instance details to see where is the execution path
+
+<p align="center">
+ <img width=75% src="docs/images/MC_details_1.png">
Review Comment:
broken image, probably cuz of the capital letters on the filename.
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
+
+If you want to start only the example and the minimal Infrastructure Services (PostgreSQL, Data-Index and Jobs Service),
+you can run the same `startServices.sh` script but passing the `example` argument
+
+```shell
+sh startServices.sh example
+```
+
+### Running the example in Development mode
+
+To run the example in Development mode, just run the following command in a Terminal:
+
+```shell
+mvn clean package quarkus:dev -Pdevelopment
+```
+
+The Development Mode will embed all the needed Infrastructure Services (PostgreSQL, Data-Index & Jobs Service) and wont
+require any extra step.
+
+The `development` profile includes the **Runtime Tools Quarkus Extension** that exposes a new section in the **Quarkus Dev-UI**
+unifying the **Management Console** & **Task Console** functionalities. **Quarkus Dev-UI** is available at http://localhost:8080/q/dev
+
+> **_NOTE:_** For more information about how to work with Kogito Runtime Tools Quarkus Extension, please refer to the [Kogito Documentation](https://docs.kogito.kie.org/latest/html_single/#con-runtime-tools-dev-ui_kogito-developing-process-services) page.
+
+### Starting an instance of the Hiring Process
+
+Once the service is up and running you can make use of the **Hiring** application by a sending request to `http://localhost:8080/hiring`.
+
+Sending the following valid `CandidateData` will start a process instance that will land into the *HR Interview* task:
+
+```json
+{
+ "candidateData": {
+ "name": "Jon",
+ "lastName": "Snow",
+ "email": "jon@snow.org",
+ "experience": 5,
+ "skills": [
+ "Java", "Kogito", "Fencing"
+ ]
+ }
+}
+```
+
+In a Terminal you can execute this curl command to start a **Hiring** process:
+```bash
+curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST http://localhost:8080/hiring -d '{"candidateData": { "name": "Jon", "lastName": "Snow", "email": "jon@snow.org", "experience": 5, "skills": ["Java", "Kogito", "Fencing"]}}'
+```
+
+If everything went well you may get a response like:
+```json
+{
+ "id": "628e679f-4deb-4abc-9f28-668914c64ef9",
+ "offer": {
+ "category": "Senior Software Engineer",
+ "salary": 40450
+ }
+}
+```
+
+In the server log You may find a trace like:
+```text
+New Hiring has been created for candidate: Jon Snow
+###################################
+Generated offer for candidate: Jon Snow
+Job Category: Senior Software Engineer
+Base salary: 40450
+###################################
+```
+
+Use the following `CandidateData` that don't match the minimal candidate requirements, to start a process that will automatically end:
+```json
+{
+ "candidateData": {
+ "name": "Jon",
+ "lastName": "Snow",
+ "email": "jon@snow.org",
+ "experience": 0,
+ "skills": []
+ }
+}
+```
+
+In a Terminal you can execute this curl command to start a **Hiring** process:
+```bash
+curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST http://localhost:8080/hiring -d '{"candidateData": { "name": "Jon", "lastName": "Snow", "email": "jon@snow.org", "experience": 0, "skills": []}}'
+```
+
+If everything went well you may get a response like:
+```json
+{
+ "id": "3659601a-bb59-458d-859e-7892621ad5b7",
+ "offer": null
+}
+```
+
+In the server log You may find a trace like:
+```text
+New Hiring has been created for candidate: Jon Snow
+###################################
+Candidate Jon Snow don't meet the requirements for the position but we'll keep it on records for the future!
+###################################
+```
+
+### Using Keycloak as Authentication Server
+
+In this Quickstart we'll be using [Keycloak](https://www.keycloak.org/) as *Authentication Server*. It will be started as a part of the project *Infrastructure Services*, you can check the configuration on the project [docker-compose.yml](docker-compose/docker-compose.yml) in [docker-compose](docker-compose) folder.
+
+It will install the *Kogito Realm* that comes with a predefined set of users:
+
+| Login | Password | Roles |
+| ------------- | ---------- | ------------------- |
+| admin | admin | *admin*, *managers* |
+| alice | alice | *user* |
+| jdoe | jdoe | *managers* |
+
+Once Keycloak is started, you should be able to access your *Keycloak Server* at [localhost:8480/auth](http://localhost:8480/auth) with *admin* user.
+
+> **_NOTE:_** This example uses keycloak authentication to enable security only in the consoles not in runtime.
+
+### Show active Hiring process instance at Kogito Management Console
+
+To access the Kogito Management Console just open your browser and navigate to ``http://localhost:8280``. You'll be redirected to the *Keycloak* log in page.
+
+<p align="center">
+ <img width=75% src="docs/images/keycloak-login.png">
+</p>
+
+Once there, log in using any of the users specified in the [Using Keycloak as Authentication Server](#using-keycloak-as-authentication-server)
+
+<p align="center">
+ <img width=75% src="docs/images/mc_list.png">
+</p>
+
+> **_NOTE:_** For more information about how to work with Kogito Management Console, please refer to the [Kogito Documentation](https://docs.kogito.kie.org/latest/html_single/#con-management-console_kogito-developing-process-services) page.
+
+Check the process instance details to see where is the execution path
+
+<p align="center">
+ <img width=75% src="docs/images/MC_details_1.png">
+</p>
+
+We have configured the timer to avoid the *HR interview* after reasonable time (3min, just for testing purpose)
+
+Let's give the app more than 3min to see the timer in action.
+
+Check the process instance details
+
+<p align="center">
+ <img width=75% src="docs/images/MC_details_2_IT_executed_job.png">
Review Comment:
broken image, probably cuz of the capital letters on the filename.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "kie-ci3 (via GitHub)" <gi...@apache.org>.
kie-ci3 commented on PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#issuecomment-1825976891
**PR job** `#1` was: **UNSTABLE**
Possible explanation: This should be test failures
<details>
<summary><b>Reproducer</b></summary>
build-chain build full_downstream -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-kogito-pipelines/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-kogito-examples -u https://github.com/apache/incubator-kie-kogito-examples/pull/1833 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution
</details>
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/1/display/redirect
**Test results:**
- PASSED: 376
- FAILED: 2
Those are the test failures:
<details>
<summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/1/testReport/org.kie.kogito.hr/HiringProcessIT/testCandidateNotMeetingRequirements/">org.kie.kogito.hr.HiringProcessIT.testCandidateNotMeetingRequirements</a></summary>
expected: <1> but was: <5>
</details>
<details>
<summary><a href="https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest_jobs/job/kogito-examples-pr/job/PR-1833/1/testReport/org.kie.kogito.hr/HiringProcessIT/PR_check___Build_projects___testApprovalProcess/">PR check / Build projects / org.kie.kogito.hr.HiringProcessIT.testApprovalProcess</a></summary>
expected: <1> but was: <5>
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1466214908
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/README.md:
##########
@@ -0,0 +1,321 @@
+# Process user tasks with timer with persistence addon : Hiring
+
+## Description
+
+This example showcases a basic implementation of the **Hiring** process that drives a *Candidate* through different
+interviews until it gets hired.
+
+This quickstart project shows a simple example user task orchestration including the use of DMN decisions to
+generate the candidate offer and timers to skip Human tasks.
+
+This example also takes advantage of the `kogito-addons-quarkus-data-index-persistence-postgresql` that enables the
+*Kogito runtime* directly persist into the *Data-Index* Database simplifying the communication of both services by removing
+the need of events (Kafka/HTTP) between them.
+
+## The Java models
+
+The **Hiring** process uses two POJOs to handle the process data, both of them can be found in the *org.kie.kogito.hr* package.
+
+The `CandidateData` POJO is the input of the process. It represents the person that wants to get the job.
+
+```java
+public class CandidateData {
+
+ private String name; // Name of the candidate
+ private String lastName; // Last name of the candidate
+ private String email; // Email of the candidate
+ private Integer experience; // Years of experience
+ private List<String> skills; // List of technical skills
+
+ // Constructors, setters, getters...
+}
+```
+
+The `Offer` POJO is the output of the process and represents the job offer that will be sent to the candidate.
+It will be automatically calculated during the process execution depending on the candidate years of experience & skills.
+```java
+public class Offer {
+
+ private String category; // Job category based on the candidate experience
+ private Integer salary; // Salary based on the candidate experience and skills
+
+ // Constructors, setters, getters...
+}
+```
+## The *New Hiring Offer* DMN
+This example makes use of the *New Hiring Offer* DMN to generate a base offer for the `Candidate`. The DMN looks like this:
+
+In this simple DMN we have an `Offer` *Decision*, that will generate the candidate offer, which
+has a requirement of a `CandidateData` *Input Data*.
+
+<p align="center">
+ <img width=55% src="docs/images/new_hiring_offer_dmn.png">
+</p>
+
+The DMN defines the following data types (`tCandidateData` & `tOffer` ) matching the POJOs defined in the project
+(`CandidateData.java` & `Offer.java`):
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_types.png">
+</p>
+
+As expected, `CandidateData` *Input Data* & `Offer` *Decision* have a `tCandidateData` data
+
+The `Offer` decision uses the following *Boxed Expression* to generate the `tOffer`:
+<p align="center">
+ <img width=75% src="docs/images/new_hiring_offer_dmn_decission.png">
+</p>
+
+## The Hiring Process
+### Process variables
+
+The process handles the following _Variables_:
+
+| Variable | Type | Tags | Description |
+|--------------------|-----------------------------------|--------------|---------------------------------------------------|
+| **candidateData** | `org.kie.kogito.hr.CandidateData` | **input** | The candidate data |
+| **offer** | `org.kie.kogito.hr.Offer` | **output** | The generated candidate offer |
+| **hr_approval** | `Boolean` | **internal** | Determines that HR department approves the hiring |
+| **it_approval** | `Boolean` | **internal** | Determines that IT department approves the hiring |
+
+### The BPMN Process
+
+<p align="center">
+ <img width=75% src="docs/images/hiring_diagram.png">
+</p>
+
+The process starts receiving the `CandidateData` as an input and storing it into the `candidateData` variable, and if the
+candidate meets two minimal requirements, the process will continue and reach the **Generate base offer**, otherwise the
+candidate application will be denied and the process will complete without sending the `offer` to the candidate.
+
+The **Generate base offer** is a *Business Rule Task* that will use the *New Hiring Offer* decision defined in the
+`NewHiringOffer.dmn` to generate the an `Offer` based on the candidate experience and skills. The task takes the `candidateData`
+as an input and will produce an instance of `org.kie.kogito.hr.Offer` that will be stored in the `offer` variable.
+
+<p align="center">
+ <img width=75% src="docs/images/generate_offer_assignments.png">
+</p>
+
+After the `offer` has been generated, the process will jump into the **HR Interview** *Human Task*, where the candidate we'll
+be interviewed by the *HR* department. The task takes the `candidateData` and `offer` as inputs and as an output will produce
+the `hr_approve` boolean and an updated `offer`.
+
+<p align="center">
+ <img width=75% src="docs/images/hr_interview_assignments.png">
+</p>
+
+The **HR Interview** *Human Task* also has a *Boundary Timer Event* that will prevent the task to delay and will cancel the
+task after certain time (for example purpose just 3 minutes). This *Boundary Timer Event* will schedule a Job in the Jobs Service
+that when trigger will notify the *Kogito Runtime* to cancel the task and deny the application.
+
+If **HR Interview** successfully completed, the process will jump into the **IT Interview** *Human Task*. Again the candidate
+we'll have a second interview with the *IT* department. Again, this task will take the `candidateData` and `offer` as inputs
+but as an output will produce the `it_approve` boolean.
+
+<p align="center">
+ <img width=75% src="docs/images/it_interview_assignments.png">
+</p>
+
+Once both tasks are completed, if the candidate got the approvals from *HR* & *IT* (both `hr_interview` & `hr_interview` being true)
+the process will jump into the **Send Offer to Candidate** *Script Task* that will notify the candidate about the offer
+and the process will end.
+
+> **NOTE:** for simplicity, all the *Human Tasks* in this example are assigned to the *jdoe* user present in the keycloak configuration
+
+## Running the example
+### Prerequisites
+
+* Java 11+ installed
+* Environment variable JAVA_HOME set accordingly
+* Maven 3.8.6+ installed
+* Docker and Docker Compose to run the required example infrastructure.
+
+And when using native image compilation, you will also need:
+- GraalVM 20.3+ installed
+- Environment variable GRAALVM_HOME set accordingly
+- GraalVM native image needs as well native-image extension: https://www.graalvm.org/reference-manual/native-image/
+- Note that GraalVM native image compilation typically requires other packages (glibc-devel, zlib-devel and gcc) to be installed too, please refer to GraalVM installation documentation for more details.
+
+### Infrastructure Services
+
+This quickstart provides a docker compose template that starts all the required services. This setup ensures that all services are connected with a default configuration.
+
+- PostgreSQL: 5432
+- Kafka: 9092
+- Data Index: 8180
+- Jobs Service: 8580
+- Management Console: 8280
+- Task Console: 8380
+- Keycloak: 8480
+- PgAdmin: 8055
+- Kogito Example Service: 8080
+
+To help bootstraping the Infrastructure Services, the example provides the `startServices.sh` script inside the *docker-compose*
+folder.
+
+> **_NOTE:_** starting the Infrastructure Services, please consider running a ```mvn clean package -Pcontainer```
+> command on the project root before running the ```startServices.sh``` script for the first time or any time you modify the project.
+
+### Building & Running the example
+
+To build the example, on a Terminal, run the following command:
+```shell
+mvn clean package -Pcontainer
+```
+This will build the example quarkus application and create a Docker image that will be started in the
+
+To execute the full example (including consoles), open a Terminal and run the following command inside the `docker-compose` folder:
+
+```shell
+sh startServices.sh
+```
+
+If you want to start only the example and the minimal Infrastructure Services (PostgreSQL, Data-Index and Jobs Service),
+you can run the same `startServices.sh` script but passing the `example` argument
+
+```shell
+sh startServices.sh example
+```
+
+### Running the example in Development mode
+
+To run the example in Development mode, just run the following command in a Terminal:
+
+```shell
+mvn clean package quarkus:dev -Pdevelopment
+```
+
+The Development Mode will embed all the needed Infrastructure Services (PostgreSQL, Data-Index & Jobs Service) and wont
+require any extra step.
+
+The `development` profile includes the **Runtime Tools Quarkus Extension** that exposes a new section in the **Quarkus Dev-UI**
+unifying the **Management Console** & **Task Console** functionalities. **Quarkus Dev-UI** is available at http://localhost:8080/q/dev
+
+> **_NOTE:_** For more information about how to work with Kogito Runtime Tools Quarkus Extension, please refer to the [Kogito Documentation](https://docs.kogito.kie.org/latest/html_single/#con-runtime-tools-dev-ui_kogito-developing-process-services) page.
+
+### Starting an instance of the Hiring Process
+
+Once the service is up and running you can make use of the **Hiring** application by a sending request to `http://localhost:8080/hiring`.
+
+Sending the following valid `CandidateData` will start a process instance that will land into the *HR Interview* task:
+
+```json
+{
+ "candidateData": {
+ "name": "Jon",
+ "lastName": "Snow",
+ "email": "jon@snow.org",
+ "experience": 5,
+ "skills": [
+ "Java", "Kogito", "Fencing"
+ ]
+ }
+}
+```
+
+In a Terminal you can execute this curl command to start a **Hiring** process:
+```bash
+curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST http://localhost:8080/hiring -d '{"candidateData": { "name": "Jon", "lastName": "Snow", "email": "jon@snow.org", "experience": 5, "skills": ["Java", "Kogito", "Fencing"]}}'
+```
+
+If everything went well you may get a response like:
+```json
+{
+ "id": "628e679f-4deb-4abc-9f28-668914c64ef9",
+ "offer": {
+ "category": "Senior Software Engineer",
+ "salary": 40450
+ }
+}
+```
+
+In the server log You may find a trace like:
+```text
+New Hiring has been created for candidate: Jon Snow
+###################################
+Generated offer for candidate: Jon Snow
+Job Category: Senior Software Engineer
+Base salary: 40450
+###################################
+```
+
+Use the following `CandidateData` that don't match the minimal candidate requirements, to start a process that will automatically end:
+```json
+{
+ "candidateData": {
+ "name": "Jon",
+ "lastName": "Snow",
+ "email": "jon@snow.org",
+ "experience": 0,
+ "skills": []
+ }
+}
+```
+
+In a Terminal you can execute this curl command to start a **Hiring** process:
+```bash
+curl -H "Content-Type: application/json" -H "Accept: application/json" -X POST http://localhost:8080/hiring -d '{"candidateData": { "name": "Jon", "lastName": "Snow", "email": "jon@snow.org", "experience": 0, "skills": []}}'
+```
+
+If everything went well you may get a response like:
+```json
+{
+ "id": "3659601a-bb59-458d-859e-7892621ad5b7",
+ "offer": null
+}
+```
+
+In the server log You may find a trace like:
+```text
+New Hiring has been created for candidate: Jon Snow
+###################################
+Candidate Jon Snow don't meet the requirements for the position but we'll keep it on records for the future!
+###################################
+```
+
+### Using Keycloak as Authentication Server
+
+In this Quickstart we'll be using [Keycloak](https://www.keycloak.org/) as *Authentication Server*. It will be started as a part of the project *Infrastructure Services*, you can check the configuration on the project [docker-compose.yml](docker-compose/docker-compose.yml) in [docker-compose](docker-compose) folder.
+
+It will install the *Kogito Realm* that comes with a predefined set of users:
+
+| Login | Password | Roles |
+| ------------- | ---------- | ------------------- |
+| admin | admin | *admin*, *managers* |
+| alice | alice | *user* |
+| jdoe | jdoe | *managers* |
+
+Once Keycloak is started, you should be able to access your *Keycloak Server* at [localhost:8480/auth](http://localhost:8480/auth) with *admin* user.
+
+> **_NOTE:_** This example uses keycloak authentication to enable security only in the consoles not in runtime.
+
+### Show active Hiring process instance at Kogito Management Console
+
+To access the Kogito Management Console just open your browser and navigate to ``http://localhost:8280``. You'll be redirected to the *Keycloak* log in page.
+
+<p align="center">
+ <img width=75% src="docs/images/keycloak-login.png">
+</p>
+
+Once there, log in using any of the users specified in the [Using Keycloak as Authentication Server](#using-keycloak-as-authentication-server)
+
+<p align="center">
+ <img width=75% src="docs/images/mc_list.png">
+</p>
+
+> **_NOTE:_** For more information about how to work with Kogito Management Console, please refer to the [Kogito Documentation](https://docs.kogito.kie.org/latest/html_single/#con-management-console_kogito-developing-process-services) page.
+
+Check the process instance details to see where is the execution path
+
+<p align="center">
+ <img width=75% src="docs/images/MC_details_1.png">
+</p>
+
+We have configured the timer to avoid the *HR interview* after reasonable time (3min, just for testing purpose)
+
+Let's give the app more than 3min to see the timer in action.
+
+Check the process instance details
+
+<p align="center">
+ <img width=75% src="docs/images/MC_details_2_IT_executed_job.png">
Review Comment:
@kmacedovarela thank you for your review, I haven't finished with the readme yet.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan merged PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1471634311
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/docker-compose.yml:
##########
@@ -0,0 +1,142 @@
+version: '3'
+
+services:
+ postgres:
+ container_name: postgres
+ image: postgres:13.4-alpine3.14
+ profiles: [ "infra", "example", "full" ]
+ ports:
+ - "5432:5432"
+ volumes:
+ - ./sql:/docker-entrypoint-initdb.d:Z
+ healthcheck:
+ test: [ "CMD", "pg_isready", "-q", "-d", "kogito", "-U", "kogito-user" ]
+ timeout: 45s
+ interval: 10s
+ retries: 50
+ environment:
+ POSTGRES_USER: postgres
+ POSTGRES_PASSWORD: postgres
+
+ pgadmin:
+ container_name: pgadmin
+ image: dpage/pgadmin4:7.8
Review Comment:
Upgraded to `dpage/pgadmin4:8.2` (and also adding default configuration)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1470937435
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/src/main/resources/application.properties:
##########
@@ -0,0 +1,52 @@
+# Packaging
+#quarkus.package.type=fast-jar
+
+#https://quarkus.io/guides/openapi-swaggerui
+quarkus.http.cors=true
+quarkus.smallrye-openapi.path=/docs/openapi.json
+quarkus.swagger-ui.always-include=true
+quarkus.kogito.data-index.graphql.ui.always-include=true
+quarkus.http.test-port=0
+
+# Kogito-service
+kogito.service.url=http://localhost:8080
+
+#Job-service
+kogito.jobs-service.url=http://localhost:8080
+
+# to be reachable from the container running job-service
+kogito.dataindex.http.url=http://localhost:8180
+kogito.dataindex.ws.url=ws://localhost:8180
+
+# run create tables scripts
+quarkus.flyway.migrate-at-start=true
+quarkus.flyway.baseline-on-migrate=true
+quarkus.flyway.locations=classpath:/db/migration,classpath:/db/jobs-service
+quarkus.flyway.table=FLYWAY_RUNTIME_SERVICE
+quarkus.hibernate-orm.database.generation=update
+
+kogito.persistence.type=jdbc
+quarkus.datasource.db-kind=postgresql
+%prod.quarkus.datasource.username=kogito-user
+%prod.quarkus.datasource.password=kogito-pass
+%prod.quarkus.datasource.jdbc.url=${QUARKUS_DATASOURCE_JDBC_URL:jdbc:postgresql://localhost:5432/kogito}
+%prod.quarkus.datasource.reactive.url=${QUARKUS_DATASOURCE_REACTIVE_URL:postgresql://localhost:5432/kogito}
+
+quarkus.native.native-image-xmx=8g
+
+# profile to pack this example into a container, to use it execute activate the maven container profile, -Pcontainer
+%container.quarkus.container-image.build=true
+%container.quarkus.container-image.push=false
+%container.quarkus.container-image.group=${USER}
+%container.quarkus.container-image.registry=dev.local
+%container.quarkus.container-image.tag=1.0-SNAPSHOT
+%container.quarkus.jib.jvm-entrypoint=/home/kogito/kogito-app-launch.sh
+%container.quarkus.jib.base-jvm-image=quay.io/kiegroup/kogito-runtime-jvm-nightly:latest
Review Comment:
yea, we still don't have the `quay.io/kiegroup/kogito-runtime-jvm` image updated with the latest chnages, I'd keep this like this and do the upgrade after we have the image publisehd.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] incubator-kie-issues#723: Adding `process-usertasks-timer-data-index-persistence-addon-quarkus` showcasing the `kogito-addons-quarkus-data-index-persistence-postgresql` including Jobs Service [incubator-kie-kogito-examples]
Posted by "pefernan (via GitHub)" <gi...@apache.org>.
pefernan commented on code in PR #1833:
URL: https://github.com/apache/incubator-kie-kogito-examples/pull/1833#discussion_r1471045056
##########
kogito-quarkus-examples/process-usertasks-timer-data-index-persistence-addon-quarkus/docker-compose/README.md:
##########
@@ -0,0 +1,57 @@
+# Kogito and Infrastructure services
+
+To allow a quick setup of all services required to run this demo, we provide a docker compose template that starts the following services:
+- Postgresql
+- PgAdmin
+- Kogito Data Index
+- Kogito Example Service (Only available if the example has been compiled using the `container` mvn profile eg: ```mvn cleanp package -Dcontainer```)
+- Kogito Management Console
+- Kogito Task Console
+- Keycloak
Review Comment:
+1 Will add `data-audit` as colocated service, so I'll mention it in the main `README.md`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org