Welcome
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 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 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.
Developers Kit
The Developers Kit (DBDK) guides contain information about the tools you can use to develop and package modules, which extend the functionality of HCL Informix® databases.
Developers Kit User's Guide
The HCL Informix® Developers Kit User's Guide describes how to use tools to develop and package modules.
Create objects by using BladeSmith
Use BladeSmith to create modules.
Create a project
New object prefix
Use a three-character object prefix in the name of the new objects you create in BladeSmith to ensure that your objects have unique names in the database when the module is registered.

HCL Informix® V15.0.0 documentation
Welcome to the documentation for HCL Informix® 15.0.0 and related client tools and products.
Product overview
HCL Informix® is a fast and scalable database server that manages traditional relational, object-relational, and dimensional databases. Its small footprint and self-managing capabilities are suited to embedded data-management solutions.
Installing
These topics describe how to install HCL Informix® database servers, client products, and modules.
Administering
In addition to administering the database server, you can tune performance, replicate data, and archive data.
Migrating and upgrading
You can upgrade to the 15.0.0 release of HCL Informix® or migrate from other database servers to Informix. Upgrading is an in-place migration method that uses your existing hardware and operating system software. Some changes to the Informix database server can affect upgrading from a previous release.
Client APIs and tools
You can use the HCL Informix® implementation of client APIs to develop applications for Informix database servers.
Embedding Informix®
When you embed HCL Informix®, you can use enterprise-class high-availability and high performance with embeddability features such as easy programmability, a small disk and memory footprint, and silent deployment.
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 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 modules
  These topics describe how to use built-in database extensions and separately installed modules.
- 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.
  - Programmer's Guide
    The HCL® Informix® DataBlade® API Programmer's Guide describes information about the , the C-language application programming interface (API) provided with HCL Informix.
  - Function Reference
    The IBM® Informix® DataBlade® API Function Reference describes the functions and the subset of functions that the supports.
  - Developers Kit
    The Developers Kit (DBDK) guides contain information about the tools you can use to develop and package modules, which extend the functionality of HCL Informix® databases.
    - Module Development Overview
      The HCL Informix® module overview serves as an overview of the HCL Informix module development process.
    - Developers Kit User's Guide
      The HCL Informix® Developers Kit User's Guide describes how to use tools to develop and package modules.
      - Getting started with module development
        This section provides an overview of module development and describes the resources and tools the HCL Informix® database server provides to facilitate development.
      - Design modules
        This section describes the module SQL design issues.
      - Programming guidelines
        Use this section to help you when you write the design specification for your module.
      - Create objects by using BladeSmith
        Use BladeSmith to create modules.
        Prerequisite tasks
        Before you begin using BladeSmith, design your module.
        Task overview
        BladeSmith project window
        The BladeSmith project window is divided into two panes. One pane, called the project view, contains a tree representing the hierarchy of the objects in the project, with folders for files, imported objects, and user-defined objects. The other pane, called the item view, contains information about the object selected in the project view.
        Create a project
        module project name
        The project name is combined with the version numbers as a unique identifier to use to register the module in the database server and to create the installation directory.
        New object prefix
        Use a three-character object prefix in the name of the new objects you create in BladeSmith to ensure that your objects have unique names in the database when the module is registered.
        Server compatibility
        When you create a project in BladeSmith, you must specify the version of the database server with which you want your module to be compatible.
        Description locale
        Project version numbers
        The optional version information can be one to four sets of numbers or letters separated by periods: for example, 1.2.3.4. The numbers correspond to the categories major, minor, revision, and release.
        Vendor information
        The vendor ID must be unique. All modules with the same vendor ID display the same information when the user requests it from . If you want to display different contact information for different modules, you must use different vendor IDs.
        Importing interfaces from another module
        A module can access data types and routines provided by another module if you import an interface from that module.
        Create module objects
        BladeSmith uses wizards to create and edit objects.
        Perform functional test data
        You can perform functional tests on your module routines by using the functional tests generated by BladeSmith. You must enter test data for functional tests in BladeSmith. You run functional tests on UNIX™, or you run them on Windows™ by using a toolkit that is compatible with UNIX, such as MKS Toolkit.
        Add SQL files
        Use BladeSmith to add custom SQL commands to the scripts that describe a module and its objects. You can include SQL commands to create tables, indexes, or SPL procedures your module requires.
        Add client files
        Client files you include in your BladeSmith project are downloaded to client workstations after a module is installed on a database server.
        Generate files
        When you generate files, BladeSmith creates files that describe the objects you defined in your project.
      - Programming module routines in C
        This section contains information to help you edit and compile C language source code generated by .
      - Create ActiveX value objects
        This section describes how to use the to create ActiveX value objects. This section describes the use of C++ to implement opaque type support routines.
      - The ActiveX value objects
        This section provides information for client application developers who are using ActiveX value objects.
      - Programming modules in Java™
        This section contains information to help you edit and compile Java™ language source code generated by BladeSmith.
      - Debugging and testing modules on UNIX™
        This section describes how to debug and perform functional tests for modules written in C for Informix® on UNIX™.
      - Debugging and testing modules on Windows™
        This section describes how to debug and perform functional tests for modules written in C and C++ for Informix® on Windows™.
      - BladePack
        BladePack creates installation packages for modules and other software products.
      - Appendixes
        This section contains additional reference information.
    - DBDK InfoShelf
      The Developers Kit InfoShelf is designed to help you work with BladeSmith.
  - J/Foundation Developer's Guide
    The HCL® J/Foundation Developer's Guide describes how to write user-defined routines (UDRs) in the Java™ programming language for Informix®.
  - R-Tree Index User's Guide
    The HCL® Informix® R-Tree Index User's Guide describes the HCL Informix R-tree secondary access method and how to access and use its components.
  - User-Defined Routines and Data Types Developer's Guide
    The HCL® Informix® User-Defined Routines and Data Types Developer's Guide describes how to define new data types and enable user-defined routines (UDRs) to extend HCL Informix.
  - Virtual-Table Interface Guide
    The IBM® Informix® Virtual-Table Interface Programmer's Guide explains how to create a primary access method with the Virtual-Table Interface (VTI) so that users have a single SQL interface to HCL Informix tables and to data that does not conform to the storage scheme of HCL Informix.
  - Virtual-Index Interface Guide
    The IBM® 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 module.
Data warehousing
In addition to designing and implementing Informix® dimensional databases, you can use tools to create data warehouse applications and optimize your data warehouse queries.
Designing databases
The first step in creating a relational database is to construct a data model, which is a precise, complete definition of the data you want to store. After you prepare your data model, you must implement it as a database and tables. To implement your data model, you first select a data type for each column and then you create a database and tables and populate the tables with data. You can also implement fragmentation strategies and control access to your data.
JSON compatibility
You can use the popular JSON-oriented query language created by MongoDB to interact with data stored in HCL Informix®.
Security
You can secure your Informix® database server and the data that is stored in your Informix databases. You can encrypt data, secure connections, control user privileges and access, and audit data security.
SQL programming
You can use the HCL Informix® implementation of the SQL language to develop applications for Informix database servers.
Troubleshooting HCL Informix®
Several troubleshooting techniques, tools, and resources are available for resolving problems that you encounter in your HCL Informix® database server environment.

New object prefix

Use a three-character object prefix in the name of the new objects you create in BladeSmith to ensure that your objects have unique names in the database when the module is registered.

Use your module new object prefix to begin the names of the following objects:

New data types
User-defined routines
Aggregates
Access methods
Executable utilities and tools provided with the module
Tables, views, and other custom SQL objects included with your module
User-defined virtual processors
Trace classes
Named memory

You do not have to use the module new object prefix for the following objects:

Names of routines that operate on data types unique to your module, including routines that you overload to take a new data type
Names of routines that operate on data types provided by other modules that you develop and maintain
Names of routines in support libraries linked to the shared object file