DBQueryOnInput

The DBQueryOnInput component is used to execute different SQL statements with each request on a configured database. The SQL to be executed is not configured in the CPS and is taken from the input message. In other DB components, the component is configured with predefined SQL statement(s) in the CPS and some or all of these statements are executed for all requests.

Points to note

• Only one query can be processed per message. If multiple queries have to be processed, use XMLSplitter to split the message into multiple messages each containing a single query.
• It is recommended NOT to use JDBC-ODBC Bridge driver to connect to any RDBMS in a production environment. Please, use a commercial JDBC driver instead.
• The JDBC drivers or the resources must be directly added onto the JDBC system lib and not as resource to the DBQueryOnInput component itself. To add JDBC drivers to DBQueryOnInput component, please refer to Adding Resources to a Microservice section.

Configuration

Managed Connection Factory Panel

The connection details are configured in the first panel, Managed Connection Factory (MCF). Figure 1 illustrates the panel with expert properties view enabled.

Connection Properties

Use Connection Details From Input

Parameters to create the connection can be specified in the input message when this property is set to true. If this property is selected the validation errors in the managed connection factory panel of the CPS are treated as warnings. So user can bypass this step without giving valid configuration and complete the configuration of the component. If valid properties are not provided even in the input message exception will be thrown at runtime.

Database Configuration

Click the Database Configuration ellipsis button to launch the Database Configuration editor as shown in the figure above, where details of the database to which the component should connect are configured.

Password Encryption Configuration

Enables use of custom keys and algorithms to encrypt passwords.

Refer to the Custom Encryption of Passwords section in the Common Configurations page for details.

Component Configuration

Database

This property determines the vendor of the database to which the component has to connect.

1. The vendor name is marked in red color if the default JDBC driver class is not present in component's classpath.
2. Even if a particular database vendor name is not present in the drop-down list, the component can still connect to the database.
3. If a vendor name is specified in the drop-down list, it only means that vendor-specific handling is done.
   Example: vendor-specific handling for data types, naming conventions etc
4. To connect to a database from a vendor whose name is not specified in the drop-down list, select Other and provide the correct values for Driver and JDBC URL.

Driver

The driver class name that should be used to connect to the database. On selecting the required value for Database, driver values are populated with the standard value (This can be changed to required value based on the driver being used).

The jar file(s) that are part of JDBC client libraries for selected vendor has to be added as resources to JDBC system library.

URL

This property determines the location at which the required database is running. On selecting the required database, URL value is populated with the standard value (This can be changed to required values based on the driver being used).
Note: The populated values have placeholders which have to be replaced to point to correct database location. In the figure above "<hostname>" may be replaced with "localhost" if the database is running on local machine.

Username

This property determines the username that should be used to connect to the database.

Password

This property determines the password for the specified user.

Connection ping sql

A SQL statement which is guaranteed to execute without exception, except when connection to the database is lost. when a SQL exception occurs on executing a configured query, this SQL statement is executed. If execution of this SQL statement fails as well, then it is assumed that connection to the database is lost and appropriate configured action (say, reconnect) is taken.
Example: select * from dual for Oracle, select 1 for MS SQL

Connection Properties

Any driver-specific connection properties which may have to be passed while creating a JDBC connection should be provided against Connection Properties. For example, fixedString=true uses FIXED CHAR semantics for string values in Oracle.

• Please refer to the documentation of the driver that is being used for valid name-values for connection properties.
• Refer to the following link http://java.sun.com/j2se/1.5.0/docs/api/java/util/Properties.html#load(java.io.InputStream) for details on the properties file.

Auto Commit (Y/N)

Commit mode that should be used by the JDBC connection.

• yes - Any transactions (queries executed) are automatically and implicitly committed to the database. This is done even before the response is generated.
• no - Any transactions (queries executed) are committed after the request is processed successfully and the response is generated, but before the message is sent out of the component.

Connection Pool Params

Defines the connection pool settings for the component.

Refer to the Connection Pool Params section in the Common Configurations page for details.

Advanced Settings

Query timeout

Time, in seconds (>= 0), after which an exception is thrown if the query execution is not complete. For example, For the default value "60", if a query to database does not return within 60 seconds, then an exception is thrown and query execution is stopped.

Enable JDBC Driver Logging

Value yes implies that logging at the driver level should be enabled. This is used as a debugging option.

Login Timeout

Time, in seconds (>= 0), after which an exception is thrown if the login process is not complete. 

Interaction Configurations Panel

Business logic configuration details are configured in the second panel, Interaction Configurations panel. The figure below illustrates the panel with the expert properties view enabled.

Attributes

Auto Commit For Test

This property determines whether auto-commit should be enabled when testing from the CPS.

• yes - Any transactions (queries executed) are automatically committed to the database while testing. Performed transactions will have to manually undone.
• no - Any transactions (queries executed) are rolled back at the completion of test.

This property will override the value provided for property Auto Commit (Y/N) in the MCF panel.

Pre Processing XSL Configuration

Pre Processing XSL configuration can be used to transform request message before processing it. Click the small button against the property to configure the properties.

Refer to the Pre/Post Processing XSL Configuration section under Common Configurations topic for details regarding XSL configuration. The properties comprising this XSL configuration are:

• Provide XSL
• XSLT Engine
• Transformation source data
• Set transformation result as

Post Processing XSL Configuration

Post Processing XSL configuration can be used to transform response message before sending it to the output port.

