📄️ RDBMS connection recovery
When a USoft application detects that an existing database connection has been lost, the current transaction is cleared and an internal rollback takes place. A rollback will also be issued on the database.
📄️ USoft for Oracle
Oracle versions 10 and later are currently supported by USoft Developer. Oracle 9 is supported with limitations.
📄️ USoft for ODBC
USoft for ODBC is a normal USoft application that connects to an (R)DBMS to retrieve and store data. The connection is made via an ODBC Driver. This can be useful when you wish to work with an RDBMS other than those directly supported by USoft. A requirement is that there must be an ODBC driver for this external (R)DBMS and that ODBC driver must support at least the requirements listed in the following section.
📄️ JDBC Rules Engine connectivity
JDBC Rules Engine connectivity allows external Java programs to make use of a USoft repository and benefit from the USoft Rules Engine. This guarantees execution of all the business, integrity, and security rules at all times. The rules are stored and managed within the USoft Developer repository. USoft Developer manages the data manipulation in professional databases, such as Oracle, Sybase, IBM's Universal database, or Microsoft's SQL Server.
📄️ JDBC example
Step 1: Loading the USoft JDBC driver classes
📄️ USoft Remote Rules Service API for ODBC
The USoft Remote Rules Service API offers a unique repository-based interface to external programs and desktop tools that support the Microsoft standard ODBC programming language interface, such as MS Excel, MS Word, MS Access and Lotus Approach. It is the first such driver that guarantees execution of all the business, integrity, and security rules at all times. Those rules are stored and managed within the USoft Developer repository. USoft Developer manages the data manipulation in RDBMSs such as SQL Server or Oracle.
📄️ Dynamic Link Libraries (DLLs)
You can write your own DLLs, and connect them to your application using the DllExecute() global action. The USoft API offers two functions to let your DLL communicate with USD through the resource mechanism. To use these you must include USAPI.H in your source file (in the API directory) and link the USAPI.LIB import library. USoft API can be used for all Windows Development Languages that can generate DLLs with PASCAL calling convention. For more information, and for some examples see the ACDLL.C file in the EXAMPLES\\API directory.
📄️ Connecting non-database users to a USoft application
In a number of cases you want to run a USoft application with a general database account and accept application users who do not have direct access to that database account. This is called account funneling: application users effectively share the same general database account.Validation Agent-specific information (password, mpped user Refer to your USoft Authorizer help for information about funneling and and user authentication.
📄️ Dynamic Data Exchange (DDE)
In a Windows environment, applications can communicate using Dynamic Data Exchange. The application that starts the conversation is called the client. The application which responds is called the server. In DDE, the client determines the topic of the conversation and the items that are exchanged, either by sending them to the server or by requesting them from it. The client may also initiate an advise loop in which it asks to be notified each time a particular item changes. USoft Developer is a DDE server and may act as a DDE client.
📄️ USoft as a DDE client
This section describes how to use a USoft application as a DDE Client. This involves starting and finishing the conversation, requesting and sending items, executing commands, and running advise loops in order to be notified when a certain item changes.
📄️ USoft as a DDE server
USoft Developer can act as a DDE server for your own C programs. Such "clients" may converse with it about two topics: Field and SQL.
📄️ Microsoft Transaction Server (MTS)
Microsoft Transaction Server (MTS) is a component-based transaction processing system for building, deploying, and administering Internet and Intranet server applications. The MTS programming model provides a transaction coordination framework for developing components that encapsulate business logic. In Windows XP, MTS and Microsoft's Component Object Model (COM) are unified in COM+.
📄️ MTS Example 1: The Bank Sample application
In this example, an MTS component connects to the Rules Engine via the USoft Remote Rules Service API. Microsoft provides the Bank Sample application as an example with the installation of MTS. To use this sample with USoft:
📄️ MTS Example 2: component sample code
The sample code below shows what an MTS component usually looks like. To make a connection, ADO is used, but you can also use the OLE-DB or the ODBC API. You should use these APIs as for a normal connection to a database. The 'Commit' or 'Rollback' call must be replaced by the SetComplete or SetAbort call of the context object. The code of the Bank Sample application components is also provided with the Sample Bank application. You can use this to obtain more details.