Last year, I wrote a blog series on how to develop web applications based on ReactJS to extract data from SAS Viya. Knowing that many customers are moving to SAS Viya and are looking for ways to transition their existing SAS 9 assets to SAS Viya, I want to take the next few articles to explain how-to build similar functionalities in the Viya world.
From the SAS Viya documentation, we can read:
SAS Drive is a hub for SAS Viya applications that enables you to easily view, organize, and share your content from one place.
The SAS Drive has some similarities and differences with the SAS Portal. SAS Drive is designed to provide access to your SAS and non-SAS assets in a central place. By SAS assets, I mean SAS data, reports and models, and non-SAS assets include images, videos and documents, that are relevant to the SAS users and projects.
It is also the central place to access the different SAS applications. SAS Drive's primary purpose is to organize and share the SAS assets. It covers some of the functionalities of the SAS Portal that are related to organizing the SAS assets in a central place.
As you most probably noticed based on the descriptions above, the SAS Drive covers the "organizational" part of the functionalities offered by the SAS Portal but not the "visual" part.
By “visual”, I mean that the Portal can be comprised of different portlets which are responsible for surfacing the different types of assets. The available portlets in SAS 9 are for:
It is also possible in SAS 9 to build custom portlets using Java. Using can easily arrange these portlets in Portal pages like depicted below:
Select any image to see a larger version.
Mobile users: To view the images, select the "Full" version at the bottom of the page.
Using SAS Visual Analytics, you can build the same kind of mixed asset elements as shown in the picture below:
If you want to display KPIs that are based on different data sources, you may quickly end-up with an overly large report which will not meet the report design recommendations nor the performance that the end-user expects.
If the end-users want to customize their experience with bookmarks that are pointing to their favorite reports or jobs, this can also be done using SAS Visual Analytics but it implies the usage of data-driven content objects or some other techniques to display user specific content.
As mentioned earlier, a portal gives the end-users the opportunity to customize their landing page and adapt the page content to their needs. A portal also gives the opportunity to administrators to display specific messages like the availability of the environment.
As small conclusion, there are many cases where you can use the SAS Drive functionalities to organize your SAS assets and SAS Visual Analytics to display KPIs and embed results from SAS Viya Jobs. You can also use SAS Studio to execute SAS Viya Jobs. A portal becomes handy when you want to do all these things from a single place.
If you need to replicate SAS 9 Portal behavior, SAS Viya offers multiple SDKs to help you in this process. The SAS Visual Analytics SDK can be used to display reports, report pages or report objects in a custom web page. The SAS Content SDK eases the navigation in the SAS Viya content. Chatbots can also be integrated using SAS Conversation Designer SDK. In case the provided SDKs are not sufficient to serve the end-user needs, it is always possible to interact with the Cloud Analytic Service and Viya using REST APIs.
The remainder of this series will explain how to use the different SDKs to build the Portal like behavior to display a report with KPIs as well as linking out to other SAS assets.
In this process, we will use ReactJS to glue the different visual components together. To implement more advanced features, we will also use the MERN stack. MERN stands for:
Find more articles from SAS Global Enablement and Learning here.
Data Literacy is for all, even absolute beginners. Jump on board with this free e-learning and boost your career prospects.