Web services management protocol on OASIS agenda

OASIS (Organisation for the Advancement of Structured Information Standards) has formed a technical committee to propose an...

OASIS (Organisation for the Advancement of Structured Information Standards) has formed a technical committee to propose an XML-based management protocol specification for Web services, a Novell official who is chairing the committee has said.

The OASIS Management Protocol Technical Committee, formed about two weeks ago, is intended to boost distributed systems management over the Internet, according to Novell. Management of Web services through use of Web services is the main reason for the initiative, Novell's Winston Bumpus, director of standards for the company and chairman of the new OASIS committee, said.

As the industry is building a Web services platform, it is important that an infrastructure to manage it exists, Bumpus said. The protocol would be used for functions such as resource allocation, monitoring, controlling, and troubleshooting, Bumpus said.

The committee is reviewing a number of technologies for use in the protocol, including XML, Soap, OMI (Open Model Interface), DMTF CIM (Distributed Management Task Force Common Information Model), and DMTF CIM Operations. The specification is expected to be ready in June 2003, with reference implementations to appear next spring and supportive products to be available in late-2003, Bumpus said.

The effort is intended to enable companies to not only manage their own services but to also oversee interaction of those services with services from other companies, according to Novell. The work is intended to deliver an industry-standard protocol for managing desktops, services and networks across an enterprise or Internet environment.

One analyst, however, was sceptical of the OASIS effort. Management of Web services is a complicated issue and is hindered because of lack of uniformity in development of Web services components, said analyst Rikki Kirzner, research director at IDC. "It's far more complex than one standard's going to solve," Kirzner said.

Read more on Integration software and middleware