Databases Reference
In-Depth Information
When this option is disabled, the application-specific data sources are no longer
packaged and deployed with the application. Instead, the application is configured
to use a global data source named as follows:
jdbc/<connectionname>DS
Using the JNDI, look for the following:
java:comp/env/jdbc/<connectionname>DS
Here,
<connectionname>
is the name of the database connection we specified when
we created our ADF-Business Component.
In our case, we specified a name of
obay
, so all we need to do now is to configure a
data source on WebLogic with the name
jdbc/obayDS
. We actually do this as part
of the installation process of the oBay application, so please refer to the installation
guide for details on how to do this.
You may find that when you disable this option, you are no longer able
to run the ListingSDO Application Module in JDeveloper, in which
case, you need to re-enable it for the purpose of testing.
Determining the SDO registry key
At runtime, before the SOA infrastructure can invoke the SDO via RMI, it must first
look for it using a registry key. The registry key is generated automatically and has
the following structure:
<ApplicationName>_JBOServiceRegistry
Here,
<ApplicationName>
is specified in the EAR deployment profile of the
ADF-BC application.
To set the application name, reopen the
Application Properties
window
and select
Deployment
from the Navigation Tree (as we did in the previous
section). From the deployment profiles, select the EAR File deployment profile
(
(ListingBC_ListingBCProfile
in the preceding screenshot) and click
Edit
.
