In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Application Server
    This chapter includes information on setting up application server definitions used with the Progress AppServer.
    Progress AppServer
    Explains how the Progress AppServer works.
    Defining the AppServer
    Explains how to use AppServer Service Maintenance (36.19.1).
    Example: Using an AppServer to Run MRP
    Gives a walkthrough of how to set up an AppServer to improve MRP performance, with details on modifying the properties file, configuring the AppServer, and starting and stopping AppServers.
    Progress AppServer
    The Progress Open Application Server, or AppServer, is a brokered collection of 4GL engines that can execute Progress programs on the server in response to remote client requests. Each AppServer instance is identified by a unique name, and contains a broker that manages a pool of 4GL engine processes, each of which is available for processing client requests.
    The client connects to an AppServer indirectly through the Progress Name Server. This provides for location transparency (and also provides the logical basis for load balancing and failover) since the clients do not need to know the host and port of the AppServer broker. The client only needs to know the unique name of the AppServer broker, which is used by the Name Server to determine the broker’s host and port.
    Each AppServer instance can be configured to have its own set of parameter values, such as the PROPATH, database connections, startup/shutdown procedures, and log files. These parameter values are specified in the ubroker.properties file, located in the DLC\properties directory, where DLC is the Progress installation directory.
    See the Progress documentation for more information on setting up and using AppServers.
    One extremely useful example of the AppServer is to improve the throughput speed of the processing-intensive task of running material requirements planning (MRP). The AppServer can distribute processing load across multiple threads, dramatically improving performance.
    See User Guide: Manufacturing for information on MRP.
    As an example of how an AppServer can be used, this chapter includes instructions for setting up an AppServer to support enhanced MRP performance.
    Before you can run applications using a Progress AppServer, the AppServer instance must be defined in AppServer Service Maintenance (36.19.1).