Architecture
The Cloverleaf Integration Services (CIS) engine script can run on a variety of Windows and UNIX platforms. This engine receives messages from external systems through protocols such as TCP/IP, FTP, and Fileset. It then performs transformations on the messages, and sends the messages to their destination through any of the same set of supported protocols.
The Cloverleaf engine records statistics to shared memory, where it can be accessed by a separate monitor daemon process. This daemon makes these statistics available to the host server through TCP/IP and ultimately available to users running the Cloverleaf IDE through the host server. The daemon also provides an alert mechanism, which can alert the user when user-defined trigger conditions occur.
The Cloverleaf host server acts as a bridge between any number of Cloverleaf IDEs and the engine and monitor Daemon. The host server interacts with the Cloverleaf IDE through RMI and accesses the Cloverleaf engine through the local file system and monitor daemon through TCP/IP.
Advanced security can be configured through the Cloverleaf security server. Residing on a separate machine from any host servers accessing it, the security server keeps access control lists on an embedded Derby database. Whenever a user attempts to perform a task, the host server queries the security server through RMI. It does this to determine whether the user has permission to perform the task.