arted, FE is started as a process within the BE SO that the BE initialises the FE as a running process interface. When FE is initialised, BE creates a special session for the FE so that all communication from the FE passes to the BE through this special session. Starting BE and FE in different JVMs means starting BE first and then connecting the FE to the BE. They can be in the same or different machines. When the FE estab- lishes a connection with the BE, then the BE creates a session and the connection from FE is transferred to this session. Henceforth, all the communication from FE to BE takes place through this session. All client requests are communicated only through the socket sessions to the FE server. FE categorises requests as read or write requests. All read requests are directly handled by the FE server and data are fetched from the database. The write request is passed to the BE and then the database is updated. 11.2.11.7 EJB Session Beans Enterprise Java beans (EJB) technology is a distributed component model that enables developers to focus on solving business problems while relying on the J2EE platform to handle system-level issues. The FE server uses stateless session beans which do not maintain any information about the client session. Thus minimum server resources are used when clients are connected. OSS for Telecom Networks Configuration Configuration information information is downloaded is downloaded Figure 11.19 Configuration information is downloaded from the BE server to FE servers. As the FE server's session beans comply with J2EE standards, they can be deployed in a J2EE application server such as WebLogic, JBoss or WebSphere. The configuration management FE server can be configured to use the session beans managed by the EJB Container. When the FE server uses the session beans from the EJB container, the server is said to be running in "EJB mode". In this mode, the ses- sion beans are deployed in the EJB container of any of the application servers and the EJB client looks up these bean