IBM DB2 9.7.4 GoGrid Server Image (GSI) Get Started Guide

triparkansasData Management

Oct 31, 2013 (3 years and 7 months ago)

383 views

IBM
®

DB2
®

GSI Start
-
up Guide





1













IBM Software


Information Management






IBM
®

DB2
®

9.7.4

GoGrid Server Image
®

(GSI)


Get Started Guide
























IBM
®

DB2
®

GSI Start
-
up Guide





2



Table of Contents


1

Introduction

................................
................................
.....

3

1.1

Purpose

................................
................................
...........

3

1.2

Topics Covered

................................
................................

3

1.3

Assumptions

................................
................................
....

3

2

GoGrid, GSI/
Instance, and Software Prerequisites

......

4

2.1

GoGrid Server Instance Information

................................
.

4

2.2

Creating a GoGrid Account

................................
..............

4

2.3

Launching a GSI

................................
..............................

5

3

GSI/Instance setup and launching using the GoGrid
Console (Web
-
based graphical user interface)

............

6

3.1

Logging into the Console

................................
.................

6

3.2

Running a GSI Instance using the GoGrid Console

..........

6

4

Connecting to a Running GSI Instance

.......................

11

4.1

Booting the IBM DB2 GSI Instance

................................

11

4.1.1

Accessing the IBM DB2 GSI Setup Page

.......

11

4.1.2

Pre
-
installed Op
erating System License
Agreement Screen

................................
.....................

12

4.1.3

IBM DB2 GSI Setup Welcome Page

...............

14

4.1.4

IBM DB2 Instance Setup Module

....................

14

4.1.5

IBM DB2 Database Module

............................

16

4.1.6

IBM DB2 GoGrid Reset

................................
..

18

4.2

GSI Instance Access via SSH

................................
........

18

4.2.1

SSH into to a Running GSI Instance via
Windows

................................
................................
....

18

4.2.2

SSH into a Running G
SI Instance via Linux

....

20

5

Working with Your Installed System

...........................

21

5.1

Using Technology Explorer

................................
............

21

5.2

DB2 Registry, Database Manager, and Database
Configuration Setti
ngs

................................
................

24

5.2.1

DB2 Fault Monitor

................................
..........

24

5.2.2

DB2 Profile Registry Parameters

....................

24

5.2.3

Database Manager Configuration Parameters

25

5.2.4

Data
base Configuration Parameters
...............

25

5.2.5

Modifying DB2 Profile Registry and
Configuration Parameters

................................
..........

25

5.3

Feedback

................................
................................
.......

26


IBM
®

DB2
®

GSI Start
-
up Guide





3



Introduction

1.1

Purpose

This document details the

deployment instructions for DB2
®

9.7 GoGrid
®

Server Images
(GSIs) under the GoGrid Cloud infrastructure.

This GSI will allow you to experience the fully functional DB2 for Linux
®
, UNIX
®
,
Windows
®

data server on the GoGrid cloud. The GSI also includes cus
tomized modules
to guide you through the GSI/DB2 server configuration steps. The remainder of this
document will guide you through these steps.

1.2


Topics Covered

This document focuses on the process of setting up a DB2 server within the GoGrid
cloud environ
ment. It will cover the following topics in detail:



Setting up a GoGrid account and subscribing to the DB2 GSI



Deploying a new GSI server instance from a GSI (GoGrid Server Image)



Setting up GoGrid Cloud Storage for performing remote backups of DB2
databa
ses

1.3

Assumptions

This documentation is intended for users who have a general knowledge of Linux and
how Linux works. The user should also possess a good understanding of Linux
commands and how to manipulate input and output.

IBM
®

DB2
®

GSI Start
-
up Guide





4




2

GoGrid, GSI/Instance, and Soft
ware Prerequisites

Before deployment of a DB2 GSI can commence, please ensure that you understand the
instance prerequisites detailed below.

2.1

GoGrid Server Instance Information

DB2 GSIs are available in both 32
-
bit and 64
-
bit versions. Currently, GoGrid ho
sts two
flavors of DB2 both running under Red Hat
®

Enterprise Linux 5.6:


-

DB2 Express 9.7 FP4 32 bit

-

DB2 Workgroup 9.7 FP4 64 bit


GoGrid
provides a number of different GSI instance sizes to meet your computing needs.
Each GSI instance provides a predictab
le amount of dedicated compute capacity and is
charged per GSI instance
-
hour consumed.


The GSI instance types described in the following table are available.


