Clustering VS Load balancing

Hi All,
I want to know the difference between Load Balancing and Clustering.
Mainly i want to choose one of the two for J2E based application and Oracle 10 G database. OS will be Sun Solaris 10.
Regards
Tejas

Similar Messages

BM clustering with load balancing

I want to implement BM clustering with load balancing according to AppNote written by Steve Aitken from March 25, 2005.
It's clear that I need to use two private addresses (from the example, these are 10.10.10.10 and 10.10.10.11). However, I'm not sure what are IP addresses 10.10.10.1 and 10.10.10.2 used for?
Existing BM servers have two NICs: first defined as private and the second as public addresses connected directly to Internet (they are from different subnets).
Sinisa

Originally Posted by phxazcraig
In article <[email protected]>, Tnelson 2000
wrote:
> I've set this up per the appnote and aren't able to get out through any
> of the ip addresses. I get a 504 Gateway Time out error. I also noticed
> that the cluster master ip address is different, 10.10.10.12, for
> example. Do you know what I need to look at to verify I have this
> configured correctly?
>
What do you mean "aren't able to get out through any of the ip
addresses"?
Do the addresses show up in any of the proxy nodes with display secondary
ipaddress? Does the proxy console option 17 show the server listening on
those addresses?
Is the gateway timeout error a BorderManager (or Windows) error? If
BMgr, then check that BMgr has a correct default gateway, DNS is working
(option 4 on proxy console screen) and try dropping filters for a test.
Craig Johnson
Novell Knowledge Partner
*** For a current patch list, tips, handy files and books on
BorderManager, go to Craig Johnson Consulting - BorderManager, NetWare, and More ***
Got it working. I noticed that my dns setting in BM2 didn't coincide with settings in BM1. So, I made them the same and reinitialized the system on both servers. Of course, when I did that, it added the secondary IP addresses. So, I'm really not sure what was stopping it from working before, unless I have something misconfigured that's preventing the secondary addresses from loading. Go figure.

Difference between Clustering and Load balancing

          What is the difference between Clustering and Load balancing?
          For example, We use Cisco Arrowpoint to do load balancing and it works fine for 3
          Sun solaris boxes/WebLogic 6.1 SP1.
          So what is the value addition to buy clustering license?
          Thanks
          Selvaraj


Hi.
          Among other things, clustering allows you to share app data (such as http session
          data) across cluster members, allowing you to failover should one cluster member
          crash.
          If your app is stateless then this doesn't mean much - load balancing alone would
          probably be ok for you.
          Regards,
          Michael
          Selvaraji wrote:
          > What is the difference between Clustering and Load balancing?
          >
          > For example, We use Cisco Arrowpoint to do load balancing and it works fine for 3
          > Sun solaris boxes/WebLogic 6.1 SP1.
          >
          > So what is the value addition to buy clustering license?
          >
          > Thanks
          >
          > Selvaraj
          Michael Young
          Developer Relations Engineer
          BEA Support

Clustering not Load balancing on solaris with apache

apache weblogic plugin does not do round-robin , it's kind of random when
          direct the request to the appserver. anyone has seen this problem?
          weblogic5.1 sp9. solaris 2.7 jre1.3.1 rc2


Actually, the random load-balancing when using Apache is caused by the fact
          that Apache (<2.0) spawns multiple processes, so single Apache instance
          will have several plug-in instances running.
          Mike Reiche <[email protected]> wrote:
          > You are using the weblogic plug-in, aren't you?
          > Only new requests are round-robinned. A second request from the same browser
          > is sent to the same server it hit the first time (sticky load-balancing).
          > Mike
          > "Tony Lu" <[email protected]> wrote:
          >>apache weblogic plugin does not do round-robin , it's kind of random
          >>when
          >>direct the request to the appserver. anyone has seen this problem?
          >>
          >>weblogic5.1 sp9. solaris 2.7 jre1.3.1 rc2
          >>
          >>
          Dimitri

Clustering for load balancing only

I wish to set up 2 WLS 8.1 machines to run an application independently to
          share load (no replication of sessions, beans etc).
          Can I create a cluster for the two servers and not turn on any session or
          bean replication, then configure the IIS or Apache plug-in to use the
          cluster and therefore create some load balancing?
          Chris


