Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

If you encounter problems with SAS Financial Management and you are asked to increase the logging level, complete the following steps:

Note that this example details the steps to increase the logging level for the "finance" component to DEBUG, but a similar process would be followed to modify the logging level for other components or for setting the logging level to something other than DEBUG.

PLEASE BE AWARE THAT THIS PROCESS IS SIGNIFICANTLY DIFFERENT FOR SAS FINANCIAL MANAGEMENT RELEASE 4.x AND RELEASE 5.x. PLEASE BE CAREFUL TO FOLLOW THE DIRECTIONS BELOW FOR THE RELEASE OF SAS FINANCIAL MANAGEMENT THAT YOU ARE USING.

1. On the mid-tier server, access the directory

   <drive>:\SAS\Config\Lev1\Web\Common\LogConfig

2. Using a standard text editor, open the appropriate <log4j.xml> file that corresponds to the component that you want to increase the logging level for.

   For example, to increase logging for Finance, edit the <SASFinance-log4j.xml> file.

3. Modify the logging level for the specific package.

   For example, to increase logging to DEBUG for "com.sas.solutions.finance", find the entry in the log4j.xml file that resembles

   <logger name="com.sas.solutions.finance" additivity="false">
      <level value="warn"/>
      <appender-ref ref="SAS_FILE"/>
   </logger>
   

   Note: If you do not see an entry similar to this in your <SASFinance-log4j.xml> file, you can add it directly to the file or you can copy and paste from a similar entry and make the necessary changes so it resembles the above.
4. Change the logging level by modifying the 'level value'; for example, change it from "warn" to "debug".
5. Once you modify the logging level, restart the SAS Remote Services and the (WebLogic or WebSphere) application servers to have these changes take effect.
6. Perform the actions that are generating the unexpected results. That should be enough to produce the necessary log output.
   Note that leaving this increased logging level turned on too long will generate too much information and will consume unnecessary system resources. Re-set the logging level to its' prior state (such as "warn"), save the file, then re-start the SAS Remote Services and the (WebLogic or WebSphere) application servers.
7. After that, check the output in the appropriate log file. The log file is written to the output location specified near the top of the log4j.xml file, with the line prefaced by <param name="File">.
   It typically points to a location such as

   <drive>:/SAS/Config/Lev1/web/Logs/SASSolutionsServices/SASFinancialManagement5.1.log

1. Edit the <logging.xml> file, which by default is located at:

   <drive>:\SAS\SASSolutionsConfig\Lev1\web\Deployments\SASSolutionsServices

2. Turn on debugging for <com.sas.solutions.finance> by changing the value of the priority attribute from 'ERROR' to 'DEBUG' and then saving the file. For example:

   <logger name="com.sas.solutions.finance" additivity="false">
      <level value="DEBUG"/>
      <appender-ref ref="CONSOLE"/>
      <appender-ref ref="FILE"/>
   </logger>
   

   If you do not see this context in your <logging.xml> file, you can add it directly to the file or you can copy and paste from a similar logger name and make the necessary changes so it resembles the above.
3. Once you modify the logging level, restart the SAS Remote Services and the (WebLogic or WebSphere) application servers to have these changes take effect.
4. Perform the actions that are generating the unexpected results. That should be enough to produce the necessary log output.
   Note that leaving this increased logging level turned on too long will generate too much information and will consume unnecessary system resources. Re-set the priorities to "ERROR", save the file, then re-start the SAS Remote Services and the (WebLogic or WebSphere) application servers.
5. After that, check the output in the log file. The log file is written to the Output location specified near the top of the <logging.xml> file, with the line prefaced by <param name="File">.
   It typically points to a location such as

   <drive>:/SAS/SASSolutionsConfig/Lev1/web/Deployments/ SASSolutionsServices/server.log

For information on how to dynamically set temporary logging levels for SAS Solutions Web applications using the SAS Solutions Web Administration Application, please refer to SAS Note 31884.

PLEASE NOTE THAT THE SAS SOLUTIONS WEB ADMINISTRATION APPLICATION IS ONLY APPLICABLE FOR SAS FINANCIAL MANAGEMENT 4.x RELEASES.

Operating System and Release Information