As mentioned in the above section, refer to the Pre/Post Processing XSL Configuration section under the Common Configurations topic for details regarding XSL configuration.

Process Message Based on Property

The property helps components to skip certain messages from processing.

Refer the Process Message Based On a Property section under the Common Configurations topic.

Generate columns as

This property determines how any data returned (result set) by the component is represented in the output message. Result sets are tabular data returned for a database query. Select queries always return result sets and stored procedures may return result sets based on the type of variables returned by stored procedures.

TAGS

Column names of result set will be generated as XML elements in the output message.

The schema on the output port is not completely defined in this case as the schema varies depending on the query sent in input.

However, since the column names are generated as elements, if the columns in result are known and same for all inputs of business scenario, a schema for the output can be generated by defining rowType element type manually and loaded into Fiorano Mapper.

This option allows direct mappings in XSLT.

ATTRIBUTES

Column names of result set will be generated as value of attribute name of element column in the output message.

The output structure is completely defined and will not vary based on the input.

Defining mappings in XSLT using this option will require writing some user-defined XSL to loop through all columns in a row and map only data from column element whose attribute name contains required column name to the required output element.

Output XSD

To configure the output XSD, click the ellipsis button.

Refer to the Schema Editor section under the Common Configurations topic for details.

Enable CSV Output

When Enable CSV Output property is selected, the output of the queries will be in CSV format.

This property is supported when CSV output is required only in the instance are either Select queries or Stored Procedure queries which return single ResultSet.

After enabling this property, the below parameters becomes editable. These separators, which act as punctuation in the CSV output, can be customized by providing the respective values:

Field Separator: The value of Column Separator to be used in CSV output.
Line Separator: The value of Row Separator to be used in CSV output.
Wrap Character: The specified character is used to wrap each field that is returned when a query is processed. This Field is not mandatory.

When separators used are:

• Field separator → ;
• Line separator → ,
• Wrap Character → "

then the output will be like:

"13579008642";"john";"hyd","124";"joseph";"bang",

Escape Character: This field is not mandatory. If the wrap character mentioned in CPS turn up in the values returned from the DB, then those characters will be prefixed by escape character specified. If no character is specified, no action will be taken.

Single Batch Mode

This option determines whether the component should send entire result of a query as a single message or as multiple messages.

• yes - Complete result of the query from input request is sent out as a single message. If the result set returned is huge then the component can run into memory problems and stop. When this value is selected, property Batch Size is hidden.
• no - Result of query from input is split and sent out as multiple messages. Number of rows from result to be included in each output message is determined by property Batch Size. When this value is selected, property Batch Size is shown.

Example: If a query returns 100 rows, and the batch size is set to 10 then 10 outputs will be generated each contains 10 rows.

Batch Size

This property is visible when the property Single Batch Mode is disbled. The property determines the number of units of result an output message contains.
Each row in a result set (typically result of a select query) or an update result (result of update, delete, insert operations) is treated as unit of result.

Example: Consider a stored procedure that returns a result of select query followed by three update queries and another select query. Assume first select return 18 rows and second query returns 11 rows. If Single Batch Mode is set as no and Batch Size is set as 10 then there will be four output messages.

• firstmessage: first 10 rows from first query
• secondmessage: remaining 8 rows from first query and 2^nd update query results.
• thirdmessage: 3^rd update query result and first 9 rows of second select query.
• fourthmessage: remaining two rows from second query.

For the Expert Properties Validate Input, Cleanup resources, Target Namespace and Monitoring configuration, please refer the respective sections in the Common Configurations page. Refer "Configuring Components for Message Encryption" section in the same page for the property Elements to Decrypt.

Input and output

Input

Input schema for the component is as shown below.

Input message contains only one element query whose value contains the query that has to be executed.

When the property Use Connection details from input is chosen, an additional element ConnectionFactorySettings is added to the input schema, as shown in the figure. Properties that are used to create the connection are present under this element.

Output

Output schema for the component depends on the value configured for property Generate columns as in Interaction Configurations panel. Output schemas based on the property value are shown in Figures 5 and 9 and sample inputs for them are shown in Figures 4 and 8.

Functional Demonstration

Scenario 1

Execution of a select query with ATTRIBUTES as the mode of column generation.
Start mckoiDB present in %FIORANO_HOME%\esb\samples\mckoiDB by executing CreateMckoiDB.bat and RunMckoi.bat files. Configure the DBQueryOnInput component as shown in Figures 15 and 16.

Use feeder and display components (shown in Figure 17) to create a flow to send sample input and check the response respectively.

Use feeder and display components to create a flow to send sample input and check the response respectively.

Send input message from the feeder, shown in the figure below.

Notice the output as shown below.

Scenario 2

Use same connection configurations as described in scenario 1 and change the Interactions Configuration.

Repeat the test as described in scenario 1 with the same input and observe the output.

Useful Tips

• Only one query can be processed per message. If multiple queries have to be processed, use XMLSplitter to split the message into multiple messages each containing a single query.
• It is recommended NOT to use JDBC-ODBC Bridge driver to connect to any RDBMS in a production environment. Please, use a commercial JDBC driver instead.
• The JDBC drivers or the resources must be directly added onto the JDBC system lib and not as resource to the DBQueryOnInput component itself. To add JDBC drivers to DBQueryOnInput component, please refer to Adding Resources to a Microservice section.