Sticky load balancing without clustering?

I don't need any type of session replication. I just want to run two
          instances of Weblogic on one machine, one IP, two different ports.
          If I run a third instance of Weblogic for proxying on the same machine
          on yet another port, can I take advantage of the HttpClusterServlet's
          sticky load balancing capabilities if the two Weblogic instances I want
          to proxy between are not participating in a cluster?
          All we require is to have an IP & port that we can hit that will
          round-robin the HTTP requests between the two Weblogic instances, and
          send all subsequent HTTP requests with the same session to the same
          Weblogic instance it sent it to before. Can this work? Thanks in
          advance,
          mg
          Mike Gorman, Director of Architecture
          YOUcentric, Inc.
          Charlotte, NC
          704-643-1000 x518
          http://www.youcentric.com

Thought I read somewhere that you must have different IP addresses for each
          server
          Mike Gorman wrote:
          > I don't need any type of session replication. I just want to run two
          > instances of Weblogic on one machine, one IP, two different ports.
          >
          > If I run a third instance of Weblogic for proxying on the same machine
          > on yet another port, can I take advantage of the HttpClusterServlet's
          > sticky load balancing capabilities if the two Weblogic instances I want
          > to proxy between are not participating in a cluster?
          >
          > All we require is to have an IP & port that we can hit that will
          > round-robin the HTTP requests between the two Weblogic instances, and
          > send all subsequent HTTP requests with the same session to the same
          > Weblogic instance it sent it to before. Can this work? Thanks in
          > advance,
          >
          > mg
          >
          > --
          > Mike Gorman, Director of Architecture
          > YOUcentric, Inc.
          > Charlotte, NC
          > 704-643-1000 x518
          > http://www.youcentric.com

Similar Messages

How to make IIS plug-in do STICKY load balancing

There are two classes of scalable services: pure and sticky. A pure service
is one where any instance of the application can respond to client requests.
A sticky service is one where a client sends its requests to the same
instance; those requests are not redirected to other instances.
It seems to me that weblogic IIS proxy plug-in does not support the sticky
load balancing.
Could someone give me some information on how to make the proxy sticky?
Is there configuration parameters for this?
Thanks,
-Lei

I set the cluster.
It seems to me that there is some problem with the Set-Cookie mechanism of
the plug-in.
Sometime it set the cookie in my browser, sometime it is not.
Even from the wlproxy.log, I could set something like
Fri Aug 03 17:56:12 2001 Hdrs to
client:[Set-Cookie]=[AribaNode=O2tII92qHlP2tpZjUV0m5ued1s6X028cUPu24QcGj1Q25
AE5VXOd!1782877802312707887!ltang.ariba.com!8001!7002; domain=ariba.com;
path=/]
But the cookie is not set in my browser, what might be wrong here?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
I do believe that this will not work since if clustering is not enabled, a
cookie will not be set on the browser that contains the primary and
secondary server.
You are specifying two different ports in your servers. You need to use
clustering in order to get this functionality with the plugin.Furthermore,
you will achieve fail-over.
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
Here is what I did for the examples under the bea sample directory.
I put the following in test1/WEB-INF/weblogic.xml
<session-descriptor>
<session-param>
<param-name> CookieDomain </param-name>
<param-value> *.ariba.com </param-value>
</session-param>
<session-param>
<param-name> CookieName </param-name>
<param-value> AribaNode </param-value>
</session-param>
<session-param>
<param-name> CookiePath </param-name>
<param-value> /test1 </param-value>
</session-param>
</session-descriptor>
</weblogic-web-app>
I add the following in iisproxy.ini
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicCluster=ltang.ariba.com:8001,achu.ariba.com:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test1
DynamicServerList=OFF
CookieName=AribaNode
I use SesssionServlet.java as an example
When I involk http://proxy/test1/SessionServlet, I always get 1
if I use
http://proxy/test1/SessionServlet:AribaNode=................................
I could see the session becomes sticky.
If I do not want to use URL rewriting, what should I do in order to makethe
session STICKY
for this example.
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
If you leave the CookieName untouched on the WebLogic side, then there
should be no reason to make the change in the plug-in.
But yes, you need to make sure the cookie names are the same.
Regards,
Eric
"Mark Vaughn" <[email protected]> wrote in message
news:[email protected]...
Actually, you also need to make sure you set the "CookieName" in theplugin.
That let's the plugin read the cookie set by WebLogic to determine
who
the
primary and secondary servers are for that session. Otherwise, theplugin
has no
way of knowing if you are establishing a new session or returning to
an
existing
one. The cookie will tell it if you have a current session and who
it
should
send you to for continuing that session, or failing that session
over.
>>>>
Eric Gross wrote:
Without having clustering enabled, you will not get Sticky load
balancing.
You need to have clustering so that a cookie is sent back to the
client
that
contains information about where it's session is located.
Otherwise,
you
are just going to get round-robin each time.
You can refer to the following page for more information:
http://e-docs.beasys.com/wls/docs61/cluster/servlet.html
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
WebLogicCluster=machine1:7001,machine2:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test,/test1
DynamicServerList=OFF
I run two standone (Admin server) weblogic servers on machine1
machine2.
Then I deploy application test.war on machine1 first, then onmachine2.
Should I make machine2 as a managed server and machine1 as an
admi
n
server?
Will this make the session sticky?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
It would help us to know how you have iisproxy.ini configured.
Sticky
load
balancing should work fine if you have the plug-in and
WebLogic
Server
setup
correctly.
How have you setup the plug-in?
Thanks,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
There are two classes of scalable services: pure and sticky.
A
pure
service
is one where any instance of the application can respond to
client
requests.
A sticky service is one where a client sends its requests to
the
same
instance; those requests are not redirected to other
instances.
It seems to me that weblogic IIS proxy plug-in does notsupport
the
sticky
load balancing.
Could someone give me some information on how to make the
proxy
sticky?
Is there configuration parameters for this?
Thanks,
-Lei
.-. Mark Vaughn
/V\ 7024 Corona Dr.
// \\ North Richland Hills, TX 76180
/( )\ [email protected]
^^-^^
"Give a man a fish and you feed him for a day;
teach him to use the Net and he won't bother you for weeks."
Ben Woodbridge

