Integration of your U2 application with other software and services can be done in a variety of ways. Some of these include tools that will be globally familiar to us all. Rocket has its own tools such as BCI & EDA and other common methods to look at might also include ODBC and REST. See below for information on all solutions.
EDA allows you to store U2 data in an external RDBMS, such as DB2® or Microsoft® SQL Server, and still access it from U2 applications that use the non-first normal form (NF2) data model.
U2 provides a variety of ways to expose the U2 data to relational applications through Open Database Connectivity (ODBC), JDBC, Object Linking and Embedding Database (OLE DB), ADO.NET, and so on. Such relational applications access U2 data as if it were first normal form (1NF) data. In addition, the Basic SQL Client Interface (BCI) allows U2 applications to access external RDBMS data using Basic programs and ECL/TCL commands through the ODBC interface.
Unlike the two methods above, EDA provides a U2 user with a transparent way to store and access the data in an external RDBMS. Once an EDA file is created, mapped, and converted, the file is used as a normal U2 file in Basic programs and ECL/TCL commands. The U2 database engine does all the mapping, command translation, and optimization.
REST is an "architectural style" that basically exploits the existing technology and protocols of the Web, including HTTP (Hypertext Transfer Protocol) and XML.
The U2 ODBC driver enables ODBC applications to connect to the UniData or UniVerse (U2) database management system (DBMS).
BCI (Unibasic SQL Client Interface) is a collection of U2 Unibasic functions which allows the developer to prepare SQL statements, which can be issue to a ODBC server.