WSRP Local Proxy Mode Needs to Work in a Cluster Where Managed Servers Have Different Port Numbers On The Same Machine
(Doc ID 974842.1)
Last updated on JULY 13, 2020
Applies to:Oracle WebLogic Portal - Version 10.3.0 to 10.3.1.0.2 [Release AS10gR3]
Information in this document applies to any platform.
As described in Using Local Proxy Mode, local proxy allows co-located WSRP producer and consumer portal applications to short-circuit network I/O and "SOAP over HTTP" overhead by using a producer that is deployed on the same server. The local proxy works when managed servers are pointing to same port number in multiple machines and registering the producer handle with localhost and that specific port.
Consider a cluster of managed servers that are part of the same machine, which cannot have the same port number configured. In that case local proxy would only be effective when the WSRP producer is registered with localhost and with one of the managed servers' ports, which would then route all consumer requests to that particular WSRP producer instance. Hence a mechanism is required to pin the WSRP consumer to the WSRP producer of the same managed server regardless of the port number entered in the WSRP WSDL URL.
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