[Edserplo_users] Customisation issues

[Steve Loch]

In the week beginning 28'th, I hope to replace the underlying database access software used by Edserplo by a new class or classes written by JOSS. Hopefully you won't notice the difference but there is potential for much to go awry. If you have (mission-critical!) concerns you can let me know. I will leave the QueryLib.class in bodcjar.jar so other bits of software won't fail. We also expect to jettison the use of the bodcConnectionPool.jar. We have yet to run tests on Windows so there may be a delay as we sort out any problems revealed. For maintenance reasons I will need to remove QueryLib once all the other software that uses it has been converted.

The reason we want to do this is so that the Edserplo software is no longer tied to the Oracle DBMS. People outside POl/BODC will be able to use Edserplo with the freely available PostgreSQL. Password changes will be done through an encrypted XML file using the appropriate utility.

This is only one of a number of customisation issues but it is probably the second biggest with the biggest being obfuscation (IP protection). The classes are not yet obfuscated although we know how to do it and it has been done. Obfuscation will be done as the last element of customisation development. Another one that has been overcome is the use of DLB's database of tidal constants. This is now optional. Tooltips (hover text for parameters) should shortly be provided by a Web service - I hope!

Steve