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

Monitoring and Logging Remote Portlet Performance

You can monitor activity between Producers and Consumers by using the message monitor servlet installed with WebLogic Workshop. You can also create custom logs to display specific information about WSRP sessions.

This section contains information on these subjects:


Monitoring Producer/Consumer Message Logs

By default, the message monitor is enabled in the web.xml file, as shown in Listing 8-1



Listing 8-1 Enabling Message Monitor in web.xml

<!-- WSRP Message Monitor Servlet -->

You easily monitor the messages regarding Producer/Consumer interaction by viewing output of this servlet. To do, use this procedure:

  1. Ensure that a WSRP session running (that is, a Consumer portlet is surfacing data from a Producer).
  2. Open a new browser.
  3. In the new browser's address bar, type the following:
  4. <host_name>:<port_number>/<webProject_name>/monitor


    For example:


    The Monitor appears in the browser, as shown in Figure 8-1.

    Figure 8-1 Monitor Appearing in a Browser

    Monitor Appearing in a Browser


Each time the remote portlet communicates with the Producer, a request-response message header appears on the monitor screen (Figure 8-2).

Figure 8-2 Monitor Message

Monitor Message



Creating Custom Logs

You can create custom logs that display particular information about a WSRP session by using the WebLogic Server loggers and handlers. These objects allow you to create your own message handlers and subscribe them to the WebLogic Server Logger objects; for example, if you want the remote portlet to listen for the messages that the Producer generates, you can create a handler and subscribe it to the Logger object in the Producer.

loggers and handlers are WebLogic Server objects. For instructions on using them to create custom logs for your WSPR Consumers and Producers, please refer to the WebLogic Server documentation site.


Skip navigation bar  Back to Top Previous Next