Extended Monitoring Guide

6. Monitor SSL-Proxied WebLogic Servers
Prev Chapter 19. BEA WebLogic Application Server Next

6. Monitor SSL-Proxied WebLogic Servers

If you are monitoring a web application running on a BEA WebLogic server you may find that the transaction always fails with a code 550 regardless of how you configure the script. This could be a result of the WebLogic server being behind an SSL proxy. When used in this configuration, WebLogic requires that a WL-Proxy-SSL header be added to the request so that it knows to redirect to HTTPS instead of HTTP.

To support this extra header in your Zenoss Web transaction, you must make the following changes on the script tab of your WebTx data source.

  • Remove any content from the Initial URL field.

  • Add the following to the beginning of the Script box.

    add_extra_header WL-Proxy-SSL true
go
Prev Up Next
5. Viewing Raw Data Home 7. Daemons