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.
DataBlade® API Programmer's GuideThe Informix® DataBlade® API Programmer's Guide describes information about the DataBlade® API, the C-language application programming interface (API) provided with HCL Informix®.
Database access
XA-compliant external data sources
Overview of integrating XA-compliant data sources in transactionsThe transaction manager, which is an integral part of the database server, not a separate module, can invoke support routines for each XA-compliant, external data source that participates in a distributed transaction at a particular transactional event, such as prepare, commit, or rollback. This interaction conforms to X/Open XA interface standards.
XA-compliant data sources and data source typesAn XA-compliant data source type is a type of data source that is capable of supporting XA protocol requirements for a resource manager that is participating in a transaction.

XA-compliant data sources and data source types

An XA-compliant data source type is a type of data source that is capable of supporting XA protocol requirements for a resource manager that is participating in a transaction.

A data source is an instance of a data source type. An XA-compliant data source must be created in each database in which you want it, and the data source must be registered into the transaction manager when it participates in the transaction.

The transaction manager maintains a list of XA data sources participating in each transaction. Each XA data source participating in each transaction must dynamically register itself with the transaction manager by calling the mi_xa_register_xadatasource() or ax_reg() function at least once per transaction. If, for some reason, the XA data source does not participate in the two-phase commit protocol, it can be unregistered by calling the mi_xa_unregister_xadatasource() or ax_unreg() function.

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.