WebSphere variables define a parameter for the system.
To enable communication between the application server and the database,
you must create WebSphere variables to specify the path to the JAR
files on the database client.
Before you begin
Note: In the previous topic, Creating a JDBC provider,
you may have already entered the directory location path to these
files because they are in the same location on all of the federated
nodes in your cell. If the directory location path was entered, the
variable has already been created; skip this procedure and proceed
to the following topic, Defining the data source. In the future,
updates to the directory location path must be made to the variable
from both the cell scope and from each node's scope.
Before you begin, the following software
should be installed:
- A supported version of WebSphere® Application Server
Network Deployment
For a list of required WebSphere Application Server fixes,
refer to the readme file, WebSpheresoftwareForTelecomReadme.html,
on the QuickStart CD.
- One of the following supported databases:
IBM® DB2® Enterprise
Server Edition
Oracle Database
- JDBC JAR file or full database client for communicating with the
database server
Before you begin, the following
steps should be completed:
- Started the application server
- Created the database
- Created JDBC provider
About this task
After you have installed the database
client on the server where you installed
WebSphere Application Server,
you must create a WebSphere variable to enable communication between
the application server and the database server.
Important: Install the database
client in the same location on each physical server.