Configure the Web server
Overview
By default WebSphere Portal uses the internal HTTP transport within WAS to handle requests, but if you have an external Web server, such as IBM HTTP Server, you can configure WebSphere Portal to use the Web server. Use a local Web server on the same machine as WebSphere Portal, or you can use a remote Web server on a different machine.
A configuration template may exist to support these instructions. Refer to the...
/qibm/proddata/portalserver5/config/helpers...directory for available configuration templates. Use the configuration template to update the wpconfig.properties file according to the property descriptions and recommended values provided below. If you do not want to use a configuration template, follow these instructions.
Configure for a local Web server
To configure WebSphere Portal to use the Web server, complete the following steps:
- Verify that the Web server is running.
- Locate...
/qibm/UserData/webas5/base/<instance>/portalserver5/config/wpconfig.properties...and create a backup copy before changing any values.
- Use a text editor to open...
/qibm/UserData/webas5/base/<instance>/portalserver5/config/wpconfig.propertiesUncomment and verify the following properties for the environment.
Section of properties file Property Value WAS properties WpsHostName Fully qualified host name of the machine running WebSphere Portal. For example,... www.setgetweb.comDefault: localhost
WpsHostPort Port number that your external Web server is currently listening for HTTP traffic. For example, 81. Default: 80
- Save the file.
- Configure WebSphere Portal for the Web server
cd /qibm/UserData/webas5/base/<instance>/portalserver5/config
WPSconfig.sh httpserver-config- Regenerate the Web Server Plugin by pulling up the WAS administrative console and clicking...
Environment | Update Web Server Plugin | OK- Restart the Web server.
- Restart WebSphere Portal:
STRQSH
cd /qibm/proddata/webas5/pme/bin
stopServer -instance <instance> <app_server>
startServer -instance <instance> <app_server>
Configure for a remote Web server
The WebSphere Web server plug-in can be installed into a Web server located on a separate (remote) server from the WAS. The Web server plug-in uses an XML configuration file (plugin-cfg.xml) containing settings that describe how to handle and pass on requests to the WASs made accessible through the plug-in.
Configure WebSphere Portal for the Web server
To configure WebSphere Portal for the remote Web server, following these steps:
- Locate the file...
/qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties...and create a backup copy before changing any values.
- Edit...
/qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties...and verify the following properties for the environment.
Note the following information:
- Do not change any settings other than those specified in these steps.
- You can also modify the wpconfig.properties file locally on the iSeries system by entering the following on an OS/400 command line:
EDTF '/qibm/userdata/webas5/base/<instance>/portalserver5/config/wpconfig.properties'- Some values, shown here in italics, may need to be modified to the specific environment.
Section of properties file Property Value WAS properties WpsHostName Fully qualified host name of the machine running WebSphere Portal. For example, www.ibm.com
Recommended: localhost
Default: localhost
WpsHostPort Port number that your external Web server is currently listening for HTTP traffic. For example, 81.
Recommended: 80
Default: 80
- Save the file.
- Open a command prompt and start the Qshell Interpreter by entering the following:
STRQSH- Change directory to /qibm/UserData/webas5/base/<instance>/portalserver5/config.
- Enter the following command to configure WebSphere Portal for the Web server:
WPSconfig.sh httpserver-config- Restart the Web server.
- Restart WebSphere Portal...
cd /qibm/proddata/webas5/pme/bin
stopServer -instance <instance> <app_server>
startServer -instance <instance> <app_server>...where instance is the name of the WAS instance, and app_server is the name of the application server. Note: The default name of the application server is the instance name.
- Verify that WebSphere Portal can be accessed from the remote Web server. For example, open a browser to...
http://<webserver_hostname>:<port_number>/wps/portal.
Next steps
You have completed this step. Continue to the next step by choosing one of the following topics:
See also