IPlanet sticky load balancing question

We have two iPlanet Application Servers v6.0 sp3 and two iPlanet
Enterprise Web servers v4.1. All machines are on the same domain name.
All machines point to the same LDAP server. The application has been
installed on both App servers. Clustering has been configured in the
App server Admin tool to be based upon system load. For non-sticky load
balancing, all works fine, and session information is carried over
properly. However, for sticky load balancing, hits going into either of
the Web servers do not always go back to the App server that first
started the session.
The online iPlanet documentation says it can be done, but we have found
differently. Has anybody else gotten this to work?
Thank you,
David Shade

Hi David,
With sticky load balancing enabled, when you execute the application first
time it will go to any kjs depending on your load banancing criteria which
you set (Round robin or server responce or whatever), this applies to only
for the first time when you send request, afterwords it will be executed in
that perticular KJS process only till that KJS is alive, whatever may be
your LoadB creteria.
You please kill that kjs and see, you will be able to see the failover.
Feel free to mail me for any further information.
Sanjeev,
Developer Support Team iAS-India.
David Shade wrote:
We have two iPlanet Application Servers v6.0 sp3 and two iPlanet
Enterprise Web servers v4.1. All machines are on the same domain name.
All machines point to the same LDAP server. The application has been
installed on both App servers. Clustering has been configured in the
App server Admin tool to be based upon system load. For non-sticky load
balancing, all works fine, and session information is carried over
properly. However, for sticky load balancing, hits going into either of
the Web servers do not always go back to the App server that first
started the session.
The online iPlanet documentation says it can be done, but we have found
differently. Has anybody else gotten this to work?
Thank you,
David Shade--
I have never learn not to learn...
------------------------------------------------------------------

Sticky Load balancing

Does WLS 5.1 supports Sticky Load Balancing?
          Thank you.
          Rob.


http://www.weblogic.com/docs51/classdocs/javadocs/weblogic/rmi/extensions/CallRouter.html
          - Prasad
          Rob wrote:
          > Looking at the online docs from BEA I found something that I think is what I
          > need. it is called Parameter-based routing
          >
          > It seems that WebLogic Clusters supports several algorithms to address this
          > kind of Load balancing. (something like sticky load balancing)
          >
          > The next text is from the online BEA's docs:
          >
          > Parameter-based routing
          >
          > It is also possible to gain finer grain control over load-balancing. Any
          > clustered object can be assigned a CallRouter. This is a plug-in that is
          > called before each invocation with the parameters of the call. The
          > CallRouter is free to examine the parameters and return the name server to
          > which the call should be routed.
          >
          > If this is correct (that this type of load balancing is slightly the same as
          > sticky load balancing) then the questions is now:
          >
          > What is exactly a CallRouter and where can I see an example of this or more
          > documentation.
          >
          > Rob wrote in message <[email protected]>...
          > >Does WLS 5.1 supports Sticky Load Balancing?
          > >
          > >Thank you.
          > >
          > >Rob.
          > >
          > >
          Cheers
          - Prasad

