Difference between revisions of "DBOInsert"
(→{{GVESB}} configuration) |
|||
| Line 39: | Line 39: | ||
| output-data || optional || The default is the value of @name-Output. | | output-data || optional || The default is the value of @name-Output. | ||
|} | |} | ||
| + | <div class="version_ge3.4.0.6"> | ||
| + | {|class="gvtable" | ||
| + | ! Attribute !! Type !! Description | ||
| + | |- | ||
| + | | autogenerate-keys || optional || Tell the engine to handle auto generated keys at runtime (ex. autoincrement primary key fields). Default to false. | ||
| + | |} | ||
| + | </div> | ||
For example: | For example: | ||
Revision as of 13:47, 31 December 2014
Description
The DBOInsert element represents the DBO optimized for insert operations.
GreenVulcano® ESB configuration
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
- 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:
| Attribute | Type | Description |
|---|---|---|
| type | fixed | This attribute must assume the value dbo |
| class | fixed | This attribute must assume the value it.greenvulcano.gvesb.datahandling.dbo.DBOInsert |
| name | required | DBOInsert 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. Mode: caller - inherit the mode of the caller xml2db - data entry mode |
| jdbc-connection-name | optional | DataSource JNDI name. Override connection defined in DBOBuilder. |
| 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. Can be set as the @output-data of a preceding DBO to use its output as input. |
| output-data | optional | The default is the value of @name-Output. |
| Attribute | Type | Description |
|---|---|---|
| autogenerate-keys | optional | Tell the engine to handle auto generated keys at runtime (ex. autoincrement primary key fields). Default to false. |
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>
Might contain the following sub-elements:
