I'm also +1 to have fully fledged profile as the default one. Because other proposed profiles might only useful for specific cases such as in a deployment. But as we promoting IoT Server as a fully capable product to work with IoT, I believe having fully fledged profile as the default one will be an added advantage.
Thanks & Regards, /charithag On Thu, Mar 24, 2016 at 2:54 PM, Ruwan Yatawara <[email protected]> wrote: > Hi Ayyoob, > > As Geeth mentioned, it makes sense to swap the two profiles and have the > fully fledged profile as the default one and the stripped down version as > the deployment friendly one. > > Thanks and Regards, > > Ruwan Yatawara > > Senior Software Engineer, > WSO2 Inc. > > email : [email protected] > mobile : +94 77 9110413 > blog : http://ruwansrants.blogspot.com/ > www: :http://wso2.com > > > On Thu, Mar 24, 2016 at 2:31 PM, Geeth Munasinghe <[email protected]> wrote: > >> Hi Ayyoob, >> >> It should be other way around where default profile has everything. When >> a user start the standalone server with "sh wso2server.sh", it should have >> everything complete their use case (Including MB and DAS features). >> >> And in real deployment user will use IoT server with only IoT related >> features. MB or DAS related features should come from those respective >> product (I mean if customer needs MB and DAS they should install separate >> DAS and MB servers). So we need to have a profile for IoT related features. >> I think by having default profile and IoT profile will do the trick for us. >> >> Thanks >> Geeth >> >> >> *G. K. S. Munasinghe* >> *Senior Software Engineer,* >> *WSO2, Inc. http://wso2.com <http://wso2.com/> * >> *lean.enterprise.middleware.* >> >> email: [email protected] >> phone:(+94) 777911226 >> >> On Thu, Mar 24, 2016 at 1:49 PM, Ayyoob Hamza <[email protected]> wrote: >> >>> [+adding prabatha] >>> >>> *Ayyoob Hamza* >>> *Software Engineer* >>> WSO2 Inc.; http://wso2.com >>> email: [email protected] cell: +94 77 1681010 <%2B94%2077%207779495> >>> >>> On Thu, Mar 24, 2016 at 1:48 PM, Ayyoob Hamza <[email protected]> wrote: >>> >>>> Hi All, >>>> In IoTS we have included MB(MQTT), DAS features within the pack to >>>> avoid initial configuration and these features are tightly bounded with IoT >>>> scenarios. However in a real deployment scenario we should not have these >>>> features installed by default but should allow the deployment to have them >>>> separately. Therefore a suggestion would be to have separate profiles to >>>> differentiate. Therefore to achieve this we can have two separate profile >>>> such as "default" and "complete" >>>> >>>> Default profile: >>>> CDMF Features, APIM Features and other related features in it. >>>> >>>> Complete profile: profile name would be "complete" this will include >>>> all the default features that can be tried out in a standalone pack. This >>>> includes the features in the default profile and in addition it will have >>>> the MB and DAS features. >>>> >>>> or we can swap above two profiles, where we can have complete features >>>> as default and have others in another profile. >>>> >>>> Please provide us your suggestion regarding this. >>>> >>>> Thanks, >>>> *Ayyoob Hamza* >>>> *Software Engineer* >>>> WSO2 Inc.; http://wso2.com >>>> email: [email protected] cell: +94 77 1681010 <%2B94%2077%207779495> >>>> >>> >>> >> > -- *Charitha Goonetilleke* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 77 751 3669 <%2B94777513669> Twitter:@CharithaWs <https://twitter.com/CharithaWs>, fb: charithag <https://www.facebook.com/charithag>, linkedin: charithag <http://www.linkedin.com/in/charithag>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
