4 thoughts on “All Systems Go with SAS 9.3”

  1. Hi Paul.

    I heard that you can’t install over the top of 9.2 (like M3 update), ie. seperate install of 9.3 is required, Is this the case? If so how does it get around using the same ports in the configs etc on the same machine…


  2. Hi Barry,

    Thanks for your comment.

    That’s right. I imagine that most would want to run SAS 9.2 and SAS 9.3 side by side for the duration of migration and testing anyway. As far as machines/ports go, there are a few options which include:

    1) Same machines + same ports: whilst possible it’s not a very realistic option as it means you have to shut the entire SAS 9.2 platform down to start the SAS 9.3 platform and vice-versa (unless you try to go down the route of having multi-homed servers and bind them to different IP addresses).

    2) Same machines + different ports: enables you have have SAS 9.2 and SAS 9.3 running side by side but they have to be on different port banks. If you have SAS 9.2 deployments as Lev1, Lev2 and Lev3 you could have SAS 9.3 deployments as Lev4, Lev5 and Lev6 for example. Of course, the machines would have to have enough resources to handle the additional deployments and you would have to use the same architecture.

    3) Different machines + same ports: the different machines could be physical or virtual. This can avoid consuming the resources from existing SAS 9.2 deployments and also allows for a change in architecture if desired such as 32-bit to 64-bit or a change/upgrade in server operating system.

    All of these have their pros and cons and SAS Institute (or partner) could advise on these and the architecture choices as appropriate for your environment. I’m sure SAS Institute would also let you know if there are any licensing implications for any of these choices in your environment if using different physical/virtual machines for example.

    The following resources are handy if you want to find out more:
    * SAS 9.3 Intelligence Platform: Installation and Configuration Guide: http://support.sas.com/documentation/cdl/en/biig/62611/PDF/default/biig.pdf
    * SAS 9.3 Intelligence Platform: Migration Guide: http://support.sas.com/documentation/cdl/en/bimig/62613/PDF/default/bimig.pdf


  3. Hi Paul,

    Need your help – Please if you can suggest me something here:

    It’s for a migration to a new installation 9.2 to 9.4:

    Looking on this site – http://support.sas.com/documentation/cdl/en/bisag/66813/HTML/default/viewer.htm#n1f9181cn1d545n1odu6hkrrcee4.htm#n1s4gwfo1t995dn1a96eghgforn0
    About halfway down, under Promoting Security Objects and Server Objects it has this paragraph;

    You can promote security objects (users, user groups, roles, and access control templates) and all of the server types that can be registered in metadata. The promotion of these objects can be useful when you are creating or refreshing a SAS environment that mirrors an existing environment. For example, you can use this feature to help create a test environment that mirrors your production environment and to refresh the test environment as needed. Or you might choose to create server or security objects in a test environment and then promote the objects to your production environment after the objects have been tested.

    Does this work?

    There is much more than 12 users. The ACT’s are very hard to read because the lag time using X windows can take 5 minutes or more to refresh a page so I am looking for a simpler way to move them.
    As far I know, The ACT’s will not migrate and I cannot figure out how to get a list of them.

  4. The ability export and import security objects was introduced in SAS 9.3, so unfortunately you can’t use this method to export ACTs from SAS 9.2 to import into a SAS 9.4 installation. You will need to manually recreate the ACTs in SAS 9.4 to match what you have in SAS 9.2 – hopefully you don’t have too many :) Our Metacoda Security Plug-ins ACT Reviewer provides a great way to review ACTs and also export HTML reports about them – you may find this useful when recreating your SAS 9.2 ACTs in SAS 9.4

    Are you using X tunnelled over SSH? I too have found significantly delays in using SAS Management Console via X over SSH. You may find it quicker to install SAS Management Console on a Windows machine (or virtual machine) and connect to your remote Unix server. Alternatively remote desktop into a Windows machine which has SAS Management Console installed and is closer to the Unix server.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.