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 configuration parametersWhen you use MQ messaging over a network, you must set several database server configuration parameters,
MQSERVER configuration parameterUse the MQSERVER configuration parameter to define a channel, specify the location of the , and specify the communication method to be used.

MQSERVER configuration parameter

Use the MQSERVER configuration parameter to define a channel, specify the location of the , and specify the communication method to be used.

onconfig.std value: none
range of values: ChannelName/TransportType/ConnectionName
takes effect: When the database server is stopped and restarted

Usage

You must set this configuration parameter when you use MQ messaging over a network. The configuration parameter contains the same information as the same as the WMQ MQSERVER environment variable.

The connection name must be a fully qualified network name.

The connection and channel names cannot include contain the forward slash (�?�) character, because it is used to separate the channel name, transport type, and connection name.