Java Open Client Runtime package
- Last Updated: May 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
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:
- 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 TLS-enabled web servers. The TLS configuration for the
individual web server 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.
As you develop your HTTPS applications, you should consider that the application deployer might require certain data encryption and digital signature algorithms when they configure their web servers.
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:
|
The following table lists the security supported by various Open Client Runtime packages.
| Package | Supported security |
|---|---|
| HTTP |
To set HTTP connection properties on the Java Open Client (such as proxy host, port, and credentials), see Alphabetical list of properties. |
| HTTPS |
For more information about TLS support, see Supported protocols, cipher, and certificates for OpenEdge client and servers, Configure TLS server sessions, and Configure TLS client sessions. To set HTTPS and TLS connection properties on the Java Open Client (such as certificate store location, host verification, and SSL session reuse), see Alphabetical list of properties. |