OIM 9.1.0.2 - Weblogic JDBC Multi Data Sources for Oracle RAC

Does OIM OIM 9.1.0.2 BP07 support Weblogic JDBC Multi Data Sources (Services>JDBC>Multi Data Sources) for Oracle RAC instead of inserting the "Oracle RAC JDBC URL" on JDBC Data Sources for xlDS and xlXADS (Services>JDBC>Data Sources> xlDS|xlXADS > Connection Poll> URL) ?
If yes, is there are any other modifications that need to be made on OIM, or just changing the data sources?

Yes, it's supported. You install against one instance directly of the Rac Server. Then you update the config.xml file and the jdbc resource in your weblogic server with the full rac address. It is documented for installation against RAC. http://docs.oracle.com/cd/E14049_01/doc.9101/e14047/database.htm#insertedID2
-Kevin

Similar Messages

Error when deploying JDBC file data source for J2EE agent in weblogic

Hi ODI experts!
we're using ODI 11g and we've installed J2EE agents on weblogic. We need to configure a connection pool within weblogic for a file data source. Thus, we've added snpsFile.jar (that was shipped with ODI 10g...) to the weblogic config so that we can configure a JDBC connection to file.
As we validate the config, an error occurs (see below):
Obviously, driver is found but cannot be deployed.
####<4 août 2011 09 h 39 CEST> <Error> <Deployer> <ppdlodi001> <SRVPPDODI_001> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <c53bfd6260db74bb:-485a441a:13193b42397:-7ffc-0000000000000027> <1312443551325> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1312443550020' for task 'weblogic.deploy.configChangeTask.6'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:218)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallbackDeliverer.java:41)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceivers(AwaitingContextUpdateCompletion.java:164)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuccess(AwaitingContextUpdateCompletion.java:66)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(AwaitingContextUpdateCompletion.java:32)
at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService.java:225)
at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:190)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: weblogic.common.ResourceException: com.sunopsis.jdbc.driver.file.a.i
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:263)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1193)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1117)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:244)
at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1110)
at weblogic.jdbc.common.internal.ConnectionPool.start(ConnectionPool.java:147)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:386)
at weblogic.jdbc.common.internal.ConnectionPoolManager.createAndStartPool(ConnectionPoolManager.java:326)
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:254)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:508)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1223)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:43)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:218)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.prepare(DeploymentReceiverCallbackDeliverer.java:41)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.callDeploymentReceivers(AwaitingContextUpdateCompletion.java:164)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.handleContextUpdateSuccess(AwaitingContextUpdateCompletion.java:66)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingContextUpdateCompletion.contextUpdated(AwaitingContextUpdateCompletion.java:32)
at weblogic.deploy.service.internal.targetserver.TargetDeploymentService.notifyContextUpdated(TargetDeploymentService.java:225)
at weblogic.deploy.service.internal.DeploymentService$1.run(DeploymentService.java:190)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks in advance for your help.
Fredd.

