Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will accompany the content that you post.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

DB2 10.1 DBA for Linux, UNIX, and Windows certification exam 611 prep, Part 8: Connectivity and networking

Darliene Hopes (dlhopes@us.ibm.com), DB2 Solution Migration Consultant, IBM
Darliene Hopes
Darliene Hopes is a DB2 solution migration consultant at IBM. She has been working with DB2 for Linux, UNIX, and Windows since the start of her career. She is an IBM Certified DB2 database administrator who has been recently and consistently contributing to the DB2 community.

Summary:  This tutorial aims to explain the process of configuring communications and the processes of cataloging databases, remote servers (nodes), and Database Connection Services (DCS) databases. You will also get introduced to DB2® Discovery and learn how to manage connections to System z® and System i® host databases. You will also learn about Lightweight Directory Access Protocol (LDAP). This tutorial prepares you for Part 8 of the DB2® 10.1 DBA for Linux®, UNIX®, and Windows® certification exam 611.

View more content in this series

Date:  25 Oct 2012
Level:  Intermediate PDF:  A4 and Letter (389 KB | 20 pages)Get Adobe® Reader®

Comments:  

DB2 discovery

DB2 discovery provides an easy way to catalog a remote server and a database without having to know detailed communication-specific information. DB2 discovery broadcasts a discovery request over the network when invoked by a client. Every DB2 server on the network configured to support the discovery process provides a response in the form of a list of instances found on the server, information about the communication protocol each instance supports, and a list of databases found within each instance.

DB2 discovery uses one of two methods to process a discovery request: search and known. When search discovery method is used, the network is searched for valid DB2 servers and databases, and a list of all servers, instances, and databases found is returned to the client with the communications information needed to catalog and connect to each. When using the known discovery method, the network is searched for a specific server using a specific communications protocol. Like the search method, when the specified server is found, a list of all instances and databases found on the server is returned to the client with the information needed to catalog and connect to each.

The parameter values in the DAS instance configuration file, DB2 Database Manager configuration file for each instance (on client and server), and the database configuration file for each database within an instance determines whether a client can launch a DB2 discovery request, how it could be accomplished, and whether a particular server will respond. These parameters control:

  • If a client can launch a DB2 discovery request.
  • If a server can be located by DB2 discovery, whether the server can be located only when search discovery method is used, or when either the search or known discovery method is used.
  • If an instance can be located with a discovery request.
  • If a database can be located with a discovery request.

Table 1 describes the configuration parameters used to control DB2 discovery behavior.


Table 4. Configuration parameters that control the behavior of DB2 discovery
ParameterValues/DefaultDescription
Client Instance
(DB2 Database Manager Configuration File)
discoverDISABLE, KNOWN, or SEARCHIdentifies the DB2 discovery action to be used by the client instance.
If this parameter is set to SEARCH, the client instance can issue search or known discovery requests. If set to KNOWN, the client instance can issue only known discovery requests. If set to DISABLE, the client instance cannot issue discover requests.
discover_instENABLE or DISABLE
Default: ENABLE
Specifies whether this instance can be detected by other DB2 discovery requests.
Server DAS Instance
(DAS Configuration File)
discoverDISABLE, KNOWN, or SEARCH
Default: SEARCH
Identifies the DB2 discovery action to be used by the client instance.
If this parameter is set to SEARCH, the server responds to search and known discovery requests. If set to KNOWN, the server will respond only to known discovery requests. If set to DISABLE, the server will not respond to discovery requests.
Server Instance
(DB2 Database Manager Configuration File)
discoverDISABLE, KNOWN, or SEARCH
Default: SEARCH
Identifies the DB2 discovery action to be used by the server instance.
If this parameter is set to SEARCH, the server instance can issue search or known discovery requests. If set to KNOWN, the server instance can issue only known discovery requests. If set to DISABLE, the server instance cannot issue discovery requests.
discover_instENABLE or DISABLE
Default: ENABLE
Identifies whether information about a particular instance found on a server will be included in the server's response to a discovery request.
If this parameter is set to ENABLE, the server will include information about the instance in its response to search and known discovery requests. If set to DISABLE, the server will not include information about the instance (and will not include information about any databases that come under the instance's control) in its response to discovery requests.
This parameter provides a way to hide an instance and all of its databases from DB2 discovery.
Server Database
(Database Configuration File)
discover_dbENABLE or DISABLE
Default: ENABLE
Identifies whether information about a particular database found on a server will be included in the server's response to a discovery request.
If this parameter is set to ENABLE, the server will include information about the database in its response to search and known discovery requests. If set to DISABLE, the server will not include information about the database in its response to discovery requests.
This parameter provides a way to hide an individual database from DB2 discovery.

At the server level, instance level, and database level, you can enable or disable DB2 discovery and control how discovery requests are initiated. You can also configure a server so DB2 discovery will not see one or more of its instances or databases when discovery requests are made. In Figure 1, you can see how configuration parameters controlling the behavior of DB2 discovery can be used to prevent it from seeing specific instances and databases stored on a server.


Figure 1. Example of how configuration parameters can affect DB2 discovery behavior
Example of how configuration parameters                         can affect DB2 discovery behavior

5 of 9 | Previous | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=842457
TutorialTitle=DB2 10.1 DBA for Linux, UNIX, and Windows certification exam 611 prep, Part 8: Connectivity and networking
publish-date=10252012
author1-email=dlhopes@us.ibm.com
author1-email-cc=