Data Services Server (WSO2)

Behind most applications are heterogeneous data stores. Most businesses require secure and managed data access across these federated data stores, data service transactions, data transformation, and validation. An organization’s data exposed as a service, decoupled from the infrastructure where it is stored is called data services in service-oriented architecture (SOA).

Data services provide a convenient mechanism to configure a Web service interface for data in various datasources such as relational databases, CSV files, Microsoft Excel sheets, Google spreadsheets etc. These data services provide unprecedented data access and straightforward integration with business processes, mashups, gadgets, business intelligence, and mobile applications.

WSO2 Data Services Server augments service-oriented architecture development efforts by providing an easy-to-use platform for integrating data stores, creating composite data views, and hosting data services. It supports secure and managed data access across federated data stores, data service transactions, and data transformation and validation using a lightweight, developer friendly, agile development approach. It provides federation support, combining data from multiple sources in single response or resource and also supports nested queries across data sources. WSO2 Data Services Server is based on Java OSGi technology, which allows components to be dynamically installed, started, stopped, updated, and uninstalled while eliminating component version conflicts.

• Data Services Server Installation
  • Description of Custom Authentication Config Parameters
• Data Services Server Usage
  • OData requests
  • REST Requests
  • Securing Private Data Services
• REST API for dataservices CRUD
  • 1. REST API Usage
    • 1.1. Save dataservice
    • 1.2. Get dataservice configuration
    • 1.3. Get list of dataservices
    • 1.4. Delete dataservice
    • Technical implementation
• Deployment Guidelines in Production
  • 1. Re-generate the keystore:
    • 1.1 Example for generating a new keystore:
    • 1.2 Example for importing a new certificate:
  • 3. Update the following files with the new keyStore name and domain alias:
  • 3. Setting Up Secure Vault Configuration (OPTIONAL)
  • 4. Adding a Custom Proxy Path
    • 4.1. Install and configure a reverse proxy
    • 4.2. Configure DSS with proxy context path
      • 4.2.1 Edit <PRODUCT_HOME>/repository/conf/carbon.xml
      • 4.2.2 Edit <PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml
      • 4.2.3 Edit <PRODUCT_HOME>/repository/conf/security/Owasp.CsrfGuard.Carbon.properties
      • 4.2.4 Remember to update the file authenticators.xml according to the new proxy config: