Generic Java driver
The generic Java driver differs from existing system drivers. It requires user additions that provide a framework for Java code This is used to implement the functionality of a system driver.
This driver differs from the UPOC type driver. It is fully threaded, provides several features not possible in a UPOC driver, and places no restrictions on the use of Java threads in the implementation.
The Java driver also permits multiple instances to run in a single process.
When using the generic Java driver, you can send inbound messages to the system engine through Java code. You can also retrieve outbound messages from the system engine through Java code.
The generic Java driver runs independently from the engine. For example, the engine does not stall when the driver is running. Data is passed between the driver and engine asynchronously. The driver has access to store, retrieve, and remove messages from its own queue in the recovery database.
Server interface
The programmatic interface includes multiple Java methods, most of which are optional. These are configured in the ini file. These are described in JDDK overview.
Generic Java Driver type in NetConfig
PROTOCOL {
{ IS_TIMED_QUERY {} }
{ QUERY_INTERVAL {} }
{ TYPE java }
}
Selecting the java protocol and then clicking Properties opens the Java Driver Protocol Properties dialog box.
If Query Interval is disabled and is enabled. Clicking opens the Scheduling dialog box. For more information on advanced scheduling, see Network Configurator schedule configuration.
is selected, thenJava protocol configuration
For configuration details, see JDDK overview.