You must choose an appropriate GSI server size for the DB2 GSI that you would like to
use.


Fo
r more information on instance types and pricing of GoGrid, please visit
H
U

http://www.gogrid.com/cloud
-
hosting/cloud
-
servers.php
U


2.2

Creating a GoGrid Account

To run GSI instances, a
GoGrid account will be required.

To sign up for a
GoGrid account
, please visit
H
U
http://
www.gogrid
.com
U
H
.

IBM
®

DB2
®

GSI Start
-
up Guide





5




Image excerpt from
https://www.gogrid.com/signUp/


2.3

Launching a GSI

GoGrid offers different interfaces to ru
n and manage your GSIs.

The GoGrid Console is a web
-
based graphical user interface for managing GSIs and
monitoring the running GSI instances in addition to some of the more infrastructure
specific features such as load balancing, cloud storage, firewall,

and VPN. This
interface allows new users to quickly get started and familiarized with the GoGrid cloud
environment.

Furthermore, the GoGrid Console is web
-
based and no additional software needs to be
installed. You can run the GoGrid Management Console

with a compatible web browser
such as the latest edition of Mozilla
®

Firefox
®

or Microsoft
®

Internet Explorer
®
.

To learn how to launch your GSIs using the GoGrid Management Console, please refer
to section

3
X

GSI
/Instance setup

and launching using the
GoGrid

Console (Web
-
based
graphical user interface)
X
H
.


IBM
®

DB2
®

GSI Start
-
up Guide





6



3

GSI/Instance setup and launching using the GoGrid
Console (Web
-
based graphic
al user interface)

3.1

Logging into the Console

In order to launch, terminate, and monitor your GSIs, you will first need to log into the
GoGrid Console. With your web browser, go to the address
H
http://my.gogrid.com
U
.
Input
the
username

and
password

that was generated when the GoGrid account was
created. Click the
Sign In
button.



If successful, you will be redirected to the GoGrid Console home screen.


3.2

Running a GSI Instance using the GoGrid Console

Under the GoGrid
Console navigation side bar, click the
“add”

button/link.

IBM
®

DB2
®

GSI Start
-
up Guide





7




You will be redirected to the GSI launch wizard. You can choose the location of where
to launch your GSI. Currently, GoGrid offers data centres located in western (US
-
West
-
1) and eastern (US
-
Ea
st
-
1) United States. Choose Cloud Server to deploy a pay
-
as
-
you
-
go cloud server instance:



You will then be presented with a list of available GSIs. Filter the list by inputting the
search string
“DB2”

in the name text box. Click the checkbox next t
o the GSI that you
IBM
®

DB2
®

GSI Start
-
up Guide





8



wish to launch. In this example, you will launch the GSI with the name
“DB2
-
EXP
-
9.7FP4
-
RHEL
-
5.6
-
32bit”
. Click the
“Next”

button to continue.



You will be presented with the GSI server details. Here you can select the name of your

GSI in addition to assigning a static IP from a list of available addresses. The GoGrid
server instance sizing can also be chosen here. For DB2 Express, the recommended
amount of RAM is 4 gigabytes. Click the
Save

button to continue

IBM
®

DB2
®

GSI Start
-
up Guide





9




The GoGrid in
frastructure will now launch the selected GSI with the attributes you
selected. You can monitor the progress of the GSI via the GoGrid Console. It usually
takes a few minutes for a server to get to the running state (green light). A GSI in the
prepping
stage is denoted with a yellow light.

IBM
®

DB2
®

GSI Start
-
up Guide





10




When the GSI is in the running state, right click on the server icon and select
Passwords
. You will be redirected to the running GSIs passwords credentials page.
Take note of the password associated with the DB2 G
SI:



In order to connect to your GSI instance, please jump to section

4

Connecting to a
Running
GSI

Instance

IBM
®

DB2
®

GSI Start
-
up Guide





11



4

Connecting to a Running GSI Instance

4.1

Booting the IBM DB2 GSI Instance

When an IBM DB2 GSI instance i
s first started, Apache HTTP server will automatically
start. Setup of the IBM DB2 GSI will proceed via a series of interactive web
-
based
configuration modules:

1.

GSI configuration login

2.

Pre
-
installed operating system and software license agreement screen
s

3.

A Welcome/Status screen denoting what setup modules have been completed

4.

DB2 Configuration Module

5.

Configuration Module Reset


A description of each interactive step is listed in the next several sub
-
sections.


4.1.1

Accessing the IBM DB2 GSI Setup Page

In order

to set up the IBM DB2
GSI

