1. Evaluating Web Services for FDMS Cynthia Loitch OAR/PMEL (PI) Eugene Burger OAR/PMEL NOAA Research Webshop 2003 Longmont, CO 3-5 June 2003

2. Overview What are Web Services, SOAP and FDMS? What are Web Services, SOAP and FDMS? Goals Goals Evaluation process Evaluation process Requirements for FDMS? Requirements for FDMS? Architecture Architecture Implementation Implementation Impressions Impressions Conclusion Conclusion

3. Web Services & SOAP Web services is a misnomer; it has nothing to do with the Web Web services is a misnomer; it has nothing to do with the Web Web services encompass a set of related standards that enable computer applications to communicate and exchange data via the Internet. Web services encompass a set of related standards that enable computer applications to communicate and exchange data via the Internet. Web Services are a technology for exposing a software API to the Internet Web Services are a technology for exposing a software API to the Internet Web Services Abstraction allow independent alteration of client and/or server configuration Web Services Abstraction allow independent alteration of client and/or server configuration Technologies utilized: Technologies utilized: HTTP HTTP XML – eXtensible Markup Language XML – eXtensible Markup Language SOAP – Simple Object Access Protocol SOAP – Simple Object Access Protocol W3c Standard supported by Microsoft, IBM etc. W3c Standard supported by Microsoft, IBM etc. An XML based protocol that enables applications to communicate over the internet by using XML documents called SOAP messages. An XML based protocol that enables applications to communicate over the internet by using XML documents called SOAP messages.

4. SOAP Message structure

5. FDMS FDMS is the Financial Database Management System utilized by NOAA Research FDMS is the Financial Database Management System utilized by NOAA Research Commitment tracking software Commitment tracking software Used throughout NOAA Research Used throughout NOAA Research 19 offices located throughout the U.S. 19 offices located throughout the U.S. Remote access via Citrix Server Remote access via Citrix Server Migrating system to a single SQLServer database Migrating system to a single SQLServer database Considering alternative client technologies with this database Considering alternative client technologies with this database

6. Goals To answer the question: To answer the question: Are Web Services with SOAP a viable client- server technology alternative for use in the next generation of the FDMS application?

7. Evaluation process Familiarize ourselves with technology Familiarize ourselves with technology Server infrastructure Server infrastructure Client options Client options Bandwidth restraints, if any Bandwidth restraints, if any

8. Requirements Client server application Client server application Secure data transfer Secure data transfer Authenticated user sessions Authenticated user sessions

10. Query page Screen snapshot of the dataset selection webpage Screen snapshot of the dataset selection webpage Asking to see information on Credit Card data download from CAMS Asking to see information on Credit Card data download from CAMS

11. Result set rendering Screen snapshot of the results web page Screen snapshot of the results web page Shows when Credit Card data downloads occurred Shows when Credit Card data downloads occurred

12. API exposed by the Web Services 2 methods exposed 2 methods exposed getDownloadDates(String) getDownloadDates(String) getDownloadSets(Date) getDownloadSets(Date)

13. SOAP Invocation message HTTP Post Header Post /ccx/DownloadMonitor HTTP/1.0 Content-Lentgh: 541 Host: Localhost Content-Type: text/xml; charset=utf-8 SOAPAction: "Axis:DownloadMonitor:DownloadService#getDownload Dates"

14. SOAP Invocation message Root element - namespace declarations <SOAP-ENV:Envelope SOAP- ENV:encodingStyle="http://schemas.xmlsoap.org/soap/ encoding/" SOAP- ENV:encodingStyle="http://schemas.xmlsoap.org/soap/ encoding/" xmlns:SOAP- ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP- ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=http://www.w3.org/2001/XMLSchema" xmlns:xsd=http://www.w3.org/2001/XMLSchema" xmlns:SOAP- ENC="http://schemas.xmlsoap.org/soap/encoding/"> xmlns:SOAP- ENC="http://schemas.xmlsoap.org/soap/encoding/">

15. SOAP Invocation message Root element - envelope body <SOAP-ENV:Body> FIMAOO</DataSet></ns1:getDownloadDates></SOAP-ENV:Body><SOAP-ENV:Envelope>

16. SOAP response message HTTP/1.0 200 OK Content-Type: text/xml; charset=utf-8 Content-Length: 580 Date: Mon, 26 May 2003 16:23:34 GMT

17. SOAP response message <SOAP-ENV:Envelope SOAP- ENV:encodingStyle="http://schemas.xmlsoap.org/soap /encoding/" SOAP- ENV:encodingStyle="http://schemas.xmlsoap.org/soap /encoding/" xmlns:SOAP- ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP- ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=http://www.w3.org/2001/XMLSchema" xmlns:xsd=http://www.w3.org/2001/XMLSchema" xmlns:SOAP- ENC="http://schemas.xmlsoap.org/soap/encoding/"> xmlns:SOAP- ENC="http://schemas.xmlsoap.org/soap/encoding/">

18. SOAP response message <SOAP-ENV:Header/><SOAP-ENV:Body SOAP- ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <cc1:getDownloadDatesResponse xmlns:cc1="axis:DownloadMonitor:DownloadService" SOAP- ENC:root="1"> 1/29/2003 3:33:30 PM </return>

19. Conclusion FDMS Applicability FDMS Applicability Tomcat and Axis server configuration settings can be complex Tomcat and Axis server configuration settings can be complex SOAP messages have some bandwidth overhead SOAP messages have some bandwidth overhead this could be mitigated by using compression this could be mitigated by using compression Custom software could simplify (FDMS) architecture Custom software could simplify (FDMS) architecture Because the user community is limited, custom written architecture is an option with FDMS. Because the user community is limited, custom written architecture is an option with FDMS. Industry standard Web Services does allow us to alter server / client applications independently Industry standard Web Services does allow us to alter server / client applications independently Client technologies, maybe using Web Services, will be considered Client technologies, maybe using Web Services, will be considered Microsoft InfoPath Microsoft InfoPath Acrobat forms Acrobat forms

20. Promising new technologies Microsoft InfoPath Microsoft InfoPath InfoPath 2003 (formerly code-named "XDocs") InfoPath 2003 (formerly code-named "XDocs") New Microsoft Office addition (2003) New Microsoft Office addition (2003) helps teams and organizations gather and share information by creating rich, dynamic XML–based forms. helps teams and organizations gather and share information by creating rich, dynamic XML–based forms. www.microsoft.com/office/preview/infopath/default.asp www.microsoft.com/office/preview/infopath/default.asp Also XML & WebServices based Also XML & WebServices based

21. Conclusion Our experience has lead us to science applications for which Web Services and SOAP are well suited. Our experience has lead us to science applications for which Web Services and SOAP are well suited. We will be developing Web Services for NOAA TAO El Nino buoy data in FY03 We will be developing Web Services for NOAA TAO El Nino buoy data in FY03