Create A Data Service With The WSO2 Data Services Eclipse Plugin

Archived Content
This article is provided for historical perspective only, and may not reflect current conditions. Please refer to relevant product page for more up-to-date product information and resources.
  • By Saminda Wijeratne
  • 22 Sep, 2008


So you are thinking of creating a data service from the Eclipse plugin? Well its as easy as singing a lullaby (unless you have something against lullabies or babies naturally hate you – in which case luckily, as non of it has any relevance for data services). This tutorial is suitable for any user who has slight knowledge of what a service is and has worked with the new Data service solution.

A Background Check - Data Services Basics (just in case)

First, make sure you understand what a dataservice is. In simple terms, a data service is the exposure of data as a Web service. I‘m sure you know what data is or otherwise you wouldn‘t be reading this tutorial. But you might want to know the type of data is supported by this plugin. It supports 4 types of data that is commonly known to most users:

  • Relational Databases
  • Excel files
  • CSV files
  • and of course JNDI data sources.

Concept of Building a Data Service

  1. We can have one or more of such data sources in a Web service. We just define those in our data service and viola!, your data service knows about the sources.

  2. But still, a data service needs to know which data needs to be extracted from those sources. Or rather, what data should be retrieved, depending upon different conditions. Thus comes the concept of a query in a data service. You can have several different types of data retrieved from a single data source you defined. Which means you can have several queries for a single data source. Thus a query defines how to retrieve only the relevant data from a given data source. Sounds greek? Doesn‘t matter, wait until we actually start the tutorial.

  3. OK hope you‘re still with me on this. So the data service knows about the sources, and how to retreive relevant data. Non of these are important for the end user, as once the data service is deployed it will all happens behind the screen.

  4. So how does the user know, which method in a service needs to be invoked, in order  to get data he/she wants? This is where “operations” come in to play. An operation in a data service, is what is exposed (or rather shown) to the end user. It is defined as what query to run when it is called, and what parameters user needs to provide for a successful execution of the query.

That's it. Now you know the basics, on how to build a data service. Let's try them using the plugin.


  1. You need Eclipse WTP 2.0 or later
  2. Download the plugin Data services plugin 1.0.1
  3. You can download the WSO2 Data Services solution from here.
  4. Prerequisites for the tutorial

    Tutorial uses MySQL 5.0 or later version database server

    I'm using the popular MySQL sample database named sakila to create the data service. You may find downloadable scripts to create this database in mysql from here.

  5. You can download the resulting sample data service for this tutorial from here.


    Don't know how to setup the data services plugin?

    Just copy the plugin jar file to the plugins folder of Eclipse. (Or in the case of Eclipse Ganymede, you can just copy it to the dropins folder instead, that is located in the same level as the plugins folder)


In this tutorial, I will demonstrate creating a Web service that exposes data stored in a relational database.

