For update this information in the database manager following command is used:

db2 UPDATE DBM CFG USING SVCENAME db2icdb2

These tasks can also be performed using the DB2 Configuration Assistant utility. 

At the client, the database information is configured using either the 

CATALOG

command or using the Configuration Assistant. The databases are configured 

under a node, which describes the host information like protocol, port, etc. To 

configure a remote TCP/IP node following command is used:

db2 CATALOG TCPIP NODE node name REMOTE host name SERVER service name

The service name registered in the server or the port number can be specified in 

the SERVER option. To catalog a database under this node, the command used 

is:

db2 CATALOG DATABASE database name AS alias name AT NODE node name

When using the Configuration Assistant GUI tool to add a database connection, 

a database discovery can be started to find the desired database.

Note: 

DB2 Discovery method is enabled at the instance level using the 

DISCOVER_INST

 parameter, and at database level using 

DISCOVER_DB

parameter. 

Application access

When deploying applications with DB2 UDB different methods can be used:

Single tier

In this configuration the application and the database reside on the same 

system. In enterprise environments, it may be rare to see such a 

configuration, because remote access to a database server is typically 

required. Nonetheless, this is quite common for developing applications that 

can later be deployed transparently in a multi tier DB2 environment without 

any changes or batch applications.

Client/Server or 2 tier

The application and the database reside on separate systems. The machines 

where the application runs typically have a DB2 client installed, which 

communicates over the network to a database server. For the application, the 

physical location of the data is transparent. The application communicates 

with the DB2 client using a standard interface (for example, ODBC) and the 

DB2 client takes over the task of accessing the data over the network. In 

some cases, such as browser or Java based access, it is not necessary to 

have the DB2 client running on the same machine where the application 

executes. 

22 

MySQL to DB2 UDB Conversion Guide