Destination IBM Informix #
replicant-cli will be referred to as the
$REPLICANT_HOME directory in the proceeding steps.
I. Set up Connection Configuration #
$REPLICANT_HOME, navigate to the sample connection configuration file:
If you store your connection credentials in AWS Secrets Manager, you can tell Replicant to retrieve them. For more information, see Retrieve credentials from AWS Secrets Manager.
Otherwise, you can put your credentials like usernames and passwords in plain form like the sample below:
type: INFORMIX host: localhost #Replace localhost with your Informix server's hostname port: 9088 # In case of SSL connection use SSL port server: 'informix' database: 'tpch' # Name of the catalog from which the tables are to be replicated username: 'informix' #Replace informix with the user that connects to your Informix server password: 'in4mix' #Replace in4mix with your user's password informix-user-password: 'in4mix' #Password for user "informix" lock-wait-duration: -1 # -1 will wait until lock is released, to use a timeout set a positive number of seconds #ssl: # trust-store: # path: "/home/informix/ssl/truststore.jks" #Path to the JKS truststore containing the trust certificate of the Informix server # password: "in4mix" #The truststore password max-connections: 15 #Maximum number of connections Replicant can open in Informix
You have to connect to the syscdcv1 catalogue on the server as the user
informixto be able to use Change Data Capture. The
informix-user-passwordparameter of the config file above should have the password of user
informix. For more information, see Preparing to use the Change Data Capture API on IBM Informix Documentation.
II. Setup Applier Configuration #
$REPLICANT_HOME, navigate to the applier configuration file:
Make the necessary changes as follows:
snapshot: threads: 16 #use-raw-tables: false #batch-size-rows: 5_000 #txn-size-rows: 1_000 #sbspace: 'specific_sbspace' #dbspace: 'specific_dbspace'
use-raw-tablesparameter tells replicant the type of Informix tables to use for the destination. Setting it to
truetells Replicant to perform the following to the destination tables:
- Remove constraints like primary-key constraints, unique constraints, and referential constraints.
- Change the destination tables to type RAW (non-logging). This improves bulk load performance. Once loading is complete, Replicant converts the tables back to STANDARD type and reinforces the constraints.
You can also specify dbspace and sbspace for the destination by using the
If you want to operate in realtime mode, you can make use of the following parameters:
realtime: threads: 16 #txn-size-rows: 10_000 #batch-size-rows: 1000 # Transactional mode config # realtime: # threads: 1 # batch-size-rows: 1000 # replay-consistency: GLOBAL # txn-group-count: 100 # _oper-queue-size-rows: 20000 # skip-upto-cursors: #last failed cursor
For a detailed explanation of configuration parameters in the applier file, read Applier Reference.