Java Environment Settings

Depending on the development tools being used, the following archive files must be either added to the class path or added to the project library in order to compile the program. It must be added to the class path in order to run the program.  Be sure to update the build XML and class paths to reflect the correct file name.  Pi Soft Java archive files are named with the following convention:  Archive name - version number. jar.

The provided archive file, TEAdmin.jar, contains all the classes of the TEAgent package and the TEAdmin package.

The Pi SoftOnlineJCE.jar and the Pi SoftOfflineJCE.jar contain all the classes required to use the Java Cryptographic Extension as the cryptographic provider and as desired key store.

The cloudCrypt.jar contains all the classes required to connect to the Amazon Web Service S3 and the Dropbox storage providers.  Use of it also requires the TEAdmin.jar and the Pi SoftOnlineJCE.jar.  (The cloudCrypt.jar also contains a command line utility for simple file transfer and encryption.)

Sun Microsystem's row set package is needed to work with the TEAgentResultSet class of the Java TEAgent package. Another database related row set package, such as the one included in the Oracle JDBC driver, may be substituted if necessary.  Standard Sun packages and JDBC drivers can usually be downloaded from the appropriate vendor's web sites.

At a minimum, an Eclipse Temurin 8 JDK (baseline jdk8u492-b09) with JCE and JSSE is needed to compile the program, and the matching runtime is needed to run the program. The runtime must support TLS 1.3.

Current Temurin JDKs ship with the unlimited-strength cryptographic policy enabled by default; no separate JCE policy files are required (including for ECC).

If Code Signing is used, the signer's CA must be imported into the key services.  See Java Code Signing for more details.