Installing and configuring solidDB® server for Universal Cache

Installing and configuring solidDB^® server for Universal Cache

1 Install Java Runtime Environment (JRE) or Java Development Kit (JDK), version 1.4.2 or newer, if not already installed.

JRE or JDK 1.4.2 or newer is needed to run the solidDB^® installer.

On Linux systems, GNU Compiler for Java (GCJ) is not supported.

2 On the downloaded installation image or the installation DVD, locate the installation program file for your operating system:

3 Double-click the installation program file. The solidDB^® installation wizard starts.

4 Follow the instructions on the wizard to complete the installation.

In Linux and UNIX operating systems, you must be able write to the directory that you are using for the installation. If the installation program cannot create the directory, you are prompted to specify a different directory.

5 Verify your solidDB^® server installation and familiarize yourself with the basic administration tasks.

For more information, see “Verifying solidDB^® installation” in the solidDB^® Getting Started Guide, as well as the solidDB^® Administrator Guide.

Configuring solidDB^® server for Universal Cache capability

To be able to use the solidDB^® server with the IBM InfoSphere CDC technology, you need modify configuration settings so that the IBM InfoSphere CDC for solidDB^® can connect to and replicate data from your solidDB^® database.

This section assumes that you are familiar with solidDB^® administration and have read, for example, “Administering solidDB^®” and “Configuring solidDB^®” in the solidDB^® Administrator Guide.

1 Set up your database environment by creating a working directory, your solidDB^® database, and user accounts.

For instructions, see “Creating a new database” in the solidDB^® Administrator Guide.

After you have installed the solidDB^® server, you can find the following directories in the installation directory:

You can use the eval_kit/cdc directory in the solidDB^® server installation directory as your working directory; it contains a sample solid.ini file for using solidDB^® with the Universal Cache capability or IBM InfoSphere CDC replication.

2 Configure the Log Reader by modifying the configuration parameters in the LogReader section of the solid.ini configuration file.

Set the LogReader.LogReaderEnabled parameter to yes.

You must enable the Log Reader to be able to use the solidDB^® database as a source database in IBM InfoSphere CDC replication. The factory value of the LogReader.LogReaderEnabled parameter is no.

Set the transaction log retention space size with the LogReader.MaxLogSize parameter.

The LogReader.MaxLogSize parameter sets the amount (size) of log files that are available for performing a catchup. The maximum size of log file depends on the available disk space and the expected downtime after which a catchup is needed. The factory value is 10 240 (10 GB).

If the log reader is enabled, the specified log file retention space is always used fully. Also, the log files can use even more space, if backups are not performed or the parameter General.CheckpointDeleteLog is set to no.

Set the in-memory buffer size for log records with the LogReader.MaxSpace parameter.

The MaxSpace parameter sets the size (in number of log records) of the in-memory log reader buffer used in throttling. The maximum number of log records depends on the expected size of load bursts. The factory value is 100000 log records.

The size of a log record is that of the (binary) row size, plus a few bytes of additional metadata overhead. When the buffer fills up, throughput throttling is applied; the operations are blocked until there is room in the log reader buffer.

3 Modify other performance and database-setup-related configuration
parameters as necessary.

Logging.DurabilityLevel

By default, the solidDB^® server durability level is set to relaxed (Logging.DurabilityLevel=1). Relaxed durability means that most recent transactions can be lost if the server fails unexpectedly.

To prevent loss of data, set the durability level to strict with the following setting in the solid.ini file:

Strict durability setting induces a performance penalty when compared to relaxed durability. Relaxed durability can be used without the risk of data loss if solidDB^® HA (HotStandby) configuration is applied with the 2-Safe replication protocol (default).

General.DefaultStoreIsMemory

By default, the solidDB^® table storage type is set to M-table (General.DefaultStoreIsMemory=yes).

By default, the solidDB^® isolation level is set to Read Committed (Sql.IsolationLevel=1).