|
| Problem | Unable to connect to remote DB2® database | | | | Solution | 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 nodenameremote ipaddressserver port db2 catalog db dbnameas aliasat 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. |
| | | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Java 2 Connectivity (J2C) Operating system(s): Multi-Platform Software version: 3.5, 4.0, 5.0, 5.1, 6.0 Software edition: Edition Independent Reference #: 1053478 IBM Group: Software Group Modified date: 2004-10-29
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|