1994
DOI: 10.1007/bfb0013414
|View full text |Cite
|
Sign up to set email alerts
|

High-level access APIs in the OSIMIS TMN platform: Harnessing and hiding

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

1995
1995
1996
1996

Publication Types

Select...
3
2

Relationship

2
3

Authors

Journals

citations
Cited by 5 publications
(5 citation statements)
references
References 1 publication
0
5
0
Order By: Relevance
“…Managed objects are accessible across management interfaces but the internal structure of the communicating applications is not dictated and may not be object-oriented. Platform infrastructures such as OSIMIS [13] have shown how such an object-oriented information specification may be mapped onto a fully object-oriented engineering framework, providing high-level Application Programming Interfaces (APIs) and various transparencies [12]. The Network Management Forum (NMF) is currently looking to standardise such object-oriented APIs.…”
Section: Osi Management Addresses the Open Communication Between Applmentioning
confidence: 99%
“…Managed objects are accessible across management interfaces but the internal structure of the communicating applications is not dictated and may not be object-oriented. Platform infrastructures such as OSIMIS [13] have shown how such an object-oriented information specification may be mapped onto a fully object-oriented engineering framework, providing high-level Application Programming Interfaces (APIs) and various transparencies [12]. The Network Management Forum (NMF) is currently looking to standardise such object-oriented APIs.…”
Section: Osi Management Addresses the Open Communication Between Applmentioning
confidence: 99%
“…Such interfaces help a lot the TMN application developer by providing the opportunity to spend more time on the application functionality rather than being concerned with handling the complexity of the "raw" CMIS service. Work on high-level, object-oriented Q (CMIS and Directory Access) APIs in C++ has been conducted in the RACE Integrated Communications Management (ICM) project [3], resulting in OSIMIS object-oriented TMN platform [1] [3]. Work is also ongoing in this area for the standardization of such APIs, driven by the Network Management Forum (NMF) [4].…”
Section: A Scripting Language For the Tmn Ws-os Motivationmentioning
confidence: 99%
“…The OSIMIS high-level C++ APIs encapsulate the underlying CMIS and Directory Access services and the Q protocol stack by using object-oriented principles and techniques. One particular abstraction for TMN OSFs functioning in managing role is the Remote MIB (RMIB) [3][1] access infrastructure, which involves the use of proxy objects (of a RMIBAgent class). These act as the local image of the remote agent applications (one-to-one mapping), and provide CMIS-like message passing, simplifying many of the CMIS access details e.g.…”
Section: A Scripting Language For the Tmn Ws-os Motivationmentioning
confidence: 99%
See 1 more Smart Citation
“…Higher object-oriented abstractions can be built on top of the CMIS services and such approaches were initially investigated in the RACE-I NEMESYS project while work in this area was taken much further in the RACE-II ICM project [Pav94].…”
Section: Generic High-level Manager Supportmentioning
confidence: 99%