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.
Java™ programming task overview

Java programming task overview

About this task

After you generate code with BladeSmith, complete these general tasks to finish your DataBlade® module code:

Procedure

Add code to the ProjectUDRs.java source code file to enable your routines to function as you intend.
See Edit methods for instructions.
Compile your source code files by using the generated makefile.
See Compiling DataBlade module Java code for instructions.
Debug your source code files by using the Java log file.
See Debug and test DataBlade Modules written in Java.
Execute functional tests.
See Perform functional tests.

Results

For a list of the Java packages, interfaces, classes, and methods you can use in Java projects, see HCL® J/Foundation Developer's Guide.

To avoid merging conflicts when you regenerate your code, add code only in areas marked by TO DO: comments or after the generated code. If you do modify code outside the designated areas, after you regenerate you might have two copies of the routine: the one you modified and the one BladeSmith generated. Although your changes remain, you must resolve conflicts in the two pieces of code.