What is the difference between the Flash technology and HTML5? – tu telugu

As you might already know, we are moving from flash technology to HTML5. This has some consequences. One consequence, for example, is that we are no longer supporting Internet Explorer 11 to view Visual Analytics reports. The reason for that is that Internet Explorer 11 has not been designed to run HTML5 applications. So make sure you have one of the supported browsers available like Google Chrome, Microsoft Edge, Firefox, or Safari if you’re running on a Mac. If you have a significant or large environment to convert from Visual Analytics 7 to Visual Analytics 8, you might consider running two versions of Visual Analytics in parallel for a limited time. This gives you, of course, more time to move the content over, and allows you to do it in smaller chunks. For example, you are converting some of the reports to the new version, and then you have time to check if everything is working as expected, where the majority of your reports are still running on your Visual Analytics SAS 9 environment. There is also something to consider about viewing reports. If your information consumers are already using a Windows 10 laptop or desktop, then you should consider using the Visual Analytics App for report viewing as well. I strongly recommend that you have a look at it because it allows the information consumers to view the report or to get their results more quickly because of the fact that this Visual Analytics App does not have the need to download the HTML5 components before it renders the report.

This results in the significantly reduced first time to view the report– the time needed to view the report for the first time. One more thing that is not on this slide here that I should mention– if you move reports from Visual Analytic 7.x to Visual Analytics 8.5, also consider the capability gap of the two versions. It might be more efficient to create some reports from scratch in the new system because we have provided a large number of new capabilities in recent releases in Visual Analytics 8. So be aware of the capability gap between the two versions. This might have consequences for your reports as well. First of all, you should look at your inventory, what you have currently in stock. What content types do you have to convert? Are there reports, explorations? Are you using custom themes? Do you use data preparation jobs or custom graphs in your report? What’s also important is knowing the size of your inventory. So are we talking about 15 reports or are we talking about several hundred reports? You can also compare different environments– for example, a dev environment versus a prod environment. R&D has developed a tool in recent years to support you in assessing your content. Let’s have a quick look at the screenshot. The name of the tool is the SAS Content Assessment Tool. What it actually does– it runs a job in your existing SAS 9 environment and gathers all the necessary metadata information to provide as a result a very detailed report of your inventory. We are currently looking at the cube and info map details inventory. It shows you that your current system– or the system that we are currently looking at has more than 1,000 information maps, some 115 OLAP cubes, and a large number of relational expressions and OLAP measures.

There are much more details in this report. Of course, this is only a screenshot of one part. You would also see, of course, Visual Analytics reports and what’s being used within those reports as well. I strongly recommend that you get in contact with your SAS representative if you are interested in running this content assessment tool in your environment to get a better view– of how you can move to SAS Viya. There are some things to consider as well. Some objects are not being promoted. First and foremost, I have to mention the data. So data has to be loaded to the target system before you do the promotion job. This is, of course, not very difficult, but you have to be aware of– other things have to be done in advance as well. For example, if your data are using custom formats, you’ll have to load them to the Viya system as well. You might have been using custom themes to customize the layout of your reports in Visual Analytics 7. These custom themes have been created in the flash world. Flash is no longer available in Visual Analytics on SAS Viya, so you have to recreate your custom themes with the new HTML5 Theme Builder on SAS Viya. You can do that also before you move the reports to the target system. Two more objects that are not part of the promotion process are Visual Data Builder jobs and Visual Statistic projects. Visual Statistics projects especially, they are coming from a very early release of Visual Analytics.

You can first promote them to explorations of the Visual Analytics 7 release, and then they are eligible for promotion to Visual Analytics on SAS Viya as well. How does the execution of the promotion actually look like? So if you’re promoting from a SAS 9 system, you first have to create your export package– namely, the SPK file either in SAS Management Console or via the batch export utility. There are some changes to authentication in SAS Viya. Therefore, there is something that you have to consider before you export the packages. If you want your authorization to be part of the promotion as well, you have to make sure that, on the new system, all the users and all the groups that you are using to define authorization settings for specific objects, must already be present on the target system. This is something that you can check by creating mapping files for– or it might be created export packages for users, and then check on the target system if all those users and groups are already present. Once you have created your export package, your SPK file, you can open the package file in the import window of SAS Environment Manager. your target files do not have exactly the same names, for example, or your CAS libraries have different names on the target system than the original SAS libraries or LASR libraries had on the source system, then you might have to adjust the mappings if needed. You can also import the package using a so-called command-line interface on SAS Viya. When you do it in Environment Manager during the import, you can also decide to save a mapping file that– for later usage. You can then use this mapping file when you do a batch import for more reports or other packages. If you are promoting within SAS Viya, it looks pretty similar, except for the fact that we no longer use SPK files as the package format. We are now creating. JSON files. These can be created in SAS Environment Manager or via batch export. I should mention that, if you are– let’s say, if you’re updating your SAS Viya environment in place, of course, there is no promotion necessary. But maybe you do a new installation on another machine or you have done a backup and you want to do a clean install of a new version. Then you have to create your content or you have to export your content. JSON file. Again, that content on the new system can be imported using the same mechanisms– either SAS Environment Manager or the command-line interface. In this case, mapping files might not be needed because you might have exactly the same structure on the target system that you had already on your source system in SAS Viya, but you can nevertheless use them to modify target data sources, for example, if necessary. Let’s have a look at the promotion of other objects. Lots of our customers are still using SAS Enterprise BI Server.

One important object that is being used in– for example, in Web Report Studio, reports within such enterprise BI Server are OLAP cubes. OLAP cubes are a multi-dimensional data structure that allows you to access data on different hierarchy levels without recalculating everything on the fly. OLAP cubes are no longer available within SAS Viya. Nevertheless, we can visualize in cross-tabulations similar reports that we had in Work Report Studio now in Visual Analytics, because Visual Analytics also knows the concept of hierarchies, and the computing power of the in-memory technology allows us to calculate those different hierarchies and the numbers related to them on the fly. If you are still using those OLAP cubes in SAS 9, you might be interested in converting them, because it’s now possible. OLAP cubes will be converted to Visual Analytics data views. Those cubes can be either based on detail tables or star schemas. The initial support is restricted to the 11 most popular MDX functions, and more are being discussed. R&D has looked at a couple of big customer environments to decide which MDX functions are favorites or are most being used at our customer sites.

Again, the SAS Content Assessment can support you in checking the eligibility of the cubes for promotion, because you’ll get a detailed report on which MDX functions are being used. This is a screenshot of the import– the first import step when you’re importing a package that contains an OLAP cube. You currently see that there is– this is the cube, and we have a couple of tables. In this case, we are importing an OLAP cube that’s based on the star schema, which has an ORDER_FACT table and a couple of dimension tables. Another object that has been used in SAS 9 is SAS Information Maps. SAS Information Maps in SAS 9 have been representing the business metadata layer for report authors. R&D has also looked at converting SAS Information Maps. The development work is currently restricted to relational information maps, meaning information maps whose target– or whose data structure behind it is relational tables. Information Maps will be converted to SAS Jobs in SAS Viya. After you have imported the information, map the SAS Job needs to run. It creates a CAS table and a Visual Analytics Data View. So the Visual Analytics Data View especially contains, for example, the calculations that are being made within the Information Map. 

Leave a Comment