Hi All,
I am trying the use case where the replicated back-end application needs to be protected via ISAM.
In order to try this use case, I created two Websphere profiles and deployed the application on both the profiles. Also, I created a junction pointing to both the servers.
WebSEAL sends the user request to any back-end application and works as a load balancer. To stick to one of the replicated back-end applications, through-out the user session, I modified the junction to stateful.
Now the use cases I wanted to try is:
If any of the back-end servers go down then
1. The user connected to it via session must be redirected to other replicated servers and users need not login again.
2. User current state must be maintained even though user requests are redirected to the replicated back-end applications.
I went through the documentation and the configuration steps that I observed are related to replicated WebSEAL instance and not the back-end applications.
The confusion I have is whether there is a need for additional configuration on Websphere Application Server or I just need to play with WebSEAL instance configurations? and How?
Do I need to implement the SSO first?
Regards,
Prashant Narkhede
------------------------------
Prashant Narkhede
------------------------------