Contents SAS/IntrNet 9.1: SAS Design-Time Controls Previous Next

Components in the SAS Design-Time Controls Package

The software components in the SAS Design-Time Controls package can be divided into four categories: client components, Dreamweaver components, Web server components, and SAS server components. This section describes the function of these components, lists the files that comprise them, and outlines the installation process for the components.

Client Components

The client components in the SAS Design-Time Controls package are the controls themselves. The controls are ActiveX controls that are designed to function inside of an HTML editor. An icon represents the control in the editor window or on the Web page that you are constructing. A tabbed dialog provides a way to view and set control properties. The controls use the HTTP protocol to connect to your Web server, run the SAS/IntrNet Application Broker, and connect to the SAS/IntrNet Application Server.

All of the controls in this release of SAS Design-Time Controls are bound into a single file named sasdtc.ocx. You do not need to perform any manual steps to install the controls. The sasdtc.ocx file is placed on your hard drive and registered when you select Client Component from the Components list box that is presented during the installation of the SAS Design-Time Controls package.

Dreamweaver Components

The Dreamweaver components are client components that provide SAS Design-Time Control support for the Macromedia products Dreamweaver and Dreamweaver UltraDev. If you use either of these tools, then you must install the Dreamweaver components after installing Dreamweaver. After you install the Dreamweaver components, the Design-Time Controls are then available as selections from the Dreamweaver Insert menu or via the SAS panel of the Dreamweaver object palette.

You do not need to perform any manual steps to install the Dreamweaver components. They are installed when you select Dreamweaver components from the Components list box that is presented during the installation of the SAS Design-Time Controls package.

Web Server Components

If you use the Design-Time Controls to create static Web pages, then the only Web server component that you must have is the Application Broker. The Broker is part of the SAS/IntrNet product. For information about the Application Broker, see the documentation for the Application Dispatcher component of SAS/IntrNet software.

If you use the controls to create dynamic Web pages, then you need to install the Application Broker on your Web server, and you also need to install support for Active Server Pages (ASP) or Java Server Pages (JSP). The controls output ASP or JSP code instead of HTML in order to create dynamic Web pages. When the ASP or JSP page is served, the code makes a connection via HTTP to the Application Broker. The Broker contacts the Application Server, runs the requested program, and returns the HTML. This HTML is deposited into the Web page stream by the ASP or JSP code.

Enabling ASP Support

To enable ASP support you need

You can install Microsoft Internet Information Server either before or after you install the AppServer.dll file.

Enabling JSP Support

To enable JSP support you need to

  1. Set up a JSP server environment on your Web server machine. This is additional software that is not provided by SAS. JSP environments exist from various vendors for many different operating systems. Install and configure your JSP server environment before proceeding with this part of the installation process.

  2. Install the file named AppServer.jar that is provided in the SAS Design-Time Controls package. The JSP code that is generated by the controls calls the Java classes that are in AppServer.jar in order to connect to the Application Broker when the page is served. To install the AppServer.jar file, you must

    1. Select Web Server Component from the Components list box that is presented during the installation of the SAS Design-Time Controls package. The installation program places the AppServer.jar file on your hard drive.

    2. Copy the AppServer.jar file to the machine where your JSP server environment is installed. If you transfer the AppServer.jar file to a different machine, then make sure you perform a binary copy or a binary transfer. Transferring the AppServer.jar file in text mode corrupts the file.

    3. Find the CLASSPATH setting for your JSP server environment and add the full path for it to the AppServer.jar file. For example, if you are using JRun from Macromedia to serve your JSP pages, then you might have a properties file that contains something similar to the following line:

         java.classpath=c:/jrun/classes

      After adding the path for AppServer.jar, the line would look like the following (single line is wrapped for readability):

         java.classpath=c:/jrun/classes;c:/Program Files/SAS/
     SAS Design-Time Controls/AppServer.jar

      After changing the CLASSPATH setting, you will probably need to restart your JSP server.

SAS Server Components

The SAS Design-Time Controls require that some additional programs be made available from your Application Server. When you access the controls from within the HTML editor, they connect to the Application Server and run various programs. These programs return lists of data sets, lists of variables, and the control output. All of the required programs are contained in a SAS catalog named WEBSDK1.

