Refer attached, how do we configure the Web Plugins on WAS because normally there is no load balancer in between IBM HTTP server and WAS.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
3 replies Latest Post - 2012-06-13T03:19:52Z by JayBlue
Pinned topic Configure IBM HTTP Server plugin via Load Balancer
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-06-13T03:19:52Z at 2012-06-13T03:19:52Z by JayBlue
SreekanthP 270002SMDN5 PostsACCEPTED ANSWER
Re: Configure IBM HTTP Server plugin via Load Balancer2012-06-12T12:33:03Z in response to JayBlueHi Jay,
I know of a configuration like the one in my attachement.
Not really very sure why would you need a another load balancer between the WAS nodes and IHS. The IHS plugin can do the request load balancing. So, for me it looks like a redundant step.
Sunit 100000DWFV194 PostsACCEPTED ANSWER
Re: Configure IBM HTTP Server plugin via Load Balancer2012-06-12T13:20:13Z in response to JayBlueIf you are using WAS ND then you do not need load balancer between IHS and WAS. You create a cluster of two WAS instances, deploy the app to the cluster. WAS Plugin will take care load balancing and session affinity plus WAS ND cluster will allow you to replicate sessions.
JayBlue 270005DWVB2 PostsACCEPTED ANSWER
Re: Configure IBM HTTP Server plugin via Load Balancer2012-06-13T03:19:52Z in response to JayBlueHi Guys,
Basically this setup for our IBM FileNet P8 implementation, we dont use clustering for WAS because we using WAS 7 standard and this WAS server is Application Engine servers. The IHS is used for End user to access FileNet application directly, and load balancer is used for other component of FileNet and also integration from other applications to connect this Application Engine.Because this solution is design by IBM and I have limited knowledge about IHS and WAS. Now I understand.
Thanks a lot.