About AnandVyas

AnandVyas · ‎01-19-2021

Ok, I get what you are referring to. How about using nohup before the start/stop command whichever way you are using it? nohup ./ObjectSpawner.sh stop nohup ./ObjectSpawner.sh start

AnandVyas · ‎01-19-2021

Hi @Chery I think SAS Viya Administration guide should be a good place which covers all the concepts related to Viya administration. If you are ok with paid trainings, then SAS has paid trainings available related to this certification. You can find more information related to the training and exam content on this link: https://www.sas.com/en_us/certification/credentials/administration/viya-admin.html All the best!

AnandVyas · ‎01-18-2021

Hi @jhck You can download from GitHub project: https://github.com/vyasanand/LASROps

AnandVyas · ‎01-17-2021

Hi @junny Error in the log only says about cachelocator directory. Can you check if it's exists and you can successfully start the service directly on server? If yes, try running the wizard again. If not, then as suggested by @SASKiwi it's best to reach out to SAS TS.

AnandVyas · ‎01-16-2021

Hi @Sajid01 Did you try "Developer Tools" in Google Chrome? It helps you export a HAR file for all the network requests. https://developers.google.com/web/tools/chrome-devtools/network/reference https://support.zendesk.com/hc/en-us/articles/204410413-Generating-a-HAR-file-for-troubleshooting

AnandVyas · ‎01-15-2021

Hi @satya1861 In most scenarios, databases are behind firewalls and when connecting internally between intranet it should be secured and protected. However if that's not the case then concern is valid. SAS uses SAS/Secure to encrypt all its connections from client and internal and supports various encryption algorithms like AES, FIPS etc. I didn't find any info on data in motion encryption for SAP R/3. I would advise to raise a SAS Technical support track for quick response.

AnandVyas · ‎01-15-2021

Hi @mailkaushikp My two cents below: You will need to request SAS Software depot for 9.4 M6 for the site from SAS account manager or representative Software Order E-Mail (SOE) should also contain your new license file and instructions to download the depot Upgrade options: SAS Migration Utility (SMU) Run pre-assessment on your current environment and create content packages On the new VM, perform the pre-installation checks Run the SDW, Install/configure and use the packages created earlier during configuration Reference: Copying an Existing SAS 9.4 Deployment Notice to SAS Migration Utility Users Partial Promotion On the new VM, perform the pre-installation checks Install the new software version of VM and using SAS export/import utilities promote your content from older environment to new one Reference: Introduction to the Promotion Tools Cloning If your site has software that can clone your entire system i.e. everything on OS and application software, data then you can clone the existing system Perform upgrade in place for the cloned instance Reference: How the SAS Deployment Wizard Adds, Updates, and Upgrades Software NOTE: Just copying of files is not supported, it should be a proper clone. Usually NOT recommended if IT teams doesn't support it fully Check out the migration guide for more detailed steps and understand the process better Migration Guide Agree with @SASKiwi that you should upgrade to M7 instead of M6. It was released in Aug 2020 For your old environment if you wish to continue using it alongside the new one, you should speak to your account executive on the terms and conditions and financial impacts If you are going to decommission the old environment, I don't think there should be any impact on license Hope this helps!

AnandVyas · ‎01-15-2021

Hi @herborfer What do you mean by asking for a key? parameter? sorry I did not get it. Could you share how are you trying to call the spawner command via RunDeck?

AnandVyas · ‎01-14-2021

Hi @EinarRoed You can start by verifying if SAS session encoding value is same when executed from EG and via batch. Below proc can fetch this information in SAS log. proc options option=encoding; run;

AnandVyas · ‎01-14-2021

Hi @jwward65 I am not sure but I think there isn't any OOTB option to restrict this option. However in Viya you can use rules to explicitly deny access to certain URI's. You can find more about this in the reference links provided below. In the URI reference link you can find different URIs related to Job Management. Job Management2 Schedule jobs. /jobExecution/jobRequests/* /jobExecution/jobRequests/*/ Both URIs are required (two separate rules). Edit scheduled jobs. /scheduler/jobs/** Monitor jobs. /jobExecution/jobs/** Reference: Access to Functionality: Overview Example Instructions on how to restrict functionality access using URIs Access to Functionality: URI Reference

AnandVyas · ‎01-14-2021

Hi @Sajid01 I have done similar testing for one of the solution using postman as my client. For all my requests there was a response, not successful always but some error code or warning. These error messages were also logged into catalina.out or application specific log file that is deployed under app server (SASServerX_Y). (<sasconfig>/Lev1/Web/Logs/SASServerX_Y) You can also try to enable debug logs and see if it helps. If the response is being lost due to network, you will require network tracing client/tools to see if there are packet drops. You can also check packet drops on the machine network interface, however network packet tracing tools can give more information.

AnandVyas · ‎01-13-2021

Hi @gra_in_aus Is the machine added to cluster as grid client?

AnandVyas · ‎01-12-2021

Hi @qoit SAS/Access interface to Hadoop is for native access to Hive and HiveServer2 tables. SAS/Access interface to Impala is for native access to Impala tables. There is a difference in how these two Hadoop services works with the latter bypassing MapReduce. But for both of these to work from SAS, HDFS is also required. Ref: What Is SAS/ACCESS Interface to Hadoop? What Is SAS/ACCESS Interface to Impala?

AnandVyas · ‎01-12-2021

Thanks for sharing the snaps. It helps to better understand the problem. Did you do any updates or changes to SASHome for whatever reason, may be like applying hot-fix or added any products later after the installation? The could be the reason your SASHome is at a different version from that of your depot. Since it only gives an error for an particular software what you can try to do is compare the version of this particular component "SAS Security Certificate Framework" in the depot versus the one installed currently. You can find this info in the ordersummary.html file in your depot eg path: /<your-file-system-path-to-depot>/install_doc/<your-site-order-number>/ If the version is different and SASHome has latest version when compared to the depot, you will have to request for a new depot with the updated files. I am not sure if this particular component can be removed independently and added again. This is something you should check with SAS TS for the best way to solve this. If this is only a client installation then probably doing a reinstall would not be much of a task. Hope this helps!

AnandVyas · ‎01-11-2021

Hi @tpr If you are trying to apply hot-fixes to your EG client which you have installed as standalone then why do you need to use the depot? You can place your hot-fixes in the SASHOME directory, launch the SDM wizard and apply the hot-fix. If you are trying to apply hot-fixes to you server binaries, you can do the same. Hot-fixes are applied to SASHOME binaries and some to configuration files as well depending on the fix. You don't apply it to the depot.