Nesrine I've read that article too. For reference, the official recommendation for QoS data in UDDI is this:
https://www.oasis-open.org/committees/download.php/5333/UDDI%20WSM-Info-1v11.doc The juddi-client includes all of those tModel keys in the WSDM Constants class I believe there's also an example utility class for weighting endpoints based on some WSDM tModel value The jUDDI server includes those tModels as part of the predefined set of tModels That said.... You need a tool that can - monitor service performance - publish/update business/service/binding/tModelInstanceInfos periodically There are a few tools that can do this that I know of. - Amberpoint SMS (which is now an oracle product) - WSO2 may have this functionality but i'm just guessing - FGSMS, definitely has this and is open source OR You can write your own solution OR You can manually attach the metrics to the service's binding template. The juddi user interface can help with that and has a number of helpers to help you populate the tmodel stuff. Does that help? On Sat, Oct 7, 2017 at 11:14 AM, Nesrine Hamdani <[email protected]> wrote: > hi, i want to developpe an extended uddi like in this article. i install > juddi disto 3.3.4 it's ok . publish service is ok but how to recognize > (implement) tmodel to have response time ... for Qos . > thank you for your help
