Sun Java System Portal Server 7.2 Deployment Planning Guide

Debugging the Gateway

ProcedureTo Check the Gateway Process

  1. Use the following command to see if the gateway process is running:

    /usr/ucb/ps -auxww | grep SRAP

    The following response is displayed:

    /usr/jdk/entsys-j2se/bin/java -Dgateway.profilename=default ... -Dgateway.notification.url=notification -Dgateway.keybase=/etc/opt/SUNWportal/cert/default -Dgateway.pass=/etc/opt/SUNWportal/cert/default/.jsspass -Dgateway.nickname=/etc/opt/SUNWportal/cert/default/.nickname -DLOG_COMPATMODE=Off -Djava.util.logging.config.file=/opt/SUNWam/lib/LogConfig.properties -Dcom.sun.portal.log.config.file=/etc/opt/SUNWportal/platform.conf.default -Dconf.suffix=default -Dserver.name=default -DSRAP_CONFIG_DIR=/etc/opt/SUNWportal com.sun.portal.netlet.eproxy.EProxy &

ProcedureTo Use Debugging

To turn debugging on or off, you set the level of debugging or set it to off.

  1. Log in as root to the Gateway machine and edit the following file:

    /etc/opt/SUNWportal/platform.conf.default

  2. Enable the debug option.

    For example:

    • debug.com.sun.portal.rewriter.original.level

    • debug.com.sun.portal.level

    • debug.com.sun.portal.rewriter.rulesetinfo.level

    • debug.com.sun.portal.rewriter.uriinfo.level


    com.iplanet.services.debug.level=FINEST

    The debug levels are:

    • OFF – Logs no debug messages.

    • Severe – Logs only serious errors in the debug file. Rewriter usually stops functioning when such errors occur.

    • WARNING – Logs errors that indicate a potential problem.

    • FINEST - Logs errors that indicate a highly detailed tracing message.