BI Tools

Tips and tricks for building information maps, OLAP cubes, reports, and dashboards

BI Admin

Learn your way around a SAS BI installation.

Visual Analytics

Learn your way around the SAS Visual Analytics tool

Coding & Data

Extract, transform, and load your data into the SAS BI toolset

Stored Processes

Create and design stored processes like a rock star

Home » BI Admin

SAS BI: Easy Customizations for SAS Portal and SAS Web Report Studio

Submitted by on 2012-08-01 – 7:00 AM 7 Comments

Last week I talked about how you could customize the style sheet for Web Report Studio.  One reader,  Kushal Ramani, a SAS consultant from Epoch Research India, suggested that I list some other items that you can easily change in Web Report Studio and SAS Portal.  All of these changes require access to SAS Management Console – so if you don’t have that access you will need to work with your SAS site administrator.

Also I’m using SAS 9.3 – if you are using a previous version then your windows or these locations may be slightly different.

Change the SAS Portal Banner Title

You can make a small tweak to the SAS Information Delivery Portal to replace your organization’s name with the word “SAS Portal” as shown in the following figure.

It’s actually a change so simple it should probably be a sin.  You can find complete details in the SAS Usage Note 37734. Just open up SAS Management Console and do the following:

  1. In the Plug-ins tab, go to Application Management > Configuration Manager > SAS Application Infrastructure.  Locate the Information Delivery Portal item in the list.
  2. Right-click Information Delivery Portal 4.3 and select Properties.
  3. From the Advanced tab, change the Portal.Banner.Title value to the name you want.
  4. Restart the Web Services, which is JBoss for me.
  5. Contemplate how easy that was.

 

Change the Web Report Studio Banners and Page Title

You may want your Web Report Studio banner and page titles to reflect your organization.  Here’s what a standard Web Report Studio report page looks like and some examples of the changes you can make.  You can hide the Product Title and also change the tab to reflect your company name.

You can make these changes in the same place as the Portal change is made.  These changes affect all Web Report Studio reports and users.   Here’s how:

  1. In the Plug-ins tab, go to Application Management > Configuration Manager > SAS Application Infrastructure.  Locate the Web Report Studio 4.3 item in the list.
  2. Right-click Web Report Studio 4.3 and select Properties.
  3. From the Advanced tab, do the following:
    1. Add a new property called webreportstudio.page.title.text and set the value to what you want to appear in the tab.
    2. Add another new property called wrs.banner.product.title.hide and set the value to true.
  4. Restart the Web Services, which is JBoss for me.
  5. It’s okay if you tell your boss you need the afternoon off due to the tremendous stress from making these changes.  It’s our secret!

Prefer a More Bare Look?

Maybe you don’t want any branding or notices on your web reports. You might prefer reports to look more like this image:

This is also a simple property change.  Again this change affects all reports and all users.  The property is called wrs.banner.hide.all and you set it to true.  This property will override other banner properties – so it doesn’t matter if you leave the other property set to true.

In an earlier post, Steve Overton offered the steps for Adding Confidentiality Disclaimer. You can find complete details and a few more properties in the SAS Web Application Administration Guide.

 

Learn all about SAS BI

You can learn more about SAS Business Intelligence from the "SAS BI Bible." Take a peek inside the Building Business Intelligience with SAS book.

The following two tabs change content below.

Tricia Aanderud

Director of Data Visualization at Zencos Consulting
Tricia Aanderud is a SAS Business Intelligence and Visual Analytics consultant based in Raleigh, NC who works for Zencos Consulting. She has written several books about SAS, presented papers at many SAS conferences, and has been using SAS since 2001. Contact her for assistance with your next project.

Tags: , ,

