This subsection describes the configuration where only a single SFO server exists in the system.
Provide a single SFO server for the multiple J2EE applications running on the J2EE server.
SFO server applications run on the SFO server.
The following figure shows an example configuration when only a single SFO server exists in the system. In this example, the SFO server and the J2EE servers are deployed on different machines.
Figure 3-52 Example configuration when only a single SFO server exists in a system (when a session failover server is deployed)
Note: For other legend items, see 3.2 Description of the system configuration.
You can deploy the SFO server on the same machine as the J2EE server.
The following figure shows an example configuration with the SFO server deployed on the same machine as the J2EE server:
Figure 3-53 Example configuration with the SFO server deployed on the same machine as the J2EE server
Note: For other legend items, see 3.2 Description of the system configuration.
The features and flow of requests are similar to the deployment of the session failover server as a separate machine.
The following subsections explain the software and the processes required on the respective machines:
The required software and the processes invoked when using the session failover function are different for each system configuration, depending on the function used. Deploy the required software and processes as per the functions used.
Invoke the following process when the SFO server is deployed in the same machine as the J2EE server:
You need to install Application Server on the session failover server machine.
Invoke the following processes:
If the SFO server is deployed on the same machine as the J2EE server, you do not need the session failover server machine.
You need to install Application Server on the management server machine.
Invoke the following process:
A Web client machine requires a Web browser.