Hi!
Some information: I found this website [http://gerardnico.com/doc/odi/webhelp/en/refmanual/connexion/jdbcdriversample.htm] explaining that the 'old' snpsFile.jar driver was deprecated and that a new one was existing... but I can't find it anywhere!
My questions are:
- Can the problem (original problem. See initial post) be due to driver version?
- Does someone know where to find this 'new' driver?
Thanks for your help.
Fredd.
Edited by: fredd2 on Aug 5, 2011 10:04 AM
Edited by: fredd2 on Aug 5, 2011 10:07 AM

Problem setting up Weblogic's data source for oracle

          Hi!
          I am trying to setup XA DataSource Pool for Oracle using Weblogic's driver. App-Server
          throws exception during startup.
          config.xml setting are appended with this posting.
          Can somebody help me identifying the problem?
          Thanks,
          Vinay
          <JDBCConnectionPool
          Name="WL_XA_1_Pool"
          Targets="examplesServer"
          CapacityIncrement="1"
          DriverName="weblogic.jdbc.oci.xa.XADataSource"
          InitialCapacity="1"
          JDBCXADebugLevel="1"
          MaxCapacity="5"
          Properties="user=vinay;password=vinay;dataSourceName=WL_XA_1_Pool;serverName=pqasun1"
          RefreshMinutes="0"
          ShrinkPeriodMinutes="15"
          ShrinkingEnabled="true"
          TestConnectionsOnRelease="false"
          TestConnectionsOnReserve="false"
          URL="jdbc:oracle:oci8:@PlatformTest"
          />
          [error_wl2.txt]


          Hi Dinu,
          Silversword is our upcoming maintenance release for WLS 6.0, and
          should be available in June timeframe.
          If you are only using 1 database instance, you can use Oracle's
          driver in non-XA mode in distributed transactions. Please refer
          to "Configuring non-XA JDBC drivers" section for details: http://e-docs.bea.com/wls/docs60/adminguide/managetx.html#1045803.
          -- Priscilla Fung, BEA Systems, Inc.
          "Dinu Ramanthara" <[email protected]> wrote:
          >
          >Hi,
          > What is Silversword?
          >
          > I need to use Oracle's Driver as I have to use Oracle
          >AQ and Oracle
          >AQ doesn't seem to work with jDriver. All my database
          >activity,
          >through AQ as well as through JDBC are restricted to the
          >same Oracle
          >instance. Given that what are my options? Should I use
          >Oracle 8.1.6
          >drivers or should I use 8.1.7 drivers.
          >
          >Is there a document/sample code illustrating what need
          >to be done
          >to bind Oracle's XADataSource to the JNDI tree.
          >
          >Regards,
          >Dinu
          >"Priscilla Fung" <[email protected]> wrote:
          >>
          >>Hi Vinay,
          >>
          >>A couple of things to note. Oracle 8.1.6's driver has
          >>a bug that
          >>does not accept foreign Xid, and thus cannot be used
          >with
          >>any 3rd
          >>party vendor's Tranaction Manager, including WLS. Oracle
          >>8.1.7's
          >>driver has fixed this problem, but they have threading
          >>issues.
          >> We have worked around the threading issues in Silversword,
          >>but
          >>not in WLS 6.0 release. For now, the only Oracle XA
          >driver
          >>we
          >>recommend is Weblogic's jDriver for Oracle.
          >>
          >>-- Priscilla Fung, BEA Systems, Inc.
          >>
          >>
          >>"Vinay" <[email protected]> wrote:
          >>>
          >>>
          >>>
          >>>
          >>>Hi!
          >>>
          >>>I am trying to setup XA DataSource Pool for Oracle using
          >>>Weblogic's driver. App-Server
          >>>throws exception during startup.
          >>>config.xml setting are appended with this posting.
          >>>
          >>>Can somebody help me identifying the problem?
          >>>
          >>>Thanks,
          >>>
          >>>Vinay
          >>>
          >>>
          >>>
          >>>
          >>> <JDBCConnectionPool
          >>> Name="WL_XA_1_Pool"
          >>> Targets="examplesServer"
          >>> CapacityIncrement="1"
          >>> DriverName="weblogic.jdbc.oci.xa.XADataSource"
          >>> InitialCapacity="1"
          >>> JDBCXADebugLevel="1"
          >>> MaxCapacity="5"
          >>> Properties="user=vinay;password=vinay;dataSourceName=WL_XA_1_Pool;serverName=pqasun1"
          >>> RefreshMinutes="0"
          >>> ShrinkPeriodMinutes="15"
          >>> ShrinkingEnabled="true"
          >>> TestConnectionsOnRelease="false"
          >>> TestConnectionsOnReserve="false"
          >>> URL="jdbc:oracle:oci8:@PlatformTest"
          >>> />
          >>>
          >>
          >

BPM and multi data sources for users??

Hi all
can BPM read users from more than Data source?
my case is i want to create from BPM Admin Center a Directory Service(or more than one) , so i can read users and groups from ldap AD and DataBase ....or from 2 ldaps
Thanks

Federated directory support was added in 10gR3. This is done at the web application level, such as the workspace and allows the workspace to connect to multiple directories and provide a consolidated interface for users. This is configured through the workspace.properties file but I am not sure how much documentation exists.

Multi data source and global transactions

hi
i am working on JDBC multidata source connectivity.... to resolve one error of "lock in doubt held "
was searching through oracle sites got some recommendation as
**Disable server side load balancing for each of the pools. This can be done by setting the INSTANCE_NAME attribute in your JDBC connect descriptor aliases.**
**For example:**
**jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=MYDBHOST1)(PORT=1522)))(CONNECT_DATA=(SERVICE_NAME=MYDB)(INSTANCE_NAME=MYDB1)))**
**If you miss the INSTANCE_NAME attribute in your JDBC connect descriptor, the Oracle TNS Listener could still redirect you to some other instance depending on the load on the instance in question.**
now i m unable to understand which data sources is to be updated with this URL multi data source or the target data sources
can some body give me some clue........

Every datasource in a MultiDataSource must have a URL that ensures that every connection
in a given DataSource is always, only to one specific and unchanging RAC node.

Urgent help: how to create data source for Weblogic RMI driver

Hi,
Please let me how to create data source for Weblogic RMI driver using Administrator
console.
I understand that the following steps are required:
1.Create connection pool for the RMI driver by specfiying URL as
jdbc:weblogic:rmi and Driver as weblogic.jdbc.rmi.Driver. Now
comes the problem.. what do put in properties text area? I am
talking about key/value pairs required?
2. Having done step 1 ( which I was not able to do) , create a new DataSource
mapping to the connection pool created from step 1.
How to accomplish step 1 ? I want to finally connect to Oracle
database. Please help me.
pradeep bhat

DataSource will internally do that for you (It will use RMI internaly) . You
dont have to worry about the details of using RMI driver. Thats what is a
DataSource is for.
sree
"pradeep bhat" <[email protected]> wrote in message
news:[email protected]...
Hi Sree,
What u have written is abt configuting Datasource for type 2 and
4 drivers.
But I want to know how to create data source for RMI driver. If
I map this datasource to connection pool that is created for
type 2 or 4 drivers, i don't understand why RMI drivers are
required in first place. If i do map the data source to connection pool
created
for type 2 or 4 drivers then where i
would not have used the URL as jdbc:weblogic:rmi and Driver as
weblogic.jdbc.rmi.Driver.
Hope u will help me.
pradeep bhat
"Sree Bodapati" <[email protected]> wrote:
Hi Pradeep
To create a connection pool you have to use a database driver not RMI
driver. So use a thin driver or the WebLogic jDriver for Oracle to setup
your connection pool. Once the connection pool is created you can create
a
DataSource and use this datasource to connect to the database.
The RMI driver can be used to get connections from the database via the
connection pool and in that case you dont need a datasource. Recommended
approach is to use a DataSource.
hth
sree
"PRADEEP BHAT" <[email protected]> wrote in message
news:[email protected]...
Hi,
Please let me how to create data source for Weblogic RMI driver using
Administrator
console.
I understand that the following steps are required:
1.Create connection pool for the RMI driver by specfiying URL as
jdbc:weblogic:rmi and Driver as weblogic.jdbc.rmi.Driver. Now
comes the problem.. what do put in properties text area? I am
talking about key/value pairs required?
2. Having done step 1 ( which I was not able to do) , create a new
DataSource
mapping to the connection pool created from step 1.
How to accomplish step 1 ? I want to finally connect to Oracle
database. Please help me.
pradeep bhat

