ShowTable of Contents
Overview
This tutorial walks through a single-node installation of IBM Connections on a Red Hat Enterprise Linux 6.3 64-bit system . The first eight lessons are required to configure a working environment.
Introduction
Lesson 1: Preparing Your System
Lesson 2: Installing WebSphere Application Server (WAS)
Lesson 3: Installing IBM HTTP Server and Plugin
Lesson 4: Installing WAS Fix Packs
Lesson 5: Installing DB2
Lesson 6: Installing Tivoli Directory Integrator
Lesson 7: Installing a Domino LDAP Directory
Lesson 8: Intermediate Steps
Lesson 9: Installing IBM Connections 4.0
Lesson 10: Installing Cognos (optional - requires another VM with 4G RAM and 100G disk space)
Lesson objectives
Connections 4.0 requires some type of database. In this tutorial, we will use DB2.
In this lesson, you will install and configure DB2 for use with Connections 4.0.
At the end of this lesson, you will be able to install and configure DB2 for use with Connections 4.0. At the end of this tutorial, you will be ready to install and configure a single-node IBM Connections 4.0 environment running on a Red Hat Enterprise Linux 6.3 64-bit system.
After completing this lesson, you will be able to do the following:
-
Identify the DB2 Installation and Fix Pack Files
-
Install DB2
-
Install DB2 Fix Pack
-
Apply the DB2 License
-
Configure Fault Monitor to Automatically Restart DB2 Instances
At the end of this lesson, you will be able to install DB2 and required fix pack.
System requirements
A RHEL 6.3 64-bit machine with a minimum of 8G memory and 100G of disk space is required.
Resources
Task 1: Install DB2
In this task, we will locate and install DB2.
|
Step
|
Action
|
|
1
|
Login as user root.
|
|
2
|
Locate the DB2 files below that were downloaded and extracted in Lesson 1, Task 7, Step 4. They should be in the directory /opt/install/DB2.
DB2_ESE_97_Linux_x86-64.tar.gz
Part Number: CZ19NEN
Description: IBM DB2 Enterprise Server Edition 9.7 for Linux® on AMD64 and Intel® EM64T systems (x64) English
DB2_ESE_Restricted_QS_Activation_97.zip
Part Number: CZ381ML
Description: IBM DB2 9.7, Enterprise Server Edition - Restricted Use - QuickStart Guide and Activation Multiplatform Multilingual
v9.7fp5_linuxx64_universal_fixpack.tar.gz
Description: DB2 9.7.0.5 fix pack
Note: If you do not have these files and need to download them, go to XL Software Downloads or IBM Passport Advantage On-line Web site or Fix Central. |
|
3
|
Install the DB2 server. Switch to /opt/install/DB2/ese and run db2setup to start the DB2 installation wizard.
[root@connections4 ]# cd /opt/install/DB2/ese
[root@connections4 ese ]# ./db2setup
|
|
4
|
At the DB2 Setup Launchpad, select Install a Product. Click Install New.
 |
|
5
|
At the Welcome to the DB2 Setup Wizard dialogue, click Next.
 |
|
6
|
Accept the terms of the license agreement. Click Next.
 |
|
7
|
For the installation type, select Typical 900 - 1090 MB. Click Next.
 |
|
8
|
At the dialogue Select installation, response file creation, or both, select Install DB2 Enterprise Server Edition on this computer and save my settings in a response file. Click Next.
 |
|
9
|
The installation directory should be /opt/IBM/db2/V9.7 (change the lower case 'ibm' to upper case 'IBM'). Click Next.
Note: If you receive an error stating that the location is not creatable or writable, see "Appendix A: Troubleshooting".
 |
|
10
|
At the dialogue Install the Tivoli System Automation for Multiplatforms, choose Do not install SA MP. Click Next.
 |
|
11
|
At the dialogue Set user information for the DB2 Administration Server, select New user and enter the following:
User name: dasusr1
UID: <leave blank>
Group name: dasadm1
GID: <leave blank>
Password: <your password>
Home directory: /home/dasusr1
Click Next.
 |
|
12
|
At the dialogue Set up a DB2 instance, select Create a DB2 instance. Click Next.
 |
|
13
|
At the dialogue Set up partitioning options for the DB2 instance, select Single partition instance. Click Next.
 |
|
14
|
At the dialogue Set user information for the DB2 instance owner, select New user and enter the following:
User name: db2inst1
UID: <leave blank>
Group name: db2iadm1
GID: <leave blank>
Password: <your password>
Home directory: /home/db2inst1
Click Next.
 |