environment, you will need to access the web
-
based
IBM DB2
GSI

Setup that is accessible via the HTTPS port (443)

(To learn how to open
HTTPS port 443, please see section

3.4

Opening Ports on a

GSI

Instance
X
)
. Open up
either Microsoft Internet Explorer or Mozilla Firefox and point the address to:

https://<GSI instance
-
address>/config


You will be directed to the login page:

IBM
®

DB2
®

GSI Start
-
up Guide





12




The IBM DB2
GSI

Set
up login page authenticates users by accepting
the password that
was generated by GoGrid.
(please refer to

section

4.4.1 Running a
GSI

Instance (EC2
API Tools)
H

and
3.3 Running a
GSI

Instance using the
GoGrid

Console
H
)
.

Once you have
inputted the password
, the login page will compare the
inputted password
and grant
access if the one you provided
matches the password field of the GSI instance
.





4.1.2

Pre
-
installed Operating System Lice
nse Agreement Screen

After you have started the IBM DB2 GSI Setup for the first time, the user will be
presented with page displaying operating system and software license agreements. The
user must accept the license agreements before continuing.



Note
: The user mus
t agree to the licenses shown, otherwise setup will not continue
any further and the GSI instance will terminate.

IBM
®

DB2
®

GSI Start
-
up Guide





13



The following URLs provide you with access to view license agreements related to
SUSE Linux Enterprise Server and DB2. Depending on which edition of DB2 is included
in the GSI, different license agreement texts are displayed.

Red Hat
®

Enterprise Li
nux 5.6:

http://docs.redhat.com/docs/en
-
US/Red_Hat_Enterprise_Linux/5/html
-
single/5.6_Release_Notes/index.html

U
DB2 Express
U
:

HU
http://www
-
03.ibm.com/software/sla/sladb.nsf/displaylis/917B96D822A2B0E8852575C90067DC16?
OpenDocument

U
DB2 Workgroup
U
:

HU
http://www
-
03.ibm.com/software/sla/sladb.nsf/displaylis/4EEDC1E87D9AFA4F852575BF00444D05
?OpenDocument

The following screenshot displays the license agreement page:



To indicate that you understand and agree to the software licensing terms, click the
checkboxes underneath all license textboxes. Click the
[Next]

button to continue. Note
that once you accept the license agreements, port
22

will be open for
SSH

acces
s to the
GSI instance.


IBM
®

DB2
®

GSI Start
-
up Guide





14



4.1.3

IBM DB2 GSI Setup Welcome Page

After you have accepted the license agreements, you will be greeted with the IBM DB2
GSI Setup Welcome page. This page contains the completion status of the various
modules that you will be running th
rough in order to set up the IBM DB2 GSI
environment.



Take note of the sidebar on the left. You may traverse through any of the setup modules
at any time. However, once you start a module, you will not be able to traverse between
different steps and o
perations of the same module. If you make a mistake with any of
the modules, you may restart the module either via a handy
[Restart]

button at the top
right hand side of each step, the left sidebar, or the
IBM DB2 GSI Reset

module. At the
bottom of each
page is a
[Next]

button to guide you along the correct path for setting up
your IBM DB2 GSI instance. Click the
[Next]

button to proceed.


4.1.4

IBM DB2 Instance Setup Module

The IBM DB2 Instance Setup module will now execute. This module allows you to
configu
re the DB2 environment on your GSI instance.

You will be prompted to input the passwords for the various DB2 users, including
passwords for the DB2 instance owner, Database Administration Server (DAS) user, and
the fenced user must be specified.

You wil
l be allowed to customize the user and group names. If non
-
default names are
inputted, they must be no longer than 8 characters in length (setup will refuse to
continue to the next screen until all inputs are valid). Once the
user

and
password

informatio
n for the various fields have been entered, select
[Next]
to continue.

IBM
®

DB2
®

GSI Start
-
up Guide





15






The DB2 instance module will be kicked off. A report will be shown after the module
completes successfully:

IBM
®

DB2
®

GSI Start
-
up Guide





16




4.1.5

IBM DB2 Database Module

Run the IBM DB2 Database Module next to create

a database on the DB2 instance you
had created in the earlier step. Select the IBM DB2 Database Module on the left hand
side menu. Select the DB2 instance, and input a database name, then click the
N
ext

button:

IBM
®

DB2
®

GSI Start
-
up Guide





17




A brief report will be shown regarding t
he database creation:


IBM
®

DB2
®

GSI Start
-
up Guide





18



4.1.6

IBM DB2 GoGrid Reset

The DB2 GoGrid Reset module offers specific options to revert the GSI back to a state
before the DB2 PHP configuration modules were run. Click the left side bar link
IBM
DB2 GoGrid Reset



This module is espec
ially useful for ISVs looking to re
-
bundle or add on
-
top of an IBM
DB2 GSI as it offers a quick way to „clean‟ the image of databases, instances, and re
-
securitizes the GSI.

4.2

GSI

Instance Access via SSH

To gain access to more powerful features such as the
D
B2CLP

and other software
within the
GSI

instance, you will need to connect to the
GSI

instance via
SSH
. The
subsections below will walk you through how to SSH into a
GSI

instance in a Windows
and Linux environment.


4.2.1

SSH into to a Running GSI Instance via
Windows

Once a GSI instance is up and running and you have accepted the operating system
and software license screens, you can login to it via SSH. In Windows, you will need a
terminal emulator, such as

PuTTY.


Click on
Session

in the
Category:

panel on
the left again to return to the connection
details screen. Enter the
IP address

or
external hostname

of the GSI instance you
have launched, then click
Open

to start an SSH session to this GSI instance.


IBM
®

DB2
®

GSI Start
-
up Guide





19





A terminal window will appear if a successful conn
ection is established to the GSI
instance. Enter “
root
” as the user when prompted for a login. The GSI instance will
then prompt for a password. Input the password associated with the GSI instance that
you retrieved from the GoGrid console.



access if
the one you provided
matches the password field of the GSI instance
.




IBM
®

DB2
®

GSI Start
-
up Guide





20





Congratulations! You have now logged into your GSI instance in the Windows
environment.

4.2.2

SSH into a Running GSI Instance via Linux

To connect to the DB2 GSI in Linux, open a term
inal window and issue the following
command to log into your GSI instance:


ssh <GSI instance
-
address>


where
<GSI instance
-
address>
is the hostname or IP address of the GSI instance. If
the GSI is launched successfully, you will be login to the Linux oper
ating system inside
the GSI.


IBM
®

DB2
®

GSI Start
-
up Guide





21





5

Working with Your Installed System

Congratulations on completing the deployment of the IBM DB2 GSI. We will now point
you to where to find the components you want to work with.

5.1

Using Technology Explorer

The Technology Explo
rer for IBM DB2 is a light weight, web
-
based console for
monitoring and performing actions on your DB2 database. In order to use the
Technology Explorer, you will need to restart the Apache HTTP server as well as have
port 443 open on your GSI instance.


The Technology Explorer requires a running DB2 instance to reference necessary DB2
libraries so it can create a connection to a database. In order for these libraries to be
loaded, Apache HTTP server must be restarted. To restart Apache HTTP server, ru
n
the following command as the
root

user:

# service httpd restart

Shutting down httpd2 (waiting for all children to
IBM
®

DB2
®

GSI Start
-
up Guide





22



terminate)
:







































done

Starting httpd2 (prefork)

























done



Using your web browser of
choice, input the URL as follows:


https://<GSI instance
-
address>/TE




You will be greeted by the front page of the Technology Explorer. To connect to an
existing DB2 database, press the
“Connections…”

button on the top left of the page,
and press
“New”
.




IBM
®

DB2
®

GSI Start
-
up Guide





23



You will be prompted for connection details. Recall that the default
Port Number

for the
DB2 instance that you configured above was
50001
. The
Database

field is simply the
name of the database you have created. Also, since you are connecting via t
he GSI
instance‟s copy of Technology Explorer, you can set the
Hostname

field as
localhost

to
point to itself. The
Username

and
Password

fields refer to the DB2 instance user name
and password. When you have your credentials set, press the Connect button
.




You will notice that you are now connected to the database. To interact with the
database, select
View

from the top menu, then
DB2

Catalog Views
:



IBM
®

DB2
®

GSI Start
-
up Guide





24




You can then click on any of the tables. Click on the table icon beside
Employee
:




There are ma
ny more features and capabilities that Technology Explorer has to offer.
For more information on Technology Explorer, including software updates and
documentation, please visit
H
U
http://sourceforge.net
/projects/db2mc/
U
H
.


5.2

DB2 Registry, Database Manager, and Database Configuration
Settings

During the initial DB2 configuration module, certain Database Manager settings have
been pre
-
configured for your environment. These settings are configured based on
expert recommendations for easy administration. If you have specific requirements, you
may change the parameters as required.

5.2.1

DB2 Fault Monitor