Urgent help: how to create data source for Weblogic T3 driver

Hi,
Please let me how to create data source for Weblogic T3 driver
using Administrator console.
I understand that the following steps are required:
1.Create connection pool for the RMI driver by specfiying URL
as jdbc:weblogic:rmi and Driver as weblogic.jdbc.rmi.Driver.
Now comes the problem.. what do put in properties text area?
I am talking about key/value pairs required?
2. Having done step 1 ( which I was not able to do) , create a
new DataSource mapping to the connection pool created from
step 1.
How to accomplish step 1 ? I want to finally connect to Oracle database. Please
help me.
pradeep bhat

Hi,
Please let me how to create data source for Weblogic T3 driver
using Administrator console.
I understand that the following steps are required:
1.Create connection pool for the RMI driver by specfiying URL
as jdbc:weblogic:rmi and Driver as weblogic.jdbc.rmi.Driver.
Now comes the problem.. what do put in properties text area?
I am talking about key/value pairs required?
2. Having done step 1 ( which I was not able to do) , create a
new DataSource mapping to the connection pool created from
step 1.
How to accomplish step 1 ? I want to finally connect to Oracle database. Please
help me.
pradeep bhat

How to set JDBC Data Sources in Oracle MapViewer for Oracle database 12c Release 1 (12.1.0.1)

How to set JDBC Data Sources in Oracle MapViewer for Oracle database 12c Release 1 (12.1.0.1)?
The following is my configuration in the conf\mapViewerConfig.xml:
<map_data_source name="mvdemo12"
jdbc_host="127.0.0.1"
jdbc_sid="orcl12c1"
jdbc_port="1522"
jdbc_user="mvdemo"
jdbc_password="7OVl2rJ+hOYxG5T3vKJQb+hW4NPgy9EN"
jdbc_mode="thin"
number_of_mappers="3"
allow_jdbc_theme_based_foi="true"
editable="true"/>

But it does not work.
After use "sqlplus mvdemo/[email protected]:1522/pdborcl", it connected to the Oracle database 12c.
Does anyone know it?
Thanks,

For 11.1.1.7.1 use the syntax for jdbc_sid, i.e.
//mypdb1.foo.com as described in the README,
- MapViewer native (non-container) data sources can now use database service name in place of SID. To supply a db service name, you will use the same jdbc_sid attribute, but specify the service name with double slashes in front, such as follows:
<map_data_source name="myds"
    jdbc_host="foo.com"
    jdbc_sid="//mypdb1.foo.com"
    jdbc_port="1522"
/>
For 11.1.1.7.0 use a container_ds instead.
i.e. instead of using
<map_data_source name="my_12c_test"
                   jdbc_host="mydbinstance"
                   jdbc_sid="pdborcl12c"
                   jdbc_port="1522"
                   jdbc_user="mytestuser"
                   jdbc_password="m2E7T48U3LfRjKwR0YFETQcjNb4gCMLG8/X0KWjO00Q="
                   jdbc_mode="thin"
                   number_of_mappers="6"
                   allow_jdbc_theme_based_foi="false"
                   editable="false"
   />
use
<map_data_source name="my_12c_test"
                   container_ds="jdbc/db12c"
                   number_of_mappers="6"
                   allow_jdbc_theme_based_foi="false"
                   editable="false"
   />
In my case the Glassfish 3.1.2.2 JDBC connection pool definition was
Property
url jdbc:oracle:thin:@mydbinstance:1522/pdborcl12c.rest_of.service.name
Uncheck the Wrap JDBC Objects option in Advanced panel, i.e. the Edit JDBC Connection Pool Advanced properties page.
Add a JDBC resource for that newly created pool
Use that in mapviewerconfig.xml as above

Help required on jdbc 2.0 driver for oracle 8.0.4

Hi all,
I wanted to know whether any oracle/Third party jdbc 2.0 driver is available to connect to oracle 8.0.4 enterprise server.
Any help would be kindly appreciated....
Regards,
Sudhakar

Ravindra Rao (guest) wrote:
: I'm looking for a Type 4 JDBC 2.0 driver for Oracle 8.0.4. Does
: Oracle provide one. I have looked at the downloads area but was
: not able to locate one.
: Any pointers?
: Ravindra Rao
: [email protected]
The only oracle JDBC driver that can run with JDK 1.2.x is in the
OTN download area and is named "816SDK for JDK 1.2"
it will work with the JDK 1.2.X using the JDBC 1.22 spec from JDK
1.1.X.
IT DOES NOT PROVIDE THE FULL JDBC 2.0 FEATURES/ FUNCTIONALITY
THAT ARE INCLUDED IN THE JDK 1.2.X CLASSES.
you're using a jdk 1.2.x/jdbc 2.0 feature -- which is anticipated
to be included in the 816 driver later this year -- it's not in
the "816SDK" JDBC driver you're using now..
816SDK can be thought of as stepping stone between 815 using jdk
1.1.x and 816 supporting jdk 1.1.x and 1.2.x.
i think of it as "8.1.5 and a half" to avoid the naming confusion
between "816sdk" and "816" .
SEE the following FAQ link for additional details :
http://technet.oracle.com/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm
null

Multi Data Source, Fail Over, Read-Only detected as unavailable

We are using WLS 10.3.6.0 with WebCenter Content (WCC) as the application.
For the production back end, RAC will be be the production DB and we need to support failover to Data Guard.
We set up a Multi Data Source (MDS) with the first simple Data Source pointing to RAC and the second Data Source pointing to Data Guard.
Upon testing, this scenario basically works correctly: when RAC is shutdown and Data Guard enabled, the switch occurs and the app works against Data Guard. And conversely, when Data Guard is shut down and RAC brought up, MDS will revert to pointing to RAC and the app will work correctly.
However the DBA insists, that the alternate Data Source should not need to be completely down but should be able to be in a read-only state and the MDS should detect that if it is in a read-only state, it will be counted as unavailable and try to use the alternate Data Source. This does not work with the default set up, I see in the logs that a connection can be made to the read-only DB instance which will not work at all with the app and is not what is desired by the customer.
Is there a way to configure the MDS so that if a Data SOurce is only available as read-only, the alternate Data Source will be used?

