we are in the process of building a telecom application, which would be deployed on the weblogic server. We are in the process of building a health management module for the application. This module needs to detect faults in various other application modules and report them via alarms (to be sent over different medias like SMS, email, SNMP etc). Before we proceed on building this framework, we would like to understand the facilities offered by weblogic server in this regard. Some of the areas where we would like to hear from you are
We would like to monitor the health of our application as running in weblogic server. We are interested in the following
1. The number of available or in-use instances of our EJBs.
2. Memory consumption
Ideally we would like to get this information periodically (time interval being configurable) through some kind of call back methods. We would like to set some limits on these parameters after which our application should be notified.
We are currently planning to implement a periodic database activity to ensure the database is up and running. A better way could have been if the underlying platform detected database failure and informed the application through a call back method. Let me know if weblogic server provides support for this.
Can we get updates on the health of Database Connection Pool and/or Data Source being used by the application? We would like to gets updates about the connection pool size. In case some of the connections in the pool become un-usable then we would like to be notified (this was happening with the previous reported XA_ERR problem). We would like to know the number of times the application got stuck due to un-availability of a database connection in the underlying pool. This information would be useful for fine-tuning of the application.
We would like to be notified if any of the following happens
1 JMS Server goes down or comes back up again
We need this alert, as we would like to disable the functions using JMS Bus upon detecting the bus failure. Currently we are planning to create a JMS connection and set an exception listener on it. If there�s a better way then do let me know.
1 Web Server goes down or comes back up again
2 Weblogic Server hosting the application goes down
3 The application becomes un-reachable (maybe because it got un-deployed or due to any other reason)
In all the above situations, we need to detect the event and raise an alert (SMS, email or any other medium).
Also, in case the server goes down is it possible to start off a new backup server remotely.
Now upon detecting a failure, we need to raise an alert. We would like to inform the administrator about the problem as soon as possible. For this purpose, we need to send the alert over a number of different mediums. The mediums that we have in mind currently are
4 Add to a database file
5 Log on to console
We intend to write our own code for sending these alerts. We don�t want to get into this unless the underlying server does not provide any ready-made api to do that. Kindly let us know if weblogic server offers some support for sending alerts over one or more medias mentioned above.
If you can also direct me to some useful links on the web that provide information relavent to above topics that would be great.
"Ignorance is bliss"
Joined: Jan 06, 2001
most of the informatio you need you can get using standard JMX programming. Weblogic also has some configurations you may do to restart managed servers when fatal problems occurs, take a look at the admin and cluster configuration options for fault tolerance. also about JMX programming you'll find information at: