Using the WLST Command updateWebgateTemplateToWebgateMapping() To Add or Update the Webgate PrimaryServerList or SecondaryServerList Corrupts the Entry Completely
(Doc ID 2643011.1)
Last updated on SEPTEMBER 20, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Symptoms
Following the documentation to use the WLST command createWebgateTemplate() to create a webgate template to add or update values in the primary server list or the secondary server list causes corruption of the ObAccessClient.xml file section for the OAM server connection settings section.
For example, the following attempts to update the numOfConnections value will result in an incorrectly defined file:
Test #1
=====
createWebgateTemplate(webgateTemplateName="TemplateA", webgateParamsList="PrimaryServerList/0/numOfConnections", webgateValuesList="34")
Results in the following:
<Setting Name="PrimaryServerList/o/numIfConnections" Type="xsd:string">numOfConnections:34</Setting>
Test #2
=====
createWebgateTemplate(webgateTemplateName="TemplateA", webgateParamsList="PrimaryServerList", webgateValuesList="numOfConnections=34")
Results in the following:
<Setting Name="PrimaryServerList" Type="xsd:string">numOfConnections:34</Setting>
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 |