Un-installing previous versions

If you had a previous version of ULC installed make sure you completely erase it.

IMPORTANT: Remember to reset the browser's helper application which is used to start ULC applications when running the UI Engine as a helper. (MIME type: application/x-ulc; file extension: .ulc).

Once you have un-installed existing ULC components copy the files from the CD to your hard disk.

top

Setting up the UI Engine

ULC R3.1 has been designed to run with Java 2 (JDK1.2.2). Follow the instructions below:

Download and install the Sun Java Runtime Environment (JRE) 1.2.2

Note: Ensure that the International version of the JRE is downloaded as all ULC samples require the internationalization support.

Set the ULCJREROOT environment variable for the location of the JRE.
(e.g: set ULCJREROOT to C:/jre1.2.2 or C:/jdk1.2.2/jre).
This variable must be set. If the variable is not set the assumption is that a JRE installation is available on the client machine and the system path and classpath variables must point to this installation. The required Swing classes are bundled together with the Java2 JDK and hence the ULCSWINGHOME environment variable is ignored.

Note: Smalltalk Users can use the IBM supplied install shield to install the UI Engine.

After the UI Engine has been installed ensure that the environment variable ULCUIHOMEis set to the directory where the UI Engine has been installed. This variable is required by the sample HTTP Server provided.
(eg: set ULCUIHOME=C:/ULC/R3.1/UIENGINE).

Running the UI Engine outside of a Web browser does not require any further configuration. You can start it immediately from UIEngine/bin/UlcUI.exe.

See Setting up the UI Engine as an Applet for the steps required for running the UI Engine inside a Web Browser as well as Web Integration.

top

Setting up the ULC Java Application Controller

In order to run the Java Application Controller (a simple desktop) you need to change one line in its configuration file (Java/Applications/AppController/AppController.properties). The Controller must know the absolute path name of the ULC distribution base directory:

 # *** ULC runtime home (absolute path) 
Ulc.runtime.home=C:/ULC/Releases/R3.1

You must change that line once to reflect the path to the top ULC directory in your local installation. Use '/' as file separator.

For example:

Ulc.runtime.home=C:/ULC/R3.1 

top

Setting up the ULC Http Server

The ULC Http server is a custom Web server that is used to read html pages and replace the token ($WEBHOST) in these pages to enable connecting to running ULC application servers using a web browser.

In the file R3.1/HttpServer/lib/HttpServer.properties you can set your own document root directory which will be searched first. Setting this parameter is not required for the samples to work correctly.

For example:

HttpServer.documentroot=c:/ULC/Releases/R3.1/HttpServer/lib

For examples of the specially formatted web pages please unpack the file R3.1/HttpServer/lib/httpserver.jar and look in the directory.

