Stored processes were a very popular feature in SAS 9.4. They were used in reporting, analytics and web application development. In Viya, the equivalent feature is jobs. Using jobs the same way as stored processes was enhanced in Viya 3.5. In addition, there is preliminary support for promoting 9.4 stored processes to Viya. In this post, I will examine what is sure to be a popular feature for SAS 9.4 users starting out with Viya.
In this blog, I will show you how a Viya administrator can track and control resource usage of personal caslibs.
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.
Find out about this new set of tools designed to be used in conjunction with the sas-admin command line interfaces.
In SAS Viya 3.4, promotion support has been added for many additional SAS 9.4 resources, making it easier to make the leap to Viya. In this blog, SAS' Gerry Nelson reviews this new functionality.
Often, in addition to content, an administrator will want to save configuration so that it can be reloaded or updated and applied to a different system. You have the ability to save and reload SAS Viya configuration using command-line interfaces. Learn more in this post.
SAS Viya 3.3 introduced a set of command-line interfaces that SAS Viya administrators will find extremely useful. The command-line interfaces(CLI) will allow administrators to perform numerous administrative tasks in batch as an alternative to using the SAS Environment Manager interface. In addition, calls to the CLI’s can be chained together
Authorization determines what a user can see and do in an application. An authorization system is used to define access control policies, and those policies are later enforced so that access requests are granted or denied. To secure resources in SAS Viya there are three authorization systems of which you need to be aware. The General
ln SAS Viya, deployments identities are managed by the environments configured identity provider. In Visual SAS Viya deployments the identity provider must be an LDAP (Lightweight Directory Access Protocol) server. Initial setup of a SAS Viya Deployment requires configuration to support reading the identity information (users and groups) from LDAP. SAS Viya 3.3
In a SAS Viya 3.2 environment two types of content can be created: SAS Visual Analytics Reports and Data Plans. For administrators, who may want to manage that content within a folder structure, there are some things to keep in mind. In the current release, both types of content can be
With the fifth maintenance release of SAS 9.4 (SAS 9.4M5) now available, it seems like a good time to get a refresher on some of the ways you can upgrade your existing SAS deployments to the latest release. Among several benefits, SAS 9.4M5 provides closer integration with the CAS in-memory runtime engine
SAS Viya deployments use credentials for accessing databases and other third-party products that require authentication. In this blog post, I will look at how this sharing of credentials is implemented in SAS Environment Manager. In SAS Viya, domains are used to store the: Credentials required to access external data sources. Identities
In this blog post I’d like to explore how to create a custom group in SAS Viya to restrict access to functionality. To illustrate my points, we will create a report developers custom group and ensure that only users of that group can create reports and analysis in SAS Visual Analytics.
In a number of my previous blogs I have discussed auditing within a SAS environment and how to identity who has accessed data or changed reports. For many companies keeping an audit trail is very important. If you’re an administrator in your environment and auditing is important at your organization,
Update-in-place supports the ability to update a SAS Deployment within a major SAS release. Updates often provide new versions of SAS products. However, when using the SAS Deployment Wizard to perform an update-in-place you cannot selectively update a machine or product. As a general rule if you want to update
One of the jobs of SAS Administrators is keeping the SAS license current. In the past, all you needed to do was update the license for Foundation SAS and you were done. This task can be performed by selecting the Renew SAS Software option in the SAS Deployment Manager. More recently,
In a couple of my previous blogs I discussed how to audit who made changes to data in a SAS environment. In the last couple of weeks I have been asked how to do the same thing for SAS Visual Analytics reports and explorations. The Visual Analytics administrator overview report
In my last blog (What is going on with my Visual Analytics audit data collection) I reviewed how middle-tier auditing works and where to look for logs to debug issues. In this follow up blog I will do the same for the Visual Analytics audit data archiving process. The archive process is
In my last blog I discussed purging audit records from the Web Infrastructure Platform SharedServices database. The blog generated a fair bit of discussion around the SAS Visual Analytics auditing data gathering and archive process. So let’s take a step back and in this blog review how data collection for auditing works and
SAS Visual Analytics contains an Administrator Overview report which provides for Visual Analytics usage information by application, user, and object. To provide data for the report you must enable collection of key actions audit data in the Visual Analytics Middle-Tier. Auditing doesn’t just apply to Visual Analytics, it can be
In my last blog, I demonstrated how to configure a SAS server to write a record to a log file showing who is opening, editing or renaming a SAS table. In this blog we will see how we can process that information. The documentation shows one way to do this via
SAS Administrators are frequently asked to log and report on which users are accessing SAS tables. This functionality is often requested by companies who, for regulatory compliance, need to track who is accessing data. In my next couple of blogs I will show how you can audit data access. In this first blog
SAS 9.4 M3 released in July 2015 with some interesting new features and functionality for platform SAS administrators. In this blog I will review at a very high level the major new features. For details you can see the SAS 9.4 System Administration guide. SAS 9.4 M3 includes a new release
In a SAS Environment there is a lot of metadata, metadata about configuration such as server definitions, users, groups and roles and metadata about content like data, reports and jobs etc. SAS Administrators often want to report on metadata. They want to know what reports have been developed and where they are stored, what
Recent updates to SAS 9.4 have introduced some nice improvements in support of automated migration using the SAS Migration Utility and SAS Deployment Wizard. SAS has been working hard to make the migration experience more user friendly and less error prone. Changes have focused on making errors easier to identify
Somebody once said that relationships are not easy. Well now they are—in SAS 9.4, at least! SAS objects have inherent relationships and dependencies, and a change to one element can often have an impact on one or many related objects. For example, for SAS Visual Analytics reports to work as
During a migration to a new release of SAS software, the SAS Migration Utility is used to analyze and package your source software. There are two ways that you can get the SAS Migration Utility. It’s available by selecting SAS Migration Utility from the Downloads page on support.sas.com. The SAS Migration