Tymeac Requirements

divider

Computer

Tymeac runs on any computer that minimally supports Java Standard Edition, version 1.1. This includes version 1.2 and 1.4 (also known as Java2.)  

Tymeac, for the Demonstration System (supplied with the Product) requires approximately 2MB of memory. The amount of computer memory, for a user system, naturally depends on the number of Functions, Queues, and Threads.

Tymeac requires disk storage for the Classes, Samples, and Documentation of approximately 6.0MB.

Client access:

J2EE --    through RMI from a servlet.
                embedded within a servlet.
J2SE --    through RMI from an applicaction.
                through RMI from an applet.
                embedded within an application.

Environment

Tymeac runs in three environments:

  1. As a non-Activatable Remote Object,
  2. an Activatable Remote Object and
  3. an internal non-RMI Server.

1. Non-Activatable Remote Object:

As an RMI Server using the RMI Registry:

The requirements are JDK1.1, minimally.
The attributes are:

  • Tymeac Server is started as a new process from an operating system command line.
  • A reference to the Remote Object is registered with the RMI Registry.
  • Tymeac Server remains active until shut down either by request or an operating system action.
  • Tymeac Clients retrieve a reference to the Tymeac Server through the RMI Registry.

As an RMI-IIOP Server using the JNDI Registry:

The requirements are SDK1.3.0, minimally.
The attributes are:

  • Tymeac Server is started as a new process from an operating system command line.
  • A reference to the Remote Object is registered with the CosNaming Server.
  • Tymeac Server remains active until shut down either by request or an operating system action.
  • Tymeac Clients retrieve a reference to the Tymeac Server through the JNDI Registry.

2. Activatable Remote Object:

The requirements are SDK 1.2,  minimally.
The attributes are:

  • Tymeac is started by the Activation System, (rmid), when either first required (lazy) or when the Activation System starts (restart.)
  • Requires registration with the Activation System by a front end process (user-written class).
  • A reference to the Remote Object is registered with the RMI Registry and the Java RMI Activation System Daemon.
  • A reference to the Remote Object may be wrapped in a proxy and the proxy registered with a Jini Lookup Service.
  • A reference to the Remote Object may remain within the back-end, (activatable remote object) process of a Jini Service so that remote clients are unaware of Tymeac functionality.
  • Remains active until:
    • Shut down either by request or an operating system action.
    • When lazy activation specified, when the inactive time expires.
    • When restart activation specified, when the Activation System stops.
  • Communication between Tymeac Server and Tymeac Clients is through:
    • The RMI Registry.
    • Jini Lookup Service.
    • Within the Jini Service back-end process.

3. Internal Non-RMI Server:

The requirements are SDK 1.2,  minimally, (when using the J2SE GUI windows otherwise JDK 1.1).
The attributes are:

  • Tymeac is started by your application.
  • A reference to the Server is returned by the createServer() method.
  • Your application calls methods on the Server similarly as with a remote object.
  • Tymeac Server remains active until shut down.

Mode

Tymeac functions in two modes: DBMS and Stand-Alone.

DBMS Mode requires a relational data base management system, a JDBC driver for that data base and one local file:

  • To store the Tymeac Functions and Queues.
  • To store the Tymeac run time log and statistics.
  • Access to one local file for start up variables and the names of the DBMS Tables.

Stand-Alone Mode is without a DBMS or access to a local file. This mode is ideal for small servers or anytime when limiting access to resources is necessary.

  • The user maintains the Tymeac Functions and Queues in User Classes.
  • In all other respects this mode functions the same as DBMS Mode.
  • The Demonstration System (supplied with the Product) is an example of Stand-Alone Mode.