12 - Lesson5 Client Connectivity

®
IBM Software Group
Lesson 5: Client Connectivity

(DB2 on Campus Lecture Series)
Raul F. Chong
IBM Toronto Laboratory
© 2005 IBM Corporation

IBM Software Group | DB2 Information Management Software
Agenda
DB2 Directories
Setup required at the server
Setup required at the client
Other methods to setup connectivity
2
Agenda
DB2 Directories
3
Directories
System database directory
list db directory
Local database directory

list db directory on <drive/path>
Node directory
list node directory
DCS directory
list dcs directory
4
Agenda
DB2 Directories
5
I) Setup required at the server

From the Configuration Assistant (CA) myhost.ibm.com
a) DB2COMM Instance “DB2”

Choose Configure Æ DB2 Registry
b) SVCENAME
Choose Configure Æ DBM configuration mydb1
Find “Communications” section.
Or
DB2COMM=TCPIP
From the Control Center Port = 50000
a) DB2COMM User defined in O/S:

User ID = myuser
Right click on instance and choose “Set up communications...”
Password = mypsw
b) SVCENAME
Right click on instance and choose “Configure parameters...”
Find “Communications” section.
6

Or
Manually using commands:
a) SVCENAME (service name) in DBM CFG

update dbm cfg using svcename <port # or service name>
If you use a service name, ensure to update these files:
– Linux: /etc/services
– Windows: c:\winnt\system32\drivers\etc\services
Example: db2cdb2inst1 50000/tcp
b) DB2COMM in the DB2 Registry

db2set DB2COMM=TCPIP
7
Launching Configuration Assistant (CA)
Start > Programs > IBM DB2 > Set-up Tools > Configuration Assistant
8
Configuration Assistant
Cataloged databases
9
Verifying the DB2COMM Registry Variable
Configuration Assistant > Configure menu > DB2 Registry

10
DB2COMM Registry Variable
Note: Changing this

parameter requires an
Instance re-start
11
Agenda
DB2 Directories
12
II) Setup required at the client

Client
Application db directory node directory

connect to mydb1
user myuser mydb1 mynode
using mypsw
Two commands to run at the client:
1) catalog tcpip node mynode

remote myhost.ibm.com server 50000
2) catalog database mydb1 at node mynode
13
Putting both setups together: At the client and server

Client myhost.ibm.com
Instance “DB2”
Application db directory node directory
connect to mydb1
user myuser mydb1 mynode network
using mypsw
mydb1
Two commands to run at the client: DB2COMM=TCPIP
Port = 50000
1) catalog tcpip node mynode User defined in O/S:

User ID = myuser
remote myhost.ibm.com server 50000 Password = mypsw
14

Two commands to run at the client:
1) catalog tcpip node mynode

remote myhost.ibm.com server 50000
OR
The Configuration Assistant Control Center

- Right click on white space - From the “All databases”
- Choose “Add database using wizard...” folder, right click and choose
“Add”
15
Launching the Add Database Wizard from the CA
Configuration Assistant > Selected menu > Add Database Using Wizard
16
Add Database Wizard
17
Caution!
The Configuration Assistant will allow you to catalog databases with

invalid hostnames, port numbers, etc.
Everything might look correct; however, when you try to connect to the
database, you will receive a connection error!
Also ensure the user ID and password you provide to connect to the
remote database is correct
By default the authentication takes place on the DB2 server you are trying to
connect to, therefore, you must provide a user ID and password defined on
that server
18
Agenda
DB2 Directories
19
Search and Discover Modes
Search the Enter server

network name and
for any choose
server protocol
20
Discovery by DB2 Clients
DB2 Client
Discovery Message
DB2 Server
Search and locate DB2 servers on the
network
DAS Level
DISCOVER=SEARCH
Requires the DAS to be running on the

DB2 server in order to discover databases Instance Level
DISCOVER_INST=DISABLE DISCOVER_INST=ENABLE
Can prevent or "hide" a server / database

from being discovered by setting the Database Level
appropriate DAS, Instance, and Database DISCOVER_DB=DISABLE DISCOVER_DB=ENABLE
level configuration parameters
21
Client and Server Profiles
If you are configuring a large number of servers or clients, rather than

set up each one individually, you can fully set up one, export a profile
(i.e. configuration file) from it, then apply the profile to the other
clients/servers
This saves an administrator a lot of time when setting up the

environment
22
Quicklab # 6 - Using the Configuration Assistant
In this Quicklab, you will use the Configuration Assistant to

catalog a database on one of your neighbor’s workstations
You can follow the same procedure to catalog a database on a
client in your own environment
Refer to the Quicklab #6 instructions
23
Good references
DB2 Connectivity Cheat sheet series from developerWorks
(www7b.boulder.ibm.com/dmdd) by Raul F. Chong
24
What’s Next?
Lesson 1 Installation & the DB2 editions

Lesson 2 The DB2 Environment
Lesson 3 Tools & scripting
Lesson 4 The DB2 architecture
Lesson 5 Client connectivity COMPLETED!
Lesson 6 Working with data objects
Lesson 7 Data movement

Lesson 8 Security
Lesson 9 Backup & recovery
Lesson 10 Maintenance
25

12 - Lesson5 Client Connectivity

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

12 - Lesson5 Client Connectivity

Uploaded by

Copyright:

Available Formats

®

IBM Software Group

Lesson 5: Client Connectivity

© 2005 IBM Corporation

 Local database directory

I) Setup required at the server

a) DB2COMM Instance “DB2”

From the Control Center Port = 50000

a) DB2COMM User defined in O/S:

Setup required at the server

 Manually using commands:

a) SVCENAME (service name) in DBM CFG

b) DB2COMM in the DB2 Registry

Launching Configuration Assistant (CA)

Verifying the DB2COMM Registry Variable

Configuration Assistant > Configure menu > DB2 Registry

DB2COMM Registry Variable

 Note: Changing this

II) Setup required at the client

Application db directory node directory

Two commands to run at the client:

1) catalog tcpip node mynode

2) catalog database mydb1 at node mynode

Putting both setups together: At the client and server

Two commands to run at the client: DB2COMM=TCPIP

1) catalog tcpip node mynode User defined in O/S:

2) catalog database mydb1 at node mynode

Setup required at the client

1) catalog tcpip node mynode

The Configuration Assistant Control Center

Launching the Add Database Wizard from the CA

Add Database Wizard

 The Configuration Assistant will allow you to catalog databases with

Search and Discover Modes

Search the Enter server

Discovery by DB2 Clients

 Requires the DAS to be running on the

 Can prevent or "hide" a server / database

Client and Server Profiles

 If you are configuring a large number of servers or clients, rather than

 This saves an administrator a lot of time when setting up the

Quicklab # 6 - Using the Configuration Assistant

 In this Quicklab, you will use the Configuration Assistant to

Lesson 1 Installation & the DB2 editions

Lesson 7 Data movement

You might also like

Local database directory

From the Control Center Port = 50000

Manually using commands:

Note: Changing this

The Configuration Assistant Control Center

The Configuration Assistant will allow you to catalog databases with

Requires the DAS to be running on the

Can prevent or "hide" a server / database

If you are configuring a large number of servers or clients, rather than

This saves an administrator a lot of time when setting up the

In this Quicklab, you will use the Configuration Assistant to