Hi Folks, Here I'm describing the overview of the carbon deployment engine (see image).
Deployer - an interface providing facility for custom deployment implementation. Artifact - represents a thing to deploy in carbon (webapp, service, dbs, etc), which will be used by the Deployer. Deployment Engine Component will consist of two main parts. 1. Scheduler 2. Repository Listener Scheduler is responsible for the scheduling the deployment task periodically. Repository Listener will do the scanning of deployer directories for artifact updates. Other than that, there will be ServiceListener which will listen to Deployer registrations/unregistrations from other components (CustomDeployers) and add/remove them to/from DeploymentEngine. Thoughts? Thanks, Kishanthan. [image: Inline image 1] -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
<<C5-DeploymentEngine.png>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
