Just saw this post on Chris H’s blog here and I am replicating it so I can find it when I need it. (cause half my posts are there so I can find them when I need them)
If you want to know what version of SAS/Access works with what operating system and what release and what database etc, then look here:
http://support.sas.com/matrix/list?SAS=All&Engine=All&OS=All&googleTrack=on
Well course is over and I passed, so wahoo for me!
I am blogging all my tweets from the course so it is easier for me to search them in the future.
(more…)
SAS 9.2 now has the concept of External Identities against a user or group.
The following is an extract of the online help:
(more…)
Setting up SAS Share to enable you to Import and Export ABM models is one of those things that always seems to be a bit tricky to get working.
I found a public doc on the old ABC Tech support site here, that explains the steps. I have also cut and paste the content below in case the doc disappears.
One thing to note is that if you have two SAS servers wanting to talk via this SAS Share link (i.e one with SAS ABM and the other with SAS DI or EG etc) you need to make sure the SAS Share names are identical on both servers or it wont work!
Oh and don’t forget that you need SAS Share OLEDB client on every PC that wants to export/import. You can install this from the SAS ABM Client install page on your ABM Webserver.
(more…)
While researching and testing the default Web Report Studio metadata security I noticed this little trick for young players, which means changes to WRS/WRV Metadata Security for a user are not instantly applied/recognised in WRS/WRV.
Words from the SAS tech support note “Changes to SAS® Web Report Studio role memberships might not immediately be enforced“:
“SAS Web Report Studio 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. ”
So effectively the WRS/WRV applications are caching the Metadata security to remove the need for the web server to query the Metadata Server each time a user logins.
So try not to be fast when testing your WRS Metadata security changes, else you will think you have done something wrong. And remember to logout and log back in after the cache has been updated.
You can update the LocalProperties.xml file to change the refresh time, and therefore make the changes appear sooner. Details on how to do this are in the SAS Tech Support note.
Researching definitions for each of the WRS default roles as part of the Advanced Metadata Security course.
The roles are documented in the SAS 9.1.3 Intelligence Platform: Web Application Administration Guide, Second Edition on page 130. What it says is:
“By default, everyone who can log on to SAS Web Report Studio can view, edit, and create new reports.
To implement security, each user of SAS Web Report Studio can be assigned to one or more standard roles. A user’s role assignments determine which SAS Web Report Studio menu items are available to that user.
-
By default, all SAS Web Report Studio users implicitly have the role. However, if you explicitly assign any members to the role, then only the explicitly-assigned members will have the role. This enables you to start using SAS Web Report Studio immediately after installation, yet still have the ability to restrict user access when locking down your deployment.
-
Each role is a superset of the preceding role. For example, members of the “WRS Report Author” role have all the permissions that apply to the “WRS Report Consumer”.
-
Once you explicitly assign members to a role, you must explicitly assign membersto each superset role. For example, if you assign members to the “WRS ReportAuthor” role, then all of the subsequent superset roles (in this example, “WRSAdvanced User”) also become explicitly-assigned roles. The reason is that WRSAdvanced User is a superset of WRS Report Author.
-
Once you explicitly assign members to a role, then any user who is not assigned to a role, or who has no metadata identity, can only view reports and manipulate reports (for example, select new data items to view in report objects).
| WRS Report Consumer |
Users who have this role can view reports and manipulate report data in the View Report view. Users can copy, move, save, rename, or delete reports. Users cannot create new reports with the report builder or report wizard.
|
| WRS Report Author * |
In addition to the abilities assigned to WRS Report Consumers, users who have this role can create reports with the report builder or report wizard. Users can also schedule reports.
|
| WRS Advanced User |
In addition to the abilities assigned to WRS Report Authors, users who have this role can distribute reports. Users cannot create or delete recipient lists that are used for report distribution.
|
| WRS Administrator |
Users who have this role can perform all tasks that are associated with SAS Web Report Studio, including the ability to create and delete recipient lists that are used for report distribution.
This role provides full permissions to SAS Web Report Studio and should be safeguarded accordingly. This role provides application level administrator functionality. However, this role has no effect on metadata access (authorization) rights to report data.
|
| WRS Prohibited |
Users who have this role cannot log on to SAS Web Report Studio. Regardless of the user’s membership in any of the previous roles, if the user attempts to log on, the logon page displays the following error message: “This user is not allowed to access SAS Web Report Studio. Please contact your administrator.”
Some organizations might apply this role for users who are allowed to access some SAS applications but not SAS Web Report Studio. Alternatively, if an organization has multiple Web Report Studio installations, this role can be used to restrict some users from specific instances.
The corresponding metadata group entity is not created during installation. You must manually create the group in metadata if you want to use this user role.
|
*By default, WRS Report Authors can schedule reports, though you can change the default behavior and limit the scheduling feature to WRS Advanced Users. To do this, in your LocalProperties.xml file, specify true for the schedulingRequiresAdvancedUserRole property.
|
I posted earlier about the removal of the Public Kiosk in SAS 9.2 / Portal 4.2.
All the feedback I got stated that they turned off the Public Kiosk in SAS 9.1.3 / Portal 2.x as a matter of course.
Just noticed a SAS Tech support notice “Enabling unchallenged access to content in SAS® Information Delivery Portal 4.2” which outlines how to allow access to the portal without the need to login.
So obviously a few people still wanted it.
If you ever need to deploy WRS to the Web Server after an install (or wondered how SAS did it for you) there is a great SAS Support Tech Note that explains the process.
It covers deploying to Web Logic, Websphere and Tomcat.
Find it on the SAS Support site here:
Configuring and Deploying SAS® Web Report Studio
Having an issue where our BEA Managed Server is blowing the JVM limit (32bit windows) and so crashed.
Found this and needed to remember it, so excuse the note to self
Formulas for calculating memory
The following formulas give an approximation of how you need to set the arguments. These
formulas are not exact and may need to be adjusted according to your processing needs.
MEM_INT=MEM_MAX
NEWSIZE=MAXNEWSIZE=1/3 OF MEM_MAX
PERMSIZE=MAXPERMSIZE
PERMSIZE < MEM_INT
MEM_MAX MAXPERMSIZE <= 3/4 physical memory
MEM_MAX MAXPERMSIZE <= 4GB RAM
ABCtech (who created Oros and who SAS brought a few years ago) created a tool called Easy API that enables you to automatically submit a Import. Export or Calc in ABM.
The utility is a visual basic script (.vbs) that requires a few parameters in a txt file.
One of those parameters is ABM server, but unfortunately nowhere does it describe what this connection string should be. Well in case you wanted to know this worked for us:
http://hostname/SasSolutions/ABM/Services/AutomationService.asmx
and how could you not know that you would ask …..