This section describes the system configuration used for inheriting session information. As a prerequisite for this configuration, the J2EE servers have to be made redundant by the load balancer.

The following are the three types of configurations for inheriting session information:

• Configuration using a database (When using the database session failover functionality)
• Configuration using an EADs server (When using the EADs session failover functionality)
  For a configuration using an EADs server, you can use the following two types of configurations:
  
  • Configuration in which the EADs server is allocated to a computer different from the J2EE server
  • Configuration in which the EADs server is allocated to the same computer as the J2EE server
• Configuration using a SFO server (When using the memory session failover functionality)
  You can deploy one or many systems on SFO server when using a configuration with SFO server. To minimize the effect of any error occurring in the SFO server, Hitachi recommends that you deploy one SFO server for one J2EE application. This section describes the following two types of configuration:
  
  • Configuration when many SFO servers exist in a system
  • Configuration when there is only one SFO server in a system

Organization of this section

3.10.1 Configuration using a database (database session failover functionality)

3.10.2 Configuration in which the EADs server is allocated to a computer different from the J2EE server (EADs session failover functionality)

3.10.3 Configuration in which the EADs server is allocated to the same computer as the J2EE server (EADs session failover functionality)

3.10.4 Configuration where many SFO servers exist in a system (Memory session failover functionality)

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