home-SAS    SAS-SAAS    First steps    Installation    Hardening    Operational    Using    My Notes
General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Scheduling    Experiences    top  bottom

Installing SAS


building SAS

Installing SAS

When ready with:
  1. the design
  2. planning
  3. having capable contractors
  4. having the operational vision

The start of the environment building can begin.

My Gathered Samples for worked out situations.
The steps to get thru:


Generic steps

Softwaredepot roll-out (SAS) The picture aside should be helpfull in understanding the technical steps of the installation.

If you have one ore more licenses (SID files), you can start with building up a software depot.
It is done by downloading with these license all needed files to your location. A registered key to the SAS support environment is needed.

SAS information: 029-2012 Preparing for a SAS® Intelligence Platform Environment Deployment/Migration.



together

Installation - Configuration

The basic clean installation will, as the work is proceeding, getting intermixed with the configuration.

The meta data configuration with all the setup of conventions to be defined, has become an essential step in the functionality.
The configuration stage assumes:

There are two phases that are somehow getting mixed up by dependencies. Some clients need to be installed configured/running before you can do an installation
1/ Installation
At the installation phase just the plain code is at is delivered is rolled out.

2/ Configuration
After installation, you can configure. This will set up all localized items needed to align to the specific business(client) situation



finding the presentation

Basic approaches

Presentation layers:
This how SAS will become avaialbe for users. There are several ways:

cost money

Virtua1ization

Virtualization:
This is more a question of cost optimization in hardware and licensing with performance requirements.



The new SAS analytics U (as of 2014). This update is for edcuation Universities (for free). It is a distribution based on a virtual machine package.



marionet

Actions to be done

A soon you have a implementation design plan that defines the logical machines 1 2 3 or 4 tiers clustering, you must get a plan-file from SAS.

When installing the software you have to be in agreement with SAS: that what is delivered and how it is installed is supported that way by SAS.

  1. You need a SAS consultant for the plan file or get agreement in the approach.

  2. Get a support agreement on the planned way it will be installed. (not the same ss SAS thinks to do)

  3. Install server(s) tiers.
    This is the placing of the "laodables". Only to be changed by SAS-supplied fixes & updates. Other log-files and SAS-work space are needed with a detailed OS security plan.

  4. Configuring server(s) side.
    This is where the processing will taken place. At this side the meta data server, log server are to run. These are based on a SAS-Foundation(Base) layer. Other log-files and SAS-work space are needed with a detailed OS security plan.



  1. Installation of the desktop: It can be made ready after having configured servers
    The same software depot is used. Options to the desktop can vary, it depends of the situation:
    1. getting it installed from the software depot. Using as a reference-server
    2. automating the process of using a software depot to desktops by adding repsonse files
    3. making snap-shots of the installation, repackaging it as MSI-packages
    4. disconnecting from the normal desktop,
      using a complete other desktop (remote) elsewhere (terminal server)
      the same installation questionnaire are moved to an server
    5. trying to get it running in a virtualized environment like app-v (softgrid)
    Every approach has advantages and disadvantages.


  2. The configuration of the desktop must be approached as a separate process.
    A guideline, document/instruction, of actions expected by the target users must be made.


  3. To be able to run the business clients with business data and logic, use a simulation of them to verify the functionality and design. See dtap04 edu/sec/rcr


  4. Make plans to test the wanted performance of the total system. Making it ready to get accepted by the users/customers.



archive

Related SAS Information

The software-depot will contain a lot of small files in many maps. Al lot of them xml-files describing a part of the installation. The installation program is java-based and is processing these xml-files.

This way of installing is a very dedicated SAS approach. It is not commonly used. It can be very surprising for installation staff using their own standards. Even normal standards like MSI or SMP are not used.

There are many guides available with all kind of information for this process. a selected list from the SAS-site eip install-center is made below.
The requirements and information with all OS networking firewall´s are minimal as they are supposed to be delivered from other sources.

Frequently asked questions about SAS® 9.3 software: kb 42384
Installation guides, overview


