Thanks Anjana! On Wed, Sep 9, 2015 at 10:03 AM, Anjana Fernando <[email protected]> wrote:
> Hi Imesh, > > We don't create p2 profiles as such for DAS, because there are some issues > with that approach, when it is used in our scenarios. So what we basically > have is a special set of Java system variables to disable whatever feature > we want to disable, and we internally disable those features. These flags > are documented and can be found here [1]. > > [1] https://docs.wso2.com/display/DAS300/Disabling+selected+DAS+components > > Cheers, > Anjana. > > On Wed, Sep 9, 2015 at 9:58 AM, Imesh Gunaratne <[email protected]> wrote: > >> Hi Anjana, >> >> Do we have any plans to create profiles for DAS data receiver, storm, >> indexer, analyzer and dashboard according to [1]? I checked the latest p2 >> profile [2] but could not see any profiles other than the default at the >> moment. >> >> [1] >> https://docs.wso2.com/display/CLUSTER420/Fully+Distributed+High+Availability+Deployment >> [2] >> https://github.com/wso2/product-bam/blob/master/modules/p2-profile-gen/pom.xml >> >> Thanks >> >> -- >> *Imesh Gunaratne* >> Senior Technical Lead >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: http://imesh.gunaratne.org >> Lean . Enterprise . Middleware >> >> > > > -- > *Anjana Fernando* > Senior Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- *Imesh Gunaratne* Senior Technical Lead WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: http://imesh.gunaratne.org Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
