CentraSite Documentation : Getting Started with CentraSite : Introducing CentraSite : Topology And Architecture : Architecture
Architecture
The following diagram describes the major sub-systems on each of the two major CentraSite components and describes the types of clients that they serve.
#
Description
The CentraSite Application Server Tier (CAST) hosts CentraSitecomponents that are provided as web applications in an application server. The components of the CentraSiteApplication Server Tier function as clients of the CentraSiteRegistry Repository component.
CentraSite Control is CentraSite's browser-based user interface, providing general purpose features for administrators, designers and end users. Because this interface is built on Software AG's pluggable UI infrastructure, it can be easily extended and customized. For more information about the CentraSite Control pluggable architecture, see the CentraSite Developer’s Guide . The pluggable infrastructure also enables you to plug into CentraSiteadditional user interfaces from the CentraSiteCommunity.
The Business UI is a lightweight alternative toCentraSite Control, offering high-level features for business users.
The CentraSiteServer performs authorization of communication from client applications to the CentraSiteRegistry Repository.
The CentraSiteApplication Server Tier hosts the UDDI services that client programs use to interact with CentraSiteusing the UDDI V3 API.
The CentraSite Controland UDDI services interact with the Registry and Repository component using the CentraSite API for JAXR (registry) and HTTP (repository).
The CentraSiteRegistry Repository component manages the content of the registry and the repository. Besides housing the data that makes up the registry and repository, this component controls access to CentraSiteand ensures that the data objects in the registry conform to the CentraSiteinformation model.
Client programs interact with the registry portion of this component using the CentraSite API for JAXR and the CentraSiteAPI for XQuery. Client programs interact with the repository portion of this component using HTTP.
Client programs do not interact directly with the CentraSiteRegistry Repository. Instead, the communication from the client is always routed via the CentraSiteServer component of the Application Server Tier.
UDDI clients interact with CentraSiteusing the UDDI V3 services that reside on the Application Server Tier. UDDI clients include developer tools supplied by Community partners, third-party UDDI browsers, UDDI-compliant IDEs and UDDI registries that are federated with CentraSite.
XQuery and JAXR-based clients interact with the CentraSiteServer component of the Application Server Tier. These clients include the CentraSiteplug-in for Eclipse, third-party applications developed by CentraSiteCommunity and (potentially) applications developed by your own organization.
Authentication of the client communication is performed by CentraSiteServer. Therefore, the clients do not send their requests directly to the Registry Repository but instead to the CentraSiteServer. The CentraSiteServer forwards authenticated client requests to the Registry Repository.
Copyright © Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback