About this Release

• Cleanup of the overall ULC API to match closer to the Swing API allowing developers moving from the Swing world to quickly get up to speed in ULC.
• Number of ULC widgets have expanded API, once again bringing ULC widgets closer to their Swing equivalents.
• Extensible Launcher and Security infrastructure based on industry standard public key certificates allowing ULC applications to be safely deployed across the Internet.
• A new ULCTransport extension mechanism that allows transports to be added on the fly without requiring any change in existing ULC code.
• Improved developer documentation and a new ULC Cookbook.
• ULCDesktopPane and ULCInternalFrame widgets have been added.
• ULCTreeTable improves upon and replaces the previously supported ULCTree widget.
• All ULC code have a new package prefix com.ulcjava.*
• The ULCBox layout now has an optional autoScrollPane property enabling a scroll pane to be added automatically on any layout where the view is not large enough to display its contents.
• ULC applications now have a licensing mechanism and all developers need to obtain a valid license before they can develop or deploy ULC applications.
• The VisualAge Composition editor support has been improved to allow developers to add custom ULC parts to the palette.

Installation

• Installing ULC for development using the JDK
  • Copy/unpack the contents of the ULC release onto a local drive (e.g: \ULC\R4.0).
  • The batch files supplied with ULC check the following environment variables:
    • ULCJREROOT
      If this variable is defined it must point to a valid Java 2 JRE directory (e.g \JDK1.3\JRE).
      Alternatively if this variable is not defined the batch files will default to using the Java JDK installed on the system and in this case the Java interpreter (java.exe on windows systems) must be found on the system path.
    • ULCLICENSEPATH
      If this variable is defined it must point to a directory containing a valid ULC ulclicense.txt file.
      Alternatively the ulclicense.txt file must be placed on the classpath of ALL ULC application servers.
  • The only code that needs to be on your classpath during development is contained in the ULCApplication/lib directory. If you are going to import the code into an IDE you can import the code from the ULCApplication/src directory.
  • To browse the provided samples, Import the source from the ULCSamples/<SampleName>/src directory.
  • Unless you are attempting to extend the UI Engine the UI Engine code does not have to be on your class path nor does it need to be imported into your IDE. The UI Engine can be started directly using the batch file UIEngineDeployment/Development/uiengine.bat or the script file UIEngineDeployment/Development/uiengine.sh.
    If you are attempting to extend the UI Engine and need to browse the source it can be found in UIEngine/src.

• Installing ULC for development within IBM VisualAge for Java

  ULC applications can be built visually using the VisualAge Composition Editor within IBM's VisualAge for Java product. This release of ULC requires VisualAge for Java V3.5 or V3.02 with Java2 support. 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 VisualAge for Java V3.5 or V3.02 with Java2 support and install it before proceeding.

  • Take a fresh VA Java 3.02/3.5 client image (IDE.ICX) with the Java2 support.
  • Unzip the file VAJava/V35/Ulc40_VAJ35.zip over your VA Java 3.5 directory.
    or
  • Unzip the file VAJava/V3302/Ulc40_VAJ302.zip over your VA Java 3.02 directory
    Note: Ensure you use the option to unpack the files using the supplied directory names. (eg: -d in PKZIP)
  • Start the IDE. This will pre-install the ULC features into your repository.
  • From the Workbench choose the File->Quick Start menu (F2) and choose the Feature->Add feature option.
  • Load the following features:
    • Ultra Light Client - Server
    • Ultra Light Client - Server Development
    • Ultra Light Client - Server Examples
  • If you would like to run the UI Engine inside VA Java as well then load the feature:
    • Ultra Light Client - UIEngine
  • From the Workbench choose the menu Window->Options and then navigate to the Resources entry. Expand the resources and edit the Workspace class path to point to a directory that contains a valid ULC ulclicense.txt file. Contact your ULC Vendor if you do not have this file.
  • Exit your Workspace and restart it.
  • To verify that all the projects have been installed correctly do the following:
    • Select the Ulc Java UI Launcher project and click the run button on the Workbench. A list of classes will be displayed. Select the Launcher class.
      Note: The Launcher class must have the ULC Java Base and ULC Java UI projects on its classpath.
    • 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.
  • Read the ULC Developers Guide for more information regarding development within the IBM VisualAge Java Environment.

