Applications Manager Blogs

Yahoo! ManageEngine Applications Manager 6.6 is out.

Some of the new features included are

- Support for Oracle Application Server Monitoring

- Support for Tru64 Unix Monitoring

- Support for Windows Event Logs monitoring

- Support for LAMP Edition and Database Edition of ManageEngine Applications Manager

- Option to schedule daily, weekly, monthly performance and availability reports

Full Build Download: http://appmanager.com/download.html

Existing users can download Service Pack 6 from

http://appmanager.com/service-packs.html and apply it on your existing build to get the new features.

Pour in your feedback!!

You might be wondering, how to start Applications Manager when Linux boots (akin to starting Applications Manager as service in Windows).

Well, you have to make certain modifications. Follow the steps given below:

In Linux, when the machine boots, the following file is called

</etc/rc.local>

You can add the following entry in this file to start the Applications Manager when the machine boots.

su -c “nohup sh <APPMANAGER-INSTALLEDDIRECTORY>/AppManager6/startApplicationsManager.sh & ” <User in which Applicatios manager is installed>

For example,

su -c “nohup sh /advent/Aug2/AppManager6/startApplicationsManager.sh &” susan

Whenever you restart the machine, Applications Manager will also start automatically.

Also, you have to add the following as first line of startApplicationsManager.sh file

cd <APPMANAGER-INSTALLEDDIRECTORY>/AppManager6/

For eg., cd /advent/Aug2/AppManager6/

Thanks,

Susan

Alistair Thomson from Xynomix wanted to do oracle 9i monitoring after installing the trial version of ManageEngine Applications Manager on Windows XP Pro. But unfortunately, the Tablespace status and Table space usage areas showed no data or error.

Alistair soon reported that it might be an Oracle version issue. After upgrading to Oracle 9.2.0.6 from 9.2.0.1, the problem was fixed. All tablespace information was now appearing in the monitor window.

Kudos to you .. Alistair Thomson!

A look at our Google Analytics data for the online demo show that users rarely click the ‘Root Cause Analysis’ icon. That could mean that this is a relatively hidden feature. We have iterated on showing different icons many times for this particular feature. Looks like users donot find it intutive still.

The Root Cause Analysis (RCA) window helps to drill down from a high level view to a details view. For example, assume you have a business application that is grouped under a monitor group named ‘banking application’. This group may have 2 linux servers, a jboss server and an Oracle database. What an RCA can tell you is that the ‘banking application’ is critical because the disk space on server 1 crossed 95% usage, the jdbc free connections is zero etc…..

The RCA view also gives you the details of individual thresholds that were crossed (and hence making the monitor group critical). You have these at various levels :

1) A metric level inside a monitor

2) A monitor level

3) A monitor group level

4) A monitor category level : this can be seen in the Home tab > Monitors bashboard view. Here you will know which all application servers are critical.

The below are some of the clickable icons in the web client wrt RCA .. .

Hope more people read this and get enlightened . Any suggestions to improve this are welcome.

Here’s a screen shot