Hi all, Here are my suggestions and explanations regarding the $subject. When deploying WSO2 ESB in Cloud Foundry, the problem lies in the fact that no buildpacks detect it.
When DEA gets a request from the Cloud Controller to stage an app, it places the code to a container and starts to look for a suitable buildpack. It calls the ‘detect’ script in every buildpack and chooses the first to return 0. The buildpacks are Git repositories which contain three shell scripts under the “bin” directory. The functional part of a buildpack consists of these three scripts: detect, compile, and release. *detect - *Detect if this buildpack applies to this application *compile* - Build the runtime used to execute the application *release* - Control how the application should be executed In case of WSO2 ESB, the Java Buildpack expects us to upload `cf push` either a *.jar file or a *.war file. So, I have come up with following suggestions. 1) Change the code so that the ESB is just a *.war file that can be dropped into a Tomcat server 2) Develop a buildpack that will execute the sh files 3) Customize the Java buildpack to detect the products 4) Create a Docker container out of the ESB and push up that Docker container (With Diego) Do you have any better options? Please let me know if you have deployed any WSO2 products in Cloud Foundry. Any suggestions are highly appreciated. Best regards, Nanduni. *Nanduni Nimalsiri* Software Engineering Intern, WSO2 Inc. (http://wso2.com) email : [email protected] blog : http://nanduni.blogspot.com/ mobile : +94714114256
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
