Latest Released Version v4.3.5.

• data-services
• data-sources
• dbconsole

carbon-data contains the source code of modules used for Data Services Server.
This repo contains Service Stubs, Components and Features of each module.
In order to be informed on the way these modules are going to be integrated and used please refer to the Wiki of the product-dss.

• OData - Implement ExpressionVisitor Olingo interface in order to elaborate SQL queries.
• Performance tunings regarding OData requests in order to limit the amount of records being retrieved.
• Extend OData configurations related to finlering tables to be exposed over odata.
• Extend OData configurations related to filtering columns to be exposed over odata and possibility to change their type.
• Bug fixes regarding MSSQL query formatting including schema parameter.
• OData now supported for Cassandra databases
• Related entities can now be queried with OData in MySQL, PostgreSQL, H2, Oracle, MicroSoft SQL Server databases.
• REST API for creating, updating, deleting dataservices within specific tenant.

All WSO2 products expose their management functionality as admin services, which are SOAP services.
In this fork of carbon.data we have exposed OSGi-level functionalities as REST APIs via JAX-RS web application.

In order to expose a SOAP-based admin service as a REST API there are several tasks that need to be done:

• Create DataServiceManager packages to be integrated inside carbon.data OSGi bundles.
• Create Jax-RS WebApp in order to provide the REST API that is going to consume the OSGi service.
• Provide multitenancy data services creation through the API, extend admin services in order to switch the AxisConfiguration according to current PrivilegedCarbonContext.
• Integrate the OAUTH2 security filter in order to allow only authorized access to the REST API for dataservices CRUD.

All the list of webservices is exposed in the following endpoint: https://mydomain.com/dss_proxy_context_path/rest/
They are protected by OAuth2 token-based authentication method, therefore the token must be provided in the Header or it can be used the apikey as a query parameter.
The API can be accesed also by using Basic Authorization Header : Basic base64Encode(username:password)

To save or update the configuration of one dataservice inside specific tenant the following call should be performed:

POST /{tenantDomain}/saveDataService    HTTPS/1.1 
Accept: application/json 
Host: https://mydomain.com/dss_proxy_context_path/DSSRestApi/rest_services
a. Authorization: Bearer <token-value>  
b. ApiKey query param https://wso2server.com/dss/DSSRestApi/rest_services/newdomain.com/saveDataService?apikey=APIKEY_VALUE

To get the configuration of one dataservice inside specific tenant the following call should be performed:

GET /{tenantDomain}/getDataService?serviceid=DATASERVICENAME    HTTPS/1.1 
Host: https://mydomain.com/dss_proxy_context_path/DSSRestApi/rest_services
a. Authorization: Bearer <token-value>  
b. ApiKey query param https://wso2server.com/dss/DSSRestApi/rest_services/newdomain.com/getDataService?serviceid=DATASERVICENAME&apikey=APIKEY_VALUE

To filter the list of dataservices inside specific tenant is important to provide the term you want to search and also provide the page number starting from 0.
The following call should be performed:

GET /{tenantDomain}/listDataService?search=TERM_TO_SEARCH&page=0    HTTPS/1.1 
Host: https://mydomain.com/dss_proxy_context_path/DSSRestApi/rest_services
Accept: application/json 
a. Authorization: Bearer <token-value>  
b. ApiKey query param https://wso2server.com/dss/DSSRestApi/rest_services/newdomain.com/listDataService?search=TERM_TO_SEARCH&page=0&apikey=APIKEY_VALUE

To delete one dataservice inside specific tenant the following call should be performed:

DELETE /{tenantDomain}/dataService/DATASERVICENAME    HTTPS/1.1 
Host: https://mydomain.com/dss_proxy_context_path/DSSRestApi/rest_services
a. Authorization: Bearer <token-value>  
b. ApiKey query param https://wso2server.com/dss/DSSRestApi/rest_services/newdomain.com/dataService/DATASERVICENAME&apikey=APIKEY_VALUE

Consider the fact that you can delete a dataservice that could be placed inside specific folder,in that case you can provide the exact value: /dataService/FOLDERNAME/DATASERVICENAME