Administration Getting Started

Managing DB2 Server Instances Accessible To Remote Clients

If you will need to manage a remote database, this section shows you how to:

• Add a remote system
• Add the instance you want to work with for that system
• Add the database you want to work with under that instance

DB2 first checks in the node directory (which contains an entry for all servers to which a database client can connect and the communications protocol used in the connection) to see if the remote system is already known. If it is not, you need to perform the steps in this section if you want to work with a system, instance, or database on a remote system. Essentially, you set yourself up as a client to the remote system.

After you install DB2, you can use the Client Configuration Assistant to search the network for systems, instances, and databases and then choose to configure communications for them (catalog the instances and databases, which creates an entry for them in the node directory and database directory, respectively). When this is done, they will be displayed in the Control Center so that you can work with them. See the Quick Beginnings book for your platform for instructions on using the Client Configuration Assistant. However, if this has not already been done, you can follow the steps below.

You must first add the system (catalog it, which creates an entry for it in the node directory) so that its instances and databases can be made known. Next, you must add the instances and databases for the system (catalog them, which creates an entry for them in the node directory and database directory, respectively).

To add a remote system:

1. From the Control Center, click with mouse button 2 on the Systems object and select Add. The Add System window opens.

2. Enter the system name in the System name field.

   If the Discover configuration parameter for the instance is set to search and the discover comm configuration parameter is not blank, you can select Refresh to get a list of the remote systems. You can then select one of the systems from the list below the System name field.

3. Type the remote instance name in the Remote instance name field.

4. Select the type of operating system for the remote system from the Operating system list.

5. Select the protocol you want used for communications with the remote locations. For a local system, Local is automatically selected and is the only valid protocol. The possible protocols are:
   • APPC
   • IPX/SPX
   • NetBIOS
   • TCP/IP
   • Named pipe (Windows NT and Windows 95 operating systems only)

   Only the protocols that the computer is currently set up for appear in the listbox.

6. Enter the appropriate Protocol parameters.

7. Optional: Enter a comment to be associated with the system.

8. Select Apply to add the system to the node directory.

Next, add the instance you want to work with on that system:

1. From the Control Center, click with mouse button 2 on the Instances object belonging to the system you just added.

2. Select Add. The Add Instance window opens.

3. Enter the required values in the fields.

4. Click on the Refresh button to have a list of existing instances displayed.

5. Select the instance you want to work with.

6. Click on the Apply push button, then the Close push button.

Finally, add the database you want to work with under that instance:

1. From the Control Center, click with mouse button 2 on the Databases object.

2. Select Add. The Add Database window opens.

3. Enter the database name, type of communication protocol, and, optionally, an alias. An alias in this case is an alternative name used to identify a database.

4. Click on the Refresh button to have a list of existing databases displayed for that instance.

5. Select the database you want to work with.

6. Click on the Apply push button, then the Close push button.

[ DB2 List of Books | Search the DB2 Books ]