XPath Missing in Retrieve Attribute from Message Filter in OAG 220.127.116.11.0
(Doc ID 2057050.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle API Gateway - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 11gR1]
Information in this document applies to any platform.
In Oracle API Gateway (OAG) 126.96.36.199.0, after upgrading from an earlier version, in this case 188.8.131.52.0, when an Attribute -> Retrieve from Message filter is used, the XPath section is empty.
In the configuration of the Attribute -> Retrieve from Message filter, there is a drop down in the section "What to extract from message" labeled "Use the following XPath".
This drop down, which is supposed to contain the XPath section, is empty. It does not show the XPath which had previously been configured.
Instead, the the filter asks for an XPath in the "Use the following XPath" drop down
The problem has been observed in OAG 184.108.40.206.0 before SP3 under either of the following two scenarios:
- The whole OAG installation was upgraded from OAG 220.127.116.11.0
- The policy using the Attribute -> Retrieve from Message filter was exported from 18.104.22.168.0, and re-imported into OAG 22.214.171.124.0.
The problem does not occur in OAG 126.96.36.199.0.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document