To configure and manage multiple Derby instances and to provide facilities to start, stop and restart Derby servers in networked mode a menu option called System Store is provided in the TDI Configuration Editor, as part of Solution Logging and Settings configuration of a project. Many of the configuration options listed take default values from the global.properties file, which was the configuration base for previous versions of TDI; now.
The System Store menu option also provides ways to configure the System Store to use other databases like IBM DB2 as the backend RDBMS. For more information, refer to "System Store settings" under The Configuration Editor -> Solution Logging and Settings in IBM TDI V7.1 Users Guide.
If the com.ibm.di.store.hostname property is set to localhost then remote connections are not allowed. If the com.ibm.di.store.hostname property is set to the IP address of the local computer running TDI, then remote clients can access this Derby instance by using the IP address. We can only start the network server for the local computer.
Property | Default value | Description |
---|---|---|
com.ibm.di.store.start.mode | automatic | The mode for starting up the Derby server process when required - set to automatic or manual. |
Com.ibm.di.store.hostname | localhost | The URL of the Derby server. |
Com.ibm.di.store.port | 1527 | The port for connecting to the Derby server. |
Com.ibm.di.store.sysibm | true | The state for using the SYSIBM schema or not; values true or false. |
com.ibm.di.store.varchar.length | 512 | The varchar(length) for the ID columns used in system store and System Store (PES) connector tables. |
Add these properties to the global.properties file after the System Store network mode properties.
Property | Default value | Description |
---|---|---|
derby.connection.requireAuthentication | true | Enables user authentication for the System Store. |
derby.authentication.provider | BUILTIN | Sets the user authentication provider to BUILTIN. This is the most basic and simple authentication provider that Derby has. |
derby.database.defaultConnectionMode | fullAccess | Defines the access level to the System Store user. The different access levels supported by Derby are "fullAccess", "readOnly" and "noAccess". |
We can configure create table SQL statements for
Property | Default value | Description |
---|---|---|
com.ibm.di.store.create.delta.systable | CREATE TABLE {0} (ID VARCHAR(VARCHAR_LENGTH) NOT NULL, SEQUENCEID int, VERSION int);ALTER TABLE {0} ADD CONSTRAINT IDI_CS_{UNIQUE} PRIMARY KEY (ID) | Create table SQL statements for the delta systable. |
com.ibm.di.store.create.delta.store | CREATE TABLE {0} (ID VARCHAR(VARCHAR_LENGTH) NOT NULL, SEQUENCEID int, ENTRY BLOB );ALTER TABLE {0} ADD CONSTRAINT IDI_DS_{UNIQUE} Primary Key (ID) | Create table SQL statements for the delta table. |
com.ibm.di.store.create.property.store | CREATE TABLE {0} (ID VARCHAR(VARCHAR_LENGTH) NOT NULL, ENTRY BLOB );ALTER TABLE {0} ADD CONSTRAINT IDI_PS_{UNIQUE} Primary Key (ID) | Create table SQL statements for the property table. |
com.ibm.di.store.create.sandbox.store | CREATE TABLE {0} (ID VARCHAR(VARCHAR_LENGTH) NOT NULL, ENTRY BLOB ) | Create table SQL statements for the Sandbox tables. |
com.ibm.di.store.create.recal.conops | CREATE TABLE {0} (METHOD varchar(VARCHAR_LENGTH), RESULT BLOB, ERROR BLOB) | Create table SQL statements for Record AssemblyLine. |
com.ibm.di.store.create.tombstones | CREATE TABLE IDI_TOMBSTONE ( ID INT GENERATED ALWAYS AS IDENTITY, COMPONENT_TYPE_ID INT, EVENT_TYPE_ID INT, START_TIME TIMESTAMP, CREATED_ON TIMESTAMP, COMPONENT_NAME VARCHAR(1024), CONFIGURATION VARCHAR(1024), EXIT_CODE INT, ERROR_DESCR VARCHAR(1024), STATS LONG VARCHAR FOR BIT DATA, GUID VARCHAR(1024) NOT NULL, USER_MESSAGE VARCHAR(1024), UNIQUE (ID, GUID)) | Specify the SQL statement for creating the Tombstone Manager table. Keep the same table names and field names. |
com.ibm.di.conn.rdbmschlog.cdcolname | ibmsnap_commitseq | Provide the ibmsnap_commitseq column name to be used by the RDBMS changelog connector. |