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

JVPLOGFILE configuration parameter

onconfig.std value: /usr/informix/jvp.log
range of values: Any valid complete file name
takes effect: When shared memory is initialized

The database server can generate Java™ trace outputs and stack dumps. The database server writes this output to the Java VP log file.

The JVPLOGFILE configuration parameter specifies the path to the Java VP log file. This parameter is optional.

To change the location of the log file, change the value of the JVPLOGFILE configuration parameter. For example, the following parameter value sets the log file to /u/sam/jvp.log:

JVPLOGFILE /u/sam/jvp.log

If you do not specify a value for this parameter, the default value is derived from the onconfig.std file. If the JVPLOGFILE parameter is not present in the onconfig file, the default file location is ./jvp.log, where ‘.’ is the current directory of the user who runs oninit.