Join the world’s largest interactive community dedicated to Oracle technologies.

just remove any other ds xml file from your deploy folder.
Keep only one ds.xml that i refered in my earlier post.

Thanks

@Gurvinder

You said:

"you dont need the FakeXAdatasource.
Just configure the JTDatasource a.d DirectJTDatasources"

It is because he is using Oracle, and Oracle does not need a Fake XA cause it supports a real XA right??
Configuring JTDatasource to use DirectJTDatasource, ATG will try to use the WLS created datasources right??

If it is right, can you help me on how to configure this correctly?

Thanks

Can you confirm if you have created these files in <ATG-home>/localconfig?
1)FakeXADataSource.properties

$class=atg.service.jdbc.FakeXADataSource
driver=oracle.jdbc.driver.OracleDriver
url=jdbc:oracle:thin:@localhost:1521:xe
user=TESTATG
password=TESTATG

2)JTDataSource.properties

$class=atg.service.jdbc.MonitoredDataSource
dataSource=/atg/dynamo/service/jdbc/FakeXADataSource


Note when you use the class as MonitoringDataSource in JTDataSource then JNDI name will not be used.

Peace
Shaik

You can use both FakeXADataSource and app server datasources.

FakeXADataSource doesn't support XA, so its not supported by ATG in production.
But for evaluation or quick test, you can still use FakeXADatasource.

The class name in JTDataSource decides to use JNDI name(JNDIReference class) or FakeXADataSOurce(MonitoringDataSource class)

The use of WatcherDataSource class can be used to monitor the connection pool in ATG.
So typical it would be.
Repository -> JTDataSource(WatcherDataSource class) -> DirectJTDataSource(MonitoringDataSource/JNDIReference class) -> FakeXADataSource/app Datasource

Peace
Shaik

Yes, you are right!

Always remember FakeXADatasource and JNDI name cannot be used together.

Peace
Shaik