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.
About MQ messagingYou can use either functions or tables to communicate between a database server application and the queue.
Prepare to use MQ messagingBefore you can use MQ messaging, you must install and configure (WMQ) and configure your database server for use with WMQ.
Prepare your database server for MQ messagingYou must prepare your HCL OneDB™ database for MQ messaging.

Prepare your database server for MQ messaging

You must prepare your HCL OneDB™ database for MQ messaging.

To prepare for MQ messaging, add user informix to the mqm group and restart the database server. Only members of the mqm group are authorized to access to WMQ queues. For more information, see the platform-specific documentation for WMQ.

The mq virtual processor is created automatically the first time you access an MQ messaging table or run an MQ messaging function.

The HCL OneDB database server has the following additional requirements:

Non-logged databases are not supported.
ANSI databases are not supported.
The Scheduler must be running.

If you attempt to run an MQ messaging function in an unlogged or ANSI database, a message that DataBlade registration failed is printed in the online message log. If the Scheduler is not running the first time that you access an MQ messaging table or run an MQ messaging function, a message that the table cannot be found or the routine cannot be resolved is returned.