Chris,
          Yes you can certainly use a Cluster simply for load balancing. There is no
          mandate that you have to take advantage of session state replication in the
          cluster.
          ~Ryan Upton
          "Chris Steains" <[email protected]> wrote in message
          news:[email protected]..
          > I wish to set up 2 WLS 8.1 machines to run an application independently to
          > share load (no replication of sessions, beans etc).
          >
          > Can I create a cluster for the two servers and not turn on any session or
          > bean replication, then configure the IIS or Apache plug-in to use the
          > cluster and therefore create some load balancing?
          >
          >
          > Chris
          >
          >

Some confusion about Web Cache clustering for load balancing

I have 4 Windows 2003 identical machines having OAS 10g installed with Web Cache (Same Passwords and Oracle Home) . I want to utilize them for load-balancing using Microsoft Network Load-balancing. I followed the Note: 259208.1 till step#10. Now we have virtual machine "IASPROD" for all other nodes {IASPROD1,IASPROD2,IASPROD3,IASPROD4 } I am able to logon to Web Cache manager from all nodes separately.
On Node-1 I added all nodes entries in " Origin Server " having routed "Enabled " for all of them. Same I did added in Site-Definitions and gave alias hostname as "IASPROD" which is virtual server.
Priority =1
Site Hostname =iasprod1.domain Port = 80
Policy = Unrestricted
Origin Server Hostnames , port,proxy
iasprod1.domain 7778 No
iasprod2.domain 7778 No
iasprod3.domain 7778 No
iasprod4.domain 7778 No
I have couple of questions might be very basic but as I am configuring very first time.
1. How do I access all the machines through virtual name as stated above ? I tried but not working.
2. This cluster setup should be repeated for all Nodes or for only node-1.
3. If for only Node-1 than what will heppen in case of Node-1 goes down.
4. How can I verify Load-balancing is working ?
If you guyz can guide me than I'll be very greatful.

One more addition Database is on AIX (9.2.0.4)

Toplink cache and clustering and load balancer

Hi All:
I have an application deployed on AIX platform. This is developed using struts, toplink and session ejbs.
Oracle 10g is installed on two AIX machines and these are in cluster. My j2ee application is deployed on oracle 10g app server.
I will be having loadbalancer in the front of this cluster. Even now with out loadbalancer , with oracle app server clustering I am observing the request sharing between two servers.
My problem is that as I am using the toplink and it uses the cache, what will be the impact on my application on below scenerios.
1. user A connects to machine 1 and reads object using toplink. At the same time user B connects to machine 2 and also reads the same object. User A will update the same object and commit it. User B will use this object and will put this as a child of some parent object and commit the parent.
I mean to say that due to different two machines, cache will not be in sync and this may cause a major problem.
Please provide your input to this.
Thanks,
Viral

Viral,
This is what ORM and more specifically TopLink help you solve.
What you need to do is configure TopLink to use your appropriate locking mechanisms. I recommend optimistic but in some cases pessimistic locking is appropriate too.
Optimistic locking will detect if the second machine attempts to modify an object that has already changed on the database. There is also support to force the UnitOfWork to verify that the optimistic locking field(s) have not changed when using the concurrent object in another relationship.
UnitOfWork.forceUpdateToVersionField(Object, boolean)
http://download-west.oracle.com/docs/cd/B14099_04/web.1012/b10491/oracle/toplink/sessions/UnitOfWork.html#forceUpdateToVersionField(java.lang.Object,%20boolean)
This method will allow you to detect if the instance you are about to use has been modified by another transaction with or without updating its version field.
Cache sync (coordination) is intended to minimize stale cache conditions but locking is the only way to guarantee it is handled at the database level.
Doug

Load balancing with multiple clusters (HTTPProxyServlet)

          Hello!
          I'm newbie in Weblogic. I would like to have clustering and load balancing in
          development environment. I've created 2 clusters, with one managed server each.
          I've created a web application for deploying the http proxy servlet and put it
          under another managed server without clustering. Below is my configuration:
          managed server without cluster (as proxy) - Port 8002
          admin server - Port 8001
          cluster_1 - multicast address 237.0.0.11, multicast port 8004, cluster address
          - t3://localhost:8006, t3://localhost:8007
          cluster_2 - multicast address 237.0.0.10, multicast port 8014, cluster address
          - t3://localhost:8006, t3://localhost:8007
          managed_cluster1 - under cluster_1, port 8006
          managed_cluster2 - under cluster_2, port 8007
          in the web.xml of the proxy, i put the following parameters:
          <param-name>WebLogicCluster</param-name>
          <param-value>localhost:8006|localhost:8007</param-value>
          However, when i send the requests to http://localhost:8002/sms, the requests always
          go to the same server, for eg: managed_cluster2?
          If i configure using single cluster, the load balancing will be in proper. What's
          the cause fo the problem? and any solution?
          Thanx in advance.
          Regards,
          joey


