Can someone explain how to set up multiple SM 9.6x application servers to use an HWLB

[OnaBrink]

I have recently upgraded our SM 9.50 system and the application server was originally configured for software vertical load blancing. I want to configure 2 application servers at 2 different locations using a spanned vlan and VIP on an HWLB (citrix netscaler) with 300 concurrent connections each. SM 9.6x documentation supports this for an F5, but it is not clearly explained. The documentation even has 2 great diagrams, but no detail. The documentation also states that if using an HWLB, you cannot use software load balancing. How could I get 300 concurrent connections if the max for a single servlet is 100.  This means I would need multiple vm servers instead of using servlets. I still wonder where and how the license file is referenced. If the license file is sitting on one server and only referenced on one server, that server is a single point of failure. This means Service Manager cannot ever be configured for high availability. If that one host goes down, no other connections can be made, which also means users connected to that host are dropped and can't be regained. Has anyone done this and if so, how? Samples of an SM.ini and SM.cfg file would be helpful as well.

[BAGAss]

there are two scalable methods
vertical (on one server)
and
horizontal (on some servers)
which one do u interesting?

[OnaBrink]

I am not referring to the software load balancing that is part of SM. I am referring to using a hardware load balancer to horizontally load balance the application server and support high availability.

[Sean Almond]

https://docs.microfocus.com/SM/9.61/Hybrid/Content/serversetup/tasks/Communicate_to_SM_via_F5_in1.htm?Highlight=hwlb

[OnaBrink]

Thank you. I have seen and read the documentation supplied by Micro Focus, but it does not explain where the license file resides or how it is referenced by the license manager.

If the license manager resides on a single node as in a software load balancer and that node fails, it would still be a single point of failure. Especially, since the license is locked to a single IP. If that is true, it doesn't really matter if an HWLB is used or not. One purpose of an HWLB is to have high availaibility and resiliency. Can someone explain how to obtain high availailability with SM application servers?

[kchamberlin]

Hi,  I'm looking for the same information as I'm about to attempt the HWLB configuration as well.  I'm  particularly interested in the scaling on each individual App server if SWLB isnt supported vertically.  Have you made any progress with this.  Documentation is Lacking to say the least!

[Madddy · Accepted solution]

you can generate license on any server, even if the server(license IP) fails, your application will be running. License IT is considered only during the start up.

you can test the same