Search docs.molo17.com

    Informix glyph screenshot Informix agent

    Target Informix

    Prerequisites

    To have Gluesync working with your Informix instance you will need to have:

    • Valid user credentials with permission to read, and write to the target tables.

    As for now there are some limitations on some data types. Please contact us for more details in case you are encountering issues on data types mapping.

    Setup via Web UI

    • Hostname / IP Address: Hostname or IP Address of your server;

    • Port: Optional, defaults to 9088;

    • Database name: Name of your database;

    • Username: Username with read/write access to the tables;

    • Password: Password belonging to the given username;

    • Max connections count: Maximum number of connections the pool can instantiate.

    Specific configuration

    This agent has no specific configuration properties.

    Updates with bulk operations during CDC

    When Use bulk operations during CDC (useBulkOperationsDuringCDC) is on for an entity, the agent does not apply an update as an UPDATE statement. It loads the change into a staging table, deletes the existing row from the target table and inserts the new version of it. With the option off, updates are applied as UPDATE statements.

    For the target table this has the following effects:

    • UPDATE triggers on the target table do not fire, while DELETE and INSERT triggers do;

    • Foreign keys that reference the table with ON DELETE CASCADE delete their child rows on every update. Any other foreign key makes the write fail while child rows exist;

    • Tools that read the logical log of the target, such as Informix Change Data Capture or Enterprise Replication, see a delete and an insert instead of an update;

    • The new row can get a new ROWID, and columns that Gluesync does not write, such as a column with a default value, are set again as for a new row.

    Setup via Rest APIs

    Here following an example of calling the Core Hub’s Rest API via curl to setup the connection for this Agent.

    Connect the agent

    curl --location --request PUT 'http://core-hub-ip-address/pipelines/{pipelineId}/agents/{agentId}/config/credentials' \
    --header 'Content-Type: application/json' \
    --header 'Authorization: ••••••' \
    --data '{
            "hostCredentials": {
            "connectionName": "myAgentNickName",
            "host": "host-address",
            "port": 9088,
            "databaseName": "db_name",
            "username": "",
            "password": "",
            "maxConnectionsCount": 100,
            "enableTls": true,
            "certificatePath": "/myPath/cert.pem"
          }
    }'