The WEBSDK1 catalog is shipped with Release 8.2 and later of the SAS System. If your SAS server is running Release 8.2 or later of the SAS System on any platform, proceed to the Important Information for Users of Version 8 and 9.

If You Use Release 8.1 and Earlier of the SAS System on Windows...

If your SAS server machine runs the Windows operating system, then you do not need to perform any manual steps to add the WEBSDK1 catalog. When you select SAS Server Component from the Components list box that is presented during the installation of the SAS Design-Time Controls package, the catalog is placed in the proper subdirectory under your SASROOT directory.

Note: If you are running Version 8 of the SAS System, read the Important Information for Version 8 Users.

If You Use Release 8.1 and Earlier of the SAS System on UNIX, VAX/VMS, and OS/390...

Note: Before you can install the WEBSDK1 catalog, you must install the SAS System, including the SAS/IntrNet product, and you must configure at least one Application Server.

To add the WEBSDK1 catalog to the UNIX, VAX/VMS, and OS/390 operating systems, you must use the CIMPORT procedure to manually import the catalog. To import the catalog

  1. After you install the SAS Design-Time Controls package on the client machine, examine the install directory and look for the following two CPORT files:

    • websdk1-version6.stc
    • websdk1-version8.stc

    Use the first file if you are installing to a SAS server that is running Version 6 of the SAS System. Use the second file if you are installing to a a SAS server that is running Version 8 or later of the SAS System.

  2. Copy the appropriate CPORT file to the machine where your Application Server is installed. Make sure to transfer the file using a binary copy or a binary transfer. Make a note of the path on the destination host to which you copy the file. You need to supply this path in the code in step 4.

  3. Make sure that you have write access to the SASHELP library and start the SAS System.

  4. Modify and submit the following code to import the WEBSDK1 catalog.

    On UNIX
    /*modify the path for infile= in the code below*/
libname myhelp '!SASROOT/sashelp';
proc cimport infile='full-path-to-websdk1-version8.stc'
lib=myhelp;
run; quit;
    On VAX/VMS
    /*modify the path for infile= in the code below*/
libname myhelp 'SAS$HELP';
proc cimport infile='full-path-to-websdk1-version8.stc'
lib=myhelp;
run; quit;
    On OS/390
    /*modify the data set name for infile= in the code below*/
proc cimport infile='DATA.WEBSDK1.V8.STC' lib=sashelp;
run; quit;

  5. If you are using Version 6 of the SAS System, then you can restart your Application Server and proceed to Testing the Installation. If you are using Version 8 of the SAS System, then you must perform the steps that are outlined in Important Information for Version 8 Users.

Important Information for Users of Version 8 and 9

Beginning with Version 8 of the SAS System, the Application Server will only run programs if they are listed in a PROGLIBS statement in the APPSRV procedure that starts the Application Server. You must find the SAS program file that starts your Application Server and edit it.

  1. Locate the SAS/IntrNet service directory that is created when you set up the Application Server:

    On Windows
    From the Windows Start menu, select Programs  [arrow] SAS  [arrow]  IntrNet  [arrow]  Service Directories. A view opens that displays the folders that contain your SAS/IntrNet Application Server files.

    On UNIX or VAX/VMS
    The service directory is typically a subdirectory of the intrnet directory that is in your home directory.

    On z/OS
    The service directory is a partitioned data set with the name prefix.WEB.service.

  2. Among the files in the service directory is a SAS program file that starts the Application Server (the default name for this file is appstart.sas). This file contains code for the APPSRV procedure. Insert the following code fragment somewhere after the PROC APPSRV statement and before the RUN statement:

       proglibs sashelp.websdk1;

  3. Restart the Application Server.

  4. Repeat these steps for each Application Server service that you want to use with SAS Design-Time Controls.

Note: z/OS is the successor to the OS/390 and MVS operating systems. SAS/IntrNet 9.1 for z/OS is supported on the MVS, OS/390, and z/OS operating systems and, throughout this document, any reference to z/OS also applies to OS/390 and MVS, unless otherwise stated.


Contents SAS/IntrNet 9.1: SAS Design-Time Controls Previous Next