Closed wiktorn closed 6 years ago
I use following docker-compose.yml
to test this:
version: '3'
services:
jbpm-workbench:
image: jboss/jbpm-workbench-showcase:7.2.0.Final
restart: always
environment:
JAVA_OPTS: "-Xms256m -Xmx512m -Djava.net.preferIPv4Stack=true"
ports:
- "8080:8080"
- "8001:8001"
kie-server:
#image: jboss/kie-server-showcase:7.2.0.Final
image: kie-local
environment:
KIE_WB_PORT_8001_TCP: "tcp://kiewb:8001"
KIE_WB_PORT_8001_TCP_ADDR: "kiewb"
KIE_WB_PORT_8080_TCP: "tcp://kiewb:8080"
KIE_WB_PORT_8080_TCP_ADDR: "kiewb"
KIE_WB_ENV_KIE_CONTEXT_PATH: "jbpm-console"
KIE_WB_ENV_KIE_SERVER_PROFILE: "standalone-full-jbpm"
links:
- jbpm-workbench:kiewb
Without my changes I'll get failures when getting process definition or process instances.
Maybe this docker-compose.yml is worth including in jbpm-workbench-showcase Readme maybe?
@wiktorn thanks for the feedback! @mbiarnes can you take a look at this PR when you have a chance please?
The goal of this changes is to make kie-server-showcase ready to be used by jbpm-workbench-showcase.
As jbpm-console uses it's users to authenticate against kie-server when getting process definitions and list I synchronized the list of users with jbpm-workbench-showcase.
This also fixes missing protocol in users & roles specification.