Defining User Accounts is a step that should start as soon as possible by needed conformation with security departments. &
Operational guides
Solutions specific guides
user based and administration based guides



believe

software depot into sashome

The software depot can be easily become as big as 20Gb. It can contain of all OS-versions the software meant for server-side and the clients.
It contains many really many xml-files describing the contents and the interactions to install

After rolling out a "sashome" map is made the sizing can be from 3Gb to 7Gb (server 10Gb) depending on the components to be installed.
The name sashome can be confusing as it is quite different to the home of Unix. On Unix "sashome" will be placed in "/opt/..."
The "sashome" is build up with:



drama2

The default installation, not ready to be used

The default installation is one that technically works. Not one that is well secured or will follow the normal support policies.
The default keys like &quatsassrv" and "sasdemo" are opening up the whole of an installation like using the root-key.
The operational process startup up of services clean up of processes and files are all missing in the default installation.

The steps to a well compliant installation are: For all: getting it attached to normal procedures already present



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Scheduling    Experiences    top  bottom

Server Side roll out SAS

bi di SAS img The picture aside should be helpfull in understanding the technical steps of the installation.
There are several parts (tiers) to deal with

The meta dataserver is one of the first parts to get running. Ss it based on normal SAS/Base that part is also needed. In the classic SAS approach, blue interlined below in the picture, this will also become available.

With clients needed to validate the server functions, the Object spawner with Workspace and Stored Process servers are to be build up.

Having those parts working the midtier (webcontainer) and web-clients can be get working.

Te last thing is all parts (business data included) getting connected and delivering to be used operationally.




believe

Installing server software

Ahead of roll-out
At this point we have some requirements. Some also have some contradictions. These are: In some way this has to be solved. This work has to be done as part of an implementation.
No easy job as no one likes this to do, or even wants it to be mentioned.
Hotfixes
The latest fixes should by applied as part of the installing.
Normally this is part of operational support process.
See the life cycle in the operational chapter for more details.
Root access
Root access (unrestricted access to machine OS) should be avoided.

Some steps requiring this keys/pswd can be surpassed.
The necessary actions can be done as request to people having root and with activity trace.



believe

managing third party components

Generic
Java, Xerces and a lot of more like web-servers, versioning, scheduling is installed with SAS.

third party support .
Pay attention on the different versions.
Java
Java is positioned as the environment to get OS version independent. The reality is that many different versions of Java (JVM) must be managed.
Every component is possible requiring a different JAVA JVM version. Some tools/software are requieing 32-bit and other 64-bit versions. Only one java version can be the default version.
An inventarization off all used Java versions is needed.

Checking the default version:
java -version

java -version:--value--



DI and other java clients have an ini file with jvm settings. This is part of a desktop configuration.
An exception is eminer webstart: emag.pdf SAS Enterprise Miner 6.2 Client Start-up Properties
You can provide such users with access to additional memory by increasing the size of the two memory properties shown below. You can increase the max.heap.size property to a value such as 1024m. However, in most cases, default user memory allocations should suffice. webstart.client.initial.heap.size=128m
webstart.client.max.heap.size=512m






believe

Web tier

This part is the most complicating as all the servers (services) should be functioning well.
At this point a webserver, java-container, webdav-server with a storage location are added.

As third party components can be choosen one of: JBOSS Weblogic and Websphere.
Installing configuring and operational administration of this part is a job to do aside SAS. JBoss is one of the three possible java-web application-servers.
  1. JBOSS
  2. Weblogic-Oracle
  3. Websphere-IBM
Jboss is the most affordable in licensing.
Comparing these options information: note:ittoolbox   note:redhat (supplier of jboss/open source).




handy

JBOSS as web application server

Jboss version
Asking a version of JBoss... Getting a terrible long list of all that components.
All these components are tested and working fine together. That is the expectation of "give me JBOSS".


