Dockerfile links4.4.0 (Dockerfile)4.4.0-alpine (Dockerfile)4.4.0-centos (Dockerfile)4.3.0, latest (Dockerfile)4.3.0-alpine (Dockerfile)4.3.0-centos (Dockerfile)Where to get help:
Docker Community Forums, Docker Community Slack, Stack Overflow or mail to WSO2 Developer mailing list
Where to file issues:
Product specific issues at WSO2 Stream Processor product repository and Docker resource usage issues at product Docker resource repository
Maintained by:
WSO2 Inc.
Supported Docker versions:
Docker v17.09.0 or above
WSO2 Stream Processor is a Streaming SQL based, high performant, lightweight, open source stream processing platform, facilitating the creation of real-time, intelligent, actionable business insights, and data products for digital businesses. It allows you to collect events via multiple transports and in multiple formats. It uses streaming SQL to process streams, detect complex events, calculate time-based aggregations, and make predictions using machine learning models.
This profile runs the distributed Siddhi applications in a production environment when WSO2 SP is set up as a fully distributed deployment. For more information, see Fully Distributed Deployment.
The following command starts a Linux Ubuntu-based Manager profile Docker image.
$ docker run -it -p 9543:9543 --name manager wso2/wso2sp-manager:4.3.0
Here, port 9543 has been mapped to the corresponding Docker host (host machine on top of which containers are spawned) port.
Assuming you have started a Docker container instance of Manager profile as instructed in the previous section
Start an Manager profile instance,
$ docker logs manager
$ docker exec -it manager bash
To start a Docker container instance of the Manager profile in debug mode (assuming 5005 to be the remote debugging port), use the following command:
$ docker run -it -p 9543:9543 -p 5005:5005 --name another-manager wso2/wso2sp-manager:4.3.0 -debug 5005
Configurations would lie on the Docker host machine and they can be volume mounted to the container. All the configurations related to Manager profile are in deployment.yaml file. Each component has a corresponding heading in the YAML file that covers most of the component-specific configuration like carbon configuration parameters, data source configuration, cluster configuration, etc. As an example, the steps required to change the HTTPS Netty Transport port using deployment.yaml is as follows:
In Manager profile product distribution, deployment.yaml configuration file can be found at {DISTRIBUTION_HOME}/conf/manager/deployment.yaml.
Copy the file to some suitable location of the host machine, referred to as {SOURCE_CONFIGS}/deployment.yaml and
increase the offset value under wso2.transport.http.listenerConfigurations["msf4j-https"].port -> to 9545.
other users for {SOURCE_CONFIGS}/deployment.yaml.$ chmod o+r {SOURCE_CONFIGS}/deployment.yaml
$ docker run -p 9545:9545 --volume {SOURCE_CONFIGS}/deployment.yaml:{TARGET_CONFIGS}/deployment.yaml wso2/wso2sp-manager:4.3.0
Here, {TARGET_CONFIGS} refers to /home/wso2carbon/wso2sp-4.3.0/conf/manager folder of the container.
Multiple product profile Docker images based on different base operating systems are available.
wso2sp-manager:{version}Ubuntu 18.04 LTS based Docker image with AdoptOpenJDK 8 pre-installed has been used as the base Docker image.
Manager profile of WSO2 Stream Processor has been installed on top of this Docker image.
wso2sp-manager:{version}-alpineAlpine based Docker image with AdoptOpenJDK 8 pre-installed has been used as the base Docker image.
Manager profile of WSO2 Stream Processor has been installed on top of this Docker image.
wso2sp-manager:{version}-centosCentOS 7 based Docker image has been used. AdoptOpenJDK 8 and Manager profile of WSO2 Stream Processor have been installed on top of this Docker image.
View license information for the software contained in this image.
As with all Docker images, these are likely to contain other software which may be under other licenses (such as Bash, etc. from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
Content type
Image
Digest
Size
332.4 MB
Last updated
over 7 years ago
docker pull wso2/wso2sp-manager