You have 2 options here Jordi, either you can use BGP loadbalancing, this requires multipath as BGP by default would only install one route from the BGP table to the RIB hence FIB.
But this may result in excessive IRL (inter rack link) usage in the cluster when traffic coming in on rack0 wants to take the bGP path out on rack1
You could also use ABF (access-list based forwarding) to forcelly push traffic received on rack0 out on the link on rack0 and use an ipsla tracker to fallback to rack1 in case the uplink is gone.
Alternatively to extend this by IGP signaling to redirect traffic preferably to rack1 to start with to minimize the IRL usage.
And then you also have the ability to use RPL in the uplink path to make one link more preferred on teh internet then the other in case you want to control a bit which link is preferably used on rack0 or rack1
regards
xander

Query on Clustering,Load Balancing and Dehydration in Oracle BPEL PM

Hi,
I had a Few queries on Dehydration ,Clustering and Load Balancing:
1) In section 5.1 "Use Case for Asynchronous Web Services",insertion of a dehydration point is mentioned.What do you exactly mean by this.Can a dehydration point be inserted explicitly?OR we have to put a wait activity or something so that dehydration happens?
2) If a dehydration point needs to be inserted explicity arent we assuming that the invoke-reply will take long?But this might not be the case always.Is is a lso possible that an asynchronous process is not a long running one.
3) Can we configure administratively ,how much time the process (say 10 seconds or so)waits after which it gets dehydrated?
4) Consider a load balancing scenario,where we have 2 BPEL PM's (PM1 and PM2) running on 2 different App Servers (SRV1 and SRV2)in an clustered environment.
Scenario:
1)We have an asynchronous process which makes a call to a human task activity.
2)A request from client comes for this process.
3) The load balancing server forwards it to PM1 on SRV1.PM1 processes the request and calls the human task.
4) PM1 has not dehydrated the process.
5) The response from the Human User comes back to the Load Balancer before the process is dehydrated by PM1.It forwards this response to PM2.PM2 searches for the Process based on the Cor-relation ID and does not find it.
Can you tell me how this scenario is handled?
I would be grateful if someone can answer these queries or direct me to some place where it is already explained.
Thanks
Dileep

1) In section 5.1 "Use Case for Asynchronous Web Services",insertion of a dehydration point is mentioned.What do you exactly mean by this.Can a dehydration point be inserted explicitly?OR we have to put a wait activity or something so that dehydration happens?
Insert a java snippet with "checkpoint();"
3) Can we configure administratively ,how much time the process (say 10 seconds or so)waits after which it gets dehydrated?
No, this is due to the performance of your database.

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 For Users

I have a single win2k8 r2 server vm with a C and D drive. The database is located on the D drive. The vendor states that the database has to be located on the server hosting the application. I need to know if there is a way to use MS Clustering to load balance
that server for logins and printing. This is a Windows Terminal (RDP) server using Citrix Xenapp 6.5. My goal is to have an additional server to balance logins and printing while the actual application remains on the original server. Please send me some
suggestions or best route to follow.

Hi,
Could you clarify
“My goal is to have an additional server to balance logins and printing while the actual application remains on the original server.” It seems you want to make the Terminal Services Session Broker service high available? If so you can refer
the following KB first:
Deploying Remote Desktop Connection Broker with High Availability Step-by-Step Guide
http://technet.microsoft.com/en-us/library/ff686148(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Load balancing with JSP

Anyone and everyone,
When configuring load balancing with Weblogic clusters, does load
balancing take effect for all services or just EJB and RMI? Or another
way of saying the same thing, can I setup weighted load balancing for
the JSP engines across 2 weblogic servers.
Thanks in advance,
Mike

