You can use the Oracle JDBC for OCI driver with Version 7.0 and later of the Application
Server.
About this task
To create a data source in the Application Server that takes advantage of the Oracle Call
Interface (OCI), or Oracle features that require OCI to be used, you must use the Oracle JDBC OCI
native libraries. Any type of Oracle JDBC provider can be configured with the Application Server to
use OCI.
Procedure
- From the administrative console, create the JDBC provider.
- Click Resources, expand JDBC, and click
JDBC Providers.
- Select the scope for the JDBC Provider. The scope can be set to a cell, node, or server level.
- Click New to create the JDBC Provider.
- Configure the settings for the JDBC provider. This provider can be used to create data sources that use either OCI or thin URLs. The type
that is used depends on what is specified in the URL. This provider cannot be used with class loader
isolation when used with OCI.
- Select Oracle for the database type on the Step 1: Create new JDBC
provider panel.
- Select an Oracle JDBC driver for the provider type on Step 1: Create new JDBC provider
panel.
- Select Connection pool data source or XA data
source for the implementation type on Step 1: Create new JDBC provider panel.
- Specify a name and, optionally, a description, for the JDBC provider.
- Click Next.
- Specify a directory location for the ojdbc6.jar or
ojdbc7.jar (if you are running Java 7 or later) Java archive (JAR) file on Step
2: Enter database specific properties for the data source panel.
最佳作法: An Application Server variable can be used in the class path.
For example,
you can use the variable ${ORACLE_JDBC_DRIVER_PATH} in the field for the class path but you must
define the variable ORACLE_JDBC_DRIVER_PATH to the Application Server. You can set the value of this
variable at this step to the directory where the ojdbc JAR is installed. Alternately, after creating
the provider, you can, at the appropriate scope level, define or change this variable in the
administrative console by clicking . Set its value to the directory where the ojdbc JAR file is installed.
For
example, the class path field could contain ${ORACLE_JDBC_DRIVER_PATH}/ojdbc6.jar
and the directory location field could contain
/root/InstantClient/12.1.0.1.0.
bprac
- Click Next.
- Review the configuration on the Summary panel and click Finish. If you need to make changes to the configuration, select the new configuration on the next
panel, make your changes, and click Apply.
- Create the data source in Application Server.
- Click Resources, expand JDBC, and click .
- Under Additional Properties, click .
- Specify the name for the data source on Step 1: Enter basic data source information
panel.
- Specify the JNDI name for the data source on Step 1: Enter basic data source information
panel.
- Click Next.
- Specify the URL of the database from which the data source obtains connections. Specify this
information on Step 2: Enter database specific properties for the data source panel.
For an OCI driver, one of these examples could be
used:
jdbc:oracle:oci:@//mySystem:1521/sample
jdbc:oracle:oci:@sample
- Select the name of the data store helper class that corresponds to the type of JDBC provider
that you configured. Select this information on Step 2: Enter database specific properties for the
data source panel.
- Click Next.
- Optional: Specify the values for the associated security aliases.
- Click Next.
- Review the configuration on the Summary panel and click Finish. If you need to make changes to the configuration, select the new configuration on the next
panel, make your changes, and click Apply.
- Save the configuration.
- Perform a test connection. If the test works, then the configuration is done. If the test
fails with linkage errors, proceed to the next step..
- Optional: Set the native library path on the JDBC Provider, set the OS environment variables, or set the
environment variables on the server.
- First, try setting the native library path on the JDBC provider and then perform a test
connection. To set the native library path:
- Edit the JDBC Provider
- Fill in the native library path with the path to the Oracle JDBC driver
native libraries. This might be the same path that you used for the class path.
最佳作法: An Application Server variable can be used in the native library path.
For
example, if the class path and the native library path are the same, you can use the variable that
was used for the class path or you can use a variable like ${ORACLE_HOME} in the field for the
native library path. You must then define the variable ORACLE_HOME to the Application Server. At
the appropriate scope level, define or change this variable in the administrative console by
clicking and set its value to the directory to where the Oracle native client libraries are
installed.
For example, the field could contain ${ORACLE_HOME}/lib if
lib is where the native libraries are installed.
bprac
- If there are still linkage failures, then the path to the Oracle native client libraries must
either be set in the OS environment that the WebSphere Application server is running in or be set in
the environment entries for the server. The environment variable to be set is specific to the platform type. These items may already
be set as part of the Oracle installation process.
- AIX: LIBPATH
- HP-UX: SHLIBPATH
- Linux/Solaris: LD_LIBRARY_PATH
- WINDOWS: PATH
- The TNS_ADMIN variable might need to be set to the path that contains files such as
tnsnames.ora or sglnet.ora. For example, if tnsnames.ora contains TNS services names that are used in
a URL such as jdbc:oracle:thin:@mydb.
- To set variables in the OS environment, follow the instructions for the platform. For example, for AIX, the following might be
used:
export LIBPATH=/InstantClient:$LIBPATH
export TNS_ADMIN=/InstantClient
- To set variables on the server, use environment entires. For example, using the administrative console:
- .
- Select Configuration tab.
- Under Server Infrastructure, expand Java and Process
Management.
- Select Process Definition and then under Additional
Properties, select Environment Entries.
- Add a name and value pair for each environment variable to be set.
- After setting the appropriate environment variables, try to test connection again.
- You will need to restart the server before using the data source in an application.
What to do next
Note the following items:
- The bit level of the Instant Client installed must match the bit level of the operating
system.
- The Instant Client selected must be the correct version for the platform it is installed on.
Instant Client for AIX5L can be used with AIX 5L or later.
- The ojdbc JAR file must be the correct version for the java version being used by WebSphere
Application Server. The ojdbc6.jar can be used with Java 6 or Java 7. The
ojdbc7.jar can only be used with Java 7.
- The ojdbc JAR file being used should be the one that was provided with the client that is being
used.