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

SBSPACENAME configuration parameter

onconfig.std value: blank
takes effect: When shared memory is initialized

The SBSPACENAME configuration parameter specifies the name of the system default sbspace. You must provide an sbspace where the database server can store the Java™ JAR files.

This parameter is not exclusively for Java code. If your database tables include smart-large-object columns that do not explicitly specify a storage space, that data is stored in the sbspace that SBSPACENAME specifies.

Tip: When you use UDRs written in Java code, create separate sbspaces for storing your smart large objects.