The load-balancing documentation you read describing the different algorithms only applies to RMI stubs (e.g., EJB clients). Please see http://www.weblogic.com/docs51/cluster/concepts.html#1026091 for a description of how load-balancing/clustering works with servlets/JSPs.
The short answer is that in using servlet clustering, most people want/need/use in-memory replication for HttpSession objects. In WLS 5.1 (and before), in-memory replication requires one or more proxy servers be set-up in front of the cluster. Typically, most people use something like BigIP to load-balance
across the proxy servers and let the weblogic plug-in for the proxy server handle the routing to the cluster. The plug-in uses round-robin until an HttpSession is established for a user, then it always tries to route to the server where the user's session is located.
Hope this helps,
Robert
Brian Lin wrote:
All,
I have a quesiton here regarding load balancing with DNS round robin. As of Chapter Adminstration of Clustering Weblogic server, Weblogic can be configured to balance by weight. How about Weblogic handle weight based balancing after DNS round robin ip response? or just can choose one way instead of both?
What's the big difference between choosing BigIP and software balancing (WL)?
Brian
"Wei Guan" <[email protected]> wrote:
I don't think you can configure this load balancing in weblogic in current
release. However, if you have Big-IP or LocalDireoctr, you can set up
weighted load-balancing there. Otherwise, weblogic proxy will use DNS round
robin to do the load-balancing between JSP engins.
My 2 cents.
Cheers - Wei
Michael Yakimisky <[email protected]> wrote in message
news:[email protected]...
Anyone and everyone,
When configuring load balancing with Weblogic clusters, does load
balancing take effect for all services or just EJB and RMI? Or another
way of saying the same thing, can I setup weighted load balancing for
the JSP engines across 2 weblogic servers.
Thanks in advance,
Mike

