Selecting records from Database Connector and storing them in a file location with and without using Loops in Mulesoft

1. MULESOFT CONNECTORS

2. CONTENTS:
• MuleSoft.
• AnyPoint studio.
• Selecting data from the database and store each record individually.

3. MULESOFT
• Mule, the runtime engine of Anypoint Platform, is a lightweight Java-based enterprise service bus (ESB) and integration platform
that allows developers to connect applications together quickly and easily, enabling them to exchange data.
•It enables easy integration of existing systems, regardless of the different technologies that the applications use, including JMS,
Web Services, JDBC, HTTP, and more.
• Mule has powerful capabilities that include:
 Service creation and hosting
 Service mediation
 Message routing
 Data transformation

4. ANYPOINT STUDIO
Accelerate developer productivity with a single graphical environment for SOA, SaaS, APIs and data integration, then deploy your
applications with one click to the Mule runtime, on-premises or in the cloud.
 Design and implement APIs with unified tooling.
 Build, edit, document and debug integrations graphically or in XML.
 Simplify data mapping and transformation.
 Complete support for the entire build-to-deploy process.
 Jumpstart your integrations with pre-built components.

5. Selecting data from the database and store each record individually
 The main aim of the use case is to when ever http service is hit the database need to select all the records in
the table and store them in a file with each record individually using for each loop.
 The full flow of the use case is given below.

6. Steps to be followed:
1)Starting with HTTP configure it. 2)Select the port no , for example 8081.

7. 3)Coming to database make sure that configuration,
operation and query are selected.
4) Provide the host, port, instance, user and
password and also add the jar file to it.

8. 5) Here the logger displays the number of records
fetched from the database.
6) Finally the data fetched from database is individually
stored record wise in the path provided to the file
collector.

9. 7) Finally right click on the project go to run as mule application and run it.

10. The same use case can also be done in another way by using the message chunk splitter.
 The flow is given bellow:

11.  This flow also have same functionality expect the message chuck splitter where we need to provide the message size to it.

12.  Now again right click on project go to run as mule application.

13. Any Queries ?