Did you already reviewed?
- Migration: Planning
- Migration: Moving to SAS 9.4 Migrating to 9.4 is better is 9.3 is becoming already old, but you may be need 9.3
All depends what is running at the moment and has to be migrated.
+ When there is SAS metadata at 9.1.3 you can decide to build that all from fresh or doing a migrate of the content.
Migration of SAS metadata content is a major action to do (when needed). To be analyze and planned separately.
+ Hardware capacity should be planned and chosen accordingly
performance/tuning
+ SAS is a C/S approach. You cannot segregate the Clients from the Server services.
Which clients are needed there are several with different behavior Eguide/AMO (.Net) and the JVM ones (SMC DI information map etc)
+ Migrating Windows to Unix is changing the OS, for real SAS code not an issue. But when user have used a lot of Windows specifics and hardcoded physical names that is a big issue.
You have to get clear on that and eliminate those issues
+ Not all functionality can be migrated from Windows to Unix. It can be you are still needing Base Foundation on Windows
I know this for SCL (old part of AF) but also seen that for the new interactive graphics designer (menu item in Eguide). Dedicated interfaces to PC based types are possible.
Integrating to open web-access can get restricted on a server (SASHFADD)
+ is there a need to implement PC-files server (dedicated Windows types to be run on a win-server)
What are the requirements for:
+ a release management process (business environment) with a DTAP approach
+ an version management process when having many developers (version management is on avoiding development conflicts)
+ security segregations with a RBAC connection
+ SIEM (security information &event monitoring) with an Incident response process
Sorry for giving some answers but asking more questions.
---->-- ja karman --<-----