In my previous post - WebLogic Load Balancing for Oracle ADF Applications, I have described how to setup cluster environment with a set of WebLogic Managed Servers together with separate WebLogic domain for Load-Balancing. Today I will describe, how to enable In-Memory replication in cluster environment.
Load-Balancing allows to distribute user sessions across cluster elements, based on current server load. However, if one of Managed Servers from cluster will go down, all the sessions on this server will be destroyed and users will loose their work. In order to avoid this, WebLogic server allows to enable replication between Managed Servers in cluster. In this blog I'm describing In-Memory HTTP replication.
You can enable session replication, basically by adding one parameter into weblogic.xml file. You should edit weblogic.xml available in your Oracle ADF application, if you don't have this file - create it in WEB-INF folder:
Specify PersistentStoreType parameter and set replicated as value:
All required configuration is done, now you can deploy application on WebLogic cluster. Here I'm accessing ADF Faces Rich Client page through Load-Balancing domain:
Load-Balancing domain have redirected to a second Managed Server, I have pressed Save button on application page couple of times, you can see it from the server log:
I have killed second Managed Server:
I didn't closed my browser and have pressed Save button again - without replication I would get server error, however now my session is successfully transferred to the next available Managed Server from cluster environment - its third server:
You can see from the log - Save operation was successfully done. User didn't lost his session and can continue work:
En post anteriores, Andrejus nos había mostrado como configurar nuestras aplicaciones hechas con ADF para poder soportar el balanceo de carga en los servidores WEB Logic. En esta oportunidad, se muestra como mejorar esta configuración y permitir el aseguramiento de las sesiones de las aplicaciones (en balanceo de carga) ante una caida en uno de los servidores.