Installation Instructions: SAS Package Reader
Version 1.6

Installing the SAS Package Reader Archive

To install the spk.tar package, unpack the package using a TAR command. You can unpack to any directory. The contents of the spk.tar package are stored in a directory named spk.

To install the spk.exe package, run the installation wizard and provide the requested information. Help is available to instruct you on valid values for each parameter. By default, the contents of the package are installed to <SAS_HOME>\SPK.

Configuring the SAS Package Reader

The spk.exe package has an installation wizard that completes the configuration of the SAS Package Reader; therefore, no additional configuration is required. If you installed the spk.tar package, you must complete the following instructions to configure the SAS Package Reader.

  1. Read the license information in the license.txt file. This file is available in the spk directory that was created during installation.

  2. Modify the configuration file (user.cfg)

    The user.cfg file that is installed in the spk directory stores configuration information for the SAS Package Reader application. To complete the configuration file, you must specify a directory for temporary files, the command to invoke a Web browser, the command to invoke the Java Runtime Environment (JRE), and the option to extend CLASSPATH for the JRE.

    The syntax for the user.cfg file is as follows:

       [AtkPropertiesTable]
       setProperty(TEMP, "temporary-file-directory")
       setProperty(BROWSER, "command to invoke a web browser")
       setProperty(BROWSER_COMMAND, "{0} {1}")
    

    Edit the user.cfg file and change the following properties so that they contain appropriate values for your local environment. Any backslash (\) character in the property values must be represented as a pair of backslashes (\\).

    TEMP
    Specify a directory where the SAS Package Reader application can store temporary copies of package entry contents for display by a Web browser. The permissions for the specified directory must be set to allow the SAS Package Reader application to write to that directory. If there are spaces in the directory name, the name must be enclosed within a single backslash and quotation marks. For example, represent the directory name "my temporary directory" as \"my temporary directory \". Notice that the backslash is not part of the path, and therefore it should not be represented as a pair of backslashes.

    BROWSER
    Specify the command, including the path, that invokes the Web browser, including any command options that are used by SAS Package Reader application. If there are any spaces in this value, the value must be enclosed within a backslash and quotation marks. For example, represent the command /path/mybrowser -option as \"/path/mybrowser -option\".

    Note: Do not modify the BROWSER_COMMAND property.

  3. Modify the start-up file (spk.txt)

    The spk.txt file is installed in the spk directory. It is a sample file that shows the typical configuration information that is used to launch the SAS Package Reader application. The syntax for the spk.txt file is as follows:

       COMMAND = {0} {1} {2} {3} {4}
       ARG0 = Java-runtime-path and classpath option
       ARG1 = SPK-path/spk/spk.jar:SPK-path/spk/atkcore.jar:
              SPK-path/spk/atkjfc.jar:SPK-path/spk/atkx.jar:
              SPK-path/spk/brgorb.jar:SPK-path/spk/iomdriver.jar:
              SPK-path/spk/iomprx.jar:SPK-path/spk/netutil.jar:
              SPK-path/spk/orb.jar:SPK-path/spk/swingall.jar:
              SPK-path/spk/retrieve.jar
       ARG2 = com.sas.apps.treader.SpkReader
       ARG3 = -ConfigFiles file:///SPK-path/spk/user.cfg
       ARG4 = -mimetypes file:///SPK-path/spk/mimetypes.cfg
    

    Edit the spk.txt file to supply appropriate values for your local environment. Any backslash (\) character in the parameter values must be represented as a pair of backslashes (\\). Change the parameter values as follows:

    COMMAND
    Do not modify this parameter.

    ARG0
    Replace Java-runtime-path with the path and command for the Java Runtime Environment you want to use to execute the SAS Package Reader application as well as the option to extend CLASSPATH. If you are using the Java 2 JRE from Sun Microsystems, use the value:
       java -cp
    

    ARG1
    Replace all occurrences of SPK-path with the path for the directory in which you installed the SAS Package reader application. The delimiter between the directories is determined by your operating system. The example uses a colon, which is the delimiter for UNIX. A semicolon is used by Windows platforms.

    ARG2
    Do not modify this value.

    ARG3
    Replace SPK-path with the path for the directory in which you installed the SAS Package Reader application.

    ARG4
    Replace SPK-path with the path for the directory in which you installed the SAS Package Reader application.

Running the SAS Package Reader

If you installed the SAS Package Reader in a Windows environment, the application is registered with the Windows registry. You can launch the Reader by double-clicking on a file with a .SPK extension, or by running the application from the Run window.

If you installed the SAS Package Reader in an environment other than Windows, you can use the JBoot application starter to launch SAS Package Reader. Submit a command like the following to launch the application:

Java-runtime-command SPK-path/spk/JBoot.jar JBoot -b SPK-path/spk/spk.txt -file package-file

where

Java-runtime-command
is the appropriate command to launch your Java Runtime Environment, with the option to extend classpath. If you are using the Java 2 JRE from Sun Microsystems, use the value:
   java -cp

SPK-path
is the path for the directory in which you installed the SAS Package Reader application.

package-file
is the path and filename of the package file that you want to display in the SAS Package Reader application.

Updated Documentation and Software

If you encounter a problem installing or configuring the SAS Package Reader, or if you have a question, see the information available from the SAS Integration Technologies Web site.



Copyright © 2003 SAS Institute Inc., Cary, NC, USA. All Rights Reserved.