The following topics cover the configurations generic for all four deployment patterns described in the previous section:
Table of Contents | ||||
---|---|---|---|---|
|
Prerequisites
1. In this example, we use the following products.
...
API Manager Component | Offset Value | Port Value |
WSO2 ELB | 0 | 9443 |
Key Manager Server | 1 | 9444 |
Manager Gateway Server | 2 | 9445 |
Publisher Server | 3 | 9446 |
Store Server | 4 | 9447 |
Worker Gateway Server | 5 | 9448 |
Configuring Shared Databases
Anchor | ||||
---|---|---|---|---|
|
We use shared databases to share information among distributed sever nodes of the API Manager. The following table shows a summarized view of the shared database configuration:
...
Details of the configuration are given below.
User Manager Database Configuration
Let's take a look at configuring the User Manager database that is shared with the API Publisher, Store, and Key Manager servers.
...
Code Block | ||
---|---|---|
| ||
<EnableEmailUserName>true</EnableEmailUserName> |
Registry Database Configuration
This section describes the creation and configuration of the registry database that will be used by the Publisher and Store server instances. The Governance space (/_system/governance) of the Publisher and Store instances are mounted to a common location within a remote governance registry instance. We will use MySQL as the registry database in this particular governance registry instance.
...
- On Linux, use wso2server.sh -Dsetup
- On Windows, use wso2server.sh -Dsetup
API Manager Database Configuration
This section describes the creation and configuration of the API manager database used by the Publisher, Store, and Key Manager server instances.
...
Next, let's take a look at deploying individual components of the API Manager.
Configuring API Manager Components
Anchor | ||||
---|---|---|---|---|
|
Caching Configuration
Refer to section Caching Configuration for information.
API Key Manager Server Configuration
The Key Manager server is primarily used to validate API keys. The same Auth Manager server can be used as the authentication manager as well. Key Manager is also used for caching configuration as discussed above.
API Gateway Configuration
API Gateway is used to route API calls made by API consumers. The Gateway component validates and authenticates users against given API keys that are stored in the Key Manager Server.
...
Info | ||
---|---|---|
| ||
The <AuthManager> and <Database> elements in <APIM_HOME>/repository/conf/api-manager.xml are not required for the API Gateway instance, so you can comment them out. |
API Publisher and API Store
API Publisher publishes APIs to the API Store, where users can access them. When users subscribes to an API, they generates access tokens to make API calls to that API.
...