I may be able to describe a trick... Try setting the "test table" property of the DataGuard DataSource
to some update statement, ideally one to a otherwise unused table. eg:
SQL update myJunkTable set foo = 1 where 1 = 0
This won't actually update the table (which could have zero rows even) but I hope the
read-only DBMS would throw an exception anyway, and this will give WLS the impression
it can't get healthy connections, and That DataSource won't be used, until the read-only
status is removed.
However, from a standard point of view, a read-only DBMS may be perfectly useful for some applications,
so that is not of itself a reason for WLS not to use it.

Weblogic 8 怎么没有设置 TX Data Source 的地方呢?请指教!谢谢

weblogic 8 怎么没有设置 TX Data Source 的地方呢？请指教！谢谢

改在Connection Pool中支持TX,这和实现才相符,因为DataSource本身只是对
Connection Pool中的物理连结二次工厂化,而对分布事务支持是在建立物理连结池Connection Pool时实现的.

Weblogic - jndi and data source connectivity problem

Unable to deploy EJB: OrganizationEJB from sempire_bc.jar
The DataSource with the JNDI name: OrganizationDB can not be located. Please ensure
that the DataSource has been deployed
successfully and that the JNDI name in your EJB Deployment descriptor is correct.
In my console, I have created a connection pool 'oraclePool' and 3 datasource
'jdbc.GangsterDB', 'jdbc.OrganizationDB' and
'jdbc.JobDB'. I have also specified the target server and there seems to be no
error. I have checked 'Monitor All Connection
Pools' and oraclePool is running. I still do not understand the problem that I
am getting and have no clue how to solve it.
Thank you
Ronak Parekh
My weblogic-ejb-jar.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
     <weblogic-enterprise-bean>
          <ejb-name>GangsterEJB</ejb-name>
          <entity-descriptor>
               <persistence>
                    <persistence-type>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                         <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
                    </persistence-type>
                    <persistence-use>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                    </persistence-use>
               </persistence>
          </entity-descriptor>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <jndi-name>jdbc.GangsterDB</jndi-name>
          </resource-description>
     </reference-descriptor>
          <local-jndi-name>jdbc.GangsterDB</local-jndi-name>
     </weblogic-enterprise-bean>
     <weblogic-enterprise-bean>
          <ejb-name>OrganizationEJB</ejb-name>
          <entity-descriptor>
               <persistence>
                    <persistence-type>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                         <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
                    </persistence-type>
                    <persistence-use>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                    </persistence-use>
               </persistence>
          </entity-descriptor>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <jndi-name>jdbc.OrganizationDB</jndi-name>
          </resource-description>
          </reference-descriptor>
          <local-jndi-name>jdbc.OrganizationDB</local-jndi-name>
     </weblogic-enterprise-bean>
     <weblogic-enterprise-bean>
          <ejb-name>JobEJB</ejb-name>
          <entity-descriptor>
               <persistence>
                    <persistence-type>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                         <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
                    </persistence-type>
                    <persistence-use>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                    </persistence-use>
               </persistence>
          </entity-descriptor>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <jndi-name>jdbc.JobDB</jndi-name>
          </resource-description>
     </reference-descriptor>
          <local-jndi-name>jdbc.JobDB</local-jndi-name>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
My ejb-jar.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC
     "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
     "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
     <display-name>Business Component CMP 2.0</display-name>
     <enterprise-beans>
<entity>
          <display-name>Gangster Entity Bean</display-name>
     <ejb-name>GangsterEJB</ejb-name>
<local-home>com.sempire.builder.business_component.GangsterHome</local-home>
<local>com.sempire.builder.business_component.Gangster</local>
<ejb-class>com.sempire.builder.business_component.GangsterBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
     <abstract-schema-name>GangsterEJB</abstract-schema-name>
<cmp-field><field-name>iD</field-name></cmp-field>
     <cmp-field><field-name>name</field-name></cmp-field>
<cmp-field><field-name>nickname</field-name></cmp-field>
<cmp-field><field-name>badness</field-name></cmp-field>
               <primkey-field>iD</primkey-field>
               <resource-ref>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params></method-params>
                    </query-method>
                    <ejb-ql>
                         <![CDATA[SELECT OBJECT(a) FROM GangsterEJB AS a]]>
                    </ejb-ql>
               </query>
          </entity>
<entity>
     <display-name>Organization Entity Bean</display-name>
<ejb-name>OrganizationEJB</ejb-name>
<local-home>com.sempire.builder.business_component.OrganizationHome</local-home>
<local>com.sempire.builder.business_component.Organization</local>
<ejb-class>com.sempire.builder.business_component.OrganizationBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>OrganizationEJB</abstract-schema-name>
<cmp-field><field-name>iD</field-name></cmp-field>
     <cmp-field><field-name>name</field-name></cmp-field>
               <cmp-field><field-name>description</field-name></cmp-field>
               <primkey-field>iD</primkey-field>
               <resource-ref>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params></method-params>
                    </query-method>
                    <ejb-ql>
                         <![CDATA[SELECT OBJECT(a) FROM OrganizationEJB AS a]]>
                    </ejb-ql>
               </query>
          </entity>
<entity>
<display-name>Job Entity Bean</display-name>
<ejb-name>JobEJB</ejb-name>
<local-home>com.sempire.builder.business_component.JobHome</local-home>
<local>com.sempire.builder.business_component.Job</local>
<ejb-class>com.sempire.builder.business_component.JobBean</ejb-class>
<persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>JobEJB</abstract-schema-name>
               <cmp-field><field-name>iD</field-name></cmp-field>
