PILATO Respected Contributor.
Respected Contributor.
598 views

OO in cluster mode - how to configure LoadBalancer

Jump to solution

Hello

I want to configure OO in cluster mode.

I will use a LoadBalancer to redirect users and requests from OMi  between the two central servers. 

For the loadbalancer configuration I need to define the KeepAlive URL. What is the KeepAlive URL for OO ? is it http://<server_name>/oo ?

 

thanks 

regards

Vincent

 

Labels (1)
0 Likes
1 Solution

Accepted Solutions
EASJosh Respected Contributor.
Respected Contributor.

Re: OO in cluster mode - how to configure LoadBalancer

Jump to solution

Hi Vincent,

That should be correct, yes, with the addition of the port number, IE https://<server_name>:8443/oo/.

More information on this is on page 86 onwards of the 10.60 Central User Guide.

Cheers,
Josh


--------------------------------------
If my post helped you, please click the 'Kudos' button.
0 Likes
4 Replies
EASJosh Respected Contributor.
Respected Contributor.

Re: OO in cluster mode - how to configure LoadBalancer

Jump to solution

Hi Vincent,

That should be correct, yes, with the addition of the port number, IE https://<server_name>:8443/oo/.

More information on this is on page 86 onwards of the 10.60 Central User Guide.

Cheers,
Josh


--------------------------------------
If my post helped you, please click the 'Kudos' button.
0 Likes
PILATO Respected Contributor.
Respected Contributor.

Re: OO in cluster mode - how to configure LoadBalancer

Jump to solution

Thanks

 

I've just found in Architecture guide the keepAlive URL and the configuration of LB :

 

For the HPE OO user interface and customer portals, the virtual IP should use a sticky session policy. The sticky session ensures that all subsequent requests will be sent to the server that handled the first login request. This means that users will only need to log in to the HPE OO interface once. l For RASes, the virtual IP should use a round robin policy, to distribute the load across the different servers. Note: If you have a different configuration that satisfies these requirements, it is okay to use it. For example, if you have a load balancer that supports JSESSION, you can use the JSESSIONID parameter to set up a single virtual IP with a sticky session policy for all sources. Since RAS requests are stateless (no JSESSIONID), this will provide a round robin policy for RASes.

Central uses the following URL to check which server is live: HTTP://:/oo/hello.html

0 Likes
Bijeshvenugopal Absent Member.
Absent Member.

Re: OO in cluster mode - how to configure LoadBalancer

Jump to solution

Hi

In the Architecture guide it's mention as "Sticky Session Policy", so its of what  type, like Sticky Source IP , Destination IP etc.

 

Regards

Bijesh V

0 Likes
AndreiTruta Outstanding Contributor.
Outstanding Contributor.

Re: OO in cluster mode - how to configure LoadBalancer

Jump to solution

You can find further info if needed in this old post too:

/t5/Grounded-in-the-Cloud/Configuring-an-Active-Active-cluster-for-HP-Operations/ba-p/6699990#.WKQiUDt963Y

that will actually get you more information once you end up here:

https://lnast01pcache.saas.hpe.com/asset/resources/pd/oo/1zi1459950151/OnBoarding_-_OO_Cluster_v1.0.pdf

Andrei Vasile Truta
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.