Hi Chris, I have come across this blog for (b)
[1] http://sumedhask.blogspot.com/2013/10/start-wso2-server-as-linux-service.html On Thu, Jun 12, 2014 at 10:37 PM, chris snow <[email protected]> wrote: > As per the $subject, what is the best practise? > > I have seen instructions for extracting the binary [1] and running the > startup script [2], but just these steps don't seem robust enough for > a production environment. In a production environment, I would > expect to see some additional steps: > > a) create a unix user account and unix group for running the service > b) creating init.d scripts for starting the service automatically > c) to security harden the service (e.g. replace self signed > certificates - which certificates, change default passwords - which > user accounts) > d) configuring clustering (this seems to be documented [3]) > e) configuring a production database credential store (this seems to > be documented [4]), or > f) configuring a production ldap credential store > > Have I missed some documentation in the wiki, or are these > undocumented steps not normally performed in production environments? > > I've also seen some puppet scripts [5]. Are these scripts production > ready? > > Many thanks, > > Chris > --- > [1] https://docs.wso2.org/display/ESB481/Installing+on+Linux > [2] https://docs.wso2.org/display/ESB481/Running+the+Product > [3] https://docs.wso2.org/display/ESB481/Clustered+Deployment > [4] https://docs.wso2.org/display/ESB481/Working+with+Databases > [5] https://github.com/wso2/Puppet/tree/master/modules/esb/4.8.0/esb > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
