1. 1 An Effective Dynamic Invocation System for Web Service BAI 2004 26 March ２００ 4 Takashi KOSHIDA Matsue National College of Technology Nara Institute of Science and Technology

2. 2 The content of my presentation 1. Introduction Some background/Problems ２. System model About WSIF, an overview of this system Implementation ３. Experimental Results Sample program Our system 4. Conclusion

3. 3 1.Introduction The B2B system is now widely used. But it is limited to regular transactions. However, SOAP,UDDI and WSDL has enabled world-wide dynamic business transactions. But, we think, not enough. Because, there are three problems. It is difficult 1.to discover the Web Service that we want to use 、 2.to know how to use it 、 3.and to make a client program for executing a Web Service.

4. 4 So, in this paper, we focused on the 3rd problem. And to solve it, we used WSIF. 3. and to make a client program for executing a Web Service.

5. 5 Web Service is the distributed processing technology on Web. XML is used for data exchange. The make up of the Web Service Service RequesterService Provider SOAP retrieval registration/publish execution UDDI WSDL

6. 6 2. System model About WSIF (Web Services Invocation Framework) It makes stub-less dynamic invocation possible. It requires WSDL description of Web Service. But,for execution, it is required to specify correctly the WSDL ’ s URL, Web Service ’ s name, method name, input-and-output parameter name and type. These are complex procedures. More easily and automatically!

7. 7 An overview of our system Automatic parameter setup and execution 1. First, the system retrieves and discovers the WSDL ’ s URL from the UDDI registry. 2. And downloads and analyzes the WSDL. 3. Then, setup the Web Service ’ s name, method name and input-and-output parameter name and type. 4. Finally,executes a Web Service. This system is applied to primitive type data as an output. However, it is applicable also to complex (user-defined) type data now.

8. 8 A part of WSDL description …………………………………………….. ………………………………………… Input parameter name/type Output parameter name/type Web Service name Method name Same name The system compares the name of these portions and distinguishes the parameter name of an input and an output.

9. 9 UDDI Registry URL of WSDL file analyze and extract setting Web Service Server tModel name, tModelKey and input parameter value retrieval WSDL data Web Service Execution WSIF API Input/output parameter name Input/output parameter type Web Service method name extract download Workflow tModel name, tModelKey, Input parameter value WSDL ’ s URL WSDL file Web Service name, method name and input-and-output parameter name and type Figure 1.

10. 10 3.Experimental Results We used the IBM UDDI registry for testing. tModelkey

11. 11 Result of sample program D:\WSIF\wsif-src-2.0\wsif-2.0\build\samples>java clients.DynamicInvoker http://services.xmethods.net/soap/urn:xmethods-delayed- quotes.wsdl getQuote IBM Reading WSDL document from 'http://services.xmethods.net/soap/urn:xmethods-delayed- quotes.wsdl' Executing operation getQuote Result: Result=91.01 Done! WSDL ’ s URL Method name Input parameter name Therefore, a user needs to know URL of a WSDL file, and the method name of Web Service beforehand. The sample program appended to WSIF has the structure of specifying

12. 12 D:\WSIF\wsif-src-2.0\wsif-2.0\build\samples>java IBMFindtModelGetWSDLaWSIF3 StockQuote UUID:F24269F0-3426-11D8- B936-000629DC0A53 IBM ***** IBM test-UDDI check program. ***** tModelName:StockQuote tModeleKey:UUID:362EC6E0-BA21-11D5-A5FE-0004AC49CC1E WSDL---URL:http://192.168.10.36/StockQuote/StockQuoteService.wsdl tModelName:StockQuote tModeleKey:UUID:62B655E0-A2C6-11D7-9CD6-000629DC0A53 WSDL---URL:http://www.cise.ufl.edu/~lnarasim/Quote.wsdl tModelName:StockQuote tModeleKey:UUID:F24269F0-3426-11D8-B936-000629DC0A53 WSDL---URL:http://services.xmethods.net/soap/urn:xmethods-delayed- quotes.wsdl Reading WSDL document from 'http://services.xmethods.net/soap/urn:xmethods-delayed-quotes.wsdl' Return = 93.14 Input parameter name tModel name tModelKey Results of our system:1 On the other hand, our system specifies

13. 13 Results of our system:2 D:\WSIF\wsif-src-2.0\wsif-2.0\build\samples>java IBMFindtModelGetWSDLaWSIF3 WeatherTemperature UUID:8A0FE2B0- 3429-11D8-B936-000629DC0A53 15470 ***** IBM test-UDDI check program. ***** tModelName:WeatherTemperature tModeleKey:UUID:8A0FE2B0-3429-11D8-B936-000629DC0A53 WSDL---URL:http://www.xmethods.net/sd/2001/TemperatureService.wsdl Reading WSDL document from 'http://www.xmethods.net/sd/2001/TemperatureService.wsdl' Return = 36.0 Input parameter name tModel name tModelKey

14. 14 D:\WSIF\wsif-src-2.0\wsif-2.0\build\samples>java IBMFindtModelGetWSDLaWSIF3 CurrencyExchangeRate UUID:E39408B0- 342A-11D8-B936-000629DC0A53 JAPAN USA ***** IBM test-UDDI check program. ***** tModelName:CurrencyExchangeRate tModeleKey:UUID:E39408B0-342A-11D8-B936-000629DC0A53 WSDL--- URL:http://www.xmethods.net/sd/2001/CurrencyExchangeService.wsdl Reading WSDL document from 'http://www.xmethods.net/sd/2001/CurrencyExchangeService.wsdl' Return = 107.58 Results of our system:3 Input parameter names tModel name tModelKey

15. 15 We developed an automatic dynamic invocation system starting from the UDDI registry. Feature Retrieval of WSDL ’ s URL from the UDDI registry Automatic data extraction and setting from the WSDL description of Web Service Stub-less execution using WSIF Output type is restricted to the primitive data type. However, for complex(user-defined) data type, we already developed as the same system also. 4.Conclusion ×

16. 16 The UDDI registry is the core of Web Service technology. But in practice, it is difficult to quickly discover necessary Web Services from the UDDI registry. We have to enable it to find easily the Web Service which a user needs. Important !