This example demonstrates how to use the WS Translator to call web
services. A dynamic VDB (defined in weather-vdb.xml) is used to access
the National Weather Service's SOAP/REST services at this URL:
http://www.nws.noaa.gov/forecasts/xml/ 


NOTE - depending on your OS/Shell the quoting/escaping required to run
the example can be complicated. It would be better to install a Java
client, such as SQLSquirrel, to run the example listed queries below. 

Steps:

1) Copy the following files to the <jboss.home>/server/<serverprofile>/deploy directory.
- weather-vdb.xml
- weather-ds.xml 

2) Start the JBoss Container

==== Using the simpleclient example ====

3) Edit JDBCClient.java and specify a username and password for a
   valid user account.

4) Use the simpleclient example run script, using the following format

$./run.sh localhost 31000 weather "example query" 


Here are two example queries from which to choose. They are formatted to be used with the simpleclient.

REST Access Example:
"select t.* from (call weather.invoke(action=>'GET', endpoint=>querystring('', '38.99,-77.02 39.70,-104.80 47.6,-122.30' as listLatLon, 'time-series' as product, '2004-01-01T00:00:00' as \"begin\", '2013-04-20T00:00:00' as \"end\", 'maxt' as maxt, 'mint' as mint) )) w, XMLTABLE('/dwml/data/location' passing w.result columns \"location-key\" string, lattitude string path 'point/@latitude', longitude string path 'point/@longitude') t"

SOAP11 RPC Access Example:
"select xmlserialize(document w.result as string) from (call weather.invoke(action=>'http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl#LatLonListZipCode', endpoint=>'http://www.weather.gov/forecasts/xml/SOAP_server/ndfdXMLserver.php', binding=>'SOAP11', request=>'<ns1:LatLonListZipCode xmlns:soapenv=\"http://schemas.xmlsoap.org/soap/envelope/\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" soapenv:encodingStyle=\"http://schemas.xmlsoap.org/soap/encoding/\" xmlns:ns1=\"http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl\"> <zipCodeList xsi:type=\"ns2:zipCodeListType\" xmlns:ns2=\"http://www.weather.gov/forecasts/xml/DWMLgen/schema/DWML.xsd\">63303</zipCodeList> </ns1:LatLonListZipCode>')) as w"


==== Using SQuirreL SQL ====

3) Create a new alias with these properties:
   * URL in this form: jdbc:teiid:weather@mm://localhost:31000
   * Driver: teiid-client.jar (reference the EDS install directory)
   * Class name: org.teiid.jdbc.TeiidDriver

4) Cut and paste the queries listed below into SQuirreL SQL's SQL frame and
   run them. 

REST Access Example:
select t.* from 
	(call weather.invoke(action=>'GET', 
		endpoint=>querystring('', '38.99,-77.02 39.70,-104.80 47.6,-122.30' as listLatLon, 
			'time-series' as product, '2004-01-01T00:00:00' as "begin", 
			'2013-04-20T00:00:00' as "end", 'maxt' as maxt, 'mint' as  mint)
	)) w, 
	XMLTABLE('/dwml/data/location' passing w.result 
		columns "location-key" string, lattitude string path 'point/@latitude', 
			longitude string path 'point/@longitude') t


SOAP11 RPC Access Example:
select xmlserialize(document w.result as string) from 
	(call weather.invoke(action=>'http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl#LatLonListZipCode', 
		endpoint=>'http://www.weather.gov/forecasts/xml/SOAP_server/ndfdXMLserver.php',
		binding=>'SOAP11',
		request=>'
		<ns1:LatLonListZipCode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
			xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
			xmlns:ns1="http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl">
			<zipCodeList xsi:type="ns2:zipCodeListType" xmlns:ns2="http://www.weather.gov/forecasts/xml/DWMLgen/schema/DWML.xsd">63303</zipCodeList>
		</ns1:LatLonListZipCode>')) as w

================ The Sample Queries Emplained ================

1. REST access of the default endpoint augmented by a query string.
   The query string is formed with the querystring function, which
   ensures proper encoding of the name/value pairs. The invoke
   procedure has a return parameter, called result that contains the
   XML value of the result document. This document is then fed into
   the XMLTABLE function to extract row values. Note that the default
   invocation binding has been set in the vdb xml to HTTP, which is
   the proper setting for REST. 


2. SOAP11 RPC call providing all of the parameter values for the
   invoke procedure. With a SOAP invocation, the action is used to
   convey the SOAPAction header value if needed. Also note the use of
   the endpoint here with an absolute URL, which will be used instead
   of the default on the datasource.

(See the DatabaseMetadata on the invoke procedure for a full description of the parameters.)