SERVICE ORIE TED COMPUTI G ARCHITECTURE FOR CLIMATE MODELI G

Size: px

Start display at page:

Download "SERVICE ORIE TED COMPUTI G ARCHITECTURE FOR CLIMATE MODELI G"

Valentine Marshall
5 years ago
Views:

1 SERVICE ORIE TED COMPUTI G ARCHITECTURE FOR CLIMATE MODELI G Monish Advani 1, Varish Mulwad 2, Uzoma Obinna 2 1 Department of Information Systems 2 Department of Computer Science and Electrical Engineering University of Maryland Baltimore County {madvani1, varish1, ouzoma1}@ umbc.edu Abstract In the Climate Modeling project, we have created web services to expose the data within the climate models. The current scope of project focused on climate models from ASA GISS and OAA GFDL and one scenario for air temperature values. However, in the course of the project we have created a framework which can be used for climate models from various agencies and various other scenarios too. Page 1 of 21

2 1. Introduction Climate Change[1] is a very complex issue: policymakers need an objective source of information about the causes of climate change, its potential environmental and socioeconomic consequences and the adaptation and mitigation options to respond to it. This is why WMO and UNEP established the Intergovernmental Panel on Climate Change (IPCC) in The IPCC Data Distribution Centre[2] (DDC) was established in 1998, following a recommendation by the IPCC Task Group on Data and Scenario Support for Impact and Climate Analysis (TGICA), to facilitate the timely distribution of a consistent set of up-todate scenarios of changes in climate and related environmental and socio-economic factors for use in climate impact and adaptation assessment. While impact researchers are free to use whatever simulations are appropriate for their studies, it is hoped that the wide accessibility to these recent scenarios, and the knowledge that other research groups are probably applying them as well, may persuade analysts to adopt some or all of the scenarios held in the DDC. One of the clear objectives of the Centre is that new studies making use of these scenarios can feed into the IPCC assessment process. Data are being provided by the DDC over the World Wide Web. All research groups supplying datasets have agreed to these being in the public domain. The data are provided free of charge, but all users are requested to register to ensure both that the data are used for public scientific research rather than for commercial applications and also that they can be informed of possible modifications, additions and other new developments at the DDC. Service Oriented Architecture[3] (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. Services[4] provide a programming metaphor that supports the right kinds of programming models for open, distributed systems. Service architectures are modular, because each service inherently offers a provider subscriber interface. This interface enables much flexibility, for instance allowing proxy agents transparently to provide new services to be based on old services and to compose services as appropriate. By introducing the concepts of Service Oriented Architecture in Climate Modeling, it will be possible to present and make the data available with the IPCC to a wider range of audience and in more simple and less sophisticated manner. 1.1 Motivation The National Oceanic and Atmospheric Administration (NOAA) are now providing various weather related information via XML web services. NOAA provides information like: Forecasts Watch/warnings Current Observations Tropical Cyclone Advisories Storm Prediction Center Forecast Products Change Notices via XML web services. The NOAA model was a motivation for the Climate Modeling project. Page 2 of 21

3 1.2 Project Summary The goal of the Climate Modeling project is to download climate model data sets provided by the IPCC s Data Distribution Center and then create a set of web services based on the data in the data sets and provide the output to the clients. In the current scope, we downloaded two data sets provided by: i. NASA GISS ii. NOAA GFDL Both the climate model outputs contain air temperature information for 20 year averages in which carbon dioxide concentrations are increased at the rate of 1% per year, until they double and thereafter constant. We created a set of web services to expose the air temperature values and created a web based interface to provide the value to the users. 2. Climate Models The following section describes the information about the climate models whose data set we downloaded: i. ASA GISS Climate Model[5] Agency Name: Goddard Institute for Space Studies (GISS), NASA, USA Model name: GISS Model Atmospheric prognostic variables: Potential Temp, Specific Humidity, Total Water Condensate (either all ice or all liquid). Oceanic prognostic variables: Potential Enthalpy (J), Salt (kg), Total Mass (kg), Velocities (m/s). Atmospheric resolution: 4 deg lat, 5 deg long Oceanic resolution: 4 deg lat, 5 deg long ii. GFDL Climate Model[6] Agency name: Geophysical Fluid Dynamics Laboratory, NOAA Model name: CM2.0 AOGCM Atmospheric prognostic variables: Zonal and meridional wind components, surface pressure, temperature, specific humidity of water vapor, cloud liquid cloud ice and cloud fraction Oceanic prognostic variables: free surface height, temperature and salinity Atmospheric resolution: 2.5 degrees longitude, 2.0 degrees latitude, 24 levels Oceanic resolution: 1 degree longitudinal, 1 degree latitudinal with enhanced tropical resolution (1/3 on equator) 3. Users The following section describes the potential audience for the climate modeling project: i. Researchers: The researchers community would benefit most from the climate modeling project. The researchers community can make use of the information available from the climate models to analyze the potential effects and changes that may take place in the environment. Although climate modeling information is made available by the IPCC Data Center, the information is provided in a format which the researchers can find difficulty in working with. With the climate modeling project, this information would be available via set of web services in a web based interface (which we have developed) or even in a console based application. ii. Developers: The developers who want to create applications to provide the climate modeling data would also benefit a lot from this project. Since our project creates a set of web services, any developer can build an application on top of the web services provided by us and use them in their applications. It would save a lot of overhead in working with the data set files, for the developers since it will be easier for them to work with the web services. Page 3 of 21

4 iii. General Public: Since climate change has become such an important issue, even the everyday common man is interested. And such people would gain a lot of insight from the information provided climate models. 4. System Design Figure 1 shows the system architecture design. We download the data sets provided NASA GISS and GFDL from the IPCC Data Center and store it on our web server. This server will be same server which will be hosting the web services. The developer who wants use the web services will host his application on his web server. The client will request the data from the client web application which in turn will talk with our web server which is hosting the web services. In our case the web server used to host the web services is the Apache Tomcat and Axis2 The client interface which we created for demonstration purposes is hosted on Internet Information Services (IIS) 7.0 web server. With these two completely different web servers, the latter being a Microsoft server and the former a Java server, we have demonstrated the cross compatible the web services provided the Climate Modeling project are. 5. Challenges In the course of the project our team encountered quite a few challenges. Besides the regular challenges of any project like setting up the work environment, choosing the right tools and right development environment, working with the climate model data set files provided by the IPCC Data Distribution Center was a challenge in itself. The data set files provided by the IPCC Data Distribution Center are in the network Common Data Form (with a file extension of.nc) also popularly called as NetCDF. We worked on various approaches to work with the data set files before choosing one. We worked with three approaches before choosing the third approach. Page 4 of 21

5 The first approach we worked on was converting the data set files from nc format to txt file format. Once the file is converted to text files, we can extract data from the text file and present it to user as per the request. Or alternatively the data could have been stored in a database and then provide data to the user as per requests. Since there would have been a lot of overhead in converting the data set file into a text file and then mining the file and storing it into the database, we decided not to use this method. The second approach we worked on using a set of Java Libraries to access the data set files. NetCDF[7] provide a set of Java Libraries to access the data set files. However given the time constraint and some problems of integrating the libraries into our code, we decided not to use this approach too. The third approach (the one which we adopted) and used the following: We used a freely available dll (provided by which helped us access the data within the data set file from VB Excel macros. So using the VB Excel macro we accessed the data set file. A Java program executed a vbscript which in turn executed the macro. ii. Microsoft Visual Studio 2005 Microsoft Visual Studio 2005[9] is an Integrated Development Environment (IDE) distributed by Microsoft. It can be used to create both console (and windows) based application and web based applications. It is based on the IIS server. In our project we used Visual Studio 2005 to create the client interface, used to demonstration of how our web services can be used. iii. Apache Tomcat Apache Tomcat [10] is a servlet container created by the Apache Software Foundation. It is used to host Servlet and Java Server Pages (jsp). In our project, the Axis 2 was hosted on Apache Tomcat iv. Apache Axis 2 Apache Axis 2[11] is core engine for web services provided by the Apache Software Foundation. We have hosted and deployed our web services on the Axis 2 server. v. Panoply Panoply[12] is a NASA GISS tool that was used to create graphs and images from the values in the dataset files 6. Tools and Resources In the course of the project we used quite a few tools and resources which are listed below: i. etbeans 6.1 Intergrated Development Environment: NetBeans[8] is freely available Integrated Development Environment (IDE) which can be used to create applications in C, C++, Java, Ruby, Perl to name a few. NetBeans is currently distributed by Sun Microsystems. In our project, we used NetBeans to create our web services and the service archive file (the.aar file) which is eventually deployed on Axis 2. vi. etcdf for Excel NetCDF for Excel[13] provided a freely available dll to access the data set files using VB Macros. vii. Arm etcdf Data Extract (A DX) Arm Netcdf Data Extract[14] (ANDX) is a command-line utility designed for routine examination and extraction of data from netcdf files. Page 5 of 21

6 7. Role of Team Members The work was distributed amongst the team members as follows: Varish Mulwad: Worked with the data set files to extract values from them Web service identification Web service creation Web service implementation All the three presentations and final report Monish Advani: Worked of method 1 to extract values from data set files (as mentioned above) Design of the user interface Backend Design Implementation of UI Final Report Obinna Uzoma: Implementation of User Interface Final Report 8. What we learnt There were lots of things that we learnt from this project. One of the most things that we learnt about was about science climate change. We realized the significance of climate change more than even before. At the end of the project, we value our environment a lot more than what we did before. We have realized how significant it is to study climate changes and their impact on planet earth. Such studies will help us make policy decisions now that will help us take care of our planet earth. We also learnt about the significance of Service Oriented Computing and Service Oriented Architecture. As stated above, services provide a programming metaphor that supports the right kinds of programming models for open, distributed systems. Service Oriented Architecture helps us create open systems, which are not locked to any particular code or domain. 9. Future Work In the current scope, we downloaded two data sets, one each from NASA GISS and GFDL and worked on one scenario for air temperature. In the process we have created a frame work which will allow working with more such data sets and scenarios. Some of the future work that can be done to extend this project is: i. Create web services to work with more data sets from other agencies ii. Create web services to work with more variables and more scenarios (besides air temperature) iii. Providing the data using a secure communication channel, so that the data transmitted is not corrupted intentionally or unintentionally by any one. iv. Comparisons of various values from different climate models which have predicted future climate changes v. Use of parallel and distributed computing resources (like the Cell BE processor) as the amount of data to be processed will be large 10. Conclusion In this report we have described the various aspects and work related completed related to the Climate Modeling project. We have successfully created web services to provide data from within the data sets of the climate models from NASA GISS and GFDL. In the process we have been able to put in a framework which will allow us to extend this project beyond these two climate model data sets. Page 6 of 21

7 11. References [1] Intergovernmental Panel on Climate Change: [2] IPCC Data Distribution Centre: [3] C. M. MacKenzie, K. Laskey, F. McCabe, P. F. Brown, and R. Metz, Reference model for service oriented architecture 1.0, OASIS, Tech. Rep., [4] Munindar P. Singh and Michael N. Huhns, "Service-Oriented Computing: Semantics, Processes, Agents", John Wiley & Sons, Ltd., 2005 [5]NASA GISS: [6]GFDL: [7] NetCDF: [8]NetBeans: [9] Microsoft Visual Studio 2005: duct.aspx?productid=4 [10] Apache Tomcat: [11] Apache Axis2: [12] Panoply: [13] NetCDF for Excel: [14] Arm Netcdf Data Extract: Page 7 of 21

8 Appendix A A. Climate Modeling Home Page Page 8 of 21

9 B. Climate Modeling Registration Page Page 9 of 21

10 C. Climate Modeling Registration Page 2 Page 10 of 21

11 D. Climate Modeling Authentication Page Page 11 of 21

12 E. Climate Modeling Options Page Page 12 of 21

13 F. Air Temperature by values Page Page 13 of 21

14 G. Air Temperature by Graphs Page (1) Page 14 of 21

15 H. Air Temperature by Graphs Page (2) Page 15 of 21

16 Appendix B: WSDL <?xml version="1.0" encoding="utf-8"?> <wsdl:definitions xmlns:wsdl=" xmlns:ns1=" xmlns:ns=" xmlns:wsaw=" xmlns:http=" xmlns:xs=" xmlns:mime=" xmlns:soap=" xmlns:soap12=" targetnamespace=" <wsdl:documentation>climatemodel</wsdl:documentation> <wsdl:types> <xs:schema attributeformdefault="qualified" elementformdefault="qualified" targetnamespace=" <xs:element name="getairtemperature"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="datasetname" nillable="true" type="xs:string"/> <xs:element minoccurs="0" name="dateslice" nillable="true" type="xs:string"/> <xs:element minoccurs="0" name="latitude" nillable="true" type="xs:string"/> <xs:element minoccurs="0" name="longitude" nillable="true" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="getairtemperatureresponse"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="getdataset"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="datasetname" nillable="true" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="getdatasetresponse"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> Page 16 of 21

17 <xs:element name="getinputparameters"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="datasetname" nillable="true" type="xs:string"/> <xs:element minoccurs="0" name="parameterrequested" nillable="true" type="xs:string"/> <xs:element minoccurs="0" name="index" type="xs:int"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="getinputparametersresponse"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="getmap"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="climatemodelname" nillable="true" type="xs:string"/> <xs:element minoccurs="0" name="dateindex" type="xs:int"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="getmapresponse"> <xs:complextype> <xs:sequence> <xs:element minoccurs="0" name="return" nillable="true" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> <xs:element name="main"> <xs:complextype> <xs:sequence> <xs:element maxoccurs="unbounded" minoccurs="0" name="args" nillable="true" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:element> </xs:schema> </wsdl:types> <wsdl:message name="getmaprequest"> <wsdl:part name="parameters" element="ns:getmap"/> </wsdl:message> <wsdl:message name="getmapresponse"> <wsdl:part name="parameters" element="ns:getmapresponse"/> </wsdl:message> <wsdl:message name="mainrequest"> <wsdl:part name="parameters" element="ns:main"/> </wsdl:message> Page 17 of 21

18 <wsdl:message name="getinputparametersrequest"> <wsdl:part name="parameters" element="ns:getinputparameters"/> </wsdl:message> <wsdl:message name="getinputparametersresponse"> <wsdl:part name="parameters" element="ns:getinputparametersresponse"/> </wsdl:message> <wsdl:message name="getairtemperaturerequest"> <wsdl:part name="parameters" element="ns:getairtemperature"/> </wsdl:message> <wsdl:message name="getairtemperatureresponse"> <wsdl:part name="parameters" element="ns:getairtemperatureresponse"/> </wsdl:message> <wsdl:message name="getdatasetrequest"> <wsdl:part name="parameters" element="ns:getdataset"/> </wsdl:message> <wsdl:message name="getdatasetresponse"> <wsdl:part name="parameters" element="ns:getdatasetresponse"/> </wsdl:message> <wsdl:porttype name="climatemodelporttype"> <wsdl:operation name="getmap"> <wsdl:input message="ns:getmaprequest" wsaw:action="urn:getmap"/> <wsdl:output message="ns:getmapresponse" wsaw:action="urn:getmapresponse"/> <wsdl:operation name="main"> <wsdl:input message="ns:mainrequest" wsaw:action="urn:main"/> <wsdl:operation name="getinputparameters"> <wsdl:input message="ns:getinputparametersrequest" wsaw:action="urn:getinputparameters"/> <wsdl:output message="ns:getinputparametersresponse" wsaw:action="urn:getinputparametersresponse"/> <wsdl:operation name="getairtemperature"> <wsdl:input message="ns:getairtemperaturerequest" wsaw:action="urn:getairtemperature"/> <wsdl:output message="ns:getairtemperatureresponse" wsaw:action="urn:getairtemperatureresponse"/> <wsdl:operation name="getdataset"> <wsdl:input message="ns:getdatasetrequest" wsaw:action="urn:getdataset"/> <wsdl:output message="ns:getdatasetresponse" wsaw:action="urn:getdatasetresponse"/> </wsdl:porttype> <wsdl:binding name="climatemodelsoap11binding" type="ns:climatemodelporttype"> <soap:binding transport=" style="document"/> <wsdl:operation name="getmap"> <soap:operation soapaction="urn:getmap" style="document"/> Page 18 of 21

19 <soap:body use="literal"/> <soap:body use="literal"/> <wsdl:operation name="main"> <soap:operation soapaction="urn:main" style="document"/> <soap:body use="literal"/> <wsdl:operation name="getinputparameters"> <soap:operation soapaction="urn:getinputparameters" style="document"/> <soap:body use="literal"/> <soap:body use="literal"/> <wsdl:operation name="getairtemperature"> <soap:operation soapaction="urn:getairtemperature" style="document"/> <soap:body use="literal"/> <soap:body use="literal"/> <wsdl:operation name="getdataset"> <soap:operation soapaction="urn:getdataset" style="document"/> <soap:body use="literal"/> <soap:body use="literal"/> </wsdl:binding> <wsdl:binding name="climatemodelsoap12binding" type="ns:climatemodelporttype"> <soap12:binding transport=" style="document"/> <wsdl:operation name="getmap"> <soap12:operation soapaction="urn:getmap" style="document"/> <soap12:body use="literal"/> <soap12:body use="literal"/> Page 19 of 21

20 <wsdl:operation name="main"> <soap12:operation soapaction="urn:main" style="document"/> <soap12:body use="literal"/> <wsdl:operation name="getinputparameters"> <soap12:operation soapaction="urn:getinputparameters" style="document"/> <soap12:body use="literal"/> <soap12:body use="literal"/> <wsdl:operation name="getairtemperature"> <soap12:operation soapaction="urn:getairtemperature" style="document"/> <soap12:body use="literal"/> <soap12:body use="literal"/> <wsdl:operation name="getdataset"> <soap12:operation soapaction="urn:getdataset" style="document"/> <soap12:body use="literal"/> <soap12:body use="literal"/> </wsdl:binding> <wsdl:binding name="climatemodelhttpbinding" type="ns:climatemodelporttype"> < verb="post"/> <wsdl:operation name="getmap"> < location="climatemodel/getmap"/> <mime:content type="text/xml" part="getmap"/> <mime:content type="text/xml" part="getmap"/> <wsdl:operation name="main"> < location="climatemodel/main"/> <mime:content type="text/xml" part="main"/> <wsdl:operation name="getinputparameters"> Page 20 of 21

21 < location="climatemodel/getinputparameters"/> <mime:content type="text/xml" part="getinputparameters"/> <mime:content type="text/xml" part="getinputparameters"/> <wsdl:operation name="getairtemperature"> < location="climatemodel/getairtemperature"/> <mime:content type="text/xml" part="getairtemperature"/> <mime:content type="text/xml" part="getairtemperature"/> <wsdl:operation name="getdataset"> < location="climatemodel/getdataset"/> <mime:content type="text/xml" part="getdataset"/> <mime:content type="text/xml" part="getdataset"/> </wsdl:binding> <wsdl:service name="climatemodel"> <wsdl:port name="climatemodelhttpsoap11endpoint" binding="ns:climatemodelsoap11binding"> <soap:address location=" odelhttpsoap11endpoint/"/> </wsdl:port> <wsdl:port name="climatemodelhttpsoap12endpoint" binding="ns:climatemodelsoap12binding"> <soap12:address location=" odelhttpsoap12endpoint/"/> </wsdl:port> <wsdl:port name="climatemodelhttpendpoint" binding="ns:climatemodelhttpbinding"> < location=" odelhttpendpoint/"/> </wsdl:port> </wsdl:service> </wsdl:definitions> Page 21 of 21

GoProCaseSoap.wsdl <?xml version='1.0' encoding='utf-8'?><wsdl:definitions name="goprocasesoapservice"

GoProCaseSoap.wsdl <?xml version='1.0' encoding='utf-8'?><wsdl:definitions name=goprocasesoapservice