Terms and Abbreviations
• Standard Server
A FOXMAN-UN machine that is not configured to use the Main/Standby Solution.
• Main Server
A FOXMAN-UN machine that is configured to make use of the Main/Standby Solution and is configured to act as a Main Server (which runs under normal circumstances).
• Standby Server
A FOXMAN-UN machine that is configured to make use of the Main/Standby Solution and is configured to act as a Standby Server (which runs under the circumstances that the Main Server is broken).
• Cold Standby Server
A Standby Server that is ready to be activated by an operator in case of Main Server breakdown.
• Warm Standby Server
A Standby Server that is automatically activated in case of Main Server breakdown.
• Partner Server
Main and Standby Server always build a pair of two. Thus, a Standby Server acts as Partner Server of its assigned Main Server and vice versa. A Main Server can have more than one Standby Server as a partner, but a Standby Server can always only have one Main Server as a partner (one to many relationship).
• Local Client
A FOXMAN-UN Client that comes installed together with a FOXMAN-UN Server. Thus, both Server and Client are running on the same physical machine.
• Remote Client
A FOXMAN-UN Client that is installed without a FOXMAN-UN Server. Thus, the Client is running remote of the FOXMAN-UN Server.
• NEM Base Services
A number of FOXMAN-UN services (Linux services) providing a base service infrastructure needed by superordinate FOXMAN-UN services.
• NEM Core Services
A number of FOXMAN-UN services (Linux services) providing a higher-level application infrastructure. NEM core services can only be executed if NEM base services are already running.