I've learned that jbpm and kie-server need to share an .m2 directory for jbpm to deploy processes to.
Here is my docker-compose
version: '3.4' services: jbpm: build: context: jboss/jbpm-workbench-showcase:7.7.0.Final 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: jboss/kie-server-showcase:7.7.0.Final-4 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:
I can confirm that when I click deploy in the jbpm workbench, that the jar is placed in the shared m2 directory
(I can see it in both the jbpm container, and the kie-server container).
However, I still can't get the containers endpoint on the kie-server to show anything other than an empty list.
http://localhost:8180/kie-server/services/rest/server/containers
how do I get kie-server to pick up my jbpm process?
also, my kie-server doesn't have any UI... some of the docs implies that it should? idk. I can't find the docs I was looking at earlier, but there were also missing screenshots..
This is all very complicated. :-\
On 18 Apr 2018, at 17:25, NullVoxPopuli <lt....@gmail.com> wrote:I posted an issue here: https://github.com/jboss-dockerfiles/jbpm/issues/35#issuecomment-382416578
maybe not the best place, but this forum seems like the right place :-)I've learned that jbpm and kie-server need to share an .m2 directory for jbpm to deploy processes to.
--
You received this message because you are subscribed to the Google Groups "Drools Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drools-setup...@googlegroups.com.
To post to this group, send email to drools...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/f7d03003-3b66-4e24-9802-adec14c7421a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On 19 Apr 2018, at 00:23, NullVoxPopuli <lt....@gmail.com> wrote:how do I generate the kjars?
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/f04d85fa-157b-4a7e-ac4c-529f49803b5a%40googlegroups.com.
docker run -p 8080:8080 -p 8001:8001 --mount type=bind,source=$PWD/deployment/local/config/niogit,target=/opt/jboss/wildfly/bin/.niogit --name jbpm jboss/jbpm-workbench-showcase:7.7.0.Final
docker run -p 8180:8080 -d --link jbpm:kie-wb jboss/kie-server-showcase:7.7.0.Final-4I can't seem to get this to work in docker-compose though.
here is my compose config:
version: '3.4'
services:
jbpm:
image: jboss/jbpm-workbench-showcase:7.7.0.Final
ports:
# Workbench
- '8080:8080'
# Git
- '8001:8001'
networks:
- backoffice
volumes:
- type: bind
source: ./deployment/local/config/niogit
target: /opt/jboss/wildfly/bin/.niogit
kie-server:
image: jboss/kie-server-showcase:7.7.0.Final-4
ports:
# Rest API Server
- '8180:8080'
links:
- jbpm:kie-wb
networks:
- backoffice
Are there environment variables I can use to that tell kie-server where the jbpm workbench is?There should be no difference between the manually run docker commands and the docker-compose config