Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem: Installing/Configuring OAS 10.1.3.x to use Different Oracle JDBC Driver Versions
Symptoms:
Oracle Containers for J2EE - Version: 10.1.3.0.0 to 10.1.3.4.0 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
OAS 10.1.3.x comes with the 10.1.0.5 Oracle JDBC driver.
With the introduction of shared libraries, we can swap the Oracle JDBC driver version the container is using system wide or import the driver we wish to use at the application level.
Solution:
nstalling/Configuring OAS 10.1.3.x to use Different Oracle JDBC Driver Versions
Firstly, if we wish to use a newer version of the Oracle JDBC driver for all applications,
we can follow the note below to switch to say a 10.2.0.4 JDBC driver for all applications.
Note 420303.1 - How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container
So in affect, once complete, we will end up with 2 oracle.jdbc shared library driver versions as shown below:
oracle.jdbc - 10.1.0_2 (Default)
oracle.jdbc - 10.2.0.4
In the $ORACLE_HOME/j2ee/{container-name}/config directory, there is a config file called system-application.xml
which we can use to identify which driver we wish to use by default for all applications within that container.
The following shows that by default, we will use the 10.2.0.4 driver for oracle.jdbc shared library at a minimum.
This is an important concept here, as you can see that you can now control what the minimum version the container should use by default.
Lets say, we altered that file to the default settings as follows.
What would be the affect then, after having added the 10.2.0.4 oracle.jdbc shared library as we did above?
Your oracle.jdbc shared library will then use the latest available version of a shared library that it imports.
You may optionally specify a minimum or maximum version to import, but in the previous example we didn't,
so in that case it will then use 10.2.0.4 oracle.jdbc shared library by default.
So in affect, if we add a new oracle.jdbc shared library with the 10.2.0.4 Oracle JDBC driver which we did if we followed Note 420303.1,
then once complete, we would be using 10.2.0.4 JDBC driver for all applications whether we wanted to or not.
The problem here, is that your aim may have been to simply add the 10.2.0.4 oracle.jdbc shared library and only make it available to certain applications rather then all applications.
So how would we overcome this?
What we need to do here, is specify that by default, we want to use the original 10.1.0.5 oracle.jdbc shared library as follows.
We must do this because we have added a 10.2.0.4 version of oracle.jdbc , which in affect,
means we will use the latest available version unless we override it as shown below.
Note: Any changes you make to system-application.xml requires you to stop and start the container to pick up the change.
So with that in place we now have ensured that all applications are using the default JDBC driver for the container,
but finally we want to ensure that certain applications can use the 10.2.0.4 version which we do in an application
specific deployment descriptor known as orion-application.xml.
Here is an example below:
With this setup in place, you can ensure that by default the container is using the shipped oracle.jdbc shared library at all times,
and that only specific application's will use a later driver version where and when needed.
In order to determine what version of the Oracle JDBC driver your container is using, you can use Note 396187.1
which will ensure you have your system setup the way you want it to be setup for the shared library oracle.jdbc.
More Information
- Note 365120.1 JDBC Driver Support for Oracle Application Server
(at the bottom of the document, it confirms what is actually certified when updating the jdbc driver in a 10.1.3 home)
References:
Installing/Configuring OAS 10.1.3.x to use Different Oracle JDBC Driver Versions [ID 787689.1]
NOTE:420303.1 - How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container
NOTE:365120.1 - JDBC Driver Support for Oracle Application Server (Fusion Middleware)
Symptoms:
Oracle Containers for J2EE - Version: 10.1.3.0.0 to 10.1.3.4.0 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
OAS 10.1.3.x comes with the 10.1.0.5 Oracle JDBC driver.
With the introduction of shared libraries, we can swap the Oracle JDBC driver version the container is using system wide or import the driver we wish to use at the application level.
Solution:
nstalling/Configuring OAS 10.1.3.x to use Different Oracle JDBC Driver Versions
Firstly, if we wish to use a newer version of the Oracle JDBC driver for all applications,
we can follow the note below to switch to say a 10.2.0.4 JDBC driver for all applications.
Note 420303.1 - How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container
So in affect, once complete, we will end up with 2 oracle.jdbc shared library driver versions as shown below:
oracle.jdbc - 10.1.0_2 (Default)
oracle.jdbc - 10.2.0.4
In the $ORACLE_HOME/j2ee/{container-name}/config directory, there is a config file called system-application.xml
which we can use to identify which driver we wish to use by default for all applications within that container.
The following shows that by default, we will use the 10.2.0.4 driver for oracle.jdbc shared library at a minimum.
This is an important concept here, as you can see that you can now control what the minimum version the container should use by default.
Lets say, we altered that file to the default settings as follows.
What would be the affect then, after having added the 10.2.0.4 oracle.jdbc shared library as we did above?
Your oracle.jdbc shared library will then use the latest available version of a shared library that it imports.
You may optionally specify a minimum or maximum version to import, but in the previous example we didn't,
so in that case it will then use 10.2.0.4 oracle.jdbc shared library by default.
So in affect, if we add a new oracle.jdbc shared library with the 10.2.0.4 Oracle JDBC driver which we did if we followed Note 420303.1,
then once complete, we would be using 10.2.0.4 JDBC driver for all applications whether we wanted to or not.
The problem here, is that your aim may have been to simply add the 10.2.0.4 oracle.jdbc shared library and only make it available to certain applications rather then all applications.
So how would we overcome this?
What we need to do here, is specify that by default, we want to use the original 10.1.0.5 oracle.jdbc shared library as follows.
We must do this because we have added a 10.2.0.4 version of oracle.jdbc , which in affect,
means we will use the latest available version unless we override it as shown below.
Note: Any changes you make to system-application.xml requires you to stop and start the container to pick up the change.
So with that in place we now have ensured that all applications are using the default JDBC driver for the container,
but finally we want to ensure that certain applications can use the 10.2.0.4 version which we do in an application
specific deployment descriptor known as orion-application.xml.
Here is an example below:
With this setup in place, you can ensure that by default the container is using the shipped oracle.jdbc shared library at all times,
and that only specific application's will use a later driver version where and when needed.
In order to determine what version of the Oracle JDBC driver your container is using, you can use Note 396187.1
which will ensure you have your system setup the way you want it to be setup for the shared library oracle.jdbc.
More Information
- Note 365120.1 JDBC Driver Support for Oracle Application Server
(at the bottom of the document, it confirms what is actually certified when updating the jdbc driver in a 10.1.3 home)
References:
Installing/Configuring OAS 10.1.3.x to use Different Oracle JDBC Driver Versions [ID 787689.1]
NOTE:420303.1 - How to Use The Latest Thin JDBC Driver Across All Applications For a 10.1.3.x OAS Container
NOTE:365120.1 - JDBC Driver Support for Oracle Application Server (Fusion Middleware)
1 comment:
Pornography is perhaps all right if you are a adult - just in moderation.
There so many gorgeous babes to decide on from that are online whatsoever
hours through the day, that you may have the ability to have a look at
horny sluts waking up to any or all forms of
naughty action whenever you want. While the normal webcam model earns
about $6,500 per month, they can do greater by creating a recognised persona that literally brings in multiple clients at once and keeps them there, even
while drawing in ever more observers.
Look into my web-site :: xxx porn
My website - http://www.adultstreamtube.com
Post a Comment