|
15
|
At the dialogue Set user information for the fenced user, select New user and enter the following:
User name: db2fenc1
UID: <leave blank>
Group name: db2fadm1
GID: <leave blank>
Password: <your password>
Home directory: /home/db2fenc1
Click Next.
 |
|
16
|
At the dialogue Prepare the DB2 tools catalog, select Do not prepare the DB2 tools catalog. Click Next.
 |
|
17
|
At the dialogue Set up notifications select Do not setup your DB2 server to send notifications at this time. Click Next.
 |
|
18
|
At the dialogue Start copying files and create response file, review your selections. When satisfied, click Finish.
 |
|
19
|
After some time (5-15 minutes), the setup will complete with a message of Setup has completed successfully. Click Finish.
Note: If the setup completes with the message Setup has completed with a minor error, see "Appendix A: Troubleshooting".
 |
|
20
|
Verify the version of DB2 installed. From a command prompt, login as the DB2 instance owner and run db2level.
[root@connections4]# su - db2inst1
[db2inst1@connections4 ~]$ db2level
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09070"
with level identifier "08010107".
Informational tokens are "DB2 v9.7.0.0", "s090521", "LINUXAMD6497", and Fix
Pack "0".
Product is installed at "/opt/IBM/db2/V9.7".
|
|
21
|
To confirm the DB2 instance is active and working, type db2sampl.
[db2inst1@connections4 ~]$ db2sampl
Starting the DB2 instance...
Creating database "SAMPLE"...
Connecting to database "SAMPLE"...
Creating tables and data in schema "DB2INST1"...
Creating tables with XML columns and XML data in schema "DB2INST1"...
Stopping the DB2 instance...
'db2sampl' processing complete.
Once this completes, type db2 connect to sample.
[db2inst1@connections4 ~]$ db2 connect to sample
Database Connection Information
Database server = DB2/LINUXX8664 9.7.0
SQL authorization ID = DB2INST1
Local database alias = SAMPLE
Once this completes, type db2 "select * from db2inst1.employee". You should see records print to screen from the sample database.
[db2inst1@connections4 ~]$ db2 "select * from db2inst1.employee"
EMPNO FIRSTNME MIDINIT LASTNAME WORKDEPT PHONENO HIREDATE JOB EDLEVEL SEX BIRTHDATE SALARY BONUS COMM
------ ------------ ------- --------------- -------- ------- ---------- -------- ------- --- ---------- ----------- ----------- -----------
000010 CHRISTINE I HAAS A00 3978 01/01/1995 PRES 18 F 08/24/1963 152750.00 1000.00 4220.00
000020 MICHAEL L THOMPSON B01 3476 10/10/2003 MANAGER 18 M 02/02/1978 94250.00 800.00 3300.00
...
..
|
|
22
|
Result: You have successfully installed DB2 v9.7.0.0 and verified that it is operational. |
Task 2: Install DB2 Fix Pack
In this task, we will install the required DB2 fix pack 5 to bring the server to DB2 v9.7.0.5.
|
Step
|
Action
|
|
1
|
Log in as user root.
|
|
2
|
Located the fix pack file v9.7fp5_linuxx64_universal_fixpack.tar.gz previously downloaded in Lesson 1, Task 7, Step 4. It should be in the directory /opt/install/DB2. Make a new DB2Fix directory and extract the files.
[root@connections4]# mkdir /opt/install/DB2Fix
[root@connections4]# cd /opt/install/DB2Fix
[root@connections4 DB2Fix]# tar xvfz ../DB2/v9.7fp5_linuxx64_universal_fixpack.tar.gz
|
|
3
|
Stop all DB2 processes using the following steps in bold below:
[root@connections4 DB2Fix]# su - db2inst1
[db2inst1@connections4 ~]$ . $HOME/sqllib/db2profile (note: this is DOT SPACE $HOME/sqllib...)
[db2inst1@connections4 ~]$ db2 force applications all
DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.
[db2inst1@connections4 ~]$ db2 terminate
DB20000I The TERMINATE command completed successfully.
[db2inst1@connections4 ~]$ db2stop
01/23/2013 15:24:27 0 0 SQL1064N DB2STOP processing was successful.
SQL1064N DB2STOP processing was successful.
[db2inst1@connections4 ~]$ db2licd -end
[db2inst1@connections4 ~]$ exit
logout
[root@connections4 DB2Fix]# su - dasusr1
[dasusr1@connections4 ~]$ . $HOME/das/dasprofile (note: this is DOT SPACE $HOME/das...)
[dasusr1@connections4 ~]$ db2admin stop
SQL4407W The DB2 Administration Server was stopped successfully.
[dasusr1@connections4 ~]$ exit
logout
[root@connections4 DB2Fix]# su - db2inst1
[db2inst1@connections4 ~]$ $HOME/sqllib/bin/ipclean
/home/db2inst1/sqllib/bin/ipclean: Removing DB2 engine and client's IPC resources for db2inst1.
[db2inst1@connections4 ~]$ exit
logout
[root@connections4 DB2Fix]#
|
|
4
|
Change to the universal directory and install the fix pack as shown below:
[root@connections4 DB2Fix]# cd /opt/install/DB2Fix/universal
[root@connections4 universal]# ./installFixPack -b /opt/IBM/db2/V9.7/
When done, you will see a message The execution completed successfully. |
|
5
|
Verify the version of DB2 installed. From a command prompt, login as the DB2 instance owner and run db2level.
[root@connections4 ~]# su - db2inst1
[db2inst1@connections4 ~]$ db2level
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release "SQL09075"
with level identifier "08060107".
Informational tokens are "DB2 v9.7.0.5", "special_29283", "IP23292_29283", and
Fix Pack "5".
Product is installed at "/opt/IBM/db2/V9.7".
|
|
6
|
Result: You have successfully installed DB2 fix pack 5 to bring the server to DB2 v9.7.0.5. |
Task 3: Apply the DB2 License to Your Server
In this task, we will apply a valid license.
|
Step
|
Action
|
|
1
|
When first installed, the DB2 license is not registered. To confirm, login as user db2inst1 and run the command db2licm -l.
[root@connections4 universal]# su - db2inst1
[db2inst1@connections4 ~]$ db2licm -l
Product name: "DB2 Enterprise Server Edition"
License type: "License not registered"
Expiry date: "License not registered"
Product identifier: "db2ese"
Version information: "9.7"
|
|
2
|
Locate the file DB2_ESE_Restricted_QS_Activation_97.zip that was downloaded in Lesson 1, Task 7, Step 4. It should be in the directory /opt/install/DB2. Login again as root and follow the steps below.
[db2inst1@connections4 ~]$ su - root
Password:
[root@connections4 ~]# mkdir -p /opt/install/DB2lic
[root@connections4 ~]# cd /opt/install/DB2lic
[root@connections4 DB2lic]# cp ../DB2/DB2_ESE_Restricted_QS_Activation_97.zip .
[root@connections4 DB2lic]# unzip DB2_ESE_Restricted_QS_Activation_97.zip
|
|
3
|
With the files now unzipped, switch to the db2inst1 user and follow steps below to license your DB2:
[root@connections4 DB2lic]# su - db2inst1
[db2inst1@connections4 ~]$ cd /opt/install/DB2lic/
[db2inst1@connections4 DB2lic]$ db2licm -a /opt/install/DB2lic/ese_o/db2/license/db2ese_o.lic
[db2inst1@connections4 DB2lic]$ db2licm -l
LIC1402I License added successfully.
LIC1426I This product is now licensed for use as outlined in your License Agreement. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT, LOCATED IN THE FOLLOWING DIRECTORY: "/opt/IBM/db2/V9.7/license/en_US.iso88591"
|
|
4
|
To confirm the DB2 server is now properly licensed, we'll again run the command db2licm -l.
[db2inst1@connections4 DB2lic]$ db2licm -l
Product name: "DB2 Enterprise Server Edition"
License type: "Restricted"
Expiry date: "Permanent"
Product identifier: "db2ese"
Version information: "9.7"
|
|
5
|
Result: The DB2 server now has a valid license applied. The product is ready for use with Connections. |
Task 4: Configure the Fault Monitor Facility to Automatically Restart DB2 UDB Instances
In this task, we will configure the Fault Monitor facility so if the DB2 Universal Database (DB2 UDB) instance exits prematurely, the fault monitor will restart it automatically.
|
Step
|
Action
|
|
1
|
Log in as user root.
|
|
2
|
Enable the Fault Monitor Coordinator by following below:
[root@connections4 ~]# cd /opt/IBM/db2/V9.7/bin
[root@connections4 bin]# ./db2fmcu -u -p /opt/IBM/db2/V9.7/bin/db2fmcd
: Specifying this option creates or replaces the db2fmcd.conf file under the /etc/init directory so that the FMCD process will be started each time you reboot. |
|
3
|
Start up the fault monitor daemon:
[root@connections4 bin]#./db2fm -i db2inst1 -U
|
|
4
|
Start up the fault monitor service:
[root@connections4 bin]#./db2fm -i db2inst1 -u
|
|
5
|
Turn on the fault monitor for the instance:
[root@connections4 bin]#./db2fm -i db2inst1 -f on
|
|
6
|
Verify the fault monitor state. Log in as the instance owner, then perform the command below. You should see similar output.
[root@connections4]# su - db2inst1
[db2inst1@connections4 ~]$db2fm -s -S
Gcf module 'fault monitor' is NOT operable
Gcf module '/opt/IBM/db2/V9.7/lib64/libdb2gcf.so' state is AVAILABLE
|
|
7
|
To confirm, reboot the server. Once reboot completes, the fault monitor service should be available. To verify it's state, login as the instance owner and perform the command below. You should see similar output.
[root@connections4]# su - db2inst1
[db2inst1@connections4 ~]$db2fm -s -S
Gcf module 'fault monitor' state is AVAILABLE
Gcf module '/home/test/sqllib/lib/libdb2gcf.so' state is AVAILABLE
|
|
8 |
Log in as root, go to /opt/IBM/db2/V9.7/bin directory, and verify the FMC Daemon state using the command below:
[db2inst1@connections4 ~]$ su - root
password:
[root@connections4 ~]# cd /opt/IBM/db2/v9.7/bin
[root@connections4 bin]# ./db2fmcu
FMC: up: PID = 3217
At this point, if the instance is shut down in any way other than via the db2stop command, the fault monitor will start it up again.
|
|
9 |
Results: The DB2 instance will be automatically restarted after shutdown or upon reboot. |
|
|
|
Appendix A: Troubleshooting
|
Problem
|
If you receive an error similar to the following:
The location specified is not creatable or writable: "/opt/IBM/db2/V9.7".
This would most likely occur on Task 1, step 8. |
|
Resolution
|
The permissions on the IBM directory were set to the default (700) or written out drwx
. The DB2 installation creates another user which must have create access under this directory structure being used. To resolve this, use the chmod command to allow read and execute permissions for both group and other on the IBM directory like this:
chmod 755 /opt/IBM
Once changed to 755, the permissions on the IBM directory (or the directory of your choice) will look like this: drwxr-xr-x
|
|
Problem
|
If you receive the following message at the completion of setup:
Setup has completed with a minor error
This may occur on Task 1, step 19. |
|
Resolution
|
Sometimes the DB2 instance is not automatically restarted. One simple way to quickly determine if it's started, login as the owner of the DB2 instance (in this case, it's db2inst1 created in Task 1, Step 14).
Now run the command dbstart.
If the DB2 instance is not already started, you will get a message stating that the DB2START processing was successful.
[db2inst1@connections4 ~]$ db2start
01/21/2013 15:10:11 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
Once the instance is started, type db2sampl to create a sample DB2 database.
[db2inst1@connections4 ~]$ db2sampl
Starting the DB2 instance...
Creating database "SAMPLE"...
Connecting to database "SAMPLE"...
Creating tables and data in schema "DB2INST1"...
Creating tables with XML columns and XML data in schema "DB2INST1"...
Stopping the DB2 instance...
'db2sampl' processing complete.
Now type db2 connect to sample to connect to the sample database.
[db2inst1@connections4 ~]$ db2 connect to sample
Database Connection Information
Database server = DB2/LINUXX8664 9.7.0
SQL authorization ID = DB2INST1
Local database alias = SAMPLE
And lastly, type db2 "select * from db2inst1.employee"
[db2inst1@connections4 ~]$ db2 "select * from db2inst1.employee"
EMPNO FIRSTNME MIDINIT LASTNAME WORKDEPT PHONENO HIREDATE JOB EDLEVEL SEX BIRTHDATE SALARY BONUS COMM
------ ------------ ------- --------------- -------- ------- ---------- -------- ------- --- ---------- ----------- ----------- -----------
000010 CHRISTINE I HAAS A00 3978 01/01/1995 PRES 18 F 08/24/1963 152750.00 1000.00 4220.00
000020 MICHAEL L THOMPSON B01 3476 10/10/2003 MANAGER 18 M 02/02/1978 94250.00 800.00 3300.00
...
..
: This should not be an issue once you complete Task 4: Configure the Fault Monitor Facility to Automatically Restart DB2 UDB Instances. |
|