Configuring Reverse Proxy Servers For WebSphere

To configure the IBM HTTP Server for use as a reverse proxy server, you use the IHS plug-in.

Before you perform the following steps, you need to install the following items:
IBM HTTP Server.
Web server plug-ins.
See PeopleTools Installation for your database platform, Installing Web Server Products, "Installing IBM HTTP Server and Web Server Plug-ins"
To configure IHS for reverse proxy:
Start WebSphere server and open the ISC window.
Navigate to Environment, Virtual Hosts, pia_host, Host Aliases.
The PeopleSoft application is deployed on a virtual host called "pia_host".
Create new entries for the required ports.
For example:
Hostname = *, Port =80/others ports  (for web server port )
Hostname = *, Port =10002 (for HTTP Administration Server port)
Hostname = *, Port =10043 (for SSL port assigned to IHS)
In a multi server environment, repeat the steps 2. and 3. for the other virtual hosts and "psemhub_host".
Click Apply and save the settings to "master".
This updates <HTTP_HOME>/webserv/profile_name/config/cells/node_name/virtualhosts.xml
From the WebSphere Plug-ins installation, copy the configureWebserverDefinition script from the <Plugin_Install_Root>/bin to the directory <PS_HOME>/webserv/profile_name/bin and run it.
This creates the web server definition in WebSphere server.
Generate the plugin-cfg.xml by selecting the web server definition in Servers, Web servers.
Copy the plugin-cfg.xml from <WAS_HOME>/profile_name/config/cells/cell_name/nodes/node_name/servers/WebserverDefinition to <Plugin_Install_Root>/config/WebserverDefinition so that IHS can communicate with WebSphere directly and access the PeopleSoft application.
Restart the WebSphere server, IBM HTTP Server, and IBM HTTP Administration Server.
Verify accessing the PeopleSoft application using the IHS HTTP port.

Note: In scenarios where the system needs to process large amounts of data, a page may become stuck in the processing status. While the change is reflected on the database, it cannot be viewed on a page until another session is started. This problem can be resolved by increasing the ServerIOTimeout from 60 seconds to 600 seconds, for example, in the Plugin-cfg.xml file located in <PLUGIN_HOME>/config/webserver1.