Solstice Enterprise Manager 4.1 Developing CORBA Applications Doc Set ContentsPreviousNextIndex


Appendix A

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:

  1. From JIDM standards:

  1. From OMG standards:

  1. SEM CORBA Gateway specific:

A.1 IDLs Based on Standards

  1. ASN1Limits.idl

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.

  1. JIDM.idl

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:
From the Agent application perspective, the following additional interfaces are used:

  1. X501Inf.idl

This IDL file contains mappings for the pre-mapped or pre-defined types as part of the JIDM standard.

  1. ASN1Types.idl

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.

  1. OSIMgmt.idl

This IDL file defines the following interfaces:

  1. X711CMI.idl

This IDL file contains mappings for the pre-mapped or pre-defined types also, as part of the JIDM standard.

  1. CosLifeCycle.idl (Life Cycle Service)

The Life Cycle Service defines the conventions used when creating, copying, deleting, and moving CORBA objects.
The IDL file defines the following interfaces:

  1. CosNaming.idl (Naming Service)

The Naming Service obtains remote references to application-specific objects.
The IDL file defines the following interfaces:

  1. CosEventChannelAdmin.idl (Event Channel Administration Services)

This IDL file defines the following interfaces:

  1. CosEventComm.idl (Event Service)

The Event Service provides a decoupled communication channel between CORBA objects.
The IDL file defines the following interfaces:

A.2 IDLs Specific to SEM CORBA Gateway

This section documents each of the IDLs listed above in the SEM CORBA Gateway-specific list.

  1. SEMAuthenticationProxy.idl

This IDL file implements an interface called AuthenticationProxy. The methods provided by this interface serve the following functionality:
The client application developer can use the AuthenticationClientBody class to interact with AuthenticationProxy.

  1. EventPortRegistry.idl

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:

  1. ASN1TypesExt.idl, CMIExt.idl, and OSIMgmtExt.idl

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:

TABLE A-1   OSIMgmt.idl Functions Extended in OSIMgtExt.idl
OSIMgmtExt.idl OSIMgmt.idl
cmis_get_text
cmis_get
cmis_set_text
cmis_set
cmis_create_text
cmis_create
cmis_create_sync_text
cmis_create_sync
cmis_delete_text
cmis_delete
cmis_action_text
cmis_action


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.

6) SEMMetaData.idl

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.


Sun Microsystems, Inc.
Copyright information. All rights reserved.
Doc Set  |   Contents   |   Previous   |   Next   |   Index