 |
|
|
|
|
|
|
| Web Services
|
The Digital Harbor architecture is designed to: consume web services by invoking standards to access information; provide web services by exposing its services using standards; and to act as an interface for web services by rendering them interactively in XML and Java.
More importantly, Digital Harbor extends the "software-as-services" model by providing the blueprint that describes the relationships between services.
In other words, today's XML provides the syntax to explain 'how' web services interface with one another; Digital Harbor provides the semantics to describe 'why, when, according to what rules' they interoperate. Obviously, this blueprint is missing today, and the relationships between application logic are described in C and Java code by developers.
Digital Harbor’s approach to composite applications views web services agnostically as another source for data or business logic, just like databases, other XML documents or legacy APIs. By providing the information architecture for web services to complement the emerging computational architecture, Digital Harbor helps organizations realize the true business value associated with a service-oriented architecture.
Digital Harbor can also provide the interface that enables web services to interoperate with full context, without having to code around the state and session-management issues of typical web applications.
|
| Standards |
Digital Harbor is designed to be open, flexible and extensible with support for emerging standards including:
- J2EE
While Smart Client does not require an application server, the Fusion Server runs inside a J2EE application server. Instead of just connecting to the application server for performance and transaction support, Digital Harbor runs inside the application server and extends its basic framework with a new set of "information services" to complement the pre-packaged "computational services" provided by the application server itself. Digital Harbor utilizes the EJB 2.1 standard.
- XML
Application data within the Digital Harbor product suite is stored and transmitted in XML, simplifying the exchange of data between processes, people and systems internal and external to the enterprise.
- Web Services, WSDL & SOAP
The Digital Harbor architecture is designed to: enable the consumption of web services by invoking standards to access information; broker web services in the context of the composite domain model by exposing its services using standards; and to act as an interface for web services by rendering them interactively in XML and Java. Digital Harbor is agnostic with respect to the source of the service - EJBs, .NET services or other objects. Digital Harbor uses WSDL as a standard interface to bind to web services and SOAP as a standard protocol to communicate with them.
- JMS
Digital Harbor uses JMS (Java Messaging Service) for messaging, enabling interoperability with other standards-based platforms.
- JCA
Digital Harbor provides hooks for JCA (Java Connector Architecture), enabling interoperability with JCA-compliant systems and enabling enterprises to grow with emerging standards.
- JDO
Digital Harbor uses a Java Data Objects implementation to connect to back-end data sources, including JDBC, XML and other types.
- JSR-168
Digital Harbor supports JSR-168 for interoperability with portals. Product components can be plugged into existing portal environments from other vendors and these portal can be made "smart" to run live in the Smart Client.
- RDF / OWL (Ontology Web Language)
Digital Harbor is a member of the W3C Organization and participates on the standards committee for OWL and RDF.
|
|
| |
| |
