E-WL: How to Configure WebLogic to Capture Client IP Addresses Behind a Load Balancer when using PeopleSoft
(Doc ID 1968048.1)
Last updated on OCTOBER 18, 2019
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.50 and later
Information in this document applies to any platform.
The purpose of this document is to outline steps to capture the original client IP for a WebLogic Managed Server’s access log without the use of a proxy server with mod_wls plugin. It is specifically meant for a configuration like this:
Client -> Hardware Load Balancer -> Managed Server
There are no proxy servers but more than one Managed Server.
If you have a proxy server using the WebLogic plugin use the solution below:
WebLogic managed servers have access logs, similar to other http server's access logs. A managed server's access log is configured to use the common log format which is used, for example, by the Apache Server.
However, the common log format cannot capture the client's IP address if there is a load balancer between the client at the managed servers; the log format will always log the IP address for the load balancer.
In many instances it is desirable to capture the IP address of the actual client making the request.
The solution described in this document is to configure Extended Log Format with some custom jars for the WebLogic managed servers.
This requires some coding, configuration changes for the managed server and a managed server restart.
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
|1. Configure the Load Balancer to Pass the Clients IP Address to WebLogic using Extended Log Format|
|2. Create Custom Jar|
|3. Add the Custom Jar File to the CLASSPATH|
|4. Configuring Extended Log Format|
|5. Set WebLogic Plug-in Enabled in WebLogic Console|
|6. Testing the Extended Log Format|