About JuanS_OCS

JuanS_OCS · ‎04-07-2016

Thank you!

JuanS_OCS · ‎04-07-2016

Could you please share an screenshot, a link or give additional details? I am not sure if I get what you need, sorry. Thank you in advance, Juan

JuanS_OCS · ‎04-07-2016

I know that option but never tried, yet! Do you know if Exports require to have EVM up and running or only the Agents? Have you tried Exports?

JuanS_OCS · ‎04-07-2016

Shinny indeed! I believe I did not received mine, yet, probably due to a similar reason as ptimusk, but maybe it is just a matter of time 😉

JuanS_OCS · ‎04-07-2016

Hi, there is not restrictions on how much additional RAM memory to allocate, just suggestions to improve the performance of SAS VA. For questions related to sizing, I would advise you to contact your SAS account manager so they can send your request to the SAS Excelence center to determine the proper sizing for your requirements. Some questions they will probably make to you, I suggest you to have this information ready for them in advance: - Number of heavy and light users (heavy user = report designer/analyst or heavy reports consumer; light user= normal report consumer) - Total amount of SAS data (uncompressed) you plan to load into VA. - Size of the biggest table you plan to load. - Speed of your CPUs in casethat you have got already that hardware. - and other questions Best regards, Juan

JuanS_OCS · ‎04-06-2016

Thanks a lot @ronan and great answers! I am very glad to read that we share similar impressions and ideas about those deployments which some leave which similar questions. 1. HTTPS/SSL: I faced the latest 2 notes and are part of my most used notes at this moment. Since M2 there are additions to post-configuration steps that are not part on the Instructions.html, but on the SAS 9.4 Platform Intelligence guide for installations. The first note never had to face it, thanks! 2. Deconfigure SAS EVM: I could guess it, and it is what I was doing to this very moment. I am facing now one installation of SAS EVM which was configured when no SSL or SSO, then SSL, SSO and migration happened. I think I could fix the issues for SSL, but it is not working yet and I have the feeling that there is something really wrong over there. That is why that tricky question, before bothering SAS Technical Support with a hard question. 3. SSO: D*mn it! 🙂 4. Different SAS level EVM agents on a single EVM instance: Indeed, if I think about it, I can see several reasons to not to do it, due to the increasing close relationships: APM/ACM, not the BackupManager, the EVM database, its depencencies with the VA Audit reports and PostgreSQL... Even if, let's say, I want just the monitoring functionality and no one of the other nice additions, I can hardly see tweaking an option due to the big impact, specially on maintenances or migrations. I might do it on a personal installation to play and test my understanding of the SAS architecture, but probably never on a customer, unless there is a better option that a batch of tweaks. All in all, this is a bit of a grey area to me, but yours was the best answer so far. I will leave the conversation open without solution for a while. If no better answer, I will accept yours as solution because it was great.

JuanS_OCS · ‎04-06-2016

Hi @Saud, so, do you want to audit only the web applications? In case that this is what you need, you may want to give a look into those: http://support.sas.com/documentation/cdl/en/bimtag/68217/HTML/default/viewer.htm#n06skrc2rtwecsn14vi4qtfl54kx.htm http://support.sas.com/documentation/cdl/en/biwaag/63149/HTML/default/viewer.htm#a003310614.htm

JuanS_OCS · ‎04-05-2016

Hi, you can get the information on different ways: - By parsing the log files (Metadata server log, Workspace server log, SAS Web Application logs) - On the SAS Management Console, if you go to the lowest level of your SAS metadata server, you can Right-click and "Connect". Then on the right side you can see your logins of the day. - APM/ACM reports can provide, I believe, such reports.

JuanS_OCS · ‎04-04-2016

I think you would be interested on the certification for SAS Platform Administrator. SAS base is for programmers and general purposes, and the one I am mentioning is for administrators.

JuanS_OCS · ‎04-04-2016

Hi, You might want at least to get a foundation level certification for RedHat (or similar) and a SAS Platform Administration certification for SAS 9 (or at least get the SAS Platform Administration Fast Track from SAS). https://support.sas.com/training/

JuanS_OCS · ‎04-04-2016

Thanks to you for your question, it was a great one (love it). I think it is an important and recursive question. And on Linux/Unix is to easy to arrange...!

JuanS_OCS · ‎04-04-2016

Looking forward to discovering what you can find out, @GyaniBaba! 🙂

JuanS_OCS · ‎04-04-2016

Indeed, dependencies and impact on maintenances is an issue. I am looking forward to hearing the incoming improvements on this matter by developers at the SGF!

JuanS_OCS · ‎04-04-2016

Thanks @GyaniBaba The question about http/https is just curiosity of mine. Specially since, if you select https during the installation for SAS EVM, http is still open. You need to follow some post-configurations in order to close it and make work properly the callback URLs. Monitoring from a single portal is one of the question on what I am most interested.

JuanS_OCS · ‎04-04-2016

Hi, a very simplified configuration (and efficient) for DR would be to have: - 2 hosts, with just the OS and the pre-requisites - 1 CFS (clustered file system), where you will have the SAS config, SAS binaries and all the user data. - have SAS configured based on alias (so you can just change the alias on the DNS to point to the new host, when one "dies"). - mount the CF directories on the active host. - register the alias/host on the DNS. On this way the server and the file system will have DR. As you have now your Production system already configured, a way to go to minimize the impact might be: - Make a good backup of your Production server - Start creating the pasive/DR server, with different hostname and align pre-requisites with primary/active production. - Create the CFS (if not yet ready), and start by making the sync (beware of permissions an lost soft and hard links!) - Stop the Production/primary server's SAS services and SAS processes. - Make an extra sync when you can stop the server --> - change hostname of the primary/current Production server. - create the DNS alias and make it the same as the current hostname. - point that alias on the DNS server to the primary server (current production, which now has a different hostname) - mount the CFS on the primary --> the folder structure and permissions should be the same as on your current status on the Production server. - Start the SAS services on the primary server, which should now work fine as before. When the primary goes down, stop all SAS services and SAS processes on the primary/production server, change the DNS alias on the DNS server to point to the secondary, change network cards and un mount the CFS from the primary and mount it on the secondary. Then start the services on the secondary.

Online Status	Offline
Date Last Visited	‎04-13-2026 07:47 AM