To complete the steps in this section, you must be logged on to the local
system as a user with System Administrative (SYSADM) authority on the
You can configure database connections through the Add Database SmartGuide, by:
Each of these is covered in more detail in the material that
You can use either a Server profile or a Client profile to configure database connections on a client.
Server profiles can be generated for a DB2 server. They contain information about instances on the server system, and databases within each instance. The information for each instance includes the protocol information required to set up a client to connect to databases in that instance.
To generate server profiles, use the Generate Access Profile function provided in the Control Center. When a profile is generated for a DB2 server system, it includes server instances that have the discover_inst configuration parameter and databases with the discover_db configuration parameter set to ENABLE. The discover parameter, for the Administration Server, must be set to either SEARCH or KNOWN to generate a profile for a server system.
For information on setting the discover_inst, discover_db and discover configuration parameters, see "Setting Discovery Parameters".
To generate an access profile, perform the following steps:
To process a server profile and add its databases to the client's connection configuration list, use the Client Configuration Assistant's Import or Add functions. Using the Add function is the preferred method.
To add a database using the Add function:
Information in Client profiles can be added to another client through the following:
|Note:||This scenario assumes that the database connections configured on one client will be exported and used to set up one or more additional clients.|
Client profiles are generated from clients using the Export function of the CCA. Use the export function to copy the database information used by one client to other clients.
The information contained in a client profile is determined during the export process. Depending on the settings chosen, it can contain the existing client's:
Export can be used to generate a customized profile that can be imported on another client to set it up initially, or to update it.
To export a profile from the client, configure the client for communications and do the following:
The Export function of the CCA is only available when the CCA is started in
administrator mode. The CCA can be started permanently in administrator
mode by modifying the Client Configuration Assistant icon to add
the parameter admin to the startup of the CCA, or by issuing the
db2cca admin command.
To customize settings, click on the appropriate Customize push button. The settings that you customize will only affect the profile to be exported, no changes will be made to your workstation. For more information, click on the Help push button.
The Import function can be used to easily set up new client systems. The Import function works as follows:
Perform these steps at the client that you want to set up. You can use this process to initially set up a new client, or to update an existing one.
||If databases are contained in the client profile that you are importing, and you select to import them, the Add Database SmartGuide starts to allow you to selectively import the databases you want to connect to.|
Instead of entering protocol information to make a
connection to remote database servers, you can use the CCA to find all the
databases on your local network by following these steps:
The following scenario assumes that messages used by the Search
method of discovery are not filtered by your network, and that the
installation defaults on the client and the server have not been
changed. In order to run the following scenario, you must ensure that
the discover parameter in the database manager configuration file on
the client, and the Administration Server configuration file on the server are
set to Search.
Searching the network can be customized to meet the needs of individual organizations. The material that follows provides details on this customization. Refer to the Administration Guide for more information on individual configuration parameters and profile registry values.
Network searching uses a DB2 facility called Discovery to obtain information from DB2 servers. This information is used to configure clients for database connections.
|Note:||Discovery cannot find information about pre-Version 5 DB2 systems.|
Two discovery methods are available for searching the network:
Known discovery allows you to discover instances and databases on systems that are known to your client, and add new systems so that their instances and databases can be discovered.
Click on the [+] sign beside the Known Systems icon to get a list of known DB2 server systems. Click on the [+] sign beside the system to get a list of the instances and databases on it. Select the database that you want to add and complete the other panels in the Add Database SmartGuide.
Initially, the list of systems will be blank; however, if you are running the CCA on the server, an entry for the local server will be shown. Add systems to the list by clicking on the Add System push button. To use this option you must know a few details about the Administration Server on the DB2 system to be searched:
The Administration Server will listen for KNOWN discovery requests, from clients, on the protocols specified by the db2comm registry value in the Administration Server.
This mode provides all of the facilities of Known discovery, and adds the option to allow your local network to be searched for DB2 servers.
Searching does not require information about the Administration Server. When you click on the [+] sign beside the Other Systems (Search the network) icon, a list of DB2 server systems is displayed. Click on the [+] beside the system to get a list of the instances and databases on it. Select the database that you want to add and complete the other panels in the Add Database SmartGuide.
Search may appear to be a simpler discovery method.
However, in larger networks, network routers and bridges can filter the
messages search uses to find DB2 servers on the network, resulting in an
incomplete or even empty list. In this case, use the Add
System method; its messages are not filtered by routers and
bridges. If in doubt, contact your network administrator for
To have the server support Known discovery, set the discover parameter in the Administration Server to KNOWN. To have it support Search discovery, set this parameter to SEARCH. To prevent discovery of the server, and all of its instances and databases, set discover to DISABLE.
On the client, enabling discovery is also done using the discover parameter; however, in this case, the discover parameter is set in the client instance (or a server acting as a client) as follows:
Administration Servers configured with the discover parameter set
to KNOWN will not respond to search requests from clients. It is
important that you consider this when changing the discover
Search discovery requires that the configuration parameter discover_comm be set on both the server (in the Administration Server's configuration file) and the client (in the database manager configuration file).
The discover_comm parameter is used to control the communication protocols that the server will listen on for search requests from clients, and that clients will use to send out search requests. The discover_comm parameter can be set to TCP/IP; this is the only protocol supported by SEARCH discovery.
On the Administration Server, the values specified for
discover_comm must be equal to, or a subset of, the values set for
To avoid problems with the Control Center and the Client Configuration
Assistant, ensure that DB2COMM is set in the DB2 registry. It
is not recommended that you use any other mechanism to set the
On the server, the discover_comm parameter is set in the Administration Server. On the client (or a server acting as a client), discover_comm is set in the instance.
|Note:||When using discovery search mode, at least one protocol specified by the discover_comm parameter on the client must match those specified by discover_comm on the Administration Server. If there is no match, the server will not respond to the client's requests.|
Check the settings for the db2comm registry value by issuing the
db2set DB2COMM command. For more information, see Chapter 21. "Controlling Your DB2 Environment".
In addition, there are two DB2 profile registry values that can be used to tune search discovery on the client: db2discoverytime and db2nbdiscoverrcvbufs. The default values should be suitable in most cases. For more information, refer to the Administration Guide.
You may have multiple instances, and multiple databases within these instances, on a server. You may want to hide some of these from the discovery process.
To allow clients to discover server instances on a system, set the discover_inst database manager configuration parameter in each server instance on the system to ENABLE (this is the default value). Set this parameter to DISABLE to hide this instance and its databases from discovery.
To allow a database to be discovered from a client, set the discover_db database configuration parameter to ENABLE (this is the default value). Set this parameter to DISABLE to hide the database from discovery.
Update the Administration Server's configuration file, in the command line processor, as follows:
update admin cfg using discover [ DISABLE | KNOWN | SEARCH ] update admin cfg using discover_comm [ TCPIP ] db2admin stop db2admin start
|Note:||Search Discovery will only operate on TCP/IP and NetBIOS.|
If the discover_comm includes NETBIOS, you must ensure
that the Workstation name (nname) configuration parameter is set for
the both the client and the Administration Server. Also, you must
ensure that the db2nbadapters registry value is set to the Adapter
number that you want to use. For more information, refer to the Administration Guide.
This specifies that the searched discovery should wait 35 seconds for a response from servers.
This specifies the number of NetBIOS buffers that will be allocated for concurrent response messages from discovered servers.
Manually configuring a database connection requires you to know:
With this information, the SmartGuide will guide you through the steps necessary to add the database connection.
[ DB2 List of Books | Search the DB2 Books ]