Skip navigation.

Using WSRP with WebLogic Portal

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

Working with Producers

The main focus of this chapter is to explain how to use WSRP with applications running in a WebLogic Server or WebLogic Express domain. In addition, this chapter explains how to install a producer into a WebLogic Server domain using WebLogic Workshop and how to specify which portlets deployed in a producer application are available to consumers.

This chapter includes the following topics:


Using WSRP in a Basic WebLogic Server Domain

This section explains how to configure a basic WebLogic Server domain as a WSRP producer. The example in this section assumes that you have a functioning Struts module deployed in a WebLogic Server domain.

Note: To complete the steps outlined in this section, you must have access to certain JAR files that are part of a WebLogic Portal installation. If you do not have WebLogic Portal installed, we recommend that you obtain a freely available installer from the BEA Systems website and install WebLogic Portal in a separate, temporary area. You can then copy the required JAR files to your producer web application and delete the temporary installation area.

The goal of this procedure is to create a portlet in a producer that can be consumed remotely. To achieve this, you need to modify the configuration of your Struts application, copy appropriate JAR and TLD files to the application, and create a portlet that references the Struts module in which your application resides.

By following this procedure, you can expose a Struts application as a remote portlet that a WebLogic Portal application can consume, as illustrated in Figure 4-1.

Figure 4-1 WebLogic Portal consumer consumes Struts portlets from a WebLogic Server producer

WebLogic Portal consumer consumes Struts portlets from a WebLogic Server producer


This section contains the following sections:

Getting Started

Before you configure the producer, we assume you have taken the following steps:

Note: We recommend that only experienced Struts and WebLogic Portal developers attempt this procedure. It is easy to make simple mistakes that can be difficult to troubleshoot. Whenever possible, we suggest ways to test your progress.

As noted previously, it is crucial that you have a Struts module that you can deploy and run successfully in the WebLogic Server environment before you configure the producer. Note that the Struts application must be configured as a Struts module. For detailed information on configuring Struts modules, refer to the Struts documentation. Basically, a module resides in a subdirectory of the web application and has its own struts-config.xml file, whose path is specified typically in the web.xml file.

Tip: Before trying to use your Struts application in a WSRP environment, try converting the application to a local portlet running in a WebLogic Portal domain. If you can convert the Struts application to a local, standalone portlet in a test environment, then your chances of running it successfully with WSRP are improved. To do this, you need WebLogic Workshop. You can download a free developer's version of WebLogic Workshop from the BEA website. For information on converting a Struts application to a portlet using WebLogic Workshop, see: Integrating Struts Applications into a Portal.

Configuring the WSRP Producer

This section explains how to configure a basic WebLogic Server domain as a WSRP producer. The goal of this procedure is to surface a Struts application as a remote portlet that can be consumed by a WebLogic Portal application.

Modify the CLASSPATH for the WebLogic Server Domain

Note: Before attempting to expose a Struts portlet with WSRP, be sure the underlying application is configured as a module and works properly before you attempt to configure the WSRP producer. We also recommend that you try to create a functioning local portlet using WebLogic Workshop. See Getting Started on page 4-2 for more information on this recommendation.

  1. Modify the CLASSPATH for the WebLogic Server domain. Open the following script file:

On Windows: DOMAIN_HOME\startWebLogic.cmd


Find the CLASSPATH definition, and add the following elements:

Note: Be sure there are no newlines within the CLASSPATH elements. Do not delete any of the elements that are already assigned to the CLASSPATH.

On Windows:


On Linux:


Listing 4-1 shows an example of the completed CLASSPATH for a Windows system.

Listing 4-1 CLASSPATH Example for Windows

  1. Create the portal-specific directories that you added to the CLASSPATH and copy the appropriate JAR files into them. If you do not have a WebLogic Portal installation, you need to install WebLogic Portal in a temporary area and copy the JAR files from there. See the note at the beginning of this section for more information on obtaining an installer. For example, the JAR files wsrp-common.jar, netuix_schemas.jar, netuix_system.jar must be on your system in the location referenced by the CLASSPATH.
  2. Checkpoint: Restart your server to ensure that the startup script functions properly. Be sure that your Struts application is deployed and works as well.

Modify the Struts Application

In this section, you will modify the Struts application. This process includes modifying configuration files and adding/replacing files within the application. The configuration files need to be updated to reference BEA-specific classes and tag library files. These components are required for the application to function within a WSRP environment. For instance, the BEA tag libraries ensure that URL rewriting for the portlet is handled properly.

  1. It is recommended that you copy the root folder of your Struts application to a new folder. You can then make changes to the new copy and preserve the original.
  2. Modify the Struts application's web.xml file as follows:

Be sure that the following elements are in your Web application's web.xml file. If any of these elements are missing, you must add them:

