Main   Products   Offshore Outsourcing   Customers   Partners   ContactUs  
JDBC Databases
  HXTT Access v7.1
  HXTT Cobol v5.0
  HXTT DBF v7.1
  Buy Now
  HXTT Excel v6.1
  HXTT Json v1.0
  HXTT Paradox v7.1
  HXTT PDF v2.0
  HXTT Text(CSV) v7.1
  HXTT Word v1.1
  HXTT XML v4.0
Offshore Outsourcing
Free Resources
  Firewall Tunneling
  Search Indexing Robot
  Conditional Compilation
  Password Recovery for MS Access
  Password Recovery for Corel Paradox
  Checksum Tool for MD5
  Character Set Converter
  Pyramid - Poker of ZYH
Heng Xing Tian Tai Lab of Xi'an City (abbr, HXTT)

Wesphere v6.1
Colin Munford
2007-06-22 05:44:14
We have configured your driver under websphere application server v6.1 as per 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.
Re:Wesphere v6.1
HXTT Support
2007-06-24 03:40:26
You can see here for help.
Re:Re:Wesphere v6.1
colin munford
2007-07-04 23:50:41
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");
connection = DriverManager.getConnection(DBF_CONNECTION_HXTT,

Colin Munford
Re:Re:Re:Wesphere v6.1
HXTT Support
2007-07-05 01:44:40
>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.
Re:Re:Re:Re:Wesphere v6.1
colin munford
2007-07-27 07:40:22
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.
Re:Re:Re:Re:Re:Wesphere v6.1
HXTT Support
2007-07-27 09:00:47
You should call
or connection.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);//or other transaction isolation level.
Re:Re:Re:Re:Re:Re:Wesphere v6.1
colin munford
2007-07-30 02:40:52
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 ?

Colin Munford
Re:Re:Re:Re:Re:Re:Re:Wesphere v6.1
HXTT Support
2007-07-30 05:04:29
>the transaction does not appear to rollback if we specify a locktype in the url
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.

Search Key   Search by Last 50 Questions


Copyright © 2003-2019 Heng Xing Tian Tai Lab of Xi'an City. | All Rights Reserved. | Privacy | Legal | Sitemap