web services - UDDI Best Practices -
my organisation getting soa world (a bit late, that's it's here!) , we're looking esb toolkit 2.0 (we have biztalk server 2009).
we're keen on implementing uddi (specifically, uddi services v3.0 ships bts 2009), we're low on actual uddi experience. want manage ever-burgeoning number of web services have across our environments.
what best practices implementing uddi? example:-
- would implement single highly-available resilient uddi server hosts services , bindings, including test environment versions? or implement separate uddi repositories test , production environments?
- i'm aware of oasis technical note v2.0 on wsdl , uddi, implement that? i.e. abstract parts of wsdl tmodels, implementation parts of wsdl bindings?
- would go effort of capturing non-web service endpoints in uddi, or use wsdl?
- what "gotchas"?
ibm has stopped using uddi, , using http , rest interface wsrr. oracle not using uddi in of solution, yet have registry , repository supports uddi v3 (this oem)
i cant see uddi used in microsoft azure platform, unsure here?
i not saying dead standard... others are
Comments
Post a Comment