R3.1/HttpServer/lib/com/ibm/ulc/httpServer/resources/*.uhtml 

To start the HttpServer on the default port run the batch file:

R3.1/HttpServer/bin/httpserver.bat

Note: The sample ULC Http server is shipped with ULC Smalltalk as well as ULC Java.
When testing the Http server you must select either the ULC Java or the ULC Smalltalk link from the ULC Http Home page depending on the ULC environment being used.

top

Setting up the UI Engine as an Applet

The currently supported Web browsers for running the ULC UI Engine as an Applet are Netscape Communicator 4.x and Microsoft Internet Explorer 4 or 5. Both must have the Java Plug-in 1.2.2 installed. See Setting up Java Plug-in for more details.

top

Setting up ULC for Smalltalk development

Note for VisualAge 4.5 users: The instructions below assume that you have already installed the Fixpack 4.5a for the Base as well as for Server Smalltalk.

IMPORTANT: You must upgrade the UI Engine release which was distributed with VA ST: Copy the UIEngine directory from the R3.1 CD over the VASTxy/ULC/UIEngine directory on your local machine. This will upgrade the IBM supplied UI Engine to the R3.1 release level.

To install ULC Smalltalk, follow these steps:

1. Take a clean VisualAge 4.5a, 5.0 or 5.5 image (normally in the newimage directory).
2. Unpack the supplied R3.1/Smalltalk/UlcR3.1.zip file into a temporary directory (tmpDir). The zip file contains ULC R3.1 for VisualAge Smalltalk 4.5a, VisualAge Smalltalk 5.0 and VisualAge Smalltalk 5.5.
   Note: The following files have been supplied in this zip file:
   • Common/import/abtexu.dat
   • Common/import/abtexv.dat
   • Common/NLS/ulccae40.cat
   • Common/NLS/*.tra (17 files)
   • Common/NLS/*.mpr (17 files)
   • Common/bitmaps/*.gif (21 files)
   • Common/ulcidl.swp
   • VAST45a/feature/abtexu.ctl
   • VAST45a/feature/abtexv.ctl
   • VAST50/feature/abtexu.ctl
   • VAST50/feature/abtexv.ctl
   • VAST55/feature/abtexu.ctl
   • VAST55/feature/abtexv.ctl

3. Backup the above files from your existing installation.
4. Prepare the import of the ULC libraries:
   • For VisualAge Smalltalk 4.5a and 5.0 the Common/import/*.dat files must be copied into the importDirectory that is specified in your abt.ini.
   • For VisualAge Smalltalk 5.5 you must use the importer utility as follows:
     

     VAST55/inst/importer.exe -z.target=my mgr dat -z.sourcedir=tmpDir/Common/import

5. The Common/NLS/*.* files must be copied into the nlspath that is specified in your abt.ini.
6. The Common/bitmaps directory must be copied into your local image directory as a sub-directory of the image directory (create it if necessary).
7. If you intend to use IIOP support copy the file Common/ulcidl.swp to your image directory on your local machine.
8. The VASTxy/feature/*.ctl files must be copied into the directory specified in installationPath in your abt.ini, where xy denotes your VisualAge Smalltalk version.
9. Start your image.
10. From the Transcript Tools menu choose the Load/Unload Features... menu.
    • For VisualAge Smalltalk 4.5a and 5.0 select Show IBM ST features. Choose the features:
      • IBM ST: Server, SST
      • IBM ST: ULC - Development
      • IBM ST: ULC - Server
    • For VisualAge Smalltalk 5.5 choose the features:
      • ST: ULC - Development (OTI)
      • ST: ULC - Server (OTI)
11. After the load has completed save your image.
12. If you have installed the ULC samples from a previous release they must be upgraded to the R3.1 release as well. Copy the contents of the R3.1/Smalltalk/Applications directory over your existing VASTxy/ULC/ULCSamples directory.
    The ULC Samples can be loaded into the development image by loading the: ULC ST Examples Run Configuration Map.

    IMPORTANT: All the executable samples on the ULC CD have been packaged for VisualAge Smalltalk 5.0. VisualAge 4.5a and 5.5 users must repackage the samples or run the samples from the development image.

top

Setting up ULC for Java development

This release of ULC Java requires VisualAge for Java V3.0 or V3.5 with Java2. To verify that you have the Java2 support installed, successfully start your VA Java IDE and from the Help menu select the menu option "About VisualAge".

The version information should read:

Version 3.x
IV3-x JDK1.2.x

If you do not see the above version information obtain the VisualAge for Java V3.0 or V3.5 with Java2 support and install it before proceeding.

1. Take a fresh VA Java 3.0/3.5 client (IDE.ICX) with the Java2 support.
2. Unzip the file R3.1/java/UlcJR3.1.zip over your VA Java 3.0/3.5 directory.
   Note: Ensure you use the option to unpack the files using the supplied directory names. (eg: -d in PKZIP)
3. Start the IDE. This will pre-install the ULC features.
4. From the Workbench choose the File->Quick Start menu (F2) and choose the Feature->Add feature option.
5. Load the following features:
   • IBM Ultra Light Client - Server
   • IBM Ultra Light Client - Server Development
   • IBM Ultra Light Client - Server Examples
   If you would like to run the UI Engine inside VA Java as well then load the feature:
   • IBM Ultra Light Client - UIEngine
   If you would like to use the ULC Test Environment inside VA Java as well then load the features:
   • IBM IDE Utility class libraries 3.x
   • IBM Ultra Light Client - Test Workbench
6. Exit your Workspace and restart it.
7. To verify that all the projects have been installed correctly do the following:
   • Select the Ulc Java UI project and click the run button on the Workbench.
     The ULC Monitor window should open and in the Console window of VisualAge Java you should see that the UI process is running.
   • Select the Ulc Java Hello project and click the run button on the Workbench.
     The Hello world sample should be running on your desktop at this point.

top

Setting up Java Plug-in

Download the Java Plug-in 1.2.2 from Sun. After installing the Plug-in you can start the Http server and run the application controller and access the Java Plug-in enabled web pages via the Http server home page.

It is recommended that you also download the HTML Converter Tool from Sun that will help you convert your web pages that use Applets to the format that is compatible with the Plug-in.

top

Testing the Environment variables

After installing all the above features use the supplied R3.1/testenv.bat batch file to validate that all the required environment variables have been correctly initialized.

top