Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Troubleshoot Web servers
This section contains information that can assist you in preventing, identifying, and correcting problems related to IBM® WebSphere® Portal Express. For information related to specific components, see the appropriate troubleshooting topic.- Problem: Some pages are not available when using Microsoft Internet Information Server 6.0
- Problem: configure Web_server_name command fails on Linux
- Problem: WebSphere Portal Express hangs while visiting through a local IIS 6.0 Web server
Problem: Some pages are not available when using Microsoft® Internet Information Server 6.0
When attempting to access some pages using Internet Information Server 6.0, you might receive an HTTP 400 - Bad Request error.
Solution: Update the value of the UrlSegmentMaxLength key in the registry. Refer to the INF: Http.sys Registry Settings for IIS for details on updating Web server settings in the registry.Attention: Incorrectly editing the registry could severely damage your system, requiring you to reinstall your operating system. Before making changes to the registry, you should back up any critical data.
- Open the Registry Editor by clicking Start > Run and then entering regedit.
- Locate the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters.
- Create a value named UrlSegmentMaxLength, with a type of DWORD and a value of 0 to indicate an unbounded length.
- Ensure that the plugin-cfg.loc file is located in the same directory as the iisWASPlugin_http.dll or IIS will not be able to use the dynamic link library.
- Exit the Registry Editor by clicking File > Exit and restart the Windows operating system.
Problem: configure Web_server_name command fails on Linux
When configuring a Web server on some Linux systems, the configureWeb_server_name.sh command might fail, with an error similar to the following:Configuration save is not complete, exception = com.ibm.ws.scripting.ScriptingException: com.ibm.websphere.management.exception.ConfigServiceException: com.ibm.websphere.management.exception.ConnectorException: ADMC0009E: The system failed to make the SOAP RPC call: invoke WASX7309W: No "save" was performed before the script "configureWebserverDefinition.jacl" exited; configuration changes will not be saved.Solution: Increase the timeout value for the type of connection you are using:
- SOAP connection: Edit the file was_profile_root/properties/soap.client.properties, and increase the value for the com.ibm.SOAP.requestTimeout property to 6000. The value is in seconds.
- RMI connection: Edit the file was_profile_root/properties/sas.client.props, and increase the value for the com.ibm.CORBA.requestTimeout property to 6000. The value is in seconds.
Problem: WebSphere Portal Express hangs while visiting through a local IIS 6.0 Web server
If a CheckPoint or ZoneLab firewall is installed on your Windows system, portal will hang when visiting through a local IIS 6.0 web server.
Solution: Uninstall the firewall and restart the server.