...
- In the management console, click the Configure tab, and then click Data Sources.
- Click Add Data Source.
- Specify the required options for connecting to the database. The available options are based on the type of datasource you are creating:
Anchor rdbms rdbms
Configuring an RDBMS datasource
When you select RDBMS as the datasource type, the following screen appears:
This is the default RDBMS datasource configuration provided by WSO2. You can also write your own RDBMS configuration by selecting the custom datasource option. Enter values for the following fields when using the default RDBMS datasource configuration:
- Data Source Type: RDBMS
- Name: Name of the datasource (must be a unique value)
- Data Source Provider: Specify the datasource provider as described below.
- Driver: The class name of the JDBC driver to use. Be sure to copy the JDBC driver relevant to the database engine to the
<ESB_HOME>/repository/components/dropinsand<ESB_HOME>/repository/components/libdirectories. For example, if you are using MySQL, you would specifycom.mysql.jdbc.Driveras the driver and would copymysql-connector-java-5.XX-bin.jarto these directories. If you do not copy the driver to these directories when you create the datasource, you will get an exception similar to "Cannot load JDBC driver class com.mysql.jdbc.Driver".
- URL: The connection URL to pass to the JDBC driver to establish the connection
- User Name: The connection user name to pass to the JDBC driver to establish the connection
- Password: The connection password to pass to the JDBC driver to establish the connection
- Expose as a JNDI Data Souce: Allows you to specify the JNDI data source as described below
- Data Source Configuration Parameters: Allows you to specify the datasource connection pool parameters when creating an RDBMS datasource
Many of these fields are similar to those in DBCP. For more information, see: http://commons.apache.org/dbcp/configuration.html
After creating datasources, you can edit and delete them as needed.
...
| Anchor | ||||
|---|---|---|---|---|
|
Datasource provider
A datasource provider connects to a source of data such as a database, accesses its data, and returns the results of the access queries. When creating an RDBMS datasource, you can use the default provider or link to an external provider. To use the default datasource provider, select default, and then enter the connection properties Driver, URL, User Name, and Password as follows:
...
If you need to add a datasource supported by an external provider class such as com.mysql.jdbc.jdbc2.optional.MysqlXADataSource, select External Data Source, click Add Property, and then enter the name and value of each connection property you need to configure. Following is an example datasource for an external datasource provider.
...
| Anchor | ||||
|---|---|---|---|---|
|
JNDI datasource
Java Naming and Directory Interface (JNDI) is a Java application programming interface (API) that provides naming and directory functionality for Java software clients to discover and look up data and objects via a name. It helps decouple object creation from the object look-up. When you have registered a datasource with JNDI, others can discover it through a JNDI look-up and use it.
...
- Name: Name of the JNDI datasource that will be visible to others in object look-up
- Use Data Source Factory: To make the datasource accessible from an external environment, you must use a data source factory. When this option is selected, a reference object will be created with the defined datasource properties. The data source factory will create the datasource instance based on the values of the reference object when accessing the datasource from an external environment. In the datasource configuration, this is set as follows:
<jndiConfig useDataSourceFactory="true"> - JNDI Properties: Properties related to the JNDI datasource (such as password). When you select this option, set the following properties:
java.naming.factory.initial: Selects the registry service provider as the initial contextjava.naming.provider.url: Specifies the location of the registry when the registry is being used as the initial context
...
Anchor custom
...
...
custom
Configuring a custom datasource
If you select the Custom datasource type, the following screen will appear:
...
- Data Source Type: Custom
- Custom Data Source Type: Specify whether the data is in a table or accessed through a query as described below
- Name: Enter a unique name for this datasource
- Description: Description of the datasource
- Configuration: XML configuration of the datasource
...
- datasource
...
Anchor CusDSType CusDSType
Custom datasource type
When creating a custom datasource, specify whether the datasource type is DS_CUSTOM_TABULAR (the data is stored in tables) or DS_CUSTOM_QUERY (non-tabular data accessed through a query). Following is more information about each type.
...