T3 protocol and clusters

Question

Hi,
          I'm porting a Java application running against WLS6.0 to use a clustered
          server solution. This means I connect via t3 protocol. Any views on the best
          way to get failover and loadbalancing from this approach, for example is
          there anyway I can get the weblogic proxy functionality of
          HttpClusterServlet without using http protocol?
          Thanks
          Sioux
          

Answer 1

Your web.xml looks OK to me.
          All you need to do is, create a .war file and copy it into applications
          directory of proxy server.
          Then register this webapp as default webapp. So whenever you hit proxy server ,
          those requests
          will be handled by this default webapp, in turn the requests will be routed to
          one of the clustered servers.
          Hope it helps
          Kumar
          Sioux France wrote:
          > Hi,
          > I understand this solution, can I ask about the possibility of using a
          > proxy?
          > Is it possible if my URL is t3://localhost:7001 and I now want to use a
          > proxy on this server to redirect to the cluster to use HttpClusterServlet
          > rather than a DNS based solution? If so what do I call to get the proxy to
          > redirect me to the cluster?
          > I've set up a servlet for HttpClusterServlet with my cluster members in the
          > parameters. How can I test from a browser that this is proxying correctly?
          > For the t3 protocol is it possible to get redirection to the cluster members
          > using HttpClusterServlet from a command line client, or is this route only
          > available for web-based queries as that is the only way the
          > HttpClusterServlet can intercept the call? i.e. Must I use my own failover
          > implementation in a DNS-based solution as discussed below?
          >
          > Here's the web.xml for my HttpClusterServlet which I've set as my default
          > webserver on the admin server. Any help understanding this appreciated!
          > Sioux
          >
          > <web-app>
          > <servlet>
          > <servlet-name>HttpClusterServlet</servlet-name>
          > <servlet-class>
          > weblogic.servlet.internal.HttpClusterServlet
          > </servlet-class>
          >
          > <init-param>
          > <param-name>defaultServers</param-name>
          > <param-value>
          > managedserver1:7003:7004|managedserver2:7003:7004
          > </param-value>
          > </init-param>
          >
          > <init-param>
          > <param-name>DebugConfigInfo</param-name>
          > <param-value>ON</param-value>
          > </init-param>
          >
          > </servlet>
          > <servlet-mapping>
          > <servlet-name>HttpClusterServlet</servlet-name>
          > <url-pattern>/</url-pattern>
          > </servlet-mapping>
          >
          > <!-- This bit is just to show it's deployed, and sure enough, it can't find
          > index.html when I call http://localhost:7001 now -->
          > <servlet-mapping>
          > <servlet-name>HttpClusterServlet</servlet-name>
          > <url-pattern>*.html</url-pattern>
          > </servlet-mapping>
          >
          > </web-app>
          >
          > "Robert Patrick" <[email protected]> wrote in message
          > news:[email protected]...
          > > The connection to the cluster is done via the JNDI lookup. The
          > PROVIDER_URL
          > > should be the "cluster name" which is either a DNS name that is mapped to
          > the
          > > list of IP addresses of the clustered servers or a hardware load-balancer.
          > Once
          > > that connection has been made, you will be looking up EJB Home objects --
          > the
          > > objects downloaded to your client are "smart stubs" that understand
          > clustering.
          > > Multiple invocations on that EJBHome reference will be load-balanced
          > across the
          > > cluster of available servers (meaning that it will handle fail-over).
          > This is
          > > easy to do since the EJBHome object is always stateless. If you use
          > stateless
          > > session beans, you can get the same behavior at the bean instance level.
          > > Stateful session beans can be replicated in-memory across a pair of server
          > > instances (much like the HttpSession replication).
          > >
          > > I suggest that you read our clustering documentation at
          > > http://e-docs.bea.com/wls/docs60/
          > >
          > > Hope this helps,
          > > Robert
          > >
          > > Sioux France wrote:
          > >
          > > > I think my point is missed, I have a lovely running cluster, with
          > clustered
          > > > EJBs, clustered JMS and now I want to call it via the t3 protocol or
          > > > something similar from a Java Application. As I understand this, it
          > means I
          > > > can't use HTTP or a proxy. I order to utilise the failover/loadbalancing
          > of
          > > > the cluster that exists, how should I connect to it from the client, can
          > I
          > > > use DNS, RMI, is there any documentation for running a cluster with Java
          > > > Application clients rather than a web front end?
          > > >
          > > > "Robert Patrick" <[email protected]> wrote in message
          > > > news:[email protected]...
          > > > > Use clustered EJBs.
          > > > >
          > > > > Sioux France wrote:
          > > > >
          > > > > > Hi,
          > > > > > I'm porting a Java application running against WLS6.0 to use a
          > clustered
          > > > > > server solution. This means I connect via t3 protocol. Any views on
          > the
          > > > best
          > > > > > way to get failover and loadbalancing from this approach, for
          > example is
          > > > > > there anyway I can get the weblogic proxy functionality of
          > > > > > HttpClusterServlet without using http protocol?
          > > > > > Thanks
          > > > > > Sioux
          > > > >
          > >