Restful Based Heterogeneous Geoprocessing Workflow
Total Page:16
File Type:pdf, Size:1020Kb
Computers & Geosciences 47 (2012) 102–110 Contents lists available at SciVerse ScienceDirect Computers & Geosciences journal homepage: www.elsevier.com/locate/cageo RESTFul based heterogeneous Geoprocessing workflow interoperation for Sensor Web Service Chao Yang a,b, Nengcheng Chen a, Liping Di b,n a State Key Laboratory of Information Engineering in Surveying, Mapping and Remote Sensing, Wuhan University, 129 Luoyu Road, Wuhan, Hubei 430079, China b Center for Spatial Information Science and Systems, George Mason University, 4400 University Drive, MSN 6E1, Fairfax, VA 22030, USA article info abstract Article history: Advanced sensors on board satellites offer detailed Earth observations. A workflow is one approach for Received 19 March 2011 designing, implementing and constructing a flexible and live link between these sensors’ resources and Received in revised form users. It can coordinate, organize and aggregate the distributed sensor Web services to meet the 1 September 2011 requirement of a complex Earth observation scenario. Accepted 7 November 2011 A RESTFul based workflow interoperation method is proposed to integrate heterogeneous work- Available online 15 November 2011 flows into an interoperable unit. The Atom protocols are applied to describe and manage workflow Keywords: resources. The XML Process Definition Language (XPDL) and Business Process Execution Language RESTFul (BPEL) workflow standards are applied to structure a workflow that accesses sensor information and Workflow interoperation one that processes it separately. Then, a scenario for nitrogen dioxide (NO ) from a volcanic eruption is OGC Web Services 2 used to investigate the feasibility of the proposed method. The RESTFul based workflows interoperation NO2 system can describe, publish, discover, access and coordinate heterogeneous Geoprocessing workflows. & 2011 Elsevier Ltd. All rights reserved. 1. Introduction (EML) (Everding and Echterhoff, 2008). The service specifications for sensors connected to the Web are mainly the Sensor Planning 1.1. Sensor Web Enablement Service (SPS) (Simonis, 2007), the Web Notification Service (WNS) (Simonis and Echterhoff, 2006), the Sensor Alert Service (SAS) The OpenGIS Web Service (OWS) framework, which is speci- (Simonis, 2006) and the Sensor Observation Service (SOS) (Na and fied by the Open Geospatial Consortium (OGC), provides a series Priest, 2007). of common Web service architectures and standards for geospa- tial information interchange and interoperation. Through these 1.2. Workflow technique for Sensor Web 2.0 specifications, isolated information is expanded into accessible Web resources and user can obtain information through distrib- In the Sensor Web 2.0 (Mandl et al., 2008) software architecture, uted Web services. the Sensor Web combines sensors and sensor networks with a In a sensor Web environment, sensors and sensor resources Service-Oriented Architecture (SOA), which allows users to discover, are distributed and heterogeneous. The Sensor Web Enablement describe and invoke services from a heterogeneous software plat- (SWE) specifications are the subset of OWS specifications that form via a series of technology such as eXtensive Makeup Language aims to create an integrated geospatial Sensor Web network (XML), Simple Object Access Protocol (SOAP) or Web Service where all types of sensors, instruments, imaging devices and Description Language (WSDL) and various workflow standards repositories of sensor data are discoverable, accessible, applicable applied in converting the Sensor Web into a desirable geospatial and controllable. workflow (or a geospatial process chain) (Chen et al., 2010a). The SWE consists of a sensor information model and a number of workflow is designed to describe the whole sensor knowledge sensor Web specifications. The information model contains four transfer process from raw sensor observations to informational parts: SensorML (Botts and Robin, 2007), Observation and Mea- products. This process connects a series of operation steps from surements (O&M) (Cox, 2007a, 2007b), Transducer Markup Lan- serving planning and observations, through data processing and guage (TML) (Havens, 2007) and Event pattern Markup Language information managing (Chen et al., 2010b). Currently, there are two main workflow industry structural and technical standards in the Web workflow applications field: an n Corresponding author. Tel.: þ1 703 993 6114; fax: þ1 703 993 6127. XML-based workflow description language (mostly in XML Process E-mail address: [email protected] (L. Di). Definition Language (XPDL) and Web Service Flow Language 0098-3004/$ - see front matter & 2011 Elsevier Ltd. All rights reserved. doi:10.1016/j.cageo.2011.11.010 C. Yang et al. / Computers & Geosciences 47 (2012) 102–110 103 (WSFL)) and the Business Process Execution Language (BPEL). XPDL (Rosenberg et al., 2008). Under the SOA environment, the work- is a Workflow Management Coalition (WfMC) standard for inter- flows are applied as Web Services, the interoperation of work- changing business process definitions between different workflows flows built on the interface chaining. Although there are or Web Services. BPEL is an industry standard executable language numerous transgressions in daily Web practice, the consensus for orchestrating Web Services into business processes. of the Web development community backs the resource-oriented A XPDL design workflow uses an XML-based syntax and is paradigm proposed by the REST model. The simplicity of the specified by an XML schema. The workflow’s components and single interface, single protocol (HTTP methods) approach has actions are both described as ‘‘Elements’’. As a standard workflow potential benefit in complex scenarios. modeling language, XPDL endorses process definition visualiza- With the explosion of Earth observation information, the trend tion and the XPDL based process supports more than 20 kinds of is to organize individual Sensor Web Services into aggregated workflow patterns. geospatial workflows to offer advanced operations for complex Unlike XPDL, BPEL is primarily concerned with the Web service application scenarios. Because the workflows vary in character it is orchestration, BPEL has its own XML based programming syntax, hard to interoperate them in a unified workflow engine. Usually, with commands such as ‘‘receive’’, ‘‘reply’’ and ‘‘invoke’’ for control- the solution under the SOA framework is that workflows are sealed ling the basic workflow process unit—‘‘Activities’’, which directs the and exposed as Web service interfaces for future interoperation. interoperation of different Web servicesandisdescribedonlybya This paper focuses on the interoperation of heterogeneous geos- series of connection subelements in a BPEL process. BPEL itself patial workflows in the Sensor Web environment using the REST- defines the syntax for an XML-based programming language. Thus, Ful method. As opposed to the Web service chaining model in the Web Services can be organized and directed in an order, which is SOA, this paper abstracts and presents the concrete workflow significant in complex Web service integration. As they differ in process as a virtual process. This process can be published and structure and operation model, transfer between an XPDL process fed as a Web resource; the resource can be created, accessed and and BPEL process workflow is hard to achieve. operated by users and then the process executed in a specific workflow engine. 1.3. REST architecture and RESTFul Web workflow In Section 2, workflow technology and the RESTFul architec- ture style are introduced as the base of the RESTFul geospatial The Representational State Transfer (REST) (Fielding, 2000)isa Workflow Interoperation System (RWIS). In Section 3, workflow styleofsoftwarearchitecturefordistributedhypermediasystems interoperation technique details of RWIS and heterogeneous such as the World Wide Web. Distributed Web content is described Sensor Web workflow instances (XPDL based sensor information as a Web resource. The RESTFul Web service (Richardson and Ruby, accessing workflow and the BPEL sensor information processing 2007) is gaining increased attention because of this simple Web workflow separately) are described. Then, the benefits of the service publishing and consuming: distributed Web Services are RWIS architecture, work pattern and evaluation of the on-demand described and referenced as Web resources with a global identifier environment observation and monitoring under the Sensor Web (e.g., a URI in HTTP), applying HTTP method (e.g., POST, GET, PUT or Environment are discussed. Finally, Section 5 summarizes this DELETE) to operate Web resources. paper and presents the outlook for the future. In the RESTFul architecture, workflows are the collections of Web resources. A web resource has three defined attributes: the 2. Methodology URI for resources, the Internet media type of the data supported by the workflow (like XML) and the set of HTTP operations 2.1. System architecture supported by the workflow. After a workflow is deployed as an operable Web resource with a specified URL, users can create, Workflow, or a chain of Web services, has been widely applied modify and delete resources, passing data and information in integrating geospatial Web services (Di, 2005). A virtual work- through different workflow platforms. The main advantages of flow (or abstraction of the workflow) describes abstract Web applying RESTFul architecture in workflow interoperation are Services and data composition and provides ontology information ease of implementation, design and operation.