Using OAM API functions with the RTP EMC

Applications can use the following functions to work with an OAM API managed object for the RTP MIB extended management component:

OAM API function

Description

oamOpenObject

Opens a managed object and starts an editing session on the specified managed object.

This function returns a handle to be used with subsequent OAM service function invocations. The managed object is completely idle until a client first opens it. Until then, absolutely no caching occurs, and no events are generated. With the first open, caching begins. Subsequent opens do not affect caching in any way.

oamCloseObject

Closes a managed object.

Each close of the managed object, except the last, essentially decrements a reference count. When the last close occurs, the managed object goes completely idle. All caching and events stop, and the cache is erased.

oamGetKeyword

Retrieves a keyword value in the managed object with the specified handle.

oamGetQualifier

Returns information about a specified keyword.


The Fusion RTP EMC is read-only. Therefore, the OAM service function oamSetKeyword does not apply and will fail if used.