Out of the box J2EE app servers (in our case weblogic) has some monitoring and fantastic logging mechanism however there is not much in the way of monitoring that can be used to really pinpoint what is happening with your applications and or your EJB's servlets database connections etc.
There are some things that can help you here these tools are:
Wily Introscope (as used by BEA internally) by Computer Associates
Quest Jprobe
There are some others out there but these are the main 2.
Other ways to monitor is to use JMX this is a purpose architected system inbuilt in J2EE model
that is effectivly a structure for writing a system to monitor your apps.
JMX is implemented using Mbeans
or drop me a email at guru.weblogic@gmail.com
Friday, 7 March 2008
Struggling with Weblogic ? Free Hands on Advice and Support
Watch this space....for free hands on advice and support.
or drop me a email at guru.weblogic@gmail.com
or drop me a email at guru.weblogic@gmail.com
Load Balancing or Clustering?
To Cluster or not to cluster that is the question?
Weblogic Server lends itself very well to clustering, all the components are available, all the specifications are there and it has had clustering capability long enough through the versions to make this a viable solution, questions is do you want to cluster?
Advantages are:
Resiliance no more single point of failure in the application tier
Session Replication, if a server goes down your session will carry on just by another server node in the cluster.
Disadvantages are:
Complexity - more complexity means more risk of it not working(down more to configuration or human error than the software)
Need more Server resources - more disk , more cpu , more network traffic etc...
Your applications will need to use the clustering services in the container and so they need to be coded to be made 'cluster aware'
Load Balancing is a much simpler setup to implement
Advantages
Quicker and easier to setup
No need to re-engineer your apps.
or drop me a email at guru.weblogic@gmail.com
Weblogic Server lends itself very well to clustering, all the components are available, all the specifications are there and it has had clustering capability long enough through the versions to make this a viable solution, questions is do you want to cluster?
Advantages are:
Resiliance no more single point of failure in the application tier
Session Replication, if a server goes down your session will carry on just by another server node in the cluster.
Disadvantages are:
Complexity - more complexity means more risk of it not working(down more to configuration or human error than the software)
Need more Server resources - more disk , more cpu , more network traffic etc...
Your applications will need to use the clustering services in the container and so they need to be coded to be made 'cluster aware'
Load Balancing is a much simpler setup to implement
Advantages
Quicker and easier to setup
No need to re-engineer your apps.
or drop me a email at guru.weblogic@gmail.com
Weblogic Portal 8.1
Portal 8.1 was a great release this had support for JDK 1.4.x and had a lot of stability and feature enhancements.
Watch this space....
or drop me a email at guru.weblogic@gmail.com
Watch this space....
or drop me a email at guru.weblogic@gmail.com
Subscribe to:
Posts (Atom)