MainFrame Architecture

The DragonFly server executes on the MainFrame as a started task or batch job. The key is that each DragonFly instance runs in its own address space on any Logical Partition (LPAR) with a TCPIP stack. This allows safe application isolation where each developer can have his or her own environment. This architecture holds for the production environment as well. Releasing a new application does not pose a threat to existing applications on other instances provided the data is not shared. Multiple versions of the DragonFly server (IE V1.2 and V1.3 ) can run simultaneously. The installation is responsible for ensuring that safe development practices are adhered to when the sharing of a common DB2 subsystem, table or VSAM file occurs.

Each DragonFly instance may have its own HTML source or it may share the HTML source with any other DragonFly instance of the same version. Likewise, the CGI programs can be shared or isolated. These features are enabled in any server instance on an LPAR sharing Direct Access Storage Devices (DASD). Each of these servers may reference any other instance including different versions using a hyperlink in HTML.

A single application may span multiple server instances. This is valuable if you require only portions of an application down for maintenance or batch processing.

The differentiating device used to separate the different instances of these servers is a combination of the TCPIP address and the PORT#. These parameters are supplied by the installation at startup time.

The DragonFly server can use any port number. We recommend setting up standards in your shop to avoid interference with any other TCPIP applications you may have.

The DragonFly server V1.30 accepts communication from Web Browsers including the DragonFly Web Browsers.

© 1999 Tyson Systems Inc. All rights reserved.