jboss part version
JBoss Application Server 5.1.0.GA
JBoss Microcontainer 2.0.10.GA
Hibernate Core 3.3.2.GA_CP03
Hibernate Entity Manager 3.4.0.GA_CP03
Hibernate Validator 3.1.0
Hibernate Search 3.1.1.GA_CP03
JBoss Web
(based on Tomcat 6.0)
2.1.10.GA
JBoss Cache 3.2.5.GA
JBoss JAXR 2.0.1
JGroups 2.6.16.GA
JBoss EJB3 1.3.6
JBoss Transactions 4.6.1.GA_CP07
JBoss Web Services (WS) 3.1.2 SP8
JBoss WS-Native 3.1.2 SP7
JBoss WS-CXF 3.1.2.SP7
JBoss AOP 2.1.6.CP01
JBoss Remoting 2.5.3.SP1
JBoss Serialization 1.0.4.FINAL


jboss part version
JSF 1.2_13
JacORB 2.3.1.jboss.patch1
JPA 1.0.0
JBoss Security 2.0.4.SP4
JBoss Negotiation 2.0.3 SP3
JBoss Profiler-jvmti 1.0.0.CR5
Xalan 2.7.1.patch03
Seam 2.2.2.EAP5
RichFaces 3.3.1.SP2
JBoss Admin Console 1.3.4.SP1
JBoss Messaging 1.4.7.GA
mod_jk 1.2.30
mod_cluster 1.0.4.GA
JBoss RESTEasy 1.2.1
JBoss Native 2.0.6
PicketLink Federation (Tech. Preview) 1.0.3
Netty 3.2.1.Final


Advise: don´t break the list of versions. Let support be done by those people doing it on more (logical) machines.



The version 5.1.0 to 9.3 SAS. v93 jbossweb Version requirements, is ok.


Jboss ear-files
How the java ear-files of SAS to get into JBOSS.....
(to be done later)

Jboss static html
Question: How to solve the static html?
Searching: jbossweb ch9   jbossweb config points to the origin of Tomcat. How tomcat is configured is to be done. jbossweb cgibin Just one cgi-dir to be configured. This will do for SAS using the logical link trick.



handy

Websphere as web application server

Websphere version
(to be checked)
Websphere ear-files
How the java ear-files of SAS to get into Websphere.....
(to be done later)

Websphere static html
Question: How to solve the static html?
IHS is an Apache version imbedded with webspehere.



handy

Additional steps

Several components in the software are requiring addtional steps.

Internet Broker
This part is needing configuration files.
VFB Virtual Frame Buffer (Unix)
This part is isolating hardware from graphics calls. Graphics are presented by Web-services





Pc files

managing pc files

To be able to interact with windows machines (Access Pc-files) the best way is to implement the usage of PC-File Server. This is normally not in scope with a SAS installation. It will interact with the Microsoft Interfaces in this way fully transparent to all formats.

To manage PC Files a dedicated Windows Server must be installed.
It is licensed with the Access/pcfiles on a server. pc files server


bu databases
Managing DBMS
With a DBMS the conenction SAS/DBMS has to be installed and configured. The most basic and sample things are that the DBMS client must be found from a SAS process. The environment of that process must have all the information.



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Experiences    top  bottom

Desktop rollout SAS

Desktops SAS contradictions:
In some way this has to be solved. This work has to be done as part of an implementation.
No easy job as no ones like this to do or even wants it to be mentioned.

The issues found applies for all of them. The things to do are:

Choosing Desktop approach

At this point we get some contradictors.
SAS is promoting analytics for highly confidential data. In that aspect all components should be implemented in a secure way.

There are several approaches the implement the desktop. I´m working them out from simple to complex.



genius

Standalone like home-use all open

This is the most simple approach when you desktop is under your control. I mean when you are allowed to install software yourself and no troublesome support policies are in place.
Just use the software depot and the SID-file you got with your license. Install the components that are listed. It is just a SOHO (Smal Office / HOme installation).

The installation process of SAS is designed for this situation. Microsoft advices to use a dedicated Admin user on your PC. The normal user(s) not allowing to install software. In this way becoming less vulnerable to malware 4us-ses etc.
managing Data Flux
This is a new bundling with SAS 93. It behaves different. Requirement are new different -sashome- for every different setting. config dataflux

managing third party components
This normally is supposed to be common knowledge


Found issues to solve (93) I



