On Thu, Nov 8, 2012 at 1:24 PM, Selvaratnam Uthaiyashankar <[email protected] > wrote:
> > > On Thu, Nov 8, 2012 at 10:43 AM, Shammi Jayasinghe <[email protected]>wrote: > >> Hi, >> >> In Wso2 Message Broker , currently we are using a custom wso2server.sh >> file. We inject this in to the pack when >> building the distribution. The reason for this customization is we need >> to have some system properties in the start >> script of MB. >> >> Reason for system properties : >> >> We are using cassandra server feature in MB which is designed to start >> the Cassandra server , when starting the >> wso2 product. But in MB we have controlled this using an OSGI service to >> not start the cassandra server automatically. >> Then we specify to start the embedded cassandra or external cassandra in >> the configuration file on MB. So , to have >> the above control , we need to have the system property. >> > > Can we have some sensible "default" value for these properties? So, if the > properties are not defined, we can assume the default and start servers. > Yes, I checked with adding a default value and it works. How every if the user is going to have an external cassandra server ( which is recommended ) , he will have to add those system properties to start script. So we are going to solve this problem by having default values for the specified system properties and Updating the product Wiki on adding required properties when using an external cassandra server after feature installation. Thanks Shammi > > (Also, this mail should go to dev@) > > > >> >> So when we try to install the MB product features via the p2 repository >> to Carbon or any wso2 product, we will have to >> have these system properties in the start up script. AFAIU there are two >> possible ways to do that. >> >> 1. Replace the existing start up scripts with the custom start up scripts >> we have for MB , when installing andes feature. >> - With this approach , there can be problems. If a user has >> added some tune up parameters or any customization >> to his start up scripts , those are getting lost when >> replaced the script. >> >> 2. Documenting to add the required system properties in the MB wiki with >> out doing any script replacements. >> - First impression of the user on feature installation >> getting bad, when it prompting errors after feature >> installation and then he need to look for the fix in the >> web. >> >> What would be the best possible way to handle this. >> >> Thanks >> Shammi >> -- >> Best Regards,* >> >> Shammi Jayasinghe* >> Senior Software Engineer; WSO2, Inc.; http://wso2.com, >> mobile: +94 71 4493085 >> >> >> > > > -- > S.Uthaiyashankar > Director, Cloud Solutions > WSO2 Inc. > http://wso2.com/ - "lean . enterprise . middleware" > > Phone: +94 714897591 > -- Best Regards,* Shammi Jayasinghe* Senior Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
