Introduction to OpenFrame

OpenFrame is a rehosting solution that migrates mainframe applications and data to an open system with minimum modifications and redevelopment efforts.

Before migration, it is important to consider the preservation of application logic, which is an important company asset and knowledge, in addition to the conversion of existing data and business applications. Moving data and applications can be costly and risky as redeveloping legacy source code that has been optimized for older hardware can introduce bugs and inconsistencies. Although difficult and expensive, it has become a necessity for businesses to integrate existing mainframes with new technology as mainframes are rapidly becoming obsolete and unable to adapt to rapidly changing business requirements.

OpenFrame allows the reuse of existing applications and data in an open system, greatly reducing the conversion cost and time and preserving important application logic.

When migrating from a mainframe to an open system with OpenFrame, existing application logic and processes can be reused with little modification. This allows the migration process to be completed in a relatively short period of time. It also prevents the inevitable system instability caused by a full redevelopment and the time-consuming troubleshooting efforts to fix these instabilities.

A key component of OpenFrame is the Tmax TP monitor, a program that monitors and manages transactions. Many TmaxSoft customers have successfully used Tmax and Tmax provides services that are missing in other rehosting products. Tmax engine updates can be applied to OpenFrame as needed to ensure a top-notch performance.

OpenFrame can be used in any business sector where mainframes are currently used.

Because business markets are rapidly changing, companies that require new application logic might first lean towards the Big Bang method instead of rehosting. However, it is not difficult to expand application functions or integrate with new business environments such as the Internet after rehosting with OpenFrame. OpenFrame can be used to rehost any mission critical applications while maintaining the existing applications and avoiding the side-effects of a full redevelopment.

OpenFrame offers many features that make it an excellent choice for a rehosting solution.

A rehosting solution that merely moves mainframe applications to an open system environment is of little use. A rehosting solution needs to provide levels of stability and performance that match or exceed those of the mainframe.

Because it is built on the powerful, market-verified Tmax TP monitor, OpenFrame can provide a stable and efficient migration process as well as transaction processing environment.

Most rehosting solutions provide suitable environments for either online or batch applications, not both. Therefore, in traditional rehosting projects, software from multiple vendors must be used to provide a complete business environment.

OpenFrame, however, is a comprehensive rehosting solution that provides all the components needed to facilitate the operation of both online and batch applications in an open system.

Integration may not be a critical issue immediately after mainframe rehosting. However, as the needs to expand the business application system or integrate with other systems rises, OpenFrame provides superior functionality compared to other rehosting vendors.

Tmax integrates with other commercial X/Open DTP XA-compliant transaction processing monitors, such as Tuxedo. Tmax ensures that OpenFrame-based systems can connect to most external tools, programs, and systems.

Additionally, OpenFrame can integrate seamlessly and reliably with the web by incorporating TmaxSoft’s advanced Web Application Server (WAS), JEUS^®(JEUS). OpenFrame modules are implemented on TP-Monitor and WAS, which are the latest technologies for an open environment, that allow OpenFrame to support next-generation systems. By employing standards-based TP-Monitor and WAS technologies, OpenFrame supports high scalability and compatibility with other systems.

When rehosting, two or more machines are typically used to achieve the performance of the existing mainframe system. In this situation, a rehosting solution must distribute system load between the machines and handle any hardware failures. OpenFrame provides both load distribution and failure recovery features to allow full and efficient use of system resources.

OpenFrame systems are usually comprised of multiple real or virtual nodes that are linked together to form a multi-node environment called a domain. If the system frequently experiences high loads, more nodes can be added to the system so that other nodes can partially or fully take over when a node is overloaded or fails.

Tmax provides powerful load balancing features that enable transaction requests to be distributed among the nodes of the system. The following diagram shows three load distribution methods.

The following diagram shows the recovery process of a failed node.

As mentioned already, OpenFrame systems are typically composed of multiple real or virtual nodes linked together in a peer-to-peer relationship. These nodes monitor each another, enabling the system to quickly react to a node failure. This peer-to-peer relationship enables multiple backups to be configured and strengthens both software and hardware fault tolerance.

As shown in the previous diagram, both Node 1 and Node 2 are capable of processing the same applications. If Node 1 experiences a software failure while processing Work 1, Node 2 can receive all subsequent transaction requests for Work 1. The failed server process in Node 1 can then be restarted.

OpenFrame systems can also recover from hardware or network failures as follows:

If an unexpected failure occurs, Tmax detects the failure and attempts to restart the failed server. However, if a node cannot be fully recovered, all requests directed to the failed node will be automatically forwarded to another node to ensure continuity of service.

As shown in the previous figure, if there is a network failure, and clients cannot connect to Node 1 to request deposit transactions; in this case, Tmax will automatically detect this failure and establish a connection to Node 2 instead. Subsequent deposit transaction requests will then be routed to Node 2.

Most rehosting solutions use inefficient and overly-complex scripts such as the UNIX shell to implement JCL.

In contrast, OpenFrame incorporates an advanced JCL processing engine called TJES that can run JCL files without modification.

You can monitor all server processes and trace their transactions from end to end in an OpenFrame system. Tmax module enables you to monitor a wide range of system statistics that can be adjusted to improve system performance.

Rehosting with OpenFrame offers the following additional benefits:

The following table compares mainframe system components with their OpenFrame counterparts.

The goal of rehosting is to migrate mainframe applications to an open system without any modification to the original business logic. Therefore, OpenFrame has been designed with components that look and function comparably to those of the mainframe. In OpenFrame manuals, many functions are described in relation to their mainframe counterparts. For this reason, OpenFrame users should be familiar with some basic mainframe components and terminology.

The following is a brief list of mainframe terminology. A more complete list can be found in the "Glossary" with a list of OpenFrame terminology.