<!-- WSRP Servlet configuration -->
<!-- WSRP Servlet mapping -->
<!-- Standard Action Servlet Configuration (with debugging) -->
<!-- WSRP Struts Adapter Tag Library Descriptors --> 
<!-- Struts Tag Library Descriptors --> 
<!-- COMMENTED in favor of WSRP adapter Tag Libraries -->
  1. Copy the following TLD files to the WEB-INF\lib directory of the Struts application:
  1. Copy the following JAR files to the WEB-INF\lib directory of the Struts application:
  1. Copy the following JAR files to the WEB-INF\lib directory of the Struts application:
  1. Checkpoint: Start your server and redeploy the Struts application now to test that it still works. If the application does not work properly, you need to recheck the preceding steps.
  2. Copy the contents of Listing 4-2 and paste it into a file named wsrp-producer-config.xml in the Struts applications's WEB-INF directory.

Listing 4-2 wsrp-producer-config.xml

<?xml version="1.0" encoding="UTF-8"?>
    xsi:schemaLocation=" wsrp-producer-config.xsd">
       This is a WSRP Producer
    <!-- This element describes the capabilities of this producer. Set
    the secure attribute to "true" if you require this producer offer
    any port over SSL. If this webapp is portal-enabled, you may
    enable registration and portlet management services by setting the
    required attribute to "true". -->
        <registration required="false" secure="false"/>
        <service-description secure="false"/>
        <!-- Set accepts-mime to true to more efficiently process uploaded files         when the consumer is a WebLogic Portal. -->
        <markup secure="false" rewrite-urls="true" 
         transport="string" accepts-mime="false"/>
        <portlet-management required="false" secure="false"/>

Note: Be sure the registration required and portlet-management required parameters are set to false.

  1. Add the following line to the struts-config.xml file of your Struts module.
<controller processorClass=
  1. Create a portlet to surface the Struts actions that you want to expose as a remote portlet to consumers. Place the portlet in a .portlet file in the directory containing the module you want to surface.
  2. For example, if you have a action in a module called echo in the /echo subdirectory, the portlet file looks like the following:

Listing 4-3 Example Portlet

<?xml version="1.0" encoding="UTF-8"?>
<portal:root xmlns:html=""
xsi:schemaLocation=" portal-support-1_0_0.xsd">
<netuix:portlet definitionLabel="portlet_sayHello" title="WSRP Echo      Example">
<netuix:strutsContent action="welcome" module="/echo"/>
  1. Checkpoint: Start the server (if it isn't running), redeploy the Struts application, and make sure it functions properly.

Testing the Producer

This section describes a procedure for testing your producer configuration.

  1. Start WebLogic Server with the new CLASSPATH setting.
  2. Use WebLogic Server Console to deploy (or redeploy) the Struts web application.
  3. Open a web browser and test the Struts web module that you want to surface. The module should work normally.
  4. Test the WSRP producer by entering its WSDL URL in a browser. For example, if your Struts application is called myStrutsApp, the WSDL URL is:
  5. http://host:port/myStrutsApp/producer?wsdl

    where host is the IP address of the server machine, port is the server's listening port number, and myStrutsApp is the root name of the Struts web application.

    If this test is successful, an XML Webservice WSDL file is returned that looks similar to the file shown in Figure 4-2.

    Figure 4-2 XML Webservice WSDL File

    XML Webservice WSDL File


Consuming the Producer Portlet

  1. On another machine, create a WebLogic Portal Domain. You can use the WebLogic Configuration Wizard to do this. If you cannot use another machine, be sure the server's listen port does not conflict with the port used by the producer server. If necessary, you can obtain a free developer's version of WebLogic Portal by visiting the BEA website.
  2. Use WebLogic Workshop to create a Portal Application and associate the application with the new WebLogic Portal Domain. If necessary, you can obtain a free developer's version of WebLogic Workshop by visiting the BEA website.
  3. Create a new Portal Web Project to the application. This application is the consumer application.
  4. Create a portal in the consumer application.
  5. Start the server that hosts the consumer.
  6. Create a remote portlet in the Portal Web Project you just created. Point the WSDL to the Struts application on the producer. For example:
  7. http://producerHost:producerPort/StrutsApp/producer?WSDL

    Where producerHost:producerPort is the IP address and port number of the machine hosting the producer, and StrutsApp is the name of the context directory for the Struts application that contains the producer portlet(s) that you wish to surface.

  8. On the consumer, add the remote portlet to the portal and open the portal. The Struts portlet you created on the producer appears in the portal.


Using WSRP in a WebLogic Express Server Domain

You can configure a WebLogic Express (WLX) server domain as a WSRP producer. To do this, follow the same steps outlined in the previous section, Using WSRP in a Basic WebLogic Server Domain on page 4-1. The procedures for configuring a WLX domain and a WebLogic Server domain as a producer are the same.


Enabling Portlets on the Producer

A Producer can have any number of portlets built on it, sometimes into the thousands. By default, all of these portlets are available to consumers as remote portlets. You can, however, specify which portlets are actually available to consumers by setting the offerPortlets property in the Portlet Property Editor.

Figure 4-3 Proxy Portlet Property Editor—Offer as Remote Property Selected

Proxy Portlet Property Editor—Offer as Remote Property Selected


For instructions on how to set this property, please refer to Enabling/Disabling a Portlet for Remote Consumption in the WebLogic Workshop online help system at:


Skip navigation bar  Back to Top Previous Next