If the file ${user.home}/taskanaUnitTest.properties is present, the {@linkplain - * DataSource} is created according to the properties jdbcDriver, jdbcUrl, dbUserName and - * dbPassword. If any of these properties is missing, or the file doesn't exist, the default - * {@linkplain DataSource} for H2 in-memory db is created. - * *
Additionally the property schemaName can be defined. If that property is missing, or
* the file doesn't exist the schemaName TASKANA will be used.
*/
diff --git a/docker-databases/db2_11-1/README.md b/docker-databases/db2_11-1/README.md
deleted file mode 100644
index 56b8d4ec8..000000000
--- a/docker-databases/db2_11-1/README.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# How to build the IBM DB2 Express-C docker image
-
-1. Download the database from either [IBM directly](https://www-01.ibm.com/marketing/iwm/iwm/web/pickUrxNew.do?source=swg-db2expressc) or from our [NT Onedrive](https://msnovatec-my.sharepoint.com/:f:/g/personal/mzo_novatec-gmbh_de/EuxS9esUxppHn-1Mobq7UT4BVWbwXga585q7o3h6hzAC6g?e=PK3KdM) (NT employees only)
-2. Name that tar file `db.tar.gz` and place it in this folder
-3. Execute a docker build command
diff --git a/docker-databases/db2_11-1/Dockerfile b/docker-databases/db2_11-5/Dockerfile
similarity index 87%
rename from docker-databases/db2_11-1/Dockerfile
rename to docker-databases/db2_11-5/Dockerfile
index e5b70d8a0..56a66b232 100644
--- a/docker-databases/db2_11-1/Dockerfile
+++ b/docker-databases/db2_11-5/Dockerfile
@@ -17,7 +17,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
-FROM centos:7
+FROM centos:8 AS base
###############################################################
#
@@ -48,19 +48,27 @@ RUN localedef -i de_DE -c -f UTF-8 \
-A /usr/share/locale/locale.alias de_DE.UTF-8 && echo "LANG=de_DE.UTF-8" > /etc/locale.conf
RUN echo "export LANG=de_DE.UTF-8" >> /etc/profile
+FROM base AS db2-install
+
COPY ./db.tar.gz /tmp/expc.tar.gz
+COPY ./db2server.rsp /tmp/db2server.rsp
RUN cd /tmp && tar xf expc.tar.gz \
- && su - db2inst1 -c "/tmp/expc/db2_install -y -b /home/db2inst1/sqllib" \
+ && su - db2inst1 -c "/tmp/server_dec/db2setup -r /tmp/db2server.rsp" \
&& echo '. /home/db2inst1/sqllib/db2profile' >> /home/db2inst1/.bash_profile \
- && rm -rf /tmp/db2* && rm -rf /tmp/expc* \
+ && rm -rf /tmp/db2* && rm -rf /tmp/expc* && rm -rf /tmp/server_dec \
&& sed -ri 's/(ENABLE_OS_AUTHENTICATION=).*/\1YES/g' /home/db2inst1/sqllib/instance/db2rfe.cfg \
&& sed -ri 's/(RESERVE_REMOTE_CONNECTION=).*/\1YES/g' /home/db2inst1/sqllib/instance/db2rfe.cfg \
&& sed -ri 's/^\*(SVCENAME=db2c_db2inst1)/\1/g' /home/db2inst1/sqllib/instance/db2rfe.cfg \
&& sed -ri 's/^\*(SVCEPORT)=48000/\1=50000/g' /home/db2inst1/sqllib/instance/db2rfe.cfg
+RUN echo "0 localhost 0" > /home/db2inst1/sqllib/db2nodes.cfg
+
+FROM base
+
+COPY --from=db2-install /home/ /home/
+
RUN su - db2inst1 -c "db2start && db2set DB2COMM=TCPIP \
- && db2set -g -null DB2_COMPATIBILITY_VECTOR \
&& db2 create database TSKDB using codeset utf-8 territory en-us \
collate using 'CLDR181_LDE_AS_CX_EX_FX_HX_NX_S3' PAGESIZE 32 K" \
&& su - db2inst1 -c "db2stop force" \
diff --git a/docker-databases/db2_11-5/README.md b/docker-databases/db2_11-5/README.md
new file mode 100644
index 000000000..04cc77a33
--- /dev/null
+++ b/docker-databases/db2_11-5/README.md
@@ -0,0 +1,6 @@
+# How to build the IBM DB2 Community Edition docker image
+
+1. Download the database from
+ https://www.ibm.com/de-de/products/db2-database/developers
+2. Name that tar file `db.tar.gz` and place it in this folder
+3. Execute a docker build command
diff --git a/docker-databases/db2_11-5/db2server.rsp b/docker-databases/db2_11-5/db2server.rsp
new file mode 100644
index 000000000..4630b807e
--- /dev/null
+++ b/docker-databases/db2_11-5/db2server.rsp
@@ -0,0 +1,939 @@
+** ============================================================================
+**
+** Sample response file for IBM DB2
+** --------------------------------
+** To select features and settings to install, uncomment the corresponding
+** keywords and specify values for those keywords. You do not need to select
+** features if you select the TYPICAL or COMPACT installation options.
+**
+** Comments are made by placing either an asterisk (*) or a hash symbol (#) at
+** the start of a line, or by placing ** or ## after the start of a line to
+** comment out the rest of that line.
+** All keywords that are currently uncommented (not preceded by * or #) are
+** mandatory and must be assigned values for the installation to continue.
+** All other keywords are optional. If optional keywords are not specified,
+** the installation will proceed using default values. Lines that start out
+** with two asterisks are documentation and should not be enabled.
+**
+** For more information on creating or configuring an ESE instance with the
+** DB2 pureScale Feature, see "Installing the
+** IBM DB2 pureScale feature for DB2 Server Edition
+** using a response file" in the DB2 Information Center.
+** For more information on configuration parameters, see "Configuring the DB2 database manager with
+** configuration parameters" in the DB2 Information Center.
+**
+** For more information on DB2 registry and environment variables, and configuration
+** parameters, see "DB2 registry and environment variables" in the DB2 Information Center.
+**
+** For more information on how to perform a response file installation, see
+** "Response file considerations" in the DB2 Information Center.
+**
+** Refer to the DB2 Information Center at:
+** https://www-01.ibm.com/support/knowledgecenter/SSEPGG_11.5.6/com.ibm.db2.luw.kc.doc/welcome.html
+**
+** ============================================================================
+** General Options
+** ---------------
+
+** Only one product can be specified for the following PROD keyword. Specifying
+** multiple products in an installation is not supported.
+PROD = DB2_SERVER_EDITION
+
+** The FILE keyword determines the base installation path. If you specify a
+** path that does not yet have this product, this will install a new copy. If
+** you specify a path that has this product, this will be considered an
+** existing installation intended to install additional functionality. This is
+** a mandatory keyword for root installation. Remove this keyword for non-root
+** installation. If not removed, its value must be $HOME/sqllib where $HOME
+** represents the HOME directory of the non-root user ID that owns the non-root
+** installation.
+FILE = /home/db2inst1/sqllib
+
+** Modify the value of the following LIC_AGREEMENT keyword to indicate that you
+** have read and agreed to the license agreement file in the db2/license
+** directory.
+LIC_AGREEMENT = ACCEPT ** ACCEPT or DECLINE
+
+** If an interactive type is set, db2setup will prompt for CD locations and
+** give feedback as to progress, otherwise nothing will be displayed until the
+** installation is complete.
+*INTERACTIVE = NONE ** NONE, YES, MACHINE
+
+** The CONFIG_ONLY keyword is used to specify that the response file is being
+** used for creating or configuring an instance, and nothing is to be
+** installed. This keyword must be set to YES if a response file is used with
+** db2isetup.
+*CONFIG_ONLY = ** YES or NO
+
+** INSTALL_TYPE keyword is used to select the installation type. If you specify
+** a TYPICAL or a COMPACT install type, no COMP keywords are required. In this
+** case the installer will select the appropriate components for you. All COMP
+** keywords are ignored by the installer unless the INSTALL_TYPE is set to
+** CUSTOM. If you select the CUSTOM install type, then ensure that you enable
+** all of the COMP keywords that are required for your database environment.
+**
+** Note: The install type is not related to the language selection.
+** ----------------------------------------------------------------------------
+INSTALL_TYPE = COMPACT ** TYPICAL, COMPACT, CUSTOM
+
+** The following components are part of all TYPICAL installations. If you
+** perform a typical installation, all of these components will be installed on
+** your computer.
+** ----------------------------------------------------------------------------
+
+** DB2 Advanced Copy Services help protect mission-critical data that requires
+** 24x7 availability. It offers an integrated solution designed to implement
+** high-efficiency backup and restore processes and helps eliminate
+** backup-related performance issues.
+*COMP = ACS ** Integrated Flash Copy Support
+
+** Provides federated support required to access DB2 for iSeries and DB2 for
+** z/OS and OS/390 data sources.
+*COMP = DB2_DATA_SOURCE_SUPPORT ** DB2 data source support
+
+** Sample database source provides sample data and metadata that allows you to
+** create a sample database using the First Steps application.
+*COMP = DB2_SAMPLE_DATABASE ** Sample database source
+
+** Enables users and applications with Federated Data Source Access
+*COMP = FED_DATA_SOURCE_SUPPORT ** Federated Data Access Support
+
+** First Steps is a graphical tool that will help familiarize you with DB2
+** features and functions.
+*COMP = FIRST_STEPS ** First Steps
+
+** Guardium Installation Manager Client component will place the Guardium
+** Installation Manager(GIM) Client under DB2 Install Path.
+*COMP = GUARDIUM_INST_MNGR_CLIENT ** Guardium Installation Manager Client
+
+** The DB2 Instance Setup wizard is a Java-based tool you can use to set up
+** instances on your computer after installing DB2.
+*COMP = INSTANCE_SETUP_SUPPORT ** DB2 Instance Setup wizard
+
+** LDAP Exploitation allows DB2 to use an LDAP directory to store database
+** directory and configuration information.
+*COMP = LDAP_EXPLOITATION ** DB2 LDAP support
+
+** (PCMK keyword for installation of Pacemaker using response file is not yet
+** supported) Pacemaker is an open-source, high availability cluster manager
+** software integrated on Linuxamd64 and Linux390x64.
+*COMP = PCMK ** Pacemaker
+
+** IBM Tivoli System Automation for Multiplatforms provides high availability
+** and disaster recovery capabilities for AIX, Linux, Solaris SPARC, and
+** Windows.
+** If this component is selected, it will either be installed, updated or
+** upgraded by the DB2 installer. Use COMP=TSAMP only if you are running as
+** root user.
+*COMP = TSAMP ** Tivoli SA MP
+
+
+** The following components are not part of TYPICAL installations, and thus can
+** only be installed through CUSTOM installs.
+** ----------------------------------------------------------------------------
+
+** The base application development tools component contains tools and files
+** (including header files, libraries, and a precompiler) that are needed for
+** developing applications that work with DB2.
+*COMP = APPLICATION_DEVELOPMENT_TOOLS ** Base application development tools
+
+** A scalable, highly-available, high performance file system optimized for
+** multi-petabyte storage management.
+** If this component is selected, it will either be installed, updated or
+** upgraded by the DB2 installer. Use COMP=GPFS only if you are running as
+** root user.
+*COMP = GPFS ** General Parallel File System (GPFS)
+
+** Application data sources use an application to access the underlying
+** nonrelational data. The raw data can be in a number of standard and
+** nonstandard formats.
+*COMP = IINR_APPLICATIONS_WRAPPER ** Application data sources
+
+** Scientific data sources are developed exclusively for the life sciences
+** industry, such as those containing genomic, proteomic, bioinformatic, and
+** cheminformatic information.
+*COMP = IINR_SCIENTIFIC_WRAPPER ** Scientific Data Sources
+
+** Structured file data sources contain nonrelational data stored in files with
+** a defined, repeatable structure.
+*COMP = IINR_STRUCTURED_FILES_WRAPPER ** Structured file data sources
+
+** Enables users and applications to submit distributed requests for data
+** managed by Informix systems.
+** This feature is only installed and not configured when the PURESCALE feature
+** is selected for installation.
+*COMP = INFORMIX_DATA_SOURCE_SUPPORT ** Informix data source support
+
+** Enables users and applications to submit distributed requests through JDBC
+** for data managed by DBMS.
+*COMP = JDBC_DATA_SOURCE_SUPPORT ** JDBC data source support
+
+** Enables users and applications to submit distributed requests for data
+** stored in any data source that supports ODBC and X/Open CLI compliant
+** drivers.
+*COMP = ODBC_DATA_SOURCE_SUPPORT ** ODBC data source support
+
+** Enables users and applications to submit distributed requests for data
+** managed by Oracle systems.
+*COMP = ORACLE_DATA_SOURCE_SUPPORT ** Oracle data source support
+
+** The IBM DB2 pureScale Feature provides clustering technology to DB2 products
+** on distributed platforms.
+** Selecting the PURESCALE feature will automatically install every other
+** required component. See the DB2 Information Center for more information on
+** the pre-installation planning and prerequisites needed for a successful IBM
+** DB2 pureScale installation and instance setup. Use COMP=PURESCALE only if
+** you are running as root user.
+*COMP = PURESCALE ** IBM DB2 pureScale Feature
+
+** Spatial Extender client contains the support required for communicating with
+** a Spatial Extender server.
+*COMP = SPATIAL_EXTENDER_CLIENT_SUPPORT ** Spatial Extender client
+
+** Provides Spatial Extender support for the DB2 server, providing the storing
+** and query of geographical information in DB2 tables.
+*COMP = SPATIAL_EXTENDER_SERVER_SUPPORT ** Spatial Extender server support
+
+** Enables users and applications to submit distributed requests for data
+** managed by Microsoft SQL Server systems.
+*COMP = SQL_SERVER_DATA_SOURCE_SUPPORT ** SQL Server data source support
+
+** Enables users and applications to submit distributed requests for data
+** managed by Sybase systems.
+*COMP = SYBASE_DATA_SOURCE_SUPPORT ** Sybase data source support
+
+** Enables users and applications to submit distributed requests for data
+** managed by Teradata systems.
+*COMP = TERADATA_DATA_SOURCE_SUPPORT ** Teradata data source support
+
+** The DB2 Text Search component, powered by OmniFind, delivers an integrated,
+** high quality and scalable search technology in DB2 databases.
+** This feature is only installed and not configured when the PURESCALE feature
+** is selected for installation.
+*COMP = TEXT_SEARCH ** DB2 Text Search
+
+** The following languages apply to all translated components. Enable the
+** language(s) you want installed. If you do not enable any language keywords,
+** then the English language (EN) will still be installed by default.
+** ---------------------------------------------------------------------------
+*LANG = BR ** Portuguese - Brazil (pt_BR)
+*LANG = CN ** Simplified Chinese (zh_CN)
+*LANG = CZ ** Czech (cs_CZ)
+*LANG = DE ** German (de_DE)
+*LANG = ES ** Spanish (es_ES)
+*LANG = FR ** French (fr_FR)
+*LANG = IT ** Italian (it_IT)
+*LANG = JP ** Japanese (ja_JP)
+*LANG = KR ** Korean (ko_KR)
+*LANG = PL ** Polish (pl_PL)
+*LANG = RU ** Russian (ru_RU)
+*LANG = TW ** Traditional Chinese (zh_TW)
+
+
+** (Valid for non-root upgrade only) Upgrade Older Release
+** -------------------------------------------------------
+** Specify whether you want to upgrade any previous versions of the product.
+** Specifying this keyword will remove any previous version and upgrade any
+** settings to the new installation. Be aware that during upgrade of the
+** current copy, only the product specified in the response file will be
+** installed. Other previously installed products need to be upgraded
+** separately following this upgrade.
+*UPGRADE_PRIOR_VERSIONS = FALSE ** TRUE or FALSE
+
+** IBM DB2 pureScale Feature Host Information
+** ------------------------------------------
+** Specify the hosts to which the DB2 product is to be installed. This section
+** must always list the installation initiating host. Do no specify any
+** keywords in this section if you are not installing the IBM DB2 pureScale
+** Feature. Ensure that password-less ssh root access is available on all hosts
+** and between all hosts.
+
+** The HOST keyword is used to specify a host identifier for one set of host
+** keys. This keyword is mandatory if you are installing the IBM DB2 pureScale
+** Feature.
+*HOST = host1 ** char(14) no spaces
+
+** Use the HOSTNAME keyword with the host identifier prefix to identify the
+** name of the host. A host can be a physical machine or LPAR, on which a DB2
+** member or a cluster caching facility will run. If an alias or IP address is
+** provided, the installer will attempt to convert it to a canonical hostname
+** prior to instance creation. The host name must be a unique host name across
+** the network. The following formats are accepted: long name (for example,
+** host1.ibm.com), short name (for example, host1), IP address (IPv4:
+** xxx.xxx.xxx.xxx). This keyword is mandatory if you have specified the HOST
+** keyword.
+*host1.HOSTNAME = ** char(255) no spaces
+
+** The CLUSTER_INTERCONNECT_NETNAME keyword is used to specify the name of a
+** high speed interconnect name that corresponds to a high speed adapter name.
+** Refer to the DB2 Information Center for valid types of high speed adapters.
+** This keyword is mandatory if you have specified the HOST keyword.
+*host1.CLUSTER_INTERCONNECT_NETNAME = ** char(255) no spaces
+
+
+*HOST = host2 ** char(14) no spaces
+*host2.HOSTNAME = ** char(255) no spaces
+*host2.CLUSTER_INTERCONNECT_NETNAME = ** char(255) no spaces
+
+** Instance Creation Settings
+** --------------------------
+** User IDs managed by NIS/NIS+ are not supported. If an existing user ID is
+** used, make sure it is not locked and its password has not expired.
+
+** Prefix name of one instance set. To create or update an instance, one set of
+** instance keywords must be specified. The instance set is comprised of the
+** identifying prefix value for the INSTANCE key followed by the keys that are
+** prefixed by the specified INSTANCE prefix value. If you are creating a DSF
+** instance you can only specify one instance at a time in this response file.
+** Note: DSF is the instance type for a IBM DB2 pureScale instance. If you are
+** not creating a DSF instance, then multiple instances can be specified for
+** creation or update in this response file.
+INSTANCE = DB2_INST ** char(8) no spaces
+
+** Real name of the instance, and also the user ID of instance owner. It can be
+** different from the value of the INSTANCE keyword. If an existing ID is
+** specified for the instance's NAME keyword, make sure the user ID exists on
+** all the participating hosts with the same UID, GID, corresponding group
+** name, user name and user home directory. Ensure that existing user IDs are
+** not locked and that the password has not expired. IBM DB2 pureScale Feature
+** users must specify a name that is unique across the IBM DB2 pureScale
+** implementation.
+DB2_INST.NAME = db2inst1 ** char(8) no spaces, no upper case letters
+
+** The UID will be generated if the keyword is not specified - highly
+** recommended.
+*DB2_INST.UID = ** Unsigned integer
+DB2_INST.GROUP_NAME = db2iadm1 ** char(30) no spaces
+
+** Use a generated GID if no value provided - highly recommended.
+*DB2_INST.GID = ** Unsigned integer
+*DB2_INST.HOME_DIRECTORY = /home/db2inst1 ** char(64) no spaces. Valid for root installation only
+*DB2_INST.PASSWORD = db2inst1-pwd
+
+** If PURESCALE is selected or installed, the default instance type will be
+** DSF.
+*DB2_INST.TYPE = ESE ** DSF ESE WSE STANDALONE CLIENT
+
+** Set the instance to be auto-started after system reboot. The AUTOSTART
+** keyword can only be used by a root installation and only a non-pureScale
+** instance type. This keyword is invalid for non-root installation. This
+** keyword cannot be used for DSF instance type.
+DB2_INST.AUTOSTART = YES ** YES or NO
+
+** The START_DURING_INSTALL keyword will start the instance during the
+** installation. If this keyword is not specified, the behavior follows the
+** AUTOSTART keyword above.
+DB2_INST.START_DURING_INSTALL = YES ** YES or NO. Default is YES.
+*DB2_INST.SVCENAME = db2c_db2inst1 ** BLANK or char(14). Reserved for root installation only
+*DB2_INST.PORT_NUMBER = 25000 ** 1024 - 65535, Reserved for root installation only
+
+** The ports in range [FCM_PORT_NUMBER, FCM_PORT_NUMBER+MAX_LOGICAL_NODES] are
+** reserved during the installation. Valid for root installation only. If your
+** instance type is DSF, the ports in range [FCM_PORT_NUMBER,
+** FCM_PORTNUMBER+MAX_LOGICAL_NODES+3] is reserved. The ports have to be
+** continuous and identical on all the participating hosts.
+*DB2_INST.FCM_PORT_NUMBER = 20000 ** 1024 - 65535, the beginning port number.
+*DB2_INST.MAX_LOGICAL_NODES = ** 1 - 128 for DSF instances or 1 - 199 for ESE instances. It is a maximum number of logical members to be used on one member host. Valid for root installation only.
+
+** The DB2CF_PORT_NUMBER and the DB2CF_MGMT_PORT_NUMBER are to be reserved for
+** the cluster caching facility (CF). As the CF is an instance designation, the
+** port names will be pre-defined based on the name of the instance. Example:
+** Where the instance name is db2sdin1, the names required for the CF ports
+** will be DB2CF_db2inst1 and DB2CF_db2inst1_MGMT. Ensure that all the port
+** names are the same on all the participating hosts. The two CF ports must be
+** available on all the participating hosts. If you want the installer to
+** generate these values, leave them commented out.
+*DB2_INST.DB2CF_PORT_NUMBER = 56001 ** 1024 - 65535.
+*DB2_INST.DB2CF_MGMT_PORT_NUMBER = 56000 ** 1024 - 65535.
+
+** The PREFERRED_PRIMARY_CF is used to specify the preferred primary cluster
+** caching facility needed to create a new IBM DB2 pureScale instance. This
+** keyword is mandatory if you are creating a new IBM DB2 pureScale instance.
+** The value provided must match the value of any HOST keyword specified in
+** this response file. If you are extending an instance, this keyword should be
+** commented out.
+*DB2_INST.PREFERRED_PRIMARY_CF = ** a host identifier, char(14)
+
+** The PREFERRED_SECONDARY_CF is used to specify the preferred secondary
+** cluster caching facility for the IBM DB2 pureScale instance. The value
+** provided must match the value of any HOST keyword specified in this response
+** file. This host identifier should be specified in any HOST section.
+*DB2_INST.PREFERRED_SECONDARY_CF = ** a host identifier, char(14)
+
+** The MEMBER keyword is required if you are creating a new IBM DB2 pureScale
+** instance. The value provided must match the value of any HOST keyword
+** specified in this response file. Specify more MEMBER keywords so that each
+** new host is defined in this response file as either a DB2 member or a
+** cluster caching facility (CF host, see above).
+*DB2_INST.MEMBER = ** a host identifier, char(14)
+*DB2_INST.CLIENT_IMPORT_PROFILE = ** a full path or a file in the same directory as the response file
+
+** Do not set FEDERATED if you are creating or configuring a DSF instance.
+*DB2_INST.FEDERATED = ** YES or NO
+
+** Do not set INFORMIX_CLIENT_HOME if you are creating or configuring a DSF
+** instance.
+*DB2_INST.INFORMIX_CLIENT_HOME = BLANK ** BLANK, char(1023)
+
+** Do not set INFORMIX_SERVER_HOME if you are creating or configuring a DSF
+** instance.
+*DB2_INST.INFORMIX_SERVER_HOME = BLANK ** BLANK, char(1023)
+*DB2_INST.ORACLE_HOME = ** any valid path , char(64) no spaces
+*DB2_INST.SYBASE_HOME = ** any valid path, char(1023)
+*DB2_INST.SYBASE_OCS = ** valid SYBASE_OCS directory name, char(1023)
+*DB2_INST.SQLSERVER_ODBC_LIB_PATH = ** the full path name where libodbc file is in, char(1023)
+*DB2_INST.SQLSERVER_ODBC_INI_PATH = ** the full path name of .odbc.ini file including the file name, char(1023)
+*DB2_INST.TERADATA_CLI_PATH = ** the full path name to libcliv2.so library
+*DB2_INST.TERADATA_ERRMSG_PATH = ** the full path name to errmsg.txt error message file
+*DB2_INST.AUTHENTICATION = SERVER ** CLIENT, SERVER, or SERVER_ENCRYPT
+
+** An existing user ID should be specified for DB2SSHID_USERNAME keyword, make
+** sure the user ID exists on all the participating hosts with the same UID,
+** GID, corresponding group name, user name and user home directory. Ensure
+** that existing user IDs are not locked and that the password has not expired.
+** IBM DB2 pureScale Feature users must specify a name that is unique across
+** the IBM DB2 pureScale implementation.
+*DB2_INST.DB2SSHID_USERNAME = ** char(8) no spaces, no upper case letters
+
+** Tivoli SA MP Tiebreaker Settings (IBM DB2 pureScale Feature only)
+** -----------------------------------------------------------------
+** The DB2_CLUSTER_SERVICES_TIEBREAKER_DEVICE_PATH keyword is used to specify
+** the device path for Tivoli SA MP Tiebreaker setup. The keyword is mandatory
+** when setting up the first IBM DB2 pureScale instance.
+
+** All the hosts specified in HOST section must have direct access to this
+** disk.
+*DB2_CLUSTER_SERVICES_TIEBREAKER_DEVICE_PATH = ** a valid device path, for example, /dev/sda
+
+** Shared File System Settings (IBM DB2 pureScale Feature only)
+** ------------------------------------------------------------
+** Only one of the following two keywords is needed when setting up the first
+** IBM DB2 pureScale instance on the host; If both INSTANCE_SHARED_DEVICE_PATH
+** and INSTANCE_SHARED_DIR are specified, INSTANCE_SHARED_DIR will be ignored.
+** If the task is to extend an instance to a new host, both of these keywords
+** will be ignored.
+
+** Specify INSTANCE_SHARED_DEVICE_PATH to create a DB2 cluster file system. All
+** the hosts specified in the HOST sections should have direct access to the
+** shared device path specified.
+*INSTANCE_SHARED_DEVICE_PATH = ** a valid device path, for example, /dev/sda
+
+** Specify the INSTANCE_SHARED_MOUNT to define the mounting point of the new
+** DB2 cluster file system. It is optional and valid only if
+** INSTANCE_SHARED_DEVICE_PATH is specified.
+** INSTANCE_SHARED_DEVICE_PATH is specified.
+*INSTANCE_SHARED_MOUNT = ** a valid mount point of the new DB2 cluster file system.
+
+** Specify the INSTANCE_SHARED_DIR to use a user-managed shared file system for
+** instance creation.
+*INSTANCE_SHARED_DIR = ** a valid mount point of shared file system.
+
+** Fenced User Creation Settings
+** -----------------------------
+** Valid for root installation only. User IDs managed by NIS/NIS+ are not
+** supported. If an existing ID is used, make sure it is not locked and its
+** password has not expired.
+
+** Make sure the user name specified for FENCED_USERNAME is not locked and its
+** password has not expired.
+*DB2_INST.FENCED_USERNAME = db2sdfe1 ** char(8) no spaces, no upper case letters
+
+** If no value is provided for FENCED_UID keyword, the DB2 installer will
+** generate one for you. This is highly recommended.
+*DB2_INST.FENCED_UID = ** Unsigned integer
+*DB2_INST.FENCED_GROUP_NAME = db2fsdm1 ** char(30) no spaces
+
+** If no value is provided for FENCED_GID keyword, the DB2 installer will
+** generate one for you. This is highly recommended.
+*DB2_INST.FENCED_GID = ** Unsigned integer
+*DB2_INST.FENCED_HOME_DIRECTORY = ** char(64) no spaces
+
+** This FENCED_PASSWORD is required if the fenced user ID is a new user
+*DB2_INST.FENCED_PASSWORD = ** char(8)
+
+** Text Search Configuration
+** -------------------------
+
+** Do not set CONFIGURE_TEXT_SEARCH if you are creating or configuring a DSF
+** instance.
+*DB2_INST.CONFIGURE_TEXT_SEARCH = NO ** YES or NO
+
+** Do not set TEXT_SEARCH_HTTP_SERVICE_NAME if you are creating or configuring
+** a DSF instance.
+*DB2_INST.TEXT_SEARCH_HTTP_SERVICE_NAME = db2j_db2inst1 ** BLANK or char(14). Valid for root installation only
+
+** Do not set TEXT_SEARCH_HTTP_PORT_NUMBER if you are creating or configuring a
+** DSF instance.
+*DB2_INST.TEXT_SEARCH_HTTP_PORT_NUMBER = 55000 ** Any unused port number from 1024 - 65535
+
+** Instance DBM CFG Settings
+** -------------------------
+*DB2_INST.CF_DIAGLEVEL = 2 ** a number in range [0 - 4]
+*DB2_INST.CF_DIAGPATH = ** BLANK or char(215)
+*DB2_INST.CF_MEM_SZ = AUTOMATIC ** AUTOMATIC or a number in range [32768 - 4 294 967 295]
+*DB2_INST.CF_NUM_CONNS = AUTOMATIC ** AUTOMATIC or a number in range [4-256]
+*DB2_INST.CF_NUM_WORKERS = AUTOMATIC ** AUTOMATIC or a number in range [1 - 31]
+*DB2_INST.RSTRT_LIGHT_MEM = AUTOMATIC ** 1-10 for AUTOMATIC or a number in range [1 - 50]
+*DB2_INST.AGENTPRI = ** SYSTEM, -1 or 41-128
+*DB2_INST.ASLHEAPSZ = ** 1 - 524288
+*DB2_INST.AUDIT_BUF_SZ = ** 0 - 65000
+*DB2_INST.CATALOG_NOAUTH = ** 0, 1, YES or NO
+*DB2_INST.CLUSTER_MGR = ** TSA, VENDOR: