A datasource is a connection set up to a storage of data, such as a database or a data file, from a server. A datasource provides information that a server can use to connect to a a storage of data.
Enabling datasource management
Datasource management is provided by the following feature in the WSO2 feature repository.
Name : WSO2 Carbon - datasource management feature
If datasource management capability is not included in your product by default, add it by installing the above feature. For instructions on the datasource management feature, see Feature Management.
Use the following steps to add a datasource:
- In the product management console, click Data Sources on the Configure tab.
- Click Add Data Source.
- Select the required options for connecting to the database. The available options are based on the type of datasource you are creating:
- Configuring a RDBMS Datasource
- Configuring a Custom Datasource
- After adding datasources, they will appear on the Data Sources page. You can edit and delete them as needed by clicking Edit or Delete links.
You can view, edit, and delete the datasources in your product instance by clicking Data Sources in the Configure menu of the product management console. However, you cannot edit or delete the default
WSO2 DAS default datasources
The default RDBMS type datasources, which are shipped with WSO2 DAS are defined in the
<DAS_HOME>/repository/conf/datsources/ directory as follows.
WSO2_CARBON_DB master datasource, which is defined in the
<DAS_HOME>/repository/conf/master-datasources.xml file is used to store data of registry and user manager of WSO2 DAS in a RDBMS.
By default, this points to the in-built H2 database of the DAS. Replace the
driverClassName settings with your custom values and also the other values accordingly in the master
-datasources.xml file as shown in the below example, to change the underlying RDBMS to which this datasource connects. For information on changing the underlying database type, see Working with Databases.
The datasource configuration options are as follows. For more information on these configuration properties, see Apache TomEE Documentation.
|The URL of the database.|
|The name of the database user.|
|The password of the database user.|
|The class name of the database driver.|
|The maximum number of active connections that can be allocated from this pool at the same time, or enter a negative value for no limit.|
|The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception. You can enter zero or a negative value to wait indefinitely.|
|The indication of whether objects will be validated before being borrowed from the pool. If the object fails to validate, it will be dropped from the pool, and another attempt will be made to borrow another.|
|The SQL query that will be used to validate connections from this pool before returning them to the caller.|
|The indication to avoid excess validation, and only run validation at the most, at this frequency (time in milliseconds). If a connection is due for validation, but has been validated previously within this interval, it will not be validated again.|
|The default auto-commit state of new connections.|
Following analytics datasources are defined in the
<DAS_HOME>/repository/conf/datsources/analytics-datasources.xml file. For more information on the usage and configuration of these datasources, see DAS Data Access Layer.
|This datasource is used by default to connect to the Analytics File System.|
|This datasource is used by default to connect to the data store of the Analytics Record Store which stores event definitions.|
|This datasource is used by default to connect to the data store of the Analytics Record Store which stores processed data.|
This is the datasource that is used to store Carbon metrics. The configurations of this datasource are defined in the
The following sections explain the datasource types, which are used in DAS.