This documentation is for older versions of WSO2 products and may not be relevant now. Please see your respective product documentation for clustering details and configurations.
Clustering Guide 4.4.x

Versions Compared

Old Version 70

changes.mady.by.user Mariangela Hills

Saved on

compared with

New Version Current

changes.mady.by.user Mariangela Hills

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: https://github.com/wso2/product-apim/issues/5042

...



 

(API Manager Database)

apimgtdb

(User Manager Database)

userdb

(Registry Database)

regdb

(Statistics Database)

statdb

(Message Broker Database)

mbstoredb

Publisher

Used

Used

Used

UsedNot used

Store

Used

Used

Used

UsedNot used

Key Manager

Used

Used

Used (in multi-tenancy mode)

Not usedNot used

Gateway

Not used

Used (in multi-tenancy mode)

Used (in multi-tenancy mode)

Not usedNot used
Traffic ManagerNot usedNot usedNot usedNot usedUsed
Note
titleNotes
  • Although the Gateway does not use the WSO2 API Manager database and the WSO2 Message Broker database, this connection is required so the default connections are required; therefore, do not remove the default configuration in the <APIMconfigurations in the <API-M_HOME>/repository/conf/datasources/master-datasources.xmlfile file. These connections should be your default database (H2 database).
  • If you have more than one Traffic Manager node, each Traffic Manager node must have its own WSO2_MB_STORE_DB database.

When we consider distributed deployment of WSO2 API Manager, we have the option of separating the five components and clustering each component as needed. Let's look more closely at how the API Manager components are deployed separately.

...