Novell Operations Center 5 Debuts as NetIQ Product

by Sean Kerner

As Attachmate takes control of Novell, new Operations Center release bulks up on Automated Configuration Management features.

The company that used to be known as Novell has undergone significant change in recent weeks. Novell was acquired by Attachmate in a $2.2 billion deal, and its product lines have now been splintered across multiple Attachmate business units.

The Novell Operations Center product is one of the former Novell products now moving within the Attachmate hierarchy. Operations Center is now part of the Attachmate NetIQ business unit. The shift comes as product hit its 5.0 release. It's not clear when, or if, Attachmate will be removing the Novell brand from the product either.

"We working through all branding items, but bottom line is that the actual product names will not change," Amie Johnson, PR manager at Novell told InternetNews.com. "At present, the name is Novell Operations Center. If and when there are branding changes, we will communicate that directly to customers, partners, journalists, analysts and the market at large."

Johnson noted that the Novell Operations Center roadmap remains intact, and as part of the integration process, Novell and NetIQ will be coming up with updated roadmaps in the next 90 days that address next steps around product integration.

The Novell Operations Center solution was first announced back in November 2010 as a Business Service Management technology. The basis for the technology comes from Novell's acquisition of BSM vendor, Managed Objects in 2008.

Michele Hudnall, BSM solution manager at Novell explained to InternetNews.com that the 5.0 release of Operations Center has evolved somewhat from the core Managed Objects product.

"It has a fresh look and feel for the customer base, Hudnall said. "It also has a configuration management system, what we call our service mapping system."

Hudnall explained that system enables administrators to manage their systems to standard configurations in an effort to help aid compliance requirements.

"The automation applies to the service model itself, so what is running in production is compared against your last approved service configuration model," Hudnall said. "The system flags when there are any discrepancies."

In Hudnall's view, the downfall of other Content Management Database (CMDB) solutions for operation monitoring is the lack of automation. She noted that some enterprises will place their configuration management into a database but then not update it as the enterprise changes.

"Keeping it accurate requires some level of automation and that's the core strength of the product," Hundall said.

Sean Michael Kerner is a senior editor at InternetNews.com, the news service of Internet.com, the network for technology professionals.

Follow ServerWatch on Twitter

This article was originally published on Friday May 20th 2011
Mobile Site | Full Site