Newcomers to SAS Viya Administration may appreciate these tried-and-tested patterns for securing folders, and the content within them (reports, data plans, models etc.). If you are new to security model design in SAS Viya, this post is for you.
Understanding SAS 9.4 architecture is key to tackling the tasks and responsibilities that come with SAS administration, and will help you know where to look to make changes or troubleshoot problems.
When working with files like SAS programs, images, documents, logs, etc., we are used to accessing them in operating system directories. In Viya, many of these files are not stored on the file-system. Let's look at where and how files are stored in Viya, and how to manage them.
From an Enterprise Guide user's perspective, a SAS library is a library. Whether it was defined in the autoexec or in the metadata or by magic, it is there for them to use with no issues. However, there is a difference as metadata defined libraries do not behave in the
BASE SAS users are already familiar with the autoexec file. This is a .sas file that typically resides in the installation folder of the SAS executable. Instructions for setting it up in UNIX, Windows, and other environments is readily available on the SAS website. In SAS BI configurations there are
After installing SAS Business Intelligence, I would also suggest verifying that all is working appropriately before adding users or importing content from another machine. (My template checklist is included below.) The act of creating the content is an extremely important test (to immediately rectify issues with accessing data, or saving
Six user import and synchronization macros are available in the SAS Foundation directory, these are documented as available in creating programs to retrieve information and compare authentication provider (such as LDAP) account information with what is stored in SAS Metadata to then synchronize the two. Try this code in BASE
Did you change your LinkedIn password yesterday? (If you didn’t, you should!) But did it happen to be the same as your corporate password? First, tisk tisk. Second, change your corporate password NOW! Ok, now that this is done ~ don’t let your saved connection profile for SAS applications lock
One of the biggest hits of the demo hall at SAS Global Forum was the cute Koala bear swag from MetaCoda.com. Everyone wanted to stop by the booth and pick one up for their badge. Driving people to your booth is the first step, but then you must have cool
Drill-through to detail is the ability to right click within a cell of a web report or OLAP viewer and request the detail source records that make up that specific cell's measure. The maximum number of records, by default, is set to 300,000. Feasibly the report user could download all
Years ago and a seemingly far galaxy away, I wrote about how to modify 9.1.3 to start Enterprise Guide users in a different location for the File folder. By default, the user only can access their personal SAS Temporary File. Why change this? I would prefer to use a central
If you are unable to export BI Dashboard Content the BI Dashboard Logical types was not installed on the system running SAS Management Console. Update this by following these steps Run the software install from the SAS Depot (mine is located at C:SAS Software Depotsetup.exe) Select ‘Install Additional Software’ Then
Which would you rather do? Click stop (or start) over and over, while waiting in between the services to make sure everything is up and running ... OR ... click one button and go have lunch? Honestly I prefer the lunch option. (And for administrators, the quickest option is always
In SAS 9.2, internal accounts can be created and utilized within the metadata and then do not require host (or domain) accounts defined elsewhere. By default, the sasadm@saspw is one such internal account. Unless you specifically declare an exception, the server-level policies for routine password resetting and locking (such as
(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:SASEBIserverLev1AppDataSASBIDashboard4.2) 1. SAS Management Console: The Group "BI Dashboard Administrators" by default is
So you have installed the SAS System, and you can check what is licensed with the proc setinit command, but what if something hiccuped in the install. Or your supporting (I mean validating) someone else's install and you need to quickly see what is available? Included below is some 'found'