jBASE Software Product Update

1. jBASE Roadshow '99 jBASE SoftwareProduct Update Dave Bryant PresidentjBASE Software, Inc. September, 1999

2. jBASE - The Product • Compiles into executable code • Performance Improvements • Interoperability Enhanced • Can access other databases from BASIC • DB2, Oracle, Sybase, Reality • Separated application from data • High levels of compatibility • Reality, Unidata, uniVerse, Sequoia, R83/91 etc

3. Java OBjEX jBASE Architecture jBASEOBjEX BASIC Application Code (.exe, .bin) jBASE Utilities jSHELL PROC Queries jBASE Library Functions jEDI OLE DBODBC JDBC jBASEFiles RDBMS User Defined Operating System Hardware

4. jBASE - The Product • All MultiValued functionality present • Data logically held the same way • All MV commands present • Spooler / debugger present (Reality) • Files and dictionaries held as separate file system objects • Data the same across all platforms

5. Microsoft Windows 95 / 98 NT Workstation NT Server Digital Alpha Intel Windows 2000 UNIX AIX HP-UX DG/UX Linux (RH 6.0) Solaris SCO & UnixWare Digital Unix Motorola SVR 4 Platform Availability

6. jBASE Future Revisions • Current Revision is 3.2.6 • Revision 3.3 • uniVerse & Unidata compatibility • Revision 4.0 (2H’00) • GUI Admin • New File System • Revision 5.0 (Future) • Java • National Language Support

7. jBASE • Release 3.3 • 4 major conversions have been done in the last 6 months, uniVerse, Unidata, PI/open, Reality • All these findings have been implemented in this version of jBASE • User defined functions • If needed there will be a 3.4

8. jBASE • Release 4.0 • Position jBASE to attack the mainstream • Graphical Admin • New file system • No manual resizing • No file corruption • SQL DDL • Referential integrity • Triggers etc more associated with files • Indexing over jRFS

9. jBASE • Release 5 • Java – Jini • National Language Support • Mainframe support (S390, AS/400) • Research being done now !!

10. Access to Other Data • jEDI Technology • Provides ability to use other databases as if Multivalued • Oracle, Sybase, SQL Server, DB2 • Other applications • MSMQ Server, PC based products • Embedded SQL • Access via ‘C’ API

11. jBASE Networking • Networking is part of the product • Data is accessible from any platforms • j4 File system is network aware • jRFS allows processing to be done on the server • Select across a network • Triggers executed where the data is

12. Distributed Files • Allows a file to be spread over several parts based on • Value of a field • User defined algorithm • File segments may be across a network • A good example would be central system, several regional servers • Need regional figures and corporate figures.

13. Transaction Management • Transactions bracket atomic I/O processing units • for example Credit – Debit pairs • Begin, commit, abort transactions • Transactions support 2 phase commit • Transaction Logging • Available over network to provide hot standby

14. Crash Resilience and Recovery with jBASE

15. Overview • J3 Secure files prevent file corruption. • jBASE Journalling provides update recording and play back in a number of configurations such as: • Simple Item update recording and replay; • Transaction update recording and replay; • Hot Standby recording and replay;

16. J3 Secure Mode Files • J3 secure file updates synched to disk. • J3 overflow and link updates performed in SAFE order and synched to disk. • If a crash occurs you either get the update or you don’t.

17. Simple Item Update • This simple configuration will record any update to files you specify. • Offers an audit trail and simple recovery of lost items. • After disaster: Restore save; apply Journal.

18. Transaction Journalling • Updates are bounded by Transaction Boundaries. • Journal records start and end of boundary. • Journal replay recovers only complete transactions. • Recovery: Restore save and replay transactions.

19. Hot Standby Journalling • Updates saved with or without boundaries. • Stored in journal and also sent to remote systems. • Journal lag time can be set and/or synched. • Recovery: Start journaller on standby; switch to standby.

20. Features & Benefits • A configuration is available for the cautious to the paranoid • - Allows an organization to choose the time to recovery and the performance profile. • Two phase commit transactions • Allows network safe and distributed transactions - all or none.

21. Features and Benefits • Mix, match and change configurations easily - • allows the site to grow the solution with the organization. • Use the journal as continuous On-line backup - • Gives 24hour operation but with secure up-to-the-minute backup.

22. Applications • Quick recovery from machine failure - switch to hot-standby. • Quick recovery without journalling high availability J3 secure system. • On-line duplication to second system (reporting, data mining, data export). • Jlogdup uses jEDI: log to Oracle, Sybase etc.

23. System Requirements • Assume journalling uses 25% of machine • plan capacity accordingly. • Using J3 secure mode with full data sync requires high throughput disk write system for batch processes. • Configure fastest practical connection between hot-standby systems. • RAID arrays well over capacity is wise - Disk based Journals can be large.

