In WSO2 SP, there are datasources specific to each runtime (i.e., worker, editor, manager, and dashboard runtimes). The datasources of each runtime are defined in the <SP_HOME>/conf/<runtime>/deployment.yaml file. e.g., To configure a datasource in the worker runtime, the relevant configurations need to be added in the <SP_Home>/conf/worker/deployment.yaml file.
...
| Database Access Requirement | Carbon coordination supports zookeeper and RDBMS based coordination. In RDBMS coordination, database access is required for updating the heartbeats of the nodes. In addition, database access is required to update the coordinator and the other members in the cluster. For more information, see Configuring Cluster Coordination . |
|---|---|
| Required/Optional | This is required. However, you can also use Zookeeper coordination instead of RDBMS. |
| Default Datasource Name | The carbon datasources are used. The default datasource varies depending on the deployment as follows:
|
| Tables | LEADER_STATUS_TABLE, MEMBERSHIP_EVENT_TABLE, REMOVED_MEMBERS_TABLE, CLUSTER_NODE_STATUS_TABLE |
| Schemas and Queries | Information about the default queries and the schema can be viewed here. |
| Tested Database Types | MySQL, Postgres, Mssql, Oracle 11g |
...
| Database Access Requirement | It gives the capability of creating the tables at the siddhi app runtime and access the existing tablesif a user defined carbon datasource or JNDI property in a siddhi app. Documentation can be found in https://wso2-extensions.github.io/siddhi-store-rdbms/api/4.0.15/ |
|---|---|
| Required/Optional | Optional |
| Default Datasource Name | No such default Datasource. User has to create the datasource in the Siddhi app |
| Tables | No such default tables. User has to define the tables |
| Schemas and Queries | Information about the default queries and schema: https://github.com/wso2-extensions/siddhi-store-rdbms/blob/v4.0.15/component/src/main/resources/rdbms-table-config.xml |
| Tested Database Types | H2, MySQL, Mssql, Oracle 11g, DB2, PostgreSQL |
...
| Database Access Requirement | Permission provider will access the DB to persist permissions and role - permission mappings. |
|---|---|
| Required/Optional | Mandatory, default is in H2 |
| Default Datasource Name | PERMISSIONS_DB |
| Tables | PERMISSIONS, ROLE_PERMISSIONS |
| Schemas and Queries | |
| Tested Database Types | H2, MySQL, Mssql, Oracle 11g |
| Recommendations for the Production Environment | The database configured for permissions can be shared between the worker profile and the dashboard profile. |