Kim, This is an area full of emotions. The research performance issues it is important to understand the whole chain of components and those effects. What you have is a BI/DI intelligence platform is built around: - metadataserver (Linux) . It will run actually a SAS/Base Foundation process. It is setup to work memory based. Inside you will find a lot of java and xml usage. Taht are not the fastest well performing parts. - a webserver with a JAVA-container for webclients (WRS Portal etc) - Computeservers defined as logical app-servers started by the objectspawner - (and more) You can place all these serversides all on one server or for load/performance spread them over multiple machines. - The desktop clients like EG, Amo (.Net) based and java-clients SMC DI EMiner etc. All is installed mostly using the SDW tool and components are place conforming this way according plans. SMC is run by a JVM environment. Assuming using JAVA would make you independent of the versions of java is wrong. Using a wrong java version by type 32/64 bit or version or source, Oracle or other can give a lot of problems. SMC is also not a simple tool as is. It will get a lot of plug-ins added coming in from the other clients DI Eminer etc. What happens is that java classes are added to it in dedicated submaps. Eminer, DI, Information Map Studi, and others are not supported on Unix environments. Metacoda | productivity through metadata visibility (paul Homes - platform admin) is delivering more of this stuff on it, that part is more options on metadata management. Knowing this, it is very common to use all the desktop java clients including SMC from the Windows desktop. A SAS DMS with X-11 is still working (9.3) but has a lot of challenges. It is fast enough when the graphical traffic in not encrypted. Getting to Unix engineers and security guys they will block this. X11 is positioned as not being secure and the traffic should tunneled encrypted. With SAS 9.4 all is required tob 64-bit on Windows and newer Windows versions and X11 are getting more into trouble. See the requirements SAS 9.4 Install Center Documentation. Slowly slowly you are getting forced to leave the old approach. Eguide, AMO, SAS VA, Web based etc are the new ways of using SAS. I do not know what you mean with "the application developer" it looks to be a guy that is installing SAS. That is normal a "SAS platform Admin" like: SAS admins: providing maximum benefit to users - SAS Users Groups An application developer that is the guy I am seeing the one is delivering the code in .sas files running your business questions. Problems in a Windows desktop (the clients) can be that they have been set up with too small sizing of resources. Often this is done by desktop virtualization approaches. Eguide is integrating in Office as is AMO you would like to have them together. JVM is a virtual machine needing his own resources as guest in the Windows OS. When all is influenced by virusscanners encrytion firewalls it is rather easy to get into a out resources too slow performance situation. Moving the windows clients to a Windows-server with a Terminal Server is an easy get away of the desktop and network administrators. All normal policies applied to the desktops should propagated to this terminal usage solution. When the internal policies are not allowing or supporting this approach you have a next challenge to solve.
... View more
