Progress
Open Client
Developer’s Guide


Selecting an Open Client Runtime Package

The Open Client Runtime is part of the client installation that you must supply with your application. Progress packages and distributes the Open Client Runtime in a number of file formats that contain different network protocol support combinations. This distribution method reduces the overhead and complexity for both you the developer and the Open Client deployer.

Based on the run-time configuration you want to support for your Open Client application, you can select one of the following Open Client Runtime distribution packages:

As you develop your HTTP/S applications, you should consider that the application deployer might require certain data encryption and digital signature algorithms when they configure their Web server’s SSL support. These requirements might exceed the capabilities of the HTTPS Lite package you select. Deployers might also require the use of SSL version 2 or TLS protocols instead of the standard SSL version 3. If any of these requirements exists, you must use the HTTPS Standard packages. For Java applets, Progress software recommends using the HTTP Lite package because of its download size.

For more information about selecting a package, see Table 2–1. For more information about the security supported, see Table 2–2.

The following table lists the types of supported applications, the supported protocols, and the Open Client Runtime packages you would use depending on the run-time configuration of your application and the protocols you want to support.

Table 2–1: Open Client Package Options
If your application run-time configuration is...
And the supported protocol is...
The Open Client Runtime package you use is...
An ActiveX Automation controller, such as Visual Basic
AppServer
or
AppServerDC
Basic (o4glrt.zip)1
A Java application or servlet
HTTP
HTTP (o4glrth.zip)
 
HTTPS
HTTPS Lite (o4glrthsl.zip)
 
HTTPS
HTTPS Standard (o4glrths.zip)
A Java applet running in the Netscape browser
AppServer
or
AppServerDC
Basic (o4glrt.jar)1
 
HTTP
HTTP (o4glrth.jar)
 
HTTPS
HTTPS Lite (o4glrthsl.jar)
 
HTTPS
HTTPS Standard (o4glrths.jar)
Java applet running in the Internet Explorer browser
AppServer
or
AppServerDC
Basic (o4glrt.cab)1
 
HTTP
HTTP (o4glrth.cab)
 
HTTPS
HTTPS Lite (o4glrthsl.cab)
 
HTTPS
HTTPS Standard (o4glrths.cab)
  1. Use only for Intranet network configurations
   

All packages support the AppServer protocol and the HTTPS packages support HTTP

For example, based on the options described in Table 2–1, if you have:

Table 2–2 lists the security supported by each Open Client Runtime package.

Table 2–2: Security Supported By Package  
For This Package...
The Following Security is Supported...
AppServer and AppServerDC
User-implemented authentication using a userid and password
HTTP
  • Authentication that includes:
    • User-implemented authentication using a userid and password
    • Basic authentication to the AIA's Web server
    • Basic Proxy server authentication
  • Proxy servers
HTTPS Lite
(limited security)
  • Authentication that includes:
    • User-implemented authentication using a userid and password
    • Basic Proxy server authentication
    • HTTP Basic authentication to the AIA's Web server
    • HTTPS using SSL V3, RSA with MD5 digital signatures, and RSA Key Exchange
  • Data Encryption using RC4-128 bit key and RC4-40 bit key
  • Proxy servers
HTTPS Standard
(full security)
  • Authentication that includes:
    • User-implemented authentication using a userid and password
    • Basic Proxy server authentication
    • HTTP basic authentication to the AIA's Web server
    • HTTPS using SSL V2, SSL V3, and TLS V1, Digital Signatures: RSA w. MD5, RSA w. SHA1, DSA 2. SHA1, and Key Exchange: RSA, Diffie-Hellman.
  • Data Encryption using RC4-128 bit key, RC4-40 bit key, DES-56 bit key, DES-40 bit key, Triple-DES-168 bit key, RC2-40 bit key
  • Proxy servers


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095