 - GDMO (Guidelines for Definition of Managed Objects) is a standard for defining objects in a network in a consistent way. With a consistent "language" for describing such objects as workstations, LAN servers, and switches, programs can be written to control or sense the status of network elements throughout a network. Basically, GDMO prescribes how a network product manufacturer must describe the product formally so that others can write programs that recognize and deal with the product. Using GDMO, you describe the class or classes of the object, how the object behaves, its attributes, and classes that it may inherit.
GDMO is part of the Open Systems Interconnection (OSI) Common Management Information Protocol (CMIP) and also the guideline for defining network objects under the Telecommunications Management Network (TMN), a comprehensive and strategic series of international standards for network management. The object definitions created using GDMO and related tools form a Management Information Base (MIB). GDMO uses Abstract Syntax Notation One (ASN.1) as the rules for syntax and attribute encoding when defining the objects.
GDMO is specified in ISO/IEC standard 10165/x.722.
 |
Learn more about Web services development |
| Operating system virtualization and Web services: Web services development and operating systems virtualization may be two different types of abstraction, but virtualization techniques look like they can have positive impact. |
| Creating rich Web service clients with Flash and Flex: Flash and Flex, titans within the RIA universe, now have XML, Ajax and scripting language functionality that make them better suited for Web services development. |
| Oracle links SOA, data services, BI and BAM: When it comes to incorporating data services, business intelligence (BI), and business activity monitoring (BAM), Oracle has not lost sight of its database roots. |
| Is Ruby on Rails ready for enterprise SOA?: Ruby on Rails promises ease in RESTful SOA development, but for it to move up to enterprise class, developers need to know how to make it scalable. |
| 2006 JavaOne coverage: A compilation of stories written about the JavaOne conference held in San Francisco this past May. |
| Chapter of the week: Security and Ajax: This chapter, excerpted from Ajax in Action, discusses security-related concerns that have particular implications for Ajax. |
| Chapter of the week: XML Web services: This chapter, excerpted from Core C# and .NET, takes a look at the pluses and minues of implementing and consuming Web services in a .NET environment. |
| Chapter of the week: Working with Beehive Web services and JSR 181: This chapter, excerpted from Pro Apache Beehive, explores the Web service capabilities that are a part of Apache Beehive. You'll learn about JSR 181, Web Services Metadata for the Java ... |
| Chapter of the week: Introduction to Web services technologies: This chapter, excerpted from Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services, focuses on the standards that make up the Web services platform and how Web ... |
| CONTRIBUTORS: |
Hou Jitao |
| LAST UPDATED: |
30 Jul 2001
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
