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).
JVPJAVAHOME configuration parameter

JVPJAVAHOME configuration parameter

This configuration parameter is deprecated and not required in HCL OneDB™. This configuration parameter will be removed in a future release.

onconfig.std value: $INFORMIXDIR/extend/krakatoa/jre/
takes effect: When shared memory is initialized

The JVPJAVAHOME configuration parameter specifies the directory where the Java™ runtime environment for the database server is installed. By default, the database server includes a tested version of the runtime environment in $INFORMIXDIR/extend/krakatoa/jre/. To modify the default location in the configuration file, replace $INFORMIXDIR/extend/krakatoa/jre/ with the path name setting of $INFORMIXDIR, followed by /extend/krakatoa/jre/.

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