Skip to Content
United States [Change]
English
Solstice TMNscript 1.1
Data Sheet
|
Solstice TMNscript enables fast prototyping and rapid development of small, very specific TMN management applications (playing either a manager or an agent role), and Java TMN applets. The product includes a client/server architecture which facilitates remote access to services provided by TMNscript. A Java client is also included, enabling communication between TMN and Java technology-enabled applications. A Tcl client and two examples of client applications for C and C++ environments are also included. Developers using TMNscript can create client/server applications which access TMN management information without needing a Q3 stack. This is done through the remote CMIS API, which allows easy client access to TMN services from a low-cost platform such as a PC, Macintosh, or entry-level UNIX® machine. For example, customer service applications such as trouble-ticketing applications can be integrated simply and rapidly into a TMN network, using TMNscript. Solstice TMNscript can also be used to create other scripting applications. For example, Solstice TMN Agent Tester was developed over Solstice TMNscript.  Key Benefits
 Product ArchitectureSolstice TMNscript has the following modules.CMIS Extension. This allows CMIS/TMN resources to be accessed through scripts, by providing services for emitting and receiving CMIS requests. The primitives are high-level, human-readable commands built on top of XMP CAE and completely hide XOM and XMP. ASN.1 Extension. The ASN.1 Extension allows ASN.1 data to be presented in human-readable form. Primitives are provided for encoding and decoding universal ASN.1 types, tags, and so on. A compiler takes ASN.1 modules and generates encoding and decoding scripts. The generated scripts contain procedures which call the ASN.1 extension to encode/decode the types contained in the input ASN.1 modules. The scripts for encoding/decoding which have been generated can then be loaded at any time, enabling Solstice TMNscript to handle new ASN.1 syntaxes dynamically. GDMO Mapper. This is a simple extension for mapping protocol names to human-readable names and vice versa. Using this, developers can write applications without dealing with protocol names such as object identifiers. A compiler takes GDMO/ASN.1 modules and generates scripts. The generated scripts map the human-readable names contained in the modules to the correct protocol names. Metadata API. This provides access to the GDMO/ASN.1 representations of the object model itself. It enables the development of applications which learn dynamically about the structure of the information they have to handle (for example, an application can learn about new object classes and their attributes). GDMO/ASN.1 Compiler. This reads standard GDMO and ASN.1 documents, and generates information used by the ASN.1 Extension, the GDMO Mapper, and the Metadata Extension. Platforms and RequirementsRequired
|
| |||||||||
 | | | |||||||||
