User Guide : Map Connectors : Source and Target Map Connectors : Derby (Embedded)
 
Share this page                  
Derby (Embedded)
Derby is an open source relational database management system (RDBMS) that is available under version 2.0 of the Apache License and implemented using Java Virtual Machine (JVM). In embedded mode, the Derby database resides in a Java application and runs in the same JVM as the application. All connection processes and database requests are handled through the Java application.
The integration platform supports insert, update, and delete operations from the 10.4.2.0 version of the Derby database in embedded mode.
This connector writes multimode output, so you can perform table drop and table insert operations directly on your target database.
Connector-Specific Notes
In embedded mode, a Derby database can accept only one connection at a time. For instance, running more than one map that uses this connector generates an error.
The naming convention to use when creating a new index is IDX_<column name>_<table name>. For example, use IDX_c_t to create an index on column "c" located in table "t."
When creating a table in the Map window, you can only specify field length for the following data types: byte, bytes, string, char, and decimal. The default field length for char is 1.
Property Options
You can set the following source (S) and target (T) properties.
Property
S/T
Description
Batch Size
S
The number of source records the connector caches before processing them in a map. The default is zero, which means to read all.
Additional Properties
ST
Name=value pairs that is required for the connection. Separate multiple pairs with semi colons.
Show System Tables
S
Required. Only applicable if the user is logged onto the database as the database administrator. Only the DBA has access to system tables.
If set to True, allows you to see all the tables created by the DBA. The system table names appear in the table list. The default is False.
Show Views
ST
If set to True, all views are displayed in the table list. Default value is True.
Scrollability of Results
S
Required. Determines how to set result set.
The three options:
• Forward Only (default) - Result set is not scrollable. The system reads the next row in the result set.
• Scrollable - Insensitive to changes - Result set is scrollable. The system can data read data forward or backward. Any changes to the result set that are made while it is open are not visible.
• Scrollable - Sensitive to changes - Result set is scrollable. Any changes that are made to the result set while it is open are visible.
Transaction Isolation
T
Allows you to specify any one of four isolation levels when reading from or writing to a database table with Derby. The default value is Read Committed.
The ANSI SQL 2 standard defines three specific ways in which serializability of a transaction may be violated: P1 (Dirty Read), P2 (Nonrepeatable Read), and P3 (Phantoms).
The following lists the four supported isolation levels:
• READ_UNCOMMITTED—Permits P1, P2, and P3.
• READ_COMMITTED—Permits P2 and P3. Does not permit P1.
• REPEATABLE_READ—Permits P3. Does not permit P1 and P2.
• SERIALIZABLE—Does not permit P1, P2 or P3.
FlushFrequency
T
Number of record inserts to buffer before sending a batch to the connector. Default is zero. If you are inserting many records, change the default to a higher value to improve performance.
Batch Response
T
This property creates a batch response file, which serves as a reporting mechanism to the connector. The file provides detailed results for each object in a batch where the batch size is greater than 1. Obtaining detailed results is useful in the following cases:
• Capturing system-generated object IDs for use in future updates.
• Correlating an error with its object and have enough information about the error for exception handling and error diagnosis.
• For more information, see Batch Response File.
Ignore Null Fields
T
If set to False (default), null values are included when updating records.
If set to True, ignores null data values when updating records.
Additional Properties
The integration platform supports the following additional properties to connect to a Derby database in embedded mode. When specifying multiple properties, separate each with a semicolon.
• bootPassword=key
• collation=collation
• create=true
• createFrom=path
• databaseName=nameofDatabase
• dataEncryption=true
• encryptionKey=key
• encryptionProvider=providerName
• encryptionAlgorithm=algorithm
• failover=true
• logDevice=logDirectoryPath
• newEncryptionKey=key
• newBootPassword=newPassword
• password=userPassword
• restoreFrom=path
• rollForwardRecoveryFrom=path
• securityMechanism=value
• shutdown=true
• slaveHost=hostname
• slavePort=portValue
• startMaster=true
• startSlave=true
• stopMaster=true
• stopSlave=true
• territory=ll_CC
• traceDirectory=path
• traceFile=path
• traceFileAppend=true
• traceLevel=value
• upgrade=true
• user=userName
• ssl=sslMode
Data Types
The integration platform supports all Derby data types, which are listed below.
• BIGINT
• BLOB
• CHAR
• CHAR FOR BIT DATA
• CLOB
• DATE
• DECIMAL
• DOUBLE
• DOUBLE PRECISION
• FLOAT
• INTEGER
• LONG VARCHAR
• LONG VARCHAR FOR BIT DATA
• NUMERIC
• REAL
• SMALLINT
• TIME
• TIMESTAMP
• VARCHAR
• VARCHAR FOR BIT DATA
• XML