DataHandler - Revision history

Anonymous at 10:43, 2 April 2012

2012-04-02T10:43:16Z

G.dimaio at 15:32, 1 April 2012

2012-04-01T15:32:30Z

Anonymous: /* {{GVESB}} Configuration */

2012-03-30T10:28:16Z

‎{{GVESB}} Configuration

Anonymous: /* Data flow */

2012-03-30T09:57:47Z

‎Data flow

Anonymous: /* DataHandler vs JDBC */

2012-03-30T09:53:10Z

‎DataHandler vs JDBC

Anonymous: /* Data flow */

2012-03-30T09:51:47Z

‎Data flow

Anonymous: /* Data flow */

2012-03-30T09:34:13Z

‎Data flow

Anonymous: /* {{GVESB}} Configuration */

2012-03-30T09:20:27Z

‎{{GVESB}} Configuration

Anonymous: /* DataHandler vs JDBC */

2012-03-30T09:02:16Z

‎DataHandler vs JDBC

Anonymous: /* {{GVESB}} Configuration */

2012-03-30T08:59:10Z

‎{{GVESB}} Configuration

@@ Line 19: / Line 19: @@
 The basic language used for map transformation is XSLT 1.0. The package includes Xalan, but it is also possible to add others XSLT processors which implement XSLT 2.0.
 ===Data flow===
@@ Line 76: / Line 116: @@
 ::grouping-separator (thousands separator, default:  .)
-===DataHandler vs JDBC===
+The DataHandler elementary operations that may be combining in a service are represented by the [[DBOBuilder#DBO|DBOs]].

@@ Line 1: / Line 1: @@
 ==Description==
-[[File:datahandlerArchitecture.jpg|thumb|DataHandler Architecture]]The DataHandler is a component extremely performable and configurable, which deals with extraction, edition, insertion and deletion of data and execution of stored procedures/functions of one or more RDBMS using JDBC APIs. It is only available in the Enterprise version.
+[[File:datahandlerArchitecture.jpg|thumb|DataHandler Architecture]]The DataHandler is an extremely powerful and configurable component, which deals with extraction and modification of data and execution of stored procedures/functions on one or more RDBMS using JDBC APIs. It is only available in the Enterprise edition.
-This component works on XML defined by XSD. Through maps of transformation, the XML input is received and normalized into another XML, which defines the data types and values, necessary to perform operations on the database.
+This component is optimized to work with XML documents as input or output. Through transformation maps, the XML passed in is converted to an XML of commands, which defines data types and values, necessary to perform the update operations on the database.
-Thereafter, the DataHandler performs operations on the database configured for the service. Depending on the type of operation configured, the DataHandler returns an output consisting in a report that describes the operation result, and a XML which, through a transformation map, is converted into a second XML defined by one XSD.
+Depending on the type of operation configured, the DataHandler returns an output consisting of a report that describes the result of the operation, and a possible internal XML document that, through a transformation map, is converted into a specific XML document for the client.
 =={{GVESB}} Configuration==
@@ Line 34: / Line 34: @@
 <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
 <RowSet>
-     <data id="0" key_1="MGP" key_2="20120325" key_3="AUST" key_4="NORD">
+     <data id="0" key_1="ASTOR" key_2="20120325" key_3="ITA" key_4="HIVAL">
          <row id="0">
              <col format="yyyyMMdd HH:mm:ss" type="timestamp">20120325 00:00:00</col>

@@ Line 16: / Line 16: @@
 * Composition of select/update calls in SQL language for finding/changing data in the database.
-The language used for map transformation is XSLT 1.0.
+You might perform a call to DataHandler by include into your workflow configuration a [[dh-call]] plugin.
 ===Data flow===

@@ Line 21: / Line 21: @@
 [[File:DataHandlerFlow.jpg|thumb|DataHandler Data flow]]
 With DataHandler the flow of data might occur in two ways:
@@ Line 68: / Line 69: @@
 : For the timestamp type it can be defined the format attribute containing the conversion pattern  string <-> date/datehour/timestamp. There are used the same conventions as in SimpleDateFormat Java class. The default value is yyyyMMdd HH:mm:ss
-: For the  float type it can be defined the following attributes describing the conversion string <-> floating/fixed point
+: For the  float type will be used the same conventions of the DecimalFormat java class. It can be defined the following attributes describing the conversion string <-> floating/fixed point
-:*format  (conversion pattern, default: #,##0.###)
+::format  (conversion pattern, default: #,##0.###)
-:*decimal-separator  (decimal separator, default:  ,)
+::decimal-separator  (decimal separator, default:  ,)
-:*grouping-separator (thousands separator, default:  .)
+::grouping-separator (thousands separator, default:  .)
 ===DataHandler vs JDBC===

@@ Line 101: / Line 101: @@
 * The DH, using XA compliant JDBC connections, can operate on multiple databases in a single invocation.
 * The DataHandler during transformations of input/output data (before of insert/update/delete and after of select), can use the helpers presents in the XSL maps that allow to perform SQL queries or scripts JavaScript and its result can be used to enhance the input/output data:
-     Insert: XML with the city names -> database with numeric id => SQL retriever that maps name
+     Insert: XML with the city names
-                                    -> id for inserts/updates and id -> name for the select
+       -> database with numeric id => SQL retriever that maps name
 * The DataHandler can perform a series of parallel data extraction into tables, or with groupings, diferents, aggregate the partial results and send the aggregate to the DTE for an eventual data transformation.
 * The DataHandler can perform a series of data extraction (also from different databases) + XML transformation (different from each other) and then add the result (via XPath) into a single document to be returned to the caller.

@@ Line 20: / Line 20: @@
 ===Data flow===
-[[File:DataHandlerFlow.jpg|thumb|DataHandler Data flow]]With DataHandler the flow of data might occur in two ways:
+[[File:DataHandlerFlow.jpg|thumb|DataHandler Data flow]]
 * From XML to Database: valid for processes of data insertion and/or update
 * From Database to XML: for extracting processes.
 ===DataHandler vs JDBC===

@@ Line 11: / Line 11: @@
 =={{GVESB}} Configuration==
-The configuration of the Datahandler (DH) component occurs in three steps:
+The configuration of the Datahandler(DH) component occurs in three steps:
 * Definition of XSD in input and output of the service;
 * Definition of maps of conversion from the format defined in the XSD created and vice versa;
@@ Line 17: / Line 17: @@
 The language used for map transformation is XSLT 1.0.
 ===DataHandler vs JDBC===
@@ Line 29: / Line 37: @@
      where last_name = <nowiki>'@{{LAST_NAME}}'</nowiki>
      <nowiki>decode{{@{{CITY}}::NULL:: ::and city='@{{CITY}}'}}</nowiki><br/>
-     If the parameter CITY is not populated the corresponding  where clause
+     If the parameter CITY is not populated the corresponding where clause
      will not be included in the statement

@@ Line 32: / Line 32: @@
      will not be included in the statement
-[[File:datahandlerVSjdbc2.jpg|thumb|DataHandler vs JDBC]]* The DataHandler can perform multiple operations depending on data:
+* The DataHandler can perform multiple operations depending on data:
 ** deleting a record on Table A -> removal of records matching the table B
 ** inserting a record on Table A -> insert a record equivalent of an audit table C
@@ Line 41: / Line 41: @@
 ** validation procedure (call statement)
 ** extraction results validation (select statement)
 * The DataHandler can operate on multiple tables in a single invocation.
 * The DH, using XA compliant JDBC connections, can operate on multiple databases in a single invocation.