<cmp-field><field-name>name</field-name></cmp-field>
<cmp-field><field-name>score</field-name></cmp-field>
               <cmp-field><field-name>setupCost</field-name></cmp-field>
               <primkey-field>iD</primkey-field>
               <resource-ref>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params></method-params>
                    </query-method>
                    <ejb-ql>
                         <![CDATA[SELECT OBJECT(a) FROM JobEJB AS a]]>
                    </ejb-ql>
               </query>
          </entity>
     </enterprise-beans>
     <relationships>
<ejb-relation>
<ejb-relation-name>organization-memberGangsters</ejb-relation-name>
<ejb-relationship-role>
     <ejb-relationship-role-name>organization---memberGangsters</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
     <ejb-name>OrganizationEJB</ejb-name>
</relationship-role-source>
<cmr-field>
     <cmr-field-name>memberGangsters</cmr-field-name>
     <cmr-field-type>java.util.Collection</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
               <ejb-relationship-role>
     <ejb-relationship-role-name>memberGangsters---organization</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<cascade-delete/>
<relationship-role-source>
     <ejb-name>GangsterEJB</ejb-name>
</relationship-role-source>
<cmr-field>
     <cmr-field-name>organization</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
</ejb-relation>
<ejb-relation>
<ejb-relation-name>gangsters-jobs</ejb-relation-name>
<ejb-relationship-role>
     <ejb-relationship-role-name>gangsters---jobs</ejb-relationship-role-name>
     <multiplicity>Many</multiplicity>
     <relationship-role-source>
          <ejb-name>GangsterEJB</ejb-name>
     </relationship-role-source>
     <cmr-field>
          <cmr-field-name>jobs</cmr-field-name>
          <cmr-field-type>java.util.Collection</cmr-field-type>
     </cmr-field>
</ejb-relationship-role>
               <ejb-relationship-role>
     <ejb-relationship-role-name>jobs---gangsters</ejb-relationship-role-name>
     <multiplicity>Many</multiplicity>
     <relationship-role-source>
          <ejb-name>JobEJB</ejb-name>
     </relationship-role-source>
     <cmr-field>
          <cmr-field-name>gangsters</cmr-field-name>
          <cmr-field-type>java.util.Collection</cmr-field-type>
     </cmr-field>
</ejb-relationship-role>
          </ejb-relation>
<ejb-relation>
<ejb-relation-name>organization-theBoss</ejb-relation-name>
     <ejb-relationship-role>
     <ejb-relationship-role-name>organization---theBoss</ejb-relationship-role-name>
     <multiplicity>One</multiplicity>
     <relationship-role-source>
          <ejb-name>OrganizationEJB</ejb-name>
     </relationship-role-source>
     <cmr-field>
          <cmr-field-name>theBoss</cmr-field-name>
               </cmr-field>
          </ejb-relationship-role>
               <ejb-relationship-role>
                    <ejb-relationship-role-name>theBoss---organization</ejb-relationship-role-name>
     <multiplicity>One</multiplicity>
<relationship-role-source>
     <ejb-name>GangsterEJB</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
     </relationships>
     <assembly-descriptor>
     <container-transaction>
     <method>
          <ejb-name>GangsterEJB</ejb-name>
          <method-name>*</method-name>
     </method>
     <method>
          <ejb-name>OrganizationEJB</ejb-name>
          <method-name>*</method-name>
     </method>
     <method>
          <ejb-name>JobEJB</ejb-name>
          <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
</ejb-jar>
My weblogic-cmp-rdbms-jar.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-rdbms20-persistence-600.dtd'>
<weblogic-rdbms-jar>
     <weblogic-rdbms-bean>
          <ejb-name>GangsterEJB</ejb-name>
          <data-source-name>GangsterDB</data-source-name>
          <table-name>GANGSTER</table-name>
          <field-map>
     <cmp-field>iD</cmp-field>
     <dbms-column>ID</dbms-column>
     </field-map>
     <field-map>
     <cmp-field>name</cmp-field>
     <dbms-column>NAME</dbms-column>
     </field-map>
          <field-map>
               <cmp-field>nickname</cmp-field>
     <dbms-column>NICKNAME</dbms-column>
     </field-map>
     <field-map>
     <cmp-field>badness</cmp-field>
     <dbms-column>BADNESS</dbms-column>
          </field-map>
          <weblogic-query>
               <query-method>
                    <method-name>findAll</method-name>
                    <method-params></method-params>
               </query-method>
          </weblogic-query>
     </weblogic-rdbms-bean>
     <weblogic-rdbms-bean>
          <ejb-name>OrganizationEJB</ejb-name>
          <data-source-name>OrganizationDB</data-source-name>
          <table-name>ORGANIZATION</table-name>
          <field-map>
               <cmp-field>iD</cmp-field>
               <dbms-column>ID</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>name</cmp-field>
               <dbms-column>NAME</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>description</cmp-field>
               <dbms-column>DESCRIPTION</dbms-column>
          </field-map>
          <weblogic-query>
               <query-method>
                    <method-name>findAll</method-name>
                    <method-params></method-params>
               </query-method>
          </weblogic-query>
     </weblogic-rdbms-bean>
     <weblogic-rdbms-bean>
          <ejb-name>JobEJB</ejb-name>
          <data-source-name>JobDB</data-source-name>
          <table-name>JOB</table-name>
     <field-map>
               <cmp-field>iD</cmp-field>
               <dbms-column>ID</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>name</cmp-field>
               <dbms-column>NAME</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>score</cmp-field>
               <dbms-column>SCORE</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>setupCost</cmp-field>
               <dbms-column>SETUPCOST</dbms-column>
          </field-map>
          <weblogic-query>
               <query-method>
                    <method-name>findAll</method-name>
                    <method-params></method-params>
               </query-method>
          </weblogic-query>
     </weblogic-rdbms-bean>
     <weblogic-rdbms-relation>
     <relation-name>organization-memberGangsters</relation-name>
     <weblogic-relationship-role>
          <relationship-role-name>memberGangsters---organization</relationship-role-name>
          <column-map>
          <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
     </weblogic-relationship-role>
