SumedhaS, Can you deploy the above mentioned jaggery modules to dev,test and prod AS instances in cloud preview and reply to this thread.
On Sat, May 3, 2014 at 8:51 AM, Amila Maha Arachchi <[email protected]> wrote: > AFAIR we have some of the mentioned modules in the AS at the moment. We'll > check what is missing and add them. Thanks for letting us know about this. > > > On Saturday, May 3, 2014, Indika Sampath <[email protected]> wrote: > >> Hi Amila, >> >> I created my own tenant and deploy the con_api jaggery app in the App >> Cloud. Build and Deployment succeeded but I got an issue when I going to >> test it. The reason was this application used number of modules. Those are >> as below. >> >> - caramel >> - markdown >> - handlebars >> - pipe >> >> Above modules must reside in the *modules* folder of the WSO2 >> Application Server (wso2as-5.2.0/modules) or any other WSO2 server which >> support artifact deployment. Is there a way to add this external modules to >> the App cloud ? I think Application server has to be restarted once we add >> these modules. >> >> Cheers! >> >> >> >> On Fri, May 2, 2014 at 12:31 PM, Amila Maha Arachchi <[email protected]>wrote: >> >> Hi Indika, >> >> You can deploy the con_api, wso2_con_api (DB) and con_front in the app >> cloud (try with your own tenant). Then I believe you need to go the API >> Cloud and create and publish the API. >> >> >> >> >> On Fri, May 2, 2014 at 12:18 PM, Indika Sampath <[email protected]> wrote: >> >> Hi All, >> >> We are planing to move the WSO2 Con application back-end application to >> the WSO2 cloud as we had a discussion with Sanjiva. Following are the >> artifacts which needs to moved to the WSO2 cloud. >> >> - con_api - Jaggery application written using Jaggery pipe >> - wso2_con_api - MySQL database to store the con related data >> - con_front - Static HTML application which provide admin console to >> feed data >> >> >> The current deployment done in the WSO2 API-M. Also MySQL database >> installed in the same server. Herewith I have attached the high level >> diagram of the current deployment. Sajiva showed us number of issues in >> this deployment and suggested to move everything to the WSO2 cloud. >> >> Following are the facts we need to consider when move to the WSO2 cloud. >> >> - Currently All GET endpoints are not secured. POST/PUT/DELETE >> endpoints are secured with OAuth. We need to secure all the endpoints >> regardless of the GET/POST/PUT/DELETE. >> - The two mobile apps (android and iOS) are consume GET endpoints. >> After we secured the all endpoints there will be refactoring to the both >> mobile application. >> - In the same way con_front application has to do the modification in >> the GET endpoints. >> - We are currently use the password grant type for generate the token. >> >> >> We appreciate if there is any suggestions. >> >> Cheers! >> >> >> -- >> Indika Sampath >> Software Engineer >> WSO2 Inc. >> http://wso2.com >> >> Phone: +94 716 424 744 >> Blog: http://indikasampath.blogspot.com/ >> >> >> >> >> -- >> *Amila Maharachchi* >> Senior Technical Lead >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> >> >> >> -- >> Indika Sampath >> Software Engineer >> WSO2 Inc. >> http://wso2.com >> >> Phone: +94 716 424 744 >> Blog: <http://indikasampath.blogspot.com/> >> > > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > -- *Amila Maharachchi* Senior Technical Lead WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
