Configuring WebSphere Application Server to use DB2 remote database
 Technote (troubleshooting)
 
Problem(Abstract)
Unable to connect to remote DB2® database
 
Resolving the problem
WebSphere® Application Server connects to a DB2® database the same way, regardless of whether the database is local or remote to the Application Server. It is the responsibility of DB2 to route data to and from the database.
If the database is local, configure the db name, dbuser, and password in WebSphere Application Server. If the database is remote, use a database alias name, dbuser, and password.

The following two commands must be performed from the DB2 command prompt on the WebSphere Application Server for DB2 to find out where the remote database is:

db2 catalog tcpip node nodename remote ipaddress server port
db2 catalog db dbname as alias at node nodename

where:
nodename is anything, but must match for both commands.
ipaddress is a remote server IP address.
port is a DB2 listener port, usually 50000 (can be checked in the services file).
dbname is the name of database to access.
alias is whatever you like. This is the name you will configure in your WebSphere data source as the databaseName.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java 2 Connectivity (J2C)
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1053478
IBM Group: Software Group
Modified date: Oct 29, 2004