Weblogic and Spring Clustering - weblogic.developer.interest.spring(Archived)

Hi,
We are using Spring's application context to load all our beanids which is hosted on a single weblogic server 9.1.
Now to provide load balancing we are clustering our weblogic servers, but the problem is how to share or replicate these beanids across all the servers which we get using application context because the Spring container will be different in all the servers.
it would be very great help to me if you can provide with some detail solution as to how we can share the beanid across all the servers.

Related

Using P13N Caching Service in Cluster (J2EE Apps)-Not portals

We are using the BEA Weblogic 8.1 app server for developing J2EE application in clustred environiment. We are running four managed servers and one admin server. (two managed servers for each hardware Dell 2250). For application performance we are caching some the data (Database Lookup tables and some dynamic data in appication scope). The problem exists with the dynamic data. When we clear the cache for dynamic data it is refreshing only in one instance of managed server. To resolve this problem, implemented the servlet 2.3 feature(HttpAttributeListner). I came to know that very quickly it won't solve the problem. I found interesting paper on BEA edocs. Here is the solution in BEA Portal world.
          
          http://dev2dev.bea.com/products/wlportal/articles/jiang.jsp
          
          Since we are not using the portal, is there any workaround to resolve the issue.
          
          Thanks,
          Chandra

Using P13N Caching Service in Cluster (J2EE Apps) - Not portals

We are using the BEA Weblogic 8.1 app server for developing J2EE application in clustred environiment. We are running four managed servers and one admin server. (two managed servers for each hardware Dell 2250). For application performance we are caching some the data (Database Lookup tables and some dynamic data in appication scope). The problem exists with the dynamic data. When we clear the cache for dynamic data it is refreshing only in one instance of managed server. To resolve this problem, implemented the servlet 2.3 feature(HttpAttributeListner). I came to know that very quickly it won't solve the problem. I found interesting paper on BEA edocs. Here is the solution in BEA Portal world.
          
          http://dev2dev.bea.com/products/wlportal/articles/jiang.jsp
          
          Since we are not using the portal, is there any solution?
          
          Thanks,
          Chandra

how to dynamically deploy to a cluster?

Hi All,
Does WL's "dynamic deployment" always deploys
the ejb (or j2ee applications) to the Administration
Server alone? Is it possible to let WL "dynamically"
and "automatically" deploys all the ejbs to a cluster?
Of course I know I can use the management console
to deploy them to the cluster. But is it possible to
"automate" this step?
Any help will be appreciated.
Lynch

Doubts regarding Weblogic Cluster and application deployment

Hi all,    Weblogic.....: 12.1.2   OS.............: AIX 7.1    We are planning to create a 2-node Weblogic cluster in different sites to comply with the client's HA requirements. With this im mind, some doubts began do rise:    1) This solution will have a Weblogic Server on site A and another Weblogic Server on site B, and we will create a Weblogic cluster with these 2 servers. It is equivalent to an Oracle Extended RAC, but with Weblogic. Our link between the sites is extremely fast, dedicated, with a latency of less than 5ms. Is it possible and viable to build such solution?    2) Regarding the application deployment, i would like to know if it is possible to deploy an application on just Weblogic Server on node A, and this application will be replicated automatically to the Weblogic Server on site B? As far as i know, i have to deploy the application on both Weblogic Servers manually. Thanks for the patience and attention.
Hi, 1) This solution will have a Weblogic Server on site A and another Weblogic Server on site B, and we will create a Weblogic cluster with these 2 servers. It is equivalent to an Oracle Extended RAC, but with Weblogic. Our link between the sites is extremely fast, dedicated, with a latency of less than 5ms. Is it possible and viable to build such solution? Yes: is very easy to configure the weblogic server cluster (much easier than configuration of rac).Please refer to:http://docs.oracle.com/cd/E24329_01/web.1211/e24425/overview.htm#CLUST114http://docs.oracle.com/cd/E24329_01/web.1211/e24425/setup.htm#CLUST431 
2) Regarding the application deployment, i would like to know if it is possible to deploy an application on just Weblogic Server on node A, and this application will be replicated automatically to the Weblogic Server on site B? As far as i know, i have to deploy the application on both Weblogic Servers manually.
You can deploy your application to the weblogic cluster: its will be automatic deployed to all cluster member (all managed servers) HTH.Borys

sessions.xml examples for application deployed on WLS cluster.

Hope someone can help here. I'm looking to deploy my Toplink enabled application on a BEA Weblogic Portal 8.1 SP 3 clustered server platform. I've gone through the documentation in some depth, but I still don't have a truly clear picture of what needs to be in the sessions.xml and how I need to configure the cluster (from a WLS perspective). So here are my questions:
Does the oracle.toplink.remote.rmi.wls.WLSClusteringService cluster-service defined in the sessions.xml need to be configured to use JMS? Or is it simply a JNDI/RMI service?
When I enable clustering from within the Session Editor, the jms and naming service sections are disabled, do I need to enter these manually in the XML?
Does anybody have an example of working session.xml using the WLSClusteringService?
Thanks! 
Unlike the other ClusteringService types, the WLSClusteringService requires no configuration, but must be used only in applications deployed within a WebLogic cluster. It uses JNDI and RMI connections.
--Gordon                                                                                                                                                                                                                                                                                                                                                                                                                                            
So I don't need to setup a multicast address for my cluster?
Thanks! 
That's correct. The WLSClusteringService will use the clustering mechanisms already existing on the WebLogic server.
--Gordon                                                                                                                                                                                                                                                               

Categories

Resources