This section will cover the deployment of Web Server. There are three basic scenarios for deployment, which are as follows.
- Standalone
-
In a standalone implementation, the Web Server hosts the scripts and customized process and transaction logic. It communicates directly with both SAP and the client platform (eg. Access or WebUI). In a standalone environment, the dispatcher is not necessary.
- Load-Balancing
-
The Web Server can be used either in a single server environment or as part of a load-balancing configuration that might involve multiple servers running simultaneously. Load-balancing can be done either in a standalone environment or in a NetWeaver environment. In a load-balancing environment with multiple Web Servers, the primary Web Server will house the scripts; the other Web Servers will simply use the scripts to enable multiple connections via the Web. In this case, the SAPProxy.ini file is configured to allow for multiple proxy servers and the Dispatcher will direct traffic as needed. For more detailed information about the Dispatcher, please see the Dispatcher.js and Load Balancing sections.
- NetWeaver
-
In a NetWeaver implementation, the Web Server functions within the NetWeaver platform as an iView. For more detailed information on using Web Server with an iView, please see the SAP Portals with iView (Enterprise Portals section).
The Web Server can be used with several different clients, including Access, WebUI, WSOffice, and the new Liquid UI FTE solution.
- Access: In an Access Suite implementation, the Web Server will function in conjunction with the Access smart phone client. The Access client resides on a supported smart phone such as iPhone or BlackBerry. The Web Server in this implementation will house the scripts and customized processes and transactions for the smart phone platform. The Web Server will parse requests to SAP from the client, removing the screen and process modifications before forwarding the request to SAP. Once the request is answered, Web Server will re-apply the modifications before forwarding the response to the client.
- WebUI: In this implementation, the GuiXT Web Server is serving up customized processes and screens to a web browser.
- WS Office: When enabling the migration of bulk data from PDF forms to SAP, the Web Server is necessary to handle the POST-ed PDF forms. In this scenario, the Web Server will handle the POST-ed forms, and then deliver them to SAP.
