Difference between revisions of "DBOInsert"
(→{{GVESB}} configuration) |
|||
| Line 22: | Line 22: | ||
* [[statement]] | * [[statement]] | ||
| − | + | The following table shows the DBOInsert attributes: | |
| − | + | {|class="gvtable" | |
| − | + | ! 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 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 | ||
| + | |- | ||
| + | | 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. | ||
| + | |- | ||
| + | | 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. | ||
| + | |- | ||
| + | | output-data || optional || The default is the value of @name-Output. | ||
| + | |} | ||
For example: | For example: | ||
Revision as of 11:16, 2 April 2012
Description
The DBOInsert element represents the DBO optimized for insert operations.
GreenVulcano® ESB configuration
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:
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 name |
| force-mode | optional | 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 | false): Tell 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. |
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>
