s during the normal functioning of the EJB client. This client is referred to as an EJB client that looks up the session beans from the application server using the Java Naming and Directory Interface (JNDI) name. The operator starts the FE server in EJB mode and connects the EJB clients. 11.2.11.8 Dynamic Downloading of Configuration Files In a distributed environment, where we have a single BE server and multiple FE servers, it may be necessary to change the configuration of a number of FE servers. Rather than reconfiguring FE servers one-by-one, it will be easier to make the changes in a centralised location and for the change to be propagated across all FE servers and their clients. To allow this, the configuration information of the FE server and its client is held only in the BE server. This information is downloaded to the FE server when the FE server is connected to the BE server and when the client is connected to the FE server. 11.2.11.9 Proxy APIs Proxy APIs are the Remote Method Invocation (RMI) APIs bound in the FE server with the implementation for the same interfaces as that in BE server's RMI registry. Proxy APIs serve three main purposes: To overcome the security restriction of the applet used by the client. The Java- implemented security policy may restrict a client applet's RMI look-up capabil- ities to a host other than the applet's code base. In that case, the applet in the client that is downloaded from the FE server would be unable to look up the APIs in the BE server if the BE server is running in a different machine from the FE server. The applet can get handles for RMI APIs in the FE server. It is then useful 11 Configuration Management Proxy Client Applet Figure 11.20 Client applet invokes methods from proxy APIs. for proxy APIs with methods that are equivalent to the APIs in BE to be provided in the FE server. The client applet may then invoke methods in the FE and achieve the desired functions. 2. For any read operation, the client's request to the proxy API is sent directly to the da