ODBC, OLEDB and JDBC are standards-based SQL interfaces for UniData and UniVerse that provide access to U2 tables, files and views, including data and calculated fields. ODBC takes full advantage of U2 multivalued data structures and extended features, such as select lists.
While ODBC is primarily a desktop connectivity tool, it can be used as an API to develop applications using SQL rather than native record access. It is a logical choice for users of ODBC-based development tools such as PowerBuilder or Visual Basic with standard data controls. An ODBC interface provides true data server independence since Rocket's extended relational features are transparently accessed and are treated like any other RDBMS. However, because it uses a relational, set-oriented approach, it requires a paradigm shift from native record-oriented U2 development.
The OLE DB protocol is a Microsoft® standard for Universal Data Access: the ability to use one protocol to access both SQL and non-SQL based data sources and seamlessly integrate them into a single application. Microsoft SQL Server uses OLE DB internally as its own data access mechanism. As application needs and development tools mature, the ability to manage heterogeneous data sources becomes more important. Such tools as PowerBuilder by Sybase now act as OLE DB consumers. UniOLEDB is the OLE DB provider for Rocket's extended relational data servers, offering tight integration with Microsoft SQL Server as well as any OLE DB compliant tool. The next wave of OLE DB support for both Windows-based development tools and the U2 servers is "chaptered rowsets", a construct which closely maps to associated multivalued fields or nested tables.
JDBC is a Java™ API that extends the capabilities of Java. Because it is a standard API, developers can write applications that use a pure Java API to access nearly any data server. Unlike ODBC, JDBC does not use a C interface, eliminating many of the concerns about security, robustness and portability of applications that may be found with ODBC.
COBOL Direct Connect (CDC) supports quick and safe redeployment of COBOL-indexed files into SQL-compliant RDBMS tables without data structure modification, source code changes, "dynamic SQL" or other migration efforts. CDC utilizes legacy applications including underlying file systems, access to GUI interfaces, and desktop DSS/4GL interoperability. In addition, new applications can be developed using Java and other modern languages that can access the COBOL data.
COBOL Direct Connect provides:
Direct redeployment of ISAM (or other) data structures into UniData's nested RDBMS which provides applications with SQL data access and permits the usage of more modern tools for reporting and BI/OLAP analysis. Preservation of your existing COBOL applications and data structures so you maintain just one set of source code. Expanded functionality with a low cost of ownership.
COBOL Direct Connect maps COBOL ISAM files into the UniData extended relational data servers. It works with most versions of AcuCobol (from AcuCorp) and MicroFocus COBOL (from Merant/MicroFocus).
InterCall provides a high performance, native, record-based, objected-oriented access to the U2 servers from any C client running on Windows® or UNIX®.
The UniCall Interface (UCI) is a 'C' language, SQL Call Level Interface (CLI) that provides a high-performance, ODBC 2-based interface to UniVerse and UniData for developers and third-party tools vendors.
UCI is available as a UNIX static library and a 32-bit Windows DLL. It uses the UniRPC mechanism, permitting applications direct access to U2 data servers for both local and networked UNIX or Windows NT-based servers. It also provides direct access to all schemas/accounts, table, views and files, and dictionary information using the U2 SQL engine.
UCI runs in 1NF mode on both UniVerse and UniData and offers capabilities for strict SQL access to tables and views via the information catalog. In addition, on UniVerse, UCI runs in NF2 mode and provides access to schemas and accounts via the Vocabulary (VOC) and UV.ACCOUNT files. While it does use ODBC-like primitives, it does not replace the use of UV/ODBC for ODBC-based enterprise and desktop integration requirements.
UniObjects is an ActiveX control whose objects are able to take full advantage of the dual interface standard for either fast COM or flexible automation interfaces, both supported by Visual Basic. As a result, UniObjects brings the proven advantages of object-oriented development to U2 Windows-based client applications development.
In the case of Visual Basic, or Visual InterDev using VB Script, UniObjects becomes a natural extension to the language. Some of the objects provided include: Session, File, Dynamic Array, Select List, Dictionary, Command, Sequential File, Transaction, and Subroutine object that permits reuse of existing application subroutines. All objects can be manipulated in the same rapid and easy-to-use manner as a traditional U2 application.
UniObjects supports rapid application development. Records are read and written using "Dynamic Array" objects, which provide easy-to-use access to complex data structures representing real-world business objects such as orders, invoices, customers, etc. Its ability to fully support the reuse of components also helps ensure the development of high quality applications faster, more efficiently, and often at a lower cost.
UniObjects lets companies capitalize on using Microsoft COM technology for new GUI application interfaces. Yet they also leverage today's application by calling existing cataloged subroutines. Developers can easily change the front end, without sacrificing years of investment in existing technology.
Using tools such as Visual Basic, or Visual InterDev with VB Script, UniObjects is just as versatile at creating Active Server pages for the Web. Visual Basic developers benefit even more because existing Visual Basic applications can be easily transitioned into Active Server pages. Once created, any standard Web browser can access applications developed using UniObjects.
UniObjects for .NET is an interface to UniData and UniVerse through Microsoft .NET. UniObjects for .NET is a proprietary middleware application program interface (API) designed specifically for software development in the .NET Framework. This interface is managed code written in C# Common Language Runtime (CLR).
Software developers can use the UniObjects for .NET API and any CLR language (such as C#, J#, VB.NET, or C++ .NET) to create applications and services.
UniObjects for Java is a 100% pure Java class library whose objects are able to take full advantage of any Java-based integrated development environment (IDE). Create Java-based applications quickly and easily on both Windows NT and UNIX servers.
Dynamic Connect is a connectivity tool which integrates host-based applications with the Microsoft Windows desktop. The graphical user interface lets you emulate a terminal and customize your workspace environment.
UCI is a C language application programm interface (API) that lets application developers create client programs that use SQL functions to access data in UniVerse data servers