The document discusses Mule's new JDBC component that allows connecting to relational databases using a single interface. It provides examples of how to perform SQL operations like select, insert, update, delete using parameterized, dynamic and template queries. It also demonstrates how to call stored procedures. Configuration of the database connector and different query types like parameterized, dynamic and from template are explained.

1. DATABASE INTEGRATE
WITH MULE

2. MULE HAS INTRODUCED IT’S NEW JDBC COMPONENT
RECENTLY WHICH ALLOW USTO CONNECT ALMOST WITH
ALMOST ANY JAVA DATABASE CONNECTIVITY (JDBC)
RELATIONAL DATABASE USING A SINGLE INTERFACE FOR
EVERY CASE.
IT ALSO RUN DIVERSE SQL OPERATIONS ON OUR DATABASE,
INCLUDING SELECT, INSERT, UPDATE, DELETE, AND EVEN
STORED PROCEDURES.
SOWE CAN SAYTHAT ALMOST ALLTYPE OF DB OPERATION
CAN BE DONE HERE SMOOTHLY WITHTHIS NEW COMPONENT

3. We I will give you few small demo here on how to operate with this new
component.
Let’s consider we have the following simple Mule flow :-
As you can see we have used the new DB connecter to fetch the Data from
Database and display the data in an XML format in logger

4. The new Database component is of 3 query type :
• Parameterized
• Dynamic
• FromTemplate
For more info.. Please visit :-
http://www.mulesoft.org/documentation/display/current/Database+C
onnector

5. Configuring the Database
For configuring the database, we need to configure the global database connector
with your existing DB as follows :-
<db:generic-config name="Generic_Database_Configuration"
url="jdbc:sqlserver://ANIRBAN-
PCSQLEXPRESS:1433;databaseName=Anirban;user=sa;password=******"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
doc:name="Generic DatabaseConfiguration" />
The above code is a sample of connecting Mule with SQL server database.

6. Now there are various ways to use this new component….
I will show you small examples here

7. Configuring a From-Template Query
You can use a template to pre-define an SQL query that you can
use and reuse in your application's flows.
It enables you to define a query statement once, in a global element
in your application (globalTemplate Query ), then reuse the query
multiple times whenever required
<db:template-query name=“simpleQuery" doc:name="Template Query">
<db:parameterized-query >select * from table1 </db:parameterized-query>
</db:template-query>
<db:select config-ref="Generic_Database_Configuration"
doc:name="Database">
<db:template-query-ref name="withoutParameter"/>
</db:select>
And referring the template in the Mule flow as follows :-

8. Dynamic query :
Mule replaces all MEL expressions in the query with the result of the
expression evaluation, then sends the result to the database. As such, you are
responsible for making sure that any string in your query statement is
interpretable by the database (i.e. quoting strings, data formatting, etc.)
<db:select config-ref="Generic_Database_Configuration" doc:name="Database">
<db:dynamic-query><![CDATA[select * from table1]]>
</db:dynamic-query>
</db:select>
Above example shows the use of dynamic query

9. Parameterized query :
Mule replaces all Mule Expression Language (MEL) expressions inside a query
with "?" to create a prepared statement, then evaluates the MEL expressions
using the current event so as to obtain the value for each parameter.
<db:select config-ref="Generic_Database_Configuration" doc:name="Database">
<db:parameterized-query><![CDATA[select * from table1 where
Id=23]]></db:parameterized-query>
</db:select>
Above example shows the use of Parameterized query

10. Stored procedure:
This new jdbc component can also execute stored procedure as follows :-
<db:stored-procedure config-ref="Generic_Database_Configuration">
<db:parameterized-query>{ call selectData() }</db:parameterized-query>
</db:stored-procedure>
Above example shows the use of stored procedure where selectData() is a stored
procedure