TOMCAT/TOMCAT64 is a web server appliance based on the Sun Java machine and Apache Tomcat, a Java Servlet and Java Server Pages container developed under the Apache License. The main documentation for Tomcat is at tomcat.apache.org. Tomcat provides standards-compliant support for Servlets and JSPs. Tomcat can work as standalone web server or as application server.

TOMCAT serves static web content, automatically deploys web applications, executes servlets and Java Server Pages from a user-configurable content volume. The paths to the documents are configurable, so that the same volume can be shared between multiple web servers and/or other appliances serving different content.

WEB serves static web content and executes scripts from a user-configurable read-only content volume. The paths to the documents and scripts are configurable, so that the same volume can be shared between multiple web servers and/or other appliances serving different content.

WEBx4 serves static web content and executes scripts from a user-configurable read-only content volume. The paths to the documents and scripts are configurable, so that the same volume can be shared between multiple web servers and/or other appliances serving different content.

WEBx8 serves static web content and executes scripts from a user-configurable read-only content volume. The paths to the documents and scripts are configurable, so that the same volume can be shared between multiple web servers and/or other appliances serving different content.

MYSQL5/MYSQL64 is a database appliance based on the MySQL database engine (http://www.mysql.org). It provides an easy way to add a database to any application.

MYSQL stores the database on an application-defined volume that can be configured on each MYSQL instance. MYSQL automatically creates an empty database when it starts on an empty volume.

MYSQLR is a database appliance based on the MySQL database engine (http://www.mysql.org). It provides an easy way to add a database to any application. The appliance can also be used in complex MYSQL replication scenarios. The appliance is based on MYSQL5 (CentOS 5/MySQL 5) but also handles database replication.

Database replication enables data from one MySQL database server (known as "master") to be replicated to one or more MySQL database servers (known as "slaves"). The MYSQLR appliance can be setup for master-slave as well as master-master replication and replication with more than two masters.

The replication setup, management and monitoring is done via a web interface. The web interface provides an easy way to start replication with close to zero downtime on the master. It can also be used to repair a replication in case of problems. The web interface can be used for copying databases from older database appliances like MYSQL and MYSQL5. MYSQLR also provides an easy way for managing and browsing your database (based on phpMyAdmin).

PGSQL/PGSQL64 is a database appliance based on the PostgreSQLdatabase engine (http://www.postgresql.org). It provides an easy way to add a database to any application. PGSQL is an enterprise-style database appliance that supports many features that are currently not supported by the MYSQLx appliances. Some of these features include stored procedures, triggers, views and user-defined data types.

The NAS appliance (Samba + HTTP interface) is a shared file storage appliance. It provides file storage accessible over HTTP, NFS, and CIFS file protocols.

The NAS appliance serves files contained within a configured (pluggable) data volume thus providing the ability for the content served by the appliance to be changed easily as well as the ability for the volume to have varied sizes. For example, if NAS is being used to store log files, the data volume does not need to be as large as what may be needed to store content for an apache server.

Load generation is controlled through a simple web interface (GUI) exposed by LOAD. The GUI is accessed through the ctl terminal. The GUI also displays historical results of load generation.

PS8 (Scalable port switch) is a switch for distributing TCP and UDP traffic to different outputs depending on the TCP/UDP port number.

The switch is cascadable; traffic that is not TCP, UDP or doesn't match parameterized port numbers is forwarded out the aux terminal.

HALB (Session-aware HTTP load balancer based on HA Proxy) is a switch for distributing workload to multiple Web servers of the same or different type. HALB is based on the HAProxy TCP/HTTP load balancing software package; which is designed to be extremely fast while consuming little resources.

RPL (Event Replicator) is a replicator for events. It replicates HTTP requests received on its input terminal to all its output terminals.

RPL sends any headers and documents received with the request to the outputs. RPL ignores the responses from the output requests, including possible failures to send the request. RPL always returns SUCCESS for recognized HTTP requests on its input, without waiting for any of the outputs to respond. For requests that require a document to be returned, RPL returns an empty document.

IN (Input gateway with firewalls - iptables) is an input gateway that provides a firewalled entry point for network traffic into an application.

IN accepts all allowed incoming traffic on its external interface and passes it through its out terminal. IN forwards only the traffic explicitly allowed through configuration of its firewall properties; IN discards all disallowed traffic.

IN supports up to 4 incoming interfaces (protocol/pair combinations), such as http, ssh, etc. By default, IN allows only tcp port 80 (http).

IN is used to accept all network traffic for applications. All external traffic must pass through an IN gateway to access any resources or services within an application.

The INSSL (HTTP gateway with SSL support) appliance is a layer-7 gateway for secure HTTP requests. It converts the requests to unencoded HTTP requests. This can be used whenever it is necessary to support secure HTTP on the client's side, but the back-end processing infrastructure does not or cannot support SSL, including:

• using a fast and light-weight HTTP server that does not have SSL support
• using multiple back-end servers, for performance or for redundancy, connected through a load-balancing switch
• using multiple back-end servers for unrelated functions, connected through a URL switch
• offloading the SSL encryption/decryption to a separate server to improve throughput

The INSSLR (Redundant HTTP input gateway with SSL support) appliance is a layer-7 gateway for secure HTTP requests. It converts the requests to unencoded HTTP requests. This can be used whenever it is necessary to support secure HTTP on the client's side, but the back-end processing infrastructure does not or cannot support SSL, including:

• using a fast and light-weight HTTP server that does not have SSL support
• using multiple back-end servers, for performance or for redundancy, connected through a load-balancing switch
• using multiple back-end servers for unrelated functions, connected through a URL switch
• offloading the SSL encryption/decryption to a separate server to improve throughput

OUT (Single host output gateway with firewall - iptables) is an output gateway that provides access to a network host located outside of an application. OUT accepts traffic from the application on its in terminal and forwards it through its external interface to the remote host.

OUT has a firewall that allows only outgoing traffic (connections and datagrams); it drops incoming traffic that is not for an already established connection or related to a datagram request.

NET (Network output gateway with firewall - iptables) is an output gateway that provides outgoing access to a network outside of an application. NET accepts traffic from the application on its in terminal and forwards it through its external interface to the outside network (e.g., the Internet).

NET has a firewall that allows only outgoing traffic (connections and datagrams); it drops incoming traffic that is not for an already established connection or related to a datagram request. NET can be configured to further limit the set of IP addresses reachable through it.