To access a database, you must
first create a JDBC provider in the Integrated Solutions Console.
Before you begin
Before you begin, the following software should
be installed:
- WebSphere® Application Server
Network Deployment,
version 7.0.0.7
- One of the following supported databases:
- IBM® DB2® Enterprise
Server Edition,
version 9.5.0.4 or 9.7.0.1
- Oracle Database,
version 11.1.0.7 or 11.2.0.1
- JDBC JAR file or full database client for communicating with the
database server
- Diameter Enabler base
Before you begin, the
following steps should be completed:
- Started the deployment manager
- Started the node agents
- Created the database
- Created an authentication alias for the database
About this task
Complete the following steps
to create a JDBC provider:
- Log in to the Integrated Solutions Console:
- Open a browser and navigate to the following
URL: https://host_name:port/ibm/console.
Where:
- host_name is the fully qualified host name
of the server where the application or the network deployment manager
is deployed.
- port is the secured port used to access the
console. The default port is 9043.
Note: The default unsecured port is 9060.
If you use 9060, you must have "http" instead of "https" in the URL.
- Enter an administrator user ID and password. (Omit the password if security is
not enabled.)
- Click Log in.
- In the navigation pane, click .
- Select cell_name from
the Scope drop-down list.
- Click New.
- Create the JDBC provider:
- Select your database type from the drop-down list.
DB2
Oracle
- Select the Provider type for
your database:
DB2 Universal JDBC Driver Provider
Oracle JDBC Driver
- Select Connection pool data source for
the Implementation type.
- Click Next.
- For database client JAR files,
perform one of the following:
- If you have database client JAR files installed in the same
location on all of the federated nodes in your cell, enter that directory
location path, which is saved as a WebSphere variable.
- If you do not have database client JAR files in the same directory
location on all nodes in your cell, leave this field blank.
Note: - By leaving this field blank, you will need to create or modify
the WebSphere variables at the node level to represent the correct
path for database client JAR files for each node.
- In the case where the location is given here, then if it ever
requires updating, make sure that the DB2UNIVERSAL_JDBC_DRIVER_PATH
or ORACLE_JDBC_DRIVER_PATH variable is updated at both the cell and
each node scope from in the Integrated
Solutions Console.
Then click Next.
- Verify that all values are correct, and
click Finish.
- Click Save to
save changes to the master configuration.
- Click OK when
node synchronization has completed.