HI Eric
Unifying the way of use of data source by defining through one
configuration (synapse.properties) and make those available for any
components that need those is a best practice. Even with current ESB,
this should work(I didn't try) because both hibernate and registry can
configure to use data sources. I will try to make this available for
this 1.7 release if I can find some time.
Currently, we don't support the encryption of passwords in datasources.
But we can support it in the same way tomcat did it (Please refer
http://websphere.sys-con.com/read/393364.htm).
I find a nice idea when reading some thing related to securing password.
All passwords are keep in a single file and after creating datasources
when starting up the application, the password file is deleted.
Passwords can not be read anymore.
Thanks
Indika
Hubert, Eric wrote:
Hi all,
today I would like to discuss with you the handling of datasources. I'm not
sure whether I have a good overview about the different ways to configure and
use datasources in WSO2 ESB. So please correct if I'm wrong on my observations.
We have at least three different types/places of datasource definitions:
1) pool approach for mediators with usage in synapse.xml and configuration in
synapse.properties
2) hibernate for statistics and registry meta-data with declaration and
configuration in wso2esb.hibernate.cfg.xml
3) datasource for registry (not sure about this, but I just doulbe checked the
current version and it seems to me as if you have already unified this with
approach 1), which I really like.
Encryption of passwords in datasources seems to be not possible, though. This
is a big problem as it is a requirement for most production environments. We
need to find a solution for this. Ideally all datasources should leverage the
same mechanism. Then it would be easy to implement this in a central place.
Could you change the mechanism with hibernate to use a jndi lookup on a
datasource you declare and configure in synapse.properties and only reference
in wso2esb.hibernate.cfg.xml
Regarding the encryption support of datasource passwords I then would like to
create a JIRA issue in the synapse project. Or is this possible and I have just
missed some configuration? I think if it is not available right now it is not
needed to reivent the wheel. Maybe you could use the same mechanism Jboss AS is
using.
Regards,
Eric
--
Eric Hubert
Software Architect
Associate Director Research & Development
Jamba! GmbH
Domaquarée
Karl-Liebknecht-Str. 5
10178 Berlin
Germany
Phone: +49- (0)30- 69 538- 3506
Fax: +49- (0)30- 69 538- 599
E-Mail: [EMAIL PROTECTED]
Jamba- Have it or hate it.
---------------------------------------------------------------------------------------
"Musik, Videos, Spiele und jede Menge coole Leute - jetzt neu bei Jamba"
Web/ WAP: http://www.jamba.de <http://www.jamba.de/>
Jamba! GmbH
Gesellschaft mit beschränkter Haftung mit Sitz in Berlin
HRB Nr. 97990 Amtsgericht Charlottenburg
Geschäftsführer: Lee Fenton, Dirk Hoffmann, Michael Paull
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
