KIE Community

Please refer to Appendix C for extending this image.

Refer to Appendix A for more information about IP address and port bindings.

Drools Workbench Showcase

See it in Docker Hub

KIE Execution server

More information for the KIE Execution Server can be found at the official documentation.

More information for the KIE Execution Server can be found at the official documentation. 

Tip: This image inherits from the KIE Execution Server one and adds custom configuration for WildFly security subsystem (security realms).

1. Pull the image:

   docker pull jboss/kie-server-showcase:6.2.0.Final

2. Run the image:

   docker run -p 8080:8080 -d –name kie-server-showcase jboss/kie-server-showcase:6.2.0.Final

3. The server is located at:

   http://localhost:8080/kie-server # Linux users
   http://<boot2docker_ip>:8080/kie-server # Windows users

    The REST API service is located at:
  
 http://localhost:8080/kie-server/services/rest/server # Linux  
 http://<boot2docker_ip>:8080/kie-server/services/rest/server # Win  

Refer to Appendix A for more information about IP address and port bindings.

You can use kie-server/kie-server for default logging – Refer to Appendix B for default users and roles included
  

jBPM Workbench

1. Pull the image:

   docker pull jboss/jbpm-workbench-showcase:6.2.0.Final

2. Run the image:

   docker run -p 8080:8080 -d –name jbpm-wb-showcase jboss/jbpm-workbench-showcase:6.2.0.Final

3. Navigate into the workbench at:

   http://localhost:8080/jbpm-console # Linux users  
   http://<boot2docker_ip>:8080/jbpm-console # Windows users

Refer to Appendix A for more information about IP address and port bindings.

You can use admin/admin for default logging – Refer to Appendix B for default users and roles included

Appendix A – IP address and ports bindings for Docker containers

Port bindings
By default, when using any of the Drools & jBPM Docker images, the port 8080 is exposed for the use of the HTTP connector. This port is not exposed to the Docker host by default, so in order to expose it and be able to navigate through the applications please read the following instructions.

The recommended use for running containers is specifying in the docker client the -p argument as:

  docker run -p 8080:8080 -d ….

Doing this way, the docker daemon binds the internal container’s port 8080 to the Docker host machine’s port 8080. So you can navigate into the applications at:

   http://<docker_host>:8080/jbpm-console
   http://<docker_host>:8080/kie-server
   http://<docker_host>:8080/drools-wb

If your Docker host machine’s port 8080 is not available, run the containers with the -P command line argument. Docker binds the internal 8080 port to an available free exposed port in the Docker host, so in order to access the application you have to discover the bind port number.

To discover running container’s ports type the following command:

   docker ps -a

This command will output the processes and the port mappings for each running container:

CONTAINERID  IMAGE             COMMAND  CREATED STATUS PORTS                     NAMES

2a55fb....   jboss/drools-w..  ...      ...     ..     0.0.0.0:49159->8080/tcp.. drools-wb

The PORTS column shows that the internal container’s port 8080 is bound to port 49159 on the Docker host, so you can navigate into the applications at:

   http://<docker_host>:49159/jbpm-console
   http://<docker_host>:49159/kie-server
   http://<docker_host>:49159/drools-wb

Docker hostname & IP address
The Docker hostname or IP address have to be specified in order to navigate through the container’s applications.

If you are running Docker in your localhost and using Linux based OS, it defaults to localhost:

   http://localhost:8080/jbpm-console
   http://localhost:8080/kie-server
   http://localhost:8080/drools-wb

If you are running Docker on another machine or in Windows environments, where Boot2Docker is required,  you have to specify the host name (if DNS available for it) or the IP address for it:

   http://192.168.1.156:8080/jbpm-console
   http://192.168.1.156:8080/kie-server
   http://192.168.1.156:8080/drools-wb

Appendix B – Default applications users & roles

The Showcase images Drools Workbench Showcase and jBPM Workbench Showcase include default users & roles:

Drools & jBPM Workbench Showcase roles

Drools & jBPM Workbench Showcase users

For KIE Execution Server Showcase there is a single user and role:

Appendix C – Extending base images

The Base images are intended to be inherited from, for adding your custom configurations or deployments.

In order to extend the images, the Dockerfile must start with: 

    FROM jboss/drools-workbench:6.2.0.Final 

At this point, custom configurations and deployments can be added. Some notes:

• JBoss WildFly is located at the path given by $JBOSS_HOME environment variable
• $JBOSS_HOME points to /opt/jboss/wildfly/
• Applications are using the server in standalone mode:
• Configurations located at $JBOSS_HOME/standalone/configuration/
• Configuration files for the standalone-full profile are used
• Deployments are located at $JBOSS_HOME/standalone/deployments/

You can find more information at each official image page at Docker Hub: