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®.
Creating extensionsYou 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.
Virtual-Index Interface GuideThe Informix® Virtual-Index Interface Programmer's Guide explains how to create a secondary access method with the Virtual-Index Interface (VII) to extend the built-in indexing schemes of HCL Informix® typically with a DataBlade® module.
XA-compliant external data sourcesThe HCL Informix® Transaction Manager recognizes XA-compliant external data sources, which can participate in two-phase commit transactions.
Create a virtual-index interface for XA data sourcesYou can create a virtual-index interface to provide data access mechanisms for external data from XA data sources.

Create a virtual-index interface for XA data sources

You can create a virtual-index interface to provide data access mechanisms for external data from XA data sources.

The interaction between the database server and external data sources is through a set of purpose routines, such as xa_open(), xa_start(), xa_prepare(), xa_rollback(), xa_commit(), xa_recover(), xa_complete(), xa_forget(), xa_close(), and xa_end() For more information about these purpose functions, see the Informix® DataBlade® API Programmer's Guide.

You can create and drop XA-compliant data source types and instances of XA-compliant data sources. After you create an external XA-compliant data source, transactions can register and unregister the data source using the mi_xa_register_xadatasource() or ax_reg() and mi_xa_unregister_xadatasource() or ax_unreg() functions. For information about creating and dropping XA-compliant data source types and instances of XA-compliant data sources and information about the functions that transactions use to register and unregister the data source, see the Informix DataBlade API Programmer's Guide and the Informix DataBlade API Function Reference.

The MQ extension is an example of a set of user-defined routines that provide data access mechanisms for external data from XA data sources and provides XA-support functions to provide transactional support for the interaction between the database server and WebSphere® MQ. For more information, see the Informix Database Extensions User's Guide.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.