Can't get sticky load balancing to work

I'm really puzzled why sticky LB is not working for a simple case I'm trying. I have two simple JSP's, both registered (see web.xml and ias-web.xml below). I'm using lite session and set distributable to false. Just in case someone can tell by just looking at my session id if it's supposed to be sticky or not, it looks like following -
GXLiteSessionID-4818869464307751325
My two JSP's are also attached below, and they're pretty simple. A new session is supposed to be created in login page and clicking on the logout page invalidates the session.
What I see is that each request (whether login or logout) is randomly sent to any server. For example, if I go to login once, further request to login or logout (whether through refresh or by clicking on the link) is not necessarily sent to the same server.
Any idea what's missing in my setup? I've tried different types of load balancing (round robin, etc.) so I know that's not it.
Thanks a lot in advance.
Jitu
-----web.xml-------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN' 'http://java.sun.com/j2ee/dtds/web-app_2_2.dtd'>
<web-app>
<display-name>WebDesk</display-name>
<distributable>false</distributable>
<servlet>
<servlet-name>TestLogin.jsp</servlet-name>
<jsp-file>TestLogin.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>TestLogin.jsp</servlet-name>
<url-pattern>TestLogin.jsp</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>TestLogout.jsp</servlet-name>
<jsp-file>TestLogout.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>TestLogout.jsp</servlet-name>
<url-pattern>TestLogout.jsp</url-pattern>
</servlet-mapping>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name></realm-name>
<form-login-config>
<form-login-page></form-login-page>
<form-error-page></form-error-page>
</form-login-config>
</login-config>
</web-app>
-----ias-web.xml------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ias-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD iAS Web Application 1.0//EN' 'http://developer.iplanet.com/appserver/dtds/IASWebApp_1_0.dtd'>
<ias-web-app>
<servlet>
<servlet-name>TestLogin.jsp</servlet-name>
<guid>{A6D6B277-288D-1C22-C3CA-0800209A2F7C}</guid>
<servlet-info>
<sticky>true</sticky>
<sticky-lb>true</sticky-lb>
</servlet-info>
</servlet>
<servlet>
<servlet-name>TestLogout.jsp</servlet-name>
<guid>{B88B7D19-28B9-1C22-EE63-0800209A2F7C}</guid>
<servlet-info>
<sticky>true</sticky>
<sticky-lb>true</sticky-lb>
</servlet-info>
</servlet>
<session-info>
<impl>lite</impl>
<timeout-type>last-access</timeout-type>
<timeout>60</timeout>
<secure>false</secure>
<domain></domain>
<path>/</path>
<scope></scope>
</session-info>
</ias-web-app>
-----TestLogin.jsp-------
<%
     java.util.Date date = new java.util.Date();
     HttpSession sess = request.getSession(true);
     System.out.println(date + ":TestLogin.jsp: sessionid = " + sess.getId() + ", new = " + sess.isNew());
%>
<HTML>
<HEAD>
<TITLE>TestLogin</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" topmargin=0 leftmargin=0 marginwidth=0 marginheight=0>
<p>
You are now logged in.<br>
<br>
TestLogin.jsp: sessionid = <%=sess.getId()%>, new = <%=sess.isNew()%><br>
<br>
Click here to logout.
</BODY>
</HTML>
----TestLogout.jsp-------
<%
     java.util.Date date = new java.util.Date();
     HttpSession sess = request.getSession(true);
     System.out.println(date + ":TestLogout.jsp: sessionid = " + sess.getId() + ", new = " + sess.isNew());
%>
<HTML>
<HEAD>
<TITLE>TestLogout</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" topmargin=0 leftmargin=0 marginwidth=0 marginheight=0>
<p>
TestLogout.jsp: sessionid = <%=sess.getId()%>, new = <%=sess.isNew()%><br>
<br>
<%
sess.invalidate();
%>
You are now logged out.<br>
<br>
Click here to login.
</BODY>
</HTML>

