OAG Retrieve Attribute From Message Filter XPATH Does not Show up After Migrating Policy to 11.1.2.3.0
(Doc ID 2069458.1)
Last updated on MARCH 10, 2023
Applies to:
Oracle API Gateway - Version 11.1.2.1.0 and laterInformation in this document applies to any platform.
Symptoms
PROBLEM DESCRIPTION
--------------------
After migrating a policy from OAG 11.1.2.1 to 11.1.2.3, the XPath value that existed in the original version of the policy is no longer present in the OAG 11.1.2.3 version. The filter being used is the "Retrieve attribute from message" Filter.
ERROR
--------
There is no errors during migration.
The XPath value in the "Retrieve attribute from message" Filter is no longer present.
ENVIRONMENT
------------
OAG 11.1.2.3
"Retrieve attribute from message" Filter
STEPS
------
1. Create a policy that uses the "Retrieve attribute from message" filter in OAG 11.1.2.1 and define an XPath expression in the filter.
2. Export the policy to an xml file.
3. Open OAG 11.1.2.3 and choose File--> import and then select the xml file created from the export above.
4. The migration will finish successfully. After completion, click on the imported policy.
5. Click on the "Retrieve attribute from message" filter and notice that the XPath section is empty.
Cause
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
Symptoms |
Cause |
Solution |
References |