genius

Reference server, closed-PC business

In a closed PC just a admin-key is able to install software. This can be a living person or an automated process.
There is an option to create a response-file to install SAS on desktops. As long as the installer key has access tot the software depot this approach can be automated. The location of the software depot can be indicated as "reference server"
With a small number of installations a living person can do the job. Can be implemented as "on location" or by "remote support".
With many installations involved or by using VDI needing to it more than once the process can be automated.

wiki: Software_repository
Found issues to solve (93) II



genius

repackage MSI , closed-PC business

This is the common approach of the last years. Having a standard for desktops the installation process of external suppliers can be replaced by analyzing snap-shots.
The snap shots are repackaged as a common MSI-installation with the normal MS-Windows approach.
Found issues to solve (93) III



genius

terminal server

Instead of installing the clients on normal used desktop, a server terminal connection is can be used.
The clients are running in the server environment. With all advantages and disadvantages. It is an older way of the more modern VDI.
Found issues to solve (93) V



genius

Virtualized Desktops, app-v

The app-v approach (formerly Softgrid) is having a lot of new things to do. It is not supported by SAS.
Found issues to solve (93) VI


As of 2013 SAS is working on app-v 461-2013 Tips and Techniques for Deploying SAS in an Application Virtualization Environment



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Experiences    top  bottom

Configuring SAS Server

bi di SAS img The whole of the installation is needing configuration.

All parts must be reviewed.


Standard config actions


Generic Server

Managing lower level part like OS network firewall is normally is supposed to be common knowledge
Some things to mention are: Optional Setup Tasks (biig)


retentionpol

backup meta data

The meta data database is an in memory database. On regular times it shoul be flushed to dasd.
Enabling normal backup procedures to get into an reliable offline backup
Clustering is a more advanced hot fail safe approach. Not the same as the classic backup.

http://support.sas.com/documentation/cdl/en/bisag/65422/HTML/default/viewer.htm#n1n8fnuni6kbjgn1805ilb6xn9vf.htm (biig)
And do not forget: a backup is only useful whn you are able to do a restore.




saswork & logging

saswork
SAS work is temporary storage should be available as plenty as needed and fast. No backup is needed.
It is toe be compared to swap or paging space of the OS-level. By default the setting is just for verifying functions, not the common big-data.
Consider multiple locations (round robin) or set by working classes (interactive web batch)
Consider by-passsing the OS-caching as SAS will cache something an big-data (+200Gb) will make rubbish of the OS-cache (10Gb).

sas-admin-common-compute-server-performance-options (Bi-notes Steve Overton 2013 jan) There are more type of servers and the behave different:
Compressing data was introduced some versions ago, I think it was 6. In those times some functionality was harmed when using it. With 9 it looks very reliable. Some underpinning found by notes in MXG documentation (part of SAS IT service solution), stating improved overall performance less disk space and no negative effects. I have set up compress=yes with good results not having any functionality harmed.

One thing to be mentioned
When having small datasets a note is coming that datasets are not compressed because of possible overhead. Some people are seeing those notes and feeling them as a problem. The best advice to them is ignore it. Tuning performance it set up for the bigger datasets. With all type of servers (WS,SP) and application servers it could be an option to set this option just there were needed. Everywhere usermod-files are present.

Another thing to be mentioned
Compressing type is default type char. Within financials (like KLP) it is possible to have datasets with almost just number types. In that case compress is binary is better. Las experienced a difference of 60% sizing in these two options. As these files were also transferred overall time also decreased. The testcase we used were datasets up to 100Gb (after compression) the real migration planned is even far bigger.

logfootprint
logging
Every sas server (service) has his own loggin location. It can be centralised.
Logging has his target on
  1. forensic research
  2. capacity planning
  3. problem/incident solving
Make it possible to use logfiles in that way.
Make some analyses prepared to show




Added config actions


