Tymeac^™ Requirements

Product

Standard Edition  (J2EE and J2SE)

Micro Edition  (J2ME)

 

Standard Edition

Server

Tymeac^™ runs on any computer that minimally supports Java^™ Standard Edition, version 1.1 for releases prior to 4.x

Release 6.0 runs on Java^™ Standard Edition,
version 1.6 minimally.

Release 5.5 runs on Java^™ Standard Edition,
version 1.5 minimally.

Release 4.x runs on Java^™ Standard Edition,
version 1.4.2 minimally.

Release 3.x runs on Java^™ Standard Edition,
version 1.1 minimally.

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 application.
                through RMI from an applet.
                through Jini from an application.
                embedded within an application.

Environment

Tymeac^™ runs in these 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.
• Custom Socket Factories are supported.

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.

As a Portable Object Adapter (IIOP) Server using the ORB Daemon:

The requirements are SDK1.4.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 ORB Daemon.
• 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 Naming Service

As a Jini^™ Service

The requirements are SDK1.4.0, minimally and Jini 2.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 a Jini look up service.
• 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 look up Service

2. Activatable Remote Object (both RMI and Jini^™) :

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.
• Custom Socket Factories are supported.

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^™ needs to keep the Tymeac^™ Functions and Queues in permanent storage. There are two supported modes: DBMS and Stand-Alone.

DBMS Mode requires a relational data base management system, a JDBC driver for that data base and either preference data or 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.

Micro Edition

Server

Tymeac^™ runs on any computer that minimally supports Java^™ Micro Edition (CLDC), version 1.0. This is the "K" Virtual Machine.

Release 1.1 supports floating point arithmetic

Tymeac^™, for the Demonstration System (for a workstation supplied with the Product) requires approximately 200K of memory. The Demonstration is for all the features of the system. A customized version naturally takes up far less memory. The amount of computer memory, for a user system, depends on the number of Functions, Queues, and Threads.

Tymeac^™ requires disk storage on a workstation for the Classes, Samples, and Documentation of approximately 2MB.

Client access:

Embedded within an application.

Environment

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 any object.
• Tymeac^™ Server remains active until shut down.