|
|
This chapter includes additional information on troubleshooting WSRP portlets.
When encountering trouble accessing the WSRP Producer from the WLP IDE or online administrative tools, attempt to access the WSRPService.wsdl using a web browser at this address: http://<IP-address>:<port-number>/wsrpproducer/1.0/WSRPService.wsdl
If errors are returned, correct them; if no errors are returned, switch to the WLP Eclipse tools and examine the error log.
Ensure that the WebLogic .portal file has been converted to streaming mode using the instructions in the WebLogic Portal documentation:
http://download.oracle.com/docs/cd/E13218_01/wlp/docs92/portals/intro_to_portal_dev.html#wp1002092
http://download.oracle.com/docs/cd/E13218_01/wlp/docs92/portals/vistools_config.html#wp1027919
WebLogic Portal provides a SOAP monitor to keep track of the SOAP traffic between a WSRP Consumer and Producer. This can help when debugging problems between these two. Instructions for accessing the SOAP monitor can be found here:
http://download.oracle.com/docs/cd/E13218_01/wlp/docs92/federation/Chap-Best_Practices.html#wp1010882
When using the SOAP monitor, it is often helpful to create a new portal file with a single portlet which makes simpler to track the traffic between the Consumer and a single Producer.
The WebLogic Portal WSRP Consumer allows access to resources hosted in remote web applications acting as WSRP Producers. The AquaLogic Interaction .NET Application Accelerator's WSRP Producer is a web application that is separate from the ASP.NET web sites being consumed. As such, WebLogic Portal will need to be configured to allow URL addressable content such as images, style sheets, and JavaScript includes to be returned to WebLogic Portal and a user's web browser.
To do this, a ResourceConnectionFilter must be added to the WebLogic Portal applications as shown below.
| Note: | This code sample works with WebLogic Portal 9.2; for instructions for 8.1.x, see the link under References below. |
<code>
package local;
import com.bea.wsrp.consumer.resource.ResourceConnectionFilter;
public final class AllowAllResourceConnectionFilter
implements ResourceConnectionFilter {/**
* Accept all resource URIs.
* @return always returns <code>true</code>
*/
public boolean allowedURL(String resourceURI) {return true;
}
}
</code>
This class is registered in WebLogic Portal by adding an entry in the appropriate location to the WEB-INF/web.xml file. For example, the following will register the permissive ResourceConnectionFilter implemented above.
<!-- WLP 9.2 ResourceProxyServlet -->
<servlet>
<servlet-name>com.bea.wsrp.consumer.resource.ResourceProxyServlet</servlet-name>
<servlet-class>com.bea.wsrp.consumer.resource.ResourceProxyServlet</servlet-class>
<init-param>
<param-name>resourceConnectionFilter</param-name>
<param-value>local.AllowAllResourceConnectionFilter</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>com.bea.wsrp.consumer.resource.ResourceProxyServlet</servlet-name>
<url-pattern>/resource/*</url-pattern>
</servlet-mapping>
| Note: | This ResourceConnectionFilter is an example and is not suitable for production. In production environments, we recommend that applications constrain allowable URLs to those that are known to produce remote ASP.NET web sites. |
WLP 9.2: http://download.oracle.com/docs/cd/E13218_01/wlp/docs92/javadoc/com/bea/wsrp/consumer/resource/ResourceConnectionFilter.html
WLP 8.1:
http://download.oracle.com/docs/cd/E13218_01/wlp/docs81/wsrp/security.html
Some portals strictly enforce the HTML 4.01 DTD ( http://www.w3.org/TR/html4/strict.dtd). Portlets that use deprecated HTML might not be displayed correctly. Confirm the DTD used by the target portal and design portlets accordingly.
|