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™.
Prepare for Java™ supportYou must install and configure software before you can write user-defined routines (UDRs) in Java™ code.
Configure Java™ support
Create an sbspaceThe database server stores Java™ JAR files as smart large objects in the system default sbspace. If you do not already have a default sbspace, you must create one.

Create an sbspace

The database server stores Java™ JAR files as smart large objects in the system default sbspace. If you do not already have a default sbspace, you must create one.

For example, the following command creates an sbspace called mysbspace:

onspaces -c -S mysbspace -g 5 -p /dev/raw_dev1 -o 500 -s 20000 -m /dev/raw_dev2 500

After you create the sbspace, set the SBSPACENAME configuration parameter in the onconfig file to the name that you gave to the sbspace (mysbspace in the preceding example).

JAR files coexist in the system default sbspace with other smart large objects that you store in that space. When you choose the size for your default sbspace, you need to consider how much space those objects require, as well as the number and size of the JAR files that you plan to install.