Load Balancing cockpit error

          We are testing clustering and load balancing using WLS 6SP1. We have found that
          the fail over works fine (i.e. we kill a server and the next call is invoked on
          another server). However, we find that all calls (modulo failover) always go to
          the same server. We expected to get round-robin for each home access. I've attached
          the config.xml and deployment descriptors. What am I missing here? Is there anything
          special I should be doing code wise?
          BTW: All calls are going to a stateless session bean.
          Regards,
          Andy
          [config.zip]


          Viresh Garg <[email protected]> wrote:
          >The attached config.zip seems to be corrupted. I can't download it.
          Wierd, I've just managed to download it. Anyway, I'll paste the
          contents into the text below.
          >
          >I am assuming that you are using a JAVA client. Could you describe your
          >test case to
          >test the load balancing between home methods of EJB ( what kind of EJB??)
          We have a stateless session bean. At each request we use JNDI to
          obtain a handle to a stateless session bean. We invoke an
          operation on it and then call remove on the stateless session
          bean. We run several of these clients (Java clients) and observe
          the system load and network traffic. We see that network traffic
          is almost minimal and system load on the "other" server is non-
          existent. We know that other server can satisfy calls to the
          stateless session bean because fail over (between calls) works
          correctly. I'm sure we are doing something daft, but I can't spot it.
          --------------------- config.xml ---------------------------
          <?xml version="1.0" encoding="UTF-8"?>
          
          <Domain Name="myDomain">
          <Security Name="petstore"
          PasswordPolicy="wl_default_password_policy" Realm="myRealm"/>
          <Application Name="wl_management_internal2" Path="C:\bea\wlserver6.0sp1\config\tmp">
          <WebAppComponent Name="wl_management_internal2"
          Targets="petstoreServer" URI="wl_management_internal2.war"/>
          </Application>
          <PasswordPolicy Name="wl_default_password_policy"/>
          <Server Cluster="PetStoreCluster" ClusterWeight="80"
          IIOPEnabled="false" JavaCompiler="C:\bea\jdk130/bin/javac"
          ListenAddress="194.152.80.29" ListenPort="7001" Machine="ROWAN"
          Name="petstoreServer" NativeIOEnabled="false"
          RootDirectory="C:\bea\wlserver6.0sp1" StdoutDebugEnabled="true"
          StdoutEnabled="true" StdoutSeverityLevel="64"
          ThreadPoolSize="15" TransactionLogFilePrefix="config/myDomain/logs/">
          <Log FileName="./config/myDomain/logs/weblogic.log" Name="petstoreServer"/>
          <ServerDebug DebugAbbreviation="false" DebugCluster="true"
          DebugClusterAnnouncements="true"
          DebugClusterFragments="true" DebugClusterHeartbeats="true"
          DebugConnection="true" DebugEJB="true" DebugEJBCache="true"
          DebugEJBCalls="false" DebugEJBDeployment="true"
          DebugEJBFreepool="true" DebugEJBLocking="true"
          DebugEJBPersistence="true" DebugEJBSecurity="true"
          DebugEventManager="true" DebugFailOver="true"
          DebugHttp="true" DebugJMSBackEnd="true" DebugJMSBoot="true"
          DebugJMSCommon="true" DebugJMSConfig="true"
          DebugJMSDurableSubscribers="true" DebugJMSFrontEnd="true"
          DebugJMSJDBCScavengeOnFlush="true" DebugJMSLocking="true"
          DebugJMSStore="true" DebugJMSXA="true" DebugJNDI="true"
          DebugJNDIFactories="true" DebugJNDIResolution="false"
          DebugLoadBalancing="true" DebugMessaging="true"
          DebugRC4="true" DebugRSA="true" DebugReplication="true"
          DebugReplicationDetails="true" DebugRouting="true"
          DebugSSL="true" DebugSecurityPasswordPolicy="true"
          DebugSecurityRealm="true" DebugTunnelingConnection="true"
          DebugTunnelingConnectionTimeout="true"
          DebugURLResolution="true" JDBCConn="true" JDBCSQL="true"
          JTA2PC="true" JTAAPI="true" JTAJDBC="true"
          JTAPropagate="true" JTARMI="true" JTARecovery="true"
          JTATLOG="true" JTAXA="true" ListenThreadDebug="true"
          LogDGCStatistics="true" MagicThreadDumpBackToSocket="false"
          MagicThreadDumpEnabled="false"
          MagicThreadDumpFile="debugMagicThreadDumpFile"
          MagicThreadDumpHost="localhost" Name="petstoreServer"/>
          <SSL CertificateCacheSize="3" Enabled="true" ListenPort="7002"
          Name="petstoreServer"
          ServerCertificateChainFileName="./config/myDomain/ca.pem"
          ServerCertificateFileName="./config/myDomain/democert.pem"
          ServerKeyFileName="./config/myDomain/demokey.pem" TrustedCAFileName="./config/myDomain/ca.pem"/>
          <WebServer DefaultWebApp="tour"
          LogFileName="./config/myDomain/logs/access.log"
          LoggingEnabled="true" Name="petstoreServer"/>
          <KernelDebug Name="petstoreServer"/>
          </Server>
          <Application Name="wl_management_internal1" Path="C:\bea\wlserver6.0sp1\config\tmp">
          <WebAppComponent Name="wl_management_internal1"
          Targets="petstoreServer" URI="wl_management_internal1.war"/>
          </Application>
          <Application Deployed="true" Name="tour" Path="C:\bea\wlserver6.0sp1\config\myDomain\applications">
          <WebAppComponent Name="tour" Targets="petstoreServer" URI="tour.war"/>
          </Application>
          <FileRealm Name="myFileRealm"/>
          <Security Name="myDomain"
          PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
          <Application Deployed="true" Name="monitorApp1_1" Path="C:\bea\wlserver6.0sp1\config\myDomain\applications\monitorApp1_1.ear">
          <EJBComponent Name="monitorBeans1_1" Targets="PetStoreCluster" URI="monitorBeans1_1.jar"/>
          <WebAppComponent Name="monitorClient1_1"
          Targets="PetStoreCluster" URI="monitorClient1_1.war"/>
          </Application>
          <ApplicationManager Name="petstore"/>
          <FileRealm Name="wl_default_file_realm"/>
          <JDBCConnectionPool CapacityIncrement="1"
          DriverName="com.inet.tds.TdsDriver" InitialCapacity="1"
          JDBCXADebugLevel="0" LoginDelaySeconds="0" MaxCapacity="10"
          Name="monitorSimplePool"
          Properties="sql7=true;user=sa;port=1433;password=;url=jdbc:inetdae7:194.152.80.29;host=194.152.80.29;database=poc3a"
          RefreshMinutes="0" ShrinkPeriodMinutes="15"
          ShrinkingEnabled="true" SupportsLocalTransaction="false"
          Targets="PetStoreCluster" TestConnectionsOnRelease="false"
          TestConnectionsOnReserve="false" URL="jdbc:inetdae7:194.152.80.29"/>
          <Machine Name="ROWAN"/>
          <Log FileName="./config/myDomain/logs/wl-domain.log" Name="petstore"/>
          <Server AcceptBacklog="50" AdministrationPort="0"
          Cluster="PetStoreCluster" ClusterWeight="100"
          CompleteHTTPMessageTimeout="480"
          CompleteIIOPMessageTimeout="480" CompleteT3MessageTimeout="480"
          ConsoleInputEnabled="false" DGCIdlePeriodsUntilTimeout="2"
          DefaultIIOPPassword="guest" DefaultIIOPUser="guest"
          DefaultProtocol="t3" DefaultSecureProtocol="t3s"
          EnabledForDomainLog="true" HelpPageURL="/docs/adminhelp/"
          HttpdEnabled="true" IIOPEnabled="false"
          IdlePeriodsUntilTimeout="4" InstrumentStackTraceEnabled="false"
          JDBCLoggingEnabled="false"
          JMSDefaultConnectionFactoriesEnabled="true"
          JavaCompiler="C:\bea\jdk130/bin/javac"
          ListenAddress="194.152.80.1" ListenPort="7001"
          ListenThreadStartDelaySecs="0"
          LogRemoteExceptionsEnabled="false" LoginTimeout="1000"
          LoginTimeoutMillis="5000" Machine="MOUSE"
          MaxHTTPMessageSize="10000000" MaxIIOPMessageSize="10000000"
          MaxT3MessageSize="10000000" Name="petstoreServerClone"
          NativeIOEnabled="false" NetworkClassLoadingEnabled="false"
          PeriodLength="60000" ResponseTimeout="0"
          ReverseDNSAllowed="false" RjvmIdleTimeout="0"
          RootDirectory="C:\bea\wlserver6.0sp1"
          SocketReaderTimeoutMaxMillis="1000"
          SocketReaderTimeoutMinMillis="100" StdoutDebugEnabled="true"
          StdoutEnabled="true" StdoutSeverityLevel="64"
          ThreadPoolPercentSocketReaders="33" ThreadPoolSize="15"
          TransactionLogFilePrefix="config/myDomain/logs/"
          TunnelingClientPingSecs="45" TunnelingClientTimeoutSecs="40"
          TunnelingEnabled="false" WorkspaceShowUserKeysOnly="false"
          ZACEnabled="true" ZACPublishRoot="exports">
          <WebServer ClusteringEnabled="false" DefaultWebApp="tour"
          HttpsKeepAliveSecs="60" KeepAliveEnabled="true"
          KeepAliveSecs="30" LogFileBufferKBytes="8"
          LogFileFlushSecs="60" LogFileFormat="common"
          LogFileName="./config/myDomain/logs/access.log"
          LogRotationPeriodMins="2147483647" LogRotationType="size"
          LoggingEnabled="true" MaxLogFileSizeKBytes="0"
          MaxPostSize="-1" MaxPostTimeSecs="-1"
          Name="petstoreServerClone" PostTimeoutSecs="0" WAPEnabled="false"/>
          <SSL CertificateCacheSize="3" ClientCertificateEnforced="false"
          Enabled="true" ExportKeyLifespan="500" HandlerEnabled="true"
          KeyEncrypted="false" ListenPort="8002"
          LoginTimeoutMillis="25000" MDAcceleration="Java"
          Name="petstoreServerClone" PeerValidationEnforced="0"
          RC4Acceleration="Native/Java" RSAAcceleration="Native/Java"
          ServerCertificateChainFileName="./config/myDomain/ca.pem"
          ServerCertificateFileName="./config/myDomain/democert.pem"
          ServerKeyFileName="./config/myDomain/demokey.pem"
          TrustedCAFileName="./config/myDomain/ca.pem" UseJava="true"/>
          <Log FileCount="7" FileMinSize="500"
          FileName="./config/myDomain/logs/weblogic_clone.log"
          FileTimeSpan="24" Name="petstoreServerClone"
          NumberOfFilesLimited="false" RotationType="none"/>
          <KernelDebug Name="petstoreServerClone"/>
          <ServerDebug DebugAbbreviation="false" DebugCluster="true"
          DebugClusterAnnouncements="true"
          DebugClusterFragments="true" DebugClusterHeartbeats="true"
          DebugConnection="true" DebugEJB="true" DebugEJBCache="true"
          DebugEJBCalls="false" DebugEJBDeployment="true"
          DebugEJBFreepool="true" DebugEJBLocking="true"
          DebugEJBPersistence="true" DebugEJBSecurity="true"
          DebugEventManager="true" DebugFailOver="true"
          DebugHttp="true" DebugJMSBackEnd="true" DebugJMSBoot="true"
          DebugJMSCommon="true" DebugJMSConfig="true"
          DebugJMSDurableSubscribers="true" DebugJMSFrontEnd="true"
          DebugJMSJDBCScavengeOnFlush="true" DebugJMSLocking="true"
          DebugJMSStore="true" DebugJMSXA="true" DebugJNDI="true"
          DebugJNDIFactories="true" DebugJNDIResolution="false"
          DebugLoadBalancing="true" DebugMessaging="true"
          DebugRC4="true" DebugRSA="true" DebugReplication="true"
          DebugReplicationDetails="true" DebugRouting="true"
          DebugSSL="true" DebugSecurityPasswordPolicy="true"
          DebugSecurityRealm="true" DebugTunnelingConnection="true"
          DebugTunnelingConnectionTimeout="true"
          DebugURLResolution="true" JDBCConn="true" JDBCSQL="true"
          JTA2PC="true" JTAAPI="true" JTAJDBC="true"
          JTAPropagate="true" JTARMI="true" JTARecovery="true"
          JTATLOG="true" JTAXA="true" ListenThreadDebug="true"
          LogDGCStatistics="false" MagicThreadDumpBackToSocket="false"
          MagicThreadDumpEnabled="false"
          MagicThreadDumpFile="debugMagicThreadDumpFile"
          MagicThreadDumpHost="localhost" Name="petstoreServerClone"/>
          </Server>
          <Log FileName="myDomain.log" Name="myDomain"/>
          <JTA Name="myDomain"/>
          <Machine Name="MOUSE"/>
          <ApplicationManager Name="myDomain"/>
          <Realm FileRealm="myFileRealm" Name="myRealm"/>
          <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          <Cluster ClusterAddress="194.152.80.1,194.152.80.29:7001"
          DefaultLoadAlgorithm="round-robin"
          MulticastAddress="224.10.10.1" Name="PetStoreCluster" ServiceAgeThresholdSeconds="180"/>
          <Application Name="console" Path="C:\bea\wlserver6.0sp1\config\examples\applications">
          <WebAppComponent Name="console" Targets="petstoreServer" URI="console.war"/>
          </Application>
          <JDBCDataSource JNDIName="monitorSimplePool"
          Name="monitorSimpleDB_1" PoolName="monitorSimplePool" Targets="PetStoreCluster"/>
          </Domain>
          ---------------------- ejb-jar.xml -------------------------
          <?xml version="1.0"?>
          <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
          1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
          <ejb-jar>
          <enterprise-beans>
          <entity>
          <ejb-name>ContractCMP</ejb-name>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.cmp.ContractCMPBean</ejb-class>
          <persistence-type>Container</persistence-type>
          <prim-key-class>com.liffe.monitor.general.ContractPK</prim-key-class>
          <reentrant>False</reentrant>
          <cmp-field>
          <field-name>contractCode</field-name>
          </cmp-field>
          <cmp-field>
          <field-name>tradeVolume</field-name>
          </cmp-field>
          <cmp-field>
          <field-name>suspended</field-name>
          </cmp-field>
          </entity>
          <entity>
          <ejb-name>ContractBMP</ejb-name>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.bmp.ContractBMPBean</ejb-class>
          <persistence-type>Bean</persistence-type>
          <prim-key-class>com.liffe.monitor.general.ContractPK</prim-key-class>
          <reentrant>False</reentrant>
          </entity>
          <session>
          <ejb-name>ContractMonitor</ejb-name>
          <home>com.liffe.monitor.contractonly.server.ContractMonitorHome</home>
          <remote>com.liffe.monitor.contractonly.server.ContractMonitor</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.ContractMonitorBean</ejb-class>
          <session-type>Stateful</session-type>
          <transaction-type>Container</transaction-type>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          </session>
          <session>
          <ejb-name>InjectorTarget</ejb-name>
          <home>com.liffe.monitor.injector.server.InjectorTargetHome</home>
          <remote>com.liffe.monitor.injector.server.InjectorTarget</remote>
          <ejb-class>com.liffe.monitor.injector.server.InjectorTargetBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          </session>
          </enterprise-beans>
          <assembly-descriptor>
          <method-permission>
          <role-name>everyone</role-name>
          <method>
          <ejb-name>InjectorTarget</ejb-name>
          <method-name>*</method-name>
          </method>
          </method-permission>
          <container-transaction>
          <method>
          <ejb-name>ContractCMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>ContractMonitor</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>InjectorTarget</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          ------------------- weblogic-ejb-jar.xml -----------------
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN'
          'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>ContractCMP</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>1000</max-beans-in-cache>
          </caching-descriptor>
          <persistence-descriptor>
          <persistence-type>
          <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
          <type-version>5.1.0</type-version>
          <type-storage>META-INF/weblogic-cmp-rdbms-jar-contractonly-cmp.xml</type-storage>
          </persistence-type>
          <persistence-use>
          <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
          <type-version>5.1.0</type-version>
          </persistence-use>
          </persistence-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>random</home-load-algorithm>
          </clustering-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>15</trans-timeout-seconds>
          </transaction-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          <transaction-isolation>
          <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
          <method>
          <ejb-name>ContractCMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          </transaction-isolation>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>ContractBMP</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>1000</max-beans-in-cache>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>random</home-load-algorithm>
          </clustering-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>15</trans-timeout-seconds>
          </transaction-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          <transaction-isolation>
          <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
          <method>
          <ejb-name>ContractBMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          </transaction-isolation>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>ContractMonitor</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>100</max-beans-in-cache>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          <reference-descriptor>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          </ejb-reference-description>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          </ejb-reference-description>
          </reference-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.ContractMonitorHome</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>InjectorTarget</ejb-name>
          <caching-descriptor>
          <max-beans-in-free-pool>50</max-beans-in-free-pool>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          <reference-descriptor>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          </ejb-reference-description>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          </ejb-reference-description>
          </reference-descriptor>
          <jndi-name>ejb/InjectorTargetHome</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ---------------------- weblogic-cmp-.... ---------------------
          <!DOCTYPE weblogic-rdbms-bean PUBLIC
          '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN'
          'http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd'>
          <weblogic-rdbms-bean>
          <pool-name>monitorSimplePool</pool-name>
          <table-name>Contract</table-name>
          <attribute-map>
          <object-link>
          <bean-field>contractCode</bean-field>
          <dbms-column>contractCode</dbms-column>
          </object-link>
          <object-link>
          <bean-field>tradeVolume</bean-field>
          <dbms-column>tradeVolume</dbms-column>
          </object-link>
          <object-link>
          <bean-field>suspended</bean-field>
          <dbms-column>suspended</dbms-column>
          </object-link>
          </attribute-map>
          <finder-list>
          <finder>
          <method-name>findByGTVolume</method-name>
          <method-params>
          <method-param>int</method-param>
          </method-params>
          <finder-query><![CDATA[(> tradeVolume $0)]]></finder-query>
          </finder>
          <finder>
          <method-name>findAllContracts</method-name>
          <finder-query><![CDATA[(isNotNull contractCode)]]></finder-query>
          </finder>
          </finder-list>
          <options>
          <use-quoted-names>false</use-quoted-names>
          </options>
          </weblogic-rdbms-bean>

