Installation and Configuration Supplement

Configuring Named Pipes on the Client

This section assumes that Named Pipes is functional on the client and server workstations. See Software Requirements for the communication protocol requirements for your platform. See Possible Client-to-Server Connectivity Scenarios for the supported communication protocols for your particular client and server.

To set up a client to use Named Pipe communications, perform the following steps:

step  1.	Identify and record parameter values.
step  2.	Configure the client: Catalog the Named Pipes node. Catalog the database.
step  3.	Test the connection between the client and server.

Step 1. Identify and Record Parameter Values

As you proceed through the configuration steps, complete the Your Value column in the following table. You can fill in some of the values before you start configuring this protocol.

Table 6. Named Pipe Values Required at the Client

Parameter	Description	Sample Value	Your Value
Computer name (computer_name)	The computer name of the server machine. On the server machine, to locate the value for this parameter, click on Start and select Settings->Control Panel. Double-click on the Network folder and select the Identification tab. Record the computer name.	server1
Instance name (instance_name)	The name of the instance on the server to which you are connecting.	db2
Node name (node_name)	A local alias, or nickname, that describes the node to which you are trying to connect. You can choose any name you want, however, all node name values within your local node directory must be unique.	db2node

Step 2. Configure the Client

The following steps configure this protocol on the client. Replace the sample values with your worksheet values.

A. Catalog the Named Pipes Node

You must add an entry to the client's node directory to describe the remote node. This entry specifies the chosen alias (node_name), the server's Computer name (computer_name), and the Instance name (instance_name) that the client will use to access the remote server.

To catalog the Named Pipes node, perform the following steps:

step  1.

Log on to the system with a valid DB2 user ID. For more information, see Appendix G. Naming Rules. If you are adding a database to a system that has a DB2 or DB2 Connect server product installed, log on to this system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority on the instance. For more information, see Working with the System Administrative Group. This restriction is controlled by the catalog_noauth database manager configuration parameter. For more information, refer to the Administration Guide.

step  2.

Catalog the node by entering the following commands: catalog npipe node node_name remote computer_name instance instance_name terminate For example, to catalog a remote node called db2node, which is located on the server called server1, in the db2 instance, use: catalog npipe node db2node remote server1 instance db2 terminate

If you need to change values that were set with the catalog node command, perform the following steps: step  1. Run the uncatalog node command in the command line processor as follows: uncatalog node node_name step  2. Recatalog the node with the values that you want to use.

B. Catalog the Database

Before a client application can access a remote database, the database must be cataloged on the server node and on any client nodes that will connect to it. When you create a database, it is automatically cataloged on the server with the database alias (database_alias) the same as the database name (database_name). The information in the database directory, along with the information in the node directory, is used on the client to establish a connection to the remote database.

To catalog a database on the client, perform the following steps:

step  1.	Log on to the system with a valid DB2 user ID. For more information, see Appendix G. Naming Rules. If you are adding a database to a system that has a DB2 or DB2 Connect server product installed, log on to this system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority on the instance. For more information, see Working with the System Administrative Group. This restriction is controlled by the catalog_noauth database manager configuration parameter. For more information, refer to the Administration Guide.
step  2.	Fill in the Your Value column in the following worksheet. Table 7. Worksheet: Parameter Values for Cataloging Databases Parameter Description Sample Value Your Value Database name (database_name) The database alias (database_alias) of the remote database. When you create a database, it is automatically cataloged on the server with the database alias (database_alias) the same as the database name (database_name). sample   Database alias (database_alias) An arbitrary local nickname for the remote database, on the client. If you do not provide one, the default is the same as the database name (database_name). This is the name that you use when connecting to a database from a client. tor1   Node name (node_name) The name of the node directory entry that describes where the database resides. Use the same value for node name (node_name) that you used to catalog the node in the previous step. db2node
step  3.	Catalog the database by entering the following commands: catalog database database_name as database_alias at node node_name terminate For example, to catalog a remote database called sample so that it has the alias tor1, on the node db2node, enter the following commands: catalog database sample as tor1 at node db2node terminate If you need to change values that were set with the catalog database command, perform the following steps: step  a. Run the uncatalog database command as follows: uncatalog database database_alias step  b. Recatalog the database with the value that you want to use.

Step 3. Test the Client-to-Server Connection

When you have finished configuring the client for communications, perform the following steps to test the connection:

You will need to connect to a remote database to test the connection.

step  1.	Start the database manager by entering the db2start command on the server (if it was not automatically started at boot time).
step  2.	Enter the following command to connect the client to the remote database: connect to database_alias user userid using password

You are now ready to start using DB2. For more advanced topics, refer to the Administration Guide and the Installation and Configuration Supplement.

Troubleshooting the Client-to-Server Connection

If the connection fails, check the following items:

At the server:

__  1.	The db2comm registry value includes the value npipe. Check the settings for the db2comm registry value by entering the db2set DB2COMM command. For more information, refer to the Administration Guide.
__  2.	The security service was started. Enter the net start db2ntsecserver command (for Windows NT servers only).
__  3.	The database was created and cataloged properly.
__  4.	The database manager was stopped and started again (enter the db2stop and db2start commands on the server).

If there are problems starting a protocol's connection managers, a warning message appears and the error messages are logged in the db2diag.log file. For more information on the db2diag.log file, refer to the Troubleshooting Guide.

At the client:

__  1.	The node was cataloged with the correct computer name (computer_name) and instance name (instance_name) of the server.
__  2.	The node name (node_name) that was specified in the database directory points to the correct entry in the node directory.
__  3.	The database was cataloged properly, using the server's database alias (database_alias) that was cataloged when the database was created on the server, as the database name (database_name) on the client.

If the connection still fails after you verify these items, refer to the Troubleshooting Guide.

[ DB2 List of Books | Search the DB2 Books ]