As mentioned in my previous post, there is the need to move OLAP cubes around. Switching to one schema to another via SAS OLAP Cube Studio is straightforward enough, but what if you need to move it from one Business Intelligence Environment to another (a Development BI Server to a
SAS recommends building OLAP Cubes on a separate 'non-production schemas' because cube building can be resource intensive and time consuming. Each OLAP Server can be defined to one & only schema at a given time, therefore you will need to setup the architecture to include another OLAP Server & Schema
So you've got a nightly process that updates a file somewhere. Unfortunetly, something still has it locked and the update fails, the nightly process crashes & burns, and someone at 8am upon arriving decides to blast you for not having updated data ready for them to analyze. Sound familar? There
The following option can be added to the Metadata Server to default users to a specific DOMAIN. This removes the requirement of using domainusername or username@domain formats for the username field. -authproviderdomain (HOSTUSER:DOMAINNAME) I made this modification within the file: ..Lev1\SASMeta\MetadataServersasv9_usermods.cfg In SAS Management Console, you must still
Ran across a situation last week that proved extremely helpful. We needed to generate detailed logs on Web Report Studio use in order to verify pooling was setup correctly and then to monitor performance of some poor performers. The easiest and most straightforward way to accomplish this was to follow
Out of the box, no members of the SASUSERS group are allowed to create OLAP Cubes. In 9.2, the error message states "The security package failed while authenticating a user", included below is a screen shot. The fastest way to remediate this is to allow the SASUSERS group to have
Included are some notes on Portal Administration in SAS 9.2. 1. Create a User Group in SMC, include members and a content administrator to this group. 2. Restart the Web Service or Log into Portal as sasadm@saspw (per documentation: http://support.sas.com/documentation/cdl/en/biwaag/63059/HTML/default/ag_permissiontrees.htm) 3. Configure a group content administrator by opening the 'Group
For SAS 9.2 implementations, changing SASADM, SASSRV, and other SAS account passwords has gotten much easier. The SAS 9.2 Deployment Manager Tool (found at /SAS Deployment Manager/9.2/config.exe) can actually be run to complete this task! The section starting with "To update a password with SAS Deployment Manager:" on page: http://support.sas.com/documentation/cdl/en/bisecag/61133/HTML/default/a003071148.htm#a003262956
(SAS 9.2) To get the SAS BI Dashboard to work appropriately, the users who have Role level access to modify and create Dashboards MUST also have read/execute/write access to the BIDashboard configuration folder (example of this location: C:\SAS\EBIserver\Lev1\AppData\SASBIDashboard4.2) 1. SAS Management Console: The Group "BI Dashboard Administrators" by default is
Is the SAS Web Applications timeout of 30 minutes still too short? You can modify these by following editing the .xml files listed on page 15 of SAS Web Application Administration Guide. Here are the steps I took to update the Portal, SAS Web Report Studio and the SAS Stored
