Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

The SAS Enterprise Miner client is a Java application. In a Windows
environment, it also interacts with the SAS Enterprise Miner Tree
Desktop Application (TDA), an MFC application for interactive tree
editing.

There are three common ways of deploying the SAS Enterprise Miner
client.

1. Local installation: This involves installing the SAS private Java
Runtime Environment (JRE), the SAS Enteprise Miner Java application, and
the TDA on each client workstation machine. For SAS Enterprise Miner
5.2, it's also necessary to install the SAS Analytics Platform there.
The installs are done in a semi-automated way by the SAS Software
Navigator using a SAS Enterprise Miner two-tier plan and selecting the
client tier of the plan.

2. Java Web Start (JWS) deployment: This involves Java network
launching protocol (JNLP, a type of XML) files. The JNLP files
communicate through Java Web Start from the mid-tier server to a
client machine, where a publicly installed Java 1.4.2 exists. The
JWS programs on each end compare notes to see if the version of the
application that is cached at the client is the current version. If not,
or if there is no cached application, then JWS sends Jars (program
files) from the mid-tier to the client (about 40M bytes).

If the programs are already cached and the version is correct, no file
transmission occurs. Then the application is run on the client. If you
want interactive tree editing and the client is Windows, the TDA would
need to be locally installed.

3. Terminal server: Using Windows terminal services or Citrix
MetaFrame, clients log on to a server machine from their client
workstation. This method is the simplest to maintain for SAS Enterprise
Miner 5.1, and is tied for simplest with JWS deployment for SAS
Enterprise Miner 5.2. For more information, see SAS Note 17312.

Options 1 and 2 actually execute the SAS Enteprise Miner Java client on
the client workstation. Option 3 executes the client on a server machine
but, because the clients use very little CPU, having multiple clients
running on one machine is typically not an overhead problem.

Note about Java Web Start client deployment:

SAS Enterprise Miner 5.2 introduces a new component called SAS
Analytics Platform. SAS Analytics Platform is a Java application that
contains all the mid-tier RMI functionality common to SAS Enterprise
Miner and two other solutions.

SAS Analytics Platform is delivered with an embedded Web engine that
allows it to offer certain administrative functions over the Web, such
as showing which users are logged on and which have workspace server
sessions that are active. The single port this abbreviated engine uses
defaults to 6098.

SAS Analytics Platform also provides this server to SAS Enterprise
Miner. SAS Enterprise Miner's part of the mid-tier application
dynamically configures the JNLP files that are necessary to run the Java
Web Start (JWS) client. No manual tailoring is necessary. The user
addresses the JWS client by a URL that contains the machine and port.
  
   http://mymachine.sas.com:6098/EnterpriseMiner/

The JWS program "javaws" is connected to the imbedded engine by the SAS
Analytics Platform and is used from the SAS private JRE.

SAS Enterprise Miner versions earlier than 5.2 required manual tailoring
of the JNLP control files and installation of the JWS client deployment
application in an independent Web server (such as Tomcat).

Operating System and Release Information