The TwineBall server uses a database created in DB2 to store data. This server can handle many different entity definitions, but the tables most often used are:
Figure 1 shows the TwineBall architecture.
Figure
1. Original TwineBall architecture
Event delivery is provided by a polling mechanism. For polling to work, the user must create event and archive tables in DB2, and triggers must also be in place.
The adapter and ODA each connect to this server via Java RMI. The adapter and ODA each take a server URL that represents the server name, port, and service name.
The standard server URL is RMI://localhost:2112/TwineBall.
Alternately, the TwineBall adapter can run independent of the server. In this case it calls an alternate implementation of the TwineBall API, written in C++. The adapter will load a C++ shared library and call into that instead of making remote RMI calls. For more information refer to Using JNI.
The TwineBall server components are listed below.
The adapter components are listed below.
The ODA components are listed below.