Instruction Manual

OEM External Specification
OEM User’s Guide—520330-001
A-4
Open Enterprise Management Server
Open Enterprise Management Server
This section describes the following components of the OEM Server:
•
Architecture and Design Considerations for the OEM Server (next)
•
OEM Request API (Client Application to OEM) on page A-5
•
Client Callback API (OEM to Client Application) on page A-23
Architecture and Design Considerations for the OEM Server
The Open Enterprise Management (OEM) Server provides a standard interface to client
applications needing to integrate with an Enterprise Management Framework. The
server executes as a standard Win32 ActiveX EXE, which allows any OLE-enabled
application to communicate with it.
For a client application to use the OEM, the client must:
•
Use the OEM Request API to pass request information to the OEM. For more
information, see OEM Request API (Client Application to OEM) on page A-5.
•
Support OLE Automation callbacks, which effectively means it must run as an
ActiveX EXE.
•
Create a callback class that implements the Client Callback API to receive command
information from the OEM. For more information, see Client Callback API (OEM
to Client Application) on page A-23.
The OEM Request API allows client applications to add managed objects and their
corresponding popup menus to the framework, set object state, and remove managed
objects or popups from the framework. In addition, the OEM request API also supplies a
set of debugging methods to assist in client application development. The intent is that
this standardized interface be simple to use from a client standpoint; the EM Adapter
portion of the OEM Gateway handles all framework-specific issues.
The Client Callback API provides a standard means of communicating framework
notification or command information back to client applications. The client is not
required to have any knowledge of the workings of the framework; the only requirement
is that the client must completely implement the set of methods and properties that make
up the API.
The OEM Server is a shared resource; as such, it could potentially become a bottleneck
for client applications or the EM framework. To remedy this situation, the OEM Server
maintains inbound and outbound queues on both the request and callback side. It
immediately queues all requests received from clients and replies to them. This prevents
clients from being blocked while the server is processing the request. The same
mechanism is used when processing callbacks from the EM framework adapter; the
server queues the commands and replies to the request. This allows the adapter (and
potentially the framework) to continue with other operations while the callback is being
handled by the server.