How does one set up jbpm + kie-server for using jbpm via a rest api?

[NullVoxPopuli]

I made a post here about what I'm doing: https://github.com/jboss-dockerfiles/jbpm/issues/35
I'll just copy it here

all I'm wanting to do is have the rest api access jbpm... right now they seem totally separate, and I haven't seen how they are supposed to connect up to each other.

I was reading: https://github.com/jboss-dockerfiles/jbpm/issues/29

and I was able to get the two showcase containers running.

docker run -p 8080:8080 -p 8001:8001 -d -e JAVA_OPTS="-Djava.net.preferIPv4Stack=true" --name jbpm-workbench jboss/jbpm-workbench-showcase:latest


docker run -p 8180:8080 -d --name kie-server -e JAVA_OPTS="-Djava.net.preferIPv4Stack=true" --link jbpm-workbench:kie_wb jboss/kie-server-showcase:latest

at http://localhost:8080/jbpm_console, I create a workflow, and deploy it and make sure the start checkbox is checked on deploy.

However, when I visit http://localhost:8180/kie-server/services/rest/server/containers

<response type="SUCCESS" msg="List of created containers">
  <kie-containers/>
</response>

My deployed project doesn't show up?

does kie not know how to communicate with jbpm?

docker logs <kie-server container id>

shows a toooooon of exceptions:

13:27:14,414 ERROR [org.kie.server.remote.rest.jbpm.QueryDataResource] (default task-10) Unexpected error during processing Can't get metadata on specified data set: jbpmProcessInstances: org.dashbuilder.dataset.exception.DataSetLookupException: Can't get metadata on specified data set: jbpmProcessInstances
...
Caused by: org.h2.jdbc.JdbcSQLException: Column "LOG.SLA_DUE_DATE" not found; SQL statement:
...


14:17:18,246 ERROR [io.undertow.request] (default task-11) UT005023: Exception handling request to /kie-server/services/rest/server/containers/aoeu_1.0.2: org.jboss.resteasy.spi.UnhandledException: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.jsontype.impl.AsWrapperTypeDeserializer.<init>(Lcom/fasterxml/jackson/databind/JavaType;Lcom/fasterxml/jackson/databind/jsontype/TypeIdResolver;Ljava/lang/String;ZLjava/lang/Class;)
...
Caused by: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.jsontype.impl.AsWrapperTypeDeserializer.<init>(Lcom/fasterxml/jackson/databind/JavaType;Lcom/fasterxml/jackson/databind/jsontype/TypeIdResolver;Ljava/lang/String;ZLjava/lang/Class;)

Is there a guide anywhere to correctly get things working?

I feel a lot of the documentation for kie and jbpm assumes some knowledge of how kie and friends are supposed to interact with each other. I don't know much, but all I want is to have a rest api into jbpm. 

Is there a volume that needs to be shared between the two docker containers?

I also have this docker-compose setup:

 

version: '3.4'
services:
  jbpm:
    image: jboss/jbpm-workbench-showcase
    ports:
      - '8080:8080'
      - '8081:8081'
      - '9990:9990'
    networks:
      - backoffice
    volumes:
      - type: bind
        source: ./deployment/local/config/niogit
        target: /opt/jboss/wildfly/bin/.niogit


  kie-server:
    image: jboss/kie-server-showcase
    ports:
      - '8180:8080'
    links:
      - jbpm:kie_wb
    networks:
      - backoffice




networks:
  internet:
  backoffice:

If I run via docker-compose the logs show no exceptions, or the logs aren't output to the default log / output of docker-compose 

Thanks!

At the time of writing this:  

jboss/jbpm-workbench-showcase is 7.7.0.Final

jboss/kie-server-showcase is

7.7.0.Final-3

$ docker --version

Docker version 18.03.0-ce, build 0520e24

$ lsb_release -rdc

Description: Ubuntu 16.04.4 LTS

Release: 16.04

Codename: xenial

$ uname -a

Linux macbuntu 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[Maciej Swiderski]

