This image contains a ready-to-run default installation of the WSO2 Business Activity Monitor (BAM) 2.5.0 with Oracle JRE 1.7 based on CentOS.
Both, JRE 1.7 and BAM 2.5.0, are installed in
/opt and the BAM settings are left unchanged. You can run the image via ...
docker run -d -t -i -p 9443:9443 --name bam dfch/wso2bam-2.5.0
... and attach to it later via:
docker attach bam
You can later detach from the console via:
So you can reach the management page at
https://localhost:9443 via the well-known credentials
Shutting down the BAM via the carbon management page will also stop the container. Performing a restart of the service will not stop the container.
For more information see Creating a docker image for WSO2 Complex Event Processor.
@raphabot At at the end of the article Creating a docker image for WSO2 Complex Event Processor you will see a link pointing to the Github repo https://github.com/dfch/wso2 that holds the Dockerfiles for the various WSO images.
@dfch Is it possible to make the Dockerfile available? One of the beauties of Docker is that we can see everything that was made to config the container.