Adding disclaimers to SAS Web Report Studio tables and graphs is sometimes necessary for confidentiality purposes. You can do this easily by using the Configuration Manager available in SAS Management Console 9.2 and up. This is shown to the right. Adding a Table Disclaimer Through SAS Management Console SAS Support provides official documentation for adding disclaimers in SAS 9.3 as well as SAS 9.2. To add the disclaimer, simply find the “Web Report Studio 4.3″ application under the Configuration Manager through SAS Management Console. Right click and go to the “Advanced” tab and add the property as shown below. Downsides The major downside is the disclaimer gets inserted on every single table and chart produced going forward. Web reports can get very cluttered with the same message. As an alternative I would recommend building a Web Report Studio template with the security message as a footer. Report writers can be educated to always use this template to enforce security policies. I noticed a reference to an XHTML fragment in the LocalProperties.xml file for Web Report Studio… Not sure how this works, but if anybody has any ideas please share! Related content: MDX: Dynamically Hiding Measures for Compliance
Tag: Administration
In this case coolest swag does equal coolest tool
One of the biggest hits of the demo hall at SAS Global Forum was the cute Koala bear swag from MetaCoda.com. Everyone wanted to stop by the booth and pick one up for their badge. Driving people to your booth is the first step, but then you must have co…
Administration: Fall in Love with JBoss Again by Configuring the JGroup Bind Address
As a consultant working for multiple clients, having JBoss installed on a laptop is common to perform demonstrations or to develop SAS BI applications. JBoss can become flaky over time and be a source of frustration for local installations because the operating environment changes very frequently compared to a server environment. Digging through logs trying to find a direct answer to why a report link does not work or why a BI Dashboard indicator will not link properly is a huge headache. I have experienced instances where some web applications work and others do not. A simple configuration task can be performed to prevent a lot of these random issues – especially for mobile laptops which change environments frequently. It involves adding an additional JVM option to the scripts or batch files which start the web application server (JBoss) and the SAS Remote Services service. Binding JBoss The 9.3 Mid-Tier administration guide describes how to set the JGroups Bind Address for JBoss, Weblogic, and WebSphere. The JGroup Bind Address needs to be set for SAS Remote Services and JBoss (or whatever the mid-tier application server is). The bind address MUST be the same for both JBoss and SAS Remote […]
Administration: Cleaning Up the WORK Library Automatically in UNIX
Here is a quick tip for keeping the WORK library clean in a UNIX/Linux environment. Most of the time SAS manages the cleanup process very well but sometimes orphaned processes can leave unwanted data lying around which can build up over time. This tip is only applicable for UNIX or Linux environments. Windows would have a similar approach with different commands. Use a Shell Script for UNIX Heavy Lifting This simple shell script will find all WORK directories created by SAS sessions and recursively remove everything within each directory older than a set time frame. The joys of shell scripting! WORK=/sas/work#!/bin/sh find $WORK/ -mtime +3 -type f -exec rm -rf {} \; exit 0 The WORK variable is set to the physical path of the WORK library on the compute server. The number 3 represents the number of days since the file was last modified. When this script is run, it initiates the find command which finds everything starting from the set directory with a last modified date older than 3 days, then forcibly removes everything within. To prevent any permission problems, it should be run as ‘root’ or any other super user. Why Not Schedule It? This shell […]
Limit the number of drill-through to detail records available from OLAP cubes
Drill-through to detail is the ability to right click within a cell of a web report or OLAP viewer and request the detail source records that make up that specific cell’s measure. The maximum number of records, by default, is set to 300,000. Feasibly t…
Revisiting the starting file location for Enterprise Guide
Years ago and a seemingly far galaxy away, I wrote about how to modify 9.1.3 to start Enterprise Guide users in a different location for the File folder. By default, the user only can access their personal SAS Temporary File. Why change this? I would p…
Promoting SAS BI Dashboard content
If you are unable to export BI Dashboard Content the BI Dashboard Logical types was not installed on the system running SAS Management Console. Update this by following these steps Run the software install from the SAS Depot (mine is located at C:\SAS …
Increasing the web timeout intervals
I’ve been spending my weekends developing a SAS Publishing book proposal. (For those interested, it involves learning how to fully leverage SAS Stored Processes as a beginning programmer.) Creating examples and jumping between coding, testing and then …