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.
DataBlade® Developers KitThe DataBlade® Developers Kit (DBDK) guides contain information about the tools you can use to develop and package DataBlade® modules, which extend the functionality of HCL OneDB™ databases.
DataBlade® Developers Kit User's GuideThe HCL OneDB™ DataBlade® Developers Kit Users Guide describes how to use OneDB® DataBlade® Developers Kit (DBDK) tools to develop and package DataBlade® modules.
Programming DataBlade® modules in Java™This section contains information to help you edit and compile Java™ language source code generated by BladeSmith.
The generated code
Logging and error handlingBladeSmith adds logging and error handling code throughout the generated source code.

Logging and error handling

BladeSmith adds logging and error handling code throughout the generated source code.

You can add additional logging calls by using the Log() method from the IfmxLog class. The Log() method calls the standard Java™ I/O package methods system.out.println() and system.err.println(). For more information about these methods, see the HCL OneDB™ JDBC Driver Programmer's Guide.

If the Java value object is used on the client, the Log() method writes the logging messages to the standard output. If the Java value object is used on the server, the Log() method writes the logging messages to the Java log file.

The Java log file is distinct from the main database server log file, online.log. The Java log file contains all logging and tracing messages specific to Java methods.

The Java log file is specified by the JVPLOGFILE configuration parameter, which is set in the onconfig file. By default, the Java log file is at the following location:

/usr/informix/jvp.log

You can change the location of the Java log file by setting the JVPLOGFILE configuration parameter; see HCL® J/Foundation Developer's Guide.