Load Balancing in Portal

Hi,
We have IIS as our intermediate web server.We have implemented Clustering.However load balancing is not done and all the requests are going to one server only.
I am not clear about where and how to implement Load balancing.
Please let me know how to go about this.
Thanks,
Suparna

Hi Suparna,
to loadbalance between different SAP WebAS Instances (CI & DI) you would need a loadbalancing instance like the SAP WebDispatcher, Reverse Proxy or a hardware loadbalancer.
Check this <a href="https://forums.sdn.sap.com/thread.jspa?threadID=117847">thread</a> and the link mentioned there.
Hope it helps,
Robert

Wlp and apache load balancing

Hi,
          I have been trying to understand webloigc clustering and load balancing capabilities. I have been through the edocs but it does not explain how things work, instead they only emphasis on how to configure.
          Consider the following scenario:
          --------cisco firewall/load balancer------------
          apatche1 apache2 apache3
          -------------------firewall-------------------------
          WLP1 WLP2 WLP3 WLP4
          My questions are:
          (1) how apache servers load balance incoming requests amongst the four portal instances? I understand that it will use weblogic proxy plug-in. the httpd.config also should be configured to proxy requests to WLP instances by adding the corresponding address:prot entries for each instance, using WebLogicCluster keyword.
          (2) Weblogic cluster will have nothing to do with load balancing? The only benefit I get of configuring weblogic cluster is session replication, right?
          (3) even failover is going to be handled by apache servers?
          (4) if I need to use SSL and I need to have my SSL encryption/decryption to be done on WLP instances; apache servers will only forward requests, no encryption/decryption to be done on the web tier. Is this possible?
          See in WebSphere the edge component will handle the load balancing and through it I can assign load weights for each appserver instance.
          (5) Are there any best practice to implement load balancing and failover on weblogic portal?
          I appreciate any input in this regards.

1. yes, configure the apache plugin. put your 4 servers in the WeblogicCluster property (host:port,host:port...). The proxy will round robin requests between the servers in the cluster, although sessions are pinned to a single server. So if a request with a session (jsessionid cookie) comes in, it will read the primary server from the cookie and route it to that server.
note that we have had trouble with keep alives ON and load balancing. we had to turn keep alives off to get load balancing working.
2. right, the cluster allows failover by replication. apache plugin will perform the failover.
3. the plugin will keep a dynamic server list so if a server goes down, it will update the cluster list and not route to it. it will also retry requests on another server on an error or timeout connecting. you can tweak timeout settings like WLSocketTimeoutSecs and ConnectTimeoutSecs. and keep idempotent ON which allows failover, unless you aplpication can't handle this.

Clustering VS Load balancing

Similar Messages

Maybe you are looking for