Solstice Enterprise Manager 4.1 Developing CORBA Applications | ![]() ![]() ![]() ![]() ![]() |
IDLs Used by SEM CORBA Gateway
The first section of this appendix describes some of the IDLs that are part of either the JIDM standards or the OMG standards. The IDL files specific to Solstice Enterprise Manager (Solstice EM) (which are not part of any standards) are documented in the second section of this appendix.
This appendix describes the following topics:
The following is a list of IDLs that the SEM CORBA Gateway implementation includes:
- ASN1Limits.idl
- JIDM.idl
- X501Inf.idl
- ASN1Types.idl
- OSIMgmt.idl
- X711CMI.idl
- CosLifeCycle.idl (Life Cycle Service)
- CosNaming.idl (Naming Service)
- CosEventChannelAdmin.idl (Event Channel Admin)
- CosEventComm.idl (Event Service)
- SEMAuthenticationProxy.idl
- EventPortRegistry.idl
- ASN1TypesExt.idl
- CMIExt.idl
- OSIMgmtExt.idl
- SEMMetaData.idl
A.1 IDLs Based on Standards
- This IDL file defines the maximum and minimum (biggest negative) double values that your machine can hold, for IDL interfaces. Use conditional compilation to support multiple architectures.
- This IDL file comprises a collection of interfaces that together define a basic set of services for developing systems management applications based on CORBA. Following the JIDM reference model, these interfaces may be used between manager applications and JIDM Frameworks, or between JIDM Frameworks and agent applications.
- From the Manager application perspective, the following interfaces are used:
- The ProxyAgent interface
- The ProxyAgentController interface
- The ProxyAgentFinder interface
- The EventPort interface
- The EventPortFactory interface
- From the Agent application perspective, the following additional interfaces are used:
- The DomainPort interface
- The DomainPortFactory interface
- The EventPortFinder interface
- This IDL file contains mappings for the pre-mapped or pre-defined types as part of the JIDM standard.
- This IDL file provides generic IDL mapping for those ASN1 types that do not have a generic IDL mapping in the CORBA/TMN Interworking standard (also known as JIDM). This generic mapping is also known as Generic Translation (GT). The mappings apply only to those ASN1 types that are not already mapped by the JIDM standard in X711CMI.idl and X501Inf.idl; types mapped in these IDL files are known as pre-mapped or pre-defined types.
- This IDL file defines the following interfaces:
- The ProxyAgent interface
- The NamingContext interface
- The ManagedObject interface
- The ManagedObjectFactory interface
- The LocalRoot interface
- The LinkedReplyHandler, EndOfRepliesHandler and MultipleRepliesHandler interfaces
- The RepliesIterator and BufferedRepliesHandler interfaces
- The LName interface
- This IDL file contains mappings for the pre-mapped or pre-defined types also, as part of the JIDM standard.
- The Life Cycle Service defines the conventions used when creating, copying, deleting, and moving CORBA objects.
- The IDL file defines the following interfaces:
- The FactoryFinder interface
- The LifeCycleObject interface
- The GenericFactory interface
- The Naming Service obtains remote references to application-specific objects.
- The IDL file defines the following interfaces:
- The NamingContext interface
- The BindingIterator interface
- The NamingContextFactory interface
- The ExtendedNamingContextFactory interface
- The LNameComponent interface
- The LName Interface
- The LNameFactory interfaces
- The Log interface
- This IDL file defines the following interfaces:
- The ProxyPushConsumer interface
- The ProxyPullSupplier interface
- The ProxyPullConsumer interface
- The ProxyPushSupplier interface
- The ConsumerAdmin interface
- The SupplierAdmin interface
- The EventChannel interface
- The EventChannelFactory interface
- The EventFactory interface
- The Event Service provides a decoupled communication channel between CORBA objects.
- The IDL file defines the following interfaces:
- The PushConsumer interface
- The PushSupplier interface
- The PullSupplier interface
- The PullConsumer interface
A.2 IDLs Specific to SEM CORBA Gateway
This section documents each of the IDLs listed above in the SEM CORBA Gateway-specific list.
- This IDL file implements an interface called AuthenticationProxy. The methods provided by this interface serve the following functionality:
- To check if access control is turned in the MIS
- To get the User Id and password from the client
- To authenticate the user on the MIS host
- The client application developer can use the AuthenticationClientBody class to interact with AuthenticationProxy.
- This IDL file contains one interface specified by name: EventPortRegistry. This is implemented by the Event Port Registry gateway (EPR). The methods provided by the interface serve the following functionality:
- Creation of EventPorts
- Find EventPort for the key and the criteria
- Find EventPort given the AE-title
- These IDL files provide support for specifying the managed objects in text format and the functions supported are basically the same as those defined in the JIDM IDL files. For example, the OSIMgmtExt.idl extends the functions supported in OSIMgmt.idl by defining functions as listed below:
- The JIDM document (OSIMgmt.idl) defines names of managed objects specified as CosNaming::Name format (which complies with the OMG CORBA standards). For more details refer to the OMG Naming Service standards.
- This is the IDL file which contains the interface MetaDataRepository, along with the definition of all the ASN1 kinds that the Metadata Repository will support.
- The interface MetaDataRepository has methods which support the following functionality.
- Get ASN1 type for the given ASN1 element
- Get textual name for an element given the ASN1 name
- Look up Node by name
- Look up Node by id
- Get textual representation of an object specified in oid
- Get oid by name
- Get doc list
- Get managed object class attributes given oid
- Get managed object class attributes given name
- Get managed object class notifications by oid
- Get managed object class notifications by name
Sun Microsystems, Inc. Copyright information. All rights reserved. |
Doc Set | Contents | Previous | Next | Index |