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.
REST (REpresentational State Transfer)
REST is an "architectural style" that basically exploits the existing technology and protocols of the Web, including HTTP (Hypertext Transfer Protocol) and XML. REST is simpler to use than the well-known SOAP (Simple Object Access Protocol) approach, which requires writing or using a provided server program (to serve data) and a client program (to request data). REST (REpresentational State Transfer) is a simple stateless architecture and involves reading a designated Web page that contains an XML file. The XML file describes and includes the desired content.
REST is often used in mobile applications, social networking Web sites, mashup tools and automated business processes. The REST style emphasizes that interactions between clients and services is enhanced by having a limited number of operations. Flexibility is provided by assigning resources their own unique universal resource indicators. Because each operation has a specific meaning (GET, POST, PUT and DELETE), REST avoids ambiguity.
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.
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.