Try OpenEdge Now
skip to main content
Java Open Clients
Configuring and Deploying Java Open Client Applications : Java Open Client Runtime package
 

Java Open Client Runtime package

If your application is a Java servlet or a Java application, use o4glrt.jar as the Open Client runtime package. This package supports the following protocols:
*AppServer or AppServerDC
*AppServerS or AppServerDCS
*HTTP
*HTTPS
These protocols are supported over the intranet and internet. The o4glrt.jar Open Client runtime package supports user-implemented authentication to a Web Server and Proxy server.
The Java Open Client runtime package o4glrt.jar supports most SSL-enabled Web servers. The individual Web server's SSL configuration and the digital certificate used to authenticate the identity of the Web server determines whether you can use this package.
This package supports user-implemented authentication to a Web server, data encryption, and Proxy server.
Note: You must have a Web server hosting the AppServer Internet Adapter (AIA) Java servlet to support the HTTP/S protocol. Also, for every Web server that hosts an AIA servlet and supports the HTTPS protocol, the client machine must have the root digital certificate of the Certificate Authority that issued the digital certificate for the Web server.
As you develop your HTTPS, AppServerS, and AppServerDCS applications, you should consider that the application deployer might require certain data encryption and digital signature algorithms when they configure their Web server's.
If you are using Progress Developer Studio for OpenEdge, you will also need to copy the following third-party Apache Tuscany jar files to the same directory where you copy the Java Open Client Runtime package you selected. These files reside in the specified OpenEdge installation directory, as shown:
OpenEdge-install-directory/java/ext/
     common-2.2.3.jar
ecore-2.2.3.jar
ecore-change-2.2.3.jar
ecore-xmi-2.2.3.jar
tuscany-sdo-api-r2.1-1.1.1.jar
tuscany-sdo-impl-1.1.1.jar
tuscany-sdo-lib-1.1.1.jar
tuscany-sdo-tools-1.1.1.jar
xsd-2.2.3.jar
The following table lists the security supported by various Open Client Runtime packages.
Table 1. Security supported by package
Package
Supported security
Basic
User-implemented authentication using a userid and password
SSL
*Authentication that includes:
*User-implemented authentication using a userid and password
*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
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
*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