Difference between revisions of "DBOThreadSelect"

From GreenVulcano Wiki
Jump to: navigation, search
({{GVESB}} configuration)
Line 20: Line 20:
 
* ''transformation''
 
* ''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/> db2xml - data extraction mode
 
* ''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/> db2xml - data extraction mode
* ''jdbc-connection-name'':  DataSource JNDI name. <br/>  Override connection defined in DBOBuilder.
+
* ''jdbc-connection-name'':  DataSource JNDI name. <br/>  Overrides the connection defined in [[DBOBuilder]].
 
* ''ignore-input'' (true|false):  Tell the engine do not use the input data.
 
* ''ignore-input'' (true|false):  Tell the engine do not use the input data.
 
* ''output-data'':  The default is the value of @name-Output.
 
* ''output-data'':  The default is the value of @name-Output.

Revision as of 16:20, 28 March 2012

Description

The DBOThreadSelect element represents the DBO optimized for select operations.

Every statement is execute in a separate thread, then the results are merged before making the transformation.

GreenVulcano® ESB configuration

DBOThreadSelect might contain the following sub-elements:


Its attributes are:

  • type: dbo
  • class: it.greenvulcano.gvesb.datahandling.dbo.DBOThreadSelect
  • 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
    db2xml - data extraction mode
  • jdbc-connection-name: DataSource JNDI name.
    Overrides the connection defined in DBOBuilder.
  • ignore-input (true|false): Tell the engine do not use the input data.
  • output-data: The default is the value of @name-Output.