Enabling the Apache log4j logging utility for the SAS® Content Server


This note explains how to enable trace logging with the Apache log4j utility for the SAS Content Server in SAS® 9.2, SAS® 9.3, and SAS® 9.4.

Enabling log4j Trace Logging for the SAS® 9.2 Content Server

For details about how to enable log4j trace logging for the SAS 9.2 Content Server, see SAS Note 37753, "Unpacking SAS® Content Server .ear files in order to change logging parameters."

Enabling log4j Trace Logging for Both the SAS® 9.3 Content Server and the SAS® 9.4 Content Server

The steps in this section pertain to the SAS Content Server in both SAS 9.3 and 9.4. There are some slight differences in the page that loads for each release (both pages are shown below), but the steps are the same.

  1. For the SAS Content Server in both SAS 9.3 and SAS 9.4, you can enable log4j traces dynamically. To do that, you need to load the log4j.jsp file by submitting the following URL in Microsoft Internet Explorer or in other supported browsers:

    http://host-name:port-number/SASContentServer/log4j.jsp
     

    Note: In this URL, host-name and port-number specify the actual host name and port number for your configuration.

    Submitting the URL above displays the following pages, respectively, for SAS 9.3 and SAS 9.4:

    SAS 9.3


    SAS 9.4

  2. In the list box at the bottom of the Set New Level column, select DEBUG for all of the loggers. This selection dynamically enables log4j traces for the SAS Content Server. Note: You do not have to restart the SAS server.