JDDK
The Generic Java Driver provides a framework where Java code can be used to implement the functionality of a system driver.
The Generic Java Driver differs from the existing UPoC type driver. It is fully threaded, provides several features not possible in a UPoC driver. This places no restrictions on the use of Java threads in the implementation.
Users of the Generic Java Driver can write Java applications against an API that:
- Encapsulates the driver.
- Deploys the applications.
- Configures the system thread to make use of them.
The Java Protocol uses the Java Driver API to interact with the system engine by a set of message exchange patterns.
The Java Driver Development Kit (JDDK) provides the necessary components for system users to take advantage of the Generic Java Driver. These include:
- JavaDriver API:
This high-level API permits an application written in Java to exchange messages with the engine by a set of usage patterns. Javadoc is included as part of the documentation for the API.
Built on a lower-level (JNI) interface with the system engine that users can also access. The source code of the high-level JavaDriver API is included as an example of usage of the low-level API.
- Run time help tool:
This is in the system IDE. It generates configuration artifacts necessary for the underlying operation of the Generic Java Driver in the system engine.
This includes Netconfig, .pni, and .ini files.
- System sample site:
This includes various threads that show the message patterns usage of the JavaDriver API.
The sample site contains the artifacts that are already built and deployed, such as the Java JAR files, .pni, .ini, and NetConfig files.
The sample site resides under the system install location and can be installed as a real system site using the standard hcisiteinit command and copying the files from the sample folder.This topic, along with the companion video tutorials, describe how to run through the sample scenarios. It also explains how the sample Java applications interact with the engine using the API to achieve the usage patterns.
- Java sample applications:
These have source code contained in Eclipse projects. They are the Java samples that were built and deployed into the sample system site. These Eclipse projects reside under the system install locations alongside the sample site.
Both the system sample site and the Java Eclipse projects that are
described in this topic reside under the system install location. This is found in a
directory named JavaDriverSamples
.
To make the sample site operational, use the standard hcisiteinit
command. This creates an empty site and copies
the contents from the samplesite directory to that
empty site.