The DB2 Fault Monitor (db2fm) is turned off on the DB2 GSI by default.


5.2.2

DB2 Profile Registry Parameters

To disp
lay a list of configured DB2 profile registry parameters issue the following
command:

db2set

all

The following is a list of set DB2 profile registry parameter specific to the DB2 GSI

IBM
®

DB2
®

GSI Start
-
up Guide





25



db2set DB2COMM=tcpip

All other DB2 profile registry parameters values ar
e set to the DB2 default values.


5.2.3

Database Manager Configuration Parameters

To display a list of configured DB2 Database Manager Configuration parameters:

db2 attach to
<DB2INSTANCE>

db2 get dbm cfg show detail

The following is a list of set DB2 profile re
gistry parameter specific to the DB2 GSI:

DFTDBPATH /db2fs

DIAGPATH /db2fs/diag

JAVA_HEAP_SZ 2048

INSTANCE_MEMORY AUTOMATIC

All other Database Manager Configuration Parameters are set to the DB2 default values.


5.2.4

Database Configuration Parameters

To display

a list of configured DB2 Database Configuration parameters:

db2 connect to
<DBNAME>

db2 get db cfg show detail

All other database parameters are set to the DB2 default values.


5.2.5

Modifying DB2 Profile Registry and Configuration Parameters

If any of the abov
e parameters do not fit your business requirements, you may change
the parameters using the following utilities.

To update DB2 profile registry parameters, execute the following as a user that belongs
to the SYSADM_GROUP (database manager configuration par
ameter). E.g. the
database instance owner:

db2set
<REGISTRY_PARAMETER>=<VALUE>


IBM
®

DB2
®

GSI Start
-
up Guide





26



To update Database Manager (DBM) configuration parameters, execute the following as
a user that belongs to the SYSADM_GROUP (database manager configuration
parameter):

db2 upda
te dbm cfg using
<PARAM_NAME> <VALUE>


To update Database (DB) configuration parameters, execute the following as a user that
has database administrative privilege:

db2 update db cfg using
<PARAM_NAME> <VALUE>


5.3

Feedback

We welcome your feedback about your
experience on the DB2 GSIs. If you would like to
comment on your experience on the DB2 GSI, please send your feedback to
H
askdata@ca.ibm.com
H
, enter the name of the DB2 GSI in the subject line.

For technical que
stions on DB2 GSIs, please refer to the DB2 Information Center
website at
H
U
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp
U
H
.

IBM
®

DB2
®

GSI Start
-
up Guide





27





© Copyright IBM Co
rporation 2011

All Rights Reserved.


IBM Canada

8200 Warden Avenue

Markham, ON

L6G 1C7

Canada


Printed in Canada

10/2011


IBM, IBM (logo), DB2 are trademarks or registered trademarks of
International Business Machines Corporation in the United States,
othe
r countries, or both.


Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.


Red Hat Enterprise Linux is a registered trademark of Red Hat in
the United States, other countries, or both.


UNIX is a registered trademark of
The Open Group in the United
States, other countries, or both


Windows and Internet Explorer are trademarks of Microsoft
Corporation in the United States, other countries, or both.


Mozilla and Firefox are trademarks of Mozilla Corporation in the
United St
ates, other countries, or both.


Java is a trademark of Sun Microsystems, Inc in the United States,
other countries, or both.


GoGrid is a registered trademark of ServePath LLC and/or its
affiliates in the United States and/or other countries


Other compan
y, product, or service names may be trademarks or
service marks of others.


References in this publication to IBM products or services do not
imply that IBM intends to make them available in all countries in
which IBM operates. The following paragraph does

not apply to the
United Kingdom or any other country where such provisions are
inconsistent with local law:


INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON
-
INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.


Some states do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to y
ou.


This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or
changes in
the product(s) and/or the program(s) described in this
publication at any time without notice.


Information concerning non
-
IBM products was obtained from the
suppliers of those products, their published announcements or
other publicly available sources. IB
M has not tested those products
and cannot confirm the accuracy of performance, compatibility or
any other claims related to non
-
IBM products. Questions on the
capabilities of non
-
IBM products should be addressed to the
suppliers of those products.


The in
formation in this publication is provided AS IS without
warranty. Such information was obtained from publicly available
sources, is current as of September 2009, and is subject to change.
Any performance data included in the paper was obtained in the
speci
fic operating environment and is provided as an illustration.
Performance in other operating environments may vary. More
specific information about the capabilities of products described
should be obtained from the suppliers of those products.