This subsection describes the configuration where many SFO servers exist in a system.
Prepare an SFO server for each J2EE application running on the J2EE server. We recommend that you deploy the J2EE application and the SFO server in a one-to-one relationship. This can help to minimize the effect of a problem occurring in the SFO server. On the other hand, if a single SFO server is deployed for multiple J2EE applications, you cannot inherit the session information of all the J2EE applications corresponding to that SFO server when an error occurs in the SFO server.
SFO server applications run on the SFO server.
The following figure shows an example configuration when multiple SFO servers exist in a system. In this example, the SFO servers and the J2EE servers are deployed on different machines. In this configuration, the machines with the SFO servers deployed, are called the session failover servers.
Figure 3-51 Example configuration when multiple SFO servers exist in a system
Note: For other legend items, see 3.2 Description of the system configuration.
The following subsections explain the software and the processes required on the respective machines:
The required software and the processes to be invoked when using the memory session failover functionality differ in each system configuration, depending on the function that is used. Deploy the required software and the processes as per the functions used.
You need to install Application Server on the session failover server machine.
Invoke the following processes:
You need to install Application Server on the management server machine.
Invoke the following process:
A Web client machine requires a Web browser.