Release Structure

The ULC R4.0 release has the following structure:

R4.0	ULC R4.0 home directory
release.html	this document
doc javadoc ULCCookbook.pdf ULCDevGuide.pdf	ULC documentation contains the ULC javadoc files the ULC Cookbook the ULC Developers Guide
UIEngine lib launcher.jar uiengine.jar src	UI Engine (client-side) runtime environment library directory launchers for the UI Engine core UI Engine framework components source directory
UIEngineDeployment Applet readme.html desktop.html hello.html pie.html Development readme.html uidesktop.bat uidesktop.sh uihello.bat uihello.sh uipie.bat uipie.sh HelperApplication readme.html uiengineHelper.bat uiengineHelper.sh desktop.ulc hello.ulc pie.ulc JavaWebStart readme.html desktop.jnlp hello.jnlp helloSandbox.jnlp pie.jnlp signing signjars.bat ulctest.keystore	UI Engine deployment scenarios deploy the UI Engine as an applet describes how to set up the environment for applets UI Engine as an applet connecting to "Desktop" sample UI Engine as an applet connecting to "Hello World" sample UI Engine as an applet connecting to "Pie" sample test the UI Engine during development describes how to set up the environment for development UI Engine batch file connecting to "Desktop" sample UI Engine script file connecting to "Desktop" sample UI Engine batch file connecting to "Hello World" sample UI Engine script file connecting to "Hello World" sample UI Engine batch file connecting to "Pie" sample UI Engine script file connecting to "Pie" sample deploy the UI Engine as a helper application describes how to set up the environment for helper applications batch file to start the UI Engine as a helper using the supplied filename script file to start the UI Engine as a helper using the supplied filename UI Engine as a helper application connecting to "Desktop" sample UI Engine as a helper application connecting to "Hello World" sample UI Engine as a helper application connecting to "Pie" sample deploy the UI Engine with Java Web Start describes how to set up the environment for Java Web Start UI Engine with Java Web Start connecting to "Desktop" sample UI Engine with Java Web Start connecting to "Hello World" sample UI Engine within a sandbox with Java Web Start connecting to "Hello World" sample UI Engine with Java Web Start connecting to "Pie" sample signing support sample batch file to sign uiengine.jar and launcher.jar keystore containing the certificate used for signing
UIExtensions PieChart lib pieChart.jar src	sample extensions to the UI Engine "Pie Chart" sample extension library directory "Pie Chart" sample extension components source directory
ULCApplication lib ulc.jar src	ULC Application (server-side) runtime environment library directory core ULC Application framework components source directory
ULCSamples readme.html Hello bin hello.bat hello.sh lib hello.jar src Desktop bin desktop.bat desktop.sh lib desktop.jar src Pie bin pie.bat pie.sh lib pie.jar src	sample extensions to the UI Engine describes how to run the sample applications "Hello World" sample application directory binaries directory batch file to start the "Hello World" sample application script file to start the "Hello World" sample application library directory "Hello World" sample application components source directory "Desktop" sample application directory binaries directory batch file to start the "Desktop" sample application script file to start the "Desktop" sample application library directory "Desktop" sample application components source directory "Pie" sample application directory binaries directory batch file to start the "Pie" sample application script file to start the "Pie" sample application library directory "Pie" sample application components source directory
VAJava V3x UlcR40_VAJ3x.zip	ULC features for the IBM VisualAge for Java IDE. directory for IBM VisualAge for Java support features for VAJ3.02 and VAJ 3.5.x IDE (incl. Composition Editor)

Trademarks

ENVY is a registered trademark of Object Technology International Inc. (OTI).
Internet Explorer is a trademark of Microsoft Corporation.
Netscape is a trademark of Netscape Communications Corporation.
Java and JavaBeans are trademarks of Sun Microsystems, Inc.
VisualAge is a trademark of IBM Corporation.
OTI is a wholly owned subsidiary of IBM Canada, Ltd.
RevaSoft AG is based in Richterswil, Switzerland.

Other product and company names herein may be trademarks of their respective owners.