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™.
HCL OneDB™ extensions and DataBlade® modulesThese topics describe how to use built-in database extensions and separately installed DataBlade® modules.
Database Extensions User's GuideThe HCL OneDB™ Database Extensions User's Guide explains how to use the database extensions that come with HCL OneDB™: Large Object Locator, MQ messaging, binary data types, basic text search, node data type, HCL OneDB™ web feature service for Geospatial Data, and SQL packages.
MQ Messaging (WMQ) messaging products provide an infrastructure for distributed, asynchronous communication of data in a distributed, heterogeneous environment. The WMQ message queue allows you to easily exchange information across platforms.
MQ messaging functionsMQ messaging functions to enable applications to exchange data directly between the application and WebSphere® MQ.

MQ messaging functions

MQ messaging functions to enable applications to exchange data directly between the application and WebSphere® MQ.

All MQ messaging functions are created with a stack size of 64K. These MQ messaging functions can be executed within SQL statements and should have an explicit or implicit transactional context.

All MQ messaging functions or MQ messaging-based VTI tables can be invoked only on local (sub-ordinator) servers. Using MQ messaging functions or MQ messaging-based VTI tables on a remote server will return an error. MQ messaging functions cannot be used when HCL OneDB™is participating as a resource manager in an externally-managed global XA transaction.

MQ messaging functions use the "informix".mqi* service and policy tables to provide default values if the optional policy and service parameters are not specified.