Saturday, November 5, 2016

WSO2 APIM 2.0.0 DB Configuraiton

APIM 2.0.0 uses the following databases.

  • Local database (WSO2_CARBON_DB) – Local registry space which is specific to each APIM instance.
  • User Manager database (WSO2UM_DB - Stores information related to users and user roles.
  • API Manager database (WSO2AM_DB) - Stores information related to the APIs along with the API subscription details
  • Registry database (WSO2REG_DB) - Content store and a metadata repository for SOA artifacts
  • Statistics database (WSO2AM_STATS_DB )- Stores information related to API statistics. After APIM analytics is configured, it writes summarized data to this database.
  • Message Broker database (WSO2_MB_STORE_DB) - Use as the message store for broker when advanced throttling is used. This is used in APIM instance which is used as Traffic Manager. If there is more than one Traffic Manager node, each Traffic Manager node must have its own message broker database.

Following are the databases required for APIM analytics.

  • WSO2_ANALYTICS_EVENT_STORE_DB - Analytics Record Store which stores event definitions
  • WSO2_ANALYTICS_PROCESSED_DATA_STORE_DB - Analytics Record Store which stores processed data
  • WSO2_GEO_LOCATION_DB - statistics generated for selected geographic locations
  • WSO2AM_STATS_DB – Store API statistics related data and this should be shared with APIM instances.
  • WSO2UM_DB – Stores information related to the users. This also should be shared with APIM instances.
  • WSO2_CARBON_DB – Local Database for the APIM Analytics.
  • WSO2REG_DB – Registry database for APIM analytics. We can configure a separate one or use the WSO2_CARBON_DB it self.

For two active-active all-in-one instances of WSO2 API Manager with analytics we can use DB connections as follows.


No comments:

Post a Comment