Stibium - Web Application - V3.0 - 概要
by Risk-Capital Research and Technology - 製品のタイプ: アプリケーション / Web Service
結果
Stibium Naming Server by Risk-Capital Research and Technology
Store a hierarchical structure of named items. The Stibium™ Naming & Directory Server enables data and Java objects to be encoded and stored in the form of xml within hierarchical database-document structures, together with any associated attribute data and/or meta-data. Stibium is deployed as a web-service module, which runs within the Apache Tomcat Web server. Stibium makes these objects and data available via JNDI-compliant naming and directory services, which can be accessed by distributed clients via SOAP xml Web services. The server maintains a hierarchical structure of named bindings which can be shared and manipulated by web-enabled clients and other agents active on 'the grid'.
The Stibium™ Naming & Directory Server is a hierarchical database that enables Java objects and data to be encoded, and stored together with any 'directory-service meta-data' attributes, in the form of xml, within a hierarchical xml-document structure. Stibium is deployed as a web-service module, that runs under the Apache Tomcat web server.
Stibium makes these objects and data available via JNDI-compliant naming and directory services, that can be accessed by distributed clients via SOAP xml web services. The server maintains a hierarchical structure of named bindings which can be shared and manipulated by web-enabled clients and other agents active on 'the grid'.
The Stibium distribution includes a web application that runs under the Apache Tomcat web server and a JNDI service provider that supports and extends standard JNDI naming and directory services.
Applications for Stibium
Stibium can be used in many situations where it is necessary or desirable to store a hierarchical structure of named items and where either local or remote web-service access is appropriate.
This can be particularly useful when many distributed agents have a shared stake in the data that is stored, when the bindings are dynamic or subject to change, and/or when it is necessary to 'mix and match' JNDI and xml based technologies.
Some Key Features:
Naming and directory services that are accessible via SOAP xml web-services
JNDI standard service provider
XML-based context and binding storage structure
Configurable binding translation and persistence mechanism
Robust mechanism for user authentication
Additional 'ContextExtension' functionality, including xpath querying
Web- and grid-enabled technology
AJAX-based web front end
What is the 'Stibium' Naming Server ?
The Stibium naming server provides Naming and Directory Services that can be accessed by web-enabled elements of distributed systems. A 'naming service' is a general term for a service that provides access to named bindings and/or their attributes.
Stibium's services are provided by a web application. This makes them accessible via SOAP xml web services, which are naturally both web-enabled and grid-enabled.
The Stibium web application uses xml data storage techniques and can store bindings that range from simple data types, such as integers and strings, through to arbitrarily complex user-defined types. Complex types are handled by using configurable state-serialization and object-encoding techniques.
The items of data that are stored by Stibium are identified by name, and are held in an xml document. In the terminology of distributed systems the association between a name and an item of data is known as a binding. These bindings can be stored in either persistent or transient mode. Transient items are only held in memory, whilst persistent items are also stored on the web server's file system. Stibium's design includes a number of features that enable it to work with either JNDI and/or xml-based application environments.
Java clients can access these naming and directory services using the Stibium JNDI Service Provider. This acts as a client to the Stibium web application, and implements the standard JNDI naming and directory service API.
The Java JNDI
The Java Naming and Directory Interfaces (or JNDI) is a set of APIs built into Java that provides a standardised means for communicating and interacting with a wide range of naming and directory services. More information is given on our Java JNDI overview page.
The Stibium JNDI service provider implements the javax.naming.directory.DirContext interface for directory services, which extends the javax.naming.Context interface for naming services.
Naming and Directory Services
In a distributed system, names are used to refer to a wide variety of types of resource, such as computers, files, remote objects and web services. In this context, a pure name is a simple key used to identify such an item uniquely within the appropriate scope or namespace.
The role of a naming service is to resolve a name: that is, to map a name onto either the resource that it identifies, or more often, onto attributes of that resource, for example, a network address. A well-known and widely-used example of this type of service is the Domain Name System (or DNS) which is used to map Internet host names onto their corresponding network IP addresses.
Naming systems are often hierarchical in nature, and then use segmented or compound names, whose components reflect the levels/nodes of the corresponding naming hierarchy.
Within a distributed computing environment, naming services constitute a significant part of the infrastructural glue that provides integrity, flexibility and resilience to that environment. This type of model is well-established, although not necessarily very widely appreciated. The Java JNDI is the standard API framework that is built into both Java J2SE and J2EE. It facilitates uniform access to naming and directory services.
Naming and directory services are often used in situations where there is a need to provide distributed agents with bindings that are shared and/or dynamic. A typical application is service registration and discovery.
Directory Services
Directory Services are an extension of naming services that also include the ability to store, manipulate and recover attributes associated with contexts and bindings. In JNDI terms, such directory services extend naming services through a richer API, which provides access to additional attribute-related functionality.
SOAP (Note1) XML Web-Services
Stibium's naming services are made available to software clients via SOAP xml web-services. This is a 'remoting' mechanism that enables function calls to be made across a network using standardised Internet techniques and protocols. Messages between the service end points are represented textually in the form of xml, according to the SOAP encoding rules.
Whilst the SOAP protocol is, in principle, independent of the mechanism used to transport xml messages between the end points, most often (and in this case) they are sent using the Internet standard http or https transport protocols.
By providing these xml web services, Stibium's functionality can, in principle, be made available to any SOAP-enabled client on the web or the grid, via either the Internet or a local network. This type of web service is rapidly becoming a widely-adopted, and perhaps even the dominant, new mechanism for providing such services across a wide range of operational contexts and hardware/software platforms.
The combination of http and xml makes such services widely accessible and provides for a high degree of interoperability between the components of a distributed systems framework, across hardware, software and operating system boundaries.
Note1. The original SOAP acronym: Simple Object Activation Protocol has now been deprecated on the (not unreasonable) grounds that SOAP does not necessarily have to have anything to do with Objects and their Activation, and is not especially Simple.
The term SOAP is still used, but it is no longer intended to have its original meaning.
PartNumbers: PC-517938-130600 517938-130600 PC-517938-130601 517938-130601 PC-517938-130602 517938-130602
PurchaseOptions: Stibium V3.1.0 1 Annual Development Server License (per server installation -upto 8 clients) , Stibium V3.1.0 1 Annual Production Server License (per server installation -First 8 clients) , Stibium V3.1.0 1 Annual Additional Production Server License (per server installation - for each additional set of 8 clients)
Resources: Read the Stibium Getting Started Guide, Read the Stibium help file, Read the Stibium Technical Manual, Browse the Stibium Java documentation, Browse the Stibium FAQ Web page, Read the Stibium End User License Agreement
Operating System for Deployment: Windows Server 2008, Windows Vista, Windows XP, Windows Server 2003, Windows 2000, Sun Solaris 10, Sun Solaris 9, Sun Solaris 8, Sun Solaris 7, Linux Kernel V2.4.x, RedHat Linux 9.x, RedHat Linux 8.x, SUSE Linux 9.x, SUSE Linux 8.x
Architecture of Product: 32Bit
Product Type: Application
Application Type: Web Service
Keywords: RCRT - Risk-Capital Research and Technology webservices web-services Author Name names naming server servers service services
クイック リンク
