Default SAS Portlets
Friday, July 18th, 2008I always forget what portlets are installed by default in the SAS Portal (compared to the many I add to test etc)
So quick note for myself to remind me (sourced from Understanding Portlets)






|
Blogging about all things SAS |
I always forget what portlets are installed by default in the SAS Portal (compared to the many I add to test etc)
So quick note for myself to remind me (sourced from Understanding Portlets)
If you are aiming to deliver self service report creation to end users, then no doubt you are deploying SAS Web Report Studio to enable them to create and manage reports.
If you have SAS Portal installed it is possible to provide single-signon between WRS and Portal.
In the Portal you create a new Application link and use:
http://webserver:port/SASWebReportStudio/logonFromPortal.do
Once the user has added this to their collection portlet, they can click on it and it will bypass the Web Report Studio login screen, automatically using their authenticated login details.
A SAS stored process is a SAS program that is hosted on a server and described by metadata. One of the major values of stored processes is that they can be consumed by most SAS reporting tools, including SAS Portal, Web Report Studio, Enterprise Guide and the Addin for Microsoft Access.
I have always been a big fan of using them as I believe they are great for creating predefined business rules which users can consume in their reports without having to define any code.
There is an interesting paper at SUGI 31 Making your own Balanced Scorecard using the SAS Information Delivery Portal that describes how a combination of Stored Processes and the SAS Portal can be used to present users with a Balanced Scorecard.
Now if it was me I would have used SAS Strategic Performance Management , but then I hate reinventing the wheel.
But I think the paper shows how with a combination of SAS Portal and Stored Processes, ”there ain’t much you can’t do.