![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section presents details of the unshared state failover sequence. Detailed configuration information is provided in Configuring Clients for Unshared State Connections.Figure 27 Unshared State FailoverClients with unshared state connections automatically connect to B after losing the connection to A.Figure 28 illustrates the dual state failover process.Figure 28 Dual State Failover ProcessIn this example, servers A1 and A2 share state. Servers B1 and B2 also share state. However, A1 and A2 do not share state with B1 and B2.The EMS clients created connections using unshared state connection factories. The initial server connections were with server A1. When the connection to A1 failed, the failover process proceeded as described in Shared State Failover Process, and the clients connect to A2.A2 then failed, before A1 restarted. The clients next created connections to B1, recreating all runtime objects from the connection (as described above in Unshared State Failover Process). B1 is now the current server. Because B1 and B2 share state, If B1 fails, B2 becomes the current server.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |