reasons to upgrage from SMC 3.0 to 3.5?

> we are currently using SMC 3.0 under Solaris 8. We

> are only using the Advanced System Monitoring product.

> We have written a number of modules. We only use the

> SMC console for debugging. We use the Java RMI

> interface to display information we grab from the

> agent on a Java servlet. Some of modules do log

> scanning, some monitor the health of various

> processes and restart the processes if necessary.

>

> Are there compelling reasons to move from SMC 3.0 to

> 3.5? Or are there compelling reasons NOT to make the

> switch. :-)

Well, for you the biggest benefit may be all the extra free stuff. What was once called the Premier Management Applications pack (PMA) and sold in 3.0 was rolled into part of the basic free package in 3.5. So server ops like web interface, CLI, group operations etc are now all free.

There are also a massive amount of bug fixes and speed enhancements. Multi-Agent installation is now very easy, and 3.5 can push out its software upgrades and patches with a few clicks in the GUI. New web server (w/https). Newer versions of Java. Jumpstart support. Multi-homed and NAT'd Server support. Lots of stuff.

Plus it's backwards compatible with 3.0 Agents... so you could migrate your Server to 3.5(.1) first, and upgrade your Agents as you find time.

Not too many places have the expertise to create their own modules: I'd love to hear more about what you use them for!

Regards.

Note: I am an employee of Halcyon (www.HalcyonInc.com)

Aronek at 2007-7-6 13:20:32 >