DBOInsert - Revision history

M.deluca: /* {{GVESB}} configuration */

2016-01-26T17:23:04Z

‎{{GVESB}} configuration

2015-01-03T13:18:19Z

2015-01-03T10:02:56Z

2015-01-03T09:49:20Z

2015-01-02T14:29:18Z

2014-12-31T13:47:21Z

2012-11-12T12:10:21Z

‎{{GVESB}} configuration

2012-04-02T11:56:05Z

‎{{GVESB}} configuration

2012-04-02T11:19:02Z

‎{{GVESB}} configuration

2012-04-02T11:16:29Z

@@ Line 140: / Line 140: @@
 </xsl:stylesheet>
 </syntaxhighlight>
 Might contain the following sub-elements:

@@ Line 53: / Line 53: @@
 </div>
-For example, the following configuration:
+For example, given the following table:
-<syntaxhighlight lang="XML">
+<syntaxhighlight lang="SQL">
-<DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"
+CREATE TABLE "TEST_GV"."TEST_TABLE_A" (
-            jdbc-connection-name="ds.test" name="Insert" type="dbobuilder">
+  "C1" VARCHAR2(50 CHAR),
-    <DBOInsert class="it.greenvulcano.gvesb.datahandling.dbo.DBOInsert"
+  "C2" VARCHAR2(20 CHAR),
-               name="Insert" transformation="Insert" type="dbo">
+  "C3" NUMBER,
-        <statement id="0" type="insert">insert into TEST_TABLE_A (C1, C2, C3, C4, C5, C6, C7)
+  "C4" NUMBER(10,3),
-values (?, ?, ?, ?, ?, ?, ?)</statement>
+  "C5" NUMBER(5,4),
-    </DBOInsert>
+  "C6" DATE,
-</DBOBuilder>
+  "C7" TIMESTAMP (6)
 </syntaxhighlight>
 using the following input XML:
@@ Line 76: / Line 77: @@
 </ser:load>
 </syntaxhighlight>
-and the following XSL transformation:
+the following DBOInsert can load records into the table:
 <syntaxhighlight lang="XML">
 <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="xsl fs java gvt" version="2.0"
@@ Line 127: / Line 139: @@
      </xsl:template>
 </xsl:stylesheet>
 </syntaxhighlight>

@@ Line 47: / Line 47: @@
 | autogenerate-keys || optional || Tell the engine to handle auto generated keys at runtime (ex. autoincrement primary key fields). Default to false.
 |}
 </div>

@@ Line 49: / Line 49: @@
 </div>
-For example:
+For example, the following configuration:
-<syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?>
+<syntaxhighlight lang="XML">
- <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" jdbc-connection-name="ds.gv_cama"
+<DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder"
-            name="InsertCampaignData" type="dbobuilder">
+            jdbc-connection-name="ds.test" name="Insert" type="dbobuilder">
-       <DBOInsert class="it.greenvulcano.gvesb.datahandling.dbo.DBOInsert" name="InsertCampaingDataInsert"
+    <DBOInsert class="it.greenvulcano.gvesb.datahandling.dbo.DBOInsert"
-                  transformation="InsertCampaignDataSeq" type="dbo">
+               name="Insert" transformation="Insert" type="dbo">
-               <statement id="0" type="insert">
+        <statement id="0" type="insert">insert into TEST_TABLE_A (C1, C2, C3, C4, C5, C6, C7)
-                   insert into CAMA.MESSAGES(......) values(?,?,?,?,?,?,?,sysdate,sysdate,?,?,?)
+values (?, ?, ?, ?, ?, ?, ?)</statement>
-               </statement>
+    </DBOInsert>
-       </DBOInsert>
+</DBOBuilder>
- </DBOBuilder>
+</syntaxhighlight>
 </syntaxhighlight>

← Older revision		Revision as of 14:29, 2 January 2015
Line 16:		Line 16:

	In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.		In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.
		+
		+	It is used by [[DBOBuilder]].

	The following table shows the DBOInsert attributes:		The following table shows the DBOInsert attributes:

@@ Line 39: / Line 39: @@
 | output-data || optional || The default is the value of @name-Output.
 |}
 For example:

@@ Line 27: / Line 27: @@
 | name || required || DBOInsert name
 |-
-| transformation || optional || Transformation name
+| transformation || optional || Transformation to be applied on the input data to obtain the internal XML commands.
 |-
 | force-mode || optional || (caller or xml2db): Force mode of the DBO, can be used in [[DBOBuilder]] whit more heterogeneous DBO. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode

@@ Line 29: / Line 29: @@
 | transformation || optional || Transformation name
 |-
-| force-mode || optional || (caller|xml2db): Force mode of the DBO, can be used in [[DBOBuilder]] whit more heterogeneous DBO. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode
+| force-mode || optional || (caller or xml2db): Force mode of the DBO, can be used in [[DBOBuilder]] whit more heterogeneous DBO. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode
 |-
 | jdbc-connection-name || optional || DataSource JNDI name. <br/>  Override connection defined in [[DBOBuilder]].
 |-
-| ignore-input || optional || (true|false):   Tell the engine do not use the input data.
+| ignore-input || optional || (true or false):  Tells the engine do not use the input data.
 |-
 | input-data || optional || The default is the value of @name-Input.<br/>  Can be set as the @output-data of a preceding DBO to use its output as input.

@@ Line 5: / Line 5: @@
 =={{GVESB}} configuration==
 [[File:DBOInsert.jpg|thumb|DBOInsert with VulCon]]
-DBOInsert allows you to make changes to the database.
+DBOInsert allows you to make insert data into the database.
 Each statement is identified by the id.
 Actions can be defined in two ways:
-Single execution of a statement
+* Single execution of a statement
-complex execution guided by XML
+* Complex execution guided by XML
 In the first modality any input is ignored and the code executes the first statement configured.
 In the second mode, the input XML (or its transformation) must contain the command (row) valid with all parameters (COL) required by the statement.
 The following table shows the DBOInsert attributes:
@@ Line 57: / Line 52: @@
   </DBOBuilder>
 </syntaxhighlight>

@@ Line 22: / Line 22: @@
 * [[statement]]
-Its attributes are:
+The following table shows the DBOInsert attributes:
+{|class="gvtable"
-* ''type'': dbo
+! Attribute !! Type !! Description
-* ''class'': it.greenvulcano.gvesb.datahandling.dbo.DBOInsert
+|-
-* ''name''
+| type || fixed || This attribute must assume the value '''dbo'''
-* ''transformation''
+|-
-* ''force-mode'' (caller|xml2db): Force mode of the DBO, can be used in [[DBOBuilder]] whit more heterogeneous DBO. <br/> Mode:<br/> caller - inherit the mode of the caller<br/> xml2db - data entry mode
+| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.datahandling.dbo.DBOInsert'''
-* ''jdbc-connection-name'':  DataSource JNDI name. <br/>  Override connection defined in [[DBOBuilder]].
+|-
-* ''ignore-input'' (true|false):   Tell the engine do not use the input data.
+| name || required || DBOInsert name
-* ''input-data'': The default is the value of @name-Input.<br/>  Can be set as the @output-data of a preceding DBO to use its output as input.
+|-
-* ''output-data'':  The default is the value of @name-Output.
+| transformation || optional || Transformation name
 For example: