Home
Extending HCL OneDB™Beyond standard relational database objects, HCL OneDB™ can be extended to handle specialized data types, access methods, routines, and other objects. HCL OneDB™ includes many built-in extensions that are fully integrated in the database server. HCL OneDB™ also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for HCL OneDB™.
Creating extensionsYou can create user-defined data types, routines, access methods, and other database objects to suit your needs. You can use application programming interfaces to write user-defined routines and applications that access data in HCL OneDB™ databases.
J/Foundation Developer's GuideThe HCL® J/Foundation Developer's Guide describes how to write user-defined routines (UDRs) in the Java™ programming language for HCL OneDB™.
Configuration parametersThis section documents the configuration parameters that you need to set to use UDRs written in Java™ code. Set these parameters in the database server configuration file (the onconfig file).
JVPHOME configuration parameter

JVPHOME configuration parameter

This configuration parameter has been deprecated and not required in HCL OneDB™ Version 11.70. This configuration parameter will be removed in a future release.

onconfig.std value: /usr/informix/extend/krakatoa
takes effect: When shared memory is initialized

The JVPHOME configuration parameter specifies the directory where the classes of the HCL OneDB JDBC Driver are installed. To modify the default setting in the configuration file, replace /usr/informix with the path name of your $INFORMIXDIR.

The JVPHOME value, JVPHOME_path, is used in several configuration parameters. If the JVPHOME location changes, you must change the configuration settings of all parameters that use the JVPHOME value.

This parameter is required if the number of JVPs (set in VPCLASS JVP) is greater than 0.