Wednesday, December 10, 2014

TIBCO API exchange gateway Overview || ASG Components

TIBCO API exchange gateway is an event-based routing engine which processes the requests and responses at high speed. Using this platform, users can route the APIs requests from consumers to various target services exposed by an organization’s internal service layer. 

TIBCO API exchange gateway provides the following key features:

• Receives, routes and forwards the requests at a high speed 
• Routes the requests between any requestor and any service endpoint 
• Protects from overuse of target service endpoints 
• Protects the access of target service endpoints from unauthorized partners 
• Reports operation activity such as performance and fault monitoring 
• Ensures service level agreements are met. 

Following diagram shows an overview of the Product functionality.

Active Matrix Service Gateway : Main Components

Design Time Components: 

The user can perform the following tasks: 
• Configure the data for a project used by Core Engine at runtime 
• Develop custom extensions to change the default behavior of the Core Engine 

Config UI 

TIBCO API Exchange Gateway provides a web-based configuration user interface (UI). Using Config UI, users can enter information such as partner data, partner operations, partner groups, Operations, mappings, throttles and routing etc. This information is used by the Core Engine at run time for the various functions of the gateway.


Studio is a design time environment. Using the studio, users can design and develop custom extensions. Custom extensions can be integrated with the default implementation to customize the default behavior of the Core Engine.

Runtime Components:

TIBCO API Exchange Gateway provides runtime components in two layers.
  • Gateway Operational Layer
  • Gateway Management Layer 
Gateway Operational Layer 
The Gateway Operational layer consists of the following sub components. 

Core Engine

The Core Engine is a high-performance, event-based, service-request routing engine that receives requests as events and uses the rules engine to determine where requests are handled. 

Cache Agent

The cache Agent stores the cache data for all objects of the cluster.

Apache HTTP Server (Optional)

This module communicates with the facade component to forward the requests for further processing.Optionally,a JMS server can be deployed to sue the JMS transport.

We can use the Apache HTTP server as follows.
  • Use Apache HTTP server as it is
  • Apache Module for RV channel 
Gateway Management Layer
The Gateway Management layer provides request tracking and logging. It has the following sub components.

Central Logger 

The Central Logger provides centralized logging of messages in a database. 

Global Throttle Manager 

The Global Throttle Manager manages the Facade Throttle Manager and Service Throttle Manager. This component maintains the state of all global throttles in both Facades (Facade Throttles) and Routers (Service Throttles). 

Cache Cleanup Agent 

The Cache Cleanup Agent component clears the cache based on the size and age of the cached values. 

Monitoring and Management Server 

The Monitoring and Management Server is the central management component that monitors the status and manages the operational tasks of all components in a gateway cluster. 

Gateway Reporting (Optional) 

The Gateway Reporting component generates various type of reports based on the data logged by the Central Logger component. This component integrates with the TIBCO Spotfire product to display the metrics. 

The following diagram illustrates the components.

External clients access the Apache HTTP server with requests. An ASG Rendezvous module is used by an Apache HTTP server to forward the requests to ASG, as Rendezvous messages.

The ASG-Core engine performs most of the routing, throttling, access control and other functions. Other engines can be started as an when needed, and they perform specific functions.

No comments:

Post a Comment

back to top