Previous Topic: Install Virtual Server for Installation of Oracle DatabaseNext Topic: Preconfigured Infrastructure Templates

Virtual Dedicated Server Application Templates › Install Virtual Server for Installation of DB2 Database

Install Virtual Server for Installation of DB2 Database

Latest Version: 1.0.1-1

Functional Overview

Install_DB2_v10_CentOS62 is a CentOS 6.2 based virtual server application prepared to install DB2 Database Version 10. The only requirement is that the installation files are copied to the application volumes.

The application contains a singleton base appliance that is used to create reusable database appliances.

The DB2 Database has a graphical installer but the graphic environment is not typically installed on Linux for System z. The base appliance comes with a minimal graphic environment and a web based VNC server. These provide access to the graphic environment required by the installer.

The application configures itself based on properties set during the first boot. The root password is set based on property value, VNC passowrd and passwords of three pre-created Linux users needed by DB2 database are set on property values.

The application is configured to install from a public CentOS repository. CentOS packages are installed by the end user by running yum -y install <package> as the root user.

Boundary

Properties

Property Name

Type

Description

vnc_pw

String

Defines the password used when connecting to graphical user interface (by VNC client or web applet) which installation runs in. This property is mandatory.

root_pw

String

Defines the password of the root account. It will be set on the first boot. This property is mandatory.

db2usr_pw

String

Defines the password of the users dasusr1, db2inst1 and db2fenc1, created for the purpose of using by DB2 instance to be installed. It will be set on the first boot. This property is mandatory.

primary_ip

String

Defines the primary IP address (v4 or v6) of the external interface of the appliance. This property is mandatory.

secondary_ip

String

Defines the secondary IP address (v4 or v6) of the external interface of the appliance. Default: (empty).

netmask

IP

Defines the network mask of the external interface. This property should be defined if IPv4 is used. Default: (empty).

gateway

IP

Defines the default IP network gateway (router) for the external interface. The gateway address can be outside the network specified by netmask. To use a gateway that does not expose an IP and serves as proxy ARP, set this property to 0.0.0.0. This property should be defined if IPv4 is used. Default: (empty).

ipv6_gateway

String

Defines the default IPv6 network gateway (router) for the external interface. This property should be defined if IPv6 is used. Default: (empty).

dns1

String

Defines the primary nameserver (v4 or v6). This property is mandatory.

dns2

String

Defines the secondary server (v4 or v6). Default: (empty).

dns3

String

Defines the third server (v4 or v6). Default: (empty).

Resources

Resource

Minimum

Maximum

Default

CPU

0.05

4

.1

Memory

512 MB

32 GB

2 GB

Bandwidth

1 Mbps

2 Gbps

100 Mbps

User Volumes

Volume

Description

install

Volume to hold the installation data.

Terminals

Name

Dir

Protocol

Description

in

in

any

When the DB2 Database software is installed, this terminal can be used to connect a client appliance for testing.

The external interface is enabled. It is used for incoming and outgoing traffic. Its network settings are configured through properties.

The default interface is enabled. It is used for maintenance (incoming ssh connections from the controller).

Operation

This application is to be used as a base for an appliance running the DB2 database. It contains all the necessary prerequisites to install DB2 Database Version 10 as described in its documentation. The application does not contain any DB2 software. That must be provided by the user who must have the necessary license to install the software

Initial Application Setup

Follow these steps:

  1. The installation should be started by provisioning the application. Here is an example provision command: 
    app provision Install_DB2_v10_CentOS62 Install_DB2_v10-1 data.size=3G install.size=1.5G DB2BASE.var.size=3G 

    DB2BASE.opt.size=1.1G vnc_pw=abcd1234 root_pw=defg1234 db2usr_pw=abcd5678 primary_ip=192.168.100.12 

    netmask=255.255.255.0 gateway=192.168.100.1 dns1=192.168.1.2 dns2=192.168.100.138
  2. The sizes of the volumes must be chosen in order to hold all data required for installation:

    Note: The volume setup in the provisioned application should accommodate for a typical install. However, there are many ways to install DB2 database and any accompanying software. If the volumes sizes and mount points do not fit your site's needs then you should change the sizes and appliance's descriptor to make any required modifications.

  3. When the appliance is provisioned and all modifications have been made, copy the installation materials to the install volume. Transfer via SSH SecureCopy protocol can be used, for example.
  4. Start the application and point your web browser to a URL with the following structure: 
    http://<primary_ip>:8888/

    alternatively, using native VNC (like TigerVNC vncviewer) client to <primary_ip>:5901
    primary_ip

    is the IP address specified during the provisioning of the application.

  5. You will be asked for a password. Enter the password that was set in the provisioned property vnc_pw.
  6. Once logged in you will se a single terminal (xterm) where you can start the installer for the product you wish to install. For example, the DB2 Database installer can be started in this way: 
     /mnt/install/eser/db2setup
  7. It is also possible to run an automated installation using a previously created response file. In that case, the graphical interface is not needed and the process can be initiated from the SSH text console.
  8. During the installation, when asking for three system Linux users, it is recommended to use the ones pre-created automatically during the first boot (dasusr1, db2inst1, db2fenc1) rather than leaving DB2 installer to create them itself. This ensures enough space for DB2 data. Alternatively, let the DB2 installer create the users but always point home directories to a volume with enough free space (/var/home is preferred).

Limitations/Requirements

After installation, the database is ready for client connections on the public IP address assigned in the application properties. However, running the application like this is not recommended. Turning the base appliance that now has the database software installed into a catalog appliance that can be reused in many applications is preferred.

The way to build such an appliance is dependent on the type of installation chosen and it is up to the end user to decide how the catalog appliance should be designed. Here are some recommended steps:

For more information on how to design appliances see the Appliance Developer Guide. 

Error Messages

In case of application startup failure, the following errors may be logged to the system log:

Error Message

Description

Incorrect 'primary_ip' value

Application failed to validate 'primary_ip' configuration option.

Incorrect 'secondary_ip' value

Application failed to validate 'secondary_ip' configuration option.

IPv4 DNS must be defined if IPv4-only networking is used

At least one IPv4 DNS server must be defined.

IPv6 DNS must be defined if IPv6-only networking is used

At least one IPv6 DNS server must be defined.

Failed to set up external network

Application failed to setup appliance interface.

Failed to set up external network -- primary and secondary IP's are identical

Primary and secondary IP's must differ

Failed to set up external network -- secondary IP XXX is in use

Secondary IP XXX is in use

Property netmask must be defined if IPv4 networking is used

Property netmask must be defined if defined any IPv4 address

Property gateway must be defined if IPv4-only networking is used

Property gateway should be defined when using only IPv4 networking

Property ipv6_gateway must be defined if IPv6-only networking is used

Property ipv6_gateway should be defined when using only IPv6 networking

Gateway is not defined

Either gateway or ipv6_gateway property should be defined

Open source and third-party software used inside of the application

The following open source third-party software is used in addition to that software found on the appliance base class (LUX64).

These packages are required by DB2 Database (as described in the installation documentation):

These packages are required to run the graphical environment and the web based VNC client:

These packages are needed as dependencies of the packages above: