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.
Create DataBlade® objects by using BladeSmithUse BladeSmith to create DataBlade® modules.
Generate filesWhen you generate files, BladeSmith creates files that describe the objects you defined in your project.
Generate installation package filesTo generate only the installation packaging files that BladePack uses to build installation packages, click the Packaging node in the Generate DataBlade dialog box, then click Generate Packaging.

Generate installation package files

To generate only the installation packaging files that BladePack uses to build installation packages, click the Packaging node in the Generate DataBlade dialog box, then click Generate Packaging.

The property associated with the Packaging node is Directory. The default directory is install. You can change the name of the directory where the installation files are saved, but the path must be relative to the project directory.

When you generate installation package files, BladeSmith creates a set of files that you use with BladePack to generate installation scripts for your DataBlade® module:


Files created	Description
project.bom	A bill of materials file.
project.cmp	A components file.
project.prd	A product file.
project.str	A string file.

Restriction: Do not edit the generated installation package files. Instead, use BladeSmith to regenerate the installation package files after you have added or removed DataBlade module objects in the project file.