Difference between revisions of "DBOInsert"

From GreenVulcano Wiki
Jump to: navigation, search
(Created page with "==Description== The DBOInsert element represents the DBO optimized for insert operations. =={{GVESB}} configuration== thumb|DBOInsert with VulCon DBOInse...")
 
({{GVESB}} configuration)
Line 5: Line 5:
 
=={{GVESB}} configuration==
 
=={{GVESB}} configuration==
 
[[File:DBOInsert.jpg|thumb|DBOInsert with VulCon]]
 
[[File:DBOInsert.jpg|thumb|DBOInsert with VulCon]]
DBOInsert might contain the following sub-elements:
+
DBOInsert allows you to make changes to the database.
 +
 
 +
Each statement is identified by the id.
 +
 
 +
Actions can be defined in two ways:
 +
Single execution of a statement
 +
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.
 +
 
 +
Might contain the following sub-elements:
 
* [[Description]]
 
* [[Description]]
 
* [[DHVariables]]
 
* [[DHVariables]]

Revision as of 13:30, 30 March 2012

Description

The DBOInsert element represents the DBO optimized for insert operations.

GreenVulcano® ESB configuration

DBOInsert with VulCon

DBOInsert allows you to make changes to the database.

Each statement is identified by the id.

Actions can be defined in two ways: Single execution of a statement 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.

Might contain the following sub-elements:

Its attributes are:

  • type: dbo
  • class: it.greenvulcano.gvesb.datahandling.dbo.DBOInsert
  • name
  • transformation
  • force-mode (caller|xml2db): Force mode of the DBO, can be used in DBOBuilder whit more heterogeneous DBO.
    Mode:
    caller - inherit the mode of the caller
    xml2db - data entry mode
  • jdbc-connection-name: DataSource JNDI name.
    Override connection defined in DBOBuilder.
  • ignore-input (true|false): Tell the engine do not use the input data.
  • input-data: The default is the value of @name-Input.
    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.

For example:

<?xml version="1.0" encoding="UTF-8"?>
 <DBOBuilder class="it.greenvulcano.gvesb.datahandling.dbobuilder.DBOBuilder" jdbc-connection-name="ds.gv_cama" 
            name="InsertCampaignData" type="dbobuilder">
       <DBOInsert class="it.greenvulcano.gvesb.datahandling.dbo.DBOInsert" name="InsertCampaingDataInsert"
                  transformation="InsertCampaignDataSeq" type="dbo">
               <statement id="0" type="insert">
                   insert into CAMA.MESSAGES(......) values(?,?,?,?,?,?,?,sysdate,sysdate,?,?,?)
               </statement>
       </DBOInsert>
 </DBOBuilder>