7 Comments »

  • Jen H says:

    Thanks for the encouragement. I do like San Francisco. 🙂

    And SCSUG is due tomorrow – I think I can write 250 words before midnight tomorrrow…

  • Hey Jen you got the makings for a great SAS Global Forum paper here!

  • There was one of those properties I tried but I couldn’t tell what it did. If I get time later I’ll try it.

    I think just being able to move the XML file between DEV, TEST, and PROD would be one major benefit.

  • Paul Homes says:

    Hi,

    I also noticed the following in the “SAS 9.3 Intelligence Platform: Web Application Administration Guide, Second Edition”, under sections “SAS Web Report Studio Administration”, “Introduction to SAS Web Report Studio Administration” on the page “Configuring SAS Web Report Studio” at http://support.sas.com/documentation/cdl/en/biwaag/64769/HTML/default/viewer.htm#p1hwr28egv0xlun1xsz3i2cgzrr7.htm

    Under “Customize the Product and Browser Window Titles for SAS Web Report Studio” it states “You can replace the default titles for the banner and the browser window in SAS Web Report Studio by customizing the properties in the LocalProperties.xml file. You cannot use the Configuration Manager in SAS Management Console to complete this task.”

    However, one of the properties specified there (webreportstudio.page.title.text) is the same one that Tricia modified in this blog post. Perhaps the documentation is in error there? Or perhaps the other property (webreportstudio.product.logo.text) can’t be changed without using LocalProperties.xml? – I haven’t tried it yet myself. If you think it is in error you can let SAS know via the Feedback link at the top of the documentation page – I have used that link from time to time and they’ve been very helpful.

    Personally, I’d prefer to make changes in metadata if I can, but where you can make the changes in either location, I don’t know for sure if there are any significant benefits of one method over the other. To make the changes to the XML file the person would need file system access on the mid tier. I imagine most SAS administrators would have this anyway but perhaps in outsourced environments with split admin roles maybe they don’t? Perhaps metadata defined properties might be easier to manage in a clustered mid-tier environment too?

    BTW Zach Marshall from SAS explained the changes to the Configuration Manager layout in a comment on one of my blog posts “SAS Management Console 9.3 Configuration Manager: Where did everything go?” at http://platformadmin.com/blogs/paul/2011/09/sas-management-console-93-configuration-manager/

    Cheers
    Paul

  • Jen H says:

    Starting to answer my own question… Reading the LocalProperties.xml file on my server, it includes the comments below. (aside, it also includes a nice description of the properties you can change)

    More questions (admitting I haven’t read too much and your book is at the office, not with me now)
    … given all the places things CAN be changed and the number of apps we may want to customize, do we have to repeat these steps for each WRS, STPServer, IDP, etc? Is there a parent location/property that would cascade to all the apps?

    I found I could set webreportstudio.product.logo.text in the “SAS Application Infrastructure” properties and it did show up in WRS. (removing that property from the WRS properties) Seems like doing it here would let me see all my properties for the various products in one place – easier to troubleshoot. Is there a reason this would be a bad idea?

    !-- 1. "local properties" - the optional file LocalProperties.xml, located -->
    !-- in the "customer" folder. -->
    !-- -->
    !-- [ my server path ] -->
    !-- -->
    !-- If this file is present, its values are processed first. SAS -->
    !-- delivers a sample, which can be copied in place then edited. -->
    !-- -->
    !-- 2. "metadata" - properties can be added/modified using SAS Management -->
    !-- Console - Configuration Manager plugin. Select the appropriate -->
    !-- component - typically "Web Report Studio 4.3". The "Settings" and -->
    !-- "Advanced" tabs combine to produce properties from "metadata". -->

    !-- "SAS Application Infrastructure", and can be modified there. -->
    !-- -->
    !-- 3. "WRS properties" - the file WebReportStudioProperties.xml (or -->
    !-- WebReportViewerProperties.xml). This file is stored in the WEB-INF -->
    !-- folder of the web application. For some web containers (WebLogic, -->
    !-- WebSphere) this file is inside the unexploaded ".ear" file - making -->
    !-- it very difficult to modify (hence the need for "metadata" and -->
    !-- "local properties"). This file has a significant advantage in that -->
    !-- a number of properties are provided with comments. The -->
    !-- administrator could read this file, and make suitable changes in -->
    !-- "local properties" or "metadata". -->

  • Excellent questions and comments Jen.

    1 – For SAS 9.3 the docs say this:

    “In previous versions of SAS Web Report Studio, the LocalProperties.xml file offered the only practical method to override properties and their values. Although this file is available and supported in SAS Web Report Studio 4.3, it is recommended that you use the Configuration Manager in SAS Management Console to configure and set properties for SAS Web Report Studio. The Configuration Manager offers a consistent interface to set properties for all SAS applications.”

    I did look at the XML file and it didn’t look to difficult to figure out. I think an advantage may be when you upgrade you can reuse it instead of trying to remember all the little things you had set.

    Do any of you system administrator types have some thoughts?

    2 – Thanks for noting that!

    Let me know if you try the XML method and what thoughts you have about it.

  • Jen H says:

    Thanks for the tips Tricia. They encourage me to just get in there and try things out.

    Comments/questions:

    1) The SAS Docmentation and “Customizing SAS Web Applications” course notes both say to modify the LocalProperties.xml file rather than use Mgmt Console. Do these have the same effect? Would one route be notably preferable to the other? Might they be dependent of user permissions or MgMt Console app?

    3) And FYI for other users, for me to get to the WRS properties, there was one more step in the navigation tree. Under “Configuration Manager” WRS was in the “SAS Application Infrastructure”. Took me a minute to find WRS until I figured that out…

    Win2008R1 server, SAS9.3 and WRS4.3, JBoss, and “reguar” BI (not EBI)