API Management 10.4 | Using CentraSite | Introduction | Topology and Architecture
 
Topology and Architecture
Basic Topology
CentraSite consists of two basic components:
* CentraSite Application Server Tier. The CentraSite Application Server Tier is a web application that runs on the Software AG Runtime. This component hosts the CentraSite graphical user interfaces and also supplies the UDDI V3.0 interface to the registry.
* CentraSite Registry Repository. The CentraSite Registry Repository is the portion of CentraSite that hosts the registry and the repository.
Typically, both components reside on the same machine. However, if conditions at your site require it, you can install these components on separate machines.
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 CentraSite components that are provided as web application. The components of the CentraSite Application Server Tier function as clients of the CentraSite Registry Repository component.
CentraSite Control is CentraSite's browser-based user interface, providing general purpose features for administrators, designers, and end users.
CentraSite Business UI is a lightweight alternative to CentraSite Control, offering high-level features for business users.
The CentraSite Server authenticates client applications to the CentraSite Registry Repository.
The CentraSite Application Server Tier hosts the UDDI services that client programs use to interact with CentraSite using the UDDI V3 API.
The CentraSite Control, CentraSite Business UI, and UDDI services interact with the Registry and Repository component using the CentraSite API for JAXR (registry) and HTTPS (repository).
The CentraSite Registry 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 CentraSite and ensures that the data objects in the registry conform to the CentraSite information model.
Client programs interact with the registry portion of this component using the CentraSite API for JAXR and the CentraSite API for XQuery. Client programs interact with the repository portion of this component using HTTP.
Client programs do not interact directly with the CentraSite Registry Repository. Instead, the communication from the client is always routed through the CentraSite Server component of the Application Server Tier.
UDDI clients interact with CentraSite using 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 integrated with CentraSite.
XQuery and JAXR-based clients interact with the CentraSite Server component of the Application Server Tier. These clients include the CentraSite plug-in for Eclipse, third-party applications developed by CentraSite Community and (potentially) applications developed by your own organization.
Authentication of the client communication is performed by CentraSite Server. Therefore, the clients do not send their requests directly to the Registry Repository but instead to the CentraSite Server. The CentraSite Server forwards authenticated client requests to the Registry Repository.
Copyright © 2015- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release