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.
BladePackBladePack creates installation packages for DataBlade® modules and other software products.
Packaging for InstallShield 3.1 installationsTo package your DataBlade® module, you add content to a BladePack project, assign components, customize the installation procedure, and build the package.
Build the installationWhen the content and organization of your installation package are complete, build and test it.

Build the installation

When the content and organization of your installation package are complete, build and test it.

To build, choose Build > Build Installation. The Build Installation wizard is launched and prompts you for the following information:

Installation type: interactive or file tree.
See Installation type for more information.
Platform for which to build the installation package.
Choose one from the list. Build a separate package for every platform.
Installation screen text.
See Installation screen display text for more information.
The target directory in which to build the installation.
This can be any directory. By default it is the project\install directory.
List of BladePack project.prd files to include in the installation package
You can bundle more than one project in a single installation.

Important: If the combined length of the path and file name of any file is longer than 255 characters, the build fails. This is due to a Windows limitation. To solve this problem, you can select a shorter staging directory.