Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Troubleshoot WSRP in the portal
In case of problems you can troubleshoot WSRP in the portal in different ways.
- Debugging and monitoring the WSRP communication
- Setting traces and using the portal run-time log file for WSRP diagnosis
- Monitoring WSRP messages between the Consumer and Producer
- Parallel portlet rendering with remote portlets
Debug and monitoring the WSRP communication
To ease debugging and monitoring of the WSRP communication, the servlet that generates the WSDL document of a WebSphere Portal Express Producer accepts the optional URL parameter port. Use this parameter to modify the ports of the WSRP interfaces that are exposed by that Producer. Specify this parameter as an addition to the URL for the Producer's WSDL document. Here is an example of a Web address that you can enter in your browser, with the port parameter added:
http://producer_portal_host:producer_port/wp_contextRoot/wsdl/wsrp_service.wsdl?port=portValue
Adding this parameter does not configure the actual ports of the WSRP interfaces. A direct communication against these ports will fail. This parameter only changes the values that appear in the WSDL document. Therefore you can use it to monitor the WSRP communication. If the port parameter is missing, then the correctly configured ports of the WSRP interfaces are exposed in the generated WSDL document.
Set traces and using the portal run-time log file for WSRP diagnosis
If you want to diagnose problems that might occur during the use of WSRP with the portal, you can set WSRP specific traces and enable run-time logs for the Consumer, Producer, and administration components of the WSRP implementation. Use the portal administration portlet Enable Tracing to do this. For more detailed information about how to enable portal run-time logging, refer to WebSphere Portal Express logs and Logging and tracing, especially WebSphere Portal Express run-time logs.
You can enable the following trace loggers for the WSRP implementation:
| Component | Trace string |
|---|---|
| Administration | com.ibm.wps.command.wsrp.*=all=enabled com.ibm.wps.wsrp.cmd.*=all=enabled |
| Consumer | com.ibm.wps.wsrp.consumer.*=all=enabled |
| Producer | com.ibm.wps.wsrp.producer.*=all=enabled |
| XMLAccess | com.ibm.wps.command.xml.*=all=enabled |
Monitor WSRP messages between the Consumer and Producer
You can use the TCPMon tool to monitor the WSRP messages between the Consumer and Producer, as described in the WebSphere Application Server Information Center topic Tracing Web services messages. To do this, configure the TCPMon tool to listen on the port that you specified for the optional port parameter. Also, set the target port to the actual port values of the Producer's WSRP interfaces. For the WebSphere Portal Express Producer, these are the ports that appear in the WSDL file when requesting the WSDL without the port parameter.
Run the TCPMon tool using the following command:
- Linux:
java -cp app_server_root/lib/webservices.jar com.ibm.ws.webservices.engine.utils.tcpmon
- i5/OS:
java -cp app_server_root/lib/webservices.jar com.ibm.ws.webservices.engine.utils.tcpmon
- Windows:
java -cp app_server_root\lib\webservices.jar com.ibm.ws.webservices.engine.utils.tcpmon
Parallel portlet rendering with remote portlets
If you encounter errors with parallel portlet rendering of remote portlets in your Consumer portal, try to improve this situation by further increasing the value of the timeout parameter parallelRenderingTimeOut beyond the value of 10000 given further above. For more details about parallel portlet rendering with remote portlets, refer to Parallel portlet rendering.