Problems With Using Environment Variables In envsettings.props in Oracle API Gateway (Doc ID 1640072.1)

Last updated on AUGUST 18, 2016

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.

Symptoms

When using OAG 11.1.2.1.0, a simple circuit is created that uses two variables.  Variable one is taken from the envsettings.props file in the environment and Variable two is created using the Set Attribute Filter.

These two variables are then displayed using the Set Message Filter.

No error is seen when using a single Variable
 
If the Set Message Filter is set to ${env.VariableOne} to display the variable from envsettings.props, the circuit completes correctly and the appropriate value is displayed on the screen.

If the Set Message Filter is set to ${VariableTwo} to display the variable from the Set Attribute filter, the circuit completes correctly and appropriate value is displayed on the screen.

Should the Set Message Filter be set to ${env.VariableOne} ${VariableTwo}, the circuit does not complete correctly and the value of Variable one is used, rather than the value of Variable one concatenated with Variable two, as is expected.

The error appears to be an issue when any filter contains two variables;  one taken from envsettings.props and one from a variable, then used to for the Set Attribute Filter.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms