1999
DOI: 10.1007/978-3-642-60111-8_19
|View full text |Cite
|
Sign up to set email alerts
|

Integration of SNMP into a CORBA-and Web-Based Management Environment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
6
0

Year Published

1999
1999
2011
2011

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 10 publications
(6 citation statements)
references
References 2 publications
0
6
0
Order By: Relevance
“…SNMP traps may be converted to Jini events which may be forwarded to appropriate event listeners according to a local policy, e.g., a generic Jini enabled messaging service to present them to a user. Our CORBA SNMP gateway [2] is an example of such a generic gateway. Since Jini is not restricted to native Java communication methods like RMI but easily integrates with CORBA systems, a Jini encapsulation of arbitrary CORBA services can be provided without much effort.…”
Section: A Vision Of a Jini-enabled Management Federationmentioning
confidence: 99%
“…SNMP traps may be converted to Jini events which may be forwarded to appropriate event listeners according to a local policy, e.g., a generic Jini enabled messaging service to present them to a user. Our CORBA SNMP gateway [2] is an example of such a generic gateway. Since Jini is not restricted to native Java communication methods like RMI but easily integrates with CORBA systems, a Jini encapsulation of arbitrary CORBA services can be provided without much effort.…”
Section: A Vision Of a Jini-enabled Management Federationmentioning
confidence: 99%
“…Based on these, and seeking an integration with heterogeneous systems, two principal lines of work arose: an attempt to achieve integration of the systems using the same network management protocol, as is the case of [16] and [17] with the use of Common Object Request Broker Architecture (CORBA); and more ambitiously, to propose a network management protocol which would be independent of the infrastructures. Some of the more extensive proposals include: CORBA/JIDM, specification of the work group Joint Inter-Domain Management (JIDM) [18] of the Object Management Group (OMG) [19]; CIM/WBEM, proposal of the Distributed Management Task Force (DMTF) [20] using techniques oriented towards Computer Integrated Manufacturing (CIM) objects and interoperation using HTTP and XML with Web Based Enterprise Management (WBEM); JMX specification defined by the Java Community Process (JCP) [21] which defines a series of Application Programming Interfaces (API) oriented to Java for network management; and WSManagement specification carried out by various companies in the sector (Sun, Intel, MS, AMD) for the integration of service management systems and resources based on Web Services.…”
Section: Introductionmentioning
confidence: 99%
“…Based on these, and seeking an integration with heterogeneous systems, two principal lines of work arose: an attempt to achieve integration of the systems using the same network management protocol, as is the case of [3] and [4] with the use of CORBA; and more ambitiously, to propose a network management protocol which would be independent of the infrastructures. Some of the more extensive proposals include: CORBA/JIDM, specification of the work group JIDM of the OMG; CIM/WBEM, proposal of the DMTF using techniques oriented towards CIM objects and interoperation using HTTP and XML with WBEM; JMX specification defined by the JCP which defines a series of API's oriented to Java for network management; and WS-Management specification carried out by various companies in the sector (SUN, INTEL, MS, AMD) for the integration of service management systems and resources based on Web Services.…”
Section: Introductionmentioning
confidence: 99%