</weblogic-rdbms-relation>
<weblogic-rdbms-relation>
     <relation-name>gangsters-jobs</relation-name>
     <table-name>JOBS</table-name>
     <weblogic-relationship-role>
          <relationship-role-name>gangsters---jobs</relationship-role-name>
          <column-map>
               <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
     </weblogic-relationship-role>
     <weblogic-relationship-role>
          <relationship-role-name>jobs---gangsters</relationship-role-name>
          <column-map>
               <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
<weblogic-rdbms-relation>
     <relation-name>organization-theBoss</relation-name>
     <weblogic-relationship-role>
          <relationship-role-name>organization---theBoss</relationship-role-name>
          <column-map>
               <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
     </weblogic-relationship-role>
</weblogic-rdbms-relation>
</weblogic-rdbms-jar>

just looking at you weblogic-ejb-jar.xml,
your ejb jndi names are the same as the data source jndi names...this
may be your problem.
Ronak Parekh wrote:
Unable to deploy EJB: OrganizationEJB from sempire_bc.jar
The DataSource with the JNDI name: OrganizationDB can not be located. Please ensure
that the DataSource has been deployed
successfully and that the JNDI name in your EJB Deployment descriptor is correct.
In my console, I have created a connection pool 'oraclePool' and 3 datasource
'jdbc.GangsterDB', 'jdbc.OrganizationDB' and
'jdbc.JobDB'. I have also specified the target server and there seems to be no
error. I have checked 'Monitor All Connection
Pools' and oraclePool is running. I still do not understand the problem that I
am getting and have no clue how to solve it.
Thank you
Ronak Parekh
My weblogic-ejb-jar.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
     <weblogic-enterprise-bean>
          <ejb-name>GangsterEJB</ejb-name>
          <entity-descriptor>
               <persistence>
                    <persistence-type>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                         <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
                    </persistence-type>
                    <persistence-use>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                    </persistence-use>
               </persistence>
          </entity-descriptor>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <jndi-name>jdbc.GangsterDB</jndi-name>
          </resource-description>
     </reference-descriptor>
          <local-jndi-name>jdbc.GangsterDB</local-jndi-name>
     </weblogic-enterprise-bean>
     <weblogic-enterprise-bean>
          <ejb-name>OrganizationEJB</ejb-name>
          <entity-descriptor>
               <persistence>
                    <persistence-type>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                         <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
                    </persistence-type>
                    <persistence-use>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                    </persistence-use>
               </persistence>
          </entity-descriptor>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <jndi-name>jdbc.OrganizationDB</jndi-name>
          </resource-description>
          </reference-descriptor>
          <local-jndi-name>jdbc.OrganizationDB</local-jndi-name>
     </weblogic-enterprise-bean>
     <weblogic-enterprise-bean>
          <ejb-name>JobEJB</ejb-name>
          <entity-descriptor>
               <persistence>
                    <persistence-type>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                         <type-storage>META-INF/weblogic-cmp-rdbms-jar.xml</type-storage>
                    </persistence-type>
                    <persistence-use>
                         <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
                         <type-version>6.0</type-version>
                    </persistence-use>
               </persistence>
          </entity-descriptor>
          <reference-descriptor>
          <resource-description>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <jndi-name>jdbc.JobDB</jndi-name>
          </resource-description>
     </reference-descriptor>
          <local-jndi-name>jdbc.JobDB</local-jndi-name>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
My ejb-jar.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC
     "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
     "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
     <display-name>Business Component CMP 2.0</display-name>
     <enterprise-beans>
<entity>
          <display-name>Gangster Entity Bean</display-name>
     <ejb-name>GangsterEJB</ejb-name>
<local-home>com.sempire.builder.business_component.GangsterHome</local-home>
<local>com.sempire.builder.business_component.Gangster</local>
<ejb-class>com.sempire.builder.business_component.GangsterBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
     <abstract-schema-name>GangsterEJB</abstract-schema-name>
<cmp-field><field-name>iD</field-name></cmp-field>
     <cmp-field><field-name>name</field-name></cmp-field>
<cmp-field><field-name>nickname</field-name></cmp-field>
<cmp-field><field-name>badness</field-name></cmp-field>
               <primkey-field>iD</primkey-field>
               <resource-ref>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params></method-params>
                    </query-method>
                    <ejb-ql>
                         <![CDATA[SELECT OBJECT(a) FROM GangsterEJB AS a]]>
                    </ejb-ql>
               </query>
          </entity>
<entity>
     <display-name>Organization Entity Bean</display-name>
<ejb-name>OrganizationEJB</ejb-name>
<local-home>com.sempire.builder.business_component.OrganizationHome</local-home>
<local>com.sempire.builder.business_component.Organization</local>
<ejb-class>com.sempire.builder.business_component.OrganizationBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>OrganizationEJB</abstract-schema-name>
<cmp-field><field-name>iD</field-name></cmp-field>
     <cmp-field><field-name>name</field-name></cmp-field>
               <cmp-field><field-name>description</field-name></cmp-field>
               <primkey-field>iD</primkey-field>
               <resource-ref>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params></method-params>
                    </query-method>
                    <ejb-ql>
                         <![CDATA[SELECT OBJECT(a) FROM OrganizationEJB AS a]]>
                    </ejb-ql>
               </query>
          </entity>