There seems to be an issue with kie server showcase docker image as apparently it is using 7.6.0.Final while it should be using 7.7.0.

We’re working on this and will provide update here as soon as we have this resolved. 

Thanks for reporting this!

Maciej

--
You received this message because you are subscribed to the Google Groups "jBPM Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-developme...@googlegroups.com.
To post to this group, send email to jbpm-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-development/b9933ffc-e958-468a-937a-3a0b7b132246%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[L. Preston Sego III]

Is the version mismatch the issue?

How is it that kie can communicate with jbpm across containers?

(Is it networking? Shared folders?)

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-development/F256A887-1C5E-4C1E-86D2-D83C9CE40BB4%40gmail.com.

[Maciej Swiderski]

On 18 Apr 2018, at 11:50, L. Preston Sego III <lt....@gmail.com> wrote:

Is the version mismatch the issue?

it seems like it, wrong version was pulled into the container, but we are investigating it as we speak

How is it that kie can communicate with jbpm across containers?

(Is it networking? Shared folders?)

it’s networking

Maciej

[NullVoxPopuli]

I specified the versions of the images in the docker-compose file.

I'm still not seeing any containers at:

http://localhost:8180/kie-server/services/rest/server/containers

what am I doing wrong?
none of the jbpm stuff is visible via the api?

[Maciej Swiderski]

you need to deploy your kjars first then they will show up there

Maciej

On 18 Apr 2018, at 15:04, NullVoxPopuli <lt....@gmail.com> wrote:

I specified the versions of the images in the docker-compose file.

I'm still not seeing any containers at:

http://localhost:8180/kie-server/services/rest/server/containers

what am I doing wrong?

none of the jbpm stuff is visible via the api?

--
You received this message because you are subscribed to the Google Groups "jBPM Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-developme...@googlegroups.com.
To post to this group, send email to jbpm-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-development/89b26ed0-c424-48a9-8fe2-4e1ed6b748ea%40googlegroups.com.

[NullVoxPopuli]

that's just this button yeah?

the log only says:

jbpm_1        | 13:23:02,218 INFO  [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (default task-18) KieModule was added: MemoryKieModule[releaseId=org.sil:hello-world:0.0.4]

but then refreshing http://localhost:8180/kie-server/services/rest/server/containers shows nothing still, just

[NullVoxPopuli]

I found this: https://groups.google.com/forum/#!topic/jbpm-setup/o0Lq5P7MNtg

I think that means that I need both docker containers to share the same m2 repo.

I'll configure docker-compose to do that, and see what happens.

[NullVoxPopuli]

well, I haven't found any difference. I can confirm the .m2 directory is shared between jbpm and kie-server, /opt/jboss/.m2
but there are still no containers from the rest api

[jboss@af5210f7df72 0.0.4]$ pwd
/opt/jboss/.m2/repository/org/sil/hello-world/0.0.4
[jboss@af5210f7df72 0.0.4]$ ls
_remote.repositories  hello-world-0.0.4.jar  hello-world-0.0.4.pom

[NullVoxPopuli]

Updated Docker-Compose.
Still don't see any containers, after deploying.

version: '3.4'
services:
  jbpm:
    build:
      context: ./source/workflow-engine/jbpm-workbench
      dockerfile: Dockerfile

    ports:
      - '8080:8080'
      - '8081:8081'
      - '9990:9990'
    networks:
      - backoffice
    volumes:

      - type: volume
        source: jbpm-m2
        target: /opt/jboss/.m2
      - type: bind
        source: ./deployment/local/config/niogit
        target: /opt/jboss/wildfly/bin/.niogit


  kie-server:
    build:
      context: ./source/workflow-engine/kie-server
      dockerfile: Dockerfile

    ports:
      - '8180:8080'
    links:
      - jbpm:kie_wb
    networks:
      -

backoffice
    volumes:
      - type: volume
        source: jbpm-m2
        target: /opt/jboss/.m2


volumes:
  jbpm-m2:


networks:
  internet:
  backoffice: