Each SAS Web Report Studio user can be assigned to one or more standard roles, which are created for you during installation. A user's role assignment determines which SAS Web Report Studio capabilities are available to that user.
Notes:
By default, SAS Web Report Studio 3.1 analyzes role memberships every 30 minutes. So, for example, if you move a user from the WRS Report Author role to the WRS Report Consumer role, the user will continue to have author privileges until the next time that he logs in after the next role membership analysis is performed.
To enforce role membership modifications immediately, you can restart your sevlet container (Tomcat, Weblogic, or Webshphere).
If you don't want to restart the servlet container every time that you change a role membership, you can increase the frequency of the analysis. To do this, you change the value of <groupCacheTimeoutMinutes> attribute for the <wrs.rolemanager> property in your LocalProperties.xml.
Caution: Analyzing role memberships uses resources, so performing this task more frequently can negatively impact performance.
If you already have a LocalProperties.xml file, then follow these steps:
- Open your LocalProperties.xml file in a text editor.
- Find the <wrs.rolemanager> property and change the <groupCacheTimeoutMinutes> attribute to the new value.
Note: If the <wrs.rolemanager> property is not in your local properties file, then copy the property information from your WebReportStudioProperties.xml file (typically located in the WebReportStudio\WEB-INF folder of the Web application server).
- Add the <wrs.rolemanager> property before the closing </properties> tag. In this example, the <groupCacheTimeoutMinutes> value has been changed to 10 minutes.
Note: The <wrs.rolemanager> property also specifies the SAS Web Report Studio user role names (not shown).
<wrs.rolemanager>
.
.
<groupCacheTimeoutMinutes>10</groupCacheTimeoutMinutes>
</wrs.rolemanager>
|
- Restart your servlet container (Tomcat, Websphere, or Weblogic).
If you do not have a LocalProperties.xml file, then follow these steps to create one, and then complete the steps listed previously.
- In the
customer subdirectory of the SAS Web Report Studio installation directory, locate the LocalProperties.xml.sample file.
- Make a copy of this file and name it
LocalProperties.xml.
For more information about the LocalProperties.xml file, see "Create a LocalProperties.xml File" on page 105 of the SAS 9.1.3 Intelligence Platform: Web Application Administration Guide, Second Edition at http://support.sas.com/documentation/configuration/biwaag.pdf.
Related: SAS Note 30789
Operating System and Release Information
| SAS System | SAS Web Report Studio | Microsoft® Windows® for x64 | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Advanced Server | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Enterprise Edition | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Standard Edition | 3.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows XP Professional | 3.1 | | 9.1 TS1M3 SP4 | |
| Windows Vista | 3.1 | | 9.1 TS1M3 SP4 | |
| 64-bit Enabled AIX | 3.1 | | 9.1 TS1M3 SP4 | |
| 64-bit Enabled Solaris | 3.1 | | 9.1 TS1M3 SP4 | |
| HP-UX IPF | 3.1 | | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
