Distributed application servers
To distribute load over multiple application servers, Enterprise Server supports the AS and MAS concept, having one Master Application Server and one or more Application Servers.
For the installation and configuration of the application server, see Infor LN Installation Guide
The purpose of the AS/MAS concept is to support an environment of distributed application servers, while limiting the effect on maintenance as much as possible. In principle, only the MAS must be updated in case of software updates. Application servers automatically retrieve the required software components and configuration files from the MAS during runtime. Only a porting set update must be installed on all application servers.
An application server has all the required processes running locally, such as the bshell, database drivers, printer drivers, and service processes (such as shared memory manager and shared memory timer). Application and configuration data (such as database configuration information, application objects, and user data) are retrieved from the master application server.
The application server is aware of the master application server through
the
BSE_REM variable. You set this variable during the
installation of the application server and it is stored in the
$BSE/lib/bse_vars file. The
BSE_REM identifies the MAS host and BSE path.
If an
Enterprise Server-related
process on the application server requires configuration files, objects, or
other file types, the network layer of that process first searches for these
files in the regular way on the local system. If this file is not found
locally, the network layer checks if a
BSE_REM variable is set, and, if so, uses that value to
search for the file on the indicated remote host (the MAS). This requires the
fs process to be running on the MAS. If the
fs process is not running yet, the application server
process starts the process.