High Availability Application Architecture
High availability application architecture is the process that is followed when implementing a new configuration into an existing ERP[clarification needed] system. The architecture contains three stages: 1)Development, 2)Quality Assurance, and 3)Production. All three of these stages must pass through the transport directory before the following stage can be executed. This entire process is used to eliminate downtime when implementing an application.
This definition must be broken into two parts in order to be fully understood. "High availability is a design and implementation that ensures a certain degree of operational continuity." Application architecture is the second part, which refers to the actual concept and design of implementing a new configuration into the particular system.
In the IT world minimizing downtime is very important, and in order to implement a new configuration into an existing computer system one must follow strict architectural guidelines before releasing the new configuration into production. Following the application architecture guidelines will greatly reduce the potential downtime when implementing a new configuration into an existing system.
Stages of Architecture
As afore mentioned, there are three stages that an application most go through before it "goes live." All three of these stages pass through the transport directory before going on to the next stage.
The final stage that the application enters is the production stage, which entails the actual system that a company runs its business on.
The transport directory serves as a compiler for all of the changes to the application that occur through the stages. This component is the mechanism that allows the changes to be tracked from stage to stage. When the application is released for production, it will be delivered out of the transport directory.
|This section is empty. You can help by adding to it. (July 2010)|
2. MARATHON everRun http://en.wikipedia.org/wiki/Marathon_Technologies