We have configured your driver under websphere application server v6.1 as per http://www.hxtt.com/test/websphere_sample.pdf but when we test the connection we recieve an error. The JVM log does not contain any useful info
'The test connection operation failed for data source cmcodebase on server server1 at node WS6ITCMNode02 with the following exception: java.sql.SQLException:
No suitable driverDSRA0010E: SQL State = 08001, Error Code = 0. View JVM logs for further details.
Could you confirm your DBF driver supports websphere application and also portal server and are there any additional steps we need to take under websphere version 6.
Thanks in anticipation.
|
You can see here http://www.hxtt.com/websphere/index.html for help.
|
Thanks for your detailed websphere configuration instructions. The connection now works successfully. Could you confirm that we need to add the special HXTT driver props as custom properties in the websphere data source Custom Properties similar to the method used for the "url".
E.G. we use a non webspere connection of
Properties props = new Properties();
props.setProperty("DeletesAreVisible", "false");
props.setProperty("Default Index Suffix", "MDX");
Class.forName(JDBC_DRIVER_CLASS_HXTT).newInstance();
connection = DriverManager.getConnection(DBF_CONNECTION_HXTT,
props);
Thanks
Colin Munford
|
>props.setProperty("DeletesAreVisible", "false");
You needn't to add since it's default value.
>props.setProperty("Default Index Suffix", "MDX");
You needn't to add too, since HXTT DBF can detect all index suffix, and you can assgign suffix in CREATE INDEX sql too.
|
How do we create transactional updates when using a websphere connection.
We have tried using transactions on the connection object and also the Initial context object however any changes to tables updated before the error occurs are still being commited even though rollback is being called.
|
You should call
connection.setAutoCommit(false);
or connection.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);//or other transaction isolation level.
|
Thanks for the response. We have done some more tests and the transaction does not appear to rollback if we specify a locktype in the url of FOXPRO or DBASEIV.
If we remove that from url it does appear to work as expected.
We had to add the lockType to update the MDX indexes so not sure how to overcome this.
Any ideas ?
Regards
Colin Munford
|
>the transaction does not appear to rollback if we specify a locktype in the url
> of FOXPRO or DBASEIV.
Yeah. If it runs on Xbase compatible mode, it will disable transaction.
>We had to add the lockType to update the MDX indexes so not sure how to overcome
> this.
If there's other Xbase applictaion read/update MDX index, you need lockType to set Xbase compatible mode. If there's no other Xbase applictaion, you needn't lockType.
|