|Table of Contents|
Setting up the database and users
- Copy the Oracle JDBC libraries (for example, <
ORACLE_HOME/jdbc/lib/ojdbc14.jar)to the <
- Remove the old database driver from the
If you get a
The value of this property should be the GMT difference of the country. If it is necessary to set this property permanently, define it inside the
A datasource is used to establish the connection to a database. By default datasources are used to connect to the default H2 database. After setting up the Oracle database to replace the default H2 database, either change the default configurations of the
WSO2_CARBON_DB datasource or configure a new datasource to point it to the new database as explained below.
The default datasource configuration are defined in the files listed below, which are located in the <
This file contains the following default datasource configurations to configure IoTS with the Carbon database and the WSO2 API Manager database.
This file contains the following default datasources used for summarization and to persist stream data. The database tables are created dynamically when running the spark script along with the required tables.
WSO2_METRICS_DB datasource in the
metrics-datasources.xml file by replacing the
driverClassName settings with your custom values and also the other values accordingly.
This file contains the following default datasource configurations to configure WSO2 IoTS with the Connected Device Management Framework and for device management.
Edit the datasources in the
Each device type will have its own datasource so that all the data required for the device type can be stored in it. Therefore, when writing a new device plugin make sure to create your own datasource too.
For example, let’s take Arduino plugin.
The elements in the above configuration are described below:
|url||The URL of the database. The default port for a DB2 instance is 50000.|
|username and password||The name and password of the database user|
|driverClassName||The class name of the database driver|
|maxActive||The maximum number of active connections that can be allocated at the same time from this pool. Enter any negative value to denote an unlimited number of active connections.|
|maxWait||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.|
|minIdle||The minimum number of active connections that can remain idle in the pool without extra ones being created, or enter zero to create none.|
|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.|
|validationQuery||The SQL query that will be used to validate connections from this pool before returning them to the caller.|
|validationInterval||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.|
Follow the steps given below to configure the new datasources to point to the new databases you create to manage registry and/or user management data separately:
- Add a new datasource with similar configurations as the
WSO2_CARBON_DBdatasource above to the <
master-datasources.xmlfile. Change its elements with your custom values. For instructions, see Setting up datasource configurations.
If you are setting up a separate database to store registry-related data, update the following configurations in the <
Code Block language xml
<dbConfig name="wso2registry"> <dataSource>jdbc/MY_DATASOURCE_NAME</dataSource> </dbConfig>
If you are setting up a separate database to store user management data, update the following configurations in the <
Code Block language xml
<Configuration> <Property name="dataSource">jdbc/MY_DATASOURCE_NAME</Property> </Configuration>
Creating the database tables
To create the database tables, connect to the database that you created earlier and run the following scripts in SQL*Plus:
To create tables in the registry and user manager database (
WSO2CARBON_DB), use the below script:
Code Block language powershell
Restart the server.
You can create database tables automatically when starting the product for the first time by using the
-Dsetupparameter as follows:
Note to writers: Add this content at the end of the page if any of the additional databases is relevant to your product.
Changing the identity/storage/product-specific databases
The topics above show how to change the
WSO2_CARBON_DB, which is used to store registry and user manager information. If you changed the product-specific database that comes by default or set up a separate database for identity or storage related data, the instructions are the same. In summary:
Add a new datasource configuration to the following files for each of the separate databases that you need to create.
|For the identity database||Add it to the |
|For the storage database||Add it to the <|
|For the product-specific database||Add it to the <|
Create the database tables using the following scripts:
|For the identity database||Use |
|For the storage database||Use |
|For the product-specific database||Use |
Update the following configurations, with the defined datasource name of the corresponding database configuration you added to the
If you are setting up a separate database to store identity-related data, update the following configurations in the <
<JDBCPersistenceManager> <DataSource> <!-- Include a data source name (jndiConfigName) from the set of datasources defined in master-datasources.xml --> <Name>jdbc/WSO2CarbonDB</Name> </DataSource> </JDBCPersistenceManager>
By default, all WSO2 products are configured to use the embedded H2 database. To configure WSO2 IoTS with Oracle, see Changing to Oracle.