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.
Switch between server-based and client-based messagingIf you are set up to use both server-based and client-based MQ messaging on your database server, you can switch between the two methods of messaging. Server-based messaging is the default method.
Switching from server-based to client-based messagingYou can switch from server-based messaging, the default method for messaging, to client-based messaging.

Switching from server-based to client-based messaging

You can switch from server-based messaging, the default method for messaging, to client-based messaging.

Before you begin

Prerequisites:

When you switch to client-based messaging, the database server and (WMQ) must be installed on the same computer.
On Windows™, you must have the MKS Toolkit to run the chown command.

About this task

To switch to server-based messaging:

Procedure

Bring down the database server.
Run this command: cd $INFORMIXDIR/extend/mqblade.2.0
Run this command: rm idsmq.bld
Run either of the following commands:
- cp idsmqc.bld idsmq.bld
- ln –s idsmqc.bld idsmq.bld
Note that these commands differ slightly from the commands used to switch to server-based messaging.
Run this command: chown Informix:Informix idsmq.bld
Run this command: chmod –w idsmq.bld
Start the database server.