Oracle® Fusion Middleware
Externalizing API Gateway Instance Configuration

When API Gateway configuration is deployed to group, the configuration package settings are applied to all API Gateway instances in the group. You can also specify API Gateway configuration values on a per-API Gateway instance basis using environment variables in the envSettings.props file. For example, you can specify the port on which the API Gateway listens for HTTP traffic with different values depending on the environment in which the API Gateway is deployed.

The environment variable settings in the envSettings.props file are external to the API Gateway core configuration. The API Gateway runtime settings are determined by a combination of external environment variable settings and core configuration. This mechanism provides a simple and powerful approach to configuring specific API Gateway instances in the context of API Gateway group configuration defined in policy and environment packages.

The envSettings.props file is located in the conf directory of your API Gateway installation, and is read each time the API Gateway starts up. Environment variable values specified in the envSettings.props file are displayed as environment variable selectors in the Policy Studio (for example, ${env.PORT.TRAFFIC}). For more details on selectors, see the API Gateway User Guide.

The envSettings.props file enables you to externalize configuration values and set them on a per-server environment basis. This section shows the configuration syntax used, and shows some example values in this file.

Environment Variable Syntax

If the API Gateway configuration contains a selector with a format of ${env.X}, where X is any string (for example, MyCustomSetting), the envSettings.props file must contain an equivalent name-value pair with the following format:

env.MyCustomSetting=MyCustomValue

When the API Gateway starts up, every occurrence of the ${env.MyCustomSetting} selector is expanded to the value of MyCustomValue. For example, by default, the HTTP port in the server configuration is set to ${env.PORT.TRAFFIC}. Specifying a name-value pair of env.PORT.TRAFFIC=8080 in the envSettings.props file results in the server opening up port 8080 at start up.

Example Settings

The following simple example shows some environment variables set in the envSettings.props file:

# default port the API Gateway listens on for HTTP traffic
env.PORT.TRAFFIC=8080

# default port the API Gateway listens on for management/configuration HTTP traffic
env.PORT.MANAGEMENT=8090

The following example screen shows the corresponding ${env.PORT.TRAFFIC} selector displayed in the Configure HTTP Interface dialog. At runtime, this is expanded to the value of the env.PORT.TRAFFIC environment variable specified in the envSettings.props file:

You can also use the envSettings.props file to bind a reference to a server host-specific SSL certificate to a specific deployment.

Example Syntax:

The following entry shows an example of the environment variable syntax used to specify a server host-specific certificate:

env.serverCertificate=${system.prefix.cert}MY_ALIASED_CERT_NAME

Alternatively, the following entry shows the syntax when the alias is the same as the Distinguished Name:

env.serverCertificate=${system.prefix.cert}CN=MY_HOST

Example Settings

When the env.serverCertificate variable is specified in the envSettings.props file, the X.509 Certificate field in the Configure HTTPS Interface dialog can then reference its value using the ${env.serverCertificate} selector. The following example screen shows the corresponding ${env.serverCertificate} selector specified at the bottom of the Select Certificate dialog, which is displayed by pressing the X.509 Certificate button:

The following example screen shows the ${env.serverCertificate} selector then referenced in X.509 Certificate field: