WebSphere known problem is messages getting stuck in queues if the processing programs malfunction, if peak condition of data streams happen, or if the overall corporate information network becomes unstable.
To handle such situations it is necessary to monitor messages queues and other critical subsystems without further overloading servers’ CPUs and wasting other resources. A monitoring agent, such as IPHost Monitor Agent gathers required data without creating significant overhead and supplies necessary report data.
IPHost Network Monitor is able to handle WebSphere monitoring by means of advanced monitor types as well as special tools named Remote Monitor Agents, able to deliver necessary data to the central IPHost Network Monitor installation.Monitor Agents allow to control the overall services and software functioning and interaction by using a number of monitor types, by providing reports and sending alerts via several channels.
IPHost Monitor Agents are set up to watch over all the resources of critical importance and notify the central IPHost Network Monitor installation as soon as data are gathered. The actual update frequency is set up at installation time or afterwards. Alerts can be of several types: sending email, SMS or IM messages, running a script or program – in other words, both human-operated and automated means can handle the situation.
A Monitor Agent running on an average desktop computer is able to handle a hundred monitors. Depending on a number of parameters to monitor, several separate Monitor Agents installations could be necessary. The agent is capable of checking various monitor types simultaneously. Also, several agents can co-exist (run concurrently) on the same server.
IPHost Network Monitor central installation (command center) us normally run on a separate server all the set up actions can be performed remotely, using corresponding remote desktop application, over a secure channel. After all the agents data are entered and connections established, it is possible to view all the data being gathered by the agents from the command center.
Creating proper monitors with reasonable parameters is the most important task. It takes up to several minutes to add a new monitor and specify parameters for it, to match the condition that should be warned about. HTTP monitors, Web Transaction Monitors and Program or script monitors can be used to control a WebSphere-based service efficiently.
HTTP(S) monitor allows to retrieve the results of a certain URL loading, using GET or POST requests. This tool is enough in most cases when no authentication is required to access certain services via HTTP-based protocol.
Web Transaction Monitor is an advanced monitor type; in all the cases where user-oriented HTTP interaction is assumed, this kind of monitor can efficiently detect and raise alerts wherever a particular HTTP(S)-based request returns proper data.
Program or script monitor is a universal (although it might be not most efficient) means to handle data: to run a program or script and let them produce data to interpret and raise alerts if necessary. Since WebSphere message queue (MQ) service is the core of WebSphere-based systems, programs or scripts can be used to access a queue and retrieve its state parameters, thus making assumption of the overall system health.
Note that WebSphere-driven service can include a great variety of miscellaneous services; other monitor types can be used to watch efficiently certain types of services.
Free 30-day trial version of IPHost Network Monitor is available. During your trial you can get support by e-mail, please use contact form to send all your inquiries on IPHost Network Monitor features and purchase.
|Windows Interface Screenshot||Web Interface Screenshot|
Download the free trial of IPHost Network Monitor and start to monitor your network and vital applications in a few minutes.
IPHost Network Monitor 5.0 build 10689 of April 29, 2016. File size: 55MB