This section guides you through the logical separation of data that you can do when clustering WSO2 Identity Server.
| Tip | ||
|---|---|---|
| ||
Before you begin, note that creating separate databases as shown below is not actually required and can be skipped. Instead, you can point all the datasources given below to a single database. This will NOT make a difference in performance. To do this, see the steps given within the flow of the deployment pattern setup in the Configuring the datasources /wiki/spaces/IS541/pages/42827917 sub topic. However, if you do want to separate the data logically into separate databases, you can follow the steps given below. |
...
| Database Name | Description | Script location | Datasource file to be modified | ||
|---|---|---|---|---|---|
USERSTOREWSO2_USER_DB | Authorization manager configurations, internal permissions and roles. | <IS_HOME>/dbscripts/ |
| ||
IDENTITY_DB | Contains identity related data, for example, OAuth 2.0, SAML 2.0, etc. | <IS_HOME>/dbscripts/identity/ |
| ||
METRICS_DB | Metrics Database is used to store the runtime metrics data reported by the Metrics JDBC Reporter periodically. There are 5 tables to store metrics data for each metric type. The metric types are Counter, Meter, Gauge, Histogram, and Timer. | <IS_HOME>/dbscripts/metrics/ | <IS_HOME>/repository/conf/datasources/metrics-datasources.xml | ||
BPS_DB | This is used to create, drop, and truncate data pertaining to the workflow feature. |
| <IS_HOME>/repository/conf/datasources/bps-datasources.xml | ||
REGISTRY_DB | Shared database for config and governance registry mounts in the product's nodes. This includes data on tenants and keystores. | <IS_HOME>/dbscripts/ | <IS_HOME>/repository/conf/datasources/master-datasources.xml |
To understand this concept further, see the following diagram.
For more information on the concept of sharing governance and config registry databases across the cluster, see the topic on Sharing Databases in a Cluster in the WSO2 Product Administration Guide.
...