If your application is a Java application, use o4glrt.jar as the Open Client runtime package. The Java Open Client connects to a Progress Application Server for OpenEdge (PAS for OpenEdge) instance, optionally through a proxy server, using one of the following protocols:

  • HTTP
  • HTTPS (recommended for production)
Note: In OpenEdge 12.x, Java Open Client supports backward compatibility for one full major version. As a result, connections to OpenEdge 11.7 deployments that use classic AppServer or AIA can still be used for compatibility purposes. However, PAS for OpenEdge is the recommended target platform.

When you use HTTPS, o4glrt.jar connects to a TLS-enabled PAS for OpenEdge instance for data encryption in transit. The TLS configuration of the target PAS for OpenEdge instance — including its supported protocol versions, cipher suites, and the digital certificate it presents — determines whether the client can establish a connection. Confirm with the application deployer which TLS versions, cipher suites, and certificate algorithms the target PAS for OpenEdge instance requires.

Any Java application that embeds the Java Open Client must include the complete set of supporting .jar files. If any are missing, the runtime may fail in ways that are difficult to diagnose. Copy the following files from the specified OpenEdge installation directories to the same directory as o4glrt.jar:

OpenEdge-install-directory/java/
      messages.jar
      ehnlog.jar 
OpenEdge-install-directory/java/oe
      oeauth-<version>.jar 
OpenEdge-install-directory/java/ext/
      common-<version>.jar
      commons-codec-<version>.jar
      commons-logging-<version>.jar
      ecore-<version>.jar
      ecore-change-<version>.jar
      ecore-xmi-<version>.jar
      httpclient-<version>.jar
      httpasyncclient-<version>.jar  
      httpcore-<version>.jar
      httpcore-nio-<version>.jar
      tuscany-sdo-api-r2.1-<version>.jar
      tuscany-sdo-impl-<version>.jar
      tuscany-sdo-lib-<version>.jar
      tuscany-sdo-tools-<version>.jar
      xsd-<version>.jar

Supported security

The Java Open Client supports the following authentication mechanisms over both HTTP and HTTPS:

Authentication to PAS for OpenEdge

  • User-implemented authentication using a user ID and password passed to the PAS for OpenEdge connect procedure
  • Basic authentication
  • Client-principal-based authentication. See Authenticate and authorize a user ID in Learn about Security and Auditing.

Authentication to an intermediate proxy server

  • Basic authentication
Transport security (HTTPS only)

To set HTTP, HTTPS, and TLS connection properties on the Java Open Client (such as proxy host, port, credentials, certificate store location, host verification, and SSL session reuse), see Alphabetical list of properties.