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.
Establish content
Files and directories to be installed or deleted
Local paths for files for multiple operating systemsIf you have files that are operating-system-specific, put them in a directory structure that is the same except for one directory, which is named for the operating system. When you add the file to your BladePack project, replace the directory named for the operating system with %OS%.

Local paths for files for multiple operating systems

If you have files that are operating-system-specific, put them in a directory structure that is the same except for one directory, which is named for the operating system. When you add the file to your BladePack project, replace the directory named for the operating system with %OS%.

For example, if you compile your C or C++ DataBlade® module on Sun Solaris and Windows™, you have two project.bld files, one in each of these directories:

project/src/c/Solaris-sparc
project\src\c\WinNT-i386

Add the project\src\c\WinNT-i386\project.bld file to the Files to Install folder and then replace WinNT-i386 with %OS%. When you build the BladePack project for Sun Solaris and Windows, BladePack adds the appropriate project.bld file to each project.

For a Java™ DataBlade module, you have only one version of the project.jar file, which is in the project/src/java directory.