Installation Steps
GlueSync SQL to NoSQL for DB2 LUW
Prerequisites
In order to have GlueSync working on your DB2 LUW instance you will need to have:
-
valid user credentials with permissions of reading, writing to the target tables and respective database
Basic configuration example
This module can be customized by using a configuration file, in JSON format.
The file name to use must be specified as parameter when launching the app, with the -f
or --file
tokens.
The file should be composed by union of common configuration file (see here Installation Steps) and source/destination specific configuration:
{
...
"sourcePort": "50000",
...
"sourceChangeRetention": 5
}
You can also specify few other options that applies to this configuration, like:
-
sourceChangeRetention (optional): defaults to
5
. Number of retention days preserved into the GlueSync GDCaction_logs
table inside your DB2 database;
Got a clustered index in a table?
If you’ve got a clustered index configuration on one of your DB2 tables you can specificy which keys GlueSync should use in order to compose your unique row identifier instead of looking for a single Primary Key.
Here following the configuration snippet you can use and customize in order to sync your table with a clustered index config:
{
...
"db2": {
"tableKeys": {
"articles": ["id1", "id2"],
"customers": ["customer_name", "customer_surname", "customer_age", "customer_id"]
}
},
...
}
-
tableKeys: is the object that represents the key-value pair list of tables and its columns that are composing your clustered index;
Looking for data modelling features or other options?
For more detailed configurations options, including the ability to perform data modelling, please have a look at the dedicated Data modelling section when sourcing from a RDBMS.