Home
Extending Informix®
Beyond standard relational database objects, HCL Informix® can be extended to handle specialized data types, access methods, routines, and other objects. Informix includes many built-in extensions that are fully integrated in the database server. Informix 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 Informix.
Informix® extensions and DataBlade® modules
These topics describe how to use built-in database extensions and separately installed DataBlade® modules.
Database Extensions User's Guide
The Informix® Database Extensions User's Guide explains how to use the database extensions that come with HCL Informix: Large Object Locator, MQ messaging, binary data types, basic text search, node data type, and SQL packages.
MQ Messaging
WebSphere® MQ (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 functions
MQ messaging functions to enable applications to exchange data directly between the application and WebSphere® MQ.

Extending Informix®
Beyond standard relational database objects, HCL Informix® can be extended to handle specialized data types, access methods, routines, and other objects. Informix includes many built-in extensions that are fully integrated in the database server. Informix 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 Informix.
- Informix® extensions and DataBlade® modules
  These topics describe how to use built-in database extensions and separately installed DataBlade® modules.
  - Database Extensions User's Guide
    The Informix® Database Extensions User's Guide explains how to use the database extensions that come with HCL Informix: Large Object Locator, MQ messaging, binary data types, basic text search, node data type, and SQL packages.
    - Large object management
      The Large Object Locator extension enables you to create a single consistent interface to large objects. It extends the concept of large objects to include data stored outside the database.
    - MQ Messaging
      WebSphere® MQ (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 messaging
        You can use either functions or tables to communicate between a database server application and the WebSphere® MQ queue.
      - MQ messaging tables
        You use Virtual-Table Interface (VTI) access method to access WMQ queues using table semantics.
      - MQ messaging functions
        MQ messaging functions to enable applications to exchange data directly between the application and WebSphere® MQ.
        Service and policy tables
        MQ messaging functions use three service and policy tables.
        MQCreateVtiRead() function
        The MQCreateVtiRead() function creates a table and maps it to a queue managed by WMQ.
        MQCreateVtiReceive() function
        The MQCreateVtiReceive() function creates a table and maps it to a queue managed by WMQ.
        MQCreateVtiWrite() function
        The MQCreateVtiWrite() function creates a write-only VTI table and maps it to a queue that WebSphere® MQ manages.
        MQHasMessage() function
        The MQHasMessage() function checks if a message is available from the WMQ.
        MQInquire() function
        The MQInquire() function, which is the same as the MQINQ() function of WebSphere® MQ, queries attributes of the queue. The MQInquire() is the interface between your SQL and WebSphere MQ.
        MQPublish() function
        The MQPublish() function publishes a message on one or more topics to a queue managed by WMQ.
        MQPublishClob() function
        The MQPublishClob() function publishes CLOB data on one or more topics to a queue managed by WMQ.
        MQRead() function
        The MQRead() function returns a message from WMQ without removing the message from the queue.
        MQReadClob() function
        The MQReadClob() function returns a message as a CLOB from WMQ without removing the message from the queue.
        MQReceive() function
        The MQReceive() function returns a message from the WMQ queue and removes the message from the queue.
        MQReceiveClob() function
        The MQReceiveClob() function retrieves a message as a CLOB from the WMQ queue and removes the message from the queue.
        MQSend() function
        The MQSend() function puts the message into the WMQ queue.
        MQSendClob() function
        The MQSendClob() function puts the CLOB data into the WMQ queue.
        MQSubscribe() function
        The MQSubscribe() function is used to register interest in WMQ messages published on one or more topics.
        MQTrace() function
        The MQTrace() procedure specifies the level of tracing and the location to which the trace file is written.
        MQUnsubscribe() function
        The MQUnsubscribe() function is used to unregister interest in WMQ messages published on one or more topics.
        MQVersion() function
        The MQVersion() function returns version information.
      - MQ messaging configuration parameters
        When you use MQ messaging over a network, you must set several database server configuration parameters,
      - MQ messaging error handling
        This topic describes MQ messaging error codes.
      - Sample MQ messaging code
        This topic contains sample SQL statements that you can run in the stores_demo database, using DB-Access.
    - Binary data types
      The binary18 and binaryvar data types allow you to store binary-encoded strings, which can be indexed for quick retrieval.
    - Basic Text Search
      You can perform basic text searching for words and phrases in a document repository stored in a column of a table.
    - Hierarchical data type
      The node data type helps to resolve a difficult relational database problem–transitive closure.
    - SQL Packages Extension
      The SQL packages extension provides SPL routines that you can use in an application that is compatible with database servers other than Informix®.
    - Regex pattern matching
      Regular expressions combine literal characters and metacharaters to define the search and replace criteria. You run the functions from the Informix® Regex extension to find matches to strings, replace strings, and split strings into substrings.
  - Performing XML Publishing
    The Informix® XML User's Guide includes information about using built-in functions for XML publishing with Informix.
  - Spatiotemporal Search for Moving Objects User's Guide
    The describes how to program applications to search data from moving objects in HCL Informix® databases using the spatiotemporal search extension.
  - TimeSeries Data User's Guide
    The Informix® TimeSeries Data User's Guide contains information to assist you in using the TimeSeries extension with HCL Informix.
  - Web DataBlade Module
    Use the Web DataBlade® module to create web applications that incorporate data that is retrieved dynamically from the HCL Informix® database.
- Creating extensions
  You 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 Informix® databases.

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 Informix®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.