<entity>
<display-name>Job Entity Bean</display-name>
<ejb-name>JobEJB</ejb-name>
<local-home>com.sempire.builder.business_component.JobHome</local-home>
<local>com.sempire.builder.business_component.Job</local>
<ejb-class>com.sempire.builder.business_component.JobBean</ejb-class>
<persistence-type>Container</persistence-type>
               <prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>JobEJB</abstract-schema-name>
               <cmp-field><field-name>iD</field-name></cmp-field>
<cmp-field><field-name>name</field-name></cmp-field>
<cmp-field><field-name>score</field-name></cmp-field>
               <cmp-field><field-name>setupCost</field-name></cmp-field>
               <primkey-field>iD</primkey-field>
               <resource-ref>
          <res-ref-name>jdbc/oraclePool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
               <query>
                    <query-method>
                         <method-name>findAll</method-name>
                         <method-params></method-params>
                    </query-method>
                    <ejb-ql>
                         <![CDATA[SELECT OBJECT(a) FROM JobEJB AS a]]>
                    </ejb-ql>
               </query>
          </entity>
     </enterprise-beans>
     <relationships>
<ejb-relation>
<ejb-relation-name>organization-memberGangsters</ejb-relation-name>
<ejb-relationship-role>
     <ejb-relationship-role-name>organization---memberGangsters</ejb-relationship-role-name>
<multiplicity>One</multiplicity>
<relationship-role-source>
     <ejb-name>OrganizationEJB</ejb-name>
</relationship-role-source>
<cmr-field>
     <cmr-field-name>memberGangsters</cmr-field-name>
     <cmr-field-type>java.util.Collection</cmr-field-type>
</cmr-field>
</ejb-relationship-role>
               <ejb-relationship-role>
     <ejb-relationship-role-name>memberGangsters---organization</ejb-relationship-role-name>
<multiplicity>Many</multiplicity>
<cascade-delete/>
<relationship-role-source>
     <ejb-name>GangsterEJB</ejb-name>
</relationship-role-source>
<cmr-field>
     <cmr-field-name>organization</cmr-field-name>
</cmr-field>
</ejb-relationship-role>
</ejb-relation>
<ejb-relation>
<ejb-relation-name>gangsters-jobs</ejb-relation-name>
<ejb-relationship-role>
     <ejb-relationship-role-name>gangsters---jobs</ejb-relationship-role-name>
     <multiplicity>Many</multiplicity>
     <relationship-role-source>
          <ejb-name>GangsterEJB</ejb-name>
     </relationship-role-source>
     <cmr-field>
          <cmr-field-name>jobs</cmr-field-name>
          <cmr-field-type>java.util.Collection</cmr-field-type>
     </cmr-field>
</ejb-relationship-role>
               <ejb-relationship-role>
     <ejb-relationship-role-name>jobs---gangsters</ejb-relationship-role-name>
     <multiplicity>Many</multiplicity>
     <relationship-role-source>
          <ejb-name>JobEJB</ejb-name>
     </relationship-role-source>
     <cmr-field>
          <cmr-field-name>gangsters</cmr-field-name>
          <cmr-field-type>java.util.Collection</cmr-field-type>
     </cmr-field>
</ejb-relationship-role>
          </ejb-relation>
<ejb-relation>
<ejb-relation-name>organization-theBoss</ejb-relation-name>
     <ejb-relationship-role>
     <ejb-relationship-role-name>organization---theBoss</ejb-relationship-role-name>
     <multiplicity>One</multiplicity>
     <relationship-role-source>
          <ejb-name>OrganizationEJB</ejb-name>
     </relationship-role-source>
     <cmr-field>
          <cmr-field-name>theBoss</cmr-field-name>
               </cmr-field>
          </ejb-relationship-role>
               <ejb-relationship-role>
                    <ejb-relationship-role-name>theBoss---organization</ejb-relationship-role-name>
     <multiplicity>One</multiplicity>
<relationship-role-source>
     <ejb-name>GangsterEJB</ejb-name>
</relationship-role-source>
</ejb-relationship-role>
</ejb-relation>
     </relationships>
     <assembly-descriptor>
     <container-transaction>
     <method>
          <ejb-name>GangsterEJB</ejb-name>
          <method-name>*</method-name>
     </method>
     <method>
          <ejb-name>OrganizationEJB</ejb-name>
          <method-name>*</method-name>
     </method>
     <method>
          <ejb-name>JobEJB</ejb-name>
          <method-name>*</method-name>
               </method>
               <trans-attribute>Required</trans-attribute>
          </container-transaction>
     </assembly-descriptor>