Creating a RDBMS Data Service

  1. First lets start the Eclipse WTP IDE. You may or may not have projects currently loaded on your workspace.
  2. Eclipse WTP IDE Instance

  3. To create a new data service:
  4. Press Ctrl + N


    File → New → Other…

    This will show the new dialog box

    New Wizard

  5. In the New Wizard dialog select WSO2 Data Services Creation Wizard and click Next. This will show the first page of the data services wizard. 
  6. Dataservice Plugin Wizard

    This page determines what you want to do. i.e. Create or modify or just deploy a dataservice. In our case we will be creating a dataservice now.

  7. Select Create a new data service from scratch among the 3 options at the top.
  8.  dataservice options

  9. Then, we need to specify where we are going to deploy the data service. Currently, we have the options of deploying a data service in the data services solution or later versions of WSAS 2.3. If you want to deploy your data service on to a running instance of these servers accessible from your computer, then select the option Data service solution url for deploying the data service and specify the url (and port as shown in the example) to that server.  The default port used for uploading a data service is port 9763, although in WSAS you could also use port 9762 also.
  10.  Dataservice deploying options

  11. If this is the first time you are deploying a data service to the server specified by the above URL, through the Eclipse plugin, in current workspace you need to set the trustore:
  12. Click on Set truststore to specify the new truststore file.



    Browse truststore

    This file is located with the binary of the WSO2 Data Services solution server itself, under the conf directory. In the current version of the plugin, it is required to provide the path to this file. Truststore files belonging to different server versions may not work for other servers. This will help identify the server as a valid server.

     After selecting a valid trustore, the wizard will ask for a password. If you leave the password textbox empty and select OK, the default password for the carbon truststore (which is "wso2carbon") will be used. In the event the password for the truststore is different from the default password, please type in the correct password.

    Password for the truststore


    The plugin remembers the most recently typed in values set in the truststore within a workspace. Therefore, the next time you use the wizard to connect to the same server, you need not set truststore again.

  13. So now, we need to provide the username and the password for the server we are intending to connect to. The plugin remembers the default username and password to access the server. In the event, the default credentials are no longer valid, you should click on Set Credentials and type in the correct username and password.
  14. Credentials


    The WSO2 Data Services solution is shipped with a default user account with the following credentials:

    user name : admin

    password : admin

    If you select the Save credentials check box, the plugin will remember the credentials entered for this workspace and will use it for whatever the server url you have specified. If you change the server url and change the credentials with the Save credentials check box selected then the credentials of the earlier server URL will be overwritten.

  15. Tick the Try it after deploying checkbox so that we can test the dataservice after it has been deployed to the server.
  16. tryi it


    Try it will only work if the dataservice was successfully deployed on the server and that the server manages to publish the service without any errors.

    If all the information required has being gathered the Next button in the wizard will be enabled. Click next to start adding datasources.

    Step 1 - Adding Data Sources


    The 2nd page of the wizard is where we actually start building our data service.

  17. Specify a valid service name in the Service Name text box. This name should comply any rules governing for creating service names.
  18. Page1 - Service Name

  19. This version of the plugin supports multiple datasources. For this tutorial we will only add one datasource. Click Add to add a new datasource. By default the first datasource you add will have no name/id for it and thus will be called [Default] for the purpose of addressing it.
  20. First datasource

    From the datasource type dialog that popped up select RDBMS and click OK.

  21. We are going to create a mysql datasource for our dataservice. So select MySQL from the Database Type combo box.
  22. RDBMS Datasource


    Eventhough it is not required the plugin can test the connection with the database server you type in with the relevant details. But the plugin also requires the required database driver classes being present in the library path. If it is not present an annoying message such as the following screen shot may be shown to you.

    Error Msg

    And you will see just above the Test Connection button you can specify where the driver class is located. If you dont already have it for mysql you can download it from here

  23. Type in the information required to connect with the mysql database server
  24. i.e.

    valid JDBC URL (If you've forgotten this is in the format jdbc:mysql://[machine-name or ip]:[port]/[database-name])

    User Name and Password

  25. After specifying the relevant details for the database connection you can click Test Connection button to test the entered details. The success and the failure of the test will be indicated right underneath the Test Connection button. If the test connection fails the message should indicate what might be wrong.
  26. Test Connection


    The test connection need not be success since the connection information may be available at the deployed server only. Thus it may not work in your computer but will work in the server with no problems.

  27. Click OK to add the RDBMS datasource we just defined to the dataservice.
  28. Datasource Added

    We have now completed the first step of defining datasources. If you want to change a defined datasource just select it from the table and click edit to change its parameters.

    Step 2 - Adding Queries

    Query Page

  29. Click Add New Query and the new query dialog will appear.
  30. New Query

  31. Select [Default] from list of datasources we created.
  32. Specify a name for this query in the Query ID text box.
  33. Type the following in SQL Statement text box.
  34. select * from film_list where film_list.category = ? and film_list.price <= ?

    Content Assistant - Sql

    Press Ctrl + <Space> to get a popup list of tables available for the query. This list will only appear if the test connection was successfull for the datasource we are using. You can just select from the list to insert the table name in the query. Try pressing a "." after a table name, it will popup a list of columns available for that table.

  35. Since the sql query we typed has two parameters which needs to be satisfied by the user, lets add 2 input mappings. Click New button to add input mappings to the query.
  36. Input mapping 1

     Type "MovieCategory" as its Name, "STRING" as SQL Type and click OK. Create another input mapping in the same way as above and put Name as "MaximumPrice", SQL Type as "DOUBLE". Then altogether you now have 2 input mappings.

    Input mappings

  37. Specify the Group By Element as "Movies" and Row Name as Movie.
  38. Now we will map the output data to xml elements or attributes etc. For that click on New button on Result (Output Mapping).
  39. output mappings

     Specify the values of the fields as above and click OK.

     one output mapping

  40. Likewise lets add more output mappings to our query as the following table.
  41. Mapping Type

    Output Field Name

    SQL Column Name
    ELEMENT Description description
    ELEMENT Category category
    ELEMENT Price price
    ELEMENT RunningTime length

    Now the query dialog will look like the following


  42. Click OK to add the query to the dataservice.

  44. Lets add 2 more queries to our dataservice. Follow the details on the table given below.

    Query ID queryKidsMovies
      SQL select * from film_list where rating='G' or rating='R'
      Group By Element ChildrenMovies
      Row Name Movies
      Output Mappings
    Mapping Type

    Output Field Name

    SQL Column Name
    ELEMENT MovieName title
    ELEMENT Description description
    ELEMENT Performers actors
    Query ID querySalesForCustomer
      SQL SELECT concat(c.first_name , " ", c.last_name) as name, sum(amount) as amount FROM (select customer_id, amount from payment where payment_date>=? and payment_date<?) as p  left join (select customer_id, first_name, last_name from customer) as c on p.customer_id=c.customer_id group by p.customer_id;
      Input Mappings

    SQL Type In/Out Type

    PaymentStartDate DATE IN
    PaymentEndDate DATE IN
       Group By Element  Customers
       Row Name  Customer
       Output Mappings  
    Mapping Type

    Output Field Name

    SQL Column Name
    ATTRIBUTE Name name
    ELEMENT TotalPaid amount


    All 3 queries are now added to the dataservice.

    quries added




    Step 3 - Adding Operations

    page 4



  46. Click Add New Operation to add operations
  47. operation dialog.



  48.  Set the Operation Name as "GetMovieList" and set Operation Parameters.
  49. operation

  50.  Click OK to add the operation to the dataservice.
  51. page4 operation added


  52. Lets add 2 more operations to the dataservice
  53. Operation Name GetKidsMovies
      Query queryKidsMovies


    Operation Name GetCustomerSales
      Query querySalesForCustomer


    PaymentStartDate Sales_Made_From

    PaymentEndDate Sales_Made_Up_To


  54.  These added operations are what the end user sees.
  55. operations added

  56. Click Finish to deploy the web service. If all goes well a success message will appear.
  57.  deploying_to_servertest_servicelaunch_webbrowser

    success msg

  58. If the data service was successfully deployed, the default Web browser will be launched with the try it page for the particular Web service.
  59. try it

  60. Specify relevant parameters and click on relevant buttons to test the service.

 try it 2try it2 results


try it 3 try it 3 results 


In this tutorial, I specifically focused on creating a data service using a RDBMS data source. Upon completing this tutorial, you should have gained some experience on vital components and developed a deeper understanding of WSO2 Data Services. Use of other types of data sources would be similar. 


Saminda Wijeratne, Software Engineer, WSO2 Inc., [email protected]