10-10-2014 09:32 AM
gibt es eine Möglichkeit den Installationspfad bzw. die Variable SASHOME nach der Installation zu verändern, damit SAS Base Elemente wie "Enhanced Editor" beispielsweise auch unter "C:\Users\userid\AppData\Roaming" gesucht bzw gefunden werden?
Hintergrund ist eine Installation auf einem Netzlaufwerk von welchem aus lizensierte User SAS starten.
Die persönlichen Daten sollen statt im eigentlichen Installationspfad unter c:\Programme\SAS\... eben lieber unter C:\Users\userid\AppData\Roaming" abgelegt werden.
Ich hoffe Ihr habt eine Idee und Lösung
10-10-2014 10:27 AM
It is possible to use many SASHOME definitions as you like to support those in several versions. It is part of the installation choices.
Some choices are stored in the Windows registry, you have to clean up those when you are getting into some problems.
In previous versions (9.1) the shared components location was a problematic one of this kind.
The SASHOME is not you personal HOME by that is a very misleading and confusing name. It is the name that is used for the "program files" sub directory name.
Personal settings should go to the Roaming structure. (My documents and settings), Perfect? No for from that you have to validate every SAS client.
The SASHOME is having a deployment log and deployment validation. As part of "program files" in a closed environment rather useless.
Within SASHOME there is a default config (and autoexec) when using SAS-base. The SAS work should not go to a roaming location that one should kept personal local hard disk (like a swap/paging file heavy load)
With SAS 9.4 there are options to use a MSI installation and not the SAS special of the deployment wizard (Eguide AMO? Base). For the Windows dedicated tools.
They are updating a lot in the Windows registry and cannot be relocated after the installation. It is possible to use a networkshare for that. That trick comes by installing it on a local drive location (use subst for the driveletter) and copy those files to a network share. The advantage is there will be a limited physical versions. Repackaging only needed when the registry or local Windows gets involved.
There are many SAS java clients (SMC, DI, information map, Miner, etc) . They have each an own dedicated ini-file and a shared one on the sashome.
The JVM is a vritual machine (JPRE) this one should be on the local machine. All other files you can place as you like on any location. The sashome is coded in ini files as is the JPRE. Thos textfile may get manipulated.
If you find a ini file being placed wrongly you can solve that using the link-command (windows 7 introduced).
Eguide I having options you should review before repackaging. Those options can be found as the desktop-administration guide or a note as limiting the number of parallel sessions in note (BI/DI server)