24. Availability • Now on UNIX Systems • Release 3.3 on NT Systems • Not available on Windows 95 or 98

25. jBASE Desktop Integration

26. Desktop Integration • jBASE OBjEX • ActiveX implementation of BASIC • jDP & jDC • OLE DB interface • Provides ODBC, JDBC, ADO, RDS

27. jBASE OBjEX • Designed to write applications • Visual Basic, VBA, Delphi etc • Integrated with VB • Will provide context sensitive help • Supports jBC constructs • Common between jBC and OBjEX • Uses same locking mechanism • jBCCallback method • Allows VB to know something has happened in jBC

28. jDP & jDC • jDP – jBASE data provider • jDC – jBASE dictionary configurator • Part of jBASE Enterprise Version • Used for standard interfaces • i.e. no customization except what the app gives you

29. jDP • Interface based on ISG Navigator • ISG (NASDAQ:SISG) • Navigator supports many other databases • DB2, Sybase, Oracle, SQL/Server • Embedded in Oracle 8i • We add the interface between jBASE and ISG

30. jDP • Looked at other products in our space • Our impression was that they were slow and difficult to use • Design goals were to make it easy to use for the Multivalued user/administrator and performant • We succeeded !!

31. jDC • Problem has always been mapping Multidimensional model onto flat ODBC/SQL model • jDC adds information to standard jBASE dictionary to allow adherence to the flat model • SQL standard names • Multivalue associations • Looks like a joined virtual table to ODBC

32. jBASE and Java Current Products and New Development Jim Idle – June ‘99

33. Introduction • The jBASE View of Java • Current Products • Java OBjEX • Release 5.0 – Java Rewrite • Summary

34. Current Products • The jBASE Data Provider • OLE/DB and ADO • ODBC • JDBC • JDBC • Type II Partly Native • NOT an ODBC layer.

35. Current Products • The jBASE JDBC Provides • Standard SQL views of multivalues (Chaptered rowsets) to Java tools • Standard Interface to Java database controls • Allows application wizards and 3rd party tools to be embedded in the application. • Immediately usable by IDEs such as JBuilder, Visual Café, et al.

36. javaOBjEX • Equivalent to our current OBjEX product • Provides jBASE Object model to standard Java • Requires Java Native Interface (JNI) [now available in all VMs] • Requires Enterprise License

37. Release 5.0 – Java Rewrite • Begins this year • Reuse some of Release 4.0 Java Development • Takes jBASE to the “World at Large” • Talks underway with IBM and Sun • Enlisting business partners for this.

38. Release 5.0 – Java Rewrite • Will take our customers with us, not leave them behind. • Java OBjEX Model supported so that current development not wasted • But deprecated in favor of business object oriented model • Will be 100% PURE Java. • Will provide native code on some systems if it can offer any performance advantage (not yet clear)

39. Release 5.0 – Java Rewrite • Will incorporate database security model • Go forward from distributed (n-tier client server) model provided in javaOBjEX • Will allow distribution of business objects definable from existing code • Will allow users to convert jBC (BASIC) to 100% Java

40. Release 5.0 – Java Rewrite • Will allow corporations to retain current staff and their application knowledge • Therefore be able to keep current application • BUT! Move the application forward technologically, and therefore (hopefully) as a business solution

41. Release 5.0 – Java Rewrite • Feature Summary • Database security (Encryptable identifiers JUID, JTID) • Business objects should be exportable via CORBA and/or JNI • Will define distributable services via JINI • Will allow 100% conversion to Java code.

42. Summary • Java is an intrinsic part of the future of jBASE. • Java OBjEX will be available shortly and will be immediately useful and reusable in release 5.0.

43. jADE • 4 GL for jBASE • Conversion to jADE from other 4GLs e.g. System Builder + • Ability to create Visual Basic directly from jADE screens • Full presentation and demo later today

44. jBASE & The Web

45. jBASE & The Web • No additional products are needed • Simply connect jBASE products to mainline products • IIS, Apache, etc • jBASE version of Coyote available soon • Several customers live on the Web using CGI Bin and ASP – Java soon.

46. jBASE Performance

47. Performance • Major Ardent VAR • Needed ability to access the outside world • Benchmarked jBASE and uniVerse • Performance and throughput for large numbers of users important • Network of RS6000 systems • 12 cpu S7A – 12 node RS6000 SP

48. Performance

49. Performance

50. Performance • Local Authority in UK • Upgraded from MDIS X35M to RS6000 F50 • Improve performance of system & supplier • 200 concurrent users • Desire to save money • $250,000+ savings per year was achieved • Maximize opportunities in IT • Y2K compliance