3.10.5 Configuration where only a single SFO server exists in a system (Memory session failover functionality)

This subsection describes the configuration where only a single SFO server exists in the system.

Organization of this subsection
(1) Features of the system configuration
(2) Processes to be invoked on the respective machines

(1) Features of the system configuration

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)

[Figure]

Note: For other legend items, see 3.2 Description of the system configuration.

Features
  • If a problem occurs in a specific J2EE server, the session information can be inherited in another J2EE server.
  • If a problem occurs in the SFO server, the session information cannot be inherited by all J2EE applications running on the system.
Flow of requests
The SFO server manages the global session information present on the J2EE server as redundant information.
When a J2EE server receives a request and a session is established, the global session information present on the SFO server is locked by the filter for the session failover that is present on the J2EE server. When the processing of the J2EE application finishes, the global session information present on the SFO server is updated as per the contents of the global session information present on the J2EE server. After this, the filter for the session failover releases the lock on the global session information present on the SFO server.
If an error occurs in the J2EE server, another J2EE server obtains the global session information present on the SFO server and the session information is inherited.

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

[Figure]

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.

Note
In this configuration, you can handle the process failure in the J2EE server, but you cannot handle the hardware failure on the Application Server 1 machine. To handle hardware failure on the Application Server machine, deploy the SFO server on a separate machine.

(2) Processes to be invoked on the respective machines

The following subsections explain the software and the processes required on the respective machines:

(a) Application server machine

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:

(b) Session failover server machine

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.

(c) Management server machine

You need to install Application Server on the management server machine.

Invoke the following process:

(d) Web client machine

A Web client machine requires a Web browser.