Want to add Web Report Studio as a link in the SAS 9.2/9.3 Portal with single sign-on?
Add a Portal application using the following url:
http://<your server>:<your port>/SASWebReportStudio/logonFromPortal.do
Postings about Individual SAS Products
If you need to display the login link on the portal after a user has logged out, Angela has posted how to do it here:
Save User Frustration by adding the magic ‘Log (back) In’ button
Well after a day trying to use the SAS 9.2/4.3 BI Dashboards I think applying the M2 patch set that has just been released is mandatory!
In SAS Web Report Studio 4.3, users can set an option that will display navigational tabs for report sections, similar to the tabs that appeared in version 3.1.
To set this property, make the following changes to the SAS Web Report Studio properties in SAS® Management Console.
When this property is set to true, sections can be accessed via tabs and via the drop-down menu in the Table of Contents pane on the left.
http://support.sas.com/documentation/onlinedoc/gridmgr/index.html
Grid Computing in SAS 9.2, Third Edition
http://support.sas.com/rnd/scalability/grid/grid_testingbench.pdf
http://blogs.sas.com/supportnews/index.php?/archives/126-Demystifying-SAS-Grid-Computing.html
Paper 098-2009 - Data Integration in a Grid-Enabled Environment
Cheryl Doninger, SAS Institute Inc., Cary, NC Nancy Rausch, SAS Institute Inc., Cary, NC
Doing some work to figure out how to remove the Edit tab for a user in WRS 4.3.
Found this table of roles for WRS on the SAS Support site here:
Predefined Roles and Capabilities for SAS Web Report Studio
By the way the trick on the edit tab is to make sure PUBLIC doesnt have access to the WRS roles, which is does seem to by default.
“Note: By default, the PUBLIC group is a member of both the Web Report Studio: Report Creation and the Web Report Studio: Report Viewing roles. So, when you are ready to restrict access to specific capabilities, remember to remove PUBLIC (which includes all users in your deployment) from the applicable roles.”
Usage Note 30789: Implementing the most basic view-only access to reports in SAS® Web Report Studio
| Capability | Report Viewing | Report Creation | Advanced | |
|---|---|---|---|---|
| Basic | ||||
| Comments | X | X | X | |
| X | X | X | ||
| Allow Direct Access to Information Maps1 | X | X | X | |
| Allow Direct Access to Cubes2 | X | X | X | |
| Allow Direct Access to Tables2 | ||||
| Promote WRV to WRS | X | X | X | |
| Refresh Data | X | X | X | |
| Modify Repository | X | X | X | |
| OLAP | ||||
| Drill | X | X | X | |
| Drill to Detail | X | X | X | |
| Expand and Collapse | X | X | X | |
| Expand and Collapse All | X | X | ||
| Output | ||||
| Save | X | X | X | |
| X | X | |||
| Export | X | X | ||
| Schedule Own Report | X | X | ||
| Report Creation | ||||
| Create Report | X | X | ||
| Basic Edit | X | X | ||
| Aggregate or Detail | X | |||
| Select All Data | X | X | ||
| Select Data in View | X | X | ||
| Copy Section2 | X | X | ||
| Advanced Report Creation | ||||
| Create Cascade Reports | ||||
| Create Report Links | X | |||
| Create Remote Application Report Links2 | X | |||
| Advanced Edit | X | |||
| Update Resources3 | X | |||
| Advanced Scheduling | ||||
| Distribute | X | |||
| Save Archive | X | |||
| Schedule Any Report | X | |||
| Schedule Folder | X | |||
| Administrative | ||||
| Manage Distribution List | ||||
| 1 If you are using (or if you migrated from) SAS Web Report Studio 4.2, then the name of this capability is Open Maps as Reports.2 This capability is new in SAS Web Report Studio 4.3.
3 If you are using (or if you migrated from) SAS Web Report Studio 4.2, then the name of this capability is Repair Report. |
||||
In order to be functional, some capabilities have prerequisites. Following is an explanation of each capability and prerequisites for certain capabilities:
If you are using (or if you migrated from) SAS Web Report Studio 4.2, then the name of this capability is Open Maps as Reports.
This capability is new in SAS Web Report Studio 4.3.
By default, this capability is not assigned to any roles because it would allow users to bypass BI row-level permissions. If you have not implemented BI row-level permissions, then consider adding this capability to the same roles to which Allow Direct Access to Cubes is assigned.
This capability is new in SAS Web Report Studio 4.3.
The Report Creation: Basic Edit capability is a prerequisite for this capability. In SAS Web Report Studio, the Include Member with Only Missing Values menu item is available only for multidimensional data sources. The Suppress Empty function in the Advanced Edit capability is required in order for users of multidimensional data sources to view and use the Include Member with Only Missing Values menu item under the Data Menu in SAS Web Report Studio.
I was doing some testing of the new Addin to Microsoft Office (AMO) 4.3/M3 a week or two ago and specifically the addin for Outlook.
When trying to open a SAS Report (.srx) in Outlook we got this error.
Looks like the SAS AMO 4.3 plugin relies on the Web Report Studio web services that automatically get installed when you install the Web tier.
The issue of course is this customer is only using AMO and has not deployed any of the web tier, but in good optimal practice are using Information Maps and .srx reports (created via Enterprise Guide).
So looks like using Outlook to access these .srx is out.
Now I know Kiwi’s (New Zealanders) are known for their number 8 wire approaches and also being frugal (a large number are of course descended from the Scots
, so a number of NZ customers have purchased BI Server and only implemented the SAS Server, Enterprise Guide and AMO, as that meets their current needs. In these cases it looks like using the Outlook version is out of the question.
And with SAS announcing an AMO/EG only offering again use of .srx reports is out im guessing.
Anyway one positive is after playing briefly with the Outlook capability on my test server, I can actually see the Outlook capability taking over from the Portal eventually. Why would users want to login to the Portal to get their reports when they can access them directly from within Outlook where they spend so much of their time?
Stopped by the AMO stand at SAS Global Forum 2011 and had a quick look at the new features coming out.
Things that took my interest:
Bring on Q3 – 2011!
Doing some research on the new SAS Addin for Microsoft Outlook 4.3, to trouble shout an issue at a customer site (more on that later) when I came across this post on the SAS Support site.
It describes a way to change the default content storage options so that when a user saves a document vis the SAS Addin for Microsoft Office, the conent is automatically available via the SAS portal.
I am a great fan of creating content once and making it easily available to as many users as is useful, via their preferred channel. This is a great technique to help with that approach.
Had an interesting experience with the new SAS 9.2 environment at a customer site.
We have got SAS 9.2 (actually SAS Grid but thats irrelevant for this post) installed on RedHat 5 Linux. As we are using Linux and not Windows we lose the standard integration with Active Directory. We didn’t want to implement PAM integration with AD (mainly because nobody can articulate clearly all the steps required to get it working).
So we were left with Host authentication. As we only had a few users in this phase thats not so bad, but as we have a few servers (i.e Grid) I really wanted a easy way to avoid creating userid’s on each server.
Aha I thought Ill use internal SAS user id’s and then get the user to inherit a trusted/host user id to run the SAS processes.
So I setup the user in Metadata with an internal id, made sure they didn’t have a standard user identity (i.e username/pwd against DefaultAuth). Also assigned the user to be a member of SAS General Servers (to inherit sassrv, planned to change this when it worked) and for extra fun added a OraAuth with a username/pwd for the Oracle DB and assigned the user as a member of that as well.
So into DI Studio and Information Map Studio as the user using the internal userid/pwd and:
Now connect using EG 4.3 with same internal userid/pwd and:
mmmmm talk to helpful onsite SAS installer, he could get it to work by adding DefaultAuth in the EG connection in the Auth Domain field. Ok try that and yip all good. So carry on testing.
mmmmm get a could not access Auth Domain.
So into some more tesing, worked out you can type what ever you ant in the Auth Domain connection to get this behaviour (i.e x would do the same as DefaultAuth).
As you do we tried all the combinations we could think of, and no cigar. So helpful SAS installer logged tech suport track and just go this back.:
Followed the distructions and wahoo we have lift off.
So it looks like you can’t use the standard Username/Password authentication method if you want to use internal userid’s/passwords and EG 4.3.
But SAS Token Authentication does work.
Now to test all the other options to see if this change effects anything else, oh the joy of testing …..
Recent Comments