rc.sas - cleanups schedule
Cleanups must be planned regular scheme. Proposal monday-morning at 05:00pm. (nobody present)
  1. kill ghost processes (looping or left over processes
  2. cleanup all left-over sas-work files, preventing shortage
  3. cleanup and gathering logfiles, preventing excessive growing


environment - Rc.sas profile.sas

The system should start up reliable.
The best way is to restart services on a regular scheme. (proposal weekly)
With Unix systems the extra advantage is that security within the running services will be refreshed
This is a serious pitfall of using Unix changing the security won´t help if not restarted of involved services

root owned files sasauth

There are 3 files: sasauth, elsrv, sasperm, needed to have root rights. These are critical files to secure environments, there fucntionality should be clear
The installation instructions aren not clear about this. Just a note is giving good ifnormation
kb15231 SAS(R)modules that must to have the setuid bit set to root in the UNIX environment.
A script is developped to be able executed it as a sudo commnad (9.2 9.3) eliminating the need using the root-key.

autoexec config usermods

The metadata deployement of 9.3 has many files for user_mods.


Added config actions


DNS Mail TNS

DNS
Everyone is convinced of the benefits using DNS (Domain Name System).
At setting up new logical machines, use logical names no machine names.

Port-numbers can not always be used. Logical names are sometiems required
Regsitrate all used fixed portnumbers in the "etc/services" file with logical names.
propogate these definitons to related clients and servers.
.htdocs or primary docuroot is the connection to the webserver part. It is used for static artifacts. These are html-pages pictures not beign modified.
The configuration can be made simple by: Check and validate the functionality before the hand over to the users.
Think about clustering of webservices.


Mail
Mail message delivering is a simple way to get information in time, no doubt about that. SAS (and other components) is able to use this.
Make the option of mail available (bulkmail - smtp port 25 outgoing).
TNS
This is the Oracle approach similar to DNS. Don't let users/customers get swamped in this. Give the option to run this a smooth as possible.
ODBC DB/2 and others have similar matters tot do.
The TNS can be bypassed by thin client approach.



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Scheduling    Experiences    top  bottom

Configuring SAS desktop




The parts needed for configuration must be well isolated.
Some help can be found with batch files environtvariablen and linkin (mklink Windows , ln softlinks Unix)

If this is not done there will be pop-up a situation of something not going well. And then finding not able to do something with it. The only option left then is defining a new desktop stack again. Normally a long duration not to be accepted by the users/customers.

roaming profiles

Flex workin areas are common in offices. As consequence the personal settings are required to move also over the locations
Roaming profiles is something to deal with. It should work well according to MS-rules, but that is not always true. Microsoft has additional information.
MS cc732275 Folder redirection. wiki Roaming_user_profile And the part (see installation) of the environment must worked out together.


process Environment

Every process get some settings by a environment. In Windows many environment variables are available. wiki Environment_variable These can be used to get it all isolated and well working. In debugging bad behavior this a source to reviewed.
The use of batch files and commands is not to be missed MS cc772390

DATA connections

The business data and all other aritfacst are expected to come with the app-server connection. This only is required with WEb-access
In the hardening chapter is mentioned the major clients are able to by-pass this. Even worse Eguide is promoted to have an Egauto project flow.
In case of batch processin all data should be pre-defined. The most easy wasy to achieve with an autoexec approach. "sasappl"

user instructions

together Mostly left out as found very complex to get it right and understnadable.

key pswd synchronisation

The connections are everywher storing some information to get seemless access.
On the desktop



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Scheduling    Experiences    top  bottom

Configuring SAS meta data




This is a new job to do since SAS version 9.

It was hidden in the past with "SAS integration technologies" and in tools like "WA" (now DI or dataflux) and "EIS" (now Olap).
bi di SAS websrv

Meta data security

Configuring the meta data security (SAS), the same basic approach as to host security (already present?) can be followed: There is a big difference in just using WEB-access or the rich desktop clients.
See the hardening chapter. Meta data security is mainly menu-tailoring, not the really security.


bi di SAS metsrv

Log Server / Monitoring

Monitoring of events is new since SAS 92. It is implemented by the ARM standard (v4) originating from Tivoli. With a arm-4 monitor server connected all events can be centralized managed.

The configuration of the log-server is done by xml-files.
bi di SAS appsrv

Application servers

Application servers better indicated as services, avoiding meaning hardware, are SAS processes with all business data connectedto it.
It can run on the host as a process owned by: It is the switching of key-ownership that get be worried in security evaluations. See the hardening chapter.


User identities - synchronization

As User (and groups) normally are centrally managed, an synchronization with those sources is highly recommended.

The reason that identities must be defined in the meta data is that all kind of information is getting connected to it. This information is not available elsewhere.

Not all user settings are definied in metadata. The property of admin-users are definien by the file: omaconf.xml. This includes the sas unrestricted admin.

The synchronization is described in the hardening chapter.
meta secure 1

User Groups - Internal security

Focusing on ACT´s users and groups needs one word to explain. The ACT is: Access Control Template. This concept is nor found in other security tooling like RACF or AD.
The ACT is a template to be applied on objects. Avoiding to need to code the same set lines over and over again. With this concept the designing off the templates is the most important task.
The security in the meta data is described in the hardening chapter.

Internal security is possible since 92. This option has no effect on the needed host security. When becoming the way of granting access to all kind of data the required security monitoring will get very important

Some tools are requiring automated meta data-update. This automated update (unrestricted) can cause conflicts in getting a secure environment.



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Scheduling    Experiences    top  bottom

Scheduling

sas schedule Scheduling is the foundation of grid computing roll out.
It it the enginf of scheduling with many solutions. Altough only visable with SAS metadata ingterfaces.
In those aspects it can not be left out of an installation proces.

Within the Java (mid-tier) it kooks like java-scheduling is used.
Other optiosn like a system scheduler (at cron) are alos options.
Intelligence Platform issues

drama

LSF platform , Grid

The schedule part is not documented with many guides. scheduling (index)   scheduleug

lsf scheduling - workload management (platform/ibm)

In-Process Scheduling

090-2010 environment OS Tuning a Distributed In-Process Scheduling Server
Because the distributed in-process scheduling server and the JMS queue manager are automatically configured, the default configuration values are acceptable for most situations. However, you can use these tips to optimize the performance of distributed in-process scheduling:-



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Scheduling    Experiences    top  bottom

Experiences installations

Way problems

XCMD Eguide - Local SAS

License files alternates

drama

Using UNC-names Windows

drama




drama

Change Options DI

In earlier releases of the product the macro variables/options associated with "Enable optional metadata macro variables" were key to proper product functionality. Changes in interconnectivity and authentication topology across SAS environments (Workspace Server to Metadata Server, Data Step Batch Server to Metadata Server) have removed the need for these options, so the default setting for the "Enable optional metadata macro variables" option is being changed from Yes to No beginning with SAS Data Integration Studio 4.7 (SAS 9.4M0).

As you have noted, this does not effect the setting of this option in jobs that already exist. To address this need SAS Data Integration Studio development created a plug-in that enables you to make bulk changes to some Job and Transformation options. With this plug-in you can alter the setting of the "Enable optional metadata macro variables" option for all your existing jobs without having to open and modify each individually.

You can download the plug-in from the following location: ftp://ftp.sas.com/techsup/download/dataintegration/ChangeOptions.zip This plug-in will work with all releases of SAS Data Integration Studio beginning with 4.21. The .zip flie contains a README.TXT that outlines how to install and use the plug-in.

I am currently working with product development on getting this plug-in's functionality expanded so it will handle all job and transformation options. The hope is that we will have this included as part of the product in a future release.
(Tom Hahl 2013, DI group linkedin)




User setttings issues

XCMD Eguide - Local SAS

drama
Update-Change
XCMD and SAS 9.3: working together again(sept 2011 CH)  
Problem
X functions (call the OS) do not work any more, using SAS Eguide as interface.

Analyses
When having installed Eguide and SAS classic (Foundation) on your windows desktop and getting "Server Execution Failed".
The action normally is a command to the Windows environment like create or list directories. Groovy and possible others are also requiring xcmd. The logic to directory access can be solved with SAS-code since 9. There is no reason to block xcmd access as long the environment to X is secured well.
Check your windows registry. Eguide is starting a local server. Several places in the registry (windows administration) are possible in effect.

HKEY_CLASSES_ROOT\CLSID\{440196D4-90F0-11D0-9F41-00A024BB830C}\LocalServer32

HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES_ROOT\CLSID\{440196D4-90F0-11D0-9F41-00A024BB830C}\LocalServer32

--\SAS\SASV9\SAS.EXE -config "--\SAS\SASV9\sasv9.cfg" -objectserver -nologo -noterminal -noxcmd



The -- should be the real location. It is a SAS adminstrator task to solve it. This together with other staff. On closed desktops this must be foreseen in advance of a roll-out. For them, see: kb20363   kb15720   kb23546  

little can be found anymore on SAS base on a desktop. Looks to be renamed.
The following is the java integration developer: itechjcdg zero configuration workspace server

The following is information about the server side: sasdummy 2009/11/19 X and SYSTASK blog. Solution
X functions are closed by design. The Platform Administrator is able to re-open it.
With all new functions Dopen, Dclose, Fopen etc. there is access to directory/files without having to use XCMD. For that part, X is not necessary anymore.

The program to change registry settings out of the blog 2009/11/19 may be used.

2012 J.A.Karman (medio 2009)

XCMD Eguide - Integration Tech / metadata

mood Problem
X functions (call the OS) do not work any more, using SAS Eguide as interface on WS or SP server.

Analyses
When using SP or WS server (Foundation) on your windows desktop and getting "Server Execution Failed".


The following are links were to find the xcmd switch: Solution
X functions are closed by design. The Platform Administrator is able to re-open it.
With all new functions Dopen, Dclose, Fopen etc. there is access to directory/files without having to use XCMD. For that part, X is not necessary anymore.

2012 J.A.Karman (medio 2012)




drama

umask Personal - Unix likes

Generic
As of the Unix alikes the user/owner is repsonsible setting access rights.
Te standard way of a user setting in a commandline does not work with SAS. It has to be solves within scritps. kb38040 ulimit (MAXSIXE) has the same approach.
Miner
Is requiring
drama

Client-Side R Versus Server-Side R

As simple it looks like. When the client is on a closed desktop and/or in a virtualized environment it is an impossible choice
R has its limitations because it is all memory based.
Running at server side it is requiring XCMd like (Rlang) settings. As long the server is running is personal user setting it is no issue.





Intelligence Platform issues

Requirements Solutions

drama These are hard to find, as with all suppliers. The tactical approach looks like first implementing afterwards the information. Consumers are protected by laws information sould be given in advance, business should be able to do this affairs by them self.

9.3 System requirments search with solutions based bundles.
Some information:

When tried several options see the same shared component everywhere popping up.
The metdataserver always has SAS/Base and SAS/connect.
Clients almost always have SAS managemetn Console en very often the Add-in Microsoft Office.
drama

Start up of services

The follwing is out of the installation/configuration phase, it should be there on an operational way:

drama

Java versions

There are 32-bit and 64-bit versions aside the version level of Java.
Many products are requiring a dedicated level/version of java
You will end up with many Java versions to run on a machine.

drama config in installation

Configuration of installation

The installation files should be not modified with goal of configuration.
For some reason this segregation is not well done. Even tips to get nice or better results are stating to change the installation files
SAS Portal and BI Dashboard: Customizing the Tabs (TA 27/09/2012)

drama config in installation

Unix quirks Configuration



drama authenticaion

Reconnect to metadata - Identity

The identiyy is a major object with all access an autorization. When a request is passed from one system to another, it is often preferable that the requesting user identity is passed along with the request
Identity Passing (bisecag)

When the user identity should be different / is failing, an overwrite is needed. A clenaup blocking every access or an different SAS metadata identity.
options metauser="%scan(&Metaama2_u,1)" /* 'sasadm_userid' */
metapass="%scan(&Metaama2_u,2)" /* 'sasadm_password' metapass='' */






OS system environment

drama

OS environment

link unexpected sources
sas: 090-2010 environment OS sasenv
 


drama

Host autentication - file exchange

Locking of files on OS level can have an impact of getting not workable.


drama

Java

It is a virtual machine (JVM) wiht its own langauge (java) and own versioning that SAS is building on. Release/version changes are having impact.




Unable to initialize TCP/IP subsystem

fire Problem
SAS/Connect fails.

It fail with SAS 9.1.3 under Windows-7 with this error. Amamzingly an other users on the same machine is succeeding in getting the connection.
The Windows firewall has been activated but not tuned. At a Windows Xp instalaltion without the firewall it is working well.

Analyses

Needed tools:
The described situation occured on a closed desktop. We need soemthing to elevate rights to an (restriced) admin-users. Found a way by getting a additional dedicated key with the rights bound to some named machines.



Option-1, Searching internet:
On Windows platforms the absence of an entry for "localhost" can cause this error message with SAS/CONNECT and other products. I don't know if it would cause a problem accessing HTML SAS Help. On Windows and Unix platforms, you'll need an entry similar to:
127.0.0.1 localhost


The SAS-note kb 3540 Is of the old time.
Background:
Until 2004 IBM did not have his own TCP/IP stack on Mainframes.
SAS/C was the common way by al lost of suppliers including IBM to implement a machine independent solution using TCP/IP. It was SAS/C delivering a standard way. Sounds incredible as SAS/C now is withdrawn by SAS as a offering. SAS will now use the other present TCP/IP stacks already presetn at OS-level.
The proposed change executed and tested. The problem: Not solved. As expected, other guys could work on same machine.

Option-2, deduce the issue by behavior and testing:


Solution
Working on...


2012 J.A.Karman (medio 2010)




Operating System / Virtualization


cloud text

Virtualization

Virtualization support (official)
pcn/virtualization (support sas) The note they expect functional equivalence but when problems arise is is customers responsibility is crude and cannot be otherwise.
There are notes modify (according fix/kb) memory settings for java. (DI SMC)
The bad thing is these configuration files are part of the installation files. Yes the virtualized managed installation to be changed.
Citrix
A search to citrix on the sas support site:
App-v (MS) - Softgrid - CCMM
The repackaging of SAS into a APP-v (microsoft) can become very challenging of all involved limitiations. Out of memory java heap

Xvfb Virtual Frame buffer
Problems or performance with grpahical procedures. If an X server is not available on the server machine, an alternative is to use the X virtual frame buffer (Xvfb) as supplied by the operating system vendor. Refer to your vendor-supplied documentation for information about the use of Xvfb. Setting the SAS_ALT_DISPLAY Variable for X Window Systems on UNIX (9.4 SAS/Graph)
Xvfb or X virtual framebuffer is a display server implementing the X11 display server protocol. In contrast to other display servers Xvfb performs all graphical operations in memory without showing any screen output

drama

Unix Ulimits

Ulimits are specific internal setttings in an unix system. Enabling to get it work or just tuning.

Paul Homes I ran into a ulimit issue with JBoss on Ubuntu 64-bit and had to do an additional PAM/su config change for the limit changes to apply (when JBoss was started by root su-ing to sas in an init script). I wrote a blog post about it here: sas-jboss-too-many-open-files
Perhaps you have the same issue on RedHat?


locked

File locking

Filelocking is done to prevent corruption of data while having many processes and users running.
Filelocks is new at 9.3: It is normally an OS fucntion to lock files. "C" has different IO fucntions to suppport that.
As IO is normally buffered it is logical to lock a file when writing. The behavior you noticed is that locking on logfiles has been implemented.

The logparm option (normal SAS-base log (lesysoptsref)

Notice the buffered options with logging, with Eip there is something as:
I am missing the filelocks setting , could be mostly expected to be the normal SAS system-option filelocks.
drama
System Modification
zsysprog installmethods -smp

IBM rational



General steps    Server rollout    Desktop rollout     Configure Server    Configure desktop    Configure Metadata    Scheduling    Experiences    top  bottom
home-SAS    SAS-SAAS    First steps    Installation    Hardening    Operational    Using    My Notes

© 2012 Jaap Karman (21 Apr 2012)