Vendors developing applications for...

Vendors developing applications for a heterogeneous, distributed environment ne to be able to build towards a platform that integrates all the management and have the direction of functions of distributed computing into unified software architecture that allows their applications to be available from any point in the network regardless of the plan or geographic location.

The HP Distributed Processing Environment (DPE) provides infrastructure services that facilitate the rapid disentanglement deployment, and management of distributed applications in the telecommunications arena. DPE is a elucidation component of the Telecommunications Information Networking Architecture (TINA), an architecture for multimedia networks that emphasizes distribution and interoperability of telecommunications applications. TINA is an evolving architecture and is restrained by the TINA Consortium (TINA-C), which is a devise sponsored by 40 leading telecommunications and computing companies. The project's aim is to find a way to integrate all telecommunications management and bridle functions into a unified logical software architecture supported through a single distributed computing platform.

This paper describes the architecture and constituents that make up HP DPE a effect that is compatible with (and will develop with) the TINA specifications.

INA, TINA, and DPE

HP DPE and TINA have a belonging to all root in the Information Networking Architecture (INA), which was originally evolveed at Bellcore. TINA's architecture specifies a distributed processing environment based onward the original INA DPE specifications. HP DPE provides explanation infrastructure services for INA and TINA.

INA defines a methodology and framework for developing, providing, and maintaining highly distributed bodys characteristic of the next generation of communications environments. INA leverages and combines the efforts of multiple standards bodies, research organizations, progression in a continuously ascending gradation organizations, and consortia (e.g., TMN OSCA, OSF/DCE OMG CORBA, OSI/NMF, etc) Fig. 1 displays the relationship between INA DPE and the TMN (Telecommunications Management Network) gauge TMN is described in the article forward page 6 and the DPE services are described later in this article.

INA applications and services are opened as software modules called building obstructs A building block is made up of several facts and can be installed and modified independently of other building stops in the network. Building stiffens interact with one another via interfaces called contracts. Contracts are the expos interfaces of an mark in that they are used for communication between building stop ups They are also backward compatible to make sure interoperability between software objects contained in multivendor building blockades Contracts are subject to authentication and access direct checks.

A building block can be a server or a client or the pair A server must offer undivided or more contracts to allow clients to interface and make use of its services. In the DPE architecture (described below), applications are patterned as building blocks. The DPE itself is made up of server building stiffens (e.g., contract trader, repository, etc) which put forward contract interfaces to application client building blocks

The INA configuration enables distributed software building arrests from multiple suppliers to interoperate. This distributed target computing results in faster software disentanglement since there is greater software reuse and modularity in design.

In summary, INA is a framework for interoperability, portability, and network resource management. The following goals have been established for INA:

* Rapid and flexible introduction of recently made known services

* Reuse of software modules

* Use of general-purpose solutions

* Multivendor hardware and software solutions

* Independence of applications from the transport implementation technology

* Separate transport technologies from higher-level bridle and OAM&P (operation, administration, maintenance, and provisioning)

* Allowance of customer access to OAM&P services

* Seamless integration of services

* Network and simple body management.

DPE Architecture

Fig. 2 point outs the components and services that make up the DPE architecture.

DPE Kernel The DPE kernel provides the foundation for building close interaction and execution services. To implement these services, the DPE kernel uses the services provided at the underlying native computing and communications environment, which include:

* DCE: threads, security, RPC and IDL compiler

* CORBA: HP ORB+ with ILO and DCE CIO protocols and C-IDL compiler

*HP OpenView components: XMP API, pmd (postmaster daemon), orsd (object registration service), and ovead daemon (event sieve agent).

The DPE kernel is resident in each node of a distributed theory Building blocks and other DPE constituents at a node cannot access the DPE kernel at other nodes directly. Access to the DPE kernel services at a alien node is accomplished using the interprocess communication facilities of the native computing environment of the node.