TagWeb Report Studio

Locating the Log Files for the SAS 9.3 Middle Tier

SASI have been doing some maintenance recently on one of our SAS EBI installations and needed to review the logs generated by the middle tier.  At some point any BI administrator will have to do this, so here are the default locations, directly from SAS:

The log files for the SAS 9.3 middle tier are located in the following directories:

Application Servers

Red Hat JBoss

  • /JBoss-home-directory/server/SAS-JBoss-server/log/server.log
  • /JBoss-home-directory/server/SAS-JBoss-server/log/boot.log

Oracle WebLogic

  • If WebLogic is started as a service, a UNIX daemon, or a batch process, the location is
    /WebLogic-home-directory/user_projects/domains/domain/servers/managed-server/logs/server.log.
  • If WebLogic is started using the Node Manager, the location is
    /WebLogic-home-directory/user_projects/domains/domain/servers/managed-server/logs/server.out.

IBM WebSphere

  • /WebSphere-home-directory/AppServer/logs/server/SystemOut.log
  • /WebSphere-home-directory/AppServer/logs/server/SystemErr.log

WebDAV Server

  • SAS Content Server:
    /SAS-configuration-directory;/Lev1/Web/Logs/SASContentServer9.3.log

SAS Web Applications

  • SAS Admin:
    /SAS-configuration-directory/Lev1/Web/Logs/SASAdmin9.3.log
  • SAS BI Dashboard:
    /SAS-configuration-directory/Lev1/Web/Logs/SASBIDashboard4.3.log
    /SAS-configuration-directory/Lev1/Web/Logs/SASBIDashboardEventGen4.3.log
  • SAS BI Portlets:
    /SAS-configuration-directory/Lev1/Web/Logs/SASBIPortlets4.3.log
    /SAS-configuration-directory/Lev1/Web/Logs/SASJSR18RemotePortlets4.3.log
  • SAS BI Web Services:
    /SAS-configuration-directory/Lev1/Web/Logs/SASBIWebServicesforJava9.3.log
  • SAS Information Delivery Portal:
    /SAS-configuration-directory/Lev1/Web/Logs/SASPortal4.3.log
  • SAS Logon Manager:
    /SAS-configuration-directory/Lev1/Web/Logs/SASLogon9.3.log
  • SAS Package Viewer:
    /SAS-configuration-directory/Lev1/Web/Logs/SASPackageViewer4.3.log
  • SAS Preferences:
    /SAS-configuration-directory/Lev1/Web/Logs/SASPreferences9.3.log
  • SAS Remote Services:
    /SAS-configuration-directory/Lev1/Web/Logs/RemoteServices.log
  • SAS Shared Apps:
    /SAS-configuration-directory/Lev1/Web/Logs/SASSharedApps9.3.log
  • SAS Stored Processes Web Application:
    /SAS-configuration-directory/Lev1/Web/Logs/SASStoredProcess9.3.log
  • SAS Web Report Studio:
    /SAS-configuration-directory/Lev1/Web/Logs/SASWebReportStudio4.3.log
    Note: Beginning with the second maintenance release for SAS 9.3 (TS1M2), the log is named SASWebReportStudio.log
  • SAS Web Infrastructure Platform Client Access:
    /SAS-configuration-directory/Lev1/Web/Logs/SASWIPClientAccess9.3.log
  • SAS Web Infrastructure Platform Services:
    /SAS-configuration-directory/Lev1/Web/Logs/SASWIPServices9.3.log
  • SAS Web Infrastructure Platform SOAP Services:
    /SAS-configuration-directory/Lev1/Web/Logs/SASWIPSoapServices9.3.log
  • SAS Workflow Services:
    /SAS-configuration-directory/Lev1/Web/Logs/SASWorkflowServices9.3.log

In my case, I was looking for my Websphere application server logs.  And as I should have suspected, my System Admin did not have the application servers or the log directories installed in the typical locations, so I had to do a little hunting.

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

Report Events in the SAS Key User Action Log

saslogofrom the SAS 9.2 Intelligence Platform Web Application Administration Guide,
Third Edition, located at:

http://support.sas.com/documentation/cdl/en/biwaag/63536/PDF/default/biwaag.pdf

The information in the Key User Action Log can be imported into SAS data sets and presented in reports. To report the data, follow these steps:

  1. Import the WebReportStudio_KeyActions.log data into a SAS data set. Here are the main steps:
    1. Assign a libref to an XML file that contains log data, and specify the XML engine.  In the following example, MyFile.xml is a copy of a Key User Action Log file:
      libname myxml xml ’C:\My Files\XML\MyFile.xml’;
    2. Use the SAS data sets procedure to import the XML file into a SAS data set.
      Here is an example:
      proc data sets library=myxml;
      This code creates a data set named EVENT in the MYXML library.
      For more information, see SAS online Help and documentation.
  2. In SAS Information Map Studio, create an information map based on the data set that you created in the preceding step. For the information map, you might want to provide the ability to filter based on the event code (<code> tag), the user name (<user> tag), the report name (<report> tag), or the date (<date> tag). For information about using SAS Information Map Studio, see the product Help.
  3. 3 In SAS Web Report Studio, define a report based on the information map that you created in the previous step. You can define the report to be refreshed manually, and then schedule the report to run at regular intervals.
Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

New Features to be Included in SAS Enterprise Guide 4.3

saslogo I was one of the unfortunate ones who was unable to attend the SAS Global Forum in Seattle last week.  Thanks to discussion forums, blogs, and Twitter, I was able to keep up with a lot that was going on.  I was particularly interested in some of the new features that will be available in the next version (4.3) of Enterprise Guide, which is scheduled to be available this summer.  Below are some of the features that were mentioned:

  • context sensitive keyword completion (syntax suggestion)
  • relative file addressing
  • code reverse engineering (see what old code is doing)
  • an autoexec process flow for projects (runs automatically when project is opened)
  • code analyzer (reads a program and turns it into a process flow)

I also had the opportunity to preview some of the new features in the upcoming version of Web Report Studio (4.3).  SAS is expanding drag and drop capabilities, which makes creation of report even easier.  The biggest news though is the ability to use more than one data source in a report section!

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

Dynamic Text that can be Included in Headers and Footers in SAS Web Report Studio 3.1 Reports

from support.sas.com:

Data source name
The name of the relational or multidimensional data source that is being used for the view elements in the report section. (Does not apply to stored processes.)
Data source description
If available, the description of the relational or multidimensional data source that is being used for the view elements in the report section. (Does not apply to stored processes.)
Date the data was last refreshed
The date and time that the query for data was last sent from SAS Web Report Studio to the underlying source of data. The format of the time value is based on the locale set for the middle tier.
Report author
If available, the name of the report author. Otherwise, the user ID of the report author is used.
Report date
Either the date and time that the report was created, or the date and time that changes to the report were last saved. The format of the time value is based on the locale set for the middle-tier.
NOTE: If you save changes in the current session, you must close and then reopen the report in order to refresh the report date.
Report description
If available, the description of the report.
Report name
The name of the report.
Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

© 2017 Technoleros

Theme by Anders NorénUp ↑