</ejb-jar>
My weblogic-cmp-rdbms-jar.xml file is:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-rdbms-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB RDBMS Persistence//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-rdbms20-persistence-600.dtd'>
<weblogic-rdbms-jar>
     <weblogic-rdbms-bean>
          <ejb-name>GangsterEJB</ejb-name>
          <data-source-name>GangsterDB</data-source-name>
          <table-name>GANGSTER</table-name>
          <field-map>
     <cmp-field>iD</cmp-field>
     <dbms-column>ID</dbms-column>
     </field-map>
     <field-map>
     <cmp-field>name</cmp-field>
     <dbms-column>NAME</dbms-column>
     </field-map>
          <field-map>
               <cmp-field>nickname</cmp-field>
     <dbms-column>NICKNAME</dbms-column>
     </field-map>
     <field-map>
     <cmp-field>badness</cmp-field>
     <dbms-column>BADNESS</dbms-column>
          </field-map>
          <weblogic-query>
               <query-method>
                    <method-name>findAll</method-name>
                    <method-params></method-params>
               </query-method>
          </weblogic-query>
     </weblogic-rdbms-bean>
     <weblogic-rdbms-bean>
          <ejb-name>OrganizationEJB</ejb-name>
          <data-source-name>OrganizationDB</data-source-name>
          <table-name>ORGANIZATION</table-name>
          <field-map>
               <cmp-field>iD</cmp-field>
               <dbms-column>ID</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>name</cmp-field>
               <dbms-column>NAME</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>description</cmp-field>
               <dbms-column>DESCRIPTION</dbms-column>
          </field-map>
          <weblogic-query>
               <query-method>
                    <method-name>findAll</method-name>
                    <method-params></method-params>
               </query-method>
          </weblogic-query>
     </weblogic-rdbms-bean>
     <weblogic-rdbms-bean>
          <ejb-name>JobEJB</ejb-name>
          <data-source-name>JobDB</data-source-name>
          <table-name>JOB</table-name>
     <field-map>
               <cmp-field>iD</cmp-field>
               <dbms-column>ID</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>name</cmp-field>
               <dbms-column>NAME</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>score</cmp-field>
               <dbms-column>SCORE</dbms-column>
          </field-map>
          <field-map>
               <cmp-field>setupCost</cmp-field>
               <dbms-column>SETUPCOST</dbms-column>
          </field-map>
          <weblogic-query>
               <query-method>
                    <method-name>findAll</method-name>
                    <method-params></method-params>
               </query-method>
          </weblogic-query>
     </weblogic-rdbms-bean>
     <weblogic-rdbms-relation>
     <relation-name>organization-memberGangsters</relation-name>
     <weblogic-relationship-role>
          <relationship-role-name>memberGangsters---organization</relationship-role-name>
          <column-map>
          <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
     </weblogic-relationship-role>
</weblogic-rdbms-relation>
<weblogic-rdbms-relation>
     <relation-name>gangsters-jobs</relation-name>
     <table-name>JOBS</table-name>
     <weblogic-relationship-role>
          <relationship-role-name>gangsters---jobs</relationship-role-name>
          <column-map>
               <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
     </weblogic-relationship-role>
     <weblogic-relationship-role>
          <relationship-role-name>jobs---gangsters</relationship-role-name>
          <column-map>
               <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
<weblogic-rdbms-relation>
     <relation-name>organization-theBoss</relation-name>
     <weblogic-relationship-role>
          <relationship-role-name>organization---theBoss</relationship-role-name>
          <column-map>
               <foreign-key-column>iD</foreign-key-column>
               <key-column>ID</key-column>
     </column-map>
     </weblogic-relationship-role>
</weblogic-rdbms-relation>
</weblogic-rdbms-jar>

Setting up JDBC Data Source for JCA Database Adapter in WLS - only SID?

Following the documentation for setting up a connection for use with the JCA Database Adapter (http://otnbeta.oracle.com/fmw11g/582tj30eapvb/integration.1111/e10231/life_cycle.htm), section 2.4.1, Step 8 simply says "Enter the connection properties in the Connection Properties page, and then click Next"
In the "Create a New JDBC Data Source" screen of the WLS Administration Console there is the entry field vaguely labeled as "Database Name:" Of course I entered the Oracle RDBMS service name (which we should ALWAYS be using), only to be informed upon clicking next, that WLS was expecting the SID.
Two things:
1. At least through this maintenance console, it appears that BEA did not understand the whole concept or value of Oracle RDBMS logical service names versus the SID (I have seen this in several products that Oracle has acquired). Best practice would be to use the Oracle RDBMS service name, which doesn't appear to be an option in this console.
2. The OFM documentation should be more helpful in explaining.

Compare to the analogous setup in OAS 10.1.3.4/EM... far better clarity in the maintenance console and option of either SID or service name.

Can JMX configure Multi Data Source

I am trying to create Multi DataSource in Weblogic.
But i am not getting enough Help on this.
I went through some site mentioning that JMX can only access and modify the JDBC Resource.
Can anyone please confirm whether we can Create MultiDataSource through JMx.
I am able to create the DataSource but struck with creation of MultiDataSource.
ALso if some one has have reference code to configute MDS code that would be great.
Regards

there's an example of it done in wlst script in the samples dir of the server, so since this uses JMX, then it will be possible in pure java/JMX..

Which ojdbc14.jar JDBC driver to use for Oracle 10g database

When ODI is installed there seems to be an Oralce JDBC driver in place in the drivers folder (ojdbc14.jar).
When we connect to an Oracle datastore and point to a table and use the 'reverse' function to populate the columns - it sort of works OK but does not bring back the datatypes properly. This is found to be when the Oracle table has UNICODE character datatypes NCHAR and NVARCHAR. If a table has CHAR and VARCHAR it is all OK but any table that has UNICODE datatyoe has a problem.
Is this likely to be the JDBC driver ?
We have tried replacing this ojdbc14.jar with the older classes12 and this, as expected, did not resolve the issue.
We then tried replacing it with the latest 10.2.0.4 ojdbc14.jar but again no difference.
Does anyone have any experience with Oracle JDBC drivers and what release level to use - and using against UNICODE datatypes in tables ?
Regards

Our problem is that when we use 'reverse' to populate the columns from a physicla table in an Oracle database - ODI is obviously 'seeing' the ORacle table and is correctly understanding the columns in the table and defining them in it's model - but wherever there is a column with a datatype in the ORacle database of NCHAR or NVARCHAR it fails to populate the datatype or the 'length' of these columns. If I manually try to specify the datatype these 2 unicode data types do NOT exist in the pull down list of datatypes.
I see what you are asking - if these datatypes are actually defined as datatypes within the actual technology - I cant access my lab right now but will check as soon as I can. Thanks for the suggestion.

OIM 9.1.0.2 - Weblogic JDBC Multi Data Sources for Oracle RAC

Similar Messages

Maybe you are looking for