Hi,
I think it's best to wait for sometime and check the behaviour of sticky load balancing for sometime, the reason being one or more of the following...
- Although sticky feature ensures that the component is run at a single server, when combined with load balancing and under heavy user loads, the load balancing takes place.
- If we rule out the previous case, then, the load balancing mechanism, especially, per component based or per server based, sends request by round robin technique initally(around 128 times or so) and then calculates the effeciency of the response time and then follows the per server based or per component based.
- Meanwhile please ensure that, you have enabled the Sticky LB option under Application using iASAT and please wait for sometime sending requests(probably 130 times) after which it's good to check the mechanism of the sticky bit technique. If it doesn't behaves as it has to then, please let me know and I can help you further on this.
Regards
RG

NAS 4.0sp6 - sticky load balancing

Hi,
Can anyone tell me if sticky load balancing is required/necessary in a
multi process (8 x kjs's) single threaded (each kjs has only one thread)
environment on one machine. We seem to be getting concurrent session
problems between kjs's.
Platform: Solaris 2.6, NAS 4.0sp6
Thanks in advance.

In general no, but it depends on how your application is written.
In your case, probably yes, but I am only guessing here.
Session is usually distributed through DSYNC and therefore is
serialisable. However, if certain programmers made their objects
non-seriable then they are forcing the sessions to be stored locally and
sticky will help with sending the requests back to the same engine to
get that session.
In your case, I wonder why you are only using 1 thread per kjs. I assume
your application code is not thread safe and therefore you made the
decision to run multiple kjs with single thread only. Following this, I
believe you might also have programmatically made your sessions
local/non ditributable (because of the thread safe issue), thus if this
is the case you probably will require sticky load balancing.
Tosh wrote:
>
Hi,
Can anyone tell me if sticky load balancing is required/necessary in a
multi process (8 x kjs's) single threaded (each kjs has only one thread)
environment on one machine. We seem to be getting concurrent session
problems between kjs's.
Platform: Solaris 2.6, NAS 4.0sp6
Thanks in advance.--
Han-Dat Luc ([email protected])
Senior Consultant
SUN Professional Services (iPlanet)
o .
o .
O _ ____ _ _
(_) _ \| | __ _ _ __ ___| |_ TM
| | |_) | |/ _` | '_ \ / _ \ __|
| | __/| | (_| | | | | __/ |_
|_|_| |_|\__,_|_| |_|\___|\__|
e-commerce solutions
Sun Microsystems Australia Pty Ltd

Load balancing without a cluster...!!!!????

Hi boys!
          I have a question for you: my NES proxy server can realize a load
          balancing between 2 weblogic 6.0 servers that are NOT IN A CLUSTER?
          I've done some tests configuring the obj.conf like the 2 weblogic
          servers were in cluster, but I dont' understand if it works correctly.
          May be I ask too much ...
          Thanks
          Patrizia


          I'm assuming your using one browser to test this.
          The first time you access a servlet or a JSP that uses session
          tracking, the WL server will store a cookie in the browser. This
          cookie identifies the IP address and port number of the WLS where
          the request was executed (the Primary), and if it is a clustered
          configuation with session replication enable, also a Secondary
          server.
          The next time you make a request to iPlanet (or Apache), wlproxy
          looks at the cookie and directs you to the same WL server - so
          you won't see any load balancing.
          If you quit out of all your browsers, then start a new browser,
          and access it again, you won't have a WL cookie, and the request
          will get load balanced to one of the WL servers.
          Mike
          Patrizia MB <[email protected]> wrote:
          >Thanks Mike,
          >but I've some problems in verifying what you've asserted.
          >In my obj.conf I've put
          >
          > <Object name="wl" ppath="*/servlet/*">
          >
          > Service fn="wl-proxy" WebLogicCluster="10.0.0.3:7060,10.0.0.8:7060"
          >DebugConfigInfo="ON" Debug="ON"
          >
          > </Object>
          >
          >Note that I have 2 NOT-Clustered WLS instances behind
          >NES: I used
          >the "WebLogicCluster" property in the obj.conf only because
          >this
          >is the only way - as far as I know ! - to specify multiple
          >nodes to the
          >proxy.
          >
          >
          >With your suggestion, accessing the URL
          >"http://<your-nes-server>/?__WebLogicBridgeConfigInfo"
          >I can see this:
          > Query String: '__WebLogicBridgeConfig'
          > This entry is cluster aware.
          > ClusterID (from obj.conf): "10.0.0.3:7060,10.0.0.8:7060"
          > WebLogic Cluster List:
          > 1.Host: '10.0.0.8' Port: 7060 Primary
          > General Server List:
          > 1.Host: '10.0.0.3' Port: 7060
          > 2.Host: '10.0.0.8' Port: 7060
          >
          >
          >
          >
          >
          >In spite of that, there's no load-balancing!
          >I checked the 2 access files on the 2 nodes, and I see
          >that all my
          >requests go to the same server 10.0.0.8.
          >Why?
          >According to which logic 10.0.0.8 has been defined the
          >Primary? (They
          >are both Administration Servers)
          >
          >I hope you'll answer to my questions!
          >
          >TIA
          >
          >Patrizia
          >
          >
          >
          >
          >
          >
          >Mike Reiche wrote:
          >
          >> The wlproxy for NES will round-robin requests to multiple
          >WL
          >> servers if they are clustered or not clustered.
          >>
          >> You can get some additional information by adding the
          >property
          >> DebugConfigInfo=ON to the WL configuration in obj.conf
          >then
          >> hitting the URL...
          >> http://<your-nes-server>/?__WebLogicBridgeConfigInfo
          >>
          >> Check the WL NSAPI doc.
          >>
          >> Mike
          >>
          >> Monteforte Patrizia <[email protected]>
          >wrote:
          >> >Hi boys!
          >> >I have a question for you: my NES proxy server can
          >realize
          >> >a load
          >> >balancing between 2 weblogic 6.0 servers that are
          >NOT
          >> >IN A CLUSTER?
          >> >I've done some tests configuring the obj.conf like
          >the
          >> >2 weblogic
          >> >servers were in cluster, but I dont' understand if
          >it
          >> >works correctly.
          >> >May be I ask too much ...
          >> >
          >> >Thanks
          >> >
          >> >Patrizia
          >> >
          >

Load Balancing in Clustered Weblogic 12c

Hi,
Weblogic.........: 12.1.3
OS..................: Oracle Enterprise Linux 6.3
We have configured a Clustered Weblogic (2 virtual servers) successfully. Now we are searching for some good Load Balancing solutions. I've tested a ProxyServlet, but it didin't really solve the question, because this kind of load balancing only balances apps in the same server.
Is it mandatory to use a third-party solution, like an Apache Httpd Server, or Big IP? In fact, i would like to know initially for some viable solutions to provide a load balancing solution to a 2-server Weblogic 12c Solution.
Thanks in advance.

Hi,
It is not manadatory, and it is possible to load balance apps on different servers with the ProxyServlet. It's only that this will be running on a server from where the others need to be accesable.
Also, it depends on what you are using this environment for. The ProxyServlet is a good solution if you want to replicate an Enterprise environment and test the load balancing with a WebLogic cluster. However, if you want to run Production applications in this environment, then consider the above suggestions: either a WebServer or a dedicated external Load Balancer.
Regards

Load balancing and clustering in sharepoint

Hi,
Still i am confuse about load balancing with cluster in sharepoint level.please let me know how to install and troubleshoot,how it is work, Advantage, etc..
Thanks,
Inguru

Hi Inguru,
Per my knowledge, SharePoint only supports Load balancing and SQL support clustering.
Here is a similar thread for you to take a look:
http://social.technet.microsoft.com/Forums/en-US/2b20d1d5-de35-486e-9b0e-37222a307615/clustering-and-load-balancing?forum=sharepointgeneralprevious
To configure load balancing for SharePoint, please follow the links below:
http://blogs.technet.com/b/praveenh/archive/2010/12/17/setting-up-load-balancing-on-a-sharepoint-farm-running-on-windows-server-2008.aspx
http://community.bamboosolutions.com/blogs/sharepoint-2013/archive/2014/01/07/network-load-balancing-for-sharepoint-2013-part-three-installing-network-load-balancing-on-wfe1-in-a-three-server-farm.aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Load balancing and clustering for SQL SERVER ANALYSIS SERVER instances to access large number of concurrent users for bi site

HI
how to do analysis server clustering
we have sharepoint bi site and we published many dashboards pointers ,filters kpis
and at a time some 200 to 300 concurrent users access these dashboards pages
so for maintain this requirement how we apply clustering for ssas intances
and also it has load balancing
adil

Hi Adil,
According to your description, you want to implement SQL Server Analysis Services Clusster and Analysis Services Load Balancing, right?
In SSAS, we can design highly available solutions in Analysis Services by using: network load balancing (NLB) technologies, failover clustering technologies, or both. For the details about implemention, please refer to the links below.
http://msdn.microsoft.com/en-us/library/dn736073.aspx
http://sqlsrvanalysissrvcs.codeplex.com/wikipage?title=Analysis%20Services%20Load%20Balancing
http://technet.microsoft.com/en-us/library/bb500217(v=sql.105).aspx
Regards,
Charlie Liao
TechNet Community Support

Sticky load balancing across 2 ports with cookies

Hi,
I have a server configuration where I have 1 top level Apache server that deals with SSL termination (and handles static content) and proxy passes dynamic content onto 2 Tomcat servers on 2 ports, one for http requests (9001) and one for the requests that were secure, but have now been un-encrypted by Apache (9002). My 2 Tomcat servers are load balanced using a CSS and I need this load balancing to stick to the tomcat servers regardless of port so that the user is stuck to the same Tomcat server for their entire session.
I would like to use arrowpoint cookies to perform this stickyness, but the documentation suggests that arrowpoint cookie load balancing (in fact any cookie based load balancing) requires the port to be specified in the content rule. Is this correct? Is my only option to use the source IP for stickyness? I don't understand why the port should be required if the stickyness is via a cookie. Can I not simply configure my 2 tomcat servers as services with no port and add a single content rule that load balances these services using arrowpoint-cookie advanced balancing?
service tomcat1
ip address x.x.x.x
active
service tomcat2
ip address x.x.x.x
active
owner me
   content sticky
     vip address x.x.x.x
     protocol tcp
     url "/*"
     add service tomcat-1
     add service tomcat-2
     advanced-balance arrowpoint-cookie
     active

Angela-
The issue with port is that cookies are very specifically HTTP only and the CSS has no way of knowing what protocol will hit a VIP prior to trying to address it as HTTP. Your issue is actually a bit clearer than it is initially led to be - you can still use 2 different rules by using the configuration below.
However, you might be headed for a headache if you don't implicitly control the client's actions. By default, browsers don't generally send cookies cross-protocol and definitely not cross-domain. Use something like httpwatch or iewatch to check out the headers your client sends to your site. Make sure when the 200ok arrives with the set-cookie that the client sends that cookie in all preceeding packets that are HTTP and HTTPS both.
service tomcat1
string "tomcat1"
ip address x.x.x.x
active
service tomcat2
string "tomcat2"
ip address x.x.x.x
active
owner me
   content sticky9001
     vip address x.x.x.x
     protocol tcp
     url "/*"
     port 9001
     add service tomcat-1
     add service tomcat-2
     advanced-balance arrowpoint-cookie
     active
   content sticky9002
     vip address x.x.x.x
     protocol tcp
     url "/*"
     port 9002
     add service tomcat-1
     add service tomcat-2
     advanced-balance arrowpoint-cookie
     active
With this configuration, the CSS will use the "string" as the cookie value. So if the client were to recieve set-cookie: ArrowpointCookie=tomcat1, it should use it for either rule, and end up on tomcat1 accessing either VIP.
Regards,
Chris

Load balancing and clustered MDBs using a Queue

With the following advice/information from
          http://e-docs.bea.com/wls/docs61/faq/jms.html#252978,
          "One customer had an example where topic MDBs are needed in which there will
          be multiple implementations of the MDBs listening on the same topic. In
          other words, more than one MDB with a different implementation may be
          subscribing to the same topic. The client has no advanced way of knowing how
          many different kinds of MDBs may be listening on the same topic, but it is
          possible for there to be more than one listener, therefore topics, not
          queues. For each kind of MDB listening on the topic, the message is
          delivered exactly once (i.e., the message will be delivered exactly once to
          an instance in each named MDB pool listening on the topic)."
          If I have a set of MDB's scraping Messages from the JMS Queue, what is the
          load-balancing behavior?
          1) Consider a lightly-loaded system, where each MDB has sufficient time to
          process the message before the next one shows up in the queue. Will the same
          MDB get all the messages?
          2) Consider a heavily-loaded system, where each MDB has insufficient time to
          process the message before the next one shows up in the queue. How would you
          characterize the de facto load-balancing behavior? least-loaded?


Have you tried the SAP WebDispatcher. This should acomplish what you want.
http://help.sap.com/saphelp_nw04/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm

Load Balancing and Clustering

How can I connect to my cluster rather than a single
server in the cluster? I have 3 instances of WLS running on the same machine, and I can connect to these three servers separately (the login.jsp page). However, when I shutdown one of them, the page cannot be displayed, which means that I was connected to the server and not the cluster.
To understand it better following is the configuration details which i am having:
1. Admin Server running on 7001 port.
2. Three server instances(Trade1,Trade2,Trade3) are running on TradeCluster having same ip address (127.0.0.1) and different port number 8001,8011,8021 respectively.
3. Trade application can be accesses via (127.0.0.1:8001 or 127.0.0.1:8011 or 127.0.0.1:8021) separately.
If server Trade1 is getting down in that case 127.0.0.1:8001 is showing "page can not be displayed". I tried to use "HttpClusterServlet" for load balancing but it was not working. How i can access application through ome common URL and how can a configure load balancing.
Can anybody help me find out what I might have missed.
TIA
Sunil

Hi,
we need to specify the cluster information in web.xml like
<web-app>
<servlet>
<servlet-name>HttpClusterServlet</servlet-name>
<servlet-class>
weblogic.servlet.proxy.HttpClusterServlet
</servlet-class>
<init-param>
<param-name>WebLogicCluster</param-name>
<param-value>
hostname1:7736|hostname2:7736|hostname:7736
</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.jsp</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>HttpClusterServlet</servlet-name>
<url-pattern>*.html</url-pattern>
</servlet-mapping>
</web-app>
and deploy the application target to cluster
Prasanna Yalam

Network Load Balancing without DNS

Good day,
I am planning on deploying four 2008R2 RDS servers using Microsoft's NLB in a Hyper-V virtual environment. My question is do I require AD DNS to be able to create & access this load balanced group of servers? My challenge is that I have 20
remote offices that connect via RDP to RDS servers at our main site. The remote offices connect to the main site over the Internet via VPN, and the PC's in these remote sites aren't members of the main site's AD environment (due to bandwidth constraints).
DNS at the main site can include the name of the NLB group of servers, but this wouldn't be available at any of these remote offices.
My two questions are:
1.) Can I connect from any of my remote sites to the NLB servers at the main site via virtual IP address of the NLB?
2.) Can I connect to INDIVIDUAL servers (for maintenance reasons) that belong to the NLB servers via their assigned IP address?
Thanks for your help!
- Joe

Hi Andrew,
Thank you for posting in Windows Server Forum.
Agree with TP’s comment, in addition you can refer below article for information.
How To Work with RD Gateway in Windows Server 2012
http://redmondmag.com/Articles/2013/12/24/RD-Gateway-in-Windows-Server.aspx?Page=2
Hope it helps!
Thanks.
Dharmesh Solanki

Sticky load balancing not working because of Address Translation

          This came up before - see below. I don't understand what the
          soltion is/was.
          WL Server puts it's ip address in the WebLogicSession cookie
          which is an internal address 192.168.201.41
          WL proxy knows WL Server only by an external address like 139.141.38.21. Since
          it does not know of any WLS with an IP
          address of 192.168.201.41, it round-robins the request instead
          of sending it to the primary WLS.
          Any help is much appreciated.
          Mike Reiche
          Robert Patrick <[email protected]> wrote:
          >Hi,
          >
          >A very typical configuration is to put the web server in the DMZ (i.e.,
          >between
          >an outer and inner firewall) and proxy the requests from the web server
          >to the
          >WebLogic server (which sits behind the inner firewall). Since all of
          >these
          >proxied requests use HTTP and a single port, the only port that needs
          >to be
          >opened in the inner firewall is an HTTP port (the outer firewall will
          >only need
          >an HTTP and/or HTTPS port opened).
          >
          >Hope this helps,
          >Robert
          >
          >Eytan Ben-Meir wrote:
          >
          >> Thanks Patrick,
          >>
          >> May be you can suggest options for securing a WLS behind a firewall?
          >>
          >> Thanks again,
          >>
          >> Eytan
          >>
          >> Robert Patrick wrote:
          >>
          >> > Hi,
          >> >
          >> > The problem is that we encode location information (e.g., IP address(es))
          >> > in the session id. If the plugin sees a session id, it decodes the
          >> > session id to find out where to route the request (i.e., which server
          >in
          >> > the cluster contains the HttpSession object for that session). Since
          >the
          >> > plugin cannot find the machine whose IP address is encoded in the
          >session
          >> > id (because of the network address translation), this will not work.
          > In
          >> > general, distributed application software needs to be modified to
          >be
          >> > capable of handling network address translation -- to my knowledge,
          >> > WebLogic Server has not been modified to support this feature (though
          >the
          >> > Enterprise version of the product has had this support for years).
          >> >
          >> > Hope this helps,
          >> > Robert
          >> >
          >> > Eytan Ben-Meir wrote:
          >> >
          >> > > Hi,
          >> > >
          >> > > Configuration:
          >> > > WLS 4.5.1 on Solaris 2.7 inside a firewall.
          >> > > SonicWall firewall with NAT (Network Address Translation).
          >> > > Netscape Enterprise Server 4.0 outside the firewall with Weblogic
          >> > > NSAPI-BRIDGE (sp 5)
          >> > >
          >> > > The problem:
          >> > > When a browser request is sent to the NE web-erver (directed to
          >the
          >> > > firewall who then redirects to a Weblogic servlet).
          >> > > IF The servlet creates a httpsession (with or without cookies)
          >the
          >> > > request fails (the firewall blocks a request directed directly
          >at the
          >> > > non-routable ip address of the Weblogic machine inside the firewall.
          >> > > IF on the other hand the servlet does not create a http session,
          >all
          >> > > works fine.??????????
          >> > > Does any body know something about this????
          >> > >
          >> > > Thanks,
          >> > >
          >> > > Eytan
          >


          This isn't my problem.
          "Mike Reiche" <[email protected]> wrote:
          >
          >This came up before - see below. I don't understand what the
          >soltion is/was.
          >
          >WL Server puts it's ip address in the WebLogicSession cookie
          > which is an internal address 192.168.201.41
          >
          >WL proxy knows WL Server only by an external address like 139.141.38.21.
          > Since
          >it does not know of any WLS with an IP
          >address of 192.168.201.41, it round-robins the request instead
          >of sending it to the primary WLS.
          >
          >Any help is much appreciated.
          >
          >Mike Reiche
          >
          >Robert Patrick <[email protected]> wrote:
          >>Hi,
          >>
          >>A very typical configuration is to put the web server in the DMZ (i.e.,
          >>between
          >>an outer and inner firewall) and proxy the requests from the web server
          >>to the
          >>WebLogic server (which sits behind the inner firewall). Since all of
          >>these
          >>proxied requests use HTTP and a single port, the only port that needs
          >>to be
          >>opened in the inner firewall is an HTTP port (the outer firewall will
          >>only need
          >>an HTTP and/or HTTPS port opened).
          >>
          >>Hope this helps,
          >>Robert
          >>
          >>Eytan Ben-Meir wrote:
          >>
          >>> Thanks Patrick,
          >>>
          >>> May be you can suggest options for securing a WLS behind a firewall?
          >>>
          >>> Thanks again,
          >>>
          >>> Eytan
          >>>
          >>> Robert Patrick wrote:
          >>>
          >>> > Hi,
          >>> >
          >>> > The problem is that we encode location information (e.g., IP address(es))
          >>> > in the session id. If the plugin sees a session id, it decodes
          >the
          >>> > session id to find out where to route the request (i.e., which server
          >>in
          >>> > the cluster contains the HttpSession object for that session).
          >Since
          >>the
          >>> > plugin cannot find the machine whose IP address is encoded in the
          >>session
          >>> > id (because of the network address translation), this will not work.
          >> In
          >>> > general, distributed application software needs to be modified to
          >>be
          >>> > capable of handling network address translation -- to my knowledge,
          >>> > WebLogic Server has not been modified to support this feature (though
          >>the
          >>> > Enterprise version of the product has had this support for years).
          >>> >
          >>> > Hope this helps,
          >>> > Robert
          >>> >
          >>> > Eytan Ben-Meir wrote:
          >>> >
          >>> > > Hi,
          >>> > >
          >>> > > Configuration:
          >>> > > WLS 4.5.1 on Solaris 2.7 inside a firewall.
          >>> > > SonicWall firewall with NAT (Network Address Translation).
          >>> > > Netscape Enterprise Server 4.0 outside the firewall with Weblogic
          >>> > > NSAPI-BRIDGE (sp 5)
          >>> > >
          >>> > > The problem:
          >>> > > When a browser request is sent to the NE web-erver (directed to
          >>the
          >>> > > firewall who then redirects to a Weblogic servlet).
          >>> > > IF The servlet creates a httpsession (with or without cookies)
          >>the
          >>> > > request fails (the firewall blocks a request directed directly
          >>at the
          >>> > > non-routable ip address of the Weblogic machine inside the firewall.
          >>> > > IF on the other hand the servlet does not create a http session,
          >>all
          >>> > > works fine.??????????
          >>> > > Does any body know something about this????
          >>> > >
          >>> > > Thanks,
          >>> > >
          >>> > > Eytan
          >>
          >

Sticky load balancing without clustering?

Similar Messages

Maybe you are looking for